BTSALOG0 JCL requirements

JCL statements

The following list summarizes the JCL statements for BTSALOG0 JCL.

JCLLIB ORDER=jclpds (Input)

This statement is a JCL statement. It must directly follow the JOB statement in the JCL stream.

This statement references the partitioned data set with a member that contains the LOG DD statements that identify the log data set names.

This statement is required only if the log data set names are to be extracted from RECON.

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.

INCLUDE (Input)

This statement is a JCL statement. This statement specifies the member name from the partitioned data set identified in JCLLIB that identifies the LOG DD statements when BTSARCN0 was used.

LOG (Input)

Refers to the IMS OLDS or SLDS.

This DD statement can be supplied in one of the following ways:

• When BTSARCN0 was not used to generate LOG DD statement, specify it in the JCL.
• When BTSARCN0 was used to generate LOG DD statement, specify it as a member of the PDS—specified by the JCLLIB statement—of the INCLUDE statement.

The DCB for this data set is RECFM=VB,LRECL=32756, or equivalent DCB, if the log data sets were created with a different LRECL.

MSGLIST (Output)

Records that are related to extracted messages are written.

You can process these records to create additional reports, if you include the MSGLIST keyword in the CNTLCRDS statements.

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

Related reading: See MSGLIST file record format for information about the MSGLIST file records.

REPORT (Output)

Diagnostic messages and summary reports are written.

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

STEPLIB (Input)

Describes the library that contains Playback.

SYSPRINT (Output)

Diagnostic messages and summary reports are written.

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

TRXOUT (Output)

Formatted extracts of the '01'x and '03'x records are written.

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

Related reading: See Playback utility record format for information about the records.

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.

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 some criteria for being ignored, it will be ignored.

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

The following keywords apply to BTSALOG0.

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 value:

• 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.

If IGNORETERM= and TERMID= have the same value, TERMID is ignored.

You can specify up to 500 IGNORETERM= specifications.

IMSLEVEL= keyword

This keyword identifies the level of IMS that was used to create the IMS log.

The format of the IMSLEVEL= keyword is IMSLEVEL=value where value is the version of IMS. For example, 15 indicates IMS 15.

The IMSLEVEL= keyword is required.

Requirement: IMSLEVEL= control statement must specify one of the currently supported versions of IMS.

LCLTIME= keyword

This keyword identifies the difference between the local time and Coordinated Universal Time (UTC), the format in which log time stamps are stored. The use of this keyword adjusts the STRTTIME and STOPTIME values, which can be entered as local time values to be consistent with the STCK values on the log, which are in UTC. The value represents the hours and minutes that need to be added to or subtracted from local time to make it match UTC.

The format of the LCLTIME= keyword is LCLTIME=shhmm where:

• s is a sign value (+ or -).

  s is required.

• hh is the hours difference between UTC and local time.

  hh is required.

• mm is the additional minutes difference between UTC and local time.

  mm is optional. Most time zones do not have additional minutes in the difference between UTC and local time.

The LCLTIME= keyword is optional. If omitted, the STRTTIME and STOPTIME values are considered to be UTC.

MSGLIST keyword

This keyword advises that records be written to the MSGLIST data set.

The format of the MSGLIST keyword is: MSGLIST

The MSGLIST keyword is optional. If omitted, no records are written to the MSGLIST data set.

PROCESS= keyword

This keyword specifies the number of records to be processed.

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 will be processed.

You can specify only one PROCESS= control statement.

SKIP= keyword

This keyword specifies the number of records to be skipped in the LOG 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.

STOPTIME= keyword

This keyword specifies the time of the first record to be processed. An exact match of time is not required; processing will begin with the first record equal to or greater than the indicated time.

The format of the STOPTIME= keyword is STOPTIME=value, where value is the 19-digit time that is used in the logs. The format of this value is yyyydddhhmmssthmiju. The last five digits are ignored.

The STOPTIME= keyword is optional. If omitted, the log will process until the end is reached, unless the PROCESS= keyword has been used.

STRTTIME= keyword

This keyword specifies the time of the first record to be processed. An exact match of time is not required; processing begins with the first record equal to or greater than the indicated time.

The format of the STRTTIME= keyword is STRTTIME=value, where value is the 19-digit time that is used in the logs. The format of this value is yyyydddhhmmssthmiju. The last five digits are ignored.

The STRTTIME= keyword is optional. If omitted, the log will be processed from the beginning of the file, unless the SKIP= keyword has been used.

TERMID= keyword

This keyword specifies an LTERM name for which you want to process associated records.

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

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

If IGNORETERM= and TERMID= have the same value, TERMID is ignored.

You can specify up to 500 TERMID= specifications.

TRX= keyword

This keyword specifies a transaction code for which associated records are to 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 500 TRX= specifications.

USERID= keyword

This keyword specifies a user ID for which associated records are to 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 500 USERID= specifications.