>> >> In the general case (amiglib perhaps an exception) to expect a DLIB (HLQ.Axxxxxx) to provide valid executables. >> >Not in thee general case. A DLIB may contain objects which need >to be linked with library subroutines to be valid executables.
At least for these SMP/E-maintained elements of z/OS, if anything it is the exception that the DLIBs contain things that are OK to execute. Distlibs ALINKLIB, ALPALIB, AMIGLIB which as part of the install are copied as-is to SYS1.LINKLIB/LPALIB/MIGLIB. Products install from the distlibs into production libraries (often under some customer-controlled naming scheme). For those FMIDs, the distlibs contain the "single csect loadmod" versions of the assembler obj (often it would have unresolved external references). It is not typically "library subroutines" that those are to be linked with but rather other members of the distlibs (and/or the resulting load module itself, such as IEANUC01) Peter Relson z/OS Core Technology Design
