I think I shared this before, to the group, but here is how we handle Spool automation when we hit the 80% threshold, these IBM SA passes get executed about 1 or 2 minutes apart until the shortage is relieved. Since we added passes 1-3 we've not many spool events, other than the occasional production job that goes wild because a developer forgot to take a Display statement out of their cobol program. These automation passes do nothing to running production jobs, intentionally.
1 MVS $CJ(E*,T*),SPOOL=(%>10),PURGE >>cancel & purge test jobs taking 10% or more of spool - gets the bad one if they exist. 2 MVS $PJ(E*,T*),SPOOL=(%>5) >>purge test jobs taking 5% or more of spool, gets the abusers if they exist 3 MVS $PJ(E*,T*),SPOOL=(%>2) >>purge test jobs taking more than 2% of spool 4 MVS $PO JOBQ,READY,A>14 >> purge all output that is not held older than 14 days 5 MVS $PO TSU(*),ALL,A>1 >>purge TSO output older than 1 day 6 MVS $PO STC(*),ALL,A>10 >>purge STC output older than 10 days. 7 MVS $PO JOBQ,Q=D,A>1 >>purge output class D (dumps) older than a day. 8 MVS $PO JOBQ,ALL,A>10 >>purge anything older than 10 days. We archive prod output to SAR. All the while, our operations staff is paging out our on call for assistance. In the event spool goes 100%, we have separate automation that will start preformatted spool volumes that are drained while problem determination is going on. _____________________________________________________________________________________________________ Dave Jousma AVP | Director, Technology Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jesse 1 Robinson Sent: Monday, November 9, 2020 1:56 PM To: [email protected] Subject: JES2 message $HASP375 Estimate exceeded **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** We've had some cases of a job taking over the spool. In researching a solution, we've noticed that message $HASP375 varies in ways we don't understand. Doc for the message looks like this: >--jobname--ESTIMATE EXCEEDED BY--nnn--+-LINES--+---------------> +-CARDS--+ +-KBYTES-+ '-PAGES--' >--+-------------+--------------------------------------------->< '-xxx--%SPOOL-' We don't understand why the overage is sometimes reported as Lines, Cards, Kbytes, or Pages. Why does JES2 pick one descriptor or another? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office <===== NEW [email protected]<mailto:[email protected]> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
