This section explains how to determine the execution conditions for job nets.
One of the execution conditions given below must be specified for job nets.
Execution condition | Description | Relationship with startup day settings |
|---|---|---|
None | Does not specify an execution condition.
| If you specify "Valid only on startup days" (*1), the job net is started on the startup day specified for child job nets or master linked job nets. If you do not specify "Valid only on startup days" (*1), the job net is started on the startup day for the parent job net. |
Execute at | Starts the job net at the specified time(s)
| Valid only on days set as the startup days. |
Execution interval | Starts the job net at regular intervals
| Valid only on days set as the startup days. |
Start at the time of server startup | Starts the job net when the schedule server starts
| Valid only on days set as the startup days. |
Start only when message event has occurred | Starts the job net only if a message event occurs.
| Waits every day for a message, regardless of the startup day setting (default). To make the job net wait for a message only on days set as startup days, you must specify "Valid only on startup days" (*2). |
*1: Valid only on startup days in the Control information tab of the Add/Change - Job window
*2: Valid only on startup days in the Message tab of the Job Net Properties window
You can specify the execution condition in the Standard information tab of the Job Net Properties window.
Combining message event occurrence and other execution conditions
You can register message events even when you have specified the following execution conditions:
Execute at
Execution interval
Start at the time of server startup
Essentially, if you combine conditions, the job net starts each time an execution condition is met.
Execution condition | Timing of job net startup |
|---|---|
Combination of message event and Execute at | The job net starts when the message event that is waited for occurs and the specified time is reached.
|
Combination of message event and Execution interval | The job net starts when the message event occurs and the fixed interval has elapsed. |
Combination of message event and Start at the time of server startup | The job net starts when the message event occurs and the server starts. |
If combining execution conditions, specify Execute at, Execution interval, or Start at the time of server startup as the execution condition in the Standard information tab of the Job Net Properties window, and register the message event to be waited for in the Message tab.
This section explains points to consider before you use message event occurrence as an execution condition.
Consider the name of the message event to be waited for. The job net starts when the message registered here occurs.
Up to 70 message events can be registered for a single job net.
If you have registered multiple queuing message events, consider whether the job net will wait for all the message events to occur before starting (AND condition) or whether to start the job net when any one event has occurred (OR condition).
By default, a job net starts when a message event occurs, regardless of the startup day setting.
To start a job net on startup days only, specify Valid only on startup days.
You can specify whether to start a job net each time the same message is generated while the job net is running.
If you specify Valid during job net execution, message events are accepted even while the job net is running. Therefore, after the job net ends, it is successively started and stopped once for each time the message was received while the job net was running.
You can define queuing message events in the Message tab of the Job Net Properties window.
To use message receipt as the trigger for starting a job net, specify the queuing message event name explained above in the job net that will receive the message. Then, in the job that will generate the message event, register the jobschmsgevent/jobschmsgeventex command and issue a message event.
Information
Counting message events
Before defining message event occurrence as the execution condition of job nets, you must understand how message event occurrences are counted and cleared. The method used for counting message events depends on, for example, whether the count is started by schedule or manually, and whether only message event occurrence is set as the execution condition or message event occurrence is combined with the startup time as the execution condition.
Refer to "Message Events and Job Net Actions" in the Systemwalker Operation Manager User's Guide for details.
