Socketname Parameter

A socket name (the socketname parameter) may be a maximum of 16 characters long and may consist of any ASCII character. Upper and lower case characters are not considered distinct.

Nodename Parameter

A node name (the nodename parameter) refers to a remote node and has a hierarchical structure as follows:

node[.domain[.organization]]

Each node, domain, and organization name may be a maximum of 16 characters long. The maximum total length of a fullyqualified node name is 50 characters. All alphanumeric characters are allowed, including the underscore (_) and dash (-) characters, but the first character of each parameter must be alphabetic.

Loading NetIPC Programs

HP 1000 NetIPC programs should be compiled and linked as CDS programs. Refer to the RTEA Programmer's Reference Manual and RTEA Link Manual for more information on CDS programs. After the program is linked, an RTE executable file (type 6) is ready to be scheduled.

Process Scheduling

There are at least six different ways (listed below) to schedule a remote HP 1000 NetIPC process from another HP 1000 node. A remote HP 1000 NetIPC process must be ready to execute by being an RTE type 6 file.

DRemote Process Management (RPM). The RPMCreate call programmatically schedules a program.

DProgramtoProgram communication (PTOP). The POPEN call programmatically schedules a program.

DDistributed EXEC (DEXEC). One of the DEXEC scheduling calls, such as DEXEC 9, 10, 12, 23, 24, programmatically schedules a program.

DREMAT. The REMAT QU (queue schedule a program without wait) command interactively schedules a program.

DTELNET virtual terminal. Logon remotely with TELNET and use the RTE XQ (schedule a program without wait) command to interactively schedule a program.

DRTE WELCOME file. The WELCOME file can have RTE run commands to schedule programs after system boot up.

You cannot use any of the above NSARPA and DS/1000IV compatible services to schedule a remote HP 1000 process from a nonHP 1000 node. These services are not provided with crosssystem support.

Remote HP 1000 processes that are to work with nonHP 1000 processes can be manually started or can be programs that are started at system start up.

62 Network Interprocess Communication