JES parameter that controls the HASP375 (ESTIMATED BYTES or LINES EXCEEDED) message

Products

• View
• Dispatch Output Mgmt
• Bundl
• Spool
• XCOM Data Transport - z/OS

Issue/Introduction

- Which JES initialization parameter controls the $HASP375 (ESTIMATED BYTES EXCEEDED) message? 

- Which JES initialization parameter controls the $HASP375 ((ESTIMATED LINES EXCEEDED)) message? 

Environment

z/OS

Resolution

As per the IBM z/OS JES2 Initialization and Tuning Reference...

- The ESTBYTE statement specifies the amount of spool space used before the $HASP375 (ESTIMATED BYTES EXCEEDED) message is initially written to the operator, the interval at which it is repeated, and the action JES2 takes if the output exceeds the estimate. Your installation can provide an output overflow installation exit routine (Exit 9) to override this statement on a per-job basis.

Note: If changed by the $T command after a job was submitted, the ESTLNCT parameters are affected as follows:
          - the INT= and OPT= values are effected immediately and are reflected during job execution
          - the NUM= value remains equal to the value when the job was submitted. It takes affect for only newly submitted jobs.

ESTBYTE - Estimated Spool Utilization for Output Exceeded

Format Description for ESTBYTE

Parameter Description for ESTBYTE

- The ESTLNCT statement specifies the default estimated print line count for a batch job, the interval at which the $HASP375 (ESTIMATED LINES EXCEEDED) message is written to the operator, and the action JES2 takes if the output exceeds the estimate. Your installation can provide an output overflow installation exit routine (Exit 9) to override this statement for each batch job processed.

ESTLNCT - Default Estimated Print Output and Options

Format Description for ESTLNCT

Parameter Description for ESTLNCT

 

Parent topic:
JES2 initialization statement descriptions