Jump to content

RSTS/E

From Alfawiki
RSTS
Company typeOperating system
IndustryComputer software
PredecessorTSS-8
Founded1970
FounderDigital Equipment Corporation engineers
FateDiscontinued; rights divested to Mentec in 1994
SuccessorNone
Headquarters
Maynard, Massachusetts
,
United States
ProductsRSTS-11, RSTS/E
OwnerDigital Equipment Corporation (now Hewlett-Packard)

RSTS () is a multi-user time-sharing operating system created by Digital Equipment Corporation (DEC, now under Hewlett-Packard) for the PDP-11 family of 16-bit minicomputers. The initial release, known as RSTS-11 (Version 1), was developed in 1970 by DEC engineers who had previously worked on the TSS-8 time-sharing system for the PDP-8. The last version, RSTS/E Version 10.1, was launched in September 1992. Both RSTS-11 and RSTS/E are frequently referred to simply as "RSTS."

RSTS-11 featured support for the BASIC programming language, specifically an advanced variant named BASIC-PLUS, which was created under contract by Evans Griffiths & Hart based in Boston. Beginning with RSTS/E version 5B, DEC broadened language compatibility by emulating runtime environments from the RT-11 and RSX-11 operating systems.

Acronyms and abbreviations

  • BTSS (Basic Time Sharing System – not commercially released) – the original designation for RSTS.
  • CCL (Concise Command Language) – command used to execute programs through the Command Line Interpreter.
  • CIL (Core Image Library) – file format containing bootable programs and OS versions up to 6A.
  • CILUS (Core Image Library Update and Save) – DOS-11 utility designed to handle CIL files.
  • CLI (Command Line Interpreter) – shell interface for user interaction.
  • CUSPs (Commonly Used System Programs) – system utilities comparable to Windows Task Manager; developed in BASIC-PLUS on RSTS-11.
  • DCL (Digital Command Language) – command interpreter scripting language.
  • DTR (DATATRIEVE) – a programming language.
  • FIP (File Information Processing) – resident handler for file requests.
  • FIRQB (File Information Request Queue Block) – data structure managing file request operations.
  • KBM (Keyboard Monitor) – functionally equivalent to CLI.
  • LAT (Local Area Transport) – Digital’s proprietary networking protocol predating TCP/IP.
  • MFD (Master File Directory) – the root directory within the file system hierarchy.
  • PBS (Print Batch Services)
  • PIP (Peripheral Interchange Program)
  • PPN (Project Programmer Number) – comparable to Unix GID/UID identifiers.
  • RDC (Remote Diagnostics Console) – replacement for PDP-11 front panel utilizing serial or modem connections.
  • RSTS-11 (Resource Sharing Time Sharing System) – original commercial product name.
  • RSTS/E (Resource Sharing Timesharing System Extended) – modern iteration of RSTS.
  • RTS (Run Time System) – shared, reentrant OS interface code mapped into user program address spaces to optimize RAM usage.
  • RTSS (Resource Time Sharing System – not marketed) – an alternative early name for RSTS.
  • SATT (Storage Allocation Truth Table) – disk allocation bitmap indicating used and free clusters.
  • SIL (Save Image Library) – OS container format that replaced CIL after transitioning from DOS-11 to native RSTS/E systems.
  • SILUS (Save Image Library Update and Save) – utility employed to generate SIL files, superseding DOS-11’s CILUS tool.
  • UFD (User File Directory) – root directory of a user’s home area.
  • XRB (Transfer Request Block) – data structure used for system requests beyond the scope of FIRQB.

1970s

The core of RSTS was developed using MACRO-11 assembly language, assembled and placed on disk with the CILUS utility operating under the DOS-11 system. Upon startup, RSTS launched an enhanced version of BASIC called BASIC-PLUS. All system utilities known as CUSPS, including tools for resource tracking and system administration, were created in BASIC-PLUS. Between 1970 and 1973, RSTS ran within 56K bytes of magnetic core memory (64K including memory-mapped I/O), accommodating up to 16 terminals and 17 concurrent jobs, with individual programs capped at 16K bytes. By 1973, DEC reported approximately 150 licensed installations.

