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 DatabaseTune Your DatabaseIndex 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:
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.