Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Overview


5.3 Execution agent restriction function

The execution agents permitted to execute jobs can be set for each unit by specifying them in operation profiles called execution agent profiles. The use of execution agent profiles helps to ensure that jobs are not executed by an inappropriate execution agent.

An execution agent profile is created for each scheduler service. In an execution agent profile, the execution agents or execution agent groups that are permitted to execute jobs are set for each unit. The hosts that are permitted to execute queueless jobs can also be set in an execution agent profile, in which target host names specified in queueless jobs are set in the execution agent profile.

The following figure shows an example of execution agent restriction.

Figure 5‒7: Example of execution agent restriction

[Figure]

In this example, AGT1 is set in the execution agent profile as an execution agent permitted to execute jobs in jobnet net1. Job job1 in jobnet net1 is executed on agent AGT1 because AGT1 is specified as an execution agent. However, execution of job job2 in jobnet net1 is suppressed by the manager host because the execution agent specified in this job is AGT2, which is not permitted to execute jobs in jobnet net1.

For details about execution agent restriction, see 2.5.1(6) Execution agent restriction in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

For details about how to specify execution agent profile settings in Windows, see 4.3.1 Procedure for setting up an execution agent profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1. For details about how to specify execution agent profile settings in UNIX, see 14.3.1 Procedure for setting up an execution agent profile in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.