PASSWORDACCESS=generate is not allowed when using -adsmnode and -adsmpwd.
This is a security restriction imposed by the TSM API.  To use the new
node name with
PASSWORDACCESS generate you have to:
1. copy dsm.opt to dsmnew.opt
2. update node name  in dsmnew.opt to new node name
3. run: domdsmc q adsm -adsmoptfile=dsmnew.opt -adsmpwd=<pwd>

Now,  the password for the new node is generated;  and,  you should be
able
to run any command without being prompted for the password as long as
you specify the -adsoptfile=domnew.opt option.

Eduardo





Lawrence Clark <Larry_Clark AT THRUWAY.STATE.NY DOT US>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/18/2005 07:01 AM
Please respond to
"ADSM: Dist Stor Manager"


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Lotus Domino scheduled backup error






Hi:
We changed the Lotus client to a new node name, have
passwordaccess=generate in the dsm.opt for the client.
It runs via a scheduled process starting a script.
The script is the same as the previous client, with the new node name
and password.

Below is the error message generated, with an explanation that is
meaningless to me.
What does 'set clientNodeNameP to NULL' mean?

ANS0237E On dsmInit, the node is not allowed when
PASSWORDACCESS=generate.


Explanation: PASSWORDACCESS=generate establishes a session with the
current hostname as the node.

System Action: The system returns to the calling procedure.

User Response: When using PASSWORDACCESS=generate, set clientNodeNameP
to NULL.