Measure Reference Manual

If the SQL journal file is under construction, bits 12 and 13 are both reported as ON.
Usage Notes
• MEASINFO calls ALLOCATESEGMENT to obtain a private extended data segment (segment
ID 10) for read traversal of the data file. The extended segment size is set to accommodate
two 30 KB (30,000-byte) read buffers and a 32 KB (32,000-byte) temporary buffer for
reconstructing records that span the read buffers.
MEASINFO opens the data file (unstructured, read only, nowait), issues a SETMODE 141 for
long transfers, and performs (30KB) READX I/O through the data file to find the information
requested.
• The length parameters bufsize and buflen must be greater than zero bytes and less than
32,001 bytes, or error 3203 (ERR^BADPARAMS) is returned.
• MEASINFO parameters are optional. However:
dfile
can be in the process stack segment or in an extended data segment. If omitted, error
3201 (ERR^MISSINGPARAM) is returned.
contab, bufsize, bytesret
are a group (that is, one cannot be passed without the other two, or error 3201
(ERR^MISSINGPARAM) is returned). contab can be in the process stack segment or in
an extended data segment. bufsize and bytesret must be in the process stack segment.
starttime, stoptime, interval
if passed, must be in the process stack segment.
entities, ctrspace
can be in the process stack segment or in an extended data segment. If either or both of
these parameters are passed, the parameter buflen must also be passed, or error 3201
(ERR^MISSINGPARAM) is returned.
buflen
must be in the process stack segment. If this parameter is passed, entities or ctrspace
must also be passed, or error 3201 (ERR^MISSINGPARAM) is returned.
If this parameter is used to limit the array size, the zero base of the array must be taken
into account. For example, a buflen of 4 (the zero base) does not allow for the return
of either entities or ctrspace information. A buflen of 8 allows for the return of
entities and ctrspace information for the CPU entity only. A buflen of 12 allows
for the return of CPU and process information, and so on.
• If any parameters are declared in an extended data segment, they must be in the same segment,
and the segment must be in use prior to calling MEASINFO.
• Parameters typed as extended references (such as dfile and contab) are expected to be
either in the process stack segment or in the same extended data segment. If any passed
parameters are part of an extended data segment, they must be in the same segment, and
the segment must be in use prior to calling MEASINFO.
• pTAL automatically handles segment management if you declare extended arrays (that is, for
dfile, contab, entities, and ctrspace). However, if you are allocating and
managing multiple extended data segments, you must ensure that the correct extended data
segment is in use prior to a call to MEASINFO. (Also, any returns by MEASINFO can occur
to only one extended data segment.)
• If an OSS journal file is under construction, both bits 14 and 15 of the settings field are
reported.
MEASINFO 397