Re: Passing a MODS as a parameter

Actually what is passed is the address of whatever occurrence was set at the time of the call. If you did an Occur 1 before the call then it is the address of the first element. Had you done some processing that left the current occurrence at (say) 20 before the call then the address of 20 would be passed.

The only way to process a MODS correctly when passed as a parm is to increment the occurrence _within_ the called routine.

But Birgitta is right - you should be using a DS array which will avoid all of the messiness. Basically MODS are deprecated - DS arrays are a much better approach.

On Feb 11, 2020, at 11:42 PM, Frank Kolmann <frank.kolmann@xxxxxxxxx> wrote:

Hi

A while back I wrote a program that uses QDFRTVFD api.
source is here
https://wiki.midrange.com/index.php/QDFRTVFD_%E2%80%94_Retrieve_Display_File_Description


I am quite sure I had this working.
But Dan Bale mentioned to me that the code is not working.

Reason why the program fails , is only the first OCCUR of the MODS is passed to the caller program.

Has something changed?

How I coded the pass of the MODS is to define the MODS in both the caller and called program and pass the pointer to the MODS via a parameter.

Thanks for any suggestions.

Frank Kolmann
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com