MAXBUFF - Default Buffer Size

#### Search Results

Search

# MAXBUFF - Default Buffer Size

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

Possible settings | `1 - 2097147`, but less than or equal to `value = RPCSIZE - 4` | Default 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 and to send back the result. The buffer must be large enough to hold the largest data area received by all client requests and all results 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 Interface Objects and Automatic RPC Execution in the Natural RPC (Remote Procedure Call) documentation.
3. On the client side, it determines the size of the buffer provided for the execution of Natural RPC calls. This buffer is used to build the client request and to receive the result from the server. The buffer must be large enough to hold the largest data area received by all client requests and all results 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.
4. On the client side, you need not specify `MAXBUFF` if you use an interface object generated with the SYSRPC utility and `COMPAT NONE`, and if the parameters neither contain dynamic fields, nor X-arrays or group structures.
5. The size of the data exchanged between the client and server is provided by the Interface Object Generation function of the SYSRPC utility. To calculate the size for RPC execution, you may use the `SYSRPC CSMASS` command; see Calculating Size Requirements in the SYSRPC Utility documentation.