On 22/04/2011 12:59 PM, Chris Mason wrote:
John
The *issue* here is that IBM - and possibly other vendors - when dealing with
socket calls - that's socket calls in general not just the actual socket() call
-
just seem not to be comprehensive in documenting all possible return codes
(errnos)
On Thu, 21 Apr 2011 13:49:14 -0700, John Weber j...@fiteq.com wrote:
Hi,
We are calling from z/OS CICS COBOL to a C program which is opening a
socket to start a TCPIP connection and we got back error 167 from the socket
() function call.
Do you have
TCPIP.SEZATCP
in both your //DFHRPL and
Hi,
We are calling from z/OS CICS COBOL to a C program which is opening a socket to
start a TCPIP connection and we got back error 167 from the socket() function
call.
However, if we call from Batch to the same C program as above, the socket opens
correctly.
Three questions:
1. What does
John
The *issue* here is that IBM - and possibly other vendors - when dealing with
socket calls - that's socket calls in general not just the actual socket() call
-
just seem not to be comprehensive in documenting all possible return codes
(errnos) for each call. For some reason which must
4 matches
Mail list logo
