This section covers the following topics:
The ADARUN function is used to invoke Entire Net-Work. ADARUN invokes the Entire Net-Work control program and:
loads the module ADAIOR, which performs all operating system-dependent functions;
reads and interprets all ADARUN parameter statements;
loads the modules needed to execute the functions specified by the ADARUN parameters;
performs any necessary modifications to those load modules, based on the specified parameters;
passes control to Entire Net-Work.
The ADARUN statement is fully described in the Operations documentation of Adabas.
The syntax of ADARUN statement and parameters is:
ADARUN statements must:
Contain the word "ADARUN" in positions 1-6, followed by "parameter=value" strings of one or more entries;
Have one or more blanks, beginning in position 7, between "ADARUN" and the first "parameter=value"; and
Not extend beyond position 72 of a line.
ADARUN control statements may contain multiple statement lines. Each line must be specified as a separate statement according to the rules above.
The ADARUN statement is fully described in the Operations documentation of Adabas.
When specifying ADARUN parameters:
Ensure that the correct program to be executed is specified (see the PROGRAM parameter);
Ensure that the correct target ID is specified (see the TARGETID parameter); and
Determine which settings for the following parameters are applicable for the session:
FORCE (overwrite active target ID)
SVC (Adabas SVC number)
Each ADARUN parameter has a default value that ADARUN uses if the parameter is not explicitly specified. Parameters can be abbreviated, but the abbreviation must be unique; that is, not the same as those of other ADARUN parameters.
The Entire Net-Work session statistics can be used to determine the best settings for each parameter. The statistics can be displayed using Entire Net-Work operator commands during the session; they are also printed automatically at the end of a session.
The following is an example of an Entire Net-Work ADARUN statement:
ADARUN PROG=NETWRK,TARGETID=3333,NAB=20,NC=50,LU=65535,SVC=251
For this node, Entire Net-Work:
runs with a target ID of 3333;
allocates an attached buffer pool for 20 interregion communication buffers;
processes as many as 50 requests simultaneously;
uses the SVC 251; and
ensures adequate buffer size for Adabas compatibility by setting the value of the LU parameter to 65535. For more information about the LU parameter, read about it in the Adabas Operations documentation.
The following table summarizes some useful Entire Net-Work ADARUN parameters for Entire Net-Work. Details for each parameter can be found in the Adabas Operations documentation.
 |
Warning: If recommended numeric values are supplied in this table, do not specify smaller values; if recommended non-numeric values are supplied in this table, do not specify other values. |
| Parameter | Specifies | Minimum | Maximum | Recommended | Default |
|---|---|---|---|---|---|
| CT | The maximum number of seconds that can elapse from the time an Adabas command has been completed until the results are returned to the user through the interregion communication (operating-system-dependent). | 1 | 16777215 | --- | 60 |
| FORCE | Whether the nucleus can overwrite an existing ID table entry. | --- | --- | --- | NO |
| LU | The size of the intermediate user buffer area. | none | none | --- | 65535 |
| NAB | The number of attached buffers to be used. | 1 | varies, depending on the amount of available virtual storage | --- | 16 |
| NC | The maximum number of command queue elements. | 20 | 32767 | --- | 200 |
| PROGRAM | The program to be run. | NETWRK | NETWRK | NETWRK | (none) |
| SVC | The Adabas SVC number to be used for the session. | --- | --- | --- | 249 |
| TARGETID (see note below) | Entire Net-Work target ID. | 1 | 65535 | --- | 1 |
Note:
The TARGETID parameter is an optional ADARUN parameter that specifies
the unique Entire Net-Work target ID of this node. It is synonymous with the Adabas
DBID parameter. All target IDs used by Entire Net-Work, Adabas (database IDs), Adabas
TPF, Natural global bufferpools, etc., must be unique throughout all Entire Net-Work
nodes. In particular, the Entire Net-Work target ID must not coincide with any
database ID used in the network, with the exception of isolated databases that
are defined for local availability only and are therefore unknown to Entire Net-Work.
