Lines Matching full:program
42 or more remote programs. A remote program implements one or more
44 documented in the specific program's protocol specification (see the
45 \fIPort Mapper Program Protocol\fP\, below, for an example). Network
48 program in order to be forward compatible with changing protocols.
51 One program may deal with high-level applications such as file system
152 itself\(emsee the \fIPort Mapper Program Protocol\fP\, below).
189 Remote program protocol version mismatches.
199 The RPC call message has three unsigned fields: remote program
200 number, remote program version number, and remote procedure number.
202 Program numbers are administered by some central authority (like
203 Sun). Once an implementor has a program number, he can implement his
204 remote program; the first implementation would most likely have the
212 numbers are documented in the specific program's protocol
217 Just as remote program protocols may change over several versions,
228 The remote program is not available on the remote system.
230 The remote program does not support the requested version number.
231 The lowest and highest supported remote program version numbers are
284 Program numbers are given out in groups of
291 Program Numbers&Description
310 group is for applications that generate program numbers dynamically.
341 its semantics. See the \fIPort Mapper Program Protocol\fP\, below,
376 PROG_UNAVAIL = 1, /* \fIremote hasn't exported program \fP*/
378 PROC_UNAVAIL = 3, /* \fIprogram can't support procedure \fP*/
441 * remote program, its version number, and the procedure within
442 * the remote program to be called. After these fields are two
446 * procedure, which are specified by the specific program
487 * the lowest and highest version numbers of the remote program
544 the same rules of flavor number assignment as there is for program
987 Here is an example of the specification of a simple ping program.
993 * Simple ping program
996 program PING_PROG {
1048 for compatibility with old client programs, and as this program
1056 .I program-def
1060 program-def:
1061 "program" identifier "{"
1081 identifiers: "program" and "version";
1084 a program definition. Nor can a version number occur more than once
1085 within the scope of a program definition.
1091 Program identifiers are in the same name space as constant and
1097 \&Port Mapper Program Protocol
1099 The port mapper program maps RPC program and version numbers to
1100 transport-specific port numbers. This program makes dynamic binding
1108 The port mapper also aids in broadcast RPC. A given RPC program will
1112 broadcast to a given program, the client actually sends its message
1128 * A mapping of (program, version, protocol) to port number
1192 program PMAP_PROG {
1218 The portmapper program currently supports two protocols (UDP/IP and
1226 When a program first becomes available on a machine, it registers
1227 itself with the port mapper program on the same machine. The program
1228 passes its program number "prog", version number "vers", transport
1238 When a program becomes unavailable, it should unregister itself with
1239 the port mapper program on the same machine. The parameters and
1244 Given a program number "prog", version number "vers", and transport
1246 which the program is awaiting call requests. A port value of zeros
1247 means the program has not been registered. The "port" field of the
1251 The procedure takes no parameters and returns a list of program,
1258 "vers", "proc", and the bytes of "args" are the program number,
1268 The port mapper communicates with the remote program using UDP/IP
1272 The procedure returns the remote program's port number, and the bytes
1294 Program Protocol Specification", RFC 793; Information Sciences