What record types are available
The following table summarizes items the Automation Reporter collects data for, subtypes, whether the data is collected cumulatively or in single intervals, and gives a brief description.
Data record type | Subtype | Interval data | Cumulative data | Description |
|---|---|---|---|---|
ACTN | ONLY | + | One record is collected per time interval; contains numeric counts for 10 different events within each record. | |
ALRT | ONLY | + | One record is collected per time interval; contains numeric counts for six different ALERT priorities within each record. | |
EVENT | ONLY | + | One record is collected for each entry in the Event Statistics Table. The record contains information such as the Text-ID of the event, how many items the event occurs in the Event Statistics Table, the number of times the event was handled, and so on | |
EXEC | ONLY | + | One record is collected for each EXEC in the SYSPROC and the SYSEXEC BLDL. The record contains information such as the EXEC name, the number of times the EXEC ran, abended and so on | |
RULE | ONLY | + | One record is created for each enabled, disabled, and suspended Rule. The record contains information such as the name of the Rule, how many times it fired, the Rule Set it belongs to, and so on. | |
RULESET | AUTO | + | One AUTO record is created every time the data is offloaded. If ten Rule Sets are active at the end of the interval, you then have one AUTO record and ten SET records. The record contains information about Rules automation such as which overall automation strategy the Rule Processor is using, whether HONOR MPF was turned on, and so on. | |
RULESET | SET | + | One SET record is created for every Rule Set that is active at the time the data is offloaded. If ten Rule Sets are active at the end of the interval, ten SET records are created. This record contains information about the Rule Set strategy (if an overall strategy of INDIVIDUAL is used in the Rule Processor), the number of Rules in the Rule Set, the fired count of the Rule Set, and so on. | |
RES | ONLY | + | One record is collected per time interval; contains information about how much private storage (above and below) was allocated, how many PQEs were created, and so on. | |
TAPE | LOCAL | + | One LOCAL record is created per interval If ten partners are participating in tape sharing activity with TapeSHARE at the end of the interval, you must save and collect the Automation Reporter TAPE: LOCAL records from each partner individually. Contains information about tape sharing activity such as the number of total device requests, the number of devices that were requested, and so on | |
TAPE | PLEX | + | One PLEX record is created per interval Within one PLEX record, if ten partners are active at the end of the interval, you have nine fields of data for each of the ten partners. Contains information about partner to partner communication such as how often a partner requested devices from the other partners, how long it took for a device to be shared, and so on. |
The following sections contain tables for each record type (and subtype where applicable) and briefly describe possible uses for the collected data.
Related topic