The following is not a request it is a fyi.
If you knew this already, my apologies.
Also some may reply why did I not read the manual, well I did,
But my understanding was completely different to what is implied QSYSMSG

Are you under the impression that QSYSMSG gets all CRITICAL messages.
It is not so.
The ONLY messages sent to QSYSMSG is what is listed in an IBM manual.
This makes QSYSMSG as useful as the proverbial .....

We set up a monitor on QSYSMSG think Ah Ha the Critical messages are now
But we got this message on QSYSOPR, nothing on QSYSMSG.
Message ID . . . . . . : CPPEA56 Severity . . . . . . . :
Message type . . . . . :
Date sent . . . . . . : 13/03/12 Time sent . . . . . . :

Message . . . . : *Attention* Contact your hardware service provider
Cause . . . . . : A power or cooling subsystem error
Recovery . . . : Contact your hardware service provider and provide
following list of possible failing




Sent a question to IBM, this is the reply.
Concerning the MSG CPP EA56 and asking why it does not got to QSYSMSG Q .
The operating system decides where the CPPEAxx message should go. Some go
to QSYSMSG message queue, if it is created by the customer.
See url:
a list of message send to QSYSMSG

The CPPEA56 is not listed here.
The SRC definition has a special flag ' critical ' that will cause the
message to go to QSYSMSG. The customer can not change that attribute
OK back to the drawing board, and redesign the monitor to work over
QSYSOPR as well as the QSYSMSG Qs,
this is a farce, I should never have set up QSYSMSG, thanks IBM for not
very much.

Frank Kolmann

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by 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.