Digital PDFs

AA-L672C-TC

July 1985

501 pages

Original

18MB

Document:	RSX-11M Command Language Manual
Order Number:	AA-L672C-TC
Revision:	0
Pages:	501
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/RSX11M_V4.2_Jul85/AA-L672C-TC_RSX-11M_Command_Language_Manual_198507.pdf

OCR Text

RSX-11M
Command Language Manual
Order No. AA-L672C- TC

RSX-11M
Command Language Manual
Order No. AA-L672C-TC

RSX-11 M Version 4.2

digital equipment corporation · maynard, massachusetts

First Printing, October
Revised, November
Revised, April
Revised, July

1979
1981
1983
1985

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 be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that. is not supplied by Digital Equipment Corporation or its
affiliated companies.
Copyright

(§) 1979, 1981, 1983, 1985 by Digital Equipment Corporation
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:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-10
DECSYSTEM-20
DEC US
DECwriter

DIBOL
EduSystem
IAS
MAS SB US
MicroPDP-11
Micro/RSTS
Micro/RSX
PDP

PDT
RSTS
RSX
UNIBUS
VAX
VMS
VT
ZK2868

HOW TO ORDER ADDITIONAL DOCUMENTATION
In Continental USA and Puerto Rico call 800-258-1710
In New Hampshire, Alaska, and Hawaii call
In Canada call

603-884-6660

613-234-7726 (Ottawa-Hull)
800-267-6215 (all other Canadian)

DIRECT MAIL ORDERS (USA & PUERTO RICO)*
Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (CANADA)
Digital Equipment of Canada Ltd.
100 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital Equipment Corporation
PSG Business Manager
clo Digital's local subsidiary or
approved distributor

*Any prepaid order from Puerto Rico must be placed
with the local Digital subsidiary (809-754-7575)

Internal orders should be placed through the Software Distribution Center (SDC), Digital Equipment
Corporation, Northboro, Massachusetts 01532

CONTENTS
Page
vii

PREFACE

SUMMARY OF TECHNICAL CHANGES
CHAPTER 1

HOW TO USE DCL

1.1
RSX-llM AND DCL: BASIC CONCEPTS
THE DCL COMMAND LINE •
1. 2
1. 2.1
Prompting
• • • • • •
.
Qualifiers • • • • • •
1. 2. 2
HELP • • • • • • . •
1. 2. 3
MCR and DCL Commands •
1.2.4
Abbreviations
•
1. 2. 5
•
Numbers and Dates
•••••
1. 2. 6
Multiple Parameters • • • •
1. 2. 7
•
Underscore Character
1. 2. 8
Colon and Equal Sign •
1. 2. 9
Quoting Strings
1.2.10
1.2.11
ANSI File Names
DECnet and DCL • • • • • •
1.2.12
1.2.12.1
SET HOST • • • •
1.2.12.2
SHOW HOST
• • • •
1. 2. 13
Command Line Continuation
•
Comments in Command Lines
1. 2 .14
1.2.15
SET DEBUG • • • • • • • • •
Errors • . . • • • • • • • •
1.2.16
1. 3
FUNCTIONAL GROUPING OF DCL COMMANDS
The SET and SHOW Commands
1. 3.1
1. 3. 2
Terminal Operations
• • • •
Handling Files • • • • • • •
1. 3. 3
1. 3. 4
Handling Devices and Volumes
Program Development • • • •
1. 3. 5
1. 3. 6
Running Tasks
• • • •
•
System Control • • • • • • • • • •
1. 3. 7
1. 4
USING THE QUEUE MANAGER: PRINT JOBS
INDIRECT COMMAND FILES IN DCL
1. 5
DCL AND RSX-llM UTILITIES AND SYSTEM
1. 6
RSX-llM DCL AND VAX/VMS DCL • • • •
1. 7
CHAPTER 2

2.1
2.2
2.3
2.4
2.5
2.5.1
2.6
2.7
2.8
2.9
2.10
2.11
2.12
CHAPTER 3

3.1
3.1.1

• 1-1
• 1-2
• • • • • 1-3
• • • • .

• • 1-3

• • • • • • • 1-4
1-6
• • • •
• 1-7
• • • • • • • 1-8

• • • •

•
•
•
•
•

• • • • •
• • • • • •

. ••.
•••.
• • • •
• • • •
• • • •
••••
• • • •
TASKS •
• • • •

1-8
1-8
1-9
1-9
1-9
1-10
1-10
1-11
1-12
1-12
1-13
1-14
1-15
1-15
1-16
1-16
1-16
1-16
1-17
1-17
1-17
1-17
1-18
1-19

THE SET AND SHOW COMMANDS
SET AND SHOW TIME
SHOW MEMORY
SET AND SHOW TERMINAL • • • •
SHOW DEVICES
SHOW QUEUE •
SHOW PROCESSOR • • • • • •
SHOW ASSIGNMENTS •
SET AND SHOW DEFAULTS • • • • • •
SHOW TASKS • • • • • •
SHOW USERS • • • • • •
SET PROTECTION • • • •
S.ET AND SHOW SYSTEM/DIRECTORY
SET DEBUG • • • • • • • • • •

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

TERMINAL OPERATIONS
LOGGING IN AND LOGGING OUT
LOGIN • • • •
• • • •
iii

• 3-2
• 3-4

CONTENTS
3.1. 2
3.1. 3
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.3
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.5
3.5.1
3.6
3.7
3.8
3.8.1
3.8.2
CHAPTER 4
4.1
4.1.1
4. 1. 2
4.1. 3
4.1. 4
,4.1.5
4.1. 6
4.2
4.2.1
4.2.2
4.2.3
4.2.3.1
4.2.3.2
4.2.3.3
4.3
4.3.1
4.3.2
4.3.3
4.3.4
4.3.5
4.3.6
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.5
4.5.1
4.5.2
4.5.3
4.5.4

LOGOUT • • • • • • • • . . . . . . . . . .
ACNT, the Account File Maintenance Program
THE KEYBOARD • • • •
• • • •
• • •
RETURN and Command Line Length • • • • • •
Line Terminators • • • • •
DELETE Versus BACK SPACE •
CAPS LOCK and SHIFT
REPEAT • • • • • • •
. . . . . . . .
SCROLL and NO SCROLL •
Other Keys
• • • •
THE KEYPAD • • • • • •
THE CTRL KEY AND CONTROL CHARACTERS
• • • •
CTRL/C
• • • •
• • • • • •
CTRL/S and CTRL/Q
• • • •
• • •
CTRL/O •
• • • • •
CTRL/Z •
• . • • •
CTRL/U • .
• • • •
CTRL/R
• • • •
CTRL/X
CTRL/L =
Other Control Characters • • • • • •
HELP • • • • • • • • • • • •
Help File Format: Writing a Help File •
BROADCAST • • • • • • • • •
REQUEST • • • • • • • • • • •
SET AND SHOW TERMINAL
SET TERMINAL •
SHOW TERMINAL

•

•
•
•

. 3-8
• 3-9
• • 3-9
3-10
3-10
3-11
3-12
.
3-12
3-12
3-12
3-15
• 3-16
•
3-17
• 3-17
3-18
3-18
3-19
3-19
3-20
3-20
3-20
3-21
3-24
3-28
3-32
3-33
3-34
3-47

HANDLING FILES
FILES ON RSX-llM SYSTEMS • • • • •
• 4-1
File Ownership and Location
• • • • • 4-2
File Specification • • • • • • •
• • • . • . 4-2
Defaults in File Specifications
• • • • •
• 4-4
Wildcards in File Specifications • •
4-6
Date-Related Qualifiers
• • • • • •
• • • 4-8
File Protection and Volume Protection . • • • • 4-9
CREATING DIRECTORIES AND SEQUENTIAL FILES
4-10
CREATE • • • • • •
• • • •
4-11
CREATE/DIRECTORY • • • • •
• • • • •
4-13
EDIT • • • • •
4-15
EDIT[/EDT] • • • • • • •
4-16
EDIT/SLP • • •
• • • •
4-20
EDIT/EDI and EDIT/editor
• • • • • • • • 4-23
MAINTAINING A DIRECTORY
4-25
DIRECTORY
• • • • • • • •
4-26
DELETE •
• • • • • • • • • • • • • • • 4-35
PURGE
• • . •
• • • •
4-39
COPY • •
• • • • • 4-42
RENAME •
4-47
CONVERT
• • • • • • • •
• • • • •
4-50
OTHER FILE-RELATED COMMANDS
. • • • • •
4-56
TYPE • . • • • • • • •
• • • • • 4-57
PRINT • . • • • • • • • •
• • • •
4-60
APPEND • • • • • • • • •
4-70
DIFFERENCES
• • • • •
4-72
UNLOCK • . • • • • • •
• • • • • • • • 4-78
SET AND SHOW • • • • • • •
• • • •
4-79
SET DEFAULT
• • • • •. •
4-80
SHOW DEFAULT • • • • • • •
• • • • • •
4-82
SET PROTECTION
4-83
SET FILE • • • • • • • • • •
4-87

CONTENTS
CHAPTER 5

HANDLING DEVICES AND VOLUMES

5.1
5. 1.1
5.1. 2

DEVICES ON RSX-llM SYSTEMS •
5-1
Volumes and Devices
• 5-4
Physical Devices, Pseudo Devices, LUNs, and
Logical Names
• • • • • •
5-5
5.1.2.1
Pseudo Devices
5-5
5.1.2.2
LUNs • • • • •
• • • • •
• 5-7
5.1.2.3
Logical Device Names
• • • • • • • • • • • 5-8
Public, Shared, Private and Unowned Devices and
5.1. 3
Mounted Volumes
• • • • • • • • • • •
• 5-8
How to Prepare a Scratch Disk for Use
• 5-9
5.1. 4
5.1. 5
Preparing a Scratch ANSI Magnetic Tape for Use 5-12
Summary of Device and Volume Use Commands
5-12
5.1. 6
5.2
ANALYZE/MEDIA
• • • • • •
5-14
ASSIGN • • • • • • • • • • • •
• • • • •
5-21
5.3
5.3.1
ASSIGN/REDIRECT
5-24
5.3.2
ASSIGN/TASK
• • • •
5-27
5.4
DEASSIGN • • •
• • • • •
• • • • •
5-29
ALLOCATE • • •
• • • •
. • • •
5-31
5.5
5.6
DEALLOCATE • •
• • • • •
5-34
MOUNT
• • • • •
• • • •
5-36
5.7
5.7.1
Mounting Magnetic Tapes and Tape Sets
5-48
DISMOUNT • • • • • • • • • •
• • • • • •
5-53
5.8
5.9
INITIALIZE • • • • • •
5-57
5-70
5.9.1
INITIALIZE/UPDATE
• • • • • • • • ••
5.10
BACKUP • • • • • • •
5-73
SET AND SHOW • • • • • • • •
5-85
5.11
5.11. 1
SHOW ASSIGNMENTS •
5-86
5.11.2
SET DEVICE • •
5-88
5. 11. 3
SHOW DEVICES • • •
5-91
CHAPTER 6
6.1
6.2
6.2.1
6.2.2
6.3
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.8
6.3.9
6.4
6.4.1
6.4.2
CHAPTER 7
7.1
7 .1.1
7.2
7.2.1
7.2.2
7.3
7.4
7.5
7.6
7.7

PROGRAM DEVELOPMENT
INTRODUCTION • • • •
LINKING THE TASK • .
• • • • • ••••
Introduction to the LINK Command • • • • •
LINK • • • • . • . . • • • .
LIBRARY • • • • • •
LIBRARY/COMPRESS
LIBRARY/CREATE • •
LIBRARY/DELETE •
LIBRARY/EXTRACT
LIBRARY/INSERT • •
LIBRARY/LIST • • •
LIBRARY/REMOVE •
LIBRARY/REPLACE
Error Messages from LIBRARY
SET AND SHOW • • •
SET GROUPFLAGS •
SHOW GROUPFLAGS

•
•
•
•

6-1
6-2
6-2
6-7
6-28
6-31
6-32
6-35
6-36
6-37
6-39
6-43
6-44
6-45
6-51
6-52
6-53

•
•
•
•

7-1
7-2
7-5
7-7
7-11
7-16
7-21
7-23
7-2 4
7-26

RONN ING TASKS
TASK INSTALLATION AND EXECUTION
Task Naming
• • • • • • • • • • • • • • •
INTRODUCTION TO THE RUN COMMAND
• • • • • •
Running Tasks Contained in Task Image Files
•
Running and Scheduling Installed Tasks • •
ABORT
• • • • • • • •
• • • • • •
CONTINUE •
• ••••
CANCEL • • • •
STOP /BLOCK • •
• • • • • • •
START

CONTENTS
7.7.1
START/UNBLOCK • • • •
INSTALL
7.8
7.9
REMOVE • • . •
FIX • • • •
7.10
7 .11
UNFIX • • • •
7.12
SET AND SHOW •
7.12.1
SET PARTITION
7.12.2
SHOW PARTITIONS
• • • • •
7.12.3
SHOW TASKS • • • •
7.12.3.1
SHOW TASKS/ACTIVE
7.12.3.2
SHOW TASKS/INSTALLED • •
7.12.3.3
SHOW TASKS/INSTALLED/DEVICE
7.12.3.4
SHOW TASKS/DYNAMIC • • • • • • • • • •
7.12.3.4.1
SHOW TASK:taskname/DYNAMIC
7.12.3.4.2
SHOW TASKS/ACTIVE/DYNAMIC
• • • •
7.12.3.5
SHOW TASK/LOGICAL UNITS
SET PRIORITY • • • 7.12.4
7.12.5
SHOW /CLOCK_QUEUE
•••••
CHAPTER 8
8.1
8.1. l
8.1. 2
8.1. 3
8 .1. 4
8.1. 5
8.1. 6
8 .1. 7

7-27
7-28
7-37
7-38
7-40
7-40
7-41
7-46
7-49
7-49
7-54
7-56
7-57
7-57
7-59
7-61
7-63
7-65

SYSTEM CONTROL
SET AND SHOW •
SET DAYTIME
SHOW [DAY]TIME
SET SYSTEM • .
SHOW SYSTEM
SYSTEM DIRECTORIES •
SHOW USERS • •
• • • .
SHOW MEMORY

CHAPTER 9

QUICK REFERENCE

APPENDIX A

COMMON ERROR MESSAGES

APPENDIX B

FUNCTIONS INITIATED BY DCL COMMANDS

• • 8-1
• • 8-1
• • 8-3
• 8-3
• • • 8-6
• • • • 8-7
• 8-8
• • 8-9

INDEX
FIGURES
3-1
4-1
4-2
4-3

Terminal Keyboard and Keypad • •
File Organization on a Volume
Job Flag Page
File Flag Page • • • • • • • •

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

Keyboard and Keypad Characters • • • • • • • • •
3-13
Display of Terminal Attributes from SHOW TERMINAL 3-49
File Types • • • • • • • • • •
• • • 4-5
Devices on RSX-llM Systems • •
• • • • 5-2
Pseudo Devices on RSX-llM
• • • • • • • • • • 5-6
Task Builder Options • • • •
• • • • • •
6-16
Base and Size Specifications for SET PARTITION • 7-42
Task Status Flags
• • • • •
• • • • • • 7-51

• • 3-1
• • • 4-1
4-62
4-63

TABLES

PREFACE

MANUAL OBJECTIVES
The RSX-llM Command Language Manual provides information needed to use
a terminal to do work on an RSX-llM system.
Important system concepts
are introduced and explained in the context of the DIGITAL Command
Language
(DCL). DCL is a user-oriented command language with English
words and prompting for required command elements.

INTENDED AUDIENCE
This manual is intended for any user of an RSX-llM system. The manual
is a reference manual with many tutorial elements, but new users
should read the Introduction to RSX-llM first.
A user is anyone who interfaces with the system to perform some task.
There are two kinds of users:
privileged
and
nonprivileged.
Privileged users have access to functions that control and modify
system operation as well as functions that permit program development
and system maintenance. Nonprivileged users have access to functions
required for program development and local maintenance only.

STRUCTURE OF THIS MANUAL
The manual is organized around the major operating system functions.
Following the introduction, each major function has a chapter to
itself. All commands relating to the function are described in the
chapter. The last chapter is an annotated alphabetical listing of all
DCL commands.
Chapter 1 introduces the basic concepts of DCL, explains how DCL is
implemented on RSX-llM, and includes many hints on using DCL. The
chapter also includes summaries of the remainder of the manual, as
well as general information about DCL, the operating system, and
various utilities and system tasks.
Chapter 2 lists the most common forms of SET and SHOW commands.
Chapter 3 covers terminal operations, including logging in and logging
out, keyboard terminology and functions, setting and displaying
terminal attributes, broadcasting messages, and using the system HELP
commands.
Chapter 4 introduces file-handling operations on RSX-llM, including
commands to create and delete files, list directories, and rename,
copy, type, and print files. Wildcards and defaults are explained.

vii

PREFACE
Chapter 5 covers peripheral devices and introduces the system I/O
terminology.
The chapter explains the relationships between hardware
devices and the software file system, and describes how to prepare
scratch disks and magnetic tapes for use on the system. Commands
affecting devices and software volumes are described.
Chapter 6 introduces the program-development facilities of the
and the DCL commands used with these facilities.

system

Chapter 7 explains how tasks run in the system and how they are named,
installed,
fixed in memory, and controlled while running.
In
addition, the chapter describes commands to abort tasks, to place
tasks in the clock queue, and to display information about tasks in
the system.
Chapter 8 covers the DCL system-control commands.
Chapter 9 is the alphabetical listing of all DCL commands and their
formats,
including comments to remind you of specific points about
many commands and command elements.
Each entry in Chapter 9 includes
a cross-reference to the full command description in an earlier
chapter.
Appendix A explains error messages common to
Other command-specific error messages are
command descriptions.

several DCL commands.
explained in the full

Appendix B lists the relationships between DCL and
operating system.

the

rest

the

described

the

If you are entirely new to computers or to DCL, you should
Introduction to RSX-llM and follow the instructions there.

read

the

ASSOCIATED MANUALS
Other documents
related
to
RSX-llM
are
RSX-llM/RSX-llS Information Directory and Index.

Although this manual is meant to be self-contained, you will find
important information in the RSX-llM/M-PLUS MCR Operations Manual and
the RSX-llM/M-PLUS Utilities Manual.
Programmers should
Development.

see

the

RSX-llM/M-PLUS

Guide

Program

CONVENTIONS USED IN THIS MANUAL
A number of conventions are used in the command descriptions
manual:
Convention

this

Meaning
A symbol that indicates the CTRL key; it must be
held down while another key is pressed. For
example,
PRL/z)
means hold down the CTRL key
while pressing z.
In examples, this control key
sequence is shown as Aa; for example, AO indicates
the result of
mRU~
because that is how the
system echoes most control key combinations.
A 1- to 3-character key symbol.
For example,
indicates the RETURN key, CIT)
indicates the
LINE FEED key, and
(§9 indicates the ESCAPE key.

IBru

viii

PREFACE

The vertical ellipsis shows where elements of
command input have been omitted because they
are irrelevant to the point being discussed.
[/qualifier]

Any command field enclosed
in
brackets
is
optional.
If the brackets include syntactical
elements, such as dots (.) or slashes
(/), those
elements are required for the field.
If the field
appears in lowercase, you are to substitute a
legal command element if you include the field.

[g,m]

This signifies either a User Identification Code
(UIC) or a directory. The g is a group number and
the m is a member number.
Where a UIC or
directory is required, only one set of brackets is
shown, as [g,m]. Where the UIC or directory is
optional, two sets of brackets are shown, as
[[g,m]]. The UIC identifies a user and is used
mainly
for
controlling access to files and
privileged system functions.

UPPERCASE

Any command field in uppercase indicates the legal
form of the command.
If you type it in that form,
it will work as described. Most DCL commands have
abbreviations.

lowercase

Any command field in
lowercase
is
to
be
substituted
for.
Usually the lowercase word
identifies the kind of substitution expected, such
as filespec, which indicates that you should fill
in the file specification.

/qualifier

Any command element preceded by a slash (/)
is a
DCL
qualifier.
Command qualifiers alter the
action of a command they are
attached
to.
Parameter qualifiers modify the action of the
command as it affects that parameter.

parameter

Required command fields are generally
called
parameters.
The most common parameters are file
specifications. Parameters are preceded by blanks
or DCL prompts.

:argument

Some parameters and qualifiers can be altered by
the inclusion of arguments preceded by a colon.
An argument can be either numerical (COPIES:3)
or
alphabetical
(NAME: KAT). The equals sign (=) can
be substituted for the
colon
to
introduce
arguments. COPIES=3 and COPIES:3 are the same.

filespec

A full file
specification
directory, file name, file
number, as in this example:

includes
type, and

device,
version

DB1:[303,S]HIPPITY.HOP;2
Full file specifications are rarely needed.
If
you do not give a version number, the highest
numbered version will be used.
If you do not give
a directory, the default directory will be used.
Some system functions default to particular file
types. See Chapter 4 for more information on file
specifications. See also the individual command
descriptions.

PREFACE
Some commands accept a file specification with a
DECnet
node
name.
See Chapter 1 for more
information.
red ink

All user input in examples is printed in
to distinguish it from system output.
what you type is shown in red.

A number of options between braces and separated
by vertical bars means that you are to choose one
of the options listed.

See Chapter 1 for more information on DCL conventions.

red ink
That is,

SUMMARY OF TECHNICAL CHANGES

The RSX-llM Command Language Manual has been revised to reflect
changes made to the software for Version 4.2.
Not all of the
alterations made to the software for this version of RSX-llM resulted
in changes to this manual; see the RSX-llM Release Notes for a
comprehensive list of all software changes.
The following is a list of DCL commands and
version of RSX-llM:

qualifiers

new

this

ANALYZE/MEDIA[/qualifier[s]] ddnn:
/ALLOCATE
/BAD BLOCKS
/BAD-BLOCKS/EXERCISE: (n,m)
/BAD-BLOCKS/NOEXERCISE
/[NO]EXERCISE[: (n,m)]
/OVERRIDE
/RETRY
/SHOW
New command. The ANALYZE/MEDIA command determines if bad blocks
exist on a disk volume and records their locations for use by the
backup and restore utilities and the INITIALIZE command.
APPEND[/qualifier[s]]
/NOWARNINGS
/REWIND
/SHARED
New qualifiers.
BACKUP[/qualifier[s]]
/CREATED:arg
AFTER: ( dd-mmm-yy hh :mm)
BEFORE:(dd-mmm-yy hh:mm)
/APPEND
New qualifiers.
COPY[/qualifier[s]]
/ALLOCATION: n
/NOWARNINGS
/OVERLAY
/PRESERVE DATE
/REWIND /SHARED
New qualifiers.

SUMMARY OF TECHNICAL CHANGES
CREATE/DIRECTORY[/qualifier]
/NOWARNINGS
/OWNER_UIC
New qualifiers.
DELETE[/qualifier[s]]
/[NO] CONFIRM
/NOWARNINGS
New qualifiers.
DIRECTORY[/qualifier[s]]
/NOWARNINGS
/REWIND
New qualifiers.
DISMOUNT[/qualifier[s]]
/SAVE
/TERMINAL
/[NO]UNLOAD
New qualifiers.
INITIALIZE[/qualifier[s]]
/BAD BLOCKS:arg
AUTOMATIC
(AUTOMATIC,MANUAL)
MANUAL
NOAUTOMATIC
OVERRIDE
(OVERRIDE,MANUAL)
/DENSITY:arg
HIGH
LOW
/LABEL:VOLUME_ACCESSIBILITY:"c"
New qualifiers.
INITIALIZE/UPDATE[/qualifier[s]]
/DENSITY:arg
HIGH
LOW
New arguments.
INSTALL[/qualifier[s]]
/[NO] INTERPRETER
New qualifier.
LINK[/qualifier[s]]
/[NO]PRINT
New qualifier.

xii

SUMMARY OF TECHNICAL CHANGES
MOUNT[/qualifier[s]]
/PROCESSOR:arg
UNIQUE
Changed argument to existing qualifier.
PRINT[/qualifier[s]]
/AFTER:TOMORROW
/NOWARNINGS
New qualifiers.
PURGE[/qualifier[s]]
/NOWARNINGS
New qualifier.
RENAME[/qualifier[s]]
/NEW VERSION
/NOWARNINGS
New qualifiers.
RUN[/qualifier[s]]
/[NO] IO PAGE
/[NO]SLAVE
New qualifiers.
SET DEVICE:ddnn:/qualifier[s]
/[NO]CHECKPOINT_FILE[:n]
New qualifier.
SET FILE [/qualifier [s]] filespec [s]
/END OF FILE:(BLOCK:n,BYTE:n)
/ENTER:synonym filespec
/NOWARNINGS
/REMOVE
/REWIND
/TRUNCATE
New command.

SET FILE establishes certain file attributes.

SET HOST nodename
New command. SET HOST connects your terminal to a remote system.
You issue this command after you have logged in to your cur~ent
system. Both your current and remote system must run DECnet
software.
SET SYSTEM/qualifier
/NETWORK UIC: [g,m]
/POOL/LIMITS
New qualifiers.

xiii

SUMMARY OF TECHNICAL CHANGES
SET TERMINAL[:ttnn:]/qualifier[s]
/INQUIRE
/[NO]ADVANCED VIDEO
/[NO]ANSI CRT/[NO]BLOCK MODE
/DEC CRT /DTCOl
/EDIT MODE
/HOSTSYNC
/LASO
/LA210
/LN03
/LQP02
/LQP03
/[NO]PARITY[:type]
ODD
EVEN
/[NO]PASTHRU
/PRINTER PORT
/PRO SERIES
/[NO)REGIS
/[NO]SOFT CHARACTERS
/[NO]TTSYNC
/VT200_SERIES
New qualifiers.
SHOW HOST
New command. SHOW HOST displays the name of the processor to which
your terminal currently is connected.
It also shows you the name
and version number of the operating system running on
the
processor.
SHOW SYSTEM[/qualifier]
/NETWORK UIC
/POOL/LIMITS
New qualifiers.
SHOW TASKS[:taskname]/qualifier[s]
/DEVICE:ddnn:
New qualifier.
SHOW TERMINAL[:ttnn:] [/qualifier]
/[NO]ADVANCED VIDEO
/[NO]ANSI CRT/ [NO]BLOCK MODE
/[NO]DEC CRT
/DTCOl /[NO]EDIT MODE
/HOSTSYNC/ [NO] LA50
/[NO]LA210
/LN03
/LQP02
/LQP03
/[NO]PARITY
/[NO]PASTHRU

xiv

SUMMARY OF TECHNICAL CHANGES
/PRINTER PORT
/PRO SERlES
/[NO]REGIS
/[NO]TTSYNC
/[NO]VT200_SERIES
New qualifiers.
TYPE[/qualifier[s]
/NOWARNINGS
/SHARED
New qualifiers.
UNLOCK[/qualifier[s]]
/NOWARNINGS
New qualifier.
The following is a list of new devices supported
4.2:
DHUll
DEUNA
KDA50
RD52
RD53

RSX-llM

Version

RQDX2
RQDX3
RUX50
TK25
TK50

The following is a list of new terminal
Version 4.2:
DTCOl
LASO
LA210
LN03

types

supported

LQP02
LQP03
PRO-series terminals
VT200-series terminals

RSX-llM

CHAPTER 1
HOW TO USE DCL

DCL is the DIGITAL Command Language. DCL provides RSX-llM users with
an extensive set of commands for interactive program development,
device and file manipulation, and interactive program execution and
control.
If you are new to computers, or if you wish a quick review of DCL and
the operating system, you should read the Introduction to RSX-llM.
This manual includes a guided tour of the operating system, including
an interactive terminal session that introduces all of the most
commonly used DCL commands.
DCL commands are full words that describe the action to be taken,
not
abbreviations or mnemonics.
Thus, if you wish to set a terminal to
lowercase, you type SET TERMINAL/LOWERCASE. Because DCL commands and
command elements are full words, they are self-documenting.
You are not required to use the full form of DCL commands at the
terminal, however.
Usually, you need type only the command elements
required to form a unique command. For instance, SE TERM/LOW will
also set a terminal to lowercase, but SE TERM/LO will not work because
there is also a command SET TERMINAL/LOCAL. See Section 1.2 for more
information on how DCL commands are parsed.

1.1

RSX-llM AND DCL:

BASIC CONCEPTS

RSX-llM systems may have one or more command line interpreters (CLis}.
All systems include MCR (the Monitor Console Routine}. Many systems
also include DCL, and some systems include other CLis. Both MCR and
DCL include commands to invoke most system tasks and utilities and to
set and display certain system characteristics.
In general, MCR
commands name tasks, such as PIP, a utility used to manipulate files
(for example, to copy or type them}, while DCL commands specify
actions directly, as in the COPY command or the TYPE command.
MCR is the fundamental command line interpreter (CLI} for the RSX-llM
operating systems.
MCR also provides commands to set and display
certain system characteristics.
MCR provides the
most
direct
interface with the RSX-llM operating system.
MCR
In general, MCR commands must be entered in exact syntax.
commands follow no set syntax rules, however. Most MCR commands are
abbreviations or mnemonics.
DCL is an optional user-oriented CL! included in most systems with
many users.
Commands in DCL are English-like words and follow
well-defined syntax rules. Full commands are self-documenting.
DCL
is designed for consistency and ease of use.

1-1

HOW TO USE DCL
DCL is the command language used on many of DIGITAL operating systems.
In particular,
RSX-llM DCL is designed for compatibility with future
releases of VAX/VMS DCL.
See Section 1.7 for more information on DCL
compatibility.
DCL on RSX-llM systems is a CL! task that translates
DCL commands into MCR commands for execution by the system.
The DCL
command SET DEBUG command displays the MCR translation for any DCL
command on your terminal.
See Section 1.2.15 for more information on
the SET DEBUG command.
Depending on the kind of use you make of your system and the nature of
your system, you may find it more convenient to use one CL! or the
other, or both. All nonprivileged system functions are available
directly from DCL, but some privileged functions are not.
All
program-development facilities and all common utility functions are
avaHable from DCL.
Because RSX-llM is designed to be tailored to
the needs of each
installation,
not every feature of DCL described in this manual is
available on every system.
Some DCL commands depend on layered
products that may not be available at your
installation.
Many
features are system-generation options that may not have been selected
at the time your system was generated.
You should see your system
manager or another knowledgeable system user if some feature described
in this manual does not appear to be available at your installation.

1.2

THE DCL COMMAND LINE

A command consists of a command name or verb describing the action the
system is to take.
Most commands also include one or more parameters
and qualifiers to further define the action of
the
command.
Qualifiers are preceded by a slash (/) and parameters are preceded by
a
space.
Both qualifiers and parameters can
take
arguments.
Arguments are preceded by a colon (:).
Commands are passed to the operating system with a terminator, either
RETURN or ESC.
(The ESC key may be labeled SEL or ALT MODE.
Its
action differs from that of the RETURN key in that the cursor does not
return to the left margin and no monitor prompt is returned after
execution is completed.)
Unless the action of the RETURN greatly differs from what is expected,
the examples and command
formats
in this manual do not include an
indication that each line in the command is terminated by a carriage
return.
(See Section 1.2.13, for a discussion of command lines too
long to fit on one line of your terminal.)
Some commands require parameters or arguments as part of the command
line.
If you fail to supply a required command element, DCL prompts
you with one or two words
indicating the general nature of the
required element.
If you do not understand the prompt, type a
question mark (?) for help.
(In some cases,
an omission causes an
error rather than a prompt.)
Section 1.2.1 discusses prompting in detail.
This section introduces the rules governing the use of DCL.
The
examples in this section are intended to illustrate these rules, not
to illustrate the full capabilities of the command. For more detail,
see the individual command descriptions.

1-2

HOW TO USE DCL
1.2.1

Prompting

The prompts teach you the form of a command
supply required command elements.

requesting

that

you

leave

out.

For example, the RENAME command works as follows:
$ RENAME IBru
From? BROWNS. STL IBm
To? ORIOLES. BLT (BIT)
The one-line format for RENAME is as follows:

$ RENAME BROWNS.STL ORIOLES.BLT IBm
The formats can be mixed.
For example:

DCL prompts for

whatever

you

$ RENAME BROWNS. STL (BIT)
To? ORIOLES.BLT (BIT)
There are no defaults for prompts.
You must supply a response to any
prompt.
If you do not wish to continue with the command, press
CTRL/Z.

1.2.2

Qualifiers

Qualifiers modify the action of the command.
with a slash (/) and are generally optional.

Qualifiers always

start

Qualifiers are either command qualifiers or parameter qualifiers.
Most qualifiers are command qualifiers.
In this manual, command
qualifiers are always shown as modifying the command verb, as in this
example:
$ TYPE/TODAY *. HLP

IBru

However, most command qualifiers can appear anywhere in the command
line.
Another name for these qualifiers is floating qualifiers.
The
following examples illustrate how command qualifiers can float:
$ TYPE *. HLP /TODAY

ffilil

or
$ TYPE IBru
File ( s)? *. HLP /TODAY IBD)
or
$ TYPE ffiIT)
File(s)? /TODAY IBIT)
File (s)? *. HLP IBlil
You can mix formats and get
following example:

exactly

the

$ TYPE/TODAY (BIT)
File(s)? *.HLP/EXCLUDE:HELPF.HLP;* (BIT)
or

1-3

same

results,

the

HOW TO USE DCL
$ TYPE/TODAY (8ITl
File(s)? *.HLP/ (8ITl
Qualifier? EXCLUDE:HELPF.HLP;* illITJ

or
$ TYPE/TODAY (8ITl
File(s)? I illITl
Qualifier? EXCLUDE:HELPF.HLP;* (8ITl
File(s)? *.HLP (8ITl

Note that you are prompted for a qualifier when a slash with no
qualifier attached appears on the command line. When you supply the
qualifier, do not type the slash again.
Almost all command qualifiers can float in this way.
In a few cases,
the command qualifier must appear directly after the command it
modifies. Whenever two similar commands are described separately,
such as ASSIGN and ASSIGN/REDIRECT or CREATE and CREATE/DIRECTORY, the
distinguishing qualifier cannot float.
Other qualifiers to such
commands can still float, however, as in this example:

$ CREATE/DIRECTORY (8ITl
Device, UFD? [303,5]/ALLOCATION:5 (8ITl
which is the same as the following example:

$ CREATE/DIRECTORY/ALLOCATION:5 [303,5] (8ITl
Parameter qualifiers, sometimes called file specification qualifiers,
cannot float.
Usually a parameter qualifier must be attached to a
file
specification,
because
most
DCL
parameters
are
file
specifications.
Many qualifiers can be negated by prefixing NO or
qualifier name.
Thus, the following command:

(mi nus)

the

while

the

$ MACRO/OBJECT SIMPLE.MAC (8ITl

directs the MACR0-11 Assembler to
following command:
$ MACRO /NOOBJECT SIMPLE. MAC

make

object

file,

$ MACRO/-OBJECT SIMPLE.MAC

tB"ill

directs the MACR0-11 Assembler to omit the object file.
In the first
example, /OBJECT is the default qualifier and need not be included
explicitly.
In other words, unless your MACRO command includes the
/NOOBJECT qualifier, an object file is produced.

1. 2. 3

HELP

HELP is available from the system for all DCL commands and also for
many other aspects of the system. You can get help through the HELP
command or by typing a question mark
(?)
in response to any DCL
prompt.

1-4

HOW TO USE DCL

For instance,
following:

you

wish

help

the

TYPE

command,

type

the

your

$ HELP 'rYPE ~
TYPE[/qualifier[s]] filespec[s]
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARN INGS
/SHARED
The TYPE command displays the contents
terminal.

text

files

$
The HELP text consists of a brief explanation of the command followed
by an illustration of the syntax, showing that TYPE accepts one or
more file specifications, and one or more qualifiers.
See Section
4.4.1 for more information on TYPE and its qualifiers.
Or, type a
HELP command naming the qualifier to get more
information on that
qualifier.
$ HELP TYPE TODAY
TYPE/TODAY filespec[s]
The /TODAY qualifier specifies that you wish the TYPE command to
type only files created today.
If you want help while being prompted by the
following procedure:

TYPE

command,

use

the

your

$ TYPE ~
File(s)?? ~
TYPE[/qualifier[s]] filespec[s]
/DATE:dd-mmm-yy
/SINCE:dd-mmrn-yy
/THROUGH:dd-rnmm-yy
/SINCE:dd-mmrn-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARNINGS
/SHARED
The TYPE command displays the contents
terminal.
File(s)?

text

files

The same help text
is printed on your terminal, but the prompt
returns, meaning the TYPE command is still waiting for you to list the
files you want typed.
You can also get help on a specific subtopic while being prompted by a
command by responding to the prompt with a question mark.
For
example, after getting help on SET, you can also get help on a
specific function of SET:
$SET ~
Function? ?
SET thing

1-5

HOW TO USE DCL

The SET command can be used to set something.
things can be set with this command:
[DAY] TIME
GROUPFLAGS
PRIORITY
TERMINAL

DEBUG
HOST
PROTECTION

For information
ACCOUNTING SET.

the

DEFAULT
LIBRARY
QUEUE
SET

ACCOUNTING

The

following

DEVICE
[NO] PARTITION
SYSTEM
command,

see

HELP

To get help on a specific topic, enter a question mark followed by the
thing:
Function? ? DEFAULT IBtll
SET DEFAULT [ddnn:] [[ufd]]
The SET DEFAULT command sets your default directory
or both.

device,

SET DEFAULT with no parameters returns a nonprivileged user to
the login device and UFD.
For privileged users, the unadorned
SET DEFAULT returns to the login device, but the UFO remains the
same.
Function?

IBtll

You can also get help by typing a question mark
in response
dollar sign prompt ($) and to the explicit DCL prompt (DCL>).

the

If you should decide after reading the help text that you have chosen
the wrong command, press CTRL/Z in response to the prompt to end the
execution of the command.
(A CTRL/Z in response to a prompt always
cancels execution of a DCL command.)
From a DCL terminal, the command HELP provides information on DCL and
the command HELP/MCR provides information on MCR.
From an MCR
terminal, the command HELP provides information on MCR and the command
HELP/DCL provides information on DCL.
There may also be special help files providing information on special
aspects of your installation.
In addition, you can create local help
files for your own use. See Chapter 3 for more information on the
HELP command and help files.

1.2.4

MCR and DCL Commands

You can usually enter MCR commands from terminals set to
commands from terminals set to MCR.

DCL

If you are at a DCL terminal and want to enter an MCR command,
simply
precede the command with an MCR.
The command is passed directly to
MCR while the terminal remains set to DCL.
Here is the format of the MCR command:
DCL>MCR
MCR command line?

mcrcommand

or
DCL>MCR mcrcommand

1-6

HOW TO USE DCL
And, if you want to enter a DCL command from an MCR terminal, use the
DCL command.
The command is executed and the terminal remains set to
MCR.
Here is the format of the DCL command:
MCR>DCL dclcommand
There are no prompts from this command.

1.2.5

Abbreviations

It is rarely necessary for you to type either the complete command
name or the complete qualifier name.
You only need to type the
characters needed to distinguish the command or qualifier from all
others.
For example:
•

TYPE can be abbreviated T because
beginning with that character.

the

INITIALIZE can be abbreviated !NI, but not IN.

•

INSTALL can be abbreviated INS, but not IN.

only

command

Three letters will usually be enough. Four letters will always be
enough.
You can often omit other parts of commands as well.
You
should experiment to find how short various commands can be cut.
For
instance, the following command:

$ SET TERMINAL/VTlOO (@!)
is the documented format for the command that sets a terminal as a
VTlOO.
The same command to VAX/VMS DCL does the same thing.
However,
the RSX-llM version of DCL permits you to type the following:

$ SE VTlOO IB§!)
to achieve the same result.
systems.

The second form does not work on

VAX/VMS

These briefer forms should be used interactively only, and not used
when you are making a permanent record or creating an indirect command
file.
You should also see Section 1.7 for a
discussion
of
compatibility between RSX-llM DCL and other versions of DCL used on
other operating systems.
For your convenience, some frequently used commands have brief forms:
Command
ABORT
BROADCAST
COPY
DIRECTORY
DEALLOCATE
DEASSIGN
EDIT
FORTRAN

Brief Form
A
B

D
DEAL
DEAS
E
F

Command
HELP
HELP
LOGOUT
LINK
MACRO
PRINT
RUN
SHOW

Brief Form
H
?

LO
L
M
p

To save time and typing, use these brief forms to replace the
names when you are entering commands.

1-7

command

HOW TO USE DCL
1.2.6

Numbers and Dates

DCL recognizes both octal and decimal numbers.
You usually do not
have to identify a number as octal or decimal. All numbers are
recognized as being octal or decimal, unless otherwise noted.
DCL recognizes dates in two forms:
dd-mrnm-yy as in 21-JUN-85
or
mrn/dd/yy as in 6/21/85
System displays are always in the first format.

1.2.7

Multiple Parameters

Some commands permit you to enter a single file specification or other
parameter by a list of parameters.
If you are entering a list of
parameters, each parameter must be set off by commas. For example:
$ PRINT ALPHA. TXT

IBDJ

causes a single file to be printed, while the following command:
$ PRINT ALPHA.TXT, BETA.TXT, GAMMA.TXT IBDJ
causes three files to be printed. You have the
blanks on either side of the comma in lists.
If you end the list with
parameters. For instance:

comma,

DCL

option

prompts

you

of
for

including
further

$ PRINT ALPHA.TXT, BETA.TXT,
File(s)? GAMMA.TXT IBru

Some commands accept a list of arguments to a single qualifier or
parameter.
In such cases, the list of arguments must be enclosed in
parentheses, with each element set off by commas.
For example,
the
following command:
$ MACRO/SHOW: (CALLS,COMMENTS) HIYA
If you need to enter only a single
parentheses. For example:
$ MACRO/SHOW:CALLS HIYA

1.2.8

argument,

you

not

need

the

Underscore Character

The underscore character
is used to make DCL commands more
readable where two words are needed to name a single command element,
such as PRINT/FLAG PAGE. However, you need not type the underscore to
enter the command. PRINT/FLAGPAGE is the same as PRINT/FLAG_PAGE.

1-8

HOW TO USE DCL
1.2.9

Colon and Equal Sign

The command descriptions in this manual show arguments set
colon (:), such as follows~

$ PRINT/COPIES:2 IZZY.TXT

off

ffiITl

You can always replace such colons with an equal sign (=),as in
example:

$ PRINT/COPIES=2 IZZY.TXT

this

ffiITl

Colons in device names, such as DBl:, and so forth, cannot be replaced
by equal signs.

1.2.10

Quoting Strings

If you want to include an exact string in a DCL command,
string in quotes.
For instance, the following message:

put

the

$ BROADCAST/ALL Rock and roll will never die (Bill
is broadcast as follows:
ll-MAY-85 13:55
From PRINCE::WRITERS
ROCK AND ROLL WILL NEVER DIE

(TT64:) to ALL

while the following command:
$ BROADCAST/ALL "Rock and roll will never die"

(Bill

is broadcast as follows:
ll-MAY-85 13:56
From PRINCE::WRITERS
"Rock and roll will never die"
You also need quotes
/PARAMETERS qualifier
INSTALL.

1.2.11

(TT64:) to ALL

when passing commands to tasks using the
to MOUNT or the /COMMAND qualifier to RUN or

ANSI File Names

ANSI file names do not have the same format as Files-11 file names and
may contain characters that are illegal in Files-11. For instance,
"MONEY&." is a legal ANSI file name, as is "CASH&.".
To use those
file names in a command, simply enter them as shown in the following
example:
$ COPY
(Bill
From? MM: "MONEY&." (Bill
To? MMl: "CASH&." (Bill

If you are copying a file from a tape to a Files-11 disk, however, you
must use only Radix-50 file specifications, such as the following:
$ COPY (Bill
From? MM: "MONEY&." IBIT
To? DB: [200,l]RADIXSO.TXT (Bill

The Radix-50 character set consists of the numbers 0 through 9,
letters of the alphabet, the dollar sign ($) and the period (.).

1-9

the

HOW TO USE DCL
1.2.12

DECnet and DCL

Some commands will accept DECnet node
specification.
They are as follows:
APPEND
COPY

CREATE
DELETE

names

DIRECTORY
PRINT

part

file

RENAME
TYPE

Several other DCL commands accept
node
names
in
the
file
specifications.
However, DECnet modifies the basic syntax of these
commands. These commands are:
PRINT, SET PROTECTION, and SET FILE.
Be sure to check the RSX DECnet Guide to User Utilities before
attempting to use these commands.
If the node you select is part of your network, you can simply add the
node to the file specification in the appropriate DCL command.
Note
that your terminal remains connected to your local node when you issue
these commands to a remote node.
In the following example, you issue a command to type on your terminal
the file ROMAN.TXT, which is located on remote node PRINCE and device
DB2:, in directory [303,5).
$TYPE PRINCE::DB2: (303,S]ROMAN.TXT (BTil
All the usual rules about file and volume protection
of course.

are

maintained,

If the remote node you specify has a different style of file
specification from RSX-llM, you must enclose the file specification in
quotation marks, as shown:
$ TYPE EEETEE: :"DISK$USERDISK: [DALTON]DESPERADO.DIS" (BTil
In addition to transmitting commands between nodes, DECnet also allows
you to connect your terminal to a remote node. See the SET HOST
command, described in the following section.

1.2.12.1

SET HOST

After you log in to a system, you can use the
connect your terminal to a different system.

SET

HOST

command

Both your current system and the remote system must run DECnet
software.
In addition, you need to have an account on the remote
system; otherwise, you will not be able to log in on the remote system
after you issue the SET HOST command.
Format
SET HOST nodename
Parameters
node name
Specifies the name of the remote system that you want to
your terminal to.

connect

A node is one system within a network of systems.
The system
that you originally log in on is called a local node; all other
systems in the network are called remote nodes.

1-10

HOW TO USE DCL
that operating system
Once you have connected to the remote node,
responds with a prompt.
After you log in, use commands that the
remote operating system accepts.
Type the LOGOUT command to log out of a remote node.
this command, you are relocated to your local node.

After

typing

You can use SET HOST to connect to only one remote host at a time.
For example, suppose you want information located at two different
remote nodes, KING and JUNE.
You cannot connect first to remote node
KING, and then execute SET HOST again to connect to remote node JUNE.
You must first log out of KING, which relocates you to your local
node, and then use SET HOST to connect to JUNE.
See the RSX-11 DECnet documentation accompanying the
product for a full explanation of this command.

DECnet

software

Examples
$ SET HOST TOOTS!

Connected to node "TOOTS!", System type
System ID: RSX TIMESHARING
$ LOGIN ~
Account or Name: 303,3
Password:
~

RSX-llM

This SET HOST command connects your terminal to the remote node
TOOTS!.
The remote system identifies itself, then prompts you.
You
log in on the remote system by using the name and password of your
account on that system.

1.2.12.2

SHOW HOST

The SHOW HOST command displays the name of the processor to which your
terminal is connected currently. The display also shows you the name
and version number of the operating system running on the processor.
The SHOW HOST command is most useful after you have connected your
terminal to a remote system with the SET HOST command. However, SHOW
HOST works whether or not your system runs DECnet software.
Without
DECnet on your system, this command simply displays information about
your local operating system.

Format
SHOW HOST

Example
$ SHOW HOST

HOST=TOOTSI RSX-llM V4.2 BL38

1-11

HOW TO USE DCL
This example indicates the display from SHOW HOST. The name of your
current processor is TOOTS!, which is running Version 4.2 of the
RSX-llM operating system.

1.2.13

Command Line Continuation

Sometimes a command will not fit all on one line.
In that case, you
can continue the line by using the hyphen (-). When you end a command
line with a hyphen and a carriage return, the DCL continuation prompt
(->)
indicates that you can continue entering the command line.
If
you are continuing a line from a prompt, such as Task? that prompt is
the indication that the line is being continued.
This feature permits you to enter command lines including
characters than your terminal has room for on one line.

DCL commands are limited to 80 characters in all.
When you type a
continuation line, count the hyphen and the two times you press the
RETURN key as three of the 80 characters. Of course, each blank, as
well as each punctuation mark, counts as one character.
Here is an example of line continuation:
$ PRINT/COPIES:2/LENGTH:60/FLAGPAGE/AFTER: (04-JUL-85) OZY.TXT,-IBIT)
->IZZY.TXT, FIZZY.TXT ~
The command is not entered until DCL encounters a line ending with a
RETURN that is not preceded by a hyphen.
In the example, the first
carriage RETURN does not enter the command. Only the second RETURN
enters the command.
The RETURN can be on a line by itself.

1.2.14

Comments in Command Lines

You may want to include comments in command lines if you are keeping a
permanent record, such as a command file, or simply an interactive
session on a hardcopy terminal. You can include comments in a DCL
command line with the exclamation point (!).
If the comment ends the command line, only a single exclamation
is needed, as in this example:
$ PRINT OZY.TXT !Poem by Shelley

If the comment is within the command line, two exclamation points
needed to set it off, as in this example:
$ PRINT!Parody of Shelley!

point

IZZY.TXT

are

These comments are ignored and not interpreted in any way by DCL.
Comments can be placed at any natural break in the command line:
between qualifiers, between parameters, even as part of a response to
a prompt. Another example:
$ PRINT/FORMS:2!Letter-quality printer!

1-12

IZZY.TXT IBru

HOW TO USE DCL
1.2.15

SET DEBUG

SET DEBUG displays the MCR translation of any DCL command.
Format
SET [NO]DEBUG[/qualifier[s]]
Command Qualifiers
/[NO]EXECUTE
/FULL
Command Qualifiers
/[NO]EXECUTE
Indicates that you wish the DCL· command to execute after the
translation is displayed.
The default is /NOEXECUTE, meaning
that the translation only is displayed. When SET DEBUG/NOEXECUTE
is in effect, you can only issue SET DEBUG commands or MCR
commands using the DCL MCR command; all other DCL commands are
trapped and translated.
You can issue SET NODEBUG to turn off
SET DEBUG.
You can also issue SET DEBUG with either /FULL or
/EXECUTE or both.
/FULL
Indicates that you wish SET DEBUG to display the logical symbols
(!FORM queue) used by DCL to translate the command as well as the
translation itself. See the RSX-llM/M-PLUS System Management
Guide for information on how DCL uses these logical symbols.
Examples
$ SET DEBUG
$ SHOW TIME

ID
ID

TIM
$ INITIALIZE/EXTENSION:200/PROTECTION: (SYS:RWED,OWN:RWED,GRO,WO)ID
Device? DK2 ID
Label? HOTROD ID
!NI DK2:HOTROD/EXT=200./PRO=[RWED,RWED,,]
$ SET DEBUG/EXECUTE ID
$ SH TIM ID
TIM

21:33:46 ll-FEB-85
$ SET NODEBUG ID

In this example, the user first issued SET DEBUG. Then the user
typed SHOW TIME. DCL displayed TIM, which is the MCR command to
display the date and time, but no date and time is displayed
because /NOEXECUTE was in effect.
Then the user typed an
INITIALIZE command and DCL displayed the MCR translation of the
same command.
Then the user typed SET DEBUG/EXECUTE and typed
SHOW TIME again. This time, after displaying the MCR command
TIM, DCL passed the command TIM to MCR and the date and time were
displayed. Finally, the user typed SET NODEBUG to end session
with SET DEBUG.
Notes
Use SET DEBUG to check on the MCR syntax of any DCL command.
This is particularly helpful when learning the brief forms of
commands.

1-13

HOW TO USE DCL
SET DEBUG creates your own copy of DCL that remains present while
SET DEBUG is in effect. Therefore, SET DEBUG creates a load on
the system. You should use SET DEBUG sparingly, particularly
when the system is under heavy use.

1. 2. 16

Errors

You can correct typing errors or change the line completely, by using
the RUBOUT or DELETE key, or by pressing CTRL/U (provided you have not
terminated the line).
You can get rid of any DCL command by pressing a CTRL/Z, provided
have not terminated the command.
If the system detects an error in the command line input,
the appropriate error message at the issuing terminal.
Here are some examples of incorrect commands and
they produce:

the

you

returns

error

messages

$ PR I J T I ZZY• T XT (Btl)
DCL
Illegal command
$ PRINT/PURPLE IZZY.TXT (Btl)
PRINT
Illegal or contradictory qualifier
PRINT/PURPLE
IZZY.TXT
,..
$ PRINT/COPIES:TWELVE IZZY.TXT
PRINT
Numeral expected
PRINT/COPIES:TWELVE
IZZY.TXT
,..

(Btl)

In the first case, the error was detected by DCL, as indicated by
first part of the error message.
There is no DCL PRIJT command.
entire command was rejected.

the
The

In the second case, the command was entered correctly, but the
qualifier was incorrect. The first part of the message shows that the
error was detected within the PRINT command itself.
The command is
reprinted and a. circumflex (") points to the error.
In the third case, the command and qualifier were
argument was in error.
The message explains
circumflex points to the error.

correct, but the
the error and the

Sometimes the circumflex does not point directly at the error, but at
the point at which the command started to go wrong, which may be
several characters before or after the actual error. Typing mistakes
are by far the most common cause of errors.
Retyping the command
often eliminates the error.
Other common causes of errors are
omitting a space or other delimiter in a command line, specifying
invalid devices or nonexistent files, issuing privileged commands from
a nonprivileged terminal, and failing to type a sufficient number of
characters to distinguish the command or command element.
The command descriptions include the most common errors produced by
the commands and suggestions for correcting the errors. All the DCL
error messages are listed and explained in Appendix A of this manual.

1-14

HOW TO USE DCL
1.3

FUNCTIONAL GROUPING OF DCL COMMANDS

This manual includes seven functional groupings of commands, each
grouping constituting a chapter.
Each of these chapters is described
here. Fully detailed descriptions of each command are included in
these functional chapters.
The functional groupings of commands are
described in Sections 1.3.1 through 1.3.7.
Each functional chapter
also includes an introduction to the important concepts of the
functional group.
Command descriptions can have five parts:
1.

Brief statement of the function of the command.

Full description of the format of the command,
including
prompts, defaults, acceptable values for arguments, and the
effects of each qualifier.

Examples of the command in use.
These examples
often
illustrate less obvious aspects of the use of the command.

Notes, including warnings about side effects, counteracting
commands,
recommendations for further reading, and so forth.
Some command descriptions do not have notes.

Error messages, including an explanation and a suggested user
action for each error. Only error messages specific to the
command are included in the command descriptions.
General
error
messages,
such as those relating to syntax, are
described in Appendix A.

In addition, the formats of all RSX-llM DCL commands are presented
alphabetical listing in Chapter 9.

Nonprivileged commands are those commands needed in everyday use of
the system by all users. Many privileged commands are also included
in DCL.
Privileged commands are those commands that affect system
operations.
For instance,
the SHOW TIME command is a nonprivileged
command, but the SET TIME command is privileged.

1.3.1

The SET and SHOW Commands

The SET commands dynamically alter system characteristics.
The SHOW
commands
display
system
characteristics.
These commands are
introduced in Chapter 2. The most useful functions of SET and SHOW
are also described in Chapter 2.
However, because such a wide variety
of functions can be altered or displayed, the remaining functions of
SET and SHOW are listed in Chapter 2 but described in the appropriate
functional chapter. SET and SHOW are the last commands described in
each chapter.
For example, SET DEVICES and SHOW DEVICES are described
in full at the end of Chapter 5; and SET TERMINAL and SHOW TERMINAL
are described at the end of Chapter 3.
The SET or SHOW command and its function are considered to form a
single command.
That is,
rather than referring to the TERMINAL
function of the SHOW command, you would refer to the SHOW TERMINAL
command.

1-15

HOW TO USE DCL
1.3.2

Terminal Operations

All commands directly related to terminal operations are described
in
Chapter 3.
The commands include BROADCAST,
HELP, LOGIN, LOGOUT,
REQUEST, SET TERMINAL, and SHOW TERMINAL.
In addition, Chapter 3
includes a detailed description of the use of the terminal keyboard on
RSX-llM systems.
All control (CTRL) characters and other important
keys are explained.

1.3.3

Handling Files

Most information in
Directories
(UFOs).
Files-11 volumes.

RSX-llM systems is in files
in User File
These files and directories are located within

All commands relating to files are described in Chapter 4.
The commands include ANALYZE/MEDIA, APPEND, CONVERT, COPY, CREATE,
CREATE/DIRECTORY, DELETE, DIFFERENCES, DIRECTORY,
EDIT,
EDIT/EDT,
EDIT/KEO, EDIT/SLP, PRINT, PURGE, RENAME, SORT, TYPE, and UNLOCK.
SET and SHOW commands described in Chapter
DEFAULT, SET FILE, and SET PROTECTION.

1.3.4

include

SET

and

SHOW

Handling Devices and Volumes

Volumes are held on magnetic media, usually disks.
The volume is in
the RSX-llM format,
called Files-11.
The disks are mounted on
hardware devices.
Devices can be as follows:
•

Public - available to all users

•

Shareable - available to some users but not others

•

Private - available to a single user only

All commands relating to volumes and devices are described in Chapter
5.
The
commands
include
ALLOCATE,
ASSIGN, ASSIGN/REDIRECT,
ASSIGN/TASK, BACKUP, DEALLOCATE, DEASSIGN, DISMOUNT,
INITIALIZE,
INITIALIZE/UPDATE, and MOUNT.
SET and SHOW commands described in Chapter 5 include SHOW
and SET and SHOW DEVICES.

1.3.5

ASSIGNMENTS

Program Development

RSX-llM provides full facilities for program development, which are
described in Chapter 6. The commands described include LIBRARY and
LINK.
SET GROUPFLAGS and SHOW GROUPFLAGS are also described in Chapter 6.

1-16

HOW TO USE DCL
1.3.6

Running Tasks

The task is the fundamental executable programming unit on RSX-llM.
All commands related to running tasks are described in Chapter 7.
These commands include ABORT, CANCEL, CONTINUE, FIX, INSTALL,
RUN, START, STOP/BLOCK, START/UNBLOCK, and UNFIX.

REMOVE,

SET and SHOW commands described in Chapter 7 include SHOW COMMON, SHOW
CLOCK_QUEUE, SET and SHOW PARTITION, SET PRIORITY, and SHOW TASKS.

1.3.7

System Control

System control commands are described in Chapter 8.
Most of these
commands are privileged, but the SHOW commands described in Chapter 8
are nonprivileged.
Only SET and SHOW commands are described in Chapter 8. These include
SET and SHOW
[DAY]TIME, SHOW MEMORY, SET and SHOW SYSTEM/DIRECTORY,
SET SYSTEM/[NO]LOGINS, SET and SHOW SYSTEM/POOL, and SHOW USERS.

1.4

USING THE QUEUE MANAGER:

PRINT JOBS

The RSX-llM Queue Manager provides facilities for printing files on
line printers or other output devices. Files can be printed under
user control or under the control of a system task or applications
task. See the description of the PRINT command in Section 4.4.2.
All uses of the Queue Manager are described in a separate manual,
the
RSX-llM/M-PLUS
Batch
and Queue Operations Manual.
The manual
introduces and explains a~the uses of the Queue Manager. The manual
includes sample print jobs, all commands for placing jobs in queues
and displaying queue contents, and a complete description of the
process of setting up the Queue Manager.
In addition, the manual
includes an explanation of writing tasks to spool output.

1.5

INDIRECT COMMAND FILES IN DCL

In addition to the batch-processing subsystem, RSX-llM provides the
Indirect Command Processor
(Indirect)
as an alternative means of
automatically passing commands to the operating system. If you have a
series of commands to be executed in the same or similar fashion every
time, you can include these commands in a file to be run by Indirect.
Indirect accepts not only DCL and MCR commands, but also special
directives that allow you to program the execution of the indirect
command file.
Indirect is described in full
in the RSX-llM/M-PLUS
Indirect Command Processor Manual.
An indirect command file can include both MCR and DCL commands.
If
the file contains commands to both of these command line interpreters
(CLis), you must either prefix each CL! command with the CL! name,
or
change the CL! setting of your terminal before each CLI command. When
your file has completed, reset the terminal to your usual CL!
in the
indirect command file.
For example, if your terminal is set to DCL
and you have MCR commands in your indirect command file,
you can
prefix each MCR command with "MCR," or set the terminal to MCR before
each command and then reset it to DCL afterwards.

1-17

HOW TO USE DCL
1.6

DCL AND RSX-llM UTILITIES AND SYSTEM TASKS

The RSX-llM operating system includes a number of utilities and other
system tasks designed to assist you in your use of the system. Most
utilities are used to create or alter files in some way.
Many DCL commands invoke these utilities transparently to the user.
Just as some DCL commands are passed to MCR, other DCL commands are
passed to utilities.
One important utility is the Peripheral Interchange Program
(PIP),
which is used to manipulate files. DCL functions such as APPEND,
COPY, DELETE, PURGE, and DIRECTORY depend on PIP. As another example,
the LINK command invokes the RSX-llM Task Builder. Appendix B of this
manual gives information on the relationships between DCL and the
utilities and other system tasks.
For more information on each RSX-llM utility, see the RSX-llM/M-PLUS
Utilities Manual.
RMS-11 utilities are described in the RMS-11
documentation supplied with your system. Some system tasks that might
be considered utilities, such as the Task Builder, are described in
separate manuals.
For descriptions of other useful and important system tasks,
following manuals:
•

RSX-llM System Generation and Installation
description of the process----Of tailoring a
particular installation.

see

Guide
system

the

a
a

•

RSX-llM/M-PLUS MCR Operations Manual - a description of MCR
plus many details on system startup procedures and system
operations.

•

RSX-llM/M-PLUS Indirect Command Processor Manual
description of the Indirect Command Processor.

•

RSX-llM/M-PLUS Batch and Queue Operations
Manual
a
description of the Queue Manager, which controls the orderly
printing of files and other output, and the batch .processing
subsystem, a means of automatic use of the system. Batch
processing is available on RSX-llM-PLUS systems only.

•

EDT Editor Manual - describes the use of EDT, the DEC Standard
editor. The manual includes an introduction to EDT.

•

RSX-llM/M-PLUS Guide to Program Development
a detailed
introduction to-the program development facilities, both DCL
and MCR, of RSX-llM/M-PLUS.

•

PDP-11 MACR0-11 Language Reference Manual - an introduction to
the MACR0-11 Assembly Language and Assembler.

full

and Micro/RSX Task Builder
Manual
a
• RSX-llM/M-PLUS
description of the task building, or linking, process in
RSX-llM.

1-18

HOW TO USE DCL
1.7

RSX-llM DCL AND VAX/VMS DCL

DCL on RSX-llM Version 4.2 and subsequent releases is designed to be
compatible with DIGITAL standard DCL on VAX/VMS Version 3.0 and
subsequent releases.
If the function being performed is identical,
the same DCL command will have the same effect on an RSX-llM system or
a VAX/VMS system. As other operating systems adopt DCL, the same will
be true for them.
In most cases, the default forms of DCL commands will have the same
effect on either kind of system. Furthermore, many qualifiers are the
same and also have the same effect.
On the other hand, operating systems that implement DCL,
including
RSX-llM, will have system-specific extensions to DCL. For example,
RSX-llM systems have several features not available on VMS systems;
DCL commands have been implemented to invoke these features.
The
command syntax for these features is different from any VMS command
syntax to avoid confusion.
In addition, many of the features discussed in this chapter are
RSX-llM extensions to the basic DCL language.
Prompts, HELP, error
messages,
system
displays,
and
command
parsing
(including
abbreviating)
are unique to RSX-llM and may not be fully compatible
with other DCL implementations.
NOTE
All the short forms and abbreviations in DCL are
intended for the convenience of interactive users at
terminals.
You should not use either these brief
command forms, or other abbreviations shorter than
four characters per command element,
in indirect
command files or any other permanent form. As new
commands are added to DCL,. these abbreviations may
change, but the full-format commands are stable.

1-19

CHAPTER 2
THE SET AND SHOW COMMANDS

The SET commands dynamically alter system characteristics.
commands display system characteristics.

The

SHOW

These commands affect every part of the operating system.
Some of
them are needed by every user every day. Others might not be used
once in a year.
SET and SHOW both prompt
Function?
There are more than 20 functions that can be altered or established
with the SET command, and more than 20 others, not all of them the
same, that can be displayed with the SHOW command. Most of the SET
functions include options, values, or negations.
Customarily, the SET or SHOW command and the function are considered
to form a single command.
That is, rather than speaking of the
TERMINAL function of the SHOW command, you would refer to the SHOW
TERMINAL command.
Some of the most commonly used variations on the SET and SHOW commands
are described for your convenience in Sections 2.1 through 2.12.
Full descriptions of all the SET and SHOW command functions appear
later in this manual.
Each chapter concludes with the SET and SHOW
commands appropriate to that chapter. Thus, SET and SHOW TERMINAL are
described at the end of Chapter 3, Terminal Operations, and SET and
SHOW DEVICES are described at the end of Chapter 5, Handling Devices
and Volumes. See the Table of Contents for references.
The following are the most commonly used SET and SHOW commands,
described here in brief form for your convenience. All of these
commands are described in detail elsewhere in this manual.

2.1

SET AND SHOW TIME

Format

SET [DAY]TIME [hh:mm[:ss]]

dd-mmm-yy
mm/dd/yy

You can set both the time and the date with this privileged command.
You can enter the date in either form, for example, 04-JUL-85, or
7/4/85.
In the latter case, mm stands for month number.
No matter
how you enter the date, it will be displayed in the first form.
See Section 8.1.1.

2-1

THE SET AND SHOW COMMANDS
The SHOW [DAY]TIME command displays the current setting of the day and
time on your system.

Format
SHOW [DAY]TIME
See Section 8.1.2.

2.2

SHOW MEMORY
SHOW MEMORY

This command brings up the RMD display, which provides information on
task activity, partitions, drivers, CPU usage, and so forth on your
system.

E'ormat
SHOW MEMORY
On video terminals, this display is dynamic. On hardcopy
the command prints a snapshot of the current RMD display.

terminals,

The display provides a rough picture of the current state of the
system.
Alternate displays include the Active Task List or a single
task header.
Not all systems include this command for
interactive use.
Most
systems, however, do run the display on a slaved video terminal
somewhere near the computer.
See Section 8.1.7 for more information on the memory display.
See
Section 7.12.4 for more information on the task list and task header
displays.

2.3

SET AND SHOW TERMINAL

You can set and display many attributes of your terminal.

The command

Format
SHOW TERMINAL
without any qualifier, displays the current setting
attributes of the terminal, as shown:
TT5:

[303,5]
CLI
DCL
BUF
LINES
TERM
66.
LOWER
NO PR IV NO HOLD
ECHO
NOVFILL NOH HT
AVO
ANSI
DEC
NOHSYNC NOPASTHRU

[303,5]
132.
LA34
NOSLAVE
NOFDX
NOEDIT
TTSYNC

2-2

HF ILL
0
OWNER
NONE
NOESC
NOC RT
WRAP
NOR PA
NOREGIS NOSOFT
NOPRINTER PORT

all

settable

SPEED=(300:300)
BRO
NOABAUD
HFF
NOREMOTE
NOE BC
TYPEAHEAD
NOBLKMOD

THE SET AND SHOW COMMANDS
·The display is explained in full in Section 3.8.2.
the more significant fields:

Here, briefly, are

Terminal number, login UIC, default UFD
CL!
BUF
SPEED
LINES
TERM
OWNER
BRO
NO PR IV

Current CLI setting
Buffer-length, that is, the width in columns
Transmit and receive speed
Page length in lines
Terminal model
Tells whether terminal has been allocated
Terminal can receive broadcast messages
Terminal is not privileged

The SET TERMINAL command permits you to set most of these attributes
for your terminal.
Privileged users can set the attributes of any
term~nal.

Format
SET TERMINAL/attribute[/attribute[s]]
Note that you can set more than one attribute at a
such as the following:
$ SET TERMINAL/VTlOO/LOWERCASE/DCL

time.

command

fBm

is accepted by the system and executed.
Here is a summary of the most important attributes you can set:
/DCL
/PAGE LENGTH:n
/[NO]BROADCAST
/CLI=cliname

/MCR
/WIDTH
/[NO]PRIVILEGE
/HOLD_SCREEN

/UPPERCASE
/LOWERCASE
/SPEED: (transmit,receive)
/SCOPE
/HARD COPY
/INQUIRE
-

You can also set your terminal as a particular model:
/ASR33
/ASR35
/DTCOl
/KSR33
/LA12
/LA30P
/LA30S
/LA34
/VT200 SERIES
See Section 3.8.1
attributes.

2.4

/LA36
/LA38
/LASO
/LAlOO
/LA120
/LA180S
/LA210
/LN03
/PRO_SERIES
for

/VT61
/VTlOO
/VTlOl
/VT102
/VT105
/VT125
/VT131
/VT132

/LQP02
/LQP03
/RT02C
/VTOSB
/VTSO
/VT52
/VT55

information

the

meaning

these

SHOW DEVICES

The SHOW DEVICES command displays the name and other information for
all devices known to the system or, if specified, information for a
specific device.
Format
SHOW DEVICES

2-3

THE SET AND SHOW COMMANDS

This command displays the name and other information for all devices
of a particular type known to the system, where dd is the 2-letter
mnemonic for the device type or pseudo-device type.
See Section
5.11.3.

2.5

SHOW QUEUE

This command displays information about the queue file maintained
the Queue Manager.
Two forms of this command are most useful.

Format

SHOW QUEUE
This command displays information about all jobs in all queues.
In
addition to showing all queue assignments, the information display
includes all Queue Manager QMG jobs and all files
included in those
jobs.
SHOW QUEUE/FULL
This command displays full information about all jobs in all queues.
In
addition to the information displayed by SHOW QUEUE, SHOW
QUEUE/FULL displays all the attributes of all the QMG jobs in the
queue, such as /FORMS, /COPIES, and /PAGE_LENGTH.
See the RSX-llM/M-PLUS Batch and Queue
information on the SHOW QUEUE commands.

2.5.1

Operations

Manual

for

SHOW PROCESSOR

The SHOW PROCESSOR command displays
readers, batch processors, printers,
control of the Queue Manager.

information about the card
and other devices under the

Format

SHOW processortype processorname[/qualifier[s]]
Parameters

processor type
The processortype is one of the following:
BATCH
CARD READER
DEVICE
INPUT
PRINTER
PROCESSOR
CARD READER and INPUT are synonyms.
DEVICE refers to all
nonbatch output processors and is a synonym for PRINTER. BATCH
refers to all batch processors.
A simple SHOW PROCESSOR command displays all
system.

processors

the

See the RSX-llM/M-PLUS Batch and Queue Operations Manual for more
information.

2-4

THE SET AND SHOW COMMANDS

processorname
For physical devices, the processor name is identical
name
of the physical device.
Thus, the device
controlled by processor LPl:.

with
LPl:

the
is

local

and

device

and

Applications processors have names of six characters.

2.6

SHOW ASSIGNMENTS

The SHOW ASSIGNMENTS command displays at your terminal all
login logical-device assignments. See Section 5.11.1.
Format

SHOW ASSIGNMENTS[:ttnn:]

2.7

SET AND SHOW DEFAULTS

The SET DEFAULT command alters your default settings
directory.

for

Format

SET DEFAULT [ddnn:] [g,m]
Parameters

dd
The 2-letter device mnemonic
nn
The 1- or 2-digit device number terminated by a colon
[g,m]
The directory is two octal numbers separated by
enclosed in brackets.

comma

and

The default device name and directory are included automatically in
every file specification included in a command unless overridden. See
Section 4.5.1.
The SHOW DEFAULT command displays
directory. See Section 4.5.2.

your

current

default

device

and

Format

SHOW DEFAULT

2.8

SHOW TASKS

This command displays information about tasks
forms of the command are most useful.
The SHOW/TASKS/ACTIVE command displays
active at your terminal.

2-5

information

the

system.

about

the

Four
tasks

THE SET AND SHOW COMMANDS

Format
SHOW TASKS/ACTIVE
The SHOW TASKS/ACTIVE/ALL command displays information about all tasks
active on the system.

Format
SHOW TASKS/ACTIVE/ALL
The SHOW TASKS/INSTALLED command,displays full information
tasks installed on the system.

about

all

Format
SHOW TASKS/INSTALLED
The SHOW TASKS/INSTALLED/DEVICE command displays
about all tasks installed on the specified device.

full

information

Format
SHOW TASKS/INSTALLED/DEVICE:ddnn:
The following commands display full information on a single active
installed task.

Format
SHOW TASKS/ACTIVE FULL taskname
SHOW TASKS/INSTALLED FULL taskname
See Section 7.12.3.

2.9

SHOW USERS

The SHOW USERS command displays the terminal number and login UIC
each logged-in terminal.

for

Format
SHOW USERS
See Section 8.1.6 for more information.

2.10

SET PROTECTION

The SET PROTECTION command alters the access protection of a file or
files.
If you wish to protect more than one file,
the file
specifications must be separated by commas.

Format
SET PROTECTION filespec[s]
Protection?
(SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:R)

2-6

THE SET AND SHOW COMMANDS
Parameter
filespec
The filespec parameter uniquely identifies a file.
The file
specification specifies the device name on which the volume
containing the file is mounted, the directory in which the file
is located, the file name, the file type, and the version number
of the file.
There are four kinds of access to files and four classes of users
who may access · files.
The previous example shows the code for
the default protection used on the system.
The four classes of users who may access files are as follows:
SYSTEM

Privileged users and the operating system itself.

OWNER

Users logged in under the same user Identification
(UIC) the file was created under.

Code

GROUP

Users logged in under the same group number as
file was created under.

UIC

WORLD

All other users

the

The four kinds of access to files are as follows:
R

READ access.
The file can be typed,
run (if a task image) , and so on.

printed,

copied,

WRITE access.

The file can be written to or altered.

EXTEND access.

The file size can be changed.

DELETE access.

The file can be deleted.

The access you specify is the access that is given.
If you specify
READ access to users in a particular category, those users will be
able to type, print, copy, or run (if it is a task image) your files.
However, your files are protected from being edited or deleted by
those users.
The protection status shown at the beginning of this section
default protection status accorded every file on the system.
PROTECTION to change the protection status of files.

is the
use SET

You must enter the class of user and the type of access in the form
shown.
If you do not wish to change the access rights of a particular
class of user, simply leave that class out.
All users can set the protection of their own files.
Privileged users
can set the protection of any file.
Note that you can set the
protection of a file so no user, including yourself, can do anything
with the file.
If you do this, you will need a privileged user to
reset the protection when you wish to use the file.
You can display the protection of a file with
and /FULL qualifier. See Section 4.3.1.

2-7

the

DIRECTORY

command

THE SET AND SHOW COMMANDS

2.11

SET AND SHOW SYSTEM/DIRECTORY

The Executive, privileged system tasks, and other system files are
kept together in a single directory called the system directory.
In
most cases, this will be the directory [3,54] on the system disk.
An
installation may, however, have more than one UFO containing such
files, and, therefore, more than one system.
For example, an
installation may have one system for regular use and a second for
backup or testing.
The two systems can have quite
different
characteristics.
The SET SYSTEM/DIRECTORY privileged command sets the system
as follows:

DIRECTORY

DIRECTORY displays information on files in directories.
Format
DIRECTORY [/format-qua!] [/destination-qua!]

[filespec [s]]

Command Qualifiers
Format Qualifiers
/FULL
/BRIEF
/FREE[ddnn:]
/SUMMARY
/ATTRIBUTES
Destination Qualifier
/OUTPUT:filespec
Other Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARNINGS
/REWIND
Parameter
filespec[s]
Specifies the file or files
for which information should be
displayed.
If you do not supply a file specification, a complete
directory for the default directory is displayed.
You can supply one or more file specifications, separated by
commas,
and directory
information on the files you name is
displayed.
You can use wildcards in place of any file specification field
except the device field.
If you do not supp~y a v7rsion number,
only information on the most recent versions is displayed.
However,
if you do not supply a file type, a null file type is
assumed.
If you do not know the file type, use a wildcard.
You can display a listing of another directory by supplying the
directory name in this field.
You can also specify device names
in the form ddnn:
in this field.
If you name files in two directories, you should name files
for
the default directory first.
If you name files from another
device or directory first, the defaults are canceled.
See the
examples.

4-26

HANDLING FILES

DIRECTORY (Cont.)
Command Qualifiers
Command qualifiers are in three groups:
1.

Format qualifiers control the appearance of the directory.

Destination qualifiers control where the
sent.

Other qualifiers modify the list of files by creation date or
exclusion.

command

output

If you do not supply a format qualifier, the display is in standard
format, giving the file name, type, and version number, the number of
blocks the file occupies, and the date and time of creation.
If you do not include a destination qualifier, the display appears
your terminal.
If you do not include any of the other
includes all files that otherwise qualify.

qualifiers,

the

display

and

version

Format Qualifiers
/BRIEF
Specifies that the display give file names,
numbers only.

types,

/FULL
Specifies that the complete directory entry be
displayed,
including File ID number, blocks used and allocated, the owning
UIC, protection status of the file,
in addition to all the
information in the standard display.
/SUMMARY
Specifies that the display give only the total number of blocks
allocated and used for the specified files.
If you give no file
specifications in the command, the display shows the total blocks
allocated and used for the default directory.
/FREE [ddnn:]
Specifies that the display give the free space and number of free
file headers on the default device or a specified device.
/ATTRIBUTES
Displays the Record Management Services (RMS-11) attributes of
file or files.
This display includes the following:
•

File name and type

•

Creation date and time

4-27

HANDLING FILES

DIRECTORY (Cont.)

•

File organization

•

Protection status

•

Allocation information

•

Last access date and time

•

Record format

•

Record size

•

Primary and alternate key definitions for indexed files

•

Bucket size for indexed and relative files

This qualifier invokes the RMS-11 DSP utility.
Note that this
display is produced for any file you specify in a DIRECTORY
command, whether or not the file is an RMS-11 file. Some display
information may not be meaningful for. non-RMS files.
See the
RMS-11 documentation supplied with your system.

Destination Qualifier
/OUTPUT:filespec
Specifies that the output of the DIRECTORY command be placed in a
file having the file specification you supply.

Other Qualifiers
/DATE:dd-mmm-yy
Specifies that you wish the DIRECTORY command to list only
created on the date given.

files

/SINCE:dd-mmm-yy
Specifies that you wish the DIRECTORY command to list only
created on or since the date given.

files

/THROUGH:dd-mmm-yy
Specifies that you wish the DIRECTORY command to list only
created on or before the date given.

files

/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the DIRECTORY command to list only
created within that range.

files

/TODAY
Specifies that. you wish the DIRECTORY command to list only
created on the same day the command is being issued.

4-28

files

HANDLING FILES

DIRECTORY (Cont.)
/EXCLUDE:filespec
Specifies that you wish the DIRECTORY command not to list certain
files.
The f ilespec argument to /EXCLUDE can contain either a
single file specification (for example, TEST.DAT;2), or wildcards
in all but one of the file specification fields (for example,
*.DAT;*, TEST.*;*, or *.*;2) if you want to exclude multiple
files.
However, the version number must be given, either
explicitly or as a wildcard (*).
/NOWARNINGS
Suppresses error messages resulting from the command.
/REWIND
Causes the tape to rewind before starting
qualifier is for magnetic tapes only.

the

operation.

This

Examples
$ DIRECTORY (BITl

Directory DBl: [303,5]
l-FEB-85 14:16
A.A;l
ANIML.BAS;l
AZ.CMD;5
BYE.CMD;l
CLEAN.CMD;l
DUN.CMD;4
EDT.CMD;22
LOX.CMD;l
LOGIN .CMD; 6
TI.CMD; 4

1.
6.
1.
1.
1.
1.
1.
1.
1.
1.

F.TSK;l
G.TSK;l
PONG.TSK;2
BUZZ.TXT;2
IZZY.TXT;l
JIVE .TXT; 1

4.
4.
12.
4.
2.

25-SEP-84
24-JAN-85
02-APR-84
25-SEP-84
10-JAN-85
23-JAN-85
07-NOV-84
27-DEC-84
06-JAN-85
30-APR-84

c
c
c

12:29
17:59
13:03
12:29
08:29
08:05
15:56
10:21
15:56
08:36

25-SEP-84 12:30
25-SEP-84 12:30
25-SEP-84 12:31
12-JAN-85 09:13
06-MAR-84 14:33
16-JAN-85 13:23

Total of 2906./3043. Blocks in 160. Files
This example shows a directory listing in the standard format.
The device and directory are named at the head of the listing,
along with the date and the time. All files in the directory are
listed because the user did not supply any file specifications.
The files shown with a C in column 3 are contiguous files, in
this case, task images.
You may see files in a directory with an
L in this position, signifying that the files are locked. Files
are locked when they are closed improperly.
See Section 4.4.5
for information on the UNLOCK command.

4-29

HANDLING FILES

DIRECTORY (Cont.)
$ DIRECTORY/SUMMARY IBtlJ
Storage used/allocated for Directory DBl: [303,5]
l-FEB-85 14:15
Total of 2892./3033.

blocks in 160.

files

This example displays the output produced by the /SUMMARY
qualifier.
If
the
user had supplied one or more file
specifications in the command, the summary would cover the blocks
used and allocated for the specified files only.

$ DIRECTORY/FREE IBtlJ
DBl: has 13742. blocks free, 3269280. blocks used out of 340670.
Largest contiguous space = 5173. blocks
124420 file headers are free, 131510. headers used out of 25593.
This example displays information about the default device.

$ DIRECTORY/FREE LBO:

IBtlJ

DBO: has 6074. blocks free, 334596. blocks used out of 340670.
Largest contiguous space = 3520. blocks
3297. file headers are free, 22296. headers used out of 25593.
This example displays information about the pseudo device LBO:.
Notice that the display gives the physical device name for the
pseudo device.
$DIR TI.CMD IBtlJ
Directory DBl: [303,5]
l-MAR-85 14:17
TI.CMD;4

28-FEB-85 08:36

Total of 1./5. blocks in 1. file
This example displays information on the most recent
the file named. See the next example.

$ DIR TI • CMD; * IBtlJ
Directory DBl: [303,5]
l-MAY-85 14: 17
TI.CMD;4
TI.CMD; 3
TI.CMD;2
TI.CMD; 1

30-APR-85 08:36
27-APR-85 16:32
27-APR-85 16:29
27-APR-85 16:28

1.
1.
1.
1.

Total of 4./20. blocks in 4. files

4-30

version

HANDLING FILES

DIRECTORY (Cont.)
This example displays information on all versions of the file
named because the user supplied a wildcard for the version
number.
$ DIR/FULL TI.CMD

Directory DBl: (303,5]
1-MAY-85 14:17
TI.CMD;4

(300,56)

1./5.

30-APR-85 08:36 (303,5]

[RWED,RWED,RWED,R]

Total of 1./5. blocks in 1. file

This example displays full information on the most recent version
of the file named.
The number in parentheses is the file
identification number assigned by the system when the file is
created.
The first number is the file number, the second is the
sequence number of the file. The UIC is the UIC of the owner,
and the final column is the protection status of the file.
See
the notes.
Protection status is listed in the order system, owner, group,
world. See Section 4.1.6 for an explanation of protection status
and how it can be altered.
$ DIRECTORY/BRIEF *.CMD

Directory DBl: (303,5]
ADV.CMD;2
AZ.CMD;5
BYE.CMD;l
CLEAN.CMD;l
DAY.CMD;l
DTC.CMD;l
DUN.CMD;4
EDT.CMD;22
LOX.CMD; 1
VTK.CMD;l

This example displays brief information on the most
version of all files of the type .CMD in the default UFO.
$ DIRECTORY /TODAY

Directory DB2: (303,5]
5-MAY-85 13: 44
Day of 5-MAY-85
05JAN85.LGI;l
2051CH4.MEM; 1
NEWINSDC3. RNO; 7
2051CH4.MEM; 2
FUT.MAI;l
NEW INS DC 3. RNO; 6
NEWINSDC3.RNO;l0
NEWINSDC4. RNO; 3
FRK.CMD;6
NEWINSDC4. RNO; 4
LOG.LOG;l

o.
339.
10.
320.
1.
9.
10.

7.
1.
11.

05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85

08:20
10:11
10:05
10:12
13: 05
09:55
10:39
11: 46
13:43
13:43
13:43

Total of 708./736. blocks in 11. files

4-31

recent

HANDLING FILES

DIRECTORY (Cont.)
In this example, the user asked for a directory of all files
created the same day the command was issued. Note that the
directory listing includes the date. See next example.
$ DIRECTORY /TODAY/EXCLUDE:*. RNO; *

(BTil

Directory DB2: [303,5]
5-MAY-85 13:45
*.RNO;* excluded
Day of 5-MAY-85

05JAN85.LGI;l
2051CH4.MEM;l
2051CH4.MEM;2
FUT.MAI;!
FRK.CMD;6
LOG.LOG;!

05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85
05-MAY-85

339.
320.
1.
1.
2.

08:20
10: 11
10: 12
13:05
13:43
13:43

Total of 672./693. blocks in 6. files
In this example, the user listed all files created the day the
command was issued but excluded all files with the .RNO file
type.
Note that the filespec argument to /EXCLUDE has a wildcard
version number. Observe also that the exclusion is noted in the
heading of the directory listing.
$ DIRECTORY/ATTRIBUTES YACHT.SEQ (BTil
SY: [303,5]YACHT.SEQ;l
FILE ORGANIZATION:
SEQUENTIAL
CREATED; 25-MAY-1985 12:32
REVISED: 15-JUN-1985 08:19 (5)
FILE PROTECTION:
[RWED,RWED,RWED,R]
RECORD FORMAT:
VARIABLE
RECORD ATTRIBUTES:
CARRIAGE RETURN
FILE ATTRIBUTES:
ALLOCATION= 10 EXTEND QUANTITY=O
This example shows the display from the /ATTRIBUTES qualifier to
DIRECTORY.
Attributes can be displayed for any file, but the
full display has meaning only for RMS-11 files.
$ DIR * • Ts KI

[

3 0 1 I 3 7 0 ] * • TXT (BTil

Directory DB!: [303,5]
20-MAY-85 09:39
CLOCK.TSK;3
F.TSK;l
G.TSK;l
TICTAC.TSK;4
TREK.TSK;l

8.
4.
4.
19.
54.

c
c
c
c
c

15-APR-85
25-APR-85
25-APR-85
Ol-APR-85
25-MAR-85

Total of 89 ./89. blocks in 5. files

4-32

08:55
12:30
12:30
12:07
12:31

HANDLING FILES

DIRECTORY (Cont.)
Directory DBl: [301,370]
20-MAY-85 09:39
FRONT.TXT;l
EDITNEWS.TXT;l2
OZY.TXT;3
TEXT.TXT; 1
NEW.TXT;l
AWARE.TXT;2
IZZY.TXT;lO

3.
2 5.
2.
151.

2.
2.

16-MAY-85
ll-MAY-85
11-MAY-85
11-MAY-85
27-APR-85
27-APR-85
12-MAY-85

11: 23
10:50
10:50
10:50
14:36
13:48
13:42

Total of 184./205. blocks in 7. files
Grand total of 273./294. blocks in 12. files in 2. directories
In this example, a user with the default directory of
[303,5]
requested directory information on files in two directories.
The
default directory was applied to the first files named, the *.TSK
files; these were listed first in the display. The second set of
files displayed, the *.TXT files, were from directory
[301,370],
which was explicitly specified in the command. Note the locked
file.
Compare this example with the next one.

$ DIR [301,370]*•TXT, *.,TSK 00)
Directory DBl: [301,370]
20-MAY-85 09:40
FRONT.TXT;l
EDITNEWS.TXT;l2
OZY.TXT;3
TEXT.TXT;l
NEW.TXT;l
AWARE.TXT;2
IZZY.TXT;lO
ADVENT.TSK;l
DUNGEON.TSK;2
PONG.TSK;2
YCLOCK. TSK; 6
STAR.TSK;2
TICTAC.TSK;5
VTCHS.TSK;l2
XCLOCK.TSK;6
LIFE.TSK;lO

3.
25.
2.
151.

2.
2.
151.
242.
12.
9.
102.
19.
26.
9.
4.

c
c
c
c
c
c
c
c
c

16-MAY-85 11: 23
11-MAY-85 10:50
ll-MAY-85 10:50
ll-MAY-85 10:50
27-APR-85 14:36
27-APR-85 13:48
12-MAY-85 13:42
13-MAY-85 14:12
21-APR-85 09:08
23-MAR-85 14:13
08-APR-85 12:17
13-JAN-85 09:07
Ol-JAN-85 11: 31
06-FEB-85 15:39
03-MAY-85 16:48
03-APR-85 13:28

Total of 758./780. blocks in 16. files
The command in this example is quite similar to the command used
in the previous one, but notice the difference in results.
The
same user, with default directory (303,5], issued the command but
this time the directory (301,370] was specified first, for the
*.TXT files.
Even though no directory was specified for the
*.TSK
files,
these files were also listed from directory
(301,370] -- not from [303,5]. This demonstrates that specifying
a directory in a DIRECTORY command resets the default directory
for the rest of the command or until another directory is
specified.

4-33

HANDLING FILES

DIRECTORY (Cont.)
Notes
For more information on directories in general, see Chapter 3
the RSX-llM/M-PLUS Utilities Manual for more information.

The full format for directory listings may include two dates.
The first is the creation date of the file. The second date
indicates the last time the file was opened by the system or a
task, such as for backup.
The decimal number in parentheses
following the second date is the number of times the file has
been opened in this fashion.
Your directory is a file that you own, but which is kept in
directory
[O,O] on the same volume as your directory.
In
directory [0,0] you will find the Master File Directory
(MFD),
which is a file named 000000.DIR. The MFD is the directory for
directory [0,0]. All directories on the volume appear in this
directory in the same form.
The directory for [303,5] is called
303005.DIR; the directory for [7,40] is 007040.DIR, and so forth.
These directory files have file protection like all other files.
The protection is for the directory file, not for files in the
directory. Since the directory is a file, READ access is the
right to list the directory, and WRITE access is the right to
create files in the directory.
If you do not have EXTEND access
to a directory, you may be denied the right to create more than a
certain number of files in the directory.
DELETE access means
the right to delete the directory file.

4-34

HANDLING FILES

DELETE
DELETE

4.3.2

DELETE deletes specified files and
files occupy.

releases

the

storage

space

the

Format
DELETE[/qualifier]
File(s)? filespec[s]
DELETE[/qualifier] filespec[s]

Command Qualifiers
/[NO]CONFIRM
/LOG
/[NO]QUERY
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yyy
/TODAY
/EXCLUDE:f ilespec
/NOWARN INGS

Parameter
filespec [s]
Specifies the file or files to be deleted.
You must supply the name, type, and version number fields of the
file specifications of the files you wish to delete. Device and
directory fields default to your current device and directory.
You can use wildcards in any file specicif ication field except
the device field.
You need not supply a file type to delete a
file with a null file type.
You can only delete files to which you have DELETE access.
To name more than one file for
specifications with commas.

deletion,

separate

their

file

Command Qualifiers
/LOG
Specifies that a list of the files deleted be displayed
terminal.

your

/[NO]QUERY
/[NO]CONFIRM
Specifies that you want to decide which files should be deleted
on an individual basis.
Each file that is specified in the
command is named. You may enter one of four characters:
Y N -

(Yes) Deletes file named and goes on to next file.
(No) Does not delete file named and goes on to next
file.

4-35

HANDLING FILES

DELETE {Cont.)
G -

(Go) Deletes the file and goes on to delete all other
files specified.
Q - (Quit) Does not delete the file and exits the task.
No additional files are deleted.
Remember that you can specify files by default or wildcard.
See
examples.
If you do not specify a version number, /QUERY is the
default.
/[NO]CONFIRM is a synonym for /QUERY.
See
the
examples.
/DATE:dd-mmm-yy
Specifies that you wish the DELETE command to affect
created on the date given.

only

files

only

files

only

files

only

files

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the DELETE command to affect
created on or since the date given.
/THROUGH:dd-mmm-yy
Specifies that you wish the DELETE command to affect
created on or before the date given.
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you want the DELETE command to affect
created within the specified range.
/TODAY
Specifies that you wish the DELETE command to affect
created on the same day the command is being issued.
/EXCLUDE:filespec
Specifies that you do not want the DELETE command to affect
certain files.
The filespec argument to /EXCLUDE can contain
either a single file specification (for example, TEST.DAT;2), or
wildcards in all but one of the file specification fields (for
example, *.DAT;*, TEST.*;*, or *.*;2)
if you want to exclude
multiple files.
However, the version number must be given,
either explicitly or as a wildcard (*).
/NOWARNINGS
Suppresses error messages resulting from the command.
Examples

$ DELETE ffiDJ
File(s)? *.DAT;* IBDJ
This example deletes all versions of all files of the type .DAT.

4-36

HANDLING FILES

DELETE (Cont.)
$DELETE FILE.FIL;l, ;3, .TXT;5

This example deletes versions 1 and 3 of FILE.FIL, and version 5
of FILE.TXT.
Note that no filename or type is specified for
version 3, and no name for .TXT;S.
$ DELETE/QUERY ID
File(s)? *.TMP;* ID
Delete file
DBl: [303,S]OGRE.TMP
Delete file
DBl: [303,S]TROLL.TMP;l
Delete file
DBl: [303,S]ORC.TMP;l
Delete file
DBl: [303,S]ELF.TMP;l
Delete file
DBl: [303,S]HOBBIT.TMP;l
Delete file
DBl: [303,S]SNIPE.TMP;l

[Y/N/G/Q]? y
[Y/N/G/Q]? y
[Y/N/G/Q]? 1
[Y/N/G/Q]? N
[Y/N/G/Q]? N
[Y/N/G/Q]? G

tBru
ID
ID
ID
tBru
tBru

The following files have been deleted:
DBl: [303,S]SNIPE.TMP;l
DBl: [303,5]SNOPE.TMP;2
In this example, the user specified all files having the type
.TMP in the DELETE command.
Three files were deleted at the
user's choice, and two were retained.
The user then directed
that all rema1n1ng files with the type .TMP be deleted.
There
were two more files, which were deleted and listed.
$ DELETE/CONFIRM ~
File(s)? *.TMP; ID
This example is equivalent to the previous one.
$ DELETE *.DOC (B@
Delete file
DBO: [303,5]WITCH.DOC;2
Delete file
DBO: [303,5]DRY.DOC;4
Delete file
DBO: [303,S]PAYCHECK.DOC;l
Delete file
DBO: [303,5]LOADING.DOC;3
Delete file
DBO: [303,5]LOADING.DOC;4
Delete file
DBO: [303,S]LOADING.DOC;S
Delete file
DBO: [303,5]LOADING.DOC;6

[Y/N/G/Q]? y ID
[Y/N/G/Q]? N tBru
[Y/N/G/Q]? y ID
[Y/N/G/Q]? y tBru
[Y/N/G/Q]? y ID
[Y/N/G/Q]? y tBru
[Y/N/G/Q]? N ~

In this example, the user specified the file type .DOC and a
wildcard for the file name. Because no version number was given,
the DELETE command defaulted to the /QUERY qualifier, enabling
the user to choose which files to delete.
$DELETE/LOG *.LST;* (B@
The following files have been deleted:
DBl: [303,S]RANGER.LST;l
DBl: [303, S]TONTO.LST; 1
DB 1: [ 3 0 3 1 5] RE ID. LST i 1
DB 1 : [ 3 0 3 , 5] S IL VER. LS T ; 1
DB 1: [ 303 1 5] SCOUT. LST i 1
DBl: [303,S]HORNET.LST;l
DB 1: [ 3 0 3, 5] KATO. LST; 1

4-37

HANDLING FILES

DELETE (Cont.)
In this example, the user specified all files with the type .LST
in the DELETE command and asked that they be listed as they are
deleted.

Notes
You must have DELETE access to delete a file.
If you wish to delete using wildcards,
it is wise to get a
directory listing using the same file specifications you plan to
delete.
In this way, you can be sure you are not deleting more
files than you intend to delete.
Remember that under the default file protection on RSX-llM
systems, you have DELETE access to your own files and all files
in directories with the same group number.
See Chapter 9 for DELETE commands directed to the Queue Manager.

4-38

HANDLING FILES

PURGE
PURGE

4.3.3

PURGE deletes all but the latest versions of files, and
storage space the deleted files occupy.

releases

the

Format
PURGE[/qualifier[s]]
File(s)? filespec[s]
PURGE[/qualifier[s]] filespec[s]

Command Qualifiers
/[NO]LOG
/KEEP:n
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARNINGS

Parameter
filespec[s]
Specifies the file group or file groups to be purged.
Because of the nature of the command, you cannot include a
version
number in the file specifications.
Multiple file
specifications must be separated by commas.
Wildcards can be
substituted for UFD, name, and type fields.
You can purge any files to which you have DELETE access.

Command Qualifiers
/[NO]LOG
Specifies that the files deleted by
terminal.
The default is /NOLOG.

PURGE

listed

your

/KEEP:n
Specifies that the n latest versions of a file be retained.
If you do not use this qualifier, all versions but the most
recent of a given file are deleted. That is, the default form of
the command includes the qualifier /KEEP:l. With the qualifier
explicitly stated, all but the n highest numbered versions are
deleted.
PURGE assumes that version numbers are in numerical
sequence and without missing numbers. See example.
If more than one file specification is given with the /KEEP
qualifier, all but the latest n versions of all files listed are
deleted.

4-39

HANDLING FILES

PURGE (Cont.)
/DATE:dd-mmm-yy
Specifies that you wish the PURGE command to
created on the date given.

affect

only

files

affect

only

files

affect

only

files

affect

only

files

Specifies that you wish the PURGE command to affect
created on the same day the command is being issued.

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the PURGE command to
created on or since the date given.
/THROUGH:dd-mmm-yy
Specifies that you wish the PURGE command to
created on or before the date given.
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the PURGE command to
created within that range.
/TODAY

/EXCLUDE:f ilespec
Specifies that you do not want the PURGE command to affect
certain files.
The filespec argument to /EXCLUDE can contain
either a single file specification {for example, TEST.DAT;2), or
wildcards in all but one of the file specification fields (for
example, *.DAT;*, TEST.*;*, or *.*;2)
if you want to exclude
multiple files.
However, the version number must be given,
either explicitly or as a wildcard {*).
/NOWARNINGS
Suppresses error messages resulting from the command.
Examples
$ PURGE (BD)
File{s)? TEMPER.TSK

In this example, all versions of TEMPER.TSK but
deleted.

$ DIRECTORY ASDIC.TMl;*, ELPASO.TEX;*

Directory DBl: [303, 5]
20-MAY-85 13:44
ASDIC.TMl;l
ASDIC.TM1;2
ASDIC.TM1;3
ASDIC.TM1;4
ASDIC.TM1;5

20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-85

1.
1.
1.

4-40

13:41
13:41
13:41
13:41
13:42

the

latest

are

HANDLING FILES

PURGE (Cont.)
ELPASO.TEX;l
ELPASO.TEX;2
ELPASO.TEX;3
ELPASO.TEX;5
ELPASO.TEX;6

20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-85

1.
1.
1.
1.
1.

13:42
13:42
13:42
13:43
13:43

Total of 9./45. blocks in 10. files

$ PURGE/LOG/KEEP:3 ASDIC.TMl

The following files have been deleted:
DBl: [303,5]ASDIC.TM1;1
DBl: [303, 5]ASDIC.TM1;2
$
$

$ PURGE/LOG/KEEP:3 ELPASO.TEX

The following files have been deleted:
DBl: [303,5]ELPASO.TEX;l
DBl: [303,5]ELPASO.TEX;2
DBl: [303, 5]ELPASO.TEX;3
$
$

$ DIRECTORY ASDIC.TMl;*, ELPASO.TEX;*
Directory DBl: [303,5]
20-MAY-85 13:46
ASDIC.TM1;3
ASDIC.TM1;4
ASDIC.TM1;5
ELPASO.TEX;5
ELPASO.TEX;6

20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-85
20-MAY-8 5

1.
1.
1.

13:41
13:41
13:42
13:43
13: 43

Total of 4./20. blocks in 5. files
In this example, the user started with two sets of five files.
The five files named ASDIC.TMl have version numbers in order.
The five files named ELPASO.TEX are numbered 1,2,3,5,6. The user
issued a PURGE command with the qualifier /KEEP:3. Versions 4,
5, and 6 of ASDIC.TMl were kept, but only versions 5 and 6 of
ELPASO.TEX.
This is because the /KEEP:3 qualifier does not save
the three highest numbered files, but rather the highest numbered
file and the next two lower numbered files of the same name in
numerical sequence. If there had been a file ELPASO.TEX;4,
it
would have been saved. Because there was none, the PURGE command
task exited, its work done.
Notes
You can purge any file to which you have DELETE access.

4-41

HANDLING FILES

COPY
4.3.4

COPY

COPY copies files.
COPY creates a sequential file copy of one or more sequential files,
or of records with either indexed or relative file organization.
Format
COPY[/qualifier[s]]
From? infile[s] [/qualifier]
To? outfile
COPY [/qualifier [s]] infile [s] [/qualifier] outfile
Command Qualifiers
/ALLOCATION:n
/[NO]CONTIGUOUS
/NOWARNINGS
/OVERLAY
/PRESERVE DATE
/REWIND /SHARED
/REPLACE
/OWN
/BLOCKSIZE:n
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
Parameters
infile[s]
Specifies the input file or files to be copied.
You must have READ access to a file to copy it.
Multiple file specifications, separated by commas, are accepted.
If you specify multiple input files, they will be concatenated in
a single output file in the order that you specify them.
outf ile
Specifies a single output file to which the input file
is copied.

files

You must have WRITE access to the directory to which you wish to
send a copy.
Under the default protection, you have WRITE access
to your directory and to all directories with the same group
number.
You can change the name, type, and version number of the file
when you enter this parameter. Wildcards in the place of the
name and the type leave the name and type unchanged.
If you use
a wildcard in either of these fields, you must use a wildcard in
both.
4-42

HANDLING FILES

COPY (Cont.)
The output file can be created by COPY. The output file need not
exist when you issue the command. If a file of the same name and
type already exists, then the file you create has a version
If you
number one higher than the highest existing version.
specify a version number for the output file field, then a file
of that version number is created.
If such a file already
exists, the operation fails.
Wildcards are acceptable for output files if the destination is
another directory.
If you have multiple input files and use
wildcards for the output file, you create multiple output files,
each with the name and type of the corresponding input file.
You can send copies to devices as well as
the examples.

directories.

You can also use the COPY command to create multiple
the same file with the same or different names.

copies

See
of

Command Qualifiers
/ALLOCATION: n [.]
Specifies that n blocks of contiguous space be allocated for the
new copy of the file.
Unless the decimal point is appended, n is
octal.
/[NO]CONTIGUOUS
If
this
Specifies that the output file must be contiguous.
qualifier
is not used,
then only files that are already
contiguous remain contiguous when copied.

The default is /NOCONTIGUOUS.
/NOWARNINGS
Suppresses error messages resulting from the command.
/OVERLAY
Causes the contents of the input file or files to be copied into
the output file. Whatever was in the output file is destroyed,
but the file ID is unchanged. The output file must exist before
you issue the command.
/PRESERVE_DATE
Specifies that you want the output file to have the same creation
date as the input file.
The default is to have today's date as
the creation date of the output file.
/REWIND
Causes the tape to rewind before starting
qualifier is for magnetic tapes only.

4-43

the

operation.

This

HANDLING FILES

COPY (Cont.)
/SHARED
Specifies that you want other users to be able to access the file
while you are copying it.
/REPLACE
If the output file has the same name, type, and version number as
an already existing file at the destination, the first file is
deleted and the file you have sent replaces it. The name, type,
and version number stay as they were.
/OWN
Changes the ownership of the file being copied from the source
UIC to the destination UIC.
After execution, both UICs own
copies.
If you do not specify /OWN, the original UIC owns both
If you are copying from another directory to your own,
copies.
use this qualifier.
/BLOCKSIZE:n
Defines block size for magnetic tape. n can be octal or decimal;
if decimal, you terminate n with a decimal point. For example:
/BLOCKSIZE:25.
/DATE:dd-mmm-yy
Specifies that you wish the COPY command
created on the date given.

affect

only

files

affect

only

files

affect

only

files

affect

only

files

Specifies that you wish the COPY command to affect
created on the same day the command is being issued.

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the COPY command
created on or since the date given.
/THROUGH:dd-mmm-yy
Specifies that you wish the COPY command
created on or before the date given.
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the COPY command
created within that range.
/TODAY

/EXCLUDE:filespec
Specifies that you do not want the COPY command to affect certain
files.
The filespec argument to /EXCLUDE can contain either a
single file specification (for example, TEST.DAT;2), or wildcards
in all but one of the file specification fields (for example,
*.DAT;*, TEST.*;*, or *.*;2) if you want to exclude multiple
files.
However, the version number must be given, either
explicitly or as a wildcard (*).

4-44

HANDLING FILES

COPY (Cont.)
Examples
$ COPY (BD)
From? [303,4]TSKBLD.CMD
To? TSKBLD.CMD (BD)

IBrn

This example copies TSKBLD.CMD from
[303,4]
to the current
directory and device. The file is still owned by the source UIC.
$ COPY *.BAS DKl:
This example copies all files with the file type .BAS from the
current device and directory to the same directory on the volume
mounted on device DKl:.
$COPY/OWN TSKBLD.CMD [303,4]BLDFIL.CMD (BD)
This example copies TSKBLD.CMD from the current directory and
device to [303,4], assigns ownership to the destination UIC, and
also changes its name to BLDFIL.CMD.
$ COPY/CONTIGUOUS LITTER.DAT *.* (BD)
This example creates a new version of the file
new version is contiguous.

LITTER.DAT.

The

$ COPY OLD1.FIL,OLD2.FIL (BD)
To? NEW. ONE (BD)
This example copies two previously existing files
file.
$ COPY CHARLA.DMP TT41:

into

one

new

(BD)

This example prints a copy of CHARLA.DMP on TT41:.
This is a
convenient means of sending messages longer than one line.
If
the terminal is busy at the time you send the copy, the copy is
held until the terminal is clear and then sent.
$ COPY FLY. TXT SPIDER. TXT (BD)
This example creates the file SPIDER.TXT with the same
as FLY.TXT, both on the current device and directory.

4-45

contents

HANDLING FILES

COPY (Cont.)
Notes
C is the short form of copy.
COPY does not affect file organization. If you wish to change
file organization, use the CONVERT command, Section 4.3.6.
Usually, READ access is much broader than WRITE access.
Under
the default protection setup, your READ access covers the whole
system, but your WRITE access is limited to other directories
with the same group number. Thus, you can copy from many places
that you cannot copy to.
Also, when you copy a file, you do not copy its protection code.
Your copy has the default protection code.
Use SET PROTECTION if
you want to change the protection code of the copy.
Note that you can change the name, type, and version number of
single file as you copy it.

4-46

HANDLING FILES

RENAME
RENAME

4.3.5

RENAME changes the name, type, or version number of an existing file.

Format
RENAME[/qualifier[s]]
Old file name? inf ile
New file name? outf ile
RENAME[/qualifier[s]] infile outfile

Command Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yyy
/TODAY
/EXCLUDE:f ilespec
/NEW VERSION
/NOWARNINGS

Parameters
infile
Specifies the file to be renamed.
You may give a wildcard (*) for either the file name or the file
type,
or both.
If you use a wildcard in these fields, you must
supply an entry in the version number field.
This may be a
wildcard.
If you give a wildcard for version number, all versions retain
their old version numbers.
If no version number is supplied,
only the highest version of the named file is renamed.
It has
the same version number as the old file.
If other files having
the new name exist, then you receive an error message.
outf ile
Specifies the new name for the file.
Wildcards leave that portion of the file specification the
as before. No wildcard is needed for the version number.

same

Command Qualifiers
/DATE:dd-mmm-yy
Specifies that you wish the RENAME command to affect
created on the date given.

only

files

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the RENAME command to affect
created on or since the date given.

4-47

HANDLING FILES

RENAME (Cont.)
/THROUGH:dd-mmm-yy
Specifies that you wish the RENAME command to affect
created on or before the date given.

only

files

only

files

only

files

/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the RENAME command to affect
created within that range.
/TODAY
Specifies that you wish the RENAME command to affect
created on the same day the command is being issued.
/EXCLUDE:filespec
Specifies that you do not want the RENAME command to affect
certain files.
The filespec argument to /EXCLUDE can contain
either a single file specification (for example, TEST.DAT;2), or
wildcards in all but one of the file specification fields (for
example, *.DAT;*, TEST.*;*, or *.*;2)
if you want to exclude
multiple files.
However,
the version number must be given,
either explicitly or as a wildcard (*).
/NEW_VERSION
Specifies that the renamed file be given a new version number.
/NOWARNINGS
Suppresses error messages resulting from the command.
Examples
$ RENAME ~
Old file name? INTRO .TXT ~
New file name? APPENDIX.TXT

In this example, the most recent
APPENDIX.TXT; 1.
$ RENAME IZZY.TXT;4 FIZZY.*

version

INTRO.TXT

In this example, IZZY.TXT;4 becomes FIZZY.TXT;l.
of IZZY.TXT are not affected.
$ RENAME AMA.DOC; 4 *. *; 11

becomes

Other

versions

In this example, AMA.DOC;4 becomes AMA.DOC;ll.

$ RENAME MAIN.TSK;* EXTRA.TSK

In this example, all files named MAIN.TSK are renamed EXTRA.TSK.
The version numbers remain the same, regardless of sequence and
order of file creation.

4-48

HANDLING FILES

RENAME (Cont.)
$RENAME MAIN.TSK;* SUB.* (8ITl
In this example, all versions of MAIN.TSK are renamed SUB.TSK.
Versions are in the order of creation, with numbers unchanged.

$REN EXHAUST.*;* REFRESH.* (8ITl
In this example, all files named EXHAUST of whatever type are
renamed REFRESH. Their file types remain the same. Note that a
wildcard is given for the input file type.
This makes an entry
in the version number field mandatory.
Notes
You cannot rename files across devices.
Using wildcards is also
yourself.

tricky.

4-49

Experiment

before

committing

HANDLING FILES

CONVERT
4.3.6

CONVERT

The CONVERT command invokes the RMSCNV utility, which moves records
fom one file to another. RMSCNV reads records from an input file and
writes them to an output file.
The action of RMSCNV depends on the
organization -- sequential, relative, or indexed -- of the two files,
and on the qualifiers you include in the CONVERT command.
See the
RMS-11 documentation supplied with your system for more information.
Format
CONVERT[/qualifier[s]]
Input file? inf ilespec
Output file? outfilespec
CONVERT[/qualifier[s]] infilespec outfilespec
Command Qualifiers
/[NO]APPEND
/BLOCK SIZE:n
/[NO]FIXED CONTROL
/[NO]IDENTIFICATION
/INDEXED
/KEY [: n]
/[NO]LOG FILE[:filespec]
/[NO] MASS INSERT
/MERGE
/[NO] PAD[: [#]arg]
/RELATIVE
/[NO]REPLACE
/SEQUENTIAL
/[NO]TRUNCATE
Parameters
inf ile
Specifies the file that is the source of records to be written to
the output file.
CONVERT reads input records sequentially,
regardless of the organization of the input file.
No wildcards
permitted.
outfile
Specifies the file that is to receive the records from the input
file.
The default file organization for the output file is
sequential.
If the output file is not sequential, use the
/RELATIVE or /INDEXED qualifier to indicate the organization.
If
the output file is to be sequential, CONVERT can create the file;
it need not exist prior to your entering the CONVERT command.
CONVERT cannot create indexed or relative files; these must have
been created prior to your entering the CONVERT command.
See the
RMS documentation supplied with your system.
No wildcards
permitted.

4-50

HANDLING FILES

CONVERT (Cont.)
Command Qualifiers
/[NO]APPEND
Specifies that you wish RMSCNV to append records to the end of an
existing sequential file.
If the output file is not sequential,
RMSCNV ignores the qualifier. You cannot use both /APPEND and
/REPLACE in the same command line.
The default is /NOAPPEND, but the action taken depends on the
presence of the /REPLACE qualifier in the command line.
If you
specified /REPLACE, RMSCNV performs the replace operation.
If
you did not specify /REPLACE, RMSCNV creates the next higher
version of the file.
This qualifier is the equivalent of the /AP switch in
command line.

RMSCNV

/BLOCK_SIZE: n
Specifies the
on magnetic
RMSCNV rounds
not specify
characters.

physical block size of an output file being created
tape.
n can be from 18 through 8192 characters.
this value up to the next multiple of 4.
If you do
this qualifier, the default tape block size is 512

This qualifier is the equivalent of the /BL switch in
command line.

RMSCNV

/[NO]FIXED_CONTROL
The
/FIXED_CONTROL
qualifier
directs
RMSCNV
to
handle
variable-with-fixed-control
(VFC)
format records in either the
input file or the output file.
If the fixed-control area of the
input file and the output file are the same size, RMSCNV performs
a straightforward copy. See the RMS-11 documentation supplied
with your system for
information on how RMSCNV handles other
combinations.
If you include this qualifier and neither file
specifies VFC records, RMSCNV terminates.
This qualifier is the equivalent of the /WF switch in
command line.

RMSCNV

The default is /NOFIXED CONTROL. This means that if one of the
named files contains VFC records, the fixed-control area of each
record is ignored. That is,
if the input file includes VFC
records and the output file does not, only the variable portion
of each record is written to the output file; if the output file
includes VFC records and the input file does not, data is written
only into the variable portion of each output record.
/[NO]IDENTIFICATION
Requests that RMSCNV print its current version number and patch
level on your terminal.
See the RMSCNV documentation for more
information.
This qualifier is the equivalent of the /ID switch in
command line.
The default is /NOIDENTIFICATION.
4-51

RMSCNV

HANDLING FILES

CONVERT (Cont.)
/INDEXED
The /INDEXED qualifier informs RMSCNV that the output is of
indexed organization.
Regardless of their organization, all
input files are read sequentially.
RMSCNV reads each record from the input file,
then applies the
output file's record format, that is, key placement within the
record, to the data.
If you do not specify the /KEY qualifier
with a value, the key of reference is the primary key; otherwise,
it is the key you specify.
This qualifier is the equivalent of
RMSCNV command line.

the

/FO:IDX

switch

See the RMSCNV documentation for more information.
/KEY [: n]
Indicates the key that establishes the order in which records are
read sequentially from an indexed input file and written to the
output file.
n can be from 0 through 9. The default is n=O and
indicates the primary key; n=l is the first alternate key; n=9 is
the ninth alternate key.
This qualifier is the equivalent of the /KR switch in
command line.

RMSCNV

/[NO]LOG[:filespec]
Directs RMSCNV to summarize processing in a log.
If you do not
include a file specification, the log appears on your terminal.
If you name a file, that file will be created and written to by
RMSCNV.
The log includes the following elements:
1.

The command string in RMSCNV format.
same as DCL format.

This will

not

the

Copies of all error messages produced during execution.

An indication of any duplicate-key problems.
If the log is
appearing on the terminal, the indication consists only of
the following message:
SOME DUPLICATE RECORDS NOT WRITTEN
If the log is being written to a file,
RMSCNV supplies the
indicator DUP RCD= followed by the first 72 characters of the
record that could not be written.

This qualifier is the equivalent of the /SL switch in
command line.
The default is /NOLOG meaning that
appear on your terminal.

4-52

only

normal

error

RMSCNV
messages

HANDLING FILES

CONVERT (Cont.)
/[NO]MASS INSERT
Directs RMSCNV to activate the RMS-11 mass insert I/O technique
and then use sequential put operations to insert records into the
output file.
This is the equivalent of the /MA switch
line.

RMSCNV

command

The
default
for
nonsequential
file
organization
is
/NOMASS INSERT.
See the RMS-11 documentation supplied with your
system tor further information.
/MERGE
Directs RMSCNV to copy records from the input file into
output file.
Both files must be of the same organization.

the

I [ N 0] PAD [ : [ # ] a r g]
Directs RMSCNV to pad records read from the input file
to the
output file's record length before writing them to the file.
If
you specify the qualifier without an argument, the pad character
is null.
If you do not include the number sign (#), the argument
can be any printing ASCII character except:
the number sign,
question mark (?), or commercial-at sign (@).
If you include the
number sign (#), n can be an octal number from 0 through 377,
representing the full ASCII character set.
This enables you to
use the three excluded characters as pad characters by specifying
43 for #, 77 for ?, and 100 for @.
Use this qualifier only
fixed-length records.

when

the

output

file

This qualifier is the equivalent of the /PD switch in
command line.

specifies
an

RMSCNV

/RELATIVE
Informs RMSCNV that the output file is of relative organization.
Regardless of their organization, all input files are read
sequentially.
The /RELATIVE qualifier is the equivalent of the
in an RMSCNV command line.

/FO:REL

switch

RMSCNV reads records from the input file and writes them into
successive record cells of the output file, beginning with cell
1.
If RMSCNV encounters a cell containing a record,
it
terminates with an error message. All records written to that
point are in the output file.
You should examine the two files
to determine how far the processing went.
See the RMS-11 documentation supplied with your system
information.

4-53

for

HANDLING FILES

CONVERT (Cont.)
/[NO]REPLACE
Directs RMSCNV to supersede an existing sequential file.
RMSCNV
replaces a file in the output account with the same file name,
type, and version number. You cannot use /REPLACE and /APPEND in
the same command line.
The /REPLACE qualifier is the equivalent
command line.

/SU

RMSCNV

The default is /NOREPLACE, but the default action depends on
whether the command line includes an /APPEND or not.
If you
specify /APPEND, RMSCNV performs the append operation.
If you do
not specify /APPEND, RMSCNV creates the next higher version of
the file.
/SEQUENTIAL
Informs RMSCNV that the
output
file
is
of
sequential
organization.
Regardless of their organization, all input files
are read sequentially. The default output file organization for
RMSCNV is sequential.
This qualifier is the equivalent of
RMSCNV command line.

the

/FO:SEQ

switch

If you do not specify either the /APPEND or /REPLACE qualifier,
and the output file is sequential, the output file need not exist
before you issue the CONVERT command.
If the output file does not exist, RMSCNV creates an output file
with the record attributes of the input file.
RMSCNV then reads
records from the input file and writes them sequentially into the
new output file.
If the output file already exists, and the command does not
include the /APPEND qualifier, RMSCNV creates the next higher
version of the file.
RMSCNV then reads records from the input
file and writes them sequentially into the new version of the
output file.
If the output file exists and you specify the /REPLACE qualifier,
RMSCNV reads records from the input file and writes them
sequentially into the output file, starting with the beginning of
the file.
If the output file exists and you specify the /APPEND qualifier,
RMSCNV reads records from the input file and writes them into the
output file, starting with the record position following the last
record already in the file.
/[NO]TRUNCATE
Directs RMSCNV to truncate records read from the input file to
the output file's record length before writing them into the
output file.
The trailing bytes of the record are truncated.

4-54

HANDLING FILES

CONVERT (Cont.)
The default is /NOTRUNCATE.
If you do not specify /TRUNCATE and
the input records are too long, RMSCNV terminates with the
following message:
CON -- Input and output record sizes do not correspond
Examples
$ CONVERT ~

Input file? FOO.BAR ~
Output file?
POOH.BAR ~
The output file does not exist. RMSCNV creates the sequential
file POOH.BAR and copies the records from FOO.BAR into it.

$ CONVERT FOO.BAR POOH.BAR

This example is the equivalent of the previous one.

$ CONVERT/INDEXED GRIZZLY.BAR CROW.BAR

RMSCNV reads each record of the
input
file
GRIZZLY.BAR
sequentially and examines the contents of the primary key field,
which is defined as an attribute of CROW.BAR.
RMSCNV then
inserts the record into CROW.BAR.

$ CONVERT/RELATIVE/KEY:l SAND.BAR MAX.BAR

RMSCNV reads the indexed input file SAND.BAR,
using the first
alternate key of the file to establish the sequence of access.
Then RMSCNV writes the records sequentially into an empty
relative output file MAX.BAR, starting with record cell 1.
Note that the /RELATIVE qualifier refers to the organization of
the output file and the /KEY qualifier refers to the organization
of the input file.

$ CONVERT/APPEND/SEQUENTIAL/KEY:2 RUNNING.BAR CORNER.BAR

RMSCNV reads the indexed input file RUNNING.BAR, using the second
alternate key of the file to establish the sequence of access.
Then RMSCNV appends the records at the end of the existing
sequential output file CORNER.BAR.
If the /APPEND qualifier had not been specified,
RMSCNV would
have created the next higher version of CORNER.BAR and written
the records from RUNNING.BAR into it.

$ CONVERT/RELATIVE/FIXED_CONTROL MAMA.BAR PAPA.BAR

RMSCNV reads fixed-length records from the indexed input file
MAMA.BAR,
using
(by default)
the primary key of the file to
establish the sequence of access.
The RMSCNV writes the records
sequentially in a VFC format
into the existing relative file
PAPA.BAR.
Record format is an attribute of each file.
As each
record is written, the first bytes become the fixed control area.
4-55

HANDLING FILES

CONVERT (Cont.)
$ CONVERT/TRUNCATE/BLOCK SIZE:l024/APPEND/KEY:9 BRER.BAR
Output file? MM3:BRER.BCK ~

RMSCNV reads the indexed input file BRER.BAR, using the file's
ninth alternate key to establish the sequence of access. The
RMSCNV writes the records to magnetic tape,
truncating them to
the output file's record length before adding them to the end of
the existing file, and formatting the tape blocks to 1024 bytes
each.
Notes
You must have a clear understanding of RMS-11 and the various
forms of file organization it supports before using the CONVERT
command. See the RMS-11 documentation supplied with your system
for further information.
Sequential files used with the CONVERT command have been
by FCS.

4.4

created

OTHER FILE-RELATED COMMANDS

The commands in this section perform varied
These commands are as follows:

actions

your

TYPE

Displays files on your terminal.

Prints files on the system line printer.

APPEND

Alter the contents of certain files.

DIFFERENCE

Displays the differences between two files.

UNLOCK

Unlocks locked files.

4-56

files.

HANDLING FILES

TYPE
4.4.1

TYPE

TYPE prints selected files on your terminal.

Format
TYPE[/qualifier[s]]
File(s)? filespec[s]
TYPE[/qualifier[s]] filespec[s]

Command Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:f ilespec
/NOWARN INGS
/SHARED

Parameter
f ilespec [ s]
Specifies the file or files to be printed on your terminal.
You can specify any file to which you have READ access.
The file name and type must be specified explicitly or specified
using wildcards
(* or %) • If no version is specified, the most
recent version is printed. A wildcard in any field prints every
file that matches otherwise.
Both the * and the % wildcards are
accepted.
You can also specify a device and a directory.
If you do
these fields default to the current device and directory.

not,

Multiple file specifications must be separated by commas.

Command Qualifiers
/DATE :dd-mmm-yy
Specifies that you wish the TYPE command
created on the date given.

affect

only

files

affect

only

files

affect

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the TYPE command
created on or since the date given.
/THROUGH:dd-mmm-yy
Specifies that you wish the TYPE command
created on or before the date given.

4-57

HANDLING FILES

TYPE {Cont.)
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the TYPE command
created within that range.

affect

only

files

Specifies that you wish the TYPE command to affect
created on the same day the command is being issued.

only

files

/TODAY

/EXCLUDE:filespec
Specifies that you do not want the TYPE command to affect certain
files.
The filespec argument to /EXCLUDE can contain either a
single file specification (for example, TEST.DAT;2), or wildcards
in all but one of the file specification fields (for example,
*.DAT;*, TEST.*;*, or *.*;2) if you want to exclude multiple
files.
However, the version number must be given, either
explicitly or as a wildcard (*).
/NOWARNINGS
Suppresses error messages resulting from the command.
/SHARED
Specifies that you want other users to be able to access the file
while you are typing it.
Examples
$ TYPE ffiDJ
File(s)? LOGIN.CMD ffiDJ
• ENABLE QU !ET
.IF <CLI> EQ "MCR" SET /DCL=TI:
SET TERMINAL LOWER
ASSIGN DBl: SYO:
@AZ

This example prints the file LOGIN.CMD from
and directory on your terminal.

the

current

device

the

current

device

$ TYP [303,12]LOGIN.CMD ffiD)
.IF <CLI> EQ "MCR" ASN DBl:=SY:
.IF <CLI> EQ "DCL" ASSIGN DBl: SYO:
TYPE LOGIN.TXT
TYPE A.A
SET /DCL=TI:
This example prints the file LOGIN.CMD from
and directory [303,12] on your terminal.

4-58

HANDLING FILES

TYPE (Cont.)
$TYPE [*,*]*.FIL;* ID
This is the beginning of a file named ARTHUR.FIL.
It goes on for several lines.

THIS MARKS THE INITIATION OF A FILE CALLED ALBERT.FIL.
IT TOO CONTINUES AT SOME LENGTH.

Now comes a file that starts like this called Z.FIL.
And some more.

At last, we reach the beginning of a file named FILLIE.FIL.
Again some more text and then
The last two lines of FILLIE.FIL.

zzzzzzzzzzzzzzzzzzzzzzzzzzzz
$

This example prints on your terminal all versions of
having the type .FIL located on the current device.

all

files

Notes
In general, RSX-llM documentation uses the term "print" to refer
to any output sent to a terminal and "type" to refer to any user
input from a terminal. The name of the TYPE command
is an
exception to this rule.
If you are typing multiple files, the CTRL/O feature works
in a
slightly different fashion. When you enter a CTRL/O, output is
discarded until you type another CTRL/O or until the beginning of
the next file
is reached, whereupon output is sent to your
terminal again.
This leaves you free to use CTRL/O on a
file-by-file basis.
You can type any file, but normally only
readable.

4-59

ASCII

text

files

are

HANDLING FILES

PRINT
4.4.2

PRINT queues files for printing on a line printer.
It can also be
PRINT defines a QMG
used to queue jobs for other output devices.
print job.
Format
PRINT[/qualifier[s]]
Fi le (S) f ilespec [/qualifier [ s] ] [, filespec [ s]]
PRINT[/qualifier[s]] filespec[/qualifier[s]] [, filespec[s]]
Command Qualifiers

File Qualifiers

/[NO]DELETE
/COPIES:n
/DEVICE :ddnn:
/[NO]HOLD
/JOB COUNT:n
I [NO]JOB PAGE
/[NO] LOWERCASE
/[NO]UPPERCASE
/QUEUE:queuename
/PAGE COUNT:n
/NAME!jobname
/PRIORITY:n
/FORMS:n
/LENGTH:n
/[NO]RESTART
/[NO]FLAG PAGE
/AFTER: (dd-mmm-yy hh:mm)
(mn/dd/yy hh:mm)
/AFTER:TOMORROW
/NOWARNINGS

/[NO]DELETE
/COPIES:n

Parameter
filespec [s]
Specifies the file or files to be printed on the line printer.
Multiple file specifications must be separated by commas.
The asterisk wildcard (*) can be used in directory, name,
type,
and version number fields,
but only to stand for the entire
field. Wildcarding of the form L*.TXT is not accepted by PRINT,
nor is the percent sign wildcard (%) accepted.
If your file specification includes no
file type is .LST.

file

type,

the

default

Command Qualifiers
/[NO]DELETE
Specifies that files be deleted or not deleted from the directory
after they are printed. The default is /NODELETE.

4-60

HANDLING FILES

PRINT (Cont.)
The /[NO]DELETE qualifier to the file specifications can be used
to override this qualifier for a given file in a list of file
specifications.
/COPIES:n
Specifies the number of copies to be printed.
The default is
/COPIES:!.
If your PRINT command includes this qualifier and
specifies more than one file,
the resulting QMG print job
consists of the specified number of copies of the first file
named, followed by that many copies of the second file,
and so
on.
If you wish to print multiple copies of files by sets, use
the /JOB_COUNT qualifier. See the examples.
The /COPIES:n qualifier to the file specification can be used to
override this qualifier for a given file
in a list of file
specifications.
/DEVICE:ddnn:
Specifies that you want the file printed on a particular device.
/[NO]HOLD
Specifies that you wish the QMG print job to be held in its queue
until you release it.
See the RELEASE/JOB or RELEASE/ENTRY
commands in Chapter 9, or the RSX-llM/M-PLUS Batch and Queue
Operations Manual. The default is /NOHOLD.
~~/JOB_COUNT:n
Specifies the number of sets of files you wish printed.
The
default is /JOB COUNT:l.
If your PRINT command includes this
qualifier and specifies more than one file,
the resulting QMG
print job consists of a set consisting of the files named in
order, followed by another set, and so on.
If you wish to print
multiple copies of one or more files, but not in sets, use the
/COPIES qualifier. See examples.
/[NO]JOB_PAGE
Specifies whether you wish a
job flag page printed at the
beginning of the QMG print job. The default is /JOB PAGE.
Use
/NOJOB PAGE when you are printing on special forms, or otherwise
do not wish to include a job flag page.
See the /[NO]FLAG PAGE
qualifier for controlling file flag pages.
Figure 4-2 shows- the
difference between job flag pages and file flag pages.
/QUEUE:queuename
Specifies the name of the print queue in which the job is
placed. The default is the PRINT queue.

/[NO]UPPERCASE
Specifies that the print job can be sent to a line printer
without the lowercase character set. The default is /UPPERCASE.

4-61

** ~sx-11~ v4,1 ••
** RS••11~ vu,1 **
** RSx•lt~ V4o1 **

~12345o789~12la,o789

~12345o789di2jL1,01sq
012345b789~1254,o78~

[7,o7JTl:.ST
•NO ~A~E LIMIT
FUQM ·~ • ~C~MAL MARD~A~f FOR~S
NO IMPLIED FO~~ Fi:.ED
Ou1sl7,o7JTEST,CMDrl

** ~bX•11M ¥4,1 **

012345b789~12l4,o7S9

2tJ•MAY•85
24•!'4AY•85
24•MAY•85
24•''14Y•85

iil91H :S8

~123U5o789~12J45b789

~12345&789~123450789
012J45~789~1234~b789
012J45b78Y~12345b789

~9t39

0909 38

09&Jq 38

-z

::D
~

......-..

n
0

llllll

71711771

l[llll
ll
l(
l[

77777777
77
77
77

I"'(

l[
lc
ll
Ll
l(
llllll

(I)

lCllll

.....

c::

77777777

bbbbbb

77777777

77
77

I I I I

,,, ,
,,,,
,,
,,
,,
I I I I

77
77

17
77

I I

77
17

JlJllJ
ll J J l J

77
77

00
00
00000000

000000
bb
bb

000000

..,__

bbbbbbbb
bb
bb
bb
bb
bb
bb
bb
bb
bbbbbb

,..
.:::J

77
77

Jl
JJ

77
77

Jl
J l J) JJ
Jl J J J ]

:x:
)II

ii::.

°'"'

I:"'

t-4

'-'
0

~
I--'

IQ
(I)

TTTTTrTTTT
TTTTTTTTTT
TT

Tt
Tt

Tt
Tt
Tt

Ti
Tt

Tt
Tt

t.fEHEt:.HI:.
tEEt:.tHHE

Et. - Et.
H

Et.
Et.Ht.Ht.
£U.EtHE
lt.. Et.
Et.
Et.
tEEt.i:.t.EEt:E

HEHEEEEI:.

ssssssss
ssssssss

~
t-4

TTTTTTTTTT
TTTT TT TT TT

SS
SS

SSS SSS
SS
SS
S$

**
* * ·RSX• 11 r-i V 4, 1 **

~1231JS0789d1254>ot89

** RSX•11M vu.1

~12345o789~i2i4,01s9

** RSX•11M vu.1 **

~12345b789~12l4So7~9

~123~5o789~1zj4,0789

tzJ

TT
TT
TT

ssssss

ssssssss
ssssssss

I:"'

** RSX•l1M vu,1 **

TT
TT
TT
TT

TT
TT
TT

l7107JTESI
FO~M

•NO PAGE LIMIT

•0 ··NO~MAL ~•wo~A~I:. FO~MS

Ft.ED
0Jlll7107JTESJ,CMOJ1
~O

I~PLIED

FO~"I

24•MAY•85
24•"1AY•85
i!4•"ilAV•8S
clJ•MAV•85

"'9U913~

09139: 38
091j9:J8

(19:39: 38

~12J45o789~12345b789
t,t2345b769~12345b789
?-1234,b789~12345b789
0123usc789~12345o789
ZK-4209-85

** ~SX•l1M va,1 **
** ~SX•tlM V4e1 **

~i23a~o769dlcJ4~o789

dl2345o789dlcjuso7s9

** ~SX•llM V4,l **

~1234So789J12~1.1,&789

TTTTTTTTTT
TTTTTTTTTT
TT
TT
Tt

t.E

£E.Et.t:.EH
tE.f.t.tEEE

Tf
Tf

.....

l.O

Ii
Cl>

s
s
s

£E

rt
TT
Tt
t'Zj

t.Ht.t.tl:.Ht.
tf.Et.tEEEh
tE. -

H. H
H
EE

£E.Et.t.EEt.EE

HE.ttHEEE

- - -

ssssssss
ssssssss

21J•M/\Y•85

L•9U9:45

COPY 1 OF l

21.1•M~Y•B5

Dt.LlTlON ~OT SPt:.CIFIED

24•MAY•85

l(.l9L)CJ&1.15
ii191Hll.l5

~1251.15o78901211.1~01a9
~12345078901211.1~0789
~1254~b78901231.1~b/89

TTTTTTTTTT
TT TT TT TT TT
TT
TT
TT

TT
TT

ssssss
ssssss

ssssssss

0J1:L7,o7JTEST,CM0J1

SS
SS
SS
SS

SSS SSS SS

.....
....' '.

I I I I

TT
TT

>
z
0

C""

°'w

t-4

Cl
t'Zj
.....

......
Cl>
t'Zj

......
QI

l.O
ltJ

QI
l.Q
<1)

cc
cc
cc
cc
cc
cc
cc
cc
cc
c~

cccccccc
cccccccc

"1M

"'"'
M"!

"""'

MMf'4M
MMl'1M

"'"'"'"'
001M

M"I
MM

MM
MM
MM

ccc~cccc

"1M
MM
MM

"'""
"' "'
MM

"'"'
cc cc cc cc

"'"'

"11'1

"'"'

l'IM

"'"'

ODDDDOOD
ODDDDDDD
DD
OD
DO
DD
DO
DD
DD
OD
DO
DD
DO
DO
DD
DO
DD
DD
DO
DO
00
DO
ODOODOOO
DDDODDDD

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

"ii

t-4

11
1111
1111
11
11
11

C""
t:i:J

11
11
11
11
11
111111
111111

.,,

-z:u
-I

0123aS0789~1cJ4~o

01Z345o789~1ll45b

89
01234S6789~1l~450 89

**
** ~SX•l1M V4e1 **

** RSX•tl"' V41l

** ~SX•11~ V41l **

ou11l7107JTlST,CMDJ1

COPY 1 OF 1
DELETlO~

NOT SPECIFIED

24•MAY•65
24•MAY•8S
24•MAY•8S

091l9US

01234~078901214~0769

0913CJ&45

01234~o7B9~12345o789
012!45b789~1231.15&789

091391"5

ZK-4210-85

.--..

n
0

....
..........
~

HANDLING FILES

PRINT (Cont.)
/[NO]LOWERCASE
Specifies that the print job must be sent to a line printer
having the lowercase character set. The default is /NOLOWERCASE.
/PAGE_COUNT:n
Sets a limit on the number of pages the job may produce,
from 1 through 32767.

ranging

Without this qualifier, the number of pages is unlimited (n=O).
/NAME:jobname
Specifies a name for the print job.
alphanumeric characters.

Your job name

can

nine

If you specify a job name, that name appears on the flag page at
the beginning of the printed output. Otherwise, the file name of
the first file is used as the job name.
The job name also appears in the SHOW QUEUE display.
name includes the UIC under which it was entered.

The

job

There can be more than one job of the same name, but each job has
a unique entry number which appears in the SHOW QUEUE display.
/PRIORITY: n
For nonprivileged
Sets the queue priority of the print job.
users, n can be from 0 through 150. Privileged users can set n
up through 250. The default is 50.
The Queue Manager prints the highest priority jobs first.
When
two jobs have the same priority, the job that has been in the
queue longest is printed first.
/FORMS:n
Specifies the type of form on which the job must be printed.
n
can have a value from 0 through 256. The default is O. See your
system manager for details on how to specify the particular forms
used at your installation.
/LENGTH:n
Sets the length of a logical page; n can be any number from 0
through 255.
The default is n=O.
If you set a length, a form
feed is automatically generated if one is not found within n
lines.
When you set the length at
length is unlimited.

the

default,

the

logical

page

This qualifier has no effect on how the printer handles form-feed
characters.
A form feed still moves the printer to the top of
the next physical form, such as the perforation in a sheet of
line-printer paper.
This qualifier simply adds ~he requirement
that the printer move to the top of the next physical page if no
form-feed character is encountered within n lines. See the
example using /LENGTH.
4-64

HANDLING FILES

PRINT (Cont.)
/[NO]RESTART
Controls requeuing of your job if it is stopped or aborted
being processed.
If /RESTART is specified,
beginning if it is aborted.
/NORESTART is the default.
job is active,
the job
printer is started.

your

job

starts

again

while

from

the

If the printer is stopped while your
picks up where it left off when the

In neither case are you missing any
/RESTART your job is all in one piece.

your

job,

but

with

If, however, the paper jams in the line printer, the operator
must see that your job is restarted above where the jam began.
/[NO]FLAG_PAGE
Adds flag pages to each file in your print job. With /FLAG PAGE,
the number of flag pages is equal to the number of job flag-pages
that precede the job.
With /NOFLAG PAGE {the default), your job is still preceded by a
job flag page, but the files in the job are printed without any
file flag page, separated only by form feeds.
You can suppress
the job flag page with the /NOJOB PAGE qualifier. Figure 4-2
shows the difference between the job flag page and the file flag
page.
/AFTER:

{dd-mm-yy hh:mm: [ss])
{rnrn/dd/yy hh :mm: [ss])

Blocks the job until after the specified time. Depending on the
print queues at that time, your job may be run immediately, or
later, when its turn comes up in the queue.
The parentheses, hyphens {or slashes), colons, and the space
between the calendar and clock fields are all necessary syntax.
Note that a space is used only between the calendar and clock
fields.
The space is not necessary if either field is omitted.
You can specify the calendar field in either of two formats:
dd-mm-yy

Uses a 1- or 2-digit number for the day,
the first
three letters for the month, and two numbers for the
year.

rnrn/dd/yy

Uses a 1- or 2-digit number for the month,
a 1- or
2-digit number for the day, and two numbers for the
year.
If you leave out the calendar
defaults to the current date.

the

day

yy must be between 77 and 92.
If you leave it
the year defaults to the current year.

out,

4-65

field,

HANDLING FILES

PRINT (Cont.)
hh:mm:ss is the hour, minute, and second.
If you leave out the clock field, the time defaults
to 00:00:00 on the given date. The parameter ss
need not be given. It defaults to 00.
In fact, you
cannot specify ss.
If you do, it is checked for
syntax only. The Queue Manager always takes a few
seconds to start the job.
Specifying a time using /AFTER is equivalent to
issuing a Print command at that time. The job may
still have to wait in its queue to be printed.
/AFTER:TOMORROW
Specifies that you want the command to execute after midnight.
Use this qualifier to queue print jobs for the early morning
hours.
If you have a command file that you run every day,
you
can include PRINT/AFTER:TOMORROW in the command file.
This
qualifier circumvents the problem that it is always after
midnight.
/NOWARNINGS
Suppresses error messages resulting from the command ••
File Qualifiers
These qualifiers are used to override the corresponding command
qualifiers when you have given multiple file specifications as
parameters to the PRINT command.
/COPIES :n
Overrides the /COPIES command
particular file specification.

qualifier

when

attached

Overrides the /[NO]DELETE command qualifier when
particular file specification.

attached

/[NO]DELETE

Examples

$ PRINT ~
File (s)? PASHA.CMD ~
PR! -- Job 305, name "PASHA

", submitted to queue "PRINT "

This example prints the most recent version of PASHA.CMD from the
default device and directory on the line printer. The Queue
Manager returns a message confirming that the job has been
submitted and given an entry number. You can use this entry
also
the
number in QMG commands.
See Chapter
9,
and
RSX-llM/M-PLUS Batch and Queue Operations Manual.
$ PRINT/COPIES:20 ~
File(s)? PASHA.CMD (BITl
PR! -- Job 706, name "PASHA

4-66

", submitted to queue "PRINT "

HANDLING FILES

PRINT (Cont.)
This example prints 20 copies of PASHA.CMD.
They are
end-to-end with no flag page except at the beginning.

printed

$ PRI/COP:20/FLAG PAGE PASHA.CMD ~
PRI -- Job 321, name "PASHA
", submitted to queue "PRINT "
This example prints 20 copies of
page.

PASHA.CMD,

each

with

flag

$ PRIN/COPIES:2 DAVID.TXT, DAN.TXT ~
PRI -- Job 18, name "DAVID
", submitted to queue "PRINT "
This example prints two copies of DAVID.TXT followed by two
copies of DAN.TXT.
It does not print two sets of one copy of
each file.
If you wish to print sets of files,
see the next
example.

$ PRINT/JOB COUNT:2 DAVID.TXT, DAN.TXT ~
PRI -- JOB 311, NAME "DAVID
", submitted to queue "PRINT "
This example prints a set consisting of a copy of DAVID.TXT
followed by a copy of DAN.TXT, and then prints another set of
DAVID.TXT followed by DAN.TXT.
$ PRI/FLAG PASHA.CMD, RAJAH.CMD, SHEIK.CMD ~
PRI -- Job 999, name "PASHA
" submitted to queue "PRINT "

This example prints one copy of each file, each with its own flag
page.

$ PRI/NAME:ARABY/FLAG PASHA.CMD, RAJAH.CMD, SHEIK.CMD f5ffi
PRI -- JOB 805, NAME "ARABY
", submitted to queue "PRINT "
This example prints one copy of each file, each with its own flag
page, and gives the name ARABY to the job as a whole.
The name
ARABY appears in the print queue and at the head of the entire
printed output.

$ PRINT/LENGTH:60 GLADRAG.MAC ~
PRI -- Job 22, name "GLADRAG ", submitted to queue "PRINT "
This example prints a single copy of the file GLADRAG.MAC.
This
is a source program file without form-feed characters in it.
The
user wants to print it on line-printer paper, a physical form 66
lines long.
To avoid printing over the perforations, the user
has specified a logical length of 60 lines.
Each time 60 lines
have been printed, the logical page is complete and the printer
moves to the top of the next physical page.
If the file had form feeds in it, the printer would move to the
top of a physical page each time it encountered a form feed and
each time it printed 60 lines without encountering a form feed.

4-67

HANDLING FILES

PRINT (Cont.)
$ PR1/COPIES:20 MOB.CCR, RIFRAF.COR, RABBLE.COR/COP:l9, PROLE.COR(Bfil)
PRI -- Job 77, name "MOB
", submitted to queue "PRINT "
This example prints 20 copies each of MOB.COR, and RIFRAF.COR, 19
copies of RABBLE.COR, and then 20 copies of PROLE.COR.

$ PRI/DELETE LASER.TST, PHASER.TST, RAZOR.TST/NODELE (Bfil)
11
PRI -- Job 406, name "LASER
,
submitted to queue "PRINT "
This example prints the three files and
from the current UFD.

deletes

the

first

two

Only the versions specified in the PRINT command are deleted,
in
this case, the most recent versions of LASER.TST and PHASER.TST.
$ PRI/AFTER: (4-JUL-85 13:13) CONST.CON (Bfil)

PRI -- Job 809, name "CONST

submitted to queue "PRINT "

This example blocks the job in its queue until the specified date
and time.
The file itself remains in its directory. Deleting
the file from its directory does not take ~t out of the queue,
but does prevent it from being printed.

$ PRI/AFTER: (17:00) GUNGA.DIN IBfil)
11
PRI -- Job 765, name "GUNGA
,
submitted to queue "PRINT "
This example prints the file after 5 P.M.
on the day the command
is entered.
If the command is entered after the specified time,
the file is printed immediately.
Notes
P is the short form of PRINT.
The PRINT command does not accept the percent sign wildcard
(%).
The asterisk wildcard
(*) can only be used to substitute for a
complete part of the file specification and NOT for part of a
file name or file type as some commands do.
For more information on the PRINT command, see the RSX-llM/M-PLUS
Batch and Queue Operations Manual.
This manual also includes a
description of the SHOW QUEUE command, which displays information
about print jobs in queues.
Once your job is in a queue, you can modify some job
with
SET
QUEUE.
See the RSX-llM/M-PLUS Batch
Operations Manual.

attributes
and Queue

The Queue Manager automatically deletes .PMT and .DMP files after
they are printed.
The /LOWERCASE and /UPPERCASE qualifiers have no effect on the
nature of your output.
They do not cause your job to be printed
all uppercase or in lowercase.
Rather,
these qualifiers must
match
the
attributes
given to the printer when it was
initialized. A printer without the lowercase character set can
be
initialized /LOWERCASE and accept print jobs with the
/LOWERCASE qualifier on the PRINT command. This might be done if
4-68

HANDLING FILES

PRINT (Cont.)
a printer with the lowercase character set was temporarily
unavailable.
In most cases, only printers with the lowercase
character set are initialized /LOWERCASE, however.
Despite your setting of the /[NO]RESTART qualifier, your job may
be restarted by commands to the Queue Manager from your system
manager.
See your system manager if you have jobs where
restarting or not restarting may be a problem.
The flag pages and the job pages have different formats for
the
banner text.
The job name page shows the UIC the PRINT command
was issued under on the first line and a 9-character job name
(derived from an explicit job name or the file name of the first
file in the job) on the second line. The flag page shows the
full 9-character file name on the first line and the file type
and version number on the second line. See Figures 4-2 and 4-3.
Entry numbers run from 1 through 999 and are unique. Various QMG
commands permit you to identify your job either by this number or
by job name.
The job name includes your UIC.
See Chapter 9 and
also the RSX-llM/M-PLUS Batch and Queue Operations Manual.

4-69

HANDLING FILES

APPEND
4.4.3

APPEND

APPEND appends to an existing sequential file records from one or more
sequential files.

Format
APPEND[/qualifier[s]]
File(s)? infile[s]
To? outf ile
APPEND[/qualifier[s]] infile[s]

outfile

Command Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARN INGS
/REWIND
/SHARED

Parameters
infile[s]
Specifies the file or files to be appended to
You can use APPEND only on sequential files.

the

output

file.

outf ile
Specifies the file to which the input files are appended.
The output file must be an existing sequential file.
The output
file has the same version number after the APPEND command is
executed as it had before the command was issued.
The input
files appear at the end of the output file in the order they were
specified.
No wildcards are permitted in output file specifications.
There are no qualifiers for the output file specification.
Although the output file must exist, it may be an empty file.

Command Qualifiers
/DATE:dd-mmm-yy
Specifies that you wish the APPEND command to affect
created on the date given.

only

files

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the APPEND command to affect
created on or since the date given.

4-70

HANDLING FILES

APPEND (Cont.)
/THROUGH:dd-mmm-yy
Specifies that you wish the APPEND command to affect
created on or before the date given.

only

files

only

files

only

files

/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the APPEND command to affect
created within that range.
/TODAY
Specifies that you wish the APPEND command to affect
created on the same day the command is being issued.
/EXCLUDE:filespec
Specifies that you do not want the APPEND command to affect
certain files.
The filespec argument to /EXCLUDE can contain
either a single file specification (for example, TEST.DAT;2), or
wildcards in all but one of the file specification fields (for
example, *.DAT;*, TEST.*;*, or *.*;2)
if you want to exclude
multiple files.
However, the version number must be given,
either explicitly or as a wildcard (*).
/NOWARNINGS
Suppress error messages resulting from the command.
/REWIND
Causes the tape to rewind before starting
qualifier is for magnetic tapes only.

the

operation.

This

access

the

file

This example appends copies of all versions of BIRD.DOG in
to the end of the most recent version of JOKER.TXT.

order

/SHARED
Specifies that you want others to be able
while your append operation is under way.
Examples
$ APPEND CBTI)
File(s)? BIRD.DOG;* CBTI)
To? JOKER. TXT CBTI)

$ APPEND *.LST LIST.FIL CBTI)

Appends copies of most recent versions of all files of the type
.LST to LIST.FIL.
Appended files appear in the order they are
listed in the directory.
Notes
APPEND does not delete the input files.
They remain intact.
Copies of the input files are placed at the end ~f the output
file.

4-71

HANDLING FILES

DIFFERENCES
4.4.4

DIFFERENCES

DIFFERENCES compares two ASCII (text) files line by line to determine
if parallel records (lines) are identical, and produces a listing of
the differences between the files, if any.
Format
DIFFERENCES[/qualifier[s]]
Filespecl? infilel
Filespec2? infile2
DIFFERENCES[/qualifier[s]] infilel infile2
Command Qualifiers
/CHANGE BAR [: n]
/IGNORE:(arg[,s])
BLANK LINES
COMMENTS
FORM FEEDS
SPACING
TRAILING BLANKS
/LINES :n
/NONUMBERS
/OUTPUT:filespec
/SLP [:au]
Parameters
infilel
Specifies the first of two files to be compared. The
must be included. The default file type is .MAC.

file

name

The file

name

inf ile2
Specifies the second of two files to be compared.
must be included. The default file type is .MAC
Command Qualifiers
/CHANGE_BAR[:nnn]
Specifies that the output consists of a listing of infile2 with
change bars applied to each line in infile2 that does not have a
corresponding line in infilel. The nnn argument is the number of
the ASCII character to be used for the change bar. The default
is 041, the exclamation point (!). Here are the codes for some
commonly used ASCII characters:

#
$

<
>
?

041
043
044
052
053
074
076
077
074

4-72

HANDLING FILES

DIFFERENCES (Cont.)
/IGNORE:(arg[,s])
BLANK LINES
COMMENTS
FORM FEEDS
SPACING
TRAILING BLANKS
Specifies that you wish certain defaults to be ignored in making
the comparison. Without the /IGNORE qualifier, the comparison is
strictly line-by-line. If you specify only one argument, you do
not need the parentheses.
If you specify more than one argument,
enclose them in parentheses and separate them with commas (,).
The default is to include all these factors in the comparison.
The BLANK LINES argument specifies that blank lines are to be
excluded -from comparison. The default is to include blank lines
in the comparison.
The COMMENTS argument specifies that comments,
that is,
text
preceded by a semicolon (;) not be included in the comparison.
Otherwise, comments are compared like all other text.
The FORM FEEDS argument specifies that lines beginning with a
single form-feed character (CTRL/L) are to be excluded from the
comparison.
The default is to include such lines in the
comparison.
The SPACING argument specifies that any sequence of blank and tab
characters is to be interpreted as a single blank for the
comparison. This argument is useful when comparing source files
that differ only in their spacing. The output listing includes
blanks and tabs as they are found in the input files, but the
blanks and tabs are ignored.
The default is to compare sequences
of blanks and tabs like any other characters.
The TRAILING BLANKS argument specifies that all blanks following
the last nonblank character in the line be ignored in the
comparison. The default is to compare trailing blanks like all
other characters.
If you specify both TRAILING BLANKS and
COMMENTS in your /IGNORE qualifier, any blanks preceding a
semicolon (;) are also ignored.
The DCL DIFFERENCES command does not have quite the same defaults
as CMP, the File Compare Utility, which DIFFERENCES invokes.
Specify /IGNORE: (BLANK LINES,FORM FEEDS)
to duplicate the CMP
defaults for blank lines and form-feeds.
Other CMP defaults need
not be specified.
/LINES :n
Specifies that n lines must be identical before a match
recognized. The default value for n is 3 identical lines.

4-73

HANDLING FILES

DIFFERENCES (Cont.)
/[NO]NUMBERS
Specifies whether or not lines in output file are preceded by
line numbers.
/NONUMBERS specifies that lines in the output file
not be preceded by line numbers.
The standard output listing
automatically includes line numbers. Line numbers start with 1
in increments of one. All lines are numbered, including blanks.
/OUTPUT:filespec
Specifies that the output listing be written to the file named in
the qualifier.
Normally, this output appears on your terminal.
/SLP[:au]
Specifies that the output listing take the form of a SLP indirect
command file.
When you include this qualifier,
the output
listing is an SLP indirect command file that makes infilel
identical to inf ile2.
The optional au argument, preceded by a
colon, is a 1- through 8-character alphanumeric audit trail
symbol.
For more information on the Source Language Input
Program (SLP), see the RSX-llM/M-PLUS Utilities Manual.
Examples
The following examples use several slightly different versions of
the same MACR0-11 source file for comparisons. The full text of
version 1 is printed here. ve.rsion 2 is identical except for
that
one Executive directive is different; version 3 has
additional blank lines inserted. In each instance, the "IDENT"
number matches the version number.
Here is the text of version 1:
.TITLE WRITE PRINT A PREDEFINED MESSAGE ON
.!DENT "01"

THE

USER

TERMINAL

.MCALL ALUN$C, QIOW$C, EXST$C
STRING: .ASCII "This is a simple MACR0-11 program."
LENGTH
.-STRING
CALCULATE THE STRING LENGTH
.EVEN
START:

ALUN$C l,TI,O
; ASSIGN THE LUN TO USE TO THE TERMINAL
QIOW$C IO.WVB,l,l,,,,STRING,LENGTH,40>
PRINT THE STRING
EXST$C EX$SUC
SUCCESSFUL EXIT IN ALL CASES
.END

SETUP THE STARTING ADDRESS

START

In the following examples, a "difference" as defined by the
DIFFERENCES command consists of one or more lines that differ in
the two files being compared.
Each "difference" ends when the
first
matching
line is encountered.
The listing of the
"difference" includes all the nonmatching lines AND the first
matching line.

4-74

HANDLING FILES

DIFFERENCES (Cont.)
$ DIFFERENCES/IGNORE:(BLANK LINES,FORM FEEDS)
Filespecl? TOM.MAC;l IB.rn
Filespec2? TOM.MAC;2 ~

***********wwww***********************************
1)
2
4
6

DB 2 : [ 3 0 3, 5] TOM. MAC ; 1
.!DENT "01"
.MCALL ALUN$C, QIOW$C, EXST$C
STRING: .ASCII "This is a simple MACR0-11 program."

***************
2)

DB 2: [ 3 0 3, 5] TOM. MAC ; 2
.!DENT "02"
.MCALL ALUN$C, QIOW$C, EXST$S
STRING: .ASCII "This is a simple MACR0-11 program."
1 differences found
TI:/-BL/-FF/-CB=TOM.MAC;l,TOM.MAC;2
2
4
6

In this example, the user compared two files that differ only in
one Executive directive -- EXST$S or EXST$C -- and in their
version numbers. The user specified the following:
/IGNORE:(BLANK_LINES,FORM FEEDS)
to reproduce the defaults of CMP, the File Compare utility, which
the DIFFERENCES command invokes.
The listing of differences between the two files starts with the
!DENT numbers on line 2 of the files.
The next line is blank in
both files. Although the line is numbered, it is not printed on
the terminal and is ignored in the comparison.
It would not
change the results if one file had the blank line there and one
did not.
The next listed difference is in the Executive calls on line 4.
Again,
the blank lines are not shown.
The next line of code
listed is the same in both files. This marks the end of a group
of iines that are different in the two files.
The command line reprinted at the bottom of the listing
CMP command line equivalent to the DIFFERENCES command.
$ DIFFERENCES TOM.MAC;l TOM.MAC;2 (Btl)

**************************************************
1)
2

DB 2 : [ 3 0 3, 5] TOM. MAC ; 1
.!DENT "01"

.MCALL

ALUN$C, QIOW$C, EXST$C

***************
2)
2
3
4

DB 2 : [ 3 0 3 , 5 ] TOM • MAC ; 2
.!DENT "02"
.MCALL

ALUN$C, QIOW$C, EXST$S

1 differences found
TI:/BL/FF/-CB=TOM.MAC;l,TOM.MAC;2

4-75

the

HANDLING FILES

DIFFERENCES (Cont.)
This example illustrates the defaults for the
DIFFERENCES
command.
The results are the same, but the blank lines are
printed.
If one file had had more blank lines than the other,
the results would not have been the same. See the examples
comparing version 1 and version 3.
$ DIFFERENCES/CHANGE BAR/IGNORE: (BLANK LINES,FORM FEEDS) TOM.MAC;l TOM.MAC;2 (@'.)
1
.TITLE WRITE PRINT A PREDEFINED MESSAGE ON THE USER TERMINAL
2
.IDENT "02"
4
.MCALL ALUN$C, QIOW$C, EXST$S
6
STRING: .ASCII "This is a simple MACR0-11 program."
7
LENGTH
.-STRING
; CALCULATE THE STRING LENGTH
8
.EVEN
10
START: ALUN$C l,TI,O
; ASSIGN THE LON TO USE THE TERMINAL
11
QIOW$C IO.WVB,l,l,,,,STRING,LENGTH,40>
12
PRINT THE STRING
; SUCCESSFUL EXIT IN ALL CASES
EXST$C EX$SUC
13
15
.END
START
; SETUP THE STARTING ADDRESS
1 differences found
TI:/-BL/-FF/CB/VB::04l=TOM.MAC;l,TOM.MAC;2

This example shows th~ effect of the /CHANGE_BAR qualifier.
The
second file is printed on the terminal with exclamation points
next to the numbers of the changed lines.
$ DIFFERENCES/IGNORE: (BLANK LINES) TOM.MAC;l TOM.MAC;3 (@'.)

**************************************************
1)
2
4

DB2: [303,S]TOM.MAC;l
• !DENT "Ol"
.MCALL ALUN$C, QIOW$C, EXST$C

***************
2)
2
4

DB2: [303,5]TOM.MAC;3
.!DENT "03"
.MCALL ALUN$C, QIOW$C, EXST$C

1 differences found
TI:/-BL/FF/-CB=TOM.MAC;l,TOM.MAC;3

Versions 1 and 3 differ only in their blank lines and version
numbers.
In this example, with /IGNORE: (BLANK LINES), the only
difference is in the !DENT numbers.
The listing of
the
difference ends with the first line that is not different. Blank
lines are numbered but otherwise ignored.

4-76

HANDLING FILES

DIFFERENCES (Cont.)
$DIFFERENCE TOM.MAC;l TOM.MAC;3 tfil.]

**************************************************
1)
2
3

DB2: [303,5]TOM.MAC;l
• !DENT "01"

***************
2)
2
3

DB2: [303, 5] TOM.MAC; 3
• !DENT "03"

**************************************************
1)
7

DB 2 : [ 3 0 3 , 5 ] TOM • MAC ; 1
LENGTH

• -STRING

CALCULATE THE STRING LENGTH

• -STRING

CALCULATE THE STRING LENGTH

***************
2)

DB2: [303,5]TOM.MAC;3
7
8

LENGTH

************************************************** '
1)
DB2: [303, 5] TOM.MAC; 1
11
QIOW$CIO.WVB,l,l,,,,<STRING,LENGTH,40>

***************
2 ) DB 2 : [ 3 0 3, 5 ] TOM. MAC ; 3
12
13
QIOW$CIO.WVB,l,l,,,,<STRING,LENGTH,40>

3 differences found
Tl:/BL/FF/-CB=TOM.MAC;l,TOM.MAC;3

Comparing
the
same
two
files
without
specifying
/IGNORE: (BLANK_LINES)
has
quite
different results.
Three
differences are found.
The first is the differing IDENT numbers.
The other two differences are nothing more than blank lines.
Notes
You can compare any two text files.
They need not be MACR0-11
source files, but most qualifiers to DIFFERENCE are for use with
MACR0-11 files.
The DIFFERENCES command invokes CMP, the
See the RSX-llM/M-PLUS Utilities Manual.

4-77

File

Compare

Utility.

HANDLING FILES

UNLOCK
4.4.5

UNLOCK

UNLOCK unlocks locked files.
Locked files are files that have been
improperly closed because a task aborted or stopped execution while
the file was open. Locked files are identified by an L in the
directory listing.
Format
UNLOCK[/qualifier[s]]
File(s)? filespec[s]l
UNLOCK[/qualifier[s]] filespec[s]
Command Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARNINGS
Parameter
filespec
Identifies the locked file(s)

that you wish to unlock.

Command Qualifiers
/DATE:dd-mmm-yy
Specifies that you wish the UNLOCK command to affect
created on the date given.

only

files

only

files

only

files

only

files

only

files

/SINCE:dd-mmm-yy
Specifies that you wish the UNLOCK command to affect
created on or since the date given.
/THROUGH:dd-mmm-yy
Specifies that you wish the UNLOCK command to affect
created on or before the date given.
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
Specifies that you wish the UNLOCK command to affect
created within that range.
/TODAY
Specifies that you wish the UNLOCK command to affect
created on the same day the command is being issued.

4-78

HANDLING FILES

UNLOCK (Cont.)
/EXCLUDE:filespec
Specifies that you do not want the UNLOCK command to affect
certain files.
The f ilespec argument to /EXCLUDE can contain
either a single file specification (for example, TEST.DAT;2), or
wildcards in all but one of the file specification fields (for
example, *.DAT;*, TEST.*;*, or *.*;2)
if you want to exclude
multiple files.
However,
the version number must be given,
either explicitly or as a wildcard (*).
/NOWARNINGS
Suppresses error messages resulting from the command.
Example

$ Directory TOPEKA.KAN IBD)
Directory DBO: [303,5]
2-MAY-~5
13:13
TOPEKA.KAN;3

32.

25-APR-85

12:29

Total of 32./40. blocks in 1. files
$
$
$ UNLOCK TOPEKA. KAN~ IBD)

$
$
$ DIRECTORY TOPEKA.KAN (RET)
Directory DBO: [303,5]
2-MAY-85 13:14

TOPEKA.KAN;3

32.

25-APR-85

12:29

Total of' 32./40. blocks in 1. files
In this example, the user found a locked file, perhaps through an
error mess~ge stating that the file could not be opened.
The
locked state is indicated by the L in the third column of the
directory listing. After the user issues the UNLOCK command, the
file is no longer locked.
Notes
In many cas~s, a locked file has no contents because the task
that opened the file aborted before writing to the file.
In this
case, you do not need to unlock the file before deleting it.
Another common case of file locking is a data file that has been
opened by some task that aborted or exited without closing the
file.
In this case, you have to unlock the data file before
running the task again.
If the file is written to by the task,
it may have been corrupted.

4.5

SET AND SHOW

You can SET and SHOW your default device and UFO.
You can SET
PROTECTION on any file in your directory or on a volume mounted on
your private (allocated) device.
4-79

HANDLING FILES

SET DEFAULT
4.5.l

SET DEFAULT

SET DEFAULT establishes your default device or directory, or both.
Format
SET DEFAULT [ddnn:] [[g,m]]
Parameters
If you issue SET DEFAULT without parameters, your default device
and
directory return to your login defaults,
if you are
nonprivileged. Privileged users must explicitly reset their
login directory.
ddnn:
Specifies the name of the device you wish to be your default
device.
The device must be a Files-11 device. The device name
can be a logical name, but the SHOW DEFAULT display names the
physical device.
[g ,m]

Specifies the directory you wish to be your default directory.
When you change your directory, the system checks your login UIC
for your privilege.
If you are nonprivileged, you remain
nonprivileged even if your new default directory has a group
number of 10 or less.
If you are privileged, this command changes your login UIC as
well as your default directory, but your privileges remain the
same.
In some cases, however, privileged users may have to reset
their directory to a privileged group number in order to use
privileged commands.
Examples

$ SET DEFAULT DRl: [303,5] IBQl
This example sets DRl: as the default device and [303,5] as the
default directory.
All subsequent commands default to this
device and directory unless you explicitly state otherwise.

$ SHOW DEFAULT ~
DBl: [303,5] TT56:
$SET DEFAULT DB2: [200,200]
$ SHO DEF ~
DB 2 : [ 2 0 0 , 2 0 0 ]
$ SET DEF ~
$ SHO DEF ~
DB 1 : [ 3 0 3 , 5 ]

4-80

HANDLING FILES

SET DEFAULT (Cont.)
This example illustrates the use of the unadorned SET DEFAULT
command.
The user started with the login default device of DBl:
and the directory [303,5], as given in the display from the SHOW
DEFAULT
command.
Then,
the
user
set the defaults to
DB2: [200,200]
and checked the setting with
SHOW
DEFAULT.
Finally, the user issued· SET DEFAULT without specifying any
parameter.
The user's defaults are returned to the login
defaults.
See notes.

$ SET DEF DKl:

$ ASSIGN DKl:

~YO:

The two commands in this example are equivalent. In each case,
When you set the default
the default device becomes DKl:.
device, SET DEFAULT actually assigns SYO: as a logical name for
the device you wisn.
SYO:
is the logical device name that
represents your default device.
Notes
SET DEFAULT is an unusual command in that it has differing
effects depending on the presence or absence of its parameters.
The only way to change your default directory in DCL is through
SET DEFAULT.
When you issue SET DEFAULT including a directory,
DCL directly alters the default directory held in your Unit
Control Block (UCB).
When you change your default device, however, SET DEFAULT
generates the equivalent of an assignment of the logical name
SYO:
to the physical device you name, as shown in the examples.
Conversely, when you issue the command without any parameters,
SET DEFAULT generates the equivalent of a deassignment of the
logical name SYO:, meaning that your default device assignment
returns to your login SYO:, which is whatever device you log in
to, and, for nonprivileged users resets your directory to your
login directory.
Becaue DCL is issuing two commands, it is possible that
succeed while the other fails.

4-81

one

may

HANDLING FILES

SHOW DEFAULT
4.5.2

SHOW DEFAULT

SHOW DEFAULT displays the current default
your terminal.

device

and

directory

/IMAGE:arg
SAVE
RESTORE
Specifies that you want to do a multiple disk-to-disk
restore operation.

backup

If you want to do a backup operation, you must use /IMAGE:SAVE
when you create the backup file that represents the image copy of
the input disk or disks. For example, this qualifier must be
used when you copy a large disk to several small disks, or if you
copy several small disks to a mounted large disk.
If you are doing a restore operation, you must use /IMAGE:RESTORE
if you are restoring from a backup file that represents the image
copy of the original disk.
NOTE
You cannot use the /IMAGE qualifier when backing
up or restoring from one disk or diskette to
another disk or diskette. For one-to-one backup
and
restore operations, use the /INITIALIZE
qualifier.
/NEW_VERSION
Specifies that a new version of the file be created in the event
of conflicts that occur during restore operations and during
backups to a mounted disk when using the /IMAGE:SAVE qualifier.
Compare with /REPLACE.
/MODIFIED:BEFORE:arg
AFTER:arg
Specifies selection of files modified
specified date or time, or both.

before

after

the

The required date/time argument can be in several formats.
You
must specify either a date or a time or both. If you do not
specify a date, the default is today.
If you do not specify a
time, the default is now.
Here are some examples:
/BEFORE:28-MAR-85
/AFTER:l4:00
/BEFORE;(l-APR-85 12:00)
/AFTER:(l-APR-85 12:00)
/BEFORE:4/l/85
/AFTER:(4/l/85 12:30)
5-76

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
Note that if you wish to enter both a date and a time, you must
use the parentheses. These formats are used wherever you specify
a date or a time or both in a BACKUP command.
/[NO]REPLACE
Specifies whether or not files from the input volume should
replace files having identical file specifications on the output
volume.
A conflict occurs when a file on the input volume and a file on
the output volume have identical file specifications.
The
default qualifier /NOREPLACE resolves that conflict by keeping
the file on t.he output volume rather than replacing it with that
on the input volume. A message informs you that the file has not
been superseded. /REPLACE resolves the conflict by deleting the
file on the output volume and replacing it with the file being
restored from the input volume.
Group 2:

Initialization

/INITIALIZE
Specifies that you wish to initialize the output disk before
proceeding with the data transfer.
You must specify this
qualifier if you wish to use any of the other initialization
qualifiers discussed here.
If you do not specify this qualifier,
but specify other initialization qualifiers, you will be asked by
a prompt whether you wish to initialize before proceeding or not.
The default is /NOINITIALIZE.
See Section
qualifiers.

5.9

for

description

INITIALIZE

and

its

/BAD _BLOCKS: arg
AUTOMATIC
MANUAL
OVERRIDE
Enters the locations ,of bad blocks on the
volume
being
initialized.
See the ANALYZE/MEDIA command description for more
information on finding and marking bad blocks.
AUTOMATIC specifies that bad-block information for the volume be
determined automatically from the file BADBLK.SYS, created by the
BAD utility. This is the default.
MANUAL specifies that bad-block information for the volume is
be entered manually.

OVERRIDE applies only to last-track devices.
It makes the disk
appear not to have bad-block information written in the last
track, even if this information is actually present.
/ACCESSED :n
Specifies the default number of File Control Blocks per volume to
be kept in memory by the ACP.
See the description of the
/ACCESSED qualifier to MOUNT (Section 5.7) for more information.

5-77

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
/EXTENSION:n
Specifies the number of blocks by which the file will be extended
when its allotted space is exhausted.
/HEADERS:n
Specifies the number of file headers to be allocated initially in
the index file.
The five system files
(INDEXF.SYS, BITMAP.SYS,
CORIMG.SYS,
BADBLK.SYS, and 000000.DIR) are not included in the value for n.
The default value for n is proportional to the capacity of the
magnetic medium.
See the description of /HEADERS in Section 5.9
for information on the different magnetic media.
/MAXIMUM_FILES:n
Specifies the maximum number of files permitted on the volume.
The value of n includes the five system files.
The value of n
must be less than or equal to the maximum value of n given in the
description of /MAXIMUM FILES in Section 5.7.
The description
also includes the default value of n for each device.
/INDEX:arg
BEGINNING
MIDDLE
END
n

Specifies the location of the index file on the volume.
This
qualifier
forces a specified location for the index file, the
Master File Directory, and the storage allocation file.
This is
usually done to minimize access time.
Four possibilities are available for the argument field:
BEGINNING

The beginning of the volume.
for tapes and DECtapes.

MIDDLE

The middle of the volume.
disks.

END

The end of the volume.

Logical block n.

This is the

default

This is the default for

The default position is the position of the
volume.

file

the

input

/FILE_PROTECTION: (code)
Specifies the default protection for all files created on the
volume being initialized.
See Section 4.1.6 for more information
on file protection.

5-78

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
The default system protection code is as follows:
(SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:R)
The default protection code is the protection code of
volume.

the

input

/WINDOWS:n
Specifies the number of mapping pointers to be allocated for file
windows.
A file window consists of a number of mapping pointers
stored in memory when the file is opened.
The default is the
volume.

number

mapping

pointers

See the discussion of the /WINDOWS qualifier in Section
more information.

the
5.7

input
for

/SAVE_SET:name
Specifies the name of the backup set to be placed on tape,
or diskette.
This name can be up to 12 characters long.

disk,

When you place several backup sets on a tape, disk, or diskette
output volume, each backup set should have a different backup set
name in case you need to restore your backup sets.
If the backup
sets have the same backup set name, only the first backup set
created can be restored.
If you do not use this qualifier, the backup set name for a tape
or an unmounted disk or a diskette defaults to the name of the
volume being backed up.
If you do not use this qualifier when
performing a multivolume backup operation to a mounted output
disk
or
diskette,
the
backup
set
name
defaults
to
[0,0]BACKUP.SYS.
When you use /SAVE SET during a tape restore operation, BACKUP
searches the first tape for the specified backup set name.
If
you do not specify a backup set name during a tape restore
operation, the first backup set on the tape is backed up.
You
can restore sequential backup sets from a tape without having to
rewind the tape between restore operations. Note that BACKUP
does not rewind the first tape in a backup set unless you specify
the /REWIND qualifier.
When you use /SAVE SET during a disk or diskette restore
operation, BACKUP searches the first disk or diskette for each
backup set you specify. Each backup set is then restored in the
order you specified.
Note that all backup sets must begin on the first tape, disk~ or
diskette in your set.
For example, if you have six backup sets
on tape, diskette, or disk, the first five backup sets must begin
and end on the first reel of tape or the first disk or diskette.
The sixth backup set must also begin on the first reel of tape,
or the first disk or diskette, but it may span more than one
tape, disk, or diskette.

5-79

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
Group 3:

Tape Control

/APPEND
Appends new data to a tape that
backup sets.

already

contains

one

If the tape is not positioned at the beginning, /APPEND causes
output to be written where the tape is currently positioned.
If
you want to start writing at logical end-of-tape, you must
specify /APPEND/REWIND, which rewinds the tape and then spaces
forward to the end of the volume.
/DENSITY:arg
800
1600
Specifies the density in bits per inch
(bpi)
for the medium
loaded on the device.
If you are adding your tape drives that
alllow other densities, you must use this qualifier. See Section
5.7 for a list of acceptable densities for DIGITAL devices.
The default is 800 bpi.
/ERROR_LIMIT:n
Specifies the number of nonfatal I/O errors that the
Restore Utility tolerates on tape reads before
execution.

Backup and
terminating

The default value for n is 25.
/LENGTH:n
Specifies the length of the output tape in decimal feet.
You may
want to use this qualifier when you know that the last part of a
tape is defective and must not be used.
You can specify a
shorter length and ensure that you do not write on that part of
the tape.
The default length is the physical length of the output tape.
/REWIND
Rewinds the first tape of a tape set before executing the command
line.
See /APPEND for further information on /REWIND.
/LABEL:TAPE:fileset-ID
Specifies a 6-character ANSI f ileset-ID.
On output operations
this ID is written on the tape. On input operations the ID is
compared with the ID already on the input tape to ensure that you
have mounted the correct tape.

Group 4:

Verification

The following qualifiers allow you to verify the accuracy of data
transfers.

5-80

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
/COMPARE
Compares the data on the output volume to the data on the
input
volume and reports any differences. /COMPARE does not copy any
data. See /VERIFY.
You must compare equivalent volumes.
You can assure that the
volumes are equivalent by including the /COMPARE qualifier in a
command that is otherwise identical to the BACKUP command that
was entered when the output volume was created.
The restriction does
/COMPARE qualifiers.

not

apply

the

/[NO]INITIALIZE

and

/VERIFY
Copies data from the input volume to the output volume,
performs a compare operation, and reports any differences.

Group 5:

then

Display

The following
transferred.

qualifiers

display

information

about

the

data

Displays at your terminal the UFO and file name of
being backed up or restored.
/NOLOG is the default.

each

file

/[NO]LOG

/LIST
Displays at your terminal
specified tape or disk
directory is on the first
set, the directory is
example.

Group 6:

the backup set names or files on the
volume.
In a multivolume tape set, the
tape of a set.
In a multivolume disk
on the first disk of the set.
See the

Disk Processing

The following qualifiers allow you to control the
operating system manages disk data transfer operations.

way

the

Appends new data to a disk or diskette that already contains
or more backup sets.

one

/APPEND

When you are using the /IMAGE qualifier, /APPEND causes BACKUP to
add the new backup set at the end of the last backup set on your
disk or diskette.
You may also append a new backup set to a
tape that already
contains one or more backup sets.
See Group 3, which describes
tape control.
You cannot use the /APPEND qualifier during a backup operation to
a mounted disk or diskette.

5-81

HANDLING DEVICES AND VOLUMES

BACKUP {Cont.)
/DIRECTORY
Directs BACKUP to create directories
(if they do not already
exist) on a mounted output volume, then copy into the directories
the files from the same directory on the input volume.
If you do
not
specify
/DIRECTORY,
BACKUP does not copy the file.
/DIRECTORY is used only with the /NOINITIALIZE qualifier.
/LABEL:INPUT:volumelabel
Specifies the volume label of the input disk.
This is not a
required parameter; if you specify it, however, BACKUP checks the
volume label.
/NOINITIALIZE
Specifies that you do not want to initialize the output disk, as
it already contains a Files-11 structure and is mounted as a
Files-11 volume.
/MOUNTED
Allows you to back up files from a disk that is mounted
Files-11.
Transfers are faster from an unmounted volume.

/[NO]PRESERVE
Specifies whether you want BACKUP to preserve file identifiers
during a transfer using disks or diskettes. The default is
/PRESERVE.
/LABEL:OUTPUT:volumelabel
Specifies a volume label for the output disk.
is the label of the input volume.

The default

label

Examples

$ BACKUP/LABEL:INPUT:RANDOM/SAVE SET:l9JUL85
From? DKO: ~
To: MMO:
~

(fifil)

BAC - Starting tape 1 on MMO:
BAC - End of tape 1 on MMO:
BAC - Completed
This example transfers all files on the RKOS disk labeled RANDOM
to the tape mounted on MMO:.
The backup set name 19JUL85
identifies the data written on the output tape.

$ BACKUP/REWIND/SAVE_SET:l8MAY85/NOINITIALIZE MMO: OMO: ~

5-82

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
This example rewinds the tape on drive MMO:, then locates the
backup set with the name 18MAY85 (there may be more than one
backup set on a tape) and transfers all files in the backup set
to DMO:
which is mounted and has a Files-11 structure. The
/NOINITIALIZE qualifier instructs BACKUP not to initialize DMO:.
$ BACKUP/LIST MMO:

VOLl
VOLl
VOLl

18MAY85
BACKUP2
19APR85

00)

INPUTl
INPUT2
RANDOM

18-MAY-85
19-APR-85
19-APR-85

This example shows a directory of a tape volume. It displays the
tape volume number, VOLl, the names of three volumes, and three
backup sets contained on the tape.
BACKUP can also be used to display the names of the files
in a
given backup set by specifying the backup set name along with the
/LIST qualifier, as in the following example:

$ BACKUP/SAVE SET:l9APR85/LIST MMO: ~
VOLl 19APR85 -RANDOM 19-APR-85 23:37:11
[303,13]
27DECE.LST;l
ASTCRSH.MAC;2
APNDXC.TXT;l
X.MAC;l
X.OBJ;l
X.TSK;l
X.MAP;l
[306,6]
27DECE.CDA;l
RSX11M.STB;3
BAC - Completed on MMO:
Notes
The BACKUP command invokes BRO, the Backup and Restore Utility.
For more information on BRO, see the RSX-llM/M-PLUS Utilities
Manual.
You must specify either /INITIALIZE or /NOINITIALIZE.
If you
specify neither, BACKUP will ask if you wish to initialize the
output device.
BACKUP is not a privileged command, but you should not use it
you are not familiar with BRO.

Error Messages
For many nonfatal errors, BACKUP continues with the
but prints a warning message such as the following:
BAC

*WARNING* APPENDING AT 800 BPI

BAC

*WARNING* BOOT BLOCK IS BAD

5-83

operation,

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
BAC

*WARNING* CANNOT RESTORE CONTIGUOUSLY

BAC

*WARNING* EOT MARKER ERROR

BAC

*WARNING* FILE IDS WILL NOT BE PRESERVED

BAC

*WARNING* NONFATAL QUALIFIER CONFLICTS BEING IGNORED
in

the

BACKUP requests response from the user with messages such as
following:

the

These and other warning messages
RSX-llM/M-PLUS Utilities Manual.
BACKUP also issues purely
following:

are

informational

explained

messages

such

Completed
Starting tape n on ddnn:
These messages require no response.

Please answer Yes or No
Mount another tape
The following are the most common error
Other
error
messages are described
Utilities Manual.

messages from BACKUP.
in the RSX-llM/M-PLUS

BAC -- *FATAL*-Allocation for sys file exceeds volume limit
Explanation: One of the five files created when a volume is
initialized does not fit on the output disk. This message
usually occurs when the output disk is smaller than the input
disk.
User Action: Reinitialize the disk using the /INDEX:BEGINNING
qualifier to BACKUP or INITIALIZE to force the allocation to
start at the beginning of the disk.
You can also use the
/MAXIMUM FILES or /HEADERS qualifiers to reduce the size of
INDEXF.SYS.
BAC -- *FATAL*-Attach failed on ddnn:
Explanation:

BRU could not attach the specified device.

User Action: Check to see if another task has the
attached, or if the device has a volume mounted on it.

device

BAC -- *FATAL*-Device conflict
Explanation: Command specified both a tape and a disk
part of the input or output device specification.

drive

User Action: You can specify either a disk or a tape but not
both.
Check command for proper device names and reenter the
command.

5-84

HANDLING DEVICES AND VOLUMES

BACKUP (Cont.)
BAC -- *FATAL*-Device not in system
Explanation: Command specified a device that is not part of
current system.
User Action:

the

Check command for proper device names and reenter.

BAC -- *FATAL*-Device not supported
Explanation:
disk.

Command specified a device that is not

tape

User Action:

Check command for proper device names and reenter.

BAC -- *FATAL*-Disk read error
Explanation: An unrecoverable read error occurred on the output
disk. This error could be caused by an undetected bad block.
User Action: Run BAD on the disk and then use
/BAD_BLOCKS:AUTOMATIC qualifier.

BACKUP

with

the

BAC -- *FATAL*-Disk write error
Explanation: An unrecoverable write error occurred on the output
disk.
This error could be caused by an undetected bad block.
User Action: Run BAD on the disk and then use
/BAD_BLOCKS:AUTOMATIC qualifier.
BAC-- *FATAL*-End of volume encountered.

BACKUP

with

the

Backup set not found

Explanation:
The backup set specified for a restore operation is
not on the tape volume.
User Action:
operation.

5.11

Mount

the

correct

tape

volume

and

retry

and

display

certain

the

SET AND SHOW

You can display
characteristics.

assignments

set

5-85

device

HANDLING DEVICES AND VOLUMES

SHOW ASSIGNMENTS

5.11.1

SHOW ASSIGNMENTS

SHOW ASSIGNMENTS displays at your terminal all local and login
logical-device assignments.
Privileged users can display assignments
from other terminals and global assignments.
Logical-device assignments are established by ASSIGN, by SET
and by ACNT, the Account File Maintenance Program.

DEFAULT,

Format
SHOW ASSIGNMENTS[/qualifier]
Command Qualifiers
/LOCAL
/GLOBAL
/TERMINAL:ttnn:
/LOGIN
/SYSTEM (synonym for /GLOBAL)
Parameters
None.
Command Qualifiers
/LOCAL
Specifies that local and login logical assignments from your
terminal are to be displayed on your terminal. This is the
default.
/GLOBAL
Specifies that all logical assignments in the system,
global assignments, are to be displayed on TI:.
privileged qualifier.

including
This is a

/TERMINAL:ttnn:
Specifies that local and login assignments from terminal ttnn:
are to be displayed on TI:. This is a privileged qualifier.
/LOGIN
Specifies that local and login logical assignments
terminal are to be displayed on your terminal.
privileged qualifier.
Examples

$ SHOW ~
Function? ASSIGNMENTS
LPO:
DRl:
LOCAL
TPO:
TTll:
LOCAL
SYO:
DBl:
LOGIN

(fi@

TI - TTll:
TI - TTll:
TI - TTll:

5-86

from your
This is a

HANDLING DEVICES AND VOLUMES

SHOW ASSIGNMENTS (Cont.)
This example shows the display for a user who has used ASSIGN to
assign local logical names to a number of devices. These logical
names can be used in place of the device names. The logical name
is displayed on the left and the physical device name (or pseudo
device name) is on the right. The type of assignment -- LOCAL or
LOGIN -- is given, and the TI:. Output to LPO: will actually go
to DRl:.
In this case, the logical name takes the place of a
physical device name. The user cannot direct output to physical
LPO:. Output to TPO: will go to TTll:, which is TI:.
In
addition, the user has the login assignment of SYO: to DBl:.
This means that DBl: is the default device for this user.
$ SHOW ASSIGNMENTS/LOCAL

This example is the equivalent of the previous example.
$ SHOW ASSIGNMENTS/TERMINAL:TT3.7:
MP~:

SYO:

SYO:
SYO:

LOCAL
LOGIN

TI - TT37:
TI - TT37:

This example, which requires a privileged terminal, displays the
logical assignments from terminal TT37:. This user has given the
local logical name MPO:
to the pseudo device, SYO:.
The login
assignment gives the login logical name SYO: to the pseudo
device SYO:. SYO: is the name of the default device.
$ SHOW ASSIGNMENTS/GLOBAL ~
SYO:
DBl:
LOCAL
TI - TT42:
SYO:
DBl:
LOGIN
TI
VT4:
TT4:
SYO:
SYO:
LOGIN
TI
SYO:
SYO:
LOGIN
TI - TT15:

WKO:
INO:
EXO:

LBO:
SYO:
SYO:

GLOBAL
GLOBAL
GLOBAL

This example, which requires a privileged terminal, displays
logical assignments for the entire system.

5-87

all

HANDLING DEVICES AND VOLUMES

SET DEVICE
5.11.2

SET DEVICE

SET DEVICE establishes certain device attributes. With the
of SET DEVICE:TI:/WIDTH:n, this is a privileged command.

exception

Format
SET DEVICE
Device? ddnn:
Attribute? attribute
SET DEVICE:ddnn:/attribute
Device Attributes
/[NO]CHECKPOINT FILE:n
/[NO]LOWERCASE /[NO]PUBLIC
/[NO]SYSTEM
/WIDTH:n
Parameter
DEVICE:ddnn:
Specifies the device for which attributes are to be set.
Note
that, when the one-line form of the command is used, the
parameter is ddnn: preceded by a colon (:) at the end of the
word DEVICE.
Device Attributes
/[NO]CHECKPOINT_FILE:n
Sets aside n
(decimal)
blocks on the specified volume in
[O,O]CORIMG.SYS, the checkpoint file.
The volume must be in
Files-11 format. Only one checkpoint file is permitted on each
volume, but several volumes may have checkpoint files.
The
system searches for checkpoint files in the order they were
created.
If space is not available in the first checkpoint file
created (the primary file), the system searches in the second
file to be created, and so on. Checkpoint files can be allocated
on volumes mounted on private devices.
In general, the system
should have checkpoint space equal to twice the total amount of
memory that all running tasks are using.
The /NOCHECKPOINT FILE attribute makes the checkpoint
file
unavailable.
If the specified file contains checkpointed tasks,
the file is not deactivated until the tasks have returned to
memory, but no new tasks will be checkpointed to the file.
The
checkpoint file is still on the volume but is zero blocks long.

5-88

HANDLING DEVICES AND VOLUMES

SET DEVICE (Cont.)
/[NO]LOWERCASE
The /LOWERCASE attribute sets a terminal or line printer so that
lowercase characters are not converted to uppercase for printing.
The /NOLOWERCASE attribute sets a terminal or line printer so
that
lowercase
characters are converted to uppercase for
printing. This is the default.
Nonprivileged users can use the SET TERMINAL/LOWERCASE command to
set TI:
in this fashion.
/[NO]PUBLIC
/[NO]SYSTEM
The /PUBLIC attribute sets the device as a public device.
This
command also mounts the device.
Public devices are accessible to
all users.
The /NOPUBLIC attribute removes the public status
This is the default setting.

device.

/[NO]SYSTEM is a synonym included for VAX/VMS compatibility.
Section 5.1.3
devices.

contains

discussion

public

and

private

/WIDTH:n
Sets the size of a device's I/O buffer. The .value of n (decimal}
is the length in characters of a line on the device.
For line printers, n must be greater than O and not greater than
255. The line-printer driver discards all characters in a record
(line} that do not fit in the I/O buffer.
For terminals, n must be greater than 2 and not greater than 255.
The terminal driver does not discard excess characters, but puts
them in a record of their own. That is, excess characters appear
one line below the line in which they should appear.
Nonprivileged users can set the width of
this command or SET TERMINAL/WIDTH:n.

their

terminals

using

length}

Examples
$ SET· (8®
Function? DEVICE (BTIJ
Dev ice? LP 1: (BTIJ
Attribute? WIDTH:80(8@

This example sets the I/O buffer size
(line
(decimal} characters on the line printer LPl:.

5-89

HANDLING DEVICES AND VOLUMES

SET DEVICE (Cont.)
$ SET DEVICE:LPl:/LOWERCASE

IB@

This example sets LPl: so that all lowercase characters sent to
it will be printed in lowercase. The command must be issued even
if the printer is controlled by the Queue Manager and has been
initialized lowercase.

$ SET DEVICE:DB3:/CHECKPOINT_FILE:256

IB@

This example creates a checkpoint file of 256 (decimal) blocks on
DB3:.
Notes
SHOW DEVICES displays the attributes set by SET DEVICE.
Error Messages
SET -- Feature not supported
Explanation: The command specified an optional feature that
not incorporated into the system at system generation.
User Action:

was

See your system manager.

SET -- Pseudo device error
Explanation:

Command attempted to set a pseudo device public.

User Action: A pseudo device cannot
command using physical device name.

set

public.

Retype

SET -- Write check not supported
Explanation: Command attempted to
device that does not support it.

enable

write-checking

User Action: Write-checking is not supported on magnetic
RLOls, or RXOls.

5-90

tapes,

HANDLING DEVICES AND VOLUMES

SHOW DEVICES
5.11.3

SHOW DEVICES

SHOW DEVICES displays information about the devices
system.

included

the

Format
SHOW DEVICES[/attribute]

[dd[nn:]]

Device Attributes
/[NO]PUBLIC
/WIDTH
/[NO]SYSTEM (synonym for /PUBLIC)
Paramter
dd[nn]:
Specifies the device or devices of a particular type on the
system for which attributes are to be displayed. dd: is the
2-letter device mnemonic terminated with a colon, which indicates
the type of device controller. The display shows the devices
under that type of controller by model name.
The command SHOW DEVICES dd[nn:]
is useful when you plan to
allocate a drive, as it shows you which drives are available.
Since the same controller may control devices whose disks are not
interchangeable, a generic allocate (ALLOCATE DB) may allocate a
device which cannot accept your disk. See examples.
Device Attributes
If you do not include an attribute, SHOW DEVICES displays a list
of all the devices on the system, including terminals and pseudo
devices.
/[NO]PUBLIC
/[NO]SYSTEM
Displays a list of all devices set (or not set)
PUBLIC.
/[NO]SYSTEM is a synonym included for VAX/VMS compatibility.
/WIDTH
Displays the size of the I/O buffer
(line length)
for a
particular device,
including a terminal.
If no device is
specified, /WIDTH defaults to TI:.
Display Information
The display from SHOW DEVICES can include a number of messages.
ddnn:
A device name in the first column indicates the device or pseudo
device for which information is being displayed. A device name
in the second column indicates a
device
to
which
the
- corresponding device in the first column has been redirected
(logically assigned).

5-91

HANDLING DEVICES AND VOLUMES

SHOW DEVICES (Cont.)
TTnn:
A terminal name in the second column, followed by the word
PRIVATE,
indicates that the device named in the first column has
been allocated by the user logged on to the terminal
in the
second column.
MOUNTED
Indicates that the device is mounted. For privileged users,
message also includes the volume label.

the

BUF=
Indicates the line length (I/O buffer size).
PUBLIC
Indicates that the device has been set public.
If your command was SHOW DEVICES /PUBLIC,
display is PUB=ddnn: or NOPUB=ddnn:

/NOPUBLIC,

the

TYPE=
Indicates the device type by model name, for example, RLOl, RX02.
If you wish to display devices by type, use the 2-letter device
mnemonic.
MARKED FOR DISMOUNT
Indicates that a mounted device has been marked for dismount, but
that the dismount has not been completed, meaning that files are
still open on the volume. The volume can be remounted while it
is marked for dismount.
OFFLINE
Indicates that the system tables contain entries for the device,
but that it is not included in the current configuration.
[directory] LOGGED ON
Indicates that the user identified by [directory]
the terminal.

is logged in on

LOADED
Indicates that a loadable device driver is currently loaded.
UNLOADED
Indicat~s

that a loadable device driver is currently not loaded.

SPOOLED
Indicates that a
Manager.

device

under

5-92

the

control

the

Queue

HANDLING DEVICES AND VOLUMES

SHOW DEVICES (Cont.)
WCHK=
NOWCHK=
Indicates a device with write-checking enabled or not enabled.

Examples
$ SHOW DEVICES (@)
DBO:
PUBLIC MOUNTED LOADED TYPE=RP06
PUBLIC MOUNTED LOADED TYPE=RP06
DBl:
DB2:
PUBLIC LOADED TYPE=RP04
PUBLIC MOUNTED LOADED TYPE=RP06
DB3:
ORO:
VT3: - PRIVATE MOUNTED LOADED TYPE=RM03
DRl:
LOADED TYPE=RM03
DKO:
LOADED
DBO: SPOOLED LOADED
LPO:
LPl:
DBO: SPOOLED LOADED
TTO:
COO:
TTO:
LOADED
TTl:
(7, 40]
(1, l]
- LOGGED ON LOADED
(7,40]
(14,10] - LOGGED ON LOADED
TT2:
TT3:
(303, 5] (303, 5] - LOGGED ON LOADED

TT66:
TT67:
NLO:
VTO:
VTl:

VT2:
VT4:
TIO:
CLO:.
SPO:
LBO:
SYO:

LOADED
LOADED
LOADED
LOADED
LOADED
(1, 1]

[ 1, 1]

(303,5]

- LOGGED ON LOADED
- LOGGED ON LOADED

TTO:
DBO:
DBO:
DBO:

This example shows the display from SHOW DEVICES.
All device~
and pseudo devices are included. For terminals, the first [g,m]
field is the login UIC and the second is the default UFO.
The
only information shown for pseudo devices is the name and the
device to which they are redirected. Privileged users also see
volume labels.
$ SHOW DEVICES DB: IB@
PUBLIC MOUNTED LOADED TYPE=RP06
DBO:
DBl:
PUBLIC MOUNTED LOADED TYPE=RP06
DB2:
PUBLIC LOADED TYPE=RP04
DB3:
PUBLIC MOUNTED LOADED TYPE=RP06
This example displays information about all devices of the type
DB:.
The mnemonic (DBnn:) identifies the device controller and
the model name (RP04) indicates the physical device type.
RP04
disks do not fit RP06 drives, even though the device controller
is the same.·

5-93

HANDLING DEVICES AND VOLUMES

SHOW DEVICES (Cont.)
$ SHOW DEVICES/PUBLIC
PUB=DBO:
PUB=DBl:
PUB=DB2:
PUB=DB3:
PUB=DSO:
PUB=DSl:
PUB=LPO:
PUB=LPl:

This example displays information about all public devices.
Public devices are accessible to all users.
They may be mounted
by any user to assure continued access to the volume mounted on
the device.

$ SHOW DEVICE/WIDTH LPO:
BUF=LPO: 00132.
$ SHOW DEVICE/WIDTH TTll:
BUF=TTll: 00080.

~
~

This example displays the line lengths of a line printer and a
terminal.
The line length is determined by the size of the I/O
buffer, which is established through SET DEVICE:ddnn:WIDTH.

5-94

CHAPTER 6
PROGRAM DEVELOPMENT

6.1

INTRODUCTION

Program development on RSX-llM operating systems
four steps:

accomplished

Creating a program in a supported source
editor

Compiling or assembling the source program to create a binary
object file

Turning the object file into a runnable task image using
Task Builder

Running the program as a task on the system

If you are not familiar with the rudiments of this
Introduction to RSX-llM.

language

process,

using

see

the

To create a source program, you must be
familiar
with
the
file-creation facilities of the system discussed in Chapter 4 of this
manual. You will also need knowledge of one of the programming
languages
available
separately
as software options.
Commands
described in this chapter on program development include commands to
maintain libraries used by programs, and the LINK command, which
controls the operation of the Task Builder.
RSX-llM systems offer extensive program development facilities. These
facilities are introduced in the RSX-llM/M-PLUS Guide to Program
Development. This manual introduces the most importan"tSO!tware tools
used in program development and takes you through the program
development process in considerable detail.

6-1

PROGRAM DEVELOPMENT

LINK
6.2

LINKING THE TASK

The MACR0-11 Relocatable Assembler or high-level language compiler
translates the program you wrote
(the source program file) into a
binary object file. You must then link or task build the object file.
Linking or task building makes a runnable task out of one or more
object files plus object modules from user-written or system library
files.

6.2.1

Introduction to the LINK Command

The LINK command invokes the Task Builder, a system utility that
builds the tasks, formally called task images, that run on the system.
The unadorned LINK command includes a number of defaults that produce
a standard task image file,
having the file type .TSK. The Task
Builder (TKB), however, provides you with many choices that are not
included in the defaults. You can use qualifiers to the LINK command
to perform the following functions:
•

Create TKB output files in addition to the task image file

•

Identify certain kinds of unusual tasks

•

Use hardware options that may not be present on all systems

•

Control the nature of the task build itself

In addition to the LINK command qualifiers,
there are also Task
Builder options that permit you to specify characteristics of the task
you are building.
The defaults provide you with a simple means of building a standard
task.
You specify in the LINK command line and, therefore, pass to
the Task Builder an object file (default file type .OBJ) produced by
the MACR0-11 Relocatable Assembler or one of the high-level language
compilers. The Task Builder then produces a runnable task image.
Invoking the Task Builder is done with a command such as the
following:

$ LINK (Bfil)
File(s)? SAMPLE
$

This command produces a single output , file called SAMPLE.TSK.
The
return of the implicit prompt tells you that the task build completed
successfully.
If, in addition to the task image file, you should want a Task Builder
map file showing the size and location of parts of the task, issue a
command such as the following:

$ LINK/MAP SAMPLE (Bfil)
$
This produces two output files, SAMPLE.TSK and SAMPLE.MAP.
The Task Builder spools SAMPLE.MAP
SAMPLE.MAP 1n your directory.
6-2

the

line

printer

and

puts

PROGRAM DEVELOPMENT

LINK (Cont.)
The following command also requests that a map file be created:

$ LINK SAMPLE.OBJ/MAP
$

This produces two output files, SAMPLE.TSK and SAMPLE.MAP.
The Task
Builder puts SAMPLE.MAP in your directory, but does not spool it to
the line printer.
If you are linking more than one object module to form a task,
the
Task Builder, by default, names the output files after the first task
named in the command line. For example, the following command:
$ LINK MOE, CURLY, LARRY

produces a task image file named MOE.TSK. That is, LINK uses the name
of the first
input file, MOE, as the name of the task unless you
change the name of the task.
Use the /TASK qualifier to change the
name of the task image file.
For instance, the following command:

$ LINK/TASK:SHEMP MOE, CURLY, LARRY IB@
$

produces a task image file named SHEMP.TSK.
command:

Or,

use

the

following

$ LINK MOE, CURLY/TASK, LARRY IB@
$

to produce a task image file named CURLY.TSK.
Note, however, that the following LINK command:
$ LINK/MAP MOE, CURLY/TASK,
$

LARRY IB@

produces a task image file named CURLY.TSK
MOE.MAP because MOE is the first input file.
form:

and a map file named
If you use the following

$ LINK/MAP:SAM MOE,CURLY,LARRY IB@
the map file is named SAM instead of MOE.
If, in addition, you want the task build to abort after
Builder finds three errors, issue a command such as this:

the

Task

$ LINK/MAP/ERROR LIMIT:3 SPARKY IB@
$
As before, this produces two output files,
the task image named
SPARKY.TSK and the map named SPARKY.MAP.
In addition, if the Task
Builder finds three errors, it sends a message to your terminal and
aborts the task build.

6-3

PROGRAM DEVELOPMENT

LINK (Cont.)
Finally, there are Task Builder options.
If you specify the /OPTION
qualifier in your LINK command, LINK prompts you for further input.
For example:

$ LINK/MAP/OPTIONS BIGJON filIJ
Option? UNITS=7 fil]
Option?
(8D)
$
The UNITS option specifies the number of I/O units for the task.
There are more than two dozen options you can specify. They are
listed in Table 6-1.
If you want to specify options, there are three ways of doing so.
must first
include the /OPTION qualifier in your LINK command.
will be prompted Option? Then you can do the following:

You
You

Specify options on separate lines.
Simply enter an option
with its arguments and press RETURN.
You will be prompted
Option? until you terminate the prompt with just a RETURN.

Specify options in a separate file.
When prompted by
Option?, simply name that file with a preceding at sign (@)
and then press RETURN.

Specify options in a separate file and name that file as an
argument to the /OPTIONS qualifier.
Note, however, that you
will not be prompted for options.

Here are three examples.
$ LINK/MAP /OPTIONS BIGJON

filIJ

Option? UNITS=7 filil
Option? ASG=SY0:6:7 filil
Option? fil]
$
or
$ LINK/MAP/OPTIONS BIGJON fil]
Option? @SPARKY .CMD fil]
Opt i on? fil]
$

$ LINK.MAP/OPTIONS:@SPARKY.CMD BIGJON filIJ
The LINK command and its qualifiers are all DCL commands, and the
format is DCL format. The Task Builder, however, does not recognize
OCL format.
It recognizes only Task Builder format.
The translation
from DCL format to TKB format is performed by DCL.
Issuing the LINK command to DCL initiates the following process:
1.

DCL reads the command line and
format.

DCL translates the command line into correct TKB format.

6-4

checks

for

correct

DCL

PROGRAM DEVELOPMENT

LINK (Cont.)

DCL places the TKB-f ormat command in a TKB indirect command
file and passes the indirect command file to the Task
Builder.

The Task Builder builds the task as directed and creates
requested output files.

all

The Task Builder returns control to DCL and DCL
TKB indirect command file.

the

deletes

If you are building standard tasks using the defaults and following
the examples given in the command description (Section 6.2.2), this
process will serve you well.
However, you will have to refer to the RSX-llM/M-PLUS and Micro/RSX
Task Builder Manual for information on how the Task Builder responds
to your LINK command. The Task Builder manual explains all the output
files produced by TKB and how TKB interprets your LINK command. All
the options are explained in the manual, all the terms used in the TKB
environment
are
defined,
and,
in general,
it elucidates the
capabilities of this complex and flexible software tool.
The description of the LINK command in this manual is not intended to
teach you how to use the Task Builder, but only to teach you how to
use the LINK command. To learn to use the Task Builder, you must go
to the Task Builder manual.
Because TKB format and DCL format are different, understanding how the
DCL commands work with the Task Builder commands may be difficult at
first. The TKB translation of your LINK command is available to you
in two forms.
First, you can use the SET DEBUG command (Section
1.2.15), which echoes on your terminal the translation of any DCL
command.
Second, you can use the /SAVE qualifier to LINK. The /SAVE
qualifier preserves the indirect command file created by DCL to be
passed to the Task Builder. This file is named ATLNK.TMP. This file
is also useful if you wish to repeat a particular task build. See the
discussion of /SAVE.
The following description should help you switch from
TKB format.

DCL

format

In TKB format, you name any output files you want produced, separated
by commas, to the left of an equal sign (=). The order you name them
determines which output files you receive.
The Task Builder can
produce up to three kinds of output files.
See the following
examples:
The following DCL command:
$ LINK SAMPLE .OBJ (@)

produces the following command in
command file:

TKB

format

the

TKB

indirect

TKB>SAMPLE. TSK=SAMPLE. OBJ (@)
In this first example, the Task Builder takes SAMPLE.OBJ as its input
file and produces as its only output file the task image SAMPLE.TSK.
The task image file takes the first position in the list of TKB output
files to the left of the equal sign (=).
6-5

PROGRAM DEVELOPMENT

LINK (Cont.)
The following DCL command:

$ LINK/MAP SAMPLE.OBJ

produces the following command in TKB format:
TKB>SAMPLE.TSK,SAMPLE.MAP=SAMPLE.OBJ

In this second example, the Task Builder takes SAMPLE.OBJ as its input
file and produces two output files, SAMPLE.TSK and SAMPLE.MAP.
The
map file takes the second position in the list of TKB output files to
the left of the equal sign.
The following DCL command:
~

$ LINK/MAP/SYMBOL_TABLE SAMPLE.OBJ

produces the following command in TKB format:
TKB>SAMPLE.TSK,SAMPLE.MAP,SAMPLE.STB=SAMPLE.OBJ

In this third example, the Task Builder takes SAMPLE.OBJ as its input
file and produces three output files, SAMPLE.TSK, SAMPLE.MAP, and
SAMPLE.STB. The symbol definition file takes the third position in
the list of TKB output files to the left of the equal sign.
you alter the output file by adding
switches
In TKB format,
(consisting of a slash and two letters) to each of these output file
specifications.
For instance, the following DCL command:

$ LINK/CODE:FIS SAMPLE.OBJ IB"rn
produces the following command in TKB format:
TKB>SAMPLE. TSK/FP=SAMPLE. OBJ

In each case, the Task Builder builds a task that
Point Processor, which is optional hardware.
Qualifiers can also be used on map files.

$ LINK/CROSS_REFERENCE SAMPLE.OBJ

uses

the

Floating

The following DCL command:

produces the following command in TKB format:
TKB>SAMPLE.TSK,SAMPLE.MAP/-SP/CR=SAMPLE.OBJ

In this case, the Task Builder map includes a listing of symbol
cross-references in the program. DCL does not require you to use the
/MAP qualifier if you use another qualifier, such as /CROSS REFERENCE,
that implies that you want a map file.
In the description of the LINK command that follows,
qualifier is identified with its equivalent in TKB format.

6-6

each

DCL

PROGRAM DEVELOPMENT

LINK (Cont.)
You can invoke the Task Builder from DCL in four ways:
1.

Issuing the LINK command with DCL qualifiers

Invoking a DCL indirect command file including a LINK
with DCL qualifiers, such as DCL>@LINKFILE

command

Issuing the LINK command and calling a
file, such as DCL>LINK @TKBFILE

TKB

indirect

command

Running the
commands

$TKB

and

Task

Builder

with

RUN

issuing

TKB

The first two methods of invoking the Task Builder require the LINK
command and DCL format.
The latter two methods require commands in
TKB format.

6.2.2

LINK

LINK invokes the Task Builder, which links object modules and routines
from user and system libraries to form an executable task.
Format
LINK[/qualifier[s]] filespec[/parameter
qualifier[s]] [,filespec[,s] 1
Command Qualifiers
/ANCILLARY PROCESSOR[:n]
/[NO]CHECKPOINT:arg
SYSTEM
TASK
/CODE: (arg [, s])
EAE
[NO]FPP
PIC
POSITION INDEPENDENT
/COMPATIBLE
/CROSS REFERENCE
/DEBUG1:filespec]
/[NO]EXECUTABLE[:filespec]
/ERROR LIMIT:n
/FAST /FULL SEARCH
/[NO]HEADER
/[NO] IO PAGE
/LONG /MAP [: f ilespec]
/[NO]MEMORY MANAGEMENT[:n]
/OPTIONS[:optionsspec]
/OVERLAY DESCRIPTION
/POSTMORTEM
/[NO] PRINT

6-7

PROGRAM DEVELOPMENT

LINK (Cont.)
/PRIVILEGED [: n]
/[NO]RECEIVE
/[NO]RESIDENT OVERLAYS
/SAVE
/[NO]SEGREGATE
/SEQUENTIAL
/SHAREABLE[:arg]
COMMON
LIBRARY
/SLAVE
/SLOW
/SYMBOL TABLE[:filespec]
/[NO]SYSTEM LIBRARY DISPLAY
/[NO]TASK[:filespec)
/TKB
/TRACE
I [NO]WARNINGS
I [NO]WIDE
Parameter
filespec[s]
Specifies the file or files to be linked. The default file type
is .OBJ for object modules and .OLB for object module libraries.
You can have any number of object modules as input files,
separated by commas. These can be specified in any order.
If,
however, one or more input files must reference an object library
(.OLB)
file,
the .OLB file must be entered in the list of input
files directly after the files that reference it.
Parameter Qualifiers
/[NO]CONCATENATE
/DEFAULT LIBRARY
/[NO] GLOBALS
/LIBRARY
/INCLUDE: (module! [: ••• :modulen] )
/OVERLAY DESCRIPTION
/SELECTIVE_SEARCH
Command Qualifiers
/ANCILLARY_PROCESSOR[:n]
Identifies
which is
relocation
default is

the task as an Ancillary Control Processor
(ACP),
a privileged task. The parameter n specifies the base
register. Acceptable values are 0, 4, or 5.
The
5.

In TKB format,
specification.

apply

the

/AC:n

6-8

switch

the

.TSK

file

PROGRAM DEVELOPMENT

LINK (Cont.)
/[NO]CHECKPOINT:arg
SYSTEM
TASK
Specifies that the task is to be
(or
is
not
to
be)
checkpointable.
Checkpointability of tasks is an important part
of the operating system's ability to share resources.
When a
higher
priority
task
seeks
access to system memory, a
checkpointable task of lower priority is checkpointed, or rolled
out to the disk to be stored in its current state until the
higher priority task exits, whereupon the lower priority task
returns and takes up where it left off.
If you do not use the /CHECKPOINT qualifier, your task is built
noncheckpointable.
The
default
is
/NOCHECKPOINT.
A
noncheckpointable task cannot be dislodged by a task of higher
priority.
Therefore,
you should always build your tasks
checkpointable unless you have some important reason for not
doing so.
You can specify how the checkpointing of the task is handled
through the arguments to the /CHECKPOINT qualifier. Your task
can be checkpointable to the system checkpoint file with the
SYSTEM
option.
This is the default.
LINK/CHECKPOINT and
LINK/CHECKPOINT:SYSTEM are equivalent commands.
Tasks built with system checkpointing cannot be checkpointed if
the system checkpoint file is full.
(The size of this file is
set with the SET DEVICE command.)
You can also reserve checkpoint space for the task as part of its
own task image file by using LINK/CHECKPOINT:TASK. Such tasks
are always checkpointable.
(If there is no system checkpoint
file, you can run only one copy of such tasks.)
It should be apparent that the checkpointability of a task has an
impact on the efficient operation of the entire system as well as
on the task itself.
If the task is built noncheckpointable,
it
can block more important tasks from running.
If it is built with
task checkpointability, mass-storage space is reserved that may
never be used.
If it is built with system checkpointability,
there may be no room for it in the system checkpoint file.
Check with your system manager for advice on
selection among these checkpointing qualifiers.

the

preferred

In TKB format, for /CHECKPOINT:SYSTEM, apply the /CP switch to
the task image file. For /CHECKPOINT:TASK, apply the /AL switch
to the task image file. For /NOCHECKPOINT, apply the /-CP switch
to the task image file.
/CODE: (arg [, s])
EAE
[NO]FPP
PIC
POSITION INDEPENDENT
Specifies that the code for the task relies on certain hardware
elements or employs certain techniques. See the RSX-llM/M-PLUS
and Micro/RSX Task Builder Manual for more information.

6-9

PROGRAM DEVELOPMENT

LINK (Cont.)
The EAE argument specifies that the task uses the Extended
Arithmetic Element.
This hardware is optional and may not be
part of your system.
In TKB format, apply the /EA switch to the
.TSK file specification.
The FPP argument specifies that the task uses the Floating Point
Processor.
This hardware is optional and may not be part of your
system. The NOFPP argument is the default.
In TKB format, apply
the /FP switch to the .TSK file specification.
The PIC and POSITION INDEPENDENT arguments are identical and
specify that the resident common or library being built is
position-independent.
In TKB format, apply the /PI switch to the
.TSK or .STB file specification.
If you want to use more than one
parentheses, separated by commas.

argument,

enclose

them

/COMPATIBLE
Specifies that the task be built in compatibility mode.
This
means that memory-resident overlay segments are aligned on
256-word boundaries for compatibility with other implementations
of the mapping directives.
Without this qualifier, overlay
segments are aligned on 32-word boundaries.
In TKB format,
specification.

apply

the

/CM

switch

the

.TSK

file

/CROSS_REFERENCE
Specifies that a listing of symbol cross-references
appended to the Task Builder map file.

If you include this qualifier, LINK automatically includes the
/MAP qualifier as well.
You do not need to specify the /MAP
qualifier unless you want to supply a name for the map file.
If
you supply a name, the map file appears in your current UFD but
is not spooled to the line printer.
In TKB format,
specification.

apply

the

/CR

switch

the

.MAP

file

/DEBUG[:filespec]
Specifies the inclusion of a debugging aid in the task image.
A
debugging aid permits you to interrupt the running of a task and
inspect registers and other memory locations at various stages.
If
you
give
no
file
specification,
the
default
is
LBO: [l,l]ODT.OBJ, which is ODT, the On-Line Debugging Tool, a
DIGITAL-supplied utility.
ODT is incorporated in the task you
are building. ODT can be used only on tasks written in the
MACR0-11 Assembly Language.
See the RSX-llM/M-PLUS and Micro/RSX
Debugging Reference Manual for further information. ~If you have a user-written debugger, name the file it is in when
you use this qualifier. This file should be an object module.

6-10

PROGRAM DEVELOPMENT

LINK {Cont.)
In TKB format, apply the /DA switch to
the
.TSK
file
specification if you wish to use ODT.
If you want to use a
user-written debugger, apply the /DA switch to the input file
specification naming the debugger.
/ERROR_LIMIT:n
Directs the Task Builder to abort LINK after n diagnostics errors
have been produced.
In TKB format,
specification.

apply

the

/XT:n

switch

the

.TSK

file

/[NO]EXECUTABLE[:taskname]
The /EXECUTABLE qualifier is a synonym for the /TASK qualifier.
See the /TASK qualfifier discussion for more information.
/FAST
Specifies that the Fast Task Builder be used to build the task.
The Fast Task Builder is considerably faster than the default
Task Builder.
Several restrictions apply to tasks to be built by the Fast
Builder:

Task

• Tasks may not be overlaid.
• Tasks may not be privileged.

• Tasks may not link to cluster libraries.
• Tasks may not link to resident libraries.
• Tasks may not use FORTRAN virtual arrays.
• The Task Builder cannot produce a .STB output file.
• The Task Builder cannot create resident libraries.
•

The LINK command is limited to the following qualifiers:
/MAP, /WIDE
/[NO]CHECKPOINT:SYSTEM
/[NO]MEMORY_MANAGEMENT
/CODE:EAE
/CODE: [NO]FPP
/DEBUG[:filespec]
/LIBRARY

6-11

PROGRAM DEVELOPMENT

LINK (Cont.)
•

The Task Builder is limited to the following options:
ACTFIL
ASG
COMMON
EXTSCT
LIBR
MAXBUF
RE SC OM
RESLIB
STACK
TASK
UNITS

In addition, the map format is nonstandard and undocumented.
You can also invoke the Fast Task Builder from DCL with the
command RUN $FTB. You must follow TKB format if you run the Fast
Task Builder in this fashion.
See the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual for more
details.
/FULL_SEARCH
Specifies that when processing modules from the default object
module library, the Task Builder should search all co tree
(overlay) segments for matching definitions or references.
Without this qualifier, unintended global references between
co-tree overlay segments are eliminated. Definitions of global
symbols from the default library are restricted in scope to
references in the main root and the current tree.
In TKB format,
specification.

apply

the

/FU

switch

the

.TSK

file

/LONG
Specifies that the map file produced by the Task Builder include
additional file information on modules used in the task build.
The long map does not include file information on modules from
the system library.
If you include this qualifier, LINK automatically includes the
/MAP qualifier as well. You need not include the /MAP qualifier

6-12

PROGRAM DEVELOPMENT

LINK (Cont.)
unless you want to supply a name for the map file.
If you supply
a name,
the map file appears in your current UFO but is not
printed on the line printer.
In TKB format,
specification.

apply

the

/-SH

switch

the

.MAP

file

/MAP [: f ilespec]
Specifies that you want a memory allocation, or map,
file
produced.
If you use /MAP as a command qualifier, without a file
specification .argument, the map appears in your UFO with a file
name derived from the name of the first input file named in the
command line and a file type of .MAP. The map is also spooled to
the line printer.
If you use /MAP with a file specification argument, either as a
command qualifier or a file specification qualifier, the map
appears in your UFO with a file name you have given. The map is
not spooled to the line printer.
If you use /MAP as a file specification qualifier, without a file
specification argument,
the map appears in your UFO with a file
name derived from the name of the .OBJ or .OLB file to which the
qualifier was attached.
The map is not spooled to the line
printer.
The following qualifiers automatically direct the Task Builder to
produce a map with special characteristics:
/CROSS REFERENCE
/LONG /SYSTEM LIBRARY DISPLAY
/WIDE

You do not need the /MAP qualifier with these qualifiers unless
you want to add a file specification argument to /MAP.
These
other map-related qualifiers can be used as either command or
file specification qualifiers, but they have no effect on file
names.
In TKB format, the /MAP qualifier corresponds to the second
position in the list of TKB output files and has the default file
type .MAP.
/[NO]HEADER
If you are building a shared region or a driver,
specify this qualifier.
The default is /HEADER.

you

In TKB format, apply the /-HD switch to either the .TSK
file specification. See /SHAREABLE.

6-13

should
or

.STB

PROGRAM DEVELOPMENT

LINK (Cont.)
/[NO]IO_PAGE
/NOIO PAGE indicates to the Task Builder that the task is over
12K and purposely does not map to the I/O page. This qualifier
is for building privileged tasks only. The default is /IO_PAGE.
/[NO]MEMORY_MANAGEMENT[:n]
Specifies that the task is being built for a system with
(or
without)
memory
management
hardware.
Use
the
/NOMEMORY MANAGEMENT qualifier when you are building a task on a
system with memory management to be run on an RSX-llM (or
RSX-llS)
system without the memory management hardware.
n
specifies the highest physical address of a task on the target
system and can be 28 (the default) or 30.
The default is /MEMORY_MANAGEMENT.
In TKB format,
specification.

apply

the

/-MM

switch

the

.TSK

file

/OPTION[:optionsspec]
Specifies one or more Task Builder options.
Use this qualifier
if you need to use any of the Task Builder options.
Information
on these options is summarized in Table 6-1. See Section 6.2.1
for information on using this qualifier. For full information,
or options, see the RSX-llM/M-PLUS and Micro/RSX Task Builder
Manual.
You can supply options for this qualifier in two ways:
you can
supply the file specification of a file containing the options,
or you can specify the options themselves.
If you do not include
a file specification with this qualifier, you are prompted for
options.
If you want to enter multiple options, you must use a
comma after each option listed.
If you want to list multiple
options on individual lines, you must end each line with a comma.
If you include a file specification with this qualifier,
this
file should contain only the option names, comments, and the
arguments associated with the options, as shown:
UNITS=8
ASG=TTO: 7: 8
; COMMENTS, PRECEDED BY SEMICOLON, ALLOWED
PAR=KROBAR:50000:40000
This file should not include anything but the option statements
and comments preceded by the semicolon (;). Comments preceded by
the exclamation point (!) are not accepted in this instance.
Do
not put any slashes in this file.
Note that the ABORT option is the only means of preventing a task
build once you have begun issuing commands to the Task Builder.
A CTRL/Z simply directs the Task Builder to begin the task build
based on whatever instructions you have issued up to that point.
Thus, if you want to be sure of being able to stop a task build
in this way, you must include the /OPTIONS qualifier in the LINK

6-14

PROGRAM DEVELOPMENT

LINK (Cont.)
command line.
This assures the availability of the ABORT option.
If you are typing the command line and make a mistake, specify
the /OPTIONS qualifier, press RETURN,
and enter the ABORT=O
option. Then press RETURN and the task build aborts.
/OVERLAY_DESCRIPTION
Specifies that the input file is an overlay description file
(type .ODL)
that controls the linking of the task.
No other
input file can be specified if you use this qualifier. The .ODL
file specifies input files to LINK.
/OVERLAY DESCRIPTION can be
either a command qualifier or a file specification qualifier.
In TKB format, use the .ODL file as the only input file to the
right of the equal sign (=) with the /MP switch applied to the
.ODL file specification.
/POSTMORTEM
Requests a Postmortem Dump should the task be
terminated
abnormally.
See the RSX-llM/M-PLUS and Micro/RSX Task Builder
Manual for information on Postmortem Dumps.
In TKB format,
specification.

apply

the

/PM

switch

the

.TSK

file

/[NO]PRINT
Causes the map file to print on your printer.
The /PRINT
qualifier is the default operation.
If you do not want a printed
listing of the map file, use the /NOPRINT qualifier.
/PRIVILEGED [: n]
Indicates that task is privileged. The argument n specifies
base relocation register.
Acceptable values are O, 4, or 5.
default is 5.

the
The

In TKB format,
specification.

file

apply

the

/PR

switch

the

.TSK

/[NO]RECEIVE
Indicates that the task may (or may not)
receive messages by
means of the Executive directive SEND. /RECEIVE is the default.
In TKB format,
specification.

apply

the

/SE

switch

the

.TSK

file

/[NO]RESIDENT_OVERLAY
Enables (or disables) recognition of the memory-resident overlay
operator
{!)
in an overlay description file.
The qualifier is
used with the /OVERLAY DESCRIPTION qualifier when the task has
memory-resident overlays. The default is /RESIDENT_OVERLAY.
In TKB format,
specification.

apply

the

/RO

6-15

switch

the

.TSK

file

PROGRAM DEVELOPMENT

LINK (Cont.)
Table 6-1
Task Builder Options
Description and
Language Key 1

Format and Defaults2

Control
Direct TKB to terminate
build (M,H)

ABORT=O
Number used for format only.
number will do.

Any

Identification
Declare task name (M,H)

TASK=one through six alphanumeric
characters
TASK=f irst six characters of task
image file name

Set task's User Identification Code (M,H)

UIC=[g,m]
UIC=terminal UIC

Declare task's priority
(M ,H)

PRI=decimal integer 1-250
PRI=set by INSTALL; 50, for
nonprivileged users

Declare task's partition
name and size (M,H)

PAR=parname[:base:length]
PAR=GEN

Declare number of open
active files (H)

ACTFIL=decimal integer
ACTFIL=4

Declare extension to
FORTRAN record buffer (H)

MAXBUF=decimal integer for record
buffer size in bytes
(larger than default)
MAXBUF=l32.

1. Language key:
M - Option is of interest to MACR0-11 programmers.
H - Option is of interest to programmers
using
languages.

high-level

2. The first entry in the format and default column gives the
format, the second entry gives the default, if any.
This chart is
only a reminder of the options, their formats, and their defaults.
You must read the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual
for full information on these options.

(continued on next page)

6-16

PROGRAM DEVELOPMENT

LINK (Cont.)
Table 6-1 (Cont.)
Task Builder Options
Description and
Language Key

Format and Defaults

Identification (Cont.)
Declare extension of
buffer used for processing format strings (H)

FMTBUF=decimal integer for length
of format buffer
(larger than default)
FMTBUF=l32.

Declare extension of
program section (M,H)

EXTSCT=psectname:extension
No default

Declare extension of
task's portion of memory;
extends D-space of rand D-space tasks
(M,H)

EXTTSK=decimal integer for increase
in task memory allocation (in
words)
Default from PAR option

Declare virtual base
address and size of
virtual program section (H)

VSECT=psectname:base:window[:length]
No default

Declare number of additional window blocks
needed by task (M,H)

WNDWS=l-7
WNDWS=O

Declare size of stack
(M,H)

STACK=decimal integer for number of
words needed for stack
STACK=256.

Sharing Storage
Declare intention to
access system-owned
common block for
data in memory; if
used with I- and
D-space tasks, common
mapped with D-space
APRs only (M,H)

COMMON=name:access-code[:apr]
No default

Declare intention to
access system-owned
resident library for
code; if used with
I- and D-space tasks,
library mapped with
I- and D-space APRs

LIBR=name:access-code[:apr]
No default

(M, H)

(continued on next page)

6-17

PROGRAM DEVELOPMENT

LINK (Cont.)
Table 6-1 (Cont.)
Task Builder Options
Description and
Language Key

Format and Defaults
Sharing Storage (Cont.)

Declare intention to
access user-owned common;
if used with I- and
D-space tasks, common
mapped with D-space APRs
only (M,H)

RESCOM=filespec/access-code[:apr]
Standard defaults on filespec

Declare intention to
access user-owned library;
if used with I- and
D-space tasks, library
mapped with I- and
D-space APRs (M,H)

RESLIB=filespec/access-code[:apr]
Standard defaults on f ilespec

Allow task to dynamicaliy
map memory-resident
shared regions at
run time. One task
address window maps
the libraries into
the same span of virtual
address space. (M,H)

CLSTR=libraryl,library2, ••• libraryn:switch: [apr]
library! is default library
switch can be RW: or RO:
apr is starting APR
No default

Device
Declare number of I/O
(logical) units (M,H)

UNITS=decimal integer 0-250
UNITS=6

Declare logical device
assignment to units (M,H)

ASG=ddnn:unit-num:unit-num •
ASG=SY0:1:2:3:4,TI0:5,CL0:6
Alterations

Declare definition of
global symbol (M)

GBLDEF:symbol-name:symbol-value
No default

Declare global symbol
reference (M)

GBLREF=symbol-name
No default

Declare series of patch
values; patches I-space
of I- and D-space
tasks (M)

ABSPAT=seg-name:address:val-1
(up to 8)
No default

(continued on next page)

6-18

PROGRAM DEVELOPMENT

LINK (Cont.)
Table 6-1 (Cont.)
Task Builder Options
Description and
Language Key

Format and Defaults
Alterations (Cont.)

Declares series of patch
values; patches D-space
of I- and D-space tasks

DSPPAT=seg-name:address:val-1
(up to 8)
No default

(M)

Declare series of patch
values relative to global
symbol (M)

GBLPAT=seg-name:sym-name[+/-offset] :val-1
(up to 8)
No default

Exclude the specified
symbols from the symbol
definition file of a
supervisor mode library

GBLXCL=syml:sym2: ••• :symn
No default

(M)

Declare address and size
of ODT SST vector (M)

ODTV=symbol-name:vector-length
No default

Declare size of task SST
vector (M)

TSKV=symbol-name:vector-length
No default

Include specified symbols
in .STB file (M,H)

GLBINC=symbol-name,symbol-name, ••• ,symbol-name
No default

/SAVE
Specifies that DCL retains the indirect command file created by
DCL to pass your LINK command to TKB. See Section 6.2.1 for a
description of DCL's handling of the LINK command.
If you
include /SAVE in your LINK command line, a file named ATLNK.TMP
appears in your directory after the task build completes.
Because this file always has the same name, you should give it a
name related to the task it builds, such as SHEMPBLD.CMD.
Then
you can issue a command in the following form:
$ LINK @SHEMPBLD (Bill

and duplicate the task build that originally produced the command
file.
This file is also useful for comparing LINK command syntax with
TKB syntax because it includes the full translation of the LINK
command into TKB format.

6-19

PROGRAM DEVELOPMENT

LINK (Cont.)
/[NO]SEGREGATE
Causes the Task Builder to order program sections alphabetically
by name within access code
(RO followed by RW).
If you also
specify /SEQUENTIAL, TKB orders program sections in their input
order by access code.
/NOSEGREGATE is the default. TKB interleaves RO and RW program
sections.
When combined with /SEQUENTIAL, /NOSEGREGATE results
in a task with program sections allocated in input order with its
RW and RO sections interleaved. If you use /NOSEQUENTIAL and
/NOSEGREGATE together, which is the default for both, TKB orders
program
sections
alphabetically
with RW and RO sections
interleaved.
In TKB format,
specification.

use

the

/[-]SG

switch

the

.TSK

file

/SEQUENTIAL
Directs Task Builder to construct a task image from program
sections in the order in which they appear. Normally, the Task
Builder finds all program sections referenced in all modules in
an overlay segment and then builds the task with those program
sections in alphabetical order. Do not use this qualifier to
build tasks that rely on alphabetical allocation of program
sections, such as FORTRAN I/O handling modules and FCS modules
from SYSLIB. See also /SEGREGATE.
In TKB format,
specification.

apply

the

/SQ

switch

the

.TSK

file

/SHAREABLE [: arg]
COMMON
LIBRARY
The COMMON argument informs the Task Builder that a shareable
common is being built.
You should always use the /NOHEADER
qualifier with /SHAREABLE:COMMON.
If you do not specify CODE:PIC
or CODE:POSITION INDEPENDENT, TKB builds an absolute shared
common. All program sections in the common are marked absolute.
If you specify CODE:PIC or CODE:POSITION INDEPENDENT, all program
sections in the common are marked relocatable. In either case,
the .STB file contains all the program section names, attributes,
lengths, and symbols. The .STB file of a common built /SHAREABLE
contains all defined program sections.
In TKB format, apply the
/CO switch to the .TSK or .STB file specification.
The LIBRARY argument informs the Task Builder that a shareable
library is being built.
You should always use /NOHEADER with
/SHAREABLE:LIBRARY. TKB includes only one program section in the
.STB
file.
If
you
do
not
specify
CODE:PIC
or
CODE:POSITION INDEPENDENT, TKB names the program section .ABS,
makes the library position-dependent, and defines all symbols as
absolute.
If you specify CODE:PIC or CODE:POSITION INDEPENDENT,
TKB gives the program section the same name as the-root segment
of the library.
TKB forces this name to be the first and only

6-20

PROGRAM DEVELOPMENT

LINK (Cont.)
declared program section in the library. TKB declares all global
symbols in the .STB file relative to that program section. In
TKB format, apply the /LI switch to the .TSK or .STB file
specification.
/SLAVE
Specifies that the task is to be slaved to a sending task.
When
a slaved task successfully executes the Executive directive
Receive Data, it is given the UIC and TI: of the sending task.
This qualifier applies only to systems with multiuser protection.
Slaved tasks cannot be run with a RUN command.
by the sending task.

They must be

run

In TKB format,
specification.

the

file

apply

the

/SL

switch

.TSK

/SLOW
Specifies that you want to use the slower, but more economical
method of task building.
You should specify this qualifier only
if your link or task build produces the following error message:
NO VIRTUAL MEMORY STORAGE AVAILABLE
The Task Builder (without the /SLOW qualifier) and the Fast Task
Builder use a symbol table structure that can be searched
quickly, but which requires more work file space than if you
specified the /SLOW qualifier.
If you receive the error message
shown, you can either reduce the work-file size (as described in
the Task Builder manual) or use the /SLOW qualifier.
In TKB format,
specification.

apply

the

/SB

switch

the

.TSK

file

/SYMBOL_TABLE[:symboltablespec]
Directs that a symbol table file be produced. The default name
is that of the first input file and the default type is .STB.
The file specification parameter overrides the defaults.
This
qualifier is used when building shared regions.
In TKB format, this qualifier corresponds to the
in
the
list of TKB output files,
called
specification.

third position
the • STB file

/[NO]SYSTEM_LIBRARY_DISPLAY
Directs the Task Builder to produce a map that includes (or does
not include)
global symbols found in LBO: [l,l]SYSLIB or in any
shared regions to which the task links.
This map is usually
considerably longer than the default map.
The information
displayed illuminates the contribution that SYSLIB or the shared
regions make to the task.
If you include this qualifier, LINK includes the /MAP qualifier
as well.
You do not need the /MAP qualifier unless you want to
supply a name for the map file.
If you supply a name,
the map
file appears in your current UFO but is not spooled to the line
printer.
6-21

PROGRAM DEVELOPMENT

LINK (Cont.)
See the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual for more
information.
~-~In TKB format,
specification.

apply

the

/MA

switch

the

.MAP

file

/[NO]TASK[:taskspec]
Specifies a name for the task image file different from that of
If used as a file
the first
input file plus the type .TSK.
specification qualifier, the task name is derived from the name
of the file to which the qualifier is attached. /EXECUTABLE is a
synonym for /TASK.
In TKB format, this qualifier corresponds to the
in
the
list of TKB output files,
called
specification.

first position
the • TSK file

The /NOTASK qualifier specifies that LINK produce no task image
file.
This qualifier is useful when you want to use some
facility of the Task Builder without building a task, to check
for unresolved symbol references or make a map, for instance.
/NOEXECUTABLE is a synonym.
In TKB format, leave the first position in the list of TKB output
file specifications blank, followed by a comma (,).
/TKB
Specifies that the default Task Builder be used to build the
task.
This is the default; the qualifier is included for
completeness.
You can also invoke the default Task Builder from DCL with the
command RUN $TKB.
You must follow TKB format if you run the
default Task Builder in this fashion.
/TRACE
Specifies that the task is to be traceable.
qualifier, a trace trap occurs on the
instruction when the task is run.
In TKB format,
specification.

apply

the

/TR

switch

When you use
completion of
to

the

.TSK

this
each
file

/[NO]WARNINGS
Suppresses diagnostic messages issued by the
Two messages are suppressed:

the

Task

Builder.

n undefined symbols segment "segname"
and
Module "modulename" multiply defines P-section "psectname"
The default is /WARNINGS.
In TKB format,
specification.

use

the

/[-]NM

6-22

switch

the

.TSK

file

PROGRAM DEVELOPMENT

LINK (Cont.)
I [NO]WIDE
Specifies that the Task Builder
format.
The default is /WIDE.

map

printed

132-column

If you include this qualifier, you include the /MAP qualifier as
well.
You do not need the /MAP qualifier unless you wish to
supply a name for the map file.
If you supply a name, the map
file appears in your current UFO but is not spooled to the line
printer.
In TKB format,
specification.

apply

the

/WI

switch

the

file

.MAP

Parameter Qualifiers
Any input file can have a parameter qualifier
identifying the kind of file that it is.

applied

it,

/[NO]CONCATENATE
Identifies the input file as a concatenated object file; this is
the default.
All modules in the file are processed to form the
task image. /NOCONCATENATE specifies that only the first object
module encountered is to be processed, regardless of how many are
present.
In TKB format, apply the /CC switch to an input
concatenated object modules.

file

containing

/DEFAULT_LIBRARY
Specifies that the file to which it is appended replace the
system object module library, LBO: [l,l]SYSLIB.OLB, as the default
library that is searched to resolve unresolved global references.
This qualifier can be applied to only one file and that file must
be an object module library, type .OLB.
In TKB format, apply the /DL switch to an input library file.
/[NO]GLOBALS
Specifies that global symbols referenced and defined by the input
file are (or are not) to be included in the map output file.
The
default is /GLOBALS.
In TKB format, apply the /-MA switch to the input file.
/INCLUDE:modulel[: ••• modulen]
Specifies as many as eight module names from a library using
/INCLUDE.
You must specify at least one.
If you use the
optional module arguments, the Task Builder takes only those
modules from the library.
The module names are defined at
assembly time.
If you want both to resolve undefined references to global
symbols and to specify modules, you must use this qualifier
twice.

6-23

PROGRAM DEVELOPMENT

LINK (Cont.)
In TKB format, apply the /LB switch to an input library
two different ways for both /LIBRARY and /INCLUDE.

file

/LIBRARY
Identifies the file as an object module library. This qualifier
is required for any input library file and is prohibited for any
other type of file. The default file type for object libraries
is .OLB.
The Task Builder searches the library file to resolve all
undefined global symbol references from files appearing to the
left of the library file in the LINK command line.
The Task
Builder then extracts any and all modules that resolve undefined
references and includes them in the task
image.
See also
/INCLUDE.
/SELECTIVE_SEARCH
Instructs the Task Builder to search the file only for undefined
references to global symbols.
This qualifier is most useful when
building an Ancillary Control Processor (ACP) or other privileged
task that maps into the Executive.
If you do not specify this
qualifier, all the Executive's global symbol definitions are
included
in
the task build, whether there are undefined
references to the global symbol or not. The Executive contains a
myriad of modules.
In these and similar circumstances, this
qualifier considerably shortens the symbol table search and
improves system performance.
If you do not use this qualifier, all global
input file are included in the task image.

symbols

from

the

In TKB format, apply the /-SS switch to an input file.

Examples
$ LINK ffil
File ( s) ? WRAY (8fil)
$

This example task builds the object file WRAY.OBJ into the task
image file WRAY.TSK.
For the LINK command to work properly,
WRAY.OBJ must be an object file.
Because the user did not
specify a
file type for
the object file,
the LINK command
supplied the default file type .OBJ.
The return of the implicit prompt indicates successful completion
of the task build~
$ LINK WRAY ·(BIT)

This example is equivalent to the previous one.

6-24

PROGRAM DEVELOPMENT

LINK (Cont.)
$ LINK/MAP WRAY IBD)

This example is similar to the previous two except that a Task
Builder map is also requested. When the task build is completed,
the map WRAY.MAP is spooled to the line printer and also appears
in your directory.
$ LINK/MAP:NEWLINK WRAY lliD)
This example is similar to the previous one, except that a file
specification is provided with the /MAP qualifier. When the task
build is completed, the map file NEWLINK.MAP appears in your
directory.
If you want a copy of this file, issue a PRINT
command.

$ LINK WRAY/MAP IBD)
This example illustrates another way of using the /MAP qualifier.
In this case, when the Task Builder exits, a file called WRAP.MAP
appears in your directory but is not spooled to the line printer.
If you want a copy of this file, issue a PRINT command.
$ LINK/DEBUG WRAY IBD)
This example builds the task WRAY.TSK including ODT, the
Debugging Tool.

On-line

$ LINK/OPTIONS WRAY IBru
Option?UNITS=8 IBru
Option?ASG=TT0:7:8 filf)
Option? filf)
$
This example illustrates the use of the /OPTIONS qualifier.
The
command sequence builds the task with eight logical units (LUNs),
with LUNs 7 and 8 assigned to TTO:.
See the discussion in
Section 6.2.1.
The entire LINK command is entered by the final
RETURN in response to the Option? prompt.

$ LINK/OPTIONS/NOMEMORY MAN WRAY ~
Option?PAR=KROBAR:50000:4oooo ~
Option? ~
$
This example builds the task to run on an unmapped system in the
partition named KROBAR, which has a base address of 50000 and a
size of 40000.

$ LINK/CHECKPOINT:SYSTEM WRAY
$ LINK/CHECKPOINT WRAY

The commands in this example are equivalent. The task
checkpointable to the system checkpoint file.

6-25

built

PROGRAM DEVELOPMENT

LINK (Cont.)
$ LINK/CHECKPOINT:TASK WRAY lBrn
In this example, the task is built with checkpoint space reserved
where the task image file is stored.

$ LINK WRAY, 3TRACK lBrn
In this example, the task
is built from two object modules,
WRAY.OBJ and 3TRACK.OBJ.
The task
image file has the name
WRAY.TSK.
It is installed and run under that name.

$ LINK/TASK:SHACK WRAY, 3TRACK lBrn
In this example the task
is built from the same two object
modules as in the previous example.
However, the task image file
is given the name SHACK.TSK by the /TASK qualifier.
It
is
installed and run under that name.

$ LINK/OPTIONS WRAY, 3TRACK lBrn
Option?TASK=SHACK lBrn
Option? lBrn
$
In this example, the task is built from two object modules.
The
task image file has the name WRAY.TSK, but the default task name
(specified by the TASK option) is SHACK.
The default task name
is used by the INSTALL command (see Section 7.8) if the user does
not specify a task name explicitly. Only privileged users can
issue the INSTALL command. This means that to run the task from
a file, you use the command RUN WRAN, but if you run it after
it
has been installed, you use the command RUN SHACK.

$ LINK/OVERLAY RAYMEN lBrn
In this example, the Task Builder uses the file RAYMEN.ODL to
build an overlaid task.
(.ODL is the default file type for the
/OVERLAY qualifier.) The input file RAYMEN.ODL must be written in
the Overlay Description Language.
Only one file can be specified
with this qualifier. The files that form the overlaid task are
called automatically.

$ LINK @WRAYBLD

This example specifies the indirect command file WRAYBLD.CMD as
input to the Task Builder. This file must be written in Task
Builder format, not DCL format.
This file can be the ATLNK.TMP
file renamed.
See the discussion under /SAVED.

Hot es
You must read the appropriate documentation to use
fully.
This is true without exception.

this

command

The RSX-llM/M-PLUS and Micro/RSX Task Builder Manual does not use
the term "link." Irlthe Task Builder manual, the preferred term
is "build."
6-26

PROGRAM DEVELOPMENT

LINK (Cont.)
Note that nonprivileged users can build privileged tasks and
high-priority tasks, but those users cannot run the privileged
tasks. Nor can they run tasks at any but the default priority of

so.

Remember that for nonprivileged users, the RUN command is ~lways
a
combination
of
three commands.
In effect,
it is an
INSTALL-RUN-REMOVE command. Thus, references to installation in
the preceding discussion refer to explicit installation by
privileged users through the INSTALL command and
implicit
installation through the RUN command as well. See Chapter 7 for
further details.
You can include comments in the LINK command line in the usual
DCL fashion.
However, comments in a list of TKB options must
appear on a line by themselves preceded by a semicolon.
Do not
use the exclamation point (!) for comments in a list of options.

Error Message
LIN -- Library invalid on last input file

Explanation: The syntax of LINK requires that the last input
file specified must be a valid (single) object file that is not
part of a library.
User Action:

Check for proper syntax and reenter the command.

6-27

PROGRAM DEVELOPMENT

LIBRARY
6.3

LIBRARY

LIBRARY creates and maintains user-written
library
files,
or
libraries.
Libraries can contain macro definitions, object modules,
or, in the case of universal libraries, anything.
Maintenance functions of LIBRARY include
extracting,
deleting,
inserting, and replacing library entries. Libraries can be compressed
(squeezed) to save disk space.
Library contents can also be listed.
User-written object module libraries can be used as input to the Task
Builder, either directly or through LINK.
The Task Builder (TKB)
searches for definitions of all global symbols referenced in your
program in the following fashion:
1.

Searches other modules included in the LINK command

2..

Searches a user-written object module library included in the
LINK command

Searches the system library

User-written macro libraries hold source macros for use as input by
the MACR0-11 Assembler, either directly or through MACRO.
The
assembler searches the library you specify for macros listed in .MCALL
statements and called in your source program before searching the
system macro library.
In general, LIBRARY handles object module libraries and
macro
libraries in the same way.
This means that references in this section
to modules can be usually taken as referring to macros as well as
object modules.
Libraries are direct access files containing one or more modules of
the same type.
These files are organized for rapid access by the Task
Builder and MACR0-11 Assembler.
Universal libraries can contain
virtually anything to which you wish to have rapid access, such as
text files.
Library files contain two directory tables.
The entry point table
(EPT)
contains entry point names (global symbols). The module name
table (MNT) contains module names. Both tables ·are in alphabetical
order.
Object module names are derived from .TITLE directives, while
entry point names are derived from defined global symbols.
Once an
entry point is located,
its associated module can be accessed
directly. Macro module names are derived from .MACRO directives;
macros are linear code and do not have entry points.
This section does not teach you how to use the Librarian Utility
Program (LBR), but only how to use the LIBRARY command. See the Notes
for suggested further reading.
Format
LIBRARY
Operation? operation[/qualifier[s]]
LIBRARY operation[/qualifier[s]]
LIBRARY @f ilespec
6-28

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
LIBRARY performs the following operations:
COMPRESS
INSERT

CREATE
LIST

DELETE
REMOVE

EXTRACT
REPLACE

Each of these operations is treated as a separate command in this
description.

Notes
LIBRARY invokes the Librarian Utility Program (LBR). To use this
command successfully, you must familiarize yourself with this
utility, which is described in the RSX-llM/M-PLUS Utilities
Manual.
LBR format differs from the format of the DCL LIBRARY command.
DCL translates the DCL command line into LBR format.
The
descriptions presented here
include cross-references to the
equivalents in LBR format of the DCL command elements.
Use the
SET DEBUG command to see the translation.
If you wish to use indirect command files with LIBRARY,
the
indirect command file must be in LBR format, not DCL format.
Only one level of indirect referencing is permitted.
You should also be familiar with the way the MACR0-11 Assembler
and the Task Builder use libraries. See the PDP-11 MACR0-11
Language Reference Manual, the RSX-llM/M-PLUS and Micro/RSX Task
Builder
Manual,
and
the RSX-llM/M-PLUS Guide to Prograffi
Development for more information.
You cannot use wildcards (the asterisk(*) and the
(%)) in file specifications in LIBRARY operations.

percent

sign

Library modules are limited to 65536 words per module.
Libraries are limited to 65536 blocks.
The LIBRARY command operates on three kinds of libraries:
•

Object module libraries.
These can be user libraries
one of the following DIGITAL-supplied libraries:

LBO: [l,l]SYSLIB.OLB

System library
(this is the
library searched by the Task
Builder by default).

LBO: [l, l]VMLIB.OLB

Virtual
library.

LBO: [l,l]EXELIB.OLB

Executive library.

LBO: [l,l]RMSLIB.OLB

Record
Management
library.

LBO: [l,l]FOROTS.OLB

FORTRAN IV library (optional).

LBO: [l,l]F4POTS.OLB

FORTRAN-IV-PLUS and
library (optional).

6-29

memory

management

Services

FORTRAN-77

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
•

•

Macro libraries.
These can be user libraries or
the following DIGITAL-supplied libraries:

one

LBO: [l,l]RSXMAC.SML

System macro library. This is
the library searched by the
{note
assembler by
default
nonstandard file type).

LB 0: [ 1, 1] EXEMAC. MLB

Executive macro library.

LBO: [l,l]RMSMAC.MLB

Record
Management
library.

Services

Universal libraries. The Librarian utility can also be
used to create and maintain a third form, universal
libraries, using the /UNIVERSAL qualifier on some of the
LIBRARY commands.

The LIBRARY command and utility have no relationship to the other
kinds of libraries used on RSX-llM systems. Specifically, LBR
has no relationship to supervisor-mode libraries or core-resident
libraries created by the Task Builder.
On RSX-llM, the system directort {LBO: [1,54], which contains all
system tasks, such as commands and utilities) is also called a
library, but also has no relationship to the LIBRARY command.
The /SQUEEZE qualifier causes all text to the right of the
rightmost semicolon to be deleted. This convention permits you
to preserve any meaningful semicolon by adding another semicolon
to its right.
Examples of meaningful semicolons include using
the ASCII value of the semicolon in code, or a semicolon marking
a comment you wish to preserve. The following line of code moves
the ASCII value of the semicolon to register 1:
MOVB

#' ; , Rl

but emerges after the /SQUEEZE as follows:
MOVB

To preserve the meaningful semicolon, use the following form:
MOVB

#';, Rl; THIS DUMMY COMMENT SAVES THE CODE

which emerges after the /SQUEEZE as follows:
MOVB

#';, Rl

Similarly, the following comment:
;NEXT 5 LINES ARE CRUCIAL
disappears after the /SQUEEZE, but this form:
;NEXT 5 LINES ARE CRUCIAL
emerges after the /SQUEEZE as the following:
;NEXT 5 LINES ARE CRUCIAL

6-30

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Keep this convention in mind whenever you are using the
qualifier.

/SQUEEZE

All error messages are described in Section 6.3.9.
Some error
messages are closely related to particular LIBRARY operations.
Descriptions of these messages are repeated in the section on the
operation to which they pertain.

6.3.1

LIBRARY/COMPRESS

LIBRARY/COMPRESS physically deletes modules that have been
deleted
through
LIBRARY/DELETE.
You can rename the
compressed library.

logically
resulting

Format
LIBRARY/COMPRESS[: (arg[,s])] libspec [newlibspec]

Arguments
GLOBAL:n
MODULES:n
BLOCKS:n

Parameters
libspec
Specifies the name of the library file to be compressed.
The
default type is .OLB, specifying an object module library.
If
you wish to compress a macro library (standard file type .MLB),
or a universal library
(standard file type .ULB), you must
specify the file type explicitly.
newlibspec
This optional parameter specifies a name for the newly compressed
library.
If you do not specify a name, the new file has the same
name as the old one. The old file is not deleted after you
create a new library with this command.

Arguments
If you are specifying more than one argument, the arguments must
be enclosed in parentheses and separated by commas.
If you are
specifying only one argument, the parentheses are not necessary.
GLOBALS:n
Specifies the number of global symbols
(entry point table
entries)
to allocate.
The default n is the number of global
symbols allocated in the old library. The maximum n is 4096.
The value of n is always forced to zero for macro and universal
libraries.

6-31

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
MODULES:n
Specifies the number of entries to allocate in the module name
table.
The default value is the number of entries in the old
library. The maximum number of module names is 4096.
BLOCKS:n
Specifies the size of the library in 256-word
default size is the size of the old library.

blocks.

The

Example
$ LIBRARY/COMPRESS LB: [l,l]SYSLIB.OLB ~

This example compresses the system object module library.
Notes
This command is equivalent to the LBR /CO
library file.
I f you
1 ike,
compressing a
operation.

6.3.2

switch

applied

you can use LIBRARY/LIST before
and
after
library to see the effects of the compress

LIBRARY/CREATE

LIBRARY/CREATE creates a library and optionally inserts
modules into it.

one

The library is a contiguous file created on a volume
random-access device, that is, disk or DECtape.

mounted

more
on

Format
LIBRARY/CREATE[: (arg[,s])] [/qualifier[s]] libspec [infilespec[,s]]
Arguments
GLOBALS:n
MODULES:n
BLOCKS:n
Command Qualifiers
/[NO]GLOBALS
/MACRO
/OBJECT
/SELECTIVE SEARCH
/SQUEEZE /UNIVERSAL

6-32

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Parameters
libspec
Specifies the name of the library file being created.
The
default file type is .OLB if an object module library is being
created, .MLB if a macro library is being created, and .ULB if a
universal library is being created.
inf ilespec [ s]
Specifies the file or files to be used as
input to the new
library file.
If no input files are specified, an empty library
file is created. The default file types are .OBJ when creating
object module libraries, .MAC when creating macro libraries, and
.UNI when creating universal libraries.

Arguments
If you are specifying more than one argument, the arguments must
be enclosed in parentheses and separated by commas.
If you are
specifying only a single argument, the parentheses are not
necessary.
GLOBALS:n
Specifies the number of global symbols
(entry point table
entries)
to allocate.
The default is 512 for object libraries.
This value is always forced to 0 for macro and universal
libraries.
n can be from 0 through 4096.
MODULES:n
Specifies the number of entries to allocate in the module name
table.
The default value is 256. n can be from 0 through 4096.
BLOCKS:n
Specifies the size of the
default size is 100 blocks.

library

256-word

blocks.

The

Specifies whether global symbols should be included in the
point table.

entry

Command Qualifiers
/[NO]GLOBALS

Use this qualifier if you wish to use the same global symbols
in
more than one module.
/GLOBALS is the default but is a no-op.
/SELECTIVE_SEARCH
Sets the selective search attribute bit in the module header of
object modules as they are inserted into an object library.
You
must specify an input file or files.
This qualifier has meaning for object module libraries only.

6-33

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Object modules with the selective search attribute are given
special treatment by the Task Builder. Global symbols defined in
modules with the selective search attribute are only included in
the
Task
Builder's symbol table if they were previously
referenced by other modules.
/SQUEEZE
Reduces the size of macro definitions by eliminating all trailing
blanks and tabs, blank lines, and comments from macro text. You
must specify an input file or files.
This qualifier has meaning for macro libraries only.
Macros that have been squeezed not only take up less room in
macro library file, but also take up less memory.

the

See the Notes to Section 6.3 for
/SQUEEZE qualifier.

the

important

information

This /SQUEEZE qualifier is the equivalent of the LBR /SZ switch
applied to the output library file when using the /CR switch.
/MACRO
Specifies that the library being created is a macro library.
/OBJECT
Specifies that the library being created is an object
library.
This is the default and need not be specified.

module

/UNIVERSAL
Specifies that the library being created is a universal library.
Example
$ LIBRARY ID
Operation? CREATE: (GLOBALS:l28,MODULES:64)
Library? CARNEGIE ID
Modules? DEWEY ,CONGRESS ,MODERN ID

This example creates the library CARNEGIE.OLB with a size of 100
blocks
(the default), 128 entry points, and 64 module names, and
inserts object modules from
the
input
files
DEWEY.OBJ,
CONGRESS.OBJ, and MODERN.OBJ.
Notes
This command is the equivalent of applying the LBR /CR switch
the output file.
Tables should be allocated
Expanding table allocations
copy the entire file.

to
maximum
anticipated
size.
requires using LIBRARY/COMPRESS to

If the qualifiers /SELECTIVE SEARCH and /SQUEEZE are used
LIBRARY/CREATE, you must specify an input file or files.

6-34

with

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
6.3.3

LIBRARY/DELETg

LIBRARY/DELETE deletes modules from any library.
See LIBRARY/REMOVE
for removing global symbols {entry points) from a library.

Format
LIBRARY/DELETE libspec module[,s]

Parameter
libspec
Specifies the name of the library from which modules
deleted.

are

module [, s]
You-can specify as many as 15 names of
separated by commas.

modules

If you do not specify the module list, you will be
it.

deleted,

prompted

for

Example
$ LIBRARY/DELETE ~
Library? BUMPERS ~
Module {s)? BUGGY, BABY, RUBBER ffirn
Modules deleted:
BUGGY
BABY
RUBBER
This example deletes the modules BUGGY, BABY, and RUBBER from the
latest version of the object module library BUMPERS.OLB.

Notes
This command is the equivalent of the LBR /DE switch
the output file.

applied

When you delete an entry from a library,
the entry is not
physically removed, but is marked for deletion. This means that
although the module is no longer accessible, the file space it
occupied is not available.
To clear this space, use the
LIBRARY/COMPRESS operation, Section 6.3.1.
If a specified module is not contained in the
following message is printed on your terminal:

library,

the

LBR -- *FATAL*--No module named "name"
All the modules in your list up to the incorrect module name will
have been deleted. None of the modules following the incorrect
module name will have been deleted. You should use LIBRARY/LIST,
Section 6.3.6, to check which modules have been deleted and which
have not.

6-35

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
See LIBRARY/REMOVE (Section 6.3.7) for
global symbols from libraries.

information

removing

LIBRARY/EXTRACT

6.3.4

LIBRARY/EXTRACT reads one or more modules from a
them into a specified output file.

library

and

writes

You can extract up to eight modules with a single LIBRARY/EXTRACT
operation.
If more than one module is extracted, the modules are
concatenated in the output file.

Format
LIBRARY/EXTRACT/qualifier[:filespec] libspec module[,s]

Command Qualifier
/OUTPUT[:filespec]

Parameters
libspec
Specifies the library from which modules are to be extracted.
The default file type is .OLB, corresponding to an object module
library.
If you wish to extract from a macro or universal
library, you must specify the appropriate file type.
module [, s]
Specifies the modules that are to be extracted. If you do not
include a list, all modules in the library are extracted and
concatenated in the output file in alphabetical order.
You can
specify up to eight modules, separated by commas.

Command Qualifier
/OUTPUT
Specifies the file to which the extracted modules or macros are
to
be
written.
If yo~ specify /OUTPUT without a file
specification, the default is to write the modules to your
terminal.
This makes sense only for macro libraries or universal
libraries containing text modules.
If you do not include the qualifier, you will be prompted To?, to
which you are to reply with a file specification. You can reply
TI:
to have the output printed on your terminal.

Examples
$ LIBR/EXTRACT/OUTPUT:MATH LBO: [l,l]SYSLIB ARITH IBm
This example extracts the module named ARITH from the library
SYSLIB.OLB,
the system object library. The module is placed in
the default directory as a file named MATH.OBJ.

6-36

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
$ LIBR/EXTRACT/OUT:TI: LBO: [l,l]RSXMAC.SML STOP$S
.MACRO STOP$S ERR
.MCALL DIR$
MOV
(PC)+,-(SP)
.BYTE
131.,l
DIR$
, ERR
.ENDM
STOP$S
This example extracts the macro named STOP$S
macro library and prints it on the terminal.

from

the

system

Notes
This command is the equivalent of the LBR /EX switch
the library file as an input file.

applied

LIBRARY/EXTRACT has no effect
modules are extracted.

which

the

6.3.5

the

library

from

LIBRARY/INSERT

LIBRARY/INSERT inserts modules from one or more files into a library.
Format
LIBRARY/INSERT libspec filespec[,s]
Command Qualifiers
/[NO]GLOBALS
/SELECTIVE SEARCH
/SQUEEZE Parameters
libspec
Specifies the library into which modules are to be inserted.
The default file type is .OLB.
If you wish to insert modules
into a macro library (file type .MLB) or a universal library
(file type .ULB), you must specify the file type explicitly.
filespec[s]
Specifies the file or files containing concatenated modules to be
inserted into the specified library.
Any number of files can be specified and each
any number of concatenated modules.

file

can

contain

The default file type is determined by the library into which
modules are being inserted.
It is .MAC for macro libraries, .OBJ
for object module libraries, and .UNI for universal libraries.

6-37

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Command Qualifiers
/[NO]GLOBALS
Specifies whether entry points for the specified
be included in the entry point table.

modules

should

Use this qualifier if you wish to insert global symbols having
the same name as symbols already in the library file.
The
default, /GLOBALS, does not permit this operation.
/SELECTIVE_SEARCH
Sets the selective search attribute bit in the module header of
object modules as they are inserted into an object library.
You
must specify an input file or files.
Object modules with this attribute are given special treatment by
the Task Builder.
Global symbols defined in modules with the
selective search attribute are not included in the Task Builder's
symbol table unless they were previously referenced by other
modules.
/SQUEEZE
Reduces the size of macro definitions by eliminating all trailing
blanks and tabs, blank lines, and comments from macro text.
You
must specify an input file or files.
Macros that have been squeezed not only take up less room in
macro library file but also take up less memory.

the

See the Notes to Section 6.3 for
/SQUEEZE qualifier.

the

important

information

This qualifier is the equivalent of the LBR /SZ switch applied to
the output file.

Example
$ LIBR/INSERT (Bfl)
Library? LBO: (1, 1] SYSLIB
Module(s)? USERSUB ~

This example inserts object modules from the file USERSUB.OBJ
into the system object module lbrary, LBO: [l,l]SYSLB.OLB.

Notes
This command is the equivalent of the LBR /IN command.
Note that a single input file can contain more
module or macro.

than

one

object

If you are inserting macros into a macro library, LIBRARY/INSERT
insert only the .MACRO and .ENDM lines and what appears between
them. All text in the file not bracketed by these assembler
directives is ignored. This feature is in addition to the action
of the /SQUEEZE qualifier.

6-38

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
If you attempt to insert a module that already exists in the
library file, the following message is printed on your terminal:
LBR -- *FATAL*Duplicate module name "name" in filename
If you attempt to insert a module with an entry point that
duplicates one that is already in the EPT, the following message
is printed on your terminal:
LBR -- *FATAL*Duplicate entry point "name" in filename
In the case of either of these messages, all operations up to the
point at which the error occurred should have been successful.
No operations past that point will have taken place.
Use
LIBRARY/LIST to check which modules have been inserted and which
have not.

6.3.6

LIBRARY/LIST

LIBRARY/LIST lists the names of all
terminal or in an output file.

modules

library

your

Format
LIBRARY/LIST[:filespec] libspec

Command Qualifiers
/BRIEF
/FULL
/[NO]NAMES

Parameter
libspec
Specifies the library you wish listed. The default file type is
.OLB.
If you wish to list a universal or macro library, you must
specify the appropriate file type.

Command Qualifiers
/LIST [: f ilespec]
If you do not include a file specification as
/LIST, the library is listed on your terminal.

argument

If you include a file specification as an argument, the default
device and UFO are the same as those of the library you are
listing and NOT your current defaults. See the examples.
/BRIEF
Specifies that you wish the list to include only
names. This is the default. See the examples.

6-39

the

module

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
/FULL
Requests a listing of all module names, along with a module
insertion,
and
description,
including
size,
date
of
module-dependent information. See the examples.
/[NO]NAMES
Requests a list of modules in the library, along with their entry
points.
The default is the /NONAMES qualifier.
See the
examples.
Examples
$ LIBRARY/LIST LBO: [l, l] SYSLIB IBfil)

Directory of file SYSLIB.OLB;l002
Object module library created by: LBR V06.00
Last insert occurred 25-MAY-85 at 19:34:32
MNT entries allocated: 768; Available: 549
EPT entries allocated: 2048; Available: 873
File space available: 00309 words
Recoverable deleted space: 14892 words
ALERR
ALSCT
ALTPRI
ANS PAD
AR ITH

This example shows the default display from LIBRARY/LIST.
the module names appear.
The information appears on
terminal.
$LIBRARY/LIST/FULL LBO: [l,l]SYSLIB

Size:00073

Inserted:22-MAY-85

Ident:OO

ALSCT

Size:00134

Inserted:22-MAY-85

Ident:OO

ALTPRI

Size:00081

Inserted:22-MAY-85

Ident:OO

ANSPAD

Size:00068

Inserted:25-MAY-85

Ident:20.0P6

ARITH

Size:00088

Inserted:22-MAY-85

Ident:03.03

6-40

Only
your

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
This example shows the display from LIBRARY/LIST/FULL, which
includes full module descriptions. This information appears on
your terminal.
$ LIBRARY/LIST/NAMES LBO: [l,l]SYSLIB

** Module:ALERR
$ALERR

** Module:ALSCT
ALSCT

** Module:ALTPRI
ALTPRI

** Module:ANSPAD
•• ANSP

** Module:ARITH
$DIV

$MUL

This example shows the display from
lists entry points for each module.

LIBRARY/LIST/NAMES,

$ LIBRARY/LIST/FULL/NAMES LBO: [l,l]SYSLIB

6-41

which

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
** Module:ALERR

Size:00073

Inserted:22-MAY-85

Ident:OO

Size:00134

Inserted:22-MAY-85

Ident:OO

Size:00081

Inserted:22-MAY-85

Ident:OO

Size:00068

Inserted:25-MAY-85

Ident:20.0P6

Size:00088

Inserted:22-MAY-85

Ident:03.03

$ALERR
** Module:ALSCT
ALSCT
** Module:ALTPRI
ALTPRI
** Module:ANSPAD
•• ANSP
** Module:ARITH

This example shows the display from LIBRARY/LIST/FULL/NAMES,
which includes not only module descriptions but also entry points
for each module.

$ SHOW DEFAULT (BTil
DB2:
[303,S]
TT56:
$ LIBRARY/LIST:FRED.LIS LBO: [l,l]SYSLIB (BTil
LBR -- *FATAL*-Open failure on file FRED.LIS
$
In this example, the user intended to create a list of the
modules in SYSLIB in the default UFO on the default device. The
error message indicates that the listing file cannot be opened.
This is because LBR attempted to place FRED.LIS on LBO:
in
[1,1], where the user did not have file creation privileges. See
next example.

$ SHOW DEFAULT (BTil
DB2:
[303,5]
TT56:
$ LIBRARY/LIST:DB2: [303, S]FRED.LIS LBO: [l, l]SYSLIB
$

(BTil

In this example, the user explicitly stated the device
directory for the listing file and the command succeeded.

6-42

and

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Notes
This command is the equivalent of applying the LBR /LI,
/LE switches to the listing file.
Note that there are
command.

6.3.7

four

possible

listing

formats

/FU,
with

or
this

LIBRARY/REMOVE

LIBRARY/REMOVE removes global symbols (entry points) from a library.
See LIBRARY/DELETE for deleting object modules from a library.

Format
LIBRARY/REMOVE libspec global [global[,s]]

Parameters
libspec
Specifies the name of the library from which you wish
global symbols.

remove

global [, s]
Specifies the global symbols you wish to remove from the library.
You can specify as many as 15 global symbols.
Example
$ LIBRARY/REMOVE DOUBLE TINKER,EVERS,CHANCE

Entry points deleted:
TINKER
EVERS
CHANCE
This example deletes the globals TINKER, EVERS, and
the library DOUBLE.OLB.

CHANCE

This command is the equivalent of the LBR /DG switch
the output file.

applied

from

Notes

If a specified global is not included in the
following message is printed on your terminal:
LBR -- *FATAL*

library,

to
the

No entry point named "name"

All the global symbols (entry points) in your list up to the
incorrect name will have been deleted.
None of the globals
following the incorrect name will have been deleted. You should
use LIBRARY/LIST (Section 6.3.6) to check which globals have been
deleted and which have not.

6-43

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
6.3.8

LIBRARY/REPLACE

LIBRARY/REPLACE replaces a module in a library with a
the same name and deletes the old module.

new

module

When a match occurs on a module name, the existing module is logically
deleted and all its entries are removed from the global symbol table.
Format
LIBRARY/REPLACE libspec filespec[,s]
Command Qualifiers
/[NO]GLOBALS
/SELECTIVE SEARCH
/SQUEEZE Parameters
libspec
Specifies the library in which modules are to be replaced.
The
default file type is .OLB, corresponding to object libraries.
If
you wish to replace macros in a macro library (file type .MLB) or
a universal library (file type .UNI), you must specify the file
type explicitly.
filespec[ ,s]
Specifies the file or files containing the new modules.
The
default file type is determined by the type of library in which
modules are being replaced.
It is .OBJ for object module
libraries,
.MAC for macro libraries, and .UNI for universal
libraries.
If the module to be replaced does not
LIBRARY performs an insert operation.

exist

the

library,

If the module to be replaced exists, a message is printed.
See
example.
If the module does not exist, it is inserted, but no
message is printed.
Command Qualifiers
/[NO]GLOBALS
Specifies whether entry points for the specified modules should
be included in the entry point table. The default is /GLOBALS.
/SELECTIVE_SEARCH
Sets the selective search attribute bit in the module header
object modules as they are inserted into an object library.

Object modules with the selective search attribute are given
special treatment by the Task Builder. Global symbols defined !n
modules with the selective search attribute are only included in
the
Task
Builder's symbol table if they were previously
referenced by other modules.

6-44

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
/SQUEEZE
Reduces the size of macro definitions by eliminating all trailing
blanks and tabs, blank lines, and comments from macro text.
Macros that have been squeezed not only take up less room in the
macro library file but also take up less memory in the assembler
when they are invoked.
See the Notes in Section 6.3 for. more information on the /SQUEEZE
qualifier.
This is the equivalent of the LBR /SZ switch applied to the input
file.
Example
$ LIBR/REPLACE LBO: [l,l]SYSLIB USERSUB

MODULE "USERSUB" REPLACED
This example replaces the modules in the file SYSLIB.OLB with new
modules bearing the same names in the file USERSUB.OBJ.
Entry
points are also redefined.
Notes
This command is the equivalent of the LBR /RP command.
There must be enough space in the library's tables for both the
modules being replaced and their replacements since the new
modules are entered before the old modules are deleted.
The old modules are logically deleted only.
You must use
LIBRARY/COMPRESS to eliminate the modules themselves and free the
space they occupy.

6.3.9

Error Messages from LIBRARY

LIBRARY has two kinds of error messages, diagnostic and fatal.
Diagnostic messages are marked *DIAG* and inform you of conditions
that require your consideration but do not warrant termination of the
command. Depending on the message and the operation, you can decide
what further action is called for.
The operation completes.
Fatal messages are marked *FATAL* and describe conditions that caused
LBR to terminate execution of your command. The operation does not
complete.
In general, fatal output errors leave the library in an indeterminate
state.
You should use LIBRARY/LIST to determine how much of the
operation completed before the fatal error occurred.
If a library
file is corrupted; the library must be re-created.
Some errors result from corrupted library files.
You can use VFY, the
File Structure Verification utility, to determine whether a file is in
Files-11 format. A library file can be in Files-11 format and still
be corrupted as a library, however.
6-45

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
Error messages appear on your terminal in the following formats:
LBR -- *DIAG*-message
LBR--*FATAL*-message
Note that error messages from LIBRARY are tagged LBR after the utility
and not LIB after the command. This is an exception to the general
rule on DCL error messages.
LBR -- Bad library header
Explanation:

The file either is not a library or is corrupted.

User Action: Make sure the file is a library.
If the file is a
library, use VFY, the File Structure Verification utility, to
determine if it is corrupted.
See
Chapter
9
of
the
RSX-llM/M-PLUS Utilities Manual.
LBR -- Command I/O error
Explanation: There are two possible causes. The problem may be
with the physical device, such as not being spun up. Or, the
file may be corrupted or have an incorrect format, such as a
record length exceeding 132 bytes.
User Action: Determine the condition that caused the message and
correct the condition. Reenter the command line.
LBR -- Command syntax error
command line
Explanation:

The reprinted command line has a syntax error.

User Action:
line.

Check for proper syntax

and

reenter

the

command

LBR -- Duplicate entry point name "name" in filename
Explanation: Your command attempted to insert
(not replace) a
module containing the given entry point name into a library
already containing an entry point of that name.
User Action: Make sure you have named the correct input file.
If not, reenter the command naming the correct input file.
If
the input file is correct, you can delete the duplicate entry
point from the library and reenter the command.
LBR -- Duplicate module name "name" in filename
Explanation: Your command attempted to insert
(not replace) a
module with the given name into a library that already contains a
module of that name.
User Action: Make sure you have named the correct input file.
If the input file is correct, you must decide whether or not to
use LIBRARY/REPLACE to replace the module that is already in the
library.

6-46

PROGRAM DEVELOPMENT

LIBRARY {Cont.)
LBR -- EPT or MNT exceeded in filename
Explanation: The GLOBAL or MODULE table limit has been
during the execution of a REPLACE or INSERT operation.

reached

User Action: Copy the library using LIBRARY/COMPRESS and include
the /MNT or /EPT qualifier to increase table size.
LBR -- EPT or MNT space exceeded in compress
Explanation: A GLOBAL or MODULE table size was specified in a
COMPRESS operation for the output library file that is not large
enough to contain the EPT or MNT entries used in the input
library.
User Action: Reenter the command line with a larger EPT
table size specified.

MNT

LBR -- Error in library tables, File "filename"
Explanation:
library.

Either the library is corrupted

not

User Action:
If the file is corrupted, no recovery is possible.
The file must be reconstructed. If the file is not a library,
reenter the command line with the correct file named.
LBR -- Fatal compress error
Explanation: The input library
corrupted or is not a library.

COMPRESS

operation

User Action:
If the file is corrupted, no recovery is possible.
The file must be reconstructed. If the file is not a library,
reenter the command line with the correct file named.
LBR -- Get time failed
Explanation: System error. LBR attempted to execute a Get
Parameters directive and failed.

Time

If the error
is
User Action: Reenter the command line.
repeated, see your system manager. Plan to submit a Software
Performance Report. Save console dialogue and other pertinent
information.
LBR -- Input error on filename
Explanation:

The file system has detected an error.

User Action: Reenter the command.
your system manager.

If the error is repeated, see

LBR -- Insufficient dynamic memory to continue
Explanation:

The partition in which LBR is running is too small.

User Action:

See your system manager.

6-47

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
LBR -- Invalid EPT and/or MNT specification
Explanation: Command included
greater than 4096.
User Action:

argument

for

/MNT

/EPT

Check for proper syntax and reenter command.

LBR -- Invalid module format, insertion-module
Explanation: Command attempted to insert
definition into an object module library.

the

named

macro

User Action: Correct error by reentering command with object
module for object module library or macro for macro library.
LBR -- Invalid format, input file filename
Explanation: Your command named either an input file that is not
in the standard format or a file that is corrupted.
User Action:
command.

Make sure you have named the right file and reenter

LBR -- Invalid library type specified
Explanation: Your command attempted to set an illegal library
type as the default. The file types .OBJ and .MAC are the only
valid default file types for the command.
User Action:

Reenter command after checking proper syntax.

LBR -- I/O error on input file "filename"
Explanation: A read error occurred on an input file.
can have two causes:

This error

A problem exists with the physical device (for
disk may not being spun up).

The input file is corrupted or in the wrong format,
records exceeding 132 bytes in length.

User Action: Determine the cause of the error
condition.
Reenter the command line.

and

example,

the

such

correct

the

LBR -- Library file specification missing
Explanation:
Your
command
was
specification of the library file.
User Action:

entered

without

proper

Check for proper syntax and reenter the command.

6-48

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
LBR -- Mark for delete failure on LBR work file
Explanation: LBR automatically creates a work file when it
begins processing commands and marks it for delete. For some
reason this marking failed. The work file is a lost file and
does not appear in any UFO.
User Action: See your operator or system manager. The file must
be deleted using VFY, the File Structure Verification utility.
See Chapter 9 of the RSX-llM/M-PLUS Utilities Manual.
LBR -- No entry point named "name"
Explanation: Your command named an entry
that is not in the library.

point

deleted

User Action: Check command for proper syntax and
reenter
command.
You may have misspelled the entry point name or named
the wrong library.
LBR -- No module named "module"
Explanation: Your command named a module to be deleted
not in the library.

that

User Action: Check command for proper syntax and
reenter
command.
You may have misspelled the module name or named the
wrong library.
LBR -- Open failure on file "filename"
Explanation: The file system detected an error while attempting
This error is caused by one of the following
to open a file.
conditions:
1.

The user directory
operation.

area

protected

There is a problem with the
being spun up.

The volume is not mounted.

The directory does not exist.

The file does not exist.

There is i'nsufficient space to allocate the library file on a
LIBRARY/CREATE or LIBRARY/COMPRESS.

There is insufficient pool space (DSR} in the Executive.

physical

against

device,

such

Write
as

User Action: Determine the cause of the error and correct it
you can. If you cannot, see your operator or system manager.

6-49

not

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
LBR -- Open failure on LBR work file
Explanation: The file system detected an error while attempting
to open the LBR work file.
The LBR work file is created on the
volume from which LBR was installed.
One of the following
conditions can cause this error:
1.

The volume is full.

The device on which the volume is mounted is write-protected.

There is a problem with the physical device.

There is insufficient pool space (DSR) in the Executive.

User Action: Determine the cause of the error and correct it
you can.
If you cannot, see your operator or system manager.

LBR -- Output error on filename
Explanation: A write error has occurred on the output file.
of the following conditions can cause this error:

One

The volume is full.

The device on which the volume is mounted is write-protected.

The hardware has failed.

User Action: Determine the cause of the error and correct it
you can.
If you cannot, see your operator or system manager.

LBR -- Positioning error on filename
Explanation: The device on which the volume is mounted
write-locked or some other hardware difficulty exists.

User Action: Determine the cause of the error if
you cannot, see your operator or system manager.

you

can.

LBR -- Virtual storage requirements exceed 65536 words
Explanation: This error may occur with maximum size libraries in
conjunction with a single command line that logically deletes a
large number of modules and entry points and continues to replace
them with an equally large number of modules and entry points
having highly dissimilar names.
Normally, this message indicates
some sort of internal system error.
User Action:
Rerun the job after dividing the command line
several smaller lines that perform the same operations.

6-50

into

PROGRAM DEVELOPMENT

LIBRARY (Cont.)
LBR -- work file I/O error

Explanation: A write error has occurred on the LBR work
One of the following conditions can cause this error:

file.

The volume is full.

The device on which the volume is mounted is write-protected.

The hardware has failed.

User Action: Determine the cause of the error and correct it
If you cannot, see your operator or system manager.

you can.

6.4

SET AND SHOW

You can set and show group global event flags.
These are a set of 32
global event flags available only to tasks run from one group of UICs.
Otherwise, these flags are identical to other global event flags.
Event flags are used for communication between tasks.
See the
RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual for further
information.

6-51

PROGRAM DEVELOPMENT

SET GROUPFLAGS
6.4.1

SET GROUPFLAGS

SET GROUPFLAGS creates and deletes group global
event
flags.
Privileged users can create and delete group global event flags for
any group.
Nonprivileged users can create and delete global event
flags for the group of which they are members.

Format
SET GROUPFLAGS[/qualifier]
Flag? n
SET GROUPFLAGS:n[/qualifier]

Command Qualifiers
/CREATE
/DELETE

Command Qualifiers
/CREATE
Specifies that you wish to create a set of group global
flags.
This is the default and need not be specified.

event

The argument n is the group with which the flags are associated.
Nonprivileged users can create and delete group global event
flags for their own login group.
Privileged users can create and
delete group global event flags without restriction.
/DELETE
Specifies that you wish to delete a set of group global event
flags.
The argument n
is the group with which the flags are
associated.

Example
$ SHOW GROUPFLAGS (8ITJ
0
000000
7
200
0
000000
$
$ SET GROUPFLAG (8ITJ
Flag? 303 ~
$

$ SHOW GROUPFLAG ~
0
000000
7
200
0
000000
0
000000
303
In this example, the user first displayed all the current group
global event flags on the system and found that there were two
sets but none for the user's group, which was 303. Then the user
created a set of group global event flags for his group and
verified their presence with the SHOW GROUPFLAGS command.

6-52

PROGRAM DEVELOPMENT

SHOW GROUPFLAGS
6.4.2

SHOW GROUPFLAGS

SHOW GROUPFLAGS displays the group global event flags currently in the
system.
Format
SHOW GROUPFLAGS
Example
$ SHOW GROUPFLAGS (BIT)

200
201

303
333

1
1
1

000000
000000
000000
000000
000000

This example shows the display from SHOW GROUPFLAGS.
The first
column is the group number with which the flags are associated.
The second column is the access count. The two 6-digit numbers
are the octal words that give the current state of each group
global event flag.
Group global event flags are flags 65 through 96. The first word
starts at flag 80 and goes right to flag 65. The second word
starts at flag 96 and goes right to flag 81. The final column is
reserved for the' delete flag DEL, which means the group global
event flags are marked for delete and are not available. See the
previous section.

6-53

CHAPTER 7

RUNNING TASKS

The task is the fundamental executable programming unit.
Tasks are built (linked) from one or more object modules.
Tasks on
RSX-llM systems include tasks built from user programs as well as
system tasks, such as compilers or utilities.
Commands described in this chapter are used to initiate and
execution of tasks and to display the status of tasks.

7.1

terminate

TASK INSTALLATION AND EXECUTION

Tasks cannot execute unless they are installed in the system.
The
System Task Directory (STD), a data structure in the Executive's
dynamic storage region (pool), is the list of installed tasks.
Each
installed task is identified by a Task Control Block (TCB) in the STD.
You can display the contents of the STD with SHOW TASKS/INSTALLED.
See Section 7.12.3.2.
Nonprivileged users can install their own tasks through the RUN
command.
These tasks remain installed as long as they are executing,
and are removed from the system when they finish.
Privileged users
can install tasks. These tasks can also be caused to execute with the
RUN command. The tasks remain installed after execution.
Many system tasks can be caused to execute with other commands.
For
instance, EDIT/EDT causes EDT, DIGITAL's interactive editor, to
execute on your terminal, and LINK causes the Task Builder to execute.
Installed tasks are not necessarily resident in memory or competing
for system resources. Most installed tasks are dormant, meaning they
are installed but have not been requested to run. A dormant task uses
little memory, yet it is immediately available when it is needed, such
as to service a real-time event.
Installed tasks can be in either of two states:
Dormant

Installed but not requested to run

Active

Installed and requested to run

Tasks remain active until they abort, exit, or terminate in some other
way. During this time, they can be in one of two substates:
Ready-to-run

Competing for CPU time on the basis of priority

Blocked

Unable to compete for CPU time either because a
needed
resource
is
not
available,
or for
synchronization purposes, or through the STOP/BLOCK
command (Section 7.6).
7-1

RUNNING TASKS
You can display the list of active tasks with SHOW TASKS/ACTIVE.
Section 7.12.3.1.

See

Tasks run at priorities from 1 through 250, with 250 being the highest
priority. The priority of a task can be established through the LINK,
INSTALL, or RUN commands. Nonprivileged users are limited to priority
50 in the commands they issue, but if a privileged user has built or
installed the task to run at a higher priority, then it will run at
that priority for both privileged and nonprivileged users.
Tasks can be
built,
installed,
or
run
as
checkpointable.
Checkpointable tasks are liable to being checkpointed, or rolled out
of memory to disks, in an incomplete state if a higher-priority task
needs the memory space they are occupying.
All memory is divided into partitions, which are subdivisions devoted
to a particular task or tasks or to system functions.
Partitions can
be dedicated to a single task or shared by several tasks.
If you do
not specify a partition when you install and run a task, it will be
installed in the default partition, named GEN. All partitions have a
name and a size.
Refer to the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual for more
information on how tasks are built, installed, and run in partitions.

7.1.1

Task Naming

Tasks are installed under names from one through six Radix-SO
characters. The names identify the task in the STD. All commands and
other operations affecting installed tasks require you to use the name
of the installed task. This section describes a number of ways tasks
acquire their installed names.
Many task names include the number of the terminal from which the task
was initiated. Terminal numbers are octal.
Unless otherwise stated,
all commands in examples in this section are assumed to have been
issued from terminal TTlO:.
Tasks resulting from system commands are named after the command and
the terminal from which the command was issued.
Thus, the following
command, issued from terminal TTlO:

$ SHOW TIME lliIT)
results in a task named SHOTlO in the STD while the task is executing.
And, the following command, passed through
number 6:

DECnet

host

terminal

SHOW TIME
results in a task name SHOH6 while the task
terminal is a DECnet virtual terminal.)

executing.

host

For tasks that are installed and run explicitly,
task names can be
established through the LINK command, the INSTALL command, and the RUN
command. For example, if you begin with a source file named ROBOT.MAC
and use the default LINK command after assembling the object file, you
will end up with a task image file named ROBOT.TSK. You can install
this task image in two ways, through the privileged INSTALL command or
through the nonprivileged RUN command.
·

7-2

RUNNING TASKS
If you issue the following privileged command:

$ INSTALL ROBOT. TSK 00)
you will find the task name ROBOT in the STD.
If you issue the following command:

$ RUN ROBOT. TSK illD)
you will find the task name TTlO in the STD while the task is
executing.
The installation is through the install-run-remove form of
RUN, which assigns a task name based on the name of the terminal from
which the command was issued.
You can override these defaults at every step.
The TASK= option of LINK permits you to specify the name under which
you wish the task image file you are creating to be installed.
If you
thus specify the installed name of ROBOTl.TSK to be EANDO when you
build the task, the following privileged command:

$ INSTALL ROBOTl.TSK

(BTIJ

results in the task name EANDO in the STD.
If, however, you issue the following command:

$ RUN ROBOTl.TSK (BTIJ
you will again find the task name TTlO in the STD while the task
executing, despite the specification of EANDO at task build time.

The following command:

$ RUN/TASK_NAME:EANDO ROBOTl.TSK

(BTIJ

results in the task name EANDO in the STD while the task is executing.
The RUN command defaults to a task name that is based on the terminal
designation
(without the colon).
Therefore, you must use the
/TASK_NAME qualifier if you want to use the RUN command to initiate
execution of more than one task at a time from the same terminal.
This is true because all task names in the STD are unique; you cannot
have two tasks named TTlO installed at the same time, for example.
See the examples in Section 7.2.
Finally, most DCL and MCR commands
work by running tasks, although you do not have to issue a RUN
command. The LINK command, for instance, runs the Task Builder. Such
tasks are named after the first three letters of the command word,
plus the terminal identifier. Thus, when you issue a command such as
the following:

$ LINK RUMBLE

illD)

the result is a task named LINTlO.
In fact, the RUN command
results in the brief existence of a task named RUNTlO.

itself

If you are running a utility, using a command in the following form:

$ MCR PIP (BTIJ
your task will have a name of the form PIPTlO.
See Section 7.2 for more information on including the dollar-sign
in a RUN command.

7-3

($)

RUNNING TASKS
On RSX-llM systems, there is a possibility of a slight variation in
the task-naming rules. If, when you run a utility, you are the only
user using that utility, the utility is installed under its prototype
name, which has a name preceded by three dots, such as ••• PIP. Any
subsequent users run the utility under a name in the form PIPTlO.
It
makes no difference to you whether you are running the prototype or a
copy.
Only uninstalled tasks initiated with the RUN command have task names
preceded by TT, or HT.
Tasks initiated by other DCL commands are
named after the first three letters of the command that initiated the
task, plus a T or H {for physical, or DECnet host terminal) plus the
unit number.

7-4

RUNNING TASKS

RUN
7.2

INTRODUCTION TO THE RON COMMAND

RUN initiates the execution of a task.
four ways:

This command can

used

To install, run, and remove upon execution a task from a task
image file stored in a user's UFO.
This is the most common
use of the command.

To install, run, and remove after execution
task image file stored in the system UFO.

To run immediately
privileged user.

To run at some future time, or according to a
task previously installed by a privileged user.

These functions
paragraphs.

are

introduced

task

previously

detail

task

from

installed

schedule,

the

following

The first and most common use of RUN is to initiate execution of tasks
contained in task image files.
The following command:

$ RUN PUPPET. TSK IBtl)
directs the operating system to look in the default UFO on the default
device for a
task image file named PUPPET.TSK. When the file is
found, the image is read in to memory and execution commences.
When
the task has executed, the image is removed from memory and from the
STD.
Whenever a RUN command includes any element of a
file
this procedure is followed.
The following command:

$ RUN DBO:MUPPET

specification,

IBtl)

directs the operating system to do the following:
•

Look in the default directory on device DBO:
MUPPET.TSK.

for a file named

•

Install and run the task image.

•

Remove the task image when it has completed execution.

The default file type in this case is .TSK, which is also the
file type for a task image file created by the Task Builder.

default

The second use of RUN is to initiate execution of tasks contained in
task image files in a system directory. The dollar sign ($) in a file
specification indicates that you want to use this form of RUN.
The
purpose of this convention is to relieve you of the necessity of
knowing exactly where on the system various system tasks are stored.

7-5

RUNNING TASKS

RUN (Cont.)
Simply include the dollar sign ($) in your RUN command and the
takes over. If you receive the following error message:

system

RUN -- File not found
or
INS -- File not found
your system manager has chosen not to include that particular task or
utility in this directory, perhaps to conserve disk space.
In this
case, see your system manager.
In general, you can use the dollar sign to run most system tasks and
utilities.
These usually have 3-letter names like PIP or TKB, but the
RMS-11 utilities have 6-letter names like RMSDSP or RMSCNV.
See the
RMS-11 documentation supplied with your system for more information on
RMS-11.
(Your system manager may also have added other task image
files not supplied by DIGITAL to this directory for your convenience.)
On RSX-llM systems, copies of many or all system tasks are placed in
the system directory on pseudo device LB:.
The directory is usually
[1,54], but it can be some other number. You can display the identity
of this directory with the command SHOW SYSTEM/DIRECTORY. You can
list the contents of the directory with a DIRECTORY command.
The system responds to the dollar sign ($) in a file specification
follows.
The following command:
$ RUN $TKB

(ffi)

directs the operating system to do the following:
•

Look for a file called TKB.TSK.

•

Install and run the task image.

•

Remove the task image when it has completed execution.

Because the Task Builder is a privileged task, it will be found in the
system directory.
The system installs, runs, and removes TKB just
like any other task.
NOTE
Privileged users can also use the dollar sign ($) with
the INSTALL command. See Section 7.8.
The third use of RUN is to execute immediately a previously installed
task.
The task must have been installed by a privileged user. The
following command:

$ RUN TURTLE (ffi)
directs the operating system to look in the list of installed tasks
(STD)
for a
task named TURTLE.
Once the system has found the task
TURTLE in the STD, the task commences its execution.
The task need
not be installed since it is already installed, nor is it removed when
it has completed its execution. The task runs under the name TURTLE,
not TTlO.
7-6

RUNNING TASKS

RUN (Cont.)
(If the system does not find an installed task of the name you give,
the command defaults to the install-run-remove form and looks in the
default UFD on the default device for a file named TURTLE.TSK, and
continues as described earlier.)
Finally, privileged users can use RUN to schedule the execution
task in several forms.
Scheduling options include:

•

Run the installed task after so many hours, minutes,
or ticks.

seconds,

•

Run the installed task at an absolute time of day.

•

Run the installed task in synchronization with the next hour,
minute, second, or tick, that is, at the beginning of the next
interval.

•

Run the installed task at regular intervals.

In addition, these scheduling options can be combined.
RUN as used to install, run, and remove tasks contained in task image
files is described in Section 7.2.1. RUN as used with previously
installed tasks is described in Section 7.2.2.

7.2.1

Running Tasks Contained in Task Image Files

When used to run an uninstalled task, RUN is actually a combination
command, encompassing INSTALL, RUN, and REMOVE.
This command is the
only way a nonprivileged user can install or remove a task.
Format
RUN[/qualifier[s]]
Task? [$]filespec
RUN[/qualifier[s]]

[$]filespec

Command Qualifiers
/[NO]CHECKPOINT
/COMMAND:"taskcommand"
/EXT ENS ION: n
/ [NO] IO PAGE
/PARTITION:parname
/[NO]POSTMORTEM
/PRIORITY: n
/[NO]SLAVE
/STATUS:arg
TASK
COMMAND
/TASK NAME:taskname
/UIC:[g,m]

7-7

RUNNING TASKS

RUN (Cont.)
Parameter
[$] filespec

Specifies a task image file on a mounted Files-11 volume.
This
task is installed, run, and then removed when it has finished
executing.
The default file type is .TSK.

See the Notes.

The dollar sign ($) directs the system to search first for the
file in the system directory.
In this case, the dollar sign
specifies a device and directory and thus counts as an element of
a file specification.

Command Qualifiers
These qualifiers establish how the
installed.

uninstalled

task

/[NO]CHECKPOINT
Specifies whether or not the task is to be run checkpointable.
The default is established when the task is built (linked).
This
qualifier is used to override the default.
In other words, this qualifier allows you to
tasks as noncheckpointable and vice versa.

run

checkpointable

/COMMAND:"taskcommand"
Passes the specified command line to the task you are running.
The command must begin with the task's acronym and it must be
valid for the task or a syntax error will occur.
Also,
the
command must be inside the quotation marks (") and not more than
40 characters long. For example, the following command:

$ RUN/COMMAND:"PIP /LI" $PIP

IBDJ

runs PIP and then passes the /LI switch to it.
directory listing.

This results in a

When the task has finished executing the command line,
is removed.

the

task

space

/EXTENSION:n
Specifies that n additional decimal words
allocated to a task.

address

/[NO]IO_PAGE
Specifies that a privileged task can overmap the I/O page.
If
you specify /IO PAGE, RUN assumes that the task will overmap the
I/O page and, if-the task is larger than SK words,
issues a
warning message.
If you specify /NOIO_PAGE, RUN assumes that the
task does not need to use the I/O page; no warning message is
issued.
The default is /IO_PAGE.

7-8

RUNNING TASKS

RUN (Cont.)
/PARTITION:parname
Specifies the partition in which the task is to run. The default
is established when the task is built (linked). This qualifier
is used to override the default.
If no partition is established at task build or with the
command, the task will run in the default partition GEN.

RUN

/[NO]POSTMORTEM
Specifies whether or not a Postmortem Dump is to be generated
the task terminates unexpectedly.

The default is determined when the task is built.
If not
specified,
the LINK command defaults to /NOPOSTMORTEM. See the
RSX-llM/M-PLUS and Micro/RSX Task Builder Manual for
more
information on Postmortem Dumps.
/PRIORITY: n
Specifies at what priority the task is to run.
This is a
privileged qualifier.
The default is established when the task
is built (linked).
This qualifier is used to override the
default.
The default priority for the Task Builder, INSTALL, and RUN is 50
(decimal).
If a task has been built or installed at another
priority, nonprivileged users can run it at that priority.
Otherwise, nonprivileged users are limited to running tasks at
the default priority.
Priorities range from 1 through 250 (decimal).
/[NO]SLAVE
Specifies the slave status of a task.
If you specify /SLAVE,
data sent to the installed task is marked with the TI: of the
sending task. When the installed task receives the data,
the
system sets the task's TI:
to that associated with the data.
This qualifier overrides the LINK qualifier /SLAVE specified when
the task was built. The default is specifed at task-build time.
/STATUS:arg
TASK
COMMAND
Specifies whether exit status is to be returned from the
command or from the task being run with the RUN command.
default is /STATUS:COMMAND and need not be specified.

RUN
The

The /STATUS:TASK qualifier may be necessary in indirect command
files that run installed tasks where the indirect command
processor must wait for the installed task to exit before
attempting to execute the next command.

7-9

RUNNING TASKS

RUN (Cont.)
/TASK_NAME:taskname
Specifies the name under which the task is to be run.
The
default is to run the task under a name derived from the name of
the terminal from which the RUN command was issued, as discussed
in Section 7.1.1.
Use this qualifier when you wish to run two tasks simultaneously
using the RUN command. Otherwise, the second RUN command causes
the following error message to appear on your terminal:
RUN -- Task name already in use
See the examples.
Task names are restricted to six Radix-50 characters.
The
Radix-50 character set consists of the 26 uppercase letters, the
10 numerals, the period (.), and the dollar sign ($).
/UIC: [g ,m]
Specifies the default UIC for the task.
This is a privileged
qualifier.
This UIC determines in what protection class the task
belongs, and thus determines file access.
The square brackets are required syntax.
Examples

$ RUN ID
Task? ROBOT

This example installs,
runs, and removes upon completion of
execution the task contained in the task
image file named
ROBOT.TSK from the default directory on the default device.

$ RUN ROBOT ID
$ RUN ROBOT. TSK ID
The two commands in this example are the equivalent of the
command in the previous example, assuming there is no installed
task named ROBOT.
If there is, only the second form, with the
file type specified, will run the task from the directory.
The following examples illustrate the task-naming convention.
See Section 7.1.1 for more information on task naming.

$ RUN/TASK_NAME:CAPEK ROBOT

$ SHOW TASKS/ACT I VE ID
MCR •••
SHOTlO
CAPEK
This example shows how the task-naming convention can
be
overridden for the RUN command by running the task under another
name using the /TASK_NAME qualifier.

7-10

RUNNING TASKS

RUN {Cont.)
$ RUN ROBOT ffiTI)
$ SHOW TASKS/ACTIVE ffiTI)
MCR •••
SHOTlO
TTlO
$ RUN ASIMOV ffiTI)
RUN -- Task name already in use
$ RUN/TASK:BINDER ASIMOV ffiTI)
$ SHOW TASKS/ACTIVE 00)
MCR •••
SHOTlO:
TTlO
BINDER

This example shows how you can run two tasks simultaneously using
the RUN command and the /TASK_NAME qualifier.

Notes
The return of the dollar sign prompt ($) signifies that the task
initiated by the RUN command has exited.
However, you need not
wait for the prompt to return to issue another command.
Simply
press RETURN or CTRL/C and enter the command.
If you specified
the /STATUS:COMMAND qualifier, the dollar sign prompt returns
immediately after you issue a RUN command for an uninstalled
task, but does not indicate that the task has completed its
execution.
This section describes RUN as it works with any portion of a file
specification included.
In general, you do not have to include
the file type, as .TSK is the default.
In one
unusual
circumstance, however, you must explicitly enter a file type.
If
there is a task already installed in the system that has the same
task name as the file name of the task image file containing the
task you wish to run, the RUN command will run the installed task
instead of the one you wish to run.
In such an instance, you
must include the file type or some other part of the file
specification, and include the dollar sign, to force the RUN
command to access the task image file.
Some error messages resulting from RUN are labeled INS rather
than RUN because this form of RUN installs the task automatically
and the error occurs during the installation.

7.2.2

Running and Scheduling Installed Tasks

RUN also initiates the execution of installed tasks.
Privileged users
can use RUN to initiate the execution of installed tasks on a schedule
by creating entries in the system clock queue.
Tasks that run as a result of entries in the clock queue run with
pseudo device COO: as their TI:.
For this reason, these commands are
privileged. Such tasks send output to COO: and not to the terminal
they were run from.

7-11

RUNNING TASKS

RUN (Cont.)
Format
RUN[/qualifier[s]]
Task? taskname
RUN[/qualifier[s]] taskname
Command Qualifiers
/DELAY:nu
/INTERVAL:nu
/SCHEDULE:hh:mm:ss
/STATUS:arg
COMMAND
TASK
/SYNCHRONIZE:u
/UIC: [g ,m]
Parameter
task name
Specifies the name of the installed task to be run. The names of
installed tasks are one through six Radix-SO characters.
If the
System Task Directory (STD) contains no entry under the task name
you supply, the system searches the default directory on the
default device for a file named taskname.TSK.
If RUN finds such
a file, it installs, runs, and removes it.
Command Qualifiers
The time-oriented qualifiers to RUN create entries in the system
clock queue.
The contents of the clock queue can be displayed
with the command SHOW CLOCK_QUEUE. See Section 7.12.5.
/DELAY:nu
Specifies that the task be run after the stated amount of time
passes.
This qualifier is privileged. The argument nu specifies
the amount of the delay as a number of units.
n is the number of
units and u is the time unit as follows:
T S MH -

Ticks
Seconds
Minutes
Hours

If your system has the standard line-frequency clock, the length
of a tick depends on the line frequency of the electric power
source serving your location. Most commonly, this frequency is
60 Hz, which results in a tick length of l/60th of a second.
If your system has an optional programmable clock, the length of
a tick depends on the choice made at system-generation time. See
your system manager for more information.
Acceptable values for these units are as follows:
T - Any positive value to a maximum of 15 bits, or 32767.

s - Any positive value to a maximum of 15 bits, or 32767~
7-12

RUNNING TASKS

RUN (Cont.)
M - The maximum value is 1440.
H - The maximum value is 24.
The system always waits at least one interval.
the system treats it as a 1.

If you specify 0,

/INTERVAL:nu
Specifies that the task is to be run at regular intervals.
This
qualifier is privileged. The argument nu specifies the interval
as a number of units of time. n is the number of units, and u is
the unit as follows:
T S MH -

Ticks
Seconds
Minutes
Hours

See the /DELAY qualifier for
units.

detailed

description

these

Specifies that the task be run at a particular time of day.
is a privileged qualifier.

This

/SCHEDULE:hh:mm:ss

/STATUS:arg
COMMAND
TASK
Specifies whether exit status is to be returned from the RUN
command or from the installed task being run with the RUN
command. This is not a privileged qualifier.
The default is
/STATUS:COMMAND and need not be specified.
The /STATUS:TASK qualifier may be necessary in indirect command
files that run installed tasks, where the indirect command
processor must wait for the installed task to exit before
attempting to execute the next command.
This qualifier can be
qualifier.

specified

separately

with

the

/UIC

/SYNCHRONIZE:u
Specifies that the execution of the task be synchronized on the
next occurrence of a particular clock unit. This is a privileged
qualifier. The argument u is the time unit as follows:
T S M H -

Ticks
Seconds
Minutes
Hours

See the /DELAY qualifier for
units.

7-13

detailed

description

these

RUNNING TASKS

RUN .(Cont.)
/UIC: [g ,m]
Specifies the default UIC for the task.
This is a privileged
qualifier.
The task's UIC determines what file-protection class
it belongs in and thus directly influences file access.
The square brackets are required syntax.
Examples
$ RUN/DELAY:SS PINBAL

(Bf]

This example initiates execution of the installed
five seconds after the command is entered.
$ RUN/INTERVAL: 20M WIZARD

task

PINBAL

task

WIZARD

task

TOMMY

(Bf]

This example initiates execution of the installed
immediately and every 20 minutes thereafter.
$ RUN/DELAY:lOM/INTERVAL:lH TOMMY (Bf]

This example initiates execution of the installed
after ten minutes and every hour thereafter.
$ RUN/SCHEDULE: 12: 00: 00 NOON (Bf]

This example initiates execution of the installed task NOON at
the next 12:00:00 after the command is entered. If you entered
the command before noon today, NOON would run at noon today.
If
you entered the command after noon today, NOON would run at noon
tomorrow.
$ RUN/SYNCHRONIZE:H BOGUS

(Bf]

This example initiates execution of the installed task named
BOGUS on the next hour.
If you entered the command at 9:15,
BOGUS would begin running at 10:00:00.
$ RUN/SYNCHRONIZE:H/INTERVAL:lH BELTOL

This example initiates execution of the installed task named
BELTOL every hour on the hour, starting with the next hour.
Notes
The dollar sign prompt ($) prompt returns immediately after you
issue a RUN command for an installed task and does not indicate
that the task has completed its execution.
You can display entries in the clock queue with SHOW CLOCK_QUEUE,
Section 7.12.S.
The clock queue is kept in pool and must be restored whenever the
system is rebooted.

7-14

RONNING TASKS

RUN (Cont.)
Error Message
RUN -- Invalid time parameter
Explanation:

Command specified an invalid time argument.

User Action:

Check for proper syntax and reenter command.

7-15

RUNNING TASKS

ABORT
7.3

ABORT

ABORT forces an orderly end to a running task or to the
specific command.

action

Tasks can also be aborted by other tasks or by error-handling
routines.
If this happens, some of the messages discussed below can
appear on your terminal without your having issued an ABORT command.
Nonprivileged users can abort any task
users can abort any task.

running

TI:.

Privileged

Format
ABORT[/COMMAND] [/qualifier[s]] commandname
ABORT/TASK[/qualifier[s]]

[taskname]

Command Qualifiers
/COMMAND
/TASK
/[NO]POSTMORTEM
Parameters
The parameters differ depending on whether you are aborting a
command or a task. The default is to abort a command. See the
examples.
commanqname
Specifies the command whose effect you wish to cancel.
This
parameter can be used only when the /TASK qualifier is not
present. You must specify at least the first three characters of
the command verb.
task name
Specifies the name of the task you wish to abort. This parameter
requires the presence of the /TASK qualifier.
If you use the
/TASK qualifier and do not specify a task name, you will get an
error message, "Illegal task name."
Command Qualifiers
/COMMAND
Specifies that you wish to abort a command.
qualifier and need not be included.

This is the

default

/[NO]POSTMORTEM
Specifies that a Postmortem Dump be taken (or not taken)
of the
task before it is aborted. See the RSX-llM/M-PLUS and Micro/RSX
Task Builder Manual for more information.

7-16

RUNNING TASKS

ABORT (Cont.)
If the task is memory-resident, the contents of its registers are
listed on the terminal.
If it is checkpointed, no register
contents are listed.
You can specify a Postmortem Dump when you build a task or when
you install it (including install-run-remove). The default for
this qualifier is determined by previous specification of the
/DUMP qualifier.
If no /POSTMORTEM qualifier has been specified,
the default is /NOPOSTMORTEM.
/TASK
Specifies that you want to abort a task by

nam~.

Examples
$ ABO RUN ID
11:11:11 Task "TTlO" terminated
Aborted via directive OR CLI

This example aborts a task initiated with the RUN command running
on your terminal. See next example.
$ RUN TREK ID
ORDERS: STAR DATE = 2000
YOU MUST DESTROY THE KLINGON INVASION FORCES OF 29 BATTLE
CRUISERS. YOU HAVE 40 SOLAR YEARS TO COMPLETE YOUR MISSION.
READY? (CTRL/C)
DCL>ABORT RUN ID
12:11:09 Task "TTlO" terminated
Aborted via directive or CLI

In this example, the user installed the interactive task TREK by
means of a RUN command. Then, instead of providing the task with
requested input, the user issued a CTRL/C to return to the DCL
monitor level and then issued the ABORT command. DCL prompted
for the command to be aborted and RUN was specified.
The task
was aborted and removed, and the message displayed. The message
mentions MCR because DCL does not actually perform the abort.
$ ABORT/TASK MACT3 ID

This example aborts the task named MACT3.
Nonprivileged users
can abort tasks running on their own terminals. Privileged users
can abort tasks by name running on any terminal.
See next
example.

7-17

RUNNING TASKS

ABORT (Cont.)
$ DIRECTORY *. RNO IB.U)
Directory DB2: [303,5]
20-MAR-85 16:28
ALTCLI.RN0;3
213.
27-AUG-84 16:52
ANNI.RN0;6
3.
30-JUL-84 09:30
APRCOM.RN0;4
9.
15-FEB-85 10:35
BEST.RNO;S
40.
28-AUG-84 15:50
CATCH.RN0;4
7.
12-MAR-85 09:39
CHAP11SMG.RNO;l3
49.
13-0CT-84 16:36
CHAP12SMG.RNO;Sl
223.
08-0CT-84 13:15
CHARSET.RN0;5
6.
15-JAN-85 11 : 5 7 (CTRL/C)
DCL>ABORT DIRECTORY IB.U)
16:29:45 Task "DIRT56" terminated
Aborted via directive or CLI
$
In this example, the user issued a DIRECTORY command and soon saw
that the file he was checking for was present. Rather than wait
for the directory listing to complete, the user typed CTRL/C and
entered the ABORT command in response to the dollar sign ($)
prompt. The ABORT command defaults to ABORT/COMMAND.

$ ABORT/DUMP RUN IB.U)
14:41:11 Task "TTlO " terminated
Aborted via directive or CLI
RO=OOOOOO
Rl=l00077
R2=135600
R3=000000
R4=000000
R5=000000
SP=012540
PS=l70017
$
In this example, the user requested a Postmortem Dump.
The
contents of the task's registers at the time of the abort are
listed on the terminal along with notification of the dump.
The
dump file will be printed on the system's line printer.
Notes
A is the short form of ABORT.
ABORT forces an orderly termination of a task.
termination, the system performs four steps:
1.

effect

the

Alters the task's priority to 247. A task must be memory
resident to be aborted. This step usually forces the quick
return of a checkpointed task.

7-18

RUNNING TASKS

ABORT (Cont.)

Performs I/O rundown:
cancels I/O for nonfile-structured
devices;
completes I/O for file-structured devices and
deaccesses files; detaches all attached,devices.

Executes the Task Termination Notification program
which displays messages on the aborted task's TI:.

Releases any memory allocated to the task if the task is
fixed.

(TKTN),
not

The TKTN routine can list a number of messages about
These messages are explained below.

the

abort.

LOGOUT also
terminal.

from

your

aborts

nonprivileged

tasks

running

Tasks can also be aborted by Executive directives issued by other
tasks, in particular, by error-handling routines.
TKTN Messages
These messages appear as part of the notification of the abort.
Often
a
list
of
register
contents also is displayed.
Understanding these messages requires an understanding of how the
PDP-11 executes instructions.
If you receive these messages and
do not understand them, you should copy them, along with any
other terminal output, and show them to your system manager.
Aborted via directive or CLI
Explanation: Either a CLI or an Executive directive
another task caused the task to be aborted.

issued

the

AST

AST abort. Bad stack
Explanation: An AST could not be effected
parameters could not be pushed on the stack.

because

Checkpoint failure. Read error
Explanation: The task could not be read back into
being checkpointed.

memory

after

IOT execution
Explanation: The task executed an IOT instruction,
routine was specified to process the trap.

and

SST

Load failure. Read error
Explanation:
error.

The task could not be loaded because of a

hardware

Memory protect violation
Explanation: The task encountered a memory-protect violation and
no SST routine was specified to process the trap.

7-19

RUNNING TASKS

ABORT (Cont.)
Non RSX EMT execution
Explanation: The task executed an EMT instruction with an
argument other than 377(octal) or, in the case of a privileged
task switching to system state, 376(octal), and no SST routine
was specified to process the trap.
Odd address or other trap four
Explanation: The task executed a word instruction with an odd
address, or it referenced a nonexistent memory location, and no
SST routine was specified to process the trap.
Parity error
Explanation: A parity error occurred while the
task
was
executing.
The task was fixed in memory so that the memory could
not be reused by another task.
Reserved INST instruction
Explanation: The task executed an illegal instruction,
SST routine was specified to process the trap.

and

the

SST

SST abort. Bad stack
Explanation: An SST could not be effected because
parameters could not be pushed onto the task's stack.
Task exit with outstanding IO
Explanation: The task exited with one or more outstanding I/O
requests.
Tasks should terminate all I/O operations before
exiting. The system does, however, clean up all outstanding I/O.
T bit trap or BPT instruction
Explanation: The task either set the T bit in the Processor
Status Word or executed a BPT instruction, and no SST routine was
specified to process the trap.
Trap execution
Explanation: The task executed a Trap instruction,
routine was specified to process the trap.

and

SST

Error Messages
ABO -- Task marked for abort
Explanation: A previous command requested that the task be
aborted, but the abort has not yet completed. This may mean the
task marked for abort is not currently resident in memory.
Oser Action:

None.

ABO -- Task not active
Explanation:

The specified task is not currently active.

Oser Action:

Check command for proper task name and reenter it.
7-20

RUNNING TASKS

CONTINUE
7.4

CONTINUE

CONTINUE resumes execution of a previously suspended task.
Nonprivileged users can continue tasks initiated from their
terminals. Privileged users can continue any suspended task.

own

Format
CONTINUE [taskname]
Parameter
If you do not supply a parameter, the task running
terminal initiated by the RUN command is continued.

your

Tasks are suspended through the execution of a SPND$S directive
within the task. A RSUM$ directive is another way of continuing
a suspended task.
taskname
Specifies the suspended task you want to continue. If you do not
specify a task name,
the default is a task named after the
terminal.
Example
$ RUN YOYO

llitlJ

"Message from Yoyo: Yoyo is suspended"
$ SHOW TASK/ACTIVE TTlO ffiDJ
TTlO
070530 GEN
00677100-00701600 PRI - 50. DPRI - 50.
STATUS:
-CHK SPN -PMD REM MCR
TI - TTlO:
IOC - 0. EFLG 000001 000000 PS 170000 PC 001254
REGS 0-6 001372 000037 000012 140311 001254
$ CONTINUE ffi)
"Message from Yoyo: Not suspended. Climbing string"
$
In this example, the user ran a task that issues a message and
then suspends itself.
Not all suspended tasks issue such
messages, but you can identify a suspended task through SHOW
TASKS/ACTIVE.
The user issued SHOW TASKS/ACTIVE and named the
task.
Included in the listing under STATUS on the second line
the mnemonic SPN verifies that the task was suspended. The user
issued CONTINUE without naming the task.
Since the task was
initiated by RUN, CONTINUE defaulted to a task name based on the
name of the terminal.
Notes
A task cannot suspend any task other than itself.
For more information on task states, see the
Micro/RSX Executive Reference Manual.

7-21

RSX-llM/M-PLUS

and

RUNNING TASKS

CONTINUE (Cont.)
Error Message
CON -- Task not suspended
Explanation:

Command attempted to continue an unsuspended task.

User Action:

None.

7-22

RONNING TASKS

CANCEL
7.5

CANCEL

CANCEL eliminates entries from the clock queue. Entries are placed in
the clock queue through the RUN$ directive or from the privileged
time-based forms of the RUN command.
Nonprivileged users can only cancel entries from a task initiated from
the entering terminal.
Privileged users can cancel any clock queue
entries.
CANCEL does not affect a currently
pending entries in the clock queue.

executing

task,

but

only

the

Format
CANCEL
Task? taskname
CANCEL taskname

Parameter
task name
Specifies the name of the installed
entries you wish to eliminate.

task

whose

clock-queue

Example
$ RUN/DELAY: SM ARDVRK (BTIJ
$ SHOW CLOCK_QUEUE (BTIJ
ARDVRK Scheduled at 17-APR-85 10:44:31:09
$ CANCEL ARDVRK (BTIJ
$ SHOW CLOCK_QUEUE (BTIJ
$
In this example, the user issued a command to run the installed
task ARDVRK at exactly five minutes from when the command was
entered. The user verified that ARDVRK was in the clock queue
(as the only entry). Then the user issued the CANCEL command to
eliminate the scheduled run of ARDVRK. The user issued a second
SHOW CLOCK QUEUE to verify that the scheduled entry was cleared.
If ARDVRK had been running at the time, the CANCEL would have had
no effect.

Notes
See Section 7.12.5 for information on SHOW CLOCK_QUEUE.

7-23

RUNNING TASKS

STOP/BLOCK
7.6

STOP/BLOCK

STOP/BLOCK blocks an installed running task.
The task no longer
executes or pompetes for memory.
Nonprivileged users can block tasks
running from their own terminals.
Privileged users can block any
task.
Format
STOP/BLOCK [taskname]
Parameter
task name
Names the task to be blocked.
If you do not name a task,
the
task initiated with the RUN command and named after the terminal
is blocked.
Example
$ RUN ADVENT (8@
$ SHO TASK/ACTIVE (8@
MCR •••
SHOTS
TTS
$ STOP /BLOCK (8@
$ SHOW TASK:TTS/FULL
TTS
100604
GEN
073464 OOS41000-00S436 PRI - SO. DPRI 50.
STATUS: BLK -CHK WFR -PMD REM MCR
TI - TTS:
IOC - O. BIO - O. EFLG - 000001 000000 PS - 170000
PC - 002206 REGS 0-6 001637 040066 040060 140311 163SOO 000000 0012S2
$
$ START/UNBLOCK 00)
$ SHOW TASK:TT5/FULL
TTS
100604
GEN
073464 OOS41000-005436 PR! - SO. DPRI - 50.
STATUS: -CHK WFR -PMD REM MCR
TI - TTS:
IOC - 1. BIO - O. EFLG - 000001 000000 PS - 170000
PC - 002206 REGS 0-6 006173 042066 040060 140311 163500 000000 001260

In this example, the user on terminal TTS: ran a task with the
RUN command, giving the task the name TTS by default. The user
then issued the STOP/BLOCK command, without naming the task.
The
/FULL display from SHOW TASKS shows task TTS's status as blocked
(BLK flag) • Then the user issued the START/UNBLOCK command and
checked the status again.
This time, the BLK flag is not
present.
Notes
The START/UNBLOCK and ABORT commands
canceling the STOP/BLOCK command.

are

the

only

means

A blocked task has an effective priority of O.
If it is
checkpointable, any task can checkpoint it. Once checkpointed,
the blocked task stays checkpointed because it is ineligible to
compete for memory.
A blocked, checkpointed task is unblocked
when it is aborted.

7-24

RUNNING TASKS

STOP/BLOCK (Cont.)
A task can also be blocked by the system while waiting
needed resource or for synchronization purposes.

for

some

There are no prompts from this command.
See Section 7.12.3 for an explanation of the task status flags.
There are several STOP/function commands associated with the
Queue Manager. See the RSX-llM/M-PLUS System Management Guide.

7-25

RONNING TASKS

START
7.7

START

The START command resumes execution of a task that was stopped by the
STOP$S directive. Note that starting a stopped task is different from
continuing a suspended one.
Format
START[/TERMINAL:ttnn:]

[taskname]

Parameter
task name
Specifies the name of the task you wish to start. If you do not
specify a taskname, the task running at your terminal that was
initiated by the RUN command is started, that is, a task named
after your terminal.
Command Qualifier
/TERMINAL:ttnn:
Allows a privileged user to start a stopped task that is
on some other terminal.

running

Notes
Several other forms of the start command are used to control the
Queue Manager. See the RSX-llM/M-PLUS Batch and Queue Operations
Manual and the RSX-llM/M-PLUS System Management Guide for more
information.

7-26

RUNNING TASKS

STARVUNBLOCK
7.7.1

START/UNBLOCK

START/UNBLOCK continues the execution of a task blocked by the
STOP/BLOCK command. Nonprivileged users can unblock any task running
from their own terminal. Privileged users can unblock any task.

Format
START/UNBLOCK [taskname]

Parameter
task name
Names the task to be unblocked. If you do not name a task,
the
task initiated with the RUN command and named after the terminal
is unblocked, if blocked.

Notes
See the description of STOP/BLOCK for an example.
- START/UNBLOCK does not unblock tasks blocked by the Executive
while waiting for system resources or for synchronization. You
can only unblock tasks blocked with the STOP/BLOCK command.
The START/UNBLOCK and ABORT commands
canceling the STOP/BLOCK command.

are

the

only

means

The system automatically unblocks a blocked task when the blocked
task is aborted.

7-27

RUNNING TASKS

INSTALL
7.8

INSTALL

INSTALL includes a specific task in the System
making it known to the system.

Task

Directory,

thus

An installed task is dormant until it is requested to run by the
Executive.
You can request an installed task to run through the RUN
command or through a variety of Executive directives, including RQST$
(Request), RUN$ (Run), and SPWN$ (Spawn).
This is a privileged command.
Nonprivileged users install tasks
temporarily through RUN, which includes most of the same qualifiers as
INSTALL. See Section 7.2.
Format
INSTALL[/qualifier[s]]
File(s)? [$]filespec
INSTALL [/qualifier [s]]

[$] filespec

Command Qualifiers

I [NO]CHECKPOINT
/COMMAND:"taskcommand"
/EXTENSION:n.
/[NO]INTERPRETER
/MULTIUSER PARTITION:parname
/PARITITION:parname
/[NO]POSTMORTEM
/PRIORITY: n
/READONLY COMMON
/[NO]SLAVE
/TASK NAME:taskname
/UIC:[g,m]
Parameter
[ $] f ilespec
Specifies the name of the task image file containing the task you
wish to install.
.TSK is the default file type. The dollar sign
($), if present, directs the system to search for the file in the
system
directory.
If you do not include the /TASK_NAME
qualifier, the task will be installed under a name based on the
first six characters of the file name unless another name was
assigned through the TASK= option of the Task Builder.
See the
examples.
Command Qualifiers
/[NO]CHECKPOINT
Specifies whether or not the task is to be checkpointable.
The
default is set at link time.
This qualifier overrides the
link-time checkpointability specification.

7-28

RUNNING TASKS

INSTALL (Cont.)
/COMMAND:"taskcomrnand"
Passes a command to the task you are installing.
The command
must be inside the quotation marks
(") and not more than 40
characters long. For example, the following command:

$ INSTALL/COMMAND:" /LI" $PIP

installs PIP and then passes the /LI switch to it.
in a directory listing.

This

results

/EXTENSION: n •
Specifies that n(decimal) additional words of address
to be allocated to a task.

space

are

/[NO] INTERPRETER
Specifies that the task being installed is a command line
interpreter (CLI).
You must install a CLI using the /INTERPRETER
qualifier before you can set a terminal to that CLI
(SET
TERMINAL/CLI:cliname)
or work with the CLI by means of the MCR
CLI command. The default is the /NOINTERPRETER qualifier.
/MULTIUSER_PARTITION:parname
Specifies the partition irito which the
multiuser task is to be installed.

read-only

portion

/PARTITION:parname
Specifies the partition into which the task is to be installed.
The default is set at link time.
This qualifier overrides the
link-time specification.
If you name a partition that does not exist, you receive a
warning message and the system attempts to install the task in
the default partition GEN.
/[NO]POSTMORTEM
Specifies whether or not a Postmortem Dump
(PMD)
is to be
generated if the task aborts because of an SST error condition.
The default is set at link time. This qualifier overrides the
link-time specification.
See the RSX-llM/M-PLUS and Micro/RSX
Task Builder Manual for further information.
/PRIORITY:n
Specifies the priority at which the task is to run. The default
is set at link time.
This qualifier overrides the default set at
link-time. The argument n can be from 0 through 250(decimal).
/READONLY_COMMON
Specifies that a common region is to be installed as a
common.

7-29

read-only

RUNNING TASKS

INSTALL (Cont.)
/[NO]SLAVE
Specifies whether or not the task is to be slaved.
Data sent to a slaved task is marked with the TI: of the sending
task. When the installed task receives the data, the system sets
the task's TI:
to that associated with the data. The default is
set at link time.
This qualifier overrides the link-time
specification.
Note that data may not be sent to a
virtual terminal.

slaved

task

running

/TASK_NAME:taskname
Specifies the name by which the task is to be referenced.
The
default is set at link time.
This qualifier overrides the
link-time specification. See the examples.
/UIC: [g ,m]
Specifies the default UIC for the task.
This task UIC determines
in what protection class the task belongs and thus directly
influences file access.
The brackets are required syntax.
Examples

$ INSTALL FATE

This example looks for a task image file named FATE.TSK on the
default device and in the default directory and installs it as
FATE in the STD, assuming no other name was specified at link
time.

$ INSTALL $LATE

This example looks in the system directory
(by convention,
[1,54])
for a task image file named LATE.TSK and installs it as
LATE in the STD, assuming no other name was specified at link
time.

$ INSTALL BUCKING

This example looks for a task image file named BUCKING.TSK on the
default device and in the default directory, and installs it as
BUCKIN in the STD, assuming no other name was specified at link
time.

$ INSTALL/TASK:DOOR GATE

This example looks on the default device in the default directory
for a task image file named GATE.TSK and installs it as DOOR in
the STD, overriding any task name specified at link time.

7-30

RUNNING TASKS

INSTALL (Cont.)
$ INSTALL/PARTITION: LEROY KILROY

This example installs the task image file named KILROY.TSK
partition named LEROY.

KEY~

$ INSTALL/CHECKPOINT/POSTMORTEM/PRIORITY:75/TASK:LARGO

This example looks for a task image file named KEY.TSK in the
default location and installs it in the STD under the name LARGO.
The task is installed as checkpointable and at a priority of
75(decimal).
If the task should exit unexpectedly, a Postmortem
Dump is generated.
Notes
REMOVE counteracts INSTALL.

See Section 7.9.

Tasks can also be installed through the install-run-remove form
of the RUN command. Such tasks remain installed only while they
are executing. While such tasks are installed, they are similar
to other
installed tasks.
You cannot, however, count on the
presence of a task installed through install-run-remove.
Several situations require tasks to be explicitly installed
through INSTALL.
If you wish for other tasks to be able to
communicate with the task while it is not active,
it must be
installed.
If you wish to run the task on a schedule, it must be
installed and then scheduled using the RUN command.
If a task is
commonly used, you may wish to sacrifice pool space to improve
system performance by installing the task.
You can display the attributes of installed
TASKS/INSTALLED. See Section 7.12.3.2.

tasks

with

SHOW

Explanation: Command attempted to access a common that
installed specifying a protection status that excludes you.

was

User Action: Find out why protection
fashion and proceed accordingly.

that

Error Messages
INS -- Access to common block denied

was

established

INS -- Addressing extensions not supported
Explanation: Command tried to install a
task with a VSECT
(virtual section) in a system that does not support this feature.
User Action:

None.

INS -- Base address must be on 4K boundary
Explanation:
4K boundary.

The base virtual address of the task was not

User Action:

Relink the task.

7-31

RUNNING TASKS

INSTALL (Cont.)
INS -- Can't install privileged task from non-privileged terminal
Explanation: A nonprivileged user attempted to
install
privileged task through the install-run-remove form of RUN.
User Action:
INS

None.

Checkpoint area too small
Explanation: The area allocated for checkpointing the task was
smaller than the partition into which the task was being
installed.
User Action: Allocate
more
checkpoint
DEVICE/CHECKPOINT and reenter the command.

space

using

SET

INS -- Checkpoint space too small, using checkpoint file
Explanation: Warning message.
The checkpoint space allocated in
the task image file is too small for the size of the task
(probably because of the /EXTENSION qualifier).
The system
supports
dynamic
allocation of checkpoint space and will
therefore use a checkpoint file on the volume to contain the task
if it must be checkpointed.
User Action: None necessary.
The task can be relinked with more
checkpoint space, or you can remove it and reinstall it with a
different value for /EXTENSION if you wish.
INS -- Common block not loaded common-name
Explanation: The specified common block was linked to
but had not been installed.
User Action:

the

task

Install the common block, then install the task.

INS -- Common block parameter mismatch common-name
Explanation: Parameters of a common block did not match those in
the task's label block.
User Action:

Correct the mismatch.

INS -- File not contiguous
Explanation: Command attempted to install a task
from
a
noncontiguous file.
Task images must be contained in contiguous
files.
User Action: Make sure you
Reenter the command.

have

specified

the

correct

file.

INS -- File not task image
Explanation: Command attempted to install a task from
whose label block indicated it was not a task image.
User Action: Make sure you
Reenter the command.

have

7-32

specified

the

correct

file
file.

RUNNING TASKS

INSTALL (Cont.)
INS -- Illegal device ddnn:

Explanation:

Warning
message.
The
device
specified
at
task-build time by the ASG option is not in the system.
The task
will be installed but may not execute as you wish.

User Action:

Determine

the

impact

the

omission

and

act

Command specified a device that
task-residence device.

was

valid

User Action:

proper

device

and

accordingly.
INS -- Illegal device/volume

Explanation:

Make sure
reenter command.

you

specified

the

not

INS -- Illegal first APR

Explariation:

A privileged task, built to run using APR 4 or 5 as
its base, was too large.
Using APR 4, the task was larger than
12K; using APR 5, the task was larger than 8K.
If the Executive
has been built to support 20K of address space, APR 5 is the only
valid base APR for tasks mapping into the Executive.
A
privileged task that does not map into the Executive must use APR
0 as its base.
User Action:

See the RSX-llM/M-PLUS and Micro/RSX Task Builder
Manual
for a description of the---;PR keyword
(/PRIVILEGED
qualifier to LINK).
INS -- Illegal priority

Explanation:

Command specified a priority value of less
or greater than 250.

User Action:

than

Reenter command after checking proper syntax.

INS -- Illegal use of parname partition or region

Explanation:

Command attempted to install task
secondary pool partition.

User Action:

into

CPU

Reenter command, specifying proper partition.

INS -- Length mismatch common block blockname

Explanation: The length parameter for the common block, as
described in the label block for the task image, did not match
the length parameter defined in the system. A task's label block
data must match system data for that task before it can be
installed.
User Action:

See your system manager.

7-33

RUNNING TASKS

INSTALL (Cont.)
INS -- No checkpoint space, assuming not checkpointable
Explanation: Warning message on systems that do not support
dynamic allocation of checkpoint space. Command attempted to
install the task as checkpointable, but the task was not built as
checkpointable and the~efore had no checkpoint space allocated.
Since the system does not support dynamic
allocation
of
checkpoint space, the system considers the task to be not
checkpointable.
User Action: If
checkpointable.

you

wish,

you

can

relink

task

the

INS -- No pool space
Explanation: No dynamic memory (DSR) was available for the
Common Block Directory (CBD) or Partition Control Block (PCB).
it

does

Explanation: No dynamic memory
(DSR) was available for
Control Block (TCB)
in the System Task Directory (STD).
cannot be installed.

Task
Task

User Action: Wait. Pool space may free up
not, see your system manager.

does

User Action: Wait. Pool space may free up
not, see your system manager.

soon.

INS -- No room available in STD for new task

soon.

INS -- Not enough APRs for task image
Explanation; The Task Builder allows you to specify the virtual
base address of a task image as a multiple of 4K. Privileged
tasks start at virtual 100000 (octal) to map the 16K Executive or
virtual 120000 (octal) to map the 20K Executive.
If the virtual
base address is set too high, the task image may not be able to
be mapped with the remaining mapping registers.
User Action: See the RSX-llM/M-PLUS and Micro/RSX Task Builder
Manual for more information on the /PR keyword---c7i?RIVILEGED
qualifier to LINK).
INS -- R/O partition
partition

parname

not

system

defaulting

task's

Explanation: Warning message. Command attempted to install a
read-only
common
in a nonexistent partition.
Common was
installed in task's partition.
User Action:

If you wish, you can create the missing partition.

INS -- Specified partition too small
Explanation: Command attempted to install task
that was smaller than the task.
User Action:
command.

Increase the size

7-34

the

partition

and

reenter

RUNNING TASKS

INSTALL (Cont.)
INS -- Task image already installed
Explanation: The requested task image, which was checkpointable,
had already been installed. On systems that do not support the
dynamic allocation of checkpoint space, checkpointable tasks that
have checkpoint space allocated can be installed only once.
Other tasks can be installed more than once
(under different
names) •
User Action:
If the system has dynamic allocation of checkpoint
spaces
rebuild
the
task
without task checkpoint space.
Otherwise, make the task noncheckpointable.
INS -- Task image I/O error
Explanation:
INSTALL either could not read the task image file,
or could not rewrite the task image header because the device was
write-locked.
User A~tion: Determine the cause of the error and correct it
you can.
If you cannot, see your system manager.

INS -- Task image virtual address overlaps common block blockname
Explanation:
The virtual addresses reserved for the task image
overlap those reserved for the common block named in the message.
A corrupt task image file probably caused the overlap.
User Action: Determine the state of the task image file and
correct the error if you can.
You may have to rebuild the task.
INS -- Task name already in use
Explanation: Command attempted to install a task with
name as one already in the system.

the

same

User Action: Determine if the two tasks are the same.
If not,
install your task using the /TASK_NAME qualifier to change the
name.
INS -- Too many common block requests
Explanation:

Task made too many common-block requests.

User Action: Tasks are limited to seven common-block references.
This error can result from an improper task build or coding
errors. Find the cause of the error and correct it.
INS -- Too many LUNS
Explanation:

Task requested more than 250 LUNs to be assigned.

User Action:
Recheck task build and code for source of the error
and correct it.

7-35

RUNNING TASKS

INSTALL (Cont.)
INS -- WARNING -- Privileged task overmaps the I/O page

Explanation:

A privileged task that is mapped into the Executive
is usually also mapped into the I/O page in order to access the
KTll registers and other devices. Many tasks do not require this
access and can use the additional 4K words of virtual address
space for the task image. The message warns that a task that may
require access to the I/O page might have grown too large.
User Action:

Determine the cause of the error and correct it

necessary.

7-36

RUNNING TASKS

REMOVE
7.9

REMOVE

REMOVE takes a task name out of the System Task Directory.
is no longer installed.
REMOVE/REGION takes the name of a
Directory and the partition list.

region

out

the

The

task

Common

Block

This is a privileged command.
Format
REMOVE
Task? taskname
REMOVE taskname
Parameter
task name
Specifies the name of the task you wish to remove.
Examples

$ REMOVE WONTON

This example removes the task named WONTON from the
Directory.
It is no longer installed.

System

Task

Notes
To remove an active task, you must first abort it.
If a task is fixed, REMOVE first unfixes it and then removes it.
See Section 7.10 for more information on fixing a task using the
FIX command.
REMOVE cancels all time-based requests for the task to run.
REMOVE deallocates all receive-by-reference and receive-data
packets for the task and detaches all attached regions. See the
RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual for more
1nformat1on.

7-37

RUNNING TASKS

FIX
7.10

FIX

FIX causes an installed task or region to be loaded and locked into
memory.
Subsequent requests for the task or region may be serviced
more quickly because it is memory-resident and does not have to be
loaded from the disk.
This is a privileged command.
Format
FIX
Task? taskname
FIX[/qualifier] taskname
Parameter
task name
Specifies the installed task you want to fix in memory.
Example
$ FIX ACNT
$

$ SHOW TASK/INSTALLED/FULL ACNT ~
ACNT
061724 GEN 100630 02264100-02342000
STATUS:
-EXE -CHK -PMD PRV FXD
TI - NONE
IOC - 0 EFLG - 000000 000000
$
$ UNFIX ACNT ~
$
$ SHO TAS INS FU ACNT ~
ACNT
061724 GEN 03S370 0047000-00S54700
STATUS:
-EXE -CHK -PMD PRV
TI - NONE
IOC - O.
EFLG - 000000 000000
$

PRI - SO. DPRI - SO.

PR! - 50. DPRI - 50.

In this example, the user fixed
in memory the installed task
ACNT.
The task's status, as displayed, includes the mnemonic FXD
under STATUS and also gives the task's location in the partition
GEN.
Notes
UNFIX and REMOVE counteract FIX.
After a task is fixed, it need not be loaded into memory because
it is already memory-resident.
Requests to run the task can be
serviced more quickly.
Fixed tasks remain memory-resident even after they exit or abort.
Fixing a checkpointable task makes it noncheckpointable.
Active tasks cannot be fixed.
before it can be fixed.

However, a task must be

The system can fix a task in memory only when
which it is to be fixed becomes available.

7-38

the

installed

partition

RUNNING TASKS

FIX (Cont.)
Not all tasks will run properly when fixed.
Certain tasks may
require data areas to contain certain values when loaded in from
the disk.
The first time the task is run, these data areas may
be modified and the task may run unpredictably thereafter. Tasks
that initialize their data areas, and therefore do not have this
problem, are called serially re-entrant.
Overlaid tasks may be fixed and, if their root segments are
serially re-entrant, will run correctly. However, since their
overlaid segments must still be read in from disk
(unless the
task was built using memory-resident overlays), not much is
gained by fixing them.

Error Messages
FIX -- Partition busy

Explanation: The partition in which the task was to be fixed
occupied, so the task cannot be fixed.
User Action:

Wait or install the task in another partition.

FIX -- Task already fixed

Explanation:

The specified task is already fixed.

User Action:

None.

FIX -- Task being fixed

Explanation:
fixed.

The specified task

User Action:

None.

7-39

the

process

being

RUNNING TASKS

UNFIX
7.11

UNFIX

UNFIX frees a fixed task from memory. The effect is to allow tasks
that have been waiting for space in the partition in which the fixed
task resides to compete for that space. This is a privileged command.
Format
UNFIX
Task? taskname
UNFIX taskname
Parameter
task name
Specifies the name of the task you wish to unfix.
Example
See example in Section 7.10.
Notes
A fixed task remains fixed after it exits or aborts.
it must be explicitly unfixed or removed.

Therefore,

Error Message
UNF -- Task not fixed

7.12

Explanation:
fixed.

Command attempted to unfix

User Action:

None.

task

that

was

not

SET AND SHOW

All users can display information about partitions, active and
installed tasks, the clock queue, and logical-unit-number assignments.
Privileged users can establish and eliminate partitions and change the
priority of active tasks.

7-40

RUNNING TASKS

SET PARTITION
7.12.l

SET PARTITION

SET [NO]PARTITION creates or eliminates partitions in
This is a privileged command.

system

memory.

A partition is a contiguous area of memory with a name, a size, a
fixed base address, and a type. RSX-llM partitions can be of four
types: system-controlled, task-controlled, common regions, and device
commons.
In
addition,
task-controlled
partitions
can
have
subpartitions.
Format
SET NOPARTITION:parname
SET PARTITION:parname/qualifier[s]
Base? n
Size? n
Required Qualifiers
/BASE:n
/SIZE:n
Qualifier
/TOP:arg
Partition Types
/COMMON
/DEVICE
/SYSTEM
/TASK
/TOP:arg
/[NO]SUBPARTITION:subparname
Required Argument
par name
Partition names are from one through six Radix-SO
Each partition (or subpartition) must have a name.

characters.

SET NOPARTITION eliminates the named partition.
Required Qualifiers
/BASE:n
Specifies the starting address of the partition.
physical base address specified in 64-byte units.

the

64-byte

/SIZE:n
Specifies the size of the partition.
units.

7-41

n is the

size

RUNNING TASKS

SET PARTITION (Cont.),
n

The argument for the base and size of the partition can be
entered in a number of formats.
In all formats, n is a number
that is multiplied by .a factor to calculate the value to be used.
See Table 7-1.
Table 7-1
Base and Size Specifications for SET PARTITION

Format
Octal
Decimal
Octal K
Decimal K

nnnn
nnnn.
nnnK
nnnK

Calculated
Value

Base Range

Size Range

(nnnn*lOO)
(nnnn.*640)
(nnn*4000)
(nnn.*2048.)

O<base<l 77777
O.<base<65535.
O<base<3777K
O<base<2047.K

O<size<2000
O<size<l024.
O<size<40K
O.<size<32.K

For system-controlled partitions, these values can range from 0
through 1920.K, or any valid representation of these limits. The
upper limit is the size of your system's memory.
Qualifier
/TOP:arg
Moves the top boundary of the specified system according to the
form the argument is stated in. The argument is a number of
64-byte blocks, expressed in one of the five following formats:
+n

Moves the top boundary of the partition up
specified amount, making the partition larger

the

-n

Moves the top boundary of the partition down by
specified amount, making the partition smaller

the

Makes the partition the specified size by
top boundary

the

[+]*

Moves the top boundary of the partition up as
possible

Moves the top boundary of the partition down as far as
possible

moving
far

Partition Types
/SYSTEM
System partitions
are
sometimes
called
system-controlled
partitions. They are the most common type of partition on mapped
systems. All systems including DCL are mapped systems.
In system partitions, the Executive allocates available space to
accommodate as many tasks as possible at one time.
This
allocation may involve moving resident tasks to arrange available
space into a contiguous block large enough to contain a requested
task.
7-42

RONNING TASKS

SET PARTITION (Cont.)
/DEVICE
Device partitions are device commons, which are used by tasks to
access the device registers of the I/O page. Device commons
provide direct access to specialized I/O equipment, such as that
used in industrial and laboratory settings. See the Processor
Handbook supplied with your system for more information on the
I/O page.
/TASK
Task-controlled partitions are sometimes called user-controlled
partitions.
Task-controlled partitions are generally used for
real-time applications where
explicit
control
of
memory
allocation
is
important.
Task-controlled
partitions are
exclusively allocated to one task at a time unless divided into
subpartitions.
/[NO]SUBPARTITION:subparname
Task-controlled partitions can be divided into as many as seven
subpartitions. SET PARTITION/NOSUBPARTITION eliminates the named
subpartition.
/COMMON
Common partitions are sometimes called common regions.
Common
partitions are used for task communications or data or code used
in common by more than one task.
See the RSX-llM/M-PLUS and
Micro/RSX Task Builder Manual for more information on common
regions.
Examples

$ SET PARTITION:TOMPAR/SYSTEM
Base? 002010 (8D)
Size? 1000 (8D)
$ SHOW PARTITION:TOMPAR ffiD)
PAR=TOMPAR:002010:1000:SYS

(8D)

This example creates a partition named TOMPAR with a base address
of 002010 and a size of lOOO(octal) bytes. The partition is
system-controlled. Since this is the default, the user need not
have specified /SYSTEM in the command.
The display from SHOW PARTITIONS is slightly different on RSX-llM
systems in that the word MAIN appears where PAR appears in this
example.

$ SET NOPARTITION (8D)
Partition name? TOMPAR (8D)
$ SHOW PARTITION:TOMPAR (8D)
SET -- Partition not in system
This example eliminates the partition TOMPAR.

$ SET NOPARTITION:TSTPAR/NOSUBPARTITION
Subpartition name? SMOKE (8D)
This example eliminates the subpartition
task-controlled partition TSTPAR.
7-43

(8D)
SMOKE

from

the

RUNNING TASKS

SET PARTITION (Cont.)
Notes
Partitions are one of the key elements in tuning RSX-llM
and making the best use of available memory.

systems

You can specify the partition you wish your task to run in with
the PAR option of the LINK command.
You can override this
specification with the /PARTITION qualifier to the INSTALL or RUN
commands.
A system partition cannot include subpartitions specifically
defined by the SET command.
The Executive dynamically defines
subpartitions in a system partition as needed for tasks installed
in
the
partition.
You should not confuse these dynamic
partitions containing tasks with the task-controlled partitions
of RSX-llM.
You can define subpartitions of task-controlled
the SET command.

partitions

with

You can display the name, size, address and type of one or more
partitions with the SHOW PARTITIONS command (Section 7.12.2).
You can display the allocation of
partitions
in
memory
graphically with the SHOW MEMORY command (Section 8.1.7).
See the RSX-llM/M-PLUS and Micro/RSX Task
information about tasks-rlin 1n part1tio~

Manual

for

If a partition currently contains an installed task, common,
loaded driver, you cannot eliminate it with SET NOPARTITION.

If you eliminate a task partition, you
any subpartitions associated with it.

Builder

automatically

eliminate

Error Messages
SET -- Alignment error
Explanation: Command attempted to create a partition but the
base address or size conflicted with existing partitions or with
the size of physical memory.
User Action:

Check command for proper values and reenter.

SET -- Nonexistent memory
Explanation: Command
nonexistent memory.
User Action:

attempted

define

partition

Check command for proper values and reenter.

SET -- Partition already exists
Explanation: Command attempted to define
already in use.
User Action:

Use another name.

7-44

a partition with a name

RUNNING TASKS

SET PARTITION {Cont.)
SET -- Space used
Explanation: Command attempted
storage area already occupied.
User Action:

create

partition

Check command for proper values and reenter.

SET -- Task installed in partitions
Explanation: Command attempted
containing an installed task.
User Action:
accordingly.

Determine

the

eliminate

cause

partition

the

error

and

proceed

define

than

seven

SET -- Too many subpartitions
Explanation: You
attempted
to
subpartitions in a task partition.
User Action:

None.

You are limited to seven subpartitions.

SET -- Unknown main partition
Explanation: You attempted
nonexistent task partition.

User Action: Determine
appropriate action.

cause

the

7-45

create
of

subpartitions
the

error

and

take

RUNNING TASKS

SHOW PARTITIONS
7.12.2

SHOW PARTITIONS

SHOW PARTITIONS displays address and content information about the
partitions of the system.
You can display information about all
partitions or about a single partition.

Format
SHOW PARTITIONS[:parname]

Parameter
If you do not specify a partition name, all partitions in the
system are displayed.
The format of the display is as follows:
parname pcbaddr baseaddr parsize MAIN
If the partition includes subpartitions, this description is
followed by one or more lines describing the contents of the
subpartitions. The format of these lines is as follows:
pcbaddr baseaddr parsize partype contentname
In both of these displays:
par name
Specifies the name of the partition
information
to
be displayed.
When
partition, the display is as follows:

about which
you specify

you want
a system

PAR=parname:baseaddr:parsize:SYS
In this display, the address and the size fields of the single
partition displayed are 64-byte values (octal 100), while in the
multiple partition display, byte values are displayed.
See the
examples.
For a
task
partition
(user-controlled
subpartitions are also displayed as follows:

partitions) ,

any

MAIN=parname:baseaddr:parsize:TASK
SUB=parname:subparname:baseaddr:parsize
pcbaddr
Specifies the address of the Partition Control Block (PCB)
baseaddr
Specifies the starting address of the partition or subpartition
parsize
Specifies the size of the partition in bytes

7-46

RUNNING TASKS

SHOW PARTITIONS (Cont.)
par type
Specifies one of the following:
MAIN
TASK
SUB
DRIVER
RO COM
RW COM
DEVICE
SEC POOL

Main partition
Dynamic task subpartition - not /TASK
(user-controlled)
Subpartition
Device driver partition
Read-only common partition
Read-write common partition
Partition is a common mapped to the I/O page
Partition is a secondary pool

contentname
Indicates one of the following:
[taskname]
(TASKNAME)
-dd:
+ xxxx +

yyyy

An inactive resident task
An active task on RSX-llM
Indicates specific device driver on RSX-llM
Indicates the name of the first
installed task that is associated with a
an unnamed common, usually the read-only
segment of a multiuser task
Indicates the name of the common

Examples
$ SHOW PART IT IONS ~
SYSPAR 035720 00201000 00010000 MAIN
036330 00201000 00010000 TASK

DRVPAR

035610 00224000 00140000 MAIN
035324 00224000 00002600 DRIVER (DB:)
035260 00227600 00001300 DRIVER (DK:)

LDRPAR

035544 00364000 00003000 MAIN
033774 00364000 00003000 TASK

SECPOL
GEN

035434 00427000 00050000 SEC POOL
035370 00477000 04701000 MAIN
117210 00477000 00024000 RW COM !FCSFSL!
041324 00523000 00004400 TASK < POOL >
062124 00545100 00012600 TASK < LPPO >

<••• LOR>

046340 00763300 00006100 TASK

7-47

< TT35

RONNING TASKS

SHOW PARTITIONS (Cont.)
This example shows the display from SHOW PARTITIONS when no
partition is named.
Information on all partitions and dynamic
task subpartitions in the system is displayed. DRVPAR contains a
number of device drivers, each in its own subpartition. Notice
that SYSPAR's base address is 00201000 and its
size
is
lOOOO(octal) bytes. See the next example.

$ SHOW PARTITION: SYSPAR IBm
PAR=SYSPAR:002010:000100:SYS
This example shows the display from SHOW PARTITIONS when a
partition is named. No information about subpartitions or about
any tasks in the partition is displayed.
Notice that SYSPAR's
base address is given as 002010 and its size is 100 64-byte
blocks.

$ SHOW PARTITION:TSTPAR IBm
MAIN=TSTPAR:003657:000700:TASK
SUB-TSTPAR:SMOKE :003657:000010
This example shows the display when SHOW PARTITIONS
task-controlled partition that includes a subpartition.

names

SHOW PARTITIONS unadorned is the equivalent of
PAR.

command

Notes

SHOW PARTITIONS with a partition name is the
MCR command SET /MAIN=parname.

7-48

the

MCR

equivalent

the

RUNNING TASKS

SHOW TASKS
7.12.3

SHOW TASKS

You can display information about active and installed tasks on the
system in a number of ways. Section 7.12.3.1 describes how static
information about tasks active on your terminal or elsewhere on the
system can be displayed in full or brief format.
Section 7.12.3.2
explains how static information about installed tasks can be displayed
in full or brief format.
Section 7.12.3.3 explains how static
information about tasks installed from a specified device can be
displayed.
Section 7.12.3.4.1 explains the dynamic display of
information about active tasks.
Section 7.12.3.4.2 explains the
dynamic display of the Active Task List. Section 7.12.3.5 explains
the display of the LUNs of an installed task.

7.12.3.l

SHOW TASKS/ACTIVE

SHOW TASKS/ACTIVE displays information about active tasks in brief and
full format.
Brief Format
SHOW TASKS/ACTIVE[:ttnn:] [/qualifier[s]]
Command Qualifiers
/BRIEF
/ALL
ttnn:
If you name a terminal in the command, the display shows in brief
form the tasks active at that terminal.
If you do not name a
terminal, the display shows in brief form the tasks active at
your terminal.
Command Qualifier
/BRIEF
Specifies that you wish to display information about active tasks
in the brief format.
This is the default and need not be
specified.
The brief format includes task names only.
/ALL
Specifies that you wish to display information about all tasks
active on the system. The default is to show information about
tasks active at your terminal only.

7-49

RUNNING TASKS

SHOW TASKS (Cont.)
Examples
$ SHOW TASKS/ACTIVE
MCR •••
SHOTS

(BTI)

This example shows the brief display from SHOW TASK/ACTIVE.
In
this case, the tasks are MCR ••• , the central command dispatcher,
and SHOTS, the SHOW task itself.
$ SHOW TASKS/ACTIVE/ALL (BTI)
LOR •••
RMDEMO
SHOH2
NETACP
MCR •••
SHOTS
DCLTS
DBOFCP

TTS6
EDTT25
EDTT30
This example shows the brief display from SHOW TASK/ACTIVE/ALL.

Pull Format
SHOW TASKS/ACTIVE/FULL [taskname]
SHOW TASK[:taskname]/ACTIVE/FULL
task name
If you include a task name, the display shows full information on
that task.
If you do not name a task, the display shows full
information on all currently active tasks.

Command Qualifier
/FULL
Requests the full format display for the SHOW TASK/ACTIVE
command.
This format includes detailed information on the state
of one or all tasks active on the system.
The format of the
display is as follows:
taskname tcbaddr parname pcbaddr taskaddrlimits pri defpri
STATUS: statusflags
TI - ttnn: IOC - iocount BOC -buffiocount EFLG -eventflags PS -pswval
PC - pcval REGS 0-6 rrlval r2val r3val r4val rSval r6val
The elements in this display are as follows:
tcbaddr

The physical address
Block (TCB) •

par name

The name of the task's partition.

7-SO

the

Task

Control

RUNNING TASKS

SHOW TASKS (Cont.)
pcbaddr

The physical address
Control Block (PCB) •

taskaddrlimi ts

The base and top of the task's
subpartition as physical addresses.

dynamic

pri

The priority at which the task
running.

actually

defpri

The default priority at which the
built or installed to run.

STATUS

The task's
status
flags.
identified in Table 7-2.

The initiating terminal.

IOC

The decimal I/O count for the task.

BIO

The decimal count of I/O buffered
terminal driver and Executive.

EFLG

Local event flags.

pswval

The Processor Status Word.

pcval

The Program Counter.

REGS

The contents of the task's other registers.
If the task was spawned by another task, the
name of the parent task is also displayed.

the

Partition

task

was

These

are

the

If the task is not in memory (OUT flag displayed, see Table 7-2),
the PC, PSW, and other registers are not displayed.
This display shows the state of the task at the time the command
was issued. You can display similar information dynamically (in
real time) for a single task with the /DYNAMIC qualifier, as
explained in Section 7.12.3.3.1.
Table 7-2
Task Status Flags
Status
Flag

TCB
Flag

ABO
ACP
AST
BLK
CAF
CAL
-CHK
CKD
CKP

T2. ABO
T3.ACP
T2.AST
TS.STP
T2.CAF
T3.CAP
T2.CHK
TS.CKD
TS.CKP

Meaning
Being aborted
Ancillary Control Processor
AST state
Blocked externally by CLI command
Dynamic checkpointing allocation failure
Checkpoint space allocated in task image
Not checkpointable
Checkpointing disabled
Checkpoint in progress or checkpointed
(continued on next page)

7-51

RUNNING TASKS

SHOW TASKS (Cont.)
Table 7-2 (Cont.)
Task Status Flags
Status
Flag

TCB
Flag

CKR
CLI
CMD
DST
-EXE
FXD
GFL
HLD
HLT
MCR
MSG
NET
NRP
NSD
-PMD
OUT
PRV
RDN
REM
REX
ROV
RST
RUN
SEF
SLV
SPN
SPNA
STP
STPA

TS.CKR
T3.CLI
T3.CMD
T2. DST
TS.EXE
T2.FXD
T3.GFL
TS.HLD
T2.HLT
T3.MCR
TS.MSG
T3.NET
TS.NRP
T3.NSD
T3. PMD
TS.OUT
T3.PRV
TS.RON
T3.REM
T2.REX
T3.ROV
T3.RST
TS.RUN
T2.SEF
T3.SLV
T2.SPN
T2.SPN
T2.STP
T2.STP
T3.SWS
T2.WFR
T2.WFR

sws

WFR
WFRA

Meaning
Checkpoint request pending
Command Line Interpreter
Task is executing a CLI task
ASTs disabled
Not executing
Fixed in memory
Task has own groqp global event flags locked
Half-loaded, awaiting pool for task header
Being terminated
Activated by MCR
Aborted, waiting for TKTN message
Network protocol level
Mapped to non-resident partition
Cannot receive data (no send data allowed)
Suppress PMD on SST abort
Out of memory
Privileged
I/O being run down
Remove on exit
Abort AST effected or in progress
Resident overlays
Restricted - used by layered software
Running on another processor
Stopped for event flag
Slaved
Being suspended
Suspended prior to AST
Stopped
Stopped prior to AST
Reserved for software services
In a wait-for state
In a wait-for state prior to AST

NOTE
These status flags are displayed by several forms
of the SHOW TASK command. They give information
on what is happening within the task and between
the task and the system.
They also identify
certain kinds of tasks.
Names prefixed by a
minus
(-)
indicate
the complement of the
condition.
Thus,
-CHK means
the
task
is
noncheckpointable.
You must understand how the
system runs tasks to understand the meanings of
all these flags.
See the RSX-llM/M-PLUS and
Micro/RSX Task Builder Manual, the RSX-llM/M-PLUS
and M1cro~Execut1ve Reference Manual, and the
RSX-llM/M-PLUS and Micro/RSX Crash Dump Analyzer
Reference Manuar- for more information. The CDA
manual has a full explanation of the contents of
the TCB.
7-52

RUNNING TASKS

SHOW TASKS (Cont.)
Examples
$ SHOW TAS/ACT/FULL TT7 (BIT)
TT7 066734 GEN 064244 01676500-02062100 PRI - 50. OPRI - 50.
STATUS: -CHK WFR -PMO REM MCR
TI - TT7: IOC - 1. EFLG - 000000 040000 PS-70004 PC-072132
REGS 0-6 041130 051172 000000 000040 010400 051520 001472

This example shows the display in full format for the task named
TT7 (initiated by a RUN command from terminal TT7:). The task is
running in the default partition GEN at a priority of 50.
The
task is not checkpointable.
It is in a "wait-for" state.
No PMD
will be generated. The task is to be removed on exit (meaning it
was installed with the install-run-remove form of RUN), and it
was activated by MCR.
(Many tasks requested from DCL are
actually activated by MCR.)
$ SHO TAS/ACT/FUL

(BIT)

••• LOR 034210 LORPAR 033774 00364000-00367000 PRI - 248. OPRI - 248.
STATUS: STP - PMO PRV NSO FXO
TI - COO: IOC - O. EFLG - 000001 000000 PS - 170000 PC - 120526
REGS 0-6 000162 024207 177777 066640 066610 066314 120250
RMOEMO 046320 GEN
046640 01367700-01415100 PRI - 225. OPRI - 225.
STATUS: -CHK WFR -PMO PRV MCR
TI - TT62: IOC - O. EFLG - 000035 040000 PS - 170010 PC - 125014
REGS 0-6 000002 131316 131436 000000 135055 000000 121240
MCR ••• 116464 SYSPAR 036330 00201000-00211000 PRI - 160. OPRI - 160.
STATUS: STP -PMO PRV CLI NSO CAL
TI - TTO: IOC - 0. EFLG - 000001 040000 PS - 170000 PC - 124412
REGS 0-6 000000 120556 000400 120512 000100 120572 120442
OCL ••• 115530 GEN
037344 00624700-00634700 PRI - 160. OPRI - 160.
STATUS: STP -PMO PRV CLI NSO CAL
TI - TTlO:
IOC - O. EFLG - 100001 040000 PS - 170000 PC - 124470
REGS 0-6 025550 025550 000000 120426 123530 000000 120362
SHOTlO 066314 GEN
066610 02221700-02261700 PRI - 160. OPRI - 160.
STATUS: -PMO REM PRV
TI - TTlO:
IOC - O. EFLG - 000001 040000 PS - 170017 PC - 121202
REGS 0-6 000000 131574 050712 000000 000000 000000 001216
OBOOFl 117570 GEN
036770 00537000-00624700 PRI - 149. OPRI - 149.
STATUS: STP ACP -PMO PRV NOS CAL ROV
TI - COO: IOC - O. EFLG - 000002 040001 PS - 170000 PC - 120546

LPPO
061444 GEN
062504 00725200-00740000 PRI - 80. OPRI - 80.
STATUS: STP PRV
TI - COO:
IOC - 0. EFLG - 000400 140000 PS - 170000 PC - 120644
REGS 0-6 121526 121640 000115 124676 000000 000001 120342
PARENT TASK NAME - QMG •••
LPPl
062024 GEN
062374 01351200-01364000 PRI - 80. OPRI - 80.
STATUS: STP PRV
TI - COO:
IOC - O. EFLG - 000400 040000 PS - 170000 PC - 120644
REGS 0-6 120362 000061 000060 140164 140440 000000 120342
PARENT TASK NAME - QMG •••
AT.TlO 041174 GEN
040640 02062100-02142000 PRI - 80. OPRI - 80.
STATUS: SEF STP WFR -PMO REM PRV MCR
TI - TTlO:
IOC - O. EFLG - 000000 140000 PS - 170010 PC - 141604
REGS 0-6 123551 123416 000122 115530 000000 000000 120664

7-53

RUNNING TASKS

SHOW TASKS (Cont.)
QMG ••• 061340 GEN
056354 01327700-01351200 PR! - 75. DPRI - 75.
STATUS: STP PRV
TI - COO: roe - o. EFLG - 000000 040000 PS - 170000 PC - 120656
REGS 0-6 121750 123350 122350 001006 000000 000000 120372
EDITlO 057420 GEN
057340 02142000-02262100
PR! - 65. DPRI - 65.
STATUS:
WFR -PMD REM
TI - TTlO: roe - o. EFLG - 000002 100000 PS - 170000 PC - 006706
REGS 0-6 000001 000000 017764 000000 103666 1015708 001700
PARENT TASK NAME - AT.TIO

This example shows the display from SHOW TASKS/ACTIVE/FULL.
Tasks are displayed in order of priority.
Note the tasks
displayed below the first break.
Tasks LPPO and LPPl are
line-printer processors. They are spawned by the Queue Manager.
AT.TlO represents an indirect command file that spawns EDT by
including an EDIT/EDT command, but the resulting task EDITlO is
not slaved.

7.12.3.2

SHOW TASKS/INSTALLED

SHOW TASKS/INSTALLED displays information
either brief or full format.

about

installed

tasks

Format
SHOW TASKS[:taskname]/INSTALLED[/qualifier]
Command Qualifiers
/BRIEF

/FULL
Parameter
task name
Specifies the task for which you wish information displayed.
If
you do not specify a task name, information on all installed
tasks is displayed.
Command Qualifiers
/BRIEF

Requests information on installed tasks in a brief format.
This
is the default and need not be specified.
The format of the
display is as follows:
taskname ident parname priority size ddnn:-lbn [memstate]
The elements in this display are as follows:
task name

The name of the task

ident

The task version identification (or
the prototype task)

7-54

the

version

RUNNING TASKS

SHOW TASKS (Cont.)
par name

The partition in which the task is installed

priority

The task's priority

size

The size of the task in bytes

ddnn:

The device from which it is to be loaded

lbn

The logical block number of its disk address

memstate

The task memory state,
CHECKPOINTED, or blank

which

can

FIXED,

If the task version identification is missing (with the rest of
the line moved left) or if it is garbage, the task was installed
from a disk that is no longer present.
If the task version
number is a date, such as 07JUL, the task was compiled on that
day.
/FULL
Requests the full format of the SHOW TASKS/INSTALLED command.
This format displays a detailed list of the states of one or all
of the installed tasks in the system, depending on the presence
of the taskname parameter.
The format of the display is as
follows:
taskname tcbaddr parname pcbaddr taskaddrlimits pri defpri
STATUS:
statusflags
TI - ddn:
IOC - iocount EFLG - eventflags
format
as
that
of
SHOW
This display is in the same
TASKS/ACTIVE/FULL. See Section 7.12.3.1 for a description of the
display.

Examples
$ SHOW TASKS/INSTALLED
12.15
LOR •••
LDRPAR
TKNPAR
TKTN
04. 7
RM DEMO Vl. 03
GEN
MTAACP 0013
GEN
FllMSG VOOlO
GEN
NETACP V02.00 GEN
EVP ••• VOL 00 GEN
••• MCR 1.1
GEN
SHOTS
1.1
GEN
••• MOU 2502
GEN
• • • DCL 00
GEN
MCR •••
2.02
SY SPAR

248.
248.
200.
200.
200.
200.
199.
160.
160.
160.
160 •
160.

00002500 LB0:-00163310 FIXED
00010000 LB 0 : - 001710 2 2
00026700 LB0:-00171022
00013600 EM0:-00000315
00025500 LBO: -00167207
00025500 DB0:-00644640
00013100 DB0:-00644640 CHECKPO IN TED
00020300 LB0:-00162467
00020300 LB0:-00162467
00037700 LB0:-00222416
00035600 DB0:-00212612
00010000 LB0:-00162443

This example shows the brief format of the display from SHOW
TASKS/INSTALLED.
LOR ••• ,
the loader, is fixed in memory.
The
task EVP •••
is checkpointed. The final entry shown, MCR ••• ,
is
the system command dispatcher. See the next example.

7-55

RUNNING TASKS

SHOW TASKS (Cont.)
$ SHOW/TASK:MCR •.• /INSTALLED/FULL ~
MCR ••• 110160 SYSPAR 11454 00202700-00212700 PRI - 160 • DPRI - 160
STATUS: STP -PMD PRV MCR CLI NSD CAL
TI - TT5: roe - o. BIO - o. EFLG - 000001 040000 PS - 170000
PC - 122436 REGS 0-6 000000 120476 000102 120516 057020 040220 120366

This example shows the full
format of the display from SHOW
TASKS/INSTALLED.
In this case, the user named a single task.
The default is to show the full display for all installed tasks.
The status flags in the second line of the display are explained
in Table 7-2.
Notes
The brief format of SHOW TASKS/INSTALLED is the MCR TAS command.
The full format of SHOW TASKS/INSTALLED is the MCR TAL command.
The /DYNAMIC qualifier enables you to watch the
display as it is updated.
See Section 7.12.3.4.

7.12.3.3

full

format

SHOW TASKS/INSTALLED/DEVICE

SHOW TASKS/INSTALLED/DEVICE displays the names and status of all tasks
installed from a specified device.
Format
SHOW TASKS/INSTALLED/DEVICE:ddnn:
Example
$ SHOW TASKS/INSTALLED/DEVICE:DRO: rRITl
DROOFl M0323 SYSPAR 149. 00055700 LB0:-00475656 FIXED
FllACP M0323 GEN
149. 00044000 LB0:-00315566
DBOlFl M0323 GEN
149. 00044000 LB0:-00315566
DB07Fl M0323 SYSPAR 149. 00044000 LB0:-00315566 FIXED
ERRLOG Vl.01 GEN
148. 00042200 LB0:-00335276
PMD ••• 0·4. 0
GEN
140. 00015200 LB0:-00503535
HRC ••• 02
GEN
140. 00055100 LB0:-00505331
SYSLOG 1.02
GEN
130. 00016300 LB0:-00504250
••• INS 06
GEN
100. 00035400 LB0:-00502750

This display contains the following information, from left to right:
•

Task name

•

Task version identification

•

Partition name

• Task priority
• Task size
• Load device identification
• Logical block number on the load device
• Task memory state
7-56

RUNNING TASKS

SHOW TASKS (Cont.)
On a processor with less than 124K words of memory, the task size
field (fifth column) contains 6-digit rather than 8-digit numbers.
FIXED indicates that the task is fixed in memory.
CHECKPOINTED
indicates that the task has been swapped out of memory to make room
for a higher priority task.
If the task version identification is missing (the rest of the line is
offset to the left) or is irrelevant, the task was installed from a
disk that has since been removed from the drive or replaced by another
one.

7.12.3.4

SHOW TASKS/DYNAMIC

SHOW TASKS/DYNAMIC displays a moving picture on a video terminal of
either a single task's activity, or of all or part of the Active Task
List.
The command also works on hard-copy terminals, providing a snapshot
display that is different in format from the conventional SHOW TASKS
display.
This command is privileged if the Resource Monitoring Display (RMD) is
not installed on the system.
The command is nonprivileged if RMD is
installed under the name ••• RMD, or if your system supports flying
installs. See your system manager for information.

7.12.3.4.1

SHOW TASK:taskname/DYNAMIC

SHOW TASK:taskname/DYNAMIC displays a moving picture of the task's
activity on a video terminal or a snapshot display on a hard-copy
terminal.

Format
SHOW TASK:taskname/DYNAMIC[/qualifier]

Command Qualifier
/RATE:n
Argument
task name
Specifies the task you wish to inspect.

Qualifiers
/DYNAMIC
Specifies that you wish the moving display.
This function
performed by the RMD task.
RMD has four display pages:
1.

Task, which displays a task header

Active, which displays all or part of the Active Task List
7-57

RUNNING TASKS

SHOW TASKS (Cont.)

Memory, which displays the contents of memory

Help, which provides help on RMD

Once you have invoked any one of these pages, through either a
SHOW TASK/DYNAMIC command or a SHOW MEMORY command, you can move
from one page to the other without leaving RMD.
The first
character of each page name is a command to RMD to go to that
page. In addition, an ESC entered from a page permits you to
enter setup commands for that page. See Section 8.1.7 for more
information on the features of RMD.
The setup commands for the Task page permit you to change the
task header being displayed.
The task you name remains the
default display for the Task page. This means you can observe a
single task header, then jump to the Memory page or the Active
page, and then back to the Task page and the named task will
still be on display.
/RATE:n
Allows you to set the rate at which the RMD display screen is to
be replotted on the first display. n is the number of seconds
between replots. The default n is 1. You can change the rate by
pressing ESC and entering a new rate. The rate setting returns
to 1 as soon as you change pages. If you wish a slower rate, you
must reset the rate each time you change the page.
Use this qualifier to slow down the display.
Task headers may change more often than once per second, but once
per second is the most rapid rate available.
Example
$ SHOW TASK:CORT5/DYNAMIC

(8filJ

The screen is cleared and the following display appears:
14-APR-85

RSX-llM V4.2 BL38 512K
Task:
Own:
RO
PC

CORT5
TTS:
022120

= 005330

Partition:
I/0 = O.

GEN STATUS: -CHK -PMD REM PRV CLI
DPri: 160 Pri: 160 SPri: 155 Len: 000356000

Rl
PS

R2
SP

000764

= 170000

002230

= 022224

R3 = 000746
$DSW = O.

R4 = 024626 RS = 022136
Eflg = 0000001 040000

LUN File

LUN File
1. SYO:

2.
3.
4.
5.
6.
7.

18:15:33

DBO: [3,33]DEEP.DAT
SYO:
SYO:
TIO:
CLO:
DBO:

7-58

RUNNING TASKS

SHOW TASKS (Cont.)
This display changes once per second and shows the task header
for a task named CORT5. The top line of the display identifies
t~e operating syste~ by name,
version, base level and memory
size, and also gives the date and time. The next line of the
display includes the task name, the partition in which the task
is running, and the task's status flags.
(See Table 7-2 for an
explanation of the status flags.) The next line lists the task's
owner (terminal, not UIC); the outstanding I/O count; the default
priority, running priority, and swapping priority; and the length
of the task in octal bytes (top minus base). The next two lines
display the contents of the task's general-purpose registers,
program counter, Processor Status Word, stack pointer, Directive
Status Word, and local event flags.
The remainder of the display
shows the logical-unit-number assignments of as many as 25 LUNs.
(Tasks can have as many as 250 LUNs.) This task has conventional
LUN assignments except for LUN 2, which is an open file.
Notes
This display is a useful tool for understanding how tasks run on
the system.
However, you must have a thorough knowledge of how
tasks run in the RSX-llM environment to understand all the
elements of this display.
Tasks built including ODT can be observed using this command, but
if you are single-stepping through the task or otherwise using
breakpoints, the registers displayed will be those of the ODT
task, not those of the named task.
This display is particularly useful for observing
complex
assemblies, as you can tell how far the assembly has gone by
which files are open. You may also be interested in observing
the Task Builder at work.

7.12.3.4.2

SHOW TASKS/ACTIVE/DYNAMIC

SHOW TASKS/ACTIVE/DYNAMIC displays a moving picture of the Active Task
List on a video terminal or a snapshot display on a hardcopy terminal.
Format
SHOW TASKS/ACTIVE/DYNAMIC[/qualifier[s]]
Command Qualifiers
/OWNER:ddnn:
/PRIORITY: n
/RATE:n
Command Qualifiers
/OWNER:arg
ddnn:
ALL
Specifies the terminal or other device from which the tasks
displayed are being run.
You can name any device, pseudo device,
logical device name, or terminal number for this argument.
The
default argument is ALL, which displays tasks owned by all
devices on the system.
7-59

RUNNING TASKS

SHOW TASKS (Cont.)
You can change the owner displayed by pressing the
entering a new device name.

ESC

key

and

Note that this qualifier differs from other "owner" qualifiers in
DCL in that it names a terminal and not a UIC as the owner.
/PRIORITY:n
Specifies the highest priority to be displayed.
250, the highest priority on the system.

The

default

Use this qualifier to shorten the display to within one
worth.

screen's

You can change this value by pressing the ESC key and entering
new priority.

/RATE:n
Allows you to set the rate at which the RMD display screen is to
be replotted on the first display. The argument n is the number
of seconds between replots.
The default value for n is 1.
You
can change the rate once the display begins by pressing the ESC
key and entering a new rate. The rate setting returns to 1 as
soon as you change pages.
If you wish a slower rate, you must
reset the rate each time you change the page.
Use this qualifier to slow down the display.
The Active Task List may change more often than once per
but once per second is the most rapid rate available.

second,

Example
$ SHOW TASKS/ACTIVE/DYNAMIC

The screen is cleared and the following display appears:
RSX-llM V4.2 BL38

512K

14-APR-85 19:08:55

OWN=ALL

Name
LDR •••
RMDEMO
SHOHO
NETACP
EVP •••
DCLTS
DBOFCP

Length
TI
00002500 coo
00026700 TTO
00026700 HTO
00025500 coo
00014200 coo
00035600 TTS
00044000 coo

Pri
248.
225.
225.
200.
199.
160.
149.

o. -CHK FXD STP -PMD
o. -CHK WFR -PMD PRV
o. -CHK -PMD PRV MCR
o. STP ACP -PMD PRV
o. STP -PMD PRV
o. -CHK STP REM PRV
o. -CHK STP ACP -PMD

I/O Status flags

CLI
PRV

LPO
TTS

00014100 coo
00002600 TTS

70.

O. STP
1. -CHK

MCR

so.

7-60

PRV SLV
WFR -PMD

REM

PRV
MCR

NSD

NSD
NSD

RUNNING TASKS

SHOW TASKS (Cont.)
The screen changes once per second and displays the Active Task
List.
The first line identifies the operating system, version
number, base level, memory size, the current owner of the tasks
being displayed, and the date and time. Since the current owner
is ALL, the remainder of the display is the Active Task List
itself.
The display includes the task name, its length in octal
bytes, its running priority, outstanding I/O count, and the
status flags for each task.
(See Table 7-2 for an explanation of
the status flags.)
$ SHOW TASKS/ACTIVE/DYNAMIC/OWNER:TT5:

The screen is cleared and the following display appears:
RSX-llM V4.2 BL38
Name

Length

SHOTS

00026700

21-APR-85

512K

OWN=TT5:

Pri I/O Status flags
TT5 0.

CHK -PMD

REM

PRV

14:57:19

MCR

This example displays the Active Task List for a single terminal.
The only task active at the terminal is the SHOW command itself.
Notes
The RMD display is in order of priority. When a new task comes
in, all tasks below it in priority are displaced on the screen.
See Section 8.1.7 for more information on RMD.

7.12.3.5

SHOW TASK/LOGICAL_UNITS

SHOW TASK:taskname/LOGICAL UNITS displays the static
Number assignments (LUNs) for an installed task.

Logical

Unit

Format
SHOW TASK:taskname/LOGICAL_UNITS
Argument
taskname
Specifies the task for which you want LUN assignments displayed.
This must be the name of a task installed through INSTALL, and
not through the install-run-remove form of RUN.
The display consists of a list of physical
devices
and
corresponding static LUN assignments. The display does not show
any dynamic LUN assignments, even when the specified task is
running.
Tasks installed through the install-run-remove form of RUN do not
have any static LUN assignments.

7-61

RUNNING TASKS

SHOW TASKS (Cont.)
Examples
~

$ SHOW TASK:TEWKSY/LOGICAL UNITS
DBl: 1.
DBl:
2.
DBl: 3.
DBl:
4.
TI 0: 5.
CLO:

This example shows the display.

$ SHOW TASK:TT7/LOGICAL ~
SHO -- Task not in system
This example shows the error message received when you attempt to
show the LUNs of a task installed through the install-run-remove
form of RUN.
Notes
You can display information
about
a
terminal's
assignments with SHOW ASSIGNMENTS, Section s.11.1.

logical

You can display information about the LUNs of a task installed
with the install-run-remove form of the RUN command with the SHOW
TASKS/DYNAMIC command. See Section 7.12.3.4.
SHOW TASK/LOGICAL_UNITS is the equivalent of the MCR LUN command.
For more information on logical units, see Chapter 5.
the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual.
Tasks can dynamically alter their
ALUN$ Executive directive.

LUN

assignments

See

also

through

the

Error Messages
SHO -- No LUNS
Explanation: Informational message.
logical units.
User Action:

The task did not

have

any

None.

SHO -- Task not in system
Explanation:
Informational message. Command specified a task
that is not in the system, or that was installed by means of the
install-run-remove form of RUN.
User
Action: SHOW
ASSIGNMENTS
displays
logical
device
assignments for your terminal. SHOW TASKS/DYNAMIC can.display
LUN assignments for tasks installed with the install-run-remove
form of RUN.

7-62

RUNNING TASKS

SET PRIORITY
7.12.4

SET PRIORITY

SET PRIORITY alters the
privileged command.

priority

active

task.

This

Format
SET PRIORITY
Priority? pnum
Task? taskname
SET PRIORITY:n taskname

Parameters
pnum
Specifies the new priority you wish to assign to the task.
Priority numbers are in the range of from 1 through 250. n is
octal or decimal. You must add a decimal point to decimal
numbers.
taskname
Specifies the name of the active task whose priority you wish
alter.

Bx ample
$ SHOW TASK: TT7 /FULL/ACT IVE (Bill
TT7 066734 GEN 064244 01676500-02062100 PRI - 50. DPRI - 50.
STATUS: -CHK WFR -PMD REM MCR
TI - TT7: roe - 1. EFLG - 000000 040000 PS-70004 PC-072132
REGS 0-6 041130 051172 000000 000040 010400 051520 001472
$ SET PRIORITY (BQ)
TASK? TT7 illrn
PRIORITY? 199 (BQ)
SET -- Syntax error
$
$ SET PRIORITY TT7 199. illrn
$ SHOW TAS ACT FUL TT7 (BQ)
TT7
066734 GEN 064244 01676500-02062100 PRI - 199. DPRI - 199.
STATUS: -CHK WFR -PMD REM MCR
TI - TT7: IOC - 1. EFLG - 000000 040000 PS-70004 PC-072132
REGS 0-6 041130 051172 000000 000040 010400 051520 001472
$
$ SET PRIORITY TT7 225 illrn
$ SHOW TAS ACT FULL TT7 illrn
TT7 066734 GEN 064244 01676500-02062100 PRI - 149. DPRI - 149.
STATUS: -CHK WFR -PMD REM MCR
TI - TT7:
IOC - 1. EFLG - 000000 040000 PS-70004 PC-072132
REGS 0-6 041130 051172 000000 000040 010400 051520 001472

This example shows the effects of SET PRIORITY. The user first
displayed the priority of task TT7 with SHOW TASKS/FULL/ACTIVE.
The user then issued SET PRIORITY to change the task's priority
to 199 but did not terminate the priority number with a decimal
point. The system rejected the command because it recognized
that a number containing a 9 was not an octal number. The user
then issued th~ command with the decimal point and it was

7-63

RUNNING TASKS

SET PRIORITY (Cont.)
processed.
The user then attempted to change the task's priority
to 255, again omitting the decimal point. This time the command
was processed without an error message, but the priority was
changed to 255(octal), which is 149(decimal).

Notes
SET PRIORITY changes both the running and default priority of a
task.
A task can change its own priority through the ALTP$
Executive directive.
With this directive, only the running
priority is changed.
There is no SHOW PRIORITY
TASKS/ACTIVE/FULL instead.

command.

You

must

SET PRIORITY is the equivalent of the MCR ALT command.

7-64

use

SHOW

RUNNING TASKS

SHOW CLOCK_QUEUE
7.12.5

SHOW /CLOCK_QUEUE

SHOW /CLOCK QUEUE displays information about tasks currently in the
clock queue.
The information consists of the task names, the next
time each task is to be run, and each task's reschedule interval,
if
one was specified.
Format
SHOW /CLOCK_QUEUE
Example
$ SHOW /CLOCK_QUEUE
LIONEL Scheduled at
ONEUP Scheduled at
CALDOR Scheduled at
TEWKSY Scheduled at

00)

29-MAY-85 17:41:31:51 Reschedule interval 05 Secs
29-MAY-85 17:48:44:05 .Reschedule interval 20 Mins
29-MAY-85 18:00:00:00 Reschedule interval 02 Hours
30-MAY-85 10:00:00:00

This example shows the display from SHOW /CLOCK QUEUE.
Installed
tasks are placed in the clock queue through the scheduling
options of the RUN command. See Section 7.2.2.
The task LIONEL is scheduled to run at 17:41:31:51
minutes, seconds, ticks) and every 5 seconds thereafter.

(hours,

The task ONEUP is scheduled to run at 17:48:44:05.
The task CALDOR is scheduled to run at 18:00:00:00 and every
hours thereafter.

two

The task TEWKSY is scheduled to run at 10:00:00:00
day.

the

Notes
SHOW /CLOCK_QUEUE is the equivalent of the MCR CLQ command.
Installed tasks are placed in the clock queue through
privileged form of the RUN command. See Section 7.2.2.

the

This command has nothing to do with queues under the control of
the Queue Manager. Entries in Queue Manager queues are displayed
through SHOW QUEUE.
See the RSX-llM-PLUS Batch and Queue
Operations Manual.

7-65

CHAPTER 8
SYSTEM CONTROL

The commands in this chapter are used to control and display certain
system level functions.
The SHOW commands in this chapter are
nonprivileged, but all other commands in the chapter are privileged.
Other commands needed for system control may be found in other
chapters of this manual, in the RSX-llM/M-PLUS MCR Operations Manual,
and in the RSX-llM/M-PLUS System Management Guide.

8.1

SET AND SHOW

You can set and display the time and date, the system directory,
and
the size of the dynamic storage region (pool). You can display the
logged-in users and the current use of memory on the system, and you
can enable and disable logins to the system.

8.1.1

SET DAYTIME

SET [DAY]TIME sets the current date and time.
Format
SET [DAY]TIME [date]

[time]

Parameters
Either the time or the date, or both, can be specified in the
command.
They can be specified in either order. If you do not
specify a time or a date, you will be prompted. The date field
and the time field must be separated by a space.
date
Specifies the date.
formats:

You can enter the

date

either

of , two

dd-mmm-yy

Where dd is the number of the day, mmm is the
first three characters of the name of the
month, and yy is the number of the year
(relative to 1900)

mn/dd/yy

Where mn is the number of the month, dd is the
number of the day, and yy is the number of the
year (relative to 1900)

Regardless of the format you choose, the date is displayed in the
first format.

8-1

SYSTEM CONTROL

SET [DAY]TIME
time
Specifies the time.

Time is entered in the following format:

Where hh is the number of the hour in the
24-hour format and mm is the number of the
minute. ss defaults to 00

hh :mm [: ss]

Examples
~

$ SET TIME

Time?

8: 05

This example sets the time at 8:05 on the current day.
$ SET DAY ~
Date? 16-JUN-85

IBITJ

This example sets the date at June 16, 1985.
unchanged.
$ SET DAY

Date?

IBITJ

06/14/85 17:14

The time setting is

IBITJ

This example sets the date at June 14, 1985, and the time at
17:14:00.
The date will not be displayed in the format entered
but as 14-JUN-85.
$ SET DAYTIME 06-JUN-44 04:00:00
$ SET TIME 04:00:00 06-JUN-44

The examples are equivalent.
and the time at 04:00 hours.

IBITJ

Both set the date at June 6,

1944,

Notes
Regardless of the prompt, you.can
either order.

8-2

enter

the

date

time

SYSTEM CONTROL

SHOW [DAY]TIME
SET SYSTEM
8.1.2

SHOW [DAY]TIME

SHOW [DAY]TIME displays the current time and date.
The
24-hour format and the date is formatted as dd-mmm-yy.

time

Format
SHOW [DAY]TIME
SHOW TIME
SHOW DAY

Example
$ SHOW TIME ~
04:00:22 06-JUN-44

8.1.3

SET SYSTEM

SET SYSTEM establishes certain characteristics of the system.
privileged command.

It is a

Format
SET SYSTEM[/qualifier]

Command Qualifiers
/DIRECTORY: [g ,m]
/EXTENSION LIMIT:n
I [NO] LOGINS
/NETWORK UIC: [g,m]
/PACKETS!n
/POOL:top:max:total
/POOL/LIMITS:arg
HIGH=n
LOW=n
MINIMUM SIZE=n
TASK PRIORITY=n

Command Qualifiers
/DIRECTORY: [g ,m]
Establishes the identity of the system directory. The directory
you name must already exist.
This command does not create a
directory.
The /DIRECTORY qualifier is the default for SET SYSTEM.
See the discussion in Section 8.1.3 for information on the use of
this command on RSX-llM systems.
/EXTENSION_LIMIT:n
Establishes the maximum size to which a task can extend itself by
means of the EXTEND TASK directive. n can be entered in all the
formats used in the SET PARTITION command. See Section 7.12.1.

8-3

SYSTEM CONTROL

SET SYSTEM (Cont.)
See the RSX-llM/M-PLUS and Micro/RSX Task Builder Manual and the
RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual for more
information on the Extend Task d1rect1ve.
/[NO]LOGINS
Enables or disables logins.
If you issue SET SYSTEM/NOLOGINS and then log out, you will have
to reboot the system to log in again unless there is another
privileged user logged in.
/NETWORK_UIC: [g,m]
Specifies the directory ([g,m]) in which all DECnet-related tasks
are stored. The qualifier applies only to systems that selected
the external communication products
option
during
system
generation.
/PACKETS:n
Specifies the maximum number of I/0 packets to be retained in a
separate queue for use by the QIO directive. Changing the number
of retained packets helps optimize the servicing of QIO requests.
n can be from 0 through 15. The default is 5.
This value is a system-generation option on RSX-llM systems.
This command is equivalent to the SET /MAXPKT command in MCR

and

VMR.

SHOW SYSTEM/PACKETS displays this limit and also
packets currently available.

the

number

/POOL:top:max:total
Increases the size of the system pool
(the dynamic storage
region).
The top argument is the number of 32-word blocks
(decimal). The max argument is the maximum size in decimal
words. The total argument is the total size in decimal words.
/POOL/LIMITS:arg[s]
HIGH=n
LOW=n
MINIMUM SIZE=n
TASK PRIORITY=n
Sets the pool limit parameters used by the Pool
(PMT). The following list defines the parameters:

Monitor

Task

HIGH

The high-pool limit in
1600 (decimal) bytes.

bytes.

The

default

LOW

The low-pool limit in
600(decimal) bytes.

bytes.

The

default

MINIMUM SIZE

The minimum byte size of the largest free pool
block required for avoiding low-pool action by
the Pool
Monitor
Task.
The
default
is
200(decimal) bytes.

8-4

.SYSTEM CONTROL

SET SYSTEM (Cont.)
TASK PRIORITY

The base task priority, which is the lowest
priority a nonprivileged task can have and still
be eligible for memory contention during times of
low pool. This priority remains in effect until
pool conditions improve.
Note that only those
tasks requested while the system is in a low-pool
state are affected. The default is 5l(decimal)
bytes.

The following list defines the limits of the parameters:
8 4.

84.

<=
low
<= minimum
<= priority

<= high
<= high
<= 250.

<= total size of system pool

See the RSX-llM/M-PLUS System Management Guide for information on
determining the values of these parameters.

Examples
$ SET SYSTEM IBru
System UFO?
[3,54)
$

IBIT)

$ SET SYSTEM [3,54)

These commands are equivalent.
They establish
directory as UFO [3,54) on pseudo device LB:.
$ SET SYSTEM/EXTENSION_LIMIT:l200

the

system

IBIT)

This command sets the maximum size to which a task can extend
itself through the Extend Task directive to 1200 (octal) 32-word
blocks (decimal) or 30K words.

8-5

SYSTEM CONTROL

SHOW SYSTEM
8.1.4

SHOW SYSTEM

SHOW SYSTEM displays information about the current system.

Format
SHOW SYSTEM[/qualifier]

Command Qualifiers
/CL!
/DIRECTORY
/EXTENSION LIMIT
/NETWORK UIC
/PACKETS/POOL
/POOL/LIMITS

Command Qualifiers
/CL!
Displays information about each command line interpreter (CLI) on
the system.
The information includes the name of the CLI, the
name of the task that implements the CLI, the number of terminals
set to the CLI, and several status flags for the CLI.
The status flags are as follows:
ACT
DSB
PRV
RST

CLI
CLI
CLI
CLI

is active
is disabled
is available to privileged users only
is restricted

For more information about adding CLis to the system, see the
RSX-llM/M-PLUS MCR Operations Manual and the RSX-llM/M-PLUS
System Management Guide.
There is no SET SYSTEM/CL! command in DCL.
/DIRECTORY
Displays the current system directory.
The display specifies
SYSUIC, but the system directory rarely has a UIC associated with
it; it is a directory. See Section 8.1.5 for more information.
/EXTENSION_LIMIT
Displays the maximum size to which a task can extend itself by
means of the Extend Task system directive. The size is displayed
as an octal number of 32-word blocks (decimal).
/NETWORK_UIC
Displays the current network directory.

8-6

SYSTEM CONTROL

SHOW SYSTEM (Cont.)
/PACKETS
Displays the maximum number and the current number
I/O packets in the format:

available

MAXPKT=m.: c.
where m is the maximum number and c
available I/O packets.

the

current

number

Generally, some number of 18-word I/O packets are set aside in
pool and retained in a separate queue for use by the QIO
directive. This number of packets (referred to as MAXPKT)
is
used to optimize the servicing of QIO requests.
/POOL
Displays the current status of the system dynamic pool as three
numbers, flor:
lfb:
tps, where flor
is the first location
available for user partitions, lfb is the largest free block in
decimal words, and tps is the total pool space in decimal words.
The SHOW MEMORY command
(Section
more information about the pool.

8.1.7)

displays

considerably

/POOL/LIMITS
Displays the current settings for the pool limit parameters.
display is in the following format:

The

PLCTL=high:low:minimum:priority
The elements are as follows:

8.1.5

high

The high pool limit in bytes

low

The low pool limit in bytes

minimum

The minimum byte size of the largest free pool block

priority

The lowest priority a nonprivileged task can have
compete for memory during periods of low pool

SYSTEM DIRECTORIES

On RSX-llM systems, the system image file and all system tasks and
utilities are kept in the system directory on pseudo device LB:. You
can display the current setting for this directory with the SHOW
SYSTEM/DIRECTORY command.
Privileged users can change the directory
with the SET SYSTEM/DIRECTORY command.
When you issue a RUN or INSTALL command and precede the file
specification
(that is, the task image file name) with a dollar sign
($),you are instructing the system that the task you wish to run or
install is in this directory.

8-7

SYSTEM CONTROL

SHOW USERS
SHOW USERS

8.1.6

SHOW USERS on RSX-llM systems displays the terminal number
UIC for all logged-in users.

and

Format
SHOW USERS
Examples
$ SHOW USERS ~
(3,54]
TTO:
TT2:
( 7 I 40]
TT5:
(301,370]
TT7:
(200. l]
(7,42]
TT16:
TT51:
(7,26]
(303,5]
TT54:
HT2:
(7,43]

This example shows the SHOW USERS display for an RSX-llM system.
The first column identifies the terminal.
The second column is
the login UIC for nonprivileged users and the current UIC for
nonprivileged users. HT2:
is a DECnet host terminal.

8-8

SYSTEM CONTROL

SHOW MEMORY
SHOW MEMORY

8.1.7

SHOW MEMORY invokes the Resource Monitoring Display
(RMD), a system
utility program.
This program displays in a graphic manner the status
of much of the system.
It is, in effect, a display of the contents of
the system pool (dynamic storage region).
The RMD program is useful for monitoring the general activity of the
system.
It is also useful viewing for a new user to see how the
operating system operates. However, you should understand that the
graphic display is approximate and cannot be used for critical
measurement.

Format
SHOW MEMORY

Example
~

$ SHOW MEMORY

The following example shows the SHOW MEMORY display for
The circled numbers are keyed to the explanation.

RSX-llM.

0
0
f)

(KERMIT)
512K
CD FREE= SY0:18470.
DBl: 62322.

RSX-llM V4.2 BL38
TASK== *IDLE*

12-MAY-85 10:59:16
DB2:14542.
DB3:DMO
PARS

POOL=l686.:3168.:55.
1686.:3168.:55.
IN:
14
141K
OUT:
4
31K

TDMDD
TICBD
:RR::

c.
o.

c
s

R
E

() ! >))

!-!

. D D

LPRQ
POMM
lODG
LE. A
M. T

.. B0 B0
1 F

o. .

F
1

c
p

.. MD 11
E
T A
c

D
T

A 5
4

c
p

E
D
T
T
1
7

L
B

4E>

<>>>>-->-->--->---->><->--> <----->----->

0*******32******64******96******128*****160*****192*****224*****
E-P-CT-TD-C-C-T---0--------------------------------------------256*****288*****320*****352*****384*****416*****448*****480*****

•

•
•e
0

CESPAR:C
TTPAR :T
DIRCOM:C
SYSPAR:T
TKNPAR: 10
DRVPAR:D
LDRPAR:T
BASIC2 :C
FCSRES:C
TSTPAR:T
GEN
:D

4D
ERRSEQ

Operating system type, version number, and base level •
Six-character name that is a DECnet node name (if DEcnet is
running on your system)
or the system name that you
selected in SYSGEN
(if DECnet is not running on your
system) •
Size in K words of the system memory.
Current date and time.
Name of the task that is currently executing or, if none is
executing, *IDLE* (Executive executing the idle loop).

8-9

SYSTEM CONTROL

SHOW MEMORY (Cont.)
~

Number of free blocks on four Files-11 devices in your
system.
If a device is dismounted, RMD displays "OMO." If
a device is off line, RMD displays "OFL."
Pool

(dynamic storage region)

information in the format:

POOL=X:Y:Z

Number of words in the largest free block in pool

Number of free words in pool

The second line records the worst case of pool since you
invoked RMD.
This line is most useful if RMD has been
running on a slaved terminal since the system was last
bootstrapped.

Ci)

Partitions in the system using the format:
partitionname:type
type
For RSX-llM systems, one of the following:
T
S
D

Task partition
Subpartition
System-controlled (dynamic) partition
Command partition

Number of tasks iri memory and amount of memory they use and
number of active tasks swapped or checkpointed out of
memory and the amount of memory they would require.

4D)

Name of each task, common, or driver
in memory and its
location in memory using the following symbols to designate
size, type (task, common, or driver), and other attributes:
Symbol

[

+ +
(

)

Attribute
Active task
Task not active but occupies memory
Named common
Unnamed common (displayed name is first
attached task)
Loaded driver using device mnemonic
Task not fixed in memory
Task fixed in memory

The hyphens and equal signs represent the amount of memory
that each task, driver, or common occupies. Where the
display shows only one delimiter and no hyphens or equal
signs,
the open delimiter is in the same location as the
closing delimiter of the preceding task.

8-10

SYSTEM CONTROL

SHOW MEMORY (Cont.)

Partition size and location.
The beginning of
each
partition is marked with the same symbols as those listed
previously plus the following additions for both operating
systems:
E
P

Executive
Pool

The lines of asterisks are proportional representations of
the amount of memory occupied by each partition. The
numbers are in lK-word
increments.
Each
numerical
character also represents the same amount of memory as an
asterisk.
~

System error count sequence recorded by the Error Logger
(always zero if Error Logger not present in your system) •

Notes

RMD must be installed under the name ••• RMD for this
work.

command

RMD adjusts its display to your terminal model. If you are at a
video terminal, the display changes as you watch it.
If you are
at a hardcopy terminal, a snapshot of the display as of the
moment you issued the command is printed on your terminal.
Often, RMD is set running on a slaved terminal near the
as part of the system bootstrap procedure.

computer

Task locations and sizes displayed by RMD should be considered
approximate.
RMD is primarily designed to provide a visual
display and system debugging tool. It does not measure task size
or location accurately.
In general, RMD is designed to allow either an operator or user
to
view the current state of the operating system.
The
information is presented in a graphic, easily comprehensible
form.
There are a number of specific instances in which RMD can help to
locate certain system lockout problems or bugs in application
and/or system-level software:
•

Bugs and other situations that cause exhaustion of system
dynamic memory (resulting in unexplained system hanging)
may be detected and more easily reproduced and diagnosed.

•

Task checkpointing and swapping can be monitored and,
in
systems with limited memory, deadlock conditions can
often be diagnosed more easily.

Free space on a number of Files-11 devices may be
• monitored
in real time, which may help in situations
where on-line storage is
program is running wild.

8-11

premium

where

some

SYSTEM CONTROL

SHOW MEMORY (Cont.)
Other pages in the RMD display are invoked by the SHOW
TASKS/DYNAMIC command (Section 7.12.3.4). Once you have
started the RMD display by either SHOW TASKS or SHOW
MEMORY, you can move from page to page without issuing
any more DCL commands.
In fact, RMD is meant to enable
you to watch the activity in memory, on the active task
list, and within a single task header and to note the
relation between these pages.
see the RSX-llM/M-PLUS
System Management Guide for a full explanation of all the
functions of RMD and for descriptions of the commands
used within RMD to change from page to page.

8-12

CHAPTER 9
QUICK REFERENCE

This chapter lists all DCL commands in alphabetical order.
Each
command
entry
includes
cross-references
to the full command
description in this manual or to other RSX-llM manuals. Each command
entry also includes a general description of the functions of the
command, as well as the full command syntax, sometimes with brief
comments behind an exclamation point {!).
These command descriptions are intended for quick reference only.
If
you are not familiar with the functions of a particular command, you
should read the main text referenced in this chapter.
The comments
are in shorthand form and are meant to serve as reminders only.
Comments include examples of input, value ranges, and cautions.
Privileged commands and qualifiers are flagged.
A number of commands
have two qualifiers listed as synonyms. Other qualifiers perform no
operation by themselves and are listed in the comments as "no-ops."
These synonyms and no-ops are usually included for compatibility with
DCL on VAX/VMS systems or for clarity and completeness. See the main
text for more information.
This chapter also lists and summarizes the DCL commands used in
setting up the Queue Manager. The RSX-llM/M-PLUS System Management
Guide includes full details on using these commands.
For your convenience, some frequently used commands have brief forms.
These
short
forms
are not necessarily compatible with other
implementations of DCL and are provided for the convenience of RSX-llM
users. They are as follows:
A

ABORT

HELP

BROADCAST

HELP

COPY

LOGOUT

DIRECTORY

LINK

DEAL

DEALLOCATE

MACRO

DEAS

DEASSIGN

EDIT

RUN

FORTRAN

SHOW

9-1

QUICK REFERENCE

Section 7.3

ABORT

ABORT forces an orderly end to a running task or to the action of a
specific command.
Nonprivileged users can abort any task running on
TI:.
Formats
ABORT[/COMMAND] [/qualifier[s]] commandname
ABORT/TASK[/qualifier] taskname
Command Qualifiers
/COMMAND
/TASK
/[NO]POSTMORTEM

lOefaul t

ALLOCATE

Section 5.4

ALLOCATE declares a specified device to be a private device.
If you
omit the unit number and colon, the first available device of that
class is allocated.
Format
ALLOCATE[/qualifier[s]] dd[nn:]

[logicalname]

!Logical names same as
!other device names:
!Two characters, octal
!unit number, and :.

Command Qualifier
/TERMINAL: ttnn:
/TYPE:devicetype

!Privileged
!RMOS, RK07, RL02, and so on.

ANALYZE/CRASH_DUMP
See the RSX-llM/M-PLUS and Micro/RSX Crash Dump Analyzer Reference
Manual.

ANALYZE/CRASH DUMP command helps you determine the cause of system
crashes by inalyzing and format~ing a memory dump created by the
Executive Crash Dump Module.
Format
ANALYZE/CRASH_DUMP[/qualifier[s]] filespec[qualifier[s]]

9-2

QUICK REFERENCE
Command Qualifiers
/LIST[:listfilespec[/qualifiers]]
/ERROR LIMIT
/PAGE COUNT:n
/PAGE-LENGTH:n
I [NO] PRINTER
/EXIT:n
/LIMIT:n
/LINES :n
/[-]SP
/BINARY:binaryf ilespec
/MEMORY SIZE:n
/SYMBOLS:symbolfilespec
File Qualifiers
/ACTIVE:(arg[, ••• ])
DEVICES
TASKS
/ALL
/DEVICES
/TASKS
/BLOCK:n
/CLOCK QUEUE
/CONTROLLERS
/DENSITY:n
/DATA STRUCTURES: (arg[, ••• ])
COMMAND PARSER
DEVICE
PARTITION
STATUS
TASK
UNIT
/DUMP[(:START:n,END:n,[,ADDRESS:n])]
/HEADERS
/KERNAL: (arg [, ••• ])
DATA: (START:n,END:n)
INSTRUCTION: (START:n,END:n)
REGISTERS
/PARTITION
/POOL: (START:n,END:n)
/SECONDARY POOL: (START:n,END:n)
/[NO]SYSTEM
/TASKS:(arg[, ••• ])
DIRECTORY
ADDRESS: (NAME:name[,START:n,END:n])
INSTRUCTION: (NAME:name[,START:n,END:n])

Section 5.2

ANALYZE/MEDIA

The ANALYZE/MEDIA command determines if bad blocks exist on a disk
volume and records their locations for use by the backup and restore
utilities and the INITIALIZE command.
Format
ANALYZE/MEDIA[/qualifier[s]] ddnn:

9-3

QUICK REFERENCE
Command Qualifiers
/ALLOCATE

!Prompts for bad block numbers
!to put in BADBLOCK.SYS and to
!enter in the bad block
!descriptor file.

/BAD BLOCKS
/BAD-BLOCKS/EXERCISE: (n,m)
/BAD-BLOCKS/NOEXERCISE
/[NOTEXERCISE[: (n,m)]
/OVERRIDE
/RETRY
/SHOW

Sec ti on 4. 4. 3

APPEND

APPEND appends to an existing sequential file records from one or more
sequential files.
Format
APPEND [/qualifier [s]]

infile [ ,s] outfile

Command Qualifiers
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec
/NOWARNINGS
/REWIND
/SHARED

!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!Filespec can include wildcards.
!Suppress error messages
!Tape only. Rewinds tape before
!beginning
!Permits others to access file
!while you append it

Section 5.3

ASSIGN

9-4

!Logical names same as
!other device names:
!Two characters, octal
!unit number, and :.

QUICK REFERENCE
Command Qualifiers
/LOCAL
/LOGIN
/GLOBAL
/SYSTEM

!Default
!Privileged
!Privileged
!Privileged; synonym for /GLOBAL.

ASSIGN/QUEUE
See the RSX-llM/M-PLUS System Management Guide.

ASSIGN/QUEUE establishes a path between a queue and a processor in the
Queue Manager subsystem. Privileged.
Format
ASSIGN/QUEUE queuename processorname

ASSIGN/REDIRECT

Section 5.3.l

ASSIGN/REDIRECT redirects output from one physical device to another.
You can also redirect output from a physical device to a pseudo device
or vice versa. Privileged.
Format
ASSIGN/REDIRECT oldddnn:

newddnn:

ASSIGN/TASK

Section 5.3.2

ASSIGN/TASK reassigns an installed task's logical unit numbers
(LUNs)
from one physical device to another. The reassignment overrides the
static LUN assignments in the task's disk image file.
You cannot
change the LUNs of an active task. Privileged.
Format
ASSIGN/TASK:taskname ddnn:

lun

BACKUP

Section S.10

See also the RSX-llM/M-PLUS Utilities Manual.
BACKUP backs up and restores Files-11 volumes.
It transfers files
from a volume to a backup volume and retrieves files from the backup
volume. BACKUP works through the Backup and Restore Utility
(BRU).
You should read carefully the main text entries on BACKUP and BRU
before using this command.
9-5

QUICK REFERENCE
Format
BACKUP[/qualifier[s]] sourceddnn: [filespec[s]] destinationddnn:
Command Qualifiers
Group 1:

Selective Backup and Restore

/CREATED:arg
AFTER: (dd-mmm-yy hh:mm) !Use with /CREATED or
BEFORE: (dd-mmm-yy hh:mm) !with /MODIFIED.
/EXCLUDE
/IMAGE:arg
!For multivolume disk operations.
SAVE
RESTORE
/MODIFIED :arg
AFTER: (dd-mmm-yy hh:mm)
BEFORE: (dd-mmm-yy hh :mm)
/NEW VERSION
/[NO]REPLACE
Group 2: Initialization
/ACCESSED:n
/BADBLOCKS:arg
AUTOMATIC
MANUAL
OVERRIDE
/EXT ENS ION: n
/FILE PROTECTION:code
/HEADERS:n
/INDEX:arg
BEGINNING
MIDDLE
END
n

/INITIALIZE
/MAXIMUM FILES:n
/SAVE_SET:name
/WINDOWS:n

!n is default number of FCBs per
!volume.
!Default

!Default n=S.
!Default is protection of involume.
!Specifies location of INDEXF.SYS
!on volume; default is location of
!file on involume.
!At logical block n.
!Default is name of volume being
!backed up.
!Default is number of mapping
!pointers on involume.

Group 3: Tape and Disk Control
/APPEND
/DENSITY:arg
800
1600
/ERROR LIMIT:n
/LABEL:TAPE:fileset-ID
/LENGTH:n
/REWIND

!May need /REWIND; see main text.
!Default density is 800 bpi.
!Default n=25.
!Usable length of output tape in
!decimal feet; default n = physical
!length of the output tape.
!Rewind first tape of tape set
!before executing the command line;
!may use with /APPEND.

Group 4: Verification
/COMPARE
/VERIFY

9-6

QUICK REFERENCE

Group 5: Display
/LIST
/[NO]LOG

!/LOG goes to TI:; /NOLOG is default.

Group 6: Disk Processing
/APPEND
/DIRECTORY
/NOINITIALIZE

!May need /IMAGE; see main text.
!Can only be used with /NOINITIALIZE.

/LABEL:arg

!See also /LABEL:TAPE:volumelabel,
!Gp 3.

INPUT:volumelabel
[OUTPUT:]volumelabel

/MOUNTED
/[NO]PRESERVE

!/LABEL:OUTPUT is default; if the
!only volumelabel in command line
!is outvolume, /LABEL:volumelabel
! will do.
!/PRESERVE is default.

Section 3.6

BROADCAST

BROADCAST displays a specified message at one or more terminals.

Formats
BROADCAST ttnn: message
BROADCAST @indirectspec
BROADCAST[/qualifier] message

Command Qualifiers
/ALL
/LOGGED_IN

! Privileged

Section 7.5

CANCEL

CANCEL does not
CANCEL eliminates entries from the clock queue.
affect a currently executing task, just the pending entries in the
clock queue.

Format
CANCEL taskname

Section 7.4

CONTINUE

CONTINUE resumes execution of a previously suspended task.

Format
CONTINUE [taskname]

!Taskname defaults to TTnn

9-7

QUICK REFERENCE
Section 4.3.6

CONVERT

CONVERT invokes the RMSCNV utility, which moves records from one file
to another.
RMSCNV reads records from an input file and writes them
to an output file. The action of RMSCNV depends on the organization
(sequential, relative, or indexed) of the two files and on the
qualifiers you include with the CONVERT command. See the main text
and the RMS-11 documentation supplied with your system for more
information.
Format
CONVERT[/qualifier[s]] infile outfile
Command Qualifiers
/ALLOCATION:n
/[NO]APPEND
/BLOCK SIZE:n
/[NO]FIXED CONTROL
/[NO]IDENTlFICATION
/INDEXED
/KEY [ :n]
/[NO]LOG FILE[:filespec]
/[NO]MASS INSERT
/MERGE
/[NO]PAD[: [#)arg]
/RELATIVE
/[NO]REPLACE
/SEQUENTIAL
/[NO]TRUNCATE

!Contiguous blocks to allocate; n
!with no decimal point is octal
!/APPEND conflicts with /REPLACE.
!Magtape block size:l8<=n<=8192; default=512.
!/NO is default.
!Prints RMS version number; /NO is default;
!no filespec required.
!Outfile is indexed; see main text.
!O<=n<=9; default=l.
!/NO is default; no filespec logs on TI:
!Both files must have same organization.
!Pad infile records to outfile length; default
!pad character is blank (040).
!Outfile is relative.
!/REPLACE conflicts with /APPEND.
!Outfile is sequential.
!/NO is default.

COPY

Section 4.3.4

COPY copies files.
Unless specified otherwise, COPY preserves the
file organization of the input file, that is, indexed files are copied
as indexed files, and so forth.
See also the CONVERT command.
Format
COPY infile[s) outfile

!See main text for multiple file copies

Command Qualifiers
/ALLOCATION:n
/BLOCK_SIZE:n

/[NO]CONTIGUOUS
/DATE:dd-mmm-yy
/EXCLUDE:filespec

!Number of contiguous block space
!Defines block size for outf ile on
!magtape; n is octal unless terminated
!with decimal point; no effect on
! inf ile.
!Specifies contiguous outfile.
!Given day only
!File specification can
!include wildcards.

9-8

QUICK REFERENCE
!Suppresses error messages
!Makes outf ile UIC owner of copy.
!Infile written over outfile.
!Output file takes creation date of
!input file.

/NOWARNINGS
/OWN
/OVERLAY
/PRESERVE_DATE
/REPLACE
/REWIND

!Magnetic tape only. Rewinds tape
!before starting operation.
!Permits other to access file
!while you copy it.
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only

/SHARED
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY

CREATE

Section 4.2.1

CREATE creates a sequential file in a directory on a file-structured
device.
After you issue the command, you can immediately enter text.
To end data entry and close the file,
type CTRL/Z.
See also
CREATE/DIRECTORY.
Format
CREATE f ilespec

CREATE/DIRECTORY

Section 4.2.2

CREATE/DIRECTORY creates a User File Directory
(UFO)
on a Files-11
volume and enters its name in the volume's Master File Directory
(MFD).
Nonprivileged users can only create directories on mounted
volumes on their own private (allocated) devices.
Format
CREATE/DIRECTORY [/qualifier]

[ddnn:]

[g ,m]

Command Qualifiers
/ALLOCATION:n
/LABEL:volumelabel
/NOWARNINGS
/OWNER_UIC

!Entries for n files.
!Compare with volume label.
!Suppresses error messages
!Owner of directory; use if
!different from creator.

/PROTECTION:code

DEALLOCATE

DEALLOCATE ,counteracts ALLOCATE.
by others.

Section 5.6

It frees a private device for access

9-9

QUICK REFERENCE
Format
DEALLOCATE[/qualifier] ddnn:

!Volume must be dismounted.

Command Qualifier
/ALL
/DEVICE

!Frees all devices allocated by TI:;
!do not specify ddnn:.
!No-op

Section 5.4

DEASSIGN

DEASSIGN deletes logical-device assignments.
DEASSIGN disassociates
logical names from physical device names, pseudo device names, or
logical device names created by ASSIGN. See also other forms of the
DEASSIGN command described in the following entries.

Format
DEASSIGN[/qualifier[s]] logicalddnn:

Command Qualifiers
/ALL
/LOCAL
/LOGIN
/GLOBAL
/SYSTEM

!Combine with any other qualifier;
!No ddnn:
!Default
! Privileged
! Privileged
!Synonym for /GLOBAL.

DEASSIGN/QUEUE
See the RSX-llM/M-PLUS System Management Guide.

DEASSIGN/QUEUE counteracts ASSIGN/QUEUE.
It is used to eliminate the
path from a queue to a processor in the Queue Manager subsystem.
Privileged.

Format
DEASSIGN/QUEUE queuename processorname

Section 4.3.2

DELETE

DELETE deletes specified versions of files and releases the storage
space the files occupy.
See also other forms of the DELETE command
described in the following entries.

Format
DELETE[/qualifier[s]]
9-10

QUICK REFERENCE
Command Qualifiers
/[NO]CONFIRM
/[NO]LOG
/[NO]QUERY
/NOWARNINGS
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Synonym to /QUERY
!Lists deleted files on TI:
!Queries before deleting;
!/NO is default.
!Suppresses error messages
!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!Filespec can include wildcards.

DELETE/ENTRY
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.

DELETE/ENTRY deletes QMG jobs by entry number.
Format
DELETE/ENTRY:n[/qualifier]

!n is QMG entry number.

Command Qualifier
/FILE_POSITION:n

DELETE/JOB
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.

DELETE/JOB deletes QMG jobs by queuename and jobname.
Format
DELETE/JOB[/qualifier] queuename [[g,m]]jobname
Command Qualifier
/FILE_POSITION:n

DELETE/processor type
See the RSX-llM/M-PLUS System Management Guide.

DELETE/PROCESSOR deletes print processors, output despoolers, or batch
processors from the Queue Manager subsystem by processor name or
device name. This command also sets the device unspooled.

9-11

QUICK REFERENCE
Format
DELETE/processortype processorname
APPLICATIONS PROCESSOR
BATCH PROCESSOR
CARD READER
DEVICE
INPUT
PRINTER
PROCESSOR

!INPUT is synonym.
!PRINTER is synonym.
!CARD READER is synonym.
!DEVICE is synonym.

DELETE/QUEUE
See the RSX-llM/M-PLUS System Management Guide.

Privileged.
DELETE/QUEUE
subsystem by name.
See
from queues.

deletes queues in the
Queue
Manager
DELETE/JOB and DELETE/ENTRY to delete jobs

Format
DELETE/QUEUE queuename/ERASE

!/ERASE is required.

Section 4.4.4

DIFFERENCES

DIFFERENCES compares two ASCII (text) files line by line to determine
if parallel records
(lines) are identical and produces a listing of
the differences between the files, if any.
Format
DIFFERENCES inf ilel infile2
Command Qualifiers
/CHANGE _BAR [: n]
/IGNORE:(arg[,s]}
BLANK LINES
COMMENTS
FORM FEEDS
SPACING
TRAILING BLANKS
/LINES :n
/[NO]NUMBERS
/OUTPUT:filespec
/SLP[:audittrail]

!n is octal ASCII code of alternate
!bar. Default n=041 (!).
!Comments begin with ";".
!Group of tabs and blanks = 1 blank.
!n lines must be same for match.
!Line numbers in output file.
!Names output file; TI: is default.
!Output is SLP indirect command file.

9-12

QUICK REFERENCE
DIRECTORY

Section 4.3.1

DIRECTORY displays information on files in directories (UFOs).
Format
DIRECTORY [/format-qual] [/destination-qual]

[other-qual [s]]

[filespec [s]]

Command Qualifiers
Format Qualifiers
/ATTRIBUTES
/BRIEF
/FREE [ddnn:]

!RMS-11 attributes
!Free blocks on volume; default is
!SY:.

/FULL
/SUMMARY

!Blocks used and allocated only.

Destination Qualifier
/OUTPUT[:filespec]

!Names output file. TI: is default.

Other Qualifiers

!Not used with /FREE or /ATT

/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!File specification can
!include wildcards.
!Suppresses error messages
!Magnetic tape only; Rewinds tape
!before starting operation.

/NOWARNINGS
/REWIND

DISMOUNT

Section 5.8

DISMOUNT marks the volume mounted on the specified device as logically
off line and disconnected from the file system.
Format
DISMOUNT ddnn:

[label]

!If label specified, volume label is
!checked.

Command Qualifiers
/ALL
/PUBLIC
/SAVE
/SYSTEM
/TERMINAL
/[NO]UNLOAD

!Dismount all devices mounted by user.
!Privileged; dismounts all users from
!volume.
!Privileged; disk keeps spinning;
!privileged tasks can access.
!Synonym for /PUBLIC.
!Privileged; dismounts volumes
!mounted from another terminal
!Magnetic tape only.
!See main text.

9-13

QUICK REFERENCE
Section 4.2.3.l

EDIT[/EDT]
See also the EDT Editor Manual.

EDIT or EDIT/EDT invokes EDT, the DEC Standard
default editor.

Editor.

EDT

the

Format
EDIT[/EDT] [/qualifier[s]] filespec
Command Qualifiers
/[NO]COMMAND[:filespec]
/[NO]CREATE
/[NO]JOURNAL[:filespec]
/[NO]OUTPUT[:filespec]
/[NO]READ ONLY
/[NO]RECOVER

!Default is /COMMAND:EDTINI.EDT.

!Default is /NOREAD ONLY.
!Default is /NORECOVER.

EDIT/SLP

Section 4.2.3.2

See also the RSX-llM/M-PLUS Utilities Manual.

EDIT/SLP invokes the Source
program-maintenance editor.

Language

Input

Program

(SLP),

Format
EDIT/SLP[/qualifier[s)] filespec
Command Qualifiers
/[NO]AUDIT [: (arg [s])]
POSITION:n
SIZE:n
/CHECKSUM [: n]
/[NO]LIST[:filespec]
/[NO]OUTPUT[:filespec]
/[NO]REPORT
/[NO]TAB
/[NO]TRUNCATE[:n]

!Default is /AUDIT: (POS:80:SIZ:8).
!n must be <=132.
!n must be <14.

!Report truncation of lines by audit
! trail.
!Right-justify with tabs or spaces;
!/NOTAB is default.
!/TRUNCATE deletes audit trails and
!trailing characters; optionally
!truncates text at specified
!horizontal position.

EDIT/EDI and EDIT/editor

Section 4.2.3.3

EDIT/EDI invokes EDI, the Line Text Editor.
user-specified editor (see list below).

9-14

EDIT/editor

invokes

QUICK REFERENCE
Format
EDIT [/qualifier]

[edit- input]

!Input accepted by editor

Command Qualifier
/EDI
/KEO
/K52
/OUTPUT:filespec
/CREATE
/SOS
/TECO
/USING:yyy

!Line Text Editor.
!Unbundled KED editor.
!VT52 version of unbundled KED editor.
!Use with /KED and /K52 (unbundled
!editors).
!Use with KED and K52.
!Unsupported Son of Stopgap.
!Unsupported Text Editor and
!Corrector.
!Unsupported user editor.

FIX

Section 7.10

FIX causes an installed task or region to be loaded
memory.
Privileged.

and

locked

into

Format
FIX taskname

!Name task

HELP

Section 3.5

Help displays information about your system. Help files for MCR, DCL,
and most utilities are supplied with the system.
Your system may also
have help for an alternate CLI or local, group, or other special help.
See main text.
Format
HELP [/qualifier (s]]

[parameterl ••• parameter9]

Command Qualifiers
/OUTPUT:filespec
/LOCAL
/GROUP
/CLI :cliname
/MCR
/DCL
/FILE:filespec
/filename

!Help text to file; default /OUTPUT:TI:.
!Help file is in default UFD; HELP % is same.
!Help file is in [g,l]; g is your group.
!For alternate CLis.
!MCR help; default for MCR terminals.
!DCL help; default for DCL terminals.
!Names file containing help text.
!LB: (1,2] filename.HLP

9-15

QUICK REFERENCE
HOLD/ENTRY
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.

HOLD/ENTRY holds a QMG job in its queue by entry number.
Format
HOLD/ENTRY:n

!n is QMG entry number.

HOLD/JOB
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.

HOLD/JOB holds a QMG job in its queue by queuename and jobname.
Format
HOLD/JOB queuename [[g,m]]jobname

INITIALIZE

Section 5.9

INITIALIZE produces a volume in
Files-11
format.
See
also
INITIALIZE/UPDATE.
You can mount the volume /FOREIGN, but it is not
required. See main text. See also other forms of the INITIALIZE
command described in the following entries.
Format
INITIALIZE[/qualifier[s]] ddnn: volumelabel !Nonprivileged must
!allocate the device.
Command Qualifiers
/ACCESSED:n

!Number of directories accessed
!simultaneously.

/BAD BLOCKS:arg
AUTOMATIC
(AUTOMATIC,MANUAL)
MANUAL
NOAUTOMATIC
OVERRIDE
(OVERRIDE,MANUAL)
/DENSITY:arg
800
1600
HIGH
LOW
/EXTENSION:n

!Default

!Extend full files by n blocks;
!default n=S.

9-16

QUICK REFERENCE
/FILE_PROTECTION: (code)
/HEADERS:n
/INDEX:arg
BEGINNING
MIDDLE
END
n
/LABEL:VOLUME_ACCESSIBILITY:"c"

!Default protection for files
!on volume.
!Locates index file on volume.
!Default for tapes and DECtapes.
!Default for disks.
!At logical block n.
!Magnetic tape only; limits
!access; c can be A--z, 0--9,
!and ! " % ' ( ) + , - I :
!= & > <
? or ;

/MAXIMUM FILES:n
/OWNER: [g,m]
/PROTECTION: (code)
/[NO]SHOW
/WINDOWS:n

!Default protection for volume.
!Display volume information on TI:;
!/NO is default.
!Mapping pointers to file windows;
!default n=7.

INITIALIZE/PROCESSOR (Output)
See the RSX-llM/M-PLUS System Management Guide.
INITIALIZE/PROCESSOR creates, names, and starts an output despooler or
batch processor.
Privileged. See next entry to initialize an input
spooler.
Format
INITIALIZE/processortype processorname[/qualifier[s]]
Processortypes:
APPLICATIONS PROCESSOR
BATCH PROCESSOR
DEVICE
PRINTER
PROCESSOR
Command Qualifiers
/FLAG PAGE:n
/FORMS:n
/[NO]SHAREABLE
/[NO]LOWERCASE
/[NO]UPPERCASE

!n can be 0-2; default n=l.
!n can be 0-255; default n=O.
!Default is NOSHAREABLE.
!Default is LOWERCASE.
!Default is NOUPPERCASE.

INITIALIZE/PROCESSOR (Input)
See the RSX-llM/M-PLUS System Management Guide.

INITIALIZE/processortype creates, names, and starts an input spooler
or
card-reader
processor.
Privileged.
See previous entry to
initialize an output despooler.

9-17

QUICK REFERENCE
Format
INITIALIZE/processortype processorname[/qualifier[s]]
CARD READER
!INPUT is synonym.
INPUT
!CARD READER is synonym.
Command Qualifiers
/CONSOLE:ddnn:
/PRINTER_QUEUE:queuename

INITIALIZE/QUEUE
See the RSX-llM/M-PLUS System Management Guide.
INITIALIZE/QUEUE creates, names, and
Manager subsystem.

starts

queue

the

Queue

Format
INITIALIZE/QUEUE queuename[/qualifier]
Command Qualifiers
/PRINTER
/NOWARNINGS

!Default

INITIALIZE/UPDATE

Section 5.9.1

INITIALIZE/UPDATE invokes the HOME utility to alter values in the
volume home block without affecting the other data on the volume.
INITIALIZE/UPDATE is only for disks and DECtapes in Files-11 format.
You can mount the volume /FOREIGN on RSX-llM, but it is not
See main text.
Format
INITIALIZE/UPDATE[/qualifier[s]] ddnn:

volumelabel

Command Qualifiers
/ACCESSED:n
/DENSITY:arg
HIGH
LOW
/EXTENSION:n
/FILE_PROTECTION:code
/LABEL:newvolumelabel
/MAXIMUM_FILES:n
/OWNER: [g ,m]
/PROTECTION:code
/[NO]SHOW
/WINDOWS:n

!Extend full files
!by n blocks.
!Default protection for files
!on volume.
!Changes volume label.
!Maximum number of files
!on volume.
!Protection for volume.
!Mapping pointers to file
!windows; default n=7.

9-18

required.

QUICK REFERENCE
INSTALL

Section 7.8

INSTALL includes a task in the System Task Directory, thus
known to the system.
Privileged.

making

Format
INSTALL[/qualifier[s]]

[$]filespec

Command Qualifiers
/[NO]CHECKPOINT
/COMMAND:"taskcommand"
/EXTENSION:n
/[NO]INTERPRETER
/MULTIUSER PARTITION:parname
/PARTITION:parname
/[NO]POSTMORTEM
/PRIORITY:ri
/READONLY COMMON
/[NO]SLAVE
/TASK NAME:taskname
/UIC:(g,m]

!n (decimal) additional words
!of address space.
!Installing a CLI? Default is no.
!Install read-only portion.
!0-250.
!Install common as read-only.
!/NOSLAVE is default.
!1-6 characters.

LIBRARY

Section 6.3

See also the RSX-llM/M-PLUS Utilities Manual.

LIBRARY creates and maintains user-written library files.
The command
has eight functions, each listed here as a separate command.
See main
text for more details 9n all functions and qualifiers.
Format
LIBRARY[/operation] [/qualifier[s]]
LIBRARY @f ilespec

!Indirect command file specification.

LIBRARY/COMPRESS

Section 6.3.1

LIBRARY/COMPRESS physically deletes modules that have been logically
deleted
through
LIBRARY/DELETE.
You can rename the resulting
compressed library. You can also use this command to copy a
library
and rename it.

9-19

QUICK REFERENCE
Format
LIBRARY/COMPRESS[: (arg[,s])] libspec [newlibspec]
GLOBAL:n
!Entry-point table entries.
MODULES:n
!Module-name table entries.
BLOCKS:n
!Size in 256-word blocks.

LIBRARY/CREATE

Section 6.3.2

LIBRARY/CREATE creates a library and optionally inserts
modules into it.

one

Format
LIBRARY/CREATE [: (arg [ ,s])] [/qualifier [s]] libspec [ infilespec [s]]
GLOBAL:n
!Entry-point table entries.
MODULES:n
!Module-name table entries.
BLOCKS:n
!Size in 256-word blocks.

Command Qualifiers
/[NO]GLOBALS
/MACRO
/OBJECT
/SELECTIVE SEARCH
/SQUEEZE /UNIVERSAL

!Include globals in entry-point table.
!Identifies macro library.
!Default; identifies object library.
!Object modules only.
!Identifies universal library.

Section 6.3.3

LIBRARY/DELETE

LIBRARY/DELETE
LIBRARY/REMOVE
library.

deletes object
modules
from
a
library.
See
for removing global symbols
(entry points) from a

Format
LIBRARY/DELETE libspec module[,module[,s]

!Name as many as 15 modules

LIBRARY/EXTRACT

Section 6.3.4

LIBRARY/EXTRACT reads one or more modules from a library and writes
them to a specified output file.
You can extract as many as eight
modules with a single command. If you extract more than one module,
the modules are concatenated in the output file.
Format
LIBRARY/EXTRACT[/qualifier] libspec module[,s]

9-20

QUICK REFERENCE
Command Qualifier
/OUTPUT[:filespec]

!Default output file is TI:; name
!a file when extracting object
!modules.

Section 6.3.S

LIBRARY/INSERT

LIBRARY/INSERT inserts modules from one or more files into a library.
Format
LIBRARY/INSERT libspec filespec[s]

!Name any number of files

Command Qualifiers
/[NO]GLOBALS
/SELECTIVE SEARCH
/SQUEEZE -

!Include globals in entry-point table.

LIBRARY/LIST

Section 6.3.6

LIBRARY/LIST lists on your terminal or in an output file the names
all modules in a library.

Format
LIBRARY/LIST[:filespec] libspec
Command Qualifiers
/BRIEF
/FULL
/[NO]NAMES

!Names plus global entry points.

Section 6.3.7

LIBRARY/REMOVE

LIBRARY/REMOVE removes global symbols (entry points) from a
library.
See LIBRARY/DELETE for deleting object modules from a library.
Format
LIBRARY/REMOVE libspec global[,global[,s]
symbols

9-21

!Name as many as !15

global

QUICK REFERENCE
LIBRARY/REPLACE

Section 6. 3. 8

LIBRARY/REPLACE replaces a module in a library with a
the same name and deletes the old module.

new

module

Format
LIBRARY/REPLACE libspec filespec[s]
Command Qualifiers
/[NO]GLOBALS
/SELECTIVE SEARCH
/SQUEEZE -

!Include globals in entry-point table.

LINK

Section 6.2.2

LINK invokes the Task Builder, which links object modules and routines
from user and system libraries to form an executable task.

LINK [/qualifier [s] 1 filespec [/qualifier [s]] [ ,filespec [s]]

Command Qualifiers
/ANCILLARY PROCESSOR[:n]
/[NO]CHECKPOINT:arg
SYSTEM
TASK
/CODE: (arg [, s])
EAE
[NO]FPP
PIC
POSITION INDEPENDENT
/COMPATIBLE
/[NO]CROSS REFERENCE
/[NO]DEBUG[:filespec]
/[NO]EXECUTABLE:filespec
/ERROR LIMIT:n
/FAST /FULL SEARCH
/[NO]HEADER
/[NO]IO PAGE
/LONG /MAP [: fi lespec]
/[NO]MEMORY_MANAGEMENT[:n]
/OPTIONS[:filespec]
/OVERLAY DESCRIPTION
/POSTMORTEM
I [NO] PRINT
/[NO]PRIVILEGED[:n]
/[NO]RECEIVE
/[NO]RESIDENT_OVERLAYS

!Task is ACP; n is 0,4, or 5.
!Checkpoints to [O,O]CORIMG.SYS.
!Checkpoints to task image file.
!Extended arithmetic element.
!Floating-point processor.
!Position-independent code.
!Synonym for PIC.
!Default is ODT.
!Names task file. Synonym for /TASK.
!Stop task build after n errors.
!Fast TKB.

!Long map
!Default is /MAP:TI:
!n for unmapped systems; see main
!text; default is /MEM; n is 28 (default) or 30.
!File contains options. Otherwise you will be prompted
!Print map file?
!Default is /NOPRIVILEGED.

9-22

QUICK REFERENCE

/SAVE
/SELECTIVE SEARCH
/[NO]SEGREGATE
/SEQUENTIAL
/SHAREABLE[:arg]
COMMON
LIBRARY
/SLAVE
/SLOW
/SYMBOL TABLE[:filespec]
/[NO]SYSTEM LIBRARY DISPLAY
/ [NO]TASK [ :filespecT
/TKB
/TRACE
/[NO]WARNINGS
/WIDE

!Saves indirect file.
!/NOSEG is default.
!Multiuser

!Less space consuming TKB
!Output .STB file
!Default is /NOSYS.
!Names task image file; /EXECUTABLE
!is synonym; names 1-6 characters;
!/NOTASK means no task built.
!Default
!/NO suppresses diagnostic messages; /WARNINGS is
!default.
!Wide map

File Qualifiers
/[NO]CONCATENATE
/DEFAULT LIBRARY
/[NO]GLOBALS
/LIBRARY
/INCLUDE: (modulel[: ••• :modulen]}
/OVERLAY DESCRIPTION
/SELECTIVE_SEARCH

!File to replace [l,l[SYSLIB.OLB
!Default is /GLOBALS; includes
!global symbols in map.
!File is object module library.
!File is object module library;
!include named modules in task image.
!File is .ODL; also a command qualifier.
!Also a command qualifier.

Section 3 .1.1

protection

system

and

!HELLO is synonym.

LOGOUT

Section 3.1.2

LOGOUT counteracts LOGIN. LOGOUT also aborts any nonprivileged tasks
running
from the terminal and also dismounts any volumes and
deallocates any private devices allocated from the terminal.

Format
LOGOUT[/qualifier]

!LO is sufficient

Command Qualifier
/[NO]HOLD

!Holds remote line after logout; /NO
! is default.

9-23

QUICK REFERENCE
Section 1.2.4

MCR

MCR enters an MCR command from a DCL terminal without leaving DCL.
Format
MCR mcrcommand

MOUNT

Section 5.7

MOUNT declares a volume to be logically known to the system, on line,
and available for use.
Some qualifiers can be used with any MOUNT
command;
some
are
limited
to
mounting
disks
(and
other
random-addressable
devices)
and others are limited to mounting
magnetic tapes.
Format for Disks and Other Random-Addressable Devices
MOUNT[/qualifier[s]] ddnn:

volumelabel

Format for Magnetic Tapes
MOUNT[/qualifier[s]] ddnn: [,ddnn: ••• ] fileset-ID
Command Qualifiers for Both Disks and Tapes
/FILE PROTECTION:(code)
/FOREIGN
/OVERRIDE:IDENTIFICATION
/PARAMETERS:"user parameters"
/PROCESSOR:arg
acpname
UNIQUE
/PROTECTION: (code)
/PUBLIC
/[NO]SHAREABLE
/[NO]SHOW
/SYSTEM
/[NO]WAIT
/[NO]WRITE

!Protection for files created during mount
!Privileged; no label needed.
!Quotes are required syntax.
!Privileged; name ACP for volume.
!Volume protection during mount
!Privileged; deallocates; sets public.
!Display volume information on TI:.
!Synonym for /PUBLIC.
!Default is /NOWAIT.

Command Qualifiers for Files-11 Devices
/ACCESSED:n
/EXT ENS ION: n
/OWNER: [g ,m]
/UNLOCK
/WINDOW:arg
n
(USER: n, INDEX: n)
FULL

!n is number of File Control Blocks.
!Extend full files by n blocks.
!Coordinate with file and volume protection
!Main use is with VFY.

Command Qualifiers for ANSI and Unlabeled Tapes
See main text for these qualifiers.
/BLOCK SIZE:n
/CARRIAGE CONTROL:arg
FORTRAN
LIST
NONE
9-24

QUICK REFERENCE
/DENSITY:arg
800
1600
/[NO]HDR3
/[NO]LABEL
/OVERRIDE: (arg[,s])
ACCESSIBILITY
EXPIRATION DATE
SET IDENTIFICATION
/RECORD SIZE:n
/TRANSLATE:arg
EBCDIC
NONE
UTl
UT2
UT3
/VOLUME_IDENTIFICATION: (volume-ID[,volume-ID[,s]])

Section 4.4.2

PRINT queues files for printing on a line
queue jobs for other output devices.

printer.

can

also

Format
PRINT [/qualifier [ s]]

filespec [/qualifier [ s]] [, f ilespec [ ,s]]

Command Qualifiers
/AFTER:TOMORROW
/AFTER:(dd-mmm-yy hh:mm)
/COPIES:n
/[NO]DELETE
/DEVICE:ddnn:
/[NO]FLAG_PAGE
/FORMS:n
/[NO]HOLD
/JOB COUNT
/[NOJJOB PAGE
/LENGTH:n
/[NO]LOWERCASE
/NAME:jobname
/PAGE COUNT:n
/PRIORITY:n
/QUEUE:queuename
/[NO]RESTART
/[NO]UPPERCASE
/NOWARNINGS

!Override on filespec.
!Override on filespec.
!Flag page on each file; default is
!/NOFLAG PAGE.
!n can be 0-256; default n=O.
!Default is /NOHOLD; same effect as
!HOLD command.
!Flagpage on job; default /JOB_PAGE.
!Page length
!l-9 characters
!Limit pages in job.
!n is 1-150 nonprivileged; through 250
!privileged; default n=50.

!Suppresses error messages.

File Qualifiers
/COPIES:n
/[NO]DELETE

9-25

QUICK REFERENCE
PURGE

Section 4.3.3

PURGE deletes all but the latest versions of files
storage space the deleted files occupy.

and

releases

the

Format
PURGE [/qualifier [ s]] filespec [s]
Command Qualifiers
/KEEP:n
/[NO]LOG
/NOWARNINGS
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Lists files on TI:. as deleted.
!Suppresses error messages
'Given day only
From given day through current day
From beginning through given day
From given day through given day
Today only
File specification can
include wildcards.

RELEASE/ENTRY
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
RELEASE/ENTRY releases by entry number a print or batch job
been held in its queue.

that

has

batch

job

Format
RELEASE/ENTRY:n

!n is QMG entry number.

RELEASE/JOB
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.

RELEASE/JOB releases by queuename and jobname a
that has been held in its queue.

Format
RELEASE/JOB queuename [[g,m]]jobname

Section 7.9

REMOVE

REMOVE counteracts INSTALL. REMOVE takes
System Task Directory. Privileged.
Format
REMOVE taskname

9-26

task

name

out

the

QUICK REFERENCE
RENAME

Section 4.3.5

RENAME changes the name, type, or version number of an existing file.
Format
RENAME[/qualifier[s]] oldfilespec newfilespec

!Watch wildcards
!and version
!numbers.

Command Qualifiers
/NEW_VERSION
/NOWARNINGS
/DATE:dd-mmm-yy
/SINCE :dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Supplies new version
!number to outfile.
!Suppresses error messages
!Given day only
!From given day through
!current day
!From beginning through
!given day
!From given day
!through given day
!Today only
!File specification
!can include wildcards.

Section 3.7

REQUEST

REQUEST sends a message to the operator's console (CO:).
Format
!Optional "quotes" around message

REQUEST message

Section 7.2.1

RUN uninstalled task

When used to run an uninstalled task (from a task image file) , RUN is
a combination command, encompassing INSTALL, RUN, and REMOVE. See
main text.
Format
RUN [/qualifier [s].]

[$] filespec

9-27

QUICK REFERENCE
Command Qualifiers
/[NO]CHECKPOINT
/COMMAND:"taskcommand"
/EXTENSION:n

!See main text.
!n {octal) additional words of address
!space.

/[NO] IO PAGE
/PARTITION:parname
/[NO]POSTMORTEM
/PRIORITY:n
/[NO]SLAVE
/STATUS:arg
TASK
COMMAND
/TASK NAME:taskname
/UIC:[g,m]

!Privileged
!Privileged

!1-6 characters
! Privileged.

RUN installed task

Section 7.2.2

taskname

Command Qualifiers

!All privileged except /STATUS

/DELAY:nu

!n is the number of units and u is the
!time unit: T,ticks; S,seconds;
!M,minutes; H,hours.

/INTERVAL:nu
/SCHEDULE:hh:mm:ss
/STATUS:arg
COMMAND
TASK
/SYNCHRONIZE:u
/UIC: [g ,m]

!Can be used only with /UIC: [g,m]
!Return status from RUN command; default.
!Return status from task being run;
!see main text on both these
!arguments.
!Synchronize on next T, S, M, or H.

SET [DAY]TIME

Section 8.1.1

SET [DAY]TIME sets the system date and time.

Privileged.

Format
SET [DAY] TIME: [dd-mmm-yy]

[hh :mm]

! Set at least one; either order.

9-28

QUICK REFERENCE
Section 1.2.15

SET DEBUG

SET DEBUG displays MCR translation of any DCL command.
Format
SET DEBUG[/qualifier[s]]
Command Qualifiers
/[NO]EXECUTE
/FULL

!Indicates whether or not to execute
!the DCL command after translation.
!Displays logical symbols.

SET DEFAULT

Section 4.5.1

SET DEFAULT establishes your default device or directory, or both.
Format
SET DEFAULT [ddnn:] [[g,m]]

!Unadorned SET DEF returns
!nonprivileged user to login device
!and directory.

Section 5.10.2

SET DEVICE

SET DEVICE establishes certain device attributes.

Privileged.

Format
SET DEVICE:ddnn:/qualifier[s]

Command Qualifiers
/[NO]CHECKPOINT_FILE[:n]
/[NO]LOWERCASE
/[NO]PUBLIC
/[NO]SYSTEM
/WIDTH:n

!n is number (decimal) of blocks in
! [O,O]CORIMG.SYS.
!Default is /NOLOWERCASE.
!Default is /NOPUBLIC.
!Synonym for /[NO]PUBLIC
!Nonprivileged for TI:.

Section 4.5.4

SET FILE

SET FILE establishes certain file attributes.
Format
SET FILE[/qualifier[s]] filespec[s]
9-29

QUICK REFERENCE
Command Qualifiers
/END_OF_FILE: (BLOCK:n,BYTE:n)
/ENTER:synonym f ilespec
/NOWARNINGS
/REMOVE
/REWIND
/TRUNCATE

See main text.
See main text.
Suppresses error messages.
See main text.
Magtape only; rewinds tape before
starting operation.
Eliminates blocks allocated but
unused; saves disk space.

SET GROUPFLAGS

Section 6.4.1

SET GROUPFLAGS creates and deletes group global event flags.
text.

See main

Format
SET GROUPFLAGS:n[/qualifier]

!Nonprivileged command for own group
!n is group number.

Command Qualifiers
/CREATE
/DELETE

!Default

SET HOST

Section 1.2.12.1

SET HOST connects your terminal to a remote system.
You issue this
command after you have logged in on your current system. Both your
current and remote system must run DECnet software.
SET HOST nodename

!nodename is the name of the
!remote system.

SET [NO]PARTITION

Section 7.12.1

SET [NO]PARTITION creates or eliminates a partition.

Privileged.

Format
SET [NO]PARTITION:parname/qualifier[s]

9-30

!Parname 1-6 characters

QUICK REFERENCE
Command Qualifiers
/BASE:n
/COMMON
/DEVICE
/SIZE:n
/[NO]SUBPARTITION:subparname
/SYSTEM
/TASK
/TOP:value

!Device common.

SET PRIORITY

Section 7.12.4

SET PRIORITY alters the priority of an active task.

Privileged.

Format
SET PRIORITY:n taskname

0 through 250

SET PROTECTION

Section 4.5.3

SET PROTECTION establishes the protection status of files.
Format
SET PROTECTION:code[/qualifier[s]] filespec[s]
SET PROTECTION[/qualifier[s]] filespec[s] (code)

!default is

!The preferred syntax;
(SY:RWED,OW:RWED,GR:RWED,W:R).

Command Qualifiers
/DATE:dd-mmm-yy
/SINCE :dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!Filespec can include wildcards.

SET QUEUE/ENTRY
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
SET QUEUE/ENTRY modifies by entry number some attributes of print or
batch jobs once they are in a queue. See SET QUEUE/JOB to modify by
job name.
Format
SET QUEUE/ENTRY:n[/qualifier]

!Only one attribute at a time

9-31

QUICK REFERENCE
Command Qualifiers
/AFTER: (dd-mmm-yy hh:mm)
/COPIES:n
/[NO]DELETE
/FILE POSITION:n
/FORMS:n
/HOLD
/LENGTH:n
/[NO]LOWERCASE
/PAGE COUNT:n
/PRIORITY :n
/RELEASE
/[NO]RESTART
/[NO]UPPERCASE

!Same as HOLD/QUEUE

!n is 1-150 nonprivileged; through 250
!privileged; default n=50.
!Same as RELEASE/QUEUE

SET QUEUE/JOB
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
SET QUEUE/JOB modifies by job name some attributes of print or batch
jobs once they are in a queue. See SET QUEUE/ENTRY to modify by entry
number.
Format
SET QUEUE/JOB[/qualifier] queuename [[g,m]]jobname
!Only one attribute at a time
Command Qualifiers
/AFTER: (ddd-mmm-yy hh:mm)
/COPIES :n
/[NO]DELETE
/FILE POSITION:n
/FORMS:n
/HOLD
/LENGTH:n
/[NO]LOWERCASE
/PAGE COUNT:n
/PRIORITY :n
/RELEASE
/[NO]RESTART
/[NO]UPPERCASE

!Same as HOLD/QUEUE

!n is 1-150 nonprivileged; through 250
!privileged; default n=50.
!Same as RELEASE/QUEUE

SET SYSTEM

Section 8.1.3

SET SYSTEM establishes certain characteristics of the system.
privileged command.
Format
SET SYSTEM/qualifier

!Qualifier required

9-32

It is a

QUICK REFERENCE
Command Qualifiers
/DIRECTORY: [g,m]
/EXTENSION_LIMIT:n
/[NO]LOGINS
/NETWORK UIC: [g,m]
/PACKETs:n
/POOL:top:max:total
/POOL/LIMITS

!Sets directory where system tasks are
!kept; does not create a directory.
!Sets maximum size a task can extend
!itself with the Extend Task
!directive.
!Sets UIC for network software
!n = 0 through 15
!Increases size of pool; see main
!text.
!Sets pool limit parameters

Section 3.8.1

SET TERMINAL

SET TERMINAL sets various attributes of your
users can set attributes for any terminal.

terminal.

Privileged

Format
SET TERMINAL[:ttnn:]/qualifier[s]
Command Qualifiers
Group 1: Common Use
/[NO]BROADCAST
/CLI:cliname
/DCL
/[NO]HOLD SCREEN
/INQUIRE /[NO]LOWERCASE
/MCR
/[NO]PRIVILEGED
/SPEED:(transmit,receive)
/[NO]UPPERCASE
/WIDTH:n

!Not for VTlOOs
!/NOLOWER same as /UPPER and is
!default.
!Privileged
!Remember to set hardware after this
!command.
!/NOUPPERCASE same as /LOWERCASE

Group 2: Terminal Setup
/[NO]ADVANCED VIDEO
/[NO]ANSI CRT/ [NO]AUTOBAUD
/ASR33
/ASR35
/[NO]BLOCK MODE
/CRFILL:n /DEC CRT
/DTCOl
/EDIT MODE
/[NO]FORM FEED
/[NO]HARDCOPY
/HOST SYNC
/KSR33
/LA12

!n can be 0-7

9-33

QUICK REFERENCE
/LA24
/LA30P
/LA30S
/LA34
/LA36
/LA38
/LASO
/LAlOO
/LA120
/LA180S
/LA210
/LFFILL
/LN03
/LQP02
/LQP03
/MODEL:arg
/PAGE LENGTH:n
/[NO]PRIORITY[:n]
/PRINTER PORT
/PRO SERIES
/[NO]REGIS
/[NO]SCOPE
/[NO]SOFT CHARACTERS
/[NO]TAB /[NO]TTSYNC
/VT05
/VT50
/VT52
/VT55
/VT61
/VTlOO
/VT101
/VT102
/VT105
/VT125
/VT131
/VT132
/VT200 SERIES
/WIDTHTn
Group 3: Task Setup
/[NO]ECHO
/[NO]EIGHT BIT
/[NO]ESCAPE
/[NO]FULL DUPLEX
/[NO]INTERACTIVE
/[NO]LOCAL
/[NO]PARITY[:type]
ODD
EVEN
/[NO]PASSALL
/[NO]PASTHRU
/[NO]REMOTE
/[NO]SLAVE
/[NO]TYPEAHEAD
/[NO]WRAP

!ODD is default.

9-34

QUICK REFERENCE
Section 5.11.1

SHOW ASSIGNMENTS

SHOW ASSIGNMENTS displays at your terminal your local and login
logical-device assignments.
Privileged users can display assignments
from other terminals and global assignments.
SHOW ASSIGNMENTS[/qualifier[s]]
Command Qualifiers
/GLOBAL
/LOCAL
/LOGIN
/SYSTEM
/TERMINAL: ttnn:

!Privileged
!Default
!Same as /LOCAL
!Synonym for /GLOBAL; privileged.
!Privileged.

SHOW CLOCK_QUEUE

Section 7.12.5

SHOW CLOCK QUEUE displays information about tasks currently in the
clock queue.
This information consists of the task names, the, next
time each task is to run, and each task's reschedule interval, if any.
SHOW CLOCK_QUEUE

SHOW [DAY)TIME

Section 8.1.2

SHOW [DAY]TIME displays the system time and date setting.
Format
SHOW [DAY]TIME

SHOW DEFAULT

Section 4.5.2

SHOW DEFAULT displays the current default device
terminal, along with your terminal number.
Format
SHOW DEFAULT

9-35

and

UFO

for

your

QUICK REFERENCE
SHOW DEVICES

Section 5.11.3

SHOW DEVICES displays information about the devices
system.

included

the

Format
SHOW DEVICES[/qualifier]

[dd[nn:]]

!Two-character mnemonic only

Command Qualifiers
/[NO]PUBLIC
/WIDTH:ddnn:
/[NO]SYSTEM

!Synonym for /PUBLIC

Section 6.4.2

SHOW GROUPFLAGS

SHOW GROUPFLAGS displays the group global event flags currently in the
system.
Format
SHOW GROUPFLAGS

SHOW HOST

Section 1.2.12.2

SHOW HOST displays the name of the processor to which your terminal
currently is connected. It also shows you the name and version number
of the operating system running on the processor.
Format
SHOW HOST

SHOW MEMORY

Section 8.1.7

SHOW MEMORY invokes the Resource Monitoring Display (RMD),
display of the system's activities in memory.
Format
SHOW MEMORY

9-36

dynamic

QUICK REFERENCE
SHOW PARTITIONS

Section 7.12.2

SHOW PARTITIONS displays address and content information about the
partitions in the system.
You can display information about all
partitions or about a single partition.
Format
SHOW PARTITIONS[:name]

SHOW PROCESSOR
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
SHOW PROCESSOR displays information about the processors, printers,
card readers, and other devices under control of the Queue Manager.
Format
SHOW processortype processorname
Processortypes:
CARD READER
DEVICE
INPUT
PRINTER

!INPUT is synonym.
!All nonbatch output processors;
!synonym for PRINTER.
!CARD READER is synonym.
!All nonbatch output processors;
!synonym for DEVICE.

PROCESSOR

SHOW QUEUE
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
SHOW QUEUE displays information about print jobs in queues.
Format
SHOW QUEUE[/qualifier]

[queuename]

Command Qualifiers
/ALL
/BRIEF
/DEVICE
/ENTRY:n
/FILES
/FORMS:n
/FULL
/NAME:jobname
/OWNER_UIC: [ [g ,m]]
/PRINTER

!All entries in all queues
!All nonbatch queues; synonym for /PRINTER.
!Lists files in each job; not as long
!as /FULL.
!Lists only jobs with
!be more than one.
!Lists only jobs from
!default UIC is login
!All nonbatch queues;
!/DEVICE.

9-37

that name; may
that UIC;
UIC.
synonym for

QUICK REFERENCE
SHOW SYSTEM

Section 8 .1. 4

SHOW SYSTEM displays information about the current system.
Format
SHOW SYSTEM[/qualifier]
Command Qualifiers
/CLI
/DIRECTORY
/EXTENSION LIMIT
/NETWORK urc
/PACKETS/POOL
/POOL/LIMITS

!CLis on current system
!Default; displays current system UFO.
!Task extension limit
!Displays current network UIC.
!Maximum I/O packets and number
!currently available.
!Displays pool statistics.
!Show pool limit parameters

Section 7.12.3.l
7.12.3.2
7.12.3.3
7.12.3.4

SHOW TASKS

SHOW TASKS displays information about active or installed tasks.
Format
SHOW TASKS[:taskname]/qualifier[s]
Command Qualifiers
/ACTIVE [: t tnn:]
/DEVICE:ddnn:
/INSTALLED
/LOGICAL_UNITS

!Show tasks installed for named
!device.
!Static LUNs for installed task
!qualifier.

/BRIEF
/FULL
/ALL

SHOW TASKS/DYNAMIC

Section 7.12.3.4.1
7.12.3.4.2

SHOW TASKS/DYNAMIC invokes RMD to display on a video terminal
continuing changes in either a single task header or of all or part of
the Active Task List. On a hard-copy terminal,
SHOW TASKS/DYNAMIC
provides a snapshot display. See main text for more information.

9-38

QUICK REFERENCE
Format to display individual task information
SHOW TASK:taskname/DYNAMIC[/qualifier]
Command Qualifier
/RATE:n

!Rate in seconds for display change; default n=l.

Format to display Active Task List
SHOW TASKS/ACTIVE/DYNAMIC[/qualifier[s]]
Command Qualifiers
/OWNER:ddnn:
ALL
/PRIORITY :n
/RATE:n

!Default is ALL.
!Highest priority to display; default n=250.
!Rate in seconds for display change; default n=l.

SHOW TERMINAL

Section 3.8.2

SHOW TERMINAL displays information
terminals on your system.

about

your

terminal

and

other

Format
SHOW TERMINAL[:ttnn:] [/qualifier]

!Without qualifier, displays all
!attributes of the terminal;
!default ttnn:=TI:.

Command Qualifiers
/[NO]ADVANCED VIDEO
/[NO]ANSI CRT/[NO]AUTOBAUD
/[NO]ASR33
/[NO]ASR35
/[NO]BLOCK MODE
/[NO]BROADCAST
/CLI:cliname
/[NO]CRFILL
/DCL
/[NO]DEC CRT
/DTCOl /[NO]ECHO
/[NO]EDIT MODE
/[NO]EIGHT BIT
/[NO]ESCAPE
/[NO]FORM FEED
/[NO]FULL-DUPLEX
/HOSTSYNC/ [NO] HARDCOPY
/[NO]HOLD SCREEN
/HT
/[NO]INTERACTIVE
/[NO]KSR33

!DECnet host terminal

9-39

QUICK REFERENCE
/[NO]LA12
/[NO]LA24
/[NO]LA30P
/[NO]LA30S
/[NO]LA34
/[NO]LA36
/[NO]LA38
/[NO]LASO
/[NO]LAlOO
/[NO]LA120
/[NO]LA180S
/[NO]LA210
/[NO]LFFILL
/LN03
/LQP02
/LQP03
/[NO]LOCAL
/LOGGED ON
/[NO]LOWERCASE
/MCR
/MODEL
/PAGE LENGTH
/[NO]PARITY
/[NO]PASSALL
/[NO]PASTHRU
/[NO]PRIVILEGE
/PRINTER PORT
/PRO SERIES
/[NOTREGIS
/[NO]SOFT CHARACTERS
/[NO]REMOTE
/[NO]SCOPE
/[NO]SLAVE
/SPEED
/[NO]TAB
/TI:
/TT
/[NO]TTSYNC
/[NO]TYPE AHEAD
/[NO]UPPERCASE
/[NO]VTOS
/[NO]VTSO
/[NO]VT52
/[NO]VTSS
/[NO]VT61
/[NO]VTlOO
/[NO]VTlOl
/[NO]VT102
/[NO]VT105
/[NO]VT125
/[NO]VT131
/[NO]VT132
/[NO]VT200 SERIES
/WIDTH
/[NO]WRAP

!NOLOWER same as /UPPER and is
!default.

!All real terminals
!/NOUPPERCASE same as /LOWERCASE.

SHOW USERS

Section 8.1.6

SHOW USERS displays all currently logged-in terminals,
including
DECnet host terminals and virtual terminals, with the default UFO and
login UIC for each.

9-40

QUICK REFERENCE
Format
SHOW USERS

Section 7. 7

START

START resumes execution of a task stopped by a STOP$S directive.
Format
START [/qualifier]

[task name]

!Taskname defaults to TTnn.

Command Qualifier
/TERMINAL:ttnn:

!Privileged

START/PROCESSOR
See the RSX-llM/M-PLUS System Management Guide.
START/PROCESSOR starts a processor, batch processor, output processor,
or card-reader processor. Privileged.
Format
START/processortype processorname[/qualifier[s]]
Processortypes:
APPLICATIONS PROCESSOR
BATCH PROCESSOR.
CARD READER
DEVICE
INPUT
PRINTER
PROCESSOR

!INPUT is synonym.
!PRINTER is synonym.
!CARD READER is synonym.
!DEVICE is synonym.

Command Qualifiers
/FORMS:n
/CONTINUE
/RESTART
/NEXT
/TOP OF FILE
/BACKSPACE:n
/FORWARDSPACE:n
/PAGE:n
/ALIGN

!Overrides value set on
!initialization.
!Default

9-41

QUICK REFERENCE
START/QUEUE
See the RSX-llM/M-PLUS System Management Guide.
START/QUEUE starts a queue. Privileged.
Format
START/QUEUE queuename

START/QUEUE/MANAGER
See the RSX-llM/M-PLUS System Management Guide.
START/QUEUE/MANAGER starts the Queue Manager. Privileged.
Format
START/QUEUE/MANAGER

START/UNBLOCK

Section 7.7.1

START/UNBLOCK continues the execution of a task blocked by the
STOP/BLOCK command. Nonprivileged users can unblock any task running
from their own terminal.
Privileged users can unblock any task.
See
main text.
Format
START/UNBLOCK [taskname]

STOP/ABORT
See the RSX-llM/M-PLUS Batch and Queue Operations Manual.
STOP/ABORT stops the curr~nt job
Privileged users can stop any job.
own jobs.

on a line printer immediately.
Nonprivileged users can stop their

Format
STOP/ABORT printer[:]

9-42

QUICK REFERENCE
Section 7.6

STOP/BLOCK

STOP/BLOCK blocks an installed running task.
The task no longer
executes or competes for memory.
Nonprivileged users can block tasks
running from their own terminals.
Privileged users can block any
task. See main text.
Format
STOP/BLOCK [taskname]

STOP/PROCESSOR
See the RSX-llM/M-PLUS System Management Guide.
STOP/PROCESSOR stops a processor, batch
processor,
card-reader
processor, printer, or other output processor. Privileged.
Format
STOP/processortype processorname[/qualifier[s]]
Processor types:
APPLICATIONS PROCESSOR
BATCH PROCESSOR.
CARD READER
DEVICE
INPUT
PRINTER
PROCESSOR

!INPUT is synonym.
!PRINTER is synonym.
!CARD READER is synonym.
!DEVICE is synonym.

Command Qualifiers
/ABORT
/FILE END
/JOB END
/PAUSE

!See main text

STOP/QUEUE
See the RSX-llM/M-PLUS System Management Guide.
STOP/QUEUE stops queues.

Privileged.

Format
STOP/QUEUE queuename

9-43

QUICK REFERENCE
STOP/QUEUE/MANAGER
See the RSX-llM/M-PLUS System Management Guide.
STOP/QUEUE/MANAGER stops the Queue Manager.

Privileged.

Format
STOP/QUEUE/MANAGER

!Marks QMG for stop after current job.

Command Qualifier
/ABORT

!Stops QMG immediately.

Section 4.4.1

TYPE

TYPE prints selected files on your terminal.
Format
TYPE [/qualifier[s]]filespec[s]
Command Qualifiers
!Suppresses error messages
!Allows other users to access file
!while you type it.
!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!File specification can
!include wildcards.

/NOWARNINGS
/SHARED
/DATE:dd-mmm-yy
/SINCE:dd-mmm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mm-yy
/TODAY
/EXCLUDE:filespec

Section 7.11

UNFIX

UNFIX frees a fixed task or region from memory.

Privileged.

Format
UNFIX taskname

!Can be region name.

9-44

QUICK REFERENCE
Section 4.4.5

UNLOCK

UNLOCK unlocks locked files.
Locked files are files that have been
improperly closed.
They are identified by an L in the directory
listing.
Format
UNLOCK [/qualifier[s]] filespec[s]
Command Qualifiers
/NOWARNINGS
/DATE:dd-mmm-yy
/SINCE:dd-rmnm-yy
/THROUGH:dd-mmm-yy
/SINCE:dd-mmm-yy/THROUGH:dd-mmm-yy
/TODAY
/EXCLUDE:filespec

!Suppresses error messages
!Given day only
!From given day through current day
!From beginning through given day
!From given day through given day
!Today only
!File specification can
!include wildcards.

9-45

APPENDIX A
COMMON ERROR MESSAGES

The following error messages are common to many DCL commands.
They
may appear on your terminal preceded by a 3-letter code identifying
the system component that detected the error.
This can be DCL or the
first three letters of the command itself. This code appears here as
yyy.
Most of the error messages with the word "expected" in them reprint
the command on your terminal with a circumflex (A) pointing to the
error. Sometimes the circumflex points to the character just past the
last successfully parsed command element.
Many of the explanations refer to the Radix-50 character set.
The
Radix-50 characters are the uppercase alphabet, the numerals 0 through
9, the dollar sign ($),and the period (.).
Many other error messages are included in the descriptions of the
commands that produce the errors. Many system tasks also issue error
messages.
These messages are explained elsewhere in the documentation
set.
In particular, many I/O errors return error messages as code
numbers. These errors are explained in the system Mini-Reference and
are discussed further in the I/O documentation. The RSX-llM/M-PLUS
MCR Operations Manual and the RSX-llM/M-PLUS Utilities Manual also
contain explanations of many errors.
yyy -- Allocation failure - no contiguous space
Explanation:
Not enough contiguous space
output volume for the file being copied.

available

the

User Action: Delete any files no longer required on the output
volume and retry the command. You may need to use the BACKUP
command or the DSC utility to compress the files on the output
disk.
yyy

Allocation failure on output file
or

yyy

Allocation failure -- no space available
Explanation:
Not enough space is available on the output
for the file being copied.

volume

User Action: Delete any files no longer required on the output
volume and retry the command. You may need to use the BACKUP
command or the DSC utility to compress the files on the output
disk.

A-1

COMMON ERROR MESSAGES
yyy -- A-Z expected
Explanati9n:
character.

The

command

typed

included

nonalphabetic

User Action:

Check command for proper syntax and reenter.

yyy -- A-Z and/or 0-9 expected
Explanation:
character.

The command as

typed

included

nonalphanumeric

User Action:

Check command for proper syntax and reenter.

yyy -- Bad error message
Explanation:

Some unusual condition has caused an error.

User Action:
Notify your operator or system manager and make
ready to send in a Software Performance Report (SPR). Record the
command that caused the error and other information on activity
at your terminal at the time.
yyy -- Bad use of wild cards in destination file name
Explanation: A wildcard (*) was specified
where it is.not permitted.

for

User Action: Reenter the command with a
file specification for the output file.

complete

and

explicit

UFD

found

output

file

yyy -- Cannot find directory file
Explanation: The command
current volume.

specified

not

User Action: Reenter the command after checking for the
UFD and correct volume.

the

correct

yyy -- Cannot find files
Explanation: The file or files specified in the command are
in the designated directory.

not

User Action:
command line.

the

Check

the

file

specification

and

reenter

yyy -- Cannot rename from one device to another
Explanation:
devices.

The command

attempted

User Action: Use the COPY command to
device to another and rename it.

rename

move

the

file

across

from

one

yyy -- Cannot truncate this f iletype
Explanation: The command attempted to truncate a file that
cannot
be
truncated.
Only files containing fixed-length,
variable-length, or sequenced records can be truncated.
User Action: Check to see if you have named the proper file
retry the command.

A-2

and

COMMON ERROR MESSAGES
yyy -- Close failure on input file
or
yyy -- Close failure on output file
Explanation: A file named in the command could not
closed. The file is locked by PIP.

properly

User Action: Use UNLOCK to unlock the file.
Determine the cause
of the error and correct it if you can.
You may need to check
the validity of the file structure with the VFY utility.
yyy -- Command function not unique
Explanation: The command as typed did not include
characters to identify some command function.
User Action:

sufficient

Retype command after checking proper syntax.

yyy -- Command line incomplete
Explanation:

The command as typed is not a complete command.

User Action:

Retype command after checking proper syntax.

yyy -- Command syntax error
Explanation:

The command did not conform to the syntax .ules.

User Action:

Check command for proper syntax and reenter it.

yyy -- Conflicting qualifier
Explanation: The command as typed included
conflict with each other in their effect.
User Action:

qualifiers

that

Retype command after checking proper syntax.

yyy -- Contradictory qualifier
Explanation: The command as
typed
included
qualifiers, such as /DELETE and /NODELETE.
User Action:

contradictory

Check for proper syntax and reenter command.

yyy -- Contradictory qualifier in key specification
Explanation: The command included a contradictory
the key definition argument to the /KEY qualifier.
User Action:

qualifier

Check command for proper syntax and reenter.

yyy -- Decimal number expected
Explanation:

The command included a number not in proper format.

User Action: Check command for proper syntax and reenter with
decimal point (.) terminating the number.

A-3

COMMON ERROR MESSAGES
yyy -- Destination expected
Explanation: You did not specify the
the command line.
User Action:
syntax.

destination

parameter

Reenter the command line after checking for

proper

yyy -- Device invalid or not specified
Explanation: The command specified an invalid
device at all when a device name is required.

device

User Action: Check the devices on the system with SHOW DEVICES.
Reenter command after checking for proper syntax. Determine the
cause of the error and correct it if you can.
If you cannot, see
your operator or system manager.
yyy -- Device not in system
Explanation: The command specified a device that is not
current system.
User Action: Check the devices on the system with SHOW
Reenter command after checking for proper syntax.

the

DEVICES.

yyy -- Device not mounted/allocated
Explanation: The command specified a device that is not properly
mounted or allocated for the command to execute.
User Action: Check the status of the device with SHOW DEVICES.
Find the cause of the error and correct it if you can.
It is
likely that you will need to mount the volume on the device.
Nonprivileged users need the volume label to mount the volume.
yyy - Device not terminal
Explanation: The command specified a device other than
a
terminal where a terminal device name is required. TI:
is not
an acceptable terminal device name in all contexts.
User Action:
syntax.

Reenter

the

command

after

checking

for

proper

yyy -- Directory write protected
Explanation: The command attempted to remove an entry from a
directory that is privileged or from a directory on a device that
is write-protected.
User Action: Determine the cause of the error and correct it if
you can.
You may need to enable write access through the device
hardware or change the protection for the directory.
If you
cannot correct the error, see your system manager or operator.
yyy -- Error dispatching command.

DSW

= 'n'

Explanation: An error occurred that was not
by DCL or some invoked task.

explicitly

handled

User Action: Look up the DSW error code in the Mini-Reference or
the RSX-llM/M-PLUS and Micro/RSX Executive Reference Manual.
Determine the cause orthe error and correct it if you can.
If
you cannot, see your system manager or operator.

A-4

COMMON ERROR MESSAGES
yyy -- Explicit output file name required
Explanation:

The command requires an explicit output file name.

User Action: Reenter the
without wildcards.

command

line

proper

syntax

and

yyy -- Extraneous input - Check for proper command structure
Explanation: The command as typed included extraneous input.
The circumflex
(A)
points to the error or just past the last
successfully parsed command element.
User Action:

Reenter the command line in proper syntax.

yyy -- Failed to attach output device
or
yyy -- Failed to detach output device
Explanation: An attempt to attach or detach a record-oriented
output device, such as a terminal or line printer, failed.
This
error _usually means the device is off-line or nonresident.
User Action:
Determine the cause of the error and correct it
you can.
If you cannot, see your operator or system manager.

yyy -- Failed to create output UFO
Explanation:
The command failed to create an entry in a
directory because the device was write-protected or because of a
privilege violation.
User Action: Determine the cause of the error and correct it if
you can.
You may need to enable write access through the device
hardware or change the protection for the directory.
If you
cannot correct the error, see your system manager or operator.
yyy -- Failed to delete file
or
yyy -- Failed to mark file for delete
Explanation:

The command attempted to delete a protected file.

Oser Action: Check for the proper file specification and default
UFO and reenter the command. You may need privilege to delete
the file.
yyy -- Failed to enter new filename
Explanation: The command specified a file that already exists in
the UFO, or the directory is protected.
User Action:

Check for proper syntax and reenter the command.

yyy -- Failed to find files
Explanation: The command specified a file or
not be found as specified.
User Action:
the command.

Check for proper file

A-5

files

specifications

that
and

could
reenter

COMMON ERROR MESSAGES
yyy -- Failed to get time parameters

Explanation:

An internal system problem has occurred.

User Action: Retry the command. If the error recurs, see your
system manager and prepare to submit a Software Performance
Report.
Record the command that caused the error and other
information on activity at your terminal at the time.
yyy -- Failed to read attributes

Explanation: The command specified a
corrupted or protected against access.

volume

that

either

User Action: You may be able to correct the error by making your
defaults the same as the device and UFO of the file you wish to
affect.
You may need to check the validity of the volume with
the VFY utility.
yyy -- Failed to remove directory entry

Explanation: The command attempted to remove an entry
directory that was either protected against access
write-protected device.

from a
or on a

User Action: Determine the cause of the error and correct it if
you can.
You may need to enable write access through the device
hardware or change the protection for the directory.
If you
cannot correct the error, see your system manager or operator.
yyy -- Failed to truncate file

Explanation: The command specified a volume that is corrupted or
is protected against access.
User Action: You may be able to correct the error by making your
defaults the same as the device and UFO of the file you wish to
affect.
You may need to check the validity of the volume with
the VFY utility.
yyy -- Failed to write attributes

Explanation: The command failed to execute because of some I/O
error.
This error can be caused by the unavailability of a
device or of pool space, or by a device error. The device may be
write-locked.
User Action: Determine the cause of the error and correct it
you can.
If you cannot, see your operator or system manager.

A-6

COMMON ERROR MESSAGES
yyy -- File is lost
Explanation:
PIP has removed a file from its UFD,
delete it, and failed to restore the directory entry.

failed

User Action:
Use the VFY utility to run the lost-file
recover the file name.

check

yyy -- Filename or f iletype not specified
Explanation:
The command as typed did not clearly specify a file
name and file type where one or the other or both is required.
This error can be caused if you do not leave a space in front of
a file specification that is a parameter.
User Action:

Retype command after checking for proper syntax.

yyy -- File not locked
Explanation:
locked.

An UNLOCK command specified

file

that

not

User Action:
the command.

Check for the proper file specification and reenter

yyy -- File specification either invalid or not specified
Explanation:
The system could not read a file specification
included in the command. This error often results from a typing
mistake or typing the command in the wrong format.
User Action:

Check for proper syntax and reenter the command.

yyy -- File specification list not available for RMS-11
Explanation: A command to an RMS-11 utility included
one input file specification.
User Action:

than

Check for proper syntax and reenter command.

yyy -- File version number not specified
Explanation:
specified.

The command requires a file version

number

User Action:

Reenter command after checking for proper syntax.

yyy -- Function not unique
Explanation: The command as typed did
characters to identify some function.
User Action:

not

include

sufficient

Retype the command but include more characters.

yyy -- Get command line - Bad @ file name
Explanation:
file.

The command specified an illegal

User Action:
command.

Check for proper file specification and reenter the

A-7

indirect

command

COMMON ERROR MESSAGES
yyy -- Illegal command
Explanation: The command, which is the first word on the command
line, is not part of DCL.
User Action: Check command for proper syntax and
the command fails again, see your system manager.

reenter.

Explanation: The command named a device in an illegal format
contained some other syntax error.

yyy -- Illegal device
1

User Action: Check command for proper syntax and reenter.
Device names are two alphabetical characters followed by an octal
number and a colon.
yyy -- Illegal filespec
Explanation:
not present.

The command required a file specification that

was

User Action: Check command for proper syntax and reenter.
See
Section 4.1.2 for a complete description of a file specification.
Perhaps some other command element is being parsed as a filespec.
Use the prompting version.
yyy -- Illegal job name
Explanation: A command to the Queue Manager named a
improper format.

job

User Action: Check command for proper syntax and reenter.
Job
names include an optional UIC and as many as nine Radix-50
characters. The job name is listed in the SHOW QUEUE display.
yyy -- Illegal, contradictory, or ambiguous qualifier
Explanation: One or more
conflict, or are in error.
User Action:

qualifiers

the

command

are

Check command for proper syntax and reenter.

yyy -- Illegal processor name
Explanation: A command to the Queue Manager named a processor in
an improper format.
User Action: Check command for proper syntax and reenter.
Processor names include as many as six Radix-50 characters.
Processor names are listed in the SHOW PROCESSOR display.
yyy -- Illegal protection code
Explanation: The command
improper format.

specified

protection

code

User Action: Check command for proper syntax and reenter.
Section 4.1.5 for more information on protection codes.

A-8

an
See

COMMON ERROR MESSAGES
yyy -- Illegal qualifier value
Explanation: The command as typed included an improper
to a qualifier.
User Action: Check command for proper syntax
DCL, an argument is preceded by a colon (:).

and

argument

reenter.

yyy -- Illegal queue name
Explanation: A command to the Queue Manager named a queue in
improper format.

User Action: ,Check command for proper syntax and reenter. Queue
names include as many as six Radix-SO characters. Queue names
are listed in the SHOW QUEUE display.
yyy -- Illegal task name
Explanation: The command named a task using a task
illegal format.

name

User Action: Check command for proper syntax and reenter.
names include as many as six Radix-SO characters.

an
Task

yyy -- Illegal use of wildcard character
Explanation: The command included a wildcard (* or %) in a file
specification in a way that would result in unpredictable or
inconsistent output.
User Action: Check command for proper syntax and
may not be able to use the wildcard.

reenter.

You

yyy -- Input device must be a directory device
Explanation:
The command as typed specified a device that is not
a directory device, such as a line printer or magnetic tape.
Directory devices are those on which Files-11 volumes with
directories can be mounted.
User Action:

Correct syntax and reenter command.

yyy -- Input files have conflicting attributes
Explanation: Warning message.
The command operation
but the files named had conflicting attributes.

completed,

User Action:
Use DIRECTORY/ATTRIBUTES to find the attributes of
all input and output files involved. Determine if the conflict
causes any difficulty.
yyy -- Invalid command function
Explanation: The command as typed requested a function
not valid for that command.
User Action:

that

Check command for proper syntax and reenter it.

yyy -- Invalid command parameter
Explanation: The command as typed included a parameter that is
not valid.
In DCL, a parameter is either entered in response to
a prompt or preceded by a space.
User Action:

Check command for proper syntax and reenter.
A-9

COMMON ERROR MESSAGES
yyy -- Invalid file specification list
Explanation: The command included a list of file specifications
in an invalid format.
In general, file specifications in lists
should be separated by commas and, optionally, blanks.
User Action:

Retype command after checking proper syntax.

yyy -- Invalid file specification qualifier
a
file
Explanation: The command included a qualifier to
specification that was not valid.
In DCL, a qualifier is
preceded by a slash (/) •
User Action:

Check for proper syntax and retype the command.

yyy -- Invalid terminal specified
Explanation: A command directed to a specific terminal named the
terminal in an improper format.
User Action: Check the name of the terminal using SHOW USERS and
reenter the command with the proper format.
yyy -- Invalid time or date
Explanation: The command specified a clock or calendar field, or
both, incorrectly.
User Action:

Check for proper syntax and retype the command.

yyy -- Invalid UIC specified
Explanation: The command specified a O, a number including an 8
or 9, or a number greater than 377 (octal) for the group or
member number in a UIC or UFO.
User Action:

Retype command after checking for proper syntax.

yyy -- I/O error on input file
or
yyy -- I/O error on output file
Explanation:

One of the following conditions exists:

•

The device is not on line.

•

The device is not mounted.

•

The hardware has failed.

•

The output volume is full.

•

The input file is corrupted.

User Action: Determine the cause of the error and correct it
you can.
If you cannot, see your operator or system manager.

A-10

COMMON ERROR MESSAGES
yyy -- Key position size or number not specified

Explanation:

The command failed to include the size or number of
a key position in the key definition argument to the /KEY
qualifier.

User Action:

Check command for proper syntax and retype it.

yyy -- Key specification out of sequence

Explanation:

The command included improper
definition argument to the /KEY qualifier.

User Action:

syntax

the

key

Check command for proper syntax and reenter.

yyy -- Magnetic tape file label not specified

Explanation:

The command attempted to initialize a magnetic tape
without specifying the required volume label.

User Action:

Retype command after you have

checked

for

proper

syntax.
yyy -- More command parameters than permitted

Explanation:

The command as typed included too many parameters.

User Action:

Check command for proper syntax and reenter.

yyy -- No such file

Explanation:

The command requested operations
does not exist.

file

that

User Action:

Make sure you have named the file properly.
Check
your defaults to be sure you are looking in the right UFD on the
right device.
You may have made a typing error.
If the desired
file
is
in fact not present, find out why it is not present and
proceed accordingly.

yyy -- Not a directory device

A directory-oriented command named
does not have directories, such a line printer.

Explanation:
User Action:
a UFD.
yyy

device

If you can, reenter the command without

that

specifying

Not logged in

Explanation:

A command was entered at a terminal

that

was

not

logged in.

User Action:

Only LOGIN, HELLO and HELP execute on terminals
that are not logged in.
If you do not know how to log in, type
HELP.
If you know how to log in, do so and reenter the command.

yyy

Numeral expected

yyy

Numeral required

Explanation:

Command included nonnumeric
characters
position where numerals are required or expected.

User Action:

Check command for proper syntax and reenter.

A-11

COMMON ERROR MESSAGES
yyy -- Octal number expected
Explanation: The command included a number with an 8 or 9
an octal number was expected.
User Action:

where

Check command for proper syntax and reenter.

yyy -- Open failure on.file
Explanation:
reason.

The system could not open a required file for

some

User Action: Check the UFO to be sure that the file is present,
not locked, and in the proper format.
If the file is locked, it
may be corrupted or contain bad data. Determine the cause of the
error and correct it if you can.
If you cannot, see your
operator or system manager.
yyy -- Output device must be a directory device
Explanation: The command as typed specified a device that is not
a directory device, such as a line printer or magnetic tape.
Directory devices are those on which Files-11 volumes with
directories can be mounted.
User Action:

Correct syntax and reenter command.

yyy -- Partition busy
Explanation: The partition into which a task was to be fixed was
occupied by a running task. The requested task thus could not be
fixed.
User Action: Wait until the partition is no longer busy or
out why the partition is busy and proceed accordingly.

find

yyy -- Primary key not specified
Explanation: A command affecting an indexed file failed to
include a primary key.
In many such commands, you cannot specify
any action on an alternate key without first identifying the
primary key.
User Action:

Check for proper syntax and reenter command.

yyy -- Privilege violation
·Explanation: The command was a privileged command
nonprivileged terminal.

issued

User Action: None.
If you must have the function
find a privileged user to issue the command for you.

requested,

yyy -- Qualifier inconsistent with compiler
Explanation: A compiler command included a
qualifier
not
acceptable by that compiler, such as a FORTRAN/F4P command
including a /LINE NUMBERS qualifier, which is for the FOR
compiler only.
User Action: Check the command for proper syntax and try it
again.
Remember that your command may be specifying a compiler
by default.

A-12

COMMON ERROR MESSAGES
yyy -- Qualifier not available for this command format
Explanation: The command included a qualifier that is invalid in
the current context of the command.
The context is usually
determined by some other qualifier in the command.
User Action:

Reenter command after checking for proper syntax.

yyy -- Qualifier not unique
Explanation: The command as typed did not include sufficient
characters to identify some qualifier.
In DCL, qualifiers are
preceded by a slash (/) •
User Action:

Retype the command, but include more characters.

yyy -- Qualifier value invalid here
Explanation: The command·s as typed included an inappropriate
argument to a qualifier.
In DCL, an argument is usually preceded
by a colon ( : ) •
User Action:

Check command for proper syntax and reenter.

yyy -- Radix-SO expected
Explanation~

The command included a non-Radix-SO character where
Radix-SO required.

User Action: Reenter the command using proper syntax.
The
Radix-SO characters are the uppercase alphabet, the numbers 0
through 9, the dollar sign ($),and the period (.).
yyy -- Repeated command parameter
Explanation: The command as typed included one parameter more
than once.
In DCL, a parameter is preceded by a blank or prompt.
User Action:

Retype command after checking for proper syntax.

yyy -- Repeated key specification
Explanation: The command as typed included the
same
key
specification more than once in the key definition argument to
the /KEY qualifier.
User Action:

Retype command after checking for proper syntax.

yyy -- Repeated keyword in key specification
Explanation: The command as typed included the same keyword more
than once in the key definition argument to the /KEY qualifier.
User Action:

Retype command after checking for proper syntax.

yyy -- Repeated magnetic tape file label
Explanation:
than once.

The command included the required volume label more

User Action:
the command.

Check command syntax for

A-13

correctness

and

reenter

COMMON ERROR MESSAGES
yyy -- Repeated qualifier
Explanation: The command specified the same qualifier more
once.
In DCL, a qualifier is preceded by a slash (/).
User Action:
it is right.

than

Reenter command after checking the syntax to see if

yyy -- Required parameter not specified
Explanation: The command cannot
execute
without
parameters, such as a file specification or attribute.
parameter is preceded by a blank or prompt.
User Action: Retry the command, using the prompts.
for all required parameters.

required
In DCL, a

DCL

prompts

yyy -- Required qualifier not specified
Explanation:
The command requires a qualifier that it does
include.
In DCL, a qualifier is preceded by a slash (/).
User Action:

not

Check for proper syntax and reenter the command.

yyy -- Required qualifier value not specified
Explanation: A qualifier to the command requires that you state
a numerical argument.
In DCL, an argument is usually preceded by
a colon (:).
User Action:

Retype command after checking for proper syntax.

yyy -- Required value not specified for position size or number
Explanation: The command failed to include a required
the key definition argument to the /INDEXED qualifier.
User Action:

value

Check command for proper syntax and reenter.

yyy -- Sorry, line too long
Explanation: DCL commands are translated for execution by MCR or
another system task or utility.
This error is caused by a
translated command line that the destination task cannot handle.
User Action: Check command syntax to see if you are specifying
elements that can be defaulted. Check to see if you can enter
the command twice with different qualifiers to accomplish in two
commands what you cannot accomplish in one. You may have to
enter the command in MCR format or the format of the task or
utility you are seeking to invoke. Check the translated command
line with SET DEBUG.
yyy -- Sorry, "-" not supported in Indirect
Explanation: An indirect command file
included an
illegal
element, as identified by the quoted part of the message.
User Action:

Check indirect command file for correctness.

A-14

COMMON ERROR MESSAGES
yyy -- Sorry, low pool
Explanation:
The command
could
not
execute
because
of
insufficient space in the system pool (dynamic storage region) •
User Action:
The pool is the Executive's data base.
In general,
each task, including commands, uses a certain amount of pool.
If
the pool is full or badly fragmented, there may not be sufficient
space for
the command to execute.
Usually, pool problems clear
up spontaneously if you wait.
Retry the command after an
interval.
If
it still does not
execute,
see your operator or system manager.
You should not
attempt to execute any other task, not even an ABORT or LOGOUT,
when the pool is low.
These tasks too absorb pool.
yyy -- Sorry, task active
Explanation:
The command required some
taken on an active task.

action

that

cannot

User Action:
Determine the cause of the error and correct it
if
you can.
If you cannot, see your system manager or operator.
Check the task with the various SHOW TASK commands,
or SHOW
MEMORY.
yyy -- Sorry, task not installed
Explanation:
installed.

The command attempted to invoke a task that was not

User Action:
Try running the task with a command in the RUN $
form.
Determine the cause of the error and correct it if you
can.
If you cannot, see your system manager or operator.
yyy -- Syntax error
Explanation:
The command
included some error
in typing
specification, such as a letter where a number should appear.
User Action:

Check for proper syntax and reenter command.

yyy -- Version must be explicit or

"*"

Explanation:
The command syntax requires that the version number
of the file must be specified explicitly or as a wildcard ( * ) .
User Action:
Reenter
correctly expressed.

the

command

with

the

version

number

yyy -- Wildcards not permitted
Explanation: Command included a wildcard (* or %)
where it is not permitted.
User Action:

context

Check for proper syntax and reenter command.

yyy -- Zero value not valid for key size or number
Explanation:
The command
included a
zero
definition argument to the /KEY qualifier.
User Action:

value

the

Check command for proper syntax and reenter.

A-15

key

APPENDIX B
FUNCTIONS INITIATED BY DCL COMMANDS

Most DCL commands initiate functions that are actually performed by
MCR or by some other system task or utility. The following table
gives these relationships, with any necessary comments.

DCL Command

MCR Command,
Task, or Utility

ABORT

ALLOCATE

ALLocate

ANALYZE/CRASH_DUMP

CDA

ANALYZE/ERROR_LOG

ERL

ANALYZE/MEDIA

BAD

APPEND

PIP

ASSIGN

ASsigN

Assign logical name

ASSIGN/QUEUE

QMG

Assign queue to
processor

ASSIGN/REDIRECT

REDirect

Redirect device

ASSIGN/TASK

REAssign

Alter LUN assignments

BACKUP

BRU

BASIC

BAS, BP2

BROADCAST

BROadcast

CANCEL

CANcel

COBOL

COB

CONTINUE

RESume

CONVERT

RMS CNV

COPY

PIP

CORAL

COR

CREATE

PIP, FCS

CREATE/DIRECTORY

UFO
B-1

Comments

FUNCTIONS INITIATED BY DCL COMMANDS

DCL Command

MCR Command,
Task, or Utility

DEALLOCATE

DEAllocate

DEASSIGN

ASsigN

Deassign logical name

DEASSIGN/QUEUE

QMG

Eliminate assignment of
queue to processor

DELETE

PIP

Delete files

DELETE/ENTRY

QMG

DELETE/JOB

QMG

DELETE/PROCESSOR

QMG

Delete despooler task

DELETE/QUEUE

QMG

Delete queue

DIFFERENCES

CMP

DIRECTORY

PIP
RMS DSP

Comments

/ATTRIBUTES qualifier

DISMOUNT

DisMOunt

EDIT

EDT, EDI, KEO, SLP

FORTRAN

FOR, F4P, F77

FIX

HELP

HELlo

HOLD/ENTRY

QMG

HOLD/JOB

QMG

INITIALIZE

INitvolume

Create Volume

INITIALIZE/PROCESSOR

QMG

Set up despooler task

INITIALIZE/QUEUE

QMG

INITIALIZE/UPDATE

HO Me

INSTALL

INS tall

LIBRARY

LBR

LINK

TKB

HELlo

LOGOUT

BYE

As part of HELlo, HELP
can run on terminals
that are not logged in.

Alter volume's
home block

Task Builder. May be
more than one on
system. FTB is Fast TKB.

B-2

FUNCTIONS INITIATED BY DCL COMMANDS

DCL Command

MCR Command,
Task, or Utility

MACRO

MAC

MCR

MOUNT

MOUnt

QMG

PURGE

PIP

RELEASE/ENTRY

QMG

RELEASE/JOB

QMG

REMOVE

REMove

RENAME

PIP

REQUEST

BROadcast

RUN

RUN INS

SET [DAY] TIME

TIMe

SET DEFAULT

SET /UIC

SET DEVICE

DEVice

SET FILE

PIP

SET GROUPFLAGS

FL Ag

SET HOST

SET /HOST

SET PARTITION

PAR, SET /MAIN,
SET /PAR, SET SUB

SET PRIORITY

ALTer

SET PROTECTION

PIP

SET QUEUE

QMG

SET SYSTEM/DIRECTORY

SET /SY SU IC

SET SYSTEM/EXTENSION LIMIT

SET /MAXEXT

SET SYSTEM/NETWORK_UIC

SET /NETUIC

SET SYSTEM/NOLOGINS

SET /NOLOGON

SET SYSTEM/PACKETS

SET /MAXPKT

SET SYSTEM/POOL

SET /POOL

SET SYSTEM/POOL/LIMITS

SET /PLC TL

SET TERMINAL

SET /attribute

SHOW ASSIGNMENTS

ASsigN

B-3

Comments

SET for UFO
ASN for SY:

FUNCTIONS INITIATED BY DCL COMMANDS

DCL Command

MCR Command,
Task, or Utility

SHOW CLOCK_QUEUE

CLQ

SHOW [DAY] TIME

TIM

SHOW DEFAULT

SET /UIC
ASsigN

SET for UFO
ASN for SY:

SHOW DEVICES

DEV
SET /PUB
SET /BUF

/PUBLIC qualifier
/WIDTH qualifier

SHOW GROUPFLAGS

FL Ag

SHOW HOST

SET /HOST

SHOW MEMORY

RMD

SHOW PARTITIONS

PAR

SHOW PROCESSOR

QMG

SHOW QUEUE

QMG

SHOW SYSTEM/CL I

CLI /SHOW

SHOW SYSTEM/DIRECTORY

SET /SYSUIC

SHOW SYSTEM/EXTENSION LIMIT
-

SET /MAXEXT

SHOW SYSTEM/NETWORK_UIC

SET /NETUIC

SHOW SYSTEM/POOL

SET /POOL

SHOW SYSTEM/POOL/LIMITS

SET /PLC TL

SHOW TASKS/ACTIVE

ACT

SHOW TASK:taskname/ACTIVE

ATL

SHOW TASKS/DYNAMIC

RMD

SHOW TASKS/INSTALLED

TAS

SHOW TASKS/INSTALLED/FULL

TAL

Comments

Resource Monitoring
Display

SHOW TASK:taskname/INSTALLED TAS
SHOW TERMINAL

DEV

SHOW TERMINAL/attribute

SET /attribute

SHOW USERS

DEV

SORT

SRT

START

UNS

START/PROCESSOR

QMG

SORT-11

B-4

FUNCTIONS INITIATED BY DCL COMMANDS

DCL Command

MCR Command,
Task, or Utility

START/QUEUE

QMG

START/QUEUE/MANAGER

QMG

START/UNBLOCK

UNBLocK

STOP/ABORT

QMG

STOP/BLOCK

Block

STOP/PROCESSOR

QMG

STOP/QUEUE

QMG

STOP/QUEUE/MANAGER

QMG

TYPE

PIP

UNFIX

UNFix

UNLOCK

PIP

B-5

Comments

INDEX

Abbreviation
DCL, 1-7
ABORT command, 7-16 to 7-20, 9-2
Access
types, 4-9
Account file, 3-9
Account File Maintenance Program
See ACNT
ACNT, 3-3, 3-4, 3-9
ACP, 5-3
DECtape, 5-39
disk, 5-39
foreign, 5-39
magnetic tape, 5-39
specifying, 5-39
ACT command
MCR, 3-2
Active Task List
See ATL
ALLOCATE command, 5-31 to 5-33,
9-2
ALTMODE key, 3-10
Ampersand (&) , 3-14
ANALYZE/CRASH DUMP command, 9-2
ANALYZE/MEDIA-command, 5-14 to
5-20, 9-3
Ancillary Control Processor
See ACP
Angle bracket
left (<) , 3-13
right (>), 3-13
CLI prompt, 3-13
ANSI, 5-3
file name, 1-9
magnetic tape
preparing, 5-12
APPEND command, 4-70 to 4-71, 9-4
Arrow key, 3-15
ASSIGN command, 5-21 to 5-23, 9-4
ASSIGN/QUEUE command, 9-5
ASSIGN/REDIRECT command, 5-24 to
5-26, 9-5
ASSIGN/TASK command, 5-27 to 5-28,
9-5
Assignment
device
global, 5-8
local, 5-8
login, 5-8
logical-device
displaying, 2-5, 5-86

Asterisk (*), 3-14, 4-6 to 4-8
At sign (@), 3-14
ATL
displaying task information,
7-57
task
displaying information, 7-59
BACK SPACE key, 3-11
Backslash (), 3-15
Backup and Restore Utility
See BRU utility
BACKUP command, 5-73 to 5-85, 9-5
to 9-7
error messages, 5-83 to 5-85
qualifiers, 5-75 to 5-82
Backup operation, 5-73
Backup set, 5-73
Bad block
locating, 5-14
BADBLK.SYS file, 5-11
Base number
in DCL, 1-8
BITMAP.SYS file, 5-11
Brace ({ }) , 3-15
BROADCAST command, 3-28 to 3-31,
9-7
error messages, 3-30
examples, 3-29
qualifiers, 3-29
BRU utility, 5-83
CANCEL command, 7-23, 9-7
CAPS LOCK key, 3-12
CBD
entry
removing, 7-37
Checkpoint file, 5-88
Circumflex () , 3-13, 3-16
CL:, 5-5
CLI, 1-1
changing, 3-3
displaying information, 8-6
Clock queue, 7-11
entry
displaying information, 7-65
eliminating, 7-23
inserting, 7-23
CMP utility, 4-77
CO:, 5-5

Index-1

INDEX
Colon (:) , 3-14
DCL, 1-9
Command
aborting, 7-16
DCL
abbreviation, 9-1
function, 1-15 to 1-17
translating to MCR, 1-13 to
1-14, 2-8, B-1
Command line
continuing, 3-10
DCL
comment, 1-12
quoting string, 1-9
terminating, 3-10
Command line interpreter
See CLI
Comment
command line
DCL, 1-12
Common
shareable
building, 6-20
Common Block Directory
See CBD
Compiler, 6-2
Console Logging, 5-5
Continuation line
See Line continuation
CONTINUE command, 7-21 to 7-22,
9-7
Control key
See CTRL key
Controller, 5-1
CONVERT command, 4-50 to 4-56,
9-8
COPY command, 4-42 to 4-46, 9-8
COPY key, 3-12
Copying
file, 4-42
CORIMG.SYS file, 5-11
Create access, 4-10
CREATE command, 4-10, 4-11 to
4-12, 9-9
CREATE/DIRECTORY command, 4-13 to
4-15, 9-9
examples, 4-14
qualifiers, 4-13 to 4-14
CTRL key, 3-16
CTRL/C, 3-10, 3-17
CTRL/G, 3-20
CTRL/I, 3-20
CTRL/K, 3-20
CTRL/L, 3-20
CTRL/M, 3-20

CTRL/O, 3-16, 3-18
CTRL/Q, 3-17
CTRL/R, 3-19
CTRL/S, 3-17
CTRL/U, 3-19
CTRL/X, 3-20
CTRL/Z, 3-10, 3-16, 3-18
Cursor
controlling, 3-15
Cursor-control key, 3-15
Date
related qualifiers, 4-8
system
displaying, 2-1, 8-3
setting, 2-1, 8-1
Date format
DCL, 1-8
DCB, 5-5
DCL, 1-1
abbreviations, 1-7
colon (:) , 1-9
command
abbreviation, 9-1
function, 1-15 to 1-17
translating to MCR, 2-8, B-1
command line, 1-2
quoting string, 1-9
comment, 1-12
dates, 1-8
DECnet, 1-10
equal sign (=) , 1-9
error messages
common, A-1
errors, 1-14
line continuation, 1-12, 3-10
number
decimal, 1-8
octal, 1-8
parameter, 1-8
qualifier, 1-3 to 1-4
quotation mark (")
using, 1-9
RSX-llM, 1-19
SET commands, 2-1
SHOW commands, 2-1
underscore ( ) , 1-8
VAX/VMS, 1-19
DCL command, 1-6
DEALLOCATE command, 5-34 to 5-35,
9-9
DEASSIGN command, 5-29 to 5-30,
9-10
DEASSIGN/QUEUE command, 9-10

Index-2

INDEX
DECnet
DCL, 1-10
directory
displaying, 8-6
setting, 8-4
DECtape, 5-3
ACP, 5-39
DECwriter II, 3-1
Delete access, 4-10, 4-84
DELETE command, 4-35 to 4-38,
9-10
DELETE key, 3-11
DELETE/ENTRY command, 9~11
DELETE/JOB command, 9-11
DELETE/processortype command,
9-11
DELETE/QUEUE command, 9-12
Density
volume
changing, 5-70
setting, 5-59
Device, 5-1, 5-4, 5-5
allocating, 5-31
attribute
displaying, 5-91
setting, 5-88
buffer
setting, 5-89
deallocating, 5-34
default, 4-2, 4-4
displaying, 4-82
setting, 4-80
displaying information, 2-3,
5-91
file
default number, 5-62
global assignment, 5-8
industrial, 5-4
laboratory, 5-4
list, 5-2
local assignment, 5-8
logical assignment
displaying, 2-5, 5-86
logical name, 5-5, 5-6, 5-8
assigning, 5-8, 5-21
deleting, 5-29
table, 5-8
login assignment, 5-8
mass-storage, 5-3
name, 5-1
owner, 5-9
peripheral, 5-1
physical, 5-4
private, 5-9, 5-12
allocating, 5-31

Device
private (Cont.)
deallocating, 5-34
protection, 5-12
pseudo, 5-1, 5-4, 5-5, 5-5 to
5-6
list, 5-6
name, 5-5
public, 5-9, 5-13
setting, 5-89
random-access, 5-3
redirecting, 5-5
output, 5-24
sequential-access, 5-3
setting default, 2-5
shareable, 5-9, 5-12
unit record, 5-3
unowned, 5-9, 5-13
Device Control Block
See DCB
Device driver, 5-1
name, 5-4
DIFFERENCES command, 4-72 to 4-77,
9-12
DIGITAL Command Language
See DCL
DIGITAL Standard Editor
See EDT
Directory, 4-1
creating, 4-10, 4-13
DECnet
displaying, 8-6
setting, 8-4
default, 4-2, 4-4
displaying, 4-82
setting, 4-80
displaying information, 4-26
setting default, 2-5
system, 7-6, 8-7
displaying, 2-8, 8-6
setting, 2-8, 8-3, 8-7
DIRECTORY command, 4-26 to 4-34,
9-13
examples, 4-29 to 4-33
qualifiers, 4-27 to 4-29
Disk, 5-3
ACP, 5-39
bad blocks
locating, 5-14
preparing, 5-9
DISMOUNT command, 5-53 to 5-56,
9-13
Dollar sign ( $)
DCL prompt, 3-13

Index-3

INDEX
Driver
device, 5-1
Dynamic storage region
See Pool
Echo, 3-9
EDI, 4-23
EDIT command, 4-15, 4-16, 9-14
EDIT/EDI command, 4-23, 9-14
EDIT/editor command, 4-23, 9-14
K52, 4-24
KEO, 4-24
sos, 4-23
TECO, 4-23
EDIT/EDT command, 4-16, 9-14
EDIT/SLP command, 4-20, 9-14
Edi ting
file, 4-16, 4-23
Editor
EDI, 4-23
EDT, 4-16
K52, 4-24
KEO, 4-24
sos, 4-23
TECO, 4-23
EDT, 4-16
ENTER key, 3-15
Entry point name, 6-28
removing, 6-43
Entry point table
See EPT
EPT, 6-28
Equal sign {=), 3-14
DCL, 1-9
Error
DCL, 1-14
Error messages
DCL
common, A-1
ESC key, 3-10
ESCAPE key, 3-10
Event flag
group global, 6-51
creating, 6-52
deleting, 6-52
displaying, 6-53
Extend access, 4-10, 4-84
Extension
file
See File type
FllACP, 5-3, 5-8
Fast Task Builder
See FTB

File, 4-1, 5-1
access, 2-7
access types, 4-9, 4-84
attribute
setting, 4-87
checkpoint, 5-88
comparing, 4-72
copying, 4-42
default number, 5-62
deleting, 4-35
displaying, 4-57
displaying information, 4-26
editing, 4-16, 4-23
excluding, 4-9
library, 6-28
locked, 4-78
maximum number
changing, 5-71
setting, 5-62
object
binary, 6-2
printing, 4-60
protection, 4-9
code, 4-9, 4-83
default, 4-84
setting, 4-83, 5-38, 5-63,
5-64, 5-71
purging, 4-39
renaming, 4-4 7
sequential
appending, 4-70
creating, 4-10, 4-11
source
maintaining, 4-20
system, 5-10
system library, 6-2
task image
name
specifying, 7-28
TKB map, 6-2
producing, 6-13
unlocking, 4-78
version number, 4-3
changing, 4-47
default, 4-4
File Compare Utility
See CMP utility
File header, 4-2
allocating, 5-60
maximum number, 5-60
File name, 4-3
ANSI, 1-9
changing, 4-47
File protection
setting, 2-6

Index-4

INDEX
Host system (Cont.)
setting, 1-10 to 1-11
Hyphen (-), 3-14

File record
moving, 4-50
File Set ID, 5-38, 5-48
File Set Identifier
See File Set ID, 5-38
File specification, 4-2
defaults, 4-4
wildcards, 4-6
File type, 4-3
changing, 4-47
default, 4-4
standard, 4-5
Files-11
volume, 5-3
backing up, 5-73
formatting, 5-57
level 401, 5-62
level 402, 5-62
restoring, 5-73
FIX command, 7-38 to 7-39, 9-15
Floating qualifier, 1-3 to 1-4
Form feed, 3-20
FTB, 6-11

Index file
locating, 5-61
INDEXF.SYS file, 5-10
Indirect, 1-17
Indirect command file
DCL, 1-17
Indirect Command Processor
See Indirect
INITIALIZE command, 5-57 to 5-69,
9-16
error messages, 5-66 to 5-69
qualifiers, 5-58 to 5-65
INITIALIZE/PROCESSOR command
input, 9-17
output, 9-17
INITIALIZE/QUEUE command, 9-18
INITIALIZE/UPDATE command, 5-70
to 5-72, 9-18
qualifiers, 5-70 to 5-71
INSTALL command, 7-28 to 7-36,
9-19
error messages, 7-31 to 7-36
qualifiers, 7-28 to 7-30
Install-run-remove form
RUN command, 7-3, 7-7

GEN partition, 7-2
Global assignment
device, 5-8
Global symbol, 6-28
removing, 6-43
Group global event flag, 6-51
creating, 6-52
deleting, 6-52
displaying, 6-53

Journal file, 4-17

HELP command, 1-4 to 1-6, 3-21 to
3-24, 9-15
examples, 3-23 to 3-24
qualifiers, 3-22
Help file
example, 3-25 to 3-27
format, 3-24 to 3-27
writing, 3-24 to 3-27
HOLD qualifier
LOGOUT command, 3-8
HOLD/ENTRY command, 9-16
HOLD/JOB command, 9-16
Home block
volume, 5-57
changing, 5-70
displaying information, 5-71
HOME command, 5-70
HOME utility
See HOME command
Host system
displaying, 1-11 to 1-12

Key
ALTMODE, 3-10
arrow, 3-15
BACK SPACE, 3-11
CAPS LOCK, 3-12
COPY, 3-12
CTRL, 3-16
cursor-control, 3-15
DELETE, 3-11
ENTER, 3-15
ESC, 3-10
ESCAPE, 3-10
LINE FEED, 3-11
NO SCROLL, 3-12
NUMBERS, 3-15
PERIOD, 3-15
PF, 3-15
REPEAT, 3-12
repeating, 3-12
RETURN, 3-2, 3-10
RUBOUT, 3-11
SCROLL, 3-12
SEL, 3-10

Index-5

INDEX
Key (Cont.)
SHIFT, 3-12
TAB, 3-20
Keyboard
terminal, 3-1, 3-9
Keypad
terminal, 3-1, 3-15
VT200-series, 3-15
LA36, 3-1
Label
volume, 5-37, 5-58
changing, 5-71
Language
compiler, 6-2
LB:, 5-5, 7-6, 8-7
LBR, 6-29
Left-angle bracket (<), 3-13
Librarian utility
See LBR
Library, 6-28
creating, 6-28, 6-32
file, 6-28
system, 6-2
macro, 6-28
maintaining, 6-28
module, 6-28
deleting, 6-35
extracting, 6-36
inserting, 6-32, 6-37
listing, 6-39
replacing, 6-44
system, 5-5
LIBRARY command, 6-28 to 6-31,
9-19
error messages, 6-45 to 6-51
functions, 6-28
LIBRARY/COMPRESS command, 6-31 to
6-32, 9-19
LIBRARY/CREATE command, 6-32 to
6-34, 9-20
LIBRARY/DELETE command, 6-35 to
6-36, 9-20
LIBRARY/EXTRACT command, 6-36 to
6-37, 9-20
LIBRARY/INSERT command, 6-37 to
6-39, 9-21
LIBRARY/LIST command, 6-39 to
6-43, 9-21
LIBRARY/REMOVE command, 6-43,
9-21
LIBRARY/REPLACE command, 6-44 to
6-45, 9-22
Line continuation
DCL, 1-12, 3-10

LINE FEED key, 3-11
Line printer, 5-3
lowercase, 5-89
Line Text Editor
See EDI
LINK command, 6-2, 6-7 to 6-27,
9-22 to 9-23
examples, 6-24 to 6-26
functions, 6-2
/OPTION qualifier, 6-4
process, 6-4
qualifiers, 6-8 to 6-24
/SAVE qualifier, 6-5
Linking tasks, 6-2
Local assignment
device, 5-8
Logging in, 3-2
Logging out, 3-2
Logical device
assignment
displaying, 2-5, 5-86
Logical name, 5-5
device, 5-5, 5-6, 5-8
assigning, 5-8, 5-21
deleting, 5-29
table, 5-8
Logical unit number
See LUN
Logical Unit Table
See LUT
Login
disabling, 8-4
enabling, 8-4
Login assignment
device, 5-8
LOGIN command, 3-4 to 3-7, 9-23
error messages, 3-7
examples, 3-5 to 3-6
LOGIN.CMD file, 3-4
LOGIN.TXT file, 3-4
LOGOUT command, 3-8 to 3-9, 5-13,
9-23
examples, 3-8
HOLD qualifier, 3-8
Lowercase, 5-89
LUN, 5-5, 5-7
assigning, 5-7
assignment
default, 5-7
displaying, 7-61
reassigning, 5-27
LUT, 5-5
Macro library, 6-28

Index-6

INDEX
MACR0-11 Relocatable Assembler,
6-2
Magnetic tape, 5-3
ACP, 5-39
ANSI
preparing, 5-12
mounting, 5-48
RMS-11, 5-44
set, 5-48
mounting, 5-48
Map file
TKB, 6-2
producing, 6-13
Master File Directory
See MFD
MCR, 1-1
MCR command, 1-6, 9-24
Memory, 7-2
displaying, 2-2, 8-9
Message
sending, 3-28, 3-32
MFD, 4-1, 5-10
MNT, 6-28
Module name table
See MNT
Monitor Console Routine
See MCR
MOUNT command, 5-8, 5-36 to 5-47,
9-24 to 9-25
error messages, 5-49 to 5-52
examples, 5-46
qualifiers, 5-38 to 5-45
MOUNT/FOREIGN command, 5-8
MTAAC, 5-3
MTAACP, 5-48
NL:, 5-6
NO SCROLL key, 3-12
Node name
specifying, 1-10
Null device, 5-6
Number sign ( ) , 3-14
NUMBERS key, 3-15
Object file
binary, 6-2
Object module, 6-2
deleting, 6-31
1 ibrary, 6-28
deleting, 6-35
extracting, 6-36
inserting, 6-32, 6-37
listing, 6-39
replacing, 6-44
linking, 6-7

Object module (Cont.)
name, 6-28

Parameter
DCL, 1-8
Parenthesis (( )) , 3-15
Partition, 7-2, 7-41
base, 7-42
boundary
changing, 7-42
creating, 7-41
eliminating, 7-41
information
displaying, 7-46
size, 7-42
system-controlled, 7-42
types, 7-42
Password, 3-5
Percent sign (%), 3-14, 4-8
Period ( .} , 3-13
PERIOD key, 3-15
Peripheral device, 5-1
Peripheral Interchange Program
See PIP utility
PF key, 3-15
PIP utility, 1-18
Plus sign (+) , 3-14
PMD
specifying, 7-16, 7-29
PMT
parameters
displaying, 8-7
setting, 8-4
Pool, 7-1
displaying contents, 8-9
displaying information, 8-7
limits
setting, 8-4
size
increasing, 8-4
Postmortem Dump
specifying, 6-15
PRINT command, 4-60 to 4-69, 9-25
examples, 4-66 to 4-68
qualifiers, 4-60 to 4-66
Print job, 4-60
Priority
task, 7-2
Program
developing, 6-1
source, 6-1
Prompt, 1-3
explicit, 3-17

Index-7

INDEX
Pseudo device, 5-1, 5-4, 5-5, 5-5
to 5-6
list, 5-6
name, 5-5
PURGE command, 4-39 to 4-41, 9-26
QMG, 1-17, 2-4, 4-60
displaying information
devices, 2-4
queue file, 2-4
Qualifier
date-related, 4-8
DCL, 1-3 to 1-4
floating, 1-3 to 1-4
Queue file
displaying information, 2-4
Queue Manager
See QMG
Quotation mark ("), 1-9
Radix-50, A-1
Read access, 4-9, 4-84
Record Management Services
See RMS-11
Redirection, 5-5, 5-24
Region
fixing, 7-38
removing, 7-37
RELEASE/ENTRY command, 9-26
RELEASE/JOB command, 9-26
REMOVE command, 7-37, 9-26
REMOVE/REGION command, 7-37
RENAME command, 4-47 to 4-49,
9-27
REPEAT key, 3-12
REQUEST command, 3-32, 9-27
Resource Monitoring Display
See RMD
RETURN key, 3-2, 3-10
Right-angle bracket (>) , 3-13
CLI prompt, 3-13
RMD, 8-9
RMS-11, 4-50
magnetic tape, 5-44
RMSCNV utility, 4-50
RUBOUT key, 3-11
RUN command, 7-5, 7-11 to 7-15,
9-27, 9-28
install-run-remove form, 7-3,
7-7 to 7-11
SCROLL key, 3-12
Scrolling
terminal, 3-12
SEL key, 3-10

Sequential file
appending, 4-70
creating, 4-10, 4-11
SET commands
DCL, 2-1
SET DAYTIME command, 2-1, 8-1,
9-28
SET DEBUG command, 1-2, 1-13 to
1-14, 2-8, 9-29
SET DEFAULT command, 2-5, 4-80 to
4-81, 9-29
SET DEVICE command, 5-88 to 5-90,
9-29
SET FILE command, 4-87 to 4-89,
9-29
SET GROUPFLAGS command, 6-52,
9-30
SET HOST command, 1-10 to 1-11,
1-11 to 1-12, 9-30
SET NODEBUG command, 1-13 to 1-14,
2-8
SET NOPARTITION command, 9-30
SET PARTITION command, 7-41 to
7-45, 9-30
SET PRIORITY command, 7-63 to
7-64, 9-31
SET PROTECTION command, 2-6, 4-83
to 4-86, 9-31
SET QUEUE/ENTRY command, 9-31
SET QUEUE/JOB command, 9-32
SET SYSTEM command, 8-3 to 8-5,
9-32
qualifiers, 8-3 to 8-5
SET SYSTEM/DIRECTORY command, 2-8,
8-7
SET TERMINAL command, 2-3, 3-34
to 3-46, 9-33 to 9-34
examples, 3-45
qualifiers, 3-35 to 3-45
SET TIME command, 2-1, 8-1, 9-28
SHIFT key, 3-12
SHOW /CLOCK QUEUE command, 7-65
SHOW ASSIGNMENTS command, 2-5,
5-86 to 5-87, 9-35
SHOW CLOCK QUEUE command, 9-35
SHOW commands
DCL, 2-1
SHOW DAYTIME command, 2-2, 8-3,
9-35
SHOW DEFAULT command, 2-5, 4-82,
9-35
SHOW DEFAULTS command, 3-2
SHOW DEVICES command, 2-3, 3-3,
5-91 to 5-94, 9-36

Index-8

INDEX
SHOW GROUPFLAGS command, 6-53,
9-36
SHOW HOST command, 9-36
SHOW MEMORY command, 2-2, 8-9 to
8-12, 9-36
SHOW PARTITIONS command, 7-46 to
7-48, 9-37
SHOW PROCESSOR command, 2-4, 9-37
SHOW QUEUE command, 2-4, 9-37
SHOW QUEUE/FULL command, 2-4
SHOW SYSTEM command, 8-6 to 8-7,
9-38
qualifiers, 8-6 to 8-7
SHOW SYSTEM/DIRECTORY command,
2-8, 8-7
SHOW TASK/LOGICAL UNITS command,
7-61 to 7-62 SHOW TASK:taskname/DYNAMIC
command, 7-57 to 7-59, 9-39
SHOW TASKS command, 9-38
SHOW TASKS command, 2-5, 7-49 to
7-62
SHOW TASKS/ACTIVE command, 3-2,
7-2, 7-49 to 7-54
SHOW TASKS/ACTIVE/DYNAMIC command,
7-59 to 7-61, 9-39
SHOW TASKS/DYNAMIC command, 9-38
SHOW TASKS/DYNAMIC command, 7-57
SHOW TASKS/INSTALLED command, 2-6,
7-54 to 7-56
SHOW TASKS/INSTALLED/DEVICE
command, 7-56 to 7-57
SHOW TERMINAL command, 2-2, 3-47
to 3-57, 9-39 to 9-40
examples, 3-51 to 3-57
qualifiers, 3-48 to 3-50
SHOW TIME command, 2-2, 8-3, 9-35
SHOW USERS command, 2-6, 8-8,
9-40
SHOW/TASKS/ACTIVE command, 2-5
Slash (/) , 3-15
SLP utility, 4-20, 4-74
Source file
maintaining, 4-20
Source Language Input Program
See SLP utility
Square bracket ([ ]) , 3-15
START command, 7-26, 9-41
START/PROCESSOR command, 9-41
START/QUEUE command, 9-42
START/QUEUE/MANAGER command, 9-42
START/UNBLOCK command, 7-27, 9-42
STD, 7-1, 7-2
entry
including, 7-28

STD
entry (Cont.)
removing, 7-37
STOP/ABORT command, 9-42
STOP/BLOCK command, 7-24 to 7-25,
9-43
STOP/PROCESSOR command, 9-43
STOP/QUEUE command, 9-43
STOP/QUEUE/MANAGER command, 9-44
String
quoting, 1-9
Subpartition, 7-41
SY:, 4-2, 4-4, 5-6
SYSLOGIN.CMD file, 3-4
System
attribute
displaying, 8-6
setting, 8-3
directory, 8-7
displaying, 8-6, 8-7
setting, 8-3, 8-7
file, 5-10
host
displaying, 1-11 to 1-12
setting, 1-10 to 1-11
multiuser protection, 3-3
pool
displaying contents, 8-9
displaying information, 8-7
increasing, 8-4
setting limits, 8-4
System date
displaying, 2-1
setting, 2-1
System directory, 7-6
displaying, 2-8
setting, 2-8
System library, 5-5
System Task Directory
See STD
System time
displaying, 2-1
setting, 2-1
Tab
vertical, 3-20
TAB key, 3-20
Task, 7-1
aborting, 7-16
active, 7-1
displaying information, 7-2,
7-49
blocking, 7-24
building, 6-2
checkpointable, 7-2

Index-9

INDEX
Task
checkpointable (Cont.)
specifying, 7-28
creating, 6-7
displaying information, 2-5,
7-57
dormant, 7-1
executing, 7-5
information
displaying, 7-57
installed, 7-1
displaying informatibn, 7-49,
7-54, 7-56
dormant, 7-28
executing, 7-6, 7-11
fixing, 7-38
LUNs
displaying, 7-61
removing, 7-7
unfixing, 7-40
installing, 7-1, 7-7, 7-28
linking, 6-2
name, 7-2
default, 7-3
removing from STD, 7-37
specifying, 7-30
priority, 7-2
changing, 7-63
specifying, 7-29
removing, 7-3 7
resuming, 7-21, 7-26, 7-27
scheduling, 7-7, 7-11
size
displaying, 8-6
extending, 8-3
status flags, 7-51 to 7-52
stopping (?), 7-24
UIC
specifying, 7-30
uninstalled
executing, 7-7
Task build
aborting, 6-3, 6-11
Task Builder
See TKB
Task Control Block
See TCB
Task image, 6-2
file, 7-5, 7-7
specifying name, 7-28
Task Termination Notification
program
TCB, 7-1
Terminal
attached, 3-2

Terminal (Cont.)
attribute
displaying, 2-2
setting, 2-2
character
deleting, 3-11, 3-19
characteristic
displaying, 2-2, 3-47
setting, 2-2, 3-34
displaying information, 3-2,
3-47
lowercase, 5-89
model, 2-3
displaying, 2-2
setting, 2-2
scrolling, 3-12
slaved, 3-2
typeahead buffer
clearing, 3-20
Terminal characteristics
displaying, 3-2
setting, 3-2
Terminal keyboard, 3-1, 3-9
Terminal keypad, 3-1, 3-15
VT200-series, 3-15
Terminal number, 3-1
Terminal output
interrupting, 3-17
skipping, 3-18
TI: , 5-6
Time
system
displaying, 2-1, 8-3
setting, 2-1, 8-1
TKB, 6-2
examples, 6-5
format, 6-5
invoking, 6-2, 6-7
map file, 6-2
producing, 6-13
options, 6-2, 6-4, 6-14
list, 6-16 to 6-19
TKTN, 7-19
messages, 7-19 to 7-20
TYPE command, 4-57 to 4-59, 9-44
Typeahead buffer
clearing, 3-20
UCB, 5-5
UFO, 4-1
creating, 4-10, 4-13
UIC, 3-4, 4-2
task
specifying, 7-30

Index-10

INDEX
Underscore ( ) , 3-14
DCL, 1-8
UNFIX command, 7-40, 9-44
Unit Control Block
See UCB
UNLOCK command, 4-78 to 4-79,
9-45
User
displaying information, 8-8
types, 4-9, 4-83
user File Directory
See UFO
User Identification Code
See UIC
Utility
using from DCL, 1-18
VAX/VMS
DCL, 1-19
verify Utility
See VFY utility
Version number
file, 4-3
changing, 4-47
default, 4-4
VFY utility, 4-87
Volume, 4-1, 5-1, 5-3, 5-4
backup, 5-73
density
changing, 5-70
setting, 5-59
dismounting, 5-53
file
default number, 5-62
maximum number
changing, 5-71
setting, 5-62

Volume (Cont.)
Files-11, 5-3
backing up, 5-73
formatting, 5-57
level 401, 5-62
level 402, 5-62
restoring, 5-73
foreign, 5-3, 5-8, 5-38
label, 5-37, 5-58
changing, 5-71
magnetic tape, 5-3
mounting, 5-36
owner
changing, 5-71
specifying, 5-42, 5-63
protection, 4-9
changing, 5-71
code, 4-10
setting, 5-40
write-protecting, 5-42
Volume Home Block, 5-57
changing, 5-70
displaying information, 5-71
Volume ID, 5-38, 5-48
Volume Identifier
See Volume ID
VTlOO, 3-1
VT200-series, 3-1
terminal keypad, 3-15
VT52, 3-1
Wildcard
asterisk (*), 3-14, 4-6 to 4-8
file specification, 4-6
percent sign (%), 3-14, 4-8
WK:, 5-6
Write access, 4-10, 4-84

Index-11

RSX-llM
Command Language Manual
AA-L672C-TC
READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent.

D Assembly language programmer
D Higher-level language programmer

D Occasional programmer (experienced)
D User with little programming experience
[] Student programmer
[] Other (please specify)

Organization
Street
S t a t e - - - - - - Zip Code - - - - - or Country

- -

Do Not Tear - Fold Here and Tape -

No Postage
Necessary

111111

if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

- -

Do Not Tear - Fold Here