rfc407.txt

RFC技术文档 从0000－05

                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112


Robert Bressler, MIT-DMCG                              Obsoletes RFC 360
Richard Guida, MIT-DMCG
Alex McKenzie, BBN-NET


























                       REMOTE JOB ENTRY PROTOCOL

                                               REMOTE Job Entry Protocol
                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112


                       REMOTE JOB ENTRY PROTOCOL

INTRODUCTION

   Remote job entry is the mechanism whereby a user at one location
   causes a batch-processing job to be run at some other location.  This
   protocol specifies the Network standard procedures for such a user to
   communicate over the Network with a remote batch-processing server,
   causing that server to retrieve a job-input file, process the job,
   and deliver the job's output file(s) to a remote location.  The
   protocol uses a TELNET connection (to a special standardized logger,
   not socket 1) for all control communication between the user and the
   server RJE processes.  The server-site then uses the File Transfer
   Protocol to retrieve the job-input file and to deliver the output
   file(s).

   There are two types of users:  direct users (persons) and user
   processes.  The direct user communicates from an interactive terminal
   attached to a TIP or any host.  This user may cause the input and/or
   output to be retrieved/sent on a specific socket at the specified
   host (such as for card readers or printers on a TIP), or the user may
   have the files transferred by file-id using File Transfer Protocol.
   The other type of user is a RJE User-process in one remote host
   communicating with the RJE Server-process in another host.  This type
   of user ultimately receives its instructions from a human user, but
   through some unspecified indirect means.  The command and response
   streams of this protocol are designed to be readily used and
   interpreted by both the human user and the user process.

   A particular user site may choose to establish the TELNET control
   connection for each logical job or may leave the control connection
   open for extended periods.  If the control connection is left open,
   then multiple job-files may be directed to be retrieved or optionally
   (to servers that are able to determine the end of one logical job by
   the input stream and form several jobs out of one input file) one
   continuous retrieval may be done (as from a TIP card reader).  This
   then forms a "hot" card reader to a particular server with the TELNET
   connection serving as a "job monitor".  Since the output is always
   transferred job at a time per connection to the output socket, the
   output from this "hot" reader would appear when ready as if to a
   "hot" printer.  Another possibility for more complex hosts is to
   attach an RJE User-process to a card reader and take instructions
   from a lead control card, causing an RJE control TELNET to be opened
   to the appropriate host with appropriate log-on and input retrieval
   commands.  This card reader would appear to the human user as a
   Network "hot" card reader.  The details of this RJE User-process are
   beyond the scope of this protocol.





                                   1

                                               REMOTE Job Entry Protocol
                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112


GENERAL SPECIFICATIONS

   User

      A human user at a real terminal or a process that supplies the
      command control stream causing a job to be submitted remotely will
      be termed the User.  The procedure by which a process user
      receives its instructions is beyond the scope of this protocol.

   User TELNET

      The User communicates its commands over the Network in Network
      Virtual Terminal code through a User TELNET process in the User's
      Host.  This User TELNET process initiates its activity via ICP to
      the standard "RJE Logger" socket (socket 5) at the desired
      RJE-server Host.

   RJE-Server TELNET

      The RJE-server process receives its command stream from and sends
      its response stream to the TELNET channel through an RJE-server
      TELNET process in the server host.  This process must listen for
      the ICP on the "RJE Logger" socket (and cause appropriate ICP
      socket shifting).

   TELNET Connection

      The command and response streams for the RJE mechanism are via a
      TELNET-like connection to a special socket with full
      specifications according to the current NWG TELNET protocol.

   RJE-Server

      The RJE-Server process resides in the Host which is providing
      Remote Batch Job Entry service.  This process receives input from
      the RJE-server TELNET, controls access through the "log-on"
      procedure, retrieves input job files, queues jobs for execution by
      the batch system, responds to status inquiries, and transmits job
      output files when available.

   User FTP

      All input and output files are transferred under control of the
      RJE-server process at its initiative.  These files may be directly
      transferred via Request-for-connection to a specific Host/socket
      or they may be transferred via File Transfer Protocol.  If the
      latter method is used, then the RJE-server acts through its local
      User FTP process to cause the transfer.  This process initiates




                                   2

                                               REMOTE Job Entry Protocol
                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112
                                                                        
                                                                        
      activity by an active Request-for-connection to the "FTP Logger"
      in the foreign host.

   Server FTP

      This process in a remote host (remote from the RJE-server) listens
      for an ICP from the User FTP and then acts upon the commands from
      the User FTP causing the appropriate file transfer.

   FTP

      When File Transfer Protocol is used for RJE files, the standard
      FTP mechanism is used as fully specified by the current NWG
      FTProtocol.

   RJE Command Language

      The RJE system is controlled by a command stream from the User
      over the TELNET connection specifying the user's identity
      (log-on), the source of the job input file, the disposition of the
      job's output files, enquiring about job status, altering job
      status or output disposition.  Additional commands affecting
      output disposition are includable in the job input file.  This
      command language is explicitly specified in a following section of
      this protocol.

   RJE Command Replies

      Every command input from the User via TELNET calls for a response
      message from the RJE-server to the User over the TELNET
      connection.  Certain other conditions also require a response
      message.  These messages are formatted in a standardized manner to
      facilitate interpretation by both human Users and User processes.
      A following section of this protocol specifies the response
      messages.

















                                   3

                                               REMOTE Job Entry Protocol
                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112
                                                                        
                                                                        
