3.2.5 Job controller processing after batch jobs have started

Batch jobs are executed as job controller processes. The job controller is started in the following manner:

• In the execution environment, the job controller is started from JP1/AJS - Agent according to JP1/AJS's schedule.

• In the execution environment, the user enters a command to start a process called a job controller.

• On the development PC, the user runs a text while editing the development environment.

To process a job after starting it:

1. The job controller analyzes the options for starting a batch job and JP1/Advanced Shell's environment files.

2. The job controller analyzes the entered job definition script file at the initial stage. During this analysis process, the job controller analyzes syntax and creates a table for storing job information without executing commands.

3. The job controller's job execution control analyzes and executes the job definition script file.

4. The file management function used in extended script commands allocates and releases regular files, temporary files, and program output data files.

5. The shell variables and environment variables in extended script commands store job step return codes in shell variables and set job information in environment variables so that this information can be referenced by user programs.

In both the Windows and the UNIX execution environment, the job controller analyzes and executes job definition scripts. For details about creating job definition scripts, see 4. Using JP1/Advanced Shell - Developer (Windows Only) and 5. Creating Job Definition Scripts.

To Page Top