How to search job log of an active job -- MIDRANGE-L

Using IBM i SQL Services like Jim O mentioned, you could use this as an example:
SELECT * FROM TABLE(QSYS2.JOBLOG_INFO('123456/QUSER/QZDASOINIT'));

Or as Joseph S mentioned, this also works:
DSPJOB JOB(JOB#/USER/JOBNAME) OUTPUT(*PRINT)

I would add as a caveat, when I do this I also makes sure to run
a CHGJOB, F4 and set the parms on a job like this before I
look at it.

Message logging:
Level . . . . . . . . . . . . 4
Severity . . . . . . . . . . . 00
Text . . . . . . . . . . . . . *MSG
Log CL program commands . . . . *YES

Respectfully,
Michael Mayer
IBM i on Power System Admin
ERMCO-ECI
2225 Industrial Rd
Dyersburg, Tennessee 38024
Office and OnCall: 731.676.4318
Cell: 518.641.8906
Email: michael.mayer@xxxxxxxxxxxxx<mailto:michael.mayer@xxxxxxxxxxxxx>
https://www.ermco-eci.com<https://www.ermco-eci.com/>
IBM i Personal Blog: https://ibmireference.blogspot.com<https://ibmireference.blogspot.com/>
"Success is not final. Failure is not fatal. It is the courage to continue that counts".

[cid:image001.gif@01D9AAA3.0777C060]

Today's Topics:

1. How to search job log of an active job (John Yeung)
2. RE: How to search job log of an active job
(Sizer, Joseph via MIDRANGE-L)
3. Re: How to search job log of an active job (dr2@xxxxxxxx<mailto:dr2@xxxxxxxx>)
4. Re: How to search job log of an active job (John Yeung)
5. Re: How to search job log of an active job (John Yeung)
6. Re: How to search job log of an active job (Jim Oberholtzer)
7. Re: Recursive DSPPGMREF (Sam_L)
8. Re: System Debugger (Sam_L)

----------------------------------------------------------------------

message: 1
date: Thu, 29 Jun 2023 13:20:44 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx<mailto:gallium.arsenide@xxxxxxxxx>>
subject: How to search job log of an active job

Is there a way to search the text of a job log while that job is still running?

Is there a way to output the job log of an active job to an output
file, spooled file, or stream file?

John Y.

------------------------------

message: 2
date: Thu, 29 Jun 2023 17:24:27 +0000
from: "Sizer, Joseph via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
subject: RE: How to search job log of an active job

DSPJOB JOB(JOB#/USER/JOBNAME) OUTPUT(*PRINT)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of John Yeung
Sent: Thursday, June 29, 2023 1:21 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: How to search job log of an active job

________________________________
CAUTION: This email originated from outside of the PENCOR network. Do not click on any links or open attachments unless the sender is known, and the content is verified as safe.
________________________________

Is there a way to search the text of a job log while that job is still running?

Is there a way to output the job log of an active job to an output file, spooled file, or stream file?

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

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

------------------------------

message: 3
date: Thu, 29 Jun 2023 13:25:21 -0400
from: dr2@xxxxxxxx<mailto:dr2@xxxxxxxx>
subject: Re: How to search job log of an active job

Why ? What are you looking for? It may be available a different way.

On 2023-06-29 13:20, John Yeung wrote:

Is there a way to search the text of a job log while that job is still running?

Is there a way to output the job log of an active job to an output
file, spooled file, or stream file?

John Y.

------------------------------

message: 4
date: Thu, 29 Jun 2023 13:37:52 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx<mailto:gallium.arsenide@xxxxxxxxx>>
subject: Re: How to search job log of an active job

On Thu, Jun 29, 2023 at 1:24?PM Sizer, Joseph via MIDRANGE-L
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:

DSPJOB JOB(JOB#/USER/JOBNAME) OUTPUT(*PRINT)

Thank you! That will do. I had a feeling there had to be something
simple. And now that you pointed me to that, I also notice that
DSPJOBLOG has output options.

John Y.

------------------------------

message: 5
date: Thu, 29 Jun 2023 13:49:14 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx<mailto:gallium.arsenide@xxxxxxxxx>>
subject: Re: How to search job log of an active job

On Thu, Jun 29, 2023 at 1:25?PM <dr2@xxxxxxxx<mailto:dr2@xxxxxxxx>> wrote:

Why ? What are you looking for? It may be available a different way.

Fair question. It varies. Sometimes I want to see if there was a
message relating to a particular file or program. Sometimes I want to
see if a particular command was issued. It could be just about
anything. Even just pure eyeball browsing. If the job log is long and
I want to jump to an arbitrary point within it, paging one screen at a
time can be painfully tedious.

John Y.

------------------------------

message: 6
date: Thu, 29 Jun 2023 13:34:52 -0500
from: Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx<mailto:midrangel@xxxxxxxxxxxxxxxxx>>
subject: Re: How to search job log of an active job

What not use the SQL service to query the job log and get specifically what
your looking for?

On Thu, Jun 29, 2023 at 12:49 PM John Yeung <gallium.arsenide@xxxxxxxxx<mailto:gallium.arsenide@xxxxxxxxx>>
wrote:

On Thu, Jun 29, 2023 at 1:25?PM <dr2@xxxxxxxx<mailto:dr2@xxxxxxxx>> wrote:

Why ? What are you looking for? It may be available a different way.

Fair question. It varies. Sometimes I want to see if there was a
message relating to a particular file or program. Sometimes I want to
see if a particular command was issued. It could be just about
anything. Even just pure eyeball browsing. If the job log is long and
I want to jump to an arbitrary point within it, paging one screen at a
time can be painfully tedious.

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

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.

--

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

------------------------------

message: 7
date: Thu, 29 Jun 2023 14:35:18 -0400
from: Sam_L <lennon_s_j@xxxxxxxxxxx<mailto:lennon_s_j@xxxxxxxxxxx>>
subject: Re: Recursive DSPPGMREF

Tim, are you a developer? Some other kind of computer professional? If
not, do you have a developer on staff who know SQL?

This code is all SQL and I think most developers could easily use it.

But I'll give you a few pointers:
1. Did you look at the readme on GitHub? You build the output table
first by running the SQL DDL.
2. You build the stored procedure by running it in SQL.
3. The test SQL gives several examples of how to run it.
4. You can run SQL on the IBM i in several ways.
a. Paste the SQL code into the Run SQL Scripts client in iACS.
b. Put the code into a source member on the IBM i and run it with the
RUNSQLSTM command.
c. The STRSQL statement gives you a green screen where you can enter
SQL statements.
d. There are probably other ways.

If you can't figure this out, then you probably need to hire a developer.

On 6/29/2023 8:00 AM, tim ken wrote:

Hi,

This seems very good but could you please also mention the steps how to run
below ( though something is there in readme file) :-

1) pgm.refs_Tbl.sql
2)pgm_refs.sql
3)pgm_refs_test.sql

