×
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.
My initial analysis of the end-user error that prompted this thread was
that a program in our QuestView application was having trouble resolving
by *LIBL to a *USRQ that another part of the application had placed in
QTEMP.
Then, this morning, looking at the problem after a fitful night's sleep,
I realized that nothing accessing a *USRQ would be forced to resolve it
by *LIBL. Looking at the joblog excerpt we were sent, and then at the
offending program, I realized that it was one of the few ILE programs in
QuestView (ILE C, in fact), and that it did qualify the *USRQ name.
Anybody have any idea why a *USRQ creation would fail, or why one might
get an MCH3401 while attempting to explicitly resolve a *USRQ in QTEMP?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
