Rene, This issue was hashed over in depth. The error you are seeing likely
comes only from Windoze clients and
not UNIX or Novel clients. Andy Railback explained the issue to me and it
has been fixed in a later release of the client
code... I kept Andy's note responding to my very same question:

>>>>>>>>>>>>>>>>begin included post>>>>>>>>>>>>>>>>>
Archives are not considered successful unless every file in your file spec
is backed up successfully. If one or more files fail, then the archive
will be flagged as failed.

The idea behind this is that archives are for long-term storage, and that
if you are looking to store the files for an extended period of time, it
is important that they *all* get archived. Thus anything other than 100%
of the files being archived will result in the failed event.

For the next release, we are planning on handling this a little
differently:

Scheduled backup-archive client operations where all the files are
processed successfully will have a status of "Success" and a return code
of 0 (zero). If the operation was invoked from the command line (or
script), dsmc will return '0' to the caller.

Scheduled backup-archive client operations where the *only* problems are
skipped files will have a status of "Success" and a return code of 4. If
the operation was invoked from the command line (or script), dsmc will
return '4' to the caller.

Thus the return code can be used to determine which events had skipped
files (and thus require further investigation) and which did not.

Standard caveat: This information is being provided on an informal basis,
and does not constitute any formal announcement or commitment.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




George Lesho <GLesho AT AFCE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/09/2002 14:04
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Return code=4 on scheduled backap



I have two TSM servers Win2K at 4.1.5 and AIX 433 at 4.1.4.5 with clients
at 4.1.3 across the board. I get this error for the Windows clients
consistantly but not the AIX clients. I have reported this to Tivoli but
their first line support person is insisting that there is a comms loss
which will be relfected in the tsm error log (but isn't). This error
occurs
when doing the FIRST incremental or an archive and doesn't appear to occur
in subsequent incrementals.  If anyone has an apar or reference that I can
pass back to the Tivoli support person, I would appreciate it.

George Lesho
AFC Enterprises




"Lambelet,Rene,VEVEY,GL-IS/CIS" <Rene.Lambelet AT NESTLE DOT COM>@VM.MARIST.EDU>
on 01/29/2002 08:38:20 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: George Lesho/Partners/AFC)
Fax to:
Subject:  Incr failed with ANS1076E *** Directory path not found ***


Hi,
on 2 of our 30 AIX clients (4.2.1.15), the incremental backup does its job
but finish with RC=4. This with schedules or with manual incr.
Error message ANS1076E *** Directory path not found *** is given right
after
start of the session.

AIX is at 4.3.3-ML09

Our TSM server is 4.1.4.0, OS/390. The error is given by first incremental
for the node too, after rename of old backups.

Any cue ?

>               René Lambelet
>               Center Information System, Nestec Ltd
>               tel + 41 21 924 3543
>               fax + 41 21 924 1369
> visit the Nestle site: http://www.nestle.com
>
>
root@ivev2104:/etc/adsm/ # dsmc i
Tivoli Storage Manager
*** Fixtest, Please see README file for more information ***
Command Line Backup Client Interface - Version 4, Release 2, Level 1.15
(C) Copyright IBM Corporation, 1990, 2001, All Rights Reserved.

Node Name: IVEV2104
Session established with server HQVTSM2P: MVS
  Server Version 4, Release 1, Level 4.0
  Data compression forced on by the server
  Server date/time: 01/29/02   14:02:58  Last access: 01/29/02   14:02:49

ANS1076E *** Directory path not found ***
^C