SHRLEVEL

The SHRLEVEL option specifies the level of access that concurrently operating Db2 applications and utilities have to the target spaces during unload processing.

REFERENCE

SHRLEVEL REFERENCE allows objects to remain in read/write access during unload processing, maintaining consistency with a point-in-time image of the data.

BMC AMI Unload performs a drain of the writer on the objects that you are unloading. You can use the ULDPARMS QRETRY parameter to control how BMC AMI Unload handles drain wait times and drain retries.

If you are unloading from a full or incremental image copy (including a cabinet copy), BMC AMI Unload unloads only from image copies that are marked as SHRLEVEL REFERENCE in SYSIBM.SYSCOPY or, for a cabinet copy, the BMCXCOPY table.

CHANGE

If you are unloading from a table space, specify SHRLEVEL CHANGE to allow read/write access to the table space during unload processing. CHANGE is the default SHRLEVEL option.

If you are unloading from a full or incremental image copy (including a cabinet copy), BMC AMI Unload unloads from image copies marked as either SHRLEVEL REFERENCE or SHRLEVEL CHANGE in SYSIBM.SYSCOPY or, for a cabinet copy, the BMCXCOPY table.

CONSISTENT

This option tells BMC AMI Unload whether to attempt to maintain consistency with a point-in-time image of the data when using SHRLEVEL CHANGE.

You can set the default value during configuration or in a utility job using the +CONSISTENT parameter. For more information, see CONSISTENT.

CONSISTENT NO	BMC AMI Unload does not restrict access to the object. Be aware that specifying CONSISTENT NO might result in the following consequences: BMC AMI Unload might not process any updated pages in the buffer pool. If you run BMC AMI Unload on a Db2 object immediately following the creation of the data set for that object, any data involved might exist only in Db2 buffer pools, causing BMC AMI Unload to terminate. If BMC AMI Unload encounters any pages that have uncommitted data, it unloads the uncommitted data.
CONSISTENT YES	(Default) BMC AMI Unload maintains consistency with a point-in-time image of the data while enabling read/write access to the data. This option is ignored when you specify INFILE.

CONSISTENT NO

BMC AMI Unload does not restrict access to the object. Be aware that specifying CONSISTENT NO might result in the following consequences:

BMC AMI Unload might not process any updated pages in the buffer pool.
If you run BMC AMI Unload on a Db2 object immediately following the creation of the data set for that object, any data involved might exist only in Db2 buffer pools, causing BMC AMI Unload to terminate.
If BMC AMI Unload encounters any pages that have uncommitted data, it unloads the uncommitted data.

CONSISTENT YES

(Default) BMC AMI Unload maintains consistency with a point-in-time image of the data while enabling read/write access to the data.

This option is ignored when you specify INFILE.

QUIESCE

The QUIESCE option is only valid with CONSISTENT NO and should follow it in the SYSIN. QUIESCE is also a command so if this Unload option is on a new line in the SYSIN a syntax error will occur in the Unload statement.

This option tells BMC AMI Unload whether to externalize the unloaded table space’s pages from the Db2 buffer pool. If you specify QUIESCE without a value, BMC AMI Unload assumes QUIESCE YES. The following table describes the values that you can specify with QUIESCE.

You can set the default value during configuration or in a utility job using the +QUIESCE parameter. For more information, see QUIESCE.

Important

The QUIESCE clause cannot start on a new line in the SYSIN, this causes a syntax error.

QUIESCE YES	YES tells BMC AMI Unload to restrict access briefly to the object while BMC AMI Unload externalizes pages from the Db2 buffer pool.
QUIESCE NO	Specify this value if you do not want BMC AMI Unload to restrict access to the object and externalize pages from the Db2 buffer pool. Warning If you specify QUIESCE NO, BMC AMI Unload does not restrict access to the objects, nor does it externalize pages from the Db2 buffer pool. These actions might result in the following consequences: BMC AMI Unload might not process any updated pages in the buffer pool. If you run BMC AMI Unload on a Db2 object immediately following the creation of the data set for that object, any data involved might exist only in Db2 buffer pools, causing BMC AMI Unload to terminate. If BMC AMI Unload encounters any pages that have uncommitted data, it unloads the uncommitted data. Specifying the default You can specify the default for the SHRLEVEL CHANGE CONSISTENT NO QUIESCE command option in your BMC AMI Utilities configuration by setting the +QUIESCE parameter installation option. BMC AMI Unload was shipped with a default value of NO for this parameter. The command option overrides the default that is in the BMC AMI Utilities configuration.

QUIESCE YES

YES tells BMC AMI Unload to restrict access briefly to the object while BMC AMI Unload externalizes pages from the Db2 buffer pool.

QUIESCE NO

Specify this value if you do not want BMC AMI Unload to restrict access to the object and externalize pages from the Db2 buffer pool.

Warning

If you specify QUIESCE NO, BMC AMI Unload does not restrict access to the objects, nor does it externalize pages from the Db2 buffer pool. These actions might result in the following consequences:

BMC AMI Unload might not process any updated pages in the buffer pool.
If you run BMC AMI Unload on a Db2 object immediately following the creation of the data set for that object, any data involved might exist only in Db2 buffer pools, causing BMC AMI Unload to terminate.
If BMC AMI Unload encounters any pages that have uncommitted data, it unloads the uncommitted data.

Specifying the default

You can specify the default for the SHRLEVEL CHANGE CONSISTENT NO QUIESCE command option in your BMC AMI Utilities configuration by setting the +QUIESCE parameter installation option. BMC AMI Unload was shipped with a default value of NO for this parameter. The command option overrides the default that is in the BMC AMI Utilities configuration.

Specifying QUIESCE YES after CONSISTENT NO acquires a writer drain, externalizes the data pages, and then releases the drain. This process occurs before BMC AMI Unload reads the table space, so the unloaded data's consistency is not guaranteed.