This Natural profile parameter is used in a Natural RPC environment to specify the maximum buffer sizes.

Possible settings	1 - 2097147	Maximum buffer size in KB.
	0	No buffer is allocated.
Default setting	0
Dynamic specification	yes
Specification within session	no

Notes:

1. MAXBUFF can be specified on both the client and the server side.
2. On the server side, it determines the size of the buffer provided by the server to receive the client request including data and to send back the result. The buffer must be large enough to hold the largest of the following two data areas for all client requests; that is, the request received by the client, and the result sent back to the client. If the size of the buffer is too small for a request, a temporary buffer with the required size is allocated and used for this request. For further information, see Stubs and Automatic RPC Execution in the Natural Remote Procedure Call (RPC) documentation.
3. On the client side, it determines the size of the buffer provided for the automatic execution of Natural RPC calls. This buffer is used to build the client request including data and to receive the result from the server. The buffer must be large enough to hold the largest of the following two data areas for all requests sent by the client.
4. The size of the data exchanged between the client and server is provided by the stub generation function of the SYSRPC utility.

Dependency on ACIVERS Settings

In case of an EntireX Broker node, special considerations apply if you are using Entire Net-Work as a transport layer. With Entire Net-Work, the receive buffer length passed to the EntireX Broker stub is restricted by the startup parameter IUBL and must not exceed 32 KB. Depending on the setting of the Natural profile parameter ACIVERS, the receive buffer length is set as follows:

• ACIVERS=1: 32000

• ACIVERS=2: 30K

• ACIVERS>2: the value specified with MAXBUFF

For further information, see the Natural Remote Procedure Call (RPC) documentation.