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

Products

• Datacom
• DATACOM - AD
• Ideal
• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• 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