ADSM-L

Re: errors

1998-05-31 14:57:33
Subject: Re: errors
From: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Sun, 31 May 1998 14:57:33 -0400
An "errno" (error number) is a return code passed back to the application from
the operating system, usually when the operating system is unable to
successfully complete a request made by the application. errno values are
briefly documented in a file called errno.h. This file is provided with
development tools such as a C or C++ compiler. On most (if not all) UNIX
platforms you can find this file in /usr/include/sys (if you have the compiler
installed).

While most errno files names are errno.h, they may vary. For example, the
Windows version of this file is called WINERROR.H.

It is also important to note that errno values vary from one operating system
to another. For example, the errno values for AIX may differ from those for
other UNIX or non-UNIX platforms.

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 05/31/98 11:25:18 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: errors


Is there a place where the "average bear" can find this errno
information?

Thanks,

Hilary Whitehead
California Power Exchange

> -----Original Message-----
> From: Andrew Raibeck [SMTP:storman AT US.IBM DOT COM]
> Sent: Friday, May 29, 1998 9:13 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: errors
>
> The errno=74 means "ENOBUFS - No buffer space available" (this is from
> the
> errno.h file for your operating system). This usually happens when
> you've
> specified a TCPWINDOWSIZE setting that is larger than your TCP/IP
> configuration
> is set up to handle. On AIX you need to check the sb_max value (on AIX
> use the
> command "no -a" to determine the current sb_max). sb_max is expressed
> in bytes,
> so if you divide by 1,024, that will tell you the maximum setting you
> can use
> for TCPWINDOWSIZE. For example, if sb_max is 65,536, then the maximum
> TCPWINDOWSIZE value you can use is 64.
>
> Try lowering TCPWINDOWSIZE so that it is less than or equal to sb_max,
> and the
> messages should go away. Alternatively you can increase sb_max.
> IMPORTANT NOTE:
> sb_max is a system-wide TCP/IP setting. You should be familiar with
> tuning
> TCP/IP (or get help from someone who knows how to tune TCP/IP) before
> changing
> sb_max or any other system-wide TCP/IP settings.
>
> Andy
>
>
>
>
> Andy Raibeck
> IBM Storage Systems Division
> ADSM Client Development
> e-mail: storman AT us.ibm DOT com
>
>
>
> ADSM-L AT VM.MARIST DOT EDU on 05/29/98 08:31:36 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: errors
>
>
> Does anyone knows what these erros mean?
>
> 05/29/1998 09:24:32 commtcp.c ( 901): TcpOpen():
> setsockopt(SO_SNDBUF): errno =
> 74
> 05/29/1998 09:24:32 commtcp.c ( 912): TcpOpen():
> setsockopt(SO_RCVBUF): errno =
> 74
> 05/29/1998 09:24:32 commtcp.c ( 945): TcpOpen(): setsockopt failed on
> one or
> more options
>
> Thanks,
>
> *********************************
>   CARLOS E. SILESKY JIMENEZ
>          PH:(505) 277-7343
>     EMAIL: silesky AT unm DOT edu
>   <----------------------->
> *********************************
>
>
>



<Prev in Thread] Current Thread [Next in Thread>