DSNJ310I (A)SYNCHRONOUS ARCHIVE LOG COMMAND QUIESCE PROCESSING STARTED FOR MAXIMUM OF xxx SECONDS
Explanation
An -ARCHIVE LOG command with the MODE(QUIESCE) option has been accepted by the Db2 subsystem. The quiesce processing has commenced.
System action
The Db2 subsystem will attempt to stop all updates to Db2 resources within the time period specified in the message. Users/jobs operating on the Db2 subsystem will be allowed to reach a point of consistency (commit point) before being blocked from further update activity. Jobs and users will be suspended until they are released by Db2 following the initiation of the offload processing. If the Db2 subsystem can effectively block all users from performing updates before the maximum specified time, the offload will be initiated immediately, and normal processing will be resumed.
- If the word SYNCHRONOUS is displayed, then the invoker used the WAIT(YES) option. This means that quiesce processing will be synchronous to the user; that is, the user can enter additional Db2 commands, but the commands will not be processed by the Db2 command processor until the quiesce processing has ended.
- If the word ASYNCHRONOUS is displayed, then the invoker used the WAIT(NO) option, or did not specify the WAIT option. This means that quiesce processing will be asynchronous to the user; that is, control will be returned to the invoker as soon as the quiesce task has been started. Thus, the Db2 command processor will accept - and process - any new Db2 commands while the quiesce task is running.
This message will be followed by message DSNJ311I or DSNJ317I.
Operator response
No operator response is necessary. However, it can be expected that users and jobs using Db2 resources will be suspended (queued) by Db2 through the duration of the specified time interval, or until the Db2 subsystem can be certain that all update activity has been effectively blocked. At some point, this message will be followed by the DSNJ311I message or DSNJ317I message.