CA 1 Collection Control dialog box
You use this dialog box to configure the data collection settings for the CA 1 feature.
- You must delete, reallocate, and initialize the RKS3DSAx persistent data stores. Otherwise, the new CA 1 tables cannot be correctly defined for historical collection.
Sizing and provisioning requirements
The collector module will create the following VSAM data sets during a collection cycle:- A primary data cluster with 3 alternate indices. This is a non-transient cluster which holds the output from the collection cycle.
- A secondary data cluster with 3 alternate indices. This is an optional copy of the primary cluster and is used by reporting modules to provide data while a collection cycle is in progress. If you disable "allow reporting during collection" then this cluster will not be created.
- A scratch data cluster. This is a transient cluster which only exists during the collection cycle.
Sizing
Use the following formulas to determine the required primary and secondary allocations of each VSAM cluster or index.- TMC values
- V (volume): total volume count (active + scratch, not including deleted volumes)
- D (dataset): active volume count + active DSNB count
- T (total objects): V + D + (D * 0.10) + (V * 0.01)
- VSAM values
- VP (primary allocation in MB): ((T * 612) + (T * 612 * 0.10)) / (1024 * 1024)
- VS (secondary allocation in MB): VP * 0.20
- VT (total allocation in MB): VP + VS
- Total space
- If "allow reporting during collection" is enabled:
- Total Primary Allocation in MB: VP * 9
- Total Secondary Allocation in MB: VS * 9
- Total Allocation in MB: VT * 9
If "allow reporting during collection" is disabled:- Total Primary Allocation in MB: VP * 5
- Total Secondary Allocation in MB: VS * 5
- Total Allocation in MB: VT * 5
SMS data class
An SMS data class must be provided to govern the VSAM data sets maintained by the collector. The SMS data class should have the following attributes:- Extended Addressability is required for VSAM data sets greater than 4GB in size.
- Multi-volume is recommended.
Details regarding the Collection Control dialog box
| 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 TMS 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 previous Sizing and provisioning requirements section 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 data sets used by the collector module. Please refer to the previous Sizing and provisioning requirements section for details on how this will affect your DASD requirements. |
| 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. |