IBM AS/400 manual Conversion, RPG III Source for TEST2, RPG III Source for COPYDS1

Resolving

Conversion

Problems

Merging

Problems

Because

of

differences between the RPG III and RPG IV language

sion

Aid

must

reorder

certain

source statements. An example of this

shown in “Example of Source Conversion” on

page 390

for the RPG III s

member

TEST1.

If

you

compare

the placement of the data structure D

Figure 194

on

page 391

and

in

Figure 195

on

page 392,

you

can

see

th

data

structure

DS1

was

moved

so

that

it precedes the record forma

Now suppose

that

the

RPG

III

member

TEST1

was

split

into

two

members

and

COPYDS1,

where

the

data structure

DS1

and

the

named

constant

CONST

are in a copy member COPYDS1.

This

copy

member

is

included

in

sourc

Figure 201

and Figure 202

show

the source

for TEST2

and

COPYDS1

respec

tively.

H

TSTPGM

FFILE1

IF

E

DISK

COMM1

FQSYSPRT O

F

132

OF

LPRINTER

LQSYSPRT

60FL 56OL

E

ARR1

3

3

1

COMM2

E

ARR2

3

3

1

IFORMAT1

I

OLDNAME

NAME

/COPY COPYDS1

C

ARR1,3

DSPLY

C

READ FORMAT1

01

C

NAME

DSPLY

C

SETON

LR

C

EXCPTOUTPUT

OQSYSPRT E

01

OUTPUT

O

ARR2,3

10

**

123

**

456

Figure

201.

RPG III Source for TEST2

I* DATA STRUCTURE COMMENT

IDS1

DS

I

1

3 FIELD1

I* NAMED CONSTANT COMMENT

I

'XYZ'

C

CONST1

COMM3

I

4

6 ARR1

Figure

202.

RPG III Source for COPYDS1

In this situation, the Conversion

Aid

would

convert

both

member

TEST2

an

copy

member

COPYDS1

correctly.

However,

when the

copy

member

is

inclu

compile

time,

it will be inserted below FORMAT1, because this is whe

directive

is

located. As a result, all

source

lines

in the

copy

mem

get

a

"source

record

is

out

of sequence" error. In RPG IV, def

must

precede

input

specifications.

Note that the Conversion Aid could not move the /COPY directive above because the contents of /COPY member are unknown.

Appendix B. Using the RPG III to RPG IV399 Conversion Aid