rfc477.txt

RFC 的详细文档！

   <socket> = [<host addr> ','] <socket number> <attributes>
   <file> = <host addr> <attributes> '/' <filename>
   <host addr> = <integer>
   <socket number> = <integer>
   <integer> = <decimal integer> _ ('D' <decimal integer>) _
   ('H' <hexadecimal integer>) _ ('X' <hexadecimal integer>) _
   ('O' <octal integer>)
   <attributes> = ':T' _ ':A' _ ':N' _ ':' _ <null> _ ':E' _
   ':TE' _ ':AE' _ ':NE'
   <filename> = 1 to 16 ASCII characters, excluding CR and LF
   (codes 0 through 127, excluding 10 and 13)

   Sets the source pathname accumulator to <pathname>.  The <pathname>
   is the means for specifying a file's source or destination; its
   semantics are as follows:


      1. Specification of <socket> indicates that RJS will establish a
         simplex connection to the stated socket (RJS issuing the
         CONNECT, user issuing a LISTEN).  The data is then transferred
         over this connection, with CLOSE signaling end of file.

      2. If <host addr> in <socket> is defaulted, the host containing
         the TELNET user will be assumed.

      3. Specification of <file> indicates that RJS will contact the
         standard FTP server socket (currently socket 3) at the stated
         host, and transfer the data according to the File Transfer
         Protocol.  The <file name> referred to here corresponds to the
         term <pathname> used in the FTP specification document, RFC
         #354.






Krilanovich                                                     [Page 7]