Memory management capabilities were introduced in 1973 for the PDP-11/40 and PDP-11/45 models, enabling 18-bit addressing (up to 256K bytes) and isolating user processes from the kernel environment. The PDP-11/20 was supported exclusively under RSTS-11.

In 1975, support extended to the PDP-11/70, which featured a 22-bit address space allowing up to two megabytes of memory and handling as many as 63 jobs simultaneously. The concepts of RTS and CCL were introduced, requiring compilation during SYSGEN. Multi-terminal support was enhanced so that a single job could manage multiple terminals—up to 128. Additionally, sophisticated interprocess communication mechanisms were implemented. By August of that year, licensed systems had grown to approximately 1,200.

By 1977, installation no longer depended on DOS-11; the kernel could be compiled within RT-11's RTS, formatted using RT-11's SILUS, and copied during time-sharing sessions. The BASIC-PLUS RTS along with other user-mode processes operated independently from the kernel. System administrators gained the ability to choose the default Keyboard Monitor (KBM) at bootstrap. Licensed installations had increased to roughly 3,100.

In 1978, final enhancements to memory management enabled RSTS to utilize up to four megabytes of PDP-11 memory through full 22-bit addressing. Support for SUPERVISORY mode made RSTS the first DEC operating system with this feature. Furthermore, DECnet support was added along with remote diagnostics capabilities via the RDC facility in Colorado Springs. By the end of the decade, licensed systems surpassed 5,000.

1980s

In 1981, machines equipped with Unibus such as the PDP-11/44, PDP-11/45, PDP-11/55, and PDP-11/70 gained support for separate instruction and data spaces. This allowed individual programs to address up to 64 KB for code and an additional 64 KB for data buffers. The DCL RTS was introduced alongside compatibility with DECnet III.

By 1983, approximately 15,000 DEC systems were running RSTS/E. Version V8.0-06 incorporated support for the MicroPDP-11—the smallest model featuring an 18-bit architecture. Installation was simplified by offering a pre-built kernel and CUSPS, marketed as MicroRSTS at a reduced cost; however, generating a full kernel required purchasing the complete version. The file system was upgraded to RSTS Directory Structure 1 (RDS1), which supported more than 1,700 user accounts—a substantial increase over its predecessor RDS0. Licensed users numbered over 10,000 with at least an equal number unlicensed.

Between 1985 and 1989, Version 9 iterations refined RSTS further. The DCL RTS became dominant while the file system evolved into RDS1.2 featuring improved user account management. Password security advanced by adopting a modified DES encryption method instead of the previous six-character Radix-50 scheme. Earlier releases maintained a single non-user system account in project zero ([0,1]) with all project one accounts having privileged status akin to a root account in Unix. Version 9 introduced multiple project zero accounts with individually assignable privileges. Networking expanded through support for the LAT protocol and compatibility with DECnet IV, enabling seamless terminal communication via DECserver, comparable to VAX systems running VMS. The shared DCL command interface across DEC operating systems improved user familiarity:

This is not just another pseudo command file processor; it is based on VMS features. The DCL command file processor is fully supported and integrated in RSTS through extensive changes to DCL and the monitor. DCL executes command files as part of your job; therefore, no pseudo keyboard or forcing of commands to your keyboard is necessary (as with ATPK).

1990s

In 1994, most of the PDP-11 software segment was divested by DEC to Mentec. Digital maintained limited support for PDP-11 users shortly thereafter, collaborating with Mentec.

By 1997, Digital and Mentec provided free licenses for RSTS version 9.6 and earlier releases strictly for non-commercial, hobbyist use on the SIMH PDP-11 emulator. This licensing arrangement also extends to several other Digital operating systems and is included within an authorized software package accessible via the official SIMH website.

