Memo: Re: Automating Scheduling service in OS/2

2002-05-22 Thread Paul Ward 

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

2002-05-22 Thread Paul Ward 

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