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.
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. A list of all Assembler fixes is not possible, but Netmaster has the SHOW PTF command, which is geared toward locating specific modules.
So 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:
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.
Some modules are not loaded in storage so you may not be able to determine the level.
3. Your best bet for an overall view is to 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. Please contact support for assistance if you suspect a problem in this area.