Re: qsys2.display_journal -- MIDRANGE-L

select * from table(qsys2.display_journal(
JOURNAL_LIBRARY *=>* '#MXJRN',
JOURNAL_NAME *=>* 'BPCS_ALL',
STARTING_RECEIVER_LIBRARY *=>* '#MXJRN',
*-- This was where you WERE putting *CURCHAIN* STARTING_RECEIVER_NAME
*=>* '*CURCHAIN',
*-- This is where it really belongs* STARTING_TIMESTAMP *=>*
'2025-04-04 07:00:00',
ENDING_TIMESTAMP *=>* '2025-04-04 08:00:00',
OBJECT_LIBRARY*=>*'ERPLXF', OBJECT_NAME*=>*'ZMA',
OBJECT_OBJTYPE*=>* '*FILE', OBJECT_MEMBER*=>*'*FIRST'))
where entry_timestamp >= '2025-03-25 13:42:00' and entry_timestamp <=
'2025-04-09 04:00:00'
;

On Thu, Apr 10, 2025 at 10:00 AM Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

What Bryan said...

As you have it now, it's getting all the journal entries and throwing out
the ones outside your time range.

If you include starting and ending timestamps, then it only reads the ones
you're interested in.

Should perform the same as the equivalent DSPJRN OUTPUT(*PRINT).

Charles

On Wed, Apr 9, 2025 at 3:08 PM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

since you are using a from/to time frame on the DSPJRN command you
should use it for the SQL function.

Starting_Timestamp => '2025-04-04 13:42:00.0000'
Ending_Timestamp => '2025-04-04 13:43:00.0000'

Greg Wilburn wrote on 4/9/2025 3:43 PM:

As slow as this works, I'm inclined to use DSPJRN

Takes 1 minute to return results for me
Meanwhile DSPJRN is nearly instant

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

Rob Berendt

Sent: Wednesday, April 9, 2025 4:02 PM
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Re: qsys2.display_journal

So, does anyone feel inspired enough to open a case with IBM asking

them

why I can put *CURCHAIN in the starting receiver library and it doesn't
error out but instead ignores it? But if I put *CURCHAIN in the

starting

receiver name it works fine?

On Wed, Apr 9, 2025 at 3:46 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

That was it! The dang thing gave me the results of the current

journal

receiver file and no error.

This works just fine:

select * from table(qsys2.display_journal(
journal_library=>'ASTJRN',
journal_name=>'ASTDTA',
starting_receiver_library=>'ASTJRN',
OBJECT_LIBRARY=>'ASTDTA',
OBJECT_NAME=>'OEORHDOH',
OBJECT_OBJTYPE=> '*FILE',
OBJECT_MEMBER=>'*FIRST')
)
where entry_timestamp >= '2025-04-04 13:42:00' and entry_timestamp <=
'2025-04-04 13:43:00'
order by entry_timestamp asc
;

Thanks all.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of

Rob

Berendt
Sent: Wednesday, April 9, 2025 3:31 PM
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxxxxxxxx>

Subject: Re: qsys2.display_journal

You're comparing a sql which looks like
DSPJRN JRN(#MXJRN/BPCS_ALL)
OBJ((ERPLXF/IIM *FILE))
RCVRNG(*CURCHAIN)
FROMTIME(040425 134200)
TOTIME(040925 040000)
To a command which looks like
DSPJRN JRN(#MXJRN/BPCS_ALL)
FILE((ERPLXF/IIM *FIRST))
RCVRNG(*CURCHAIN)
FROMTIME(040425 134200)
TOTIME(040925 040000)

Notice the FILE vs OBJ parameters? Not that it makes a difference but

it

might.

At first I thought that there was no need to use the named parameters
because if I get the library mixed up with the journal it errors out

hard.

But then I looked at it harder.
You're specifying *CURCHAIN for the library. That doesn't do squat.

It

should error out, but it doesn't. You need to specify *CURCHAIN for

the

journal receiver name, not the journal receiver library.
Try that.

On Wed, Apr 9, 2025 at 2:08 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Any ideas why the DSPJRN command displays my journal entries yet the
corresponding SQL statement will not?

This works:
DSPJRN JRN(ASTJRN/ASTDTA) FILE((OEORHDOH)) RCVRNG(*CURCHAIN)
FROMTIME('04042025' '134200') TOTIME('04042025' '134300')

This yields no results:

select * from table(qsys2.display_journal('ASTJRN',

'ASTDTA','*CURCHAIN',

OBJECT_LIBRARY=>'ASTDTA', OBJECT_NAME=>'OEORHDOH',
OBJECT_OBJTYPE=> '*FILE', OBJECT_MEMBER=>'*FIRST'))
where entry_timestamp >= '2025-04-04 13:42:00' and entry_timestamp <=
'2025-04-04 13:43:00'

If I change the Date/Time qualification to match the date in the

CURRENT

journal receiver, the SQL table function yields results. It's like

the

chaining isn't working.

[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:

gwilburn@xxxxxxxxxxxxxxxxxxxxxxx

1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
--
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.

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

Greg Wilburn
Director of IT
301.895.3792 ext. 1231
--
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.

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

Greg Wilburn
Director of IT
301.895.3792 ext. 1231

--

-- .
Bryan

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

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