Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Configuration Guide


6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached

If the number of jobs (PC jobs other than queueless jobs, Unix jobs other than queueless jobs, flexible jobs#, HTTP connection jobs, action jobs other than queueless jobs, or custom jobs) that are being executed concurrently on an agent host has reached the maximum, the succeeding jobs might remain queued, delaying their execution.

#:

For a flexible job, replace agent host with relay agent.

JP1/AJS3 provides a setting that outputs the following message to the integrated trace log when the number of jobs being executed concurrently reaches the maximum. By enabling the setting, you can confirm that job execution was delayed because the maximum was reached.

KAVU4310-I The number of executing jobs reaches the concurrently-executable-job-limit (maximum-number-of-concurrently-executable-jobs) at the agent (agent-host-name). (host name: host-name, job number: job-number)

If this message is not output even when this setting is enabled and the status of jobs is Now queuing, various causes are possible. Accordingly, check the setting of the maximum number of concurrently executable jobs, the job transfer restriction status, and the job execution host status for the execution agent or execution agent group.

  1. The maximum number of concurrently executable jobs is 0.

    Use the ajsagtshow command to check the maximum number of concurrently executable jobs (CON-EXE) on the execution agent.

    For details about the ajsagtshow command, see ajsagtshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

  2. The job transfer restriction status of the execution agent group is Hold or Blockade. Alternatively, the job transfer restriction status of the execution agent is Ineffective, Hold, or Blockade.

    Use the ajsagtshow command to check the job transfer restriction status of the execution agent group or execution agent.

    For details about the ajsagtshow command, see ajsagtshow in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

  3. The agent host has stopped or failed.

    Use the integrated trace log on the agent host to check for stoppage of the JP1/AJS3 service or the occurrence of an error on the agent host. Also check whether the agent host is able to communicate with the manager host.

If queue or submit jobs are used, check the agent, agent group, or job execution host for the following possible causes:

  1. The maximum number of concurrently executable jobs is 0.

    Use the jpqagtshow command to check the maximum number of concurrently executable jobs (CUREXECHGNUM).

    For details about the jpqagtshow command, see jpqagtshow in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

  2. In the settings for queues (including the default queue), the job exit is closed.

    Use the jpqqueshow command to check the job exit status (EXITSTATUS).

    For details about the jpqqueshow command, see jpqqueshow in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

  3. The agent host has stopped or failed.

    Use the integrated trace log on the agent host to check for stoppage of the JP1/AJS3 service or the occurrence of an error on the agent host. Also check whether the agent host is able to communicate with the manager host.

  4. A necessary resource has been locked by another job.

    Use the jpqresshow command to check for jobs whose status is EXECUTING.

    For details about the jpqresshow command, see jpqresshow in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

For details about the maximum number of concurrently executable jobs when queue or submit jobs are used, see 2.5.4 Maximum number of concurrently executable jobs in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The following describes how to set output of a message that reports that the maximum number of concurrently executable jobs has been reached.

Organization of this subsection

(1) Definition procedure

  1. In Windows Control Panel, open the Services administrative tool, and stop the following service:

    • JP1/AJS3 service

    Cautionary note:

    In a cluster system, check the cluster settings, and also stop the JP1/AJS3 service on each logical host.

  2. Execute the following command to set the environment setting parameters described in (2) below:

    jajs_config -k definition-key "parameter-name-1"=value-1 ["parameter-name-2"=value-2]
  3. Restart JP1/AJS3.

    The new settings are applied.

(2) Environment setting parameters

Table 6‒31: Environment setting parameters used to set output of the message that reports that the maximum number of concurrently executable jobs has been reached

Definition key

Environment setting parameter

Explanation

  • For all scheduler services

    [{JP1_DEFAULT|logical-host}\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Job]#

  • For a specific scheduler service

    [{JP1_DEFAULT|logical-host}\JP1AJSMANAGER\scheduler-service\QUEUE\MANAGER\Job]#

  • For submit jobs

    [{JP1_DEFAULT|logical-host}\JP1NBQMANAGER\Job]#

"MaximumExecJobLogOption"=

Specifies output of the message that reports that the maximum number of concurrently executable jobs has been reached.

"MaximumExecJobLogInterval"=

Specifies the interval for re-output of the message that reports that the maximum number of concurrently executable jobs has been reached.

#:

The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

For details about the definition of these environment setting parameters, see the following: