We have a Native SQL PL procedure (we'll call it SP4) that calls another Native SQL PL procedure (SP5). SP5 can perform CONNECT to Remote DB2s as needed to access data there. Occasionally the call to SP4 results in -905 with a message like:
UNSUCCESSFUL EXECUTION DUE TO RESOURCE LIMIT BEING EXCEEDED, RESOURCE NAME = ASUTIME LIMIT = 000000000192 CPU SECONDS (000018000000 SERVICE UNITS) DERIVED FROM SYSIBM.DSNRLST01 Error in subsystem: DBnn.ppp *Error Calling SP5 DB2_USER_ID=user_id DB_APPL_ID=db2jcc_application< (certain values masked for anonymity)
When this happens the procedure (SP4) has only been executing for a second or two. So it seems highly unlikely it used up 192 CPU seconds.
Also when we get -905 the DBnn in the error message is always to the local DB2 where the call originated.
Any suggestions other than setting these to ASUTIME NO LIMIT?
------------------------------
StefanKolevSS&C
------------------------------