2.13.1 Settings for integrating with JP1/AJS
This subsection describes the definition of JP1/AJS jobs, when systems are integrated with JP1/AJS.
Start a batch server in advance when executing a batch application from JP1/AJS.
- Organization of this subsection
(1) Starting a batch application
When you want to integrate the systems with JP1/AJS, you define the cjexecjob command as a UNIX job or PC job of JP1/AJS. Specify the following contents in Script file name, Parameter, and User at the time of execution fields on the window used for defining the properties of a JP1/AJS job.
-
Script file name
Specifies the cjexecjob command. For details on the path of the cjexecjob command, see cjexecjob (Execute batch application) in the uCosminexus Application Server Command Reference Guide.
-
Parameter
Specifies class name and arguments of the batch applications to be executed.
-
User at the time of execution
Specifies the user who executes a batch server.
For details on the settings of JP1/AJS, see the JP1/Automatic Job Management System Operation Guide.
(2) Forced termination of a batch application
When the system is integrated with JP1/AJS, and you forcefully terminate a job-net or a job, you define the cjkilljob command as a recovery job of JP1/AJS. However, when you want to forcefully stop a root job-net, the recovery job is not executed. Therefore, the batch application that is executing on a batch server continues as it is. In such cases, directly execute the cjkilljob command and forcefully stop the batch application.
For details on the settings of JP1/AJS, see the JP1/Automatic Job Management System Operation Guide.