What data sets to keep when you quiesce a data sharing member

When you quiesce a member, you must keep the log data sets until they are no longer needed for recovery. Other members might need updates that are recorded on the quiesced member's log.

You must keep the BSDS, too, because it contains information that points to those log data sets. The BSDS is also needed for group restart. However, if you are confident that logs for the quiesced member are no longer necessary, because that member has been quiesced for a long time or is permanently quiesced, it is possible to delete the BSDS data sets. If you delete the BSDS data sets, expect the following message during group restart:

DSNR020I -DB2A csect-name START MEMBER DB1A, OR REPLY 'NO' or QUIESCED'

When you respond with QUIESCED, Db2 issues the following message:

DSNR030I -DB2A csect-name WILL CONTINUE WITHOUT THE DB1A MEMBER'S
LOG,
                          REPLY 'YES' OR 'NO'

In summary, you must do one of the following things to ensure that you have group restart capability:

Keep the quiesced member's BSDS data sets (thus avoiding the preceding WTOR messages).
Update your group restart procedure to ensure that operators know how to respond to the DSNR020I and DSNR030I messages.