G.4 Cautionary notes on using JP1/AJS3 - Agent Minimal Edition
This section describes points to note when using JP1/AJS3 - Agent Minimal Edition.
- Organization of this subsection
(1) Installing JP1/AJS3 - Agent Minimal Edition in an overwrite installation
If you install JP1/AJS3 - Agent Minimal Edition in an overwrite installation or upgrade installation, the number of executed jobs is not inherited.
(2) Change of the system time
Changing the system time on a computer where JP1/AJS3 - Agent Minimal Edition is running can affect the number of jobs executed per day. If you change the system time, note the following points:
-
Before changing the system time, make sure that there is no job that needs to be re-executed. If the system time is changed, the number of executed jobs might be incremented even when a job is re-executed within 48 hours after the KAVU3607-I message was output to the job execution history log file.
-
If you turn back the system time by a period that spans dates, the number of jobs that can be executed in the current day might be reduced from the maximum number of jobs set before the change of the system time.
(3) Cautionary notes on disaster recovery operation
The following describes points to note when using JP1/AJS3 - Agent Minimal Edition in the disaster recovery mode.
For details about the disaster recovery operation, see 11. Disaster Recovery in JP1/AJS3 in the JP1/Automatic Job Management System 3 Administration Guide.
JP1/AJS3 - Agent Minimal Edition manages the number of executed jobs for each computer where an agent host is installed. Therefore, how to count the number of executed jobs after switching over operation to a remote site differs depending on whether the agent host is shared by the main site and a remote site.
(a) In the case of unshared agent type
In a system configuration of unshared agent type, the number of executed jobs is not inherited when operation is switched over from the main site to a remote site. At the remote site to which operation was switched over, a maximum of 10 jobs can be executed per day.
The following figure shows an example of switching over operation to a remote site in a system configuration of unshared agent type.
If, after a job has been executed at the main site, operation is switched over to a remote site, and then the job is re-executed at the remote site, the number of executed jobs is incremented.
(b) In the case of shared agent type
In a system configuration of shared agent type, the number of executed jobs is inherited when operation is switched over from the main site to a remote site.
The following figure shows an example of switching over operation to a remote site in a system configuration of shared agent type.
Assume that the logical host name of JP1/AJS3 - Manager is different between the main site and remote site. In such a case, if, after a job has been executed at the main site, operation is switched over to a remote site, and then the job is re-executed at the remote site, the number of executed jobs is incremented.