Re: Managing or purging remote journal receivers -- MIDRANGE-L

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

Subject: Re: Managing or purging remote journal receivers
From: Bryan Dietz <bdietz400@xxxxxxxxx>
Date: Wed, 6 Sep 2017 07:14:04 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

given those "deficiencies" in the SQL view, maybe a RFE is in order.

Bryan

Darren Strong wrote on 9/5/2017 10:56 AM:

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

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.