Tracking NCL usage in Netmaster / SOLVE


Article ID: 197538


Updated On:


SOLVE:Operations Automation SOLVE:FTS NetMaster Network Management for TCP/IP NetMaster File Transfer Management NetMaster Network Automation NetMaster Network Management for SNA


Looking for the most comprehensive method possible to track all NCL / OML / REXX activity that run on a given region - which ones are used, last hit date if possible.


Release : 11.9
Component : CA SOLVE:Operations Automation for z/OS

Release : 12.2
Component : Netmaster Suite


Please read through the instructions to determine if this will be helpful for your environment

 NCL proc HBOSPRMN was written that requires that a PTF be applied:
     SO14616 (for SOLVE:Operations) or SO14546 (for Netmaster).
    The PTF ensures that any time a PROC - NCL/OML/REXX, is loaded and an event is created, the proc will catch that. 
    Since it is impossible to execute a proc without first loading it, this will capture absolutely everything that the region executes.

Please open a case with CA Netmaster support and include the number of this Knowledge doc  if you would like to use this,  as the HBOSPRMN proc is not part of the distributed code. 

NOTE: This does not supply a last hit date, nor does it show how many times a proc has run, but it ensures all procs are found and reported.

To implement:
1. Ensure you have the fix applied and have received the HBOSPRMN proc.

2. Add the new NCL proc to your TESTEXEC

3. Add this to NMREADY to start the monitor 

4. When the system is running, issue
    HBOSPRMN DUMPVAR=YES to see all procs that have been loaded


System + CSNM38        Limit 1000
hbosprmn dumpvar=yes              
NCL,OML,REXX = $ADLIBDF, count=1          
NCL,OML,REXX = $AMALRCV, count=1          
NCL,OML,REXX = $AMALRXZ, count=1          
NCL,OML,REXX = $AMCALL, count=2            
NCL,OML,REXX = $AMDBMS, count=1 

This is cumulative from initialization of the region until it is stopped.
So it is best to issue the last DUMPVAR command shortly before stopping the region to get the complete list of procs.


The proc can be started in test without cycling - simply submit it from CMD using the same command as above -