×
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.
Your procedure interface defines the name of the parameter being passed.
inPlist1 likeds(plist1) const;
By using LIKEDS the data structure is automatically qualified.
So, in the Procedure you would reference the fields by qualifying access.
inPlist1.fieldname
The data structure plist1 is empty because, within the service program, it has not been set to a value.
If you "must" use the unqualified fields from plist1, then your procedure would need to load plist1 from inPlist1.
I find it best to use qualified data structures whenever possible.
Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Greg Wilburn
Sent: Monday, April 15, 2019 7:49 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Advice passing a large parameter
OK... but the subfields in inPlist1 have the same name.
When I look at inPlist1 in debug, I can see data in the subfields. Yet when referencing just the subfield name in the procedure, it is empty.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
