Db2 commands issued by BMC AMI Copy for read and write databases
Status changes made in the UTILINIT phase (R/W databases)
Scenario 1 | ||||||
---|---|---|---|---|---|---|
SHRLEVEL | Initial status 3 | FULL option | -STOP | -START RO | QUIESCE | DRAIN |
NONE | Any | YES or NO | Yes | No | No | No |
REFERENCE | UT | YES or NO | Yes | No | No | No |
REFERENCE | RO | YES or NO | No | No | Yes | No |
REFERENCE | RO,COPY | YES or NO | No | No | See note 4 | No |
REFERENCE | RW | YES or NO | No | Yes | Yes | No |
REFERENCE | RW,COPY | YES or NO | No | Yes | See note 4 | No |
CHANGE | Any | NO | No | No | See note 5 | No |
CONCURRENT STARTRO or LOCKTABLE | Any | YES or NO | No | Yes | No | |
CONCURRENT DRAIN | Any | YES or NO | No | No | No | Yes |
1 The information in this table does not apply to the table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, and DSDNB01.SYSDBDXA.
2 For concurrent partition or data set copies, only the first copy utility to access the space (based upon BMCUTIL table entries) modifies the status. QUIESCE BEFORE tells to issue a QUIESCE during the UTILINIT phase when the status is not STOP or COPY.
3 This is the initial status of the target table space or partition.
4 If there are pages in the Db2 buffer, or if this is a data sharing subsystem, turns off COPY-pending and issues a QUIESCE.
5 If SLCHGQSC=YES and has an issue identifying a valid LRSN, will QUIESCE; otherwise, it will not QUIESCE. If SLCHGQSC=YES and SOFTQUIESCE=YES, it performs the DRAIN function instead of a QUIESCE. Also, DRAINWAIT, DRAINDELAY, and DRAINRETRY apply in this case.
6 SHRLEVEL CONCURRENT copies restart the space in RW at the end of the UTILINIT phase unless another BMC utility has already started the space in RO or the space was originally in COPY-pending status.
7 issues the -START RO command only when READONLY is set to STARTRO. Otherwise, uses LOCK TABLE.
The information in the UTILTERM phase table applies to both table spaces and index spaces with the exception that RESETMOD NO is always used for index copies.
Status changes made in the UTILTERM phase (R/W databases)
Scenario 1 | ||||
---|---|---|---|---|
SHRLEVEL | Initial status 3 | RESETMOD | -STOP | -START 4 |
NONE | Any | NO | No | Yes |
NONE | Any | YES | No | Yes |
REFERENCE | UT | NO | No | Yes |
REFERENCE | UT | YES | No | Yes |
REFERENCE | RO | NO | No | No |
REFERENCE | RO | YES | Yes | Yes |
REFERENCE | RW | NO | No | Yes |
REFERENCE | RW | YES | Yes | Yes |
REFERENCE | RW,COPY | NO | No | Yes |
REFERENCE | RW,COPY | YES | Yes | Yes |
CHANGE | Any | NO | No | No 5 |
CONCURRENT | Any | NO | No | No 6 |
1 The information in this table does not apply to the table spaces DSNDB06.SYSCOPY, DSNDB01.SYSUTILX, DSNDB01.DBD01, and DSDNB01.SYSDBDXA.
2 For concurrent partition or data set copies, only the copy utility completing last (based upon BMCUTIL table entries) modifies the status. QUIESCE AFTER tells to issue a QUIESCE during the UTILTERM phase when the status of the space is not STOP or COPY.
3 This is the initial status of the target table space or partition.
4 When is running concurrently with another BMC utility on the same space, the last utility puts the space back to its initial status.
5 If the RESETCHG installation option is set to YES, SHRLEVEL CHANGE performs a DISPLAY and compares the original status information, and if is the last utility to relinquish control of the space, the space is returned to its initial status.
6 SHRLEVEL CONCURRENT performs a DISPLAY and compares the original status information. If it is different, a START is issued at the end. If the status is COPY-pending, SHRLEVEL CONCURRENT might perform a START.