Documentation

RSTS distribution packages consisted of at least eleven substantial three-ring binders (often referred to as "The orange wall"), complemented by a smaller binder containing the RSTS/E Quick Reference Guide, along with a paperback titled Introduction to BASIC AA-0155B-TK. The contents of these binders are organized as follows:

Volume 1: General Information and Installation

  • Documentation Directory
  • Release Notes
  • Maintenance Notebook
  • System Installation and Update Guide

Volume 2: System Management

  • System Manager's Guide

Volume 3: System Usage

  • System User's Guide
  • Guide to Writing Command Procedures

Volume 4: Utilities

  • Utilities Reference Manual
  • Introduction to the EDT Editor
  • SORT/MERGE User's Guide
  • RUNOFF User's Guide

Volume 4A: Utilities

  • EDT Editor Manual

Volume 4B: Utilities

  • Task Builder Reference Manual
  • Programmer's Utilities Manual
  • RT11 Utilities Manual
  • TECO User's Guide

Volume 5: BASIC-PLUS

  • BASIC-PLUS Language Manual

Volume 6: System Programming

  • Programming Manual

Volume 7: MACRO Programming

  • System Directives Manual
  • ODT Reference Manual

Volume 7A: MACRO Programming

  • MACRO-11 Language Manual
  • RMS-11 MACRO Programmer's Guide

Volume 8: RMS [Record Management Services]

  • RMS-11: An Introduction
  • RMS11 User's Guide
  • RMS-11 Utilities

Communication

RSTS interacts with users primarily through serial communication channels, supporting local terminals via a 20 mA current loop, RS-232 connections (either local serial ports or modems), or Ethernet using DECnet or LAT protocols. The system could accommodate up to 128 terminals concurrently (multi-terminal operation) and handle as many as 63 simultaneous jobs, contingent upon hardware factors such as CPU, memory capacity, disk availability, and workload—though typical configurations featured fewer terminals. Users had the option to submit batch jobs or execute commands semi-interactively through the "ATPK" batch utility on pseudo-terminals, functioning similarly to batch command execution in MS-DOS.

Login [Project, Programmer]

Access to the system is initiated by entering the LOGIN command (or alternatively HELLO) at a terminal that is not currently logged in. Any input provided at a logged-out terminal triggers the LOGIN program to interpret the command. If the input corresponds to an allowed command for unauthenticated users, the relevant program is CHAINed; otherwise, the system displays "Please say HELLO." Prior to Version 9, users could perform a single-line login sequence, although this method revealed passwords on screen: 

Bye

HELLO 1,1;SECRET

Ready

or 

I 1,1;SECRET

Ready

or 

LOGIN 1,1;SECRET

Ready

Terminal states are identified by prompts: "Ready" signifies a logged-in user interacting with BASIC-PLUS KBM (keyboard monitor), whereas "Bye" indicates a logged-out terminal.

Logging in requires specifying a PPN (project-programmer number) alongside a password. User identifiers are composed of two numbers—a project number (analogous to a Unix group ID) and a programmer number—each ranging from 0 to 254. Accounts follow the format [project,programmer], such as [10,5], [2,146], or [200,220]. System processes operating while logged out use the special account [0,0], displayed as **,** within SYSTAT CUSP, but this does not represent a valid user account. Employing a slash (/) instead of a comma in the login suppresses the system-wide message stored in [1,2]NOTICE.TXT (comparable to Unix’s message of the day) during login.

System and user accounts

Within each project, the programmer number 0 is generally allocated as a group account, identified by the symbol "#". For instance, a user such as [20,103] can access shared resources in [20,0] by using filenames that start with "#". This design facilitates scenarios like educational settings, where an instructor ([project,0]) can distribute materials to students ([project,x]).

