Adding a comma to the EXEC JCL statement for continuation, resulted in the wrong Utility ID being used.

Document ID : KB000024015
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

When we add a comma to the PARM parameter of the EXEC JCL statement, in order to continue the parameter onto the next line, the comma is miss-interpreted and an incorrect utility ID is used.

//STEP1  EXEC PGM=PTLDRIVM,
//       PARM=('EP=UTLGLCTL/SSID,RESTART(PHASE),,',
//       'USERID.JOBNAME'),
//       REGION=7M

The utility ID is generated as follows:

PFU0255I - UTILID - ,USERID.JOBNAME - CHECKSUM - 16527
                            -----------------

The utility ID is suffixed with a comma.

Resolution:

The PARM parameter does not require an additional comma for continuation. The continuation is provided by enclosing the parameter in parenthesis.

In the above example, a comma is required to signify that no plan is coded, but no additional comma is required for the continuation:

//      PARM=('EP=UTLGLCTL/SSID,RESTART(PHASE),',
//      'USERID.JOBNAME'),
//      REGION=7M

Additional Information:

IBM documents the PARM JCL parameter as follows and provides two further examples:

The PARM= keyword is continued onto a second statement by enclosing the value it specifies in parenthesis, and enclosing any sub expressions within apostrophes followed by a comma. Begin the continued PARM value anywhere in columns 4 through 16 on the next JCL statement.

Example:

//JS10 EXEC ASMFC,PARM.PS10=(ESD,TERM,NUM,STMT,DECK,OBJECT,
//          NOMAP,NOLIST,'WORK=NOW')
 
or

//STEP201 EXEC PGM=SAS,PARM=('SYSIN=SASIN',
// MACRO,NOMPRINT,SOURCE))