Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Calculating message buffer space — An example z/OS MVS Setting Up a Sysplex SA23-1399-00 |
|
To limit the number of message buffers in your system
and maintain adequate signaling performance, you need to know how
much buffer space is required to support a particular message length.
(The message buffer space required for a particular message length
can vary from release to release.) For this release of MVS™,
compute the message buffer space required for a single message as
follows: subtract 1K from the message length, round the result up
to the nearest multiple of 4K, then add 2K. For example, if the message
length is 40,000 bytes:
So, a MAXMSG value of 42K provides enough message buffer space to send a single message of 40,000 bytes. Because the transport class needs more than a single message buffer to have an adequate supply for signalling, the MAXMSG value, in this example, should be a multiple of 42K. For details on deciding which MAXMSG value to use, see Planning signaling services in a sysplex. Total Buffer Space: To compute the maximum
message buffer space that MVS can allocate per system, use the
following formula:
To calculate the buffer space for a transport class, multiply 64K or the specified message buffer space (whichever is greater) by the number of systems in the sysplex. For local message buffer spaces, add the LOCALMSG value for each transport class specified for the system. For example, in a sysplex of four systems, suppose COUPLxx is defined
as follows for one of the systems:
For this system, the buffer space values for the paths and transport
classes are:
The total maximum buffer space for the system is:
|
Copyright IBM Corporation 1990, 2014
|