Data item
Description
Status
(Connection Status)
Specifies either Connection Successful, Error, Unknown, or "-"
depending on the status.
Last connection time
(Connected Time)
Specifies the last connection time.
Behavior of the setremoteconnections command
The following lists includes details about the behavior of the
setremoteconnections
command when
specifying an agentless connection-destination definition file for the
/file
option:
• The first line of the file is the header section output by the
setremoteconnections
command and is
ignored unconditionally. The second and subsequent lines are treated as agentless connection-
destination definitions.
• When you specify two or more agentless connection-destination definitions in the file, a single syntax
error in either definition causes the command to end with an error, and no agentless connection-
destination definitions are registered.
• The values of the data items output by the
listremoteconnections
command in CSV format are
enclosed in double quotation marks ("). However, if the values are not enclosed by double quotation
marks, they are not treated as errors. (This is because when you edit a CSV file in Excel, double
quotation marks are removed).
• If the value of the first data item (ID) of an agentless connection-destination definition is a null
character, the specified content is added as an agentless connection-destination definition.
• If a value is specified for the first data item (ID) of an agentless connection-destination definition, the
agentless connection-destination definition corresponding to the specified ID is updated with the
content specified in the line. If the agentless connection destination definition corresponding to the
specified ID does not exist, the system generates an error.
• When two or more agentless connection-destination definitions are specified in a file and the addition
or update portion of the definitions fails, the command results are as follows:
- A return value (warning, not error) is used to report a definition that was not successfully registered.
- Information is output as a standard error, which enables you to identify the definition that was not
successfully registered.
- The registration processing continues for all remaining definitions, even if an error occurs.
Usage example: Register or update the agentless connection-destination definitions in
Automation Director with the content of a specified file
setremoteconnection /file bbbbb /user xxxxx /password yyyyy
Example: Successful registration of agentless connection-destination definition
KNAE03000-I The setremoteconnection command will now start.
KNAE03002-E The remote connection definition was registered (ID:12345, line number: 12345).
Example: Unsuccessful registration or update
KNAE03000-I The setremoteconnection command will now start.
KNAE03002-E The setremoteconnection command ended abnormally (12345).
CLI commands
117