When overriding to use a different systems database, IBM® recommends that you 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.
Although the current version of the stand-alone dump program might be able to dump a new version of MVS successfully, it is not guaranteed. MVS might have changed such that the stand-alone dump program would not be able to locate vital information it needs to operate.
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=OVRIDE. 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=OVRIDE.
// EXEC ASMAC,PARM.C='DECK,NOOBJECT'
//C.SYSLIB DD DSN=SYS1.MACLIB,DISP=SHR,UNIT=3390,VOL=SER=OVRIDE
//C.SYSPUNCH DD DSN=SMITH.TEST.CNTL(SADMP#2),DISP=OLD
//C.SYSIN DD *
AMDSADMP IPL=D3390, IPL FROM DASD X
VOLSER=SADIPL, VOL=SER=SADIPL X
OUTPUT=(D330,SYS1,SADMP), DEFAULT OUTPUT DEVICE X
MSG=ALL, ALL MESSAGES TO CONSOLE X
DUMP=('SP(ALL) IN ASID(1) ALSO DATASPACES OF ASID(1,'JESXCF',
'APPC','SMSVSAM', 'CONSOLES','SYSBMAS') ALSO PAGETABLES OF
DATASPACES X
ALSO SP(ALL) IN ASID('JES2')'), X
MINASID=ALL, INCLUDE SWAPPED OUT SPACES X
REUSEDS=CHOICE, PROMPT FOR DATASET REUSE X
DDSPROMPT=NO, OVERRIDE BUILD DATASETS X
ALIB=(OVRIDE,3390)
END
/*