If you have a TSM administrator's id, you can use that with
virtualnodename option, instead of needing the individual client
password, but from your email I assume you do not have an
administrator's id.

But you probably DO know the TSM name of the machine you are likely to
use to recover if your machine is unavailable.

On YOUR machine, start the TSM client, pull down UTILITIES -> NODE
ACCESS LIST. 
OR alternatively, you can use the TSM command line command:  SET ACCESS.
Read about this in the book, or the HELP.

You can grant access to the recovery machine to restore your machine's
files.
No password required after the SET ACCESS is done.
(Of course, you have to plan ahead and do this BEFORE your machine
dies.)

Also under UTILITIES, you can change your own password, instead of
letting the TSM server do it.
If your TSM admin has set up to force password change every 30 days, and
you change it on day 29, the TSM server won't change it again.  So you
WILL know what it is.

Hope that helps.






-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Chris Rodgers
Sent: Thursday, December 16, 2004 1:31 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Passwordaccess Generate


> You shouldn't ever need to know it, there are other ways to do
> everything I can think of.
>
> What problem are you having that you need it for?
> Maybe I can tell you how to get around it....

My computer is backed up via TSM to my university's central ADSM server.
If I want to do anything which needs more than my own node password
(which I know), I have to raise a support request with them. For
password resets, these are set to something random which is then sent
out on paper arriving a day or two later! Therefore, if I want to be
able to recover files in the event of my machine dying (as I did this
afternoon), it's invaluable to have the node password so that I can use
the -virtualnodename option on another machine to get back my files more
quickly and get back to work.

Similarly, if a machine dies completely, one also has to wait for the
paper password to arrive before being able to get on with doing a bare
metal restore because of course the encrypted password dies with the
machine. Hmm...

Why has this facility (or the MAILPROG equivalent) been removed from
v5.3 and upwards? This seems a useful sort of thing to me.

Thanks,

Chris.