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


Procedure

z/OS DFSMSdfp Diagnosis
SC23-6863-00

If the failure is indicated by an ABEND001, use the following procedure to determine the module name. Otherwise, see Table 1.

  1. Using the formatted portion of the dump obtained earlier, scan the RBs for the job in question, looking for the one that issued an EOV SVC just prior to the abend. The INTCODE field of the RB contains X'0037' for jobs that issued an EOV SVC. Check the dump and locate the INTCODE field. Refer to z/OS MVS Diagnosis: Tools and Service Aids for information on dumps.
  2. The instruction address in the RB's PSW is the failure-related address. Determine the module name by matching that address with the addresses in an LPA map. Most SAM modules reside in the LPA. (The exceptions are module IGG019V6 in SYS1.SVCLIB and SAM modules in SYS1.LINKLIB that support IBM® 3505/3525 Reader/Punch.)
  3. Use the entire module name as the module keyword.

    Example: If the module name is IGG019BB, specify the module name keyword as IGG019BB.

    If the system issued message IEC020I to inform the system operator of the abend, the message text identifies the O/C/EOV module that processes SAM abend 001s. Record the module name. If your keyword string does not produce any similar problems in the software support database, replace the SAM module name with the O/C/EOV module name that appears in the IEC020I message and perform the search again.

  4. See Modifier keywords.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014