I have a couple of questions about REXX DLL's.

I have a DLL that _almost_ works.  As long as you only have _one_ session
running with it at a time.

The problem _seems_ to be something about the global variables I have, or
at least that's all I can figure out.  The only reason I doubt this is that
a DLL loaded by seperate processes should have its own global data space...
shouldn't it?

If so, then nothing should conflict between the two processes (instances of
the command interpreter, whether I use 4OS/2 2.52A or the Warp CMD.EXE).

If not, would I get a Sys3175 error when using a pointer that was created
in the first process ... in a second one?  Or how about a semaphore created
in the first process?

(I want to use a semaphore around global access, obviously.)

The DLL, as I said, seems to work in its own process, with no one else
running it.  As soon as I try to use a function in the second process which
uses the globals (i.e., the load/drop functions work fine in the second
process), the second process quits - the first one continues to work fine.

This is just plain annoying now.  

Any help would be very much appreciated.  (Code _can_ be posted, but please
specify what you want posted - there's over 36k of source here...)


--- Maximus/2 3.01