How to Use CA JCLCheck › Integrating Products › About External Variables › CA WA ESP Edition Parameters

CA WA ESP Edition Parameters

This topic contains the CA WA ESP Edition parameters and the following example:

• Sample Parameter Data Set

This procedure describes how to specify the parameters.

Follow these steps:

1. Specify the CA WA ESP Edition parameters in a sequential file (including partitioned data set member).
2. Start the parameters in column 1 and stop on or before column 71.
3. Specify the parameters in any order (there is no correct parameter order).
4. Specify comment lines (if necessary) by placing an asterisk (*) in column 1. Do not add comments to the right side of the parameter value.

The following parameters are for CA WA ESP Edition:

COMMAND=command

Identifies the CA WA ESP Edition command to invoke. This parameter is mandatory and can only be set to SIMULATE or SCAN.

Example: COMMAND=SIMULATE

SUBSYS=subsys

Identifies the CA WA ESP Edition subsystem name. If no subsystem name is specified, ESP is used.

Example: SUBSYS=ESPP

SYMBOL=symbol

Identifies the symbol-introducer character. If no symbol is specified, the character is taken from the subsystem.

Example: SYMBOL=%

EVENT=eventid

Identifies the name of the event for which CA WA ESP Edition simulates processing. This field is mandatory when invoking the SIMULATE command.

Example: EVENT=CYBER.PAYROLL

SCHED=schedtime

Represents the schedule time for the job. The time can be any valid time specification on a SCHEDULE statement. When schedtime contains separator characters (commas or blanks), it must be enclosed in quotes. If no schedule time is specified, the default is the next scheduled time.

Example: SCHED=TOMORROW

SYMLIB=symlib

SYMLIB2=symlib

SYMLIB3=symlib

Identifies the names of the data sets to be used as symbol libraries for symbolic variable generation. The parameters SYMLIB2 and SYMLIB3 can be used when the data set names do not fit on the SYMLIB line. All file names should be fully-qualified.

Example: SYMLIB=USERID1.JCKESP.CNTL(SYMLIB)

CALENDAR=cal

CALENDR2=cal

CALENDR3=cal

Identifies the calendars that are retrieved for this SCAN. The parameters CALENDR2 and CALENDR3 can be used when the calendar names do not fit on the CALENDAR line.

Example: CALENDAR=CAL2011

PROCJOB=jobname

Identifies the fully qualified CA WA ESP Edition job name, which endures process-mode simulation. This parameter is a mandatory field when invoking the SIMULATE command in ISPF. If PROCJOB is not specified in batch, the job name that is used comes from the JOBNAME parameter (specified in the RESPARM parameter). If PROCJOB is not specified when running under EDCHEK, the job name that is used comes from the ISPF EDIT session member name.

Example: PROCJOB=C.WICKEDWITCH

VARS=var_list

VARS2=var_list

VARS3=var_list

VARS4=var_list

VARS5=var_list

Provides a list of variable names and values. These variables can include monitor and signal variables. The parameters VARS2, VARS3, VARS4, and VARS5 can be used when the variables do not fit on the VARS line.

Example: VARS=MNJOB(PAYJOB1),MNAPPL(PAYROLL)

USER1=user_data

USER12=user_data

Identifies the USER1 variable passed to the event. The parameter USER12 can be used when the variable does not fit on the USER1 line.

Example: USER1=IEFBR14

USER2=user_data

USER22=user_data

Identifies the USER2 variable passed to the event. The parameter USER22 can be used when the variable does not fit on the USER2 line.

Example: USER2=SYSIN

USER3=user_data

USER32=user_data

Identifies the USER3 variable passed to the event. The parameter USER32 can be used when the variable does not fit on the USER3 line.

Example: USER3=SYSPRINT

USER4=user_data

USER42=user_data

Identifies the USER4 variable passed to the event. The parameter USER42 can be used when the variable does not fit on the USER4 line.

Example: USER4=SYSUDUMP

JCLSCAN=exit_rtn

Identifies the name of the JCLSCAN exit module.

Example: JCLSCAN=CYBJCSCN

RECORD

Informs CA JCLCheck to record the resolution session. The record data is written to the partitioned data set allocated in the RECORD DD statement. Allocate this file as a PDS whose DCB is LRECL=500, RECFM=FB, and DSORG=PO. Under EDCHEK and ISPF, the name of this file must be specified in the JCKUSRES CLIST. In a batch job, the JCL deck must contain a RECORD DD statement.

Use this parameter only under the direction of CA Support.

Example: RECORD

RECORDSEQ

Informs CA JCLCheck to record the resolution session. The record data is written to a sequential data set allocated in the RECORDSQ DD statement. Allocate this file as a sequential file whose DCB is LRECL=500, RECFM=FB. Under EDCHEK and ISPF, the name of this file must be specified in the JCKUSRES CLIST. In a batch job, the JCL deck must contain a RECORDSQ DD statement.

Use this parameter only under the direction of CA Support.

Example: RECORDSEQ