Digital PDFs

DEC-11-OMUPA-B-D

September 1975

294 pages

Original

9.3MB

Document:	RSX-11M Utilities Procedures Manual
Order Number:	DEC-11-OMUPA-B-D
Revision:	0
Pages:	294
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V2/DEC-11-OMUPA-B-D_Util_197509.pdf

OCR Text

RSX-11M
Utilities Procedures Manual
Order No. DEC-11-0MUPA-B-D

RSX-11M
Utilities Procedures Manual
Order No. DEC-11-0M UPA-B-0

RSX-llM Version 2

digital equipment corporation · maynard. massachusetts

First Printing, November 1974
Revised, September 1975

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 to the terms of such
license.
Digital Equipment Corporation assumes no responsibility for the use
or reliability of its software on equipment that is not supplied by
Digital.

@ 1974, 1975 by Digital Equipment Corporation

The HOW TO OBTAIN SOFTWARE INFORMATION pages, located at the back of
this document, explain the various services available to Digital software users.
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
DECOS
UNIBUS
COMPUTER LABS
COMTEX
DDT
DECCOMM

DECsystem-lo
DECtape
DIBOL
EDU SYSTEM
FLIP CHIP
FOCAL
INDAC
LAB-8

MASS BUS
OMNIBUS
OS/8
PHA
RSTS
RSX
TYPESET-8
TYPESET-11

LIMITED RIGHTS LEGEND
Contract No.
Contractor or Subcontractor:

Digital Equipment Corporation

All the material contained herein is considered limited rights data
under such contract.

CONTENTS
Page
PREFACE

CHAPTER

0.1
0.2
0.3

MANUAL OBJECTIVES AND READER ASSUMPTIONS
STRUCTURE OF THE DOCUMENT
ASSOCIATED DOCUMENTS

xi
xi
xiii

INTRODUCTION

1-1

1.1
1. 2
1. 2 .1
1. 2. 2
1.3
1. 3 .1

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

1. 5

RSX-llM UTILITY PROGRAMS
INITIATING RSX-llM UTILITIES
Initiating of Installed Utilities
Initiation of Uninstalled Utilities
RSX-llM UTILITY COMMAND STRINGS
Conunand Format Conventions
INDIRECT FILES
SYSTEM-WIDE CONVENTIONS

PERIPHERAL INTERCHANGE PROGRAM (PIP)

2-1

2.1
2.2
2.3
2.3.l
2.3.2
2.3.3
2.3.4
2.3.4.1
2.3.4.2
2.3.5
2.4
2.4.1
2.4.2

INTRODUCTION TO PIP
INITIATING PIP
PIP COMMAND STRING
Lists of File Specifiers
Defaults in File Specifiers
PIP Conunand Switches and Subswitches
Asterisk Convention - Wild Cards
Wild Cards in Output File Specifiers
Wild Cards in Input Specifiers
File Identification Option
PIP COMMANDS
APPEND Conunand (/AP)
COPY Conunand (No Switch) and MERGE Conunand
(/ME)
DEFAULT Conunand (/DF)
DELETE Conunand (/DE)
ENTER Conunand (/EN)
FREE Conunand (/FR)
IDENTIFY Conunand (/ID)
LIST Conunand (/LI)
PROTECT Conunand (/PR)
PURGE Conunand (/PU[:n])
REMOVE Conunand (/RM)
RENAME Conunand (/RE)
SPOOL Conunand (/SP)
UNLOCK Conunand (/UN)
UPDATE Conunand (/UP)
PIP ERROR MESSAGES
PIP ERROR CODES

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

,
JI
..L. ~

CHAPTER

2.4.3
2.4.4
2.4.5
2.4.6
2.4.7
2.4.8
2.4.9
2.4.10
2.4.11
2.4.12
2.4.13
2.4.14
2.4.15
2.5
2.6

iii

1-7
1-8

2-8
2-12
2-13
2-15
2-16
2-16
2-17
2-21
2-24
2-25
2-26
2-28
2-29
2-30
2-31
2-41

CONTENTS (Cont.)
Page
CHAPTER

CHAPTER

FILE TRANSFER PROGRAM (FLX)

3-1

3.1
3.2
3.3
3.4
3.5
3.5.1
3.5.2
3.5.3
3.6
3.6.1
3.6.2
3.6.3
3.7
3.7.1
3.7.2
3.7.2.1
3.7.2.2
3.8
3.9
3.9.1
3.9.2
3.9.3
3.10

INTRODUCTION TO FLX
INITIATING FLX
FLX COMMAND STRING
FILE TRANSFERS
DOS VOLUME DIRECTORY MANIPULATION
DOS Directory Listings
Deleting DOS Files
Initializing DOS-11 Volumes
RT VOLUME DIRECTORY MANIPULATION
RT Directory Listings
Deleting RT Files
Initializing RT-11 Volumes
FLX CASSETTE SUPPORT
Cassette File Formats
Multi-Volume Cassette Support
FLX Output Files
FLX Input File
FLX PAPER TAPE SUPPORT
FLX SWITCHES
Format Mode Switches
Transfer Mode Switches
File Control Switches
FLX ERROR MESSAGES

3-1
3-2
3-2
3-2
3-3
3-3
3-3
3-3
3-3
3-3
3-4
3-4
3-5
3-5
3-9
3-9
3-10
3-10
3-11
3-11
3-13
3-15
3-20

FILE DUMP UTILITY (DMP)

4-1

4.1
4.2
4.3
4.4
4.5

INTRODUCTION TO DMP
INITIATING DMP
DMP COMMAND STRINGS
DMP SWITCHES
DMP ERROR MESSAGES

4-1
4-2
4-2
4 ... 2
4-5

LINE TEXT EDITOR (EDI)

5-1

5.1
5.2
5.2.1
5.2.2
5.2.2.1
5.2.3
5.2.4
5.2.5
5.2.5.1
5.2.5.2
5.2.5.3
5.2.6
5.2.6.1
5. 2. 6. 2
5.2.7
5.2.7.1
5.2.7.2

INTRODUCTION
USING EDI
Preparing to Run EDI
Initiating EDI
Defaults in File Specifiers
EDI Control Modes
Changing Control Mode
Text Access Modes
Line-by-Line Mode
Block Mode
Line-by-Line Vs. Block Mode
Text Files
Input and Secondary Files
Output Files
Terminal Conventions
Carriage Return
Character Erase (RUBOUT) and Line Delete
(CTRL U)

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

5-7

CONTENTS (Cont.)
Page
5.2.8
5.2.8.1
5.2.8.2
5.3
5.3.l
5.3.2
5.3.3
5.3.4
5.4
5.4.1
5:4:1=1
5.4.1.2
5.4.2
5.4.3
5.4.3.1
5.4.3.2
5.4.3.3
5.4.3.4
5.4.3.5
5.4.3.6
5.4.3.7
5.4.3.8
5.4.3.9
5.4.3.10
5.4.3.11
5.4.3.12
5.4.3.13
5.4.3.14
5.4.3.15
5.4.4
5.5
5.5.1
5.5.1.1
5.5.1.2
c::

c::

EDI Command Conventions
Use of *
Search String Constants
EDI ERROR REPORTING
Command Level Informational and Error
Messages
File Access Warning Messages
Error Messages Requiring EDI Restart
Fatal Error Messages
BASIC EDI OPERATION AND COMMANDS
Basic EDI Operations
Creating a File
Entering Text Into a File
Editing a File
Basic EDI Commands
ADD Command
ADD AND PRINT Command
CHANGE Cornmand
CTRL/Z Cornmand
DELETE Command
DELETE AND PRINT Command
EXIT Command
INSERT Cornmand
LOCATE Command
NEXT Cornmand
NEXT PRINT Command
PRINT Command
RENEW Command
RETYPE Command
TOP OF FILE Command
Sample Editing Session
EXTENDED EDI COMMANDS
Setup Commands
BLOCK ON/OFF Command
CONCATENATION CHARACTER Command

.J•.Je.L.eJ

OPENS Cornmand

5.5.1.4
5.5.1.5
5.5.1.6
5.5.1.7
5.5.1.8
5.5.1.9
5.5.1.10
5.5.2
5.5.2.1
5.5.2.2
5.5.2.3
5.5.3
5.5.3.1
5.5.3.2
5.5.3.3
5.5.3.4
5.5.3.5
5.5.3.6
5.5.3.7
5.5.3.8
5.5.3.9

OUTPUT ON/OFF Command
SELECT PRIMARY Command
SELECT SECONDARY Command
SIZE Command
TAB ON/OFF Command
UPPER CASE ON/OFF Command
VERIFY ON/OFF Command
EDI Input/Output Commands
FILE Command
READ Command
WRITE Command
Line Pointer Control (Locative) Commands
BEGIN Command
BOTTOM Command
END Command
FIND Command
OLDPAGE Command
PAGE Comrnand
PAGE FIND Command
PAGE LOCATE Command
SEARCH AND CHANGE Command

5-8
5-8
5-8
5-9
5-9
5-9
5-9
5-10
5-10
5-10
5-10
5-11
5-11
5-13
5-15
5-15
5-15
5-16
5-16
5-17
5-18
5-18
5-19
5-19
5-20
5-20
5-22
5-22
5-22
5-23
5-23
5-23
5-25
5-25
5-26
5-26
5-27
5-28
5-29
5-29
5-30
5-31
5-31
5-32
5-32
5-33
5-34
5-36
5-36
5-36
5-37
5-37
5-38
5-38
5-39
5-39

CONTENTS (Cont.)
Page
5.5.3.10
5.5.4
5.5.4.1
5.5.4.2
5.5.4.3
5.5.4.4
5.5.4.5
5.5.4.6
5.5.4.7
5.5.4.8
5.5.4.9
5.5.4.10
5.5.4.11
5.5.4.12
5.5.4.13
5.5.4.14
5.5.5
5.5.5.1
5.5.5.2
5.5.5.3
5.5.5.4
5.5.5.5
5.6
5.6.1
5.6.2
5.6.3
5.6.4
CHAPTER 6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.3
6.4
6.4.1
6.4.2
6.5
6.6
6.7
6.7.1
6.8
6.8.1
6.8.2
6.9
6.10
CHAPTER 7
7.1
7 .1.1
7 .1. 2
7 .1. 3
7 .1. 4
7 .1. 5

TOP Command
Text Modification and Manipulation Commands
ERASE Command
FORM FEED Command
LINE CBANGE Command
LIST ON TERMINAL Command
LIST ON PSEUDO-DEVICE Command
MACRO Command
MACRO CALL Command
MACRO EXECUTE Command
MACRO (IMMEDIATE) Command
OVERLAY Command
PASTE Command
SAVE Command
TYPE Command
UNSAVE Command
EDI Close Operation Commands
CLOSE Command
CLOSES Command
CLOSE AND DELETE Command
EXIT AND DELETE Command
KILL Command
EDI ERROR MESSAGES
Corrunand Level Informational and Error Messages
File Access Warning Messages
Error Messages Requiring EDI Restart
Fatal Error Messages

5-40
5-40
5-42
5-43
5-43
5-43
5-44
5-44
5-45
5-46
5-47
5-47
5-48
5-48
5-49
5-50
5-50
5-51
5-51
5-51
5-52
5-52
5-52
5-52
5-58
5 .... 59
5-62

SOURCE LANGUAGE INPUT PROGRAM (SLP)

6-1

INTRODUCTION TO SLP
PREPARING TO RUN SLP
Capabilities
Environment
Restrictions
INITIATING SLP
SLP STARTUP
Defaults in File Specifiers
Examples of SLP Initialization
SLP OUTPUT CONTROL SWITCHES
SLP OUTPUT FILES
SLP EDIT COMMANDS
SLP Edit Control Characters
INDIRECT FILES
Creating an Indirect File
Using Indirect Files
SLP EDITING EXAMPLES
SLP ERROR MESSAGES

6-1
6-1
6-1
6-1
6-2
6..,.2
6-2
6-3
6-3
6-4
6-4
6-6
6-6
6-8
6-8
6-9
6-9
6-12

LIBRARIAN UTILITY PROGRAM (LBR)

7-1

INTRODUCTION TO LBR
Format of Library Files
Library Header
Entry Point Table
Module Name Table
Module Header

7-1
7-1
7-2
7-2
7-4
7-4

CONTENTS (Cont.)
Page

7.5.10
7.5.11
7.6
7.7
7.8
7.8.1
7.8.2

INITIATING LBR
LBR COMMAND STRING
DEFAULTS IN LBR FILE SPECIFIERS
LBR FILE OPTION SWITCHES
Compress Switch (/CO)
Create Switch (/CR)
Delete Switch (/DE)
Default Switch (/DF)
Delete Global Switch (/DG)
Insert Switch (/IN)
List Switches (/LI, /LE, /FU)
Replace Switch (/RP)
Spool Switch (/SP}
Selective Search Switch (/SS)
Squeeze Switch (/SZ)
COMBINING LIBRARY FUNCTIONS
LBR CONSTRAINTS
LBR ERROR MESSAGES
Effect of Fatal Errors on Library Files
Error Messages

7-5
7-5
7-5
7-7
7-7
7-9
7-11
7-12
7-13
7-14
7-15
7-17
7-23
7-23
7-24
7-26
7-27
7-27
7-28
7-28

FILE STRUCTURE VERIFICATION UTILITY (VFY)

8-1

8.1
8.2
8.3
8.3.1
8.4
8.4.1
8.4.1.1
8.4.1.2
8.4.1.3
8.4.1.4
8.4.1.5
8.4.2
8.4.3
8.4.4
8.4.5
8.4.6
8.4.7
8.4.8
8.5
8.6

INTRODUCTION TO VFY
INITIATING VFY
VFY COMMAND STRING
Defaults in File Specifiers
VFY COMMAND SWITCHES
Validity Check
File Error Reporting
Files Marked-for-Delete
Deletion of Multiply Allocated Blocks
Elimination of Free Blocks
Recovering Lost Blocks
DELETE Switch (/DE)
UPDATE Switch (/UP)
REBUILD Switch (/RE)
FREE Switch (/FR)
LOST Switch (/LO)
LIST Switch (/LI)
READ CHECK Switch (/RC)
VFY ERROR MESSAGES
VFY ERROR CODES

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

9-14
8-16

COMMANDS AND SWITCHES

A-1

INTRODUCTION
PIP COMMAND SUMMARY
FLX COMMAND SUMMARY
DMP COMMAND SUMMARY
EDI COMMAND SUMMARY
SLP COMMAND SUMMARY
LIBR COMMAND SUMMARY
VFY COMMAND SUMMARY

A-1
A-1
A-3
A-5
A-5
A-12

7.2
7.3
7.4
7.5
7.5.1
7.5.2
7.5.3
7.5.4
7.5.5
7.5.6
7.5.7
7.5.8
.,

'•-'·~

CHAPTER

APPENDIX A
A.l
A. 2
A. 3
A. 4
A. 5
A. 6

A. 7

A.8

vii

8--13

A-13

A-14

CONTENTS (Cont . )
Page
APPENDIX B
B.l
B.1.1
B. l. 2
B. l. 3
B. l. 4
B.2
B.2.1
B.2.2
B.3
B.3.1
B.3.2
B.3.3
B.3.4
B.4
B.4.1
B.4.2
B.4.3
B.4.4
APPENDIX c
C.l
C.2
C.3
C.4

LBR, EDI AND DMP EXAMPLES

B-1

SAMPLE LISTINGS FOR LBR LIST SWITCHES
(OBJECT LIBRARY)
List Module Names
List Module Names and Full Module
Information
List Module Names, Full Module Information
and Module Entry Points (Global Symbols)
List Module Names and Module Entry Points
(Global Symbols)
SAMPLE LISTING FOR LBR LIST SWITCHES
(MACRO LIBRARY)
List Module Names
List Module Names and Full Module Information
SAMPLE EDITING OPERATIONS
File Editing Sample
SAVE and UNSAVE Example
Use of Immediate Macro Command
Use of Macro Commands
SAMPLE DMP LISTINGS
Use of /LB Switch
"Standard" Command Line
Dump Only the Header from SYSGEN.CMD
Use of /BA Switch

B-13
B-13
B-14
B-15
B-16
B-20
B-23
B-24
B-26
B-26
B-26
B-28
B-28

RSX-llM PRINT SPOOLER TASK

C-1

RECEIVE QUEUE OPERATION
TEXT REQUIREMENTS
TASK BUILD INFORMATION
PRT ERROR MESSAGES

C-1
C-1
C-2
C-3

INDEX

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

Index-1
FIGURES
Page

Figure

2-J
2-2

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

7-1
7-2
7-3

Results of COPY Command With and Without
/NV Specified
Sample Directories Before and After
Execution of /EN Command
Directory Listing Examples
Format of Protection Word
Use of Purge Switch
Results of Rename Command With and Without
/NV Specified
DEC Standard Cassette File Structure
DEC Standard Cassette File Label
DOS Directory Listings
RT Directory Listing
General Library File Format
Contents of Library Header
Formal of Ent.ry Point Table Element

viii

2-12
2-16
2-20
2-23
2-25
2-28
3-6
3..,.7

3-18
3-19
7-2
7-3

7-4

CONTENTS (Cont.)
FIGURES (Cont.)
Page
7-4
7-5
7-6
7-7
7-8
7-9
7-10
8-1
C-1

Format of Module Name Table Element
Module Header Format
Sample Files Used in LBR Examples
Output Library File After Execution of
Example 1
Output Library File After Execution of
Example 2
Output Library File After Execution of
Example 3
MACRO Listing Before and After Running
LBR with /SZ Switch
VFY Listing Sample Using the /LI Switch
PRT Send Data Buff er Format

7-4
7-5
7-20
7-21
7-21
7-22
7-26
8-13
C-2

TABLES
Page
Table

2-1
2-2
2-3
2-4
2-5
')

..J-.L

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

PIP Default File Specifiers
PIP Functions and Commands
PIP COPY and MERGE Command Subswitches
LIST Command Switches
PIP Error Codes
CT" •..,...; .+-,...'J,....""",...
'-\,,....J.1C::U
FLX Format r.1ode .JVV
FLX Transfer Mode Switches
FLX File Control Switches
DMP Switches
EDI Default File Specifiers
Line-by-Line vs. Block Mode
Basic EDI Commands
EDI Setup Commands
EDI Input/Output Commands
EDI Locative Commands
EDI Text Modification and Manipulation
Commands
EDI Close Operation Commands
Defaults in SLP File Specifiers
SLP Output Control Switches
SLP Edit Control Characters
Defaults in LBR File Specifiers
LBR File Option Switches
VFY Default File Specifiers
VFY Functions and Switches
VFY Error Codes
..L

2-2
2-6
2-10
2-18
2-41
3-12

3-13
3-15
4-3
5-4
5---6

5-14
5-24
5-32
5-35
5-41
5-50
6-3
6-5
6-7
7-6
7-7
8-4
8-4
8-17

PREFACE
O~l

MANUAL OBJECTIVES AND READER ASSUMPTIONS

The goal of this manual is to describe the utility programs supplied
with the RSX-llM and to provide all the information necessary to use
these programs. Within the RSX-llM utility program set, programs are
provided to perform the following functions:
File transfer
File conversion
File listing
Interactive context editing
Batch-oriented editing
Library maintenance
File structure verification
on Files-11 disk volumes.
It is assumed the reader is familiar with the PDP-11 computer, its
peripheral devices and the software supplied with the RSX-llM system.
Users of this manual should be also familiar with the RSX-llM Operator's
Procedure Manual which provides supporting information necessary for
the full utilization of the RSX-llM utilities.
This manual is organized and written as a reference manual and our
reader class assumptions require a system programmer level of expertise; thus, the manual will not contain definitions of data processing
terms and concepts familiar to this level of expertise.

0.2

STRUCTURE OF THE DOCUMENT

This document contains an intr0<1uctory chapter which provides general
operating information and a separate chapter for each utility program,
containing specific operating information.
Chapter 1 describes the procedures required for initiating the utility
programs, defines command formats and command strings, and identifies
system-wide conventions.

Chapter 2 details the Peripheral Interchange Utility Program (PIP), a
file transfer progrfiltn
Chapter 3 details the File Transfer Utility program (FLX), a file conversion program.
Chapter 4 describes the File Dump Utility program (DMP), a file listing
program.
Chapter 5 contains detailed information on the Line Text Editor Utility
program (EDI), an interactive context editing program.
Chapter 6 details the Source Language Input Utility program (SLP), a
batch-oriented editing program.
Chapter 7 describes the Librarian Utility Program, a library maintenance program.
Chapter 8 details the File Structure Verification Utility program
(VFY), a file structure verification program for Files-11 disk volumes.
Appendix A contains a command summary for each utility.
Appendix B contains sample LBR and DMP listings, and EDI examples.
Appendix C contains a description of the print spooler task.
Throughout this manual the following conventions are used to describe
examples and command string formats:
a._)indicates a carriage return
b.G}indicates ALTMode or ESCape key
c. In examples, messages which are typed out by the system,
are underlined.
d. In all cases, except where [ UIC ] is specified, brackets
signify optional parameters.
e. ~ indicates a space.
Additional conventions and definitions are given in Chapter 1.

xii

0.3

ASSOCIATED DOCUMENTS

Other manuals closely allied to the purposes of this document are
described briefly in the RSX-llM/RSX-llS Documentation Directory,
Order No. DEC-11-0MUGA-B-D. The Documentation Directory defines the
intended readership of each manual in the RSX-llM/RSX-llS set and
provides a brief synopsis of each manual's contents.

xiii

CHAPTER 1
INTRODUCTION

1.1

RSX-llM UTILITY PROGRAMS

RSX-llM provides the user with a comprehensive set of utility
programs. The utility programs and their identifiers are as follows:
•

Peripheral Interchange Utility Program (PIP)
PIP is a file transfer program that provides the user with
facilities for copying, renaming, listing, deleting, and
unlocking files.

•

File Transfer Utility Program (FLX)
FLX is a file conversion program that provides the user with
a facility for transferring DOS-11 or RT-11 files to Files-11
volumes and vice versa.

•

File Dump Utility Program (DMP)
DMP is a file listing program that provides the user with a
facility for obtaining a printed copy of the contents of
files.

•

Line Text Editor Utility Program (EDI)
EDI is an interactive context editing program that provides
the user with a facility for creating and maintaining text
files.

•

Source Language Input Utility Program (SLP)
SLP is a batch-oriented editing program that provides the
user with a facility for creating and maintaining text files
on disk.

•

Librarian Utility Program (LBR)
LBR is a library maintenance program that provides the user
with a facility for creating, modifying, updating, listing,
and maintaining library files.

•

File Structure Verification Utility Program (VFY)
VFY is a disk verification program that provides the user
with a facility for verifying the consistency and validity of
the file structure on a Files-11 volume.

1-1

INTRODUCTION
1.2

INITIATING RSX-llM UTILITIES

There are six methods for initiating RSX-llM utility programs.
These
methods are described below. The first four methods apply when the
utility program is installed and ready to be executed. The remaining
two cause the utility program to be installed, executed, and then
removed on exit.
NOTE
The RSX-llM systems provided in the
distribution
kit
require
that all
utilities be initiated via methods five
and six. However, using the INSTALL MCR
Command
(see
RSX-llM·
Operator's
Procedures
Manual),
the
user
can
permanently install the utility programs
in his system and thus make the first
four methods of initiation available.

1.2.1

Initiation of Installed Utilities
Method 1.

Lutilityname command string_)
loads, executes the specified command(s), and exits.

Method 2.

Lutil i tyname..J
responds with the following prompt.
utilityname>
At this point, the user enters the utility
string to execute the desired function.

command

When the utility has completed processing a command
string it again issues a prompt. The user can either
enter another command string or enter a CTRL/Z* to
terminate the utility.
Method 3.

2.RUN •.• util i tyname..)
responds with the following prompt:
util i tyname>
At this point, the user enters the utility
string to execute the desired function.

* CTRL/Z is entered by holding down the CTRL key while
depressing the z key.

1-2

command

simultaneously

INTRODUCTION
When the utility has completed processing a command
string, it again issues a prompt.
The user can
either enter another command string or enter CTRL/Z
to terminate the utility.
Method 4.

~RUN

... util i tyname/UIC= [group ,member]__)

The UIC under which the utility executes is explicity
specified for this run only.
Normally, utility
programs execute with the default UIC associated with
the initiating terminal
(see SET /UIC MCR command
described in RSX-llM Operator's Procedures Manual).
When the utility is loaded, it issues the following
prompt:
util i tyname>
At this point! the user enters the utility
string to execute the desired function.

command

When the utility has completed processing a comman~
string, it again issues a prompt.
The user can
either enter another command string or enter CTRL/Z
to terminate the utility.
NOTE
Methods 3 and 4 should not
multi-user RSX-llM systems.

1.2.2

used

Initiation of Uninstalled Utilities
Method 5.

>RUN $utilitvname_)
causes the utility to be installed and loaded, and to
issue the following prompt:
util i tyname>
At this point, the user enters the utility
string to execute the desired function.

command

When the utility has completed processing a command
string, it again issues a prompt. The user either
enters another command string to execute the desired
function or enters CTRL/Z to cause the utility to
exit. After exiting, the utility is removed from the
system.
Method 6.

~RUN

$utilityname/UIC=[group,member]_.J

1-3

INTRODUCTION
The UIC under which the utility executes is explicity
specified for this run only.
Normally, utility
programs execute with the default UIC associated with
the initiating terminal (See SET /UIC MCR command
described in the RSX-llM
Operator's
Procedures
Manual).
When the utility is installed and loaded,
it issues the following prompt:
utilityname>
At this point, the user enters the utility
string to execute the desired function.

command

1.3

RSX-llM UTILITY COMMAND STRINGS

Commands to RSX-llM utilities are expressed in the following format:
outflespc-1, ..• ,outflespc-n=inflespc-l, ... ,inflespc-n
or
@indirect
where:
outflespc

is an output file specifier.

inflespc

is an input file specifier.
Any number of file specifiers is possible, the actual
number being determined by the task which will use
the file command string. In no case, however, can
the total length of the command string exceed the
maximum line length (80 characters).
Each file specifier (whether input or output) has the
following format:
dev: [g,m]filename.typ;ver/sw ... /sw
where:
dev:

is the physical device on which the
volume containing the desired file is
mounted; for example, DKO:
or DTl:.
The name consists of 2 ASCII characters

1-4

INTRODUCTION
followed by an optional 1- or 2-digit
(octal) unit number and a colon.
[g,m]

is the user identification code (UIC),
consisting of a group number and a
member number, associated with the user
file directory (UFO} containing the
desired file.

filename

is the name of the file. In RSX-llM, a
filename can be up to nine alphanumeric
characters in length.
Filename and
type are always separated by a period
(

.) .

typ

is a means of distinguishing among
forms of one file.
For example, a
source FORTRAN program might be named
COMP.FTN,
while
the
object
code
associated with that program might be
called COMP.OBJ. File type and version
always are separated by a semicolon
(;).
File
type may be up to 3
alphanumeric characters.

ver

is
an
octal
number
used
to
differentiate among versions of a file.
For example, if a file is first created
using the editor, it is assigned a
version number of 1. If the file is
subsequently opened for editing, the
editor keeps the original file for
backup and creates a new file with the
same filename and type, but with a
version number of 2. Version is in the
range 0 thru 77777(8).

/sw

is a 2-character ASCII name identifying
a switch option. The switch itself may
have three forms.
If
the
switch
designator, for example, is SW, then:
/SW
/-SW,
/NOSW

sets the switch
action;
negates
the
switch action,
and
negates
also
the
switch
action.

In addition, the switch identifier may
be followed by any number of values.
The permitted values are ASCII strings,
octal numbers, and decimal numbers.

1-5

INTRODUCTION
The default for a numerical value is
octal.
Decimal values are terminated
by a decimal point. Values preceded by
a pound sign (#) are octal; the octal
option is included for use as explicit
documentation, since a numeric value
not terminated with a decimal point is
an octal value. Finally, any numeric
value may be preceded by a + or - sign;
plus is the default.
If explicit octal (#) is used, the sign
(if the sign is used) must precede the
# (pound)
sign.
The following are
valid switch specifications:
/SW:27:MAP:29.

/-SW
/NOSW:-#SO:SWITCH
The number of permissible values and
the switch interpretations themselves
depend entirely on the particular task
to which they are directed.
@indirect

is an indirect command
following format:

file

specifier

the

used

@dev: [g,m]filename.typ;ver

1.3.1

Command Format Conventions

Throughout this manual, the
presenting command formats.
[ ]

following

conventions

are

Entries within square brackets indicate optional items.
The use of such items may be for readability, e.g.,
BL[OCK]; or to denote repetition, e.g., [n].
EXCEPTION

~~--~-

[g,m]

The square brackets
are
REQUIRED
when
specifying a User's Identification Code.

One or more spaces.
Underlined characters denote
system.

those

displayed

ABC

Characters in upper case indicate constants,
items the user must enter exactly as presented.

filespec

A file specifier, i.e., dev:[g,m]filename.type;ver

1-6

the
i.e.,

INTRODUCTION

1.4

dev

A device specifier, i.e., device name and unit
such as DKl:.

type

The file type, such as .CMD, .OBJ, or .OLB.

ver

The version number of the file.

[g ,m]

The User's Identification Code composed of two octal
numbers separated by a comma and surrounded by square
brackets. The left-hand number is the user's group
number;
the right-hand number is the user's member
number.

[uic]

Also used to indicate the User's Identification Code;
[uic] and [g ,m] are used intercha.ngeably in the RSX-llM
documentation.

Indicates an indirect file specifier follows.

Indicates that a command switch follows.
If a minus
sign (-) or the letters NO are placed between the slash
(/) and the switch name, it denotes th~t the switch
action is negated.

number,

INDIRECT FILES

An indirect file is a sequential file containing a list of commands
exclusive
to,
and interpretable by a single task, usually a
system-supplied component of RSX-llM, such as MACR0-11, the Task
Builder or a utility program.
Indirect files are initiated by replacing the file specification
command string required by a task with a filename string preceded by
an at sign (@).
example; to initiate a file of MACR0-11 commands, the
input:

Fo~

user

would

>MAC
After MACR0-11 is initiated, it accesses the file INPT.CMD for all its
commands.
An indirect file may contain any command interpretable by the task
which it is directed, but no others.
Indirect files may not contain indirect file references
one level of command file indirection is permitted).

(i.e.,

to
only

A complete description of indirect files for use with MCR is contained
in the RSX-llM Operator's Procedures Manual.

1-7

INTRODUCTION
NOTES

1.5

The default file type
command files is .CMD.

for

indirect

Other default
values
for
command file specifiers are:

indirect

dev

SYO:

[uic]

The UIC under which
the specified utility
is running.

filename

No default.

type

.CMD

ver

Latest version

SYSTEM-WIDE CONVENTIONS

There are a number of system-wide conventions of which the user should
be aware.
1.

The use of NO is the equivalent of a minus
specifying the negation of a switch, e.g.,

sign

(-)

The alphanumeric file names and types are composed
letters A through Z and the numbers 0 through 9.

the

All numbers followed by a period (.) denote decimal
others are interpreted as octal numbers.

numbers;

/NOSP is equivalent to /-SP

I-8

CHAPTER 2
PERIPHERAL INTERCHANGE PROGRAM (PIP)

2.1

INTRODUCTION TO PIP

The Peripheral Interchange Program (PIP) is an RSX-llM file utility
program that transfers data files from one standard Files-11 device to
another. PIP also performs simple control functions.
The major
functions performed by PIP are:

2.2

•

Copy files from one device to another

•

Delete files

•

Rename files

•

List file directories

•

Set the default device and UIC for PIP

•

Unlock files

INITIATING PIP

All RSX-llM utility programs can be initiated in several ways.
methods are described in Section 1.2. The methods for PIP are:

These

2PIP~

>PIP command

string~

>RUN ... PIP__)
~RUN

... PIP/UIC=[group,member]_J

>RUN $PIP__}
>RUN $PIP/UIC=[group,member]_.)

2.3

PIP COMMAND STRING

All commands to PIP are issued by entering PIP command strings through
the initiating terminal.
The format of the elements which comprise
PIP command strings differs for each command. Therefore, the command
string formats will be individually described in their respective
sections.

2-1

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.3.1

Lists of File Specifiers

All of the commands, except /IDENTIFY and /DEFAULT, accept a list of
file specifiers on which to operate. In all cases, the lists have the
property that the device, directory, filename, and type are propagated
down the list to provide defaults for missing fields in subsequent
file specifiers.

2.3.2

Defaults in File Specifiers

If any of the elements in the file specifier, except the filename and
type, are omitted, PIP uses a default. These default values are
listed in Table 2-1.
Table 2-1
PIP Default File Specifiers
Element

Default Value

dev:

SYO: -- For first file specifier, the unit on
which the system disk is mounted, or the default
specified by the PIP /DF switch;
otherwise, the
same as specified or assumed for previous file
specifier.

[uic]

For first file specifier, the default UIC under
which PIP is running (usually (200,200]), the UIC
specified by the MCR SET command, or the default
specified by the PIP /DF switch; otherwise, the
same as specified or assumed for previous file
specifier.

filename

No default for the first file specifier. For the
second
through
n file specifiers, the last
previously specified filename. An asterisk (wild
card) specification is valid (see Section 2.3.4).

.typ

No default for the first file specifier. For the
second
through
n file specifiers, the last
previously specified .typ.
An asterisk (wild
card) specification is valid (see Section 2.3.4).

;version

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

2-2

PERIPHERAL INTERCHANGE PROGRAM (PIP)
NOTE
A version number of ;-1 may be used to
specify the oldest version of a file. An
explicit version of ;O ~r
may be
specified
to signify the most recent
version.

2.3.3

PIP Command Switches and Subswitches

A switch. specification consists of a slash (/}
followed by a
2-character switch name, and is optionally followed by a subswitch
name separated from the switch code by a slash. The subswitch itself
can have arguments which are separated from the subswitch by a colon
(:). If more than one subswitch is used, each is preceded by a slash.
When present, a switch must follow any file or UIC specification;
that is, a switch cannot appear before the filename, type, version, or
UIC of the file on which the switch is to operate.
However, some
switches may be specified without any file specification at all.
Command switches are global, that is, they may be specified once for
an entire list of file specifiers, and may appear on either side of
the equal sign. For example:
stringl,string2,string3/DE
The /DE switch applies to all of the strings;
the file specifiers would be deleted.

the files described

Switch arguments are specified as octal, decimal, or alphabetic
characters, depending on the switch. These values are discussed in
detail in the sections which discuss the individual PIP commands.
Command subswitches are local, that is, they only apply to the file
specifier which immediately precedes them. In the following example,
the NEW VERSION subswitch is applied to a particular file
(ASDG.MAC).
(The NEW VERSION subswitch is used with the RENAME command in this
example) :
*.SMP=PRTX.QRT,ASDG.MAC/NV,KG.BAC/RE
In this example, files PRTX.QRT and KG.BAC are renamed, but they
maintain their associated version numbers.
File ASDG.MAC is also
renamed, but the version number is forced to one greater than the
latest version of file ASDG.SMP.
NOTE
If a subswitch is applied to the first
file specifier in a collection of file
specifiers, and no command switch has
been specified, PIP assumes that the
command with which the subswitch is
associated is the one requested, and the
entire list of files is treated as
though
the
command
were
actually

2-3

PERIPHERAL INTERCHANGE PROGRAM (PIP)
specified.
Example:
PIP>FILE1/GR:R/WO,FILE2/GR:RW._}
This command is equivalent to:
PIP>FILE1/GR:R/WO,FILE2/GR:RW/PR_}
This example would result in the
following file protection:

2.3.4

a. FILEl

SYSTEM
MEMBER
GROUP
WORLD

Unchanged
Unchanged
Read access
No access

b. FILE2

SYSTEM
MEMBER
GROUP
WORLD

Unchanged
Unchanged
Read/write access
Unchanged

Asterisk Convention - Wild Cards

PIP allows wild cards to be specified by means of an asterisk
character in the file specifier.
The * character in one or more
fields of a file specifier stands for "all"; e.g., all files, types
or all versions. Wild card use, however, is restricted in some cases.
Sections 2.3.4.1 and 2.3.4.2 describe the allowable
uses
and
restrictions on wild cards for input and output files.

2.3.4.1 Wild Cards in Output File Specifiers - Use of wild cards in
the output file specifiers is very restricted. In the following types
of command actions, the output file specifier may not have any wild
cards:
•

Copying a single file

•

Concatenating files to a specified file

•

Appending to an existing file

•

Updating (rewriting) an existing file

•

Listing a directory

When a list of files is to be copied, the
*.*;* or default.

output

specifier

must

For the RENAME and ENTER commands, the output specifier may have wild
cards mixed with specified fields. Furthermore, a wild card field may
optionally be left null. In either case, the equivalent field of the
input file specifier is used.
In all

cases

where

wild

cards

are

2-4

allowed

the

output

file

PERIPHERAL INTERCHANGE PROGRAM (PIP)
specifier, the wild card UIC form [*,*] (but not [n,*] or [*,n]) may
be used to indicate that the output UIC is to be the same as the input
UIC.

2.3.4.2 Wild Cards in Input Specifiers - The following
features are provided for input file specifiers:

•
•

wild

card

*.*;* means all versions of all files .
*.DAT;* means all versions of all files of type DAT .

•

TEST.*;* means all versions and all
TEST.

types

files

named

•
•

TEST.DAT;* means all versions of file TEST.DAT .

•

*.DAT means the most recent version of all files
DAT.

with

type

•

TEST.* means the most recent version of all types
named TEST.

files

•

TEST.DAT means the most recent version of TEST.DAT .

*·* means the most recent version of all files .

The following wild card UIC features are also provided:
•

[*,*] means all group, member number combinations (each from
1 to 377 octal);

2.3.5

•

[nl,*] means all member numbers under group nl;

•

[*,n2] means all group numbers for member n2.

and

File Identification Option

Wherever a file specifier is used to describe an already existing
file, the /FI (file identification) option can be used. This option
allows the user to specify the file he wants to access by specifying
the device, unit, and its unique file identification number. This
file identification is assigned to the file at file creation time by
the RSX-llM system. Although the file identification number of a file
is normally invisible to the user, it can be obtained by using the PIP
FULL LIST command /FU.
(Section 2.4.8 contains a description of the
LIST command). This will give the user a full or complete directory
listing of his files. The full list of his directory contains, among
other pertinent information about the file,
its
unique
file
identification number.
The user need only specify this number using
the /FI option to access his files. The /FI option is specified in
the following format:
/FI:nl:n2
where nl and n2 are the file number and file sequence
file, respectively.

2-5

number

the

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.4

PIP COMMANDS

PIP commands are in the form of switches appended to optional file
specifiers.
Command switches and functions are summarized in Table
2-2.
NOTE
Only one of the PIP command switches
listed in Table 2-2 can appear on a
command line. More than one subswitch
on a line is legal, as described in the
following command descriptions.
Table 2-2
PIP Functions and Commands
Command

Switch

Append

/AP

Copy

No switch

Fune ti on
Add files to the end of an existing file.
Copy a file.

Default

/DF

Change PIP's default device or UIC.

Delete

/DE

Delete one or more files.

Enter

/EN

Enter a synonym for a file in
file.

directory

Free

/FR

Print out
volume.

specified

Identify

/ID

Identify the version of PIP being used.

List

/LI

List a directory file.

Merge

/ME

Concatenate two
file.

Protect

/PR

Change the protection of a file.

Purge

/PU:n

Delete obsolete version(s) of a file.

Remove

/RM

Remove a file entry from a directory.

Rename

/RE

Change the name of a file.

Spool

/SP

Specify a list of files to be
deleted.

Unlock

/UN

Unlock a file.

Update

/UP

Rewrite an existing file.

2-6

available

space

files

into

printed

one

and

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.4.1

APPEND Command (/AP)

FUNCTION
The APPEND command opens an
file(s) onto the end of it.

existing

file

and

appends

the

input

FORMAT
outfile=infile-l[,infile-2, ... ,infile-n]/AP[/FO]
where:
outfile

is the output file specifier in the format:
dev: [uic]filename.typ;ver[/AP] [/FO]
NOTES

inf ile

No wild card specifiers are
the output file specifier.

allowed

The file type and record attributes
taken from the existing file.

are

No defaults are allowed
name or file type.

file

for

the

is the input file specifier in the format:
dev:[uic]filename.typ;ver/AP
NOTE
If filename, file type, and version
null, then *.*;* is the default.

are

/AP

is the APPEND switch

/FO

is the Set File
Ownership
subswitch
which
specifies that the owning UIC of the output file
corresponds to the directory into which the file
was
entered.
If the /FO subswitch is not
specified, the owning UIC of the new file is the
UIC under which PIP is running, regardless of the
directory into which the files were entered
(see
COPY command for examples using /FO).

EXAMPLE
PIP>DKl:FILEl.DAT;l=FILE2.DAT;l,FILE3.DAT;l,FILE4.DAT;l/AP_J
FILEl.DAT;l
on DKl: will be
opened, and the contents of
FILE2.DAT;l, FILE3.DAT;l and FILE4.DAT;l will be appended to it.

2-7

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.4.2

COPY Command (No Switch) and MERGE Command (/ME)

FUNCTION
The COPY command is used to create a copy of a file on the same or
another device.
The COPY command is the PIP default command, if an
implicit output file specifier is used and no command switch is
specified.
When an explicit output file specifier and only one input
file specifier are contained in a command line, the PIP default
command is also COPY. The MERGE command is used to create a new file
from two or more existing files.
If an explicit output file specifier
is used and more than one input file is named without an appended
switch, the MERGE command becomes the PIP default command.
FORMAT
outf ile

infile-l[,infile-2, .•• ,infile-n]

where:
outf ile

is the output file specifier in the format:
dev: [uic]filename.type;ver/subswitch
NOTE
If the output filename, file type, and
version are either null or *.*;*, the
input filename, file type, and version
are
preserved.
See
/NV
and /SU
subswitches. If any of the output file
name, file type, or version fields is
present, none may be wild and there may
be only one input file specifier for a
COPY command.

infile

is the input file specifier in the format:
dev: [uic]filename.type;ver/subswitch
NOTE
If the filename, file type, and version
fields are all null, then *.*;* is the
default.

2-8

PERIPHERAL INTERCHANGE PROGRAM (PIP)
EXAMPLES
1.

PIP>DKl: SAMP. DAT=DK2: TEST. DAT__)
Copy the latest version of file TEST.DAT from DK2:
as SAMP.DAT.

DKO:

PIP>LP:=*.LST__}
Copy the latest version of all files with a type of
the line printer.

DKl:

PIP>DKl: [*,*]=DKO: [11,*]_.)
Copy all files from all members in group number
to DKl:, preserving the UIC.

.LST

PIP>DKl:SAMP.DAT=DK2:TEST.DAT;l,NEW.DAT;2/ME_.)
Concatenate version l of file TEST.DAT and version 2 of
NEW.DAT from DK2: generating file SAMP.DAT on DKl.

and

TESTPROG.OBJ

FIP>DKl:=DKO:*.DAT;*__J
Copy all versions of all of the files of the
DKO: to DKl: .

file

PI P>DKl: =TESTPROG. MAC,. OBJ _J
Copy the latest versions of TESTPROG.MAC
from the system device to DKl:.

type

DAT

from

PIP>DT0:=[200,10]*.*;*_.)
Copy all files under [200,10] from system device to DTO:.

PIP>DPO: [200,lO]=DTO:*.*_J
Copy all of user's files from DTO:

to DPO: [200,10].

The optional subswitches described in Table 2-3 are used with both the

rnov
"'"'L
.&..

~nA

"""'.&.&'-A

MPD~P

J.."J..LLL'\.V.L.1

nnmm~nA~

\,,....VlLULLt.l .. J.U ...:> e

2-9

PERIPHERAL INTERCHANGE PROGRAM (PIP)
Table 2-3
PIP COPY and MERGE Command Subswitches
Description

Subswitch

NOTE
All of the subswitches below can appear on
either the output or input file specifier.
If the subswitch is placed on an input
file specifier, it pertains only to that
file. If the subswitch is placed on the
output file specifier, it pertains to the
entire list of input specifiers.
/BL: n [ . ]

Blocks Allocated - This switch specifies the number
of contiguous blocks to allocate to the output file,
where n is an octal or decimal value (decimal values
must be followed by a decimal point). The /BL:n
switch is useful for copying a ~ontiguous file and
changing its size.

/CO

Contiguous Output - This switch
file to be contiguous.

/-CO

Noncontiguous Output - This switch causes the output
file to be noncontiguous.

causes

the

output

NOTE
If none of the
above
subswitches
is
specified, PIP defaults to the size and
attributes of the input file.

/FO

Set File Ownership - This subswitch specifies that
the owning UIC of the output file corresponds to the
directory into which the file was entered.
If the
/FO switch is not specified, the owning UIC of all
new files is the UIC under which PIP is running,
regardless of the directory in which the files were
entered. This subswitch can be used with both COPY
and MERGE commands.
If PIP is running under the UIC [1,1], the command:
DKO: [200,200]=DK1: [200,220]TEST.DAT
results in a new file being created in the [200,200]
directory on DKO: and the file being owned by UIC
[1,1].
However, the command:
DKO: [200,200]=DK1: [200,220]TEST.DAT/FO

2-10

PERIPHERAL INTERCHANGE PROGRAM (PIP}
Table 2-3 (Cont.}
PIP COPY and MERGE Command Subswitches

I Subswi tch

Description
results in the output
[200,200].

/SU

file

being

owned

UIC

Supersede - This switch allows the user to copy a
file of which the name, type, and version of the
file already exists in the specified
output
directory file.
The old file is deleted and
replaced with the specified input file.
New Version - This switch allows the user to force
the output version number of the file being copied
to the latest version plus one of the file already
in the output directory.
If the file does not
already exist in the output directory, a version
of one is assigned. The results which occur when
the /NV switch is specified are depicted in Figure
2-1.

Examples Using /FO Subswitch
NOTE
When using the /FO subswitch, PIP must
be running under a UIC that has write
access to all output directories.
1.

PIP>DKl: [*,*]/FO=DPO: [13,10], [32,10], [34,10]_.)
Copy all the files from the specified input directories to
the corresponding directories of DKl:, making the file owners
agree with the output directories.

PIP>DKl: [*:*J=DKO: f*,10]*.MAC/FO-==_)
Copy all the .MAC files from all group numbers with member
number 10 to DKl:, preserving the directory UIC and setting
the file owner for each file to the directory UIC.

2-11

PERIPHERAL INTERCHANGE PROGRAM (PIP)

Directories Before COPY
INPUT DIRECTOFY
c2.n, 2.in J

OUTPUT DIRECTORY

RICK.DAT;!

RICK.DAT;2

[l~~, l~~J

RICK.DAT;4

Directories After COPY Without /NV Switch Set
(version number preserved)
INPUT DIRECTORY
[ 2,01, 2,Ll]

OUTPUT DIRECTORY
[ 1,0,0, 1,0,0]

RICK.DAT;!

RICK.DAT;2
RICK.DAT;4
RICK.DAT;!

The command used was:
DKl:[l,6,0,1,0,0] =

DK2:[2~1,2~l]RICK.DAT;~

Directories After COPY With /NV Switch Set
INPUT DIRECTORY
[2~1,2~Ll

OUTPUT DIRECTORY
c1n,1nJ

RICK.DAT;!

RICK.DAT;2
RICK.DAT;4
RICK.DAT;5

The command used was:
DKl:[l~~,l~~]

= DK1:[2~1,2~l]RICK.DAT;l/N::>

NOTE
The version specified with the /NV subswitch must be explicit or default; no
wild cards allowed.

Figure 2-1
Results of COPY Comma~d With and Without /NV Specified

2.4.3

DEFAULT Command (/DF)

FUNCTION
The DEFAULT command provides the user with a facility
default device or UIC.

change

the

The normal default UIC is the UIC under which PIP is currently
running;
that is, the UIC specified in the last MCR SET/UIC command,
or that specified with the /UIC switch in a RUN .•. PIP command.

2-12

PERIPHERAL INTERCHANGE PROGRAM (PIP)
NOTE
The /DF command
UIC.
It does
which PIP is
circumvent file

alters only the default
not affect the UIC under
running, nor does
it
protection.

The normal default device for PIP is SYO:.
FORMAT
dev: [group,member]/DF
where:
dev:

if specified, is the new default device to be
applied to subsequent PIP command strings.

[group,member]

if specified, is the new default UIC to be
applied to subsequent PIP command strings.

/DF

is the DEFAULT command switch.

EXAMPLES
1.

PIP>[27,27]/DF_}
Set the default UIC to [27,27].

PIP>DKl:/DF_}
Set the default device to DK!:.

PIP>DKl: [27,27]/DF./
Set the default device to DKl:, and the default UIC to
[27,27].

2.4.4

DELETE Command (/DE)

FUNCTION
The DELETE command provides the user with a facility to delete files.
FORMAT
infile-l[,infile-2, ... ,infile-n]/DE
where:
inf ile

is the file specifier for the file to
in the format:

dev: [uic]filename.type;version/switch

2-13

deleted

PERIPHERAL INTERCHANGE PROGRAM (PIP)
NOTES
1.

A version number must always be specified
when using the DELETE command switch.

When deleting files, a version number of
;-1 may be used to specify the oldest
version of a file. An explicit version of
;O or
may be specified to signify the
most recent version.
Examples
a.

PIP>TEST. DAT; -1/DE ~_)
Delete the oldest version
of file TEST.DAT

PIP>TEST1.DAT;O,TEST2.DAT;/DE~

Delete the latest version of
files TESTl.DAT and TEST2.D~T.
Wild cards in the filename or file type
fields are illegal when a version of
;-1,
;O, ~r ; is specified.

/DE

The file specifier must be issued because
a null filename, file type, and version
does not default to *.*;*.

The input file specifier can take all the
usual forms, including wild cards, even in
the group, member number [UIC]. The only
special requirement is that the version
number field must always be explicit or
"*"
It cannot be defaulted to the most
recent version if wild cards are used.

is the DELETE command switch.

EXAMPLES
1.

PIP>TEST. DAT; 5/DE ~
Delete version 5 of the file
directory on the default device.

the

default

TEST.DAT

the

default

PIP>TEST.DAT;l,;2/DE~_j

Delete versions 1 and 2 of file
directory on the default device.
3.

TEST.DAT

PIP>*.OBJ;*,*.TMP;*/DE~

Delete all versions of all files of the type OBJ and TMP from
the current default directory on the default device.

2-14

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.4.5

ENTER Command (/EN)

FUNCTION
Tne ~NT~H command prov1aes ~ne facility to enter a synonym for a file
in a directory or directories, thus allowing the file to be Recessed
by more than one name. Also provided is a subswitch, New Version
(/NV), which allows the user to force the version number of the file
being entered into the directory to a number one greater than the
latest version for the file.
FORMAT
outfile=infile-l[,infile-2, •.. ,infile-n]/EN[/NV]
where~

outf ile

is the file specifier to be given to the new
directory entry. The output file specifier has a
special property in that the filename, type, and
version are individually allowed to be explicit,
wild card (*) or defaulted (null). A name, type,
or version field that is either wild card (*) or
defaulted
(null) means that the corresponding
~ield of the input file is to be used.

in file

is the file specifier for the input
format:

file

the

dev: [uic]filename.type~ver/sw[/subsw]
If no device is specified, in either the input or
output file specifier, then the current default
device is assumed to be the default device.
If a
device is specified on either the input or output
side, that device is defaulted for the other side.
If both the input side and the output side
explicitly reference different devices, PIP will
flag this as an error and request that the line be
reentered.
The default input file specifier is
/EN

is the ENTER command switch.

/NV

is the New Version subswitch.
NOTE
The /NV subswitch may appear on either
side of the equal sign. If it appears
on the output side, all of the files
being
entered will be forced to a
version number one greater than the
latest version of the file.
If it
appears on the input side, only files
that have the /NV subswitch appended to
them will be forced to a number one
greater than the latest version.

2-15

* .*·*
' .

PERIPHERAL INTERCHANGE PROGRAM (PIP)
EXAMPLE
PIP>[l01,10l]TWIG/EN=[200,200]RICK.DAT;l_.}
Before
DIRECTORY [101,101]

DIRECTORY [200,200]

JEN.OBJ;2

RICK.DAT;l

LAU.OBJ;3
After
DIRECTORY [200,200]

DIRECTORY (101,101]

RICK.DAT;l

JEN.OBJ;2
LAU.OBJ;3
TWIG.DAT;l

NOTE
The directory items for RICK.DAT;l and
TWIG.DAT;l both reference the same file.

Figure 2-2
Sample Directories Before and After Execution of /EN Command

2.4.6

FREE Command (/FR)

FUNCTION
The FREE command provides the user with the ability to print
available space on a specified volume.

out

the

FORMAT
dev:/FR
The output from the /FR command is shown below.
dev:

2.4.7

HAS nnnn.

BLOCKS FREE, nnnn.

BLOCKS USED OUT OF nnnn.

IDENTIFY Command (/ID)

FUNCTION
The IDENTIFY command allows the user to identify the
being used.

2-16

version

PIP

PERIPHERAL INTERCHANGE PROGRAM (PIP)
FORMAT
/ID

NOTE
When this command is
invoked,
the
version number is listed on the input
terminal as follows:
PIP VERSION Mvvee
where:
vv is the version number.
ee is the edit number.
EXAMPLE
PIP>/ID_)

PIP VERSION Ml301

2.4.8

LIST Command (/LI)

FUNCTION
The LIST command provides the user with the facility to list one or
more directories.
Also provided are three alternate mode switches
(/BR, /FU and /TB) which allow the user to specify a choice of
directory listing formats. These switches are described in Table 2-4.
FORMAT
[listfile]=infile-l[,infile-2, ..• ,infile7n]/LI [/switch]
where:
listfile

is the listing file specifier in the format:
dev: [uic]filename.type;ver
NOTE
I f listfile
is
defaults to TI: .

inf ile

not

specified,

is the input file specifier in the format:
dev: [uic]filename.typ;ver/switch
NOTE

The default for this file is * *·*
'

2-17

PERIPHERAL INTERCHANGE PROGRAM (PIP)
/LI

is the LIST command switch.
This switch
the following information to be listed.
1.

filename.type;version

number of blocks used (decimal)

3•

f i l e code :
non-contiguous
contiguous
locked

(null)

c
L

/switch

causes

creation date and time

are the alternate mode switches
command described in Table 2-4.

the

LIST

Table 2-4
LIST Command Switches
Description

Switch
/BR

This switch specifies the brief form
of
directory listing.
This switch will cause
only the filename, type, and version to be
listed.

/FU[:n]

This switch specifies the full
directory
format.
This switch has an optional modifier
which allows the specification of the number
of characters to be printed on a line.
If specified, n is the number of characters
per line.
If not specified, the number is
defaulted to (80.). This switch causes the
following information to be listed:
1.

filename. type; version

file identification
format:

number

the

(file number, file sequence number)
3.

number of

blocks

used/allocated

10)

file code
(null) = non-contiguous
C = contiguous
L = locked

creation date and time

2-18

(base

PERIPHERAL INTERCHANGE PROGRAM (PIP}
Table 2-4 (Cont.)
LIST Command Switches
Description

Switch
6.

owner UIC and
format:

file

protection

the

[group ,member]
[system,owner,group,world]
NOTE
These protection
fields
contain the values R,W,E,D.

can

where:
R
W
E

7.
8.

Read access permitted
Write access permitted
Extend privilege permitted
D
Delete privilege permitted
date and
time
of the last update
pius the number of revisions.
summary line:
The number of blocks used, the number of
blocks allocated, and the number of
files are printed.
The summary line is not printed when the
/BR switch is specified.

/TB

This switch specifies that the user wants only the
summary line in the following format.
TOTAL OF nnnn./mmmm.

BLOCKS IN xxxx.

FILES

where:
nnnn

blocks used

mmmm

blocks allocated

xx xx

number of files
NOTE

Figure 2-3 contains
sample
directory
listings in the various formats.

2-19

PERIPHERAL INTERCHANGE PROGRAM (PIP)
Total Blocks (/TB) Format

STORAGE USED/ALLOCATED FOR DIRECTORY DK2:C200r270J
15-JUL-75 15:46
TOTAL OF 145./150. DLOCKS IN 5. FILES

Brief {/BR) Format

DIRECTORY DK2:c200,270J
CKTST.HAC;6
IOTST.HACf4
IOTST.TSK;1
CKTST.TSK;1
CKTST.HAC;7

Standard (/LI) Format

DIRECTORY DK2:C200r270J
15-JUL-75 15:46
CKTST.HAC;6
IOTST.HAC;4
IOTST. TSKH
CKTST.TSKfl
CKTST.HACP7

4.
69.

69.

15-JUL-75 15:39
15-JUL-75 15:39
c 15-JUL-75 15:39
c 15-JUL-75 15:40
L 15-JUL-75 15:40

TOTAL OF 145. BLOCKS IN S. FILES

Full {/FU) Format

DIRECTORY DK2lC200r270J
lS-JUL-75 15:46
(10r10)
C200r270JCRWEDrRWEDrRWEDrRJ
IOTST.HAc;4
<11r11)
C200,270J[RWED•RWED,RWEDrRJ
IOTST.TSK;l
(7,12)
C200•270J[RWED•RWEDrRWEDrRJ
CKTST.TSK;1
<12,13>
[200r270JCRWEDrRWEDrRWEDrRJ
CKTST.MACP7
<13r14)
C200,270JCRWED,RWEDrRWED,RJ
CKTST~HACf6

3./3.

15-JUL-75 15S39

4./4.

15-JUL-75 1:5: 39

69./69.

15-JUL-75 15:39

69.169.

15-JUL-75 15:40

o.;s.

L 15-JUL-75 15:40

TOTAL OF 145./150. BLOCKS IN S. FILES
Figure 2-3
Directory Listing Examples

2-20

PERIPHERAL INTERCHANGE PROGRAM (PIP)
EXAMPLES
PIP>/LI.)

Equivalent to TI:=/LI
where the directory of the current default device and UIC
listed.
2.

PIP>LP:=[*,*]/FU:l32._.)
List, on
listing) ,
device.

the
all

line printer,
in full
of the directories on

format
(132-column
the current default

PIP>TI:=TEST.DAT/FU.)
List on TI:
the full directory listing {80-column)
for
the
latest version of TEST.DAT on the current default device and
directory.

PIP>JUL13.DIR=[200,200]*.*/LI__}
List the latest version of all files in directory
[200,200]
on the current default device to file JUL13.DIR in the
default directory on the default device.

PIP>LP:=[ll,*]*.CMD;*/LI_J
List, on the line printer, all versions of all files of
.CMD in all directories in group 11.

type

PIP>LP:/BR=[ll,11]*.CMD;*,*.DAT;*,*.MAC;l.)
List, on the line printer, in brief format, aii versions of
all files with a
type of .CMD;
all versions of all files
with a type of .DAT; and all files of type MAC with a
version number of 1. These files all reside in the directory
[11,11] on the current default device.

2.4.9

PROTECT Command (/PR)

FUNCTION
The PROTECT command provides the facility to alter the protection of a
file.
File protection is provided for four categories as follows:
1.

System - Specifies what categories of access the system UICs
are allowed to the file (all group numbers less than
or equal to 10 octal).

Owner

- Specifies what categories of

access

the

has

owner

allowed himself.
3.

Group - Specifies what categories of access other members
the same group have.

World

- Specifies what categories of access have
all UICs not covered above.

2-21

been

given

PERIPHERAL INTERCHANGE PROGRAM (PIP)
For each category, the user can specify
Read, Write, Extend, or Delete the file.

whether

that

directory

[100,100]

device

DKl:

UPDATE Command (/UP)

FUNCTION
The UPDATE command is similar to a COPY or MERGE command, except that
an existing file is opened and new data is written into it from the
beginning.
FORMAT
outfile=infile-l[,infile-2, ... ,infile-n]/UP[/FO]
where:
outf ile

is the file specifier for the file to be rewritten
in the format:
dev: [uic]filename.type;ver
As in the MERGE and the APPEND commands, the
output file specifier must be explicit, i.e., no
wild cards are allowed.
NOTE
The characteristics and record attributes
of the output file are taken from the
first input file.

2-30

PERIPHERAL INTERCHANGE PROGRAM (PIP)
inf ile

is the file specifier for the file to be copied
into the file being rewritten in the format:
dev: [uic]filename.type;ver/switch

NOTE
A null filename, file
defaults to *.*;*.

type,

and

version

/UP

is the UPDATE command switch.

/FO

is the Set File
Ownership
subswitch
which
specifies that the owning UIC of the output file
corresponds to the directory into which the file
was entered. If the /FO switch is not specified,
the owning UIC of all new files is the UIC under
which PIP is running, regardless of the directory
into which the file was entered
(see the COPY
command for examples using /FO) .

EXAMPLE
PIP>DKl:SAMPLE.DAT;l=TESTl.DAT;l,TEST2.DAT;l,TEST3.DAT;l/UP__}
The file SAMPLE.DAT;l on DKl: will be opened, and the contents
of files TESTl.DAT;l, TEST2.DAT;l and TEST3.DAT;l will replace
the data which already exists in the file.

2.5

PIP ERROR MESSAGES

Errors encountered by PIP during processing are reported to
in the following format:

the

user

PIP -- <main error message>
<filename or filespec> - <secondary error message>
The filename or filespec, if present, identifies the file or set of
files being processed when the error occurred. If the error was
detected by the operating system, file system, or device driver, the
secondary error message is included to explain the cause of the error.
PIP error messages are contained in message files on the system
device.
If PIP cannot access the message files, errors are reported
in the following format:
PIP -- ERROR CODE nn.
<filename or filespec> - <Driver Code

-mm.>

or
<QIO Error Code

2-31

-gg.>

PERIPHERAL INTERCHANGE PROGRAM (PIP)
where:
nn

is one of the PIP error codes
in Table 2-5.

contained

-mm

is one of the standard system, file
primitive, or file control service codes
listed in Appendix I of the RSX-11 I/O
Operations Reference Manual.

-qq

is one of the directive error codes
listed in Appendix I of the RSX-11 I/O
Operations Reference Manual.

The PIP error messages, their descriptions and suggested user
are as follows.
PIP

actions

ALLOCATION FAILURE - NO CONTIGUOUS SPACE
Description
Contiguous space available on the output volume
for the file being copied.

insufficient

the

Suggested User Action
Delete all files that are no longer
volume, and reenter the command line.

required

output

PIP -- ALLOCATION FAILURE ON OUTPUT FILE
or
PIP

ALLOCATION FAILURE - NO SPACE AVAILABLE
Description
Space available on the output volume is insufficient for the file
being copied.
Suggested User Action
Delete all files that are no longer
volume, and reenter the command line.

required

the

output

PIP -- BAD USE OF WILD CARDS IN DESTINATION FILE NAME
Description
The user has specified a wild card "*" for an output
where use of a wild card is explicitly disallowed.

filename

Suggested User Action
Reenter the command line with the proper output
specified.

2-32

file

explicitly

PERIPHERAL INTERCHANGE PROGRAM (PIP)
PIP -- CANNOT FIND DIRECTORY FILE
Description
The user has specified a UFD that does not exist on the
volume.

specific

Suggested User Action
Reenter the command line, specifying the correct UIC.
PIP -- CANNOT FIND FILE(S)
Description
The file(s) specified in
designated directory.

the

command

were

not

found

the

Suggested User Action
Check the file specifier and reenter the command line.
PIP -- CANNOT RENAME FROM ONE DEVICE TO ANOTHER
Description
The user has attempted to rename a file across devices.
Suggested User Action
Reenter the command line, renaming the file on the input
then,
enter another command to transfer the file
originally intended volume.

volume;
to the

PIP -- CLOSE FAILURE ON INPUT FILE
or
PIP -- CLOSE FAILURE ON OUTPUT FILE
Description
For some reason, the input or output file cannot be properly
closed. The file will be locked to indicate possible corruption.
Suggested User Action
Reenter the command line. If the error recurs, run the validity
check of the file structure verfication utility {VFY} against the
volume in question to determine if it is corrupted.
VFY is
described in Cha~ter 8.
PIP -- COMMAND SYNTAX ERROR
Description
The user has entered a command in a format that does not
to syntax rules.

2-33

conform

PERIPHERAL INTERCHANGE PROGRAM (PIP)
Suggested User Action
Reenter the command line with the correct syntax.
PIP -- DEVICE NOT MOUNTED
Description
The message is self-explanatory.
Suggested User Action
Mount the device, and reenter the command line.
PIP -- DIRECTORY WRITE PROTECTED
Description
PIP could not remove an entry from a directory because the device
was write-protected, or because of privilege violation.
Suggested User Action
Write enable the unit, or have the owner of the directory
its protection.

change

PIP -- ERROR FROM PARSE
Description
The specified directory file does not exist.
Suggested User Action
Reenter the command line with the correct UIC specified.
PIP -- FAILED TO ATTACH OUTPUT DEVICE
or
PIP

FAILED TO DETACH OUTPUT DEVICE
Description
An attempt to attach/detach a record-oriented output device has
failed.
This is usually caused by the device being off-line or
not resident.
Suggested User Action
Ensure that the device is on-line and reenter the command line.

PIP -- FAILED TO DELETE FILE
or

2-34

PERIPHERAL INTERCHANGE PROGRAM (PIP)
PIP -- FAILED TO MARK FILE FOR DELETE
Description
The user has attempted to delete a protected file.
Suggested User Action
Request PIP under the correct UIC and reenter the command line.
PIP -- FAILED TO ENTER NEW FILE NAME
Description
The user
has specified a
file
that already exists
in the
directory
filet
or
the
user does not have the necessary
privileges to make entries in the specified directory file.
Suggested User Action
Reenter the command line, ensuring that the filename and UIC are
specified correctly, or
request PIP under the correct UIC and
reenter the command line.
PIP -- FAILED TO FIND FILE(S)
Description
The file(s) specified in the command line were not found
designated directory.

the

trying

Suggested User Action
Check the file specifier and reenter the command line.
PIP -- FAILED TO GET TIME PARAMETERS
Description
An internal system failure occurred
obtain the current date and time.

while

PIP

was

Suggested User Action
Reenter the command line.
If the
software support representative.

problem

persists,

consult

PIP -- FAILED TO OPEN STORAGE BITMAP FILE
Description
PIP could not read
the specified volume's
usually because of a privilege violation.

storage

bit

map,

Suggested User Action
Retry by running PIP under a system UIC,
or have the
manager change the protection on the storage bit map.

2-35

system

PERIPHERAL INTERCHANGE PROGRAM (PIP)
PIP -- FAILED TC READ ATTRIBUTES
Description
The user's volume is corrupted or the user
necessary privileges to access the file.

does

not

have

the

Suggested User Action
Ensure that PIP is running under the correct UIC. If the UIC is
correct, then run the validity check of the file structure
verification utility (VFY) against the volume in question to
determine where and to what extent the volume is corrupted. VFY
is described in Chapter 8.
PIP -- FAILED TO REMOVE DIRECTORY ENTRY
Description
PIP could not remove an entry from a directory because the
was write-protected, or a privilege violation was detected.

unit

Suggested User Action
Write enable the unit, or have the owner of the directory
its protection.

change

PIP -- FILE IS LOST
Description
PIP has removed a file from its directory, failed to
and failed to restore the directory entry.

delete

it,

Suggested User Action
Run the lost check of the file structure verification utility
(VFY) to recover the filename. VFY is described in Chapter 8.
PIP -- FAILED TO SPOOL FILE FOR PRINTING
Description
Insufficient system dynamic memory is available, or
task is not installed.

the

spooler

Suggested User Action
Wait for spooler queue to empty or install the spooler
reenter the command line.

2-36

task

and

PERIPHERAL INTERCHANGE PROGRAM (PIP)
PIP -- FAILED TO WRITE ATTRIBUTES
Description
The user volume is corrupted or the user does not
necessary privileges to write the file attributes.

have

the

Suggested User Action
Ensure that PIP is running under the correct UIC. If the UIC is
correct, then run the validity check of the file structure
verification utility (VFY) against the volume in question to
determine where and to what extent the volume is corrupted. VFY
is described in Chapter 8.
PIP -- FILE NOT LOCKED
Description
The user issued an unlock command for a file that was not locked.
Suggested User Action
Reenter the command line, specifying the correct file.
PIP -- ILLEGAL COMMAND
Description
The user has entered a command that is not recognized by PIP.
Suggested User Action
Reenter the
specified.

command

line

with

the

PIP

command

correctly

PIP -- ILLEGAL SWITCH
Description
The user has specified a switch that is not a legal PIP switch or
has used a legal switch in an illegal manner.
Suggested User Action
Reenter the command line with the correct switch specification.
PIP -- ILLEGAL "*" COPY TO SAME DEVICE AND DIRECTORY
Description
The user has attempted to copy all versions of a file into the
same directory that is being scanned for input files. This
results in an infinite number of copies of the same file.

2-37

PERIPHERAL INTERCHANGE PROGRAM {PIP)
Suggested User Action
Reenter the command line, renaming the files or copying them into
a different directory.
PIP -- ILLEGAL USE OF WILD CARD VERSION
Description
The use of a wild card version number in the attempted
results in inconsistent or unpredictable output.

operation

Suggested User Action
Reenter the command line with different options or with
or default version number.

explicit

PIP -- I/O ERROR ON INPUT FILE
or
PIP -- I/O ERROR ON OUTPUT FILE
Description
One of the following conditions may exist:
1.

The device is not on-line,

The device is not mounted.

The hardware has failed.

The volume is full {output only) .

Input file is corrupted.

Suggested User Action
1.

Determine which condition exists.

Rectify the condition.

Reenter the command line.

PIP -- EXPLICIT OUTPUT FILENAME REQUIRED
Description
This message is self explanatory.
Suggested User Action
Reenter the command line
specified.

with

2-38

the

output

filename

explicitly

PERIPHERAL INTERCHANGE PROGRAM (PIP)
PIP -- NOT A DIRECTORY DEVICE
Description
The user has issued a directory-oriented command to
(such as a printer) that does not have directories.

device

Suggested User Action
Reenter the command line without specifying a UIC.
PIP -- NOT ENOUGH BUFFER SPACE AVAILABLE
Description
PIP has insufficient I/O buffer space to
command.

perform

the

requested

Suggested User Action
Have the system manager install PIP in a larger partition.
PIP -- NO SUCH FILE(S)
Description
The file(s) specified in
designated directory.

the

command

were

not

found

the

The user has specified a UIC other than [*,*] as the output
UIC for a copy.

file

Suggested User Action
Check the file specifier and reenter the command line.
PIP -- ONLY[*,*] IS LEGAL AS DESTINATION UIC
Description

Suggested User Action
Reenter the command line with [*,*] specified as the output UIC.
PIP -- OPEN FAILURE ON INPUT FILE
or
PIP -- OPEN FAILURE ON OUTPUT FILE
Description
The specified file could not be opened.
conditions may exist:
1.

The file is protected against access.

2-39

One

the

following

PERIPHERAL INTERCHANGE PROGRAM {PIP)
2.

A problem exists on the physical device {e.g., device
down) .

cycled

The volume is not mounted

The specified file directory does not exist.

The named file does not exist in the specified directory.

Suggested User Action
1.

Determine which condition exists.

Rectify the condition.

Reenter the command line.

PIP -- OUTPUT FILE ALREADY EXISTS-NOT SUPERSEDED
Description
An output file of the same name, type, and version
already exists.

the

file

Suggested User Action
Retry the copy with the /NV switch to assign a new version number
or the /SU switch to supersede the output file.
PIP -- TOO MANY COMMAND SWITCHES - AMBIGUOUS
Description
The user has
conflict.

specified

too

many

switches,

the

switches

Suggested User Action
Reenter the command line, specifying the correct set of switches.
PIP -- VERSION MUST BE EXPLICIT OR "*"
Description
The version number of the specified
explicitly or as a wild card "*"

file

must

expressed

number

correctly

Suggested User Action
Reenter the
expressed.

command

line

with

2-40

the

version

PERIPHERAL INTERCHANGE PROGRAM (PIP)
2.6

PIP ERROR CODES

Table 2-5 identifies the error codes PIP issues when it doesn't have
access to the message files.
Message descriptions and suggested user
actions are identical to the information contained in Section 2.5.
Table 2-5
PIP Error Codes
Error Code
1.

2.
3.
4.
5.
6.

7.
8.
9.

10.
11.
12.
13.
14.

15.
16.

17.
18.
19.
20.

21.
22.
23.
24.
25.

26.
27.
28.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.

PIP Error Message is:
COMMAND SYNTAX ERROR
ILLEGAL SWITCH
TOO MANY COMMAND SWITCHES - AMBIGUOUS
ONLY [*,*] IS LEGAL AS DESTINATION UIC
ILLEGAL COMMAND
ILLEGAL 11 * 11 COPY TO SAME DEVICE AND DIRECTORY
BAD USE OF WILD CARDS IN DESTINATION FILE NAME
EXPLICIT OUTPUT FILE NAME REQUIRED
ALLOCATION FAILURE - NO CONTIGUOUS SPACE
ALLOCATION FAILURE - NO SPACE AVAILABLE
ALLOCATION FAILURE ON OUTPUT FILE
I/0 ERROR ON INPUT FILE
I/0 ERROR ON OUTPUT FILE
ILLEGAL USE OF WILD CARD VERSION
OPEN FAILURE ON INPUT FILE
OPEN FAILURE ON OUTPUT FILE
CLOSE FAILURE ON INPUT FILE
CLOSE FAILURE ON OUTPUT FILE
FAILED TO DETACH OUTPUT DEVICE
DEVICE NOT MOUNTED
OUTPUT FILE ALREADY EXISTS - NOT SUPERSEDED
FAILED TO MARK FILE FOR DELETE
FILE IS LOST
VERSION MUST BE EXPLICIT OR 11 * 11
ERROR FROM PARSE
FAILED TO DELETE FILE
CANNOT FIND DIRECTORY FILE
FAILED TO ATTACH OUTPUT DEVICE
NOT A DIRECTORY DEVICE
FAILED TO WRITE ATTRIBUTES
FAILED TO READ ATTRIBUTES
FILE NOT LOCKED
FAILED TO ENTER NEW FILE NAME
FAILED TO RESTORE ORIGINAL DIRECTORY ENTRY - FILE
IS LOST
CANNOT RENAME FROM ONE DEVICE TO ANOTHER.
FAILED TO SPOOL FILE FOR PRINTING
{Not used in RSX-llM)
FAILED TO OPEN STORAGE BITMAP FILE
FAILED TO FIND FILE {S)
CANNOT FIND FILE{S)
NO SUCH FILE{S)
FAILED TO REMOVE DIRECTORY ENTRY
DIRECTORY WRITE PROTECTED
NOT ENOUGH BUFFER SPACE AVAILABLE

2-41

CHAPTER 3
FILE TRANSFER PROGRAM (FLX)

3.1

INTRODUCTION TO FLX

FLX is a file utility program that performs
DOS-11 or RT-11 and Files-11 formats.
following conversions:

•

From DOS-11 to Files-11 format,

•
•

From Files-11 to DOS-11 format,

file

conversion

between

FLX is designed to perform the

From DOS-11 to DOS-11 format,

From Files-11 to Files-11 format,

•

From RT-11 to Files-11 format,

•
•

From Files-11 to RT-11 format,
From RT-11 to RT-11 format.

FLX also allows the user to:
1.

List directories of cassettes, RT-11, or DOS-11 volumes,

Delete files from DOS-11 and RT-11 volumes,

Initialize cassettes, RT-11, or DOS-11 volumes.

Valid DOS-11 devices are:
DK, DT, MT, MM, CT, PR, and PP
Valid RT-11 devices are:
DK, DT, and DX
All valid
cassette.

Files-11

devices

are

3-1

supported,

including

RSX-format

FILE TRANSFER PROGRAM (FLX)
3.2

INITIATING FLX

All RSX-llM utilities can be initiated in several ways.
The various
methods are explained in Section 1.2. The methods for FLX are:
2._FLX.)
>FLX command

string~

>RUN ... FLX __}
>RUN ..• FLX/UIC= [group ,member]._)
~RUN $FLX~

>RUN

3.3

$FLX/UIC=[group,member]~

FLX COMMAND STRING

The command string issued to FLX consists of an optional output file
specifiers, and one or more input file specifier in the following
format:
outfile=infile-1 [, infile-2, ... ,infile-n]
For a complete description of file specifiers, see Section 1.3.
wild card s a r e on 1 y v a 1 id f o r " inf i l e " spec if i er s •
Version numbers are only valid for Files-11 files and may not be
specified as wild.
The standard rules for updating version numbers
apply.

3.4

FILE TRANSFERS

File transfers are specified by a command containing an output and an
input specifier together with a Format Mode Switch to denote the
format to be used. For example:
FLX>DTO:/DO=DKl:SYSl.MAC/RS~

transfers SYSl.MAC from Files-11 DKl:

to the DOS-11 DTO:.

FLX>DT 1: /RT=DKO: SYS 1. MAC/RS._,;'
transfers SYSl.MAC from Files-11 DKO:

to RT-11 DTl:.

If no /RS, /RT, or /DO is specified, FLX assumes /DO for input
specifiers and /RS for output. This "DOS-to-RSX" default transfer
direction can be dynamically modified
see /DO and /RS switch
descriptions.

3-2

FILE TRANSFER PROGRAM (FLX)
3.5
3.5.l

DOS VOLUME DIRECTORY MANIPULATION
DOS Directory Listings

The /LI or /DI switch instructs FLX to issue the directory of the
cassette or DOS-11 volume specified in the input specifiers to the
Files-11 file specified in the output specifier.
If no output
specifier is present, then the directory will be issued to TI:. For
example:
FLX>LP:=DTO: (100,100]*.MAC/LI_J
lists on the line printer the directory of all .MAC
(100,100] on DOS-11 DTO:.

under

UIC

Files may be deleted from DOS-11 disks or DECtape by using the
switch.
The delete command string uses no output specifier.
example:

/DE
For

3.5.2

files

Deleting DOS Files

FLX>DKl: (100,lOO]SYSl.MAC/DE_.}
deletes SYSl.MAC under UIC (100,100] from the DOS-11 DKl:.

3.5.3

Initializing DOS-11 Volumes

Cassettes and DOS-11 volumes are initialized by using the /ZE
The initialize command has no output specifier. For example:

switch.

FLX>DTl:/ZE _J
Initializes DOS-11 DTl:.

3.6
3.6.1

RT VOLUME DIRECTORY MANIPULATION
RT Directory Listings

The /LI or /DI switch, when combined with the /RT switch, instructs
FLX to issue the directory of the RT-11 volume specified in the input
specifiers to the Files-11 file specified in the output specifier. If
no output specifier is present, then the directory will be issued to
TI: For example:
FLX>LP:=DTO:*.MAC/LI/RT_J
lists on the line printer the directory of all
DTO:.

3-3

.MAC

files

RT-11

FILE TRANSFER PROGRAM (FLX)
3.6.2

Deleting RT Files

Files may be deleted from RT-11 disks or DECtape by using the /DE
switch in conjunction with the /RT switch. The delete command string
uses no output specifier. For example:
FLX>DKl:SYSl.MAC/DE/RT_.}
deletes SYSl.MAC from RT-11 DKl:.

3.6.3

Initializing RT-11 Volumes

RT-11 volumes are initialized by using the /ZE switch in conjunction
with the /RT switch. The initialize command uses no output specifier.
For example:
FLX>DTl:/ZE/RT_J
initializes RT-11 DTl:.
When initializing RT-11 volumes, the
argument in the form:

/ZE

switch

takes

optional

/ZE:n
where n specifies the number of extra words per directory entry.
A
directory segment consists of two disk blocks with a total of 512
words. The directory header uses five words, leaving 507 words for
directory entries.
Normally, each directory entry is 7-words long and two directory
entries within each directory segment are allocated to the file
system. Therefore, the number of entries in each segment (when no
extra words are specified) are determined as follows:
Directory Entries

(507+7) -2
72-2 = 70 entries

When extra words are specified (via /ZE:n) for directory entries,
number of directory entries are determined as follows:

the

Directory Entries= [507-;-(n+7)] -2
For example, 61 entries can be
switch /ZE:l is used.

made

per

directory

segment

the

The /NU switch is used with the /ZE and /RT switches to specify the.
number of djrectory segments to allocate to the RT-11 volume. The /NU
switch has the following form:
/NU:n
where n specifies the number of directory segments to allocate.
If
the /NU switch is not specified, or if n is not specified, four
directory segments are allocated.
The maximum number of segments
which can be allocated is 37(8) or 31(10). For example:
FLX>DTO:/ZE:2/NU:6/RT..J

3-4

FILE TRANSFER PROGRAM (FLX)
This command initializes RT-11 DTO:, allocates two extra
directory entry, and allocates six directory segments.

3.7

words

per

FLX CASSETTE SUPPORT

FLX supports the DEC standard cassette file structure. Files may be
transferred to and from cassettes in either RSX (/RS) or DOS (/DO)
transfer mode. The transfer mode selected depends on the user's file
format requirements.

3.7.l

Cassette File Formats

The file format for RSX or DOS cassette files is essentially the same.
That is, they both conform to the DEC standard casette file format.
The DEC standard cassette file structure is described in Figure 3-1.
The DEC standard cassette file label is described in Figure 3-2.
The difference between the RSX and DOS cassette file
follows:
RSX Format

formats

are

DOS Format

•

Standard level 2

Standard level 0

•

12-character file name (9+3)

9-character file name (6+3)

•

Blocks of any size up to 512
bytes ( 128 bytes default)

•
•

•

Version numbers

•

128-byte blocks
NO version numbers

RSX cassette file mode (level 2) is a superset of the DOS cassette
file mode (level 0). Therefore, any cassette written in DOS mode can
be read in RSX mode. The reverse of this, however, is only true when:

file was written with 128-byte blocks, and

The

The extra file header data (version number, etc.), which does
not appear in DOS files, can be ignored.

RSX mode files and DOS mode files can be mixed on a given cassette, as
long as a proper retrieval mode is utilized when the files are being
accessed. Files of various block sizes can also share a given
cassette.
FLX uses the block size contained in the file label data
when reading a file.

3-5

FILE TRANSFER PROGRAM (FLX)

leader

IRG=inter record gap

IRG

File label

T}I

IRG

2 bytes

I
I

Data blocks

IRG

I
I
I

I
I
I
I

:
EOF
I
I

file

I~
t

I
I
I
I

files

EOF

I--

IRG
logical
end-oftape

32-byte null file label

Clear
trailer

---

Figure 3-1
DEC Standard Cassette File Structure

3-6

FILE TRANSFER PROGRAM (FLX)

1
2

Filename

3
4
5
6

File type
8

Data type

9
10

Record size
11

Sequence Number

13 I

Support Level

15 I
16 I

17
18
19

Date

20 I

Version Number

21
~~

L.L.

Record attributes byte

Unused (for user info)

24
25
26

Filename pt. 2

27
28
29

Unused (for user info)

30
31

Figure 3-2
DEC Standard Cassette File Label

3-7

FILE TRANSFER PROGRAM (FLX)

Filename

6 ASCII Characters

File type

3 ASCII Characters

Data type

Describes the type of file
to follow.

Record size

Unknown type

ASCII (formatted)

Formatted binary (DOS)

DOS LDA format

Unformatted binary TSK
format

16-bit binary record size,
where

~<size

<512. and even.

Sequence number

Used for multi-volume files,
~ for sequence one.

Support level

for DOS format

2 for RSX format
Date

6 ASCII characters in
ddmmyy form

Version number

16-bit version number used
in RSX mode. Undefined in
DOS mode.
The Files-11 standard rules for
version numbers apply to file
creation.

Record attributes

1 = FORTRAN carriage
control present
2 = standard carriage control

Filename pt. 2

3 ASCII characters used in
RSX mode. Undefined in DOS
mode.

Figure 3-2 (Cont.)
DEC Standard Cassette File Label

3-8

FILE TRANSFER PROGRAM {FLX}
3.7.2

Multi-Volume Cassette Support

FLX supports multi-volume cassettes in both RSX and DOS formats.
No
special switches are required to notify FLX that a multi-volume file
is being accessed.

3.7.2.1 FLX Output Files - When FLX detects the physical end-of-tape
for an output cassette, the following sequence of events occurs.
1.

FLX issues the following message:
FLX -- END OF VOLUME ON CASSETTE
CTn: [g ,m]

The cassette is rewound.

FLX issues an additional message.
MOUNT NEW CASSETTE?
FLX>

(Y, Z (OUTPUT ONLY} OR CR}

At this point, the user has three alternatives:
a.

The user can mount the next output cassette volume and
type Y, followed by a carriage return. If the user
selects this alternative, the new cassette is rewound,
FLX searches for the logical end-of-tape {end of the last
file}, and then continues transferring data onto the
tape.
If a file with the same name as the current input
file is encountered on the new output cassette while
searching for the logical end of tape, FLX prints the
message:
FLX -~ FILE ALREADY EXISTS
and then returns to step 3 above.

The user can mount the next output cassette volume and
type Z, followed by a carriage return. The new cassette
is rewound, and FLX continues by transferring data onto
it.
Thus, the tape is effectively zeroed before data is
transferred to it.

The user can enter a carriage
transfer.

return

If the user selects alternative c, FLX assumes that
and issues the following message:

to
EOF

terminate
is

desired,

FLX -- REQUEST TERMINATED -- LAST BLOCK NOT WRITTEN
The last input file block processed was not written onto the tape.

3-9

the

FILE TRANSFER PROGRAM (FLX)
3.7.2.2 FLX Input File - When FLX detects the physical end-of-tape
for an input cassette, the following sequence of events occurs:
1.

FLX issues the following message, including the
specifier on which the end-of-tape was detected:

input

file

FLX -- END OF VOLUME ON CASSETTE
CTn: [g,m] filename.type
2.

The cassette is rewound.

FLX issues an additional message:
(Y, Z (OUTPUT ONLY) OR CR)

MOUNT NEW CASSETTE:
FLX>
4.

At this point the user has two alternatives:
a.

The user can mount the next input cassette volume and
type Y, followed by a carriage return to continue; or

The user can type a
transfer.

carriage

return

terminate

the

If the user selects alternative a, the new input cassette is rewound,
and a validity check is performed on the file label and sequence
number. If the file label and sequence number are correct, FLX begins
processing data from the volume.
If, however, the file label and
sequence number are not correct, FLX issues the following message:
FLX -- FILE NOT FOUND
the process then returns to step 3 above.
If the user selects alternative b, FLX assumes that
and the transfer is terminated.

EOF

desired,

NOTE
If the input file is being processed as
a formatted binary or an ASCII file, a
format error may occur.
If the user types Z, FLX prints the message:
FLX -- BAD RESPONSE
the process then returns to step 3 above.

3. 8

FLX PAPER TAPIL.§£1!?.;f?.QRT

FLX supports the standard DEC paper
Paper Tape Reader/Punch and the
devices.

tape devices, i.e., the PC-11
PR-11 Paper Tape Reader, as DOS

FLX provides the ability to delimit records on paper tape for files
that are in formatted binary mode or in formatted ASCII mode.

3-10

FILE TRANSFER PROGRAM (FLX)
Formatted binary records are delimited by standard DOS 4-byte headers
and a trailing checksum. Formatted ASCII records which do not already
end with line feeds or form feeds are delimited by
carriage
return-line feed pairs.
Special treatment is given to files which normally default to image
mode transfers, i.e., TSK, OLB, MLB, and SYS files. On output to
paper tape, these files are written, by default, in formatted binary.
When read back from paper tape to a Files-11 volume, the file is
written with fixed-length, 512-byte records as the default.
These defaults insure, when these files are read back from paper tape,
that they will be in exactly the same format as they were before they
were punched. However, the new files will not be contiguous unless
the user specifies /CO/BL:n with the output file specifier. An
appropriate value for n (the number of contiguous blocks to allocate),
must be known by the user before issuing the command.
NOTE
The use of explicit
transfer
mode
switches when transferring TSK, OLB,
MLB, and SYS files between paper tape
and Files-11 volumes can cause files
read back in from paper tape to be
different
from the files that were
originally written out.

3.9

FLX SWITCHES

FLX provides three types of switches for file transfers: format mode
switches, which specify the format of the file;
transfer mode
switches which control the mode of transfer
(e.g., formatted ASCII
mode, formatted binary mode, or image mode);
and file control
switches, which control such things as the number of blocks to be
allocated to the output file, or the output file's UIC, etc. Switch
specificatons consist of a slash (/), followed by a 2-character switch
name, and is optionally followed by a value separated from the switch
specifier by a colon (:).

3.9.1

Format Mode Switches

FLX has three format mode switches:
/DO (DOS format), /RT (RT-11
format);
and /RS (Files-11 format). When specified, these switches
describe the format of the specified files.
These switches are
described in Table 3-1.

3-11

FILE TRANSFER PROGRAM (FLX)
Table 3-1
FLX Format Mode Switches
Description

Switch
/DO

Identifies the file as a DOS-11 formatted file.
NOTE
If no /DO, /RT, or /RS switch is specified
in a command string, FLX initially assumes
/RS for output files and /DO for
input
files.
However,
this default transfer
direction can be dynamically changed by
specifying a command consisting of only
the switch desired for the input side (/DO
or /RS only) . See the note following /RT
for the /RT default operation.
Example:
To specify the default transfer
from RSX to DOS, type:

direction

FLX>/RS_J
To specify the default transfer
from DOS to RSX, type:

direction

FLX>/DO_)
/RS

Identifies the file as a Files-11 formatted file.
NOTE
See notes for /DO and /RT switches.

/RT

Identifies the file as an RT-11 formatted file.
NOTE
If the /RT switch is specified on one side
of a command string, the default entry for
the other side is /RS.
Examples:
1.

FLX>DKO:=DTO:SYSl.MAC/RT.)
The output is defaulted to /RS.

FLX>DKO:/RT=DKO:SYSl.MAC__}
The input is defaulted to /RS.

3-12

FILE TRANSFER PROGRAM (FLX)
3.9.2

Transfer Mode Switches

FLX has three modes of file transfer for conversion in either
direction between DOS-11 and Files-11, or between RT-11 and Files-11.
These modes are: formatted binary, formatted ASCII, and image mode.
When a switch is specified, it determines the transfer mode to be
applied during translation. The switch formats and descriptions are
listed in Table 3-2 below.
Table 3-2
FLX Transfer Mode Switches

Description

Switch

/FA:n

Formatted ASCII

The DOS-11 or RT-11 file is to be formatted ASCII.
Formatted ASCII is defined as ASCII data records
terminated by carriage return/form feed
(CR-FF),form
feed
(FF), or vertical tab (VT).
In
transfers from DOS-11 or RT-11 files to Files-11
files, CR-LF pairs are removed from the end of
records. In transfers from Files-11 files to
DOS-11 or RT-11 files, CR-LF pairs are added to
the end of each record which does not already end
with LF or FF.
In both directions all nulls,
rubouts, and vertical tabs (VT) are removed from
input records.
If n
is
specified
with
Files-11
output,
fixed-length records of size n are generated.
Output records will be padded with nulls, if
necessary.
If n is not specified with Files-11 output, then
variable-length records are generated. The output
record size will equal the input record size.
NOTE
ASCII data is transferred as 7-bit values.
The eighth bit of each byte is masked off
before transfer. CTRL/Z (ASCII 032 octal)
is treated as the logical end of input
file for formatted ASCII transfers from
DOS-11 cassette or paper tape to Files-11.

3-13

FILE TRANSFER PROGRAM (FLX)
Table 3-2 (Cont.)
FLX Transfer Mode Switches
~--------~--------·--·--···-----·····----------------------~

Description

Switch
/FB:n

Formatted Binary
The DOS-11 or RT-11 file is to be formatted
binary.
In formatted binary mode, formatted
binary headers and checksums are added to records
output to DOS-11 or RT-11 files, and they are
removed when transferred to Files-11 files.
If n is specified with Files-11 output, then
fixed-length records of size n will be output (512
bytes is the maximum).
FLX pads records with
nulls to create the specified length. If n is not
specified
with
Files-11
output,
then
variable-length records are produced. The output
record size is equal to the input record size.

/IM:n

Image Mode
The transfer is to be in image mode.
Image mode
forces fixed-length records. The value n can be
used to indicate the desired record length for
Files-11 output (512 bytes is maximum). If the
value n is not specified, a record length of 512
bytes is assumed.
NOTES
1.

The following dGfaul t transfer modes are
assumed for these file types (with the
exception of paper tape transfers -- see
Section 3. 8).
Mode
-

File Type

/IM

TSK, OLB, MLB, SYS

/FB

OBJ, STB, BIN, LDA

/FA

All others

If the value n is specified in conjunction
with /FA, /FB, or /IM when the output file
is not a Files-ll file, it is ignored.

3-14

FILE TRANSFER PROGRAM (FLX)
3.9.3

File Control Switches

In addition to the switches associated with the transfer modes and
directions, FLX provides switches to control file processing. These
switches are described in Table 3-3.
Table 3-3
FLX File Control Switches
Description

Switch
/BL:n

Indicates the number of contiguous blocks to be
allocated to the output file ·where n spec i f ies the
number of bloc ks.
This switch is used normally in
/CO.
I f /BL is not spec i f ied, the

conjunction

input

file

size

with
is

used as the output file size.
NOTE
I

The file allocation scheme used for RT-11
volumes normally allocates the largest
available space on the volume for a new
Using /BL:n with the /RT switch for
file.
the output file causes the output file to
be allocated the first <UNUSED> space of
.
> n.
size_
However, when the RT-11 file is
closed, the input file size is used as the
output file size. I f the input file size
is not ~ n, an error results. Since all
RT-11 files are contiguous, the /CO switch
is not required with the /BL:n switch for
RT-11 output.

1·

/BS:n

Spec i f ies the block size for cassette tape output,
where:
n specifies the block size in bytes.
128 is
I f /BS is not spec i f ied, a block size of
assumed.
/BS is only valid in a cassette tape
(CT) output file spec i f ier.

I /CO

Indicates that
contiguous.

the

output

file

The /CO switch is meaningful
DECtape.

only

is
to

disks

and

I f the input
file is paper tape, cassette
DOS-11 mag tape, /BL is also required.

3-15

FILE TRANSFER PROGRAM (FLX)
Table 3-3 (Cont.)
FLX File Control Switches
Description

Switch

NOTE
The file types .TSK, .SYS, and .OLB are
transferred to Files-11 volumes with /CO
implied when the input is a FILES-11
volume or a DOS-11 DECtape or disk.
/DE

Deletes files from a DOS-11 DECtape or disk.
It
is used also in conjunction with /RT to delete
files from an RT-11 DECtape or disk.
NOTE
When /DE is specified, the FLX
string has no output specifier.

/DI

command

Causes a directory listing of cassettes or DOS
volumes to be listed on a specified output file.
It is used also in conjunction with /RT to
generate a directory listing of RT-11 volumes in a
specified output file.
NOTES
1.

Files-11 volume directories
listed using FLX.

If no output specifier is present,
the directory is issued to TI:.

If no filename
assumed.

can

specified,

not

* *

be
then
is

Figure 3-3 contains sample DOS volume directory
listings,
along
with
a description of the
information contained in each field.
Figure 3-4
contains sample RT volume directory listings,
along with a description of the
information
contained in each field.

3-16

FILE TRANSFER PROGRAM (FLX)
Table 3-3 (Cont.)
FLX File Control Switches

I Switch

Description

I
r

I /FC
I

Indicates
that
FORTRAN
carriage
control
conventions are to be used, i.e., FD.FTN is set in
the file data block.
The default is a carriage
return and line feed between records, i.e., FD.CR
is set. The /FC switch applies only to Files-11
output files.
Refer to the RSX-11 I/O Operations
Reference Manual for a discussion of the file data
block and record attributes.

/ID

Requests the current version number of FLX.
The
switch can be part of an output or input specifier
or it can be typed in response to the FLX prompt
message (FLX>).

/LI

Same as /DI

/NU:n

Used in conjunction with the /ZE and /RT switches
to specify the number of directory blocks (n) to
allocate when initializing an RT-11 disk
or
DECtape.
If
/NU:n
is not specified, four
directory blocks are allocated.
The
maximum
number of blocks which can be allocated is 37
octal ( 31 dee imal) .

/SP

Indicates that the converted file is to be spooled
via the print spooler.
The /SP switch applies
only to Files-11 output files.
The print spooler
is described in Appendix C.

/UI

Indicates that the output file is to have the same
UIC as the input file.
The /UI switch is ignored
if the output specifier contains an explicit UIC.
Causes each record written to the cassette
..,.,......,,~
L.CClU

~""~
CU.J.\,.I.

T7"'V".:-1=.;,...~
V'C..L i..1...1..C'Ue

m'h.,....

.1.lJ.C

/'t7Q

V.L.I

rlT.7.;4-,...'h,

OYY.J..l..\,.,.ll

.;ra

.J..C>

r'\.'r"'lo,~7
Vll..L:f

·n~1;,-=1
Vc;...t.J...&..\.A

with a CT output file specifier.
/ZE

Initializes cassettes or DOS-11 volumes.
It
used also
in conjunction with /RT (and /ND)
initialize RT-11 volumes.
NOTES
1.

For DOS-11 DECtaper /ZE creates
for the current UIC.

The /ZE command uses no output specifier.

3-17

entry

is
to

FILE TRANSFER PROGRAM (FLX)
DECtape Directory Listing
DIRECTORY
19-SEP-74

DT : [ 2 0 0 , 2 0 0 J
104.
8.
6.
14.

FLX.TSK
UFD.TSK
TKN.TSK
MOU.TSK

19-SEP-74
19-SEP-74
19-SEP-74
19-SEP-74

<233>
<233>
<233>
<233>

TOTAL OF 132. BLOCKS IN 4. FILES
Casette Directory Listing
DIRECTORY
19-SEP-74
UFD.TSK;l-0
TKN. TSK; 1-0
MOU.TSK;l-0

CTl: [200,200]
28.
20.
52.

19-SEP-74 128.
19-SEP-74 128.
19-SEP-74 128.

TOTAL OF 100. BLOCKS IN 3. FILES
These directories contain similar
information.
The following
explains what that information is and where it is located.

key
1

0) ( 8or 10)
1.

Identifies this as a directory listing.

Specifies the device name and unit number.

Is the User Identification Code.

Is the date the directory was listed.

Is the filename, file type, version number
only) , and sequence number (cassettes only).

Is the file size in blocks.

Is the file creation date.

Is the record size in bytes for the file

Is a total of the actual file sizes, and the total number
files in the directoty.

10.

Protection code (disk and DECtape only).

Figure 3-3
DOS Directory Listings
3-18

(RSX

cassettes

(cassettes only).
of

FILE TRANSFER PROGRAM (FLX)
DECtape Directory Listing
DIRECTORY
4-JUN-75

DK:

SIPBOO.MAC
49.
< UNUSED >
6.
SIP
.MAC
10.
SIPCD .MAC
7.
< UNUSED >
21.
SIPQIO.MAC
7.
< UNUSED > 4686.

4-JUN-75
4-JUN-75
4-JUN-75
4-JUN-75

4713. FREE BLOCKS
TOTAL OF 73. BLOCKS IN 4. FILES
The following key explains what the information is, and
located.

CD
0

v
(i)
G)

\:J

(;\.

where

\::...)

Identifies this as a directory listing.

Specifies the device name and unit number.

Is the date the directory was listed.

Is the filename and file type;
(unused) space.

Is the number of blocks in the file or free space.

Is the file creation datei or blank for free space.

Is the total number of free blocks on the volume.

Is the total number of
volume.

blocks

allocated

Figure 3-4
RT Directory Listing

3-19

indicates

files

free

the

~ILE

3.10

TRANSFER PROGRAM (FLX)

FLX ERROR MESSAGES

Errors encountered by
initiating terminal.

FLX

during

processing

are

reported

The FLX error messages, their descriptions and suggested user
are described below.

the

actions

FLX -- BAD LIST FILE SPEC
Description
The user has specified one of the following:
1.

More than one output file for an /LI or /DI operation.

Wild cards in the output file for an /LI or /DI operation.

Suggested User Action
Reenter the command line correctly.
FLX -- BAD RESPONSE
Description
The user has specified the Z response to the message:
MOUNT NEW CASSETTE (Y, Z (OUTPUT ONLY) OR CR)
FLX>
and the cassette in question is an input volume.
Suggested User Action
Respond with Y or CR after the message has been redisplayed.
FLX -- CAN'T OPEN @ FILE
Description
The specified indirect command file could not be opened
of the following reasons:

for

The file is protected against access.

A problem exists on the physical device (e.g., device
down) •

Volume is not mounted.

The specified file directory does not exist.

The named file does not exist in the specified directory.

The volume is not on-line.

Suggested User Action
Correct the condition and reenter the command line.

3-20

one

cycled

FILE TRANSFER PROGRAM (FLX)
FLX -- CO FILES TO OUTPUT DEVICE NOT ALLOWED
Description
The user has used the /CO switch with an
(e.g. , MT, CT, or PP) .

illegal

output

device

Suggested User Action
Reenter the command line without the /CO switch specified.
FLX -- CASSETTE ERROR I/O TERMINATED
Description
hardware
error
has
occurred
during
the
An unexpected
end-of-volume sequence on a cassette volume. The transfer is
aborted.
Suggested User Action
Reenter the command line using a new cassette.
FLX -- COMMAND SYNTAX ERROR
Description
The user has entered a command in a format that does not
to syntax rules.

conform

Suggested User Action
Reenter the command line with the correct syntax.
FLX -- CONFLICTING TRANSFER MODES SPECIFIED
Description
The user has specified conflicting transfer mode switches.
Example:
SY:=DT:FOO.OBJ/IM/FB.-J
Suggested User Action
Reenter the command line
specified.

with

only

one

transfer

mode

switch

FLX -- DOS OR RT-11 DEVICE NOT VALID FORMAT
Description
The device specified with the /DO switch has an incorrect DOS
file structure, or the device specified with the /RT switch has
an incorrect RT file structure.
Suggested User Action
Correct the problem, and reenter the command line.

3-21

FILE TRANSFER PROGRAM (FLX)
FLX -- DT:

UFD FULL

Description
The DECtape directory is full.
Suggested User Action
Clean up the directory by deleting all unnecessary files.
FLX
END OF VOLUME ON CASSETTE
MOUNT NEW CASSETTE? (Y, Z (OUTPUT ONLY) OR CR)
Description
Physical end-of-tape has been encountered during a cassette
transfer.
The tape rewinds, and the user is asked to mount the
next cassette.
Suggested User Action
See Section 3.7.2.1 if an output transfer is being performed
Section 3.7.2.2 if an input transfer is being performed.

FLX -- ERROR DURING DIRECTORY I/O
Description
One of the following conditions may exist:
l.

The volume is not write-enabled.

The /DO, /RT or /RS switches were incorrectly specified.

The volume is not of the proper format.

A hardware error occurred during a
(i.e., bad tape).

directory

I/O

operation

Suggested User Action
The following user actions
conditions listed above.

correspond

(by

number)

the

Write-enable the volume.

Respecify the /DO, /DT or /RS switches correctly.

No recovery is possible with the volume currently mounted.
Mount a volume which is in the proper format, and retry the
operation.

Retry the operation.

FLX -- FILE ALREADY EXISTS
Description
The user specified an output file which
device specified.

3-22

already

exists

the

FILE TRANSFER PROGRAM (FLX)
Suggested User Action
Reenter the file specifier using a new or corrected filename.
FLX -- @ FILE NESTING EXCEEDED
Description
More than one level of indirect files was specified.
Suggested User Action
Retry the
specified.

operation

with

only

one

level

indirect

file

The named file does not appear, as specified,
directory.

the

requested

directory

correctly

FLX -- FILE NOT FOUND
Description

Suggested User Action
Retry the operation with the
specified.

filename

and

FLX -- WARNING -- INPUT FILE OUT OF SEQUENCE
Description
A cassette multi-volume file is being accessed out of sequence.
Suggested User Action
This is a warning message.
terminated by the user.

The

transfer

will

continue

unless

FLX -- @ FILE SYNTAX ERROR
Description
Syntax error in the indirect file specifier.
Suggested User Action
1.

Edit the indirect command file using either EDI or SLP.

Rerun FLX using the corrected cpmmand file.

FLX -- FMTD ASCII RECORD FORMAT BAD
or
FLX -- FMTD BINARY RECORD FORMAT BAD
Description
Either the file is corrupted, or the file is not of the specified
type.

3-23

FILE TRANSFER PROGRAM {FLX)
Suggested User Action
If the file is corrupted, there is no recovery possible. If the
file type is incorrect, retry the operation with the correct
type.
FLX -- ILLEGAL /BS SIZE -- USE O<N<=512.

AND EVEN

Description
An illegal block size
cassette output.

was

specified

with

the

/BS

switch

Suggested User Action
Reenter the command line with a lega.l block size.
FLX -- INCORRECT # IN/OUT SPECS
Description
The user specified more than one input or output specifier
command where only one is allowed.

Suggested User Action
Reenter the command line with the proper syntax.
FLX -- INVALID DEVICE
Description
The user specified a device that cannot be utilized as an input
or output device, e.g., trying to read from a line printer.
Suggested User Action
Reenter the command line with a legal device specified.
FLX -- INVALID DOS OR RT-11 FILE SPEC
or
FLX -- INVALID RSX FILE SPEC
Description
The file specifier does not conform to proper
specified operation could not be performed
device.

syntax, or the
on the specified

Suggested User Action
Reenter the file specifier with the proper syntax.
FLX -- INVALID SWITCH
Description
The user has specified a switch that is not a valid FLX switch or
does not conform to proper syntax.

3-24

FILE TRANSFER PROGRAM (FLX)
Suggested User Action
Reenter the command line with a correct switch specification.
FLX -- 1/0 ERROR

Description
One of the following conditions may exist:
1.

The specified device is not on-line.

A Files-11 volume is not mounted.

A hardware error has occurred (e.g., bad tape).

Suggested User Action
1.

Ensure that the device is on-line and
mounted (if it is an Files-11 volume).

Reenter the command line.

that

the

volume

FLX -- I/O ERROR DELETING LINKED FILE
Description
An uncorrectable error occurred while a DOS linked file was being
deleted.
Suggested User Action
No action required;
the file is
volume may be corrupted.

effectively

deleted,

but

the

FLX -- I/O ERROR INITIALIZING DIRECTORY
Description
One of the following conditions may exist:
1.

The specified device is not on-line.

The specified volume is not mounted.

A hardware error has occurred (e.g., bad tape).

Suggested User Action
1.

Ensure that the device is on-line and in operable condition.

Reenter the command line with the required switch specified.

FLX -- I/O ERROR ON COMMAND INPUT
Description
An unexpected error in command input was encountered from
an indirect command file, or TI:; FLX exits.
Suggested User Action
Restart FLX.

3-25

either

FILE TRANSFER PROGRAM (FLX)
FLX -- I/O ERROR ON FLX TEMPORARY FILE
Description
FLX encountered an error condition with its temporary file.
FLX
creates a temporary file on SY: for operations involving DOS-11
CT, DT, or MT. This error occurs when:
1.

SY:

is not on-line and mounted.

SY:

is write-locked.

A protection violation occurred.

An I/O error was encountered.

Suggested User Action
Correct the error condition and reenter the command line.
FLX -- I/O ERROR ON LIST FILE
Description
An error occurred on the output device during a /DI or /LI
sequence.
There is a hardware problem with the output device
(e.g., device powered down).
Suggested User Action
1.

Rectify the condition.

Reenter the command line.

FLX -- OUTPUT DEVICE FULL
Description
The DOS or RT-11 output volume does not contain enough space
the output file.

for

Suggested User Action
Delete all unnecessary files and reenter the command line.
FLX -- OUTPUT FILE SPEC NOT ALLOWED
Description
The user supplied an output file specifier
does not allow one.

for

command

Suggested User Action
Reenter the command without an output file specifier.

3-26

that

FILE TRANSFER PROGRAM (FLX)
FLX -- RECORD TOO LARGE
Description
FLX has detected an input record in a Files-11 transfer that is
larger than the specified or implied record size for the file,
i.e., the file is corrupted.
Suggested User Action
The file in question is unusable.
FLX -- REQUEST TERMINATED

LAST BLOCK NOT WRITTEN

Description
The <CR> reply was given by the user to indicate that no new
volume wouia oe mounted when an end-of-voiume was encountered on
cassette output. The block which FLX was attempting to write
when it encountered the end of the cassette has not been written.
Suggested User Action
No action is required;

the message is purely informational.

FLX -- SPECIFIED RECORD SIZE BAD, 512.

USED

Description
The record size specified with the /FA, /FB, or /IM switch is not
acceptable. A record size of 512(10) bytes is assumed.
Suggested User Action
This is a warning message;

no action is required.

FLX -- UNABLE TO ALLOCATE FILE
Description
There is no available space on the DOS or Files-11 volume for the
specified file; the volume is full.
Suggested User Action
Delete all unnecessary files and reenter the command line.
FLX -- UNABLE TO OPEN FILE
Description
A specified input or output Files-11 file could
Possible reasons are:
1.

Input file does not exist.

Volume is not mounted.

Protection violation occurred.

not

Suggested User Action
Correct the condition and reenter the command line.

3-27

opened.

FILE TRANSFER PROGRAM (FLX}
FLX -- UNABLE TO OPEN LIST FILE
Description
The list file cannot be opened under the specified filename and
UIC; the specified device may not be a valid Files-11 volume.
Suggested User Action
Reenter the command line specifying the correct filename and UIC.
FLX -- UNDIAGNOSABLE REQUEST
Description
FLX does not recognize the command line syntax.
Suggested User Action
Reenter the command line with the proper syntax.
FLX -- /CO FILES FROM INPUT DEVICE NOT ALLOWED UNLESS BL:

SPEC

Description
When transferring files from MT, PR, or CT, the /CO switch can be
only specified when the /BL switch is also specified.
Suggested User Action
Reenter the command line, specifying the /BL switch.
FLX --

* IN VERSION NUMBER NOT ALLOWED

Description
A wild card was detected in the version number field
specifier.

file

Suggested User Action
Reenter the command line
specified.

with

3-28

all

version

numbers

explicitly

CHAPTER 4
FILE DUMP UTILITY (DMP)

4.1

INTRODUCTION TO DMP

The File Dump utility (DMP) program produces a printed listing of the
contents of a file.
The listing can be directed to any suitable
output device: line printer, terminal, DECtape or disk. DMP runs in
either one of two modes:
1.

File Mode
In file mode, one input file is specified and all, or a
specified range (see /BL:n:m) of virtual blocks, of the named
file is dumped.
NOTES

A virtual block refers to a
relative block of data in a
file.

Virtual blocks are numbered
sequentially from 1 through
n, where n is the total
number of virtual blocks of
the file.

The input device must be a
Files-11 structured volume
and must be mounted via the
MCR MOUNT command.

Device Mode
In device mode, only the device is specified, and a specified
range (/BL:n:m) of logical blocks is dumped.
NOTES
a.

/BL:n:m
switch
is
required parameter.

A logical block refers to
the actual 512-byte block
on disk and DECtape, and

4-1

FILE DUMP UTILITY (DMP)
physical records on magtape
and cassette.
DMP
will
handle physical records up
to 2048 bytes in length.

4.2

Logical blocks are numbered
from 0 to n-1, where n is
the total number of logical
blocks on the device.

The volume to be dumped
must not be mounted.

INITIATING DMP

All RSX-llM utility programs can be initiated in several ways.
methods are described in Section 1.2. The methods for DMP are:

These

2_DMP_J
>DMP command string_)
>RUN •.. DMP_}
>RUN ..• DMP/UIC= [group ,member] _J
>RUN $DMP..,.j
>RUN $DMP/UIC=[group,member]..,.)

4.3· DMP COMMAND STRINGS
Commands to DMP are expressed in the following format:
outfile=infile/switch
For a complete description of file specifiers, see Section 1.3.

4.4

DMP SWITCHES

DMP switch specifications consist of a slash (/)
followed by a
2-character switch name, optionally followed by a value, which is
separated from the switch by a colon (:).
Eight switches are
recognized by DMP. These switches are described in Table 4-1.

4-2

FILE DUMP UTILITY (DMP)
Table 4-1
DMP Switches
Description

Switch
Default

Word mode octal dump

/AS

The /AS switch specifies that the data should be
dumped in ASCII mode.
The control characters
(0-37) are printed as t,
followed
by
the
alphabetic
character
corresponding
to
the
character code +100. For example, bell
(code 7)
is
printed
as
tG
(code 107).
Lower case
characters (140-177) are printed as%, followed by
the corresponding upper case character (character
code -4 0) .

/BA:n:m

This switch allows the user to specify a 2-word
base block address, where n = high-order base
block address
(octal), and m = low-order base
block address (octal). When specified, all future
block numbers will be added to this value to
obtain an effective block number. This switch is
useful to specify block numbers that exceed 16
bits. For example:
DMP >/BA: l: 0 __}

Specifies that all future block numbers
will
be
relative
to
65536(10)
(200000 (8)).
DMP>/BA: 0: 0 __}
Clears the base address.
/BL:n:m

Specifies the range of blocks to be dumped, where
n is the first block and m is the last block.
NOTES
1.

If the /BL:n:m switch is specified
in file mode, it specifies the range
of virtual blocks to be dumped.

If the /BL:n:m switch is specified
as /BL:O in file mode, no virtual
blocks are dumped. This is useful
when the user wishes to dump only
the header portion of the file
(see
/HD).

The /BL:n:m switch is a required
parameter in device mode. When used
in device mode, it spec i f ies the
range
of
logical blocks to be
dumped.

4-3

FILE DUMP UTILITY (DMP)
Table 4-1 (Cont.)
DMP Switches
Description

Switch
/BY

The /BY switch specifies that the data
dumped in byte octal format.

should

/HD

This switch is an optional parameter to be used in
file mode.
If specified, /HD causes the file
header as well as the specified portion of the
file to be dumped.
NOTE
If just the header portion of the file is
desired, the user can specify /HD/BL:O.
The file header is described in Appendix F
of the RSX-11 I/O Operations Reference
Manual.

/ID

Causes DMP's version to be identified.
This
switch may be specified on a line by itself at any
time.
Example:
>DMP /ID_)

/LB

Logical block. This switch gives the user only
the starting block number and a contiguous or
noncontiguous indication for the file.
Example:
DMP>TI:=DKO:RICKSFILE.DAT;3/LB__}
STARTING BLOCK NUMBER = 0,135163 C
File RICKSFILE.DAT, version 3 is a contiguous file
starting at block number 0,135163.
(See /BA:n:m
for block number description.)

/MD [: n]

Memory dump. This switch allows control of line
numbers.
Line numbers are normally reset to zero
whenever a block boundary is crossed.
The /MD
[:n]
switch
allows
lines
to
be numbered
sequentially for the full extent of the file,
i.e., the line numbers are not reset when block
boundaries are crossed. The optional value (:n)
allows the user to specify the value of the first
line number. The default is 0.
NOTE
Sample listings are presented in
B.4.

4-4

Appendix

FILE DUMP UTILITY (DMP)
4.5

DMP ERROR MESSAGES

DMP -- BAD DEVICE NAME
Description
The user has
specifier.

specified

invalid

device

name

file

Suggested User Action
Reenter the command line specifying the correct device.
DMP -- BLOCK SWITCH REQUIRED IN LOGICAL BLOCK MODE
Description
Self-explanatory -- /BL switch must be specified.
Suggested User Action
Reenter the command line with the /BL switch specified.
DMP -- CANNOT FIND INPUT FILE
Description
The requested file cannot be located in the specified directory.
Suggested User Action
Reenter the command with the correct filename and UIC specified.
DMP -- COMMAND SYNTAX ERROR
Description
The user has entered a command in a format that does not
to syntax rules.

conform

Suggested User Action
Reenter the command line with the correct syntax.
DMP -- FAILED TO ASSIGN LUN
Description
The user has specified an illegal device in a file specifier.
Suggested User Action
Reenter the command line with the correct device specified.

4-5

FILE DUMP UTILITY (DMP)
DMP -- FAILED TO READ ATTRIBUTES
Description
The user has attempted to access a file for
have read access privileges.

which

does

not

the

Suggested User Action
Rerun DMP using a UIC which has read
file.

access

privileges

DMP -- ILLEGAL SWITCH
Description
The user has specified a switch that is not a valid DMP switch or
used a legal switch in an invalid manner.
Suggested User Action
Reenter the command line with the correct switch specified.
DMP -- I/O ERROR ON INPUT FILE
or
DMP -- I/O ERROR ON OUTPUT FILE
Description
One of the following conditions exists:
1.

A problem exists on the physical device (e.g., device
down) .

File is corrupted or the format is incorrect.

Output volume is full.

Suggested User Action
1.

Determine which of the above conditions may exist.

Rectify the condition.

Reenter the command line.

4-6

cycled

FILE DUMP UTILITY (DMP}
DMP -- NO INPUT FILE SPECIFIED
Description
The user has terminated a command without entering an input
specifier.

file

Suggested User Action
Reenter the command line with an input file specified.
DMP -- NO LISTS OR WILD CARDS ALLOWED
Description
The user either entered a command with more than one input
output filename or entered a wild card in a file specifiere

Suggested User Action
Reenter the command line with only one input file specifier
one output file specifier. No wild card specifiers allowed.

and

DMP -- OPEN FAILURE ON INDIRECT FILE
Description
The requested indirect command file does not exist as
One of the following conditions may exist:
1.

The file is protected against access.

A problem exists on the physical
cycled down) .

The volume is not mounted.

The specified file directory does not exist.

The named
directory.

file

does

not

exist

device

specified.

(e.g.,

the

specified

Suggested User Action
1.

Determine which of the above conditions may exist.

Rectify the condition.

Reenter the command line.

4-7

device

FILE DUMP UTILITY (DMP}
DMP -- OPEN FAILURE ON INPUT FILE
or
DMP -- OPEN FAILURE ON OUTPUT FILE
Description
One of the following conditions may exist:
1.

The file is protected against access.

The named
directory.

The volume is not mounted.

The specified file directory does not exist.

A problem exists on the physical
cycled down} •

file

does

not

exist

device

the

(e.g.,

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

4-8

specified

device

CHAPTER 5
LINE TEXT EDITOR (EDI)

5.1

INTRODUCTION

The Line Text Editor (EDI) is an interactive context-editing program
that provides the capability to create and modify source programs and
other ASCII text material. EDI may be directed to read a line, or
group of lines, from the input file into an internal buffer by means
of terminal commands. The user can then, by means of additional
commands, examine, delete and change text, and insert new text at any
point in the buffer. When the line or block of lines has been edited,
the user can issue a command to write the data into a new file.
EDI is most frequently used to modify MACRO and FORTRAN source
programs, but it can also be used to edit any ASCII text material.
The EDI commands are described in sections 5.4 and 5.5.

5.2

USING EDI

This section is designed to give the user a step-by-step
using the RSX-llM Line Text Editor.

5.2.l

approach

Preparing to Run EDI

Before initiating EDI, the user must consider the following:
format

All

files.

other

EDI can operate only on Files-11
file formats are rejected.

The output file generated by EDI always resides on the same
device as the input file. The outpµt file cannot be directed
to another device.
Example:
If a user has a file on DECtape and he wants to edit
file and store the resulting file on disk, he must:

that

Transfer the file to disk and perform the editing there.

Edit the file on DECtape and then transfer
disk using PIP.

5-1

the

file

LINE TEXT EDITOR (EDI}

5.2.2

If a device other than SYO: is to be utilized,
mounted via the MCR MOUNT command.

must

If other than the latest version of a file is to be edited,
the desired version number can be explicitly stated in the
file specifier. This file will be opened as the input file
and the version number of the output file will be one greater
than the latest version of the file. If a command issued
during the editing session closes the explicit version of the
file without terminating the session (e.g., a TOF command),
both output and input files are closed, and the latest
version of the file is reopened as the input file.

Initiating EDI

All RSX-llM utility programs can be initiated in several ways.
methods are described in Section 1.2. The methods for EDI are:

These

~EDI_}

>EDI command string _J
>RUN ••• EDI_}
>RUN ... EDI/UIC=[group,member],.J
>RUN $EDI_}
>RUN $EDI/UIC=[group,member]_}
If any format except ">EDI command string" is .used,
following prompting message:

EDI

issues

the

At this point, the user must enter a file specifier for the file to be
edited. The file specifier is in the following format:
dev: [uic]filename.typ
If the file specifier is a new file (i.e., the file specified cannot
be found on the specified device) , the assumption is that the user
wishes to create a new file with the given filename. EDI then prints
the following comment lines:
[CREATING NEW FILE]
INPUT
and enters Input mode.
NOTES
1.

Edit control modes
Section 5.2.3.

If the message "FILE DOES NOT EXIST" is
displayed, it means that the specified
user file directory is nonexistent.

5-2

are

described

LINE TEXT EDITOR (EDI}
3.

EDI does not accept
file specifiers.

indirect

command

The abbreviation "filespec" is used in
the command formats to indicate file
specifier.

If an existing filename is specified, EDI prints:
[PAGE l]

*
and waits in Edit mode for the first command to be issued.
If the ">EDI command string" format is used, the p~ompt message (EDI>}
is not issued, and EDI starts up in either Input or Edit mode,
depending on the filename specified: Input mode if the filename is
new; Edit mode if the filename already exists.
NOTE
At program startup, after the input file
has been identified and the output file
has been created, the program is ready
for commands. The first line available
to the user for editing is always one
line above the top of the input file or
the block buffer.
This allows
for
inserting text at the beginning of the
input file or the block buffer.
If,
however, the user wishes to manipulate
the first line of text, he must perform
a NEXT operation to make that line
available.

5.2.2.1 Defaults in File Specifiers - If any of the elements of the
file specifier, except filename and type for input file, are omitted,
EDI uses a default. The default values-for both- the input and the
output files are listed in Table 5-1.

5-3

LINE TEXT EDITOR (EDI)
Table 5-1
EDI Default File Specifiers

Element

Default Value
for Input File

Default Value
for Output File

dev:

SYO:

Same as input device

[uic]

UIC under which EDI
is currently running

Same as input [uic]

filename

No default--must
be specified

Same as input filename

.typ

No default--must
be specified

Same as input file type

;version

Latest version

Latest version+l

5.2.3

EDI Control Modes

EDI is capable of operating in two control modes:
•

Edit mode (command mode)

•

Input mode (text mode)

Edit mode is invoked automatically at program startup, if an
file is being edited.

existing

When in Edit mode, EDI issues an asterisk(*) as a prompt.
Also EDI
accepts and acts upon control words and data strings to open and close
files; to bring in lines of text from an open file;
to change,
delete, or replace information in an open file; or to insert single
or multiple lines anywhere in a file.
Input mode is invoked automatically at program startup
if
a
non-existent file is specified.
When Input mode is active, lines
entered at the terminal are treated as text to be inserted into the
output file.

5.2.4

Changing Control Mode

If EDI is in Edit mode and the user wishes to enter Input mode, the
INSERT command is issued, followed by a carriage return. This will
place EDI in Input mode, and all lines entered from this point will be
added into the file as new text, following the current line.
NOTE
The INSERT command
section 5.4.3.8.

5-4

described

LINE TEXT EDITOR (EDI)
If EDI is in Input mode and the user wishes to switch to Edit mode, a
carriage return is entered as the first character in a line. EDI will
then issue the prompting character * , which signifies that the Edit
mode is active.

5.2.5

Text Access Modes

EDI provides the user with two modes
lines of text in the input file:

accessing

and

manipulating

•

Line-by-line Mode - Allows the user to access lines of text
one line at a time (a line is a string of characters
terminated by a carriage return).

•

Block Mode - Allows the user to access a block of lines,
a line-by-line basis.

NOTE
Block mode is the default text access mode.

5.2.5.1 Line-by-Line Mode - In this mode, a single line is the unit
of the input file available to the user for modification at any point.
Line-by-line mode is entered by issuing a BLCCK OFF command, and is
terminated by issuing a BLOCK ON command. The BLOCK ON/OFF command is
described in section 5.5.1.1.

The line currently available is specified by a pointer, which can be
thought of as moving sequentially through the file, starting just
before the first line in tne r11e. ~ne user can manipulate the line
pointer by using the editing commands which are described in sections
5.4 and 5.5.
When a file is opened at the beginning of an editing session, the
first line of that file can be brought into memory and made available
for modification. This line remains in memory until the user requests
that a new line be brought in. The pointer then moves down the file
until the line requested is encountered. That line is brought into
memory and, as the "current" line, can be modified. ~hen a new line
is brought in, the old, or previous, line is written into the output
file, and is no longer accessible unless the user issues a TOP command
(the TOP command is described in Section 5.5.3.10). The TOF command
can be used to move the line pointer to the top of the file; however
TOF always causes EDI to re-enter the block mode (see Section
5.4.3.15).

Block Mode - In this mode, a user-specified portion (80 lines
is the default) of the input file is held in the block buffer for
editing until the user requests that the contents of the buffer be
added to the output file.
5.2.5.2

5-5

LINE TEXT EDITOR (EDI)
When the user is operating in block mode, EDI executes commands only
with respect to that portion of the input file currently in the
buffer. The lines of text in the buffer can be addressed backward as
well as forward within the buffer, thus allowing the user to back up
to a previously edited line without having to process the entire block
or file all over again, or having to issue a TOF command.

5.2.5.3 Line-by-Line Vs. Block Mode - Table 5-2 provides a
summary of the differences between line-by-line and block mode.

brief

Table 5-2
Line-by-Line vs. Block Mode
Block Mode

Line-by-Line Mode
One line available for
modification at a time
(see third statement below
for exception).

Entire block of lines available
for modification at a time, on
a line-by-line basis.

forward through
I accessed
the file.

Lines can only be

Lines can be accessed forward
and backward within a block.

Locative commands, those
which allow the user to
locate a string of text
for modification, can be
applied to search the
entire file.

Locative commands search only
the block that is in memory.
To search more data, another
block must be read in.

NOTE
The line pointer, regardless of
mode utilized, always points
iirst character- in the line.

5.2.6

editing
to the

Text Files

The following sections describe how data may be added
the operations performed on output files.

5-6

files,

and

LINE TEXT EDITOR {EDI)
5.2.6.1

Input and Secondary Files - EDI accepts input from:

The input terminal {i.e., commands and text entries).

Files-11 volumes which contain
a.

The file to be edited;

A secondary file;

A save file;

A macro file.

The input file is always preserved. To delete the input file, the
user can use the CLOSE-AND-DELETE command or the EXIT-AND-DELETE
command, or PIP can be utilized. Any system failure, EDI failure, or
lack of space on the output volume does not cause the loss of the
input file. Only the output file is affected. The output file is not
completely destroyed;
it is a truncated version of the input file
containing all of the edits to the point of failure.

5.2.6.2 Output Files - The output device is defaulted to the input
device, as well as the same directory and filename, with the version
number incremented by one. If the user wishes to change any of the
file parameters (except device and directory), he can specify a
completely new file specifier when closing a file or exiting at the
end of an EDI session.

5.2.7

Terminal Conventions

5.2.7.l Carriage Return - The carriage
effects, depending on how it is used:

retutn

has

the

f ollcwing

When issued in place of an

input
return causes EDI to terminate.

When issued in Edit mode, carriage return causes the next
line to be printed and that line to be the current line.

When issued in Input mode as the first character in the line,
carriage return causes a return to Edit mode.

When issued alone after an INSERT
puts the user in Input mode.

command,

carriage

return

5.2.7.2 Character Erase (RUBOUT) and Line Delete (CTRL U) - Two
terminal commands are provided which permit the deletion {erasure) of
individual characters in a line or the deletion of an entire line.
RUBOUT deletes individual characters.
CTRL/U deletes the current
input line. For a complete description of these commands, see the
RSX-llM Operator's Procedures Manual.
During editorial operations, neither the
affects previously prepared text.

5-7

RUBOUT

nor

CTRL/U

command

LINE TEXT EDITOR (EDI)
5.2.8

EDI Command Conventions

5.2.8.l Use of* - The asterisk character, *, can be used in place of
a numeric argument and is equal to 32767(10).
Example
The following command would result in the printing of the remainder of
the block buffer or file.
PRINT

5.2.8.2 Search String Constants - In a number of the EDI commands,
the user must identify a string(s) of characters to be located and/or
changed. To reduce the necessary terminal entries, the more advanced
user can utilize the following special string constructs.
In these
special cases, the three periods
( ... ) are used to represent any
number of intervening characters.
Case 1. string-I .••
string-2

- Any string which starts with string-I,
continues with any number of intervening
characters, and ends with string-2.

Case 2 . . • . "string"

- Any string which starts at the beginning
of
the current line and ends with
'·string".

Case 3.

- Any string which starts with "string"
and ends at the end of the current line.

Case 4.

"string" •..

- A string which is the current line.

Examples
THIS IS A SAMPLE OF SPECIAL STRING CONSTRUCTS.
Using the preceding
sentence and the commands specified in each case, observe the results:
Case 1.

C /S A ... E O/S AN EXAMPLE 0
results in
THIS IS AN EXAMPLE OF SPECIAL STRING CONSTRUCTS.

Case 2.

C / ... SPEC/THIS IS AN EXAMPL~ OF SPEC
results in
THIS IS AN EXAMPLE OF SPECIAI STRING CONSTRUCTS.

Case 3.

C /STRING •.. /EDI STRING CONSTRUCTS.
results in
THIS IS A SAMPLE OF SPECIAL EDI STRING CONSTRUCTS.

Case 4.

C / ... /EXAMPLES OF SPECIAL EDI CONSTRUCTS.
results in
EXAMPLES OF SPECIAL EDI CONSTRUCTS.

5-8

LINE TEXT EDITOR (EDI)
5.3

EDI ERROR REPORTING

Errors encountered by EDI are reported to the user by appropriate
error messages displayed on the input terminal. For the purpose of
clarification, these messages (and their descriptions and suggested
user actions) are described as four separate classes of errors. These
classes are:
•

Command level informational error messages

•

File access warning messages

•

Error messages requiring EDI restart

•

Fatal error messages

Input and output files are affected differently by the occurrence of
errors.
Input files are always preserved. The resulting output file
is a truncated version of the input file, containing all edits
completed up to the time of the error.

5.3.l

Command Level Informational and Error Messages

Messages in this class indicate information that is designed to be
helpful to the user or identify errors that were encountered in the
previous command. All messages in this class are enclosed within
square brackets and followed by a prompt for a new command. These
messages are described in Section 5.6.1.

5.3.2

File Access Warning Messages

File access warning messages represent attempts on the part of the
user to access directories, files, or devices that are not present in
the host system or which are protected against access.
Each message
is prefixed with:
EDI -and, after the message is displayed, EDI returns to command level and
requests input by issuing an asterisk. These messages are described
in Section 5.6.2.

5.3.3

Error Messages Requiring EDI Restart

The error messages that result in restarting the editing session are
caused by conditions encountered by EDI that make it impossible to
continue the current editing session. EDI closes all open files (with
the exception of the secondary input file), reinitializes, and then
prompts for the next file to be edited.
Each message is prefixed
with:
EDI -These messages are described in Section 5.6.3.

5-9

LINE TEXT EDITOR (EDI)
5.3.4

Fatal Error Messages

Fatal error messages represent system and/or hardware error conditions
which make it impossible for EDI to continue execution. All files are
closed and EDI terminates its execution.
Each error message is
prefixed with:
EDI -and followed by the exit message:
[EXIT]
on the next line.

5.4

These messages are described in Section 5.6.4.

BASIC EDI OPERATION AND COMMANDS

EDI can be used to create new files, enter new text into existing
files, and edit new and existing files.
These operations are
described in this section, along with the basic EDI commands which are
required by the new user.

5.4.1

Basic EDI Operations

5.4.1.1 Creating a File - To create a file using EDI, a nonexistent
filename is used as the file specifier. This causes EDI to print the
following lines on the user terminal:
[CREATING NEW FILE]
INPUT
and to enter Input mode. The user then types the desired text on the
terminal, observing the required spacing within the line. When the
typing of the line is complete, the line is terminated by a carriage
return. The next line is entered in an identical manner.
During file creation, input errors on lines which have been terminated
by a carriage return are corrected by switching to Edit mode. This is
accomplished by typing a carriage return as the first character in a
line.
Once Edit mode is entered, EDI issues a prompt (*) to indicate
that it is ready to receive an edit command. If additional text is to
be inserted after the corrections have been completed, the user must
locate the text line preceding the desired entry point and return EDI
to the Input mode by typing an I, followed by a carriage return. The
user can switch between the Input and Edit modes, as required, by
following the procedures described in this paragraph.
When the file creation and necessary corrections have been completed,
the user must switch to Edit mode to exit from EDI. The output file
is stored with the file specifier used when EDI was initiated, or it
can be renamed with the EXIT command.

5-10

LINE TEXT EDITOR (EDI}
S.4.1.2 Entering Text Into a File - Text can be entered into a file
in either Input or Edit mode. Since there are differences between the
two modes of text entry, each is described separately:
•

Entering Text in Input Mode - When EDI is in Input mode, the
information typed on the terminal is inserted in the line
following the current line. As each line is terminated by a
carriage return, the line pointer is moved down one line and the
line which was just entered becomes the current line.
EDI does
not recognize any command and remains in Input mode until a
carriage return is typed as the first character of a line.
Then
EDI switches to Edit mode.

•

Entering Text in Edit Mode - When EDI is in Edit mode, text can
be appended to the current line (via an ADD or ADD & PRINT
command), inserted as a line following the current line (via an
INSERT command), or used to replace the current line (via a
RETYPE command). Each of the commands inserts only a single line
of text;
the command must be reissued to insert another line.
Other EDI commands can be used to modify a single line or a
complete file, but the ADD, ADD & PRINT, INSERT, and RETYPE
commands are mainly the commands used to insert text in Edit
mode.

S.4.2

Editing a File

Editing operations are performed only when in Edit mode.
available with EDI are categorized as follows:

The commands

•

Setup commands select data modes, select and open
operating conditions, etc.

files,

select

•

Input/Output commands transfer
output files.

input

files

and

•

Locative commands control the positioning
pointer.

current

line

•

Text modification and manipulation commands display,
modify the text.

change

and

•

Close operation commands terminate editing operations.

text

from

the

The various commands are described in Sections S.4.3 and S.S.
Two text access modes are available with EDI, and a command is
available
that
allows
the user to select either mode.
The
line-by-line mode allows the user to locate a line anywhere within a
file, but the current line pointer must always be moved down through
the file being edited. Once a line is passed, the pointer must be
moved to the beginning of the file to access that line agai~.

S-11

LINE TEXT EDITOR (EDI)
The second text access mode, which is the more frequently used of the
two modes, is block mode. In block mode, a block of data is stored in
the block buffer, and the line pointer can be moved up or down through
the data block.
The default size of the data block is 80 lines.
Since data is packed in the block buffer, the user can increase or
decrease the data block size, as required, or he can read additional
data blocks into the block buffer as long as the buffer capacity is
not exceeded. Once the contents of the block buffer are established,
only the contents of the block buffer are available for editing
operations.
If another block is to be edited, the block buffer must
be renewed before new data can be edited. Because of this limitation
in block mode, commands have been included in EDI that allow the user
to specify a string or page number not in the present contents of the
block buffer.
Then, EDI performs the necessary search and renew
operations to locate the desired data and load it into the block
buffer. After selecting edit mode, the user moves the line pointer to
locate the line to be changed. The user then can perform editing
operations, which can consist of adding, changing, modifying or
deleting data, with a wide variety of commands. If a common change is
required more than once in a line or to more than one line, commands
are available to perform these operations without requiring the user
to locate each occurrence and enter the required command. Storage for
up to three EDI macro definitions is available so that frequently-used
EDI commands or string of EDI commands can be stored, called, and
executed, when required.
A single EDI command can insert the contents of a save file into the
file or data block being edited. Another command can delete a number
of lines and place EDI in Input mode so new lines can be entered via
the terminal in place of the original lines. Storage capacity of the
block buffer must never be exceeded;
surpassing buffer capacity
during an operation is considered an EDI error condition. The data
which caused the overflow will be deleted.
Commands are included in EDI to
operations:

perform

the

following

input/output

•

Write the contents of the block buffer into the output file
and renew the contents of the block buffer with the next
input data block.

•

Write the contents of the block buffer into the output
and erase the present contents of the block buffer.

file

•

Read the next block
buffer.

block

•

Write edited text into the output file and return to top
file.

group

blocks

into

the

In all cases, the input/output commands have no effect on the input
file.
The input file can be deleted only during closing operations.
In most cases, an editing session is terminated by transferring the
contents of the block buffer and the remaining lines in the input
file, in that order, to the output file, and then closing the files.
Whether EDI is terminated is dependent upon which closing command is
used. The available closing commands are as follows:

5-12

LINE TEXT EDITOR (EDI)

•

Close the current editing session and remain in EDI .

•

Close the current editing session, delete the input file and
remain in EDI.

•

Exit EDI without deleting the input file •

•

Exit EDI and delete the input file .

•

Remain in EDI but delete both output and input files .

EDI is a versatile editing tool which enables the user to edit all
types of text files. In the following descriptions of the commands,
examples are included using text lines and files to illustrate the
function of the various commands.
Text has been used in these
examples so that the intent of the command is not lost in the syntax
of a language which the new user may not understand.

5.4.3

Basic EDI Commands

The basic EDI commands listed in Table 5-3 allow the user to create a
file, modify a file by adding, deleting, or changing its contents, and
exit after the desired operations have been completed. These commands
are the most important commands to the new user; therefore, they have
been presented as a group near the beginning of this section to
provide the new user with an understanding of some of the more
important EDI capabilities. As the user becomes familiar with EDI
operations, the additional commands described in Section 5.5 will
allow utilization of the full EDI capabilities.

5-13

LINE TEXT EDITOR (EDI)
Table 5-3
Basic EDI Commands
Command

Command Format

ADD

A[DD]

ADD & PRINT

AP (string)

Append {string) to
current
line and print resultant line.

CHANGE

[n]C[HANGE] /string-1/
string-2/

Replace string-1 with string-2
n times in the current line.

CTRL Z

Close files
and
editing session.

DELETE

D [ELETE]
or
D[ELETE]

DELETE &

I PRINT

Description

(string)

DP [n]

Append
line.

[n]
[-n]

EX[IT]

INSERT

I[NSERT]

[filespec]

I NEXT

current

terminate

Same as
DELETE except
current line is printed.

new

files, name output file
I Close
and terminate editing session.

(string)
II

LOCATE

Delete current line and n-1
lines if n is (+); delete n
lines preceding current line
if n is {-).
[-n] operates in
block mode only.

or DP -nJ

EXIT

{string)

(string)
following
Enter
current line or enter
input
mode if
(string)
is not
specified.

[n]L[OCATE] {string)

Locate "nth"
string.

occurrence

N[EXT]

Establish new current line n
lines away from current line.

N[E~T]

[n] or
[-n]

NEXT & PRINT

NP [n]

or NP [-n]

P [RINT]

[n]

Print current line and the
The last
next
n-1 lines.
printed line
is
the
new
I current line.

RENEW

REN [EW]

[n]

Write current block to output
file and read new block from
input file {block mode only) .

RETYPE

R[ETYPE]

(string)

Replace current
line
with
string;
or delete current
line if {string) is null.

TOP OF FILE

TOF

Establish
and
current line.

new

Return to top of input file
and save all pages previously
edited.

5-14

LINE TEXT EDITOR (EDI)
5.4.3.1

ADD Command

Function
This command causes the specified string to be appended to
line.

"-~-

L.11C:

_, .

____ "'"'

..._U.L.LC:UL.

Format
A[DD]

(string)

Example
The following command completes the line HAPPY DAYS ARE HERE
~A

5.4.3.2

AGAIN ...)

ADD AND PRINT Command

Function
This command performs the same function as
that the resultant line is printed.

the

ADD

command,

except

Using the same line as the ADD command, the following
the new line to be printed as folrows:

command

causes

Format
AP (string)
Example

!AP

AGAIN . ._)

HAPPY DAYS ARE HERE AGAIN.

5.4.3.3

CHANGE Command

Function
This command searches for string-1 in the current line and, if found,
replaces it with string-2.
If string-1 is given, but cannot be
located in the current line, EDI prints [NO MATCH] and returns an *
prompt.
If string-1 is null (not given), string-2 is inserted at the
beginning of the line. If string-2 is null, string-1 is deleted from
the current line. The search for string-1 begins at the beginning of
the current line and proceeds across the line until a match is found.
The delimiters may be any matching characters which are not contained
in the specified string. Slashes are shown in the example. The first
character following the command is considered the beginning delimiter
and the next matching character ends the string.
Thus, characters
used as delimiters must not appear in the string itself. The closing
delimiter is optional.
A numeric value "n" preceding the command results in the
occurrenceE
of
string-1 being changed to string-2.

5-15

first "n"
For each

LINE TEXT EDITOR (EDI)
replacement of string-1 with string-2, the entire line is rescanned
beginning at the first character in the line. This allows the user to
generate a string of !l characters as shown in the example below.
If no match occurs, a [NO MATCH] message is displayed.
Format
[n]C[HANGE] /string-1/string-2[/]
Example
If a line contained
A;;;;;B;C;D.

5.4.3.4

A;B;C;D,

then

the

command

4C/;/;;

generates

CTRL/Z Command

Function
Typing CTRL/Z (holding the CTRL key down while typing the letter Z)
terminates the editing session. If an output file is open when CTRL/Z
is typed, then all remaining lines in the block buffer and the input
file are transferred (in that order) into the output file, all files·
are closed, and EDI exits. These actions occur if EDI is prompting
for command input with an asterisk or is in Input mode. If EDI is
prompting for another file specifier when CTRL Z is entered, all files
are closed (including any open secondary input file), and EDI exits.

5.4.3.5

DELETE Command

Function
This command causes lines of text
manner:

deleted

the

following

If n is given as +n, the current line and n-1 lines following
the current line are deleted. The new line available for
modification {the new current line) is the line following the
last deleted line.

If n is given as -n, the current line is not deleted, but the
specified number of lines that precede it are deleted. The
line pointer remains unchanged.

If n is null, the current line is deleted, and the next
becomes the new current line.
NOTES
1.

A negative value for n can be used
in block mode.

only

If n is not specified, a value of +l
assumed.

5-16

line

LINE TEXT EDITOR (EDI)
Format
D[ELETE]

[n]

or
D[ELETE]

[-n]

Example
To delete the previous five lines in the block buffer,
command is typed:
~D

5.4.3.6

the

following

-5..)

DELETE AND PRINT Command

Function
This command performs the same function as the DELETE command, except
that the new current line is printed when the deletion of all lines
has been completed.
Format
DP [n]
or
DP [-n]
NOTES
1.

If n is not specified, +l is assumed.

A negative value for n can be used
in block mode.

only

Exam;ele
If the following lines are contained in a file:

THIS IS LINE 1
THIS IS LINE 2
THIS IS LINE 3
THIS IS LINE 4
and the line pointer is at the first
obtains the results shown below:
~DP

2../

THIS IS LINE 3

5-17

line,

the

following

command

LINE TEXT EDITOR (EDI)
5.4.3.7

EXIT Command

Function
This command transfers all rema1n1ng lines in the block buffer and
input file (in that order) into the output file, closes the files, and
terminates the editing session. If file specifier is used, the output
file is renamed to the specified filename.
Format
EX[IT]

[filespec]

Example
The following command terminates the editing session, without renaming
the output file, and causes the following printout:
!EX.)
[EXIT]

5.4.3.8

INSERT Command

Function
This command inserts "string" immediately following the current line.
The string becomes the new current line.
If "string" is not
specified, the user enters Input mode.
Format
I (NSERT)

{string)

Example
! I TEXT INSERT IN EDIT MODE __)

Inserts
a
immediately
line.

~L ABC.J

Locates a line containing ABC.

ABC IS THE START OF THE ALPHABET

This is the line found.

-*I ....J

An I followed

TEXT INSERT 1 IN INPUT MODE...)

return causes EDI to

switch

TEXT INSERT 2 IN INPUT MODE_.}

a series

ETC._}

of new lines can be input
following the current line.

Input

line
of
text
after the current

mode

and

carriage

A carriage return as the first
character in a line causes EDI
to return to Edit mode and
prompt for a new command.

5-18

LINE TEXT EDITOR (EDI)
5.4.3.9

LOCATE Command

Function
This command causes a search of the block buffer or input file,
beginning at the line following the current line for "string", which
may occur anywhere in the line sought. If "string" is not specified,
the line following the current line is considered a match. A numeric
value "n" preceding the command results in locating the "nth"
occurrence of "string".
The line pointer is positioned to the line
containing the located string. LOCATE applies to the block buffer if
EDI is in block mode and to the input file if in line-by-line mode.
When the line is located, it is printed, unless a VERIFY OFF command
is in effect.
Format
[ n] L [OCATE]

(string)

Example
The following command can be used to locate the line
HERE AGAIN.

HAPPY

DAYS

ARE

The file or block buffer is checked, and the line is printed
is located, if the VERIFY ON command is in effect.

when

5.4.3.10

ppy __;

NEXT Command

Function
This command establishes a new current line at n lines, plus
from the current line.

v ..

rn ... uu.:>,

Format
N [EXT]

[n]

or
N [EXT]

[-n]
NOTES

If n is not specified, a value of +l
assumed.

A negative n can be
block mode.

the

moves

the

used

only

Example
In the block mode, the following
pointer back five lines:

command

~N -5 _.}

5-19

current

line

LINE TEXT EDITOR (EDI)
5.4.3.11

NEXT PRINT Command

Function
Same as NEXT command, except the new current line is printed.
Format
NP [n]
or
NP [-n]
NOTES
The following conventions can be used in
place of issuing a complete NP command.
1.

Pressing the <CR> key is the same as
NP+l command.

Pressing the <ALTMODE> (or ESCape)
key
while in the block mode is the same as
an NP-1 command.

If n is not specified, then a
+l is assumed.

value

Example
Assume the following four lines are contained in the file and the line
pointer is at the first line.
LINE 1 OF THE FILE
LINE 2 OF THE FILE
LINE 3 OF THE FILE
LINE 4 OF THE FILE
If the following command is issued, EDI
printout:

would

return

the

following

~NP 2~
~INE

5.4.3.12

3 OF THE FILE

PRINT Command

Function
This command prints out the current line and the next n-1 lines on the
terminal;
the last line printed becomes the new current line.
(Compare with the TYPE command, Section 5.5.4.13.)

5-20

LINE TEXT EDITOR (EDI}
Format
P [RINT]

[n]
NOTE

If n is not specified, a value of +l
assumed.

Example
The following
commands:

example

illustrates

both

the

and

Before
File B

File A

Line v

Line A
Q i s the
Line B

Line w

Line Pointer

Line c

Line

Line D

Line y

Line

Line z

5_)

~TYPE

~PRINT

Line v

Line B

Line w

Line x

T.: - -

l.J.1.Jl~

Line

Line D

Line

Line E

Line z

:!!..

After
File A

File B

Line A

Line v

Line B

Line w

Line c

Line x

Line D

Line

Line E

Line z

5-21

5_.)

the

TYPE

LINE TEXT EDITOR (EDI}
5.4.3.13

RENEW Command

Function
This command writes the current block buffer into the output file and
reads a new block from the input file.
The value n, which is
optional, specifies how many times the RENEW command is to be
repeated.
If n is specified, the process is repeated n times, the
inter-blocks are written into the output file, and the last block is
left in the block buffer. If n is not specified, it is assumed that
the process is to be performed only once. This command can be used
only in the block mode.
Format
REN[EW]

[n]

~RENEW

10__)

Example

In this example, ten consecutive blocks are transferred from the input
file to the block buffer. The initial contents of the block buffer
and the next nine blocks are transferred to the output file.
The
current line pointer is pointing to the first line in the tenth block,
which is currently in the block buffer.

5.4.3.14

RETYPE Command

Function
This command causes the current line to be replaced by
"string" is not specified, the line will be deleted.

"string".

Format
R[ETYPE]

[string]

Example
~R

THIS IS A NEW LINE_.}

In this example, the string "THIS IS A NEW LINE" replaces the
line.

5.4.3.15

current

TOP OF FILE Command

Function
This command causes a return to the top of the input file and saves
previously
edited
text.
If this command is issued when in
line-by-line mode, EDI will switch to block mode after saving 'the
edited data. The first block is read into the block buffer.

5-22

LINE TEXT EDITOR (EDI)
Format
TOF
Example
~TOF_.)

This command causes the previously edited pages to be written into the
output file and the current line pointer to be reset to the top of the
input fi1e. The first block is read into the block buffer.

5.4.4

S~mple

Editing Session

Section B.2.1 contains a sample EDI editing session
how EDI commands can be used to edit a file.

5.5

5.5.1

that

illustrates

EXTENDED EDI COMMANDS

Setup Commands

The setup commands required at the start of an editing session allow
the user to provide parameters for EDI features. Table 5-4 contains a
list of these commands.

5-23

LINE TEXT EDITOR (EDI)
Table 5-4
EDI Setup Commands

Command

Command
Format

BLOCK ON/OFF

BL[OCK] ON or
BL[OCK] OFF

Switch text access modes.

CONCATENATION
CHARACTER

CC [letter]

Change concatenation character
to
specified
character
(default is &) •

OPENS

OP[ENS] filespec

Open specified secondary file.

OUTPUT ON/OFF

OU[TPUT] ON or
OU[TPUT] OFF

Continue/Discontinue transfer
to output file (line-by-line
mode) .

SELECT PRIMARY

Reestablish
input file.

SELECT SECONDARY

SIZE

Description

primary

file

Select opened secondary
as input file.

as
file

SIZE n

Specify maximum
number
of
lines to be read into block
buffer (default is 80 lines).

TA[B] ON or

Turn automatic tabbing on or
off. If TAB ON is selected,
all text lines are moved over
8 spaces, unless the line has
a label followed by a colon,
or the line starts with a
semicolon in column 1.

UPPER CASE
ON/OFF

UC ON or UC OFF

Convert lower-case characters
entered
from
terminal
to
upper-case characters.

VERIFY ON/OFF

V[ERIFY] ON or
V[ERIFY] OFF

Select whether locative and
change commands are verified.

TAB

I TA [B] OFF

5-24

LINE TEXT EDITOR (EDI)
5.5.l.l

BLOCK ON/OFF Command

Function
This command allows the user to switch between block mode and
line-by-line mode.
When BLOCK ON is issued, block mode becomes
active, and the next block of text is brought into the block buffer.
When BLOCK OFF is issued, the current block being processed is written
to the output file, and line-by-line mode becomes active, with the
first line from the next sequential block in the input file as the
current line.
NOTES
1.

If a conflicting BLOCK command is issued
(e.g., BLOCK ON is issued when EDI is
already in BLOCK ON mode) : the command
is ignored.

BLOCK ON is the default text access
mode. It is assumed when neither ON nor
OFF is specified.

Format
BL[OCK] ON
or
BL[OCK] OFF
Example
~BLOCK

ON..)

This command causes EDI to switch to block mode and the next block
text to be read into the block buffer.

5.5.1.2

CONCATENATION CHARACTER Command

Function
This command allows the user to change the command concatenation
character to the specified character.
If none is specified, the
ampersand (&) is assumed. The concatenation character links two EDI
commands on the same command line.

5-25

LINE TEXT EDITOR (EDI)
Format
CC [letter]
Example
~c
~L

:..J
A&B:C /A&B/ABC/_J

~cc & __)

In this example, the string to be located contains an ampersand.
Therefore, the default concatenation character must be changed to
something else before the line can be located.
The first command line changes
from & to ..

the

default

concatenation

character

The second command line instructs EDI to locate the string A&B and
change string A&B to ABC.
(Note: this line contains two commands
which are concatenated by the new concatenation character, ":".)
The third command line changes the concatenation character back to the
normal default value, &.

5.5.1.3

OPENS Command

Function
This command opens the specified secondary input file.
The primary
input file, if any, remains open and subsequent text is read from
primary input file until the secondary input file is selected for
input (see Section 5.5.1.6 for a description of SELECT SECONDARY
command).
Format
OP[ENS] filespec
Example
~OPENS

RICKS.MAC_}

~SS../
~READ

l__J

In this example, the file RICKS.MAC is opened as a secondary
file, selected for input, and the first block is read in.

5.5.1.4

input

OUTPUT ON/OFF Command

Function
This command allows the user to selectively
transfer of text to the output file.

5-26

continue/discontinue the
OUTPUT ON is the default

LINE TEXT EDITOR (EDI)
it is automatically established each time a CLOSE command
This command can be used only in the line-by-line mode.

condition;
is issued.
Format

OU[TPUT] ON
or
OU[TPUT] OFF
NOTE
If neither ON nor OFF is
is assumed.

specified,

Example
~OUTPUT

~NP

OFF _J

5 __}

~OUTPUT

ON_!

In this example, the user wishes to bypass five lines of text in the
input file without having these lines written into the output file.
The first command line causes the transfer of text to ·the output
to be disabled.

file

The second command line causes five consecutive lines of text from the
input file to be bypassed.
The third command causes the transfer of text to the output file to be
reenabled.

5.5.1.5

SELECT PRIMARY Command

Function
This command selects the primary file for input. It allows the user
to reestablish the primary input file as the file from which text is
to be read.
Format
SP

5-27

LINE TEXT EDITOR (EDI)
Example
~OPENS

SECOND.MAC_}

!SS_}
!RENEW 10 __}
!CLOSES_}
~SP

In this example, the user
1.

Opens the secondary file SECOND.MAC.

Selects SECOND.MAC as the seconaary input file.

Issues a RENEW command, which reads ten consecutive blocks
from the secondary input file into the block buffer. The
first nine blocks are automatically transferred to the output
file.

Closes the secondary input file SECOND.MAC.
NOTE
The secondary file need not be closed
before the primary file is reselected as
input.

5.5.1.6

Reselects the primary input file for input.

SELECT SECONDARY Command

Function
This command allows the user to select the secondary file as the input
file.
Format
SS
Example
To add text to the output file from a secondary input file, the user
must first open the secondary input file and select it for input. The
use of the SS command is illustrated in the example presented in
Section 5.5.1.5.

5-28

LINE TEXT EDITOR (EDI)
5.5.1.7

SIZE Command

Function
This command allows the user to specify the maximum number of lines to
be read into the block buffer on a single READ. The default value for
SIZE is 80 lines.
Format
SIZE n
Example
~SIZE 50..J

This command would condition EDI to read a default of
the block buffer during a single READ command=

5.5.1.8

lines

into

TAB ON/OFF Command

Function
Turn automatic tabbing on or off. TAB OFF is the default at the start
of an editing session. TAB ON results in a tab (equivalent to eight
spaces) being inserted automatically at the beginning of each input
line unless the line contains a label followed by a colon, or the
first column in the line contains a semicolon.
Format
TA[B] ON
or
TA[B] OFF
NO'I'E
If neither ON nor OFF is specified when
a TAB command is issued, ON is assumed.
Example
~TAB

ON__;

~I__}

; HI THERE. THIS IS A SAMPLE OF TABBING.__)
THIS LINE GETS A TAB..)
1: THIS ONE DOESN'T_)
END__}

__;

OFF_)
*N -3..}

~TAB

4.)

; HI THERE. THIS IS A SAMPLE OF TABBING.
THIS LINE GETS A TAB
1: THIS ONE DOESN'T
END

5-29

LINE TEXT EDITOR (EDI)
5.5.1.9

UPPER CASE ON/OFF Command

Function
This command allows the user to enter lower-case characters from a
terminal and have them converted to upper-case characters. If UPPER
CASE OFF is issued, all input characters are accepted as they are
entered (no conversion is performed) , except that all EDI commands are
converted to upper-case characters.
Format
UC ON
or
UC OFF
NOTE
If neither ON nor OFF is specified, then
ON is assumed.
UC ON is default at
startup.
Example
~UC

OFF~_}

!I this line is entered in lower case__;
~UC ON_.)
!I this line is converted to upper case..)
Assuming that the input terminal is capable of generating lower case
input, the above example would create the following lines in the
output file.
this line is entered in lower case
THIS LINE IS CONVERTED TO UPPER CASE

5-30

LINE TEXT EDITOR (EDI)
5.5.1.10

VERIFY ON/OFF Command

Function
This command aiiows the user to select whether locative and change
commands are to be verified. Specifying VERIFY ON allows the user to
determine whether the desired change has been correctly done.
EDI is
in the VERIFY ON mode at the start of editing.
Format
V [ERIFY]

[ON]

or
V[ERIFY]

[OFF]
NOTE

I f neither ON nor OFF is

specified,

is assumed.
Example
!.V OFF_}
~L VERIFY__}
!P~

LINE IS PRINTED AUTOMATICALLY IF VERIFY IS ON
*N -2..)

!v ON_/

~L VERIFY~

LINE IS PRINTED AUTOMATICALLY IF VERIFY IS ON
In this example, the PRINT command is issued to verify that the
desired line has been located when VERIFY is OFF, but when the LOCATE
command is reissued with VERIFY ON, EDI prints the line automatically.

5.5.2

EDI Input/Output Commands

Input/Output commands are used to transfer text to and from input
output files.
Table 5-5 contains a list of these commands.

5-31

and

LINE TEXT EDITOR (EDI)
Table 5-5
EDI Input/Output Commands

Command

Command
Format

FIL[

FI[LE] f ilespec

Transfer lines from input file to
output file and the
both
the
specified file until a form-feed or
end-of-file is encountered.

READ

REA[D]

Read next n blocks of text into
block buffer.
I f buffer contains
text, new text is appended to it.

WRITE

W[RITE]

5.5.2.1

Description

[n]

Write contents of block buffer to
output file and erase block buffer.

FILE Command

Function
This command transfers lines from the input file to both the output
file and a specified file, beginning with the current line, until a
forQ-feed character is encountered as the first character in a line or
end-of-file is reached.
At that time the specified file is closed,
and the form-feed character is not included in the specified file.
During the transfer, the original file remains intact (i.e., all lines
written to the specified file are also written to the normal output
file, including the form-feed).
When the command is complete, the
current line in the input file is one line beyond the form-feed.
If the specified file is not an existing file, a new file is created.
When the specified file does exist, the contents of the specified file
are overwritten with the new data.
Format
FI[LE] filespec
Example
!FI SEC.DAT.)
In this example, the contents of the input file from the current line
to end-of-file (assuming that no form-feed character is encountered)
is written into the output file and file SEC.DAT.

5.5.2.2

READ Command

Function
This command allows the user to read the next n blocks
the block buffer.

5-32

text

into

LINE TEXT EDITOR (EDI)
If a block is already in the buffer, the new blocks
it.

are

appended

NOTE
EDI must be running in block mode before
this command can be executed.
Format
REA [D]

[n]

If n is not specified, a value of 1 is assumed.
be positive.

The value of

must

Example
!READ 4 ~_)
In this example, four blocks of the input file are read into the block
buffer.
NOTE
The number of blocks specified should
not exceed buffer capacity.
If the
blocks being read in exceed block buffer
capacity, EDI will fill the block buffer
and then issue a diagnostic message
explaining that the buffer capacity has
been exceeded. Following the message,
EDI will issue an * prompt and wait for
another command.
At this point, the
user should issue a TOF command, locate
the line where the first READ command
was issued, and issue a READ command
with a
smaller
number
of
blocks
specified.

5.5.2.3

WRITE Command

Function
This command causes the entire contents of the block buffer to be
written into the output file. The contents of the block buffer is
then erased.
NOTE
EDI must be running in block mode before
this command can be executed.

5-33

LINE TEXT EDITOR (EDI)
Format
w[RITE]
Example
!:_W_}

?:_REA 2..)
In this example, the contents of the block buffer is written into the
output file and the block buffer is erased. Then, the next two blocks
are read into the block buffer.

5.5.3

Line Pointer Control (Locative) Commands

During editing operations, EDI maintains a pointer that identifies the
current
line (i.e., the line to which any subsequent editing
operations will refer). Commands which modify the line pointer's
location are called locative commands and they are listed in Table
5-6.

The user can issue commands which control the positioning of the line
pointer and cause the pointer to be set to a line identified only by a
text string contained in the line. The commands provided enable the
user to:
1.

Set the line pointer to either the top or bottom of the input
file or block buffer.

Move the· line pointer a specified number of lines
its current position.

Cause a line, identified only by a text string, to become the
current line.
NOTES
1.

The carriage return key can be used to
move the line pointer from the current
line to the next line. Alternately, the
ALTMODE (or ESCape) key can be used to
move the line pointer from the current
input line to the previous input line
(block mode only) •

If the VERIFY ON command is in
the line is printed when found.

5-34

effect,

away

from

LINE TEXT EDITOR (EDI)
Table 5-6
EDI Locative Commands
Command
Format

Command

Description

BEGIN

B [EGIN]

Set current line to the
line preceding top line
in file or block buffer
(identical to TOP).

BOTTOM

BO[TTOM]

Set current line to last
line in file or block
buf t"er.

END

E[ND]

Identical to BOTTOM.

FIND

[n]F[IND]

(string)

Search current block or
input file, beginning at
line following
current
line
for
the
"nth"
occurrence
of
string.
String
must
begin in
column 1.
Line pointer
is set to indicated line.

IOLDPAGE
(Block
Mode Only)

I OL[DPAGE] n

Return to TOF and read
page n into block buffer.

PAGE
(Block
Mode Only)

PAG[E] n

Enter block mode. Read
page n into block buffer.
Page n must be greater
than current page number.

PAGE FIND
(Block
Mode Only)

[n]PF[IND]

PAGE LOCATE
(Block
Mode Only)

[n]PL[OCATE]

SEARCH AND
CHANGE

SC /string-l/string-2/

Locate
string-1
and
replace all occurrences
in line with string-2.

TOP

T[OP]

Identical to BEGIN.

(string)

5-35

Search successive blocks
for the "nth" occurrence
of string.
String must
start in column 1.
Search successive blocks
for the "nth" occurrence
of string. String may be
anywhere in line.

LINE TEXT EDITOR (EDI)
5.5.3.l

BEGIN Command

Function
This command sets the current line pointer to the beginning (top) of
the file (line-by-line mode) or block buffer (block mode). The
current line is one line preceding the top line in the file or block
buffer. This allows text to be inserted at the beginning of a file or
block.
Format
B [EGIN]

Example

In this example, the current line pointer is moved to the top
block buffer (block mode is assumed).

5.5.3.2

the

BOTTOM Command

Function
This command sets the current line pointer to the end of the block or
input file.
If EDI is in block mode, only line pointer positioning
occurs. In line-by-line mode, all lines are copied from the input
file to the output file until an EOF is reached. The last line is
printed if the VERIFY ON command is in effect.
Format
BO[TTOM]
Example
~V ON.,)

~BO.,)

THIS IS THE LAST LINE
In this example, the line pointer is moved to the bottom of the
buffer, and the last line is printed.

5.5.3.3

END Command

Function
This command is identical to the BOTTOM command.
Format
E[ND]

5-36

block

LINE TEXT EDITOR (EDI)
5.5.3.4

FIND Command

Function
This command searches the block buffer or input file, beginning at the
line following the current line for "string", which must begin in
column 1 of the lines searched.
If "string"
is not specified,
the
next line is considered a match. A numeric value of "n" preceding the
command results in finding the "nth" occurrence of "string" and
positioning the line pointer to the line containing it.
FIND applies to the block buffer if EDI is in block mode
input file if EDI is in line-by-line mode.

and

When the line containing the desired "string" is found, it is
if the VERIFY ON command is in effect.

the

printed

Format
[n]F[IND]

(string)

Example
*V ON.)
~F LOOK.)

LOOK AT THE FIRST CHARACTER IN THE LINE.
In this example, EDI searches the block buffer (or file)
for
that begins with LOOK and prints the line when it is found.

5.5.3.5

line

OLDPAGE Command

Function
This command causes EDI to enter block mode, if not already in block
mode, and read page n into the block buffer.
This command is
identical to the PAGE command, except that OLDPAGE allows the user to
back up to previous page "n".
EDI actually accomplishes this by
performing a TOF operation followed by a PAGE n operation (see Section
5.5.3.6).
Format
OL[DPAGE] n
Example
*OL l_.)
[PAGE

In this example, EDI locates page 1, reads it into the
and prints the new page number.

5-37

block

buffer,

LINE TEXT EDITOR (EDI)
5.5.3.6

PAGE Command

Function
This command causes EDI to enter block mode, if not already in block
mode, and read page n into the block buffer. A page is always
delimited by form-feeds. If n is less than the current page number,
an error message is displayed. Otherwise, the necessary number of
RENEW commands is executed to read page n into the block buffer.
Format
PAG[E] n
Example
~PAG

7.)

[PAGE

In this example, EDI locates page 7 if the present page number is less
than 7, reads page 7 into the block buffer and prints the new page
number.

5.5.3.7

PAGE FIND Command

Function
This command functions identically to the FIND command, except that
successive blocks are searched until the "nth" occurrence of "string"
has been found. The contents of the block buffer and the blocks
between the current block and the block in which the "nth" occurrence
of the string is located are copied into the output file. The string
must begin in column 1 of the line searched.
Format
[n]PF[IND]

(string)
NOTE

This command can be used only
mode.

block

Example
This command is used in the same manner as the FIND command, except
that the specified string can be in a block following the current
block.

5-38

LINE TEXT EDITOR (EDI}
5.5.3.8

PAGE LOCATE Command

Function
This command causes a search of the current block, starting at the
line following the current line, and successive blocks until the "nth"
occurrence of the string has been located.
Text from the current
block buffer is written into the output file. The string can occur
any place in the lines checked. The line is printed if the VERIFY ON
command is in effect.
Format
[n]PL[OCATE]

(string}
NOTE

This command can be used only
mode.

block

Example
This command is used in the same manner as the LOCATE command, except
that the specified string can be in a block other than the current
block.

5.5.3.9

SEARCH AND CHANGE Command

Function
This command causes a search for string-1 in the block buffer (block
mode} or input file (line-by-line mode}, beginning at the line
following the current line. The string may occur anywhere in the
line.
When string-1 is located, it and all occurrences of the string
in that line are replaced by string-2. The located line becomes the
current line.
If string-! is not specified, then the match occurs on the next line,
and string-2 is inserted at the beginning of the line. The new
current line is printed if the VERIFY ON command is in effect.
If
string-1 is given but EDI cannot locate the string, EDI returns an *
prompt, and the line pointer is positioned at the line preceding the
top of the file or block buffer.
Format
SC /string-l/string-2/

~-39

LINE TEXT EDITOR (EDI)
Example
If the following incorrect line is contained in the current block:
THES ES THE LINE TO BE ESSUED.
The following command can be issued to correct the errors:
~V
~SC

ON..)
/ES/IS/_)

THIS IS THE LINE TO BE ISSUED.
The corrected line is printed
effect.

5.5.3.10

since

the

VERIFY

command

TOP Command

Function
This command sets the current line pointer to the top of the file
(line-by-line mode) or block buffer (block mode). The current line is
one line preceding the top line in the file or block buffer, allowing
text to be inserted at the beginning of a file or block.
Format
T[OP]
Example

This command moves the line pointer to the top of the block buffer
file.

5.5.4

Text Modification and Manipulation Commands

The text modification and manipulation commands enable the user to
display, change, and modify text. Table 5-7 contains a list of these
commands.

5-40

LINE TEXT EDITOR (EDI)
Table 5-7
EDI Text Modification and Manipulation Commands

I'Command
ERASE

Command
Format
Erase the current line
and next n-1 lines if in
line-by-line mode.

ERASE n

Erase the current block
buffer and the next (n-1)
blocksi if in block mode.
Insert
form-feed
into
block
buffer (used to
delimit a page}.

FORM FEED

LINE CHANGE

[n]LC /string-l/string-2/ Change all occurrences of
string-1 in current line
(and
n-1
lines)
to
string-2.

LIST ON TERMINAL

LI[ST]

Print
on
the
user
terminal
all
lines
remaining in block buffer
or in ~ne input file,
beginning
at
current
line.

LIST ON PSEUDODEVICE

Same as LI, except printing
is
performed
on
pseudo-device CL:.

MACRO

MACRO [x]

(definition)

Used to define macros.
Up to three macros can be
defined.
Numeric
arguments to be passed at
execution are identified
by a % in definition.

MACRO CALL

MC[ALL]

Used to retrieve macro
definitions
stored
in
file MCALL; n .

MACRO EXECUTE

[n]Mx [a]

[ n]
Execute macro [ x]
passing
times
while
numeric argument [a] •

MACRO (IMMEDIATE)

[n]<definition>

execute
Define and
macro n times.

OVERLAY

O[VERLAY]

Delete n lines,
enter
Input mode, and insert
new line(s) as typed, in
place
of
original
line(s).

[n]

5-41

LINE TEXT EDITOR (EDI)
Table 5-7 (Cont.)
EDI Text Modification and Manipulation Commands
Command
Format

Command

Description

PASTE

PA[STE) /str-l/str-2/

Search
all
remaining
lines in file or block
buff er for string-I and
replace with string-2.

SAVE

SA[VE)

Save current line and the
next
n-1
lines
in
specified
file.
If
f ilespec
is
not
specified,
lines
are
saved in file SAVE. TMP.

[n)

TYPE

TY[PE)

UNSAVE

UNS[AVE)

I
I

[ f ilespec)

[ n)

Print next n lines.
pointer
remains
current line.

[ filespec)

5.5.4.l

Insert all lines
from
specified file following
current
line.
If
f ilespec
is
not
spec if ied, SAVE.TMP
is
used.

Function
This command causes the current line, or the current block buffer, and
the next n-1 blocks to be erased.
In line-by-line mode, only a
specification of l is allowed. This causes the current line to be
erased.
In block mode, the current block buffer and the next n-1
blocks are erased.
Format
ERASE n
NOTE
If n is not specified, +l is assumed.
Example
5..)

This command causes the content of the current block buffer and
next 4 blocks to be erased and not written into the output file.

5-42

Line
at

ERASE Command

~ERASE

the

LINE TEXT EDITOR (EDI)
5.5.4.2

FORM FEED Command

Function
This command allows the user to insert form-feeds into the text.
Form-feed cannot be entered in input modee The form-feed is inserted
after the current line, and the new current line becomes the line
containing the form-feed. Form-feeds are used to delimit an EDI page.
Format
FF
Example
~p_J

THIS IS THE LAST LINE ON THE PAGE
~FF.J

In this example, a form feed is inserted into the text
current line.

5.5.4.3

following

the

LINE CHANGE Command

Function
This command is similar to CHANGE, except that all occurrences of
string-1 in the current line are changed to string-2. A numeric value
n" preceding the command results in the current line and the next n-1
lines being changed. If string-2 is null, all occurrences of string-I
are deleted. New lines are printed if the VERIFY ON command is in
effect.
11

If string-I is given but EDI cannot locate the string in
line, EDI prints [NO MATCH] and returns an * prompt.

the

current

Format
[n]LC /string-l/string-2/
Example
If the current line is:
THES ES THE LINE TO BE ESSUED.
Then, the following command could be issued to correct the errors:
!.V ON_,l

*LC /ES/IS~
THIS IS THE LINE TO BE ISSUED

5.5.4.4

LIST ON TERMINAL Command

Function
This command prints on the user terminal all lines in the block buffer

5·-43

LINE TEXT EDITOR (EDI)
{block mode) or all remaining lines in the input file (line-by-line
mode), beginning at the current line. At the end of the listing, the
current line pointer is repositioned to the top of the input file or
block buffer.
NOTE
To suppress printing at any point,
CTRL/O.

type

Format
LI[ST]
Example
~LI_}

This command causes all remaining lines in the block buffer or all
remaining lines in the input file to be printed on the user terminal.

5.5.4.5

LIST ON PSEUDO-DEVICE Command

Function
This command functions in the same manner as the LIST ON TERMINAL
command, excepe that the remaining lines in the block buffer (block
mode} or the remaining lines of the input file (line-by-line mode) are
listed ~n the pseudo-device CL:.
Format
LP
Example

This command causes all remaining lines in the block buffer or all
remaining lines in the input file to be printed on the pseudo-device
CL:.

5.5.4.6

MACRO Command

Function
This command is used to define macros. Space is available for three
macro definitions.
The definition portion can be any legal EDI
command or string of legal EDI commands connected by the concatenation
character.
If a numeric argument is to be passed to the macro at
execution time, a percent sign (%) must be inserted in the macro
definition
at the point where the numeric argument is to be
substituted. Then, the "a" value, which is passed via the MACRO
EXECUTE command, replaces the percent sign when the macro is executed
(see Section 5.5.4.8 for a description of the MACRO EXECUTE command).

5-44

LINE TEXT EDITOR (EDI)
Format
MACRO x definition
where:

is the macro number (1, 2 or 3).

Example
To find the nth occurrence of the string ABC in the current block and
replace that occurrence and all remaining occurrences within the block
with the string DEF, the following macro could be used:
*MACRO l %L ABC&PA /ABC/DEF_)
The following command executes the macro and searches for the 10th and
----- --~nicceed i:n9···0e:cuYYence--·0T--A:1:rc-.-----rse·e--se·c-£Ton--s-: s. 4. a.)
*M

-':.L

...L

1 ()

)

...LV~

The following macro definition and subsequent invocation could be used
to change all occurrences of the strings ABC and GHI to DEF and JKL,
respectively. The substitution is made in the current block, and the
next four blocks (five blocks in all).
*MACRO l PA /ABC/DEF/&PA /GHI/JKL/&RENEW~

~SM

5.5.4.7

l..J

(MACRO command)
(MACRO EXECUTE command)

MACRO CALL Command

Function
This command allows the user to retrieve up to three macro definitions
previously stored by the user in a file.- The macro definitions must
contain only the "definition" portion of the MACRO command and will be
stored in successive macro areas (i.e., the first macro definition
goes into macro 1 area, the second definition, goes into macro 2 area,
and the third goes into macro 3 area) .
The filename of the file used to store the macro definitions must be
MCALL;n, where n represents a version of the file. If the desired ~ui
macro definitions are not contained in the latest version of file
MCALL,
the version number of the file containing the desired
definitions can be forced to the latest version number using the PIP
COPY command with the /NV subswitch specified (see Section 2.4.2).
The filename must have a null or blank file type.
Format
MC[ALL]
NOTE
Strings of concatenated EDI commands can
be written as EDI macro definitions, and
up to three EDI macro definitions can be
stored in file MCALL;n. The MC command
is used to call the latest version of
file
MCALL
and
move
the
three

5-45

LINE TEXT EDITOR (EDI)
definitions into the macro storage area.
Then the user can execute the desired
macro without having
to
type
the
complete command.
Example
*MC_)
This command would retrieve the macro definitions stored in file
MCALL;n, where n represents the latest version of the file MCALL.

5.5.4.8

MACRO EXECUTE Command

Function
This command causes macro "x" to be executed "n" times while passing
it an optional numeric argument "a". If a macro numeric argument is
defined via the percent sign (%) in the macro definition, the numeric
argument contained in this command is passed for each execution of the
macro (See Section 5.5.4.6.). Before a macro can be executed, it must
have been defined via a MACRO command and stored in the EDI macro
storage area. If the desired macro definition is stored in a file,
the file must be called via a MACRO CALL command to move the
definition into the EDI macro storage area.
NOTE
Using this command, any one of the three
macro definitions stored in the EDI
macro storage area can be executed any
number of times.
Format
[ n] Mx

[a]

where:

is the number of times the
executed.

macro

is the macro nuraber.

is the numeric argument to be passed when the
macro is executed (ignored if % argument is
not present in macro definition).

Examp~es

Execute macro number 1, twice.
~3M2 5.)

Execute macro number 2, three times, passing the numeric argument
each time the macro is executed.

(5)

Section B.2.4 contains an example which illustrates how a file can
edited using the EDI MACRO commands.

5-46

LINE TEXT EDITOR {EDI)
5.5.4.9

MACRO {IMMEDIATE} Command

Function
This command allows the user to define and execute a macro in one
step.
The definition is enclosed within angle brackets and is
identical to that of the MACRO command. The definition is copied into
the macro 1 storage area and immediately executed n times.
{Macro
storage is discussed in the description of MACRO CALL, Section
5.5.4.7.) The macro definition may also be subsequently executed via
an Ml command. The command is actually equivalent to the two macro
commands:
MACRO 1 definition
nMl

n<definition>
Example
*<L ABC&C /ABC/DEF>..J
This command causes EDI to search the current block buffer for
string "ABC" and, when located, to change the string to "DEF".

the

Section B.2.3 contains an example which illustrates the use of the EDI
immediate MACRO command.

5.5.4.10

OVERLAY Command

Function
This command causes deletion of n lines and replacement with any
number of lines typed in by the user. If n is not specified, the
current line is deleted and replaced with any number of lines typed.
When the OVERLAY command is issued, EDI enters Input mode. The user
can enter text via ~ne user terminal. ~o leave Input mode, a carriage
return is typed as the first character in a line.
Format
O[VERLAY]

[n]
NOTE

If n is not specified, a value of +l
assumed.
'

Example

This command deletes two lines and causes EDI to enter Input mode.

5-47

LINE TEXT EDITOR (EDI)
5.5.4.11

PASTE Command

Function
This command is id7ntical to the LINE CHANGE command, except that all
lines remaining in the input file or block buffer are searched, and
all occurrences of string-I are replaced with string-2.
Modified
lines are printed if the VERIFY ON command is in effect. If string-I
is given, but a match cannot be located, the EDI returns an * prompt.
The line pointer is at the top of the buffer or top of file when the
command is complete.
Format
PA[STE] /string-1/string-2[/]
Example
If the following lines are to be corrected:
THIS ARE LINE 1
THIS ARE LINE 2
THIS ARE LINE 3
The command is as follows:
*PA /ARE/IS/_}
If the VERIFY ON
printed.

command

effect,

all

corrected

lines

are

NOTE
To discontinue printing, type CTRL/O.
5.5.4.12

SAVE Command

Function
This command causes the current line, and the next n-1 lines, to be
saved in the file specified by the file specifier. If the file
already exists, a new version is created with the same name, and the
appropriate information is saved in the new file.
If no file is specified, a save file
SAVE.TMP.

generated,

under

NOTE
The input file or buffer information
that is transferred to the SAVE file
remains intact. The new current line
pointer will be positioned to the last
line saved. The SAVE command does not
delete lines in the block buffer or
input file.

5-48

the

name

LINE TEXT EDITOR (EDI)
Format
SA[VE] [n]

[filespec]

Example
A user can save and later insert small groups of lines in several
places in an output file by using the SAVE and UNSAVE commands.
Suppose the user has a file called EDIT.MAC which contains six lines
to be inserted in a number of places in another file called HELP.MAC.
The procedure is:
1.

Start an editing session using EDIT.MAC as the input file.

Locate the lines to be inserted into HELP.MAC.

Issue SAVE 6

command.

(This transfers the six lines
SAVE. TMP.)

saved

into

the

file

Issue a KILL command to terminate the editing session.

Start a new editing session using HELP.MAC as the input file.

Locate each place where the six lines are to be inserted
issue the UNSAVE command (see Section 5.5.4.14).

Make further edits to the input file, as desired, or EXIT.

and

NOTE
The save file is not deleted by EDI and remains
the specified volume until the user deletes it.
5.5.4.13

TYPE Command

Function
This command is functionally the same as the PRINT command, except
that the current line pointer is unchanged. That is, after printing
the specified number of lines, the line pointer is positioned to the
first line printed by the TYPE command.
(Compare with the PRINT
command - Section 5.4.3.12.)
Format
TY [PE]

[n]
NOTE

If n is not specified, a value of
assumed.

Example
See the example of the PRINT command (Section

5-49

5.4~3.12).

LINE TEXT EDITOR (EDI)
5.5.4.14

UNSAVE Command

Function
This command retrieves all the lines in a specified file and
inserts
them immediately following the current line.
If no file is specified,
the file is defaulted to SAVE.TMP.
The new current line pointer
is
positioned at the last line retrieved from the file.
The file used in
this command can be any text file;
it is often the file created with
a SAVE command.
Format
UNS[AVE]

[filespec]

Example
If file SEC.DAT;! contains a group of lines which are to be inserted
following the current line, the following command performs the desired
operation.

~UNS SEC.DAT;l~
Section B.2.2 contains an
commands.

5.5.5

example

using

the

EDI

SAVE

and

UNSAVE

EDI Close Operation Commands

The close operation commands are used to terminate EDI operations and
to write the remainder of the input file into the output file.
Table
5-8 contains a list of these commands.
Table 5-8
EDI Close Operation Commands
Command
Format

Command
CLOSE

CL[OSE]

CLOSES

EXIT

KILL

Description

[ f ilespec l

Transfer remaining lines in
block buffer and input file to
output file and close file.
I f file
specifier
is used,
output file is renamed.
EDI>
prompt is issued.
Close secondary file.

DELETE

CD[L]

[filespec]

Same as CL, except input file
is deleted.
EDI> prompt is
issued.

DELETE

ED [X]

[ f ilespec]

Same as CDL, except
after
files are closed and renamed,
EDI exits.

KILL

Input file and output file are
closed.
Output
file
is I
I
.t:lH>
prompt
lS
~eleted.
issued.

I
5-50

.l .. -

LINE TEXT EDITOR (EDI)
5.5.5.1

CLOSE Command

Function
This command transfers all remaining lines in ~ne o~ock buffer and
input file
(in that order)
into the output file, and closes both
files.
If a file specifier is included, the output file is renamed to
the specified file.
EDI then returns to its initial command sequence,
prompts with EDI> and waits for another file specifier to be entered.
NOTE
If a secondary file was opened during
the editing session and not closed, it
remains open.
Format
CL[OSE]

[filespec]

Example
~CL_)
EDI>

This command closes both input and output files, and
the initial command sequence.

5.5.5.2

EDI

returns

CLOSES Command

Function
This command is used when the user has finished extracting text from a
secondary file and wishes to close it. The secondary file is closed
and cannot be used for input unless reopened.
Format
CLOSES

5.5.5.3

CLOSE AND DELETE Command

Function
This command transfers all remaining lines in the block buffer and the
input file
(in that order)
into the output file, and closes both
files.
The input file is then deleted.
If a file specifier
is
included, the output file is renamed to the specified file.
In
effect, this command acts just like CLOSE, except that the input file
is deleted. See NOTE contained in Section 5.5.5.1.
Format
CD[L)

[filespec)

5-51

LINE TEXT EDITOR (EDI)
5.5.5.4

EXIT AND DELETE Command

Function
This command functions in the
command, except that, after
exits.

same way as the CLOSE and DELETE
the files are closed and renamed, EDI

Format
ED[X]

5.5.5.5

[filespec]

KILL Command

Function
This command returns EDI to the initial command sequence without
retaining the output file. When this command is executed, the input
file is closed, and the output file is deleted.
Format
KILL
Example
:KILL_)
EDI>
In this example, the output file is not retained, and EDI returns
the initial command sequence waiting for the next file specifier.

5.6

EDI ERROR MESSAGES

The four classes of EDI error messages are:
•

Command level informational and error messages

•

File access warning messages

•

Error messages requiring EDI restart

•

Fatal error messages

The following sections describe all the messages that may be displayed
in each class. If the recovery procedure is not evident, a suggested
user action is supplied.

5.6.1

Command Level Informational and Error Messages

5-52

LINE TEXT EDITOR (EDI)
end-of-buffer in block mode:
(*EOB*]

*
Note that immediately following the message, EDI outputs
to prompt for the next command.

asterisk

The messages in this class follow.

[ALREADY PASSED THAT PAGE!]
Description
The user has attempted to access a page number that is less than
the current page.
Prior pages can be accessed only via the
OLDPAGE command.
Suggested User Action
If the PAGE command has been incorrectly entered, retype the
command with the proper page number. Otherwise, use an OLDPAGE
command to access the desired page.
[BUFFER CAPACITY EXCEEDED BY]
offending line
[LINE DELETED]
Description
A READ,

UNSAVE,

INSERT,

OVERLAY

command

has

capacity of the block buffer to be exceeded.
caused the overflow is displayed and deleted.

caused

The line that

Suggested User Action
If a new file is being created, empty the
command and continue the editing session.

buffer

with

WRITE

If an existing file is being edited, it may be possible to
continue via a RENEW or WRITE command. Otherwise, use the CLOSE
command to close the output file and save all edits. Reopen the
output file as the input file and, using the SIZE command, reduce
the number of lines read into each buffer; then, using the PAGE
LOCATE command, search to the position in the file where editing
is to continue.
Occasionally, a file that was not created by EDI causes this
message (i.e., an attempt to open the file for input produces
this message). If this occurs, the following procedure may be
used to successfully edit the file:
1.

Start the editing session by specifying a filename that
not correspond to any file in the current directory.
causes EDI to create a new file and enter Input mode.

Type carriage return to enter edit mode.

5-53

does
This

LINE TEXT EDITOR (EDI)
3.

Using the SIZE command, reduce the number of lines read
each buffer.

into

Use the KILL command to terminate the creation of the file.

When EDI prompts for a new file specifier, enter the name
the desired file.

[CONCATENATING CHAR CHANGED TO "&"]
Description
The user has changed the command concatenation character and an
OLDPAGE, TOF, or TYPE command has caused it to be changed back to
II

& II

Suggested User Action
Use the CC command to
concatenation character.

reestablish

the

desired

command

[CREATING NEW FILE]
INPUT
Description
The in~ut file specified in the command does not exist and EDI
has created a new file. EDI automatically enters Input mode and
awaits the input of text lines.
Suggested User Action
If the intent is to create a new file,
session, entering new lines as required.
mode by typing carriage return;
use
terminate the creation of the new file.
new file specifier, enter the correct file

continue the editing
Otherwise, enter Edit
the KILL command to
When EDI prompts for a
specification.

[ILL CMD]
Description
A command that is not recognized by EDI has been entered;
or a
command that is not compatible with the current mode has been
attempted (e.g., a READ command in line-by-line mode).

[ILL NUM]
Description
A non-numeric character has been specified in a numeric field, or
a negative number has been entered where only positive numbers
are allowed.

5-54

LINE TEXT EDITOR (EDI)
[ILL STRING CONST]
Description
A search string specified in a CHANGE, LC, PASTE, or SC command
contains only one command concatenation character or does not
contain a
matching
string
termination
character
(e.g.,
PASTE /ALPHABETA, whereas PASTE /ALPHA/BETA is correct) .

[ILLEGAL IN BLOCK ON MODE]
Description
An attempt has been made to execute a command that is illegal
block mode.

[ILLEGAL FILE NAME GIVEN IN CLOSE OR EXIT]
or
[FILE WAS NOT RENAMED]
Description
A syntactically incorrect file specifier has been given in a
CLOSE or EXIT command, or the attempt to rename the output file
has failed.
Suggested User Action
The output file is closed under the name of the input file
without any loss of information.
The Peripheral Interchange
Program (PIP) can be used to rename the file to the desired name.

[MACRO NOT DEFINED]
Description
An attempt has been made to execute a macro with the
but the specified macro has not been defined.

M command,

Suggested User Action
Use the MACRO command to define
execute it with the M command.

the

desired

macro

and

then

[MACRO NUMERIC ARG UNDEFINED]
Description
A macro has been executed with an M command that did not contain
a numeric argument, and the body of the referenced macro contains
the numeric argument replacement character "%".

5-55

LINE TEXT EDITOR (EDI)
Suggested User Action
Retype the command, specifying the appropriate numeric argument.

[MCALL FILE DOES NOT EXIST]
Description
An MCALL command has been executed to define a set of macros, but
the file MCALL does not exist in the current directory.
Suggested User Action
The desired set of macro definitions may exist under another UFO.
If this is the case, use PIP to copy or rename the MCALL file
into the current directory.

[NO INPUT FILE OPEN]
Description
A PAGE, READ or RENEW command has been attempted and a new file
is being created.
These commands can be executed only when an
existing file is being edited.

[NO MATCH]
Description
A CHANGE command has specified a string to be changed that is not
in the current line.
[OVERLAYING PREVIOUSLY DEFINED MACRO]
Description
A MACRO command has resulted in the redefinition of a previously
defined macro.
This message is intended to make the user aware
that the previous definition is no longer in effect.
[SAVE FILE DOES NOT EXIST]
Description
A file was specified in an UNSAVE command that cannot be
in the respective directory.

located

Suggested User Action
Examine the file specifier to ensure its correctness.
If the
file specifier is in error, correct the error, then retry the
command.

5-56

LINE TEXT EDITOR {EDI)
[SECONDARY FILE ALREADY OPEN]
Description
An attempt has been made to ope~ a secondary input file when
another secondary input file is already open. Alternatively, a
CLOSE or KILL command has been executed, or an error has been
encountered that causes EDI to restart, and the secondary file is
found to be open from the previous edit.
The former case
represents an error, whereas the latter informs the user that he
still has a secondary file open.
Suggested User Action
Close the secondary input file using the CLOSES command, and then
open the desired secondary file with the OPENS command.
[SECONDARY FILE CURRENTLY SELECTED FOR INPUT]
Description
A CLOSE or KILL command has been issued, or an error
EDI to restart, when the secondary input file
selected for input.

has caused
is open and

Suggested User Action
Issue an SP command, a CLOSES command and proceed.

[SYNTAX ERROR]
Description
A command has been entered that is syntactically incorrect.
[TOO MANY CHARS]
Description
A CHANGE, LC, PASTE, or SC command has resulted in a line that
contains too many characters. EDI limits the length of a line to
90 characters.
Suggested User Action
Retype the line to ensure that the line is valid.

[*BOB*]
Description
The beginning-of-buffer has been reached.
The current line
pointer is positioned just before the first line in the buffer.
Thus, new text lines can be entered before the first line.

5-57

LINE TEXT EDITOR (EDI)
[*EOB*]
Description
The end-of-buffer has been reached. The current line pointer now
points to the beginning of the buffer. Thus, if new lines are
inserted, they appear before the first line in the buffer.
[*EOF*]
Description
The end-of-file has been reached on the input file.
Suggested User Action
If the editing session is complete, use the CLOSE or EXIT command
to close the output file.
Otherwise, use the TOF command to
return to the first block in the file and then continue editing
the file.

5.6.2

File Access Warning Messages

Messages in this class represent attempts on the part of the user to
access directories, files, or devices that are not present in the host
system. Each message is prefixed with:
EDI
and, after the message is displayed, EDI returns to command level
prints an asterisk to request input.

and

The messages in this class follow.

EDI -- DEVICE NOT IN SYSTEM
Description
A FIL&, OPENS, SAVE, or UNSAVE cbmmand contains the specification
of a device that does not exist in the host system.
Suggested User Action
Reenter the command line, specifying only
the system.

devices

available

EDI -- FILE DOES NOT EXIST
Description
An attempt has been made in a FILE or SAVE command to create a
file in a directory that does not exist on the specified volume.

5-58

LINE TEXT EDITOR (EDI)
WARNING
The remaining error messages in this
class should not occur and represent
failures in EDI.
If
such
errors
persist,
consult
your DEC software
support representative.
EDI -- BAD DEVICE NAME
EDI -- BAD FILE NAME
EDI -- DEVICE NOT READY
EDI -- FILE ALREADY OPEN
EDI -- RENAME NAME ALREADY IN USE
EDI -- RENAME ON TWO DIFFERENT DEVICES
EDI -- WRITE ATTEMPT TO LOCKED UNIT

5.6.3

Error Messages Requiring EDI Restart

The error messages described in this section are caused by conditions
encountered by EDI that make it impossible to continue the current
editing session. EDI closes all open files (with the exception of the
secondary input file),
reinitializes, and then prompts for the next
file to be edited.
As with file access warning messages, each message in
prefixed with:

this

class

EDI -After the appropriate message has been displayed, EDI prompts with:
EDI>
The editing session may be terminated at this point by typing carriage
return, or it can be continued by entering the next file specifier.
If a secondary file was open when the error condition was encountered,
the secondary file must be closed using the EDI commands.
The messages in this class follow.

5-59

LINE TEXT EDITOR (EDI)
EDI -- BAD RECORD TYPE - FILE NO LONGER USABLE
Description
The record type defined in the header block of the input file
(primary input, secondary input, UNSAVE, or MCALL) is not
supported by File Control Services (FCS); thus, the file cannot
be used for input to EDI.
Suggested User Action
The referenced file has been created without using FCS, or the
file structure on the volume is damaged. If the latter is the
case, the validity check of the file structure verification
utility (VFY) should be run to determine the extent of the
damage. VFY is described in Chapter 8.
EDI -- FILE IS ACCESSED FOR WRITE
Description
The input file (primary input, secondary input, UNSAVE, or MCALL)
is currently being written by another task.
Suggested User Action
Wait for the file to be written
line.

and

then

reenter

the

command

EDI -- FILE IS LOCKED TO WRITE ACCESS
Description
The output file (text output, FILE, or SAVE) is currently
accessed for read by one or more tasks and is locked against all
writers.
Suggested User Action
Wait for all readers of the file
command line.

finish,

then

reenter

the

EDI -- ILLEGAL RECORD ATTRIBUTES - FILE NOT USABLE
Description
The record attributes defined in the header block of the input
file (primary input, secondary input, UNSAVE, or MCALL) are not
supported by FCS; thus, the file cannot be used for input to
EDI.
Suggested User Action
The referenced file has been created without using FCS or the
file structure on the volume is damaged. If the latter is the
case, the validity check of the file structure verification
utility (VFY) should be run to determine the extent of the
damage.

5-60

LINE TEXT EDITOR (EDI)
EDI -- PRIMARY FILE NOT PROPERLY CLOSED
Description
When the primary input file was last written, a close check was
specified, and the writing task did not properly close the file
(e.g., the task was aborted}. Thus, the file attributes were not
written, and the file may contain inconsistent data.
Suggested User Action
Exit from EDI by typing carriage return.
Fun the Peripheral
Interchange Program (PIP}
and use the /UN switch to unlock the
file. Reinitiate EDI and try to recover the data in the file.
EDI -- PRIVILEGE VIOLATION
Description
A privilege violation
following reasons:

occurs

during

file

access

for

the

The specified volume is not mounted.

The UIC under which EDI is running does not possess the
necessary privileges to access the specified directory.

The UIC under which EDI is running does not possess
necessary privileges to access the specified file.

the

Suggested User Action
If the volume is not mounted, then mount it using the MCR MOUNT
command.
Otherwise, reinitiate EDI under a UIC that has
appropriate access privileges to both the specified directory and
the file.
EDI -- RECORD IS TOO LARGE FOR USER BUFFER

The input file (primary input, secondary input, UNSAVE, or MCALL}
being accessed was not created by EDI (or SLP) and contains
records that are too large. The maximum record length supported
by EDI is 90 bytes.
EDI -- SECONDARY FILE NOT PROPERLY CLOSED - NOT USABLE
Description
When the secondary input file was last written, a close check was
specified, and the writing task did not properly close the file
(e.g., the task was aborted}. Thus, the file attributes were not
written, and the file may contain inconsistent data.
Suggested User Action
Run PIP and use the /UN switch to unlock the
EDI and try to recover the data in the file.

5-61

file.

Re initiate

LINE TEXT EDITOR (EDI)

WARNING
The remaining error messages in this
class should not occur and represent
failures in EDI.
If
such
errors
persist,
consult
your DEC software
support representative.
EDI -- BAD DIRECTORY SYNTAX
EDI -- DUPLICATE ENTRY IN DIRECTORY
EDI -- END OF FILE
EDI -- ILLEGAL RECORD ACCESS BITS - FILE NOT USABLE
EDI -- ILLEGAL RECORD NUMBER - FILE NOT USABLE

5.6.4

Fatal Error Messages

The fatal error messages represent system and/or hardware error
conditions which make it impossible for EDI to continue execution.
All files are closed and EDI terminates its execution.
The output
file may be truncated. Each error message is prefixed with:
EDI -and followed by the exit message:
[EXIT]
on the next line.
The advanced user may be able to utilize the truncated version of an
output file in the following manner to save the editing performed
prior to the fatal error condition.
1.

Use PIP to rename the truncated version of the output file to
avoid confusion.

Restart the editing session on the original input file.

Issue an OPENS command, specifying the renamed
secondary file.

Issue an SS command to select the secondary file for input.

Issue an ERASE command to erase the first block of the input
file, unless the truncated output file did not contain the
entire first block.

Issue as many READ 1 and WRITE commands as necessary to reach
the EOF on the secondary file.

Issue an SP command to select the primary file for input.

5-62

file

the

LINE TEXT EDITOR (EDI)
8.

Issue a CLOSES command to close the secondary file.

Issue a WRITE command to ensure
written into the output file.

that

10.

Issue as many READ 1 and ERASE
bypass all input file blocks
renamed file.

commands as necessary to
which are complete in the

11.

Continue the normal editing session.

the

last

block

was

The messages in this class follow.

EDI -- CALLER'S NODES EXHAUSTED
Description
System dynamic storage has been depleted, and insufficient space
is available to allocate the control blocks necessary to open,
close, read, or write a file.
Suggested User Action
This probably is a system failure, but it could also represent a
transient
overload condition.
Wait until system load has
diminished and reinitiate EDI.
EDI -- DEVICE FULL
Description
Insufficient space exists on the output
output file (text output, FILE, or SAVE).

volume

extend

Suggested User Action
Determine which volume is being written. If it is required that
the specified file be written on this volume, then space must be
made available. Use PIP to purge (/PU) or delete (/DE)
unwanted
files.
EDI -- FILE HEADER CHECKSUM ERROR
Description
An input file (primary input, secondary input, UNSAVE, or MCALL)
has a header block that does not contain a proper checksum.
Suggested User Action
The file structure on the specified volume is damaged.
Run
validity check of the file structure verification utility (VFY)
to determine the extent of the damage.
VFY is described in
Chapter 8.

5-63

LINE TEXT EDITOR (EDI)
EDI -- FILE HEADER FULL
Description
Insufficient retrieval pointer space exists in the header
to extend an output file (text output, FILE, or SAVE).

block

Suggested User Action
An attempt is being made to create an output file that is larger
than can be described in a file header block. Split the file
into two or more files and process them separately.
EDI -- FILE PROCESSOR DEVICE WRITE ERROR
Description
This error message can be received
session on a write-locked device.

initiating

editing

Suggested User Action
Unlock device if it is write-locked.
Otherwise, a hardwareproblem may exist. Consult the DEC field service representative.
EDI -- INDEX FILE FULL
Description
File header block is not available to create an output file (text
output, FILE, or SAVE).
When a volume is initialized, the
maximum number of files that may be created on the volume is
established. An attempt has been made to exceed this maximum.
Suggested User Action
Determine which volume is being referenced. If it is required
that the specified file be created on this volume, then space
must be made available. Use PIP to purge (/PU) or delete (/DE)
unwanted files.
WARNING
The following error messages signify
hardware problems.
If possible, all
important files should be removed from
the volume. If errors persist, consult
the DEC field service representative.

5-64

LINE TEXT EDITOR (EDI)
EDI -- BAD BLOCK ON DEVICE
EDI -- FILE PROCESSOR DEVICE READ ERROR
EDI -- HARDWARE ERROR ON DEVICE
EDI -- PARITY ERROR ON DEVICE
WARNING
The remaining error messages in this
class should not occur and represent
failures in EDI.
If
such
errors
persist,
consult
your DEC software
support representative.
EDI -- BAD DIRECTORY FILE
EDI -- BAD PARAMETERS ON A QIO
EDI -- INVALID FUNCTION CODE ON A QIO
EDI -- NO BLOCKS LEFT
EDI

REQUEST TERMINATED

EDI -- WRITE ATTRIBUTE DATA FORMAT ERROR
EDI -- UNEXPECTED ERROR - EDITOR WILL ABORT
TASK " ... EDI" TERMINATED

5-65

CHAPTER 6
SOURCE LANGUAGE INPUT PROGRAM (SLP)

6.1

INTRODUCTION TO SLP

The Source Language Input Program l~L~J is a batch-oriented editing
program that is used to create and maintain source language files on
disk.

6.2

PREPARING TO RUN SLP

Before attempting to use SLP, the user should become
SLP's capabilities, environment, and restrictions.

familiar

with

Capabilities

6.2.1

SLP permits the user to:
1.

Create new source files.

Create
indirect
commands.

Edit an already existing source file.
commands are provided:

6.2.2

Delete

Replace

Insert

files

which

contain

Obtain line-number listings of files.
used as an aid to editing the file.

edit

control

The following

editing

SLP

These listings can

Environment

SLP accepts input from the following media:
1.

Any RSX-llM supported terminal device (on-line).

Card reader or indirect command file.

6-1

SOURCE LANGUAGE INPUT PROGRAM (SLP)
3.

6.2.3

Any RSX-llM supported volume
file).

(on-line

indirect

command

Restrictions
1.

The user must know in advance which lines, by line number, he
wants to edit. It is advisable, therefore, for the user to
have on hand a current line-number listing of the file he
wants to edit (line boundaries are the first character and
the carriage return).

SLP cannot handle input lines greater than
80
ASCII
characters in length.
If more than 80 characters are
specified an error is declared~

Edit commands refer to line numbers that must be in ascending
order starting with 1 and continuing throughout the entire
file. Form feeds and page directives are treated as though
they are simply part of the text.

6.3

INITIATING SLP

All RSX-llM utility programs can be initiated in several ways.
methods are described in Section 1.2. The methods for SLP are:

These

>SLP command string.)
>RUN •.• SLP ~
>RUN •.• SLP/UIC=[group,member]__J
>RUN $SLP.J
>RUN $SLP/UIC=[group,member].)

6.4

SLP STARTUP

After SLP has been initiated, the user must enter an initial command
to direct SLP to perform the desired function (e.g., create a new
file, select a file for editing, or list a file). The general format
of SLP commands is as follows:
outfile [/switch] [ ,1 istfile [/switch]] = infile [/switch]
where:
/switch

is one or more of SLP's optional output control
switches.
The SLP output control switches are
described in Section 6.5.

For a complete description of file specifiers, see Section 1.3.

6-2

SOURCE LANGUAGE INPUT PROGRAM {SLP)
6.4.1

Defaults in File Specifiers

Defaults in SLP file specifiers are described in Table 6-1.

Table 6-1
Defaults in SLP File Specifiers
Default

Spec if ier

Output File and Input File

dev:

SYO:
List File
The device specified or
file specifier.
[uic]

implied

the

output

Output File and Input File
The UIC under which SLP is currently running.
List File

-· --Tne
UlC- specified or implied by the
specifier.

I filename

Must be specified

I .type

Must be specified

output

file II

I
I
I

Latest version for input files;
latest
one for output and listing files.

;ver

6.4.2

version

plus

Examples of SLP Initialization

Example 1.
SLP>KATESFILE.MAC_J
A new file, KATESFILE.MAC, is to be
input from the terminal.

created

SYO:.

SLP

expects

Example 2.
SLP>,LP:=KATESFILE.MAC • ..J
This example produces a line-number listing of KATESFILE.MAC
line printer. No other output file is produced.

the

Example 3.
SLP>KATESFILE.MAC,LP:=KATESFILE.MAC;l_J
In this example, the input file( KATESFILE.MAC;l)
is to be edited,
producing an updated output file name KATESFILE.MAC with a version

6-3

SOURCE LANGUAGE INPUT PROGRAM (SLP)
number one greater than the latest version for the file.
In addition,
a line-number listing of the output file (KATESFILE.MAC) is produced
on the line printer.

6.5

SLP OUTPUT CONTROL SWITCHES

The SLP output control switches are described in Table 6-2. A switch
specification consists of a slash (/) followed by a 2-character name
for an enabling function, or a slash (/) followed by a minus (-) and a
2-character switch name for a disabling functton.
If more than one
switch is used, each switch is preceded by a slash.

6.6

SLP OUTPUT FILES

When a file is edited, SLP produces an output file on disk under the
name specified by the user. If the /AU switch is specified (default
condition), the output file contains information about the changes
that have been made, so the user can more readily determine how the
new file differs from the old one.
Unless specifically suppressed, an audit trail is always created
the output file, indicating changes effected by the edits.

Each line that has been inserted during the last editing
flagged by appending the characters ;**NEW** to the line.

session

The line following the inserted line(s) may be flagged by the
characters ;**-N, where N is a decimal value equal to the number of
lines that were deleted from the old file. For example:
;THIS IS A NEW LINE ADDED TO THE FILE
;THIS IS THE NEXT LINE

;**NEW**
;**-1

indicates that the new line has simply replaced one of the old
That is, the edit command looked like:

lines.

-m,m..)
;THIS IS A NEW LINE ADDED TO THE FILE..)
where m is the number of the line that was replaced.
be entries of the following kind:

There

may

also

have

been

;**NEW**
;**-16

;THIS LINE IS A REPLACEMENT
;NEXT OLD LINE

indicating that a new line has been inserted, but 16 lines
deleted immediately-preceding the next old line.

Lines may also be flagged with just the ;**-N characters, with no
immediately-preceding new lines, to indicate simply that lines have
been deleted, without being replaced.
If the /AU switch is specified when a file is being edited, the
current flags are stripped prior to output of the updated file. Thus,
the flags are reliable indicators of the editing that was done on the
most recent update of the file.

6-4

SOURCE LANGUAGE INPUT PROGRAM (SLP)
Table 6-2
SLP Output Control Switches

I Switch
I /AU or /-AU

Description
The /AU switch causes the editing audit trail to be
included, and the /-AU switch suppresses the editing
audit trail. That is, new and deleted lines are not
flagged when /-AU is in effect. Either switch can
be specified in the command string, in either an
input or an output file specifier. For example:
DKl:AX.MAC/-AU,LP:=AX.MAC__}
or
DKl:AX.MAC,LP:=AX.MAC/-AU_.)
Both specifications are legal and procuce an
file with no audit trail.

output

/AU is the default condition.
/BF or /-BF

When an audit trail is being produced, it may be
desirable to specify the blank fill (/BF) switch,
especially when the file being edited is a FORTRAN
source program.
The /BF switch causes the audit
trail text to be right-justified by inserting blanks
at the end of the text line, rather than tabs.
To disable the blank fill function, specify /-BF.
Either switch may be specified on input or output
files.
Neither has any effect if auditing is
suppressed.
/BF is the default condition.

/DB or /-DB

Listing files are normally single-spaced. To create
a double-spaced listing file, the /DB switch must be
specified, as in the following example:
DKO:XYZ.MAC,LP:/DB=DKO:XYZ.MAC;3_.)
/-DB is the default condition.

/SP or /-SP

Listing files may be spooled to a file-structured
volume by specifying a listing file as shown in the
following example:
DK:ABC.MAC,DKl:/SP=ABC.MAC_.}
This causes the list file to be written to the
volume mounted on DKl: prior to being output on a
line printer. The /SP switch has no effect if the
listing device is not file-structured. That is, if
the line printer is specified, no spooling occurs.
Output directly to a file-structured device without
printing the file can be accomplished by specifying
/-SP. The print spooler is described in Appendix C.
/SP is the default condition.

6-5

SOURCE LANGUAGE INPUT PROGRAM (SLP)
6.7

SLP EDIT COMMANDS

Following the initial command line, the user enters text lines, or
deletes or corrects lines in the original source file. Text that is
to be inserted at the beginning of the file is entered immediately
following the initial command line. To correct or replace a line, or
lines, or to insert text in the middle or at the end of the file, the
user must first specify an edit command, followed by a decimal value
referring to a line in the input file.
For example:
-9

The minus sign and line number may appear as the only element on the
line, or they may be followed by a comma and a second line number, as
shown below:
-9,12
-9,9

SLP interprets the user's purpose by exam1n1ng the edit command. When
a single line number is specified (e.g., -9 alone), SLP interprets the
user's purpose to be the insertion of new text lines into the source
file.
The line number indicates that the new text is to be inserted
following the specified line (in the first example, new text would be
placed in the file following line 9).
When the user provides an edit command in the second format (-9,12),
SLP deletes all text lines from line 9 through line 12, inclusively.
The user can follow the edit command with lines of text, which will be
inserted into the file in the location previously occupied by the
deleted lines {i.e., the first new text line is the new line 9).
The edit command (-9,9) indicates that SLP is to delete line 9.
text line (or lines) follows, it replaces the deleted line.

NOTE
Line numbers must always be specified in
ascending
sequence.
Thus, -9,8 is
illegal, and an error message is printed
(refer to Section 6.10).
It is also
illegal to refer to a line number lower
than a line number that was referenced
in a prior edit command.

6.7.1

SLP Edit Control Characters

SLP recognizes four edit control characters in character position 1:
the "minus" sign (-), the "less than" sign (<), the slash (/), and the
"at" sign (@). Table 6-3 describes the function of these characters.

6-6

SOURCE LANGUAGE INPUT PROGRAM (SLP)
Table 6-3
SLP Edit Control Characters

Function
-

Indicates that
performed with
specified.

(minus)

an editing function is to be
reference to the line number(s)

-n

Insert text following line n.

-n,n

Delete line n.

-n,m

Delete lines n through m, inc1usively.

I (slash)

The slash is placed in the first position of a
line cu indicate that the editing of a file is
complete. SLP responds by printing SLP> to inform
the user that it has terminated editing on the
previously specified file and is now ready to
begin editing another. The user responds either
by entering a new file specification, or by
terminating the editing session altogether by
typing CTRL/Z.

(at)

I ;?:~@~ 0ch7:!~~:~ei~h~~tc~~ ;~e~~i~=~~lo...i~~~;o~r~.!.. ~.~.

I ind i r ec t f i l e •
..l..L.11C

.L.J..lUL'""'U'-

\,...L.&U.\...

t..J.LJ.L.

.a....,,;i

"-'-'

"'""''-'-"·

...... ~

---

That i s , input i s to be found in a
file rather than being entered from the terminal.
user must indicate the device and file by
I The
specifying their names immediately after the @
sign. For example:

I
I

@DK:DKSFIL.COR..)
instructs SLP to read input from
the
file
DKSFIL.COR on physical device unit DKO:. Indirect
described in Section 6.8.
1 files are more fully
Unless otherwise specified, the file type defaults
I to CMD.
I

< (less
than)

The < character
is
used when entering a line
that begins with one of the special edit control
characters.
It causes the line to be shifted one
character position to the left, resulting in the
deletion of the < character and the entry of the
desired control character as the first character
on the line.
This is especially useful when
creating correction files. For example:
<@DIRBLK. COR_}

6-7

SOURCE LANGUAGE INPUT PROGRAM (SLP)
Table 6-3 (Cont.)
SLP Edit Control Characters
Character

Fune tion
causes the line
@DIRBLK.COR
to be entered into the file.
Subsequently,
this file is referenced by SLP, the line

when

@DIRB LK. COR _}
will be interpreted as a reference to an
file named DIRBLK. COR.

indirect

Similarly, specifying
<-23,29

results in the edit command -23,29 being written
into the output file. Thus, when the file is read
by SLP, lines 23 through 29 of the specified input
file will be deleted.

6.8

INDIRECT FILES

Indirect files contain both editing commands and correction lines to
be inserted into the file being edited. These files are input from a
device other than the terminal. An example of indirect file usage in
SLP follows. See Section 1.4 for a discussion of indirect files.

6.8.1

Creating an Indirect File

The following example shows how
inserted into an indirect file.

corrections

and

SLP

commands

are

Initiate SLP by specifying an initial command line
contains
an output file specifier and a listing
specifier. The following is a typical command line:

that
file

Example
1.

SLP>FROG.COR,LP:_.}
In this example, SLP will generate the file FROG.COR,
will produce a listing of this file as it is generated.
2.

and

Begin entering correction or insertion lines into the file.
Supply the appropriate edit commands and insert as text. The
correct line numbers for text being edited must be obtained
from a listing of the file that is to be edited; new text,
however, can be entered without line numbers.
In order to
generate edit command lines, it is necessary to use the shift
command character (<) in the first position of the input

6-8

SOURCE LANGUAGE INPUT PROGRAM (SLP)
line.

For example, to create the line
-29,36

as a text line in FROG.COR, you must

~n~C'ifv
-r----.1.

<-29,36..J
Thus, a typical correction file might be entered as:

<-15_)
;THIS ROUTINE CALLS THE ERROR PROCESSOR_)
$HEDR:
SAVRG
;SAVE NONVOLATILE REGISTERS_)
BNE 10$
;IF NE YES__}
RETURN..)
<-40 I 56 _J

Using Indirect Files

6.8.2

The following example shows how an indirect file can be used.
Example:
1.

Assuming that the corrections contained in AMND.COR are to be
applied to a file named WPT.MAC, the file specifier to SLP
is:
SLP>WPT.MAC,LP:=WPT.MAC~__)

which is followed by the indirect-file edit control statement
referring to the correction file:
@AMND. COR..)
NOTE
initial
command
line,
If
the
WPT.MAC,LP:=WPT.MAC, was included in the
indirect file, then editing would have
been initiated as follows:
SPL>@AMND.COR_}
2.

6.9

SLP reads correction input from the latest version of file
AMND.COR and returns to the terminal for further input to
finish updating WPT.MAC. If the user includes a termination
edit control line in AMND.COR (</), SLP responds by printing
SLP> at the terminal after terminating editing operations on
WPT.MAC. All files are closed and a listing is sent to LP:.

SLP EDITING EXAMPLES

The following examples indicate the various editing functions that SLP
can perform and the command formats used.

6-9

SOURCE LANGUAGE INPUT PROGRAM (SLP)
Example 1:
SLP>ALBLK.MAC,LP:=ALBLK.MAC;l_.}
-23,23_..,,1
; Rl=SIZE OF BLOCK TO ALLOCATE IN BYTES._.}
-33 _.)
;GET ADDRESS OF FREE POOL HEADER_.}
#$FRHD,R2
MOV
-36,36..J
-39,39~_)

ASR

;CONVERT TO WORDS.J

I _J
In this example, the following editing functions are performed:
Line 23 is replaced by a corrected version (i.e.,;
TO ALLOCATE IN BYTES.).

Rl=SIZE

BLOCK

A new line is inserted after line 33.
Line 36 is deleted (and not replaced).
Line 39 is replaced by a corrected version (i.e.,
ASR Rl

;CONVERT TO WORDS).

The output file is named ALBLK.MAC, and
produced on the line printer.

line-numbered

listing

Example 2:
SLP>BLKSG.MAC,LP:=BLKSG.MAC;l..)
-55,55_.}
BCS
60$
;IF CS YES...J
-107,107_./
CALL
$ERMSG
;OUTPUT ERROR MESSAGE_.)
/_.)

In Example 2, the following editing functions are performed:
Line 55 is replaced by a corrected line;
Line 107 is replaced by a corrected line.
The output file is named BLKSG.MAC, and a
produced.

6-10

line

numbered

listing

SOURCE LANGUAGE INPUT PROGRAM (SLP)
Example 3:
SLP>CATB.ABC;l,DKl:CATB.DAT=CATB.ZYX.)
-15,16_/
CNTRL:
.BYTE
9: 0.~)
-33,35_,/
$CDTD:: MOVB
#'9,CNTRL ;SET DECIMAL LIMIT_)
-38' 38_}
COTB::
MOVB
#'7,CNTRL ;SET OCTAL LIMIT__)
-43, 45_)
#I ,RS
; BLANK?_)
CMPB
;IF EQUAL YES..}
BEQ
1$
;HT?_)
CMPB
#HT,RS
BEQ
1$
;IF EQUAL YES__}
-4 7 I 50 _)
3$:
MOV
R5,R2
;SET TERMINAL CHARACTER_}
/.)
1

Lines 15 and 16 are deleted and replaced by a corrected line;
Lines 33 through 35 are
starting with $CDTD;

deleted

and

replaced

the

single

line

the

single

line

Line 38 is replaced;
Lines 43 through 45 are replaced by four text lines;
Lines 47 through 50 are
beginning with 3 $: .

deleted

and

replaced

The output file is created with the name CATB.ABC;
the list file
(CATB.DAT)
is written to the volume mounted on DKl: prior to being
spooled to the line printer. The input file, CATB.ZYX, remains in its
original form.
Example 4:
SLP>GETBK.C46,LP:_.)
--

• TITLE GETBK_)

@CMCOD..)
;GET ALLOCATED BLOCKS_}
;_)

;:J

In Example 4, the user is creating a new file named GETBK.C46.
The
first text line defines the program title. The next line is an edit
control line, which refers SLP to an indirect file named CMCOD.CMD
with the default file type CMD. When indirect input is complete, SLP
returns to the terminal for further input at the line following
@CMCOD.

6-11

SOURCE LANGUAGE INPUT PROGRAM (SLP)
SLP ERROR MESSAGES

6.10

SLP error messages are issued in two different formats:

•

SLP followed by two dashes and the error message.
If
applicable, the command line in error is printed on the next
line.

•

SLP followed by two
offending filename.

dashes,

the

error

message

and

the

actions

are

Examples
SLP -- SYNTAX ERROR
RICKSFILE.MAC,LP:=SHIRLEY.MAC;2
or
SLP -- OPEN FAILURE LINE LISTING FILE filename
SLP error messages, descriptions, and suggested user
follows.
SLP -- COMMAND SYNTAX ERROR
command line
Description
The command line format does not conform to syntax rules.
This
is a fatal error; the currently opened files are closed and SLP
is reinitialized.
Suggested User Action
Reenter the command line.
SLP -- ILLEGAL DEVICE NAME
command line
Description
The device specified is not a legal device.
This is a
error; it causes the editing session to be reinitialized.

fatal

Suggested User Action
Reenter the command line.
SLP -- ILLEGAL DIRECTORY
command line segment
Description
The directory is not legally specified. This is a
it causes the editing session to be reinitialized.
Suggested User Action
Reenter the command line.

6-12

fatal

error;

SOURCE LANGUAGE INPUT PROGRAM (SLP)
SLP -- ILLEGAL ERROR/SEVERITY CODE pl p2 p3
Description
This error message indicates an error in the SLP program.
Suggested User Action
Reenter the command line. If the error
DEC field support representative.

persists,

contact

your

SLP -- ILLEGAL FILE NAME
command line segment
Description
A file specification io greater than 30 characters in length or
contains a wild card (i.e., an asterisk in place of a file
specification element). This is a fatal error;
it causes the
editing session to be reinitialized.

Suggested User Action
Reenter the command line.
SLP -- ILLEGAL GET COMMAND LINE ERROR
Description
The system, for some reason, is unable to read a command line.
This indicates an internal system failure or an error in the SLP
program.
Suggested User Action
Reenter the command line. If the error
DEC field support representative.

persists,

contact

your

SLP -- ILLEGAL SWITCH
command line segment
Description
The switch is not a valid SLP switch or a legal switch is used in
an invalid manner. This is a fatal error; it causes the editing
session to be reinitialized.
Suggested User Action
Reenter the command line with the correct switch specified.

6-13

SOURCE LANGUAGE INPUT PROGRAM {SLP)
SLP -- INDIRECT COMMAND SYNTAX ERROR
command line
Description
The command line format specified for the indirect file does
conform
to
syntax
rules.
This is a fatal error;
currently-opened files are closed and SLP is reinitialized.

not
the

Suggested User Action
Reenter the command line.
SLP -- INDIRECT FILE DEPTH EXCEEDED
command line
Description
More than one level of indirection has been specified in a
command file. This is a fatal error; the currently-opened files
are closed, and SLP is reinitialized.
Suggested user Action
Correct the command file and reenter the command line.
SLP -- I/O ERROR COMMAND INPUT FILE
or
SLP -- I/0 ERROR COMMAND OUTPUT FILE
or
SLP -- I/0 ERROR CORRECTION INPUT FILE filename
or
SLP -- I/0 ERROR LINE LISTING FILE filename
or
SLP -- I/0 ERROR SOURCE OUTPUT FILE filename
Description
One of the following conditions may exist:
1.

A problem exists on the physical device {e.g., device
down) .

Length of command line is greater than 80 characters.

File is corrupted or the format is incorrect.

Suggested User Action
1.

Determine which of the above condition exists.

Rectify the condition.

Reenter the command line.

6-14

cycled

SOURCE LANGUAGE INPUT PROGRAM (SLP)
SLP -- INDIRECT FILE OPEN FAILURE
command line
or

SLP -- OPEN FAILURE CORRECTION INPUT FILE filename
or
SLP -- OPEN FAILURE LINE LISTING FILE filename
or
SLP -- OPEN FAILURE SOURCE OUPUT FILE filename
Description
One of the following conditions may exist:
1.

The file is protected against an access.

A problem exists with the physical device (e.g.,
on-1 ine) .

The volume is not mounted.

The specified file directory does not exist.

The named file does not exist in the specified directory.

The available Executive dynamic memory
the operation.

These are fatal errors;
reinitialized.

they causes the editing

not

insufficient

for

session

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

6-15

device

SOURCE LANGUAGE INPUT PROGRAM (SLP)
SLP -- PREMATURE EOF CORRECTION INPUT FILE filename
Description
An out-of-range line number has been specified in a correction
file or from the terminal, e.g., -1000 has been specified for an
800 line file.
Suggested user Action
1.
2.

Terminate the current editing session.
Restart the editing session, entering
number.

the

correct

line

SLP -- PREMATURE EOF COMMAND INPUT FILE
Description
This is caused by typing CTRL/Z at the terminal, which sends an
end-of-file to SLP before the/ is read. SLP types out SLP>,
indicating that a new file specification is expected.
Suggested User Action
Restart the editing session at the point
inadvertently typed.

6-16

where

the

CTRL/Z

was

CHAPTER 7
LIBRARIAN UTILITY PROGRAM (LBR)

7.1

INTRODUCTION TO LBR

The Librarian Utility Program (LBR) allows the user to create, update,
modify, list, and maintain object and macro library files. A library
file is a direct access file containing one or more modules of the
same module type. Library files are organized for rapic access by the
Task Builder and MACR0-11 Assembler.
The Librarian and library files, working in conjunction with the
MACR0-11 Assembler and the Task Builder, provide fast entry point
search time, easy update with minimal copying of entire files, and the
ability to handle multiple module types.
Library files contain two directory tables;
an entry point table
(EPT)
that contains entry point names, and a module name table (MNT)
that contains module names.
Both the EPT and MNT are alphabetically ordered. Object module names
are derived from .TITLE directives, while entry point names are
derived from defined global symbols. Once an entry point is located,
its associated module can be accessed directly.
Macro module names are derived from .MACRO
point names are not applicable.

7.1.1

directives;

macro

entry

Format of Library Files

A library file consists of a header, an entry point table, a module
name table, the library modules, and (usually) free space. The entry
point table has zero length for macro libraries. See Figure 7-1.

7-1

LIBRARIAN UTILITY PROGRAM (LBR)
Library
Header

FixedLength
Records

Entry Point
Table

Module Name
Table

-Block
boundaries

-~·

VariableLength
Records

Module 1 Header
Module 1
:

Module n Header

Module n
Available Space

Figure 7-1
General Library File Format

7.1.2

Library Header

The header section is a full block in which the first 23 words are
used to describe the current status of the library. Its contents are
updated as the library is modified, so the Librarian can access the
information it needs to perform its functions (Insert, Compress,
etc.) • See Figure 7-2.

7.1.3

Entry Point Table

The entry point table consists of 4-word elements containing an entry
point name (words 0-1), and a pointer to the module header where the
entry point is defined (words 2-3). See Figure 7-3.
This table is
searched when a library module is referenced by one of its entry
points. The table is sequenced in order of ascending entry point
names. The entry point table is not used for macro library files.

7-2

LIBRARIAN UTILITY PROGRAM (LBR)
OFFSET
WORD

NON ZERO ID

LIBRARY TYPE

LBR (LIBRARIAN) VERSION

(.!DENT FORMAT)
YEAR

6
10

DATE AND

MONTH

TIME LAST

DAY

INSERT

HOUR

MINUTE

SECOND

RESERVED

SIZE EPT ENTR's

EPT STARTING RELATIVE BLOCK

NO. EPT ENTRIES ALLOCATED

RESERVED

SIZE MNT ENTR'S

MNT STARTING REL BLOCK

34
36

NO. EPT ENTRIES AVAILABLE

NO. MNT ENTRIES

ALLOCATED

NO. MNT ENTRIES AVAILABLE

LOGICALLY DELETED

AVAILABLE (BYTES)

CONTIGUOUS SPACE

AVAILABLE (BYTES)

NEXT INSERT RELATIVE BLOCK

START BYTE WITHIN BLOCK

Figure 7-2
Contents of Library Header

7-3

LIBRARIAN UTILITY PROGRAM (LBR)
WORD

GLOBAL SYMBOL

NAME (RAD50)

ADDRESS OF
MODULE
HEADER

RELATIVE BLK.
BYTE

BLOCK

Figure 7-3
Format Of Entry Point Table Element

7.1.4

Module Name Table

The module name table is searched when the library module is
referenced by its module name, rather than by one of its entry points.
It is comprised of 4-word elements; a module name (words 0-1) and a
pointer to the module header (words 2-3). See Figure 7-4. The module
name table is sequenced in order of ascending module names.

WORD

MODULE NAME

(RAD50)

2
3

ADDRESS OF
MODULE
HEADER

RELATIVE BLK.
BYTE

BLOCK

Figure 7-4
Format of Module Name Table Element

7.1.5

Module Header

Each module starts with an 8-word header, identifying the type and
status of the module, its length (number of words), etc. See Figure
7-5.
For object modules, the low-order bit of the attributes byte is set if
the module has the selective search attribute. Also, for object
modules, the two words of type-dependent information contain the
module identification defined by the .!DENT directive at assembly
time. For macro modules, these two fields are undefined.

7-4

LIBRARIAN UTILITY PROGRAM (LBR)
OFFSET FROM
START OF
MODULE HEADER
0

ATTRIBUTES

STATUS

SIZE OF

MODULE (BYTES)

6
10

O=NORMAL MODULE
l=DELETED MODULE

YEAR

DATE
MODULE
INSERTED

MONTH
DAY

12
14

TYPE DEPENDENT

INFORMATION

Figure 7-5
Module Header Format

7.2

INITIATING LBR

All RSX-llM utilities can be initiated in several ways.
are described in Section 1.2. The methods for LBR are:

These methods

~LBR__J

>LBR command string__)
>RUN ... LBR__}
>RUN •.. LBR/UIC=[group,member]~~
>RUN $LBR_}
>RUN $LBR/UIC=[group,member]__J

7.3

LBR COMMAND STRING

LBR accepts command strings in the following general format:
outfile[,listfile]=infile-l[,infile-2, ... ,infile-n]
LBR allows only one level of indirect command file.
For a complete
description of file specifiers, see Section 1.3; for a description of
indirect files, see Section 1.4.

7.4

DEFAULTS IN LBR FILE SPECIFIERS

Defaults in LBR file specifiers are described in Table 7-1.

7-5

LIBRARIAN UTILITY PROGRAM (LBR)
Table 7-1
Defaults in LBR File Soecifiers
Specifier
dev:

Default
Output File
SYO:
Listing File
The device which was specified for the output
file;
otherwise, the default for the output
file.
Input File
For the first input file specifier, SYO:.
For the second through n input file specifiers,
the device specified in the previous input file
specifier;
otherwise, the default for the
previous input file specifier.

[uic]

Output File
The UIC under which LBR is currently running.
Listing File
The UIC which was
file;
otherwise,
file spec if i er .

specified for the output
the default for the output

Input File
For the first input file specifier,
under which LBR is currently running.

the

UIC

For the second through n input file specifiers,
the UIC specified in the previous input file
specifier;
otherwise, the default for the
previous input file specifier.
filename

No default.

Must be specified.

.type

Output File
Depends on the default in effect (see Section
7.5.4), except when the /CR or /CO switch is
specified {see Sections
7.5.1
or
7.5.2,
respectively) .
Listing File
.LST
Input File
Refer

the

descriptions

/CO

(Section

7.5.1), /IN
(Section 7.5.6), and /RP (Section
7.5.8) switches.

;ver

Latest version of the file, or latest version plus
one for the output file when the /CO or /CR switches
are spec if ied.

/switch

Output File
/IN (Insert)

List File

~~~~~~__.~~~~/~S~P~/~L~I~-(s_p_o_o~l~a-n-d~l-i_s_t~m-o_d_u_l_e~n-a_m_e_s_) _J
_

Input File
None.

7-6

LIBRARIAN UTILITY PROGRAM ( LBR)
7.5

LBR FILE OPTION SWITCHES

LBR file options are in the form of switches appended to
specifiers. These option switches are summarized in Table 7-2.

file

Table 7-2
LBR File Option Switches
Option

Switch

Function

Compress

/CO

Compress a library file.

Create

/CR

Create a library file.

I .ur:..

/T"'\n

Delete a library module and all of its
entry points.

Default

/DF

Specify the default library file type.

Delete Global

/DG

Insert

/IN

Insert a module.

List

/LI

List module names.

/LE

List module names and module entry
points.

/FU

List module names and full module
description.

/RP

Replace a module.

/-RP

Don't replace a module.

/SP

Spool the listing for printing.

/-SP

Don't spool the listing.

Selective Search

/SS

Set selective search attribute in
module header.

Squeeze

/SZ

Reduce the size of macro source.

n - 1 _..__
Lii:: J. I:: 1...1:::

Replace

Spool

7.5.1

I Delete a library module entry point.

Compress Switch (/CO)

FUNCTION
The Compress Switch provides the user with a facility for rearranging
a file by physically deleting all logically deleted records, putting
all free space at the end of the file, and making the free space
available for new library module inserts. Additionally, the library
table specification may be altered for the resulting library.
LBR
accomplishes this by creating a new file that is a compressed copy of
the old library file.

7-7

LIBRARIAN UTILITY PROGRAM (LBR)
NOTE
The old library file is not
after the new file is created.

deleted

The /CO switch can be appended only to the output file specifier.
FORMAT
outfile/CO:size:ept:mnt

infile

where:
outf ile

is the file specifier for the file that is to
become the compressed version of the input file.
NOTE
Default type is .OLB if input file is an
object library or .MLB if input file is
a macro library.

/CO

is the Compress switch.

:size

is the size of the new library file in 256-word
blocks.
If omitted, the size of the old library
file is the default size.

:ept

is the number of entry point table (EPT} entries
to allocate.
If the value specified is not a
multiple of 64(10}, the next highest multiple of
64(10}
is used. If omitted, the number of EPT's
in the old library file is the default value.
This parameter is always forced to zero for macro
libraries.
NOTE
Maximum number of entries is 4096(10).

:mnt

is the number of module name table (MNT} entries
to allocate.
If the value specified is not a
multiple of 64(10), the next highest multiple of
64(10)
is used. If omitted, the number of MNT's
in the old library file is the default value.
NOTE
Maximum number of entries is 4096(10}.

inf ile

is the file specifier of the library
compressed.

7-8

file

(LBR)

NOTE
Default file type
is
.OLB for object
libraries and .MLB for macro libraries.
The actual default type is determined by
the current default library type (see
Section 7. 5. 4).
EXAMPLE
LBR>RICKLIB/CO:l00.:128.:64.=SHEILA.OLB__}
In this example, file SHEILA.OLB is compressed, and
RICKLIB.OLB, is created with the following attributes:

new

file,

size= 100(10) blocks
ept

128(10) entry points

mnt

64(10) module names

NOTES
The new file,
RICKLIB.OLB,
received a
version
number
that is one version
greater than the latest version for
the
file.
Both files, RICKLIB.OLB and SHEILA.OLE,
reside in the default directory file on
SYO:.

7.5.2

Create Switch (/CR)

FUNCTION
The Create switch provides the user with a facility for allocating a
contiguous library file on a direct access device (e.g., disk).
It
initializes the Library file header, the entry point table, and the
module name tablee
The /CR switch can be appended only to the output file specifier.
FORMAT
outfile/CR:size:ept:mnt:type
where:
outf ile

is the file specifier for the library file being
created.
The default file
type
is .OLB if an
object library is being created, or
.MLB if a
macro library is being created.

/CR

is the create switch.

:size

is the size of the library file
in 256-word
blocks.
The default size is 100(10) blocks.

:ept

(EPT)
entries
is the number of entry point table
to allocate.
The default value is 512 (10) for

7-9

LIBRARIAN UTILITY PROGRAM (LBR)
object libraries. This parameter is always forced
to zero for macro libraries.
NOTE
Maximum number of entries is 4096(10).
is the number of module name table (MNT) entries
to allocate. The default value is 256(10).

:mnt

NOTE
Maximum number of
:type

entri~s

is 4096(10).

is the type of library to be created.
Acceptable
types are OBJ for object libraries and MAC for
macro libraries. The default is the last value
specified or implied with the /DF switch (see
Section 7.5.4), or OBJ if /DF has not been
specified.
NOTE
The EPT and MNT are automatically filled
out to the next disk block boundary, if
the values specified are not multiples
of 64(10).

EXAMPLE
LBR>RICKLIB/CR::l28.:64.:0BJ=SHEILA,LAURA,JENNY_)
In this example, a combination of functions are performed. First, the
library file RICKLIB.OLB is created in the default directory on SYO:;
RICKLIB has the following attributes:
size= 100(10) blocks (default size),
ept

128(10) entry points,

mnt

64(10) module names.

type = .OBJ
Second, object modules from the input files SHEILA.OBJ, LAURA.OBJ, and
JENNY.OBJ, which reside in the default directory on SYO:, are inserted
into the newly created library file. Insert is the default switch for
input files (see Section 7.5.6).

7-10

LIBRARIAN UTILITY PROGRAM (LBR}
7.5.3

Delete Switch (/DE)

FUNCTION
T~e

Delete switch provides the user with a facility for deleting
library modules and their associated entry points (global symbols)
from a library file. Up to 15 library modules and their associated
entry points can be deleted with one delete command.

When LBR begins processing the /DE switch,
message on the initiating terminal:

prints

the

following

MODULES DELETED:
As modules are logically deleted from the library file, the module
name is printed on the initiating terminal. See the example at the
end of this section.
If a specified library module is not contained in the library file, a
message is printed on the initiating terminal, and the processing of
the current command is terminated. This message is as follows:
LBR -- *FATAL* - NO MODULE NAMED "name"
The /DE switch can be appended only to the library file specifier.
NOTE
When LBR deletes a module from a library
file,
the module is not physically
removed from the file, but is marked for
deletion. This means, that although the
module is no longer accessible, the file
space that the module once occupied is
not available for use
(unless
the
deleted module is the last module which
was inserted). To physically remove the
module from the file and make the freed
space available for use, the user must
compress
the
library
(see Section
7.5.1).

FORMAT
outfile/DE:module-l[:module-2: •.. :module-n]
where:
outfile

is the file specifier for the library file.

/DE

is the delete switch.

:module

is the name of the module to be deleted.

7-11

LIBRARIAN UTILITY PROGRAM (LBR)
EXAMPLE
LBR>RICKLIB/DE:SHEILA:LAURA:JENNY_/
MODULES DELETED:
SHEILA
LAURA
JENNY
In this example, the modules SHEILA, LAURA, and JENNY and their
associated entry points are deleted from the latest version of library
file SYO:RICKLIB.OLB.

7.5.4

Default Switch (/DF)

FUNCTION
The Default switch provides the user with a facility for specifying
the default library file type. Acceptable values are OBJ for object
libraries and MAC for macro libraries. A default value of OBJ is used
by LBR to process the /OF switch.
Specifying a default value:
1.

Sets the default type argument for the Create switch (/CR).

Provides a file type default value of .MLB for macro
libraries and .OLB for object libraries when opening an
output (library) file, except in the cases of /CO and /CR.
When /CO is specified, the default applies to the library
input file. When /CR is specified, the default type is .OLB
if an object library is being created, or .MLB if a macro
library is being created. The /OF switch only affects the
name of the file to be opened; thereafter, the library
header record information is used to determine the type of
library file being processed.

The /DF switch can be issued alone
specifier.

appended

library

file

FORMAT
outfile/DF:type •.•
or
/DF:type
where:
outf ile

is the file specifier for the library file.

/OF

is the Default switch.

type

is OBJ for object library files and MAC for
library files.

7-12

macro

LIBRARIAN UTILITY PROGRAM (LBR)
NOTE
If a type other than OBJ or MAC is
specified, the current default library
type will be set to object libraries,
and
the
following message will be
displayed:
LBR -- INVALID LIBRARY TYPE SPECIFIED
EXAMPLES
1.

LBR>/DF:MAC_}
LBR>RICKLIB=inf ile_)
File RICKLIB.MLB is opened for insertion.

LBR>/DF:MAC_}
LBR>RICKLIB/DF:OBJ=infile_J
File RICKLIB.OLB is opened for insertion.

LBR> /OF: MAC_)
LBR>RICKLIB/CR_}
Macro library RICKLIB.MLB is created.

LBR>/DF:MAC_J
LBR>RICKLIB/CR::::OBJ_J
Object library RICKLIB.OLB is ----.L-..::1
l.t::U •
~r.t::a

LBR>/DF__)
LBR>TEMP/CO=RICKLIB_}
RICKLIB.OLB is opened for compression. If RICKLIB.OLB is an
object library, the file TEMP.OLB is created to receive the
compressed output. If RICKLIB.OLB is a macro library (a
nonstandard use of the type OLB) , the file TEMP.MLB is
created'.

LBR>/DF:OBJ_/
LBR>TEMP/CO=RICKLIB.MLB_}
Assuming that file RICKLIB.MLB is a macro library, the macro
library file TEMP.MLB is created to receive the compressed
output.

7.5.5

Delete Global Switch (/DG)

FUNCTION
The Delete Global switch provides the user with a facility for
deleting a specified entry point (global symbol) from the EPT. Up to
15 entry points may be deleted with one command.
This command does
not affect the object module which contains the actual symbol
definition.

7-13

LIBRARIAN UTILITY PROGRAM (LBR)
When LBR begins processing the /DG switch,
message on the initiating terminal:

prints

the

following

ENTRY POINTS DELETED:
As entry points are deleted from the library file, the entry point is
printed on the initiating terminal. See the example at the end of
this section.
If a specified entry point is not contained in the EPT, a message is
printed on the initiating terminal, and the processing of the current
command is terminated. This message is as follows:
LBR -- *FATAL* - NO ENTRY POINT NAMED "name"
The /DG switch can only be appended to the 1 ibrary file specifier.
FORMAT
outfile/DG:global-l[:global-2: .•. :global-n]
·where:
outfile

is the library file specifier.

/DG

is the Delete Global switch.

global

is the name of the entry point to be deleted.

EXAMPLE
LBR>RICKLIB/DG:SHEILA:LAURA:JENNY_}
ENTRY POINTS DELETED:
SHEILA
LAURA
JENNY
In this example, the entry points SHEILA, LAURA and JENNY are deleted
from the latest version of the library file named SYO:RICKLIB.OLB.

7.5.6

Insert Switch (/IN)

FUNCTION
The Insert switch provides the user with a facility for inserting
library modules into a library file. Any number of input files can be
specified, and each file can contain any number of concatenated input
modules.
For macro libraries, only first-level macro definitions are
extracted from the input files. All text outside of the first-level
macro definitions is ignored. The /IN switch is the default library
file option, and can be appended only to the library file specifier.

7-14

LIBRARIAN UTILITY PROGRAM (LBR)
If the user attempts to insert an input module which already exists in
the library file, the following message is printed on the initiating
terminal:
LBR -- *FATAL* DUPLICATE MODULE NAME "name" IN filename
Likewise, if the user attempts to insert a module and a module
contains an entry point that duplicates one that is already in the
EPT, the following message is printed on the initiating terminal:
LBR -- *FATAL* DUPLICATE ENTRY POINT "name" IN filename
FORMAT
outfile[/IN]=infile-l[,infile-2, ... ,infile-n]
where:
outfile

is the file specifier for the library file into
which the input modules are to be inserted. The
default type depends on the current default (see
Section 7.5.4). It is .OLB if the current default
is object libraries or .MLB if the current default
is macro libraries.

/IN

is the Insert switch.

inf ile

is the file specifier for
the
input
file
containing modules to be inserted into the library
file. The default type is .OBJ if outfile is an
object library and .MAC if outfile is a macro
library.

EXAMPLE
LB R> RIC KL IB /IN =SHE I LA, LA URA, JENNY.)
In this example, the modules contained in the latest versions of files
SHEILA, LAURA and JENNY, which reside in the default directory on
SYO:, are inserted into the latest version of the library file
RICKLIB; which also resides in the default directory on SYO:= The
default file type for files SHEILA, LAURA, and JENNY is .OBJ if
RICKLIB is an object module library or .MAC if RICKLIB is a macro
library.

7.5.7

List Switches (/LI, /LE, /FU)

FUNCTION
The List switches provide the user with a facility for producing a
printed listing of the contents of a library file. Three switches
allow the user to select the type of listing desired. Th~se switches
are as follows:
/LI

Produces a listing of the names of all modules
library file.

the

/LE

Produces a listing of the names of all modules in
library file and their corresponding entry points.

the

7-15

LIBRARIAN UTILITY PROGRAM (LBR)
/FU

Produces a listing of the names of all modules in the
library file and gives a full module description for
each:
i.e.,
size,
date
of
insertion,
and
module-dependent information.
NOTE
Appendix B.l contains sample listings
three types of library listing.

These switches can be appended only to the output
the list file specifier.

file

all

specifier

FORMAT
outfile[,listfile]/switch(es)
where:
outf ile

is the file specifier for the library
contents is to be listed.

1 istfile

is the optional listing file specifier.
is directed
specified,
the
listing
initiating terminal.

/switch (es)

file

whose
If

not
the

is the list option(s) selected.
NOTE
The /LI switch is the default value, and
need not be specified when a listing file
has been specified, or when any other list
switch is included in the command.

EXAMPLES
1.

LBR>RICKLIB/LI__}

In this example, a listing of the names of all the modules contained
in file SYO:RICKLIB.OLB is printed on the initiating terminal.
2.

LBR>RICKLIB/LE_.,/

In this example, a listing of the names of all the modules and their
entry points (contained in file SYO:RICKLIB.OLB) is printed on the
initiating terminal.
3.

LBR>RICKLIB/FU__}

In this example, a listing of the names of all the modules, and a full
description of each module contained in file SYO:RICKLIB.OLB, is
printed on the initiating terminal.

7-16

LIBRARIAN UTILITY PROGRAM (LBR)
4.

LBR>DKl: [200 1 200]RICKLIB,LP:/LE/FU_J

In this example, a listing of the names of all the modules, their
entry points, and a full description of each module for file RICKLIB,
residing in directory [200,200] on DKl:, is printed on the line
printer.

7.5.8

Replace Switch (/RP)

FUNCTION
The Replace switch provides the user with a facility for replacing
modules in a library file with input modules of the same name. Any
number of input files are allowed, and each file can contain any
numbe~ of concatenated input modules.
When a match occurs on a module name, the existing module is logically
deleted, and all of its entries are removed from the EPT. The /RP
switch does not imply module replacement on matching entry point
names. That condition is always fatal.
As each module in the library file is replaced, a message is printed
on the initiating terminal. This message, which contains the name of
the module being replaced, is as follows:
MODULE "name" REPLACED
If the module to be replaced does not exist in the library file, LBR
assumes that the input module is to be inserted and automatically
inserts it without printing a message.
FORMAT
The /RP switch can be specified in either of the following formats:
a.

Global format - The /RP switch is appended to the file
specifier, and all of the input files are assumed to contain
modules to be replaced.

Local format - The /RP switch is appended to an input file
specifier, and only the file to which the /RP switch is
appended is considered to contain modules to be replaced.

Global Format
outfile/RP=infile-l[,infile-2,.,.,infile-n]
where:
out file

is the file specifier for the library file.
The
default type depends on the current default (see
Section 7.5.4). It is .OLB if the current default
is object libraries or the .MLB if the current
default is macro libraries.

7-17

LIBRARIAN UTILITY PROGRAM {LBR)
/RP

is the Replace switch.

inf ile

is the input file specifier for the file that
contains modules to be replaced in the library
file. The default type is .OBJ if outfile is an
object library, or .MAC if it is a macro library.

This format of the /RP switch allows the user to specify a list of
input files without having to append the /RP switch to each of them.
NOTE
Should the user want to override the
global function for a particular input
file {that is, to instruct LBR
to
process a particular file in a list as a
file containing modules to be inserted
but not replaced) , the user can append
/-RP or /NORP to the desired input file
spec if ier.
Local Format
outfile=infile-1 [/RP] [, infile-2 [/RP], ... , infile-n [/RP]]
where:
outf ile

is the file specifier for the library file.
The
local format default is the same as the global
format default described above.

infile

is the input file specifier for the file that
contains modules to be inserted or replaced in the
output library file. The local format default is
the same as the global format default described
above.

/RP

is the Replace switch.
NOTE
Appending the /RP switch to an input file
specifier constitutes the local format of
the switch.
This overrides
the
LBR
default (Insert) and instructs LBR to
treat the module(s) contained in
the
specified file as modules to be replaced.

7-18

LIBRARIAN UTILITY PROGRAM (LBR}
EXAMPLES
The files used in the following four examples, and the modules
contained within each file, are depicted in Figure 7-6. For the
examples, these files are assumed to reside in the default directory
on the default device, and the initial state of the library file is
assumed to be as shown in Figure 7-6.
1.

LBR>RICKLIB/RP=SHEILA, LAURA, JENNY..)
MODULE
MODULE
MODULE
MODULE
MODULE

"SHEILA"
LAURAl"
"LAURA2"
"JENNYl"
"JENNY2"
11

REPLACED
REPLACED
REPLACED
REPLACED
REPLACED

In this example, the global format for the /RP switch is used. Object
modules from the input files SHEILA, LAURA, and JENNY replace modules
by the same names in the library file named RICKLIB.
The resulting
library file is shown in Figure 7-7.
2.

LBR>RICKLIB=CHRIS, SHEILA/RP-./
MODULE "SHEILA" REPLACED

In this example, the local format of the /RP switch is used.
The
object module SHEILA from file SHEILA is replaced in the library file
RICKLIB. The object modules in the file CHRIS are inserted in the
library file.
(See Insert switch in Section 7.5.6.) The resulting
library file is shown in Figure 7-8.

7-19

Output
Library File
File Name

RICKLIB. OLB; 1
JENNYl

-.I

""'

Input Files
SHEILA.OBJ;l

LAURA.OBJ;!

JENNY.OBJ;!

CHRIS. OBJ; 1

SHEILA

LAURA!

JENNYl

CHRIS!
CHRIS2

Object

JENNY2

LAURA2

JENNY2

Modules

LAURA!

LAURA3

JENNY3

LAURA2
SHEILA

Figure 7-6
Sample Files Used in LBR Examples

LIBRARIAN UTILITY PROGRAM (LBR}
RICKLIB. OLB; 1

JENNYl
JENNY2
JENNY3

LAURAl
LAURA2
LAURA3

SHEILA
*These modules did not exist on the
library file prior to the execution of
this example, but they did exist on the
input files.
LBR, therefore, assumed
that they were to be inserted.
Since
LBR handled these modules as a normal
insert, no message was printed on the
input terminal.

Figure 7-7
Output Library File After Execution of Example 1

RICKLIB. OLB; 1
CHRISl

CHRIS2

JENNYl
JENNY2
LAURAl
LAURA2
SHEILA

*This module replaced
**These modules inserted
Figure 7-8
Output Library File After Execution of Example 2

7-21

LIBRARIAN UTILITY PROGRAM (LBR)
3.

LBR>RICKLIB/RP=SHEILA,LAURA,JENNY,CHRIS/-RP..)
MODULE
MODULE
MODULE
MODULE
MODULE

"SHEILA"
"LAURAl II
"LAURA2"
11
JENNY1 11
"JENNY2"

REPLACED
REPLACED
REPLACED
REPLACED
REPLACED

In this example, the /-RP switch is used to override the global format
of the command. Object modules in files SHEILA, LAURA, and JENNY are
processed as modules to be replaced, and file CHRIS is processed as a
file which contains modules to be inserted. The resulting library
file is shown in Figure 7-9.
RICKLIB. OLB; 1
CHRIS!

CHRIS2

JENNY!
JENNY2
JENNY3

LAURA!
LAURA2
LAURA3

SHEILA
*These modules were inserted by default.
**These modules were specified to be
inserted. Had a module of the same name
been present, a
fatal error message
would have been issued. See Example 4
below.

Figure 7-9
Output Library File After Execution of Example 3

LBR>RICKLIB/RP=SHEILA,LAURA/-RP,JENNY..)
MODULE "SHEILA" REPLACED
LBR -- *FATAL* -- DUPLICATE MODULE "LAURA!" IN LAURA.OBJ;!

In this example, only module SHEILA from file SHEILA was replaced.
The user specified that the modules in file LAURA not be replaced
(/-RP), but inserted. One of the modules contained in file LAURA
duplicated an already existing module in file RICKLIB (see Figure
7-6). Therefore, LBR issued the fatal error message and terminated
the processing of the current command.

7-22

LIBRARIAN UTILITY PROGRAM (LBR)
7.5.9

Spool Switch (/SP}

The Spool switch is the list file default switch. Whether the switch
is specified or not, the results are the same, i.e., the listing file
is spooled to the line printer. The listing file can be spooled to
any file-structured device (e.g., disk).
After the listing file is created, a request is made to the print
spooler task to print the spooled file;
printing is performed
asynchronously (see Appendix C for a description of the spooler task).
The automatic printing of the listing file can be inhibited by
specifying a minus sign (-) or the letters NO between the slash (/)
and the SP in the spool switch (/-SP or /NOSP).
This causes the
listing file to be created, but the request to the print spooler task
is not issued. Therefore, the file is not automatically printed.
The /SP switch can only be appended to the list file specifier.
FORMAT
outfile,listfile[/SP] or [/-SP]
where:
outfile

is the file specifier for the library file.

l istf ile

is the listing file specifier.

/SP or /-SP

is the Spool switch.

EXAMPLE
LBR>RICKLIB/DE: SHEILA 1 RICKLST/-SP ._/

In this example, the following occurs:
1.

The module SHEILA and its associated entry points are deleted
from the library file SY:RICKLIB.

The listing of the contents of resulting library file RICKLIB
is written to the list file SY:RICKLST.LST. ~Ince the /-SP
switch is specified, the file is not automatically printed.

7.5.10

Selective Search Switch (/SS)

FUNCTION
The Selective Search switch is used to set the selective search
attribute bit in the module header of object modules as they are
inserted into an object library.
The switch has no effect when
applied to modules being inserted into a macro library. The switch
may be specified only on input files for insertion or replacement
operations, and it affects all modules in the input file to which it
is applied.
Object modules with the selective search attribute are given special
treatment by the Task Builder. Global symbols defined in modules with
the selective search attribute are only included in the Task Builder's

7-23

LIBRARIAN UTILITY PROGRAM (LBR)
symbol table if they are previously referenced by other modules.
Thus, only referenced symbols will be listed with the module in the
Task Builder memory allocation file, thereby reducing task build time.
The /SS switch should only be applied to object files whose modules
contain only absolute (not relocatable) symbol definitions.
See the
RSX-llM Task Builder Reference Manual for more information.
FORMAT
outfile=infile-1/SS[,infile-2[/SS] , ... ,infile-n[/SS]]
where:
outf ile

is the file specifier for the library file.

inf ile

is the file specifier for the input file
contains modules to be selectively searched.

/SS

is the Selective Search switch.

7.5~11

that

Squeeze Switch (/SZ)

FUNCTION
The Squeeze switch provides the user with a facility for reducing the
size of macro definitions by eliminating all trailing blanks and tabs,
blank lines, and comments from macro text. The /SZ switch is used to
conserve memory in the MACR0-11 Assembler and to reduce the size of
macro library files. The Squeeze switch has no effect on object
libraries.
FORMAT
The /SZ switch can be specified in either of the following formats:
1.

Global format - The /SZ switch is appended to the library
file specifier, and all of the input files are assumed to
contain modules to be squeezed.

Local format - The /SZ switch is appended to an input file
specifier, and only the file to which the /SZ switch is
appended is considered to contain modules to be squeezed.

Global Format
outfile/SZ=infile-l,[,infile-2, ... ,infile-n]
where:
outf ile

is the file specifier for the library file.

/SZ

is the Squeeze switch.

infile

is the file specifier for the input file that
contains modules to be squeezed before being
inserted into the library file.

This format of the /SZ switch allows the user to specify a list of
input files without having to append the /SZ switch to each of them.

7-24

LIBRP_RIAN UTILITY PROGRAM (LBR)
NOTE

Should the user want to override the
global function for a particular input
file (that is, to instruct LBR
to
process a particular file in a list as a
file containing modules to be inserted
but not squeezed), the user can append
/-SZ or /NOSZ to the desired input file
specifier.
Local Format
outfile=infile-1/SZ [ ,infile-2 [/SZ], ... , inft°le-n[/SZ]]
where:
outfile

is the file specifier for the library file.

inf ile

is the file specifier for the file that contains
modules to be squeezed before being inserted into
the library file.

/SZ

is the Squeeze

s~itch.

NOTE

LBR uses the following algorithm on each
line to be squeezed and inserts the
resultant line into the library file:
1.

The line is examined for
rightmost semicolon (;).

If a semicolon is

the

located, it
deleted, along with all
trailing characters
the
in
line.
is

All trailing blanks and tabs in
the line are deleted.

If the resulting line is null,
nothing is transferred to the
library file.

EXAMPLE
Figure 7-10 illustrates the use of the LBR /SZ switch.
A file
containing input text to be squeezed is illustrated, along with the
text actually inserted into the library file after the squeeze
operation has been completed.

7-25

LIBRARIAN UTILITY PROGRAM {LBR)
BEFORE BEING SQUEEZED
.MACRO

MOVSTR RX,RY,?LBL

;***

- - NOTE :
BOTH ARGUMENTS MUST BE REGISTERS

LBL:

MOVB
BNE
DEC

{RX)+, (RY)+
LBL
RY

;MOVE A CHARACTER
;CONTINUE UNTIL NULL SEEN
;BACKUP OUTPUT PTR TO NULL

;END OF MOVSTR
.ENDM

AFTER BEING SQUEEZED
.MACRO

MOVSTR RX,RY,?LBL

;***

- - NOTE :

;
LBL:

BOTH ARGUMENTS MUST BE REGISTERS
MOVB
{RX)+, {RY)+
BNE
LBL
DEC
RY
.ENDM

Figure 7-10
MACRO Listing Before and After Running LBR with /SZ Switch

7.6

COMBINING LIBRARY FUNCTIONS

Two or more library functions may be requested in the same command
line.
The only exceptions are that COMPRESS cannot be requested with
anything else except LIST, and CREATE and DELETE cannot be specified
in the same command line.
Functions are performed in the following order:
1.

/DF

/CR or /CO

/DE

/DG

/IN, /RP, /SS, /SZ

/LI, /LE, /FU

EXAMPLE
LBR>FILE/DE:XYZ:$A,LP:/LE/FU=MODX,MODY/RP__}

7-26

LIBRARIAN UTILITY PROGRAM (LBR)
Functions are performed in order, as:
Delete modules XYZ and $A.
Insert all modules from MODX and MODY, replacing
of modules in MODY.

any

duplicates

Produce a listing of the resultant library file on the
printer with full module descriptions and all entry points.

7.7

line

LBR CONSTRAINTS

The following constraints apply to LBR:

7.8

Limit of 65,536(10) words per module.

Limit of 65,536(10) blocks per library,

Tables should be allocated to maximum anticipated size.
Expanding table allocations requires using Compress to copy
the entire file.

A fatal error results if an attempt is made to insert a
module into a library which contains a differently named
module with the same entry point.
See Insert command,
Section 7. 5. 6.

The use of "wild cards" in file specifiers is not allowed
(i.e., forms such as *.OBJ, where the "*" is used to indicate
"all modules with type .OBJ").

LBR ERROR MESSAGES

Error messages reported
diagnostic and fatal.

the

user

LBR

are

two

types:

Diagnostic error messages inform the user that a condition exists that
requires consideration, but the nature nF the condition does not
warrant termination of the command. Diagnostic messages are issued to
TI:, in the format:
LBR -- *DIAG* - message
Fatal error messages inform the user that a condition exists that
caused LBR to terminate the processing of a command. When this
occurs, LBR returns to the highest level of command input.
For
example, if the command is entered in response to the MCR prompt,
i.e.,
>LBR command
then, LBR issues the fatal error message and exits. If, however,
command is entered in response to the LBR prompt, i.e.,
LBR>command
LBR issues the fatal error message and reprompts.

7-27

the

LIBRARIAN UTILITY PROGRAM (LBR)
Fatal error messages are issued to TI:

in the format:

LBR -- *FATAL* - message
NOTE
If a fatal error occurs during the
processing of an indirect command file,
the command file is closed, the fatal
error message, followed by the command
line in error, is issued to TI:, and LBR
returns to the highest level of command
input.

7.8.l

Effect of Fatal Errors on Library Files

The status of a library file after fatal errors is:
errors

leave

In general, output
indeterminate state.

During the deletion process, the library is rewritten prior
to the printing of the individual module-Jentry-point-deleted
messages.

During the replacement process, the library is rewritten
prior to the printing of the individual module-replaced
messages.

During the insert process, the library is rewritten after the
insertion of all modules in each individual input file, i.e.,
between input files.

7.8.2

Error Messages

LBR

ILLEGAL GET COMMAND LINE ERROR CODE

the

library

Description
The system, for some reason, is unable to read a command line.
This is an internal system failure.
Suggested User Action
Reenter the command line.
If the
software support representative.

problem

persists,

consult

LBR -- INPUT ERROR ON filename
Description
The file system, while attempting to process an input
detected an error.

7-28

file,

has

LIBRARIAN UTILITY PROGRAM (LBR)
A problem exists with the physical device
down) .

(e.g.,

device

cycled

The user has entered a command in a format that does not
to syntax rules.

conform

Suggested User Action
Reenter the command line.
LBR -- COMMAND SYNTAX ERROR
command line
Description

Suggested User Action
Reenter the command line, using the correct syntax.
LBR -- OUTPUT ERROR ON filename
Description
A write error has occurred on the
following conditions may exist:

The volume is full.

The device is write-protected.

The hardware has failed.

output

file.

One

the

Suggested user Action
If the volume is full, the user
files and rerun LBR.

should

delete

If the device is write-protected, the user
the device, and reenter the command line.

all

unnecessary

should

write-enable

If the hardware has failed, the user can swap devices and reenter
the command line or wait until the device is repaired and rerun
LBR.
LBR -- ILLEGAL SWITCH
command line
Description
The user specified a non-LBR switch
invalid context.

legal

switch

Suggested User Action
Reenter the command line with the correct switch specification.

7-29

LIBRARIAN UTILITY PROGRAM (LBR)
LBR

INSUFFICIENT DYNAMIC MEMORY TO CONTINUE
Description
The partition in which LBR is running is too small.
Suggested User Action
Remove the task (LBR), install it
reenter the command line.

larger

partition,

and

LBR -- INVALID LIBRARY TYPE SPECIFIED
Description
The user specified an illegal library type in a CREATE or DEFAULT
command.
The file types OBJ and MAC are the only valid
specifications. See Sections 7.5.2 and 7.5.4.
Suggested User Action
Reenter the command line with OBJ or MAC specified.
LBR -- COMMAND I/O ERROR
Description
One of the following conditions may exist:
1.

A problem exists on the physical
up) .

device

The file is corrupted or the format
record length exceeds 132 bytes).

(e.g.,
is

not

cycled

incorrect

(e.g.,

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

LBR -- INDIRECT FILE OPEN FAILURE
command 1 ine
Description
The requested indirect command file does not exist as
One of the following conditions may exist:

specified.

The user directory area is protected against access.

A problem exists on the physical device (e.g., device
down) .

The volume is not mounted.

The specified file directory does not exist.

7-30

cycled

LIBRARIAN UTILITY PROGRAM (LBR)
5.

The file does not exist as specified.

Insufficient dynamic memory in Executive.

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

LBR -- INDIRECT COMMAND SYNTAX ERROR
command line
Description
The user specified an indirect file in a
conform to syntax rules.

format

that

does

not

Suggested User Action
Reenter the command line with the correct syntax.
LBR -- BAD LIBRARY HEADER
Description
Either the file is not a library file or the file is corrupted.
Suggested User Action
1.

If the file is not a library file, reenter the
with a proper library file specified.

command

line

If the file is a proper library file, the user should run the
file structure verification utility {VFY) against the volume
to determine if it is corrupted (see Chapter 8).

If the volume is corrupted, it must be
it can be used.

reconstructed

before

An attempt has been made to exceed one level of indirect
files.

command

LBR -- INDIRECT FILE DEPTH EXCEEDED
command line
Description

Suggested User Action
Rerun the job with only one level of indirect command file.

7-31

LIBRARIAN UTILITY PROGRAM (LBR)
LBR -- I/0 ERROR ON INPUT FILE filename
Description
A read error has occurred on an input file.
conditions may exist:
device

One of the following

A problem exists on the physical
up) •

(e.g.,

The file is corrupted or the format is wrong
exceeds 132 bytes) .

not

cycled

(record

length

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

LBR -- OPEN FAILURE ON FILE filename
De script ion
The file system, while attempting to open a file, has detected an
error. One of the following conditions may exist:
1.

The user directory area is protected against an open.

A problem exists on the physical device (e.g., device
down) .

The volume is not mounted.

The specified file directory does not exist.

The file does not exist as specified.

Insufficient contiguous space to allocate
(compress and create only).

Insufficient dynamic memory in Executive.

the

library

cycled

file

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

LBR -- INVALID EPT AND/OR MNT SPECIFICATION
Description
The user, when specifying a /CR or /CO command, entered an EPT or
MNT value which was greater than 4096(10).
Suggested User Action
Reenter the command line with the correct value specified.
7-32

LIBRARIAN UTILITY PROGRAM (LBR)
LBR -- POSITIONING ERROR ON filename
Description
The device is write-locked.
Suggested User Action
If the device is write-locked, write enable it
command line.

and

reenter

the

LBR -- EPT OR MNT EXCEEDED IN filename
De script ion
The EPT or MNT table limit has been reached during the
of an Insert or Replace command.

execution

Suggested User Action
1.

Copy the library, increasing the table space via the COMPRESS
command.

Reenter the command line.

LBR -- DUPLICATE MODULE NAME "name" IN filename
Cescription
An attempt has been made to insert (without replacement) a module
into a library that already contains a module with the specified
name.
Suggested User Action
1.

Determine if the specified input file is the correct file.

If the input file is correct, the user must decide whether to
delete the duplicate module from the library file and insert
the new one, or replace the duplicate module by rerunning LBR
with the /RP switch appended to the input file specifier.

LBR -- GET TIME FAILED
Description
This error occurs when LBR attempts to execute a Get Time
Parameters directive and fails. The error is caused by a system
malfunction.
Suggested User Action
Reenter the command line.
If the
software support representative.

7-33

problem

persists,

consult

LIBRARIAN UTILITY PROGRAM {LBR)
LBR -- NO MODULE NAMED "module"
Description
The user has attempted to delete a module
specified library file.

that

not

the

Suggested User Action

LBR

Determine if the module name is misspelled or
library file is specified.

the

Reenter the command
spec i f ied.

module

name

correctly

line

with

the

wrong

INVALID NAME -- "name"
De script ion
A module name or entry point that contains
character has been specified for deletion.

non-Radix-50

NOTE
Radix-50 characters consist of the letters A through Z,
the numbers 0 through 9, and the special characters
period {.) and dollar sign {$).
Suggested User Action
Reenter the command line with a valid name.
LBR -- LIBRARY FILE SPECIFICATION MISSING
Description
The user has entered a command
file.

without

specifying

the

library

Suggested User Action
Reenter the command line with the library file specified.
LBR -- ILLEGAL SWITCH COMBINATION
Description
The user has
combination.

specified switches
See Section 7.6.

that

cannot

executed

Suggested User Action
Reenter the command line, specifying the switches in
sequence.

7-34

the

proper

LIBRARIAN UTILITY PROGRAM (LBR)
LBR -- NO ENTRY POINT NAMED "name"
Description
--..!-.L..
The user has attempted to delete an entry pV.1.lll.
the specified library file.

-~~

llV l.

Suggested User Action
1.

Determine if the entry point is misspelled or
library file is specified.

Reenter the command
specified.

line

with

the

entry

the

point

wrong

correctly

LBR -- DUPLICATE ENTRY POINT NAME "name" IN filename
Description
An attempt has been made to insert a module into a library
when both contain an identically-named entry point.

file

Suggested User Action
1.

Determine if the specified input file is the correct file.
If not, reenter the command line, specifying the correct
input file.

If the input file is the correct file, the user may
the duplicate entry point from the library and rerun.

delete

LBR = = TOO MANY OUTPUT FILES SPECIFIED

Description
The user has specified more than two output files;
following assumptions:

LBR makes the

The first output file specified is the output library file.

The second output file specified is the listing file.

The third through n files specified to the left of the
sign are ignored.

equal

Suggested User Action
No action is required.
were not specified.

LBR continues as though the extra file(s)

LBR -- EXACTLY ONE INPUT FILE MUST APPEAR WITH. /CO
Description
The user has specified no file or more
file in the /CO command.

7-35

than

one

input

library

LIBRARIAN UTILITY PROGRAM (LBR}
Suggested User Action
Reenter the command line with only one input file specified.
LBR -- FATAL COMPRESS ERROR
Description
The user's input library file is corrupted or is
file.

not

library

Suggested User Action
No recovery is
reconstructed.

possible.

The

file

must

question

LBR -- EPT OR MNT SPACE EXCEEDED IN COMPRESS
Description
The user has specified an EPT or MNT table size for the output
library file that is not large enough to contain the EPT or MNT
entries used in the input library file.
Suggested User Action
Reenter the command line with a larger
specified.

EPT

MNT

table

size

LBR -- ERROR IN LIBRARY TABLES, FILE filename
Description
The library file is corrupted or is not a library file.
Suggested User Action
If the file is corrupted, no recovery is possible;
be reconstructed.

the file must

If the file is not a library file, the user should reenter
command line with the correct library file specified.

the

LBR -- INVALID FORMAT, INPUT FILE filename
Description
The format of the specified input file is not the standard format
for a macro source or object file, or the input file is
corrupted.
Suggested User Action
Reenter the command line with the correct input file specified.

7-36

LIBRARIAN UTILITY PROGRAM (LBR)
LBR -- OPEN FAILURE ON LBR WORK FILE
Description
The file system, while attempting to open the LBR work file,
detected an error.

has

NOTE
The LBR work file is created on the volume from which LBR
was installed.
One of the following conditions may exist:
1.

The volume is full.

The device is write-protected.

A problem exists with the physical device.

Insufficient dynamic memory in Executive.

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

LBR -- MARK FOR DELETE FAILURE ON LBR WORK FILE

Description
When LBR begins processing commands, it automatically creates a
work file and marks it for delete. For some reason, this marking
for delete failed.
The work file constitutes a lost file, because it does not appear
in any file directory.
Suggested User Action
The file may be deleted by running
the
verification utility (VFY) (see Chapter 8).

file

structure

LBR -- ILLEGAL FILENAME
command line
Description
The user has entered one of the following:
1.

A file specifier which contains a wild card.

A file specifier which contains neither a filename
type.

7-37

nor

file

LIBRARIAN UTILITY PROGRAM (LBR)
~uggested

User Action

Reenter the command line correctly.
LBR -- ILLEGAL DEVICE/VOLUME
command line
Description
The user has entered a device specifier that does not conform
syntax rules.

NOTE
A device specifier consists of 2 ASCII characters,
followed by one or two optional octal digits.
Suggested User Action
Reenter the
specified.

command

line

with

the

correct

device

syntax

LBR -- ILLEGAL DIRECTORY
command line
Description
The user has entered a UIC that does not conform to syntax rules.
NOTE
UIC syntax consists of a left square
bracket, followed by one to three octal
digits, a comma, one to three octal
digits, and terminated by a right square
bracket.
Suggested User Action
Reenter the command line with the correct UIC syntax.
LBR -- WORK FILE I/O ERROR
Description
A write error has occurred on the LBR
following conditions may exist:
1.

The volume is full.

The device is write-protected.

The hardware has failed.

7-38

work

file.

One

the

LIBRARIAN UTILITY PROGRAM (LBR)
Suggested User Action
If the volume is full, the user
files and rerun.

should

delete

If the device is write-protected, the user
the device, and reenter the command line.

all

should

unnecessary
write

enable

If the hardware has failed, the user can swap devices and retry
the command, or wait until the device is repaired and rerun LBR.
LBR -- VIRTUAL STORAGE REQUIREMENTS EXCEED 65536 WORDS
Description
This error may occur with maximum size libraries in conjuction
with a single command line which logically deletes a large number
of modules and entry points, and continues to replace them with
an equally large number of modules and entry points having highly
dissimilar names.
Normally, this message indicates some
error.

sort

internal

system

Suggested User Action
Rerun the job, but divide the complicated command line
several smaller command lines which do the same operations.

7-39

into

CHAPTER 8
FILE STRUCTURE VERIFICATION UTILITY (VFY)

8.1

INTRODUCTION TO VFY

The File Structure Verification Utility (VFY} program provides:
1.

The ability to check the
file-structured volume.

readability

The ability to print out the number of available blocks on
file-structured volume (/FRee}.

The ability to search for files which are in the index file,
but not in any directory, i.e., files which are "lost" in the
sense that they cannot be accessed by filename
(/LOst}
(see
RSX-11 I/0 Operations Reference Manual for a description of
the index file} .

The ability to list all files in the index file, showing
file ID, filename, and owner (/List}.

The ability to mark as "used" all the blocks that appear to
be
available, which are actually allocated to a file
(/UPdate}.

The ability to rebuild the storage allocation bit map so that
it properly reflects the information in the index file
(/REbuild} .

The ability to restore
(/DElete}.

for

delete

The ability to perform a read check on every allocated
on a file-structured volume (/RC}.

block

files

that

are

and

validity

marked

NOTES
1.

There should be no other activity on the volume;
in particular, activities which create new files,
extend existing files, or delete files while VFY
is running.

VFY must not be aborted while a /UP, /RE or /DE
command is being processed. Aborting VFY while it
is in the process of modifying the
storage
allocation or index files may seriously endanger
the integrity of that volume.

8-1

the

FILE STRUCTURE VERIFICATION UTILITY (VFY)
8.2

INITIATING VFY

All RSX-llM utility programs can be initiated in several ways.
methods are described in Section 1.2. The methods for VFY are:

These

~VFY__}

>VFY command string__)
>RUN ... VFY-./
>RUN ..• VFY/UIC=[group,member]__J
>RUN $VFY_}
>RUN $VFY/UIC=[group,member]__J
VFY normally operates in a read-only mode, assuming that the scratch
file, if required, is on another device. VFY requires write-access
under the following conditions:
1.

If the /UP or /RE switch is used, VFY requires write-access
to the storage allocation map ([0,0]BITMAP.SYS).

If the /DE switch is specified, VFY requires write-access
the index file ([0,0]INDEXF.SYS).

If the /LO switch is specified and lost files are found,
requires write-access to the [1,3] user file directory.

VFY

VFY may be run under any UIC if only read access is required.
write access is required, VFY must run under a system UIC.

8.3

VFY COMMAND STRING

All commands to VFY are issued by entering a VFY command string
through the initiating terminal. The VFY command string is formatted
as follows:
listfile,scratchdev=indev/switch
or
indev/switch

(This is a short form of TI:,indev=indev/switch)

where:
listfile

specifies the output listing file in the following
format:
dev: [uic]filename.typ;ver

scratchdev

specifies the device on which the scratch file
produced by VFY is to be written. This parameter
is in the following format:
dev:

8-2

FILE STRUCTURE VERIFICATION UTILITY (VFY)
The scratch file is used by VFY during the
verification scan and during the lost file scan.
It is created but is not entered in a directory.
Therefore, it is invisible to the user. The
scratch file is
automaticallv
deleted
upon
termination of the VFY program. NOTE
If the user has reason to suspect that his
system disk is of questionable integrity,
the scratch file should be forced onto
another
device
by
utilizing
this
parameter.
It is recommended that the scratch file
always be assigned to another volume. The
scratch file is not used for the /FREE and
/LIST commands.

indev

specifies the volume to be
verified.
parameter is in the following format:

This

dev:
/switch

specifies the function to be performed,
parameter is in the following format:

This

/sw
The VFY command switches are described in detail
in Section 8.4.
If no switch is specified, the
VFY program performs a validity check.
For a complete description of command strings, see Section 1.3.

u.~.i

Defaults in File

Default file specifiers are listed in Table 8-1.

8-3

FILE STRUCTURE VERIFICATION UTILITY (VFY)
Table 8-1
VFY Default File Specifiers
Element
dev:

Default Value
Output listing device
TI:
Scratch file device
SYO:
Volume to be verified
SYO:

8.4

[uic]

The UIC under which VFY is currently running.

filename

No default - must be specified.

.typ

No default - must be specified.

;ver

Latest version plus 1.

VFY COMMAND SWITCHES

VFY commands are specified in the form of switches appended to the VFY
command string.
Command switches and functions are summarized in
Table 8-2.
Table 8-2
VFY Functions and Switches
Function

Switch

Validity Check

Null

Check readability and validity
of
volume mounted on
the
specified device.

Delete

/DE

Reset
indicators.

Update

/UP

Allocate blocks which appear
to be available but have been
allocated to a file.

Purpose

8-4

marked-for-delete

FILE STRUCTURE VERIFICATION UTILITY (VFY)
Table 8-2 (Cont.)
VFY Functions and Switches
Fune ti on

Purpose

Switch

Rebuild

/RE

Recover blocks which appear to
be
allocated
but are not
contained in a file.

Free

/FR

Print out the available
on a volume.

space

Scan entire file
structure
looking LuL files wIIl.(.;n are
not in any directory.

Lost

List

/LI

List entire index file by file
iden ti f ica ti on.

Read Check

/RC

Check entire volume to see if
every block of every file can
be read.

8.4.1

Validity Check

Validity Check (no command switch) checks the readability and validity
of the volume mounted on the specified device. This feature entails
reading all the file headers in the index file and checking that all
the disk blocks referenced in the map area of each file header are
marked as allocated in the bit map (i.e., allocated to that file).
Rules for running the Validity Check:
1.

The volume to be checked must
structured volume, as follows:

mounted

Files-11

another

2._MOU dev:_)
2.

The volume may be write-protected if:
a.

It is not the system volume;

The required scratch file
file-structured volume.

directed

When the validity check is completed, a listing of the
printed. This output is described in Section 8.4.1.1.

8-5

results

FILE STRUCTURE VERIFICATION UTILITY (VFY)
8.4.1.1 File Error Reporting - After the volume has been verified,
and the normal output messages have been printed, error conditions are
reported. All errors for a given file are preceded by a file
identification line that identifies the file in error. This line is
formatted as follows:
FILE ID nn,nn filename.type;version OWNER [g,m]
where:
nn,nn

is the unique file iden ti f ica ti on number assigned
to the file by the system at file-creation time.

filename

is the user filename.

.type

is the file type (i.e., OBJ for object file).

;version

is the version number of the file.

[g,m]

is the UIC which owns the file.

This file identification line is
following messages:

followed

one

the

I/O ERROR READING FILE HEADER-ERROR CODE -32
Failed to read the file header for the specified file ID.
BAD FILE HEADER
Software checks on the validity of the file header
that the header has been corrupted.

indicate

MULTIPLE ALLOCATION n,n
The specified (double precision)
logical block number is
allocated to more than one file. If this error occurs, a
second pass is automatically taken which will indicate all
files that share each multipally allocated block. The
second pass is taken after all file headers have been
checked (see Section 8.4.1.3).
BLOCK IS MARKED FREE n,n
The specified logical block number is allocated to the
indicated file but is not marked as allocated in the storage
allocation map.
(see Section 8.4.1.4).
BAD BLOCK NUMBER n,n
The specified block number was found in the header for
file but is illegal for the device (out of range).
indicates a corrupted file header.

this
This

FILE IS MARKED FOR DELETE
This indicates that a system failure occurred while the
The deletion was not
specified file was being deleted.
completed and the file header still exists (see Section
8.4.1.2).

8-6

FILE STRUCTURE VERIFICATION UTILITY (VFY)
HEADER MAP OUT OF SYNC
This indicates an error in the header map
indicates a corrupted file header.

which

also

The last error message for the file is followed by a summary line
that file, as follows:

for

SUMMARY:

area

MULT=nn, FREE=nn, BAD=nn.

where:
MOLT

is the number of multiple block allocations.

FREE

is the number of blocks marked
have been allocated.

free

BAD

is the number of bad
file header.

pointers

retrieval

that

should
in

the

NOTE
If the output for VFY is directed to a
terminal device, and the user does not
wish to see all the error messages for a
given file entering CTRL/O terminates
the listing of
all
further
error
messages for that particular file, i.e.,
all messages but the summary line.

8.4.l.2 Files Marked-for-Delete - If a
file
has
been
markedfor-delete but the deletion process was not completed, the user has
two options:
the file can be restored, if still required, and its
consistency checked, or the deletion process can be completed to
recover the lost space. These operations are described below.
•

Restoring a File
To restore a file marked-for-delete, the disk volume must be
mounted using the MCR MOUNT command with the /UNL switch
specified. For example:
2.MOU DKO:/UNL_}
Then, run VFY specifying the /DE switch to reset
marked-for-delete indicators in file headers.
Once
delete indicator has been reset, run VFY specifying the
switch to scan the entire file structure.
NOTE
The deletion process may have proceeded
partially and a portion at the end of
the file may be missing. This condition
can be detected by a directory listing
obtained using the PIP /FU switch
(see
Section 2.4.8).

8-7

the
the
/LO

FILE STRUCTURE VERIFICATION UTILITY (VFY)
•

Deleting a File
Files that are marked-for-delete can be deleted directly
with PIP, once their unique File ID has been obtained via a
validity check. The File ID appears as the first entry in
the file identification line which precedes each list of
file errors (see Section 8.4.1.1).
The following example
illustrates how the File ID is used with PIP to delete a
file:
Example:
.2.PIP /FI:l2:20/DE_J
In this example, the file with File ID 12,20 is deleted from
the system device. PIP issues the following error message
j;PIP -- FAILED TO MARK FILE FOR DELETE-NO SUCH FILE"
since the file system denies the existence of files already
marked-for-delete; however, the file is completely deleted.

Once files have been restored or deleted, run VFY with the /RE switch
specified to assure the consistency of the volume's storage allocation
map.

8.4.1.3 Deletion Of Multiply Allocated Blocks - If
the
file
structure contains
multiply
allocated blocks, it is necessary to
delete files until there are no more such blocks. An automatic rescan
of the volume identifies which files share which blocks. This rescan
lists the first as well as subsequent files containing the multiply
allocated blocks.
Once the user has this information, he must then
determine which, if any, of the files can be saved and delete the
rest, using the Delete function provided by the PIP utility.
NOTE
Extreme caution should be taken
in
deleting
multiply
allocated files.
After the files have been deleted, VFY
should be run once again to ensure that
all of the
multiply
allocated files
have been deleted.

8.4.1.4 Elimination Of Free Blocks - Once there are
no
multiply
allocated blocks, the next concern is the elimination of blocks that
are marked FREE in the storage allocation map, but which are actually
allocated to a file. To cause these blocks to be reallocated in the
storage allocation map, the user must rerun the validity check specify
the /UP switch. This allocates all blocks that should have
been marked as allocated. See Section 8.4.3 for a description of the
/UP switch.

8-8

FILE STRUCTURE VERIFICATION UTILITY (VFY)
NOTE
Once there are no multiply allocated
blocks and no blocks marked free that
are actually in use, the file structure
is
safe for writing new files and
extending existing files.
However, if
there were such errors, there may be
files which have
had
data
blocks
overwritten as the result of multiple
allocation.

8.4.1.5 Recovering Lost Blocks - The user can determine whether any
blocks have been lost on a file-structured volume by exam1n1ng the
last two lines of output from the validity check. The last two lines
of output give the free space on the volume. The first line of the
two tells how much room is available according to the index file
(i.e., the number of blocks that are not in use by any file in the
index file). The last line specifies how much room is available
according to the storage allocation map. Assuming there are no other
errors, these two figures should agree. If the index file indicates
that more blocks are free than the storage allocation map, then those
blocks are "lost" in the sense that they appear to be allocated, but
no file contains ~nem. Lost blocks may be recovered by rerunning the
validity check specifying the /RE switch. See Section 8.4.4 for a
description of the /RE switch.

8.4.2

DELETE Switch {/DE)

FUNCTION
The DELETE switch allows the user to reset the marked-for-delete
indicators in the file header area of those files which are marked for
deletion, but which were never actually deleted.
FORMAT
listfile,scratchdev=indev/DE
or
indev/DE

8-9

FILE STRUCTURE VERIFICATION UTILITY (VFY)
NOTES

8.4.3

The volume must be mounted with
/UNL switch.

VFY must be running under
UIC.

the

system

UPDATE Switch (/UP)

FUNCTION
The UPDATE switch allows the user to al~ocate all blocks
to be available but are actually allocated to a file.
FORMAT
listfile,scratchdev=indev/UP
or
indev/UP
NOTES
1.

multiply
Files with
allocated
blocks must be deleted from the file
structure before the update can be
run.

The volume being
write-enabled.

VFY must be running under
UIC.

The scratch file should
be
on
another
volume.
If
this
is
impossible, the volume
must
be
dismounted
immediately after VFY
terminates.
(Failure to do this may
result in partial updating of the
storage allocation map.) Then the
volume should be mounted again, and
the scratch file must be deleted
manually.
VFY issues a detailed
message in this case specifying the
name of the scratch file to be
deleted.

updated

must
a

system

The message is:
VFY

TO COMPLETE THE STORAGE MAP
UPDATE DISMOUNT THE VOLUME
IMMEDIATELY. THEN MOUNT IT
AND
DELETE
THE FOLLOWING
FILE:
[g,m] filespec

8-10

that

appear

FILE STRUCTURE VERIFICATION UTILITY (VFY)
where:

8.4.4

[g ,m]

is the UIC.

file spec

is the name of
the file to be
deleted.

REBUILD Switch (/RE)

FUNCTION
The REBUILD switch allows the user to recover blocks that are lost in
the sense that they appear to be allocated, but no file contains them.
FORMAT
listfile,scratchdev=indev/RE
or
indev/RE

NOTES
1.

Multiply
allocated blocks must be
removed
{deleted) from the file
structure before the rebuild can be

The volume being
write-enabled.

VFY must be running under
UIC.

The scratch file should
be
on
another
volume.
If
this
is
impossible, the volume
must
be
dismounted
immediately after VFY
terminates.
{Failure to do this may
result in partial updating of the
storage allocation map.) Then the
volume should be mounted again, and
the scratch file must be deleted
manually.
VFY issues a detailed
message in this case, specifying the
name of the scratch file to be
deleted.

8-11

updated

must
a

system

FILE STRUCTURE VERIFICATION UTILITY (VFY)
FREE Switch (/FR)

8.4.5

FUNCTION
The FREE switch provides the user with the ability to
available space on a specified volume.

out

the

FORMAT
listfile=indev/FR
or
indev/FR
The output from the /FR command is shown below:
dev: HAS nnnn.

BLOCKS FREE, nnnn.

BLOCKS USED OUT OF nnnn.

LOST Switch (/LO)

8.4.6

FUNCTION
The LOST switch provides the facility to scan the entire file
structure looking for files which are not in any directory and, thus,
are lost in the sense that they cannot be referenced by filename.
A
list of the files is produced, and if the "lost file directory" [1,3)
exists on that volume, all the files will be entered in that
directory.
FORMAT
listfile,scratchdev=indev/LO
or
indev/LO

LIST Switch (/LI)

8.4.7

FUNCTION
The LIST switch provides the facility to list the entire index file by
file identification.
The output for each file specifies the file
number, file sequence number, filename, and owner.
A typical index
file listing is illustrated in Figure 8-1.
FORMAT
listfile,scratchdev=indev/LI
or
indev/LI

8-12

FILE STRUCTURE VERIFICATION UTILITY (VFY)
VFY>DK:/LI.)
LISTING OF INDEX ON DKO:
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE
FILE

ID
ID
ID
ID
ID
ID
ID
ID
ID
ID
ID
ID

000001,000001
000002,000002
000003,000003
000004,000004
000005,000005
000006,000006
000007,000007
000010,000010
000011, 000011
000012,000012
000013,000036
000014,000037

INDEXF.SYS;l
OWNER [ 1'1]
,,
BITMAP.SYS;l
OWNER Lr .1., ' .1. J
BADBLK.SYS;l
OWNER [ 1' 1]
000000.DIR;l
OWNER [ 1' 1]
CORIMG.SYS;l
OWNER [l, 1]
001001.DIR;l
OWNER [ 1' 1]
001002.DIR;l
OWNER [ 1, 2]
EXEMC.MLB;l
OWNER [ 1' 1]
RSXMAC.SML;l
OWNER [ 1'1]
NODES.TBL;l
OWNER [ 1'1]
QIOSYM .MSG; 311
OWNER [ 1' 2]
F4PCOM.MSG;l
OWNER [1,2]

Figure 8-1
VFY Listing Sample Using the /LI Switch

8.4.8

READ CHECK Switch (/RC)

FUNCTION
The READ CHECK switch provides the facility to check that every
of every file on a specified volume can be read.

block

FORMAT
listfile=indev/RC[:n]

indev/RC [ :n]
NOTE
Since the READ CHECK is a read-only operation, the volume
can be write-protected.
The optional parameter [:n] is the blocking factor which indicates the
number of file blocks to be read at a time.
The default value is the
maximum number of blocks in dynamic memory available to VFY.
The dynamic memory available may be increased by installing VFY in a
larger partition.
Five blocks are available when VFY is installed in
an BK partition, and four blocks are added for each lK increment.
For the fastest possible read check, the maximum block factor
should
be used.
Whenever
an error
is encountered, each block of the
portion-in-error
is reread
individually to determine which data
block(s) cannot be read.
When an error is detected, a file identification line is listed in the
following format:

8-13

FILE STRUCTURE VERIFICATION UTILITY (VFY)
FILE ID nn,nn filename.typ;ver.

blocks used/blocks allocated

Following this line, an error message is listed. If a blocking factor
other than 1 is in use, an error message in the following form will be
issued:
ERROR STARTING AT VBN nl,n2 LBN nl,n2 - ERROR CODE -err
Following the first error message, there should be one or more error
messages indicating the exact block(s) in error. The second error
message line(s) will be in the following form:
ERROR AT VBN nl,n2 LBN nl,n2 - ERROR CODE -err
If an "ERROR STARTING AT" line is displayed without one or more "ERROR
AT" lines, a multiblock read operation on the selected device has
failed, but the data blocks appear to be individually readable.
NOTES

8.5

If the VBN of the unreadable block
listed in the "ERROR AT" line is
beyond the block-used-count,
the
data portion of the file is all
right.

The negative number printed after
the ERROR CODE message is -4 to
indicate a device parity
error.
Other error codes are contained in
Appendix I of
the
RSX-11
I/O
Operations Reference Manual.

VFY ERROR MESSAGES

VFY -- COMMAND SYNTAX ERROR
Description
The command entered does not conform to command syntax rules.
Suggested User Action
Reenter the command line with the correct syntax specified.
VFY -- FAILED TO ALLOCATE SPACE FOR TEMP FILE
Description
The volume specified for the temporary scratch file is full.
Suggested User Action
Use PIP to delete all unnecessary files and rerun VFY.

8-14

FILE STRUCTURE VERIFICATION UTILITY {VFY)
VFY -- FAILED TO ATTACH DEVICE
or
VFY -- FAILED TO DETACH DEVICE
or
VFY

ILLEGAL DEVICE
Description
The file specifier entered contains an illegal device.
Suggested User Action
Reenter the command line with the correct device specified.

VFY -- ILLEGAL SWITCH
Description
The switch specified is not a valid VFY switch or a valid
is used illegally.
Suggested User Action
Reenter the command line with the correct switch specified.
VFY -- I/O ERROR ON INPUT FILE
or
VFY

I/O ERROR ON OUTPUT FILE
Description
One of the following conditions may exist:
1.

The device is not on-line.

The device is not mounted.

The hardware has failed.

Suggested User Action
1.

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

8-15

switch

FILE STRUCTURE VERIFICATION UTILITY (VFY)
VFY -- NO DYNAMIC MEMORY AVAILABLE - PARTITION TOO SMALL
Description
VFY does not have enough buffer space to run.
Suggested User Action
Run VFY in a larger partition (8K minimum).
VFY -- OPEN FAILURE ON BIT MAP
or
VFY -- OPEN FAILURE ON INDEX FILE
or
VFY -- OPEN FAILURE ON LISTING FILE
or
VFY

OPEN FAILURE ON TEMPORARY FILE
Description
One of the following conditions may exist:
1.

VFY is not running under a system UIC, but should be.

The named file does not exist in specified directory.

The volume is not mounted.

The specified file directory does not exist.

Suggested User Action

8.6

Determine which of the above conditions exists.

Rectify the condition.

Reenter the command line.

VFY ERROR CODES

If VFY cannot access the message file,
following format:

errors

are

reported

the

VFY -- ERROR CODE nn.
where:
nn.
Refer to
actions.

Section

is one of the error codes contained in Table 8-3.
8.5

for

error

descriptions

8-16

and

suggested

user

FILE STRUCTURE VERIFICATION UTILITY (VFY)
Table 8-3
VFY Error Codes
ERROR
CODES
1.

2.
3.
4.
5.

6.
7.
8.
9.
in

Ll
•.

VFY ERROR MESSAGE IS:
ILLEGAL DEVICE
OPEN FAILURE ON BIT MAP
OPEN FAILURE ON TEMPORARY FILE
FAILED TO ALLOCATE SPACE FOR TEMP FILE
FAILED TO DETACH DEVICE
FAILED TO ATTACH DEVICE
COMMAND SYNTAX ERROR
I/0 ERROR ON INPUT FILE
I/0 ERROR ON OUTPUT FILE
ILLEGAL SWITCH
OPEN FAILURE ON LISTING FILE

NO DYNAMIC MEMORY AVAILABLE - PARTITION TOO SMALL
-~~..__O_P_E_N~F-A_I_L_U_R_E~O-N~I-N_D_E_X~F-I_L_E~~~~~~~~~~~~~

8-17

APPENDIX A
COMMANDS AND SWITCHES

A.l

INTRODUCTION

This appendix presents a summary of the commands and/or switches used
by the RSX-llM utilities described in this manual. Each of the
numbered sections of this appendix corresponds, in number, to the
chapter discussing that utility. For example, Chapter 2 and Section
A.2 both deal with PIP.
Commands and switches are presented alphabetically within the sections
of this appendix, regardless of their presentation in the various
chapters.

A.2

PIP COMMAND SUMMARY
APPEND
outfile[/FO]=infile-1
[,infile-2, ... ,infile-n]/AP[/FO]
where /FO is File Owner
COPY AND MERGE
outfile[/switch]=infile-1
f ,infile-2, ... ,infile-n]
[/switch]
/swi tch=BL: n [.] Block allocated.
co
Contiguous output.
-co
Non-contiguous
output.
FO
File Owner.
NV
New Version.
Supersede.
SU
DEFAULT
dev: [group,member]/DF

Opens an existing file

(outfile} and appends
the
input
file(s}
onto the end of it.
Creates a copy of a
file on the same or
another
device.

See Table 2-3 for a
complete
description
switches.
of
these
Changes
the
default
device and/or UIC.

DELETE
infile-l[,infile-2, ... ,infile-n]/DE

A-1

Deletes files.

COMMANDS AND SWITCHES
ENTER
outf ile= inf ile-1
[,infile-2, ... ,infile-n]/EN[/NV]
where /NV is New Version.

FREE
dev:/FR

Enters
a
synonym for
file
in a
directory
with an option to force
the
version number of
outf ile" to one greater
than the latest version
for the file.
Prints out the available
space on a volume.

IDENTIFY
/ID

Causes the version of PIP
currently
in use to be
displayed
on
the
terminal.

LIST
[listfile]=infile-1[, ... ,infile-n]/LI
where [listfile] defaults to
Lists
one
or
more
TI: if not specified.
directories
with
an
option
to
specify
Alternate Mode Switches
d ir ec tor y
listing
/BR
Brief format.
formats.
For a complete descrip/FU[:n] Full format.
tion of these switches,
/TB
Total blocks format.
see Table 2-4.
PROTECT
infile-1/PR[/SY[:RWED] [/OW[:RWED]]
[/GR[:RWED]] [/WO[:RWED]] [/FO]
where SY is system access rights.
OW is owner access rights.
GR is group access rights.
WO is world access rights.

Alters file protection.
See Section 2.4.9 for
a complete description of
these switches.

RWED is read, write, extend,
delete privilege.
FO is File Owner subswitch.
PURGE
-----ynfile-l[,infile-2, ... ,infile-n]/PU[:n]
Deletes a specified range
of obsolete versions of a
file.
REMOVE
infile-l[,infile-2, ... ,infile-n]/RM

A-2

Removes an entry
directory file.

from

COMMANDS AND SWITCHES
RENAME
outfile=infile-1
[,infile-2, ... ,infile-n]/RE
[/NV]

where NV is New Version=

SPOOL
---rnfile-l[,infile-2, ... ,infile-n]
/SP
UNLOCK
infile-l[,infile-2, ... ,infile-n]
/UN
UPDATE
outfile= infile-1
[,infile-2, ... ,infile-n]/UP[/FO]
where FO is File Owner.

A.3

Changes the name of a
file
with
an
option
to
force
the version
number of "outfile" to
one
greater
than the
latest version for the
file.
Specifies a list of
files to be printed.
Unlocks a
file
which
was locked as a result of
being improperly closed.
Opens
an
existing
file(s)
(infile)
and
writes
it,
from
the
beginning, onto outfile.

FLX COMMAND SUMMARY

The FLX commands have the following format:
outfile=infile-l[,infile-2, ... ,infile-n]
/switch

where switch

Performs file conversion between DOS-11,
RT-11
and
Files-11
formats.

BL:n

Indicates th~ number
of contiguous blocks
to be allocated to the
output file.

BS:n

Specifies the
block
size for cassette tape
output.

Indicates
that
the
output file is to be
contiguous.

Deletes files
DOS-11
or
volume.

Causes
a
directory
listing of DOS or RT
volumes;
or DOS or
RSX
cassette
tape
volumes to be listed.

A-3

from a
RT-11

COMMANDS AND SWITCHES
DO

Identifies the file as
a
DOS-11
formatted
file.

FA:n

Formatted ASCII.

FB:n

Formatted binary.

Indicates that FORTRAN
carriage
control
conventions are to be
used.

Requests the current
version number of FLX.

IM:n

Image mode.

Same as DI.

NU:n

Used with /ZE and /RT
switches
to specify
the
number
of
directory
blocks to
allocate.

Indicates that file is
a Files-11 formatted
file.

Indicates that file is
an
RT-11
formatted
file.

Indicates
that
the
converted file is to
be spooled via
the
print spooler.

Indicates
that
the
output file is to have
the same UIC as the
input file.

Verify
after
write
(for cassette only).

Initializes DOS and RT
volumes and cassettes
for DOS or RSX files.

See Tables 3-2 and 3-3 for a complete description of these switches.

A-4

COMMANDS AND SWITCHES
A.4

DMP COMMAND SUMMARY

The DMP utility has one command.
file

onto

Data should be
in ASCII mode.

dumped

BA:n:m

Specifies a base block
address.

BL:n:m

Specifies the
first
and
last
logical
blocks to be dumped.

Data should be dumped
in byte octal format.

Includes
the
in the
header
dumped.

Causes
the
current
version of DMP to be
on
the
printed
listing.

Causes
starting
(logical) block number
and a contiguous or
hon-contiguous indication for the file to
be printed.

MD [: n]

Controls line number
sequencing
during a
memory image dump.

Dumps a
outfile.

outfile=infile/switch
where switch

See Table

A.5

4~1

file
data

for a complete description of these switches.

EDI COMMAND SUMMARY
ADD
-A[DD]

(string)

Add the text specified
by "string" to the end
of the current line.

ADD AND PRINT
AP (string)

Same as ADD, except
the new current line
is printed.

A-5

COMMANDS AND SWITCHES
BEGIN
B[EGIN]

Sets the current line
pointer to the top of
the block buffer or
input file.

BLOCK ON or OFF
BL[OCK] [ON] or [OFF]

Switch
modes.

BOTTOM
BO[TTOM]

text

access

Sets the current line
pointer to the bottom
of block buffer
or
input file.

CHANGE
[n]C[HANGE] /string-1/string-2

CLOSE
CL[OSE] filespec

Search for string-1 in
the current line and
replace it with the
text
specified
in
string-2. The integer
n allows the user to
repeat the
command,
thus allowing string-2
to be substituted for
string-1 n times.
Transfer the remaining
lines
in the block
buffer and the input
file into the output
file, then close both
the input file and the
output file.

CLOSES
CLOSES

Close secondary input
file
and
begin
selecting lines from
the input file.

CLOSE AND DELETE
CDL f ilespec

Same as
the
CLOSE
command, except that
the input
file
is
deleted.

A-6

COMMANDS AND SWITCHES
CONCATENATION CHARACTER
CC character

Change command concatenation character to
the
specified
character
(default is
&) •

CTRL/Z

DELETE
D[ELETE]

Same as EXIT if in
Edit mode; otherwise,
it causes an immediate
exit of EDI.
Delete the current and
next n-1 lines, if n
is positive; delete n
lines
preceding the
current line, but not
the current line, if n
is negative.

[n] or [-n]

DELETE AND PRINT
DP [n] or [-n]

Same as DELETE, except
that the new current
line is printed out.

END
E[ND]

Same as
command.

ERASE
ERASE [n]

the

BOTTOM

Erase the entire block
buffer,
the current
line, and the next n
blocks.

EXIT
EX[IT]

Same as CLOSE command,
except
that,
when
files are closed, EDI
exits.

EXIT AND DELETE
ED [X] file spec

Exit from the editing
session,
close
the
output file,
delete
the input file.

FORM FEED
FF

Insert form feed
block buffer.

A-7

into

COMMANDS AND SWITCHES
FILE

~~FI[LE]

filespec

Transfer lines
from
the input file to the
file
specified
by
filespec.

FIND
[n]F[IND]

(string)

Find the line starting
with "string" or, if n
is specified, the nth
line
starting
with
string".

INSERT
I[NSERT]

(string)

Insert "string" immediately following the
current
line.
If
string" is null, EDI
enters Input mode.

KILL
KILL

Terminate this editing
session;
close input
and
output
files;
delete
the
output
file.

LINE CHANGE
[n]LC /string-1/string-2

Same as CHANGE, except
that all occurrences
of string-1 in
the
current
line
are
changed to string-2.

LIST ON TERMINAL
LI[ST]

Print o~ user terminal
all
lines in block
buffer
or
all
rema1n1ng
lines
in
input file, starting
with current line.

LIST ON PSEUDO-DEVICE
LP

List the text in the
block buffer or input
file
on
the
pseudo-device
CL:,
starting
with
the
current line.

LOCATE
[n] L [OCATE] string

Search
the
block
buffer
for "string"
or, if n is specified,
the nth occurrence of
string".

A-8

COMMANDS AND SWITCHES
MACRO
---r.iA[CRO] x definition

Define macro x
definition".

MACRO CALL
MC[ALL]

Retrieve macros from
the latest version of
file MCALL;n.

MACRO EXECUTE
[n] Mx [a]

Execute macro x for n
executions, passing it
the numeric argument
a.

MACRO IMMEDIATE
[n]<definition>

Allows the user
to
define and execute a
macro n times in one
step.

NEXT
N [ EXT ]

[ n] or [ - n]

Establish
a
new
current line + or - n
lines from the current
line.

Same as Next command,
but the new current
line is printed.

NEXT PRINT
NP

[n]

[ -n]

OLD PAGE
OL[DPAGE] n

Back up to page n.

OPENS
OP [ENS 1 f ilespec

Open secondary
file.

OUTPUT ON or OFF
OU [TPUT] [ON] or [OFF]
OVERLAY
0 [VERLAY]

PAGE
PAG[E]

input

Turn output on or off.
Delete
the
current
line and the next n-1
lines, and enter Input
mode.

[n]

Enter block mode, if
not already in block
mode, and read page n
into the block buffer.

A-9

COMMANDS AND SWITCHES
PAGE FIND
[n]PF[IND]

{string)

PAGE LOCATE
[n]PL[OCATE]

Identical
to
FIND
command, except that
it searches successive
pages until the nth
occurrence of i•string"
is found.

{string)

Same
as
LOCATE
command, except that
successive pages are
searched for the value
specified by "string".

PASTE
PA[STE] /string-1/string-2

Same
as
the
LINE
CHANGE command, except
that all lines in the
remainder of the input
file or block buffer
are
searched
for
str ing-1.
Wherever
found,
string-1
is
replaced
with
string-2.

PRINT
P [RINT]

[n]

Print the
and
the
lines,
terminal.

READ
REA [D]

[ n]

Read the next n pages
into the block buffer.

RENEW
REN [EW]

[n]

Write
the
current
buffer and read in the
next.
If
n
is
specified, repeat n-1
times.

RETYPE
R [ETYPE]

(string)

Replace the
line with the
string". If
is null, the
deleted.

SAVE
SA [VE]

[n]

[ filespec]

next line,
next
n-1
on
the

current
text of
string"
line is

Save the current line,
and
the
next
n-1
lines, in the
file
specified by filespec.

A-10

COMMANDS AND SWITCHES
SEARCH & CHANGE
SC /string-1/string-2

Search for string-1,
in the block buffer or
input file
starting
~~~h

YY.L'-ll

~h~

\...!..l.'C

,~~~

..LJ..J..L'C

~~11~~-

.LV•..L.VYY

ing the current line.
When
string-I
is
found,
replace
all
occurrences
in line
with string-2.
SELECT PRIMARY
SP

Select
file.

SELECT SECONDARY
SS

primary

input

Select secondary input
file.

SIZE
SIZE n

Specify maximum number
of lines to be read
into the block buffer
on a single READ.

TAB ON or OFF
TA [B] [ON] or [OFF]

Turn automatic tabbing
on or off.

TOP
-T[OP]

Same as BEGIN command.

TOP OF FILE

TOF

TYPE
--TY [PE]

Return to the top of
the
input file,
in
block mode, and save
all pages previously
edited.
[n]

UNSAVE
UN s [A VE ]

Same as PRINT command,
except
that
the
current line pointer
does not change.

[ files pe c ]

Retrieve
the
lines
which were previously
saved on f ilespec and
insert
them
immediately following
the current line.

UPPER CASE ON or OFF
UC [ON] or [OFF]

Turn
upper
case
conversion on or off.

A-11

COMMANDS AND SWITCHES
VERIFY ON or OFF
V[ERIFY] [ON] or [OFF]

Allows user to
whether
or
locative and
commands
are
verified.

WRITE
W[RITE]

A.6

select
not
change
to be

Write
the
current
block to the output
file, and erase the
contents
of
the
buffer.

SLP COMMAND SUMMARY

The SLP utility has only one command.
outfile[,listfile/SP or/-SP]=infile
[/switch]

Perform
batchor iented editing
to
create
and maintain
source language files
on disk.

where switch

AU and -AU

Enable and disable the
editing audit trail,
which indicates
the
changes
made during
the
most
recent
editing session.

BF and -BF

Enable
and
disable
blank
fill when an
audit trail is being
produced.

DB and -DB

Enable
and
disable
double-spaced listing.

and where SP and -SP

Enable and disable the
spooling
of listing
files
to
a
file
structured volume.

See Table 6-2 for a complete description of these switches
6-3 for a description of the SLP edit control characters.

A-12

and

Table

COMMANDS AND SWITCHES
A.7

LBR COMMAND SUMMARY
COMPRESS
outfile/CO:size:ept:mnt:=infile

CREATE
outfile/CR:size:ept:mnt:type

DELETE
outfile/DE:module-1
[:module-2: ... :module-n]

DEFAULT
outfile/DF:type •..
or
/DF:type

Creates a new library
file
and
transfers
contents,
but
physically
deletes
logically
deleted
records in the file
and puts
all
free
space at the end of
the file.
Allocates a contiguous
library
file
on a
direct access device.
Deletes
library
modules
and
their
associated
entry
points from a file.
Specifies
default
library
file
type.

DELETE GLOBAL
outfile/DG:global-1
[:global-2: ... :global-n]

Deletes
specified
library module entry
points from a file.

INSERT
outfile[/IN]=infile-1
[,infile-2, .•. ,infile-n]

Inserts
library
modules into a library
file.

LIST

~~outfile[,listfile]/switch(es)

where

/switch(es)=

Lists all modules
the library file.

Lists all modules in
the library file and
all
their
entry
points.

Lists all modules in
the library file and
provides a full module
description including
size,
date
of
insertion,
and
version.

A-13

COMMANDS AND SWITCHES
REPLACE
outfile/RP=infile-1
[,infile-2, •.. ,infile-n]
or

Inserts, and in certain cases, replaces
library modules in a
library file.

outfile=infile-1[/RP]
[, infile-2 [/RP], ... , infile-n [/RP]]
SPOOL
outfile,listfile/SP

The listing file is
spooled
out
for
pr in ting.

SELECTIVE SEARCH
outfile=infile-1/SS
[, infile-2 [/SS], ... ,
infile-n[/SS]]

Sets selective search
attribute
bit
in
object module header.

SQUEEZE
outf ile/SZ=inf ile-1
[, infile-2, .•. , infile-n]

Reduces
size
macro sources.

or
outfile=infile-1/SZ
[,inf ile-2 [/SZ] , ..• ,
infile-n[/SZ]]

A.8

VFY COMMAND SUMMARY
DELETE
listfile, scratchdev=indev/DE
or indev/DE

Resets the marked-fordelete indicators in
the file header area
of those files marked
for
deletion,
but
which
were
never
actually deleted.

FREE

~~listfile=indev/FR

Prints out the available
space
on
a
volume.

or indev/FR
LIST

~~listfile, scratchdev=indev/LI

or indev/LI

A-14

Lists the entire index
file
by
file
identification.

COMMANDS AND SWITCHES
LOST

~~listfile, scratchdev=indev/LO

or indev/LO

READ CHECK
listfile=indev/RC[:n]

Scans the entire file
structure looking for
files that are not in
any directory.
Checks
that
every
block of every file on
specified volume can
be read.

or indev/RC[:n]
REBUILD
listfile, scratchdev=indev/RE
or indev/RE

UPDATE
listfile,scratchdev=indev/UP
or indev/UP

A-15

Recovers blocks that
appear
to
be
allocated, but which
are no~ contained in
any file.
Allocates blocks that
appear
to
be
available, but which
are actually allocated
to a file.

APPENDIX B
LBR, EDI AND DMP EXAMPLES
B.l

SAMPLE LISTINGS FOR LBR LIST SWITCHES (OBJECT LIBRARY}

B.1.1

List Module Names
LBR>MAC,LP:_/

or
LBR> MAC , LP : /LI _}
nF FILE MAC.OLR;\
MODULF LlRRARV ~~FATED ~VI LB~ V~~2VM
LAST INSERT occu~~FO 22•SEP-74 AT t1:~t1S~
MNT F.NT~I~S ALLOCATEn: 6d; AVAILAHLt: 20
FPT ENTRIES bLLUCATtOI ~4~: AVAILABLE: 92
FILE SPACE AVAJLASLE: ~~~15 ~OROS
OI~~CTO~Y

08J~CT

AS(;MT
ASSE~

CNrHL

cnDHD
r)ATDR

E1'1RuS
ENl')LN

ENDPS
DP~S

FLOAT

GETLN
GMA~G

I NI=' I l

JNTFL
INOFL

LA REL
LIS TC
LSTNi;
t.tAC~n

MAC~S

MCALL
MLI~~

MSCOR
~D~CT
P~C1CSI
P~nl'C

?ROSIN

PST
i::fEAD

REPT
~OLH{"I

~SOAT
RSE~~.C

B-1

~5111\!P

SECT~
SETIJT~

SETIHJ

SF.Tl MM
~ETMX

SPACE
STMhJT

SVMRL

woRDR
ltl~ I TE

B.1.2

List Module Names and Full Module Information
LB!•_> MAC , LP : /FU~
or
LBR>MAC, LP: /LI/FU ~
~I~ErTOMV nF FILE MAC.OL~;t
OBJECT ~ODULE LIR~A~V CMEAf~n ~v: LB~ VX~2VM
LAST INSERT occu~~EO 22-StP-74 AT 11:5115~
MNT ENTRIE~ ALLOCATED: 64; AVAILARLE: 2~
~PT ENTRTE~ ALLOCATEn: b4~: AVAILABLE: a~
FIL~ SPACt AVATLABL~: ~~01~ WO~DS

ASr.t-H

SIZEtl11n64

ASSE~

SllEs~~7ct9

CNIHL

CODl-1D

SIZF. :0~727
S I l E : '~ ~ 9 2 ...~

DAT DR

5IZUVlfl414

r NSE:.~ rm

EN~DS

SIZEH'IC,,248

tNSERTfD

Ef'.inL~

!;IH.:v~812

JNSE~TFD

ENl')PS

SIZEHl\V16~1

TNSE~TE'D

FXP~S

SIZE.rnt~11

TN~F..~Hr'>

F'LOAT
C:ETLM

SIZE aH'IJ3b

l~JSERlfD

TNSE..IHED
TN5Er;(TF.O
t ~1 SE.RTF. D
Tf'l~EqTEO

17-JUL-74 IDFNT:~2
1•AllG•74 IDE.NTcV'5~1
3\•JUL-74 JDENTsCi'4
17•JUL•74 IDENTa~n
17•JUL•74 IDF.NT107
1•ALIG•74 IDENT1~6
Jt•JUL•74 I OE"NT: VI~
17-JUL-74 IOE"ITH.,4
31-JUL-74 IDENT:~t:i
17-JUL-74 IDENT:02
17-JUL-74 !L>ENT10b
17-JUL-74 TDENT;Ci'1
9·Sf P•74
11"'lf::.NT112
31·JUL•74 IDFNTl~1

T~JFL

$IZE ~li.H>7~
SI 2E Vl~29~
SIZE V1"'Y4 l
SIZE ~0493

INSERTED

TNOFL
LABEL

~IZE

0096~

I~SE~TfD:Y•SFP-74

IOENT:~t

SIZE

004~~

IN~ERTED

IDENT:~ai

LIS TC

SIZE

~0284

JNSERTECJ 17-JUL-74

IDENT:04

LST\JG

~~566

INSERHD 17•JUL•7d
lN5ERTED 11 ... JuL-74

IDENT1V117

~,\CRO

SIH
SIH

MAC.($

SIZE vl1 :>4~

GMA~G

J NF IL

MC ALL

~<~19

1•AlJG•74

JDENTH~t.3

~02!=i8

S Il E Vl1307

INSE~TED!17-JUL•74

I DENT 04

St ZE
SIZE

JD ENT

~IZE

vl~264

SIZE

0~~~7

MSCD~

SIZE

~~84j

Vl~2~b

NDRCT

SIZE

PROCSJ

~ 17 I:

~0216

PR("IPC

SIZE
SIZE.

Vl~8t'i~

PST
REAO

TNSE.~H'D

9•SEP•74
IN5l:~HD 31·JUL•74
TNSE~TED 31•JUL•74
TNSEl=lHO 3t•JUL•74
INSEl(TED 31·JUL•74
JNSt~Trn 17·JUL•74
INSERT Eu 17•JUL•74
PJSE.RTF.:Dr 17-JUL-74

MLJij~

PRns.-i

INSE.~TFD

INSE.QTED

INSERTED

!DENTS~9

I DE >-Jl V\ 1

J[JENT VI ':l
TDrnT ei 8
JOE NT ~2
TD ENT el 1
IlJF.NT Vl2

I DENT

ROLHD
RSDAT

SIZEt~i'15Ro

JNSERTEDt17•JUL•74
JNSEQTEnr31-JUL•74
TNSERF[)11•AllG•74

SIZE:~~J74

TNSE~TF0:17•JUL·7~

IOENT:V'o

~SF~EC

SIZE.:{,~974

!"iSEQTED: 1-Aur~-74

I~ENT:17M

~5UNP

!;jIZEHq117

JNS~RTF0:17•JUL•74

IDF.NT101

REPT

~ill l 98
l~ ~ 4 7

B-2

IDFNT "'1
IDENT:~5

B.1.3

IDE.NT:;u

StCT~

SlZEH~0551

I~~ERTE011•AUG•74

SETOii1

SI:ZErn~1~b

JNSf~TED:17-JUL•74

IDENTH'l2

SETON

~IZE:~0b7~

Jt.JUL-74
iN5E~iED i7-JUL·74
I NSE~TE"D 17-JUL-74
INSE~Trn 22·5EP•74
p.ISERTED 17-JUL-74
INSERTED 17-JUL·ld
lN~f.~TEO 17•JUL-74
TNSE.~TED 17-JUL•74

TDENT:~6

SEil-.;i"i

SilF..#i1~29~

~ETMX

SIZE:;?J0131

SPACE

SI7.EIV'~4.d9

STM"IT

SJZE:t-H"31~

SYMrjL
WQRDB

StlEtvi~732

WRITE

S 1 ZE"HHH R9

SIZErn~1.41

TNSE~TED

IDE~i:02

IDENT:01
JD ENT H'!4
ICJENTt~3

JD ENT: ~4
IDF.~T:~2
IDE~T:~1

List Module Names, Full Module Information and Module Entry
Points
(Global Symbols)
LBR>MAC,LP:/FU/LE_..)
or
LBR>MAC ,LP :/LI/FU/LE _J
DI~ECT~RY OF FILE MAC.OLR;t
n8JECT ~~OULE LIBRARY CREATEn 81: LgR VX~2VM
LAST !~SERT ocru~RF.D 2~·SEP-74 AT 11:~1:5~
MNT ~NTRtE~ ALLOCATED: 64; AVAtLAHLE: 2~

EPT ENT~IES ALLOCATED: 64~J AVAILABLEt Q2
FILE SPACE. AVAILA8LEr ~~~15 WORDS

•• MODIJLE:ASGMT
AS GMT

IOENT:~2

ASGMH

AS5EM

~ODULE:C:NDTL

CND8AS

CNOTOP

** MODULEICODHO
CPtSTL
PCROLL
u

INSERTED:17•JUL•74

MODULE I ASSEM

ALLOC$
u

SIZE1~02~4

INSIZE
?CRT~L

MODULE:DATDR

ALKB

CL~All

~IZf :~0727

IFF

SI7-E:~~923

ObJDMP
RLDOMP

FNA~L

B-3

MACP1

tFT

JNSERTED:17•JUL•74

ORJINI
RLDPNT

:;Jl[![ll0414

IDE~T

EDTTOP

LC~ITS

TNSERTED:J1•JUL•74

FNDC

•• HODULESENBL.,S
EDTBAS

EORITS

ORJL~C
srcon~

ORJPNT
TST~LD

tNSERTEDr17-.JUL•74

XCTPA3

'XCTPRG

IDENT:~4

IFTF
IDENT:~o

ORJSFC
ZAPCPX
IDE~T:~J

PC~CNT

•• HQDlJLEIENDLN
ENDLl N

...

MODULEIENDPS
ENl)P1

••

AA SER~

EkRCNl

INSERTED1J1•JUL•74

LI N~UF

LINE ND

IDENT:"'6

LSTFHIF

~IZEr~1~6~

INSERTED:17•JUL•74

IDENTIM

SllEr~1211

lNSERTED131•JUL•74

I l)E:NT: ~6

ENDP2

MODULEtEXP~S

~ELTRM

••

ERRAT.S

Silt.1iHl812

ABSFXP
RELTST

ABSTRM

ABSTST

EAPR

GLA~XP

GUH RM

MODUL~IFLOAT

SIZE:0~~3~

!NSERTED:17•JUL•74

IDENT1n

•• MODULE I GETLN

SIZE.r1t1~~7~

lNSERTE~r17•JUL•74

toi.:NT:05

FFCNT

GET LIN

LINNIJM

(;MARG

GMARGF

RMArotG

•• MODULErINFIL
CMLM2
OPENCH

••

C:MLM3
OPNSFIC

MODULE:I~Ifl
S~CNAM

OBJNAM

•• MODULESLAAE.L
LA REL

....

LC TT OP

~ODuLE1LSTNG

C:l-iLF
PUT I< Al

SIZEr~~941

C:MLMd
OPSWTt

PAGEXT

PAGNUM

IN~~RTED19•SEP•74

SEC~END

IDENT112

CMLM~

CSI~2

CSIM~

FINP1

I~PM1

OPS~T2

OLITERM

OUT Mt

STKM1

$OPSwT

SlZErn~49J

INSE~TED:31•JUL·74

SIZE1ii'~96~

INSERTEDt9•SEP·74

IDENTn11

SIZE:0~4C'll!J

INSERTEDt1•AUG•7•

IDENTH14

SIZE.1~0284

INSERTED117•JUL•74

IDENlt04

INSERTEOf 17•JuL•74

IDE NT nu

IDENT:"1

U~OFL

UBELF

•• MOOULE1LISTC
LCTBAS

LPPC~IT

SINIFL

•• 1'10DULE1JNOFL
LSTNA~

~ELEXP

TF J:(M

LI ST

PAGE

SlZE13eJ566

LI NPPG

L~TDEV

LSTREQ

?UT LIN

PUTLP

SETBVT

•• MoDULE:MAC~o

sIZEt~20tQ

PAG'1NE
SET PF~

PF0

?Ft

SETPF1

SETWDB

INSERTEDt17•JUL•74

ALTSAV

ASCII

ASC Il

AASEDT

r:uSU'.D

~ASLTFi

RA SC ND
BASLSV

BASCOD
BAS MU

JU SMAR

RAS~EG

FUSSAT

8ASSE.C

AA5SQC

RASSST

~ASSTK

B-4

BASCPX

PUTK8
SETWRD

IDENTH:l13

IHS0f-4A
BASMAC
BASSWT

8A5DUM
~ASPST

fHSSV"1

C:LCHA)(
DUMROL

CLCNAM
EDTROL

F.:~R,r,

ERR,f

CLCSEC
E"-'DFLG
ERR,I

E~~.R

E~R,T

IMPPAS

ERR,Q
IMPPAT

MU~Ol.

MAA~OL

NL I ST

ODD
REGROL
RS,CPX

A YT MOD
CODROL

CHRPNT

CLCFGS

CLCLOC

C...,DROL

CPX~OL

DMA~OL

DSAtiL

EOT

ERRMNE

E~R,

fRR,A

ER~.L

Ei:H~.M

ERR,N

ER~.O

ERR,B
ERR,P

EQR,U
IRPC
M,ACROL
OVMACR
ROLRAS
RS,EDT

E"QR,Z
LCDROL

EVEN

FL.AGS

LSYr-lOL
MQVBYT

OVSTMT
l=lOLSIZ

LI8ROL
MODE
PASS
RULTOP

PST~OL

REG~AS

RS,C~lO

QS11LCD

RS,L!H

RS,LSY

RS,QEG

RS.SAT

~S.SRC

~50ARS

~s-;,uor

RS,SEC
SA H~nL

RS, COD
RS,"IAA
RS.SST

~AVREG

SEC~OL

SECfOlo(

S IZCOD
S!ZMAA
SIZSST

SJZC.PX

SIZDM~

SIZEDT

SJZM6B

SIZSVM

S~C~OL

TOPE OT
TOPRF.'.G

SJZSTK
SYMROL
TOPLCD
TOPSAT

SlZMAC
s1zs11q
SVMROL
TO?LIB
TOPSFC

SIZDUM
SIZPST
TOPCND
TOPLSY
TUPSRC

TOPCOD
TOP'"1AA
TOP SST

StZLCD
SIZSAT
SSTROL
TOPCP)(
TOPMAR
TOPSTK

VALU~

WQ~D

XCTLIN

)(HIT 0

XMIT 1

XMIT2

XMIT5

XMIT6

XMJ T7

ALl<W

SY~BFG

"4E")CIT

•• MODl.ILF:: ~H~S
fNDLOA
PROMCF

SilE:~1~4~

JN$ERTEDr9•SEP•74

GElBLk

t-1ACR

MA( ROC

PROMT

Sf.TMAC

~CIMT

•• MOOULEs"ICALL

SIZRFG

RS,MAR
RS,STK

MACRnF

~ T • ~,AC

IMPURE
MACP2
OPCEF(~

I~PURT

MAC?2F
O?CLAS

~EGTOP

RELLVL

RS.OMA
RS.MAC

~s.ouM

RS,SltJT

SE. TXPR
SI ZLl H
SIZSEC
ST KROL
TnP!)~u

RS.PST
RS1SYM
SIZCND
SJZLSY

S!ZSRC
SwTROL
TOPDUM

TOPMAC

TQPPST

TOPSWT

TQPSYM

X"1IT3

H1lT4

I DU,, T: \!'IQ
"IT i "1 AX

SlZC.1'10264

INS~~TEDt31•JUL•74

IDENTHH

s1n:ll('B~1

INSE~TEDt31•JUL•74

IDENTHl6

P~OMA

MCAL.L

•• MODULE Z MLI BS
CPVMAC

FINSML.

•• MOOUl.E:NtSCOR
ENO

••

ERROR

MODULE1ND~CT

NA;;G

NCHR

•• MOOULE1PROCSI

GETFID

INJSML.

SlZEt~~843

GLOBL

INSERTED1Jt•JUL•74

P~lNT

SIZEtlll02~8

SB TTL

SET HO~

IDENT:08
TIT LE

INSERTEDIJ1•JUL•74

IDE~TH'l2

!NSERTED:17•JUL•74

IDENTl01

NTYPE

SIZEHHJ216

OS ADD~

DSMSI<

FNADO~

ENMSI<

NL.MSI<

PAMSI<

PROCSI

SPMSI<

•• MODlJLE&PROPC

S ~1LFDB

SIZEt0t-11865

LIA DOR

LIMSI<

INSERTED117•JUL•74

AEXP

OPCU1i1

OPCL~1

O?CL02

OPCL~7

OPCL~S

OPCL09

OPCL121

B-5

OPCL"'3
PROPC

OPCL~4

MLMSI<

NLADDR

IDENT111'2
OPCL05

OPCL0b

•• MODULEt?ROSW
PRl")SW

SwTRAS

•• MODULE:PST
A$VTOP

DFLCNO

SSTBAS

SS TT OP

•• HODULEtREAD
GE.TVBN

I~P

** MODULE:ROLHD
APPEND
N E,l( T

SlZEHH307
nFLGBM
wROSVM

A~'1,~AX

AUFT~L

lDE.NTSC~4

l"lFLGF.V

DFLMAC

DFLS~C

PST BAS

IDENTl01

SIZEH1Ci141.3

I~SERTED:Jt•JUL•74

!DENT:01

'"1PUSH

SlZFtt1~6A5

LSRFGS

ROLNDX

!NSt~TEDt1•AUG•74

LSFLAG
ROLUPD

~IZE!~c-1374

LSRCH

LSV,,KN

SCAN~

SEA~CH

JNSE~TED117-JUL-74

Jl)FNT1~6

CNfl~1SK

i. . j I) ... ~ L)

CIHJC f'.1 J

L "<Av L,.

ED.A~A

F.;), GAL

ED• RF. r;

ENDvtC

(';MAPNT
LC "1C SI
LC.Cnf-1
LC.SRC
MACNXT

LBL.E.ND
LC SAVE
LC.LD
l.C.SVM
MAr'. l)t T
MSRPRP
STLBLJF'

LCHE~L

ED,LSR
LCENDL
LCSBAK
LC.MC

LC FLAG
LC.
LC.MD

LCINIT
LC.BEX

LC,TH~

LI BNUM

MS RM RP

S~C:NUM

STAF<S

SJZErn~974

LCSAVL
LC,LOC
LC.TDC:
MAC.<1RT
MSHHT

MSAA?G

"1SB~LK

MSRTVP

P~GlDN

P~(.;TTL

TTLBRK

TTLBUF
IDENT117M

CM I RUF

C~LBLK

CNTTAL

CONT

CSIBLK

F'DR 1

GETFLG

GETPLl

HDRTTL

In, TTY

PURGMC
TSTST!<

REST RT
VB NS AV

LOAM AC
RLDBUF
SLIM IT

To\EnF

TQ,ER~

JO.NNU

nt;J~UF

n~Jf tL

SRCMRK

SRCPNT

SRCSAV

Io.our

s1Zt.l,.,li1117

I~sERTED117•JuL•74

s1nn:1~:is1

lNSERTEDt1•AUG•74

1DENTl04

SAT TOP

SEC I NI

lDENpli'1

R50UNP

C: SECT

LPqT

PSE" CT

B-6

l 'J ! N l I

LC.ME
MACGSB
MSBCNT

tNS~RTED11•AUG•/4

MACLDG
SRCCLO
SSwTCH

•• MClDULEISECT?

MSRCH
SSRCH

EDMCSI

MSHLr.H

** MODuLE:i<5UNP

LSG8AS
SCAN

IDE~Ta05

r r~ n11 r x

C'\iULVL
EDMRAK
GMAblK
LC MA 51(
LC,CND
LC.SEQ
~AC NAM

!:LOSRC
l='DBTBL

RE~T

FDR2
IQ,OPN
PASSSW

ASECT

PST TOP

INSERTEDr17•JUL•74

INSERT

•• '-'ODULE I RSEX~C
DE FMC

INSERTED117•JUL•74

S!ZEHHll198

OSRCH

MODULE:~Sl".IAT

EDMASK
FXMFLG
LCLVL
LC.RIN
LC,MEB
MACLVL
MSREND
SMLLVL

IDFNTt03

S111TTOP

l AF'

••

TNSERTEDt17•JUL•74

$READ

** MODULEt~EPl
ENDMAC

SJZEt0~258

SATEHS

DAT TIM
IOfTRL
LSTFIL
S?SAV
$LSTVZ

•• MODULErSETDJR

s1ZE1~~126

INSERTED117•JUL•74

IDENT:~2

SIZE1~~292

tNSt~TEDt17•JUL•74

IDENTt~2

SET DIR

SETON

SE"TTIM

•• MODULEISETIMM
SE.TDSP

HTIMM

•• MODULE:SPACE
MRKUUT

QEMMAC

SHFMS8

•• MODULE:STMNT

SQZSTK

SIZ~r~~3t~

IN5ERTEDr17•JUL•74

IOE~T:~J

SIZE1~~732

TNSERTED:17•JUL·7~

IDENT:~4

STMNT

** MODULE:SVMBL
Ai'CGCNT

4~GPNT

Cl-1SC6N

CT.NUM

CT.~C

CT, PC: X
DNC:F

CTTHL
CT.SMC
E.XPFLG

CT,SP
GETCHR

CT.COM
r:T,SPT

CT, Tli8

cvTNUM

GETNR

GETR5vl

GETSYM

MlJL

MUll-<5~

SET CHI<

SETNµ

SETR5~,,

SET SY~i

nrv

r')~J

GS~RG

GS6RGF'

TSTARG

TSTF-t~ii

SIZt:~~141

••

B.1.4

CT.ALP

!NStRTED:17•JUL•74

IOENT:~2

~ODULF."1~~11~

List Module Names and Module Entry Points (Global Symbols)
LBR>MAC, LP: /LE__}
or
LBR>MAC, LP: /LI/LE.,)
DI~ECTO~Y
~~

nR.H. CT

nF FTLE

n1J LE

LAST !NciEh'T

~Ac.nLRJ1
LI~ !.U. RY C ~FA Tf. r'l

occ:u~~rn

RV:

LB Q V)( 0 2 V~

22·SEP·74 4T 11 ::,1 =~~

B-7

~LLOC:ATEDI 64J AVAlLABLEs 2~
ALLOCATtOI 64~J AVAILABLE a 9~
FILE SPACE AVAlLAALU ~L-'~15 liiOQDS

f'lllNT
EPT

FNT~TES

F..:NTl-lIE~

•• MOOULE'IASGMT
ASG~T

ASGMTF

•• Ml')DIJLEIASSEM
ALL QC$

CLSALL

rnR ITS

LC:BITS

MACP1

lCCTPAS

XCTPRG

F.~JDC

JFF

IFT

IFTF

IIF

TNSIZE

!1HJDMP

08JINI
~LOPNT

OBJ SEC
ZAPCPlC

PCRCNT

~Ll')DMP

ORJLOC
STCOOE

OB.JPNT

PC~TRL

PAD IV

IHM:i~

~ELEXP

ASSfM

•• MODULE:CNDll
CNfHUS

C~DTC'P

•• MODULEICODHD
CP'XSTL
PC ROLL

TST~LD

•• MQOllL E J DA TOR
~Ll<B

tDE'~T

". MODULEIENBDS
F.DT~AS

EDT TOP

ENA Bl

•• M00ULEIEN0LN
E ~DLI N

ERQRTS

~~QCNT

LINBUF

LINE ND

LSTHUF"

ARSTRM
TERM

A8STSl

EXPQ

GLREXP

GL~ PH1

Ll N ~JI.I H

LPPCNT

PAGEXT

PAGNIJ~·1

SEQEND

•• ~OOULEIEND~S
ENDPt

...

ENDP2

MOOULEIEXPi;.iS
At;iSE.Rf.l

ARSE)(P

REL TR~

QfLTST

•• MODULE1FLOAT
•• MODlJLEtr.ETLN
FFC "iT

GET LIN

B-8

GM!~G

t'.PO!oiGF'

QMH~G

•• MODULF.' I 1 NF'll
CMLM:?

C~LM3

CHLH4

C"1LM5

nPENC:H

OPNS~C

OPSittT1

OP~~T2

C: SI "1 t>
OUT ERM

CSIM~

F!NP1

P~PM1

OUTM1

5TKM1

$Q?SWT

•• MODULE1INJFL
SRCNAM

$J~IFL

•• MODULE:t~OFL
LSTNAM

...

OBJ NA""

'l"-IOFL

MODULEZLAAt.L
LAAEL

;to

LA8E.LF

MODULE:LJSTC

LCTBAS

LC TT OP

LI~ T

PAr.t.

LSHH'.V

LSTi.CF1~

PAG~NE

pi:·~

PF1

PUTKA ·

PUTLP

SETbYT

SETPF0

SET PF 1

SET111DS

SEhiRIJ

ASC lZ
RASLIH

RA SC ND

BASCO(')

EU SC PX

BASUt-1A

RASDUM

RASLSV

AAS~AA

RA~MAB

BASMAC

fHSPST

RASSRC

8ASSST

~ASSWT

CLrFGS

BASSTI<
CLC:MAX

AASSYH
CLCSEC
ENDFLG

•• MOl)ULE':LSTt-.iG
Ci<LF

r-'UTt<BL

LI t-IPPG
PJTLIN

•• ,.;noULEr~ACRO
ALTSAV

ASCII

AASEDT

~ASL CD

~ASREG

8ASS~T

RLK~

RYTMOD

AASSEC
CH~P"-1 T

CNl)ROL
F:OT

CIJDto<OL

CPXi.WL

l')~H ~OL

CLCLOC
r'lSAgl

E~R,..."4t.

FR~.

E~P.A

F.~R.R

~RR.D

CLCNAM
EOTRnL
FRR.E

E~R,L

E'RR,M

Ek'R,N

F~Q,P

E~P,Q

E.RR.R

F.Rl-<,T

i:~~.u

~Q~.z

F VF N

EMR,O
FLAGS

IMPURE

LI~ROL

LSY~OL

MODE

MOV!;VT

NLJ ST

Q\/MAC~

liVST~T

PAS~

REG~AS

ROLP,AS
RS,EDT

ROLTnP

RS,COD

~S.LtH

R~.'1AA

RS,MA~

~S,REG

ROLSJl.
QS,LCO
?S.SAT

PSTROL
RS,CND
QS.LSY

MAAROL
ODO
REGMOL
RS,C?X

MACP2

MACROL

LCDROL
"'1EX IT

JMPPAS
MUROL

IMPPAT

I~PC

PS.SEC

~S.SRC

RS.SST

RS.Sh

R5;11ARS

~5~DOT

SATROL

!;AVRE"G

SEC~OL

SECTOlo<

~IZCOD

~IZCPX

SIZDMA

SIZEl'H

SIZMAA

SlZMAB

srz uc

SI ZOUM

S!ZREG

SI ZLCO
SIZSAT

SI7SST

~IZSTI<

S!ZSwT

SilPST
SIZSYM

S~C~OL

SST~OL

SYM~EG

~Y"1H0L

~""'~nL

TOPC~D

TOPCl='X

TQP~l)T

TOPLt:D
TQPSAT

TCH'LlA
TOP SEC

TtJPSRC

VALUE

"40~ [)

)(CTLTN

)(HJ T0

TOPCOIJ
TOP"1AA
TO? SST
Hl! T1

)(MJT5

oqu;

XM !T7

TOPRFG

TOPLSY

B-9

f)Ut-4Rf1L

TOPMAH
TOPSTK
XMIT2

~RR,T

~JZSF.C

!MPURT
MACP2F
OPCLAS
RELLVL
RS,r>UM
RS.PST
RSeSVM
SIZCND
STZLSY
SilSRC

ST KROL
TuPDMA

s~TROL
roPou~

TQP"1AC

TOPPST
TQPSYM
XMIT4

OPCE~~

REG TOP
RS.OMA

RS,MAC
RS,SWT
HTXPR
S IZLI t-4

TtWSWT
X'.~ IT 3

•• "1nDIJLE s l.1H~S
PRM'1CF

PR 0'1T

St Tr-uc

WCJMT

(;ETF ID

INJSML

SMLFD~

Gl0f3L

P~JNT

SB TTL

SETHDR

TITLE

EN rnn~

EN~SK

LIA!)DR

Ll~SI<

MLMSI(

NLADD~

P~ncs1

SPMSK

OPCL~42

OPCL~S

OPCL~o

DFLS~C

PSTtU~

PST TO?

•• MODULr::1-1cALL
MCALL

••

MODULE:~LJB~

CPVl-1AC

FI NS~L

•• MOOULE:~SCDR
EN I)

F.:~RQR

•• M<iOULE:NDQCT
NARG

\JCH~

NTYPF.

•• MQDULE:P~OCSI
1154[)1)~
NL~31(

••

D5M51<
? A "151<

MIJDUL~:P~Ol-'C

AE)tp

OPCL~(1

tiPCL~l

OPC:L02

OPCL~J

OPCLM

r'JPCL~B

OP CL'~ g

QPCL1~

PR()PC

nFLGEV

DFL~1AC

•• MnDULE:Pi-lOS~
PRQSW

s..iHUS

Sl'iTTOP

•• MODuLEsPST
RH TOP

SST!iAS

DFLCND
SSTH1P

rH·LGRM
~l/1<DSVM

•• MQDULEaREAD
GETV~N

~READ

•• M(lOIJLE'lqEPT
F,Nf)l-1AC

J~P

~PLIS11

~tPT

!NSflH

LS~Fr.S

UiFLAr.

LSGiHS

LSRCH

LSY~l(N

MS~CH

l')S;(CH

ROLNl')X

ROLUPD

SCA"l

SC A NIAi

SS~CH

•• MODIJLEi~OLHD
APPEN0
NE )(f
7AP

B-10

•• Mt"lDULE:: Q51'Al
A~Gi'"i 4 X
F.:QMASt<

EXMFLG
LCLVL
LC,8IN
LC,MEA
MACLVL

EDlN!i
ENDVE'C

eNDLVL.

eNDHFA.

CN[}M5~

C1'iDiiii:tD

cONCrH

CR1on:

fDMHAK
r;MAFiLK
LC MASK

FIJMCSI
r;MAPNT

ED. GBL

EO • LSB

F.D.~EG

Lc.cND

LC.COM

ED.AMA
LBLEND
LC SAVE
LC,LD
LC.SYM
t-H CT XT

LCBE(';L
LCSAVL
LC.LOC

Le.roe:

LCENDL
LCSBAK
LC,MC
LC,TTM

LCFLAG
LC.
LC.Mr)
LI RNUM

LClNIT
LC•BEX
LCeME

MACvHH

MSA~LK

'"1SBCNT

PRGIDN

PQGTTL

LC MC SI

LC• SFC.i

LC,S~C

MACN'O

MS~ENO

MACNAM
MSBLGH

SMLLVL

S~C:NlJM

MACGSR

MSBMRP
STARS

MSBPRP

MSB TX T

MSRH'G
MS~ TVP

STLBUF

TTL 8QK

TTLBUF

CONT

CSI8LK

DATT IM

GETPLI

~DR TTL

IO, TTY

LOA MAC

REST~T

IOFTBL
LSTFIL
S?SAV
$LSTVZ

•• MODULE i ~SEXFC
CL0Si:;>C
FDBTl?L

r,MIBUF

CMlt3LK

F'DB l

F0~2

TO,t.RR

T(l,NNU

I 0 • 0 P ~J

08J~UF

ORJFIL

PASSS~

C>.JTTRL
GETFLG
IO,OUT
PURGMC

SRCCLO
'SWTCH

SQCMwK

SrcC~NT

S~CSAV

TSTSTK

VANS AV

RLDBUF
$LIMIT

•• MODULE I

qsu~~p

LI r-11 T

PSf.CT

SA HUS

SA TT np

SEC INI

SHFMSB

SQZSTK

BUFTBL
nEFMC

lOHOF
"1ACLDG

R~~UNP

•• MODULESSEClR
ASECT

CSECT

•• HODULEtSETr>I~
SE TD IR

•• MODULE:SE.TO~
SETON

...

SE.TTPI

MODULE s ~r. TI MM
SE.TDSP

SET IM~

•• MODULE I SETM)t'
~ET~AX

•• HODULErSPACF
M~KOUT

~EMMAC

•• MODULE: SH1NT
STMNT

B-11

•• MOOULEiSYMBL
A~GCNT

CT• ll.IU"'1
(')IV
GSARG
TSTARG

AQGPNT
CT• PC:

CHSCAN

DNC
GSARGF

DNCF

r:TTBL
Cl,S"'1C
F.XPFLG

r-1UL

~ULR50

rT,PCt

TSHHH~

** MODULE 11t1QRDB
BYTE

SQCMO

B-12

CT.ALP

er.en~

CT.r:OL

r.T.Lr

Cl, SP

r:T,SPT

CT,TAb

Cvl~U~

GET CH~
SET CH~

GE Tt~ Fl

GE.T~~l?.I

GETSYM

SEH~R

SET~5~

SETSY"1

B.2
B.2.1

SAMPLE LISTING FOR LBR LIST SWITCHES (MACRO LIBRARY)
List Module Names
LBR>MAC,LP:_)

or
LBR>MAC,LP:LI.,}

DlRECTll~Y OF FlLE EXEMC,MLBH
~ACRO Ll~RA~v c~F.ATEO ~vs
LB~ vi~3,4
LAST P.iS!:.~T occ~1"~E.O 2 .. j[JN•75 AT il:i6i25
M~T ENTRIES ALLiCATfOI 641 AVAlLA~LEs ~2

EPi ENTRIES A~LOCATEOt ~J AVAILABLE: 0
FILE S~ACE AVAILABLE• ~~789 wowns
ARQDF$

CLl<OF$

CUC OF$
CVCDF$
OEVD~$

EMBQn
F11DF~
HOROfi:~
~~OOFi

PC8DF$
r.:i1<TQF$
TC6D~!

B-13

B.2.2

List Module Names and Full Module Information
LBR>MAC,LP:/LE/FU_)
or
LBR>MAC,LP:/LI/LE/FU_)
OlRECT~~v

OF FILE

EXf~C,Ml~Jl

1"1ACRC! l !R~AiJy C~FATE:.r. RVS
LHR v•v.i3,d
L AS T I ·~ Sf '< T 0 CC: ' I ~ ~ f. '.) 2 • J lJ ti; • 7 5 A T 1 7 2 1 ei I ? 5
~ N T E ~"' T ":' I f S A Ll. J C A T t. (i : 6 4 1 A V A I I. A ~ L E J 5 2
~PT

~NT~r~s

FlLF

SPAr~

ALLOCATED: ~f AVATLAbLEI 0
AVA!LARLf J 007~9 ~OQOS

B-14

SAMPLES OF LISTING AND EDITING
B.3

SAMPLE EDITING OPERATIONS

Four sample editing operations are
included
in this section to
illustrate how the various EDI commands can be used.
In the first
example, a file is edited using a few basic EDI commands.
The second
example,
illustrates the use of the SAVE, UNSAVE and PASTE commands.
In the second example, two save files are generated, modified, and
appended to the original file.
Any closed file may be appended to or
inserted within an open file in the same manner shown in the second
example. The third example illustrates how an immediate macro command
can be defined and executed
in a single step.
The last example
illustrates how a file containing errors can be edited using the macro
commands.

B-15

B.3.1

File Editing Sample

>EDI PRTBLD.CMD./
(PAGE
1]
*P * :.J

File PRTBLD.CMD is opened for editing. A PRINT * command
is issued to print the contents of the file.
The following
errors are detected:

J..

J COMMAND FILE TO BUILD
; PRNT SYMBIONT
J FOR RSX-llM MAXXED SYSTEM

1 - PRNT should be PRINT.
2 - MAXXED should be MAPPED.

;

11,54]PRT/MM/-CP,LP:=PRTBLD/MP

3 - /CP should have been used instead of /-CP.

i
~; OPTIONS
;

4 - INPUT should be appended to the line containing
the word OPTIONS.

STACK=40
PAR=PARK:O:lOOOO
!JNITS=4
TASK=PRT ...
ASG=C0:2,LP:3
PRI=60
UC=[lO,l]

5 - PARK should be PAR4K.

6 - UC should be UIC.

;

, SPECIFY
; SPECIFY FLAG WHICH CONTROLS
; FILE DELETION AFTER PRINTING
.L
J TO ENABLE DELETION USE

7 - The line containing

SPECIFY should be deleted.

;

GBLPAT=PRT;$DELET:l
TO INHIBIT DELETION USE

;

; DEFAULT FROM ASSEMBLY IS
; FILE DELETION ENARBLED

8 - The comment line containing the format used to inhibit
deletion is missing.
9 - ENARBLED should be ENABLED.

GBLPAT=PRT:$DELET

-f*EOB*]

10 - A :1 should be appended to the line following
the word $DELET.
The end of buffer is reached and EDI causes the EOB message
to be printed.

*TOF__}
fPAGE
1)
*PL PRNT__.J
: PRNT SYMBIONT
~C/RN/RIN/__)
; PRINT SYMBIONT
"!!..._/

; FOR RSX-llM MAXXED SYSTEM
*C/XX/PP/._,/
T FOR RSX-llM MAPPED SYSTEM
~NP

3__)

[l,54]PRT/MM/-CP,LP:=PRTBLD/MP
~C,/-CP,/CP,__J

[l,54]PRT/MM/CP,LP:=PRTBLD/MP
PAR=__.)
PAR=PARK:O:lOOOO
~ C/RK/R4K/_.)
PAR=PAR4K:O:l0000
~PL

~NP

-3_/

; OPTIONS

~AP

INPUT~

; OPTIONS INPUT
~PL UC___;
UC=[lO,l]
~C/UC/UIC/__)
UIC=[lO,l]

A TOF command is issued to move the line pointer to top of
file and editing is started.
1 - A PAGE LOCATE command is issued to locate the first
line in error and the line is printed automatically.
A CHANGE command is issued to correct the line
and the corrected line is verified automatically.
2 - A carriage return is entered following the prompt to
move the line pointer and print the next line in error.
A CHANGE command is issued to correct the line and the
corrected line is verified automatically.
3 - A NEXT PRINT 3 command is issued to locate the
next line in error and the line is printed. A CHANGE
command is issued to correct the line and the corrected
line is verified automatically.
5 - A PAGE LOCATE command is issued to locate the next
line in error and the line is printed automatically. A
CHANGE command is issued to correct the line and the
corrected line is verified automatically.
4 - A line in error was bypassed by mistake; therefore, a
NEXT PRINT -3 command is issued to back the line
pointer up. An ADD AND PRINT command is used to correct
the line
6 - A PAGE LOCATE command is used to located the next line
in error and the line is printed automatically.
A CHANGE command is issued to correct the line and
the corrected line is verified automatically.

l"lj

t"1
H
(/)

8
H

:J::"

ti:l
t1
H

8
H

~_)

!.J
; SPECIFY
:DP_.)
; SPECIFY FLAG WHICH CONTROLS
~PL

INH_.)

; TO INHIBIT DELETION USE
:I_._J
;~

GBLPAT=PRT:$DELET:O__J
..,,;

:PL RB_.}
; FILE DELETION ENARBLED
_":_C/R//_J
; FILE DELETION ENABLED

)

7 - The line pointer is moved down two lines via the
carriage return option to locate the next line in
error. A DELETE AND PRINT command is issued to delete
the line containing ; SPECIFY and print the
next line.
A PAGE LOCATE command is issued to locate the
point in the file where the new comment lines
are to be inserted. EDI is switched to the Input
mode, two lines are entered, and EDI is switched
back to Edit mode by entering a carriage return as
the first character in the line •
9 - A PAGE LOCATE command is issued to locate the next
line in error. A CHANGE command is issued to
correct the spelling error. The line is verified
automatically.
8 -

10 - The line pointer is moved down two lines using two

;

*..)
~BLPAT=PRT:$DELET
:~AP : l._J

carriage returns to locate the last line in error.
An ADD AND PRINT command is issued to append
:1 following the word $DELET.

GBLPAT=PRT:$DELET:l

-~TOF::J-·

[PAGE

The necessary corrections are complete so the line
pointer is moved to the top of the file via a TOF command.
trl
t:1
H

H
H

A PRINT * command is issued to print the complete
file with all corrections

; COMMAND FILE TO BUILD
; PRINT SYMBIONT
_L_!_OR RSX-llM MAPPED SYSTEM
;

[l,54]PRT/MM/CP,LP:=PRTBLD/MP
;

T OPTIONS INPUT
;

STACK=40
PAR=PAR4K:0:10000
UNITS=4
TASK=PRT ...
ASG=C0:2,LP:3
PRI=60
UIC=[lO,l]
;

, SPECIFY FLAG WHICH CONTROLS
FILE -DELETION AFTER PRINTING
;

; TO ENABLE DELETION USE
;

;

GBLPAT=PRT:$DELET:l

;

; TO INHIBIT DELETION USE
;

;

GBLPAT=PRT:$DELET:O

;

; DEFAULT FROM ASSEMBLY IS
FILE DELETION ENABLED
;

GBLPAT=PRT:$DELET:l

[*EOB*]

~EX_}

[EXIT]

An Exit command is issued to close the file and
terminate the editing session.

B.3.2

SAVE and UNSAVE Example

*LI__}
THIS IS
THIS IS
~HIS IS
~HIS IS
THIS IS

LINE
LINE
LINE
LINE
LINE

1 PAGE
2 PAGE
3 PAGE
4 PAGE
5 PAGE

1
1
1
1
1

.[*EOB*]
:~.::;-

The line pointer is returned to the top.
A SAVE command is used to save the
five lines in a separate file.

*SA 5 SAVI. DAT___./

~T__.J
~SA 5

The line pointer is returned to the top.
A second SAVE command is used to generate
a second saved file. The primary input file is closed.
The first save file is opened and a
LIST command is used to verify the file.

SAV2.DAT_}

-~CL__}

tp
I

"'
0

_EDI>SAVl. DAT_.)
[PAGE
l]
:LI_}
'rHIS IS LINE 1 PAGE
'rHIS IS LINE 2 PAGE
THIS IS LINE 3 PAGE
THIS IS LINE 4 PAGE
'rHIS IS LINE 5 PAGE

The file to be used in this example is
printed via a LIST command.

1
1
1
1
1

[*EOB*]

----

"'PA/PAGE l/PAGE 2/__.}
THIS IS LINE 1 PAGE 2
'rHIS IS LINE 2 PAGE 2
THIS IS LINE 3 PAGE 2
'rHIS IS LINE 4 PAGE 2
THIS IS LINE 5 PAGE 2
~CL__)

A PASTE command is used to change
PAGE 1 to PAGE 2 in all lines.

The first save file is closed.

The second save file is opened.

EDI>SAV2. DAT___}
[PAGE
l]
~LI__}

THIS IS
THIS IS
THIS IS
THIS IS
THIS IS
[*EOB*]

LINE
LINE
LINE
LINE
LINE

1 PAGE
2 PAGE
3 PAGE
4 PAGE
5 PAGE

~PA/PAGE l/PAGE

THIS
THIS
THIS
THIS
THIS

IS
IS
IS
IS
IS

LINE
LINE
LINE
LINE
LINE

EDI>START.DAT_)

(PAGE

3/._}

1 PAGE
2 PAGE
3 PAGE
4 PAGE
5 PAGE

~CL_)

1
1
1
1
1

3
3
3
3
3

The LIST command is used to verify
the contents of the file.

A PASTE command is used to change
PAGE 1 to PAGE 3 in all lines.
Ul

::s::

"'O
L'

The second save file is closed
The original input file is opened again.

tI:I
Ul

t-ij

L'
H

1-3
H

::t:oi

t:l
tI:I

t:l
H

1-3
H

~BO_._/

to
I

N
N

THIS IS LINE 5 PAGE
~UNS SAVl. DAT_}
*UNS SAV2. DAT__)
*T.._/
!LI..J
THIS IS LINE 1 PAGE
THIS IS LINE 2 PAGE
THIS IS LINE 3 PAGE
THIS IS LINE 4 PAGE
THIS IS LINE 5 PAGE
THIS IS LINE 1 PAGE
THIS IS LINE 2 PAGE
THIS IS LINE 3 PAGE
THIS IS LINE 4 PAGE
THIS IS LINE 5 PAGE
THIS IS LINE 1 PAGE
THIS IS LINE 2 PAGE
THIS IS LINE 3 PAGE
THIS IS LINE 4 PAGE
THIS IS LINE 5 PAGE
l*EOB*]
*EX _.., J
-·
1EXIT]

1
1
1
1
1
2
2
2
2
2
3
3
3
3
3

The last line in the file is located.
Two UNSAVE commands are used to
append the two save files to the
original input file.
A LIST command is used to
verify the contents of the
combined file.

CJ)

'""Cl
L'
trl
CJ)

'Tl

L'
H
CJ)

1-3
H

::r;.

tJ
trl

tJ
H

1-3
H

B.3.3

Use of Immediate Macro Command

~LI__}

LINE
LINE
ABC IN LI_NE
_ABC __ IN LINE
ABC IN LINE
AB~-- IN
AB_~ IN

- ABC
2 - ABC
3 - ABC
4 - ABC
5 - ABC

A LIST command is issued to print
the file used in this example.

.:...

tx1
I

ABC IN LINE N - ABC
[*EOB*]
~4<F ABC&C/ABC/DEF/>../
[OVERLAYING PREVIOUSLY DEFINED MACRO]
ABC IN LINE 1 - ABC
DEF IN LINE 1 - ABC
ABC IN LINE 2 - ABC
DEF IN LINE 2 - ABC
ABC IN LINE 3 - ABC
DEF IN LINE 3 - ABC
ABC IN LINE 4 - ABC
DEF IN LINE 4 - ABC

The immediate macro is defined
and executed to find the first
four lines which start with ABC
and change the first occurrence
of the string ABC to DEF.
The FIND command causes the line
to be printed before the change.
The CHANGE command causes
the line to be printed after
the change.

B.3.4

Use of Macro Commands

~LI_}

THIS LITTLE FILE HAS
MANY CONNON ETTORS SO
WE CAN SHOW YOU HOW
YHE MACRO CONNANDS CAN

The LIST command is used to print the
file and the file is checked for errors.
The following errors are located.
1. The string NN is used in place
of MM (see macro 1} •

~~USED.

FIRST, YHE DESIRED MACRO
MUST BE DEFINED; YHE LINE
POINTER IS MOVED TO A LINE
WITH AN ETTOR; AND YHEN, YHE
MACRO EXECUTE CONNAND
IS ISSUED TO COTTECT YHE

2. The string TT is used in place
of RR (see macro 2) •

3. The string YHE is used in place
of THE (see macro 3) .

~TTOR

f*EOB*]
*MACRO 1 C/NN/MM/_.}
*MACRO 2 SC/TT/RR/_.)
*MACRO 3 PA/YHE/THE/_.)
*M3 _.}
THE MACRO CONNANDS CAN
FIRST, THE DESIRED MACRO
MUST BE DEFINED; THE LINE
WITH AN ETTOR; AND THEN, THE
IS ISSUED TO COTTECT THE
_:NP2__.}
MANY CONNON ETTORS SO
~Ml_}

The three macro definitions which will
correct the errors are typed.
Macro 3 is used to change all YHE
strings to THE.

NP2 is used to locate a line with errors.
Ml is used to change NN to MM.

MANY COMMON ETTORS SO
~M2_.)

MANY COMMON ERRORS SO

M2 is used to change TT to RR

~NP2__}

THE MACRO CONNANDS CAN
~Ml:J
THE MACRO COMMANDS CAN

NP2 is used to locate the next line in error.
Ml is used to change NN to MM.
M2 is used to locate the next TT string
and change it to RR.

WITH AN ERROR; AND THEN, THE

* )
----

MACRO EXECUTE CONNAND
*Ml_.}
MACRO EXECUTE COMMAND

_}is used to locate the next line in error.
Ml is used to change NN to MM.

~M2__}

IS ISSUED TO CORRECT THE
~M2__...J

.ERROR

M2 is used to locate the next TT string and
chanqe it to RR.
M2 is used to locate the last error in the
file and correct it .

~T__/
~LI_)

to
I
N

THIS LITTLE FILE HAS
MANY COMMON ERRORS SO
WE CAN.SHOW YOU HOW
THE MACRO COMMANDS CAN
BE USED.
FIRS~THE DESIRED MACRO
M.U.S_T BE DEFINED; THE LINE
POINTER IS MOVED TO A LINE
WITH AN ERROR; AND THEN, THE
MACRO EXECUTE COMMAND
IS ISSUED TO CORRECT THE
ERROR.
[*EOB*]

After all lines have been corrected, the
file is printed using the LIST command.

B.4

SAMPLE DMP LISTINGS

B.4.1

Use of /LB Switch

DMP>TI:=SY:BIGMAC.TSK/LB_.}
STARTING BLOCK NUMBER = ~£135163 C
~TI:=SY:SYSGEN.CMD/LB__}

~'~~16~6

STARTING BLOCK NUMBER=
B.4.2

"Standard" Command Line

This command will dump virtual blocks 1 and 2 in SYSGEN.CMD in
ASCII mode.
DMP>LP:=SY:SYSGEN.CMD/AS/BL:l:2_.}
DMP>
OU MP OF

000000
000020

000040
0000b0
000100

DP01[200,200]SVSGEN,CMOJ15 •FILE ID 7157,35146,0
vlRTUAL BLOCK 0,00~~01 • SIZE 512, BYTE'S

••A ••R. T'
T

E
M

T
L.

000120

000140
0001b0

R
A

B
E
E

0H200

< .. ,

000220

R
H

000240
0002b0

0003b0
000400

0HU0
0004&0
0210500
H05Z0
000540

0005&0
000b00
000020

000b40
H06&0
000700
000720

•p
1
M I
u R

s y s
6
s v s

)(

""I
M

s s
c u T

•• ••y , ••u , ••B u• •I sL. 0 I NA
M

u•
I

A
A
N
N
N

0
p

B
G

w I

E
I<

R
N

•
H
w

-~
N

6
I
E

T
A
E

ti1

0
0
L

0
A

R
T

G
M

0
E

s ,,.A

p
E
f
E

I
A

, •• •• c c s ss
s ... .... ' ... •o ... s ....
l iii.
= ... •G , s'
s
x

000300
210121320
0003ll0
000~20

-. •• "'",' ti. , .... ""• ,

A
I

-·
-·

u
A

s
c

s
I
f
I N
L
••
•• • I
••
N s
F
f
l
A c •z ••
B
• I
I
B I G
B
A c •
F F
, I 0 E M •• c• I .,.wF' ....T aI
T s
s * B I
I
••
•
F T
, * I B0 E .,pF ...II .-,pL. E ••s A Fc R• T0 sDM E
L E T E
'
'
s y s G E
s
·1
s T
..,I 0
v I R G I N
N 0 T E
'
0
E
I'
T
s
D I s
[

'"'G

... N

,..Q

I<
N

A
M

...

N
N

000740

T
L.
l

H0'7b0

E
0

... x
F

s s

E
l
fill ·1

s
v
G I
G e: s ...
I

B-26

0
T
E

w E

, 5 i iE.

T
E
I

R R 0
1 -1 •1

-·
~

p
R

1
w
M

•

DUMP OF OP01[200,Z00]SVSGEN,CMOJ15 •FILE IO 7157,3514&10
VIRTU~L

000000
000020
00004'0

H00b0
000100
000120
000140
0001&0
000200

000220
000240
0H2b0

000300
000320
000340
000300
000400
0004Z0

0
--A

p
E
0

•N

T
0

]

T
E

•0

•••• s I '
•s ••
I
p

L
p
T
F

--· -s ...

• c M 0
R s x 8

E. .. p

T
N

u •p
2

E
E

T
p

• c
* u•
I

p
E

x
I
p
E
M
0
I
R

H ·s
0

F
I

I
I

s
I

I..

A
E

•s

e J
c
c 1
s =
x A s

...

p
I

T • f
c =
c
s x '4

.,
-·
' •

t<
0

l
M

p
E
0

•••• s EI T *I u• 0I cB •J' *, *1 1 , ""•E
p
s
s T B • M .
""R ••
I
p I
E
c
0
I
••
*M A c ,
... ... R, ••s 7x M
I
c
0

1-1

u
N

[

c u
R

w E
E w
E

N
0

000&60

00071210
000720

I
F
M B
G
t F

I
N

R
H
y

L
E

•w E

E
I

s
s...
s

s
I
0
0
y
N

•
A
y

G
M

u L
T

L
R

•R

D
I

]

, s'

000540

12100760

0
A

"'N

000740

•p

000500

000040

••1

D
M 0
I
• cs "
x B L' *D • c
p
p

000560
000«>00
000020

T
E

000440
012104b0
000520

T
E

BLOCK 0,000~02 • SIZE 512, BYTES

N
E
E
N
N

A
0
A
I
A

B-27

c
G
D

T
T
y
0

c
s
T
s

p
T
0

E
0

N
~

R
R

!Iii'0

T
;
E

N
G

...
I

•1

"'•

R
R

H
"'I

R
1

E
b
y
p

s
A

,
'
"•
u ,.
I
M

N
I
0

s
I
u

""'p:•

E
E
N

s
0

R
K
0

E'
"'I

s s e:
'9i ..

B.4.3

?ump Only the Header from SYSGEN.CMD

DMP>LP:=SY:SYSGEN.CMD/HD/BL:~:~_)

DMP>

DUMP OF OP01[200,200]SVSGEN,CMDs15 • FILE ID 7157, 3514b10
FIL.E HEADER

(7157135140)
SYSGEN.CMOS15
[200, 200] [RWEO, RWEO, RwE01 R]
000000

000020

000040
0000b0

000100
000120
000140
000lb0

000200
000220
0002tH~

0002b0
000300

000320
000340
0003b0
0~0lf 00

000"'20
000"'40
000~60

000500
000520

000sq0
U05o0
000b00

000020
000040
H0bo0
000700

000720
000740
0007b0

B.4.4

000401 100200
0000'11"1 000010
00000~ 000000
000015 000001
030462 0474bl
k'J00000 0000PI~ 000000
1'H>00o 0020A"1 001 &0&
000000 0000A0 000000
000000 00000"' 000000

027027 007157 ~3514b
"90077 000000 000012
000000 1300~00 000000
02b22b 0000L'J0 012314
030464 032461 030462

034064 032461
000000 0014lH

11 .. oc;r .. 74 11148

1,110.

1&0000 000000 001002
000000
000000
030401
052103

000000 000000
000000 075273
041517 033524

032067 030461
000000 000000 000000
000000 0441Sb 001400
0000~0 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
000000 000000 000000
00121000 000000 000000
000000 000000 000000

044300 000000
000000 000000
00b000 ~00000 000000 0000PIA 000000
~00000 000000 000000 0000V11~ 000000
000000 CHJ0000 000000 0000PI~ 000000
0'10000 0000(30 00000121 0000~~ 000000
000000 1Hl0000 000000 000000 000000
ae0000 000000 00000121 0210121"''1.I 000000 000000 000000 0001210 0
0"0000 000000 000000 0000PI~ 000000 0000'110 000000 000li:Hrn
LJ0~000 000000 000000 0000AA 000000 00001210 000000 000000
'100000 000000 000000 0000AA
000000 1.Hl0000 000000 0000~A
000000 000000 00D000 0000PIA
0"J00"J0 000000 000000 0000PIA
000000 IJ00000 0000ft~
000000 000000 0000AA
000000 000000 1300000 0000M
000000 1300000 000000 000001')
000000 000000 000000 000001'1
000000 000000 000000 0000PJA
000000 1300000 00001210 001Z10AA
000000 ~00000 000000 0000l-'A
000000 000000 000000 0000~~
000000 IHJ0000 .,00000 0000PIVJ
000000 '300000 000000 0000~"'
iJ~0000
0~0000

000000 000000
000000 000000
000000 000000
000000 000000
000000 000H0
000000 000000
000000 000000
000000 000000
000000 00001210
000000 0000H
000000 000000
000000 000000
000000 000000
H0000 000000
000000 000000

000000 000000
000000 000000
000000 000000

0HH0 000000
000H0 000000

000000 000000
000000 000000
000000 000000
000000 000000
000000 000000

000000 12100000
000000 000000
000000 00000Ql

000000 000000
000000 1bb212

Use of /BA Switch

The first command sets the base block address to 2, the next command
causes virtual blocks 3 and 4 to be dumped.
~/BA:~:2_)

DMP>LP:=SYSGEN.CMD/BY/BL:l:2.j
DMP>

B-28

DUMP OF OP01[2001200]SYSGEN,CMOs15 •FILE lD 715713514610
VIRTUAL BLOCK

000000
000020
000040
000060
0210100
000120

000140
0001 b0
000200

000220
000240
0002&0

000300
000320
000340

000360
000400

000420
000440
000460
000500
000520
000540

000so0
000000
OIOIOl~:>OI
.,.,.,
""

.....

000040
000000

000700
000720
000740

000700

0100~~03

• SIZE 512, BYTES

.
...... 115
.
.
122 104

103 110 111 116 105 040
I. i
110 040 001
I '"1
073 011 131 117 125 0't0
123 105 115 102 114 131
117 116 11'4 131 0lH?l 111
040 114 111 123
103 124 040 124 110 105
10b 040 131 117
105 040 114 111 116 105
115 040 124 117
114 120 060 072 051 040
040 120 122 111
040 104 111 123 113 056
117 122 040 101
ia40 0lf 0 124 110 105 122 105 ()J40 111 123 040 116 117 124 040 040
01.&0 103 '162 000 ~73 011 105 t16 117 125 107 110 040 123 120 101
1 ()3 105 040 111 116 040 124 110 105 0412! 123 117 125 122 103 105
040 104 111 123 113 01~0 124 117 040 113 105 105 120 040 101 111.1
114 0ll0 124 11"' 105 0 1~0 031 "100 073 011 101 123 123 105 115 102
114 131 040 114 111 123 124 111 116 107 040 10& 111 114 105 1C!3
056 073 001 000 073 105 010 "'00 122 125 116 040 044 123 107 110
101 124 040 124 110 111 123 040
0iH 00121 073 101 "63 000 073
120 117 111 116 124 040 127 105 040 1Z2 105 116 101 115 105 040
124 110 ies 040 101 123 123 105 115 102 114 131 ~40 103 117 115
115 101 11b 104 040 106 111 114 105 040 046 000 073 040 101 116
104 040 124 110 105 0'40 123 131 123 124 105 115 040 102 125 111
114 104 "IJ 0 103 117 115 115 101 1tb 104 040 10c 111 114 105 040
124 117 020 000 056 111 100 10& 040 101 040 013 011 133 061 061
054 002 060 135 1320 000 056 111 100 124 040 101 040 073 011 133
~61 061 054 0b2 06'4 135 001 ~00 073 125 057. 000 05b 111 106 10b
JI
Gan
062 000 i35 057 122
,,,o
0oi
"'"' 't ...t 't 'c;.r;i... ..."'.,,.,.,."1 4 ,,;;,.;i"l
IP'"' CJ
"' ... .,ai
""''
1os 075 122 123 130 101 123 115 056 103 115 104 073 052 054 122
121 130 1!32 114 10Q 056 103 115 uu 073 052 011 057 000 05& 111
1130 124 04tl 101 040 120 111 120 12140 133 061 061 054 062 064 135
057 122 105 075 122 123 130 101 123 115 056 103 115 104 073 052
054 122 123 130 102 114 104 £1J56 103 115 104 073 052 000 077 000
aso 101 123 113 040 132 040 104 111 104 040 131 117 125 040 101
116 101 "40 117 116
127 ..t • 1 c>a. t.. t °' ~40
066 113 040 127 117
115 101 131 040 107

.. ·- ....

040 101
115 4.. 1 7

~40

101
105 fl II'"'I.Ifl
123 072 000
105 124 ~40 101 123
124 111 11b 107 123 040
125 040 104 U 1 122 105
kl73 000 073 rut 124 110
116 124 105 122 040 050
116 117 121.J 110 105 122
;) ;)

1(,1

12'4

"'""

• "' t

f".I

I'll

• "lr

B-29

,.. L ·4

~04

~~,

~;;)'t

• • 1".11

• l'I.

lo;,J

OUM" OF OP01[200,200]SYSGEN,CMDJ15 •FILE ID 7157,3514610
VIRTU~~

000000
000020
0000q0

000060
000100

000120
000140
000160

000200
000220

000240
0002b0
000300
000320
000340
0003b0
000400
000"120

000440
000460
000500
000520

000540
000560

12100000
000020
000b40
000bb0

000700
000120
000740
0007&0

BLOCK 0,000004 • SIZE 512, BYTES

11b 123 127 105 122 040 12'4 110 105 040 123 131 123 107 105 11&
121 125 105 123 124 111 117 116 123 040 124 117 040 131 117
125 122 040 123 101 124 111 123 106 101 103 124 111 117 no 040
020 000 05b 111 106 124 040 132 040 056 107 117 124 117 040 061
068 k)00 01'1 ta00 ~73 111 074 ~HJ 073 040 127 105 040 127 111 11 '4
114 ~lf 0 105 130 111 12/l 040 1lb 117 127 040 123 117 040 124 110
1('1 124 '140 131 117 125 040 115 101 131 040 122 105 123 124 101
122 124 040 124 110 111 123 "J40 103 117 115 115 101 116 104 040
113b 111 114 105 067 000 073 ~40 106 122 117 115 040 124 110 105
102 105 107 111 11& 116 111 llb 107 05& 01.J0 124 110 111 123
~"'*'
0
41d 121 111 11" 114 040 101 114 114 117 127 040 101 040 103 114
105 101 ltb 040 125 120 040 117 106 040 124 110 105 122 070 000
an b40 104 111 123 113 040 101 1lb 10" 040 101 049 11b 105 127
122 125 Ub 040 117 106 1'140 123 107 116 040 124 117 040 123
1"S 114 1135 103 12tf 01~0 12" \10 105 040 120 122 117 120 105 122
04J 117 120 124 111 117 116 123 022 000 073 0U 100 117 122 040
131 117 125 122 k'40 123 131 123 12'1 105 115 056 001 000 073 040
a12 b00 Id Sb 107 117 124 117 Pl40 12'61 "'60 060 0b0 0~6 000 050 061
ao0 060 072 073 ~37 000 073 A40 llb 117 127 12140 127 105 040 101
123 123 1135 us 102 114 105 V!40 12~ 110 105 0a0 105 130 us 103
125 124 111 126 105 01.10 001 "100 073 124 ~27 000 056 111 106 1121&
040 101 040 123 105 124 040 "157 125 111 103 075 133 0&1 061 054
002 000 135 k'H~0 027 000 050 111 100 124 040 101 040 123 105 124
040 057 125 111 103 075 133 ~61 0b1 054 062 064 135 073 013 000
115 101 1e3 040 10El 122 123 130 101 123 115 000 001 000 073 10&
ao2 000 ld73 040 116 117 127 ~40 127 105 040 102 125 111 114 104
04~ 12t1 110 105 040 103 117 t16 103 101 124 105 116 101 124 105
1 "4 040 117 102 112 105 103 124 040 115 117 104 125 114 105 040
Ub 111 114 105 024 000 073 t'J40 10b 117 122 040 124 110 105 040
105 130 us 103 125 124 111 \2b 105 056 001 00e 073 104 024 000
120 111 120 0q0 122 123 130 001 0b1 115 056 117 102 123 075 052
05b 117 1"2 112 02b 000 120 111 120 040 056 117 102 112 057 122
040

"""

B-30

APPENDIX C
RSX-llM PRINT SPOOLER TASK

The RSX-llM Print Spooler task (PRT ... ) provides a
means
of
eliminating contention for the system line printer. Rather than
waiting for the line printer to become available, a task directs the
output intended for the line printer to a disk file. The task issues
a Send Data directive to the print spooler, placing a data block,
which identifies the file to be spooled, in the print spooler queue.
A Request directive then is issued by the task to activate the print
spooler, in case it is not already active. All files identified in
the print spooler queue are printed in a first in - first out (FIFO)
order.

C.l

RECEIVE QUEUE OPERATION

The standard method of placing a user file in the print spooler
receive queue (and requesting its execution) is via the PRINT$ macro
call, which is described in the RSX-11 I/O Operations Reference
Manual.
Files are spooled in this same manner by the RSX-llM
utilities which support the spool (/SP) option.
Each entry in the
print
spooler receive queue consists of a 13-word data block
containing the file-related information illustrated in Figure C-1.

C.2

TEXT REQUIREMENTS

The print spooler task prints ASCII text with a maximum line length of
132 bytes.
It will properly handle files with all modes of FCS
carriage control (i.e., standard, embedded and FORTRAN).

C-1

RSX-llM PRINT SPOOLER TASK

WORD
Filename

RADIX-50

File type in RADIX-50

File version (binary)

Device name in ASCII

Unit number (binary)

File

10
11

Directory ID

12
13

Figure C-1
PRT Send Data Buffer Format

C.3

TASK BUILD INFORMATION

The print spooler task must be built during an RSX-llM system
generation because the task image file (PRT.TSK) is not distributed on
the standard release kits. Normally, the print spooler is built to
delete all files which have been spooled, but the print spooler build
file can be edited during system generation to disable the automatic
delete feature.
When the print spooler is built without automatic
delete, spooled files are retained after printing. If the system has
a deleting print spooler, all spooled files are deleted after
printing. Therefore, the user should know whether or not the system
currently running has a deleting print spooler before spooling files.
The print spooler employs double buffering to increase

C-2

throughput

RSX-llM PRINT SPOOLER TASK
the line printer. However, when the print spooler is checkpointable
{the default from the build file),
the Executive limits the print
spooler to one outstanding I/O operation, thus effectively reducing it
to single buffering.
To effectively use the double
buffering
capability
of the print spooler,
it must e1tner be built as
noncheckpointable during system generation, or installed in the system
as noncheckpointable.
However, the print spooler should not be made
noncheckpointable if this will adversely effect the execution of other
tasks in the same partition.
See the RSX-llM System
generation information.

C.4

Generation

Manual

for

detailed

system

PRT ERROR MESSAGES

All error messages issued by PRT are sent to the console terminal
pseudo-device CO:. The error messages have the following format:

via

PRT -- text
In all but the receive failure error, the messages supply information
that identifies the sender task and the file in question. All PRT
errors are fatal;
upon error detection, printing of the input file is
terminated, and a clean up/restart procedure is entered.
In the case of the receive failure error,
the sender and file
information are unavailable.
Furthermore, PRT does not attempt to
dequeue additional spool requests because of the nature of this error
condition.
Instead, PRT exits causing its receive queue to be purged
by the system.
RECEIVE FAILURE, d. -- TASK EXITING
Description
The Receive Data or Exit directive failed while attempting to
obtain the next file specifier from the queue. The system error
code {d.) is printed to identify the error.
NO DEVICE NAME - SENDER: task FILE: filename.typ;ver
Description
The dequeued print request did not contain a device name.
NO FILE ID - SENDER: task FILE: filename.typ;ver
Description
The dequeued print request did not contain a file ID.

C-3

RSX-llM PRINT SPOOLER TASK
OPEN FAILURE INPUT FILE - SENDER: task FILE: filename.typ;ver, d.
Description
The specified file could not be opened.
conditions may exist:

One

the

following

The file is protected against access for read privileges.

A problem exists on the physical device (e.g., device
down) .

The volume is not mounted.

The specified file directory does not exist.

The named file does not exist in the specified directory.

The file is already deleted.

The system error code (d.)

cycled

is printed to identify the failure.

ATTACH FAILURE - SENDER: task FILE: filename.typ;ver, d.
or
DETACH FAILURE - SENDER: task FILE: filename.typ;ver, d.
Description
The line printer could not be attached/detached
(i.e.,
system
does not contain a line printer).
The system error code (d.) is
printed to identify the error.
PRINT ERROR - SENDER: task FILE: filename.typ;ver, d.
Description
The

A Queue I/O request to the line printer has failed.
error code (d.) is printed to identify the error.

system

I/O ERROR INPUT FILE - SENDER: task FILE: filename.typ;ver, d.
Description
An error was detected while reading the input file.
following conditions may exist:

One

A problem exists on the physical device (e.g., device
down) .

Length of the text line is greater than 132 bytes.

File is corrupted or the format is incorrect.

The system error code (d.)

cycled

is printed to identify the error.

C-4

the

INDEX
Aborting VFY, restrictions when,
8-1
Access modes, text, 5-5
Access warning messages, file,
5-9, 5-58
ADD AND PRINT command, 5-15
ADD command, 5-15
ALT Mode key, 5-20
APPEND command, 2-7
ASCII mode switch, 4-3
/AS switch, 4-3
Asterisk convention, wild cards,
2-4

Base block address switch, specify I 4-3
Basic EDI commands, 5-13
Basic EDI operation and commands,
5-10
/BA switch, 4-3
BEGIN command, 5-36
Block address switch, specify
base, 4-3
Block command, 5-25
Block mode, 5-5
Block mode, line-by-line vs., 5-6
Block switch, logical, 4-4
Blocks, deletion of multiply
Blocks, elimination of free, 8-8
Blocks, recovering lost, 8-9
Blocks switch, specify first and
last, 4-3
/BL switch, 4-3
BOTTOM command, 5-36
Buffer capacity exceeded, 5-53
/BY switch, 4-4
Byte mode switch, 4-4

Carriage return, use of, 5-7
Cassette directory listing, 3-18
Cassette file formats, 3-5
Cassette support, FLX, 3-5
Cassette support, multi-volume,
3-9
CHANGE command, 5-15
Changing control mode, 5-4
Character erase (RUBOUT) , 5-7
Check, validity, 8-5
CLOSE AND DELETE command, 5-51
CLOSE command, 5-51
Close operation commands, EDI,
5-50
CLOSES command, 5-51
/CO, COMPRESS switch, 7-7
Combining library functions, 7-26

Command,
ADD, 5-15
ADD AND PRINT, 5-15
APPEND, 2-7
BEGIN, 5-36
BLOCK, 5-25
BOTTOM, 5-36
CHANGE, 5-15
CLOSE, 5-51
CLOSE AND DELETE, 5-51
CLOSES, 5-51
CONCATENATION CHARACTER, 5-25
COPY, 2-8
CTRL/Z, 1-2, 5-16
DEFAULT, 2-12
DELETE, 2-13, 5-16
DELETE AND PRINT, 5-17
END, 5-36
ENTER, 2-15
ERASE, 5-42
EXIT, 5-18
EXIT AND DELETE, 5-52
FILE, 5-32
FIND, 5-37
FORM FEED, 5-43
FREE, 2-16
IDENTIFY, 2-16
INSERT, 5-18
KILL, 5-52
LINE CHANGE, 5-43
LIST, 2-17
LIST ON PSEUDO-DEVICE, 5-44
LIST ON TERMINAL, 5-43
LOCATE, 5-19
MACRO, 5-44
MACRO CALL, 5-45
MACRO EXECUTE, 5-46
MACRO IMMEDIATE, 5-47
MERGE I 2-8
NEXT I 5-19
NEXT PRINT, 5-20
OLDPAGE, 5-37
OPENS, 5-26
OUTPUT, 5-26
OVERLAY, 5-47
PAGE, ~-38
PAGE FIND, 5-38
PAGE LOCATE, 5-39
PASTE, 5-48
PRINT, 5-20
PROTECT, 2-21
PURGE, 2-24
READ, 5-32
REMOVE, 2-25
RENAME, 2-26
RENEW I 5-22
RETYPE, 5-22
SAVE, 5-48
SEARCH AND CHANGE, 5-39
SELECT PRIMARY, 5-27

Index-1

Command (cont.),
SELECT SECONDARY, 5-28
SIZE, 5-29
SPOOL, 2-28
TAB, 5-29
TOP, 5-40
TOP OF FILE, 5-22
TYPE, 5-49
UNLOCK, 2-29
UNSAVE, 5-50
UPDATE, 2-30
UPPER CASE, 5-30
VERIFY, 5-31
WRITE, 5-33
Command, concatenation character,
5-25
Command conventions, EDI, 5-7
Command format conventions, 1-6
Command level informational and
error messages, 5-9, 5-52
Command string,
DMP, 4-2
FLX, 3-2
LBR, 7-5
PIP, 2-1
VFY, 8-2
Command strings, utility, 1-4
Command switches and subswitches,
PIP, 2-3
Command switches, VFY, 8-4
Commands,
EDI close operation, 5-50
input/output, 5-31
line pointer (locative), 5-34
PIP, 2-6
setup, 5-23
text modification and manipulation, 5-40
Compress switch, (/CO), 7-7
Concatenation character command,
5-25
Constants, search string, 5-8
Constraints, LBR, 7-27
Control characters, SLP edit, 6-6
Control mode, changing, 5-4
Control modes, EDI, 5-4
Control switches, file, 3-15
Control switches, SLP output, 6-5
Convention, wild cards, asterisk,
2-4
Conventions,
command format, 1-6
EDI command, 5-8
system-wide, 1-8
terminal, 5-7
COPY command, 2-8
Creating a file, 5-10
Creating an indirect file, 6-8
/CR, CREATE switch, 7-9
Create switch (/CR), 7-9
CTRL/Z command, 5-16

/DE, DELETE switch, 7-11
DEFAULT command, 2-12
Defaults in file specifiers,
EDI, 5-3
LBR, 7-5
PIP, 2-2
SLP, 6-3
VFY, 8-3
DEFAULT switch, 7-12
DELETE AND PRINT command, 5-17
DELETE command, 2-13, 5-16
Delete, files marked for, 8-7
Delete global switch (/DG), 7-13
DELETE switch (/DE), 7-11, 8-9
Deleting a file, 8-8
Deleting DOS files, 3-3
Deleting RT files, 3-4
Deletion of multiply allocated
blocks, 8-8
/DF, DEFAULT switch, 7-12
/DG, DELETE GLOBAL switch, 7-13
Directory listings,
DOS, 3-3
RT, 3-3
Directory manipulation,
DOS volume, 3-3
RT volume, 3-3
DMP,
file dump utility, 4-1
initiating, 4-2
DMP command strings, 4-2
DMP error messages, 4-5
DMP switches, 4-2
DOS directory listings, 3-3, 3-18
DOS files, deleting, 3-3
DOS-11 volumes, initializing, 3-3
DOS volume directory manipulation,
3-3

EDI,
command conven_tions, 5-7
control modes, 5-4
default file specifiers, 5-3
error messages, 5-52
error reporting, 5-9
initiating, 5-2
line text editor, 5-1
modes, 5-4
operation and commands, basic,
5-10
preparing to run, 5-1
text access, 5-5
using, 5-1
EDI commands,
basic, 5-13
close operations, 5-50
extended, 5-23
input/output, 5-31
line pointer control (locative),
C:: __ ")A
..J

Index-2

..J'"t

EDI commands (cont.),
setup, 5-23
text modification and manipulation, 5-40
Edit commands, SLP, 6-6
Edit control characters, SLP, 6-6
Edit mode, entering text in, 5-11
Edit modes, EDI, 5-4
Editing a file, 5-11
Editing examples, SLP, 6-9
Editing session, sample, 5-23
Elimination of free blocks, 8-8
END command, 5-36
ENTER command, 2-15
Entering text in edit mode, 5-11
Entering text in input mode, 5-11
Entering text into a file, 5-11
Entry point table, 7-2
ERASE command, 5-42
Error codes,
PIP, 2-41
VFY, 8-16
Error messages,
DMP, 4-5
EDI I 5-52
fatal, 5-10, 5-62
FLX, 3-20
LBR, 7-27
PIP, 2-31
SLP, 6-12
VFY, 8-14
Error messages, command level
informational and, 5-9, 5-52
Error messages requiring EDI
restart, 5-9, 5-59
Error reporting,
EDI, 5-9
file I 8-6
Exceeded buffer capacity, 5-53
EXIT

&.~D

DELETE

--~~--;:J
\,.,UllULICUJ.U. 1

C'._f:'.")
J
- J,;;..

EXIT command, 5-18
Extended EDI commands, 5-23

Fatal error messages, 5-10, 5-62
File access warning messages, 5-9,
5-58
File, creating a, 5-10
File, deleting a, 8-8
File, entering text into a, 5-11
File, editing a, 5-11
File, restoring a, 8-7
File access warning messages, 5-9,
5-58
FILE command, 5-32
File control switches, 3-15
File dump utility (DMP) , 4-1
File error reporting, 8-6
File formats, cassette, 3-5
File header switch, 4-4
File identification option, 2-5

File name, 1-5
File option switches, LBR, 7-7
Filespec, 5-3
File specifiers,
defaults in LBR, 7-6
defaults in PIP, 2-2
defaults in SLP, 6-3
defaults in VFY, 8-3
list of, 2-2
File transfer program (FLX), 3-1
File transfers, 3-2
File structure verification
utility (VFY), 8-1
Files,
deleting, DOS, 3-3
deleting, RT, 3-4
format of library, 7-1
indirect, 1-7, 6-8
library, 7-28
marked-for-delete, 8-7
output, 5-6
SLP output, 6-4
text, 5-6
FIND command, 5-37
FLX,
cassette support 1 3-5
command string 1 3-2
error messages, 3-20
file transfer program, 3-1
initiating, 3-2
input files, 3-10
output files, 3-9
paper tape support, 3-10
switches, 3-11
Format conventions,
command, 1-6
Format of library files, 7-1
Format mode switches, 3-11
Formats, cassette file, 3-5
FORM FEED command, 5-43
Free blocks, elimination of, 8-8
FREE cornrnand, 2-16
FREE switch (/FR), 8-12
/FR, FREE switch, 8-12
/FU,/LE,/LI, list switches, 7-15

/HD switch, 4-4
Header,
library, 7-2
module, 7-4
Header switch, file, 4-4

/ID switch, 4-4
Identification switch, 4-4
IDENTIFY command, 2-16
Indirect file, creating an, 6-8
Indirect files, 1-7, 6-8
Indirect files, using, 6-9

Index-3

Inflespc, 1-4
Informational and error messages,
command level, 5-9, 5-52
/IN, INSERT switch, 7-14
Initializing,
DOS-11 volumes, 3-3
RT-11 volumes, 3-4
Initiation of installed utilities,
1-2
Initiation of uninstalled
utilities, 1-3
Initiating,
DMP, 4-2
EDI, 5-2
FLX, 3-2
LBR, 7-5
PIP, 2-1
RSX-llM utilities, 1-2
SLP, 6-2
VFY, 8-2
Input and secondary files, 5-7
Input file, FLX, 3-10
Input mode, entering text in, 5-11
Input/Output commands, 5-31
INSERT command, 5-18
Insert switch (/IN) , 7-14
Installed utilities, initiation
of, 1-2

KILL command, 5-52

/LB switch, 4-4
LBR command string, 7-5
LBR constraints, 7-27
LBR error messages, 7-27
LBR file option switches, 7-7
LBR, initiating, 7-5
LBR, librarian utility program,
7-1
/LE,/LI,/FU, list switches, 7-15
Librarian utility program {LBR),
7-1
Library files, 7-28
Library files, format of, 7-1
Library functions, combining, 7-26
Library header, 7-2
/LI,/LE,/FU, list switches, 7-15
/LI, LIST switch, 8-12
Line-by-line mode, 5-5
Line-by-line vs. block mode, 5-6
LINE CHANGE command, 5-43
Line delete {CTRL/U) , 5-7
Line pointer control {locative)
commands, 5-34
Line text editor {EDI), 5-1
LIST command, 2-17
LIST ON PSEUDO-DEVICE co:rnmand;

LIST ON TERMINAL command, 5-43
LIST switch (/LI), 8-12
List switches (/LI,/LE,/FU), 7-15
LOCATE command, 5-19
Locative commands, line pointer,
5-34
Logical block switch, 4-4
/LO, LOST switch, 8-12
Lost blocks, recovering, 8-9
LOST switch (/LO), 8-12

MACRO CALL command, 5-45
MACRO command, 5-44
MACRO EXECUTE command, 5-46
MACRO IMMEDIATE command, 5-47
/MD switch, 4-4
Memory dump switch, 4-4
MERGE command, 2-8
Mode,
block, 5-5
changing control, 5-4
line-by-line, 5-5
Mode switch, ASCII, 4-3
Mode switch, byte, 4-4
Mode switches, format, 3-11
Mode switches, transfer, 3-12
Modes, EDI control, 5-4
Module header, 7-4
Module name table, 7-4
Multiply-allocated blocks,
deletion of, 8-8
Multi-volume cassette support, 3-9

NEXT command, 5-19
NEXT PRINT command, 5-20
Normal operation, VFY, 8-2

OLDPAGE command, 5-37
OPENS command, 5-26
Outflespc, 1-4
OUTPUT command, 5-26
Output control switches, SLP, 6-4
Output files,
EDI, 5-7
FLX, 3-10
SLP, 6-4
OVERLAY command, 5-47

PAGE command, 5-38
PAGE FIND command, 5-38
PAGE LOCATE, 5-39
Paper tape support, FLX, 3-10
PASTE command,

5-44

Index-4

5-48

Peripheral Interchange Program
(PIP) , 2-1
PIP commands, 2-6
PIP
2-1
PIP command switches and subswitches, 2-3
PIP error codes, 2-41
PIP error messages, 2-31
PIP, Peripheral Interchange Program, 2-1
Preparing to run EDI, 5-1
Preparing to run SLP, 6-1
PRINT command, 5-20
PROTECT command, 2-21
PURGE command, 2-24

/RC, READ CHECK switch, 8-13
READ CHECK switch (/RC) I 8-13
READ command, 5-32
REBUILD switch (/RE), 8-11
Recovering lost blocks, 8-9
REMOVE commqnd, 2-25
RENAME command, 2-26
RENEW command, 5-22
REPLACE switch (/RP), 7-17
global format, 7-17
local format, 7-18
/RE, REBUILD switch, 8-11
Restart, error messages requiring
EDI, 5-9, 5-59
Restoring a file; 8-7
Restrictions,
while running VFY, 8-1
when aborting VFY, 8-1
RETYPE command, 5-22
/RP, replace switch, 1-L1
RSX-llM utilities, initiating, 1-2
RT directory listing, 3-19
RT directory listings, 3-3
RT files, deleting, 3-4
RT volume directory manipulation,
3-3
RT-11 volumes, initializing, 3-4
Run EDI, preparing to, 5-1
Run SLP, preparing to, 6-1
Running VFY, restrictions while,
8-1

Sample editing session, 5-23
SAVE command, 5-48
SEARCH AND CHANGE command, 5-39
Search string constants, 5-8
Secondary files, input and, 5-7
SELECT PRIMARY command, 5-27
SELECT SECONDARY command, 5-28
Selective search switch (/SS) ,
7-23
Setup commands, 5-23

SIZE command, 5-29
SLP,
capabilities, 6-1
edit control characters, 6-7
editing examples, 6-10
environment, 6-1
error messages, 6-12
initialization, examples of, 6-3
initiating, 6-2
output control switches, 6-4
output files, 6-4
restrictions, 6-2
source language input program,
6-1
startup, 6-:2
Source language input program
(SLP) , 6-1
Specify base block address switch,
4-3
Specify first and last blocks
switch, 4-3
SPOOL command, 2-28
Spool switch (/SP) , 7-23
/SP, spool switch, 7-23
Squeeze switch (/SZ), 7-24
Startup, SLP, 6-2
String,
DMP command, 4-2
FLX command, 3-2
UTILITY command, 1-4
VFY command, 8-2
Subswitches, PIP command switches
and, 2-3
Switch,
/AS, 4-3
ASCII mode, 4-3
/BA, 4-3
/BL, 4-3
/BY, 4-4
byte mode, 4-4
/CO, COMPRESS, 7-7
/CR, CREATE I 7-9
/DE, DELETE, 7-11, 8-9
/DF, DEFAULT, 7-12
/DG, DELETE GLOBAL, 7-13
file header, 4-4
/FR, FREE, 8-12
/HD, 4-4
/ID, 4-4
Identification, 4-4
/IN, INSERT, 7-14
/LB I 4-4
/LI, LIST, 8-12
logical block, 4-4
/LO, LOST, 8-12
/MD, 4-4
memory dump, 4-4
/RC, READ CHECK, 8-13
/RE, REBUILD, 8-11
/RP, REPLACE, 7-17
specify base block address, 4-3

Index-5

Switch (cont.),
specify first and last blocks,
4-3
/SP, SPOOL, 7-23
/SS, SELECTIVE SEARCH, 7-23
/SZ, SQUEEZE, 7-24
/UP, UPDATE, 8-10
Switches (/LI,/LE,/FU), list, 7-15
Switches and subswitches, PIP
command, 2-3
Switches,
DMP, 4-2
file control, 3-15
FLX, 3-11
format mode, 3-11
LBR file option, 7-7
transfer mode, 3-13
VFY command, 8-4
System-wide conventions, 1-8

TAB command, 5-29
Terminal conventions, 5-7
Text access modes, 5-5
Text files, 5-6
Text modification and manipulation commands, 5-40
TOP commands, 5-40
TOP OF FILE commands, 5-22
Transfer mode switches, 3-13
Transfers, file, 3-2
Truncated output file, utilizing
a, 5-62
TYPE command, 5-49

Validity check, 8-5
VERIFY command, 5-31
VFY,
command string, 8-2
command switches, 8-4
error codes, 8-16
error messages, 8-14
file structure verification
utility, 8-1
initiating, 8-2
normal operation, 8-2
Volume directory manipulation, RT,
3-3
Volumes, initializing DOS-11, 3-3
Volumes, initializing RT, 3-4

Warning messages, file access,
5-9, 5-58
Wild cards, asterisk convention,
2-4
WRITE command, 5-33

Uninstalled utilities, initiation
of, 1-3
UNLOCK command, 2-29
UNSAVE command, 5-50
UPDATE command, 2-30
UPDATE switch (/UP), 8-10
UPPER CASE command, 5-30
Use of carriage return, 5-7
Use of*, 5-8
User identification code, 1-5
Using EDI, 5-1
Using indirect files, 6-9
Utilities, initiating RSX-llM, 1-2
Utility command string, 1-4
Utilizing a truncated output file,
5-62

Index-6

RSX-llM Utilities Procedures
Manual
DEC-11-0MUPA-B-D
READER'S COMMENTS
NOTE:

This form is for document comments only. Problems
with software should be reported on a Software
Problem Repcrt (SPR) form

Did you find errors in this manual?

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

Is there sufficient documentation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.

Assembly language programmer

Higher-level language programmer

0
0

Occasional programmer (experienced)
User with little programming experience

Student programmer

Non-programmer interested in computer concepts and capabilities

CitY~~~~~~~~~~~~~~State~~~~~~~Zip Code~~~~~~~

or
Country
If you require a written reply,

please check here.

-----------------------------------------------------------Fold l-lere-----------------------------------------------------------~

·---------------------------------------------- Do Not Tear - Fold l-lere and Staple -----------------------------------------------

FIRST CLASS
PERMIT NO. 33
MAYNARD, MASS.
BUSINESS REPLY MAIL
:\'O POSTAGE STAMP NECESSARY IF MAILED IN THE UNITED STATES

Postage will be paid by:

Software Communications
P. 0. Box F
Maynard, Massachusetts 01754

digital equipment corporation

Pri~tcd

ir US.A.