RE: SQL display_journal

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?