Re: Automating Scheduling service in OS/2
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=X 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
Re: Automating Scheduling service in OS/2
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
Re: Automating Scheduling service in OS/2
We have the following in a dir d:\autoapp (all the *.cmd files get run on reboot) and in tsmc.cmd is the following d: cd d:\tsmdir start /min /c TSM Client - Scheduler d:\tsmdir\dsmc schedule -password=whatever FYI Tim Williams -Original Message- From: Paul Ward [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 7: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
Memo: Re: Automating Scheduling service in OS/2
The problem that I am encountering is that upon reboot the machine calls the following script from the startup.cmd instSchd.cmd the instSchd.cmd is a script that is generated when you use the configuration wizard to configure the scheduler the script contains the following: C: CD \tivoli\tsm\client\ba start TSM Client Scheduler dsmc schedule -password=cgdadmin what I have found is that when the machine reboots this script continues to fail unless I start up to the client gui using the dsm command and login with the user name and password. Once I have done this everything works fine. my dsm.opt file contains the following: NODENAME HIE0541 TCPSERVERADDRESS 165.140.7.93 PASSWORDACCESS GENERATE What I am thinking right now is perhaps there is something that has to be set on the server side Paul Zlatko Krastev [EMAIL PROTECTED] on 22 May 2002 05:33 Sent by:ADSM: Dist Stor Manager [EMAIL PROTECTED] To:[EMAIL PROTECTED] cc: Our Ref: Your Ref: Subject:Re: Automating Scheduling service in OS/2 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
Memo: Re: Automating Scheduling service in OS/2
Nick, I tired what you suggested but I am still stuck. When the dsmc schedule command is run it prompts for a password. When I enter the password I either get a ANS107E session rejected error or I get ANS1353E error. However once I fire up the GUI and login with the password I can run the dsmc schedule command with no problems. I am just wondering if I have something set incorrectly on the Server. Paul