Can I run the Socket Listener with AOR and TOR in different LPARs?
search cancel

Can I run the Socket Listener with AOR and TOR in different LPARs?

book

Article ID: 11345

calendar_today

Updated On:

Products

Gen Gen - Workstation Toolset Gen - Host Encyclopedia Gen - Run Time Distributed

Issue/Introduction

Setting up a CICS region for the Socket Server Listener to run.



Can the Socket Server Listener provided by CA's Direct Connect for CICS to run where the AOR (Application Owning Region) and TOR (Terminal Owning Region) are on different LPAR's?

Environment

z/OS CICS

Resolution

It is not possible to run the CA Gen Socket Listener in a environment where AOR and TOR regions are on different z/OS Images (LPAR's). 

Example: AOR in LPAR A and TOR LPAR B

The Following error Message will occur:

 * 
 TISRVLIS TASK=00000035 02/27/2009 08:48:05 GIVESOCKET NOT TAKEN FOR SERVER  
 from AOR error message:                                                     
 Z145     TASK=00002430 02/27/2009 08:47:55 TIRSIPIN SOCKET ERROR TAKESOCKET 
 RETCODE=-0000001 ERRNO=     113                                             
 * 

 

 

Additional Information

This is an IBM CICS Socket interface limitation:

*
CICS sockets requires that the AOR must be on the same z/OS image as the TOR (givesocket/takesocket limited to same z/OS).

Requirement: The EZAO transaction must be running on the CICS where you want to start the CICS sockets interface. You cannot start a CICS socket interface from a different CICS.

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.halc001/stsezao.htm