Digital PDFs

AA-EZ12B-TC

August 1990

338 pages

Original

171MB

Document:	RSTS/E System Users Guide
Order Number:	AA-EZ12B-TC
Revision:	0
Pages:	338
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V10/AA-EZ12B-TC_RSTS_E_System_Users_Guide_Aug1990.pdf

OCR Text

- RSTS/E System User's Guide
Order Number: AA-EZ12B-TC
August 1990

wore

RSTS/E System User's Guide
Order Number: AA-EZ12B-TC
August 1990

This manual contains general information about RSTS/E, provides rules for using Del on
RSTS/E, and describes commands for file, system and programming operations.

Operating System and Version: RSTS/E Version 10.0
Software Version:

digital equipment corporation
maynard, massachusetts

RSTS/E Version 10.0

August 1990
The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation
assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used
or copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment not supplied
by Digital Equipment Corporation or its affiliated companies.
Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.

© Digital Equipment Corporation 1990. All rights reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document requests
the user's critical evaluation to assist in preparing future documentation. The following are
trademarks of Digital Equipment Corporation:
ALL-IN-1
DECICMS
DECdx
DEC/FMS-11
DECmail
DECnet
DECnetiE
DECSA
DECserver
DECsystem-10
DECSYSTEM-20
DECUS
DECworld
DELUA
DEQNA

DEUNA
DIBOL
EDT
lAS
LA
LN01
Micro/RSX
OS/8
PDP
PDP-11
PDT
Q-BUS
RMS-11
RSTS

RSX
RT
RT-11
TOPS-10
TOPS-21
ULTRIX
UNIBUS
VAX
VAXmate
VMS
VT
WPS-PLUS
Rainbow

~DmDDmD'"

IBM is a registered trademark of International Business Machines Corporation.
RMS is a trademark of American Management Systems, Inc.

Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1
1.1

Getting Started with RSTS/E
Using Your Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Your Project-Programmer Number . . . . . . . . . . . . . . . . . . . . . . . . . .
Your Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using the Terminal (CTRL, DELETE, RETURN Keys) ........... .
Beginning a Terminal Session: HELLO or LOGIN .............. .
The System Command Environment ....................... .
Other Command Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 .1.1
1.1.2
1.1.3
1.1.4
1.1.5
1.1.6
1.1.7

1-1
1-1
1-2
1-2

1-3
1-6
1-8
1-8

1.2.1
1.2.2
1.2.3

Echo on Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Login Command Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Getting Information About Commands: HELP ................. .
Ending a Terminal Session: LOGOUT or BYE ................ .

1-9
1-9
1-10
1-12

1.3

Using DCL Command Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-13

1.4

Editing and Recalling Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Line Editing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2
Command Recall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.3
RECALL Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.4
Command Line Editing and Recall Keys .................... .
1.4.5
Editing Multiline Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-14
1-14
1-14
1-16

Maintaining Flies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Accounts, Directories, and Files . . . . . . . . . . . . . . . . . . . . . . . . . . .
Putting Files into Your Directory .......................... .
Displaying Your Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rle Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rle Names and Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.5.1
Protection Codes . . . . . .. . . . . . . . . . . . . . . . . . . . . . .
1.5.5.2
Wildcards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Exceeding Your Disk Quota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.6

1-19
1-19

1.6

Running a Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-26

1.7

Using DECnet/E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.1
Displaying Network Status: SHOW NETWORK ................ .
1.7.2
Using the Network: SET HOST . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.3
SET HOST Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-26
1-28
1-28
1-29

1.2

(

1 .4.1

1.5

1.5.1
1.5.2
1 .5.3
1.5.4
1.5.5

(

1-18
1-18

1-20
1-20
1-21
1-22
1-24
1-25
1-25

iii

Chapter 2
2.1

2.2

2.3

Chapter 3

Using RSTS/E Commands and Command Procedures
Understanding Command Formats ............................... .
2.1 .1
Entering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2
Continuing Commands on More than One line . . . . . . . . . . . . . . . . .
2.1.3
Entering Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.4
Abbreviating Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5
Abbreviating Command Names . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.6
Abbreviating Parameters, Qualifiers, and Qualifier Arguments ...... .

2-1
2-4
2-4
2-5
2-5
2~
2~

Entering File Specification lists ................................ .
2.2.1
Entering Entry Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.2
Entering Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3
Determining Qualifier Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.4
Entering Qualifier Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.5
Entering Output File Qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.6
Entering Uppercase, Lowercase, and Nonalphanumeric Characters .. .
2.2.7
Entering Dates and Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.8
The /BEFORE, /SINCE, and /AFTER Qualifiers . . . . . . . . . . . . . . . . .
2.2.9
Absolute Date and lime Formats . . . . . . . . . . . . . . . . . . . . . . . . . .
Combinations of Absolute Dates and limes . . . . . . . . . . . . . . . . . . .
2.2.10
2.2.11
Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.12
Relative Date and Time Formats . . . . . . . . . . . . . . . . . . . . . . . . . .

2-7
2-7
2-8
2-8
2-9
2-11
2-11
2-11
2-12
2-12
2-13

Using Command Procedures ................................... .
2.3.1
Creating Command Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2
Formatting Command Procedures . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3
Executing Command Procedures . . . . . . . . . . . . . . . . . . . . . . . . . .

2-13
2-14
2-15
2-15

2~
2~

WORKING WITH FILES

3.1

Creating and Modifying Text Files ............................... .
3.1.1
CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1.2
EDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-2
3-2
3-5

3.2

Displaying File Names and Files ................................ .
3.2.1
DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2
TYPE ............................................ .

3-9
3-9
3-16

3.3

Deleting Files: DELETE ...................................... .

3-19

3.4

Copying, Renaming, and Appending Files ......................... .
3.4.1
COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.3
APPEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-23
3-23
3-32
3-36

3.5

Backing Up and Restoring Files ................................ .
3.5.1
BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2
BACKUP/DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.3
RESTORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.4
RESTORE/DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-39
3-39
3-44
3-47
3-53

3.6

Sorting Files and Merging Sorted Files ........................... .
3.6.1
SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2
MERGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-56
3-56
3~2

3.7

Comparing Files: DIFFERENCES ................................ .

3-68

3.8

Allowing Access to Files ..................................... .
3.8.1
Using Protection Codes ............................... .
3.8.2
SET PROTECTION .................................. .

3-71
3-71
3-74

3.9

Setting File Characteristics: SET FILE ............................ .

3-77

Chapter 4

System and Account Operations

4.1

SHOW ................................................... .

4-1

4.2

System and Account Status ................................... .
4.2.1
Attached and Detached Jobs ............................ .
SHOW USER ...................................... .
4.2.2
4.2.3
SHOW JOB ....................................... .
4.2.4
CTRUT .......................................... .
SHOW PORT ...................................... .
4.2.5
SHOW SYSTEM .................................... .
4.2.6
SHOW ACCOUNT ................................... .
4.2.7

4-4
4-6
4-8
4-9
4-10
4-11
4-13
4-14

4.3

SET ..................................................... .
4.3.1
SET PASSWORD ................................... .
SET PROMPT ...................................... .
4.3.2

4-16
4-17
4-19

4.4

REQUEST ................................................ .

4-20

(
Chapter 5
5.1

Displaying and Setting Terminal Characteristics ..................... .
5.1.1
SHOW TERMINAL ................................... .
5.1.2
SET TERMINAL .................................... .

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

5.2

Creating a Log File of a Terminal Session ......................... .
5.2.1
OPENIlOG_FILE .................................... .
CLOSE/LOG_FILE ................................... .
5.2.2
SET LOG_FILE ..................................... .
5.2.3

5--11
5--11
5--14
5--15

Chapter 6
6.1

6.2

6.3

(

Terminal Status and Operations

Working with Devices
Working with Physical Devices ................................. .
6.1.1
Allocating Devices ................................... .
6.1.2
Assigning and Allocating Devices ......................... .
6.1.3
Device Independence ................................. .

6-1

6-4
6-4
6-4

Working with Disks ......................................... .
6.2.1
The Public Disk Structure .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.2
Private Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4

Working with Magnetic Tapes .................................. .
6.3.1
Protecting Files on Tapes .............................. .
Tape Density ....................................... .
6.3.2
ANSI and DOS Format ................................ .
6.3.3

6-6
6-6
6-6
6-6

6-5
6-5

6.4

Physical Device Commands ................................... .
ALLOCATE ........................................ .
DEALLOCATE ...................................... .
6.4.2
MOUNT .......................................... .
6.4.3
6.4.4
INITIALIZE ........................................ .
DiSMOUNT ........................................ .
6.4.5
SHOW DEVICE, SHOW DEVICE/ALLOCATED, SHOW DISKS ..... .
6.4.6

6.4.1

6.5

Logical Names ............................................. .
Logical Names and Devices ............................ .
6.5.2
Systemwide and User Logicals . . . . . . . . . . . . . . . . . .......... .
6.5.3
Numbers of Logical Names ............................. .
6.5.4
How to Override Name Precedence ....................... .
6.5.5
ASSIGN .......................................... .
6.5.6
DEASSiGN ........................................ .

6.5.1

Chapter 7

6-10
6-11
6-14
6-16
6-17
6-18
6-18
6-19

6-19
6-19

6-20
6-23

Print/Batch Services
7-1

Specifying Print and Batch Entries .............................. .
7.1.1
Entry Number ...................................... .
7.1.2
Entry Specification ................................... .

7-2
7-2

7.2

Printing Files: PRINT ........................................ .

7-3

7.3

Submitting Entries for Batch Processing: SUBMIT ................... .

7-7

7.4

Displaying Print and Batch Queue Entries: SHOW ENTRY .............. .

7-10

7.5

Modifying a Print or Batch Queue Entry: SET ENTRY ................. .

7-14

7.6

Deleting a Print or Batch Entry from a Queue: DELETE/ENTRY .......... .

7-17

7.7

Displaying a Queue's Characteristics: SHOW QUEUE ................. .

7-18

7.1

Chapter 8

Program Development

8.1

Developing Programs on RSTS/E

8-1

8.2

Overview ................................................. .
8.2.1
Editing ........................................... .
8.2.2
Compiling ......................................... .
8.2.3
linking ........................................... .
8.2.3.1
Combining Modules .......................... .
8.2.3.2
Relocating Addresses ......................... .
8.2.4
Testing ........................................... .

8-2
8-2
B-3
B-3
B-4
B-4
B-4

The RT11 and RSX Tools ..................................... .
8.3.1
RTii-Based Programming .............................. .
8.3.2
RSX-Based Programming .............................. .

8-5
8-5

8.4

BASiC ................................................... .

8-7

8.5

CC ..................................................... .

B--8

8.6

COBOL .................................................. .

8-14

8.3

6-8
6-8

B-4

8.7

OIBOl ................................................... .

8-19

8.8

FORTRAN ................................................ .
8.8.1
FORTRAN/F77 ..................................... .
8.8.2
FORTRAN/FOR ..................................... .

8-21
8-22
8-25

8.9

MACRO .................................................. .

8-28

8.10

liNK .................................................... .
8.10.1
Overlaid Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.10.1.1
When You Can Use ISTRUCTURE ................ .
8.10.1.2
When Must You Use Overlays? .................. .
8.10.1.3
What Are Overlays? .......................... .
8.10.1.4
Rules for Constructing Overlays .................. .
8.10.1.5
The ISTRUCTURE Dialogue .................... .
The Memory Map File ................................ .
8.10.2
8.10.3
The Temporary Files Produced by LINK ..................... .

8-30
8-38
8-38
8-38
8-39
8-40
8-43
8-45
8-46

8.11

RUN .................................................... .

8-47

Appendix A

(

DCl Error Messages

A.1

Special Characters Used in Error Messages ........................ .

A-1

A.2

OCl Error Messages ........................................ .

A-2

Appendix B

More About Command Environments and RSTS/E File Specification

B.1

More About Command Environments ............................. .
B.1.1
Switching Between Command Environments ................. .
BASIC-PLUS Keyboard Monitor Commands .................. .
B.1.2
RT11 Keyboard Monitor Commands ....................... .
B.1.3
RSX Keyboard Monitor Commands ........................ .
B.1.4

B.2

More About The RSTS/E File Specification ......................... .
B.2.1
RSTS/E File Specification Switch ......................... .
IPROTECT Switch ................................... .
B.2.2
B.2.3
IFllESIZE Switch .................................... .
B.2.4
IClUSTERSIZE Switch ................................ .
IPOSITION Switch ................................... .
B.2.5
B.2.6
IMODE and IRONlY Switches ........................... .

B-6
8-7
8-7
8-7
B-8
8-9
8-10

GLOSSARY

Index

(

vii

Examples
8-1

Sample From A Memory Map File ................................ .

8-46

1-1

Executing System and User Login Files ............................. .

1-10

2-1

The COPY Command Format ................................... .

2-3

8-1

Outlining the Call Structure ..................................... .

8-39

8-2

A Simple Overlay in Memory .................................... .

8-40

8-3

Separate Paths in An Overlay Structure ............................. .

8-41

8-4

Allocating Space for Common Areas ............................... .

8-42

8-5

Overlay Structure Using Concatenated Files .......................... .

8-44

Figures

Tables
1-1

Special Function Keys on RSTS/E ................................ .

1-4

1-2

RSTS/E File Types ........................................... .

1-23

2-1

Terms Used in Command Formats ................................ .

2-2

Nonalphanumeric Characters .................................... .

2-10

3-1

Commands for File Operations ................................... .

3-1

3-2

IINITIALIZE and lOUT_LABEL Interaction During BACKUP ................ .

3-41

3-3

IINITIALIZE and lOUT_LABEL Interaction During RESTORE ............... .

3-50

3-4

File Protection Codes for Nonexecutable Files ........................ .

3-72

3-5

File Protection Codes for Executable Files ........................... .

3-72

3-6

Common File Protection Codes .................................. .

3-73

4-1

SHOW Command Options ...................................... .

4-2

SHOW USER and SHOW JOB Abbreviations ......................... .

4-1
4-5
4-16
6-1
6-2
6-17
7-1
7-12
7-13
8-1
8-5
8-32
B-2

4-3

SET Command Options ....................................... .

6-1

Commands for Devices and Logical Names .......................... .

6-2
6-3
7-1
7-2
7-3
8-1
8-2
8-3
B-1

B-2
B-3

RSTS/E Physical Device Names ................................. .
Abbreviations in SHOW DEVICE/ALLOCATED and SHOW DISKS Displays ..... .
Print/Batch Services Commands .................................. .
ISTATUS Keywords .......................................... .
VMS IBY_JOB_STATUS Synonyms ............................... .
Program Development Commands ................................ .
Program Development Commands for RT11 and RSX ................... .
Language Qualifier, Source Language, and Linker Relationship ............. .
BASIC-PLUS Commands ...................................... .
RT11 Com mands ............................................ .
RSX Commands ............................................ .

B-4
B-6

)

viii

Preface

Objectives
This manual describes the RSTSIE operating system and the use of the Digital
Command Language (DCL) on RSTSIE systems.
This manual describes commands for operations such as working with files,
getting information about the system and its devices, printing files and running
batch jobs, and developing programs. Note that this manual does not describe
commands which require privileges for you to use them; see the RSTS / E System
Manager's Guide for descriptions of privileged DeL commands.

Audience

(

Although some familiarity with computers is helpful, you do not need to be an
experienced computer user or programmer to use this manual.

Document Structure
The manual is divided into eight chapters and two appendixes:

(

Chapter 1

Describes the basics of the RSTSIE system and how to use it. It includes descriptions of the command environments, running a program,
and using DECnetlE. (DECnetIE allows you to communicate with other
computers.)

Chapter 2

Describes how to use commands interactively and introduces how to
use command procedures.

Chapter 3

Describes the RSTSIE commands used to create, display, edit, copy, and
compare files.

Chapter 4

Describes how to use DCL in day-to-day RSTSIE operations, such as
displaying system status and changing your password.

Chapter 5

Describes how to display and set your terminal characteristics, and
how to enable and disable terminal logging.

Chapter 6

Describes the devices available for your use on a RSTSIE system.

Chapter 7

Describes the commands in the RSTSIE PrintlBatch Services (PBS)
facility, used to submit files for print or batch processing.

Chapter 8

Describes the commands available for you to develop and run programs.

Appendix A

Lists error messages that RSTSIE displays when you enter a command
that RSTSIE cannot execute.

Appendix B

Contains information about the BASIC-PLUS, RSX, and RTll command environments. It also contains information about RSTSIE file
specification.

The manual also contains a glossary of RSTSIE and DeL terms.

Related Documents
To learn about editing text with the EDT editor, see the Introduction to the EDT
Editor and the EDT Editor Manual.

See the RSTS / E Guide to Writing Command Procedures for more information On
command procedures and their use.
For complete details on how to define and control SORT and MERGE operations,
see the PDP-ll SORT/MERGE User's Guide.
To get started with BASIC-PLUS-2 programming, read the Introduction to BASIC
Manual.

See the RSTS / E Documentation Directory for a description of the other manuals
in the RSTSIE documentation set.

Conventions
This manual uses the following symbols and conventions:
[ ]

Square brackets show the optional parts of a command in format
statements. For example:
DIRECTORY [file-specL ... ]]
The square brackets in this example indicate that you can include a file
specification ([file-spec)), or more than one ([, ... )), if you choose.
Square brackets also indicate an optional part of the command. For
example:
![NO]DELETE
This means you can type either !DELETE or INODELETE, depending
on the form of the qualifier you select.
Do not confuse the square brackets in command formats with the
square brackets in Project-Programmer numbers (PPNs), as in [52,20).
See Chapter 1 for a description.

Angle brackets surrounding text indicate a place holder for what the
system inserts when an error message occurs.

CtrllX

The control key, which you use in combination with another key. For
example, enter CtrlfU by holding down the Ctrl key and pressing the
keyboard key labeled "U." RSTSIE displays, or echoes, CtrlfU at your
terminal, as J\U.

<RET>

The key labeled Return on your terminal. You press the Return key to
complete lines and commands that the system will process.

this typeface

Information in this typeface indicates an example of computer/user
dialogue.

color

In examples, red characters indicate information that you enter into
the computer. Black characters represent data produced by the computer.

( I )

A vertical bar indicates a choice. For example:
ILOWERCASE=[INPUT I OUTPUT]
means you can enter ILOWERCASE=INPUT OR ILOWERCASE=OUTPUT.

bold

A term in bold lettering indicates that the term is defined in the
glossary at the end of this guide. The bold typeface appears only at the
initial usage of the term.

Summary of Technical Changes for RSTS/E V10.0
RSTSIE V10.O is a major release of the RSTSIE PDP-ll operating system. This
manual describes the following new features:
•

Extended logicals

•

Host initiated (Outbound) LAT

•

Command line editing and recall

•

Operator/Message Services (OMS)

(

Chapter 1

Getting Started with RSTS/E
This chapter introduces you to RSTS/E and contains information to help you
become familiar with using the system.
This chapter explains how to:

1.1

•

Use your account

Edit and recall your commands

Maintain files

•

Run a program

Use DECnetIE

Using Your Account
In order for you to use the computer, your system manager must assign you
an account number and password. The account number identifies you to the
system. The password is a precaution to keep unauthorized users from accessing
the system.
When you log in, the system displays a message at your terminal to confirm that
you are logged in to your account. The system may also display informational
messages.

1.1.1

Privileges
After you log in, you have access to all the RSTSIE facilities that your account
allows. Your system manager decides what privileges to give your account.
Like most users of your system, you will probably have sufficient privileges to
create, modify, copy, and delete your own files, as well as to change your own
password. Other users of your system may be granted additional privileges,
allowing them to perform operations such as:
•

Creating and deleting accounts

Adding commands to the system

Controlling the number of users on the system

•

Saving user files in case of accidental damage

Ii>

Shutting down the system

•

Reading and modifying other users' files

Getting Started with RSTS/E

1-1

This manual describes only those commands, command qualifiers or switches,
and functions that can be used by most system users, that is, users who do not
have privilege to affect accounts other than their own, or to affect the system
itself. See the RSTS / E System Manager's Guide for detailed descriptions of
commands, qualifiers, and functions requiring additional privileges.

1.1.2

Your Project-Programmer Number
Account numbers on RSTSIE are called project-programmer numbers, or
PPNs. Your PPN corresponds to your account and identifies you as a system user.
A PPN consists of two numbers enclosed in square brackets and separated by a
comma, for example, [52,20]. The numbers are as follows:
•

A project number (the number 52 in [52,20]), which corresponds to a group of
users. For example, all employees in a particular work group may be assigned
the same project number.

•

A programmer number (the number 20 in [52,20]), which is unique for each
user in the group.

The brackets around the PPN show that the two numbers are used together.
Do not type the brackets when you log in, although you will need to use the
brackets in many operations dealing with files. Also, do not confuse brackets
around a PPN with brackets used to indicate optional parts of a command. (See
"Conventions" in the Preface.)
If you have more than one account on the system, you must use different PPNs
and passwords to log in to your different accounts.

1.1.3

Your Password
Your password protects your account from unauthorized use. Passwords on
RSTSIE systems can consist of 6 to 14 alphanumeric characters. (The system manager may restrict some users' passwords to a maximum length of 6
characters, while other users may use up to 14 characters.)
Your system manager may assign you a password or let you choose your own.
The method of assigning a password depends on the policy at your site. However,
most users are granted sufficient privilege to change their own passwords at will.
(Frequent password changes help to protect the system from unauthorized users.)
To minimize the chances that unauthorized users can discover your password,
Digital recommends the following guidelines:

•

Do not use names or words that could be readily associated with any user (for
example, WRITER, GUEST, or your first name).

•

Choose a password that contains both letters and digits.

•

Change your password at least once a month.

See Chapter 4 for details on how to use the SET PASSWORD command to change
your password.

1-2

Getting Started with RSTS/E

1.1.4

Using the Terminal (CTRL, DELETE, RETURN Keys)
You use a tenninal to communicate with the system. Tenninals can be grouped
into two main categories: hardcopy and video. A hardcopy tenninal, such as an
LA120, prints the characters you type and data from the system onto line printer
paper. A video tenninal, such as a VT100 or VT220, displays characters on a
Cathode Ray Tube (CRT) screen.
Most of the keys on a tenninal match the keys on a typewriter keyboard.
However, several keys on your tenninal's keyboard have special functions.
Three of the most commonly used function keys are labeled CtrI, Delete (also
known as Rubout), and Return.
For a complete list of the Control Keys which have special meaning to RSTSIE,
see Table I-I.

Ctrl The key labeled Ctrl is called the control key. You always use the control key
in combination with another key. For example, you can use CtrllU to delete all
the characters on a command line, up to the cursor, if you have not yet pressed
the Return key. Enter CtrllU by holding down the control key and then pressing
the "U" key on the keyboard. RSTSIE will clear all characters on the line up to
the cursor. On hardcopy tenninals, RSTSIE will display, or "echo", this at your
tenninal as AU. For example:
$ EDIT/EDT RACER. PDQ <Ctrl/U>

On your tenninal, this looks like:
$ EDIT/EDT RACER. PDQ AU
(

The line is now deleted. Press the Return key for the DCL prompt:
<RET>
$

Delete The Delete key has the same function on a hardcopy tenninal and on
a video tenninal, but the effects look different. On some hardcopy tenninals
the key labeled Rubout perfonns the delete function. On the VT200-series and
VT300-series tenninals the Delete key is labeled (<Kl). Use the Delete key to
erase one letter at a time, or hold the key down to erase words and lines. For
example, suppose you misspell a command and use the Delete key twice:
$ COPIE <DEL><DEL>

On a video tenninal, the resulting line reads:
$ cOP

By contrast, a hardcopy tenninal displays deleted characters between backslashes
(\), because a hardcopy tenninal is not designed to "erase" characters. For
example:
$ COPIE\EI\

Return The Return key allows you to:
•

End commands - . - When you enter the name of a command, pressing the
RETURN key tells the system to execute the command. For example:
DIRECTORY <RET>

(

Getting Started with RSTS/E

1-3

•

End lines - - - When you enter text in a file, the Return key ends each line
and begins a new one. For example:
Each year about 500 <RET>
runners enter Littleton's <RET>
annual road race. <RET>

•

Respond to a prompt - - - Sometimes pressing the Return key causes the
system or a program to assume a response, or "default." For example, the
following system prompt allows you to enter a line width, but lets you know
that, if you press Return without entering a number, the system assumes a
width of 50 characters per line:
Width of line <50>? <RET>

Table 1-1 is a list of special keys, including control keys, that you can use
at various levels of the system. Some keys have special line editing or recall
purposes. Command Line Editing and Command Recall is discussed in section
1.4.
Table 1-1: Special Function Keys on RSTS/E
Key

Function

CtrllA or F14

Toggles from overstrike mode to insert mode, or vice
versa, while editing a command line. Effective only until
a delimiter is entered, then the mode reverts back to the
terminal setting.

CtrllB or Up Arrow

Recalls the previous command typed by the user at the
current command level. When CtrllB or Up Arrow is entered,
the current line, if any, is erased and the next previous
command from the recall buffer is put in its place. The
cursor is positioned at the end of the recalled command,
regardless of the position of the cursor previous to the recall.

CtrllC

Halts execution of the current command or program and
usually returns control to the job keyboard monitor. (In
some programs, CtrllC may return you to the program's
command level.) CtrllC echoes on the terminal as "C. You
can lose data with CtrllC because it causes an immediate
halt.

CtrllD or Left Arrow

Moves the cursor left, or backward, one character position in
the command line. If the cursor is already at the beginning
of the command line, the key is ignored.

CtrllF or Right Arrow

Moves the cursor to the right or forward one character
position in the command line. If the cursor is already at the
end of the command line, the key is ignored.

CtrllH, Backspace, or F12

Moves the cursor to the beginning of the command line. If
the cursor is already at the beginning of the command line,
the key is ignored.

CtrlJE

Moves the cursor to the end of the command line. If the
cursor is already at the end of the command line, the key is
ignored.

CtrlJl or TAB

Moves the cursor to the next tab stop on the terminal line.
By default, tab stops are eight spaces apart (see the SET
TERMINAL!I'AB command ).

(continued on next page)

1-4 Getting Started with RSTS/ E

Table 1-1 (Cont.):

Special Function Keys on RSTS/E

Key

Function

CtrllJ, Line Feed, OR F13

On terminals that do not support line editing, it ends the
current line. Line Feed moves the cursor to the next line but
does not return the cursor to the left side of the screen. On
terminals that do support line editing, deletes the word to
the left of the cursor. Deleting a word will do the following:
1.

2.
3.

Delete any consecutive spaces and tabs immediately to
the left of the cursor.
Delete any consecutive alphanumeric characters [A-Z,
a-z, 0-9], immediately to the left of the cursor.
If no characters were deleted in step 2, then delete a
single, non-alphanumeric, character.

CTRLIL or Form Feed

Sends a typed line to the system for processing and skips four
lines on a video terminal. Form Feed and CtrllL advance the
paper to the top of the next page on hardcopy terminals (see
the SET TERMINAUFORM_FEED command).

CtrllN or Down Arrow

Performs a function similar to CTRLIB or Up Arrow except it
moves forward in the recall list, obtaining the next command
entered. Requesting a forward recall, when at the most
recent entered command of the recall buffer, results in
erasing the current command line on the screen, and no line
is recalled.

CtrllO

Stops and restarts terminal output while a program is
running. CtrllO does not affect program execution; however,
the system discards all terminal output the program produces
between the time you stop output and restart it again. CtrllO
echoes as "1\0" on the terminal.

CtrllQ

Resumes terminal output suspended by CtrllS while a
program is running. You can only use CtrllQ if the TTSYNC
(or STALL) characteristic is set for the terminal. (See
Chapter 5 for more information on terminal characteristics.)

CtrllR

Redisplays all characters of the current command line.

CtrllS

Suspends terminal output while a program is running.
You can use CtrllS only if the DeL TTSYNC (or STALL)
characteristic is set for the terminal. When you use CtrllS,
the system saves all terminal output that the program
produces instead of discarding it (as it does when you use
CtrllO). (See Chapter 5 for more information on terminal
characteristics.)

CtrllT

Displays a one-line status report for your job. The report
includes your job number, keyboard number, job state, and
other information. See Chapter 4 for more information.

(continued on next page)

Getting Started with RSTS/E

1-5

Table 1-1 (Cont.):

Special Function Keys on RSTS/E

Key

Function

CtrllU

Erases all characters from the beginning of the line to the
cursor. The remaining characters are shifted to the beginning
of the command line. CtrllU erases characters from the
screen on terminals which support line editing. On multiline
commands, deletes only the portion of the command from the
cursor to the left margin. CtrllU behaves the same, whether
command line editing is enabled or not. If the terminal is
set to HARDCOPY, "U will be displayed and the remaining
portion of the command will be displayed on the next line,
similar to earlier versions of RSTS!E.

Ctrl/X

Deletes all type-ahead including the current terminal line.
Ctrl/X echoes as "X and moves the cursor to the next line.

CtrlJZ

Is an end-of-file (EOF) marker. Ctrl/Z can also be used to end
a DCL command and return to the DCL prompt. Echoes as
""Z" on the terminal.

Delete or Rubout

Erases the character to the left of the cursor. Any characters to the right of the cursor are shifted to the left. On
hardcopy terminals, erased characters are displayed between
backslashes.

Escape or Altmode or
CtrlJ[

Sends a typed line to the system for processing or starts an
escape sequence if the terminal is set !ESCAPE_SEQUENCE.
Escape, Altmode, and CtrlJ[ Echo on your terminal as a dollar
sign ($).

Hold Screen

Performs the same function as CtrlJS and CtrlJQ on VT200
and VT300-family terminals. The TISYNC (or STALL)
characteristic must be set for the terminal.

No Scroll

Performs the same function as CtrlJS and CtrlJQ on VT100,
VT101, VT125, and other VT100-series terminals. The DCL
TISYNC (or STALL) characteristic must be set for the
terminal.

Return

Sends a typed line to the system for processing. Pressing
Return moves the cursor to the beginning of the next line.

NOTE

A common mistake is to press the No Scroll key (on VT100s), Hold
Screen key (on VT200 or VT300 series), or CtrllS (on VT52s) to stop
output to the terminal, and then forget to press No Scroll, Hold Screen,
or CtrllQ to resume output. (Nothing is displayed at the terminal when
you press No Scroll, Hold Screen, or CtrllS.) In either case, the system
does not display another DCL prompt when you press Return. You
must press No Scroll or Hold Screen again, or CtrllQ, to resume output.

1.1.5

Beginning a Terminal Session : HELLO or LOGIN
You can log in to your account on the system as soon as you have a PPN and
password. RSTSIE provides two commands for logging in to your account:
HELLO and LOGIN. To get started, type HELLO (or LOGIN) and press Return:
HELLO <RET>

1-6

Getting Started with RSTS/E

The system signals that it is in operation by displaying a message similar to:
RSTS/E V10.0-L

15-Jun-90

05:52 PM

User:

This message gives you the following information:
•

The name and version number of the computer's software.

•

The current date and time. RSTSIE keeps track of the length of time you use
the system and its resources, starting with the date and time of login.

•

The prompt for your account PPN. RSTSIE displays the User: prompt.

Login also allows you to log in using a (system) logical name instead of a PPN.
You can respond to LOGIN's User: prompt with a system logical name (without
a trailing colon). Most systems which use this feature will set up the logicals to
match your name, or account type, (for example, Smith, Writers, or Manager).
Enter your account PPN, (or system logical name) and password after the
prompts as shown. Note that the system does not display your password as
you type it. This prevents anyone who may be watching from discovering your
password.
User: 52,20 <RET>
Password: <RET>

You will generally be able to log in this way with no problems. However, it may
help you to know the following constraints:
•

If you wait too long before answering the User: and Password: prompts (the
limit is 30 seconds) or if your response to either prompt is incorrect, the
system prints ?Invalid entry - try again, and reprints the User prompt. If
you type in the wrong PPN, the system does not tell you until after you have
typed your password.

•

Mter two invalid login attempts, RSTSIE waits 5 seconds before displaying
the User prompt; this wait time increases with each successive invalid login
attempt.

•

Mter five invalid login attempts, the system prints ??Access denied. If you
are trying to use the system over a dialup line when this happens, the
system disconnects the phone line. Verify your PPN and password before
trying again.

When you log in successfully, you may see two messages showing the date and
time you last logged in to the system, both interactively and noninteractively.
Noninteractive logins are batch jobs or network file transfers. These messages
confirm that you now have access to RSTSIE. For example:
Last interactive login on 14-Jun-90, 08:50 PM at KB48:
Last noninteractive login on 05-Jun-90, 02:08 AM

Your system manager may choose to display other messages of general system
interest:
15-Jun-90

The system will be down Saturday, 16-Jun-90,
from 8:00 AM to 1:00 PM for maintenance.

RSTSIE is now at the command level, which means that it is ready to accept the
commands you enter. The dollar sign ($) prompt indicates the DeL command
environment, which is the default for RSTSIE.

Getting Started with RSTS/E

1-7

You can also use the LOGIN command when you are already logged in to the
system if you want to "reset" your current job to the state it was when you
originally logged in. Use the LOGIN command to log in your current job under a
different account. This allows you to switch between accounts without having to
first issue the LOGOUT command. If you do not have sufficient privilege, then
you will be prompted for the password of the account you want to log into. Typing
LOGIN while you are logged in causes RSTSIE to execute the Login procedure
again, as if you had logged out and then logged back in.

1.1.6 The System Command Environment
The default keyboard monitor on your system is the command environment that
is present when you log in. DCL is the default keyboard monitor for RSTSIE
systems. The dollar sign ($) prompt means that RSTSIE is ready for you to enter
DCL commands.

1.1.7 Other Command Environments
From DCL, you can switch to one of three other command environments, all of
which have different prompts, as shown:
Ready

The BASIC-PLUS environment
The RSX environment
The RTll environment

Some commands - such as RUN to run a computer program - are common to all
environments. Other commands are available in only one environment, although
the actions you perform are similar throughout the command environments.
For example, you use the DELETE command in the DCL environment to delete
files you have created; you use the UNSAVE command in the BASIC-PLUS
environment to perform the same function.
RSTSIE uses DCL as its default command environment because DCL commands
are used on other Digital systems, including VAXlVMS. So if you change from a
RSTSIE to a VAXlVMS system, or back again, you will be able to use many of the
same commands.
You may want to switch from the DCL command environment, depending on
your work needs or your particular preference. For example, the BASIC-PLUS
environment is useful if you do a great deal of programming in the BASICPLUS language. By the same token, the RSX and RTll environments emulate
the commands available on Digital's RSX and RT-ll operating systems for the
PDP-ll computer; if you have worked with either of these systems, you may feel
more "at home" in one of these environments. Appendix B provides more detailed
information about switching between the command environments. In addition, it
lists some of the commonly used commands in the BASIC-PLUS, RSX, and RTll
environments.

1-8 Getting Started with RSTS/E

1.2 Echo on Read
Echo on read is the processing and echoing of characters typed on a terminal
only when a program or command environment is waiting for input. In versions
of RSTSIE prior to VI0.0, characters were processed and echoed as soon as you
typed them, even if no program or command environment was waiting for imput.
In some instances, these typeahead characters would be processed incorrectly. For
example, if you begin typing your password before LOGIN issued its Password:
prompt, the characters you typed were echoed, then when the password: prompt
was issued, your password would show up before the prompt making the entry
incorrect.
Echo on read has a very different "look and feel" than previous versions of
RSTSIE. Most noticeable is the lack of any visual cues when you type ahead
(since typeahead characters are no longer echoed until a read occurs). You may
conclude that your terminal or the system is not functioning properly; if so, type
CtrllT to see that your terminal and the system are still operating.

1.2.1

Using login Command Files
At login, the RSTSIE system attempts to execute the systemwide command file
LOGIN. COM located in account [0,1] on the system disk. This file contains
commands defined by the system manager that are executed for aU users. In
addition, the systemwide login command file normally contains a command that
invokes a private LOGIN.COM file located in your directory on the system disk.
If your system manager allows the use of private LOGIN. COM files, the system
automatically executes these commands every time you log in. This feature lets
you tailor the system for your everyday use.
For example, if you enter the same sequence of commands every time you log
in, place these commands in a command file (also called a command procedure)
named LOGIN.COM. You can also define synonyms for often-used DCL commands
in your LOGIN.COM file, making them easier to type and remember. The
LOGIN. COM file could also contain commands to assign logical names, run
programs, execute other command procedures, or display message files. For
example:
$ TYPE $NEWS.TXT
$ @TERMoCOM
$ RUN DB1: [2,214]COOKIE.EXE
$ ASSIGN DR3: [4,214] WORK ACCT
$ TODO == "@REMIND"
$ S == "SHOW SYSTEM"
$ WH-O == "SHOW USERS"

Display system messages
Execute a command procedure
Run a program
Assign a logical name
Define a command to execute a procedure
Abbreviate a command
Nickname a command

Use the at sign (@) command to execute and test your LOGIN.COM file. For
detailed information on creating and executing various types of command
procedures, including LOGIN,COM files, see the RSTS/E Guide to Writing
Command Procedures. Figure 1-1 shows the difference between the user-defined
and the system-defined login command files.

Getting Started with RSTS/E

1-9

Figure 1-1:

Executing System and User Login Files

RSTS/E V9.0

15-Jun-85

12:35 PM

User: 2,214
PasslA1ord:
Last logged in on 14-Jun-85

9:35 AM at KB32:

,
The system LOGIN.COM runs
until the end-of-file,
when control is passed
to [2,214] LOGIN.COM

SY:[OtlJ LOGHLCOM
$TYPE $NOTICE,TXT
$ENDLOG I ~j:
DB1: [2 ,214J LOGHLCOM

[2,214] LOGIN.COM runs
until the end-of-file

$ASSIGN DR3:[2.214J WORK:
$RUN DB1:[2.214J COOKIE.EXE

~
When [2,214] LOGIN.COM
completes, control is
returned to user at
terminal

In Figure 1-1, the file specification for the system-defined Login command file
is SY:[O,I]LOGIN.COM. The file specification for the user-defined Login file is
DBl:[2,214]LOGIN.COM. When user [2,214] logs in, the system-defined Login
file executes first. After the system-defined Login file completes, the command
interpreter locates and executes the user-defined login file on the default disk and
directory for user [2,214].

1.2.2

Getting Information About Commands: HELP
You can use the help facility to learn about the commands that are available on
RSTSIE. Each time you use HELP, RSTSIE displays the information you request
and then displays the DCL prompt.
To use HELP, type:
$ HELP <RET>

1-10

Getting Started with RSTS/E

The system displays the list of DCL Commands as well as various general help
topics on which you can get information:
You can obtain online information about any DCL command or qualifier,
as well as many other general topics . For more complete details about a
topic, refer to the appropriate RSTS manual or guide.
The RSTS/E System User's Guide contains descriptions of the DCL commands
and qualifiers that you use in file, system, and programming operations .
The RSTS/E System Manager's Guide contains descriptions of the DCL
commands and qualifiers used in system management operations.
See the RSTS/E Quick Reference Guide for the syntax of all
DCL commands and qualifiers on RSTS/E.
For instructions on how to use this HELP facility, type HELP HELP from
DCL, or type HELP in response to the HELP Topic? prompt.
Additional help is available on:
@

ASSIGN
BYE
Command Recall
DEALLOCATE
DIBOL
EDIT
Files
GOSUB
INITIALIZE
Line Editing
MACRO
OPEN
Programs
REMOVE
RETURN
Servers
STOP
UNLOAD

Accounts
ATTACH
CC
COPY
DEASSIGN
DIFFERENCES
Entries
FORCE
GOTO
INQUIRE
LINK
MAIL
Operators
Queues
RENAME
RTll
SET
SUBMIT
WAIT

Advanced
BACKUP
CCL
CREATE
DEFINE
DIRECTORY
EOD
Forms
HANGUP
INSTALL
LOAD
MERGE
Passwords
Quotas
REPLY
RSX
SHOW
Symbols
WRITE

ALLOCATE
BASIC
CLOSE
Dates
DELETE
DISMOUNT
EXIT
FORTRAN
HELP
Keys
LOGIN
MOUNT
PRINT
READ
REQUEST
RUN
SORT
Times

APPEND
BROADCAST
COBOL
DCL
DETACH
DUMP
Expressions
Functions
IF
Labels
LOGOUT
ON
Privileges
RECALL
RESTORE
Runtime Systems
START
TYPE

The help display on your system may be different from what is shown here
because the system manager can change the help information.
The display lists topics on which help is available. For example, if you want to
read about the LOGIN command, you type:
$ HELP LOGIN <RET>

RSTSIE displays information about the LOGIN command and lists its restrictions
and qualifiers. The display on your terminal reads:
$ HELP LOGIN

LOGIN
The LOGIN command is used to:
o Create a new job at a terminal you specify. You can use this
feature in your system startup procedure, to log in various users
automatically. You must have WACNT or GACNT privilege to do this.
o Log in your current job under a different account . This allows you
to switch between accounts without having to first issue the LOGOUT
command . If you do not have sufficient privilege, then you will be
prompted for the password of the account you want to log into .
o Reset your current job to its initial logged-in state (the state
your job was in after logging in). This is useful for resetting
logical assignments, DCL symbols, prompts, etc. to their initial
state. This requires no privilege.

Getting Started with RSTS/E

1-11

Format:
LOGIN

[account]

If you do not include an account <emphasis> (parameter\bold), then your
own <line> account PPN is assumed.
Privileges required:
DEVICE to create a new job at a restricted terminal.
GACNT or WACNT to log in a new job under a different account.
GACNT or WACNT to log in a different account without being
prompted for that account's password.
Command Qualifiers
/[NO]OVERRIDE[=NOLOGINS]
/TERMINAL=KBn [ : ]

Defaults
/NOOVERRIDE

Prompts
Password:

(if logging into different account and no WACNT or
GACNT privilege)

For more information, see the RSTS/E System User's Guide and
and the RSTS/E System Manager's Guide.

The "Advanced" topic gives more detailed information about RSTS/E on a wide
variety of subtopics.
$HELP ADVANCED <RET>
Advanced
The HELP topic ADVANCED is generally for reference by RSTS/E
programmers. You can find more complete information about the
subtopics below in the RSTS/E Programming Manual and the RSTS/E
System Directives Manual.
Additional help is available on:
ASCII chart
Magtapes
SYS calls

Disks
PEEK
Terminals

FIP codes
Pseudokeyboard

Floppy SPEC%
STATUS word

RSTS/E help messages are available in a "hierarchy." This means that the
help you request is available in levels of increasing detail. You can type HELP
ADVANCED and a subtopic, such as Disks, for information about the disks on
RSTSIE:
$HELP ADVANCED DISK <RET>

Each topic may have a subtopic, or a subsubtopic which you can include in the
command line:
$HELP ADVANCED DISK SIZES <RET>

1.2.3

Ending a Terminal Session: LOGOUT or BYE
RSTSIE provides two commands for ending, or logging out of, your terminal
session when you are finished using the system: LOGOUT and BYE. (Use
whichever of these two commands you find most convenient; their effect is
identical.)
You can include one of two qualifiers when using the LOGOUT command: /BRIEF
or/FULL.
If you simply type LOGOUT (or BYE), the /FULL qualifier is the default:
$ LOGOUT <RET>

1-12

Getting Started with RSTS/E

RSTSIE displays information about the status of your account at the time of
logout:
Saved all disk files on SY: 1568 blocks in use
Job 13 User 52,20 logged off KB2 at 15-Jun-90 02:36 PM
System RSTS V10.0-L
Run time was 3 minutes, 2.4 seconds
Elapsed time was 21 minutes
Good afternoon

The logout information tells you:
•

The status of your permanent files (Saved all disk files). RSTSIE also shows
the use of your file storage space (1568 blocks in use).

•

Your job number (13), PPN (52,20), terminal number (KB2), the date (15-Jun90) and time of logout (02:36 PM).

•

The name and version of the computer's software (RSTSIE VI0.0-L).

•

The time you spent at the terminal (run time and elapsed time).

•

Any logout messages (Good afternoon).

Note the difference between run time (3 minutes and 2.4 seconds) and elapsed
time (21 minutes). Run time is the amount of the Central Processing Unit's
(CPU) time you used. The commands you type require the use of the system's
CPU. Elapsed time shows how long you were logged in to the system. Although
you were logged in for 21 minutes, you used the computer's CPU for only a
fraction of that time. If you include the /BRIEF qualifier after the LOGOUT
command, RSTSIE ends your session at the terminal by displaying a one-line
message. The BYE command has a corresponding qualifier, /F (for "fast"), which
produces the same message as LOGOUT/BRIEF:
/

$ BYE!F <RET>

Job 13 User 52,20 logged off KB2 at 15-Jun-90 02:36 PM

1.3 Using DCl Command Qualifiers
In the DCL environment, you use commands by typing a command name and
pressing the RETURN key. You can also use qualifiers, which modify the effects
of a command, by typing a slash (I) followed by a word the computer recognizes
as a qualifier. For example, the LOGOUT command has two possible qualifiers:
/BRIEF and /FULL.
You type a qualifier after the command name but before pressing the RETURN
key. If you do not use qualifiers, DCL makes assumptions known as defaults.
For example, if you use the LOGOUT command, the /FULL qualifier is the
default. You could type the /BRIEF qualifier instead, which modifies the effect of
LOGOUT by displaying a one-line message instead of the full Logout display.
Chapter 2 describes the use of qualifiers in more detail. In addition, the
command descriptions in this manual list the qualifiers and defaults available for
each command.

Getting Started with RSTS/E

1-13

1.4 Editing and Recalling Commands
This section describes command line editing and command Hne recall. These
features significantly improve productivity by reducing the amount of keystrokes
required to enter commands or correct typing errors. Because these features are
implemented in the RSTS/E monitor, they are available at the DCL command
level, within other keyboard monitors, and at the application program level.

1.4.1

Command line Editing
Prior to RSTSIE V10.O, the only two line editing functions were:
..

The Delete or Rubout key to delete the previously typed character (to the left
of the cursor)

Ctr1JU to delete the entire line

This made it difficult to correct errors discovered near the beginning of a command; you could either delete all characters back to the character to be corrected,
or delete the line and re-enter it. There was no way to move the cursor within
the line to make corrections.
Command line editing makes it easier by adding several line functions that allow
you to:
'"

Move the cursor left or right one character

Move the cursor to beginning or end of the line

Delete the previous word

Delete to the beginning of the line

Insert a new character at the cursor position

01>

Overstrike (replace) an existing character at the cursor position

These functions reduce the amount of typing required to correct errors or, when
coupled with command recall, modify and re-execute already entered commands.

1.4.2

Command Recali
Command recan allows you to recan your most recently entered commands
or program input lines. Command recall extends line editing additionally by
allowing you to recan and change commands or program lines after they have
been entered and executed. This saves time in re-entering the same command
(such as editing the same file multiple times) or correcting a command that did
not execute as expected.
RSTS/E provides command recall for the following three separate command
levels:

1-14

DCL commands

Commands entered in other keyboard monitors

Program input

Getting Started with RSTS/E

Each command level is limited in size, therefore only a certain number of
commands can be stored and maintained. As commands are entered, the oldest
command in the buffer is deleted to make room for the new command. Unlike
recalling commands on VMS, RSTSIE is not limited to only 20 commands.
Instead, RSTSIE maintains as many commands as will fit in the buffer. The
actual number of commands saved depends on the size of the buffer and the
length of each command entered.
DCL commands are stored in their own command level. The DCL level can be
thought of as the highest command level, with the keyboard monitor level and
program level following it. Commands stored in the DCL level are maintained
until you log out, until they are replaced with newer commands as space
is reclaimed, or until you specifically erase them with the RECALLIERASE
command. You can use the DCL RECALL/ALL command to list all of the
commands available for recall in the DCL level, or to recall a specific command
either by index number or text. See Section 1.4.3 for more information on the
RECALL command.
If you switch from DCL to another keyboard monitor, either with the SET
JOBIKEYBOARD_MONITOR command or the SWITCH system command (CCL),
you advance to the second command level - the keyboard monitor level. All
commands entered at this level are stored and maintained separately from
your DCL commands. Once you return to the DCL command level, all of the
commands entered at the keyboard monitor level are erased and the DCL level
is reactivated. This feature is especially useful for users who must occasionally
switch to another keyboard monitor, such as BASIC-PLUS, to perform a task
not accessible from DCL, for example, compiling a BASIC-PLUS program. The
separate keyboard monitor level prevents non-DCL commands from being stored
in the DCL level.

A third command recall level is provided for program input. Whenever a program
initially prompts for input from the terminal, the monitor sets up the third level.
Lines entered at the program level are automatically saved and may be recalled,
just like at the DCL level, without any special coding on the part of the program.
Program lines will continue to be stored across program chains and Concise
Command Languages (CCL) until you return to DCL or another keyboard
monitor. At that time, the commands stored for the program are erased and the
DCL or other keyboard monitor's level is reactivated.
Use the Up Arrow and Down Arrow terminal keys to move backward or forward
in the current recall buffer (CtrllB and CtrllN can also be used, for terminals that
do not have arrow keys).
You can also use the DCL RECALL command to manage commands at the DCL
command level. Use the RECALL command to:
•

Display your saved commands

•

Erase your saved commands

•

Recall a saved command by index number

•

Recall a saved command by text

See the next section on the RECALL command for more information.

Getting Started with RSTS/E

1-15

1.4.3

RECALL Command
The RECALL command is used to:
•

List all of the commands available for recall

•

Erase all of the commands in the current level

•

Recall a command by its index number

•

Recall a specific command by its leading text

Format
RECALL

[integer I leading-substring]

Command Qualifiers
/All
/ERASE

Command Parameters
[integer]
Specifies the number of the DCL command you wish to recall. The default is
1, indicating the most recently entered command. Command 2 is the next most
recently entered command. The RECALL command itself is never assigned a
number, since it is not saved in the command recall buffer. Use the RECALL/ALL
command to list all available commands and their associated numbers. Command
numbers can range from 1 to 65535. Thus any command entered at the DCL
prompt may be recalled. If the number of stored commands is less than the
number specified, the earliest available command is recalled. An error is returned
if an integer not in the range 1 to 65535 is specified. When a command is
recalled, it is not automatically executed. It is displayed on the screen with the
cursor positioned at the end of the line.
[leading-substring]
You can also recall commands based on a leading substring of the command you
wish to recall. The term leading substring refers to the first several characters in
a command string. The substring can be as short as a single character. If the
substring is not unique, RECALL recalls the most recently issued command line
that matches the substring. For example, suppose you issue a SHOW SERVER
command and later issue a SHOW TIME command. If you then type RECALL
S, the SHOW TIME command is recalled. You must type RECALL SHOW S, to
recall the SHOW SERVER command.

When searching for a command to match, leading spaces and tabs in the command are ignored. All alphabetic characters are considered case insensitive for
comparison purposes.
An error is returned if the leading substring does not match any command stored
in the current command level.
When a command is recalled, it is not automatically executed. It is displayed on
the screen with the cursor positioned at the end of the line.

1-16

Getting Started with RSTS/E

Command Qualifiers
fAll
Displays all commands currently available for recall, along with their command
nwnbers. Remember that the RECALL command itself is never stored in the
recall buffer.

If /ALL is specified immediately after the RECALL command, an error will be
returned if the integer or leading substring parameter is also specified.
If /ALL is specified after the parameter, it is assumed that /ALL is part of the
leading substring to recall. For example, if you enter a COPY/ALLOCATION= ...
command, and later issue the command RECALL COPY/ALL, the COPY command win be recalled because there is a match on the characters COPY/ALL.
fERASE
Erases the contents of recall buffer. All commands stored by the monitor for each
level (DCL, other keyboard monitors, and programs) will no longer be available
for recall. If !ERASE is specified immediately after the RECALL command, an
error will be returned if the integer or leading substring parameter is specified.
If !ERASE is specified after the parameter, it is assumed that !ERASE is part of
the leading substring of the text to recall. For example, if you issue the command
RECALL l!ERASE, it will result in an error unless you previously entered a
command which began with "l!ERASE". !ERASE is ignored if /ALL is specified.

Getting Started with RSTS/E

1-17

104.4

Command Line Editing and Recall Keys
All command line editing and recan keys are identical to those defined on VMS,
with one exception. This exception is that RSTSIE defines the CtrllN key to recan
the next (more recent) command in the recan buffer. VMS has no such control
key defined. CtrllN has the same effect as the Down Arrow key. RSTSIE provides
the CtrllN key to complement the CtrllB (recall previous command) key, so that
you can move backward and forward in the recan list while the terminal is open
in Escape Sequence mode (mode 256).
Listed below are the special command line editing and recall keys. The online
help topic Keys and the RSTS / E Quick Reference Guide also contain information
on the use ofthese keys. Table l-llists aU keys which have special meaning to
RSTSIE, in fun detail.

Left Arrow or Ctrl / D moves the cursor left, or backward, one character.
Right Arrow or Ctrl/ F moves the cursor right, or forward, one character.
Ctrl / H, (BACKSPACE), or F12 moves the cursor to the beginning of the line.
Ctrl / E moves the cursor to the end of the command line.
Ctrl / A or F14 toggles between overstrike mode and insert mode.
Ctrl/J, (LINE FEED), or F13 deletes the word to the left of the cursor.
Ctrl/ U erases all characters from the beginning of the line to the cursor.
Ctrll R redisplays the command line without changing the cursor position.
Up Arrow or Ctrl / B recalls the previous command.
Down Arrow or Ctrl / N recalls the next command.

1.4.5

Editing Multiline Commands
Multiline commands are commands or lines that extend beyond the terminal's
width and wrap onto one or more subsequent lines. The following rules apply
when editing multiline commands on terminals which support line editing:
•

You can only move the cursor left or right or delete characters on the last line
of a multiline command. You cannot move the cursor from the last line to a
previous line of the command unless you first delete all of the characters on
the last line (thereby making the previous line the last line).
If the cursor is positioned at the first character of the last line and you press
the Left arrow or CtrllD key to move the cursor left (to the last character of
the previous line), then the key is ignored and the cursor does not move. You
must first delete all of the characters on the last line, before you may position
the cursor at the end of the previous line using the delete key.

1-18

Pressing Ctr]JU when the cursor is positioned on the last line of a multiline
command line only erases characters to the beginning of that line, not to the
beginning of the entire command. As always, any characters from the cursor
to the end of that line are shifted left to the beginning of the line.

Similarly, pressing Backspace or Ctrl/H when the cursor is positioned on the
last line of a multiline command only moves the cursor to the beginning of
that line, not to the beginning of the first line.

If you press Line Feed or CtrllJ to delete the word to the left of the cursor,
and that word extends back to the previous line of a multiline command (the
word is split across two lines), only those characters back to the beginning
of the current line are deleted. The remainder of the word at the end of the
previous line is not deleted.

Getting Started with RSTS/E

When you type CtrllR on multiline commands, the cursor is moved to the
left hand margin, and spaces are displayed until the cursor lines up under
the start of the command. For example, if you type a command which wraps
onto a second line and press CtrllR, the display looks like this (vertical lines
indicate terminal margins):
AFTER "R

BEFORE "R
IPROMPT> Command wraps herel
land continues on 2nd line. I

IPROMPT> Command wraps herel
I
Command wraps herel
land continues on 2nd line. I

Unlike VMS, RSTSIE does not save the current command's prompt. It cannot
redisplay the prompt with the command when CtrllR is pressed.
Because of these limitations, you should try to avoid entering multiline commands
whenever possible. In some cases you can use DCL command abbreviations or
redefine frequently used "long" DCL command/qualifier strings to reduce the
length of your command. You can also redefine your terminal width to 132
columns (on terminals that support the extended width feature) to allow for
longer commands on a single line.

1.5 Maintaining Files
Many of the DCL commands in this manual affect files. It is helpful to understand the relationship between accounts and directories when you work with
files.

1.5.1

Accounts, Directories, and Files
When you begin a RSTSIE session, you log in to an account. Your PPN is an
account number, which identifies you to the system.
The system uses your account to keep track of the system resources you use,
such as the amount of time you access the computer's memory (run time) or are
logged in (elapsed time), and the amount of storage space your files require. If
you have more than one account on the system, RSTSIE sees each account as
belonging to a separate user, who is identified by a PPN.
A directory is a collection of files in your account that are kept in a specific
location on a disk. An account may have several directories on different disks.
Each directory stores information, such as the name and size of each file.
You identify a file by specifying its location and its name. A file's location consists
of:
•

The node on the network - A node is a computer system with DECnetiE,
which connects two or more systems together. See the section "Using
DECnet" for more information.

The device - Files are usually kept on disks or magnetic tapes. Your files
are located on a set of disks called the public structure, unless you specify
otherwise.

The directory - A device can be divided into directories, in which you can
store files. You specify your directory like you specify your account, by using
yourPPN.

Getting Started with RSTS/E

1-19

A file's name, chosen by the person who created the file, consists of:
•
•

The file name - One- to six-alphanumeric characters (MYFILE)
The file type - Zero- to three-alphanumeric characters, preceded by a period
(.TXT)

1.5.2

Putting Files into Your Directory
You can put files into your directory either by moving them from another
directory or account or by creating them. The following example creates a file
with the CREATE command (see Chapter 3) to show the placement of a file in a
directory.
Th use the CREATE command, type:
$ CREATE <RET>

The command prompts you for a file specification:
File:

You can assign the file almost any name you choose. For this example, name the
file ROAD .MAP:
File:

ROAD.MAP <RET>

Enter the text as follows, and press Ctrl/Z when you are finished. (CtrllZ is
displayed on the terminal as I\Z, but the characters I\Z do not become part of the
file.) If you make a mistake on a line before you press the RETURN key, you
can press the DELETE key to correct it, or use any line editing keys described in
Table 1-1.
Although I have been a jogger for <RET>
more than eight years, I did not <RET>
enter any road races until 1989. <RET>
<Ctrl/Z>
$

The newly created file named ROAD.MAP is now in your directory.

1.5.3

Displaying Your Files
If you are new to a RSTSIE system, you mayor may not have files in your
directory. Files exist in your directory only if someone put them there; it is
possible that the system manager or another user gave you some files. If you
created ROAD.MAP in the previous section, then information about the file
appears in a directory listing.

You can check for files in your directory with the command:
$ DIRECTORY <RET>

If you have no files in your directory, RSTSIE displays a message similar to:
%No files matching [52,20 ] ????????? - continu i ng

The PPN ([52,20]) identifies your directory, and the question marks (?????????)
show that no files are found.

1-20

Getting Started with RSTS/E

If there are files in your directory, the system displays information about each

file. For example:
(

Name .Typ
TEMP16.TMP
BRANCH.BAC
FSS
.BAC
HELP . COM

Size
1
15C
lIC
1

Prot
< 60>
<124>
<124>
< 60>

Name
MAIL
MAIL
lOB
ROAD

.Typ
. MAl
. SYS
. BAC
. MAP

Size
30
14

lIC
1

Prot
< 60>
< 60>
<124>
< 60>

SY: [52,20]

Total of 84 blocks in 8 files in SY: [52,20]

Your directory provides the following information about each file in your account:
Name.Typ

The names and types of your files.

Size

The size of your files in numbers of blocks. (A block is 512
characters.)

Prot

The protection code assigned to your files. This determines
whether or not other users can read, write or execute the files .

SY:[52,20] identifies your directory as being on the system disk (SY:) in your
account ([52,20]).
Certain operations (such as compiling and linking programs) cause RSTSIE to
create a temporary file with a .TMP file type. Temporary files are scratch files
that programs use for work space. The file named TEMP16 .TMP in the preceding
listing is a temporary file.
Do not display or work with temporary files, because they often contain codes
that can make your terminal work abnormally. Temporary files are mentioned
only because they use disk space and are displayed in the directory listing; the
system automatically deletes them when you Logout.
The TYPE command displays the contents of a file. The following example shows
the contents of the file ROAD.MAP:
$ TYPE ROAD.MAP <RET>
Although I have been a jogger for
more than eight years, I did not
enter any road races until 1989.

1.5.4

File Specifications
A file specification is the full name and location of a file. In its complete form, the
file specification includes:
•

A node name on the DECnetIE network, if applicable

•

The device name or logical name (see Chapter 6 for descriptions)

•

The directory

•

The file name

•

The file type

The format of a complete file specification is:
node: :device:[directory]filename.typ
The delimiters (special characters) in a file specification are brackets, commas,
and colons. Brackets ([]) surround a PPN. A comma (,) separates the two
numbers in a PPN. Double colons (:: ) follow node names, while a single colon (:)
follows the device name.

Getting Started with RSTS/E

1-21

The delimiters (@), (%), (&) and (#) have been accepted since V9.0 to specify
special system accounts, but their use is not supported. They are reserved DCL
characters, and may have other meanings in the future.
The special account delimiter (!) does not work in DCL. The exclamation point is
used as the comment delimiter.
Parentheses "()" are reserved DCL characters and cannot be used as a delimiter
for a PPN in DCL.
Protection codes in angle brackets « » cannot be used in DCL. The DCL syntax
for protection codes is IPROTECTION:nn.
A dollar sign ($) in place of a PPN indicates the directory [1,2], which is the
system library. (The system library stores most of the system files and programs.)
For example, the following command displays a system file named NOTICE.TXT:
$ TYPE $NOTICE.TXT <RET>

A file specification can be as simple as:
ROAD.MAP

In this case, RSTSIE assumes your own directory, the local node, and the system
disk by default. See the section "Using DECnet" for an explanation of host node.

An example of a file specification that does not assume any defaults is:
GARP::DRO: [52,20]ROAD.MAP

The parts of the file specification are:

1.5.5

GARP::

The node (system) on the network

DRO:

The device at node GARP:: on which the file is located

[52,20]

The directory on the disk at node GARP::

ROAD.MAP

The file name and type

File Names and Types
When creating a file, you can assign it any name with up to six alphanumeric
characters. You can also change the name of a file with the RENAME command
(see Chapter 3).
A file type consists of one to three alphanumeric characters that follow a file
name. There is a period between the file name and file type. File types provide
you with a shorthand way to identify a file's contents. For example, the file
STATUS.DOC has a file name of STATUS and a file type of .DOC.
NOTE

If you assign a file name of more than six characters or a file type of
more than three characters, RSTSIE accepts your input then truncates
the name to the first six characters and the type to the first three
characters. For example, if you name a file LONGNAME.LIST, RSTSIE
truncates it to LONGNA.LIS.
You can assign any alphanumeric file name and type in a file specification,
although it is a good idea to use a "mnemonic" name. This means that you
should assign the file a name that reminds you of its contents. For example,
TEST.DAT could be a data file (.DAT) that you create to test a program (TEST). If
you have a file containing a BASIC-PLUS program to run your payroll, you might
name it PAYROL.BAS. The file type .BAS indicates a BASIC-PLUS source file. (A
"source" file contains the program you typed in.)
1-22

Getting Started with RSTS/E

An advantage of using a mnemonic file type is that RSTSIE recognizes several
file types by default (for example, .DOC, .DAT, .RNO, .COM, and so on). If you
assign a file one of these types, then you do not always have to type it explicitly.
For example, if you are using the COBOL command to compile a program, you
can type:
$ COBOL PROGl <RET>

RSTSIE assumes the resulting source file to be PROG1.CBL, because the file type
.CBL is the default for a COBOL source file.
Table 1-2 lists some common file types on RSTSIE.

Table 1-2:

RSTS/E File Types

File

Meaning

.B2S

BASIC-PLUS-2 source file

.BAC

BASIC-PLUS compiled file

.BAK

Backup file created by several types of utility programs

.BAS

BASIC-PLUS source file

.BCK

BACKUP container set (or RMSBCK container set)

PDP-ll C source file

.CBL

COBOL source file

.CMD

Task Builder Command file

.COM

DCL command procedure

.CRF

Cross-reference listing file

.CTL

Batch control file

.DAT

Data file

.DBL

DIBOL source file

.DIF

DIFFERENCES or FILCOM output file

.DIR

File produced by the DIRECTORY command

.DOC

RUNOFF output file

.EDT

EDT initialization file

.ERR

System error file

.ESC

Terminal setup file

.FLB

FMS-ll form library file

.FOR

FORTRAN-IV source file

.FTN

FORTRAN-77 source file

Header file in C language

.HLP

System program help text file

.LIB

Resident library file

.LNK

Input file used by the DCL LINK command

.LOG

Batch output log file

.LST

Listing file

.MAC

MACRO source file

.MAl

DECmaillRSTS mailbox file

(continued on next page)

Getting Started with RSTS/E

1-23

Table 1-2 (Cont.):

1.5.5.1

RSTS/E File Types

File

Meaning

.MAP

Map file created by the LINK command or Task Builder

.MLB

MACRO library file used by the RSX-based MACRO assembler

.MSG

DECmail message file

.OBJ

Object file, which is a compiled BASIC-PLUS-2, COBOL, DIBOL,
FORTRAN, or MACRO program

.ODL

Overlay Description Language input file used by the Task Builder

.OLB

Object module library file used by the Task Builder

.OMS

OperatorlMessages Services log file

.PMD

Postmortem Dump file

.RNO

RUNOFF input file

.RTS

Run-time system

.SAV

Executable FORTRAN-IV or MACRO program produced by the LINK
command or the RTll-based LINK program

.SIL

Save Image Library (RSTSIE monitor or system program)

.SKL

Skeleton file produced by the COBOL-81 compiler

.SML

RTll source MACRO library

.SRT

SORT-ll file

.STB

Symbol table file produced by the Task Builder

.SYS

System file, usually for internal use

.TEC

TECO source file

.TES

TECO source program

.TMP

Temporary file created by a system program (deleted when you Logout or if
the disk is rebuilt)

.TSK

Executable BASIC-PLUS-2, COBOL, DIBOL, FORTRAN-77, or MACRO
program produced by the LINK command or the Task Builder

.TXT

ASCII text file

.ULB

Universal library file

.UNI

Default file type for universal library files

Protection Codes

You detennine who, if anyone, can have access to files you create by using
protection codes. RSTSIE displays the protection codes of files between angle
brackets « » in your directory listing. For example:
Name .Typ
FINISH. COB
START .BAS

Size

Prot

89
12

< 60>
< 60>

Name .Typ
TENK .RNO
ROAD .MAP

Size

Prot

130
3

< 60>
< 60>

SY: [52,20]

In the example, 60 is the default protection code that RSTSIE assigns. (On some
systems, the system manager may have chosen a different default protection
code.) If one of your files has a protection code of 60, only you (or a user with
additional privileges) can read, edit, or delete it. A protection code remains fixed
until you change it. See the section "Allowing Access to Files" in Chapter 3 for a
list of available protection codes and a description of how to assign them.

1-24 Getting Started with RSTS/E

1.5.5.2

Wildcards

Wildcards let you refer to a group of files all at once by specifying a pattern
of identification. You can use Wildcards to specify all files that have a common
element in their names.
For example, if you have the files TIMING.COB, TIMING.BAS, and TIMING.DAT
is your directory, you can display information about them by typing a wildcard (in
this case an asterisk) in place of the file type:
$ DIRECTORY TIMING. * <RET>

RSTSIE provides the following two wildcard characters:

1.5.6

•

Asterisk (*) - Use the * as a wildcard in specifying a PPN (for example,
[*,20], [52,*], or [*,*]) or in specifying file names or types (for example, *.BAS,
or MYFILE.*). You can also use Trailing Wildcards (for example, TEXT*.DAT
matches all files that start with TEXT).

•

Question mark (?) - Use the? as a wildcard to replace a single character
in a file name or type. The question mark wildcard will display all file
names containing the alphanumeric string, regardless of whether the single
character is present. (For example, specifying PROG?COB will display
PROG.COB, as well as PROGl.COB, PROG3.COB, and PROGB.COB, if those
files are present in the directory.)

Exceeding Your Disk Qu ota
On occasion, you may create more files thah your RSTSIE disk quota allows. A
disk quota is the amount of file storage space allocated to your account.
RSTSIE enforces two disk quotas for your account: a "logged-in" quota which is
enforced all the time you are using the system; and a "logged-out" quota, which is
enforced at Logout time. You cannot Logout if you have exceeded your quota; you
must first delete one or more files and then try again.
For example, if you created a file named BIRDS.TXT to practice editing text, but
you no longer need the file, you can delete it by typing:
$ DELETE BIRDS.TXT <RET>

If you try to Logout and find you have exceeded your disk quota, the system

displays a message similar to:
$ LOGOUT <RET>
Disk quota of 1000 exceeded by 128 blocks
Some file(s) must be deleted before logging out
$

In the previous example, RSTSIE will not let you Logout until you free at least
128 blocks of storage space. The Size column in the DIRECTORY command (see
Chapter 3) includes the blocks of storage space each file requires:
$ DIRECTORY <RET>

Name .Typ
VANISH. COB
STRIDR.BAS
FLAGS .DAT

Size
89
120
159

Prot

< 60>
< 60>
< 60>

Name .Typ
PATTYC . RNO
ROAD • MAP
TEST . MAC

Size
130
280
350

Prot
< 60>
< 60>
< 60>

SY:[52,20]

Total of 1128 blocks in 6 files in SY: [52,20]

Getting Started with RSTS/E

1-25

In general, it is a good idea to delete any files you do not need before attempting
to Logout. This practice saves space on the system. If you need all your files, you
can copy some of them onto magnetic tape to store them before deleting them
from your directory. See Chapter 6 for information about copying tHes to magnetic
tape.

1.6 Running a Program
You run most programs by typing RUN followed by the name of the program. A
program that can be run is called an "executable" program. Chapter 8 describes
the DCL commands for running, compiling, and linking programs on RSTSIE.
For more information about each programming language, refer to the appropriate
language manual and user's guide.
There are two types of executable programs: user programs and system
programs.
Some programs are referred to as user programs because they are created by a
system user. For example, if you create a BASIC-PLUS program named BANKER
that balances a checkbook, you can run the user program BANKER.BAC by
typing:
$ RUN BANKER.BAC <RET>

Other programs are referred to as system programs, because they are installed
as part of the system software. You can run system programs with one of the
following:
•

A DCL command - For example, you run the system's editor program (EDT)
by typing EDIT and pressing the Return key. EDIT is the DCL command
that runs the EDT program.

•

The RUN command - For example, you can switch to DCL from another
keyboard monitor by typing:
RUN $SWITCH <RET>
Keyboard Monitor to switch to?
$

DCL <RET>

1.7 Using DECnet/E
The DECnet facility links two or more Digital computer systems as a network.
DECnet refers to both the hardware (machinery) and software (programs)
involved in network operations. The DECnet software available on RSTSIE is
called DECnetJE.
If your system has DECnetJE, then your system is part of a network that allows
you to perform file, system, and programming operations on another system. To
find out if your system has DECnetJE, type the following command:
$ SHOW NETWORK <RET>

1-26

Getting Started with RSTS/ E

You should get one of the following responses:
•

If the system displays network information (see the "Displaying Network
Status" section), you can use DECnetIE on your system.

•

If DECnetIE is on your system but is not currently in operation, the system
displays:
$ SHOW NETWORK <RET>
No information

•

If your system does not have DECnetlE, the system displays the error
message:
?Command not installed

NOTE

If your system does not have DECnetlE, go on to Chapter 2.

You can use some of the commands in this manual over the network. The
commands and their qualifiers that you can use in network operations are labeled
with the symbol (N) in the command descriptions.
DECnetIE also lets you log in to another computer system from your account. You
can then use that system as though your terminal were connected to it directly.
Use the SET HOST command (see the next section) to log in to another system,
or node, on the network.

Th log in to another system on the network, you need to have an account and
password for that system. In addition, the network between your system and
the other system must be working. (You use the SHOW NETWORK command,
described in the next section, to check for available nodes on the network.)
You should know the following terms to become familiar with DECnetlE:
Network

The family of software modules, files, hardware components, and
facilities that ties different Digital systems together.

Node

A computer system that is connected to other computers by a network.
Node names are assigned by the system manager. There are three
types of nodes :
Host

The node you access with the SET HOST command.

Local

The node you logged in to before using the network; your
original system.

Remote

Any node in the network other than the local node.

Th summarize, the node of the network you first log in to is local, and the system
you reach by the network is remote. You connect to another system by specifying
the host and then logging in. However, if you want to communicate with a
system on the network from your local node, you can use DCL commands over
the network without logging in to the remote system.
For a complete description of the capabilities that DECnetIE has to offer, see the

Introduction to DECnet and the manuals in the DECnetlE documentation set.

Getting Started with RSTS/E 1-27

1.7.1

Displaying Network Status: SHOW NETWORK
The SHOW NETWORK command displays the systems you can connect to on the
network. To use the SHOW NETWORK command, type:
$ SHOW NETWORK <RET>

If the network is in operation, RSTSIE displays the names of the different nodes
your system can access. For example:
Active Node Volatile Summary as of ll-JUN-90 14:31:11
Executor Node = 1.135 (GARP)
State
Identification
Active Links
Remote Node

On
GARP DECnet/E V4.1
3
1.13 (SNOOPY)

State
Circuit

Remote Node

Reachable
DMC-l

1.20 (CLOUD9)

State
Circuit

Reachable
DMC-l

For a complete description of the elements in the SHOW NETWORK display, see
the DECnet/E System Manager's Guide.

1.7.2

Using the Network: SET HOST
The SET HOST command lets you log in to another computer from the system
you are currently logged in to. To use the SET HOST command, type:
$ SET HOST <RET>

RSTSIE prompts you for the node name with:
Node:

Enter the name of a node that is available on the network. For example, you
connect to a node named SPEEDY by typing:
Node: SPEEDY <RET>

A faster method is to type SET HOST and follow it directly by a node name, then
press RETURN. For example:
$ SET HOST SPEEDY <RET>

Mter the connection is made, the local node displays a message stating that the
connection has been established. You must have an account on the remote node
to log in. When the connection is established, you use the normal login dialogue
for that system. When you successfully log in, you can use the remote node as if
your terminal were connected to it directly.
When you are finished, use the LOGOUT command to Logout of the remote node.

Mter about five seconds, control returns to your local node.

1-28 Getting Started with RSTS/E

There are two ways you can end your session at the remote node and return
directly to the local node:
•

The first way, which Digital recommends for normal use, is to follow the host
system's normal Logout procedure. This deletes any temporary files you may
be using.

•

The second way is to type CTRLIP, which prompts you for a network command. For example:
<CTRL/P> <RET>
GARP::NET> EXIT <RET>

For more information on using the network, see the DECnet / E Guide to User
Utilities.

1.7.3

SET HOST Behavior
When you use SET HOST to connect to a remote system (using the NET utility),
commands that you enter on your local system are sent to the remote system for
processing. There are two character transfer modes available during a network
connection:
•

NORMAL mode

•

ODT mode

These modes are selected by typing CtrllP (followed by RETURN if the current
mode is NORMAL mode) and entering either ODT or NORMAL. In the default
NORMAL mode, characters are echoed by the local system but the command
is not sent to the remote system until a line delimiter is entered. ODT mode
instructs the NET program to open the local terminal in binary mode, causing
all characters to be echoed and sent to the remote system as they are typed.
NORMAL mode is the preferred mode, as it reduces network overhead for each
character typed.
If LINE_EDITING and RECALL are enabled on the local system, these functions
will also work when connected to a remote system, depending on the SET
HOST transfer mode in effect. If the connection is operating in ODT mode, then
the monitor will send all characters, including line editing and recall control
characters and escape sequences, to the remote system. If LINE_EDITING and
RECALL are enabled on the remote system (assuming that the remote system
is running RSTSIE VIO.O or an operating system that supports these functions),
those functions are performed by the remote system. Otherwise, the special
characters are processed according to the key definitions defined on the remote
system.
If the SET HOST connection is operating in NORMAL mode, and the LINE_
EDITING and RECALL terminal attributes are enabled, the monitor on your
local system handles all line editing and recall functions. The monitor treats all
characters typed as data to the NET program. This means that regardless of
your current level at the remote system (DCL, Keyboard Monitor, or Program),
all commands that you enter are maintained in your local system's program recall
buffer.

This behavior effectively gives you full command line editing and recal1 on any
remote system that you connect to. However, some applications on the remote
system may assign functions to keys defined in VIO.O as command line editing
or recall function keys. For example, DECmail-ll defines the Right Arrow key
as read next message and the Left Arrow key as read previous message. If you

Getting Started with RSTS/E

1-29

attempt to run DECmail-ll on a remote system while in NORMAL transfer mode,
and with LINE_EDITING enabled, the left and right arrow keys are intercepted
and processed by your local system as line editing keys, effectively blocking their
use by DECmail-ll on the remote system. Because there are more special editing
keys defined than in previous versions of RSTSIE, you may encounter remote
applications that do not process certain special keys correctly.
There are two ways to overcome these problems. The easiest is to switch to ODT
mode while connected to the remote system. Doing so opens your terminal in
binary mode, thereby disabling command line editing and recall, and allowing
any special line editing and recall keys to be passed to the remote system.
Alternatively, you can use the SET TERMINAL command to disable command
line editing (INOLINE_EDITING) or recall (INORECALL) or both prior to issuing
the SET HOST command to connect to the remote system.
Note that this does not represent an actual change in behavior compared to
earlier RSTSIE versions. Prior to VIO.O, arrow keys and other special function
keys did not work properly across a network connection unless you switched to
ODT transfer mode. Thus, the behavior is different, but consistent in relation to
your local system. Since all commands are read by the NET program, they are
stored and recalled as program-level commands.

1-30 Getting Started with RSTS/E

Chapter 2

Using RSTS/E Commands and Command
Procedures
This chapter shows how to use RSTSIE commands interactively. It also introduces
special groups of commands, called command procedures or command files, that
the system executes automatically for you.
This chapter explains how to enter:

•
•
•
•
•
•
•
2.1

Commands
File specifications
Qualifiers
Character string data
Numeric values
Date and time values
Command procedures

Understanding Command Formats
The commands in this manual are grouped by related functions. (For example,
Chapter 3 describes all commands that manipulate files.) Each command
description includes:
•

A brief description of the command's function

•

Syntax information (command parameters)

•

The command's qualifiers and defaults, if any

•

The command's prompts, if any

•

Detailed information about each command parameter and qualifier

Using RSTS/E Commands and Command Procedures

2-1

The command format descriptions in this manual use the terms in Table 2-1.
Table 2-1: Terms Used in Command Formats

Term.

Meaning

Format

The use of the elements in a command string.

Qualifiers

The elements that modify the effect of the command string in
someway.

Command Qualifiers

Qualifiers that modify the command itself.

File Qualifiers

Qualifiers that modify the treatment of a file included in the
command string.

Defaults

The assumptions RSTSIE makes when you enter the command string and do not use all the available parts of the
format.

Prompts

The text that RSTSIE displays to request your input.

Command Parameters

The parts of a command string that specify what the command is operating on. (For example, what file is affected by
the command.)

file-spec

A file specification.

input file-spec

The specification of a file to be used as input in the command
string.

output file-spec

The specification of a file to be used as output in the command string.

For example, the command format in Figure 2-1 lists the syntax elements for
using the COPY command. (See Chapter 3 for the complete COPY command
description.)

2-2

Using RSTS/E Commands and Command Procedures

Figure 2-1:

The COPY Command Format

COpy
Duplicating. Renaming. and Appending Files
The commands described in this section let you duplicate, rename, and append the
contents of files.

COpy
The COPY command duplicates one or more existing files, or concatenates two or
more files. You can use this command for local and network file specifications.
Format
COPY

input-file-spec[, ... j output-file-spec

Command Qualifiers

IAllocation = n
IBEFORE = date
IBLOCK _ SIZE = n
CLUSTER _ SIZE = n
ICREATE
I[NO]CONT,lCZUOUS
I[NOjLOG ~
IMODIFIED
I [NO jOVERLA Y
IPOSITION[ = nj
[=MIDDLEj
[=INDEXj
IPROTECTION~=
n
I[NOjQUERY N
I[NO]REPLACE N
ISINCE = date

Defaults

@
lLOG

INOOVERLAY
IPOSITION = 0

INOQUERY

Prompts

From: input-file-spec[ ,.. . ]
TO: output-file-spec
OK to replace existing file file-spec?

Use COpy to:
• Copy one file to another file
• Merge more than one file into a single file
• Copy a group of files to another group of files
For example, if you have a file named SMITH.MAR and you want to make a copy
of it as file JONES.JOE, you type:
$

COPY SMITH.MAR JoNES.JoE ®]

Using RSTS/E Commands and Command Procedures

2-3

Suppose you want to use COPY to copy all the files named JOKES and GAMES
in your account to one file named PARTY.TYM on disk DB2:.
In the following example, you specify that the files should not replace existing
files. Therefore, you include the following information in the command line:
•

A command qualifier (INOREPLACE)

•

Two input file-specs (JOKES.* and GAMES.*)

•

One output file-spec (DB2:PARTY.TYM)

The dialogue at your terminal looks like:
$ COPY/NOREPLACE <RET>
From:
JOKES.*,GAMES.* <RET>
To:
DB2:PARTY.TYM <RET>
File JOKES.l copied to DB2: [52, 20] PARTY.TYM
File JOKES.2 copied to DB2: [52, 20] PARTY.TYM
File GAMES.TXT copied to DB2: [52,20]PARTY.TYM
$

Note that RSTSIE prompts you for your input. This is called "interactive" mode,
meaning that you and the system are communicating directly with each other.
RSTSIE can also operate in "batch" mode, meaning that the system is executing commands in a command procedure. (A command procedure is a series of
commands that RSTSIE processes automatically without requiring input from
you.)
RSTSIE displays its DCL dollar sign ($) prompt when the COPY operation is
complete.

2.1.1

Entering Commands
The complete specification of a command, including the command name, command
qualifiers, parameters, and file qualifiers (if any), is called a command string.
Because you can continue a command on more than one line, RSTSIE uses the
term command string to define the entire command that is passed to the system.
By contrast, the term command line describes the part of a command string that
you type on one line.
The general format of a command string is:

$ command-name[lqualifiers ... J parameter[lqualifiers ...J[ ...]
Each item in a command must follow these rules:

2.1.2

•

At least one blank or tab character must separate the command name
from the first parameter; at least one blank must separate each additional
parameter from the previous parameter. Note that you can use multiple
blanks and tabs in all cases where a single blank is required.

•

Each qualifier must be preceded by a slash (/). You can enter any number of
blanks or tabs before or after the slash.

Continuing Commands on More than One Line
The maximum number of characters you can enter on one line is 132. However,
you can enter a command string on more than one line by using the continuation
character, a hyphen (-), as the last element on a command line.

2-4

Using RSTS/E Commands and Command Procedures

Command line continuation is especially useful when you enter a command and
want to specify many qualifiers, or when you place a command in a command
procedure and want to make the procedure more readable. For example:
$ PRINT MYFILE - <RET>
/AFTER=l7:00 - <RET>
/COPIES=20 - <RET>
/NAME=GUIDO <RET>

There is no restriction on the number of continued lines you can use to enter a
command. However, the total number of characters in a command string must
not exceed 255.

2.1.3

Entering Comments
Comments explain or document commands or files. You indicate a comment by
preceding it with an exclamation mark (!). For example, the following line in
a command procedure uses a comment to explain the use of the DIRECTORY
command in a control file:
$ DIRECTORY W: [*,*]

!W: is a logical name for disk DB2:

All the text (and spaces) starting at the exclamation point to the end of the
line is considered a comment. The comment does not affect the action of the
DIRECTORY command.
Comments are valid in the following positions:
•

As the first item on a command line; in this case, the entire line is considered
a comment and is not processed.

•

Following the last character in a command string, or after a hyphen that
signals continuation in a command line.

For example:
$ !THIS ENTIRE LINE IS A COMMENT <RET>
$ PRINT MYFILE - !
PRINT COMMAND COMMENT <RET>
Continue: /COPIES=3
3 COPIES, PLEASE <RET>

The system prints the "Continue:" prompt in the last line to show that what
follows is a continuation line.
When you continue a command on more than one line, RSTSIE uses the Continue:
prompt to indicate that it is still accepting the command. Note that the hyphen
to continue the command must come before the comment. Hyphens after the exclamation point (!) are ignored. This means that you cannot continue comments,
although the next line could read:
$ -

! Comment included. <RET>

In this last line, you have no command, just a comment.

2.1.4

Abbreviating Keywords
Keywords are the command names, qualifiers, or options that RSTS/E recognizes. You can abbreviate all RSTSIE keywords by truncating (abbreviating) them
to the first four characters. You can also abbreviate many of these keywords to
two or three characters, if the keyword remains unique. You can abbreviate:
•

Command names

•

Command keyword parameters
Using RSTS/E Commands and Command Procedures

2-5

•

Qualifiers

Qualifier keyword values

The following sections describe the rules for abbreviating keywords.

2.1.5

Abbreviating Command Names
You can abbreviate command names to two characters if the abbreviation is
unique. For example, the PRINT command is the only command that begins with
the characters "PR." Therefore, you can abbreviate the PRINT command to two
characters. The DEALLOCATE and DEASSIGN commands, however, have the
same first three characters, so you cannot abbreviate these commands to fewer
than four characters.

2.1.6

Abbreviating Parameters, Qualifiers, and Qualifier Arguments
You can also abbreviate parameters, qualifiers, and qualifier arguments to two
characters if the abbreviation is unique. For example, ISIZ is the minimmn
abbreviation of the ISIZE qualifier; fewer than three characters conflicts with
ISINCE. (Note that the slash (/) character is not considered when counting
characters.)
Some qualifiers permit a negative form. For example, /NOJOURNAL is the
negative form of the IJOURNAL qualifier. In applying the minimum fourcharacter abbreviation rule, do not count the NO prefix as the first two of the four
characters. In this case, the minimum abbreviation that guarantees uniqueness
is /NOJOUR.
The underscore C), as in the I[NO]D_LINES qualifier, is considered optional
syntax. This means that the minimmn abbreviation for guaranteed uniqueness is
ID_LIN and /NOD_LIN.

2.2 Entering File Specification lists
An input file parameter for many commands has the format:
file-spec[, ... ]
This format indicates that you can enter more than one file specification. You can
separate the file specifications with commas (,) or plus signs (+). See Table 2-2
for further discussion.
Any nmnber of blanks or tab characters can come before or fonow the commas or
plus signs. RSTS/E treats the list of file specifications as a single parameter.

2.2.1

Entering Entry Specifications
An entry specification parameter, used in PrintlBatch Services (PBS) commands,
has the format:
qu,eue-name:[ppn]entry-spec
This format indicates:
..

2-6

The queue in which the print or batch entry is to be placed.

Using RSTS/E Commands and Command Procedures

•

The project-programmer number (PPN) assigned to the entry.
If you do not specify a PPN, the default is your own. (Unless you have

sufficient privileges, you cannot specify a PPN different from your own.)
•

The name of the print or batch entry.

See Chapter 7 for more information on print and batch entries.

2.2.2

Entering Qualifiers
Commands can take one or both of the following types of qualifiers:
•

Command qualifiers

•

File qualifiers

Command qualifiers have the same meaning regardless of whether they appear
after the command name or after a parameter. For example:
$ PRINT/QUEUE=LPl: SPRING.SUM,FALL.SUM <RET>
$ PRINT SPRING.SUM,FALL.SUM/QUEUE=LPl: <RET>

In this example, the IQUEUE qualifier is a command qualifier; therefore, the two
PRINT commands are the same.
Unlike command qualifiers, file qualifiers can have different meanings depending
on where you place them in the command line. If you specify a file qualifier
immediately after a file specification parameter, it affects only the file it follows .
If you specify a file qualifier after the command name, it affects all the files
specified as parameters.
For example:
$ PRINT/COPIES=2 SPRING.SUM,FALL.SUM <RET>
$ PRINT SPRING. SUM/COPIES=2, FALL. SUM <RET>

The first PRINT command requests two copies of each of the files SPRING.8UM
and FALL.SUM. The second PRINT command requests two copies of the file
SPRING.SUM, but only one copy of FALL.SUM.
In some cases, you can specify file qualifiers only after a parameter-not after the
command name. (For example, the /LIBRARY qualifier used with the MACRO
command.) In this case, the qualifier description indicates that the qualifier can
apply only to a file parameter. In general, however, if you specify a file qualifier
following the command name, the qualifier applies to all files specified.

2.2.3

Determining Qualifier Defaults
Many of the command formats in this manual show defaults. When you do
not explicitly include a qualifier in a command line, RSTSIE assumes a default
qualifier. For example, when you copy a file, RSTSIE normally displays a message
confirming that the COPY operation was successful. If you type INOLOG in the
command line, you suppress the message. Otherwise, RSTSIE assumes the /LOG
qualifier and displays the message.

Using RSTS/E Commands and Command Procedures

2-7

2.2.4

Entering Qualifier Arguments
Many qualifiers can be followed by a keyword, file specification, character string,
or numeric value.
You must separate a qualifier and value with either an equal sign (=) or colon (:).
For example, the following specifications are the same:
/OUTPUT=DB1:NEW.DAT

/OUTPUT:DB1:NEW.DAT

Many qualifiers accept one keyword or variable value. This manual presents this
format as:
/qualifier=value

For example:
/COPIES=3
/DATE=MODIFIED

2.2.5

Entering Output File Qualifiers
Some qualifiers request output from a command and optionally accept a file
specification value. For example, the /LIST and /OBJECT qualifiers for the
compilers, as well as the /EXECUTABLE and /MAP qualifiers for the LINK
command, are output file qualifiers that fit into this category.
The following rules apply to output file qualifiers:
•

•

2-8

If the qualifier is present by default, the output file specification defaults to
your directory on the public disk structure and the name of the first input
file. The qualifier provides a default file type. For example:
Command

Output File

LINK A

A.TSK

LINKA,B

A.TSK

LINK [52,20]A,[52,20]B

A.TSK

LINKA.OBJ

A.TSK

If the qualifier does not specify an output file specification, the output file
specification defaults to your account on the public disk structure and the
name of the first input file. The qualifier provides a default file type. For
example:
Command

Output File

LINKlEXECUTABLE A

A.TSK

LINKlEXECUTABLE A,B

A.TSK

LINKlEXECUTABLE A.OBJ

A.TSK

Using RSTS/E Commands and Command Procedures

•

If you specify /LIST without a file specification, the listing goes where the
object file goes, but it has a .LST file type. If you do not specify an object file,

then the listing has the same name as the first input file, an .LST file type,
and is in your directory on SY:.
"

If you specify !MAP without a file specification, the map goes where the
executable file goes, but it has a .MAP file type. If you do not specify an

executable file, then the map has the same name as the first input file, a
.MAP file type, and is in your directory on SY:.
"

If the qualifier indicates a file specification for the output file, then any parts

entered in the file specification are used to name the output file, and no
default file name is supplied. For example:

2.2.6

Command

Output File

LINK A,BIEXECUTABLE=C

C.TSK

FORTRANILIST=A B+C

A.LST, B.OBJ

LINKlEXE=[52,20]A

[52,20]A.TSK

Entering Uppercase, lowercase, and Nonalphanumeric Characters
You should remember the following rules when you enter RSTSIE commands:
..

You can use any combination of uppercase and lowercase letters; both are
treated the same.

RSTS/E treats multiple blanks and tabs the same as a single blank.
RSTS/E ignores blanks and tabs at the beginning or end of the command
string, around commas and plus signs, around equal signs, and around colons
that delimit qualifier values. RSTSIE does not pennit blanks or tabs in file
specifications, dates and times, keywords, or numbers.

You can use quoted, or literal, strings in some RSTS/E commands (such as
REQUEST) and in network file specifications. A quoted string consists of
characters enclosed in quotation marks.

Using RSTS/E Commands and Command Procedures

2-9

Table 2-2 lists nonalphanumeric characters that have special meanings in
RSTSIE.

Table 2-2: Nonalphanumeric Characters
Symbol

Name

Meaning

Colon

A colon can serve one of the following functions:
•
•
•

2-10

Device name delimiter in a file specification.
Node name delimiter; used as a double colon (::).
Qualifier value delimiter; separates a qualifier
name from its value.

Slash

Qualifier delimiter.

Plus sign

List element separator for parameters.

Comma

List element separator for parameters.

Hyphen

Continuation character. As the last nonblank character in a command string, indicates that a continuation line follows. If the statement to be continued
contains a comment, the hyphen must be the last
nonblank character before the exclamation point.

[ ]

Square brackets

Directory delimiters in a file specification.

Question mark

Wildcard character in a file specification.

Equal sign

Qualifier value delimiter; separates a qualifier name
from its value.

Asterisk

Wildcard character in a file specification.

Period

File type delimiter in file specifications.

Exclamation point

Comment delimiter.

Quotation mark

Literal string delimiter.

Apostrophe

Symbol substitution delimiter.

Dollar sign

Command file character. Used as the first character
in first position of a command file statement. In a file
specification, denotes the directory [1,2], which is the
system library.

At sign

Executes a command procedure interactively.

<SPACE>

Space

Separates fields in a command string. Otherwise
ignored unless embedded in a string delimited by
quotation marks.

<TAB>

Tab

Separates fields in a command string. (Equivalent to
one space [blank] character; otherwise ignored.)

Using RSTS/E Commands and Command Procedures

2.2.7

Entering Dates and Times
Some RSTSIE commands let you specify a date or time when the command will
take effect. For example, you can print 10 copies of a file to be printed after 5:00
PM on a weekend, when fewer people need the line printer, by typing a line such
as:
$ PRINT NOTIN.NOW/COPIES=lO/AFTER=15-JUN-90:5:00PM <RET>

In RSTSIE, you can specify the following date and time formats:
•

Absolute - A specific date and time of day. For example:
15-Jun-1990:10:53:22

•

Relative - A date or time calculated from the current date or time. For
example:
+3DAYS or +2HOURS

•

Combinations of absolute and relative dates and times. For example:
TOMORROW+3DAYS-IHOUR

2.2.8

The IBEFORE, ISINCE, and IAFTER Qualifiers
You can specify a date with any command that allows the (SINCE or /BEFORE
qualifier. (Generally these commands are used for working with files.) The
(SINCE=date qualifier applies to files that are created or modified on or since
the specified date, depending on whether or not you also use the (CREATED or
!MODIFIED qualifier.
The /BEFORE=date qualifier applies to files that are created or modified before
the specified date, depending on whether or not you also use the (CREATED or
!MODIFIED qualifier.
You can use the (SINCE and /BEFORE qualifiers together to provide a range of
dates for file operations.
The (AFTER qualifier lets you specify a date, a time, or both. Use (AFTER with
commands that affect jobs in a batch or print queue, to indicate that the system
should not begin executing the batch job, or print the file, until after a specified
time.

2.2.9

Absolute Date and Time Formats
There are three formats for absolute dates:
•

The alphanumeric format is dd-mmm-yy, as in 23-MAR-90. In this format,
dd is the date of the month; mmm is the first three letters of the month; and
yy is the last two digits of the year, or the entire year (as in 1990). The yy
is optional-you can just type dd-mm. If you omit the year, RSTSIE assumes
the current year.

•

The numeric format is yy.mm.dd, as in 90.3.23 (for March 23, 1990). In this
format, yy is the last two digits of the year or the entire year (as in 1990);
mm is the month; and dd is the date of the month.

Using RSTS/E Commands and Command Procedures

2-11

•

Use these keywords to specify a date: TODAY, TOMORROW, or YESTERDAY.
NOTE

You can specify any date from 1-JAN-70 to 31-DEC-99, inclusive. If you
specify a date outside that range, you get the message:
?Invalid date

There are two formats for absolute times: 24-hour time and AMlPM time.
•

A 24-hour time has the form hh:mm. In this format, hh is the hour, in the
range 0 to 24, and mm is the minute, in the range 0 to 59. The minute is
optional. The default minute is 00. For example, 11 is equivalent to 11:00.
The limits of time formats are:
00:00 is midnight, and is considered the beginning of the specified date.
12:00 is noon.
24:00 is midnight, and is considered the end of the specified date.

An AMIPM time can be in the format hh:mmAM, hh:mmPM, or 12:00M. In
this format, hh is the hour, in the range 1 to 12; mm is the minute, in the
range 0 to 59; and M (for meridian) stands for noon. You can use either 00:00
or 24:00 to specify midnight.

•

2.2.10

Combinations of Absolute Dates and Times
The order for specifying both a date and time is date:time. For example:
23-JUN-90:11:00AM
TOMORROW: 1:00AM

If you specify just a time, RSTSIE assumes TODAY. If you specify just a date

when using the IAFTER qualifier, then RSTSIE assumes 11:59PM. (In other
words, the job processes after the end of the specified day.)

2.2.11

Syntax
The punctuation marks (syntax) in a time specification indicate the time value
you enter. If you specify both the date (dd-mmm-yy) and the time (hh:mm), you
must type the colon between the date and the time.
A line ending with a hyphen (-) is continued, rather than recognized as a part of
the date. For example:
$ PRINT/AFTER=15CONTINUE: <RET>

This PRINT command specifies 3:00 PM today, according to 24-hour time.

2-12

Using RSTS/E Commands and Command Procedures

2.2.12

Relative Date and Time Formats
In addition to absolute dates and times, you can also specify relative dates and
times. There are three formats for relative dates and times:
•

+ or -nD[AYS]. For example:
+23D or -2DAYS

•

+ or -nH[OURS]. For example:
+23H or -8HOURS

•

+ or -nM[INUTES]. For example:
+30M or -15MINUTES

You may specify these formats in any order or in any combination you choose.
If you specify a relative date, you mayor may not want to also specify either an
absolute or relative time, with the following results:
•

If you do specify an absolute time, then that time is used. For example,
PRINT/AFTER=3PM+2DAYS means 2 days from today at 3:00 PM.

•

If you do not specify an absolute time, but specify only a relative time, then
the time is calculated from the current time. For example (if it is currently
1:45 PM), PRINT/AFTER=TOMORROW+2HOURS means tomorrow at 3:45
PM.

•

If you do not specify a time at all, then time is not considered. For example,
PRINT/AFTER=05-AUG+3DAYS means first thing on August 9th; this has
the same result as specifying IAFTER=08-AUG.

Some other examples of specifying relative dates and times are:
•

To print out a listing three days from today starting at 3:00 PM, type:
PRINT/AFTER=3:00PM+3DAYS

•

To print a file tomorrow at the same time as today, type:
PRINT/AFTER=TODAY+OHOURS

or
PRINT/AFTER=+24HOURS

•

To set up a batch job named WEEKLY that resubmits itself every seven days

starting at 2 PM, type the following command in WEEKLY.COM:
SUBMIT/AFTER=2:00PM+7DAYS WEEKLY . COM

2.3 Using Command Procedures
Command procedures are files that contain DCL commands. You execute
these commands by running the procedure. Use command procedures to
execute sequences of commands you use during interactive terminal sessions or
commands you submit for batch processing. To fully understand how to use
command procedures on RSTSIE, see the RSTS / E Guide to Writing Command
Procedures.

Using RSTS/E Commands and Command Procedures

2-13

Command procedures can range from simple to complex. A simple command
procedure consists of one or more command lines for the DCL command
interpreter to execute. For example, the following command procedure deletes all
temporary (.TMP) files and then shows a directory listing:

DIRECT.COM
$ ! Delete .TMP files and show directory
$ DELETE *.TMP
$ DIRECTORY

A more complex command procedure performs program-like functions. It can:
•

Contain loops and error checking routines

Perform arithmetic calculations and input/output (110) operations

•

Manipulate character string data

•

Call or pass parameters to other command procedures

For example, the following command procedure displays all occurrences of files
with a .B2S file type in a user's account:

B2S.COM
$ ! Display all .B2S files
$ NEXT FILE

F$SEARCH ("_SY: * .B2S")

$ LOOP:
$ IF NEXT_FILE .EQS.

1111

THEN EXIT

$ WRITE 0 NEXT FILE
$ NEXT FILE = F$SEARCH()
$ GOTO LOOP

2.3.1

Creating Command Procedures
To create a command procedure, use either a text editor (such as EDT) or the

DCL CREATE command. The following example shows how to create a simple
command procedure using EDT:
$ EDIT/EDT RUN.COM <RET>
Input file does not exist
[EOB]
$ !Run three programs
$ RUN PROGl <RET>
$ RUN PROG2 <RET>
$ RUN PROG3 <RET>
<CTRL/Z>
*EXIT
RUN.COM 4 lines

2-14

Using RSTS/E Commands and Command Procedures

The next example shows how to create the same procedure using the DCL
CREATE command:
$ CREATE RUN.COM <RET>
$

!Run three programs

$ RUN PROGI <RET>
$ RUN PROG2 <RET>
$ RUN PROG3 <RET>

<CTRL!Z>
$

Note that the examples use the file type .COM. When you enter the at (@)
command at the DCL prompt, the command interpreter assumes that the at
sign (@) character is followed by the name of a file with the file type .COM. In
addition, if you enter the @ command without specifying a file, RSTSIE prompts
you for the file specification.

2.3.2

Formatting Command Procedures
When you create a command procedure, start each command line with a dollar
sign ($) character. The use of the $ character ensures that DCL will process the
command when you execute the procedure from another keyboard monitor such
as BASIC-PLUS. Omit the $ character for data lines.

2.3.3

Executing Command Procedures
You can execute command procedures in many different ways on RSTSIE systems.
For example:
•

At login time, using LOGIN.COM files

•

At DCL command level, using the at sign (@) command (or from any other
keyboard monitor, using the $ character before the @ command)

•

In batch processing, using the SUBMIT command

•

From inside another command procedure (nesting)

•

With the RUN command from any keyboard monitor, providing the command
file is executable

See the RSTS / E Guide to Writing Command Procedures for a complete description of each method of executing command procedures.

Using RSTS/E Commands and Command Procedures

2-15

Chapter 3

WORKING WITH FILES
This chapter describes DeL commands that are used in file operations.
Table 3-llists the commands as they appear in this chapter.
Table 3-1:

Commands for File Operations

Command

Meaning
Creating and Modifying Text Files

CREATE

Lets you enter text that you can save as a file.

EDIT

Starts the EDT text editor.
Displaying File Names and Files

DIRECTORY

Displays information about files in a directory.

TYPE

Displays the contents of individual text files at the terminal.
Deleting Files

DELETE

Deletes files from a directory.
Copying, Renaming, and Appending Files

COPY

Duplicates a file or concatenates files.

RENAME

Assigns a new name to a file.

APPEND

Copies a file to the end of another file.
Backing Up and Restoring a Directory of files

BACKUP

Creates a Backup set on a specified disk or magnetic tape.

BACKUPIDIRECTORY

Lists files contained in an existing Backup saveset.

RESTORE

Restores a RSTSIE disk or subset of that disk from a tape or disk Backup
set.

RESTOREIDIRECTORY

Allows Restore to lists files contained in an existing backup saveset.
Sorting and Merging Files

SORT

Invokes the PDP-ll SORT utility to reorder the contents of a file or files,
and combine several sorted files into a single output file.

(continued on next page)

WORKING WITH FILES 3-1

Table 3-1 (Cont):

Commands for File Operations

Command

Meaning
Sorting and Merging Files

MERGE

Invokes the PDP-ll MERGE utility to combine two through ten similarly
sorted input files and create a single output file.
Comparing Files

DIFFERENCES

Creates a new file that lists differences in the text of two other files. Use
DIFFERENCES to compare earlier versions of a file with its later versions.
Allowing Access to Your Files

SET PROTECTION

Specifies the protection code of a file to determine who, if anyone, can
read, modify, or delete a file. The /DEFAULT qualifier assigns the same
protection code to all the files you create in a session at the terminal.
Setting File Characteristics

SET FILE

3.1

Sets various characteristics of a specified file.

Creating and Modifying Text Files
The CREATE and EDIT commands let you create files in DCL.

3.1.1

CREATE
The CREATE command lets you enter text and save it as a file.
Although you will use the EDIT command more often than CREATE to create
files, the CREATE command is useful when you want to:
e

Preallocate (set) the size of a file

Create a file from a command procedure

There is less overhead when you preallocate the size of a file, because the system
assigns enough space for the file only once, rather than having to assign more
space several times as the file grows larger.
Because preaHocation causes less overhead, access to the file is faster. Allocating
the size of a file is not necessary, but it is occasionally useful if a program will be
using the file. Preallocation avoids possible overhead caused when the file size is
extended by the program's use.
You also preallocate the size of a file if you need a contiguous file of a specific size.
You must specify IALLOCATION with the ICONTIGUOUS qualifier.
While you are creating a file with the CREATE command, you can use the Delete
and CtrllU keys to delete text on the current line. When you are finished entering
text, you press Ctrl/Z to save the text as a file.

3-2

WORKING WITH FILES

Format
CREATE

file-spec

Command Qualifiers
IALLOCATION=n
ICLUSTER_SIZE=n
I[NO]CONTIGUOUS
IPOSITION=n
=MIDDLE
=INDEX
IPROTECTION=n
I[NO]REPLACE

Defaults
IALLOCATION=O
none
INOCONTIGUOUS
IPOSITION=O

none
none

Prompts
File: file-spec
OK to replace existing file filespec?

Command Parameters
File-spec

Specifies the name of the file to be created. You cannot use wildcard characters in
the file specification.

Command Qualifiers
I ALLOCATION=n
Creates space on the disk by forcing the initial allocation of the file to a number
of 512-character blocks, which you specify with n. The following example provides
three blocks of space to create a file named BOSTON.MAR:
$ CREATE BOSTON.MAR/ALLOCATION=3 <RET>

ICLUSTER_SIZE=n

Establishes the cluster size for a disk file. A cluster is a number of contiguous
blocks taken together as a unit. The cluster size is the minimum unit of allocation
for the file.
This qualifier is useful for large files. By specifying a large cluster size, you can
speed up random access to the data. See Appendix B for more information on
specifying cluster size.
ICONTIGUOUS
INOCONTIGUOUS

Indicates whether or not the file is to be contiguous, which means that the file
occupies consecutive physical disk blocks.
If you do not specify an allocation, or if the allocation is too small, you get the
following error message when the system tries to increase the size of the
contiguous output file:
?Protection violation

WORKING WITH FILES

3-3

IPROTECTION=n

Specifies the protection code of the file.
RSTSIE normally assigns files a protection code of 60, unless your system
manager has changed the default. If you use the SET PROTECTION/DEFAULT
command before creating the file, the protection code becomes the value you
specified as the default. See the SET PROTECTION command at the end of this
chapter.
IPOSITION=n
IPOSITION=MIDDLE
IPOSITION=INDEX

Specifies the starting position of the target file on disk. This qualifier is ignored
for files created on devices other than disks.
If you specify /POSITION with an argument, then that value indicates the start-

ing disk cluster at which to place the file. The minimum value is 0 (beginning
of disk) and the maximum value is the disk's maximum cluster number. If you
specify 0 (the default), the file is created at the first available cluster on the disk.
If you specify /POSITION=MIDDLE, the file is created at the first available
cluster past the middle of the disk.
If you specify /POSITION=INDEX, the file is created at the first available cluster
following the storage allocation table (SATT.SYS) on the disk.
IREPLACE
INOREPLACE

!REPLACE requests that if a file already exists with the same file specification as
the one you are creating, the existing file is to be deleted.
For example, if there is a file named BLACK.CAT in your directory, and you want
the file you are creating to replace the existing file, type:
$ CREATE BLACK.CAT/REPLACE <RET>

If the CREATE command is going to replace an existing file, but you do not
specify !REPLACE or INOREPLACE, DCL displays the prompt:
OK to replace existing filespec ?

You can reply with one of the following:
Y

Yes, replace the file

No, do not replace the file

<RET>

No, do not replace the file

INOREPLACE forces the CREATE command to fail if the file being created
already exists. In addition, it suppresses the "OK to replace existing filespec?"
prompt.
If you use the CREATE command in a command procedure, you should explicitly
specify either !REPLACE or INOREPLACE . This prevents DCL from issuing the
"OK to replace existing filespec?" prompt.

3-4 WORKING WITH FILES

3.1.2

EDIT
The EDIT command starts the EDT editor program, which lets you create and
edit text files.
This section provides basic command and syntax information for the EDIT
command. Th learn about editing text with the EDT editor, see the Introduction
to the EDT Editor, which is a tutorial manual that you can use at your terminal.
For details about each command and feature of EDT, see the EDT Editor Manual.
You can also get information about EDT while using it. EDT's help facility
provides a description about each of its editing commands. Mter you use the
EDIT command to start EDT, type HELP after the asterisk (*) prompt for help
text. (In keypad editing, you press the HELP key for help text. See the EDT
Editor Manual for details.)

Format
EDIT

file-spec

Command Qualifiers

Defaults

/[NO]COMMAND[=file-spec]
/[NO]CREATE
/EDT
/FORMAT =STREAM
/FORMAT =VARIABLE
/[NO]JOURNAL[=file-spec]
/[NO]OUTPUT[=file-spec]
/[NO]READ_ONLY
/[NO]RECOVER

/COMMAND=EDTI N I. EDT
ICREATE
/EDT
/FORMAT =STREAM
See discussion
/JOURNAL
/OUTPUT
/NOREAD_ONLY
/NORECOVER

Prompts
File: file-spec

Command Parameters
file-spec
Specifies the file to be created or edited using the EDT editor. If the file does not
exist, it is created.
The only part of the file specification that you must supply is the file name. EDT
does not provide a default file type when creating files; if you do not include a file
type, no file type is assigned.
You cannot use wildcard characters in the file specification.

WORKING WITH FILES

3-5

Command Qualifiers
ICOMMAN D[ =fi Ie-spec]
INOCOMMAND

Controls whether or not EDT reads a command file before prompting at the
terminal. If you specify a command file, EDT executes all commands in the file
before beginning the editing session. For example, if you have a file named
CHANGE.INI containing line editing commands, you use it when editing the file
RVN.DAT by typing:
$ EDIT RUN.DAT/COMMAND=CHANGE.INI <RET>

By default, EDT looks for a command file named EDTINI.EDT when you begin
an editing session. If the file EDTINI.EDT is in your directory on the public
structure, EDT uses the commands it contains when the session begins. If
you specify the /NO COMMAND qualifier, EDT does not read a command file
before beginning the editing session. To suppress the effects of the command file
EDTINI.EDT when you start an editing session with file RVN.DAT, type:
$ EDIT RUN.DAT/NOCOMMAND <RET>

Otherwise, the commands in the EDTINI.EDT file automatically affect your
editing session.
You cannot use wildcard characters in the command file specification.
ICREATE
INOCREATE

Controls whether or not to open a new file when the specified file does not exist.
The default is ICREATE .
IEDT

Makes sure that the EDIT command starts EDT, if your system manager has
changed the default on your system from EDT to another editor. Otherwise, you
do not need to use this qualifier.
For example:
$ EDIT/EDT NEWFIL.RNO <RET>

The EDT editor is invoked, so you can produce a file named NEWFIL.RNO.
IFORMAT=STREAM
IFORMAT=VARIABLE

Determines the format of the output file.
/FORMAT=STREAM creates the file in stream ASCII format. The default is
/FORMAT=STREAM. /FORMAT=VARIABLE creates the file in variable-length
format. See the RMS-ll User's Guide for information about stream and variable
file formats.
IJOURNAL[=file-spec]
INOJOURNAL

Controls whether or not a journal file is created for the editing session. A journal
file contains a copy of the edits you make to another file, from the beginning to
the end of the editing session. If your editing session ends abnormally (as in a
system failure or "crash"), you can restart EDT (using the !RECOVER qualifier)
and reinstate all commands from the aborted session.
When you begin an editing session, EDT automatically creates a journal file with
the same name as the input file and a .JOU file type. If you are editing a file
named RVN.DAT, for example, the journal file is named RUN.JOU.

3-6

WORKING WITH FILES

The command line to state explicitly that you want a journal file when you edit
RVN.DAT, and to name the journal file RVNDAT.VOl is:
$ EDIT RUN.DAT/JOURNAL=RUNDAT.VOI <RET>

If you specify the INOJOURNAL qualifier, no journal file is created.

If you omit the IJOURNAL qualifier or if you specify the qualifier without a file
specification, the editor creates a journal file with the same file name as your
input file and a default file type of .JOU. EDT also assumes a default file type of
.JOU if you specify a file name but not a file type when you use the IJOURNAL
qualifier.
Your directory contains the journal file when the system resumes operation after
a system crash. By default, EDT places the journal file in the same directory
and device as the output file, if you specified IOUTPUT when creating the file.
Otherwise, EDT uses the same directory and device as the input file.
For example, suppose you start a session to edit the existing file MARY.DAT, but
you want the finished output file to become file BETH.DAT:
$ EDIT MARY.DAT/OUTPUT=BETH.DAT <RET>

If the system crashes, the journal file is named BETH.JOU. You can then recover

from a system crash by typing:
$ EDIT MARY.DAT/OUTPUT=BETH.DAT/RECOVER <RET>

If you used the IOUTPUT qualifier to invoke EDT, you must also use it when

you recover the file. (The journal file does not "remember" the command line you
typed to begin the editing session.)
You cannot use wildcard characters in the journal file specification.
You cannot use INOJOURNAL if you specify INOREAD_ONLY.
IOUTPUT[=fi Ie-spec]
INOOUTPUT

Defines the file specification of the file created during the editing session. If you
do not specify the IOUTPUT qualifier, the output file replaces the input file, and
the previous version of the input file is saved as filename .BAK. EDT deletes any
previous file named filename.BAK.
For example, suppose you type:
$ EDIT PAPER.NUM <RET>

If you continue the editing session and then exit from EDT by saving your edits,

EDT automatically creates a new output file named PAPER.NUM. The file you
began the session with is renamed to PAPER.BAK.
If you want the output file to be named something other than the original file

name, you can specify the output file name explicitly. For example, the following
command line tells EDT to put the contents of the file you are about to update
into a file named SUPPLY.DAT:
$ EDIT PAPER.NUM/OUTPUT=SUPPLY.DAT <RET>

You cannot use wildcard characters in the file specification.

WORKING WITH FILES 3-7

You can suppress the creation of the output file with the INOOUTPUT qualifier.
For example:
$ EDIT PAPER.NUM/NOOUTPUT <RET>

Use of the INOOUTPUT qualifier does not suppress creation of the journal file.
You cannot use /OUTPUT if you specify !READ_ONLY.
IREAD_ONLY
INOREAD_ONLY

Controls whether EDT disables journaling and the creation of an output file
when you view a file. The !READ_ONLY qualifier is equivalent to specifying
INOOUTPUT and INOJOURNAL. You can use the !READ_ONLY qualifier to
examine files without modifying them.
The default is INOREAD_ONLY, which allows journaling and output.
I RECOVER
I NORECOVER

Determines whether EDT reads commands from a journal file before starting the
editing session. The !RECOVER qualifier is useful if you are editing a file and
the system crashes, as in the case of a power failure. The !RECOVER qualifier
lets you restore your work on the file. The default is INORECOVER, which tells
EDT not to recover the edits you made to the file.
For example, if you are editing file PAPER.NUM when the system ceases
operations, or crashes, you can use the !RECOVER qualifier to restore your work
when the system is back in operation:
$ EDIT PAPER.NUM/RECOVER <RET>

If you named the journal file something other than PAPER.JOU (for example,

to REAMS.DAT) when you began the previous editing session, use the following
command line when restoring your work:
$ EDIT PAPER.NUM/RECOVER/JOURNAL=REAMS.DAT <RET>

3-8

WORKING WITH FILES

3.2 Displaying File Names and Files
The DIRECTORY command displays information about files. Use the TYPE
command to display the contents of individual files.

3.2.1

DIRECTORY
The DIRECTORY command displays information about files.

Format
DIRECTORY

[file-spec[, .. .]]

Command Qualifiers
IBEFORE=date
IBRIEF
ICREATED
IDATE[=CREATEDj
[=MODIFIEDj
[=ALLj
INODATE
IFULL
IMODIFIED
IOUTPUT=file-spec
I[NOjPROTECTION
ISELECT=SIZE=n
=SIZE=MINIMUM=n
=SIZE=MAXIMUM=n
=SIZE=(MINIMUM=m,MAXIMUM=n)
ISINCE=date
ISIZE[=ALLOCATIONj
[=USEDj
INOSIZE
/TOTAL

Defaults
none
See discussion
none
INODATE

none
none
none
none
IPROTECTION
See discussion

none
ISIZE=USED
ISIZE
none

Prompts
If you type the DIRECTORY command and press the RETURN key, DCL lists the

files in your directory on the public structure. For example:
$ DIRECTORY <RET>
Name .Typ
FINISH. COB
START . BAS
TEMP16. TMP

Size
130
89
258

Prot
< 60>
< 60>
< 60>

Name .Typ
TEN
.K
ROAD . MAP

Size
4
3

Prot
< 60>
< 60>

SY: [52,20]

Total of 484 blocks in 5 files in SY: [52,20 ]

WORKING WITH FILES 3-9

You can see directory listings only of files to which you have access (read, write,
or execute). If you specify a file or directory which is not yours, and to which you
do not have access, one of the following error messages is displayed:
?File does not exist
?Can't find file or account

Command Parameters
file-spec[, ... ]
Specifies one or more files to be listed. If your installation has DECnetiE, you
can also specify the node on which the files are located. The default is the local
node.
The rules for using the file specification are:
•

If you do not enter a file specification, the DIRECTORY command lists all the

files in your directory on the system disk.
•

If you specify only a device name, the DIRECTORY command lists the files in

your directory on that device. For example, if you have files on a disk named
DBl:, you can type:
$ DIR DB1: <RET>

•

If you use wildcards for a file name or type, RSTSIE displays all files with

that name or type. For example, if your account contains files named RACE. 1,
RACE.2, and RACE.3, you can type:
$ DIRECTORY RACE.*

Th get information about all the files in the directories you have access to,
type:
$ DIRECTORY [*,*]*.* <RET>

This lists all files in all directories on the public disk structure. The first set
of asterisks (in [*,*]) corresponds to every account number. The second set of
asterisks (*. *) represents every file name and type.
•

If a file specification contains a file name and a wildcard for the file type, the

DIRECTORY command assumes all file types. Similarly, you can specify a
file type and a wildcard for the file name. Therefore, both of the following are
valid command lines:
$ DIRECTORY RACE.* <RET>
$ DIRECTORY *.1 <RET>

If you provide more than one file specification, separate the file specifications

with commas (,) or plus signs (+). You can use wildcard characters in the
directory specification, file name, or file type of a file specification to list all
files that satisfy the elements you specify. For example:
$ DIRECTORY RACE.1,*.DAT,DB1:*.* <RET>

3-10

WORKING WITH FILES

Command Qualifiers
IBEFORE=date

Specifies that only those files created or modified earlier than a given date be
listed. See Chapter 2 for the syntax to specify dates.
You can use the /BEFORE qualifier with either the /CREATED or /MODIFIED
qualifier. For example:
$ DIRECTORY/CREATED/BEFORE=28-JUN-90 <RET>
$ DIRECTORY/MODIFIED/BEFORE=TODAY <RET>

If you omit the /BEFORE qualifier, RSTS/E displays the files without regard to

their dates.
You can use /BEFORE only when listing files on the local (your own) node.
IBRIEF

Lists only the file name and type of each file. If you specify /BRIEF, you do not
see the number of blocks for the files or their protection codes. For example:
$ DIRECTORY/BRIEF <RET>

Name . Typ
SY: [52,20]
ROAD . MAP

Name . Typ

TEMP25.TMP

STRIDE.TXT

Name . Typ
PACE

.DAT

4 files 25 blocks

If you do not specify /BRIEF, the sizes and protection codes are also included in

the display.
ICREATED

Selects the files according to their dates of creation. Use the /CREATED qualifier
only with the !BEFORE or /SINCE qualifiers. For example:
$ DIRECTORY/BEFORE=10-JUN-90/CREATED <RET>

Name .Typ
ROAD . MAP
PACE .DAT

Size
Prot
4
< 60>
8
< 60>

Name .Typ
STRIDE.TXT

Size
21

Prot
< 40>

SY: [52,20]

Total of 33 blocks in 3 files in SY: [52,20]

Do not use /CREATED with the /MODIFIED qualifier. (You can select files either
according to their date of creation or date of modification, but not both.) Mter a
file is created, any later updates cause the file to be modified.
By default, the selection of files according to a date uses the creation date.
You can use /CREATED only when listing files on the local (your own) node.
IDATE=CREATED
IDATE=MODIFIED
IDATE[=ALL]

The /DATE qualifier causes the DIRECTORY listing to include the date when
a file was created or last accessed, or both. If you specify /DATE without an
argument, /DATE=ALL is the default.
/DATE=CREATED requests information about the file's creation date and time:
$ DIRECTORY/DATE=CREATED <RET>

Name .Typ
ROAD .MAP

Size
4

Prot
< 60>

Date
14-Jun-9 0

Time
10:13 AM

SY: [52,20]

Total of 4 blocks in 1 file in SY: [52,20]

WORKING WITH FILES

3-11

/DATE=MODIFIED displays the date when the file was last updated or accessed:
$ DIRECTORY/DATE=MODIFIED <RET>
Name .Typ
Size Prot
SY: [52,20]
ROAD . MAP
4
< 60>
40> 14-Jun-90

Access

Name .Typ

08-Jun-90

STRIDE.TXT

Size
21

Prot

Access

Total of 25 blocks in 2 files in SY: [52,20]

/DATE=ALL provides date and time information about the creation and access of
a file:
$ DIRECTORY/DATE=ALL <RET>
Name .Typ
ROAD . MAP

Size
4

Prot
< 60>

Access
Date
08-Jun-90 14-Jun-90

Time
04:25 PM

SY:[52,20]

Total of 4 blocks in 1 file in SY: [52,20]

INODATE
Lists information about files but does not include dates. Unless you specify
/DATE, the /NODATE qualifier is assumed. For example:
$ DIRECTORY/NODATE <RET>

Name .Typ
ROAD . MAP

Size
4

Prot
< 60>

Name .Typ
STRIDE.TXT

Size
21

Prot
< 40>

SY: [52,20]

Total of 25 blocks in 2 files in SY: [52,20]

You can use /DATE and /NODATE only when listing files on the local (your own)
node.

IFULL
Lists the following items for each file:

•
•
•
•
•
•
•

Name
Type
Number of blocks used
Protection
Date last accessed or modified
Creation date and time
Cluster size

•
•

Run-time system name

•

File attributes, if any

Position of first block in file

The /FULL qualifier implies the qualifiers /DATE=ALL and !PROTECTION as
defaults. The /FULL qualifier also includes information about the file's cluster
size (in the Clu column) and position on the disk (in the Pos column). Often the
/FULL qualifier is used with a file specification. For example:
$ DIRECTORY/FULL RACE.* <RET>

Name.Typ Size Prot
Access
Date
Time
Clu
RTS Pos SY:[52,20]
RACE .1 4
<60> 20-Jun-90 20-Jun-90 01:02 PM 4 ... RSX 22699
<60> 20-Jun-90 20-Jun- 90 09:55 AM 4 ... RSX 23284
RACE .2 3
Total of 7 blocks in 2 files on SY: [52,20]

3-12

WORKING WITH FILES

IMODIFIED

Selects files according to the last date the file was modified. Use this qualifier
only with the !BEFORE or /SINCE qualifiers. For example:
$ DIRECTORY/MODIFIED/BEFORE=12-JUN-90 <RET>

Name .Typ
ROAD . MAP

Size
4

Prot
< 60>

Name . Typ
STRIDE.TXT

Size
21

Prot
< 40>

SY:[52,20

Prot
< 40>

SY: [52,20]

Total of 25 blocks in 2 files in SY: [52,20]
$ DIRECTORY/MODIFIED/SINCE=18-JUN-90

Name . Typ
ROAD • MAP
RACE .1

Size
4
3

Prot
< 60>
< 60>

Name .Typ
STRIDE.TXT

Size
21

Total of 28 blocks in 3 files in SY: [52,20]

Note that this display lists only the file name and type, file size, and protection
code. Use IDATE=MODIFIED to display the dates of file access.
Do not use /MODIFIED with the /CREATED qualifier. (The date you specify
can apply only to the creation or modified date; thus, you cannot specify both
/CREATED and /MODIFIED.) After a file is created, any later updates cause the
file to be modified.
You can use /MODIFIED only when listing files on the local (your own) node.
IOUTPUT=file-spec

Creates a file containing the output of a DIRECTORY listing, instead of displaying the output at your terminal. You must include a file name with the /OUTPUT
qualifier. If you omit the file type in the file specification, the default type is .DIR.
For example, the following command line puts the directory listing into a file
named RACES.DIR:
$ DIRECTORY/OUTPUT=RACES <RET>
$ TYPE RACES.DIR <RET>

Name .Typ
ROAD . MAP
RACE .1

Size
4
3

Prot
< 60>
< 60>

Name . Typ Size
STRIDE.TXT 21

Prot
< 40>

SY: [52,20]

Prot

SY: [52,20]

Total of 28 blocks in 3 files in SY: [52,20]
$ DIRECTORY RACES <RET>

Name .Typ
RACES.DIR

Size
2

Prot
< 60>

Name . Typ

Size

Total of 2 blocks in 1 file in SY: [52,20]

Note that the output file has the type .DIR.
You cannot use wildcard characters in the output file specification.
IPROTECTION
INOPROTECTION

Specifies the protection code of files to be in the directory listing.
You can use this qualifier only when listing files on the local (your own) node.

WORKING WITH FILES 3-13

/SELECT=SIZE=n
/SELECT=SIZE=MINIMUM=n
/SELECT=SIZE=MAXIMUM=n
/SELECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:
n

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or
equal to n.

MAXIMUM=n

Selects only those files with size less than or
equal to n.

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

/SINCE=date

Specifies that only those files created or modified on or after a specified date be
displayed.
You normally use the ISINCE qualifier with either the ICREATED or /MODIFIED
qualifier. If you omit the ISINCE qualifier, you obtain all the files, regardless of
creation date. The date can be either TODAY or YESTERDAY, or a date in the
format dd-mmm-yy or yy.mm.dd (as in 12-MAY-90 or 90.5.12). For example:
$ OIRECTORY/CREATEO/SINCE=06-APR-90 <RET>

Name .Typ
ROAD . MAP
RACE .1

Size
4
3

Prot
< 60>
< 60>

Name .Typ Size
STRIDE . TXT 21

Prot
< 40>

SY: [52,20]

Total of 28 blocks in 3 files in SY: [52,20]

You can use ISINCE only when listing files on the local (your own) node.
/SIZE=ALLOCATION
/SIZE=USED

The ISIZE qualifier lists the number of blocks a file either uses or is allocated.
Compare the following two examples:
$ OIR *.LOG/SIZE=USED <RET>

Name .Typ Size
BAR
.LOG
3
LINK .LOG 12

Prot
< 60>
< 60>

Name .Typ Size
Faa
.LOG
6
HELP .LOG
6

Prot
< 40>
< 60>

SY: [52,20]

Total of 27 blocks in 4 files in SY: [52,20]
$ OIR *.LOG/SIZE=ALLOCATION <RET>

Name .Typ Size
BAR
.LOG
4
LINK .LOG
12

Prot
< 60>
< 60>

Name .Typ Size
Faa
.LOG
HELP
.LOG

8
8

Prot
SY: [52,20]
< 40>
< 60>

Total of 32 blocks allocated in 4 files in SY: [52,20]

The first example shows ISIZE=USED, which is the default. The Size column
shows the number of blocks used by each file . By contrast, the Size column in the
second example shows the number of blocks allocated to store each file. This may
be larger because disk space is allocated in multiples of the file's cluster size.
You can use ISIZE only when listing files on the local (your own) node.

3-14

WORKING WITH FILES

INOSIZE
The /NOSIZE qualifier suppresses information on file size. The default is /SIZE.
ITOTAL
The trOTAL qualifier displays the total amount of space your files require,
without listing information about each file. For example:
$ DIRECTORY/TOTAL <RET>
SY: [52,20]
Total of 647 blocks in 24 files in SY: [52,20]

You can use trOTAL only when listing files on the local (your own) node.

WORKING WITH FILES

3-15

3.2.2 TYPE
The TYPE command displays the contents of a text file (as opposed to a binary or
temporary file) at the terminal.

Format
TYPE

[node::]file-spec[, ...]

Command Qualifiers

Defaults

IBEFORE=date
I[NO]CONFIRM
ICREATED
I[NO] LOG
IMODIFIED
I[NO]QUERY ([N))
ISELECT=SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
ISINCE=date

none
INOCONFIRM
none
INOLOG
none
INOQUERY
See discussion

none

Prompts
File: file-spee[, ... ]

For example, you can display the contents of the file TRAIN. TXT:
$ TYPE TRAIN.TXT <RET>
Even though it was difficu l t to
undertake a new running regime,
I was amazed at how soon I was
able to increase my daily mileage.

You can control the display of a file in any of the following ways:
•

'lb temporarily halt the output, use CtrllS. To resume output where it was
interrupted, use CtrllQ. This works only if your terminal has the TTSYNC
characteristic set. (See Chapter 5 for more information on setting terminal
characteristics.) On VT100 terminals you can also press the NO SCROLL
key to stop and restart output. On VT200 terminals you can press the HOLD
SCREEN key to stop and restart output.

•

'lb suppress the display but continue command processing, use CtrllO. If you

press CtrllO again before processing is completed, output resumes at the
current point in command processing.
•

3-16

'lb stop command execution entirely, press CtrllC. The use of CtrllC returns
you to DCL command level.

WORKING WITH FILES

Command Parameters
file-spec[, ... ]
Specifies one or more files to be displayed. If your insta Hat.ion has DECnetlE,
you can specify the node where the files are located. You can also use wildcards.
If you want to display more than one file, separate the file specifications with
commas (,) or plus signs (+). In either case, RSTSIE displays the files in the order
you specify. The TYPE command allows wildcards in place of the directory, file
name, and file type fields. The following command line contains wildcards and
commas:
$ TYPE *.TXT,ROAD.MAP,RACE.* <RET>

This command line displays the contents of all files having the file type .TXT, the
file ROAD.MAP, and all files named RACE.

Command Qualifiers
IBEFORE=date
ISINCE=date
ICREATED
IMODIFIED
Displays files created or modified before or since the specified date. See Chapter 2
for information on specifying dates and times.

The following example displays all data files created before Ol-Jun-90:
$ TYPE/CREATED/BEFORE=Ol-Jun-90 *.DAT OLDWRK.DAT <RET>

The following example displays all files that were modified today:
$ TYPE/MODIFIED/SINCE=TODAY *.* NUWORK.WED <RET>

ICONFIRM
INOCONFIRM
Controls whether or not a prompt appears requesting permission to display each
file. This qualifier is synonymous with IQUERY. The default is INOCONFIRM.
IlOG
INOlOG
Controls whether or not a message appears for each file displayed. The default is
INOLOG.
IQUERY
INOQUERY
Controls whether or not the system displays the name of each file you request
and asks if you want to see the file . (The IQUERY qualifier is useful only when
you use wildcard file specifications in the TYPE command line.)

For example, if you have eight files in your directory with the file type .TXT, you
can type:
$ TYPE *.TXT/QUERY <RET>

WORKING WITH FILES

3-17

DeL prints a file specification followed by a question mark (?) prompt. You can
reply by typing one of the following responses:
Y

Yes, display the file

No, do not display the file

<RET>

No, do not display the file

Quit; return to command level

For example:
[52,20]TRAIN .TXT? N <RET>
[52,20]STRIDE.TXT? Y <RET>
Hill training taught me that
short, quick steps are good for
running uphill. Longer strides
are best for downhill inclines
and straightaways.
[52,20]PACE
$

.TXT? <Ctrl/Z>

/SELECT=SIZE=n
/SELECT=SIZE=MINIMUM=n
/SELECT=SIZE=MAXIMUM=n
/SELECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:
n

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or
equal to n.

MAXIMUM=n

Selects only those files with size less than or
equal to n.

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

3-18 WORKING WITH FILES

3.3 Deleting Files: DELETE
The DELETE command pennanently removes a file from a directory.

Format
DELETE

file-spec[, ...]

Command Qualifiers
IBEFORE=date
I[NO]CONFIRM
ICREATED
IERASE
I[NO]lOG (N)
IMODIFIED
I[NO]QUERY (N)
ISElECT=SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
ISINCE=date
I[NO]WARNINGS

Defaults
none
INOCONFIRM
none
none
IlOG
none
INOQUERY
See discussion

none
/WARNINGS

Prompts
Files: file-spec[, ... )

For example, if you want to delete the file BETH.DAT, type:
$ DELETE BETH.DAT <RET>

Command Parameters
file-spec[, ... )

Specifies the name of one or more files to be deleted. If your installation has
DECnetlE, you can specify the node where the files are located.
Each file specification must contain a file name and a file type. You can specify
wildcard characters for the directory, file name, or file type. For example:
$ DELETE DB2:RACE.* <RET>

To delete more than one file, separate the file specifications with commas (,) or
plus signs (+). If you omit the account specification or device name, RSTSIE uses

your directory and the system disk. For example:
$ DELETE ROAD.MAP,*.TXT+STRIDE.* <RET>

WORKING WITH FILES

3-19

Command Qualifiers
IBEFORE=date

Specifies that only the files dated earlier than a particular date be deleted. The
/BEFORE qualifier is useful only when you include wildcard characters in the file
specification.
Use the ICREATED or /MODIFIED qualifiers in conjunction with /BEFORE to
request that RSTSIE delete only files created or modified before the specified date.
For example, suppose you have files named RESULT.A, RESULT.B, and
RESULT.C in your directory, and you created file RESULT.C today. To delete
the files created before today, type:
$ DELETE/BEFORE=TODAY RESULT.* <RET>
RESULT.A deleted
RESULT.B deleted

You can use /BEFORE only when deleting files on the local (your own) node.
ICONFIRM
INOCONFIRM

Displays each file specification and asks if you want to delete that file.
/CONFIRM is synonymous with IQUERY. The default is /NOCONFIRM.
ICREATED

Specifies that only files created within a defined time period be deleted. Use the
ICREATED qualifier with either the /BEFORE or ISINCE qualifiers.
For example, if you do not want to save any of the files you created today, type:
$ DELETE/CREATED/SINCE=TODAY <RET>

You can use ICREATED only when deleting files on the local (your own) node.
IERASE

Specifies that you want to zero the file prior to deleting it. This qualifier is useful
if you want to erase a file for security purposes.
For example, to erase the file JIM. LOG, type:
$ DELETE/ERASE JIM. LOG <RET>
JIM.LOG erased and deleted

IlOG
INOlOG
Controls whether the DELETE command displays the file specification of each file
after its deletion.

The default is /LOG; normally the DELETE command displays the names of files
after it deletes them. For example:
$ DELETE RISTUS.ONE <RET>
RISTUS.ONE deleted

You can request the deletion message explicitly with /LOG:
$ DELETE/LOG PETER.WRK <RET>
PETER . WRK deleted

Note that the /NOLOG qualifier suppresses the usual message:
$ DELETE/NOLOG ROAD.MAP <RET>

3-20 WORKING WITH FILES

IMODIFIED

Specifies that only files modified within a defined time period be deleted. Use the
!MODIFIED qualifier with either the !BEFORE or ISINCE qualifiers.
For example, if you want to delete all files that have not been modified since June
11, type:
$ DELETE/MODIFIED/BEFORE=ll-JUN <RET>

A file's revision date is updated whenever the file is modified. (Your system
manager may have changed this, so that the date is updated whenever the file is
read or modified.)
You can use !MODIFIED only when deleting files on the local (your own) node.
IQUERY
INOQUERY

Specifies that you want to select files to be deleted. Use the IQUERY qualifier
when you use a wildcard in the command line, so you can avoid deleting files
unintentionally. The default is /NO QUERY.
For example, suppose you want to delete some of your files with a .DAT file type.
The command line is:
$ DELETE * . DAT/QUERY <RET>

DCL prints a file specification followed by a question mark (?) prompt. You can
reply by typing one of the following responses:
Y

Yes, delete the file

No, do not delete the file

<RET>

No, do not delete the file

Quit; return to command level

The display at your terminal looks similar to:
[52,20]WRI TE .DAT? N <RET>
[52,20]MANUAL.DAT? Y <RET>
MANUAL.DAT deleted
[52,20]PACE

.DAT? <Ctrl/Z>

ISELECT=SIZE=n
ISELECT=SIZE=MINIMUM=n
ISELECT=SIZE=MAXIMUM=n
ISELECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:
n

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or
equal to n.

MAXIMUM=n

Selects only those files with size less than or
equal to n.

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

ISINCE=date

Specifies that only the files dated on or after a particular date be deleted.
A file is implicitly modified on the date it was created. Therefore, a file's date of
modification never exceeds its date of creation.
WORKING WITH FILES

3-21

Use the /CREATED or /MODIFIED qualifier to request that only files created or
modified on or after the specified date be deleted. If you do not specify /CREATED
or !MODIFIED, the DELETE command deletes all files created since the specified
date.
For example, the following command line deletes all files created on or after June
11:
$ DELETE/SINCE=ll-JUN *.* <RET>

1b delete all files named RACE that were modified since April 6, type:
$ DELETE/MODIFIED/SINCE=06-APR RACE.* <RET>

You can use /SINCE only when deleting files on the local (your own) node.
IWARNINGS
INOWARNINGS

Displays an error message if the specified files are not found. The default is
!WARNINGS.

3-22 WORKING WITH FILES

3.4 Copying, Renaming, and Appending Files
This section describes commands that let you copy, rename, and appenli the
contents of files.

3.4.1

COpy
The COPY command duplicates one or more existing files, or concatenates two or
more files. You can use this command for local and network file specifications.
Use COpy to:
•

Copy one file to another file

•

Merge more than one file into a single file

•

Copy a group of files to another group of files

For example, if you have a file named SMITH.MAR and you want to make a copy
of it as file JONES.JOE, you type:
$ COPY SMITH.MAR JONES. JOE <RET>

The following command copies all of your files on the public structure (SY:) to a
tape (MTO:). (If the tape is in DOS format, the files are copied to your PPN on
the tape.) For example:
$ COpy SY:*.* MTO: <RET>

'Ib copy every file on a tape (MTO:) into your directory on the public structure
(SY:), type:
$ COPY MTO: [*,*]*.* *.* <RET>

If you copy files from ANSI tape to disk, you do not need to include the [*,*]
directory specification. (ANSI format tapes do not have directories.)
When you specify more than one input file and a single output file, the COPY
command merges all the input files into the output file:
$ COPY RABBIT.l,RABBIT.2,RABBIT.3 BUNNY.ALL <RET>

The example merges a copy of files RABBIT.1, RABBIT. 2, and RABBIT.3 into one
file named BUNNY.ALL.

If you specify more than one input file and give an output file specification that
contains a wildcard character, the COPY command creates one output file for
each input file:
$ COpy HARE.l,HARE.2,HARE.3 BIGFUT.* <RET>

The example copies files HARE.1, HARE.2, and HARE.3 into files named
BIGFUT.1, BIGFUT.2, and BIGFUT.3, respectively.
Similarly, the following example copies all files named ONE into files named
TWO, with the same file types:
$ COPY ONE.* TWO.* <RET>

WORKING WITH FILES

3-23

You can specify multiple input files in any of the following ways :
•

Separate input file specifications with commas (,) or plus signs (+). For
example:
$ COpy ROAD.LST,RACE.DAT,ENTRY.LST RESULT.MRG <RET>

The input files ROAD.LST, RACE.DAT, and ENTRY.LST are copied in that
order into an output file named RESULT.MRG.
•

Specify wildcard characters in place of the directory specification, file name,
or file type of an input file specification. The following example copies all
COBOL source files on D:[160,*] to the public structure:
$ COPY D: [160,*)*.CBL SY:*.* <RET>

The expression D:[160,*] means all directories on disk D: with project number
160. For example, directories D:[160,5],D:[160,25], and D:[160,39]. All
COBOL source files (*.CBL) on D:[160,*] are copied to the public structure
(SY:) into files of the same name and type. You must have access to each of
these files to use this command string.
The COPY command creates multiple output files when you specify multiple
input files and do one of the following:
•

Include asterisk wildcard characters (*) in the output directory specification,
file name, or file type fields. For example:
$ COpy RACEl.*,ROAD.MAP DBl:*.* <RET>

•

Omit the output file name, or omit the file type and its preceding period
(either of which is equivalent to specifying a wildcard).

When you specify a wildcard for any part of the output file specification, the
COpy command uses the corresponding part of the input file specification.

Format
COpy

[node::]input-fiJe-spec[, .. .]

Command Qualifiers
IAllOCATION=n
IBEFORE=date
IBlOCK_S IZE=n
IClUSTER SIZE=n
I[NO]CONFIRM
ICREATED
I[NO]CONTIGUOUS (N)
I[NO]lOG (N)
IMODIFIED
I[NO]OVERLAY
IPOSITION[=n]
[=MIDDlE]
[=INDEX]
IPROTECTION=n
I[NO]QUERY (N)
I[NO]REPLACE (N)
I[NO] RETAIN_ DATES

3-24

WORKING WITH FILES

[node::]output-file-spec
Defaults
none
none
IBlOCK_SIZE=512
none
INOCONFIRM
none
See discussion
IlOG
none
INOOVERLAY
IPOSITION=O

none
INOQUERY
See discussion
INORETAIN_ DATES

/SELECT =SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
/SINCE=date
ITRANSFER--,MODE=n
=BLOCK
=RECORD

See discussion

none
ITRANSFER_ MODE=AUTOMATIC

Prompts
From: input-file-spec[, ... ]
To: output-file-spec
OK to replace existing file file-spec?

Command Parameters
input-file-spec[, ... ]
Specifies one or more input files to be copied. If you specify more than one input
file, separate them with either commas (,) or plus signs (+). You can use wildcard
characters for the directory, file name, or file type.
The following example uses wildcards and commas:
$ COPY *.TXT,RACE.I,RACE.2 FINISH.TXT <RET>

This command line copies all files with the type .TXT, and files RACE.l and
RACE.2 into a file named FINISH.TXT.

output-file-spec
Specifies the name of the file into which the input files are to be copied.
You must specify at least one part of the output file specification.
If you do not specify a device or directory, the COPY command uses the public
structure and your own directory. For other parts that you do not specify, the
COpy command uses the corresponding field of the input file specification.
If you specify an asterisk wildcard character (*) in place of the file name or file
type of the output file specification, the COPY command creates one or more
output files, based on the input file specification. It uses the corresponding part
of the input file specification to name the output file.

For example, assume you have files NAME.l, NAME.2, and NAME.3 in your
directory. To copy these files into duplicates named NEW.l, NEW.2, and NEW.3,
you type:
$ COPY NAME.* NEW.* <RET>

You can use wildcard characters in the directory specification of an output file.
For example, the following command copies all files in all directories on the public
structure onto DBl:, into the corresponding directory, file names, and file types:
$ COpy [*, * 1* . * DBI: [*, * 1

The preceding command line copies all files in all directories onto a disk named
DBl:. The file names remain the same because you do not specify an output file
name.

WORKING WITH FILES

3-25

The ability to copy files depends on the file protection codes and whether or not
you have write access to the directory to which you are copying them.

Command Qualifiers
I ALLOCATION=n

Creates space on the disk by forcing the initial allocation of the output file to
a number of 512-byte blocks, which you specify with n. The following example
provides three blocks of space to copy the file PAPERNUM into SUPPLY.DAT:
$ COPY PAPER.NUM SUPPLY.DAT/ALLOCATION=3 <RET>

If you do not specify the initial allocation of the output file, then RSTSIE
determines it by the size of the input file being copied.

You can use IALLOCATION only if the input and output files are on the local
(your own) node.
IBEFORE=date
ISINCE=date
ICREATED
IMODIFIED

Copies files created or modified before or since the specified date. See Chapter 2
for information on specifying dates and times.
The following example copies all data files created before 01-Jun-90 into a file
named OLDWRKDAT:
$ COPY/CREATED/BEFORE=Ol-Jun-90 *.DAT OLDWRK.DAT <RET>

The following example copies all files that were modified today into a file named
NUWORKWED:
$ COPY/MODIFIED/SINCE=TODAY *.* NUWORK.WED <RET>

IBLOCK_SIZE=n

Lets you specify a block size for output to magnetic tape. For example:
$ COPY MYFILE.TXT

MMO:MYFILE.TXT/BLOCK_SIZE=2048

The argument of the IBLOCK_SIZE=n qualifier must be an even integer in the
range of 18 to 4096 bytes. The default is 512 bytes.
If you are copying a large file, a larger block size can be useful because it reduces
the number of interblock gaps that are needed; therefore, you can fit more data
onto a tape. On the other hand, a small block size is often preferable for a small
file, since it reduces the amount of space wasted at the end of the file.

If you specify an invalid value for n, the COPY command prints the error message
?Bad block size.
The IBLOCK_SIZE=n qualifier has the following restrictions:

3-26

•

The qualifier can be used only for magnetic tape. Its use on disk is ignored.

•

The qualifier applies only to output files . The COPY command automatically
handles input magnetic tape files with block sizes other than 512 bytes.

•

If the output tape is in ANSI format and is intended for interchange with
another operating system, the block size must be an even integer between 18
and 2048 bytes. Tapes having block sizes greater than 2048 bytes cannot be
read by other operating systems.

•

If the output tape is intended for use on the RT-ll operating system, the
block size must be 512 bytes.

WORKING WITH FILES

If both the input and output files are on magnetic tape, and both have large block
sizes, the COPY command may fail because of insufficient buffer space. If this
happens, transfer the file to disk, and then use the COPY command to transfer
the file from disk to tape.
ICLUSTER_SIZE=n
Establishes the cluster size for a disk file. A cluster size is a number of contiguous blocks taken together as a unit. The cluster size is the minimum unit of
allocation for the file.

This qualifier is especially useful for large files because specifying a large cluster
size speeds random access to the data.
In addition, you can avoid filling up your directory by specifying a large cluster
size. (In your directory, the system maintains an internal list of the clusters in
each file. If your directory fills up, you will receive the error message ?No room
for user on device, even though the disk is not full.)
RSTSIE allows cluster sizes of 1, 2, 4, 8, 16, 32, 64, 128, and 256 blocks. With
the SHOW DISK command, you can display the minimum cluster size of each
disk. If you specify a cluster size below the minimum, the system uses the disk's
minimum and does not display an error message.
ICONFIRM
INOCONFIRM
Indicates whether or not the system asks for confirmation before copying each
file. This qualifier is synonymous with IQUERY. The default is INOCONFIRM.
ICONTIGUOUS
INOCONTIGUOUS
Indicates whether or not the output file is to be contiguous. A contiguous file
occupies consecutive logical disk blocks.

For example, the following command line causes the file MANUAL. RUN to be
stored in consecutive blocks on disk DB2:.
$ COPY MANUAL.RUN DB2:*.*/CONTIGUOUS <RET>

By default, the COPY command creates an output file in the same format as
the corresponding input file. If an input file is contiguous, the COPY command
attempts to create a contiguous output file. If there is not enough contiguous disk
space, the system copies the file into available empty disk blocks and displays the
message:
%File file-spec created noncontiguous

The ICONTIGUOUS qualifier should not be used if the output file is not on disk.
If you are concatenating several input files, or if the single input file is on a
device other than disk, and you are creating a contiguous output file, you must
use the IALLOCATION qualifier to preallocate the size of the output file. This
is necessary because the system cannot judge the size of the output file in these
cases.
If you do not specify an allocation, or if the allocation is too small, RSTSIE
displays the following error message when the system tries to increase the size of
the contiguous output file:
?Protection violation

If you copy a file from a tape and want the file to be contiguous, you can use two
COPY commands: one to copy the file from the tape, and another to create a
contiguous file.

WORKING WITH FILES 3-27

For example, assume you want to copy file FRIDAYWOW from tape MTO: to a
contiguous file in your account ([52,20]) on the public structure. You rename the
file to WORK END temporarily, because you cannot copy file FRIDAY.WOW to
itself when making it contiguous:
$ COPY MTO:FRIDAY.WOW SY: [52,20]WORK.END/LOG <RET>
[File FRIDAY.WOW copied to SY: [52,20]WORK.END]
$ COPY WORK.END FRIDAY.WOW/CONTIGUOUS/LOG <RET>
[File SY: [52,20]WORK.END copied to SY: [52,20]FRIDAY.WOW]

$ DELETE WORK.END/LOG <RET>
WORK. END Deleted

The first command copies file FRIDAY.WOW from tape MTO: into a file named
WORKEND in your account ([52,20]) on the public structure. The second
command copies WORK END to a contiguous file named FRIDAYWOW. The
third command deletes the file WORKEND, because you used it only to move
file FRIDAYWOW into your account as a contiguous file . (Note that the /LOG
qualifier displays each completed file operation.)
If you specify /CONTIGUOUS and there is not enough contiguous disk space, the
file is not contiguous and the system prints the error message:
?No room for user on device

If you specified a network node name on either the input or output file, a different
error message displays:
?Device full:

Can't create or extend file

flOG
fNOlOG

Controls whether the COPY command displays the file specifications of each file
copied. /LOG is the default.
Unless you specify INOLOG, the COPY command displays the file specifications
of the input and output files . For example:
$ COPY DR3: [52,20]CREATE.BAS [1,248]*.* <RET>
[File DR3 : [52, 20] CREATE.BAS copied to [1,248]CREATE.BAS]

fOVERlAY
fNOOVERlAY

Requests that data in the input file be copied into an existing output file,
replacing the output file's existing data. The physical location of the file on disk
does not change.
For example, assume you rewrote the first chapter (CHAP 1. TXT) of a manual
(MANUAL. RUN). To overlay the existing chapter with the new first chapter, type:
$ COpy CHAP1.TXT MANUAL.RUN/OVERLAY <RET>

If the input file is smaller than the output file, the excess data in the output file
is not removed. In such a case (unless you use the INOLOG qualifier), the COPY
command prints a message similar to the following:
[File CHAP1.TXT copied into prefix of [1,248] MANUAL.RUN]

The default is INOOVERLAY. In addition, RSTS/E ignores the /OVERLAY
qualifier if the output file is written to any device other than a disk.
You can use this qualifier only when the input and output files are on the local
(your own) node.

3-28

WORKING WITH FILES

/POSITION=n
/POSITION=MIDDLE
/POSITION=INDEX

Specifies the starting position of the target file on disk. This qualifier is ignored
for files copied on devices other than disks.
If you specify /POSITION with an argument, then that value indicates the
starting disk cluster at which to copy the file. The minimum value is 0 (beginning
of disk) and the maximum value is the disk's maximum cluster number. If you
specify 0 (the default), the file is copied at the first available cluster on the disk.
If you specify /POSITION=MIDDLE, the file is copied to the first available cluster
past the middle of the disk.
If you specify /POSITION=INDEX, the file is copied to the first available cluster
following the storage allocation table (SATT.SYS) on the disk.
/PROTECTION=n

Specifies the protection code of the output file.
You cannot use /PROTECTION with IOVERLAY, or in network operations.
By default, RSTSIE assigns files a protection code of 60, unless your system manager changes the default. Furthermore, if you use the SET
PROTECTIONIDEFAULT command before the COPY operation, the protection
code becomes the value you specified as the default. See the SET PROTECTION
command description at the end of this chapter.
You can use /PROTECTION only if the input and output files are on the local
(your own) node.
/QUERY
/NOQUERY

Lets you select files to be copied when you specifY more than one file . The
IQUERY qualifier is useful only if you use wildcards. The default is /NO QUERY.
When you use IQUERY, RSTSIE displays each input file name and a question
mark prompt. Enter one of the following responses after each prompt:
Y

Yes, copy the file

No, do not copy the file

<RET>

No, do not copy the file

Skip remaining files; return to command level

For example, if you have files STRIDE.TXT, RACE. TXT, and FINISH.TXT in your
account, you can use the IQUERY qualifier as follows :
$ COPY *.TXT MANUAL.RUN/NOOVERLAY/QUERY <RET>
STRIDE . TXT? Y <RET>
File STRIDE.TXT copied to MANUAL.RUN
RACE . TXT? N <RET>
FINISH.TXT? <Ctrl/Z>
$

WORKING WITH FILES

3-29

IREPLACE
INOREPLACE

The !REPLACE qualifier requests that if a file already exists with the same file
specification as the one you are creating, the existing file is to be deleted.
For example, if there is a file named ROAD.MAP in your default directory, and
you want the file you are copying to replace the existing file, type:
$ COPY ROAD.MAP/REPLACE <RET>

If the COPY command is going to replace an existing file, but you do not specify
!REPLACE or INOREPLACE, RSTSIE displays the prompt:
OK to replace existing filespec ?

You can reply with one of the following:
Y

Yes, replace the file

No, do not replace the file

<RET>

No, do not replace the file

A YES response allows you to copy the file and replace the existing file.
Otherwise, the system returns to command level.
For example, suppose you mistakenly enter the name of an existing file that you
do not want replaced. The display at the terminal reads:
$ COPY FOO.TXT SORE.FUT <RET>
OK to replace existing file DR1: [52,20]SORE.FUT? N <RET>

The INOREPLACE qualifier forces the COPY command to fail if the file being
created already exists. In addition, it suppresses the "OK to replace existing
filespec?" prompt.
If you use the COPY command in a command procedure, you should explicitly
specify either !REPLACE or INOREPLACE. This prevents DCL from issuing the
"OK to replace existing filespec?" prompt.
IRETAIN_DATES
INORETAIN_DATES

For disk output, the !RETAIN_DATES qualifier retains the creation date-time
and access date of the input file.
The INORETAIN_DATES qualifier does not retain the input file's creation datetime and access date. The output file is created with the current date-time. The
default is INORETAIN_DATES.
ISELECT=SIZE=n
ISELECT=SIZE=MINIMUM=n
ISELECT=SIZE=MAXIMUM=n
ISELECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:

3-30

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or
equal to n .

MAXlMUM=n

Selects only those files with size less than or
equal to n .

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

WORKING WITH FILES

ITRANSFER_MODE:n
ITRANSFER_MODE:AUTOMATIC
ITRANSFER_MODE=BlOCK
~RANSFER_MODE:RECORD

Used on the input filespec to select the method by which the file(s) are transferred
to or from a remote node. The default is trRANSFER_MODE=AUTOMATIC.
ITRANSFER_MODE=BLOCK causes the file to be transferred as binary data
consisting of 512-byte blocks. This mode of transfer is generally faster than
record mode. However, it is only applicable for RSTS-to-RSTS file transfers, since
other operating systems may not have compatible file attributes and blocksizes.
ITRANSFER_MODE=RECORD copies the file as a collection of records based on
the file record format. This mode of transfer is generally slower than block mode.
However, records are a common medium of exchange for otherwise incompatible
file systems. This mode is recommended for file transfers involving TOPSI0/20,
ULTRIX, RT-ll and DECnet-DOS systems.
If ITRANSFER_MODE=AUTOMATIC is specified, then the most suitable mode of
transfer will automatically be selected.

WORKING WITH FilES

3-31

3.4.2

RENAME
The RENAME command changes the file name or type of an existing file.

Format
RENAME

old-file-spec[, ...J new-file-spec

Command Qualifiers
IBEFORE=date
I[NO]CONFIRM
ICREATED
I[NO] lOG
IMODIFIED
IPROTECTION=n
I[NO]QUERY
I[NO]REPLACE
ISElECT=SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
ISINCE=date
I[NO]WARNINGS

Defaults
none
INOCONFIRM
none
IlOG
none
See discussion
INOQUERY
INOREPlACE
See discussion

none
/WARNINGS

Prompts
From: old-file-spec[, ... ]
To:
new-file-spec

For example, you can rename the file JIM.DAT to JOHN.DAT with the command
line:
$ RENAME JIM.DAT JOHN.DAT <RET>

Command Parameters
old-tile-spee[, ... ]
Specifies one or more files whose specifications you want to change. The files
must be stored on a disk.

You can use wildcard characters in the directory, file name, or file type of the file
specification. If you use wildcards, all the files you specify are renamed (assuming
that they are your own files or that you have additional privilege to rename other
users' files).
new-tile-spec
Provides the new file name or type to be applied to the input file. The RENAME
command uses the file name and type of the input file specification to provide
defaults for fields you do not specify in the output file. (You cannot change the
device or directory of the files .)

3-32

WORKING WITH FILES

You can specify an asterisk (*) in place of the file name or type of the output
file specification, or you can omit either one; the RENAME command uses the
corresponding field in the input file specification to name the output file. The
IQUERY qualifier is useful when you use RENAME with wildcards.

Command Qualifiers
fBEFORE=date
fSINCE=date
fCREATED
fMODIFIED

Renames files created or modified before or since the specified date. See
Chapter 2 for information on specifying absolute date and time formats.
The following example renames all files created before Ol-Jun-90 with a file type
of .TXT to files with a file type of .DAT:
$ RENAME/CREATED/BEFORE=Ol-JUN-90 *.TXT *.DAT <RET>

The following example renames all files that were modified today to files with a
file extension of .WED:
$ RENAME/MODIFIED/SINCE=TODAY *.* *.WED <RET>

fCONFIRM
fNOCONFIRM

Prompts for confirmation before renaming files. This qualifier is synonymous
with IQUERY. The default is INOCONFIRM.
flOG
fNOlOG

When you rename a file, RSTSIE automatically displays a message to confirm
that the file was renamed. You can also request this message explicitly with the
/LOG qualifier, although /LOG is the default. The INOLOG qualifier suppresses
the message. For example:
$ RENAME RACEl.TXT FUNl.RUN <RET>
RACE l . TXT renamed to FUNl .RUN
$ RENAME RACE2.TXT FUN2.RUN/LOG <RET>
RACE2.TXT renamed to FUN2.RUN

$ RENAME RACE3.TXT FUN3.RUN/NOLOG <RET>

fPROTECTION=n
Specifies the protection code to assign to the file to be renamed. By default, the
protection codes of the files are not changed.
fQUERY
fNOQUERY

Allows you to select which files you want to rename. The IQUERY qualifier is
only useful when you use wildcards in the old file specification. The default is
INOQUERY.

WORKING WITH FILES

3-33

When you use IQUERY, RSTSIE displays individual file names and a question
mark prompt. You can reply with:
Y

Yes, rename the file

No, do not rename the file

<RET>

No, do not rename the file

Skip remaining files; return to command level

If the file exists and you do not specify !REPLACE, DCL displays the error

message:
?Name or account now exists - file file-spec - continuing

For example, suppose you want to rename some of your files with a .TXT file type
to files with a .DAT file type. You can enter the following command line and then
answer the prompts as follows:
$ RENAME *.TXT *.DAT/QUERY <RET>
[52,20]RACE1.TXT? Y <RET>
RACE1.TXT renamed to RACE1.DAT
[52,20]STRIDE.TXT? Y <RET>
?Name or account now exists - file STRIDE.DAT - continuing
[52,20]ATLAS.TXT? N <RET>
[52,20]TEXT.TXT? <Ctrl/Z>
$

IREPLACE
INOREPLACE
Replaces any existing files with a file to which you assign the same name. The
default is INOREPLACE. The INOREPLACE qualifier (whether by default or by
inclusion) is useful when you know that you need all your files and do not want
to risk replacing one.

For example, assume you want to rename the file PAVED.DAT to TRACKS.DAT,
and that you no longer need the existing file named TRACKS.DAT. The first of
the following command lines assumes the INOREPLACE qualifier, the second
explicitly includes INOREPLACE, and the third command line replaces the file:
$ RENAME PAVED.DAT TRACKS.DAT <RET>
?Name or account now exists - file TRACKS.DAT - continuing
$ RENAME PAVED.DAT TRACKS.DAT/NOREPLACE <RET>
?Name or account now exists - file TRACKS.DAT - continuing
$ RENAME PAVED.DAT TRACKS.DAT/REPLACE <RET>
File PAVED.DAT renamed to TRACKS.DAT

3-34 WORKING WITH FILES

ISELECT=SIZE=n
ISELECT=SIZE=MINIMUM=n
ISELECT=SIZE=MAXIMUM=n
ISELECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:
n

Selects only those files with size equal to n.

MINlMUM=n

Selects only those files with size greater than or
equal to n.

MAXIMUM=n

Selects only those files with size less than or
equal to n.

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

IWARNINGS
INOWARNINGS

Displays an error message if you try to rename a file to the same name as an
existing file. The default is !WARNINGS.

WORKING WITH FILES 3-35

3.4.3

APPEND
The APPEND command adds the contents of one or more files to the end of
the file you specify. APPEND is similar in syntax and function to the COpy
command.
For example, assume you create two files and then decide to append the first file
to the second one:
$ CREATE FILE.A <RET>
This is File A. <RET>

<Ctrl/Z>
$ CREATE FILE.B <RET>
And this is File B. <RET>

The APPEND command puts the contents of FILE.A at the end of FILE.B:
$ APPEND FILE.A FILE.B <RET>
[File FILE .A appended to [52,20]FILE

.B]

$ TYPE FILE.B <RET>
And this is File B.
This is File A.

FILE.B now includes a copy of FILE.A; the original FILE.A remains unchanged.
Note that you cannot append a file to itself. If you try, RSTSIE displays an error
message:
$ APPEND MOXIE.DAT MOXIE.DAT <RET>
?Protection violation - file MOXIE .DAT

Format
APPEND

input-file-spec[, ...] output-file-spec

Command Qualifiers
IBEFORE=date
I[NO]CONFIRM
ICREATED
I[NO]LOG (N)
IMODIFIED
I[NO]QUERY (N)
ISELECT=SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
ISINCE=date
Prompts
From: input-file-spec[, ...]
To: output-file-spec

3-36

WORKING WITH FILES

Defaults
none
INOCONFIRM
none
ILOG
none
INOQUERY
See discussion

none

Command Parameters
input-tile-spec[, ... ]
Specifies one or more input files to append to the output file . If your installation
has DECnetiE, you can specify the node where the input files are located.

If you specify more than one input file, separate the file specifications with
commas (,) or plus signs (+). All files are appended, in the order specified, to the
end of the output file.
You can use wildcards in any part of the file specification. For example, to
combine files STRIDE .REP, STRIDE.COP, and STRIDE.TXT into an existing file
named EVENT.DOC, you type:
$ APPEND STRIDE.* <RET>
To:
EVENT.DOC <RET>
[File STRIDE.REP appended to [52,20]EVENT.DOC]
[File STRIDE.COP appended to [52,20]EVENT.DOC]
[File STRIDE.TXT appended to [52,20]EVENT.DOC]

output-tile-spec
Specifies the file to which the input files are to be appended. (The output file
must be on a disk.) If yom installation has DECnetiE, you can specify the node
where the output file is located.

If the output file does not exist, RSTSIE displays the following error messages:
?Can't find file or account - file output-file-spec - continuing
[File input-file-spec copied to output-file - spec]

RSTSIE then creates a new output file.
You must specify at least one part of the output file specification. If you do not
specify a device and/or directory, the APPEND command uses yom directory on
the public disk structme. For other fields that you do not specify, the APPEND
command uses the corresponding field of the input file specification.
If you specify the asterisk wildcard character (*) in any part of the output file
specification, the APPEND command uses the corresponding field of the related
input file specification. For example:
$ APPEND ONE.* <RET>
To: TWO. * <RET>
[File ONE.TXT appended to [52,20]TWO . TXT]
[File ONE.DAT appended to [52,20]TWO . DAT]

Command Qualifiers
IBEFORE=date
ISINCE=date
ICREATED
IMODIFIED
Appends files created or modified before or since the specified date. See Chapter 2
for information on specifying dates and times.

The following example appends all data files created before Ol-Jun-90 to a file
named OLDWRK.DAT:
$ APPEND/CREATED/BEFORE=Ol-Jun-90 *.DAT OLDWRK.DAT <RET>

WORKING WITH FILES

3-37

The following example appends all files that were modified today to a file named
NUWORKWED:
$ APPEND/MODIFIED/SINCE=TODAY *.* NUWORK.WED <RET>

/CONFIRM
/NOCONFIRM

Requests confirmation before appending files. This qualifier is synonymous with
IQUERY. The default is INOCONFIRM.
flOG
/NOlOG

Controls whether the APPEND command displays the file specifications of each
file appended. Unless you specify INOLOG, the APPEND command displays the
file specifications of the input and output files after each append operation. For
example:
$ APPEND ATHENS.TXT OHIO. TXT/LOG <RET>
[File ATHENS.TXT appended to [52,20l0HIO.TXTl
$ APPENDATHENS.TXT MASS.TXT <RET>
[File ATHENS.TXT appended to [52,20lMASS.TXTl
$ APPEND ATHENS.TXT MAINE.TXT/NOLOG <RET>

/QUERY
/NOQUERY

Determines whether to append individual files to other files . The IQUERY
qualifier is only useful when you use wildcards in the input file specification. The
default is INOQUERY.
When you use the IQUERY qualifier, DCL displays a file name followed by a
question mark prompt. You can reply with either:
Y

Yes, append the file

No, do not append the file

<RET>

No, do not append the file

Skip remaining files; return to command level

For example, suppose you want to append some of your files with the type .DAT
to a file named RACES.TXT:
$ APPEND *.DAT TO RACES.TXT/QUERY <RET>
RACE1.DAT? Y
[RACE1.DAT appended to [52,20lRACES.TXTl
RACE2.DAT? N <RET>
RACE3 . DAT? <Ctrl/Z>
$

/SElECT=SIZE=n
/SElECT=SIZE=MINIMUM=n
/SElECT=SIZE=MAXIMUM=n
/SElECT=SIZE=(MINIMUM=m,MAXIMUM=n)

Selects files based on their size. The specified size can be:

3-38

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or equal to n.

MAXIMUM=n

Selects only those files with size less than or equal to n.

MINIMUM=m,
MAXIMUM=n

Selects only those files with size between m and n inclusive.

WORKING WITH FILES

3.5 Backing Up and Restoring Files
The commands in this section let. you copy the contents of your disk files to
magnetic tape or to another disk then restore the same files back onto your
system if necessary. Backing up files is a precautionary measure to let you
recover from the loss or destruction of valuable information. Files created by
BACKUP are called Backup sets. A Backup set is a RSTSIE file that can be
copied just like any other RSTSIE file. However, only BACKUP and RESTORE
can interpret the data in a Backup set.

3.5.1

BACKUP
The BACKUP command allows you to create a Backup set on a specified disk or
magnetic tape from one or more RSTSIE disk files.

Format
BACKUP

filespec[, ...] backup-set

Command Qualifiers

Defaults

ICREATED={date:time)
IMODIFIED={date:time)
IEND=action

See discussion

IEXCLUDE={filespec-list)
IINCLUDE=(filespec-list)
I[NO]INITIAUZE
IIN_LABEL=name
I[NO]UST_FILE[=filespec]
lOUT_LABEL=name
I[NO]OUTPUT[=filelspec]
I[NO]PROMPT
I[NO]QUERY
I[NO]REWIND
I[NO]VERIFY[=ONLy]

IEND=DISMOUNT for disks
IEND=NOREWIND for tapes
No files excluded
No files included
INOINITIAUZE
Volume ID is not checked
lUST_FILE=KB:
See discussion
IOUTPUT=KB:
IPROMPT
INOQUERY
INOREWIND
INOVERIFY

Prompts
See Discussion

Command Parameters
filespec[, ... ]
Identifies the files located on a disk to be backed up. The file specification should
be a standard RSTSIE file specification or a list of specifications separated by the
plus (+) sign or a comma (,):

WORKING WITH FILES

3-39

If you do not specify device, the default is SY:. The PPN is optional and defaults
to the user's current account. You can use wildcards in the PPN. The file
specification is optional and defaults to *.*. You can use standard wildcards.
If you specify a filename but not the type, BACKUP assumes a * type. If the
filename ends with a period, BACKUP assumes a null type. If you specify a file
type, you must also specify a filename.
backup-set
Identifies the disk or tape where the Backup set is to be created. The Backup
set specification should be a standard RSTSIE file specification. You must specify
the device. PPN is optional and defaults to the user's current account. The file
specification is optional and defaults to BACKUP.BCK.

Command Qualifiers
ICREATED=(date:time)
IMODI FI ED=( date :time)

The /CREATED and /M:ODIFIED qualifiers let you select the files to be backed
up, as chosen by the file specification criteria (see the input-file-spec description),
based on the creation date/time or revision date or both. If no file specification
criteria exist, these qualifiers apply to all files on the input volume for this
operation. You can use /CREATED and /MODIFIED in conjunction with each
other; they are not mutually exclusive. To be selected, a file has to satisfy all the
criteria you specify.
The date-time argument is of the standard form (for example, dd-mmm-yy or
yy.mm.dd and hh:mm AM or hh:mm PM). You must specify the date. If you do
not specify the time, it defaults to 00:00. In addition, if you specify the time, you
must separate it from the date by a colon (:).
The following generic terms can be used in the subqualifier:
..

TODAY-meaning 00:00 on the current (system) date

YESTERDAY-meaning 00:00 on the date previous to the current date

When used with /CREATED, the generic terms also accept a time argument.
If you do not specify either /CREATED or !MODIFIED, BACKUP selects all

specified files for transfer to the Backup set.
NOTE

Files transferred by BACKUP retain their original creation and
revision dates (that is, the dates on the source volume). You need the
DATES privilege to keep these original dates; otherwise, RSTSIE lists
the current date as the creation date of the backed-up file.
IEND=action

Specifies the disposition of the tape or disk drive at the end of the backup
operation.
For tapes, IEND=[NO]REWIND specifies whether or not to rewind the output
tape after the BACKUP operation is complete. The default is IEND=REWIND,
which leaves the tape positioned immediately after the backup set just written.
For disks you can specify IEND=[NO]DISMOUNT. The default is IEND=DISMOUNT.
IEXCLUDE=(filespec-list)

Lets you specify files that you want excluded from the BACKUP operation (for
example, [O,l]SWAP?.sYS). You can include a list of file specifications in the
command line up to the maximum length of a DCL command line.
3-40

WORKING WITH FILES

The default is that no files are excluded.
IINCLUDE=(filespec-llst)
Lets you specify files or accounts that you want to be unconditionally processed. You can include a list of file specifications in the command line up to the
maximum length of a DCL command line.

Files in this set override those excluded with the /EXCLUDE qualifier.
I[NO]INITIALIZE
Specifies the disposition of the output media prior to the data transfer operation
and sets the default device specification in the "Where can this volume be located
<default>?" prompt.

For disk volumes, /INITIALIZE specifies that any file structure on the disk is to
be disregarded and the volume is to be reinitialized with a RSTS/E file structure
as if it were done with the INITIALIZE command.
For magnetic tape volumes, /INITIALIZE specifies that BACKUP initializes the
tape as a standard ANSI tape.
IN_LABEL=name
Specifies the name to be compared to the source volume ID. If you use this
qualifier, the source volume ID must equal the specified name before BACKUP
can perform the requested operation.
ILiST
INOUST_FILE[ =filespec]
Controls the production of a directory-like listing file that catalogues the sequence
of events in the BACKUP operation. The file specification can be any valid
RSTS/E file specification (wildcards are not allowed).

The default is your terminal (KB:).
You can use this qualifier to produce a listing of files in the Backup set.
lOUT_LABEL=name

Specifies the desired name for the output volume ID. The resultant name can
vary depending on the interaction between lOUT_LABEL and I[NO]INITIALIZE.
Table 3-2 lists the possible outcome from the interaction of I[NO]INITIALIZE and
lOUT_LABEL during BACKUP.
Table 3-2: IINITIALIZE and lOUT_LABEL Interaction During BACKUP
Qualifiers
Specified

Output Volume ID

/OUT_LABEL=name
/INITIALIZE

The Specified name.

/OUT_LABEL=name
INOINITIALIZE

The specified name; however, the operation is only successful if
the output volume label has the same name.

/INITIALIZE (only)

BACKUP supplies the name "BACKUP".

INOINITIALIZE (only)

The name is unchanged.

WORKING WITH FILES

3-41

IOUTPUT
INOOUTPUT[=filespec]

Controls the production of a directory-like listing file that catalogues the sequence
of events in the BACKUP operation. The file specification can be any valid
RSTSfE file specification (wildcards are not allowed). You can use this qualifier
to produce a listing of files in the Backup set. /NO OUTPUT is a synonym for
/NOLIST_FILE.
The default is your terminal (KB:).
I[NO]PROMPT

Normally, the Backup utility issues a MOUNT prompt, for each BACKUP
operation even if the Backup set's device is already mounted. You can eliminate
the prompt for the first volume by including the /NOPROMPT qualifier in your
command line.
The default is !PROMPT.
I[NO]QUERY

Causes BACKUP to prompt you for each file that meets the selection criteria as
to whether or not the file should be transferred. A y[ES] response effects the
transfer. A response of N[O] or pressing Return bypasses the file. Any other
response causes the prompt to be reissued.
A YES/ALL response causes the current file and all remaining files to be transferred without any further prompting. A response of NO/ALL causes the current
file and all remaining files to be bypassed without any further prompting.
The default is /NOQUERY.
I[NO]REWIND

For tape backup files, indicates whether to rewind the tape before searching for
the logical end of tape to create the backup file.
BACKUP must locate the logical end of tape so that it can create the backup file
after any files already on the tape. While searching for the end of tape, BACKUP
will check the name of each file it encounters and report an error ifit finds a file
with the same name as the backup file. This prevents having two files with the
same name on the tape.
If you specify /REWIND, BACKUP rewinds the tape and scans the entire tape for

a duplicate file.
If you specify /NOREWIND, BACKUP scans from the tape's current position, and

will not detect duplicate files located earlier on the tape.
The default is INOREWIND.

3-42

WORKING WITH FILES

I[NO]VERIFY[ =ONLY]
The NERIFY qualifier specifies that a comparison operation is to be performed
on all data transferred. This postprocess verification reports the presence of
any data difference. For any differences found, BACKUP displays the PPN, file
name, and file type at your terminal. NERIFY =ONLY causes the verifY only pass
to be made over the same input and output specifications used for the backup
pass. You can use NERIFY=ONLY to compare the contents of a backup set with
the source disk to determine what files have changed since the backup set was
created. You can also use this qualifier to verifY several backup sets on one tape
without having to wait for the tape to rewind after each backup set.

The default is tNOVERIFY.
Examples
BACKUP DR1:PAYROL.DAT MTO:PAYROL.BCK

This command saves a file to a save set on tape
BACKUP DR2:PAYROL.DAT,DR2:BENEFI.DAT,DR2:VACATI.DAT MTO:DAT17M.BCK

This command saves a list of files to a save set on tape

WORKING WITH FILES

3-43

3.5.2

BACKUP/DIRECTORY
The BACKUPIDIRECTORY command allows you to list files contained in an
existing backup saveset. BACKUPIDIRECTORY prompts with:
Please mount volume 1 of Backup set backup-set-name
Where can this volume be located <default>?

At the prompt, enter the device name where the saveset is located. The default is
the output device you specified in the BACKUPIDIRECTORY command line.

Format
BACKUP/DIRECTORY
Command Qualifiers
IBRIEF
ICREATED=date:time
IMODIFIED=date:time
END=action
IEXCLUDE=(filespec-list)
IFULL
liN CLU DE=(filespec-list)
IIN_LABEL=name
I[NO]LlST_FILE[=filespec]
IOCCURRENCE=number
I[NO]OUTPUT[=filespec]
I[NO]PROMPT
I[NO]REWIND
SELECT=(filespec-list)

backup-set
Defaults
IBRIEF
See discussion
See discussion
IEND=DISMOUNT for disks
IEND=NOREWIND for tapes
No files excluded
IBRIEF
No files included
Volume ID is not checked
your terminal
First occurrence
your terminal
IPROMPT
INOREWIND
All files

Command Parameters
backup-set

Identifies the Backup set for which you want to obtain a directory listing. The
Backup set specification should be a standard RSTSIE device specification. The
default device is SY:, the default PPN is your current account and the default file
type is .BCK.

Command Qualifiers
/BRIEF
If you specify this qualifier, a fonnat similar to the DCL full directory (minus file

attributes) is displayed.
The default is !BRIEF.

3-44

WORKING WITH FILES

ICREATED=(date:time)
IMODIFIED=(date:time)

The /CREATED and /MODIFIED qualifiers let you select the files included in
the directory listing, as chosen by the file specification criteria, based on the
creation date/time, revision date, or both. If no file specification criteria exist,
these qualifiers apply to all files on the volume for this operation. You can
use /CREATED and /MODIFIED in conjunction with each other; they are not
mutually exclusive. 'Ib be selected, a file has to satisfy all the criteria you specifY.
You can specifY an exact date or range of dates for either qualifier. In the range
format, each qualifier must take an argument of one or both of the subqualifiers
BEFORE or AFTER. The subqualifier order in the argument is immaterial.
The date-time argument is of the standard form (for example, dd-mmm-yy or
yy.mm.dd and hh:mm AlPM or hh:mm). You must specifY the date. If you do not
specify the time, it defaults to 00:00. In addition, if you specifY the time, you
must separate it from the date by a colon(:). The following generic terms can be
used in the subqualifier:
•

TODAY-meaning 00:00 on the current (system) date

•

YESTERDAY-meaning 00:00 on the date previous to the current date

When used with /CREATED, the generic terms also accept a time argument. If
you do not specify either /CREATED or /MODIFIED, BACKUPIDIRECTORY lists
all specified files.
NOTE

Files transferred during the backup operation retain their original
creation and revision dates (that is, the dates on the source volume).
You need the DATES privilege to keep these original dates; otherwise,
RSTS/E lists the current date as the creation date of the backed-up file.
IEND=action

Specifies the disposition of the tape or disk drive at the end of the directory
listing operation.
For tapes you can specify![NO]REWIND. /REWIND rewinds the tape at the end
of the directory listing operation.
For disks you can specify I[NO]DISMOUNT. The default is !DISMOUNT, which
logically dismounts the disk drive at the end of the directory listing operation.
EXCLUDE=(filespec-list)
This qualifier lets you specifY files that you want excluded from the
BACKUPIDIRECTORY operation (for example, [O,l]SWAP?SYS). You can include a list of file specifications in the command line up to the maximum length
of a DCL command line.

The default is that no files are excluded.
IFULL
If you specifY this qualifier, detailed information for each file on multiple lines is

displayed.
'Ib display information for specific files use /SELECT or /EXCLUDE with
BACKUPIDIRECTORY.

WORKING WITH FILES 3-45

liN CLU DE=(fi lespec-list)
This qualifier lets you specify files or accounts that you want to be unconditionally
listed. You can include a list of file specifications in the command line up to the
maximum length of a DCL command line.
IIN_LABEL=name
This qualifier specifies the name to be compared to the source volume ID. If you
use this qualifier, the source volume ID must equal the specified name before
BACKUPIDIRECTORY can perform the requested operation.
I[NO]LlST_FILE[=filespec]
This qualifier controls the production of a directory-like listing file that catalogues the sequence of events in the BACKUPIDIRECTORY operation. The
file specification can be any valid RSTSIE file specification (wildcards are not
allowed).

You can use this qualifier to produce a listing of files in the Backup set.
The default is your terminal (KB:).
IOCCURRENCE=number
Specifies the occurrence of the named backup set used in the BACKUP process.
The default is the first occurrence.
I[NO]OUTPUT[=filespec]
This qualifier controls the production of a directory-like listing file that catalogues
the sequence of events in the BACKUPIDIRECTORY operation. The file specification can be any valid RSTSIE specification (wildcards are not allowed). You can
use this qualifier to produce a listing of files in the Backup set. INOOUTPUT is a
synonym for INOLlST_FILE.

The default is your terminal (KB:).
I[NO]PROMPT
For each BACKUPIDIRECTORY operation a MOUNT prompt is issued, even
if the Backup set's device is already mounted. By including the INOPROMPT
qualifier in your command line you can eliminate the prompt for the first volume.

The default is !PROMPT.
I[NO]REWIND
This qualifier indicates whether to rewind the tape before searching for the logical
end of tape.

The default is INOREWIND.
ISELECT=(filespec-list)
This qualifier specifies the files you want to list.

The default is to list all files in the backup set.

3-46

WORKING WITH FILES

3.5.3

RESTORE
This command restores a RSTSIE disk or subset thereof from a tape or disk
Backup set. Once RSTSIE determines the syntactic validity of the command
specification and issues any warning message relative to either the command or
the environment, RESTORE prompts with:
Please mount volume 1 of Backup set backup-set-name
Where can this volume be located <default>?

At the prompt, enter the device to use or press Return or Line Feed to accept the
default value. The default value is the device specified as the input parameter. If
you specify INOPROMPT, RESTORE omits the prompt message.
If you are doing a partial restore, and you know what volume to start with,

start with that volume (although you may start with any volume). RESTORE
issues a confirmation message and starts with the volume you specify. Note that
RESTORE may issue a warning message in this case.

Format
RESTORE

backup-set output-fife-spec

Command Qualifiers
ICREATED=(date:time)
IMODIFIED=(date:time)
IEND=action
IEXCLUDE=(filespec-list)
I[NO]FILE_DATA
IINCLUDE=(filespec-list)
I[NO]INITIAUZE
IIN_LABEL=name
I[NO]UST_FILE[=filespec]
IOCCURRENCE=number
lOUT_LABEL=name
I[NO]OUTPUT[=filespec]
I[NO]PROMPT
I[NO]QUERY
I[NO] REPLACE[=QUERy]
I[NO]REWIND
ISELECT[=(filespec-list)]
I[NO]VERIFY[=ONLy]

Defaults
See discussion
IEND=DISMOUNT
None excluded
IF ILE_DATA
None included
See discussion
Volume ID not checked
lUST_FILE=KB:
IOCCURRENCE=1
See discussion
Your terminal
IPROMPT
INOQUERY
IREPLACE=QUERY
INOREWIND
See discussion
INOVERIFY

Prompts
See discussion

WORKING WITH FILES

3-47

Command Parameters
backup-set
Identifies the device where the first volume of the Backup set is mounted. The
Backup set specification should be a standard RSTSIE device specification. If
you do not specify a device, the default is SY:. PPN is optional and defaults
to the user's current account. The file specification is optional and defaults
to BACKUP.BCK. If the restore operation needs more than one volume in the
Backup set, RESTORE prompts you for subsequent volumes as follows:
Please dismount volume 1 of Backup set backup-set-name
Please mount volume 2 of Backup set backup-set-name
Where can this volume be located <default>?

output-filespec
Identifies where to put the files or accounts to be restored. The file specification
should be a standard RSTSIE file specification. If you do not specify device, the
default is SY:. The PPN is optional and defaults to the user's current account.
You can use wildcards in the PPN. The file specification is optional and defaults
to *. *. You can use standard wildcards. If you specify a filename but not the
type, BACKUP assumes a * type. If the filename ends with a period, BACKUP
assumes a null type. If you specify a file type, you must also specify a filename.
If you specify a wildcard PPN, RESTORE transfers all selected files to:

[*,*] -

the same accounts as on the Backup set

[n, *] - forces the project number to n, uses the programmer number as on
the Backup set

[*,n] - forces the programmer number to n, uses the project number as on
the Backup set

Command Qualifiers
ICREATED=date:time
IMODlFIED=date :time
The /CREATED and /MODIFIED qualifiers let you select the files to be restored,
as chosen by the file selection criteria (see the output-file-spec description), based
on the creation dates/times and/or revision dates. If no file selection criteria exist,
these qualifiers apply to all files on the input volume to which you have access for
this operation. You can use /CREATED and /MODIFIED in conjunction with each
other; they are not mutually exclusive. To be selected, a file has to satisfy all the
criteria you specify.

You can specify an exact date or a range of dates for either qualifier. In the
range of dates format, each qualifier must take an argument of one or both of the
subqualifiers, BEFORE or AFTER. The order of the sub qualifiers in the argument
is immaterial. If you specify both BEFORE and AFTER dates for either one of
the qualifiers, the AFTER date must be earlier than the BEFORE date.
If you do not use either /CREATED or !MODIFIED, all specified files are selected
for transfer from the Backup set.

NOTE

BACKUP retains both the creation and revision dates as they were on
the source volume for the files transferred if you have DATES privilege.

3-48

WORKING WITH FILES

IEND=action
REWIND causes the magnetic tape to be rewound to the load point and
dismounted following successful completion of the RESTORE operation.
/END=NOREWIND causes the magnetic tape to remain positioned after the
most recent Backup set. The default is END=NOREWIND.

If you want the Backup set's device to remain mounted at the end of the BACKUP
operation, specify END=NODISMOUNT in the command line. The default is
END=DISMOUNT.
IEXCLUDE=(filespec-list)
Lets you specify files that you want to be excluded from the RESTORE operation. You can include a list of file specifications in the command line up to the
maximum length of a DCL command line.
I[NO]FILE_DATA
Controls whether file data is transferred during a RESTORE operation. If you
specify !FILE_DATA, RESTORE transfers the file data from the Backup set to
the RSTS/E volume. If you specify INOFILE_DATA, RESTORE proceeds without
restoring any of the specified files. The default is !FILE_DATA.
IINCLUDE=(filespec-list)
Lets you specify files that you want to be unconditionally processed. You can
include a list of file specifications in the command line up to the maximum length
of a DCL command line.

Files in this set override those specified with the /EXCLUDE qualifier.
I[NO]INITIALIZE
Specifies the disposition of the output media prior to the data transfer operation.

The /INITIALIZE qualifier specifies that RESTORE should disregard any file
structure on the disk and reinitialize the volume with a RSTS/E file structure as
if it were done with the INITIALIZE command.
You can only specify INOINITIALIZE when the RESTORE operation is from a
Backup set to an existing RSTS/E disk. In this case, RESTORE places the files
on the existing file structures instead of replacing them.
IIN_LABEL=name
Specifies the name to be compared to the source volume ID. If you use this qualifier, the source volume ID must equal the specified name before the RESTORE
operation can be performed.
I[NO]LlST_FILE[=file-spec]
Generates a directory-like listing file, cataloguing the sequence of events in
the RESTORE operation. If you specify !LIST_FILE, you must include the file
specification. It can be any legal RSTS/E file specification (wildcards are not
allowed). The default is !LIST_FILE=KB:.
IOCCURRENCE=number
Indicates the particular occurrence of a named Backup set to use when more than
one Backup set of the same name exists on a magnetic tape. You must specify the
argument which refers to the position relative to either the current tape position
or the beginning of the tape depending on the use of I[NO]REWIND.

RSTS/E Backup sets are interchangeable with VAX Backup sets. However, VAX
Backup set names can be greater than six characters, while RSTS/E looks at
only the first six characters. Therefore, RSTS/E cannot distinguish between two
VAX names that have the same first six characters (for example, ABCDEF and
ABCDEFG). To transfer ABCDEFG, you must use ABCDEF/OCCURRENCE=2.
WORKING WITH FILES 3-49

The default is IOCCURRENCE=l; the first occurrence of the named Backup set.
lOUT_LABEL=name
Specifies the desired name for the output volume ID. The resultant name can
vary depending on the interaction between lOUT_LABEL and I[NO]INITIALIZE.

Table 3-3 summarizes the possible outcomes from the interaction of
![NO]INITIALIZE and lOUT_LABEL during RESTORE.
Table 3-3: IINITIALIZE and lOUT_LABEL Interaction During RESTORE
Qualifiers Specified

Output Volume ID

IOUT_LABEL=name
/INITIALIZE

The specified name.

IOUT_LABEL=name
INOINITIALIZE

The specified name; however, the operation is only
successful if the output volume label has the same name.

/INITIALIZE (only)

The destination volume name is the same as the source
volume name.

INOINITIALIZE (only)

The name is unchanged.

I[NO]OUTPUT[=filespec]
Controls the production of a directory-like listing file that catalogues the sequence
of events in the RESTORE operation. The file specification can be any valid
RSTSIE file specification (wildcards are not allowed). You can use this qualifier
to produce a listing of files in the Backup set. /NO OUTPUT is a synonym for
/NOLIST_FILE. The default is your terminal (KB:).
I[NO]PROMPT
Normally, the BACKUP utility issues a MOUNT prompt for each RESTORE
operation even if the Backup set's device is already mounted. You can eliminate
the prompt for the first volume by including the /NOPROMPT qualifier in your
command line. The default is !PROMPT.
I[NO]QUERY
Causes RESTORE to prompt you as to whether each file that meets the selection criteria should be transferred. A Y[ES] response effects the transfer. A
response of N[O] or pressing <RET> bypasses the file. Any other response causes
RESTORE to reissue the prompt.

A YES/ALL response causes the current file and all remaining files to be transferred without any further prompting. A response of NO/ALL causes the current
file and all remaining files to be bypassed without any further prompting.
The default is INOQUERY.
I[NO]REPLACE[=QUERY]
Indicates what action should be taken if a file to be transferred already exists
on the output disk. If you specify !REPLACE, RESTORE replaces the file if it
exists; any existing file is deleted. If you specify INOREPLACE, RESTORE issues
a warning and does not replace the file if it already exists.

The default, !REPLACE=QUERY, prompts you to replace any file that already
exists. Answer Y or YES to replace the current file. Answer N or NO to not
replace the existing file and proceed with the next file.
If you respond YES/ALL to the prompt, all remaining selected files are copied and
replace existing copies without prompting. If you respond NO/ALL to the prompt,
all remaining selected files are copied and do not replace existing files without
prompting.
3-50

WORKING WITH FILES

/[NO]REWIND

Specifies the disposition of a magnetic tape Backup set volume before processing.
The default is INOREWIND.
If you specify /REWIND, t.he search for the Backup set hegins at t.he heginning
of the tape. The INOREWIND qualifier means the search starts at the present
position.
If the logical end-of-tape on the volume is found before the desired Backup set,
the tape is rewound and an error message appears at the terminal.
/SELECT[ =(filespec-list)]

Lets you select specific files from the input Backup set to be restored. You can
use the ISELECT qualifier in conjunction with the /EXCLUDE qualifier and the
/INCLUDE qualifier or both. If you use ISELECT in combination with other
qualifiers, the file transfer candidates are chosen according to the following
criteria:
•

All files on the volume for which the user has read access privilege are
initially considered

•

If you use the ICREATED or /MODIFIED qualifiers, only those files from
criterion 1 which meet the time bracket standard are considered.

•

If you use the ISELECT qualifier, only those files from criterion 2 that match
one of the ISELECT file specifications are considered.

•

If you use the /EXCLUDE qualifier, any files from criterion 3 that match one

of the /EXCLUDE file specifications are removed from consideration.
•

If you use the /INCLUDE qualifier, RESTORE also considers any files
meeting the inclusion criteria, provided that you have access to them. Note
that RSTS/E does not consider the ICREATED, /MODIFIED, ISELECT, or
/EXCLUDE qualifiers when processing the /INCLUDE list.

/[NO]VERIFY[=ONLY]

The NERIFY qualifier specifies that a comparison operation is to be performed on
all data transferred. This postprocess verification (for multivolume Backup sets,
all volumes are transferred before any volume is verified) reports the presence
of any data differences. For any differences found, RESTORE displays the PPN,
file name, and file type at the user's terminal. NERIFY= ONLY causes the verify
only pass to be made over the same input and output specifications used for
the backup pass. You can use NERIFY=ONLY to compare the contents of the
restored disk with the source disk to determine what files have changed since the
backup set was created. You can also use this qualifier to verify several backup
sets on one tape without having to wait for the tape to rewind after each backup
set.
The default is INOVERIFY.

WORKING WITH FILES

3-51

Examples
RESTORE/SELECT=[*,*JPAYROL.DAT MTO:PAYROL.BCK DRl:*.*

This command restores a file from a save set on tape
RESTORE MMO:1409MA.BCK DUl: [*,*J*.*

This command restores a disk from a save set on tape
RESTORE MTO:DAT17M.BCK/SELECT= (PAYROL.DAT,BENEFI.DAT,VACATI.DAT) DR2: [*.*J*.*

This command restores a list of files from a save set on tape
RESTORE/LIST_FILE=928FEB.LOG/ACCOUNT_DATA MMO:928FEB.BCK DRl: [*.*J*.*

This command restores a disk from a save set, and if a file exists, replaces it

3-52

WORKING WITH FILES

3.5.4

RESTORE/DIRECTORY
Allows RESTORE to list files within an existing BACKUP saveset.
RESTOREIDIRECTORY prompts with:
Please mount volume 1 of Backup set backup-set-name
Where can this volume be located <default>?

At the prompt, enter the device name where the saveset is located. The default is
the output device you specified in the RESTOREIDIRECTORY command line.

Format
RESTORE/DIRECTORY

backup-set

Command Qualifiers

Defaults

IBRIEF
ICREATED=date:time
IMODIFIED=date:time
IEND=action

IBRIEF
See discussion

IEXCLUDE=(filespec-list)
IFULL
/IN CLUDE=(filespec-list)
/IN_LABEL=name
I[NO] LIST_FILE[=filespec]
IOCCURRENCE=number
I[NO]OUTPUT[=filespec]
I[NO]PROMPT
I[NO]REWIND
ISELECT=(filespec-list)

IEND=DISMOUNT for disks
IEND=NOREWIND for tapes
No files excluded
IBRIEF
No files included
Volume ID is not checked
Your terminal
First occurrence
Your terminal
IPROMPT
INOREWIND
All files

Command Parameters
backup-set
Identifies the disk or tape that contains the Backup set. The Backup set specification should be a standard RSTSIE device specification. You must specify the
device. PPN is optional and defaults to the user's current account. The file specification is optional and defaults to BACKUP.BCK. If the backup set consists of
more than one volume, RESTOREIDIRECTORY prompts for subsequent volumes
as follows:
Please dismount volume 1 of Backup set backup-set-name
Please mount volume 2 of Backup set backup-set-name
Where can this volume be located <default>?

WORKING WITH FILES

3-53

Command Qualifiers
IBRIEF
Displays a format similar to the DCL full directory (minus file attributes) and is
the default qualifier.
ICREATED=(date:time)
IMODIFIED=(date:time)
The ICREATED and /MODIFIED qualifiers let you select the files included in
the directory listing, as chosen by the file specification criteria, based on the
creation date/time and/or revision date. If no file specification criteria exist,
these qualifiers apply to all files on the volume for this operation. You can
use ICREATED and /MODIFIED in conjunction with each other; they are not
mutually exclusive. To be selected, a file has to satisfy all the criteria you specify.

You can specify an exact date or range of dates for either qualifier. In the range
format, each qualifier must take an argument of one or both of the subqualifiers
BEFORE or AFTER. The subqualifier order in the argument is immaterial.
The date-time argument is of the standard form (for example, dd-mmm-yy or
yy.mm.dd and hh:mm AM or hh:mm PM). You must specify the date. If you do
not specify the time, it defaults to 00:00. In addition, if you specify the time, you
must separate it from the date by a colon (:).
The following generic terms can be used in the subqualifier:
•

TODAY-meaning 00:00 on the current (system) date

•

YESTERDAY-meaning 00:00 on the date previous to the current date

When used with ICREATED, the generic terms also accept a time argument.
If you do not specify either ICREATED or /MODIFIED, RESTOREIDIRECTORY
lists all specified files.
NOTE

Files transferred during the backup operation retain their original
creation and revision dates (that is, the dates on the source volume).
You need the DATES privilege to keep these original dates; otherwise,
RSTSIE lists the current date as the creation date of the backed-up file.
IEND=action
Specifies the disposition of the tape or disk drive at the end of the directory
listing operation.

For tapes you can specify IEND=[NO]REWIND. IEND=REWIND rewinds the tape
at the end of the directory listing operation.
For disks you can specify IEND=[NO]DISMOUNT. The default is IEND=DISMOUNT,
which logically dismounts the disk drive at the end of the directory listing
operation.
IEXCLUDE=(filespec-list)
Lets you specify files that you want excluded from the RESTOREIDIRECTORY
operation (for example, [O,l]SWAPl.SYS). You can include a list of file specifications in the command line up to the maximum length of a DCL command line.
The default is that no files are excluded.

3-54 WORKING WITH FILES

IFULL

Displays detailed infonnation for each file on multiple lines.
To display infonnation for specific files use ICREATED, !MODIFIED, /EXCLUDE,
/INCLUDE, and ISELECT.
IINCLUDE=(filespec-list)

Lets you specify files or accounts that you want to be unconditionally listed. You
can include a list of file specifications in the command line up to the maximum
length of a DCL command line.
Files in this set override those excluded with the /EXCLUDE qualifier.
IIN_LABEL=name

Specifies the name to be compared to the backup set volume ID. If you
use this qualifier, the volume ID must equal the specified name before
RESTOREIDIRECTORY can perfonn the requested operation.
I[NO]LlST_FILE[ =filespec]

Controls the production of a directory-like listing file that catalogues the sequence
of events in the RESTOREIDIRECTORY operation. The file specification can be
any valid RSTS/E file specification (wildcards are not allowed). The default is
your tenninal (KB:).
You can use this qualifier to produce a listing of files in the Backup set.
IOCCURRENCE=number

Specifies the occurrence of the named backup set used in the backup process. The
default is the first occurrence.
I[NO]OUTPUT[=fi lespec]

Controls the production of a directory-like listing file that catalogues the sequence
of events in the RESTOREIDIRECTORY operation. The file specification can
be any valid RSTSIE file specification (wildcards are not allowed). You can use
this qualifier to produce a listing of files in the Backup set. INOOUTPUT is a
synonym for INOLIST_FILE. The default is your tenninal (KB:).
I[NO]PROMPT

Nonnally, the Restore utility issues a MOUNT prompt, for each
RESTOREIDIRECTORY operation even if the Backup set's device is already
mounted. You can eliminate the prompt for the first volume by including the
INOPROMPT qualifier in your command line. The default is !PROMPT.
I[NO]REWIND

For tape backup files, indicates whether to rewind the tape before searching for
the logical end of tape. The default is INOREWIND.
IS ELECT=(filespec-list)

Specifies the files you want to list. The default is to list all files in the backup set.

WORKING WITH FILES 3-55

3.6 Sorting Files and Merging Sorted Files
The commands in this section let you reorder the contents of a file or files, and
combine several sorted files into a single output file.

3.6.1

SORT
The SORT command invokes the PDP-ll SORT utility to reorder the records
in one through ten files into a defined sequence and to create a single new file
containing the reordered records.
This section provides basic command and syntax information for the SORT
command. For complete details on the qualifiers and additional information
on how to define and control SORT operations, see the PDP-I1 SORT/MERGE
User's Guide.

Format
SORT

input-file-spee[, ...]/qualifiers output-file-spec/qualifiers

Command Qualifiers
/COLLATING_SEQUENCE=sequence
/[NO]DUPUCATES
/KEY=(field[, ... J)
/PROCESS=type
/SPECIFICATION[=filespecj
/[NO]STABLE
/[NO]STATISTICS
/wORK_FILES=n

Defaults
/COLLATING_SEQUENCE=ASCII
/DUPLICATES
See discussion
/PROCESS=RECORD
See discussion
/NOSTABLE
/NOSTATISTICS
none

Input File Qualifiers
/FORMAT =(file-attribute[, ... ])
/INDEXED_SEQUENTIAl[ =nj
/[NO]SHAREABLE
fTREE_SPACE=n

See discussion
Default Value=1
/NOSHAREABLE
none

Output File Qualifiers
/ ALLOCATION=n
/BUCKET_SIZE=n
/[NO]CONTIGUOUS
/FORMAT =(record-format[, ... ])
/INDEXED_SEQUENTIAl[ =n]
/LOAD_FILL
/[NO]OVERLAY=n
/RELATIVE
/SEQUENTIAl

See discussion
none
/NOCONTIGUOUS
See discussion
Default Value=1
none
/NOOVERLAY
See discussion
See discussion

Prompts
File:
input-file-spec[, ... ]/qualifiers
Output:
output-fiie-spec/qualifiers

3-56

WORKING WITH FILES

Command Parameters
input-file-spec[, ... ]
Specifies the names of the file(s) whose records are to be sorted. If the file
specifications do not include a file type, SORT assumes the default file of .DAT.
output-file-spec
Specifies the name of the file into which the sorted records are to be written. Its
qualifiers can request characteristics for the sorted output file. The command
string may have only one output file specification.

If the output file specification does not include a file type, SORT assigns the
default file type of .DAT to the output file, regardless of the file type(s) of the
input file(s).

Command Qualifiers
ICOLLATING_SEQUENCE=sequence
Specifies the collating sequence in which records are to be arranged. The
sequence may be ASCII, EBCDIC, or MULTINATIONAL. The default is
ICOLLATING_SEQUENCE=ASCII.
IDUPLICATES
INODUPLICATES
Alternatively specifies how input files containing records with equal keys are to
be sorted in the output file (see the previous I[NO]STABLE qualifier discussion).
The INODUPLICATES qualifier specifies that only one record be retained when
SORT encounters records with equal keys. The default is /DUPLICATES.
NOTE

Do not use INODUPLICATES and 1STABLE in the same SORT
operation.
IKEY=(field[, ... ])
Defines a SORT key. You can specify this qualifier up to ten times to define ten
different key fields to be sorted.

The /KEY qualifier consists of two required arguments that define the position
and size of the key field within the record, and several optional arguments that
define the type of data within the key field. You must separate the arguments
with commas and enclose them in parentheses.

Required Arguments for the /KEY Qualifier
POSITION=n

Specifies the position of the key within each record, where the first
character of the record is position 1.

SIZE=n

Specifies the length of the SORT key in characters, bytes, or digits,
depending on the key field data type. The total of all key field sizes
must be less than 255 bytes. The valid sizes, based on data type, are:

WORKING WITH FILES

3-57

Data Type

Values forn

CHARACTER

1-255

BINARY

1,2,4,8

DECIMAL

1-31

NOTE

You cannot use the SIZE argument with floating point data types
(D_FLOATING, F _FLOATING, or ASCII_FLOATING.
Optional Arguments for the /KEY Qualifier
CHARACTER
BINARY
DECIMAL
ASCII_FLOATING
ASCII_ZONED
DIBOL_ZONED
D_FLOATING
F_FLOATING
PACKED_DECIMAL

Indicates the type of data in the SORT key field. If not
specified, SORT assumes that data is CHARACTER.

SIGNED
UNSIGNED

Indicates whether a binary or decimal key is to be compared as a signed or an unsigned integer. UNSIGNED
causes all numbers to be treated as positive. SIGNED is
the default.

LEADING_SIGN
TRAILING_SIGN

Indicates whether the sign of a decimal data type key
appears at the beginning or end of the key. If you specify
the key data type as DECIMAL, but do not specify either
of these subqualifiers, the default is TRAILING_SIGN.

OVERPUNCHED_SIGN
SEPARATE_SIGN

Indicates whether the sign of a decimal data type key
is superimposed on the decimal value or is separated
from the decimal value. If you specify the key data
type as DECIMAL, but do not specify either of these
subqualifiers, the default is OVERPUNCHED_SIGN.

ASCENDING
DESCENDING

Indicates whether the key is to be sorted into ascending or descending order. If you specify neither of these
subqualifiers, the default is ASCENDING.

/PROCESS=type

Defines the type of sort. You can specify one of the following sort types:
RECORD

Requests SORT to resequence the entire contents of the input file(s)
and create an output file containing the reordered records.

TAG

Requests SORT to sort only the record keys, and then reaccess
the input files to create an output file containing the resequenced
records.

ADDRESS

Requests SORT to produce an address file sorted by record keys.
The output file can be read as an index to read the original file in
the desired sequence.

INDEX

Requests SORT to produce an address file containing the key field of
each data record and a pointer to its location in the input file. The
output file can be read to randomly access the data in the original
file in the desired sequence.

The default is IPROCESS=RECORD.

3-58 WORKING WITH FILES

ISPECIFiCATION[dile-spec]
Indicates that commands and file qualifiers, including key field definitions, are
contained in a specification file. See the PDP-ll SORTI MERGE User's Guide for
complete details on using specification files.
ISTABLE
INOSTABLE
Specifies how input files containing records with equal keys are to be sorted in the
output file. The default is INOSTABLE, which causes any records with equal keys
to be grouped together in the output file, possibly resulting in an unpredictable
sort order for those particular records. The ISTABLE qualifier specifies that
any records with equal keys are to be directed to the output file in the order in
which they were input to SORT. See the following I[NO]DUPLICATES qualifier
discussion.
ISTATISTICS
INOSTATISTiCS
Specifies whether a statistical summary displays after the SORT operation
completes. The default is INOSTATISTICS.
IWORK_FllES=n
Specifies the number of temporary work files to be used during the sort process.
You can specify 0 or any value from 3 through 10. A value of 0 indicates that no
work files are necessary because the data will fit in physical memory.

Input Fiie Qualifiers
IFORMAT=(file-attributeL ... ])
Specifies attributes of the input file to override the existing data that SORT
normally obtains through PDP-ll RMS. You can specify one or both of the
following arguments:
Defines the size of the file in blocks. This argument is required for
files that are not on disk or magnetic tape.
If no input file size is specified, SORT uses the default value of 1000
blocks.
Specifies, in bytes, the length of the longest record, overriding
the record size defined in the file header or label. This argument
is required for files that are not on disk or magnetic tape, or if
the longest record length (LRL) is unavailable or known to be
inaccurate.

liN DEXED_ SEQUENTIAl[ =n]
Specifies that the organization of the input file is indexed-sequential. You specify
the number of keys (1 through 255) to make sure that SORT allocates sufficient
RMS space. The default value is 1.
ISHAREABLE
INOSHAREABlE
Specifies whether the input files are opened in write-shareable mode. Use this
qualifier when you want to sort files that may be updated by another user during
the sort operation. The default is INOSHAREABLE.

WORKING WITH FILES

3-59

TREE_SPACE=n

Specifies the percentage distribution of available work area between
SORTIMERGE tree-related data structures and I/O-related data structures.
You can specify from 1 to 100 percent (%). For SORT, the default division of work
area is 55% to the tree and 45% to 1/0.

Output File Qualifiers
I ALLOCATION=n
Specifies the number of 512-byte blocks to be allocated for the output file. By
default, SORT allocates blocks based on the number of records sorted.
IBUCKET_ SIZE=n

Used with disk files, this qualifier specifies the number of 512-byte blocks per
bucket for the output file. The maximum size you can specify is 32 blocks. If you
do not specify a bucket size, the bucket size of the output file defaults to that of
the input file.
ICONTIGUOUS
INOCONTIGUOUS

Specifies whether the allocation of disk space for the output file is to be contiguous. If you specify ICONTIGUOUS, you must also specify IALLOCATION
to define the number of blocks to allocate for the output file. The default is
INOCONTIGUOUS.
IFORMAT=(record-format[, ... ])

Defines the output file record format. You can specify one or more of the following
arguments:
FIXED[=n]
VARIABLE[=n]
RMS_STREAM[=n]
STREAM[=n]
CONTROLLED[=n]

Defines the output file record format and size, where n is
the length of the longest record in the output file. If n is
not specified, the default is a length long enough to hold the
longest output record.

BLOCK_SIZE=n

Specifies, when the output file is directed to disk or magtape,
the block size in bytes. If one or more input files is a tape file,
the output file block size defaults to the maximum of the block
sizes of all tape input files. If the input file is a disk file, the
default value is 512 bytes.

liN DEXED_SEQUENTIAL[=n]

Specifies that the organization of the output file is indexed-sequential. You
specify the number of keys (1 through 255) to make sure that SORT allocates
sufficient RMS space. The default value is 1.
ILOAD_FILL

Used only with indexed files, this qualifier loads the buckets according to the fill
size established when the file was created.

3-60

WORKING WITH FILES

IOVERLAY
INOOVERLAY

Specifies whether an existing file is to be overlaid with the sorted records of the
input file. The default is /NOOVERLAY, which means a new output file is creat~d
and does not overlay an existing file.
IRELATIVE

Specifies that the organization of the output file is relative. By default, a
RECORD or TAG sort process results in an output file that has the same
organization as the input file. Use the /RELATIVE qualifier to create a relative
output file from a sequential or indexed-sequential input file.
ISEQUENTIAL

Specifies that the organization of the output file is sequential. This is the default
for an ADDRESS or INDEX sort process; for a RECORD or TAG sort process, the
output file organization defaults to the organization of the input file.

WORKING WITH FILES 3-61

3.6.2

MERGE
The MERGE command invokes the PDP-ll MERGE utility to combine two
through ten similarly sorted input files and create a single output file. Note that
input files to be merged must be in sorted order.
This section provides basic command and syntax information for the MERGE
command. For complete details on the qualifiers and additional information on
how to define and control MERGE operations, see the PDP-II SORT/MERGE
User's Guide.

Format
MERG E

input-file-spec 1,input-file-spec2[, ...] /qualifiers output-file-spec/qualifiers

Command Qualifiers
I[NO]CHECK_SEOUENCE
ICOLLATING_SEOUENCE=sequence
I[NO]DUPLICATES
IKEY=(field[, ... ])
IPROCESS=type
ISPECIFICATION[=file-spec]
I[NO]STABLE
I[NO]STATISTICS
/wORK_FILES=n

Defaults
ICHECK_SEOUENCE
ICOLLATING_SEOUENCE=ASCII
IDUPLICATES
See discussion
IPROCESS=RECORD
See discussion
INOSTABLE
INOSTATISTICS
See discussion

Input File Qualifiers
IFORMAT=(file-attribute[, ... ])
IINDEXED_SEOUENTIAL[=n]
I[NO]SHAREABLE
/TREE_SPACE=n

See discussion
Default value=1
INOSHAREABLE
See discussion

Output File Qualifiers

I ALLOCATION=n
IBUCKET_SIZE=n
I[NO]CONTIGUOUS
IFORMAT=(record-format[, ... ])
IINDEXED_SEOUENTIAL[=n]
ILOAD_FILL
I[NO]OVERLAY
IRELATIVE
ISEOUENTIAL

See discussion
none
INOCONTIGUOUS
See discussion
Default Value= 1
none
INOOVERLAY
See discussion
See discussion

Prompts
File:
input-file-spec1,input-file-spec2[, ... ] Iqualifiers
Output:
output-file-spec/qualifiers

3-62

WORKING WITH FILES

Command Parameters
i nput-file-spec1 ,i nput-file-spec2[, ... ]
Specifies the names of the sorted files whose records are to be merged. At least
two files, but not more than ten, must be specified and separated by commas. The
keys must be the same in all files.
If the file specifications do not include a file type, MERGE assumes the default

file type of .DAT.
output-tile-spec
Specifies the name of the merged file to be created. Its qualifiers can request
characteristics for the merged output file. The command string may have only
one output file specification.
If the output file specification does not include a file type, MERGE assigns the

default file type of .DAT to the output file, regardless of the file types of the input
files.

Command Qualifiers
ICHECK_SEQUENCE
INOCHECK_SEQUENCE

Examines the input files to be merged to make sure that they are in order. If a
record is out of order, MERGE displays the following warning message at the end
of the merge operation:
%SOR-E-BAD_ORDER, Input file [nl is out of order

The default is ICHECK_SEQUENCE.
ICOLLATING_SEQUENCE=sequence

Specifies the collating sequence in which records are to be arranged. The
sequence may be ASCII, EBCDIC, or MULTINATIONAL. The default is
ICOLLATING_SEQUENCE=ASCII.
IDUPUCATES
INODUPUCATES

Alternatively specifies how input files containing records with equal keys are to
be merged in the output file (see the previous ![NO]STABLE qualifier discussion).
The /NODUPLICATES qualifier specifies that only one record be retained when
MERGE encounters records with equal keys. The default is /DUPLICATES.
NOTE

Do not use /NODUPLICATES and /STABLE in the same merge
operation.
IKE"=(field[, ... J)

Defines a MERGE key. This qualifier can be specified up to ten times to define
ten different key fields to be merged.
The /KEY qualifier consists of two required arguments that define the position
and size of the key field within the record, and several optional arguments that
define the type of data within the key field. The arguments must be separated
with commas and enclosed in parentheses.

WORKING WiTH FilES

3-63

Required Arguments for the /KEY Qualifier
POSITION=n

Specifies the position of the key within each record, where the first
character of the record is position 1.

SIZE=n

Specifies the length of the MERGE key in characters, bytes, or digits,
depending on the key field data type. The total of all key field sizes
must be less than 255 bytes. The valid sizes, based on data type, are:

Data Type

Values forn

CHARACTER

1-255

BINARY

1,2,4,8

DECIMAL

1-31

NOTE

You cannot use the SIZE argument with floating point data types
(D_FLOATING, F _FLOATING, or ASCII_FLOATING).

Optional Arguments for the /KEY Qualifier

3-64

CHARACTER
BINARY
DECIMAL
ASCII_FLOATING
ASCII_ZONED
DIBOL_ZONED
D_FLOATING
F_FLOATING
PACKED_DECIMAL

Indicates the type of data in the MERGE key field. If not
specified, MERGE assumes that data is CHARACTER.

SIGNED
UNSIGNED

Indicates whether a binary or decimal key is to be compared
as a signed or an unsigned integer. UNSIGNED causes all
numbers to be treated as positive. SIGNED is the default.

LEADING_SIGN
TRAILING_SIGN

Indicates whether the sign of a decimal data type key
appears at the beginning or end of the key. If you specify
the key data type as DECIMAL, but do not specify either of
these subqualifiers, the default is TRAILING_SIGN.

OVERPUNCHED_SIGN
SEPARATE_SIGN

Indicates whether the sign of a decimal data type key is
superimposed on the decimal value or is separated from
the decimal value. If you specify the key data type as
DECIMAL, but do not specify either of these subqualifiers,
the default is OVERPUNCHED_SIGN.

ASCENDING
DESCENDING

Indicates whether the key is to be merged into ascending or descending order. If you specify neither of these
subqualifiers, the default is ASCENDING.

WORKING WITH FILES

IPROCESS=type

Defines the type of merge. You can specify one of the following merge types:
RECORD

Requests MERGE to resequence the entire contents of the input files and
create an output file containing the reordered records.

TAG

Requests MERGE to merge only the record keys, and then reaccess the
input files to create an output file containing the resequenced records.

ADDRESS

Requests MERGE to produce an address file merged by record keys. The
output file can be read as an index to read the original file in the desired
sequence.

INDEX

Requests MERGE to produce an address file containing the key field
of each data record and a pointer to its location in the input file. The
output file can be read to randomly access the data in the original file in
the desired sequence.

The default is IPROCESS=RECORD.
ISPECIFICATION[=file-spec]

Indicates that commands and file qualifiers, including key field definitions, are
contained in a specification file. See the PDP-ll SORT/MERGE User's Guide for
complete details on using specification files.
/STABLE
INOSTABLE

Specifies how input files containing records with equal keys are to be merged in
the output file. The default is INOSTABLE, which causes any records with equal
keys to be grouped together in the output file, possibly resulting in an unpredictable merge order for those particular records. The ISTABLE qualifier specifies
that any records with equal keys are to be directed to the output file in the order
in which they were input to MERGE. See the following I[NOJDUPLICATES
qualifier discussion.
ISTATISTICS
INOSTATISTICS

Specifies whether a statistical summary displays after the MERGE operation
completes. The default is INOSTATISTICS.
IWORK_FILES=n

Specifies the number of temporary work files to be used during the merge process.
You can specify 0 or any value from 3 through 10. A value of 0 indicates that no
work files are necessary because the data will fit in physical memory.

WORKING WITH FILES

3-65

Input File Qualifiers
IFORMAT =(file-attribute[, ... ])
Specifies attributes of the input file to override the existing data that MERGE
nonnaHy obtains through PDP-ll RMS. You can specify one or both of the
following arguments:
Defines the size of the file in blocks. This argument is required for
files that are not on disk or magnetic tape.
If no input file size is specified, MERGE uses the default value of
1000 blocks.
RECORD_SIZE:n

Specifies, in bytes, the length of the longest record, overriding
the record size defined in the file header or label. This argument
is required for files that are not on disk or magnetic tape, or if
the longest record length (LRL) is unavailable or known to be
inaccurate.

liN DEXED_ SEQUENTiAl[:::n]
Specifies that the organization of the input file is indexed-sequential. You specify
the number of keys (1 through 255) to make sure that MERGE allocates sufficient
RMS space. The default value is 1.
ISHAREABlE
INOSHAREABlE
Specifies whether the input files are opened in write-shareable mode. Use this
qualifier when you want to merge files that may be updated by another user
during the merge operation. The default is INOSHAREABLE.
TREE_SPACE=n

Specifies the percentage distribution of available work area between
SORTfMERGE tree-related data structures and I/O-related data structures.
You can specify from 1 to 100 percent (%). The default division of work area is
30% to the merge list and 70% to I/O.

Output File Qualifiers
I ALLOCATION=11

Specifies the number of 512-byte blocks to be allocated for the output file. By
default, MERGE allocates blocks based on the number of records sorted.
IBUCKET_SIZE
Used with disk files, this qualifier specifies the number of 512-byte blocks per
bucket for the output file. The maximum size you can specify is 32 blocks. If you
do not specify a bucket size, the bucket size of the output file defaults to that of
the input file.
ICONTIGUOUS
INOCONTIGUOUS
Specifies whether the allocation of disk space for the output file is to be contiguous. If you specify ICONTIGUOUS, you must also specify IALLOCATION
to define the number of blocks to allocate for the output file. The default is
INOCONTIGUOUS.

3-66

WORKING WITH FILES

IFORMAT=(record-format[, ... ])

Defines the output file record format. You can specify one or more of the following
arguments:
FIXED[=n]
VARIABLE[=n]
RMS_STREAM[=n]
STREAM[=n]
CONTROLLED[=n]

Defines the output file record format. and Rizp, where n is
the length of the longest record in the output file. If n is
not specified, the default is a length long enough to hold the
longest output record.

BLOCK_SIZE=n

Specifies, when the output file is directed to disk or magtape, the block size in bytes. If one or more input files is a
tape file, the output file block size defaults to the maximum
of the block sizes of all tape input files. If the input file is a
disk file, the default value is 512 bytes.

/INDEXED_SEQUENTIAL[ =n]

Specifies that the organization of the output file is indexed-sequential. You
specify the number of keys (1 through 255) to make sure that MERGE allocates
sufficient RMS space. The default value is 1.
ILOAD_FILL

Used only with indexed files, this qualifier loads the buckets according to the fill
size established when the file was created.
IOVERLAY
INOOVERLAY

Specifies whether an existing file is to be overlaid with the sorted records of the
input file. The default is /NOOVERLAY, which means a new output file is created
and does not overlay an existing file.
IRELATIVE

WORKING WITH FILES

3-67

3.7 Comparing Files: DIFFERENCES
The DIFFERENCES command compares two text files and lists any sections of
text that differ between the two files.

Format
DIFFERENCES

input-file-spec

Command Qualifiers
IIGNORE=BLANK_LlNES
IMATCH=size
IMAXIMUM_DIFFERENCES=n
IOUTPUT=file-spec

compare-fife-spec
Defaults
See discussion
IMATCH=3
IMAXIMUM_DIFFERENCES=300
IOUTPUT=KB:

Prompts
File 1:
input-file-spec
File 2:
compare-file-spec

DIFFERENCES compares the two files by groups of lines and produces an output
file if the /OUTPUT qualifier is used; otherwise, output is sent to the terminal.
This output file lists the differences, if any.
The qualifiers for the DIFFERENCES command can be categorized according to
their functions:
"

The IIGNORE=BLANKLINES qualifier requests DIFFERENCES to ignore
blank lines while comparing files.
By default, DIFFERENCES compares every line in each file.

The /MATCH and /MAXIMUM_DIFFERENCES qualifiers control the extent
of the comparison.
By default, DIFFERENCES reads every line in the first input file and looks
for a matching line in the second input file. Lines are considered matched
only if three identical sequential lines are found in each file.

The DIFFERENCES command normally displays its report at your terminal.
Use the IOUTPUT qualifier to request DIFFERENCES to write the output to an
alternate file or device. If the two files are significantly different, then the system
may print one of the following error messages:
?Maximum memory exceeded
?Maximum differences (300) encountered - skipping rest of file

For example, you may want to use DIFFERENCES to compare a file (such as
HOME.WRK) with its earlier backup version (HOME.BAK). The command line
you enter is:
$

3-68

WORKING WITH FILES

RSTS/E displays a message telling you which files it is comparing:
Comparing: 1) SY : [2,214]HOME.WRK to 2) SY: [2,214]HOME.BAK

Because you did not include a directory in the command line, the default is your
directory.
Next, RSTS/E displays the lines containing text that does not match. The
sections in the following example are labeled 1) and 2), corresponding to the first
and second file being compared. The sections of text are separated by rows of
asterisks (*):
******************************
1) SY: [2,214]HOME.WRK
the writings of Milton and
Donne . Fortunately, I find
their work interesting.

**********
2) SY: [2, 214] HOME.BAK
the writings of Marchand and
Hogan . Fortunately, I find
their work interesting .
?1 Difference Found

Notice that the numbers 1) and 2) correspond to HOME.WRK and its backup
version, HOME.BAK. DIFFERENCES lists the differences in the two files one
group of lines at a time.

Command Parameters
input-tile-spec
Specifies the name of the first input file to be compared.

You must include a file name. The default file type is null. You cannot use
wildcard characters in the file specification.
compare-tile-spec
Specifies the name of the second input file to be compared.

You must include a file name. The default file type is null.

Command Qualifiers
IIGNORE=BLANK_LlNES
Specifies that blank lines between data lines are to be ignored during the
comparison. By default, the DIFFERENCES command compares every line in
each file and reports all differences.

For example, if files REGAN.TOM and REGAN.sAM have similar contents but
have unequal numbers of blank lines, you can disregard the blank lines in their
comparison by typing:
$ DIFFERENCES REGAN.TOM REGAN.SAM/IGNORE=BLANK_LINES <RET>

IMATCH=size
Controls the number of lines that must be identical for DIFFERENCES to
consider them a match. For example, to make sure that five identical lines are
found to be considered a match between MARYB.TXT and BILL.TXT, type:
$ DIFFERENCES MARYB.TXT BILL.TXT!MATCH=5 <RET>

By default, after DIFFERENCES finds unmatched lines, it assumes that the files
match after it finds 3 sequential lines that match. The match size you specify
overrides the default value of 3.

WORKING WITH FILES

3-69

IMAXIMUM_DIFFERENCES=n
If you specify /MAXIMUM_DIFFERENCES, DIFFERENCES tenninates after
locating n differences. The output file lists differences only on lines compared
until the maximum has been reached.

For example, you may need to compare two large data files (MIKE.DAT and
EDDIE.DAT), but if more than four differences are found, any further comparison
would not be worth your while. In this case you type:
$ DIFFERENCES MIKE.DAT EDDIE.DAT/MAXIMUM_DIFFERENCES=4 <RET>

By default, DIFFERENCES aborts after 300 differences are found.
IOUTPUT=file-spec

Stores the result of the comparison in a file rather than displaying it at your
tenninal. If you omit the /OUTPUT qualifier, the output displays at your
tenninal.
The /OUTPUT qualifier is especially useful if you are using a video tenninal
and want a listing of the output. For example, you can request that the output
from comparing files RACE.A and RACE.B be stored in a file that you name
RESULT.C:
$ DIFFERENCES RACE.A RACE.B/OUTPUT=RESULT.C <RET>

If you specify /OUTPUT without a file specification, the output goes to a file with
the same file name as the first input file and a file type of .DIF. If you had not
assigned the file name RESULT.C in the previous example, it would have been
named RACE.DIF.

You cannot use wildcard characters in the file specification.

3-70

WORKING WITH FILES

3.8 Allowing Access to Files
This section describes what it means to assign protection codes to your files. Then
it explains how to use the SET PROTECTION command and the /DEFAULT
qualifier.

3.8.1

Using Protection Codes
A protection code determines who has access to a file.
The protection code consists of one to three decimal digits. This code determines
the file's degree of protection on two levels:
•

The actions (reading, writing, executing, and deleting) against which it is
protected. Anyone who can write in a file can also delete it, and vice versa.

•

The user or class of users against whom it is protected.

RSTSIE recognizes three classes of users for protection purposes:
•

Owner - The owner of the file, known to the system by a PPN (such as
[52,20]).

•

Group - The owner's group, known to the system by any PPN whose project
number (the 52 in [52,20]) is the same as the owner's project number. Group
read or write access also allows the owner read or write access.

•

World - All other users on the system, known to the system by any PPN
whose project number is different from the owner's. World read or write
access also allows both the owner and the owner's group read or write
access.

For example, 60 is the default protection code that RSTSIE normally assigns.
(The code is something other than 60 if your system manager changed the
default, or if you use the SET PROTECTION/DEFAULT command described in
the next section.) If one of your files has a protection code of 60, only you or
a user with sufficient privileges can read, edit, or delete it. A protection code
remains fixed unless you change it.
NOTE

Some users on your system (for example, the system manager) may
have privileges that allow them to access files regardless of the
protection codes.
When you create a file, RSTSIE assigns it the default protection code 60:
$ CREATE ANNIE.OAT <RET>
Here's a file of only one line.
<Ctrl/Z>
$ OIR ANNIE.OAT <RET>

Name .Typ
ANNIE .OAT

Size
1

Prot
< 60>

Name .Typ

Size

Prot

SY: [52,20]

Total of 1 block in 1 file in SY: [52,20]

WORKING WITH FILES

3-71

You assign a protection code with the SET PROTECTION command, as in:
$ SET PROTECTION=40 ANNIE.OAT <RET>
.OAT<40>
ANNIE
. OAT renamed to ANNI E
$ OIR ANNIE.OAT <RET>

Name . Typ
ANNIE . OAT

S i ze
1

Prot
< 40>

Name . Typ

Size

Prot

SY: [52,20]

Total o f 1 block in 1 fi l e in SY: [ 52,20 ]

A factor in assigning protection codes is whether a file is executable. An executable file is produced by the LINK command or by the COMPILE command of
BASIC-PLUS or BASIC-PLUS-2. An executable file contains the protection code
64.
A nonexecutable file, on the other hand, is any file that does not contain a
protection code of 64. Table 3-4 lists the file protection codes for nonexecutable
files.
Table 3-4:

File Protection Codes for Nonexecutable Files

Code

Merurlng

Protection against reading by owner

Protection against writing by owner

Protection against reading by owner's group

Protection against writing by owner's group

Protection against reading by anyone not in the owner's group

Protection against writing by anyone not in the owner's group

128

A protected data file; overwritten with zeros when deleted

Individual codes added to the executable protection code 64 have meanings
different from those above.
Table 3-5 lists the compiled codes for executable files (64 + code).
Table 3-5:

File Protection Codes for Executable Files

64 + Code

Meaning

Execute protection against the owner

Read and write protection against the owner

Execute protection against the owner's group

Read and write protection against the owner's group

Execute protection against all others not in the owner's group

Read and write protection against all others not in the owner's group

128

Program with privileges

The protection code you set for a file is the total of the code numbers for the
types of protection you want. For example, the usual system default (60) protects
against reading, writing, and deleting by all users except its owner, because it is
a sum of 4, 8, 16, and 32.

3-72

WORKING WITH FILES

Table 3-6 lists common codes and their meanings.
Table 3-6:

Common File Protection Codes

Code

Sum of Codes

Meaning

232

128+64+32+8

Executable file that is privileged and protected against
reading and writing by anyone except owner. However,
anyone can execute the file.

124

64+32+16+8+4

Executable file that is protected against reading, writing, and
execution by anyone except owner.

104

64+32+8

Executable file that is protected against reading and writing
by anyone except owner. However, anyone can execute the
file.

32+16+8+4+2

Protected against reading by anyone except owner. Protected
against accidental deletion or modification by owner or anyone
else.

32+16+8+4

Protection against reading and writing by anyone except
owner.

32+16

Protection against reading and writing by anyone not in
owner's group. Can be read or written by anyone in owner's
group.

32+8+2

Protection against writing by anyone including owner; readable by everyone.

32+8

Protection against writing by anyone except owner; readable
by everyone.

No protection (any user can read, write, and delete).

WORKING WITH FILES

3-73

3.8.2

SET PROTECTION
The SET PROTECTION command specifies the protection code of a file. You
assign a protection code to determine who else, if anyone, can have 8CCeR!'l to your
files. (To check the protection codes of your files, use the /PROTECTION qualifier
with the DIRECTORY command.)
A file specification and protection code are required unless you use the /DEFAULT
qualifier. You must include either an equal sign or a space between the command
SET PROTECTION and the protection code you specify.

Format
SET PROTECTION[=]n

filespec[, ...J

Command Qualifiers
IBEFORE=date
I[NO]CONFIRM
ICREATED
IDEFAUlT
IMODIFIED
I[NO]QUERY
I[NO]lOG
ISElECT=SIZE=n
=MINIMUM=n
=MAXIMUM=n
=(MINIMUM=m,MAXIMUM=n)
ISINCE=date

Defaults
none
INOCONFIRM
none
IDEFAUlT
none
INOQUERY
IlOG
See discussion

none

For example, you set the protection code of a file named TIME.TRY to 42 by
typing:
$ SET PROTECTION=42 TIME.TRY <RET>

Command Parameters
n
The value you specify for n can be any of the protection codes in Table 3-4,
Table 3-5, and Table 3-6, depending on the privileges you have been given by the
system manager.
filespec[, ... ]
You can include one or more file specifications in the command string. Wildcard
characters are allowed.

3-74

WORKING WITH FilES

Command Qualifiers
IBEFORE=date
ISINCE=date
ICREATED
IMODIFIED

Changes the protection codes of files created or modified before or since the
specified date. See Chapter 2 for information on specifying dates and times.
I CONFIRM
INOCONFIRM

Prompts for permission to change a file protection code. This qualifier is
synonymous with IQUERY. The default is /NOCONFIRM.
IDEFAULT

The /DEFAULT qualifier specifies the default protection code of each file you
create. (You can override the default for individual files.) /DEFAULT stays in
effect until you logout.
If you use SET PROTECTION/DEFAULT, RSTSIE assigns the protection code

you specify to all files you create during the current session. Do not include a file
specification when you use the /DEFAULT qualifier. Also, you must include either
an equal sign or a space between the command and the protection code:
SET PROTECTION[=]n/DEFAULT

IQUERY
INOQUERY

The IQUERY qualifier prompts you to state whether you want to change a file's
protection code. The default is /NO QUERY.
The IQUERY qualifier is useful only when you use wildcards in the file specification. You can enter one of the following responses to the question mark
prompt:
Y

Yes, change the protection code

No, do not change the protection code

<RET>

No, do not change the protection code

Return to command level

For example, if you have several files named MOODY, you can determine their
protection codes as follows:
$ SET PROTECTION=40/QUERY MOODY.* <RET>
[ 52,20]MOODY .DAT? Y <RET>
MOODY.DAT renamed to MOODY.DAT < 40>
[52,20]MOODY .LIN? N <RET>
[52,20]MOODY .JON? <Ctrl/Z>

Do not use either the IQUERY or /NOQUERY qualifiers with /DEFAULT.

WORKING WITH FILES

3-75

flOG
fNOlOG
Detennines whether RSTSIE displays a message to confinn that a file's protection
code was changed. The default is !LOG. To suppress the message when changing
the protection code of a file (such as STRIPE.LIS), type:
$ SET PROTECTION=64 STRIPE.LIS/NOLOG <RET>

Unless you specify INOLOG, a message displays:
$ SET PROTECTION=64 STRIPE.LIS/LOG <RET>
STRIPE.LIS renamed to STRIPE.LIS < 64>

Do not use !LOG or INOLOG with /DEFAULT.
fSElECT =SIZE=n
fSElECT=SIZE=MINIMUM=n
fSElECT=SIZE=MAXIMUM=n
fSElECT =SIZE=(MINIMUM=m,MAXIMUM=n)
Selects files based on their size. The specified size can be:

3-76

Selects only those files with size equal to n.

MINIMUM=n

Selects only those files with size greater than or
equal to n .

MAXIMUM=n

Selects only those files with size less than or
equal to n.

MINIMUM=m,MAXIMUM=n

Selects only those files with size between m and n
inclusive.

WORKING WITH FILES

3.9 Setting File Cha.racteristics: SET FILE
In addition to the SET PROTECTION command described in the previous section,
you can use the SET FILE command to specify protection code, as wen as other
characteristics of a file.

Forma.t
SET FILE

file-spec

Command Qualifiers

Defaults

[NO]BACKUP
[NO]CACHE
=RANDOM
=SEQUENTIAl
/NOCONTIGUOUS
/[NO]DElETABLE
/[NO]IGNORE
/[NO] lOG
/[NO]PLACED
/PROTECTION=n
/RUNTIME_SYSTEM=name

none
See discussion

none

none
none
See discussion

none
none
none

Command Parameters
file-spec
Specifies the file whose characteristics you want to set or change.

Command Qualifiers
/BACKUP
/NOBACKUP

Indicates whether BACKUP records the contents of the file. The INOBACKUP
qualifier causes BACKUP to record the attributes of the file but not its contents.
The INOBACKUP qualifier is useful for saving files that contain unimportant
data, such as SWAPFILES.
/CACHE
/CACHE=RANDOM
/CACHE=SEQUENTIAL
/NOCACHE

Detennines whether a file is cached when open and, specifies the caching mode.
You can specify either RANDOM or SEQUENTIAL for the cache-mode parameter,
which marks the file's UFD entry so that the file is automatically cached when
open.
The default is /CACHE=RANDOM if you do not specify a cache-mode parameter.
The INOCACHE qualifier specifies that the file is not automatically cached when
open. Th cache such a file, use the SET CACHE/ALL command.
WORKING WITH FILES

3-77

fNOCONTIGUOUS
Lets you extend a contiguous file by changing it to noncontiguous.
fDElETABlE
fNODElETABlE
Indicates whether a file can be deleted or renamed during timesharing. In
a directory listing, RSTSIE shows NODELETABLE files by displaying the P
(protected) flag after the size.
/IGNORE
fNOIGNORE
Indicates whether BACKUP looks at the file. The !IGNORE qualifier causes
BACKUP to completely ignore the file during all operations.

The !IGNORE qualifier is used for excluding temporary files from backup sets.
flOG
fNOlOG
Specifies whether the file specification of each modified file is displayed at the
terminal. If the file specification contains any wildcards, the default is /LOG.
Otherwise, the default is INOLOG.
fPlACED
fNOPlACED
Specifies whether a file, after modification, is placed at its present position on the

disk.
fPROTECTION=n
Specifies the protection code of a file. The protection code must be in the range
o to 255. You can also use the SET PROTECTION command, described in the
previous section, to specify a file's protection code.
fRUNTIME_SYSTEM=name
Specifies the run-time system associated with the file.

3-78 WORKING WITH FILES

Chapter 4

System and Account Operations

This chapter describes the commands that let you perform common system and
account operations, such as:

4.1

•

Displaying system status

•

Displaying account information

•

Changing your password

•

Sending a message to the system operator's terminal

SHOW
Use the SHOW command to display information about the system and its
resources, as well as the current status of your job or account.
To specify the type of information you want the SHOW command to display, use

one of the options listed in Table 4-1.
NOTE

The SHOW command has additional capabilities for users with greater
levels of privilege. See the RSTS / E System Manager's Guide for more
information.

Format
SHOW

option

Table 4-1 lists the options that you can use with the SHOW command.
Table 4-1:

SHOW Command Options

Option

Displays

ACCOUNT

Infonnation about accounts. See this
chapter for more infonnation.

BUFFERS

Infonnation about available buffers,
in-use and maximum job count, hung
tenninal count, and total logged errors.

(continued on next page)

System and Account Operations

4-1

Table 4-1 (Cont.):

SHOW Command Options

Option

Displays

CACHE

Current cache settings.

COUNTERSILAT

Information about counters that is
relevant to managing !AT on the host
node.

DATE
DAYTIME
TIME

Current date and time.

DEVICE [dev[:]] DEVICE/ALL

Status of devices in use on the system, or
a device you specifY. See Chapter 6 for
more information.

DEVICE/ALLOCATED

All allocated or open devices, excluding
terminals and disks. See Chapter 6 for
more information.

DISKS

Status of all mounted disks. See Chapter
6 for more information.

ENTRY [entry]
ENTRY/ALL

Print or batch entries that have been
queued. See Chapter 7 for more information.

FILE [file-spec]
FILE/ALL

Information about installed files on
the system. See the RSTS / E System
Manager's Guide for more information.

JOB [job-number]
JOB/ALL

Status of jobs on the system. See this
chapter for more information.

JOBIPRIVILEGES

Privileges assigned to your account.

LIBRARY

All installed resident libraries and
dynamic regions.

LOGICAL [name]

Information about a logical name, or
all systemwide and user-defined logical
names.

MEMORY

Status of system memory allocation.

NETWORK

Names of the nodes that your system can
access.

NODEILAT

Information about the current LAT host
node characteristics.

OPERATOR_SERVICES

Status of the Operator Message Services
(OMS) package.

PORT [name[:]]

Characteristics of LAT ports on the
RSTSIE node.

PRINTER [printer-name[:]]
PRINTER/ALL

Characteristics of all printers on the
system, or the printer you specify.

QUEUE [queue-name[:]]
QUEUE/ALL

Characteristics of a print or batch queue.
See Chapter 7 for more information.

RECENERS

Status of all declared message receivers.

RUNTIME_SYSTEMS

Status of all installed run-time systems.

(continued on next page)

4-2

System and Account Operations

Table 4-1 (Cont.):

SHOW Command Options

Option

Displays

SERVER [server-name[:]]
SERVER/ALL

Characteristics of one or more servers in
the PrintlBatch Services (PBS) facility.
See the RSTS / E System Manager's
Guide for more information.

SERVICESILAT [service_name]

Information about the service(s) offered
by the LAT host node.

SESSIONS [server_name]

Information about the sessions currently
running LAT on the host node.

SYMBOL [symbol-name]
SYMBOUALL

Value of a specified symbol or all symbols
in a local symbol table or the global
symbol table. See Chapter 6 for more
information.

SYSTEM

System default characteristics. See this
chapter for more information.

TERMINAL

Characteristics of your terminal. See
Chapter 5 for more information.

TERMINAL_SERVERSILAT [server_name]

Information about the terminal server
known to the LAT host node.

USER [PPNl
USER/ALL

Information about attached jobs, or all
jobs, on the system. See this chapter for
more information.

System and Account Operations

4-3

4.2 System and Account Status
The SHOW USER command di!'lplays information about. users who are logged in
and what system resources they are using. The SHOW JOB command displays
the status of your current job. The SHOW SYSTEM command displays the
default characteristics of the system. The SHOW ACCOUNT command displays
data about an account.
The following is an example of the SHOW USER command, along with an
explanation of each numbered element in the display:
$ SHOW USER <RET>

RSTS V10.0-L

status at 09-Jun-90, 05:50 PM Up : 2 6:22:19

Job
3
5

Who
1,226
1,214
1,196
1,231

Where
KB27
KB26
KB30*
KB45!

What
NET
SYSTAT
DCL
BACKUP

Size
17/64K
20/64K
4/64K
15/64K

State
SL
RN Lck
"C
SL

Run-Time RTS
3.4
.. . RSX
3.2
... RSX
9:39.4 DCL
8:13.6 ... RSX

The display tells you the following:
1. System status information - You are using RSTS/E Version 10.0-L software.
At the present day and time (09-Jun-90, 05:50 PM) the system has been
operating for 2 days, 6 hours, 22 minutes, and 19 seconds (Up: 26:22:19).

2. Job - There are five attached jobs now in use on the system.
3. Who - This column displays the accounts to which the jobs belong.
4. Where - This column displays the keyboards controlled by the jobs. The
asterisk (*) following KB30 indicates a dialup line.
The exclamation point (!) following KB45 indicates a LAT line.
5. What - Various operations (SYSTAT, BACKUP) are being performed.
6. Size - These numbers indicate both the actual size of your job, as well as the
size to which the job can expand. The size is shown in thousands of words or K words - of computer storage space. In computing, K approximates
thousand-word units of memory storage (actually 1K=1024 words). The Size
column is mainly to tell you the load each job places on the system.
7.

State - The status of each job is determined by the operation being
performed. For example, the SYSTAT job's status is RN Lck. This means that
the job is running or waiting to run (RN), and that it is locked in memory
(Lck) during the SYSTAT operation. The SYSTAT operation is completed
when the display appears at your terminal and is followed by the DCL
prompt, which shows that your job is no longer locked in memory.

Run-Time - The system keeps track of the CPU time each job uses. For
example, the BACKUP job has used a total of 8 minutes and 13 seconds of
CPU time.

9. RTS (Run-Time System) - RSTS/E provides a variety of run-time systems,
including DCL and null RTS (shown on the display as "... RSX").
Table 4-2 shows the elements you may find in a system status display. You
might want to refer to this table when you use the SHOW USER or SHOW JOB
commands.

4-4

System and Account Operations

Table 4-2:

SHOW USER and SHOW JOB Abbreviations

Abbreviation

Meaning

Description

Where Column
DET

Detached

Job is detached from all terminals.

Dialup

Job is running over a dialup line.
Who Column

** ,**

Job is not logged in to the system.
State Column (Job Status)

Run

Job is running or waiting to run.

Residency

Job is waiting for residency. (The job
has been swapped out of memory and is
waiting to be swapped back in.)

Buffers

Job is waiting for buffers (no space is
available for I/O buffers).

Sleep

Job is sleeping (SLEEP statement).

SendiReceive

Job is sleeping and is a message receiver.

File Processor

Job is waiting for file processing by the
system (opening or closing a file, file
search).

Terminal

Job is waiting to perform output to a
terminal.

Hibernating

Job is detached and waiting to perform
I/O to or from a terminal. (Someone
must attach to the job before it can
resume execution.)

Keyboard

Job is waiting for input from a terminal.

CtrlJC

Job is at command level, awaiting
a command. (In other words, the
keyboard monitor has displayed its
prompt and is waiting for input.)

Card Reader

Job is waiting for input from a card
reader.

MT,MM,orMS

Magnetic tape

Job is waiting for magnetic tape I/O.

Line Printer

Job is waiting to perform line printer
output.

DECtape

Job is waiting for DECtape I/O.

DK, DM, DB, DP,
DL,DR,DU

Disk

Job is waiting to perform disk I/O.

Flexible Diskette

Job is waiting to perform flexible
diskette I/O.

RJ2780

Job is waiting for RJ2780 I/O. (The
RJ2780 is a device for communicating
with an IBM system.)

(continued on next page)

System and Account Operations

4-5

Table 4-2 (Cont.):

SHOW USER and SHOW JOB Abbreviations

Abbreviation

Meaning

Description

State Column (Job Status)

Job's state cannot be determined by the
SHOW command.

+ or-

Temporary Privileges

Job has temporary privilege. A plus
sign (+) means that the temporary
privilege is active. The minus sign (-)
means that the program has temporary
privilege, but that it is not active.

The following status descriptions may appear after
one or more of the other job state abbreviations:
Lck

Locked

Job is locked in memory for the current
operation.

Nsw

No Swapping

A program has requested that the job
not be swapped from memory.

Swi

Swapping In

Job is currently being swapped into
memory.

Swo

Swapping Out

Job is currently being swapped out of
memory.

Xnn

Job is swapped out and occupies slot nn
in swap file X; file is denoted by A, B,
C, or D to represent files 0 through 3 of
the swapping structure. For example,
A13 means slot 13 of swapping file 0
(SWAPO.SYS).
RTS Column (Run-time System) 1

BASIC

The BASIC-PLUS run-time system.

BASIC2

BASIC-PLUS-2

The BASIC-PLUS-2 run-time system.

DCL

The Digital Command Language (DCL)
keyboard monitor.

RTll

The RTll run-time system.

RSX

The RSX run-time system.

... RSX

"Null RTS," meaning the monitor is
executing your job directly without
using a run-time system.

1 Any run-time system available on your system may appear in this column. Some of the most
commonly used run-time systems are listed here.

4.2.1

Attached and Detached Jobs
Some of the command displays of system status involve attached and detached
jobs. An attached job is one that is associated with a tenninal, and thus allows
user input. By contrast, a detached job on RSTS/E is used to perfonn various
system functions, such as printing files on the line printer.

4-6

System and Account Operations

For example, suppose the system manager invokes a program at system start-up
time to keep track of jobs that run through any queue on the system. RSTSIE
considers that job to be detached, because it is not associated with a specific
terminal.
You may not recognize the names of programs that are run by detached jobs.
They need not be standard RSTSIE programs-some could be created at your
site. In addition, some of these programs are used primarily by the system
manager. Programs for system management are described in the RSTS / E System
Manager's Guide.
The following is an example of a display produced by the SHOW USER/ALL
or SHOW JOB/ALL commands. Note that both attached and detached jobs are
displayed:
RSTS V10.0-L

status at 09-Jun-90, 05:50 PM Up: 6:22:34

Job
1
2
4
7
12
15
17

Where
Det
Det
KB30
Det
P1J17
KB26
Det

Who
1,2
1,2
1,196
1,2
1,217
1,214
1,2

What
ERRCPY
OPSRUN
DCL
QUMRUN
DCL
SYSTAT
PBS ...

Size
11/64K
22/64K
4/64K
24/64K
14/64K
20/64K
18/64K

State
SR A40
SL
"C
SL
RN
RN Lck
SL

Run-Time
10.2
2:44.7
9:39.4
1:04.5
8:52.8
5.2
6:00.0

Pri/RB
0/6
-8/6
-8/6
0/6
-16/6
-8/6
-8/6

RTS
... RSX
... RSX
DCL
... RSX
DCL
... RSX
... RSX

System and Account Operations

4-7

4.2.2

SHOW USER
The SHOW USER command displays information about the status of jobs on the
system.

Format
SHOW USER

[[p,pnll

Command Qualifiers
IAll
IAlTACHED
IDETACHED
I[NO]OUTPUT[=filespec]
ITERM INAl=KBn:

Defaults
none
none
none
none
none

Command Parameters
[[p,pn]]
Specifies the account whose jobs are to be displayed. If you do not specify an
account, the SHOW USER command displays all attached jobs on the system.

Command Qualifiers
IAll
Specifies that all jobs, both attached and detached, be displayed.
IATTACHED
Specifies that only attached jobs be displayed.
IDETACHED
Specifies that only detached jobs be displayed.
IOUTPUT[=filespec]
INOOUTPUT
Writes the information to the specified file. If you specify INOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.
ITERMINAl=KBn:
Specifies that only the job logged in at a particular terminal be displayed.

4-8

System and Account Operations

4.2.3

SHOW JOB
The SHOW JOB command, like SHOW USER, also displays infonnation about
the status of jobs on the system. This command is more convenient, however, for
quickly showing the status of only your own job.

Format
SHOW JOB

ljob-number]

Command Qualifiers
fAll
IATIACHED
IDETACHED
I[NOjOUTPUT[=filespec]

Defaults

none
none
none
none
none

/TERMINAl=KBn:

Command Parameters
job-number
Specifies the the job number to be displayed. If you do not specify a job number,
the SHOW JOB command displays only your own job. For example:
$
5

1,214

KB26

SYSTAT

20/64K

RN Lck

4.2

-8/6

... RSX

Command Qualifiers
IAll
Specifies that an jobs, both attached and detached, be displayed.
IATTACHED
Specifies that only attached jobs be displayed.
IDETACHED
Specifies that only detached jobs be displayed.
IOUTPUT[=filespec]
INOOUTPUT
Writes the information to the specified file. If you specify /NOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.

ITERMINAl=KBn:
Specifies that only the job logged in at a particular terminal be displayed.

System and Account Operations

4-9

4.2.4

CTRlIT
In addition to using the SHOW JOB command, you can get a quick one-line
status report on your current job by pressing Ctrlfr. When you press CtrlfI',
RSTSIE displays a report similar to the following:
18

GARP: :KB32

TEST+BAS4F

KB(OR) 11(16)K+16K 3.3(+.5)

The report shows:

4-10

Your current job number (for example, 18)

The node name of your system (for example, GARP)

The keyboard number of your terminal (for example, KB32)

The name of the progTam or operation you are currently running (for example,
TEST)

The current run-time system name (for example, BAS4F)

The current job state (for example, KB(OR))

The current program size in K-words (for example, 11). If two numbers
appear in this field (for example, 4+10), it represents the instruction size and
the data size or a split I & D space task.

The maximum progTam size in K-words (for example, (16)K)

The run-time system size in K-words (for example, +16K)

The amount of CPU time in seconds your job has used (for example, 3.3)

The amount of time the job has run since the last Ctrltr (for example, (+.5))

System and Account Operations

4.2.5

SHOW PORT
This command displays the characteristics of LAT ports on the RSTS/E node.
By default, both interactive and application ports are displayed. The information shown includes the local port name, the port type (either Interactive
or Application) and the default queued setting (either Queued or Nonqueued),
the terminal server name, the remote service (if specified), the remote port (if
specified) and the connection status.
If the port is not assigned to a terminal server, only the local port name and
type are displayed. If the port is assigned but not yet connected, the requested
terminal server, remote service, and remote port are shown. If the port is

waiting to connect, the connection status "In Progress" is shown; if the connection
is queued, the queue position is also displayed. If the port is connected, the
terminal server, the remote service and the remote port to which it is actually
connected are shown, and the job number is displayed. Example:
$ SHOW PORT

Port Type Terminal Server Remote Service Remote Port Connect Status

--KBI A,Q SERVER
KB2
KB3
KB4
KBs
KB6
KB7

SERVICE A

A,NQ SERVER 1
A,Q SERVER 2
A,Q SERVER 2
A,NQ Not Assigned
I,NQ SERVER 3
I,NQ SERVER 3

A=Application Port

SERVICE C
SERVICE C

I=Interactive Port

PORT 1
PORT 1
PORT 2

Connected, Job=3
Not connected
I n Pr ogress
Queue Pos=I

TWAs5
TWAS 6

Connected, Job=I
Connected, Job=2

Q=QUEUED

NQ=NOQUEUED

Format
SHOW/PORT

[port-name]

Command Qualifiers
fAll
f[NO]APPLICATION
f[NO]INTERACTIVE
fLAT
f[NO]OUTPUT[=filespec]

Defaults
fAll
none
none
flAT
your terminal

Prompts
none

Command Parameters
port-name
Specifies the name of the local port for which characteristics will be displayed.
The porCname must be in the form of KBIn: or KBn: where n is a value from 0
through 127. If a porCname is not specified, the characteristics for all ports are
shown.

System ~nrl Account Orwmtions

4-11

Command Qualifiers
fAll
Generates a display of aU LAT ports, both application and interactive. The
default is fALL.
f[NO]APPlICATION

Generates a display of all LAT application ports. This qualifier is ignored if a
port_name is specified. If /NOAPPLICATION is specified, only interactive ports
are displayed.
f[NO]INTERACTIVE
Generates a display of all LAT interactive ports. This qualifier is ignored if a
port_name is specified. If INOINTERACTIVE is specified, only application ports
are displayed.
flAT
Indicates that LAT ports are to be displayed. The default is /LAT.
f[NO]OUTPUT[=filespec]
Writes the information to the specified file. If you specify INOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on your terminal.

4-12

System and Account Operations

4.2.6

SHOW SYSTEM
The SHOW SYSTEM command displays the default characteristics of the system.
For example:

System name:
Currently installed Monitor:
Swap Maximum:
Date format:
Time format:
Magtape label default:
Magtape density default:
Power fail restart delay:
Dynamic Region Limit:
Hangup:
Monitor Statistics:
Job limit:
Current jobs:
Password Prompting:
Last System Password change:
LAT Software:
FMS Software:
Current Pseudo keyboards:
Answerback message:

RSTS VIO.O-L BSRTD::
VIOLAT
66K

Alphabetic
AM PM
DOS
800 BPI
300 seconds
OK words
Delayed
Enabled
45
37
All users
02-Jul-90 at 02:21 PM
Installed
Upon reboot: Not installed
Not Installed Upon reboot: installed
10
None

Format
SHOW SYSTEM
Command Qualifiers
/EMT_LOGGING
/[NO]OUTPUT[=filespec]

Defaults
none
none

Command Qualifiers
/EMT_LOGGING

Displays the status of each EMT loggable.
/OUTPUT[=filespec]
/NOOUTPUT

Writes the information to the specified file. If you specify /NO OUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.

System and Account Operations

4-13

4.2.7

SHOW ACCOUNT
The SHOW ACCOUNT command displays data about an account.

Format
SHOW ACCOUNT

[device-name :[p,pnJJ

Command Qualifiers

Defaults

IACCOUNTING_DATA
IBRIEF
IFULL
I[NO]OUTPUT[=filespec]

See discussion
IBRIEF
IBRIEF
See discussion

Command Parameters
device-name:[p,pn]
Specifies the disk and account to be displayed. If you do not specify the disk, the
default is SYO:; if you do not specify account, the default is your own PPN.

Command Qualifiers
IACCOUNTING_DATA
IBRIEF
IFULL

Specifies the amount or type of information to be displayed about the account.
If you specify IACCOUNTING_DATA, RSTSIE displays accounting information
only. For example:
$ SHOW ACCOUNT/ACCOUNTING_DATA <RET>

Accou n t

Name

Alloca ti on

KCT

CPU - Time

Connect

Dev ice

46 92

10 4 11 24

01 :4 0 : 27 . 3

91 : 21

02:4 8

[1 ,2 1 4 ]

If you specifY !BRIEF (the default), RSTSIE displays brief general information
about your account. For example:
$ SHOW ACCOUNT <RET>

Acco unt

Name

Allocation

[ 1,2 1 4 ]

4-14

System and Account Operations

46 92

IDNCLP
IDN

P KB2 :

Last Login
19 - Jun- 90 10 : 48 AM

Expires

If you specify !FULL, RSTSIE displays complete information about your account.
For example:
_SY: [52,20]

Account Display

- SY: [52,20]

"Mary Smith"

RSTS V10.0-L BSRTD::
03:27 PM on 19-Jun-90
Created: 26-May-87

Privileges:

DATES DEVICE EXQTA
JOBCTL MOUNT OPER
SWCFG SWCTL SYSIO
WRTNFS WWRITE

Attributes:

INTERACTIVE
NOLOOKUP

Quotas:

Disk usage
Job limits
Send/Receive

GACNT GREAD GWRITE HWCFG
PBSCTL RDMEM RDNFS SEND
SYSMOD TMPPRV TUNE
USERl

DIALUP
NETWORK
PASSWORD PROMPT

- Logged out:
-

Detached:
RIB:

Accounting:

CPU Time:
Device Time:
Connect Time:
Blocks allocated:

unlimited
10
1

48:22:55.1
40:57
219:44
2464

HWCTL INSTAL
SETPAS SHUTUP
WACNT WREAD

NOCAPTIVE
NOEXPIRE
Logged in:
Total:
Message:

unlimited
unlimited
unlimited

Kilo-Core Ticks:
UFD Clustersize:
UFD Size:
UFD Used:

41949386
16
2

9.8%

Last Password change on 01-Jun-90 at 06:06 PM
Last interactive login on KB61: on 19-Jun-90 at 08:00 AM
Last non-interactive login on 12-Jun-90 at 05:00 PM

IOUTPUT[=filespec]
INOOUTPUT

Writes the information to the specified file. If you specify /NOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the tenninal.

System and Account Operations

4-15

4.3 SET
Use SET and an option to d~fine or change certain defl'Iult chllrllctenRtlcR, Ruch
as the default protection codes the system assigns to your files.

Format
SET

option

Table 4-3 lists the options that you can use with the SET command.
Table 4-3:

SET Command Options

Option

Function

ENTRY

Modifies an entry on a print or batch queue. See Chapter 7 for more
information.

FILE

Specifies the characteristics of a file. See Chapter 3 for more
information.

HOST

Specifies the network node to connect your terminal to, so you can
log in to that node. See Chapter 1 for more information.

LOG_FILE

Selectively enables or disables output to a log file that you previously opened with the OPENILOG_FILE command. See Chapter 5
for more information.

PASSWORD

Lets you change your password. See this chapter for more information.

PROMPT

Lets you change your prompt text. See this chapter for more
information.

PROTECTION

Determines the protection code of a file. See Chapter 3 for more
information.

TERMINAL

Specifies the characteristics of a terminal. See Chapter 5 for more
information.

NOTE

The following SET options are used in command procedures. See the
RSTS / E Guide to Writing Command Procedures for more information
on how to use these options

4-16

[NO]CONTROL=C

Controls CTRLlC checking within a command procedure.

[NO]DATA

Controls whether DCL reads data required by a program or a
command from your terminal, rather than from a command file.

[NO]ECHO

Controls whether terminal output is enabled or disabled during
command procedure execution.

[NO]ON

Controls error checking within a command procedure.

[NO]VERIFY

Controls whether DCL command lines are displayed during command procedure execution.

System and Account Operations

4.3.1

SET PASSWORD
The SET PASSWORD command lets you change your own password at any time
to provide a greater level of protection against unauthorized users of the system.
To maintain secrecy, you should change your password frequently.
Usually, all users are granted the privilege to do this; however, in some cases
the system manager may restrict which users have the right to change their
passwords.

Format
SET PASSWORD

device-name:[p,pn]

Command Qualifiers
/[NO] lOG

Defaults
flOG

Prompts
Old password: old password
New password: new password
New password again, for verification: new password

Command Parameters
device-name:[p,pn]
Specifies the disk and account for which the password is to be changed. Unless
you have sufficient privileges, you can only change your own account's password.
If you do not specify the disk, the default is SYO:; if you do not specify an account,
the default is your own PPN.

Command Qualifiers
flOG
fNOlOG
Specifies whether the following message, confirming that the password was
changed, displays:
Password set for account dev:[PPN].

The default is fLOG.
Passwords can contain from 6 to 14 characters. The characters can be in
uppercase, lowercase, or a combination. Valid characters are:
•

A through Z

•

a through z

•

0 through 9

•

Any printable character (for example, $, *,#, +, ), including spaces, except the
question mark (?) character.

System and Account Operations

4-17

Digital recommends the following guidelines to minimize the chances that
unauthorized users can discover your password either by trial and error guessing
or a systematic search:
•

Do not use names or words that could be readily associated with any user (for
example, WRITER, GUEST, or any part of your name).

•

Change your password at least once a month.

When you type your password, RSTSIE does not display (echo) your input; this
helps ensure secrecy. To protect against typing errors that you cannot see when
you enter your new password, you must type the new password twice. If you do
make an error, an error message displays and the password remains unchanged.
NOTE

In some cases, the system manager may have modified your account
with a special qualifier (/LOOKUP). If so, you will not be able to use
a password over six characters long, and you can only use letters and
digits. See your system manager if you have trouble changing your
password.

4-18

System and Account Operations

4.3.2

SET PROMPT
The SET PROMPT command allows you to change your prompt text. The prompt
can be an expression or a quoted string. The maximum length allowed is 255
characters.

Format
SET PROMPT

[prompt]

Command Qualifiers
flOG_FilE

Defaults
none

Command Qualifiers
fLOG_FILE
Enables the specified prompt only while logging your terminal session.

System and Account Operations

4-19

4.4 REQUEST
The REQUEST command displays a message at all operator terminals.

Format
REQUEST

['1message[']

Command Qualifiers
IPROMPT
I[NO]REPLY[=DCL-symbol-name]
I[NO]TIME_OUT[=wait-minutes]

Defaults
none
IREPLY
See discussion

When you use the REQUEST command to send a message to an operator, the
message is displayed at all defined operator terminals.

Command Parameters
message
Specifies the text of a message to be displayed at operator terminals. For
example:
$ REQUEST "Do we need more paper for the line printer?" <RET>

The command can have a maximum length of 255 characters.

Command Qualifiers
IPROMPT
Causes you to be prompted for multiple lines of text that will make up the text
of the request. The text is entered in a manner similar to the CREATE and
BROADCAST commands. The length of this request text can have a maximum of
500 characters. This qualifier conflicts with the request-text parameter, and will
cause an error if both are specified on the same command line.
I[NO]REPLY[=DCL-symbol-name]
Indicates whether a reply is expected. /REPLY indicates that a reply is required.
The job will be placed in a wait state until an operator replies to the request,
or the user types CtrllC to cancel the request. The optional [DCL-symbol-name]
indicates the text of the operator's reply will be placed in the specified DCL
symbol. You can specify !LOCAL or IGLOBAL to indicate whether the symbol
should be placed in the local symbol table or the global symbol table. The default
is !LOCAL.

/NOREPLY indicates that no reply is expected, and control returns to DCL after
the REQUEST has been sent.
I[NO]TIME_OUT[=wait-minutes]
Specifies the length of time (in minutes) to wait for a reply. If no reply is given
after the amount of time specified, the request will be canceled and control
returned to DCL. You can specify any integer in the range 1-255. By default,
there is no time limit imposed on the REQUEST command.

4-20

System and Account Operations

Chapter 5

Terminal Status and Operations

This chapter describes various operations you perform on your terminal, including
the following:
•

Displaying and setting terminal characteristics

•

Creating a log file of a terminal session

Use the SHOW TERMINAL command to display information about your terminal
and the SET TERMINAL command to change that information. Use the
OPENILOG_FILE and CLOSEILOG_FILE commands to begin and end terminal
logging to a file, and the SET LOG_FILE command to selectively enable and
disable logging within the log file.

5.1

Displaying and Setting Terminal Characteristics
The SHOW TERMINAL command, described in this chapter, produces a display
similar to the following:
$ SHOW TERMINAL <RET>
Terminal: KB56:

Device_Type : VT220

No Broadcast
Break
No Delimiter
Eight_Bit
Interactive
Lowercase
Speed not settable Tab

Control=(R,T,C,X)
No Form
Resume=Control C
TTSync

CRFill=O
Hostsync
Scope
Width=80

Now, suppose you want to change the No Broadcast characteristic (which prevents
messages from other users from appearing on your terminal) to Broadcast (which
allows these messages). You use the following SET TERMINAL command to
change this characteristic:
$ SET TERMINAL/BROADCAST <RET>

This change (replacing "No Broadcast" with "Broadcast") is now shown in the
SHOW TERMINAL display:
$ SHOW TERMINAL <RET>
Terminal: KB56 :

Device_Type: VT220

Broadcast
Break
Eight_Bit
No Delimiter
Interactive
Lowercase
Speed not settable Tab

Control=(R,T,C,X)
No Form
Resume =Control C
TTSync

CRFill =O
Hostsync
Scope
Width=80

Many of these characteristics (such as CRFill=n, Parity, and TTYSYNC) need
to be set only once for the terminal, so you may never need to reset them .
Usually the system manager sets these characteristics when the terminal
is first connected to the system. However, characteristics such as Broadcast

Terminal Status and Operations

5-1

and Width=n depend on your preference for using the tenninal. See the SET
TERMINAL command in this chapter for a description of characteristics you can
set.
There are no true "default" dHlracteri~tics. That i~, if you do not Rpecify a
characteristic, it is either implied by a tenninal type (such as NT100), or it
remains constant when you change other settings. A tenninal characteristic
remains the same unless you either change it or specify a different tenninal
type. The SET TERMINAL command description lists the tenninal types you can
specify.
Although RSTSIE assigns a set of predefined characteristics for each specific
tenninal type, you can reset any of these characteristics. For example, suppose
you type:
$ SET TERMINAL/DEVICE_TYPE=VT240 <RET>

RSTSIE now assumes that your tenninal has a set of characteristics that
correspond to a VT240. You can check these characteristics with the SHOW
TERMINAL command, and change them if you want.

5.1.1

SHOW TERMINAL
The SHOW TERMINAL command displays the current or pennanent characteristics of a tenninal. Each of these characteristics can be changed with a
corresponding option of the SET TERMINAL command. If the tenninal is in use
as a LAT port connected to a tenninal server, then the name of the server, service
and remote port are also displayed.
NOTE

The SHOW TERMINAL command has additional capabilities for users
with greater levels of privilege. See the RSTS / E System Manager's
Guide for more infonnation.

Format
SHOW TERMINAL

[KB[C]n[:]]

Command Qualifiers
fAll
fBRIEF
fFUll
f[NO]OUTPUT[ =filespec]
f[NO]PERMANENT

Defaults
fAll
fBRIEF
fBRIEF
See discussion
fNOPERMANENT

Command Parameters
[KB[C]n[:]]
Specifies the tenninal whose characteristics are to be displayed. Unless you
have additional privilege to specify other tenninals, you can only display the
characteristics of your own terminal.

5-2

Terminal Status and Operations

Command Qualifiers
IAll

Displays the characteristics of aU terminals on the system.
IBRIEF
Specifies a brief display; it is the default. For example:
$ SHOW TERMINAL <RET>
Terminal: KB46:
Device Type: VT220
LAT Server/Port: JTSVAX/TWA7 Break
Broadcast
No Delimiter
Eight_Bit
Interactive
Lowercase
Speed not settable Tab

LAT Interactive Port
Control=(R,T,C,X)
No Form
Resume=Control C
TTSync

CRFill=O
Hostsync
Scope
Width=BO

IFUll
Specifies a display showing additional characteristics. For example:
$ SHOW TERMINAL/FULL <RET>
Terminal: KB46:
Device Type: VT220
LAT Server/Port: JTSVAX/TWA7 132 Columns
Advanced Video
No Answerback
No Autobaud
Buffer_Quota=16B Control=(R,T,C,X)
No Dialup
Eight Bit
Hostsync
Inter~ctive
No Loadable Characters
No Operator
Overstrike
Recall
Regis
Scope
Select Erase
Tab
TTSync
Width=BO

LAT Interactive Port

No Alt Mode
ANSI
Break
Broadcast
CRFill=O
No Delimiter
Escape_Sequence No Form
No Katakana
Line_editing
No Local Echo
Lowercase
No Parity
No Printer Port
Restricted
Resume=Control C
Sixel
Speed not settable
Up_Arrow
User_Defined_Keys

IOUTPUT[ =fi lespec]
INOOUTPUT

Writes the information to the specified file. If you specify INOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.
IPERMANENT
INOPERMANENT

Specifies whether the display shows the permanent characteristics set for your
terminal by the system manager. The default is INOPERMANENT, showing the
characteristics you have set for the current terminal session. When you logout,
RSTSIE resets your terminal to the permanent characteristics.

Terminal Status and Operations

5-3

5.1.2

SET TERMINAL
The SET TERMINAL command lets you specify the characteristics of your
terminal.
NOTE

The SET TERMINAL command has additional capabilities for users
with greater levels of privilege. See the RSTS / E System Manager's
Guide for more information.

Format
SET TERMINAL

[KB[C]n[:]]

Command Qualifiers
/[NO]132_COLUMNS
/[NOjADVANCED_VIDEO
/[NO]ALT_MODE
/[NO]ANSI
/[NO]BREAK
/[NO]BROADCAST
I[NO]CONTROL=[( option[,option, ... ])]
I[NO]CRFILL[=n]
/[NO]DELIMfTER[ =c]
/DEVICE_TYPE=terminal type
/[NO]EIGHT_BIT
/[NO]ESCAPE_SEQUENCE
I[NO]FORM_FEED
IHARDCOPY
/SCOPE
/[NO]HOSTSYNC
IINQUIRE
/INSERT
/OVERSTRIKE
/[NO]KATAKANA
/[NO]UNE_EDITING
/[NO]LOADABLE_CHARACTERS
/[NO]LOCAL_ECHO
/LOWERCASE[=INPUT IOUTPUT]
/[NO]PARiTY[ =option]
/[NO]PRINTER_PORT
/[NO]RECALL
/[NO]REGIS
/RESET
/RESUME=[ANY ICONTROL_C]
/[NO]SELECT_ERASE
/SETUP=filespec
I[NO]SIXEL
/SPEED=(input[,output)]
/[NO]TAB
/[NO]TTSYNC

5-4

Terminal Status and Operations

Defaults
none
none
none
none
none
none
none
/NOCRFILL
none
See discussion
none
none
none
See discussion
none
none
none
/OVERSTRIKE
/OVERSTRIKE
none
none
none
none
See discussion
none
none
none
none
See discussion
none
none
none
none
none
none
none

fTYPE=n
/[NO]UP_ARROW
/UPPERCASE[=INPUT I OUTPUT]
/[NO]USER_DEFINED_KEYS
/WIDTH=n

none
none
See discussion
none
none

Command Parameters
[KBn[:]]

Specifies the terminal whose characteristics are to be set. Unless you have
sufficient privilege to specify other terminals, you can only set the characteristics
of your own terminaL

Command Qualifiers
1132_COLUMNS
IN0132_COLUMNS

Specifies whether the terminal can display single-width characters in an array of
24 lines by 132 columns.
I ADVANCED_VIDEO
INOADVANCED_VIDEO
Specifies whether the terminal supports the Advanced Video Option (AVO), which
includes additional character attributes, screen memory, and ROM sockets.
IALT_MODE
/NOALT_MODE

Specifies whether the system treats ASCII 027, 125, and 126 as ESCAPE. If you
specify /NOALT_MODE, the system treats only ASCII 027 code as ESCAPE.
IANSI
/NOANSI

Specifies whether the terminal supports ANSI escape sequences. ANSI is
required for Command Line Editing.
IBREAK
INOBREAK

Specifies whether the system translates the BREAK key as a CTRLlC character
(Binary 3). If you specify /NOBREAK, the system translates the BREAK key as a
NULL character (Binary 0).
/BROADCAST
INOBROADCAST

Specifies whether the terminal receives system broadcast messages.
ICONTROL=[(option[,option, ... ])]
INOCONTROL=[(option[,option, ... ])]

Specifies the following:
/CONTROL=R Indicates CtrllR will redisplay the command line.
/NOCONTROL=R Means that CtrllR is interpreted as data.
/CONTROL=T Indicates that CtrllT will give a one line staus report.
/NOCONTROL=T Means that CtrllT is interpreted as data.

Terminal Status and Operations

5-5

/CONTROL=C means that CtrllCs are trapped and handled.
/NOCONTROL=C means that CtrllC is interpreted as data.
/CONTROL=X means that CtrllX clears the type-ahead buffer.
INOCONTROL=X means that CtrllX is interpreted as data
To set more than one of these options on a single command line, you can combine

them in a list. For example:
SET TERMINAL/CONTROL=(R,T,C)

/CRFILL[=n]
/NOCRFILL

Specifies the carriage return fill factor, where n is between 0 and 6. The default
is INOCRFILL, meaning that no fill characters are generated.
IDELIMITER[=c]
INODELIMITER

Specifies a private delimiter. If the argument is a character within quotation
marks (for example, /DELIMITER= ".<tab>"), that character becomes the private
delimiter.
If the argument is a number (for example, /DELIMITER=9), the private delimiter

becomes the character whose binary value matches that number. Thus, any
ASCII character whose binary value is between 1 and 127 can be a private
delimiter.
The /NODE LIMITER qualifier cancels any private delimiter previously set with
/DELIMITER.
IDEVICE_TYPE=terminal type

Sets the default characteristics for the specified terminal type. The following
terminal types can be specified with this qualifier:
LA12

LA75

LA324

VT52

VTI05

VT240

LA34

LAI00

LN03

VT55

VT125

VT241

LA36

LA120

LQP02

VT100

VT131

VT320

LA38

LA180S

LQP03

VTI0l

VT132

VT330

LA50

LA210

VKI00

VTI02

VT220

VT340

NOTE

You can specify the following terminal types without explicitly using
the /DEVICE_TYPE qualifier: LA34, LA36, LA38, LA120, VT52, or
VT100.
l EIGHT_BIT
INOEIGHT_BIT

Specifies whether the terminal supports eight bit characters.
IESCAPE_SEQUENCE
INOESCAPE_SEQUENCE

Specifies whether the system treats an ESC character (value 27) as an indication
of an incoming escape sequence. The system does not echo either the ESC
character or the characters in the sequence.
If you specify /NOESCAPE_SEQUENCE, the system treats the ESC character as
a line terminator and echoes it as a dollar sign ($) character.

5-6

Terminal Status and Operations

IFORM_FEED
INOFORM_FEED

Specifies whether the hardware fonn feed and vertical tab control are enabled.
The system transmits fonn feed and vertical tab characters without translation.
If you specify /NOFORM_FEED, the hardware fonn feed and vertical tab control

are disabled. The system transmits four line feed characters in place of a fonn
feed or vertical tab character.
IHARDCOPY
ISCOPE

Specifies whether the tenninal is a hardcopy or a CRT display device. If you
specify !HARDCOPY, then /NOTTSYNC is set by default.
If you specify ISCOPE, then /TTSYNC is set by default.
IHOSTSYNC
INOHOSTSYNC

Specifies whether the tenninal has special hardware that lets the computer
interrupt character transmission by sending an XOFF character (Value 19) to the
tenninal. The computer instructs the tenninal to resume character transmission
by sending an XON character (Value 17) to the tenninal. /HOST_SYNC conflicts
with IRESUME=ANY.
IINQUIRE

Interrogates the tenninal by sending an ANSI ESCAPE identifying sequence
to detennine the tenninal type. The system then sets the appropriate tenninal
characteristics.
If the terminal does not respond within five seconds, the system searches the
default file $TERDFL.SYS for the tenninal's default characteristics. If an entry

is found, the system sets the specified characteristics; if no entry is found, the
system displays an error message.
This qualifier causes the terminal's type-ahead buffer to be cleared.
You should only use the !INQUIRE qualifier on Digital tenninals. (However,
Digital does not support it on LA36 tenninals.)
IINSERT
IOVERSTRIKE

Allows you to insert characters (INSERT mode) when editing a command line or
type over the current character (OVERSTRIKE mode). This mode becomes the
default whenever a new command is entered. See Chapter 1 for more infonnation
on command line editing.
IKATAKANA
INOKATAKANA

Specifies whether the tenninal supports the Katakana character set.
IUNE_EDITING
INOLlNE_EDITING

Enables or disables line editing capabilities on the tenninal. This qualifier is
valid only at the application level; it is ignored at the DCL level or at other
run-time systems levels. See Chapter 1 for more infonnation on command line
editing.

Terminal Status and Operations

5-7

ILOADABLE_CHARACTERS
INOLOADABLE_CHARACTERS

Specifies whether the terminal supports dynamically redefinable character sets,
allowing the terminal to load fonts that can then be invoked as a character set.
ILOCAL_ECHO
INOLOCAL_ECHO

The /LOCAL_ECHO qualifier specifies that the system does not echo characters
received from the terminal. This qualifier is used only for terminals that have
their own local echo.
If you specify INOLOCAL_ECHO, characters are sent to the system, which echoes
each character received and translates certain characters as to their action. For
example, the CR character echoes as a carriage return and line feed sequence.
ILOWERCASE[=INPUT I OUTPUT]
IUPPERCASE[=INPUT I OUTPUT]

Specifies the following:
/LOWERCASE enables lowercase for input and output.
!UPPERCASE disables lowercase for input and output.
/LOWERCASE=INPUT enables lowercase for input.
/LOWERCASE=OUTPUT enables lowercase for output.
/UPPERCASE=INPUT disables lowercase for input.
IUPPERCASE=OUTPUT disables lowercase for output.
If you specify /LOWERCASE or /LOWERCASE=INPUT, then INOALT_MODE
is set by default. If you specify /UPPERCASE or /uPPERCASE=INPUT, then
IALT_MODE is set by default.

IPARITY[=option]
INOPARITY

Specifies whether EVEN or ODD parity option is set, in which case the system
sends characters to the terminal with the parity bit set for either even or odd
parity, but ignores the parity bit on characters received.
If you specify INOPARITY, the system ignores the parity bit on characters it
receives and treats the parity bit on characters it transmits to the terminal as a
data bit.
IPRINTER_PORT
INOPRiNTER_PORT

Specifies whether the terminal has a printer port.
IRECAll
INORECAlL

Enables or disables command recall capabilities on the terminal.
IREGiS
/NOREGIS

Specifies whether the terminal supports the Remote Graphic Instruction Set
(ReGIS).

5-8

Terminal Status and Operations

IRESET

Resets the tenninal's characteristics, if you have changed them, back to the
pennanent set of characteristics that the system manager originally assigned for
that terminal.
IRESUME=[ANY I CONTROL_C]

Defines XONIXOFF processing. The argument ANY enables typeout and echo
when you type any character after XOFF. The argument CONTROL_C enables typeout and echo only when XON or Ctr]JC are entered after XOFF.
IRESUME=ANY is not valid if the terminal is set /HOST_SYNC.
ISCOPE

Specifies the terminal is a CRT display.
ISELECT_ERASE
INOSELECT_ERASE

Specifies whether the terminal supports the selectively erasable charader
attribute.
ISETUP=filespec

Sends the specified file's data, in binary mode, to the terminal. If you specify
the file name alone, the system assumes the file is in the user's account on the
system disk with a file type of .ESC.
Use this qualifier to initialize a terminal for which special software settings must
be made.
ISIXEL
INOSIXEL

Specifies whether the terminal supports Sixel Graphics, which transfers binary
graphic images between the system and the terminal or the terminal and a
printer.
ISPEED=(inpul[,outpui)]

Specifies the speed at which the terminal sends or receives data or both. If you
specify only one speed, RSTSIE uses that speed for both input and output.
ITAB
INOTAB

Specifies whether hardware tab control is enabled. The system transmits tab
characters without translation.
If you specify INOTAB, hardware tab control is disabled. To move to the next tab
stop, the system transmits the correct number of space characters instead of the
tab character.
ITTSYNC
II\IOTTSYNC

Specifies whether the system responds to the Ctr]JS combination (XOFF) by
interrupting character transmission and to the Ctr]JQ combination (XON) by
resuming character transmission.
If you specify INOTTSYNC, the Ctr]JS and Ctrl/Q combinations have no special
meaning.
ITYPE=n

Sets the value of the terminal's type code, which identifies the terminal type in
the SHOW TERMINAL display. Values 0-127 are reserved for Digital terminals.
Values 128-255 can be used to identify other terminals.

Terminal Status and Operations

5-9

/UP_ARROW
/NOUP _ARROW

Specifies whether the system echoes a control and graphic character combination
as the circumflex (1\) character (Value 94), followed by the proper graphic. For
example, CtrllE prints out as I\E.
If you specify /NOUP_ARROW, the system echoes control and graphic character
combina tions as is.
/UPPERCASE[=INPUT I OUTPUT]

Disables use of lowercase character for terminal INPUT and/or OUTPUT.
/USER_DEFINED _KEYS
/NOUSER_DEFINED_KEYS

Specifies whether the terminal supports User Defined Keys (UDKs), which let you
save a full command string and invoke it with a single key.
/WIDTH=11

Sets the width of the terminal's print line to n, which can be between 1 and 254.

5-10

Terminal Status and Operations

5.2 Creating a Log File of a Terminal Session
This section tel1s you how to create and use a terminal log fil~ t.o save a copy of
the output that appears during a session at your terminal. Mter you open the
log file, all characters that are written to the terminal are saved in the file. Note
that you can use a terminal log file either at the interactive level or within a
command procedure. Whenever a log file is open and terminal logging is in effect,
DCL changes its dollar sign prompt ($) to a dollar sign followed by a period ($.),
as a reminder that logging is in effect.
The characters written to a log file are the same characters output to the
terminal, with the following exceptions:
•

Messages broadcast to the terminal do not appear in the log file.

•

If you enter Ctrl!r at the terminal, neither the AT nor the one line status
display appear in the log file.

•

If you enter CtrllR at the terminal, neither the AR nor the redisplayed line
appear in the log file.

Note that any condition or command that disables terminal output, such as
entering CtrllO at the terminal, also disables output to the log file. In addition,
if you enable a log file during execution of a command procedure, the SET
NOVERIFY command disables output of DCL command lines both to the
terminal and to the log file. The SET NOECHO command disables output of data
and command lines to the terminal only; output continues to be written to the log
file.
The following sections describe the commands that you use to:

5.2.1

•

Open a terminal log file

•

Close a terminal log file

•

Selectively disable and enable output to the log file

OPEN/LOG FILE
The OPENILOG_FILE command opens a disk file for terminal logging. You can
issue the OPENILOG_FILE command either interactively or within a command
procedure.
You can only open one log file at any given time. If a log file is already open when
you attempt to open a second log file, RSTSIE issues an error message and does
not open the second file; instead, the current log file remains open.

Terminal Status and Operations

5-11

Format
OPEN/LOG FILE

file-spec

Command Qualifiers
fAPPEND
fDISABlE
fENABlE
f[NO]REPLACE
f[NO]TIME_STAMP

Defaults
See discussion
fENABlE
fENABlE
See discussion
fNOTIME_STAMP

Prompts
File: file-spec

Command Parameters
file-spec
Specifies the disk file to open for logging terminal output. RSTS/E displays an
error message if you specify a nondisk file, or if the file-spec is invalid. RSTS/E
also displays an error message if a log file is already open. If you do not specify a
file type, RSTSIE assumes a file type of .LOG. Unless you include the fAPPEND
qualifier, RSTS/E opens the file for output, and deletes any existing file of the
same name.

Command Qualifiers
(APPEND
Tells RSTS/E to add data to the end of the file you specify. This qualifier lets you
append terminal output to the end of an existing log file. If the file you specify
does not exist, RSTSIE ignores this qualifier and opens a new file. Note that only
RSTS/E stream ASCII files can be appended: if you specify a file that has RMS
attributes, an error message displays.
(DISABLE

Indicates that terminal output should not be logged to the file until you issue the
SET LOG_FILEIENABLE command to enable terminal logging.
(ENABLE

Indicates that output should be logged to the file. This qualifier is the default
when you issue the OPENILOG_FILE command.
(REPLACE
(NOREPLACE

Specifies whether to replace an existing file with a new file. If the log file that
you specify already exists:
"

The !REPLACE qualifier tens RSTS/E to delete the existing file and create a
new file.

The /NOREPLACE qualifier tens RSTS/E not to replace the file if it exists; in
this case, an error message displays.

If you specify neither qualifier, RSTS/E issues a warning message and asks if you
want to replace the file.
5-12

Terminal Status and Operations

Note that this qualifier conflicts with the /APPEND qualifier.
ITIME_STAMP
INOTIME_STAMP

Indicates whether to prefix each line in the log file with a date/time stamp. The
default is /NOTIME_STAMP. However, if you specify /TIME_STAMP, RSTS/E
prefixes each line in the log file with a date/time stamp specifying the date and
time that the line was copied to the log file. Note that the date and time format
is based on the system defaults that your system manager establishes. The
date/time fields occupy the first 22 characters of each line.
Here is an example using the OPENILOG_FILE command:
$ OPEN/LOG_FILE/TIME_STAMP TERM. LOG <RET>
$•

This command opens the log file TERM.LOG. The TIME_STAMP qualifier
specifies that the date and time is to precede each line written to the log file.
Note that after you open the log file, the prompt indicates that a log file is active.

Terminal Status and Operations

5-13

5.2.2

CLOSE/LOG_FILE
The CLOSEILOG_FILE command closes a log file that you opened with the
OPENILOG_FILE command.

Format
CLOSE/LOG FILE

Use the CLOSEILOG_FILE command to close an open log file either during a
session at your terminal or within a command procedure. The RSTSIE monitor
makes sure that any open log file is closed whenever you log out of the system or
whenever your job is killed.
If logging is enabled when you issue the CLOSEILOG_FILE command, RSTSIE
writes the command itself to the log file, before closing it. If no log file is open
when you issue this command, RSTSIE displays an error message. For example:
! Get a list of files in the directory

$ OPEN/LOG_FILE DIR.LOG
$ .DIRECTORY
Name .Typ
FINISH . COB
START . BAS
TEMP16 . TMP

Size
130
89
258

Prot

< 60>
< 60>
< 60>

Name .Typ
LETTER .MEM
ROAD
. MAP

Size
4
3

Prot

SY: [52,20]

< 60>
< 60>

Total of 484 blocks in 5 files in SY: [52,20]

$ .CLOSE/LOG_FILE

This example:

1. Opens the log file DIR.LOG with the OPENILOG_FILE command.

5-14

Lists the files in your directory, which are also written to the log file.

Closes the log file with the CLOSEILOG_FILE command.

Terminal Status and Operations

5.2.3

SET LOG FILE
Mter you open a log file, you can use the SET LOG_FILE command to selectively
enable and disable logging to the file. You can also use this command to enable or
disable the time stamp feature in the log.

Format
SET LOG FILE
Command Qualifiers

Defaults

IDISABLE
IENABLE
I[NO]TIME_STAMP

none
none
none

Command Qualifiers
IDISABLE
Indicates that terminal or command file output should not be logged to the
current log file. If logging is currently disabled, RSTSIE ignores this qualifier.
This qualifier conflicts with IENABLE.
IENABLE
Indicates that terminal or command file output to the log file should be enabled.
If logging is currently enabled, RSTSIE ignores this qualifier. This qualifier
conflicts with /DISABLE.
I[NO]TIME_STAMP
Enables or disables the time stamp feature, which prefixes each line in the log
file with a date/time stamp in a format that your system manager has defined.

Use the SET LOG_FILE/DISABLE command to temporarily suppress output to
the current log file. Mter you disable logging, RSTSIE displays the $ prompt to
indicate that logging is disabled.
If you issue the SET LOG_FILE/DISABLE command when no log file is open,
RSTSIE displays an error message. If you issue the command when logging is

already disabled, RSTSIE ignores the command. For example:
$ OPEN/LOG_FILE TEMP.LOG <RET>

$ INQUIRE FILE "Enter the name of the file to edit"

$ SET LOG FILE/DISABLE
$ EDIT 'FILE'
$ SET LOG_FILE/ENABLE

$ CLOSE/LOG_FILE
$ EXIT

Terminal Status and Operations

5-15

In this command procedure you:
1.

Open the log file TEMP LOG and write output to the file.

Use the INQUIRE command to prompt for the name of a file to edit.

3. Issue the SET LOG_FILEIDISABLE command to temporarily disable logging
because you do not want to log the editing session.
4.

Use the SET LOG_FILEIENABLE command to reenable logging after the
editing session ends, and continue writing output to the file.

Issue the CLOSEILOG_FILE command to close TEMP.LOG before the
procedure exits.

Use the SET LOG_FILEIENABLE command to reenable output to an open log
file. After you reenable logging, RSTSIE displays the DCL $ prompt followed
by a period ($.), to indicate that logging is in effect. If you issue the SET LOG_
FILEIENABLE command when no log file is open, RSTSIE displays an error
message. If you issue the command when logging is already enabled, RSTSIE
ignores the command.
Note that you can also use this command to enable or disable the time stamp
feature, as well as enabling or disabling output to the current log file. For
example:

!Disable logging temporarily

$. SET LOG_FILE/DISABLE

!Now reenable logging

$ SET LOG_FILE/ENABLE

!Now disable time stamps

$. SET LOG_FILE/NOTIME_STAMP

$. !Now reenable time stamps
$. SET LOG_FILE/TIME_STAMP
$.

In this example, you temporarily disable and reenable logging, and then temporarily disable and reenable time stamps in the log file.

5-16

Terminal Status and Operations

Chapter 6

Working with Devices
All RSTSIE users share the system's peripheral devices, such as line printers and
magnetic tape drives. You can refer to these devices by either physical or logical
device names.
Table 6-1 summarizes the commands you use to work with devices.

6.1

Table 6-1:

Commands for Devices and Logical Names

Command

Meaning

ALLOCATE

Reserves a device so that only you can use it

DEALLOCATE

Releases a device from your exclusive use, so that other
users may access the device

MOUNT

Logically loads a magnetic tape or disk onto a device

INITIALIZE

Clears ("zeros") a tape for use

DISMOUNT

Logically unloads a magnetic tape or disk from a device

SHOW DEVICE

Displays devices that are in use on your system

SHOW DEVICE/ALLOCATED

Displays status of allocated and open devices

SHOW DISKS

Displays status of all mounted disks

ASSIGN

Assigns a logical name to a directory or a physical device

DEASSIGN

Cancels logical name assignments you made with the
ASSIGN command

Working with Physical Devices
Each of the devices on a RSTSIE system has its own device name. A physical
device name is also called a device designator or device specification (because you
use it to specify a device).
The system assigns physical device names to peripheral devices, such as:
•

Line printers (LP:)

•

Terminals (KB: or TT:, for "keyboard")

•

Magnetic tape drives (MM:, MT:, or MS:, depending on the kind of tape drive)

•

Disk drives (such as DB:, DM:, or DR:, depending on the kind of disk)

Note that a physical device name consists of two letters, optionally followed by a
unit number, and always ended with a colon (:). The alphabetic characters are
generally an abbreviation of the device's generic name. The unit number uniquely
identifies the device itself or the drive on which it is mounted.
Working with Devices

6-1

You can use physical device names in all operations that let you specify a
device. For example, you can display the characteristics of a specific terminal by
including a physical device name, such as KB2:
$

SHOW TERMINAL KB2: <RET>

Similarly, you can determine which disk or magnetic tape you want to use in file
transfer operations. For instance, assume you have a tape mounted on a tape
drive named MT2:. To copy file RACE.ME in your directory to the tape on drive
MT2:, type:
$

COPY RACE .ME MT2: <RET>

Another example of a physical device name is SY:, which refers to the public
disk structure. You can therefore use SY: to refer to the public disk structure,
regardless of the drive on which a disk is located. Such an assignment is useful
if, for example, the drive on which the disk is usually mounted is put offline
for maintenance, and the system disk is temporarily mounted on another drive.
Then, in order to reference accounts on the system disk, you do not need to adapt
your commands or programs to fit hardware changes.
If you do not specify a physical device name, the system assumes the public
structure (SY:). For non-file-structured devices (for example, a line printer)
you only need to specify the physical device name; the system ignores any
specified file name, type, or directory.

Physical device names are also often used in logical name assignments (discussed
later in this chapter). The following example assigns the logical name MARCH to
DB2:, which is a disk drive:
$ ASSIGN DB2: MARCH <RET>

Table 6-2 lists the RSTSIE physical device names.
Table 6-2:

RSTS/E Physical Device Names

Designator

Device

DK:, DL:, DM:, DP:, DR:,
DB:, DU:, or SY:

RSTSIE public disk structure

SYO:

System disk

DKO: to DK7:

RK05 disk units 0 through 7

DLO: to DL3:

RLOlJRL02 disk units 0 through 3

DMO: to DM7:

RK06IRK07 disk units 0 through 7

DPO: to DP7:

RP02IRP03 disk units 0 through 7

DRO: to DR7:

RM02IRM03IRM05IRM80 disk units 0 through 7

DBO: to DB7:

RP04IRP05/RP06 disk units 0 through 7

DUO: to DUI5:

RA901RA821RA811RA801RA701RA60/RC251RD541RD531RD521

RD511RX50!RX33 units 0 through 15
CR:

CRll punched or CMll mark sense card reader

CD:

CDll punched card reader

MTO: to MT7:

TEI0lfUI0lfS03 magnetic tape units 0 through 7

MMO: toMM7:

TE16lfU16lfU45ITU77 magnetic tape units 0 through 7

MSO: to MS3:

TSI11TU80ITSV05 magnetic tape units 0 through 3

(continued on next page)

6-2

Working with Devices

Table 6-2 (Cont.):

RSTS/E Physical Device Names

Designator

Device

MUO:to MUl:

TK50!fU81trU81E: magnetic tape units 0 or 1

LPO: to LP7:

Line printer units 0 through 7

DTO: to DT7:

TU56 DECtape units 0 through 7

KB:

Your terminal

KBn:

Terminal n on the system

KBAnn:

Terminal on subline nn of a DLll A,B type single line
interface

KBBnn:

Terminal on subline nn of a DLll C,D type single line
interface

KBCnn:

Terminal on subline nn of a DLllE type single line modem
interface

KBDnn:

Terminal on sub line nn of a pseudo keyboard

KBFnn:

Terminal on subline nn of a DR multiplexer

KGBnn:

Terminal on subline nn of a DZlDZVIDZQ multiplexer

KBRnn:

Terminal on subline nn of a DVHlDHU multiplexer

KBlnn:

Terminal is a LAT terminal

TT: or TI:

Your terminal (synonyms for KB:, the terminal that initiated
the job)

TTn:

Terminal n on the system (synonym for KBn:)

NL:

The null device

PKn:

Pseudo keyboard n

DXO: to DX7: or
DYO: to DY7:

RXOl/RX02 flexible diskette (floppy disk) units 0 through 7

NOTE

You can reference LPn:, DTn:, DXn:, KBn:, MMn:, MTn:, and MSn:
where n is between 0 and the maximum number of such units on
the system. LP:, DT:, DX:, MM:, MT:, and MS: are each the same as
specifying unit 0 of the related device.
If your system has only TSll, TU80, or TSV05 tape units, the

designators MS: and MT: are the same. If your system has only TE16,
TU16, TU45, or TU77 tape units, the designators MM: and MT: are the
same.
If you do not specify a unit number, the defaults are:

Disk - Public structure
Keyboard - Yours
All other device - Unit 0
Use the SHOW DEVICE command, described later in this chapter, for a list of
devices in use on your system. If you specify a device or type of device that is
not part of your system's configuration, the system displays the following error
message:
?Not a valid device

An underscore C) before a name suppresses any interpretation of the name as a
logical name. For example, if you assign the logical name MTO: to a disk, you
specify _MTO: when you want to refer to magnetic tape unit O.
Working with Devices 6-3

6.1.1

Allocating Devices
Sometimes you may need to allocate (reserve), a device for your exclusive use.
Only one job at a time can use an allocated device.
You can only allocate devices that are not already in use. For example, if another
user is already using a tape drive, you cannot immediately allocate it to yourself.
If you attempt to do so, the system displays the following error message:
?Device not available

6.1.2

Assigning and Allocating Devices
The ALLOCATE command allocates a device to you. ALLOCATE can also assign
a logical name for the device you are using.
Use the ALLOCATE command to assign logical names and allocate devices for
your use. Use the ASSIGN command to assign logical names only. In either case,
you get an error message if you try to exceed the number of logical names you
can assign.
The DEALLOCATE command releases a device from your exclusive use, but only
the DEASSIGN command cancels the logical name assignment.

6.1.3

Device Independence
Device independence is a central idea in RSTSIE. This means that you can use
a file on one device much as you can use a file on any other device. This idea
applies both to the system user and to the programmer.
As much as possible, the system tries to hide the differences between devices
from both the system user and the programmer. For example, you can read data
that is on a tape just as you read data that is on a disk.
However, different devices offer different capabilities. RSTSIE cannot entirely
hide these differences. The following sections discuss some of the differences
among devices.

6.2 Working with Disks
A disk is either public or private, as determined by your system manager. Any
user who has an account on the system can create files on a public disk. If a disk
is private, you cannot place files there unless your system manager (or a user
with sufficient privileges) creates an account for you on that disk.
Every RSTSIE installation has at least one public disk (and sometimes more),
called the system disk. For most purposes, the public disks on a given system are
treated as a unit. This unit is called the public disk structure, and has the device
name SY: (which stands for system).
When you create a file and do not specify what device to create it on, or when you
specify SY:, the system creates the file on one of the public disks. (The system
also decides which public disk to create it on if there is more than one public
disk.) When you specify an existing file and do not specify a device (or when you
specify SY:), the system searches each of the public disks for the file.

6-4

Working with Devices

You cannot have two files of the same name and type on two different public
disks, just as you cannot have two files of the same name and type on a single
disk. If you try to give a file the same specification as an existing file, one of the
following two things can happen (depending on the command):
•

You get the following error message:
?Name or account now exists

•

6.2.1

The existing file is replaced

The Public Disk Structure
Users share computing time on the RSTSIE system. Each user is allocated a
"slice" of the processor's time. Users may share another system resource as
well: the array of devices. One set of devices (disks) is shared by a number of
users. This shared set of devices is called the public disk structure, because it is
always accessible to all users and because the system treats it as a unit. On some
systems, it may include many separate disk packs. One of these, the system disk,
contains the system code, language processors, and, possibly, the library of system
programs. The other disk packs (the public disks) contain information created by
the users. (The system disk also may contain user programs and data, which are
stored in files.)
When you are logged in to the system and working with a disk file, you are
usually not concerned about which disk in the public structure happens to
contain your file. The particular disk is chosen by the system according to
current time-sharing needs. Each of the disks contains a master list of users'
accounts, and, for each account, a list of all files stored under that account. By
using these lists, the system is able to locate your file when you request it from
your terminal.

6.2.2

Private Disks
A good deal of system file activity, such as creation, access, editing, and deletion,
takes place on the public disk structure. Because it is the largest constantly
available medium of file storage, it is generally the busiest. However, not all the
disks on the system need be in the public structure. Some of them may be private
disks, which belong to a single user account or perhaps to a few user accounts.
(These accounts alone are on the disk.)
An important difference between a private disk and one on the public structure
is that you can always create a file on the public structure, whereas you can
do so on a private disk only if you have a directory there. On both types of
disks, file protection codes govern your read and write access to existing files.
Another difference is that a private disk can be mounted or dismounted at any
time, whereas a public disk must remain mounted during timesharing. This
difference is of special concern to the owner(s) of the private disk and to your
system manager, who determines which disks on the system are public and which
are private.

Working with Devices 6-5

6.3 Working with Magnetic Tapes
Magnetic tape is a compact, relatively inexpensive medium that can provide large
amounts of offline storage. One reel of magnetic tape can store many files.
Unlike disks, magnetic tape allows only sequential access to :files.
To copy files from a tape, you should:
1. Allocate the drive. (This step is optional, but it provides security.)
2.
3.

Physically mount the tape.
Issue the MOUNT command. (This step is optional, if the tape has default

density and format.) The MOUNT command also allocates the drive, if you
did not allocate it already.

6.3.1

Copy files from the tape using the COPY command. (With the COpy
command, you can copy a file that requires multiple tapes. User programs
can access tape files if they are stored on only one tape, but system programs
can access files stored on more than one tape.)

Issue the DISMOUNT command. (This step is optional, but it deaUocates the
drive and rewinds the tape.)

Physically dismount the tape.

Protecting Files on Tapes
Protection of files on tapes works differently from protection of files on disks.
While you are using a tape, the device is allocated to your job. While the device
is allocated to you, you have complete control over the tape. You can read any
file on it. No other user can access the tape while it is allocated to your job. The
MOUNT command and the ALLOCATE command both allocate the tape device
to your job. The DISMOUNT, DEALLOCATE, and LOGOUT commands free the
tape device so that other jobs can allocate it.

6.3.2

Tape Density
When you initialize a tape on a device, you decide what the tape's density will be.
The two considerations are:
..

The amount of information to be stored on the tape

The degree of portability (interchangeability) between systems

For example, assume you have a choice of specifying a density of 800 or 1600 bits
per inch (bpi). You can get roughly twice as much information on a tape with a
density of 1600 bpi; however, not all tape drives support 1600 bpi.

6.3.3

ANSI and DOS Format
RSTSIE has two file structures for tapes:
..
@

6-6

ANSI format, because it complies with the standards of the American
National Standards Institute
DOS format, because RSTS/E adopted it from the Disk Operating System
format.

Working with Devices

The ANSI format is an industry standard. The advantages to using ANSI format
tapes are:
..

Portability - If you expect to move the contents of a tape from one system to
another, it is very possible that the other systems will recognize ANSI format.

Multiple tapes - The files you copy can be stored on more than one reel of
tape.
NOTE

Where ANSI is used in RSTSIE documentation, it refers to the RSTSIE
implementation of American National Standard X3.27-1978, magnetic
tape labels and file structure for information exchange. RSTSIE
implements a subset of this standard.
In addition, RSTSIE uses U (undefined) record format, which is not
defined in ANSI standard X3.27-1978.
The advantages of using DOS tape are:
..

Files are associated with PPNs.

•

Files are better for storing binary files that have no attributes, such as .OBJ
(object) or .BAC (compiled BASIC-PLUS) files.

When you initialize a tape with the INITIALIZE command, you can select either
ANSI or DOS format. Later, when you mount the tape, you must again tell
the system whether the tape is in ANSI or DOS format. If you do not specify a
format, the system uses the default determined by your system manager.
There are three ways to ten if a tape containing data is written in DOS or ANSI
format:
..

Look for a label on the tape. The person who put data on the tape may have
placed a label on the tape and written DOS or ANSI on it.

Try mounting the tape as either DOS or ANSI. When you mount a tape on
a drive, RSTSIE checks the format. If you entered the right format, you can
continue with tape operations. If you entered the incorrect format, RSTSIE
displays the following error message:
?Bad directory for device

You can try again using the other format.
e

Use the MOUNT command, and don't specify a format.

If the tape is in ANSI format, then files on the tape do not have PPNs. They have
only names and types.
If the tape is in DOS format, then each file on the tape has a PPN. The PPN of a
tape is like the directory on a disk file. For example, a DOS format tape on drive
MTO: might contain a file whose specification is:
MTO: [1,2]SLOW.RUN

Another file on the tape might have the specification:
MTO: [3,49]GOOD.RUN

Working with Devices

6-7

6.4 Physical Device Commands
This section contains descriptions of some commands you use when working with
physical devices. See the RSTS / E System Manager's Guide for commands and
functions that require additional privileges to use.

6.4.1

ALLOCATE
The ALLOCATE command reserves a physical device for your use during the
current session and optionally establishes a logical name for the device. Once
a device has been allocated, other users cannot access the device until you
specifically deallocate it or logout. You can allocate a device only when it is not
allocated by another job.

Format
ALLOCATE

device-name[:]

Command Qualifiers
/[NO]QUEUED

[Iogical-name[:]]
Defaults
See discussion

Prompts
Device: device-name

Command Parameters
device-name[ :]
A logical or physical name.
logical-name[:]
Specifies a one- to fifteen-character logical name to be associated with the device.
RSTSIE automatically translates any references you make to the logical name
to a physical device associated with the name. The logical name parameter is
optional.

Command Qualifiers
/QUEUED
/[NO]QUEUED
The ALLOCATEI[NO]QUEUED command temporarily sets the queueing characteristic of the local LAT port you are allocating. This setting remains in effect
until you deallocate the device. This qualifier is only valid if the device being
allocated is a local LAT port.
If IQUEUED is specified, connections initiated by this local LAT port to a terminal

server are placed on the server's queue if the server supports queueing and the
remote port is currently busy. If INOQUEUED is specified, connections are not
queued and fail if the remote port is busy.

6-8

Working with Devices

Use the SHOW PORT command to display the port's connection status. If the
port is set IQUEUED, and the server is busy, a connection status of "In Progress"
and the position in the queue are shown.
If this qualifier is not specined, the queued setting that was specified when the
port was created or assigned is used during the time that you have it allocated.

Working with Devices

6-9

6.4.2

DEALLOCATE
The DEALLOCATE command releases a device that you reserved for private use,
so that other users may have access to it. (However, note that DEALLOCATE
does not deassign any logical name you may have assigned to the device; for that
you need the DEASSIGN command.)

Format
DEALLOCATE

[device-name[:]]

Command Qualifiers
fAll

Defaults
none

Prompts
Device: device-name[:]

Command Parameters
device-name[ :]
Specifies the name of the device to be deallocated. The device name can be a
physical device name or a logical name. The device name parameter is required
unless you specify the fALL qualifier.

Command Qualifiers
fAll
Requests that all devices you have currently allocated be deallocated.
If you specify fALL, you cannot specify a device name.

6-10

Working with Devices

6.4.3

MOUNT
The MOUNT command prepares a tape or disk for processing by system commands or user programs. Issue the MOUNT command after you physically mount
the tape or disk and put the drive on line.
NOTE

The MOUNT command has additional capabilities for users with
greater levels of privilege. See the RSTS / E System Manager's Guide
for more information.
If the MOUNT command fails with the following error message, but
you do not have sufficient privileges, have your system manager mount
the disk:
?Disk pack needs REBUILDing

Format
For disks:

MOUNT device-name[:] pack-id [logical-name}}
For magnetic tapes:

MOUNT device-name[:] {[/abe!]}
Command Qualifiers
/[NO]WRITE

Defaults
See discussion

Command Qualifiers for Disks
/PRIVATE
/[NO]SHAREABLE

Defaults
/PRIVATE
/SHAREABlE

Command Qualifiers for Tapes
/DENSITY=n
/FORMAT =ANSI
/FORMAT =DOS
/FORMAT =FOREIGN

Defaults
See discussion
none
none
none

Prompts
Device: device-name[:]
Label: label (for ANSI tapes only)
Pack-id: pack-id (for disks only)

Depending on whether you are mounting a tape or disk, the MOUNT command:
..

Specifies a tape's density and format

Checks that a tape or disk's device specification is correct

Checks that a tape or disk has been initialized

Verifies that a tape or disk drive has not been allocated to another user

Working with Devices

6-11

•

Allocates a tape drive (reserves it for your use)

•

Verifies that a disk or tape is physically loaded on the device you specified

•

Verifies that the pack-id on a disk or the label on a tape (except for DOS tape)
matches the label you specified

•

Allows you to mount a private pack for your own use

Command Parameters
device-name[:]
Specifies the physical or logical name of the drive on which a device is to be
logically mounted.
pack-id
log ical-name
label
Identifies the tape or disk to be mounted. The pack-id or label can have from one
to six alphanumeric characters. The logical-name can be up to 15 characters.

The label is required when you mount a disk or a tape in ANSI format. It is not
required (and is ignored) when you mount a tape in DOS or foreign format.

Command Qualifiers
IWRITE
INOWRITE
Controls whether or not you can write data to a tape or disk. The !WRITE
qualifier allows you to modify the data contained on a tape or disk. If you specify
INOWRITE, you cannot modify the data.
You can specify INOWRITE to provide read-only access to protect files. For a
disk, this is equivalent to write-protecting it. For a tape, the drive itself must be
write-protected; INOWRITE simply generates an error message if the device is
not write-protected.
When the device is not write-protected, /WRITE is the default for tapes. When
the disk drive is not write-protected, !WRITE is also the default for disks
(initialized as read/write). However, INOWRITE is the default if the drive is
write-protected. Therefore, if you receive the warning message %Device write
protected, you have logically mounted your disk or tape with read-only access.
The default is also INOWRITE for disks initialized as read-only.

IPRIVATE
Allows you to mount a private disk, accessible only to those users who have
accounts on the disk. (Your system manager designates whether disks are public
or private.)
ISHAREABLE
INOSHAREABLE
Determines whether the private disk you use is shared. The INOSHAREABLE
qualifier allows you to mount a private disk that is accessible only to the job that
mounts it. The /SHAREABLE qualifier allows all users who have accounts on
the disk to access it. The /PRIVATE and /SHAREABLE qualifiers have the same
meaning. If you specify INOSHAREABLE, you cannot specify /PRIVATE.
The default is /SHAREABLE.

6-12

Working with Devices

IOEN5ITY=n

Specifies the density in bits per inch (bpi) at which the tape will be read or
written. This qualifier is valid only with tapes. You can specify 800, 1600, 6250,
6667,8000, or 10000 bpi, depending on the density supported by the tape drive.
The default density depends on your installation.
IFORMAT=AN51
IFORMAT=005
IFORMAT=FOREIGN

Indicates whether the tape is in a standard fonnat used by the RSTSIE operating
system. This qualifier is valid only with tapes. A tape is FOREIGN if it is not
in ANSI or DOS fonnat. If you mount a tape with IFORMAT=FOREIGN, the
program you use to read the tape must be able to process any labels on the tape.

Working with Devices 6-13

6.4.4

INITIALIZE
The INITIALIZE command deletes any data on a tape and writes a new label.
INITIALIZE allocates the tape drive if it is not already allocated.
Use INITIALIZE to prepare a new tape or a tape that contains no useful files.
Use MOUNT to prepare an already initialized tape that contains files you want
to keep.
NOTE

See the RSTS / E System Manager's Guide for information on using
INITIALIZE with disks.

Format
INITIALIZE

device-name[:] [label]
Defaults
See discussion
See discussion
See discussion

Command Qualifiers
IDENSITY=n
IFORMAT=ANSI
IFORMAT=DOS
Prompts
Device: device-name[:]
Label: label
Proceed (Y or N):

NOTE

The label prompt appears only for a tape in ANSI format or if
IFORMAT=ANSI is specified. The proceed prompt asks you to confirm
whether you want to initialize the tape. Type yes or no (Y or N) in
response to the prompt.

Command Parameters
device-name[:]
Specifies the name of the drive on which the tape is physically mounted.
label
Specifies the identification to be encoded on the tape. You can specify a maximum
of six alphanumeric characters. For an ANSI-format tape, the label is required.
For a DOS-format tape, the label is ignored, because DOS tapes do not have
labels.

6-14

Working with Devices

Command Qualifiers
IDENSITY=n

Specifies the density in bpi at which to write the tape. You can specify a density
of either 800, 1600, 6250, 6667, 8000, or 10000 bpi if the tape drive supports it.
If you do not specify a density, the system uses the default specified by your

system manager.
IFORMAT=ANSI
IFORMAT=DOS

Specifies the tape format. If you do not specify a format, DeL uses the default
determined by your system manager.

Working with Devices

6-15

6.4.5

DISMOUNT
The DISMOUNT command releases a disk or tape previously accessed with a
MOUNT command. Use the DISMOUNT command before you take the drive off
line, or before you physically dismount the tape or disk.
NOTE

The DISMOUNT command has additional capabilities for users with
greater levels of privilege. See the RSTS / E System Manager's Guide
for more information.
The DISMOUNT command deallocates the device if it was allocated to you. You
cannot DISMOUNT a device if there are open files on it. If you try, RSTS/E
displays the error message:
?Account or device in use

Format
DISMOUNT

device-name[:] [label]

Command Qualifiers for Tapes
/[NO]UNLOAD

Defaults
/UNLOAD

Prompts
Device: device-name[:]
Pack-id: pack-id label

Command Parameters
device-name[:]
Specifies the name of the device to be dismounted. If you omit a unit number, the
default depends on the type of device.
label
Specifies the identification label of the device. Unless you have additional
privilege, you must specify a disk's pack-id label to dismount it. For tapes, the
label is optional (and is ignored).

Command Qualifiers
/UNLOAD
I[NO]UNLOAD

Rewinds and unloads the tape. This protects the tape against unauthorized
access by other users. The default is /UNLOAD.

6-16

Working with Devices

6.4.6

SHOW DEVICE, SHOW DEVICE/ALLOCATED, SHOW DISKS
There are three SHOW commands that display information about physical devices
on the system. They are:
•

SHOW DEVICE [deY:] - Displays all devices on the system, or a specified
device

•

SHOW DEVICE/ALLOCATED - Displays the status of all allocated and
open devices

•

SHOW DISKS - Displays the status of all mounted disks

Examples of each command, and their displays, follow:
$ SHOW DEVICE KB32: <RET>
Device KB32:
(KBG3:)
Control DZO:3

CSR 760140

Status: Restricted

$ SHOW DEVICE/ALLOCATED <RET>

Busy Devices:
Device
Job
PKO
10
DMR-O
TRN
DMC-1
TRN
DMP-O.O
TRN

Why
Open
AS+Open
AS+Open
AS+Open

$ SHOW DISKS <RET>

Disk Structure:
Size
Dsk Open
DB3
0 340664
DB4
2 340664
DU1
47 400168

Free
Clu
15288
4%
8
21920
6%
8
41864 10%
8

Level
Err Name
0 DBL8
1.1
2 S
1.2
o GROKSY 1.2

Comments
Pri, R-O, DLW, DP
Pri, DLW
Pub, DLW

See the RSTS / E System Manager's Guide for more information on each column
type in the previous three examples.
Table 6-3 contains the abbreviations included in the SHOW DEVICE/ALLOCATED
and SHOW DISKS displays.
Table 6-3:

Abbreviations in SHOW DEVICE/ALLOCATED and SHOW DISKS
Displays

Abbreviation

Meaning

Description

SHOW DEVICE/ALLOCATED Command
AS

Assigned

OPEN

Open

Device is open on a channel.

DOS

Magnetic tape is assigned with DOS (Disk
Operating System) format.

ANSI

Magnetic tape is assigned with ANSI
(American National Standards Institute)
format.

TRN

Network Services

The monitor is using the device for DEC net
communications.

Device is explicitly allocated to a job.

(continued on next page)

Working with Devices

6-17

Table 6-3 (Cont.):
Abbreviation

Abbreviations in SHOW DEVICE/ALLOCATED and SHOW
DISKS Displays
Meaning
Description
SHOW DISKS Command

Pub

Public

Disk is public.

Pri

Private

Disk is private.

NFS

Non-file- structured

Disk is open as a non-file-structured device.

R-O

Read-only

Disk unit is read-only (write-protected).

DLW

Date of Last Write

Date oflast write (modify), rather than
date oflast access, is stored in file accounting entries.

Dual-Ported

The disk can be accessed by two different
RSTSIE systems at the same time. The
disk must be read-only.

Lck

Locked

Disk is in a locked state.

NFF

New Files First

New files on the disk are put at the beginning of the directory.

Job n

Private disk is allocated to job n (reported
with PRI and NFS).

Dirty

Disk needs rebuilding (reported with PRI,
LCK, and R-O).

6.5 Logical Names
Logical names let you keep programs and command files independent of the
physical locations of those files. They also provide a convenient shorthand way to
specify devices and directories that you refer to frequently.
You can assign a logical name to a physical device name or to a directory. The
logical names that you assign are valid for your job only. For example, only your
job can reference the logical name that you assign to a device. No other job can
reference that logical name.

6.5.1

Logical Names and Devices
You can use logical device names to describe the nature of information on a disk,
magnetic tape, or other medium. The logical name may be easier to remember
than the physical name with its device number. You can choose a logical name
without regard to what device types may be available at some future time.
The logical names that you assign for devices do not depend on the physical
device specifications. Unlike a physical name, a logical name is independent of
the drive on which the medium is mounted. Logical device names make it easier
to adapt a program for use on different drives. Thus, if you write a program
referencing physical devices, you can give these devices logical names of your own
choosing by issuing the ASSIGN command. This action associates your chosen
names with the devices and makes the program independent of the devices'
physical locations on the system.

6-18

Working with Devices

6.5.2

Systemwide and User Logicals
When you assign logical names, you are the only one who can use them. Your
logical name assignments are deleted when you logout. The logical names that
you assign are called user logical names, to distinguish them from systemwide
logicals.
Systemwide logicals are logical names that everyone on the system can use.
Certain systemwide logicals are standard for most RSTS/E systems; others are
assigned for your site by the system manager. See the RSTS / E System Manager's
Guide for more information on systemwide logicals.

6.5.3

Numbers of Logical Names
The maximum number of logical name assignments that a job can have is not a
fixed limit. RSTS/E supports 100 - 170 logicals per job with logical names of up to
15 characters each. A job can have approximately 100 long logicals (greater than
six characters) or 170 short logicals (six characters or less) or a mixture of both.
You can assign more than one logical name to a device. For example, you could
assign to the tape on drive MMO: the logical names RACE1, RACE2, and RACE3,
and use any of these three names as your application requires.

6.5.4

How to Override Name Precedence
Sometimes you may have a logical name that conflicts with a physical name.
The system always recognizes and accepts a device's physical name, whether
or not a logical name has been assigned to that device. Thus, you can specify
a magnetic tape running on drive MT2 and assigned the logical name STAR as
either MT2: or as STAR:.
If you put an underscore before a physical name, the system will not try to
interpret it as a logical name (for example, _MT2:). A physical device name
preceded by an underscore causes the system to access that device, regardless of
any prior assignment.

RSTS/E evaluates the parts of a file specification in the following sequence. When
a file specification contains a name followed by a colon, RSTS/E first determines
whether or not the name is a user logical. If it is, then the system replaces the
name with its expansion. (An expansion is the device name or PPN to which
the logical name was assigned.) Otherwise, it checks to see if the name is a
systemwide logical.
If the name is not a systemwide logical, RSTS/E then determines whether the
name designates a valid physical device on your RSTS/E system. (During system
generation, your system manager selects which devices are valid on your system.)
Finally, if the device name is not a physical device name, the system displays the
error message:
?Not a valid device

Working with Devices

6-19

6.5.5

ASSIGN
The ASSIGN command assigns a logical name to a directory or a physical device.
The names you assign stay in effect until you logout, or until you deassign the
name with the DEASSIGN command.
NOTE

The ASSIGN command has additional capabilities for users with
greater levels of privilege. See the RSTS / E System Manager's Guide
for more information.

Format
ASSIGN

device-name:[[ppn]] logical-name[:]

Command Qualifiers
IUSER
I[NO]REPLACE[=QUERy]

Defaults
IUSER
IREPLACE

Prompts
Device: devnam:[[ppnJ]
Logical name: logical-name

When you use the ASSIGN command, one of the following can occur:
•

The command works as expected, and no message is displayed.

•

The assignment statement is incorrect, and one of the following error
messages displays:
?Not a valid device
?No file name or type permitted

•

You exceed the maximum number of logical name assignments you can make,
and the following error message displays:
?Too many logical names assigned

•

You reassigned a logical name and the following informational message
displays:
Previous logical name assignment replaced

Command Parameters
devnam :[[ppn]]
Specifies the name of the device or PPN to be assigned a logical name. Brackets
around the PPN are required, as in the following example:
$ ASSIGN MT1: [2,214] KENDRA_DIRECTORY:

logical-name[:]
Specifies a one- to fifteen-character logical name to associate with the device.

6-20 Working with Devices

The ASSIGN command equates a logical name to a part of a physical file
specification. The following example equates the logical name EXCER_DISK: to
the directory DB2:[3,24]:
$ ASSIGN DB2: [3,24] EXCER_DISK:

The string "DB2:[3,24]" is called the "expansion" of the logical name
EXCER_DISK.
Later, you can refer to the directory by its logical name when you issue a RSTS/E
command. For example:
$ DIRECTORY EXCER_DISK:

When the system executes this DIRECTORY command, it replaces the logical
name EXCER_DISK: with its expansion, DB2:[3,24], and lists all of the files in
that directory on your terminal.
Another example is:
$ TYPE EXCER:RUNNER.DAT

When the system executes this command, it replaces the logical name .
EXCER_DISK: with its expansion and displays the contents of the file
DB2:[3,24]RUNNER.DAT on your terminal.
You can equate a logical name to a physical device name, to a directory, or to
both. For example:
$ ASS I GN DB2: EXCER DISK
$ ASS I GN [3,24 ] EXCER_DISK :
$ ASS I GN DB2: [3,24 ] EXCER_ DI SK:

! (DB2 : is a physical device)
! ([3,24] is a directory)

! ([3,24]

is a directory on DB2:)

When you assign a logical name, the partial file specification that you assign to
the logical name may itself include a previously assigned logical name. When the
system executes the ASSIGN command, it replaces the previously assigned logical
name with its expansion and displays an informational message. Therefore, if
you later change the assignment of the first logical name, the expansion of the
second logical name is not affected. For example, consider the following sequence
of commands:
$
$
$
$

ASSIGN DB2: WORK:
ASSIGN WORK: [3,24] EXCER DISK:
DEASSIGN WORK:
TYPE EXCER DISK:RUNNER.DAT

In this example, the logical name EXCER_DISK: corresponds to DB2 :[3,24] . The
TYPE command displays DB2:[3,24]RUNNER.DAT even though the logical name
WORK: has been deassigned.

Command Qualifiers
/USER

The /uSER qualifier indicates a user logical assignment. This qualifier is
provided primarily for completeness; if you do not specify !USER or ISYSTEM,
then the command assigns a user logical, as it did previously. You can include the
/uSER qualifier in DCL command procedures to explicitly state the type of logical
assignment you are making.

Working with Devices

6-21

IREPLACE[=QUERY]
I[NO]REPLACE[=QUERY]

The I[NO]REPLACE[=QUERY] qualifier specifies what action to take if the logical
name specified is already assigned. !REPLACE replaces the existing assignment
with the new assignment. /NOREPLACE returns an error message if the logical
name is already assigned. !REPLACE=QUERY prompts you to proceed with the
assignment if the logical name is already in use. The default is !REPLACE.

6-22

Working with Devices

6.5.6

DEASSIGN
The DEASSIGN command cancels logical name assignments you made with the
ASSIGN command.
NOTE

The DEASSIGN command has additional capabilities for users with
greater levels of privilege. See the RSTS / E System Manager's Guide
for more information.

Format
DEASSIGN

[Iogical-name[:]

Command Qualifiers
IAll
IUSER

Defaults
none
See discussion

Prompts
logical Name: logical-name[:]

Command Parameters
logical-name[:]
Specifies a one- to fifteen-character logical name to deassign.
A logical name is required unless you specify fALL . If you do not specify either
fALL or a logical name, the system prompts you for a logical name. For example:
$ DEASSIGN <RET>
Logical Name: EXCER_DISK <RET>

Command Qualifiers
IAll
Deletes all logical names that you assigned. For example:
$ DEASSIGN/ALL <RET>

IUSER
The /uSER qualifier is provided primarily for completeness; if you do not specify
/uSER or fSYSTEM, then the command deassigns a user logical, as it did
previously. You can include the /uSER qualifier in DeL command procedures to
explicitly state the type of logical deassignment you are making.

Working with Devices

6-23

Chapter 7

Print/Batch Services
Whenever you use the PRINT command to print files or use the SUBMIT
command to execute command procedures for batch processing, you are
automatically using the RSTSIE PrintlBatch Services (PBS) facility. This chapter
describes the commands you use to:
@

Place entries on a print or batch queue for printing or batch processing

Check the status of your print or batch job on a queue

Modify your print or batch entry before it is printed or processed

•

Delete a print or batch entry from a queue

Your system manager usually sets up default print and batch queues for your
system, so that you only need to use the simple commands this chapter describes
to print files or submit command procedures for batch processing. If you are
interested in, or need to know, more detailed information about how PBS
performs its print and batch processing functions, see the complete description of
PBS organization and operations in the RSTS / E System Manager's Guide.
Table 7-1 summarizes the PBS commands that this chapter describes.
Table 7-1:

7.1

Print/Satch Services Commands

Command

Meaning

Produces a listing, or "hard copy," of a file.

SUBMIT

Submits a command file for batch processing.

SHOW ENTRY

Displays the names of files that are currently being printed or
processed, as well as files pending on the print or batch queue.

SET ENTRY

Modifies one or more attributes of a file that is entered on a print
or batch queue.

DELETEIENTRY

Cancels an entry on the print or batch queue.

SHOW QUEUE

Displays the status of a print or batch queue.

Specifying Print and Batch Entries
The PRINT and SUBMIT commands instruct PBS to enter files on a print or
batch queue, respectively. A PBS queue controls how print and batch system
resources are allocated.

Print/Batch Services

7-1

Once a file is queued for printing or batch processing, it becomes an "entry." You
may need to access your print or batch entry often. For example, you may want
to modify the entry or delete it, or you may want to display the entry's status
in the queue so you can see whether it has started or finished printing or batch
processing. PBS provides two methods of identifying and accessing entries in a
queue:

7.1.1

•

Entry number

•

Entry specification

Entry Number
PBS assigns a unique entry-number to each queued print or batch entry. This
number shows the order in which the entry was placed in the print or batch
queue. Since it is unique, you can use the entry-number to identify and access
your entry if you want to modify, delete, or display it.
For example, here is an entry on a print queue, as displayed by the SHOW
ENTRY command:
Entry

Pos

Type

Qu eue

3686

1st

Batch

BASELEVEL

Owne r
1, 170]

Name

s tatus

Pri

BLDMGR

STARTED

255

This display tells you that the entry-number is 3686, which you can then use to
identify the entry while it is in the queue.

7.1.2

Entry Specification
Besides the entry-number, you can also access an entry in a queue by specifying
the following attributes:
•

The name of the queue on which the entry is located

•

The entry's owner (PPN)

•

The entry name

PBS permanently establishes these attributes when it creates the entry; you
cannot modify them once the entry is placed in the queue. The format of an
entry-spec is:
queue-name:[PPN]entry-name
Thus, you would type the entry-spec for the entry shown in the previous example
as follows:
PRINT: [1,214]MAIL

Unlike entry-numbers, entry-specs do not uniquely identify an entry. For
instance, in the above example, you (as user [1,214]) could have several entries
named MAIL on the print queue named PRINT:. You should therefore be very
careful when using entry-specs to access an entry to modify or delete it; you
might inadvertently modify or delete other entries having the same entry-spec.

7-2

Print/Batch Services

7.2 Printing Files: PRINT
The PRINT command queues one or more files for printing, either on the default
print queue or on a queue you specify.

Format
PRINT

[NODE::Jfile-spec[, ...J [entry-specJ

Command Qualifiers
IAFTER=date-time
IFORMS=form-name
IHOLD
IJOB_COUNT=n
INAME=entry-name
I[NO]NOTIFY
IOWNER=[p,pn]
IPAGE_LlMIT=n
IPAGE_LlMIT=UNLIMITED
IPRIORITY=n
IQUEUE=queue-name[:]

Defaults
none
See discussion
none
IJOB_COUNT=1
See discussion
INONOTIFY
See discussion
See discussion
See discussion
See discussion
See discussion

File Qualifiers
I[NO]CONVERT
ICOPIES=n
I[NO]DELETE
I[NO]FEED
I[NO] FLAG_PAGES
I[NO]TRUNCATE
I[NO]WRAP

Defaults
INOCONVERT
ICOPIES=1
INODELETE
IFEED
IF LAG_PAGES
INOTRUNCATE
/WRAP

Prompts
File: file-spec[, ... ]

Command Parameters
file-spec[, ... ]

Specifies one or more files to be printed. If you specify more than one file,
separate the file specifications with commas (,) or plus signs (+). In either case,
the PRINT command prints all the files as a single print job. You can use
wildcard characters for the file name, file type, and directory.
If you do not specify a file type, the PRINT command uses the default file type
.LST. If you do not specify a device, the PRINT command uses SY:.

You can also specify a node name as part of the file specification. If you specify a
file on a remote node, PBS temporarily copies the file into your account, prints it,
and then deletes it. Note that you cannot use any qualifiers if you specify a node
name.

Print/Batch Services

7-3

entry-spec
The entry-spec specifies the queue and the name of the entry in the fonnat queuename:[PPN]entry-name. The entry-name can contain from one to nine characters.
If you do not specify a queue, PBS submits the entry on the default print queue.
If you do not specify an entry-name, PBS assigns the first non-numeric file name
in the list of specified file-specs, or PRINT if none is found. Your own PPN is the
default.

Command Qualifiers
I AFTER=date-time
Requests that the file not be printed until a specific time of day or date. See
Chapter 2 for a description of the standard syntax rules for specifying date and
time values .

For example, to have a file named TIBET.MEM start printing after 5:30#PM on
September 11 (after nonnal working hours when there are fewer requests for
listings), specify the date and time as:
$ PRINT/AFTER=11-SEP:05:30PM TIBET.MEM

If the specified date or time has already passed, the file is queued for printing as
soon as possible.
IFORMS=form-name
Specifies the name of the fonn required for the specified file(s). You specify the
fonns type with an alphanumeric name defined by the system manager. Check
with the system manager to learn which fonn names you can specify.
IHOLD
Specifies that the entry be placed in a HOLD state on the queue. Entries
in a HOLD state are not processed until you release them with the SET
ENTRYIRELEASE command.
IJOB_COUNT=n
Requests that the entire job be printed n times, from 1 to 255. By default, the job
is printed once.

The following example prints four copies of a file named AFGHAN.TXT:
$ PRINT/JOB_COUNT=4 AFGHAN.TXT

/JOB_COUNT differs from the ICOPIES qualifier in the order in which multiple
files are printed. For example, if you request three copies of files INDIA.TXT and
MARCH.FIL, the IJOB_COUNT qualifier prints one copy of INDIA.TXT, followed
by one copy of MARCH.FIL, and repeats the grouping until three copies of each
file are printed:
$ PRINT/JOB_COUNT=3 INDIA.TXT,MARCH.FIL

INAME=entry-name
Specifies the 1 through 9 character name assigned to the entry. You can display
the entry-name with the SHOW ENTRY command. In addition, PBS prints the
entry-name on the first page (also known as the flag, or banner, page) of the hard
copy.
INOTIFY
INONOTIFY
Specifies whether your tenninal session is notified of events that occur related to
your print entry. The default is INONOTIFY.

7-4

PrinVBatch Services

IOWNER=[p,pn]

Indicates the owner of the print job. PBS displays the project-programmer
number on the job header page. You can only specify jobs with your own PPN
(the default), unless you have sufficient privilege to specify others.
IPAGE_LlMIT =n
IPAGE_LlMIT =UNLIMITED

Specifies the maximum number of pages to be printed in the job. You can specify
only up to the maximum page limit assigned to the queue by the system manager.
You can specify IPAGE_LIMIT=UNLIMITED only if the queue's maximum page
limit is also set to UNLIMITED.
IPRIORITY=n

Specifies the priority of the print job, in the range 1 through 255 . The PRINT
command processes entries in priority order: higher-priority entries before
lower-priority entries.
You cannot specify a priority higher than the maximum priority assigned to the
queue by the system manager.
IQUEUE=queue-name[:]

Specifies the name of the queue on which the entry is placed. The queue you
specify must be a print queue.
If you do not specify a queue-name in the entry-spec or if you do not specify
IQUEUE, PBS places the entry on the default print queue.

Use the SHOW ENTRY command to verify an entry's position in the queue.

File Qualifiers
ICONVERT
INOCONVERT

Specifies whether all zeros should be converted to the letter 0 before printing.
The default is INOCONVERT.
ICOPIES=n

Specifies the number of copies to print. By default, the PRINT command prints
one copy of a file; you can use ICOPIES to request up to 255 copies. For example,
the following command line requests three copies of file INDIA.TXT:
$ PRINT/COPIES=3 INDIA. TXT

If you specify ICOPIES after the PRINT command name, each file is printed

the number of times you specify. For example, to print three copies each of
BOMBAY.TXT and LAHORE.MEM, type:
$ PRINT/COPIES=3 BOMBAY.TXT, LAHORE.MEM

If you specify ICOPIES after a file specification, PBS prints only that file the

specified number of times. The following command line requests two copies
of NEPAL.DAT, one copy of SIKKIM.DAT (by default), and five copies of
BHUTAN.DAT:
$ PRINT NEPAL.DAT/COPIES=2,SIKKIM.DAT,BHUTAN.DAT/COPIES=5

The ICOPIES qualifier differs from IJOB_COUNT in the order in which multiple
files are printed. For example, if you request three copies of files TEXAS.DAT and
MARCH.FIL, PBS prints three copies of TEXAS.DAT, followed by three copies of
MARCH.FIL.
$ PRINT/COPIES=3 TEDFOR.BOB,MOODY.JON

Print/Batch Services

7-5

IDELETE
INODELETE
Controls whether files are deleted after printing. INODELETE is the default.
If you specifY /DELETE after the PRINT command name, all files specified are

deleted after printing. For example:
$

PRINT/DELETE OUTPUT.DAT,RESULT.TXT

Both OUTPUT.DAT and RESULT.TXT are deleted after printing.
If you specifY /DELETE after a file-spec, only that file is deleted after printing.
For example:
$

PRINT CONCRD.MAS, LOWELL.MAS/DELETE, BOXBRO.MAS

Only the file LOWELL.MAS is deleted after printing.
You must have write access to the file to delete it after printing,

IFEED
INOFEED
Specifies whether the printer should leave six blank lines at the end of each page.
The default is !FEED .
IFLAG_PAGES
INOFLAG_PAGES
Specifies whether flag (file header) pages should be printed at the beginning of
each file listing. If you specify !FLAG_PAGES, the number of flag pages printed
is determined by the system manager, and may vary according to the form you
specify with the !FORMS qualifier.
ITRUNCATE
INOTRUNCATE
Indicates whether lines that exceed the width of the page should be truncated.
The system manager determines the page width; it may vary according to the
form you specify with the !FORMS qualifier.
The default is INOTRUNCATE, which means that lines exceeding the form width
continue, or "wrap," onto the next line.

IWRAP
INOWRAP
Indicates whether or not the characters that exceed the form width should print
on the same line. The default is !WRAP.

7-6

Print/Batch Services

7.3 Submitting Entries for Batch Processing: SUBMIT
The SUBMIT command enters a request for batch processing, either on the
default batch queue or on a queue you specify.
When you use the SUBMIT command, you specify one or more command
procedures to be executed by the batch server. See the RSTS / E Guide to Writing
Command Procedures for detailed information about writing and executing
command procedures.

Format
SUBMIT

file-spec[, ...] [entry-spec]

Command Qualifiers
/AFTER=date:time
/CPU_LlMIT=n
/CPU_LlMIT =UNLIMITED
/HOLD
/[NO] LOG_DELETE
/[NO]LOG_FILE=file-spec
/[NO] LOG_QUEUE=queue-name
/NAME=entry-name
/[NO]NOTIFY
/OWNER=ppn
/PARAM ETERS=(parameter[, ... ])
/PRIORITY=n
/QUEUE=queue-name
!TIME_LIMIT=n
!TIME_LIMIT=UNLIMITED

Defaults
See discussion
See discussion
See discussion
none
/NOLOG_DELETE
See discussion
/NOLOG_QUEUE
none
/NONOTIFY
See discussion
none
none
none
See discussion
See discussion

File Qualifiers
/[NO]DELETE

Defaults
/NODELETE

Prompts
File: file-spec[, ... ]

Command Parameters
file-spec

Specifies one or more command files (procedures) to be submitted for batch job
execution. You must specify a file name. If you do not specify a file type, PBS
assumes a default file type of .COM, and if you do not specify a device, PBS
assumes the default device _SY:. Wildcards are allowed.
You can only submit files to which you have read access. For each file-spec in
the SUBMIT command, PBS attempts to find at least one file to which you have
read access; if it finds none, PBS displays an error message and refuses the batch
request. If you specify the !DELETE qualifier with a file-spec, you must have
both read and write access.
Print/Batch Services

7-7

entry-spec
The entry-spec specifies the queue and the name of the entry in the format queuename:[PPN]entry-name. The entry-name can contain from one to nine characters.
If you do not specify a queue, PBS submits the entry on the default. batch queue.
If you do not specify an entry-name, PBS assigns the first non-numeric file name
in the list of file-specs, or BATCH if none is found. Your own PPN is the default.

Command Qualifiers
f AFTER=date:time

Specifies a date:time value after which the entry is eligible for batch processing.
If you do not specify this qualifier, PBS assumes the entry is immediately eligible.
If you specify only a time value, PBS assumes today's date. If you specifY only a

date value, PBS assumes the end of the day (11:59 p.m.).
fCPU_UMIT:n
fCPU_UMIT =UNUMITED
Specifies the maximum CPU time, in minutes, allowed for your batch job. This
limit applies to the entire batch job, not to each command procedure within the
job. You can only specify the maximum CPU limit of the batch request's queue.
If you specify ICPU_LIMIT=UNLIMITED, the batch request's queue must

also have its maximum CPU limit set to UNLIMITED. A batch request with
CPU_LIMIT=UNLIMITED is allowed an infinite amount of CPU usage during
processing.
If you do not specify this qualifier, PBS assigns the batch queue's default CPU

limit.
fHOlD
Specifies that the entry be placed in a HOLD state on the queue. Entries
in a HOLD state are not processed until you release them with the SET
ENTRY/RELEASE command.
flOG_DELETE
fNOlOG DELETE
Specifies whether the log file should be deleted after printing. The default is
/NOLOG_DELETE.
flOG_FilE [=file-spec]
fNOlOG_FILE
Specifies whether a log file is created for the batch job and if so, the file-spec of
the log. By default, PBS creates a log file at the start of a batch job.
If you do not specify a file-spec, PBS creates the log file in your own account on

the default device SY:, using the first six characters of the entry name and a file
type of .LOG. (Any file with the same name will be replaced.)
If you specify a file-spec, PBS creates that file at the start of the batch job,
replacing any file having the same name.
flOG_QUEUE [=queue-name]
fNOlOG_QUEUE
Specifies whether a log file should be queued for printing when the batch job
completes and if so, the queue on which it should be printed. The default is
/NOLOG_QUEUE.
If you do not specify a queue name, PBS queues the log file on the default print

queue.

7-8

Print/Batch Services

INAME=entry-name

Specifies the one- to nine-character name assigned to the entry.
INOTIFY
INONOTIFY

Specifies whether or not your terminal session is notified of events that occur
related to your batch entry. The default is INONOTIFY.
IOWNER=ppn

Indicates the owner of the batch job. You can only specify your own PPN, unless
you have sufficient privilege to specify others.
IPARAMETERS=(parameter[, ... ])

Specifies from one to eight optional parameters to be passed to the batch job.
PBS assigns the parameters to the local symbols PI through P8 when it executes
the first command procedure in the job.
IPRIORITY=n

Specifies the priority of the batch request, in the range I to 255. PBS processes
entries with higher priorities before those with lower priorities. You cannot
specify a priority higher than the queue's maximum.
IQUEUE=queue-name[:]

Specifies the name of the queue on which the entry is placed. The queue specified
must be a batch queue.
Use the SHOW ENTRY command to verify an entry's position in the queue.
ITIME_L1MIT=n
ITIME_L1MIT=UNLIMITED

Specifies the maximum elapsed time, in minutes, allowed for the requested batch
job. This limit applies to the entire batch job, not to each command procedure
within the job. You can only specify the maximum time limit of the batch
request's queue.
If you specify ITIME_LIMIT=UNLIMITED, the batch request's queue must

also have its maximum time limit set to UNLIMITED. A batch request with
TIME_LIMIT=UNLIMITED is not limited to any amount of elapsed time during
processing.
If you do not specify this qualifier, PBS assigns the batch queue's default time

limit.

File Qualifiers
IDELETE
INODELETE

Specifies whether the command file should be deleted after batch processing
completes. You must have write access to the file for which you specify /DELETE.
The default is INODELETE.
You may type the /DELETE qualifier after any file name to delete only that file,
or you may type the /DELETE qualifier immediately after the SUBMIT command
to delete all files included in the command.

Print/Batch Services

7-9

7.4 Displaying Print and Batch Queue Entries: SHOW ENTRY
The SHOW ENTRY command displays information about entries in the print
or batch queue. This display shows each entry's current status as well as its
characteristics, such as queue-name, entry-name, entry-number, owner, and
priority.

Format
SHOW ENTRY

[entry-spec or entry-number]

Command Qualifiers
fAll
fBATCH
fBRIEF
fFllES
fFUll
f[NO]OUTPUT[=filespec]
fPRINT
fSTATUS[=(keyword[, ... ])

Defaults
See discussion
See discussion
fBRIEF
fBRIEF
fBRIEF
See discussion
none
none

Command Parameters
entry-spec
entry-number
Specifies the entry-spec or entry-number of the entry you want to display. Use the
entry-number when you want to display a single entry. Use the full entry-spec
(queue:[ppn]name) to display all entries meeting the specification.

You can specify wildcard characters anywhere in the entry-spec. If you do not
specify any entry parameter, the SHOW ENTRY command displays all print and
batch entries owned by you.
NOTE

By default, PBS does not display entries by queue. To see a list of the
entries in a particular queue, specify the queue-name in the entry-spec.

Command Qualifiers
fAll
Specifies that all entries are to be displayed. Using the fALL qualifier is the same
as specifying the entry-spec *:[*,*]*, although you may include other qualifiers to
restrict the entries selected.

If you do not specify fALL, the entry-spec defaults to entries with your PPN.
/BATCH

Specifies that only batch queue entries be displayed. This qualifier conflicts with
!PRINT.
The default is that both print and batch queue entries are displayed.

7-10

Print/Batch Services

IBRIEF
Requests a brief listing of information about entries in the queue. It is the
default. For example:
$ SHOW ENTRY/BRIEF <RET>

Entry

Pos

Type

Queue

3686

1st

Batch

BASELEVEL

Owner
1,170]

Name

Status

Pri

BLDMGR

STARTED

255

The /BRIEF qualifier displays the following information about each entry:
•

Entry number

•

Position - the entry's start position relative to other entries

•

Entry type - Print or Batch

•

Queue name

•

Owner's PPN

•

Entry name

•

Entry status - one of the following:
READY - The entry is ready for processing.
AFTER - The entry is waiting for an IAFTER date and time to be met
before it can start processing.
HOLD - The entry is waiting for a SET ENTRYIRELEASE command in
order to start processing.
STARTED - The entry has started processing. (Use the /FULL qualifier
to display the date and time that the entry started.)
ABORTING - The entry is in the process of being terminated.

•

Priority in the queue

IFILES
Displays all file-specs, and their qualifiers, included in the entry. Unless you have
additional privilege, you can only see the file-specs contained in your own entries.
IFULL
Displays the full status of each entry. In addition to all the information shown by
the /BRIEF and /FILES qualifiers, the /FULL qualifier also displays the following:
•

Priority

•

JOB_COUNT (number of copies to be printed)

•

Date and time the entry was submitted

•

Date and time the entry was last modified (if ever)

•

Date and time the entry started processing

•

AFTER date and time (specified by the IAFTER qualifier)

•

Server name (if the job is STARTED)

Print/Batch Services

7-11

For example:
$ SHOW ENTRY/FULL <RET>
Status

Pri

1st Batch BASELEVEL
1,170] BLDMGR
STARTED
Entered 19-Jun-90 08:23 AM
Started 19-Jun-90 11:25 AM on batch server BA9:
CPU limit UNLIMITED, Time limit UNLIMITED
Log file _SY: [1, 170]BLDMGR.LOG, No log queue
No parameters
1> _DU13:[170,59]BLDMGR.COM

255

Entry
3686

Pos

Type

Queue

Owner

Name

IOUTPUT[=filespec]
INOOUTPUT
Writes the information to the specified file . If you specify INOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.
IPRINT
Displays only entries on print queues.
ISTATUS[=(keyword[, ... ])]
Displays all of the entries in PRINT or BATCH queues with the specified status
that are currently being processes or waiting to be processed.

The /STATUS qualifier accepts one or more status keyword arguments. If you
specify multiple status keywords, then SHOW ENTRY displays those entries with
any of the specified status.
For example, the command:
$ SHOW ENTRY/ALL/STATUS=FORMS WAIT

displays all (print) entries that are waiting for a forms change. The command:
$ SHOW ENTRY/ALL/STATUS=(HOLD,AFTER)

displays entries that are on hold or waiting for their after date/time to expire.
See Table 7-2 for a list of the /STATUS keywords and their meaning:
Table 7-2:

ISTATUS Keywords

Keyword

Meaning

AFTER

Displays entries with the status AFTER, indicating they are waiting
for their specified after date/time to elapse.

ABORTING

Displays entries with the status ABORTING, indicating they have
started but are in the process of being terminated.
Displays (print) entries with the status FORMS_WAIT, indicating
they are waiting for their required form to be installed on an
assigned print server.

HOLD

Displays entries with the status HOLD, indicating they cannot start until they are taken off HOLD status via the SET
ENTRYIRELEASE command.

READY

Displays entries with the status READY, indicating they are waiting
for a Print or Batch server to become available for processing.

(continued on next page)

7-12

Print/Batch Services

Table 7-2 (Cont.):

ISTATUS Keywords

Keyword

Meaning

STARTED

Displays entries with the status STARTED, indicating they are
currently being processed by a Print or Batch server.

NOTE

For compatibility with VMS, RSTSIE also supports the VMS SHOW
ENTRY qualifier /BY_JOB_STATUS and most of its keyword arguments. See Table 7-3 for the RSTSIE keywords and their VMS
synonyms:
Table 7-3:

VMS IBY_JOB_STATUS Synonyms

RSTSIE Syntax

VMS Synonym.

$ SHOW ENTRY/STATUS

$ SHOW ENTRYIBY JOB STATUS

=ABORTING

none

=AFTER
=FORMS_WAIT

none

=HOLD

=HOLDING

=READY

=PENDING

=STARTED

=EXECUTING

PrinVBatch Services

7-13

7.5 Modifying a Print or Batch Queue Entry: SET ENTRY
The SET ENTRY command modifies one or more attributes of an entry. You also
use SET ENTRY to hold or release an entry for processing.

Format
SET ENTRY

entry-spec or entry-number

Command Qualifiers
I[NO]AFTER=date:time
IAll
IBATCH
ICPU_UMIT=n
ICPU_UMIT=UNUMITED
IFORMS=form-name
IHOlD
IJOB_COUNT=n
IPAGE_LlMIT=n
IPAGE LIMIT =UNUMITED
IPRINT
IPRIORITY=n
IRElEASE
!TiME_LIMIT=n
!TIME_LIMIT=UNLIMITED

Defaults
none
See discussion
none
none
none
See discussion
none
none
none
none
See discussion
none
none
none
none

Prompts
Entry: entry-spec or entry-number

Command Parameters
entry-spec
entry-number
Specifies either the entry-spec or entry-number of the print or batch entry to be
modified. If you specify the entry-spec, PBS modifies aU entries matching the
specification. If you specify the entry-number, PBS modifies only the entry with
the matching number. Wildcards are allowed.

Command Qualifiers
I AFTER:date:time
INOAFTER
Specifies a date:time value after which the entry is eligible for printing or batch
processing.
If you specify only a time value, PBS assumes today's date. If you specify only a

date value, PBS assumes the end of the day (11:59 p.m.).

7-14

Print/Batch Services

For example, you type the following command line to have a job named BOCAT
printed after March 2 at 1:00 in the afternoon:
$ SET ENTRY BOCAT/AFTER=02-JUN-90:01:00PM

The INOAFTER qualifier releases an entry (previously set with the IAFTER
qualifier) for immediate processing.
IAll

Specifies that all of your entries are to be modified. Using the IALL qualifier is
the same as specifying the entry-spec *:[*,*]*, although you may include other
qualifiers to restrict the entries selected.
IBATCH

Specifies that only batch queue entries be modified.
By default, both print and batch queue entries are selected to be changed.
ICPU_LlMIT=n
ICPU_LlMIT =UNLIMITED

(Batch entries only.) Specifies the maximum CPU time, in minutes, allowed for
the batch job. This limit applies to the entire batch job, not to each command
procedure within the job.
If you specify ICPU_LIMIT=UNLIMITED, the batch request's queue must
also have its maximum CPU limit set to UNLIMITED. A batch request with
CPU_LIMIT=UNLIMITED is allowed an infinite amount of CPU usage during
processing.
IFORMS=form-name

(Print entries only.) Specifies the name of the form required by the entry. See
your system manager to find out which form names you can specify.
IHOlD

Specifies that the entry be placed in a HOLD state on the print or batch queue.
PBS does not process entries in a HOLD state until you release them with the
SET ENTRYIRELEASE command.
IJOB_COUNT=n

(Print entries only.) Specifies that the entire job be printed n times, from 1 to
255.
IPAGE_LlMIT =n
IPAGE_LlMIT =UNLIMITED

(Print entries only.) Specifies the maximum number of pages to be printed in the
job. You can specify only up to the maximum page limit assigned to the queue by
the system manager, unless you have sufficient privilege to specify a higher limit.
You can specify IPAGE_LIMIT=UNLIMITED only if the queue's maximum page
limit is also set to UNLIMITED.
IPRINT

Specifies that only print queue entries be modified .
The default is that both print and batch queue entries are selected to be changed.
IPRIORITY=n

Specifies the priority of the print or batch request, in the range 1 to 255. PBS
processes entries with higher priorities before those with lower priorities. You
cannot specify a priority higher than the queue's maximum.

Print/Batch Services

7-15

IRE LEASE

Specifies that an entry previously placed in a HOLD state be released.
ITIME_LlMIT=n
ITIME_LlMIT=UNLIMITED

(Batch entries only.) Specifies the maximum elapsed time, in minutes, allowed
for the requested batch job. This limit applies to the entire batch job, not to each
command procedure within the job.
If you specify ITIME_LIMIT=VNLIMITED, the batch request's queue must
also have its maximum time limit set to UNLIMITED. A batch request with
TIME_LIMIT=UNLIMITED is not limited to any amount of elapsed time during
processing.

7-16

Print/Batch Services

7.6 Deleting a Print or Batch Entry from a Queue: DELETE/ENTRY
The DELETEIENTRY command uses the name or number of an entry to cancel a
request to the print or batch queue.

Format
DELETE/ENTRY

entry-spec or entry-number

Command Qualifiers

Defaults

fAll
fBATCH
fPRINT

none
See discussion
See discussion

Prompts
Entry: entry-spec or entry-number

Command Parameters
entry-spec

entry-number
Specifies either the entry-spec or entry-number of the print or batch entry to
be deleted. If you specify the entry-spec, PBS deletes all entries matching the
specification. If you specify the entry-number, PBS deletes only the entry with
the matching number. Wildcards are allowed.
NOTE

Be careful when you delete jobs using the entry-spec parameter. More
than one entry with the same entry-spec may exist.

Command Qualifiers
/All
Specifies that all of your entries are to be deleted. Using the fALL qualifier is
the same as specifying the entry-spec *:[*,*]*, although you may include other
qualifiers to restrict the entries selected.
/BATCH

Specifies that only batch queue entries be deleted.
The default is that both print and batch queue entries are selected.
/PRINT

Specifies that only print queue entries be deleted.
The default is that both print and batch queue entries are selected.

Print/Batch Services

7-17

7.7 Displa.ying a Queue's Characteristics: SHOW QUEUE
The SHOW QUEUE command displays the status of one OT mOTe print OT batch
queues. The display includes infonnation about the queue's characteristics, such
as default fonn name, size limits, and the servers assigned to the queue.

Format
SHOW QUEUE

queue-name[:]

Command Qualifiers
fAll
fBATCH
IBRiEF
IFULL
f[NO]OUTPUT[=filespecj
fPRINT

Defaults
none
See discussion
IBRIEF
IBRIEF
none
See discussion

Prompts
Queue: queue-name[:]

Command Parameters
queue-name [:1
Specifies the name of the queue to be displayed. Wildcards are allowed.

Command Qualifiers
fAll
Specifies that aU queues be displayed.

fBATCH
Specifies that only batch queues be displayed.

The default is to display all queues matching the queue-name parameter,
regardless of type.
fBRIEF
Specifies a brief display (the default), which includes the fan owing infonnation
about the specified queue:

Queue type - Print or Batch

Queue name

Queue status - one or more of the following:
DEFAULT - Queue is the default queue.
OPEN - Queue can accept requests.
CLOSED - Queue v'Iill not accept requests.
STARTED - Entries on the queue can be started.

7-18

Print/Batch Services

STOPPED - Entries on the queue cannot be started.
MARKED FOR DELETION - Queue will be deleted as soon as it
becomes empty.
IFULL

Specifies a full display, which includes all the information in the brief (default)
display, along with the following additional information:
•

Default form name (Print queues only) - The name assigned to the default
paper form in the printer.

•

Default/maximum priority - The default priority assigned to entries in the
queue and the maximum priority that can be specified for entries.

•

Default/maximum page limit (Print queues only) - The default page limit
assigned to entries in the queue and the maximum page limit that can be
specified for entries.

•

Default/maximum CPU limit (Batch queues only) - The default CPU limit
assigned to entries in the queue and the maximum CPU limit that can be
specified for entries.

•

Default/maximum time limit (Batch queues only) - The default time limit
assigned to entries in the queue and the maximum time limit that can be
specified for entries.

•

Assigned servers - The list of print and batch servers currently assigned to
the queue.

IOUTPUT[=fi lespec]
INOOUTPUT

Writes the information to the specified file. If you specify /NOOUTPUT, the
information is suppressed and not displayed. If the optional filespec argument is
omitted, the output displays on the terminal.
IPRINT

Specifies that only print queues be displayed.
The default is to display all queues matching the queue-name parameter,
regardless of type.

Print/Batch Services 7-19

Chapter 8

Program Development
This chapter describes DCL commands for developing, linking, and running
programs on RSTSIE.
NOTE

This manual does not explain programming concepts. To use this
chapter, you need to know how to write programs in the language you
select. See the appropriate programming manuals for information
about using each language.
Table 8-1 describes the commands you use to develop programs on RSTSIE.
Table 8-1:
Command

Program Development Commands
Function
Programming Languages and Environments

BASIC

Invokes the BASIC-PLUS or BASIC-PLUS-2 programming environment,
depending on the qualifiers you use or the default set by your system
manager.

Compiles PDPll-C programs.

COBOL

Compiles COBOL-81 programs.

DIBOL

Compiles a DIBOL-U program.

FORTRAN

Compiles a FORTRAN program. 'I\vo compilers are available:
FORTRAN-IV and FORTRAN-77; depending on the qualifiers you
use or the default set by your system manager.

MACRO

Assembles a program written in MACRO-ll.
Programming Operations

8.1

LINK

Links together object files to produce an executable file.

RUN

Executes a system or user program.

Developing Programs on RSTS/E
You can develop programs on RSTSIE using a variety of techniques and languages. BASIC-PLUS (supplied with all RSTSIE systems) is highly interactive,
and provides a self-contained programming environment.
BASIC-PLUS is an interpreted language. As you enter lines of source code into
the system, BASIC-PLUS immediately translates them into code that the system
can execute. Thus, you can run a program right after you finish entering it.
Program Development

8-1

Other high-level languages (such as BASIC-PLUS-2, CC, COBOL, DIBOL, and
FORTRAN) are compiled languages, generating PDP-ll object code. To develop
programs in these languages, you must create a source program, then compile it
and link it before it can be run.
In addition, the MACRO-ll assembler (supplied with all RSTSIE systems)
lets you write programs that correspond line-for-line with PDP-ll machine
instructions. You follow the same general steps to develop MACRO programs as
you do for compiled languages.
BASIC-PLUS and BASIC-PLUS-2 are command environments on RSTSIE. This
means that you can switch from DCL command level to a BASIC environment,
which has its own prompt for accepting your input. (The BASIC-PLUS prompt
is "Ready." The BASIC-PLUS-2 prompt is usually "BASIC2," depending on what
your system manager has specified.) By contrast, you develop programs in some
other languages by using DCL commands.
The number and type of programming tools available on any given RSTSIE
system (as well as the language you choose for any given application) depend
on many factors. These factors include: the size of the system; its cost; and the
application environment.
The following is an overview of the program development cycle for compiled
languages - that is, those RSTSIE languages other than BASIC-PLUS. For
information about programming in a specific language (including sample
programs and procedures), see the appropriate language manual.

8.2 Overview
RSTSIE offers a number of different languages for program development.
Although each language is unique, you use a similar process when developing any
program that you compile.
Briefly, the major steps are:

1. Design - Planning and initial coding.
2. Edit - Entering code into a source file.
3. Compile - Compiling or assembling source code into an object file.
4.

Link - Combining object files into an executable file.

5. Test - Making trial runs of an executable file and finding errors.
The next four sections introduce the tools you use for the edit, compile, link,
and test steps. The commands you use in each step depend on the programming
language you select.

8.2.1

Editing
A source program is a file containing text; this is the form of your program that
you actually write. The text in a source program consists of statements in BASIC,
CC, COBOL, DIBOL, FORTRAN, MACRO, or some other high-level language.
You generally use an editor such as EDT (which you invoke with the EDIT
command) to create a file containing the text of your source statements. An editor
allows you to type lines of the program and save it as a file. When you have
entered the program lines into the file the way you want them, you are ready for
the compile step.

8-2

Program Development

8.2.2

Compiling
There is a command for compiling each high-level language. The compiler:

Reads the source-code file you have created with your editor

Compiles it into PDP-ll machine code

Writes the compiled machine code into an object file

On PDP-ll systems, the object output is called a "module"; it contains your
program in the binary language that, when linked, is executable by a PDP-ll
computer.
A single line of source code, especially in a high-level language, may be compiled
into many PDP-ll instructions. The efficiency (and improved clarity) of not
having to write machine instructions a line at a time is one of the important
reasons for using a high-level language.
MACRO is called an "assembler." For tills discussion, its function is the same as
that of any compiler. MACRO turns source code into object code, and it fits into
the program development cycle the same way as do the compilers.
In addition, the MACRO assembler can produce a listing that shows both your
source code and the generated object code. This listing, like other listings
prepared by compilers, is helpful during the debugging process.
Another listing that is useful in debugging is the "cross-reference" listing. This
listing shows where each symbol is referenced in your source program. For the
MACRO assembler, you can request this cross-reference as part of the assembler's
program listing. For some of the other languages, there are separate programs
that operate independently of the compilers to produce cross-reference listings.
For example, BASIC-PLUS has BPCREF; BASIC-PLUS-2 has B2CREF.

8.2.3

linking
A program that is ready for execution by the system is caned an executable file.
(Other terms for executable file are save image, task, or load module.)
Th prepare an executable file from your object module, you must link it. Linking
a program into an executable file performs three major functions:
..

Combination of modules - You can link several separately compiled object
files together into a single executable file.

Relocation of addresses - Because the assignment of actual memory locations
for any object module must depend on the other object modules which go into
the load module with it, the link step is the time when references to absolute
memory locations are fixed.

Other object modules - You can incorporate modules that the system
supplies into your executable file. Each high-level language requires certain
object modules to be linked into executable files for programs written in that
language.

Program Development

8-3

8.2.3.1

Combining Modules
There are two main reasons why you want to be able to link an executable file
from separately compiled object modules:
..

If your program is complex, it is helpful to be able to compile it in several

smaller pieces as opposed to one large program. During debugging, you can
then recompile only the smaller piece that you have changed before linking a
new executable file for further testing.
..

You can link subroutines into a main program. You do so by maintaining
a library of subroutines from which the linker can extract object modules.
Therefore, you can reduce repetitious source coding in your main program.

The use of subroutines also allows you to write the main portion of your program in one language, and other portions in another. For example, when
writing a main program in FORTRAN, you might also want to code a special
or performance-sensitive subroutine in MACRO.

8.2.3.2

Relocating Addresses
The final location of an object module in a linked executable file cannot be
determined until the object modules are combined during linking. Therefore,
object modules are relocatable. In addition to binary machine instructions, an
object module contains tables of information that direct link-time operations, such
as address relocation.
Note that the linker can optionally produce a listing of resolved addresses, called
a map.

8.2.4

Testing
You can rarely create a program that does not contain at least one error, either
in its logic or in its coding. You may discover errors while you are editing the
program. Furthermore, the compiler may find errors during the compilation
process. The compiler informs you of any errors it finds by using error flags
in the listings. The linking process may also catch certain errors and issue
appropriate messages.
However, often you do not discover that the program does not work properly until
you run your program. Some programming errors are difficult to find. For this
reason, special debugging tools are supplied with most high-level languages. See
the appropriate programming language manual for information about available
debugging tools.

8.3 The RT11 and RSX Tools
Most of the high-level languages available on RSTSIE are very similar to corresponding languages on RT-ll or RSX-ll. Therefore, the program development
commands you use on RSTSIE are similar to the RTll and RSX program
development commands.
For example, when you develop a FORTRAN-IV program on RSTSIE, you use
commands similar to those on RTll. When you develop a program in other
high-level languages (including FORTRAN-77, but excluding BASIC-PLUS), you
use commands similar to those on RSX. You can develop MACRO-ll programs
using either set of program development commands.

8-4

Program Development

The description of the program development cycle stated earlier applies to the
commands for either RTll or RSX. However, the appropriate command for each
programming environment is unique: there is one set of commands for RTll, and
another set for RSX.
Table 8-2 shows the two sets of commands.
Table 8-2:

Program Development Commands for RTH and RSX

Generic Name

RTll Command

RSXCommand

CC
LINKICC

COBOL

DIBOL

FORTRAN

FORTRANIFOR

FORTRANIF77

MACRO

MACROIRTll

MACRO/RSXll

Linker

LINKIFOR
LINKlRTll

LINKlF77
LINKlC8I
LINKIDIBOL
LINKlRSXll
LINKlBP2
LINKICC

The file types assigned to executable files are .SAV for the RTll-based linker
and .TSK for the RSX-based linker. The file type of object files is .OBJ in either
environment.

8.3.1

RT11-Based Programming
You can use RSTS/E's RTll-based commands to develop programs in either
FORTRAN-IV or MACRO. Depending on your application, the programs you
develop can be either:
..

Run directly on your RSTSIE system

Debugged on RSTSIE, compiled, and run on an RT-ll system

Using MACRO, you can write programs that use any feature of RSTSIE, or
programs that use only RTll monitor directives.

8.3.2

RSX-Based Programming
You can use RSTSIE's RSX-based commands to develop programs in MACRO or
any of the high-level languages. Depending on your application, your developed
programs can be either:
..

Run directly on your RSTSIE system

Debugged on RSTSIE, compiled, and run on an RSX-ll system

Using MACRO, you can write programs that use any feature of RSTSIE, or
programs that use only RSX monitor directives. Certain features of RSTS/E are
also available directly through some high-level languages. (For example, the
BASIC-PLUS SYS calls, which are also available in BASIC-PLUS-2.)

Program Development

8-5

If you want to use the RMS data management package in your application, you
will be using RSTSIE's RSX-based languages. (See RMS documentation for more
information.)

8-6

Program Development

8.4 BASIC
The BASIC command places you in the BASIC-PLUS or BASIC-PLUS-2
programming environment, depending on the qualifiers you use and the system's
default.
In BASIC-PLUS, you can use BASIC-PLUS keyboard monitor commands (for
program development), or CCL commands. In BASIC-PLUS-2, you can use
program development commands.
To return to DCL from the BASIC-PLUS or BASIC-PLUS-2 environment, type:
$

or
$SWITCH

See Appendix B, or the appropriate language manual, for details on the commands you can use in these environments.
BASICIBP2 invokes the BASIC-PLUS-2 environment to begin a programming
session:
$ BASIC/BP2 <RET>

The system displays the following prompt for the BASIC-PLUS-2 environment:
BASIC2

BASICIBPLUS invokes the BASIC-PLUS environment:
$ BASIC/BPLUS <RET>

The system displays the following prompt for the BASIC-PLUS environment:
Re a dy

Format
BASIC
Command Qualifiers
IBP2
IBPLUS

Defaults
IBP2

Command Qualifiers
IBP2
Invokes the BASIC-PLUS-2 programming environment.
IBPLUS
Invokes the BASIC-PLUS programming environment.

Program Development

8-7

8.5 CC
The CC command invokes the PDP-ll C compiler to compile C source programs.
NOTE

All user input is converted to uppercase unless it is enclosed in
quotation marks.

Format
CC

(file-spec[, ...])

Command Qualifiers
f[NO]DEFINE=("identifier[(param, ... )] token-string" [, ... ])
fENVIRONMENT =([NO]FPU, [NO]PIC)
fENVIRONMENT =NOPIC, FPU
f[NO]ERROR_LlMIT[=qualifier]
fERROR_LlMIT =30
f[NO]INCLUDE_DIRECTORY=(pathname [, ... ])
f[NO]LlST[=file-spec]
f[NO]MACRO[=file-spec]
f[NO]MEMORy[=qualifier]
f[NO]MODULE=(identifier I "string" [,identifier I"string"])
f[NO]OBJECT[ =file-spec]
fSHOW[=option, ...]
fSHOW=(CONDITIONALS, SOURCE)
f[NO]STANDARD[=(option, ... )]
f[NO]TERM INAL[=[NO]SOURCE]
f[NO]TITLE=(identifier)
/[NO]UNDEFINE=(identifier[, ... ])
/[NO]WARNINGS[=(option, ... )]
/[NO]WORK_FILE_SIZE=integer_number

Defaults
fNODEFINE
See discussion
fERROR_LlMIT =30
See discussion
See discussion
/NOLIST
fNOMACRO
fNOMEMORY
See discussion
/OBJECT
See discussion
See discussion
fANSI
fNOSOURCE
fNOTITLE
/NOUNDEFINE
/WARNINGS
See discussion

PROMPTS
file-spec[, ... ]

Command Parameters
file-spec[, ... ]

One or more PDP-ll C source files separated by plus signs or commas. If
plus signs are used, the input files are concatenated into a single object file.
If commas are used, each file is compiled separately to create separate object
files. If no input file extension is specified, PDP-ll C assumes the .C default file
extension.

8-8

Program Development

Qualifiers indicate special actions to be performed by the compiler or special
input file properties. Compiler qualifiers can apply to either the CC command
or to the specification of the file being compiled. When a qualifier follows the
CC command, it applies to all the files listed. When a qualifier follows the file
specification, it applies only to the file immediately preceding it.

Command Qualifiers
IDEFINE=("identifier[(param, ... )] token-string" [, ...J)
INODEFINE

Performs the same function as the #define preprocessor directive. That is,
/DEFINE defines a token string or macro to be substituted for every occurrence of
a given identifier in the program. All input is converted to uppercase unless it is
enclosed in quotation marks.
The simplest form of a /DEFINE definition is: /DEFINE=("TRUE 1")
This results in a definition the same as: #define TRUE 1
Macro definitions must be enclosed in quotation marks as in: /DEFINE=("funct(a)
a+sin(a)")
This definition produces the same results as: #define funct(a) a+sin(a)
When more than one /DEFINE is present on the command line or in a single
compilation unit, only the last /DEFINE is used. When both /DEFINE and
IUNDEFINE are present in a command line, /DEFINE is evaluated before
IUNDEFINE. The default is INODEFINE.
IENVIRONMENT=([NO]FPU, [NO]PIC)
IENVIRONMENT=(NOPIC,FPU)

Specifies the type of environment in which the generated code is to execute or the
type of environment in which the object module is to be linked or both.
If you specify [NO]FPU, [NO]PIC, provide at least one value, or an error message
is generated.
If FPU is specified or defaulted, FPU instructions are generated as appropriate.

If NOFPU is specified, FPU instructions are not be generated.
If you specify PIC, PDP-ll C produces position independent code. If you specify

or default to NOPIC, non-pic code may be generated. For information on position
independent code, refer to the related discussion in the PDP-ll MACRO-ll
Language Reference Manual.
The default is IENVIRONMENT=(NOPIC,FPU).
IERROR_ LlMIT[=qualifier]
IERROR_LlMIT=30
INOERROR_LlMIT

Indicates the maximum integer error count. If the number of errors encountered
(exclusive of informationals and warnings) exceeds the integer value specified, the
compilation is aborted without further source code analysis.
The default is IERROR_LIMIT=30. If INOERROR_LIMIT is specified, compilation
proceeds regardless of the number of errors encountered.
IINCLUDE_DIRECTORY=(pathname [, ... J)
INOINCLUDE_DIRECTORY

Provides an additional level of search for include files. Each pathname argument
can be either a logical name or a legal directory specification, in quoted form.

Program Development

8-9

The fonns ofinc1usion effected are the #include "file-spec" and #inc1ude <file-spec>
fonns. For the quoted fonn, the order of search is as follows:
•

The directory containing the top level source file

•

The directories specified in the /INCLUDE_DIRECTORY qualifier (if any)

•

The current default directory

For the bracketed fonn, the order of search is as follows:
•

The directories specified in the /INCLUDE_DIRECTORY qualifier (if any)

•

The directory or search list of directories specified in the logical name, CLB

•

The directory specified by CC$:

The default is INOINCLUDE_DIRECTORY.
ILlST[ =file-spec]
/NOLIST
Controls whether a listing file is produced. The default output file extension is
.LST. The default is INOLIST.
IMACRO[=file-spec]
INOMACRO

Controls whether a macro listing file is produced. The default output file
extension is .MAC. A legal MACRO-11 source program corresponding to the
translation of the source program is placed in the specified file.
Note that the /MACRO qualifier differs from the ISHOW=MACHINE_CODE
qualifier as follows:
•

The /MACRO qualifier places a MACRO-11 source program in a separate file
rather than the listing file

•

The MACRO-11 source program may be assembled under MACRO-11 without
modification

•

The ISHOW=MACHINE_CODE qualifier places a machine code listing similar
to the list file output by MACRO-11 into the listing file. The machine code
listing cannot be directly assembled under MACRO-11

The default is INOMACRO.
IMEMORY[=quallfier]
INOMEMORY

Determine the amount (in 8Kb regions) of extended memory to allocate in a
PDP-11 host environment.
The specified integer value determines the number of 8192-byte regions which
are to be allocated. An integer between 0 and 512 may be specified to allocate up
to the 4Mb architectural limit of the PDP-11.
If the specified amount of extended memory is not available or if the specified

value exceeds the maximum size established by the system manager when PDP11 C is installed, the largest number of available 8192 byte regions which does
not exceed the installation maximum are allocated.
In general, the greater amount of extended memory allocated, the less work file
activity, and the faster the perfonnance of the compiler. INOMEMORY is the
default and is equivalent to IMEMORY=O. The default value is the maximum size
detennined during installation of PDP-11 C.

8-10

Program Development

IMODULE=(identifier I "string" [,identifier I "string"])
IMODULE=("last-file-spec-name", "V1.0")
Controls the compiler produced output module header for the program file. This
qualifier will accept a maximum of two string values, and you must supply at
least the first string value.

The last-file-spec-name is the last file name specified for a given compilation unit.
The default is /MODULE=("last-file-spec-name","V1.0").
IOBJECT[=file-spec]
IOBJECT
Controls whether a object file is produced. The output file extension is .OBJ. The
default is IOBJECT.
ISHOW[=(option,. .. )]
ISHOW=(CONDITIONALS,SOURCE)
Used with the !LIST qualifier to set or cancel specific listing options. You can
select the following options:

•

ALL
Print all listing information.

•

[NO]CONDITIONALS
Specifying ISHOW=CONDITIONALS causes conditional program segments
that were not compiled (due to #if type preprocessing directives) to appear
in the listing. Specifying ISHOW=NOCONDITIONALS causes conditional
program segments that were not compiled to be omitted in the listing. The
default is ISHOW=CONDITIONALS, or as established during installation of
PDP-ll C.
NOTE

The ISHOW=[NO]CONDITIONALS qualifier is similar to the same
qualifier used by DIBOL and MACRO-32.
•

[NO]EXPANSION
Specifying ISHOW=EXPANSION causes final macro expansions to be printed
in the program listing. Specifying this option, causes the macro nesting level
of the last macro expanded on the line to print next to each line. The default
is ISHOW=NOEXPANSION.

•

[NO]INCLUDE
Specifying !INCLUDE causes the contents of #include files to be printed. The
default is ISHOW=NOINCLUDE.

•

[NO]INTERMEDIATE
Specifying !INTERMEDIATE causes the intermediate macro expansions in
the program listing to be printed. The default is ISHOW=NOINTERMEDIATE.

•

NONE
No listing information is printed.

•

[NO]MACHINE_CODE
Specifying ISHOW=NOMACHINE_CODE directs the compiler to NOT list the
generated machine code in the listing file. The default is ISHOW=MACHINE_
CODE.

•

[NO]SOURCE
Specifying /NOSOURCE causes the source file statements not to be printed.
The default is ISHOW=SOURCE.

Program Development

8-11

ISTANDARD[::(option, ... )]
INOSTANDARD
Determines what language features is allowed, or flagged as nonstandard. One of
the following values may be specified:
@

ANSI

•

/NOSTANDARD implies PDP-ll C native syntax and semantics

•

/STANDARD=ANSI implies ANSI C standard syntax and semantics. The
default is /NOSTANDARD. Compilation time may increase slightly when
/STANDARD=ANSI is specified.

•

If /STANDARD is specified without a value, /STANDARD=ANSI is assumed

ITERMINAL[::[NO]SOURCE]
Encompasses the functionality of VAX C's /SHOW =TERMINAL qualifier and
embodies additional functionality as well. If /NOTERMINAL is specified, only the
summary message is displayed on the user terminal or batch log, as appropriate
(this is the same as /SHOW=NOTERMINAL under VAX C).

If /TERMINAL or ITERMINAL:::NOSOURCE is specified, compiler messages are
displayed on the user terminal or batch log, as appropriate, but associated user
source text is not displayed (this is the same as /SHOW=TERMINAL under VAX
C).
If /TERMINAL=SOURCE is specified, compiler messages and associated user
source text (without macro expansion) are displayed on the user terminal or
batch log, as appropriate (this functionality is not available under VAX C).

The default is /TERMINAL=NOSOURCE, or as established during installation of
PDP-ll C.
ITITLE=(identifier)
/NOTITLE
Controls the compiler produced output list header for the program file. This
qualifier if asserted must be supplied with a string value. The identifier is the
list title name for a given compilation unit.

The default is /NOTITLE.
IUNDEFINE::(identifier[, ... ])
INOUNDEFINE
Performs the same function as the #undef preprocessor directive-it cancels a
macro definition. It is useful for undefining the predefined PDPll C preprocessor
constants. For example, if you use a preprocessor constant (such as pdpc, PDPC,
PDPllC, or vms) to conditionally compile segments of PDPll C specific code, you
can undefine constants to see how the portable sections of your program execute.
For example; /UNDEFINE="pdpc".

When both !DEFINE and /UNDEFINE are present on the CC command line,
!DEFINE is evaluated before /UNDEFINE. The default is /NOUNDEFINE.
IWARNINGS
I[NO}WARNINGS[::(option, ... )]
Controls whether the compiler prints warning diagnostic messages, informational
diagnostic messages, neither, or both. The options are NOINFORMATIONALS
and NOWARNINGS.

The /WARNINGS qualifier alone forces the compiler to print both informationals
and warnings (the same as if no qualifier were used on the command line). The
/NOWARNINGS qualifier forces the compiler to suppress both informationals and
warnings.
8-12

Program Development

The !WARNINGS=NOINFORMATIONALS qualifier forces the compiler to
suppress the informationals. The !WARNINGS=NOWARNINGS qualifier forces
the compiler to suppress warnings. The default is !WARNINGS.
/[NO]WORK_FILE_ SIZE= integer_number

The integer_number is a integer value between 1 and 65535 representing the
number of 512-byte disk blocks to allocate for the work file.
If !WORK_FILE_SIZE is not specified, a default work file size that is specified

when PDP-ll C is installed is used. If the specified value exceeds the maximum
determined by the system manager when PDP-ll C is installed, the maximum
value is used instead. The work file size determines PDP-ll C's capacity for
processing source input. Note that the /MEMORY qualifier affects PDP-ll C's
performance, not capacity.
The work file is placed at a location that is specified when PDP-ll C is installed.
PDP-ll C first attempts to open the work file contiguously. If insufficient
contiguous disk storage is available, PDP-ll C attempts to open the work file
noncontiguously. If insufficient noncontiguous disk storage is available, PDP-ll C
issues a diagnostic and aborts. PDP-ll C does not extend the work file: if work
file storage is exausted during compilation, a diagnostic is issued and PDP-ll C
aborts.
NOTE

If this qualifier is used it MUST be specified with the first compilation

unit.

Program Development 8-13

8.6 COBOL
The COBOL command compiles a COBOL-81 program. (You can compile only one
source file at a time with COBOL-81.)

Format
COBOL
Command Qualifiers
I[NO]ANSI_FORMAT

Defaults
INOANSI_FORMAT

IC81

I[NO]CHECK
ICHECKHNO]BOUNDS]
ICHECK[=[NO]PERFORM]
ICODE=[NOJCIS
/[NO]CROSS_REFERENCE
/[NO]DEBUG
I[NO]DIAGNOSTICS[=diagfile]
I[N 0] LlST[=Iistfile]
I[NO]MAP
INAMES=aa
I[NO]OBJECT[=objfile]
I[NO]OPTIMIZE
I[NO]SHOW
ISHOW[=[NO]MAP]
ISTANDARD[=option]
I[NO]SUBPROGRAM
!TEMPORARY=device
I[NO]TRUNCATE
I[NO]WARNiNGS
IWARNINGS[=[NO]INFORMATIONAL]

ICHECK
none
none
See discussion
INOCROSS_REFERENCE
INODEBUG
INODIAGNOSTICS
INOUST
INOMAP
INAMES=SC
10BJECT[=objfile]
INOOPTIMIZE
INOSHOW
See discussion
INOSTANDARD
INOSUBPROGRAM
ITEMP=SY:
INOTRUNCATE
/WARNINGS
IWARNINGS=INFORMATIONAL

Prompts
File: source_file

Command Parameters
source_file
Specifies a COBOL program to be compiled. You must specifY a source file name.
If you do not include a file type, the compiler uses the default type of .CBL.
No wildcards are allowed for the source file.

8-14

Program Development

Command Qualifiers
IANSLFORMAT
INOANSI_FORMAT

Indicates whether the source program is in ANSI COBOL format or in Digital's
terminal format.
An ANSI COBOL source file has 80-character records with Area A beginning in
column position 8.

The recommended default is for the COBOL command to assume that the input
records are in terminal format. (Area A begins in column position 1 and the
lines do not have line numbers.) However, your system manager can change the
default at system installation.
IC81

Specifies the COBOL-81 compiler. This is the default.
/CHECK
INOCHECK
ICHECK[=[NO]BOUNDS]
ICHECK[=[NO]PERFORM]

Controls whether the compiler produces extra code to check for program correctness at run time. The /CHECK qualifier verifies subscripts, indexes, and perform
statement ranges. The /CHECK qualifier is the recommended default and causes
COBOL-81 to check each subscript and table at run time against the ranges
defined by its data-name's OCCURS clause. (Your system manager can change
this default at system installation.) The /CHECK qualifier also causes COBOL-81
to determine if your program's PERFORM ranges are nested properly (if nested
at all). If COBOL-81 detects improper nesting during execution, it issues an error
message to that effect.
The /NOCHECK qualifier suppresses all checking, which can save execution time
and decrease task image size. If you use /NOCHECK to suppress error checking,
an out-of-range subscript or index does not generate an error message. The
/NOCHECK qualifier also stops the compiler from generating code needed for
checking PERFORM statement ranges. If you use /NOCHECK and the program's
PERFORM statements are nested incorrectly, the program does not produce valid
results.
You can have the compiler generate code to check only subscripts and indexes
by specifying ICHECK=(BOUNDS, NOPERFORM). Likewise, you can check only
PERFORM statement ranges by specifying ICHECK=(PERFORM, NOBOUNDS).
ICODE=CIS
ICODE=NOCIS

Controls whether the compiler uses Commercial Instruction Set (CIS) in the
object code it produces. CIS speeds program execution; however, not all processors
support CIS.
If your processor has CIS, the recommended default is ICODE=CIS; however, your
system manager can change the default at system installation. If your processor
does not have CIS, the default is ICODE=NOCIS.
/CROSS_REFERENCE
INOCROSS_REFERENCE

Controls whether the compiler listing includes a cross-reference listing. By
default, the compiler does not create a cross-reference listing. In addition, you
receive the error message ?Additional qualifier needed, unless you specify the
!LIST qualifier.
Program Development 8-15

IDE BUG
INODEBUG
Causes the compiler to use the COBOL-81 Symbolic Debugger. (The debugger lets
you control and monitor your program as it runs by referring to the source version
rather than the object code produced by the compiler.) The compiler generates
symbol information in the object module for all data-names and procedure-names.
This increases the size of the object file, but when you finish debugging and no
longer need the symbols, you can recompile without using this qualifier.

The recommended default is INODEBUG; however, the system manager can
change the default at system installation.
If you use the Symbolic Debugger in your program, you must also use the

LINKIDEBUG command to include the Debugger in your task image. See the
LINK command for more information.
IDIAGNOSTICS[=diagfile]
INODIAGNOSTICS
Controls whether the compiler produces an output diagnostic file.

The diagnostic file is a subset of the list file. It contains only the diagnostics
issued, along with the line of source code to which each diagnostic applies.
By default, the COBOL-81 compiler does not create a diagnostics file. If you
specify /DIAGNOSTICS without a file specification, the compiler creates a
diagnostic file with the same name as the object file, and in the same directory
on the same device as the object file, but with a .DIA file type. If you also specify
INOOBJECT, then the file has the same name as the source file, and is in your
directory on SY:.
ILlST[=listfile]
INOLIST
Controls whether the compiler produces an output listing.

The COBOL-81 compiler, by default, does not create a listing file. If you specify
/LIST without a file specification, the compiler creates a listing with the same
name as the object file, and in the same directory on the same device as the object
file, but with an .LST file type. If you also specify /NOOBJECT, then the file has
the same name as the source file, and is in your directory on SY:.
If you include a file specification, the listing is written to that file or device. The

default file type is .LST.
IMAP
INOMAP
The !MAP qualifier is the same as /SHOW=MAP. The /NOMAP qualifier is the
same as /SHOW=NOMAP. This qualifier exists for compatibility with previous
releases of RSTS/E.
INAMES=aa
Requests the compiler to generate program section names ending with the
two-character alphanumeric suffix, aa. If you link several object files into one
executable file then each object file must have a different suffix for its program
section names.

If you do not specify the /NAMES qualifier, RSTS/E uses the default suffix SC.

8-16

Program Development

IOBJ ECT[ =objfile]
INOOBJECT

Controls whether the compiler produces an object file and a skeleton file. These
files are used as input to the LINK command, which in turn produces an
executable program.
By default, (or if you specify /OBJECT without a file specification), the compiler
produces an object file with the same file name as the input file in your directory
on the public disk structure, with a file type of .OBJ. The compiler also uses the
default file type of .OBJ when you include a file name but no file type with the
/OBJECT qualifier. The skeleton file is in the same directory and has the same
name as the object file, but has an .SKL file type.
You cannot use wildcard characters in the file specification.
IOPTIMIZE
INOOPTIMIZE

TeIls the compiler whether to produce optimized code. The default is /OPrIMIZE.
ISHOW
INOSHOW
ISHOW=MAP
ISHOW=NOMAP

Determines whether the compiler produces a Data Division map showing the
memory addresses for Data Division entries. The /SHOW and /SHOW=MAP
qualifiers perform the same operations. The INOSHOW and ISHOW=NOMAP
qualifiers also produce the same results and are the recommended defaults.
However, your system manager can change the default at system installation.
You can use this qualifier only in conjunction with !LIST.
ISTANDARD=option
INOSTANDARD

STANDARD=85 compiles code according to the ANSI 1985 COBOL standard.
STANDARD=V2 compiles code according to the syntax rules for COBOL-81 V2.5.
The default is INOSTANDARD.
ISUBPROGRAM
INOSUBPROGRAM

Indicates the compiler is compiling a subprogram. Use this qualifier only if the
subprogram has not passed parameters from the calling program-that is, if the
subprogram does not contain the PROCEDURE DIVISION USING header. The
default is INOSUBPROGRAM.
ITEMPORARY=device

Changes the storage area for temporary work files from SY: (the default) to the
value you specify for "dev" (device). This qualifier is useful if you are running out
of space on the system disk, or if you have a faster disk available. Because of the
way the compiler names its temporary work files, two simultaneous compilations
of source programs with the same file name, in the same account, (regardless
of the types used) produces unpredictable results. This problem will not occur,
however, if you use the /TEMPORARY=dev qualifier to specify a nondefault device
for those files.

Program Development

8-17

ITRUNCATE
INOTRUNCATE

Specifies that the compiler perform decimal truncation on the values of COMP
data items.
The recommended default is for COBOL-81 to perform binary truncation rather
than decimal truncation. (Your system manager can change the default at
system installation.) With binary truncation, the maximum value a COMP
item can contain depends on its storage allocation. If you specify !TRUNCATE,
the maximum value depends on the item's PICTURE character-string. See the
COBOL-81 RSTS I E User's Guide for more information.
I[NO]WARNINGS
IWARNINGS=INFORMATIONAL
IWARNINGS[=NOINFORMATIONAL]

The /NOWARNINGS and /wARNINGS=NOINFORMATIONAL qualifiers stop the
compiler from issuing informational diagnostics during the compilation. If you
specify either of these qualifiers, only warning and fatal diagnostics will appear
in the list file, diagnostics file, and diagnostic summary.
The /WARNINGS and /wARNINGS=INFORMATIONAL qualifiers, the recommended defaults, specify that the compiler issue informational diagnostics during
the compilation.

8-18

Program Development

8.7 DIBOL
The DIBOL command compiles a DIBOL-ll program. You can include up to six
source file specifications to be compiled into a single object file with the DIBOL
compiler. The default file type is .DBL.

Format
DIBOL

filespec[, ...]

File Qualifiers
I[NO]DEBUG
I[NO]LlST[=listfile]
I[NO]OBJECT[=objfile]
I[NO]OPTIM IZE
I[NO]STANDARD
ISTANDARD=ANSI
ISTANDARD=D83
I[NO]WARNINGS

Defaults
INODEBUG
/NO LIST
IOBJECT
INOOPTIMIZE
INOSTANDARD
INOSTANDARD
INOSTANDARD
/WARNINGS

Command Parameters
filespec[, ... ]

Specifies a DIBOL program to be compiled. You can include up to six source file
specifications to be compiled into a single object file. If you do not include a file
type, the compiler uses the default type of .DBL.
No wildcards are allowed for the source file.

File Qualifiers
IDE BUG
INODEBUG

Controls whether the compiler uses the DIBOL Debugging Technique (DDT).
If you specify /DEBUG, you must also use the /DEBUG qualifier when you or
more separately compiled subroutines, and you want to use the debugging tool
on the entire program, you must compile each subroutine with the /DEBUG
qualifier. You can mix sections of your program that have been compiled with
/DEBUG with sections that have not been compiled with /DEBUG. However, you
can use debugging tools only in the sections compiled with /DEBUG.
ILlST[=listfile]
/NOLIST

Controls whether or not the DIBOL compiler produces an output listing.
By default, the compiler does not create a listing file. If you specify /LIST without
a file specification, then the compiler gives a listing file the same file name as the
object file (or, if you specify INOOBJECT, as the first input source file). The file is
placed in the same directory on the same device as the object file, but with a .LST
file type.
You cannot use wildcard characters in the file specification.
Program Development

8-19

IOBJ ECT[=objfile]
INOOBJECT

Controls whether the compiler produces an output object file.
By default, or if you specify /OBJECT without a file specification, the compiler
produces an object module that has the same file name as the first input source
file, and places it in your directory on the public disk structure with a file type of
.OBJ.
You cannot use wildcard characters in the file specification.
IOPTIMIZE
INOOPTIMIZE

Produces optimized code. The default is /NOOPI'IMIZE.
ISTANDARD
ISTANDARD=ANSI
ISTANDARD=D83

Specifies the syntax that the DIBOL compiler will accept. Specifying /STANDARD
or /STANDARD=ANSI tells the compiler to accept ANSI DIBOL SYNTAX.
Specifying /STANDARD=D83 tells the compiler to accept DIBOL-83 syntax. The
default is /NO STANDARD .
IWARNINGS
INOWARNINGS

Controls whether the compiler produces diagnostic messages for warning conditions.
Use /NOWARNINGS to override the compiler default. (The default is to issue
warning diagnostic messages.)

6-20

Program Development

8.8 FORTRAN
The FORTRAN command compiles up to six FORTRAN source files into a single
object file.
There are two FORTRAN compilers available on RSTSIE:

Command

Invokes

FORTRAN/F77
FORTRAN/FOR

FORTRAN-77
FORTRAN-IV

Program Development

8-21

8.8.1

FORTRAN/F77
The FORTRANIF77 command invokes the FORTRAN-77 compiler.

Format
FORTRAN/F77

file-spec£, .. .J

Command Qualifiers
I[NO]CHECK
ICONTINUATIONS=n
I[NO]D_LlNES
I[NO]DEBUG
I[NO] 14
I[NO]IDENTIFICATION
I[NO]LlST[=listfile]
I[NO]MACHINE_CODE
I[NO]OBJ ECT[=objfile]
[NO]OPTIM IZE
ISTANDARD[=ALL]
ISTANDARD[=SOURCE]
ISTANDARD[=SYNTAX]
INOSTANDARD
I[NO]WARNINGS
/wORK_FILES=n

Defaults
ICHECK
ICONTINUATIONS= 19
INOD_LlNES
INODEBUG
INOl4
INOIDENTIFICATION
INOLIST
INOMACHINE_CODE
IOBJECT
IOPTIMIZE
INOSTANDARD
INOSTANDARD
INOSTANDARD
INOSTANDARD
/WARNINGS
/wORK_FILES=2

Prompts
File: file-spec[, ... ]

Command Parameters
file·spec[ •... ]

Specifies one or more FORTRAN source programs to be compiled. If you do not
specify a file type, the compiler uses the default file type of .FTN.
You can specify more than one input file. The files are compiled as a single input
file. The result is one object module and. if !LIST is specified, one listing.
You cannot use wildcard characters in the file specification.

Command Qualifiers
/CHECK
/NOCHECK

Controls whether the compiler produces extra code that checks for program correctness at run time. The ICHECK qualifier (the default) causes the production
of code to check that all array references are to addresses within the address
boundaries specified in the array declaration.
/CONTINUATIONS=n

Specifies the maximum number of continuation lines to be permitted.
8-22

Program Development

The number of lines, n, is a decimal number from 0 through 99. By default, the
compiler accepts a maximum of 19 continuation lines.
IDEBUG
INODEBUG

Specifies that the compiler is to provide symbol table information for use by
the FORTRAN-77 symbolic debugger. When you use the /DEBUG qualifier you
should also use the /NOOPrIMIZE qualifier.
The default is /NODEBUG.
ID_LlNES
INOD_LlNES

Indicates whether the compiler reads and compiles debugging lines, which have
a D in column 1 of the source program. (Debugging lines check that the program
is working; they are not needed after the program is debugged.) If you specify
/D_LINES, lines that have a D in column 1 are compiled.
The default is /NO_DLINES, which means the compiler assumes that lines
beginning with a D are comments and does not compile them.

114
INOl4

Controls how the compiler interprets INTEGER and LOGICAL declarations that
do not specify a length.
If you specify 114, the compiler allocates a default length of two words (four bytes)

for integer and logical variables.
If you specify /NOI4, the compiler interprets the declarations as INTEGER*2 and

LOGICAL*2, respectively. /NOI4 is the default.
IIDENTIFICATION
INOIDENTIFICATION

Controls whether the FORTRAN-77 compiler identification and version numbers
are typed on your terminal. The default is /NOIDENTIFICATION.
ILlST[=listfile]
/NOLIST

Controls whether a listing file is produced.
By default, the compiler does not create a listing file. If you specify /LIST without
a file specification, then the compiler gives a listing file the same file name as the
object file, (or, if you specify /NOOBJECT, as the first input source file) and in the
same directory on the same device as the object file, but with an .LST file type.
If you give a file specification, the listing is written to that file. The default file

type is .LST.
You cannot use wildcard characters in the file specification.
IMACHINE_CODE
INOMACHINE_CODE

Controls whether the listing produced by the compiler includes the machine
language code that the compiler generated.
The default is /NOMACHINE_CODE, which omits machine language code in the
listing. The /MACHINE_CODE qualifier is invalid unless you also specify the
/LIST qualifier.

Program Development

8-23

IOBJECT[=objfile]
INOOBJECT

Controls whether the compiler produces an output object file.
By default (or if you specify IOB.JECT wit.hout a file specificat.ion). the compiler
produces an object module that has the same file name as the first input source
file, in your directory on the public disk structure. The default file type .OBJ.
You cannot use wildcard characters in the file specification.
IOPTIMIZE
INOOPTIMIZE

Tells the compiler whether to produce optimized code. The default is IOPTIMIZE.
Use the /NO OPTIMIZE qualifier during a debugging session to make sure that
the debugger has sufficient information to help you locate errors in your source
program.
ISTANDARD[=ALL]
ISTANDARD[=SOURCE]
ISTANDARD[=SYNTAX]
INOSTANDARD

Checks your source code for extensions to ANSI standard FORTRAN at the
full-language level, where:
ALL
SOURCE

Checks for all extensions

SYNTAX

Checks for syntax extensions

Checks for lowercase letters and tab characters

The default is /NOSTANDARD.
IWARNINGS
INOWARNINGS

Controls whether the compiler produces diagnostic messages for warning
conditions.
Use /NOWARNINGS to override the compiler default, which is to issue warning
diagnostic messages.
IWORK_FILES=n

Determines the number of temporary disk work files that should be used during
compilation. You can use from one to three files; the default value for n is 2.
If you increase the number of files, the size of the largest program to be compiled
can be increased, but you may decrease compilation speed.

8-24

Program Development

8.8.2

FORTRAN/FOR
The FORTRANIFOR command invokes the FORTRAN-IV compiler.

Format
FORTRAN/FOR

filespec[, .. .]

Qualifiers
/CODE=EAE
/CODE=EIS
/CODE=FIS
ICODE=THR
I[NO] D_LlN ES
I[NO]EXTEND_SOURCE
I[NO]14
I[NO]LlNENUMBERS
I[NO]LlST[=listfile]
/[NO]MACHINE_CODE
/[NO]OBJECT[ =objfile]
/[NO]OPTIMIZE
/[NO]WARNINGS

Defaults
See discussion
See discussion
See discussion
See discussion
INOD_LlNES
INOEXTEND_SOURCE
INOl4
ILiNENUMBERS
INOLIST
INOMACHINE_CODE
IOBJECT
IOPTIMIZE
/WARNINGS

Command Parameters
filespec [, ... J
Specifies one or more source files to be compiled into a single object file. The
default file type is .FOR.

Command Qualifiers
/CODE=EAE
/CODE=EIS
/CODE=FIS
/CODE=THR

The /CODE qualifiers select the type of object code to be generated.
The compiler produces distinctly different types of object programs by generating
either threaded code or inline code. The default is determined by the system
manager at system installation time.
The valid values are:
EAE - Selects EAE hardware
EIS - Selects EIS hardware
FIS - Selects EIS and FIS hardware
THR - Selects threaded code

Program Development

8-25

When the compiler produces inline code (lCODE= fonowed by EAE, EIS, or FIS)
the object program executes at greater speed and generally uses less physical
memory. Inline code achieves this optimization, in part, by omitting instructions
to detect or report certain error conditions. However, you can generate code for
error checking by including the /CODE=THR option in the compiler command
line.
When the compiler generates threaded code (through the /CODE=THR option),
the object program produced uses a symbolic library routine to perlorm each
operation required for program execution. The executable program consists of
a "threaded" list of the addresses of library routines and appropriate operand
addresses. This type of code generation produces an object module that operates
independently of hardware arithmetic configuration. You can combine it with any
of the FORTRAN-IV OTS libraries to produce a valid executable program for each
type of arithmetic hardware without any need for recompilation.
ID_LiNES
/NOD_LINES

Indicates whether the compiler reads and compiles debugging lines. (Debugging
lines have a D in column 1 of the source program.) If you specify ID_LINES, lines
that have a D in column 1 are compiled.
The default is /NOD_LINES, which means the compiler assumes that lines
beginning with a D are comments and does not compile them.
IEXTEND_SOURCE
I[NO]EXTEND_SOURCE

Indicates whether to allow source lines to contain significant characters in
columns 73 through 80.
The default is INOEXTEND_SOURCE.
114
INOl4
Controls how the compiler interprets INTEGER and LOGICAL declarations that
do not specify a length.
If you specify II4, the compiler allocates a default length of two words (four bytes)

for integer and logical variables.
By default (or if you specify /NOI4), the compiler interprets these as INTEGER*2
and LOGICAL*2, respectively.
IUNENUMBERS
INOUNENUMBERS

The /LINENUMBERS qualifier indicates that internal sequence numbers are to
be included in the executable program for routine diagnostics.
The /NOLlNENUMBERS qualifier suppresses generation of internal sequence
numbers.
lUST=[Iistfile]
/NOLIST

Controls whether a listing file is produced.
The compiler does not create a listing file by default. If you specify /LIST without
a file specification, then the compiler gives a listing file the same file name as the
object file. (If you specify INOOBJECT, then the compiler gives the name of the
first input source file.) The file also is in the same directory on the same device
as the object file, but with an .LST file type.

8-26

Program Development

If you give a file specification, the default file type is .LST. You cannot use

wildcard characters in the file specification.
IMACHiNE_CODE
/NOMACHINE_CODE

Controls whether the compiler produces an output object file.
By default, or if you specify /OBJECT without a file specification, the compiler
produces an object module that has the same file name as the first input source
file, in your directory on the public disk structure, with a default file type of .OBJ.
If you give a file specification, the default file type is .OBJ. You cannot use

wildcard characters in the file specification.
IOPTIMIZE
INOOPTIMIZE

Tells the compiler whether to produce optimized code. The default :is /OPrIMIZE.
Use the lNOOPTIMIZE qualifier during a debugging session to make sure that
the debugger has sufficient information to help you locate errors in your source
program.
IWARNINGS
INOWARNINGS

Controls whether the compiler produces diagnostic messages for warning conditions.
Use /NOWARNINGS to override the compiler default. (The default is to issue
warning diagnostic messages.)

Program Development

8-27

8.9 MACRO
The MACRO command invokes a MACRO-ll assembler. You can include up to
six file specifications with the MACRO command.
On RSTSIE you can use either MACROIRTll or MACROIRSXll. The default is
MACROIRSXll, unless your system manager has changed it. The default file
type is .MAC with one exception: .MLB is the default file type if you use the
RSX-based assembler with the /LIBRARY qualifier.

Format
MACRO/RT11

filespec[, ... ]

MACRO/RSX11

filespec[, ...]

Command Qualifiers
/[NO]UST[=listfile]
I[NO]OBJECT[=objfile]

Defaults
/UST[ =listfile]
IOBJECT[=objfile]

File Qualifiers
/UBRARY

Command Parameters
filespec[, ... ]

Specifies one or more source files to be compiled into a single object file. The
default file type is .MAC with one exception: .MLB is the default file type if you
use the RSX-based assembler with the /LIBRARY qualifier.

Command Qualifiers
IUST[=listfile]
/NOUST

Controls whether a listing file is produced. Unlike the other languages on
RSTSIE, MACRO produces a listing file by default. (In other words, the !LIST
qualifier is assumed.) The assembler gives a listing file the same file name as the
object file and puts it in the same directory on the same device as the object file.
If you specify INOOBJECT, then it assumes the name of the first input source
file, and is placed in your directory on the public structure. The default file type
is .LST.
You cannot use wildcard characters in the file specification.
IOBJECT[=objfile]
INOOBJECT

Controls whether the assembler produces an output object module.
By default (or if you specify /OBJECT without a file specification), the assembler
produces an object module that has the same file name as the first input source
file, on your directory on the public structure. The default file type is .OBJ.

8-28

Program Development

You cannot use wildcard characters in the file specification.

File Qualifiers
ILiBRARY
Indicates that the file is a macro library.
When a macro call is found in the source program, MACRO-ll searches the user
macro library for the named macro definitions. If necessary, MACRO-ll then
continues the search with the system macro library.

Program Development

8-29

8.10 UNK
The LINK command combines one or more of your compiled or assembled object
files, including routines from appropriate libraries, into a single executable file.
NOTE

This section describes the DeL LINK command and its qualifiers.
See the RSTS IE Task Builder Reference Manual or the RSTS IE
RTll Utilities Manual for a complete description of linking concepts,
overlays, and libraries.

Format for Simple (Non-Overlaid) Link
LINK

file-spec[, ...1

Format for Overlaid Link
LINK /STRUCTURE

LINK prompts for overlay structure

Command Qualifiers
ICODE=[NOjDATA_SPACE
ISORTy,ND_MERGE=[NO]RESIDENT

Defaults
ICODE=NODATA_SPACE
none

language Qualifier
IBASIC or IBP2
ICC
ICOBOl or IC81
IDIBOl
I[NO]DMS
IF77
IFOR
IRSX11
IRT11
ISTACK

See discussion
none
none
none
INODMS
none
none
See discussion
none
See discussion

Debugging Qualifier
/[NO] DEBUG

INODEBUG

Description Qualifier

8-30

IDESCRIPTION

See discussion

Forms Management System Qualifier
I[NO]FMS

none

Program Development

Library Qualifiers
IFMS[=[NO] RES IDENT]
IOTS=[NOJRESIDENT
I[NO]RMS
IRMS=[NO]RESIDENT
=SUPERVISOR
=USER

none
none
none

Output File Qualifiers
/[NO]EXECUTABLE[=filespec]
I[NO]MAP[=filespec]

IEXECUTABLE
INOMAP

Overfay Qualifier
ISTRUCTURE

Defaults
(no overlay structure)

Prompt (No Overlays)
Files: file-spec1 [,file-spec2, ... ]
Prompt (Overlays requested with /STRUCTURE qualifier)
ROOT files:
file-spec1 [,file-spec2, ... ]
Root COMMON areas:
[common-areaJ[, ... I
Overlay:
[file-spec[, ... U+U

(more prompts for overlays)

Two linker programs are available on RSTS/E:
•

The RSX-based linker (the Task Builder)

•

The RTll-based linker (LINK.SAV)

The LINK command invokes one or the other, depending on your source
language. (You indicate the source language by including a language qualifier.)
BASIC-PLUS-2 is the default.

Program Development

~31

Table 8-3 shows the language qualifiers and whether the RSX-ll-based or
RTll-based linker is run in each case.
Table 8-3:

language Qualifier, Source Language, and Linker Relationship

Qualifier

Source Language

Linker

!BP2
!BASIC

BASIC-PLUS-2

RSX-ll-based

ICO

PDPll-O-based

ICOBOL
1081

COBOL-81

RSX-ll-based

IDIBOL

DIBOL

RSX-ll-based

!F77

FORTRAN-77

RSX-ll-based

!FOR

FORTRAN-IV

RTll-based

IRSXll

MAORO Assembler

RSX-ll-based

IRTll

MACRO Assembler

RTll-based

Command Parameters
input file list
The LINK command creates an executable file from one or more of your compiled
or assembled object files. You specify the input files, that is, the object files, in
one of two places in the LINK command: either beginning on the same line as
the LINK command or in response to the prompt, depending on whether you use
the /STRUCTURE qualifier to request overlays.

In any case, the standard RSTSIE defaults for file specifications apply. The
default device is the public structure (SY:); the device must be disk. The default
file type for input files (your object files to be linked) is .OBJ. Note that for
COBOL programs, the LINK command expects to find a skeleton file (type .SKL)
on the same device and account, with the same file name, as each .OBJ file listed.
(A COBOL compile automatically produces .SKL and .OBJ files.)
Simple (Nonoverlaid) Linking

For a simple (nonoverlaid) link, specify the object files beginning on the same line
as the LINK command. If you have many files, you can continue a line by typing
a hyphen (-) at the end ofthe line.
The LINK command translates the command you specify into a command line
to another program. The translated command cannot exceed 127 characters (80
characters for a COBOL program). If the continued command line is too long,
you get the error message ?Command too long. If you need to link more files, you
must run the Task Builder or the LINK linker directly (see the RSTS / E Task
Builder Reference Manual or the RSTS / E RTll Utilities Manual).
The files you name are linked, together with routines from appropriate libraries,
in the order you specify. That is, the first file you name occupies the lowest range
of addresses in the program, the second file you name is linked to occupy a range
of addresses immediately fonowing the first, and so forth.

Command Qualifiers
/CODE=[NO]DATA_SPACE
This qualifier indicates the program uses seperate I & D space.

8-32

Program Development

ISORT_AND_MERGE::[NO]RESIDENT

This qualifier invokes the SortllVIerge utility and specifies the correct library
(resident vs. nonresident).

language Qualifiers
IBASIC
IBP2

Indicates that the object files listed in the command are BASIC-PLUS-2 object
files. Unless your system manager selects another default for your site, IBP2 is
the default if you do not specify any language qualifier. (IBASIC and IBP2 are
equivalent qualifiers.)
This qualifier provides an easy way to link BASIC-PLUS-2 programs. However,
Digital recommends that you use the IDESCRIPI'ION qualifier instead of /BP2
to link nonoverlaid BASIC-PLUS-2 programs. !DESCRIPTION allows you to
use the defaults you specify at installation and with the BASIC-PLUS-2 BUILD
command. You cannot use these defaults when you use the !BASIC and IBP2
qualifiers with the LINK command. Instead, you must specify what you would
like to use each time you type the LINK command.
A BASIC-PLUS-2 program requires the resident library RMS (Record
Management Services) if any OPEN statements include the ORGANIZATION
clause or if the FMS (Forms Management System) qualifier is specified. See the
PDP-ll BASIC-PLUS-2 Language Reference Manual for more information.
ICC

Indicates that the files listed in the command are PDPll-C object files.
ICOBOL
IC81

Indicates that the skeleton and object files listed in the command are COBOL-81
files. (lCOBOL and ICS1 are equivalent qualifiers.)
The LINK command includes RMS if the COBOL program requires it.
IDIBOL

Indicates that the object files listed in the command are DIBOL object files.
IDMS
INODMS

This qualifier invokes the DMS variant of the Dibol compiler. The default is
INODMS.
IFOR

Indicates that the files listed in the command are FORTRAN-N object files.
IF77

Indicates that the files listed in the command are FORTRAN-77 object files.
With FORTRAN-77, you can use I/O channels 1-14 in your program. The
maximum record size for I/O is 512 bytes. See the PDP-ll FORTRAN User's
Guide if you need a larger record size.
If your program stores a format specification in an array, the size of the specification is limited by the size of an internal buffer, which is 64 bytes. See the PDP-ll
FORTRAN-77 User's Guide if your program requires more space.

The LINK command always includes RMS with this qualifier. You cannot specify
IOTS=RESIDENT with this qualifier. FORTRAN-77 does not have an Object

Time System (OTS) resident library.

Program Development

8-33

IRSX11

Indicates that the RSX-ll-based assembler (using the MACROIRSXll command)
on RSTSIE systems (MAC.TSK) produced the object files listed in the command.
The LINK command includes RMS only if you specify the IRMS qualifier. The
default for MACRO programs is !NORMS.
IRTH

Indicates that the RTll-based assembler (using the MACROIRTll command) on
RSTS/E systems (MACRO.SAV) produced the object files listed in the command.
The LINK command cannot use RMS with this qualifier.
ISTACK

Specifies the size of the executable program's stack space, in words. The /STACK
qualifier corresponds to the STACK=n option in the Task Builder Reference
Manual. See the RSTS / E Task Builder Reference Manual for further details.

Forms Management System Qualifier
/FMS
INOFMS

Indicates that you used the capabilities of the Digital Forms Management System
(FMS-ll) in your program. You can use this qualifier in conjunction with any of
the RSX-based language qualifiers. You cannot use it with the /FOR or IRTll
qualifiers.
IFMS=RESIDENT
IFMS=NORESIDENT

Specifies the FMS resident libraries FDVRDB and FDVRES. FDVRDB is the
FMS resident library that uses debug mode. FDVRES is the resident library
without debug mode.
Your system manager can decide to let these libraries belong to a cluster. Cluster
libraries are useful if you need to use more than one resident library. When they
are clustered, resident libraries share the same virtual address space in your
program. See the RSTS / E Task Builder Reference Manual for more information
on cluster libraries.
Without cluster libraries, FMS uses 4K words of virtual address space in your
program.
With cluster libraries, the LINK command dusters the FMS resident libraries
with an resident libraries being used. However, the LINK command will not use
cluster libraries with the /DIBOL qualifier.
/FMS=NORESIDENT specifies FMS without a resident library.

Debugging Qualifier
/DEBUG
I[NO]DEBUG
Invokes the appropriate debugging tool for a program that is written in COBOL81, DIBOL, or RSX-ll-based MACRO, and/or uses FMS. The debuggers invoked
with each qualifier follow. The default for each language is INODEBUG.
Note that when you use the /DEBUG qualifier with either IC8l or /DIBOL,
you must also use the /DEBUG qualifier when you compile the program. If
your program consists of a main program and one or more separately compiled
subroutines, and you want to use the debugging tool on the entire program, you
must compile each subroutine with the /DEBUG qualifier. You can mix sections
of your program that have been compiled using /DEBUG with sections that have
8-34

Program Development

not been compiled using /DEBUG. However, the debugging tools will be used only
in the sections compiled with /DEBUG.
For a COBOL-81 program, /DEBUG invokes the COBOL-81 Symbolic Debugger.
See the COBOL-81 RSTS / E User's Guide for information on the debugging
techniques used.
For a DIBOL program, /DEBUG invokes the DIBOL Debugging Technique
(DDT). See the CTS-500 DIBOL User's Guide for information on the debugging
techniques used.
If you are using FMS, /DEBUG invokes the debug mode of FMS in addition to
the other debugging tool. The debug mode of FMS is not available with COBOL81. See the FMS-ll/RSTS Reference Software Manual for information on the
debugging techniques used.

For an RSX-ll-based MACRO program, /DEBUG invokes the Octal Debugging
Tool (ODT). See the IAS/RSX-ll ODT Reference Manual for information on the
debugging techniques used.
For a FORTRAN or RTll-based MACRO program, /DEBUG has no meaning.
If you use /DEBUG and it cannot be applied, you receive the error message:
?Additional qualifier needed.

Description Qualifier
IDESCRIPTION

Indicates that the input file describes the process for linking the program,
including object files to link, the executable and/or map files to create, and
various other options. A description file is sometimes called a "task builder
command file."
If you program in BASIC-PLUS-2, you can specify /DESCRIPTION if you want
to use CMD and ODL Task Builder command files created by the BASIC-PLUS-2
BUILD command. Although /DESCRIPTION and IBP2 can perform the same
functions, unlike IBP2, you can tailor /DESCRIPTION to your system, generally
resul ting in a smaller program.
You cannot use this qualifier with any of the other LINK qualifiers. The default
file type is .CMD. You can specify only one input file with /DESCRIPTION.
Two general types of libraries may be available on your system:
•

Disk libraries (nonresident)

•

Resident libraries

A library is a collection of software modules in a single file. For disk libraries, the
Task Builder takes a copy of each routine that you reference in your program and
builds it into your program.
Your system manager defines libraries as resident (residing in computer memory)
so that more than one user can share them. Instead of building routines into
your program (as is done with disk libraries), you share a copy of the library. The
copy is resident in memory as long as you or someone else requires it.
Because they are shared, resident libraries occupy less space on the system. Your
program uses less memory and processor time: therefore; it runs faster. However,
because it is necessary to dedicate permanent physical memory for resident
libraries, your system manager might choose not to install them. By default,
the LINK command uses resident libraries if they are present on your system.
Otherwise, LINK uses the appropriate disk libraries.
Program Development

8-35

Because both resident and disk libraries take memory from your job, their use
affects the amount of memory that is available for your program to work in.
There is a 32K-word limit on job space that can not be set to any other value by
your System Manager if your program does not use I-and-D space. However, if
your program does use I-and-D space and you are on an I-and-D system, your
job space can be set between a 32K-word and a 64K-word limit by your System
Manager. If you are not on an I-and-D system and try to use I-and-D space you
will get an error message.
The BASIC-PLUS-2, COBOL-81, and RMS resident libraries can be clustered,
which means they share virtual address space in your program. In general, 24K
words of address space are available to your program when you use resident
libraries that are clustered.
To learn which libraries are available on your system, type SHOW LIBRARIES.
Note that the defaults are to use the resident libraries on your system. Therefore,
the following descriptions of the resident libraries are of interest only if you want
to change the defaults.

Address Space and Library Qualifiers
IOTS=RESIDENT
IOTS=NORESIDENT

Specifies the resident library for a language Object Time System (OTS). You can
use IOTS=RESIDENT only with BASIC-PLUS-2, COBOL-81, and DIBOL.
IOTS=NORESIDENT specifies the disk library for the language you are using.
IRMS
INORMS
IRMS=RESIDENT
IRMS=NORESIDENT
IRMS=SUPERVISOR
IRMS=USER

The IRMS qualifier specifies that RMS (Record Management Services) will be
used and is the default for all RSX-ll-based languages except MACRO. The
default is IRMS.
The SUPERVISOR or USER arguments use the specified resident library instead
of the disk library. For more information, see the previous section on Language
Qualifiers.
Two qualifiers, I[NO]EXECUTABLE and I[NO]MAP, control the output files
produced by the LINK command.

Output File Qualifiers
IEXECUTABLE[=file-spec]
INOEXECUTABLE

Indicates that you want the LINK command to produce an executable file. The
default is /EXECUTABLE. If you use the /EXECUTABLE qualifier, you can
specify a name for the executable file. If you omit the file specification, LINK
produces an executable file on the public disk structure (SY:) in your account with
a file name the same as the first file name in the input list. The default file type
is .TSK (for RSX-based languages) or .SAV (for RTll-based languages).
If you use the INOEXECUTABLE qualifier, the LINK command does not

produce an executable file. You must use the /MAP qualifier if you use
INOEXECUTABLE.

8-36

Program Development

IMAP[:file-spec]
INOMAP
Use the /MAP qualifier to indicate that you want the LINK command to produce
a memory map file. Use the INOMAP qualifier, or (since INOMAP is t.he default)
simply omit the qualifier if you do not want. a memory map file. You must specify
/MAP if you use the INOEXECUTABLE qualifier.

If you use !MAP, you can also assign a file specification for the memory map file.
If you omit the file specification, LINK produces map file on the same device, with
the same account and name as the executable file. The default file type is .MAP.

For RSX-based languages, specifying the !MAP qualifier produces the Task
Builder's memory map file. For RTH-based languages, the !MAP qualifier
produces the LINK.SAV memory map.

Overlay Qualifier
ISTRUCTURE
Indicates that you want to be prompted for an overlay structure (see the following
sections).

Program Development

8-37

8.10.1

Overlaid Linking
For overlays, do not specify the object files on the same line as the LINK command. Instead, simply specify the ISTRUCTURE qualifier (and other qualifiers, if
you want). The ISTRUCTURE qualifier causes LINK to prompt you for an overlay structure, described later in this chapter. Specify the object files in response
to these prompts.
The linking process includes routines in the executable file that are obtained from
appropriate libraries. You can choose the libraries from which these routines are
called. The choice depends on the qualifiers you use with the LINK command,
and whether you choose to use the resident libraries installed on your system.

8.10.1.1

When You Can Use ISTRUCTURE

If you wrote your program in BASIC-PLUS-2, DIBOL, or FORTRAN-77, you can
use the ISTRUCTURE qualifier with the LINK command to specify an overlay
structure. The ISTRUCTURE qualifier presents a dialogue that makes it easy to
work with overlays.
NOTE

Instead of using LINK and ISTRUCTURE, you can specify overlays
for these languages using the Overlay Description Language (ODL)
recognized by the Task Builder. The RSTS / E Task Builder Reference
Manual describes ODL. Using the ODL language is more complex than
using the ISTRUCTURE qualifier with LINK; however, it is also more
powerful.
COBOL programmers work with overlays within the language itself, by using the
segmentation facility of the COBOL compiler. The RSTS / E COBOL User's Guide
describes this facility. You do not need to use the ISTRUCTURE qualifier if you
are doing overlays in COBOL; the LINK command processes the skeleton files
output from the COBOL-81 compiler.
If you program in FORTRAN-IV or in MACRO under the RTll run-time system,
you must run the LINK.SAV program directly to specify an overlay structure.
The RSTS / E RTll Utilities Manual describes this program in detail.
When you use the ISTRUCTURE qualifier, you are prompted for an overlay
structure.
8.10.1.2

When Must You Use Overlays?

If your program is too large to fit in the space available, you must specify an
overlay structure for it. The discussion of the language qualifiers tell how much
space is available for programs written in the various languages when you use
the LINK command.
The easiest way to find out if your program is too large is to try to link it using a
language qualifier. If you get the error message ?Task has invalid memory limits,
your program is too large.

8-38

Program Development

8.10.1.3

What Are Overlays?

The best way to explain overlays is by example. Suppose your program consists
of a main program (caned MAIN) and two separately compiled subroutines (called
SUB1 and SUB2). Suppose further that MAIN calls both SUB1 and SUB2, and
that neither SUBl nor SUB2 contain any calls to separately compiled subroutines
or to MAIN. Figure 8--1 illustrates the call structure.
Figure 8-1:

Outlining the Call Structure

MAIN

(CAll SUB1)

SUB1

(CAll SUB2)

SUB2
MK-00574-01

You can specify an overlay structure such that MAIN is loaded when the program
is first run. When MAIN calls SUBl, the loading code built into MAIN during
the LINK process loads SUBI for execution. Then, when control passes back to
MAIN and it calls SUB2, SUB2 is brought in to memory overlaying SUB1.

Program Development

8-39

Figure 8--2 illustrates a simple overlay in memory. Note that SUBl and SUB2
do not call or use data from each other. This logical independence is necessary
for program pieces that overlay each other. In this example, calls or references to
data that are not currently in memory must be made from the root, which is the
MAIN program.
Figure 8-2:

A Simple Overlay in Memory

MAIN

SUB1
SUB2

(UNUSED MEMORY)
(UNUSED MEMORY)

TIME 1

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

TIME 2
MK-00575-01

8.10.1.4

Rules for Constructing Overlays
In general, you must structure an overlay tree so that calls or references to data
take place between overlay pieces that are on the same path. A path is any route
from the root of the structure that follows a series of branches to an outermost
piece of the tree. Calls or references to data cannot take place between pieces
that are along different paths.

8-40

Program Development

Consider the overlay structure shown in Figure 8-3. The structure shows pieces
that overlay each other as separate branches of a tree. Paths C and D would start
at the same virtual address, as would E, F, and G. The paths in this structure are
A-B-C, A-B-D-F, A-B-D-E, and A-B-D-G. Calls may be made between pieces on
any of these paths. However, F could not call G, E, or C; C could not call D, E, F,
or G, and so forth.
Figure 8-3:

Separate Paths in An Overlay Structure

FOUR PATHS:
A

II:!;1

I
I' .
I: I

B
l :1

I:
i
I: .

I1... ::-:-.·.-:-:-:.-:-:.7.::-:-.:.7j
_______ , :.

I : I

, '.i

I :

D
:1

: ~i

r--- - -- - - -- - --- -- ... -._'-'- ._._._._._.- '-j
I

I
I
I

MK-OOS78-01

When you use the /STRUCTURE dialogue to specify an overlay structure, you
must be careful to specify a structure that does not contain calls or references to
data that cross paths.
You must also be careful when you work with common areas in an overlay
structure. If a FORTRAN program and subprogram both define a common area
A, for example, where is the space for A to be allocated?

Program Development 8-41

Two examples are shown in Figure 8-4. The common block COMA is defined in
the pieces A2 and A21. The space for COMA is allocated in A2 because that piece
is closer to the root. The common block COMB, however, is defined in AO and BO.
These pieces are not on the same path, so the space for COMB is allocated in both
AO and BO. Note that AO and BO cannot communicate through COMB. When the
overlay containing BO is loaded, for example, any data stored in COMB by AO is
lost.
The /STRUCTURE dialogue that follows allows you to place COMB in the root of
the overlay structure, where it can be accessed by AO and BO properly.

Figure 8-4: Allocating Space for Common Areas

ROOT

-- I
,, --1BO
I
I
I
DEF COMB
, DEF COMB ,
'- ---1- ---!~- ~P=:E

,,,- -- -1---1
,
AO

1- -

1
1

-I

r -

1
1
I

A21

-1- - - -:
A2

DEF COMA

FOR COMB ALLOCATED
IN BOTH AO AND BO BECAUSE
THEY A RE ON DIFFERENT PATHS

I
1'--

SPACE FOR COMA ALLOCATED
IN A2 BECAUSE IT IS
CLOSER TO THE ROOT

A22

DEF COMA
MK-00591-01

8-42

Program Development

8.10.1.5

The ISTRUCTURE Dialogue

You can use the ISTRUCTURE qualifier with !F77, !BASIC, or !BP2 and the
IDIBOL qualifier. You cannot use ISTRUCTURE with the !FOR, IRTll, ICOBOL,
or IC81 qualifiers.
When you use ISTRUCTURE, the LINK command prompts you for an overlay
structure, as shown in the following example. The following example shows how
you would link the overlay structure shown in Figure 8-4:
$ LINK/F77/STRUCTURE <RET>
ROOT files: ROOT <RET>
Root PSECTS: COMB <RET>
Overlay: AO+ <RET>
Overlay: Al <RET>
Overlay: A2+ <RET>
Overlay: A2 <RET>
Overlay: A22 <RET>
Overlay: <RET>
Overlay: <RET>
Overlay: BO
Overlay: <RET>

ROOT files: Prompt
The first prompt presented is "ROOT files:". You respond to this prompt by typing
the object files that are to form the root of the overlay tree. In this case, there is
only one such file, named ROOT. If you have more than one such file, type them
all on one line and separate them with commas. If you need to continue, type a
hyphen (-) at the end of a line. The LINK command then displays the Continue:
prompt.
There is a limit on the number of characters you can type for root files; the
translated command line must be less than or equal to 127 characters.

Root PSECTS: Prompt
The next prompt presented is "Root COMMON areas:". If you are a high-level
language programmer, you will probably be interested in this question only if
you define a common area in two pieces of your program that overlay each other.
When you need to place such a common area in the root of the overlay structure,
where it can be accessed properly as a common area, you specify the name of the
common area in response to this question.
If you need to place more than one such common area in the root, you simply type
the common area names, separated by commas. To continue a line, type a hyphen
or a comma at the end of the line. If you type a comma, the LINK command
assumes you have finished one PSECT name and displays the Continue: prompt
for you to type more. Typing a hyphen lets you continue typing a PSECT name
you began on the previous line.

There is no limit to the number of program sections you can place in the root of
your program.

Overlay: Prompts
With further ISTRUCTURE prompts, you define the overlay structure beyond the
root section. You respond to the "Overlay:" prompts with file specifications for
object files to be linked. You use two symbols, the plus sign (+) and the comma (,)
to show how the files are to be overlaid. You can also use the exclamation point
(!) to include comments in the overlay dialogue.

Program Development

8-43

The Plus Sign (+) Symbol

Consider again the following LINK command to overlay the structure shown in
Figure 8-4:
$ LINK/F77/STRUCTURE <RET>
ROOT files: ROOT <RET>
Root COMMON areas: COMB <RET>
Overlay: AO+ <RET>
Overlay: Al <RET>
Overlay: A2+ <RET>
Overlay: A2 <RET>
Overlay: A22 <RET>
Overlay: <RET>
Overlay: <RET>
Overlay: BO
Overlay: <RET>

As shown, you indicate a branch in the overlay structure by ending a line with a
plus sign following the pieces from which the branch occurs. The next Overlay:
prompt is indented two places, to show that you are at the next overlay level. For
example, Al and A2 overlay each other; their addresses begin immediately after
the address taken by AO. Likewise, A2 and A22 overlay each other after A2.
Repeat this process to obtain the desired overlay structure. When you want to
return to the previous level in the overlay structure, press the RETURN key in
response to an Overlay: prompt.
Note that you can nest overlays to seven levels .
The Comma (,) Symbol

You use the comma (,) operator in an Overlay: prompt between files that are to
be concatenated in the overlay structure.
For example, consider the structure in Figure 8-5.

Figure 8-5:

Overlay Structure Using Concatenated Files

CNTRl

I
B1
B2
B3
B4
B5
A21

A22
MK-00589-01

8-44

Program Development

This structure is similar to the one shown in Figure 8--4, except that the files
B1, B2, B3, B4, and B5 are concatenated to form one overlay. Use commas to
separate files that are to be concatenated. The following example shows how to
use LINK with this structure:
$ LINK!F77!STRUCTURE <RET>
ROOT files: CNTRL <RET>
Root COMMON areas: <RET>
Overlay: AO+ <RET>
Overlay : Al <RET>
Overlay: A2+ <RET>
Overlay: A2 <RET>
Overlay: A22 <RET>
Overlay: <RET>
Overlay: <RET>
Overlay: BI,B2,B3,B4,B5
Overlay: <RET>

If you end a line with a comma, the LINK command assumes that you want to
continue concatenating files on the same branch. A Continue: prompt at the
same level displays for you to continue. For example, the following two lines are
the same as the Overlay: B1,B2,B3,B4,B5 line shown previously:
Overlay: BI,B2,
Continue: B3,B4,B5

8.10.2

The Memory Map File
As noted in the section on output file qualifiers, the /MAP qualifier causes the
LINK command to produce a memory map file. This file is a detailed listing of
the virtual addresses that your program occupies. You can use the /MAP qualifier
with any language qualifier.
There are two maps available, depending on the language qualifier you use. The
RSX-based languages produce a memory map that is described in the RSTS/E
Thsk Builder Reference Manual. The RTll-based languages produce a memory
map that is described in the RSTS/E RTll Utilities Manual.
You will probably be interested in the memory map only if you are working with
overlays and want to examine in some detail what the LINK command has done
for you.
Example 8-1 shows the first page of a memory map that the following LINK
command sequence produces.
$ LINK!STRUCTURE!MAP=TRY2!EXEC=TRY2 <RET>
ROOT Files: USER <RET>
Root COMMON areas: <RET>
Overlay: INTRO <RET>
Overlay: CRUNCH <RET>
Overlay: CHATR <RET>
Overlay: <RET>

Program Development

8-45

Example 8-1:
TRY2.TSK

Sample From A Memory Map File

Memory allocation map
TKB OB .006
22-JUN-90
13:42

PAGE 1

PARTITION NAME
GEN
IDENTIFICATION
16RE
TASK UIC
[1,196]
STACK
LIMITS: 001000 001777 001000 00512.
PRG XFR ADDRESS: 021154
TOTAL ADDRESS WINDOWS: 4.
TASK
EXTENSION
512. WORDS
TASK IMAGE SIZE
604B. WORDS
TOTAL TASK SIZE
6560. WORDS
TASK ADDRESS LIMITS: 000000 027447
R-W DISK BLK LIMITS: 000002 000036 000035 00029.
TRY2.TSK OVERLAY DESCRIPTION:
BASE

TOP

000000
022130
022130
022130
024320
025614

022127
023707
022577
024317
025613
027447

LENGTH

-----022130
001560
000450
002170
001274
001634

09304.
OOBBO.
00296.
01144.
00700.
00924.

USER
INTRO
CRUNCH
CHATR
R3PUT
R3UPDA

Example 8-1 shows that the memory map file is obscure in tenns of what you
specify in the LINK command. However, you can detennine some basic facts:

8.10.3

•

The size of the program is listed in the line headed "TOTAL TASK SIZE." In
this case, the program is 6560 words long.

•

The section headed TRY2.TSK OVERLAY DESCRIPTION shows the overlay
structure constructed by LINK. The first two columns of infonnation give
the starting address (BASE) and ending address (TOP) of each major overlay
piece in the structure. The next two columns (LENGTH) give the length of
each piece in octal and decimal number of bytes, respectively.

•

The original LINK command dealt with four files: USER, INTRO, CRUNCH,
and CHATR. You can see the overlay structure specified by the indentation
in the memory map: INTRO, CRUNCH, and CHATR overlay each other
following USER.

•

R3PUT and R3UPDA are overlay pieces from the disk library RMSLIB.OLB,
which the LINK command has placed in two special overlay structures called
co-trees. The RSTS / E Task Builder Reference Manual describes co-trees.

The Temporary Files Produced by LINK
When you use the LINK command with RSX-based languages, the LINK command processor creates two files for the Task Builder: a command file and an
ODL file. These files tell the Task Builder what to do in creating the executable
file and map file.
These files are left in your account. The .TMP file type indicates that they are
temporary files; that is, they are deleted from your account when you logout.
The command file is the same type of command file you would use with the
!DESCRIPTION qualifier. (These temporary files are not created if you use the
!DESCRIPTION qualifier.)

8-46

Program Development

8.11

RUN
Runs an executable file.

Format
RUN

file-spec

Prompts
Program: file-spec

Command Parameters
file-spec
Specifies an executable file.
If you do not specify a file type, the RUN command uses any of the following file

types, which correspond to executable files:
•

.BAC - A BASIC-PLUS compiled program. (See the BASIC command
description for more infonnation.)

•

.COM - A DCL command file. You may use the @ command on any .COM
file, but to use the RUN command, the executable bit (64) must be set.

•

.SAV - A "save image" file, which runs under the RTll run-time system.
(For example, a FORTRAN-IV executable file is a save image file.) Save
image files are produced by LINKIFOR or by LINKlRTll.

•

.TSK - A "task" file, which runs under the RSX run-time system (or a
derivative of RSX). See the LINK command description and the RSTS / E Task
Builder Reference Manual for more infonnation.

Your installation may have a different set of executable file types, depending on
the run-time systems your system manager has installed.
If you omit a file type, the RUN command searches the specified directory for

a file having each runnable file type. The order of the search depends on your
installation. For example, at some installations the RUN command might search
for a .TSK file first. If that fails, RUN then searches for a .BAC file, then a .SAV
file. However, another installation might search for file types in a different order.
You cannot use wildcard characters in the file specification, and you must specify
a file name.
Examples of using the RUN command are:
$ RUN $SYSTAT

This example runs a system program named SYSTAT. The dollar sign ($ in
$SYSTAT) indicates the directory [1,2], which is the system library.
$ RUN BANKER

This example runs a user program named BANKER in your account on the public
structure.

Program Development

8-47

Appendix A

Del Error Messages

This appendix lists some DCL error messages that you may encounter when
using RSTSIE. Section A.2 also indicates the probable cause of the error in your
use of a command or system program.
If you perfonn DECnetlE operations, you may receive messages that are
described in DECnetIE documentation but not in this appendix. In addition, the
utility programs that support DeL can produce messages not all of which are
listed here. Those messages are listed in the RSTS / E Utilities Reference Manual.

A.1

Special Characters Used in Error Messages
The question mark (7) and percent sign (%) characters preceding a message
indicate its severity. A single question mark precedes nonfatal error messages,
which means that the command failed to do what you asked but you can continue.
For example:
?Too many parameters

In this case, the command failed because you included too many parameters.
A double question mark precedes severe error messages, which means that the
command failed to do what you asked and you cannot continue. For example:
??Fatal system I/O failure

By contrast, the percent sign identifies a warning message, which means that the
command may not have worked as you intended. For example:
%Logical name has not been assigned

In this case, the MOUNT command worked but no logical name was assigned to
the device.
Informational messages do not have a preceding character; they provide extra
details about the effects of a command. For example:
Queue file being reorganized - please wait ...

This message infonns you that, as a result of your command, the file is being
reorganized.
Angle brackets «
» surrounding text indicate a place holder for what the
system inserts when an error message occurs.
Section A.2 lists the DCL error messages that you can get when using RSTSIE
and the probable cause.

Del Error Messages

A-1

A.2 Del Error Messages
?Account or device in use

Explanation: The device cannot be mounted or dismounted because it
is open or has one or more open files. This error can also occur when a
user attempts to access a non-shared disk from a job other than the one
that mounted the disk.
?Additional argument required

Explanation: You did not specify enough arguments in the DCL
function.
?Additional qualifier required

Explanation: You did not include a qualifier required in a command.
?Ambiguous keyword

Explanation: You abbreviated a keyword too short; DCL cannot
distinguish it from other keywords.
?Argument not allowed

Explanation: You used an argument with a qualifier that does not
accept one.
?Argumentrequired

Explanation: An argument was not supplied with a qualifier which
required one. For example, ISINCE=, without an argument, would
generate this error.
The user did not supply an argument to a DCL function that required
one.
??Bad directory for device

Explanation: The directory of the device referenced is in an unreadable
format. For example, the tape format differs from the format you
specified with the MOUNT command.
?Can't access terminal <error text>

Explanation: An error occurred while attempting to access the terminal
to send the setup file to.
?Can't find file or account

Explanation: Either the account or file does not exist, or you typed a
file specification incorrectly.
?Can't mount a private disk as public

Explanation: You tried to mount as public (using the MOUNT
command's /PUBLIC qualifier) a disk that was initialized as private.
?Can't rebuild disk because device is write protected

Explanation: A privileged user attempted to rebuild a disk (using
the MOUNT command's /REBUILD qualifier), and the drive is write
protected. Therefore, the mount and rebuild operations fail.

A-2

Del Error Messages

?Channel already open

Explanation: The channel specified in the OPEN command already has
a file open on it. You must either specify a different channel number or
use the CLOSE command to close the channel first.
?Channel not open for input

Explanation: The channel specified by a READ command is either not
open or open for writing only.
?Channel not open for output

Explanation: The channel specified by a WRITE command is either not
open or open for reading only.
?Command not found

Explanation: The requested command is not in the recall buffer.
?Command not installed

Explanation: You typed a DCL command that has not been installed
on your system. The DCL keyboard monitor could not find the utility
needed to carry out your command. This message can also be displayed
if you type a remote file specification in a command that allows remote
file specifications, but your system does not have DECnetlE.
?Command too long

Explanation: The length of the command, including continuation
lines, exceeds the maximum allowed for the command. Or, the length
of the translated command string exceeds the maximum allowed for the
command.
For example, this message occurs with the LINK command in either of
two cases:
•

The text you typed in response to the $ prompt and the Files: or
Root files: prompt added up to more than 127 characters after
translation.

•

With LINK/COBOL, the text was longer than 80 characters after
translation.

%Command will proceed as requested

Explanation: The user's symbol tables could not be written out to the
DCL work file, but the command will be processed. The user may be
over quota. Corrective action should be taken before the user continues
processing.
?Comma required

Explanation: A DCL function required two or more arguments and
they were not separated by a comma.
?Confiicting arguments

Explanation: Two arguments are considered to conflict within a
qualifier argument list. For example, you cannot specify both !BRIEF
and !RESET with the SHOW ACCOUNT command.

Del Error Messages

A-3

?Confiicting elements

Explanation: You specified qualifiers or parameters in a command that
do not agree in type (for example, a print qualifier with a batch server).
?Confiicts with terminal setting IAUTOBAUD

Explanation: The terminal is set to IAUTOBAUD on the SET
TERMINAL/ANSWERBACK command.
?Conflicts with terminal setting IANSWERBACK

Explanation: , The terminal is set IANSWERBACK on the SET
TERMINAL/AUTOBAUD command.
?Conflicts with terminal setting /HOST_SYNC

Explanation: The terminal is set /HOST_SYNC on the SET
TERMINALIRESUME=ANY command.
?Conflicts with terminal setting IRESUME=ANY

Explanation: The terminal is set IRESUME=ANY on the SET
TERMINAL/HOST_SYNC command.
?Controller disabled or inoperative

Explanation: The LAT device is disabled on a STOPILAT, STARTILAT
or SHOW COUNTERSIDEVICE command.
?CPU limit exceeds queue's maximum

Explanation: You specified a ICPU_LIMIT value in a SUBMIT
command larger than the maximum allowed for the queue.
?Data error on device

Explanation: One or more characters may have been transmitted
incorrectly due to a parity error, bad punch combination on a card, or
similar error.
?Data error or incorrect density

Explanation: This message occurs for one of the following reasons:
•

You specified the incorrect density.

•

You did not specify a density, but your system's default density is
incorrect for the tape.

•

The data on the tape is damaged.

•

The tape drive is faulty.

To correct the problem, specify the correct density. If that does not solve
the problem, try mounting the tape on another drive.
?Default macro for KB<n>: does not exist

Explanation: The SET TERMINALIINQUIRE command could not
recognize the terminal and there was no default macro specified for
this keyboard in the default file, TERDFL.SYS. You should supply a
default macro for the keyboard. Until that is done, the keyboard's
characteristics have to be set manually.

A-4

Del Error Messages

?Device does not exist

Explanation: The device name you specified does not exist on your
system.
%Device hung or write locked
%Dismount win proceed as requested

Explanation: You attempted to dismount a disk that has been
physically dismounted. However, the logical dismount win succeed.
?Device hung or write locked

Explanation: Check the hardware condition of the device requested.
Possible causes of this error include a line printer out of paper or a disk
drive being offline.
%Device in use

Explanation: You specified INOSHAREABLE in an INITIALIZE/SERVER
command; however, the print server's device is not available or no
pseudo keyboards are currently available for the batch server. PBS
allocates the device as soon as it becomes available.
?Device is not a terminal

Explanation: A device other than a terminal was specified. Only
specify keyboards.
?Device must be disk

Explanation: You specified a file on a nondisk device, where a disk
device is required.
?Device not available

Explanation: The specified device exists on the system, but an attempt
to allocate or use it is prohibited for one of the foHowing reasons:
..

The device is currently reserved by another job .

The device requires privilege for ownership and you do not have the
necessary privilege.

The device or its controller has been disabled by the system manager.

The device is a keyboard line for pseudo keyboard use only.

?Device not file-structured

Explanation: An attempt was made to access a device, other than a
disk drive or magnetic tape drive, as a file-structured device.
?Device not write protected

Explanation: You specified the INOWRITE qualifier when you tried to
mount a tape, but the device is not write protected. Write protect the
device by removing the plastic ring from the tape hub.
?Device offline

Explanation: You tried to use a tape or disk, but the device is off line.

Del Error Messages

A-5

%Device write protected

Explanation: The tape or disk is protected against write access.
Therefore, you can only read files on the device, but cannot write
(perform output) to the device. If you want to write to the device. first
write enable the device, next dismount the device, and then mount the
device again.
?Device write protected

Explanation: You requested write access to a device that is write
protected. Write enable the device and then retype the command.
?Directory does not exist

Explanation: A file specification indicates a directory that does not
exist on the particular disk. Or, a wildcard directory specification failed
to produce a match on the disk specified. This error can occur only with
disk files.
??Disk error during swap

Explanation: A hardware error occurs when your job is swapped
into or out of memory. The contents of the job area are lost, but the
job remains logged in to the system and returns to DCL. Report such
occurrences to the system manager.
Disk is being rebuili - wait ...

Explanation: This informational message is displayed when a user
attempts to rebuild a disk. The disk is logically mounted when the
rebuilding operation is complete.
%Disk is restricted and mounted non-shared, read-only

Explanation: A user specified INOREBUILD (to suppress rebuilding)
in the MOUNT command and the disk was dirty. Therefore, the disk
is mounted non-shared and restricted, and read-only access is granted.
("Restricted" means that access is allowed only to users with DEVICE
privilege.)
?Disk is mounted non-shared

Explanation: This message can be displayed for one of two reasons:
..

A user with MOUNT privilege attempted to dismount a private or
public disk that was mounted as non-shared by specifying !PUBLIC
in the DISMOUNT command.

A user without MOUNT privilege attempted to dismount a private
disk that was mounted as non-shared by specifying /PUBLIC in the
DISMOUNT command.

Therefore, the dismount fails. In both cases, the requests to mount and
dismount are from different jobs.

A-6

Del Error Messages

?Disk is mounted private or non-shared

Explanation: This message can be displayed for one of two reasons:
•

A user with MOUNT privilege attempted to dismount a private or
public disk that was mounted as non-shared (by the same job) or
private by specifying /PUBLIC in the DISMOUNT command.

•

A user without MOUNT privilege attempted to dismount a private
disk that was mounted as non-shared (by the same job) or private by
specifying /PUBLIC in the DISMOUNT command.

Therefore, in both cases the dismount fails.
?Disk is mounted public

Explanation: A user with MOUNT privilege attempted to dismount a
public disk that was mounted as public, without specifying /PUBLIC in
the DISMOUNT command, so the dismount fails.
%Disk is mounted read-only

Explanation: This warning occurs if you do not specify either read or
write access (INOWRITE or /WRITE) when mounting a disk initialized
as read-only. Therefore, you are granted read access only.
?Disk needs rebuilding but device is write protected

Explanation: A privileged user attempted to mount a dirty disk (and
did not specify IREBIDLD or /NOREBUILD), but the device is write
protected and the automatic rebuilding cannot be performed. Therefore,
the mount fails.
?Disk needs rebuilding but you do not have the necessary privilege

Explanation: This message occurs when a user without MOUNT
privilege tries to mount a private disk that was not logically dismounted.
The system manager can correct the situation by rebuilding the disk.
?Disk pack is locked out

Explanation: This message occurs when a user without DEVICE
privilege attempts to open files on a disk restricted to users with
DEVICE privilege.
?Disk pack is not mounted

Explanation: The DISMOUNT command was attempted, but the disk
pack was not mounted on the specified disk drive.
??Disk pack mount error

Explanation: Fatal disk mounting error. The disk is corrupt and
cannot be successfully mounted with the MOUNT command.
?Division by zero

Explanation: The expression specified by the user attempted to divide
by zero.
?Dollar signs are not allowed in user logical names

Explanation: You included dollar signs in the logical name on the
ASSIGN command. Dollar signs are only allowed in system logical
names.
Del Error Messages

A-7

?Do not specify file name or type

Explanation: This message can occur with the first parameter of
the ASSIGN command. Remember to use a space between the first
parameter (the string you assign) and the second parameter (the name
you assign it). For example, "ASSIGN DR3: X", not "ASSIGN DR3:X".
?End of file on device

Explanation: A READ command was attempted but no data was
available. Either the file is empty or you attempted to read past the last
record in the file.
?Equal sign required

Explanation: You used a qualifier that requires an argument, but you
did not give an argument.
?Error in forms definition <forms-name>
<error message>

Explanation: An error, as the error message in the second line
describes, was discovered in the forms definition displayed.
You used a qualifier that requires an argument, but you did not give an
argument.
?Error number <nn>(message text is not online)

Explanation: An I/O error occurred while the system was attempting
to retrieve an error message. Possible causes could be that the device
containing the system error file (ERR.SYS) is off line, or that the system
error file contains a bad block.
This is a serious error, and should be reported to the system manager.
?Error opening PBS file <file-spec>
<error message>

Explanation: An error, as the error message in the second line
describes, occurred opening the PBS file indicated.
<error text> opening setup file <filename>

Explanation: An error occurred while trying to gain access to the setup
file.
<error text> opening speed file

Explanation: An error occurred while trying to gain access to the speed
file. The speed is not set and the rest of the command is executed.
<error text> opening/reading default file

Explanation: An error occurred while processing the default file.
<error text> reading setup file <filename>

Explanation: An error occurred while processing the setup file.
<error text> reading speed file

Explanation: An error occurred while processing the speed file. The
speed is not set and the rest of the command is executed.

A-a

DeL Error Messages

??Fatal system I/O failure

Explanation: An I/O error has occurred on the system level. The
results of the last command are unpredictable. This error is caused by a
hardware condition. Report such OCCUITences to your system manager.
?File does not exist

Explanation: This message occurs for one of the following reasons:
..

An input file that must be present is not present.

4»

A wildcard file specification does not match any files.

<\>

A file is not accessible because of its assigned protection code.

?File name required

Explanation: A file specification you typed does not include a file name,
but one is needed.
?File specification required

Explanation: This error occurs if you specify node:: without a file
specification (except with DIRECTORY). It also occurs if you have two
commas with no characters between them in a file specification list.
?Files cannot be on different nodes

Explanation: This message occurs with network operations. Each
input file specification you include in a network command must be on
the same node.
?FHe must be disk

Explanation: The file specified on the OPEN command was not a disk
file.
?Fonn <fonn-name> does not exist

Explanation: The form name you specified was not defined by the
system manager. See your system manager to find out what form names
are available.
?Forms Definition File does not exist

Explanation: The forms definition file, PBS$:FORMS.SYS does not
exist.
?Forms not defined [for server <server-name>J

Explanation: The forms you specified could not be found in the fonns
definition file.
?Identification string contains invalid characters

Explanation: A node identification string was specified which did not
contain alphanumeric characters.
?Identification string too long

Explanation: A node identification string was specified which exceeded
64 characters.

Del Error Messages

A-9

%ID label ignored

Explanation: You mounted a tape in DOS format and specified an ID
label. Identification labels are not encoded on DOS tapes; therefore, the
label you specified is not recognized by the MOUNT command.
%ID label should be specified when you mount an ANSI tape

Explanation: You mounted a tape in ANSI format, but did not specify
the tape identification label. Digital recommends that you specify the
identification label. Thus, the MOUNT command can verify that the
tape you selected has been mounted.
?ID labels don't match

Explanation: The identification label you specified does not match the
identification label encoded on the tape. To correct the problem, specify
the correct identification label. If you do not know what identification
label is encoded on the tape, you can omit the ID label from the MOUNT
command.
?Illegal byte count for I/O

Explanation: The range of memory starting at the load address given
is not available. Refer to the memory status report of a display program
(SYSTAT or DISPLY) to select an available range of memory.
?Illegal filename

Explanation: The file name given in the command contains characters
other than alphabetic or numeric characters.
?Illegal switch usage

Explanation: A eeL command contains an error in an otherwise valid
CeL switch (qualifier). For example, you cannot use the /SI:n switch
without a value for n or a colon; or you cannot specify more than one of
the same type of eCL switch.
?megal value <n>

Explanation: The swap file number specified is not 0, 1, or 3. (The
swap file 2 already exists on the system disk and need not be added.)
?Impossible density for this device

Explanation: You tried to mount or initialize a tape, but specified a
density not available on the tape drive you used. To correct the problem,
use another drive or specify a different density.
?Incorrect density

Explanation: You specified a density different from the tape's density.
This message appears only if you are using a tape drive that determines
the tape's correct density. Therefore, you do not need to specify the tape
density with the MOUNT command.

A-10

Del Error Messages

?Incorrect density or uninitialized tape

Explanation: This message can occur for the following reasons:
•

You tried to mount a tape that had not been initialized.

•

You specified an incorrect density.

•

You did not specify a density, and your system default density was
incorrect for the tape.

If the tape has not been initialized, use the INITIALIZE command.
Otherwise, specify the correct density.
?Invalid account

Explanation: The account specified was not valid either containing
invalid characters (for example, [1\1\1\]) or an invalid format (for example,
[1,2345]).
?Invalid argument

Explanation: This error can occur when you use a qualifier in the form
/qualifier=argwnent. The qualifier you used is spelled properly, and the
equal sign (=) or colon (:) is present; however, the argwnent is either
missing or syntactically invalid.
This error message is displayed when there is no more specific messages
to describe the syntax error.
?Invalid at interactive level

Explanation: You specified a command that is invalid at the interactive
level. (For example, GOTO LABEL)
?Invalid BATCH command

Explanation: Although the command is valid in interactive mode, the
command is not a valid BATCH command because it implies or requires
interaction with the user. (For example, INQUIRE, SET NODATA)
?Invalid CCL command

Explanation: You used the CCL prefix followed by a command that is
not installed as a CCL command on your system.
?Invalid channel number

Explanation: The I/O channel number specified was invalid. Channel
numbers can range from 1 to 13 on OPEN, READ and CLOSE
commands, and from 0 to 13 on WRITE commands.
?Invalid character

Explanation: You typed an invalid punctuation character.
?Invalid characters in service name

Explanation: The service name does not contain alphanumeric
characters on a DELETE/SERVICE command.
?Invalid command

Explanation: The command name you gave is not a DCL command,
and is not defined on your system as a CCL command. Or, the line
begins with a punctuation character rather than with a keyword.
Del Error Messages

A-11

?Invalid date

Explanation: A date either has improper syntax, represents a
nonexistent date (for example, 30-Feb), or represents a date before 1970
or after 1999.
?Invalid density <n>

Explanation: You tried to mount or initialize a tape, but specified a
density other than 800 or 1600 bpi. The n is the density you specified.
?Invalid device

Explanation: The device specified could not be found in the list of
standard devices or in the user-defined macros. Specify a valid device.
?Invalid entry name

Explanation: The entry name you specified is invalid.
?Invalid expression

Explanation: This covers a range of expression problems. The most
common of these is an expression ending in an operator without
supplying a second operand (for example, A = B *).
?Invalid Ethernet Device

Explanation: The device-name is not valid on a SHOW
COUNTERSIDEVICE command.
?Invalid file specification

Explanation: A local file specification has improper syntax.
?Invalid fill factor

Explanation: A fill factor was specified that was less than 0 or greater
than 6.
?Invalid form definition

Explanation: The definition of the specified form contains an invalid
keyword or keyword argument.
?Invalid form name

Explanation: The form name you specified is either longer than six
characters or consists of one or more nonalphanumeric characters.
?Invalid function name

Explanation: The function name specified after F$ is invalid. The
minimum abbreviation point is not met for the function (for example,
F$LE is not valid because of F$LEFT and F$LEN).
%Invalid keyboard numbers <n , n> in default file

Explanation: The numbers you specified in the default file were less
than 0, greater than 127, or the first number of the range is greater
than the second number of the range.

A-12

Del Error Messages

%Invalid keyboard nwnbers <n , n> in speed file

Explanation: The nwnbers you specified in the speed file were less
than 0, greater than 127, or the first number of the range is greater
than the second number of the range.
?Invalid keyword

Explanation: The keyword is not recognized. This error occurs with
keywords that are not qualifiers and are not command names. (For
example, it can occur with the options of SET and SHOW, and with
qualifier values that are keywords.)
?Invalid label

Explanation: The label specified in the command procedure contains
invalid characters.
?Invalid node name

Explanation: The node name field of the file specification contained
invalid characters.
?Invalid operator

Explanation: The operator you specified in the expression is not a
defined logical, arithmetic, string, arithmetic comparison or string
comparison operator.
?Invalid PPN

Explanation: The project-programmer nwnber (PPN) you specified
does not have valid syntax.
?Invalid print device

Explanation: The device you specified is not a valid print device
because it is not a line printer or terminal.
?Invalid private delimiter

Explanation: The delimiter you specified was not in one of the correct
formats.
?Invalid qualifier

Explanation: The qualifier keyword is not valid in the command you
typed. (This message may indicate an error in spelling or typing.)
?Invalid qualifier for disk

Explanation: This message occurs when you specify an invalid qualifier
for disks. For example, IFORMAT=ANSI (applies to tapes).
?Invalid qualifier for tape

Explanation: This message occurs when you specify an invalid qualifier
for tapes. For example, /PRIVATE (applies to disks).
?Invalid queue name

Explanation: The queue name you specified is invalid.

Del Error Messages

A-13

?Invalid server name

Explanation: The server name you specified is invalid.
?Invalid speed

Explanation: The speed specified was not a valid speed for the interface
of the terminal. Only specify speeds that the interface supports.
?Invalid symbol name

Explanation: You specified a symbol name that contains invalid
characters.
?Invalid time

Explanation: A time either has improper syntax or represents a
nonexistent time (like 25:00 or 13:00PM).
?Invalid width

Explanation: You specified a width that was less than 1 or greater
than 254.
?Invalid with network file specification

Explanation: You gave a network file specification in one of the
commands that accepts them (RENAME, COPY, and so on), but you also
gave a qualifier that can be used only with local operations.
?I/O to detached keyboard

Explanation: This message can result from one of two actions:
•

You tried to perform I/O with a terminal line that is used for dialup
terminals, but nobody was dialed in.

•

Your job became detached (perhaps because you were dialed in and
your line was later hung up) and then tried to perform I/O with the
terminal.

The second situation either causes the job to hibernate or causes this
error condition, after which the job hibernates. You see this message
when you subsequently attach to the job.
?K.eyword required

Explanation: You typed nonalphanumeric characters when a keyword
is needed instead. (If you type alphanumeric characters without a valid
keyword, you receive the error message, ?Invalid keyword.)
?Label already defined

Explanation: A label was defined more than once in an indirect
command procedure.
?Label too long

Explanation: The label you specified in the indirect command procedure was longer than 255 characters.
?LAT already started on this line

Explanation: A LAT service was already enabled when you attempted
to open another LAT line using the STARTILAT command.
A-14

Del Error Messages

?LAT not started

Explanation: A STOPILAT command has been issued and there is no
active LAT service enabled.
?Log file already open

Explanation: A log file was already currently open when you attempted
to open another log file using the OPEN/LOG_FILE command.
?Log file not currently open

Explanation: You attempted to enable or disable logging using the SET
LOG_FILE command, and a log file did not exist.
?Log file print queue closed

Explanation: The print queue required for a SUBMIT command's
/LOG_QUEUE qualifier is closed or marked for deletion. Use a different
print queue for the log file.
?Log file print queue does not exist

Explanation: The print queue you specified with the /LOG_QUEUE
qualifier in a SUBMIT command does not exist. Specify a different
queue.
%Logical name not assigned

Explanation: This warning can be displayed for one of two reasons:
•

You had INSTAL privilege and specified a logical name that was not
assigned as a system logical. (This means that neither the alternate
logical name nor the pack-id label were assigned.)

•

You did not have INSTAL privilege and specified an alternate logical
name when attempting to mount a disk.

The mount succeeds in both cases, but the logical name is not assigned.
?Logical too long

Explanation: Logical name was over 15 characters.
?Magtape record length error

Explanation: When performing input from magnetic tape, the record
on tape was found to be longer than the buffer designated to handle the
record.
?Magtape select error

Explanation: When access to a magnetic tape· drive was attempted, the
selected unit was found to be off line. This error can occur when you
transfer data to or from a tape.
?Map or executable file required

Explanation: With LINK, you specified INOEXECUTABLE and did not
specify a map file.

Del Error Messages A-15

??Maximum memory exceeded

Explanation: This is a nonrecoverable RSTSIE error caused by the
following conditions:
..

While loading a program into memory, the job's private maximum
memory size was reached.

While executing a program, the system required more memory for
string or I/O buffer space, and the job's private maximum memory
size or the system maximum was reached.

?Maximwn nwnber of LAT lines already enabled

Explanation: The nwnber of LAT lines on the Ethernet portal has
reached the limit on a STARTILAT command.
?Missing closing apostrophe

Explanation: The user did not specify matching apostrophes (' ... ')
when requesting apostrophe substitution.
?Missing closing bracket

Explanation: This error can occur in a local or remote file specification.
There is a left bracket ([) or left angle bracket «), but no right bracket
(]) or right angle bracket (».
?Missing closing quote

Explanation: A quotation mark COO) is not matched with another
quotation mark. (This error can occur in remote file specifications.)
?Missing device or file name

Explanation: The command must contain either a device specification
or a device and file name specification. If you use the /SI:n switch, a file
name must be present.
?Missing open parenthesis

Explanation: You did not specify an open parenthesis [(] when one was
expected.
%More than 16 speeds specified for <terminal>

Explanation: While processing the TERSPD.SYS file, a terminal was
found that had more than 16 speeds specified. Only the first 16 speeds
are used.
?Narne or account now exists

Explanation: You attempted either to COpy to or RENAME an
existing file. This error can occur with RENAME if you do not specify
!REPLACE and the output file already exists. It can also occur with
COPY if you specify /NOREPLACE and the output file already exists.
?Network node names must be the same

Explanation: Different node names were specified on input file
specifications.

A-16

Del Error Messages

?No active LAT sessions [on server-name]

Explanation: There is no active session on the specified server on a
"SHOW SESSION [server-name]" command.
?No active servers

Explanation: A terminal server name has been entered and the
specified server is not active.
?No buffer space available

Explanation: The system is overloaded and cannot complete your
command because small buffers are currently unavailable. Try the
command again later.
%No commands to recall

Explanation: RECALL/ALL command was issued when no commands
were available for recall. Check that Command Line Recall is enabled
by using the SHOW TERMINAL command.
?No channels available

Explanation: A DCL 110 or command file channel is not available.
You may have issued an OPEN or at (@) command, but a channel is not
available. Use the CLOSE command to close one or more files or use the
EXIT command to unnest a level and try again.
?No default (Print,Batch) queue

Explanation: You did not specify a queue name with the PRINT or
SUBMIT command, and no default queue exists.
?No default print queue for log file

Explanation: The fLOG_QUEUE qualifier in a SUBMIT command
was specified without an explicit queue name; however, no default print
queue exists. Use an explicit queue name for the log file.
?No file name or type permitted

Explanation: A device:ppn syntax was expected and you supplied a full
file specification which included either a file name or type.
?No known terminal servers

Explanation: All terminal servers are requested to be displayed and
none exists on a "SHOW TERMINAL_SERVERILAT" command.
?No LAT Node characteristics set

Explanation: The Ethernet device has not been specified on a
STARTfLAT command.
?No LAT services currently offered

Explanation: No LAT services are available on a SHOW
TERMINALILAT command.

Del Error Messages

A-17

?No logins

Explanation: This message can be displayed when you try to log in, for
one of two reasons:
@

The system is full, so it cannot accept additional users.

The system manager has disabled logins.

(Possibly, logins are disabled because the system will be shut down
shortly.)
?Non-executable file

Explanation: This error occurs if the file you are trying to run is a
source file; for example, .BAS. You need to compile and link the file
before you run it. (Note that an executable file includes the value 64 in
its protection code.)
?Non-printable character

Explanation: You typed a control character.
??Non-res run-time system

Explanation: This message generally indicates hardware problems.
For example, the run-time system referenced has not been loaded
into memory and cannot be loaded for some reason, and is therefore
nonresident.

%No owner rights to (print, batch) entry <entry-spec>

Explanation: The entry shown is not your own and you do not have
sufficient privilege to delete it or modify it.
?NO prefix not allowed

Explanation: You used the INO prefix improperly.
%No (Print,Batch) entry <entry-spec> found

Explanation: No entries matching the entry-spec you specified in a
SHOW ENTRY or SET ENTRY command were found.
%No (Print,Batch) queue <queue-name> found

Explanation: No queues matching the queue name you specified in a
SHOW QUEUE or SET QUEUE command were found.
%No (Print,Batch) server <server-name> found

Explanation: No servers matching the server name you specified in a
SHOW SERVER or SET SERVER command were found.
?No qualifiers allowed

Explanation: The user specified a qualifier on a command that does
not allow qualifiers.
?No (read,write,or read/write) access to file <file-spec> [by owner]

Explanation: The file specifications in a PRINT or SUBMIT command
requires access that you or the specified owner does not have.

A-iS

DeL Error Messages

?No room available for new LAT Service

Explanation: The system does not have enough resources to add
another LAT service on a CREATE/SERVICE command.
?N0 room for user on device

Explanation: In attempting to create a file on a device, or write
information to a device, you exceeded some size limit. If it was a
nondisk device, this error indicates that the device was full. If it was a
disk device, this error indicates one of three conditions:
•

The disk as a whole is full.

•

You attempted to create a contiguous file, and there is not enough
space on the disk. (However, the /CONTIGUOUS qualifier for the
commands COPY and CREATE produce only a warning if there is
not enough contiguous space.
If you attempted to create a contiguous file but were unable to, try to
create a noncontiguous file of the same size. If you are able to create
a noncontiguous file then you can conclude the problem is lack of
contiguous space.

•

If you have eliminated the first two conditions, then the disk
directory has reached its capacity. This capacity is independent of
your disk quota. The number varies, depending on the directory
cluster size that the system manager assigned when creating the
directory and the sizes of the files in it. Large files fill up a directory
faster than small files, especially if the large files have small cluster
sizes. Also, if the directory itself has a large cluster size, it can hold
more files and larger files.

?No run-time system

Explanation: This error can occur if the program you are trying to run
requires a run-time system that is not installed.
?Not a valid device

Explanation: The device name that you gave is invalid for any of the
following reasons:
•

It is not assigned as a systemwide or user logical name.

•

It is not a physical device name of any device that is installed on
your system.

•

The device name is valid, but not with this command. For example,
"INITIALIZE TT:" (you cannot initialize a terminal).

?Not a valid LAT line

Explanation: The server specified is not valid on a "SHOW SESSIONS
server-name" command.
?Not enough available memory

Explanation: An attempt was made to load an executable program that
is too large to run, given the job's private maximum memory size. Either
the program must be allowed to expand above a private maximum
memory size, or the system manager must increase the job's private
memory size maximum to accommodate the program.

Del Error Messages

A-19

?Not enough small buffers to create the logical terminal

Explanation: The system does not have enough small buffers to add
another logical terminal on a CREATE/PORT command.
?Number not in range dow> or <high>

Explanation: You typed a number where one is allowed, but the
number is not in the valid range. The valid range is from <low> to
<high>.
?Nwnber too big

Explanation: You typed a number where one is allowed, but the
number is too large. Refer to the command description to find out the
largest acceptable value.
?Number too small

Explanation: You typed a number where one is allowed, but the
number is too small. Refer to the command description to find out the
smallest acceptable value.
?Pack-id labels don't match

Explanation: The identification code for the specified disk pack does
not match the identification code already on the pack. This message can
occur when you try to mount or dismount a disk.
?Page limit exceeds queue's maximum

Explanation: You specified a /PAGE_LIMIT value in a PRINT
command larger than the maximum allowed for the queue.
?Parameter out of range

Explanation: Numeric parameter was not in the range of accepted
values.
?Parameter or argument too long

Explanation: A file specification, text string, or qualifier argument
exceeded 127 characters.
?Port [port-name] does not exist

Explanation: The device specified is not a LAT port on a SHOW PORT
command. Port names must be in the format "KEn".
?PPN does not exist

Explanation: The project-programmer number (PPN) you specified as
part of the job specification does not exist.
?PPN needed

Explanation: The command you typed requires that a PPN be specified.
Previous logical name assignment replaced

Explanation: An informational message to indicate that an ASSIGN
command redefined a previously defined user logical.

A-20

Del Error Messages

(Print, Batch) entry <entry-number> <entry-spec> created
Explanation: Acknowledgment message to PRINT or SUBMIT
command.
(Print, Batch) entry <entry-spec> - <error text>
Explanation: For SET ENTRY, indicates that an entry was not
modified for the reason stated in the error text.
?PrintIBatch Services already started
Explanation: You issued the START/QUEUEIMANAGER command;
however, the PrintlBatch Services (PBS) package is already started.
?PrintlBatch services not running
Explanation: You issued a command that requires action by PBS;
however, the package is not running.
(Print,Batch) queue <queue-name> assigned to server <server-name>
Explanation: Acknowledgment message for ASSIGN/QUEUE command.
(Print, Batch) queue <queue-name> deassigned from server <server-name>
Explanation: Acknowledgment message for DEASSIGN/QUEUE
command.
(Print,Batch) queue <queue-name> closed
Explanation: Acknowledgment message for CLOSE/QUEUE command.
(Print, Batch) queue <queue-name> deleted
Explanation: Acknowledgment message for DELETE/QUEUE command.
%(Print,Batch) queue <queue-name> - <error text>
Explanation: For SET QUEUE, indicates that a queue was not
modified for the reason stated in the error text.
(Print,Batch) queue <queue-name> marked for deletion
Explanation: Acknowledgment message for DELETE/QUEUE
command when the queue you specified still has entries on it. The queue
is deleted as soon as it becomes empty.
(Print,Batch) queue <queue-name> opened
Explanation: Acknowledgment message for OPEN/QUEUE command.
(Print,Batch) queue <queue-name> started
Explanation: Acknowledgment message for START/QUEUE command.
(Print,Batch) queue <queue-name> stopped
Explanation: Acknowledgment message for STOP/QUEUE command.
(Print,Batch) server <server-name> (deleted,marked for deletion)
Explanation: Acknowledgment message for DELETE/SERVER
command.
Del Error Messages

A-21

%(Print,Batch) server <server-name> - <error text>

Explanation: For SET SERVER, indicates that a server was not
modified for the reason stated in the error text.
(Print, Batch) server <server-name> initialized [non-]shareable
[with forms <form-name>]

Explanation: Acknowledgment message for INITIALIZE/SERVER
command.
(Print, Batch) server <server-name> modified

Explanation: Acknowledgment message for SET SERVER command.
(Print, Batch) server <server-name> started

Explanation: Acknowledgment message for START/SERVER command.
(Print,Batch) server <server-name> stopped

Explanation: Acknowledgment message for STOP/SERVER command.
PrintlBatch Services started at <time>

Explanation: Acknowledgment message when you issue the
START/QUEUEIMANAGER command to begin PrintlBatch Services.
PrintlBatch Services stopped at <time>

Explanation: Acknowledgment message for STOP/QUEUEIMANAGER
command if no jobs are being processed.
PrintlBatch Services will stop after (completing, aborting) <n> job[s]

Explanation: Acknowledgment message for STOP/QUEUEIMANAGER
command if any jobs are currently in progress.
?Priority exceeds queue's maximum

Explanation: You specified a priority for a PRINT or SUBMIT entry
larger than the maximum allowed for the queue.
?<privilege> privilege required

Explanation: You typed a command that requires some privilege, and
you do not have it.
??Program failure in <program-name>

Explanation: This message reports a problem in the software. It is
followed on the next line by an explanation of the problem. You should
verify that the failing program is correctly installed. If necessary, you
should then submit an SPR. The SPR should show the dialogue that
preceded the message, the exact text of the message, and a list of
patches that have been installed in the failing program.
?Program PBS$:PBS.TSK does not exist

Explanation: The PrintlBatch Services (PBS) program was not found
when you issued the START/QUEUEIMANAGER command.

A-22

Del Error Messages

?Protection violation

Explanation: This error can occur for reasons similar to the following:
..

You typed a CeL command that your system manager has protected
against general use.

You tried to run a program to which you do not have execute access.

•

You tried to read a file to which you do not have read access.

•

You tried to write to or delete a file to which you do not have write
access.

If this message occurs because of a protection violation with one of your
own files, you can use the SET PROTECTION command to change the
file's protection code. (However, this error can also occur because of other
conditions.)

%Public disk mounted as private

Explanation: A user with MOUNT privilege mounted a disk initialized as public without specifying !PRIVATE, !PUBLIC, /SHARE, or
/NOSHARE. The system mounts the disk as private.
?Qualifier conflicts with file type

Explanation: You specified the /APPEND qualifier and the file has
RlvlS attributes.
?Qualifier conflicts with parameter

Explanation: You typed a parameter and a qualifier that should not
be present together. For example, with the DEASSIGN command, you
specified the /ALL qualifier and a logical name.
?Queue already assigned to server

Explanation: You issued an ASSIGN/QUEUE for a queue already
assigned to the server you specified. Use the SHOW QUEUEIFULL
command to see which servers are assigned to a queue.
?Queue does not exist

Explanation: You specified the name of a queue that does not exist.
?Queue is (closed,deleted)

Explanation: A PRINT or SUBMIT command entry could not be
created on a queue because the queue is closed or marked for deletion.
Use a different queue.
?Queue is privileged

Explanation: The queue you specified in a PRINT or SUBMIT command requires one or more privileges that you do not have. Use the
SHOW QUEUEIFULL command to display the privileges that the queue
requires.
?Queue manager message queue full

Explanation: There is no room for additional messages to be sent to
PBS at this time. Reissue the request.

Del Error Messages

A-23

?Quoted string expected

Explanation: A quoted string or character was expected and was either
missing or was not enclosed in quotes.
%Record too long, line truncated

Explanation: The record on a READ command was too long. The
assignment occurred; however, only the first 255 characters were processed.
?Remote port name cannot exceed 16 characters

Explanation: The remote port name is longer than 16 characters on a
CREATEIPORT, ASSIGNIPORT or SET PORT command.
?Reserved symbol name

Explanation: The user attempted to define a local or global symbol
which began with a reserved prefix of $, F$ or :1'$, or delete a reserved
global symbol from the symbol table that began with $.
?Server already exists

Explanation: You issued the INITIALIZE/SERVER command to define
a server that already exists.
?Server does not exist

Explanation: You specified the name of a print or batch server that
does not exist. Use the SHOW SERVER command to list the defined
servers.
?Server [server-name] does not exist

Explanation: A SHOW TERMINAL [server-name] command was
entered and the specified server does not exist.
?Server name cannot exceed 16 characters

Explanation: The terminal server name is longer than 16 characters
on a CREATEIPORT or ASSIGNIPORT command.
?service name cannot exceed 16 characters

Explanation: The service name is longer than 16 characters on a
CREATEIPORT, ASSIGNIPORT or SET PORT command.
?Service [service-name] already exists

Explanation: The LAT service already exists on a CREATE/SERVICE
command.
?Service [service-name] does not exist

Explanation: The specified service does not exist.
?Single character expected

Explanation: A single character inside quotes was expected and more
than one character was supplied (for example, SET DATAlEND_OF_
DATA = "$$").

A-24

Del Error Messages

?Speed is not allowed for <terminal>

Explanation: The speed specified is not one of the speeds allowed for
this terminal in the TERSPD.SYS file.
??Stack overflow

Explanation: This message indicates a system problem. The system
manager should send in an SPR, giving the dialogue that preceded the
message, the text of the message, and a list of patches that have been
installed.
?String too long

Explanation: While in an expression, a string became too long to fit in
the 255 available bytes.
?Substitution too complex

Explanation: The user's request for apostrophe substitution was
rejected because the substitution was too complex. It reached the
maximum number of substitution iterations allowed on one command.
?Symbol name conflicts with <symbol-name>

Explanation: The user specified an assignment whose symbol name or
abbreviation point conflicted with an existing symbol definition in the
same symbol table.
?Symbol name too long

Explanation: The symbol name specified by the user exceeded 255
characters.
%Symbol table almost full

Explanation: This warning is issued when your local or global symbol
table has less than 100 free bytes.
??Symbol table full

Explanation: You attempted to define a label or symbol when the local
or global symbol table was already filled up. Note that if you are in a
command procedure when your symbol table gets full, the command
procedure aborts.
?Syntax error

Explanation: The command has improper syntax. This occurs when
there is not a more specific message describing the syntax error.
?That port is currently in use

Explanation: The port already exists on a "CREATE PORT port-name"
command.
?The port name specified is not a dynamic keyboard

Explanation: The port-name is invalid on a CREATEIPORT port-name
command. Port names must be in the format "KBn".
?The port name specified is not a LAT port

Explanation: The port-name is invalid on a SHOW PORT command.
Port names must be in the format "KBn".
Del Error Messages A-25

?The port name specified is not an outbound LAT port
Explanation: The port-name is invalid on a SET PORT, ASSIGNIPORT,
DEASSIGNIPORT or DELETEIPORT command. Port names must be
in the format "KBn". The specified keyboard must have already been
created as an application port with the CREATE/PORT command.
?THEN clause required
Explanation: The action clause was missing on the IF <expression>
THEN command or on the ON <severity-level> THEN command.
?THEN keyword required
Explanation: The THEN keyword was missing on the IF <expression>
THEN command or on the ON <severity-level> THEN command.
?Time limit exceeds queue's maximum
Explanation: You specified a !TIME_LIMIT value in a SUBMIT command larger than the maximum allowed for the queue.
?Too many arguments
Explanation: You used the notation /qualifier=(arg,arg, ... ) with a
qualifier that accepts only a single argument.
?Too many elements in list
Explanation: In a list of file specifications or other items (separated by
commas or plus signs), you indicated more file specifications than are
allowed. For example, you exceeded one of the following limits:
..

The DIBOL, RENAME, DELETE, and SET PROTECTION commands allow six file specifications.

The COPY command allows six input file specifications and one
output file specification.

The PRINT and SUBMIT commands allow up to 11 file specifications.

?Too many files or parameters
Explanation: You specified too many file specifications in a PRINT or
SUBMIT command, or a parameter string in a SUBMIT command is too
long to be handled by PBS. Reduce the number of file specifications or
use a shorter parameter string.
?Too many logical names assigned
Explanation: With the ASSIGN command, you exceeded the maximum
number of logical names. You can only assign up to four logical names
(only three logical names if any of the logical assignments includes a
PPN).
?Too many open files on unit
Explanation: You specified the same magnetic tape or DECtape drive
both as input and output files on COpy or APPEND.

A-26

Del Error Messages

?Tho many parameters

Explanation: This message occurs if you specify more command parameters than the command can accept. For example, you specified more
than eight parameters with the /PARAMETERS qualifier.
?Tho many printers initialized

Explanation: The device you specified could not be initialized because
the maximum number of spooling devices has already been initialized.
?Unable to copy tape command file to disk

Explanation: The user specified an indirect command file on magnetic
tape, and some error occurred when attempting to copy it to a temporary
disk file for processing.
??Unable to create DCL work file

Explanation: DCL's work file for storing the user's symbol tables could
not be created on disk. The user may be over quota. Corrective action
should be taken before the user continues processing.
??Unable to read DCL work file

Explanation: The user's symbol tables could not be read in from the
DCL work file. If RSTSIE is processing an indirect command file, then
control immediately returns to the interactive level.
?Unable to start PrintlBatch Services
<error message>

Explanation: Some external condition, as the error message on the
second line describes, prevented PBS from being started.
??Unable to write DCL work file

Explanation: The user's symbol tables could not be written out to the
DCL work file. The user may be over quota. Corrective action should
be taken before the user continues processing. If RSTSIE is processing
an indirect command file, then control immediately returns to the
interactive level.
?Unbalanced parentheses

Explanation: Parentheses do not match up (for example, A=((5)+6).
?Undefined label <label>

Explanation: The label specified on the GOTO command does not exist
in the indirect command procedure being executed.
?Undefined symbol

Explanation: The symbol name specified is not defined in the global or
local symbol tables.
?Unexpected character

Explanation: A character was encountered in a qualifier or a parameter that was not expected. For example, in
SET TERMINALfWlDTH=80FOO, the "F" of "FOO" would be an unexpected character.

DeL Error Messages

A-27

?Unit number required

Explanation: This message occurs when you specify a device-name
without a device-number (for example, DM: instead of DMO:).
?User macros nested too deep

Explanation: There were more than 50 nested user macros or a user
macro caned itself.
?Wildcard entry name not allowed

Explanation: The command you specified does not anow wildcard entry
names. Specify the name of a single entry instead.
?Wildcards not allowed

Explanation: You included a wildcard in a file specification, where
Wildcards are not allowed.
?Wildcard PPN not allowed

Explanation: The command you specified does not allow wildcard
PPNs. Specify the name of a single PPN instead.
?Wildcard queue name not allowed

Explanation: The command you specified does not anow wildcard
queue names. Specify the name of a single queue instead.
?You need MOUNT privilege to dismount a public disk

Explanation: This message occurs when a user without MOUNT
privilege tries to dismount a disk initialized as public. A user without
MOUNT privilege can dismount only private disks.
?You need MOUNT privilege to mount a public disk

Explanation: This message occurs when a user without MOUNT
privilege tries to mount a disk initialized as public. A user without
MOUNT privilege can mount only private disks.
?You must have MOUNT privilege to rebuild the disk

Explanation: This message occurs when a user without MOUNT
privilege attempts to rebuild a private disk with the !REBUILD qualifier
of the MOUNT command. Have your system manager rebuild the disk.

A-28

Del Error Messages

Appendix B

More About Command Environments and RSTS/E
File Specification

This appendix provides infonnation primarily for users who are familiar with
earlier versions (V9.0 and before) of RSTSIE, especially those users who work
mostly within command environments other than DCL.

B.1

More About Command Environments
Chapter 1 discusses the four RSTSIE command environments: DCL, BASICPLUS, RTll, and RSX. Each offers its own advantages. Each command
environment has its own prompt:
Prompt

Environment

Digital Command Language (DCL) environment

Ready

BASIC-PLUS environment
RTll environment
RSX environment

Since DCL is the default command environment on RSTSIE, this manual has
already described many DCL commands to help you in your work. If you want
to switch to one of the other command environments, see the appropriate
documentation for complete descriptions of the commands you can use in
BASIC-PLUS, RTll, and RSX.

B.1.1

Switching Between Command Environments
DCL is the default RSTSIE command environment. You can switch to another,
however. Use the following command to switch to and from any command
environment:
$ SET JOB!KEYBOARD_MONITOR=[commanc environment name]

The command environment name can be anyone of the following:
•

DCL

•

BASIC

•

RTll

•

RSX

More About Command Environments and RSTS/E File Specification

8-1

The system transfers control to that keyboard monitor, establishing it as your "job
keyboard monitor." That is, you can type commands to the keyboard monitor you
switched to until you switch again, or logout of the system.
NOTE

You can issue DCL commands from any keyboard monitor by typing
the $ character followed by the command. For example, if you are in
the BASIC-PLUS command environment and you want to use the DCL
SHOW USER command, type:

$ SHOW USER
DCL will execute the SHOW USER command, then automatically
return to the BASIC-PLUS environment.
Note that if you type the $ character with no command, you will switch
back into the DCL command environment.

B.1.2

BASIC-PLUS Keyboard Monitor Commands
The BASIC-PLUS command environment provides commands useful to the
BASIC-PLUS programmer on RSTSIE systems. The BASIC-PLUS interpreter
lets you type in a program using BASIC-PLUS statements that are translated
and stored in your job area.
Many of the BASIC-PLUS commands (which are distinct from language statements) let you list, compile, store, and otherwise work with the BASIC-PLUS
program you create. Note, however, that BASIC-PLUS has a very powerful feature, called "immediate mode" that allows you to type many language statements
as though they were commands.
Table B-1 briefly describes BASIC-PLUS commands. See the BASIC-PLUS
Language Manual for a complete description of BASIC-PLUS commands.
Table B-1:

BASIC·PLUS Commands

Command

Description

APPEND

Includes the contents of a previously saved source program into
the current program.

CAT or CATALOG

Displays the file directory for your account. Unless another
device is specified following the term CAT or CATALOG, the
public disk structure is the assumed device.

CCONT

Can be used by privileged users only. The command operates
the same as the CONT command, but detaches the job from the
terminal.

COMPILE

Allows you to store a translated version of your BASIC program.
The file is stored on disk with the current name and the file type
.BAC. Or, you can specify a new file name and type.

CONT

Allows you to continue execution of the program currently in
memory following the execution of a STOP statement.

(continued on next page)

8-2

More About Command Environments and RSTS/E File Specification

Table B-1 (Cont.):

8.1.3

BASIC-PLUS Commands

Command

Description

DELETE

Allows you to remove one or more lines from the program
currently in memory. After the word DELETE, type the line
number of the single line to be deleted or two line numbers
separated by a hyphen (-) indicating the first and last line of
the section of code to be removed. Several single lines or line
sections can be indicated by separating the line numbers, or line
number pairs, with a comma.
.

EXIT

Returns you to the job keyboard monitor.

KEY

Reenables the echo feature on the terminal after a TAPE
command. Enter with the LINE FEED or ESCAPE key.

LENGTH

Displays the length of the current program in memory, in lK
increments.

LIST

Displays the program currently in memory at your terminal.
You can list the entire program currently in memory, or one or
more lines of that program.

LISTNH

Does the same thing as LIST, except that it does not print a
header containing the program name and current date.

NEW

Clears your area in memory and allows you to input a new
program from the terminal. You indicate a program name
following NEW or when the system requests it.

OLD

Clears your area in memory and allows you to recall a saved
program from a storage device. You indicate a program name
following the word OLD or when BASIC-PLUS requests it.

RENAME

Lets you change the name of the program currently in memory.

RUN

Lets you begin execution of the program currently in memory.
Or, if the RUN command is followed by a file specification, including device and account if desired, you can run any program.

RUNNH

Executes the program currently in memory, but does not print
header information with the program name and current date.

SAVE

Saves the source program currently in memory in a file on the
system disk, under its current name with the file type of .BAS.
Or, you can give a complete file specification (including device
and account).

SCALE

Sets the scale factor to a designated value or displays the values
currently in effect if no value is designated.

TAPE

Disables the echo feature on the terminal; this is useful if you
are using a terminal with a paper-tape reader.

UNSAVE

Deletes the file specified.

RT11 Keyboard Monitor Commands
The RTll Run-Time System has a keyboard monitor. If you switch control to
RTll, a period (.) prompt displays, and you can type commands. You can use the
standard RSTSIE commands ASSIGN, BYE, DEASSIGN, HELLO, and MOUNT.
Table B-2 briefly describes RTll commands.

More About Command Environments and RSTS/E File Specification

8-3

Table B-2:

RT11 Commands

Command

Description

BIEID

The commands B, E, and D let you examine memory locations,
as follows:

B <address>--Sets a base address from which offsets in E
and D commands are computed. Initially, the base is O.

E <offset>--Prints the contents of location <address> +
<offset>.
..
D <offset> <value>--Replaces the contents of location
<address-> + <offset> with <value>.
Any address from 0 to 177777 is valid for these commands;
however, addresses outside your current job image area (as
determined by the SIZE command) will give an error.
..

CCO[NTINUE]

Resumes the execution, as a detached job, of a program that was
stopped by a CTRUC. If, for any reason, the program cannot
be restarted, the error message ?Can't continue displays on the
terminal.

CO[NTINUE]

Resumes execution of a program stopped by a CTRUC. If, for
any reason, the program cannot be restarted, the error message
?Can't continue displays on the terminal.

CL[OSE]

Closes all open channels. Tentative files are made permanent.

DATE

Displays the current date on the job's terminal.

ER[ROR]

Prints the RSTSIE error message teArt associated vvith the last
encountered error, if there was one. For example, any failure
on file lookup gives an error message similar to ?Fil not fnd?
Typing CTRUC to return to RTll's period prompt (.) and then
typing ERR will print the full RSTSIE error message for the
error encountered; for example, can't find file or account.

GE[T]

Loads an RTll-executable file (with a file type of .SAV) into
memory, but does not execute it. (The START command is used
to run programs loaded with GET.) No automatic expansion
of the job image area occurs with GET; you must use SIZE if
necessary.
Loading for GET differs from R or RUN in that certain low-core
areas are preserved rather than loaded from block 0 of the .sAV
file.

IN[ITIALIZE]

Resets all RTll conditions, except for logical assignments, to the
state they are in when RTll is first entered as the job keyboard
monitor.

LOCK

Denies access to a disk pack by users with insufficient privileges.
The format is:
LOCK dev:
where dev: is the device designation for the disk.

MO[NITOR]

Exits to the job keyboard monitor. This will be the default
keyboard monitor unless you have run the SWITCH utility to
set a job keyboard monitor.

(continued on next page)

8-4

More About Command Environments and RSTS/E File Specification

Table 8-2 (Cant.):

RT11 Commands

Command

Description

Runs a program from the system library account. The file can be
associated with any llln-time system. For example, R LINK has
the same effect as RUN $LINK
The R command will automatically expand the user job image
area, if necessary.

RE[ENTER]

Reenters or restarts a program already in memory whose
execution has been halted. Bit 13 in the Job StatUB Word (see
the RSTS/E System Directives Manual) must be set to allow a
restart. If it is set, execution begins at the address specified by
the contents of word 40 in the low 1000 bytes of virtual memory.
All channels are reset (see .SRESET directive, RSTS / E System
Directives Manual) unless the chain bit (bit 8 of the Job Status
Word) is set. If restart is not possible, the message ?No restart
is displayed on the terminal.

Loads the file named (from the user's account if no project programmer number is given) and begins execution. The program
may be associated with any run-time system. If necessary, the
user job image area is automatically expanded for the program
to be loaded and llln. The RN and R commands are identical
except for the accounts searched for the file when no explicit
project-programmer number is given.

RU is the same as a GET followed by a START. You must
use SIZE to expand the user job image area, if necessary; no
automatic expansion occurs with RU.

RUN

This command is passed on by the RTll run-time system to
the RSTS/E monitor - it works the same in any command
environment.

SH[UTUP]

If (1) only one job is running on the system, (2) logins are
disabled, (3) no disks except the system disk are mounted, and
(4) no files are open on the system disk, then the SHUTUP
command logs the current job off the system and bootstraps the
initialization code after the job is logged off.

SI[ZE]

Sets the size available for an RTll program, in K words. When
the RTll llln-time system is entered, the size is set to 2K words.
To see the current size, type SIZE without a value.
You must use SIZE to insure enough memory before typing
a GET or RU command. The job image area is automatically
expanded for Rand RN commands, from information carried in
the file itself However, a size given with SIZE overrides any
computed value (for Rand RN) if the computed value is smaller
than the SIZE value.

ST[ART]

Starts a program loaded with GET. The format of the command
is:
ST[ART] [addr]
where addr is an even octal number specifying the address
where program execution is to begin. If addr is omitted or 0,
execution begins with the address in location 40 in the low 1000
bytes of memory.

TI[ME]

Displays the current time of day at the job's terminal.

(continued on next page)

More About Command Environments and RSTS/E File Specification

8-5

Table B-2 (Cont.):

RT11 Commands

Command

Description

UNLOCK

Unlocks a disk pack, so that programs running under nonprivileged accounts can open files on the disk. The format
is:
UNLOCKdev:
where dev: is the device designation of the disk to be unlocked.

VE[RSION]

8.1.4

Prints the current emulator version number.

RSX Keyboard Monitor Commands
The RSX run-time system has a keyboard monitor. If you switch control to RSX,
an angle bracket (» prompt is displayed. You can use the standard RSTSIE
commands ASSIGN, BYE, DEASSIGN, HELLO, and MOUNT.
Table B-3 briefly describes RSX commands.
Table B-3:

RSX Commands

Command

Description

DISMOUNT

Prepares a device for dismounting, so that you can remove a
disk pack of magnetic tape from a device. The format of the
command is:
DISMOUNT dev:

UNSAVE

Deletes a specifically named file from your account. The format
of the command is:
UNSAVE filename.type

SHUTUP

Shuts down the system if no other jobs are running on the
system, all disks are dismounted, all other run-time systems are
removed, and no logins are allowed.

B.2 More About The RSTS/E File Specification
Many commands in the environments discussed in the previous section require
that you identify a file to serve as either input or output to the command.
This section provides further infonnation on specifying RSTSIE files in these
command environments.
The general fonn for a RSTSIE file specification is:
device:[project,programmer]filename. type/switches
The following section discusses only the /switch element in the RSTSIE file
specification. See Chapter 1 for a description of the other elements of specifying
files.
NOTE

The traditional RSTSIE file specification switches !MODE, /SIZE,
and IRONLY cannot be used in DCL. Many of the same features are
available through DCL, but you must use DCL notation.

8-6

More About Command Environments and RSTS/E File Specification

8.2.1

RSTS/E File Specification Switch
A file specification switch may be included as the final element of the specification
string. You may specify the following switch options:
•

!PROTECT - protection to be given to the file

•

IFILESIZE - disk size (in blocks) to which the file is pre-extended

•

ICLUSTERSIZE - minimum number of contiguous disk blocks forming a
cluster

•

!POSITION - specific block number on disk at which the file is to be placed

•

/MODE - read/write mode in which the file's data is passed to the device
driver

•

IRONLY - read-only mode value for a disk file

If a file specification switch is not at the end of the file specification, is missing a
colon, or is not a valid form, the system prints the error message ?Illegal switch
usage. For example, either of the following specifications will produce the switch
usage error message:
•

ABC/SI:100 [1,2]

•

ABC/SI

If an argument is missing, or contains an illegal character, the system generates
an ?Illegal number error message.

8.2.2 IPROTECT Switch
The !PROTECT switch establishes a protection code for the file. The !PROTECT
switch consists of:
•

A slash (/)

•

PROTECT (or a minimum abbreviation of PR)

•

A colon (:)

•

A number specifying the protection code. Use a number sign (#) before octal
numbers, and a decimal point (.) to terminate decimal numbers.

The protection code is a string of one to three digits. This string determines
the file's degree of protection on two levels: the actions - reading, writing, and
deleting - against which it is protected, and the user or class of users against
whom it is protected.
See Chapter 3 for a complete description of how to specify protection codes.

8.2.3 IFILESIZE Switch
The IFILESIZE switch allows the creation of a disk file of the specified size,
in blocks, before any read/write operations are performed. Thus, IFILESIZE
reserves space on the disk for data to be placed in the file. This switch consists
of:
•

A slash (/)

•

FILESIZE or SIZE (or a minimum abbreviation of FI or SI)

More About Command Environments and RSTS/E File Specification

8-7

•

A colon (:)

•

An optional number sign (#) for octal conversion of the argument n

•

The argument n, a decimal number which indicates the number of blocks in
the pre-extended file

•

An optional trailing decimal point (.) to ensure that n is interpreted as a
decimal number.

The argument n specifies the length in disk blocks to which the file is preextended. That is, it reserves a specified portion of disk space for the file. The
value of the IFILESIZE argument is dependent on the type of file. If the file's
protection marks it as executable, the argument n must be in the range of 0 to
65535. If the capability to create large files is present on your system and the file
is not marked as executable, the argument n can be in the range of 0 to 2*23-1
(assuming that the disk is large enough). Note that you cannot run an executable
file that is larger than 65535 blocks. An attempt to pre-extend such a file beyond
block 65535 returns a ?Protection violation error message.
The IFILESIZE switch may be minimally abbreviated to IFI or to lSI. The
following list shows its valid forms:
IFI:[#]n[.]
IFIL:[#]n[.]
IFILE:[#]n[.]

IFILESIZE:[#]n[.]
or
ISI:[#]n[.]

ISIZE:[#]n[.]

8.2.4

/CLUSTERSIZE Switch
The ICLUSTERSIZE switch establishes the minimum cluster size for a disk
file; a cluster is a number of contiguous blocks taken together as a unit. The
ICLUSTERSIZE switch is especially useful for large files; specifying a large
cluster size speeds up random access to the data and prevents such files from
crowding or filling your directory, whose size is limited. RSTS/E permits cluster
sizes of 1, 2, 4, 8, 16, 32, 64, 128, or 256 blocks.
The ICLUSTERSIZE switch consists of:

8-8

•

A slash (/)

•

CLUSTERSIZE (or a minimum abbreviation of CL)

•

A colon (:)

•

An optional minus sign (-) to specify a negative cluster size (see the next
paragraph)

More About Command Environments and RSTS/E File Specification

An optional number sign (#) for octal interpretation of the argument n

The argument n specifying the duster size in blocks

A decimal point (.) to ensure decimal interpretation of n

The following list shows the valid fonns of the option:
ICL:[-][#]n[.]

ICLU:[- ][#]n[.]
ICLUS:[- ][#]n[.]

ICLUSTERSIZE:[- J[#]n[.]
Specifying a negative duster size avoids certain errors associated with disk
devices. A negative duster size causes the system to use the absolute value of
the cluster size, if the device on wrAich the file is created allows that value. If
the absolute value is less than the device duster size at which the file is to be
created, the system uses the device cluster size instead of returning an error.

B .2.5 /POSITION Switch
The !POSITION switch allows you to specify the location of a file on disk. The
/POSITION switch consists of:
..

A slash (/)

POSITION (or a minimum abbreviation of PO)

A colon (:)

The argument n, a decimal number that specifies the desired placement of
the file

The argument n indicates a device cluster number on the disk. The device cluster
numbers vary from disk to disk; see the RSTS / E System Generation Manual for
a table of device sizes.
If the value of n in IPOSITION:n is 0, no placement is perfonned and the system
detennines the location of the file on the disk. If the value of n is a nonzero

number, the system attempts to place the first block of the file at the specified
device cluster number on the disk. If the file cannot be placed at that location,
the system places the first block of the file at the first free cluster number that is
greater than the specification.
When a file is placed, it is marked as such by the monitor. Note that no error
is returned if the system is unable to place the file at the specified location. To
detennine the actual location of the file on disk, use the IPO,IFU, or IS options of
the DIRECT program. For example:
SY: [2,211]
RMSTST.B2S
RMSTST.OBJ
RMSTST.MAP
CHTST .BAS
CHTST1.TSK

18698
18720
18723
6020
16562

More About Command Environments and RSTS/E File Specification

8-9

The fonowing list shows the valid forms of the POSITION option:
IPO:n
IPOS:n
IPOSI:n

IPOSITION:n
Note that the position of a file on disk may change if you backup and restore the
file with the BACKUP program.

B.2.6

IMODE and IRONlY Switches
The /MODE switch enables the passing of up to 16 (decimal) bits of information
to the device driver at file open time. The meaning of these bits (if any) is
device dependent, and determines the read/write mode for data transfer. For
explanations of the bits, see the RSTS / E Programming Manual.
The /MODE switch consists of:
•

A slash (/)

MODE (or a minimum abbreviation of MO)

A colon (:)

An optional number sign (#) for octal interpretation of the argument n

The argument n specifying a mode setting between 0 and 32767 (decimal)
inclusive

An optional decimal point (.) to ensure decimal interpretation of n

The following list shows the valid forms of the option:
/MO:[#]n[.]
/MOD:[#Jn[.J
/MODE:[#]n[.J
The IRONLY switch enables setting of the read-only MODE value for a disk file.
The IRONLY switch consists of:
..

A slash (/)

«I

RONLY (or a minimum abbreviation of RO)

The following list shows the valid forms of the option:
IRO
IRON
IRONL
IRONLY

8-10

More About Command Environments and RSTS/E File Specification

GLOSSARY

Absolute Time

A specific date or time provided in a command line. (Compare with Real
Time.)
Account

What you log in to with a Project-Programmer Nwnber (PPN) and a password
on a RSTSIE system.
Account Number

A nwnber that identifies the project group and the programmer. It is also
known as the Project-Programmer Number (PPN, such as [3,25]). You need
an account number (which new users receive from the system manager) to
log in to the system. The system uses the account to charge you for computer
time and arrange, find, and protect your stored files.
Alphanumeric

A contraction of alphabetic-nwneric; the set of characters that compose text.
Characters include letters and nwnerals, and exclude special characters.
ANSI

American National Standards Institute. Creates standards to ensure
consistency in all aspects of computer technology: command languages,
keyboards, codes, and so forth.
ASCII

American Standard Code for Information Interchange, a standard 7-bit code
representing the 128 characters in which textual information is recorded.
Batch Processing

A way of scheduling programs that allows you to enter jobs to be run without
your input at a terminal. Batch processing can be used, for example, in data
processing operations that need no interaction.
Baud Rate

The speed at which information is transferred between devices on a system.
Bit

A contraction of "binary digit." A bit is the smallest unit of information in a
binary system of notation.
Block

A set of consecutive machine words, characters, or digits handled as a unit,
particularly in input and output operations. On the RSTSIE system, a block
is equal to 256 16-bit words or 512 8-bit bytes.
Glossary-1

BPI

Bits per inch; a measure of tape density. Common densities for magnetic
tapes are 800, 1600, 6250, 6667, 8000, and 10000 bpi.
Buffer

A temporary storage area used to contain data. Buffers hold data being
passed between processes or devices that operate at different speeds or
times.
Byte

A group of eight binary digits (bits) processed as a unit. Each ASCII
character is stored in one byte.

CCl
See Concise Command Language.
Central Processing Unit (CPU)

The portion of a computer system that controls the interpretation and
execution of instructions.
Channel

A logical concept that helps you manage the flow of data to and from a
running program.
Character
An element in a set of symbols. A human-readable symbol can be a letter

from A to Z, a number from 0 to 9, or a special symbol. A machine intelligible
symbol is made of a group of binary digits. Some machine-readable symbols
are "nonprinting" characters (such as tabs or control characters), because they
cannot be displayed on a line printer listing or a video screen.
Cluster Size

The unit of size in which files are allocated. Cluster size is measured in
blocks.
Command

A user-initiated order to a computer system that causes the performance of a
predefined operation. A command is the part of an instruction that specifies
the operation to be performed.
Command environment
An interface through which you can communicate with the computer. DCL

and BASIC-PLUS are examples of command environments.
Command level

The part of a session at a terminal when the system awaits your input. For
example, you can recognize DCL command level by its dollar sign ($) prompt.
Command line/command string

A line (or set of continued lines), normally terminated by pressing the
RETURN key. A command line or string contains a command and (optionally)
information modifying the command. The full form of the command string
contains a command, its qualifiers, and its parameters (file specifications, for
example) and their qualifiers.

Glossary-2

Command line editing

Allows you to edit with the following line functions:
Move the cursor left or right one character
Move the cursor to the beginning or end of the line
Delete the previous word
Delete to the beginning of the line
Insert a new character at the cursor position
Overstrike (replace) an existing character at the cursor position
Command line recall

Allows you to recall your most recently entered commands or program input
lines.
Compile

To translate a source program (one written by a user) into machine language.
Concatenate

To unite in a series; to link together many items into one.
Concise Command language (CCl)

A way to call a system program and provide it with input on a single
command line. Many system programs (such as PIP on RSTSIE), use the
name of the program as the command name, followed by the command line
required by that program. CCLs can be different for each RSTSIE system.
CPU

See Central Processing Unit.
Crash
An unexpected computer system shut-down, caused by problems such as

power failures.
Creation date

The date on which a file on RSTSIE is created or updated.
CRT

Cathode Ray Tube. A CRT is used in video display terminals, such as VT220s
and VT100s. Sometimes video terminals are called "CRT devices."
CTRl (control key)

The keyboard character that causes a control action. It is used in combination
with an alphabetic key. For example, if you hold down the control key and
press the "U" key on a RSTSIE system, the system responds by deleting
characters from the cursor to the beginning of the line.
DECnet

A family of hardware/software products that creates distributed networks
from Digital computers and their interconnecting devices. DECnet allows you
to do such operations as copying files from one computer (node) to another,
and connecting your terminal to a remote computer.
Default

To omit information in a computer operation and let the computer make
a predefined assumption about the operation; the assumption made by a
program when you do not provide a value.

Glossary-3

Density

The number of bits per inch (bpi) that can be stored on a magnetic tape.
Device

A peripheral hardware unit used to perform input and output operations.
Dialup Line

A communications circuit that connects a terminal and a computer over a
telephone line.
Digital Command language (DCl)

The default command language on RSTSIE systems.
Disk

A mass storage device that holds data on rotating magnetic platters.
Disk Quota

The capacity of a disk to store information. Each user of a computer system
is allowed a finite amount of storage space. On RSTSIE, the system notifies
you if you try to exceed your disk quota.
Display

The printing of text at a hardcopy terminal, or the output of text at a video
screen.

DOS
Disk Operating System. DOS is used primarily to refer to a tape format.
EchO

The display of characters you type at a terminal. When you log in to a
RSTSIE system, for example, generally the PPN is echoed, but the password
is not..
Echo on read

The processing and echoing of characters typed on a terminal only when a
read occurs.
Editing Session

The time you spend at a terminal using a text editor.
Editor

A program that allows you to modify data, programs, or files.
Elapsed Time

The amount of time you are logged in to a computer system.
Error Message

A notice from the computer that indicates an error and usually contains
recovery information; a program message indicating the presence of a
mistake. For example, RSTSIE displays an error message if you type in data
that it cannot process.
Field

One or more characters treated as a unit; a specified area of a record used for
a single type of data. For example, a file name is occasionally referred to as
the "name field" of a complete file specification.

Glossary-4

File

An ordered collection of stored text or data; a collection of related infonnation.
For example, you could create files on RSTSIE to contain data for a program
or text for a report.
File Specification

The name used to identify the node, device, directory name, file name, and
file type under which you store a file.
File Type

The part of a file specification that follows the file name. A file type
(sometimes called an "extension" on RSTSIE) consists of a period (.) followed
by up to three alphanumeric characters.
Hard copy

Computer output printed on paper, such as from a line printer or a hardcopy
tenninal.
Hardware

The physical equipment or machinery of a computer system. Devices are
examples of hardware. (Compare with Software.)
Help Facility

A set of online messages that describes the functions of available programs on
a system.
Host

The computer system that processes your commands and responds to them.
The network node that you are currently logged in to.
Input

Infonnation that is transmitted to a computer; infonnation to be processed
by the computer; a device involved in gathering data. For example, when
you type in a program at a tenninal that is connected to the computer, you
are providing input. Among other things, the terminal is serving as an input
device.
Insert mode

Indicates that each new character should be inserted at the current cursor
position; characters to the right of the cursor are shifted right one character
to make room for the new character.
Installation

The location of a computer system. For example, this manual refers to your
installation as the computer system at your site.
Interactive

The process of communication between a person and a computer system. For
example, the computer prompts you for input and you type in a response.
Interface

A shared boundary between two elements of a computer system, such as
between two programs or devices.
Job

Everything a user does from beginning to end of a tenninal session, for
example, commands, programs, processing, or output.
Glossary-5

Job Header
An area of memory where each job on the system is assigned its own set of
recall buffers
Job Number
The number RSTS/E assigns to your job when you log in. Your job number is
deleted when you logout.
Journaling
The recording of user input during an editing session. For example, if you
edit a file using EDT and the system crashes, journaling allows you to recover
your work when the system resumes operation.
Keyboard
The set of keys that you use to type at a terminal to provide input to the
computer.
Keyboard Monitor
A part of the system software that provides communication between a person
at a keyboard and the operating system. The keyboard monitor interprets the
commands you type at the keyboard.
Keyword
A word that is an integral part of a command or qualifier.

LAT
The abbreviation for local area transport; LAT is a communications protocol
used in a local area network.
Link

To combine or connect two independent entities; a reference to another
element in a set of elements. Linking is generally used to mean combining
two or more object files into an executable file.
Literal

Characters that are interpreted literally. For example, in BASIC-PLUS
programming, you can enclose a character string in quotation marks so that
the characters are used as literals.
Local Node
The node a user first logs in to on the system. The local node is generally
used in discussions of network operations. (Compare with Remote Node.)
Logical Name
A name that a user or system manager can assign to a physical device or to a
PPN. (Compare with Physical Name.)
Log In
The process of gaining access to a computer system.
Log Out
The process of ending a session with the computer.

Glossary--6

Longest Record Length (LRL)
Is dependent on the record format. For variable-length and stream records,
the size of the largest record inserted in that file is the longest record length.
For fixed-length records, the longest record length is the same for every
record in the file.
Magnetic Tape
A plastic tape coated with magnetic material on which data is recorded in
narrow tracks.
Memory
Internal computer storage. Memory is also a device on which data can be
stored and from which it can be accessed.
Merge
In files, to join the contents of one file to the contents of another file.
Mnemonic
An aid to memory, as in mnemonic file names, where the name of the file
reminds you of the contents of the file.
Mode
A state of being, such as "interactive mode," in which the system or a program
prompts you for your input.
Multiline commands
Commands or lines that extend beyond the terminal's width and wrap onto
one or more subsequent lines.
Network
A set of interconnected computer systems.
Node
An individual computer system in a network that can communicate with
other computer systems in the network.
Non-File-Structured Device
A device that does not separate data into distinct files and does not maintain
directories.
Null
An element that is explicitly left blank. For example, a null file type consists
of no alphanumeric characters. In other words, the file specification includes
a file type, which is null.
Operator
1. The part of an instruction that tells the computer what to do. For example,
the plus sign (+) is an operator telling the computer to perform addition. 2. A
person who controls the running or function of a machine or device.
Operator/Message Services (OMS)
Receives event information, such as LOGIN attempts or printer offline
notices, from various system programs and broadcasts the messages to all
operator terminals. If requested to do so, OMS also saves the messages in its
log file for later display (via the SHOW REQUESTS command.)

Glossary-7

Operating System

Software that controls the execution of computer programs and performs
system functions. An operating system is an integrated collection of programs
that supervise computer operations.
Operator Terminals

Terminals designated to receive operator messages or requests or both.
Output

The device involved in transferring data from memory; the data created as
the result of transfer; processed data. For example, when your terminal
displays the contents of a file, the terminal serves as an output device.
overstrike mode

Indicates that each new character should replace (overstrike) the character
positioned at the cursor.
Parameter

The object of a command. A parameter can be a file specification or a keyword
option.
Parity Bit

A binary digit appended to a group of bits to make the sum of all the bits
always odd (odd parity) or always even (even parity). (Parity pertains to the
way data is transmitted between the system and its devices.) A parity bit is
used to verify data storage.
Password

The character string assigned to each user that verifies user access privileges
to a system; a way of assuring file confidentiality on time-sharing systems.
You need a PPN and a password to log in to a RSTSIE system.
PBS

The PrintlBatch Services package which provides several important services
for RSTSIE users and system managers. The major components of PBS are:
Queue Manager accepts all user requests, controls all print and batch
queues, schedules jobs to run, and creates new jobs as needed to process
requests.
Print Servers process print requests on selected printers. Both line
printers (LP) and terminals (KB) can be handled by print servers.
Batch Servers control execution of submitted command procedures, using
the DCL command file processor.
User Interface is how an application program communicates with PBS.
Physical Name

A name for a peripheral device; identifies the drive, control circuit, and
medium together. (Compare with Logical Name.)
Port

A device that passes messages between the monitor and one or more
terminals.
Priority

The level of importance assigned to an operation in computing. For example,
you can set the priority of a print request so that your job is printed before or
after other jobs in the print queue.
Glossary-8

Programming

The process of planning, writing, testing, and correcting the steps required
for a computer to solve a problem or perform a desired operation.
Project-Programmer Number (PPN)

See Account Number.
Prompt

A symbol indicating that the system is prepared for input from a user.

Protection Code
A feature that allows you to decide who can have access to your files.
Pseudo Keyboard
A part of RSTSIE software, primarily used in batch jobs. The pseudo
keyboard operates like a real terminal, except that the "typist" is a program
rather than a person.
Qualifier

A command language keyword that modifies the operation of a command.
Qualifiers are always preceded by slash (I) characters. (On some systems, a
qualifier is called a "switch.")
Queue

A line-up of jobs to be performed in sequence, as in a batch or print queue, in
which certain jobs are given priority over others.
Read

A process that performs input from a file or a device.
Read-Only

The state a device or file is in when it can be used for input but not for
output. (Same as Write-Locked.)
Real Time

Synonym for time as we know it, in 24-hour days. (Compare with Absolute
Time.)
Remote Node

Any node in the network other than the local node. In other words, a remote
node is any node except the one you originally logged in to. (Compare with
Local Node.)
RSTS/E

An acronym for Resource-Sharing Timesharing Systern/Extended, a Digital
operating system.

Run Burst
The length of time, measured in ticks, that a job is allowed to run
uninterrupted in the CPU of a computer.
Run Time
The time in which a program is executed. Run time is the actual amount of
CPU time required for a program to complete execution.

Glossary-9

Run-Time System
System software that manages a programming language. The number of
run-time systems can differ from one system to another.
Software
The set of programs that controls the operation of a computer system.
SPR
Software Performance Report. Submitted by a user (generally the system
manager) to report a possible problem in the software.
Swapping
The transfer of a job from memory to disk or vice versa. Lets the system run
more jobs than its memory can hold at once.
Switch
See Qualifier.
Syntax
The rules governing the structure of statements in a computer language; the
structure of a language.
System
A combination of hardware and software that performs processing operations;
a collection of components that forms a functional unit.
System Manager
The person or group of people who schedule the access and use of a computer
system.
Temporary File
A file that is deleted from your account when you logout.
Terminal
A device, consisting of a keyboard and display mechanism, used to enter and
receive data to and from a computer. LA120s (hardcopy) and VT100s (video)
are examples of terminals.
Terminal Server
A system part that connects terminals to services on nodes in a local area
network; users have the same capability that they would have if they were
connected to the node by direct lines.
Tick
A fraction of a time slice. A tick is about 1/60 of a second.
Timesharing
A method of computer operation in which more than one user shares the
system at the same time. The central theory of timesharing is that the
system processes each user's job in slices of time, so rapidly that the user is
often unaware that processing time is shared.
Time Slice
The amount of time (in fractions of a second) that the computer assigns to
each user's job during timesharing.

Glossary-10

Translator
Software that converts human-readable programs into machine-readable
code.
Typeahead characters
Characters that are processed and echoed as soon as you type them, even if
no read is pending.
Utility
A program or set of programs that performs a set of commonly used functions,
such as copying or deleting files. The PIP program and the EDT editor are
examples of utilities on RSTSIE.

Wildcard
A symbol that allows you to refer to more than one file with a single file
specification. The asterisk (*) is a commonly used wildcard symbol in DCL, as
in *.DAT to specify aU names of data files.
Word
A unit of storage in the computer. A word holds 16 bits, or two ASCII
characters, of information.
Write
A process that performs output to a file or a device.

Glossary-i 1

Index
A
Abbreviations
in SHOW DEVICE/ALLOCATED display, 6-17!
in SHOW DISKS display, 6-171
in system status display, 4--41
Account
using, 1-1 10 1-25
I ACCOUNTING_DATA qualifier
SHOW ACCOUNT command, 4-14
Account number, 1-19
IADVANCED VIDEO qualifier
SET TERMINAL command, 5--5
I AFTER=date:time qualifier
PRINT command, 7-3
SET ENTRY command, 7-14
SUBMIT command, 7-7
/AFTER qualifier, 2-11
ALLOCATE command, 6-8
Allocating common area space, 8-421g
I ALLOCATION=n qualifier
COPY command, 3-25
CREATE command, 3-2
I ALLOCATION qualifier
MERGE command, 3-{;3
SORT command, 3-57
/ ALL qualifier
DELETE/ENTRY command, 7-17
RECALL command, 1-16
SET ENTRY command, 7-14
SHOW/PORT command, 4-12
SHOW ENTRY command, 7-10
SHOW JOB command, 4-9
SHOW QUEUE command, 7-18
SHOW TERMINAL command, 5--2
SHOW USER command, 4-8
IAlT MODE qualifier
SET TERMINAL command, 5--5
ANSI format, 6--6
IANSI FORMAT qualifier
COBOL command, 8-14
APPEND command, 3-36 to 3-38
IBEFORE=dale qualilier, 3-37
/CONFIRM qualifier, 3-37
ICREATED qualifier, 3-37
/LOG qualifier, 3-37
IMODIFIED qualifier, 3-37
IQUERY qualifier, 3-37
ISELECT=SIZE qualifier, 3-37
ISINCE=da!e qualifier, 3-37
/APPEND qualifier
OPEN/LOG_FILE command, 5--12

lAP PLICATION qualifier
SHOW/PORT command, 4-12
Arguments
abbreviating, 2-6
entering, 2-8
ASSIGN command, 6-20
Attached jobs, 4-{;
IATTACHED qualifier
SHOW JOB command, 4-9
SHOW USER command, 4-8

B
BACKSPACE, 1-18
BACKUP/DiRECTORY command
/OCCURRENCE qualifier, 3--46
Backup command, 3-39
BACKUP command
/CREATED qualifier, 3--40
/END qualifier, 3--40
/EXCLUDE qualifier, 3--40
IINCLUDE qualifier, 3--41
IINITIALIZE qualifier, 3--41
liN LABEL qualifier, 3--41
ILIST_FILE qualifier, 3--41
/MODIFIED qualifier, 3--40
lOUT LABEL qualifier, 3--41
IPROMPT qualifier, 3--42
/QUERY qualifier, 3--42
/REWIND qualifier, 3--42
!VERIFY qualifier, 3--43
IBACKUP qualifier
SET FILE command, 3-77
BASIC command, 8-7
/BP2 qualifier, 8-7
IBPLUS qualifier, 8-7
BASIC-PLUS
command environment, 1-8
commands, B-2t
BASIC programming, 8-7
/BATCH qualifier
DELETE/ENTRY command, 7-17
SET ENTRY command, 7-14
SHOW ENTRY command, 7-10
SHOW QUEUE command, 7-18
/BEFORE=date qualifier
APPEND command, 3-37
COpy command, 3-25
DELETE command, 3-19
DIRECTORY command, 3-9
RENAME command, 3-32

Index-1

IBEFORE=date qualifier (Cont.)
SET PROTECTION command. 3-74
TYPE command. 3-16
IBEFORE qualifier. 2-11
IBLOCK_SIZE=n qualifier
COPY command. 3-25
IBP2 qualifier
BASIC command. 8-7
IBPLUS qualifier
BASIC command. 8-7
IBREAK qualifier
SET TERMINAL command. 5-5
IBRIEF qualifier
DIRECTORY command. 3-9
RESTORE/DIRECTORY command, 3-54
SHOW ACCOUNT command. 4-14
SHOW ENTRY command. 7-10
SHOW QUEUE command. 7-18
SHOW TERMINAL command. 5-2
IBROADCAST qualifier
SET TERMINAL command. 5-5
IBUCKET_SIZE qualifier
MERGE command. 3--63
SORT command. 3-57
BYE command. 1-12 to 1-13

c
IC81 qualifier

COBOL command. 8-14
ICACHE qualifier
SET FILE command. 3-77
Call structure outline. 8-39fg
CC command. 8-8
IDEFINE qualifier. 8-8
IENVIRONMENT=([NO]FPU. [NO]PIC) qualifier.
8-8
I[NO]ERROR_LlMIT[=qualifier] qualifier. 8-8
I[NO]INCLUDE_DIRECTORY=(pathname [. ... J)
qualifier. 8-8
I[NO]UST[=fiIe-spec] qualifier. 8-8
I[NO]MACRO[=file-spec] qualifier. 8-8
I[NO]MEMORY[=qualifier] qualifier. 8-8
I[NO]MODULE qualifier. 8-8
I[NO]OBJECT[=fiIe-spec] qualifier. 8-8
I[NO]STANDARDl=(option •... )] qualifier. 8-8
I[NO]TERMINAL[=[NO]SOURCE] qualifier. 8-8
I[N01TITLE=(identifier) qualifier. 8-8
I[NO]UNDEFINE=(identifier[ •... ]) qualifier. 8-8
I[NO]WARNINGSl=(option •... )] qualifier. 8-8
I[NO]WORK_FILE qualifier. 8-8
ISHOW[=option •... ] qualifier. 8-8
CC Programming. 8-8
ICHECK=BOUNDS qualifier
COBOL command. 8-14
ICHECK=PERFORM qualifier
COBOL command. 8-14
ICHECK qualifier
COBOL command. 8-14
FORTRAN/F77 command. 8-22
ICHECK_SEQUENCE qualifier
MERGE command. 3--63
CLOSE/LOG_FILE command. 5-14
ICLUSTERSIZE switch. B-8
ICLUSTER_SIZE=n qualifier
COpy command. 3-25
CREATE command. 3-2

Index-2

COBOL-81 programming. 8-14
COBOL command. 8-14
IANSI_FORMAT qualifier. 8-14
IC81 qualifier. 8-14
ICHECK=BOUNDS qualifier. 8-14
ICHECK=PERFORM qualifier. 8-14
ICHECK qualifier. 8-14
ICODE=CIS qualifier. 8-14
ICROSS_REFERENCE qualifier. 8-14
IDEBUG qualifier. 8-14
IDIAGNOSTICS qualifier. 8-14
lUST qualifier. 8-14
IMAP qualifier. 8-14
INAMES=aa qualifier. 8-14
INODIAGNOSTICS qualifier. 8-14
INOUST qualifier. 8-14
INOOBJECT qualifier. 8-14
INOOPTIMIZE qualifier. 8-14
INOSTANDARD=option qualifier. 8-14
IOBJECT qualifier. 8-14
IOPTIMIZE qualifier. 8-14
ISHOW=MAP qualifier. 8-14
ISHOW qualifier. 8-14
ISTANDARD=option qualifier. 8-14
ISUBPROGRAM qualifier. 8-14
ITEMPORARY=device qualifier. 8-14
IWARNINGS qualifier. 8-14
ICODE=CIS qualifier
COBOL command. 8-14
ICODE qualifier
FORTRAN/FOR command. 8-25
ICOLLATING_SEQUENCE qualifier
MERGE command. 3-63
SORT command. 3-57
1132_COLUMNS qualifier
SET TERMINAL command. 5-5
@ command. 2-15
Command
RECALL. 1-14
ICOMMAND=file-spec qualifier
EDIT command. 3-5
Command environments. 1-8
BASIC-PLUS. B-1
DCL. B-1
RSX. B-1
RT11. B-1
Command files
see command procedures
Command line editing. 1-18
echo on read. 1-9
keys. 1-18
SET HOST. 1-29
Command Line Editing. 1-14
Command procedures. 2-13 to 2-15
Login. 1-9 to 1-10
Command recall
echo on read. 1-9
keys. 1-18
SET HOST. 1-29
Command Recall. 1-14
Commands
abbreviating. 2-6
ALLOCATE. 6-8
APPEND. 3-36 to 3-38
ASSIGN. 6-20
BACKUP. 3-39
BASIC. 8-7

Commands (Cont.)
BASIC-PLUS, B-21
BYE, 1-12 to 1-13
CC, 8-8
CLOSE/LOG]ILE, 5--14
COBOL, 8-14
continuing on more than one line, 2-4
COPY, 3-23 to 3-31
CREATE, 3--2 to 3-4
DEALLOCATE, 6-10
DEASSIGN, 6-23
DELETE, 3-19 to 3-22
DELETE/ENTRY, 7-17
DIBOL, 8-19
DIFFERENCES, 3--68 to 3--70
DIRECTORY, 3--9 to 3-15
DISMOUNT, 6-16
EDIT, 3--5 to 3-8
entering, 2-4
entering qualifiers, 2-7
for file operations, 3--1t
format description, 2-2fg
formats, 2-1 to 2-13
FORTRAN, 8-21
HELLO, 1--6
HELP, 1-10 to 1-12
INITIALIZE, 6-14
LINK, 8-30 to 8-46
LOGIN, 1-6
LOGOUT, 1-12 to 1-13
MACRO, 8-28
MERGE, 3--62 to 3--67
MOUNT, 6-11
OPEN/LOG_FILE, 5--11
PRINT, 7-3
program development, 8-1 t
qualifier defaults, 2-7
RECALL, 1-16
RENAME, 3-32 to 3-35
REQUEST, 4-20
RSX, B--6t
RT11, B-3t
RUN, 8-47
SET, 4-16 to 4-19
SET/LOG]ILE, 5--15
SET ENTRY, 7-14
SET FILE, 3-77
SET HOST, 1-28
SET PASSWORD, 4-17
SET PROMPT, 4-19
SET TERMINAL, 5-4 to 5--10
SHOW, 4-1 to 4-15
SHOW ACCOUNT, 4-14
SHOW DEVICE, 6-17
SHOW DEVICE/ALLOCATED, 6-17
SHOW DISKS, 6-17
SHOW ENTRY, 7-10
SHOW JOB, 4-9
SHOW NETWORK, 1-28
SHOW PORT, 4-11
SHOW QUEUE, 7-18
SHOW SYSTEM, 4-13
SHOW TERMINAL, 5--2
SHOW USER, 4-8
SORT, 3--56 to 3--61
SUBMIT, 7-7
terms used in formats, 2-21

Commands (Cont.)
TYPE, 3-16 to 3-18
using qualifiers, 1-13
Comments
entering, 2-5
Compiling programs, 8-3
ICONFIRM qualifier
APPEND command, 3--37
COPY command, 3-25
DELETE command, 3-19
RENAME command, 3-32
SET PROTECTION command, 3-74
TYPE command, 3--16
ICONTIGUOUS qualifier
COPY command, 3-25
CREATE command, 3-2
MERGE command, 3--63
SORT command, 3--57
Continuation character, 2-4
ICONTINUATIONS=n qualifier
FORTRAN/F77 command, 8-22
Control keys
CTRUC, 3--16
CTRUO, 3--16
Ctrl/Q, 1--6
CTRUQ, 3--16
CTRUS, 1-6, 3--16
Ctrl/U, 1-3
ICONTROL qualifier
SET TERMINAL command, 5--5
ICONVERT qualifier
PRINT command, 7-3
ICOPIES=n qualifier
PRINT command, 7-3
COPY command, 3-23 to 3-31
IALLOCATION=n qualifier, 3--25
IBEFORE=date qualifier, 3--25
IBLOCK_SIZE=n qualifier, 3--25
ICLUSTER_SIZE=n qualifier, 3-25
ICON FIRM qualifier, 3--25
ICONTIGUOUS qualifier, 3-25
ICREATED qualifier, 3-25
IMODIFIED qualifier, 3-25
IOVERLAY qualifier, 3-25
IPOSITION qualifier, 3--25
IPROTECTION=n qualifier, 3--25
IQUERY qualifier, 3-25
IREPLACE qualifier, 3--25
IRETAIN_DATES qualifier, 3-25
ISELECT=SIZE qualifier, 3-25
ISINCE=date qualifier, 3-25
ICPU_LlMIT=n qualifier
SET ENTRY command, 7-14
SUBMIT command, 7-7
CREATE command, 3--2 to 3-4
IALLOCATION=n qualifier, 3--2
ICLUSTER_SIZE=n qualifier, 3-2
ICONTIGUOUS qualifier, 3-2
IPOSITION qualifier, 3--2
IPROTECTION=n qualifier, 3--2
IREPLACE qualifier, 3--2
ICREATED qualifier
APPEND command, 3--37
BACKUP command, 3-40
COPY command, 3-25
DELETE command, 3-19
DIRECTORY command, 3--9

Index-3

ICREATED qualifier (Cont.)
RENAME command, 3-32
RESTORE/DIRECTORY command, 3-54
RESTORE command, 3-48
TYPE command, 3-16
ICREATE qualifier
EDIT command, 3-5
ICRFlll qualifier
SET TERMINAL command, 5-5
ICROSS_REFERENCE qualifier
COBOL command, 8-14
CtrVA, 1-18
CtrVB, 1-18
CTRUC key, 3-16
CtrVD, 1-18
CtrVE, 1-18
CtrVF, 1-18
CtrVH, 1-18
CtrVJ, 1-18
CtrVN, 1-18
CTRUQ key, 3-16
CtrVR, 1-18
CTRUS key, 3-16
CTRUT key, 4-10
to show job status, 4-10
CtrVU, 1-18
Ctrl keys
see control keys

o
Date and time formats, 2-11
absolute, 2-11
relative, 2-13
IDATE qualifier
DIRECTORY command, 3-9
Dates
format for entering, 2-11
DCl
default keyboard monitor, 1-8
using command qualifiers, 1-13
DCl command descriptions
RESTORE, 3-52
DEAllOCATE command, 6--10
DEASSIGN command, 6--23
IDEBUG qualifier
COBOL command, 8-14
DIBOl command, 8-19
DECnetiE
using, 1-26 to 1-29
Default
keyboard monitor, 1-8
IDEFAUlT qualifier
SET PROTECTION command, 3-74
IDEFINE qualifier
CC Command, 8-8
IDElETABlE qualifier
SET FilE command, 3-77
DELETE/ENTRY command, 7-17
IAll qualifier, 7-17
IBATCH qualifier, 7-17
IPRINT qualifier, 7-17
DELETE command, 3-19 to 3-22
IBEFORE=CIate qualifier, 3-19
ICONFIRM qualifier, 3-19
ICREATED qualifier, 3-19
IERASE qualifier, 3-19

Index-4

DELETE command (Cont.)
IlOG qualifier, 3-19
IMODIFIED qualifier, 3-19
IQUERY qualifier, 3-19
ISElECT=SIZE qualifier, 3-19
ISINCE=date qualifier, 3-19
IWARNINGS qualifier, 3-19
DELETE key, 1-4
IDElETE qualifier
PRINT command, 7-3
SUBMIT command, 7-7
IDELIMITER qualifier
SET TERMINAL command, 5-5
IDENSITY=n qualifier
INITIALIZE command, 6--16
MOUNT command, 6--11
Detached jobs, 4-6
IDETACHED qualifier
SHOW JOB command, 4-9
SHOW USER command, 4-8
Devices
AllOCATE command, 6--8
ASSIGN command, 6--20
DEAllOCATE command, 6--10
DEASSIGN command, 6--23
disks, 6-4 to 6--5
DISMOUNT command, 6--16
INITIALIZE command, 6--14
logical names, 6--18 to 6--23
magnetic tape, 6-6 to 6--7
MOUNT command, 6--11
names, 6--1, 6--2t
physical, 6--1 to 6--18
SHOW command, 6--17
specifying, 6--1
table of commands, 6--1t
IDEVICE_TYPE qualifier
SET TERMINAL command, 5-5
IDIAGNOSTICS qualifier
COBOL command, 8-14
DIBOl-11 programming, 8-19
DIBOl command, 8-19
IDEBUG qualifier, 8-19
ILiST qualifier, 8-19
INOLIST qualifier, 8-19
INOOBJECT qualifier, 8-19
INOWARNINGS qualifier, 8-19
IOBJECT qualifier, 8-19
IOPTIMIZE qualifier, 8-19
ISTANDARD qualifier, 6--19
IWARNINGS qualifier, 8-19
DIFFERENCES command, 3-68 to 3-70
IIGNORE=BlANKLINES qualifier, 3-68
IMATCH=size qualifier, 3-68
IMAXIMUM_DIFFERENCES=n qualifier, 3-68
IOUTPUT=file-spec qualifier, 3-68
Directory, 1-19
DIRECTORY command, 3-9 to 3-15
IBEFORE=date qualifier, 3-9
IBRIEF qualifier, 3-9
ICREATED qualifier, 3-9
IDATE qualifier, 3-9
IFUll qualifier, 3-9
IMODIFIED qualifier, 3-9
INODATE qualifier, 3-9
INOSIZE qualifier, 3-9
IPROTECTION qualifier, 3-9

DIRECTORY command (Cont.)
ISELECT=SIZE qualifier, 3-9
ISINCE=date qualifier, 3-9
ISIZE qualifier, 3-9
ITOTAL qualifier, 3-9
IDISABLE qualifier
OPEN/LOG_FILE command, 5-12
SET/LOG_FILE command, 5-15
Disk quota, 1-25 to 1-26
Disks, 6--4 to 6-5
private, 6-5
public, 6--4
system, 6--4
DISMOUNT command, 6-16
Dollar sign ($) prompt, 1-7
DOS format, 6-6
Down Arrow, 1-18
IDUPLICATES qualifier
MERGE command, 3-63
SORT command, 3-57
ID_LlNES qualifier
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25

E
Echo on read, 1-9
EDIT command, 3-5 to 3-8
ICOMMAND=file-spec qualifier, 3-5
ICREATE qualifier, 3-5
IEDT qualifier, 3-5
IFORMAT=STREAM qualifier, 3-5
IFORMAT=VARIABLE qualifier, 3-5
IJOURNAL=[file-spec) qualifier, 3-5
INOCOMMAND qualifier, 3-5
INOJOURNAL qualifier, 3-5
INOOUTPUT qualifier, 3-5
10UTPUT=file-spec qualifier, 3-5
IRECOVER qualifier, 3-5
Editing
command line, 1-14
multiline commands, 1-18
EDT editor, 3-5 to 3-8
IEDT qualifier
EDIT command, 3-5
lEIGHT_BIT qualifier
SET TERMINAL command, 5-5
IEMT_LOGGING qualifier
SHOW SYSTEM command, 4-13
IENABLE qualifier
OPEN/LOG_FILE command, 5-12
SET/LOG_FILE command, 5-15
lEND qualifier
BACKUP command, 3-40
RESTORE/DIRECTORY command, 3-54
RESTORE command, 3-49
Entry
number, 7-2
specification, 7-2
IENVIRONMENT=([NO)FPU, [NO)PIC) qualifier
CC Command, 8-8
IERASE qualifier
DELETE command, 3-19
RECALL command, 1-16
Error messages, A-1
DCL, A-1t to A-28t
use of ? and % characters, A-1

IESCAPE_SEQUENCE qualifier
SET TERMINAL command, 5-5
Exclamation point
as comment character, 2-5
IEXCLUDE qualifier
BACKUP command, 3-40
RESTORE/DIRECTORY command, 3-54
RESTORE command, 3-49
Executable file, 8-3

F
F12, 1-18
F13, 1-18
F14, 1-18
IFEED qualifier
PRINT command, 7-3
Files
appending, 3-36 to 3-38
commands, 3-1t
comparing, 3-68 to 3-70
copying, 3-23 to 3-31
creating, 1-20, 3-2 to 3-8
deleting, 3-19 to 3-22
displaying, 1-20,3-9 to 3-18
merging, 3-62 to 3-67
names and types, 1-22
preallocating, 3-2
protecting, 3-71 to 3-76
protection codes, 1-24
renaming, 3-32 to 3-35
RSTS types, 1-24t
sorting, 3-56 to 3-61
specifying, 1-21
specifying lists of, 2-6
specifying RSTS/E, 8-6
using and maintaining, 1-19 to 1-25
using Wildcards, 1-25
FILES
Backup, 3-39
IFILESIZE switch, 8-7
IFILES qualifier
SHOW ENTRY command, 7-10
IFILE_DATA qualifier
RESTORE command, 3-49
IFLAG_PAGES qualifier
PRINT command, 7-3
IFORMAT=ANSI qualifier
INITIALIZE command, 6-16
MOUNT command, 6-11
IFORMAT=DOS qualifier
INITIALIZE command, 6-16
MOUNT command, 6-11
IFORMAT=FOREIGN qualifier
MOUNT command, 6-11
IFORMAT=STREAM qualifier
EDIT command, 3-5
IFORMAT=VARIABLE qualifier
EDIT command, 3-5
IFORMAT qualifier
MERGE command, 3-63
SORT command, 3-57
IFORMS=form-name qualifier
PRINT command, 7-3
SET ENTRY command, 7-14
IFORM_FEED qualifier
SET TERMINAL command, 5-5

Index-5

FORTRAN/F77 command
/CHECK qualifier, 8-22
/CONTINUATIONS=n qualifier, 8-22
/D_LlNES qualifier, 8-22
/14 qualifier, 8-22
/IDENTIFICATION qualifier, 8-22
/LiST qualifier, 8-22
/MACHINE_CODE qualifier, 8-22
/NOLIST qualifier, 8-22
/NOOBJECT qualifier, 8-25
/OBJECT qualifier, 8-22
/OPTIMIZE qualifier, 8-22
/STANDARD qualifier, 8-22
/WARNINGS qualifier, 8-22, 8-25
/WORK_FILES=n qualifier, 8-22, 8-25
FORTRAN/FOR command
/CODE qualifier, 8-25
/D_LlNES qualifier, 8-25
/14 qualifier, 8-25
/LiNENUMBERS qualifier, 8-25
/LiST qualifier, 8-25
/MACHINE_CODE qualifier, 8-25
/NOOBJECT qualifier, 8-25
/OBJECT qualifier, 8-25
/OPTIMIZE qualifier, 8-25
/WARNINGS qualifier, 8-25
FORTRAN commands, 8-21
FORTRAN programming, 8-21
/FULL qualifier
DIRECTORY command, 3-9
RESTORE/DIRECTORY command, 3-55
SHOW ACCOUNT command, 4-14
SHOW ENTRY command, 7-10
SHOW QUEUE command, 7-18
SHOW TERMINAL command, 5-2
Function keys
see Keys

H
/HARDCOPY qualifier
SET TERMINAL command, 5-5
HELLO command, 1-6
HELP command, 1-10 to 1-12
/HOLD qualifier
PRINT command, 7--3
SET ENTRY command, 7-14
SUBMIT command, 7-7
/HOST_SYNC qualifier
SET TERMINAL command, 5-5
Hyphen
as continuation character, 2-4

/14 qualifier
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
/IDENTIFICATION qualifier
FORTRAN/F77 command, 8-22
/lGNORE=BLANKLINES qualifier
DIFFERENCES command, 3-68
/IGNORE qualifier
SET FILE command, 3-77
/INCLUDE qualifier
BACKUP command, 3-41

Index-6

/INCLUDE qualifier (Cont.)
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-49
/INDEXED_SEQUENTIAL qualifier
MERGE command, 3-63
SORT command, 3-57
!INITIALIZE
Interaction During BACKUP, 3-41t
INITIALIZE command, &-14
/DENSITY=n qualifier, &-16
/FORMAT=ANSI qualifier, &-16
/FORMAT=DOS qualifier, &-16
/INITIALIZE qualifier
BACKUP command, 3-41
RESTORE command, 3-49
/INQUIRE qualifier
SET TERMINAL command, 5-5
/INSERT qualifier
SET TERMINAL command, 5-5
/INTERACTIVE qualifier
SHOW/PORT command, 4-12
/IN_LABEL qualifier
BACKUP command, 3-41
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-49

J
Jobs
attached, 4-6
detached, 4-6
/JOB_COUNT=n qualifier
PRINT command, 7-3
SET ENTRY command, 7-14
/JOURNAl=[file-spec] qualifier
EDIT command, 3-5

K
/KATAKANA qualifier
SET TERMINAL command, 5-5
Keyboard monitor
default, 1-8
/KEY qualifier
MERGE command, 3-63
SORT command, 3-57
Keys, 1-6t
ALTMODE, 1-6t
BACKSPACE, 1-18
Command line editing, 1-18
BACKSPACE, 1-18
CtrVA, 1-18
CtrVB, 1-18
CtrVD, 1-18
CtrVE, 1-18
CtrVF, 1-18
CtrVH, 1-18
CtrVJ, 1-18
CtrVN, 1-18
CtrVR, 1-18
CtrVU, 1-18
Down Arrow, 1-18
F12, 1-18
F13, 1-18
F14, 1-18
Left Arrow, 1-18
LINE FEED, 1-18

Keys
Command line editing (Cont.)
Right Arrow, 1-18
Up Arrow, 1-18
Command recall, 1-18
BACKSPACE, 1-18
Ctrl/A, 1-18
Ctrl/B, 1-18
Ctrl/D, 1-18
Ctrl/E, 1-18
Ctrl/F, 1-18
Ctrl/H, 1-18
Ctrl/J, 1-18
CtrllN, 1-18
Ctrl/R, 1-18
Ctrl/U, 1-18
Down Arrow, 1-18
F12, 1-18
F13, 1-18
F14, 1-18
left Arrow, 1-18
LINE FEED, 1-18
Right Arrow, 1-18
Up Arrow, 1-18
CTRUC, 1-6t, 3-16
CTRUI, 1-6t
CTRUJ, 1-6t
CTRUl, 1-6t
CTRUO, 1-6t, 3-16
CTRUQ, 1-6, 1-6t, 3-16
CTRUR, 1-6t
CTRUS, 1-6, 1-6t, 3-16
CTRUT, 1-6t, 4-10
CtrllU, 1-3
CTRUU, 1-6t
CTRUX, 1-6t
CTRUZ, 1-6t
DELETE, 1-4, 1-6t
Down Arrow, 1-18
ESCAPE, 1-6t
F12, 1-18
F13, 1-18
F14, 1-18
FORM FEED, 1-6t
HOLD SCREEN, 1-6t
left Arrow, 1-18
LINE FEED, 1-6t, 1-18
No Scroll, 1-6
NO SCROll, 3-16
RETURN, 1-4, 1-6t
Right Arrow, 1-18
RUBOUT, 1-6t
TAB, 1-6t
Up Arrow, 1-18
Keywords
abbreviating, 2-5
TODAY, 2-11
TOMORROW, 2-11
YESTERDAY, 2-11

L
language qualifiers, 8-32t
lLAT qualifier
SHOW/PORT command, 4-12
left Arrow key, 1-18

ILiBRARY qualifier
MACRO command, 8-28
LINE FEED, 1-18
ILiNENUMBERS qualifier
FORTRAN/FOR command, 8-25
ILlNE_EDITING qualifier
SET TERMINAL command, 5-5
LINK command, 8-30 to 8-46
qualifiers, 8-30 to 8-46
ILiST qualifier
COBOL command, 8-14
DIBOl command, 8-19
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
MACRO command, 8-28
ILiST]llE qualifier
BACKUP command, 3-41
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-49
IlOADABlE_CHARACTERS qualifier
SET TERMINAL command, 5-5
IlOAD_Flll qualifier
MERGE command, 3-63
SORT command, 3-57
IlOCAl_ECHO qualifier
SET TERMINAL command, 5-5
log file
of terminal session, 5-11 to 5-16
logical devices
see logical names
logical names, 6-18 to 6-23
ASSIGN command, 6-20
DEASSIGN command, 6-23
overriding, 6-19
specifying, 6-18
systemwide, 6-19
table of commands, 6-1t
user, 6-19
login
procedure, 1-6 to 1-8
lOGIN.COM file, 1-9 to 1-10
system and user, 1-9fg
lOGIN command, 1-6
lOGOUT command, 1-12 to 1-13
logout procedure, 1-12 to 1-13
IlOG qualifier
APPEND command, 3-37
COPY command, 3-25
DELETE command, 3-19
RENAME command, 3-B2
SET FilE command, 3-77
SET PASSWORD command, 4-17
SET PROTECTION command, 3-74
TYPE command, 3-16
IlOG_DElETE qualifier
SUBMIT command, 7-7
IlOG_FllEdile-spec qualifier
SUBMIT command, 7-7
IlOG_FllE qualifier
SET PROMPT command, 4-19
IlOG_QUEUE=queue-name qualifier
SUBMIT command, 7-7
IlOWERCASE qualifier
SET TERMINAL command, 5-5

Index-7

M
IMACHINE_CODE qualifier
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
MACRO-11 programming, 8-28
MACRO assembler, 8-3
MACRO command
ICROSS_REFERENCE qualifier, 8-28
ILiBRARY qualifier, 8-28
lUST qualifier, 8-28
INOUST qualifier, 8-28
INOOBJECT qualifier, 8-28
IOBJECT qualifier, 8-28
MACRO commands, 8-28
Magnetic tape, 6-6 to 8-7
ANSI and DOS format, 8-6
density, 8-6
IMAP qualifier
COBOL command, 8-14
IMATCH=size qualifier
DIFFERENCES command, 3-68
IMAXIMUM_DIFFERENCES=n qualifier
DIFFERENCES command, 3-68
Memory map file sample, 8-46ex
MERGE command, 3-62 to 3-67
IALLOCATION qualifier, 3-63
IBUCKET_SIZE qualifier, 3-63
ICHECK_SEQUENCE qualifier, 3-63
ICOLLATiNG_SEQUENCE qualilier, 3-63
ICONTIGUOUS qualifier, 3-63
IDUPUCATES qualifier, 3-63
IFORMAT qualifier, 3-63
IINDEXED_SEQUENTIAL qualifier, 3-63
IKEY qualifier, 3--63
ILOAD_FILL qualifier, 3-63
IOVERLAY qualifier, 3-63
IPROCESS qualifier, 3-63
IRELATIVE qualifier, 3--63
ISEQUENTIAL qualifier, 3-63
ISHAREABLE qualifier, 3-63
ISPECIFICATION qualifier, 3-63
ISTABlE qualifier, 3-63
ISTATISTICS qualifier, 3-63
/TREE_SPACE qualifier, 3-63
IWORK_FllES qualifier, 3-63
IMODE switch, 8--10
IMODIFIED qualifier
APPEND command, 3--37
BACKUP command, 3-40
COPY command, 3-25
DELETE command, 3-19
DIRECTORY command, 3-9
RENAME command, 3-32
RESTORE/DIRECTORY command, 3-54
RESTORE command, 3-48
SET PROTECTION command, 3-74
TYPE command, 3-16
MOUNT command, 8-11
IOENSITY=n qualifier, 8-11
IFORMAT=ANSI qualifier, 8-11
IFORMAT =DOS qualifier, 8-11
IFORMAT=FOREIGN qualifier, 8-11
IPRIVATE qualifier, 8-11
ISHARE qualifier, 8-11
IWRITE qualifier, 8-11

Index-8

Multiline commands
editing, 1-18

N
INAME=entry-name qualifier
PRINT command, 7-3
SUBMIT command, 7-7
INAMES=aa qualifier
COBOL command, 8-14
Network
using, 1-26 10 1-29
INOCOMMAND qualifier
EDIT command, 3-5
INOCONTIGUOUS qualifier
SET FilE command, 3-77
INODATE qualifier
DIRECTORY command, 3-9
INODIAGNOSTICS qualifier
COBOL command, 8--14
INOJOURNAL qualifier
EDIT command, 3-5
INOLIST qualifier
COBOL command, 8-14
DIBOl command, 8-19
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
MACRO command, 8-28
Nonalphanumeric characters, 2-101
INOOBJECT qualifier
COBOL command, 8-14
DIBOl command, 8-19
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
MACRO command, 8-28
INOOPTIMIZE qualifier
COBOL command, 8-14
INOOUTPUT qualifier
EDIT command, 3-5
NORMAL mode, 1-29
No Scroll key, 1-6
NO SCROLL key, 3-16
INOSIZE qualifier
DIRECTORY command, 3-9
INOSTANDARD=option qualifier
COBOL command, 8-14
INOTIFY qualifier
PRINT command, 7-3
SUBMIT command, 7-7
INOWARNINGS qualifier
DIBOL command, 8-19
I[NOJERROR_UMIT[=qualifier] qualifier
CC Command, 8-8
I[NOJINCLUDE_DIRECTORY qualifier
CC Command, 8-8
I[NO!UST[=file-spec] qualifier
CC Command, 8-8
I[NOjMACRO[dile-spec! qualifier
CC Command, 8-8
I[NOjMEMORY[=qualifier] qualifier
CC Command, 8-8
I[NOIMODULE qualifier
CC Command, 8-8
I[NOJOBJECTI=file-spec] qualifier
CC Command, 8-8
I[NO]STAN DARDI=( option, ... )] qualifier
CC Command, 8-8

I[NO]TERMINAL[=[NO)SOURCE) qualifier
CC Command. 8-8
I[NO]TITLE=(identifier) qualifier
CC Command. 8-8
I[NO)UNDEFINE=(identifier[. ... ]) qualifier
CC Command. 8-8
I[NO)WARNINGSl=(option •... )) qualifier
CC Command. 8-8
I[NO)WORK_FILE_SIZE qualifier
CC Command. 8-8

o
Object module. 8-3
IOBJECT qualifier
COBOL command. 8-14
DIBOL command. 8-19
FORTRAN/F77 command. 8-22
FORTRAN/FOR command. 8-25
MACRO command. 8-28
IOCCURRENCE qualifier
BACKUP/DIRECTORY command. 3--46
RESTORE/DIRECTORY command. 3-55
RESTORE command. 3--49
ODT mode. 1-29
OPEN/LOG]ILE command. 5-11
IAPPEND qualifier. 5-12
IDISABLE qualifier. 5-12
IENABLE qualifier. 5-12
IREPLACE qualifier. 5-12
!TIME_STAMP qualifier. 5-12
IOPTIMIZE qualifier
COBOL command. 8-14
DIBOL command. 8-19
FORTRAN/F77 command. 8-22
FORTRAN/FOR command. 8-25
IOUTPUT=file-spec qualifier
DIFFERENCES command. 3-68
DIRECTORY command. 3-9
EDIT command. 3-5
IOUTPUT qualifier
RESTORE/DIRECTORY command. 3-55
RESTORE command. 3-50
SHOW/PORT command. 4-12
SHOW ACCOUNT command. 4-14
SHOW ENTRY command. 7-10
SHOW JOB command. 4-9
SHOW QUEUE command. 7-18
SHOW SYSTEM command. 4-13
SHOW TERMINAL command. 5-2
SHOW USER command. 4-8
lOUT_LABEL
Interaction During BACKUP. 3--41t
lOUT_LABEL qualifier
BACKUP command. 3--41
RESTORE command. 3-50
Overlay
concatenated files. 8-45
in memory. 8-40fg
paths. 8-41fg
IOVERLAY qualifier
COPY command. 3-25
MERGE command. 3-63
SORT command. 3-57
Overlays. 8-37 to 8-46
IOVERSTRIKE qualifier
SET TERMINAL command. 5-5

IOWNER=ppn qualifier
PRINT command. 7-3
SUBMIT command. 7-7

p
IPAGE_L1MIT=n qualifier
PRINT command. 7-3
SET ENTRY command. 7-14
Parameters
abbreviating. 2-6
IPARAMETERS qualifier
SUBMIT command. 7-7
IPARITY qualifier
SET TERMINAL command. 5-5
Password
changing your own. 4-17
guidelines. 1-2
PBS
see Print/Batch Services
commands. 7-1t
specifying entries. 2-6
Peripheral devices
see physical devices
IPERMANENT qualifier
SHOW TERMINAL command. 5-2
Physical devices. 6-1 to 6-18
ALLOCATE command. 6-8
DEALLOCATE command. 6-10
disks. 6-4 to 6-5
DISMOUNT command. 6-16
INITIALIZE command. 6-14
magnetic tape. 6-6 to 6-7
MOUNT command, 6-11
names. 6-1. 6-2t
SHOW command. 6-17
specifying. 6-1
IPLACED qualifier
SET FILE command. 3-77
IPOSITION qualifier
COPY command. 3-25
CREATE command. 3-2
IPOSITION switch. 8-9
PPN
see project-programmer number
Preallocating files. 3-2
Print/Batch Services (PBS). 7-1 to 7-19
DELETE/ENTRY command. 7-17
entry-number. 7-2
entry specification. 7-2
print and batch queues. 7-1
PRINT command. 7-3
SET ENTRY command. 7-14
SHOW ENTRY command. 7-10
SHOW QUEUE command. 7-18
SUBMIT command. 7-7
PRINT command. 7-3
IAFTER=date:time qualifier. 7-13
IFORMS=form-name qualifier. 7-13
IHOLD qualifier. 7-3
IJOB_COUNT=n qualifier. 7-13
INAME=entry-name qualifier. 7-13
INOTIFY qualifier. 7-3
IWRAP qualifier. 7-13
IPRINTER_PORT qualifier
SET TERMINAL command. 5-5

Index-9

/PRINT qualifier
DELETE/ENTRY command, 7-17
SET ENTRY command, 7-14
SHOW ENTRY command, 7-10
SHOW QUEUE command, 7-18
/PRIORITY=n qualifier
PRINT command, 7-3
SET ENTRY command, 7-14
/PRIVATE qualifier
MOUNT command, 6-11
Privileges, 1-1
/PROCESS qualifier
MERGE command, 3--63
SORT command, 3-57
Program development commands, 8-1t
Programming
BASIC-PLUS, 8-7
BASIC-PlUS-2, 8-7
CC, 8-8
COBOl-81, 8-14
DIBOl-11, 8-19
FORTRAN, 8-21
MACRO-11, 8-28
RSX based, 8-5
RT11 based, 8-5
Programs
compiling, 8-3
creating, 8-2
linking, 8-3, 8-30 to 8-46
running, 1-26, 8-47
testing, 8-4
Project-programmer number (PPN), 1-2
$ prompt, 1-7
Prompt
changing your text, 4-19
/PROMPT qualifier
BACKUP command, 3-42
REQUEST command, 4-20
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-50
Prompts
Dollar sign ($), 1-7
Ready, 1-8
Protection
of files on tape, 6-6
/PROTECTION=n qualifier
COPY command, 3-25
CREATE command, 3-2
RENAME command, 3-32
SET FilE command, 3-77
Protection codes, 1-24, 3-71 to 3-76
common, 3-73t
for executable files, 3-72t
for nonexecutable files, 3-72t
/PROTECTION qualifier
DIRECTORY command, 3-9
/PROTECT switch, B-7
Public disk structure, 6-5

Q
Qualifiers
abbreviating, 2--6
/AFTER, 2-11
APPEND command, 3-37
BASIC command, 8-7
/BEFORE, 2-11

Index-10

Qualifiers (Cont.)
CC Command, 8-8
COBOL command, 8-14
COPY command, 3-25
CREATE command, 3-2
defaults, 2-7
DELETE/ENTRY command, 7-17
DELETE command, 3-19
DIBOl command, 8-19
DIFFERENCES command, 3-68
DIRECTORY command, 3-9
entering, 2-7
entering arguments, 2-8
FORTRAN/FOR command, 8-25
INITIALIZE command, 6-16
LINK command, 8-30 to 8-46
MACRO command, 8-28
MERGE command, 3-63
MOUNT command, 6-11
OPEN/lOG_FilE command, 5-12
RENAME command, 3-32
SET/lOG_FilE, 5-15
SET ENTRY command, 7-14
SET FilE command, 3-77
SET PROTECTION command, 3-74
SET TERMINAL command, 5-5
SHOW ACCOUNT command, 4-14
SHOW ENTRY command, 7-10
SHOW JOB command, 4-9
SHOW QUEUE command, 7-18
SHOW TERMINAL command, 5-2
SHOW USER command, 4-8
/SINCE, 2-11
SORT command, 3-57
SUBMIT command, 7-7
TYPE command, 3-16
using with DCl commands, 1-13
with EDIT command, 3-5
with FORTRAN/F77 command, 8-25
/QUERY qualifier
APPEND command, 3-37
BACKUP command, 3-42
COPY command, 3-25
DELETE command, 3-19
RENAME command, 3-32
RESTORE command, 3-50
SET PROTECTION command, 3-74
TYPE command, 3-16
Queue, 7-1
/QUEUE qualifier
PRINT command, 7-3
/QUEUE-queue-name qualifier
SUBMIT command, 7-7
Quota
disk, 1-6, 1-25

R
Ready prompt, 1-8
/READ_ONlY qualifier
EDIT command, 3-5
RECAll command, 1-16
/All qualifier, 1-16
/ERASE qualifier, 1-16
/RECAll qualifier
SET TERMINAL command, 5-5

IRECOVER qualifier
EDIT command, 3-5
IREGIS qualifier
SET TERMINAL command, 5-5
IRELATIVE qualifier
MERGE command, 3-{)3
SORT command, 3-57
IRELEASE qualifier
SET ENTRY command, 7-14
RENAME command, 3-32 to 3-35
IBEFORE=date qualifier, 3-32
ICON FIRM qualifier, 3-32
ICREATED qualifier, 3-32
ILOG qualifier, 3-32
IMODIFIED qualifier, 3-32
IPROTECTION=n qualifier, 3-32
IQUERY qualifier, 3-32
IREPLACE qualifier, 3-32
ISELECT=SIZE qualifier, 3-32
ISINCE=date qualifier, 3-32
IWARNINGS qualifier, 3-32
IREPLACE qualifier
COPY command, 3-25
CREATE command, 3-2
OPEN/LOG_FILE command, 5-12
RENAME command, 3-32
RESTORE command, 3-50
IREPLY qualifier
REQUEST command, 4-20
REQUEST command, 4-20
IPROMPT qualifier, 4-20
IREPLY qualifier, 4-20
ITIME_OUT qualifier, 4-20
IRESET qualifier
SET TERMINAL command, 5-5
RESTORE/DIRECTORY command
IBRIEF qualifier, 3-54
ICREATED qualifier, 3-54
lEND qualifier, 3-54
IEXCLUDE qualifier, 3-54
IFULL qualifier, 3-55
/INCLUDE qualifier, 3-55
/IN_LABEL qualifier, 3-55
ILlST_FILE qualifier, 3-55
IMODIFIED qualifier, 3-54
IOCCURRENCE qualifier, 3-55
IOUTPUT qualifier, 3-55
IPROMPT qualifier, 3-55
IREWIND qualifier, 3-55
ISELECT qualifier, 3-55
RESTORE command, 3-52
ICREATED qualifier, 3-48
lEND qualifier, 3-49
IEXCLUDE qualifier, 3-49
IFILE_DATA qualifier, 3-49
/INCLUDE qualifier, 3-49
/INITIALIZE qualifier, 3-49
/IN_LABEL qualifier, 3-49
IMODIFIED qualifier, 3-48
IOCCURRENCE qualifier, 3-49
IOUTPUT qualifier, 3-50
lOUT_LABEL qualifier, 3-50
IPROMPT qualifier, 3-50
IQUERY qualifier, 3-50
IREPLACE qualifier, 3-50
restrictions, 3-47
IREWIND qualifier, 3-51

RESTORE command (Cont.)
ISELECT qualifier, 3-51
!VERIFY qualifier, 3-51
Restrictions
RESTORE command, 3-47
IRETA IN_DATES qualifier
COpy command, 3-25
RETURN key, 1-4
IREWIND qualifier
BACKUP command, 3-42
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-51
Right Arrow key, 1-18
IRONLY switch, B-10
RSX
command environment, 1-8
commands, B-6t
RSX-based programming, 8-5
RT11
command environment, 1-8
commands, B-3t
RT11 and RSX program development commands,
8-51
RT11-based programming, 8-5
RUBOUT key
see DELETE key
RUN command, 8-47
Running a program, 1-26
IRUNTIME_SYSTEM=name qualifier
SET FILE command, 3-77

s
ISCOPE qualifier
SET TERMINAL command, 5-5
ISELECT=SIZE qualifier
APPEND command, 3-37
COpy command, 3-25
DELETE command, 3-19
DIRECTORY command, 3-9
RENAME command, 3-32
SET PROTECTION command, 3-74
TYPE command, 3-16
ISELECT qualifier
RESTORE/DIRECTORY command, 3-55
RESTORE command, 3-51
ISELECT_ERASE qualifier
SET TERMINAL command, 5-5
ISEQUENTIAL qualifier
MERGE command, 3-63
SORT command, 3-57
SET/LOG_FILE command, 5-15
IDISABLE qualifier, 5-15
IENABLE qualifier, 5-15
!TIME_STAMP qualifier, 5-15
SET command, 4-16 to 4-19
ENTRY, 7-14
HOST, 1-28
options, 4-16t
PASSWORD, 4-17
PROMPT, 4-19
TERMINAL, 5-4 to 5-10
SET CONTROL=C command, 4-16t
SET DATA command, 4-16t
SET ECHO command, 4-16t
SET ENTRY command, 4-161,7-14
IAFTER=date:time qualifier, 7-14

Index-11

SET ENTRY command (Cont.)
IALL qualifier, 7-14
IBATCH qualifier, 7-14
ICPU_LlMIT=n qualifier, 7-14
IFORMS=form-name qualifier, 7-14
IHOLD qualifier, 7-14
IJOB_COUNT=n qualifier, 7-14
IPAGE_LlMIT=n qualifier, 7-14
IPRIORITY=n qualifier, 7-14
IRELEASE qualifier, 7-14
!TIME_LlMIT=n qualifier, 7-14
SET FILE command, 3-n,4--16t
IBACKUP qualifier, 3-n
ICACHE qualifier, 3-n
IDELETABLE qualifier, 3-n
!IGNORE qualifier, 3-77
ILOG qualifier, 3-77
INOCONTIGUOUS qualifier, 3-77
IPLACED qualifier, 3-n
IPROTECTION=n qualifier, 3-n
IRUNTIME_SYSTEM=name qualifier, 3-77
SET HOST, 1-29
NORMAL mode, 1-29
ODT mode, 1-29
SET HOST command, 4--16t
SET LOG_FILE command, 4--16t
SET ON command, 4-16t
SET PASSWORD command, 4-16t, 4--17
ILOG qualifier, 4--17
SET PROMPT command, 4--19
ILOG_FILE qualifier, 4-19
SET PROTECTION command, 4--16t
IBEFORE=CIate qualifier, 3-74
ICON FIRM qualifier, 3-74
IDEFAULT qualifier, 3-74
ILOG qualifier, 3-74
IMODIFIED qualifier, 3-74
IQUERY qualifier, 3-74
ISELECT=SIZE qualifier, 3-74
ISINCE=date qualifier, 3-74
SET TERMINAL command, 4--16t, 5-4 to 5-10
IADVANCED_VIDEO qualifier, 5-5
IALT_MODE qualifier, 5-5
IANSI qualifier, 5-5
IBREAK qualifier, 5-5
IBROADCAST qualifier, 5-5
1132_COLUMNS qualifier, 5-5
ICONTROL qualifier, 5-5
ICRFILL qualifier, 5-5
IDELIMITER qualifier, 5-5
IDEVICE_TYPE qualifier, 5-5
lEIGHT_BIT qualifier, 5-5
IESCAPE_SEQUENCE qualifier, 5-5
IFORM_FEED qualifier, 5-5
IHARDCOPY qualifier, 5-5
IHOST_SYNC qualifier, 5-5
!INQUIRE qualifier, 5-5
!INSERT qualifier, 5-5
IKATAKANA qualifier, 5-5
ILlNE_EDITING qualifier, 5-5
ILOADABLE_CHARACTERS qualifier, 5-5
ILOCAL_ECHO qualifier, 5-5
ILOWERCASE qualifier, 5-5
IOVERSTRIKE qualifier, 5-5
IPRINTER_PORT qualifier, 5-5
IRECALL qualifier, 5-5
IREGIS qualifier, 5-5

Index-12

SET TERMINAL command (Cont.)
IRESET qualifier, 5-5
IRESUME qualifier, 5-5
ISCOPE qualifier, 5-5
ISELECT_ERASE qualifier, 5-5
ISETUP=file-name qualifier, 5-5
ISIXEL qualifier, 5-5
ISPEED qualifier, 5-5
/TAB qualifier, 5-5
ITTSYNC qualifier, 5-5
/TYPE=n qualifier, 5-5
IUPPERCASE qualifier, 5-5
IUP_ARROW qualifier, 5-5
IUSER_DEFINED_KEYS qualifier, 5-5
/wIDTH=n qualifier, 5-5
ISETUP=file-name qualifier
SET TERMINAL command, 5-5
SET VERIFY command, 4-16t
ISHAREABLE qualifier
MERGE command, 3-63
SORT command, 3-57
ISHARE qualifier
MOUNT command, 6--11
SHOW/PORT command
IALL qualifier, 4--12
fAPPLICATION qualifier, 4-12
flNTERACTIVE qualifier, 4--12
fLAT qualifier, 4-12
fOUTPUT qualifier, 4-12
ISHOW=MAP qualifier
COBOL command, 8-14
SHOW ACCOUNT command, 4-1t,4-14
IACCOUNTING_DATA qualifier, 4--14
IBRIEF qualifier, 4-14
IFULL qualifier, 4--14
IOUTPUT qualifier, 4-14
SHOW BUFFERS command, 4-1t
SHOW CACHE command, 4-1t
SHOW command, 4--1 to 4-15
ACCOUNT, 4-14
DEVICE, 6--17
DEVICE/ALLOCATED, 6--17
DISKS, 6--17
ENTRY, 7-10
JOB,4-9
NETWORK, 1-28
options, 4--1t
PORT, 4-11
QUEUE, 7-18
SYSTEM, 4-13
TERMINAL, 5-2
USER, 4--8
SHOW COUNTERS/LAT command, 4-H
SHOW DATE command, 4-1t
SHOW DAYTIME command, 4-1t
SHOW DEVICE/ALLOCATED
abbreviations, 6--17t
SHOW DEVICE/ALLOCATED command, 4-1t,6--17
SHOW DEVICE command, 4--1t, 6--17
SHOW DISKS
abbreviations, 6--17t
SHOW DISKS command, 4--1t,6--17
SHOW ENTRY command, 4--1t,7-10
IALL qualifier, 7-10
IBATCH qualifier, 7-10
IBRIEF qualifier, 7-10
IFILES qualifier, 7-10

SHOW ENTRY command (Cont.)
IFUll qualifier, 7-10
IOUTPUT qualifier, 7-10
IPRINT qualifier, 7-10
ISTATUS qualifier, 7-10
SHOW FilE command, 4-11
SHOW JOB/PRIVILEGES command, 4-1t
SHOW JOB command, 4-H,4-9
abbreviations, 4-41
IAll qualifier, 4-9
IATTACHED qualifier, 4-9
IDETACHED qualifier, 4-9
IOUTPUT qualifier, 4-9
ITERMINAl=KBn: qualifier, 4-9
SHOW LIBRARY command, 4-H
SHOWlOGICAlS command, 4-H
SHOW MEMORY command, 4-it
SHOW NETWORK command, 4-1t
SHOW NODEILAT command, 4-it
SHOW OPERATOR_SERVICES command, 4-H
SHOW PORT command, 4-U, 4-11
SHOW PRINTER command, 4-H
ISHOW qualifier
COBOL command, 8-14
SHOW QUEUE command, 4-it,7-18
IAll qualifier, 7-18
IBATCH qualifier, 7-18
IBRIEF qualifier, 7-18
IFULl qualifier, 7-18
IOUTPUT qualifier, 7-18
IPRINT qualifier, 7-18
SHOW RECEIVERS command, 4-H
SHOW RUNTIME_SYSTEMS command, 4-11
SHOW SERVER command, 4-H
SHOW SERVICES/lAT command, 4-1t
SHOW SESSIONS command, 4-11
SHOW SYMBOL command, 4-1t
SHOW SYSTEM command, 4-1t,4-13
IEMT_lOGGINGS qualifier, 4-13
IOUTPUT qualifier, 4-13
SHOW TERMINAL command, 4-1t, 5-2
IAll qualifier, 5-2
IBRIEF qualifier, 5-2
IFUll qualifier, 5-2
IOUTPUT qualifier, 5-2
IPERMANENT qualifier, 5-2
SHOW TERMINAl_SERVERS/lAT command, 4-11
SHOW TIME command, 4-H
SHOW USER command, 4-1t,4-8
abbreviations, 4-4t
IAll qualifier, 4-8
IATTACHED qualifier, 4-8
IDETACHED qualifier, 4-8
IOUTPUT qualifier, 4-8
ITERMINAl=KBn: qualifier, 4-8
ISHOW[=option •... ] qualifier
CC Command. 8-8
ISINCE=date qualifier
APPEND command. 3--37
COpy command, 3-25
DELETE command. 3-19
DIRECTORY command, 3-9
RENAME command. 3-32
SET PROTECTION command, 3-74
TYPE command, 3-16
ISINCE qualifier, 2-11

ISIXEl qualifier
SET TERMINAL command, 5-5
ISIZE qualifier
DIRECTORY command, 3-9
SORT command, 3-56 to 3-61
IAllOCATION qualifier, 3-57
IBUCKET_SIZE qualifier, 3-57
ICOLLATING_SEQUENCE qualifier, 3-57
ICONTIGUOUS qualifier, 3-57
IDUPLICATES qualifier, 3-57
IFORMAT qualifier, 3-57
IINDEXED_SEQUENTIAl qualifier, 3-57
IKEY qualifier, 3-57
IlOAD_Flll qualifier, 3-57
IOVERLAY qualifier, 3-57
IPROCESS qualifier, 3-57
IRELATIVE qualifier, 3-57
ISEQUENTIAl qualifier, 3-57
ISHAREABlE qualifier, 3-57
ISPECIFICATION qualifier, 3-57
ISTABlE qualifier, 3-57
ISTATISTICS qualifier. 3-57
/TREE_SPACE qualifier, 3-57
IWORKJILES qualifier. 3-57
ISPECIFICATION qualifier
MERGE command. 3-63
SORT command. 3-57
ISPEED qualifier
SET TERMINAL command, 5-5
ISTABlE qualifier
MERGE command, 3-63
SORT command. 3-57
ISTANDARD=option qualifier
COBOL command. 8-14
ISTANDARD qualifier
DIBOl command. 8-19
FORTRAN/F77 command. 8--22
ISTATISTICS qualifier
MERGE command. 3-63
SORT command. 3-57
ISTATUS qualifier
SHOW ENTRY command. 7-10
SUBMIT command. 7-7
IAFTER=date:time qualifier. 7-7
ICPU_L1MIT=n qualifier. 7-7
IDElETE qualifier. 7-7
IHOLD qualifier, 7-7
IlOG_DElETE qualifier. 7-7
IlOG_FILE=file-spec qualifier. 7-7
IlOG_QUEUE=queue-name qualifier, 7-7
INAME=entry-name qualifier. 7-7
INOTIFY qualifier. 7-7
IOWNER=ppn qualifier. 7-7
IPARAMETERS=(parameter.... ) qualifier, 7-7
IPRIORITY=n qualifier. 7-7
IQUEUE=queue-name qualifier. 7-7
!TIME_LIMIT=n qualifier. 7-7
System disk. 6-4
System status display. 4-4. 4-4t
Systemwide logical names. 6-19

T
/TAB qualifier
SET TERMINAL command, 5-5
Tape density. 6-6
Task Builder. 8--31

Index-13

ITEMPORARY=device qualifier
COBOL command, 8-14
/TERMINAL=KBn: qualifier
SHOW JOB command, 4-9
SHOW USER command, 4-8
Terminal characteristics
displaying, 5-1, 5-2
setting, 5-1, 5-4 to 5-10
Terminal logging, 5-11 to 5-16
CLOSE/LOG_FILE, 5-14
OPEN/LOG_FILE, 5-11
SET/LOG_FILE, 5-15
Times
format for entering, 2-11
/TIME_LlMIT=n qualifier
SET ENTRY command, 7-14
SUBMIT command, 7-7
/TIME_OUT qualifier
REQUEST command, 4-20
/TIME_STAMP qualifier
OPEN/LOG FILE command, 5-12
SET/LOG_ALE command, 5-15
TODAY keyword, 2-11
TOMORROW keyword, 2-11
/TOTAL qualifier
DIRECTORY command, 3-9
/TREE_SPACE qualifier
MERGE command, 3-63
SORT command, 3-57
/TRUNCATE qualifier
COBOL command, 8-14
PRINT command, 7--3
/TTSYNC qualifier
SET TERMINAL command, 5-5
/TYPE=n qualifier
SET TERMINAL command, 5-5
Typeahead, 1-9
TYPE command, 3-16 to 3-18
/BEFORE=date qualifier, 3-16
/CONFIRM qualifier, 3-16
/CREATED qualifier, 3-16
/LOG qualifier, 3-16
/MODIFIED qualifier, 3-16
/QUERY qualifier, 3-16
/SELECT=SIZE qualifier, 3-16
/SINCE=date qualifier, 3-16

u
Underscore character
to override name precedence, 6-19
Up Arrow, 1-18
/UPPERCASE qualifier
SET TERMINAL command, 5-5
/UP_ARROW qualifier
SET TERMINAL command, 5-5
User logical names, 6-19
/USER DEFINED KEYS qualifier
SET TERMINAL command, 5-5

v
/VERIFY qualifier
BACKUP command, 3-43
RESTORE command, 3-51

Index-14

w
/WARNINGS qualifier
COBOL command, 8-14
DELETE command, 3-19
DIBOL command, 8-19
FORTRAN/F77 command, 8-22
FORTRAN/FOR command, 8-25
RENAME command, 3--32
/WIDTH=n qualifier
SET TERMINAL command, 5-5
Wildcards, 1-25
/WORK FILES=n qualifier
FORTRAN/F77 command, 8-22
/WORK FILES qualifier
MERGE command, 3-63
SORT command, 3-57
/WRAP qualifier
PRINT command, 7-3
/WRITE qualifier
MOUNT command, 6-11

y
YESTERDAY keyword, 2-1.1

How to Order Additional Documentation

Technical Support
If you need help deciding which documentation best meets your needs, call 800-343-4040 before placing
your electronic, telephone,· or direct mail order.

Electronic Orders
To place an order at the Electronic Store, dial 800-DEC-DEMO (800-332-3366) using a 1200- or 2400-baud
modem. If you need assistance using the Electronic Store, call 800-DIGITAL (800-344-4825).

Telephone and Direct Mail Orders
Your Location

Call

Contact

Continental USA,
Alaska, or Hawaii

800-DIGITAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

Puerto Rico

809-754-7575

Local Digital subsidiary

Canada

800-267-6215

Digital Equipment of Canada
Attn: DECdirect Operations KA02/2
P.O. Box 13000
100 Herzberg Road
Kanata, Ontario, Canada K2K 2A6

International
Internal1

Local Digital subsidiary or
approved distributor
USASSB Order Processing - WMOlE15
or

U.S. Area Software Supply Business
Digital Equipment Corporation
Westminster, Massachusetts 01473

IFor internal orders, you must submit an Internal Software Order Form (EN-01740-07).

Reader's Comments

RSTS/E User's Guide
AA-EZ12B-TC

Please use this postage-paid form to comment on this manual. If you require a written reply to a software
problem and are eligible to receive one under Software Performance Report (SPR) service, submit your
comments on an SPR form.
Thank you for your assistance.

I rate this manual's:
Accuracy (software works as manual says)
Completeness (enough information)
Clarity (easy to understand)
Organization (structure of subject matter)
Figures (useful)
Examples (useful)
Index (ability to find topic)
Page layout (easy to find information)

Excellent

Good

Fair

Poor

0
0
D
0
D
0
0
0

0
0
D
0
0
0
0
0

I would like to see morel1ess

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

Namefl'itle

Dept.

Company

Date

Mailing Address
Phone

- -

~ -

Do Not Tear - Fold Here and Tape - -

- -

BUSINESS REPLY MAil
FIRST- CLASS MAil PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

DIGITAL EQUIPMENT CORPORATION
CORPORATE USER PUBliCATIONS
CONTINENTAL BOULEVARD MK01-2/EI2
PO BOX 9501
MERRIMACK NH 03054-9982

I
I
I
I
I
I
I
I
i
I!!. " " II. II. " ,1.1. ,I II. L LI. ,I. ,I, " 1.11 I. " I
I
_ - _____________________ , I
01

Do Not Tear - Fold Here -

NO POSTAGE
NECESSARY
IF MAILED
INTHE
UNITED STATES

~DmDDmDTM

_ _ _ _ _ _ _ _

- -

I
I
I
I
I

I
I
I
III
I:='
I~

IJ$

g
(1)

Er
(1)

Reader's Comments

RSTS/E User's Guide
M-EZ12B-TC

Excellent

Good

Fair

Poor

0
0
0
0
0
0
0
0

I would like to see morelless

What I like best about this manual is

What I like least about this manual is

I found the following errors in this manual:
Page

Description

Additional comments or suggestions to improve this manual:

I am using Version _ _ _ of the software this manual describes.

NametTitle

Dept.

Company

Date

Mailing Address
Phone

Do Not Tear - Fold Here and Tape - - - - - - - - -

- -

- - - - -

- - - -

- -,

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

~DmDDmDTM

BUSINESS REPLY MAIL
FIRST- CLASS MAIL PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
CORPORATE USER PUBLICATIONS
CONTINENTAL BOULEVARD MK01-2/E12
PO BOX 9501
MERRIMACK NH 03054-9982

111 ••••• 11.11 •••• 1.1 •• 1•• 11.1 •• 1.1 •• 1•• 1••• 1.111 ••• 1
_______ -

Do Not Tear - Fold Here - - - - - - - - - - - - - - - - - - - - - - -

--"1

Printed in U.S.A.