The following table is a map of the 800-byte Audit call area, which consists of subfields (counters) that are maintained by C1MATCHx. You must initialize the P9AUDIT area with blank spaces before your first call to C1MATCHx.
When C1MATCHx is first called, all numeric fields in this area are set to zero. Thereafter, these fields are incremented as indicated by the field usage. You can, however, clear all or some of these fields to zero after each match attempt, so that you can report on the resource requirements of individual match attempts.
Each counter is a nine-digit packed number occupying five bytes, unless otherwise noted.
|
Positions |
Name |
Length |
Contents |
|---|---|---|---|
|
1-5 |
P9AZPX |
5 |
Database read operations for the ZIP Index file. |
|
6-10 |
P9ACTX |
5 |
Database read operations for the City Details file. |
|
11-15 |
P9ALCL |
5 |
Database read operations for the Locality file. |
|
16-20 |
P9ADTL |
5 |
Database read operations for the Street Details file. |
|
21-25 |
P9ACNT |
5 |
Database read operations for the County file. |
|
26-30 |
P9ASTR |
5 |
Database read operations for street information. |
|
31-85 |
Reserved |
55 |
|
|
86-90 |
P9ARZPX |
5 |
Database read requests (whether or not an I/O operation resulted) for the ZIP Index file. |
|
91-95 |
P9ARCTX |
5 |
Database read requests (whether or not an I/O operation resulted) for the City Details file. |
|
96-100 |
P9ARLCL |
5 |
Database read requests (whether or not an I/O operation resulted) for the Locality file. |
|
101-105 |
P9ARDTL |
5 |
Database read requests (whether or not an I/O operation resulted) for the Street Details file. |
|
106-110 |
P9ARCNT |
5 |
Database read requests (whether or not an I/O operation resulted) for the County file. |
|
111-115 |
P9ARSTR |
5 |
Database read operations for Street Name details. |
|
116-800 |
Reserved |
685 |
|