Original Idea

The CDC 6000 series was a family of mainframe computers designed by Seymour Cray and James E. Thornton and manufactured by Control Data Corporation in the 1960s. The computers in the series were extremely fast for their time and considered to be the first supercomputers.

Living Computers has recently refurbished and put on-line a CDC 6500 supercomputer. The system was originally used at Purdue University from 1967 to 1989.

This document is a short guide for those interested in exploring the 6500's interactive command environment.

(Note: The primary author worked briefly with a CDC NOS computer 30 years ago, but all information below is based on study of the referenced manuals and experimentation on LC's 6500. We apologize for any inaccuracies and welcome corrections and improvement suggestions.)

1. Start your Secure Shell (SSH) client and connect to cdc6500@tty.livingcomputers.org .
2. After the USER NUMBER prompt enter your user name (your input will be concealed by the row of Xs). You may need to type more slowly than you are used to with other systems.
3. After the PASSWORD prompt type your password (your input will be concealed by the row of Xs).
4. After the RECOVER /SYSTEM: prompt enter a subsystem name (see below) or other command. (Enter RECOVER to recover previously interrupted session.)

[CONNECTED TO MUX6676 LINE 1]


 16/08/24. 20.43.27.
 LIVING COMPUTER MUSEUM 6500.           NOS 1.3-485/11.
USER NUMBER
XXXXXXXXXXXXXXX                                                  ← 2.
PASSWORD
XXXXXXXX                                                         ← 3.
PORT    :      5, TTY
RECOVER /SYSTEM:

The 6500's Network Operating System (NOS) time-sharing system, the Interactive Facility (IAF), includes a number of subsystems, similar to applications on other computer systems, to provide various functions to the user. Subsystems can be selected explicitly by command (see below), or automatically when you select a primary file.

Although the Null subsystem provides a general-purpose environment with file and system utilities, in most cases you can move directly between subsystems as needed without going through the Null subsystem.

A basic understanding of the 6500 file system is necessary to use most IAF comands.

Permanent files are preserved by the system from their creation until their deletion by user command. Each permanent file is owned by a single user and is normally accessible only by its owner, though it is possible to make files accessible by other users as well.

Two types of files are supported:

Direct access: Used for random access and database applications.

Indirect access: Common sequential access files, including program source files.

Whenever an indirect access file is accessed, or a new indirect access file created, the system first makes a temporary copy of the file, to which are directed all references and updates to the file. The temporary file must be saved in order for changes to be applied to the permanent file. Unsaved changes will be discarded at the end of the user's session.

A temporary file is not created when a direct access file is opened. Changes made to a direct access file are immediately applied to the permanent file.

The primary file is the temporary file, usually a program source file, that a user is viewing, modifying, or executing at a given time. Although a user session may simultaneously open multiple temporary files, a given user may have only one primary file at a time.

The currently selected primary file automatically determines the user's active subsystem. When a new indirect access file is saved as a permanent file for the first time, the file system records the active subsystem at the time. Then when the file is selected as primary sometime later, the system automatically activates the original subsystem.

Local files are the set of temporary files and direct access files (permanent files) currently open by a particular job or user session.

File names my be up to seven alphanumeric (upper-case) characters and may not begin with a numeric character. The following file names are reserved by the system:

There are several ways to develop programs using NOS 1.3 on the CDC 6500. Two of them are:

(1) Using the BATCH subsystem the typical edit, compile, run development process can be used with ALGOL, BASIC, COBOL, FORTRAN 4 Extended, Minnesota FORTRAN, and Pascal. Refer to details on the BATCH subsystem, below.

(2) Using the BASIC, FTNTS, and FORTRAN subsystems. These provide environments for interactively creating, modifying, debugging, and running programs:

These three subsystems provide a development environment similar to the original Dartmouth BASIC and versions of Microsoft BASIC for microcomputers and early PCs.

For all subsystems, program source code is stored in indirect access files. The file's subsystem flag, set when first created, indicates the file's source programming language (and compiler version for Fortran source files).

Create new source files, list and select existing source files, view contents, and save changes to source files using the file commands documented above.

Each programming subsystem includes a simple editing function for entering and modifying program source code in the primary file as follows:

To add a source code line: Type a new line sequence number followed by a space and then a program statement. Source code lines will be stored and compiled/executed in the order of line sequence numbers, so lines can be entered in any order.

To modify a source code line: Type line sequence number of the program statement to be changed followed by a space and the modified program statement.

To delete a source code line: Type the line sequence number followed immediately by the Enter key.

• In the BASIC subsystem, use line sequence numbers as the targets of GOTO and other statements.
• In the Fortran language subsystems (FORTRAN and FTNTS), the line sequence numbers are not the same as the line label numbers used by Fortran PRINT/WRITE/FORMAT, GO TO, and other statements. Line label numbers should be inserted in necessary lines between the line sequence number and program statement.
• In the Fortran language subsystems, program statement text Following the line sequence numbers may conform to or ignore standard Fortran column rules at the programmer's choice.
• In the BASIC subsystem, program statement without a preceding line sequence number will be executed immediately and are not added to the primary file. This is useful for testing statements before modifying your program. Use PRINT statements to display results of calculations, etc.

FORTRAN subsystem example Here the FORTRAN subsystem is selected, an existing program is loaded, listed, and run.

FTNTS subsystem example Here the FTNTS subsystem is selected, an existing program is loaded, listed, and run. Note the way the FORTRAN line numbers 190, 210, and 230 as specified in addition to the editing line numbers which do not make up part of the program.

Although the programming subsystems include basic functionality for entering and modifying program source code in the primary file, the NOS Text Editor program (EDIT) provides both advanced editing functions and the ability to edit other local files besides the primary file.

Here is an example session using the EDIT command to create and edit a simple ASCII text file.

The BATCH subsystem provides the ability to create and submit batch jobs as well as run system commands interactively. It is probably the closest to the modern shell or command-line environment.

The typical process is as follows,

• Create a new, empty, file
• Add the program source to the file using the EDIT or XEDIT text editors
• Save the program source file to permanent storage
• Invoke the compiler for the program source language
• Correct any reported errors
• Recompile
• Replace the file in permanent storage with the revised file
• Invoke the compiled loadable-object file

COBOL Here is an example of creating, compiling, and running an example COBOL program. It waits for entry of two integer values, calulates the product and prints the result.

Use the ACCESS subsystem to communicate with other users connected to the 6500.

Share permanent files with other 6500 users.

In order to transfer data to or from the 6500, your best option is to copy and paste. If you're having trouble pasting in programs, you may want to try using TeraTerm after altering the line delay under Setup → Additonal settings → Copy and Paste → Paste delay per line to about 250ms.

1. BASIC Language Version 2 Reference Manual (PDF). Control Data Corporation. Oct. 1974. Accessed Nov. 11, 2017.
2. FORTRAN Extended Reference Manual Version 4 (PDF). Control Data Corporation. Oct. 22, 1971. Accessed Nov. 11, 2017.
3. Interactive Facility Version 1 Reference Manual (PDF). Control Data Corporation. Aug. 10, 1979. Accessed Nov. 11, 2017.
4. NOS Version 1 Reference Manual Volume 1 of 2 (PDF). Control Data Corporation. Dec. 3, 1976. Accessed Nov. 11, 2017.
5. NOS Version 1 Text Editor Reference Manual (PDF). Control Data Corporation. Mar. 8, 1976. Accessed Nov. 11, 2017.
6. COBOL Reference Manual (PDF). Control Data Corporation. Jun. 1967. Accessed Sep. 10, 2019.
7. Pascal Version 1 Users Manual (PDF). Control Data Corporation. Sep. 1983. Accessed Sep. 9, 2019.

The author would like to make the following improvements to this document:

• Document compilation and execution of programs with FORTRAN subsystem.
• XEDIT text editor command guide.
• Batch subsystem guide continued, add FORTRAN and Pascal examples.
• Execute subsystem guide.