The OSCMD keyword tells CA Automation Point to issue an operating system command to the session that sent the current message. For example, you could use the OSCMD keyword to invoke a CA OPS/MVS REXX program.
This keyword has the following format:
OSCMD(commandtext)
or
OSCMD((commandtext) SESSION(sessid))
Specifies the text of the command. If you specify the SESSION operand, the OSCMD keyword directs the operating system command to the indicated session (specified by sessid), rather than to the session that generated the message.
Specifies the session to which the OSCMD command is to be directed. This operand cannot be used to specify the name of an internal session (AXC, VOX, or OPS).
Usage Note:
If you use the OSCMD keyword in a time rule, the SESSION operand is required because time events are not associated with specific sessions.
Example:
The following message indicates that CA OPS/MVS is active:
OPS0123O AOF INITIALIZATION COMPLETE
The following rule issues a command to CA OPS/MVS indicating that CA Automation Point is active and ready for CA OPS/MVS to use it:
MSGID(OPS0123O), OSCMD(AXC HERE)
|
Copyright © 2012 CA Technologies.
All rights reserved.
|
|