Defining spool partition overflow

To provide for occasions when a requested spool partition is full, you can specify where each spool partition's overflow data should go. To do this, use the OVRFL parameter on the SPART initialization statement:

To specify that spool data directed to a particular spool partition should overflow into another named spool partition, specify OVRFL=name on the SPART statement that defines the requested spool partition.
To specify that spool data directed to a spool partition should overflow into the default partition, specify OVRFL=YES. This specification is also the default.
To specify that spool data directed to a spool partition should not overflow into another partition, specify OVRFL=NO. In this case, the requester waits until track groups within the requested partition become available.
The default partition cannot overflow. It always has the attribute of OVRFL=NO.

A spool partition that accepts overflow from another partition may, in turn, overflow into a third partition, and so on. This can continue until the overflowing spool data reaches a partition that allows no overflow.

SPART Initialization Statements — Example

    SPART,NAME=TSODATA,OVRFL=SMLBATCH
    SPART,NAME=SMLBATCH,OVRFL=YES
    SPART,NAME=DEFPART,DEF=YES
    SPART,NAME=BIGBATCH,OVRFL=NO

The TSODATA partition contains TSO output data, the SMLBATCH partition contains output data from small batch jobs, and the BIGBATCH partition contains output data from large batch jobs. If the TSODATA partition becomes full, the TSO output data overflows into the SMLBATCH partition. If the SMLBATCH partition becomes full, it overflows into the default partition, DEFPART. The default partition cannot overflow. Neither can the BIGBATCH partition, because its SPART statement specifies OVRFL=NO.

If an overflow partition begins running low on space, JES3 suspends job selection for jobs requesting that partition or for any partition that overflows into that partition. (The marg subparameter of the SPLIM parameter on the SPART initialization statement for that partition or on the BUFFER initialization statement defines when the partition is running low on space.) If an overflow partition reaches a critical space shortage, JES3 suspends all SYSOUT buffer processing for jobs requesting that partition or any partition that overflows into that partition. (The min subparameter of the SPLIM parameter on the SPART initialization statement for that partition or on the BUFFER initialization statement defines when the partition has a critical space shortage.)

Attention:

Avoid allowing too many partitions to overflow into the default partition. If the default partition begins running low or critically short on space, JES3 takes the same actions as for any overflow partition that runs low or critically short on space. With a critical spool space shortage, JES3 also prevents any new work from starting because the default partition has no room for a job's input data (SYSIN).
The initialization stream must not define a circular spool partition overflow.
Circular Overflow with SPART
```
    SPART,NAME=TSODATA,OVRFL=SMLBATCH
    SPART,NAME=SMLBATCH,OVRFL=TNYBATCH
    SPART,NAME=TNYBATCH,OVRFL=TSODATA
```
If the TSODATA partition overflows into the SMLBATCH partition, and the SMLBATCH partition overflows into the TNYBATCH partition, the TNYBATCH partition cannot overflow into the already-overflowing TSODATA partition. JES3 detects the circular overflow condition on the SPART statement for the TNYBATCH partition and changes the overflow specification to OVRFL=NO. If this situation arises in your initialization stream, use the *INQUIRY and *MODIFY commands to respecify the spool partition overflow.