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

RE: Weird error involving a *USRQ in QTEMP

We have a customer who is experiencing a problem that I've never seen
before: he is getting a "Could not resolve to" message on a *USRQ that
we explicitly create in QTEMP when the application is launched. So far
as I can determine, all of our references to the *USRQ are fully
qualified.

Do you have message IDs? Job logs? Anything we can sink our teeth into
here? "Could not resolve to message" or "could not resolve to user queue?"
What instruction was being executed? What were the parameters
specifications? What were the parameter values?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A fanatic is one who can't change his mind and won't change the subject."
-- Winston Churchill


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