Re: DFHSM Migration of SYS1 datasets ?
Dave, We have been working on the rewording the SETMIG command as there is some confusion in the hierarchical order or the SETMIG commands, I will see if we can update that with the fact if you want to change SYS1. data sets you have to specify the period. Max Smith DFSMShsm Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM Migration of SYS1 datasets ?
Thank you. I don't think it would have occurred to me to try it with the period. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Max Smith > Sent: Wednesday, March 28, 2018 2:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > Hi Dave, > > I was able to get this to work by specifying SETMIG LEVEL(SYS1.) > COMMANDMIGRATION. It requires the period to distinguish it from data sets > starting with SYS1 eg SYS1SSS > > Also tried SETMIG LEVEL(SYS1.TEST) COMMANDMIGRATION and it failed. That > is because the LEVEL(SYS1.) NOMIGRATION is specified first and will override > what the second one specifies. > > Also the subparameter COMMANDMIGRATION is only valid on the LEVEL > parameter. > > Also the only way I can see you can remove a SETMIG command would be to > STOP and RESTART HSM. > > The QUERY RETAIN command will show you what you have specified. > > Max Smith > DFSMShsm Development > > -- > 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 Migration of SYS1 datasets ?
Hi Dave, I was able to get this to work by specifying SETMIG LEVEL(SYS1.) COMMANDMIGRATION. It requires the period to distinguish it from data sets starting with SYS1 eg SYS1SSS Also tried SETMIG LEVEL(SYS1.TEST) COMMANDMIGRATION and it failed. That is because the LEVEL(SYS1.) NOMIGRATION is specified first and will override what the second one specifies. Also the subparameter COMMANDMIGRATION is only valid on the LEVEL parameter. Also the only way I can see you can remove a SETMIG command would be to STOP and RESTART HSM. The QUERY RETAIN command will show you what you have specified. Max Smith DFSMShsm Development -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM Migration of SYS1 datasets ?
Have you tried the rename-dataset-and-establish-alias I suggested? Maybe you don't have the necessary access authority to the dataset / master catalogue. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave Sent: Wednesday, 28 March 2018 9:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM Migration of SYS1 datasets ? So, why doesn't it work for me? It's not a big enough issue for me to try and open a PMR, especially since I probably need to route that through our MFaaS provider now! > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Anthony Thompson > Sent: Tuesday, March 27, 2018 5:21 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > Quite right Bart. > > HSM V2.3 Impl & Cust Ch 4 (User Datasets) has Table 4 listing dataset > type support for space management functions. One of the entries in > that table says datasets starting with SYS1 or HSM won't get > command-migrated, but notes that the restriction can be over-ridden by SETMIG > LEVEL(). Page 62. > > Same page number in the 2.1 version of the manual. > > Ant. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of van der Grijn, Bart (B) > Sent: Wednesday, 28 March 2018 4:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > I've never used the option, but the way I read the manual (z/OS 2.3), > it specifically requires the LEVEL parameter. I assume that means you > need to do a SETMIG for LEVEL(SYS1) rather than at the DATASETNAME level. > I haven't tested this, it's just how I interpret the manual. > FWIW, > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, March 27, 2018 4:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > This email originated from outside of the organization. > > > And the SETMIG command's apparent explicit purpose as documented to > allow removing/reinstating this restriction by LEVEL or DATASETNAME. > > > -Original Message- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Anthony Thompson > > Sent: Monday, March 26, 2018 8:48 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM Migration of SYS1 datasets ? > > > > ARC1245I Reason Code 1: > > > > The data set is a system data set, a VSAM catalog, or an integrated > > catalog facility (ICF) catalog. Either the first four characters of > > the data set name are HSM, or the first five characters of the data > > set name are SYS1, or the data set name is SYSCTLG. > > > > > > HSM does not process SYS1 datasets. > > > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the > > dataset is generally not required by any of your started tasks or > > other > processes. > > > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB > > alias for > it. > > Of course, the new datasetname would need to be catalogued in the > > master catalogue too. > > > > Ant. > > > > -Original Message- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave > > Sent: Tuesday, 27 March 2018 11:19 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: DFHSM Migration of SYS1 datasets ? > > > > I am at z/OS 2.1. I understand the need to make this hard, but what > > am I missing. > > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION > ARC0170I > > SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET > NOT > > ELIGIBLE FOR MIGRATION > > > > The documentation indicates that the SETMIG command should allow me > > to request DFHSM perform this migration. I've tried several > > varations using SETMIG LEVEL also. The volume where this dataset > > resides is Non- > SMS. > > > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > > > Does this function just not work? Or have missed something obvious. > > > > Dave Gibney > > Information Technology Services > > Washington State University > > > >
Re: DFHSM Migration of SYS1 datasets ?
So, why doesn't it work for me? It's not a big enough issue for me to try and open a PMR, especially since I probably need to route that through our MFaaS provider now! > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Anthony Thompson > Sent: Tuesday, March 27, 2018 5:21 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > Quite right Bart. > > HSM V2.3 Impl & Cust Ch 4 (User Datasets) has Table 4 listing dataset type > support for space management functions. One of the entries in that table > says datasets starting with SYS1 or HSM won't get command-migrated, but > notes that the restriction can be over-ridden by SETMIG LEVEL(). Page 62. > > Same page number in the 2.1 version of the manual. > > Ant. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of van der Grijn, Bart (B) > Sent: Wednesday, 28 March 2018 4:11 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > I've never used the option, but the way I read the manual (z/OS 2.3), it > specifically requires the LEVEL parameter. I assume that means you need to > do a SETMIG for LEVEL(SYS1) rather than at the DATASETNAME level. > I haven't tested this, it's just how I interpret the manual. > FWIW, > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, March 27, 2018 4:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > This email originated from outside of the organization. > > > And the SETMIG command's apparent explicit purpose as documented to > allow removing/reinstating this restriction by LEVEL or DATASETNAME. > > > -Original Message- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Anthony Thompson > > Sent: Monday, March 26, 2018 8:48 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM Migration of SYS1 datasets ? > > > > ARC1245I Reason Code 1: > > > > The data set is a system data set, a VSAM catalog, or an integrated > > catalog facility (ICF) catalog. Either the first four characters of > > the data set name are HSM, or the first five characters of the data > > set name are SYS1, or the data set name is SYSCTLG. > > > > > > HSM does not process SYS1 datasets. > > > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the > > dataset is generally not required by any of your started tasks or other > processes. > > > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for > it. > > Of course, the new datasetname would need to be catalogued in the > > master catalogue too. > > > > Ant. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Gibney, Dave > > Sent: Tuesday, 27 March 2018 11:19 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: DFHSM Migration of SYS1 datasets ? > > > > I am at z/OS 2.1. I understand the need to make this hard, but what am > > I missing. > > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION > ARC0170I > > SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET > NOT > > ELIGIBLE FOR MIGRATION > > > > The documentation indicates that the SETMIG command should allow me to > > request DFHSM perform this migration. I've tried several varations > > using SETMIG LEVEL also. The volume where this dataset resides is Non- > SMS. > > > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > > > Does this function just not work? Or have missed something obvious. > > > > Dave Gibney > > Information Technology Services > > Washington State University > > > > > > -- > 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 Migration of SYS1 datasets ?
Quite right Bart. HSM V2.3 Impl & Cust Ch 4 (User Datasets) has Table 4 listing dataset type support for space management functions. One of the entries in that table says datasets starting with SYS1 or HSM won't get command-migrated, but notes that the restriction can be over-ridden by SETMIG LEVEL(). Page 62. Same page number in the 2.1 version of the manual. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of van der Grijn, Bart (B) Sent: Wednesday, 28 March 2018 4:11 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM Migration of SYS1 datasets ? I've never used the option, but the way I read the manual (z/OS 2.3), it specifically requires the LEVEL parameter. I assume that means you need to do a SETMIG for LEVEL(SYS1) rather than at the DATASETNAME level. I haven't tested this, it's just how I interpret the manual. FWIW, Bart -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave Sent: Tuesday, March 27, 2018 4:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM Migration of SYS1 datasets ? This email originated from outside of the organization. And the SETMIG command's apparent explicit purpose as documented to allow removing/reinstating this restriction by LEVEL or DATASETNAME. > -Original Message- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Anthony Thompson > Sent: Monday, March 26, 2018 8:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > ARC1245I Reason Code 1: > > The data set is a system data set, a VSAM catalog, or an integrated > catalog facility (ICF) catalog. Either the first four characters of > the data set name are HSM, or the first five characters of the data > set name are SYS1, or the data set name is SYSCTLG. > > > HSM does not process SYS1 datasets. > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the > dataset is generally not required by any of your started tasks or other > processes. > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for it. > Of course, the new datasetname would need to be catalogued in the > master catalogue too. > > Ant. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, 27 March 2018 11:19 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM Migration of SYS1 datasets ? > > I am at z/OS 2.1. I understand the need to make this hard, but what am > I missing. > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION ARC0170I > SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET NOT > ELIGIBLE FOR MIGRATION > > The documentation indicates that the SETMIG command should allow me to > request DFHSM perform this migration. I've tried several varations > using SETMIG LEVEL also. The volume where this dataset resides is Non-SMS. > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > Does this function just not work? Or have missed something obvious. > > Dave Gibney > Information Technology Services > Washington State University > > -- 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 Migration of SYS1 datasets ?
I tried both LEVEL(SYS1) and DATASETNAME. The MIGRATE (or HMIGRATE) command gets the same response in all cases I tried. > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of van der Grijn, Bart (B) > Sent: Tuesday, March 27, 2018 11:41 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > I've never used the option, but the way I read the manual (z/OS 2.3), it > specifically requires the LEVEL parameter. I assume that means you need to > do a SETMIG for LEVEL(SYS1) rather than at the DATASETNAME level. > I haven't tested this, it's just how I interpret the manual. > FWIW, > Bart > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, March 27, 2018 4:00 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > This email originated from outside of the organization. > > > And the SETMIG command's apparent explicit purpose as documented to > allow removing/reinstating this restriction by LEVEL or DATASETNAME. > > > -Original Message- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Anthony Thompson > > Sent: Monday, March 26, 2018 8:48 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: DFHSM Migration of SYS1 datasets ? > > > > ARC1245I Reason Code 1: > > > > The data set is a system data set, a VSAM catalog, or an integrated > > catalog facility (ICF) catalog. Either the first four characters of > > the data set name are HSM, or the first five characters of the data > > set name are SYS1, or the data set name is SYSCTLG. > > > > > > HSM does not process SYS1 datasets. > > > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the > > dataset is generally not required by any of your started tasks or other > processes. > > > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for > it. > > Of course, the new datasetname would need to be catalogued in the > > master catalogue too. > > > > Ant. > > > > -Original Message- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Gibney, Dave > > Sent: Tuesday, 27 March 2018 11:19 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: DFHSM Migration of SYS1 datasets ? > > > > I am at z/OS 2.1. I understand the need to make this hard, but what am > > I missing. > > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION > ARC0170I > > SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET > NOT > > ELIGIBLE FOR MIGRATION > > > > The documentation indicates that the SETMIG command should allow me to > > request DFHSM perform this migration. I've tried several varations > > using SETMIG LEVEL also. The volume where this dataset resides is Non- > SMS. > > > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > > > Does this function just not work? Or have missed something obvious. > > > > Dave Gibney > > Information Technology Services > > Washington State University > > > > > > -- > 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 Migration of SYS1 datasets ?
I've never used the option, but the way I read the manual (z/OS 2.3), it specifically requires the LEVEL parameter. I assume that means you need to do a SETMIG for LEVEL(SYS1) rather than at the DATASETNAME level. I haven't tested this, it's just how I interpret the manual. FWIW, Bart -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave Sent: Tuesday, March 27, 2018 4:00 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: DFHSM Migration of SYS1 datasets ? This email originated from outside of the organization. And the SETMIG command's apparent explicit purpose as documented to allow removing/reinstating this restriction by LEVEL or DATASETNAME. > -Original Message- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Anthony Thompson > Sent: Monday, March 26, 2018 8:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > ARC1245I Reason Code 1: > > The data set is a system data set, a VSAM catalog, or an integrated catalog > facility (ICF) catalog. Either the first four characters of the data set name > are > HSM, or the first five characters of the data > set name are SYS1, or the data set name is SYSCTLG. > > > HSM does not process SYS1 datasets. > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the dataset is > generally not required by any of your started tasks or other processes. > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for it. > Of course, the new datasetname would need to be catalogued in the master > catalogue too. > > Ant. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, 27 March 2018 11:19 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM Migration of SYS1 datasets ? > > I am at z/OS 2.1. I understand the need to make this hard, but what am I > missing. > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION > ARC0170I SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET NOT > ELIGIBLE FOR MIGRATION > > The documentation indicates that the SETMIG command should allow me to > request DFHSM perform this migration. I've tried several varations using > SETMIG LEVEL also. The volume where this dataset resides is Non-SMS. > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > Does this function just not work? Or have missed something obvious. > > Dave Gibney > Information Technology Services > Washington State University > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM Migration of SYS1 datasets ?
According to dfHSM Impl/Cust guide Chapter 16, this is possible (z/OS 2.2). I did not check to see when this capability was added. It may not be possible at you level of z/OS. Have you checked the log(s) for S913 or other messages besides the ARC1245I message? Accessing data without allocation or OPEN (non-SMS) If DFSMShsm migrates a data set, subsequent access to the data set while it is migrated must cause allocation to do a catalog LOCATE or OPEN must be issued to cause the data set to be automatically recalled. For example, if the volser and unit are specified on a SYSPROC DD statement in a TSO logon procedure, a problem exists if that data set is migrated. The problem exists because no catalog LOCATE is done by allocation and no OPEN is performed in TSO unless the volume specified is an SMS-managed volume. DFSMShsm does not migrate data sets having SYS1 as the first qualifier unless a SETMIG LEVEL request has been issued to remove this restriction. For other data sets used in the above manner, the system programmer must either not specify the volser and unit (which causes a catalog LOCATE by allocation), or specify the names of the data sets on SETMIG commands placed in the DFSMShsm startup member to prevent them from migrating. HTH. ::DISCLAIMER:: -- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: DFHSM Migration of SYS1 datasets ?
And the SETMIG command's apparent explicit purpose as documented to allow removing/reinstating this restriction by LEVEL or DATASETNAME. > -Original Message- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > Behalf Of Anthony Thompson > Sent: Monday, March 26, 2018 8:48 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DFHSM Migration of SYS1 datasets ? > > ARC1245I Reason Code 1: > > The data set is a system data set, a VSAM catalog, or an integrated catalog > facility (ICF) catalog. Either the first four characters of the data set name > are > HSM, or the first five characters of the data > set name are SYS1, or the data set name is SYSCTLG. > > > HSM does not process SYS1 datasets. > > If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the dataset is > generally not required by any of your started tasks or other processes. > > You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for it. > Of course, the new datasetname would need to be catalogued in the master > catalogue too. > > Ant. > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, 27 March 2018 11:19 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: DFHSM Migration of SYS1 datasets ? > > I am at z/OS 2.1. I understand the need to make this hard, but what am I > missing. > F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION > ARC0170I SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED > EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE > DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE > FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET NOT > ELIGIBLE FOR MIGRATION > > The documentation indicates that the SETMIG command should allow me to > request DFHSM perform this migration. I've tried several varations using > SETMIG LEVEL also. The volume where this dataset resides is Non-SMS. > > Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 > > Does this function just not work? Or have missed something obvious. > > Dave Gibney > Information Technology Services > Washington State University > > > -- > 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 Migration of SYS1 datasets ?
ARC1245I Reason Code 1: The data set is a system data set, a VSAM catalog, or an integrated catalog facility (ICF) catalog. Either the first four characters of the data set name are HSM, or the first five characters of the data set name are SYS1, or the data set name is SYSCTLG. HSM does not process SYS1 datasets. If you are trying to migrate SYS1.PSF.FDEFLIB, that implies the dataset is generally not required by any of your started tasks or other processes. You could rename it to another HLQ, establish a SYS1.PSF.FDEFLIB alias for it. Of course, the new datasetname would need to be catalogued in the master catalogue too. Ant. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gibney, Dave Sent: Tuesday, 27 March 2018 11:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: DFHSM Migration of SYS1 datasets ? I am at z/OS 2.1. I understand the need to make this hard, but what am I missing. F DFHSM,SETMIG DATASETNAME(SYS1.PSF.FDEFLIB) COMMANDMIGRATION ARC0170I SETMIG DSN SYS1.PSF.FDEFLIB PROCESSED EJES510 LT01-GIBNEY--/F DFHSM,MIGRATE DATASETNAME(SYS1.PSF.FDEFLIB) F DFHSM,MIGRATE DATASETNAME(SYS1.PSF.FDEFLIB) ARC1001I SYS1.PSF.FDEFLIB MIGRATE FAILED, RC=0045, 051 ARC1001I (CONT.) REAS=0001 ARC1245I DATA SET NOT ELIGIBLE FOR MIGRATION The documentation indicates that the SETMIG command should allow me to request DFHSM perform this migration. I've tried several varations using SETMIG LEVEL also. The volume where this dataset resides is Non-SMS. Yes, I know I can use ADRDSSU to move it, but not to M1 or ML2 Does this function just not work? Or have missed something obvious. Dave Gibney Information Technology Services Washington State University -- 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
