Natural Buffer Pool

The shared-memory Natural buffer pool serves as a temporary storage area into which Natural cataloged object(s) (for example, programs) are loaded from a Natural system file for subsequent execution by the Natural runtime system and/or object compilation by the Natural compiler.

Since Natural generates reentrant Natural object code, it is possible for a single copy of a Natural object to be executed by more than one user at the same time. For this purpose, each object is loaded only once from a Natural system file into the Natural buffer pool, instead of being loaded by every caller of the object.

This section describes the basic principles of buffer pool operation and depicts the object loading procedure.


Object Loading

Object loading into the buffer pool is initialized when an executable Natural object is requested for execution.

When object execution is requested, the respective cataloged object(s) are read from the appropriate Natural system file and loaded into the buffer pool where they can be executed by the Natural runtime system.

Apart from executable Natural objects, non-executable objects of the type data area (local, global, parameter) are also loaded into the buffer pool if a Natural object that references such a data area is cataloged or recataloged (compiled).

Related Topic:

Object Execution - Natural Runtime System, Natural Nucleus

Object Removal

Objects are removed from the buffer pool when they are no longer referenced by a user and space is required for loading new objects. This guarantees maximum use of available storage space in the buffer pool.

If a buffer pool cache exists, unused objects are swapped from the buffer pool into the buffer pool cache. If an unused object is also removed from the buffer pool cache or if no buffer pool cache exists, the respective object is reloaded from the appropriate Natural system file when a user references it again.

Example of Object Loading and Execution

The diagram below illustrates the process flow when loading and executing a Natural program:

 

Illustrates the internal mechanics of how a Natural program is executed, highlighting the roles of the Natural Command Interpreter, the Runtime System, the Object Loader, and the Buffer Pool Manager

Legend

2

A user issues the Natural system command EXECUTE, requesting execution of a Natural object of the type program with the name PGM01.

3

The Natural command interpreter interprets the command and passes the request to the Natural runtime system.

3

The Natural runtime system passes the request to the object loader.

4

The object loader instructs the buffer pool manager to search the buffer pool (and the buffer pool cache, if available) for PGM01 and determine the address at which the object is stored in the buffer pool.

If the buffer pool manager finds the buffer pool address of PGM01, the buffer pool passes the address to the object loader and execution continues with 8.
If the buffer pool manager does not find the buffer pool address of PGM01, the buffer pool manager returns the negative search result to the object loader and object execution continues with 5 .

5

The object loader retrieves the cataloged object of PGM01 from the appropriate Natural system file.

6

The object loader passes the cataloged object of PGM01 to the buffer pool manager.

7

The buffer pool manager loads PGM01 into the buffer pool.

8

The buffer pool manager returns the buffer pool address of PGM01 to the object loader.

9

The object loader passes the buffer pool address of PGM01 to the Natural runtime system.

10

The Natural runtime system interprets and executes the compiled code of the cataloged object of PGM01.

Related Topics

The following topics in the System Architecture documentation refer to the Natural buffer pool:

The following topics in other Natural documentation refer to the Natural buffer pool: