We have a few old OS/2 machines running a Ver. 3.1 Client. We start the schedule in the startup.cmd file using the following command: start /b /min dsmc.exe schedule -password=XXXXX
These machines haven't needed attention for years, and I don't have time to dig up my notes, but I think that the /b specifies to start in the background, and /min specifies to run minimized. -----Original Message----- From: Paul Ward [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 5:47 PM To: [EMAIL PROTECTED] 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
