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



Al Mac Wheel wrote:

Error messages ought to go to MSGQs with most serious to QSYSMSGQ.

Just IMO and purely _personal_ opinion here, but QSYSMSG should be used for its documented purpose. IBM documents what goes into QSYSMSG and under what conditions it happens. Now, I'll grant that the messages documented for QSYSMSG tend to be "most serious"; but I would avoid sending anything there myself. A "most serious" application error, for example, might be inappropriate. (That might be totally unrelated to the above comment, but I wanted to make a distinction.)

QSYSMSG is an IBM object (and optional). As such, its operation and requirements are subject to change. IIRC & ICBW, it was possible in the distant past to gain a level of access to the QHST message queue as a message queue. But it was early on somehow changed to shield it from 'normal' access methods. (E.g., DSPMSG QHST fails.)

Non-IBM use opens the slim possibility of unintended locks at the wrong moments. Also, if a 'never-ending' monitor job doesn't get started or abends, then some other job that is sending non-standard messages might enter a bug-loop that fills and potentially wraps QSYSMSG, possibly causing loss of notification.

All that is just my opinion for general consideration... YMMV.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.