IBM Mainframe Forum

by **RalphEagle** » Wed Jun 16, 2021 3:01 pm

Hi,

I am defining variable names inside a JCL, such as:

//V1   SET SELO='WORK.JOHN.SHEET'
//V2   SET SELRFMT='WORK.JOHN.OUTPUT.CODE'

I would like to introduce a variable part in these, so that the name JOHN above can be customized as well:

Select all

//V0   SET NAME='MARY'
//V1   SET SELO='WORK.&NAME..SHEET'
//V2   SET SELRFMT='WORK.&NAME..OUTPUT.CODE'

I get an error from improper use of ampersand in the DSN field, I suppose because double substitution is not recognized?

Select all

 6 IEFC627I INCORRECT USE OF AMPERSAND IN THE DSN FIELD

Is there a way to do this?

Thank you,

by **sergeyken** » Wed Jun 16, 2021 5:08 pm

Do not use quotes when combining new value including other SET-variables.
This way you’ll be on safe side.

Select all

//V0   SET NAME='MARY'
//V1   SET SELO=WORK.&NAME..SHEET
//V2   SET SELRFMT=WORK.&NAME..OUTPUT.CODE

by **willy jensen** » Wed Jun 16, 2021 5:34 pm

Actually, don't use quotes unless absolutely necessary

Select all

//V0   SET NAME=MARY                        
//V1   SET SELO=WORK.&NAME..SHEET           
//V2   SET SELRFMT=WORK.&NAME..OUTPUT.CODE

by **RalphEagle** » Wed Jun 16, 2021 5:49 pm

Thanks, it worked like a charm!

by **sergeyken** » Wed Jun 16, 2021 6:05 pm

The problem with quotes, and parameters has been created by IBM itself, long time ago.

Parameters are substituted within quotes in PARM field:

Select all

// EXEC PGM=xxxx,PARM=‘&START,&END’ - this works fine

The same parameters are NOT substituted in most of other situations with quotes:

Select all

// SET ALLPARM=‘&START,&END’     - ampersands are not resolved
// EXEC PGM=xxxx,PARM=‘&ALLPARM’ - this does not work
// EXEC PGM=yyyy,PARM=&ALLPARM   - this does not work as well

We need to blame IBM for this mess they have created!

by **sergeyken** » Wed Jun 16, 2021 6:23 pm

But there is one secret trick

Select all

// SET QUOTE=’’’’
// SET COMMA=’,’
// SET ALLPARM=&QUOTE&START&COMMA&END&QUOTE
// EXEC PGM=yyyy,PARM=&ALLPARM   - this works! But is ugly…

IBM Mainframe Forum

Variable part in a JCL variable name

Variable part in a JCL variable name

Re: Variable part in a JCL variable name

Re: Variable part in a JCL variable name

Re: Variable part in a JCL variable name

Re: Variable part in a JCL variable name

Re: Variable part in a JCL variable name