Subject RE: [IBO] no wait stored procedure?
Author IBO Support List
Post date 2014-06-09T12:46:37Z
The reason you use a separate TIB_Session, TIB_Connection, TIB_Transaction, TIB_Statement, etc. is so that you do not run into any multi-threading problems. You don't want two threads operating with or through the same handles because you can either corrupt your memory buffers or you will bump into protected resources that will make your operation become serialized anyway. By using totally separate resources for each thread context everything works properly in a true asynchronous manner.
 
Hope this helps,
Jason Wharton
 

From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]
Sent: Monday, June 9, 2014 12:03 AM
To: IBObjects@yahoogroups.com
Subject: RE: [IBO] no wait stored procedure?

Thanks Jason and Rob for comments. I will try making a new thread in my program which runs a procedure in the DB. I am doing this now in the program's main thread. 

I will use a separate connection, transaction and tib_dsql component. I cannot say why I must or should have these separate so would welcome an explanation. 

By not using isql in a scheduled bat file execution I will keep all maintenance tasks internal to the program.

Russell