IBM AS/400 manual Analyzing Your Conversion

Models: AS/400

1 489
Download 489 pages 47.95 Kb
Page 417
Image 417
Analyzing Your Conversion

Analyzing Your Conversion

¹Record address file (RAF) entries on extension specifications have

replaced by the keyword RAFDATA on the File Description specificat

¹ The

line

counter

specifications have been eliminated. They have b

by

the

keywords

FORMLEN and FORMOFL on the file description specific

See

Lines

6 and

7.

¹All specification types have been expanded to allow for 10-charac fields and files.

¹ In RPG IV, data

structures (which are defined using

definition

must precede the input specifications.

 

 

Note

that

in

the

converted source, the data structure

DS1

(Line

moved to

precede

the specification containing the FORMAT1

informatio

19).

 

 

 

 

 

 

 

 

¹ In

RPG

III,

named

constants can appear in the middle

of

a dat

is

not

allowed

in

RPG

IV.

 

 

In the converted source, CONST1 (Line 16) has been moved to follow structure DS1 (Line 11).

¹ If a specification is moved, any comment that precedes it is al

In

the

converted

source, the comments above CONST1 and DS1 were m

with

the

following

specifications.

¹In RPG III, to define an array as a data structure subfield

array

and

a

data

structure

subfield with

the

same

name.

This

d

is not allowed in RPG IV. Instead you specify the

array

attrib

define

the

subfields

using

the

new keyword

syntax.

 

 

 

 

In this example, ARR1 is defined twice in

the

OPM

version,

but

h

merged

into

a

single

definition

in converted

source.

See

Lines 13

The merging

of

RPG

III array

specifications may result

in

the

 

array definitions. If the reordered arrays are compile-time arr

loading

of

array

data may be affected. To overcome this proble

vides

a

keyword

format for the ** records. Following **, you enter

keywords FTRANS, ALTSEQ, or CTDATA. If

the keyword

is

CTDATA,

you

 

enter

the

array

or

table name in

positions 10

-

19.

 

 

In

this

example,

the array ARR2 now precedes

array

ARR1,

due

of

the

two

RPG

III specifications for ARR2. The Conversion Aid

the

keywords and

array names in the converted ** records, which

correct

loading of

the compile-time

data. See

Lines 29

and

31.

¹Note that array syntax has changed. The notation ARR1,3 in RPG I ARR1(3) in RPG IV. See line 28.

Analyzing Your Conversion

The

Conversion Aid

provides you with two ways to analyze your convers

They

are:

 

¹

The

conversion

error report

¹

The

log file

 

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

Page 417
Image 417
IBM AS/400 manual Analyzing Your Conversion