Technique
Problem
When a Reporting Server's agent is killed, whether manually or by some other Data Service Level setting such as connection_limit, does the query processing also stop?
Solution
The functionality of connection_limit is to stop the Reporting Server agents, not the Database Management System process. This behavior is dependent on the database. For example, in Oracle, the Database Management System process stops while in DB2, it continues to run.
Instead, try using the NONBLOCK mode. For example:
ENGINE [DB2] SET NONBLOCK {0|n}
This feature allows the adapter to cancel a query in response to a client request while the adapter is waiting on engine processing. This wait state usually occurs during SQL parsing, before the first row of an answer set is ready for delivery to the adapter or while waiting for access to an object that has been locked by another application.
Some adapters have a NONBLOCK setting that will allow such requests to be interrupted and canceled in the event the agent is stopped. To determine which adapters work with this setting, review the appropriate chapters in the Adapter Administration WebFOCUS Reporting Server Release 8206 DataMigrator Server Release 7710 manual and search for NONBLOCK to see if it is supported.