Anthony Fletcher wrote: >Has anyone heard of a way to suppress generation of LOGREC records?
No, not as far as I know. >We recently had a situation where an application was abending repeatedly and >generating LOGREC records. This manifested itself as very HIGH CPU use in >MSTJCL00 but because the LOGREC records are going to the LOGGER they were >being generated so fast that it was impossible to get to look at one. Just stop/cancel the application and have a look at the records using EREP while looking in SYSLOG and joblog at that same same time. >We were wondering whether there was a way to temporarily tell the LOGREC >processor to stop generating records. We did consider switching LOGREC back to >DASD records which would fill up, but suspected that the attempt to create >records would still use a lot of CPU so would prefer a setting that told the >LOGREC writer to not even try. You can create a LARGE LOGREC dataset just for diagnostics (Use EVENT=Y to quickly see what happened) and then switch back to your Log stream. Are you getting thousand records? If so, what type of records? Last question: Are you also getting dumps and dumps? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
