Which Control-M files are needed when using the JCLCheck Resolve External Variable?
search cancel

Which Control-M files are needed when using the JCLCheck Resolve External Variable?

book

Article ID: 103574

calendar_today

Updated On:

Products

JCLCheck Workload Automation

Issue/Introduction

The JCLCheck Resolve External Variable feature for Control-M requires several Control-M  files to be available in JCLCheck.

Environment

Release: 12.0
Component: JCLCheck Workload Automation

Resolution


These DD names and their corresponding files are needed for JCLCheck  to resolve Control-M variables in the validating JCL: 

//DAALOCIN DD DSN=CTM.dallocin.file,DISP=SHR     CTM allocation file
//DAPARM   DD DSN=CTM.daparm.file,DISP=SHR       CTM Parm file
//DAPRENV  DD DUMMY                              Always use DUMMY CTM Environment file when using JCLCheck CAZ1PRES

You do not need to include these files if your installation uses a Control-M exit to provide these files dynamically.

The easiest way to find out if these DD names and corresponding files in your environment are needed is to locate the procedure CTMAESIM in your PROC library.  Review the PROC to see if the DD names of  DAALOCIN, DAPARM and DAPRENV exists. Use these same DD names and files for CA JCLCheck when resolving Control-M JCLs.

Note:   If your DAALOCIN points to a member name, you will also need to add the member name.

 

Additional Information

How to customize CA JCLCHECK when CONTROL-M has multiple DAPARM files?