Seeing SD4302E and SD4303I messages in Netmaster log

Products

• CA NetMaster Network Automation
• CA NetMaster Network Management for SNA
• CA NetMaster Network Management for TCP/IP
• CA NetMaster File Transfer Management

Issue/Introduction

Netmaster region shows  a few or many of these messages on startup

 SD4301I Checking MODS entities from [email protected]$W3 are at NMTI5392 level for PTF SO0
 SD4302E Missing maintenance SO09324 detected for element [email protected]$$$             
 SD4303I [email protected]$$$ last update NMTI5383, expected NMS2293                       
 SD4302E Missing maintenance SO06597 detected for element [email protected]$AM             
 SD4303I [email protected]$AM last update INSTALL, expected NMS2250                        
 SD4306E Missing maintenance SO06597 detected for element [email protected]$AM in PANLDIS  
 SD4307I [email protected]$AM last update INSTALL , expected NMS2250                       
 SD4302E Missing maintenance SO09623 detected for element [email protected]$FA             
 SD4303I [email protected]$FA last update INSTALL, expected NMTI5445                       

Cause

mismatch between SMP/E applied maintenance and runtime VSAM files in region

Environment

Release : 12.2

Component : CA NetMaster Suite

Resolution

There are two options.

1) For PTFs that update content used in the VSAM files (generally MODSDIS and PANLDIS), the ++HOLDDATA provides JCL to run the NMVIP program that ports the changes over from SMP managed libraries to the VSAM datasets.  

2) A new to 12.2 VSAMUPDATE parameter group allows the Netmaster region to update the VSAM files automatically when it initializes after applying maintenance.

The process for doing so is described in the Installing and Upgrading Guide 
https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-netmaster-shared-content-library/12-2/install-or-upgrade-ca-netmaster-products/post-installation-tasks/apply-maintenance-for-vsam-and-ramdb.html

Similarly, to verify whether there is a discrepancy between VSAM and the runtime libraries, $$SYSPRO was enhanced to track this as well.

Our doc  states that $$SYSPRO has been updated to provide VSAM maintenance checking.
$$SYSPRO VSAM verifies that VSAM files have been updated by the NMVIP job as recommended in the PTF HOLDDATA.

This enhancement is supplied via PTF SO04199 (included at level 1904 and above).

Additional Information

$$SYSPRO update is described here in the PRE-GA section of the Netmaster for TCP/IP 12.2 Release notes 
https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-netmaster-network-management-for-tcp-ip/12-2/release-notes/Updates-Pre-GA.html