× 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/28/13 10:01 AM, Vernon Hamberg wrote:
I'm wondering about default authority to QADBXREF - reason is, I
can't use it - just installed Data Studio along with RDi 9 - error
log reports the authority error.

What are the error messages and their context; i.e. from the spooled joblog? There have been past defects whereby the underlying database query feature incorrectly processes logical data authority, by performing improper references directly to the based-on file; i.e. it may not be the problem with the installed software accessing the wrong file, but the server improperly processing its request to access a catalog VIEW; e.g. SYSTABLES, SYSVIEWS, or SYSINDEXES. Given the specific failure, a search for a known defect and PTF can be performed.

Ours is set as USER DEF - the only thing set is Read - everything
else, including Opr, is blank.

The physical database files owned and controlled by the *DBXREF [the RDB file only consequentially owned and controlled by the feature, for conspicuous convenience] are all assigned *READ data authority. That is by design, and while there may be occasion to effect change the authority to those files [in rare situations whereby the QDBSRVXR and QDBSRVXR2 jobs do not hold locks], doing so is unsupported... and the System Database Cross-Reference feature may at any moment [and should at restart] /correct/ those authorities.


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.