Jesse 1 Robinson wrote: >I'm posting this here because I was asked too. It's beyond crazy. As I >indicated earlier, we are trying to reduce spool full conditions by limiting >job output via ESTLNCT. Yesterday we set the limit on one system like this: >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.
What were the old values of NUM and INT? >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. The output message appears in the job log even before the >first step executes! Check if you have any wacko JES2 exit(s)... Any limiting statements in that job itself? >We ran the job in a different class with a different job name. Always the same >message. You said you changed it on one system. What happens on the other system(s)? >Does this make sense to anyone?!? No. My users will certainly jump up and down if that happens to their jobs... Groete / Greetings Elardus Engelbrecht We have now an extreme cold front in South Africa, it is so extremely cold, when I tried to get money from an ATM, the bank said my account is Frozen! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
