Distinct different limits may be set (ESTBYTES, ESTLINES, ESTPAGES) that
are independently checked.  The exact message received depends on which
limit is reached.  If the setting allows the job to continue, you can
get a succession or these messages if the job continues to produce more
output.   Production jobs would generally be allowed to continue until
some human could evaluate whether the behavior warranted cancellation.

Many short lines take up less space, which is why you may want a
separate limit based on bytes, which would be more directly proportional
to spool space used.

To catch program errors that waste paper with unintended page ejects or
unanticipated number of print pages you use ESTPAGES.  To count pages,
the spool output must contain standard carriage control bytes that
includes page ejects to indicate the start of a new page, or there must
be a LINECT parameter to force a page overflow after a fixed number of
lines.   A program might not be designed to write carriage control
bytes, or a looping program may output the same line repeatedly with no
page ejects, which is why you need ESTBYTES or ESTLINES limits in
addition to ESTPAGES limits.

Whatever an installation defines as default values for these limits,
they can be overridden by explicit JCL in production jobs where that is
appropriate.   There obviously should also be installation standards
that disallows routine or arbitrary use of those overrides in ways that
would defeat the purpose of using those limits to warn of inappropriate
or erroneous program behavior.
    Joel C. Ewing

On 11/9/20 12:55 PM, Jesse 1 Robinson wrote:
> We've had some cases of a job taking over the spool. In researching a 
> solution, we've noticed that message $HASP375 varies in ways we don't 
> understand. Doc for the message looks like this:
>
>> --jobname--ESTIMATE EXCEEDED BY--nnn--+-LINES--+--------------->
>                                        +-CARDS--+
>                                        +-KBYTES-+
>                                        '-PAGES--'
>
>> --+-------------+---------------------------------------------><
>    '-xxx--%SPOOL-'
>
> We don't understand why the overage is sometimes reported as Lines, Cards, 
> Kbytes, or Pages. Why does JES2 pick one descriptor or another?
>
>
> .
> .
> J.O.Skip Robinson
> Southern California Edison Company
> Electric Dragon Team Paddler
> SHARE MVS Program Co-Manager
> 323-715-0595 Mobile
> 626-543-6132 Office <===== NEW
> [email protected]<mailto:[email protected]>
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN


-- 
Joel C. Ewing

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to