Messages when output limit exceeded in a non-APPC scheduling environment

In a non-APPC scheduling environment, you can request that the system send a warning message when the limit is exceeded by using the JOB statement parameters and installation defaults described in Messages when output limit exceeded in an APPC scheduling environment. In addition, you can code a BYTES, CARDS, LINES, or PAGES parameter on a JES2 /*JOBPARM statement or on a JES3 //*MAIN statement to limit output for a job.

When you code the WARNING subparameter on the //*MAIN statement, the system sends a warning message to the operator when a job's output exceeds the limit you have specified.

When you code an output limit on the /*JOBPARM statement, the system sends a warning message to the operator when:

The job's output exceeds the limit you have specified, and
The warning option has been specified at JES2 initialization as the installation default.

Defaults and multiple messages: If you do not code an output limit on the JOB statement, the system uses the limit coded on the //*MAIN statement or the /*JOBPARM statement. If you do not code a //*MAIN or a /*JOBPARM statement, the system uses the installation default limit specified at JES initialization.

If you code multiple //*MAIN statements specifying output limits for a job, or you code a limit and WARNING subparameter on the JOB statement as well as the //*MAIN statement, the operator will receive multiple warning messages.