Digital PDFs

EK-T11SY-OP-001

February 1975

124 pages

Original

6.8MB

Document:	TMS-11 System Managers and Usrs Guide
Order Number:	EK-T11SY-OP
Revision:	001
Pages:	124
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/typeset-11/EK-T11SY-OP-001_TMS-11_System_Managers_and_Usrs_Guide_Feb1975.pdf

OCR Text

TMS-11 System
Manager's
and User's Guide

For

additional

copies

order

No.

EK-TllSY-OP-OOI

from Marketing Manager - Typeset-ll

Graphic Arts Dept., Digital Equipment Corporation, Maynard, Mass.

Price $10.00

digital equipment corporation · maynard. massachusetts

1st Edition, February 1975

The material in this manual is for informational
purposes and is subject to change without notice.
Digital Equipment Corporation assumes no responsibility for any errors which may appear in this
manual.

Printed in U.S.A.

The following are trademarks of Digital Equipment
Corporation, Maynard, Massachusetts:

DEC
FLIP CHIP
DIGITAL

PDP
FOCAL
COMPUTER LAB

CONTENTS
Page
CHAPTER 1

INTRODUCTION

1.1
1.2
1.3
1.3.1
1.3.2
1.3.3
1.3.4
1.4
1.5

PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COMPANION DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DOCUMENTATION CONVENTIONS . . .
. . . . . . . . . . . . . . . . . . . . . .
Carriage Return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Blank Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Braces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Angle Brackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTROL CHARACTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VT20 COMMAND MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 2

SYSTEM MANAGER'S INFORMATION

2.1
2.1.1
2.1.2
2.2
2.3
2.4

SYSTEM DESCRIPTION
The Monitor Console Routine
System Terminals
SYSTEM CONFIGURATION
INPUTS . . . . . . . . . . .
EDIT FUNCTION OPTIONS

CHAPTER 3

FILE IDENTIFICATION AND ACCESS

3.1
3.1.1
3.2
3.3
3.4
3.4.1
3.4.2
3.4.3

FILE NAMING CONVENTIONS
Wild Card Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILE PROTECTION AND ACCESS . . . . . . . . . . . . . . . . . . . . . . . . .
FILE FLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILE FLOW OPTIONS
.............................. .
Routing Files Using Justify Command . . . . . . . . . . . . . . . . . . . . .
Routing Files From Input Tapes . . . . . . . . . . . . . . . . . . . . . . . . .
System Flow By Default Standards . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 4

QUEUE MANAGER

4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.2.1
4.4.2.2
4.4.2.3
4.4.2.4
4.4.3
4.4.3.1
4.4.3.2
4.4.3.3
4.4.3.4
4.4.3.5
4.4.3.6
4.4.4

QUEUE MANAGER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUEUES ., . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USING QUEUE COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUEUE ENTRY COMMANDS
...............................
Using Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Print Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Punch Command . . . . . . . . . . . . . . . . . . . . . . . . . .
Set Command
Output Command Switches . . . . . . . . . . . . . . . . . . . . . . .
Justification Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Justify Command
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
JH Command
. . . . . . . . . . . . .
. . . . . . . . . . ..
JS Command
. . . . . . . . . . . . . . . ..
. . . . . . . . . . ..
JTCommand
. . . . . . . . . . ..
JC Command
JPCommand
. . . . . . . . . . . . ..
Justify Control Switches .

............... .

. . . . . . . . . . . ..

iii

1-1
1-1
1-3
1-3
1-3
1-3
1-3
1-3
1-3

2-1
2-1
2-1
2-3
2-3
2-4

3-1
3-2
3-2
3-4
3-5
3-5
3-6
3-7

4-1
4-1
4-2
4-2
4-3
4-3
4-3
4-3
4-4
4-4
4-4
4-4
4-4
4-4
4-5
4-5
4-5
4-5

CONTENTS (Cont)
Page
4.4.5
4.4.5.1
4.4.5.2
4.4.5.3
4.4.5.4
4.5
4.5.1
4.5.2
4.6
4.6.1
4.6.1.1
4.6.1.2
4.6.1.3
4.6.1.4
4.6.2
4.6.2.1
4.6.2.2
4.6.2.3
4.6.2.4
4.6.2.5
4.6.2.6
4.6.2.7
4.6.2.8
4.6.2.9
4.6.2.10
4.6.3
4.7
4.7.1
4.7.2

Queue Control Commands . . . . .
Queue Output Commands .
Queue Activation
Queue Deactivation
Queue Manager Exit ..
ASSIGNING PRIORITY . . . . . .
Modifying File Priority . . . .
Removing an Item from a Queue .
SYSTEM STATUS . . . . . . . . . . .
System Status Reports ..
Abort Status .
Queue Status . . . .
Spooler Status .. .
Active Queue Listing
Story Status . . . . . . .
Select by Story Name
Select by Story Status
Select by Item Number
Select by Queue Name
Select Expanded Listing Format
Select All Terminals
Select All Time . . . . . . . .
Select Last Item
Select Line Printer For Listing
Select Last Listing Format ..
Combined Queue Listing Commands
THE ALLOTTER . . . . . .
Machine Status Update .
Machine Status .

CHAPTERS

SYSTEM OPERA nON

5.1
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.3
5.3.1
5.3.2
5.3.3
S.3.4
5.3.5
5.3.6
5.3.7

MONITOR CONSOLE ROUTINE
RSX-llD COMMANDS
Mount Command
Dismount Command .
Enter Time Command
Active Task List Command
Request Command
Abort Command ..
Unload Command
Load Command
. . . . . .
TYPESET-II UTILITY COMMANDS
Directory Command ..
Proof Extract Command
The Delete Command
The Rename Command
The Copy Command
Append Command .
The Merge Command

4·6
4·6
4-6
4-6
4-7
4-7
4-7
4-7
4-8
4-8
4-8
4-8
4-8
4-8
4-9
4-9
4-9
· 4-10
· 4-10
· 4-10
· 4-11
.4-11
· 4-11
· 4-11
· 4-11
. . . 4-12
. . . . . . 4-12
. . 4-12
· . . . . . . 4-13

5-1
5-1
5-1
5-1
5-1
5-1
5-2
5-2
5-2
5-2
· . . . . .. 5-2
· . . . . . . 5-3
5-6
· . . . . .. 5-7
5-8
· . . . . .. 5-8
· . . . . . . 5-9
· . . . . . . 5-10

CONTENTS (Cont)

Page
5.3.8
5.3.9

The Protect Command
The Unlock Command

. . . 5-10
. . . 5-11

CHAPTER 6

HOUSEKEEPING OPERA nONS

6.1
6.1.1
6.1.2
6.1.3
6.2
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.4
6.4.1
6.4.1.1
6.4.2
6.4.2.1
6.4.2.2
6.4.3
6.4.3.1
6.4.4
6.4.5

HOUSEKEEPING DISK PACKS AND FILES . . . . . . . . . . . . . . . . . . . . . . ..
Minor Housekeeping (Designating Files to be Saved) . . . . . . . . . . . . . . . . . .
Daily Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Weekly Housekeeping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BACKUP DISK PACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXCEPTION WORD DICTIONARY UPDATE PROGRAM . . . . . . . . . . . . . .
DIC Input . . . . . . . . . . . . . . . . . . . . . . . . .
. ........ .
Correcting and/or Deleting Words . . . . . . . . . . . . . . . . . . . . . . . . . . .
............................. .
Installing and Running DIC
Optional DIC Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exiting and RemOving DIC . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hyphenation Symbology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FORMAT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using J&H to Create Formats . . . . . . . . . . . . . . . . . . . . . . . . . .
System (protected) Formats . . . . . . . . . . . . . . . . . . . . . . . . . .
Protecting an Existing Format . . . . . . . . . . . . . . . . . . . . . . . . . .
Unprotecting a Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Altering a F orrna t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................
Altering a Temporary Format using J&H
Deleting Formats . . . . . . . . . . . . .
. . . . . .
. . . . . . . . . . . ..
Managing Temporary Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 7

ERROR MESSAGES

7.1

GENERAL . . . . . .

6-1
6-1
6-2
6-2

6-3
6-3
6-3
6-3
6-4
6-4
6-5
6-5

6-6
6-6
6-6

6-6
6-6
6-7
6-7
6-7
6-7
6-7

. . . . . . . . . . . . . . . . . . . . . . ..

7-1

CHAPTERS

STARTUP AND SHUTDOWN OPERATION

8.1
8.2
8.3
8.4
8.5
8.6
8.7
8.8
8.9

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TYPESET-ll SYSTEM INITIALIZATION
. . . . . . . . . . . . .
STARTING THE TYPESET-II SYSTEM . . . . . . . . . . . . . . . . . .
REST ARTING THE TYPESET-II SYSTEM
........................
SHUTTING DOWN THE TYPESET-II SYSTEM . . . , . . . . . . . . . . . . . .
NORMAL Vf20 RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RELOADING Vf20 AT THE PDP-l 1/45 (MCR CONSOLE) . . . . . . . . . . . .
BOOTSTRAP LOADER LOADING PROCEDURE
. . . . . . . . . . . . . .
LOADING Vf20 DIAGNOSTICS . . . . . . . . . . . . . . . . . . . . . . . . . .

8~ 1
8-1
8-2
8-4
8-5
8-6
8-6
8-7
8-7

CHAPTER 9

RECOVERY PROCEDURE

9.1
9.1.1
9.1.2
9.1.3
9.1.4
9.1.5

SOFTWARE RECOVERY PROCEDURES
Recovery from System Crashes
. . . . . . . . . . . . . . . . . . . . .
Recovery from System Hangs . . . . . . . . . . . . . . . . . . . . . .
Recovery from Vf20 Hangs . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . .
Task Aborts . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Task Aborts

9-1
9-1
9-1
9-1
9-1
9-1

CONTENTS (Cont)
Page
9.1.6
9.1.7
9.2
9.2.1
9.2.2
9.2.3
9.2.4
9.2.4.1
9.2.4.2
9.2.4.3
9.2.4.4
9.3
9.3.1
9.3.2
9.3.3

Running V~rify
....................................
Reporting Software Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HARDWARE RECOVERY PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LA30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Input/Output Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Input-Readers . . . . . . . . . _ . . . . . . . . . . . . . . . . . . . . . . ..
Input-VT20s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output-Paper Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Output-On-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BACKUP SYSTEMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Backup Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Software Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

CHAPTER 10

TYPESET SYSTEM EQUIPMENT OPERATION

10.1
10.2
10.3

RELOADING THE TAPE PUNCHES . . . . . . . . . . . . . . . . . . . . .
LPII PAPER INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . .
DISKPACK AND CARTRIDGE HANDLING . . . . . . . . . . . . . . . . .

CHAPTER 11

PREVENTIVE MAINTENANCE

11.1
11.2
11.3
11.4
11.5
11.6
11.7

COMPUTER AIR FILTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
TAPE READERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
TAPE PUNCHES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
PAPER TAPE SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
DEC TAPE TRANSPORTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
LINEPRINTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
DEC DISK AIR FILTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

APPENDIX A

GLOSSARY

APPENDIX B

COMMAND SUMMARY

B.l
B.2
B.3
B.3.1
B.4
B.5

QUEUE COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QUEUE LIST COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OUTPUT COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Justify Command Switches
..............................
UTILITY COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MCR COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..

APPENDIX C

LOADING FORMATTER PROGRAMS USING mE ABSOLUTE LOADER

C.1
C.2

BOOTSTRAP LOADING PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . .. C-l
FORMATTER LOADING PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

9-1
9-2
9-2
9-2
9-2
9-2
9-2
9-2
9-2
9-2
9-3
9-3
9-3
9-3
9-4

10-1
10-1
10-2

B-1
B-2
B-3
B-4
B-4
B-5

CONTENTS (Cont)
Page
APPENDIX D

RP02/RP03 DISK DRIVE CONTROLS AND FORMATTING PROCEDURES

D.1
D.2
D.2.1
D.2.2
D.2.3
D.2.3.l
D.2.3.2
D.2.4
D.2.4.l
D.2.S
D.2.S.l
D.2.S.2
D.2.S.3
D.2.6
D.2.6.1
D.2.6.2

RP02/RP03 CONTROLS
...... .
RP02/RP03 DISK FORMATTER
Requirements
Loading Procedure . . .
Standard Formatter
Starting Procedure
Operating Procedure
Starting Procedure . . . .
Operating Procedure
Special Formatter
Starting Address ..
Operating Procedure
Parameter Changing
Errors
...... .
Error Halt
Error Printouts

APPENDIX E

RFll/RSll CONTROLS, INDICATORS, AND FORMATTING

E.l
E.1.1
E.1.2
E.2

CONTROLS AND INDICATORS
RSll Controls . . . . .
RF 11 Indicators . . . .
RFlljRSl1 FORMATTING .

APPENDIX F

DECTAPE CONTROLS AND FORMATTING

F.1
F.2
F.2.1
F.2.2
F.2.3
F.2.4
F.2.S
F.2.S.1
F.2.6

DEC TAPE CONTROLS . . . . . . . .
DEC TAPE FORMATTER . . . . . . . .
Loading Procedure (Using PR68-E)
Preliminary Operations . . . . . . .
Starting Procedure .
Operating Procedure
Errors
Error Halt
Error Printouts

APPENDIX G

RKOS DISK DRIVE CONTROLS AND FORMATTING PROCEDURE

G.I
G.2
G.2.1
G.2.2
G.2.3

CONTROLS AND INDICATORS . . . . . . . .
FORMATTING RKII DISK CARTRIDGES·
Program Loading .. . . . . . . . . . . .
RKOS Drive Cartridge Mounting Procedure
Format Program . . . . . . . . .

APPENDIX H

LA30 CONTROLS AND INDICATORS

H.l

CONTROLS AND INDICATORS

D-l
D-l
D-l
D-2
D-2
D-2
D-2
D-2
D-2
D-2
D-2
D-2
D-3
D-3
D-3
D-3

E-l
E-l
E-l
E-S

F-I
F-3
F-3
F-3
F-3
F-3
F4
F4
F4

G-I
G-I
G-I
G-3
G-3

. . . . . . . . . . . . . . . . . . . . . . . . . . . H-I

vii

CONTENTS (Cont)

Page
APPENDIX I

TAPE FORMATS

I.1
1.2

INPUT TAPE FORMAT
OUTPUT TAPE FORMAT

APPENDIX)

FORMATTING DISKS USING ROLLIN

J.I

LOADING ROLLIN PROGRAM
FORMATTING RKOS DECPACKS
FORMATTING RP03 DISK PACK

J.2
J.3

1·1
1·1

J·I
J·I

J·2

ILLUSTRATIONS
Figure No.
2·1

2·2
2·3
3·1

3·2
3·3

4·1
6·1
D·I
E·I
E·2
F·I

F·2
G·I
H·I
H·2

Title
Typical Production Cycle
Typical Typeset· 1 I Hardware Configuration
Typical File Flow . . . . . . . .
Example Of File Access Hierarchy .
File Flow Options . . . . . . . . .
File Flow Options . . . . . . . . .
Queue Manager, Queues, and Spoolers .
A Partial LP Listing of a IHY Generated JHDICT .PRF File
Maintenance Panel . . . . . . . . . . . . . . . . . .
Write Lockout Switches
RF 11 Indicators . . . .
DECtape Controls
. . . . . . . . . .
Maintenance Panel Controls and Indicators
Controls and Indicators· RKOS
LA30 Keyboard and Controls . . . . .
LA30 Power Controls

Page
2·2

2-4
2·5

.. 3-4
3·5
3·6
4·1

6·5
D·I
E·2

E-4
F·3

F-4
G·I
H·2
H·2

TABLES

Table No.
1·1
2·1
3·1
4-1
6·1

6·2
8·1

8·2
9·1
11·1
11·2
C·I

Title

Page

Typeset·ll Control Characters ..
. . . . . . . . .
1·3
Typeset·ll Programs . . . . . . . .
. .....
2·3
File Syntax Summary by Command
. . . . . . . . .
3·3
.......... .
List of Typeset. 1 I Queues and Spoolers
4-2
DIC Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6·5
Hyphenation Symbols and Corresponding Messages . . . . . . '. . . . . . . . . . . . . . . 6·6
........................ .
Bootstrap Loader
8·7
VT20 Diagnostics . . . . . . . . . . . . . . . . . . . . .
8·7
Hardware Backup Devices and Procedures . . . . . . . . .
9·3
Preventive Maintenance Checklist for Typeset.ll Systems .
11·2
Paper Tape Specifications
. . . . . . . . . . . . . . . .
11·3
.................................... .
Bootstrap Loader
C·1

viii

TABLES (Cont)
Table No.
E-l

E-2
E-3
F-l
G-l
H-l

Title

RS 11 Controls . . . . .
RF 11 Address Indicators
RF11 Error Indicators .
TU56 DECtape Transport Controls
Controls and Indicators
LA30 Controls and Indicators

Page
E-l

E-2
E-2
F-l
G-2

H-l

CHAPTER 1
INTRODUCTION

1.1 PURPOSE
This manual provides a description of the Typeset-II
system and explains how to use the system. A description of all Typeset-I I commands and examples
showing how to use them are provided for the System
Manager and Users.

1.2 COMPANION DOCUMENTS
The following documents pertain to the Typeset- I I
system. These manuals are not required for normal
Typeset-II operation, but some users may want them
to enhance or extend their systems operation and capabilities.

Document
Title

Document
Number

Introduction to RSX-llD

DEC-I1-0XINA-A-D

An introduction to the talents, capabilities, and features of RSX-I 10.

RSX-IID Operations Procedures

DEC-I1-0XDOA-B-D

A description of RSX-I1D Monitor Console Routine
(MCR) commands and how to use them.

RSX-I1D Concepts and
Capabilities

DEC-II-OXDCA-B-D

A presentation of the application and programming
of RSX-11D systems.

RSX-IID System Genera-,
tion Reference Manual

DEC-II-OXDIA-B-D

Provides .information to generate systems (programs)
to operate under RSX-11D executive.

RSX-IID Executive Reference Manual

DEC-II-OXERA-A-D

Provides information about control and operation of
the the RSX-I1D executive.

RSX-IID 1/0 Operations
Reference Manual

DEC-II-OXFSA-A-D

Provides RSX-11D operator information and a description of all RSX-I1D commands.

RSX-1ID Utility
tions

Opera-

DEC-II-OXUPA-A-D

Provides a description of all RSX-IID utility programs. (PIP, VERIFY, FILEX).

RSX-IID Task Builder
Reference Manual

DEC-II-OXDLA-B-D

Provides information to generate RSX- II 0 tasks to
operate under the RSX-I 10 system.

RSX-llD
Techniques

DEC-1I-OXDDA-B-D

Provides the programmer with information to debug
programs generated to operate under RSX-11 D.

Debugging

Description

1-1

Document
Title

Document
Number

RSX-UD Device Handler
Reference Manual

DEC-II-OXDHA-A-D

Provides information about the RSX-IID Devici
Handler Programs.

