Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for CICS, version 7.3

Archive-purge process

The CMRPURG job performs the following operations:
  1. The job reads data from the recorder data sets, merges it with another archive data set (HISTORY=YES), and then writes it to the history output tape (HISTORY=YES or HISTORY=OUT). If HISTORY=NO is specified, the data is deleted and not archived.

  2. The job purges data from the recorder data sets.

    Note

    Purging is performed here so that abends (such as tape errors) do not leave the recorder data sets in a state of reduced integrity.

    The data that is purged is determined by the DATE= control statement. The entire data set can be purged by specifying DATE=12319999, or a portion of the recorder data set can be purged as follows:

  • A. If only part of a data set is to be purged, you can define the VSAM REUSE parameter when the MainView for CICS recorder data set is defined, as described in the MainView for CICS Customization Guide, and allocate a temporary data set, as shown by CMRWRK1 in the previous sample JCL. CMRPURG uses CMRWRK1 to contain temporarily the records that are to remain on the recorder data set. REUSE reorganizes and resets the data sets so that records written to CMRWRK1 from these data sets can be reloaded.

  • B. CMRPURG processes the CMRDETL or CTGDETL recorder data set. The records stamped with the DATE value or a date previous to the specified date are written as specified by the HISTORY= control statement.

  • C. The selected records are deleted from the data set if NOREUSE is specified, which can be a time-consuming update to the data set.

    If an abend occurs while archiving data, check the messages on the report output to determine at what point it occurred. CMRPURG does not write the same record twice if it exists on both the history and the recorder data sets.

    Each phase of the archive-purge process is recorded in the Recorder File Purge Report. The following figure shows a typical listing for CMRDETL recorder data sets.

    Sample recorder file purge report listings

    Report Listing for CMRDETL Recorder File
    
      C I C S   M A N A G E R   R E C O R D E R   F I L E   P U R G E
    
    FT290I-DETAIL TRANSACTION RECORDER FILE BEING PROCESSED
    FT293I-BEGINNING ARCHIVE OF REQUESTED RECORDS
    FT294I-ARCHIVE OF REQUESTED RECORDS COMPLETED
    FT295I-BEGINNING PURGE OF REQUESTED RECORDS
    FT296I-PURGE OF REQUESTED RECORDS COMPLETED
    FT297I-CMRWRK1 DATASET FOUND - BEGINNING REORGANIZATION
    FT298I-ENTERING SECOND PHASE OF REORGANIZATION
    FT301I-REORGANIZATION OF RECORDER FILE COMPLETED
    
      ------ RECORDER FILE ------     -- HISTORY FILE ACTIVITY --
          INPUT        PURGED               INPUT     OUTPUT
    
        000001667     000001666           000000000 000001666

Was this page helpful? Yes No Submitting... Thank you

Comments