MSMC0616E The SCS address space was unable to open an INET/INET6 socket...

book

Article ID: 49832

calendar_today

Updated On:

Products

CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA Mainframe Software Manager (Chorus Software Manager) CA MICS Resource Management 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 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 CA Datacom/AD

Issue/Introduction

Description:

This Knowledge Document discusses the IPv4/IPv6 related definitions in member MSMCPARM.

The default setting in MSMCPARM is for IPv6

   <TCPIP ipaddr="::" port/>  

In case your system is not configured with an AF_INET6 domain in BPXPRMxx member, this setting will result in following message during start of MSMCPROC:

MSMC0616E The SCS address space was unable to open an INET/INET6

socket with an errno of 1114 with a message of EDC8114I Address

family not supported.

Solution:

If the environment does not support IPv6, then you must change in MSMCPARM the TCPIP ipaddr to
"0.0.0.0" since the default "::" is unspecified address for IPv6.

Change in MSMCPARM       
<TCPIP ipaddr="::" port/> 
to 
 
<TCPIP ipaddr="0.0.0.0" port/>

The IPv4 unspecified address (i.e., "0.0.0.0") may be specified to indicate that the SCS address space should accept TCP connection requests through all IPv4 interfaces.

The IPv6 unspecified address (i.e., "::") may be specified to indicate that the SCS address space should accept TCP connection requests through all interfaces, both IPv4 and IPv6.

As an alternative you can do as follows:

If you add to your BPXPRMxx member, the appropriate Address Family for IPV6 support to your existing IP Address Family support, you can use "::" and be prepared to use IPV6 in the future. Below highlighted in yellow is a snippet of adding the Address Family for IPV6 to INET. You should refer to IBM manuals for complete choices and syntax.

Snippet:

NETWORK DOMAINNAME(AF_INET)
        DOMAINNUMBER(2)     
        MAXSOCKETS(30000)   
        TYPE(INET)          
        INADDRANYPORT(5555) 
        INADDRANYCOUNT(1000)
                            
NETWORK DOMAINNAME(AF_UNIX) 
        DOMAINNUMBER(1)     
        MAXSOCKETS(2000)    
        TYPE(UDS)           
                            
NETWORK DOMAINNAME(AF_INET6)
        DOMAINNUMBER(19)    
        MAXSOCKETS(30000)   
        TYPE(INET)          

IBM Manuals for syntax and detail information on IP configuration:

  • MVS Initialization and Tuning Reference ... for BPXPRM member syntax
  • z/OS Communication Server IP Configuration Guide
  • z/OS Communication Server IP Configuration Reference

Environment

Release:
Component: MSM