Using a cataloged procedure

For example, the following JCL calls the IBM®-supplied cataloged procedure IGYWC for compiling an Enterprise COBOL program and defining the required data sets:

//JOB1      JOB1   
//STEPA     EXEC PROC=IGYWC
//COBOL.SYSIN DD *             
000100 IDENTIFICATION DIVISION
      * (the source code)
. . .
/*

You can omit /* after the source code. If your source code is stored in a data set, replace SYSIN DD * with appropriate parameters that describe the data set.

You can use these procedures with any of the job schedulers that are part of z/OS®. When a scheduler encounters parameters that it does not require, the scheduler either ignores them or substitutes alternative parameters.

If the compiler options are not explicitly supplied with the procedure, default options established at the installation apply. You can override these default options by using an EXEC statement that includes the required options.

You can specify data sets to be in the z/OS UNIX file system by overriding the corresponding DD statement. However, the compiler utility files (SYSUTx) and copy libraries (SYSLIB) you specify must be MVS data sets.

Additional details about invoking cataloged procedures, overriding and adding to EXEC statements, and overriding and adding to DD statements are in the Language Environment® information.