How to interpret output messages from TUNE INDEX?

Document ID : KB000023202
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

The TUNE INDEX can issue messages which at first reading can be misleading. Knowledge of how the utility works at a high level can help in understanding these messages.

Instructions:

The TUNE INDEX utility can operate on more than one index occurrence, specifically, if the index being TUNED is a user-owned indexed set.

If TUNE INDEX encounters an unexpected non-zero error status, it will issue a combination of messages which might be confusing, such as:

DB002994 T171 C0M333: IDMSTUNE  -  processing started                        
DB002994 T171 C0M333: IDMSTUNE  -  Indexes selected for processing:          
DB002994 T171 C0M333: IDMSTUNE  -  R1-NDX (IBC=10) in area DML-AREA-1                                                              
DB002994 T171 C0M333: IDMSTUNE  -  Database error 0011 in area DML-AREA-1                                                           
DB002994 T171 C0M333: IDMSTUNE  -  Index R1-NDX occurrence 170502:1    
DB002994 T171 C1M333: IDMSTUNE  -  Skipping this index occurrence            
DB002994 T171 C0M333: IDMSTUNE  -  Statistics for area DML-AREA-1        
DB002994 T171 C0M333: IDMSTUNE  -  Orphan adoption read 0 records                                                                 
DB002994 T171 C0M333: IDMSTUNE  -  Orphan adoption adopted 0 index orphans (of which 0 SR8s)   
DB002994 T171 C0M333: IDMSTUNE  -  Resequencing read 1 records               
DB002994 T171 C0M333: IDMSTUNE  -  Statistics for area OPER-AREA-SGEN28      
DB002994 T171 C0M333: IDMSTUNE  -  Orphan adoption read 7,750 records (of which 7,747 SR8s)                                                                       
DB002994 T171 C0M333: IDMSTUNE  -  Orphan adoption adopted 14 index orphans  
DB002994 T171 C0M333: IDMSTUNE  -  Resequencing read 9 records 
DB002994 T171 C0M333: IDMSTUNE  -  processing completed

When errors are encountered and the utility is running in CV mode, it will rollback the changes for that index occurrence only, and then attempt to continue on and process the remaining indexes. That is what is meant by the "Skipping this index occurrence" message. TUNE INDEX will ultimately complete and issue messages that it did end successfully, which could be confusing when taken in conjunction with the "Database error" message. In this case it will end with a return code of 4.

What is meant is that it did go on and successfully process other indexes, after the database error was encountered and changes for that index occurrence were rolled back.

If the TUNE INDEX utility is being run in local mode, no recovery is possible, and none of this occurs. When a database error is encountered, the utility aborts, ends with a return code of 8, and the database must be restored.

Additional Information:

For more information regarding TUNE INDEX, see the manual, CA IDMS Utilities Guide chapter 5 "Utility Statements", "TUNE INDEX".