If you're using the IEWBIND macros, note the documentation here:
https://www.ibm.com/docs/en/zos/3.2.0?topic=api-loading-binder
In particular the last sentence of that first paragraph -- The binder keeps the
EP of the IEWBIND program in the DIALOG, so it's only loaded once.
After CREATEWorkmod, the DIALOG is found from the WORKMOD, and only the WORKMOD
is passed to subsequent calls like IEWBIND GETN.
So possibly you invoked the IEWBIND macro but the WORKMOD or DIALOG got trashed.
Regarding TSO TEST, I took a simple program which I knew could not be handled
by the binder LOADW. With the bound progam object it worked fine.
When I tried then passing the object module (disregarding that I knew I hadn't
set it up to resolve symbols etc) I got this output:
test 'barryl.binder.obj(hw)' object
IEW2278I B352 INVOCATION PARAMETERS -
TERM,NOPRINT,NCAL,NOMAP,NORES,LET,NAME=TEMPNAME
IEW2454W 9203 SYMBOL CEEBETBL UNRESOLVED. NO AUTOCALL (NCAL) SPECIFIED.
IEW2454W 9203 SYMBOL CEEROOTA UNRESOLVED. NO AUTOCALL (NCAL) SPECIFIED.
IEW2454W 9203 SYMBOL CEESG003 UNRESOLVED. NO AUTOCALL (NCAL) SPECIFIED.
IEW2454W 9203 SYMBOL printf UNRESOLVED. NO AUTOCALL (NCAL) SPECIFIED.
IEW2454W 9203 SYMBOL EDCINPL UNRESOLVED. NO AUTOCALL (NCAL) SPECIFIED.
IEW2678S 3980 MODULE CONTAINS DATA CLASSES NOT SUPPORTED BY THE LOAD FUNCTION.
IEW2008I 0F03 PROCESSING COMPLETED. RETURN CODE = 12.
IKJ57002I NO ACTIVE PROGRAM LEFT
READY
From these messages it's appears that TSO TEST of an object module, is first
binding and then loading it using the IEWBIND LOADW function.
I did also find this in the z/OS TSO/E Programming Guide:
https://www.ibm.com/docs/en/zos/3.2.0?topic=testauth-considerations-31-bit-addressing
The 5th bullet says in part that TSO TEST uses the loader when it is given an
object module. I believe it calls HEWLOAD (aka IEWBLODI) to do this.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
