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
Does the job net that waits for the message have a status that does not recognize message events?
Action method
If the job net waiting for the message is in any of the following states, the message event cannot be recognized when it has occurred. Check if any of the following conditions apply.
The job net has the "Executing" status. (*1)
The job net has the "Warning" status. (*1) (*2)
The job net has the "Disabled" status.
The job net has the "Abended" status. (*3)
The job net has the "Canceled" status. (*4)
The cumulative occurrence count of message events exceeded 255 times. (*5)
The job net waiting for the message falls on an unscheduled day. (*6)
Once in a day is specified for Start only when wait event has occurred, and the job net has already been started. (*7) (V11.0L10/11.0 or later)
*1: This is recognized if Valid during job net execution is selected.
*2: Only a job net with the Job Execution Control attribute can be in a warning state.
*3: This is recognized if the job net is included in a group. Additionally, even if the job net is not included in the group, it will be recognized if Validate job net confirmation is not selected in the Advanced Settings for Verification window that is called from the Define Jobscheduler Startup Parameters window. Note that, in V13.2.0 or earlier, Validate job net confirmation is specified on the Use function1 tab in the Define Jobscheduler Startup Parameters window.
*4: This is recognized if the job net is included in a group. Additionally, even if the job net is not included in the group, it will be recognized if Check canceled is not selected in the Advanced Settings for Verification window that is called from the Define Jobscheduler Startup Parameters window. Note that, in V13.2.0 or earlier, Check canceled is specified on the Use function1 tab in the Define Jobscheduler Startup Parameters window.
*5: If the execution condition of job net is specified as Start only when message event has occurred, it internally retains the number of message event occurrences. This occurrence count refers to the cumulative occurrence count. The cumulative occurrence count increases by one each time a message event occurs. However, the occurrence count decreases by one each time a job net is started by the occurrence of a message event. Note that the cumulative occurrence count of message events should not exceed 255.
*6: This is recognized if Valid only on startup days is not selected.
*7: This is recognized again after the Reinstate operation has been performed.
Action 2
Points to check
Was the message event correctly generated?
Action method
Check if any of the following conditions apply.
Do the generated message event and the message event defined in the job net match? (case-sensitivity is used.)
Was the message event generated to the host that waits for the message event?
Was the message event generated to the subsystem that waits for the message event?
Was the message event generated to the job net that waits for the message event? (V11.0L10/11.0 or later)
Action 3
Points to check
Was the Systemwalker MpJobsch service started on the host that generated the message event?
Cause
Even if the message event was correctly generated, it will not be recognized by the job net if the Systemwalker MpJobsch service was not started.
Action method
Check if the Systemwalker MpJobsch service was started on the host that generated the message event.
Action 4
Points to check
Did you try to generate a message event to an SE version Systemwalker Operation Manager from an EE version Systemwalker Operation Manager?
Refer to "4.10.5 The Message "MpJobsch: ERROR: 0309: Usage: jobschmsgevent event_name[:project_name[/job_net_name] [message_text]] [-h host_name] [-t:INFO | -t:WARN | -t:ERROR]" is Output when the jobschmsgevent Command is Executed from a Schedule Job [UNIX Versions]" for information on the cause and action method.
Action 5 [Windows versions]
Points to check
When the following check boxes were not selected on the Use function1 (*1) tab in the Define Jobscheduler Startup Parameters window, was the "Systemwalker MpJobsch" service started?
Use message waiting
Application
*1: In V5.0L20 or earlier, the Options tab is used.
Cause
If the "Systemwalker MpJobsch" service was started when the above check boxes were not selected, the message event will be discarded even if generated. (The job net will not start when the message event is generated.)
Action method
When the following check boxes are selected on the Use function1 (*1) tab in the Define Jobscheduler Startup Parameters window, start the "Systemwalker MpJobsch" service:
Use message waiting
Applications
*1: In V5.0L20 or earlier, the Options tab is used.
