CA VM:Director API commands return messages that can be trapped. The default destination for messages is the terminal of the user ID that issued the API command (if the command is in a program, this is the user ID that ran the program), but you can use the following options to redirect messages to multiple destinations. The calling application can parse messages in a file or program stack and use their information for any purpose.
Places all informational and error messages generated by the API command in a CMS file on the issuing user’s A‑disk.
By default, the name of this CMS file is the name of the command that generated the messages (for example, ADDENTRY). The filetype is always RESULTS.
To store the messages in a different file, specify that filename. If you do not specify a filename, the FILE option must be the last one on the command line.
If a file with the name filename RESULTS A does not exist on the issuing user ID A‑disk, CA VM:Director creates it. If the file does exist, CA VM:Director appends new messages to its end.
You cannot use the FILE option with the NOWAIT option.
Displays (MSG) or does not display (NOMSG) informational and error messages generated by the API command at the issuing user’s terminal.
Places all informational and error messages in the issuing user’s program stack: in first‑in, first‑out (FIFO) order or last‑in, first‑out (LIFO) order.
The STACK option cannot be used with the NOWAIT option.
The named REXX stem variable does one of the following:
Commands with a STEM option must be issued from a REXX program.
|
Copyright © 2014 CA.
All rights reserved.
|
|