Re: DFHSM QUESTION - EXPIRATION OF DSN
I don't think so. Or if you are right then there are some big issues in the next few years that IBM's own products won't be able to support. As an example IBM semi announced that soon there will be dynamic storage(DASD) expansion and it will be done with volser (ex ABC001,ABC002 etc etc) ie adding volsers without having to update the ACS routines and DFDSS statements/ or DD JCL and this will apparently include DFHSM and any other product that needs Backup/restore generic volsers. DMS had this ability *LONG TIME AGO*. I don't see any issue about integrity with items like that (in fact our DASD boss when the MSS came in worked with the DMS people to support the concept of MVSGRP in DMS, IBM never did it. Ed On Oct 30, 2014, at 12:48 AM, Elardus Engelbrecht wrote: Ed Gould wrote: There are still quite a few items that DFDSS hasn't caught up with but thats a different horse to flog. Although I was reading an article about z/OS and there are a few things percolating up the like dynamic DASD and the like that will make us wonder why it took so long. Possible reasons: Backward compatibility issues? No business case to catch up? Integrity issues? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
We put unused volsers into SMS Storage groups then init actual volumes when more space is needed. On Thu, Oct 30, 2014 at 12:20 PM, Ed Gould edgould1...@comcast.net wrote: I don't think so. Or if you are right then there are some big issues in the next few years that IBM's own products won't be able to support. As an example IBM semi announced that soon there will be dynamic storage(DASD) expansion and it will be done with volser (ex ABC001,ABC002 etc etc) ie adding volsers without having to update the ACS routines and DFDSS statements/ or DD JCL and this will apparently include DFHSM and any other product that needs Backup/restore generic volsers. DMS had this ability *LONG TIME AGO*. I don't see any issue about integrity with items like that (in fact our DASD boss when the MSS came in worked with the DMS people to support the concept of MVSGRP in DMS, IBM never did it. Ed On Oct 30, 2014, at 12:48 AM, Elardus Engelbrecht wrote: Ed Gould wrote: There are still quite a few items that DFDSS hasn't caught up with but thats a different horse to flog. Although I was reading an article about z/OS and there are a few things percolating up the like dynamic DASD and the like that will make us wonder why it took so long. Possible reasons: Backward compatibility issues? No business case to catch up? Integrity issues? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 30, 2014, at 5:33 PM, Mike Schwab wrote: We put unused volsers into SMS Storage groups then init actual volumes when more space is needed. --SNIP--- You still have to put them in your ACS routines and DFDSS won't allow patterning of volsers (AFAIK). ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Correct. We put in a range of volumes. Example LGA 001-099. We then initialize a few of the volumes, say LGA 001-009. When these volumes get to 90% full, and allocations fail, we init volume LGA 010. Once online it probably will be used for over half the allocations until it becomes fairly balanced. On Thu, Oct 30, 2014 at 6:26 PM, Ed Gould edgould1...@comcast.net wrote: On Oct 30, 2014, at 5:33 PM, Mike Schwab wrote: We put unused volsers into SMS Storage groups then init actual volumes when more space is needed. --SNIP--- You still have to put them in your ACS routines and DFDSS won't allow patterning of volsers (AFAIK). ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Esmie, You are posing an invalid situation for what you specified. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. If the dataset has not migrated, numerous possible conditions exist: 1) it was referenced and therefore not eligible for migration because of usage. 2) it has not been backed up and is not eligible for migration 3) the volume is not eligible for migration and/or backup 4) something else is afoot that we are not aware of (premature ending of space management windows, etc.) Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 7:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM QUESTION - EXPIRATION OF DSN Good Morning Gentle Readers, I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Bob, I understand that. Hoever, if the dsn is not migrated will it be deleted? Does the Expiration attributes take precdence over the Migration attributes/ On Wed, 10/29/14, Richards, Robert B. robert.richa...@opm.gov wrote: Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN To: IBM-MAIN@LISTSERV.UA.EDU Received: Wednesday, October 29, 2014, 7:53 AM Esmie, You are posing an invalid situation for what you specified. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. If the dataset has not migrated, numerous possible conditions exist: 1) it was referenced and therefore not eligible for migration because of usage. 2) it has not been backed up and is not eligible for migration 3) the volume is not eligible for migration and/or backup 4) something else is afoot that we are not aware of (premature ending of space management windows, etc.) Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 7:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM QUESTION - EXPIRATION OF DSN Good Morning Gentle Readers, I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
If the dsn is not migrated because migration is broken for that dataset *and* 540 days go by, then YES, it will expire if it has not been referenced. For 540 days. It is not a matter of precedence. An exception to all this is threshold mangement. If HSM doesn't think the volume meets criteria to qualify for PSM or SSM, then a dataset can sit on a primary volume forever. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 8:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN Bob, I understand that. Hoever, if the dsn is not migrated will it be deleted? Does the Expiration attributes take precdence over the Migration attributes/ On Wed, 10/29/14, Richards, Robert B. robert.richa...@opm.gov wrote: Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN To: IBM-MAIN@LISTSERV.UA.EDU Received: Wednesday, October 29, 2014, 7:53 AM Esmie, You are posing an invalid situation for what you specified. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. If the dataset has not migrated, numerous possible conditions exist: 1) it was referenced and therefore not eligible for migration because of usage. 2) it has not been backed up and is not eligible for migration 3) the volume is not eligible for migration and/or backup 4) something else is afoot that we are not aware of (premature ending of space management windows, etc.) Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 7:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM QUESTION - EXPIRATION OF DSN Good Morning Gentle Readers, I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Bob, Thanks very much for your help. On Wed, 10/29/14, Richards, Robert B. robert.richa...@opm.gov wrote: Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN To: IBM-MAIN@LISTSERV.UA.EDU Received: Wednesday, October 29, 2014, 8:50 AM If the dsn is not migrated because migration is broken for that dataset *and* 540 days go by, then YES, it will expire if it has not been referenced. For 540 days. It is not a matter of precedence. An exception to all this is threshold mangement. If HSM doesn't think the volume meets criteria to qualify for PSM or SSM, then a dataset can sit on a primary volume forever. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 8:24 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN Bob, I understand that. Hoever, if the dsn is not migrated will it be deleted? Does the Expiration attributes take precdence over the Migration attributes/ On Wed, 10/29/14, Richards, Robert B. robert.richa...@opm.gov wrote: Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN To: IBM-MAIN@LISTSERV.UA.EDU Received: Wednesday, October 29, 2014, 7:53 AM Esmie, You are posing an invalid situation for what you specified. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. If the dataset has not migrated, numerous possible conditions exist: 1) it was referenced and therefore not eligible for migration because of usage. 2) it has not been backed up and is not eligible for migration 3) the volume is not eligible for migration and/or backup 4) something else is afoot that we are not aware of (premature ending of space management windows, etc.) Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of esmie moo Sent: Wednesday, October 29, 2014 7:32 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM QUESTION - EXPIRATION OF DSN Good Morning Gentle Readers, I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Bob, We have a similar situation at our end. There is a dsn with the following atribute: Expire after Days Non-usage . : 365. Migration Attributes Primary Days Non-usage . : 2 Level 1 Days Date/Days . : 10 Command or Auto Migrate . : BOTH What if the DSN is empty and not backed (because HSM doesn't backup empty dsns) would the dsn be deleted after 365 days non-usage / non referenced? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
snip After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. /snip Minor correction: After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 days of non-usage, it will migrate to ML2. If not already migrated to ML1, it will migrate directly to ML2. After 540 days, it will expire. HTH, snip After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 more days of non-usage, it will migrate to ML2. After 540 days, it will expire. If the dataset has not migrated, numerous possible conditions exist: 1) it was referenced and therefore not eligible for migration because of usage. 2) it has not been backed up and is not eligible for migration 3) the volume is not eligible for migration and/or backup 4) something else is afoot that we are not aware of (premature ending of space management windows, etc.) Bob snipage I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Yes. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Willie Bunter Sent: Wednesday, October 29, 2014 9:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN Bob, We have a similar situation at our end. There is a dsn with the following atribute: Expire after Days Non-usage . : 365. Migration Attributes Primary Days Non-usage . : 2 Level 1 Days Date/Days . : 10 Command or Auto Migrate . : BOTH What if the DSN is empty and not backed (because HSM doesn't backup empty dsns) would the dsn be deleted after 365 days non-usage / non referenced? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
There is a bit that can be set. Check the dfHSM Implementation Guide for Disabling delete-if-backed-up (DBU) processing for SMS data Sets snip We have a similar situation at our end. There is a dsn with the following atribute: Expire after Days Non-usage . : 365. Migration Attributes Primary Days Non-usage . : 2 Level 1 Days Date/Days . : 10 Command or Auto Migrate . : BOTH What if the DSN is empty and not backed (because HSM doesn't backup empty dsns) would the dsn be deleted after 365 days non-usage / non referenced? /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Hmmm, will this thread ever *expires* ? :-D ;-D :-D Staller, Allan wrote: Minor correction: Thanks. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 days of non-usage, it will migrate to ML2. If not already migrated to ML1, it will migrate directly to ML2. After 540 days, it will expire. Just a little question if you don't mind, please: 'expire' - does it means it is deleted and uncataloged? What about its backup(s)? Will it stays (with later HBDEL) or not? Ok, I will migrate back to under my rock... Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Thank you Bob. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Expire means deleted and uncatalogued. Backups (if any) are handled as described in the MGMTCLAS for the dataset. This is an entirely different set of processing. snip Staller, Allan wrote: Minor correction: Thanks. After 4 days of non-usage, the dsn *will* migrate to ML1. After 7 days of non-usage, it will migrate to ML2. If not already migrated to ML1, it will migrate directly to ML2. After 540 days, it will expire. Just a little question if you don't mind, please: 'expire' - does it means it is deleted and uncataloged? What about its backup(s)? Will it stays (with later HBDEL) or not? Ok, I will migrate back to under my rock... Groete / Greetings Elardus Engelbrecht /snip -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Staller, Allan wrote: Expire means deleted and uncatalogued. Thanks. That will settle some burning issues with my storage admin who think it is RACF, but I could prove it is HSM. Backups (if any) are handled as described in the MGMTCLAS for the dataset. This is an entirely different set of processing. Yes, thanks for refreshing my memory. One of my DBAs found out too late there were no HSM backups for his *important* datasets. He could restore from an old DFDSS backup his old versions, rebuild the members and he is back in business. Who said this? He who has backup, laugh the last and loudest! Much appreciated! Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Thanks for the tip. This is very handy. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Willie Bunter Sent: Wednesday, October 29, 2014 6:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN Bob, We have a similar situation at our end. There is a dsn with the following atribute: Expire after Days Non-usage . : 365. Migration Attributes Primary Days Non-usage . : 2 Level 1 Days Date/Days . : 10 Command or Auto Migrate . : BOTH What if the DSN is empty and not backed (because HSM doesn't backup empty dsns) would the dsn be deleted after 365 days non-usage / non referenced? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. From the other hand such common issues gave me a lot of consultant work ;-) -- Radoslaw Skorupka Lodz, Poland --- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, October 29, 2014 2:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. A side effect of doing this is that you can also eliminate MODLDSCB's for Generation datasets. From the other hand such common issues gave me a lot of consultant work ;-) -- Radoslaw Skorupka Lodz, Poland --- Treść tej wiadomości może zawierać informacje prawnie chronione Banku przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o podobnym charakterze jest prawnie zabronione i może być karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku. This e-mail may contain legally privileged information of the Bank and is intended solely for business use of the addressee. This e-mail may only be received by the addressee and may not be disclosed to any third parties. If you are not the intended addressee of this e-mail or the employee authorized to forward it to the addressee, be advised that any dissemination, copying, distribution or any other similar activity is legally prohibited and may be punishable. If you received this e-mail by mistake please advise the sender immediately by using the reply facility in your e-mail software and delete permanently this e-mail including any copies of it either printed or saved to hard drive. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, www.mBank.pl, e-mail: kont...@mbank.pl Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców KRS 025237, NIP: 526- 021-50-88. Według stanu na dzień 01.01.2014 r. kapitał zakładowy mBanku S.A. (w całości wpłacony) wynosi 168.696.052 złote. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 29, 2014, at 4:39 PM, R.S. wrote: W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. R.S. Define invalid datasets, please. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Wednesday, October 29, 2014 4:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN On Oct 29, 2014, at 4:39 PM, R.S. wrote: W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. R.S. Define invalid datasets, please. From HSM's perspective, they lack a DSORG. Most frequently created by JCL where the program doesn't actually OPEN the output file for some reason. On non-SMS disk, they can also lack an EOF mark with older z/OS (or perhaps OS390) Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 29, 2014, at 6:14 PM, Gibney, Dave wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Wednesday, October 29, 2014 4:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN On Oct 29, 2014, at 4:39 PM, R.S. wrote: W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. R.S. Define invalid datasets, please. From HSM's perspective, they lack a DSORG. Most frequently created by JCL where the program doesn't actually OPEN the output file for some reason. On non-SMS disk, they can also lack an EOF mark with older z/OS (or perhaps OS390) From the comment it could have been a dataset that didn't have a local standard name. I had a standard (DASD) that if it didn't have a valid dsorg it was deleted. I regularly went through and deleted them. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Wednesday, October 29, 2014 4:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN On Oct 29, 2014, at 6:14 PM, Gibney, Dave wrote: -Original Message- From: IBM Mainframe Discussion List [mailto:IBM- m...@listserv.ua.edu] On Behalf Of Ed Gould Sent: Wednesday, October 29, 2014 4:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM QUESTION - EXPIRATION OF DSN On Oct 29, 2014, at 4:39 PM, R.S. wrote: W dniu 2014-10-29 o 18:47, Gibney, Dave pisze: HSM will happily back-up empty datasets. INVALID datasets are another matter. But, it is an easy matter to define a DEFAULT DATACLAS with DSORG=PS and never have another invalid dataset. True. However I would prefer to have some feature to avoid creation of invalid datasets. I saw a lot of invalid datasets and none of them was really need by the creator. R.S. Define invalid datasets, please. From HSM's perspective, they lack a DSORG. Most frequently created by JCL where the program doesn't actually OPEN the output file for some reason. On non-SMS disk, they can also lack an EOF mark with older z/OS (or perhaps OS390) From the comment it could have been a dataset that didn't have a local standard name. I had a standard (DASD) that if it didn't have a valid dsorg it was deleted. I regularly went through and deleted them. 25 years ago or more, so did I. With SMS, HSM and DSROG via a DEFAULT DATACLAS, I don't have to do this manual deletion of obvious errors. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Esmie, If I am you, I will do the following to find out for myself what the state of affairs are. I will create a dataset with Expiration Attributes Expire after Days Non-usage . : 10 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH And see what happens in the 10 days. There is nothing like the satisfaction of trying it and finding the answer yourself. Greetings James 2014-10-29 11:32 GMT+00:00 esmie moo esmie_...@yahoo.ca: Good Morning Gentle Readers, I have a question about the expiration of a dsn by HSM. The rule says the following : Expiration Attributes Expire after Days Non-usage . : 540 Expire after Date/Days . . . . : NOLIMIT Retention Limit . . . . . . . : 0 However the Migration attributes are as follows: Migration Attributes Primary Days Non-usage . : 4 Level 1 Days Date/Days . : 7 Command or Auto Migrate . : BOTH My question is will HSM delete the dsn if it is NOT migrated? I think that the DSN needs to be migrated in order for HSM to delte the dsn. Could anybody confirm my comprehension or mis-comprehension should it be the case? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
On Oct 29, 2014, at 6:44 PM, Gibney, Dave wrote: -- SNIP- - From the comment it could have been a dataset that didn't have a local standard name. I had a standard (DASD) that if it didn't have a valid dsorg it was deleted. I regularly went through and deleted them. 25 years ago or more, so did I. With SMS, HSM and DSROG via a DEFAULT DATACLAS, I don't have to do this manual deletion of obvious errors. Ahhh the luxury of SMS I could have done so as well, BTW it was not a manual effort but a production job that ran once a day (DMS) and it was fully automatic. I disliked DMS for a lot of reasons but it did have a lot of features that it took DFDSS 25+ years to catch up up with There are still quite a few items that DFDSS hasn't caught up with but thats a different horse to flog . Although I was reading an article about Z/ os and there are a few things percolating up the like dynamic DASD and the like that will make us wonder why it took so long. Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM QUESTION - EXPIRATION OF DSN
Ed Gould wrote: There are still quite a few items that DFDSS hasn't caught up with but thats a different horse to flog. Although I was reading an article about z/OS and there are a few things percolating up the like dynamic DASD and the like that will make us wonder why it took so long. Possible reasons: Backward compatibility issues? No business case to catch up? Integrity issues? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
