Memo: Re: Automating Scheduling service in OS/2
2002-05-22 14:29:29
Subject: |
Memo: Re: Automating Scheduling service in OS/2 |
From: |
Paul Ward <paul_ward AT HSBC DOT CA> |
Date: |
Wed, 22 May 2002 11:23:13 -0700 |
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 <acit AT VM.MARIST DOT EDU> on 22 May 2002 05:33
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
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" <ADSM-L AT VM.MARIST DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Memo: Re: Automating Scheduling service in OS/2,
Paul Ward <=
|
|
|