Allow offline backup to automatically force all Allow offline utilities such as backup, restore, rollforward to auconnections

Modern enterprise applications are often using connection pooling for database access. Connection pools are usually monitored by application servers, and dead connections are reestablished with minimal delays.
.
For offline backup operations, this leads to the need to shut down application (or at least to terminate the connection pool component) in order to reliably perform the backup. The reasons for that are explained in the following technote: http://www-01.ibm.com/support/docview.wss?uid=swg21636292
.
The suggested workarounds are all instance-level (e.g. restarting instance in restricted mode or disabling TCPIP communications), and, therefore, have some drawbacks in cases when the single instance hosts multiple databases.
.
As application servers have their own management tools and are usually running remotely from DB2, it is not very simple/feasible to integrate the required application management procedures (stopping the application or the connection pool) with DB2 automated backup operations.
.
A better approach would be to add the new option to the (offline) DB2 backup command, which would disallow new connections to the database, force all existing connections and deactivate the database before starting the backup.
.
The possible syntax: BACKUP DB name FORCE OFFLINE, where FORCE OFFLINE could be specified where ONLINE keyword is currently allowed (of cause, ONLINE and FORCE OFFLINE are incompatible options).
.
Automatic backup, enabled by setting AUTO_BACKUP=ON, should use this new BACKUP option in order to achieve 100% reliable backups, without ever hitting SQL1035N.