The following examples show how to code the AMDSADMP macro to create
various kinds of stand-alone dump programs.
Figure 1 shows the AMDSADMP macro coded
without explicitly specified parameters to generate a direct access
resident dump program. The defaults are:
IPL=DSYSDA
VOLSER=SADUMP
ULABEL=NOPURGE
CONSOLE=(01F,3278)
SYSUT=SYSDA
OUTPUT=T282
MSG=ALL
MINASID=ALL
COMPACT=YES
REUSEDS=CHOICE
DDSPROMPT=NO
Figure 1. Example: Accepting All Defaults DUMP1 AMDSADMP
In
Figure 2, the IPL parameter specifies
tape as the residence volume, and the VOLSER parameter identifies
that tape. All other parameters are allowed to default. The defaults
are:
ULABEL=NOPURGE
CONSOLE=(01F,3278)
SYSUT=SYSDA
OUTPUT=T282
MSG=ALL
MINASID=ALL
COMPACT=YES
REUSEDS=CHOICE
DDSPROMPT=NO
Figure 2. Example:
Generating an unformatted, tape resident dump program AMDSADMP IPL=T3400,VOLSER=SATAPE
In
Figure 3, the OUTPUT parameter directs
the stand-alone dump output to dump data set SYS1.SADMP on device
450, and the REUSEDS parameter specifies that the operator be prompted
about whether to reuse the dump data set. The defaults are:
IPL=DSYSDA
VOLSER=SADUMP
ULABEL=NOPURGE
CONSOLE=(01F,3278)
SYSUT=SYSDA
MSG=ALL
MINASID=ALL
COMPACT=YES
DDSPROMPT=NO
Figure 3. Example: Generating a dump program with output to
DASD AMDSADMP OUTPUT=D450,REUSEDS=CHOICE
In
Figure 4, the OUTPUT parameter directs
the stand-alone dump output to dump data set SADMP.DDS1 on device
450. Furthermore, the DDSPROMPT=YES keyword allows for run-time dump
data set prompting. The defaults are:
IPL=DSYSDA
VOLSER=SADUMP
ULABEL=NOPURGE
CONSOLE=(01F,3278)
SYSUT=SYSDA
MSG=ALL
MINASID=ALL
COMPACT=YES
REUSEDS=CHOICE
Figure 4. Example: Generating a dump program with output to
DASD AMDSADMP OUTPUT=(D450,SADMP.DDS1),DDSPROMPT=YES
Recommended specification during the build process is as follows:
SP(ALL) IN ASID(1,'JESXCF')
ALSO DATASPACES OF ASID(1,'JESXCF', 'APPC', 'SMSVSAM', 'CONSOLE', 'SYSBMAS')
ALSO PAGETABLES OF DATASPACES
If you run JES2, add:
ALSO SP(ALL) IN ASID('JES2')
Additional subpools and dataspaces might be needed, depending on
your installed IBM®, vendor,
and locally-written products and applications.