2.2.3 Jobnet definition considerations
This section describes the matters you need to consider when defining jobnets.
For details of the information you can define in a jobnet, see the description of the Define Details dialog box for a root jobnet in 12. Windows and Dialog Boxes in the JP1/Automatic Job Management System 3 Operator's Guide.
- Organization of this subsection
(1) Execution agent
You can specify the name of the agent that is to execute a jobnet. In systems that use execution agent restriction, you can select execution agents from a list of execution agent profiles. An execution agent is a logical name representing the agent host to which a job or jobnet is distributed. Based on the execution agent information defined in the manager host, the manager maps the execution agent specified in the job or jobnet to the physical host name of the agent host, and distributes the jobs accordingly.
By specifying an execution agent group, you can distribute the processing load among a group of execution agents. The manager distributes jobs among the execution agents according to their assigned priorities.
(2) Concurrent execution and schedule option
For jobnets that are executed periodically, consider whether you want JP1/AJS3 to run multiple instances of the process concurrently if the process has not completed by the time the next scheduled start time arrives. For details, see 3.3.3 Concurrent execution and schedule option in the manual JP1/Automatic Job Management System 3 Overview.
(3) Number of logs to keep
Consider how many generations of execution logs you need to keep for the jobnet. For details, see 4.2.3 Jobnet generation management in the manual JP1/Automatic Job Management System 3 Overview.
(4) Timeout period
When a jobnet fails to execute by its scheduled start time, consider how long you want the jobnet to wait to execute before it times out. Jobnets that time out while waiting to execute are placed in Skipped so not executed status. For details, see the description of timeout periods in 3.1.1(2) Jobnets in the manual JP1/Automatic Job Management System 3 Overview.
A jobnet that is on hold is also placed in Skipped so not exe. status if the timeout period expires. If the timeout period expires while you are performing a temporary change operation, the jobnet is placed in Skipped so not exe. status. In this case, you might have to execute the jobnet again. If you do not want jobnets to be placed in Skipped so not exe. status, specify the timeout period with a margin, as shown below.
- If you consider one day as the timeout period:
-
Specify two days or unlimited.
- If you consider two days as the timeout period:
-
Specify unlimited.
To set Use system settings in the definition of the timeout period, specify any of the above values for the EXECDEFER environment setting parameter.
(5) Jobnet monitoring
By setting the time required to execute a jobnet, you can monitor for end delays based on how much time has passed since the jobnet started. For details, see 5. Monitoring Method Considerations.
(6) Execution order control
You can assign an execution order to the jobnets at the highest level of the hierarchy to facilitate job management. For details, see 2.2.4 Using jobnet connectors to control the order of root jobnet execution.
(7) JP1 resource group
Consider the access permissions you need to assign to each jobnet. For details, see 6. Access Permission Considerations.
(8) Cautionary notes
-
Do not use a space character at the end of a comment in a jobnet definition. All space characters after a comment are treated as invalid.
-
Do not use machine-dependent characters in any part of a jobnet definition, because these characters might not be displayed correctly.