RFC 477                Remote Job Service at UCSB            23 May 1973


      4. The type of carriage control and the data code used are
         determined by <attributes>.  The meaning of this parameter is
         as follows:

         ':T'        ASCII code, TELNET carriage control
         ':A'        ASCII code, ASA carriage control
         ':N'        ASCII code, no carriage control
         ':'         identical to ':N' for input, ':A' for output
         <null>      identical to ':N' for input, ':A' for output
         ':E'        identical to ':NE' for input, ':AE' for output
         ':TE'       EBCDIC code, TELNET carriage control
         ':AE'       EBCDIC code, ASA carriage control
         ':NE'       EBCDIC code, no carriage control

         Detailed descriptions of the transfer modes may be found
         below under 'RJS File Transfer.'

   ('OUTPATH' _ 'OUT') <output file> '=' <disp> <CA>
   <output file> = 'A' _ 'B' _ <null>
   <disp> = <pathname> _ '(H)' _ ('(S)' (pathname>) _ '(D)'

   Stores <disp> in the print pathname accumulator if <output file> is
   either 'A' or <null>, or in the punch pathname accumulator if <output
   file> is 'B'.  The meanings of the options for <disp> are as follows:

   <pathname>            transmit-and-discard - the file is sent and
                         then deleted

   '(H)'                 hold only - the file is not sent but rather
                         held for user intervention

   '(S)' <pathname>      save - the file is sent and then held for user
                         intervention

   '(D)'                 discard - the file is deleted as soon as it is
                         produced

   'INPUT' <CA>

   Creates a job, stores with it the contents of the source, print, and
   punch accounting parameter and pathname accumulators, and places it
   in a queue within RJS of jobs owned by the user awaiting source file
   transfer.  When it becomes the first or only job in this queue, the
   retrieval of its source file is initiated.  A job identifier
   ('jobid') is assigned to the job and displayed to the user.  The
   contents of the source and print pathname accumulators must have been
   set by INPATH and OUTPATH commands previous to the INPUT command.  If
   successful, the message '260 ASSIGNED JOBID IS <jobid>.' is



Krilanovich                                                     [Page 8]

RFC 477                Remote Job Service at UCSB            23 May 1973


   displayed, where <jobid> is that which may used in subsequent RJS
   commands to identify this particular job.  If the user is found to
   own the maximum number of jobs (currently 5), an attempt is made to
   satisfy the request by finding the oldest of the user's jobs that has
   completed processing.  If this can be done, the old job is deleted,
   and the response to the command is '260 JOB <old jobid> IS BEING
   DISCARDED TO MAKE ROOM FOR THE NEW JOB.', followed by a continuation
   line of 'ASSIGNED JOB ID IS <new jobid>.'  The following error
   responses are possible:  '360 SOURCE PATHNAME HAS NOT BEEN
   SPECIFIED.', '505 PRINT PATHNAME HAS NOT BEEN SPECIFIED.', '504 NEW
   JOBS ARE NOT BEING ACCEPTED AT THIS TIME.', and '504 USER (user name>
   ALREADY OWNS THE MAXIMUM NUMBER OF JOBS.'

   'CHANGE' <jobid> <output file> '=' <disp> <CA>

   Stores <disp> as the print pathname of job <jobid> if <output file>
   is either 'A', or <null>, or as the punch pathname if <output file>
   is 'B', if the appropriated file transfer has not yet begun.  The
   following error replies are possible:  '464 JOB <jobid> NOT FOUND.',
   '5O4 JOB <jobid> IS ALREADY BEING, OR HAS BEEN, PRINTED.', if <output
   file> is 'A', '504 JOB <jobid> IS ALREADY BEING OR HAS BEEN,
   PUNCHED.', if <output file> is 'B', and '464 USER <user name> DOES
   NOT OWN JOB <jobid>.'

   'STATUS' <jobid> <CA>

   Causes the status of the job known to RJS as <jobid> to be displayed.
   Included in this display are in which stage of RJS processing the job
   is ('BEING READ', 'IN EXECUTION', 'BEING PRINTED', 'BEING PUNCHED',
   or 'HAS COMPLETED'), the pathname information (accounting parameters,
   host name, socket number, attributes, disposition, and filename) for
   those files (source, print and punch) that have been supplied for the
   job, and if the job has failed at some stage of RJS processing, an
   explanation of the failure.  The possible responses are '464 JOB
   <jobid> NOT FOUND.', and a line with reply code 161 followed by zero
   or more continuation lines explaining the status of the job.

   'CANCEL' <jobid> <CA>

   Causes processing of the job known to RJS as <jobid> to terminate
   immediately, and all record of it to be deleted.  If FTP data and/or
   command connections are pending or established, they are closed; if
   the job is in execution, an OS CANCEL command is issued to terminate
   execution.  Any output from the job is lost, and a subsequent request
   for status of job <jobid> will return the diagnostic that the job is
   not found.  The successful responses are '262 JOB <jobid> DELETED.'





Krilanovich                                                     [Page 9]

RFC 477                Remote Job Service at UCSB            23 May 1973


   and '262 JOB <jobid> WILL BE DELETED AS SOON AS POSSIBLE.'; the
   possible failure responses are '464 JOB NOT FOUND.' and '464 USER
   <user name> DOES NOT OWN JOB <jobid>.'

   The following standard RJS commands are as yet not implemented, and
   elicit the response '506 COMMAND NOT IMPLEMENTED.':  ABORT, ALTER,
   BACK, HOLD, OP, RECOVER, RESTART, and SKIP.

RJS Commands - Local Syntax Conventions

   In addition to those general conventions discussed above, the
   following rules hold for local syntax:

      1. Except in certain circumstances, noted below, a period may be
         used for command accept.

      2. The following control characters have the indicated functions:

      SOH (control A)  delete last character
      DEL              delete last character
      SYN (control V)  delete last word
      CAN (control X)  delete entire line
      EOT (control D)  display current word
      ACK (control F)  display entire line
      '?'              display acceptable input forms
      ESC              force recognition of current word
      blank            force recognition of current word


      3. The TELNET control characters 'you-echo' and 'I-echo' have the
         desired results.  'You-echo' also has the effect of changing to
         character at a time mode, if the user is not already in
         character at a time mode.

Description of RJS Commands, Local Syntax

   The following is a list of those commands supported in local syntax.
   In those cases where no success reply is indicated, RJS responds with
   CR-LF followed by the prompt character.  In those cases where it is
   stated that the user must be, or must not be, logged in, 'LOGIN
   PLEASE.' or 'LOGGED IN.', respectively, are displayed if the user is
   not in the appropriate state.  When a reference is made to a response
   listed under a standard syntax command, it should be noted that reply
   id's are not displayed under local syntax.

   'FULLDUPLEX' <CA>

   Sets the user to fullduplex and character at a time modes.



Krilanovich                                                    [Page 10]

RFC 477                Remote Job Service at UCSB            23 May 1973


   'HALFDUPLEX' <CA>

   Sets the user to halfduplex mode.

   'LINE<-AT<-A<-TIME' <CA>

   Set's the user to halfduplex, line at a time modes.  The control
   characters previously described remain effective, but RJS will send
   no output over the TELNET connection except when the current command
   line is empty.

   'LOGIN' <user name> <password> <account> <CA>

   Specifies the UCSB Computer Center user name and account to which the
   user's use Of RJS is to be billed, logs the user in, and sets the
   source, print, and punch accounting parameter accumulators to <user
   name>, <password> and <account>.  This command is valid only if the
   user is not logged in, and has the same replies as the standard
   syntax 'PASS' command.

   'DISCONNECT' <CA>

   Closes the TELNET connection.  If the user is logged in, he is first
   logged out.  The effective action taken in response to an unexpected
   close on the TELNET connection is that of a DISCONNECT.  The response
   to a DISCONNECT command is 'TTY <integer> IS DISCONNECTED.'

   The remaining commands require the user to be logged in.

   'LOG0UT' <CA>

   Logs the user out and terminates billing of subsequent activity over
   the TELNET connection to the previously effective accounting
   parameters, and performs the effective action of the REINITIALIZE
   command.  LOGOUT does not close the TELNET connection, nor does it
   affect any file transfers in progress for jobs owned by the user.

   'REINITIALIZE' <CA>

   Resets to empty the following accumulators:  source, print and punch
   accounting parameter, source, print and punch pathname, and login
   accounting parameter.

   'ACCOUNTING' <account parms> <CA>
   <account parms> = '(' <u> ',' <p> ',' <a> ')'
   <u> = <user name> _ <null>
   <p> = <password> _ <null>
   <a> = <account> _ <null>



Krilanovich                                                    [Page 11]

RFC 477                Remote Job Service at UCSB            23 May 1973


   Sets the source, print and punch accounting parameters to <account
   parms>.  Specification of <null> for any of <u>, <p>, or <a>
   indicates use of the contents of the corresponding login accumulator.

   'SOURCE' <account parms> <CA>

   Set the source accounting parameter accumulators to <account parms>.

   'PRINT' <account parms> <CA>

   Sets the print accounting parameter accumulators to <account parms>.

   'PUNCH' <account parms> <CA>

   Sets the punch accounting parameter accumulators to <account parms>.

   'SOURCE' <jobid> (<account parms> _ <null>) <pathname> <CA>

   Sets the source pathname of job <jobid> to <pathname>, and the source
   accounting parameters to <account parms>, if specified, or otherwise
   to the contents of the source accounting parameter accumulators.  If
   job <jobid> already exists and its source pathname has not been
   specified, the new pathname is stored; if it has been specified, it
   is changed unless source file retrieval has already begun.  If the
   job does not already exist, a new job is created and the pathname
   stored.  Restrictions are that if a job with a given <jobid> has
   completed processing, it must be DELETE'd before that <jobid> may be
   used for a new job; a user may only alter jobs owned by him; and he
   may not own more than a certain fixed number of jobs (currently 5).
   If the user already owns the maximum number, an attempt is made to
   delete an old job to make room for the new one, as described for
   INPUT under standard syntax.  The SOURCE command has the following
   possible error responses:  'NEW JOBS ARE NOT BEING ACCEPTED AT THIS
   TIME.', 'USER <user name> ALREADY OWNS THE MAXIMUM NUMBER OF JOBS.',
   'USER <user name> DOES NOT OWN JOB <jobid>.', 'JOB <jobid> HAS
   ALREADY COMPLETED.', and 'JOB <jobid> IS ALREADY BEING, OR HAS BEEN,
   READ.'

   'PRINT <jobid> (<account parms> _ <null>) <disp> <CA>

   Sets the print pathname of job <jobid> to <disp>, and the print
   accounting parameters to <account parms> if specified, or otherwise
   to the contents of the print accounting parameter accumulators.  The
   PRINT command either creates a new job or modifies an existing one,
   as explained under SOURCE, and has the same restrictions and error
   messages listed for the SOURCE command, after making the obvious
   substitution of 'PRINTED' for 'READ'.  The PRINT command is valid
   only before print file transfer begins.



Krilanovich                                                    [Page 12]

RFC 477                Remote Job Service at UCSB            23 May 1973


   'PUNCH' <jobid> (<account parms> _ <null>) <disp> <CA>

   Sets the punch pathname of job <jobid> to <disp>, and the punch
   accounting parameters to <account parms> if specified, or otherwise
   to the contents of the punch accounting parameter accumulators.  The
   PUNCH command either creates a new job or modifies an existing one,
   like the SOURCE and PRINT commands, and has the same restrictions and
   error messages listed for the SOURCE command, after making the
   substitution of 'PUNCHED' for 'READ'.  The PUNCH command is valid
   only before punch file transfer begins.

   'DELETE' <jobid> <CA>

   Identical in function to the CANCEL command in standard syntax.

   'INPUT' <jobid> <CA>

   Places the job identified by <jobid> in a queue within RJS of jobs
   owned by the users awaiting source file transfer.  When it becomes
   the first or only job in this queue, the retrieval of the source file
   is initiated.  If the INPUT command is successful, the message 'JOB
   <jobid> ACCEPTED FOR PROCESSING.' is displayed.  The following error
   messages are possible:  'JOB <jobid> NOT FOUND.', 'USER <user name>
   DOES NOT OWN JOB <jobid>.', 'JOB <jobid> HAS ALREADY COMPLETED.', '
   SOURCE PATHNAME HAS NOT BEEN SPECIFIED.' and 'PRINT PATHNAME HAS NOT
   BEEN SPECIFIED.'

   'JOBSTAT' <jobid> <CA>

   Identical in function and response to the 'STATUS' <jobid> command in
   standard syntax.

   'JOBLIST' <CA>