This article is now available in our new knowledge base: IBM i - SQ99999 error code 10 filling up job logs
A DB2 operation may generate a message like this:
SQ99999 Diagnostic 30 QSQCLI QSYS *STMT QP2USER2 QSYS STMT
From module . . . . . . . . : SQLPRD
From procedure . . . . . . : SQLParamData
Statement . . . . . . . . . : 12682
To module . . . . . . . . . : QP2API
To procedure . . . . . . . : runpase_common__FiPvT2
Statement . . . . . . . . . : 5
Message . . . . : Error occurred in SQL Call Level Interface
Cause . . . . . : A procedure call encountered an error. The
error code is 10. Error codes are: 10 -- Function sequence error.
There may be thousands of these errors in the job logs for the Apache child jobs running PHP with calls to DB2 or the Toolkit. These errors are harmless, and do not indicate an actual crash, despite the level 30 applied to the message. They do fill up the logs with so many errors it can be difficult to find a relevant error when a crash does occur. Also, they can cause the logs to overrun the limits, causing a crash if page wrapping is not in effect. Also, if job logs are sent to spool files, the quantity of messages can be so great as to make a significant impact on storage capacity.
Zend Server for IBM i, running on any supported version of IBM i.
This issue has been resolved By IBM, APAR SE62545. Please apply the PTF appropriate for your version of the IBM i operating system: