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


Steps for using the ABENDxxx failure keyword

z/OS DFSMShsm Diagnosis
GC52-1387-00

The format of the keyword string is:
 5695DF170 Rnnn ABENDxxxx module name

Rnnn is the release keyword, and its optional use can reduce the number of matches in the search.

  1. Add the abend code (xxxx) to the ABEND keyword. DFSMShsm issues either system or user abend codes; therefore, you should use both of the following search methods:
    System abend code
    Entered in hexadecimal and has a fixed length of 3 hexadecimal characters. For example, use ABEND0C6 if an 0C6 abend occurred. Other search words common to a DFSMShsm system abend include: ABEND0C4, ABEND878, and ABENDE37.
    User abend code
    Entered in decimal and varies in length. It is entered without any leading zeros. For example, a 3EC abend would be entered as ABEND1004. Note that there are no zeroes between the abend prefix and the first nonzero character in the decimal value of the user abend code.
  2. If the abnormal end has occurred in a DFSMShsm primary address space, message ARC0003I indicates the module name and offset of the abnormal end. An alternate method can be used, however, if message ARC0003I is not received or if the message states that the module and offset are unknown. The program status word (PSW) and the register contents at the time of the abend can be found in the RTM2WA summary obtained by using the SUMMARY command in the Interactive Problem Control System (IPCS). Proceed to the instructions in Step 4 after you have determined the storage location at which the abend occurred.
  3. If the abnormal end has occurred in the ABARS secondary address space, message ARC6035E indicates the module name and offset of the abnormal end. The PSW address and the register contents at the time of the abend are saved in the ARCWABNP control block. To find this control block, issue a FIND command for WABNP250 from the IPCS browse function. Look at the WABPSW2 field to find the PSW address at the time of the abend. If message ARC6035E is not received, the data in ARCWABNP is not reliable and you must use the information stored in the RTM2WA summary. The program status word (PSW) and the register contents at the time of the abend can be found in the RTM2WA by using the SUMMARY command in IPCS. Proceed to the instructions in Step 4 after you have determined the storage location at which the abend occurred.
  4. If the module corresponding to the address in the PSW is not identified by either message ARC0003I or ARC6035E, you can identify the failing module using IPCS. Issue a LOCATE command for the PSW address from the browse function. If the address is not found, issue the WHERE command to identify the failing load module. If the WHERE command indicates that the load module is in LPA, issue the IPCS LPAMAP command to identify the failing CSECT. If the LOCATE did find the PSW address, read backward through “eye catcher area” in the dump, until you find the name of the module that abnormally ended. See the following example:
       00DDCFD0.  00000000  00000000  00000000  00000000  | ................ |
       00DDBFE0.  00000000  00000000  00000000  00000000  | ................ |
       00DDBFF0.  00000000  00000000  00000000  00000000  | ................ |
       00DDC000.  47F0F00C  001847F0  F006011E  05C041B0  | .00....00....».. |
       00DDC010.  CFFF4AF0  F00407FF  47F0C080  C9C7C7F0  | ...00....0».IGG0 |
       00DDC020.  F1F9C2E9  F0F261F1  F961F8F8  C8C4D7F2  | 19BZ02/19/88HDP2 |
       00DDC030.  F2F3F040  E4E8F1F8  F6F4F840  F5F6F6F5  | 230 UY18648 5665 |
       00DDC040.  60E7C1F2  404DC35D  40C3D6D7  E8D9C9C7  | -X2A (C) COPYRIG |
       00DDC050.  C8E340C9  C2D440C3  D6D9D74B  40F1F9F8  | HT IBM CORP. 198 |
       00DDC060.  F26B40F1  F9F8F240  D3C9C3C5  D5E2C5C4  | 2, 1982 LICENSED |
       00DDC070.  40D4C1E3  C5D9C9C1  D3E24060  40D7D9D6  |  MATERIALS - PRO |
       00DDC080.  D7C5D9E3  E840D6C6  40C9C2D4  40009180  | PERTY OF IBM .j. |
       00DDC090.  10254780  C114900F  D0004120  20005F20  | ....A...Œ.....¬. |
    Note: This example was obtained by using Interactive Problem Control System (IPCS).

    The preceding example reflects a typical module “eye catcher” in the dump. The “eye catcher” area varies from component to component but generally contains the module name (shown highlighted) the compile date, the function modification identifier (FMID), and the service level in the form of a program temporary fix (PTF) or APAR number. In this example, the module name is IGG019BZ, the compile date is 02/19/88, the FMID is HDP2230, and the service level is PTF UY18648.

    To find the “eye catcher” area at the abend location, use the instruction address from the “PSW on entry to ABEND” or the “PSW at time of error”. Scroll backward in the dump scanning the EBCDIC columns until you locate the associated module name in the “eye catcher” area.

    In this example, module IGG019BZ is a part of DFP and not DFSMShsm. Because the abend occurred in the DFSMShsm address space but in a DFP module, the error could be in either DFSMShsm or DFSMSdfp.

    After determining the module name, the format of the keyword string is ABENDxxx module name, where xxx is the abend code. If the failing module is a non-DFSMShsm module, do not use the DFSMShsm component identification number (5695DF170) or the Rnnn keyword.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014