If you run it from the command line, despite the fact that it succeeds, what
errorlevel does your script exit with?  What errorlevel does your
d:\oracle\ora81\bin\rman command exit with?

Alex Paschal
Storage Administrator
Freightliner, LLC
(503) 745-6850 phone/vmail


-----Original Message-----
From: Koen Willems [mailto:koen_willems AT HOTMAIL DOT COM]
Sent: Thursday, November 21, 2002 7:02 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: scheduler fails on tdp command scripts (still drives me
nuts )


Del,

You are right echo comes with output c:\test.txt

So how whats wrong with my script ?

I still get a return code 3

orcschedppim.cmd

rem ==================================================
rem orcsched.cmd
rem ==================================================

rem ==================================================
rem set rman executable
rem ==================================================
set ora_exe=d:\oracle\ora81\bin\rman

rem ==================================================
rem set script and log directory
rem ==================================================
rem set ora_script_dir=d:\oracle\scripts\
set ora_script_dir=c:\progra~1\tivoli\tsm\agentoba\
rem ==================================================
rem run the backup script
rem ==================================================

%ora_exe% target system/manager@ppim rcvcat rman_db1/rman_db1@orcl cmdfile
bkdbppim.scr msglog bkdbppim.log

bkdbppim.scr

run
{
   allocate channel t1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=C:\Progra~1\Tivoli\TSM\AgentOBA\tdpoppim.opt)';
   allocate channel t2 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=C:\Progra~1\Tivoli\TSM\AgentOBA\tdpoppim.opt)';
      backup
      filesperset 5
      format 'df_%t_%s_%p'
      (database);

   release channel t1;
   release channel t2;
}

Best Regards,

Koen Willems



>From: Del Hoobler <hoobler AT US.IBM DOT COM>
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: scheduler fails on tdp command scripts (still  drives me nuts
>)
>Date: Thu, 21 Nov 2002 09:01:38 -0500
>
>Koen,
>
>How do you *know* the script isn't running?
>>From the schedule log... it appears that it is.
>And something within the script is failing
>and reflecting the RC=3.
>Add some
>       echo Doing xxxxx >> C:\TEMP\SCRIPT.OUT
>statements to your script to find out for sure
>if it is running and where it might be failing.
>(Change "xxxx" to be what the script is doing at
>the time.)
>
>Thanks,
>
>Del
>
>----------------------------------------------------
>
>Del Hoobler
>IBM Corporation
>hoobler AT us.ibm DOT com
>
>- Never cut what can be untied.
>- Commit yourself to constant improvement.


_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail