Re: Possible automated troubleshooting

On Tue, Apr 5, 2016 at 10:10 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

So if you would have clicked on that link instead of giving be grief over
the semantics of using the word "api" instead of "service" you would have
seen the website for QSYS2.JOBLOG_INFO in the IBM Knowledge Center.

Rob, I didn't give you grief. But maybe I was unclear.

You presented two options: RECORD_LOCK_INFO and JOBLOG_INFO. Indeed,
both of these are accessible via SQL. *You* referred to the first one
as an SQL service and the second as an API. Whatever. I was just
repeating your terminology.

You made the following comment:

But the aforementioned joblog info api will tell you the particular row
you're looking for.

To me, that implies that the advantage of JOBLOG_INFO is that it tells
you the row you are looking for.

All I was saying is that RECORD_LOCK_INFO already gives you the row
you are looking for, in the RELATIVE_RECORD_NUMBER column.

I was actually trying to be nice and giving you the benefit of the
doubt, expressing this thought as "maybe I misunderstood, and you are
talking about something else besides the RRN of the locked record"?

John Y.