Re: Global variable across module and language boundaries?

[Bill Meecham <BMeecham@xxxxxxxxxxxxxxxxxxxx>]

A dataQueue, keyed or not, would be a better way to handle.

----- Original Message ----- 
From: James H H  <mailto:jamesl@xxxxxxxxxxx> Lampert 
To: Midrange Systems Technical  <mailto:midrange-l@xxxxxxxxxxxx> Discussion 
Sent: Monday, March 06, 2006 7:08 PM
Subject: Re: Global variable across module and language boundaries?


"Gary Monnier" wrote: 
> Easy as pie.  Use a user space.   Just obtain a pointer 
> to the space. When you change the space in one program it 
> is also changed in the other. 

That hardly qualifies as "easy as pie," and in the 
situation at hand (i.e., one module telling another 
whether or not it's already copied a work-file into QTEMP) 
it amounts to using a bazooka to swat a fly. 

And I said IN AN ILE PROGRAM, ACROSS MODULE AND LANGUAGE 
BOUNDARIES, not across PROGRAM boundaries or across JOB 
boundaries. Something like a "common block" in Fortran. Or 
declaring a Java variable as "public static" (or even just 
"public"). 

Sorry if I seem a bit irritable.