Previous Topic: Address Space Message Rate ControlNext Topic: Preventing Problems


Using Message Control Parameters

To understand how these two parameters interact in CA OPS/MVS, consider the analogy of a bathtub filling with water, where the bathtub is an address space and the water is address space messages.

The first thing to do in the analogy is create this bathtub with the MSGTHRESHOLD parameter. This parameter is the finite number of messages that the server can hold; in other words, it indicates the depth of the bathtub.

Next, establish how many messages can drain out of the server with the MSGDRAINRATE parameter. This is analogous to the size of the drain hole for water leaving the bathtub. It actually limits how fast messages are flowing, in messages per second.

Finally, note that CA OPS/MVS can issue a message indicating that MSGTHRESHOLD has been exceeded.

So, if the MSGDRAINRATE set to the requirements of your installation is not big enough, the messages back up and spill out of the server. In other words, the number of messages being held exceeds the MSGTHRESHOLD number. Once this happens, message OPS4402O notifies you.

Note: OPS4402O is not WTOd. It is sent directly to the OPSLOG of the issuing subsystem and, for automation purposes, to the AOF of that subsystem. It does not appear in SYSLOG.

Example: Message rate control could be as follows:

Given these values, an address space that is issuing 11 messages per second would exceed MSGTHRESHOLD in less than a minute.