Beesley, Paul wrote:
We run a job every day at 06:30 to clear LOGREC and write to a history
file ( JCL below ).
Every day without fail the following message is issued while the job is
running.
*IFB081I LOGREC DATA SET IS FULL,06.30.58,
DSN=SYS1.FIF2.LOGREC
When I check LOGREC, its full of MDR records for every DASD volume in
the known universe as at 06:30.
Why is this happening and how can I stop it ? There's not much point
clearing logrec only for it to fill up again with useless MDR records.
This caused us to have no valid logrec records for IBM the other day
after a system outage ...
//JS010 EXEC PGM=IFCEREP1,TIME=10,
// PARM='LINECT=60,ACC=Y,HIST=N,ZERO=Y,SYSUM=Y'
//SERLOG DD DSN=SYS1.FIF2.LOGREC,DISP=SHR
//ACCDEV DD DSN=SYS3.FIF2.EREPHIST,
// DISP=(NEW,CATLG,DELETE),
// SPACE=(2000,(3000,3000),RLSE),
// AVGREC=U,
// LRECL=2000,
// RECFM=VB
//DIRECTWK DD UNIT=SYSALLDA,SPACE=(CYL,(5,5))
//TOURIST DD SYSOUT=*
//EREPPT DD SYSOUT=*
//SYSIN DD DUMMY,DCB=BLKSIZE=80
IFCEREP1 downloads the MDR's at the time it runs (Z EOD also does this).
I think they also get downloaded if the counters overflow.
You should increase the size of you LOGREC or switch to the system
logger. If your LOGREC is full, and you don't want to loose the MDR's
you can run IFCOFFLD which dumps/clears LOGREC without downloading
the MDR's.
--
Richard
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
