001

01

Y

Y

INDEX BEING OPENED IS FOR WRONG DATABASE.

Probable JCL error. Also possible
is that the data set has been
overlaid by an index for a different database.

Review JCL provided to be pointing to the correct data set name. In z/OS, if dynamic allocation is being used, review the data set name dynamically allocated for accuracy. If these are correct, review and correct a situation where another task used this data set for its index. An INIT and RETIX for all areas of base is required to rebuild the index.

002

02

Y

Y

INDEX IS NOT LINKED TO THE
CXX BEING USED.

The following are possible reasons:

• Probable JCL error.
• The data set has been overlaid
  by an index for a different database.
• The name of the CXX was
  changed during an initialize
  and load of the CXX.
• The LINK keyword of the
  DBUTLTY function CXXMAINT ALTER may have been specified incorrectly. The CXXMAINT
  ALTER LINK option allows you
  to suppress an edit to ensure
  that an Index Area (IXX) or
  data area is being accessed through the proper Directory (CXX).

Review JCL provided to be pointing to the correct data set name. In z/OS, if dynamic allocation is being used, review the data set name dynamically allocated for being accurate. The error message contains the name of the CXX being used and the name of the CXX to which this index is linked.

If the necessary index has been destroyed, an INIT and RETIX of all areas is necessary to rebuild the index. If you know that the data in the index is correct (as in a CXX name change) then use the DBUTLTY LINK function to change the CXX link in the index to the correct CXX. For more information, see the CA Datacom/DB Database and System Administration Guide and the CA Datacom/DB DBUTLTY Reference Guide.

003

03

Y

Y

INDEX WAS EITHER CORRUPTED BY A FAILED LOAD OR RETIX USING OPTIMIZE PARM, OR
INDEX BUILDING IN PROGRESS DURING A LOAD OR RETIX WITH OPTIMIZE=YES BUT NO CORRUPTION OCCURRED.

The index was either corrupted by a LOAD or RETIX that used OPTIMIZE but failed to complete, or index processing was in progress during a LOAD or RETIX that used OPTIMIZE.

If a RETIX or LOAD against the database failed while using the OPTIMIZE option, the index must be initialized and all areas reLOADed or RETIXed. If the error occurred while a LOAD with OPTIMIZE or a RETIX with OPTIMIZE was in progress against any area in the database, allow the process to complete before re-attempting the job that incurred this return code, and index initialization is not required in this case.

004

04

Y

Y

INDEX DEVICE TYPE CHANGE

The device type in which the index now resides is not the same device type as when it was initialized.

The index must not be moved from one device type to another without using the INIT and then the LOAD or RETIX functions to rebuild it.

005

05

N

N

You are trying to open a read-only DBID (non-optimized), and there has been a prior DEFRAG failure.

Open the DBID for update.

006

06

Y

Y

POSSIBLE JCL ERROR

An error was received while reading
an index area control block. The problem could have occurred
because of a JCL condition such as pointing to a wrong data set, that
is to say, the problem is not with
the data set itself but with the JCL.

Ensure that your JCL is correct, for example that it is pointing to the correct data set.

007

07

N

N

You are trying to open an index that has not been initialized.

Initialize the index that has been created but not initialized. A CXX report for the database can tell you which indexes are not initialized.

043

2B

Y

Y

NO VALID INDEX

The attempt to open a database
failed because the index was not initialized.

Before attempting to open the database, initialize the index by executing the DBUTLTY INIT AREA=IXX function.