EREP presents information from the logrec software error records
in five reports.
- Detail Edit Report for an Abend
- The system obtains most of the information for an abend logrec
error record from the system diagnostic work area (SDWA). The report
contents are:
- Record header: report type (SOFTWARE RECORD), system, job name,
error identifier (ERRORID), date, and time
- Search argument abstract
- Serviceability information
- Time of error information
- Status information from the request block
- Recovery environment
- Recovery routine action
- Hexadecimal dump of the SDWA, including the variable recording
area (VRA)
Figure 1 shows how to generate
detail edits and summaries of all software and operational records:
Figure 1. Example:
Printing a detail edit report//STEP7 EXEC PGM=IFCEREP1,PARM='CARD'
//ACCIN DD DSN=EHISTORY,DISP=SHR
//DIRECTWK DD UNIT=SYSDA,
// SPACE=(CYL,5,,CONTIG)
//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133
//TOURIST DD SYSOUT=A,DCB=BLKSIZE=133
//SYSIN DD *
PRINT=PS
TYPE=SIE
HIST
ACC=N
ENDPARM
- Detail edit report for a symptom record
- The system obtains most of the information for a non-abend logrec
error record from the symptom record identified in the SYMREC macro.
A programmer can build the symptom record using the SYMRBLD macro.
The report contents are:
- Record reader: report type (SYMPTOM RECORD), system, date, and
time
- Search argument abstract
- System environment
- Component information
- Primary and secondary symptom strings
- Free-format component information
- Hexadecimal dump of the symptom record
- System summary report
- The report summarizes errors for each of your installation's principle
parts, or subsystems: processors, channels, subchannels, storage,
operating system control programs, and I/O subsystems. The report
contents are:
- Record header: report type (SYSTEM SUMMARY), system, date, time
- Total errors and errors for each processor for the following types
of errors:
- IPL
- Machine check
- Program error
- End of day
- Identifications for processors in the report
- Event history report
- The report shows the error history: the frequency, order, and
pattern of errors. The report contents are:
- Record header: report type (EVENT HISTORY)
- Abstracts for abend and non-abend logrec error records in chronological
order
- Totals of the types of logrec error records for the system and
for each processor
The
JCL shown in
Figure 2 defines a two-step
job. The first step prints an event history report for all logrec
data set records. The second step formats each software, IPL, and
EOD record individually. The event history report is printed as a
result of the EVENT=Y parameter on the EXEC statement of the first
step. It can be a very useful tool to the problem solver because
it prints the records in the same sequence they were recorded and
therefore shows an interaction between hardware error records and
software error records.
Figure 2. Example: Printing an event history report//EREP JOB MSGLEVEL=1
//EREPA EXEC PGM=IFCEREP1,PARM='EVENT=Y,ACC=N',
// REGION=256K
//SERLOG DD DSN=SYS1.LOGREC,DISP=SHR
//TOURIST DD SYSOUT=A
//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133
//SYSIN DD DUMMY
//EREPB EXEC PGM=IFCEREP1,PARM='TYPE=SIE,PRINT=PS,ACC=N',
// REGION=256K
//SERLOG DD DSN=SYS1.LOGREC,DISP=SHR
//TOURIST DD SYSOUT=A
//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133
//SYSIN DD DUMMY
/*
- Detail summary report
- The report summarizes information about data in logrec error records.
The report contents are:
- Record header: report type being summarized
- Summary information and counts
The example in
Figure 3 shows how
to generate detail summaries of all I/O errors.
Figure 3. Example: Printing a detail
summary report//STEP6 EXEC PGM=IFCEREP1,PARM='CARD'
//ACCIN DD DSN=EHISTORY,DISP=(OLD,PASS)
//DIRECTWK DD UNIT=SYSDA,
// SPACE=(CYL,5,,CONTIG)
//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133
//TOURIST DD SYSOUT=A,DCB=BLKSIZE=133
//SYSIN DD DSN=EREP.PARMS(STEP6),
// DISP=(OLD,PASS)
// DD DSN=EREP.CONTROLS,
// DISP=(OLD,PASS)
PRINT=SU
TYPE=DOTH
DEV=(N34XX,N3704,N3705,N3720,N3725,N3745)
HIST
ACC=N
ENDPARM