Bufferpool Management

An attempt was made to free the fixed buffer pool element address $2, however, this address is not allocated in the $1 buffer pool. The request was issued from the location indicated by $3.

This indicates that an invalid free request has been issued for the buffer pool as indicated by $1. Using the $3 address, the module and offset from which the request was issued can be determined. Generally speaking it indicates a problem with the usage of the $1 buffer pool. When $1 is a Software AG created buffer pool, this should be reported to your local support centre.

An attempt was made to free the fixed buffer element address $4. This buffer was found to be within the buffer pool $1 and the subpool as identified by $2 and $3, however, the address provided did not point to the start of a buffer in this subpool. The request was issued from the location indicated by $5.

This indicates that an invalid free request has been issued for the buffer pool as indicated by $1. Using the $5 address, the module and offset from which the request was issued can be determined. This indicates a problem with the usage of the $1 buffer pool. When $1 is a Software AG created buffer pool, this should be reported to your local support centre.

An attempt was made to free the fixed buffer address $4 in the $1 fixed buffer pool. The address was found to be in subpool name $2 id $3, however, it was already free. The request was issued from the location indicated by $5.

This indicates that a module attempted to free the buffer identified by $4 twice. Using the $3 address, the module and offset from which the request was issued can be determined. This highlights a logic error with the usage of the $1 buffer pool. When $1 is a Software AG created buffer pool, this should be reported to your local support centre.

A 'get' request has been issued for the $1 buffer pool and can be resolved by the subpool $2 id $3. This subpool, and any extensions that may have previously been allocated, is full and therefore another extension has to be built.

An attempt will be made to create the extensions. A subsequent message will inidcate the sucess or otherwise of the attempt to expand.

When this occurs frequently for the same subpool, it might be worth considering increasing the base allocation for the subpool to avoid the overhead of expansion.

At attempt to expand subpool $2 id $3 in the $1 buffer pool failed due. $4 contains the status of the request in hexadecimal format. This represents a two byte return code followed by a two byte feedback code indicating why the expansion request failed. Feedback Explanation 18 Equal subpools specified 1C, 20, 24 Not enough storage in the region/partition for controlblocks 3C Bufferpool not allowed to expand 44 Not enough storage in the region/partition/DS for expansion

Determine why the expansion failed based on the status as indicated by $4. Gerneally speaking, this will only occur due to a shortage of storage in the region. In this case, review the size of the region in which Com-plete is running or reduce the usage of the storage which is in short supply.

This message is issued when a new subpool or subpool extenstion is allocated by the fixed buffer pool manager. A preceeding or subsequent message will indicate why it has been allocated. The values are as follows...

$1 - Subpool name

$2 - Numeric Subpool ID

$3 - The Element size contained in this subpool in bytes

$4 - The number of elements allocated in this subpool

$5 - The total size of storage allocated for this subpool

$6 - Where the subpool storage resides. This can be ANY, BELOW, DS, ECSA or CSA.

$7 - The storage protect key which the subpool storage has assigned. This will normally be Com-plete's key.

A 'get' request has been issued for the $1 buffer pool, however, no subpool exists to satisfy the request. As the buffer pool was created with an option indicating that the subpools should automatically be created if no match is found, the fixed buffer pool manager is about to attempt to create a subpool to match the request. The buffer subpool will be built with an element size of $2 and with options $3. These options are the hexadecimal option bytes as passed to the 'get' request. $4 is the address from where the 'get request was issued.

Further messages will be issued indicating the success or otherwise of the attempt to create the new subpool.

An attempt to create a new buffer subpool for the $1 buffer pool failed. $2 is the status indicating the reason for the failure. This status is a hexadecimal representation of a return and feedback code with the first two bytes representing the return code and the second two bytes the feedback code. The possible values and their meanings are described in the explanation of message BPM0005.

The program which issued the 'get' request which resulted in an attempt to create a subpool to satisfy the request will be notified that the 'get' failed.

The subpool $2 id $3 in the buffer pool $1 was previously expanded due to excessive demands on the space allocated in the base area. The fixed buffer pool mananger has determined that enough space now exists to delete some of the expansions. In this case, $4 indicates the number of expansions which have been deleted and are no longer available to the subpool. They can of course be allocated again in the future should they be required.

