RE: MODS confusion

David,

a) If you want to be safe, make sure that all parameter lists match
exactly.
b) If parameter lists don't match, make sure you understand EXACTLY what
is going on.
c) If you don't exactly understand what is going on, read everything Scott
Klement has written about parameters and pointers (he is a brilliant
explainer) or go back to a.

But I wonder what you are trying to achieve. Replacing program calls with
procedure calls in order to be able to change to a 'real' procedure later?
If you create a prototype for the RPG III program, you don't have to
specify in your callers whether they call a program or a procedure. When
you want to replace the program with a procedure, change the prototype,
compile all the callers and you're done.

Joep Beckeringh


rpg400-l-bounces@xxxxxxxxxxxx wrote on 28-01-2010 11:11:59:

David FOXWELL

Joep, I am informed that the reason for an encapsulating
subprocedure SP2 is that the callers will not have to be modified if
the RPGIII is ever converted to a subprocedure.

However, I've been asked to correct the parameter error in SP2. I've
looked and seen how this has been done elsewhere. This is what I have

found :

Pgm RPGIV
Module1
D globalDS E DS EXTNAME(myFile) OCCURS(20)

SP1 B
D wArrayDS LIKEDS ( globalDS ) DIM ( %ELEM ( globalDS ))
CALL SP2 ( wArrayDS );

Module2
D globalDS E DS EXTNAME(myFile) OCCURS(20)

D SP2 PI
D ADS LIKEDS ( globalDS ) DIM ( %ELEM ( globalDS ))

C CALL RPGIII
C PARM ADs


Pgm RPGIII
IODS E DSMYFILE 20
C *ENTRY PLIST
C PARM ODS