RSX-IID Writing Device
Handler Task

DEC-II-OXPHA-A-D

Provides information to write RSX-IIO Devicl
Handler Programs

RSX-IID MACRO Assembler Reference Manual

DEC-II-OXDMA-8-G

Provides information for the user to write program
in MACRO language.

RSX-llD FORTRAN IV
Complier and Object Time
System Reference Manual

DEC-II-OXFMA-C-D

Provides information for RSX-llD users to writl
source programs in FORTRAN, the source progran
for RSX-IID.

RSX-II D System Test
Reference Manual

DEC-II-OXSTA-8-D

Provides timing information about RSX-IID perform
ance.

RSX-llD System Generation and Installation
Guide

DEC-II-OXDIA-A-D

Defines the procedures used to install, update, anI
test an RSX-II D system.

PDP-11/45
Handbook

112.01071.1876

A detailed description of PDP-1l/45 hardware anI
software to assist programmers, engineers, and opera
tors in the operation of the PDP-I 1145 computer.

LA30 DECwriter Maintenance Manual

DEC-OO-LA30-D

General information about operation, installation
and maintenance of the LA30 DECwriter.

RP II Disk Pack Controller
Maintenance Manual

DEC-CS-RPII-D

A complete description of the RP] I Disk Pack Con
troller.

Typeset-II VT20 Operator's Guide

DEC-II-HVT20A-A-D

Provides user information required to operate thl
POP-}] Text Editing Option.

Typeset-II Markup Manual

DEC-IIHMUPA-A-D

Provides information for the user to create format
and mark up copy for typesetting

Typeset-II System Error
Messages Manual

DEC-II-HSYEA-A-D

Provides a description of the error messages gener
ated by the system and general recovery techniques.

Typeset-II Class Ad System User's Guide

DEC-II-HCADA-A-D

Provide information for using the classifed ad system

Processor

Description

1·2

1.3

DOCUMENTATION CONVENTIONS

Table I-I
Typeset-II Control Characters

1.3.1 Caniage Return
A carriage return (the CR key) is always typed at the
end of a command string to indicate that the command is complete. The carriage return notation used
in this manual is the symbol <CR>. These angle
brackets are for clarity only, and should not be typed.

Control Character

Function

Wake up the Monitor Console
Routine. If no operator commands are entered at the MCR
t~rminal,
after approximately
one and one-half minutes, the
keys on the .terminal are disabled . and <CTRL C> must
be typed to reactivate the terminal.

Quit the mode that is presently
in operation and return to
MCR mode. For example, if the
user is doing PIP functions and
wishes to return to MCR, he
would type <CTRL Z>. The
previous operation must be
completed and a response
printed at the terminal, i.e.,
PIP> before this will work.

Stop typeout of information on
the terminal. This is normally
used during startup and shutdown operations to stop printout of information at the MCR
terminal.

At the terminal type out the
line of commands just entered.

At the terminal cancel the line
of commands just entered.

<ALT>

Deactivates the LA30 (disables
LA30 keys). <CTRLlC> must
be typed to reactivate the terminal. <ALT> is used instead of
<CR> for some special MCR
commands.

1.3.2 Blank Spaces
No symbol is used in this manual to denote blank
spaces.

1.3.3 Braces
Braces [ ] are used to indicate that a choice must be
made from the enclosed information or that the use
of the feature is optional.

1.3.4 Angle Brackets
Angle brackets < > are used to enclose· the keys
where necessary for clarity throughout the manual,
but the brackets are not typed.

For example, <RUBOUT> means the RUBOUT
key.

1.4 CONTROL CHARACTERS
Control characters such as are typed at the sy~tem
console only (not at the vt20) by holding down the
CTRL key and depressing the letter C. The angle
brackets should not be typed. The Typeset-II system
control characters are' listed in Table 1-1.
I.S VT20 COMMAND MODE
The © symbol is used before all commands. that can
be used on the VT20 to indicate that the VT20 must
be in the command mode when the command is
given. The © symbol, followed by a line of dots. is
displayed on the VT20 screen when the <CMND>
key is depressed; the key is lit to indicate that the
VT20 is in the command mode. If the VT20 is
already in command mode, depressing the
<CMND> key will cancel command mode.

1-3

CHAPTER 2
SYSTEM MANAGER'S INFORMATION
schedules jobs so that many operations can be performed simulta~eously. This type of operation is
called timesharing.

2.1 SYSTEM DESCRIPTION
The Typeset-II System is a large volume. multi-task
processing system. which allows copy preparation (inputting. editing. processing. and outputting). data
flow control. and system management operations to
occur simultaneously. An entire publication can be
stored. proofed. edited and corrected. or revised before the text is phototypeset.

2.1.1 The Monitor Console Routine
The interface between the Typeset-II programs and
the RSX-IID system is provided by the Monitor
Console Routine (MCR). MCR dialogue is established by typing <CTRLlC> on the system console.
This causes an MCR Dispatch Task to run, which
outputs an MCR> prompting symbol and reads a
line of command input. The command input line indicates the function to be performed and contains
parameters when necessary. The Dispatch Task causes
an MCR Function Task to run which performs the
requested function. There is one MCR Function Task
for every MCR function. If the system is running an
MCR Task. which uses the MCR console to carry on
a further dialogue with the user. typing <CTRLlC>
on the console will not cause MCR> to be printed
out. The user must wait until the previously requested
task is completed.

Proof copies can be output on a high-speed line
printer. Copy editing and rearranging is done off-line
at the VT20 Display Terminal using the computer's
time for data transmission only. The final text is output to an on-line photocomp machine or paper tape
punch. The production cycle of the system (Figure 21) consists of the following steps:
1.
2.
3.
4.
S.
6.
7.

Story Markup
Input Tape Preparation or File Creation
Processing of Files by J and H Program
Proofreading
Correcting
Reprocessing by J and H if necessary
Output Tape Preparation (Final Punch) or
Output to an on-line Photocomp Machine

The Typeset-II System has MCR functions to provide system status, perform task scheduling. change
logical unit assignments, etc.

Copy may be coded in advance for the perforator operators by the markup personnel. Input tapes are prepared from the coded copy by the perforator operators. The tapes are read into the system via the highspeed tape readers and stored on disk packs for editing at the VT20.

2.1.2 System Terminals
There are two types of terminals in the system. The
MCR terminal may be an LA30 DECwriter or a
VT05. It is recommended that use of the MCR terminal be limited to the sys~em manager. All RSX-IID
and Typeset-II commands except Create and Edit
may be given from this terminal. The VT20 terminal
is normally used for edit operations, some input/output operations, and utility operations (i.e., directory)
that are listed in the VT20 Users Guide. The system
manager may use this terminal for some of his control and supervisory functions. The VT20 cannot be
used to issue RSX-llD commands.

The Typeset-II System consists of a combination of
programs (software and hardware) which are integrated into a typesetting .system. All of the programs
in. Table 2-1 operate under an executive program
called the RSX-llD Operating System. RSX-llD allocates the use of the central processor's time and

2·1

STORY
MARK-UP

ON LINE
STORAGE

CREATE

PROOF
COpy

CORRECTIONS

CORRECTED
PROOF COPY

'.>'"'-"-...... FINAL PUNCH

11-2227

Figure 2-1 Typical Production Cycle

2-2

2.2 SYSTEM CONFIGURATION
A typical Typeset-II hardware configuration (Figure
2-2) consists of the following:

Table 2-1
Typeset-II. Programs
Program

Function

Queue Manager

The Queue Manager program is
the controller of the system, building and maintaining queues for
the transmission of requests between component tasks (Spoolers,
J and H. and the VT20 terminal
program.)

Spoolers

Handlers

Application
Monitor

VT20 Software

J and H

CLASS-AD
Management
System

Allotter

PDP-III45 central processor unit with at least
80K of memory.
VT20 Text Editing Subsystem for edit and file
manipulation operations. Each VT20 subsystem
has two display terminals.
LA30 DECwriter or VT05 video display terminal system control and monitoring.

The Spooler programs handle all
input/output activity for sequential
character devices (paper tape readers. punches. photocomps. and line
printers).

RPllC controller with two RP03 disk pack
drives.
RFll controller with RSII fixed head disk
drive for program storage.

Handlers are special tasks under
RSX-IID that control the actual
machine input/output.

TM II controller with TV 10 magnetic tape
drives for program loading and data backup.

The Application Monitor controls
VT20 terminal processes and provides functions for file control,
editing functions. and queue operations.

PA611 controller with dual PR68 paper tape
readers and PP67 paper tape punches.
LPDIlILPCOI photocomposition interface that
is designed and configured for the user's photocomposition machine.

The VT20 software consists of the
programs in the PDP-IlI05 processor that control two VT20 terminals and communicates with the
main computer while editing story
files.

LPll or LV II column line printer to provide
proof copy for editing.

2.3 INPUTS
The Typeset-II System supports multiple inputs from
the following sources:

J and H will accept a stream of input files from the JAH queue and
determine the proper word breaks
and line endings for text to be set
on a photocomp machine.

Paper tape input prepared by a perforator
operator.
2. Wire service communications (via paper
tape).
3. Optical Character Readers (OCR) via paper
tape.

This is an optional system that
may be added to the software system. enabling the user to maintain
ads in a data base.

Data from keyboard perforators or OCR is expected
to be in TIS code. which is customized for each
user's system. The input spoolers use customized tables to convert the input data, which is in TIS code.
to the standard ASCII code used by the Typeset-II
System. The data is stored on the system disk as files.
under names specified in a header punched in front
of each story (Appendix I). The area in the directory

The Allotter is a program that
maximizes the effectiveness of the
photocomp spooler. i.e., it routes
files to an available photocomp
with the appropriate setup to handle the file.

2-3

PR68E
TAPE
READER

RS!!
DISK
DRIVE

I--

I
I
PR68E
TAPE
READER

MAGTAPE
r--- TRANSPORT

PA6!!
READER
PUNCH
CONTROL

PP67
TAPE
PUNCH
I

~
)

I--

(BACKUP)

I
UP TO 4
APE READERS

TU10

2 RK05 OR RP03
DISK DRIVES

TU56
DECTAPE
TRANSPORT
(DUAL DRIVE)

IPDP-lt/45
CENTRAL
COMPUTER WITH
80 K OF CORE
MEMORY

PA6!t
READER
PUNCH
CONTROL

I
UP TO 4
PUNCHES
I

I--

PP67
TAPE
PUNCH

LPCtl
PHOTOCOMP
INTERFACE

PDP-II/05
COMPUTER

LA30
DECWRITER
TERMINAL

LPt t
LINE
PRINTER

VT20
TERMINAL
AND
KEYBOARD

USERS
PHOTOCOMP
MACHINE

11-2283

FigQre 2-2 Typical Typeset-II Hardware Configuration

may also be defined for each input device by default
so that all stories from a particular input device are
sent to a specified user area.

Notice that both wire services are input with a .WIR
extension and a version number of I.
Some wire service stories are received in advance of
the date they are to be released. If specified at installation time, a file storage option can be included that
routes advanced wire service stories to the local pool
UIC. This allows wildcarding to be used for renaming
advance files to a wire service advance pool.

Copy from wire service is also input to the system on
paper tape. Wire service stories are automatically
stripped to remove all justification and hyphenation.
The copy is then handled as any other copy, i.e.,
stored for editing on the VTIO and routed automatically to justification and hyphenation. Defaults may
be set up to route the justified and hyphenated copy
to a photocomp machine or to the disk for storage.

2.4 EDIT FUNCTION OPTIONS
Two edit function options are available and must be
specified at installation. When a file is edited, the
new version(s) can either remain in the UIC area
logged into or, if the file resides in anotht.. UIC area,
it can be returned to that area. For example, if a file
(STORY.HOT;I) is created in UIC [20,4] and a user
logged into [77.1] wishes to edit that file, the edited
version can either remain in [77,1] or return to [20,4]
depending on the system file flow structure.

Filenames for wire service stories are structured to
differentiate between AP and UPI services. The
header of a wire service story identifies which service
is sending the story; the Typeset-II system appends
either the letter A (for AP) or the letter U for (UPI)
to the beginning of the filename. Thus, if story A 104
is from the AP wire service, the filename becomes
AAI04.WIR: 1. If a story from UPI happens to have
the same name, the filename becomes UAI04.WIR;1.

Typical file flow for a Typeset-II system is shown in
Figure 2-3.

2-4

INPUT
SPOOLER

J AND H

PROOF
COPY

UNJUSTIFIED
TEXT FILE

SET FILE
(BINARY)

PRINT
SPOOLER
PROOF FILE
OUTPUT
SPOOLER

EDIT

EDITED
TEXT

APPLICATIONSI-_ _ _ _ _ _ _ _ _ _ _ _....J
MONITOR

UTILITY
AND PIP
OPERATIONS

CP-OB4B

Figure 2-3 Typical File Flow

2-5

CHAPTER 3
FILE IDENTIFICATION AND ACCESS
[G,U] = gro.up
and
user
(default = lo.gged in user).

Each jo.b, or take, o.n the Typeset-II system is sto.red
as a file. Since each user may have many files, there
must be a metho.d fo.r keeping ali o.f these files separate. This is acco.mplished by giving each user a
unique area in the data base o.f the system. This area
is identified by the user's group-and-user number.
Fo.r example, if the group-and-user number is 1,3 the
user has an area in the data base identified by that
number. Each file created Dr each file input to. the
system o.n paper tape with that group-and-user number go.es to. the co.rresPo.nding area and is uniquely
named.The group-and-user number is also. referred to.
as the User Identificatio.n Co.de.

number

= file name with up to. 9 alphanumeric
characters.

EXT = file type with up to. 3 alphanumeric
characters (defimlt = co.mmand dependent).
VER = versio.n number (default
sio.n).

latest ver-

Since files are identified by their name and their
group-and-user number, two. users may use the same
filename as lo.ng as they have different group-anduser numbers. The files will be distinct and separate.
Fo.llo.wing are so.me filename examples:

3.1 FILE NAMING CONVENTIONS
Each file is assigned a device, group-and-user number, and filename. The device is the name o.f the
piece o.f hardware where the file is stored; the gro.upand-user number is the area assigned to. the user. The
file name is the actual name o.f the file, and the file
extensio.n (file type) indicates what catego.ry the file is
asso.ciated with. The file name and the file extensio.n
are separated by a perio.d. The extensio.n is fo.llo.wed
by a semico.lo.n and a versio.n number. The TypesetII files are identified as fo.llo.ws:

BOSTON.MON;l
JERRY.TUE;4
STORY.SUN;i
STORY.SUN;2
STORY.SUN;3

Three versio.ns o.f the same
sto.ry sto.red in separate files.

FILE = DEV:[G,U]FN.EXT;VER where:
The file extensio.n co.uld be used to. indicate the date
the info.rmatio.n in the file is to. be printed. Fo.r example:

DEV = device and unit number as fo.llo.ws (default = system disk, unit 0):
DPx
DFx
MTx

RP03 Disk
DFII Disk
Magtape Drive

x is the unit number o.f device

3-1

EXTENSION

POSSIBLE MEANING

.sUN
.F5
.M2

Sunday
February fifth
Mo.nday seco.nd editio.n

Identifying stories that are printed on a certain day is
helpful during housekeeping operations. For example
if all stories that are used in the Monday edition of a
paper have a .MON extension, the user can delete all
of these files with one simple command.

Alternatively, the command:
©DE FILA.*;*<CR>
means delete all files in the user's data base with a
file name of FILA, regardless of the file extension or
version, and the command:

A new version number is assigned to a file each time
a file change operation takes place, (i.e., EDIT, JAR).
The file with the highest version number is always
the latest file. If no version number is specified when
a command is given, the latest version number is automatically used.

©DE *.*;*<CR>
means delete all files in the user's data base regardless of file name, file extension, or version.

Paper tape filenames are assigned to a file when it is
punched on paper tape by the perforator operator
(See Appendix I for tape formats). When the paper
tape is input to the system the leader contains the file
name, extension, and the group-and-user number. If
no extension is supplied when the file is input the
system supplies a .PRF extension. This information is
recorded in the directory so that the file can be retrieved when the user is ready to edit the file. If no
VIC is supplied, the file will be stored in the user
area associated with the input device.

Table 3-1 lists the VT20B commands and indicates
whether wild card features can be used or not. Also
included is default and multiple file information.
3.2 FILE PROTECTION AND ACCESS
File Protection and access is determined by the
group-and-user number (VIC) and passwords (Figure
3-1). The VIC is a sequence of two numbers represented as G,V where both G and V are from one to
three digits. The first number, G, represents a group
and the second number, V, represents an individual
user in that group. Each VIC represents an area
where the group and user may store files. There are
four levels of VIC codes:

3.1.1 Wild Card Conventions
In order to provide an efficient method for referencing multiple files, a 'wild card' feature is included in
Typeset-II. The wild card is the asterisk character (*)
which is used to signify any file name, file extension,
or version number.

1. System Manager: Privileged to read, write,
and delete files in any user area.
2. Controllers: Privileged to read, write, and
delete files in any area in their newspaper.

For example, in order to delete file FILA.SVN;4
from the system the following command is required:

3. Supervisors: Privileged to read, write, and
delete all files in their group's user area(s).

©DE FILA.SVN;4<CR>
In order to delete files:

4. Operators: Privileged to read, write, and
delete files in their unique area.

FILA.MON;l
FILB.MON;2
FILC.MON;l

Files in the common pools (Figure 3-1) may be read
(copied) by users in any area. The System Manager is
the only user who can copy files back into these areas.

it is only necessary to provide the command:
©DE *.MON;*<CR>

Files that are not assigned a VIC when they are input to the system are input to the newspaper pool
and may be accessed by anyone in that newspaper.
The controller or supervisor may assign these files to
an operator after they are in the system, and the operator can copy them into his area.

where the asterisk (*) means all files in the user's
data base, with the file extension .MON, regardless of
file name or version. This could be used to delete all
files with a particular .day extension.

3-2

Table 3-1
File Syntax Summary by Command

Wild Carding Allowed

Command

File Name

Extension

Version
Number

Multiple
Files
Allowed
(commas)

AP
C
CO
D
DE
E
EX
J *
ME
P
PRO
PU

YES
NO
YES
YES
YES
NO
YES
NO
YES
NO
YES
NO
NO
YES
NO
YES
NO

YES
NO
YES
YES
YES
NO
YES
YES
YES
YES
YES
YES
NO
YES
YES
YES
NO

Q
R
S
UN
US

Version
Default
Allowed
(latest)

YES
YES
YES
YES
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
NO

Ext.
Default
(if any)

.PRF

.PRF
.PRF
.PRF
.sET

.SET

* Includes all justify commands
The recommended UIC codes are (See Figure 3-1):

Function

Group

The following UICs are for DEC use and are not assigned to a Typeset-II user:

User
1,1-377 except 1.10 which is assigned to the
System Manager
h. 2,1-377
c. 11-17,1-377
a.

System Manager

