This chapter shows how to process the load module (LM) Implementation Package (IP) to create the Executable Load Modules and Opslibs for z/OS (zLIBs). During processing, the Installation Tool:
The functions associated with processing the load module IP are performed through the Installation Tool menu.
Source code for Load Module components that have their Dynamically Link packaging property set or defaulted to Compatibility is not included in the IP unless the option Process modules marked for Compatibility was also selected.
Selecting the option Process modules marked for Compatibility causes two tokens to be included in the ICM. The two tokens are as follows:
The PCOMPAT token, found in the execunit section of the load module, applies to every component of the load module and causes the components to be compiled twice.
The LINK token is specified for every component that is marked for Compatibility and causes the Implementation Toolset to build the component as a non-DLL load module.
If the load module is defined as a zLIB module (using the toolset), the remote file includes the keyword lmtype=zlib which will cause the modules to be included in a DLL by the same name as the Load Module name. The zLIB (DLL) will be placed in the loadlib associated with the EXEC lib.
The installation process link-edits the dynamic action blocks including z/OS Library modules for batch processing in addition to regular link-edit if Batch Executable library is specified
For z/OS Libraries, the online version of z/OS Library DLL will be populated in the regular Executable Load Modules Library. The batch version of z/OS Library will be saved in the Batch Executable library if specified. DB2 attachment type for batch z/OS Library DLLs will be as specified by the TIRDBATT parameter, defaulting to DSN.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|