This topic contains the TWS parameters and the following example:
This procedure describes how to specify the parameters.
Follow these steps:
The following parameters are for TWS:
Identifies the TWS subsystem name. If no TWS subsystem name is provided, OPCC is used. This parameter must be present on the first non-comment line.
Example: SUBSYS=OPOP
Identifies the 16-character application ID that is used for selection in batch and for variable substitution in JCL in EDCHEK. This parameter is mandatory.
Example: ADID=DFAG0D00BCV2GRCA
Specifies the ten-character input arrival date and time that is used for selection in batch and for variable table selection in EDCHEK. This field defaults to the current date and time.
Example: IA=1004301800
Identifies the 16-character work application ID. This application ID is created to hold external JCL for resolution temporarily. You can use W_ADIDC and W_ADIDT instead to create the work ADID. This field defaults to JCLCHECKDEFAULT.
Example: W_ADID=DFAG0D00BCV2GRCA
Specifies a two character numeric value between 01-15.
When the W_ADID keyword is omitted or set to "JCLCHECKDEFAULT", the work ADID (W_ADID) value can be created from the production ADID specified in OADID. The value in OADID is modified starting at the column specified in W_ADIDC. W_ADIDT specifies the two characters to substitute. W_ADIDC must be set to a two-character numeric value between 01-15. W_ADIDT must be set to a two-character text value.
Example: W_ADIDC=09 W_ADIDT=PR
If OADID is set to PRODAPPLTX023, the work application name (W_ADID) that would be generated is PRODAPPLPR023.
Specifies the date on which the application is valid. This field defaults to the current date.
Example: VALID=100722
Specifies the four-character workstation name that is used for operations in the work application. This workstation must be a valid Type C (computer) workstation that is defined to TWS. This parameter is mandatory if SRCETYPE=SEQ.
Example: W_WSNAME=WSPR
Specifies the three-digit work operation number (0-255). If any TWS variables in the JCL refer to &OOPNO, this value is substituted. This parameter is mandatory if SRCETYPE=SEQ.
Example: W_OPNO=10
Specifies the eight-character group definition ID that is used for the work application.
Example: W_GROUP=GROUPPRD
Specifies the 16-character owner ID that is used for the work application.
Example: W_OWNER=USERID1
By default, CA JCLCheck uses the ADRUN option on the INSERT APPLICATION to prevent TWS from submitting the application for execution. Sites that use the TWS GROUPID option to specify run dates must specify ADRUN=NO as TWS does not allow both. Care must be taken when using ADRUN=NO to insure TWS does not select the application for submission. When using the TWS interface through the ISPF panels, specify the ADRUN option in the Appl Run Dates (Y or N) field (panel JCK0207).
Specifies a six-character temporary variable name that is used internally to replace the &OADID variable in the JCL during the variable resolution process. In TWS, the &OADID variable can be used in JCL to specify the Application ID. Since CA JCLCheck uses a work application, the value that is supplied by TWS in the &OADID variable is the work application ID (not the original application ID). The original application ID can be inappropriate for the JCL. This temporary variable name is used internally instead of the &OADID variable in the JCL. The name must begin with “&T”, then four alpha-numeric characters that equal a total of six characters in length. Also, do not match this name with any other variable name that is defined in the JCL. If not specified, &TJCG0 is used.
Example: &OADID=&TJCHK
Specifies the 12-character simulated date and time. The yyyy can be any year between 1984 - 2071. This field defaults to the current date and time.
Example: SIMTIME=201007011248
Identifies the 16-character JCL variable table name for the work application. In a batch job, it defaults to the value specified in the application. In ISPF, if not specified, the default is the table specified in the application or the system default.
Example: JCLVTAB=TESTVARIABLETBL
Identifies the source of the input JCL.
I—Internal—The input JCL is pulled directly from TWS.
E—External—The input JCL comes from an external file that a SYSIN DD statement defines.
EI—External/Internal—The input JCL comes from an external file that a SYSIN DD statement defines. However, when a particular member is not found in the SYSIN file, the internal JCL for the event is used.
Example: SOURCE=E
Identifies the format of the SYSIN file when SOURCE=E or EI. This parameter is mandatory when SOURCE=E or EI. This parameter is ignored if SOURCE=I.
Example: SRCETYPE=SEQ
Informs CA JCLCheck to take diagnostic snap dumps. The dumps are written to the file allocated in the SNAP DD statement. Allocate this file as a SYSOUT file or a file whose DCB is LRECL=125, BLKSIZE=882, RECFM=VBA, and DSORG=PS. Under EDCHEK, a SNAP DD statement must be allocated before calling CA JCLCheck. Under the ISPF interface, a data set with the name of the Resolve Parm File with an '.S' appended to the end of it is allocated automatically. In a batch job, the JCL deck must contain a SNAP DD statement.
Use this parameter only under the direction of CA Support.
Example: SNAP
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, a RECORD DD statement must be allocated before calling CA JCLCheck. Under the ISPF interface, a data set with the name of the Resolve Parm File with an '.R' appended to the end of it is allocated automatically. 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
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 and RECFM=FB. Under EDCHEK, a RECORDSQ DD statement must be allocated before calling CA JCLCheck. In a batch job, the JCL deck must contain a RECORDSQ DD statement. This option is not supported under the ISPF interface.
Use this parameter only under the direction of CA Support.
Example: RECORDSEQ
Note: The ADID and IA values are used to select the jobs that are processed by accessing the application records in TWS. The ADID and IA values are also used to retrieve the list of operations (jobs) and dependent operations in the application. These values provide the job names and operation numbers for each job being processed, as well as the execution order for the operations. The execution order is the order CA JCLCheck processes the operations.
|
Copyright © 2013 CA.
All rights reserved.
|
|