Skip to Content
Information
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 CMF 6.3.

Preprocessing of Extractor data sets

There are several reasons why you might want to preprocess CMF Extractor data sets before producing reports:

  • Extractor data set damage

    System outages can damage the integrity of Extractor output data sets and cause a variety of QSAM-related errors when using the Analyzer. The CX10CVBS utility that is distributed with CMF MONITOR repairs damaged Extractor data sets and copies them to a new data set. CX10CVBS can process sequential as well as VSAM files.

    After you have used the CX10CVBS utility to copy the data, S001 and S002 abends are eliminated when using the CMF MONITOR Analyzer because of the presence of an end-of-file (EOF) mark.

  • Specific record type collections

    You might want to create a subset of a data set to be used as input to CMF, RMF, or a user-written report program, so that the data set contains only specific record types. A smaller data set can decrease processing time for your reports, or a user-written program might accept only certain types of SMF records.

  • RMF identical record creation

    By processing the CMF data using the CX10CVBS utility, CMF flags that are set in a reserved field in the CMF records are reset, making the CMF records identical to RMF records.

  • Specific sequence requirement

    The normal sequence of CMF- and RMF-created SMF records from any given system is DATE and TIME, as the records are written in chronological order. In addition, the SYSID in a set of records from a given system is always the same; therefore, the actual sequence of the records can be said to be SYSID, DATE, TIME. Analyzer expects each input file to be ordered in this sequence, whether there is a single input file, a concatenation of two or more files under a single DD name, or multiple input files, each under a unique DD name.

    Under some circumstances, Analyzer enforces this requirement and, should a record be read that is out of sequence, it will terminate immediately. Those circumstances are as follows:

    • When Analyzer encounters a SHIFT statement with RPTS=DAILY parameters specified in conjunction with a SYSPLEX statement with RPTS=COMBINED specified; this situation demands that data input to Analyzer be sorted in a specific sequence in order to be properly processed
    • When you want to produce LOTUS DOMINO reports
    • When you want to produce HTTP server reports
    • When you want to produce Dataset Activity reports

    Any sort utility that is supported by MVS can be used to sort CMF data. The sort control statement should be written as follows:

    SORT FIELDS=(15,4,CH,A,11,4,BI,A,7,4,BI,A),EQUALS

This section contains the following topics:

Related topics

DOMINO
HTTP
DATASET
CMF-record-mapping



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

CMF MONITOR 6.2