Create historical data collections
Tips
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.
Warning
With higher granularity (a smaller interval means more data collected) there are 2 obvious considerations:
- CPU overhead on data collection and retrieval;
- 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 value | Attribute group | Collection interval (minutes) |
|---|---|---|
| adrspacs | Address Spaces | 1 |
| depregns | Dependent Regions Statistics | 1 |
| ictcbcpu | TCBCPU Utilization | 1 |
| kipimshlt | IMSPLEX Health | 1 |
| poolutil | Pool Utilization | 1 |
| subpools | Sub Pool Statistics | 1 |
| vsamsubp | VSAM Subpools | 1 |
| kip_lrti02 | IMS RTA Group Items Slots | 1 |
| balg | Balancing Groups | 1 |
| bufpools | Buffer Pool Statistics | 1 |
| dlideprg | Dependent Regions Detail | 1 |