Home > IT Answers > DataCenter > Error 1027 on CICS Sockets Connect
Help

Question

  Asked: Sep 17 2006   11:36 AM GMT
  Asked by: RogerRabbit

Error 1027 on CICS Sockets Connect


Zseries, Networking

I receive return code 1027 from connect API.
My client application can connect lot of times, but some times I receive the 1027. The conccurent server is an UNIX system that remains working and accepting new connections.
How can I do the connect work? I try the connect again, in the same task, but the result was the same 1027 on return code.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window
Help

Answer Wiki (Improve, edit or add to this answer)

IMPROVE THIS ANSWER
View History
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
Last Answered: Sep 18 2006  8:54 AM GMT  by oxtsd04




RogerRabbit. One thought that comes to mind is that you may not have specified a valid socket number on the CONNECT call via the S parm. Prior to doing the CONNECT call you must issue a SOCKET call to get a socket number assigned to your task. The socket number assigned by the SOCKET call must then be specified via the S parm on the CONNECT call. Are you doing this?
  • AddThis Social Bookmark Button

Browse more Questions and Answers on DataCenter and Networking.

Looking for relevant DataCenter Whitepapers? Visit the SearchDataCenter.com Research Library.


RSS - Discussions Help

Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

oxtsd04  |   Sep 18 2006  9:33AM GMT

RogerRabbit, After some further research I have some more questions for you.

1. On your INITAPI call what do you specify for MAXSOC or do you take the default or minimum value of 50?
2. Is your client transaction a long running client that establishes multiple connections and issues multiple SOCKET calls? If so does it issue a CLOSE call when it is done with a SOCKET? If not you might be hitting your limit of open SOCKETS as specified via MAXSOC on the INITAPI call.
3. What programming language are you using?
4. Are you using the original CICS Sockets interface where you issue CALLS to EZACICAL, or are you using the new sockets extended API where you issue CALLS to EZASOKET? It is highly recommended that you use EZASOKET.
5. What release of CICS are you running?
6. What release of MVS or z/OS are you running?

 

RogerRabbit  |   Sep 18 2006  12:17PM GMT

1. I specify for MAXSOC=1
2. My client transaction establishes one connections by task and issues only one SOCKET calls, write and read the socket and close the socket. We are running more than one task ate the same time, connecting on the same server and port.
3. I’m using COBOL and issue CALLS to EZASOKET.
5. What release of CICS are you running?
I’m asking for my client
6. What release of MVS or z/OS are you running?
I’m asking for my client

 

RogerRabbit  |   Sep 18 2006  12:39PM GMT

My program issue a call to SOCKET:
CALL ‘EZASOKET’ USING SOKET-SOCKET AF-INET SOCTYPE
PROTO ERRNO RETCODE.

The RETCODE return = 0, so I move IPADDR, PORT and issue a call to CONNECT:

CALL ‘EZASOKET’ USING SOKET-CONNECT SOCKID NAME
ERRNO RETCODE.

I did not move nothing to SOCKID, Is that correct?
In the server program TAKESOCKET give me a SOCKID in the return code.
In the client program I need move some value to SOCKID??

 

RogerRabbit  |   Sep 18 2006  12:52PM GMT

My program issue a call to SOCKET:
CALL ‘EZASOKET’ USING SOKET-SOCKET AF-INET SOCTYPE
PROTO ERRNO RETCODE.

The RETCODE return = 0, so I move IPADDR, PORT and issue a call to CONNECT:

CALL ‘EZASOKET’ USING SOKET-CONNECT SOCKID NAME
ERRNO RETCODE.

few times I receive RETCODE=1027, allmost always calls return 0.
I did not move nothing to SOCKID, Is that correct?
In the server program TAKESOCKET give me a SOCKID in the return code.
In the client program I need move some value to SOCKID??

 

RogerRabbit  |   Sep 18 2006  1:33PM GMT

CICS Version TS 2.3
Z/OS Verison 1.4

I’ve been using CICS sockets since 2003.
And I think that is the best feature in the CICS environment.

Thank you…