See the chapter on "Automating Tasks" in the 5.1 client manual for
information on return codes from the command line client.
In Windows, return codes from the last command (or program) executed can
be detected via the %errorlevel% variable. For example:
dsmc incremental
echo TSM return code is %errorlevel%
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (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.
Michael Moore <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/02/2002 13:30
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Trapping TSM Messages on NT4 and W2K
Currently we are using the TSM scheduler service to drive the client
backups. But, the direction of our company is to use ESP (scheduling
package) to drive the backups and all TSM maintenance events (DB backups,
reclamation, storage pool backups etc.).
Our NT group will be responsible for the client backups. The problem they
are having is trapping error codes from the backup client. What I am
looking for is some code that traps the return code from the client, which
can be used by ESP to determine if the backup completed successfully or
not. For example, on our AIX clients, we allow a return code of 0 or 4.
The 0 or 4 is returned to the ESP task, and ESP compeletes the job as
normal. If the return code is anything else, ESP treats it as an abend,
and notification begins.
Thanks for any information!!
Michael Moore
VF Services Inc.
121 Smith Street
Greensboro, NC 27420-1488
Voice: 336-332-4423
Fax: 336-332-4544
