GDDM-PGF V2R1.3 Programming Guide and Reference
GDDM-PGF V2R1.3 Programming Guide and Reference
Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF |
BOOK
Link-editing the programs GDDM-PGF V2R1.3 Programming Guide and Reference SC33-0333-01 |
|
Except under VM/CMS the object code from the compilation must be link-edited with a GDDM interface routine appropriate to the subsystem and to the interface used (reentrant or nonreentrant). Under OS/VS, the link-edit SYSLIBs should include the GDDM load library. The correct interface module is selected by an INCLUDE control statement specifying the appropriate member, as follows: Another way is to use the automatic-library-call facility. For this, the source programs must be changed to replace the references to FSINIT with the appropriate member, as follows: Note that for PL/I the standard declarations do not include the other forms of FSINIT. They must, therefore, always be explicitly declared thus:
DCL FSINNC ENTRY EXTERNAL OPTIONS (ASM INTER);
On DOS/VS, GDDM should be included from the relocatable libraries during
link-editing. The correct interface modules should be selected as
follows:
and should be included as described under the information on link-editing for CICS/DOS/VS in the GDDM Base Application Programming Guide. The automatic inclusion of the interface modules by source-program modification is not available for DOS/VS. In VM/CMS, there is no link-editing. However, the CMS GLOBAL TXTLIB command must be executed (as described in the GDDM Base Application Programming Guide under the information on running a program under CMS) to identify TXTLIBs from which GDDM/PGF routines can be loaded. The TXTLIBs required depend on the sample program attributes and the presence of GDDM/PGF in a discontiguous shared segment (DCSS), as follows: |
 Copyright IBM Corporation 1990, 2012 |
