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


Procedure for SVC dump

z/OS DFSMSdfp Diagnosis
SC23-6863-00

SVC dumps invoked by the SDUMP macro are usually written as a result of an entry into a functional recovery routine (FRR) or ESTAE routine. The component recovery routine specifies the addresses that are dumped and directs the dump to one of the SYS1.DUMPxx data sets. The SVC dump contains enough information for you to build the keyword string.

You can find the structured search keywords in the Summary Diagnostic Worksheet Figure 1 under the section RETAIN® SEARCH ARGUMENT. Use these keywords in freeform searches.

If the abend code is X'08B', then SMS has experienced a "data in virtual" (DIV) abend. Do the following:
  • Obtain the registers from the time of abend, using either the IGD300I message or the system diagnostic work area (SDWA).
  • Examine the contents of register 15. The two low-order bytes contain the DIV reason code related to the abend. Append the reason code to the keyword prefix RC. and record it on the Keyword worksheet.

    See the description of the applicable DIV reason code listed under abend code 08B in z/OS MVS System Codes. It might help you define more closely the source of the failure. If it indicates that the problem is external to DFSMSdfp, continue the diagnosis process within the component involved.

If the abend code is X'0F4', then an error occurred during program management binder, DCME, HFS, PDSE, or VSAM RLS processing. Do the following:
  • Review SYS1.LOGREC for X'0F4' software records, PDSE symptom records, and any other records produced at the time of the error. Program management binder, DCME, HFS, PDSE, and VSAM RLS symptom records are primarily used to identify incidents identified with program management binder, DCME, HFS, PDSE, and VSAM RLS X'0F4' abends. When program management binder, DCME, HFS, PDSE, or VSAM RLS symptom records occur without an X'0F4', use the symptom strings to search for matching problems in the IBM® software support database, and if no errors exist, contact the IBM Support Center.
  • Prior to the ABEND error, a return code is placed in general register 15, and a unique reason code is placed in general register 0 describing the exceptional condition. Append the reason code from general register 0 to the keyword prefix RSN and record it as a modifier keyword on the Keyword worksheet. Remove the leading zeroes from the return code from general register 15 and append it to the keyword prefix RC. Record it as a modifier keyword on the Keyword worksheet. Using the information from Figure 1 as an example, the modifier keywords would be as follows:
    abend0f4   rsn21042716  rc24
    PDSE reason codes are used primarily for searching the IBM software support database; therefore, reason code descriptions are not documented in this information.

To determine keywords for SVC dumps, do the following:

  1. Use IPCS to print the summary dump (SUMDUMP). See z/OS MVS IPCS User's Guide.
  2. The title page of the Summary Diagnostic Worksheet contains the dump header and title page, which provide failure-related symptoms extracted from the dump. (See the example in Figure 1.) One or more of the following symptoms should be present:
    • ABENDnnn
    • Module or CSECT name or both
    • Component Identifier
    • Release Level
    • Service Level
    • FMID

    Refer to z/OS Problem Management, z/OS MVS Diagnosis: Reference, and z/OS MVS Diagnosis: Tools and Service Aids for a detailed explanation of each symptom.

  3. If you can identify the ABEND CODE by using the dump header and title page, see Building the Abend keyword.
  4. If the dump does not have a header title or does not otherwise enable you to identify the ABEND CODE, use the SUMDUMP printed from the SYS1.DUMPxx data set and continue with Procedure for SYSABEND, SYSMDUMP, or SYSUDUMP.
Figure 1. Sample Summary Diagnostic Worksheet
TITLE
LIST 00000000 HEADER POSITION(:hex.0058:ehex.) LENGTH(97) CHARACTER
HEADER ADDRESS(00000058)
00000058 |                         COMPID=DF115,CSECT=IGWBVLP1+0F0C,DATE=12 |
00000080 | /20/04,MAINTID=NONE    ,ABND=0F4,RC=00000024,RSN=21042716        |
                        * * * *  S Y M P T O M  * * * *
  Primary Symptom String:
    RIDS/IGWBBMF1#L RIDS/IGWBVLP1 PIDS/5695DF115 AB/S00F4 RIDS/IGWBSGLR#R VALU/HD1641854 REGS/0E010 REGS/0CEE4
    PRCS/00000024
    Symptom            Symptom data       Explanation
    ---------------    -------------      -----------
    RIDS/IGWBBMF1#L    IGWBBMF1#L         Routine identifier
    PIDS/5695DF115     5695DF115          Component identifier
    AB/S00F4           00F4               ABEND code - system
    RIDS/IGWBSGLR#R    IGWBSGLR#R         Routine identifier
    VALU/HD1641854     D1641854           Error related hexadecimal value
    REGS/0E010         0E010              Program register
    PRCS/00000024      00000024           Return code
