ADSM-L

Re: Passwordaccess generate failing

2002-06-27 13:14:59
Subject: Re: Passwordaccess generate failing
From: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
Date: Thu, 27 Jun 2002 13:12:59 -0400
To clear the slate, do this.
Change password at the server for this node.
Set client to passwordaccess generate.  (make sure you have
killed or stopped any scheduler running on client).
On client do a dsmc, then a "q ses" you should be prompted
for password.  After getting q ses output, then quit and try again
and you shouldn't be prompted for password this time.

Then restart your scheduler.

David Longo

>>> John.Luscombe AT CONCORDIA DOT CH 06/27/02 10:59AM >>>
Hi listers,

You'll have to forgive me, I'm a bit of a TSM novice.

We have TSM 4.2.something running under AIX. Our DB2 guy had a problem
moving a table from one client node to another. He did some reading that
suggested changing the password at the server to a known value, and
switching off passwordaccess generate at the client. I did this, no
problems, he was able to restore his tables.

The problem now is, how do I get it back to the way it was before? I've done
some reading through archives, but must be missing something.

When I have passwordaccess prompt, I can do a dsmc sched, and enter the
userid and password as set on the server, no problems. But as soon as I
switch on access generate and do a dsmc sched and enter the userid, then it
bombs immediately. I'm guessing what's happening is that the client is
sending the encrypted password back to the server which of course doesn't
match. But how do I get them back in sync.

Thanks for your help

Frustrated beginner.



"MMS <health-first.org>" made the following
 annotations on 06/27/2002 01:14:22 PM
------------------------------------------------------------------------------
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or 
privilege is waived or lost by any mistransmission.  If you receive this 
message in error, please immediately delete it and all copies of it from your 
system, destroy any hard copies of it, and notify the sender.  You must not, 
directly or indirectly, use, disclose, distribute, print, or copy any part of 
this message if you are not the intended recipient.  Health First reserves the 
right to monitor all e-mail communications through its networks.  Any views or 
opinions expressed in this message are solely those of the individual sender, 
except (1) where the message states such views or opinions are on behalf of a 
particular entity;  and (2) the sender is authorized by the entity to give such 
views or opinions.
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or 
privilege is waived or lost by any mistransmission.  If you receive this 
message in error, please immediately delete it and all copies of it from your 
system, destroy any hard copies of it, and notify the sender.  You must not, 
directly or indirectly, use, disclose, distribute, print, or copy any part of 
this message if you are not the intended recipient.  Health First reserves the 
right to monitor all e-mail communications through its networks.  Any views or 
opinions expressed in this message are solely those of the individual sender, 
except (1) where the message states such views or opinions are on behalf of a 
particular entity;  and (2) the sender is authorized by the entity to give such 
views or opinions.

 ===========================================================================
<Prev in Thread] Current Thread [Next in Thread>