🚀 go-pugleaf

In article <3ikp6i$pmg@status.gen.nz> acullen@iconz.co.nz (A J Cullen) writes:
>
>The SOM compiler insists on generating an output file with a .C
>prefix (builds a C file for input to C compiler). I'd like to input
>this file to the SQLPREP DB2/2 precompiler, but it wants to output
>filename.C as well. 

Hello... I'm not familiar with the SOM side, but after the SOM compiler
generates a .C file, could this be renamed to .SQC and then put through the
DB2/2 SQLPREP?

Thanks... Bo Taramina... DB2 Client/Server Support

In <3ikp6i$pmg@status.gen.nz>, acullen@iconz.co.nz (A J Cullen) writes:
>Hello,
>  I would like to use embedded SQL in a SOM environment.
>I've read the DB2/2 docs dealing with SQLPREP and the SOM compiler
>docs and I can't see a solution for the following problem:
>
>The SOM compiler insists on generating an output file with a .C
>prefix (builds a C file for input to C compiler). I'd like to input
>this file to the SQLPREP DB2/2 precompiler, but it wants to output
>filename.C as well. 
>Anyone successfully using DB2 precompiler with SOM-II under OS/2?
>Thanks for any help or workarounds.

Andrew,
I face the same problem. I havent already started with implementing a solution
but I plan to include the function in IDL the following way:

	#ifndef CPP_GEN
		int	sql_func();
           #endif

If I generate the CPP (or C) file I will explicit define the CPP_GEN label which
prevents the function stub to be generated. The header files for usage and
implementation will define the method.
All I have now to do is write the stub for the method into the .SQC file, compile
and link it with the method file.
I will start work on that in a few days and will then see how it works. I think
however it could work that way.
Regards, Klaus