gtpo1mh7Operations

Link-Edit Procedures

The following statements are required for the link edit:

//LKED      EXEC   PGM=IEWLF440,REGION=88K,PARM='LET,LIST,XREF,DCBS,
//                 SIZE=(88K,6K),NCAL,OVLY'
//SYSPRINT DD      SYSOUT=A,DCB=(RECFM=FBM,LRECL=121,BLKSIZE=605)
//SYSLMOD  DD      DSN=ACP.LINK.RELvv,DISP=OLD,DCB=BLKSIZE=1200
//OBJLIB   DD      DSN=ACP.OBJ.RELvv,DISP=SHR
//SYSUT1   DD      DSN=&&SYSUT1,UNIT=SYSDA,SPACE=(7294,(100,100))
//SYSLIN   DD      *
           ENTRY   PPCP
          INCLUDE  OBJLIB(PPCPnn)
          INCLUDE  OBJLIB(CCMCDCnn)
          OVERLAY  ONE
          INCLUDE  OBJLIB(STPPnn)
          OVERLAY  ONE
          INCLUDE  OBJLIB(BMP0nn)
          OVERLAY  TWO
          INCLUDE  OBJLIB(BMP1nn)
          OVERLAY  TWO
          INCLUDE  OBJLIB(BMP2nn)
          OVERLAY  TWO
          INCLUDE  OBJLIB(BMP3nn)
          OVERLAY  TWO
          INCLUDE  OBJLIB(BMP4nn)
          OVERLAY  TWO
          INCLUDE  OBJLIB(BMP5nn)
          OVERLAY  THREE
          INCLUDE  OBJLIB(BMP6nn)
          OVERLAY  THREE
          INCLUDE  OBJLIB(BMP7nn)
          NAME     PPCPnn(R)
/*

The global label table must be included in the TPF release link library. Standard MVS linkage editor procedures can be used to place it there. The table must be named BMGL.

For MVS systems, you must change the program name to IEWL.

The program version number is represented by nn (for example, BMP0nn).

If all of the DOF modules are not located in the current version of the TPF object library, it may be necessary to concatenate an object library from an earlier release to the OBJLIB data definition.

If the TPF system does not support local 3270 terminals, you do not need to include the BMP5, BMP6, and BMP7 segments in the link edit.

If the TPF system does not support PTV, you do not need to include all the BMP segments in the link edit.