MF61657 - OSP-DB-OTHER-INCORROUT for key positioning, if OPNQRYF KEYFL

TYPE PROGRAM  RELEASE   NUMBER   MIN/MAX  OPTION
---- -------- --------- -------  -------  ------
CO   5770999  V7R3M0    MF61658   00/00    0000



NOTICE:
-------
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels.  This PTF may be a prerequisite
for future PTFs.  By applying this PTF you authorize and agree to the
foregoing.

This PTF is subject to the terms of the 'IBM License Agreement for Machine
Code', the terms of which were provided in a printed document that was
delivered with the machine.

SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.





APAR Error Description / Circumvention

-----------------------------------------------
Migrated from 610 to 720 since then have experience incorrect
output from a production processes

The key fields being used in the customer's RPG do not match
what is in OPNQRYF. The following changes were tried:

- remove the 4th key in OPNQRYF and recompile CL program - same
issue
- Created an index to match the RPG key fields and recompile RPG
program - same issue
- RPG does use SETLL but not using the options in memo to users

Results:
- CQE returns 4 rows with building a temp file
- SQE returns 2 rows with using PF Access path to access the
data

CORRECTION FOR APAR MA45431 :
-----------------------------
The SQE optimizer may select an index that has ordering that is
exactly reversed from the KEYFLD ordering for native queries, to
save time and cycles building an index with the required
ordering.

When this is done, the collation is reversed by the query to
obtain the required ordering.  There was a problem with this
reversal for certain key positioning requests.  This could
result in some equal not being returned.  This issue was fixed.

CIRCUMVENTION FOR APAR MA45431 :
--------------------------------
None.


Activation Instructions


None.




Special Instructions


None.


Default Instructions

THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.



Supersedes

PTF/FIX NO(S).  APAR TITLE LINE
--------------  ------------------------------------------------------------
     NONE

Summary Information

System i Support