Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Limited supportBMC 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 IMS Offline 5.6.

Log Edit input data

Input to Log Edit consists of IMS transaction workload data that has been recorded in the IMS log.

Some of the IMS log records are written by IMS and some are written by the Event Collector. The Log Edit IMFLEDIT program processes all of the BMC AMI Ops Monitor for IMS Offline product records and some of the IMS records to produce reports and files that can serve as input to the BMC AMI Ops Monitor for IMS Offline components. All input data should represent a single day, as described in Customizing-after-installation.

To implement input record selection through the standard IMS log archive process, specify a user output file and record selection control statements.

With the IMFLEDIT program, you can extract the data directly from the IMS log or from an archived subset of the log. Sample log archive JCL is provided in BMC AMI Ops Monitor for IMS Offline BBSAMP member ARCHJCL. Sample control statements are provided in members ARCHCTL1 and ARCHCTL2.

Log-record-layouts describes the record layout of the IMS log files.

Tip

To avoid producing a separate data set during each archive run, you can specify DISP=MOD for the user output file.

This section contains the following topics:

 

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