BMCSYNC table

This topic describes the BMCSYNC table, which contains information about the status of the objects that the currently running utilities are accessing. The BMCSYNC table synchronizes and controls access to Db2 spaces by concurrently running BMC utility products. If you have more than one BMC utility installed, all of these utilities should share the same BMCSYNC table.

The utilities insert rows into the BMCSYNC table during the UTILINIT phase. While the job runs, the utilities update the table as the status of the object changes. The utilities delete rows from the BMCSYNC table during the UTILTERM phase.

Related topics

Common-utility-tables

Examples-of-CHECK-PLUS-jobs

Maintaining-common-utility-tables

CHECK-command-syntax

SQL-batch-execution-program

Common-utility-tables

BMCSYNC table

Column name	Data type	Description
UTILID	CHAR(16)	Utility identifier For BMC AMI Recover, this column is blank when a RECOVER UNLOADKEYS command creates the row and then a RECOVER BUILDINDEX command reads and deletes the row.
NAME1	CHAR(8)	Database name or creator name ¹ For DASD MANAGER PLUS, the value is the database name.
NAME2	CHAR(18)	Space, table, or index name ¹ For DASD MANAGER PLUS, the BMCSTATS utility always inserts the space name (limited to a maximum of 8 characters).
KIND	CHAR(2)	Type of object: IP (index partition) IX (index) TB (table) TP (table space partition) TS (table space) DD, DW (dynamic work file allocation) CI (copy information) RD (restart data set block)
PARTITION	SMALLINT	Partition number: Null or 0 for a single data set, nonpartitioned space Data set number for a multi-data-set, nonpartitioned space Partition number for a partitioned space BMC AMI Copy, LOADPLUS, UNLOAD PLUS, CHECK PLUS, DASD MANAGER PLUS, and REORG PLUS use null or 0 for any nonpartitioned space.
BMCID	SMALLINT	Internal identifier of the object DASD MANAGER PLUS does not use this column.
UTILNAME	CHAR(8)	Name of the executing utility: CHECK COPY STATS LOAD RECOVER REORG UNLOAD
SHRLEVEL	CHAR(1)	Degree to which utilities can share this object: Blank means that no status is requested, and any other utility can obtain any status. S allows sharing among any number of SHRLEVEL S utilities. X indicates that exclusive control is required. No other utility can run with SHRLEVEL X. For more information, see Executing BMC utilities concurrently.
STATUS	CHAR(1)	Status of the utility or object: Blank (indicates no processing has been done) C (for CHECK PLUS, indicates checked) L (for LOADPLUS, indicates loaded) U (for UNLOAD PLUS, indicates unloaded) R (for REORG PLUS, indicates reloaded) DASD MANAGER PLUS does not use this column.
XCOUNT	INTEGER	The number of rows or keys processed in the current phase. DASD MANAGER PLUS does not use this column.
DDNAME	CHAR(8)	Check, load, unload, or work ddname. DASD MANAGER PLUS does not use this column.
BLOCKS	INTEGER	Number of blocks for the check, load, unload, or work data set DASD MANAGER PLUS does not use this column.
ORIG_STATUS	CHAR(8)	The encoded representation of the original Db2 status of the space. For BMC AMI Recover, this column restores the Db2 status of a space after recovery, if necessary. DASD MANAGER PLUS does not use this column.
EXTRBA	CHAR(6)	(BMC AMI Recover only) log point at which this space was externalized BMC AMI Recover serialization logic uses this column. The other utilities do not use this column.
STATE	LONG VARCHAR	Restart information for the space For example, the STATE indicates the object state and sync information. DASD MANAGER PLUS does not use this column.
INSTANCE	SMALLINT	(BMC AMI Recovery Manager and BMC AMI Recover) the instance number of the current base objects (table and index) The default value is 1. The other utilities do not use this column.

¹ (LOADPLUS, UNLOAD PLUS, CHECK PLUS, and REORG PLUS) If the value for NAME1 exceeds 8 bytes or the value for NAME2 exceeds 18 bytes, NAME1 contains the DBID for the object. NAME2 contains the table OBID or index ISOBID of the object in hexadecimal format.

Sometimes, you might need to increase the size allocation of the BMCSYNC table space from the standard size that was allocated during installation. The following table lists the factors that you should consider when estimating the appropriate size allocation in various scenarios:

Scenario	Factors
You are processing a large number of partitions	Number of utilities that you are running concurrently Number of partitions that you are processing concurrently Number of files that you are allocating dynamically
You are loading or unloading XML data and the XML table space is partition-by-growth	Number of utilities that you are running concurrently Number of XML columns that you are loading or unloading Value of MAXPARTITIONS (in this scenario, a minimum of 256 partitions) Number of files that you are allocating dynamically
You are loading or unloading LOB data	Number of utilities that you are running concurrently Number of LOB columns that you are loading or unloading Number of partitions in the base table space Number of files that you are allocating dynamically

Do not run an IBM utility that attempts to manipulate data within the same objects on which a BMC utility is currently processing.
If BMCSTATS is processing multiple objects and encounters an object that is held by another utility, the BMCSTATS job issues a warning. The warning identifies the object and the utility that is using it. BMCSTATS continues processing the next object.
If BMCSTATS is processing an object and another utility requires exclusive control of that object, the other utility stops execution at initialization time.

BMCSYNC table

On this page