There are two notable project numbers: project 0, which is designated for system software (in versions prior to Version 9, only one account existed: [0,1]), and project 1, reserved for privileged user accounts. Unlike Unix’s single root user, all accounts ranging from [1,0] through [1,254] possess elevated privileges. With the introduction of Version 9, system administrators gained the ability to assign more detailed privilege levels.

The account [0,1] serves as the repository for operating system components, runtime libraries, and boot files: 

DIR [0,1]
 Name .Ext    Size   Prot    Date       SY:[0,1]
BADB  .SYS       0P  <63> 06-Jun-98         Bad blocks list
SATT  .SYS       3CP <63> 06-Jun-98         Disk allocation bitmap
INIT  .SYS     419P  <40> 06-Jun-98         Boot loader
ERR   .ERR      16CP <40> 06-Jun-98         System error messages
RSTS  .SIL     307CP <60> 06-Jun-98         Operating system
BASIC .RTS      73CP <60> 06-Jun-98         BASIC-PLUS runtime
RT11  .RTS      20C  <60> 06-Jun-98         RT-11 runtime
SWAP  .SYS    1024CP <63> 06-Jun-98         Swap file
CRASH .SYS      35CP <63> 06-Jun-98         Crash dump
RSX   .RTS      16C  <60> 23-Sep-79         RSX-11 runtime
TECO  .RTS      39C  <60> 24-Sep-79         TECO editor

This directory contains a total of eleven files occupying 1952 blocks in SY:[0,1].

The DIR command invokes the DIRECT utility to display file listings. File sizes are measured in disk blocks of 512 bytes each. The letter "C" indicates contiguous allocation of disk space; "P" signifies protection against deletion unless explicitly removed. Protection codes (<40>, <60>, <63>) specify access permissions comparable to Unix’s read, write, and execute flags: code <60> marks private files; <63> denotes private files protected from deletion; and <40> identifies public files.

Library files are stored under account [1,1], accessible via the LB: device name. The system’s startup account is [1,2], which holds system CUSPS—command files invoked by prefixing their names with a dollar sign ($). Additional privileged accounts include [1,3] ("!"), [1,4] ("%"), and [1,5] ("&"). Notably, account [1,1] uniquely allows execution of the POKE system call for direct memory manipulation, making it functionally analogous to Unix’s root user.

Run-time environments

RSTS supported several run-time environments (RTS) designed for executing programs written in languages such as BASIC-PLUS, its compiled successor BASIC-Plus-2, COBOL (upgraded later to COBOL-85), FORTRAN IV (later updated to FORTRAN-77), along with DIBOL and MUMPS. These RTSs operated independently from one another, enabling users to switch between environments to run different applications and then return seamlessly to their original session. Most RTSs featured a command-line interface known as the KBM. Prior to Version 9, system administrators had to designate which RTS would be loaded at boot time—typically one supporting compiled program execution.

System managers were also able to implement special CCL (concise command language) commands—memory-resident shortcuts akin to Windows shortcuts or Unix symbolic links—that took precedence over KBM commands except for the DCL interpreter. CCLs could be loaded either during system startup or dynamically at runtime but did not exist as permanent files on disk.

Users had the capability to "SWITCH" between RTS environments, input BASIC-PLUS statements directly, execute programs, or run CCL commands with various options. Many RSTS installations included a "Control-T" status feature providing real-time information on the current program in execution, active RTS environment, memory usage statistics, and expansion possibilities.

BASIC-PLUS

Programs designed for BASIC-PLUS operated within the BASIC RTS environment, utilizing up to 32K bytes of memory from a total 64K. This interpreted language transformed keywords into a distinct bytecode known as PCODE, with variables and data stored separately in memory. Using the interactive SAVE command, the current memory state could be saved as a ".BAC" file on disk. Although not officially documented, two graduates from Southampton University created a decompiler that could reconstruct BAC files back into the original BASIC-Plus source code. The BASIC RTS occupied the remaining portion of memory.

