4. Operands

The keywords LANG and DEBUG are the same as those in the DEBUT [U4.11.01] procedure.

The BASE keyword is different for the POURSUITE procedure.

4.1. Keyword BASE

BASE =

The functionality of this keyword is to redefine the values of the parameters of the direct access files associated with the « databases » in case you do not want to use those set by default. The maximum size of the associated file (s), and therefore the maximum number of records, can be redefined using the parameter passed on the command line behind the keyword

In POURSUITE mode, some characteristics of the GLOBALE base can no longer be changed.

Values by default for parameters associated with databases

VOLATILE
NMAX_ENRE	62914
LONG_ENRE	100 K words
LONG_REPE	2000

The word is worth 8 bytes on a 64-bit platform and 4 bytes on a 32-bit platform.

On Linux 64, procedure POURSUITE, with values by default, will allocate a direct access file of at most \(62914\) records from \(100\mathit{Kmot}\) (the \(K\) equals \(1024\)) for the “VOLATILE” database.

Note:

The actual size of the file is dynamic; it depends on the volume of information to be effectively stored. This size is limited by operating conditions and a parameter defined among the values characterizing the platform. On the 64-bit Linux reference platform, the initial*size* is set to 48GB.*This value is used to size 2 objects used by the memory manager, it will be changed automatically during execution if necessary. It is possible to*modif*this value* by passing an argument on the executable command line behind the keyword « –max_base size » where size is a real value measured in MB. *

For the Global database, which can be saved and re-used as calculation data, the maximum size initiale in « POURSUITE » is kept as it is if the « –max_base » parameter is not used, but can be redefined as needed in this way.

4.1.1. Operand FICHIER

♦ FICHIER =

Symbolic name of the base under consideration.

Only the database parameter “VOLATILE” can be redefined.

4.1.2. Operands LONG_ENRE/NMAX_ENRE/LONG_REPE

Definition of database parameters (direct access files).

/| LONG_ENTER= lenr

lenr is the length of the records in \(\mathit{Kmots}\) of the direct access files used.

Note:

Memory manager JEVEUX uses this setting to determine two types of objects: large objects that will be split into as many records as needed, and small objects that will be accumulated in a record-sized buffer before being unloaded.

| NMAX_ENRE= NENR

nenn is the number of records by default, this value is determined from LONG_ENRE and an operating parameter under LINUX64 set to \(12\mathit{Go}\) (51539607552 bytes) for the maximum size of the file associated with a database.

Note:

The two operands LONG_ENRE and NMAX_ENRE must be used carefully, as misuse may lead to the sudden termination of the program by saturation of the direct access files. The consistency between the maximum file size and the value resulting from the product of the two parameters LONG_ENRE and NMAX_ENRE is checked at the start of execution.

| LONG_REPE= lrep

lrep is the initial length of the directory (maximum number of objects addressable by JEVEUX), it is managed dynamically by the memory manager, which extends the size of the directory and all associated system objects as and when needed.

4.2. Keyword CODE

This keyword allows you to activate the generation of the.code file. For test cases only, this keyword is a simplified version of the DEBUT CODE keyword.