× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



My hypothesis about the timestamp being in previous/post receivers is
flawed.
This returns rows even though they are outside of that receiver's range.
starting_timestamp => '2023-04-02-00.00.00.000000',
ending_timestamp => '2023-04-05-07.34.59.999999'
And so do these:
starting_timestamp => '1800-04-02-00.00.00.000000',
ending_timestamp => '2900-04-05-07.34.59.999999'
And so do these:
starting_timestamp => '0001-01-01-00.00.00.000000',
ending_timestamp => '2900-04-05-07.34.59.999999'

Ooo, I found something. Stay tuned for a new thread...

On Wed, Apr 5, 2023 at 7:33 AM Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

If you want everything starting at the beginning to the end isn't it
rather pointless to specify a starting and ending timestamp especially when
you are selecting a single receiver?
The documentation says
If no starting timestamp is specified, *FIRST is used.
If no ending timestamp is specified, *LAST is used.
Maybe specifying dates like you are freaks it out since those dates start
in a different receiver and end in a different receiver than the one you
specify?

BTW, any attempt to try
starting_timestamp => '*FIRST',
ending_timestamp => '*LAST'
will result in:
SQL State: 22023
Vendor Code: -809
Message:[SQL0802] Data conversion or data mapping error.

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

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.