HSMS consists of a privileged component (Task PRivileged, TPR modules) and a nonprivileged component (Task Unprivileged, TU load module).
The privileged component is implemented as a subsystem. This subsystem HSMS is loaded into the system memory area (class 4 memory).
HSMS must be loaded for a BS2000 session by a user equipped with the “subsystem management” privilege. After loading, HSMS is available to all users. HSMS is called by individual users via a load module.
The period of time between loading and unloading the HSMS subsystem is referred to in this manual as an HSMS session.
There are two alternative methods of loading HSMS:
Users assigned the “subsystem management” privilege can use the following DSSM command to load HSMS:
/START-SUBSYSTEM SUBSYSTEM-NAME=HSMS
HSMS is unloaded using the DSSM command
/STOP-SUBSYSTEM SUBSYSTEM-NAME=HSMS
If HSMS is loaded using a DSSM command, no control parameters can be passed to
HSMS. Use of the DSSM commands permits HSMS to be loaded directly in a CMDFILE at BS2000 startup.
A user with the “subsystem management” privilege can load HSMS after calling the
TU program HSMS (see section "Calling HSMS") by issuing the following statement:
//START-HSMS
This HSMS statement can be used to pass control parameters for the HSMS run (see “HSMS Vol. 2” [1], START-HSMS statement).
HSMS is unloaded with the statement:
//STOP-HSMS
Additional parameters controlling the unloading of HSMS can also be included with this HSMS statement (see “HSMS Vol. 2” [1], STOP-HSMS statement).
HSMS-SV is no longer included in the delivery package in HSMS V9.0B and higher. Consequently HSMS V9.0B or higher only supports workstations which are connected to the local BS2000-UFS via NFS.
HSMS attempts to start the ARCHIVE subsystem. If it does not succeed, HSMS itself likewise fails to start.
Any parameters modified temporarily during an HSMS session are lost even after a /HOLD-SUBSYSTEM or //STOP-HSMS SUBSYSTEM=HOLD followed by a restart.
One thing that happens when HSMS is loaded is that the BCAM host names that are to be valid for the HSMS session are defined. If work is to take place not only on the local computer, HSMS may not therefore be loaded until BCAM has been started.