MAREN in a multiprocessor configuration

To ensure maximum availability of MAREN in a multiprocessor configuration with joint resources, access to the MAREN catalog must be possible from all systems at any time. The MAREN catalog must therefore be installed on a shared pubset and accessible via RFA. All systems which are intended for a MAREN network, in other words which jointly access the same MAREN catalog, must be interconnected via HIPLEX MSCF. In the event of the master failing, another system (backup master) automatically assumes the role of master and continues running the MAREN applications without interruption.

Prerequisites

1. HIPLEX MSCF must be installed and started under TSOS on all systems which jointly access the same MAREN catalog. The system involved must be interlinked via an MSCF connection. This can take place either statically with the MSCF parameter file or dynamically using the following command:
   /START-MSCF-CONNECTION PARTNER-NAME=<system name>,CLOSELY-COUPLED
2. The pubset containing the shared MAREN catalog must be entered as a shared pubset in the MRSCAT of the systems involved:
   /ADD-MASTER-CATALOG-ENTRY ENTRY=<spvs-catid>,SHARED-PUBSET=*YES
3. The master and backup master must be defined for the shared pubset:
   /SET-PUBSET-ATTRIBUTES PUBSET=<spvs-catid>,MASTER=<master-sysid>,
         BACKUP-MASTER=<backup-sysid>,ALTERNATE-BACKUP=*BY-SHARER
   The shared pubset is imported into the master:
   /IMPORT-PUBSET PUBSET=<spvs-catid>,USE=*SHARE,SHARER-TYPE=*MASTER
   and into all the other systems (i.e. slaves):
   /IMPORT-PUBSET PUBSET=<spvs-catid>,USE=*SHARE,SHARER-TYPE=*SLAVE
4. The user ID SYSMAREN must exist on the home pubset of all systems that have access to the MAREN catalog. It must be checked whether the standard catalogue identifier of the respective home pubset is entered and adjusted if necessary:
   /MODIFY-USER-ATTRIBUTES USER-ID=SYSMAREN,...PUBSET=*HOME,DEF-PUBSET=*HOME
5. If the SYSMAREN user ID has different access authorization on the master than on the local system, the account number and the password for SYSMAREN on the master must be specified whithin the MARENCP ENTER file. They are needed to establish the RFA connection to the shared pubset with the MAREN catalog.
6. The MAREN catalog must be created or installed on the shared pubset under the user ID SYSMAREN.
7. The MARENLIB facility (for using MAREN exits) and the MAREN program files must be installed on the home pubset of all systems that have access to the MAREN catalog. This is because the source and target user IDs must match for an RFA connection to a shared pubset.
8. On slave systems, direct access to the MAREN catalog via MARENADM is possible only under the user ID SYSMAREN. This is because the source and target user IDs must match a user ID on the shared pubset for an RFA connection. Access to the MAREN catalog by other user IDs is handled via the MARENCP task.

The systems of the MAREN network are then interconnected and exchange messages and signals via HIPLEX MSCF.

If the master of the shared pubset fails, the “backup master” automatically assumes the role of master. Within the MARENCP task, the RFA connection to the shared pubset is restored on all systems and MARENCP is restarted.