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
Was Wait for startup time selected?
Cause
If Wait for startup time is not selected, the job net time condition and the wait for message condition will be handled as separate execution conditions, so the job net will be started only when the startup time arrives, or when a message event is generated.
Action method
Ensure that Wait for startup time is selected on the Message tab in the Job Net Properties window.
Action 2
Points to check
Are there message events that were waited for remaining?
Cause
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, a job net that starts when the scheduled start time (9:00) arrives, and in which message events are generated every day, is registered. Here, if a message event that is waited for on Apr 1 is generated after the job net starts, it will be recognized that this message event was generated. As a result, when Apr 2 (9:00) arrives, the job net starts and may cause a problem.
Action method
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.
Action 3
Points to check
Did the effective user of the jobschmsgclear command try to clear a message event without the message event clear rights, causing the message to remain?
Action method
To clear a message event, grant operation rights to the effective user of the jobschmsgclear command as the access rights for the project that the job net belongs to.
