Yes, I've read some posts somewhere before saying that export variable is
not the best thing to use. Therefore, I've never try to use it. But to use
that feature, I would assume that PROGRAMA and PROGRAMD will need to somehow
bind to each other, no?....
"Jon Paris" <jon.paris@xxxxxxxxxxxxxx> wrote in message
news:mailman.48911.1308000743.2702.rpg400-l@xxxxxxxxxxxx...
There has to be a better way to handle the whole thing - but in some
respects your proposed solution is a reinvention of the wheel. What's wrong
with simply adding the Export keyword to the variable's definition and
retrieve it elsewhere by specifying Import? Not one of my favorite ILE
features but it is a lot less code (and less confusing think) than your
proposed solution.
Jon Paris
Partner400.com
Need the best in SQL education? Check out www.DB2foriDirections.com
On Jun 13, 2011, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
My idea is to create an export procedure in a service program. This
procs will accepts the PROGRAMA's two entry-parms by reference.
This mailing list archive is Copyright 1997-2025 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
