NPM/390 NPM R270 may use a few CPU cycles even when not collecting data.
Even after stopping all collection from the FNMSTRT member, NPM will continue to use a minor amount of CPU cycles.
To baseline NPM, do the following. The items are listed in decreasing importance to overall CPU usage. You may reach a point where CPU usage is only a few seconds a day and further actions are not needed. It is not possible to completely remove all CPU cycles since NPM is a started task and there will always be some activity in associated with NPM timer pops.
1. Remove all FNMSTRT entries and calls to executable files.
2. Set HOSTCOLL=NO on the FNMINIT members NPM statement.
3. Set PORTNUM=0. Even if it is commented out it will default to 1965 and cause NPM to open a TCPIP port. Note: PTF UA00498 must be applied. The PORTNUM parm is also in FNMINIT on the NPM statement.
(Note. At this point the NPM Java Console users will not be able to connect to NPM. The TELNET and SNMPCOLL parms will also be forced to 'NO'.
4. Remove any NCP statements from FNMINIT. (It is now a command and should be driven from FNMSTRT but NPM will nevertheless convert it to a command. NCP's will continue to attempt to bind NPM whether or not the NCP statements are present. Lacking the NCP command, NPM will not bind the NCP however.
5. Remove the VTAM and SMF exits from being executed. See appendix E of the NPM Reference for details. (SH19-6965-06).
6. Remove the VSAM exit FNMBLVRP.
7. Change EVENT=NONE, LIST=NO and CONFIG=NO. Each will take a few cycles in testing the environment on each timer pop.