You use this dialog box to configure the data collection settings for the CA 1 feature.
The CA 1 Status feature is turned off by default. It is recommended that you first run a collection cycle off-hours to test how the feature may affect performance. Use the information from this test session to estimate the impact of collection on the address space of the Tivoli® Enterprise Monitoring Server and on the overall z/OS system. This estimate can help you choose optimal configuration settings, such as what time of day to start collection of data and what deadline (if any) to impose for completion of collection. Please refer to the next section for sizing and provisioning requirements.
Sizing
Use the following formulas to determine the required primary and secondary allocations of each VSAM cluster or index.TMC values
VSAM values:
Total Space:
If "allow reporting during collection" is enabled:
SMS data class
An SMS data class must be provided to govern the VSAM datasets maintained by the collector. The SMS data class should have the following attributes:Section/option | Comments |
---|---|
Collection Scheduling | |
Start collection at (hh:mm) | Select this check box to activate most of the
other fields in the dialog box. hh is an integer from 1 to
12, and mm is an integer from 0 to 60. By default, collection is set to run daily. You deselect specific days of the week in the Every area to prevent collection on specific days. Start collection at causes the backend controller to schedule Summary Collection to begin at the specified time on the specified days of the week. If unchecked, Summary collection does not automatically run. |
Stop collection at (hh:mm) | Use this setting to prevent data collection
from continuing into a time period when critical jobs run that require
significant amounts of system resources. You can also use this setting
to prevent collection when the CA 1 subsystem itself is in heavy use
and requires exclusive access to its TMC. hh is an integer
from 1 to 12, and mm is an integer from 0 to 60. If you specify a stop time and collection is halted because that time is reached, attributes and reports for every volume and data set processed up to the point that collection was halted are available for viewing from the Tivoli Enterprise Portal. Stop collection at causes the backend controller to halt the CA 1 Summary Collection process at the indicated time of day. This response can be useful in environments where the CA 1 TMC is extremely large and the summary process interferes with normal CA 1 processing, or where a limit should be placed on the amount of elapsed time/resources consumed by the summary collection process. |
Collection Options | |
Allow reporting during collection |
When you select this check box, a second VSAM cluster will remain in existence so that the user may request data during a collection cycle.
Data from the previous collection cycle will be shown. By deselecting this check box, only a single VSAM cluster will be maintained
and access to data will not be possible during a collection cycle.
Please refer to the Sizing and provisioning requirements section above for details on how this will affect your DASD requirements. |
SMS Data Class |
An explicit SMS data class must be provided to the govern the VSAM datasets used by the collector module.
Please refer to the Sizing and provisioning requirements section above for more details on this value. |
Collection Status | |
Status message: Force Start button or Force Stop button | Status messages include, Collection
not active, Collection in progress, Collection
waiting, Collection failed, Collection
completed, Collection halted due to deadline,
and Collection halted by user or operator. Click Force Start to manually force data collection to start. A Force Stop button is available while data collection is running to manually force data collection to stop. Results are displayed that include all volumes and data sets processed up to the point that collection was halted. And the status shown is Collection completed. If you stop the collection by clicking on Force Stop button, the state in the Collection Status area is Collection halted by user or operator. The status is not Stopped. |