HP XP Continuous Access Software - Manual (Page 383)

Porting notice for OpenVMS 383
Example $ spawn /NOWAIT /PROCESS=horcm0 horcmstart 0
%DCL-S-SPAWNED, process HORCM0 spawned
$
starting HORCM inst 0
$ spawn /NOWAIT /PROCESS=horcm1 horcmstart 1
%DCL-S-SPAWNED, process HORCM1 spawned
$
starting HORCM inst 1
$
Note that the subprocess (HORCM, the RM daemon) created by spawn
will be terminated when the terminal is logged off or the session is
terminated. To run the process independently of LOGOFF, use the RUN
/DETACHED
command.
Privileges for using RAID Manager
• A user account for RAID Manager must have the same privileges as
“SYSTEM” (that is, it must be able to use the SCSI class driver and
Mailbox driver directly). Some OpenVMS system administrators may
not allow RAID Manager to run from the system account. In this case,
create another account on the system, such as “RMadmin” that has the
same privileges as “SYSTEM.”
• RAID Manager uses the Mailbox driver for communication between
the RAID Manager components. So, the RAID Manager command
processor and RM daemon (called HORCM) must have the same
privileges.
If the RAID Manager command processor and HORCM execute with
different privileges, then the RAID Manager command processor will
hang or be unable to attach to the daemon.
Installation
RAID Manager requires that the logical name sys$posix_root exist on the
system. Define sys$posix_root before installing RAID Manager.
It is recommended that the three logical names shown below be defined in
LOGIN.COM prior to RAID Manager installation: