>> problem 1 mixing db2_connect/db2_pconnect:Problem: There is a problem mixing db2_connect/db2_pconnect, IF you choose to use db2_pclose.More: Technically problem exists when you do not consistently use both matching (p)connect/(p)close pairs in all scripts.Work around: Do not use db2_pclose. Fix: This will need a fix in an future release of ibm_db2.

>> problem 2 *LOCAL-*DEBUG: Problem: PHP ibm_db2 version has no effect on *LOCAL-*DEBUG, as this function is purely IBM i DB2 PTFs. Fix: Most likely your machine DB2 PTFs are out of date, so please update to latest DB2 PTF group and retry test.

Thanks for the reply rangercairns. In all of our scripts we use either connect or pconnect exclusively. Typically, if the script has more than one call to the dB, we use pconnect and we don't ever use (p)close. I had read before about that causing issues. I will double check the PTFs, but our hardware guys say that we have the latest and the greatest.

Oh i see you already answered not using db2_pclose() in a previous post (i have to train myself to read backward in these things) ...

Another possibility comes to mind ... there is a old/bad version of the PASE libdb400.a driver that got accidentally shipped with Zend Server. I suggest you remove the stale version of libdb400.a and retry: