How to determine the maintenance level for Netmaster?

Products

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

Issue/Introduction

Determining the maintenance level for the SOLVE/Netmaster products has changed over time.
The /LEVELS and $$SYSPRO commands were useful for Service Packs, but we are no longer using that methodology.
While no single command is currently available that supplies a comprehensive answer, it is possible to verify that specific fixes are applied.

Environment

All SOLVE and Netmaster products

Resolution

1. To determine all the fixes that are applied to libraries in the COMMANDS DD (all  *EXEC and custom libraries in use), you can issue $$SYSPRO APAR. 
     This lists every NCL and OML proc beginning with ‘$’ along with the latest applied maintenance.
       Below is a small excerpt.  Note that the TESTEXEC entry is highlighted.  
       Please note also that the previous entry in AUDE0.LIB.NCL is not highlighted.  This means that if you have an additional library
       in your COMMANDS DD that contains custom code, or if you use a dataset for custom code that does not have a llq of TESTEXEC,
       the modules contained within that library that start with '$' and that may be overriding distributed code will not be highlighted.    

 

2.   Netmaster has the  SHOW PTF command, which  is geared toward determining the level of specific modules.
      If you have an assembler fix applied and want to verify it is included in your runtime, you include the last 3 characters from the module
      in the SHOW PTF command to verify the fix level.  

     Example: You just applied fix RO80298 that updates module NM00000M.

     From the Command Entry Screen (enter CMD from any user prompt to get there) issue command SH PTF=00M and you will get this back:

     SH PTF=00M
     N14510 PTF LEVEL FOR MODULE NM00000M IS RO80298 VER: 0706 ADT: 2015/04/14-01.24

     For a fix that is part of the SOLVESSI, the command would be
     SSIS SH PTF=xxx.

     The downside when you want to determine a more complete level of maintenance is that this is a per module process, and the module must be loaded in storage or no value will be found.

Another option to provide a more comprehensive list of what is in your SOLVE / Netmaster LOAD library is to use the CA Common Services command CAMODID.
The simplest method is to issue this from the TSO command prompt.

From TSO, issue  CAMODID HELP to see what's all available.
There are various options; DSN, DDN, or SYSTEM.

Please review the manual for additional information regarding all the ways in which you can invoke the command - TSO, batchjob, REXX, etc.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-mainframe-software/traditional-management/ca-common-services-for-z-os/14-1/administrating/resource-initialization-manager/how-to-use-camodid.html

EXAMPLE:

If you are using a STEPLIB in your active SOLVE / Netmaster STC, you can use this command
 CAMODID DDN(STEPLIB) JOB(slv-netmasterstcname)

To check a specific LOAD library, use
CAMODID DSN(hlq.loadlib)

Other options are available to suit your specific needs.

This will show a list of PTFs and FMIDs, so only the PTFs  displayed are those that were that last applied to modules in the library.

 

3.  To see all PTFs in the CSI, run an SMP/E query report and verify that the last few PTFs are included in your region.

 

4.  Verifying fixes that are included in your VSAM files is more difficult.  If the PTF was applied and the  ++HOLD instructions followed to copy
      the information into the VSAM file, verification is normally not necessary.  
   Netmaster 12.2 will show messages in the log indicating he latest PTFs applied ot MODSDIS and PANLDIS. SOLVE products do not have that functionality.
   Please contact support for assistance if you suspect a problem in this area.