Ok, now I understand. I have compiled using the CBCC PROC adding LP64 to the
compiler options and binding with the CBCQB PROC but I still get these binder
errors:
IEW2322I 1220 9253 INCLUDE '/SHARED/usr/lpp/IBM/zoau/v1r3/lib/zoautil.x'
IEW2456E 9207 SYMBOL term__FP17zoautil_vector4_s UNRESOLVED. MEMBER COULD NOT
BE INCLUDED FROM THE DESIGNATED CALL
LIBRARY.
IEW2456E 9207 SYMBOL free_response__FP15zoau_response_s UNRESOLVED. MEMBER
COULD NOT BE INCLUDED FROM THE DESIGNATED
CALL LIBRARY.
IEW2456E 9207 SYMBOL init__FUi UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM
THE DESIGNATED CALL LIBRARY.
IEW2456E 9207 SYMBOL version__Fv UNRESOLVED. MEMBER COULD NOT BE INCLUDED FROM
THE DESIGNATED CALL LIBRARY.
It was suggested to me elsewhere that the ZOAU version we have currently is old
(v1.3.2.1) since v1.3.6 is the current one. I will see if we can upgrade and
test again.
Thanks for the clarification about LIBPATH.
Peter
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of D
Gaebler
Sent: Wednesday, August 20, 2025 11:31 AM
To: [email protected]
Subject: Re: Binding C++ programs that use zoautil functions
The LIBPATH is just required for execution of the module you are trying to
bind. The .x file needs to be fully qualified with the INCLUDE binder statement.
The .x file contains the exports when compiling the DLL. You always bind to the
.x file not to the .so (DLL).
The .x file contains the IMPORT statements which functions are exported by the
DLL with the same name, so the binder knows what functions can be resolved by
calls to the DLL.
If you look inside the .x file, you will see the IMPORT CODE statements.
Hope that 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
