Denis, does that requirement apply to a JCL BIND operation? The zoautil.so file is in the same Unix directory as the zoautil.x file used to do the IMPORT’s, can’t the binder find it there?
If LIBPATH is in fact required, how could a JCL BIND set that variable for the binder to use? I will recompile with LP64 using the 64-bit compile PROC EDCQCB and see what happens. Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of D Gaebler Sent: Wednesday, August 20, 2025 1:03 AM To: [email protected] Subject: Re: Binding C++ programs that use zoautil functions Hi Peter, one more idea, I recently discovered during tests, that if the AMODE does not match, the binder include does not happen and there is no suitable error message. zoautil.so is 64bit. So if the C is LP32, the link does not work. If you need to call the zoautil functions from 31bit, then you need to look into 31/64bit interoperability. Either by LE runtime options or CEL4RO64. One addition to the previous INCLUDE .x file, it requires LIBPATH being set at runtime to find the .so file. Hope it helps, Denis. -- 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 [email protected] with the message: INFO IBM-MAIN
