IBM AS/400 manual DBCS Data in Character Fields, Ile Rpg, Dbcs

		Differences	Between	OPM	RPG/400	and	ILE RPG
give	different	results	than expected when DDS features are used
more	than one	search	argument	to	match	a	given key in the file.

For example, if ABSVAL is used on a numeric key, both -1 and 1 w succeed as search arguments for a key in the file with a value hexadecimal collating sequence, a search argument of -1 will not su an actual key of 1.

ILE RPG does key comparisons using *HEX collating sequence only for pre-V3R1 DDM files. See “Using Pre-V3R1 DDM Files” on page 313 f information.

13.

ILE

RPG

allows

the

To

File and

the

From

File specified

for preru

and tables to be different. In OPM

RPG,

both file

names

must be

they

are different

the diagnostic

message

QRG3038

is

issued.

14.

When

translation

of

a

RAF-Controlled file is

specified,

the

results

RPG may

differ

from

OPM

RPG/400,

depending

on

the translation

table.

due to the different sequence of operations. In OPM RPG/400 the retrieve record, translate and compare; in ILE RPG the sequence compare and retrieve record.

DBCS Data in Character Fields

1.In OPM RPG/400, position 57 (Transparency Check) of the control speci allows you to specify whether the RPG/400 compiler should scan cha literals and constants for DBCS characters. If you specify that should scan for transparent literals, and if a character literal t apostrophe followed by a shift-out fails the transparency check,

reparsed as a literal that is not transparent.

In ILE RPG,		there	is	no	option on	the	control	specification		to	sp
the compiler should perform transparency check								on	character	literal
acter	literal	contains		a shift-out		control character, regardless					of
the shift-out character within the character								literal, the shift-ou
fies	the beginning		of	DBCS	data.	The	compiler	will	check for the

¹A matching shift-in for each shift-out (that is, the shift-out

control characters should be balanced)

¹

An even

number

(minimally

two)

between the shift-in

and

the

shift

¹

The

absence

of an embedded shift-out in the DBCS data

If

the above

conditions

are

not

met,

the

compiler

will

issue

a

d

message, and the literal will

not

be

reparsed.

As

a result,

if

t

literals

in

your

OPM RPG programs that fail the transparency check

by

the

OPM

RPG

compiler,

such

programs

will

get

compilation errors

i

RPG.

2.In OPM RPG/400, if there are two consecutive apostrophes enclosed shift-out and shift-in control characters inside a character litera secutive apostrophes are considered as one single apostrophe if literal is not a transparent literal. The character literal will not literal if:

¹The character literal does not start with an apostrophe followe shift-out

¹The character literal fails the transparency check performed b

Appendix A. Behavioral Differences Between OPM RPG/400 and ILE 377RPG for AS/400