RETIX (Reconstruct Index) › Rebuilding an Index Area › When to Use › Successful Execution Requirements and Controls

Successful Execution Requirements and Controls

Environmental Requirements when MULTUSE=NO, SIMPLIFY NO, or MUF down

• The database may not be open for update anywhere.
• The database may not be open in any MUF for read.
• The database may not have any table in unloading status.

Environmental Requirements when MULTUSE=NO, Simplify YES and MUF enabled

• The database may be open for update but must have no users.

Environmental Controls when MULTUSE=NO, SIMPLIFY NO, or MUF down

• The database will be opened for update.
• The utility has no knowledge about current ACCESS database or area status.
• The utility sets no ACCESS database or area status.

Environmental Controls when MULTUSE=NO, Simplify YES and MUF enabled

• The database will be opened for update if not already.
• All areas will be closed if open.
• The utility will execute with every ACCESS database or area status.
• The utility sets protection to block other incompatible DBUTLTY functions.

Environmental Requirements when MULTUSE=YES

• The database may or may not be open for update in the connected MUF.
• The database may not be open for update in another MUF or Single User job.
• The database may not have any table in unloading status.
• The database ACCESS must be set OPTIMIZE and WRITE/UTLTY.
• The area ACCESS must be set WRITE/UTLTY.
• The area may have no table in an open User Requirements Table.
• The area may not have any other MULTUSE=YES utility executing.
• The area must be closed.
• When MULTUSE=YES, this function will not be allowed against a Data Sharing MUF if more than one is executing.

Environmental Controls when MULTUSE=YES

• The database will be opened by MUF for update.
• The utility sets ACCESS area OFF (utility set).
• The utility sets RETIX executing this MUF this database or area.