Using two-stage generation of stand-alone dump when migrating

When migrating to a new version of MVS™, generate a new version of the stand-alone dump program. Use the new MVS system data sets to build the new version of the stand-alone dump program.

Always use a stand-alone dump version that is generated from the same release of MVS that you want to dump. IBM® does not guarantee that a different level of stand-alone dump will successfully dump anything other than the level of MVS it was designed for. The new version of MVS might have changed making the stand-alone dump program unable to locate vital information it needs to operate.

To generate a new version of the stand-alone dump program, follow the same steps you followed for a normal two-stage generation, then add the following steps:

Ensure that the new version of the AMDSADMP macro is being used by specifying the correct SYSLIB data set.
Use the NUCLIB, MODLIB, LNKLIB and/or ALIB parameters on the AMDSADMP macro invocation to create the correct stage-two JCL.

The output shown in Figure 1 assembles the version of the AMDSADMP macro contained in the SYSLIB data set SYS1.MACLIB, found on a 3390 DASD with volser=NEWSYS. Because the ALIB parameter is specified, the stage-two JCL will use the SYS1.NUCLEUS, SYS1.MODGEN, and SYS1.LINKLIB system data sets, also found on the 3390 DASD with volser=NEWSYS.

Figure 1. Example: Stage-two JCL to assemble the AMDSADMP macro

//ASSEMSAD JOB  MSGLEVEL=(1,1)
//ASM      EXEC PGM=ASMA90,REGION=4096K,PARM='DECK'
//SYSLIB   DD   DSN=SYS1.MACLIB,DISP=SHR,
//             UNIT=3390,VOL=SER=NEWSYS
//SYSUT1   DD   UNIT=SYSDA,SPACE=(1700,(400,50))
//SYSPRINT DD   SYSOUT=(*,,STD),HOLD=YES
//SYSPUNCH DD   DSN=D10.SYS430.STAGE3.JCL(SADMPST2),DISP=SHR
//SYSLIN   DD   SYSOUT=H
//SYSIN    DD   *
           AMDSADMP   MINASID=ALL,IPL=DSYSDA,                          X
               DUMP=('DATASPACES OF ASID('XCFAS','CTTX','APPC')'),     X
               VOLSER=SADUMP,                                          X
               CONSOLE=((020,3277),(030,3277),(040,3277),(050,3277)),  X
               PROMPT,MSG=ALL,                                         X
               OUTPUT=T560,                                            X
               ALIB=(NEWSYS,3390)
           END
/*

Note: Using the ALIB parameter is convenient if all of the system data sets used by the stand-alone dump program reside on the same volume. Also, note that the same results could have been achieved by coding the NUCLIB, MODLIB, and LNKLIB keywords separately with each specifying NEWSYS and 3390 for volser and unit.

Figure 2 shows the output that assembles the version of the AMDSADMP macro contained in the SYSLIB data set, SYS1.MACLIB, found on a 3390 DASD with volser=NEWSYS. Because the MODLIB parameter is specified, the stage-two JCL will use the SYS1.MODGEN system data set found on a 3380 DASD with volser=SYS51A. Because the ALIB parameter is specified, the stage-two JCL will use the SYS1.NUCLEUS and SYS1.LINKLIB system data sets found on a 3390 DASD with volser=SYS51B.

Figure 2. Example: Stage-two JCL to assemble the AMDSADMP macro

//ASSEMSAD JOB  MSGLEVEL=(1,1)
//ASM      EXEC PGM=ASMA90,REGION=4096K,PARM='DECK'
//SYSLIB   DD   DSN=SYS1.MACLIB,DISP=SHR,
//             UNIT=3390,VOL=SER=NEWSYS
//SYSUT1   DD   UNIT=SYSDA,SPACE=(1700,(400,50))
//SYSPRINT DD   SYSOUT=(*,,STD),HOLD=YES
//SYSPUNCH DD   DSN=D10.SYS430.STAGE3.JCL(SADMPST2),DISP=SHR
//SYSLIN   DD   SYSOUT=H
//SYSIN    DD   *
           AMDSADMP   MINASID=ALL,IPL=DSYSDA,                          X
               DUMP=('DATASPACES OF ASID('XCFAS','CTTX','APPC')'),     X
               VOLSER=SADUMP,                                          X
               CONSOLE=((020,3277),(030,3277),(040,3277),(050,3277)),  X
               PROMPT,MSG=ALL,                                         X
               OUTPUT=T560,                                            X
               MODLIB=(SYS51A,3380),                                   X
               ALIB=(SYS51B,3390)
           END
/*

Note that the ALIB parameter has no effect on the SYS1.MODGEN system data set because the MODLIB parameter was specified separately. The stand-alone dump program will be generated using the cataloged system data sets if the NUCLIB, MODLIB, LNKLIB, or ALIB parameters are not specified.