Articles

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  […]

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. […]

First of all and before defining a Logrec log stream, the Systems Programmer should make sure that the system in question was IPLed with a Logrec data set initialized by IFCDIP00. If this is not the case, you cannot change the Logrec recording medium from LOGSTREAM to DATASET using the […]