Use prestart jobs to reduce the amount of time required to handle
a program start request. This topic discusses the most common tasks associated
with prestart jobs.
Start a prestart job
Prestart jobs typically start at the same time the subsystem is started. You manually start a prestart job when all prestart jobs have been ended by the system due to an error or were never started during subsystem start up due to STRJOBS (*NO) on the prestart job entry. To start a prestart job, use the character-based interface.
Queue or reject program start requests
If a program start request arrives when the current number of prestart jobs is less than the number specified in the MAXJOBS attribute on the prestart job entry, and none of the prestart jobs are available to handle the program start request, you have the option to have this new request rejected or queued.
End a prestart job
You can use the iSeries™ Navigator or the character-based interface
to end a prestart job and any associated inline data files for a prestart
job entry in an active subsystem. Jobs can be waiting for a request or can
already be associated with a request. Spooled output files associated with
the jobs being ended can also be ended or allowed to remain on the output
queue. The limit on the number of messages being written to each of the job
logs can also be changed.