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
]
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
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
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
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
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
