Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see ALTER and BMC AMI Change Manager for Db2 13.1.

Sync tables


Execution inserts records into the sync table at various points throughout the processing of a worklist.

The records in the sync table for a particular work ID are used as progress indicators during execution of a worklist. In addition, these records are used during restarts to resume execution at the point of a failure. The sync records also contain information about the settings for authorization IDs at the time of failure.

The following table describes several of the columns in the sync table:

Column name

Description

WKOWNER

Owner of the work ID

WKNAME

Name of the work ID

SYNCCMD

Worklist command that is being executed at the time of the sync

SYNCSEQ

Worklist sequence number

SYNCAUTH

Current switched authorization ID (using the -AUTH command), if any

SYNCSETS

Current complete SET CURRENT SQLID command, if any

SYNCGLID

GLID in effect, if any

SYNCDATA

Variable text describing why the sync was recorded

SYNCSETP

Path for triggers and views

 The following table describes the conditions under which sync records are written.

Condition

Description

-AMS command

Execution generates a sync record before any AMS (IDCAMS ALTER, DEFINE, or DELETE) commands.

-AUTH command

An -AUTH command causes a sync record.

-BEGU command

For the Database Administration for DB2 and BMC Database Administration for DB2 solutions, Execution generates a sync record before a UOW is sent to an XIM initiator.

-SETS command

A -SETS worklist command causes a sync record. SYNCDATA contains the actual SET CURRENT SQLID command text.

-SETP command

A -SETP worklist command sets a path for triggers and views and executes before the creation of a trigger or a view.

-SQL DROP statements

Execution generates a sync record before any Db2 object is dropped.

-SYNC command

An explicit sync request causes the product to write the text on the -SYNC worklist command to column SYNCDATA along with the sequence number. -SYNC also causes a commit.

The name of an object in the -SYNC command might be truncated if the name contains up to 128 characters. To determine the full name of the object, review the worklist command that precedes the -SYNC command in the worklist.

-STOP command

A -STOP command is identical to a -SYNC command except that execution of the worklist is halted with return code 4.

-UOWC command

For the Database Administration for DB2 and BMC Database Administration for DB2 solution, Execution changes the BEGU command to a UOWC command when a UOW completes in an XIM initiator.

End of job

The product writes an end of job (EOJ) sync record at the end of the worklist. The EOJ sync record has a SYNCCMD of DONE and SYNCSEQ 999999.

Error

Any worklist error, such as an SQL error or utility failure, will cause an error sync record.

You can recognize error sync records by the characters EMSG in column SYNCCMD.

 You can delete all sync records in the sync table for a work ID at the end of a successful (no errors) Execution run by specifying the SYNCDELETE keyword in the AEXIN input stream. The sync tables require ongoing maintenance. For more information about maintaining sync tables, see Getting-started.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

ALTER and BMC AMI Change Manager for Db2 12.1