Content deleted Content added
Stevebroshar (talk | contribs) Co-locate Unix implementation info |
Guy Harris (talk | contribs) →{{anchor|Consolidator}}Linkage editor: Rephrase to make it clear that there's a hardware range (S/360 through IBM Z) and an OS range (OS/360 through z/OS). |
||
Line 53:
== {{anchor|Consolidator}}Linkage editor ==
In IBM [[System/360]] through [[IBM Z]] [[Mainframe computer|mainframe]]
One advantage of this is that it allows a program to be maintained without having to keep all of the intermediate object files, or without having to re-compile program sections that haven't changed. It also permits program updates to be distributed in the form of small files (originally [[card deck (computing)|card deck]]s), containing only the object module to be replaced. In such systems, object code is in the form and format of 80-byte punched-card images, so that updates can be introduced into a system using that medium. In later releases of OS/360 and in subsequent systems, load-modules contain additional data about versions of components modules, to create a traceable record of updates. It also allows one to add, change, or remove an [[overlay (programming)|overlay]] structure from an already linked load module.
|