Specifying object code files: SYSLNK and SYSPCH

When using the OBJECT assembler option, or DECK assembler option, you can store the object code on disk or tape. The assembler uses the SYSLNK or SYSPCH files you define in your JCL to store the object code.

In this example, the created object module is ready to be passed to the linkage editor:

// DLBL IJSYSLN,'file-ID',0,SD
// EXTENT SYSLNK,volser,1,0,start,tracks
// ASSGN SYSLNK,DISK,VOL=volser,SHR

You do not need to define SYSLNK in your JCL if the NOOBJECT option is in effect.

The following example defines SYSPCH as a direct-access device file:

// DLBL IJSYSPH,'file-ID',0,SD
// EXTENT SYSPCH,volser,1,0,start,tracks
ASSGN SYSPCH,DISK,VOL=volser,SHR

You do not need to define the SYSPCH file if the NODECK option is in effect.