Troubleshooting
Problem
The following messages are seen in the TEMS RKLVLOG: M2END: Unable to process all output due to insufficient output buffer - see VTPSNAP Increase LROWS value in RKANPAR member KM2IPARM. KM3DDAG Rule 'CACHE_data_table_3990' has return code = (117440520)
Cause
This message is issued when the amount of data rows returned by an underlying OMEGAMON Classic session exceeds the LROWS (Logical Rows) value specified in the RKANSAMU(KM2IPARM) member. The default value shipped with the product is 3000. There are some commands that may return more than 3000 rows of data. In that case, the LROWS value should be increased to an appropriate value for the system in question. Typically, this is related to the DASD MVS Devices table and workspace in the TEP and Enhanced 3270UI. It refers to online cached DASD devices. It is recommended that the LROWS value be set to the number of online cached devices + 100 to allow for some growth.
The LROWS issue applies ONLY to cache data which is obtained from an underlying OMEGAMON Classic session. The RMF response time data for this table is gathered from a probe that is not dependent on LROWS at all. That RMF data is merged with the Cache data from OMEGAMON Classic. If there are not enough LROWS, then some of the cache attributes will not get filled in, but the RMF values are all always filled in for all online devices regardless of the LROWS value.
If you create a situation that only looks at RMF criteria, then the code does not gather any cache data and will not have an LROWS issue. However, the DASD MVS Devices workspace must always gather all data for all devices. If you have more than 9999 online cached devices, then there is no way to stop the messages from being issued when the DASD MVS Devices workspace is selected. In that case, some rows will not contain cache values and you can ignore the messages in the RKLVLOG.
Even if you change the workspace query or create your own customized query to select a limited number of devices based on response time or busy, the code needs to gather ALL the data for ALL the devices in order to test the threshold criteria.
Below is a breakdown of the RMF and Cache attributes in the DASDMVSDEV table:
From RMF
ADDRESS
CUBUSY
DEVBUSY
DIRPBUSY
HYPERPAV
IOCONN
IODISCON
IOPEND
IORATE
IOSQUEUE
LCUNUM
OPENALLOC
PAVCOUNT
PCTBUSY
PCTRESERVE
RESPTIME
STRGROUP
VOLSER
From OMEGAMON Cache service
MODEL
CACHSTAT
READHIT
WRITEHIT
FASTHIT
Was this topic helpful?
Document Information
More support for:
Tivoli OMEGAMON XE on z/OS
Software version:
5.1.0, 5.1.1, 5.3.0, 4.2.0
Operating system(s):
z/OS
Document number:
294719
Modified date:
23 December 2019
UID
swg22000636