RETIX (Reconstruct Index) › Rebuilding the Data Space Index or Recounting Records › When to Use › Using KEYNAME=*SETR to Recount Records and Update CXX

Using KEYNAME=*SETR to Recount Records and Update CXX

The count of records in a table, as known to the CXX, can become wrong if the MUF is restarted after a MUF outage occurs. The DBUTLTY RETIX function, with the KEYNAME=*SETR option, lets you recount the records and set the new value in MUF. Using the keywords DBID=, AREA=, and KEYNAME=*SETR with RETIX opens the database and reads through the area, using GSETP/GETPS commands to find all records. After processing all blocks, the count sets in the CXX definition. If no other task is concurrently running to do adds or deletes, at the completion of the RETIX function the count reflects the number of records. If another task is concurrently running, however, the new counts could be high, low, or equal, depending upon concurrency, but they will still almost certainly be more accurate than before the RETIX function with the KEYNAME=*SETR option was executed.

If the counts need to be updated on DASD, follow the RETIX function with a COMM STATS function.

Note: The RETIX function executes only for a URI area and only if MUF is not currently running as a full MUFplex with two or more enabled or logically executing MUFs.