Measure Reference Manual

Table 5 Measure Callable Procedures (continued)
PageDescriptionProcedureFunction
380Adjusts ZMS style structure
records to the MEASDDLS
MEAS_ADJUSTZMSRECORD_Adjusting record
formats
format with which an
application was compiled
381Allocates timer cells for
maintaining TCELLBUSY,
MEAS_ALLOCATE_TIMERCELLS_Maintaining fine
granularity timers
TCELLQUEUE, and
TCELLQBUSY timers
381Sets, resets, increments, or
decrements a TCELLBUSY,
MEAS_BUMP_TIMERCELL_
TCELLQUEUE, or TCELLQBUSY
timer
389Deallocates timer cellsMEAS_DEALLOCATE_TIMERCELLS_
436Retrieves timer values for one
or more TCELLBUSY,
MEAS_RETRIEVE_TIMERCELLS_
TCELLQUEUE, and
TCELLQBUSY timers
Measure Procedures Overview
Reading in Measure Records (DDL)
Measure DDL records change from PVU to PVU. New counters are always added to the end of
the existing Measure DDL records to ensure that applications using existing counters are not affected
by the addition of new counters.
Some simple coding practices can help you avoid compatibility problems with future PVUs. User
applications that request records through the programmatic interface should use a buffer large
enough to accommodate the new longer records (even if the new fields are of no interest). Because
Measure does not return partial records, applications written to use buffers of several thousand
bytes avoid compatibility problems in reading the DDL records.
Legacy and ZMS Style Records
In H01 and later PVUs, the internal representation of Measure data is in ZMS style records, and
any further enhancements will occur only in ZMS style. Yet the default style of records returned by
Measure APIs is still legacy.
To take advantage of future enhancements and improve application performance, it is advisable
to port existing applications to use ZMS style. To achieve this effect, use the templateversion
parameter (present in various procedure calls).
If your application continues to request legacy style records, Measure converts the data from its
internal representation to legacy style. This conversion affects legacy counter fields in several ways:
• If the legacy record has two versions of the same counter--one 32-bit version and one 64-bit
version (typically ending in -F)--the 64-bit field will invariably contain a value. The 32-bit field
will contain a value only if the value in the internal ZMS style record fits into 32 bits. If the
internal value does not fit into 32 bits, the 32-bit counter returned to the application has a
value of -1.
• MAX-QLEN counters are no longer maintained. Those fields are returned in legacy style records
with a value of 1.
• Fields that have been added to ZMS style records since the Measure G12 PVU are not available
to applications requesting legacy style records.
Measure Procedures Overview 375