IBM AS/400 manual RPG/400

Differences

Between

OPM

RPG/400

and

ILE

RPG

4. Call

performance

for

LR-on will be greatly

improved

by

having

no

PSD

PSDS

no

longer

than

80

bytes,

since

some

of

the

information

that

fil

PSDS

after

80

bytes

is

costly

to

obtain.

If the PSDS is not code

short

to

contain

the

date

and

time

the

program

started,

these

t

not

be

available

in

a

formatted

dump.

All

other

PSDS

values

will

be

no

matter

how

long

the

PSDS

is.

5. The

prefix

for

ILE

RPG

inquiry

messages

is

RNQ, so

if

you

use

reply

list,

you

must add RNQ entries similar to your existing

RPG

6. In

OPM,

if

a

CL

program calls your RPG program followed by a MONMSG

the

RPG program

receives

a

notify

or

status

message, the

CL

MONMSG

not

handle

the

notify

or

status

message.

If

you

are

calling

ILE

CL and

both

are

in

the

same

activation

group, the

ILE

CL

MONMSG

will

the notify or status message and the RPG procedure

will

halt

imme

without

an

RPG

error

message

being

issued.

For

more

information

se

lems

when

ILE

CL

Monitors

for

Notify

and

Status

Messages”

on page 2

7. When

displaying

a variable using the ILE

source

debugger,

you

wi

able

results

if:

¹

the

ILE

RPG

program

uses

an

externally

described

file

and

¹

the

variable

is

defined

in

the

data

base

file

but

not

refe

RPG

program.

I/O

1.In ILE RPG you can read a record in a file opened for updat overridden with SHARE(*YES), and then update this locked record in a

program that has opened the same file for update.

2. You	cannot	modify the	MR indicator	using the MOVE or SETON operatio
(RPG	III	only prevents	using SETON	with MR.)

3. The File Type entry on the File specification no longer dictates operations that must be present in the calculation specifications.

For

example,

in

RPG III, if

you

define

a

file

as

an

update

f

have

an UPDAT operation later in the program. This

is

no

longer

tru

IV.

However, your file definition still must be

consistent

with

th

present

in

the

program.

So

if

you

have

an

UPDATE

operation

in

your

the

file

must

be

defined

as

an

update

file.

4. ILE

RPG

will allow record blocking even

if

the

COMMIT

keyword

is

s

the

file

description

specification.

5. In

RPG

IV,

a

file

opened

for update

will

also

be

opened

as

d

You

do

not

need

any

DELETE

operations to

make it

delete

capable.

6. In

RPG

IV,

you

do

not

have

to

code

an

actual

number

for

the

devices that will be used by a multiple-device file. If you sp

MAXDEV(*FILE)		on a	file description		specification, then	the number			o
areas	created		for	SAVEDS and SAVEIND is based on the			number	of	d
that your		file	can	handle. (The	SAVEDS, SAVEIND, and MAXDEV keywords
an RPG	IV	file	description specification correspond			to	the	SAVDS,

NUM options on a RPG III file description specification continuati respectively.)

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