tableBASE can produce a report summarizing your use of tableBASE. This report, known as the tableSPACE Report, includes such information as the space occupied by each table in the tableSPACE Region (TSR), the number of accesses for each table, and much more. These statistics provide information on usage during the life of the region and can be used to optimize performance in all environments.
You control the frequency with which this information is collected. For a local TSR, this is done using the STROBE parameter. For example, if you specify a strobe interval of 10,000, the statistics collection routine is called after every 10,000 calls to tableBASE. The tableSPACE report can be printed on demand or when tableBASE terminates.
For a VTS-TSR, the STROBEMETHOD parameter is also required. A value of 0, 1 or 2 for STROBEMETHOD means that the STROBE parameter still represents the number of calls after which to collect tableBASE usage statistics. A value of 3 for STROBEMETHOD means that STROBE now represents the number of minute intervals after which to collect usage statistics. The default value for STROBEMETHOD is 0.
For STROBEMETHOD of 0, 1 or 2, strobe processing has been improved so that tableBASE processing is prevented from waiting for the strobe report. If the number of calls in the STROBE parameter is set to a small value and tableBASE calls are made more frequently than strobe reports can be produced, the frequency of reports may change due to strobe reports being bypassed.
For tableBASE performance reasons, tableBASE strobe is now handled by a sub-task. Since the sub-task is running concurrently with tableBASE calls, the status of the TSR can change while the strobe data is being gathered. This may lead to apparent inconsistencies in the reports, such as the total number of tables open, and the actual number listed.