Is there an option that tells the binder to INCLUDE a module only if it
resolves at least one unresolved symbol?
My specific case is the CICS/MQ stub library. 99% of our CICS programs do not
use MQ, yet currently I have our CICS compile proc do an INCLUDE of this module
in order to satisfy the one case where it is needed. Since CICS and MQ do not
provide aliases of the actually entry points, AUTOCALL does not find the module
(CSQCSTUB). So it seems to me that something that would be useful would be a
happy middle between "always include this member" and what AUTOCALL does.
The "obvious" other option is to do the INCLUDE of this module only for this
program. This may seem strange, but our inhouse written change control process
does not currently allow for this. Because almost every other symbol is
resolved simply by AUTOCALL; and for the one that doesn't (the DFHELII stub) we
simply always do an INCLUDE for that if the compile is for a CICS program.
Obviously we can enhance our system to allow us to specify for each program any
additional modules it requires. But this seems such an "obvious" feature to me
that I wonder why its not supplied (if that is the case).
Am I just missing what I am looking for?
If I'm not missing it, would you vote for an RFE for such a feature?
Frank
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
