Re: New DFSMSrmm retention method
Thanks, Mike. Rereading the background posts helped me see my mix-up. What I had missed earlier was the fact that EXPDT is just JCL independent of RMM (I didn't know if there was a VRS rule with the same name as the JCL parameter...) and WHILECATALOG was the only VRS rule in place. So the WHILECATALOG would hold the tape forever, never getting to the EXPDT processing. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Wood Sent: Monday, October 22, 2012 5:42 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: New DFSMSrmm retention method Rex, The only way to link a VRS to the volume EXPDT is to use the UNTILEXPIRED retention type in the VRS. So, unless, UNTILEXPIRED is used, the WHILECATALOG VRS retains the data set until it is uncataloged, and only then, when the data set is dropped from VRS retention is the volume EXPDT considered. From R13, with EXPDT retention method you can ensure that only the volume EXPDT is considered. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
> From: Mike Wood > To: IBM-MAIN@LISTSERV.UA.EDU > I am sceptical about using RETPD(93000) as a default retention for all new > tape data sets. > But, if that works for you . . . . . Well, we have been keeping cataloged datasets on DASD forever (NOLIMIT in MC). Therefore, I'd use the same principle for cataloged datasets on tape. Whether that is questionable, I agree. > I hope that helps you, it does, thanks a bunch! Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
On Tuesday, 23 October 2012 08:17:09 UTC+1, Walter Marguccio wrote:
> Mike,
> I understand that, for cataloged datasets, the WHILECATALOG keyword,
> specified
> in a single VRS or in a VRS chain, always wins. Am I correct ?
Correct. while a data set is cataloged and matching to the example VRS it will
be VRS retained.
> Ever since we migrated to rmm, we have:
> a) RETPD(5) in EDGPRMxx and
> b) one VRS defined as: dsname('**') WHILECATALOG LOCATION(HOME)
> with this setup, a cataloged dataset with a given RETPD/EXPDT will never be
> deleted.
>
> If I want RETPD/EXPDT to be honored for a dataset, and want to stick to VRSEL
> retention method, I suppose I need to change:
> a) RETPD in EDGPRMxx from 5 to 93000 (keep the data almost forever)
> b) update my only VRS as: dsname('**') UNTILEXPIRED LOCATION(HOME)
Making the above change will ensure that VRS retention is assured until the
EXPDT is reached
> Or, I change the global retention method from VRSEL to EXPDT, and still need
> to change
> a) RETPD in EDGPRMxx from 5 to 93000
> Are my assumptions correct ?
Looks like it. Once the parmlib OPTION RETENTIONMETHOD(RETPD) is in use, any
volumes that use this retention method will not be considered by VRSEL
processing and only the volume EXPDT used to determine when EXPROC will expire
the volume.
I am sceptical about using RETPD(93000) as a default retention for all new tape
data sets. But, if that works for you . . . . .
I hope that helps you,
Mike Wood
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
> From: Mike Wood
> To: IBM-MAIN@LISTSERV.UA.EDU
> So, if still cataloged, and the VRS specifies WHILECATALOG,
> a data set will be retained regardless of the EXPDT/RETPD.
Mike,
I understand that, for cataloged datasets, the WHILECATALOG keyword, specified
in a single VRS or in a VRS chain, always wins. Am I correct ?
Ever since we migrated to rmm, we have:
a) RETPD(5) in EDGPRMxx and
b) one VRS defined as: dsname('**') WHILECATALOG LOCATION(HOME)
with this setup, a cataloged dataset with a given RETPD/EXPDT will never be
deleted.
If I want RETPD/EXPDT to be honored for a dataset, and want to stick to VRSEL
retention method, I suppose I need to change:
a) RETPD in EDGPRMxx from 5 to 93000 (keep the data almost forever)
b) update my only VRS as: dsname('**') UNTILEXPIRED LOCATION(HOME)
Or, I change the global retention method from VRSEL to EXPDT, and still need to
change
a) RETPD in EDGPRMxx from 5 to 93000
Are my assumptions correct ?
Walter Marguccio
z/OS Systems Programmer
BELENUS LOB Informatic GmbH
Munich - Germany
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
Rex, The only way to link a VRS to the volume EXPDT is to use the UNTILEXPIRED retention type in the VRS. So, unless, UNTILEXPIRED is used, the WHILECATALOG VRS retains the data set until it is uncataloged, and only then, when the data set is dropped from VRS retention is the volume EXPDT considered. From R13, with EXPDT retention method you can ensure that only the volume EXPDT is considered. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
Mike, Your response confused me (easily done, I know). When VRSes are used, and in recent releases, when VRSEL retention method is used, all the retention types in the VRS must be true for a data set to be retained. So, if still cataloged, and the VRS specifies WHILECATALOG, a data set will be retained regardless of the EXPDT/RETPD. You said that all the retention types in the VRS must be true for the dataset to be retained. In my thinking, another way of saying that is if any of the retention types is NOT true anymore, the dataset will be deleted. So if you are using both EXPDT/RETPD and WHILECATALOG, if either of them becomes false, the dataset will be deleted. Yet you said it would be kept regardless of RETPD/EXPDT. Where is my disconnect? Thanks. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mike Wood Sent: Monday, October 22, 2012 2:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: New DFSMSrmm retention method On Monday, 22 October 2012 10:08:36 UTC+1, Walter Marguccio wrote: > Hello all, > ever since we migrated from CA-1 to rmm in 2008, I have been told that > the latter would never delete a cataloged dataset, even if the dataset > had a RETPD or EXPDT specified at allocation time. In other words, the > VRSEL retention method would never allow the above, no matter which > combination of VRS(es) was used. > Has the new EXPDT retention method (introduced at z/OS 1.13 level) > been implemented in order to satisfy such requirement ?� > > Walter Marguccio Walter, What you remember/were told, about cataloged tape data sets is not in fact true. rmm can "delete" a cataloged tape data set if the matching VRS includes some other retention type than WHILECATALOG. When VRSes are used, and in recent releases, when VRSEL retention method is used, all the retention types in the VRS must be true for a data set to be retained. So, if still cataloged, and the VRS specifies WHILECATALOG, a data set will be retained regardless of the EXPDT/RETPD. The EXPDT retention method was introduced to provide an option for retention that did not require post processing other than simply checking the volume EXPDT vs the current date. Thus reducing the overhead of determining whether to scratch a tape. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: New DFSMSrmm retention method
On Monday, 22 October 2012 10:08:36 UTC+1, Walter Marguccio wrote: > Hello all, > ever since we migrated from CA-1 to rmm in 2008, I have been told that > the latter would never delete a cataloged dataset, even if the dataset > had a RETPD or EXPDT specified at allocation time. In other words, the > VRSEL retention method would never allow the above, no matter which > combination of VRS(es) was used. > Has the new EXPDT retention method (introduced at z/OS 1.13 level) been > implemented in order to satisfy such requirement ?� > > Walter Marguccio Walter, What you remember/were told, about cataloged tape data sets is not in fact true. rmm can "delete" a cataloged tape data set if the matching VRS includes some other retention type than WHILECATALOG. When VRSes are used, and in recent releases, when VRSEL retention method is used, all the retention types in the VRS must be true for a data set to be retained. So, if still cataloged, and the VRS specifies WHILECATALOG, a data set will be retained regardless of the EXPDT/RETPD. The EXPDT retention method was introduced to provide an option for retention that did not require post processing other than simply checking the volume EXPDT vs the current date. Thus reducing the overhead of determining whether to scratch a tape. Mike Wood -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
New DFSMSrmm retention method
Hello all, ever since we migrated from CA-1 to rmm in 2008, I have been told that the latter would never delete a cataloged dataset, even if the dataset had a RETPD or EXPDT specified at allocation time. In other words, the VRSEL retention method would never allow the above, no matter which combination of VRS(es) was used. Has the new EXPDT retention method (introduced at z/OS 1.13 level) been implemented in order to satisfy such requirement ? Walter Marguccio z/OS Systems Programmer BELENUS LOB Informatic GmbH Munich - Germany -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
