ADSM-L

Re: ADSM scheduler

1999-11-04 21:02:21
Subject: Re: ADSM scheduler
From: Andy Raibeck <storman AT US.IBM DOT COM>
Date: Thu, 4 Nov 1999 18:02:21 -0800
Hi Kyle and Birger,

Actually, if you get a Dr. Watson failure from an ADSM module,
you should call ADSM support (same goes for TSM) and provide
them with the Dr. Watson log. This helps get the problem to us
that much sooner, and reduces the number of vendors you need to
contact.

This problem in particular looks like APAR IC23396, which the
fixtest I posted about earlier today (version 3.1.0.7f2) will
address. Try it, and see if it helps.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

I have 2 comments.

First, Usually when you get a Dr. Watson error you get a drwtsn32.log file
created in C:\winnt.  This file can be sent to Microsoft to get a better
idea of what was going on at the time.  You may have know that but some
people on the list might find that useful.  Usually MS can say that a
certain DLL is causing the problem.  Then armed with that you can call ADSM
support and tell them what to look at.

Second, was the scheduler create automatically or by the dsmcutil.exe
command.  I have had sporadic unexplainable (because I didn't send a log
file to MS) Dr. Watson errors after using the dsmcutil.exe.  In my case
making sure I used 8.3 naming for the paths on all options being passed to
the dsmcutil command fixed my problem.  Even if this scheduler was created
from a normal install I might recreate it using the dsmcutil command.  Here
is what I put in a batch file to accomplish this.

rem //////////////////////////////////////////////////////////////////
rem Use this Batch File to create an ADSM Scheduler Service
rem Before you run it replace:
rem 1) Replace "********" with the actual node name for the client.
rem 2) Replace SERVER with the name of the server you are backing up
rem    to or simply remove it.
rem 3) Replace "######" with the actual password.
rem 4) The following 3 files must be in the /clientdir:
rem    A. dsm.opt
rem    B. dscament.txt
rem    C. dsmcsvc.exe
rem    If the /clientdir is the baclient folder then this is no
rem    problem because the files are there.  This is more important
rem    when you want to have multiple schedulers running on the same
rem    node.   In this case I recommend using different folders
rem    because it will use the file called dsm.opt even if you have
rem    another file specified for /optfile.
rem
rem  5) The reason you need to specify the /schedlog and /errorlog is
rem     because the options for them in the dsm.opt file are ignored.
rem     That means they won't go where you say you want them in the
rem     dsm.opt.  They will go to their default locations.
rem
rem //////////////////////////////////////////////////////////////////
rem
set A=dsmcutil install /name:"ADSM Central Scheduler SERVER"
set B=/clientdir:"C:\Progra~1\IBM\ADSM\Baclient\SERVER"
set C=/password:###### /autostart:Yes
set D=/OPTFILE:"C:\Progra~1\IBM\ADSM\Baclient\SERVER\dsm.opt"
set E=/SCHEDLOG:"C:\Progra~1\IBM\ADSM\SERVER_dsmsched.log"
set F=/ERRORLOG:"C:\Progra~1\IBM\ADSM\SERVER_dsmerror.log"
set G=/NODE:"********"
%A% %B% %C% %D% %E% %F% %G%
rem //////////////////////////////////////////////////////////////////

Hope this helps.

Kyle

<Prev in Thread] Current Thread [Next in Thread>