📄 rfc189.txt
字号:
Braden [Page 13] RFC 189 Interim NETRJS Specifications July 1971 APPENDIX C Carriage Control The carriage control characters sent in a printer channel by NETRJS conform to IBM's extended USASI code, defined by the following table: CODE ACTION BEFORE WRITING RECORD blank Space one line before printing 0 Space two lines before printing - Space three lines before printing + Suppress space before printing 1 Skip to channel 1 2 Skip to channel 2 3 Skip to channel 3 4 Skip to channel 4 5 Skip to channel 5 6 Skip to channel 6 7 Skip to channel 7 8 Skip to channel 8 9 Skip to channel 9 A Skip to channel 10 B Skip to channel 11 C Skip to channel 12Braden [Page 14] RFC 189 Interim NETRJS Specifications July 1971 APPENDIX D Network/RJS Command SummaryTerminal Control and Information Command SIGNON First command of a session; identifies VRBT by giving its terminal id. SIGNOFF Last command of a session; RJS waits for any data transfer in progress to complete and then closes all connections. STATUS Outputs on the remote operator console a complete list, or a summary, of all jobs in the system for this VRBT, with an indication of their processing status in the Model 91. ALERT Outputs on the operator console the special "Alert" message, if any, from CCN computer operator. The Alert message is also automatically sent when the user does a SIGNON, or whenever the message changes. MSG Sends a message to CCN computer operator or to any other RJS terminal (real or virtual). A message from the computer operator or another RJS terminal will automatically appear on the remote operator console.Job Control and Routing Commands Under CCN's job management system, the default destination for output is the input source. Thus, a job submitted under a given VRBT will be returned to that VRBT (i.e., the same terminal id), unless the user's JCL overrides the default destination. RJS places print and punch output described for a particular remote terminal into either an Active Queue or a Deferred Queue. When the user opens his print or punch output channel, RJS immediately starts sending job output from the Active Queue, and continues this queue is empty. Job output in the Deferred Queue, on the other hand, must be called for by job name, (via a RESET command from the remote opera- tor) before RJS will send it. The Active/Deferred choice for output from a job is determined by the deferral status of the VRBT when the job is entered; the deferral status, which is set to the Active option when the user signs on, may be changed by the SET command.Braden [Page 15] RFC 189 Interim NETRJS Specifications July 1971 SET Allows the remote user to change certain properties of his VRBT for the duration of the current session; (a) May change the default output destination to be another (real or virtual) RJS terminal or the central facility. (b) May change the deferral status of the VRBT. DEFER Moves the print and punch output for a specified job or set of jobs from the Active Queue to the Deferred queue. If the job's output is in the process of being transmitted over a channel, RJS aborts the channel and saves the current output location before moving the job to the Deferred Queue. A subsequent RESET command will return it to the Active Queue with an implied Backspace (BSP). RESET Moves specified job(s) from Deferred to Active Queue so they may be sent to user. A specific list of job names or all jobs can be moved with one RESET command. ROUTE Re-routes output of specified jobs (or all jobs) waiting in the Active and Deferred Queues for this VRBT. The new destination may be any other RJS terminal or the central facility. ABORT Cancels a job which was successfully submitted and awaiting execution or is current executing in the Model 91. If he cancelled job was in execution, all output it produced ill be returned.Output Stream Control Commands BSP (BACKSPACE) "Backspaces" output stream within current sysout data set. Actual amount backspaced depends upon sysout blocking but is typically equivalent to a page on the line printer. CAN (CANCEL) (a) On an output channel, CAN causes the rest of the output in the sysout data set currently being transmitted to be omitted. Alternatively, may omit the rest of the sysout data sets for the job currently being transmitted; however, the remain- ing system and accounting messages will be sent.Braden [Page 16] RFC 189 Interim NETRJS Specifications July 1971 (b) On an input channel, CAN causes RJS to ignore the job currently being read. However, the channel is not aborted as a result, and RJS will continue reading in jobs on the channel. (c) CAN can delete all sysout data sets for specified job(s) waiting in Active or Deferred Queue. RST (RESTART) (a) Restarts a specified output stream at the begin- ning of the current sysout data set or, option- ally, at the beginning of the job. (b) Marks as restarted specified job(s) whose transmission was earlier interrupted by system failure or user action (e.g., DEFER command or aborting the channel). When RJS transmits these jobs again it will start at the beginning of the partially transmitted sysout data set or, option- ally, at the beginning of the job. This function may be applied to jobs in either the Active or the Deferred Queue; however, if the job was in the Deferred Queue then RST also moves it to the Active Queue. If the job was never transmitted, RST has no effect other than this queue movement. REPEAT Sends additional copies of the output of specified jobs. EAM Echoes the card reader stream back in the printer or punch stream, or both.Braden [Page 17] RFC 189 Interim NETRJS Specifications July 1971 +---------------------------------+ | RJS | +---------------------------------+ ^ | ^ | | | v | v v +------------------------------+ CCN -- Server | | | NETRJS | +------------------------------+ ^ | ^ | | | v | v v +----------+ +---------------+ | TELNET | | Data Xfer | (server) | Server | | 3rd Level | +----------+ +---------------+ ^ | ^ | |---------------------|-----|----------|-----|-----|----------------- O | O | | | | p | p | C| C| C| e I | e O| I h| O h| P h| ARPA r n | r u| n a| u a| u a| a p | a t| p n| t n| n n| Network t u | t p| u n| p n| c n| o t | o u| t e| u e| h e| r | r t| l| t l| l|---------------------|-----|----------|-----|-----|----------------- | | | | | | V | V V +----------+ +---------------+ | TELNET | | Data Xfer | (user) | Server | | 3rd Level | +----------+ +---------------+ Remote ^ ^ | | / "Virtual | | | User / Remote Batch | V V / Terminal" +------------------+ / | | V | NETRJS | +---------+ | User | / |<------------->| Process | / Console | | | +____________| +------------------+ ^ | | | V V (file) (file) (file) FIGURE 1. SCHEMATIC OF NETRJS OPERATIONBraden [Page 18] RFC 189 Interim NETRJS Specifications July 1971 +------+ +------+ +-----------+ +---------------------+TRANSACTION <--> | X'FF'| |Filler| |Sequence | | Data Length | | | | Count| | Number | | in bits | +------+ +------+ +-----------+ +---------------------+ +------+ | X'00'| { RECORD } * | | +------+ <---- n text bytes ------> +--+-----+ +--------+ +--------+ +--------+TRUNCATED <--> |11|Devid| | n (8) | | Text | . . . | Text |RECORD | | (6) | | | | (8) | | (8) | +--+-----+ +--------+ +--------+ +--------+ / \ | +---+----+ | * | |110| n | (n blanks) | | | |(5) | | | +---+----+ | | | +--+-----+ / +---+----+ +--------+ |COMPRESSED<--> |10|Devid|< |111| n | |Char- | (n replications |RECORD | | (6) | \ | |(5) | | acter | of "Character") | +--+-----+ | +---+----+ +--------+ | | | | +--+-----+ +--------+ +--------+ | | |10| n | | Text | . . .| Text | | | | | (6) | | (8) | | (8) | | | +--+-----+ +--------+ +--------+ | \ / +------+ | X'00'| | | +------+ FIGURE 2. DATA TRANSFER PROTOCOL IN NETRJS [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Tony Hansen 11/98 ]Braden [Page 19] ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -