Guidelines for Issuing OPSCMD

When you are issuing OPSCMD in automation procedures, follow these guidelines:

In coded automation procedures, such as CLISTs or OPS/REXX programs, always specify the complete text of command processors and their keywords and operands. Doing so avoids syntax ambiguity in the future as we add new command processors to CA OPS/MVS.
The length of all operands for the CAPTURE, STOPMSG, and STOPRESP keywords, added together, cannot exceed 1240 bytes.
Since the CA OPS/MVS MSF component sends only 320 bytes of OPSCMD text to a remote system, you should limit the length of CAPTURE, STOPMSG, and STOPRESP operands accordingly.
OPSCMD does not support the command stacking delimiter.