backup master
A slave processor which is to become the new master processor of a shared pubset following a master change.
batch mode
Job started with the ENTER command. In contrast to interactive mode, execution is predefined and specified in an ENTER file.
BCAM
BCAM (Basic Communication Access Method). This is a functional unit of the data communication system DCM. BCAM implements transport services and the associated administrative functions.
catalog ID (= CATID)
See "CATID".
CATID (= catalog ID)
Identifies a pubset (see "volume serial number", "pubset"). It is specified in the complete file name / path name in the form :catid:.
console
Terminal of systems support, used for system operation.
control volume set
The control volume set is the container for global pubset metadata files of SM pubsets.
exported pubset
See "imported pubset".
heterogeneous network
MSCF network comprising hosts with different BS2000 versions.
home pubset
The home pubset is required to initialize the BS2000 operating system and during the entire session. Each processor running under BS2000 has one home pubset.
User access to BS2000 is always via the home pubset. This is where the logon is validated and the access permissions and availability of resources are checked.
imported pubset
MPVS (Multiple Public Volume Sets), a functional extension of the Data Management System, allows several sets of public disks (pubsets) to be installed within a session. Further pubsets can be imported as needed onto the system of the home pubset, which is required throughout the session; these can then be accessed directly by the importing system. The properties of imported pubsets can be queried using the SHOW-MASTER-CATALOG-ENTRY and SHOW-PUBSET-PARAMETERS commands.
Each user can create, edit and delete files and job variables on an imported pubset, provided this authorization is granted by the system management.
Of course, an imported pubset can also be exported again, i.e. moved from the system. The home pubset cannot be exported.
long connection
Communication variant in HIPLEX MSCF. A long connection is set up and cleared down by MSCF applications and is available exclusively to these applications for communication purposes. The link to the server tasks of the MSCF applications remains open for the entire lifetime of the connection, i.e. for a long period.
master change
Process in which the master attribute of a processor in a shared pubset network is transferred to a different sharer. This process is initiated by unloading MSCF on the master processor (also with shutdown), by the failure of the master processor, and by a master export with master change. An unsuccessful master change can be restarted by issuing the IMPORT-PUBSET command.
master processor
The processor on which all DMS administration functions of a shared pubset are executed.
MRSCAT
Data structure which assigns a catalog ID to the BCAM name of the BS2000 processor managing the catalog. The pubsets are addressed using the MRSCAT catalog directory. Although any pubset can possess such a catalog directory, only the MRSCAT of the home pubset is used for pubset addressing during the session.
MSCF
Subsystem of BS2000which allows privileged components (MSCF applications) of the operating system to communicate with other BS2000 entities.
MSCF communicates by means of BCAM.
MSCF configuration file
The configuration file is used to define the configuration parameters and the processors with which an MSCF connection is to be established. The configuration file is executed automatically when HIPLEX MSCF is started. A configuration file in command format is mandatory for the XCS network.
MSCF connection
Communication paths which exist between two processors and are managed by the MSCF subsystem.
MSCF server task
Special system task which executes an MSCF job of a partner processor on the local processor. The number of MSCF server tasks is increased and decreased dynamically by MSCF.
MSCF trace file
File containing the traces of the MSCF subsystem. The MSCF traces are an important source of information for diagnosing error situations.
non-relevant partner
See "relevant partner".
partner
Remote BS2000 system which can also be a guest system under VM2000.
(BS2000) processor
BS2000 OS DX server with the BS2000 OS DX (native) operating system or a VM2000 guest system on a BS2000 OS DX server with VM2000.
In other literature the term “BS2000 system” (system for short) is also used.
pubset (= PVS, public volume set)
A pubset (PVS) is a public storage area (i.e. memory available to all users) on disk storage units combined to form one administrative unit. A pubset must contain at least one disk. The disk numbered ‘0’ is called the PUBRES; in particular, this contains the references to any other disks in the pubset. Pubsets are divided into SF and SM pubsets.
A single-feature pubset (SF pubset) is made up of volumes with identical physical characteristics.
A system-managed pubset (SM pubset), which comprises one or more volume sets (max. 255), can be viewed as an independent repository for logically related data.
In addition to the data, the SM pubset contains the associated metadata and thus represents a switch unit.
See "control volume set".
See "imported pubset".
See "pubset configuration file".
pubset configuration file
The volume sets belonging to an SM pubset and their characteristics are detailed in the pubset configuration file :<catid>: $TSOS.SYS.PUBSET.CONFIG. This file is created implicitly when the pubset is generated and is always contained on the control volume set.
See "pubset".
PVS
See "pubset".
PVS ID
Pubset identifier; specified in the form :catid: in the full file name / path name.
registered function
Functional unit whose entities are established on all processors in the XCS network and whose inter-processor cooperation is supported by XCM.
relevant partner
From the point of view of partner monitoring, the term "relevant partners" refers to the partner processors on which BS2000 version OSD-BC ≥ V10.0 is running and to which a CCS connection is established or has been established at any time in the current HIPLEX MSCF session. All other partner processors are called "non-relevant partners".
RFA
Remote File Access; software product that enables access to files located on non-local (i.e. remote) BS2000 processors. RFA can be used with or without MSCF.
SF pubset
See "pubset".
shareable private disk (= SPD)
A disk mounted in a disk drive that can be accessed by more than one processor via direct hardware connections.
shared pubset
Public volume set which can be accessed by two or more processors concurrently.
shared pubset network
Network of processors which access a shared pubset.
shared resource
Shared resources are utilized by all the users of the respective network (e.g. disks, global memory). Shared resources must therefore be accessible from all processors.
sharer
Processors which have simultaneously imported a particular pubset (shared pubset).
sharer in the SVL
SVL entry of a sharer on each volume of a shared pubset. The entry is normally made at import and deleted at export or in the event of a processor failure.
short connection
Communication variant in HIPLEX MSCF. A short connection is set up with the START-MSCF-CONNECTION command and cleared down with STOP-MSCF-CONNECTION, and is available equally to all MSCF applications. A link between the job-submitting task and the job-receiving task only exists for the short duration of a job.
slave processor
Any sharer of a shared pubset which is not the master processor.
SM pubset
See "pubset".
Software Monitor openSM2
The openSM2 monitoring system provides the user with statistical data on the performance of the DP system and the utilization of resources.
standby mode
In the event of a processor failure (and when maintenance tasks are being carried out), the continued availability of critical applications is ensured if the environment required for such an application is maintained on a standby system and the application is automatically started on this system should the processor fail.
This is guaranteed by the product HIPLEX AF (AF = Availability Facility) in the shared pubset network.
SVL (= standard volume label)
Standard volume label with volume serial number.
SYSID
System identifier comprising one to three characters. Possible values are: A...Z; 0...9 and 65...192; (default: 250).
user catalog
A user catalog contains the pubset-specific permissions for each user entered in this file. The entries in the user catalog control which user ID can access a pubset. If a user does not have an entry for a particular pubset in the user catalog, this user cannot access this pubset or any shareable files (unless general permission is defined via the system parameter FSHARING).
Users can check which entries exist for them by issuing the SHOW-USER-ATTRIBUTES command.
The user catalog is sometimes known as the JOIN file.
volume serial number (= VSN)
A 6-position number assigned to the volume during initialization (VOLIN or INIT). This number is contained in the standard volume label and is used to identify the volume.
The VSN of public volumes begins with the character string "PUB" (PUB notation) or contains a period between the 1st and 6th character (dot notation). In PUB notation, the 4th character is the SF pubset ID or (with SM pubsets) the volume set ID.
volume set
Component of an SM pubset comprising one or more volumes (max. 255). Each volume set contains complete files. The control volume set is a special volume set as it contains global pubset metadata files.
VSN
See "volume serial number".
watchdog
Functional unit of the MSCF subsystem. Manages the sharer configuration of all shared pubsets, monitors the sharer using a disk protocol, and implements the necessary DMS recovery measures in the event of a failure.
watchdog file
The file $TSOS.SYS.PVS.SHARER.CONTROL on a shared pubset. It is required for the disk protocol (reading/writing vital-sign messages). The file is automatically created in shared mode the first time the pubset is imported and must not be modified. Otherwise, the pubset cannot be used as a shared pubset until it has been exclusively imported and the watchdog file has been deleted.
XCS Configuration Manager (XCM)
Component of HIPLEX MSCF. Ensures global consistency in the XCS network by monitoring the XCS sharers and, in the event of configuration changes, by reconfiguring the distributed system functions which exist on the sharers.
XCS network
An XCS network combines up to 16 processors into one function network. CCS connections are established between all processors and the processors have imported at least one shared pubset (XCS pubset).
XCS pubset
A special shared pubset which is mandatory for the XCS network and is imported exclusively by the processors in an XCS network. The XCS pubset must be imported by all processors in this XCS network. An XCS network requires at least one XCS pubset.