Pro*C Context - checking for status

Question

Does anyone know a function that I can pass an SQL context (the one allocated via EXEC SQL ALLOCATE CONTEXT) to and obtain both the connected status and last error encountered?
I'm in the process of writing an API to abstract some thread and database control away from our application code. One of its responsibilities will be to monitor each thread under its control and the associated DB context (the one allocated via EXEC SQL ALLOCATE CONTEXT) to insure that the database is connected. The thing is that I need a function to hand a context and see whether or not the database is connected and/or if any irrecoverable errors have occurred. Because the application is multi-threaded the API will not (and really can not) have access to the SQLCA of the calling thread. Because the way Pro*C compiles things, I would have to pass the SQLCA for the current function and thread back to the API, which is pointless and is a "stupid" contract (why must I hand the API my SQLCA...I shouldn't have to). However, I would have to guess that the context has enough information in it to at least give me the connected state and maybe the last error encountered in the context. What I need is a function to extract that information.
Thanks!

Answer 1

OK...so I did a little research myself, and I came up pretty short of anything except maybe the connection status. I can possibly get that by getting the OCIEnv * handle via an SQLLIB call then pass that to an OCIGetAttr call to get the "server" handle, then pass that to an OCIGetAttr call that will get the connected status. However, that only takes care of one of my issues.
So, since I don't like any of the solutions I've found so far, I'm contemplating setting up the threaded sqlca in a context that my API can access and requiring the API user to do something like:
#define sqlca (cxt->sqlca)
I'll pass the user cxt as part of the callback function so it'll be guarenteed thread safe.
This seems like it will work just fine...just an annoying step. In fact, I wish that Pro*C allowed the user to redefine sqlca in a better fashion than this. It really seems like multi-threading was an afterthought with things like this. Global sqlca gets stomped in multi-threaded apps, so they force you to define stack level sqlcas for every function.... That's bogus in and of itself, but now I need access to the sqlca in my API, and it'd be really nice to do something like:
EXEC SQL SET SQLCA apiGetSqlca()
And it would pull in that sqlca pointer everywhere. Worse yet, the Pro*C compiler assumes that the local SQLCA is not a pointer, and precompiles "&sqlca" all over the place (the reason the #define works in the first place). This makes it even more of a pain, because at least I could allow the API user to do something like: "sqlca = apiGetSqlca();" and have things work, but since sqlca can't be a pointer I'm up a creak with this too! Basically I have to redefine the symbol "sqlca" so that the pre-compiler points this symbol at the correct location where my API can access it.
Anyway...that's my rant, and currently the only solution I can find that will force all error conditions to wind up in a location that my API can access. Anyone else have any ideas?!?