RFC 589

RFC 589: CCN NETRJS Server Messages to Remote User 🎀

RFC589 is titled CCN NETRJS Server Messages to Remote User 💖 Robert T. Braden of UCLA/CCN wrote it, and it's dated November 26, 1973. It was received at the NIC on 14-DEC-73 as NIC #20268. The document doesn't state a category or status, and it doesn't list anything it obsoletes or updates, so I'm not guessing at any of that 🙈

Okay bestie, this RFC is basically the menu of every message a remote user can get from the CCN NETRJS server 📨 It's all about connecting, signing on and off, what happens when the remote site or network messes up, and what happens when CCN itself has a meltdown. Let's go, it's giving very organized energy ✨

---

A. Initial Connection, Signon, and Signoff 🦋

1. If CCN refuses an ICP to a NETRJS socket, that means one of two things. Either there's no free core within the NCP region, or CCN's software is crashing 💀
2. Once the ICP is completed, CCN might send the user one of these messages and then close the Telnet connections:

NRJ110I NETRJS PORTS BUSY.  TRY LATER

This one may be expected every now and then. If it happens frequently, it should be reported to CCN User Relations (825-7548), or to BELL@CCN.

NRJ111I RJS NOT UP, TRY LATER

3. Normally though, the user gets a READY message 🌸

NRJ876R CCN NETRJS READY.  ENTER SIGNON

If the user sends no operator input for 3 minutes, CCN sends the following and closes the Telnet connection ⏰

NRJ308R SIGNON TIMEOUT EXCEEDED

NRJ205R NETRJS SESSION TERMINATED

If the user sends an invalid SIGNON command, they get this one 🙅‍♀️

NRJ307R INVALID SIGNON, RE-ENTER

Finally, a valid signon gets acknowledged by RJS with this message 🎉

RJS750I TERMINAL -termid- HAS SIGNED ONTO RJS

4. If the user ends the session by entering a SIGNOFF command, NETRJS waits until all data transfer has completed. Then it sends the following and closes the Telnet connection 👋

NRJ205R NETRJS SESSION TERMINATED

---

B. Remote Site or Network Failures 🫶

1. During data transfer, the user must be reasonably responsive. If they aren't, CCN closes the data transfer connection and sends the remote operator this message 😤

NRJ504I DATA TRANSFER TIMEOUT FOR THE -device-, -termid-

a) If -device- is PRINTER or PUNCH, the user site stopped accepting bits (sending "allocates") for over 5 minutes.

b) If -device- is READER, the user site left the 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. That's presumably due to user site software or a Network transmission error 🤷‍♀️ The messages beginning with the word "BAD" follow an NRJ512I message that contains the faulty header in hex. They are:

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.

NRJ507I BAD HEADER TYPE FOR NETRJS READER

Type code in header is not X'FF' (data) or X'FE' (end-of-data).

NRJ511I BAD FILL BIT COUNT FOR NETRJS READER

The filler bit count in header is not a multiple of 8.

3. If the header is correct but a data record is faulty, the remote user gets this message 🥲

NRJ602I line STREAM ERROR - READER, -code-

A protocol error was detected in the READER stream. CCN closes the stream and readies it to be reopened, so the remote user can retry the data transfer operation. The valid -code- values are:

CODE            ERROR

  1             Device id byte has high bit off.

  2             End of transaction in the middle of a data line.

  3             Truncated input line longer than 255 bytes.

  4             In compressed text, string control byte has high
                bit off.

  5             In compressed text, duplicate blank string extends
                line longer than 255 bytes.

  6             In compressed text, duplicate character string
                extends line longer than 255 bytes.

  7             In compressed text, character string extends line
                longer than 255 bytes.

4. Finally, if the user aborts their own data transfer, they get this message 🛑

NRJ502I NETRJS -device- DATA TRANSFER ABORTED BY USER
-termid-.

---

C. CCN Failures 💅

1. The CCN operator can cancel a NETRJS session. That aborts any open data transfer streams and sends this message 😬

NRJ204I NETRJS SESSION ABORTED BY CENTRAL OPERATOR, TERM=
-termid-

2. Any of the following messages point to a serious CCN Network software problem, and they cause the session to be aborted 🚨

NRJ106A NETRJS DEAD - EXCHANGE INOPERATIVE

NRJ201A NETRJS DT SOCKET ERROR - BAD LISTEN

NRJ208A NETRJS PROGRAM CHECK IN -device-, code=ccc

NRJ209A NETRJS LOAD FAILED FOR -device-, code=xx

NRJ304I RJS LINE HANDLER DEAD

NRJ401I RJS LINE HANDLER DEAD

NRJ402I RJS LINE HANDLER DEAD

Any of these should be reported to CCN.

3. Besides global catastrophes like the ones above, the user might run into a failure of one particular data transfer process. These don't end the session. They only cause the data connection to be refused or terminated, and the user can try to open the data connection again. Repeated failures should be reported to CCN 🔁

NRJ501I NO CORE FOR DATA TRANSFER BUFFER -device-

NRJ503I NO CORE FOR DATA TRANSFER WORKAREA -device-

NRJ207I NO CORE FOR-device-DATA TRANSFER MODULE

Because of core memory limitations in CCN's NCP, -device- can't be started right now. The data transfer connection indicated by -device- will be refused. This may happen now and then during busy periods, but repeated occurrences should be reported to CCN.

NRJ509I -device- DATA TRANSFER DEAD

NRJ510I -device- DATA TRANSFER DEAD

NRJ602I line STREAM ERROR - PRINTER, -code-

NRJ602I line STREAM ERROR - PUNCH, -code-

CCN's data transfer failed here, but recovery may be possible. The user can try again ✨

---

[ This RFC was put into machine readable form for entry ]
[ into the online RFC archives by Tony Hansen 10/98     ]