RE: Parameter prototype question

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt

If you specified VALUE on myDossier....the calling procedure
will never see the value from GetMyDossier.

VALUE & CONST both mean a parm is input only and is protected
from being updated.

Thanks, I knew that about VALUE, but lack of experience made me forget it. Testing today quickly reminded me.
Also, I now understand what Joep meant about no such thing as an output parameters. I thought there were just parameters, full stop.

Options(*VARSIZE) would work as another suggested....but if
you use it, you should also pass another parm that indicates
the size of myDossier. That way if GetMyDossier expects at
least 7 bytes, if somebody comes along and only gives you 5
bytes, you can deal with the issue. Otherwise you'd be
corrupting memory.

The easiest way to deal with this is to pass the dossier back
as the RETURNED VALUE from GetMyDossier

evalr DisplayField_myDossier = GetMyDossier ( inputParm );

D GetMyDossier PR LIKE ( Ref_myDossier )
D inputParm LIKE ( Ref_InPutParm ) CONST

Of course you lose the Boolean returned value, but depending
on how you are using it, there are other options.

I just created a 9A work variable and passed that, then copied the result to the 7A variable.