×
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.
Dennis Lovelady wrote:
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?
About the only other things I can tell you about the QUSCRTUQ call is
that (as I said earlier) it's created explicitly in QTEMP, it's FIFO,
message length 132, initial 64 messages, increment 64 messages, public
*EXCLUDE (as if that made any difference for a *USRQ created in QTEMP),
REPLACE(*NO), *USER domain, *NO pointers.
I'm still waiting for the answers to the questions I had sent to the
end-user, that would tell me more about the error messages, as well as
whether or not the *USRQ actually got created.
--
JHHL
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.
midrange.com
