Organization: China Interactive Publishing Network (http://www.china-pub.com/)
RFC Document Chinese Translation Program (http://www.china-pub.com/compters/emook/aboutemook.htm)
E-mail: Ouyang@china-pub.com
Translator: Shao Yi (EPL shaoyi@163.net)
Translation time: 2001-11-7
Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but must
Keep the translation and copyright information of this document.
Network Working Group James E. White
Request for Comments: 105 Computer Research Lab.
Category: Information university of California
Santa Barbara, California
March 1971
Remote login and remote output returned network manual through UCSB
table of Contents
First, remote login (RJE) 2
1.1 RJE login 2
1.2 RJE join 2
1.2.1 Class A (Spending Mode) Input 3
1.2.2 Class B (unregulated record) input 3
1.2.3 Class C (fixed length record) input 4
Second, remote output return (RJOR) 4
2.1 Rjor login 4
2.2 Input Joint 5
2.3 Output join 6
In the following discussion, 'byte' means 8 bits and numbered from left to right.
First, remote login (RJE)
The UCSB will receive a batch pseudo card file at the socket number X'200 'located in the address three. Network user should
This is a account at the center of the UCSB. Account # _1025, programmer name 'ucla', 'sri', 'UTAH', etc.
It can be used when checking. 360/75 runs in OS MVT and HASP. The user submits tasks to HASP to develop progress
Table, and by the OS through a middle process called RJE. This intermediate process is addressed by a socket number X'200 '.
And can be excited through the logging. The intent of this section is to provide the programmer to provide the necessary information for the communication with the RJE; and assume that it is familiar
Understand the mass service provided by the computer center, as well as the service control language requirements.
RJE delivers all network control programs based on the host-host transport protocol on August 3, 1970.
Packet. It looks forward to the first received message packets for type 0, discard the top eight (message type) and assume that they are
Zero, and the boundary of the IMP message packet is not considered within the subsequent connection period.
1.1 RJE login
In order to submit one or more tasks to batch processing, the network user must establish a single connection with RJE. RJE
Refers only when a single junction is established (ie when a user sends a document). In other days,
It saves direct access memory and must be triggered by the log logger. One login sequence can always pass to the socket
The X'200 'transmits the join request message to initialize. RJE serves multiple users from different time. If RJE is being used
Send a connection application to the socket, the network control program queues the information. When the current file transfer is completed,
RJE will monitor and accept the next request message in its information queue (if present); if there is no information queue
With its request message, it will terminate execution and release it occupied the main memory. When RJE is not in the kernel, the log recorder listened to the socket X'200 ', and the first call it received, read the RJE into the kernel, and stop listening,
Continued by RJE listen on the socket. Therefore, to initialize a login sequence, the user sends the socket X'200 '
Squire. If the request is accepted, he is connected with RJE. If the request is rejected, he should re-issue
Send a connection request; once the request is accepted, he will be connected to RJE. Refused again means that the network control program
Source is warned. Once the join is established, RJE will consider that the user has logged in.
In order to prevent RJE from being monopolized by a single user, it is specified in the software: if a RJE is from the connection user party.
When the wait for transmission exceeds a certain period of time, the join is terminated. Now this time limit has been set to each record
Minute, but it can be shortened or extended as needed in the future. In addition to this termination, RJE will keep it infinitely
Joints between users. The card image will be accepted in the connection, and each card will be transferred to HASP as it is.
When the document is transmitted, the user is required to end the join. RJE will explain this action as a mark at the end of the file, and
And considered that the user has logged out.
1.2 RJE connection
RJE looks forward to the first byte of the connection from the connection established to which it is received, that is, the tag message type 0;
It discards this byte without checking, and then invalid numbers in the IMP message packet boundary. The second byte received
Translated to determine the marker in the data format thereafter.
Bytes translate as follows:
BITS 0-1 = 00: Subsequent documents are Class A input (for streaming input).
= 01: Undefined, should not appear.
= 10: Subsequent documents are class B input (variable length record).
= 11: Subsequent documents are Class C input (fixed length record).
BITS 2-7: For the test, it should be zero.
Once given, this statement is valid throughout the joint process.
The user sends its document as a card image, regardless of the specified input category. Each document will be
Add deletion to 80 bits by filling or truncated manner on the right. The sent documents must be written in strict accordance with the computer center
Format organization placed in the machine. Each task in the document must submit a task card and all its common work, respectively.
Industry Control Language (allowed to batch jobs, and transparent to RJE). To load special (non-residing) for any requirements
The task of disk and tape must be inserted into a special job control language card after this task card, format:
/ * Setup Vol-Ser, Vol-Ser, ...
1 2
Here "Vol-Ser" is the volume sequence number of the request to load the volume. "/ * Setup" begins in the first column, "Vol-Ser"
It must be started in page 16. This task will enter the system with a HASP to enter the system until the request volume can be added by the operating mechanism.
Load. If the user forgets to declare all such request volumes, his task will be canceled immediately. Not included in the document
All cards of the input data must be composed of a valid expanded binary-decimal exchange code.
1.2.1 Class A (Spending Mode)
If the RJE input is declared as a class, the RJE is interpreted as an empty through the third byte of the data received.
The character statement statement. Each of the received bytes is compared to that character. Any different characters are
A next byte of the current card image. Whenever the space is encountered, the previous byte is the current card image.
The last byte, then fill or intercept characters as specified, and pass it to HASP. There may be zero or more or non-spacers between two spaces. Therefore, when the input is described as a class, the data transmitted to the RJE should have the following format:
1 1 1 Variable 1
----- ------- ----- / ---- // -------- ------ - /
| | | | BREAK | / | | BREAK | /
| X'00 '| x'00' | char. | / | card image | char. | / ...
----- ------- ----- / ---- // -------- ------ - /
The length of each of the fields is already described in bytes. Zero or specific numbers in parentheses [angle brackets]
Send it before the connection is closed by the user.
1.2.2 Class B (unregulated record) input
If the input of RJE is declared as a Class B, all inputs after the initial two bytes should contain a phase
Neighbor variable length recording string. Each record is made from a single-byte OP code (the OP code should be X'01 '), and one for explanation
Subsequently, the two-word thrust number of the unsigned lengths in the digital field variable length is composed.
The length of the text field should be zero or the positive code length field must contain an integer, this integer should be 8 times.
number. The text represents a card image, fill or intercept characters according to the regulations, and passed it to HASP. therefore
When the input is illustrated as a class B, the data transmitted to the RJE should have the following format:
1 1 1 2 l bits
----- ------- / ------- ----- --- // ----- /
| | | | / | | | Text | /
| X'00 '| X'80' | / | X'01 '| L | Card Image | / ...
----- ------- / ------- ----- --- // ----- /
Here, the length of each field has been described in bytes in addition to another description. Brand [angry bracket]
Zero or specific numbers can be sent before they are closable by the user.
1.2.3 Class C (fixed length record) input
If the RJE's input is declared as a C class, all inputs after the initial two bytes should be determined by an adjacent
Long, 80 bytes card mapping string consists. Therefore, when the input is illustrated as a C class, the data transmitted to the RJE should be
There is a format:
1 1 80
----- ------- / -------------------- /
| | | | / | | /
| X'00 '| X'c0' | / | Card Image | / ...
----- ------- / -------------------- /
The length of each of the fields is already described in bytes. Zero or specific numbers in parentheses [angle brackets] can be sent before they are closable by the user.
Second, the remote output return (RJOR)
As long as the task is submitted, the eighth bit of the counting parameters on the task card is the character 't', and then the RJE is submitted.
The Class A Sysout output of the task in the UCSB is always acquired by contacting the socket X'300 '.
The output is retrieved according to the request, and the subsequent process to the network called RJOR's process to the network
User broadcast. Rjor can trigger through the log recorder. This section is designed to provide programmers with the necessary letter of communication with RJOR
interest.
Rjor Based on the host-host transport protocol on August 3, 1970, passed all networks through the network control program.
Packet. Rjor is looking forward to the first received message message is type 0, discard the first bit and assume it zero, and it is
The boundary of the Imp message packet is not considered within the subsequent connection period. Similarly, the first message packet type sent by RJOR is
0: The first byte consists of zero, and thereafter, the IMP message packet boundary is not important during the coupling cycle.
2.1 RJOR login
In order to obtain a calculated output from the batch mode task, the network user must establish a joint connection with the RJOR.
Rjor is only in the core memory resident area (ie, when a user is receiving or transmitting control information or one
Documentation When or when the RJOR waits the previously requested output document (or some documentation)). In other days,
It saves direct access memory and must be triggered by the log logger. One login sequence can always pass to the socket
The X'300 'transmits the join request packet to initialize. If another user is looking forward to send a connection when another user is logging in
Application, the network control program queues the information. After the current connection termination, RJOR will listen and accept its information.
The next request message in the queue (if any); if there is no request message in the information queue, and it already
When all its output file request packets are completed, it will terminate the execution and release the main memory it occupied. Rjor
When not in the kernel, the log recorder monitors from the socket X'300 ', and eliminates the first call it receives, will RJOR
After reading the kernel, stop listening, continues to listen by Rjor on the socket. So to initialize a login sequence,
The user sends a join request to the socket X'300 '. If the request is accepted, he has established contact with RJOR. in case
The request is rejected, but he should resend the sending request; once the request is accepted, he will be connected to RJOR. once again
Refuse means that the resources of the network control program are warned. Once the first half of the requested duplex connection is established, Rjor is
It is considered that the user is already logged in.
In the first join (hereinafter referred to as input coupling), the user sends a flag to specify the function executed by the RJOR, at the same time
The task name to which functions to be applied is also specified. Rjor then closes this join. Rjor sends control information, please
The configuration of the message and the auxiliary connection of the RJOR socket in the point three, the number are the RJOR socket, and said
Bright. At the same time, the user-switched word number is also the socket number of the RJOR socket number connected to the user.
Description. The user's request message is not necessarily executed immediately. If it is the former case, RJOR is connected to the specified user
The collation is issued a joint request, and if necessary, can be used as the user output
Send any appropriate control information. The RJOR then closes the connection and considers that the user has logged out. If the user
The request message cannot be satisfied immediately (for example, the task output of the task is not submitted or has not yet ended), then the second sufficiently long coupled is created by RJOR, and the delay information is notified to the user, and then shut down. Then when the request message can be
When used, the join is reopened and transmits the required data and then close the join. The user is considered to be logged out.
In order to prevent RJOR from being monopolized by a single user, it is specified in the software: if the connection user requests to close, or
When a RJOR waits for a certain amount of time limit that is completed, the connection is terminated. Now, this time is extremely
The restriction has been set to each record a minute, but it can be shortened or extended in the future.
2.2 Input join
Rjor looks forward to it from the first byte of the data from the input coupled to 0, ie the tag message type 0; it will
This byte is discarded without checking, and then invalid numbers in the IMP message packet border. The second word of receiving data
The section is interpreted as an identification of the function to be executed. Follow this marker byte, Rjor expects an eight-byte expanded binary
- Decimal exchange code task name and fill a blank character in the right when necessary. The marker byte is translated as follows:
Bit 0 = 1: Send the output generated by the specified task.
Bit 1 = 1: Clear the output document created by the specified task.
Bit 2 = 1: Delay as needed to execute functions indicated on 0-1 bits.
= 0: If the function indicated by 0-1 bits cannot be executed immediately, return a simple message, add this
Take the description.
Bit 3 = 1: A request with a waiting output (bit 2) option that belongs to the specified task will be canceled.
BITS 4-7: For test, it should be zero.
Any combination of 0-2 bits is allowed. If the third bit is 1, the other digits are not processed. If the zero
The bit is equal to 1 and the first bit is equal to one, then the output document is sent, and then clear it. If the two identified tasks
Sunding, the output from the second task will overwrite the output from the first task. under these circumstances,
The user should clear the output from the task after the first task is sent so that the request from the second task is not
Will only return another copy of the first task output.
2.3 Output join
Rjor can turn on the output connection one or twice as the result of a single transmission in the output join. In these two love
In any of the case, the first byte of the transmission will be composed of zero to indicate the message type 0.
And thereafter, the IMP message packet boundary is not important during the coupling cycle. Follow the first byte, RJOR will
Those applicable responses send task names. The task name will exist with one by the consistent with the user.
The 8-byte number of numbers. Follow this task name, RJOR will send a logical record of variable length. <* Each piece should be
A single-byte operation code, a double-byte length field group that describes the unsigned length bit of the subsequent variable length text segment
to make. The length of the original field should be zero or positive bytes; this length field should contain an integer of an 8 multiplier.
The currently defined opcode is shown in Figure 1. One opcode located in X'01 'indicates that the text is included in
Requests the record of the Sysout dataset created by the output task. All words with logical records with opcode X'01 '
The length of the segment is the same. For data sets different from this value, the record length is different from the right side of its standard record.
Fill empty characters or intercept to meet the requirements. Usually the calculation output of the first column for specifying the printer has been
Drop without any appearance. Record is transferred to the user according to their printing on the printer. Totally, these
The record includes all information that may appear in the printout, except for the HASP separator.
In addition to all logical records other than operating code X'01 ', the length field contains zero, and the operation code communicates all the information of the logic record. *
Operation code (hexadecimal number) name
----------------------------------------------- ------------
00 Document At the end of the document All output from this task has been sent (lasting one
The code is a logical record of x'01 ').
01 The output text field contains a SYSOUT data generated by this task
recording.
02 Output document has been cleared. The output from this task has been cleared in accordance with the request.
The 03 buffer kernel space is insufficient. The main storage space for transmitting the task is insufficient. pass
Send tasks is canceled and any clear request is prohibited.
04 file I / O error. I have encountered an unrecoverable I / O error when reading the output document.
error. The transfer task is canceled and any clear request is disabled.
05 Clear the file I / O error. An unrecoverable I / O occurs when the output document is cleared
error. The transfer task is canceled and any clear request is disabled.
06 The request queue is full. The output from the task does not exist, and has specified waiting output to select
Item, but RJOR's request queue space has been full and has been disabled.
07 Waiting to output. The output from the task does not exist, and has specified waiting output to select
Item, Rjor is waiting for task output.
08 No discovered request user request cancels the specified output option before sending
Request a command. But Rjor did not find such a request.
09 request is canceled. According to the user's request, the previously sent specified waiting output selection
The request command of the item is canceled.
0A Search Document I / O Errors. An unsteady occurs when you try to position the output document of the task
A complex I / O error. User request is canceled.
0B did not find the output. No output from this task is found. User does not specify waiting
Options.
Figure 1. Output connection operand
[This RFC document is from Randy Dunlap in April 97]
[Compiled RFC online file as machine readable form]
* This limit is only temporary, we are doing patch work. This patch will be released soon.
RFC105 - NetWork Specifications for Remote Job Entry Andremote Job Output Retrieval At UCSB
Remote login and remote output returned network manual through UCSB
1
RFC Document Chinese Translation Program
