Managing the transaction server log of logs

After the log_of_logs is registered, RUV can automatically track the relationship between the CICS APPLID/FILEID, the VSAM file DSN, and the archives by scanning the operation and storing the information in the LOG_OF_LOGS. The relationships are established by using the tie-up records produced by CICS and Transaction Server. You can use the Transaction Server log of logs to quickly build an inventory of VSAM files that are being updated by Transaction Server regions. RUV reads the log of logs log stream and records the DSN and APPLID_FILEID information in the RUV repository. This information is available with the REPORT LOG_OF_LOGS command as described in LOG_OF_LOGS-report.

You can view information about the APPLID/FILEID associations that RUV has built from the log of logs and has recorded in the repository by using the REPORT APPLID(*) and REPORT VSAM_FILE(*) commands. RUV does not record recovery data from the log of logs; it just uses the information to create APPLID/FILEID/DSN associations. These associations are also built from tie-up records that are recorded on log streams.

RUV does not use the log of logs during recovery processing but obtains the relevant information from the RUV repository. The log of logs is merely a fast, convenient method for populating the repository with this information.

You can use the DELETE LOG_OF_LOGS command to remove the repository reference to the log of logs and prevent automatic scanning of the log of logs. This reference cannot be removed automatically.

To suspend processing of the log of logs temporarily, you can change the status of the log of logs to INACTIVE.

The Last Scanned field on the Log of Logs List panel contains the date and time of the last archive of a log stream. This field is updated only when a log stream is archived. The Date and Time field on the Log of Logs Detail panel shows the date and time that the file was opened or closed by CICS and Transaction Server; this action may occur after the scan is performed.

This topic contains the following information:

• • Using the REGISTER LOG_OF_LOGS command
  • Using the ADD LOG_OF_LOGS command
  • Using the UPDATE LOG_OF_LOGS command
  • Using the DELETE LOG_OF_LOGS command
  • Using the REPORT LOG_OF_LOGS command
  • Using the LOG_OF_LOGS keyword
  • Using the DELETE keyword
  • Using the DAYS keyword
  • Using the START_TIME keyword
  • Using Optional keywords
  • Coding ADD LOG_OF_LOGS statements
  • Coding DELETE LOG_OF_LOGS statements
  • Coding REGISTER LOG_OF_LOGS statements
  • Coding UPDATE LOG_OF_LOGS statements

Using the REGISTER LOG_OF_LOGS command

To scan, register, and add all recoverable CICS VSAM files immediately, use the REGISTER LOG_OF_LOGS command, as shown in the following recommended method:

Using the ADD LOG_OF_LOGS command

To automatically scan the Transaction Server's log of logs each time a z/OS log stream is archived, add a log of logs record to the repository by using the ADD LOG_OF_LOGS command, as shown in the following example:

Log of logs that are in an inactive status will not be automatically scanned. An automatic scan uses a default of DELETE(NO). The log of logs scan reads only new data that has been placed in the log since the last scan.

Using the UPDATE LOG_OF_LOGS command

To update the COMMENT and STATUS information in the log of logs record in the repository, use the UPDATE LOG_OF_LOGS command, as shown in the following example:

Using the DELETE LOG_OF_LOGS command

To delete the log of logs record from the repository, use the DELETE LOG_OF_LOGS command, as shown in the following example:

Using the REPORT LOG_OF_LOGS command

To report the log of logs record from the repository, use the REPORT LOG_OF_LOGS command, as shown in the following example:

The REPORT LOG_OF_LOGS output is described in LOG_OF_LOGS-report.

Using the LOG_OF_LOGS keyword

Use the required LOG_OF_LOGS keyword to identify the z/OS log of logs as follows:

• On the REGISTER, ADD, and UPDATE LOG_OF_LOGS command, set the value to the fully qualified log stream name.
• On the DELETE LOG_OF_LOGS command, set the value to the log stream name. You can use masking (wildcard) characters in the name. You can include multiple names; use a separator between the names.

Using the DELETE keyword

Use the optional DELETE keyword on the REGISTER LOG_OF_LOGS command to control whether RUV deletes the data that has been read from the log stream. Set one of the following values. The default value is NO.

• NO
  Leave the data intact. CICS tie-up records are written to the log of logs each time a CICS VSAM file is opened or closed; consequently, the log of logs slowly grows. You may want to run a delete job once a month or quarterly to clean out old information.
• YES
  Delete the data from the log stream.

Using the DAYS keyword

Use the optional DAYS keyword on the REGISTER LOG_OF_LOGS command to limit the number of days of data to be scanned; for example, DAYS(7) causes RUV to scan the last week of activity. Set the value to the number (1 through 999) of days.

The DAYS keyword on the SET DEFAULT command does not apply to the log of logs information. For more information, see Using-the-DAYS-keyword.

Using the START_TIME keyword

Use the optional START_TIME keyword on the REGISTER LOG_OF_LOGS command to set the starting time for the scan. For more information, see Using-the-START_TIME-keyword.

Using Optional keywords

You can use the following optional keywords on the ADD LOG_OF_LOGS and UPDATE LOG_OF_LOGS commands:

• COMMENT (see Using-the-COMMENT-keyword)
• STATUS (see Using-the-STATUS-keyword)

Coding ADD LOG_OF_LOGS statements

To code an ADD LOG_OF_LOGS statement, use the following syntax:

Coding DELETE LOG_OF_LOGS statements

To code a DELETE LOG_OF_LOGS statement, use the following syntax:

Coding REGISTER LOG_OF_LOGS statements

To code a REGISTER LOG_OF_LOGS statement, use the following syntax:

Coding UPDATE LOG_OF_LOGS statements

To code an UPDATE LOG_OF_LOGS statement, use the following syntax: