Monitoring agent is running out of storage

If response time is slow on the monitoring agent, check the RKLVLOG for messages about a possible storage problem. A storage usage event is generated every hour and is written to the RKLVLOG.

Typically the STORAGE command is used in conjunction with the EVERY command to schedule period issuance of the STORAGE command. The KN3AGST member of RKANCMD has the following line by default. 
EVERY 00:60:00 STORAGE D     * LOG STORAGE USE
Where:
EVERY
Is a command that is used to schedule another command for periodic execution.
00:60:00
Shows the hours, minutes, and seconds. A value of 00:60:00 indicates that the command is to be run every 60 minutes.
STORAGE
Displays statistics of ITMS:Engine storage usage.
D
Stands for Detail. STORAGE provides both primary and extended storage statistics. This information is helpful in tuning ITMS:Engine memory management.
The default entry causes the STORAGE D command to be issued every 60 minutes. The interval at which the command is automatically issued is defined during the Tivoli Enterprise Portal configuration with the Enable storage detail logging parameter on the Specify Advanced Configuration Options panel, where the values are Y or N. Two other settings are associated with the Enable storage detail logging parameter:
  • Set the Storage detail logging interval to monitor storage. The interval values are written as part of the second EVERY command in &rhilev.&midlev.RKANCMDU(KDSSTART). The default is 60 minutes.
  • Set the Flush VSAM buffers interval to force all deferred VSAM writes to DASD. The interval values are written as part of the third EVERY command in &rhilev.&midlev.&rtename.RKANCMDU(KDSSTART). The default is 30 minutes.

    This modify command is useful if the monitoring server is already running with storage detail logging initially disabled. Issuing the modify command activates storage detail logging without having to recycle the monitoring server. The default is Y.

  • To disable storage detail logging, set this parameter to N, which then generates the second EVERY command as a comment.
