On Tue, 11 Aug 2009 14:51:52 +0100, Beesley, Paul
<[email protected]> 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 ...
>
<snip>
1) Have you looked into what those MDR records are?
2) How big is your LOGREC data set and why not just make it large
enough to handle whatever the "normal" activity would be PLUS
a large fudge factor for abnormal activity?
3) Have you considered using the system logger for LOGREC since you
wouldn't run into a full condition for some unexpected abnormal
activity (unless your DASD pool fills up)?
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[email protected]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
----------------------------------------------------------------------
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
