|
James H. H. Lampert wrote:
A little bit of information from the customer:
It only happens, so far, for one user. It's evidently sporadic
(wonderful!), but has happened twice. The next time it occurs,
we will hopefully get the <HELP> and <F9> on at least what
appear to be the key messages, and the contents of QTEMP
immediately after the crash.
<<SNIP>>
From MI, I am resolving a system pointer to the queue, in the
QTEMP context, immediately after it is created, and as long as
the system pointer I already have for QTEMP is good (and there's
at present no reason not to assume so, as it's used elsewhere,
and is BASPCO POS(65)),
the system pointer to the *USRQ should be good. And I am indeed enqueueing with an MI ENQ statement.
The program that does the dequeueing is in ILE C, with code in
the form:
_DEQ_Msg_Prefix_T d_msg_prefix;
_SYSPTR queue;
char bar[132];
. . .
queue = rslvsp(_Usrq, "FOO", "QTEMP", _AUTH_ALL);
. . .
#pragma cancel_handler(cancelHandler, 0)
. . .
while (deqi(&d_msg_prefix, bar, queue)) {
<here, the dequeued message is processed>
}
#pragma disable_handler
. . .
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.