Is this a UNIX client? If so, are you coding NODENAME in the dsm.opt file?
PASSWORDACCESS GENERATE does not work if you code NODENAME in dsm.opt. If you
put it in dsm.opt, then ADSM assumes you want to be the "virtual root user",
which gives you access to all of that node's data, requiring you to enter a
password. Instead, put NODENAME in the dsm.sys file.
As far as allowing you to code a nodename that matches the machine name... I am
not aware of such a restriction. What is the exact text of the error message
you are getting (including the ANSxxxxx message code)? What operating
system/version is your client running? What do your dsm.opt and dsm.sys files
look like?
Oh yes, make sure you are at the latest V2 ADSM client code.
Andy
Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
ADSM-L AT VM.MARIST DOT EDU
03/16/98 09:34 PM
Please respond to jdschn AT ibm DOT net @ internet
To: ADSM-L AT VM.MARIST DOT EDU @ internet
cc:
Subject: Question about "Nodename" parameter
Greetings,
This list is a big help. My thanks to all you who contribute.
If this question has been discussed lots of times, just point me
to the archives, and I will get the answer myself, but I took this
to IBM ADSM Level 1, and they told me I was not experiencing a bug,
but ADSM was "working as designed".
I am trying to get "passwordaccess generate" to work on a node called
"father". When I put "nodename father" in the client options file
it doesn't work. I get an error when I bring up 'dsmc' that says
the nodename *can't* be the same as the actual node name. Why is
there any such restriction? Why can't I call the node what I
want?
But as if that wasn't strange enough, when I take the "nodename"
line completely out, the client 'dsmc' comes up fine, and uses the
actual node name of the node, just like I wanted to do originally.
Why does this inconsistancy exist?
The reason I care is that "passwordaccess generate" doesn't seem to
work unless you leave the "nodename" line out. If you specify a
nodename other than the real nodename of the machine in the "nodename"
line, the "passwordaccess generate" line in the systems option file
seems to be ignored. Does anybody know why that is?
I have been helping out at a company who uses nodenames other than
the real machine nodename because they always thought they had to.
They have these nodenamed embedded in scripts and it would be a real
pain to change it all now. But they would like "passwordaccess
generate" to work, otherwise they have to imbed passwords in a script
to bring up the client, which is not too cool.
I am running the latest 2.1 client, (and server, too, if that matters).
Thanks in advance,
John Schneider
***********************************************************************
* John D. Schneider * Email: jdschn AT ibm DOT net * Phone: 314-349-4556 *
* Lowery Systems, Inc. ***********************************************
* 275 Axminister * Disclaimer: Opinions expressed here are mine*
* Fenton, MO 63026 * and mine alone. My company is off the hook.*
***********************************************************************
|
