Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
There is a backup done for this storage group. I regret my error. On Thu, 1/14/16, Gibney, David Allen,Jr wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, January 14, 2016, 3:18 PM Also, what are the actual dataset attributes? DFHSM doesn't do some "incomplete" datasets. Are they backed up. DFHSM often doesn't delete if there is not a back-up. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of willie bunter > Sent: Thursday, January 14, 2016 9:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in particular there is no migration it is to be > expired/deleted after 1 day of non-usage. > > You have touched on the point of space management algorithms for > migration. I assume that this would also pertain to the deletion of files as > well. Right? > > ---- > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 12:45 PM > > So depending on the > version of z/OS - look at On Demand Migration (v2.1 and above), this might > help more > > Second, correct, files are only moved if DFHSM feels the volume needs to > have the space back, however, you could have a migration policy in the > management class that says - if this is still on DASD after 1 month, then > migrate the file. > > It depends on > what your requirements are. You can just let files migrate as HSM sees fit > based on its algorithms for space management, or you can setup a > management class that says it gets migrated if unused in XX days. > > Many choices. > > Lizette > > > > -Original Message- > > From: IBM > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: > IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE > MANAGEMENT > > Good Day To All, > > I need to confirm if I my > understanding about SMS & SPACE management is > correct. > > We have noticed that there are several dsns which have been on dasd for > over > > 10 months. The volumes and dsns are all SMS managed and DFHSM > performs the > necessary migration and deletion. I checked the > MANAGEMENT class and the dsns > are to be deleted after 1 day non-usage > > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . . . : 1 > > Retention Limit . . . . . . . : > 0 > > > > Below are the > attributes of the Storage Group: > > > > > > Allocation/migration > Threshold : High > 85 (1-100) Low . . 1 > > > (0-99) > > Alloc/Migr Threshold > Track-Managed: High 85 (1-100) Low . . 1 (0- > 99) > Guaranteed > Backup Frequency . . . . . > . (1 to or > > NOLIMIT) > > > BreakPointValue . . . . . . . . . . . . > (0-65520 > > or blank) > > Processing > Priority . . . . . . . . . . 50 > (1-100) > > > > I think that the dsns are not deleted because SMS did not select some of > these > volumes have not met the criteria of the Low threshold of 1. I > remember > reading somewhere (on this board the following): > > > > For primary space > management, HSM only looks at the low threshold. If the > volume exceeds > the low threshold, then we will process any data sets that are > eligible for > migration on that volume. > > > > > Could someone confirm if I am > correct? > > > > > 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/SMS QUESTION - SPACE MANAGEMENT
I stand corrected. There is a backup done for this storage group. On Fri, 1/15/16, Gonzalo Cengotita wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, January 15, 2016, 3:31 AM Hi If the those file's Management class has the "Auto backup" set to YES but the storage Group has the "Auto Backup" set to NO you will find an error in your HSM log saying the dataset cannot be removed because is in need of a backup. Those messages are in the HSM MIGLOG in the records headed ACTION=EXPIRED or SPCMGMT, (RC=53). Regards, Gonzalo Cengotita *Gonzalo Cengotita* 2016-01-14 21:18 GMT+01:00 Gibney, David Allen,Jr : > Also, what are the actual dataset attributes? DFHSM doesn't do some > "incomplete" datasets. Are they backed up. DFHSM often doesn't delete if > there is not a back-up. > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of willie bunter > > Sent: Thursday, January 14, 2016 9:53 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > > Lizette, > > > > Thanks for the info. For this dsn in particular there is no migration > it is to be > > expired/deleted after 1 day of non-usage. > > > > You have touched on the point of space management algorithms for > > migration. I assume that this would also pertain to the deletion of > files as > > well. Right? > > > > > > On Thu, 1/14/16, Lizette Koehler wrote: > > > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > To: IBM-MAIN@LISTSERV.UA.EDU > > Received: Thursday, January 14, 2016, 12:45 PM > > > > So depending on the > > version of z/OS - look at On Demand Migration (v2.1 and above), this > might > > help more > > > > Second, correct, files are only moved if DFHSM feels the volume needs > to > > have the space back, however, you could have a migration policy in the > > management class that says - if this is still on DASD after 1 month, > then > > migrate the file. > > > > It depends on > > what your requirements are. You can just let files migrate as HSM > sees fit > > based on its algorithms for space management, or you can setup a > > management class that says it gets migrated if unused in XX days. > > > > Many choices. > > > > Lizette > > > > > > > -Original Message- > > > From: IBM > > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > > To: > > IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE > > MANAGEMENT > > Good Day To All, > > I need to confirm if I my > > understanding about SMS & SPACE management is > correct. > > > We have noticed that there are several dsns which have been on dasd > for > > over > > > 10 months. The volumes and dsns are all SMS managed and DFHSM > > performs the > necessary migration and deletion. I checked the > > MANAGEMENT class and the dsns > are to be deleted after 1 day > non-usage > > > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . > . . : 1 > > > Retention Limit . . . . . . . : > > 0 > > > > > > Below are the > > attributes of the Storage Group: > > > > > > > > > Allocation/migration > > Threshold : High > > 85 (1-100) Low . . 1 > > > > > (0-99) > > > Alloc/Migr Threshold > > Track-Managed: High 85 (1-100) Low . . 1 (0- > 99) > > Guaranteed > > Backup Frequency . . . . . > > . (1 to or > > > NOLIMIT) > > > > > BreakPointValue . . . . . . . . . . . . > > (0-65520 > > > or blank) > > > Processing > > Priority . . . . . . . . . . 50 > > (1-100) > > > > > > I think that the dsns are not deleted because SMS did not select > some of > > these > volumes have not met the criteria of the Low threshold of 1. I > > remember > reading somewhere (on this board the followin
Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
This storage group is selected for space management. Thanks for the tip about the patch. I will try that out. On Fri, 1/15/16, Glenn Wilcock wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, January 15, 2016, 10:31 AM Hi, a couple of other things to look at: (1) Verify that the volume is being selected for space management. As indicated, HSM doesn't process data sets on a volume unless the volume exceeds its high threshold. Once a volume is selected, HSM will process all eligible data sets on that volume until the low threshold is reached. (2) Enable PATCH .MGCB.+26 X’FF’, which indicates that HSM should issue additional ARC0734I messages to indicate why data sets weren't selected for processing. (This patch is documented in the DFSMShsm Diagnosis manual). Glenn Wilcock DFSMShsm Architect -- 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/SMS QUESTION - SPACE MANAGEMENT
There is no HSM backup taken for this storage group. On Fri, 1/15/16, Gibney, David Allen,Jr wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Friday, January 15, 2016, 8:06 PM What about back up? > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of willie bunter > Sent: Friday, January 15, 2016 4:07 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Migrate the dsn after 10 days of non-usage. > > > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 1:52 PM > > What does your management > class for this dataset say as well as the HSM policy? > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > > Behalf Of willie bunter > > Sent: Thursday, January 14, 2016 10:53 AM > To: IBM- > m...@listserv.ua.edu > Subject: Re: DFHSM/SMS QUESTION - SPACE > MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in > particular there is no migration it is > to be expired/deleted after 1 day of > non-usage. > > > > You have touched on the point of space management algorithms for > migration. I > assume that this would also pertain to the deletion of files as > well. Right? > > > > > ---- > > On Thu, 1/14/16, Lizette Koehler > wrote: > > > > Subject: > Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM- > m...@listserv.ua.edu > Received: Thursday, January 14, 2016, > 12:45 PM > > > > So > depending on the > > version of z/OS - > look at On Demand Migration (v2.1 and above), this might > help more > > > > Second, correct, files are only > moved if DFHSM feels the volume needs to > have the space back, however, > you could have a migration policy in the > management class that says - if > this is still on DASD after 1 month, then > migrate the file. > > > > It > depends on > > what your requirements > are. You can just let files migrate as HSM sees fit > based on its algorithms > for space management, or you can setup a management > class that says > it gets migrated if unused in XX days. > > > > Many choices. > > > > Lizette > > > > > > > > -Original Message- > > > From: > IBM > > Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > Behalf Of > > willie bunter > > Sent: Thursday, January 14, 2016 10:23 AM > To: > IBM- > > m...@listserv.ua.edu > > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > Good Day > To All, > > I need to confirm if I my understanding about SMS & > > SPACE management is > correct. > > > We have noticed that > there are several dsns which have been on dasd for > over > > 10 > months. The volumes and dsns are all SMS managed and DFHSM performs > the > > necessary migration and deletion. I checked the MANAGEMENT > class and the > dsns > are to be deleted after 1 day non-usage > > > Expire after Days > Non- > > usage . : 1 > Expire > after Date/Days . . . . : 1 > Retention > Limit . . . . . . . > : > > 0 > > > > > > Below > are the > > attributes of the Storage > Group: > > > > > > > > > > Allocation/migration > > Threshold : High > > 85 (1-100) Low . . 1 > > > > > (0-99) > > > Alloc/Migr Threshold > > Track-Managed: High > 85 (1-100) Low . . 1 (0- > > 99) > Guaranteed > > Backup > Frequency . . . . . > > . > (1 to or > > > > NOLIMIT) > > > > > > BreakPointValue . . . . . . . . . . . . > > > (0-65520 > > > or > blank) > > > Processing > > Priority . . . . . . . . . . 50 > > (1-100) > > > > > > I think
Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
What about back up? > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of willie bunter > Sent: Friday, January 15, 2016 4:07 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Migrate the dsn after 10 days of non-usage. > > > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 1:52 PM > > What does your management > class for this dataset say as well as the HSM policy? > > Lizette > > > > -Original Message- > > From: IBM Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > > Behalf Of willie bunter > > Sent: Thursday, January 14, 2016 10:53 AM > To: IBM- > m...@listserv.ua.edu > Subject: Re: DFHSM/SMS QUESTION - SPACE > MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in > particular there is no migration it is > to be expired/deleted after 1 day > of > non-usage. > > > > You have touched on the point of space management algorithms for > migration. I > assume that this would also pertain to the deletion of > files as > well. Right? > > > > > > > On Thu, 1/14/16, Lizette Koehler > wrote: > > > > Subject: > Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM- > m...@listserv.ua.edu > Received: Thursday, January 14, 2016, > 12:45 PM > > > > So > depending on the > > version of z/OS - > look at On Demand Migration (v2.1 and above), this might > help more > > > > Second, correct, files are only > moved if DFHSM feels the volume needs to > have the space back, however, > you could have a migration policy in the > management class that says - > if > this is still on DASD after 1 month, then > migrate the file. > > > > It > depends on > > what your requirements > are. You can just let files migrate as HSM sees fit > based on its > algorithms > for space management, or you can setup a management > class that says > it gets migrated if unused in XX days. > > > > Many choices. > > > > Lizette > > > > > > > > -Original Message- > > > From: > IBM > > Mainframe Discussion List > [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On > Behalf Of > > willie bunter > > Sent: Thursday, January 14, 2016 10:23 AM > To: > IBM- > > m...@listserv.ua.edu > > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > Good Day > To All, > > I need to confirm if I my understanding about SMS & > > SPACE management is > correct. > > > We have noticed that > there are several dsns which have been on dasd for > over > > 10 > months. The volumes and dsns are all SMS managed and DFHSM performs > the > > necessary migration and deletion. I checked the MANAGEMENT > class and the > dsns > are to be deleted after 1 day non-usage > > > Expire after Days > Non- > > usage . : 1 > Expire > after Date/Days . . . . : 1 > Retention > Limit . . . . . . . > : > > 0 > > > > > > Below > are the > > attributes of the Storage > Group: > > > > > > > > > > Allocation/migration > > Threshold : High > > 85 (1-100) Low . . 1 > > > > > (0-99) > > > Alloc/Migr Threshold > > Track-Managed: High > 85 (1-100) Low . . 1 (0- > > 99) > Guaranteed > > Backup > Frequency . . . . . > > . > (1 to or > > > > NOLIMIT) > > > > > > BreakPointValue . . . . . . . . . . . . > > > (0-65520 > > > or > blank) > > > Processing > > Priority . . . . . . . . . . 50 > > (1-100) > > > > > > I think > that the dsns are not deleted because SMS did not select some of > these > > > volumes have not met the criteria of the Low threshold of 1. I > > remember > reading somewhere (on this board the following): > > > > > > For primary space > > management, HSM only looks at the low threshold. If the > volume > exceeds the > low threshold, then we will process any data sets that > are > eligible for > migration on that volume. > > > > > > > > Could someone confirm if I am > > correct? > > > > > > > > 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/SMS QUESTION - SPACE MANAGEMENT
Migrate the dsn after 10 days of non-usage. On Thu, 1/14/16, Lizette Koehler wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, January 14, 2016, 1:52 PM What does your management class for this dataset say as well as the HSM policy? Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in particular there is no migration it is > to be expired/deleted after 1 day of non-usage. > > You have touched on the point of space management algorithms for migration. I > assume that this would also pertain to the deletion of files as well. Right? > > > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 12:45 PM > > So depending on the > version of z/OS - look at On Demand Migration (v2.1 and above), this might > help more > > Second, correct, files are only moved if DFHSM feels the volume needs to > have the space back, however, you could have a migration policy in the > management class that says - if this is still on DASD after 1 month, then > migrate the file. > > It depends on > what your requirements are. You can just let files migrate as HSM sees fit > based on its algorithms for space management, or you can setup a management > class that says it gets migrated if unused in XX days. > > Many choices. > > Lizette > > > > -Original Message- > > From: IBM > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of > willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: IBM- > m...@listserv.ua.edu > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > Good Day To All, > > I need to confirm if I my understanding about SMS & > SPACE management is > correct. > > We have noticed that there are several dsns which have been on dasd for > over > > 10 months. The volumes and dsns are all SMS managed and DFHSM performs the > > necessary migration and deletion. I checked the MANAGEMENT class and the > dsns > are to be deleted after 1 day non-usage > > Expire after Days Non- > usage . : 1 > Expire after Date/Days . . . . : 1 > Retention > Limit . . . . . . . : > 0 > > > > Below are the > attributes of the Storage Group: > > > > > > Allocation/migration > Threshold : High > 85 (1-100) Low . . 1 > > > (0-99) > > Alloc/Migr Threshold > Track-Managed: High 85 (1-100) Low . . 1 (0- > 99) > Guaranteed > Backup Frequency . . . . . > . (1 to or > > NOLIMIT) > > > BreakPointValue . . . . . . . . . . . . > (0-65520 > > or blank) > > Processing > Priority . . . . . . . . . . 50 > (1-100) > > > > I think that the dsns are not deleted because SMS did not select some of > these > volumes have not met the criteria of the Low threshold of 1. I > remember > reading somewhere (on this board the following): > > > > For primary space > management, HSM only looks at the low threshold. If the > volume exceeds the > low threshold, then we will process any data sets that are > eligible for > migration on that volume. > > > > > Could someone confirm if I am > correct? > > > > > 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/SMS QUESTION - SPACE MANAGEMENT
Hi, a couple of other things to look at: (1) Verify that the volume is being selected for space management. As indicated, HSM doesn't process data sets on a volume unless the volume exceeds its high threshold. Once a volume is selected, HSM will process all eligible data sets on that volume until the low threshold is reached. (2) Enable PATCH .MGCB.+26 X’FF’, which indicates that HSM should issue additional ARC0734I messages to indicate why data sets weren't selected for processing. (This patch is documented in the DFSMShsm Diagnosis manual). Glenn Wilcock DFSMShsm Architect -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
Hi If the those file's Management class has the "Auto backup" set to YES but the storage Group has the "Auto Backup" set to NO you will find an error in your HSM log saying the dataset cannot be removed because is in need of a backup. Those messages are in the HSM MIGLOG in the records headed ACTION=EXPIRED or SPCMGMT, (RC=53). Regards, Gonzalo Cengotita *Gonzalo Cengotita* 2016-01-14 21:18 GMT+01:00 Gibney, David Allen,Jr : > Also, what are the actual dataset attributes? DFHSM doesn't do some > "incomplete" datasets. Are they backed up. DFHSM often doesn't delete if > there is not a back-up. > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of willie bunter > > Sent: Thursday, January 14, 2016 9:53 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > > Lizette, > > > > Thanks for the info. For this dsn in particular there is no migration > it is to be > > expired/deleted after 1 day of non-usage. > > > > You have touched on the point of space management algorithms for > > migration. I assume that this would also pertain to the deletion of > files as > > well. Right? > > > > > > On Thu, 1/14/16, Lizette Koehler wrote: > > > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > To: IBM-MAIN@LISTSERV.UA.EDU > > Received: Thursday, January 14, 2016, 12:45 PM > > > > So depending on the > > version of z/OS - look at On Demand Migration (v2.1 and above), this > might > > help more > > > > Second, correct, files are only moved if DFHSM feels the volume needs > to > > have the space back, however, you could have a migration policy in the > > management class that says - if this is still on DASD after 1 month, > then > > migrate the file. > > > > It depends on > > what your requirements are. You can just let files migrate as HSM > sees fit > > based on its algorithms for space management, or you can setup a > > management class that says it gets migrated if unused in XX days. > > > > Many choices. > > > > Lizette > > > > > > > -Original Message- > > > From: IBM > > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > > To: > > IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE > > MANAGEMENT > > Good Day To All, > > I need to confirm if I my > > understanding about SMS & SPACE management is > correct. > > > We have noticed that there are several dsns which have been on dasd > for > > over > > > 10 months. The volumes and dsns are all SMS managed and DFHSM > > performs the > necessary migration and deletion. I checked the > > MANAGEMENT class and the dsns > are to be deleted after 1 day > non-usage > > > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . > . . : 1 > > > Retention Limit . . . . . . . : > > 0 > > > > > > Below are the > > attributes of the Storage Group: > > > > > > > > > Allocation/migration > > Threshold :High > > 85 (1-100) Low . . 1 > > > > > (0-99) > > > Alloc/Migr Threshold > > Track-Managed: High85 (1-100)Low . . 1 (0- > 99) > > Guaranteed > > Backup Frequency . . . . . > > . (1 to or > > > NOLIMIT) > > > > > BreakPointValue . . . . . . . . . . . . > > (0-65520 > > > or blank) > > > Processing > > Priority . . . . . . . . . . 50 > > (1-100) > > > > > > I think that the dsns are not deleted because SMS did not select > some of > > these > volumes have not met the criteria of the Low threshold of 1. I > > remember > reading somewhere (on this board the following): > > > > > > For primary space > > management, HSM only looks at the low threshold. If the > volume > exceeds > > the low threshold, then we will process any data sets that are > > eligible for > > migration on that volume. > > > > > > > > Could someone confirm if I am > > correct? > > > > > > > > Thanks. > > > >
Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
Also, what are the actual dataset attributes? DFHSM doesn't do some "incomplete" datasets. Are they backed up. DFHSM often doesn't delete if there is not a back-up. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of willie bunter > Sent: Thursday, January 14, 2016 9:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in particular there is no migration it is > to be > expired/deleted after 1 day of non-usage. > > You have touched on the point of space management algorithms for > migration. I assume that this would also pertain to the deletion of files as > well. Right? > > -------- > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 12:45 PM > > So depending on the > version of z/OS - look at On Demand Migration (v2.1 and above), this might > help more > > Second, correct, files are only moved if DFHSM feels the volume needs to > have the space back, however, you could have a migration policy in the > management class that says - if this is still on DASD after 1 month, then > migrate the file. > > It depends on > what your requirements are. You can just let files migrate as HSM sees fit > based on its algorithms for space management, or you can setup a > management class that says it gets migrated if unused in XX days. > > Many choices. > > Lizette > > > > -Original Message- > > From: IBM > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: > IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE > MANAGEMENT > > Good Day To All, > > I need to confirm if I my > understanding about SMS & SPACE management is > correct. > > We have noticed that there are several dsns which have been on dasd for > over > > 10 months. The volumes and dsns are all SMS managed and DFHSM > performs the > necessary migration and deletion. I checked the > MANAGEMENT class and the dsns > are to be deleted after 1 day non-usage > > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . . . > > : 1 > > Retention Limit . . . . . . . : > 0 > > > > Below are the > attributes of the Storage Group: > > > > > > Allocation/migration > Threshold : High > 85 (1-100) Low . . 1 > > > (0-99) > > Alloc/Migr Threshold > Track-Managed: High 85 (1-100) Low . . 1 (0- > 99) > Guaranteed > Backup Frequency . . . . . > . (1 to or > > NOLIMIT) > > > BreakPointValue . . . . . . . . . . . . > (0-65520 > > or blank) > > Processing > Priority . . . . . . . . . . 50 > (1-100) > > > > I think that the dsns are not deleted because SMS did not select some of > these > volumes have not met the criteria of the Low threshold of 1. I > remember > reading somewhere (on this board the following): > > > > For primary space > management, HSM only looks at the low threshold. If the > volume exceeds > the low threshold, then we will process any data sets that are > eligible > for > migration on that volume. > > > > > Could someone confirm if I am > correct? > > > > > 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/SMS QUESTION - SPACE MANAGEMENT
What does your management class for this dataset say as well as the HSM policy? Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:53 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Lizette, > > Thanks for the info. For this dsn in particular there is no migration it is > to be expired/deleted after 1 day of non-usage. > > You have touched on the point of space management algorithms for migration. I > assume that this would also pertain to the deletion of files as well. Right? > > > On Thu, 1/14/16, Lizette Koehler wrote: > > Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT > To: IBM-MAIN@LISTSERV.UA.EDU > Received: Thursday, January 14, 2016, 12:45 PM > > So depending on the > version of z/OS - look at On Demand Migration (v2.1 and above), this might > help more > > Second, correct, files are only moved if DFHSM feels the volume needs to > have the space back, however, you could have a migration policy in the > management class that says - if this is still on DASD after 1 month, then > migrate the file. > > It depends on > what your requirements are. You can just let files migrate as HSM sees fit > based on its algorithms for space management, or you can setup a management > class that says it gets migrated if unused in XX days. > > Many choices. > > Lizette > > > > -Original Message- > > From: IBM > Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of > willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: IBM- > m...@listserv.ua.edu > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > > Good Day To All, > > I need to confirm if I my understanding about SMS & > SPACE management is > correct. > > We have noticed that there are several dsns which have been on dasd for > over > > 10 months. The volumes and dsns are all SMS managed and DFHSM performs the > > necessary migration and deletion. I checked the MANAGEMENT class and the > dsns > are to be deleted after 1 day non-usage > > Expire after Days Non- > usage . : 1 > Expire after Date/Days . . . . : 1 > Retention > Limit . . . . . . . : > 0 > > > > Below are the > attributes of the Storage Group: > > > > > > Allocation/migration > Threshold :High > 85 (1-100) Low . . 1 > > > (0-99) > > Alloc/Migr Threshold > Track-Managed: High85 (1-100)Low . . 1 (0- > 99) > Guaranteed > Backup Frequency . . . . . > . (1 to or > > NOLIMIT) > > > BreakPointValue . . . . . . . . . . . . > (0-65520 > > or blank) > > Processing > Priority . . . . . . . . . . 50 > (1-100) > > > > I think that the dsns are not deleted because SMS did not select some of > these > volumes have not met the criteria of the Low threshold of 1. I > remember > reading somewhere (on this board the following): > > > > For primary space > management, HSM only looks at the low threshold. If the > volume exceeds the > low threshold, then we will process any data sets that are > eligible for > migration on that volume. > > > > > Could someone confirm if I am > correct? > > > > > Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT
Lizette, Thanks for the info. For this dsn in particular there is no migration it is to be expired/deleted after 1 day of non-usage. You have touched on the point of space management algorithms for migration. I assume that this would also pertain to the deletion of files as well. Right? On Thu, 1/14/16, Lizette Koehler wrote: Subject: Re: DFHSM/SMS QUESTION - SPACE MANAGEMENT To: IBM-MAIN@LISTSERV.UA.EDU Received: Thursday, January 14, 2016, 12:45 PM So depending on the version of z/OS - look at On Demand Migration (v2.1 and above), this might help more Second, correct, files are only moved if DFHSM feels the volume needs to have the space back, however, you could have a migration policy in the management class that says - if this is still on DASD after 1 month, then migrate the file. It depends on what your requirements are. You can just let files migrate as HSM sees fit based on its algorithms for space management, or you can setup a management class that says it gets migrated if unused in XX days. Many choices. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Good Day To All, > > I need to confirm if I my understanding about SMS & SPACE management is > correct. > We have noticed that there are several dsns which have been on dasd for over > 10 months. The volumes and dsns are all SMS managed and DFHSM performs the > necessary migration and deletion. I checked the MANAGEMENT class and the dsns > are to be deleted after 1 day non-usage > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . . . : 1 > Retention Limit . . . . . . . : 0 > > Below are the attributes of the Storage Group: > > > Allocation/migration Threshold : High 85 (1-100) Low . . 1 > (0-99) > Alloc/Migr Threshold Track-Managed: High 85 (1-100) Low . . 1 (0- > 99) > Guaranteed Backup Frequency . . . . . . (1 to or > NOLIMIT) > BreakPointValue . . . . . . . . . . . . (0-65520 > or blank) > Processing Priority . . . . . . . . . . 50 (1-100) > > I think that the dsns are not deleted because SMS did not select some of these > volumes have not met the criteria of the Low threshold of 1. I remember > reading somewhere (on this board the following): > > For primary space management, HSM only looks at the low threshold. If the > volume exceeds the low threshold, then we will process any data sets that are > eligible for migration on that volume. > > Could someone confirm if I am correct? > > 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/SMS QUESTION - SPACE MANAGEMENT
So depending on the version of z/OS - look at On Demand Migration (v2.1 and above), this might help more Second, correct, files are only moved if DFHSM feels the volume needs to have the space back, however, you could have a migration policy in the management class that says - if this is still on DASD after 1 month, then migrate the file. It depends on what your requirements are. You can just let files migrate as HSM sees fit based on its algorithms for space management, or you can setup a management class that says it gets migrated if unused in XX days. Many choices. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of willie bunter > Sent: Thursday, January 14, 2016 10:23 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM/SMS QUESTION - SPACE MANAGEMENT > > Good Day To All, > > I need to confirm if I my understanding about SMS & SPACE management is > correct. > We have noticed that there are several dsns which have been on dasd for over > 10 months. The volumes and dsns are all SMS managed and DFHSM performs the > necessary migration and deletion. I checked the MANAGEMENT class and the dsns > are to be deleted after 1 day non-usage > > Expire after Days Non-usage . : 1 > Expire after Date/Days . . . . : 1 > Retention Limit . . . . . . . : 0 > > Below are the attributes of the Storage Group: > > > Allocation/migration Threshold :High85 (1-100) Low . . 1 > (0-99) > Alloc/Migr Threshold Track-Managed: High85 (1-100)Low . . 1 (0- > 99) > Guaranteed Backup Frequency . . . . . . (1 to or > NOLIMIT) > BreakPointValue . . . . . . . . . . . . (0-65520 > or blank) > Processing Priority . . . . . . . . . . 50 (1-100) > > I think that the dsns are not deleted because SMS did not select some of these > volumes have not met the criteria of the Low threshold of 1. I remember > reading somewhere (on this board the following): > > For primary space management, HSM only looks at the low threshold. If the > volume exceeds the low threshold, then we will process any data sets that are > eligible for migration on that volume. > > Could someone confirm if I am correct? > > Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
DFHSM/SMS QUESTION - SPACE MANAGEMENT
Good Day To All, I need to confirm if I my understanding about SMS & SPACE management is correct. We have noticed that there are several dsns which have been on dasd for over 10 months. The volumes and dsns are all SMS managed and DFHSM performs the necessary migration and deletion. I checked the MANAGEMENT class and the dsns are to be deleted after 1 day non-usage Expire after Days Non-usage . : 1 Expire after Date/Days . . . . : 1 Retention Limit . . . . . . . : 0 Below are the attributes of the Storage Group: Allocation/migration Threshold :High85 (1-100) Low . . 1 (0-99) Alloc/Migr Threshold Track-Managed: High85 (1-100)Low . . 1 (0-99) Guaranteed Backup Frequency . . . . . . (1 to or NOLIMIT) BreakPointValue . . . . . . . . . . . . (0-65520 or blank) Processing Priority . . . . . . . . . . 50 (1-100) I think that the dsns are not deleted because SMS did not select some of these volumes have not met the criteria of the Low threshold of 1. I remember reading somewhere (on this board the following): For primary space management, HSM only looks at the low threshold. If the volume exceeds the low threshold, then we will process any data sets that are eligible for migration on that volume. Could someone confirm if I am correct? Thanks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
