CPI4329 - Arrival sequence access was used for &12 &13

CPI4329
Message Text:	Arrival sequence access was used for &12 &13.
Cause Text:	Arrival sequence access was used to select records from member &2 of file &13 in library &1. If file &13 in library &1 is a logical file then member &8 of physical file &6 in library &7 is the actual file from which records are being selected. A file name starting with N or QUERY for the file indicates it is a temporary file.
Recovery Text:	The use of an access path may improve the performance of the query if record selection is specified. If an access path does not exist, you may want to create one whose left-most key fields match fields in the record selection. Matching more key fields in the access path with fields in the record selection will result in improved performance. Generally, to force the use of an existing access path, specify order by fields that match the left-most key fields of that access path. For more information refer to Data access on DB2 UDB for iSeries: data access paths and methods.

CPI4329

Message Text:

Arrival sequence access was used for &12 &13.

Cause Text:

Arrival sequence access was used to select records from member &2 of file &13 in library &1.

If file &13 in library &1 is a logical file then member &8 of physical file &6 in library &7 is the actual file from which records are being selected.

A file name starting with *N or *QUERY for the file indicates it is a temporary file.

Recovery Text:

The use of an access path may improve the performance of the query if record selection is specified.

If an access path does not exist, you may want to create one whose left-most key fields match fields in the record selection. Matching more key fields in the access path with fields in the record selection will result in improved performance.

Generally, to force the use of an existing access path, specify order by fields that match the left-most key fields of that access path.

For more information refer to Data access on DB2 UDB for iSeries: data access paths and methods.

If an index does not exist, you may want to create one whose key column matches one of the columns in the row selection. You should only create an index if the row selection (WHERE clause) selects 20% or fewer rows in the table. To force the use of an existing index, change the ORDER BY clause of the query to specify the first key column of the index, or ensure that the query is running under a first I/O environment.