G.3 Counting the number of executed jobs

(1) Counting the number of executed jobs

JP1/AJS3 - Agent Minimal Edition manages the number of jobs that are executed. When JP1/AJS3 - Agent Minimal Edition receives a job execution request from the manager host, that job is added to the number of executed jobs.

Assume that you want to re-execute or automatically retry a job by JP1/AJS3 - Agent Minimal Edition. In such a case, re-execute or automatically retry the job within 48 hours after the KAVU3607-I message that includes the execution ID of the job was output to the job execution history log file.However, if a job is re-executed or automatically retried 48 hours or more after the original request, the job is counted as one of the 10 jobs executed for the day on which it is re-executed or automatically retried. Note that the addition of this job reduces the maximum number of remaining jobs that can be executed on that day. As a result, jobs that were scheduled to be executed on that day might not be executed. If it is likely that jobs will not be re-executed or automatically retried within 48 hours, we recommend that you use JP1/AJS3 - Agent to avoid this problem.

Supplementary notes

• JP1/AJS3 - Agent Minimal Edition manages the number of executed jobs by using the following information included in the job execution requests received from JP1/AJS3 - Manager:

  - Manager host name

  - Scheduler service name

  - Job name

  - Execution ID

  A re-executed or automatically retried job will not be added to the current day's number of executed jobs if the job's information, as described in the preceding list, matches a job that was executed in the previous 48 hours. However, if 48 hours or more have passed since the message KAVU3607-I was output to the job execution history log file, the job will be added to the number of jobs executed that day.

• The execution ID of a job does not change if the job is re-executed or automatically retried. However, the execution ID of a job executed by JP1/AJS3 - Agent Minimal Edition changes if a jobnet that contains the job is registered for immediate execution. In addition, the execution ID changes if a jobnet that contains the job is re-registered for execution after its registration is canceled, or after the manager host is cold-started. When a job is executed with a different execution ID, the job will be added to the number of jobs executed that day. In the event of system-wide recovery or recovery from a system failure, you might need to cold-start the manager host. We recommend, therefore, that you create an operational plan for JP1/AJS3 - Agent Minimal Edition so that no more than five jobs are executed per day.

• JP1/AJS3 - Agent Minimal Edition differs from JP1/AJS3 - Agent in that you must take into account the number of executed jobs when you register jobs for execution, or when you cancel registration. For jobs that are registered for execution (or for which registration is canceled), we recommend that you create a root jobnet for each job that is to be executed by using JP1/AJS3 - Agent Minimal Edition to distinguish such jobs from other jobs.

• If you use JP1/AJS3 - Agent Minimal Edition to execute a job multiple times for test purposes, re-execute the job rather than repeatedly registering the job for immediate execution with JP1/AJS3 - Manager. If you repeatedly register the job for execution, JP1/AJS3 - Agent Minimal Edition adds each execution of the job to the number of jobs executed that day.

The number of jobs executed per day is counted per computer. If multiple agent hosts (physical and logical hosts) exist on the same computer, the jobs executed by individual agent hosts are tallied, and a maximum of 10 jobs can be executed.

The following figure shows how to count the number of executed jobs when multiple agent hosts exist on the same computer.

Figure G‒2: Counting the number of executed jobs when multiple agent hosts exist on the same computer

The number of executed jobs is reset every day at 00:00 o'clock in the time zone set on the computer where JP1/AJS3 - Agent Minimal Edition is installed. The number of executed jobs is always reset at 00:00 o'clock, even if a local date and time is set for the scheduler service by JP1/AJS3 - Manager. Even if the number of jobs executed in a day is less than 10, the remaining number of jobs that can be executed in the day is not carried over to the next day.

Note, however, that event jobs can be executed without limitation on the number executed.

If JP1/AJS3 - Agent Minimal Edition uses the connection source restriction function, it can reject job execution requests from the manager hosts that are not permitted to connect to JP1/AJS3 - Agent Minimal Edition. In that case, the number of executed jobs is not incremented even when such a manager host issues a job execution request.

To Page Top

(2) Checking the number of executed jobs

You can check the number of jobs executed by JP1/AJS3 - Agent Minimal Edition in a day on the agent host where JP1/AJS3 - Agent Minimal Edition is running.

To check the number of jobs executed in a day from the agent host:

Open the job execution history log file (jpqjobhistory{0|1}.log).

The job execution history log file storage directories are as follows:

In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

%ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\log

The default %ALLUSERSPROFILE% value is system-drive\ProgramData.

A folder protected by the system is the path to a folder in any of the following:

- system-drive\Windows

- system-drive\Program Files

- system-drive\Program Files (x86)

In Windows, if the installation folder is other than the above:

JP1/AJS3-Agent-Minimal-Edition-installation-folder\log

In Linux:

/var/opt/jp1ajs2/log

1. Among the KAVU3607-I messages output to the job execution history log file, find the message that was output last with the date for which you want to check the number of executed jobs.

2. Check the number of executed jobs indicated in the found message.

Cautionary notes

When log records in a job execution history log file are wrapped around to the next file, the original file is not deleted but is overwritten with new log records from the top of the file. To distinguish between log records output before and after wrapping around, the following character string (endpoint identifier) is output at the end of the latest log record.

----------< End of Data >----------

Each time a job is executed, the endpoint identifier at the end of the preceding log data is deleted, new log data is output, and then the endpoint identifier is output at the end of the new log data. Therefore, note the following points when referencing a job execution history log file:

• To check the latest log data, reference the log data preceding the endpoint identifier. The log data that follows the endpoint identifier is the log records output before wrapping around.

• If the log records in a job execution history log file have been wrapped around in special timing, two or more endpoint identifiers might remain in the job execution history log file. In such a case, the first endpoint identifier counted from the top of the file is valid.

To Page Top

(3) After the number of jobs executed in a day has reached 10

If an attempt is made to execute a job after the number of jobs executed by JP1/AJS3 - Agent Minimal Edition in a day has reached 10, the eleventh job ends in Failed to start status. Then, the KAVU3608-E message is output to the integrated trace log and job execution history log file on the computer where JP1/AJS3 - Agent Minimal Edition is running. The same message is also output in the Execution Result Details window of JP1/AJS3 - View.

If a job executed by JP1/AJS3 - Agent Minimal Edition ends in Failed to start status and the KAVU3608-E message is output, review system operations so that the number of jobs executed per day will not exceed 10.

If a transfer file has been specified in the job definition for the job executed as the eleventh or subsequent job, the job ends in Failed to start status, but the file is transferred to the destination agent host. If you want to delete that file, in the Define Details dialog box, select the Transfer File tab, and then select the Yes check box.

To Page Top