Limiting considerations

When automatic command processing is active, commands entered at system speed (rather than at operator speed) may congest the system. In turn, system response to the commands may tend to flood the console with the response messages.

If your installation is experiencing difficulty either with commands congesting the system or messages flooding the console, reevaluate the mix of commands submitted with automatic command processing and try some changes.

Automatic command processing can also end prematurely under the following conditions:

If the operator enters the $Z A command to halt automatic command processing and then lets 24 hours or more elapse without restarting it.
If the operator specifies a start time for automatic command processing that is earlier than the current time, the command will be issued and then canceled.
If the operator specifies a start time that does not include an hour specification, but only a minute specification, the command will be canceled without being issued.
If the system becomes so congested that the automatic commands are delayed approximately 5 minutes.

When an automatic command specifying T= has been executed, it must be reentered if it is to be executed at a later time. Make sure the operator fully understands the procedures for using automatic command processing. They are fully outlined in z/OS JES2 Commands.