An autostart job is a batch job doing repetitive work, one-time initialization work that is associated with a particular subsystem, initializes functions for an application, or provides centralized service functions for other jobs in the same subsystem. An autostart job in the controlling subsystem can be used to start other subsystems (as does the IBM-supplied controlling subsystem). The autostart jobs associated with a subsystem are automatically started each time the subsystem is started.
Since all autostart jobs are started when the subsystem starts, the value specified for the maximum number of jobs in the subsystem does not prevent the autostart jobs from starting. If the maximum number of jobs in the subsystem is exceeded, no other jobs can be started. When enough autostart jobs have completed so that the number of jobs running is below the maximum activity level, other jobs in the subsystem can start.
The job description that is used for an autostart job is specified using the Add Autostart Job Entry (ADDAJE) command. When the subsystem is started, the job operates under the user profile name in the specified job description. You may not specify the job description which contains USER(*RQD). Because the autostart job operates under the user profile that is specified by the job description, you need to control who is allowed to change the job description.
If more than one autostart job is specified for a subsystem, all autostart jobs are started immediately rather than one followed by another. If the maximum number of jobs of the subsystem is exceeded, no other jobs can be started in the subsystem until enough autostart jobs have completed so that the number of jobs running is below the maximum activity level.