× 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.



Ok let me ask the question I should have asked in the first place.  What
exactly are the requirements you need to fulfill with this?  Is is
necessary for all subsequent calls to reference the data? If so then
there maybe a more efficient(& much simpler) way of doing this. 


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx] On
Behalf Of Dan
Sent: Tuesday, January 31, 2006 2:42 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Passing a pointer-based array as a parameter

On 1/31/06, DeLong, Eric <EDeLong@xxxxxxxxxxxxxxx> wrote:
>
> Wait, I'm confused....  Why would you need to load this structure for
all
> users?  Each job (ie, interactive user) is seperate from each other
job.
> The fact that they're invoking the procedure from a common service
program
> has no bearing.  Each interactive session (job) initializes this array
> independently, so you'd only ever need to load this for the specific
> user....


Well, no, I think.  Each interactive application needs to have its own
area.  I need to account for nested calls.  IOW,
PgmA calls
  PgmB calls
    PgmC calls
      PgmD calls
        PgmE etc.
All 5 interactive programs, in the same job, would have to have their
own
structure.

But I am leaning towards Scott's latest suggestion, which I believe will
simplify things *greatly*.

- Dan

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.