Gary L. Biggs <[log in to unmask]> wrote:

>bad data, couldn't possibly be MY code! ;) I know that Allbase
>provides a trace facility that they use in the lab that will show
>what is going on. Does anyone on the list know how to enable it? I'd

It's too late for Gary (he was able to find the problem using other means)
but I was able to dig up some information on a few JCWs that can help debug
Allbase. These were buried in some notes from 3 years ago. I thought other
people on the list might be interested.

There are 3 JCWs that can be used to change some operations in Allbase.
They can also be used to get trace information.

SETJCW HPSQLDEBUGFLAG=1
This is the main "switch". If it is not set or set to 0, none of the other
JCWs will be used.

SETJCW HPSQLDEBUGOPT=1
When set to 1, Allbase bypasses all index scans and forces serial scans.
You should use this option if you suspect corruption in an index file.

SETJCW HPSQLDEBUGCORE=1
When set to 1, Allbase displays a detailed trace of all internal
operations. You can enter DEBUG CORE 1 in ISQL to get the same result.

SETJCW HPSQLDEBUGCORE=2
Similar to the previous option i.e. Allbase displays a trace on internal
operations but in a short format (not as many details). Enter DEBUG CORE 2
in ISQL to enable it.

Again, it has been a long time since I have used these. I would think that
Allbase still recognizes these JCWs.

Francois Desrochers - Robelle Consulting Ltd
email: [log in to unmask]