TBFNV General checklist for NetView for z/OS TEMA problems
Why doesn't my TEMA (Tivoli NetView for z/OS Enterprise Management Agent) receive data from NetView for z/OS V6 ?
Verify status and connections with operator commands and messages
The IBM Knowledge Center, NetView for z/OS 6.2 Troubleshooting Guide, section 'Diagnosing Tivoli NetView for z/OS Enterprise Management Agent problems' is an excellent reference for helping diagnose and resolve TEMA problems.
CANSNA is the default started task procedure name for the NetView agent.
Things to check in the NetView for z/OS address space:
- Verify that NetView for z/OS is connected to the agent.
NetView for z/OS command 'NACTL LISTCONN' should display information like the example output below if NetView for z/OS is connected:
NTVE4 NACTL LISTCONN
BNH888I DISPLAY OF NETVIEW ENTERPRISE MANAGEMENT AGENT CONNECTIONS
BNH889I TASK STATUS SOURCE DEST PPI LCL PPI
BNH890I NAME NAME RECEIVER RECEIVER
BNH834I -------- ------------ -------- --------- ---------
BNH834I AUTONALC CONNECTED NTVE4 CNMEMARX NTVE4
Note the CONNECTED status. (Dest PPI receiver value will match the BNH857I value for receiver should the NVEMACMD be used). In addition, the syslog should have a BNH880I message from the agent indicating that the NetView node is connected:
09.29.17 STC04692 BNH880I NETVIEW ENTERPRISE MANAGEMENT AGENT NTVE4 SUBNODE IS ACTIVE
If command: NACTL LISTCONN returns error message:
CNM249E LISTCONN : NO DATA FOUND FOR 'NETVIEW ENTERPRISE MANAGEMENT AGENT CONNECTIONS', the reason may be that NACMD command was not issued from NetView or did not work. The NACMD command establishes the connection between NetView and the agent.
To help diagnose message CNM249E, issue command: /?NALCLOP: NACMD
and check the log for any error messages. If the command works, NetView should be connected to the agent. NetView generally issues the NACMD command under the covers out of automation but it may have not been issued for some reason.
- Verify that the data collectors are running with command: NACLT LISTINFO.
Things to check in the agent address space
- Verify that the agent job is active
z/OS command D J,<agentjob> will show if agent is running.
- Verify that the agent initialized successfully:
Look for BNH messages issued by agent at initialization
BNH877I NETVIEW ENTERPRISE MANAGEMENT AGENT INTERFACE IS READY FOR WORK
BNH856I NETVIEW ENTERPRISE MANAGEMENT AGENT INITIALIZED SUCCESSFULLY
- Verify that the PPI is active: Issue NetView command: DISPPI
- Verify that the agent is connected to the PPI and check the PPI sender/receiver names.
z/OS command: MODIFY (f) <agentjob>,NVEMACMD can be used for this.
17.12.21 NMP219 f cansna,nvemacmd status
17.12.21 NMP219 STC04692 BNH858I NETVIEW ENTERPRISE MANAGEMENT AGENT PROGRAM TO PROGRAM INTERFACE IS ACTIVE
17.19.50 NMP219 f cansna,NVEMACMD PPIINFO
17.19.50 NMP219 STC04692 BNH857I PROGRAM TO PROGRAM INTERFACE SENDER CNMEMATX 17.19.50 NMP219 STC04692 BNH857I PROGRAM TO PROGRAM INTERFACE RECEIVER CNMEMARX
- Verify that the agent is connected to the TEMS.
In the RKLVLOG for the agent, look for these entries (substitute the customer’s values for CMS and transport):
15:28:47.92 (00AC-D372343:kraaulog.cpp,755,"IRA_OutputLogMsg") Connecting to CMS PARMGRTE:CMS
15:28:47.92 (00AD-ED372343:kraaulog.cpp,543,"ctira_insert_log") KRAREGG000, Connecting to CMS PARMGRTE:CMS, Producer(IRA_Manager
15:28:47.92 (00AE-ED372343:kraarreg.cpp,1125,"ConnectToProxy") Successfully connected to CMS PARMGRTE:CMS using ip.pipe:#9
Most Agent configuration is contained in the KNAENV member of the RKANPARU data set in the run-time environment. Most of the configuration on the NetView side is done in CNMSTYLE. A key point to check is that the KNA_PPIRCV statement in KNAENV should match the value for (TEMA)NACMD.DESTPPI in CNMSTYLE.
The agent log is defined by the RKLVLOG DD statement in the agent startup job. By default, the log is assigned to SYSOUT class X. The log can be moved to a dataset by using the SDSF PRINT facility.