NetIPC itself does not include a call to schedule a peer process.
In programs communicating between multiple HP 3000 systems, you
can use the Remote Process Management (RPM) call, RPMCREATE, to programmatically schedule program execution.
However, RPM between HP 3000 and HP 1000 systems, and between HP
3000 and HP 9000 systems, is not currently supported by
Hewlett-Packard. Instead, you must manually start up each NetIPC
program on its respective system.
HP 3000 Program Startup |
 |
To manually start up an HP 3000 NetIPC program, log on to
the HP 3000 and run the NetIPC program (with the RUN command).
You can schedule the program to start at a particular time
by writing a job file to execute the program, and then including
time and date parameters in the :STREAM command that executes the job file.
HP 1000 Program Startup |
|
To manually start up an HP 1000 NetIPC program, simply logon
to the HP 1000 system and run the NetIPC program with the RTE XQ (run program without wait) command.
To have the NetIPC program execute at system start up, put
the RTE XQ command in the WELCOME file.
HP 9000 Program Startup |
|
Remote HP 9000 processes can be manually started or can be
scheduled by daemons that are started at system start up. In HP-UX
a daemon is a process that runs continuously and usually performs
system administrative tasks. Although a daemon runs continuously,
it performs actions either at a specified time, or upon a specified
event.
To manually start up a NetIPC program, simply logon to the
HP 9000 system and run the NetIPC program. HP recommends that you
write a NetIPC daemon to schedule your NetIPC programs. You can
start the daemon at start up by invoking it from the /etc/netlinkrc file. Refer to the NS/ARPA Services/9000
Series 800 Node Manager's Guide for more information
about this file and system start up.
PC NetIPC Program Startup |
|
To manually start up a PC NetIPC program, enter the NetIPC
program name at the MS-DOS prompt.
To execute from within MS-Windows, copy the NetIPC program
files to your Windows directory and double click the mouse on the
executable file.
