On 13 June 2017 at 12:46, Jesse 1 Robinson <[email protected]> wrote:
> ESTLNCT NUM=20000,INT=20000,OPT=1 > > We changed NUM from the old value, but added OPT=1 to cancel the job with > no dump. On this system only, a particular job started getting S722 for no > apparent reason. It produces hardly any output at all. We looked at older > executions-including yesterday before the JES change-and it appears that > this job has *always* produced the output exceeded message but with no > abend because of OPT=0. Is it possible the job is printing a bazillion lines with no paper advance, or even just very short lines? In other words lots of lines occupying little actual space? > The output message appears in the job log even before the first step > executes! Now *that* is bizarre (and shoots down my theory, I think). Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
