×
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.
Well, it looks like the QjoRetrieveJournalInformation API might be capable
of returning a receiver directory. I had chosen to use the
QSYS2.JOURNAL_INFO view instead of this API, but I'll now be looking at
this API to see if it can do what I need. Apparently the API is much more
capable in this case.
___________________________________
Darren Strong
Dekko
From: Darren Strong <darren@xxxxxxxxx>
To: "midrange-l " <midrange-l@xxxxxxxxxxxx>
Date: 09/05/2017 10:21 AM
Subject: Managing or purging remote journal receivers
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I have setup a system to purge our regular journal receivers by date or
count. This system centers around the QSYS2.JOURNAL_INFO view, and the
QjoRtvJrnReceiverInformation API. Works great for regular journal
receivers. When I try to apply the same system to a remote journal, the
API doesn't return the next receiver in the chain, by design according to
the API documentation, so, I'm looking for a way I can identify and purge
these receivers.
___________________________________
Darren Strong
Dekko
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
