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

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

could it be that there were no joblog? i think that the the QSH command when run from a command prompt will spawn a new job. that job does not have a joblog.

Try this:
QSH CMD('db2 "values job_name" >> loglog.txt')

you should see a new job.

Bryan

Charles Wilt wrote on 8/28/2020 12:52 PM:

Nobody has any thoughts?

So more info...

From an interactive QSH, (on the problem box)

db2 "select * from table (qsys2.joblog_info('*'))"

returns
0 RECORD(S) SELECTED.

Works fine on another box...

Charles

On Thu, Aug 27, 2020 at 2:23 PM Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Any thoughts as to why this would return with an exit status of 1 and an
outfile that says "0 RECORD(S) SELECTED."?

QSH CMD('db2 "select * from table (qsys2.joblog_info(''*''))" >
loglog.txt')

running
select * from table (qsys2.joblog_info('*'))

in STRSQL returns data in the same 5250 session...

This works fine
qsh cmd('db2 "select * from sysibm.sysdummy1" > test.txt')

And the problem command works fine when run on a different system...

Thanks!
Charles

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.