Also what about the "LINES", "BYTES" parameters on the JOB card, where
you can not only specify the limit for the job as a whole but the action
to take (CANCEL, DUMP, WARNING) when that limit is reached? I believe
the default action for the JOBPARM LINES exceeded is just to WARN, but
there are all sorts of available provisions for customizing system behavior.
I can't remember whether we had to define a JES2 exit or just change
defaults in the JES2PARM member, but it is certainly possible (and
probably wise) to set up a system default for the maximum SYSOUT a job
in your shop is allowed to generate without termination, and with proper
sizing of SPOOL space you can define that at a value that is less than
will kill your SPOOL space and more SYSOUT than any rational person who
knows what he is doing could need. And, in the highly unlikely event a
legitimate requirement for more output is encountered, that can still be
allowed by an explicit specification of a larger but still finite SYSOUT
limit value for that specific job.
And as John points out, an OUTLIM on an individual DD can be used to
enforce a limit on a specific SYSOUT DD, while still being able to
generate additional SYSOUT for the JOB, like maybe for a diagnostic DUMP.
Joel C. Ewing
On 03/11/2014 02:14 PM, John McKown wrote:
> I use OUTLIM on the individual SYSOUT= statements to force an S722. But
> that can be PITA.
>
>
> On Tue, Mar 11, 2014 at 1:54 PM, Barry Merrill <ba...@mxg.com> wrote:
>
>> It appears that there is no JCL option for an individual job that
>> can be enabled to cause the job to terminate when
>> /*JOBPARM LINES=10
>> is used and the job has produced 10,001 lines of output.
>>
>> I can only find references to JES2 EXIT 9 where the decision
>> is made for lines exceeded.
>>
>> I never needed this before, but then I never completely filled
>> my spool before with a runaway job.
>>
>> The circumvention was to point SYSOUT file to a CYL(1) disk
>> file and force the B37 ABEND to get control of the job and
>> to read the log messages.
>>
>> Barry Merrill
>>
>>
>> Herbert W. "Barry" Merrill, PhD
>> President-Programmer
>> MXG Software
>> Merrill Consultants
>> 10717 Cromwell Drive
>> Dallas, TX 75229
>> ba...@mxg.com
>>
>> http://www.mxg.com - FAQ has Most Answers
>> ad...@mxg.com - invoices/PO/Payment
>> supp...@mxg.com - technical
>> tel: 214 351 1966 - expect slow reply, use email
>> fax: 214 350 3694 - prefer email, still works
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>
>
>
--
Joel C. Ewing, Bentonville, AR jcew...@acm.org
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
