Yes, the DLL compiler option was the key, as Miklos told me.
Yes, the LIBPATH is required to be set at runtime. The IBM-supplied JCL sample
provides this in the PARM to the executable sample program:
//GOWAPCCC EXEC PGM=*.IEWAPCCC.BIND.SYSLMOD,
// PARM='ENVAR("LIBPATH=/usr/lib"),MSGFILE(MYSTDERR)//bin/sh'
Peter
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Don Poitras
> Sent: Wednesday, July 13, 2011 11:19 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: HOWTO question: Linking non-XPLINK C with a shared object
> (.so) library
>
> Peter,
> Did you supply the DLL compiler option? Usually, it's better to just
> include the DLL side file (/usr/lib/iewbndd.x) rather than trying to
> write all these yourself. Remember at runtime, you must set LIBPATH to
> be able to find the DLL.
--
This message and any attachments are intended only for the use of the addressee
and may contain information that is privileged and confidential. If the reader
of the message is not the intended recipient or an authorized representative of
the intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
