×
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.
Jack--
Thanks for the idea. We tried changing QSYSOPR profile DLVRY(*NOTIFY) before the flash, but it didn't take. The messages still broke.
I halfway think that the OS knows it was an abnormal termination and wants to make sure you know everything that was running when the system went down. Worst part is that about 2 steps later in the startup process messages start 'stacking up' in the message queue and you can respond to them when you get around to them. ):
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
.
.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Is it possible to change QSYSOPR profile default message delivery parm.
On Wed, Apr 30, 2014 at 9:19 AM, PaulMmn <PaulMmn@xxxxxxxxxxxxx> wrote (in part):
Is there any way to suppress *INFO messages, or put the [QSYSOPR] message queue into
*NOTIFY mode during an IPL from an Abnormal Termination?
Thanks! Our "ENTER" fingers will be overjoyed!
--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
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.