For languages capable of producing genuine binary executables such as BASIC-Plus-2, FORTRAN-IV, or Macro Assembler, the available memory expanded to 56K bytes, reserving 8K for the RTS. The typical BASIC-PLUS prompt displayed was "Ready," and pressing Control-T revealed system status details including program name, RTS type, and memory consumption.

DCL (Digital Command Language)

Beginning with Version 9, DCL assumed the role of the primary startup RTS, despite its inability to run binary executables directly—a capability previously provided by the now-obsolete RSX RTS (detailed below). DCL was incorporated into all recent DEC operating systems—RSX-11, RT-11, VMS, and later OpenVMS versions—to ensure compatibility. The default prompt for DCL is the dollar sign "$" (example): <syntaxhighlight lang="console"> $ write 0 "Hello World, it is "+F$TIME() Hello World, it is 01-Jan-08 10:20 PM $ inquire p1 "Press Control-T for 1 line status:" Press Control-T for 1 line status: 1 KB0 DCL+DCL KB(0R) 4(8)K+24K 0.1(+0.1) -8 $ set verify/debug/watch $ show memory (show memory) (SYSTAT/C)

Memory allocation table: 

Start   End  Length  Permanent   Temporary
  0K -   85K (  86K) MONITOR
 86K - 1737K (1652K)   (User)

1738K - 1747K ( 10K) (User) DAPRES LIB 1748K - 1751K ( 4K) (User) RMSRES LIB 1752K - 2043K ( 292K) ** XBUF ** 2044K - *** END *** $ </syntaxhighlight>

RSX (Realtime System eXecutive)

Applications developed for the RSX RTS, including COBOL, Macro Assembler, and BASIC-Plus-2, had access to up to 56K of memory due to the RTS reserving the uppermost 8K. From RSTS Version 7 onwards, RSX RTS was integrated within the kernel itself, thereby freeing the entire 64K bytes for user-level programs.

Memory limitations were managed through the use of libraries, overlays, or chaining programs by sharing memory segments ("Core Common"). When RSX serves as the default KBM, its command prompt appears as the ">" character (example): <syntaxhighlight lang="doscon"> >run Please type HELLO >HELLO 1,1;SECRET >run ?What? >help Valid keyboard commands are:

ASSIGN DISMOUNT HELP RUN UNSAVE BYE EXIT MOUNT SHUTUP DEASSIGN HELLO REASSIGN SWITCH

>run CSPCOM CSP>HWORLD=HWORLD CSP>^Z >RUN TKB TKB>HWORLD=HWORLD,LB:CSPCOM.OLB/LB TKB>// >run HWORLD.TSK Hello World Press Control-T for 1 line status: ? 1 KB0 HWORLD+...RSX KB(0R) 7(32)K+0K 0.8(+0.2) +0

>DIR HWORLD.*/na/ex/si/pr SY:[1,2] HWORLD.BAS 1 <60> HWORLD.BAC 7C <124> HWORLD.OBJ 2 <60> HWORLD.TSK 25C <124>

Total of 35 blocks in 4 files in SY:[1,2]

> </syntaxhighlight>

RT-11

The RT-11 RTS simulated the Single Job variant of RT-11, residing in the upper 8K of memory while allocating the lower 56K for CUSPS, which were commonly FORTRAN-IV or Macro Assembler applications. When RT-11 is set as the default KBM, its command prompt appears as a "." character, demonstrated in the example below:

<syntaxhighlight lang="man"> .VERSION Please type HELLO

.HELLO 1,1;SECRET

.VERSION RT-11SJ V3-03; RSTS/E V8.0

.R PIP

  • HWORLD.MAC=KB:
       .MCALL .TTYIN,.PRINT,.EXIT

HWORLD: .ASCII /Hello World/<15><12> 

       .ASCIZ /Press Control-T for 1 line status:/
       .EVEN

