13.1.2 Preventing execution of jobs that are invalid due to an incorrectly specified execution agent or other reason

(1) Operation

The JP1/AJS3 system operates as follows:

• Multiple departments share a manager host

• Each department is restricted to specific execution agents

• Each department has its own scheduler service

The following figure shows an example in which the inventory and accounting departments use separate execution agents and scheduler services.

Figure 13‒4: Example using different execution agents and scheduler services

To Page Top

(2) Problem

You want to prevent departments from executing jobs using an execution agent allocated to another department.

Figure 13‒5: Example of job execution using an execution agent allocated to another department

To Page Top

(3) Solution

By using the execution agent restriction function, you can prevent a job from being executed on an execution agent without permission. By this process, you can avoid the problems that arise when you use an execution agent intended for use by another department.

To use the execution agent restriction function, you create an execution agent profile and assign it to the scheduler service. An execution agent profile defines the execution agents permitted for each unit type.

When you set an execution agent profile, the JP1/AJS3 system checks the execution agent of a unit when:

• The unit is defined

  An Exec-agent combo box appears in the Define Details dialog box when you define a unit in JP1/AJS3 - View. This box displays a list of the execution agents permitted by the execution agent profile. Because you can only select an execution agent that appears in the combo box, there is no way a user can choose the wrong execution agent.

  Figure 13‒6: Execution agent restriction (at unit definition)

  In the Define Details dialog box, if you enter an execution agent that does not appear in the list into the Exec-agent combo box and then click OK, an error occurs. However, you can configure the execution agent profile to display a warning message instead, and permit the unit to be defined.

• The job is executed

  Job execution is suppressed if the execution agent specified for the job is not permitted by the execution agent profile.

  If you change the execution agent profile after defining the unit, the execution agent is checked against the latest version of the execution agent profile.

  Figure 13‒7: Execution agent restriction (at job execution)

  In this example, AGT02 was permitted as an execution agent for job 1 in the execution agent profile when the unit was defined, but is no longer permitted when the time comes to execute the job. If you leave the unit definition unchanged and attempt to execute job 1 using AGT02, execution is suppressed according to the execution agent profile. To execute the job, amend the unit definition to specify AGT05 as the execution agent for job 1.

To Page Top

(4) Timing

Use this functionality in the following scenarios:

• One JP1/AJS3 - Manager host is used by multiple departments

• You want to reduce job execution errors resulting from improperly defined jobs

To Page Top

(5) Manual references

Type	Item	Location
Overview	Execution agent restriction	2.5.1(6) Execution agent restriction in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide
Configuration		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 Windows) 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 (for UNIX)

To Page Top