v If the MQ agent is running in its own address space, check its RKPDLOG
(time stamp not shown):
Response: &philev.RMQSGRP3 1700 83 14 5000 Active Write
Response: &philev.RMQSGRP2 1700 25 0 5000 Empty Read Access
Response: &philev.RMQSGRP1 1700 25 0 5000 Empty Read Access
Response: &philev.RKMQPDS3 23327 31 0 4000 Empty Read Access
Response: &philev.RKMQPDS2 23327 6598 143 4000 Partial Read Access
Response: &philev.RKMQPDS1 23327 3523 105 4000 Active Write
4. Verify that the files are not being used by another task.
5. Verify that the files are initialized correctly and that the KppPDICT is inserted
into the persistent data store files.
6. Verify that the maintenance procedure is correctly processing the persistent
data store files.
Example
Examples of the error codes in the RKPDLOG:
Error code 25804
Indicates that an attempt was made to read slot 0 of the GENHIST dataset.
This is a protected record and the persistent data store will not allow the
slot to be read. One possible cause is a problem with DELETE processing.
The warehouse code, which is the only code that attempts to use the delete
logic, might be generating a bad condition.
Run the RECOVERY command which will save the data and rebuild the
indexes so that the data is once again usable.
Error code 3205
The last 3 digits represent the error and the beginning digits represent the
persistent data store function that was being called. The 205 indicates the
error RowExceedsFileFormat.
This error is generated if the row you attempt to insert is larger than what
will fit in a block allocated to the persistent data store data set. The actual
maximum length is about 100 bytes smaller than the block size. Therefore,
if you allocate a block size of 1000 (Window=1) and attempt to write a row
greater then 900, you receive this message. The persistent data store cannot
span a data row across multiple blocks. One other possibility is that either
the API calls to the persistent data store to do the insert are specifying an
invalid row length or the lengths of all the columns put together for the
insert exceed the buffer length.
Error code 35404
This code has many causes. One possibility is that a PARMA parameter
intended for the agent processing is mistakenly set to the monitoring
server and interpreted as a column name. This might be due to obsolete
SQL saved in the monitoring server database. In most cases you can ignore
this error. Set monitoring server traces to (UNIT:kdssqprs input,error).
The UNIT:kdssqprs input, error trace returns large amounts of data. Turn
the trace off as soon as you finish troubleshooting.
KFAPERR : error code 14209
Persistent data store Filename is Not Available messages in the
RKLVLOG of an agent or monitoring server on z/OS: Error 8 trying to set
up table <table-name>, KRAIRA000, Starting UADVISOR_Kpp_table-name,
where pp is the two-character component or product code and table-name
is the application table name.
24 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
