To provide the best performance to customer applications, databases are analyzed and the data areas are often reorganized to orient the data to the native key structure. In the Workload Automation CA 7 configuration, there are a number of options recommended that lessen the need for reorganization.
z/OS
Workload Automation CA 7 12.1
Datacom/AD 15.1
The documentation for Workload Automation CA 7 indicates that reorganization on the CA 7 database should not be needed , except in rare circumstances.
See the following sections:
In essence, the reason that no reorganization is needed is that the data is maintained in memory within the Datacom Multi-User Facility (MUF) , and is accessed using optimized memory fetch processing. The recommended initial configuration of the MUF Startup Options is to define memory for 115% of the current data allocation for many of the data areas. That can be seen by looking at the MUF output for lines like this:
COVERED IXX0770,115%
COVERED MIN0770,100%
COVERED DFS0770,115%
In addition to having so much of the data in memory, the content of some tables is so dynamic that it is quite difficult to maintain a reorganized structure for very long. For example, the PRN table is adding new records for completed jobs and deleting records that are stale or expired based on business rules. This means that the blocks containing data are always changing, making the reorganization effort somewhat futile.
By following the recommendations in the CA 7 documentation above, most tuning and optimization needs should be met. As there may be exceptions and unique situations, tuning is never a "one size fits all" approach.
For more information about CA 7 operation, please refer to the online documentation CA 7 Workload Automation 12.1.
For more information about tuning and optimizing Datacom databases, please refer to Optimizing Datacom/DB Performance.
As always, please contact Broadcom support for Datacom if any further questions.