Password configuration matrix

Edit online

After you select the suitable password-handling method, follow this configuration matrix to set the password keywords and parameters.

Proceed as indicated by the step number.
Table 1. Password handling for UNIX™ or Linux™

Password handling parameters and profile actions in a UNIX or Linux environment.
Step Profile/Action Parameter Password
No Manual Set by IBM Storage Protect™
1 IBM Storage Protect admin AUTHENTICATION EXPIRATION PERIOD (see note 1) OFF ON n days (see note 2) ON n days
2 dsm.sys

PASSWORDACCESS

PASSWORDDIR (see note 5)

NODENAME

 Unavailable

PROMPT

Unavailable

Unavailable

.

GENERATE

path

nodename
3 IBM Storage Protect admin UPDATE NODE (see notes 1, 6) Unavailable password password
4 Data Protection for SAP profile (initSID.utl) For each SERVER statement, specify:

PASSWORDREQUIRED

ADSMNODE

  

NO

nodename

    		 

YES

nodename

    		 

NO

(see note 4)

   
5 Data Protection for SAP command line

Specify in each SERVER statement:

backint -p initSID.utl 
-f password
 Unavailable    password (See notes 3,7,8)    password (See notes 3,7,8)
6 Command line backom -c password Unavailable password (See notes 3, 7) password (See notes 3, 7
6 Command line backom -c password Unavailable password (See notes 3, 7) password (See notes 3, 7)
Note:
  1. See appropriate IBM Storage Protect documentation.
  2. If you are using manual password generation during testing, make sure that the expiration period is set to an appropriate time.
  3. This password must be the one that is effective on the IBM Storage Protect server for the node.
  4. ADSMNODE must not be set when PASSWORDACCESS generate is set.
  5. The users SIDadm and db2SID oraSID must have read and write permission for the path specified in the PASSWORDDIR option in the IBM Storage Protect client options file.
  6. This step is only necessary if the password is expired (manual-handling only) or must be changed on the IBM Storage Protect server.
  7. A password must be entered for each server statement in the Data Protection for SAP profile.
  8. When you use Oracle RMAN with PASSWORDACCESS GENERATE, backups must always be started with the same user ID provided in step 5 (setting of passwords).
  9. When you use PASSWORDACCESS GENERATE, the operations must always be used with the same user ID provided in step 5 (setting of passwords).