Applicable versions and levels
Windows versions: V5.0L10 or later
Solaris versions: 5.0 or later
Linux versions: 5.2, V10.0L10 or later
Linux for Itanium versions: V12.0L10 or later
HP-UX versions: 5.1 or later
AIX versions: 5.1 or later
DS versions: V20L10
Action 1
Points to check
On the Message tab in the Job Net Properties window, was Start when a message event occurs set as the wait condition?
Action method
To wait for all message events, select Start when all message events have occurred.
Action 2
Points to check
Have message events from other unintended job nets occurred?
Action method
Check if message events from other job nets have occurred.
Action 3
Points to check
Are there message events that were waited for remaining?
Cause
The cause may be the same as the cause described in "Action 2" of "4.2.3 A Job Net that Waits for a Message Event and a Startup Time is Started at an Unintended Time".
For job nets for which the only execution condition is "when the message event is generated", the number of times each message event is generated is counted.
The number of occurrences of message events is counted as shown in the example below. If excessive message events occurred or message events remained due to job net start operations previously, job nets may start in combination with previous messages even if message events that were supposed to occur for that day did not occur.
For example, in a job net that waits for msg-a and msg-b, msg-a was generated twice, and msg-b was generated once on Dec 1. The msg-a and msg-b message events were both generated on Dec 1, so the job net was started, but one extra msg-a event was generated. On the next day (Dec 2) when msg-a and msg-b are to be generated, the job net will be started when msg-b is generated even if msg-a is not generated yet (because msg-a remains from the previous day). If msg-a is generated after that, the job net will be started if msg-b is generated on the next day as well.
Action method
Perform the action method described in "Action 2" of "4.2.3 A Job Net that Waits for a Message Event and a Startup Time is Started at an Unintended Time".
Check the current occurrence status of message events in the jobschprint -a command execution result (an "*" mark is displayed for message events that have already occurred at the point when the jobschprint command is executed), or in the Message Event List window. If message events that were not expected to occur on this day have been notified, this could be due to past message events that still remain, therefore, execute the jobschmsgclear command to clear these messages.
