Text |
Buffer pool initialization is not linked. |
Explanation |
Driver entry CMBPGETS is missing. Natural environment is incomplete. |
Action |
Check your Natural environment. |
Text |
Incompatible version for ... buffer pool .... |
Explanation |
The version of the buffer pool already initialized is not supported by the current Natural version. |
Action |
Ensure that the buffer pool is allocated and initialized by a compatible Natural version. |
Text |
Incompatible type for ... buffer pool .... |
Explanation |
Natural has various buffer pools to share common virtual memory.
For example: - type Natural for Natural programs,
- type SORT for common external sort space,
- type EDIT for common external editor buffers,
- type MONITOR for common monitor data.
Because the buffer pool types have different storage layouts,
it is not possible to use the buffer pool types interchangeably. |
Action |
Check NTBPI macro settings in your Natural parameter module for local pools or the parameter settings in your startup JCL for global buffer pools. |
Text |
Initialization of ... buffer pool failed. (...). |
Explanation |
The indicated buffer pool could not be initialized for one of the following reasons: - GETMAIN for the local buffer pool storage failed - specified buffer pool size (BPSIZE parameter) is too small - missing LINK for the EDTSTUB (installation error) |
Action |
Please check installation and correct the problem. |
Text |
Global :1: buffer pool :2: not found. |
Explanation |
The global buffer pool :2: of type :1: could not be found. Either the global buffer pool is not yet allocated or the used name of the global buffer pool is wrong. If the buffer pool could not be found because the Natural subsystem does not exist, the name of the Natural subsystem is appended to the name of the global buffer pool, separated by a slash (/). |
Action |
Check the name of the global buffer pool (Natural profile parameter BPNAME or NTBPI/BPI subparameter NAME) and/or the name of the Natural subsystem (Natural profile parameter SUBSID). |
Text |
Global ... buffer pool ... allocated in system key. |
Explanation |
The indicated global buffer pool has been allocated in system key, but the authorized services manager (ASM) has not been started or is not of the required minimum version. To process a buffer pool that has been allocated in system key, the ASM is required. |
Action |
Start an authorized services manager of the required minimum version for the Natural subsystem in use. |
Text |
Error :1: while loading preload list :2: :3:. |
Explanation |
Natural error :1: has occurred when Natural tried to load the buffer pool preload list :2: at the start of the Natural session. If the Natural error occurs when the preload list is being read, the information :3: is blank. If the Natural error occurs when an object named in the preload list is being loaded, :3: contains library and program name of the object. The typical Natural error will be NAT0082, which means that either the preload list or one the named objects could not be found. |
Action |
Check the object names in your preload list. |
Text |
Buffer pool propagation failed. |
Explanation |
The propagation of changes to the currently used Natural buffer pool is requested by the current setting of the Natural profile parameter BPPROP, but the propagation failed. Possible reasons: - The Natural Authorized Services Manager is not started for the Natural subsystem ID used by the current Natural session. - The Natural Authorized Services Manager is started without an XCF group name and BPPROP=PLEX or BPPROP=GPLEX is requested by the current Natural session. |
Action |
Contact the Natural administrator and/or check the setting of the Natural profile parameter BPPROP. |
Text |
Allocation of local buffer pool cache failed. |
Explanation |
A buffer pool cache has been requested for a local Natural buffer pool, but the cache could not be allocated. The local Natural buffer pool is operational, but runs without a cache. This error message is preceded by other error messages which indicate the reason. |
Action |
Check the preceding error messages. |
Text |
Work area could not be obtained by Authorized Services Manager. |
Explanation |
The Authorized Services Manager (ASM) could not obtain the work area for the PC routine which is used to access a buffer pool in system key. |
Action |
Increase the amount of available space for the ASM address space. If the problem persists, contact Software AG Support. |
Text |
Cache creation failure :1: :2: :3: Reason= :4:. |
Explanation |
The cache create function has failed. The message shows the failing operating-system macro and the macro function (:1:). It also indicates the type of macro-request failure (:2:), that is, whether the macro failed due to macro failure (RC=) or ABEND (CC=). Parameter :3: is the ABEND code or macro-request return code respectively. Parameter :4: is the associated reason code. |
Action |
See the relevant operating-system manuals for the reason of the failure. |
Text |
Cache deletion failure :1: :2: :3: Reason= :4:. |
Explanation |
The cache delete function has failed. The message shows the failing operating-system macro and the macro function (:1:). It also indicates the type of macro request failure (:2:), that is, whether the macro failed due to macro failure (RC=) or ABEND (CC=). Parameter :3: is the ABEND code or macro-request return code respectively. Parameter :4: is the associated reason code. |
Action |
See the relevant operating-system macros for the reason of the failure. |