Re: Errors backing up a Digital Unix machine

Thanks for thw quick reply Andy.

The problem I am having is that we are starting to backup platforms which I
have no experience on, I don't even have accounts to login to them. while I
know ADSM, I have to work with people who know Unix, and we don't speak the
same language.

If you (the adsm developers) aren't going to enhance the message processing,
it would be really useful if all the vendor files discribing
errno=<something>, rc=<something>, win32rc=<something>, etc. could be put on
your website.

The current messages don't give me a clue as to how to resolve them.  Could
your ponder these additional items?

From the same client, what could be the root cause for the difference
between the messages with rc=104 and the ANS* messages?

02/04/1999 05:27:51 PrivIncrFileSpace: Received rc=104 from
fioGetDirEntries:  /analog  /asic_lib/rss06um/cadence/gyro3/lvn600h2/layout
02/04/1999 05:27:52 ANS1228E Sending of object
'/analog/asic_lib/rss06um/cadence/gyro3/r20k20k' failed 02/04/1999 05:27:52
ANS4005E Error processing '/analog/asic_lib/rss06um/cadence/gyro3/r20k20k':
file not found 02/04/1999 05:27:58 PrivIncrFileSpace: Received rc=104 from
fioGetDirEntries:  /analog  /asic_lib/rss06um/cadence/gyro3/lvreglo

Also the same client gave these messages and quit on the filespace it was
working on.  The errno 35 means EWOULDBLOCK 35 /* Operation would block */
Can you be my service representative like the ANS1028S message says?

02/04/1999 05:24:45 TransErrno: Unexpected error from acl_get_file, errno =
35 02/04/1999 05:24:45 ANS1028S Internal program error.  Please see your
service representative.

TIA,

--
--------------------------
--------------------------
Bill Colwell
Bill Colwell
C. S. Draper Lab
Cambridge, Ma.
bcolwell AT draper DOT com
--------------------------
In <8725670D.00799761.00 AT d53mta05h.boulder.ibm DOT com>, on 02/03/99
In <8725670D.00799761.00 AT d53mta05h.boulder.ibm DOT com>, on 02/03/99
   at 02:05 PM, Andy Raibeck <storman AT US.IBM DOT COM> said:

>Hi Bill,

>The rc=104 is an ADSM return code in this case, which are
>(as I am sure you already know) documented in the API header
>file dsmrc.h. From the header file:

>#define DSM_RC_FILE_NOT_FOUND      104 /* specified file not found
>          */

>Maybe something was going out and deleting files just before
>ADSM was able to back them up?

>By the way, you can usually differentiate between OS return
>codes and ADSM return codes. Typically the ADSM return code
>will say "rc=nnn", while the OS return code will say
>"errno=nnnn".

>Best regards,

>Andy

>Andy Raibeck
>IBM Storage Systems Division
>ADSM Client Development
>e-mail: storman AT us.ibm DOT com
>"The only dumb question is the one that goes unasked."

>We recently started backing up a large server running digital unix. The
>client is 3.1.0.6, the server is 3.1.2.1 on os/390.

>We are backing up lots of files but are also getting
>lots of these messages --

>02/03/1999 00:54:31 PrivIncrFileSpace: Received rc=104 from
>fioGetDirEntries:  /user1  /kmh4005/matlab/ds/divers_sonar1

>I know I should look up the rc in the clients errno.h file, and I did. The
>rc's listed go up to 103, skip 104, then list some higher ones! I am
>assuming the errno.h is downlevel from the executing os code. Does anyone
>have an up to date errno.h they can mail to me, or otherwise explain what
>the problem is?

>TIA,

>--
>--------------------------
>Bill Colwell
>C. S. Draper Lab
>Cambridge, Ma.
>bcolwell AT draper DOT com
>--------------------------