×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Luis,
Thanks for the tip on CPA4259/QUERY_TIME_LIMIT, but we did not see that during a check yesterday
where we compared the report showing SQL 02000 and the job's log covering that time.
I checked WRKRPYLE and don't see an entry there.
From what I see that message would tend to put the affected job in message wait ?
I'd be VERY happy to find an explanation like that, and suspect something similar given we go > 100% CPU after noon.
As stated, I think these jobs have the most detailed log, but so far I've found "nothing".
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Wednesday, July 15, 2015 11:55 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Unexpected SQLSTATE returned from embedded SQL
Gary,
Do you have any message in the job's joblog? The only additional thing I could guess (big WAG) is that you had QAQQINI's QUERY_TIME_LIMIT exceeded (CPA4259). Again, big WAG
Regards,
Luis
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.