BTSAPRE0 JCL requirements

JCL statements

The following list summarizes the JCL statements for BTSAPRE0 JCL.

BTSIN (Input)

Additional statements required by in the BTSIN of IMS Batch Terminal Simulator will be written.

The DCB for this data set is RECFM=FB,LRECL=80.

CNTLCRDS (Input)

Contains the CNTLCRDS control statements.

The DCB for this data set is RECFM=FB,LRECL=80.

CROSSREF (Output)

Formatted extracts of the '01'x and '03'x records from BTSALOG0 are written. An additional sequence number is prefixed to the first record for each message.

The DCB for this data set is RECFM=VB,LRECL=32756.

PAGECNTL (Input)

Input file used to specify the number of physical pages to be associated with a MOD name, in the case of a multi-page MOD.

The DCB for this data set is RECFM=FB,LRECL=80.

STEPLIB (Input)

Describes the library that contains Playback.

SYSPRINT (Output)

Diagnostic messages and summary reports will be written.

The DCB for this data set is RECFM=FB,LRECL=133.

TRXIN (Input)

Contains the formatted extracts of the '01'x and '03'x records created by BTSALOG0.

The DCB for this data set is RECFM=VB,LRECL=32756.

TRXOUT (Output)

Formatted extracts of the '01'x and '03'x records from BTSALOG0 are written, each with an additional sequence number prefixed.

The DCB for this data set is RECFM=VB,LRECL=32756.

CNTLCRDS control statement keywords

Playback processing can be influenced by the CNTLCRDS control statements that are read from the CNTLCRDS file.

Most control statements are optional. The default result of statement omission is discussed for each keyword.

All of the keywords are optional. If none of the IGNORE-related keywords are used, no records will be specifically bypassed for processing. If none of the selection-related keywords are used, all records will be candidates for processing.

If a record matches some criteria for processing and also matches some criteria for being ignored, it will not be processed.

Related reading: For syntax rules, see Syntax rules for the control statements.

The following keywords apply to BTSAPRE0.

IGNOREMOD= keyword

This keyword specifies a MOD name for which associated records will not be processed.

The format of the IGNOREMOD= keyword is IGNOREMOD=modname where modname is an 8-character field.

Additional allowable modname value:

• BLNK#VAL - eight characters of blank

The IGNOREMOD= keyword is optional. If omitted, no records will be ignored based upon the MOD name.

If IGNOREMOD= and MODNAME= have the same value, MODNAME is ignored.

You can specify up to 1000 IGNOREMOD= specifications.

IGNORETERM= keyword

This keyword specifies an LTERM name for which associated records will not be processed.

The format of the IGNORETERM= keyword is IGNORETERM=lterm_name where lterm_name is an 8-character field.

Additional allowable lterm_name values are:

• HIGH#VAL - eight characters of 'FF'X
• NULL#VAL - eight characters of '00'X

The IGNORETERM= keyword is optional. If omitted, no records will be ignored based upon the LTERM name.

You can specify up to 1000 IGNORETERM= specifications.

IGNORETYPE= keyword

This keyword specifies a log type, for which associated records will not be processed.

The format of the IGNORETYPE= keyword is IGNORETYPE=log_type where log_type is '01' or '03'.

The IGNORETYPE= keyword is optional. If omitted, no records are ignored based upon the log type.

MODNAME= keyword

This keyword specifies a MOD name for which associated records will be processed.

The format of the MODNAME= keyword is MODNAME=modname where modname is an 8-character field.

The MODNAME= keyword is optional. If omitted, no records will be selected specifically based upon the MOD name.

If IGNOREMOD= and MODNAME= have the same value, MODNAME is ignored.

You can specify up to 1000 MODNAME= specifications.

PROCESS= keyword

This keyword specifies the number of records to be processed from the CROSSREF file.

The format of the PROCESS= keyword is PROCESS=value where value is a 1- to 8-digit numeral.

The PROCESS= keyword is optional. If omitted, all of the records from where processing begins are processed.

You can specify only one PROCESS= control statement.

SKIP= keyword

This keyword specifies the number of records to be skipped in the TRXIN file prior to processing records.

The format of the SKIP= keyword is SKIP=value where value is a 1- to 8-digit numeral.

The SKIP= keyword is optional. If omitted, no records are skipped prior to record processing.

You can specify only one SKIP= control statement.

TRX= keyword

This keyword specifies a transaction code for which associated records will be processed.

The format of the TRX= keyword is TRX=transaction_code where transaction_code is an 8-character field.

The TRX= keyword is optional. If omitted, no records will be selected specifically based upon the TRX= value.

You can specify up to 1000 TRX= specifications.

TRXLINK keyword

This keyword specifies that the records associated with the specified transaction are also processed.

Use this keyword together with the TRX= keyword. When both the TRX= keyword and the TRXLINK keyword are specified, in addition to the records identified by the TRX= keyword, BTSAPRE0 also processes the records that have the same originating timestamp as the records identified by the TRX= keyword.

To specify the TRXLINK keyword, do not code the TRX= keyword in CNTLCRDS DD of the BTSALOG0 module. If coded, necessary records will not be extracted in the BTSALOG0 step.

The TRXLINK keyword is optional. If this keyword is omitted and the TRX= keyword is specified, only the records that contain the specified transaction code are processed.

USERID= keyword

This keyword specifies a user ID for which associated records will be processed.

The format of the USERID= keyword is USERID=userid where userid is an 8-character field.

The USERID= keyword is optional. If omitted, no records are selected specifically based upon the USERID= value.

You can specify up to 1000 USERID= specifications.

PAGECNTL control statement keywords

Playback supports screen processing when there are multiple physical pages associated with a MOD. However, Playback cannot automatically detect which MODS have multiple pages. You can use the PAGECNTL file, which is used by BTSAPRE0, to specify the number of physical pages that are associated with a MOD. If there is only one page associated with a MOD, you do not need to use the PAGECNTL file.

Records that contain the control statements that are described in this topic are read from the PAGECNTL file.

Related reading: For syntax rules, see Syntax rules for the control statements.

The following keywords apply to the PAGECNTL DD statement.

MODNAME= keyword

This keyword specifies a MOD name for which associated records will be processed.

The format of the MODNAME= keyword is MODNAME=modname where modname is an 8-character field.

The MODNAME= keyword is required.

You can specify up to 1000 MODNAME= specifications.

PAGES= keyword

This keyword specifies the number of physical pages that are present in the indicated MOD name.

The format of the PAGES= keyword is PAGES=value where value is a 1- to 2-digit numeric.

The PAGES= keyword is required.