Newspaper File
Pools

300-367

1-377

Common Pool

370-377

1-377

Controllers

3-7

1-377

Supervisors

20-277

1-377

Operators

20-277

10-377

A password is assigned to each authorized user. The
password consists of from one to five alphanumeric
characters assigned to each UIC. Passwords are nonprinting, that is, they do not appear on the Teletype,
DECwriter, or VT20 terminal during log-in.
Passwords are not nonrially required at the MCR
console (Teletype or DECwriter).

3-3

SYSTEM MANAGER

1,10

CONTROLLER

3,1
3,2
3,3
.3,4

4,1
4,2
4,3

'5,1
5,2
'5,3

OPERATORS

[20,10]- [20,30]

[21,10]-[21,30]

OPERATORS OPERATORS
[30~oH3O,3q [31,10]-[31,30]

OPERATORS

[32,10]-[32,30] [33,10]-[33,30][34,10]-[34,30]

OPERATORS

[40,10]-[40,30]

OPERATORS

[41,10]-[41,30] [42,10]-[42,30]

COMMON POOL

[370,1]-[370,2]

11-2

Figure 3-1 Example Of File Access Hierarchy

3.3 FILE FLOW
Each file that is input to the system is assigned a file
name, extension, and group-and-user number and
may produce (depending on data flow options) up to
three files (Figure 3-2) as follows:
1.

An unjustified proof file which can be called
to the VT20 terminal for editing. The version number for this file is 1.

A justified proof file that can be edited.
This file is assigned version number 2. The
line printer will automatically print a copy
of this file if data flow defaults require it to
be printed.

A file with a .SET extension in machine
code that can be output to the Photocomp
machine. This file is assigned version 1.

When the operator cans a file to the VT20 to be
edited, the system automatically creates a new version
of the file. As an example, if a file called
JOE.MON;3 is edited, a new file called JOE.MON;4
is created. After the VT20 operator completes his
editing operations both the edited version
(JOE.MON;4) and the old file (JOE.MON;3) are retained.

At the end of the edit cycle the operator would normally justify the edited version of the story and two
more files are generated in the process. As shown in
file flow (Figure 3-3), the justify command produces
a justified proof file called JOE.MON;5 and a new
JOE. SET; 1 file. The old JOE.SET; 1 file is deleted. A
copy of JOE.MON;5 is printed on the line printer if
the data flow defaults require it to be printed.

3-4

3.4.1 Routing Files Using Justify Command
The justify commands request that a file be assigned
to the JAH queue for processing by the JAH Spooler.
Different versions of this command determine the
subsequent data flow for the file that has been justified. The JAH commands. switches. and subsequent
data flow are described in Paragraph 4.4.3.

3.4 FILE FLOW OPTIONS
Data flow through the Typeset-II system is customized and controlled by the user to select one of several paths through the system (Figure 3-2) with a
minimum of commands. For example the command
to have a file processed by J and H may provide options to specify the file to be output to a photocomp
machine. paper ta'Pe punch. or line printer. The .SET
file will always be produced and may optionally be
queued to any output device. or not at all. A file may
also be marked for deletion after successful output.

PR-SPOOLER

STORY

~ NO FURTHER ACTION

FILE

1Iii-~--1. TO "LP" QUEUE

\0._ _ _ _ _. . .

TO J & H

NO FURTHER ACTION
TO "PC" QUEUE (ALLOTER)
SET STORY
TO "PP" QUEUE

/
/

EITHER OR
BOTH MAY

BE GENE,.R_A_T_E_D_ _ _ _•

J&H

TO "CAD" QUEUE
NO FURTHER ACTION

JUSTIFIED
PROOF
TO "LP" QUEUE

TOJ&H
EDITED
STORY
TO LP FOR PROOF

TO PC QUEUE (ALLOTER)
SET
STORY

~-..... TO SPECIFIED PCR

TO PP QUEUE (OR SPECIFIED PPR)
11-2461

Figure 3-2 File Flow Options

3-5

PAPER
-- .. TAPE

PUNCH

/
/

,,
CP-1449

Figure 3-3 File Flow Options

where /PF is the switch that will queue the input m
to the line printer queue and a line printer copy wi!
be printed of FILE. These switches are appended tl
the filename on the paper tape (Appendix I) whel
the tape is input to the system. The switches used fa
data flow controlled by the input tape are as follows:

3.4.2 Routing Files From Input Tapes
Switches may be appended to a filename when a file
is input to the system to specify the route the file will
take and the processing required. For example:
FILEIPF

3-6

-----

. -=-..-=---=
..

-~----.--------.~.=

.. - - - - - - - - -

-~.~

Switch

3.4.3 System Flow By Default Standards
Copy preparation and processing is greatly speeded
through use of system default standards. System flow
options are predetermined by system defaults customized for each user. One user may desire that a line
printer proof be generated for all copy input to the
system while another user desires proof copy on only
selected inputs.

Operation

IJC

Queue to J and H and queue the
.SET and proof files to CLASS AD
as an insert.

IJH

Queue FILE to J and H but do not
queue resulting .SET or proof file .
.SET and proof are stored on the
disk until the user types a command
to process the file.

IJP

Queue to J and H and send the
proof file to the line printer.

IJS

Queue FILE to J and H and send
the .sET file to PC (photocomp)
queue. Do not print a proof copy on
the line printer.

IJT

Queue FILE to J and H and queue
the .sET file to PP (paper tape
punch) queue. Do not print a proof
copy on the line printer.

INO

Queue nowhere. This overrides the
system default so that the file will
not follow the file flow which has
been established for the system when
routing is. not specified by switches.

IPF

Print a copy of the input file on the
line printer.

IPR:x

Assigns a priority for the operation
where x is a number from 0 to 255.
If the number is issued from the
VT20. it is a decimal number. otherwise. it is an octal number unless a
period (.) is included.

Different input devices may have different system
flow default parameters. Reader 0 input may be sent
to the JAH queue and then automatically on to the
line printer where a proof is generated, while Reader
I input may be stored on the system disk with no
further processing. The system defaults may be overridden by switches which are appended to the filename when the paper tape is perforated.

3-7

CHAPTER 4
QUEUE MANAGER

4.1
QUEUE MANAGER
Typeset-II incorporates a very sophisticated Queue
Manager program. As simultaneous inputs are received by the system and stored on disk files. the
Queue Manager automatically assigns them to a dynamic queue according to the action requested. If, for
example. the copy is to be justified, it will queue the
file to the JAH queue for processing.

A list of queues is given in Table 4-1 and illustrated
in Figure 4-1. There are also commands that combine
a queue entry with instructions to the associated task
to make further queue entries. This allows the user to
control file flow. For example. the user may put a
file in the .JAH queue and with the same command
string he may direct this file to an on-line photocomp
machine after JAH has completed processing the file.

Similiar queues exist for proofing copies on the line
printer and outputting on the photocomp machines or
punches. Since operators are not required to wait for
completion of a task before they begin another, a
true multi-user environment is created. Each user is
free to work at a different pace as processing occurs
independently.

Queues may be connected to more then one spooler.
For example. the PP queue is connected to PPOSP
and PPISP so that files in the PP queue may be
punched on PPO or PP1. In fact, they will be
punched on the first punch that becomes available. If
a file must be directed to a particular unit. a special
queue command (Paragraph 4.4.5.1) is used.

The Queue Manager also maintains a file which has
a list of tasks assigned to each queue and the status
of that task. In the event of a system crash the
queues are rebuilt automatically when the system is
restarted.

Q-PPO

4.2 QUEUES
All Typeset-II operations are controlled by the
Queue Manager on a priority basis. Normally, a user
would not specify a priority and the system would
process items in a queue on a first-in first-out basis.
To allow the user to send important stories through
the system quickly. each entry on a queue has an associated priority. A priority is a number in the range
I to 255. where the queue entries with the highest
priority will be done first. Thus. if we have 2 proofs
to be printed on the line printer, one with a priority
of 10. and one with 20. the proof having priority 20
will be printed first even if it was placed in the queue
later. If no priority is assigned. the system assigns a
priority 10 automatically.

PUN

PPO
QUE

PPI
QUE

PPOSP

PPISP

PP
QUE

SET

LPC
QUE

PCOSP

CP-0849

Figure 4-1 Queue Manager, Queues. and Spoolers

4-1

When files are directed to a photocomp machine a
special routine, the Allotter, controls the PC queue in
accordance with the priority assigned to the file and
current machine setups. The ABotter will determine
the machine setup and film size required to process
the file and direct the file to a unit that meets these
requirements.

command may be used to output a file, process files
through J and H. or control the operation of the
queues themselves. These commands may be given
from the VT20 or MCR terminal. The VT20 must be
in command mode (©) and the MCR terminal must
be in OPR mode.
Following are some general rules on file names for
queue entry commands-. The general form for these
commands is:

Table 4-1
List of Typeset-II Queues aDd Spoolers

©COMMAND FILES
Queue Name
Mnemonic

Equipment

Spooler

PRx
PPx
PCx
LPx *
JAH

Papertape Reader
Papertape Punch
Photocomp Machine
Line Printer
J and H Joblist

PRxSP
PPxSP
PCxSP
LPxSP
JAH

where COMMAND is the function desired and
FILES is the group of stories to which that function
is· applied. In the most general case, FILES consists
of the string:
DEVICE:[VIC]FILENAME.TYPE:
VERSION ISWITCHES,etc.
In order to save keystrokes, the user would not normally type in the complete string, but would take advantage of the system defaults. In particular:

where:
x = Unit number assigned to the equipment
associated with the queue and spooler.

DEVICE:

Unless there were some very unusual circumstances, the device is
always the default device and does
not have to be input.

[VIC]

If the story is located in the user's
area, this can be omitted. It must
be used to access pool files.

FILENAME

If the name of the story was the
same as the story last queued or
edited, this can be omitted. For
example, if the user has just
printed a story with the command:

* If system has only one LP, the line printer queue is
named LP.
4.3 USING QUEUE COMMANDS
The MCR terminal must be in the OPR mode to use
any of the Queue commands. To get in the OPR
mode the user must type:
MCR>OPR
and the terminal responds with:
*READY*

©P STORY<CR>

At this time, the user can type in Queue commands.
To return to the MCR mode, the user must type
<CTRLlZ> or KIL<CR>. To use Queue commands at the VT20, the terminal must be in command mode (©).

he may decide that it can be justified. In such a case it is only necessary ,to type:
©J<CR>
.TYPE

4.4 QUEUE ENTRY COMMANDS
These commands are used to enter a file into a queue
for processing bytbe spooler associated with that
queue (Table 4-1 and Figure 4-1). The queue entry

Most often, the default for each
command is correct and this can
be left out. The default is specified
for each command.

4-2

-.---.----------.-~.~=.==~-----~------

----~-----------=-

;VERSION

ISWITCHES

Most often the user wishes to operate on the latest version and this
can be omitted.

Tbe Print command -is of the form:

The important thing to bear in
mind here is that the switches on
the first file carry over to every
file in the list. For example:

and causes the file named In the command to be
printed out on the line printer.

©P FILE<CR>

Example
©P FILEA < CR >

©PU STORYIIDE,STORY2
<CR>

prints FILEA at the line printer. The Print command
may also be of the form:

punches and deletes both STORYI
and STORY2.

©P FILEI,FILE2,FILE3<CR>
,ETC.

This is only needed if more than
one story is desired. It should be
remembered that the last filename
in the list determines the new default filename.

to print more than one file with one command string.
A switch ISP:x (x is a number L 2, or, 3) may be
added to the Print command string to select spacing
of line printer copy.

4.4.1 Using Command
This command is not. strictly speaking, a queue entry
command, but is very useful in conjunction with
them. It is used to modify the default extension for
the print and justify commands. The format is:

Example
©P FILEA/SP:2<CR>
causes the line printer copy of FILEA to be double
spaced.

©US .EXT<CR>
For example, if a newspaper uses the day of the
week as the normal story extension, after logging in
on MONDAY the user types:

4.4.2.2 Punch Command
The PUnch command is of the form:
©PU FILE<CR>

©US .MON <CR>
and causes the file named in the command to be
punched on paper tape.

To then print a story he types:
©P STORY<CR>

Example

rather than:

©PU FILEA < CR >

©P STORY.MON<CR>
This command causes FILEA to be punched on paper tape. The PUnch command may also be of the
form:

4.4.2
Output Commands
This group of commands enters a file into a queue
for one of the ouput devices.

©PU FILEI,FILE2,FILE3<CR>

4.4.2.1 Print Command
The default file type is .PRF and can be changed by
the USing command.

to punch more than one file with one command
string. The default file type is .SET.

4-3

4.4.2.3 Set Command
The SET command is of the general form:

4.4.3.1 Justify Command
The Justify command causes a file to be processed by
J and H. generates a proof file and/or .SET file, and
routes the file. after processing, as determined by system defaults for a particular terminal.

©S FILE<CR>
and assigns the file named in the command to the PC
queue for output on one of the on-line photocomp
machines.

Example
©J FILEA<CR>

Example
causes FILEA to be processed by J and H and routed
afterward according to system defaults.

©S FILEA<CR>
causes FILEA to be output on the on-line photocomp
machine. The SET command may also be of the
form:

NOTE
The IPR and IDE switches for the output
command also apply to the Justify commands. The IDE switch, when applied to a
justify command, does not mean that J and
H is to delete its input file, but rather, that
it is to set the IDE switch if any output
files are queued.

©S FILEl.FILE2,FILE3<CR>
to output more than one file to a photocomp machine using one command string. The default file
type is .SET.

Other forms of the Justify command and the resulting
file flow are discussed in the following paragraphs.

4.4.2.4 Output Command Switches
The IPR (priority) and IDE (delete) switches may be
appended to the filename in any of the output command strings. The /PR switch is described in Paragraph 4.5. The IDE switch causes the file to be deleted from the system after it is processed by the
spooler indicated in the command.

4.4.3.2 JH Command
The JH command is of the form:
©JH FILE<CR>
and causes the file named in the command to be processed by J and H. A proof file and .SET Gustified
file) are generated. Neither of the files are queued to
an output device.

Example
©PU FILEA/DE<CR>
causes FILEA to be deleted from the system after it
has been punched on paper tape.

Example
©JH FILEA<CR>

4.4.3 Justification Commands
The default file type is .PRF and can be changed
with the USing command.

assigns FILEA to the JAH queue where it is processed. Two files, a proof file and a set file. are generated.

