Additional verifications regarding SNA Network Management Interface (SNANMI) security requirement errors NSN581 and NSN585, which can appear during NetMaster Subsystem Interface STC startup.

Products

• CA CMDB for z/OS
• CA NetSpy Network Performance
• CA NetMaster Network Automation
• CA SOLVE
• CA NetMaster Network Management for SNA
• CA NetMaster Network Management for TCP/IP
• CA NetMaster File Transfer Management
• CA SOLVE:Operations Automation
• SOLVE:Access Session Management
• CA SOLVE:CA Mainframe Connector
• CA SOLVE:FTS
• CA SOLVE

Issue/Introduction

Description:

During NetMaster Subsystem Interface STC startup, SNANMI-related security requirement errors NSN581 and NSN585 may still appear, despite the basic verifications found on manual NetMaster for TCP/IP Installation Guide r12 (pp. 196 and 197).

Solution:

Here's a couple of things that can be verified, to try to isolate the problem:

1. VTAM will attempt to access the /var directory when opening the socket--typically this is where the problem is. Look in the VTAM (typically STC = NET) JESLOG, and you will see messages either showing success or failure to open the server management socket.
   
   It follows a successful msg:

   IST1925I SOCKET OPENED BY SNAMGMT SERVER SUBTASK

   It follows an example when VTAM JESLOG shows an authorization problem:

   ACF04056 ACCESS TO RESOURCE IST.NETMGMT.XXXX.SNAMGMT TYPE RSER BYNMTCPSSI NOT AUTHORIZED

2. The following command will look out for NET and will show if VTAM has opened the socket required for this API:

   syscmd D OMVS,SOCKETS NET    00000001          LISTEN 00000E9B 00000000SOCKET NAME: /var/sock/SNAMGMTNET    00001E64 00001E63 ACP    00088412 00224786SOCKET NAME: /var/sock/SNAMGMT

Environment

Release:
Component: NMTIP