Logrec is a z/OS dataset which records information about events, such as hardware problems, and software abends. Information is written to the dataset even though the information may have been suppressed elsewhere.
JCL to print it
//IBMPEREP JOB (ACCT),'PRINT LOGREC',CLASS=A,MSGCLASS=H
//STEP EXEC PGM=IFCEREP1,PARM='CARD'
//SERLOG DD DISP=SHR,DSN=SYS1.S0W1.LOGREC
//DIRECTWK DD UNIT=SYSDA,SPACE=(CYL,10,,CONTIG)
//EREPPT DD SYSOUT=A,DCB=BLKSIZE=133
//TOURIST DD SYSOUT=A,DCB=BLKSIZE=133
//ZERLOG DD SYSOUT=A,DCB=BLKSIZE=133
//SYSIN DD *
PRINT=PS
ACC=N
ZERO=N
ENDPARM
//
To print and clear specify ZERO=Y.
The command syntax is given here.
Example output
IPL record
IPL RECORD EDIT AND PRINTING SECTION
DAY YEAR HH MM SS TH
DATE -122 26 TIME -06 05 01 52
MODEL - 1090 CPU SERIAL NO. - 011238
MVS/ESA V7 R3
IPL REASON CODE - DF DEFAULT -U-
SUBSYSTEM ID - 00 SUBSYSTEM NAME - NULL
HIGHEST STORAGE ADDRESS 7FFFFFFF
LAST ACTIVITY INFORMATION :
DAY YEAR HH MM SS TH
DATE -121 26 TIME -19 14 13 68
END OF IPL RECORD
3270 termination
DEVICE NUMBER: 000703 DAY YEAR JOB IDENTITY: VTAM
DEVICE TYPE: 3277
MODEL: 1090 HH MM SS.TH
ERROR PATH: EF-0703 CPU ID: 111238 TIME: 19 16 26.42
RECORD IS: TEMPORARY
MODE IS: 370XA
---UNIT STATUS---- SUB-CHANNEL STATUS
....
DEVICE DEPENDENT DATA
TYPE OF RECORD: CLOSEDOWN (X'20')
TERMINAL NAME: LCL703 SIO CNTR: 00000003 TEMP. ERRORS: 00
Software abend
See Where’s my dump?
How often should I clear it?
Periodically you should archive the data, so you can later do trend analysis, such as which disks are having more I/O problems than usual.
When logrec fills up, your automation can trigger a job to copy the logrec dataset, and clear it.
One thought on “Processing LOGREC”