How to tune/reorganize CA Datacom database for CA 7


Article ID: 124869


Updated On:


CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Workload Automation CA 7 Edition


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 CA 7 configuration, there are a number of options recommended that lessen the need for reorganization.


Release: SEVDT.99000-12.0-Workload Automation-CA 7 Edition


CA DocOps documentation for CA Workload Automation CA 7® Edition - 12.0 indicates that you normally might not need to perform reorganization on your database areas, except in rare circumstances. Please see the following sections: 
Reorganize Your Database
Tune Your Database
Index Defragementation

In essence, the reason that you do not need to run a special reorganization is that your data is maintained in memory within the MUF, and is accessed using optimized memory fetch processing. The recommended initial configuration of your MUF Startup Options is that you define memory for 115% of the current data allocation for many of the data areas. You can see your actual configuration 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 of your tuning and optimization needs should be met. As there may be exceptions and unique situations, tuning is never a "one size fits all" approach.

Additional Information

For more information about CA 7 operation, please refer to the CA DocOps website: CA Workload Automation CA 7® Edition - 12.0

For more information about tuning and optimizing your CA Datacom databases, please refer to the following CA DocOps pages:
Version 15.1CA Datacom/DB Database and System AdministrationOptimizing CA Datacom/DB Performance
Version 15,0 -  CA Datacom /DB Database and System AdministrationOptimizing CA Datacom /DB Performance

For Version 14.0, please refer to the CA Datacom Version 14.02 Bookshelf, and the CA Datacom/DB Database and System Administration Guide, in the section "Optimizing CA Datacom/DB Performance".

As always, please contact CA Technologies support for CA Datacom if you have further questions.