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
Are there message events remaining that were generated in the past?
Cause
Generated message events will remain if the job net started after the execution condition was met, or unless the message event was not cleared using the jobschmsgclear command.
If the job net was started manually, the message event will not be cleared.
Action method
Check the generation state of the message in the Message Event List window, and then clear the message using the jobschmsgclear command.
Action 2
Points to check
Was Start only when message event has occurred selected?
Cause
If Start only when message event has occurred is not selected, the job net may start by another execution condition being met.
Action method
To start the job net only after a message event has occurred, select Start only when message event has occurred. If there are also other execution conditions, review the execution conditions of the job net and then set the execution condition according to the operation.
Action 3
Points to check
Have message events from other unintended job nets occurred?
Action method
Check if message events from other job nets have occurred.
Note that, if jobschmsgevent is specified directly in the command field, the jobschprint-a command can be used to identify the job that generated the message event.
