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

You might be on the right track...

Except it works on a different box.

Is there a setting to control rather of not QSH spawns a different thread?

I can't imagine it actually spawns a job, since by definition, a job would
have a joblog.

Charles


On Fri, Aug 28, 2020 at 1:36 PM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com