ADSM-L

Upgrade to TSM client 5.2.3.0 Benefit or Nuisance.

2004-07-08 12:19:03
Subject: Upgrade to TSM client 5.2.3.0 Benefit or Nuisance.
From: Joe Pendergast <JPendergast AT WATSONPHARM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 8 Jul 2004 09:18:41 -0700
I have just upgraded my TSM clients and server to 5.2.3.0 on the AIX
5.2.0.0 systems, and come across an interesting new message.

ANS1115W File '/oracle/stage' excluded by Include/Exclude list

This new output message is repeated for each directory that I have excluded
in the inclexcl listing.  They appear on screen during an interactive
backup (dsmc i) and are also placed in the schedule log (dsmsched.log) on
scheduled backups.

Benefit = The administrator can analyze the results of the inclexcl file
changes by executing a backup.
Detriment = Programs scanning for "W"arning messages will show this purely
"I"nformative message.

Problem observed:  An interactive backup (executed in a ksh script) now
exits with a return code of "4" indicating files have been skipped.  Yes, I
agree, the files have been skipped, but they were skipped by design.
Previously my special (ksh) backup processes completed normally (return
code 0), and now they complete with an error (return code 4).

TSM support response:  The message and return code are working as designed.

If any of the technical people in this list agree that the files skipped
because of the inclexcl list should not trigger a return code 4, please
contact TSM support and tell them.

I appreciate any workaround ideas to keep my "ksh" backups from failing
with return code 4 as a result of the inclexcl statements.  I would still
like to see the return code 4 if there were truly "failed" files.