Associating A Client Node With A Client Option Set - IBM E16RMLL-I - Tivoli Storage Manager Implementation Manual

Example 8-21 shows how to clone the client option set named WINDOWS to
another named WINDOWS_CLONE, replacing the VERBOSE option with the
QUIET option.
Example 8-21 Copying client option sets
tsm: ATLANTIC>
ANR2055I COPY CLOPTSET: Optionset WINDOWS copied to optionset WINDOWS_CLONE.
tsm: ATLANTIC>
ANR2053I DELETE CLIENTOPT: Option VERBOSE, sequence number 0,has been deleted
from optionset WINDOWS_CLONE.
tsm: ATLANTIC>
ANR2050I DEFINE CLIENTOPT: Option QUIET defined in optionset WINDOWS_CLONE.

8.3.5 Associating a client node with a client option set

The client node definition should be updated to use a client option set. You need
either system privilege, unrestricted policy privilege, or restricted policy privilege
for the policy domain to which the client node belongs to use the required update
node command.
Use the SQL select command to view the names of all the client option sets, as
shown in Example 8-22.
Example 8-22 Select command for client option sets
tsm: ATLANTIC>
OPTIONSET_NAME
------------------
AIX
WINDOWS
Example 8-23 shows how to associate the client node named MILES with the
client option set AIX.
Example 8-23 Associating a client with a client option set
tsm: ATLANTIC>
ANR2063I Node MILES updated.
copy cloptset windows windows_clone
delete clientopt windows_clone verbose
define clientopt windows_clone quiet ''
select * from cloptsets
DESCRIPTION
------------------
Include/Exclude
list for AIX
Systems
Include/Exclude
list for Windows
System
update node miles cloptset=aix
Chapter 8. Managing Tivoli Storage Manager
LAST_UPDATE_BY PROFILE
------------------ ----------
TSMADMIN1
TSMADMIN1
301