z/OS DFSMSdfp Diagnosis
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Abend type-of-failure procedure

z/OS DFSMSdfp Diagnosis
SC23-6863-00

  1. If the system issued a message identifying an abend condition, the module name might appear in the message text. The CSECT name or module name might also appear in the dump title in a console message or after executing the DISPLAY DUMP,TITLE system command.
  2. If an EREP software record exists for the failure, use the failing PSW address with maps of the nucleus and LPA to determine the failing module, and then go to Step 3.d. (See EREP User's Guide for details.)
  3. If neither condition is true, continue as follows:
    1. Using the formatted section of the dump, scan the RBs for the job in question, looking for the one representing the failing user program.
    2. The interrupt code field in the user's RB should indicate an SVC code representing the call to the DFSMSdfp service that abended. The next RB represents the failing DFSMSdfp service. Its interrupt code field (IC portion of the WC-L-IC field) should match the abend code.
    3. Using the address portion of the PSW field in that RB, locate that address in the dump and scan toward the lower addresses, looking in the translated EBCDIC in the right-hand column for a module name. Most DFSMSdfp modules contain the module name at the start of each CSECT. You can also determine the module name by matching that address with the addresses in a map of the nucleus or LPA.
    4. Specify the entire module name as the module keyword.
  4. See Modifier keywords.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014