Using NS3000/iX Network Services (36920-90008)

142 Chapter 7
Remote Process Management
RPMCREATE
remote process and then do not abort the remote session, you can
subsequently issue commands in the remote session. See “Releasing a
Remote Environment” in the “Virtual Terminal” chapter of this manual.
RPMCREATE can also create a new process on the local node. The new
process will be created in your local session if (1) the location and login
parameters are omitted or blank or (2) location is the local node name
and login is the logon for your local session (including session name, if
any). A new process will also be created on your local node, but in a
different session, if (1) you specify your local node name, and a logon
different from your own and (2) software loopback has been configured
and activated for your local node.
Bit 31 (the low-order bit) of the flags parameter determines whether the
newly created process will be dependent on its creator or independent
(the default). A local dependent process that was created under the
same logon as its creator will terminate automatically when the creator
terminates. (In order to conserve system resources, you should make
local processes independent; that is, set the bit off.)
A remote dependent process will terminate if:
• RPMKILL has been called for the dependent process.
• The creator process terminates before calling RPMKILL.
• The transport fails.
• The system on which the creator is running fails.
If the remote process is independent, it will continue to execute unless
explicitly terminated by RPMKILL. Dependent mode ensures that the
new process will not become an “orphan” in the event of a program,
system, or network link failure. However, independent mode is less
costly in terms of resources: the connection set up for the RPMCREATE is
not maintained after the remote process is created. You should
normally use independent mode for processes that are expected to
terminate themselves.
Preferred Method of Creating Interactive
Programs
RPM works best to create non-interactive server programs on a remote
system. If you use RPM to create interactive programs, some
restrictions exist (described in a following section). Therefore, as an
alternative to using the RPMCREATE intrinsic to create interactive
programs, HP recommends that you call the REMOTE RUN command
from the COMMAND intrinsic. Using this method will suspend the master
process in the COMMAND intrinsic while the slave program runs. Only
use RPMCREATE if you require parallel execution of a master and slave
process.