Start: .PRINT #HWORLD 

       .TTYIN
       .EXIT
       .END    START

^Z

  • ^Z

.R MACRO HWORLD=HWORLD

  • ^Z

.R LINK

  • HWORLD=HWORLD
  • ^Z

.R HWORLD.SAV Hello World Press Control-T for 1 line status: 1 KB0 HWORLD+RT11 KB(0R) 2(28)K+4K 0.6(+0.2) +0

..DIR HWORLD.*/na/ex/si/pr SY:[1,2] HWORLD.BAS 1 <60> HWORLD.BAC 7C <124> HWORLD.TSK 25C <124> HWORLD.MAC 1 <60> HWORLD.OBJ 1 <60> HWORLD.SAV 2C <124>

Total of 37 blocks in 6 files in SY:[1,2]

. </syntaxhighlight>

TECO (Text Editor and COrrector)

The TECO editor operated as an RTS designed to optimize memory usage for the editing buffer and was initially introduced with RSTS V5B, preceding general runtime systems such as RSX and RT11. Unlike other RSTS RTSs, TECO did not include an integrated KBM; instead, users started TECO by executing a TECO program file (TECO.TEC). Both TECO and its related editor QEDIT served as direct forerunners to the UNIX text editor ED. Most RSTS installations utilized CCL commands to manage files—creating files with MAKE filespec, editing via TECO filespec, or running TECO scripts using MUNG filespec, data. Below is a sample illustrating TECO computing pi to twenty decimal places:

<syntaxhighlight lang="text"> Ready

run TECO

  • GZ0J\UNQN"E 20UN '

BUH BUV HK QN< J BUQ QN*10/3UI QI< \ +2*10+(QQ*QI)UA B L K QI*2-1UJ QA/QJUQ QA-(QQ*QJ)-2\ 10@I// -1%I > QQ/10UT QH+QT+48UW QW-58"E 48UW %V ' QV"N QV^T ' QWUV QQ-(QT*10)UH > QV^T @^A/ /HKEX$$ 31415926535897932384

Ready </syntaxhighlight>

System start-up (INIT.SYS)

When prompted with "Option:" during system initialization, entering an invalid command resulted in the message "Type 'HELP' for help." If the user then entered 'HELP' including the quotation marks, the system replied with "How amusing, anyway..." before displaying the standard help information.

PDP-11 console lights

System administrators had the ability to compile a kernel feature that produced a dynamic pattern on console lights resembling two snakes chasing each other. The default kernel animation showed one snake moving from right to left on data indicator lights; by adding a separate "lights" module, a second snake appeared moving left to right on address indicator lights. This functionality operated using supervisory mode prior to version 9.0. Similarly, RSX implemented a comparable display featuring two snakes engaged in a game of chicken on the console.

Teco easter egg

Using the command 'make' created a new text file and launched TECO. When users typed 'make love', it generated a file called 'love' and displayed the phrase 'Not War?'

Open Files List

During the 1990s, Kevin Herbert—who later joined DEC—introduced an undocumented feature that allowed users to press a key combination to view their currently open files along with details such as allocated blocks and file sizes.

Stardate

Beginning with release 9.0, an undocumented feature allowed system administrators to present the system date as a stardate, a concept inspired by the television show Star Trek. RSTS was pioneering in providing this stardate display option.

Add-ons by other companies

System Industries secured the exclusive license for RSTS to create SIMACS (SImultaneous Machine ACceSs), an enhancement for their disk controllers that enabled multiple PDP-11 RSTS systems to write simultaneously to shared disks. Dr. Albert Chu of System Industries designed SIMACS, which utilized a semaphore mechanism to manage exclusive write permissions among processors.

