|
I stand corrected. I don't think that it did so in the early versions, but I could be wrong. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com bdietz@3x.com Sent by: To: MIDRANGE-L@midrange.com owner-midrange-l@mi cc: drange.com Subject: RE: QSYSOPR message queue segregation 07/19/01 01:29 PM Please respond to MIDRANGE-L Hey Al on V5R1 the main menu says OS/400 Main Menu. They did change from AS/400. Makes you wonder why they chose not to use iSeries. Bryan Dietz barsa@barsaconsulting.com Sent by: owner-midrange-l@midrange.com 07/19/2001 12:44 PM Please respond to MIDRANGE-L To: MIDRANGE-L@midrange.com cc: Subject: RE: QSYSOPR message queue segregation A few points, QSYSOPR is an original part of the System/38 architecture. Early in the life of the System/38, I tried to put two different companies on one System/38, and then realized that there was no way that I could not direct messages from different subsystems to different message queues. As the System/38 was a relatively small system, this was not a big limiting factor. It might be a reasonable requirement in light of the size of the AS/400 today. (Yes, I will start to call it the iSeries when they change the name on the MAIN menu.) You can LPAR a UNI processor, if it's the new S-Star processors that were announced in May. Unfortunately, IBM did not give these processors a new number line (like 900 models). So there are some model 270/8xx that you can LPAR as UNIs, with others that you can't. It seems that IBM's doing everything it possibly can to make sure that this product remains a secret. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Michael Oakes <Michael.Oakes@eb.u To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> k.com> cc: Sent by: Subject: RE: QSYSOPR message queue segregation owner-midrange-l@mi drange.com 07/19/01 10:50 AM Please respond to MIDRANGE-L Thanks Al, Your posts to this message board have been authoritive and very helpful to me in the past. Hopefully I can get to the bottom of this one! I am hoping to go deeper and try to understand the mechanism behind the error handling on the 400. I think there must be a way to have the message queue changed for different environments/subsystems. Similar to the way I can configure printers to route to a dedicated printer message queue where these are trapped and reponded to automatically using Robot Console. LPAR is out of the question as I have only one processor! There must be somewhere that is stating this message go here, that message go there. Regards Michael -----Original Message----- From: barsa@barsaconsulting.com [mailto:barsa@barsaconsulting.com] Sent: 19 July 2001 14:43 To: MIDRANGE-L@midrange.com Subject: Re: QSYSOPR message queue segregation When the system wants to send a message to QSYSOPR, you don't get much choices. There are two notable exceptions: 1. You can segregate "critical messages" to another message queue names QSYSMSG in QSYS. Messages that go here regarding: System integrity from a security perspective (these go to QSYSMSG instead of QSYSOPR) DASD integrity - a possible RAID-5 or mirroring failure (these go to QSYSMSG as well as QSYSOPR) System Integrity - a looming failure of OS/400 (these go to QSYSMSG as well as QSYSOPR) 2. You can segregate configuration messages (which are typically less critical messages - except for when something fails to work) using the system value QCFGMSGQ (first shipped in V4R4). A message queue with the same name is also shipped in QSYS for this purpose. Caution, if you turn this on, the default for printer messages is here. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com Michael Oakes <Michael.Oakes@eb.u To: MIDRANGE-L@midrange.com k.com> cc: Sent by: Subject: QSYSOPR message queue segregation owner-midrange-l@mi drange.com 07/18/01 06:17 PM Please respond to MIDRANGE-L I am unfortunate enough to have to host Production and Development environments on the same AS/400 system. Does anyone know how to change the job, subsystem or profile defaults to use say QDEVOPR instead of QSYSOPR? I am trying to provide proper response times to production problems whilst removing developer coding errors from QSYSOPR. Any help would be very much appreciated. Michael Oakes AS/400 Operations Manager Electronics Boutique Plc ****************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at: mailto:postmaster@eb.uk.com The recipient acknowledges that transmissions made via the Internet can be corrupted and therefore EB Plc and any of its subsidiaries do not give any warranty as to the quality or accuracy of any information contained in the message or assume any liability for it or for its transmission, reception or storage. This footnote also confirms that this email message has been swept by Anti-Virus software for the presence of computer viruses. http://www.eb.uk.com http://www.game.uk.com ****************************************************************** +--- | 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 +--- +--- | 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 +--- ****************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager at: mailto:postmaster@eb.uk.com The recipient acknowledges that transmissions made via the Internet can be corrupted and therefore EB Plc and any of its subsidiaries do not give any warranty as to the quality or accuracy of any information contained in the message or assume any liability for it or for its transmission, reception or storage. This footnote also confirms that this email message has been swept by Anti-Virus software for the presence of computer viruses. http://www.eb.uk.com http://www.game.uk.com ****************************************************************** +--- | 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 +--- +--- | 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 +--- +--- | 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 +--- +--- | 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-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.
midrange.com
