Control-M auto-edit variables are not getting resolved when using CA-JCLCHECK
Article ID: 189281
Updated On:
Products
JCLCheck Workload Automation
UNICENTER JCLCHECK COMMON COMPONENT
Issue/Introduction
Control-M auto-edit variables are not getting resolved when using CA JCLCheck with the CAZ1PRES Resolve program to validate a Control-M job.
Environment
Release : 12.0
Component : CA JCLCheck Workload Automation
Resolution
To resolve Control-M variables:
1. Add Control-M CTMAESIM option SETVAR to the CA JCLCheck RESPARMS DD control data set in the CAZ1PRES step.
Example:
SETVAR %%myvar=xyz
and/or
2. Use Control-M control statement %%LIBSYM with %%MEMSYM, and/or control statement %%GLOBAL in the JCL member. These control statements are used to set values for user-defined variables.
Example:
//* %%LIBSYM AUTOEDIT.LIBRARY %%MEMSYM member
//JOB statement
//STEP1 EXEC MYPROC,
%%IF %%MYVAR EQ xyz
// CONDMTH='(0,NE)',
%%ENDIF
// OUTN='*'
1. Add Control-M CTMAESIM option SETVAR to the CA JCLCheck RESPARMS DD control data set in the CAZ1PRES step.
Example:
SETVAR %%myvar=xyz
and/or
2. Use Control-M control statement %%LIBSYM with %%MEMSYM, and/or control statement %%GLOBAL in the JCL member. These control statements are used to set values for user-defined variables.
Example:
//* %%LIBSYM AUTOEDIT.LIBRARY %%MEMSYM member
//JOB statement
//STEP1 EXEC MYPROC,
%%IF %%MYVAR EQ xyz
// CONDMTH='(0,NE)',
%%ENDIF
// OUTN='*'
Additional Information
In the Documentation:
Feedback
Yes
No
Powered by
