BMCHIST_STEP table
Related topics
The BMCHIST_STEP table stores information about the job step. This table has information about the job itself, such as the job name, the product being run, timing information, and return codes.
The BMCHIST_STEP table contains information about completed runs of some of the BMC AMI Data for Db2 products. The updates are performed automatically by the following products if the BMC History updates are enabled:
- BMC AMI Copy
- BMC AMI Log Master
- High-speed Apply Engine
- BMC AMI Recover
- BMC AMI Utilities
Column name | Data type | Description |
|---|---|---|
JOBNAME | CHAR(8) | Name of the job submitted |
JOBID | CHAR(8) | Job Entry Subsystem (JES) job ID given to the job |
STEP_NBR | SMALLINT(2) | Step number within the job |
STEP_NAME | CHAR(8) | Step name within the job |
UTILNAME | CHAR(8) | Name of the utility:
|
UTILID | CHAR(16) | Utility identifier |
RESTART | SMALLINT(2) | Restart number |
AUTHID | CHAR(8) | USERID job under which job runs |
ROW_IDENTITY | BIGINT(8) | Identity column used to tie the BMCHIST_STEP with the BMCHIST_OBJECT |
BEG_TSTAMP | TIMESTAMP(12) | Time stamp when step started running |
END_TSTAMP | TIMESTAMP(12) | Time stamp when step completed |
ELAPSED | DECIMAL(9,2) | Elapsed time for step to complete (in seconds) |
TOTAL_CPU | DECIMAL(9,2) | Total amount of CPU used, being the sum of the GP_CPU and ZIIP_CPU |
GP_CPU | DECIMAL(9,2) | Amount of time in seconds used on regular central processors |
ZIIP_CPU | DECIMAL(9,2) | Amount of time in seconds used by zIIP processors If the central processors are not running at full speed, the utility scales ZIIP_CPU to match the speed of the central processors. zIIP CPU times reflect time only for enclaves that are created by BMC AMI Log Master. It does not include zIIP CPU times for enclaves that are owned by other processes, such as sort. |
ZIIP_ELIGIBLE | DECIMAL(9,2) | Amount of time in seconds for zIIP-eligible code to run on central processors because a zIIP processor was not available zIIP eligible times reflect time only for enclaves that are created by BMC AMI Log Master. It does not include zIIP eligible times for enclaves that are owned by other processes, such as sort. |
NORMALIZATION_FACTOR | SMALLINT(2) | The ratio of the speed of a zIIP processor to the speed of a central processor multiplied by 256 |
SERVICE_UNITS | INTEGER(4) | Number of service units |
CPU_MODEL | CHAR(4) | CPU model number |
MVS_SNAME | CHAR(8) | LPAR name |
STEP_RC | CHAR(5) | Return code of the job step |
NGT_SERVERS | SMALLINT(2) | Number of BMC AMI Utilities servers used |
TYPE_OF_RUN | CHAR(1) | Types of run:
|
REPORTONLY | CHAR(1) | Summary report only
A reorganization of the object does not occur. |
OBJ_COUNT | INTEGER(4) | Number of objects processed This number does not include partitions. |
SCHEMA_VERSION | SMALLINT(2) | Version of the data stored in the table |
Maintaining the BMCHIST_STEP table
When a utility completes successfully, it inserts a row into the BMCHIST_STEP table. You can control the expansion of this table by deleting old rows.
To delete old rows from the BMCHIST_Step table
To delete selected rows from the BMCHIST_STEP table based on the date that the utility was completed, use the following sample SQL statement:
FROM <creatorName>.CMN_BMCHIST_STEP
WHERE DATE < 'yyyy-mm-dd';
To delete selected BMC AMI Log Master rows from the BMCHIST_STEP table based on the date that the utility was completed, use the following sample SQL statement:
FROM <creatorName>.CMN_BMCHIST_STEP
WHERE UTILNAME = 'LOGMASTR' AND DATE(BEG_TSTAMP) < 'yyyy-mm-dd';