This innovation necessitated extensive modifications to RSTS’s disk input/output architecture. The originally single-threaded FIPS (File Information Processing System) was upgraded to support request timeouts and implement round-robin scheduling, addressing potential disk access stalls. Philip Hunt, also from System Industries and working in Milpitas, California, developed this enhancement before moving on to Digital Equipment in New England.

SIMACS functionality extended beyond the PDP-11 series, also accommodating VAXen platforms.

ROSS/V

In 1981, Evans Griffiths & Hart launched ROSS/V, which enabled all RSTS user mode processes—including CUSPS, RTSs, and user applications—to operate without modification under VMS on VAX-11 hardware. This emulator replicated kernel functions normally handled by the RSTS kernel on PDP-11 machines. Additionally, Evans Griffiths & Hart subcontracted the original BASIC-PLUS language for $10,500.

Other PDP-11 emulators

RSTS and its associated software are compatible with various PDP-11 emulators such as SIMH and Ersatz-11. For further information, refer to PDP-11.

Versions

Initially called BTSS (Basic Time Sharing System), the product was renamed RTSS prior to release due to a naming conflict with a Honeywell product. A typographical mistake subsequently altered RTSS to RSTS.[1]

Version Release date Notes
1 Not released
2A-19 1971 Deployed at Carleton College and Seattle Pacific College.
2B June 1971 Installed at Delaware School Auxiliary Association.[2]
2C October 1971 Improved software support including record I/O
3A-19 January 1972
3B May 1972
3C June 1972 Introduced UPDATE mode functionality
4A-12 October 1972 Added support for new hardware
4B July 1975 Patch release of V4A without additional features

With enhanced memory management for PDP-11/40 and PDP-11/45 models, the system was rebranded as RSTS/E.

Version Release date Notes
5A-21 July 1973 Memory management expanded from 64KB up to 256KB
5B-24 November 1974 Introduced multiple SWAP files, RTS enhancements, and CCL
5C-01 March 1975 Patch update of V5B without new features
6A-02 August 1975 Added support for new hardware; implemented 22-bit addressing (up to 2 MB); allowed up to 63 concurrent jobs
6B-02 February 1977 Supported additional hardware; SYSGEN utility available under RT-11; runtime CCL introduced
6C-03 February 1978 Incorporated DECnet Phase II, DTR, DIBOL support; introduced SUPERVISOR mode
7.0 August 1978 Supported new hardware with up to 4 MB memory; added RDC support
7.1 February 1981 Kernel mode instruction/data space separation; DECnet Phase III implemented
7.2 August 1982 Added compatibility with new hardware including UDA50 drives
8.0-06 April 1983 Supported MicroPDP-11 hardware platforms
9.0-14 May 1985 Enhanced hardware support; set DCL as default shell; introduced PBS; multiple privilege levels; hashed passwords; new backup utility; Stardate feature added
9.1-05 October 1985 Improved hardware compatibility; multi-threaded FIP implementation; LOAD INDEX feature introduced
9.2-10 June 1986 Added support for additional new hardware devices
9.3-20 January 1987 Enhanced hardware support; incorporated DECnet Phase IV
9.4 July 1987 Supported newer hardware; improved scheduler and terminal services functionality
9.5-08 December 1987 Increased cluster size limit to 64; introduced BACKUP/DIR commands
9.6 September 1988 Added LAT protocol support; HELP SPIKE feature introduced
9.7 July 1989 Supported new hardware platforms; DV0: runtime feature added; ANSI PDP-11C made available
10.0 May 1990 Command line history functionality implemented in TTDRV
10.1 September 1992 Applied Year 2000 (Y2K) compliance fixes


Clones in the Soviet Union

  • DOS-KP (Russian: "ДОС-КП")

Applications

User-11 was sometimes employed by computer service bureaus to manage data on DEC PDP-11 machines running the RSTS/E operating system.

See also

External links

  1. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named PeterDickRSTS80th
  2. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
Retrieved from "https://www.alfawiki.org/index.php?title=RSTS/E&oldid=22783"