I like your email address Mr. TSM_User.

I had not necessarily thought of it, but you are correct.  All incremental
backups for 4.2.3 client systems now show a return code of "4" in the Event
log.
This does make it much more difficult to extrapolate which systems need
their inclexcl files adjusted.





                      TSM_User
                      <[email protected]        To:       ADSM-L AT VM.MARIST 
DOT EDU
                      OM>                      cc:
                      Sent by: "ADSM:          Subject:  Re: Upgrade to TSM 
client 5.2.3.0 Benefit or Nuisance.
                      Dist Stor
                      Manager"
                      <[email protected]
                      .EDU>


                      07/08/2004 12:03
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"






I have not had a chance to test this yet but if your script is getting a
return code of 4 then it would seem that the event will also now get a
return code of 4 when a scheduled backup skips files that were excluded.



If that is true then that is insane.  A nice feature of the TSM Operational
report is to show you what backups completed but with skipped files.  Of
course it seems to use that return code to show you that.  Up until now you
could review those systems and determine if you want to add some excludes
or if you should take some measures to ensure the files get backed up.



Now it would seem nearly every backup will end with skipped files.  Its
obvious to me that this now will complicate getting a handle on what is
happening with the backups.



If this is really the way it works.  Not that I doubt Joe but it is hard to
believe it was done like that.  Why not have a return code of 2?



As for a work around.  I have written a script that opens up the
dsmerror.log and reviews the data and time stamp to get messages just for
the current nights backup.  From there I grep for errors like ANS4987E,
ANS4037E and maybe a few others.  These messages will show you that files
failed for different reasons.  You just can't rely on the return code now.



Joe Pendergast <JPendergast AT WATSONPHARM DOT COM> wrote:
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.


---------------------------------
Do you Yahoo!?
 Yahoo! Mail Address AutoComplete - You start. We finish.