Linking Application Programs › Option 1: Manual Linkage

Option 1: Manual Linkage

Code control statements to the IBM Linkage Editor to include the DBCSVPR routine last in the load module. These examples have been changed to DBCSRPR instead of DBCSVPR. This allows the application options to control the LINK EDIT without having to supply override parameters such as AMODE/RMODE to the LINK EDIT.

Here is an example for z/OS environments:

//LKED    EXEC PGM=IEWL,
   //. . .
   //. . .
   //CICSLIB DD DSN=users.CTS,SDFHLOAD,DISP=SHR
   //OBJLIB  DD DSN=users.OBJECT.LIB,DISP=SHR
   //DBCLLD  DD DSN=userhlq.CAB1LOAD,DISP=SHR
   //. . .
   //SYSIN   DD *
     INCLUDE CICSLIB(DFHEILxx)
     INCLUDE OBJLIB(pgmname)
     INCLUDE DBCLLD(DBCSRPR)
     NAME pgmname
   /*

Here is an example for z/VSE environments:

// DLBL   DBCLLD,'DBC14LIBRARY'
// EXTENT ,VSE300
// LIBDEF OBJ,SEARCH=(DBCLLD.DBC14,USER.OBJECT,CICSTS.TS11)
// LIBDEF  PHASE,CATALOG=USER.PHASE
// OPTION CATAL
 PHASE pgmname,*
 INCLUDE DFHELxx
 INCLUDE pgmname
 INCLUDE DBCSVPR
// EXEC LNKEDT
/*

For both z/OS and z/VSE, DDNAME DBCLLD references the CA Datacom CICS Services product load library defined during installation.

For z/OS and z/VSE, the DFHEILxx module represents the CICS command-level interface module that must be included from your appropriate CICS library. For more information about these module names, see the note in Option 2: Automatic Linkage.