× 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 10-Jun-2014 11:57 -0500, rob@xxxxxxxxx wrote:
Should these receivers even be in QSYS?


That inquiry seems possibly to have been influenced by the lack of the OP having shown that the output was from a DSPJRNRCVA of a specific *JRNRCV, for which neither the receiver name nor its library name was included. There was no implication that the receivers were in the library QSYS, only that the *JRN [named QAUDJRN] associated with that Journal Receiver was in the library QSYS. If there was no such influence on the origin of that inquiry, or merely FWiW as more general interest, then...

Journal Receivers should never be created in QSYS. They are potentially /disturbing/ to install and both save and recovery [install] scenarios with both DSLO and SAVSYS. They are best avoided rather than trying to figure out how to resolve any issues that might result from having created any there; i.e. I doubt that the issues that they cause [due to naming and auto-creation with a different name], are either generally eliminated or otherwise easily overcome [most notably, the likelihood of eventual name collision causing problems with either user-managed or system-managed receiver management processing].


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.