Re: SQL display_journal

I opened a case on these date ranges. Reply:

"IBM development answered that system date functions only extend to the
system date range of 2069.

Since the DISPLAY_JOURNAL function uses the QjoRetrieveJournalEntries API,
and that API uses system date functions, the developer says that any date
past 2069 would be unreliable. "

Based on this I would suggest defaulting the prompt to a timestamp using a
year of 2069. This should allow this journal scraping function to work for
the next 46 years. This is 10 years longer than I've been at my current
employer. Defaulting the year to something beginning with 20 should save
two keystrokes for those cases where the user does change the desired end
date.

On Tue, Apr 4, 2023 at 3:44 PM Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

Did you try:
'2099-12-31-24.00.00.000000'

Mit freundlichen Grüßen / Best regards

Birgitta Hauser
Modernization – Education – Consulting on IBM i

IBM Champion since 2020

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
„Train people well enough so they can leave, treat them well enough so
they don't want to.“ (Richard Branson)

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Gerald Magnuson
Sent: Tuesday, 4 April 2023 19:16
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: SQL display_journal

I had the same behavior (ending ts is earlier than start) when I did:
starting_timestamp => '0001-01-01-00.00.00.000000',

ending_timestamp => '2099-12-31-23.59.59.999999'

On Tue, Apr 4, 2023 at 11:31 AM <smith5646midrange@xxxxxxxxx> wrote:

To add more confusion, I just changed to the following



starting_timestamp => '2023-04-02-00.00.00.000000',

ending_timestamp => '9999-12-31-23.59.59.999999'



and now I am getting an error that the ending timestamp is earlier
than the starting_timestamp.



We are running V7.4 and they keep the PTFs current.



From: smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx>
Sent: Tuesday, April 4, 2023 11:35 AM
To: 'Midrange Systems Technical Discussion'
<midrange-l@xxxxxxxxxxxxxxxxxx

Subject: SQL display_journal



I am trying to pull data from a journal receiver using SQL using that
starting_timestamp and ending_timestamp parms. I was not getting any
results so I tried switching my dates to be from
0001-01-01-00.00.00.000000 to 9999-12-31-23.59.59.999999 to include

everything in the receiver.

When I use the below statement with the starting and ending timestamp,
I get
0 rows returned.

select *
from table (qsys2.display_journal ('##JOURNALS',
'IPLIBD',
object_objtype => '*FILE',
starting_receiver_name =>
'IPLIBD3277',
starting_receiver_library =>
'##JOURNALS',
ending_receiver_name =>
'IPLIBD3277',

ending_receiver_library =>
'##JOURNALS',
starting_timestamp =>
'0001-01-01-00.00.00.000000',
ending_timestamp =>
'9999-12-31-23.59.59.999999'
)
) ;



However, when I use the below statement WITHOUT the starting and
ending timestamp, I get lots of rows returned.



select *
from table (qsys2.display_journal ('##JOURNALS',
'IPLIBD',
object_objtype => '*FILE',
starting_receiver_name =>
'IPLIBD3277',
starting_receiver_library =>
'##JOURNALS',
ending_receiver_name =>
'IPLIBD3277',

ending_receiver_library =>
'##JOURNALS' )
) ;



What am I overlooking?

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


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