6.2.3 Behavior when the JP1/AJS3 service is started and stopped
This subsection describes the job statuses of service linkage objects monitoring jobs.
- Organization of this subsection
(1) Statuses when the service is started or stopped
The service is started or stopped according to the JP1/AJS3 specifications. The status at this time is determined by the specifications of custom event jobs. See the specifications of custom event jobs in the manual JP1/Automatic Job Management System 3 Administration Guide.
However, for in what status the service linkage objects monitoring job in Running status before the service is stopped will be started, see (2).
(2) How the service linkage objects monitoring job works after the service is restarted
The following describes the operation that occurs after the service stops while a service linkage objects monitoring job is running and then the service is restarted with hot start.
(a) How the monitoring status can be passed after the service is restarted
When a service linkage objects monitoring job enters the Running status, the data can be stored in files whenever necessary while monitoring objects are monitored. In this way, even if the JP1/AJS3 service stops, the previous monitoring status can be restored after its restart.
Note that no events can be detected if they occur between the service stop and the resumed event monitoring after the service restart. If the file into which the data is stored cannot be opened, a KNBB6162-W message is output to the process log of the execution agent and the integrated trace log. Also, if the file has an invalid format, a KNBB6403-W message is output to the service linkage file monitoring job log and the integrated trace log. In both cases, monitoring continues.
(b) Definition after the service is restarted
If you modify the definition# of a service linkage objects monitoring job while monitoring is continued after the service is restarted, when you restart the JP1/AJS3 service, the job works with the definition at the recent execution registration unless the execution registration is performed again.
- #
-
The definition refers to a definition on the custom event job. For a service linkage objects monitoring job, the definitions of Monitoring objects, Monitoring interval, and Monitoring options in JP1/AJS3 for Cloud Service Applications use the ones read when the job goes running after the JP1/AJS3 service is started, regardless of a change of the job definition in JP1/AJS. For details about the operation that occurs after JP1/AJS3 for Cloud Service Applications definitions are changed, see (c) JP1/AJS3 for Cloud Service Applications definitions after the service is restarted.
(c) JP1/AJS3 for Cloud Service Applications definitions after the service is restarted
When a definition in JP1/AJS3 for Cloud Service Applications is modified, the job also works with the definition read when the job goes running after the JP1/AJS3 service is started, as described in (b) Definition after the service is restarted.