See the PRESCHEDULECMD and POSTSCHEDULECMD options in the 5.1 or 5.2
client manual for a discussion on how the exit code from the PRE/POST
commands affects the over-all return code from the client. Also see the
chapter on "Automating tasks" for a discussion on return codes issued by
the command line client/scheduler.
For TSM server-scheduled operations, you can use QUERY EVENT with the
FORMAT=DETAILED option to see the status and return code from the client.
While those won't tell you specifically whether the PRE/POSTSCHEDULECMD
option didn't work, a non-zero return code should prompt you to
investigate the client logs to see why they didn't get a return code of
zero (you can also bypass return code 4 if skipped files are not a
concern, at your own discretion). While you would still need to view the
client logs, at least you have an indicator of which specific clients to
look at, as opposed to having to look at all of them.
TSM versions prior to 5.1 did not reliable return codes, so this won't
help you with clients running pre-5.1 code.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
brian welsh <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
09/11/2003 06:02
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: How to check exit-code pre- and postschedule
commands?
Hello,
TSM-server AIX 5.1 and TSM 4.2.2.8
TSM-clients Windows and UNIX
For some clients we are working with pre- and postschedule commands. It
sometimes happens, for some reason, a post-schedule command is not
executed
correctly and not executed at all. In the dsmsched.log the exit code is
not
0.
On server-site you see nothing at all and you don't know the post is not
executed correctly, but f.i. a database is not started, so we have a
problem.
I'm wondering how other administrators are checking the exit-codes of pre-
and postscheduled commands. Is there a way to do this without checkin the
client logfiles?
Thans,
Brian.
_________________________________________________________________
MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
