We do this all the time for about 200 NT and W2K nodes the way Andy has described with a product called Control-M. The only issue we have ever had is Control-M loses its registry stuff every now and then and the backup does not complete at all. ESP may not have this problem. To alleviate this, each day, I run a post task on the TSM server to compare the begin and end dates for all filespaces and generate a report of the ones that have not backed up.
I am doing this under V4.2.2. Supposedly, under V5.1 the return codes are more consistent, but I have never seen a problem under V4.2.2. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: Andy Raibeck [mailto:[EMAIL PROTECTED]] Sent: Saturday, August 03, 2002 1:40 AM To: [EMAIL PROTECTED] Subject: Re: Trapping TSM Messages on NT4 and W2K 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
