Creating object code (SYSLIN or SYSPUNCH)

When using the OBJECT compiler option, you can store the object code on disk as a traditional MVS™ data set or a z/OS® UNIX file, or on tape. The compiler uses the file that you define in the SYSLIN or SYSPUNCH DD statement.


//SYSLIN   DD  DSNAME=dsname,UNIT=SYSDA,
//             SPACE=(subparms),DISP=(MOD,PASS)

Use the DISP parameter of the SYSLIN DD statement to indicate whether the object code data set is to be:

  • Passed to the binder (linkage-editor)
  • Cataloged
  • Kept
  • Added to an existing cataloged library

In the example above, the data is created and passed to another job step, the binder (linkage-editor) job step.

Your installation might use the DECK option and the SYSPUNCH DD statement. B is the standard output class for punch data sets:


//SYSPUNCH DD  SYSOUT=B

You do not need the SYSLIN DD statement if the NOOBJECT option is in effect. You do not need the SYSPUNCH DD statement if the NODECK option is in effect.

related references  
OBJECT  
DECK