To control storage detail logging dynamically, issue the following modify command for the z/OS® console to either the monitoring server or the monitoring agent started task to enable storage detail logging: 
MODIFY procname,STORAGE D
Where:
MODIFY
Is the z/OS command.
procname
Is the name of the monitoring server or monitoring agent started task. The default name of monitoring server started task is CANSHUB. The default name of the monitoring agent started task is CANSN3.
STORAGE
Displays statistics of ITMS:Engine storage usage.
D
Stands for Detail. STORAGE provides both primary and extended storage statistics. This information is helpful in tuning ITMS:Engine memory management.
After you issue this command, look in the RKLVLOG for the output. The typical output of this command and an explanation are found below. 
01 KLVSD001 PRIMARY MAIN STORAGE INFORMATION:
02 KLVSD003 ALLOCATION DETAIL:
03 KLVSD004 SIZE(1-16) USE(1629) TOTAL(1652) ACCESSED(2122)
04 KLVSD004 SIZE(17-32) USE(1222) TOTAL(1256) ACCESSED(1804)
05 KLVSD004 SIZE(33-48) USE(43) TOTAL(51) ACCESSED(989)
06 KLVSD004 SIZE(49-64) USE(30) TOTAL(321) ACCESSED(789)
07 KLVSD004 SIZE(65-80) USE(190) TOTAL(299) ACCESSED(474)
08 KLVSD004 SIZE(81-96) USE(277) TOTAL(432) ACCESSED(492)
09 KLVSD004 SIZE(97-112) USE(27) TOTAL(43) ACCESSED(412)
10 KLVSD004 SIZE(113-128) USE(39) TOTAL(43) ACCESSED(311)
11 KLVSD004 SIZE(129-160) USE(79) TOTAL(374) ACCESSED(222)
12 KLVSD004 SIZE(161-192) USE(84) TOTAL(111) ACCESSED(205)
13 KLVSD004 SIZE(193-224) USE(96) TOTAL(127) ACCESSED(177)
14 KLVSD004 SIZE(225-256) USE(148) TOTAL(259) ACCESSED(192)
15 KLVSD004 SIZE(257-320) USE(342) TOTAL(365) ACCESSED(144)
16 KLVSD004 SIZE(321-384) USE(40) TOTAL(54) ACCESSED(98)
17 KLVSD004 SIZE(385-512) USE(5) TOTAL(35) ACCESSED(80)
18 KLVSD004 SIZE(513-768) USE(21) TOTAL(26) ACCESSED(92)
19 KLVSD004 SIZE(769-1024) USE(14) TOTAL(17) ACCESSED(12)
20 KLVSD004 SIZE(1025-2048) USE(28) TOTAL(35) ACCESSED(8)
21 KLVSD004 SIZE(2049-4096) USE(81) TOTAL(97) ACCESSED(2)
22 KLVSD004 SIZE(4097-8192) USE(8) TOTAL(9) ACCESSED(1)
23 KLVSD004 SIZE(8193-16384) USE(1) TOTAL(1) ACCESSED(1)
24 KLVSD005 LIMIT(65536) SLOPE(9) SIZES(23) TOTAL(2916K) FREE(2055K)
25 OVERHEAD(44936)
27 KLVSD031 BUFFER POOL INFORMATION
28 KLVSD032 POOL BUFSIZE(3564) SEGSIZE(65536) MASK(3FFFF) SIDEQ(0)
29 KLVSD033 BUFFERS INUSE(0) MAX(0) GETS(0) FREES(0)
30 KLVSD033 SEGMENTS INUSE(0) MAX(0) GETS(0) FREES(0) Q(0) QMAX(0)
31 KLVSD032 POOL BUFSIZE(3440) SEGSIZE(65536) MASK(7FFFF) SIDEQ(0)
32 KLVSD033 BUFFERS INUSE(3) MAX(9) GETS(245) FREES(242)
33 KLVSD033 SEGMENTS INUSE(1) MAX(1) GETS(1) FREES(0) Q(1) QMAX(1)
34 KLVSD032 POOL BUFSIZE(2560) SEGSIZE(65536) MASK(1FFFFFF) SIDEQ(0)
35 KLVSD033 BUFFERS INUSE(53) MAX(57) GETS(340) FREES(287)
36 KLVSD033 SEGMENTS INUSE(3) MAX(3) GETS(13) FREES(10) Q(1) QMAX(2)
37 KLVSD032 POOL BUFSIZE(1920) SEGSIZE(65536) MASK(FFFFFFFF) SIDEQ(0)
38 KLVSD033 BUFFERS INUSE(1) MAX(2) GETS(60) FREES(59)
39 KLVSD033 SEGMENTS INUSE(1) MAX(1) GETS(36) FREES(35) Q(1) QMAX(1)
40 KLVSD039 END OF BUFFER POOL INFORMATION
41 ----------------------------------------------------------------
Where:
01
Is a ITMS:Engine header message.
02
Is an ITMS:Engine header message.
03 - 23
Is an ITMS:Engine message specifying the following values:
  • SIZE: The range (m-n, in bytes) of the sizes of data blocks in the storage area. For example, SIZE(1-16) indicates that this area contains all of the blocks that are from 1 to 16 bytes long.
  • USE: The number of blocks in use.
  • TOTAL: The total number of storage blocks allocated.
    Note: If the values of both USE and TOTAL are zero, the message does not appear
  • ACCESSED: The total number of times the storage block size was accessed.
24
Is an ITMS:Engine message specifying the following values:
  • OVERHEAD: The amount of storage (in bytes) used for storage control.
  • LIMIT: The size (in bytes) of the largest block that can be allocated.
  • SLOPE: An IBM-internal parameter.
  • SIZES: Specifies the number of storage areas.
  • TOTAL: Specifies (in kilobytes) the total amount of storage.
  • FREE: Specifies (in kilobytes) the amount of storage available.
25
Is a continuation of the previous ITMS:Engine message specifying the following value:
  • OVERHEAD: The amount of storage (in bytes) used for storage control.
26
Is an ITMS:Engine message specifying the following values:
  • TMS : The amount (in bytes) of temporary storage allocated. ITMS:Engine uses this storage, for example, to resolve a string expression. In general, this value should be zero.
  • PREFIX: The length (in bytes) of the storage block prefix.
  • CUSHION: The overhead (in bytes) for each storage block. This value is equal to the value of PREFIX plus the debug overhead, if any.
27 - 40
Is buffer pool usage information.
41
Is a line of dashes indicating the final line of the display.