OK. Let me add a little more background explanation to my previous post. Naturally, if the output is from a loop or other error you don't want to just permit it. But sometimes that is not the case. There was a case a few years ago, since fixed by APAR (I don't remember exactly which product took the APAR). Ordinary size print jobs through Infoprint Server started getting S722 abends. The reason was that the output was all being counted together because all of the output came from aopoutd daemon running in Unix for all the jobs. The S722 abends were not because of the output of the individual jobs, but because of the accumulated output of all the jobs processed. The fix was things like the _BPX_UNLIMITED_OUTPUT environment variable so that the aopoutd daemon could continue to process the jobs without every job getting S722 because the limit had been passed. --Roger
On Fri, Jul 5, 2019 at 8:36 AM Roger Bolan <[email protected]> wrote: > See page 124 section 5.4 here > http://www.redbooks.ibm.com/redbooks/pdfs/sg246377.pdf > Setting ESTBYTE OPT=0 may help. > If Unix is involved then _BPX_UNLIMITED_OUTPUT=YES might also help. > --Roger > > On Fri, Jul 5, 2019 at 7:46 AM raji ece <[email protected]> wrote: > >> One of our job is abending with RC S722 and the error show the maximum >> outlimit execeed. We have coded lines=999999(Maximum limit) and run but >> getting same error. Current zos level is 1.13. any idea? >> >> ---------------------------------------------------------------------- >> 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
