Starting job scheduling *START,JSS

Function

You can start job scheduling after JES3 issues message IAT3100 notifying you that initialization processing is complete on the global:

IAT3100  JES3 xxxxx SYSTEM type START ON yyyy.ddd AS main

where xxxxx is the release level of JES3, type is COLD, WARM, or HOT. yyyy.ddd is the Julian date, and main is the JES3 name of the main.

Before starting job scheduling, you can use JES3 commands to cancel jobs, change the status of jobs, and change the status of devices. during a hot start with analysis, you can release jobs in spool hold status after reinstating a spool data set that contains data for the jobs, and you can vary devices online or offline. You can make adjustments for any system data that might have been lost during the restart. You can also make any changes to the system that were made before a hot start or a warm start but did not remain in effect after the restart. See Table 1 for a summary of the changes that remain in effect after a restart.

When you are satisfied that the system is ready to begin processing, enter a *START,JSS command to start job scheduling.

Syntax


>>-+-*START-+--,--JSS------------------------------------------><
   '-*S-----'

Result

After you enter the *START,JSS command, be sure the global is varied online to JES3. If it is not, issue the *MODIFY,V,main,ON command to vary the processor online. This ensures that the subsystem interface, the MVS™ system commands, and the system log are initialized. JES3 then issues the following message:

IAT2645     ***** main CONNECT COMPLETE *****

If you do not want the global to run jobs, you can now vary the main offline to JES3 scheduling with the *MODIFY,V,main,OFF command. At this point, you can resubmit any jobs that were canceled or whose processing was altered as a result of the restart.