It is unclear from your post.  Is IBM saying that there are 65k sockets in
finwait / finwait2 ?  Or just that there are no available sockets?  If you
have reserved a ton of ports, it is possible to artificially constrain the
system.  I was at a shop that had locked down all the ports ( in the name
of PCI ) except a few hundred and they were experiencing something similar.

Rob Schramm

On Thu, Apr 14, 2016, 10:50 AM Tracy Adams <[email protected]> wrote:

> So an update to my quest of knowledge...
> https://en.wikipedia.org/wiki/Unix_domain_socket and
> http://www.thomasstover.com/uds.html
>
> The bottom line is this form of "socket" is integral for any process to
> process communication not just networking, amy I going down the right path?
>
> ________________________________________
> From: IBM Mainframe Discussion List <[email protected]> on behalf
> of Tracy Adams <[email protected]>
> Sent: Thursday, April 14, 2016 9:38 AM
> To: [email protected]
> Subject: OMVS (TCPIP) internals question
>
> I am trying to understand the function of TCPIP and its "max sockets".  We
> are experiencing a problem that happens infrequently where our CICS
> application closing down the DataPower port with an error that indicates
> max sockets has been reached.  IBM support has confirmed this in a dump.
> They say our max and current values are at 65,535 when the dump was
> initiated and to increase our maxsockets setting in BPXPRMxx.  We are set
> at the default of 64000.  Its maximum value is 16 million.  This parameter
> is in the "network" definition of a "a single sockets file system".
>
>
> What I am grappling with is what is a "single sockets file system" and how
> the heck can we be hitting 65k units of anything?  We are not that big!
> (so I think)  So who and what consumes all these entries in this single
> socket file system?  How can I monitor this?  Netstat shows active
> connections between 700 - 900 so I don't believe this is the right spot to
> be looking.
>
>
> Quick explanations would be great, recommendations on readings that will
> clarify would be awesome as well.
>
>
> TIA,
>
>
> Tracy
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
-- 

Rob Schramm
The Art of Mainframe, Inc

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to