Binding the executable or DLL into a PDSE

To bind the executable or DLL into a PDSE you can use sample JCL in Figure 1. While this JCL will work for most simple executables, the binder options (specified as PARM= below) will not be appropriate for all executables or DLLs. If you have a makefile for the executable or DLL, this will tell you what binder options should be used.

Because most executables in the file system today are program objects (new load module format), they must be bound into PDSE libraries. So, SYSLMOD DD should point to a PDSE (Data Set Name Type = Library).

Figure 1. Job for placing a program in the LPA

//PUTINLPA  JOB  MSGLEVEL=(1,1)
//*                                                            *
//* INLMOD DD STATEMENT SPECIFIES THE DIRECTORY THAT CONTAINS  *
//* THE PROGRAM.                                               *
//*                                                            *
//* THE INCLUDE STATEMENT SPECIFIES THE NAME OF THE FILE TO    *
//* RUN FROM THE LPA.                                          *
//*                                                            *
//* THE NAME STATEMENT SPECIFIES THE FILE NAME BUT IN          *
//* UPPERCASE. THIS MUST BE SAME AS THE FILE NAME.             *
//*                                                            *
//LINK     EXEC PGM=IEWL,REGION=100M,
//  PARM='LIST,XREF,LET,RENT,REUS,AMODE=31,RMODE=ANY,CASE=MIXED'
//SYSUT1   DD UNIT=SYSDA,SPACE=(CYL,(10,10))
//SYSPRINT DD SYSOUT=*
//INLMOD   DD PATH='/bin/'
//SYSLMOD  DD DSN=OECMD.LPALIB,DISP=SHR
//SYSLIN   DD *
         INCLUDE INLMOD(myprog)
         ENTRY   CEESTART
         NAME    MYPROG(R)
/*

Use an SMP/E USERMOD to link any IBM-supplied programs from a UNIX file system into another library, such as when loading it into LPA. Doing so automatically keeps the two copies of the module at the same level when service is installed. It also provides a record of modifications to your systems. See SMP/E for z/OS User's Guide for more information about SMP/E usermods.

Also, not all modules are eligible for LPA. Modules placed in LPA must be both reentrant and executable. For more information about PROGxx, see z/OS MVS Initialization and Tuning Reference.