On Tuesday, 26 January 2016 18:03:13 UTC, Tom Marchant wrote: > On Tue, 26 Jan 2016 10:48:40 -0600, Bill Woodger wrote: > > >On Tuesday, 26 January 2016 16:22:32 UTC, Warren, Cliff wrote: > >> I use Enterprise PLI V3 and it does require you to compile into a PDSE > > > >The PROC you are using is set up to use the Binder. Other PROCs are set > >up to use the Link-Editor. > > AFAIK, the Binder can do anything that the Linkage Editor can do. In > particular, the Binder is perfectly capable of producing a load module, > which is stored in a PDS, or a program object, stored in a PDSE or Unix file. > > -- > Tom Marchant > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN
Sorry not to be clear that I was paraphrasing the PL/I Programming Guide: "Cataloged procedures IBMZCB and IBMZCBG use features of the program management binder introduced in DFSMS/MVS ® 1.4 in place of the prelinker supplied with Language Environment. These procedures produce a program object in a PDSE. Cataloged procedures IBMZCPL, IBMZCPLG and IBMZCPG use the prelinker supplied with Language Environment and produce a load module in PDS. Use these procedures if you do not want to use a PDSE. ... The IBMZCB cataloged procedure, shown in Figure 11 on page 142, includes two procedure steps: PLI, which is identical to cataloged procedure IBMZC, and BIND, which invokes the Program Management binder (symbolic name IEWBLINK) to bind the object module produced in the first procedure step. ... The IBMZCPL cataloged procedure, shown in Figure 13, includes three procedure steps: PLI, which is identical to cataloged procedure IBMZC; PLKED, which invokes the Language Environment prelinker; and LKED, which invokes the linkage editor (symbolic name IEWL) to link-edit the object module produced in the first procedure step." At the end of the day, it is the JCL which determines where the executable program resides. PL/I can create programs which do not require to be a Program Object. COBOL V5 cannot. Aside 1: Without an "unless we feel like it" clause, I'm not buying a "we won't do that" unless the Board are behind it. Aside 2: Who thought it was a good idea to name a place where one or more Object Programs can turn up a Program Object. That's clear, right? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
