OPNQRYF Key Mismatches with RPG on versions 7.2 and beyond

Hi All,

We are considering an OS upgrade from 7.1 to 7.3.

I was reading thru the release notes. Following is an exact excerpt from
the 7.2 release notes that caught my attention.

I am unable to understand the solution.

Is the recommended solution to simply Re-Compile the RPG that is called by
the CL that does the OPNQRYF with KEYFLD ?

OR do i need to change the KEY fields within the PF (DDS) to match the KEY
fields referenced by the OPNQRYF & then recompile the RPG ?


*RPG application and OPNQRYF key mismatches might produce*

*different results*



Existing RPG applications that position a file using *SETLL *or *SETGT *with
*LOVAL or *HIVAL, where the file corresponds to an OPNQRYF native query,
might produce different results in v7r2 than in prior releases. This
difference will only occur in cases where the RPG application was compiled
with a file having a different key definition than what was specified on
the *OPNQRYF KEYFLD *parameter. This mismatch was typically caught at
application coding time, and corrected. However, certain mismatches can
appear to produce the results expected by the programmer, and so it was not
previously discovered.



In v7r2, depending on the nature of the mismatch, the behavior may be
different. If this mismatch is discovered, the application should be
recompiled to ensure the key definitions match. Also, if *SETLL *or
*SETGT *with
*LOVAL or *HIVAL is used only to position to the top or bottom of a
collated result set, then consider using SETLL *START or *END, which does
not require keys generated by the compiler.

----
Regards,
Mohan Eashver