The detail edit report for a software record shows the complete contents of an error record for an abnormal end, including the system diagnostic work area (SDWA). The report is produced by EREP and, through the VERBEXIT LOGDATA subcommand, under IPCS.
Use the detail edit report for a software record to determine the cause of an abend, and the recovery action that the system or application has either taken or not taken. This report enables you to locate where an error occurred, similar to the analysis of an SVC dump. Once you locate the error, you can develop a search argument to obtain a fix for the problem.
For more information, refer to the following documentation:
- See EREP User's Guide for information about producing a detail edit report for an SDWA-type record.
- See z/OS MVS IPCS Commands for information about the VERBEXIT LOGDATA subcommand.
The example output shown in Example: One record with SDWARC4 and 64-bit information is from one record with SDWARC4 and 64-bit information. This record also has information in the VRA, which is formatted.
Example: One record with SDWARC4 and 64-bit information
TYPE: SOFTWARE RECORD REPORT: SOFTWARE EDIT REPORT DAY.YEAR
(SVC 13) REPORT DATE: 343.04
FORMATTED BY: IEAVTFDE HBB7703 ERROR DATE: 336.04
MODEL: 2084 HH:MM:SS.TH
SERIAL: 11778D TIME: 17:43:44.72
JOBNAME: PIDA1028 SYSTEM NAME: J50
ERRORID: SEQ=00757 CPU=0056 ASID=0097 TIME=17:43:44.7
SEARCH ARGUMENT ABSTRACT
PIDS/5752SCLDR RIDS/IEWLDR00#L RIDS/IEWLUNF0 AB/S0378 PRCS/00000014
RIDS/IEWLRECV#R
SYMPTOM DESCRIPTION
------- -----------
PIDS/5752SCLDR PROGRAM ID: 5752SCLDR
RIDS/IEWLDR00#L LOAD MODULE NAME: IEWLDR00
RIDS/IEWLUNF0 CSECT NAME: IEWLUNF0
AB/S0378 SYSTEM ABEND CODE: 0378
PRCS/00000014 ABEND REASON CODE: 00000014
RIDS/IEWLRECV#R RECOVERY ROUTINE CSECT NAME: IEWLRECV
OTHER SERVICEABILITY INFORMATION
SUBFUNCTION: LSLOADER
SERVICEABILITY INFORMATION NOT PROVIDED BY THE RECOVERY ROUTINE
RECOVERY ROUTINE LABEL
DATE ASSEMBLED
MODULE LEVEL
TIME OF ERROR INFORMATION
PSW: 07041000 80000000 00000000 012F902E
INSTRUCTION LENGTH: 02 INTERRUPT CODE: 000D
FAILING INSTRUCTION TEXT: 00181610 0A0D18CE 18FB180C
BREAKING EVENT ADDRESS: 00000000_00000000
AR/GR 0-1 00000000/00000000_84000000 00000000/00000000_84378000
AR/GR 2-3 00000000/00000000_00000020 00000000/00000000_0000FC03
AR/GR 4-5 00000000/00000001_008FD098 00000000/00000000_00FD5750
AR/GR 6-7 01FF000C/00000000_00000003 01FF000C/00000001_00F52C00
AR/GR 8-9 00000000/00000001_7F33F4A8 00000000/00000001_00001748
AR/GR 10-11 00000000/00000001_2C417000 01FF000C/00000001_7F36EC88
AR/GR 12-13 00000000/00000000_8651F240 00000000/00000001_7F33F0E8
AR/GR 14-15 00000000/00000000_8651FF54 00000000/00000000_00000014
HOME ASID: 0097 PRIMARY ASID: 0097 SECONDARY ASID: 0097
PKM: 00C0 AX: 0000 EAX: 0000
RTM WAS ENTERED BECAUSE AN SVC WAS ISSUED IN AN IMPROPER MODE.
THE ERROR OCCURRED WHILE: A TYPE 1 SVC WAS IN CONTROL
A LOCKED OR DISABLED ROUTINE WAS IN CONTROL
LOCKS HELD: LOCAL/CML
NO SUPER BITS WERE SET.
RECOVERY ENVIRONMENT
RECOVERY ROUTINE TYPE: FUNCTIONAL RECOVERY ROUTINE (FRR)
PSW AT ENTRY TO FRR: 070C0000 86502368
FRR PARAMETER AREA ON ENTRY TO FRR:
+00 7F33F4A8 00000000 00000000 00000000 00000000 00000000
RECOVERY ROUTINE ACTION
THE RECOVERY ROUTINE RETRIED TO ADDRESS 0651FFA2.
THE REQUESTED SVC DUMP WAS SUCCESSFULLY STARTED.
NO LOCKS WERE REQUESTED TO BE FREED.
THE SDWA WAS REQUESTED TO BE FREED BEFORE RETRY.
THE REGISTER VALUES TO BE USED FOR RETRY:
REGISTERS 0-7
GR: 008FDD00 00000000 7FFFC100 00000000 008FD098 7FFFC150 7FFFBF48 00F52C00
AR: 00000000 00000000 00000000 00000000 00000000 00000000 01FF000C 01FF000C
REGISTERS 8-15
GR: 7F33F4A8 06520100 00FD5750 00000001 8651F240 7F33F0E8 7F33F638 00000000
AR: 00000000 00000000 00000000 01FF000C 00000000 00000000 00000000 00000000
HEXADECIMAL DUMP
HEADER
+000 40831820 00000000 0004336F 17434472 | C.........?....|
+010 0011778D 20848000 |.....D.. |
JOBNAME
+000 D7C9C4C1 F1F0F2F8 |PIDA1028 |
SDWA BASE
+000 00000C00 04378000 00000000 00000000 |................|
+010 00000000 00000000 84000000 84378000 |........D...D...|
+020 00000020 0000FC03 008FD098 00FD5750 |..........}Q...&|
+030 00000003 00F52C00 7F33F4A8 00001748 |.....5..".4Y....|
+040 2C417000 7F36EC88 8651F240 7F33F0E8 |...."..HF.2 ".0Y|
.
.
.
+180 00000000 00000000 00000000 0009BD27 |................|
+190 00FFA0B0 |.... |
VARIABLE RECORDING AREA (SDWAVRA)
+000 KEY: 37 LENGTH: 06
+002 C4C4D5C1 D4C5 |DDNAME |
+008 KEY: 39 LENGTH: 08
+00A 6060C8C6 E2606060 |--HFS--- |
.
.
.
+0AA 0003 |.. |
+0AC KEY: 53 LENGTH: 00
+0AE KEY: FF LENGTH: 00
SDWA FIRST RECORDABLE EXTENSION (SDWARC1)
+000 E2C3D3C4 D9D3E2D3 D6C1C4C5 D9404040 |SCLDRLSLOADER |
+010 40404040 40404040 40404040 00000000 | ....|
+020 00000000 00000000 00000000 00000014 |................|
+030 00000000 00000000 F5F7F5F2 01000001 |........5752....|
.
.
.
+1B0 00000000 00000000 00000000 00000000 |................|
+1C0 D1F5F040 40404040 |J50 |
SDWA SECOND RECORDABLE EXTENSION (SDWARC2)
+000 00000000 00000000 00000000 00000000 |................|
SDWA THIRD RECORDABLE EXTENSION (SDWARC3)
+000 00000000 00000000 00000000 00000000 |................|
+010 00000000 00000000 00000000 00000000 |................|
SDWA FOURTH RECORDABLE EXTENSION (SDWARC4)
+000 00000000 84000000 00000000 84378000 |....D.......D...|
+010 00000000 00000020 00000000 0000FC03 |................|
+020 00000001 008FD098 00000000 00FD5750 |......}Q.......&|
+030 00000000 00000003 00000001 00F52C00 |.............5..|
.
.
.
+150 00000000 00000000 07041000 80000000 |................|
+160 00000000 012F902E |........ |
SDWA FIFTH RECORDABLE EXTENSION (SDWARC5)
+000 00000000 00000000 00000000 00000000 |................|
+010 00000000 00000000 00000000 00000000 |................|
+020 00000000 00000000 00000000 00000000 |................|
+030 00000000 00000000 00000000 00000000 |................|
.
.
.
+090 00000000 00000000 00000000 00000000 |................|
ERRORID
+000 02F50056 00970009 BD27 |.5...P.... |- TYPE: SOFTWARE RECORD
- Indicates that the detail edit report is for an SDWA-type record.
- REPORT DATE
- Indicates the date on which the EREP report was created.
- ERROR DATE
- Indicates the date on which the error occurred.
- TIME
- Indicates the time, as local, at which the error occurred.
- JOBNAME
- If the jobname is NONE-FRR, the error being recorded occurred in system or subsystem code covered by a functional recovery routine (FRR).
- SYSTEM NAME
- Indicates the name of the system where the SDWA-type record was created.
- ERRORID
- Allows you to coordinate diagnostic information from logrec, the
console log (SYSLOG), and system dumps. The ERRORID is a concatenation
of the following:
- SEQ
- A unique number assigned to each error. The sequence number indicates
the order of the errors, but the records might not be listed in order.
It is important to scan all entries and examine the sequence numbers
to understand which error occurred first.
You might find the same sequence number used in more than one entry when several recovery routines, as a result of percolation, get control and request recording for the same error; however, the error time stamp will be different.
- CPU
- The internal identification number of the central processor that the failing process was running on at the time the error occurred. Use information from the system trace table about this CPU to learn more about the error.
- ASID
- The address space identifier (ASID) of the current, or home, address space at the time the error occurred.
- TIME
- Indicates the time of the error.
- PIDS/... RIDS/... AB/... PRCS/...
- Use this symptom string to do a structured search of any IBM® database.
- PROGRAM ID
- The program ID (PID) indicates the product and the component where the error occurred. For IBM products, see the tables in z/OS MVS Diagnosis: Reference that list the products and components. For non-IBM products, see the appropriate vendor-supplied documentation.
- LOAD MODULE NAME
- Indicates the load module in control at the time of the error.
- CSECT NAME
- Supplied by the recovery routine that obtained control for the error. See the PSW for more information.
- SYSTEM ABEND CODE
- Indicates what system or user completion code was issued by the system, application, or component. See z/OS MVS System Codes for information about system abend codes. See the appropriate product documentation for user abend codes.
- ABEND REASON CODE
- Indicates the reason code, when available, associated with a system or user abend code.
- RECOVERY ROUTINE CSECT NAME
- Indicates the recovery routine that was given control to handle the error condition.
- PSW
- Indicates the program status word (PSW) at the time of the error.
If the software record is an SVC 13, the address in the second half of the PSW indicates the address of the module that detected the error. You need to find the caller of that module. The caller's address will reside either in register 14, or, if register 14 points to module IEAVEEXP, use the STATUS section of the software record to determine the caller. In the STATUS section, the interrupt code will indicate the last SVC that was issued.
If the software record is a program interrupt, the address in the second half of the PSW usually points to the failing module.
- FAILING INSTRUCTION TEXT
- Contains 12 bytes of the instruction stream at the time of the error, including the actual instruction that caused the abend. Starting at the end of the sixth byte, subtract the instruction length to indicate the failing instruction. In the preceding example, the failing instruction is X'0A0D'.
- THE ERROR OCCURRED WHILE . . .
- Provides information about the system environment at the time of error, indicating what type of routine was in control, whether locks were held, and whether supervisor FRRs were set at the time of the error.
- STATUS
- The PSW and registers that follow come from the request block (RB) associated with the ESTAE recovery routine that obtained control for the error. Using the information indicated will enable you to determine the program that was running at the time of the error. This information included in the STATUS section does not appear when an FRR handles recovery.
- RECOVERY ROUTINE ACTION
- Describes the recovery action performed or requested to be performed by the recovery routine. In the preceding example, an SVC dump was not requested. There are times, however, when the recovery routine will request an SVC dump. If SVC DUMP SUCCESSFULLY STARTED appears in this section, the error identifier (ERROR ID) appears in the SVC dump and in message IEA911E as it appears in the logrec error record.
- HEXADECIMAL DUMP
- Provides an unformatted hexadecimal dump of the SDWA control block. Depending on an indicator in the SDWA, which is set by the recovery routine generating the record, the SDWA is displayed in hexadecimal; EBCDIC text; or key, length, and data format.
- VARIABLE RECORDING AREA (SDWAVRA)
- Provides component-specific information. Using the information
in the PROGRAM ID field, determine the component. For IBM products, see z/OS MVS Diagnosis: Reference for
diagnostic information related to system components.
The SDWAVRA can optionally be mapped in a key-length-data format. Recovery routines use the SDWAVRA to construct messages and provide data that often contains valuable debugging information. Some MVS™ recovery routines use the key-length-data format to provide standardized diagnostic information for software incidents. This formatted information allows you to screen duplicate errors.
Constants for the key field have been defined to describe data, such as: return and/or reason codes, parameter lists, registers, and control block information. For example, a key of X'10' indicates a recovery routine parameter area. The SDWAVRAM bit (in the fixed portion of the SDWA) indicates that the SDWAVRA has been mapped in the key-length-data format as described by the IHAVRA mapping macro.
For the format of the SDWA, including a description of the keys, see z/OS® MVS Data Areas in z/OS Internet library.
- SDWA RECORDABLE EXTENSIONS
- In addition to the SDWA standard area and the SDWAVRA, the SDWA
recordable extensions also contain valuable debugging information,
as follows:
- SDWARC1 (recording extension 1) contains additional component service data (such as the component ID, the component name, the address of the TCB representing the task that incurred the failure, the control registers, original completion code and reason code, linkage stack pointer, and translation exception access register number).
- SDWARC2 (recording extension 2) contains additional I/O machine check data (such as the machine check interruption code).
- SDWARC3 (recording extension 3) contains locking information (such as the locks to be freed, and the addresses of lockwords).
Note: The SDWA that is in the logrec buffer is a compressed SDWA in which the recordable extensions start directly after the used portion of the SDWAVRA. The SDWAURAL field contains the length of the SDWAVRA.