Dwight,
I guess it just depends upon whether you might have a security concern with
hard coding passwords into scripts - this will also cause a problem when a
password expires on the server (the period of which can be set of course)
afterwhich you'll either have to update your password in each one of your
scripts or on your server. It all comes down to how stringent your security
regulations are I guess... With 'passwordaccess generate' in your dsm.sys
you'll never have to faff about again!
Rgds,
David McClelland
---------------------------
Tivoli Storage Management Team
IBM EMEA Technical Centre,
Internet: [EMAIL PROTECTED]
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Ask again.
just add the
-pass=blah
to your dsmc incr and it shouldn't ask for the id...
dsmc incr -pass=blah <somedir>
now this would be with passwordaccess prompt which is what we run our unix
clients with...
Dwight
-----Original Message-----
From: Sean McNamara [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 03, 2001 10:21 AM
To: [EMAIL PROTECTED]
Subject: Ask again.
Good Morning,
I asked this question a bit earlier in the week and did not get much of a
response. I am simply trying to do a "dsmc incr <directory>" on a server
and it
asks for a user id (interactively). I am attempting to run this command as
part
of a scheduled job and have not been able to figure out how to pass it a
"return" in my unix script. Do I have to pass a return in the script or
can
I
set an option to avoid the user id request?
> Any ideas?
>
Sean
