Hitachi

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


15.2.3 Customizing the execution agent or agent attribute values created by the automatic agent definition function

You can customize the execution agent or agent attribute values created by the automatic agent definition function in advance by using the common definition information.

The applicable objects and job types differ according to the definition key.

Table 15‒14: Objects and job types to which customization is applicable

No.

Definition key

Object

Job type

1

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

All execution agents

  • PC job

  • Unix job

  • Flexible job#2

  • HTTP connection job

  • Action job

2

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

Execution agent for the scheduler service specified by the definition key

  • PC job

  • Unix job

  • Flexible job#2

  • HTTP connection job

  • Action job

3

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

All agents and default queue

  • Submit job

#1:

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.

#2:

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

To customize the execution agent or agent attribute values created by the automatic agent definition function can be customized by using the common definition information, execute the jajs_config command.

The following describes the customization procedure.

Organization of this subsection

(1) Definition procedure

  1. Stop the JP1/AJS3 service.

    Execute the following commands to confirm that all processes have stopped:

    # /etc/opt/jp1ajs2/jajs_stop#1
    # /opt/jp1ajs2/bin/jajs_spmd_status
    #1:

    Confirm that automatic termination has been set.

  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] 
    ["parameter-name-3"=value-3] 
    ["parameter-name-4"=value-4]
  3. Restart the JP1/AJS3 service.

    The new settings are applied.

(2) Environment setting parameters

Table 15‒15: Environment setting parameters used to customize the attribute values set by the automatic agent definition function

Definition key

Environment setting parameter

Applicable manager

Explanation

  • For all scheduler services

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

  • For a specific scheduler service

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

  • For submit jobs

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

"AutoCreateExecJobs"=

C, S

Specifies the maximum number of concurrently executable jobs set by the automatic agent definition function.

"AutoCreateMaxJobs"=

C

Specifies the maximum number of jobs set by the automatic agent definition function.

"AutoCreateWarnJobs"=

C

Specifies the number of jobs set by the automatic agent definition function as the threshold value for warning.

"AutoCreatePriority"=

C

Specifies the agent priority set by the automatic agent definition function

Legend:

C: Job execution control manager for submit jobs

S: Job execution control manager for scheduler services

#:

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:

(3) Note

When you use the agent automatic definition function and the execution agent restriction function, an execution agent that is automatically defined during job execution needs to be set in the execution agent profile before execution of the job. If the execution agent has not been set in the execution agent profile, the job is placed in the Failed to start status, in which case the execution agent will not be added.