An attempt was made to free a fixed buffer element from the buffer pool $1. This was found to be in subpool $2 id $3 and was found to have been gotten with a token provided on the 'get' request. On the free request either no token was provided, or a token was provided which didn't match the token provided on the 'get' request. The free request was issued from the location indicated by $7. $5 is the token which was provided on the 'get' request and $6 is the token which was provided on this request. If either are blank, it indicates that no token was provided for the appropriate request. $4 is the address of the token which was the target of the free request.

The buffer is not freed.

This indicates that there is an error in the handling of the $1 buffer pool. When a buffer is gotten with a token specified, the free request must be issued with the same token name before the free request will be processed. Using the $6 address, the module and offset from which the request was issued can be determined. When $1 is a Software AG created buffer pool, this should be reported to your local support centre.

A request has been issued to free fixed buffer element from the $1 buffer pool. The buffer has been found in subpool $2 id $3 and was found to have been gotten with a chain specified. In this case, the free request has been issued without a chain base specified or the buffer element was not found on the chain provided. The request was issued from the location indicated by $7. $5 is the address of the SPDS for the buffer pool element and $6 is the address of the chain base provided on the free request. $4 is the address of the buffer which was the target of the free request.

The buffer is not freed.

When a buffer is gotten with a chain request, the fixed buffer pool manager chains information for the gotten buffer into the provided chain. To ensure that the system intergrity is maintained, the buffer must be removed from this prior to it being freed. In this case either the free request did not provide a chain base or the buffer does not exist in the provided chain and therefore cannot be removed from the chain. This indicates that there is a logic error in the use of the $1 buffer pool. Using the $6 address, the module and offset from which the request was issued can be determined. When $1 is a Software AG created buffer pool, this should be reported to your local support centre.

This indicates that an attempt to create a new buffer subpool for buffer pool $1 was successful. This will be preceeded by message '6' which will indicate the size and attributes of the newly created subpool.

An attempt to expand subpool $2 id $3 in the $1 buffer pool was successful. A preceeding message will have indicated the attributes of the newly created subpool extension.

An internal request was issued to perform a fixed buffer pool management function for the $1 buffer pool. The request completed successfully, however, the status information as indicated by $2 was returned. $2 is the hex representation of a two byte return code and a two byte feedback code. The first two bytes are the return code and should always be x'0004', while the second two bytes are the feedback code. The request which was being issued will have been indicated by a preceeding message.

Processing continues. Normally a message will following indicating that the indicated processing completed sucessfully.

This message should not normally be issued and indicates the possibility of a logic error in the fixed buffer pool manager. Although no direct problems are associated with this message, it should be reported to your local support centre.

A FREEALL request has been issued for the $1 buffer pool to free a group of buffers with certain attributes, however, this has resulted in a free request for a buffer which has already been freed. The request was issued from the address indicated by $2.

The FREEALL request will be terminated, possibly resulting in buffers being left allocated when they are no longer in use.

This indicates that a logic error exists in the handling of the $1 buffer pool. Using the $2 address, the module and offset from which the request was issued can be determined. When this is a Software AG controlled buffer pool, this should be reported to your local support centre.

The buffer pool named $1 has been allocated successfully. One or more fixed buffer pool number '6' messages will be subsequently issued describing the various subpools created for this buffer pool.

The buffer pool known as $1 has been successfully deleted.

A $2 request for buffer pool $1 returned a status $3 to the caller. The caller indicated that a message should be issued in the event of a status for the request and this message is the result. The $3 status consists of a halfword return code and halfword feedback code respectively. When the buffer pool no longer exists, $1 will contain the string '$UNAVAIL'.

The system will continue as normally as possible. This message will generally only be issued when a program is not in a position to handle a failure due to the nature of the module. For example, if the routine which builds output messages cannot get a buffer, then it is unlikely that it will be able to get a buffer to print a message about the fact that it cannot get a buffer.

When this occurs for a Software AG created buffer pool, it should be reported to your local support centre.