"IBM Mainframe Assembler List" <[email protected]> wrote on 
10/19/2023 09:49:31 AM:
> At my company, the standard going back at least 37 years has been to
> compile or assemble, then the job immediately NCAL links the object 
> deck into an "object module" (not to be confused with PDSE "program 
> object"). The object deck is discarded, the object module is saved.
> 
> I'm not sure *why* we do this, except that it makes it easier to 
> link the object into composite load modules.
> 
> Is this common? Or do other groups save the object deck?


        Now I'm talking z/VSE-land here, but...  Every shop I have been in 
catalogs the SYSLNK object deck as an "object module" (library member type 
OBJ) without doing any linkage editor step.  Anytime we run the linkage 
editor it is always to create a load module (library member type PHASE).

        When we want to make composite load modules we can string linkage 
editor INCLUDE statements of OBJ members, via SYSLNK, to feed into the 
linkage editor.  This step can also include a SYSLNK object deck at the 
same time and if there is a single PHASE statement (in SYSLNK) then a 
single load module is the result.  But multiple PHASE statements can be 
interspersed in SYSLNK to create multiple load modules in a single 
execution of the linkage editor.

        I did work in a couple of MVS/SP shops but I was not as familiar 
with the compile processes there and always created only load modules.

Sincerely,

Dave Clark
-- 
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331




*********************************************************************************************
This email message and any attachments is for use only by the named 
addressee(s) and may contain confidential, privileged and/or proprietary 
information. If you have received this message in error, please 
immediately notify the sender and delete and destroy the message and all 
copies. All unauthorized direct or indirect use or disclosure of this 
message is strictly prohibited. No right to confidentiality or privilege 
is waived or lost by any error in transmission. 
*********************************************************************************************

Reply via email to