The Justify commands, as a group, cause a file to be
processed by J and H. The form of the command determines the routing of files, and whether a proof
copy or a line printer copy is generated. All of these
commands allow more than one file to be specified
(e.g., ©Jx Filel, File2, File3<CR».

4.4.3.3 JS Command
The JS command is of the form:
©JS FILE<CR>
and causes the file named in the command to be processed by J and H. Only a .SET file is generated and
the .SET file is assigned to the PC queue for processing by the photocomp machine.

where x = the second letter of the command name,
if any.

Example

sent to the line printer, but the SET file is not
queued to CLASS AD as an insert.

©JS FILEA<CR>
The ICH and INP switches may be appended to the
JC command string. The ICH switch causes a file to
be sent to CLASS AD as a change to existing ads,
rather than as an insert to the CLASS AD data base.

causes FILEA to be processed by J and H and outputs FILEA.SET to the on-line photocomp machine.
If an error occurs during the processing of this file. a
proof copy is generated and printed at the line
printer. and the .SET file is not queued to the photocomp unless the 10K switch was specified (Paragraph
4.4.4).

Example
©JC FILE/CH <CR>

4.4.3.4 JT Command
The JT command is of the form:

This example is sent to CLASS AD to replace the
existing ads contained in FILE, in the CLASS AD
data base.

©JT FILE<CR>
When the INP switch is appended to the JC command string, no proof file is generated.

and causes the file named in the command to be processed by J and H. which produces a .sET file only.
The .SET file is output to the paper tape punch.

Example

©JC FILE/NP<CR>

©JT FILEA<CR>

This command causes the file to be processed by J
and H and the .SET file queued to CLASS AD as an
insertion. No proof file is generated and therefore,
the text of the ad is not stored in the CLASS AD
data base.

causes FILEA to be processed by JAH to generate a
.SET file. FILEA.SET is output on the paper tape
punch. If an error occurs during the processing of this
file. a proof file is generated and printed at the line
printer. and the .SET file is not queued to the punch
unless the 10K switch was specified (Paragraph
4.4.4).

4.4.3.6 JP Command
The JP command is of the form:

4.4.3.5 JC Command
The JC command is of the form:

©JP FILE<CR>
and causes the file named in the command to be processed by J and H. A .SET and proof file are generated and the proof file is output on the line printer.

©JC FILE<CR>
and causes the file named in the command to be processed by J and H and generates a .SET and a proof
file. Both files are queued to the CLASS AD data
base.

Example
©JP FILEA<CR>

Example

causes FILEA to be processed by J and H. A proof
file and a .SET are generated and the proof file is
output to the line printer.

©JC FILEA<CR>
causes FILEA to be processed by J and H and generates a proof file and a .SET file. These files are
queued to the CLASS AD data base. If an error occurs during processing of the file, the proof copy is

4.4.4 Justify Control Switches
The Justification commands in Paragraph 4.4.3 may
be further controlled by appending switches to the
filename in any of the Justify commands. A switch is

4-5

used to modify a command and to change the file
flow. The switches which may be used with the Justify commands are as follows:

Example

Switch

Meaning

assigns FILEA to the PPO (paper tape punch unit 0'
queue. If the unit number is not specified, the file i:
punched on the first free punch.

IDE

Delete the output file .SET or the
proof file after the spooler has
completed the output operation.

IHP

Generate a proof file but do not
queue the proof file. hold the file
in storage.

©Q PPO = FILEA<CR>

To output a file to a specific on-line photocomp rna
chine, the command:
©Q PCx = FILE<CR>
where:

IHS

Do not queue the .SET file. hold
the file in storage.

INP

Do not generate a proof file.

10K

Send the file to the specified
spooler even if there have been
warning level errors generated by
that J and H.

IPF

Generate a proof file and queue it
to the line printer.

IPR:x

Assign a priority x from I to 255.

A command using a swit<:h is of the form:

x is the unit number of the photocomp
is used. If the unit number is not specified, the AI,
lotter determines the required machine setup for th(
file named in the command and routes the file to th(
correct machine.

Queue Activation
The command:

4.4.5.2

©Q QUEUENAME/AC<CR>
activates the queue named in the command.

©JP FILE/NP<CR>
Example
The INP switch prevents a proof copy from being
produced when FILE is processed by J and H.
4.4.5
Queue Control Commands
The queue control commands provide the system
manager with the ability to assign files to a particular
queue and force the processing to be done on a particular unit. Only the system manager may use these
commands.
4.4.5. t

Queue Output Commands
The Queue command is of the form:
©Q QUEUENAME = FILE<CR>
and assigns the file named in the command to the
queue also named in the command, for processing by
the spooler associated with that queue.

©Q LP/AC<CR>
activates the LP queue and the line printer spoolel
starts to print files assigned to that queue.

Queue Deadivation
The command:

4.4.5.3

©Q QUEUENAME/-AC<CR>
deactivates a queue, an~ the spooler associated witt
that queue stops pr~ce~slng files upon completion 01
the item currently in progress. However, files may b(
assigned to the queue even if it is deactivated. Thf
files assigned to the queue are processed by the ap·
propriate spooler when the queue is reactivated.

Example

restriction is overridden for stories with a priority
greater than 128.

©Q LP/-AC<CR>
Example
deactivates the LP (line printer) queue and the line
printer spooler stops printing copies of files assigned
to the queue.

©S STORY IPR: 128<CR>
causes the machine to stop or the film to be cut (depending on system defaults) when STORY is output
to the photocomp machine.

4.4.5.4
Queue Manager Exit
The command:

4.5.1
Modifying File Priority
The priority of a file that is assigned to a queue may
be modified by the command:

©Q/EX<CR>
causes the Queue Manager to close out all queues
and shut down the Queue Manager. This command is
only used in the system shutdown procedure.

©Q QUEUENAME/MO:x/PR:y<CR>
where:

4.5
ASSIGNING PRIORITY
The Queue Manager operates on a priority basis so
each file is assigned a priority by the user or automatically by the system if the user does not assign
one. A priority from I to 255 may be assigned to the
processing of a file by using the IPR switch When a
command is given or the file is input to the system.
The intention of this command is to allow hot stories to be processed quickly.

x is the item number of the file
y is the new priority
Example
©Q LP/MO:IO/PR:100<CR>
changes the priority of item 10 on the LP Queue to
100. and it is printed before all items with a priority
less than 100.

Example

4.5.2
Removing an Item from a Queue
An item that has been assigned to a queue for processing may be removed from that queue using the
command:

©P FILE/PR: 100<CR>
This example assigns a priority of 100 to FILE when
it is dispatched to the LP queue; it is printed before
all other files with a lower priority.

©Q QUEUENAME/KI:x<CR>
If no priority is assigned. the system automatically assigns a priority of 10 to the file.

where:

Priority serves a special function in connection with
files for output to photocomp machines. Normally.
the spooler sends a cut-film or stop command to a
photocomp machine after a given length of film (as
desired by the user). However, if any file has been
given a priority greater than 128, the spooler will output the cut film or stop immediately. Further, when
the Allotter is included in the system, priority allocation is useful. Stories will normally be output to a
machine loaded with the minimum correct film width,

x is the item number of the file to be removed
If the item is currently being processed. it will be
aborted as soon as the command is input. Item numbers are assigned by the system when a file is assigned to a queue. The item number of a file assigned to a queue may be determined by using the
story status commands (Paragraph 4.6.2). The item
number of the last item queued is displayed on the
VT20 screen.

4-7

Example

©Q LP/KI:32<CR>

QUEUE: LP TO BE PROCESSED: 10 -- ACTIVE
QUEUE: JAH TO BE PROCESSED: 3 -- ACTIVE
QUEUE: PP TO BE PROCESSED: 1 -- INACTIVE
QUEUE: PPO TO BE PROCESSED: 0 -- INACTIVE
QUEUE: PPI TO BE PROCESSED: 0 -- INACTIVE
QUEUE: PC TO BE PROCESSED: 5 -- ACTIVE
QUEUE: PCO TO BE PROCESSED: 0 -- INACTIVE
QUEUE: PCI TO BE PROCESSED: 0 -- INACTIVE
QUEUE: CAD TO BE PROCESSED: 0 -- INACTIVE
QUEUE: RUN TO BE PROCESSED: 0 -- INACTIVE

will remove item number 32 from the LP (line
printer) queue and halt the printing if currently in
progress.

4.6

SYSTEM STATUS

4.6.1 System Status Reports
Any user can determine the status of the system or
the status of any stories in the system by typing the
appropriate Queue command at the MCR terminal or
at the VT20. Status listings may be displayed at the
terminal or printed on the line printer. These commands are designed to allow the user to select just
the portion of the information desired by stringing
the appropriate switches together.

4.6.1.3 Spooler Status
The command:
©Q/SP<CR>

lists at the termmal names of all the spoolers and
their status: waiting. not loaded. or processing an
item.

4.6.1.1 Abort Status
All system aborts will cause a message to be printed
at the MCR terminal when the abort takes place. The
item number that produced the error and the spooler
which was processing the file when the abort occured
is given. However. to obtain a listing of all aborts
that occur during the day use the abort command:

Example
SPOOLER: LPOSP
SPOOLER: JAH
SPOOLER: PPOSP
SPOOLER: PPISP
SPOOLER: PCOSP
SPOOLER: PCISP
SPOOLER: CADSPL

©Q/AB<CR>

to list at the terminal all abort reports.
Example

-- WAITING
-- PROCESSING ITEM # 10
-- WAITING
-- WAITING
-- WAITING
-- PROCESSING ITEM #6
-- NOT LOADED

TASK VT2MON ABORT CODE = 35. PC =
042570 PS = 174000 SP = 000332 RO = 000015
RI = 041560 R2 = 002340 R3 = 000001 R4 =
000000 R5 =·000000

4.6.1.4 Active Queue Listing
The command:

TASK VT3LOG ABORT CODE = 35. PC =
001200 PS = 174000 SP = 000766 RO = 000023
RI = 005230 R2 = 000000 R3 = 000001 R4 =
005416 R5 = 000000

lists at the terminal. queue sizes. items processed. and
the number of errors generated.

©Q/SY<CR>

Example
QSIZE = 3/85/500.
ITEM = 5151799.
ERROR = 0.0

4.6.1.2 Queue Status
The command:
©Q/QU<CR>

Queue size consists of 3 numbers; the first number is
the current number of unprocessed items on all
queues. the second number is the maximum number
of unprocessed items on all queues during the day.

lists at the terminal the queues. the number of items
to be processed by each queue. and whether they are
active or inactive.

4-8

and the third number is the maximum number of unprocessed items that can be on all queues before priority allocation is lost. Item consists of 2 numbers:
the first number indicates the current highest item
number and the second number indicates the highest
item number that can be reached before the system
pauses to extend the file.

JAH #377. 10. DPO:[100.100]LST.VTI: I (VT2MON)
DONE

Error is the number of parity errors.

Example
JAH #365. 10. DPO:[100.100]LST.EDI: I (VT2MON)
ERROR = QI36

4.6.2
Story Status
The normal default is to list. in brief format the stories the user requested, from this terminal, in the last
hour. For this information, use the command:

4.6.2.2

The command:

#493.
10.
DPO:[200.216]CONTENTS.SET: I
(VT2MON) DONE 0

lists at the terminal all items the user requested. in
the last hour. that are not completed (waiting).

#494.
10.
DPO:[200.216]CHANGE.SET: I
(VT2MON) DONE 10

JAH

Select by Story Status

If aitin~

<DQ<CR>
Example PC

#388. 10. DPO:[100.100]LST.PTI:3 (VT2MON)
DONE 0

Example
LP

#41. 10. DPO:[200.200]ROY.PRF: I (VTOMON)

#499. 10. DPO:[200.200]ROY.PRF: I
(VT2MON) DONE 0

#42. 10. DPO:[200.200]ROY2.PRF:2 (VTOMON)

# 500. 10. DPO:[200.200]ROY2.PRF: I
(VT2MON)

Error

The command:
To override anv of the default conditions. use the select-by-story-name option (Paragraph 4.6.2.1) or the
select-by-story-status option (Paragraph 4.6.2.2).

lists at the terminal all items the user requested. In
the last hour. that resulted in an error.

4.6.2.1 Select by Story N arne
The status of particular stories in one user area. or a
group of user areas. can also be selected. To use this
option. simply put in the portions of the story name
desired after the Queue command.

Example
JAH

#3.
10.
DPO:[210.221]LABEL.PRF:5
(VT3MON) ERROR = A3

JAH

#5.
10.
DPO:[210.221 ]LABEL.PRF:6
(VT3MON) ERROR = A3

Example
<DQ[1 00.100] LST
This command will list stories queued from area
100.100 with the name LST, in the last hour. from
the user's terminal.

The error can be interpreted by referencing the
Typeset-II Error Messages manual.

4-9

Example

Done

The command:

©Q/I::20

lists at the terminal the status of all item numbers 20.
or less. that the user requested.

©Q/D<CR>

lists at the terminal all items the user requested. in
the last hour. that have been completed.

If both item numbers are left out. the item numbers
last input are used.

Example
Example

#493. 10. DPO:(200.216]CONTENTS.SET; 1
(VT2MON) DONE 0

©Q/I

#494. 10. DPOt200.216]CHANGE.SET; 1
(VT2MON) DONE 10

lists at the terminal the status of all item numbers
specified in the last II that the user requested.

4.6.2.4 Select by Queue Name
The command:

4.6.2.3 Select by Item Number
The command:

©Q/Q:QUEUENAME<CR>

©Q/I:X:Y <CR>

lists at the terminal the status of all item numbers. in
the range X to Y. that the user requested.

lists at the terminal the status of the items on the
queue named in the command. requested by the user
in the last hour.

Example

©Q/I:I0:16<CR>

©Q/Q:LP<CR>

lists at the terminal the status of all item numbers. in
the range 10 through 16. 'that the user requested.

lists at the terminal items that are in the line printer
queue as shown below.

If the the second item number is left out only item X
will list.

Example

Example
©Q/I:IO<CR>

# 5. 10. DPO:(200.200]ROY l.PRF; 1 (VT3MON)
DONE 0

#7. 10. DPO:[200.200]ROY2.PRF; I (VT3MON)
DONE 0

#8. 10. DPO:[200.200]ROYl.PRF; I (VT3MON)
DONE 0

lists at the terminal the status of item number 10.
If the second item number is left out, but the : follows the first item number, from Item X to the end
of the file will list.

4.6.2.5 Select Expanded Listing Format

Example

Time Information

©Q/I:15:

The command:
lists at the terminal the status of all item numbers. 15
or greater. that the user requested.

©Q/ST<CR>

lists at the terminal all items the user requested, in
the last hour. with time information.

If the first item number is left out. item numbers 1 to
Yare listed,
4-10

Example

4.6.2.7 Select All Time
The command:

LP #88. 10. DPO:[40.l1LENGTH.FIT;2 (VTOMON)
DONE
3-JUN-74 14:07:46.6 SENT: 14:07:46.6 TOOK:
00:00:35.1

lists at the terminal all items requested by the user.

Switch Options

Example

The command:

JAH

#3.
10.
DPD:[330.101VT9999.EDI; I
(VT2MON) ERROR = A36

JAH

#37.
10.
DPO:[330.101STRY98.VTI: I
(VT2MON) DONE

#388.
10.
(VT2MON)

©Q/B<CR>

©Q/SW<CR>

lists at the terminal all items the user requested, in
the last hour. with the switch options used.
Example
PC #494. 10. DPO:[200.2161CHANGE.SET; 1
(VT2MON) DONE 10 IDE

4.6.2.8 Select Last Item
The command:

LP #499. 10. DPO:[200.2001ROY.PRF; 1 (VT2MON)
DONE 0 ISP:2

©Q/L<CR>
lists the last items specified in the previous queue
output command.

JAH
# 500. 10. DPO:[200.2001ROY2.PRF; 1
(VT2MON) DONE /lS/NP

Example

4.6.2.6 Select All Tenninals
The command:

©Q/A<CR>

#26. 10. DPO:[210,2211VT200PB.PRF;2
(VT3MON) DONE 0

In this example. Item 26 was the last thing queued
from this terminal.

lists at the terminal all items queued in the last hour.
Example
LP

DPO:[330. 101STORY2.PTI;3

4.6.2.9 Select Line Printer For Listing
The command:

#465. 10. DPO:[200,2031BASEAD.PRF;5
(VT4MON) DONE 0

©Q/LP

CAD#466. 10. DPO:[320.l1TUEJUN04. (VT3MON)
DONE

performs the equivalent of:
©Q/ST/AB

RUN#467. 10. DPO:[320.l]. ( ... OPR) DONE
except that the listing is done on the line printer.
CAD#468. 10. DPO:[320.l1TUEJUN04. (VT4MON)
DONE

4.6.2.10 Select Last Listing Fonnat
The command:

CAD#470. 10. DPO:[320.l1TUEJUN04E. (VTIMON)
DONE
LP

©Q/F<CR>

uses the same switch format as the last queue list
command.

#472.
10.
DPO:[320.11LOGCAD.PRF; 1
(VTOMON) DONE 0

4-11

4.6.3 Combined Queue Listing Commands
The queue listing commands may be combined to
cause several operations, to be initiated when only
one command string is typed,

LP #4. 10. DPQ:{212.4]OUTSP.LST;2 ( ... OPR)
DONE O'
4-AUG-74 21:18:00.4 SENT: 21:18:00.5 TOOK:
00:05:44.8

4.7

Example
©Q/QU/E<CR>
will list at the terminal all queue names and all items
requested by the user, in the last hour, that resulted
in an error.
Example
©Q/LP/A/B/SW<CR>
prints a complete listing of all queue activity for the
day at the line printer. This command is normally
used to get a complete list of the day's activity at the
end of the day.
Example
©Q/D/ST<CR>
supplies timing information for all items on' jobs that
were done.
One of the most useful forms of the Queue command
and the one used by most operators to determine the
status of work done at the system terminal is:
©Q/ST I A/B<cr>

THE ALLOTTER

The Allotter assigns files to the correct photocomp
machine when they have been assigned to the PC
queue by the Set command. Each file in the system is
identified by a filenarile, extension, version number,
and UIC. Appended to this information is a machine
number, setup number, and column width (film size).
Machine number refers to a partK:1iI1ar type of machine; each type is assigaed a different number. The
setup number refers to a particular machine setup required to process a file (font. typeface, etc.). When a
file is assigned to the PC queue for output by the
photocomp machine, the Allotter looks at this data,
compares it with the current machine status, and
sends it the machine that has the correct setup to
process this file. This eliminates the aeed for an operator to check the setup of each machine and to assign
each file to a particular machine.
However, if a file inust be output to a particular photocomp machine, this can be' done using the queue
commands (see Paragraph 4.4.5),

4.7.1
Machine Status Update
The system manager m.ay change the setup of photocomp machines as production requirements change.
The form of the command used to change a machine
setup is:

This command lists at the terminal all items done at
all terminals during the day along with the time information.

©CS PCx/SU:y/FS:z/FO or I-FO<CR>
where:

Example
PCx
PCO # l. 255. 0:[2,3]PCSTOP.SET; I (SYS) DONE
4-AUG-74 20: 12:55.8
LP
#2.
IO. DPO:[200,2]OUTSPOI6.PRF; 1
(VT2MON) DONE 0
4-AUG-74 21:10:15.0 SENT: 21:10:15.1 TOOK:
00:00:09.7
LP #3. 10. DPO:[212,4]OUTSPA.LST;2 (VT2MON)
DONE 0
4-AUG-74 21:11:11.3 SENT: 21:11:11.3 TOOK:
00:01:21.2

- 4-12

specifies the pbotocomp machine's assigned unit number.

ISU:y specifies that a new setup is to be
mounted and y is an octal number specifying the se~up.
IFS:z specifies a film size in inches and 114
inches as follows:
8: = 8 inches
8:2 = 8 112 inches

IFO

I -FO

activates film override and allows output
on any available size of film. For example if the stories to typeset require 3.7
inch column width and all the inachines
in the system contain 8 inch film IFO
will allow these files to be output on a
machine with 8.inch film.

will check the PC queue or queues and list at the
terminal a summary of the number of items awaiting
output by machine number, the machine' setup number and film size.
Example
OUTPUT STATUS [ALL] ON 9-JUL-74 AT
16:28:40
M/C TYPE:FILM-SIZES:TXT
3.75
8
SETUP ACTV HOLD M/C# ACTV HOLD M/C#

deactivates film override and allows output only on specified size of film. For
example. if a story requires 3.75 inch
film and ~onl:! of the machines have this
size these files will not be typeset.

1
M/C TYPE:-

FILM-SIZES:-

PAC
4
8.50
SETUP ACTV HOLD M/C# ACrV HOLD M/C#
I 12
2
0
0
I
3
2

Ail switches are optional and their omission indicates
no change in machine setup.
©CS CIISU:2/FS:8/FO<CR>

Following is an explaination of the output.
This example calls for machine setup number 2 on
photocomp machine number one. The film size is
changed to 8 inches and the film override is activated.

M/C TYPE:-

FILM-SIZES:#1
#2
#2
SETUP ACTV HOLD M/C# ACTV HOLD M/C#
#3 #4
#5
#6
#4
#5
#6

4.7.2 Machine Status
Occasionally the user may wish to check the status of
the photocomp machines to determine their setup,
film size, etc.

# I:
#2:
#3:

The command:

#4:

©Q/OS/Q:PCx<CR>

#5:

where:

#6:

x is the unit number.
(Omission of IQ:PCx implies all queues.)

4-13

The type of machines is printed here, i.e.
TXT, 191, or CRT.
The film sizes for machines of this type
are printed here.
The machine setup number is printed
here.
The number of items available for processing are listed here.
The number of items on a queue that is
not active are listed here.
The number of the machine that has the
setup on it is listed here.

CHAPTER 5
SYSTEM OPERATION

5.1 MONITOR CONSOLE ROUTINE
This chapter describes the MCR commands used by
the operator to communicate with the Typeset-II system via the MCR console. The MCR (Monitor Console Routine) is the interface for the RSX-ll D system. MCR input is initiated by typing <CTRLlC>.
The system responds by printing the characters
MCR> on the console indicating that it will now accept an MCR command.

5.2.2 Dismount Command
The Dismount command causes the device named in
the command to become unavailable for storage and
retrieval of data.
Format
MCR>DMO DEVICE:<CR>
Example

5.2 RSX-11D COMMANDS
Command names are three characters in length. The
MCR accepts the three characters and then searches
for a blank. Therefore. embedded blanks are not allowed in a command name. If a command is entered
incorrectly. a message will be printed at the terminal.

MCR>DMO DP:<CR>

5.2.3 Enter Time Command
The enter TIMe command is used to enter the correct
time into the system.

NOTE
Only the RSX-llD commands used frequently by the user are listed here. The
RSX-11D Operator's Procedures Manual
(DEC-ll-OXDOA-B-D) contains a complete list of RSX-llD commands.

Format
MCR>TIM TIME DATE<CR>
where:
Time is entered as HH:MM:SS
Date is entered as MO:DA:YR

5.2.1 Mount Command
The MOUnt command causes the device named in
the command to become available for storage and retrieval of data.

Example
MCR>TIM 14:55:05 liI8!74<CR>

Format

5.2.4 Active Task List Command
The ACTive task list command prints statistical information about each active task. DEC programmers or
Field Service personnel may ask the user to generate
this listing for their evaluation; otherwise. it is unlikely that the user will need this command.

MCR>MOU DEVICE:<CR>
Example
MCR>MOU DP:<CR>

5-1

Format

5.2.8 Load Command
The LOAd command allows the operator to specify
that an indicated 110 device handler be made resident in memory and ready for service. 110 requests
to a device are not honored unless the requested device handler is resident.

MCR>ACT<CR>
Example
DP .... STS WO 250 000 000 020 003 000 064600
000000 000000
RECJS 174000 000276 002676 000010 000000
00000 I 002200 150000
000262
VT.... STS WO 250 000 000 020 007 000 264000
000000 000000
RECJS 174000 005742 0004]4 000017 000000
060160 175640 123264
000414

Format
MCR>LOA DEVICE<CR>
Example
MCR>LOA LP<CR>

5.3 TYPESET-II UTILITY COMMANDS
To use the utility commands. the system console must
be in OPR mode. To get into OPR mode from MCR
mode. the user should type OPR<CR>. The terminal will print out:

5.2.5 Request Command
The REQuest command allows the operator to request the immediate execution of a task.

*READY*

Format
MCR>REQ TASKNAME<CR>

The user can now type any of the utility commands
listed in the following paragraphs.

Example

NOTE
To exit the OPR mode, at any time, type
KIL<CR>.

MCR>REQ CLASAD<CR>

5.2.6 Abort Command
The ABOrt command allows the console operator to
terminate the execution of an indicated task.

The format of the elements which comprise the command strings differs for each command. The terms
used to describe these elements. however. are consistent and are described as follows:

Format

QUTFILE - The output file specifier in the
format:

MCR>ABO TASKNAME<CR>
Example

DEV :[UIC]FILE.TYPE: VER
MCR>ABO JAH<CR>
IN FILE -

The input file specifier in the format:

5.2.7 Unload Command
The UNLoad command allows the operator to cause
an indicated 110 handler task to release memory.

DEV :[UIC]FILE.TYPE: VER

Format

If more than one file can 'be specified. they are distinguished as
INFILEI. INFILE2. etc.

MCR>UNL DEVICE<CR>
/SWITCH - The command switch in the format:

Example

/SW:VALUE

MCR>UNL LP<CR>

5-2

In order to save keystrokes, the user would not normally type in the complete file specifier string, but
would take advantage of the system defaults. In parti;:-ular:

Wild cards provide another method of saving keystrokes. In particular:

[*, *] do the command on all areas of the
device. This format is only available to
the system manager.

[UIC]DEV:-

The unit on which the system disk is
mounted. The device will normally be the
default device and this can be omitted.

[UIC]-

The user's UIC. If the file is located m the
user's area this can be omitted.

FILE-

The file name of the specifier before the
comma, if any. If the name of the file is the
same as the one immediately preceding it.
this can be ommited. For example, in the
line:

[GROUP.*]- do the command on all areas of the device with the given group number. This
format is available to the System Manager, controllers. and group editors.
FILE-

* do the command on all file names in
the directory.

.TYPE-

.* do the command on all file types m
the directory.

:VER-

: * do the command on all file versions
in the directory.

©COMMAND FILE.PRF..SET<CR>
the file after the comma is FILE.SET.
.TYPE- The file type of the specifier before the
comma, if any. If the type of the file is the
same as the one immediately preceding it.
this can be ommited. For example, in the
line:

The examples listed with the following commands illustrate the use of the above features.

5.3.1
©COMMAND FILEl.PRF.FILE2<CR>
the file after the comma is FILE2.PRF
:VER-

Directory Command

The Directory command provides the user with the
facility to list one or more directories. The format for
this command is:

The default for input files is the most recent
version number. The default for output files
is the next higher version number, or version
one if the file doesn't already exist in the
output directory. An exception is the DElete
function which requires an explicit version
number. The format:

©D
Ol)TFILE = INFILE 1 ILl IFU.
INFILE2/U/FU... c

where:
OUTFILE is the listing file specifier. If omitted.
the default is the terminal the user is on.

:0
can be used to specify the newest version.

INFILE is the input file specifier. If omitted.
the default is all the files in the user's area.

The format:

III is the optional List Intermediate switch.

:-1

IFU is the optional list FUll switch.

can be used to specify the oldest version.

5-3

The following shows samples of the directory listing
in all of its possible formats:
©D<CR>
DIRECTORY DPO:[4.I]
27-AUG-74 15:51
II SUG5.PRF: 1
IISUGA.PRF:2
IISUG5.PRF:2
<0D/LI<CR>
DIRECTORY DPO:[4.1]
27-AUG-74 15:52
II SUG5.PRF: I
IISUGA.PRF:2
II SUG5.PRF:2

28.
16.
26.

27-AUG-74 12:37
C 21-AUG-74 16:19
L 27-AUG-74 14:13

<0D/FU<CR>
DIRECTORY DPO:[4.I]
27-AUG-74 15:53
IISUG5.PRF:I
12:37
[4.1 ]
IISUGA.PRF:2
16:19
[ 1.l0]
IISUG5.PRF:2
14: 13
[4.1]

(5355,556)

27-AUG-74

28.130.

[RWED,RWED,RWED,R]
(10531.1456)

28-AUG-74 14:49(2.)
16.120.
C
21-AUG-74

[RWED,RWED.RWED.R]
(3665.656)

26.130.

[RWED,RWED,RWED,R]

5-4

27-AUG-74

The following gives an explanation of the items appearing in the III and IFU listing format.

III
FILENAME.TYP;VER UUUU. CL DA-MON-YR
HH:MM
Item

Meaning

FILENAME
TYP
VER
UUUU

File name
File type
File version
Number of blocks used
If present. indicates file is contiguous
If present. indicates file is locked
Day of month file was created
Month of year file was created
Year file was created
Hour of day file was created
Minute of hour file was created

L
DA
MON
YR
HH
MM

IFU
FILENAME.TYP;VER (NUMBE,SEQUE) UUUU.! AAAA.
CL
DA-MON-YR
HH:MM
[GRO,VSE][SYST,OWNE,GROU,WORL]
da-mon-yr
hh:mm(REV.)

Item

Meaning

FILENAME
TYP
VER
NUMBE
SEQUE
UUUU
AAAA
C

File name
File type
File version
File number
File sequence number
Number of blocks used
Number of blocks allocated
If present indicates file is
contiguous
If present indicates file is
locked
Day of month file was created
Month of year file was created
Year file was created

L
DA
MON
YR

5-5

Item

Meaning

Hour of day file was created
Minute of hour file was
created
Group number of file's
owner
User number of file's owner
Protection code for system
Protection code for owner
Protection code for group
Protection code for world
Day of month file was last
revised
Month of year file was last
revised
Year file was last revised
Hour of day file was last
revised
Minute of hour file was last
revised
Number of revisions to the
file

MM
GRO
USE
SYST
OWNE
GROU
WORL
da
mon
yr
hh
mm
REV

2. ©D*.SET;*<CR>
List· on the terminal all files in the user's are
with a file extension of .SET.
3. ©D STORYl.PRF.STORY2;*<CR>
List on the terminal the lastest version (
STORYl.PRF and all versions of STORY2.PRF.
4.

List on the terminal all files in the 100.120 area.
5. ©D ME.DIR = IFU <CR>

Create a file ME.DIR containing a full listing c
all files in the user's area. This command is useft
when a full listing would overflow the VT20'
memory. The directory can then be printed 0
the line printer with the command
©P ME.DIR<CR>
5.3.2 Proof Extract Command
The proof EXtract command provides the user wit
the facility to determine the general content of stor
files by looking at the first few lines of text in eac
story. After the text displayed fills the VT20 screer
... MORE? is displayed and the user may pres
<NEXT> to look at more stories or quit by pressin
<FINI>. The format for this command is:

The protection codes are:
RWED-

©D[100.l20]<CR>

Read access is granted
Write access is granted
Extend access is granted
Delete access is granted

©EX INFILElIFU.INFILE2/FU ....
Examples of Directory commands:
I.

where:

©D STORY.*;*<CR>

INFILE is the input file specifier. If omittec
the default is all the files in the user's area.

List on the terminal all files III the user's area
with a file name of STORY.

IFU is the optional FUll switch.

5-6

",,'" .''',,"'"'

The following shows samples of the proof extract listing in its two possible formats.
©EX<CR>
DIRECTORY DPO:[4.1]
lISUG5.PRF:l
CHAPTER 5 SYSTEM OPERATION
5.IMONITOR CONSO
IISUGA.PRF:2
APPENDIX A
GLOSSARY
TERM DEFINITION
©EXfFU<CR>
DIRECTORY DPO:[4.1]
IlSUG5.PRF:1
CHAPTER 5 SYSTEM OPERATION 5.IMONITOR CONSOLE INTERFACE
OPERATION
This section describe
IISUGA.PRF:2
APPENDIX A
GLOSSARY
TERM DEFINITION
Algorithm A set of wel1-defined op
Examples of proof EXtract command:
1.

fPU:n

©EX[I00.120]<CR>
Extract all story files from the 100.120 area.

©EX*.*<CR>
Extract the latest version of all story files in
the user's area.

©EX*.MON <CR>

NOTE
Version numbers must be explictly
input for deletes and must be left
out for purges. This precaution
will protect the user from deleting
a file when purge was intended.

Extract the latest version of all story files
with a .MON extension.
4.

The PUrge switch provides the user with a
convenient method of deleting all old versions of files and keeping the n most recent
version. If the optional value n is specified
then al1 but the n most recent versions are
deleted. If the n value is omitted it is defaulted to I and all but the latest version are
deleted.

©EX[300,1]*.WIR<CR>
Extract all wire service stories in the 300, I
file pool area.

Example of Delete command:

5.3.3 The Delete Command
The DElete command provides the facility to delete
specified files. The format for this command is:

©DE STORY.MON:I<CR>
Delete version I of the file STORY.MON.

©DE INFILE IfPU :n,INFILE2fPU :n, ...

2. ©DE*.SUN:*<CR>

where:

Delete all files in the user's area which have
a .SUN extension.

INFILE is the input file specifier. This must always be input because there is no default.

3. ©DE*.*:*<CR>
Delete all files in the user's area.·

fPU:n is the optional PUrge switch.

5·7

INFILE is the input file specifier. It must be
input because there is no default.

4. ©DE STORYl.MON;1,;2,STORY2;1<CR>
Delete versions
and 2 of file
STORYl.MON and version 1 of file
STORY2.MON.
5.

NOTE
Renaming files across devices is not
allowed.

©DE STORY.TUE;O<CR>
Examples of Rename command:
Delete the newest
STORY.TUE.

file

1. ©R STORY2.MON; 1 = STORY1.MON;5
<CR>

©DE STORY.TUE;-I<CR>
Delete the
STORY.TUE.

version

oldest

version

Rename file STORYI.MON;5 to become
STORY2.MON;1.
2. ©R
BACKUP.*;* = STORYl.*;!I'.
STORY2.*;* <CR>

©DE STORY.*/PU:2<CR>
Delete all but the two latest versions of all
files with a file name of STORY.

Rename all files with the names STORYI
and STORY2 to BACKUP preserving type
and version.

©DE STORYI.MON/PU,STORY2;*<CR>
3. ©R*.*;I = *.*<CR>
Delete all but the latest version of
STORYI.MON and all versions of
STORY2.MON

Rename all of the latest copies of files to
version I.

NOTE
The IPU switch does not carry over
from one specifier to the next.

CAUTION
There must not be other versions of
these files!!
4.

5.3.4 The Rename Command
The Rename command provides the user with the facility to change the name of a file. The format for
this command is:

©R[200.220] = [200.200]*.*;*<CR>
Rename all files out of [200.200] into [200.220]
preserving the filename.

5.3.5 The Copy Command
The COpy command allows the user to transfer files
from another user's area on the disk to his area. to
another disk. or to a different medium (i.e .. magtape).
The user may also create another copy of a file where
the copy is given a different name. The format for
this command is:

©R OUTFILE = INFILE l.INFILE2 ....
where:
OUTFILE is the output file specifier. It has the
special property that the file name. type. and
version are individually allowed to be explict.
wild card (*). or defaulted (null). A name. type.
or version field that is either wild card or null
means that the corresponding field of the input
file is to be used. Thus. the rename command
provides the facility to change one or more
fields while preserving the others.

©CO OUTFILE = INFILEI/SU/NV,INFILE2
ISU/NV, ...
where:
OUTFILE is the output file specifier. If omitted
the default is the input file specifier.

5-8

INFILE is the input file specifier. It must not
be null.

Copy the latest version of the file STORYI.MON
in user area [200.200) into the new file
STORY2.MON. The version number of the new
file will be the same as the latest version of
STORYI.MON.

ISU is the optional SUpersede switch and INV
is the optional New Version switch.

2. ©CO STORY2.MON = STORYI.MON:IISU
<CR>

/SU- This switch allows the user to copy a file
into an area in which the name. type. and version of the file already exist. The old file is deleted and replaced with the specified input file.

Copy the file STORYI.MON: I into the file
STORY2.MON: I. If the file STORY2.MON: I
already exists in the user's area replace the old
file with the one copied in. The old file is deleted.

INV- This switch allows the user to force the
output version number of the file being copied
to the latest version of the file. If the file
doesn't already exist a version of I is assigned.
The following depicts the results which occur
when the INV switch is specified.

3. ©CO STORY2.MON = STORYI.MON:I/NV
<CR>
Copy the file STORYI.MON: I into a new file
with the name STORY2.MON and cause the version number to be the newest version of that file.
If STORY2.MON does not already exist make
the version ·number I.

Directories Before COpy
Input Directory
Output Directory
STORYl.MON;1

STORYl.MON;2
STORYl.MON;4

4. ©CO = [377.1)*.*<CR>

Directory After COpy Without INV Switch set
Input Qirectory
Output Directory
STORYI.MON;1

Copy the latest version of all files in area [377.1)
to the user's area prese~ving file name. type. and
version.

STORYI.MON;2
STORYI.MON;4
STORYI.MON;1

5. ©CO STORYI.MON = [377.IJ*.*<CR>
Copy the latest version of all files in area [377.l)
into the new file STORYI.MON by merging the
files together. This is an alternate to the MErge
command. Refer to Paragraph 5.3.6 for details.

Directory After COpy With INV Switch set
Input Directory
Output Directory
STORYI.MON;1

STORY I.MON;2
STORYI.MON;4
STORYl.MON;5

5.3.6 Append Command
The APpend command allows the user to add to the
·end of an existing file the concatenation of the input
files. The format for this command is:

NOTE
The version specified in the input tile specifier must be explicit or default; no wild
cards allowed.

©AP OUTFILE = INFILE- UNFILE-2 ....
where:

Examples of COpy command: .
OUTFILE is the output file specifier. It must be
the name of an existing file. No wild cards are
allowed.

I. ©CO STORY2.MON = [200.2IO)STORYI.MON
<CR>

5-9

INFILE is the input file specifier. It must not
be null.

S.3.7 The Merge Command
The MErge command creates a new file and copies
the list of input files into it. producing a file which is
the concatenation of the input files. The format for
this command is:

NOTE
It is recommended that the user not
use this command but rather use the
MErge command. Append overwrites
an existing tile and does not create
any backup should anything go wrong.
If an error message is produced while
appending, the user should edit the
output tile back to its original form
and then re-input the APpend command, correcting the problem that
caused the error.

©ME OUTFILE = INFILE UNFILE2 ....
where:
OUTFILE is the output file specifier. This must
be explict i.e .. no wild cards are allowed.
INFILE is the input file specifier. This must not
be null.

Examples of APpend command:
I. «JAP STORYI.MON = STORY2.MON<CR>

MErge is almost identical in its operation to the APpend command. The only difference is that MErge
creates a new ouput file. whereas. APpend adds to an
already existing file. MErge. therefore. provides complete backup since all the input files are preserved. If
an error is detected during a merge. it is only necessary to delete the newly created output file and start
over.

Append the latest version of STORY2.MON to
the end of the latest version of STORYI.MON.
The following shows the result of this command:

File

Original Contents

STORYI.MON

Now is the time for all good
me

STORY2.MON

n to come to the aid of their
country.

File

Final Contents

STORYI.MON

Now is the time for all good
men to come to the aid of
their country.

STORY2.MON

5.3.8 The Protect Command
The PROtect command provides the facility to alter
the protection of a file. File protection is provided for
four categories as follows:

n to come to the aid of their
country.

2. ©AP MON.WIR = [377.1]*.WIR
Append to the end of the latest version of the file
MON.WIR all files in area [377,1] with the extension .WIR.

5·10

SYstem - Protection against system accounts
(all groups less than or equal to 10).

OWner-

Protection against the owner of the
file.

3. GRoup-

Protection against other users In the
same group.

Protection against all accounts not
covered above.

WOrld-

For each category the user can specify whether those
accounts may Read. Write. Extend (APpend). or
Delete the file. The format of the command is as follows:
©PRO

2. ©PRO STORY.HOT;I/OW:D<CR>
Allow the user to delete STORYI.HOT:1. The
owner will not be able to read. write. or extend
the file after the command is issued

INFILE/WO:rwed/GR:rwerl/OW:rwed
3. ©PRO PERSONNEL.YOU:*/SY/GR/WO

ISY:rwed

Protect all versions of the file PERSONNEL.YOU
from being accessed by anyone but the owner.
The System Manager has the power to reprotect
this file if needed.

The switches ISY. lOW. IGR. IWO allow the user
to specify which protection is to be altered (others are
left intact). The values which follow the switch are
any of the 4 letters R. W. E. D (for Read. Write.
Extend. Delete) in any order. They specify which
privileges that group of accounts may have. If the
switch is present and no value is given then no privileges are granted for that group of accounts.

5.3.9 The Unlock Command
The UNlock command allows the user to unlock a
locked file. If Class Ad is running when a system
crash occurrs. the .CAD files will become locked.
They must be unlocked before Class Ad can be restarted. Any other locked file should be unlocked and
deleted.

Examples of PROtect command
1. ©PRO STORY.HOT; lIOW:RWE<CR>

The format for the UNlock command is:
Protect STORY.HOT; 1 so that the owner of the
story cannot inadvertently delete it.

©UN INFILEI.INFILE2 ....

5-11

CHAPTER 6
HOUSEKEEPING OPERATIONS

6.1 HOUSEKEEPING DISK PACKS AND FILES
To simpli(v housekeeping operations and identification of files. the file extensions may be allocated to
identi(v day-to-day work. department work. multipaperwork. etc.

The following file extensions have been assigned to
the system and should not be used to identify files
unless they fall into these categories.
.WIR Wire service
.SET Machine code output file
.FMT Format files

Examples
FILEI.MON
FILEI.TUE
FILEI.SAT

The housekeeping operation procedures are. divided
into three categories - Minor Housekeeping. Daily
Housekeeping. and Weekly Housekeeping. Each of
these procedures is explained in the following paragraphs.

Identifies day-to-day work.

FILEI.SPT
Identifies department work
FILE2.NEW
FILEI.WOM
FILEI.Tl

6.1.1

Minor Housekeeping (Designating Files to be

Saved)

This procedure is used to rename files with a new
extension so they will be saved when the daily or
weekly housekeeping procedures are performed to
clean up system files. The Rename command is used
to change the extension of files to be saved for future
use or to be used the next day. For example:

Identifies multi-paper day-to-day
work.

FILE2.T3
FILEI.N2
FILE2.N4

©R FILE.SAV = FILE.SUN<CR>
Files to be saved can be identified by .SAV; files to
be repeated can be identified by .REP. If the user
decides to save a file that has been assigned an extension that is to be deleted, he can change the extension using the REname command (Paragraph
5.3.4). Copy received in advance of the day it is to be
printed may be assigned a .SAV extension or it could
be identified by the day or date it is to be printed.

(new extension) = (old extension)
will change the extension to an extension .sA V that
would not be deleted when files with the .SUN extension are deleted from the system during daily or
weekly housekeeping operations.
©R FILE.MON = FILE.SUN<CR>
will change the extension of FILE to .MON so that it
will not be deleted until housekeeping is done on
Monday .

For example:
.sAT (day) or .028 (date) etc.

6-1

6.1.2 Daily Housekeeping
Daily housekeeping is done after minor housekeeping
has been done to change the extension names of files
to be saved. To delete all files that have been used
on a given day, in the area that the user is logged in
under, the command:
©DE*.DAY:*<CR>
should be used. For example:

Load 173100 into the SWITCH REGISTER
and press LOAD ADDRESS (LA).

Set SWITCH REGISTER to 177344 for
DECtape and press START. (Go to step
11. )

Set the SWITCH REGISTER to 173120 for
DECtape or 173136 for magtape and press
LOAD ADDRESS (LA).

10. Press START.

©DE*.SUN:*<CR>

11. Wait for:

will delete all files from the user's area that have a
.SUN extension.

ROLLIN VXX

6.1.3 Weekly Housekeeping
The weekly housekeeping procedure should be done
once a week, or daily, if the system handles a large
number of files. This procedure is used to renew or
refresh the data on the system pack to prevent deterioration of the Typeset-II program. It is the same effect as installing ihe master pack or a new system
pack since all data is completely rewritten. The master pack mentioned in this procedure should be
stored in a vault or safe to prevent its deterioration
or damage in a fire, flood, etc.

to be typed out at the terminal (XX is the
version number of the ROLLIN tape on
your site).
12. Type:
DPO:<DPI :/VE<CR>
When # is typed out again. remove the
master pack from drive I and return it to
the vault.

The weekly housekeeping operation procedure follows:
1.

Shut down typeset system as explained In
Paragraph 8.5.

Mount ROLLIN DECtape on DTO or magtape on MTO.

Remove today's pack from DPO and set it
aside.

Mount tom morrow's pack on drive 0 with
drive on READ/WRITE.

Mount master pack, from the vault, on drive
I with drive on READ ONLY.

Set ENABLE/HALT to ENABLE.

13. Mount today's pack on drive 1 and leave
control set to READ ONLY.
14. Restart typeset system following the procedure in Paragraph 8.3.

NOTE
The next 2 steps will copy all files
that were saved during daily housekeeping procedure from DPI to DPO.

15. To copy all .SA V files from DPI to DPO
type:
MCR>REQ ... PIP/UIC = [x'Y]<ALT>
where:

NOTE
Systems with a BM792 Bootstrap
Loader Program should perform steps
7 and 8 and systems with a MRllDB Bootstrap Loader should perform
steps 9 and 10.

[X.Y] is the user area to be copied.
The terminal will respond with:
PIP>
6-2

Now type:

6.3 EXCEPTION WORD DICTIONARY UPDATE
PROGRAM
When it becomes necessary for the J&H program to
hyphenate a word. the exception word dictionary file
(JHDICT.sYS) and a set of probability tables are
accessed simultaneously. If the word in question is
listed in the exception word dictionary. it is hyphenated accordingly, otherwise, it is hyphenated according to the probability tables (Le., algorithmically).
The JHDICT.SYS file resides on the system disk in
UIC[2.3] and contains a current list of properly hyphenated words. The probability tables are core resident and are used to compute the most probable location of a hyphen in any word.

PIP>DPO: = DPI:*.SAV.:* <CR>
NOTE
This procedure must be performed for
all user areas containing .SAV files to
be copied over.

To return to MCR mode type:
<CTRLlZ>
then

If a word is typeset with improper hyphenation, it
was either entered in the exception word dictionary
incorrectly, or it is not in the dictionary. The exception word dictionary update program (DIC) is used
either to correct improper hyphenation or to enter
new words in the exception word dictionay.

<CTRLlC>.
16. Remove DECtape or magtape and return to
storage.
17. Remove today's pack and return to storage.
6.2 BACKUP DISK PACKS
Once the Typeset-II System has been installed. extreme care should be taken to maintain backup RP03
disk packs. The RSX-IID and Typeset-II Programs
are installed on the RP03 disk at the time of installation. Each system should have four RP03 packs containing the system programs as follows:
I.

A fire storage pack. stored in a bank vault.
so it can never be destroyed at the installation.

A master backup pack should be stored in a
safe place at the installation to be used to
refresh the system pack during the weekly
housekeeping operation.

6.3.1 DIC Input
The input to the DIC program is a proof format file
typically named update which contains one word per
line with all legal hyphens inserted. The input file is
created at the VT20 by typing:
©Filename< CR >
This command string creates the input update file
into which the desired words may be entered. Following is an example of typical words as they might appear in the input file.
di-a-tom<CR>
cym-bid-i-um <CR >

3. The system pack that is installed on the system disk for system operation plus a backup
in the computer room. If this procedure is
followed. the user will always have Ii disk
pack available for system operation. If it is
ever' necessary to remove the fire storage
pack for system operation. it should be copied using the weekly housekeeping procedure and returned to fire storage as soon as
possible.

NOTE
Each one-word line must be terminated with a < CR >.

6.3.2 Correcting and/or Deleting Words
If.a word is incorrectly hyphenated in the dictionary
(e.g.,dia-tom),it is corrected by entering the word correctly hyphenated in the update file and running the
DIC program. When the program is run, the incorrectly hyphenated form of the word is deleted and
replaced by the correctly hyphenated form.

NOTE
One clean pack per drive should be
kept for maintenance purposes.
6-3

Words are deleted from the exception word dictionary by marking them with the () symbol in the update file as follows:

enough core to run both the system programs and
DIe simultaneously. If you type:
MCR>DIC<CR>

diatom
and the system response is:
The deletion occurs when the DIC program is run.
MEMORY NOT AVAILABLE
6.3.3 Installing and Running DIe
The DIC program is normally run at the beginning
of the day prior to doing a batch start-up (BAT
STARTUP). Running the program merges the input
file with the current exception word dictionary creating a new version of the JHDICT.SYS file. The input
file does not have to be in alphabetical order.

To run DIC at the system console, type:
MCR>INS [2,IO]DIC
This installs the DIC program in the system. Now
type:
MCR> DIC<CR>
DIC>[UIC]FILENAME<CR>
where:
UIC is the input file UIe.
FILENAME is the input file name (typically
UPDATE)
Assuming that there are no errors, these two command strings cause the new JHDICT.SYS file to be
generated in UIC [2.3].When the file is complete, the
system responds with:
DIC>
If there is an error, the new ~HDICT.SYS file is not
created and an error message is generated. The error
messages are listed at the end of this document.
A second method of activating the DIC program is
used if it is desirable to run DIC after the Typeset-ll
system is started up. However, there may not be

then, type:
MCR>REQ# ... DIC(ALT)
to run the DIC program. This forces the J&H program out of core (i.e .. checkpoints J&H) and runs
DIe.
NOTE
Running DIe after system startup does not
incorporate the resulting updated exception
word dictionary into the system until the
next time BAT STARTUP is run (normally
the beginning of the next day).

After running the DIC program, the new dictionary
([2,3]JHDICT.sYS) must be copied to the production
master pack, so that it will be incorporated into subsequent daily production packs.

6.3.4 Optional DIe Switches
The switches listed in Table 6-1 are available for
manipulating file flow when the DIC program is run.
The proof output file generated when either fLO or
fHY is specified is named JHDICT.PRF and is
stored in VIC [1,10]. This file can be printed on the
line printer after typeset is started from either a VT20
or the MCR console using OPR by typing, P
(1, IO]JHDICT.PRF.
Once DIC is installed, a listing of the current exception word dictionary can be obtained by using the
fLO switch without specifying a filename, for example:
MCR>OPR P [l.IO]JHDICT.PRF

Table 6-1
DIC Switches
Definition

Switch

Fonn

Create

fCR

Creates a new dictionary from the input proof file
and ignores the old dictionary. THIS OPTION IS
FOR USE BY DIGITAL EQUIPMENT CORP
ONLY.

Log

fLO

Creates a new dictionary by updating the current dictionary with the input proof file and generates a
proof output file (JHDICT.PRF), which contains a
list of all of the words in the new (updated) dictionary. Can also be used to obtain a listing of the current dictionary without first doing an update (see below).

Hyhphenation

fHY

Compares the hyphenation given in the specified input file to the J&H hyphenation algorithm for each
of the words in the input file, and generates a proof
output file, JHDICT.PRF (Figure 6-1) that can be
listed as explained below. This switch overrides the
fLO and fCR switches; no new dictionary is created
when this option is used.

6.3.5 Exiting and Removing DIC
To exit from the DIC program, type:

AARD-VARK
ABAN-DON
ABAN-DONED
ABAN-DON-MENT
ABI.L-I-TIES
A.ln.L-I-TY
A.B-O-LI-TION
ABRUPT--LY
AB-SO-LUTE-LY
ABUN-DANCE
ABUN-DANT
A.C-A-DEM-IC
ACAD-E-MY

(100%)
(OK)
(OK)
(OK)
(BAD HYPHENS)
(BAD HYPHENS)
(MISSED HYPHENS)
(OK)
(100%)
(OK)
(OK)
(MISSED HYPHENS)
(BAD HYPHENS)
AC-CEL~ER-AT-ED
(MISSED HYPHENS)
AC-CEL-ER-OM-E-TER (MISSED HYPHENS)

CTRLZ
The system responds with:
MCR>
To remove Ole. type:
MCR>REM ... DIC<CR>
6.3.6 Hyphenation Symbology
Figure 6-1 is part of a line printer listing showing an
example of the output file that is generated when the
fHY switch is used. The file contains properly and
improperly hyphenated words. Table 6-2 lists and defines the hyphenation symbols used to compare the
hyphenation produced by the system to that specified
in the dictionary.

Figure 6-1 A Partial LP Listing of a IHY
Generated JHDICT.PRF File

6-5

Table 6-2
Hyphenation Symbols and Corresponding Messages
Symbol

Either. or -

Message

Definition

(BAD HYPHENS)

The hyphen was computed by J&H but was not indicated in the input file.

(MISSED HYPHENS)

The hyphen is specified in the input file but was not
computed by J&H.

(OK)

A hyphenation error follows the first letter or
preceeds the last letter of a word. Since such a point
would not be considered for hyphenation, the error is
not considered to be significant.

(100%)

The hyphenation specified in the input file is the
same as that computed by J&H.

6.4 FORMAT MANAGEMENT
The Typeset-II System Manager will have to edit existing formats from time to time and create new formats as production requirements change (refer to
Typeset-II Markup Manual. DEC-II-HMUPA-A-D).

6.4.2 System (Protected) Formats
Some formats are designed to be used frequently in
many stories. These system formats must be protected
against inadvertent or malicious alteration or deletion.
which can be done by using PIP to set a file protection. prohibiting any access to the format file except
reading the file.

6.4.1 Creating Formats
Formats may be created either by processing format
definition commands through the justification and
hypenation program, or by creating format files and
transferring them to the format storage area.

6.4.2.1 Protecting an Existing Format
All formats are stored in one area. under UIC [2.1].
Once a system format has been created. the file containing the format may be protected by running PIP
on the MCR terminal under a system manager's UIC.
To protect a format. type the following commands:

6.4.1.1 Using J&H to Create Formats
Refer to the J&H Markup Manual for information on
the format definition commands. To define a series of
formats using the J & H program, create a file for
input to the J&H program which contains only the
format definitions. This file may be created either by
perforating a paper tape and submitting the tape to
the paper tape reader, or by creating a file through
the VT20 editor. When the file is created, submit it to
the J&H program (for a file created ~y the input
spooler, the spooler may automatically queue input
files to J&H), and the processing of the file causes
the formats to be created, in VIC [2,1].

MCR>REQ ... PIP/VIC = [2.1]<ALT>
PIP>NAMEl.FMT;I/PR:-I0422 <CR>
PIP>NAME2.FMT; I/PR:-I0422 <CR>

Continue typing to protect each format. If the only
formats stored in the area are system formats. a wild
card form of the command may be used to protect all
the formats:
PIP>[2.I]*.FMT; IIPR:-10422 <CR>

6-6

6.4.3.1 Altering a Temporary Format using J&H
To alter or replace a format using the J&H program.
simply create a file containing the format definition.
and process the file through the J & H program as
described in Paragraph 6.4.1. The new definition replaces the old definition. if the existing format is not
protected.

When a format has been protected in this manner. it
cannot be deleted or altered; any attempts to redefine
the format using the format definition commands in
J&H cause an error message to be generated and the
file is unchanged.

NOTE
An attempt to alter a protected format produces the error message:

6.4.4 Deleting Formats
To delete a format. the format must first be unprotected and then deleted as follows:

<?? PROTECTED FORMAT>

6.4.2.2

MCR>REQ ... PIP/VIC = [2.I]<ALT>
PIP>NAME.FMT;l!PR:O <CR>
PIP>NAME.FMT;I/DE <CR>

Unprotecting a Format

When it is necessary to edit or delete a system format. the protected file must first be unprotected. This
is done in much the same manner as protecting the
format. except that the value provided to the protection switch in the PIP command is O. For example.
unprotecting a system format named PAGENO is
done by the following commands:

To return to MCR mode type:
<CTRLlZ>
then
<CTRLlC>.

MCR>REQ ... PIP/UIC = [2.I]<ALT>
PIP> PAGENO.FMT; I/PR:O <CR>

6.4.3 Altering a Format
A format may be altered by redefining it using the
J&H program. or by editing the format file and replacing the file in the format storage area. To alter a
system format. the format must be unprotected as described in Paragraph 6.4.2.2.

6.4.5 Managing Temporary Formats
Temporary formats should be allocated file names
that allow easy identification for easy deletion. The
system manager should allocate format names so only
a few names are used each day. In this manner. they
can be located. edited. or deleted easily.

6-7

CHAPTER
ERROR MESSAGE~

7.1 GENERAL
There are two basic types of error messages: RSXII D error messages and Typeset-II error messages.
All error messages are coded and the code is issued
when an error occurs. The error codes are listed in
the Typeset-II Error Messages Manual (DEC-I 1HSYEA-A-D). When an error code is issued. refer to
this manual to determine which error has occured
and the appropriate corrective action to be taken.

7-1

CHAPTER 8
STARTUP AND SHUTDOWN OPERATION

8.1

INTRODUCTION

8.2 TYPESET-II SYSTEM INITIALIZATION
System initialization ensures that the switches on the
11/45 and 11 IDS computer console and terminal are
set to the correct positions for system operation. The
initialization procedure is:

There are several programs included In the .TypesetII System software:
Example

RSX-IID Operating System

1. Tum computer POWER key ON.

Typeset-II Programs (Queue Manager. Applications Monitor. J AND H. CLASS-AD.
and Spoolers)

VT20 Program

VT20 Load Program (VTLOAD)

Set the ENABLEIHALT switch to HALT.

NOTE
Perform step 3 on systems with a Teletype, and step 4 on systems with a
DECwriter.

The RSX-II D and the typeset programs must be
loaded into the PDP-I1I45 system to allow the system to operate. The VT20 program must be loaded
into the PDP-II IDS processor to allow operation of
the Video Display Terminals (VDT's). The VT20 program is transferred from the PDP-I1I45 processor to
the PDP-II IDS processor by VTLOAD. and loaded
into the PDP-II IDS by the Absolute Loader. The
Loader is. in tum, transferred from the PDP-I 1/45 by
VTLOAD and loaded into the PDP-I 1105.

Turn Teletype control switch to LINE. Teletype motor should be running.

Set CB 1 and CB2 at rear of LA30 to ON
and verify that the READY indicator is on.
Set the mode switch to ON-LINE and
BAUD RATE to the correct baud rate for
your system.

NOTE
For normal operation, the AC power
cable must be connected to the Teletype or DECwriter correctly and the
AC power and data cables must be
connected to the tape punches. If either of these cables has been accidently disconnected, the associated
peripheral device will not function.

Normally the Typeset Programs and the VT20 programs are stored in the system and need only be
started to run them. It is good practice however. to
initialize the system daily to ensure that the system is
running properly.

8-1

Set control switch on each tape punch to
AVAILABLE. Ensure that the punches contain sufficient tape.

Ensure power is applied to the disk drives.

Ensure that the Line Printer POWER.
READY. and ON-LINE lamps are lit.

8.3

Load SWITCH REGISTER with 773154.
press LOAD ADDRESS. then press START.
After START is pressed the RSX-IID program will be bootstrapped from the system
disk into core memory.

Follow instructions below:

. NOTE
Entries that the operator must type are underlined. The information typed out as a
result of these commands may vary from
system to system, but the information typed
in is the same for all systems.

Ensure that power is applied to the photocomp machine.

STARTING THE TYPESET-ll SYSTEM
NOTE
When starting the system at the beginning
of the day, or after the system has been
shutdown, the start procedure should be
used. If the system crashes, and must be
restarted during the day, use the restart
procedure in Paragraph 8.4.

When the program is in core memory the terminal
will type out the following message:
TYPESET-l I RSX-004A
This message is the version number assigned to your
RSX-llD operating system.

After the system initialization procedure has been
performed. the system may be started as follows:

SA Yo-CORE SIZE:80<CR>

NOTE
If at any point during the startup procedure
you cannot continue the startup procedure
return to step 1 and start the procedure
over.
1.

The user must type in the size of core memory for his
system. 80 is used in the example just shown.
The user must type in the time of day and the date
as shown in the following example:

Ensure ENABLE/HALT set to HALT then
set ENABLE/ HALT to ENABLE.

MCR>TIM 9:30:00 2125!74<CR>

NOTE
Perform steps 2 and 3 on systems
with a BM792 Bootstrap Loader and
step4 on systems with an MRll
Bootstrap Loader.
2.

Load SWITCH REGISTER with 173100
and press LOAD ADDRESS (LA).

Load SWITCH REGISTER with 176716.
then press START. (Continue with step 5.)

MCR>MOU DPO:<CR>
MOUNT-**VOLUME INFORM ATION**
DEVICE = DPO
CLASS = FILEII
LABEL =
UIC = [lJ]
ACCESS = [RWED.RWED.RWED.
RWED]
CHARAC = []

8-2

After the next command is typed. the programs will
be started and the queues will be activated. The user
can observe the system terminal and observe when
each operation is completed. The typeout here is a
typical example of the typeout seen but not necessarily the typeout you will see on your system:

: START UP SPOOLERS
STA PROSP/UIC = [1.1]
STA PRISP/UIC = [1.1]
STA PPOSP
STA PPISP
STA PCOSP
REM PRT
STA LPOSP

MCR>BAT STARTUP<ALT>
: STARTUP.JOB

: START UP JAH
: STARTUP TYPESET
STA JAH/UIC = [1.1]
: LOAD 1/0 DRIVERS
UNL LP
UNL MO
LOA VT
LOA PR
LOA PP
LOA PC
LOA LX

: START UP LOGIN PROGRAMS
STA VTOLOG
STA VTlLOG
STA VT2LOG
STA VT3LOG
; ACTIVATE THE QUEUES

: NOW SET UP OF:
:OPR ©STARTUP
INIDF:
MOU OF:
MOUNT-**VOLUME INFORMATlON**
DEVICE = DFO
CLASS = FILE II
LABEL =
UIC = [10.1]
ACCESS = [RWED.RWED.RWED.
RWED]
CHARAC = []
UFO DF:[1.I]
PIP ©[1.I1]JAHSYS

: PUT IN NEW TKTN
REM .TKTN
INS [12.1] TYTKTN
INS [12.1]TKTNI
: UNFIX BPR ...
INS [11.1]UNF/TASK = ... UNX
UNX BPR ...
REM ... UNX
******END OF BATCH

: FUDGE REQUEST
INS [11.1]REQ/TASK = ... STA/PAR = MCR

Now type:

: START QUEUE MANAGER

PIP [2.4]*.QUE:*/DE
STA QM

The terminal will respond with:
MCR>

8·3

The terminal will respond with:

There may be some items of equipment that the user
does not use every day or at certain times of the day
or the batch startup operation may not activate all
the queues that are needed. The user should type the
command:

MCR>
At this time. the Typeset system is started and the
user can commence his daily operations.

MCR>OPR Q/QU<CR>
8.4 RESTARTING THE TYPESET-II SYSTEM
If the Typeset system crashes after it has been started
using the procedure in' Paragraph 8.3, and there are
files assigned to queues for processing. the system
should be restarted using this procedure. Otherwise.
all files assigned to queues and waiting to be processed will have to be reassigned to the appropriate
queues using the Queue commands. This procedure
allows the system to pick up at the point where it
crashed. and continue processing files. Any file that
was being processed when the system stopped will be
reprocessed in its entirety. Any files that were being
edited will be locked. The current version of each file
must be unlocked and deleted (except for .CAD files
[Paragraph 5.3.9]) before the file can be re-edited.

and there will be listed at the terminal a list of all
queues and their status. active or inactive. From this
list the user can select the queues he would like to
activate or deactivate for the day's operation. If the
user wishes to activate or deactivate for the day's operation. or if the user wishes to activate a queue that
is not active type:
MCR>OPR<CR>
The terminal will respond with:
*READY*
5. To activate a queue. type:

NOTE
This procedure cannot be used if the system was shutdown according to the procedure in Paragraph 8.5.

Q Queue namel AC<CR>
Example

Restart the system as follows:

Q PC31 AC<CR>

This example will activate the queue for photocomp
number 3. Any queue on the system may be activated in a similiar way.

Set ENABLE/HALT to ENABLE
NOTE
Perform steps 2 and 3 on systems
with a BM792 Bootstrap Loader and
step 4 on systems with a MR 11
Bootstrap Loader.

6. To deactivate a queue. type:
Q Queue name/-AC<CR>
2.

Load SWITCH REGISTER with 17310C
and press LOAD ADDRESS (LA).

Load SWITCH REGISTER with 1767H
and press LOAD ADDRESS. Then pres~
START. (Continue with step 5).

Load SWITCH REGISTER with 17315£
and press LOAb ADDRESS. then presi
START.

Example
Q PC3/-AC<CR>

This example will deactivate the queue for photocomp number 3. After the necessary queues have
been activated or deactivated type:
<CTRLlC>

8-4

All entries required by the operator are the same as
the startup procedure except the BAT command is
RESTART instead of START.

The terminal will respond with:
*READY*

NOTE
Entries required by the operator are underlined.

Now type:

TYPESET = II RSX-004A
SAV--CORE SIZE:80<CR>
MCR>TIM 9:30:00 2125174<CR>
MCR>MOU DPO:<CR>
MCR>BAT RESTART<ALT>

The system will take a few minutes to clos~
down the CLASS AD system. so the opera·
tor will have to wait a few minutes for th(
terminal to print:

CAD CLOSE<CR>

*READY*
After this step is performed. the typeout of information at the terminal is almost the same as the startup
procedure (Paragraphs 8.3). Refer to this paragraph if
an explanation is required.

Now type:
<CTRLlZ>

8.5 SHUTTING DOWN THE TYPESET-ll SYSTEM

The terminal will respond with:
MCR>

CAUTION
All users should be logged otT the system
before shutdown is started; otherwise files
that are being edited will be locked.

Now type:
MCR>DMO CAO:<CR>
MCR>DMO DPI:<CR>

Shut down the typeset system as follows;
If this step fails. try again: it may take
few seconds to shut down CLASS AD.

NOTE
Responses required by the operators are
underlined.
1.

Now type:
MCR>OPR Q/EX<CR>

Type:
<CRTLlC>

The terminal will close out all queues an
stop the QUEUE MANAGER. The term
nal will respond with:

If the terminal is in OPR mode. the user
must type KIL<CR> to return to MCR.

MCR>
2.

The terminal will respond with:
4.

Type:

MCR>
MCR>ABO JAH<CR>
Now type:
5.
MCR>SET/UIC = [1.10] <CR>
MCR>OPR<CR>

Type:
MCR>DMO DF:<CR>

8-5

To load the VT20 from the PDP-ll/45 MCR Console, proceed as follows:

Type:
MCR>DMO DPO:<CR>

Set ENABLE/HALT to HALT.

At the PDP-IlI05
VT20:

associated with

the

Set ENABLE/HALT to HALT.

8.6 NORMAL VT20 RESTART
At the PDP-II/OS proceed as follows to start the
VT20 program:

Set 37744 io at the SWITCH REGISTER.

Set ENABLE/HALT to HALT

Press ENABLE/HALT.

Set 0400 in at the SWITCH REGISTER.

Press LOAD/ADDRESS (LA) and
then press START.

Press ENABLE/HALT to ENABLE

Press LOAD/ADDRESS (LA) and then
press START.

At LA30 type:
MCR> VTL<CR>
The terminal wi1\ respond with:

After the VT20 is restarted the cursor at the terminal
will be displayed in the upper left hand corner. The
LOG IN message wi1\ not be displayed. The user
should hit <CMND> to put the terminal in the
CMND mode. The user can now log in. To log in
type:

VTL>
Now type:
VTL> VTx: <CR>
Where:

©x,y<CR>

x = 0.2.4.6 for the VT20 unit number.
where:

When the program has been loaded. the
LA30 will respond with:

x,y is the user's group-and-user number.
VTL>
The Terminal wi1\ respond with:

Type:
<CTRLlZ> <CTRLlC>

To return to the MCR mode.
and the user should type in the correct password.
When the password is typed correctly, the terminal
will respond with:

At this time
*PLEASE LOGIN*

*READY*

wiIl be displayed the terminal and the user
can log in as usual.

and the user Can continue his operation.

NOTE
If the VT20 cannot be restarted using

the load procedure the Bootstrap
Loader must. be loaded as explained
in the following paragraphs. .

8.7
RELOADING VT20 AT THE PDP-ll/45
(MCR CONSOLE)

8·6

_..

_--_._----_.

8.8
BOOTSTRAP LOADER LOADING PROCEDURE
The procedure for loading the Bootstrap Loader is:
1.

Depress HALT.

Set SWITCH REGISTER to 37744.

Depress LOAD ADDRESS.

Set SWITCH REGISTER to 016701 (the
contents of location 37744 of the Bootstrap
Loader).

Depress DEPOSIT.

Set SWITCH REGISTER to the contents of
the next memory location in the Bootstrap
Loader (Table 8-1) and depress DEPOSIT.
The address is incremented automatically
each time DEPOSIT is depressed.

Table 8-1
Bootstrap Loader

Location

Contents

Location

Contents

37744
37746
37750
37752
37754
37756
37760

016701
000026
012702
000352
005211
105711
100376

37762
37764
37766
37770
37772
37774
37776

116162
000002
037400
005267
177756
000765
175610

8.9 LOADING VT20 DIAGNOSTICS
The following vt20 Diagnostic programs listed
Table 8.2 are supplied with the Typeset-II system.

Table 8-2
VT20 Diagnostics

Repeat step 6 for all memory locations in
the Bootstrap Loader.

Title

MainDEC Number

Filename

VT20
Diagnostic

II-DBVTA-PB

vnOE.DIA

DL110ff
Line Test

II-DZDLA-PB

DL1IE.DIA

II Family
Instruction
Exerciser

II-DZQKC-PB

PDPll.DIA

Worst Case
Noise Test

II-DZMMG-PB

NOISE.DIA

Random
Data Test

II-DZMMI-PB

RANDAT.DIA

After the Bootstrap Loader is loaded into memory it
may be checked as follows:
\.

Set the SWITCH REGISTER to 37744 (address of first word in the Bootstrap Loader).

Press LOAD ADDRESS.

Depress EXAMINE and observe the contents of the memory location on the ADDRESS/DATA lights. It should be 016701
for location 37744.

To observe the next location. depress EXAMINE again.

Continue to depress EXAMINE until all
memory locations in the Bootstrap Loader
have been checked.

These diagnostic programs are stored in user are.
2,12 and must be transmitted to the VT20 to h
tested using the VTLOAD Program. The diagnostic

After the Bootstrap Loader is reloaded. repeat the
loading procedure in Paragraph 8.7.

8-7

are linked to the Absolute Loader so only a one pass
load is required to transfer these programs. To transfer a VT20 Diagnostic Program from the PDP-I1I45
to the PDP-II/05 of the VT20 to be tested, proceed
as follows:

will be printed at the terminal. Now type:
MCR> VTL<CR>
and the terminal will respond with:
VTL>

l. Perform step I of the procedure to reload
the VT20 from the PDP-I1I45 MCR console (Paragraph 8.7).

Now type:
VTL>VTx:/NR = [2.I2]FILE.DIA <CR>
where:

2. Ensure that the LA30 is in the MCR mode:
if not. type:

x is a number 0, 2, 4. or. 6 for the VT20
unit number.

INR is a switch to suppress the rebooting
ofVTLOG.

The message:
FILENAME is one of the diagnostics
named in Table 8-2.

MCR>

_________

8-8

_ _ _ _ _ _ _ _ __

CHAPTER
RECOVERY PROCEDUR1
9.1

SOFTWARE RECOVERY PROCEDURES

9.1.5 Manual Task Aborts
It may become necessary to manually stop a task, I
ther because it appears to be hung, or to correct:
operational error. To accomplish this, type:

9.1.1 Recovery from System Crashes
If the Typeset system crashes it normally prints the
message:

MCR>ABO taskname
MCR> REQ taskname

CRASH -- CONT. WITH SCRATCH ON DECTAPE UNIT 7
If the system is equiped with a DECtape drive:
I.

Mount a scratch DECtape on the drive.

Set WRITE ENABLE; unit 7, and REMOTE switches.

Press CONTINUE on the console.

Send tape te> DEC for analysis.

NOTE
For VTlO monitor tasks, VTxMON should
be aborted, but VTxLOG is requested when
you are ready to restart the task (x . = the
unit number).

When a spooler task is manually aborted and r~
tarted, processing automatically begins with the ne
task.

The DECtape drive should become active. After the
drive stops moving or if the system does not support
DECtape, refer to Paragraph 8.4 to restart the system.

To force a spooler task to discontinue processing tl
current file and go on to the next, use the OPR cor
mand Q/SP to find the number of the item beil
processed, and the JKI command to kill that itel
Processing automatically restarts on the next task.

9.1.2 Recovery from System Hangs
If the MCR console does not respond to
<CTRLlC> and production through the system
seems to have come to a standstill, the system is
probably hung. Depress HALT and then refer to
Paragraph 8.4 to restart the system.

9.1.6 Running Verify
If an installation consistently gets DISK FULL errol
the System Manager should keep track of the numb
of free blocks on the system disk and delete til
when this number goes under 500. This is accOI
plished. by typing <CTRLlC> on the MCR conso
When the system responds with MCR> type:

9.1.3 Recovery from VTlO Hangs
Refer to Paragraphs 8.6 through 8.8 for a description
of VT20 restart procedures.

MCR>REQ VERIFY<ALT>
VER>SY:/FR<CR>

9.1.4 Task Aborts
If a task aborts, a message prints out on the MCR
consdl~. Since the task is automatically requested, the
System Manager is not required to do anything when
this message occurs. Refer to Paragraph 4.6.1.1 for
more details.

Verify will then list the number of free blocks. '
return to MCR mode type:
< CTRLlZ > <CTRLlC>

9·1

9.1.7 Reporting Software Errors
Software Performance Reports forms (S.P.R.) may be
obtained from the Field Service Applications Engineer, or from any DEC office. When completed, these
reports should contain any and all useful information
pertaining to the so.ftware problem. Examples of output and listings should be attached to give a better
description of the problem. The report should then be
sent to your Regional Typeset Specialist.
9.2

4. Ensure that the power cable is connected.
9.2.4

Input/Output Errors

9.2.4.1 Input-Readers
Acceptance of an input take by the system (i.e.. a
'good' filename) is indicated by a short pause in reading after the first few inches of the take. If a bad
filename is read, no pause will occur and the tape
will pass straight through the reader, the data being
ignored by the system. If this occurs. remove the tape
and check for a mispunched filename, dirt or chad
obscuring the data holes or bad registration of the
feed holes (see Paragraph 11.2). If anything wrong is
found, correct it and read the tape in again. Ensure
that the tape guides are properly adjusted for sixlevel tapes and the switch behind the reader is in the
six-level position. If nothing wrong is found or the
tape is rejected again. process the tape through another reader. If this is now accepted and continual
trouble is experienced with the first reader, take it
out of service and notify your local Field Service Office. If problems are encountered with all readers,
and cannot be isolated to bad registration. out-of-spec
tape etc., notify your local Field Service Office.

HARDWARE RECOVERY PROCEDURES

9.2.1 . Introduction
There are many symptoms that may appear due to
hardware failures. Some of the symptoms are too
complex to be easily isolated; this section describes
some of the basic problem areas and the possible recovery procedure.
9.2.2 Line Printer
The Line Printer recovery procedures are as follows:
1. Ensure that power is on and power cable is
connected.
2. Ensure ON LINE/OFF LINE is set to ON
LINE.
3. Ensure that an adequate supply of paper is
installed correctly (see Paragraph 10.2)

9.2.4.2 Input-VT20s
If text and/or commands entered via the ASCII keyboard are displayed as garbage on the screen, at a
convenient time, reload the VT20 (Paragraph 8.5) to
see if this will clear up the problem. If reloading does
not solve the problem, discontinue using the term inal(s) and notify your local Field Service Office. If all
terminals are giving problems, a restart of the system
may first be attempted before notifying your local office.

9.2.3 LA30
The LA30 recovery procedures are as follows:
1.

Set MODE switch to ON LINE and BAUD
RATE to correct rate for your system.

If the keys are inactive (no response when a
key is depressed), type:
<CTRLlC>
and the terminal should respond with:

If text brought to the screen while editing is garbage,
at a convenient time, reload the VT20 (Paragraph
8.5). If this does not solve the problem, discontinue
using the terminal(s) and inform your local Field Service Office. If all terminals are affected, replace the
system disk and/or restart. the system.

MCR>
at this time, you should. be able to type
commands. If not perform the following
steps:

9.2.4.3 Output-Paper Tape
If bad output from the photocomposition machines is
found, determine first if the problem can be isolated

2. Set CB 1 and CB2 at rear of LA30 to ON
·and verify that READY indicator is lit.

9-2

to one photocomp machine and/or one paper-tape
punch. If the former, reload the program in the photocomp machine (where applicable) and try again. If
bad output is due to one punch only, discontinue us~
ing the punch and notify your local Field Service Office. The isolation is performed by taking two or
three paper tapes from each punch and running them
on all photocomps. An alternative isolation method is
to punch one file out twice on each punch; then hold
the tapes together and compare for missing or extra
data holes. Isolate the bad punch if found and remove from service.

9.3.1 Hardware Backup Units
Table 9-1 shows the hardware components, backup
device used, and procedures in the event of a hardware failure.

9.2.4.4 Output-On-Line Interface
Determine which photocomp machine is glvmg the
problem. Determine whether it is the photocomp machine or LPDll/LPCOI by interchanging the LPCOI
to photocomp machine cable between two machines.
If the LPOl1lLPCOI is found to be a fault, remove
from service and notify your local Field Service Office.

9.3.2 Data Backup
The system and disk pack file structures are designed
to reduce the possibility of losing stories entered into
the system; Crashes and system failures which cause
the loss of stories in the system will be very rare. If
they occur, work still in the system will have to be reentered either manually, or by use of the optional
Fail-Safe magtape feature.

9.3 BACKUP SYSTEMS
For maximum protection against extended periods of
downtime or system failure at critical times, two similarly configured systems are recommended. The prime
system to be used for production, while the second
system may be used for other functions, such as Business Data. Processing, or a dedicated editorial system.

Table 9-1
Hardware Backup Devices And Procedures

Failure Occurs on

Back-up Device

Procedures and Comments

11145 core memory, RFll,
RSll, RPII-C, LA30,
PA6II-C, RP03 system

Second System

Move both RP03 diskpacks to the second system.
Switch VT20s and photocomps to the second system.
Restart system.

VT20 (or OLlIs), readers,
punches, photocomp interfaces

Additional devices

Normally these devices will be backed up by having
multiple devices available.

LPll

Either transfer to the second system or eliminate hard
copy.

Class Ad RP03

Either transfer to the second system or only process
text and ClassAd input. Wait until unit is running
and then insert ads.

TUlO/TUll Magtape

Not essential to operation.

9-3

Formats, Exception Word Dictionary, and advance
material are backed up if the standard operating procedures are followed. This is accomplished by copying
the system pack onto a reserve disk. In addition.
copying the updated CLASS AD disk provides
backup for this data base.

In the event that the classified disk crashes. the reserve (updated) classified disk and the system disk
are put on either the primary system or the backup
system' and all new ads for the day are transferred
from the system disk. This procedure will allow complete system backup in minimum time.

Generation of next day's classified section is accomplished by reading ads into the storage and edit disk
and after editing, transferring the ads into the classified disk. Transferring the ads into the classified disk
does not kill .the files on the system disk. Therefore.
all ads are stored both on the system disk and the
classified' disk.

9.3.3 Software Backup
Copying the system pack provides complete software
redundancy. Several copies of this disk are recommended.

CHAPTER 10
TYPESET SYSTEM EQUIPMENT OPERATION
10.2 LPll PAPER INSTALLATION
The following procedure should be used when loading paper in the line printer:

This chapter gives procedures for system operation
such as loading tape punches with paper tape, reloading line printer with paper, etc.

10.1 RELOADING THE TAPE PUNCHES
The supply of paper tape in each tape punch is replenished as follows:
I.

Remove the tape punch from service by
setting the control switch on the top to
OFF.
Tear the paper tape close to the feed switch;
remove the tape spool.

Load the tape spool and remount it on the
tape punch.

Set the control switch to CONTINUOUS
and clear the remaining paper tape from the
tape channel by depressing the tape feed
switch.

NOTE
Do not use the motor ON/OFF
switch on the side of the punch to run
the motor.

Open front door of cabinet to gain access to
maintenance panel and turn main ac power
switch on. Verify that control panel POWER
indicator lights.

Lift control panel TOP OF FORM switch
and release to move tractors to correct loading position.

Open the drum gate by moving the drum
gate latch knob to the left and up. Swing
drum gate open.

Adjust right-hand tractor paper width adjustment for proper paper width by loosening the set screw on the 80-column model or
by using the easy release mechanism on the
120-column model. Make certain that the
right-hand tractor is tightened in place after
it is adjusted.

Open spring-loaded pressure plates on both
tractors.

Load paper so that a perforation is pointed
to by the two red arrows (top-of-form indicators). Paper should lie smoothly between
tractors without wrinkling or tearing the
feed holes.

Thread the paper tape through the punch as
directed in Bulletin 215B.

Start the tape by depressing the tape feed
switch and pulling the tape gently, if necessary.

Set the control switch to AVAILABLE.

7. Close spring-loaded pressure plates on both
tractors.

NOTE
The tape punch is not returned to service until the control switch is set to
AVAILABLE.

8. Adjust the COPIES CONTROL lever to the
number of copies to be made. For example,
set to 1-2 for single forms, set to 5-6 for sixpart forms.

10-1

Close drum gate and lock into position with
drum gate latch. After approximately 10 seconds, the control panel READY indicator
should light. If it does not, check to see if
any error is indicated. An error is indicated
if one of the following lights is on: DRUM
GATE, PAPER FAULT, or PRINT INHIBIT.

When removing the pack or cartridge from
the cabinet, it should be put in the drive
immediately after removing it from the plastic bag. If there is a pack or cartridge in the
drive, it should be put into the plastic bag
immediately after verifying that the access
door is tightly closed.

Never touch the disk surface with bare
hands.

Do not attempt to clean the disk surface or
the inside of the diskpack or cartridge yourself. Your field office can recommend a
cleaning service. The only way to prevent
contamination of the diskpacks and a possible head crash is to exercise extreme care in
handling packs. together with sensible cleanliness of the computer room. The recommended periodic preventive maintenance
found in the disk maintenance manual
should be followed.

At no time should the disk be carried in the
trunk of one's car. The trunk is too dirty
and the shock from the ride can cause it to
move around inside the shell and chew up
the retainer button. Always carry it on the
front seat of the car.

10. Lift TOP OF FORM switch several times to
ensure that paper is feeding properly.
11. Set system to on-line mode by lifting ON
LINE/OFF Ll,NE switch and verifying that
ON LINE indicator lights. At this point,
printed matter can be aligned with the pa~
per lines by rotating the paper vertical adjustment knob.

10.3 DISKPACK AND CARTRIDGE HANDLING
All Typeset-II disk users should be familiar with the
following procedures for disk pack and cartridge handling:
.t"

Diskpacks should be stored in clean cabinets
when not in the drive. Each disk should
have its own shelf or compartment. Packs
should be stored in a horizontal position;
however, packs should never be stacked one
on top of another in a horizontal position.
RK05 disk cartridges can be stored in a vertical or horizontal position.

Before storing the pack or cartridge, the access door should be closed tightly; the pack
or cartridge should be enclos' d in the plastic·
bag that comes with the diskpack.

The cartridge should be handled only by the
front to rear axis, never on the side. If it is
grabbed by the side, which has the air vent,
it is:

The head assembly in a disk drive actually flies closer
than a fingerprint smudge or large smoke particle. A
buildup of dirt particles on a disk head is called oxide buildup. This oxide buildup causes improper head
flight which may cause various types of problems in
your Graphic Arts system and can lead to CAT ASTROPHIC DESTRUCTION OF HEADS AND
DISK.
CAUTION

Possible to break vent loose if plastic
rivets are used.

Since vent is flexible steel, it may
come in contact with disk surface and
cause a scratch.

Do not attempt to use a noisy diskpack,
cartridge or drive unit. If either drive emits
a noise when it is running, shut the system
down and use the backup typesetting system with a copy of the. diskpack to continue processing. Do not attempt to remove
the diskpack from th~ noisy drive or interchange the diskpacks in any way. A damaged disk pack could damage the other
drive; conversely, a damaged drive could
damage another diskpack.

10-2

CHAPTER 11
PREVENTIVE MAINTENANCE

11.1 COMPUTER AIR FILTER
Inspect the air filters once a month. If a filter is dirty.
remove it. clean it with soap and water. dry it thoroughly. and re-install it.

11.3 TAPE PUNCHES
Empty the chad box on each tape punch at the beginning of each shift before perforating any tape. Do
not allow chad accumulation to block the flow from
the chad chute.

11.2 TAPE READERS
Clean each tape reader at the beginning of each shift
before processing any tape. Limit daily cleaning to
the removal of tape fuzz and dust from the condensing lens and phototransistor apertures.

Thoroughly clean each tape punch once a week. Remove all tape chaf. chad. and dust from the area
around the punch block and the tape-feed ratchet
wheel. Use a firm brush and compressed air to clean
this area.

Thoroughly clean the interior of each reader weekly
as follows:
I.

Turn computer POWER key OFF (counterclockwise ).

Remove the knob from the tape spring arm.

11.4 PAPER TAPE SPECIFICATIONS
The chemical and optical properties of the paper tape
used with the Typeset-II System affect both the life
expectancy of the tape punches and the accuracy of
the tape readers. The recommended paper tape specifications are listed in Table 11-2. Any paper tape that
conforms to these specifications can be used in both
the tape punches and the tape readers without
adversely affecting their operation. Avoid changes in
tape color and extreme changes in translucence. Both
properties affect the sensitivity adjustment of the tape
readers.

CAUTION
Do not remove the cover from the
chassis unless the power is turned off.
This action can damage the tape
reader.
3.

11.5 DECTAPE TRANSPORTS
Remove the DECtape from the DECtape transport
and clean each transport once a week to remove accumulated tape emulsion. oxide particles. and dust
from the tape guide and the read/write head assemble. Use a camel hair brush to remove dust. Use
magnetic tape head solvent and a Q-tip to remove
oxide particles and tape emulsion from tape guide
and head assembly.

Pull the cover forward halfway. tilt it upward 45 degrees. and remove it from the
chassis.

CAUTION
Do not disturb the optical alignment
of the reader lamp or condensing lens.

Remove accumulated tape fuzz and dust
from the inside of the cover. the reader
lamp. the condensing lens. the sprocket
wheel. the tape hold-down bracket. and the
tape path guide. Use a camel hair brllsh to
clean the parts.

11.6 LINE PRINTER
Refer to Maintenance Manual (DEC-ll-HMFLA-AD) for cleaning, ribbon installation. paper loading,
and routine preventive maintenance instructions. The
line printer does not require any lubrication.

11·1

Table 11-1
Preventive Maintenance Checklist for Typeset-II Systems

Computer

VT20
Terminal

Daily

None

Weekly

Monthly

DECtape
Transports

DECdisk

Line Printer

Check chad box;
empty if necessary

None

Qean reader lamp
sprocket wheel,
condensing lens,
tape hold down
bracket, tape path
guide, and cover
interior.

Qean area around
punch block and
tape feed ratchet
wheel.

Qean tape guide
and read/write
head assembly. *

None

Inspect and
clean*

None

Inspect and
clean air
ftlter.*

None

Tape Readers

Tape Punches

None

Clean phototransistor
apertures and condensing lens.

None

Inspect and
clean air
ftlter.*

Inspect
and clean
air ftlter
(see VT20
User's Guide)

Lubricate as
directed in
Bulletin 215B,
Section 5.

Visually inspect
program tape for
translucent areas,
streaks, or smears
that indicate wear
or damage. Inspect
during program
loading.
---

_ .. _-

(*Maintenance intervals can be increased or decreased, as necessary, to suit the environment of the equipment. Consult your Dec Field Service Representative.

11.7 DECDISK AIR FILTER
Refer to Maintenance Manual (DEC-ll-HRFC-D)
for inspection and cleaning instructions.
Table 11-2
Paper Tape Specifications

Characteristic

Property

Specification

Oil content

6% minimum
12% maximum

Uniformly impregwith
nated
a
lightly
refined.
parafin-base. lightgrade lubricating
oil that is light in
color.

Translucence

32% to 28%
maximum

Maximum transmission of incident
light through the
paper limited by
combined oil content and paper
opacity.

General
quality

Standard grade
contains
less
than 1% ash
and .04% grit

Color

Solid

Completely free of
slime spots. pin
holes. translucent
spots. holes. tears.
wrinkles. creases.
and excess lint.
fuzz. or dust. Consistently use the
same color.

11-3

APPENDIX A

GLOSSARY

Definition

Term
algorithm

A set of well-defined operations performed in a prescribed sequence for the
solution of a particular set of problems.

alphanumeric

Pertains to a character set that contains only the 26 letters and 10 numerals.

ASCII

The abbreviation for American Standard Code for Information Interchange.
The internal code used by Typeset-II to store text.

asynchronous

Pertains to operations that do not occur in any particular time sequence.

auxiliary storage

Devices that supplement the storage of core memory such as disk, DECtape,
or magtape.

background processing

The automatic execution of lower priority computer programs when higher
priority programs are not using the system resources.

binary

Pertains to the number system with a radix of two.

binary code

A code that makes use of exactly two distinct characters, 0 and 1.

bit

A binary digit. In the PDP-II computer, each word is composed of 16 bits.

bootstrap

A technique or device designed to start up operations from an input device.

bug

A mistake in a program which causes erroneous results.

central processor unit

The unit of a computing system that includes the circuits controlling the
interpretation and execution of instructions.

character

A single letter, numeral, or symbol used to represent information.

clear

To zero the contents of a storage location.

command

A user order to a computer system, usually given through a terminal.

console

An external panel on the computer or peripheral where controls and
indicators are available for manual monitoring and operating of the device.

A-I

data

A general term used to denote any or all facts, numbers, letters, and symbols.
It connotes basic elements of information which may be processed by a
computer.

debug

To detect, locate, and correct mistakes in a program.

delimiter

A character that separates and organizes elements of data.

digital computer

A device that performs sequences of arithmetic and logical operations on
discrete data.

directory device

A device (such as disk) which is partitioned by software into several distinct
files. A directory of these files is maintained on the device to locate the files.

downtime

The time interval during which a device is inoperative.

dump

To copy the contents of all or part of core memory, usually onto an external
storage medium.

execute

To carry out an instruction or run a program on the computer.

executive

The master control program that observes, supervises, controls, or verifies the
operation of a system.

external storage

See auxiliary storage.

file

A collection of related records treated as a unit.

file name

Alphanumeric characters used to identify a particular file.

file name extension

A short appendage to the file name used to identify the type of data in the
file.

file name version

An appendage to the file name and extension, which follows the extension,
used to indicate that a file has been updated. Each time a file is edited, a new
version number is assigned to the edited file; thus, the file with the largest
version number is the latest copy of a story.

file structured device

See directory device.

flowchart

A graphical representation of an algorithm.

format

The arrangement of data.

full duplex

Describes a communications channel
independent transmission and reception.

half duplex

Describes a communications channel capable of transmission and/or
reception, but not both simultaneously.

hardware

Physical equipment, e.g., mechanical or electrical devices.

A-2

capable

of simultaneous and

initialize

To set counters, switches, and addresses to zero or other starting values at the
beginning of a computer routine.

input

The transferring of data from auxiliary storage into the internal storage of the
computer.

instruction

A statement that specifies an operation and the values or location of the
operand.

leader

The blank section at the beginning of the tape.

machine code

A numeric code expressing operations built into the hardware.

macro instruction

An instruction in a source language that is equivalent to a specified sequence
of machine instructions.

mass storage

See auxiliary storage.

memory

The alterable storage in a computer.

memory protection

A method of preventing the contents of some part of main memory from
being destroyed or altered.

monitor

See executive.

multiprocessing'

Utilization of several computers or processors to logically or functionally
divide jobs or processes, and to execute them simultaneously.

multiprogramming

Pertains to the execution of two or more programs in core at the same time;
execution cycles between programs.

off-line

Pertains to equipment or devices not under direct control of the computer.

on-line

Pertains to equipment or devices under direct control of the computer.

output

Information transferred from the internal storage of a computer to output
devices or auxiliary storage.

parity

A method of checking the correctness of binary data.

password

An alphanumeric code used to validate access to the system.

program

A complete sequence of instructions and routines necessary to solve a
particular problem.

queue

A waiting list. In Typeset-II, list of takes to be operated on (e.g., Punch
queue, J and H queue).

radix

The base of a number system.

random access

A storage device in which the addressability of data is effectively independent
of the location of the data, e.g., disk.

A-3

read

To transfer information from an input device to core memory.

re-al-time

Pertains to computation performed while the related physical process is
taking place so that results of the computation can be used in guiding the
physical process.

record

A collection of related items of data treated as a unit.

RSX-llD

A hardware-software complex which is the base for development of real-time
systems such as Typeset-Ii.

serial access

A storage device in which data can only be addressed sequentially, e.g., line
printer, paper tape.

software

The collection of programs and routines associated with a computer.

spooling

MOving data from one device to another through the use of queues.

storage device

A device in which data can be entered, retained, and retrieved.

string

A connected sequence of entities such as characters in a command string.

synchronous

Pertains to operations that occur in a particular time sequence.

system

A combination of software and hardware which performs a speCific
processing operation.

take

A job that Typeset-II will process as a unit from input to output.

task

See program.

terminal

A peripheral device in a system through which data can enter or leave the
computer.

timesharing

A method of allocating central processor time and other computer resources
to multiple users so that the computer, in effect, processes a number of
programs simultaneously.

UIC

A string of two numbers that represent an area of a disk.

user

Any person interacting with a computer system.

write

To transfer information from core memory to an output device, a peripheral
device, or auxiliary storage.

APPENDIX B
COMMAND SUMMARY

A Typeset-II file is defined by a general definition:

FILE

EXT =

file type with up to 3 alphanumeric
characters (default = command dependent).

VER

version number (default = latest version).

DEV:[G.U]FILENAME.EXT:VER

where:

device and unit number (default
system disk unit 0).

[G.U] =

group-and-user number (default
logged in. user).

DEV

Wherever FILE appears in a Typeset-II command.
this information must be inserted. That is. the format
of the command is simply stated:
©P FILE<CR>
instead of:

FILE

B.l

file name with up to 9 alphanumeric
characters.

QUEUE COMMANDS

COMMAND

FORM

USE

Activate

Activates the queue specified in the command.

Deactivate

Deactivates the queue specified in the command.

Exit

©Q/EX<CR>

Causes the QUEUE MANAGER to exit. This
command is used to shut down the system at
the end of the day.

Kill Item

Remove item number x from the queue
named in the command.

Modify Item

Assign a new priority. y. to item number x in
the queue named in the command.

B-1

B.2

QUEUE LIST COMMANDS

COMMAND

FORM

USE

Abort

©Q/AB<CR>

List abort reports.

All Users

©Q/A<CR>

List items queued by everyone in the system.

Beginning

©Q/B<CR>

List items that have been queued from the
beginning of the day.

Done

©Q/D<CR>

List items that have been finished.

Error

©Q/E<CR>

List items that resulted in an error.

Format

©Q/F<CR>

List items with the last format used.

Item Numbers

©Q/I:x:y<CR>

List item numbers x through y.

Last Item

©Q/L<CR>

List the last item queued.

Line Printer

©Q/LP<CR>

This switch. when added to a list command
will cause the list to be printed on the line
printer.

Queue

List items assigned to the queue named in
the command.

Queues

©Q/QU<CR>

List all queue names.

Spoolers

©Q/SP<CR>

List all spooler names.

Status

©Q/ST<CR>

List items with timing information.

System

©Q/SY<CR>

List QUEUE MANAGER data.

Waiting

~Q/W<CR>

List items that are not completed.

B·2

-------~---.--~

....----=---=.

=.-==~~--========~

-===------

B.3

OUTPUT COMMANDS

COMMAND

USE

FORM

©J FILE<CR>

Processes the file named in the command
through J and H. The file named in the command will be directed to the JH queue.

©JC FILE<CR>

Processes the file named in the command
through J and H and generates a .SET file to
be sent to CLASS AD as an insert.

©JP FILE<CR>

Processes the file named in the command
through J and H and generates a .SET and a
.PRF file. The .PRF file is sent to the line
printer.

©JH FILE<CR>

Processes the file named in the command
through J and H and generates a .PRF file
and .SET file.

©JS FILE<CR>

Processes the file named in the command
through J and H and generates only a .SET
file to be output on the photo composition
machine.

©JT FILE<CR>

Processes the file named in the command
through J and H and generates only a .SET
file to be output on the paper tape punch.

©P FILE<CR>

Used to request a line printer copy of a file
from any storage device. This command
causes the named file to be placed in the LP
(Line Printer) queue.

Punch

©PU FILE<CR>

Used to output files to paper tape punches.
This command causes the named file to be
placed in the PP (Punch) queue.

Queue

Direct a file to the queue named in the command. This command is used when a file
must be directed to a specific unit number.

Set

©S FILE<CR>

Used to output· files to an on-line photocomposition machine. This command causes the
named file to be placed in the PC (Photocomposition) queue.

Justify

B-3

B.3.1 Justify Command Switches

SWITCH

USE

SWITCH
IDE

Deletes the file after the spooler has
completed the indicated operation.

IHP

Generates a .PRF file but does not
print it on

IHS

Does not queue .SET file.

B.4

USE

INP

Does not generate a .PRF file.

10K

Sends file to specified spooler even if
there has been a warning level error.

IPF

Generates a .PRF file and prints it on
line printer.

IPR:x

Assign a priority for the operation
where x is a number from 0 to 255.

UTILITY COMMANDS
FORM

USE

Append

Connect two or more files together to form
one continuous file. FILEA must exist in the
system before the append command is used.

Copy

Create FILEA from FILEB: both files exist
in the user's data base area and will appear
in the directory list.

Delete

©DE FILE<CR>

Deletes file named from the user's area. The
version number must be specified or the *
(wild card) must be used.