RFC 589 (rfc589) - Page 2 of 5
CCN NETRJS server messages to remote user
Alternative Format: Original Text Document
NIC #20268
P.2
7 Finally, a valid signon will be acknowledged by RJS with the
message:
RJS750I TERMINAL -termid- HAS SIGNED ONTO RJS
4. If the user terminates the session by entering a SIGNOFF com-
mand, NETRJS will wait until all data transfer has completed
before sending the message:
NRJ205R NETRJS SESSION TERMINATED
and closing the Telnet connection.
B. _R_E_M_O_T_E _S_I_T_E _O_R _N_E_T_W_O_R_K _F_A_I_L_U_R_E_S
1. During data transfer, the user must be reasonably responsive.
If not, CCN will close the data transfer connection and send
the remote operator message:
NRJ504I DATA TRANSFER TIMEOUT FOR THE -device-, -termid-
a) if -device- is PRINTER or PUNCH, user site
stopped accepting bits (sending "allocates")
for over 5 minutes.
b) if -device- is READER, user site left reader
connection open without sending any bits for 5
minutes.
2. During data transfer on the CR connection, CCN may detect an
incorrect header or record, presumably due to user site
software or Network transmission error. The following mes-
sages beginning with the word "BAD" will follow an NRJ512I
message containing the faulty header in hex:
NRJ505I BAD HEADER SEQUENCE FOR NETRJS READER
Sequence number in transaction header does not match
internal counter of records passed.
NRJ506I BAD HEADER LENGTH FOR NETRJS READER
Length given in header exceeds 880 bytes.