Paul, Yes, that is all I can find as well, but if only ++MODs can be used to cause a link, what is the ++PROGRAM used for. The reference manual states that it is used to deliver a linked edited load module, but it says nothing about what the load module would be used for.
So, assuming for the moment that ONLY ++MODs can be used to deliver object programs for use by the linkage editor, how would one accomplish the following: SMP/E environment #1: Deliver, assemble and link the 8 constituent modules creating 8 standalone load modules. Capture the output of the assembler during the assembly process in order to deliver the object decks to SMP/E environment #2. SMP/E environment #2: Deliver the object decks from SMP/E environment #1. Link the 8 object decks along with a stub to create a load module usable in the environment controlled by SMP/E #2. The two environments cannot be combined. I have tried changing my assembler options to state OBECT versus NOOBJECT, and supplying a DD statement for SYSLIN and that works, on a module by module basis. However, I also have UCLIN MAC GENASM statements for each of the modules so that if any of the macros and DSECTs used by the module are changed, the source will be reassembled and the modules relinked. Delivering a macro that is used by 2 or more of the modules causes them to be reassembled and that's where the problem lies. In the deliver process of the new macro, if more than one module gets reassembled, the output decks overwrite each other to that only the last module assembled is saved. If I can figure out how to cause SMP/E to keep the output of each module assembly when a new macro is delivered, then I'm home free as I can deliver an object deck via ++MOD to the second environment rather than load modules via ++PROGRAMs. Ideas? Thoughts? Thanks, Chuck Charles (Chuck) Hardee Senior Systems Engineer/Database Administration CCG Information Technology Thermo Fisher Scientific 300 Industry Drive | Pittsburgh, PA 15275 Phone +1 (724) 517-2633 | Mobile +1 (412) 877-2809 | FAX: +1 (412) 490-9230 [email protected] | www.thermofisher.com WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. If you are not the intended recipient, please inform the sender and delete all copies. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Tuesday, August 12, 2014 4:03 PM To: [email protected] Subject: Re: Another SMP/E opportunity On Tue, 12 Aug 2014 12:04:30 -0700, Hardee, Chuck wrote: >Hello Fellow Mainframers! > >I have another SMP/E opportunity for you to help on. > >I have 8 load modules that have been assembled and linked standalone outside >of SMP/E. >I have delivered those 8 load modules to my target zone via ++PROGRAM >statements, each in their own usermod and each in their own "maintaining" job >stream. Each of the were delivered to SMP/E successfully ... > >I am trying to combing these 8 modules into a load module in a final, 9th >usermod. >The 9th usermod has a small program being delivered in order to "force" the >assembly and link of the final module. >The program in this usermod is delivered via a ++SRC statement and assembled >clean and triggers the link. > ... > >Any thoughts about what might be incorrect or missing would be greatly >appreciated. > Looking at: http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.gim1000/bldlmod.htm#bldlmod Building load modules SMP/E for z/OS Commands SA23-2275-00 ... I see discussion only of building load modules from MOD elements, not of building from PROGRAM elements. I suspect SMP/E doesn't support what you're attempting. (I was frustrated enough when I learned that a MODule can not be INCLUDEd by citing the name of its TALIAS or DALIAS in an INCLUDE statement in JCLIN.) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
