) /
HI-A-RBA * 100
In the case above this will be (662077440 - 173260800) / 662077440 * 100
= 73.8 %
*Potential Free Space (if reorganised)*
The higher percentage free space figure will be: FREESPC / HI-A-RBA * 100
In the case above this will be 517779456 / 662077440 * 100 = 78.2 %
Richard Marchant
Gadi,
I would advise you do the following so HSM knows what's where:
HSEND ADDVOL newvolser UNIT(3390) MIGRATION(ML1 NODRAIN)
HSEND ADDVOL oldvolser UNIT(3390) MIGRATION(DRAIN)
HSEND FREEVOL MVOL(oldvolser) AGE(0) TARGETLEVEL(ML1)
Once complete you can DELVOL the oldvolser.
HTH
Ri
Gadi,
HSM should move all the files.
Richard Marchant
Johannesburg
On Mon, Jul 13, 2020 at 8:43 AM Gadi Ben-Avi wrote:
> Thanks
> Will HSM move the files already on the old volume, or do I have to do it
> myself?
>
> Gadi
>
> -Original Message-
> From: IBM M
Gadi,
FREEVOL should move these files if they are good.
Check they are active files.
Richard Marchant
Johannesburg
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gadi Ben-Avi
Sent: Monday, July 13, 2020 10:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re
procedure. Then recall it as above.
HTH
Richard Marchant
Johannesburg
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gadi Ben-Avi
Sent: Monday, July 13, 2020 10:55 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Changing the volser of an HSM ML1 volume
All of the
Gadi,
Try running the FREEVOL again and then post the DFHSM log of the FREEVOL
output.
Richard Marchant
Johannesburg
On Mon, Jul 13, 2020 at 12:19 PM Gadi Ben-Avi wrote:
> Hi Again,
> The VTOC records are newish. There are some from today and some from
> earlier in the year.
>
Gadi,
Please execute the following command:
*HSEND AUDIT MEDCTL VOLUMES(ML1000) FIX*
Richard Marchant
Johannesburg
On Mon, Jul 13, 2020 at 2:27 PM Gadi Ben-Avi wrote:
> Hi Richard,
> Enclosed is the output from the FREEVOL command.
> This partition does not have any issues with H
Gadi,
Did you FIXCDS the "A" and "D" records of these files?
Was the output good?
Richard Marchant
Johannesburg
On Mon, Jul 13, 2020 at 3:02 PM Gadi Ben-Avi wrote:
> I got a bunch of messages saying
> /* ERR 141 ML1000 - SCRATCHED EMPTY DATA SET
> HSM.VTOC.T01
Jake,
Check *Secure Data Solution* by Secure Data Innovations AG
Richard
On Tue, Oct 15, 2019 at 8:04 AM Jake Anderson
wrote:
> Hi Group
>
> I am looking for alternative solution for IBM VTL. So far i have found
> luminex, EMC DLM, Model9...
>
> Are there anyother virtual tape solution for ma
Have you tried ISMF, Option 1, list the uncataloged datasets and issue
DELETEs
Richard Marchant
Edcon Stores Ltd
On Wed, Sep 12, 2018 at 1:51 PM Hilario Garcia wrote:
> Hello dear colleagues,
>
> For unknown reasons I have a volume with the following content in the vtoc:
>
>
Migration is LIMITED
On Wed, 01 Nov 2017 at 17:19, Bill Johnson <
0047540adefe-dmarc-requ...@listserv.ua.edu> wrote:
> F dfhsm,Q SETSYS
> F DFSMSHSM,Q SETSYSARC0101I QUERY SETSYS COMMAND STARTING ON
> HOST=1ARC0147I BUDENSITY=*, BUUNIT=3490, BU RECYCLE 948ARC0147I (CONT.)
> PERCENTAGE=020%, M
Tony,
When DFHSM does migration and backup by dataset (not an auto-function) it
will not MARKFULL the tape.
Make sure you users are not doing this.
An HBACKUP or a HMIGRATE command should send the result to ML1 DASD unless
ML2 is specified on the HMIGRATE command.
There are settings in the mana
S or their associated records in the BCDS or MCDS
depending whether they are backup or migration tapes.
Richard Marchant
Johannesburg
On Wed, Dec 14, 2016 at 2:03 PM, Tony Thigpen wrote:
> They are in both catalogs. I am not currently concerned with the CA-1
> catalog since CA-1 normally sc
) DAYS(0) [CONVERT]
Richard Marchant
RSA
On Tue, Feb 21, 2017 at 4:46 PM, Tony Thigpen wrote:
> I just ran the following:
>
> MIGRATE VOLUME(HDGAC0 MIGRATE(365)) ML2
>
> I got the following:
>
> ARC0570I COMMAND MIGRATION FOR HDGAC6 VOLUME(S) TERMINATED, RC=25 REASON=0
&
Jake,
Minimum allocation for a file on DASD is one track.
Richard
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jake anderson
Sent: 08 August 2012 01:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Space Allocation In Bytes
Hi,
I
particular volume(s). For non-SMS volumes (ADDVOLed with AUTOMIG turned on) and
for SMS volumes the storage group containing the volumes must be defined with
AM=Y.
Richard Marchant
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of
We could be the topside of the planet!
Richard Marchant
Johannesburg
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tom Rusnak
Sent: 26 September 2012 03:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CBT File745 (File Formatter aka OS
Dennis,
Make sure you allocate a new COMMDS do not try using an existing one.
Richard
Hello,
I want to switch to new sms commds on current environment that has same commds
shared by 3 lpars. I come from an older sms environment where each lpar had
their own set of cds's so this is differe
J.P.
Another possibility, if you write the backups to a storage group reserved for
backups, would be to use HSM's INTERVALMIGRATION option on the specific storage
group. This option runs interval migration on the hour every hour except when
PRIMARY SPACE MANAGEMENT is running. This is done by
Lizette,
ML2 data does not dedupe well, 2 to 1 if you are very lucky. DataDomains are a
very expensive option if the dedupe ratio is poor. Ask EMC if they have other
disk options that can be placed behind their DLM boxes that just have normal
compression and replication features, it should work
John,
If you are migrating to another primary volume use the command:
MIGRATE VOLUME(SYC103 MIGRATE(5)) CONVERT(VOL001)
Where VOL001 is another DFHSM managed volume
If you are migrating to ML1 or ML2 you must specify them instead of the CONVERT
keyword.
Richard
-Original Message-
Fr
Gadi,
In South Africa we have installed Luminex VTL / Data Domain solutions for
mainframe customers and it works very well. The Data Domain is not mandatory
and could be replaced with less expensive disk as Luminex now has replication
and compression capabilities, this would make it a cheaper s
Esmie,
There was quite a long thread about this very issue quite recently, please
check the archives. Unfortunately there were no easy answers.
Richard
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of esmie moo
Sent: Thursday, June 2
David,
Where are the two GDGs located? Are they on different SMS groups or different
non-SMS volumes? If they are separated are you allowing HSM to perform
autobackup on both entities?
Richard
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Before you install Z/OS 1.13 do you need to remove the IMBED and REPLICATE
parameters from your old Usercatalogs or will they co-exist with Z/OS 1.13?
We are currently running Z/OS 1.11 and a number of the Usercatalogs have the
IMBED parameter with no obvious ill affect.
Richard
ices
T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Richard Marchant
Sent: Tuesday, July 16, 2013 12:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Missing HSM backups
David,
Mike,
Might be a silly question but does DFHSM have authority to update your master
catalog?
Richard
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mike Wojtukiewicz
Sent: Friday, July 19, 2013 1:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Lizette,
One of the main selling points of the DataDomain is the Global Compression
feature (data deduplication). This works well for multiple backups but not for
archived data which ML2 data effectively is, so in your case using a DataDomain
at the backend would be a very expensive option.
L
Theo,
Check out Glen Wilcock's 'What's new in DFHSM' March 2014. This was
presented at SHARE in Anaheim in 2014. You can google it and download.
There is a section called 'Storage Tiering' which goes into detail
about SPMGCLTR (not SPGMCLTR) and the &A
TORCLAS)
> WHEN ('EASYTIER') SET &STORGRP = 'EASYTIER'
> WHEN ('SCSATA') SET &STORGRP = 'SGSATA'
> OTHERWISE SET &STORGRP = &STORGRP
>END
> ELSE ...
>
> -Original Message-
> From: IBM
llocated tracks . : 1
>
> Storage class . . . : USRSCTR1Allocated extents . : 1
>
> Volume serial . . . : UMGG13
>
> Device type . . . . : 3390
>
> Data class . . . . . : USERS
>
> Organization . . . : PS Current Utilization
>
> Rec
Volume serial . . . : UMGG13
>
> Device type . . . . : 3390
>
> Data class . . . . . : USERS
>
> Organization . . . : PS Current Utilization
>
> Record format . . . : FB Used tracks . . . . : 0
>
> Record length . . . : 80
John,
I would advise re-allocating the COMMDS file. The old COMMDS holds old
conflicting infomation, you need to start with a new clean one.
Richard
From: IBM Mainframe Discussion List [IBM-MAIN@listserv.ua.edu] on behalf of
John Norgauer [john.norga...
33 matches
Mail list logo
