In a message dated 01-10-95, Bill Nelson said to All:

BN>Anybody,
BN>   I have a problem with MicroFocus COBOL since upgrading to Warp, and I
BN>wonder if anyone else has run into this.

BN>   I have built a DLL with about 200 entry points in it using the
BN>MicroFocus COBOL 3.2.20 compiler.  This DLL worked fine under previous
BN>versions of OS/2, but under Warp I get the following behaviour.  The
BN>first program that I start running that accesses the DLL works fine.
BN>However, if I try to invoke a second program that uses the DLL while
BN>the first one is still active, I get a SYS005: access denied message.
BN>This message is being issued before the first line of my code gets
BN>executed.  I suspect it is coming from a MicroFocus startup routine
BN>in the DLL initialization code.

BN>Has anybody else encountered this, or know why Warp would cause the
BN>different behavior?

I haven't run into it.  However, I never include multiple modules into a
single DLL in COBOL.  With this setup I don't have any problems whatsoever.
It also allows for the use of the DLL compiler parm and therefore eases
development for me.  You loose at little bit in terms of responsiveness
when subsequent modules are loaded, however it also ensures that only
the modules invoked are actually loaded.


...Raetus
___
 * MR/2 2.1 #179 * Paul Harvey fans always have a good day but do they see
the light ?

--- Maximus/2 2.02