HP XP Continuous Access Software - Manual (Page 369)

Porting notice for MPE/iX 369
HORCM daemon startup
HORCM can start as a daemon process from a UNIX Shell. But in the case
of MPE/iX, if a parent process exits, then any child process also dies at the
same time. In other words, it looks like MPE/iX POSIX cannot launch a
daemon process from a POSIX Shell. Therefore, horcmstart.sh has been
changed to wait until HORCM has exited after startup of the horcmgr.
According to the rules for MPE/iX, horcmstart.sh is run as a MPE JOB.
The following is an example of a JOB control file named JRAIDMR1 (
HORCMINST=1 ).
!job jraidmr1, manager.sys;pri=cs
!setvar TZ "PST8PDT"
!xeq sh.hpbin.sys '/HORCM/usr/bin/horcmstart.sh 1'
!eoj
When you execute this JOB in the background by using the STREAM
command of MPE/iX, you will have the HORCM daemon running in the
background. You will be able to verify that the HORCM daemon is running
as a JOB by using the SHOWJOB command.
shell/iX> callci STREAM JRAIDMR1
#J15
shell/iX> callci SHOWJOB
Command device
Because MPE/iX POSIX does not provide raw I/O such as UNIX, RAID
manager has used the SCSI pass-thru driver to access the command device
on XP256/512, and is also using the normal read/write SCSI commands for
some RM control operations.
You need to confirm that MPE/iX has installed the patch MPEKXU3
before using the SCSI pass-thru driver
JOBNUM STATE IPRI JIN JLIST INTRODUCED JOB NAME
#J14 EXEC 10S LP WED 9:02P JRAIDMR0,MANAGER.SYS
#J15 EXEC 10S LP WED 9:02P JRAIDMR1,MANAGER.SYS
#S28 EXEC QUIET 9 9 WED 9:10P MANAGER.SYS