Link-editing a GDDM application program

GDDM V3R2 Base Application Programming Guide

Link-editing a GDDM application program

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

Examples of the JCL that can be used to compile and link-edit application programs written in PL/I or COBOL are listed in "Example: JCL to compile and link PL/I GDDM applications under IMS" in topic D.14 and "Example: JCL to compile and link COBOL GDDM applications under IMS" in topic D.15.

Unless an application program uses dynamic load facilities to access GDDM through the system programmer interface (see below), a GDDM application program must be link-edited with the appropriate GDDM interface module as well as the DL/I interface module. The interface module used depends on the type of GDDM interface used and the language of the application program, or, to be precise, of the program specification block (PSB) for the transaction.

The module to be used may be explicitly controlled by linkage editor control statements, or one of the alternative versions of the initialization entry point can be used. The latter causes the correct GDDM interface modules to be loaded by the automatic library call capability of the linkage editor.

There are four alternative initialization calls for GDDM in an IMS environment. They allow for a choice of nonreentrant and reentrant interface and nonPL/I and PL/I PSBs. The names of the initialization calls are as follows:

Interface Non-PL/I PSB PL/I PSB

Nonreentrant FSINNI FSINNPI Reentrant FSINRI FSINRPI

If direct control of the link-edit process is chosen, the initialization call should be coded using the FSINIT (or SPINIT) entry point, and the following modules explicitly included by the link-edit process:

Interface Non-PL/I PSB PL/I PSB

Nonreentrant ADMASNI ADMASNJ Reentrant ADMASRI ADMASRJ System Programmer ADMASPI ADMASPJ

Notices | Terms of use | Support | Contact z/OS