I can tell one thing to NOT do. I tried something similar for one particular job that involved lots of modules, and got into trouble because I saved a pointer to the values in another module, instead of having it return the values each time I needed them. That worked just fine in test, but failed intermittently in production because apparently the variables in modules that are not in the invocation stack can get moved around by the operating system, and external references to them don't get updated.

At 12:00 5/22/2004, Joe Pluta wrote:
Typically, I have a separately bound program I call that keeps the job
level values, and I bind in a module to keep static variables at the
program level.  So, I have a program that returns J_SESSION, and both
Program A and Program B call it through an EXTPGM call.  However, each
has its own P_CALLLEVEL value, which it gets through an EXTPROC call to
a bound module.

In the world of service programs, can I emulate this?

Pete Hall pbhall@xxxxxxxxxxxxx http://www.pbhall.us/


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.