On Sun, 17 Dec 2023 11:01:23 -0600, Paul Gilmartin <[email protected]> wrote:
>The CSECT() option of the ++MOD MCS should clarify this. But it's optional, >and I don't know that it's verified, even if present. CSECT defaults to ++MOD name which generates BINDER REPLACE statements. Specifying additional CSECT names allows one ++MOD to contain multiple CSECTs. I suspect that this is important for packaging LE programs. >Fiendish case: a CSECT in one ++MOD is identical to the name of a different >++MOD. Having the same CSECT name in different ++MODs is not a problem. A problem only occurs if both MODs are included into the same LMOD. >Why are TALIAS and DALIAS mutually exclusive? ++MOD have a dist library DDN but do not have a target library DDN. DALIAS has an obvious implementation. TALIAS on the other hand is used for something that is not obvious because the MOD does not physically exist as a member in a target library. What and where are you going to attach an alias name. I suspect that TALIAS has a meaning in both target and dist that conflicts with DALIAS. >SMP/E doesn't understand its own alias names. Once, as an experiment I created >an alias. In standalone JCL SYSLIN "INCLUDE alias" worked. Failed in SMP/E. >Went to SR. Got WAD. An alias is not a SMP/e object so JCLiN cannot process an alias. All SMP/e objects are unique but the same alias can be used for many objects. SMP/e cannot identify the SMP/e object which affected. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
