Hi,

I enclosed two separate notes I previously posted to this forum
to try to explain this situation.  The confusion comes from
trying to overload the use of the "nodename" option - there is
a trade off between this and naming yet another option - in this
case a new name for the nodename use in dsm.sys may have been the
better choice.      John Viksne

Subject: Re: Problems with PASSWORDACCESS GENERATE option

The nodename option is used in two ways:

1.(The original usage) If the nodename is entered either on the
command line or in the dsm.opt file it allows workstationA to
pretend to be workstationB.  This will prompt the user for
the password, irrespective of the PASSWORDACCESS option.

2.The ADSM client's name is (usually) the hostname on the workstation.
This, however, is uppercased when sent to the ADSM server and
'sunxyz' client is the same as 'SUNxyz'.  The nodename option
in the dsm.sys file can be used to override the usage of the hostname.
Passwordaccess option works as if the hostname were used.
                                   John Viksne

Subject: ADSM, BACKINT, & SAP R/3

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

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