Example: Using JCL to copy from the file system to a PDS

To copy an executable out of the file system and into a data set, you need to use the binder to reprocess the executable. Here is an example of JCL our friend TURBO wrote for copying a z/OS XL C/C++ load module into a data set:

  //TURBO     JOB (XX,YY,ZZ),MSGCLASS=H,CLASS=A,
  //          MSGLEVEL=(1,1)
  //*
  //LKED      EXEC PGM=IEWBLINK,REGION=500K,
  //          PARM='LIST,REUS,RENT,NCAL,LET,MAP'
  //SYSPRINT DD  SYSOUT=*
  //SYSLMOD  DD  DSN=TURBO.POSIX.LOADLIB,DISP=SHR
  //*
  //INLIB    DD  PATH='/u/turbo/llib/payrll',
  //             PATHOPTS=(ORDONLY)
  //*
  //SYSLIN   DD  *
          INCLUDE INLIB
          ENTRY CEESTART
          NAME PAYRLL(R)
  /*

This job relinks, or rebinds, the z/OS XL C/C++ executable /u/turbo/llib/payrll, and puts the output into TURBO.POSIX.LOADLIB(PAYRLL). Be sure you specify the correct entry point—in this case, CEESTART—for a z/OS XL C/C++ program. If you do not specify the entry point, the entry point is assumed to be at the beginning of the executable. Also, if required, you must specify AC=1.

If this is a DLL created using V2R4 or later and without the use of the prelinker, any definition side-decks of IMPORT control statements will need to be re-specified as input to the binder. In general, any control statements and options that were used when the original /u/turbo/llib/payrll was created will need to be specified again.