Synopsis
jobschchkmsgevt message event name [-i <monitoring interval>] |
Description
The jobschchkmsgevt command is called by Wait for Message Event jobs.
It waits for message events (message events generated without a project name or job net name specified, and message events generated with a project and job net specified) generated for job nets where this command is executed as a job.
This command waits for messages generated after the command execution starts, and it ends when a message event being waited for is generated.
Options
message event name
Specify, using up to 12 bytes, the name of the message event that you want to wait for.
The name cannot contain a comma (,), space, or user-defined character.
-i interval
Specify the interval, from 1 to 3600 seconds, for checking the generation of message events. If this option is omitted, this check will be performed at an interval of 60 seconds.
Return Values
Return value | Meaning |
|---|---|
0 | Terminated normally |
Other than 0 | Terminated abnormally |
Command Location
Windows | Systemwalker Operation Manager installation directory\MpWalker.JM\bin |
Solaris | /usr/bin |
Cautions
This command can be executed only if it is registered as a Systemwalker Operation Manager job (Wait for Message Event job). It cannot be executed directly from the command prompt or by any means other than as a Systemwalker Operation Manager job.
This command cannot wait for message events generated for anything other than the job net where this command is executed.
This command waits only for message events generated in schedule servers. It cannot be executed in network jobs or Distributed Execution jobs.
There is no limit on the number of simultaneous executions of this command, but if a large number of instances of this command (Wait for Message Event job) is executed, there may be a delay before the command (job) ends. This is because access is concentrated on the message event occurrence history file.
If a message event occurs multiple times in the same monitoring interval, the message event that occurred first is output in the execution result.
Example
An example job definition that waits for message event "ABC" is shown below.
jobschchkmsgevt ABC |
Execution Result/Output Format
CM_MSGEVENT=ABC |
