Ansicht
Dokumentation

RNI2002 - Key comparison for file &7 is being performed using the *HEX collating sequence. ( OS/400 )

RNI2002 - Key comparison for file &7 is being performed using the *HEX collating sequence. ( OS/400 )

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by IBM.
SAP E-Book


Message : RNI2002
Key comparison for file &7 is being performed using the *HEX collating sequence.

Message Long Text :

Cause . . . . . : The RPG program &1 in library &3 at statement &4 attempted to do a key comparison during a READE, READPE, or SETLL operation; or during Sequential-within-limits processing by a record address file. The key comparison was not able to be performed by Data Management. As a result, the key comparison was done using the *HEX collating sequence, which may give a different result from the key comparison done by Data Management.
Some of the DDS features that cause the key comparison to differ are:
- ALTSEQ was specified for the file.
- ABSVAL, ZONE, UNSIGNED, or DIGIT keywords on key fields.
- Variable length, Date, Time, or Timestamp key fields.
- ALWNULL was specified for the file and either the key in the file or in the search argument has null values.
- The SRTSEQ for the file is not *HEX.
This may give different results than expected when the content of the fields on which the access path is built differs from the actual content of the fields, or if the fields are null-capable.
Some of the conditions that may cause Data Management not to be able to perform the requested key comparison are:
1 A Get Next Key Equal following a Read Multiple does not require a search key to be provided.
2 Keyed feedback was not requested for file &7 at open time.
3 The Read request was performed via a group-by view of the data.
4 File &7 is a Distributed Data Management (DDM) file and the remote file was created before Version 3 Release 1 Modification 0.
This message is only issued once after the file has been opened. Subsequent key comparisons for this file may be done by Data Management or using the *HEX collating sequence, depending on the cause.
The actual file is &8.
Recovery . . . : If key comparisons performed using the *HEX collating sequence are acceptable then ignore this message. Otherwise, try the recovery that corresponds to the relevant condition from the numbered list above:
1 Issue an OVRDBF command with either SEQONLY(*NO) or SEQONLY(*YES 1) specified so a Read multiple will read only one record.
2 Ensure the open is requested with keyed feedback.
3 Use a physical copy of the group-by data.
4 Change the DDM file &7 so that the remote file is on a Version 3 Release 1 Modification 0 or higher system.

Message File : QRNXMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by IBM.

Length: 3298 Date: 20240426 Time: 150518     sap01-206 ( 3 ms )