Thanks for the help,
As far as we know, the client did not drop its connection. Is there any way
this could occur if attempts were being made to use a broken network card
that was not being used by AIX/TSM but was in the machine? I understood that
Unix/AIX would prevent things like this affecting the rest of the machine.
Are the attempts to use the card causing TCP/IP to break / lose open
sockets???
Matt Warren.
>-----Original Message-----
>From: Richard Sims [mailto:[EMAIL PROTECTED]]
>Sent: 10 October 2000 12:38:PM
>To: [EMAIL PROTECTED]
>Subject: Re: TCP/IP error reason codes
>
>
>>The error message is a response to file being in use.
>>
>>0X00000020 The process cannot access the file because it
>is being used
>>by another process.
>>
>> -----Original Message-----
>> Could anyone tell me what 'Reason code 32' means in
>the following;
>> ANR8216W error sending data on socket 54. Reason code 32
>
>Nope. The ANR8216W error message refers to a data
>transmission problem,
>not file contention. TSM uses the term "Reason code" to be generic, in
>supporting multiple operating systems with their various terminologies.
>In Unix, the reason code is the errno value, which in this case refers
>to:
>
>EPIPE 32 Broken pipe
> A write on a pipe or socket for which
>there is no
> process to read the data. This
>condition normally
> generates a signal (SIGPIPE); the
>error is returned if
> the signal is caught or ignored, else
>the program is
> terminated.
>
>Basically, the client dropped its end of the connection.
>
> Richard Sims, BU
>
