Skip to main content

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL

Can anyone give us assistance with this error? Our situation is as follows:
1. SQL 2012 DBs, RM/COBOL v 10.01 and InstantSQL used for LCS development.
2. Perform a READ (SELECT) call to TransactionPend table
3. Perform a WRITE (INSERT) call to TransactionPendClosed table using the same record as #2 above.
4. Receive 'Connection is busy with results for another hstmt'.

5.  If we did not receive the above error, Perform a DELETE call to TransactionPend (same table as #2) using the same record as #2 and #3.


How do I make the READ call release the connection handle? I've tried using the 'DROP' option without success.

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL
Your steps number 2 and 3 don't indicate what READ call or WRITE call do with respect to InstantSQL, so the situation is hard to diagnose, but I will try. The question you ask is answered by no, you don't want to free the connection handle since you'll need the connection to do the Write call, assuming that means doing an INSERT SQL statement for the same connection. You need to free the statement handle from the the read, which should be done with an SQL END QUERY statement for the QueryHandle returned for the "read", meaning the SQL PREPARE QUERY for the SQL statement used in the READ call. Have you reviewed your code flow against the Simple Query Flowchart in the InstantSQL help?

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL
Your steps number 2 and 3 don't indicate what READ call or WRITE call do with respect to InstantSQL, so the situation is hard to diagnose, but I will try. The question you ask is answered by no, you don't want to free the connection handle since you'll need the connection to do the Write call, assuming that means doing an INSERT SQL statement for the same connection. You need to free the statement handle from the the read, which should be done with an SQL END QUERY statement for the QueryHandle returned for the "read", meaning the SQL PREPARE QUERY for the SQL statement used in the READ call. Have you reviewed your code flow against the Simple Query Flowchart in the InstantSQL help?

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL
Your steps number 2 and 3 don't indicate what READ call or WRITE call do with respect to InstantSQL, so the situation is hard to diagnose, but I will try. The question you ask is answered by no, you don't want to free the connection handle since you'll need the connection to do the Write call, assuming that means doing an INSERT SQL statement for the same connection. You need to free the statement handle from the the read, which should be done with an SQL END QUERY statement for the QueryHandle returned for the "read", meaning the SQL PREPARE QUERY for the SQL statement used in the READ call. Have you reviewed your code flow against the Simple Query Flowchart in the InstantSQL help?

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL
I've updated my posting to provide more information.
I tried the SQL END QUERY as follows:
Read TransactionPend table
IF SQL RETURN OK
SQL END QUERY
Insert row to TransactionPendClosed table
Received Connection busy... error

 Using RM/Cobol with the WOW Extension Designer version 10.01 and InstantSQL I am attempt to read data from a SQL Server 2012 database. At times, but not in all cases I receive the following error: “Connection is busy with results for another hstmt”. According to another response, this error was fixed in release 9.1.2.1 of the Extend Software however we do not use Extend.


#SQLserver
#RMCOBOL
#InstantSQL
Did "Read TransactionPend table" read all the data, that is, fetched all rows until sql-EndOfData has been set to true or an error has occurred? Then the SQL END QUERY should be executed unconditionally.

Did you make sure the query handle specified in the SQL END QUERY statement is the one used in the read code?

Did the SQL END QUERY complete successfully?

Could there be another query statement outstanding, for example, a prior insert statement?

Have you tried SQL DESCRIBE QUERY on the query handle causing the error and inspected the information returned for the description?
Terms & ConditionsAccessibility statement