Target Environment and Construction Paths › How to Set the Target Environment › Environment Parameters List › Dynamic Linking Options (for z/OS operating systems only)

Dynamic Linking Options (for z/OS operating systems only)

The Dynamically Link packaging option is available for applications built for the z/OS execution environments. The Dynamically Link packaging property of each individual Procedure steps, Screens and Action Blocks (including EABs) can be set to Default, Yes, No, or Compatibility. When set to Default, the actual value is derived from the value entered for the Dynamic Link Default option of the specific component.

For a business system the following values can be specified:

• Yes-indicates the component is resolved as the target of a dynamic program call and as such is considered to be dynamic linked at runtime. The component is generated and built so they reside in their own separately loadable executables. These applications are built as DLLs.
• No-indicates that the component will be statically linked into the application.
• Compatibility-indicates that the component will be dynamically called at runtime and will reside in a non-DLL module. The Compatibility option uses specific CA Gen runtime to enable DLLs to issue a dynamic program call to non-DLL load modules. This requires that the module issuing the dynamic program call be regenerated and reinstalled. CA Gen allows modules marked for Compatibility to be rebuilt in such a way that they are able to use CA Gen runtime DLLs. This requires that the modules marked for Compatibility be reinstalled and, if necessary, regenerated as specified in z/OS Application Migration section in the Release Notes.

More information:

Packaging

Packaging Process

Types of Packaging

Prerequisites

How to Package

Object Relationships

Create Load Module or Batch Job

Creating a Load Module

Add Objects for Packaging

Creating a Batch Job

Add Components for Batch Packaging

Modify Existing Load Module or Batch Job

Modifying an Existing Load Module

Add a Procedure Step to an Existing Load Module

Delete a Procedure Step in an Existing Load Module

Modifying an Existing Batch Job

Add a Procedure Step to an Existing Batch Job

Delete a Batch Job or Batch Job Step

Detail Component Objects

Member Names

Source, Screen and Load Module Naming Rules

MFS Source Naming Rules

Transaction Codes

Clear Screen Transaction Codes

Dialog Flow Transaction Codes

Transaction Code Naming Rules

Complete Option

Default File (Member) Names

Detailing Load Modules

Detailing Batch Jobs

Load Module Size

z/OS Dynamic Linking

Features of Dynamic Link

Considerations for Using the Dynamic Linking Option

Online Packaging

Selecting the Business System

Defining Load Modules

Name the Load Module

Add Procedure Steps

Defining Source Names

Assigning Transaction Codes

Batch Packaging

Selecting the Business System

Defining Batch Jobs

Name the Batch Job

Add Procedure

Defining Job Step Properties

Window Packaging

Selecting the Business System

Defining Load Modules

Name the Load Module

Add Procedure Steps

Defining Source Names

Assigning Transaction Codes

Cooperative Packaging

Selecting the Business System

Defining Load Modules

Name the Load Module

Add Procedure Steps

Defining Source Names

Assigning Transaction Codes

Specify Environment Parameters

Results of Packaging