HP XP RAID Manager Software - Manual (Page 375)

Porting notice for MPE/iX 375
This problem is resolved by RM010904(3), which supports the traffic
control method for MPE socket.
The traffic control method is to limit sending the packets for multiple
commands at the same time, and over-packets are queued (FIFO) to wait
until sending the next packets.The queued packets are sent after a reply is
received for the sent message. This method controls the amount of packets
that are sent to the remote host at the same time. The amount of packets are
controlled by the HORCMTRFCTL environment variable for HORCM.
The default for the amount of packets for MPE is one
(HORCMTRFCTL=1).
HORCMTRFCTL is effective for all (other) platforms, but the default is
not controlled (HORCMTRFCTL=0).
In RM 1.09.02 or earlier, the following is needed to avoid this problem.
• Isolates RM instances with groups performing at the same time.
This will isolate the message on the socket. A maximum number of
RM instances are 32 on one command device. (In the case of NO
RMLIB).
• Uses '-l' option (pairsplit -l, pairresync -l, pairevtwait -l) on PVOL
instance. This will not use the remote RM instance except paircreate.
Known issues and concerns
MPE panic with the “rm” command
The MPE POSIX layer is unable to execute the rm command when the
directory you are trying to remove is pointed to by a symbolic link. In
/HORCM there is a symbolic link to /users/HORCM. While trying to
remove the directory under this symbolic link (two levels down), it gets a
nil pointer causing a system failure. This is entirely attributed to a POSIX
bug and HP realizes that it is a critical bug that needs to be fixed soon; it
has been submitted as an urgent request for a fix.
Display of the “dstat” command
DSTAT can only display up to 12 characters for the product-id.