Kbase P173786: How to determine transaction scope at runtime
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/12/2010 |
|
Status: Verified
GOAL:
How to determine transaction scope at runtime
GOAL:
How to tell where a transaction started at runtime
FACT(s) (Environment):
<file-name> in use by <user> on <tty>. Wait or choose CANCEL to stop. (2624)
All Supported Operating Systems
OpenEdge 10.1B
FIX:
OpenEdge Release 10.1B introduced a new log entry type named '4gltrans' which allows tracking when a transaction BEGINS, ENDS or is UNDONE. This can be used like any other log entry type that is associated with the -clientlog startup parameter or through the LOG-MANAGER system handle. Below is an example of implementing this log entry type both on the command-line (at startup) and through the LOG-MANAGER session handle:
<client startup>
-clientlog <logfilename> -logentrytypes 4gltrans -logginglevel <n>
<log-manager>
LOG-MANAGER:LOGFILE-NAME = "<logfilename".
LOG-MANAGER:LOG-ENTRY-TYPES = "4gltrans".
LOG-MANAGER:LOGGING-LEVEL = <int>.
There are two levels at which logging is performed:
Level 2 - Logs when a transaction BEGINS and ENDS or when a transaction is UNDONE
Level 3 - Logs when a transaction OR subtransaction BEGINS, ENDS or is UNDONE
The logged data for these events looks similar to the following:
BEGIN TRANS
BEGIN SUB-TRANS
UNDO SUB-TRANS
END TRANS