Steve wrote...

>HP confirmed for me that DBOPENS are single-threaded.  I'm not a programmer,
>so my explanation may be distorted, but we had an Order Entry app that
>called a "Notes module" for every order line entered.  This module did a
>DBOPEN every time.  When we hit our busy season, this bottleneck became
>immediately apparent.  We found it (with HP's help) using SPT collector and
>analyzer.  It was a 5 minute fix, but definitely illustrated the single
>threaded nature of DBOPENS.

This is also a good reminder to all people playing with CGI programs
to provide live database data to web pages. If these short-lived CGI
programs do DBOPENs for each and every http request, this might not
be too painful for low hit rates, but could turn out to hurt when the
web usage gets more popular among users...

It's not just the single-threading, it's also the DBOPEN "overhead".

Lars.

PS... I will resist the temptation to mention my ongoing pleasant
experiments with Java servlets for dynamic web page content today,
but Java Web Server from Sun or Apache JServ *is* fun to play with.