IBM E027SLL-H - Tivoli Monitoring - PC Troubleshooting Manual page 45

Active RAS1 Classes: EVERYT EVERYE EVERYU
(4558D8CC.0035-1114:kpxreqds.cpp,661,"determineTargetsFromNodelist") Entry
(4558D8CC.0036-1114:kpxreqds.cpp,669,"determineTargetsFromNodelist") Exit
(4558D8CC.0037-1114:kpxreqds.cpp,821,"determineTargetsFromAccessList")
Active RAS1 Classes: EVERYT EVERYE EVERYU
(4558D8CC.0038-1114:kpxreqds.cpp,821,"determineTargetsFromAccessList") Entry
(4558D8CC.0039-1114:kpxreqds.cpp,837,"determineTargetsFromAccessList")
Calling KFA_GetAccessListNodes for NT_Paging_File_Critical, 5140
(4558D8cc.003A-1114:kpxreqds.cpp,852,"determineTargetsFromAccessList")Node #0
Primary:KATE:NT
(4558D8CC.003B-1114:kpxreqds.cpp,891,"determineTargetsFromAccessList")
Deleting NodeRecEntry: #0, node_entries @0x1B63B90, next @0xNULL,
ptr_next @0xNULL
(4558D8CC.003C-1114:kpxreqds.cpp,898,"determineTargetsFromAccessList") Exit
4. Did the agent return data?
v On the monitoring server set this trace level (UNIT:kpxrpcrq ERROR STATE)
to show the number of rows returned by each agent.
(3A933B00.24A827C0-154:kpxrpcrq.cpp,547,"IRA_NCS_Sample")
Rcvd 1 rows sz 448 tbl *.NTLOGINFO req NT_Log_Space_Low <4294706777,761>
node <Primary:NODE1:NT
v If Yes: See step 6.
v If No: Is the situation authored correctly? At the agent, trace (UNIT:kdsfilt
all).
a. Yes: The problem might be related to the monitoring agent. See the
Troubleshooting appendix of the distributed agent's User's Guide or the
Troubleshooting Guide of the z/OS monitoring agent.
b. No: See step 5.
5. Look in the log of the monitoring server to which the agent is attached. Search
for the situation name and look for any errors logged.
v Catalog errors (message return codes 202 and 209). Ensure the application
support is installed at the monitoring server.
v Message KO41046 is missing – situation failed to lodge message:
KO41039 Error in request MCS_Sit. Status= 1133. Reason= 1133.
KO41039 Error in request MCS_Sit. Status= 1131. Reason= 1131.
(4558E8EF.0079-11A4:ko4sitma.cpp,782,"IBInterface::lodge") error:
Lodge <1131>
(4558E8EF.007A-11A4:ko4ibstr.cpp,659,"IBStream::op_ls_req") IB Err: 1131
(4558E8EF.007B-11A4:ko4sit.cpp,658,"Situation::slice") Sit MCS_Sit: Unable
to lodge - giving up.
KO48156 Not able to start monitoring for situation MCS_Sit.
v SITMON/IB Lodge errors
a. Attribute file is incorrect (wrong version) or missing and the RULE could
not be created.
b. A value of 1133 or 1203 leads to a value of 1131.
c. A value of 1145 generally means that the referenced situation either has
been deleted or has not been distributed correctly.
#define ERR_LODGEERROR
#define ERR_NOATTRIBUTE
#define ERR_DUPLICATEINSERT
#define ERR_INVALIDSITNAME
#define ERR_RULESYNTAX
6. Did SITMON receive the data?
v Monitoring server trace (UNIT:ko4async ERROR STATE FLOW)
(UNIT:ko4tobje ALL) (UNIT:ko4sitma ALL)
v If Yes and SITMON receives the data: Does the situation apply to the
Enterprise? For example:
1131 // Bad lodge request
1133 // No attribute found
1144 // Duplicate record exists
1145 // Invalid sitname supplied
1203 // Generic rule syntax error
Chapter 3. Common problem solving
27