Tweet
QIBM_QZDA_SQL2 Exit Program Questions -------------------------------------------------------------------------------- We have written a home grown application to monitor the basic network exit points. We have discovered, much to our dismay, that the QIBM_QZDA_SQL2 Exit Program is slowing down our JDE OneWorld reports. We use the AS/400 as a DB2 backend. We are running V5R3M0. After watching the process with the database monitor and stub checking, we notice that the QIBM_QZDA_SQL2 Exit Program is being called for each I/O!! When we remove the exit program the 20 hour job goes down to 8 hours. The QIBM_QTMF_SERVER_REQ exit point has the ability to use a return code (#2) that does the following Always allow this operation identifier: Allow this operation identifier unconditionally for the remainder of the current session. This operation identifier will not call the exit program again. The documentation for the QIBM_QZDA_SQL2 exit point says that anything other than the X'F0' value will allow the operation. Does anyone know if the same return code values that work for QIBM_QTMF_SERVER_REQ also work for QIBM_QZDA_SQL2? Failing that, does anyone know a way around our performance problem? Thanks, Chris