CmsConfig setsys command

Edit online

On a Linux® client system, use the CmsConfig setsys command to set the path of the client system-options file (typically dsm.sys) to an existing node definition without first reading the contents of the client system-options file.

This command can be helpful if the client system-options file does not have a typical name or is in a non-default location.

Requirement: If the node definition does not exist, you must first issue the CmsConfig addnode command to create the node definition.

Unlike the CmsConfig discover command, the CmsConfig setsys command does not create associated log definitions in the client-configuration.xml file. You must use the CmsComfog addlog command to create the log definitions.

Syntax

Parameters

nodeName: The client node name that is associated with the log files. For most client systems, only one node name is registered to the IBM Storage Protect server. However, on systems with multiple users, such as Linux client systems, there can be more than one client node name. This parameter is required.
sysPath: The fully qualified path of the client system-options file. This parameter is required.
Example: /opt/backup_tools/tivoli/tsm/baclient/dsm.sys

Example

Set the client system-options file path for the node SUSAN. The path for the client system-options file is /opt/tivoli/tsm/client/ba/bin/dsm.sys.

Issue the following command, from the /opt/tivoli/tsm/cms/bin directory.

Command:

./CmsConfig.sh setopt SUSAN /opt/tivoli/tsm/client/ba/bin/dsm.sys

Output:


Adding node configuration file.

Finished adding client configuration file.