|
I believe that years ago when I created min eI read something that said the QSYSOPR message queue must be created in QSYS - if you want OS/400 to use it anyway ! :-) ...Neil "Jim Franz" <franz400@triad.rr.com> Sent by: owner-midrange-l@midrange.com 2001/04/13 15:45 Please respond to MIDRANGE-L To: <MIDRANGE-L@midrange.com> cc: Subject: Re: QSYSMSG (was:Re: Help w/ AS/400) while we are figuring out if it is "instead of" qsysopr, i need to add the question: Does it have to be in QSYS? Can it be in QUSRSYS? jim ----- Original Message ----- From: <MacWheel99@aol.com> To: <MIDRANGE-L@midrange.com> Sent: Friday, April 13, 2001 3:04 PM Subject: Re: QSYSMSG (was:Re: Help w/ AS/400) > Time for another clarification. > > In one of my IBM classes on Sys/Admin/Op > I thought the instructor said that this stuff went to BOTH QSYSMSG AND > QSYSOPR ... that the QSYSMSG was like a subset of what went to QSYSOPR > > It is possible that I heard or remembered it wrong because hey when there is > a lot of material on areas that were unfamiliar to us, we don't get it all > quite right. > > This is NOT what Jim is saying. > > > From: jimlangston@conexfreight.com (Jim Langston) > > > QSYSMSG is a special message queue you can set up if you want to. > > If you just do a CRTMSGQ QSYSMSG, the system will then route what it > > considers to be more critical messages into that queue instead of > > QSYSOPR. > > > > Nothing has to be changed except creating the queue. > > MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.