RE: QSH db2 command and qsys2.joblog_info() - exit status 1 -- MIDRANGE-L

Subject: RE: QSH db2 command and qsys2.joblog_info() - exit status 1
From: Rob Berendt <rob@xxxxxxxxx>
Date: Mon, 31 Aug 2020 11:37:34 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Perhaps I read Bryan's response wrong.
When I ran his command I got
520158/ROB/QP0ZSPWP
Which basically does say that if you're looking for a way to get the joblog from your job then using QSH to fire off the SQL is not the way to do it.
You might want to try RUNSQLSTM or some of the homegrown EXESQL or
RUNSQL SQL('CREATE TABLE QTEMP.LOGLOG AS (Select * from table(qsys2.joblog_info(''*''))) with data') COMMIT(*NC)

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSH db2 command and qsys2.joblog_info() - exit status 1 , Charles Wilt

This mailing list archive is Copyright 1997-2025 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.