Previous Topic: How to Customize the Time Series Facility DatabaseNext Topic: (Optional) Check Space Used by the TSF Database Manually

Managing Databases › Time Series Facility Database › How to Customize the Time Series Facility Database › Automate Database Space Monitoring

Automate Database Space Monitoring

TSF provides a database space use monitor. This monitor runs once per hour on the half hour to measure the number of blocks used for the data area and system area. The number of blocks used includes all blocks that contain any data, from nearly empty to 100 percent full. When the usage of a data block or a system block moves above 80 percent, the monitor issues warning message ETJTS454W. The accompanying informational messages ETJTS455I and ETJTS456I provide details about the current use of each data and system area.

Whenever a data area reaches 100 percent block use, you must take the database offline. The dynamic extend facility automatically extends the data area when it becomes full and lets you continue with the database. Space is added as an additional extent using the secondary allocation amount defined for the data set in the TSDB002 job.

Dynamic extend provides temporary relief from a full condition. Schedule a manual increase in the size of the database as soon as possible. Without a manual increase in database size, the dynamic extend feature repeats each time the data area reaches 100 percent block use. This cycle continues until an IEC030I B37-04 message condition occurs.

Follow these steps:

  1. Launch your automation product, such as CA OPS/MVS.
  2. Define ETJTS454W as a trigger or event message to generate a notification that the space use is high and you must increase the TSF database space allocation. Complete this step using your site-specific practices.

    Database space monitoring is automated. When a threshold is exceeded, the ETJTS454W, ETJTS455I, and ETJTS456I messages appear.

  3. Define the CA Datacom/AD message DB01705I as a trigger or event message to your automation tool. Doing so generates a notification message that a dynamic extend has started and that a user should manually schedule an increase in the size of the database. Complete this step using your site-specific practices.