

Special Usage Considerations › Resolve External Variable Installation Considerations
Resolve External Variable Installation Considerations
This topic discusses the resolve external variable installation considerations for CA WA CA 7 Edition, CA WA ESP Edition, Control-M, and Tivoli Workload Scheduler.
The following considerations are for CA WA CA 7 Edition
The following considerations are for CA WA ESP Edition
The following considerations are for Control-M
- The user of CA JCLCheck is the user ID used when CTMAESIM is called. This user must have the proper authority in CTMAESIM.
- Load module CAZ1PRES must reside in an authorized load library.
- The ISPF interface and EDCHEK must allocate several CTM DD statements before resolving CTM variables in the JCL. Modify the JCKUSRCM CLIST in CAI.CAZ2CLS0 as follows:
- Set variable &CTMALOC to point to the appropriate Control-M DAALOCIN file.
- Set variable &CTMPARM to point to the appropriate Control-M DAPARM file.
- Set variable &CTMPREN to point to the appropriate Control-M DAPRENV file.
Note: Some installations use a Control-M exit to provide these files, in which case you can leave these values in JCLUSRCM at their default values, ‘&STR()’.
- For batch jobs, update CAZ1JCCM as indicated in the procedure's comments. This includes specifying the following CTM files in the step that calls CAZ1PRES. Customize the CAZ1JCCM proc to specify these statements before it is used.
//DAALOCIN DD DSN=CTM.dallocin.file,DISP=SHR CTM allocation file
//DAPARM DD DSN=CTM.daparm.file,DISP=SHR CTM Parm file
//DAPRENV DD DSN=CTM.daprenv.file,DISP=SHR CTM Environment file
Note: Some installations use a Control-M exit to provide these files, in which case you do not need to include them.
The following considerations are for Tivoli Workload Scheduler
- The user of CA JCLCheck is the user ID used to issue commands to TWS. This user must have the proper authority in TWS to access the PIF interface and access the application, workstations, and operations they want to process.
- Load module CAZ1PRES must reside in an authorized load library.
- The ISPF interface, EDCHEK, and each batch job must allocate several TWS DD statements before resolving TWS variables in JCL. Modify the JCKUSRTW CLIST in CAI.CAZ2CLS0 as follows:
- Set variable &TWMLOG to the desired SYSOUT class for the EQQMLOG DD statement. This variable is for the TWS message log.
- Set variable &TWDUMP to the desired SYSOUT class for the EQQDUMP DD statement. This variable is for the TWS dump file.
- Set variable &TWYPARM to the data set that contains the parameters for the PIF interface. The EQQYPARM DD statement references this data set.
- Set variables &TWMLIB1 to &TWMLIB4 to the data sets that make up the EQQMLIB DD statement concatenation. These variables are for the TWS message library.
- For batch jobs, customize the CAZ1JCTW procedure. The following four TWS DD statements must be allocated in the step that calls CAZ1PRES.
Note: For more information about these statements, see Specify the Product and Parameters in Batch in the Tutorial.
//EQQMLOG DD SYSOUT=* TWS MESSAGE LOG
//EQQDUMP DD SYSOUT=* TWS DUMP FILE
//EQQYPARM DD DSN=tws.pif.parms PIF INTERFACE PARMS
//EQQMLIB DD DSN=tws.message.library TWS MESSAGE LIBRARY
Copyright © 2014 CA.
All rights reserved.
 
|
|