My OS/2 client works fine with PASSWORDACCESS GENERATE. It even works correct with OS/2 Security Enablement Services. Why you do not want to use it and prefer to include the password on command line?
Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Automating Scheduling service in OS/2 Hey All, I have a question relating to automating the scheduler on a os/2 client running TSM 3.7.2 client. What happens is upon boot up the os/2 machine calls a script which runs the following command "dsmc schedule -password =<password>". The problem is that this command fails unless I have logged in with the dsm command. So what I do currently is when the machine boots up I issue the dsm command, I then specify the password manually and finally I run the dsmc command with the scheduler option. I been looking through the manuals to find a command or some configuration settings to solve this problem but I haven't been able to find anything yet. I am fairly new to TSM and I would appreciate any help anyone could give. Oh by the way the Server is a NT machine running TSM 4.2.1 thanks in advance Paul
