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
