RE: Multiple occurrence data structure anomaly -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Unfortunately I don't have the luxury of being able to spend time
testing hypothetical situations like that - although it would be
interesting to try it. I have my work-around by always setting the
occurrence to 1 before calling - so I'll just have to be satisfied with
that. Thanks for all your comments.

Trevor Briggs
Analyst/Programmer
Lincare, Inc.
(727) 431-1246
TBriggs2@xxxxxxxxxxx

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Friday, July 05, 2013 2:32 PM
To: RPG programming on the IBM i / System i
Subject: RE: Multiple occurrence data structure anomaly

My recommendation. Write a test program in RPG III. Do nothing but
create a
MODS with 50 occurrence. Set to some number and pass. Create a second
program to do nothing but receive.

Do the same thing you did to the programs. Convert both to RPG IV? Test.
Does the same thing If not, you know you have a problem with the
compiler.
If it works something else going on.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.