RFC 283 (rfc283) - Page 3 of 9

NETRJT: Remote Job Service Protocol for TIPS

In the longer term, we believe that the NETRJT protocol described
here should be considered as the first draft of a Network standard for
remote job entry via TIP's. In its present form, NETRJT owes much to
the ideas and comments of Alex McKenzie (BBN), Jon Postel (NMC), Jim
White (UCSB), and Steve Wolfe (CCN).

B.  NETRJT COMMANDS
    ---------------

 NETRJT provides the following commands over the remote operator
connection, in addition to the NETRJS operator commands (see Appendix
D of RFC #189). The symbol "#" denotes one or more spaces.  We will
use the IBM meta-language to describe the command syntax. The literal
text shown here in upper case may, in fact, be entered in either upper
or lower case.

   1. Opening a Stream
      ----------------

               /            \           
               | PR [INTER] |  _         _
               |            | |           |
    O [PEN] # | (jobname) | [ =socket-number[ /host-name ]]
               |            | |           |
               | R  [EADER] | |   (*)     |
               \            / |_         _|


 If the specified device does not already have an open connection, the
NETRJT server will request connection to the specified socket. The
optional "(jobname)" para- meter is used to specify a particular job
by name; for more information on the semantics of this parameter, see
the discussion of input and output operations below. The "/host-name"
parameter, to be implemented later, is intended to allow the file to
be at a host different from both user and server hosts. We include it
here only to suggest a syntax.

 The socket number may have a one-letter suffix D, H, or O to mean
decimal, hex, or octal. Octal is the default, so the O suffix may be
omitted.  If BBN establishes standardized TIP sockets for specific
unit record devices, the socket number parameter could be omitted when
the standard socket number is intended.