Measure Reference Manual

OSS Journal Segment
The OSS journal segment is a set of OSS file pathname translations captured for Measure data
collection. It provides OSS file pathname translations for data records in the Measure data file
when such translations are no longer available from the OSS name server. The OSS name server
cannot translate the OSS file pathname due to time constraints and the relocation of the data file
to another node or network.
The main feature of OSS file pathname support in Measure is the creation of an OSS journal
segment. The OSS journal segment ensures portability of OSS file pathnames translation between
systems and over time. It also eliminates the need to access the OSS name server of the system
being measured to analyze or report on OSS objects in Measure data.
OSS journal segment construction is not required when you use or view OSS file pathnames in
Measure data or when you analyze Measure data on the local system. OSS journal segment
construction is required when OSS file pathname translation must be available to reporting
applications in structured Measure data output.
Measure builds the OSS journal segment at measurement shutdown and inserts it in the Measure
data file. The journal segment is loaded into memory and attached to an application process or
MEASCOM when a Measure data file is opened for analysis. This feature is optional. The default
is no journal segment.
If an OSS file is deleted before the measurement ends, the translation may not be captured in the
OSS journal. As a result, the following message may be generated in the MEASCOM listing: ***
Translation - Not Available ***.
Entity Report Formats
The length of entity reports varies because the display of OSS file pathnames might add a variable
number of lines to a report if the name is longer than a single line can display.
To control scrolling of Measure entity reports, use the PAGESIZE command. PAGESIZE lets you
specify the exact number of lines to display before another prompt is issued. For details, see
PAGESIZE (page 102).
Measure Support for ANSI SQL Names
SQL/MX objects such as tables and indexes have ANSI SQL names in addition to their underlying
Guardian names. Measure G11 and later PVUs can provide ANSI SQL names in certain Measure
output.
For more information on ANSI SQL names and SQL/MX, see the SQL/MX Reference Manual and
the SQL/MX Installation and Management Guide.
Handling of ANSI SQL Names
• ANSI SQL names are always displayed and entered in single quotes (') and are case-sensitive.
ANSI SQL delimited identifiers enclosed in double quotes (") are permitted inside the single
quotes. For example:
‘Catalog_12.Schema_34.Table_56’
‘Catalog_12."A.B.C PARTITION D$”” <>".Table_56’
NOTE: When an ANSI SQL name is passed as an argument to a callable procedure, it
should not be enclosed in single quotes. See Chapter 4: Measure Callable Procedures
(page 373).
• ANSI SQL names can refer to specific objects or to a set of objects within a specific schema
and catalog. If a catalog is specified, only files within that immediate catalog are included.
Files contained within schema subordinate to the specified catalog are not included.
Measure Support for ANSI SQL Names 149