Using DLL in a call from rexx to C

rameshvs · New User Joined: 10 Aug 2007 Posts: 30 Location: atlanta

Hi All,

I have a question for which am sure I am missing something. I have a C++ module which I am calling from REXX using LINKMVS and passing parameters. It works fine if I dont inlcude any external functions from C++. I mean if I include an external function from a DLL (of c programs) the program is not able to identify and dumping at run time. On the other hand if I execute a program directly from a JOB it works very well. Please suggest me as to what could be the missing link. I mean is it the way I am binding the DLL or something else wrong.

I tried the above C++ routine with TSO CALL command also but am having the same issue. So I think TSO is not able to identify the DLL.

Can you please help me out with this.

Thanks
Ramesh.

dick scherrer · Posted: Thu Oct 04, 2007 4:56 am

Hello,

Is this

rameshvs · New User Joined: 10 Aug 2007 Posts: 30 Location: atlanta

Yes Dick,

I am getting the program not found abend. But I am not able to solve by concatenating to the ISPLLIB.
Here is the detail.

I have REXX, R1 from which I am calling C++ program C1 using LINKMVS. To call C1 through LINKMVS I have to concatenate the load library(dataset LOAD) that has C1 load to ISPLLIB using LIBDEF. So I am able to do all these and am calling.

Now in the C1 program there is a reference to an external function F1 that is bound into DLL D1. The system abend is specifying that the program is not able to fing DLL D1 though it is present in the same LOAD dataset.

So system is able to find the load module for C1 from LOAD dataset why are we havivng issue with the DLL.

Please let me know if I am not clear, I will try and give more detailed explanation.

Thanks
Ramesh.

dick scherrer · Posted: Thu Oct 04, 2007 7:59 am

Hello Ramesh,

I believe you are clear. I also believe i'm "in over my head"

Is is possible that another dd using the same library needs to be allocated in the tso session?

Is the dataset with the dll part of the joblib/steplib in the batch job?

Is there another dd in the batch job that names this library?

rameshvs · New User Joined: 10 Aug 2007 Posts: 30 Location: atlanta

Yes Dick,

May be some other dataset but how should it be allocated and what should it be allocated to.

Yeah with the JCL, actually since everything is in the same load library which is part of the STEPLIB there is not problem.

I dont have a separate library in batch JCL to find the DDL's.

I am not getting a clue on how to get this resolved.

Thanks
Ramesh

dick scherrer · Posted: Thu Oct 04, 2007 11:35 am

Hi Ramesh,

I don't know if this will help - it is a COBOL reference for OO applications on the mainframe.

http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp?topic=/com.ibm.entcobol4.doc/tpooo08.htm

Maybe there will be something that can help.

I'll keep looking for something more useful.

SPACHFR · New User Joined: 07 Mar 2006 Posts: 5 Location: France

Hi,

Did you link your DLL and C programme when you have created the C LOAD ?

I am worked on a same structure program.

C source
C DLL (externals functions)
Rexx with LINKMVS to call the C pgm

compile C pgm to have a OBJ
Pre Link and LInk the C OBJ with the DLL

add STEPLIB in your JLC that use the rexx to provide where are your DLL and C LOAD.

(sorry for my English.....)

rameshvs · New User Joined: 10 Aug 2007 Posts: 30 Location: atlanta

Thanks for the responses.

I got it fixed in a way may not be ideal though but it seems to work. Here is what I have done insted of dynamically binding the DLL I have bound it Statis by including the objects specifically in the include statement.

This I have to do because I am not running my REXX from a JCL but running it in the foreground.

Once again thanks for the responses.
Ramesh.

dick scherrer · Posted: Wed Oct 17, 2007 7:00 am

Hello,

Thank you for letting us know you have it working.

If you talk with your system support people, they may be able to modify your signon procedure to include the needed dataset(s) at the end of your library allocation.