Do you know how to solve the following situation:
A user was in online mode and updating DB2 records.
He has forgotten to finish his updating transaction and has left the
office for a break (a few hours).
Is it possible that DB2-2/6000 can finish the transaction (rollback
or commit) automatically?
Does there exist DB2-parameters for configuring such behaviour?
For example to check periodically for transactions with no activity?
How can the application program or the DB2-administrator be informed
about such situations?
Thanks for replying.
Manfred Simon
CompuServe: 101376,2720
DB2 for AIX V2.1.1 ships with the governor application (in sqllib/adm/db2gov).
Type 'db2gov -help' for information on how it operates.
You can use the governor to setup the configuration which would issue a
FORCE to cancel an application which has spent too much time in the Unit of
Work. You can use the configuration file to specify which users and/or
applications this would be applicable to. You have to be careful not to
cancel legitimate long-running queries that you want to keep running.
When the governor take action (e.g. forcing an application or changing it's
priority), it is logged in the administrator-specified file.
--
Gene Kligerman
DB2 Development, IBM Software Solutions Toronto Lab
ge...@vnet.ibm.com
>DB2 for AIX V2.1.1 ships with the governor application (in sqllib/adm/db2gov).
>Type 'db2gov -help' for information on how it operates.
I think V2.1.1 is until now not available in Germany.
Could you send me the source code of this application by email?
Thanks!
Manfred Simon
10137...@compuserve.com