RJE COMMANDS OVER TELNET CONNECTION

   GENERAL CONVENTIONS

   1. Each of the commands will be contained in one input line
      terminated by the standard TELNET "crlf".  The line may be of any
      length desired by the user (explicitly, not restricted to a
      physical terminal line width).  The characters "cr" and "lf" will
      be ignored by the RJE-server except in the explicit order "crlf"
      and may be used as needed for local terminal control.

   2. All commands will begin with a recognized command name and may
      then contain recognized syntactic element strings and free-form
      variable strings (for user-id, file-ids, etc.).  Recognized words
      consist of alphanumeric strings (letters and digits) or
      punctuation.  Recognized alphanumeric string elements must be
      separated from each other and from unrecognizable strings by at
      least one blank or a syntacticly permitted punctuation.  Other
      blanks may be used freely as desired before or after any syntactic
      element ("blank" is understood here to mean ASCII SPACE (octal
      040); formally:  <blank>::= <blank><ASCII SPACE> | <ASCII SPACE> ;
      thus, a sequence of SPACES is also permissible in place of
      <blank>, although there is no syntactic necessity for there to be
      more than one).  The "=" after the command name in all commands
      except OUT and CHANGE is optional.

   3. Recognized alphanumeric strings may contain upper case letters or
      lower case letters in any mixture without syntactic
      differentiation.  Unrecognizable strings will be used exactly as
      presented with full differentiation of upper and lower case input,
      unless the host finally using the string defines otherwise.

   4. There are two types of Unrecognizable strings:  final and
      imbedded.  Final strings appear as the last syntactic element of a
      command and are parsed as beginning with the next non-blank
      character of the input stream and continuing to the last non-blank
      character before the "crlf".

   Imbedded strings include "job-id" and "job-file-id" in the OUT,
   CHANGE, and ALTER commands.  At present these fields will be left
   undelimited since they must only be recognizable by the server host
   which hopefully can recognize its own job-ids and file-names.

   SYNTAX

   The following command descriptions are given in a BNF syntax.  Names
   within angle brackets are non-terminal syntactic elements which are
   expanded in succeeding syntactic equations.  Each equation has the




                                   4

                                               REMOTE Job Entry Protocol
                                                         (Oct. 16, 1972)
                                                       RFC 407 NIC 12112
                                                                        
                                                                        
   defined name on the left of the ::= and a set of alternative
   definitions, separated by vertical lines "|", on the right.

   REINITIALIZE

      REINIT

         This command puts the user into a state identical to the state
         immediately after a successful connection to the RJE-server,
         prior to having sent any commands over the TELNET connection.
         The effective action taken is that of an ABORT and a flushing
         of all INPUT, OUTPUT and ID information.  Naturally, the user
         is still responsible for any usage charges incurred prior to
         his REINIT command.  The TELNET connection is not affected in
         any way.

   USER

      User = <user-id>

         This command must be the first command over a new TELNET
         connection.  As such, it initiates a "logon" sequence.  The
         response to this command is one of the following:

            1.  User code in error.
            2.  Enter password (if user code ok).
            3.  Log-on ok, proceed (if no password requested).