Example: batch compilation

The following steps occur:

• PROG1 and PROG2 are link-edited together to form one program object that has the name PROG2. The entry point of this program object defaults to the first program in the program object, PROG1.
• PROG3 is link-edited by itself into a program object that has the name PROG3. Because it is the only program in the program object, the entry point is also PROG3.

//jobname  JOB  acctno,name,MSGLEVEL=1
//stepname EXEC IGYWCL
//COBOL.SYSIN  DD *
010100 IDENTIFICATION DIVISION.
010200  PROGRAM-ID PROG1.
        . . .
019000  END PROGRAM PROG1.
020100 IDENTIFICATION DIVISION.
020200  PROGRAM-ID PROG2.
        . . .
029000  END PROGRAM PROG2.
 CBL NAME
030100 IDENTIFICATION DIVISION.
030200  PROGRAM-ID PROG3.
        . . .
039000  END PROGRAM PROG3.
/*
//LKED.SYSLMOD DD DSN=&&GOSET                   (1)
/*
//P2       EXEC PGM=PROG2
//STEPLIB  DD   DSN=&&GOSET,DISP=(SHR,PASS)     (2)
. . .                                           (3)
/*
//P3       EXEC PGM=PROG3
//STEPLIB  DD   DSN=&&GOSET,DISP=(SHR,PASS)     (2)
. . .                                           (4)
/*
//

(1)

The data-set name for the LKED step SYSLMOD is changed to the temporary name &&GOSET, without any member name.

(2)

The temporary data set &&GOSET is used as the STEPLIB for steps P2 and P3 to run the compiled programs. If the Language Environment® library does not reside in shared storage, you must also add the library data set as a DD statement for STEPLIB.

(3)

Other DD statements and input that are required to run PROG1 and PROG2 must be added.

(4)

Other DD statements and input that are required to run PROG3 must be added.