Hi Robert,
When I run that, it always returns zero - even if I set it to different numbers on our driver level - this is the driver for our programming language by Soft Velocity
...
This seems to be a Clarion bug / issue which we are going to have to get them involved in.
We do support standardized ODBC transaction calls with the ODBC driver via SQLSetConnectAttr (see: ODBC transaction isolation levels), otherwise you will need to use the SET OPTION SQL statement. Maybe this information will help diagnose the isolation level issue with SoftVelocity...?
You simply select to run a stored procedure, and it's frozen. But, if you open SCJVIEW and look at any locks - there are NONE at all.
It sounds like something internal to the database engine may be holding up the processing of the queries / stored procedure: can you supply the stored procedure definition?
If you can still open Sybase Central and still query other data / run sa_locks(), this implies that the database server is still doing some processing, so it may not be completely locked up at this point.
I am in the middle of opening a support incident with SAP
This sounds like a good plan for a way forward. If it's required, we have also have specialized diagnostic tools available internally in technical support that can help diagnose issues like this, but technical support will need to work with you in order to collect the information from the database server and provide the specialized diagnostic tool to you directly.
Regards,
Jeff Albion
SAP Active Global Support