On Fri, 11 Sep 2015 11:08:38 -0400, Kurt Quackenbush wrote: >It is link edit steps in >JCLIN that tells SMP/E how to put the MODs together to create these load >modules.
When you code your JCLIN, one thing to remember is that it is coded as though the target element is created from the DLIB libraries. In most cases, SMP/E doesn't actually build the elements that way, but that's how you tell it what needs to be done. Once you understand that, the JCLIN is much easier to grasp. Also, the JCLIN can be simplified from actual JCL that would be required to link the load modules or program objects. The data set names provided don't have to actually exist. SMP/E uses only the low-level qualifier to determine the DDNAME (and DDDEF) to use. CALLLIBS processing can be confusing at first, too. Beware of SYSLIB. Both the assembler and the binder use SYSLIB, and they use it for very different purposes. If your product includes a SYSLIB DDDEF, it will be used for macro libraries, not for Auto-call libraries for the binder. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
