MAREN V12.6B can execute in BS2000 OS DX V1.0B and higher.
Prerequisites for MAREN operation are:
- the software product SORT (BS2000), among other things for generating printer lists (see the “SORT” manual [22]);
- the software product RFA when access is to take place to the central MAREN catalog from remote systems in the MAREN network in shared mode (see the “RFA” manual [18]);
- the software product HIPLEX MSCF for information transfer between systems in the MAREN network in the case of some MARENADM statements (see the “HIPLEX MSCF” manual [12]).
User ID SYSMAREN
The user ID SYSMAREN is configured by default in BS2000 for operating MAREN. SYSMAREN is configured with the TAPE-ADMINISTRATION privilege. If the software product SECOS is in use, the TAPE-ADMINISTRATION privilege can be assigned to any user IDs, see "Authorization structure in MAREN".
The files of MAREN are installed under SYSMAREN. The MARENCP control program must be started under SYSMAREN later on.
The account number under which the MARENCP task is subsequently started should have the TP authorization (entry in the user catalog: MAX-ALLOWED-CATEGORY=TP).
Providing storage space for the MAREN catalog files
Depending on the mode of operation selected (exclusive or shared mode), storage space on the selected disks must be allocated for the files of the MAREN catalog.
The MAREN catalog files can be stored under any user ID, but it is recommended that you make the catalog available under the user ID SYSMAREN. The advantage to this approach is that it enables MARENCP to access the catalog files without having to make them shareable. In this case, MARENADM can only access the catalog files directly under TSOS or SYSMAREN.
To avoid scattering the MAREN catalog files and thereby impairing performance, sufficiently large values should be selected when allocating primary and secondary storage areas.
The size of the individual files can be estimated based on the following criteria:
- Volume catalog (see section “Volume catalog”). In the case of an NK-ISAM catalog, a PAM block contains one catalog entry. This size must be taken into consideration in the primary allocation. In these cases, 6000 MAREN catalog entries will require 6000 PAM pages.
- Logging file (see section “Logging files”). One PAM block contains one logging record. Since one logging record is written each time an catalog entry is changed, the size of the file steadily increases. Thus, at least two new logging records are added just to create a tape output file. Therefore, when allocating space, a rough estimate should be made of how many updates will be made in the catalog entries during the period the logging file remains assigned. For data security reasons and to avoid adversely affecting performance, each system in the MAREN network should have its own logging file. The block size selected for the logging file can also vary.