Is a procedure that checks the VST's for transactions that stay open for a long time. It also estimates the used size of the bi file.
If transactions take too long or if the used bi size gets too large a mail is sent.
I'd like to upload the code to codeshare but I don't see how.
Hi Carl,
just add/attach to this forum, we'll then move in the right category
Hi Bernard,
No (didn't see previous post), Yes (having difficulties).
Could you indicate me where to attach. When posting a message I see
B for bold, I for Italic, U for underline, Spell Check and Quote original above the message
Preview, Post message and Cancel below
I don't see a way to attach or upload a file. I'm probably looking in the wrong place.
Hi Carl,
our error, when you add an entry now, you should see the "attach files" button below the message body.
I did get your email but could I ask you to try to attach so I know my change worked?
Thanks!
Hi, here is the transaction monitor source. It certainly needs more documentation. Reading the thread on the peg should help to understand the source.
Extract the zip file.
Edit tmon/src/transmon.i
run with
_progres -db ... -zn -p tmon/src/transmon.p
All comments welcome.
[View:~/cfs-file.ashx/__key/communityserver-discussions-components-files/19/tmon.zip:550:0]
can you point us to the thread on the peg?
The thread on the peg is http://www.peg.com/lists/dba/history/200710/msg00033.html .
It is mentioned in the source as well
The materials are posted here: