When scripting command input, use CLI syntax as defined in this guide. For use with SSH or Telnet, use a space character between command names, parameters, and their values (as shown throughout this guide). For use with the HTTP or HTTPS interface, use a ’/’ character instead of a space character between command names, parameters, and their values.
When writing scripts to parse XML API output, use an XML library to parse the data. For parsing, a script should not rely on ordering, spacing, or column position. To find a specific property, a script should compare property names as it searches through the data. This allows the script to be compatible with future versions that could potentially add new fields to the output.
CAUTION:Because API format does not use confirmation prompts, use caution when scripting commands that may cause data unavailability or data loss.
The output of show commands is intended for monitoring or obtaining the current configuration. Other commands provide configuration data and display one or more status objects that specify the status of command processing. The last status object specifies the overall status of the command; other status objects indicate intermediate processing status.
The following example shows the API status object, using the
ipa output option:
In a script, each command should check the previous command’s status before proceeding. If the value of the status object’s
return-code property is 0, the command succeeded; any other value means that the command failed.
NOTE:If you script an operation to repeatedly add and remove disk groups, set a delay of at least two minutes between deleting a disk group and creating the next one.
Example command input and API output
The following example shows a command formatted for use with the command-line interface, the same command formatted for use with the HTTPS interface, and command output in the XML and JSON APIs.
Command-line interface format: create user JSmith interfaces wbi password Abc#1379