SQL Error

General discussion on Zend Server for IBM System i
Post Reply
jc8150
Posts: 3
Joined: Wed Jul 15, 2015 5:23 pm

SQL Error

Post by jc8150 » Tue Oct 20, 2015 8:33 pm

We are writing an application that basically retrieves data from the is-series using the XML toolkit and it works great for the first transaction.
Performance degrades for subsequent transactions and finally the system times out at 30 seconds.

The debug.log file shows the following:

<jobtime><![CDATA[10/20/15 15:17:02.528837]]></jobtime>
<jobtext><![CDATA[QSQCONN CLEANUP 22503 QSQCONN CLEANUP 22503 Connection to relational database S067EC8T already exists.]]></jobtext>
</joblogrec>
</joblogscan>
<joblog job='XTOOLKIT' user='OBER4445' nbr='729995'>
<![CDATA[ge the RDB directory entry (CHGRDBDIRE) for the
5770SS1 V7R1M0 100423 Display Job Log COMMDEV4 10/20/15 15:17:02 Page 2750
Job name . . . . . . . . . . : XTOOLKIT User . . . . . . : OBER4445 Number . . . . . . . . . . . : 729995
Job description . . . . . . : ZSVR_JOBD Library . . . . . : ZENDSVR6
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
relational database you are connecting to so that at least part of the
communication information is different from what is specified in the entry
for S067EC8T. For APPC connections, the communication information is the
remote location, device description, local location, remote network
identifier, mode, and transaction program. For TCP/IP connections, the
communication information is the remote location and port identification.
SQ99999 Diagnostic 30 10/20/15 15:17:02.528928 QSQCLI QSYS *STMT XMLSERVICE ZENDSVR6 *STMT
From module . . . . . . . . : SQLFE
From procedure . . . . . . : SQLFreeEnv
Statement . . . . . . . . . : 11865
To module . . . . . . . . . : PLUGPERF
To procedure . . . . . . . : LOG_QUERY
Statement . . . . . . . . . : 5719
Message . . . . : Error occurred in SQL Call Level Interface
Cause . . . . . : A procedure call encountered an error. The error code is
10. Error codes are: 3 -- Program type out of range. 4 -- SQL data type out
of range. 9 -- Argument value not valid. 10 -- Function sequence error. 12
-- Transaction operation state not valid. 13 -- Memory management problem.
14 -- Maximum number of handles allocated. 15 -- No cursor name available.
16 -- Handle type for operation not valid. 17 -- Connection no longer
available. 21 -- Descriptor or descriptor information not valid. Recovery .
. . : Refer to the DB2 for i5/OS SQL Call Level Interface (ODBC) topic
collection in the Database category in the IBM i Information Center book for
a complete description of the error. Specifically, look at the procedure
that sent the error.]]>

Any input would be greatly appreciated.

Post Reply