ADSM-L

Re: schedule failing to start on client

2004-11-16 15:39:21
Subject: Re: schedule failing to start on client
From: Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 16 Nov 2004 14:38:18 -0600
For anyone that was curious, Andy's ofm suggestion seems to have taken
care of it.  The ofm does load after sms/dsmcad in the autoexec.ncf, so
I'm not sure why this was a problem, but it apparently was.  I unloaded
dsmcad, ofm, and sms, then reloaded sms, dsmcad, and ofm, in that order.
 It seems to be working now.


Troy Frank
Network Services
University of Wisconsin Medical Foundation
608.829.5384

>>> storman AT US.IBM DOT COM 11/16/2004 2:08:12 PM >>>
Try turning off St. Bernard's OFM before starting dsmcad (if you are
using
OFM).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" < ADSM-L AT VM.MARIST DOT EDU > wrote on 11/16/2004
11:21:01:

> We've got a 5.2.2.2 server, and the client in question is a Netware
> 5.1sp7 box running tsmclient 5.2.2.3. The dsmcad service is loaded
and
> running, but when it tries to wake up and run its 9pm schedule, it
> fails. This is the message I get in dsmerror.log ...
>
> 11/16/2004 11:31:57 UseExternalTimer: Unable to read timer file
> '_T-00002.TMP', errno=4, error:Bad file number
> 11/16/2004 11:31:59 ANS1977E Dsmcad schedule invocation was
> unsuccessful - will try again.
>
> This is the message I see in dsmched.log ...
>
> 11/16/2004 07:51:11 The Scheduler is under the control of the TSM
> Scheduler Daemon
>
> The dsmwebcl.log shows this...
>
> Executing scheduled command now.
> ANS1977E Dsmcad schedule invocation was unsuccessful - will try
again.
>
> in 10 minutes.
>
> So far I've tried uninstalling/reinstalling the tsm client, but that
> didn't seem to fix it.
>
>
> Troy Frank
> Network Services
> University of Wisconsin Medical Foundation
> 608.829.5384
> Confidentiality Notice follows:
>
> The information in this message (and the documents attached to it,
if
any)
> is confidential and may be legally privileged. It is intended solely
for
> the addressee. Access to this message by anyone else is unauthorized.
If
> you are not the intended recipient, any disclosure, copying,
distribution
> or any action taken, or omitted to be taken in reliance on it is
> prohibited and may be unlawful. If you have received this message in
> error, please delete all electronic copies of this message (and the
> documents attached to it, if any), destroy any hard copies you may
have
> created and notify me immediately by replying to this email. Thank
you.
Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.