Allan, Good points.
So where can job output be controlled. ESTLNCT Line Count based on the HASP375 message EXIT09 /*JOBPARM LINES= SYSOUT statements can reference line counts as well /*OUTPUT statements EXIT43(?) OPT=0 Should have been honored if the system it ran on has an OPT=0 when the $DESTLNCT command is issued. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Staller, Allan > Sent: Wednesday, October 16, 2013 9:14 AM > To: [email protected] > Subject: Re: Abend S722 & $HAPS375 > > Code in user exits checking job class and taking different actions? > > IEFUSI/IEFUSO/IEFUJI,.... > > <snip> > This weekend we converted some jobs from one jobclass to another (JES2) – the > jobclass definitions are identical save for one is WLM managed and the other > isn’t. > We’d already converted a substantial amount of jobs to this class months ago > but > this weekend SOME of the weekly DASD defrag jobs abended with a S722 > following a $HASP375 Estimated Lines Exceeded. I can’t track down what is > triggering these jobs to abend so hoping someone can point me in the right > direction. > ....remainder snipped > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email to > [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
