Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide

2.5.1 Defining execution agents

Consider the following points when defining the agent host information to be registered in the manager hosts.

Organization of this subsection

(1) Assigning execution agent names and agent host names

(2) Maximum number of concurrently executable jobs

(3) Default execution agent

(4) Adding a execution agent

(5) Defining an agent automatically

(1) Assigning execution agent names and agent host names

The agent host information to be registered in a manager host consists of the logical names of the agent hosts (execution agent names) and their physical host names. Assign each agent host an execution agent. A maximum of 1,024 execution agents can be registered in one manager host.

When defining a job or jobnet, specify the execution agent name as the host on which the job is to be executed. The manager host references the registered execution agent information, and sends the job to the agent host corresponding to the execution agent name defined in the job or jobnet. Thus, when the agent host configuration needs to be changed due to an increase or decrease in work volume, rather than having to change the job or jobnet definition, you can simply change the execution agent information registered on the manager host without disrupting JP1/AJS3 operations.

(2) Maximum number of concurrently executable jobs

The number of jobs that can be executed concurrently on an agent host can be restricted according to the resources available for that host. The setting applies to Unix jobs, PC jobs, action jobs, and custom jobs.

The maximum number of concurrently executable jobs can be specified for particular time periods (set in 30-minute units). The default setting is 00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day).

For example, if you specify 08:00-17:30=5, a maximum of five jobs can be executed concurrently during the time period 8:00 to 17:30. By adjusting the maximum number of concurrent jobs in this way, you can distribute the processing load at certain times of the day.

When the number of jobs to be executed reaches the maximum number of concurrently executable jobs, additional jobs are queued on the manager host.

Cautionary notes

The default setting will suffice if only short jobs are executed, and no more than a few jobs will be registered for execution simultaneously. However, if you execute jobs with long execution times or register many jobs at the same time, the number of concurrent jobs will quickly reach the maximum, and remain there for a extended periods of time. This might affect the execution of subsequent jobs.
When the maximum number of concurrently executable jobs is reached on an agent host, subsequent jobs are made to wait in the queuing status until the active jobs finish. In such cases, jobs will take longer than expected to execute. Take the job execution time and the number of jobs executed per unit of time into consideration when you set the maximum number of concurrently executable jobs.

The maximum number of concurrently executable jobs you specify applies to each execution agent. If different execution agents are mapped to the same execution host, the sum of the maximum number of concurrently executable jobs specified for these execution agents is set for the jobs that will be executed on that execution host.
As an example, take the addition of an execution agent that uses the local host name and whose maximum number of concurrently executable jobs is set to 00:00-00:00=10 (maximum of 10 concurrent jobs, 24 hours a day). In this case, because the maximum number of concurrently executable jobs for the default execution agent is 00:00-00:00=5 (maximum of five concurrent jobs, 24 hours a day), a maximum of 15 jobs could be executed concurrently.
When you specify a maximum number of concurrently executable jobs, specify a value appropriate for the execution host.

(3) Default execution agent

By default, the local host is set as an agent host in the information registered in the manager host. This agent is referred to as the default execution agent.

The agent host information defined as the default execution agent is as follows:

Table 2-19 Information defined as the default execution agent

No. Item Setting

1 Execution agent name @SYSTEM

2 Execution host name Manager host name

3 Maximum number of concurrently executable jobs 5 (00:00-00:00=5)

4 Job transfer restriction status Enabled

This default execution agent can be used to execute jobs in a standalone configuration. It is also used when no execution agent is specified in the job or jobnet definition.

To change the default execution agent definition, use the ajsagtalt command. For details about the command, see ajsagtalt in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

Cautionary note

When you execute jobs on the local host, you can specify the local host name in Target agent in the unit definition. To do so, add an execution agent, other than the default execution agent, that has the same name as the local host name. Note, however, that if you migrate the unit definition to another manager host when the local host name is specified, you need to change the Target agent setting according to the destination host name. For this reason, we recommend that you use the default execution agent when you execute jobs on the local host.

No.	Item	Setting
1	Execution agent name	@SYSTEM
2	Execution host name	Manager host name
3	Maximum number of concurrently executable jobs	5 (00:00-00:00=5)
4	Job transfer restriction status	Enabled

(4) Adding a execution agent

By default, a single execution agent (default execution agent) is created on the manager host during setup. However, you will need to add execution agents if you plan to have multiple agent hosts and to distribute job processing among them.

You can add an execution agent using the ajsagtadd command. For details about the procedure, see 4.1 Execution agent settings in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

You can also add information about multiple execution agents as a batch job. For details, see the description of the -f option in ajsagtadd in 2. Commands in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 1.

(5) Defining an agent automatically

When the setting for automatically defining an agent is enabled, the agent definition (assigned execution agent name and agent host name) that has the same name as the execution agent name specified in the job's Define Details dialog box is automatically added to the manager host.

To define an agent automatically, specify 1 in the environment setting parameter AutoCreate. For details about this parameter, see 2.3 Setting up the job execution environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

Cautionary note

We recommend that the system administrator enable the AutoCreate parameter when setting up JP1/AJS3. When this parameter is set, only users who have both JP1_JPQ_User permission and JP1_JPQ_Admin permission are allowed to execute jobs.

[Contents][Back][Next]

[Trademarks]