are all these sqlrpgle programs or stored procedures , it would be nice if
you could please elaborate in more details it's attribute type so
accordingly it could be tried to execute based on it's object type and the
sequence like first create this with this member type (attribute type) then
this then this and check output finally like this.

------------------------------

message: 8
date: Thu, 29 Jun 2023 14:43:19 -0400
from: Sam_L <lennon_s_j@xxxxxxxxxxx<mailto:lennon_s_j@xxxxxxxxxxx>>
subject: Re: System Debugger

I still can't get the debugger to stop. Everything works as expected,
the source shows up, I set multiple breakpoints, and start it off. The
code animates and jumps around as the breakpoints are hit, but it never
stops until the program completes.

I was specifically using a stored procedure in this case and can debug
it the green screen debug so I've got it compiled correctly. And I've
had similar problems on RPG code.

If someone could confirm this experience on PUB400.COM<http://PUB400.COM> it would be
appreciated.

Thanks, Sam

On 6/25/2023 6:35 PM, a4g atl wrote:

You need to see the program is being run with the same user ID you
specified when starting the debugger. If the user profiles do not match, it
will not stop.

------------------------------

Subject: Digest Footer

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

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.

------------------------------

End of MIDRANGE-L Digest, Vol 22, Issue 551
*******************************************

The information in this email may be confidential. It is intended only for the person(s) named above. If you are not the intended recipient, please notify the sender and do not review, distribute, or duplicate this email.