How to update record counts in the CXX for CA Datacom


Article ID: 39774


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



On occasion, something may happen within the CA Datacom MUF to cause the record counts for a table listed in the CXX to be incorrect – if the MUF abends while the table is open, if a backup of the CXX from an earlier point in time is reloaded, etc.

While it is possible to take the suspect database offline to run the DBUTLTY BACKUP and LOAD functions, this is not the best approach for tables that are extremely large or for companies that move ever closer to 24x7 availability.

In these situations, there is another option available that can make this information more accurate, and it is another DBUTLTY function called RETIX. The RETIX function is most-well known for its ability to rebuild an index from the various data areas in a database, but another part of its function will recount the records in the tables, too.


To use this function to reset the record counts, you will use the standard DBUTLTY JCL, with the below SYSIN samples, for either a single area or for an entire database.

  • To reset the counts for a single area:
  • To reset the counts for an entire database:

Note that this task runs with the MUF open and without disabling or turning off access to the database. If no other task is concurrently adding or deleting records, this function will produce an accurate count of the number of records; if another task is running concurrently, the new record count could be correct, or it could be high or low. Therefore, if it is possible, this function should run while there is no other add or delete activity in the database, so that it produces the best result.

If running CA Datacom/DB or CA Datacom/AD version 14.0, be sure that you have applied PTF RO66356 (DB 14.0 #325), "CXX ON DASD UPDATED WHEN RETIX *SETR/*DATA ARE RUN" so that the updated statistics are written to the DASD copy of the CXX; otherwise you should include a COMM OPTION=STATS,DBID=nnnnfunction immediately following the RETIX function. If you are running version 15.0, this is not needed.

Additional Information:

For further information about using the RETIX function, please refer to the following Guides.

CA Datacom/DB Version 14.02 DBUTLTY Reference Guide, in the section “RETIX (Reconstruct Index)Rebuilding the Data Space Index or Recounting Records › How to Use

CA Datacom/DB Version 15.0 DBUTLTY Reference Guide, in the section “RETIX (Reconstruct Index)Rebuilding the Data Space Index or Recounting Records › How to Use

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



Component: DB