stack terminated connection; RC=reason_code interpreted
stack Stack name
reason_code NMI connection terminated reason code
interpreted Interpreted NMI connection terminated reason code:
STKTRM Normal termination
EACCES Permission is denied
EINVAL The parameter is incorrect
ENOMEM Not enough space is available
EPIPE The pipe is broken
EBLOCK The descriptor is marked nonblocking, and the requested function cannot complete immediately
EUNKN Unknown reason
This message indicates that the VIP agent has failed to connect with IBM’s Network Management API (NM API). A VIP agent terminates if the NM API’s SYSTCPSM interface is not enabled. The agent will continue running if the NM API’s SYSTCPCN NMI is not enabled; however, the agent will not be able to provide information for TCP connections on the stack.
The return code in the message indicates the problem more precisely.
Example 1:
0x0000006F = EACCES = permission denied
probably means the site does not authorize – via RACF, ACF2, Top Secret, etc. – the VIP agent’s user ID to access the portion of the NM API named in the message. The agent’s user ID must have authority to access the NM API resources in the SERVAUTH class. If SERVAUTH is not enabled, the agent’s user ID must have super-user privileges.
Example 2:
0x00000081 = ENOENT = No such file, directory, or IPC member exists
probably means the system has not enabled the portion of the NM API named in the message.
To verify that the SMFSRV and TCPCNNSRV NMIs are enabled, issue the command D TCPIP,,NETSTAT,CONFIG.
It will return results like the following:
NETWORK MONITOR CONFIGURATION INFORMATION:
PKTTRCSRV: YES TCPCNNSRV: YES MINLIFTIM: 3 NTASRV: YES
SMFSRV: YES
For help enabling the NM API, see the VIP Environment Checklist, available on the Downloads page of the SDS website. For more information, see IBM manuals z/OS Unix System Services Messages and Codes and z/OS Communications Server IP Programmer’s Guide and Reference.