4.4.1 Environment settings for event jobs
This subsection explains the environment settings (environment setting parameters) related to event jobs on a JP1/AJS3 - Agent host, and considers items that can be specified as options when event jobs are used. Consider the setting according to the operation environment.
- Organization of this subsection
(1) Linking with the mail system
You can use the mail system linkage function to define mail transmission and reception to a jobnet.
For details about the environment settings (environment setting parameters) when linking with a mail system, see the section corresponding to the OS. For Windows, see 2.3.4(4) Environment setting parameters used by the mail system linkage function in the JP1/Automatic Job Management System 3 Linkage Guide. For UNIX, see 2.4.2(3) Environment setting parameters used for email reception monitoring jobs in the JP1/Automatic Job Management System 3 Linkage Guide.
For details about setting procedures, if necessary, see the section corresponding to the OS. For Windows, see 2.3.4 Setting up the environment for the mail system linkage in the JP1/Automatic Job Management System 3 Linkage Guide. For UNIX, see 2.4.2 Setting up the environment for an email reception monitoring job in the JP1/Automatic Job Management System 3 Linkage Guide.
(2) Setting the log size for event jobs
The size of the log file for event jobs depends on such things as the number of event jobs executed and the number of monitoring conditions satisfied. As a general guide, set a log size large enough for 24 hours' worth of entries as a minimum, or 1-3 days' worth preferably. To estimate the required log size, see 3.4.3 Estimating the size of the log information output by event jobs.
(3) Processing events in order of occurrence
When an event job has start conditions, events that trigger the job might occur in succession but be processed in a different order, depending on the communication conditions. You might want to preserve the actual order of events that satisfied the start conditions if, for example, the event information will be passed to a parameter. In this case, use the event order option. Set this option on all agent hosts that execute event jobs. For details, see 6.3.2 Setting the event order option in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows systems) or 15.3.2 Setting the event order option in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX systems).
(4) Passing the status of a Monitoring Files job
You can save information as needed while a Monitoring Files job is monitoring the target files. This allows the job status to be passed at restart if the JP1/AJS3 service temporarily stops. For example, in a cluster system, if the JP1/AJS3 service is stopped and restarted while a Monitoring Files job is running, the job can be resumed from its previous monitoring status. We recommend that you use this setting to maintain the consistency of a Monitoring Files job should the JP1/AJS3 service stop.
To pass the monitoring status, the Monitoring Files job needs to be continuously active. Whether the monitoring status can be passed depends on whether the Monitoring Files job continues running or is stopped.
For the conditions under which the monitoring status is passed, see the description of the status passing option for Monitoring Files jobs in 7.6.2 Notes on the Monitoring Files job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
For the setting procedure, see 6.3.3 Setting the status passing option for the file monitoring job in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows systems) or 15.3.3 Setting the status passing option for the file monitoring job in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX systems).