We recently found that we need to disable the health check NM_PA_STACKS in specific regions because when an LPAR is capped the health check runs into a timeout and produces false positives.
Therefor I followed the instructions in https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-netmaster-network-management-for-tcp-ip/12-2/administering/health-checks.html and added "HC DELETE NM_PA_STACKS" to the respective NMREADY member.
I restarted the region and first the job output showed
126.96.36.199 BG-SYS NM90BSYS +HC DELETE NM_PA_STACKS
188.8.131.52 BG-SYS NM90BSYS NH0620 HC DELETE COMMAND COMPLETE. CHECK: NM_PA_STACKS DELETED
184.108.40.206 BG-SYS NM90BSYS N03906 EXEC NMREADY PROCESSING COMPLETE. NCLID 001395
And some seconds later it showed
220.127.116.11 - - NH3020 CHECK: NM_INITIALIZE DEFINED. CORR: 80B9100080C51FE8
18.104.22.168 - - NH3020 CHECK: NM_PA_STACKS DEFINED. CORR: 80B9100080C6CFE8
22.214.171.124 - - NH3020 CHECK: NM_SOCKETS DEFINED. CORR: 80B9100080CA6FE8
126.96.36.199 - - NH3020 CHECK: NM_SSI DEFINED. CORR: 80B9100080CA7FE8
188.8.131.52 - - NH3020 CHECK: NM_WEB_PORT DEFINED. CORR: 80B9100080CA8FE8
184.108.40.206 - - NH3020 CHECK: NM_ZIIP DEFINED. CORR: 80B9100080CA9FE8
220.127.116.11 - - NH3020 CHECK: NM_ZIIPSSI DEFINED. CORR: 80B9100080CAAFE8
18.104.22.168 - - NY6606 SSM heartbeat active
What did I do wrong? Why does the health check get enabled after it was first deleted?
I also tried the method of setting PPREF='XOPT=NOHC' in the RUNSYSIN which did work but disabled all the health checks in total.
Release : 12.2
Component : CA NetMaster Network Management for TCP/IP
I would suggest to NOT issue the HC DELETE command.
The command is only deleting the check from Netmaster.
If the goal is to DELETE the check from HC then you need to issue -
sub bsys AFTER .2 cmd=OPSYS F hCHECK,delete,CHECK=(CA_NM,[email protected])