HP XP P9500 Configuration Manual page 20

(3) IPC method using MailBox driver
As an alternate method of the UNIX domain socket for IPC (Inter Process Communication), RAID
Manager use the mailbox driver to enable the communication between RAID Manager and HORCM.
Therefore, if RAID Manager and HORCM are executing in different jobs (different terminal), then
you must redefine LNM$TEMPORARY_MAILBOX in the LNM$PROCESS_DIRECTORY table as follows:
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
(4) Startup method for HORCM daemon
HORCM can start as the daemon process from a UNIX Shell. But in the case of 'vfork' of CRTL, if
a parent process has exit() then a child process also ends at the same time. In other words it looks
that OpenVMS cannot make a daemon process from the POSIX program. Therefore, horcmstart.exe
has been changed to wait until HORCM has been exiting by horcmshutdown.exe after startup of
the horcmgr. According to the rule for creating process in OpenVMS, to start up the horcmstart.exe
is to create the detached process or Batch JOB by using DCL command, as this method closely
resembles the horcmd process on UNIX.
For example, using the Detached process:
If you want to have the HORCM daemon running in the background, you need to make the
Detached LOGINOUT.EXE Process by using the 'RUN /DETACHED' command of the OpenVMS,
and need to make the commands file for LOGINOUT.EXE.
The following are examples of "loginhorcm*.com" file given to SYS$INPUT for LOGINOUT.EXE,
and are examples that "VMS4$DKB100:[SYS0.SYSMGR.]" was defined as SYS$POSIX_ROOT.
loginhorcm0.com
$ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT
$ DEFINE DCL$PATH SYS$POSIX_ROOT:[horcm.usr.bin],SYS$POSIX_ROOT:[horcm.etc]
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
$ horcmstart 0
loginhorcm1.com
$ DEFINE/TRANSLATION=(CONCEALED,TERMINAL) SYS$POSIX_ROOT
$ DEFINE DCL$PATH SYS$POSIX_ROOT:[horcm.usr.bin],SYS$POSIX_ROOT:[horcm.etc]
$ DEFINE/TABLE=LNM$PROCESS_DIRECTORY LNM$TEMPORARY_MAILBOX LNM$GROUP
$ horcmstart 1
$ run /DETACHED SYS$SYSTEM:LOGINOUT.EXE /PROCESS_NAME=horcm0 -
_$ /INPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]loginhorcm0.com -
_$ /OUTPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run0.out -
_$ /ERROR=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run0.err
%RUN-S-PROC_ID, identification of created process is 00004160
$
$
$$ run /DETACHED SYS$SYSTEM:LOGINOUT.EXE /PROCESS_NAME=horcm1 -
_$ /INPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]loginhorcm1.com -
_$ /OUTPUT=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run1.out -
_$ /ERROR=VMS4$DKB100:[SYS0.SYSMGR.][horcm]run1.err
%RUN-S-PROC_ID, identification of created process is 00004166
You can also verify that the HORCM daemon is running as Detached Process by using the show
process command.
$ show process horcm0
25-MAR-2003 23:27:27.72
Terminal:
User Identifier:
Base priority:
Default file spec:
Number of Kthreads: 1
Soft CPU Affinity: off
$$ horcmshutdown 0 1
inst 0:
20 Installation requirements
User: SYSTEM
Node: VMS4
[SYSTEM]
4
Not available
"VMS4$DKB100:[SYS0.SYSMGR.]"
"VMS4$DKB100:[SYS0.SYSMGR.]"
Process ID:
Process name: "HORCM0"
00004160