CA-DISK fully honors SMS constructs and rules, it they don't they will
be PMR'ed. 
That is why I need to know what HSM does, because that is the 'truth'.

Kees.

"Staller, Allan" <[email protected]> wrote in message
news:<[email protected]>...
> EXPIREBV is used for NON-SMS managed datasets. "Secondary space
management" replicates the functions of EXPIREBV for SMS managed
datasets. 
> "Secondary space management" also performs some functions that are
common to both SMS and non-SMS managed datasets.
> 
> There are good explanations of the processing differences between SMS
and non-SMS managed datasets in: 
> z/OS V1R13.0 DFSMShsm Storage Administration
> 
> BTW, does CA-DISK co-operate w/dfSMS?
> 
> HTH,
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
On Behalf Of Vernooij, CP - SPLXM
> Sent: Monday, July 02, 2012 3:14 PM
> To: [email protected]
> Subject: Re: SMS Retain Days Extra Backup Versions - question.
> 
> Allan,
> 
> Thanks for your effort so far.
> Since I am not familiar with HSM, DFSMShsm Storage Administration says
that "the next processing of the EXPIREBV command deletes" the excessive
backups. Is this secondary space management?
> 
> Kees.
> 
> "Staller, Allan" <[email protected]> wrote in message
news:<[email protected]>...
> > Kees, et. al
> > 
> > I have processed my test case. 
> > 
> > Management class attributes:
> > Expire Non-usage 15 days
> > No. of Backups DS Exists - 2
> > No. of Backups DS Deleted - 1
> > Retain Days Extra backups - 3
> > Retain Days Only backup - 3
> > 
> > Version 1 backed up 2012/06/27
> > Version 2 backed up 2012/06/28
> > 
> > According to Kees, the version 1 backup should have been deleted
> 2012/07/01. However, an HSM List command shows both versions still
exist.
> > Versions in excess of "No. of backups DS exists" are deleted
> immediately duiring the next secondary space management cycle.
> > 
> > I appears, this behavior  can be attributed to CA-Disk.
> > 
> > Just to close the loop, I will post again 15 days after the version
1
> backup was  created (2012/07/12) or earlier if something changes.
> > 
> > HTH,
> > 
> > 
> > 
> > <snip>
> > We don't have HSM, we have CA-DISK and it does as I described.
> > From the DFSMS manual I read (90% sure) that this is as designed: on
> day 100, backup#1 receives an expiration date of day 60 and is deleted
immediately.
> > It would help if someone could confirm that HSM works the same.
> > If so, a PMR against something working as designed won't stand a
> chance.
> > If not, I can PMR CA-DISK.
> > 
> > Kees.
> > 
> > "Staller, Allan" <[email protected]> wrote in message
> news:<[email protected]>...
> > > I believe I have accurately described the actual behavior in my
> shop.
> > I
> > > (admittedly) have not subjected this to a formal review.
> > > Sounds like a good PMR to me.
> > 
> > </snip>
> > 
> >
----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to [email protected] with the message: INFO IBM-MAIN
> > 
> >
----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions, send

> > email to [email protected] with the message: INFO IBM-MAIN
> > 
> ********************************************************
> For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee only. If
you are not the addressee, you are notified that no part of the e-mail
or any attachment may be disclosed, copied or distributed, and that any
other action related to this e-mail or attachment is strictly
prohibited, and may be unlawful. If you have received this e-mail by
error, please notify the sender immediately by return e-mail, and delete
this message. 
> 
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
its employees shall not be liable for the incorrect or incomplete
transmission of this e-mail or any attachments, nor responsible for any
delay in receipt. 
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
> ********************************************************
>                       
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send
email to [email protected] with the message: INFO IBM-MAIN
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
> 
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************
                        

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to