Why does a Datacom Server connection get a "TCP/IP CONV FAILURE: Socket operation on nonsocket." error?

book

Article ID: 48568

calendar_today

Updated On:

Products

CA Datacom CA DATACOM - AD CA Ideal CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

Description:

Trying a TCP/IP connection from a Windows client, a user could receive a pop-up or an error message stating: "TCP/IP CONV FAILURE: Socket operation on nonsocket."

Solution:

This message is returned when a TCP/IP connection cannot be established with the mainframe Server region as the port specified in the ODBC Data Source or in the connection string is, for any reason, not operational.

Here is a list of the most common conditions :


  • The Server Mainframe region is not active or has abended.
  • PROTOCOL=BOTH is not coded in the Server Mainframe region start up options.
  • Wrong Host Name and/or Port Number in the ODBC Data Source or in the connection string
  • FIREWALL settings prevent a successful connection to the mainframe port where the Datacom Mainframe Server STC is listening.

Environment

Release:
Component: IDEAL