Re: external data structure in free rpgle cant be use in DCL-PI ?

Either of those would be perfect. Because really, the issue is that I want to declare the parameter in my D-specs, and then just refer to it in the PI.  However, I'm not sure how you might then define the parameter for the prototype, especially one included in a copy book.  I think you'd have to include the data structure in the /COPY.


On 3/12/2020 5:47 AM, Barbara Morris wrote:

On 2020-03-11 6:37 p.m., Jon Paris wrote:

To allow a variable (say a DS) referenced in a PI relate to a variable already defined in the code.

This could be done with *Entry Plist - but you get a variable already defined if you try to do it in free-form.

That difference was where this thread started.

*slaps forehead*

I have to admit that I don't think that we even thought of allowing a parameter in the PI to refer to a variable that was already defined.

I think it didn't occur to us was because the PI parameter is more of a "definition" than a *ENTRY PLIST parameter is. I was going to say "especially for a LIKEDS definition", but that rule was in place long before LIKEDS.

You're right, that could be done. I think it would need some kind of keyword on the non-PI definition though, to indicate the programmer's intention for it to actually be a PI parameter. Or maybe a special kind of PI parameter that says the actual parameter is defined elsewhere.