× 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.


  1.  Home
  2. MIDRANGE-L
  3. January 2019

Re: JOB_INFO when system job tables are really large.

Agreed.  To paraphrase, when the DB2 services work, they're very, very good, but when they are broke they are horrid.  :)

Maybe they need a way to store more robust error information that you could access with a variant of GET DIAGNOSTICS.


On 1/3/2019 8:19 AM, Rob Berendt wrote:
Joe,

I took your words to heart and tried again.

I removed the WHERE clause and put it into the UDTF parms. I also used
other UDTF parms and I'm getting further
SELECT JOB_NAME, JOB_STATUS, JOB_LOG_PENDING, J.*
FROM TABLE(QSYS2.JOB_INFO(
JOB_USER_FILTER =>'<redacted>',
JOB_STATUS_FILTER => '*OUTQ',
JOB_TYPE_FILTER => '*BATCH'
)) J
FETCH first 100 ROWS ONLY;

I can chunk this however I still thing IBM could improve the error
handling for this API

Rob Berendt



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.