Create historical data collections


To ensure that ODP forwards attributes to Instana as soon as you start collecting them, update the ODP collection configuration member KAYOPEN before creating the corresponding historical data collections.


With higher granularity (a smaller interval means more data collected) there are 2 obvious considerations:

  1. CPU overhead on data collection and retrieval;
  2. DASD space to hold historical tables.

Should you grow in CPU usage or Persistent Data Store, consider raising the interval and/or skipping warehousing for certain tables on PDS and just go with open data.

Create the following historical data collections for the IMS agent. This can be done via the E3270UI or the Tivoli Enterprise Portal within the IMS workspace.

table_name field valueAttribute groupCollection interval (minutes)
adrspacsAddress Spaces1
depregnsDependent Regions Statistics1
ictcbcpuTCBCPU Utilization1
kipimshltIMSPLEX Health1
poolutilPool Utilization1
subpoolsSub Pool Statistics1
vsamsubpVSAM Subpools1
kip_lrti02IMS RTA Group Items Slots1
balgBalancing Groups1
bufpoolsBuffer Pool Statistics1
dlideprgDependent Regions Detail1
Last Updated:
Contributors: Jim Porell