4.3.7 Options for using event jobs

(1) Setting the event job log

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.

To Page Top

(2) 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 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 15.3.2 Setting the event order option in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

To Page Top

(3) 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 Job Management Partner 1/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 Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 15.3.3 Setting the status passing option for the file monitoring job in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

To Page Top

(4) Passing event data containing double quotation marks

The information received by an event job can be passed to the parameters of standard jobs and action jobs. Any double quotation marks (") contained in the event data to be passed must be preceded by a backslash (\) when the event is issued. If the backslash is missing, the double quotation mark will be ignored or other issues might occur when the received event data is passed.

To prevent this, we recommend that you set an option to pass data containing double quotation marks exactly as in the issued event.

When you set this option, JP1/AJS3 inserts a backslash before each double quotation mark. This allows the information received by an event job to be passed to a job parameter regardless of whether it contains any double quotation marks.

If a backslash already precedes a double quotation mark in the information to be passed, this option adds a second backslash. Therefore, the string AB\"C, for example, will be passed as AB\"C, not AB"C. If you have already added backslashes intentionally, do not set this option.

Cautionary note

The received event data, passed from an event job to a parameter in a standard job or action job, must fit within the maximum length of that parameter. Note that with this option specified, there will be an extra backslash before any double quotation mark.

Consider the effects of passing data containing double quotation marks when this option is enabled, with reference to the following example:

Example;

The maximum length of a command statement in a Unix job is 1,023 bytes. If there are 1,023 bytes of event data containing a double quotation mark, specifying this option will result in an error because the passed data will exceed 1,024 bytes when the backslash is inserted.

For details about setting this option, see 6.3.4 Passing event data containing double quotation marks in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 15.3.4 Passing event data containing double quotation marks in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

To Page Top