Problem O2/2 warp 32bit cobol calling 16bit c 
Author Message
 Problem O2/2 warp 32bit cobol calling 16bit c

I am having problems calling 16bit dll from 32bit cobol under os/2 warp.
It seems the thunking from 32bit to 16bit is not working.
The calling convention used is 35.
.
SPECIAL-NAMES.
           call-convention 35 is thunked.
.
WORKING-STORAGE SECTION.        
        01  connID            pic  9(9) comp-5.
        77  ws-error-code  pic  9(9)  comp-5.
.
PROCEDURE DIVISION.
.  
        call thunked "NWGetDefaultConnectionID" using
               by reference  connID
           returning         ws-error-code
        end-call

Links compiles and links o.k.

Links with.

link386 OF98/pmtype:pm+cobintfn+panels2+MFFH+XFHNAME+CBLLDS,OF98.DLL,,mfrts32+mfcmlib+os2386+SQL17O32+OFDBG+DSRUN+nwcalls,OF98.DEF/NOD/NOE/NOI;




Tue, 27 Jul 1999 03:00:00 GMT  
 Problem O2/2 warp 32bit cobol calling 16bit c

Quote:

> I am having problems calling 16bit dll from 32bit cobol under os/2 warp.
> It seems the thunking from 32bit to 16bit is not working.

What do you mean when you say, "not working"?

Del.



Fri, 30 Jul 1999 03:00:00 GMT  
 
 [ 2 post ] 

 Relevant Pages 

1. Windows 16bit C Calling 32Bit ASM

2. Problem calling COBOL DLL from VB4-16bit

3. Problem: Changing from 16bit to 32bit

4. Help request: Realia 16bit to 32bit conversion problem

5. Calling COBOL DLL from VB4-16bit

6. How to Calling COBOL DLL from VB4-16bit

7. MF cobol 16bit call under VisOc

8. Going from 16bit to 32bit

9. 16bit to 32bit conversion

10. 32bit runtime errors - 16bit runs fim

11. 32bit vs 16bit

 

 
Powered by phpBB® Forum Software