I think of the actual priority of my most loved ones as the lowest of any of the services required.
For example, if your most loved CICS has to wait for MQ, and MQ is below, say, less important CICS's, then your most loved CICS will be held up by this less important work. In effect, the priority of your most loved CICS is below that of your other CICS's. Therefore, you normally want such 'server' address spaces (VTAM, DB2, MQ, etc) to run well above all other work in the environment, to include your most loved CICS(s). MY $0.02. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Clark Lowery Sent: Tuesday, May 16, 2006 7:22 AM To: [email protected] Subject: MQ priority settings in z/os We have recently seen overall system slowdowns while application programs wait on an MQ response to a PUT or GET. When this occurs, we also see high CPU delays in the MQ MSTR and CHIN. We run high-volume (1200 tran/sec) transactions through a CTG/CICS/DB2 structure, and are debating how the MQ priority should be set. Should it be the same as the CICS AORs that are issuing the calls? Any hints will be appreciated! Clark NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
