Replacing a spool data set

You can replace or delete a spool data set using the *MODIFY CONFIG command, a hotstart with refresh, or a warm start using the procedures that follow. You can create the new data set on a volume or device type that is different than the one being replaced. You can also change the size of the data set and redefine the single track table (STT) range using the STT or STTL parameter on the TRACK or FORMAT initialization statement.

When you replace a spool data set, JES3 cancels all jobs with data on the replaced spool data set. If the replaced data set contains STT records, JES3 might lose information that could result in the loss of jobs in the system. STT records include information such as the status of devices, DJC network data, deadline queue data, volume unavailable data, dynamic allocation checkpoint data, output service checkpoint data, JESNEWS, device fencing data, virtual unit status, GMS status, and FSS checkpoint data. If STT data is lost, JES3 issues messages that allow you to take the appropriate recovery actions.

You can migrate STT data to a different set of spool data sets by running the *F Q,DD=ddname,DRAIN command. To migrate job data from the affected spools, you can use the *CALL,DJ dump jobs facility to offload the data to different spool data sets.

As a last resort, you can cancel all jobs on a specific data set using the *F Q,DD=ddname,CANCEL command. After you cancel the jobs, the user can resubmit them. You can then replace the spool data set at a convenient time; you must use the same ddname for the new spool data set that was used for the old spool data set.