All parameter names of the commands are case-insensitive, however the values assigned to them may not be. For example, a path name on Windows might be case-insensitive, on Linux it will definitely not be case-insensitive.
As mentioned above in the chapter dealing with the batch interface, parameters can be preceded by a hyphen (-) but this is optional. When coding a batch file it is recommended to use this preceding hyphen to avoid any ambiguity.
The CLI uses the blank as a delimiter to separate parameters, options and commands. If a parameter value contains a blank, then the parameter value should be enclosed in quotes. As these quotes should not be interpreted by a shell or command prompt but by the CLI, it might be necessary to escape the quotes from a shell or command prompt by preceding backslashes (\).
Note: The CLI reports errors only on parameters not known to the CLI or to inconsistent parameters. If a parameter is coded with a command or action that is not mentioned in the syntax description (but it is a defined parameter of the CLI and used by other commands), then the parameter is ignored for the coded command or action. No error or warning is displayed.
|
Copyright © 2013 CA.
All rights reserved.
|
|