Recovering from Output Writer FSS Failures

JES3 tracks each data set sent to an output writer functional subsystem (FSS) until the FSS notifies JES3 that it has printed the data set. If an FSS fails, JES3 reschedules all data sets that were printing at the time of the failure.

An output writer FSS can fail under any of the following conditions:

The operator reIPLs the system.
Operator commands cancel the FSS.
The last active writer in the JES3 global address space fails. In this case, the output writer FSS associated with it also ends.

If an FSS fails, JES3 also fails all of the writers that are in the JES3 global address space and that sent work to the FSS.

In all of these cases, JES3 recovers the work the FSS was processing and reschedules it.

To restart the FSS, use operator commands to start a writer dynamic support program (DSP) for a page mode device. The writer DSP restarts the output writer FSS.

If you define more than one device to run under the control of an output writer FSS, and one of those devices fail, the FSS remains active and the remaining devices continue processing work. However, if the failed device is the last active device running under control of an output writer FSS, then JES3 cancels the FSS.

After a hot start, output writer FSSs continue running in their own address spaces unless:

The FSSDEF initialization statement specified TERM=YES.
The operator IPLs the processor on which the FSSs were operating.

If an output writer FSS runs out of work before the JES3 global address space restarts, the output writer FSS remains idle until the restart. After the hot start, JES3 restarts the writer DSPs, both hot writers and dynamic writers, associated with output writer FSSs that were active before the hot start. The writer DSPs reestablish contact with the output writer FSSs and work continues as before the hot start.