ADSM-L

ADSM, BACKINT, & SAP R/3

1996-05-06 11:14:33
Subject: ADSM, BACKINT, & SAP R/3
From: John Viksne <viksnej AT VNET.IBM DOT COM>
Date: Mon, 6 May 1996 08:14:33 PDT
Hi Susan,


There are three places from which an ADSM unix client can get
the name used to connect with an ADSM server:
   1. The 'gethostname' system call
   2. The nodename from the dsm.sys file
   3. The nodename from the dsm.opt or from the command line
      (i.e. dsmc -nodename=mexico)

Number 1 is the default and the "adsm owner" of the files is the
login uid.

When entered, #2 overrides #1 and the "adsm owner" is again the
login uid.  This allows not only the override, but multiple
adsm nodenames for the same physical workstation.  One could
have multiple stanza names is the dsm.sys file, going to the
same or different servers, with separate nodenames.  If password
generate is used this would save separate passwords for each
stanza name.  This could be invoked using the command line
(dsmc -server=xxx) or using the DSM_CONFIG environment variable
to point to different dsm.opt files.

The #3 option was meant to be temporary pretend - it requires
the user enter a password even if password generate is indicated
in the dsm.sys file.  This mode does NOT use the login id for
adsm owner.  Instead it gives access to all of the files
backed up under this nodename - i.e. virtual root authority.
The 'virtual root authority' is why there is a check to prevent
the nodename entered being the same as the 'gethostname'.

I'm not sure what you thought was gained by duplicating the
executable code and hope this explanation helps.    John Viksne
<Prev in Thread] Current Thread [Next in Thread>