On Jul 15, 12:01pm, David Abry wrote:
<=> Subject:
<=>Subject: Re: PASSWORD?
<=>To: ADSM-L AT VM.MARIST DOT EDU
<=>Date: Mon, 15 Jul 1996 12:01:19 -0400 (EDT)
<=>From: "David Abry" <dabry AT sicom2.riscman DOT com>
<=>In-Reply-To:  <31EB1422 AT msmail.clear.co DOT nz> from "Dianne Sharp" at 
Jul 15,
96 05:01:00 pm
<=>X-Mailer: ELM [version 2.4 PL24alpha3]
<=>Content-Type: text
<=>Content-Length: 355
<=>
<=>I set the dsm.opt file to PASSWORDACCESS=GENERATE.  Can anybody tell me
<=>what this exactly means and what my password is when I first login to the
<=>dsm?  Is my password the same as the password I used when registering the
<=>admin?  For example, reg admin <nodename> <password> ?  I tried all of
<=>the values and I still am unable to connect to the server.
<=> End of excerpt from David Abry

This allows you to avoid giving a password when you start a client session. (To
my knowledge, this does NOT work for admin sessions).

If I understand well, the mechanism is as follows.
You define or update your client in the ADSM server, giving it a password (say
PASS1).
The first time that your client tries to contact the server, it will prompt the
user for a password. Reply with PASS1. This will enable the client session to
work. Moreover, the password will be automatically updated to something else
(say PASS2), and stored both in the server and in a client file (don't know
which one). The next time the client will open a session to the server, it will
use the new password PASS2. Again PASS2 will be updated to something else on
both client and server. The same sort of processing will take place for each
new session that is started from that client.

Be aware that there is a bug (I have seen it with servers at 2.1.x.7 and .8,
and probably earlier versions as well. I am not sure about the client levels):
If too many sessions are started concurrently, The server get confused and
generates the error message

ANR9999D smexec.c(3129): Unknown Node Conversion State: -1
.

At that stage, there is a very good chance that some client sessions will be
aborted, and more importantly, that the server and client password information
get out of synch, forbidding any new sessions to successfuly connect. If this
happen, you will need to update the password of your client "by hand" on the
server, then start (e.g.) a dsmc session on your client, enter a command that
will force some chit-chat with the server (e.g. "q files").  at this stage, a
password will be asked. Reply with the password that you just gave on the
server. That should resynch server and client.

A (several?) PMRs has (have) been opened on this subject a long time ago (ours
was opened on May the 17th). I do not think that there is any fix available
yet, but in this case, I would be delighted to hear that I am wrong :-)

--
Regards
Regards

+-------------------+----------------------------------+---------------------+
| Francis Dequenne  | Systems Section                  |      /~~\  /~~\     |
| ECMWF             | e-mail: fdequenne AT ecmwf DOT int      |     /    \/    
\    |
| Shinfield Park    | Tel:    (+44 1734) 499361        |   ECMWF             |
| Reading           | Fax:    (+44 1734) 869450        |   ECMWF             |
| Berkshire RG2 9AX | Telex:  (+44 1734) 847908        |     \    /\    /    |
| United Kingdom    |                                  |      \__/  \__/     |
+-------------------+----------------------------------+---------------------+