RE: MODS confusion

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de
J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx

Technically you can (it does not even have to be a character
field), but it might be confusing for whoever has to do
anything with the program after you.

What is the use of SP2? If all it does is call the RPG III
program, you might as well create a prototype for the RPG III
program (yes, you can) and call it directly from SP1.

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


So, I will have to change all the callers so that they pass an array DS instead of a MODS so that they will compile. But is the end result any different?