SEO

#1 (**permalink**) 04-09-2008, 11:25 PM

Progress 7.3/8.2, DB 7.3E16 (NLM)

We start our application via precompiled runtime.r module ('-p
runtime.r' within .pf file), calling then the main startup
immediately. Two problems exist here.

1. When DB connection is lost, some users fall into OS, others fall
into Progress editor

2. When user presses CTRL-BREAK during application execution,
application tries to call runtime.r again. But if there's an active
transaction before she presses CTRL-BREAK, calling runtime.r again
will fail and the DB crashes with SYSTEM ERROR: tmstrt: transaction
already active. (434)

The former isn't the main problem. The latter may cause DB damage, so
it's considered red alert. Tried to implement the istrans.p scheme on
runtime.r but this won't work. Seems the client doesn't see the
already active transaction but the DB does.

Is there another workaround? Database is the latest NLM version IMHO
(and we have to use NLM), clients are either V7.3 or V8.2 (some
running via tcp/ip on Windows terminal server).

All help is greatly appreciated.

- Michael

#2 (**permalink**) 04-09-2008, 11:25 PM

mk@isp.hem.de (Michael Kochendoerfer) wrote in message news:<762faa69.0307142318.6f778ee7@posting.google. com>...

hi mike,

the problem is all the bad habits your users picked-up
ctrl-break resets and such violent exits
force crash recovery what did you expect ???

a few simple solutions are -
to build a loop that your users can leave it/transaction with esc
or exit and undo buttons to do the same.

and brake those users hands
they only understand force !!!

> Progress 7.3/8.2, DB 7.3E16 (NLM)
>
> We start our application via precompiled runtime.r module ('-p
> runtime.r' within .pf file), calling then the main startup
> immediately. Two problems exist here.
>
> 1. When DB connection is lost, some users fall into OS, others fall
> into Progress editor
>
> 2. When user presses CTRL-BREAK during application execution,
> application tries to call runtime.r again. But if there's an active
> transaction before she presses CTRL-BREAK, calling runtime.r again
> will fail and the DB crashes with SYSTEM ERROR: tmstrt: transaction
> already active. (434)
>
> The former isn't the main problem. The latter may cause DB damage, so
> it's considered red alert. Tried to implement the istrans.p scheme on
> runtime.r but this won't work. Seems the client doesn't see the
> already active transaction but the DB does.
>
> Is there another workaround? Database is the latest NLM version IMHO
> (and we have to use NLM), clients are either V7.3 or V8.2 (some
> running via tcp/ip on Windows terminal server).
>
> All help is greatly appreciated.
>
> - Michael

#3 (**permalink**) 04-09-2008, 11:25 PM

The first problem can be easily addressed

Add the -rr option to the startup script and make sure that you have
"quit" as a command in the startup procedure so that they fall to the
right place.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Transaction problems V7/V8