You don't indicate which TSM client and server versions you are running,
nor do you indicate what the scheduled event is doing. In general, though,
I would say that this behavior is a probable bug and should be reported to
IBM support.
--------------------------------------------------
Starting with version 5.1, the output from QUERY EVENT FORMAT=DETAILED
should more accurately reflect the status of the scheduled event (See the
chapter on "Automating Tasks", section "Return codes from the command line
interface" in the client manual for details). As I mentioned above, you
did not say what the scheduled command was. However, some caveats for
scheduled events where ACTION=COMMAND:
1) If the command ends with a nonzero return code that is less than 12,
the event will be reported as "Complete" (note that QUERY EVENT
FORMAT=DETAILED will show the return code). This problem is described in
APAR IC35203.
2) If the command is executed asynchronously, then it is not possible for
TSM to track the outcome, in which case the event will be reported as
"Complete" with return code 0. For example:
;my script
start command1 ;command1 launched asynchronously
exit lastrc ;command1 launched successfully, exits with rc 0
Note: the "scripts" in this post are written in a "pseudo" code to
illustrate my meaning, and do not represent actual working scripts.
If you wish to see a more accurate status reported to TSM, then the
command should be configured to run synchronously (if possible). For
example:
;my modified script
command1 ;run command1, wait for completion
exit lastrc ;exits with rc from command1
3) If the command is a script that includes several commands, and each of
those commands may or may not end with return code 0, but ultimately the
script exits with a return code of 0, then the event will be reported as
"Complete" with return code 0. For instance, if the script does this:
;my script
command1 ;fails with lastrc = 4
command2 ;succeeds with lastrc = 0
exit lastrc ;exits with rc 0
In this case, if you wish to see a more accurate status reported to TSM,
then the script will need to be modified to exit with a nonzero return
code as appropriate (i.e. the script will need to track the return code
from each command within the script, then exit with a nonzero return code
if any command fails). For instance:
;my modified script to exit with highest rc
set scriptrc = 0 ;initialize scriptrc
command1 ;fails with lastrc = 4
if lastrc > scriptrc then scriptrc = lastrc ;scriptrc = 4
command2 ;succeeds with lastrc = 0
if lastrc > scriptrc then scriptrc = lastrc ;scriptrc still = 4
exit scriptrc ;exits with rc 4
If the script contains commands that execute asynchronously, then it is
not possible for the script (or TSM) to track the outcome of the
asynchronous command(s). Refer to (2) above.
--------------------------------------------------
If you are not using the 5.1 client, then try the 5.1 client to see if it
makes a difference. If the 5.1 client still violates the behaviors
described above, then this is (probably) a bug and should be reported to
IBM support. For example, I would expect that 5.1 should report a
completion status of "Failed" for the behavior you describe.
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.eyebm DOT com (change eye to i to reply)
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
shekhar Dhotre <Shekhar.Dhotre AT LENDLEASEREI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/27/2002 13:07
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: TSM Scheduler shows backups completed successfully
dsmerror.log shows
backups failed ?
Hi All ,
q eve * * shows all backups are completing successfully but clients
dsmerror.log file shows schedule command failed ,How I can verify that
these backups are completing successfully other than restore test?
26-12-2002 20:45:08 ANS1909E The scheduled command failed.
26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.
Retur
tsm: TSM>q eve * * begindate=today-1
Scheduled Start Actual Start Schedule Name Node Name Status
-------------------- -------------------- ------------- -------------
---------
12/26/02 01:00:00 12/26/02 01:02:06 AMERUAT_HOT_- F5N73 Completed
DAILY
12/26/02 01:58:42 12/26/02 01:58:44 F2N17_CMD F2N17 Completed
12/26/02 02:25:29 12/26/02 02:32:57 F3N45_DAILY_- F3N45 Completed
BACKUP
12/26/02 03:00:00 12/26/02 03:00:10 F2N29_DAILY_- F2N29 Completed
BACKUP
12/26/02 05:00:00 12/26/02 05:01:15 F3N47_DAILY_- F3N47 Completed
BACKUP
12/26/02 06:00:00 12/26/02 06:01:00 F3N43_DAILY_- F3N43 Completed
BACKUP
12/26/02 09:00:00 12/26/02 12:06:30 CPD39_DAILY_- F3N37 Completed
BACKUP
12/26/02 10:00:00 12/26/02 10:00:03 CPA35_DAILY F3N35 Completed
12/26/02 19:00:00 12/26/02 19:13:01 EMEAPROD_HOT- F2N21 Completed
_DAILY
12/26/02 19:18:00 12/26/02 19:19:30 SPCWS SPCWS01 Completed
12/26/02 19:35:00 12/26/02 19:48:18 TAHODEV_HOT_- F5N67 Completed
DAILY
more... (<ENTER> to continue, 'C' to cancel)
tsm: TSM>q eve * *
Scheduled Start Actual Start Schedule Name Node Name Status
-------------------- -------------------- ------------- -------------
---------
12/27/02 01:00:00 12/27/02 01:01:20 AMERUAT_HOT_- F5N73 Completed
DAILY
12/27/02 01:58:42 12/27/02 01:58:44 F2N17_CMD F2N17 Completed
12/27/02 02:25:29 12/27/02 02:32:59 F3N45_DAILY_- F3N45 Completed
BACKUP
12/27/02 03:00:00 12/27/02 03:44:02 APUAT0_COLD_- F5N73 Completed
DAILY
12/27/02 03:00:00 12/27/02 03:04:38 F2N29_DAILY_- F2N29 Completed
BACKUP
12/27/02 05:00:00 12/27/02 05:06:44 F3N47_DAILY_- F3N47 Completed
BACKUP
12/27/02 06:00:00 12/27/02 06:07:10 F3N43_DAILY_- F3N43 Completed
BACKUP
12/27/02 09:00:00 12/27/02 11:47:14 CPD39_DAILY_- F3N37 Completed
BACKUP
12/27/02 10:00:00 12/27/02 10:00:03 CPA35_DAILY F3N35 Completed
12/27/02 11:00:00 12/27/02 11:06:23 APPROD_HOT_D- F2N21 Completed
AILY
f2n21 /tsg/tsm>more dsmerror.log
26-12-2002 20:45:08 ANS1909E The scheduled command failed.
26-12-2002 20:45:08 ANS1512E Scheduled event 'EMEAPROD_HOT_DAILY' failed.
Retur
n code = 1.
27-12-2002 08:50:15 ANS1038S Invalid option specified
27-12-2002 08:50:15 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:31 ANS1038S Invalid option specified
27-12-2002 08:50:31 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:42 ANS1038S Invalid option specified
27-12-2002 08:50:42 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:50:56 ANS1038S Invalid option specified
27-12-2002 08:50:56 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:51:00 ANS1038S Invalid option specified
27-12-2002 08:51:00 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 08:51:05 ANS1038S Invalid option specified
27-12-2002 08:51:05 ANS1820E Command line options must be preceded by a
'-'
27-12-2002 13:10:19 ANS1909E The scheduled command failed.
27-12-2002 13:10:19 ANS1512E Scheduled event 'APPROD_HOT_DAILY' failed.
Return
code = 1.
27-12-2002 13:10:19 ANS1005E TCP/IP read error on socket = 6, errno = 73,
reason
: 'A connection with a remote socket was reset by that socket.'.
Thank You
SD
|
