Digital PDFs

AA-H607A-TA

March 1979

372 pages

Original

9.5MB

Document:	0s/8 System Reference Manual
Order Number:	AA-H607A-TA
Revision:
Pages:	372
Original Filename:	http://bitsavers.org/pdf/dec/pdp8/os8/AA-H607A-TA_OS8_V3D_sysMan.pdf

OCR Text

08/8
System Reference Manual
Order No. AA-H607A-TA

ABSTRACT

This document describes 05/8 system conventions,
keyboard commands, and utility programs.

SUPERSESSION/UPDATE INFORMATION:

This manual supersedes sections of 05/8 Handbook
(DEC-S8-0SHBA-A-DI and the 05/8 Handbook
Update (DEC-S8-0SHBA-A-DN41.

OPERATING SYSTEM AND VERSION:

OS/8V3D

To order additional copies of this document, contact the Software Distribution
Center, Digital Equipment Corporation, Maynard, Massachusetts 01754

digital equipment corporation · maynard, massachusetts

First Printing, March 1979

The information in this document is subject to change without notice
and should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may only be used or copied in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

The postage-prepaid READER'S COMMENTS form on the last page of this
document requests the user's critical evaluation to assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

DIGITAL
DEC
PDP
DECUS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM
ASSIST-11
VAX
DEC net
DATATRIEVE

DECsystem-10
DECtape
DIBOL
EDUSYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8
DECSYSTEM-20
RTS-8
VMS
lAS
TRAX

MASSBUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11
TMS-11
ITPS-10
SBI
PDT

CONTENTS

Page
xiii

DOCUMENTATION SET FOR OS/8
CHAPTER

CHAPTER

OVERVIEW

1-1

1.1
1.2
1.3
1.4

INTRODUCTION TO OS/8
OS/8 I/O DEVICES
HARDWARE CONFIGURATIONS
SYSTEM SOFTWARE COMPONENTS

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

SYSTEM CONVENTIONS

2-1

2.1
2.2
2.3

PERMANENT DEVICE NAMES
FILE NAMES AND EXTENSIONS
UNITS OF STORAGE

2-1
2-2
2-4

OS/8 KEYBOARD COMMANDS

3-1

3.1
3.2
3.3
3.3.1
3.3.1.1

INTRODUCTION
COMMAND FORMAT
COMMAND AND FILE OPTIONS
Command Options
The Slash Construction -- Single-Letter
Options
The Parenthesis Construction -- Mu1tip1eLetter Options
The Equal Sign Construction -- Octal
Number Options
File Options
Additional Switch Options -- the Dash
Construction
COMMANDS THAT REMEMBER FILE SPECIFICATIONS
USING WILDCARDS
Wildcards in Input Filenames
Wildcards in ,Output Specifications
Warnings and Suggestions
INDIRECT COMMANDS
USING DEFAULTS
GETTING HELP -- THE HELP COMMAND
ENTERING A COMMAND LINE -- CORRECTING AND
PREVENTING ERRORS
ASSIGN
Canceling a Logical Name
Checking for Duplicate Names
BACKSPACE
BASIC
BOOT
CCL
COMPARE
COMPARE Output
COMPARE Options

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

3.3.1.2
3.3.1.3
3.3.2
3.3.3
3.4
3.5
3.5.1
3.5.2
3.5.3
3.6
3.7
3.8
3.9
3.10
3.10.1
3.10.2
3.11
3.12
3.13
3.14
3.15
3.15.1
3.15.2

iii

3-5
3-5
3-5
3-5
3-6
3-6
- 3-7
3-7
3-7
3-8
3-8
3-9
3-9
3-10
3-11
3-11
3-11
3-12
3-13
3-14
3-15
3-16
3-16
3-17

CONTENTS (Cont • )

Page
3.16
3.16.1
3.16.2
3.16.2.1
3.16.2.2
3.16.2.3
3.17
3.17.1
3.17.2
3.17.3
3.17.4
3.17.5
3.18
3.19
3.19.1
3.20
3.21
3.22
3.22.1
3.22.2
3.22.3
3.23
3.23.1
3.23.2
3.24
3.25
3.25.1
3.26
3.27
3.28
3.29
3.30
3.30.1
3.31
3.32
3.33
3.33.1
3.33.2
3.34
3.35
3.36
3.37
3.38
3.39
3.40
3.41
3.41.1
3.42
3.43
3.44
3.45
3.45.1
3.46
3.47
3.48
3.49
3.50

COMPILE
COMPILE Input
COMPILE Output
Output File 1 -- the Binary Code
Output File 2 -- the Listing File
COMPILE Options and Errors
COpy
COpy Input
COpy Output
COpy Terminal Display
Predeletion and Postdeletion
COpy Options
CREATE
CREF
CREF Options
DATE
DEASSIGN
DELETE
The Conditional DELETE
DELETE Terminal Display
DELETE Options
DIRECT
DIRECT Output
DIRECT Options
DUPLICATE
EDIT
Recalling Arguments
EOF
EXECUTE
GET
HELP
LIST
LIST Options
LOAD
t-1AKE
MAP

MAP Output
MAP Options
MEMORY
MUNG
ODT
PAL

PRINT
PUNCH
R

RENAME
RENAME Options
RES
REWIND
RUN
SAVE
The Job Status Word
SET
SKIP
START
SQUISH
SUBMIT

3-19
3-19
3-20
3-20
3-21
3-21
3-22
3-22
3-22
3-22
3-23
3-23
3-24
3-25
3-25
3-26
3-27
3-28
3-28
3-29
3-29
3-30
3-30
3-30
3-32
3-33
3-33
3-34
3-35
3-36
3-37
3-38
3-38
3-39
3-40
3-41
3-41
3-41
3-43
3-44
3-45
3-46
3-47
3-48
3-49
3-50
3-50
3-51
3-52
3-53
3-54
3-55
3-56
3-57
3-58
3-59
3-60

CONTENTS (Cont.)

Page

CHAPTER

3.51
3.52
3.53
3.53.1
3.54
3.55
3.56
3.57

TECO
TERMINATE
TYPE
TYPE Options
UA, UB, and UC
UNLOAD
VERSION
ZERO

3-61
3-62
3-63
3-63
3-64
3-65
3-66
3-67

THE OS/8 SYMBOLIC EDITOR

4-1

4.1
4.2
4.3
4.3.1
4.3.2
4.3.2.1
4.3.2.2
4.3.2.3
4.3.2.4
4.3.2.5
4.3.2.6
4.4
4.4.1
4.4.2
4.4.2.1
4.4.2.2
4.5
4.6
4.7

INTRODUCTION
CALLING THE EDITOR
MODES OF OPERATION
Text Mode
Command Mode
Input Commands
Listing commands
Output commands
Editing Commands
Search Commands
Special Command Mode Characters
SEARCHING A TEXT
Single-Character Search -- the S Command
The Character String Search
Intrabuffer String Search
Interbuffer String Search -- J Command
EDITOR OPTIONS
EDITOR ERROR MESSAGES
SUMMARY OF EDITOR COMMANDS AND SPECIAL
CHARACTERS

4-1
4-1
4-2
4-3
4-4
4-5
4-6
4-6
4-8
4-9
4-10
4-12
4-12
4-13
4-13
4-16
4-17
4-18

THE COMMAND DECODER

5-1

5.1
5.2
5.3

ENTERING I/O SPECIFICATIONS
COMMAND DECODER ERROR MESSAGES
THE CCL AND THE COMMAND DECODER

5-1
5-3
5-3

BATCH

6-1

6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.4
6.5
6.6
6.7

INTRODUCTION
BATCH PROCESSING UNDER OS/8
Input Files
Output Files
I/O Devices
Spooling
Entering File Specifications
BATCH MONITOR COMMANDS
Defining a BATCH Job
Using OS/8 Keyboard Commands
Using the Command Decoder
Additional Features
THE BATCH INPUT FILE
BATCH ERROR MESSAGES
RUNNING BATCH FROM PUNCHED CARDS
RESTRICTIONS UNDER OS/8 BATCH
BATCH DEMONSTRATION PROGRAM

6-1
6-1
6-2
6-2
6-2
6-2
6-2
6-4
6-4
6-5
6-6
6-6
6-7
6-9
6-11
6-12
6-13

6.8

4-19

CONTENTS (Cont.)

Page

6.12

LOADING AND SAVING BATCH
LOADING AND SAVING PROGRAMS FOR USE UNDER
BATCH
TRANSFERRING THE SYSTEM SOFTWARE FROM
CASSETTE TO THE SYSTEM DEVICE
RUNNING FORTRAN IV UNDER BATCH IN 32K

BITMAP

7-1

7.1
7.2
7.3
7.4

FILE AND DEVICE SPECIFICATIONS
BITMAP OUTPUT
BITMAP ERROR MESSAGES
ASSEMBLY INSTRUCTIONS

7-1
7-2
7-3
7-3

BOOT

8-1

8.1
8.2

BOOTING WITH BOOT
BOOT PRIORITIES

8-1
8-2

BUILD

9-1

9.1
9.1.1
9.1. 2
9.2
9.3
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.3.6
9.3.7
9.3.8
9.3.9
9.3.10
9.3.11
9.3.12
9.3.13
9.3.14
9.3.15
9.3.16
9.3.17
9.3.18
9.3.19
9.3.20
9.4
9.5
9.5.1
9.5.2
9.5.3
9.5.4
9.6

OS/8 DEVICE HANDLERS
Cassette Systems
Paper Tape Systems
CALLING AND USING BUILD
BUILD COMMANDS
The Hyphen Construction
PRINT
QLIST
LOAD
INSERT
DELETE
REPLACE
UNLOAD

9-1
9-3
9-3
9-6
9-7
9-8
9-8
9-9
9-9
9-10
9-11
9-12
9-13
9-13
9-14
9-15
9-15
9-16
9-16
9-17
9-17
9-17
9-17
9-18
9-19
9-20
9-21
9-22
9-22
9-23
9-24
9-25

CASSETTE AND MAGNETIC TAPE POSITIONER

6.9
6.10
6.11

CHAPTER

NAME

ALTER
EXAMINE
DSK
CORE
DCB
CTL
VERSION
SIZE
SYSTEM
BUILD
BOOTSTRAP
BUILD ERROR MESSAGES
BUILD DEVICE HANDLER FORMAT
Header Block
Descriptor Block
Breakdown of DCB Word
Entry Point Offset
CREATING A SYSTEM HANDLER

6-18
6-18
6-19
6-21

10-1

(CAMP)

CONTENTS (Cont.)

Page

CHAPTER

CFAPTER

CHAPTER

10.1
10.1.1
10.1. 2
10.1.3
10.1. 4
10.1. 5
10.1. 6
10.1. 7
10.2

CAMP COMMANDS
BACKSPACE Command
EOF Command
HELP Command
REWIND Command
SKIP Command
UNLOAD command
VERSION Command
CAMP ERROR MESSAGE SUMMARY

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

CROSS-REFERENCE PROGRAM (CREF)

11-1

11.1
11.1.1
11.1.2
11.2
11.3
11.4
11.5

CALLING AND USING CREF
CREF Options
Examples of CREF Usage
PSEUDO-OP HANDLING
INTERPRETING CREF OUTPUT
RESTRICTIONS
CREF ERROR MESSAGES

11-1
11-1
11-2
11-3
11-3
11-5
11-6

DIRECT

12-1

12.1
12.1.1
12.2
12.3

CALLING AND USING DIRECT
DIRECT options
DIRECT EXAMPLES
DIRECT ERROR MESSAGES

12-1
12-2
12-3
12-5

DECTAPE COpy AND FORMAT PROGRAMS

13-1

13.1
13.1.1
13.1.2
13.1.3
13.1.4
13 .2
13.2.1
13.2.2
13.2.3
13.3
13.3.1
13.4
13.4.1
13.4.2

DTFRMT
Loading Procedure
Using the Program
Error Messages
Details of DTFRMT Operation and storage
TDFRMT
Operating Procedures
Error Messages
Details of TDFRMT Operation and Storage
DTCOPY
Error Messages
TDCOPY
Error Messages
Details of Operation

13-1
13-1
13-1
13-3
13-4
13-5
13-5
13-7
13-8
13-10
13-11
13-12
13-13
13-15

DUMP

14-1

14.1
14.2
14.3

FORM FEEDS
ADDING THE DUMP HANDLER TO YOUR SYSTEM
FORMAT OF THE DUMP

14-2
14-2
14-2

EPIC

15-1

15.1
15.2
15.3
15.4
15.5

LOADING EPIC
RESTART PROCEDURE
PAPER TAPE FACILITY
COMMAND FORMAT
DEFAULT OPTIONS

15-1
15-2
15-2
15-2
15-3

vii

CONTENTS (Cont.)

Page

CHAPTER

lS.6
15.7
15.8
15.9
lS.9.1
lS.9.2
15.10
lS.ll
lS.12
lS.13
15.14

ERROR CONDITIONS
LOW SPEED I/O
DEVICE CODES
EDITING CAPABILITY
Initial Command Format
Editing Commands
COMPARE CAPABILITY
ERROR MESSAGES
PAPER TAPE FORMAT
LOADING EPIC FROM PAPER TAPE
EPIC ASSEMBLY INSTRUCTIONS

lS-4
15-4
15-4
15-5
15-5
15-5
15-8
lS-8
lS-10
lS-11
15-11

FILE-ORIENTED TRANSFER PROGRAM (FOTP)

16-1

16.1
16.1.1
16.1. 2
16.2
16.2.1
16.2.2
16.2.3
16.2.4
16.3
16.3.1
16.4

CALLING FOTP
Input Specifications
Output Specifications
USING FOTP
Additional FOTP Commands
Advantages of Predeletion
Advantages of Postdeletion
Control Characters
FOTP OPTIONS
Examples of FOTP Specification Commands
ERROR MESSAGES

16-1
16-1
16-3
16-3
16-5
16-7
16-7
16-7
16-7
16-10
16-11

FUTIL

17-1

17.1
17.1.1
17.1.2
17.1.3
17.1.4
17.1.S
17.1.6
17.2
17.2.1
17.3
17.3.1
17.3.1.1
17.3.1.2
17.3.1.3
17.3.2
17.3.2.1
17.3.2.2
17.3.2.3
17.3.2.4
17.3.2.5
17.3.2.6
17.3.2.7
17.3.2.8
17.3.2.9
17.3.3
17.3.3.1
17.3.3.2
17.3.4
17.3.4.1

INTRODUCTION
Special Characters Used in FUTIL
Running FUTIL
Access Method
Referencing Words on the Device
Numeric Item (or Numbers)
Errors and Error Messages
SINGLE-CHARACTER (ODT-LIKE) COMMANDS
Symbolic Output Formats
WORD-TYPE COMMANDS
Output Formats
DUMP
LIST
MODIFY
Search Limits
WORD (Search)
STRING (Search)
SMASK
SET
SHOW
FILE
WRITE
SCAN
REWIND
File Output
OPEN
CLOSE
Batch Operation
IF

17-1
17-1
17-2
17-3
17-5
17-6
17-7
17-7
17-9
17-11
17-12
17-13
17-13
17-14
17-15
17-16
17-17
17-18
17-18
17-19
17-20
17-22
17-22
17-22
17-23
17-23
17-24
17-24
17-24

viii

CONTENTS (Cont.)

Page
17.3.4.2
17.3.4.3
17.3.4.4
17.3.4.5
17.4
17.5
17.6
17.7
CHAPTER

CHAPTER

END
COMMENT
EXIT
EVAL
EXAMPLES
PROGRAM EXECUTION AND MEMORY ALLOCATION
COMMAND SUMMARY
SINGLE-CHARACTER COMMAND OUTPUT FORMAT
SUMMARY

17-24
17-25
17-25
17-25
17-26
17-33
17-34
17-35

MAGTAPE/CASSETTE PERIPHERAL INTERCHANGE
PROGRAM (MCPIP)

18-1

18.1
18.1.1
18.2

CALLING AND USING MCPIP
MCPIP Options
MCPIP ERROR MESSAGES

18-1
18-2
18-4

OCTAL DEBUGGING TECHNIQUE (ODT)

19-1

19.1
19.2
19.3
19.3.1
19.3.2
19.3.3
19.4
19.4.1
19.4.2
19.5
19.6
19.7

FEATURES
CALLING AND USING ODT
COMMANDS
Special Characters
Illegal Characters
Control Commands
ADDITIONAL TECHNIQUES
Current Location
Indirect References
ERRORS
PROGRAMMING NOTES SUMMARY
SUMMARY OF ODT COMMANDS

19-1
19-1
19-2
19-2
19-4
19-4
19-4
19-7
19-7
19-7
19-7
19-8

PERIPHERAL INTERCHANGE PROGRAM (PIP)

20-1

20.1
20.1.1
20.1. 2
20.2

20-1
20-1
20-6

20.3

CALLING AND USING PIP
PIP Options
Examples of PIP Specification Commands
ADDITIONAL INFORMATION WORDS IN FILE
DIRECTORIES
PIP ERROR MESSAGES

20-8
20-8

PIP10

21-1

21.1
21.2
21.3
21. 4
21.5

CALLING AND USING PIP10
HOW TO COpy LARGE FILES WITH PIP10 (SR)
PIP10 OPTIONS
PIP10 EXAMPLES
ERROR MESSAGES

21-1
21-2
21-2
21-3
21-3

RESOURCES (RESORC)

22-1

22.1
22.2
22.2.1
22.2.2
22.2.3
22.3

CALLING AND USING RESORC
RESORC OPTIONS
Fast Mode (IF Option)
Limited Mode (/L Option)
Extended Mode (/E Option)
RESORC ERROR MESSAGES

22-1
22-2
22-2
22-2
22-3
22-6

CONTENTS (Cont.)

Page
CHAPTER

RKLFMT DISK FORMATTER PROGRAM

23-1

23.1
23.2
23.2.1
23.2.2
23.3
23.4
23.5
23.6
23.7
23.7.1
23.7.2
23.7.3
23.7.4

RUNNING THE PROGRAM
STANDARD TEST PROCEDURES
RK05J Drive cartridge Mounting Procedure
RK05F Drive Setup Procedure
FORMAT PROGRAM
ERRORS
PROGRAM DESCRIPTION
CONTROL CHARACTERS
MISCELLANEOUS
Waiting Message
End of Pass
Errors
Location Changes

23-1
23-2
23-2
23-2
23-3
23-4
23-4
23-5
23-5
23-5
23-6
23-6
23-6

CHAPTER

RXCOPY PROGRAM

24-1

CHAPTER

SET PROGRAM

25-1

25.1
25.1.1
25.1. 2
25.1. 3
25.1. 4
25.1.5
25.1. 6
25.1.7
25.1. 8
25.1.9
25.1.10
25.1.11
25.1.12
25.1.13
25.1.14
25.2
25.2.1
25.3
25.3.1
25.3.2
25.4
25.4.1
25.4.2
25.4.3
25.5
25.5.1
25.5.2
25.5.3
25.5.4
25.5.5
25.6
25.6.1
25.6.2
25.6.3
25.6.4
25.6.5
25.6.6

TERMINAL ATTRIBUTES
Arrow
CODE n
COLumn n
ECHO
ESCape
FILL
FLAG
HEIGHT m
LC
PAGE
PAUSE n
SCOPE
TAB
WIDTH n
CARD READER ATTRIBUTES
CODE n
MAGNETIC TAPE ATTRIBUTES
PARITY x
FILES
SYSTEM ATTRIBUTES
INITIAL xxxxx
OS8
OS78
LINE PRINTER ATTRIBUTES
LA78
LA8A
LC
LV8E
WIDTH n
ANY DEVICE ATTRIBUTES
FILES
DVCode nn
LOCation n=m or LOCation n
READOnly
VERSION x
BLOCK h, LOCation n=m or BLOCK h, LOC n

25-3
25-3
25-3
25-4
25-4
25-4
25-5
25-5
25-5
25-6
25-6
25-6
25-7
25-7
25-7
25-8
25-8
25-8
25-8
25-8
25-9
25-9
25-9
25-9
25-10
25-10
25-10
25-10
25-10
25-11
25-11
25-11
25-12
25-12
25-13
25-13
25-13

CONTENTS (Cont.)

Page
CHAPTER

SRCCOM

26-1

26.1
26.2
26.3
26.4

SRCCOM ASSEMBLY INSTRUCTIONS
LOADING SRCCOM
SRCCOM OUTPUT
ERROR MESSAGES

26-1
26-1
26-2
26-4

APPENDIX A

CHARACTER CODES

A-I

APPENDIX B

LOADING PROCEDURES

B-1

INITIALIZING THE SYSTEM
LOADERS
Binary (BIN) Loader

B-1
B-1
B-6

APPENDIX C

OS/8 DEMONSTRATION RUN

C-l

APPENDIX D

OS/8 FILE NAME EXTENSIONS

D-l

APPENDIX E

OS/8 DEVICE HANDLERS

E-l

HIGH-SPEED READER/PUNCH
LOW-SPEED READER/PUNCH
TTY HANDLERS
LINE PRINTERS
VR12 SCOPE
CARD READER
DECTAPES
MAGNETIC TAPE
CASSETTES
BATCH HANDLER
DSK AND SYS

E-l
E-l
E-l
E-2
E-2
E-3
E-3
E-3
E-3
E-4
E-4

OBTAINING OS/8 PROGRAM VERSION NUMBERS

F-l

B.l
B.2
B.2.l

E.l
E.2
E.3
E.4
E.5
E.6
E.7
E.8
E.9
E.IO
E.ll
APPENDIX F

FIGURES
FIGURE

6-1
6-2
B-1
B-2
B-3
B-4

Sample BATCH Input File
Punched Card Input File
Loading the RIM Loader
Checking the RIM Loader
Loading the BIN Loader
Loading a Binary Tape Using BIN

6-7
6-12
B-4
B-5
B-7
B-9

TABLES
TABLE

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

Permanent Device Names
OS/8 File Name Extensions
Keyboard Monitor Error Messages
Switch Options
Editor Key Control Commands

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

CONTENT (Cont.)

Page
TABLES (Cont.)
TABLE

4-2
4-3
4-4
4-5
4-6
4-7
4-8
4-9
4-10
4-11
5-1
5-2
5-3
6-1
6-2
6-3
7-1
8-1
9-1
9-2
9-3
9-4
9-5
9-6

9-7
10-1
11-1
11-2
12-1
12-2
15-1
15-2
16-1
16-2
18-1
18-2
19-1
20-1
20-2
21-1
22-1
22-2
24-1
24-2
25-1
25-2
26-1
A-I
B-1
B-2

Editor Input Commands
Editor Listing Commands
Editor Output Commands
Editing Commands: Deletion and Alteration
Editor Search Commands
Editor Special Characters: Command Mode
Aborting Editor String Search Commands
Nonfatal Editor Error Messages
Editor Error Codes
Editor Command and Special Characters
Examples of Output to the Command Decoder
Examples of Input to the Command Decoder
Command Decoder Error Messages
Run-Time Options
BATCH Monitor Commands
BATCH Error Messages
Bitmap Options
BOOT Mnemonics
Standard DEC tape System Device Handlers
Standard Cassette System Device Handlers
Standard Paper Tape System Device Handlers
OS/8 Device Handlers
BUILD Editing Characters
BUILD Error Messages
DCB Word
CAMP Error Messages
CREF Options
CREF Error Messages
DIRECT Options
DIRECT Error Messages
EPIC Commands
EPIC Error Messages
FOTP Options
FOTP Error Messages
MCPIP Options
MCPIP Error Messages
ODT Command Summary
PIP Options
PIP Error Messages
PIPI0 Error Messages
RESORC Device Types
RESORC Error Messages
RXCOPY Options
RXCOPY Error Messages
SET Command Attributes
SET Error Messages
SRCCOM Run-Time Options
ASCII Character Set
RIM Loader for Low-Speed Reader
RIM Loader for High-Speed Reader

xii

4-5
4-6
4-7
4-9
4-10
4-10
4-17
4-18
4-19
4-19
5-1
5-2
5-3
6-3
6-5
6-9
7-2
8-2
9-2
9-3
9-3
9-4

9-7
9-20
9-23
10-5
11-2
11-7
12-2
12-5
15-6
15-9
16-8
16-12
18-2
18-4
19-8
20-1
20-8
21-4
22-3
22-6
24-1
24-2
25-1
25-2
26-2
A-I
B-2
B-3

DOCUMENTATION SET FOR OS/8

OS/8 SYSTEM GENERATION NOTES (AA-H606A-TA)
The System Generation Notes provide the information you need
to get a new OS/8 system running.
OS/8 SYSTEM REFERENCE MANUAL (AA-H607A-TA)
The System Reference
Manual
describes
OS/8
system
conventions, keyboard commands, and utility programs.
OS/8 TECO REFERENCE MANUAL (AA-H608A-TA)
The TECO Reference Manual describes the OS/8 version of this
character-oriented text editing and correcting program.
OS/8 LANGUAGE REFERENCE MANUAL (AA-H609A-TA)
The Language Reference Manual
describes all languages
supported by OS/8, including BASIC, FORTRAN IV, and the PAL8
assembly language.
OS/8 ERROR MESSAGES (AA-H610A-TA)
This manual lists in alphabetical order all error
generated by OS/8 system programs and languages.

xiii

messages

CHAPTER 1
OVERVIEW

1.1

INTRODUCTION TO 05/8

This manual describes the 05/8 keyboard commands, the 05/8 Editor, and
the 05/8 library of utility programs.
These commands and system
programs enable you to develop user-written programs in PAL8 assembly
language, BASIC, FORTRAN IV, and other languages available under 05/8.
The 05/8 library includes the following system programs.
BATCH
The BATCH monitor enables you to prepare a job on punched cards,
high-speed paper tape, or the system device and then leave it for
05/8 to run.
BITMAP
The BITMAP program produces a table to show the locations that
binary file occupies in memory.

BOOT
The BOOT program loads standard hardware bootstraps into memory.
BUILD
The BUILD program lets you alter the device configuration in your
system to insert new devices or add user-written handlers.
CAMP
The Cassette and Magnetic Tape Positioner program enables you
manipulate cassettes and magnetic tapes.

CREF
The Cross Reference Program produces a table in assembly listings
that enables you to locate references to symbols and literals.
DIRECT
The DIRECT program produces various types of directories.
DTFRMT, DTCOPY,TDFRMT, TDCOPY
These programs format and copy DECtapes.
DUMP
The DUMP program sends listings to the LP08 line printer.
EPIC
The Edit, Punch, and Compare program reads and punches
tapes, edits files, and compares files in any format.

paper

The File-Oriented Transfer Program
between file-structured devices.

files

FOTP

1-1

transfers

groups

OVERVIEW

FUTIL
The File Utility program enables you to examine
contents of mass storage devices.

and

modify

the

MCPIP
The Magtape/Cassette Peripheral Interchange
Program
file-transfer program for cassettes and magnetic tapes.

debug

ODT
The Octal Debugging Technique enables you to run
program by typing instructions at the keyboard.

and

PIP
The Peripheral Interchange Program transfers files
between
devices and provides file and directory maintenance functions.
PIPIO
This is a file-transfer program that reads and writes
DECtape files using a TC08 or TD8E DEC tape controller.

ASCII

RESORC
The RESORC program prints a listing of active device handlers.
RKLFMT
The RKLFMT program formats RKOS disks.
RXCOPY
The RXCOPY program copies diskettes.
SET
The SET program makes it possible for you to modify the operating
characteristics of OS/8.
SRCCOM
The Source Compare program compares two source files line by line
and prints the differences.

1.2

OS/8 I/O DEVICES

OS/8 provides device independence. You can write programs without
concern for specific I/O devices.
In running a program, you can
select the most effective I/O devices available. Furthermore, if the
system configuration is altered, you need not rewrite programs to take
advantage of the new configuration.
The OS/8 system controls the copying of data from any medium to any
other medium by means of subroutine calls to execute I/O routines.
Logical names can be assigned to devices within the system to enable
symbolic referencing of devices.
Variable-length I/O buffers can be specified by the user program.
Large buffers ensure efficient use of storage devices and a minimum of
time spent in data-transfer operations by minImIzIng disk and tape
motion. OS/8 takes full advantage of th~ RK8E disk pack for fast bulk
storage, yet full system services are possible with a single DECtape.

1-2

OVERVIEW
1.3

HARDWARE CONFIGURATIONS

The 05/8 system can operate with the following devices as
device.

the

system

TCOI/TC08 DECtape
LINCtape (PDP-12)
TD8E DECtape
DF32/RF08 disk
RK8E disk
RK8 disk
RXOI diskette
The term system device refers to the device on which the OS/8 system
resides and which it utilizes for system functions. Thus, DECtape
unit 0 is the system device for a DECtape-based system.
A nonsystem
device is any peripheral not specifically used for system functions,
such as LPT:, PTR:, DTA2:, etc.
TD8E DECtape can be used either with 12K words of core memory or
8K words of core memory and 2S6 words of Read-only-Memory (ROM).
If DF32 is the system device,
available.

least

64K

platters)

must

with
be

The minimum 05/8 configuration is a PDP-8 series computer with 8K
words of memory, one DECtape used as the system device, and a console
terminal. A multiple DECtape system performs appreciably faster than
a single DECtape system. The multiple DECtape system reduces DECtape
motion since it is possible to copy directly (without intermediate
searching)
from the system DECtape to another DEC tape (or vice versa)
when editing or assembling.
A typical medium-sized system might contain a PDP-8/E with at least 8K
words of core memory, TD8E DECtape and control, and an RK8E disk pack
and control. A disk system offers the additional convenience of easy
and fast access to files and large amounts of storage.
Up to IS of the following devices can be included
system:
•

As many as
TD8E/TUS6)

DECtape

units

•

TA8E/TU60 cassette units

•

TM8E/TUIO magnetic tape units

•

High-speed paper tape reader/punch

•

Up to four RK8E disks

•

Up to four RK8 disks

•

Up to four RS08 disks

1-3

(TCOI/TUSS,

single

05/8

TC08/TUS6,

OVERVIEW

1.4

•

Up to four DF32 disks

•

Card reader (optical mark or punched cards)

•

Line printer

•

PDP-12 LINCtape

•

PDP-12 scope

•

Any other device for which it is possible to
handler in one or two pages of core

write

device

SYSTEM SOFTWARE COMPONENTS

The main software components of the OS/8 system include
Keyboard Monitor
The Concise Command Language
Command Decoder
Library of system programs
Device handlers
User Service Routine (USR)
The Keyboard Monitor provides communication between you and the OS/8
executive routines by accepting commands from the console terminal.
The commands enable you to create logical names for devices,
run
system and user programs, and save programs.
The Concise Command Language (CCL) provides an extended set of Monitor
Commands.
The Command Decoder allows you to communicate with a system library
program by accepting a command string from the keyboard indicating
input/output files.
Following your keyboard command to run a system
library program, the Command Decoder prints an asterisk and then
accepts the command line containing device and file specifications.
The library of system programs contains the programs mentioned
Section 1.1 and any of the extension programs you choose.

Device handlers are subroutines designed to transfer data to and from
peripheral devices.
OS/8 is able to interface with as many as 15
different peripherals at a time.
During system generation, device
handlers become an integral part of the system~ both system and user
programs have access to any available device.
(The BUILD program
allows quick and easy alteration of any available device.)
The User Service Routine (USR) controls the directory operations for
the OS/8 system.
A program can use the USR by means of standard
subroutine calls such as those used to activate device handler
subroutines.
Some of the functions performed by the USR are loading
device handlers, searching file directories, creating and closing
output files,
calling the Command Decoder, and chaining of programs.
The details on the operation and use of the USR are contained in the
OS/8 Software S~~ Manual
(DEC-S8-0SSMB-A-D).
For normal OS/8
usage, the USR function is unseen by the user and need be of no
concern.

1-4

OVERVIEW
When 05/8 is operating, the Command Decoder, Keyboard Monitor, and USR
are swapped into core from the system device as required. When their
operation has been completed, the previous contents of core are
restored.
The memory-resident portion of 05/8 is extremely small
allowing for a maximum uSe of memory by user programs.

1-5

(256

words),

CHAPTER 2
SYSTEM CONVENTIONS

OS/8 observes the following conventions
files, and units of storage.

2.1

the

names

devices,

PERMANENT DEVICE NAMES

During configuration, the OS/8 BUILD program assigns permanent names
to
the devices in a system.
You can change these names by
reconfiguring the system, but you must keep in mind that some CCL
commands and system programs operate on the assumption that certain
names are present. The DIRECT command, for example, uses the name
TTY:
as a default device for listings, and the CREF program assumes
LPT: as a default output device. Therefore, it is good practice to
keep the following names always present on the system.
SYS:
DSK:
TTY:
LPT:
Table 2-1 lists all the device names used by OS/8.
Table 2-1
Permanent Device Names
Permanent Name

I/O Device

SYS

System device (disk if the system has a
large disk -- RK8 or RF08; otherwise DTAO)

DTAn

DEC tape n, where n is an
range 0 to 7, inclusive

LTAn

When using BUILD, LINCtapes may be called
LTA rather than DTA. n is an integer in
the range 0 to 7 inclusive.

DSK

Default storage device for all files.
The
assignment of DSK is specified at system
generation time. usually DSK is the disk
on a single disk system or DTAO on a
DEC tape system.

integer

the

(continued on next page)

2-1

SYSTEM CONVENTIONS
Table 2-1
(Cont.)
Permanent Device Names
--------

-------------~---~~

Permanent Name

2.2

I/O Device

TTY

Terminal keyboard and printer

PTP

Paper tape punch

PTR

Paper tape reader (Before accepting input,
the system prints an up-arrow (t), to which
the user replies by typing any key.)

CDR

Card reader

LPT

Line printer (Performs a form
it
begins printing output
program. )

CSAn

Cassette drive n, where n is an integer
the range 0 to 7, inclusive

MTAn

Magnetic tape drive n, where n is
integer in the range 0 to 7 inclusive

DF32 disk

RF08 disk

RKAn

RKOl or RKOS disk unit n, where
integer in the range 0 to 3

VR12 scope (PDP-12 only)

BAT

Pseudo device which reads from BATCH input
stream (see BATCH section in Chapter 2)

RXAn

Diskette n (floppy), where n is an
in the range of 0-7 inclusive

integer

RKBn

DECpack n, where n is
range 0-1

NULL

Device which on input returns an immediate
end-of-file
and
on
output
ignores
characters.

DUMP

Prints contents of device blocks on LPT.

feed
from

integer

before
a new

the

FILE NAMES AND EXTENSIONS

File names may contain up to six alphanumeric characters, followed
optionally
by
a period and an extension of two alphanumeric
characters. The extension usually identifies the file by type.
For
example, a .PA extension after a file name indicates that the file
contains a PAL8 source program.

2-2

SYSTEM CONVENTIONS
In most cases, you will want to conform to the standard extensions
established for OS/8.
If you omit the extension on an output file
specification, some system programs append assumed extensions.
PAL8,
for example, will add .PA to an output file.
If you specify a file
for input and omit the extension, some system programs will look for a
file with an assumed extension.
For example, if you specify a program
called PUMP as input to PAL8, PAL8 looks for PUMP.PA.
If it fails to
find it, it looks for the file name and no extension.- Table 2-2 lists
the file name extensions used by OS/8.
Table 2-2
OS/8 File Name Extensions
.BA

BASIC source file (default extension for
BASIC input file)

.BI

Batch input file

.BK

Backup ASCII file (default extension for
TECO output file)

.BN

Absolute binary file (default extension for
ABSLDR, BUILD, and BITMAP input files;
also used as default extension for PAL8
binary output file)

.DA

Data file

.DC

Documentation file

.DI

Directory listing

.FT

FORTRAN language source
file
extension for FORT input files)

.HL

Help file (default extension for HELP input
files)

.LD

F4 load mode (default assumed
system, F4 loader)

.LS

Assembly listing output
file
extension for PAL8 and SABR)

.MA

Macro source file

.MP

File containing a loading map (used by
Linking Loader)

.PA

PAL8 source file

.RA

RALF assembly language file

.RB

Relocatable binary source file

.RL

Relocatable binary file (default extension
for a Linking Loader input file;
also used
as the default extension for an 8K SABR
output file)

(default

run-time
(default

the

(continued on next page)

2-3

SYSTEM CONVENTIONS
Table 2-2
(Cont.)
OS/8 File Name Extensions
.SB

8K SABR source file

.SV

Core image file or SAVE file;
appended to
a file name by the R, RUN, SAVE, and GET
Keyboard Monitor commands

.Sy

System head

.TE

TECO macro file (default
MUNG input file)

.TM

Temporary file generated by FORTRAN or SABR
for
system use (default extension for CREF
input files and PAL8 output files)

.TX

Text files

2.3

extension

for

UNITS OF STORAGE

OS/8 uses the terms "word", "page", "record", and "block" to describe
units of storage.
In directory listings, for example, OS/8 lists file
lengths in blocks or records.
The terms are defined thus:
1 block=l record=2 pages=256(decimal) words
A word consists of 12 bits.

2-4

CHAPTER 3
05/8 KEYBOARD COMMANDS

3.1

INTRODUCTION

The
OS/8
Monitor
and
program -- CCL.SV -- provide
keyboard commands.
•

Command
the
Concise
you with more than fifty

The Monitor provides the following commands,
abbreviate to the first two letters.

Language
different

which

you

may

ASSIGN
DEASSIGN
GET
SAVE
ODT
RUN
R

START
DATE
The Monitor displays a dot to indicate that
accept a command.

ready

To execute a command that you
ALTMODE.

press

RETURN

have

typed,

Any error that you make in the use of these commands causes
the Monitor to print an error message, display the dot, and
wait for you to try again. For a description of these error
messages, see Table 3-1.
Table 3-1
Keyboard Monitor Error Messages
Message

Meaning

BAD ARGS

The arguments to the SAVE command are
not
consistent
and
violate
restrictions listed in 1, 2, 3 under
SAVE command.

BAD CORE IMAGE

The
file
requested
was
a
not
core-image file (it could have been an
ASCII or binary file).
(continued on next page)

3-1

OS/8 KEYBOARD COMMANDS
Table 3-1
(Cont.)
Keyboard Monitor Error Messages
Message

Meaning

~--------------------------~r-----------------------~---------------------~

BAD DATE

The date
has
not
been
entered
correctly
(using
slashes) ,
or
incorrect arguments were used, or the
date was out of range.

ILLEGAL ARG.

The SAVE
correctly~

command was not expressed
illegal syntax used.

MONITOR ERROR 2 AT xxxx
(DIRECTORY I/O ERROR)

Attempt made to output to a WRITELOCKed device, usually DECtape~ or an
error has occurred reading/writing a
directory.

MONITOR ERROR 5 AT xxxx
(I/O ERROR ON SYS)

An error occurred while doing I/O to
the system device.
This error is
normally
the
result
of
not
WRITE-ENABLing the system device.

MONITOR ERROR 6 AT xxxx
(DIRECTORY OVERFLOW)

A directory overflow
has
(no room for tentative file
directory) .

name NOT AVAILABLE

The device with the name given is not
listed in any system table, or it is
not available for use at the moment
(check the device in question), or the
user tried to obtain input from an
output-only
device
(such
as the
high-speed paper tape punch).

name NOT FOUND

The file with the name given was not
found on the device indicated, or the
user
tried
to
input
from
an
output-only device.

NO! !

The user attempted to start (with .ST)
a program that cannot be started. The
user must not restart any user program
or
system
library
program
that
modified itself while in core
(bit 2
of the Job Status Word is set~
see
the GET command for details).

NO CeLl

The command was not a legal keyboard
monitor command.
It was, however, a
valid CCL command~
but the
file
CCL.SV was not found, or an I/O error
occurred while trying to read the
file.

SAVE ERROR

An I/O error has occurred while saving
the
program.
The program remains
intact in core.

occurred
entry in

(continued on next page)

3-2

05/8 KEYBOARD COMMANDS
Table 3-1
(Cont.)
Keyboard Monitor Error Messages
Message

Meaning

SYSTEM ERR

An error occurred while doing I/O to
the system device. The system should
be restarted at 7600 or 7605. Do not
press CONTinue, as this is sure to
cause futher errors.

TOO FEW ARGS

An important argument has been omitted
from a command. For example,
...,LRUN [lSK

would generate this message, as the
program to be run has not been entered
in the command.
USER ERROR 0 AT xxxx

An input error was detected while
loading the program. xxxx refers to
the Monitor location where the error
was generated.

abcd?

Where abcd is not a legal command~
for example, if the user typed:
~HELLO

the system would echo:

HELLO?
•

The Concise Command Language program (CCL)
provides
an
extended set of Monitor commands.
Some of these commands
allow you to call a system program indirectly, perform an
operation, and return automatically to the Monitor. This
method is simpler to use than the standard calling sequence
for a program. For example, the following two-line sequence
causes PAL8 to assemble a source program called SCOOP.PA and
send a binary and listing file to DSK, the default device .

..t.,R PAL8
~SCOOP.BN,SCOOP.LS<SCOOP.PA

You can obtain the same results faster by using
command with the -LS option .

the

CCL

PAL

not

available

..!.,.PAL SCOOP.PA-LS
Other CCL commands perform special
through OS/8 utility programs.

functions

You can write your own CCL commands and add them to the CCL
program.
For instructions, see the OS/8 Software Support
Manual.

3-3

OS/8 KEYBOARD COMMANDS
You enter a CCL command the same way you enter a Keyboard
Monitor Command -- in response to the terminal dot. Normally,
you terminate the command line with the RETURN key. Depending
on the characteristics of the command you are using, control
may return to the Monitor when the operation is completed or
may remain within another OS/8 program.
To remain under
program control when control would normally return to you,
terminate the CCL command with an ALTMODE.
(Note that this
termination procedure is the opposite of the way most OS/8
programs work.)
A special CCL command
called CCL -- deactivates the entire
Concise Command Language Program and all the commands that run
under it. To reactivate the program, you must run it with the
R command.
CCL provides the following commands, which you may
to the letters printed as capitals:
BACkspace
BAsic
BOot
CCL
COMPare
COMpile
COPy
CREate
CREF
DAte
DEassign
DELete
DIRect

3.2

DUplicate
EDIT
DOF
EXEcute
HELp
LIst
LOad
MAKe
MAP

MEMory
MUNG
ODT
PAL

PRInt
PUnch
REName
RES
REWind
SET
SKIP
SQuish
SUbmit
TEco
TYpe
UA
UB

abbreviate

UC
UNLoad
VERsion
ZERO

COMMAND FORMAT

The general format of ~he command line is
command output:file<input:file/option
where
command

is a legal OS/8 command

output:

is the name of the device you specify to receive output

file

is the name and extension of an output file

input:

is the name of the device you specify for input

file

is the name and extension of an input file

/option

is a command qualifier

Some commands permit multiple file and device specifications;
refer
to the descriptions of the command~ you want to use for details.

3.3

COMMAND AND FILE OPTIONS

OS/8 command options let you choose the way you want to execute a
command.
File options let you optimize the storage on an output
device.
3-4

OS/8 KEYBOARD COMMANDS
3.3.1

Command Options

OS/8 recognizes single letters, letter strings, and numbers as symbols
for command options.
All options are defined in this manual along
with the commands they modify.

3.3.1.1 The
Slash
Construction -- Single-Letter
Options Single-letter options follow a slash {I} and may appear anywhere in
the command line even in the middle of a filename.
For example, this
line
~COPY

RXA1:SECOND.EX<RXAO:FIRST.EX/T

and this line
~COPY

RXA1:SECOND.EX/T<RXAO:FIRST.EX

both specify the /T option, which causes
current date to the output file.

the

system

assign

the

3.3.1.2 The Parenthesis Construction -- Multiple-Letter Options - If
you use two or more letter options in a command line, you may group
them together as a string within parentheses. This construction may
appear anywhere in the line. For example, this command
~COPY

RXA1:0UTPUT.EX<SYS:INPUT.EX(GT)

is the same as typing
~COPY RXA1:0UTPUT.EX<SYS:INPUT.EX/G~T

3.3.1.3 The Equal Sign Construction -- Octal Number Options - An
octal number option, preceded by an equal sign, may occur only once in
a command line.
If you place it in the middle of the line, you must
follow it with a separator character (a comma or left-angle bracket)
or another option and a separator character.
For example, this line,
which includes an octal 3,
~DIRECT

SYS:=3

causes DIRECT to list the directory of SYS:
columns.

3.3.2

on the terminal in

three

File Options

A file option places an upper limit on the number of blocks an output
file may use.
(One block contains 256 words.) This option allows the
system to optimize file storage.
For example, this command line
~PAL

BINARY[19],LIST[200l<SOURCE.PA

calls for two output files, BINARY and LIST, which may have a
length of 19 blocks and 200 blocks respectively.

3-5

maximum

OS/8 KEYBOARD COMMANDS
3.3.3

Additional Switch Options--the Dash Construction

A special set of command options enable you to send output to the
lineprinter or terminal, generate a listing file or a memory map, or
call for a particular compiler or assembler.
These options are
described in Table 3-2.
Table 3-2
Switch Options
Option

3.4

Meaning

-L

Send output to LPT.

-LS

Generate a listing file
(used with the COMPILE,
EXECUTE,
and PAL commands).
The listing file is
written onto SYS:
if no output device is specified
and is given a .LS extension. The listing filename
is the same as the filename that immediately preceded
the CCL -LS option.

-MP

Generate a memory map
(used
EXECUTE, and PAL commands).

with

the

COMPILE,

-NB

DO not create a binary file (used with
EXECUTE, and PAL commands).

the

COMPILE,

-T

Send output to terminal.

-PA

Selects the PAL8 compiler when the files extension
does not determine it
(used with the COMPILE and
EXECUTE commands).

-FT

Selects the FORTRAN IV compiler
extension does not determine it
COMPILE and EXECUTE commands).

when the
file
(used with the

COMMANDS THAT REMEMBER FILE SPECIFICATIONS

If you omit the device and file specifications in a CREATE, EDIT, PAL,
COMPILE, LOAD, or EXECUTE command, OS/8 assigns it the last argument
to appear in any command in the group.
For example,
these two
commands
~COMPILE

TEST.PA

~EXECUTE

instruct the system to compile TEST.PA,
then load and execute it.
When you enter the COMPILE command, the system stores the argument in
a temporary file for later reference by the EXECUTE command.
This
feature works only with commands that you enter on the same day.

3-6

OS/8 KEYBOARD COMMANDS
3.5

USING WILDCARDS

Wildcards, which certain OS/8 commands accept, make it possible for
you to refer to a group of related files with a single file
specification. OS/8 provides two wildcards:
•

the asterisk
extension

•

the question mark (?), which replaces any single character

3.5.1

(*),

which

replaces

entire

filename

Wildcards in Input Filenames

The following commands permit both the asterisk and question
wildcards in input specifications.

mark

COpy
DELETE
DIRECT
LIST
RENAME
TYPE
Here are some examples of the various ways you
specifications with wildcards.

can

abbreviate

input

.DEL TE5T1.*

deletes all files on DSK with the name
and any extension

TESTI

.DIR *.BN

displays a directory of all files on DSK with
a .BN extension and any name
displays a directory of all files with
beginning TES and any extension

names

lists the contents of all DSK files
names of three characters or less

with

A filename may not contain embedded asterisks. For example, TE*T.* is
an illegal specification and will produce the following error message:
ILLEGAL

If you use a wildcard in a command other than the ones
OS/8 prints the error message

listed

above,

ILLEGAL * OR ?

3.5.2

Wildcards in Output Specifications

You may use the asterisk wildcard in an output file name.
The
question mark, however, is illegal. If you omit the output file name
altogether, the system assumes * * -- that is, all files with any
extension.
For example, this command

copies all files from SYS with a PA
extension BK.
3-7

extension

RXAl,

adding

the

OS/8 KEYBOARD COMMANDS
3.5.3

Warnings and Suggestions

Use wildcards in COpy and DELETE commands with extreme caution to
avoid destroying irreplacable files.
Always observe the following
fail-safe measures.
•

Keep a backup copy
important files.

the

system

•

Use the Q option with COpy and DELETE. The system pauses to
make sure you have specified the file you intended.
If you
wish to go through with the operation, type Y in response to
the query.
If not, type any other character.

For further discussion of wildcards, see
Program (FOTP).

3.6

the

diskette

and

File-Oriented

all

other

Transfer

INDIRECT COMMANDS

You may occasionally wish to refer to the same group of files in
several commands.
To avoid typing the same filenames and extensions
in each command line, use the indirect -- @ file -- feature.
An

indir~ct

file specification has the following format.

@device:file.ex
where
file.ex

is a file containing the file specifications
to include in the command

you

want

To use the @ construction, you must first create a file containing the
list of file names you wish to include in the command line. For
example, assume you have created a file called FLIST.CM that contains
the string
FILEB,FILEC/L,FILED
TO include these names in a COMPILE command, type
~COMPILE

FILEA,@FLIST,FILEZ

The system ignores carriage returns and line feeds -- but
nulls -- within the command line. A null signifies end-of-line.

not

Command files may not exceed one block in length.
If a command line
contains more than 512 characters, the system prints the following
message:
COMMAND LINE OVERFLOW
The following commands will not accept indirect files.
ASSIGN
DEASSIGN
GET
START

R
RUN
SAVE
ODT
DATE
3-8

OS/8 KEYBOARD COMMANDS
3.7

USING DEFAULTS

A default device, file name, or extension is the name the system
assumes if you omit the specification in a command line. You can
often reduce the amount of typing necessary to enter a command by
taking advantage of the following system defaults.
•

DSK is the default device for input and output devices in most
commands.
This means that you can omit the device whenever
you refer to a file on DSK.
For example, the following
command makes a copy of a file called HUMPTY on DSK and calls
it DUMPTY .

• COPY DUMPTY<HUMPTY
•

Any device -- stated or assumed
in an input specification
becomes the default device for any additional input files in
the command line. For example, this command lists three files
on RXAI .

• LIST RXA1:0NE,TWO,THREE
•

Some commands assume special default devices.
DIRECT
TYPE, for example, default to the terminal for output.
following command will display the directory of DSK on
terminal .

and
The
the

• DIR
The description of the OS/8 command
defaults that each command accepts.

about

the

OS/8

HELP retrieves and displays a file called HELP.HL, which contains
information you request.

the

To obtain a hard copy of the information from the
the -L option •

use

3.8

includes

information

GETTING HELP--THE HELP COMMAND

To obtain additional information about the use
commands, use the HELP command. The format is

and

format

.HELP command
where
command

is the name of any OS/8 command

• HELP PAL-L

3-9

line

printer,

OS/8 KEYBOARD COMMANDS
3.9

ENTERING A COMMAND LINE--CORRECTING AND PREVENTING ERRORS

The RETURN key enters a command line and causes the system to take the
action you have called for. Therefore, before you press RETURN, check
the line carefully for errors.
•

To correct single-character typing errors, use the DELETE key.
This key erases the last character you have typed. Successive
DELETEs will erase characters back to the beginning of the
line.

remove an entire line, type CTRL/U by holding down the CTRL
• To
The monitor will echo the command and
key and striking U.
display a dot to indicate that it is ready to
command.
•

another

To verify the contents of the line you are typing, strike the
LINE FEED key. The system will display whatever characters it
has received so far.
Use the LINE FEED key to check a line in
which you have made numerous corrections.

If you enter a command line that you have typed
the following will result:

incorrectly,

one

•

The system will fail to recognize or accept the command.
In
this case, it will display a question mark and a dot and wait
for you to try again.

•

The Monitor will accept the command and attempt to execute it.
If
you
notice your error at this point, type CTRL/C
immediately (simultaneously pressing CTRL and C).
Depending
on the type of command and the files involved, this may halt
execution.

3-10

ASSIGN

OS/8 KEYBOARD COMMANDS
3.10

ASSIGN

The ASSIGN command assigns a logical name -- that is, a name that you
create -- to one of the available permanent devices. The format of
the command is
ASSIGN perm user
where
perm

is the permanent name of the device

user

is the one-to-four-character name you want to assign

Note that a device name does not require a colon when it
ASSIGN command.

follows

the

The following rules apply to the assignment and use of logical names.
•

You may assign only one logical name to a device at a time.

•

Once you have assigned a name to a device, you may refer to it
by either its logical or permanent name. ASSIGN makes the two
names equivalent.

For example, this command
~ASSIGN

RXAl DEV2

assigns the logical name DEV2 to RXAI.
You
device by either name in any command line.

3.10.1

may

now

refer

the

Canceling a Logical Name

To cancel a logical name, type the ASSIGN command with the permanent
device name only. For example, to remove DEV2 as a logical name for
RXAl, enter

.,!.ASSIGN RXAl

3.10.2

Checking for Duplicate Names

To determine if a logical name is unique in the OS/8 system, enter the
name by itself in an ASSIGN command line. For example, to see if DEV2
already exists, type

.ASSIGN DEV2
If the name does not appear
displays the message

any

the

system

tables,

ASSIGN

DEV2 NOT AVAILABLE
All 1- and 2-character names are unique in OS/8.
3- and 4-character names.
ASSIGN is a Monitor command.

3-11

You need

test

only

BACKSPACE
3.11

OS/8 KEYBOARD COMMANDS

BACKSPACE

The BACKSPACE command runs the OS/8 CAMP program and spaces a magnetic
tape or cassette backward a specified number of files or records.
BACKSPACE is equivalent to the CAMP BACKSPACE command. When CAMP has
completed a BACKSPACE operation, it returns control to the Monitor.
The format is
BACKSPACE dev:nnnn X
where
dev:

is the permanent name of a cassette
drive

magnetic

nnnn

is an unsigned decimal number representing
of records or files you wish to backspace.
the number, BACKSPACE assumes nnnn=l.

is an R or F to indicate records or files. If you
not specify records or files, BACKSPACE assumes F.

tape

the number
If you omit
do

For example, this command

.BACKSPACE CSAO:2 F
positions the cassette mounted on CASO backward two files.
For complete information on the BACKSPACE command, see the chapter
the CAMP program.
BACKSPACE is a CCL command and runs the CAMP program.

3-12

BASIC

05/8 KEYBOARD COMMANDS
3.12

BASIC

The BASIC command invokes the BASIC Editor.

The format is

BASIC
As soon as it is ready to accept your first instruction, BASIC
the query

prints

NEW OR OLD -to determine if you want to create a new file or work on an old one.
For example, this command

.BASIC
NEW OR OLD -- NEW STUFF.BA
tells the BASIC Editor to accept a new program called STUFF.BA
For complete information
Reference Manual.

OS/8

3-13

BASIC,

see

the

OS/8

Language

BOOT
3.13

OS/8 KEYBOARD COMMANDS

BOOT

The BOOT command makes it possible for you to bootstrap
device or onto another PDP/8 system. The format is

onto

another

BOOT/dv
where
dv

is a mnemonic listed in the BOOT chapter in this manual

If you type BOOT with no argument, BOOT prints
that you must enter a mnemonic.

slash

indicate

For example, this command
~BOOT/RF

bootstraps onto the RF08 disk.
If you wish to halt before doing the bootstrap, type
mnemonic, and a period. For example:

the

command,

.BOOT/CA.
The period causes the computer to halt, giving you time to mount a new
device.
To continue the operation, press the CONTINUE switch on the
console. This form of the command is useful when only one 'disk or
DECtape drive exists on the system.
For complete information, see the BOOT chapter in this manual.

3-14

CCl

05/8 KEYBOARD COMMANDS
3.14

CCL

The CCL command disables the Concise Command Language program
system device. The format is

the

CCL
The command accepts no arguments.
The CCL command totally deactivates the CCL feature of OS/8 so that
the system will not accept any CCL command. If you wish to use CCL
again, you must reactivate it with the R command. To do this, type
.R CCl

3-15

COMPARE
3.15

OS/8 KEYBOARD COMMANDS

COMPARE

The COMPARE command makes a line-by-line comparison of two input
source files and sends the results to an output device. In most
COMPARE operations, the two source files are different versions of the
same program. COMPARE prints the editing changes, making it a useful
tool for debugging.
The format is
COMPARE output:file<input:filel,input:file2
where
output:file

is the file containing the results
of
the
comparison and the device you want to send it to

input:filel

is the first input source file for comparison

input:file2

is the second SOurce file

COMPARE makes the following assumptions:
•

If you omit an input or output device, COMPARE assumes DSK

•

If you omit the output specification altogether, COMPARE
assumes TTY.
(In most cases you will want to see the results
on the terminal.)

For example, this command

.COMPARE RXAl:APPLE.FT,RXAl:0RANGE.FT
compares two FORTRAN source files on RXAI -- APPLE
sends the results to the terminal.

3.15.1

and

ORANGE -- and

COMPARE Output

COMPARE produces the following output sequence:
1.

the current version number of the utility program SRCCOM

the header line of both input files (the header is the first
line of the file and usually contains the file name and
creation date)

a difference group (see below)

additional difference groups, if any, until
end of the shorter file

reaches

the

COMPARE reads two input files one line at a time until it encounters
three consecutive matching lines. Then it outputs all lines from both
files up to and including the first matching line.
This output is
called a difference group. For a complete description of difference
groups, see the SRCCOM chapter in this manual.

3-16

OS/8 KEYBOARD COMMANDS
For example, consider two files on DSK--NITTY and GRITTY.
NITTY

GRITTY

C
D
E
F
G

C
D
E
G
H
J

I
J

To compare these two files and
terminal, type

have

the

results

number

displayed

the

.COHPARE NITTY,GRITTY
COMPARE prints the current version
program that does the comparison,

SRCCOM,

the

utility

SRCCOH V4A
the header lines

1 )NITTY
2)GRffiy
and the results of the comparison in two difference groups

1)002
1)

B
C

****
2)002

*********
1)002
F
1)
1)
1)
1)

G
H
I
J

****
2)002
2)
2)

G
H
J

If COMPARE discovers two identical files, it prints

NO DIFFERENCES
in the output file.

3.15.2

COMPARE Options

COMPARE provides the following options:
•

In normal operation, COMPARE outputs lines until it
encounters three consecutive matching lines. To change
the number of lines that interrupt processing, use the
=k option, where k is the number of lines (in octal)
that you want to specify.

3-17

OS/8 KEYBOARD COMMANDS

•

COMPARE ignores comment fields during the comparison of
assembly language source files.

•

COMPARE treats a blank line as valid
blanks instead of a carriage return.

•

COMPARE ignores
comparison.

•

COMPARE converts all tabs from the input file to spaces
on the output device.

•

COMPARE ignores all
comparison and does
device.

all

tabs

spaces

containing
during

the

comment
fields
during
the
not send comments to the output

COMPARE is a CCL command and runs SRCCOM.

3-18

and

input

OS/8 KEYBOARD COMMANDS
3.16

COMPILE

The COMPILE command
•

assembles a PAL8 source program and outputs an absolute binary
file and a listing file or a CREF file

•

compiles and assembles a FORTRAN IV source program and outputs
a relocatable binary file and a listing file

•

compiles, loads, and executes a BASIC source program

The format for a PAL8 program is
COM output:prog.BN,output:list.LS<input:filel.PA, •.• file9.PA
where
output:prog.BN

is a PAL8 binary file

output:list.LS

is a PAL8 listing file

input:filel, ... file 9

is a single source program, which you
may enter in up to nine separate files

For example, this command line
~COMPILE

RXA1:ACE.BN,RXA1:ACE.LS<RXA1:ACE.PA

assembles a PAL8 source program on RXAI called ACE.PA and
binary file, ACE.BN, and a listing file, ACE.LS.

produces

The format for a FORTRAN source program is
COMPILE output:prog.RL,output:list.LS<input:filel.FT, ••• file9.FT
where
output:prog.RL

is an assembled FORTRAN program

output: 1 ist. LS

is a listing file

input:filel, .•. file 9

is a FORTRAN source program stored in up
to nine files

For example, this command
~COMPILE

RXA2:DEUCE.RL,RXA2:DEUCE.LS<RXA1:DEUCE.FT

assembles DEUCE.FT and outputs a binary and a listing file -- DEUCE.RL
and DEUCE.LS.

3.16.1

COMPILE Input

Enter your PAL8, FORTRAN, or BASIC program as an input file or files.
You may include up to nine input files in a single COMPILE command
line. COMPILE assumes that they all contain sections of the same
program.
The extension on the file name identifies the type of program the file
contains and tells the command which assembler or compiler to summon.

3-19

OS/8 KEYBOARD COMMANDS

•

.PA

identifies a PAL8 source program

•

.FT

identifies a FORTRAN source program

•

.BA

identifies a BASIC source program

If you use nonstandard extensions, you must specify the assembler or
compiler your program requires with processor switch options -PA, -FT,
or -BA.
COMPILE makes the following assumptions about input device names:
•

If you omit the device
COMPILE assumes DSK.

the

first

•

If you omit the device in subsequent
assumes the last device you name.

input

specification,

input

entries,

assigning

the

COMPILE

For example, this command line
~COMPILE

PARTl.PA,PART2.PA,PART3.PA

assembles a 3-part PAL8 program on DSK.

3.16.2

COMPILE Output

COMPILE outputs binary and listing
specify.

3.16.2.1

files,

names

you

Output File 1 -- the Binary Code

•

If your input file is a PAL8 source program, COMPILE assigns
the first output file name to the binary code generated by the
assembler, adding a .BN extension if you omit it.

•

If your input file is a FORTRAN program, COMPILE assigns the
first output file name to the relocatable binary code produced
by the FORTRAN assembler, adding .RL if you omit
the
extension.

If you omit the device, COMPILE assumes DSK. If you omit
name, COMPILE assumes the name of the first input file.

the

file

For example, this command line
~COMPILE

RXAl:SUNDAY(RXA2:MONDAY.FT

compiles and assembles the source program MONDAY.FT and
RXAl as a binary file called SUNDAY.RL.

sends

In certain COMPILE operations, you may wish to suppress the output
binary file and generate only a listing file. To suppress a binary
file, use the -NB (no binary) switch. For example,
~COMPILE

SAMPLEoPA-LS-NB

assembles SAMPLE.PA and produces only a listing file.

3-20

OS/8 KEYBOARD COMMANDS
3.16.2.2 Output File 2 -- the Listing File - You can
listing file of a PAL8 or FORTRAN program in two ways:

request

•

Enter a second output file in the COMPILE line.
COMPILE
generates the listing and assigns it the name you specify,
adding .LS if you omit the extension.

•

Type the -LS switch option after an input file name.
COMPILE
generates the listing, gives it the name immediately preceding
the switch, and adds the .LS extension.

For example, this command
~COMPILE

PARTY,PARTY~PARTY.PA

and this command
~COMPILE

PARTY.PA-LS

both generate a listing file PARTY.LS.
If you use the PAL8 /C option, the second output file is passed to the
CREF program, which produces a cross-reference listing.

3.16.2.3 COMPILE Options and Errors - For a complete description of
COMPILE options and errors, see the sections on PAL8, FORTRAN IV, and
BASIC in the OS/8 Language Reference Manual.
COMPILE is a CCL command.

3-21

COpy
3.17

OS/8 KEYBOARD COMMANDS

COPY

The COpy command transfers files from
format is

one

device

another.

The

COpy output:file<input:filel, •.. input:file5
COpy sends files to the output device in exactly the same format and
order in which they appear in the command. Since the operation makes
no changes at all in the files, you may transfer any kind of
file -- memory image, binary, source -- with the COpy command.

3.17.1

COpy Input

You enter the file or files you want
command line.

transfer

input

the

A complete COpy input specification includes a device, a file name,
and an extension. You may enter up to five input files in a command
line. COpy uses the following input defaults:
•

If you omit the device name in the first input
COpy assumes DSK.

specification,

•

If you
omit
the
device
name
in
succeeding
specifications, COpy assumes the last device entered.

input

You may use the wildcards * and? to transfer an entire group of
related files with a single command. The specification *.* tells COpy
to transfer all the files on a device.

3.17.2

COPY Output

A complete output specification includes a device, a file name, and an
extension.
You may enter only one output specification in a command
line.
If you want your transferred file to have a different name from
the original, you must enter that name as the output file.
COpy uses the following output defaults:
•

If you omit the device, COpy assumes DSK.

•

If you omit the output file name, COpy assumes *.* -- that is,
it assumes that the output file has the same name as the input
file.

You may use only the wildcard *;
the question mark
(?)
is illegal.
Keep in mind that as output the specification *.* tells COpy to give
the output file the same name as the input file.

3.17.3

COPY Terminal Display

During execution, COpy prints on the terminal the names of the files
it has transferred.
For example,
the following command transfers
three files from DSK to RXAI.
~roPY

RXA1:FLOWER.PA<ROSE.PA,DAISY.PA,ZINNIA.PA

3-22

OS/8 KEYBOARD COMMANDS
COpy displays

FII rs COPIED
RO!..l .PA
DAl::>Y.PA
ZINNIA.PA

3.17.4

Predeletion and Postdeletion

Before COPY transfers a file to an output device, it checks the file
name against the output file directory. If it finds a file on the
device with the same name and extension as the file it is going to
transfer, COpy automatically deletes it before it does the transfer.
This operation -- called predeletion -- makes space for the new file
on the output device, which may not otherwise be able to hold another
file. However, it may also cause you to lose a valuable file if for
some reason the input fails. To help protect against such loss, COpy
provides a second method of transfer called postdeletion.
In this
mode, COpy deletes any file with the same name as the input file only
after it has completed the transfer. To specify postdeletion, use the
/N option.

3.17.5

COPY Options

•

COpy transfers all input files with
onto the output device.

the

•

A file will not fit on the output device.

current

date

COpy prints

MOUNT NEW DEVICE
on the terminal. You remove the current device and
mount a new one on the same unit. To continue the
transfer, type any character. If possible, ZERO the
directory of the new device.

•

As part of the transfer operation, COpy changes the
creation date on the output file to the current date.
Without /T, COPY transfers the original date.

•

copy transfers input files in the exact order that they
appear in the command line -- not the order in which
they occur on the device.

•

COpy transfers all files on a device
you specify in the command line.

•

COpy prints its current version number.

•

•
•

except

the

ones

COpy transfers all files on a device except those
the current date.

with

COpy pauses before a transfer to make sure you want
go through with the operation. If you do, type Y;
not, type any other character.

to
if

COpy uses postdeletion.

COpy is a CCL command and runs FOTP. For complete information on file
transfer, see the FOTP chapter in this manual.

3-23

CREATE
3.18

OS/8 KEYBOARD COMMANDS

CREATE

The CREATE command summons the OS/8 Editor to let you open and write a
new file.
CREATE accepts no input specifications and only one file
name and device for output. The format is
CREATE output:file
where
output:file

is the name of the file you want to create and the
device you want to store it on.

For example, this line

.CREATE BIRDY.PA
opens a file called BIRDY.PA on the default device, DSK.
After you press the RETURN key to execute the command, the OS/8 Editor
displays a number sign
(t) to indicate that it is ready to receive
your instructions and text. To CREATE a file with the OS/8 Editor,
see Chapter 4 in this manual.
Each time you enter a CREATE command, the Monitor holds the argument
(the device and file name) in a temporary location.
If you type an
EDIT command later without an argument, EDIT reads the file name in
this location. This convenient feature works only with files that you
CREATE and EDIT on the same day.
CREATE is a CCL command and runs EDIT.SV.

3-24

CREF

OS/8 KEYBOARD COMMANDS
3.19

CREF

The CREF command assembles a
PAL8
program
and
cross-reference listing, usually on the line printer.

produces

The format is
CREF outdev:file.LS<indev:file.PA
CREF makes the
specifications.

following

assumptions

about

output

and

input

•

If you omit the extension on the input file, CREF assumes PA.

•

If you omit the extension on the output file, CREF adds LS.

•

If you omit the output specifications altogether,
the file to the line printer.

3.19.1

CREF

sends

CREF Options

• /P

CREF disables pass-one listing
output
until
it
encounters a $ in the source program. Thus, if you use
the /P option, CREF prints a dollar sign and the symbol
table.

•

CREF disables pass-one listing output
table.

•

CREF does not process literals. This option provides
space for CREF to operate on large programs with many
symbols and literals.

•

and

the

symbol

CREF does not eliminate the intermediate CREFLS.TM file
that is output from assembly and used as input to CREF.
CREF cross-references mammoth files in two
major
passes.
Pass one processes the symbols from A through
LGnnnn; pass two processes the symbols from LHnnnn
through Z and the literals.

CREF is a CCL command and runs PAL8.SV and CREF.SV.

3-25

DATE
3.20

OS/8 KEYBOARD COMMANDS

DATE

The DATE command lets you set and inspect the current system date.
You should always set the date as soon as you bootstrap the system.
TO set the date, type
DATE dd-mmm-yy
where
dd

is a two-digit number representing the day of the month

mmm

are the first three letters of the month

are the last two digits of the year

For example:

.DATE 23-MAY-77
TO inspect the current system date, type

,!.DATE
For example:

..t.DA 1-JUN-77
.DA
~WEDNESDAY JUNE 1, 1977
The system uses the current date in directories, newly created files,
and files transferred from one device to another. If you enter the
date after booting, the only valid directory entry dates are those for
the current year and seven years preceding it. The system will print
any earlier date incorrectly.
If you enter
message.

the

date

incorrectly,

BAD DATE
The DATE command runs program CCL.SV.

3-26

the

Monitor

prints

error

DEASSIGN

OS/8 KEYBOARD COMMANDS
3.21

DEASSIGN

DEASSIGN invalidates all logical (user-defined) names that
given to permanent devices.
(See the ASSIGN command.)

you

have

logical

name

The format is
DEASSIGN
For example, the following pair of commands assign
DEVI to SYS and then cancel it •
• ASSIGN SYS DEV1
:DEASSIGN
The Monitor performs the DEASSIGN function.

3-27

the

DELETE
3.22

OS/8 KEYBOARD COMMANDS

DELETE

The DELETE command removes files from the directory of the device
specify. The format is

you

DELETE input:filel, ..• file5
Enter the files -- up to five -- that you want to delete as input
You may specify only one device in a
files in the command line.
command line. DELETE makes the following assumptions about input
specifications.
•

If you omit the device name in the first input
DELETE assumes DSK.

specification,

•

If you omit the device name in succeeding specifications,
DELETE assumes the last device you entered. For example, this
command

.DELETE RXA1:EAST,WEST,NORTH,SOUTH
deletes four files from RXAI.
Note that DELETE does not actually remove the file from the device.
It simply erases its name from the directory, making the space it
occupies available for a new file. This means that in some cases you
may be able to retrieve a file you have mistakenly "deleted." For
details on retrieving lost files,
see the PIP /1 option in this
manual.
Also See the SUPERTECO section in the OS/8 TECO Reference
Manual.
You may use the wildcard asterisk
(*)
to specify file names and
extensions and the question mark (?) to indicate single characters.
Wildcards enable you to remove an entire group of related files with a
single DELETE command. For example, this command
~DELETE

*.PA

removes all files with a PA extension from the system device.
Use
wildcards with extreme caution to avoid deleting irreplacable files.

3.22.1

The Conditional DELETE

In most DELETE operations you simply list the files you want to remove
from a device as input files.
In some cases, however, you may wish to
remove a file only on the condition that some other related file
exists -- a source file, for example, if the device also contains the
program in binary code.
To call for this kind of DELETE, use the following format:
DELETE output:file<input:file
where
output:file

is the file you
present

input:file

is file f

3-28

wish

delete

file

OS/8 KEYBOARD COMMANDS
This command deletes, for example, any DSK file with a .PA extension,
only on the condition that DSK contains a file with the same name and
a .BN extension .

• DELETE *.PA<*.BN
FILES DELETED:
TESTl.PA
TEST2.PA
Only the wildcard (*) is legal in an out specification.
use the question mark.

3.22.2

You

may

not

DELETE Terminal Display

During execution, DELETE prints on the terminal the names of the files
it has removed. For example:

.DELETE" RXA2:SNOW.BA,RAIN.BA
DELETED:
SNOW.BA
RAIN.BA

FI~ES

3.22.3

DELETE Options

You may qualify a DELETE command with the following slash options:

•

DELETE removes only those files that have
date.

the

current

•

DELETE removes all files except those with the
date.

current

•

DELETE removes all the files from a device
ones you specify in the command line.

•

DELETE prints a question mark before execution to make
sure that you specified the right files for removal.
If your answer is yes, type Yi
if no, type any other
character.

•

DELETE displays a log of all files it has found for
deletion but does not remove the file names from the
directory.

except

the

DELETE causes the execution of program eeL.SV and FOTP.SV with the /D
option.
For further information on deleting files, see the FOTP
chapter in this manual.

3-29

DIRECT
3.23

OS/8 KEYBOARD COMMANDS

DIRECT

The DIRECT command produces listings of OS/8 device directories.
format is

The

DIRECT output:file(input:filel, .•. input:file5
DIRECT prints a directory of all the files on all the devices
(up to
5)
that you specify in the command line. DIRECT makes the following
assumptions about input and output specifications:
•

If you omit the input device, DIRECT assumes DSK.

•

If you omit input file names, DIRECT assumes
all files with any extension.

*.* -- that

is,

•

If you omit the output device, DIRECT prints the directory
the terminal.

•

DIRECT automatically adds a DI extension on an output file.

Always use wildcards in your input specifications when requesting a
list of related files on a device. For example, this command calls
for a list of all files on DSK that have a .PA or .BN extension.

You may use wildcards to represent an output file name or extension.

3.23.1

DIRECT Output

The standard DIRECT listing has the following format:
filespec

dd-mmm-yy

nnn

(file name and
extension)

(number of blocks used
in decimal)

(file-creation date)

If you do not enter the current date with the DATE command when you
boot
the
system, your directory listings will not include a
file-creation date.
For examples of DIRECT output, see the DIRECT chapter.

3.23.2

DIRECT Options

DIRECT options
directories.

• =n
• /C
• /E
• /F
• /M

enable

you

produce

DIRECT lists a directory
number from 1 to 7.

the
n

following
columns,

special

where

DIRECT lists only files with the current system date.
DIRECT includes empty files in the listing.
DIRECT lists only
dates.

file

names,

DIRECT lists empty files only.

3-30

omitting

lengths

and

OS/8 KEYBOARD COMMANDS

•

DIRECT lists only files with
current date.

•

DIRECT lists the file name you specify and
that follow it in the device directory.

•

DIRECT lists files in the same
them in the command line.
input file specification as
request.

DIRECT lists all files on a device except the ones
specify in the command line.

DIRECT displays its current version number.

·
•

3-31

date

other

than
all

the
files

order that you enter
That is, it treats each
a separate
directory
you

DUPLICATE
3.24

OS/8 KEYBOARD COMMANDS

DUPLICATE

The DUPLICATE command copies the entire contents of
another diskette. The format is

one

diskette

DUPLICATE output diskette:<input diskette:
You may use DUPLICATE to transfer the contents of diskettes only. For
example, the following command transfers the contents of RXAO to RXAl,
the device specified for output.
~DUPLICATE

RXA1:<RXAO:

DUPLICATE is a CCL command and runs the RXCOPY program.
For a
description of the options you can use with DUPLICATE, see the RXCOPY
chapter in this manual.

3-32

EDIT

OS/8 KEYBOARD COMMANDS
3.25

EDIT

The EDIT command summons the OS/8 Editor to let you retrieve and work
on a source program that you have stored as a file. The format is
EDIT output:file<input:filel, .•• input:file9
where
input:filel ••. 9

is a program (stored in one to nine files)
you want to work on and the device on which
it is located

output: file

is the name of the modified
device you want to send it to

file

The Editor signals with a number sign (t) as soon as it is
accept
your
first
instruction.
For
a discussion
instructions, see Chapter 4.

3.25.1

and

the

ready to
of these

Recalling Arguments

The EDIT command can recall arguments from a previous EDIT or CREATE
command entered on the same day. If you enter both an input and an
output file, EDIT remembers only the output specification.

3-33

EOF
3.26

OS/8 KEYBOARD COMMANDS
EOF

The EOF (End of File) command runs the CAMP program and writes a
single mark
(file gap)
on the specified magnetic tape or cassette.
The EOF command has the format
EOF device
where
device

is either MTAn or CSAn, signifying the device
which the file gap mark is to be written

For example, this command
.EOF MTA3
writes an end-of-file mark on the magnetic tape mounted on MTA3.
For a complete description of CAMP commands, see the CAMP
this manual.

3-34

chapter

EXECUTE

OS/8 KEYBOARD COMMANDS

3.27

EXECUTE

The EXECUTE command
•

assembles or compiles, links, loads,
program

and

executes

•

links, loads, and runs an assembled or compiled program

•

runs a linked and loaded program

source

The format is
EXECUTE output:file.bn,file.ls(input:filel, .•• file9
The EXECUTE command is the same as the COMPILE command with the IG
option. The input and output specifications depend on the compiler or
assembler you invoke.
For complete information, see the COMPILE
command and the various language chapters in the OS/8 Language
Reference Manual.

3-35

GET
3.28

OS/8 KEYBOARD COMMANDS
GET

The GET command loads a memory-image file -- that is, an SV file you
have created with the SAVE command -- back into memory. The format is
GET input:file.SV
If you omit the extension, GET looks for a file with the name you
specify and an .SV extension. You must specify the device; GET does
not assume DSK.
For example, to load into memory a file called JOBCNT.SV on RXAO, type
~GET

RXAO:JOBCNT

During execution, GET loads the file and its Core Control Block into
memory,
then transfers the CCB to a special area on the system device
for reference and maintenance. GET also places the Job Status Word
into location 7746 of field 0 to indicate what parts of memory the
file uses and how. It loads the block number of the first block of
the file into location 7747.
To run a program that you have loaded into memory with
START or EXECUTE command.
The Monitor performs the GET operation.

3-36

GET,

use

the

HELP

OS/8 KEYBOARD COMMANDS
3.29

HELP

The HELP command sends information on OS/8 system
output device, usually the terminal. The format is

programs

HELP output:file<OS/8
where
is the name of an OS/8 keyboard command or
program

OS/8

system

The default output device for HELP is TTY, the terminal.
To see a complete listing of keyboard commands, type

.HELP
For information on a specific command, enter the command name
argument in a HELP line:

the

.HELP PAL
To obtain a listing of all legal arguments for HELP, type
~HELP

HELP

HELP runs the program HELP.SV, which uses a reference file HELP.HL.
This file, which must be located on the system device, contains a list
of all the HELP subfiles available along with the HELP text itself.

3-37

LIST
3.30

OS/8 KEYBOARD COMMANDS
LIST

The LIST command sends to the line printer the contents of the files
(up to five)
that you specify as input in the command line. The
format is
LIST input:filel, ••• input:file5
LIST requires no output specification, assuming LPT.
input device, LIST looks for the file on DSK.

If you omit

For example, this command prints the source program
on DSK, on the line printer •

PROG.BA,

the

located

• LIST PROG.BA

LIST outputs the contents of each input file in the
you enter the files in the command line.

3.30.1

same

order

that

LIST Options

• /C
• /0
• /V
• /Q

LIST prints all files with the current date.
LIST prints all files except
date.

those

LIST prints all files except the ones
the command line.

with
you

the

current

specify

LIST displays each file name and a question mark.
If
you want to list that file, type Y;
if not, type any
other character.

LIST runs CCL.SV and FOTP.SV.

3-38

LOAD

OS/S KEYBOARD COMMANDS
3.31

LOAD

The LOAD command lets you load a PALS absolute
FORTRAN relocatable binary file into memory.

binary

file

The extension on the input file determines which
summons.

loader

the

absolute

binary

command

•

BN identifies a PALS program in
causes LOAD to summon the ABSLDR.

form

and

•

RL identifies a FORTRAN program in relocatable code and causes
LOAD to summon the FORTRAN loader.

To LOAD a PALS program, use the following format:
LOAD input:filel.BN, ••• input:file9.BN
where
is a PALS absolute binary file contained
in 1 to 9 files

input:filel.BN, ••. 9.BN
If your input
specifications.

file

PALS

program,

LOAD

ignores

output

For example, this command

.LOAD RXA1:TIC.BN,TAC.BN,TOE.BN
places a 3-part program in memory.
To LOAD a FORTRAN program, use the following format:
LOAD output:image.LD,output:map.LS(input:filel.RL, ••• input:file9.RL
where
output:image.LD

is an optional loader image file

output:map.LS

is an optional loader symbol map

input:file.RL .•• 9.RL

is a FORTRAN program in relocatable
binary form stored in 1 to 9 files

Once you have placed the program in memory, you can
•

run it with the START command

•

create an .SV file with the SAVE command

•

debug the program with ODT

For a list of the options that LOAD accepts, see the chapters
PALS ABSLDR and the FORTRAN loader.

3-39

the

MAKE
3.32

OS/8 KEYBOARD COMMANDS

MAKE

The MAKE command runs TECO and opens the file you specify for
The format is

output.

MAKE output:file
If you omit the device name and the file extension, MAKE
and .PA.

assumes

If the file you specify already exists, MAKE prints the message
7.!3IJPERSFDING
-----For example, this command
.MAKE DTA1:TEXT.TX
is the same as typing
.R TEeD
!EWDTA1:TEXT.TX$$
For further information, see the OS/8 TECO Reference Manual.

3-40

DSK

OS/8 KEYBOARD COMMANDS
3.33

MAP

The MAP command produces a map -- usually on the line printer -- of
all the memory locations used by the absolute binary files you specify
in the command line.
The format is
MAP output:file<input:filel, .•• input:file9
MAP accepts a minimum of nine files as input in a single command line.
To specify more than nine files, press the ESCAPE key after the ninth
entry. This causes the Command Decoder to print an asterisk
(*),
indicating that you may continue to specify input files, terminating
each with the RETURN key.
To execute this command, type another
ESCAPE.
If you omit the extension from an input file name, MAP assumes .BN.
If you omit the output device, MAP sends the map to the line printer.
To display a map on the terminal, use the /T option.

3.33.1

MAP Output

MAP depicts MEMORY as a series of lOa-digit lines (in octal), grouped
in pairs. Each pair of lines represents one memory page~ each digit
in a line represents one memory location. Depending on the contents
of a location, MAP prints the digit 0, 1, 2, or 3.
•

a means the program did not load into this location.

•

1 means the location was loaded into once.

•

2 means the location was loaded into twice.

•

3 means the location was loaded into three times.

If you specify the terminal as the output device, MAP prints a set of
octal numbers across the top of the map. Each number -- ranging from
00 to 77 -- is the vertical co-ordinate for the column of digits below
it.
To determine the memory address of any entry in the map, add the
line number at the left to the octal number directly above.
For examples of MAP output, see the BITMAP chapter in this manual.

3.33.2

MAP Options

You can modify MAP output with the following options:

• /n
• /R

MAP confines the construction of maps to the field
specify as n.

you

MAP resets the map just constructed in memory to look
as though nothing has been read in. If you specify the
wrong file in a MAP command, use the /R option at the
end of the line.

3-41

OS/8 KEYBOARD COMMANDS

•

MAP reads every absolute binary program in an input
file.
In normal operation, MAP accepts only the first
file.

•

MAP changes the format of the output map -- that is, it
sends a map to the line printer in terminal format and
vice versa.

The MAP command runs CCL.SV and BITMAP.SV.

3-42

MEMORY

OS/8 KEYBOARD COMMANDS
3.34

MEMORY

The MEMORY command finds the highest field available
limits the fields available in software.

hardware

The format is
MEMORY
or
MEMORY n
where
is an octal number from 0 to 7 representing the number
of fields
(each containing 4K words of memory) in
software.

For example, this command line

.MEMORY 3
limits the amount of memory available in the system to 16K words.
The following list shows all the values of n and their meaning:

1
2
3
4
5
6
7

all available memory fields
8K words of memory
12K words
16K words
20K words
24K words
28K words
32K words

To find the amount of memory currently being used by OS/8, type the
command with no argument.
The following output indicates that a
MEMORY 4 command, entered previously, has restricted a 32K system to
only 20K words of available memory •

• MEMORY
201(/32""

MEMORY

If the system is using all available memory, the
total amount. For example:

• MEMORY
MEMORY

321(

The MEMORY command causes the execution of CCL.SV.

3-43

Monitor

prints

the

MUNG
3.35

OS/8 KEYBOARD COMMANDS

MUNG

The MUNG command lets you call a predefined TECO macro to operate on a
source file. The format is
MUNG device:file,text
where
device:file

is a file containing a TECO macro.
If you omit
the extension, MUNG assumes .TE. If you type a
period after the file name, MUNG assigns no
extension.

text

is an argument to the macro.
requires no argument, omit the
command line.

If the macro
comma in the

MUNG reads the first page of the specified file -- the macro -- into
Q-register Y.
Then it enters the text into the TECO text buffer.
With the pointer at the end of the buffer, TECO executes the macro in
Q-register Y. If the text argument is too long, MUNG prints the error
message

COMMAND TOO LONG
For complete information on TECO, see the TECO Reference Manual.

3-44

OS/8 KEYBOARD COMMANDS
3.36

OOT

ODT

The ODT command enables you to debug the program currently in memory,
control its execution, and make alterations by typing ODT instructions
at the terminal.
The format is
ODT
Once you have entered the command with the RETURN key, you may examine
and modify any memory location of the program currently in memory or
use the breakpoint feature to control program execution.
When using ODT to debug a program, you must call I/O devices by their
permanent names.
As long as ODT is in control of the system, all
user-defined names are invalid.
For a complete discussion of ODT, see the ODT chapter.

3-45

P~L
3.37

OS/8 KEYBOARD COMMANDS
PAL

The PAL command assembles a PAL8 source file,
binary file with a .BN extension.

producing

absolute

The format is
PAL output:binary.BN,output:listing.LS,CREF.LS<input:source.PA
where
output:binary.BN

is an absolute binary
device

file

and

output

output:listing.LS

is an optional listing file
device

and

output

output:CREF.LS

is an optional file used by CREF

input:source

is a PAL8 program and an input device

If you omit the extension in the input specification, PAL assumes PA.
If you omit the extension from the output files, PAL assumes BN and
LS.
The following example causes PAL to assemble a file
and produce a listing file •

called

BOOMER.PA

• PAL BOOMER,BOOMER~BOOMER.PA
PAL can recall arguments from any previous COMPILE, LOAD,
command that you enter on the same day.

EXECUTE

The /C option causes PAL8 to chain to the CREF program, which produces
a cross-reference file and assigns it the name of the second output
file.
For a complete list of PAL options, see the PAL8 chapter in
Language Reference Manual.
PAL runs CCL.SV and PAL.SV.

3-46

the

OS/8

OS/8 KEYBOARD COMMANDS
3.38

The PRINT command runs a program called LPTSPL if you have such a
program on your OS/8 system. LPTSPL can be a user-written program or
a program obtained from DECUS.

3-47

PUNCH
3.39

OS/8 KEYBOARD COMMANDS

PUNCH

The PUNCH command runs PIP and punches the file specified on the paper
tape. The format is
PUNCH output:file<input:file
If you omit the output specification, PUNCH sends the file to PTP.

3-48

OS/8 KEYBOARD COMMANDS

3.40

The R command loads and starts a .emory-image
device. The format is

file

from

the

system

R file.SV
R writes the block number of the first block in the file
7747 in field O.

location

Since the R command loads files from the system device only, you may
not specify an input device other than DSK in the command line. If
you omit the file extension, R assumes SV.
For example, this command

.R TEST
looks for a program called TEST.SV on the system device and loads
executes it.

and

The R command differs from the RUN command in that it does not send
the Core Control Block to the system device. To save a program that
does not have its Core Control Block in the usual place on SYS, you
must include all the optional arguments in the SAVE command.
Always use R to call a system program, since these do not have to be
resaved.
If you want to run a program that you eventually plan to
update (using ODT, for example) and then save, use the RUN and GET
command rather than R.

3-49

RENAME
3.41

OS/8 KEYBOARD COMMANDS

RENAME

The RENAME command lets you change

name of a file.

The format is

RENAME device:newname<device:oldname
where
device:oldname

is the file name you want to change
the device on which it is located

device:newname

is the new name and the same device

You must specify the same device for input and output in
line.

the

and

command

RENAME changes the input file name and prints the message FILES
RENAMED on the screen, followed by the old file name. Thus, if you
type
.RENAME RXA1:FILE.PA~RXA1:RECORD.PA
the file RECORD.PA on RXAI becomes FILE.PA.
contents of the input file remain the same.

The creation date and the

You may use wildcards with the RENAME command.

3.41.1

RENAME Options

RENAME provides the following options:

• IC
• 10
• IV
• IT

RENAME changes the name of the input file
has the current date.

only

RENAME changes the name of the input file
does not have the current date.

only

RENAME changes the name of all files on a device except
the ones specified as input in the command line.
RENAME changes the name of the input file and gives
the current date.

RENAME runs CCL.SV and FOTP.SV with the IR extension.

3-50

OS/8 KEYBOARD COMMANDS
3.42

RES

The RES command runs the RESORC program and lists the device
present on an OS/8 system. The format is

handlers

RES output:file<input:file

For a description of the input and output specifications for RES and a
list of RES options, see the chapter on the RESORC program in this
manual.

3-51

REWIND
3.43

OS/8 KEYBOARD COMMANDS

REWIND

The REWIND command runs the CAMP program and issues a rewind command
to a specified OS/8 device controller. This command operates in the
same way as the CAMP REWIND command. For a complete description of
this command, see the CAMP chapter in this manual.

3-52

RUN

OS/8 KEYBOARD COMMANDS
3.44

RUN

The RUN command loads a memory image (SV) file into memory,
transfers
its Core Control Block to the system device, and begins execution at
the starting address of the program.
It places the block number of
the first block in the file into location 7747 of field O.
The format is
RUN input:file
If you enter a file name without an extension, RUN
must specify a device; RUN does not assume DSK.

assumes

For example, the following RUN command
RXAI •

STARTs

• RUN RXA2:PROG.SV

3-53

GETs

and

SV.

You

PROG.SV

SAVE
3.45

OS/8 KEYBOARD COMMANDS

SAVE

The SAVE command makes an executable binary file of the program
currently in memory, assigns it a name, and stores it on a device. If
you do not specify the locations in memory that you want to save, the
SAVE command automatically looks for the information on the current
Core Control Block.
The format is
SAVE device:file fnnnn-fmmmm,fpppp;fssss=cccc
where
fnnnn

is a 5-digit octal number representing the
field
(f)
and
starting
address of a
continuous portion of memory that you want to
save

fmmmm

is the final address (in the same field)
that part of memory you intend to save

fpppp

is a 5-digit octal number representing the
address of one location in memory. A single
address causes SAVE to save the entire page
on which the location occurs

;fssss

is a 5-digit octal number representing the
starting address of the program you want to
save

=cccc

is a 4-digit octal number representing
contents of the Job Status Word

the

If you omit the extension on the file name, SAVE appends SV.
If you
omit the other arguments, SAVE finds the locations it requires in the
current Core Control Block.
The SAVE command places the following restrictions on arguments in the
command line.
•

You must specify the output device.
DSK.

SAVE does not default

•

The beginning and ending addresses of an area
(fnnnn-fmmmm) must both appear in the same field.

•

When you specify a location or an area on one page, SAVE takes
the entire page.
If you call for another part of that same
page in the same command line, SAVE sends an error message to
the terminal,
informing you that it has already saved the
page.

•

If you omit the field number, SAVE assumes field O.

memory

saving locations 7600-7777 in fields 0-2. The resident
• Avoid
monitor code resides in these areas of memory. To avoid
accidentally destroying a portion of the Monitor,
SAVEs involving 7600 to fields above field 2.

restrict

you specify an address on an odd-numbered page, SAVE can
• If
save it only if it also saves the preceding page. The system
does this automatically.

3-54

OS/8 KEYBOARD COMMANDS
3.45.1

The Job Status Word

The Job Status Word, which resides in memory with the file
(at
location 7746 in field 0), indicates what parts of the file use memory
and how.
Meaning

Bit Condition
Bit 0=1

File does not load into
field 0 (0000-1777).

locations

0-1777

Bit 1=1

File does not load into
field 1 (10000-11777).

locations

0-1777

Bit 2=1

Program must be reloaded before it can be
restarted because it modifies itself during
execution.

Bit 3=1

Program being run will
monitor.

Bit 4=1

A memory image file that was generated
the LINKER contains overlays.

Bit 5

Reserved for 05/78 system programs.

Bits 6-9

Unused, and reserved for future expansion.

Bit 10=1

Locations 0-1777 in field 0 need not be saved
when calling the Command Decoder overlays.

Bit 11=1

Locations 0-1777 in field 1 need
when calling the USR.

The Monitor runs the SAVE command.

3-55

not

destroy

not

the

BATCH
through

saved

SET
3.46

OS/8 KEYBOARD COMMANDS
SET

The SET command enables you to modify the operating characteristics of
OS/8 by specifying certain attributes of system programs in the
command line. Use SET to make frequently required changes in system
programs, especially those with I/O handlers.
The format is
SET device [NO] attribute [argument]
where
device

indicates the handler of the device you
to modify

want

indicates that the following
not apply

does

attribute

is the characteristic you want to modify

argument

is an optional parameter required by
SET commands

attribute

For details, see the chapter on the SET program in this manual.

3-56

certain

SKIP

OS/8 KEYBOARD COMMANDS
3.47

SKIP

The SKIP command runs the CAMP program and advances over the number of
files or records on a magnetic tape that you specify. The format is
SKIP MTAn:

nnnn keyword

where
MTAn

is any magnetic tape drive

nnnn

is an unsigned decimal number representing
of files you want to advance over

keyword

specifies FILE, RECORD, or EOD (end-of-data)

If you omit nnnn or EOD, SKIP assumes 1.
SKIP assumes FILE.

you

omit

the

number

keyword,

For example, this command
~SKIP

MTAO:2 RECORDS

advances the tape on MTAO forward two records.
For complete information on the SKIP command, see the chapter
CAMP program in this manual.

3-57

the

START
3.48

OS/8 KEYBOARD COMMANDS

START

The START command begins execution of the memory image program
currently in memory at the address you specify in the command line.
If you omit the address, START uses the starting location in the
current Core Control Block.
The format is
START fnnnn
where
fnnnn

is a 5-digit octal number representing a field (f)
and
the location in memory (nnnn)
you want to use as a
starting address

For example, this command

.!.START 10555
starts executing the program currently in memory at
field 1.

location

555

This command

.START
starts the program at
Control Block.

the

address

The Monitor runs the START command.

3-58

contained

the

current

Core

SQUISH

OS/8 KEYBOARD CO~NDS
3.49

SQUISH

The SQUISH command eliminates any embedded empty files on
you specify for input.

the

device

The format is
SQUISH device
Before it executes a command, SQUISH prints a message to ask
are sure you have specified the right device. For example:

you

.SQUISH RXA1:
ARE YOU SURE'!'
If you want to continue, type Y.

If not, type any other character.

If you specify both an input and an output device in the command line,
SQUISH copies all the files from the input device to the output device
and eliminates any embedded empty files. For example:
~SQUISH

RXAO:<RXAl

If the output device is a system device, SQUISH always
system programs.
NOTE
An error during a SQUISH can corrupt the
entire contents of a device in a way
that may not be immediately apparent to
you.
Therefore, do not use SQUISH
unless you have a copy of both the
system programs and your other files.
SQUISH runs CCL.SV and PIP.SV with the /S option.

3-59

preserves

the

SUBMIT
3.50

OS/8 KEYBOARD COMMANDS

SUBMIT

The SUBMIT co~and performs batch processing with optional spooling to
a file-structured output device. SUBMIT runs multiple programs and
sequences of system commands that require little or no interaction
with the user or operator.
The format is
SUBMIT spool device:<input:file
where
spool device:

is optional

input:file

is an input file name and device. If you omit the
device and extension, the system assumes DSK and
B1.

For a complete discussion of the BATCH program, see the BATCH chapter.
SUBMIT runs CCL.SV and BATCH.SV.

3-60

TECO

OS/8 KEYBOARD COMMANDS
3.51

TECO

The TECO command summons the TECO editor, opens the files you
for input, and creates an output file.

specify

The format is
TECO output:file<input:filel, .•• input:file5
If you omit the output specification, TECO does an edit backup on the
input file you specify. If you omit the input file extension, TECO
assumes PA.
TECO reads the first page of the input
before it returns control to you.

file

into

the

text

buffer

TECO remembers the name of the output file.
Thus, the next TECO
command you enter without arguments will use this file for input.
For complete information, see the TECO section in
Reference Manual.

3-61

the

OS/8

Language

TERMINATE
3.52

OS/8 KEYBOARD COMMANDS

TERMINATE

The TERMINATE command causes the system to emulate a terminal with
knowledge of disk drives, processor, or memory. The format is
TERMINATE
This command runs eCL.SV.

3-62

TYPE

OS/8 KEYBOARD COMMANDS
3.53

TYPE

The TYPE command displays on the terminal the contents
you specify for input. The format is

the

files

TYPE input:filel, ••• input:file5

•

TYPE displays the contents of each input file on the terminal in the
same order that you enter them in the command line. Although the
command accepts no more than five files in a line, you can extend this
number with wildcards.
For example, this command displays all files with a BS extension

3.53.1

TYPE Options

TYPE provides the following options:
TYPE displays only files with the current date.

•

TYPE displays all the files on a device except the ones
you specify.

•

TYPE prints each file name on the terminal, followed by
a question mark. To display the file, type Y. To skip
it, type any other character.

TYPE displays only files with a noncurrent date.

TYPE runs CCL.SV and FOTP.SV.

3-63

UA,UB,UC
3.54

OS/8 KEYBOARD COMMANDS

UA, UB, and UC

The UA, UB, and UC commands let you store CCL commands and their
arguments in temporary files and recall them for later use. Unlike
other commands that remember arguments, UA, UB, and UC do not forget
command lines that you have entered on previous days. This is because
the system does not delete the files each time the qate changes.
The format is
UA
UB
UC

command line

where
command line

is the CCL command with arguments that you want to
recall

For example, this command
.UA COpy

RXA1:~DSK:RECALL.BS

stores the COpy command and its arguments in
execute the command, type

temporary

file.

Note that you can store and recall only three commands at a time.
Use UA, UB, and UC to recall command lines
BATCH job.

3-64

that

recur

throughout

UNLOAD

OS/8 KEYBOARD COMMANDS
3.55

UNLOAD

The UNLOAD command
•

turns a magnetic tape controller off line and rewinds the
tape, returning to the CAMP program during the rewind. To use
the magnetic tape after the UNLOAD command, you must turn it
on line manually.

•

unloads TC08 and TD8E DEC tapes from their reels.
UNLOAD
rewinds the DEC tape on the unit you specify, selects a
different unit, and returns control to CAMP for another
command.
This DECtape unit cannot be used until you issue
another legal command -- for example, an ASSIGN command -- to
the DECtape controller.

•

write-locks an RK8E disk.

The format is
~UNLOAD

device

where
device

is a magnetic tape, a TC08 or
disk

UNLOAD runs CCL.SV and CAMP.SV.

3-65

TC8E

DECTAPE,

RK8E

VERSION
3.56

OS/8 KEYBOARD COMMANDS

VERSION

The VERSION command prints the version numbers of the OS/8 Monitor and
the CCL program. The format is
VERSION

3-66

ZERO

OS/8 KEYBOARD COMMANDS
3.57

ZERO

The ZERO command clears the directory of the device
creating an empty file directory. The format is

you

specify,

ZERO device
For example, the following example clears the directory of RXAI •
• ZERO RXA1:
Use ZERO only on devices that contain user programs and data files.
If you zero the system device, you will destroy the system programs.
ZERO will not clear the directory of SYS until it has printed a
message to ask if you are sure you want to proceed. If you do, type
Yi
if you do not, type any other character.

3-67

CHAPTER 4
THE OS/8 SYMBOLIC EDITOR

4.1

INTRODUCTION

The Editor allows you to create and modify ASCII source files.
These
files may contain assembly language programs, FORTRAN and BASIC
programs, or any other information that has the format of character
strings.
The Editor is a helpful tool; however, it must be told precisely what
to do.
You direct its operation by typing commands in the form of a
single letter or a letter with arguments and, in most cases, pressing
the RETURN key directly after the command line.
This chapter describes the procedures you follow to create a file
the commands you use to modify it.

4.2

and

CALLING THE EDITOR

The CREATE and EDIT commands call and run the OS/8 Editor.
The CREATE command summons the Editor to let you open and write a
fIle. The format is

new

CREATE outdev:file
CREATE accepts no input specifications and only one file name and
device for output.
You provide the input by typing in text at the
terminal.
After you press the RETURN key to execute the command,
the system
Editor displays a number sign (t) on the screen to indicate that it is
ready to receive your first instruction.
Thus,

.CREATE RXA1:RUN1.PA
!
opens a file named RUNl.PA on output device RXAI.
To enter text, you must put the Editor into text mode with the I or
instruction.
(For details on text mode, see Section 4.3.1.)
The EDIT command summons the OS/8 Editor to let you retrieve and
on a source program previously stored as a file. The format is
EDIT outdev:file=indev:filel, ... indev:file9

4-1

work

THE OS/8 SYMBOLIC EDITOR
The Editor signals with a number sign (t) as soon as it
accept your first instruction.

ready

To work on a source program that you have created and stored as a file
(or sequence of files), enter the file or files as input in the EDIT
command line. EDIT will accept up to nine input files in a line.
The Editor allows only one output file in a command line.
You must
specify an output file to receive the modified version of your source
program.
For example, the following command opens input file TABLE.FT on RXAO
and a file called FILEl.FT on RXAI for output (The Editor signals when
ready.) :

.EDIT RXA1:FILE1.FT<RXAO:TABLE.FT
t

To cause the Editor to read in the first page of the input file,
type
R in response to the number sign.
(For details on Editor commands,
see Section 4.3.2.)

4.3

MODES OF OPERATION

The OS/8 Editor operates in two modes:
mode.

the command mode and the

text

In the command mode, the Editor prints a t on the terminal to indicate
that it is waiting for you to type a command on the keyboard.
In text mode, the Editor accepts anything you type at the keyboard
part of the file you are creating or modifying.

The key commands in Table 4-1 enable you to transfer between modes
return control to the Keyboard Monitor.

Table 4-1
Editor Key Control Commands

Command

Mode in Which
Used

Meaning

CTRL/C

Text and Command
Modes

Returns
control
to
the
Keyboard Monitor.
All text
that has been edited is lost.
CTRL/C should be used with
utmost
caution,
since no
output file will be stored.

CTRL/O

Command Mode

Stops the listing of text.
Returns control to Command
Mode.

CTRL/L

Text Mode

Returns the Editor to Command
Mode.

4-2

THE OS/8 SYMBOLIC EDITOR
4.3.1

Text Mode

To put the Editor in text mode so that you can enter a new file -- or
add to one that you have already created -- type the Insert or Append
command. The format is:
I RETURN
or
A RETURN
These commands cause the Editor to place the text that you enter at
the terminal into its text buffer. If you use the Insert command, the
Editor stores the text before the first line of any existing material
in the buffer. The Append command instructs the Editor to place the
text you enter after the last line of existing text in the buffer.
The Editor accepts text in both upper and lower case.
To enter a line of text that you have typed on the terminal, press the
RETURN key.
For example:
II

READ OF THE BUFFER
or

IA
BOTTOM OF THE BUFFER
Before you type RETURN, read the line over for errors.
Make
corrections with the DELETE key or the CTRL/U key command. DELETE
erases the last character you typed. CTRL/U deletes the entire line.
(CTRL/U is equivalent to typing DELETE back to the beginning of the
line.)
To correct a line that you have sent to the buffer with RETURN,
must put the Editor in command mode with CTRL/L and use
appropriate editing commands (see Section 4.3.2.4).

you
the

The buffer holds approximately 5600 characters (decimal).
When 256
locations remain, the Editor rings the warning bell on the terminal.
From this point until the buffer is full,
typing RETURN causes the
Editor to enter a line of text, then switch to command mode and ring
the terminal bell. You may continue to enter text by this method one
line at a time until the Editor detects the absolute end of its
buffer.
To continue, you must first empty the buffer.
The Page command
enables you to send the contents of the buffer
or any part of
it -- to an output device. To use the Page command, return to command
mode with CTRL/L. The format of the command is
P RETURN
or
nP RETURN
or
m,nP RETURN
4-3

THE OS/8 SYMBOLIC EDITOR
where
n

is a line you want to send to an output device.

n,m

is a sequence of lines (n through m)
to send to an output device

that you wish

The P command automatically appends a form feed to the output, thus
producing a page of text. This allows you to paginate the contents of
your file.
Before you start typing in the next page, make sure that no text
remains in the buffer. To do this, use the Kill command (see Section
(to
4.3.2.3), which clears the buffer. Then type the Append command
put the Editor back in text mode) and continue entering your source
program.
To return to command mode at any point, type CTRL/L.
To end the session -- that is, to place all remaining text in the
output file, close the file,
and return control to the Keyboard
Monitor -- use the Exit command. The format is:
E RETURN

4.3.2

Command Mode

In command mode, the Editor performs the operations you specify on the
text in the buffer.
To enter text into the buffer from your input
command. The format is:

device,

use

the

Read

R RETURN
The Read command instructs the Editor to read a page of text from an
input device into the buffer -- that is,
to read text until it
encounters a form feed character.
If the buffer contains text
already, the Editor adds the new page to It.
The Editor provides five types of command:
Editing, and Search.

Input,

Listing,

Output,

Each command consists of a single letter, preceded optionally by
or two numeric arguments. The letter Indicates the operation:
arguments in most cases tell the Editor which lines to act upon.
Enter the commands after the number sign prompt in
The general format is
X RETURN
or
nX RETURN
or
m,nX RETURN

4-4

upper

case

one
the
only.

THE OS/8 SYMBOLIC EDITOR
where

is a command

m,n

are line numbers (m must be less than n.)

Except for noted exceptions, you terminate the command with the RETURN
key.

4.3.2.1 Input Commands - Input commands instruct the Editor to accept
text from the terminal (text that you type in) or from an input device
(text that you have stored as a file). To execute the commands,
type
RETURN key.
Note:
•

Special characters, including lower-case letters may be input
to the file.
The ESCape character is echoed as a dollar sign
($) for readability.

•

In these commands, the Editor ignores ASCII codes 340 through
376.
These codes include the codes for the lower-case
alphabet (ASCII 341-372). The Editor returns to the command
mode only after encountering a form feed or when the text
buffer becomes full.
Table 4-2
Editor Input Commands

Command

Meaning

Append the text being typed at the keyboard until a
form feed (ASCII 214 or CTRL/L) is encountered. The
form feed returns control to command mode.
Text
input following the A command is appended to whatever
is currently in the text buffer.

Insert whatever text is typed before line 1 of the
text buffer.
The form feed (CTRL/L) terminates the
insertion process and returns control to the command
mode.

Insert whatever text is typed (until a form
typed) before line n of the text buffer.

Read one page from the input device specified to the
EDIT or CREATE commands, and append the new text to
the current contents of the buffer.
If no input file
was indicated or if no input remains, a question mark
(?) is printed and the Editor returns to the command
mode.

4-5

feed

THE OS/8 SYMBOLIC EDITOR
4.3.2.2 Listing Commands - List commands display on the terminal all
or part of the contents of the text buffer. Type RETURN key to
execute.
Table 4-3
Editor Listing Commands
Meaning

Command
L

List entire
terminal.

List line n of the text buffer on the terminal.

m,nL

List lines m through n of
terminal.

Get and list the next line that has a
label
associated with it. A label in this context is any
line of text that does not begin with one of the
following:
space

TAB
RETURN

contents

(ASCII
(ASCII
(ASCII
(ASCII

the

text

buffer

the

240)
257)
211)
215)

At the termination of a G command, control returns to
the command mode with the current line counter equal
to the line just listed.
nG

Get and list the first line that begins with a label,
starting the search at line n.

Print the number of available memory locations in the
text buffer.
The Editor returns the number of
locations on the next line. To estimate the number
of characters that can be accommodated in this area,
multiply the number of free locations by 1.7.

The Editor remains in command mode after a list command and updates
the value of the current line counter to be equal to the number of the
last line prin~ed.

4.3.2.3 Output Commands - Output commands send text from the buffer
to a device you specify for output. Type RETURN key to execute.

4-6

THE OS/8 SYMBOLIC EDITOR
Table 4-4
Editor Output Commands
Command
E

Meaning
Output the current buffer and transfer all remaining
pages of input to the output file:
close the output
file and enter it in the directory. When this buffer
is full,
the text is output to the indicated output
file. The E command automatically outputs a form
feed after the last line of output, and returns
control to the Monitor.
NOTE
If you do not use the E command to close
a
file after editing, any changes,
additions, or corrections
will
not
appear in the output file. Thus, the E
command should usually be the
last
command that you enter in an editing
session (also see Q command).

Write the entire text buffer to the output file.

Write line n of the text buffer to the output file.

m,nP

Write lines m through n,
file.

inclusive,

the

output

NOTE
The P command automatically appends a
form feed to its output, thus producing
a page of text. This command allows you
to paginate your listing. However, if
the K command is not used after a P
command, the text remains in the buffer
and is again output with the new text
read in before the next P command.

Kill the buffer.
buffer.

All text is deleted from

the

text

NOTE
The Editor ignores the commands nK or
m,nK, with the result that you cannot
destroy the buffer by mistyping a List
command (m, nL).
(continued on next page)

4-7

THE OS/8 SYMBOLIC EDITOR
Table 4-4
(Cont.)
Editor Output Commands
Command

Meaning

Immediate end-of-file. The Q command causes the text
buffer to be output.
The file
is then closed
(entered into the directory with the current date as
its creation date),
and control returns to the
Monitor.

Write the current buffer to the indicated output file
and read the next logical page. The N command is
equivalent to a P, K, R command sequence.

Write the current buffer to the output file, kill the
buffer, and read the next logical page. This is done
n times until the nth logical page is in the text
buffer.
Control then returns to command mode.
(The
N command cannot be used with an empty text buffer,
since there is no text to be written.
If the buffer
is empty when the N command is attempted, a question
mark
(?)
is printed.)
For example, to read in the
fourth page of a file, give the commands
!R (to read the first page)
and

!3N (to read three more pages)

The V command causes the entire text buffer to be
listed on the line printer. The V command only works
with the LA78 line printer.
It does not work with
the LQP78 line printer.

List line n of the buffer on the line printer.

m,nV

List lines
printer.

through

inclusive,

the

line

4.3.2.4 Editing Commands - The following commands permit deletion
alteration of text in the buffer. Type RETURN key to execute.

4-8

THE OS/8 SYMBOLIC EDITOR
Table 4-5
Editing Commands: Deletion and Alteration
Command

Meaning

Change the text of line n to the line(s) typed after
the command is entered (typing a form feed terminates
the text input). The C command is equivalent to a 0
command followed by an I command.

m,nC

Delete lines m through n, and replace with the text
line(s)
typed after the command is entered.
(Typing
CTRL/L indicates the end of the changed lines.)
The C command utilizes the text collector in altering
text.

Delete line n from the buffer.

m,nD

Delete lines m through n from the buffer.

Yank (read) in n pages from the input file into
text
buffer,
without writing any output.
example,

the
For

!5Y
reads through four logical pages of input, deleting
them without producing output.
The fifth page is
read into the text buffer, and control automatically
returns to command mode.
NOTE
Use this command with caution;
it
irrevocably deletes the contents of the
text buffer.
m,n$pM

Move lines m through n directly before line p in the
text buffer. The $ character means that you type the
dollar sign key,
not ESCape, ALTMODE, or other
possibilities.
The old occurrence of the moved text
is then removed. This command can move one line, but
it needs three arguments.
You can provide three
arguments by specifying the same line number twice.
For example,

moves line 6 in front of line 21 .

----~-~----~------~.~~~----------------------------------------------------~

4.3.2.5 Search Commands - Search commands cause the Editor to search
a text for occurrences of characters and strings that you specify.
The Editor sets the current line pointer at the line containing the
characters you want to find.
Search commands are discussed in detail in Section 4.4.

4-9

THE OS/8 SYMBOLIC EDITOR
Tab-Ie 4-6
Editor Search Commands
Command

Meaning

Perform a character search (Section 4.4.1) •

Perform an interbuffer search for
(Section 4.4.2.2).

character

strings

Look for next
being sought.

string

currently

ESC($)

Perform an intrabuffer character string search.

occurrence

the

4.3.2.6 Special Command Mode Characters - The Editor
following special characters in command mode:
Table 4-7
Editor Special Characters:
Character
Period (.)

recognizes

the

Command Mode
Function

The Editor assigns an implicit decimal
number
to the line on which it is
currently operating. At any given time
the period, which represents this decimal
number, may be used as an argument to a
command.
In the following example, the L
command is used since it allows text to
be listed. Typing

means list the current line.

Typing

!.-l,.+lL
means list the line preceding the current
line, the current line, and the line
following it, and then update the current
line counter to the decimal number of the
last line printed.
The Editor updates
the current line counter, represented by
the period, as follows:
•

After an R (Read page) or A (Append)
command, the period is equal to the
number of the last line in the
buffer.

•

After an I (Insert)
or C (Change)
command,
the period is equal to the
number of the last line entered.
(continued on next page)

4-10

THE OS/8 SYMBOLIC EDITOR

Table 4-7
(Cont.)
Editor Special Characters: Command Mode
Character
Period (.)

(Cont.)

Slash (I)

Function
•

After an L (List) or S (Search)
command, the period is equal to the
number of the last line listed.

•

After a D (Delete)
command, the
period is equal to the number of the
line immediately after the deletion.

•

After a K (Kill) command, the period
is equal to O.

•

After a G (Get and list) command,
the period is equal to the number of
the line displayed by the G.

•

After an M (Move)
command,
the
period is not updated and remains
whatever it was before the command.

The symbol slash (I) has a value equal to
the decimal number of the last line in
the buffer. It may also be used as an
argument to a command. For example,

means list from line 10 to the end of the
buffer.
LINE FEED Key

When the Editor is in command mode,
pressing the LINE FEED key has the same
effect as

•• +lL
which causes the Editor to display the
line following the current one and to
increment the value of the current line
counter (dot) by one. LINE FEED does not
perform this function while in the text
mode.
Right-Angle Bracket (»

Typing the right-angle bracket (»
while
in command mode is equivalent to typing

•• +lL
and causes the Editor to echo> and then
display the line following the current
line. The value of the current line
counter is increased by one so that it
refers to the last line displayed.
(continued on next page)

4-11

THE OS/8 SYMBOLIC EDITOR
Table 4-7
(Cont.)
Editor Special Characters: Command Mode
Character

Meaning

Left-Angle Bracket «)

In command mode, typing the left-angle
bracket «) is equivalent to typing
t.-1L
and causes the Editor to echo < and then
print the line preceding the current
line. The value of the current line
counter is decreased by one so that it
refers to the last line printed.

Equal Sign (=)

In the command mode, using the equal sign
in
conjunction with either the line
indicator period (.) or slash (I)
causes
the Editor to display the decimal value
of the argument preceding it.
You can
find by this method the number of the
current line (.=nnnn) or the total number
of lines in the buffer (/=nnnn).

Colon (:)

The colon performs exactly the
function as the equal sign (=).

ESCape Key

When the Editor
is in command mode,
pressing
the
ESCape key signals an
intrabuffer character search.
It echoes
as a dollar sign
($)
on the terminal
screen. When the Editor is in text mode,
the Escape key echoes as a dollar sign,
but it is stored in the file as an ESCape
character (033).

4.4

same

SEARCHING A TEXT

The following search commands enable you to make additions and
corrections in your text. The Editor searches for occurrences of the
single character or character string that you specify.

4.4.1

Single-Character Search -- the S Command

The format of a single-character search is:
S RETURN
X

where
X

is the alphanumeric character you want
for.

4-12

THE OS/8 SYMBOLIC EDITOR
To specify a line or a sequence of lines that you want to search,
the following format:

use

nS RETURN
n,mS RETURN
For example, the following command causes the Editor to
20-40 for an occurrence of the character B:

lines

120, 405

The Editor displays the character it is searching for and everything
preceding it in the line. At this point you can perform the following
operations.
•

Delete the entire portion of the line not yet displayed and
terminate the line and the search by pressing the RETURN key.

•

Delete characters from right to left by typing the DELETE key.

•

Insert characters after the last one printed simply by
them.

•

Insert a carriage return/line feed,
thus dividing the line
into two, by pressing the LINE FEED key followed by CTRL/L.

•

Continue searching the line to the
search character by typing CTRL/L.

•

Change the search character in the line and continue searching
by typing CTRL/G(BELL) followed by the new search character.
This allows all editing to be done in one pass.

•

Type CTRL/G(BELL) twice to terminate the command.

occurrence

typing

the

The usual form of the character search command is #.S, followed by the
RETURN key and the character to be located. Use this form of the
command to modify the current line.

4.4.2

The Character String Search

The Editor can search the buffer for any unique combination of
characters.
In a character string search, the Editor sets the current
line pointer at the line containing the first occurrence of the
string.
Two types of character string search are available:
interbuffer.

intrabuffer

and

4.4.2.1 Intrabuffer String Search - In an intrabuffer search, the
Editor scans the text in the buffer for the string you specify.
If it
fails to find an occurrence of the string, it prints a question mark
and returns to command mode.
To initiate an intrabuffer search, type the ESCape key in response to
the Editor's prompt and enter the string.
(ESCape echoes as a dollar
sign.) The string must occur in one line.

4-13

THE OS/8 SYMBOLIC EDITOR
If you wish to begin the search at line 1 of the buffer, terminate the
string with a single quotation mark ('). If you wish to begin the
search at the current line + 1, use a double quotation mark
(n)
to
terminate the string.
The format of an intrabuffer search command is:
$string' RETURN
or
$string" RETURN
where
$

is a prompt character printed by the Editor

string

is a group of up to 20 ASCII characters

(single quote)

causes the Editor to begin searching at

line

1 of the buffer

(double quote)

causes the Editor
current line +1

begin

searching

NOTE
Do not
include
single
or
double
quotation marks in a string because the
Editor recognizes them as instructions.
The Editor places the number of the first line containing the search
string in the current line indicator and displays the prompt sign (I).
To display the number on the terminal,
type the indicator dot
(.)
followed by an equal sign. The format is:

=
You can use a line number you obtain this way as an
Editor command.

argument

any

For example, the following command causes the Editor to search for the
first occurrence of the string CDFIO, beginning at line 1 of the
buffer:

!$CDF10'

!
The response to this command is revealed as line 35:
•• =-35

Command lines can include more than one instruction.
assume that the buffer contains the following text:
ABC DEF GJO
lA2B3C4D5E6
.STRINGABCD

4-14

For

example,

THE OS/8 SYMBOLIC EDITOR
To list the line that contains ABC, type

tSABC'L

The search begins with line 1 and continues until the Editor finds the
string. The Editor sets the current line counter equal to the line in
which the string ABC occurred. The L (List) command causes the line
to be printed as follows:
ABC DEF GJO
The Editor returns to command mode, awaiting further commands.
want to find the next reference to ABC, type:

If you

t"L
In this case, the quotation marks (") cause the last string the Editor
searched for to be used again, with the search beginning at the
current line +1.
It is not necessary to enter the search string
again.
The command may be used several times in succession. For
example, if you want to find the fourth occurrence of a string
containing the characters FEWMET, type
!SFEWMET' """L
This command will list the line which contains the fourth occurrence
of that string. The L command (or any other command code) can follow
either' or". The L command causes the line to be listed if the
Editor finds the string.
To clear the text string buffer, type
tS'
The Editor responds with a question mark and clears
buffer.

the

text

string

The properties of the commands 'and " allow for easy and useful
editing, as the following example illustrates. To change the CIF 20
to CIF 10, enter the following commands:
tSDUM, 'SCIF 20"C
elF 10
INEW FIELD
The above set of instructions first causes the Editor to start at line
1 and search for the line beginning with DUM,. Then it searches for
CIF 20, starting from the line after the line containing DUM,.
The
line number of the line containing the string CIF 20 becomes the
current line number. The C command applies the instructions of the
command line to what is typed in the next line -- that is, the string
CIF 10.
Since this search feature produces a line number as a result, any
operations which require a line number will accept a string instead.
For example:
!SSTRING'+4L
lists the fourth line after the first occurrence of the text STRING in
the text buffer.

lists all lines between the two labels, inclusive.

4-15

THE OS/8 SYMBOLIC EDITOR
!$PFlUG'S
performs a character search on the line which contains PFLUG.
(Type
the search character after typing the RETURN key that enters the
line.)
In commands that include both strings and explicit numbers,
should appear first.
For example, the following commands:

strings

!l+$BAD!'L
will not list the next
correct syntax is:

line

after

the

string

BAD!

occurs.

The

t$BAD!'+lL

4.4.2.2 Interbuffer String Search -- J
Command - In an interbuffer
search,
the Editor scans the contents of the text buffer for the
character string you specify. If it fails to find an occurrence of
the string, it sends the buffer to an output file, clears the buffer,
and reads in the next page of text from the input file.
The Editor
then resumes the search at line 1 of the new buffer. When the input
file is exhausted, the Editor prints the number sign prompt (#)
and
awaits your next instruction.
If the search is successful, the Editor sets the current line
indicator equal to the number of the line containing the first
occurrence of the string.
The format for an interbuffer search is:
RETURN
$string'

where
$

is a prompt character printed by the Editor

string

is a group of up to 20 ASCII characters

(single quote)

causes the Editor to begin searching at
1 of the buffer.

line

To display the number of the line containing the string, type the
current line indicator dot (.) after the Editor's number sign prompt
(#), followed by an equal sign. The format is:

For example, the following command instructs the Editor to make an
interbuffer search for the string WRITE, beginning at line 1 of the
current buffer. The.= construction reveals that line 4 of the
current buffer contains the string.

!WRITE'
!.=0004

4-16

THE OS/8 SYMBOLIC EDITOR
To find further occurrences of the string WRITE, type the F command.
The F command searches the buffer for the last character string
entered, starting from the current line count + 1. The displayed line
following the F command line contains a number prompt sign (I), the
format you type to obtain a line number (.=), and the line number.
The result is:
:l:F

:1:.=0008

This example causes a search for the string WRITE, starting at the
current line + 1. If you have specified no output file, the J or F
command reads the next input buffer without attempting to produce any
output.
NOTE
interbuffer
Use the J command
for
searches only. After the J or F command
has processed the entire input file,
execute either an E or Q command to
close the output file.
The following commands may be used to abort the string search command,
once given:
Table 4-8
Aborting Editor String Search Commands
Command

Explanation

CTRL/U

A CTRL/U will return control to the Editor command
mode i f you type it while entering text in a string
search command.

DELETE

Pressing the DELETE key while entering tex~ for a
string search causes the text so far entered to be
ignored and allows a new string to be inserted.
The
Editor displays a dollar sign ($) in response.

4.5

EDITOR OPTIONS

The Editor provides the following options:

•

The Editor converts two or more spaces to
reading from an input device.

•

The Editor deletes the old_ copy of the output file
(if
one exists)
before opening the new output file on the
device.
If you do not specify /0, the Editor does not
delete the old copy of the output file until you have
transferred all data to the new file with the E or Q
command.

4-17

TAB

when

THE OS/8 SYMBOLIC EDITOR
4.6

EDITOR ERROR MESSAGES

Two types of error messages, nonfatal and fatal, are generated when an
error is made while running the Editor.
Nonfatal errors, such as an incorrect format in a command string or a
search for nonexistent information, cause the Editor to display a
question mark.
For example, if a command requires two arguments,
and
only one is provided,
the Editor will display a question mark (?),
perform a carriage return/line feed, and ignore the command as typed.
Similarly,
if you type an illegal or unrecognized command character,
the error message ?
will be displayed,
followed by a carriage
return/line feed;
the command will be ignored. However, if you
provide an argument for a command that does not require one,
the
argument may be ignored and the normal function of the command
performed. The following examples illustrate nonfatal errors that you
may encounter while using the Editor.
Table 4-9
Nonfatal Editor Error Messages
Condition/Message

Explanation
The buffer is empty.
requested.

7,5L

The arguments are in the
Editor cannot list backward.

17$lOM

Nonexistent information
wrong order.

This command requires two arguments
$; only one was provided.

Nonexistent command letter.

The

before the

Major errors cause control to return to the Monitor and may be due to
one of the causes listed in Table 4-2. These errors cause a message
to be printed in the form

where
n

is an error code listed in the table
indicates that control has passed to the Monitor.

These errors generally result in complete loss of the output file.

4-18

THE OS/8 SYMBOLIC EDITOR
Table 4-10
Editor Error Codes
Error Code

Meaning

Editor failed in reading a device. Error occurred in
device handler; most likely a hardware malfunction.

Editor failed in writing onto a device;
hardware malfunction.

File close error occurred.
For
output file could not be closed;
exist on that device.

File open error occurred. This error occurs if the
output device is a read-only device or if no output
file name is specified on a file-oriented output
device.

Device handler error occurred. The Editor could not
load the device handler for the specified device.
This error should not normally occur.
_____________________________________
.. ____________________

L -_____________

4.7

generally

some reason the
the file does not

SUMMARY OF EDITOR COMMANDS AND SPECIAL CHARACTERS

The command and special characters
summarized in Table 4-11.

discussed

this

chapter

are

Table 4-11
Editor Command and Special Characters
Command

Meaning

Format

Append the following text being typed at
the keyboard until a CTRL/L (form feed)
is typed. The form feed returns control
to
the
command
mode.
Text input
following the A command is appended to
whatever is present in the text buffer.

List the number of available
memory
locations in the text buffer. The Editor
returns the number of locations on the
next line.
To estimate the number of
characters that can be accommodated in
this area,
multiply the number of free
locations by 1.7.

Change the text of line n to the line(s)
typed
after the command is entered.
(Typing a CTRL/L terminates the input.)
(continued on next page)

4-19

THE OS/8 SYMBOLIC EDITOR
Table 4-11
(Cont.)
Editor Command and Special Characters
Command

Meaning

Format

-~-~-------~-~--~---~------I

C (Cont.)

m,nC

Delete lines m through n and replace with
the text line(s) typed after the command
is entered.
(Typing CTRL/L indicates the
end of the inserted lines.)

Delete line n from the buffer.

m,nD

Delete lines m through n from the buffer.

Output the text buffer and transfer all
remalnlng pages of the input file to the
output file, closing the output file and
returning to the Monitor.

Follows a string search. Look for next
occurrence of the string currently being
sought (by the J command).
NOTE

If the search fails while you are using
the F command, further commands cause
the system to prompt with a?
The file
must be closed and then reopened.
G

Get and list the next line that has a
A label in
label associated with it.
this context is any line of text that
does not begin with one of the following:
space

TAB
RETURN

(ASCII
(ASCII
(ASCII
(ASCII

240)
257)
211)
215)

command,
At the termination of a G
control goes to the command mode with the
current line indicator (.) equal to the
line just listed.
nG

Get and list the first line that begins
with a label, starting the search at line

n.
I

Insert whatever text is typed before line
1 of the text buffer.
(Typing CTRL/L
terminates the entering
process
and
returns control to the Editor command
mode. )

Insert whatever text is typed
(until a
CTRL/L is typed)
before line n of the
text buffer.
(continued on next page)

4-20

THE OS/8 SYMBOLIC EDITOR
Table 4-11
(Cont.)
Editor Command and Special Characters
Command

Format

Meaning
Interbuffer search command for character
strings
(see Section 4.4.2.2 describing
the InterBuffer Character String Search).

NOTE
If the search fails while you are using
the J command, further commands cause
the system to prompt with a?
The file
must be closed and then reopened.
K

Kill the buffer.
the text buffer.

Delete

all

text

from

NOTE
The Editor ignores the commands nK and
m,nK with the result that you cannot
destroy the buffer by mistyping a List
command (m,nL).
L

List entire contents of the
on the terminal.

List line n of the
terminal.

m,nL

List lines m through n of the text buffer
on the terminal. Control then returns to
command mode.

m,n$pM

Move lines m through n directly before
line
p in the text buffer.
The $
character represents typing the dollar
sign key, and not other possible keys.
The old occurrence of the moved text is
removed.

Write the current buffer to
file and read the next page.

Write the current buffer to the output
file,
kill the buffer, and read the next
page. This action is repeated n times
until the nth page is in the text buffer.
Control then returns to command mode.

L-_~

___________

~L-

text

buffer

the

buffer
on

the

output

You may not use the N command with an
empty text buffer. A question mark (?)
printed if you
attempt to do this.
___________ is
_________________
.______________________________

-J

(continued on next page)

4-21

THE 05/8 SYMBOLIC EDITOR
Tabl~ 4-11
(Cont.)
Editor Command and Special Characters

---------,--------rCommand

~~---------------~------_,

Format

Meaning

Write the entire text buffer to the
output file.
The P command automatically
outputs a FORM character (214) after
the
last line of output.

Write line n of the text buffer to
output file and a FORM character.

the

m,nP

Write lines m through n,
inclusive,
the output file and a FORM character.

Immediate end-of-file. Q causes the text
buffer to be output and the file closed.

Read one page from the input device and
append
the new text to the current
contents of the text buffer.
If no input
file
was
indicated or if no input
remains, a question mark (?) is displayed
and control returns to the command mode.

Character
4.4.1) •

List the entire text buffer on
printer.

List line n of the
line printer.

m,nV

List lines m through n, inclusive, on the
line printer.

Yank (read) in a logical page from the
input file,
without writing any output.
For example,

command

text

(see

buffer

Section
the

line

the

ISY
reads through four logical pages
of
input, deleting them without producing
output. The fifth page is read into the
text buffer,
and control automatically
returns to the command mode.
$(ESC)

$TEXT'

Perform a character string search for the
string TEXT.
Following a string search,
In
causes
a
search
for the next
occurrence of the string
(see Section
4.4.2.1
describing
the
Intrabuffer
Character String Search).
(continued on next page)

4-22

THE OS/8 SYMBOLIC EDITOR
Table 4-11
(Cont.)
Editor Command and Special Characters
Command

Format

.= or .•

Meaning
Typing these characters
obtains
the
current line number
(.=)
and the last
line number (/=) in the text buffer. The
number
is
printed
by
the
Editor
immediately after you type the equal
sign.
(The colon character is equivalent
to the equal sign.)

1= or I:

Equivalent to .+lL, list the next line in
the text buffer.

Equivalent to .-lL, list
line in the text buffer.

LINE FEED Key

the

preceding

Equivalent to .+lL, list the next line in
the text buffer.

Print the current Editor version number.

4-23

CHAPTER 5
THE COMMAND DECODER

The Command Decoder is a subroutine that OS/8 system programs use to
interpret the I/O specifications for devices and files and for options
that you enter in the command line.

5.1

ENTERING I/O SPECIFICATIONS

When you run a utility program with the R command, the program calls
the Command Decoder, which prints an asterisk to request your I/O
specifications.
I/O specifications to the Command Decoder have the following general
format (Device and file names must adhere to the conventions described
in Chapter 2.):
.R utility
*output specs<input specs/options
The Command Decoder accepts 0 to 3 output files and 0 to 9 input
files.
Keep in mind, however, that the system programs using the
Command Decoder determine their own I/O requirements and restrictions.
These are described in the chapters on system programs in this manual.
Table 5-1 contains examples of
Command Decoder.

legal

output

specifications

the

Table 5-1
Examples of Output to the Command Decoder
File Format

Meaning

EXPLE.EX

Output to a file named EXPLE.EX on device
DSK (the default file storage device).

LPT:

Output to the LPT. This format generally
specifies a nonfile-structured device.

DTA2:EXPLE.EX

Output to a file named EXPLE.EX
DTA2.

DTA2:EXPLE.EX[99]

Output to a file named EXPLE.EX on device
DTA2.
A maximum output file size of 99
blocks is specified.

null

No output specified.

device

5-1

THE COMMAND DECODER
Table 5-2 contains examples
Command Decoder.

legal

input

specifications

the

Table 5-2
Examples of Input to the Command Decoder
File Format

Meaning

DTA2: INPUT

Input from a file named INPUT.df on device
DTA2.
"df" is the assumed input file
extension specified in the Command Decoder.

DTA2:INPUT.EX

Input from a file named INPUT.EX on device
DTA2.
In this case .EX overrides the
assumed input file extension.

INPUT.EX

Input from a file named INPUT. EX.
If there
is no previously specified input device in
the command line, input is from device DSK,
the
default
file
storage
device;
otherwise, the input device is the same as
the last specified input device.

PTR:

Input from device PTR;
nonfile-structured
devices do not require a file name.

DTA2:

Input from device DTA2 treated as a nonfile
structured device, as, for example, in the
PIP command line:

!.TTV:/L<nTA2:
No LOOKUP operation is performed in the
last two formats because in each case the
device is assumed to be nonfile structured.
null

Repeats input from the previous device
specified (must not be first in input list,
and must refer to a nonfile-structured
device).
For example:

! <.F'TR:"
(two null files) indicates that three paper
tapes are to be loaded.
NOTE
Whenever you omit a file extension from
an input file specification, the Command
Decoder performs a LOOKUP for the given
name to which the system program has
appended an assumed extension If the
LOOKUP fails,
a second LOOKUP is made
for the file to which a null
(zero)
extension has been appended.

5-2

THE COMMAND DECODER
5.2

COMMAND DECODER ERROR MESSAGES

If the Command Decoder detects an error in the command line, it prints
one of the error messages in Table 5-3. After the error message, the
Command Decoder starts a new line, prints an asterisk (*), and waits
for another command line.
Table 5-3
Command Decoder Error Messages
Error Message

Meaning

ILLEGAL SYNTAX

The
command
incorrectly.

TOO MANY FILES

More than 3 output files or 9 input
files were specified (in special mode,
more than 1 output file or more than 5
input files).

device DOES NOT EXIST

The specified device name does not
correspond to any permanent device
name or to any user-assigned device
name.

name NOT FOUND

The specified input file name was
found on the selected device.

5.3

line

formatted

not

THE CCL AND THE COMMAND DECODER

The CCL uses its own copy of the Command Decoder instead of the copy
available from the Monitor. Thus, the CCL Command Decoder has several
options not available via standard USR calls to the OS/8 Command
Decoder, for example, multiple default extensions.
For complete information on the Command Decoder, see the OS/8 Software
Support Manual.

5-3

CHAPTER 6
BATCH

6.1

INTRODUCTION

OS/8 BATCH provides PDP-8 users with a batch processing monitor that
is integrated into the OS/8 monitor structure.
The system is
organized in such a way that it may be used in either a keyboard input
configuration or as a batch stream processor.
BATCH may be run on any OS/8 system equipped with at least 12K of
memory.
A line printer, although optional, is highly desirable.
BATCH will support up to 32K of memory and any I/O devices that are
present in the system.
OS/8 BATCH processing is ideally suited to frequently run production
jobs, large and long-running programs, and programs that require
little or no interaction with the user. BATCH permits you to prepare
a job on punched cards, high-speed paper tape or the OS/8 system
device and leave it for the computer operator to start and run.
Output is returned to you in the form of line printer and/or
teleprinter listings that include program output as well as a
comprehensive summary of all action taken by the user program, the
monitor system and the computer operator.
BATCH provides optional spooling of output files. This feature serves
to increase throughput on any system, but it is particularly valuable
when a line printer is not available. BATCH also performs extensive
command analysis and error diagnosis, as well as detailed interaction
with the user/operator to facilitate initializing the system and
establishing system parameters.
Almost any program that runs under interactive OS/8 may also be run
under BATCH.
Since BATCH is called from the keyboard in the same
manner as any other system program, interactive users may use BATCH to
execute multiprogram utility routines, even when continuous batch
processing is not desired.
With a few exceptions, BATCH uses the standard OS/8 command set. This
chapter assumes that you are familiar with the operation and use of
OS/8.

6.2

BATCH PROCESSING UNDER OS/8

The BATCH
OS/8 BATCH maintains an input file and an output file.
input file may be a punched card, high-speed paper tape, disk, or
DECtape file consisting of a series of BATCH commands.
If the input
file is a disk or DECtape file, it must reside on the OS/8 system
device or on a device whose handler is coresident with the OS/8 system
device (e.g., RKBO on RKOS systems).

6-1

BATCH
6.2.1

Input Files

Each command in the BATCH input file occupies one file record. If the
file is a punched card file, each punched card constitutes one record,
which must contain one complete BATCH command. If the file resides on
paper tape, disk, or DECtape, each record consists of one logical line
or of all the characters between two line terminators,
including the
second terminator.

6.2.2

Output Files

The BATCH output file is a line printer listing on which BATCH prints
job headers, certain messages that result from conditions within the
input file, an image of each record in the input file,
and certain
types of user output. If a line printer is not present in the system,
the output file is printed on the terminal.

6.2.3

I/O Devices

BATCH accepts user input files (i.e., program and data files) from any
device in the OS/8 system; however, high-speed paper tape input files
are not allowed when the BATCH input file also resides on high-speed
paper tape. User output files may be directed to any output device in
the system.

6.2.4

Spooling

You may optionally spool output files with BATCH.
When you request
spooling, every output file is assigned a file name from a list of
names maintained by BATCH and directed to a file-structured spool
device instead of to the user-specified device. Spooling of output
files increases BATCH throughput when system resources are scarce and
permits you to postpone slow output operations until a more favorable
time. For example, you may initialize a batch processing run that
generates many output listings so that it reroutes all listings from
the terminal or line printer to a specified DECtape unit.
You may
then dump this DECtape onto the appropriate hard copy device after the
run, when more time is available.
The spool device may be any
file-structured device you select.
To call OS/8 BATCH from the keyboard, type

.R BATCH
in response to the dot generated by the OS/8 monitor.
BATCH then
calls the OS/8 Command Decoder to obtain its parameters, input device,
and file name (if file-structured).
If CCL is enabled, you may also
invoke BATCH via the SUBMIT command,
in which case the BATCH
parameters, input device, and file name
(if file-structured)
are
specified on the same line as the SUBMIT command.

6.2.5

Entering File Specifications

The format for a BATCH command string is:
*SPDV:

(DEV:INPUT/option/option

6-2

BATCH
where
SPDV:

is the device on which to spool nonfile-structured
output.
If you do not specify SPDV:, no spooling is
performed.
Note that spooling
applies
only
to
nonfile-structured output devices specified to the
Command Decoder. BATCH does not spool the output of
programs such as FOTP, which use a special mode of the
Command Decoder.

DEV:INPUT is the input device and file if the input is from SYS:
or a device whose handler is coresident with SYS:.
The default extension for BATCH input files is .BI.
The Run-Time Options are used to specify input from the paper tape
reader or the card reader. The Run-Time Options and their meanings
are listed in Table 6-1.
Table 6-1
Run-Time Options
Option

Meaning

Read the input file from the card
CR8/E) •

Treat OS/8 Keyboard Monitor and OS/8 Command Decoder
errors as nonfatal errors.
If IE is not specified,
OS/8 Keyboard Monitor and OS/8 Command Decoder errors
cause the current job to be aborted.

IP
IQ

Read the input file from the paper tape reader.

Output the BATCH log to the terminal. You need only
specify this option when a line printer is available.
If a line printer is not available, the BATCH log is
automatically output to the terminal.

Process the batch input file without echoing and
without sending the $JOB and $END batch monitor
commands to either terminal or BATCH log.

BATCH will not pause for operator response to $MSG
lines.
Any attempt to use TTY:, PTR:, or CDR:
as
input devices to the Command Decoder in an unattended
BATCH stream will caUSe the current job to be
aborted.

reader

Do not output a BATCH log. $JOB and
only line output to the terminal.

$MSG

(CR8/1

are

the

(continued on next page)

6-3

BATCH
Table 6-1
(Cont.)
Run-Time Options
Option

Meaning

Print the
terminal.

version

number

OS/8

BATCH

the

Accept card input in DEC 026 format. This option is
used only when the /C option is specified. The
default card input format is DEC 029.
NOTE
When running BATCH, do not move the
input
file.
In particular, do not
SQUISH the device containing the BATCH
input file. Moving the input file while
BATCH is running produces unpredictable
results.
If you must SQUISH SYS under
BATCH, place the BATCH input file at the
beginning of SYS so it will not move.
In addition, avoid moving
while BATCH is running.

6.3

SYS:BATCH.SV

BATCH MONITOR COMMANDS

A BATCH command is a character or string of characters that begins
with the first character of a record in the BATCH input file.
If the
input file is a disk, DECtape or paper tape file, each BATCH command
must be followed by a carriage return/line feed combination. If the
input file is a punched card file, each command must begin in the
first column of a punched card. Disk and paper tape files may contain
form feed characters. Form feed characters are ignored by BATCH on
input.
OS/8 BATCH recognizes four monitor level commands.
These commands
allow routine housekeeping operations in a multi-job, batch processing
environment and provide communication between the BATCH programmer and
the computer operator.
Table 6-2 lists the BATCH monitor commands,
which may be considered as an extension of the OS/8 Keyboard Monitor
command set.
Note that the first character of the $JOB, $MSG, and
$END commands is a dollar sign. The BATCH monitor does not recognize
the ALTMODE character.
In the current version, any record that begins with a dollar sign
character but is not one of the BATCH monitor commands listed in Table
6-2 is copied onto the output file and ignored by BATCH.

6.3.1

Defining a BATCH Job

A BATCH processing job consists of a $JOB command record and all the
commands that follow it up to the next $JOB or $END record. Normally,
all the commands submitted by one user are processed as a single job,
and all output from these commands appears under one job header.

6-4

BATCH
Table 6-2
BATCH Monitor Commands
Meaning

Command
$JOB

Initialize for a new job and print a job header on
the output file.
The remainder of the $JOB record is
included in the job header but is ignored by BATCH.
It
should
be
used for
identifying jobs, and
correlating output from the teletype, line printer,
and spool device.

$MSG

Ring the terminal bell and print an image of the
record at the teleprinter.
If you do not specify the
/U option, implying that an operator is present,
BATCH pauses until any key is struck at the keyboard.
If you do specify the /U option, processing continues
uninterrupted.

$END

Terminate batch processing and exit to the OS/8
Keyboard Monitor.
A $END command record should be
the last record of every BATCH input file.

Copy the record onto the output file, then ignore it.
BATCH assumes that every record beginning with a
slash is a comment.

After BATCH encounters a $JOB command, it scans the input file until
it finds a Keyboard Monitor command. Any records that follow the $JOB
command and precede the first Keyboard Monitor command are written
onto the output file and ignored by BATCH.
NOTE
To abort a BATCH job or a sequence of
jobs, use the console HALT switch and
manually branch to location 7000 in the
highest field.
This causes BATCH to
scan its input for the
next
SJOB
command.

6.3.2

Using OS/8 Keyboard Commands

The first character of every Keyboard Monitor command record is a dot
(.).
The rest of the record contains an OS/8 Keyboard Monitor
command, which should appear
in standard OS/8 format.
However,
commands that would be terminated with an ALTMODE under interactive
OS/8 should be terminated with a dollar sign under BATCH.
Every
standard OS/8 Keyboard Monitor command is legal input to BATCH;
however, the ODT command will go to the terminal for input instead of
to the BATCH file.
Typing CTRL/C to ODT will terminate BATCH. Type
7600G to ODT to resume the BATCH run.
BATCH executes a Keyboard Monitor command by stripping off the initial
dot character and loading the remainder of the record into the
Keyboard Monitor buffer. BATCH then passes control to the Keyboard
Monitor, which executes the command as though it had been typed at the
keyboard.

6-5

BATCH
Keyboard Monitor commands that return control to the monitor level
should be followed by a BATCH monitor command or another Keyboard
Monitor command. Keyboard Monitor commands that transfer control to
the program level should be followed by a Command Decoder file
specificationwhenever the running program calls the Command Decoder.
All OS/8 V3 CCL commands are legal under BATCH, including the SUBMIT
command (which can be used to chain from one BATCH stream to another).

6.3.3

Using the Command Decoder

When a running program c~lls the Command Decoder, the Command Decoder
determines whether batch processing is in progress and,
if so,
instructs BATCH to read the next record of the BATCH input file.
BATCH
expects
this record to contain a Command Decoder file
specification.
The first character of every Command Decoder file specification record
is an asterisk (*). The rest of the record contains an OS/8 Command
Decoder file (and/or option) specification, which should appear in
standard OS/8 format.
As with BATCH monitor commands and Keyboard
Monitor commands, any Command Decoder specification that would be
terminated with an ALTMODE under interactive OS/8 should be terminated
with a dollar sign under BATCH.
BATCH executes a Command Decoder file specification by stripping off
the initial asterisk character and loading the remainder of the record
into the Command Decoder buffer. BATCH then passes control to the
Command Decoder, which decodes the file specification as though it had
been typed at the keyboard and returns control to the running program.

6.3.4

Additional Features

If BATCH reads a record from the input file, expecting to find a
Command Decoder file specification, and finds a Keyboard Monitor
command instead, BATCH returns control to the monitor level by
recalling the Keyboard Monitor to execute the command. The running
program is thus terminated; control remains at the monitor level. If
BATCH encounters a BATCH monitor command when it expects to find a
Command Decoder specification, it executes the BATCH monitor command
and continues processing the input file. As long as a Command Decoder
file specification is read before the next Keyboard Monitor command,
control will eventually return to the running program, and the file
specification will be executed.
A BATCH monitor command is legal at any level of command execution,
and the BATCH monitor returns control to the level from which it was
entered. Keyboard Monitor commands are also legal at any level (under
BATCH, but not under interactive OS/8); however, the Keyboard Monitor
terminates any program that may be running when it is called and
returns control to the monitor level.
The computer operator may type CTRL/C at any time during a batch
processing run.
Typing CTRL/C at the program level causes an
effective jump to location 07600, which recalls the BATCH monitor.
The BATCH monitor then recognizes the CTRL/C and terminates the BATCH
run.

6-6

BATCH
6.4

THE BATCH INPUT FILE

Figure 6-1 shows a listing of a BATCH input file.
This listing
represents the output that you obtain by using PIP to transfer the
BATCH input file from disk to the console terminal. Assume that OS/8
BATCH is loaded on a 12K system containing one TU56 dual DEC tape
transport, a line printer, a Teletype terminal, and a disk as the
system device.
If you specify the disk file shown in Figure 6-1 as an
input file, BATCH will begin processing by printing a job header and
executing the DATE command.
fJOB OS/8 BATCH PROCESSING EXAMPLE I I
.[lATE 3/5/74
.R PIP
/LIST SYSTEM DEVICE DIRECTORY ON TELETYPE
*TTY:<SYS:/F
/NOW LIST THE DIRECTORY OF DECTAPE 13 ON THE LPT
fMSG MOUNT TAPE 13 ON UNIT 1
*LPT: ·.DTAI :/L
/NOW TRANSFER FORTRAN SOURCE PROGRAM
IFROM DISK TO DECTAPE 13 (UNIT 1)
fMSG WRITE ENABLE UNIT 1
*DTA1:FORTS1.FT "DSK:FORTS1.FT
ICOMPILE FORTRAN SOURCE
.R FORT
*DTA1:FORTS1.RL,FORTS1.LS~FORTS1.FT

/THAT CONCLUDES JOB I I
fJOB OS/8 BATCH PROCESSING EXAMPLE 12
SMSG MOUNT TAPE 12 ON UNIT 1, WRITE ENABLED
.R PAL8
*PTP:,DTA1:PROG.LSrDTA1:PROG.PA
.RUN DSK CREF
*DTA1:PROG.LS
/END OF EXAMPLF 12 AND END OF INPUT FILE
fEND

Figure 6-1

Sample BATCH Input File

Control remains at the monitor level, so BATCH executes the next
command by calling and starting the Peripheral Interchange Program.
PIP, in turn, calls the Command Decoder, which accepts and decodes the
file/option specification that occupies the next executable record
(following the comment) of the input file. The Command Decoder passes
control to the program level, and PIP lists the short form of the
system disk directory at the terminal.
If spooling is active, BATCH intercepts this output and stores it in a
temporary file on the spool device. Assuming that DTAO is the spool
device and that this listing is the first nonfile-structured output
file intercepted by BATCH, the output is stored in a file named
BTCHAI. BATCH then prints the message:
tSF'{1nL

TO F-ILF II rCHIH

6-7

BATCH
on both the console terminal and the
rerouted to the spool device is
successive files are named:

The next file
line printer.
assigned the file name BTCHA2;

BTCHA3
BTCHA4

BTCHA9
BTCHBO
BTCHBl

BTCHZ9
allowing a total of 260 spool device files, which is more than
adequate in view of the maximum size of the 05/8 file directory (about
240 entries). If output to a spool device file is generated by a
program that appends a default extension to output file names, the
spool device file is assigned a standard default extension.
You may
then transfer all the spool device files to the terminal or line
printer by using the program FOTP, with the input file specification
dev:BTCH??*.
Returning to the example of Figure 6-1, PIP executes the file
specification that appears in the fifth record of the input file and
recalls the Command Decoder.
The Command Decoder then instructs BATCH to scan the input file for
the next file specification record.
BATCH processes the comment
record by copying it onto the line printer, then processes the $MSG
command by ringing the terminal bell, copying the $MSG record onto the
terminal, and, assuming that an operator is present, pausing until any
key is typed at the terminal.
Once the operator has resumed processing by typing any character,
BATCH reads the eighth record In the file, recognizes it as a Command
Decoder specification record, and transfers control back to the
Command Decoder.
Processing continues in this manner until the third Command Decoder
specification record is reao. When BATCH searches for the next file
specification record, it reads and executes the last $MSG command,
then encounters a Keyboard Monitor command. BATCH passes this command
to the Keyboard Monitor, which terminates PIP and calls the FORTRAN
compiler to load and compile source program FORTSI. Upon completion
of these operations, FORTRAN routes its output to the specified files
and returns control to the monitor level. BATCH then encounters the
second $JOB record, caUSIng it to terminate the current job and print
a new header.
The second job calls PAL8 to assemble a source program from disk. The
output listing is directed to DECtape #2, mounted on unit 1, while the
binary output file is dumped onto high-speed paper tape.
The job
concludes by running CREF to produce a cross-referenced listing of the
assembled program.

6-8

BATCH

execute
This job illustrates how you may use OS/8 BATCH
to
multiprogram utility routines.
If USer #2 is a programmer who usually
follows a PAL8 assembly by running CREF, job,2 could be a utili ty
routine that combines the call to PAL8, the call to CREF, and both
file specifications into a single software package that you may run
under batch processing or in an interactive environment.
The $END record that appears as the last record in Figure 6-1 serves
as a signal that batch processing has concluded;
it causes BATCH to
recall the Keyboard Monitor and reestablish interactive processing
under OS/8. This command is always the last record of the BATCH input
file.

6.5

BATCH ERROR MESSAGES

BATCH generates two types of error messages.
The
run-time error message that appears in the form:

first

type

'BATCH ERR
The second type of error message is generated when the Keyboard
Monitor or the Command Decoder recognizes a command error in the BATCH
input file. When this occurs, either the Keyboard Monitor or the
Command Decoder transmits a standard OS/8 error message, and BATCH
will append a "." character to the beginning of the message, so that
it appears in the form:
iSYSTEM ERROR
Any occurrence of a Keyboard Monitor or Command Decoder error normally
causes BATCH to abort the current job and scan the input file for the
next $JOB command. If the /E option was specified, BATCH treats
Keyboard Monitor and Command Decoder errors as nonfatal and continues
the BATCH run.
Table 6-3 lists the BATCH error
probable cause for the error.

messages,

their

meanings,

and

the

Table 6-3
BATCH Error Messages

MeSSag-e~------~
'MONITOR OVERLAYED

iBAD LINE. JOB ABORTED

Meaning

The Command Decoder attempted to call
the
BATCH
monitor to accept and
transmit a file specification, but
found
that
a
user
program had
overlayed part or all of the BATCH
monitor.
Control
returns to the
monitor level, and BATCH executes the
next Keyboard Monitor command.
The BATCH monitor detected a record
in the input file that did not have
one of the characters dot,
slash,
dollar sign, or asterisk
as
the
first character of the record.
The
record is ignored, and
BATCH scans
the input file for the next $JOB
record.
-.------~~-~-----~(continued-on next -page)
6-9

BATCH
Table 6-3
(Cont.)
BATCH Error Messages

tSPOOL TO FILE BTCHAI

(Where the "A" may be any character of
the alphabet and the "1" may be any
decimal digit.) BATCH has intercepted
a nonfile-structured output file and
rerouted it to the spool device. This
is not, generally, an error condition.
Spool device file names are assigned
sequentially,
beginning
with file
BTCHAI. Standard default extensions
may
be
assigned
by some system
programs.

tMANUAL HELP NEEDED

BATCH is attempting to operate an I/O
device, such as PTR or TTY, that will
require operator intervention. If the
initial dialogue indicated that an
operator is not present, this message
is suppressed, the current job is
aborted, and BATCij scans the input
file for the next $JOB command record.
If an operator is present, he should
have been notified what action to take
by a $MSG command.

ULLEGAL INPUT

A file specification has designated
TTY or PTR as an input device although
the initial dialogue indicates that an
operator
is
not
available.
The
current job is aborted, and BATCH
scans the input file for the next $JOB
command record.

#INPUT FAILURE

Either a hardware problem prevented
BATCH from reading the next record of
the input file, or BATCH read the last
record
of the input file without
encountering a $END command record.
If a hardware problem exists, correct
the problem and type any character at
the Teletype to resume processing.

tSYS ERROR

A hardware problem prevented BATCH
from
performing an I/O operation.
Program execution halts,
and
the
system must be restarted manually.
This message often indicates that the
system device is not write-enabled.

INSUFFICIENT CORE FOR
BATCH RUN

OS/8 BATCH requires 12K of core to
run.
Control returns to the OS/8
Monitor.

BATCH.SV NOT FOUND ON
SYS:

A copy of BATCH.SV must exist on the
system device. Control returns to the
OS/8 Monitor.

~-------

--------

- - - - - - - - - - - - - - - - - - - - ~-- - - - - - - - - - '

(continued on next page)

6-10

BATCH
Table 6-3
(Cont.)
BATCH Error Messages

r-__________M
__e_s_s_a_g_e____________+r_-_-====~~~~-------IM-e-a-nfng
WRONG OS/8 MONITOR

OS/8 BATCH requires an OS/8 Monitor no
older than version 3.

DEV NOT IMPLEMENTED

BATCH cannot accept input from the
specified input device because its
handler is not permanently resident
(SYS:
or
coresident with SYS:).
Control
returns
to
the
Command
Decoder.

ILLEGAL SPOOL DEVICE

The device specified as a spooling
output device must be file structured.
Control
returns
to
the
Command
Decoder.
--------~-------------------------!

6.6

RUNNING BATCH FROM PUNCHED CARDS

The carriage'return and ALTMODE characters are not defined in the
punched card character set.
BATCH allows you to omit terminating
carriage return characters from punched card input files. Thus, when
BATCH reads a punched card input file, it appends a carriage return to
the content of each card, immediately following the last character on
the card that is not a space character. As with disk, DECtape or
paper tape input files, BATCH considers the dollar sign character to
be equivalent to an ALTMODE when it appears on a punched card in any
column except the first.
When you run BATCH with a punched card input file, it is possible to
embed your input files in the BATCH input file.
You should insert
your input files into the BATCH input file in such a way that BATCH
will never attempt to read a record of the files. That is, your files
should follow a command record that transfers control to the program
level, and the running program must exhaust all records of your file
before returning to the monitor level.
Figure 6-2 illustrates how you may modify the second sample job of
Figure 6-1 to run from a punched card input file with an embedded user
file.
In this example, PAL8 reads the punched card user file and
assembles the source program, then returns control to the monitor
level. BATCH reads the next card of the input file, which should
contain the .R CREF command.
If PAL8 has not read every record of the
user input file, however, BATCH will encounter a record from this file
rather than the Keyboard Monitor command record. This results in the
message:

tBAD LINE. JOB ABORfED
and causes BATCH to scan the input file for the next $JOB record.

6-11

BATCH

($END
(
EMBEDDED
USER FILE

lEND OF EXAMPLE #2

~ *DTA1·PROG LS

.RUN DSK CREF

~-::-

I.!il ;

,...-

(*PTP:,DTAl PROG.LS CDR·

1111

(.R PAL8

($MSG MOUNT TAPE ~ ~~ UNIT 1
$JOB OS/8 BATCH PROI l:.... I~jG EXAMPLE #2

Figure 6-2

6.7

Punched Card Input File

RESTRICTIONS UNDER OS/8 BATCH

OS/8 BATCH is a "friendly" system;
that is, one that is largely
unprotected from user errors. The BATCH monitor resides in locations
5000 to 7577 in the highest memory field available. BATCH also uses
the following locations in field 0 and the memory field in which it
resides:
Location

Used as:

07777
N7774-N7777

Batch processing flag
Internal pointers

Both the Keyboard Monitor and the Command Decoder check the batch
processing flag whenever they are entered from the program level. Any
user program that modifies location 07777 may cause batch processing
to be terminated prematurely before the next record of the BATCH input
file is read.
When the Keyboard Monitor is entered from the program level (effective
JMP to 07600 or 07605), it checks the batch processing flag and reads
a new copy of the BATCH monitor into core if batch processing is in
progress.
The Command Decoder, however, does NOT perform this
operation. Thus, the Command Decoder must not be called unless the
BATCH monitor is already in core.
This means that you may load large programs over the BATCH monitor as
long as they do not modify the last four locations in the highest
memory field; however, once a user core load has overwritten the
BATCH monitor, execution must remain at the program level until the
Keyboard Monitor has been reentered and a new copy of the BATCH
monitor is read into core.
You must not call the Command Decoder
after you have loaded your program over the BATCH monitor.

6-12

BATCH
In general, this restriction applies only to loader programs and only
when the loader calls the Command Decoder more than once while
building a large core load. You can avoid multiple calls to the
Command Decoder when loading large programs during batch processing if
you first build the core load in a stand-alone environment and then
save it for subsequent execution under BATCH.
In conjunction with this, note that it is impossible to save the core
image of any program that overlays the BATCH monitor under BATCH.
After the load operation but before the save is executed, the BATCH
monitor is read back into core, destroying part of the user program~
Thus, the Keyboard Monitor SAVE operation causes part of the BATCH
monitor to be saved instead of that part of the user program that
originally overlayed the BATCH monitor.

6.S

BATCH DEMONSTRATION PROGRAM

The following listing was produced by running BATCH on a 12K PDP-S/E
system containing a disk, DECtape and a line printer. Only the
Teletype output is reproduced here, and page breaks were inserted
arbitrarily to divide the listing into convenient segments. The same
BATCH input file has been processed twice, with two different system
configurations.
Notice that the first BATCH processing run begins by listing the BATCH
input file,
and that the three demonstration programs are listed
shortly thereafter •

• R BATCH
*SYS:DEMO/U
$JOB OS/8 BATCH DEMO
.MSG BEGIN BY LISTING BATCH INPUT FILE ON TERMINAL:
.R PIP
*TTY: <.DEMO. BI
.DATA 3/5/74
.MSG SYS1EM DEVICE ASSIGNED LOGICAL NAME "IN"
.ASSIGN SYS IN
$MSG MOUNT SCRATCH DEC TAPE ON UNIT 1
.R PIP
IZERO DECTAPE DIRECTORY
.MSG WRITE ENABLE UNIT 1
*DTA1! .: IZ
ILIST SYSTEM DIRECTORY ON LINE PRINTER
*LPT: .. IN!/E
ITRANSFER DEMO PROGRAMS TO DECTAPE
*DTA1! DEM01. PA· ·DEM01. PA
*DTA1:DEM02.FT~DEM02.FT

*[ITA1: DEMtJ3. FT· .. DE"M03. FT
ILIST THE" FIRST DEMO PROGRAM
*TTY: IN:DEM01.PA/T
ILJST THE SE"COND DEMO PROGRAM
*TTY! IN!DEM02.FT/T
ILIsr THE THIRD DEMO PROGRAM
*TTY! .IN:DEM03.FT/T
/ASSEMBLF DEM01.PA
.R PAL8
*IN!DEM01.BN,DEM01.LS :IN:DEM01.PA
IPRINT CROSS REFERENCE LISTING
.R CRE!-="
*LPT! IN!DEM01.LS
ILOAD ASSEMBLED BINARY INTO CORE

6-13

BATCH

.R ABLSDR
*DEM01.BN$
IRUN FIRST DEMO PROGRAM
.START 200
INOW SAVE CORE IMAGE OF DEM01.PA, BUT MUST
IRELOAD FIRST, SINCE DEMOI IS SELF-MODIFYING
.R ABSLDR
*IN:DEM01.BN$
.SAVE SYS DEMOI 0,200
IRUN DEM01.SV TO BE SURE THAT IT WAS SAVED CORRECTLY
.RUN SYS DEMOI
INOW COMPILE FORTRAN MAINLINE PROGRAM
.R FORT
*IN:DEM02.BN,LPT:<IN:DEM02.FT$
ICOMPILE FORTRAN FUNCTION ROUTINE
.R FORT
*IN:DEM03.BN,LPT:<IN:DEM03.FT$
ITRANSFER BOTH BINARY FILES TO DECTAPE
.R PIP
*DTA1:DEM02.BN<DEM02.BN/B
*DTA1:DEM03.BN<DEM03.BN/B
ILOAD AND EXECUTE FORTRAN PACKAGE
.R lOADER
*DEM02.BN,DEM03.BN/G
IRENAME DEM03.BN FOR FUTURE REFERENCE
.R PIP
*FACT<DEM03.BN/I
*DEM03.BN<D
IADD FORTRAN FUNCTION TO FORTRAN LIBRARY
• R LIBSET
*LIB8.BN/S
*FACT$
IFINAllY, DELETE TEMPORARY FILE "FACT"
.R PIP
*FACT·UD
INOW CLEAN UP DISK AREA
*DEM01.BN,DEMOI.SV,DEM02.BN<D
$HSG DEVICE NAMES DEASSIGNED
.DEASSIGN
$END

$MSG SYSTEM DEVICE ASSIGNED LOGICAL NAME "IN"
$MSG MOUNT SCRATCH DEC TAPE ON UNIT 1
$MSG WRITE ENABLE UNIT 1
*10
IR1,
*200
START,

300
ClA Cll
TlS
TAD I IRI
JMS TYPE
JMS TEST
JMP .-4

6-14

BATCH

TYPE,

TSF
JMP .-1
TLS
CLA
JMP I fYF'E

TEST,

TAD IRl
TAD M335
SZA CLA
JMP I TEST
TSF
JMP .-1
JMP 7600
-335

M335,
*301

215;212;212;241;241;241;305;330;305;303
325;324;311;317;316;240;303;317;315;320
314;305;324;305;241;241;241;215;212;212
$

FORTRAN DEMONSTRATION PROGRAM
DIMENSION A(35)
DO 10 N=2,34,2
A(N)=FACT(N)
WRITE (1,60)N,A(N)
STOP
FORMAT (13, '! = ',E14.7)
END

10
6')

FORTRAN FUNCTION TO COMPUTE FACTORIALS
FUNCTION FACT(N)
IF (N-34) 1,5,5
IF (N) 2.4,2
M=-N-2
FACT=N
DO 3 /\=l~M
C=N-/\
FACT=FACT*C
RETURN
FACT=l.
RETURN
WRITE (1,6) N
FACT-=O.
RETURN
FORMAT (15,'! EXCEEDS CAPACITY OF PROGRAM.')
END

4
5
6

"'EXECUTION COMPLETE'"
! , ! EXECUTION COMPLETE! ! !
2'
4!
6'
8!
10!
12!
14'
16'
18!

=
=
=
=
=
=

=
=

0.2000000E+Ol
0.2400000E+02
0.7200000E+03
0.4032000E+05
0.3628800E+07
0.4790016E+09
0.8717829E+ll
0.2092279E+14
0.6402374E+16

6-15

BATCH
20! = 0.2432902E+19
22! = 0.1124001E+22
24' = 0.6204484E+24
26! 0.4032915E+27
28! = 0.3048883E+30
30' = 0.2652529E+33
32' = 0.2631308E+36
"34! EXCEEDS CAPACITY OF PROGRAM.
34' = O.OOOOOOOE+OO
$MSG DEVICE NAMES DEASSIGNED
END BATCH

The next run is initiated via the SUBMIT command •
• SUBMIT SYS:~SYS:DEMO/U/T
$JOB OS/8 BATCH DEMO
$MSG BEGIN BY LISTING BATCH INPUT FILE ON TELETYPE:
.R PIP
*TTY: "~_DEMO. BI
SPOOL TO FILE BTCHAl
.DATE 8/3/72
'MSG SYSTEM DEVICE ASSIGNED LOGICAL NAME "IN"
.ASSIGN SYS IN
$M5G MOUNT SCRATCH DECTAPE ON UNIT 1
.R PIP
IZERO DEC TAPE DIRECTORY
$MSG WRITE ENABLE UNIT 1
*DTA1:</Z
ILIST SYSTEM DIRECTORY ON LINE PRINTER
*LPT:<IN:/E
SPOOL TO FILE BTCHA2
ITRANSFER DEMO PROGRAMS TO DEC TAPE
*DTAl : DEM01. PA"""DEM01. PA
*DTA1:DEM02.FT~DEH02.FT
*DTA1:DEM03.FT~DEM03.FT

/LIST FIRST DEMO PROGRAM
*TTY:'-:IN:DEM01.PA/T
SPOOL TO FILE BTCHA3
/LIST SECOND DEMO PROGRAM
*TTY:~IN:DEM02.FT/T

SPOOL TO FILE BTCHA4
/LIST THIRD DEMO PROGRAM
*TTY:~IN:DEM03.FT/T

SPOOL TO FILE BTCHA5
/ASSEMBLE DEM01.PA
.R PAL8
*IN:DEM01.BN,DEM01.L5 IN:DEM01.PA
/PRINT CROSS REFERENCE LISTING
.R CREF
*LPT:-IN:DEM01.L5

6-16

BATCH
*SPOOL TO FILE BTCHA6
/LOAD ASSEMBLED BINARY INTO CORE
.R ABSLDR
*DEM01.BN$
/RUN FIRST DEMO PROGRAM
.START 200
II !EXECUTION COMPLETE! ! !
/NOW SAVE CORE IMAGE OF DEM01.PA, BUT HUST
/RELOAD FIRST, SINCE DEHOl IS SELF-MODIFYING
.R ABSLDR
*IN:DEM01.BN$
.SAVE SYS DEHOl 0,200
/RUN DEM01.SV TO ENSURE THAT IT WAS SAVED CORRECTLY
.RUN SYS DEMOl
,I IEXECUTION COMPLETE!!!
/NOW COMPILE FORTRAN HAINLINE PROGRAM
.R FORT
*IN:DEM02.BN,LPT:
IN:DEM02.FT$
SPOOL TO FILE BTCHA7
/COMPILE FORTRAN FUNCTION ROUTINE
.R FORT
*IN:DEM03.RN,LPT:
IN:DEM03.FT$
SPOOL TO FILE BTCHA8
/TRANSFER BOTH BINARY FILES TO DECTAPE
.R PIP
*DTA1:DEM02.BN<DEM02.BN/B
*DTA1:DEM03.BN<DEM03.BN/B
/LOAD AND EXECUTE FORTRAN PACKAGE
.R LOADER
*DEM02.BN,DEM03.BN/G
0.2000000E+Ol
41 = 0.2400000E+02
6! = 0.7200000E+03
8!
0.4032000E+05
10!
0.3628800E+07
12! = 0.4790016E+09
14! = 0.8717829E+11
16' = 0.2092279E+14
18! = 0.6402374E+16
20 1 = 0.2432902E+19
22! = o • 1124001E+22
241
0.6204484E+24
26 1 = 0.4032915E+27
28 1 = 0.3048883E+30
30 1
0.2652529E+33
32! = 0.2631308E+36
34! EXCEEDS CAPACITY OF PROGRAM.
341 = O.OOOOOOOE+OO
IRENAME DEM03.BN FOR FUTURE REFERENCE
.R PIP
*FACr~DEM03.BN/I

*[lEM03. BN··· /D
IADD FORTRAN FUNCTION TO FORTRAN LIBRARY
.R LIBSET
*LIB8.BN/S
*FAC T$
IFINALLY, DELETE TEMPORARY FILE "FACT"

6-17

BATCH
.R PIP

*FACT::.ID
INOW CLEAN UP DISK AREA
*DEM01.BN,DEM01.SV,DEM02.BN(/D
$MSG DEVICE NAMES DEASSIGNED
.DEASSIGN
$END
tEND BATCH

6.9

LOADING AND SAVING BATCH

.
You may load and save the paper tape binary version of OS/8 BATCH on
the OS/8 system device by typing the following commands in response to
the prompt signs generated by the OS/8 monitor:

.R ABSLDR

iPTR:(9P)$~
~SAVE SYS BATCH

Once the ALTMODE ($) has been entered, the system will print an
uparrow and pause.
Load the binary paper tape into the high-speed
reader, turn the reader on, and type any character at the keyboard to
continue.

6.10

LOADING AND SAVING PROGRAMS FOR USE UNDER BATCH

A program that never uses more than 8K of core can never destroy the
BATCH monitor.
When you are loading this sort of program from a
DEC tape system, you can save considerable time through the use of the
/P option.
The /p option is a new ABSLDR option designed for use under OS/8
BATCH.
It causes the 400 bit of the job status word (location 07746)
to be set and prevents the Keyboard Monitor from reading a fresh
version of the BATCH monitor into core every time the monitor level is
reentered from the program level.
For example, OS/8 PIP never uses more than 8K of core.
method of loading PIP would be:

Thus, the best

.R ABSLDR
jPTR:(89P)=13000$
.!.

The /P option is not really necessary on a disk system, because very
little time is required to refresh the BATCH monitor from disk. You
should not use the /P option with any program that occupies or
modifies core above field 1.

6-18

BATCH

6.11

TRANSFERRING THE SYSTEM SOFTWARE FROM CASSETTE TO THE SYSTEM DEVICE

The following BATCH file can be used to transfer
Software from cassette to the system device .

• JOB JOB TO LOAD SYSTEM CASSETTE 12 TO SYSTEM DEVICE
.R MCPIP
*SYS:CCL.SV-CSAO:CCL.SV
*SYS:DIRECT.SV~CSAO:DIRECT.SV

*SYS:FOTP.SV·~CSAO:FOTP.SV

*SYS;PIP.SV CSAO:PIP.SV
*SYS:LIBS.RL':CSAO:LIBS.RL
*SYS:EDTT.SV:CSAO:EDIT.SV
*SYS:PALB.SV·CSAO:PALB.SV
*SYS:CREF.SV·CSAO:CREF.SV
*SYS:BITMAP.SV~CSAO:BITMAP.SV
*SYS:BOOT.SV·CSAO:~OOT.SV

«SYS:CAMP.SV· CSAO:CAMP.SV
*SYS:RK8FMf.SV ·CSAO:RKSFMT.SV
*SYS: fd,FFM r • SV . CSAO: RKEFMT. SV
HND

.JOB JOB TO LOAD SYSTEM CASSETTE 13 TO SYSTEM DEVICE
.R MCPIP
*SYS: FORT. SV -.CSAl : FORT. SV
*SYS: SABR. SV·"CSA1: SABR. SV
*SYS:LOADER.SV· CSA1:LOADER.SV
*SYS:SRCCOM.SV CSA1;SRCCOM.SV
*SYS:EPIC.SV:CSA1:EPIC.SV
*SYS:PIP10.SV~CSA1:PIP10.SV
*SYS:~ESO~C.SV ·CSA1:RESORC.SV

*SYS:DTCOPY.SV ·CSA1:DTCOPY.SV
*SYS:fDCOPY.SV/CSA1:TDCOPY.SV
*SYS:TDFRMT.SV·:CSA1:TDFRMT.SV
*SYS: DTFRMT. SV· 'eSA1: DTFRMT. SV
SENfi

$,lnB JOB Til LOAD SYSTEM 14 TO SYSTEM DEVICE
.~ MCF IF'
*SY~:rr,08SY.BN CSAO:TCOBSY.BN
*SYS:rnSESY.BN CSAO:TDSESY.BN
*SYS:LINCSY.BN-CSAO:LINCSY.BN
*SYS:nF32SY.BN .CSAO:DF3~SY.BN
*SYS: RFOSSY • BN·. CSAO: RFOBSY • BN
*SYS:R~OBSY.BN· CSAO:R~OSSY.BN

*SYS:R~8ESY.BN~CSAO:RKSESY.BN

*SYS:ROMMSY.BN· CSAO:ROMMSY.BN
tSYS: L INCNS. BN ··CSAO: LINCNS. BN
*SYS:TCOBNS.BN CSAO:TCOSNS.BN
*SYS:R~SENS.BN'CSAO:R~SENS.BN

*SYS:PT8f.BN·rSAO:PTSE.BN
*SYS: LSPT • BN<TSAO: LSPT • BN
*SYS: L645. BN· 'CSAO: L645. BN
*SYS:ASR33.BN CSAO:ASR33.BN
*SYS:R~ORNS.BN·r,SAO:RKOBNS.BN

6-19

the

OS/8

System

BATCH
*SYS1CR8E.BN(CSAO:CR8E.BN
*SYS1BAT.BN<CSAO:BAT.BN
*SYS:TD8EA.BN<CSAO:TD8EA.BN
*SYS1TD8EB.BN<CSA01TD8EB.BN
*SYS:TD8EC.BN<CSAO:TD8EC.BN
*SYS:TD8ED.BN<CSAO:TD8ED.BN
*SYS:VR12.BN<CSAO:VR12.BN

*SYS1RF08NS.BN<CSA~:RF08NS.BN

*SYS:DF32NS.BN<CSAO:DF32NS.BN
*SYS:KL8E.BN<CSAO:KL8E.BN
*SYS:LPSV.BN<CSAO:LPSV.BN
*SYS:TM8E.BN<CSAO:TM8E.BN
*SYS:CSA.BN<CSAO:CSA.BN
*SYS1CSB.BN<CSAO:CSB.BN
*SYS:CSC.BN<CSAO:CSC.BN
*SYS:CSD.BN<CSAO:CSD.BN
*SYS:DIRECT.HL<CSAO:DIRECT.HL
*SYS:BATCH.HL<CSAO:BATCH.HL
*SYS:SABR.HL<CSAO:SABR.HL
*SYS1PIP.HL<CSAO:PIP.HL
*SYS:FOTP.HL<CSAO:FOTP.HL
*SYS:ABSLDR.HL<CSAO:ABSLDR.HL
*SYS:PIP10.HL<CSAO:PIP10.HL
*SYS:BOOT.HL<CSAO:BOOT.HL
*SYS:LOADER.~L<CSAO:LOADER.HL

*SYS:BITMAP.HL<CSAO:BITMAP.HL
*SYS:EDIT.HL<CSAO:EDIT.HL
*SYS:CREF.HL<CSAO:CREF.HL
*SYS:BUILD.HL<CSAO:BUILD.HL
*SYS:PAL8.HL<CSAO:PAL8.HL
*SYS:ODT.HL<CSAO:ODT.HL
*SYS:SRCCOM.HL<CSAO:SRCCOM.HL
*SYS:CCL.HL<CSAO:CCL.HL
*SYS:TECO.HL<CSAO:TECO.HL
*SYS:FORT.HL<CSAO:FORT.HL
*SYS:LOAD.HL<CSAO:LO.HL
*SYS:LIBRA.HL<CSAO:LIBRA.HL
*SYS:EPIC.HL<CSAO:EPIC.HL
SEND

$JOB JOB TO LOAD SYSTEM CASSETTE 15 TO SYSTEM DEVICE
.R MCPIP
*SYS1LIB8.RL<CSA1:LIB8.RL
*SYS:GENIOX.RL<CSA1:GENIOX.RL
*SYS1IOH.RL<CSA1:IOH.RL
*SYS:FLOAT.RL<CSA1:FLOAT.RL
*SYS:INTEGR.RL~CSA1:INTEGR.RL

*SYS:UTILTY.RL<CSA1:UTILTY.RL
*SYS:POWERS.RL~CSA1:POWERS.RL

*SYS1IPOWRS.RL<CSA1:IPOWRS.RL
*SYS:SQRT.RL~CSA1:SQRT.RL

*SYS1TRIG.RL<CSA1:TRIG.RL
*SYS:ATAN.RL~CSA1:ATAN.RL

*SYS:RWTAPE.RL<CSA11RWTAPE.RL
*SYS1IOPEN.RL<CSA1:IOPEN.RL
*SYS:LIBSET.SU<CSA11LIBSET.SU
*SYS:KL8E.PA<CSA11KL8E.PA
.END

6-20

BATCH

$JOB JOB TO LOAD SYSTEM CASSETTE t6 TO SYSTEM DEVICE
.R MCF'IF'
*SYS:CCL.F'A<CSAO:CCL.PA
$END

$JOB JOB TO LOAD OS/8 EXTENSION CASSETTE TO SYSTEM DEVICE
.R MCF'IP
*SYS:BATCH.SV<CSA1:BATCH.SV
*SYS:BASIC.SV<CSA1:BASIC.SV
*SYS:BCOhF'.SV/CSA1:BCOMF'.SV
*SYS:BLOAD.SV~CSA1:BLOAD.SV

*SYS:BRTS.SV<CSA1:BRTS.SV
*SYS:BASIC.AF<CSA1:BASIC.AF
*SYS:BASIC.SF<CSA1:BASIC.SF
*SYS:BASIC.FF<CSA1:BASIC.FF
*SYS:BASIC.UF<CSA1:BASIC.UF
*SYS:EAEOVR.BN<CSA1:EAEOVR.BN
*SYS:RESEO.BA<CSA1:RESEO.BA
*SYS: TECO. SV<.CSAI : TECO. SV
*SYS:MSBAT.SV<CSA1:MSBAT.SV
*SYS:GENIOX.RL~CSA1:GENIOX.RL

$END

6.12

RUNNING FORTRAN IV UNDER BATCH IN 32K

To run FORTRAN IV V3D under BATCH V3D causes a problem because BATCH
allows the use of 32K words of memory, but the FRTS loader restricts
memory to 28K. If you do not have a TD83 ROM and would like to run
FORTRAN IV under BATCH in 32K, install the following patch to FRTS.SV •

• GET SYS FRTS
.ODT
12713/

5326

7000

~SAVE

SYS

FRTS

6-21

CHAPTER 7
BITMAP

The BITMAP program constructs a table
locations used by given binary files.

(map)

showing

the

memory

BITMAP uses 8K of core to map programs using up to 16K of core, but it
requires 12K of core to map programs using more than 16K of core.

7.1

FILE AND DEVICE SPECIFICATIONS

To call BITMAP from the system device, type

.R BITMAP
The system responds by printing an asterisk (*) in the left margin.
Type the input line to BITMAP, specifying input devices and file name
(if input is from a mass storage device), any options desired, and an
output device and file name (if output is to a mass storage device).
The standard input devices for BITMAP are PTR, DTAn, DSK, and SYS.
Any other device can serve as an input device if a device handler
exists in the system. Do not use TTY because the binary code may
appear to the TTY handler as control characters.
BITMAP accepts only absolute binary files;
you may
not
use
relocatable and core image files.
If you do not type an extension to
the input file name, BITMAP defaults to the .BN extension.
If more
than one program is present in a file, only the first program is
bitmapped.
(This feature allows BITMAP to ignore any noise characters
caused by reading over the end of a paper tape.) The /S switch can
override this feature.
Type the RETURN key at the end of an input specification line to
signal that you wish to continue to input on the next line. When
there is no more input, use the ALT MODE key as a line terminator.
The Command Decoder is not recalled, and control returns to the
Keyboard Monitor. The last line typed specifies the output device on
which the bit map is to be produced.
You may specify any legal OS/8
output device, but if you don't specify one, output goes to the
console terminal. For example:

.R BITMAP
iDTA1:FILE1,FILE2,FILE3,FILE4
!LPT:<PTR:$If an output file is specified without an extension, BITMAP inserts a
.MP extension.
The preceding lines cause FILEl, FILE2, FILE3, and
FILE4 from DECtape 1 to be considered. Then a file is read from the
high-speed paper tape reader. When you press the ALT MODE key, the $

7-1

BITMAP
character is printed, which indicates a return to the Keyboard
Monitor. A bit map, which combines all the files read, is produced on
the line printer.
The various options BITMAP accepts are listed in Table 7-1.
Table 7-1
Bitmap Options
Meaning

Option

Reset internal bit map of BITMAP to
nothing has been input.

Consider all binary programs in the specified input
file (s)
(instead of only the first program in each
file, which is normally done) .

Where n is an integer, forces mapping of all files
specified on this input line as if it were initially
in field n.

This is used to change the style of output - i.e.,
put
teletype-style
output
on
non-teletype or
non-teletype-style output on teletypes.

look

though

Consider the following examples of command lines to BITMAP:
.R BITMAP
iSYS:PROG.Ol
!DTA 1 : MAP-'~DT AS: PATCH. BN

The preceding commands first create a bit map of the combined files
PROG.Ol
(on the system device) and PATCH.BN (on DECtape 5) and then
store the output in file MAP.MP on DEC tape 1 •
.!.R BITMAP
!LPT:<A,B,C$

This example combines three binary files (A, B, and C) on device
to produce a bit map on the line printer •

DSK:

• R BITMAP
!TTY:<PTR:/S$~

The preceding example reads a binary tape from the high-speed paper
tape reader, combines all binary files on the paper tape, and produces
a bit map of these files on the terminal.

7.2

BITMAP OUTPUT

BITMAP outputs a series of lines, each comprised of a string of
digits.
Each digit represents a single core location and has the
value 0, 1, 2, or 3. The value is assigned as follows:

means that the location was not loaded into.

means that the location was loaded into once.

7-2

BITMAP
2

means that the location was loaded into twice.

means that the location was loaded into three or more times.

Occurrence of a 2 or 3 may imply a programming error
(e.g., two
separate routines are trying to load values into the same location).
Each line of digits represents 100(8) core locations, and lines are
blocked in pairs to represent pages. On teletype output, a set of
octal coordinates that associates one core location to each digit
borders the bit map. Adding the horizontal and vertical coordinates
that lie directly to the left and above the entry determines the
corresponding core location for any given entry in the map.

7.3

BITMAP ERROR MESSAGES

After each error message, control returns to the Command Decoder. You
can repeat the procedure, or reset the program (using the /R option)
and repeat using different inputs.
Message

7.4

Meaning

I/O ERROR
FILE #n

An I/O error occurred in input file number n.

BAD INPUT,
FILE tn

A physical end-of-file has been reached before a
logical end-of-file, or extraneous characters have
been found in binary file n.

BAD CHECKSUM,
FILE tn

File number n of
checksum errOr.

NO INPUT

No binary file was found on the designated device.

ERROR ON
OUTPUT
DEVICE

Error occurred while writing on output device,
i.e., output errOr on DECtape write.

NO /1

Cannot produce a bit map of an image file.

the

input

file

list

ASSEMBLY INSTRUCTIONS

Use PAL8 to make BITMAP.BN from BITMAP.PA as follows:
.R PAL8
jDEV:BITMAP:DEV:BITMAP
Use ABSLDR to make BITMAP.SV from BITMAP.BN on a DECtape file:
~R ABSLDR
!DEV:BITMAP~12000/9$
~SAVE

DEV

BITMA~

To load and save the binary paper tape (DEC-S8-0SYSB-A-PB15):
.R ABSLDR
jPTR:=12000/9$~SAVE DEV BITMAP

7-3

had

CHAPTER 8
BOOT

BOOT is an OS/8 program that you use to bootstrap from one PDP-8
system to another and to bootstrap from one device to another by
typing commands on the keyboard. BOOT can run conveniently from OS/8
and COS 300, and can also run from any other PDP-8 monitor system
(e. g., CAPS-8).

8.1

BOOTING WITH BOOT

To run BOOT from COS 300, see Chapter
Reference Manual (DEC-08-0COSA-E-D).

the

COS

300

System

To run BOOT from OS/8, type:

.R BOOT/dv
or

.RUN DEV:BOOT/dv
where dv is a two-character mnemonic that must immediately follow a
slash.
This mnemonic represents the device type and the system to be
bootstrapped. Do not attempt to bootstrap onto a device that is not
ready or does not exist.
To run BOOT from an OS/8 device with CCL enabled, type:

• BOOT/dv
If you use this form of call, BOOT.SV must be present
device.

the

system

If you type the following:

!oR BOOT
the system responds with a slash, and you can enter the dv mnemonic.
If_ an illegal mnemonic is typed, the system prints:

to allow you to enter a new mnemonic.
then enter the correct command.

Type RUBOUT to erase the

line,

If a period follows the device mnemonic, the program loads the correct
bootstrap into core and then halts.
Press CONT to branch to the
bootstrap.
8-1

BOOT

Table 8-1 lists the legal mnemonics for BOOT.
Table 8-1
BOOT Mnemonics

TA8E cassette

CAPS-8

Any disk (RF08,
DF32, RK8E, RK8)

OS/8, COS-300

LINCtape

DIAL-V2, DIAL-MS

RF08 or DF32

Disk Monitor

Any tape (TC08,
TD8E, LINCtape)

05/8, COS 300

LINCtape

OS/8, COS 300

PT8E paper tape

Loads BIN/loader into
field 0

RK8E disk

05/8, COS 300

RF08, DF32 disks

05/8, COS 300

RK8 disk

05/8, COS 300

TC08 DEC tape

05/8, COS 300, Disk Monitor,
DEC library system,
and others

TD8E DEC tape

OS/8, COS 30G

TC08 DEC tape unit 4

Typeset bootstrap

Types BOOT's version number

Zeroes core (field 0)

8.2

System or Comments

Device

Mnemonic

RXOI Diskette

05/8

BOOT PRIORITIES

More than one type of device (e.g., disk, DECtape) may be present on
the 05/8 system. When you use the DK or DT mnemonic, BOOT assumes the
following priorities:
Disk
1.
2.
3.

DECtap~

RF08 or DF32
RK8E
RK8

2.
3.

TC08
TD8E
LINCtape

8-2

CHAPTER 9
BUILD

BUILD is the system generation program for OS/8 that allows you to:
•

Create an OS/8 monitor system from cassettes or paper tapes.

•

Maintain and
system.

•

Add device handlers supplied by DIGITAL to a new
system.

•

Add your own device handlers to a new or existing system.

update

device

handlers

existing
or

OS/8

existing

with BUILD, you use simple keyboard commands to manipulate the device
handlers that make up the OS/8 peripheral configuration. BUILD allows
you to quickly and easily insert devices not standard on the system.

9.1

OS/8 DEVICE HANDLERS

Each OS/8 configuration has certain device handlers available within
BUILD when the system is supplied by DIGITAL. The handlers supplied
with BUILD depend on the distribution media of OS/8 software,
i.e.,
DECtape
(LINCtape), cassettes, or paper tape. These device handlers
are detailed for specific distribution media in Tables 9-1, 9-2, and
9-3 (see Appendix (G) for more information).
You must activate the device handlers included with BUILD before the
OS/8 system can use them. The BUILD commands INSERT, REPLACE, and
SYSTEM activate the device handlers.
A maximum of 15 handlers,
including the system device (SYS) and the default mass storage device
(DSK), can be made active.
Inactive devices, although included with BUILD, cannot be used on the
system until they are made active by the INSERT command. Thus,
several system handlers may be supplied with BUILD, but only one may
be marked active.
All other OS/8-supported device handlers are supplied with every
configuration.
But if they are not included in the original BUILD,
you must load them into BUILD before you can use them.
The BUILD
command LOAD accomplishes this. See Table 9-4 for a complete list of
the device handlers available with OS/8.
Two names identify handlers in BUILD. The first is the group name,
assigned to an entire group of handlers of the same type. For
example, the nonsystem TC08 DECtape handler supplied with a DECtape
system, which has four separate internal handlers, has the group name
TC.

9-1

BUILD
The second name is the permanent device name. This is the name by
which OS/8 identifies the physical device. For example, TC08 DECtape
unit 3 has the group name TC and the permanent name DTA3.
When OS/8 software is supplied on DEC tape or LINCtape, BUILD
the device handlers shown in Table 9-1.

includes

Table 9-1
Standard DEC tape System Device Handlers

Handler

Group
Name

Permanent
Name (s)

TC08 DEC tape system handler

TC08

SYS

TC08 nonsystem DEC tape
drives 0-3

DTAO-DTA3

12K TD8E DEC tape system
handler and drives 0 and 1

TD8E

SYS, DTAO, DTAI

8K ROM TD8E DEC tape system
handler and drives 0 and 1

ROM

SYS, DTAO, DTAI

TD8E nonsystem DEC tape
drives 0 and 1

TD8A

DTAO, DTAI

TD8E nonsystem DEC tape
drives 2 and 3

-TD8B

DTA2, DTA3

RK8E disk system handler

RK8E

SYS ,RKBO

RK8E disk nonsystem handler

RK05

RKAO, RKAl,
RKBO, RKBI

RK8 disk system handler

RK8

SYS, RKAI

RK8 disk nonsystem handler

RKOI

RKAO, RKAI

LINCtape system handler

LINC

SYS

LINCtape nonsystem handler

LNC

LTAO-LTA3

RF08 disk system handler

RF08

SYS

Console terminal (2-page ha ndler)

KL8E

TTY

High-speed I/O simulated on
ASR-33 Teletype

KS33

PTR, PTP

High-speed reader/punch

PT8E

PTR, PTP

LP08, LS8E, LV8E line print ers

LPSV

LPT

TA8E cassette drives 0 and 1

TA8A

CSAO, CSAI

PDP-12 scope

VR12

The handlers supplied with a DECtape or LINCtape system are on the
System Tape 12
(AL-4712C-BA).
To include extra handlers in BUILD,
mount this tape and use the LOAD command.
9-2

BUILD
9.1.1

Cassette Systems

When OS/8 software is supplied on cassettes, the device handlers shown
in Table 9-2 are included in BUILD.
Table 9-2
Standard Cassette System Device Handlers
Group
Name

Permanent
Name(s)

RK8E

SYS, RKBO

RK8

SYS, RKAI

RF08

SYS

DF32 disk system handler

DF32

SYS

Console terminal (2-page handler)

KL8E

TTY

High-speed I/O simulated
on ASR-33 Teletype

KS33

PTR, PTP

High-speed reader/punch

PT8E

PTR, PTP

TA8E cassette drives 0 and 1

TA8A

CSAO, CSAI

Handler
RK8E disk system handler
RK8 disk system handler

RF08 disk system handler

LPSV_ _ L----.
LPT

LP08, LS8E, LV8E line printers

___

These handlers are present on the system cassette AR-4588C-BA.
To
include extra handlers in BUILD, build an OS/8 system, use MCPIP to
move specific device handlers onto the system device,
then use the
BUILD command LOAD. MCPIP is discussed in detail in Chapter 18.

9.1.2

Paper Tape Systems

When OS/8 software is supplied on paper tape,
shown in Table 9-3 are included in BUILD.

the

device

handlers

Table 9-3
Standard Paper Tape System Device Handlers
Group
Name

Handler

Permanent
Name(s)
~~----~

RK8E disk system handler

RK8E

SYS, RKBO

RK8 disk system handler

RK8

SYS, RKAI

RF08 disk system handler

RF08

SYS

DF32 disk system handler

DF32

SYS

(continued on next page)

9-3

BUILD

Table 9-3
(Cont.)
Standard Paper Tape System Device Handlers
Group
Name

Permanent
Name (s)

Console terminal ( 2-page handler)

KL8E

TTY

High-speed I/O simulated
on ASR-33 Teletype

KS33

PTR, PTP

High-speed reader/punch

PT8E

PTR, PTP

TA8E cassette drives 0 and 1

TA8A

CSAO, CSAI

LP08, LS8E, LV8E line printers

LPSV

LPT

Handler

Two binary paper tapes provide other OS/8 handlers not included in
BUILD:
AK-4660C-BA
contains
the
file-structured
handlers;
AK-4671C-BA contains character-oriented handlers. These tapes contain
handlers that you can load into core using the BUILD command LOAD.
The BUILD device handler tapes are composed of separate segments, with
a short length of leader/trailer code between them.
(All of these
handlers are in the special format described in BUILD Device Handler
Format in this section.) Table 9-4 contains a list of the handlers
that are included on the tapes. The handlers are listed in the order
in which they appear on the tapes. The TC08 handler is the first
segment on handler tape tl, and the KL8E terminal handler is the first
segment on handler tape 42. The segments should be either labeled or
separated for easier use.
To utilize a binary handler file, place the desired segment into the
paper tape reader. Use the BUILD command LOAD to load that segment as
follows:
$LOAD PTR [:]

Type a colon
(:) after the device name if
you
loaded BUILD from an OS/8 system device. The
allows time to place the tape in the reader. Type
any keyboard character to load the tape. When the
$ reappears, the handler has been loaded into
BUILD's table.
Type the BUILD command PRINT to
verify that the handler has been loaded.
A

Table 9-4
OS/8 Device Handlers

Permanent
Name (s)

File Name
on DECtape,
LINCtape, or
Cassette

Handler

Group
Name

TC08 DEC tape system handler

TC08

SYS, DTAO

TC08SY.BN

12K TD8E DEC tape system
handler

TD8E

SYS, DTAO, DTAI

TD8ESY.BN

8K ROM TD8E DEC tape
system handler

ROM

SYS, DTAO, DTAI

ROMMSY.BN

(continued on next page)
9-4

BUILD

Table 9-4
(Cont.)
OS/B Device Handlers

Handler

Group
Name

Permanent
Name(s)

File Name
on DECtape,
LINCtape, or
Cassette

LINCtape system handler

LINC

SYS, LTAO

LINCSY.BN

RKBE disk system handler

RKBE

SYS, RKAO, RKBO

RKBESY.BN

RKB disk system handler

RKB

SYS, RKAO, RKAI

RKOBSY.BN

RFOB disk system handler

RFOB

SYS

RFOBSY.BN

DF32 disk system handler

DF32

SYS

DF32SY.BN

TDBE DECtape drives 0 and I

TDBA

DTAO, DTAI

TDBEA.BN

TDBE DECtape drives 2 and 3

TDBB

DTA2, DTA3

TDBEB.BN

TDBE DECtape drives 4 and 5

TDBC

DTA4, DTA5

TDBEC.BN

TDBE DECtape drives 6 and 7

TDBD

DTA6, DTA7

TDBED.BN

TCOB DEC tape drives 0-7

DTAO-DTA7

TCOBNS.BN

LINCtape drives 0-7

LNC

LTAO-LTA7

LINCNS.BN

RKBE disk nonsystem handler

RK05

RKAO-3, RKBO-3

RKBENS.BN

RKB disk nonsystem handler

RKOI

RKAO-RKA3

RKOBNS.BN

RFOB disk nonsystem handler

RF, NULL

RKOBNS.BN

DF32 disk nonsystem handler

DF32NS.BN

RXOISY disk system handler

RXBE

SYS

RXOISY.BN

RXOINS disk nonsystem handler

RXOI

RXAO.RXAI

RXOINS.BN

VT50 VT-50 input handler

VT50

LST

VT50.BN

LQP line printer handler

LQP

LPT

LQP.BN

Octal block DUMP handler

DUMP

DUMP.BN

RX7BB disk nonsystem
handler (for VT-7B only)

RXOI

RXA2, RXA3

RX7BB.BN

Console terminal (2-page
handler)

KLBE

TTY

KLBE.BN

Console terminal (I-page
handler)

AS33

TTY

ASR33.BN
(continued on next page)

9-5

BUILD
Table 9-4
(Cont.)
OS/B Device Handlers
-~----;--

Group
Name

Handler

Permanent
Name (s)

File Name
on DECtape,
LINCtape, or
Cassette

High-speed I/O simulated on
ASR-33 Teletype

KS33

PTR, PTP

LSPT.BN

High-speed reader/punch

PTBE

PTR, PTP

PTBE.BN

LPOB, LSBE, LVBE line
printers

LPSV

LPT

LPSV.BN

Anelex 645 line printer

L645

LPT

L645.BN

Card reader

CRBE

CDR

CRBE.BN

BATCH handler

BAT

BAT.BN

PDP-12 scope

VRl2

VRI2.BN

TUIO magnetic tape drives 0-7

TMBE

MTAO-MTA7

TMBE.BN

TABE cassette drives 0 and I

TABA

CSAO, CSAI

CSA.BN

TABE cassette drives 2 and 3

TABB

CSA2, CSA3

CSB.BN

TABE cassette drives 4 and 5

TABC

CSA4, CSA5

CSC.BN

TABE cassette drives 6 and 7

TABD

CSA6, CSA7

CSD.BN

9.2

CALLING AND USING BUILD

BUILD is distributed as both a binary paper tape or cassette and as a
core image file
(BUILD.SV)
on the system DECtape or LINCtape. You
should load and save the binary BUILD file on the system device when
you build the initial system (see OS/B System Generation Notes). To
use the BUILD.SV file on the system aevice, type the following command
in response to the dot the OS/B Keyboard Monitor prints:
.RUN SYS BUILD
NOTE
It is important that you specify the RUN
command, rather than the R command, when
loading BUILD into core.
This will
allow the use of the SAV command without
specifying SAVE arguments.
BUILD responds by printing a $, signaling that it is ready
commands.

BUILD uses a keyboard monitor similar to the one contained in the OS/B
system.
Text is input from the terminal and interpreted by BUILD.
Table 9-5 lists the special characters that are available for editing.
9-6

BUILD
Table 9-5
BUILD Editing Characters
Character

Function

ALT MODE key

Terminate
execution.
generated.

CARRIAGE RETURN

Terminate
command;
begin
execution.
Also
generate
return/line feed combination.

CTRL/C

Terminate command;
return
the OS/8 Keyboard Monitor.

CTRL/O

Terminate
BUILD.

CTRL/U

Ignore line;

LINE FEED key

Examine contents of the command line.

RUBOUT key

Delete the last typed
command.

command;
begin
command
No carriage return/line feed is

printing;

command
carriage

immediately

return

control

character

A-Z, 0-9, SPACE, PERIOD, =, COMMA, COLON, HYPHEN
Typing any other character causes the error message:

SYNTAX ERROR

BUILD COMMANDS

The commands available in BUILD are:
ALTER
BOOT
BUILD
CORE
CTL
DCB
DELETE
DSK
EXAMINE

INSERT
LOAD
NAME
PRINT
QLIST
REPLACE
SYSTEM
UNLOAD
VERSION

The general format of the command string is:
$command args

9-7

the line may be typed again.

from

The standard characters permitted in a BUILD command line are:

9.3

the

BUILD

where command represents a legal command
represents a file name, device, group
associated with the command. You can type
abbreviate it to the first two characters.

from the list and args
name, or other argument
the command in full or
For example:

$PRINT
and
$PR
are the same. If you attempt to issue an illegal command, BUILD
replies by printing the illegal command preceded by a?
Thus the
illegal command ERASE would appear:

fERASE
?ERASE

r-"

9.3.1

The Hyphen Construction

Certain BUILD commands (DELETE, INSERT, REPLACE) allow the use of the
hyphen construction to specify more than one permanent name. These
permanent names must be four characters long and must differ only in
the last character.
You can insert permanent names that meet this
restriction with the hyphen construction, so long as the last
characters form a sequence of consecutive ASCII characters.
For example, if you wish to delete DEC tape handlers DTAO, DTAl,
and DTA3, type:

DTA2,

$DELETE DTAO,DTA1.DTA2,DTA3
or you can use the hyphen construction and type:

$DELETE DTAO-3

9.3.2

Syntax:
$PRINT or $PR
Function:
Prints detailed list of the
example shows five handlers.

RFOS:
RKSE:
Kl HE :
P11I1":
LF"bV:

SYS
*SYS
*TTY
PTR
LPT

BUILD

devices

tables.

The

following

*RKBO
*PTP

Group names are printed first in each line, followed by a colon.
Following the group name is the list of permanent names available with
each group.
If one of the permanent names in a group is SYS, then
this handler can be a system handler. An OS/8 system must have just
one system handler.
Some system handlers have other coresident
handlers.

9-8

BUILD
Any handler that is active is marked with an asterisk to the left of
its permanent name (RKBO, TTY, PTP in the printout), and the devices
will be included in the new OS/8 system (i.e., these handlers were
inserted with the INSERT, SYS, or REPLACE commands. Other commands
are available for removing, loading, and deactivating handlers).
The
preceding printout indicates that RK8E is the system device. The
handler RK8E:RKBO is also marked as being active.
After printing the list of available handlers, the PRINT command might
also
print some additional information.
If,
for example, you
specified RK8E:RKBO with the DSK command, the following is printed:
DSK=RKSE:RKBO
If you specified the core command to restrict the
message:

core

12K,

the

CORE=2
is printed, indicating that field 2 is to be the
available to the OS/8 system.

9.3.3

highest

core

field

QLIST

Syntax:
$QLIST or $QL
Function:
List the active permanent names on the system. No * is printed
the system device is the only group name printed. For example:

and

$QLIST

~TR DTA3 RKOS:SYS LPT DTA4

9.3.4

LOAD

Syntax:
$LOAD activename or $LOAD dev:filename
Function:
Use LOAD to load a new device handler into BUILD. This handler can be
one supplied by DIGITAL or one you have written. See the OS/8
Software Support Manual (DEC-S8-0SSMB-A-D) for instructions on writing
device handlers.- This handler is input into BUILD as a binary file or
image.
If you are running BUILD stand-alone, e.g., to create an initial
system, the LOAD command has the form:

OS/8

$LOAD activename
where activename is the permanent name of an input device handler that
the INSERT, REPLACE, or SYSTEM command has made active.
It must be a
handler for a non-file structured device. For example, to load a new
handler from a binary paper tape with the PTR handler already in
BUILD, type:
!LOAD PTR
9-9

BUILD
If you are running BUILD under control of OS/8, the LOAD
the form:

command

has

$LOAD dev:filename
where dev is an input device handler that exists in the current OS/8
system.
(These are not the same as the handlers that BUILD marks
active.) If no dev:
is specified, DSK:
is assumed.
If dev:
is non-file structured (i.e., paper tape), you may
filename. The filename has the form:

omit

the

name.extension
Filename is the binary file of the new handler to be loaded.
The
default extension is .BN. If you use no extension, you may omit the
dot (.).
Example:

$LOAD DTA3:HANDLR.03

Load a file named HANDLR,
extension of 03, from DTA3.

with

You may specify several files that you are loading on one line.
Separate the files by commas.
You must specify a device for each
file, or DSK will be assumed. If multiple files are specified, each
file must contain a separate handler to be loaded. For example:

$LOAD DTA3:FILE1,DTAS:FILE2
Once you have successfully issued the LOAD command, the new device
handlers become available for further manipulation. The new handlers
will appear in the PRINT output, but will not be marked as active.

9.3.5

INSERT

Syntax:
$INSERT gname,pname
Function:
After a LOAD command has made a handler or group of handlers available
for insertion into the OS/8 system, use the INSERT command to make
particular entry points active.
The INSERT command
uses
two
arguments;
gname and pname. Gname is the group name of the handler,
for example, the gname for TC08 DECtape is TC. Pname is the permanent
name by which the device is currently known to BUILD. See Table 9-4
for a complete list of permanent device names. TC08 DECtape thus has
the group name TC and the permanent names DTAO-DTA7.
Examples:

$IN "'L8E.TTY
,!IN TC08.SYS
If you specified no permanent name (and no :), the first name
device group is assumed. For example:

$INSERT TC
would assign DTAO as the permanent name.

9-10

the

BUILD
You can insert several handlers in the same group into the same
command by separating the permanent names with commas. For example:
SIN TC,DTAO,DTA3,DTA7
If several permanent names (each four characters long) differ only in
the last character, you can insert them simultaneously with the hyphen
construction so long as the last characters form a sequence of
consecutive ASCII characters.
Example:
!INSERT TC,DTA2-5
is the same as
$INSERT TC,DTA2,DTA3,DTA4,DTA5
and
~INSERT

RK01,R~AO-2

is the same as
$INSERT RK01,RKAO,RKA1,RKA2
If the permanent name specified is not part of the group name
specified, or if the group name does not exist, the following message
is printed:
name NOT FOUND
If disk is the device you are inserting, you can follow the group name
with a construction of the form:
pname=n
Where n is a digit in the range 1 to 7 and represents the number of
platters available. Use this option for the RF08 and DF32 disks. For
example:
.!IN RF,RF=2
If you specify no such option, =1 is assumed. If n is too
the device specified, the following message is printed:

9.3.6

large

for

DELETE

Syntax:
$DELETE aname
Function:
DELETE takes a device that is currently marked as active and makes it
inactive.
(Active devices are marked with an * in the PRINT command
output and are printed by the QLIST command.)
The argument for DELETE is the permanent name of the device. You can
obtain the current permanent name from the PRINT or QLIST output. The
major function of DELETE is to make device slots available to BUILD.
9-11

BUILD

For example, assume that the QLIST command output is:

DTAO DTAl RKBE:SYS RKBO TTY LPT CSAO CSAl CSA2 CSA3
If the following command is issued to BUILD:

$DELETE CSAO,CSA1,CSA2,CSA3
CSAO, CSAl, CSA2, and CSA3 will no longer be permanent devices, and
the slots used by the TA8A and TA8B device groups will be made
available to BUILD. The QLIST output after the above command will be:

DTAO DTAl RKBE:SYS RKBO TTY LPT
Note, as previously explained, that you can
use
the
hyphen
construction in DELETE to remove a sequence of devices. Therefore,
you can type the command to make the cassette handlers inactive as
follows:

!DELETE CSAO-3

9.3.7

REPLACE

Syntax:
$REPLACE pname=gname, pnamel
Function:
REPLACE combines the functions of DELETE and INSERT to delete one
device and activate another in a single step. The arguments for
REPLACE are:
pname

The permanent name of the device to be deleted.
(Same as the argument of the DELETE command.)

gname, pname2

The group name and permanent
name
of
the
particular device to be inserted into the system
(see INSERT for more details).

Example:
Assume the PRINT output is:

RKAl

RKBl

Use REPLACE to delete the card reader (CDR) and
group handler for RKAO:

!REPLACE CDR=RK05,R~AO
The output of PRINT after this REPLACE is:

P11:!t)
*PTP
*PTR
CRII F· "'-:---':''':'''C-'D'':'R--:''':'''''':'':''';'
RKOS:
*RKAO
RKBO

RKAl

RKBt

9-12

insert

the

RK05

BUILD
Use the hyphen construction with REPLACE to delete and insert more
than one device handler. For example, assume you are replacing the
LINCtape handlers LTAO, LTAI, LTA2, and LTA5 with DEC tape handlers
DTAO, DTAI, DTA2, and DTA5. The following command accomplishes this:

$REPLACE LTAO-2,LTAS=TC,DTAO-2,DTAS

9.3.B

UNLOAD

Syntax:
$UNLOAD gname, or $UNLOAD gname, pname
Function:
Use UNLOAD to delete a handler group
(gname) or a permanent name
from the BUILD system.
(This differs from DELETE, which does
(pname)
not physically eliminate a device.) Use UNLOAD primarily when the NO
ROOM error occurs during a LOAD command.
For example, assume you are removing
handlers. Type the command:

the

entire

group

LINCtape

!UNLOAD LNC
This command unloads the LINCtape handler LNC and all permanent
(LTAO, LTAI, LTA2, LTA3, etc.) associated with it.

names

To remove a particular permanent name from BUILD, e.g., DTA3, type:

$UNLOAD TC:DTA3
This command unloads only the entry point name.
To remove several permanent names, but not the entire group, use
UNLOAD command, with commas separating the permanent names.
example:

the
For

$UNLOAD TC:DTAO,DTA2
You cannot use the hyphen construction with the UNLOAD command.

9.3.9

NAME

Syntax:
$NAME pname=pnamel
Function:
The NAME command allows you to alter the device name that will be used
by OS/B.
The first argument, pname, must be the current name of a
device marked active in the PRINT output. Pname2 is the name you wish
to call this device. You may use only 4-character device names in the
NAME command. If you enter longer names, all characters beyond the
first four are ignored.
After you use the NAME command, pname2
becomes the current permanent name; pname is unknown to BUILD.

9-13

BUILD

Example:
Assume that the PRINT output is:
R"~iE: : - - .+(;YS

*nTAO

*DTAl
*RKBO

KUII" :
P1I:IE:

*TTY
*PTP

*PTR

DTA3

DTA:!

To change the paper tape reader so that it is
permanent name READ, use the following command:

recognized

the

$NAME PTR=READ
The output from PRINT would then be:
TC
R"'"BE" :
KKBf:
PT-SE";

*DTAO
*SYS
*TTY
*PIP

*DTAl
*RKBO

DTA2

DTA3

*READ

If the permanent name specified as pname is
device, the message:

not

currently

active

pname NOT FOUND
is printed. If this message appears,
determine the correct permanent name.

the

output

The ALTER command allows you to change locations in
The arguments are:

device

handlers.

9.3.10

check

ALTER

Syntax:
$ALTER gname, loc=newvalue
Function:

gname

Group name of the handler.

loc

Alter relative octal location.
If the handler is
a I-page handler, loc must be an octal number in
the range 0-0177.
If it is a 2-page handler, loc
must be an octal number in the range 0-0377.

newvalue

An octal number specifying the new contents of the
location specified by loco
If you do not enter
=newvalue, BUILD prints the old value of loc
followed by a slash. You can then enter newvalue
or type a carriage return to retain the old value.

9-14

BUILD
9.3.11

EXAMINE

Syntax:
$EXAMINE gname, loc
Function:
EXAMINE allows you to examine, but not modify,
device handler. See the ALTER command.

9.3.12

location

within

DSK

Syntax:
$DSK=gname,pname or $DSK=aname
Function:
Use the DSK command to specify which device
DSK, the default storage device for OS/8.
of the command, i.e.,

you are designating as
If you use the first form

$DSK=gname,pname
the gname is the group name of the device, and pname is the
name. For example:

permanent

$DS~=TC08:DTAO

assigns DTAO as the device called DSK.
When you issue the DSK command, you need not enter the permanent name.
However, you must enter the permanent name, via an INSERT, REPLACE, or
SYSTEM command before you issue the BOOT command.
If you use the second form of the command, i.e.,
$DSK=aname
aname must be a permanent name BUILD marks as active.
For example,
the following command specifies the already active device RKAO as the
default device DSK:
$DS~=RKAO

If you enter no DSK command, or if you issue the
argument, i.e.,

command

$DS~=

or
$DS~

BUILD specifies SYS as DSK when you issue a BOOT command.

9-15

without

BUILD
9.3.13

CORE

Syntax:
SCORE n
Function:
You use the CORE command to specify the highest core field available
to the OS/8 system being built. The n is an octal number in the range
o to 7. If n is 0 or omitted, or if you do not use the CORE command,
the built system will use all of the available core.
If n specifies
more core than is available, the following message is printed:
?CORE
The value of n for the available core sizes is as follows:
Value of n

Core

all available core
8K
12K
16K
20K
24K
28K
32K

1
2
3
4

5
6
7

For example, a system that is to use only 24K of a 32K system requires
the following CORE command:
$CORE 5

9.3.14

DCB

Syntax:
$DCB aname or $DCBaname=newvalue
Function:
The DCB command
associated with
DCB words) •

allows you to examine or modify the DCB word
a permanent name (see Section 9.5 for information on

The DCB word is the first word that appears after the permanent name
in a description (from the handler header information words). Aname
must be the permanent name of a device currently marked as active in
the PRINT output.
Example:

!DCB DTA4=6160
changes the DCB of DTA4 so that this handler
device. You could also type this command as:

!DCB DTA4
4160/6160

9-16

becomes

read-only

BUILD
9.3.15

CTL

Syntax:
$CTL aname=loc
Function:
The CTL command allows you to modify the control word that
after the DCB word in the handler header block. For example:

appears

!CTL LTA3=24
changes the entry point of the LTA3 handler to relative location 24.

9.3.16

VERSION

Syntax:
$VERSION or $VE
Function:
The VERSION command prints BUILD's version number on the terminal.

9.3.17

SIZE

Syntax:
$SIZE aname or $SIZE aname=new value
aname must be the permanent name
active.

device

currently

marked

Example:
!SIZE RF08=-1777
changes the length of the RFOB handler to 1777.
Function:
The SIZE command modifies word ten of a handler header block.
Word
ten specifies the size,
in blocks, of a single platter on a system
device.

9.3.lB

SYSTEM

Syntax:
$SYSTEM sname=n
Function:
The SYSTEM command specifies devices that are system handlers or that
are coresident with system handlers. The number n reflects the number
of platters included in the system device
(valid only for multiple
platter RFOB and DF32 disks).
(Table 1-6 lists the available system

9-17

BUILD

handlers and their associated values for n.) The argument sname must
be one of the legal device system names. If it is not, BUILD prints:

'!'SYS
thereby requesting a new system specification.
Action is not taken on the SYSTEM command until you give the BOOTSTRAP
command, so you may respecify a device with SYS. The system device
used is the last one issued prior to the BOOT command.
Specifying a
new system device is not always necessary. For example, if you wish
to insert new peripheral handlers, then this command is not needed.
If you do not issue it, the OS/8 resident system is not affected
beyond having altered device tables.
BUILD includes the SYSTEM command only so it will be compatible with
older versions of BUILD. You can specify the system device with the
INSERT command. For example, the command:

!SYS RFOS=2
is the same as the command:

!INSERT RFOS,SYS=2
If the device specified in the SYS command is not the current system
device, you will have an opportunity to have a zero directory placed
on your new system device. If the system device is the same as the
current system device, no new directory will result.

9.3.19

BUILD

Syntax:
$BUILD or $BU
Function:
You use the BUILD command only when building an initial OS/8 system
from cassettes or paper tape. When you type the BUILD command, BUILD
prints:

LOAD OS/S:
to which you must respond by typing the device that contains
OS/8 monitor, e.g.,

BUILD then loads and writes the various parts of OS/8 onto the
device. After writing OS/8, BUILD prints:

the

new

system

to which you respond with the appropriate device, or with a carriage
return to specify that the device is the same as the one specified in
the LOAD OS/8: message. BUILD loads the Command Decoder and writes
it onto the system device.
Do not use the BUILD command at any time other than while building an
initial OS/8 system.
When you type this command, OS/8 assumes that
you are building a new OS/8 system.
It automatically zeroes the
system device directory.
Refer to the OS/8 System Generation Notes
for instructions on building an initial system.
9-18

BUILD
9.3.20

BOOTSTRAP

Syntax:
$BOOTSTRAP or $BO
Function:
BOOTSTRAP is the command that finally implements all the changes that
you made with BUILD. BOOT rewrites all relevant Monitor tables and
device handlers to reflect the updated system status.
The devices
BUILD had marked active now become device handlers in the system.
Before you type a BOOTSTRAP command,
device with either the SYSTEM or
specified, the message:

you must specify the system
INSERT command.
If no SYS is

SYS NOT FOUND
is printed.
If the system device specified is different from the current system
device, BUILD copies the system from the current system device to the
new system device. After the copy is complete, BUILD asks:

WRITE ZERO DIRECT?
to determine whether a new (zero) directory is to be written on the
new system device. If the reply is YES, the system will place a zero
directory on the device. Any other reply causes the system to retain
the old directory.
NOTE
Exercise care if you want the
old
directory retained. The directory must
be one of an OS/8 system device.
After you answer this question, BUILD updates the system and prints:

SYS BUILT
Control returns to the Keyboard Monitor. When the BOOTSTRAP command
has performed its functions and the Keyboard Monitor is once again
active, save the copy of BUILD just used. This way, an image of the
current system status is preserved, and you can use the saved copy of
BUILD again. When it is used again,
the devices initially marked
active remain marked active. To save BUILD, type:

.SAVE SYS BUILD
in response to the dot printed by the Keyboard Monitor. This assumes
that you originally loaded BUILD into core with a RU or RUN command.

9-19

BUILD
9.4

BUILD ERROR MESSAGES

The following is a list of error messages that may appear when
BUILD. These messages usually indicate a syntax or user error.

using

Table 9-6
BUILD Error Messages
Message

Explanation

?BAD ARG

No device name was
command.

?BAD INPUT

An error was detected in the binary file;
it is not a proper input for the LOAD
command.

?BAD LOAD

An attempt was made to load a binary
handler that is not in the correct format.

?BAD ORIGIN

The origin in a binary file is not
range 200-577.

?CORE

A CORE command specified more memory than
is
physically
available, or the BOOT
command was issued on an 8K system with a
2-page system handler active.
Two-page
system handlers require at least 12K of
core to be present on the OS/8 system.

?DSK

The device specified in a DSK
not a file structured device.

?HANDLERS

More than 15 handlers,
including SYS and
DSK, were active when a BOOT command was
issued.

I/O ERR

An error occurred while reading from
input device during a LOAD command.

?NAME

A device or file name was not designated in
a command that requires one to be present.

NO ROOM

Too many device handlers were present on
the system when a LOAD or BUILD command was
typed. The UNLOAD command must be used to
remove a handler before another can be
loaded.

name NOT FOUND

The device or file name designated
command was not found.

the

?PLAT

The =n in a SYS command is too large
the device specified, e.g., RF08=5.

for

?SLOTS

More than eight groups
of
non-system
handlers were inserted. Each slot may have
more than one entry point.
To correct,
delete PNAMES until there are eight or
fewer nonsystem handlers.

included

the

command

LOAD

the

(continued on next page)
9-20

BUILD
Table 9-6
(Cont.)
BUILD Error Messages
Message

Explanation

~-------------------~--------------------------~--------------~--;

?SYNTAX

An illegal character was typed in a BUILD
command line. The line must be retyped.

?SYS

One of the following conditions exists:
a.
b.
c.

A permanent name in a SYS command was
not a system handler or coresident with
one.
A BOOT command was issued when two or
more system handlers were active.
A BOOT command was issued when an
active handler that must be coresident
with a SYS handler did not have the
system handler active.

SYS ERR

An I/O error occurred with
a
system
handler.
The computer halts.
Press CONT
to retry or restart the BUILD procedure
from the beginning. Do not assume that a
valid OS/8 system remains in core.

SYS NOT FOUND

No active handler with the name SYS
present
when
a BOOTSTRAP command
issued.

was
was

~-------------------~-----------------------------------------------------~

9.5

BUILD DEVICE HANDLER FORMAT

Use the BUILD command LOAD to load device handlers not provided by
BUILD into core. They can then be inserted into the OS/8 system. The
format of the input to LOAD is a binary file containing the handler as
well as a header block that contains information pertaining to the
devices included in that file.
You should code the handler
in PAL8
machine language.
The structure of the source for a BUILD device
handler is:
*0
HEADER BLOCK
*200
BODY OF DEVICE
HANDLER
The origins at 0 and 200 are vital to BUILD. The *0 is an important
part of the header block.
If you omit this, you cannot load. The
*200 is also necessary for loading.
If the handler contains an origin
outside the range 200-577, BUILD generates an error message and then
aborts the load.

9-21

BUILD
9.5.1

Header Block

The header block contains the following information:
Word 1:

-x, where X is the

Words 2-9:

Descriptor block for
group.

Words 10-17:

Descriptor block for second handler in the group.

number of separate handlers
contained in this file. Thus a handler for TC08
has the first word equal to -lO(octal).
the

first

handler

the

Descriptor block for the last handler in the
group.
If the handler is a system handler, the
length of the bootstrap and the bootstrap itself
follows.
Thus, each handler in the group must have an eight-word block
describing its characteristics. If more than twelve handlers are in a
group, an error generates during the LOAD.

9.5.2

Descriptor Block

Each eight-word descriptor block contains the following information:
Words 1,2:

Device type name. This name is the group name, or
type, of all the handlers in this group. It is
usually designated by the DEVICE pseudo-oPe
Example:

Words 3,4:

(permanent
OS/8 device name. This is the name
name)
by which the particular device will be
recognized in the OS/8 system. The NAME command
can alter it.
Example:

Word 5:

DEVICE RKAO

Device Control Block. This word reflects the type
of device,
in accordance with Table 9-7.
Bits
9-11 specify the maximum number of platters on the
device (0=1).
Example:

Word 6:

DEVICE RK8

4050

Entry point word.
This word must contain the
entry point offset in bits 5-11
(see Section
9.5.4). Bit 0 should be a 1 if the handler is a
two-page handler.
Bit 1 should be a 1 if the
entry point is SYS. Bit 2 should be a 1 if the
entry point is coresident with SYS.
Example:

0020

9-22

BUILD
Word 7:

Must be O.

Word 8:

Must be 0, except for a system handler that uses
it to specify the block length of the device as a
negative number.

As an example, consider the handler for the nonsystem RKOS handlers.
This file contains four separate handlers;
the source code would
appear as follows:
*0
-4
DEVICE RKOS;
DEVICE RKOS;
DEVICE RKOS;
DEVICE RKOS;

/4 DEVICES
DEVICE RKAO;
DEVICE RKBO;
DEVICE RKAl;
DEVICE RKBl;

40S0;
40S0;
40S0;
40S0;

0020;
0021;
0022;
0023;

ZBLOCK
ZBLOCK
ZBLOCK
ZBLOCK

2
2
2
2

*200
(HANDLER BODY)
The device type of the group is RKOS
(Words 1-2).
The permanent
device names are RKAO, RKBO, RKAl, RKBI. Since each device is RKOS,
the device control block (DCB) word for each is identical.
The entry point word indicates where the entry point for that
particular device occurs relative to the top of the page. Thus, in
the above example, RKAO enters at the 20th location from the top of
the page, RKBO at the 21st, etc.
It is vital that this information is accurate.
If errors exist in
this data, unpredictable results occur when you generate the system.

9.S.3

Breakdown of DCB Word

The DCB word for a device provides specific information that
in the OS/8 Monitor. Table 9-7 details its structure.

used

Table 9 . . . 7
DCB Word
r--~------.---.----

Bit

---------------

Meaning

if file structured device

if read-only device (e.g., PTR)

if write-only device (e.g., LPT)
Device Type

3-8

00
01
02
03
04

console terminal

= high-speed paper tape reader
= high-speed paper tape punch
= card reader
line printer

-------------------~

(continued on next page)

9-23

BUILD
Table 9-7
(Cont.)
DCB Word
Meaning

Bit

Device Type
3-8
(Cont. )

9-11

05 = RK8 Disk
06 = RF08 (1 platter)
07 = RF08 (2 platter)
10 = RF08 (3 platter)
11 = RF08 (4 platter)
12 = DF32 (1 platter)
13 = DF32 (2 platter)
14 = DF32 (3 platter)
15 = DF32 (4 platter)
16 = TC08 DEC tape
17 = LINCtape
20 = TM8E magnetic tape
21 = TD8E DEC tape
22 = BAT - BATCH handler
23 = RK8E disk
24 = NULL - NULL handler
25 = RXOI diskette
26 = Unused
27 = TA8E cassettes
30 = PDP-12 scope
31-35 = Unused by DIGITAL
36 = Dump Handler
37 = Unused by DIGITAL
40-77 = Reserved for user-written handlers
Used only by OS/8 Monitor

Whenever you insert a device
obtain correct results.

9.5.4

into

OS/8,

this

structure

Entry Point Offset

Word 6 of each device descriptor block specifies the relative entry
point of that particular handler. Devices supplied by DIGITAL have a
fixed set of entry points, described below.
Use care when coding new device handlers for insertion into the
system.
The entry point offset for the new handler must not be the
same for any other file structured device in the system. For example,
OS/8 currently uses relative entry points 7-24 for file structured
devices. No new handler should have entry points at 7 to 24 of the
page. If this occurs, the system may perform incorrectly.

9-24

BUILD
Current file device and entry point offsets appear below:
Entry Relative to Top of Page

Device

10-17
10-17
10-17

TC08 DEC tape
TD8E DEC tape
LINCtape
System device
RK8/RK8E disk
RF/DF disk
RXAO
RXAI

20-23
24
30
34

Thus, the user-coded file devices should use entry points
7-24, 30, 34.

other

than

If you add a new file structured user device to the system, alter the
device-length table in PIP to permit zeroing of the device directory.
To do this, use ODT as follows:
.GET SYS PIP
.ODT
136nn/0000 xxxx
~C

(user types CTRL/C)

.SAVE SYS PIP
The nn represents the two-digit device Table 9-12 indicates. The xxxx
is the negative of the last block number on the device. Both nn and
xxx x are octal numbers.
For example, if you assign the new device a code of 40 (currently the
first unused entry), and the last OS/8 block on the device was block
1000, PIP would change as follows:

.GET SYS PIP
70DT
13640/0000 7000

...!.SAVE SYS PIP

9.6

CREATING A SYSTEM HANDLER

When you create
restrictions:

new

system

handler,

observe

the

following

•

The length of a bootstrap must be greater than or equal to 21
(octal)
locations.
You must pad a bootstrap shorter than 21
locations, otherwise BUILD results are unpredictable.

•

The length of the bootstrap must be less than or equal to
(octal) locations.

•

If the system handler is a one-page handler, only the first 47
(octal)
locations of the bootstrap are significant. The
remaining locations are ignored and not written on the system
device.
Also, no handler may have more than 20 (octal) entry
points.

•

If a system handler is two pages long, relative location 12 of
the first page must contain a 3. The second page loads into
location 27600 and is stored on block 66 of SYS:.

9-25

177

CHAPTER 10
CASSETTE AND MAGNETIC TAPE POSITIONER (CAMP)

The CAMP program positions cassettes, magnetic tapes, and
other devices. To call CAMP from the system device, type:

certain

.R CAMP
in response to the Keyboard Monitor dot. CAMP prints a i to indicate
it is ready to receive a command. You may terminate the command line
you enter with a carriage return (CAMP retains control) or an ALTMODE
(control returns to the Keyboard Monitor).

10.1

CAMP COMMANDS

Each CAMP command begins with a keyword consisting of two or more
letters.
You need not type the full CAMP command; however, each
command has letters that are required. The CAMP commands appear below
in alphabetical order. Letters not required are underlined.
BACKS.PACE
EOt
HELP
REWIND
SKIP
UNLOAD
VERSION

10.1.1

BACKSPACE Command

The BACKSPACE command spaces a magnetic tape or cassette backward a
specified number of files or records. You may also issue this command
indirectly with the CCL BACKSPACE command.
The BACKSPACE command has the form:
Records
BA dev: nnnn
Files
Where "dev:" is the permanent name of a cassette or magnetic tape
drive.
The "nnnn" is an unsigned decimal number representing the
number of records or files to backspace. This number must be in the
range 0-4095.
If you enter no number, nnnn=l is assumed. A keyword
beginning with either an R, indicating records, or an F, indicating
files,
follows this number.
If neither F nor R is entered, F is
assumed.

10-1

CASSETTE AND MAGNETIC TAPE POSITIONER (CAMP)
Examples:
~BA

CSAO:

2 F

positions the cassette mounted on CSAO backward two files.
tBA MTAl:
positions the magnetic tape mounted on MTAl backward one file.
If a file mark is read before the tape
number of records, the message:

has

spaced

over

the

proper

% CAN'T - AT BOF
appears and the device is moved forward one record. This leaves the
device positioned at the beginning of the file (just before a data
record) .
The file where the device is currently positioned is not counted when
you make an attempt to backspace a number of files.
For example, the
command:
tBA MTAl:

3 F

moves the tape backward over four file marks and then moves it forward
one record. The tape is then positioned at the beginning of the file.
If nnnn=O, the tape backspaces to the beginning of the file where it
is currently positioned.

10.1.2

EOF Command

The EOF command writes a single file mark (file gap) on the magnetic
tape or cassette you have specified. You may also issue this command
indirectly with the CCL EOF command.
The EOF command has the form:
EOF dev:
where "dev:" is the permanent name of
drive.

cassette

magnetic

tape

Example:
tEOF CSAl:

10.1.3

HELP Command

The HELP command prints a short message on the console terminal,
reminding you of the CAMP command syntax. The form of this command
is:
~HELP

10-2

CASSETTE AND MAGNETIC TAPE POSITIONER (CAMP)
10.1.4

REWIND Command

The REWIND command issues a rewind command to one of the following
OS/8 device controllers: cassette, magnetic tape, or TC08 DECtape.
The REWIND command form is:
REWIND dev:
where "dev:" can be any OS/8 file structured device. If "dev:" is a
cassette, control returns to CAMP while the cassette is rewinding:
CAMP prints another I, indicating it is ready to receive another
command.
If "dev:" is magnetic tape or TC08 DECtape, the device
rewinds immediately, and control returns to the OS/8 Keyboard Monitor
while the device is rewinding.
If you issue a REWIND command to any
other OS/8 device (e.g., LINCtape), control returns to CAMP after the
device is rewound.
Example:
tRE DTA1:

10.1.5

SKIP Command

The SKIP command advances over the number of files or records you
specified on a magnetic tape.
You may also issue this command
indirectly with the CCL SKIP command. You do not implement the SKIP
command for cassettes.
The SKIP command has the form:
#SKIP MTAn:

nnnn Records
Files
EOD

where MTAn: may be any magnetic tape drive, depending upon the number
of magnetic tape drives on the OS/8 system. The "nnnn" is an unsigned
decimal number representing the number of files or records you are
advancing over.
This number must be in the range 0-4095. EOD
indicates that the tape is to advance to the end of data. The end of
data on a magnetic tape is a point between two file marks.
If the
tape is already past the end of data, rewind it before you issue the
EOD command. If you have specified neither "nnnn" nor EOD, nnnn=l is
assumed.
If you have specified a number, a keyword beginning with R (for
records)
or F (for files) may follow.
If neither F nor R is entered,
F is assumed.
Examples:
tSKIP MTAO:

2 RECORDS

advances the magnetic tape on MTAO:
tSKIP MTA1:

forward two records.

6 F

advances the magnetic tape on MTAl:

10-3

forward six files.

CASSETTE AND MAGNETIC TAPE POSITIONER (CAMP)
If a file mark is read before the tape has advanced
number of records, the warning message:

over

the

proper

% CAN'T - AT EOF
appears and the tape moves backward one record to the end of the file
(just after the last data record but before the file mark). If
nnnn=O, nnnn=l is assumed when skipping records.
The file where the tape is currently positioned is counted when you
attempt to advance over a number of files. Thus nnnn=l means to
advance to the beginning of the next file.
If nnnn is greater than 0,
the tape is positioned at the beginning of a file (just after a file
mark but before any data records). If nnnn=O, the tape advances to
the end of the file where currently positioned (before a file mark,
but after all data records).
If you encounter the end of data before you have skipped the specified
number of files, the warning message:

% CAN'T - AT EOn
appears and the tape is positioned at the end of data.
If a tape is
already positioned at the end of data, the SKIP command produces
meaningless results.

10.1.6

UNLOAD Command

The UNLOAD command rewinds a magnetic tape controller and turns it off
line.
As the tape is rewinding, control returns to CAMP for another
command. You will have to manually turn the magnetic tape on line for
use after you have issued an UNLOAD command.
You may also use the UNLOAD command to unload TC08 and TD8E DECtapes
from their reels. When used on DECtapes, the UNLOAD command rewinds
the DECtape on the unit specified, selects a different unit, and
returns control to CAMP for another command. This DECtape unit cannot
be used until another legal command, e.g., the Keyboard Monitor ASSIGN
command, is issued to the DECtape controller.
You can also use the UNLOAD command to write-lock an RK8E disk.
The UNLOAD command form is:
tUNLOAD dev:
where "dev:" may be anyone of the following:
magnetic tape
TC08 DEC tape
TD8E DEC tape
RK8E disk

10.1.7

VERSION Command

The VERSION command prints the version number of CAMP on the terminal.
This command form is:
tVERSION

10-4

CASSETTE AND MAGNETIC TAPE POSITIONER (CAMP)
10.2

CAMP ERROR MESSAGE SUMMARY

The error messages listed in Table
operation.

10-1

may

appear

during

CAMP

Table 10-1
CAMP Error Messages
Explanation

Messages
% CAN'T - AT BOF

A file mark was read before the
specified number of records were
read over in a BACKSPACE command.
The device is moved forward so
that it is positioned at the
beginning of the file.

? CAN'T - AT BOT

A BACKSPACE command cannot move
the device backward the specified
number of files
because
the
device
is
positioned at the
beginning of the first file.

% CAN'T - AT EOD

The specified number of files
cannot be advanced over because
the end of data was encountered.
The tape is positioned at the end
of data.

% CAN'T - AT EOF

A file mark was read before the
specified number of records were
advanced over in a SKIP command.
The tape is moved backward one
record to leave it positioned at
the end of the file.

? CAN'T - DEVICE DOESN'T EXIST

The device specified in a CAMP
command is not present on the
OS/8 system.

? CAN'T - DEVICE IS READ-ONLY

The device specified in a CAMP
command is a read-only device,
e.g., PTR.

? CAN'T - DEVICE IS WRITE-ONLY

The device specified in a CAMP
command is a write-only device,
e.g., TTY.

? CAN'T FOR THIS DEVICE

The operation specified does not
make
sense
for
the
device
specified, e.g., REWIND LPT:.

? CAN'T I/O ERROR

An
input/output
error
has
occurred, and a brief explanation
will follow.

? NUMBER TOO BIG

The
"nnnn"
specified in
BACKSPACE or SKIP
command
greater than 4095.

? SYNTAX ERROR

An illegal character was typed in
a CAMP command or a command was
formatted
incorrectly.
The
command must be retyped.
10-5

a
is

CHAPTER 11
CROSS-REFERENCE PROGRAM (CREF)

CREF aids you in writing, debugging, and maintaining assembly language
programs by pinpointing all references to a particular symbol. CREF
operates on output from either the PALS, SABR, or RALF assembler.

11.1

CALLING AND USING CREF

To call CREF from the system device, type

.R CREF
in response to the Keyboard Monitor dot.
This loads the Command
Decoder, which replies by printing an asterisk in the left margin.
Enter one output file specification and one input file specification.
NOTE
The input to CREF must be the listing
pass output from either the PALS, SABR,
or RALF assembler. If this is not the
case, CREF will not operate properly.
RALF is not fully supported by CREF.
If you specify no output file, CREF assumes you are sending the output
to the line printer.
If you specify no input or output file
extension, the extension .LS is assumed.
If you specify no input
file, control returns to the Command Decoder until an input file is
specified. The CREF version number is printed at the end of the CREF
table in the form Vn, where n is the current version number.

11.1.1

CREF Options

The following options are available to you. The optlon and
specification are placed in the command string.

11-1

the

file

CROSS-REFERENCE PROGRAM (CREF)
Table ll-l
CREF Options
Option Code

I--~----

Meaning

-----~- -~----~-~-/P

Disable pass 1 listing output.
The output is
reenabled
when
$
(or END for SABRE)
is
encountered. Thus the $ (END) and symbol table
are
printed
if
you
use the /P option.
Inoperable for RALF output.

Disable pass 1 listing output and
table.
Inoperable for RALF output.

Interpret input as RALF code.

Interpret input as SABR code.
Signal CREF to
accept special SABR characters. If you use the
/Q option, the /X option is forced on.

Do not process literals. For programs with too
many symbols and literals for CREF, this option
may create enough space for CREF to operate.

Do not eliminate the file CREFLS.TM. If you do
not specify the /A option, and if CREF was
chained to from PAL8, the file CREFLS.TM is
eliminated.

Cross-reference mammoth files in two
major
passes.
Pass 1 processes the symbols from A
through LGnnnn; pass 2 processes the symbols
from
LHnnnn through Z and literals.
This
permits significantly
large
files
to
be
cross-referenced. If the /M option is used, the
file CREF.SV must be on the system device.

11.1.2

the

symbol

Examples of CREF Usage

Examples of calling and using CREF are given below.
Example 1:

.R CREF
iF-TEMP
The Command Decoder prints an * CREF assigns LPT:
as the output
device.
The input file is PTEMP, assumed to be on device SYS, with
the extension .LS. If you do not find the file SYS:PTEMP.LS, a search
for SYS:PTEMP is attempted.
Example 2:
~R CREF
!.SBRLS/R

Given to the Command Decoder, this command string causes output to be
sent to the line printer. The input is expected to be a SABR listing
file named SBRLS.LS or SBRLS from device SYS:.

11-2

CROSS-REFERENCE PROGRAM (CREF)
Example 3:

.R CREF

iDTA1:LIST~DTA3:PALIST/X

This command string causes output to be sent to DEC tape unit 1, as a
file named LIST.LS.
Input is expected to be a PALS listing file
called PALIST.LS or PALIST. No literals appear in the CREF output
table.
Example 4:

.R CREF
iDTA2:LIST<SYS:BIGLST
The source listing, symbol table, and cross-reference of symbols in
the file BIGLST or BIGLST.LS on SYS is in the file LIST.LS on DTA2.
To list the CREF output you may now run PIP.SV as follows:

.R PIP
.!LFT:-::DTA2:LIST.LS

11.2

PSEUDO-OP HANDLING

The PALS and SABR assemblers have certain pseudo-ops that cause CREF
to perform actions similar to those taken by the assembler whose
output is being processed. These pseudo-ops are described below:
Action Taken by CREF

PALS Pseudo-Op

11.3

EXPUNGE

CREF purges its current symbol table of all
permanent and user-defined symbols. If any
literals were in the symbol table, they are
not deleted.

FIXTAB

Causes all symbols (except literals)
to be
marked as permanent symbols. After a FIXTAB,
no references will be reported by CREF.

TEXT

Ignores characters between delimiters.

End-of-input signal.

INTERPRETING CREF OUTPUT

The output of CREF consists of two parts. On the first pass through
the input file CREF generates a sequentially numbered listing file.
The sequence numbers are decimal. The IP and IU options disable this
part of the output.
The cross-reference table appears after the listing.
This table
contains every user-defined symbol and literal, sorted alphabetically.
An underline (or back-arrow on most DEC terminals)
indicates each
literal, and it is followed by the field and address where the literal
ocCUrs. For each symbol and literal there appears a list of numbers
specifying the line in which each is referenced.

11-3

CROSS-REFERENCE PROGRAM (CREF)
If CREF finds too many references to fit into core at one time,'
multiple passes are required to process all symbols. The minimum
number of passes is two. The maximum number of passes depends on the
size of the input file and on the amount of core available. CREF
calculates the number of core fields available and uses all available
space for reference tables. If there is not enough core available,
three or more passes are required. For example, the current OS/8 SABR
assembler
(5518 source lines, 849 symbols)
requires four passes
through CREF on an 8K machine.
The following example illustrates a program that PAL8 has assembled
and CREF has listed. Form feeds on the terminal have been converted
to a series of carriage return/line feed combinations followed by a
dotted tear line. Notice the line in the CREF table where a t follows
the defined symbol. All literals and symbols defined by OPDEF or
SKPDF in SABR do not have a t following them.
/EXAMPLE PROGRAM
PAL8-V9B

EXAMPLE PROGRAM

/
/
/

3
4
{.

8
9

10
11
12
13
14
15
16
17
18
19
20
21
23
24
25
26
27
28
29
30
31
32
33

34
35
36

10200
10201
10202
10203
10377

0200
7300
1207
1777'
1177
1376
3777'
5610
0011
0400
0003
0407
0400
1207
1377
1177
1377
3207
6213
5776'
0000
0407
0200
0003
0002
0001
1377
1177
6203
5200
0003

10177

0002

00200
00201
00202
00203
00204
00205
00206
00207
00210
00376
00377
00400
00401
00402
00403
00404
00405
00406
00407
00576
00577
00177

03/05/74

PAGE

EXAMPLE PROGRAM
ILLUSTRATING DETAILS OF LISTING FORMAT
USING PALS AND CREF

*200
START,

CLA CLL
TAD A
TAD B
TAD [2
TAD (3
DCA LINK
JMP I ADDRP2
A,
0011
ADDRP2, P2

P2,

LIN",

TAD LIN"
TAD (3
TAD [2
TAD (3
DCA B
CDF CIF 10
J!'!P FLDl

/CURRENT PAGE SYMBOL
/OFF-PAGE SYMBOL, LIN" GENERATED
/FAGE ZERO LITERAL
/CURRENT PAGE LITERAL
/OFF-PAGE SYMBOL, LIN" GENERATED
/USER CREATED LIN"
/INDIRECT ADDRESS

/PAGE 2 START
/NOTE THAT THIS IS A NEW LITERAL
/NOTE THAT THIS IS SAME OLD LITE~AL
/SAME AS CURRENT PAGE LITERAL
/CURRENT PAGE SYMBOL
/CHANGE FIELDS
/OFF PAGE SYMBOL. LIN" GENERATED

!i-LIN"

FIELD
FLD1,

TAD (3
TAl. [2
CIF CDF 0
JMP START

/FIELD 1, DEFAULT TO PAGE 1 *200
/NEW LITERAL, BECAUSE IN PAGE 0 OF NEW FIELD
/CHANGE FIELDS AGAIN
/NO LIN" GENERATED, SAME FAGE, OTHER FI~Ln

11-4

CROSS-REFERENCE PROGRAM (CREF)
/

EXAMPLE PROGRAM

PAL8-V9B

03/05/74

PAGE 2

0207
ADDRP2 0210
B
0407
FLDl
0200
LINK
0407
P2
0400
START 0200
ERRORS DETECTED: 0
LINKS GENERATED: 3
A
ADDRP2
B
FLDl
LINK
P2
START
_00177
_00377
_00577
_10177
_10377

11
7
23
10
13
5*
8
9
18
31
30

12:1:
13:1:
21
30:1:
17
17:1:
33
19

25:1:
24:1:

11.4

RESTRICTIONS

CREF has the following restrictions:
can handle a maximum of 896
(decimal)
symbols in one
• CREF
major pass.
(In 8K, PAL8 is limited to 897 symbols while SABR
is limited to fewer than 800 symbols.) If CREF finds more than
896 symbols, it generates an error message.
•

If any symbol in the input file has more than
references, an error message appears.

2044

(decimal)

•

If more than 8192 (decimal) source lines are
numbers return to 4096, not O.

input,

sequence

•

If you use the /0 option in PAL8 (to generate a DDT-compatible
symbol table) and you put the output listing through CREF, no
symbol table listing will appear.

•

Use of semicolons - This is a restriction that, when not
observed, could cause errors in the CREF table.
You should
follow these suggestions when preparing source files in order
to insure a proper CREF listing.
Do not use semicolons on
lines with pseudo-ops.
In particular, do
not
use
a
combination such as the following:
£3000
TEST

:r.ERROR:r.

TAD [42

EXPR=O

11-5

CROSS-REFERENCE PROGRAM (CREF)
In this case, CREF does not process the page zero literal
properly.
It generates a literal derived from the expanded
TEXT message. No error message generates, but the literal
table entry is meaningless.
As a general rule, do not use
semicolons as line terminators inside conditional assembly
brackets
For example:

«».

EXOR=O
IFNZRO EXOR<CLA;TAD B; HLT \ERROR>
\THIS IS THE NEXT LINE PAST IFNZRO
The conditional code is not assembled; but because CREF does
not
realize
this,
it tries to process the bracketed
instructions. As a result of the semicolons, extra symbols
may be processed and some valid references missed. However,
if the code had been assembled CREF would operate properly.
There are two ways around this:
a.

Write straight-line code:

EXOR=O
IFNZRO EX OR <
CLA
TAD B
HLT ERROR
b.

Use XLIST
example:

around

conditional

the

preceding

XLIST turns off the listing, if the code does not
and turns it back on after the conditional code.

assemble,

IFZERO EXOR <XL 1ST>
IFNZRO EX OR <CLA;TAD B;
IFZERO EXOR <XLIST>

•

Formats - There are several output
generating a PAL8 listing file:

code,

HLT\ERROR>

formats

you

can

use

/T Form feeds converted to carriage return/line feeds.
/H No heading or form feeds generated.
/0 DDT-compatible symbol table is generated.
For best results with CREF, use none of these switches.
This
generates a heading and form feed in the output. CREF
automatically converts form feeds to carriage return/line
feeds if output is to the terminal.
•

11.5

PAL8-generated links are not recognized by CREF.
CREF
processes only literals specifically generated with ( and [.

CREF ERROR MESSAGES

CREF errors are nonrecoverable errors, and control returns to the
Keyboard Monitor through location 07605 (no core saved). Table 11-2
lists the error messages printed by CREF.

11-6

CROSS-REFERENCE PROGRAM (CREF)
Table 11-2
CREF Error Messages
Error Message

Meaning

SYM OVERFLOW

More than 896
(decimal)
symbols and
were encountered during a major pass.

ENTER FAILED

Entering
an
output
file
was
unsuccessful - possibly output was specified to
a read-only device.

OUT DEV FULL

The output device
only) .

CLOSE FAILED

CLOSE on output file failed.

INPUT ERROR

A read from the input device failed.

DEV LPT BAD

The default output device, LPT, is not available
on this system.

2045 REFS

More than 2044
symbol were made.

HANDLER FAIL

This is a fatal error on output;
it can occur
if either the system device or the selected
output device is WRITE-LOCKed.

11-7

full

(decimal)

(directory

references

literals

devices

one

CHAPTER 12
DIRECT

DIRECT is an OS/8 program that produces listings of OS/8 device
directories. The directories produced vary depending upon the options
you specify in the DIRECT command line.
The standard directory
listing consists of the following columns:
file name, file name
extension, length (decimal) in blocks written, and creation date.
DIRECT supports the wild card construction, accepting * in place of
the file name or extension, or? in place of a character. See the
FOTP chapter for a description of wild card construction.

12.1

CALLING AND USING DIRECT

To call DIRECT from the system device, type:
.R DIRECT
in response to the Keyboard Monitor dot. You may also call DIRECT via
the CCL command DIR. The Command Decoder prints an asterisk in the
left margin, indicating it is ready to accept a line of I/O files and
options.
You can enter one output specification, and one to five
input specifications in a DIRECT command line. You may terminate the
I/O command line with a carriage return (DIRECT retains control) or
with an ALTMODE (control returns to the Keyboard Monitor).
The output specification consists of a device upon which you can
produce the directory, a file name, and a file name extension. All
parts of the output specification are optional, as is the output
specification itself. You should specify a file name and extension if
you desire to save the directory for listing at a later time. If you
specify no output device, TTY is assumed. If you give a file name
without an extension, the extension .DI is assumed. The wild card ?
and * are not permitted in DIRECT output file names and extensions.
A DIRECT input specification consists of a device, an optional file
name, and an optional extension.
The wild cards * and? are
permitted in input specifications. If you specify an input device
with no file name or extension, *.* is assumed. DIRECT determines
which files have the form specified and prints a directory listing of
just those files.
NOTE
If you want to include the date in your
directory listing, you must enter it
first with the DATE command.

12-1

DIRECT
12.1.1

DIRECT Options

The following table lists the options you can use in a DIRECT I/O
specification line.
Examples of the use of these options are shown
after Table 12-1.
Table 12-1
.DIRECT Options
Option

Meaning

Incl~de the starting block numbers
each file in the directory.

List only files with the current date, i.e., the
date entered with the most recent DATE command.

Include empty
listing.

List a short form of the
file lengths and dates.

List additional information words in octal,
other than the first that is listed as the date.

List the standard form of
the
including
file
name, extension,
blocks, and creation date.
The /L
assumed if none is specified.

List only the empty spaces in the directory.

Use n columns in the directory listing.
This
option allows you to specify the number of
directory entries per line of output.
The Un"
must be in the range 0 to 7. The =n option is
useful when a wide column printer, e.g., 132
columns, is being used.

List only files
date.

List the remainder of the files after the first
one found.
This option causes DIRECT to find
the first file that matches the specifications
given and then list a directory that includes
the first matching file and all files that
follow it on the device. The /C and /0 options
are still
considered
when
listing
these
remaining files.
If /R and /V are used in the
same command, only the first file of the form
specified is listed.

Treat each input specification separately.
The
/U option creates a separate directory listing
for each input specification.

List files not of the form specified.

Print the version number of DIRECT.

file

with

spaces

other

(octal)

for

the

directory

directory,

omitting

than

directory,
length in
option is

the

current

' - - - _ . _ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ------

12-2

DIRECT
12.2

DIRECT EXAMPLES

The following are legal command strings to DIRECT and the resultant
DIRECT output. To facilitate understanding of the DIRECT options, the
same device (DTAO) is used for each of the examples. The current date
is 21-JAN-74.
When DIRECT has completed an operation, control returns to the Command
Decoder for additional input.
Example 1:
This example shows a directory of all the files on DTAO, listed in two
columns on the terminal (TTY) .

• R DIRECT
*DTAO:=2
21-JAN-74
MTP~A.PA

MTPALB.PA
WNTSTC.BA
WNPPPA.PA
WNP,ALB.PA
WNXX .BA

1 18-JAN-74
1 18-JAN-74
1 19-JAN-74
1 19-JAN-74
1 21-JAN-74
1 21-JAN-74

WNTSTA.BA
WNTSTB.BA
WtWALA.PA
WNTSTD.BA
MTPALC.PA
WNXY .BA

1 18-JAN-74
1 19-JAN-74
1 19-JAN-74
1 21-JAN-74
1 21-JAN-74
1 21-JAN-74

718 FREE BLOCKS
Example 2:
This example shows all files that have a file name beginning with
have any file extension, and do not have the current date.
directory is listed in two columns on TTY.

WN,
The

21-JAN-74
WNTSTA.BA
WNTSTC.BA
WNPPPA.PA

1 18-JAN-74
1 19-JAN-74
1 19-JAN-74

WNTSTB.BA
WNPALA.PA

1 19-JAN-74
1 19-JAN-74

718 FREE BLOCKS
Example 3:
This example shows files that have any file name, have a .BA
extension, and have the current date. TTY lists the directory in a
single column.

21-JAN-74
WNTSTD.BA
WNXX .BA
WNXY .BA

1 21-JAN-74
1 21~JAN-74
I""::fl.-'::' JAN - 7 4

718 FREE BLOCKS

12-3

DIRECT
Example 4:
This example demonstrates the use of the /U option to produce separate
directories for each input specification. The command specifies that
all files beginning with WN and having .BA extensions appear first,
and that all files beginning with WN and having .PA extensions appear
next. The short form of the directory is to be listed on the line
printer (LPT) in three columns .

.!LPT:<DTAO:WN1111.BA,WN1111.PA/F/U=3
21-JAN-74
WNTSTA.BA
WNTSTD.BA

WNTSTB.BA
WNXX .BA

WNTSTC.BA
WNXY .BA

718 FREE BLOCKS
21-JAN-74
WNPALA.PA

WNPPPA.PA

WNf'ALB.PA

718 FREE BLOCKS
Example 5:
This example demonstrates the use of the /V option to print files not
of the specified form and the use of the /0 option to exclude files
with the current date. TTY is to print in a single column all files
except those beginning with WN.

21-JAN-74
MTf'ALA.PA
I'1Tf'ALB.PA

1 18-JAN-74
1 18-JAN-74

718 FREE BLOCKS
Example 6:
This example demonstrates the use of the /R option to list part of the
directory.
DIRECT finds the first file that begins with WN and has a
.PA extension;
that file and all files that follow are listed.
TTY
lists the directory in two columns.

21-JAN-74
WNPALA.F'A

WN~I STD. BA

MTf'ALC.f'A
WNXY .BA

1 19-JAN-74
1 21-JAN-74
1 21-JAN-74
1 21-JAN-74

WNf'PPA.PA
WrH ALB.FA
WU:a.X • BA

718 FREE BLOCKS

12-4

l' 19-JAN-74
1 21-JAN-74
1 21-JAN-74

DIRECT
12.3

DIRECT ERROR MESSAGES

The following error
program.

messages

may

appear

when

running

the

DIRECT

Table 12-2
DIRECT Error Messages
Message

Meaning

BAD INPUT DIRECTORY

This message occurs when
the
input device has a bad directory,
e.g., the device is not an OS/8
device, or a DEC tape has not been
zeroed.

DEVICE DOES NOT HAVE A
DIRECTORY

The
input
device
is
a
non-directory device, e.g., PTR.
DIRECT can only read directories
from file structured devices.

EQUALS OPTION BAD

The =n option is not in the range
0-7.

ERROR CLOSING FILE

System error.

ERROR READING INPUT
DIRECTORY

An error occurred while reading
the directory.

ERROR WRITING FILE

An error occurred
the output file.

writing

An asterisk (*) was included in
the output file specification or
an illegal * was included in the
input file name.

ILLEGAL ?

A question mark (?) was included
in the output file specification.

NO ROOM FOR OUTPUT FILE

The output device does not
sufficient
space
for
directory to be written.

ILLEGAL

THERE IS NO HOPE - THERE IS NO
TTY HANDLER IN YOUR SYSTEM!

while

__________________________

have
the

A command was issued to print a
directory on the terminal when no
TTY handler is present on the
OS/8 system. Use BUILD to insert
a TTY handler in the system.

_ _- L _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

12-5

CHAPTER 13
DECTAPE COpy AND FORMAT PROGRAMS

The following programs enable you to format and copy DECtapes.

13.1

DTFRMT

This program records the required timing and mark tracks on a
mounted on the TCOI-TU55 unit or a TC08-TU56 DECtape unit.

DECtape

The program interacts with you via the terminal to obtain the
necessary data for each set of DECtapes to be formatted. As soon as
one set of tapes is formatted, the program is ready to format another
set.
Two full passes are required to completely format each DECtape, and up
to eight DEC tapes may be formatted at a time (assuming that you have
eight tape transports).
with
a
minimum
of
operator-program
communication, you can mount and format new tapes in the same fashion
upon completion of a cycle.

13.1.1

Loading Procedure

Load the program into core using the standard Binary Loader.

13.1.2

Using the Program

To start the program from the console, key 1000 into the SWITCH
REGISTER.
Depress LOAD ADDRESS and depress START. DTA? is printed
on the terminal.
Mount the DECtapes to be marked onto the tape transports, with just
enough tUrns of tape on the right-hand reel of each transport to
provide a grip. Make sure that no two tape units are set to the same
unit number.
Set the RDMK-WRTM-NORMAL switch located on the TCOI
maintenance control panel to the WRTM position. For each transport to
be used, set the WRITE ENABLED-WRITE LOCK switch to WRITE ENABLED, and
the REMOTE-OFF-LOCAL switch to REMOTE.
To run the program from the terminal, type:
.R DTFRMT
in response to the Keyboard Monitor dot.
program. The printout:

13-1

You now

converse

with

the

DECTAPE COpy AND FORMAT PROGRAMS
asks which DECtape units you are using. Type a unit number or series
of unit numbers, corresponding to the DECtape units with mounted
tapes. For instance, if you have mounted tapes on units 2, 5, 7, and
8, type 2 5 7 8 followed by a carriage return. Spaces are ignored, so
it makes no difference if you type spaces between the unit numbers.
Only one specification of a unit is significant, i.e., typing 2 2 5 7
7 5 8 2 8 has the same effect as typing 2 5 7 8.
Once you have specified the units you wish to use, the program types:

DIRECT?
Respond by typing:
MARK

0 r

MARK XXXX

If you type:

MARK
the program assumes 201(8)
words, 2702(8)
blocks
(standard PDP-8
format). Otherwise, XXXX is accepted as a decimal number of words per
block, and must be divisible by 3. Note that typing MARK 384 will
cause the program to generate a standard PDP-IO format DEC tape
(1102(8) blocks of 600(8) words, which is equivalent to 1102(8) blocks
of 200(8) words, where each word is 36 bits rather than 12 bits).
The program now types:
XXXX WORDS, YYYY BLOCKS OK?

(YES OR NO)

This serves as a final check for block count. XXX X and YYYY are octal
values representing the final outcome of a formula solved by the
program. They determine the number of blocks you may write on a
DECtape, given a specified number of words.
If you give a NO answer,
the program reverts to DIRECT?
If YES, the tape on the first unit
specified begins to move.
Once all of the tapes specified have been marked, the printout:

SET SWITCH TO NORMAL
appears. Return the RDMK-WRTM-NORMAL switch to NORMAL, and strike the
RETURN key on the terminal, starting the second pass. Note that
during the second pass with multiple DECtape units, as soon as one
tape stops and the next tape starts, the first tape is completed and
may be replaced with a fresh tape in preparation for recycling.
The program continues by itself
printout occurs. Typing:

until

completed.

Now

the

DIRECT?

SAME·::
repeats the entire process with the original constants.
The new
DECtapes must be mounted and ready to write timing and mark tracks
before you type SAME. Also, in response to DIRECT?, typing RDR causes
the printout of the unit numbers of the DECtapes and the last twelve
block numbers. RDF causes the printout of the unit numbers and the
first twelve block numbers.
RESTART returns the program to DTA?
Unit numbers are printed as NOOO, where N is the unit number (0 means
DECtape unit 8).
Once formatting begins, control C will cause the
program to restart at DTA?
If you wish to return to the monitor,
type control C.

13-2

DECTAPE COpy AND FORMAT PROGRAMS
Following are several examples of successful operation.
The program
prints the underlined portions. A carriage return should follow all
responses.
1.

Create a standard tape on unit 4.

l!I.A1 4
DIRECT? MARK
0201 WO"RDS, 2702 BLOCKS O"? YES OR ~
YES
SET SWITCH TO NORMAL
DIRECT'!'
2.

Create 16 standard PDP-IO format tapes - eight at a time,
units 1-8.

DTA'!' 12345678
DIRECT? MARK 384
0600 WORDS, 1102 BLOCKS OK'!' YES OR NO
YES
SET SWITCH TO NORMAL (TYPE <CR»
DIRECT? SAME
"SE rSwiTCH TO NORMAL (TYPE <CR»
DIRECT?

13.1.3

Error Messages

Errors typed to DTA?

and DIRECT?

revert back to DTA?

or DIRECT?

Error messages for response to MARK XXXX:
NOT DECIMAL

A character in XXXX is not 0-9.

NOT DIVISIBLE BY 3

XXXX cannot be divided evenly by 3.

TOO MANY WORDS

The number of words plus 15 exceeds 7777(8).

TOO MANY BLOCKS

The number of blocks
exceeds 7777 (8) .

generated

XXXX

Error messages for response to YES (after message - revert back DTA?):
SETUP?

Indicates an error in the DEC tape setup:
unit in WRITE-LOCK
nonselectable unit
switch not in WRTM position

Error messages for marking and verifying a tape:
XXXX SHOULD BE YYYY BLK ERROR PHASE X
XXXX SHOULD BE YYYY DATA ERROR PHASE X
END TAPE ERROR PHASE X
MARK TRACK ERROR PHASE X
PARITY ERROR PHASE X
SELECT ERROR PHASE X
TIMING ERROR PHASE X
LAST INT NOT END ZONE
Although an error message should cause doubt concerning the entire
process, you can restart by phases (except when in phase 0) by typing
RETRY<. Type RESTART< to return to DTA?

13-3

DECTAPE COPY AND FORMAT PROGRAMS
PHASE 0:
PHASE 1:
PHASE 2:
PHASE 3:

MARK TRACK WRITE
WRITING LAST REVERSE BLOCK NUMBER FORWARD
WRITING BLOCK NUMBERS AND DATA IN REVERSE
READING AND CHECKING BLOCK NUMBERS AND DATA

The error message LAST INT NOT END ZONE indicates an interrupt
occurred between the first or last block number and the end zone.
You can restart the entire program at 1000(8) any time.

13.1.4

Details of DTFRMT Operation and Storage

The program writes timing and mark tracks on a DECtape.
It then
inserts block numbers and parity correct information, checking the
results of all operations.
The number of block frames the program writes is
number of words per block. The formula
blocks per tape

function

the

212080
------ +2
NW+15

(where NW equals the number of words the program writes)
is used by
the program to compute the number of blocks. But thi's number 1S
adjusted by the program to provide the standard PDP-8 format of 129
(12-bit) words, 1744 blocks, and standard PDP-IO format of 128
(36-bit) words, 578 blocks.
Two full passes are required to mark and verify a tape.
Pass 1

Marks the ~ape forward,
inserts
parity correct date in reverse.

block

numbers

and

Pass 2

Reads and checks block numbers
reverse.

data

forward

and

During the forward direction of the first pass, the TCOI switches into
WRITE TIMING AND MARK TRACKS, CONTINUOUS MODE, FORWARD. The program
manipulates data it is writing by monitoring the word count register
and the DTF, (DECtape flag).
Initially, the program writes ten feet
of end-zone code, and abutting the end zone are about two standard
block lengths of interblock sync. To the TCOl, this interblock sync
acts as no operation, but guarantees that at turn-around time, block 0
is read f1rst (or 2701 if turning out of the forward end zone). Now
the program writes the remainder of the tape, creating block frames.
The formula above determines the number of such frames.
Upon
complet1on of the block framing, another extended interblock sync zone
is written, as well as ten feet of end zone.
Pass 1 forward is now complete (timing and mark tracks are written).
The program orders the tape to MOVE in reverse for three seconds, thus
moving it out of the end zone and onto the marked section.
The tape
once again moves forward, and the program writes the last REVERSE
BLOCK NUMBER until it senses the forward end zone. The tape now turns
out of the end zone in SEARCH, and the program waits for a block
interrupt (first reverse block number). When the DTF rises, the TCOI
switches
into
WRITE
ALL,
CONTINUOUS,
REVERSE.
Thus DTFRMT
synchronizes the system and writes all block numbers and data, until
the forward end zone is sensed.
This completes the marking and
blocking of the tape. Pass 2 in CONTINUOUS MODE checks the data and
block numbers to be certain they are correct. When you specify
multiple DECtape units, Pass 1 forward ends for each tape before Pass
1 reverse begins.
13-4

DECTAPE COpy AND FORMAT PROGRAMS
13.2

TDFRMT

The TD8-E DEC tape formatter program records the timing and mark tracks
on a DEC tape mounted on the TU56 DEC tape transport.
TDFRMT interacts with you via the terminal to obtain the necessary
data for each set of rECtapes the program will format. As soon as one
set of tapes is formatted, the program is ready to format another set.
The program requires three full passes to completely format each
DECtape, and it can format up to two DEC tapes at a time (units 0 and
1). Upon completion of a cycle, the program can mount and format new
tapes
in
the
same
way, with a minimum of operator-program
communication. Excluding tape setup time, the program formats one
tape in three minutes from start to finish.
Mount the DECtapes to be marked onto the tape transports with just
enough turns of tape on the right-hand reel of each transport to
provide a grip. Make sure that no two tape units are set to the same
unit number.
Set the switch on the TD8-E to WTM position. For each
transport you are using, set the WRITE ENABLED-WRITE-LOCK switch to
WRITE ENABLED, and the REMOTE-OFF-LOCAL switch to REMOTE.

13.2.1

Operating Procedures

Type:

...!oR TIIFRMT
in response to the Keyboard Monitor dot. ,You are now set to
with the program. The printout:

converse

UNIT?

asks which DEC tape units you are using. Type one or two unit numbers
corresponding to the DEC tape units with mounted tapes. For instance,
if you have mounted tapes on units 0 and 1, type 0 1.
Spaces are
ignored, so it makes no difference if you type spaces between the unit
numbers. Only one specification of a unit is significant,
i.e.,
typing 000111 has the same effect as typing 01.
Once you have specified the unit(s)
types:

you

wish

use,

the

program

FORMAT?
Respond by typing:
MARK or MARK XXX X
If you type:
MARK
the program assumes 201 words, 2702 blocks
(standard PDP-8 format) .
Otherwise the program accepts XXXX as a decimal numb~r of words per
block that must be divisible by 3. Note that typing MARK 384 will
cause the program to generate standard PDP-IO format DECtapes (1102 (8)
blocks of 600 words, which is equivalent to 1102(8)
blocks of 200
words, where each word is 36 bits rather than 12 bits).

13-5

DECTAPE COPY AND FORMAT PROGRAMS
The program now types:
XXXX WORDS, YYYY BLOCKS OK?

(YES OR NO)

This serves as a final check for block count. XXXX and YYYY are octal
values representing the final outcome of a formula solved by the
program. This determines the number of blocks the program can write
on DECtape, given a specified number of words. If you give a NO
answer, the program reverts to FORMAT?
If YES, the program types out
SET SWITCH TO WTM. Hit carriage return on the teletype and the tape
on the first unit specified begins to move,
if you have set the
switch.
Once the program has marked all of the specified tapes, the printout
SET SWITCH TO OFF appears. Reset the WTM switch to off, and strike
the return key on the terminal, starting the second pass.
Note that
during the second pass with multiple DECtape units, as soon as one
tape stops and the next tape starts, the first tape is completed. You
may replace it with a fresh tape in preparation for recycling.
The program continues by itself until it is completed.
the FORMAT printout occurs. Typing:

At this

point

SAME<
repeats the entire process with the original constants. Make sure you
have mounted the new DEC tapes before you type a carriage return in
response to the message SET SWITCH TO WTM. The tapes should be ready
to write timing and mark tracks. Also, in response to DIRECT?, typing
RDR causes the printout of the unit number of the DECtape and the last
22 block numbers. RDF< causes the printout of the unit number and the
first 22 block numbers. RESTART< returns the program to UNIT?
Unit
numbers are printed as OOON, where N is the unit number.
Following are several examples of successful operations. The program
prints the underlined portions. A carriage return should follow all
responses.
1.

Create a standard PDP-8 tape on unit 1.

UNIT'!' 1
FURMAT'!' MARK
O~Ol WORDS, 2702 BLOCKS, OK? (VES OR NO)
YE!..i

SET SWITCH TO WTM
SET SWITCH TO OFF
FORMAT'!'
2.

Create four standard PDP-IO format tapes, two at
units OIl.

UNIT? 01
FORMAT? MARK 384
0600 WORDS, 1102 BLOCKS OK? (VES OR N02
YFS

SET SWITCH TO WTM
SET SWITCHTO orF
~gRMAT! SAME
G~T SWITCH TO WTM
s~r SWITCH TO U.F
FORMAT?

13-6

time

DECTAPE COPY AND FORMAT PROGRAMS
13.2.2

Error Messages

Errors typed to UNIT and FORMAT revert back to UNIT?

or FORMAT?

Error messages for response to MARK XXXX:
NOT DECIMAL

A character in XXXX is not 0-9

NOT DIVISIBLE BY 3

XXXX cannot be divided evenly by 3

TOO MANY WORDS

The number of words plus 15 exceeds 7777(8)

TOO MANY BLOCKS

The number of
exceeds 7777

blocks

generated

XXXX

Error messages for response to SET SWITCH TO WTM:
SETUP?
Indicates an error in the DECtape setup.
One of
the units specified is in write-lock position, not
selected, or the write flip-flop is unable to be
set, or there may be a timing error.
(After
message revert back to UNIT.)
Switch not set to WTM or single-line flag failed to set.
Set switch to WTM.
This typeout says that either the switch on the
M868 modules is not set to the WTM position or the
timing generator for writing the mark and timing
tracks is not setting the single-line flag.
RECOVERY:
If you did not set the switch to WTM position, set
the
switch
and hit carriage return on the
teletype.
If the switch was set to WTM position and this
type out occurred, try again or examine the timing
generator circuit.
Error messages for marking and verifying a tape:
PC
PC
PC
PC
PC
PC

XXX X
XXX X
XXX X
XXX X
XXXX
XXX X

MARK TRACK ERROR PHASE Y
BLOCK NUMBER ERROR PHASE Y
DATA ERROR PHASE Y
CHECKSUM ERROR PHASE Y
TIMING ERROR PHASE Y
WRITE ERROR PHASE Y

XXXX equals the program counter at time of the failure.
number of the pass involved.

Y equals

the

Although an error message should cause doubt concerning the entire
process, you can restart the phase
(except in phase 0) by typing
RETRY<. Type RESTART< to return to UNIT?
PHASE 0:

WRITE TIMING AND MARK TRACK FORWARD

PHASE 1:

READS MARK TRACK REVERSE

PHASE 2:

WRITE DATA, FORWARD BLOCK AND REVERSE
FORWARD AND WRITES THE CHECKSUMS

13-7

BLOCK

NUMBERS

DECTAPE COPY AND FORMAT PROGRAMS
PHASE 3:

DISPLAYS BLOCK NUMBERS IN AC REVERSE

PHASE 4:

READS DATA, FORWARD BLOCK AND REVERSE
FORWARD AND CALCULATES THE CHECKSUM

PHASE 5:

READS REVERSE BLOCK NUMBERS IN REVERSE

BLOCK

NUMBERS

You can restart the entire program at 0200 any time.

13.2.3

Details of

TDFRMT Operation and Storage

The program writes timing and mark track in a forward direction on a
DEC tape with the WTM switch set. Then it reads the mark track in the
reverse direction with the switch set to off. The program checks all
of the mark track once it is in sync. When it finishes reading the
mark track reverse, it bounces off the end zone and starts writing
zeroes to the first block mark. The program is now in sync.
reverse
The program now continues writing forward block numbers,
checksum, data, checksum, and reverse block numbers for the rest of
the tape. When it sees the end zone,
it turns around.
It starts
displaying the reverse block number in the accumulator until it hits
the end zone again.
At this point the tape turns around and starts reading and comparing
all forward block numbers;
reverse checksum; all data, checksum, and
reverse block numbers that were written in Phase 2.
This comparison
is made on all blocks until the end zone is reached. The tape turns
around in the end zone and starts looking for reverse block numbers
and comparing them all the way down the tape to the end zone. The
formatting is now complete, the tape stops, and FORMAT is typed out
waiting for new directions.
The number of block frames to be written is a function of
of words per block.

the

number

The program uses the formula
BLOCKS PER TAPE

[(212080)/(NW+15)]+2

(where NW equals the number of words to be written)
to compute the
number of blocks, but it is adjusted by the program to provide the
standard PDP-8 format of 129(10) (12-bit) words, 1474(10) blocks, and
standard PDP-IO format of 128(10) (36-bit) words, 578(10) blocks.
The writing of the mark track is done through AC bits 0, 3, 6, and 9.
The following description shows how the program writes the mark track.
1.

Install the tape with enough turns to create a pull.
The
reverse end zone requires a sequence of three data words for
its pattern.
4044
0440
4404
In the mark track the words appear at 101101101101101
(5555(8».
The reverse end zone should cover about 10 feet
of tape. Write the above three words 4096(10) times.

Write the three words in point 3, or expand code 99 times.

13-8

DECTAPE COpy AND FORMAT PROGRAMS
3.

Expand code, three words of expand
follow each block.

code

should

immediately

0404
0404
0404
In the mark track the words appear as 010101010101 (2525(8».
4.

The forward block mark and reverse guard require three words.
0404
4004
4040
Which appear on the mark track as 010110011010 (2632(8».

The lock mark, reverse checksum, reverse
prefinal consist of six PDP-8 memory words.

final,

reverse

0040
0000
4000
0040
0000
4000
These
words
appear
on
the
001000001000001000001000 (10101010(8».
6.

mark

track

Mark track code for data is generated by
4440
0044
4000
These three words appear as 111000111000
(7070(8»
repeated 41(10) times for a 129-word block.

The prefinal, final, checksum, and reverse
six PDP-8 words.

lock

and

are

consist

track

4440
4444
4044
4440
4444
4044
These
words
appear
on
the
111011111011111011111011 (73737373(8».
8.

mark

The guard and reverse block mark consist of three words
4040
0440
0404
which appear as 101001100101 (5145(8».

Generate 2702(8) block patterns.
times.

13-9

Repeat 3 through 8

2702(8)

DECTAPE COPY AND FORMAT PROGRAMS
10.

100 expand codes (see 3).

11.

The end zone pattern consists of three words,
0400
4004
0040
which appears on the mark track as 010010010010
Repeat these three words 4096(10) times.

13.3

(2222(8».

DTCOPY

A dialog on the terminal controls the TCOl, TC08, and TU-55 Copy
Program.
Your responses to the questions are in the form of octal
numbers followed by a carriage return.
Separate the answers with
semicolons when more than one is required.
Alphabetic or other
illegal characters will cause an error message to be generated and the
question to be repeated. If you type too many digits for the expected
response, only the last ones typed will be used.
If the response was
to be either 0 or 1
(YES or NO), a non-zero final digit will be
assumed to be 1.
Before answering the dialog's questions, you should make s~re that all
the DECtapes involved are mounted on their respective drives and all
drives set to REMOTE. You may set the input drive to WRITE-LOCK or
WRITE ENABLE~ all output drives must be set to WRITE ENABLE. No two
drives may have the same unit number.
Type:
.R DTCOPY

in response to the Keyboard Monitor dot.

The program prints:

DECtape COpy V10A

For each set of copies, the dialog is as follows:
DECTAPE COPY V10A
FROM UNIT 0
TO UNIT :2
FIRST BLOCK TO COpy (OCTAL) 0
FINAL BLOCK TO COpy (OCTAL) 700
PDP-8 WORDS PER BLOCK 0201
VERIFY OUTPUT? (O=YES, 1=NO): 0

When all specified copies have been finished, the
and the dialog continues:

tapes

are

rewound

rHINE

DEC TAPE COpy V10A
n::OM UNIT

You may return to the monitor by typing CTRL/C at any time.
characters are not echo printed.)

13-10

(Control

DECTAPE COpy AND FORMAT PROGRAMS
13.3.1

Error Messages

DTCOPY produces the following error messages:
ILLEGAL RESPONSE
Your response to the dialog was not correct;
for exanple, an alphabetic character was
typed or carriage return was typed before an
octal number was given. The question will be
restated and any previous answer ignored.
Type nothing until the terminal has stopped
printing.
SELECT ERROR UNIT n
During attempted data transfer, unit n was
not found.
The program waits for you to
correct the cause of the error.
You should
check to see that:
1.
2.
3.
4.

when unit n is an output drive, it is
set to WRITE ENABLE.
unit n is set to REMOTE.
there is only one unit n.
all units
are
set
to
numbers
appropriate to their TD8E internal
wiring.

When you have corrected the cause of the
error, you may type CTRL/R to resume transfer
or type CTRL/S to restart the dialog.
TAPE ERROR BLOCK x UNIT n
During attempted transfer, a parity error or
timing error was detected, or too great a
block number was requested near block x on
the tape on unit n. The tapes are rewound
and the dialog is automatically restarted at
DONE, REPEAT (YES=l, NO=O).
VERIFY ERROR BLOCK x UNIT n
The data on the input tape does not match the
data that was written on block x of the
output tape on unit n. You may type CTRL/R
to ignore the error and continue with the
transfer, CTRL/T to try the last transfer
again and continue if the error does not
recur, or CTRL/S to restart the dialog.
ILLEGAL FORMAT UNIT n
Indicates one of two situations: Either the
number of words per block on unit n does not
agree with the number of words per block on
the input unit;
or, when the number of
blocks on the tape was calculated from the
block length of the input tape, the length
was found to be illegal.
The number of
blocks is only calculated if you request the
whole tape copy option. In either case, when
the error has been corrected, you may type
CTRL/R to check the formats of all tapes
again and continue, or CTRL/S to restart the
dialog.

13-11

DECTAPE COpy AND FORMAT PROGRAMS
13.4

TDCOPY

A dialog on the terminal controls TD83 Copy. Your responses to the
questions are ln the form of octal numbers followed by a carriage
return. Separate the answers with semicolons when more than one is
required.
Alphabetic or other illegal characters will cause an error
message to be generated and the question to be repeated. If you type
too many digits for the expected response, only the last ones typed
will be used. If the response was to be either 0 or 1 (YES or NO), a
non-zero final digit will be assumed to be 1.
Before answering the dialog's questions, make sure that all the
DEC tapes involved are mounted on their respective drives and all the
drives set to REMOTE. You may set the input drive to WRITE-LOCK or
WRITE ENABLE; all output drives must be set to WRITE ENABLE. No two
drives may have the same unit number.
Type:
.R TDCOPY
in response to the Keyboard Monitor dot.

The program prints:

TD8E COpy V4A
HIGHEST FIELD AVAILABLE:
Respond with the number of the highest field you want used for buffer
space.
This response may allow data to be preserved in any higher
field or may make full use of the available memory. This question is
asked only once:
immediately after you have loaded the program. To
change the response, you must execute the program again. If you want
to use 4K of memory, respond with a 0;
if 8K, respond with a 1, and
so forth.
For each set of copies, the dialog is as follows:
Comments
FROM UNIT: 0

You may specify one unit number.
You may specify up to seven unit
numbers, separated by semicolons.

FIRST INPUT BLOCK: 100

You may supply
block number.

any

legal

DEC tape

FIRST OUTPUT BLOCK: 200

You may supply
block number.

any

legal

DEC tape

NUMBER OF BLOCKS TO COPY: 50

You may supply
of blocks.

appropriate

number

VERIFY OUTPUT (YES=l, NO=O): 1
0201 12-BIT WORDS PER BLOCK

Determined by program from tape
input unit.

The program checks the block length of all the specified tapes.
If
any are found to be different from the input tape, the ILLEGAL FORMAT
UNIT n error message is generated.

13-12

DECTAPE COPY AND FORMAT PROGRAMS
When the program has finished all specified
tapes and the dialog continues:

copies,

rewinds

the

REPEAT (YES=l, NO=O):
If you want to copy more tapes with the same set of specifications,
you should place them on the drives before typing 1 to repeat the
previous operation. If you desire a different set of specifications,
type 0 to restart the dialog.
Occasionally a TDSE drive will not stop fast enough after the tapes
have rewound, causing the end of the tape to spin off the reel.
If
this should happen, you can set the drive to OFF and stop the reel by
hand.
This will not affect the validity of the copy.
If the dialog
does not continue properly after one or more tapes have spun off, you
can restart the program.
In response to any question in the dialog, type CTRL/S to restart the
dialog at REPEAT (YES=l, NO=O) or CTRL/C to exit the monitor. You may
also type either CTRL/S or CTRL/C during a small amount of further
motion.
If you type CTRL/S during the dialog, you answer NO to the
REPEAT question;
this option is mainly for cases where a complete set
of specifications is already available.
A unique component in the dialog allows you to copy the entire input
tape onto the output tape with a minimum of effort. This feature
eliminates the need to specify the starting block numbers and number
of blocks to copy.
In this case, the answer to FIRST INPUT BLOCK:
is
only a carriage return. The shortened dialog is as follows:

TDBE COp-r:
FROM UNIT: 0
TO UNITS: 1;2;3;4;5;6;7
FIRST INPUT BLOC~:
VERIFY OUTPUT (YFS=l, NO=O): 1
0"20112':"lff'TWORII'; PER BLOC"
The preceding sample dialog will cause the entire tape on unit 0 to be
copied onto the other seven tapes and verified.

13.4.1

Error Messages

TDCOPY produces the following error messages:
ILLEGAL RESPONSE
Your response
to
the
dialog
was
improper:
for example, you typed an
alphabetic character or carriage return
before a required octal number. The
questions will be restated and
any
previous answer ignored. Type nothing
until the terminal has stopped printing.

13-13

DEC TAPE COPY AND FORMAT PROGRAMS
SELECT ERROR UNIT n
During attempted data transfer, unit n
was not found.
The program waits for
you to correct the cause of the error.
Check to see that:
1.
2.
3.
4.

when unit n is an output drive,
it is set to WRITE ENABLE.
unit n is set to REMOTE.
there is only one unit n.
all units are set to numbers
appropriate
to
their
TD8E
internal wiring.

When you have corrected the cause of the
error, type CTRL/R to resume transfer or
CTRL/S to restart the dialog.
TAPE ERROR BLOCK x UNIT n
During attempted transfer, a
parity
error or timing error was detected, or
too great a block number was requested
near block x on the tape on unit n. The
tapes are rewound
and
the
dialog
automatically restarts at DONE, REPEAT
(YES=l, NO=O).
VERIFY ERROR BLOCK x UNIT n
The data on the input tape does not
match the data written on the block x of
the output tape on unit n.
Type CTRL/R to ignore the error and
continue with the transfer, CTRL/T to
try the last transfer again and continue
if the error does not recur, or CTRL/S
to restart the dialog.
ILLEGAL FORMAT UNIT n
Indicates one of two situations: Either
the number of words per block on unit n
does not agree with the number of words
per block on the input unit; or when
the program calculated the number of
blocks on the tape from the block length
of the input tape, the length was found
to be illegal. The number of blocks is
calculated only if you request the whole
tape copy option. In either case, when
the error has been corrected,
type
CTRL/R to check the formats of all tapes
again and continue, or CTRL/S to restart
the dialog.

13-14

DECTAPE COpy AND FORMAT PROGRAMS
13.4.2

Details of Operation

After the answers to the dialog have been stored,
procedure:
1.

use

the

following

The number of words per block is determined from the input
tape.
All output tapes are checked to see if they have the
same format as the input tape.
If you used the shortened
dialog option, the number of blocks on the tape is determined
using the formula:
# of blocks

= (636,160/(words per block + 17»

+ 2 (octal)

or
# of blocks = (2l2,080/(words per block + 15»

+ 2 (decimal)

The response to the VERIFY question is checked. The
loop is set up to verify or not, as was requested.

The loop that copies the input tape is entered,
same set of specifications for each output tape.
a.
b.

copying

using

the

The buffers are filled from the input tape.
All output tapes are written with the contents of the
buffers.
If verification was requested, a separate set of
buffers is filled from the output tape and the two
sets of buffers are compared.
If there are any
discrepancies a VERIFY ERROR has occurred.
If more blocks remain to be copied, the loop is
entered again.

d.
4.

When all the specified blocks have been
output tapes, all the tapes are rewound.

The REPEAT option is offered.

copied

onto

the

The number of fields to be used for buffer space is determined
immediately after loading. As soon as you have answered the question,
it is removed from the program.
If you verify the output tape, each available field,
including that
part of field
not occupied by the program, is divided in half. The
lower half is used as the input and output buffer; the upper half is
used for verification.
The output tape is read back into the upper
half and the two halves are compared. If they are not identical, a
VERIFY ERROR has occurred.

13-15

CHAPTER 14
DUMP

The DUMP handler is a new OS/8 2-page handler that obtains blocks of
binary data on file-structured devices and sends them to the LP08 line
printer to produce a listing. This listing is called a DUMP.
Format:
.COpy DUMP:<dev:filename.ex
or
.R PIP
*DUMP:<dev:filename.ex/I
Example:
.COPY DUMP:<SYS:FL2
After typing the command line, followed by a carriage return, type the
initial block number of the area in the specified file you want
dumped. This automatically dumps block number 0000 of the file.
In
addition, the DUMP routine skips to the block number specified and
dumps it and any block numbers greater than it.
Because the DUMP handler contains a routine that interacts with the
keyboard monitor, you can change the block number previously entered
by typing a new block number on the keyboard. When you type a new
block number, the current block number is dumped before the new block
number takes effect.
If you enter a carriage return after the command line and do not
supply a block number, the DUMP handler starts at block number 0000 of
the file and dumps all the remaining block numbers in the specified
file.
Each block of data (2 memory pages) sent to the LP08 line printer
results in a printed page of data followed by a form feed.
If an
uneven number of pages is sent to the line printer during the DUMP
operation, the odd numbered page printed on the line printer will show
only half a block (one memory page) of data.
If you type an illegal character (excluding 0-7, carriage return, and
CTRL/C) while entering the block number, a question mark (?) echoes on
the terminal. Any digits typed before it are ignored, and you can
type in a new block number.
If you type CTRL/C while the DUMP handler
is running, control returns to the keyboard monitor.
In addition to the CCL format shown using the COpy command, there is a
-D option. When specified, this option forces the output device to be
DUMP:. You can use this option with any CCL command.

14-1

DUMP
14.1

FORM FEEDS

A form feed on the LP08 line printer occurs before block 0 data is
sent to the handler and after the handler is called to do a close
(page count of 0).

14.2

ADDING THE DUMP HANDLER TO YOUR SYSTEM

You can add the DUMP handler to your system through the BUILD program.
Its group name, as well as its entry point name, is DUMP: and the
current version of the handler is A. This handler does not directly
interact with the keyboard monitor, but rather contains a routine that
performs that function.
It is a 2-page handler and it has no
coresident handler.
The keyboard monitor runs completely overlapped
with the LP08 handler.

14.3

FORMAT OF THE DUMP

The top left of every printed page in the DUMP listing has a 4-digit
octal number.
This number is the relative file block number of the
data that is printed on that page. The first column of 4-digit octal
numbers represents line numbers. Each line number is followed by a
slash (I), which distinguishes the line number from the remalnlng
eight columns. The remaining eight columns represent the actual data
words located within a specific block in a file.
The next column
containing 16 characters is a representation of the eight data words
on that line. Two 6-bit characters are packed in one word
(that is,
two ASCII characters represent each data word) .
The last column containing 12 characters is another representation of
the eight data words on that line. Three 8-bit characters are packed
in two words:
that is, every two data words are represented by three
ASCII characters.
Some of the spaces in this column could represent
non-printable characters. Any character that is not on the line
printer can be referred to as a non-printable character.
The following listing is an example of a single printed
DUMP listing.

14-2

page

from

DUMP

0004

7733
0001/ 1501
0002/ 7767
0003/ 0502
0004/ 0215
0005/ 7777
0006/ 0000
0007/ 2001
0010/ 7762
001I/ 0000
0012/ 1601
0013/ 7777
0014/ 0000
0015/ 1501
0016/ 7777
0017/ 0000
0020/ 2001
0021/ 7776
0022/ 1520
0023/ 2320
0024/ 7762
0025/ 1520
0026/ 2001
0027/ 7776
0030/ 0363
0031/ 1320
0032/ 7744
0033/ 5654
0034/ 0300
0035/ 1501
0036/ 7666
0037/ 4000
0000/

2213
6264
1420
1404
6314
0662
0000

6304
0663
0000

6314
0362
0000

6314
2263
0000

6324
2266
6400

6334
0425
6500
6324
1501
6500
6354
0000
0000

6300
6264
1234
7235

1720 7777 1322
7653 1322 0506 6300
2326 0000 0216 8304
2326 6354 7737 0425
7776 0681 0000 0000
0000 0000 1501 6314
1501 6314 7777 0425
7761 2425 1520 6200
0000 0000 1501 6314
1521 6314 7777 0363
7777 0361 0000 0000
0000 0000 1501 6314
1501 6314 7777 2262
7777 2261 0000 0000
0000 0000 1501 6314
1501 6314 7777 0425
7762 0425 1520 6300
8070 1623 0216 6324
0216 6324 7776 0425
7774 0425 1520 6500
1520 6600 2001 6354
0216 6354 7776 0425
7762 0425 1520 6500
0363 6500 0216 6354
2001 6354 7400 0617
7775 1501 0363 6500
7252 1501 0363 6500
7271 6300 0001 6264
0216 6264 7767 3000
7777 7252 7277 7304
4000 7235 7241 2422
7241 2422 4000 7235
0000

0506
2202
7777
1520
1501
7777
1520
2001
7777
0000

1501
7777

0000

1501
7777

1520
0216
7777
1520
2001
7761
1520
0216
7735
1700
1520
1423
7653
0000

7440
7666
7241

14-3

p R F@
6300 ?[KK@@QP'1?KREF3@ [
6264 MA24>+KREF3@R824 A4<+R F@ 4L
V@D
2213 ?7LPSV@@BN3D??RK
P0
B VL
0000 EBLDSV3,? DUMP@@
I
AL<
6314 BN3L?>FI~3L L
2
AL< 4
0664 ??F2@@@@MA3L??F4
AL< P 0
0000 @.@@!@MA3L??DUMP@@
P < LL
DL
6314 PA3D?IDUMP2@PA3L
AL< 5
3
0665 ?2F3@@:@@MA3LTIF5
AL<
0000 @@@@MA3L??C3@@@@
AL<
6314 MA3L ??C I@@@@MA3L AL<
AL<
0364 ??C2@@@@MA3L??C4
AL<2
0000 @@@@MA3LTIR2@@!@@
AL<
6314 MA3L??R 1@CtL@.'@MA3L AL< I
3
AL<
0365 ??K3@@@@MA3L ??C5
P@<
AL<
6300 ~MA3L??DUMP3@
P@< T
TL
6324 PA3T?2DUMP3@BN3T
0425 ?> RF08NSBN3T??DU
8 CT
P0
0000 MP4@BN3P>DUMP@@ P = T
P@= \L
6334 SV3\?<DUMP5@PA3\
V\L
0425 ?2DUMP6@PA3,?lDU
P= L
P =
6400 MP6@BN3,?>DUMP4@ P =
P@= \
6334 PA3T?2DUMP5@BN3\
TL
1501 ?>MAC35@BN3,?]MA
A @
]A
@O
@ L
0000 C35@PA3,<@FOO@@@
6354 MP3,1=MAC35@MP3,
P < A @ P<
*A @ <
6354 ?$@@ *MAC35@LS3,
1322 2,@@ 93@PA24>+KR
, @9@ 4L+R
0000 EF3@BN24?7X@@@@@ F@ 4
A4< * ?D @
5300 MA24?? * ?;D< +@
6
6
1234 >61\@.) '!TR>61\
2422 @:) 'TR@'):!TR

CHAPTER 15
EPIC

EPIC, the Edit, Punch and Compare utility program for
the following functions:
•

Read and punch tape files and patches

•

Edit arbitrary files

•

Compare files in any format

These functions are discussed in the next few pages.
assumes you have an elementary knowledge of OS/8.

15.1

OS/8,

performs

The

discussion

LOADING EPIC

To load the EPIC program, type:
.R EPIC
in response to the Keyboard Monitor dot. Specify the EPIC function
you want by including one of the following numeric options in the file
command line:
.R EPIC
*TRANS.AS(/O$

o paper tape
1 edit
2 compare
punch the file TRANS stored on
SYS .

• R EPIC
fetch FILEA
editing

*DTA1:FILEA.SV(/1$

from

DTAI

for

compare file ABC on the disk
with file XYZ on DTAI and
output
block
numbers
and
locations of each non-match on
the Teletype.

.R EPIC
*DS~:ABC.SV<DTA1:XYZ.SV/2$

After you have included one of these numeric options in a command, you
do not have to specify it again in subsequent sequential commands
requiring the same option. Specifying the number puts EPIC in a mode
in which it remains until another number is specified. Initially,
EPIC is set to option o. You use the character ALTMODE, which appears
as a $ on the terminal, to end a command that includes a numeric
option.

15-1

EPIC
15.2

RESTART PROCEDURE

You can restart EPIC at location 0200. Default options remain active.
The default options are discussed later in this section.

15.3

PAPER TAPE FACILITY

EPIC's paper tape option (/0) punches OS/8 files and file patches onto
paper tape, and creates OS/8 files from paper tapes. Whole files or
patches (blocks) of files can be read or punched. Parity checks are
punched to ensure accurate reads. Because of the paper tape format
used, tapes must be both punched and read by EPIC. A file punched by
PIP, for example, is not acceptable to EPIC.

15.4

COMMAND FORMAT

To request the paper tape facility, specify option o.
Your response
to the command decoder's * determines whether a tape is to be punched
or read. In both cases, no input files or devices are specified.
To
punch a tape, specify the file name;
to read a tape, you need not
enter a file name (that information is encoded on the paper tape).
The command line specifying the mode of EPIC is terminated by ALTMODE.
To punch a tape, respond with:
*dev:name</O/other options$
To read a tape, respond with:
*dev:</O/other options$
If a file name is specified, EPIC looks up the name on the specified
device and punches the file (including the file name) onto paper tape.
If no file name is specified, EPIC reads in a paper tape and enters it
onto the output device under the name it read in from the tape.
The other options for handling paper tape are:
/L

Use low speed paper tape reader or punch

Do not punch end of tape upon completion

Punch or read a patch (instead of the whole file)

Set relative block to 0

/=n

Punch relative block n

Clear default name

You can combine these options to achieve the desired results:

If the /L option is not specified, EPIC assumes a
high-speed paper tape device. Thus, SYS:</O means
read a tape from the high-speed reader to device
SYS,
but
SYS:</O/L means read it from the
low-speed device.

15-2

EPIC
/E

The /E option can be used to punch a series of
patches to a file for all patches except the last
one. With the /E option the end of tape mark is
not punched.
The end of tape must have the "end
of tape" punch, a 377 punch and a length of
leader/trailer tape.

The /P option is required to indicate the tape to
be read or punched is a patch, not an entire file.
Generally, the command required to read in a patch
is
simply
dev:</P.
File
name
and block
specification are already punched on the tape.
Option /Z or =n must be used with the /P option to
indicate punching block 0 or some other block
The patch is
(relative block n), respectively.
read on top of an existing file on the specified
output device, that is, modifying an old file, not
creating a new one.

15.5

The /Y option is used to clear the default file
name when switching from punching to reading paper
tape and when reading more than one paper tape.

DEFAULT OPTIONS

Throughout EPIC, if you do not specify options, files, or devices, the
program defaults to the last such item specified. There is an initial
default device: SYS is assumed if no output device is specified.
No
options are assumed initially, except for relative block O. Note that
device and file name options carry between EPIC modes 0, 1 and 2.
Specifying an option (that is, L, P, E, Z, etc.) in a command string
disables default to any options from the previous command
(except 0,
1, 2).
For example, to punch blocks 0, 1 and 30 of the file TRANS on the SYS
device and read them back onto that file on DTA3, the commands are:
Punch block 0 of TRANS on high-speed punch
with no end of tape punch. Because EPIC
defaults to the paper-tape option initially,
o is not required in this case.
Punch block 1 of file
TRANS
with
no
end-of-tape character on high-speed device .

• R EPIC
*TRANS ,:lP /E/Z$

...!.=1
*=30/P
*DTA3: . /Y

Punch block
30
of
the file TRANS
high-speed
punch. Punch end of tape
disables E).

on
(P

Read the tape from the high speed device and
put out to file whose name is encoded in the
patch on device DTA3 until end of tape is
reached.
File name and relative block are
punched on the tape so this information is
not necessary.
Y clears the default name
(TRANS) .

15-3

EPIC
15.6

ERROR CONDITIONS

If an error occurs while reading a block of paper tape, EPIC outputs
an error message (the e~ror messages are listed at the end of this
section), and halts. You should reposition the paper tape to the
leader/trailer just in front of the block just read before continuing
(refer to Section 15.12, Paper Tape Format). Three consecutive read
errors terminate the command.
When EPIC is reading in a non-patch
file it checks the initial block read of every tape and block that is
reread because of error. This is done to determine if the read was
accurate up to name and block number. If the wrong block number or
file name is read, EPIC outputs an appropriate message indicating the
type of error. It then halts with AC=7777 to allow you to reposition
the tape over the correct block or to enter the correct tape before
continuing.

15.7

LOW SPEED I/O

The execution of EPIC differs for low-speed I/O.
Before starting a
low-speed punch, EPIC halts with 7777 in the AC to allow you to turn
on the low-speed punch and then press the CONT key on the computer
console. Upon completion of a punch command, EPIC halts with the AC=O
to allow you to turn off the punch. When you press the CONT key, EPIC
recalls the command decoder. For low-speed input EPIC halts only upon
completion of the read.
If a file or a series of files to be punched exceeds 32 blocks, EPIC
segments it by punching end of tape after 32 blocks. This end-of-tape
punch, done automatically and independently of the E option, keeps
tapes short enough to fit into a paper tape tray. Upon physical end
of tape, EPIC halts with the AC=O if the low-speed punch 1S being
used.
This is done to allow you to turn off the punch before
cont1nuing. As soon as the punch is turned off, EPIC outputs the
message END OF TAPE ENTER NEXT and then halts with the AC=7777 to
allow both high- and low-speed users to remove the paper tape.
Note
that low-speed users get both halts, but high-speed users get only the
7777 halt. In general, a halt with AC=O means to turn paper tape
device off, and a halt with AC=7777 means to turn device on. All
halts are terminated by depressing the console CONTinue key. If EPIC
encounters end of tape while reading a non-patch file, it outputs the
message END OF TAPE ENTER NEXT and halts with AC=7777. This indicates
that the file is segmented across a number of tapes and that you
should enter the next tape.

15.8

DEVICE CODES

Most of the execution time is spent waiting for paper tape devices.
During I/O wait, EPIC holds the device code and version number in the
AC. The device code is in bits 3-5 and the version number is in bits
6-11. The codes are as follows:
1 high-speed reader
2 high-speed punch
3 low-speed reader (console TTY)
4 low-speed punch (console TTY)
If you forget to turn on the high-speed reader, EPIC hangs with lxx in
the AC.
You can always restart EPIC at 0200. The OS/8 CTRL/C is
normally in effect; the exceptions are when EPIC is waiting for a
paper tape device or when input is from the low-speed reader.

15-4

EPIC
NOTE
When input is from the low-speed reader,
EPIC forces the output device to be SYS
because it is the only OS/8 I/O handler
that does not check for CTRL/C.
Thus, if you were to enter the command:

.DTA2:</L
EPIC would force it to be

.SYS:</L

15.9

EDITING CAPABILITY

Option 1 of EPIC is the file editing and searching facility.
With
this feature, you can add patches directly to the file by specifying
relative blocks and locations in the file.

15.9.1

Initial Command Format

The general format of a command for the editing option is:
.R EPIC
*DEV: NAME</OF'TIONS/l $

The /1$ specifies edit mode for EPIC.
As with the paper tape option, default conditions apply. If you have
not specified a device and/or file name, the last one mentioned is
used. When editing, the only option available in the initial command
is:
/Y

Clear default name (if one exists)

Editing is performed one block at a time. The relative block you are
currently processing is known as the current block; the location you
are currently processing is known as the current location
(0-377).
Relative block 0 is the first block of the file if a file name is
specified or block 0 of the device if no file name is specified.

15.9.2

Editing Commands

After the initial (file specification) command, you use a series of
keyboard commands to perform the editing. The general format of an
editing command is:
x

or
x,nl,n2
where x is a command letter and nl,n2 are octal numeric arguments.
If
you use a numeric argument, the letter is followed by a comma. You

15-5

EPIC
can type up to 32~10 characters on a line. Default conditions apply
to these commands as well. If carriage return is the only character
typed as an editing command, the last command specified is executed.
The commands are listed and explained in Table 15-1.
Table 15-1
EPIC Commands
Meaning

Command
E

Exit to command decoder;
write out
block of file if it has been modified.

current

R, n

Read relative block n (octal) of file and set
current location to O.
Do not write current
block. If n is not specified, the current block
is read. If the relative block is out of range,
a? is printed. There are 1341 blocks per OS/8
tape and 6260 per RK8 disk platter.

Write the current block of file if it has been
modified and read in the next sequential block
of the file.
If the current block -is the last
block of the file, a ?
is printed and the
current location is unmodified.

S, nl, n2

Search the current block for the value nl with
the mask n2.
If either nl or n2 or both are
omitted, the last value specified is used.
The
initial mask is 7777. Masking is performed in a
logical AND fashion.
If the S command is
terminated by the RETURN key, the search is for
the current block only. If the S command is
terminated by the LINE FEED key, the search
continues to the end of the file.
If the search
fails
(either in the block or to the end of the
file), EPIC prints a ?
If the search is
successful, EPIC prints:
ml m2
m3 /
where ml is the relative block, m2 is the
relative location within the block, and m3 is
the contents of the location (ml is omitted if a
previous match was found in the same block). To
change the contents, type the new contents (in
octal) after the slash. To continue the search,
type the LINE FEED key;
to terminate the
search, type the RETURN key.
(If the contents
are not to be changed, type one
of
the
terminators.)
(continued on next page)

15-6

EPIC
Table 15-1
(Cont.)
EPIC Commands
Command
0, n

Meaning
Open location n of the current block. If n is
not specified, the last opened location is the
default. If there is no default, location 0 is
opened. EPIC responds with
ml /
which is the contents of location n.
This
location
may
be
modified
as in search.
Terminating with the LINE FEED key closes the
current location and opens the next.
If the
current location is the last one in the block,
location 0 of the next block is opened, and the
current block is written out as if it had been
modified.
Print current status, as:

ml (F or B) m2 m3 m4
where ml is the current block, m2 is the current
location, m3 is the search word, and m4 is the
mask word. If you type F, the file has been
modified
since option 1 was requested:
B
indicates the current block has been modified.
Once a modified block has been written to the
file, the F is the only code output.
~

_ _ _ _ _ _ _ _ _ _ _ _ _ _L -_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __ _

Thus a reasonable sequence is:
• R EPIC
*nSKtISOMER<:/1$
R,2
S,3126,7770

0004 0110
3124 /3121
,,7777
000-1 0132
3126 / 3127
C

0004 B 0132 3126 7777

w
...1
R,2
0, 10

1367 /1364
3324 •
E

Call EPIC .
Edit file ISOMER on DSK.
Read block 2.
Search for a 312x in that block.
Not there.
Search for it throughout the file.
Found at block 4, location 110.
Change contents to 3121.
Search for 31xx throughout the rest
of the block (locations 110-377).
Found at location 132 of block 4.
Contains 3126. Change to 3127.
Check status.
At location 132 of block 4 which
has been mOdified;
the current
search word is 3126 and mask is
7777.
Write block 4.
Block 4 written but file is only
four blocks long, no block 5 to
read.
Read block 2.
Open location 10.
Contains 1367. Change to 1364.
Check
next
location.
No
modifications.
Exit editing option.

*
15-7

EPIC
15.10

COMPARE CAPABILITY

A third feature of EPIC is file compare (/2). Because EPIC uses an
absolute compare technique, there are no limitations in the data
format or the length of the file. The files you are comparing must
reside on the system device.
COMMAND FORMAT
Option 2 of EPIC requires only one command, specified as follows:
SYS:filel<SYS:file2/options/2$
Specify the first file to be compared to the left of
bracket, the second file to the right. The options are:
/A

Abort when the first non-match is found.

List physical block number for each file where
exists.

If you specify no options, the block numbers
non-match are listed on the terminal.

and

the

non-match

locations

For example, to compare files PYTHGI and PYTHG2 and find
locations, the sequence is as follows:

angle

all

each

unequal

..!.SYS: PYTHG 1 <SYS: PYTHG21'2$
SYS:0174 SYS:0631
0152 7450 3421
0153 5741 2021
0154 3421 3022
~

To compare them and list unequal blocks, the command is:
~SYS:PYTHG1SYS:PYTHG2/B/2$

If this block match followed the preceding locations match command,
sufficient command and its results are:

~/B

SYS;0174

SYS:0631

To abort after the first non-match, use the sequence:
.:!/A

SYS:0174

15.11

SYS:0631

ERROR MESSAGES

EPIC can print certain
(option 0) operations.

error messages when
(See Table 15-2.)

15-8

performing

paper

tape

EPIC
Table 15-2
EPIC Error Messages
Explanation

Message

~--------------------4--------------------.-------------------

BAD =BLK

---------

When EPIC is punching a patch, it checks
the block specified by "=n" to see if it is
within range.
If the block is out of
range, EPIC outputs this error message and
returns to the command
decoder.
For
example, if a file JOE were two blocks long
and you requested:
SYS:JOE</P=3
the error message would be printed.

END OF TAPE

EPIC was expecting a block of tape and
found end of tape instead. EPIC halts with
AC=7777 to allow you to reposition the
tape.
When you depress the CONT key, EPIC
attempts to read the block.

END OF TAPE
ENTER NEXT

When EPIC is reading a file that is
segmented across a number of paper tapes
and encounters the end of a segment, it
outputs this message and halts with AC=7777
to allow you to enter the next segment of
paper tape. Press the CONT key to continue
reading.

I/O ERROR

If EPIC encounters an error while reading
or writing a mass storage device, or if a
paper tape read fails three consecutive
times, EPIC outputs this error message,
deletes the output file if one exists, and
returns to the command decoder.

L/T ERROR

EPIC was expecting leader trailer and found
non-leader trailer while attempting to read
a block. The program prints this error
message and halts with AC=7777 to allow you
to reposition the tape, then press the CONT
key.

NEED:namel
FOUND name2

EPIC read a block of tape for the file
NAME2 when it was expecting a block of the
file NAMEI.
This error typically occurs
when you come to the end of a segment for
NAMEI and enter some segment of NAME2
instead of the next segment for NAMEI.
EPIC halts with AC=7777 to allow you to
enter the correct paper tape.

NEED: nlFOUND: n2

EPIC read block n2 of the file when it was
expecting block nl of the file.
EPIC halts
with AC=7777 to allow you to reposition the
paper tape.
This error typically occurs
when you reposition the tape to the wrong
block after a read error.
(continued on next page)

15-9

EPIC
Table 15-2
(Cont.)
EPIC Error Messages
Explanation

Message
PARITY ERROR

EPIC failed to read a block correctly, for
example, the reader dropped some bits.
EPIC halts with AC=7777 to allow you to
reposition the tape so that it can try the
read again.

PTR:NAME IS TOO
BIG FOR dev:

The paper tape file NAME will not fit on
the specified output device DEV:.
EPIC
aborts the command and returns to the
command decoder. EPIC makes the check for
size before writing on the output device.

USR n dev:name

The USR
encountered
an
error
while
attempting to perform a fetch, lookup,
enter, or close on the file NAME on device
DEV. n=l is a fetch, n=2 is lookup, n=3 is
enter, n=4 is close.
EPIC aborts the
command and returns to the command decoder.
For example, if you request EPIC to punch a
file on SYS that does not exist:

SYS:NILL·{
EPIC outputs the message

USR 0002 SYS:NILL
indicating that it could not find the
NILL on the device SYS.

15.12

file

PAPER TAPE FORMAT

Paper tapes punched by EPIC have the following format:
2
FEET

DATA

INCHES
BLOCK

LIT

BLOCK
LIT

LSTART OF
PUNCH

INCHES

......

LIT

2
FEET
LIT

BLOCK~

END OF tAPE
PUNCH

Leader trailer is any string of 0 or 200 punches; usually it is just
200 punches;
leader trailer is terminated by a 201 punch, which
indicates the start of a data block. The first punch after the last
data block is 377, which is end of tape. Each data block has the
following format:

---.------r---r-------~-r-----:-r:lI

~H_:_:_:_:_R~.

::::

_~ ~~:1+

...........

---------

15-10

DATA
P CRC
BYTE

CRC

EPIC
Each byte is 12 punches (96 bits)
and corresponds to eight 12-bit
words; each byte is followed by an even-odd parity punch of the eight
words in the byte. Each block is terminated by two CRC punches of
longitudinal parity.
The header byte contains information about the file for example, file
name and relative block number. The data bytes constitute the actual
data of the block; each 256-word block has 32 data bytes.

15.13

LOADING EPIC FROM PAPER TAPE

If you use receive EPIC on paper-tape, use the following procedure
load the tape and save it on a mass storage device.

.R.ABSLIIR

*PTRa~

.SA SYS EPIC 0-7577;0200=0

15.14

Use ABSLDR
after
Read from reader;
is
output,
type any key to start
reader
Save on mass storage with starting
address of 200

EPIC ASSEMBLY INSTRUCTIONS

Use the PAL8 (version 9) assembler to assemble EPIC as follows:

..,!.R PAL8
.!.IIEV:EPIC.BN,IIEV:EPIC.LS<IIEV:EPIC.PA
To create the save file, use ABSLDR:

..,!.R ABSLIIR
*IIEV:EPIC.BN$
~SA IIEV EPIC 0-7577;0200=0

Call ABSLDR •
Load EPIC.BN on device specified.
Save EPIC on device specified.
0-7577 = area in core used during
execution. 0200 = restart address.

15-11

CHAPTER 16
FILE-ORIENTED TRANSFER PROGRAM (FOTP)

FOTP transfers files from one device to another, deletes files from a
device, and renames files.
FOTP is significantly faster than PIP and
performs certain functions not available with PIP. For example, FOTP
can transfer files longer than 256 blocks and can perform multiple
file transfers and deletions without requiring multiple accesses of
the directory.
FOTP copies files in the image mode, that is, it copies the file word
for word, character for character, without making any changes in the
file.
(This corresponds to the /1 option in PIP.) Thus you may use
FOTP to copy core image and binary files as well as ASCII files,
without specifying options to identify the type of file.

16.1

CALLING FOTP

To call FOTP from the system device, type:

.R FOTP
in response to the Keyboard Monitor dot.
(You can also call FOTP
indirectly with several CCL commands. See the CCL section of Chapter
1.) The Command Decoder prints an asterisk in the left margin and
waits to receive a line of I/O files and options. FOTP accepts one
output specification and up to five input specifications.
The I/O
specification line may be terminated with a carriage return (FOTP
retains control) or with an ALTMODE (control returns to the Keyboard
Monitor) .

16.1.1

Input Specifications

FOTP input specifications consist of a device, a file name, and a file
name extension. Input specifications are optional but must be present
if you do not include an output specification.
Within the input specification, FOTP allows you to use a wild card
construction.
This means that the file name or the extension may be
replaced totally with an asterisk or partially with a question mark to
designate certain file names or extensions. You can use the asterisk
as a wild field to designate the entire file name or extension.
For
example:
TESTl.*

All files with the name TESTI and any extension.

*.BN

All files with a BN extension and any file name.

*.*

All files.
16-1

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
The question mark serves as a wild character to designate part of the
file name or extension. Use a question mark for each character you
want to match;
for example, PR??
matches on four characters or
fewer. Some examples follow.
TEST2.B?

All files with the
beginning with B.

name

TEST2

TES??PA

All files with a PA extension and any file name
five characters beginning with TES.

????

All files with file names of two characters or less.

You can specify the asterisk and the question
same command line.
???*

and

mark

any

extension

together

the

All files with file names of three characters or less.

The following are examples of legal FOTP input specifications:
DSK:
SYS:A
LTA3:TESTIA
DTA7:A.BN
FILE
FILE3.DA

4
NAME?TX,NAM??BN
N?ME.
??????D?

*.BN
PRN:*.??
?W?B?Z.?A
A specification may not contain embedded asterisks;
for example,
A*B.* is an illegal specification. The following are illegal input
specifications:
A,B,C
A:B:C
A?*.B
.AB
DAT:A.*B
A?B:C
*:BIN
If no device is explicitly given for an input specification, the
device associated with the previous specification is assumed.
If no
device is explicitly given for the first specification, the DSK:
is
assumed. Thus, the following input specifications are equivalent:
DSK:B
SYS:B.*,C.*,D.*
B.*,DTAO:,SYS:*.BN

B
SYS:B.*,SYS:C.*,SYS:D.*
DK:B.*,DTAO:,SYS:*.BN

You can include as many as five input specifications in a single
command line.
If all the files are on the same device, the input
device need be specified only once. For example:
DTAO:*.BN,*.SV,*.RL
refers to files on DTAO that have .BN, .SV, or .RL extensions with any
file name.

16-2

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
16.1.2

Output Specifications

FOTP output specifications consist of a device, a file name, and a
file extension. Output specifications are optional. You can use the
wild card asterisk in output specifications, but use of the question
mark is illegal.
If no output device is specified but a file name is given, then
is assumed. If no file name is specified, then *.* is assumed.
the following output specifications are equivalent:
DSK:A
DSK:A.*
DTA3:*.*

A
A. *

DTA3:

16.2

DSK:
Thus

USING FOTP

Since FOTP performs file transfers in a different manner than other
OS/8 transfer programs, the following is a detailed description of the
way FOTP works. One of the main uses of FOTP is to copy files from
one device to another. The following examples show how FOTP examines
each aspect of a command to determine what operation will take place.
Example 1:
To copy the file SMILE.PA from DTA3 to DTAS, changing its name to
FROWN.PA, type the following command in response to the Command
Decoder *:

*DTA5: FROWN. F'A·:.DTA3: SMILE. F'A
1.

If FOTP does not find the file SMILE.PA on DTA3,
following message appears and no transfer is made:

the

*NO FILES OF THE FORM SMILE.PA
2.

FOTP examines DTAS to determine whether it already contains a
file FROWN.PA. If FROWN.PA is already on DTAS, FOTP deletes
it before beginning the transfer. This process is known as
predeletion.

The /N option specifies that no predeletion is desired.
the command:

Thus

~DTA5:FROWN.F'A~DTA3:SMILE.F'A/N

begins to copy SMILE.PA to DTAS without deleting the old
FROWN.PA.
FOTP does this by opening a tentative file named
FROWN.PA on DTAS. When the command completes the transfer
operation, it closes the tentative file.
Closing this
tentative file makes it a permanent file and deletes any old
files of the same name. This process is called postdeletion.
4.

FOTP assigns the creation date of SMILE.PA to FROWN.PA. This
is an advantage over PIP, which would assign the current date
to the new file.
If you always transfer files with FOTP, you
preserve the original creation date of the file. Thus this
feature of FOTP allows you to differentiate between versions
of a file since the more recent version should have a later
date.

16-3

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
5.

Use the /T option of FOTP to assign the current date to a
file.
For example, if SMILE.PA is undated, FOTP assigns the
current date to the newly created FROWN.PA.
-.!IrTAS:FROWN.PA-:':IrTA3:SMILE.PA/T

You may be using the additional information words feature of
OS/8.
This feature allows you to associate additional
information (other than the creation date)
with each file
entry in a device directory. FOTP transfers such additional
information words from SMILE.PA to FROWN.PA.
(PIP does not
perform this function.)
If the file structure on DTAS has space for more information
words than with SMILE.PA, then those extra words are set to

If the file structure on DTAS does not have enough space for
all
the
additional
information words associated with
SMILE.PA, then FROWN.PA is given as many as can fit (from the
left) .
Excess information words
(on the right) are not
transferred.
Example 2:
Normally, you copy files from one device to another without changing
the file name.
For example, to copy the file TEST.PA from DTAI to
DTA2, type:
*IrTA2:TEST.PA<DTAI:TEST.PA

in response to the asterisk printed by the Command Decoder.
Since
this transfer operation is so common, FOTP allows the output file name
to be abbreviated to *.*. The *.* means that you use the input file
name as the output file name.
Thus you could type the preceding
command as:

Since the *.* specification is so frequently used, it is the default,
that is, if no output file name is specified, *.* is assumed. So you
can further simplify the preceding command to:
...!.IrTA2: <DTAI: TEST. PA

Example 3:
One feature of FOTP allows you to use the same command line to
transfer multiple files from one device to another. For example, to
transfer five FORTRAN source files from SYS to RKA2, type:
-.!RKA2: *. *-:"SYS: DATAl. FT, DATA:!. FT, DATA3. FT, DATM. FT, DATAS .FT

The wild card characters * and ?, explained
previously,
are
particularly useful when doing multiple file transfers. For example,
to transfer all FORTRAN II source files from SYS to RKA2, type:

The specification *.FT stands for files with any name
.FT extension.
To copy all files from DTAI to DSK, type:

16-4

that

have

the

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Note that the *.* specification has a different meaning when it
appears on the left side of the < than it does when it appears on the
right. When used on the output (left) side, *.* means that the output
file name is the same as the input file name. When used on the input
(right) side, *.* means transfer or consider all files on this device.
For example:

*RKA2:<SYS:TEST1.PA,TEST2.PA,TEST3.PA
copies three files from SYS to RKA2. PIP would require three commands
to perform the same operation. Each command transfers one file.
In the preceding example, no output file name is specified, so *.* is
assumed.
No device is specified for the files TEST2.PA and TEST3.PA,
so the device specified as the previous input device (SYS) is assumed.
Frequently, you will copy several files with similar names (as above)
from one device to another.
In many cases, you can reference these
files by a single file specification, using the ?
wild character.
For example, the command:

transfers all files on DTAI that have the extension .PA and that
names beginning with TEST followed by one other character.

16.2.1

have

Additional FOTP Commands

Here are some additional FOTP commands that you may find useful.
To transfer the file X.Y from disk to DECtape:

..!DTAO:<X.Y
To transfer the files A, B, C, D and E from SYS:

to DTA3:

To transfer all FORTRAN source files
producing a log of those copied:

DECtape

another,

To list all FORTRAN and BASIC files on the line printer
appearance on DSK:

order

listing

all

from

one

.!.LPT: <*.FT, *. SA
To list all FORTRAN and BASIC files on the line printer,
FORTRAN files before all BASIC files:

To copy all files other than .SV and .BN files from DTA3:
to DSK:,
then copy all files other than those whose names begin with a K from
DTA2:
to DSK:. Log all files copied:

16-5

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
To copy the file A.B from DSK:
to DTAl:, changing its
Give the new file today's date:

name

C.D.

*DTA1:C.D<A.B/T
To copy all files from LTA2:
that have the extension .PA to SYS:,
changing the extension to .PL and allocating storage on SYS: without
doing predeletions:

To find all files on RKA2: with the name FOO and any extension but
those that have today's date, and copy them to SYS:, changing the file
name to WXYZ yet keeping the extension:

To delete all disk files (except those with today's date) that either
have the extension .LS, .TM, or .BK and those whose file name begins
with TMP:

To delete each .BN file for which there is a corresponding .PA file:

**.BN<*.PA/D
To delete all .LS files on DTA3: for which there is a file on RKAO:
with the same name but with an extension of either .PA or .RA or with
no extension:

To delete all files on the disk for which there are already copies
one of the four DECtape drives:

To produce a log of all files on DTAl:
that have the file name FOO
and an extension which is the same as any file on SYS: that has a one
or two-character file name beginnlng with a "T". Do not perform any
transfers or deletions:
lICDTA 1 : FOa. lIC· 'SYS: T'!' • *IN/D/L

To change the name of the file DSK:FILE.PA to FILE2.PA:
*FILE2.PA<FILE.PA/R
To rename all files on DTA6:

with a .PA extension to a .PB extension:

To change the extension from .RL to .OL of all files on DTAl:
that
correspond to files on DSK: with the same name and today's date:

16-6

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
16.2.2

Advantages of Predeletion

The default mode (and the recommended one)
of FOTP is the use of
predeletion when copying files.
Predeletion creates space on the
output device for the new file. Suppose that,
in Example 1 above
(Section 16.2), DTA5 were almost full.
There might not be enough
space on DTA5 for SMILE.PA.
Deleting FROWN.PA first could create
enough space for SMILE.PA.
Predeletion normally places the new file in the space occupied by the
file you are replacing.
In Example 1 above, if FROWN.PA is first
deleted, the space where it resided is empty. You could then use this
empty space for the new copy of FROWN.PA (the former SMILE.PA). If
you did not use predeletion, the new tentative file for FROWN.PA would
probably be placed at the end of the tape. This procedure would
create a gap (EMPTY) when the old copy of FROWN.PA was deleted;
thus
the files on DTA5 would be ordered differently.

16.2.3

Advantages of Postdeletion

Postdeletion is a slightly safer method of transferring files because
you do not delete the original file until you complete a transfer.
Suppose that, in Example 1 above, SMILE.PA is an updated version of
the FROWN.PA, existing on DTA5, and that these are the only two copies
of a certain source file.
If you perform predeletion and SMILE.PA is
discovered to have a permanent input error, that source file will have
ceased to exist because SMILE.PA will be unreadable and FROWN.PA will
have been deleted.
The use of postdeletion in this case would save
the original copy (FROWN.PA)
even though the
updated
version
(SMILE.PA) could not be read.

16.2.4

Control Characters

You can use the special characters CTRL/C and CTRL/P to terminate FOTP
operations.
When you type CTRL/C, FOTP continues operation until the
files on the output device are the same as those in the output device
directory. Control then returns to the OS/8 Keyboard Monitor.
CTRL/P causes FOTP to terminate the current operation but to still
retain control. The output device directory is updated to reflect the
operations completed before the termination occurred. FOTP prints an
asterisk and can receive another I/O specification line.
If you type CTRL/C or CTRL/P when deleting (/D) or renaming
(/R),
FOTP operations are performed and the following message appears:

ORIGINAL DIRECTORY PRESlRVED

16.3

FOTP OPTIONS

The options listed in Table 16-1 may be used in a
line.

16-7

FOTP

specification

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Table 16-1
FOTP Options
.....-------~-----

Meaning

Option
!----------1------------- - -

Current date. Consider only those input files
with the current date when performing a FOTP
operation.
For example, if you
type
the
command:

FOTP transfers from DTAO to DSK only those input
files that have the current date.

Do not perform any I/O transfers, that is,
perform
only
deletions.
/D
is
not an
abbreviation for delete although it usually
performs that operation. This option compares
the input
specification
with
the
output
specification, if any, for matching files.
If a
match is made,
FOTP
performs
as
though
transferring the file,
and then deletes the
transferred file.
If no transfer occurs, no postdeletion occurs.
Predeletion might still occur unless you include
the /N option. If you specify no output device,
FOTP assumes the first input device specified as
the output device. If you specify no output
files or extensions, that is, *.* is specified
or assumed, the input file names become the
output file names.
If you specify no input
files, no deletion takes place.

Failsafe. The /F option protects files during a
transfer operation.
It is particularly useful
when transferring a great number of files from
disk to DECtape.
The /F option allows you to
mount a new volume if a large file will not fit
on the output device or if all files will not
fit on the output device.
If, for example, you
wish to transfer all .BN files from DSK to DTAO,
type:
*[lTAO: ·:.[lSK: *. BN/F

If the output device becomes
full
before
transfer is complete
(or if a large file will
not fit), FOTP prints:
~MOUNT

NExT OUTPUT VOLUME:

Dismount the current tape and mount a new tape
on
the same unit.
Type any character to
continue. The device mounted must have a good
OS/8
directory.
FOTP
then continues the
transfer on the new volume and updates the
directories of both volumes.
(continued on next page)

16-8

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Table 16-1
(Cont.)
FOTP Options
Option

Meaning

List on the terminal the names of files affected
during the FOTP operation. Note that neither
the device nor the output file is listed.

No predeletion. Delete output file names after
a successful I/O transfer occurs. If an I/O
transfer proceeds, any other files of the same
name will automatically be deleted when the file
is closed.

Other than the current date.
Consider only
those input files with a date other than the
current date when performing a FOTP operation.

Query the user about each relevant file name to
determine
whether
you
want the specified
operation to occur for that file. This relevant
file name could be either an input or output
file name depending upon the type of FOTP
operation being performed. For example, if you
are renaming input files, FOTP prints
the
affected input file names. If you are deleting
output files, FOTP prints the output files that
will be affected.
FOTP prints each relevant
file name on the terminal and waits for you to
respond.
A response of Y causes the specified
operation to be performed. Any other response
causes that file to be ignored, and FOTP prints
the next relevant file name.

Rename the output file without performing any
transfer.
Perform this operation by specifying
the same device as both the input and output
device. For example:

*DSK:TEST3.PA<DSK:TEST2.PA/R
would change the name of the DSK file TEST2.PA
to TEST3.PA without performing any transfer.
(a)

(b)

The rename option (/R) now looks at the /T
switch.
If /T is typed, then not only is
the file renamed, but the new file receives
today's date. Without /T, the new name has
the same date as the old name.
The rename option (/R) now allows you to
rename a file to its own name. This was
not previously permitted. It is not very
useful
unless
you include some other
switch, for example /T.
(continued on next page)

16-9

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Table 16-1
(Cont.)
FOTP Options

Option

Meaning

r-----------------T--------------

/R (cont.)

(c)

-----------------------------~

If you have specified no output file with
/R, the FOTP assumes the same name as the
first input file.
Example:
To redate all files on a
1, 1976:

DEC tape

Jan.

*DATE 1/1/76
*RENAME DTAO:*.*/T
/T

Assign the current
input file.

date

the

corresponding

Treat each input specification separately. This
option causes FOTP to find files in the same
order as they are entered
in
the
input
specifications. For example, the command:

*DTAO:<DSK:TEST.PA,DATA1.FT,TEST2.PA/U/L
TEST.PA
DATA1.FT
TEST2.Pf1
finds the files in the order that they were
specified in the command, not in the order in
which they may appear on DSK.
/V

the
For

transfers to DTAO all files on SYS
those with .SV or .HL extensions.

other

than

the

Print the
terminal.

16.3.1

Consider only input files which do not have
form specified by the input specifications.
example, the command:

version

number

FOTP

Examples of FOTP Specification Commands

The following are legal command strings to FOTP.
When FOTP has
completed an operation, control returns to the Command Decoder for
additional input, unless you use ALTMODE to terminate the FOTP command
line.
Example 4:

*DTAO: -::A.B
This command string transfers the file A.B
DTAO.

16-10

from

the

device

DSK

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Example 5:

This command string transfers the files A, B, C, D,
system device to DTA3.

and

from

the

from

DTA5

This command string lists all FORTRAN files, then all BASIC
the line printer.

files

Example 6:

This command string transfers all FORTRAN source files
DTA2, producing a log of those copied.
Example 7:
~LPT:<*.FT,*.BA/U

Example 8:

This command string copies from DTA3 to DSK all files other than core
image
(.SV)
and binary (.BN). It then copies from DTA2 to DSK all
files other than those with names beginning with K.
A listing is
printed of all files copied.
Example 9:
*DTA1!C.D<A.B/T
This command copies the file A.B from DSK to DTAl, changing
to C.D, and assigns the current date to the file.

its

name

This command copies from LTA2 to the system device all files with
extension, changing the extension to .PL.

.PA

Example 10:

Example 11:

This command string deletes any disk file that has an extension of
.LS,
.TM, or .BK or a name beginning with TMP if the file does not
have the current date.

16.4

ERROR MESSAGES

The FOTP error messages are listed in Table 16-2.

16-11

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Table 16-2
FOTP Error Messages
Message

Meaning

ALREADY EXISTS (file name)

An attempt waS made to rename
output
file with the name of
existing output file.

an
an

BAD INPUT DIRECTORY

The directory on the specified input
device is not a valid OS/8 device
directory.

BAD OUTPUT DEVICE

Self-explanatory.
This
usually appears when you
non-file-structured device
output device.

BAD OUTPUT DIRECTORY

The directory on the specified output
device is not a valid OS/8 device
directory.

DELETES PERFORMED
ONLY ON INPUT
DEVICE GROUP 1
CAN'T HANDLE
MULTIPLE DEVICE
DELETES

You specified more than one input
device with the /D option when you
specification
included
no
output
(device or file name).

ERROR ON INPUT DEVICE,
SKIPPING (file name)

The file specified is not transferred,
but any previous or subsequent files
are transferred and indicated in the
new directory.

ERROR ON OUTPUT DEVICE,
SKIPPING (file name)

The file specified is not transferred,
but any previous or subsequent files
are transferred and indicated in the
new directory.

ERROR READING INPUT
DIRECTORY

Self-explanatory.

ERROR READING
OUTPUT DIRECTORY

Self-explanatory.

ERROR WRITING
OUTPUT DIRECTORY

Self-explanatory.

ILLEGAL *

You entered an asterisk as an embedded
character in a file name, for example,
TMP*.BN.

ILLEGAL ?

You entered a question
output specification.

NO FILES OF THE
FORM xxxx

No files of the form (xxxx) specified
were found on the current input device
group.

message
specify a
as
the

mark

(continued on next page)

16-12

FILE-ORIENTED TRANSFER PROGRAM (FOTP)
Table 16-2
(Cont.)
FOTP Error Messages
Message

Meaning

~------------------------~------------------------------------------~

NO ROOM, SKIPPING
(file name)

No space is available on the output
device to
perform
the
transfer.
Predeletion may already have occurred.

SYSTEM ERROR-CLOSING
FILE

Self-explanatory.

USE PIP FOR NON-FILE
STRUCTURED DEVICE

An input device specified
file-structured device, for
PTR.

16-13

is not a
example,

CHAPTER 17
FUTIL

17.1

INTRODUCTION

FUTIL enables you to examine and modify the contents of mass storage
devices.
It is the only program currently available that you can use
to patch programs containing overlays (F4/LOAD outputs).
Other
possible uses include examination and repair of OS/8 directories; bad
block checking and correction;
decimal/octal conversion of double
precision numbers;
output of the Core Control Block (CCB) of .SV
files and the HEADER of .LD files;
and the creation of special
directories.
Supporting these functions is signed double-precision
arithmetic expression evaluation that you can use in the command
syntax whenever you need a numeric value.
FUTIL commands are divided into two groups.
The first group uses
single
letters
to direct the program in the examination and
modification of single words on the device specified.
The second
group of commands uses command words to direct the program in the
dumping, listing, modifying and searching of the device on
a
block-by-block basis.
Also included in this group is a series of
commands to direct the program in some auxiliary functions including
setting and resetting switches and variables within the program,
showing current FUTIL parameters.
Several examples appear in Section 17.4. The first two examples are
especially simple and well-documented and can acquaint you with the
features of FUTIL. You may want to look at them at this point to get
a better understanding of the material that follows.

17.1.1

Special Characters Used in FUTIL

Several characters, when keyed, cause immediate action from the
program.
Typing either CTRL/P or CTRL/C will immediately cause the
program to stop whatever it is doing. CTRL/P then causes the program
to go back to command input mode and wait for you, while CTRL/C
returns control to the OS/8 Monitor.
CTRL/S and CTRL/Q control
program execution (including all I/O). Typing CTRL/S at any time will
cause the program to pause and wait for either CTRL/C, CTRL/P or
CTRL/Q.
Typing CTRL/Q will then allow program execution to resume.
Any other characters entered at this point will be simply ignored. If
a CTRL/Q is typed by itself at any time, it is simply ignored.

17-1

FUTIL
NOTE
CTRL/S and CTRL/Q are active at all
times, not just during console output.
The result is that both input from the
console and program execution with no
console interaction (such as SCAN, WORD
and STRING command execution) will pause
and restart with these keys.
During console terminal input, three other keys help with editing the
input string of characters. These keys are RUBOUT, CTRL/U and CTRL/R.
The action of RUBOUT and CTRL/U is exactly the same as for the OS/8
Monitor and Command Decoder (including usage of "scope mode" operation
to change the action of the RUBOUT key from echoing the rubbed out
characters between backslashes to erasing the characters from the
screen). The action of CTRL/R is the same as that of the LINE-FEED
key for the Monitor and Command Decoder.
If you have upper-lower case terminals, the program translates all
lower case characters received from the keyboard to upper case. The
characters are echoed and handled internally as upper case characters.
While this makes use easier, it does not allow any lower-case
characters to be input directly.
In those cases where you need lower-case codes in the modification of
a file,
either use the codes directly or use a text editor. This
translation occurs only on input. Lower-case characters in a file
will be printed to the best ability of the output device. This may
produce incorrect results on upper-lower case line printers.
All of the commands are taken in context. This means that many of the
characters in the single character command set will not be considered
to be commands if they are included in a line that begins with a
command word or if they are embedded within expressions.
The carriage-return always starts command execution and terminates all
word-type command lines.

17.1.2

Running FUTIL

To run FUTIL, type:

.R FUTIL
or

.RU dev:FUTIL
When started, FUTIL is set up to access the system device, the ERROR
message output mode is set to LONG, the access MODE is set to NORMAL,
and no file is known. To access some other device, type:
SET DEVICE dev
To set the ERROR mode to SHORT, type:
SET ERROR SHORT

17-2

FUTIL
To use some other access mode, type:
SET MODE <mode>
command with a <mode> of LOAD, OFFSET or SAVE. When in OFFSET mode,
the OFFSET to be used can be specified by the command SET OFFSET nnnn.
Lastly, a file lookup can be performed by giving a FILE command
(with
three default extensions).

17.1.3

Access Method

The program accesses the OS/8 device one OS/8 block (256 words)
at a
time.
For every location specified, the real block and word are
determined and compared with the current block in memory.
If the
desired
block
and
current
block
are
not
the
same, the
<something-changed> flag is checked to see if anything has been
changed in the current block. If nothing has been changed, the new
block is read in.
If something has been changed, the current (modified) block is first
written out and then the new block is read in. This action happens
correctly even when the access mode is changed because it is done at
the level of the OS/8 block number just before calling the current
device handler. The status of the <something-changed> flag can be
determined by simply SHOWing ABS, REL or ODT locations. If the flag
is set, the word MOD will be output following location information.
The contents of the OS/8 device, therefore, do not change unless the
block in which changes are made is written out either implicitly, as
described above, or explicitly, using the WRITE command
(discussed
near the end of the section on word-type commands). The result is
that typing CTRL/C before writing out the current block
(assuming it
has been modified)
will return to the Monitor without modifying the
contents of the device.
Note, also, that only one implicit write attempt is made by the
program.
Should an error occur when the write is attempted (for
example, write-locked device), an explicit WRITE command must be given
to actually write out the block.
If you change the words within some blocks accidentally,
the
<something-changed> flag can be reset by using the SET command to
reset the device (described further along in this writeup) to the same
device currently being used. This will reset the <something-changed>
flag, the current block in memory, and the file start block and
core-control-block/header-block (if they had been set by a FILE
command) •
The resetting of the current block in memory will cause the next
access to the device to read in the block desired. The resetting of
the file information will require a new file command to be given to
set it back up.
If you cannot remember the current setting of the
device, use SHOW DEVICE first and then set it the same.
Files stored on an OS/8 mass-storage device generally fall into one of
four categories.
The program has four corresponding modes for
accessing the device. The current mode of the program can be set by
the SET command or by chaining (as described previously) and examined
by the SHOW command (to be described later).

17-3

FUTIL
The four categories and their corresponding modes are:
1.

General (binary, ASCII and data) files - NORMAL mode

Core image (save) files - SAVE mode

FORTRAN IV load modules - LOAD mode

System overlays - OFFSET mode

The actual operation of the program for each
follows:

these

modes

NORMAL

The high order 7 bits of the 15 bit address are added
to the current block number to get the actual block
number. The low 8 bits of the 15 bit address are used
to specify the desired word within that block.

SAVE

The file to be examined must be set up by a FILE
command.
Block numbers are used to specify an overlay
number (future MACREL/LINK support) and must be exactly
zero
(0)
for files without overlays (generated by the
monitor SAVE command). The core segment data
(pages
and fields) from the file's CCB (core-control-block) is
used to determine where on the device the desired word
is located.
This is done by first determining the
correct block from the file's CCB and then using the
low 8 bits of the address to specify the desired word
within that block. Specifying a nonexistent address or
overlay for one of the single-character (ODT) commands
will cause an error. Specifying a nonexistent address
or overlay for any of the word-type commands will cause
the program to ignore the address and access no data.

LOAD

The file to be examined must be set up by a FILE
command.
Block number specifications are actually
taken as FORTRAN IV overlay specifications and must be
contained within the file.
You use the information
from the OIT (overlay-information-table) in the header
block of the file to determine where on the device the
desired word is located.
Nonexistent addresses are
handled the same way as for SAVE mode.
NOTE
Because the block part
of
the
location
specification changes definition depending on
the mode in use, it is recommended that the
first operation following a switch to SAVE or
LOAD mode explicitly specify a block part of O.
Otherwise a previously specified block part
will be taken to mean a non-existent overlay
number, causing an error.

OFFSET

The 12-bit OFFSET (set by the SET command and examined
by the SHOW command) is subtracted from the low order
12 bits of the address and then the same arithmetic as
with the NORMAL mode is used. This mode is used mostly
with system overlays whose start block number and
actual loading address is known. By setting the OFFSET
to the loading address (which can only be a 12 bit
number), the 12 bit actual addresses of the overlay can
be used.
17-4

FUTIL

The SAVE and LOAD modes are mentioned together throughout this chapter
as MAPPED modes because their method of address translation uses a
descriptor block from the file of interest to control access to the
file in a noncontiguous manner.
NOTE
For all access modes, the OS/8 block
number for the block to be read is
stored (for display) in the computer MQ
register
(if present).
The value is
stored before checking if the current
block
needs to be written.
It is
particularly useful for following the
progress of the SCAN command.

17.1.4

Referencing Words on the Device

The words on the OS/8 device are referenced by their location (often
abbreviated as <1». This location consists of an optional block or
overlay number (which must be followed by a "." if present), and an
address or displacement. The block/overlay number is a 12-bit number
which must be in the range 0 thru 7776
(octal), or 4094
(decimal) •
Block number 7777
(or 4095, decimal) does not exist under OS/8, and
the program will ignore this number.
The overlay number is further limited to the number of overlays at a
given address. Whenever the block/overlay part of the location is not
used, the program will use the
last
specified
value.
The
address/displacement is a 15 bit number (5 octal digits), but leading
O's need not be specified. Thus, the forms and their corresponding
examples are as follows:
Form

Example

1201.37524

3.57633

15721

223
CAUTION

Neither this program nor the OS/8 device
handlers generally incl.ude checking for
legal block numbers.
It is assumed that
all accesses to the device will be done
after checking with the directory for
legal file start blocks and lengths,
which is the normal mode of operation
under
OS/8.
This
can
have very
interesting results with this program;
for example, the RK8/E handler, given a
block number greater than 6257
(octal)
on device RKAO, will continue on into
device RKBO.

17-5

FUTIL
For the rest of this document, unless otherwise stated, block will
mean
block
or
overlay
and
address will mean <address> or
<displacement>, depending on usage. Therefore the definition will be:
[block.]address=<location>=<l>
Since these location references are numeric input, all of the
characteristics described next can also be used when specifying
locations.

17.1.5

Numeric Item (or Numbers)

The program uses two switches, CTRL/D and CTRL/K, to allow the input
of octal, decimal or mixed numeric input wherever numeric input is
used. Each new command line always resets the input mode to octal.
The character CTRL/D switches the input mode to decimal.
The
character CTRL/K switches the input mode back to octal.
These two
switches may be located anywhere in numeric input.
For example, when inputting a string of numbers, the
alternately decimal and octal if it were

input

would

Two other characters, the double quote (") and the apostrophe ('), may
be used for numeric input. The double quote functions the same way in
this program as it does in PAL8:
the 8-bit ASCII value of the
following character is used as a number. As with all character input,
the special characters described earlier cannot be used.
The
apostrophe functions in the same way that the TEXT pseudo-op operates
in PAL8: the following two characters are masked to 6 bits each and
packed into a 12-bit word.
Two characters must always follow the
single quote. If you desire to pack one half of the word with a 6-bit
00, use the character "@". For example, a string equivalent to the
file name PIP.SV would be represented by the following string:
'PI,'P@,O,'SV
Expressions may also be used for numeric input when enclosed in
parentheses.
Use parentheses for each expression, thereby making all
the options of the EVAL command available for numeric input.
For
example, the contents of the switch register can be used for a number
by the expression (S), or the current block number +5 could be used by
the expression (B+5). See the discussion of the EVAL command for the
other options available.
NOTE
Parentheses
must
surround
the
expression.
Neither digits nor the
switch characters may be outside of the
parentheses or an error will result.
This is required because many of the
non-alphabetic characters have multiple
meanings (commands or operators) so the
use of parentheses eliminates ambiguity.

17-6

FUTIL
17.1.6

Errors and Error Messages

Whenever the program recognizes an error, it outputs an error message.
The message tells both what went wrong and where in the command line
the error occurred. Depending on the setting of the ERROR mode
switch, either short or long messages are output:
?<ee>at<cc><error messdge>
or
?<ee>at<cc>
where <ee> is the error code, <cc> is the number of the column in the
command line where the program stopped scanning, and <error message>
is the message itself. There are currently 45 error conditions with
corresponding codes and messages to assist you. The error codes and
their messages can be printed out by the SHOW ERRORS command.
The
ERROR mode is set by the SET command.
The error messages are swapped with the USR but not in the normal
manner, allowing write-locked startup with the loss of the message
text (see Section 17.5 for more information).

17.2

SINGLE-CHARACTER (ODT-LIKE) COMMANDS

These commands allow you to modify and examine words on an OS/8 device
in the same way that ODT allows you to modify and examine main memory.
In all of the following commands where the numeric item <n> is
specified, the operation of closing the location is to place the value
of <n> into the word, if open. If the current location is not open,
or if <n> is not specified, no change takes place.
Refer to
Introduction to Pr~ammi~ and to Chapter 19, on ODT, for more
information. Note that [<n>] (with the following commands) means that
a numeric item may be supplied optionally.
<1>/

Open and output the contents of
the current OUTPUT mode.

Reopen the last location opened by one of these
commands and output its contents in the current
OUTPUT mode.

[<n>]t

Close the current location, reopen it and output
its
contents
in
BCD
(3-digit binary-coded
dec imal) .

[<n>]$
(dollar sign)

Close the current location, reopen it and output
its contents in OS/8 ASCII.

[<n>]%

Close the current location, reopen it and output
its contents in BYTE octal
(8 bits with OS/8
packing) .

[< n>] &

Close the current location, reopen it, and
its contents in XS240 format packed ASCII.

output

[<n>] :

Close the current lcoation, reopen it, and
its contents in SIGNED decimal.

output

17-7

location

<1>

FUTIL

[<n>]<

Close the current location, reopen it, and
its contents in OCTAL.

output

[<n>] =

Close the current location, reopen it, and
its contents in UNSIGNED decimal.

output

[<n>]>

Close the current location, reopen it, and
its contents in PDP (symbolic).

output

[<n>] ?

Close the current location, reopen it, and output
its contents in DIRECTORY format [negated DECIMAL,
DATE (see "@" next) and packed (ASCII)].

[<n>]@

Close the current location, reopen it, and output
its contents in DATE format:
dd-mmm-yy 2 digits
each for the day and year and 3 alphabetic
characters for the month (except for illegal month
numbers, which are output as a space and 2 decimal
digits) .

[ <n>] [

Close the current location, reopen it, and
its contents in ASCII.

output

[<n>] \

Close the current location, reopen it, and
its contents in FPP (symbolic).

output

[<n>] ]

Close the current location, reopen it, and
its contents in packed ASCII.

output

[<n>]$
(" ALTMODE" or
"ESCAPE" key)

Close the current location, reopen it, and type
its contents as specified by the current FORMAT.

[<n>]<cr>

Close the current location.

[<n>] :

Close the current location and open the next
sequential location. Neither address nor contents
are output, but one space is echoed.
NOTE
The
";"
command
advances
through
addresses without outputting their value
in octal when some other format is more
helpful.
For example, when examining a
directory, the file name and extension
can be output using the "]" command
(PACKED ASCII), the date can be output
using the "@" command, and the file
length can be output using the ":"
command. All of this information can be
made to appear on one line by using the
";" command. This does the incrementing
between each of the output commands.
The result would look similar to this:

17-8

FUTIL
For the following commands, the location of the newly opened word is
output before the contents are output. This location is composed of
the 12-bit block number (4 octal digits), a "." for a separator, and
the 15 bit address (5 octal digits). This is immediately followed by
a slash (I) to separate the contents from the address.
[<n>] <line feed>

Close the current location; open and output
the contents of the next sequential location
in the current OUTPUT mode.

[< n>] !

Close the current location; open and output
the
contents of the previous sequential
location in the current OUTPUT mode.

[<n>]A(circumflex
or up-arrow)

Close current location; open the location
(that would have been referenced if the
contents
were
a PDP-8 memory reference
instruction), and output the contents of the
new location in the current OUTPUT mode.
This command works like the
stand-alone
version of ODT (not like the OS/8 version).
Even if bit 3 of the word is set, this
command will not do the equivalent of an
indirect reference.

[<n>] (backarrow
or underline)

Close the current location, take its contents
as an address, open that location, and print
its contents in the current OUTPUT mode.
This operates as an indirect address into the
current field.
The field currently being
examined (the high octal digit of the 5-digit
location)
will
not be changed by this
operation.

<1>+

Open the location <1> locations forward from
the current location, and output its contents
in
the
current
OUTPUT
mode.
15-bit
arithmetic is used and the block part is
ignored, so this will operate across field
boundaries, that is, within a 32K area.

<1>-

Open the location <1> locations backward from
the current location and output its contents
in
the
current
OUTPUT
mode.
Same
restrictions as with the '+' command.

The current OUTPUT mode has been mentioned several times above.
The
program will output the contents of a location either as a four-digit
octal number or as a four-digit octal number with two spaces and the
symbolic representation
(PDP or FPP) of the word. See the SET and
SHOW commands (Sections 17.3.2.4 and 17.3.2.5) and the following
section.

17.2.1

Symbolic Output Formats

The symbolic typeout is in nearly the same format that input to an
assembler would need to be to generate the contents of the current
location. It is assumed that these contents are either a PDP-8 or an
FPP-12/8A instruction, depending on the output selected. If the word
to be output is not an instruction (as is the case for the second word
of all 2-word instructions), the decoding will be meaningless.

17-9

FUTIL
For PDP-8 instructions, decoding into mnemonics is done for all memory
reference instructions, for all legal operate instructions (including
8/E EAE instructions except for SWAB), for all 8/E processor, extended
memory and memory parity lOT's, for teletype and high-speed paper-tape
lOT'S, for 8/E redundancy check option lOT'S, for programmable
real-time clock lOT's and for FPP lOT's.
There are currently a total of 96 lOT'S, and the program has space for
an additional 32 lOT codes and their mnemonics. These can be patched
directly into the program using itself.
The first word of each
four-word entry is the lOT code
(for example, 6221 for CDF 20),
followed by 3 words containing up to 6 packed ASCII characters padded
with trailing O's.
No attempt is made to decode any micro-coded lOT's. Either an exact
match for the current contents will be found in the table or the
program will output:
lOT nnnn
where nnnn is the octal typeout of the low 9 bits of the code.
The next free location in the table (in field 1) is pointed to by the
contents of location 10000. The table is terminated by the first 0
for an lOT code, so additions must be contiguous and added directly at
the current end of the table.
For FPP instructions, the full FPP-8/A instruction set is decoded
except for IMUL, which is actually an integer mode LEA. For the data
manipulation instructions, the op-code mnemonic is followed by a "t"
for the long-indexed format, by a "%" for the indirect-indexed format,
and by a space for the base addressing format.
For the indirect-indexed and
address is output as:

base

addressing

formats,

the

operand

B+nnn
where nnn is the 3-digit octal value of the displacement (3 or 7 bits)
multiplied by 3. These formats are those used by the RALF assembler.
This is also true for LEA instructions (that is, LEAl is decoded as
LEA%) .
Both jump and load-truth instruction decoding is done as a single
mnemonic whose last two characters indicate the specified condition.
All instructions that use two words are decoded with an asterisk in
the location in the normal assembler format where the value of the
second word would go.
Index register number and "+" for auto-increment (if used)
are also
shown in the assembler format. Any combinations that are not in the
FPP-8/A instruction definitions are output as unused.
NOTE
For both of these output formats, the
use of the mapped access modes (and the
OFFSET mode for PDP decoding) allow the
use
of
the
actual addresses when
decoding the instruction.

17-10

FOTIL
17.3

WORD-TYPE COMMANDS

These commands are grouped by function, as follows:
Group 1:
DUMP
LIST
MODIFY

type/list out the contents of one or more blocks.
type/list out the contents of one or more locations.
modify one or more locations.

Group 2:
WORD
STRING
SMASK

word search
string search
set up string search mask

Group 3:
SET
SHOW
FILE
WRITE
SCAN
REWIND

set up program switches and variables
show settings of program switches and variables
look up file(s) on device
write out current buffer
scan for bad blocks
move device to block 1 and reset directory segment

Group 4:
OPEN
CLOSE

open an output file on a file-structured device
close the open output file

Group 5:
IF
END
COMMENT
EXIT

cause command skipping based on expression value
resume command execution after unsatisfied IF
pass user commentary to output device
exit to OS/8 (same as CTRL/C)

Group 6:
EVAL

evaluate a signed, double-precision expression.

Command words may always be abbreviated to their first two characters,
as with the Monitor and BUILD, and some of the commands and their
options may also be abbreviated to only one letter. When this is the
case, the command forms given will include the one-letter form.
The
option forms will give the one-letter form directly under
the full
word form.
NOTE
In many cases, two or more words start
with the same letter.
In these cases,
only one of
these
words
may
be
abbreviated to one letter.
The descriptions for each command include each of the possible forms
of the command;
an example of that form follows it on the same line.

17-11

FUTIL
17.3.1

Output Formats

The FORMAT option is used to SET up the output format for
the "$"
(ALTMODE or ESCAPE) command, described earlier, and the default format
for the DUMP, LIST and MODIFY commands, described below.
The syntax
of this command is shown with the other SET commands, but is described
here to make the descriptions of the following three commands more
understandable. The format may be one of the following:
ASCII

output each word as a single ASCII character.

PACKED
P

Output each word as two 6-bit trimmed and packed
ASCII characters. This is the format of PAL8 TEXT
strings.

Output each word as 1 or 2 OS/8 packed ASCII
characters.
The even address words output 1
character and the odd address words output 2
characters.

XS240

Output each word as two 6-bit packed
ASCII
characters by adding a space (240 octal) to the
contents of each 6-bit byte. This is the format
of PAL12 SIXBIT strings.

BYTE

Output each word as 1 or 2 OS/8 packed bytes of 8
bits each as 3-digit octal numbers. The even
address words output 1 number and the odd address
words output 2 numbers.

UNSIGNED

Output each word as an unsigned decimal number.

SIGNED

Output each word as a signed decimal number.

OCTAL

Output each word as a 4-digit octal number.

BCD

Output each word as 3 BCD digits. The digits 0
through 9 are followed by":" (10), ";" (11),
"<"
(12), "=" (13), ">" (14), and "?" (15).

o
B

PDP
FPP

Output each word as an octal number, followed by
2 spaces and its mnemonic representation, assuming
it to be a PDP-8 or an FPP-8A instruction. See
the symbolic output description.