If z/TPFDF is
used for data storage, the information is kept in a z/TPFDF database composed
of index and detail files.
Figure 1 provides a high-level view
of the structure of the files in the z/TPFDF database. The
upper-level index files contain an entry for every day the collector
was started. Each entry points to a detail file the holds the detail
performance data for that day. Figure 1. CDCz/TPFDF file structure
There are as many as 36 index files, one for each processor. z/TPFDF file uf1t.asm contains
the DBDEF macro that defines the CDCz/TPFDF database and
is shipped with z/TPFDF.
The key field refers to the type of data for the entry. The different types of data structures
stored and the associated key field are shown in Table 1.
Table 1. Key field data types
Key (Hex)
Type of Data
X'80'
System messages
X'81'
System lists
X'82'
System blocks
X'83'
DASD / Pools
X'84'
DASD devices
X'85'
System VFA
X'86'
Subsystem VFA
X'87'
MPIF
X'88'
TAPE
X'89'
TCP/IP
X'8A'
I-stream
X'8B'
Subsystem messages
X'8C'
Subsystem user messages
X'8D'
LODIC resource priority classes
X'8E'
IBM MQ summary
X'8F'
IBM MQ queue detail
X'90'
IBM MQ channel detail
X'92'
LPAR utilization
X'93'
CDC record
X'94'
Static system information
X'95'
History data
X'96'
Channel utilization
X'97'
Enhanced channel utilization
X'98'
DASD service time
X'99'
LODIC utilization priority classes
X'9A'
Predefined user data
X'9B'
Common deployment files
X'9C'
Services data
X'9D'
z/TPF application manager for Java™ (JAM) data
X'9E'
Remote data store data
X'9F'
DASD metrics for each DASD module
Notes:
Data that is associated with keys X'83', X'93', and
X'95' is not stored on any database, but is written to the IBM MQ queue.
Data that is associated with keys higher than X'9B' is not written to z/TPFAR.
Data that is associated with key X'9F' is written to
the IBM MQ queue.
The format of the data in the z/TPFDF database is defined by the C/C++ data structures in the
cdcp_collect_lib.h header file.
You must enter the following commands the first time that you use z/TPFDF as the storage
mechanism for CDC:
ZUDFM DEF INIT
ZUDFM INIT FCA0
ZUDFM INIT FCA0
The first command builds the z/TPFDF tables. The
next two commands, which are the same, initialize the z/TPFDF database. Only
enter these commands when the databases are being set up for the very
first time, or when you want to delete all of the data and reinitialize
the database. In a loosely coupled system, these commands initialize
or delete and reinitialize the data for the whole complex.
Data that is associated with keys X'83', X'93', and
X'95' is not stored on any database, but is written to the IBM MQ queue.