B.3 Notes on starting from a job scheduler other than JP1/AJS
Note the following points when starting a batch job of JP1/Advanced Shell by using a job scheduler other than JP1/AJS:
The SIGKILL signal is assumed to be sent when a job is forcibly terminated from a job scheduler other than JP1/AJS. For the signal sent at the time of a forced termination, see the manual of the job scheduler.
-
A post-process that is unique to a user at the time of forced termination cannot be executed even by defining the environment setting parameter, TRAP_ACTION_SIGTERM.
-
JP1/Advanced Shell might create a temporary file to execute a job. Specify with the environment setting parameter, TEMP_FILE_DIR, the path of the directory in which the temporary file will be stored. Although the temporary file is normally deleted, the temporary file might remain if a job that is running is forcibly terminated. In such case, the file will need to be deleted manually.
-
If a job that is running is forcibly terminated, files created with the #-adsh_file command, #-adsh_file_temp command, #-adsh_spoolfile command, or adshfile command might remain. In such case, the file will need to be deleted manually.
-
If the adshread command is waiting for a reply of the reply-request message and the command forcibly terminated from a job scheduler other than JP1/AJS, the information regarding the reply-request message might remain on the shared memory and the reply-waiting event might remain on JP1/IM - View. In such case, you will need to either cancel the reply-wait status of the reply-request message with the -d option of the adshchmsg command, or restart the user-reply functionality management daemon or service.
-
If the command is forcibly terminated from a job scheduler other than JP1/AJS while the adshjava command is executing a batch application, the Java batch application might not be forcibly terminated and continue to be executed.
-
Items related to the operation information shown in Table B-1 are not extracted. Items related to the operation information shown in Table B-1 are not extracted for the adshevtout command.
Item name |
Corresponding adshevtout option |
Contents |
---|---|---|
Jp1ajsService |
-c |
Name of scheduler service of JP1/AJS |
Jp1ajsJobName |
-g |
Job name of JP1/AJS |
Jp1ajsExecId |
-k |
Execution ID of the job of JP1/AJS |
Jp1ajsJobId |
-n |
Job number of JP1/AJS |
Jp1ajsRootJobnet |
-r |
Root job net name of JP1/AJS |