BAAPI0003 SOCKET Register FAILED ACTIONING /PARMS GROUP NMAPI
search cancel

BAAPI0003 SOCKET Register FAILED ACTIONING /PARMS GROUP NMAPI

book

Article ID: 256428

calendar_today

Updated On:

Products

NetMaster Network Management for TCP/IP

Issue/Introduction

API interface in NetMaster was turned on and it resulted in a socket error for /var/sock/ : BAAPI0003 SOCKET Register FAILED,
 
RC=8 FDBK=24 RSN=36 VERRIN= .  This is related to /PARMS group $NM NMAPI--parm NMAPI.   
 

F5=ILog:

Time     Log Data                                                                       
18.45.41 IAIN0126 Processing for parameter group $NM NMAPI started                      
18.45.41 IAIN0124 Global variable GLBL$NMAPION set to "YES"                             
18.45.41 IAIN0124 Global variable GLBL$NMAPIPN set to "/var/sock"                       
18.45.41 IAIN0178 Processing for parameter group $NM NMAPI ended, status is COMPLETED   
18.45.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.46.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.47.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.48.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.49.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.50.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.51.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.52.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  
18.53.52 BAAPI0003 SOCKET Register FAILED, RC=8 FDBK=24 RSN=36 VERRIN=                  

Environment

OS:  z/OS

Release : 12.2

Resolution

The IBM (HPNS) sockets interface was being used--and that was the problem.  The following steps were then performed:

=/parm 

U               $NM SOCKETS     TCP/IP Sockets Interface  

Ensure interface type = USS, like:

TCP/IP Interface Type ........ USS     

Ensure everything else is correct as well, PF08 to verify.

PF06 to  ACTION

From Command Entry do the following--it should now look similar to this:

sh tcpip                                                        
N3AF05 TCP/IP INTERFACE IS ACTIVE NAME=USS PRIMARY=YES IPVERS=6
N3AF06 TCP/IP PARMS PFSNAME=TCPIP    

-

Now update that NMAPI parm with /var/sock and PF06 to ACTION.

-

 
The API became active on the var/sock path.
 
22.15.45 IAIN0124 Global variable GLBL$NMAPIPN set to "/var/sock"                     
 
22.15.45 BAAPI0006 API SERVER ACTIVE ON PATH /var/sock/NMAPI.<region>                  
 
22.15.45 IAIN0178 Processing for parameter group $NM NMAPI ended, status is COMPLETED 

-