| 1 | Save the console sheet from the primary console. For systems
with remote consoles, save the remote console sheet. In systems with
multiple console support (MCS), save a copy of the hardcopy log. |
| 2 | Save the job stream associated with the job. |
| 3 | Save the system output (SYSOUT) associated with the job. |
| 4 | Ensure that the job step includes one of these:
- SYSABEND DD statement
- SYSDUMP DD statement
- PL1DUMP DD statement
- SYSMDUMP DD statement
|
| 5 | If SMP/E is used to make all the changes to the
system, run the LIST SYSMODS FORFMID(HPRFxxx) command of
SMP/E to obtain a list of the current maintenance for PSF from the
SMP consolidated software inventory, SMPCSI. HPRFxxx is the
current FMID, such as HPRF440 for PSF 4.4.0 for z/OS®. |
| 6 | Run the AMBLIST service aid program to obtain:
- An object module listing specifying the LISTOBJ function
- A load module map and cross-reference listing, specifying the
OUTPUT = BOTH option of the LISTLOAD function
|
| 7 | Run the MVS™ DUMP command
to dump the contents of the PSF address space to a dump data set.
If needed, use IPCS to view the dump. |
| 8 | Save all the associated output. |
| 9 | Save the dump. |
| 10 | Have the system generation (SYSGEN) output available from:
|
| 11 | Run the EREP service aid to dump the SYS1.LOGREC data set,
and save the resulting output. For MSS, run the following program
to dump the SYS1.LOGREC data set:
- Service aid IFCISDAO
- Program ISDASDAO with the DETAIL(ALL) parameter
|
| 12 | Save the control card associated with the job. |
| 13 | Save the source input associated with the job. |
| 14 | Run the system utility program to obtain a list of these:
- Volume table of contents of the associated volume, specifying
the FORMAT option
- Volume table of contents of the associated volume, specifying
the DUMP option
- Directory of the associated data set
|
| 15 | Run the IEBPTPCH data set utility to print these:
- Directory of the applicable data set
- Applicable data set
- Applicable member
- Applicable procedure
|
| 16 | Have the linkage editor/loader map available. |
| 17 | To report a possible software error, consult your IBM Support Center. |
| 18 | To report a possible hardware or microcode error, consult your
printer service representative. |
| 19 | Take a PSF full trace output data set. |
| 20 | Print the associated SVC dump data set by using the ABSDUMP
service aid with the GO statement. |
| 21 | Run the AMASPZAP service aid program with the ABSDUMP statement
to print the contents of the applicable:
|
| 22 | Use the IEBCOPY to unload the SYS1.IMAGELIB to tape. |
| 23 | Consult your IBM system engineer. |
| 24 | Have the JES initialization output available. |
| 25 | Take a PSF SYNC trace output data set. |
| 26 | Save PSF system task output. |
| 27 | Create a PSF dump on this message, and ensure that an internal
PSF trace is in the dump (TRACE=YES) (DUMP=,APSXXXXI). |
| 28 | Save the security definitions library member. |
| 29 | Take a PSF notify subtask (NST) trace output data set. |
| 30 | If running under JES3, create a PSF dump to obtain additional information contained
in the JES3 FSS/FSA trace tables. |
| 31 | On z/OS,
verify the enable/disable state of PSF with the command D PROD,STATE,
and save the system log. |
| 32 | See PSF for z/OS: AFP Download Plus to
determine the download receiver support needed. |
| 33 | Create a PSF dump on the reason code specified by RS('reasoncode'X)
in the message, and ensure that an internal PSF trace is in the dump
(TRACE=YES) (DUMP=reasoncode). |
PSF for z/OS: Messages and Codes
Copyright IBM Corporation 1990, 2014