HP3000-L Archives

November 1998, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bruce Toback <[log in to unmask]>
Reply To:
Bruce Toback <[log in to unmask]>
Date:
Mon, 23 Nov 1998 12:37:57 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Alfredo writes:

>Barry encountered an IMAGE status -3906 (which is not a very friendly
>thing, by the way), and he became worried when his application could not
>perform a DBOPEN.  Naturally, his first thought was that he had a database
>corruption.

This has hit my clients as well, on several occasions. Isn't there a
facility in TPI to intercept DBERROR and DBEXPLAIN? If not, can one be
added? Most programmers go to the trouble of calling one or the other in
order to speed up diagnosis of problems, but TPI errors just end up being
completely opaque. The customer looks in the IMAGE manual (it's an IMAGE
error, after all; it says so in the message), discovers that s/he's got
an *undocumented* error, and panics.

How about it, TPI vendors? Can we get real error messages through the
documented DBERROR and DBEXPLAIN interfaces?

-- Bruce


--------------------------------------------------------------------------
Bruce Toback    Tel: (602) 996-8601| My candle burns at both ends;
OPT, Inc.            (800) 858-4507| It will not last the night;
11801 N. Tatum Blvd. Ste. 142      | But ah, my foes, and oh, my friends -
Phoenix AZ 85028                   | It gives a lovely light.
btoback AT optc.com                |     -- Edna St. Vincent Millay
Mail sent to [log in to unmask] will be inspected for a
fee of US$250. Mailing to said address constitutes agreement to
pay, including collection costs.

ATOM RSS1 RSS2