What does your OPENINFO string look like for the group the server is in? And how are you building the client? Are you passing the -r switch to buildclient? Is the client a native client or workstation client?
It sounds like a DB2 problem, but let's see the details of the above questions first.
Oracle Tuxedo Chief Architect
the client is a native client, it is built with buildclient, the -r parameter is used.
The OPENINFO in the Tuxedo config file is:
###xxx### are placeholders.
Thanks for looking at my question.
I'm not sure what is happening in your application, but it could be related to the DB2 SUSPEND_CURSOR option, which is documented at IBM Knowledge Center
This "Specifies whether cursors are to be kept when a transaction thread of control is suspended. Valid values are T, F, or no value. TP monitors that suspend a transaction branch can reuse the suspended thread or process for other transactions. If SUSPEND_CURSOR is off, all cursors except cursors with hold attributes are closed. On resumption of the suspended transaction, the application must obtain the cursors again. If SUSPEND_CURSOR is on, any open cursors are not closed, and are available to the suspended transaction on resumption. A value of T means that SUSPEND_CURSOR is on; a value of
F means that SUSPEND_CURSOR is off; This parameter can be used to override the setting derived from a specified TPM value. If this parameter is not specified, the default value of F is used."
Although you don't specify this parameter in your OPENINFO and the default is "F", perhaps there could be some other way for the DB administrator to override this value. You may want to experiment with "DECLARE xxxx CURSOR WITH HOLD" in your program to see if the WITH HOLD clause will produce the desired behavior.