Batch Job Process Chain

The diagram below shows the relationship between the user interface (Lawson Interface Desktop or Lawson Portal) and batch job programs.


Component	Description
lajs	The `lajs` program is the Lawson batch server. It runs under the subsystem and spawns `execjob`.
execjob	The `execjob` program is the job executor that manages the batch job.
larpgrts	The larpgrts service program, bound into the application programs, is the primary interface for the applications to the Environment.

The basic steps of the batch job process chain are very similar to those for the online program process chain.

A user accesses an application or Environment form to define the job parameters and submit the job. Depending on the user interface, either the lapm program or the IOS programs verify, through screen edits and the application programs, that the job’s parameters are valid. If they are not, the user receives an error message immediately and the job ends.
If the parameters are valid, lapm or IOS contacts lajs, the Lawson batch server.
lajs spawns execjob to manage the batch job.
lajs sends a message to the user confirming that the job was submitted.
execjob sends the data request to the appropriate application program and waits to obtain an exit status for the job.
The application program edits the parameters. If the parameters are valid, it retrieves the data and calls the appropriate print routines.
If the parameters are invalid, it returns an "Invalid parameters" status for the job.
If the program fails, execjob sets the job status to "Needs recovery," sends the job status to lajs and the Print Manager, and writes the results of the job to the job’s log file.