Hello Clark, Follow that data.
Defuse the wait conditions as much as possible. (is it a valid wait ?) Place the MSTR and CHIN s started tasks, but by all means use ENCLAVES for the actual transactions or programs that treverse the MQ/CICS/DB2 address spaces. Kevin -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Clark Lowery Sent: Tuesday, May 16, 2006 8: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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
