CPI432C - All access paths were considered for file &1

CPI432C
Message Text:	All access paths were considered for file &1.
Cause Text:	The query optimizer considered all access paths built over member &3 of file &1 in library &2. The list below shows the access paths considered. If file &1 in library &2 is a logical file then the access paths specified are actually built over member &9 of physical file &7 in library &8. Following each access path name in the list is a reason code which explains why the access path was not used. A reason code of 0 indicates that the access path was used to implement the query. The reason codes and their meanings follow: Access path was not in a valid state. The system invalidated the access path. Access path was not in a valid state. The user requested that the access path be rebuilt. Access path is a temporary access path (resides in library QTEMP) and was not specified as the file to be queried. The cost to use this access path, as determined by the optimizer, was higher than the cost associated with the chosen access method. The keys of the access path did not match the fields specified for the ordering/grouping criteria. For distributed file queries, the access path keys must exactly match the ordering fields if the access path is to be used when ALWCPYDTA(YES or NO) is specified. The keys of the access path did not match the fields specified for the join criteria. Use of this access path would not minimize delays when reading records from the file. The user requested to minimize delays when reading records from the file. The access path cannot be used for a secondary file of the join query because it contains static select/omit selection criteria. The join-type of the query does not allow the use of select/omit access paths for secondary files. File &1 contains record ID selection. The join-type of the query forces a temporary access path to be built to process the record ID selection. and greater - View the second level message text of the next message issued (CPI432D) for an explanation of these reason codes.
Recovery Text:	The user may want to delete any access paths no longer needed.

CPI432C

Message Text:

All access paths were considered for file &1.

Cause Text:

The query optimizer considered all access paths built over member &3 of file &1 in library &2.

The list below shows the access paths considered. If file &1 in library &2 is a logical file then the access paths specified are actually built over member &9 of physical file &7 in library &8.

Following each access path name in the list is a reason code which explains why the access path was not used. A reason code of 0 indicates that the access path was used to implement the query.

The reason codes and their meanings follow:

Access path was not in a valid state. The system invalidated the access path.
Access path was not in a valid state. The user requested that the access path be rebuilt.
Access path is a temporary access path (resides in library QTEMP) and was not specified as the file to be queried.
The cost to use this access path, as determined by the optimizer, was higher than the cost associated with the chosen access method.
The keys of the access path did not match the fields specified for the ordering/grouping criteria. For distributed file queries, the access path keys must exactly match the ordering fields if the access path is to be used when ALWCPYDTA(*YES or *NO) is specified.
The keys of the access path did not match the fields specified for the join criteria.
Use of this access path would not minimize delays when reading records from the file. The user requested to minimize delays when reading records from the file.
The access path cannot be used for a secondary file of the join query because it contains static select/omit selection criteria. The join-type of the query does not allow the use of select/omit access paths for secondary files.
File &1 contains record ID selection. The join-type of the query forces a temporary access path to be built to process the record ID selection.
and greater - View the second level message text of the next message issued (CPI432D) for an explanation of these reason codes.

Recovery Text:

The user may want to delete any access paths no longer needed.

The optimizer considered all indexes built over the specified table. Since the optimizer examined all indexes for the table, it determined the current best access to the table.

The message help contains a list of the indexes. With each index a reason code is added. The reason code explains why the index was or was not used.