RMS

Example 10-7 shows an examination of an alternate record.

You can use the Analyze/RMS_File utility to create an FDL file
generally called an analysis file. FDL files created by
ANALYZE/RMS_FILE contain statistics about each area and key in the
primary sections named ANALYSIS_OF_AREA and ANALYSIS_OF_KEY.

These analysis sections are then used by the Edit/FDL utility in its
Optimize script. You can compare the statistics in these sections with
your assumptions about the file’s use; you may find some places in the
file’s structure where additional tuning will be possible.

RMS Collector for T4 and Friends

Overview

This article
provides a technique of expanding T4 and Friends with additional data
collectors and with minimal impact to the core T4 procedures and utilizing
services provided by them. The example described is uses a MONITOR RMS
extension to monitor RMS file statistics.

RMS Performance: Duplicate key chains

Hein van den Heuvel

Does
your application use RMS Indexed files?
Do you know what a SIDR is? Do you know what a duplicate key chain is?
You probably should, since SIDRs and duplicate key chains can cause thousands
of read I/Os as the result of a single record insert. With that, they can have
a tremendous impact not just on the application doing the insert, but also on
total system performance. Application managers, of course, notice
a slowdown over time, and all too often they solve that by throwing more
hardware at the problem. But what if you already have the biggest box on the
market? Modest file tuning and a convert can help avoid all those read I/Os and
restore performance. I have yet to investigate an RMS application that did not
have this duplicate key chain problem. Maybe this is because I get called in
only for bad cases, or because indeed so many applications have this problem,
at least to some degree.