Effect of DELETE on Load Modules
DELETE deletes the named load module from the load area of the dictionary. The subschema compiler also automatically erases the PROG-051 dictionary record occurrence associated with the load module, except if the record:
Effect of DISPLAY on Load Modules
DISPLAY displays online output at the terminal and lists batch output in the compiler's activity listing. The output always appears as comments regardless of the default option in effect.
Effect of PUNCH on Load Modules
PUNCH writes output to the system punch file or to a module in the dictionary. All punched output is also listed in a subschema compiler's activity listing.
The subschema compiler produces an object (relocatable) deck accompanied by ADD LOAD MODULE syntax from the named load module. The object deck can subsequently be link edited and placed in a load library. You can also use this option to move a load module from one dictionary to another.
Note: When you punch a load module from the dictionary load area (DDLDCLOD area) into an object module, the DDDL compiler omits the RMODE/AMODE attributes because the RMODE/AMODE clause is not acceptable to the linkage editor. If you are punching the load module to add it to a different dictionary, then you must edit the punched syntax to include the RMODE/AMODE clause.
Systems with 24-bit Addressing Load Modules Below the Line
For DC/UCF systems running in 24-bit mode, modules are loaded below the 16-megabyte lines regardless of the RMODE specification.
Residency Mode Determines Which Program Pool to Use
For DC/UCF systems running in 31-bit mode, modules with an RMODE of ANY are loaded into XA program pools (above the 16-megabyte line); modules with an RMODE of 24 are loaded into non-XA program pools (below the 16-megabyte line).
|
Copyright © 2014 CA.
All rights reserved.
|
|