The EST Byte, Line, Page can be dynamically changed. The simplest way to avoid an IPL (and JES2 just stops when spool is full - but will respond to commands like PURGE)
Is to cycle the STC, add another spool volume, or see what is really going on. If the STC is filling up spool, it needs to be determined why. We have automated the HASP050 / HASP375 message to send emails and alerts when some of the JES2 functions are impacted (BERT, SPOOL, JNUM, etc.) My understanding is the IEFUSO exit can cancel an STC if it exceeds its limits. You can code the STCCLASS statement in JES2 and allow the IEFUSO to do its job. You can also use automation tools to monitor for HASP375, HASP050 or other You can use products like z/OSEM or EASYEXIT (DTS Software) to control your jobs names (STC, TSU, or JOB) for determining final action. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of George Henke > Sent: Thursday, June 08, 2017 1:59 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Does the JES2 ESTBYTE parm limit STC or just batch output? > > Just averted a near disaster, a mid-day IPL of 4 LPARs, with a STC filling up > the spool with 10B bytes of data because the ESTBYTE limit was not turned on > for termination, OPT=1. > > But would it have done anything anyway for a STC or does it just apply to > batch and APPC. > > The manual is silently ambiguous on this. > > If anyone has had success limiting STC output so, please let me know, else it > will probably be JES2 Exit 20. > > -- > George Henke > (C) 845 401 5614 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
