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 the CA OPS/MVS product.
If you are invoking a command processor online, as you would during an interactive TSO session, you can (in most cases) use the shortest unique abbreviations. Be aware that the shortest unique abbreviation of a command processor, keyword, or operand can change from release to release.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|