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 [Windows versions]
Points to check
Does the host that generated the message event have a user account that can execute the jobschmsgevent command?
Was the user account password invalid or expired?
Cause
The jobschmsgevent command functions to record events to the application event log of the specified host. For this reason, the user account that executes the jobschmsgevent command must pass authentication also on the host that generated the message.
Action method
Change the user account of the command executor so that it will be authenticated on the other host. For example, when executing the command as a job of Systemwalker Operation Manager, ensure that the Systemwalker MpMjes service startup account can pass the authentication on the host that generates message events.
Action 2 [Windows versions]
Points to check
Is the event log capacity of the host that generated the message event full?
Cause
If the event log capacity of the host that generated the message event is full, the execution of the jobschmsgevent command may fail because the event could not be recorded.
Action method
Before starting the operation, in the application event log properties of the host that generated the message event, ensure that the log size is sufficiently large, or set or configure to overwrite events as necessary, to ensure that the capacity of the event log is sufficient.
Action 3 [Windows versions]
Points to check
Was a firewall built between hosts that have message link, so that the NetBIOS interface port was restricted?
Cause
The NetBIOS interface is used to record the event log, therefore if a firewall is built between hosts that have message link so that the NetBIOS interface port is restricted, the message will not be notified correctly.
Action method
Do not execute the job by specifying the host name in the jobschmsgevent command. Execute as a network job instead.
Action 4 [Windows versions]
Points to check
Was the Server service started?
Cause
It is mandatory that the Server service be started on the host that generates the message event using the jobschmsgevent command.
Action method
Start the Server service on the host that generates the message event.
Action 5
Points to check
Did you use double quotation marks (") in the message event name?
Action method
Double quotation marks (") are recognized as normal characters, not symbols used for enclosing words, when the yen sign (\) is appended immediately before in the number shown below. This number varies according to the operating system. If double quotation marks (") are used in the message event name, take the action shown below.
[Windows versions]
Append three yen signs ("\") before the double quotation marks (") of the message event name.
[Example] \\\"message event string\\\"
[UNIX versions]
Append one yen sign ("\") before the double quotation marks (") of the message event name.
[Example] \"message event string\"
Action 6
Points to check
If the job net waiting for message event is in any of the following states, the message event cannot be recognized when it has occurred.
The job net is "Executing". (*1)
The job net is in a warning state. (*1)
The job net is in an End delayed state. (*1)
The job net is in a disabled state.
The job net is in an abended state. (*2)
The job net is in a Canceled state. (*3)
The cumulative occurrence count of message events exceeded 255 times. (*4)
The job net waiting for a message event falls on the unscheduled day. (*5)
Once in a day is specified for Start only when message event has occurred, and the job net has already been started. (*6)
*1: This is recognized if Valid during job net execution is selected.
*2: 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.
*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 Check canceled is not selected in the Advanced Settings for Verification window.
*4: 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.
*5: This is recognized if Valid only on startup days is not selected.
*6: This is recognized again after the Reinstate operation is performed.
Action method
Take an appropriate action, for example change the settings, or change the status by performing an operation.
Action 7
Points to check
Does the job net history information show that a message event occurred immediately before or after job net startup and completion were output?
If a message event occurs at such times, on rare occasions the occurrence of the message event may not be recognized. The timing of this phenomenon will be within the short period when preprocessing for job net startup or postprocessing after job net termination is being performed. Occurrence of message events is not recognized during such preprocessing or postprocessing.
Action method
To receive message events while a job net is executing, display the Job Net Properties window for the job net that is to receive message events, click the Message tab, and select Valid during job net execution.
If the issue persists, make the generation of message events wait after job net termination by, for example, taking the sleep action for a few seconds.
