Dispatch priority for z/OS address spaces

IBM recommends that the address space providing service to other address spaces be at the higher dispatching priority than those needing the service. IBM MQ provides services to many applications and MainView Middleware Monitor(MVMM) relies on IBM MQ for information concerning the current state of the messaging environment.

The fact that MVMM provides information regarding the state of IBM MQ warrants MVMM being at the same level as IBM MQ. If MVMMdoes not get the information it needs this message appears in the z/OS operator's console: MQS0301W - IBM MQ Command Server did not accept a command. If the system load continues to not allow timely monitoring, MVMM indicates that monitoring is ineffective with a severe message.

The agent and extensions should be non-swappable. You should assign the following start order to the agent and extensions: QPEA, QPCFG, QPMON, QPBTM. The stop order should be QPBTM, QPCFG, QPMON, QPEA.

The MVMM Extensible Agent and extensions should all run in the same class, and they should mirror the z/OS queue managers. Further, you should stop the MVMM Extensible Agent and extensions before stopping the queue managers. No harm is done if you do not stop the MVMM Extensible Agent or extensions before stopping the queue managers. Memory allocation should be 4 megabytes or more.