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


  1.  Home
  2. MIDRANGE-L
  3. September 2003

Re: Getting rid of Journals

Oliver - response inline

Vern

At 11:06 AM 9/25/2003 +0200, you wrote:
Hi,

we have a bunch of journals on our 820 (V5R1) that I would like to get rid
of.

QUSRDIRDB  QSQJRN
RMSCHV42     QSQJRN
NULLID             QSQJRN
QSYS2              QSQJRN

Do I really need 4 instances of QSQJRN or can I consolidate into 1. And
how to do it?

QSQJRN is related to a collection - it is part of the local SQL catalog for a collection. It is there when someone used CREATE COLLECTION. The one in QSYS2 is the system-wide SQL catalog. Don't do snything with any of these.


QUSRBRM  QJ1ACM
QUSRBRM  QJ1AJRN2

We don't use BRMS. How do I get rid of these 2?

Looks like part of the product - take a look at objects in the library that start with QJ1A* and QJR1A* (journal receivers) - they're probably very small and are no problem. To get rid of them, DLTLICPGM. If BRMS is not installed, blow away the library.

QUSRRDARS QRLCJRN

Another one. What is this for?

I looked at the improved search site at IBM iSeries support and found that this is for Content Manager OnDemand. Could be left over, along with receivers, after DLTLICPGM. Installation manual for product is at <http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c415333302.htm>. If not using, DLTLICPGM once you check around ;-) whether it should be there.

Regards,

Oliver



As an Amazon Associate we earn from qualifying purchases.

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