REXX calling MF Cobol DLLs problem 
Author Message
 REXX calling MF Cobol DLLs problem

Hello from Melbourne Australia,

We are having trouble calling Microfocus Cobol 3.2 DLLs
from REXX under OS/2. There are two major related

(1) -- Unless the Cobol DLLs are statically linked with
LCOBOL (instead of the dynamic COBLIB), we get SYS3175
errors as soon as REXX calls our DLLs. The Cobol procedure
division is never reached, the error occurs very early.

(2) -- If a REXX program directly or indirectly calls a
Cobol DLL that uses any of the function routines stored
in COBINTFN (date routines etc), then a SYS3175 error will

We can get around the problem by statically linking the
appropriate DLLs with LCOBOL and avoiding call to COBINTFN
routines, but it's rather tedious identifying all of these
modules and having separate link steps for them.

Rather than go into details at the moment, I'm fishing first
to see if anyone can help out with this problem, then I can
supply any extra information you need.

Greg Keogh

Mon, 21 Dec 1998 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. Calling MF COBOL-DLL from VB

2. Calling C++ DLL from MF COBOL

3. Calling Win32 DLL Functions from MF COBOL

4. MF-COBOL and DLL's: Call shows strange errors

5. calling a MF COBOL .dll (ver 3.2.50) from VB5

6. 32-bit MF COBOL DLL calling from VB4

7. How to compile and link to C-DLL out of COBOL-DLL (MF)

8. problem with mf cobol calling win32 api

9. tso rexx calls cobol calls cobol -> splat

10. calling Non-Rexx DLLs from REXX with RXU

11. VB 6 call to Fujitsu COBOL DLL problem

12. Problem calling COBOL DLL from VB4-16bit


Powered by phpBB® Forum Software