The following parameters are used to select the records for EREP to use: Parameter Description CPU=({nnnnnn|Xnnnnn|XXnnnn}.model [, …]) Processor serial and machine type numbers. Use only the records associated with this particular processor. nnnnnn – the six-digit hexadecimal CPU ID number. It defines a single processor in an n-way central […]
Next are a few examples of Jobs to list information from the Logrec Data Set: 1. Detail Edit Report This job generates detail edits and summaries of all software and operational records: //EREPRPT1 JOB,MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID //REPORT1 EXEC PGM=IFCEREP1,PARM=’CARD’ //ACCIN DD DSN=MVS.LOGREC.HISTORY,DISP=SHR //DIRECTWK DD UNIT=SYSDA, // SPACE=(CYL,5,,CONTIG) //EREPPT DD SYSOUT=A,DCB=BLKSIZE=133 //TOURIST DD […]
The following parameters are used to request reports from EREP: Parameter Description EVENT=Y or N Produces a three-part event history report that lists errors in chronological order. Shows how often errors occur and in what order. Used to establish a pattern and identify problems. No is the default value. PRINT= […]
By creating a history file and then running all the reports against that file, the Systems Programmer ensures that all of the reports are using the same set of records. //LOGRECHS JOB CLASS=A,MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID //*—————————————————————— //* COPIES SYS1.LOGREC TO HISTORY FILE MVS.LOGREC.HISTORY //*—————————————————————— //HISTORY EXEC PGM=IFCEREP1,REGION=1024K, // PARM=’ACC,ZERO=N’ //SERLOG DD DISP=(OLD,KEEP),DSN=SYS1.LOGREC […]
It’s not uncommon for the SYS1.LOGREC dataset to fill up. Although you should dump the content of the SYS1.LOGREC to DASD or Tape to keep that information for future use (if you need to analyse a problem), you sometimes may simply wish to clear all its content and re-initialize it. […]
Copyright © 2024 Rui Miguel Feio