Restarting JES3 on the global main

To restart JES3 after an orderly shutdown or after JES3 ends abnormally, use hot start or warm start initialization. Table 1 summarizes the characteristics of global processor starts.

Before you restart JES3, be sure that all spool data sets that were available to the system before JES3 ended are still available (unless you are using the procedures to replace, remove, add, or delete a spool data set). The volumes containing the data sets do not have to be mounted at the same addresses. Also, be sure that any spool data sets you are using that were not used during the last start or restart are available to the system.

After initialization processing is complete, you can restart the local mains, and then proceed as follows. If:

You entered the *F,Q,H command to put all jobs in hold status when stopping JES3, be sure to release the jobs by entering the *F,Q,R command.
The system ended abnormally because of an equipment or system failure, return jobs that were running on a processor at the time of the failure to the appropriate programmer; when a job does not end correctly, the programmer might have to take corrective actions before the job can be restarted.
You used JES3 commands to change system parameters before JES3 ended and you are restarting JES3 with a hot start, a hot start with refresh, or with a warm start that does not include the changes in the initialization stream, certain changes are lost.
Commands that remain in effect after a restart shows the command changes that remain in effect across a warm start and a hot start. To reinstate changes to parameters that did not remain in effect across the restart, enter the appropriate JES3 commands.

You can restart job scheduling by entering the *START,JSS command. All jobs that were waiting to run and completed jobs that were waiting for output processing when JES3 ends are unaffected by the restart; they continue processing as though no restart had occurred. If you did not IPL MVS™ before restarting JES3, all jobs processing when JES3 ended also continue processing. If you performed an IPL, JES3 examines jobs that were in processing for their MVS restart options. Jobs that cannot be restarted are processed according to their JES3 failure options (on the job's //*main JCL statement or the system default). If the system failed, resubmit any jobs being read into the system at the time of the failure.

If a functional subsystem was ended because of an IPL of the main, JES3 restarts the FSS automatically.