Use the CMS command to run a CMS subset command, CP command, or EXEC on the CA VM:Director service virtual machine.
CMS {cmscommand | CP command | EXEC name}
A CMS subset command (not a user area module).
A CP command.
An EXEC, including any necessary parameters to pass to the EXEC.
When the CMS command transmits a CMS subset to CA VM:Director, the CMS subset active flag is set to prevent the execution of any user area modules. However, the CMS subset environment is not entered, and control always returns to CA VM:Director following the execution of the specified command.
The CMS command cannot execute a CMS or CP command that attempts a console read; it terminates abnormally if you give it such a command. If you must transmit such a command, build an EXEC that stacks the necessary command or commands before invoking it. For example, if you want to transmit the XEDIT command, build an EXEC that includes a final FFILE or QQUIT, before invoking XEDIT.
If the EXEC interpreter is being invoked, the command must begin with EXEC. CA VM:Director ignores the IMPEX flag setting.
If you transmit a CP command and the IMPCP flag is off, the command must begin with CP. If the IMPCP flag is on, the command need not begin with CP. CA VM:Director treats the command first as if it is a CMS command and then a CP command.
Note: For a description of the CMS SET IMPEX command and the CMS SET IMPCP command, see the IBM CMS Commands and Utilities Reference manual for your release of VM.
|
Copyright © 2014 CA.
All rights reserved.
|
|