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



On 30-May-2010 23:54, Evan Harris wrote:

<<SNIP>>

I don't really like the fact that the receivers for a system
journal are in library QRECOVERY - I think I'd want to do
something about that, even if it was only forcing a journal
change to get the receivers into a more correct library. Where
do these receivers live on the other systems ?

On Mon, May 31, 2010 at 4:02 PM, PaultinNZ wrote:

<<SNIP>>

"WRKJRNA JRN(QSYS2/QSQJRN)" shows the current Receiver as
QSQRRN0248 in Lib QRECOVERY.

<<SNIP>>

The library QRECOVERY is chosen purposely by the OS, as the location for some of its receivers, if\when those receivers are not required for B&R. That is because the library QRECOVERY is purposely omitted from B&R. See:
http://archive.midrange.com/midrange-l/200803/msg01307.html

The concern I would have for the given setup is the receiver naming of QSQRRN####, which is unknown to me [from the perspective of the OPTION(01) of the OS. To me, that receiver appears to have been user-created, not system-created. In that case, only then would I be concerned that "the receivers for a system journal are in library QRECOVERY"; i.e. not for the system-created receivers, which are expected to reside there, until customized to reside elsewhere [except QSYS] under whatever [appropriate non-system] naming.

Regards, Chuck

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.