Setting SERVER statement configuration reference

Edit online

The SERVER statement is specified in the Data Protection for SAP profile, and in the IBM Storage Protect™ client option file.

There are corresponding keywords in the IBM Storage Protect client option file. Depending on the choice of password handling, some parameters are ignored. The corresponding sections in the Data Protection for SAP profile and the IBM Storage Protect client option file are established by using the logical server name. This logical server name is defined by the keywords SERVER or SERVERNAME.

Table 1. SERVER statement and appropriate profile and option file settings.
Configuration possibilities	Data Protection for SAP profileinit`SID`.utl	IBM Storage Protect client option file dsm.sys or`server`.opt^[2]
single path; no password or manual password	`SERVER server ADSMNODE node^[1]`	`SERVERNAME server TCPSERVERADDRESS address NODENAME do not specify`
single path; automatic password byIBM Storage Protect	`SERVER server ADSMNODE do not specify`	`SERVERNAME server NODENAME node TCPSERVERADDRESS address`
several paths/servers; no password or manual password	`SERVER server 1 ADSMNODE node 1 SERVER server 1 ADSMNODE node n`	`SERVERNAME server 1 NODENAME do not specify TCPSERVERADDRESS address 1 SERVERNAME server n NODENAME do not specify TCPSERVERADDRESS address n`
several paths/servers; automatic password byIBM Storage Protect^[3]	`SERVER server 1 ADSMNODE do not specify SERVER server n ADSMNODE do not specify`	`SERVERNAME server 1 NODENAME do not specify TCPSERVERADDRESS address 1 SERVERNAME server n NODENAME do not specify TCPSERVERADDRESS address n`
several paths/servers; automatic password byIBM Storage Protect^[4]	`SERVER server ADSMNODE do not specify TCP_ADDRESS address 1 SERVER server n ADSMNODE do not specify TCP_ADDRESS address n`	`SERVERNAME server NODENAME node TCPSERVERADDRESS address`

Notes:

[1]

If ADSMNODE is not specified, the host name is used.

[2]

On UNIX™ or Linux™, dsm.sys is the single client option file for all IBM Storage Protect servers.

On Windows™, there is a separate client option file server.opt for each IBM Storage Protect server.

[3]

If two different physical systems have the same IBM Storage Protect node name or if multiple paths are defined on one node by using several server stanzas, passwordaccess generate might work only for the first stanza that is used after password expiration. During the first client/server contact, the user is prompted for the same password for each server stanza separately. A copy of the password is stored for each stanza. When the password expires, a new password is generated for the stanza that connects the first client/server contact. All subsequent attempts to connect through other server stanzas fail because there is no logical link between their copies of the old password and the updated copy. The updated copy is generated by the first stanza that is used after password expiration. To avoid this situation, update the passwords before they expire. When the passwords are expired, run these tasks to update the password:

Run dsmadmc and update the password on the server.
Run dsmc -servername=stanza1 and use the new password to generate a valid entry.
Run dsmc -servername=stanza2 and use the new password to generate a valid entry.

[4]

If you are using IBM Storage Protect API 5.5 (or later), you can use the TCP_ADDRESS parameter in the Data Protection for SAP profile. This parameter eliminates the requirement to set multiple stanzas in the IBM Storage Protect client option file for multiple paths. The parameter also eliminates the problem when it updates the password (see [3]).

You must use IBM Storage Protect API 5.5 (or later), you can use the TCP_ADDRESS parameter in the Data Protection for SAP profile. This parameter eliminates the requirement to set multiple stanzas in the IBM Storage Protect client option file for multiple paths. The parameter also eliminates the problem when it updates the password (see [3]).