The dump does not contain a secondary symptom string.
         ****** DUMP ANALYSIS AND ELIMINATION (DAE) ******
THIS DUMP WAS NOT SUPPRESSED BECAUSE
DAE WAS NOT CHECKING FOR PREVIOUS OCCURRENCES.
CRITERIA FOR USE AS A UNIQUE DUMP IDENTIFIER BY DAE:
     MINIMUM NUMBER OF SYMPTOMS:  07  FOUND: 09
     MINIMUM TOTAL STRING LENGTH: 025 FOUND: 130
     SYMPTOMS REQUIRED TO BE PRESENT: MOD/ CSECT/
     SYMPTOMS THAT ARE TO BE USED IF AVAILABLE, BUT ARE NOT REQUIRED:
       PIDS/ AB/S AB/U REXN/ FI/ REGS/ HRC1/ SUB1/
MVS SYMPTOM STRING:
MOD/IGWBBMF1 CSECT/IGWBVLP1 PIDS/5695DF115 AB/S00F4 REXN/IGWBSGLR
FI/9C7918F60A0D4140D1641854 REGS/0E010 REGS/0CEE4 HRC1/00000024
RETAIN SEARCH ARGUMENT:
RIDS/IGWBBMF1#L RIDS/IGWBVLP1 PIDS/5695DF115 AB/S00F4 RIDS/IGWBSGLR#R
VALU/HD1641854 REGS/0E010 REGS/0CEE4 PRCS/00000024
SYMPTOMS PRESENT FOR USE AS A UNIQUE DUMP IDENTIFIER BY DAE: RETAIN
MVS KEY   KEY     SYMPTOM DATA               EXPLANATION
-------  ------   ------------               -----------
MOD/     RIDS/    IGWBBMF1                   LOAD MODULE NAME
CSECT/   RIDS/    IGWBVLP1                   ASSEMBLY MODULE CSECT NAME
PIDS/    PIDS/    5695DF115                  PRODUCT/COMPONENT IDENTIFIER
AB/S     AB/S     S00F4                      ABEND CODE-SYSTEM
REXN/    RIDS/    IGWBSGLR                   RECOVERY ROUTINE CSECT NAME
FI/      VALU/H   9C7918F60A0D4140D1641854   FAILING INSTRUCTION AREA
REGS/    REGS/    0E010                      REG/PSW DIFFERENCE
REGS/    REGS/    0CEE4                      REG/PSW DIFFERENCE
HRC1/    PRCS/    00000024                   REASON CODE
ADDITIONAL SYMPTOM DATA NOT USED BY DAE TO IDENTIFY THIS DUMP: RETAIN
MVS KEY   KEY     SYMPTOM DATA               EXPLANATION
-------  ------   ------------               -----------
CID1/    VALU/C   DF115                      COMPONENT IDENTIFIER
AMD1/    VALU/C   12#20#91                   MODULE ASSEMBLY DATE
VRS1/    VALU/C   NONE                       VERSION-PRODUCT/PTF IDENTIFIER
RRL1/    FLDS/    IGWFRCSD                   RECOVERY ROUTINE LABEL
CDB1/    VALU/C   5695                       BASE COMPONENT IDENTIFIER
FRR1/    VALU/H   C9C7E6C6C5C6D7407F6810287F681250
                                             FRR PARAMETER AREA
ASID1/   VALU/H   004D                       TASK RELATED ASID
ORCC1/   PRCS/    0F4000                     ORIGINAL COMPLETION CODE
ORRC1/   PRCS/    00000024                   ORIGINAL REASON CODE
@201/    VALU/C   W                          DEVELOPER ASSIGNED SYMPTOM KEY
@201/    VALU/C   H                          DEVELOPER ASSIGNED SYMPTOM KEY
@202/    VALU/C   ##                         DEVELOPER ASSIGNED SYMPTOM KEY
@202/    VALU/C   #COMPID#DF115#CSECT#IGWBVLP1#0F0C#DATE#12#20#
                                             DEVELOPER ASSIGNED SYMPTOM KEY

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014