From snippets I've picked up over the last few months, I have a feeling
there will be a number of you with "been there, done that" thoughts
running through your heads on this, so if any of you could shed some
light (or point me to the post/FAQ I've overlooked), it would be
greatly appreciated.
 
Q1: how do I avoid hitting the "MAX XACT"?  (related: how can I make
the MAX XACT something larger than 1, and be sure it stays that way?)
 
Usually, the indication I've reached this is that Access "stops", can't
alt-tab away from it, can't ctrl-break the current query, etc.  After
several minutes of this, I eventually bomb-out Access [ok, probably bad
thing to do, but...]  When I get back to a working session via WRQ, and
attempt to kill the session from ISQL using the "TERMINATE USER"
command, I end up locking up THAT session on the connect attempt.
SQLMON tells me that the DBEnvironment's maximum transaction limit has
been reached, so it won't attempt to map a few system related tables.
Meanwhile, the /load screen shows all access levels to be at 0%,
meaning nothing is happening, but the /lock screen doesn't detect any
deadlocks.  Since the initial connection wasn't via a "real" logon, but
rather an ODBC backdoor, there isn't a session to :ABORTJOB to clear
this idle user.
 
Q1a: once all the above has happened, I've noted that doing an ANSTOP
ARPA command to stop the ODBC link from the HP side leaves one process
in a rather odd state -- using VESOFT's somewhat enhanced SHOWPROC
output, the queue/priority of the process is -125! (not even an A/B/C/D
or E!)  The process name is garbage (???), but the pin still exists.
It seems at this point the only remedy is a shutdown/reboot, which I'd
rather not do, but do I have any choice at this point?
 
Q2: What is DBCORE INTERNAL ERROR 147 (DB-somesuch-ERR 13262)?
Usually, I get a message box with the message to write down "both
numbers above" repeated three times in the same message box.
 
Q3: I noted recently there was a discusion of how to update detail sets
on the HP from an ACCESS SQL statement.  Basically, it all boiled down
to Access's requirement that the set have a unique key, so I
restructured my dataset to have a unique key, re-wrote my data loader
to generate said unique keys, and now I find that I get a general "ODBC
Failed" error when I try to access the entire set.  (If I step through
the datasheet a page at a time, it seems to work OK, but when I press
the ">|" button to go to the last record, Access leaves me sitting with
an hourglass for about a minute then reports this error)  Likewise my
"archive query" which simply transferred records from the HP to the PC
aborts with the same message.  I'm not dealing with a massively large
set, only about 2000-3000 records of about 160 bytes.  Admittedly, this
will grow somewhat in the future (at about 200 records/day), but once
they are transferred to the PC, they can be deleted from the HP, which
leads into the next question:
 
Q4: Even with this "unique key", I still can't seem to delete or add
records from Access into the HP -- what have I overlooked?
 
Hopefully, these questions aren't complete stumpers, so I trust those
of you "with the t-shirt" can regale me with your mempories and horror
stories and other exciting things I can look forward to...
 
-----
Tom Emerson
Modular Data, Inc.
[log in to unmask] (here)
[log in to unmask] (preferred)
 
--
Tom Emerson
..can now be reached at:
   [log in to unmask] (here)
   [log in to unmask]    (preferred)