Digital PDFs

AA-2762F-TC

June 1985

639 pages

Original

23MB

Document:	RSTS/E V9.0 System Managers Guide
Order Number:	AA-2762F-TC
Revision:	0
Pages:	639
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsts_e/V09/2_System_Mangement/AA-2762F-TC_RSTS_E_V9.0_System_Managers_Guide_Jun85.pdf

OCR Text

RSTS/E
System Manager's Guide
Order No. AA-2762F-TC

June 1985
This manual describes how to manage a RSTS/E system.

OPERATING SYSTEM AND VERSION: RSTS/E

V9.0

RSTSIE

V9.0

SOFTWARE VERSION:

digital equipment corporation. maynard. massachusetts

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 or its affiliated companies.

The postage-paid READER'S COMMENTS form on the last page of this document requests your critical evaluation to assist us in preparing future documentation.

The following are trademarks of Digital Equipment Corporation:

~DmDDmD TM

DIBOL
FMS-11

DEC
DECmail
DECmate
DEC net
DECtape
DECUS
DECwrlter

LA
MASS BUS
PDP
P/OS
Professional
Q-BUS
Rainbow

ReGIS
RSTS
RSX
RT
UNIBUS
VAX
VMS

VT
Work Processor

CONTENTS

PREFACE

xvii

SUMMARY OF TECHNICAL CHANGES

xxi

Chapter 1

Overview of RSTS/E System Management
Glossary of RSTS/E Terms . . . .
. . .
System Management
. . .
. ....•.....
Disk Organization
. . • . . ..
. ....
Types of Disks . .
.......
. ....
File Structures . . . .
. ....
Level 0 Disk Structure (Pre-V8.0)
...
. ..
Levell Disk Structure (for V8.0 and V9.0) . . . .
Differences Between Level 0, Level 1.1, and Level

1.2

.. . . . . . . ..

....

Disk Optimization
. . .
System Operation Concepts
. . .
Privilege
. . . . . . . . . . . . .
Multiple Privileges
. . . . . .
Classes of System Activities
Account Management Activities
. . .
File Access Activities .
....
Multiple Privilege Masks . . . . . .
Chapter 2

..... 1 -9

1-10
1-10
1-11
1-12
1-12
1-12
1-12
1-14

. . . .
....

Starting, Halting, and Automatic Recovery of RSTS/E
Starting up RSTS/E .
...........
..
Bootstrapping RSTS/E with a Hardware Bootstrap
Loader. . . . . . . . . . . . . . .
. ..
Bootstrapping RSTS/E after a System Halt
.
Starting Timesharing . . . . . . . . . . .
..
Halting the RSTS/E System . . . . . . . . .
. ..
Automatic Recovery and Restart Facilities
. . ..
Catastrophic Errors and System Crashes .
. ..
Automatic Recovery from Catastrophic Errors . . .
Automatic Restart Mode Initialization . . . . . .
Power-Fail Hardware Used by RSTS/E . . . . . . . .

Chapter 3

1-1
1-3
1-4
1-4
1-5
1-6
1-8

2-1
2-2
2-2
2-3
2-5
2-5
2-5
2-7
2-8
2-8

The System Start-Up Command Files
Creating and Using Command Files . .
System Start-Up Command File: START.COM
Mount All Disks
. . . . . . . .
Assign System-Wide Logical Names . .
Start Error Logging
. . . . . .
Enable Caching (Optional)
...
Set Default System Characteristics .
Install Run-Time Systems . . . . . .
iii

.
.

• •
• •

· •
• • •

.
·
•
•
•
·
•
•

3-1
3-3
3-7
3-7
3-7
3-8
3-8
3-8

Install Libraries . . . . . . . .
. . . . 3-8
Set Terminal Characteristics .
. . . . 3-9
Define System Commands . . . .
. . . . . . . . 3-9
Set Printer Characteristics . . . . . . . . . . . 3-9
Start Print/Batch Services . . . .
...
3-10
Start OPSER-Based Spooling Package (Optional)
3-10
Start Error Analysis . . . . . . .
. . . 3-10
Enable Logins
. . . . . . . . . . . . . . . 3-10
Logout the Initial Start-up Job
. . . 3-10
Chapter 4

Shutting Down the RSTS/E System
Performing System Shutdown: SHUTUP
. . . . 4-1
Running SHUTUP . . . .
. . . . 4-1
SHUTUP phases
. . . . . . . . ..
. . . . . . . . 4-2
Set-up Dialogue phase . . . . . . . . . . . . . . 4-3
Warning Message phase
. . . . . .
. . . . 4-5
DECnet/E Shutdown Phase (When Necessary) . . . . . 4-7
Initial Job Killing phase . . . . . . . . . . . . 4-8
Print/Batch Shutdown Phase (When Necessary)
. . . 4-9
OPSER Shutdown phase (When Necessary)
. . .
4-10
EVTLOG Shutdown Phase (When Necessary) . . . . .
4-11
ERRCPY Shutdown Phase (When Necessary) . . . . .
4-11
Final Job Killing Phase (When Necessary)
4-12
EMT Logging Shutdown Phase (When Necessary)
4-12
Remove Run-Time Systems and Resident Libraries
Phase
. . . . . . . . . . . . . .
. . .
4-12
4-12
Swap File Removal Phase
. ..
...... .
Disk Dismount phase
. . .
. . . 4-12
Final Shutdown Phase . .
......... .
4-13
4-13
SHUTUP Operation Examples
. . . . . . . . .
SHUTUP Example: Large RSTS/E System . . . .
4-13
4-15
SHUTUP Example: Small RSTS/E System . . . .
SHUTUP Example: DECnet/E Shutdown
.. .
4-16
Notes on SHUTUP Operation . . . . . . .
4-18

Chapter 5

Managing Quotas
Disk Quotas
. . . . . . .
Disk Quota Operations
. . . .
Logged-In Disk Quotas . . . .
Logged-Out Disk Quotas . . . .
Job Quotas . . . . . . .
.. .
Detached-Job Quota .
. . .
Job Quotas and Login
...
Send/Receive Quotas
. . .
RIB Quota
. ..
.... .
Message Quota . . .
.. .

. ..
. • .

.5- 1

• . • • .5- 2
• • • • 5- 2
· . . .5- 3
• • 5- 4

. . .5- 4
• • 5-5

• • • • 5- 5

. . . .

• • 5-5
. . . .5- 5

Chapter 6

Managing Privileges
RSTS/E-Defined privileges
. • . • . . . • • . • 6-1
DATES privilege . . . . . • . . . . • .
. •• 6-3
DEVICE Privilege . . . . . . . . .
. • • • • • 6-3
EXQTA Privilege . . . . . . . . . . . . . . . • . 6-4
GACNT Privilege . . . . . . . . . . . . . • • . . 6-4
GREAD Privilege . . . . . . . . . . • .
. . . 6-4
GWRITE Privilege
. . . . . • • • . • 6-4
HWCFG Privilege . . . .
....
. • • • • 6-4
HWCTL Privilege . . . . . • . . . . . . • • • • . 6-5
INSTAL Privilege . . . . . . . . . . . . . • • • . 6-5
JOBCTL Privilege .
......•
. • • • • 6-5
MOUNT Privilege
. . . .
. . . • . 6-5
PBSCTL Privilege . . . . . . . . . . . . . • • • . 6-5
RDMEM Privilege
. ..
. . . . . . • • • . 6-5
RDNFS Privilege . . . . . .
....••
. 6-5
SEND Privilege . . . . .
. • . . . . . . . . • 6-6
SETPAS Privilege . . . . . . . . . . . . . .
. 6-6
SHUTUP privilege .
........
. . • . 6-6
SWCFG Privilege
. • . . . • . • . 6-6
SWCTL Privilege . . . .
. . . . . • . . . 6-7
SYSIO Privilege
. . . .
. . ••
. 6-7
SYSMOD Privilege . . . .
. . . . . • . . . 6-7
TUNE Privilege . . . . . . . . . . . . . . .
. 6-8
WACNT Privilege . . • . . . . . . . . . . • . . . 6-9
WREAD Privilege . . . . . . . . . • . . . . . . . 6-9
WRTNFS Privilege . .
. . . . . . . . . . . • . 6-9
WWRITE Privilege .
.......
6-10
User-Defined Privileges
6-10
Multiple Privileges and Jobs
...
. . • . . 6-10
Privilege Masks . . . . . . . . . . . . . . • . 6-10
Job creation .
.......
. . . • . • 6-11
Login

Chapter 7

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

6-11

Logout . . .
....
Spawned jobs
...........•••
Running Programs Under Multiple Privileges •
Running System Programs . . . • . • • .
Temporary Privileges . . . . . . . • . . . •
Designating a Program as Privileged . . . . ••
Running a Privileged Program . . . . . . • • . •
Program exit. . . . . . . . . . . . . • • • • •

6-11
6-11
6-12
6-12
6-13
6-13
6-14
6-14

Managing Accounts
Accounts . . . . . . . . . . . . . . .
Project-Programmer Number (PPN)
Account Access Privileges . . . .
Account Data . . . . . . . . • . . •
Account Name . . . . . . . . . • .
Date/Time/Keyboard of Last Login .
Date/Time of Last Password Change
v

. . . ..
.

. 7-1

• • • • • • • 7-2
. . • • • . .7- 3

• 7-4
. . • . . . 7-4
. . • . •.
7-4
. . . ••
. 7-4

Password . . . . . . . . . . . . . . . .
7-4
Interactive Flag . .
........
. . 7-5
Captive Account Flag .
. . .
. . 7-5
Network Flag..
..........
. 7-6
Dial-Up Flag. . . . . . . .
....
. . 7-6
Expiration Date
. . . . . . . . . . . . . . . 7-6
Authorized Privilege Mask . . . . . . . . . . . . 7-6
Creation Date
. .'. . . . . . . . .
... 7 -6
UFD Cluster Size . .
. . . . . . . . . . . . . 7-6
Quotas .
. . . . . . . . . . . .
. . 7-7
System Data
. . . . . ..
. . . . . . . . . . . . 7-7
Commands . . . . . . .
. . . . . . . ..
. 7-7
CREATE/ACCOUNT Command.
. . . . . . . . . . . . . 7-8
DELETE/ACCOUNT Command
. . . . . . . . . . .
7-13
SET ACCOUNT Command . . .
. . . . .
7-16
SET PASSWORD Command
..........
7-20
SHOW ACCOUNT Command
..........
7-22
Chapter 8

Managing Terminals
. . 8-1
Understanding the SET TERMINAL Command . .
Terminal Line Speed Characteristics File:
• 8-2
TERSPD. SYS . . . . . . . . . . . . . . . .
Setting Terminals Other Than Your Own
. . .
• 8-4
User-Defined Terminal Characteristics File:
T ERMA C . S YS . . . . . . . . . . . . . . . . . . . . 8 - 5
Automatic Setting of Terminal Characteristics:
TERDFL.SYS . . . . . . . . . . . . . . . . . . . . 8-6
Setting Permanent Terminal Characteristics . . . . 8-7
Using the /NOBROADCAST and /BROADCAST Command
Qualifiers . . . . . . . . . . . . . . . . . . . . 8-7
Error Messages . . . . .
. . . . . . . . . . . . . 8-8
Co mm and s . . . . . . . . .
. . . . . ..
. 8-8
SET TERMINAL Command . . . . . . . . . . . . . . . 8-9
SHOW TERMINAL Command
. . . . . . .
8-20

Chapter 9

Managing print/Batch Services
Managing the Print/Batch Services Package . . . . . .
Queue Manager
. . . . . . . . . . . ..
.
Queue Types
.............
Queue Names . . . . . . . . . . . . . . . . .
Default Queues . .
. ...........
Assigning Servers to Queues . . . . . . . . .
Queue Priorities . . . . . . . . . . . . . . .
Opening and Closing Queues . .
...
.
Starting and Stopping Queues .
...
.
Processing Requests
. . . . . . .
.
Accessing Entries on a Queue .
. .....
Job Limits for Queues
............

9-3
9-3

9-4
9-4
9-4
9-5
9-6

9-7
9-7
9-7
9-9
9-9

Print Servers . . . . . . . . . . . . . . . . .
Device Ownership . . . . . . . . . . . . . .
Job Copies and File Copies . .
Header Pages . . . . .
... .
Page Limits . . . . .
. .. .
Control Characters and Escape Sequences
Eight-Bit Characters . . . . . . . . . . . .
Batch Servers
. . . . . . . . . . ..
.. .
Executing Command Files
. . . ..
.. .
CPU and Time Limits
. . . . . ..
. ..
Managing Form~ for PBS . . . . . . . . . . . . .
Forms Attributes . . . .
..... .
The Forms Definition File
. . ..
. ..
Forms Definition Keywords
...
Changing Forms
. . .
. . .
. . . . . . . . . . . . ..
.. .
Mul tiple Jobs
The Primary Job
. . . . . ..
.. .
Secondary Jobs . . . . .
. ..
.. .
Descriptions of PBS's DCL Commands. . . .
. ..
ASSIGN/QUEUE Command . . . . . . . . .
.. .
CLOSE/QUEUE Command . . . . . . . . .
.. .
DEASSIGN/QUEUE Command . . . . . . . .
.. .
DELETE/QUEUE Command . . . . . . . . .
.. .
DELETE/SERVER Command . . . . . . . .
.. .
INITIALIZE/QUEUE Command . . . . . . .
.. .
INITIALIZE/SERVER Command . . . . . .
.. .
OPEN/QUEUE Command
......
.. .
SET QUEUE Command . . . . . . . . . . . . . . .
SET SERVER Command . . . . .
...
...
SHOW SERVER Command
. . . . . . . . . .
START/QUEUE Command
. . .
. . .
START/QUEUE/MANAGER Command
. ..
.. .
....
.. .
START/SERVER Command . . .
STOP QUEUE Command . . . .
...... .
STOP/QUEUE/MANAGER Command . . . . . .
.. .
STOP/SERVER Command . . .
....
.. .
Chapter 10

9-10
9-10
9-11
9-12
9-13
9-14
9-15
9-15
9-15
9-16
9-17
9-17
9-18
9-19
9-22
9-23
9-23
9-23
9-24
9-25
9-26
9-27
9-28
9-29
9-30
9-34
9-36
9-37
9-41
9-44
9-46
9-47
9-49
9-51
9-52.
9-53

Managing System Errors
Use of the Error Logging Programs: ERRINT and ERRCPY 10-2
Error Logging Initialization: ERRINT .
. . . 10-2
10-3
Examples of ERRINT Dialog~e
. . . . . .
Error Logging: ERRCPY . . . . . . . . . . . . . 10-4
Displaying Errors: ERRDIS
. . ..
. . . 10-4
10-5
Running ERRDIS .
........... .
Help Report
. . . . . . .
. . . 10-7
10-7
Summary Report .
. . . . . . . . .. .
10-9
Bad Block Rep9rt . . . . . . .
. . .
Adding Bad Blocks to the Bad Block File . . . . 10-10

vii

Full Report
. . . • . . . . . . . . . ..
.
User Description in Full Report . . . . . .
Disk Error Detailed Description . . . . • •
MSCP Variations on the Full Report .
.•
Nondisk Peripheral Device Error Detailed
Description . . . . . . . . . . • . . . . .
Nonperipheral Error Detailed Description . .
Analyzing System Crashes: ANALYS . . . . .
. •.
Running the ANALYS Program . . . . . . . . . • •
ANALYS Output
. . . . . . . . .
. ..••
Chapter 11

10-22
10-24
10-27
10-27
10-29

Device Management and Caching Control
Principles of Device Management
. . • •
Optimizing Disk Directory Structure: REORDR
. . • •
Why Use REORDR?
. . . . . . ..
....••
Dialogue Questions and Responses. . . . . . . •
Reordering Your Disks
. . . . . . ..
...
Error and Processing Messages
REORDR Example . . . . . . . . . . . .
...
Caching Control
. . . . . . . . ..
....•.
Size of the Cache
. . . . . .
. ..
.
Sequential and Random Caching Modes
. ..
.
Random Mode Caching
.•
Sequential Mode caching
........
Caching Guidelines. . .
. . .
•
DCL Command Descriptions . . . . . . . . . . . . . .
ALLOCATE Command.
. . . . . .
.
DEALLOCATE Command. . . . . . .
...
.
SET CACHE Command
. . . . . .
. .....
SET DEVICE Command . . . . . . . . . . . . . . •
SET PRINTER ~ommand
. . . .
. .
SHOW CACHE Command . . . . . . . . . . . . . . .
SHOW DEVICE Command . . . . . . . . . . . . . .
SHOW DISKS Command. . . . .
. •
SHOW PRINTER Command.
.....

Chapter 12

10-11
10-12
10-14
10-19

11-2
11~2

11-2
11-3
11-5
11-6
11-8
11-9
11-10
11-10
11-11
11-11
11-12
11-15
11-16
11-17
11-18
11-22
11-23
11-26
11-28
11-29
11-30

Managing System Files and Logical Names
Run-Time System Control
. . . . . . • . . . . . . .
Adding and Removing Auxiliary Run-Time Systems.
Associating a File with a Run-Time System . . .
Resident Library Control . . . . . .
....
Resident Library DCL Commands . . . . . . . . .
System Logical Names . . . .
. .....
Assigning Logical Names
. . ..
. ...
Removing Logical Names .
. ...
Listing System Logical Names .
. ....
Defining Concise Command Language Commands .
..
Adding a CCL Definition . . . . . . . . • • . .
Listing Currently Defined CCL Commands .
..
Removing a CCL Definition . . . . . . . . . . .
viii

12-3
12-5
12-9
12-9
12-10
12-11
12-12
12-13
12-14
12-14
12-14
12-16
12-17

System File Control . . . . . . . . . . . . . . . . 12-17
Adding and Removing Swap Files . . . • . . . . . 12-18
Adding and Removing Overlay and Error Files . . 12-21
using the DUMP/SYSTEM Command
. . . . . 12-22
DCL Command Descriptions . . . . .
. . . 12-23
ASSIGN/SYSTEM Command . . . .
. 12-24
DEASSIGN/SYSTEM Command . . . . . . . . . . . . 12-25
DEFINE/COMMAND/SYSTEM Command
. . . 12-26
DELETE/COMMAND/SYSTEM Command . . . . .
12-27
DUMP/SYSTEM Command
. ..
. . . . . . . . . 12-28
INSTALL/ERROR_FILE Command. .
. . . 12-29
INSTALL/LIBRARY Command . . . . . .
. . . . 12-30
INSTALL/OVERLAY_FILE Command.
...
. . 12-32
INSTALL/RUNTIME_SYSTEM Command
...
12-33
INSTALL/SWAP_FILE Command
. . . . . 12-36
REMOVE/ERROR_FILE ~ommand
. . . . . ..
12-38
REMOVE/LIBRARY Command . . . . . . . . . . .
12-39
REMOVE/OVERLAY FILE Command . . .
. . . 12-40
REMOVE/RUNTIME-SYSTEM Command
. ..
12-41
REMOVE/SWAP_FILE Command. . . . . . . . . .
12-42
SET FILE Command. . . . . . .
. . . . . . . . 12-43
SHOW COMMAND/SYSTEM Command . . . . . .
. . 12-45
SHOW FILE/SYSTEM Command. . . . .
. . . 12-46
SHOW LIBRARY Command . . . . .
. . . . . . . 12 - 47
SHOW LOGICALS Command . . . . . . . . . . . . . 12-48
SHOW LOGICAL/SYSTEM Command . . . . . . . . . . 12-49
SHOW RUNTIME SYSTEM Command . . . . . .
. . 12-50
UNLOAD/LIBRARY Command. . . .
. . . 12-51
UNLOAD/RUNTIME_SYSTEM Command
. . ..
. . . 12-52
Chapter 13

Job 11anagement
Controlling the Number of Logged-In Jobs.
...
Broadcasting Messages to Terminals
...
Controlling Jobs. . .
. . . . . . . . .
Removing Jobs
. . . . . . . . . . ..
...
Placing a Job on HOLD . . . . .
......
Setting Job Priority, Run Burst, and Maximum Size
Controlling Keyboards and Remote Lines .
....
DCL Command Descriptions .
.........
ATTACH Command . .
....
...
..
BROADCAST Command . . . . . . . .
. ....
DETACH Command. . . . .
...
. ....
FORCE Command . . . . . . . .
. ....
HANGUP Command. . . . . . . . . .
. ....
LOGIN Command . . .
. .......
REMOVE/JOB Command. . . . . .
...
..
SET JOB Command . . . . . . .
. ......
SET SYSTEM Command . . . . . . . . . • . . . . .
SHOW JOB/PRIVILEGE Command .
. .......

13-2
13-3
13-4
13-5
13-6
13-6
13-9
13-9
13 -10
13-11
13-13
13-14
13-15
13-16
13-18
13-19
13-21
13-22

Chapter 14

Miscellaneous System Management Functions
Loading and Unloading Monitor Overlays.
· . . .
Suspending System Operations . . . . . . . . · . . .
Changing System Date and Time
. . . . . . . · . ..
Recording System Activities: EMT Logging
• • • .
Programming. for the EMT Logger.
· . . .
How EMT Logging Works
. . . . . · • . . • • • •
Data Returned by EMT Logging . .
· . . .
EMT Logging and System Security . . . . • . • .
Monitoring System Status: SYSTAT . . . .
· . . .
Dynamic Display of System Status: DISPLY
• • • .
Running the DISPLY Program . . . . . . . · . . .
Screen Layout . . . . . . .
· ...
Job Status Statistics
. . . · . ..
. ...
. ......
BUSY Devices . . . .
Disks
. . . . . .
· . . . . . . . . .
Message Receivers
. . . . . · . . • . . • . • .
Free Buffers . . .
... · . . . . . . . . .
Run-Time Systems . . . . . .
......
Resident Libraries
...
· . . . . . . .
Memory Status
. . .
· .......
DCL Command Descriptions . . . .
· . . .
.
LOAD/OVERLAY Command . . . . · • . • . • • . • •
SET DATE Command . . . . . . · . . . . . . . . .
SET SYSTEM Command . . . . .
· . . . . . . .
SET TIME Command . . . . . . · • . • . . • . . •
SHOW SYSTEM Command . . . .
......
UNLOAD/OVERLAY Command .
· . . .
.

Chapter 15

Managing Disks and Tapes
Working with Disks and Tapes . . .
Initializing Disks and Tapes
Mounting and Dismounting Tapes
DCL Command Descriptions . . . . .
DISMOUNT Command for Disks . .
DISMOUNT Command for Tapes . .
INITIALIZE Command for Disks .
INITIALIZE Command for Tapes .
MOUNT Command for Disks
MOUNT Command for Tapes
.

Chapter 16

14 -1
14 - 2
14 - 3
14 - 4
14 - 5
14 - 5
14 - 6
14 - 7
14 - 7
14 - 9
14 - 9
14-15
14-17
14-20
14 - 21
14 - 23
14 - 24
14-25
14 - 26
14-27
14-28
14 - 29
14 - 31
14 - 32
14 - 35
14-36
14-37

and
. .
. .
. .
. .
.

. . . . . . . 15-1
. . . . . . . 15-2
Disks . . . . 15-3
. . . . . . . 15-3
..
. . . 15-4
. . . . . . . 15-6
. . . . . . . 15-7
. . . . . . . 15-14
. . . . 15-16
. .
. 15-23

Backing Up and Restoring Files
DCL Command Descriptions . .
BACKUP Command . .
...
RESTORE Command
. . . .

. .

16 - 2
16-3
. . . . . 16-12

Appendix A

Managing the OPSER Spooling Package
Overview of Operator Services . . . . . . . . . .
A-2
OPSER Program Overview . . . . . .
. . . . . . A-2
QUEMAN Program Overview
. . A-5
SPOOL Program Overview .
. . . . A-6
BATCH Program Overview . . . . . .
.••.
A-6
RJ2780 Program Overview
. ..
. . . . . . A-6
Controlling RESTOR with OPSER
• . . . . . A-7
Overview of OPSER Shutdown . . . . . . . . . • . . A-7
Operator Services Program: OPSER .
. . . . A-7
OPSER Operator Commands
. . .
A-IO
Message Types
. . . . . . . .
. . . A-13
Valid Operator and Online Job Lists . . . .
A-16
Operator INTERRUPT Command . . . . . . . . .
A-16
OPSER start-Up Procedure. . . . . . .
. . • A-17
OPSER Action Under Various start-Up Conditions. A-18
Queue Manager Program: QUEMAN . . . . . .
. . . A-19
QUEMAN start-up Commands and Switches • . .
A-21
QUEMAN Interrupt Commands . . . . . . . . .
A-23
QUEMAN start-up Procedure . . . . . .
. . . A-26
QUEMAN Action Under Various start-up Conditions
A-27
QUEMAN Consistency Checking . . . . . . . . . . A-27
Line Printer Spooling Program: SPOOL . . . . . .
A-29
SPOOL Start-Up Options.
. . . . . . . . . . A-31
Line Printer Spooling
. . . . . . . . .
A-37
Keyboard Spooling
. . . . . . . . . . . . . A-38
Start-Up Error Processing
. . .
A-39
SPOOL Interrupt Commands. . . . .
...
A-41
SPOOL Start-Up Examples
. . . . . .
A-42
Line Printer start-Up with All Defaults
A-42
Line Printer Start-Up with Narrow Width
A-43
Keyboard Start-Up on an LA36 . . . . . .
A-45
Keyboard Start-Up on an LA180
. . . A-46
Recovery from Line Printer Errors
. . .
A-47
Line Printer Output . . . . . . . . . . . . . . A-48
Error Messages During User Output
. . . A-49
Changing and Aligning Forms . . . . . .
A-51
Batch Processor Program: BATCH . . . . . . . . .
A-52
BATCH Start-Up Options. . . .
...
A-53
BATCH Interrupt Commands. . . . . . . .
A-55
BATCH Start-Up Procedure
......
A-56
Operator Action Requests from BATCH . . . . . . A-56
Operator Communication Program: PLEASE.
A-58
Running and Terminating PLEASE . .
.•.
A- 58
OPSER Commands through PLEASE . . .
A-59
PLEASE as a CCL Command . . .
...
A- 61
Terminating Operator Services and Spooling .
A-61
OPSER Shutdown Levels . . . . . . .
A-61
OPSER Manual Shutdown Procedure . . . .
A-62
RESTOR as an OPSER Controlled Program . . .
A-63

Appendix B

Number Conversion

Appendix C

Disk Device Sizes

Appendix D

General RSTS/E Messages
Special Characters Used irt Error Messages

Appendix E

. . . . . . 0-1

SAVE/RESTORE System Program
When to Use SAVE/RESTORE . . .
......
. . E-l
Definitions of SAVE/RESTORE Terms
. . E-2
Running SAVE/RESTORE. . . . . .
...
E-2
SAVE/RESTORE Switches
. . . . . . . . . .
. . E-S
SAVE/RESTORE Dialogue . . . . . . . . . . . . . . . . E-7
SAVE Volumes. . . . . . . . . . . . .
. • E-8
Device Specifications . . . . . . . . . . . . . . E-9
Privileges Required
. . . ..
. . . E-10
Checking the Input Volume
. . . . . . . E-10
Checking the Output Volume .
...
. . . E-12
Saving a RSTS/E Disk using the SAVE Dialogue . . E-14
Restoring a RSTS/E Disk using the RESTORE
E-20
Dialogue . . . . . . . . . . . . . . . . . .
Copying a RSTS/E Disk using the IMAGE Dialogue . E-26
IDENTIFY Dialogue
. . . . . . . . . . . . . . . E-32
Full Function Command Line . . . .
. . . E-34
SAVE/RESTORE and Booting . . . . . . . . .
. . . E-34
Operator Interface During Processing .
. . . E-36
Mounting and Dismounting Volumes . . . . . . . . E-36
Re-Accessing Devices . .
. . . . . . . . . . E-38
Aborting SAVE/RESTORE
. . . . . . ..
. . . E-38
SAVE/RESTORE Summary Report
. . . . . . . . . . . . E-38
Summary Report Format and Example
. . . . . . . E-38
Summary Report Run Statistics
. . . E-40
SAVE/RESTORE Error Handling
. . . . . . . . . . . . E-4l
General SAVE/RESTORE Error Messages
. . . . . . E-42
Transfer Errors-Fatal and Nonfatal . . . • . . . E-49

Appendix F

Device Testing Package (DEVTST)
Introduction to DEVTST . . . .
DEVTST Operating Procedures
DEVTST Dialogue Errors . . . .
CPEXER . . . . . . . . . . . .
CPEXER Tests . . . . . .
CPEXER Dialogue
. . . . .
CPEXER Errors
. . . . . .
CPUTST . . . . . . .
CPUTST Dialogue
CPUTST Errors
xii

.
.

•

.
.
.

•

•
.

•
•

•

•
•

•
.

· . F-l
• • F-2
• • F-4
F-S
• • F-6
· . F-7
• • F-7
• • F-9
•
F -10
•
F -1 0

F-IO

DSKEXR . .
DSKEXR Dialogue
DSKEXR Errors
DSKSEK . . . . . . .
DSKSEK Dialogue
DSKSEK Errors
DTEXER . .
DTEXER Dialogue
DTEXER Errors
DXEXER . .
DXEXER Dialogue
DXEXER Errors
KBEXER . .
KBEXER Dialogue
KBEXER Errors
.. .
LPEXER . . . . . • . •
LPEXER Dialogue
LPEXER Errors
MTEXER . .
MTEXER Dialogue
MTEXER Errors
PPEXER . .
PPEXER Dialogue
PPEXER Errors
PREXER . .
PREXER Dialogue
PREXER Errors

F-ll
F-12
F-13
F-13
F-13
F-14
F-15
F-15
F-16
F-16
F-17
F-17
F-18
F-18
F-18
F-19
F-19
F-19
F-20
F-20
F-21
F-21
F-21
F-22
F-22
F-22

INDEX

FIGURES
1-1 MFDs and UFDs in Level 0 File structure
. . . . . . . 1-7
1-2 MFD, GFDs, and UFDs in the Levell File Structure
. . 1-8
9-1 One-to-One Configuration. .
. . . . • . . 9-5
9-2 One-to-Many Configuration
. . . .
. . ..
9-5
9-3 Many-to-One Configuration . . . . . . . . . . . . . . 9-6
11-1 Caching Mode Checks. . .
. . ..
. • . . 11-13
11-2 Monitor Caching Checks
. . ' . . • . 11-19
13-1 priority Byte Format
. . . . . . . . . . • . .
13-7
A-I System Controlled Programs and Operator Interaction
. A-4
E-l Summary Report Format
. . . . . . . . • . .
E-39

TABLES
2-1 Initialization Option Summqry
6-1 RSTS/E Privileges
......... .
7-1 DCL Commands for Managing Accounts •
xiii

. . . . . . 2-4
•

• 6-2

. . . . . . . 7 -1

8-1 RSTS/E Supported Controller Typ~~ . . . . . . . . . . 8-3
9-1 DCL Commands for the Print/Batch Services Package . . 9-1
9-2 PBS Batch Job Exit Status Messages. . . .
. . . 9-16
10-1 ERRDIS Dialogue Explanation..
...
10-S
10-2 User Description Data. . . . . . . . . .
. . 10-14
10-3 Disk Error Detailed Description. ,. .
.10-17
10-4 Nondisk Peripheral Device Format
. . . . . 10-24
10-S Nonperipheral Error Format
. ..
. . . . . 10-26
10-6 ANALYS Program Dialogue . . . . . . . . . . . . . . 10-28
10-7 System Crash Error Code . . . . .
. 10-30
11-1 DCL Commands for Device Management and Caching
Control . . . . . . . .
. ..
. . . 11-1
11-2 REORDR Dialogue Questions. . . . . . . . . . .
11-4
11-3 REORDR Message Text. . . . . . . . . . . . . .
11-7
12-1 DCL Commands for Managing System Files and Logical
N arne s • • . • . . • . • . • . • . • . . • • . . • •
12-1
13-1 DCL Commands for Job Management . . . . . . . .
13-1
14-1 DCL Commands for Miscellaneous System Functions
14-1
14-2 DISPLY Program Switches. . . .
. .....
14-10
14-3 DISPLY Program Commands . . . . . . . . . . .
· 14-12
14-4 STATE Column Attributes . . . . . . . . . . .
· 14-19
14-S Busy Devices Status Abbreviations: WHY Column . . · 14-21
14-6 Disk Status Abbreviations: COMMENT Column . .
· 14-22
14-7 Message Receivers Abbreviations . . . . . . .
· 14-24
14-8 Run-Time Systems and Resident Libraries Report
Abbreviations . . . . . . . . . . . . . .
· 14-26
14-9 Memory Status Report Abbreviations
. . .
· 14-28
IS-1 DCL Commands for Disk and Tape Handling .
. . .
IS-1
lS-2 Disk Size and Cluster Size
. . . . . .
lS-8
lS-3 The /PUBLIC, /PRIVATE, and /[NO]SHARE Qualifiers
for the MOUNT Command. . . . . . . . . . . .
. lS-18
16-1 /INITIALIZE and lOUT LABEL Interaction During BACKUP 16-9
16-2 BACKUP Quick Reference Table
. . . . . . ..
. 16-11
16-3 /INITIALIZE and lOUT_LABEL Interaction During
RESTORE . . . . . . . . . . . . . . . . . . . . . · 16-18
16-4 RESTORE Quick Reference Table . . . . . . . . . . · 16-21
A-l OPSER Commands • . . . • . . . . . . . . .
A-I0
A-2 OPSER Message and Action Request Contents
A-14
A-3 OPSER Online Job List
..... .
A-16
A-4 QUEMAN Start-Up Commands
.. .
A-21
A-S QUEMAN Start-Up Switches . . . . . . .
A-22
A- 6 QUEMAN Interrupt Commands
. ..
. ..
A-23
A-7 NEXT Command Error Text
. . ..
. ..
A-26
A-8 SPOOL Start-Up Options. . .
. .... .
A- 31
A-9 SPOOL Line Printer Default Values
.. .
A-37
A-IO SPOOL Keyboard Default Values .
. . . . . . . . A-38
A- 39
A-l1 SPOOL Syntax Error Messages . . . .
A-12 SPOOL Interrupt Commands . . . . . . . .
A- 41
A-13 SPOOL User Requested Output Error Messages
A- SO
A-14 BATCH Start-up Options
. . . . . . A- S4
A-IS BATCH Interrupt Commands
. ..
.. .
A- S6
A-16 BATCH Device Type Designators .
A- S7
xiv

A-17 PLEASE Commands to OPSER
... .
A-18 RESTOR Commands through OPSER
.. .
B-1 Bit Values in the PDP-II Word . . .
·
C-l Disk Device Sizes . . . . . . . . . . . . .
D-l General RSTS/E Messages
. . . ..
. .. •
E-l SAVE/RESTORE Functions . .
. ..
E-2 SAVE/RESTORE Switches
...
E-3 SAVE/RESTORE Device Specification Switches.
E-4 SAVE/RESTORE Input Volume Error Messages
E-5 SAVE Dialogue Questions . . . . . . . . . . •
E-6 RESTORE Dialogue Questions .
. ..
E-7 IMAGE Dialogue Questions .
. ... ·
E-8 IDENTIFY Dialogue Question .
. .•.
E-9 Booting RSTS/E and SAVE Set Volumes
•
E-IO Summary Report Run Totals . . . . .
•
E-ll General SAVE/RESTORE Error Messages . . . .
E-12 SAVE/RESTORE Nonfatal Transfer Errors .
•
F-l DEVTST Programs
. . . . .
. .. .
•
F-2 RSTS/E Device Designators
.. .
F-3 DEVTST Error Messages
.. . • •

•

•
•

•

•
•

•

A-60
A- 63
. B-1
. C-l
• D- 2
• E- 4
• E-6
E-IO
E-ll
E -15
E-21
E-27
E-32
E - 35
E - 40
E-42
E - 50
• F-3
F-3
• F-5

Preface

Objectives
This guide tells you how to manage a RSTS/E system on a day-to-day
basis.
To use the features that this guide describes, RSTS/E requires
you to have certain privileges. Only the RSTS/E system manager and
users with the needed privileges should have access to this guide.
Audience
This guide is primarily for use by system managers and operators.
You
do not need to have a great deal of knowledge and experience about
RSTS/E to manage a RSTS/E system. However, to perform certain system
management tasks, you should understand how to use a text editor like
EDT and should be familiar with the DIGITAL Command Language (DCL).
In addition, because not all customers install their own systems, the
manual includes information for DIGITAL field service engineers and
software support representatives.
This information is clearly
indicated.
Document structure
This manual contains 16 chapters and six appendixes:
Chapter I

Contains a glossary of RSTS/E terms and an overview of the
RSTS/E disk structures, system management concepts,
multiple privileges, account management, and file access.

Chapter 2

Describes procedures for starting, halting, and restarting
RSTS/E.

Chapter 3

Describes what you should include in the system start-up
command file.

Chapter 4

Describes the phases that you need to process when
shutting down the RSTS/E system.

Chapter 5

Explains the quotas that you can use to limit the amount
of various system resources that users can have.

Chapter 6

Describes the privileges that you can assign to a user
when you create an account.

xvii

Chapter 7

Gives background information on managing RSTS/E accounts
and then describes the DCL commands that you use to create
and maintain the accounts.

Chapter 8

Gives background information on managing terminals and
then describes the DCL commands that you can use.

Chapter 9

Gives background information on the Print/Batch Services
(PBS) Package and then describes the DCL commands for
using PBS.

Chapter 10

Describes the programs and DCL commands that are available
to help you manage system errors.

Chapter 11

Introduces the concepts of device management and caching
control on your RSTS/E system and then describes the DCL
commands that you can use.

Chapter 12

Gives background information on RSTS/E system files and
logical names and then describes the DCL commands that you
can use to manage them.

Chapter 13

Gives background information on RSTS/E jobs and then
describes the DeL commands that you can use to manage
them.

Chapter 14

Describes miscellaneous DCL commands that you can use to
manage your RSTS/E system.

Chapter 15

Gives background information on working with disks and
tapes and then describes the DCL commands that you can use
to manage them.

Chapter 16

Describes the DCL commands that you can use to back up and
restore disk files and accounts.

Appendix A

Describes the OPSER-based spooling package.

Appendix B

Lists the octal and decimal values of each bit in the
PDP-II word.

Appendix C

Lists the cluster size and total size of each disk that
RSTS/E supports.

Appendix D

Lists the general RSTS/E messages that you may encounter
when using your RSTS/E system.

Appendix E

Describes the SAVE/RESTORE system program for copying and
backing up disks.

xviii

Appendix F

Describes the Device Testing Package (DEVTST) that you can
use to verify the reliability of RSTS/E supported
hardware.

Related Documentation
As system manager you are responsible for setting certain parameters
that affect the monitor and, consequently, the monitor directives.
You also need to make decisions related to the installation and
updating of your RSTS/E system. For more information on these topics,
refer to:
RSTS/E System Installation and Update Guide
RSTS/E System Directives Manual
RSTS/E Programming Manual
For more information on RSTS/E documentation, consult the RSTS/E
Documentation Directory.
In addition to the RSTS/E documentation, you should have access to the
following manuals:
PDP-II Peripherals Handbook
DECnet/E System Manager's Guide
Conventions
Symbols and other conventions represent keyboard characters, or aid in
the presentation of information. This guide uses the following
symbols and conventions:
<RET>

Represents a carriage-return/line-feed
combination. Press the RETURN key on your
keyboard to produce this combination.

<LF>

Represents a line-feed character. Press the LINE
FEED key on your keyboard to produce this
character.

Represents the CTRL key and some other character,
represented here by x. For example, enter
<CTRL/U> by holding down the CTRL key and pressing
the keyboard key labeled "U". RSTS echoes or
displays the character at your terminal as AU.

xix

color

In examples, black characters are data produced by
the computer.
Red characters indicate information that you type.

[ ]

Square brackets show the optional parts of a
command in format statements. For example:
DIRECTORY [file-spec[, ... ]]
The optional parts of the command let you include
a file specification ([file-spec]), or more than
one ([ , ... ]), if you choose.
Square brackets also indicate the choice you have
in using a command. For example:
/[NO]DELETE
This means you can type either /DELETE or
/NODELETE, depending on the form of the qualifier
you select.

Summary of Technical Changes
The RSTS/E System Manager's Guide contains revisions and updates to
reflect the hardware and software that RSTS/E currently supports.
Wherever possible, the examples use the new DCL commands.
The significant changes for RSTS/E are:
o

The default keyboard monitor is DCL

Additional Quotas (see Chapter 5)

Multiple Privileges (see Chapter 6)

Account Management (see Chapter 7)

Terminal Management (see Chapter 8)

Print/Batch Services (see Chapter 9)

Backing Up and Restoring Files (see Chapter 16)

Other Miscellaneous System Management Changes (see Chapters
11-14)

Several utility programs formerly described in this manual are now in
the RSTS/E utilities Reference Manual.
They are:
o

CPATCH

GRIPE

ODT

ONLPAT

RESTOR

TALK

Also, the information on updating the RSTS/E software is now in the
RSTS/E System Installation and Update Manual.

xxi

Chapter I
Overview of RSTS/E System Management

RSTS/E runs on a PDP-II computer.
RSTS/E allows simultaneous,
time-shared access to PDP-II hardware and to RSTS/E software
components through either local or remote asynchronous terminals.
The
RSTS/E Software Product Description, which is part of the RSTS/E media
kit, describes the hardware and software RSTS/E supports.
This guide
describes the software a system manager uses to control the operation
of a RSTS/E system.
The following sections introduce you to some
important RSTS/E concepts.

Glossary of RSTS/E Terms
To understand how RSTS/E works, you need to know these terms:
CCL (Concise Command Language)
A concise way to run a RSTS/E system program.
The CCL syntax
lets you run a program without the RUN command and, unlike the
RUN command, lets you place the entire command on one line.
After the program completes executing, control returns to your
job keyboard monitor.
The system manager chooses the CCL
commands for a particular RSTS/E system.
In DCL, CCL's are
defined using the DEFINE/COMMAND/SYSTEM command (see Chapter 12).
DCL (DIGITAL Command Language)
A set of commands available on many different DIGITAL systems.
These commands perform basic tasks like copying files, printing
files, and running programs.
On RSTS/E, the DCL run-time system
manages the DCL command environment.
See the RSTS/E System
User's Guide for more information about DCL on RSTS/E.
See the
RSTS/E Quick Reference Guide for a complete list of all DCL
commands available on RSTS/E.

1-1

Overview of RSTS/E System Management
Default Keyboard Monitor
The main keyboard monitor that you work with on a RSTS/E system.
You enter the default keyboard monitor after you log in.
The
default keyboard monitor is DCL.
Job
The unit that RSTS/E uses to keep track of you (and other users)
during a terminal session. When you log in, the system creates a
job for you and assigns it a job number.
The system uses your
job number to keep track of everything you do from the beginning
to the end of your terminal session.
Job Keyboard Monitor
The keyboard monitor that manages a job.
Your job keyboard
monitor is the same as the default keyboard monitor, unless you
decide to change it with the SWITCH program. After you change
your job keyboard monitor, you remain under its control until youlog out or use SWITCH again to change your keyboard monitor.
Keyboard Monitor
The part of a run-time system which interprets keyboard commands.
When you work in the DIGITAL Command Language (DCL) environment,
for example, you type commands that the DCL keyboard monitor
receives and interprets.
Each RSTS/E keyboard monitor has an
identifying "prompt" that it displays to indicate when it expects
command input.
Common keyboard monitor prompts on RSTS/E are:
dollar sign ($) for DCL; "Ready" for BASIC-PLUS; angle bracket
(»
for RSX; and period (.) for RTll.
Monitor or Executive
The master control system software that observes, supervises,
controls or verifies the operation of a computer system.
The
collection of routines that controls the operation of user and
system programs, schedules operations, allocates resources, and
performs I/O.
Operating System
The collection of programs, including a monitor or executive and
system programs, that organizes a central processor and
peripheral devices into a working unit for the development and
execution of application programs.

1-2

Overview of RSTS/E System Management
primary Run-Time System
The run-time system that is permanently resident and that was
installed when you established the defaults for your current
monitor.
The primary run-time system must be RSX or DCL.
Program Development
The process of writing, entering, translating, and debugging
source programs.
Public Structure
The set of all disks that are public. When you do not include a
name in your file specification, the system by default
accesses one of the disks on the public structure.
The device
name SY: represents the name for all disks in the public
structure.
Thus, if you do not have any public disks other than
the system disk, SYO: and SY: are equivalents.
If you have more
than the system disk in the public structure, SY: refers to the
aggregate of all public disks.
SYO: refers to the system disk.
devi~e

Run-Time System
System software that manages part of the RSTS/E system.
For
example, the BASIC-PLUS run-time system manages the BASIC-PLUS
programming environment.
The run-time system controls the
interaction between a user or program and the monitor.
System Disk
The disk required by the RSTS/E monitor to start the system and
to allow the system to run properly under timesharing.
RSTS/E
assigns device name SYO: to the system disk.
System Program
Any general-purpose program included in an operating system to
perform common functions.
CUSP is an acronym for Commonly Used
System Program.

System Management
Management of RSTS/E begins with providing a properly tailored
hardware and software configuration, proceeds through initializing the
software at system installation time, and continues with the daily
functioning of ,timesharing.
To make sure you perform these steps
efficiently, you should be familiar with time-sharing concepts and
practices or have a close working relationship with a senior
programmer or analyst experienced with time-sharing systems.
1-3

Overview of RSTS/E System Management
To manage a system well, you should know the processing requirements
of the system and also its capabilities and structure.
Information in
the RSTS/E System Installation and update Guide describes important
aspects of hardware and software options and provides memory
requirements to assist in configuring a RSTS/E system.
As the system manager, you should be particularly careful about
initializing your system for the first time.
Because there are so
many variables, no prepackaged approach can give you a completely
optimized RSTS/E system.
The RSTS/E System Installation and Update
Guide provides detailed information about all the initialization
options.
To make sure that important information reaches the right persons
within your organization, you should make someone responsible for
current documentation of the system.
This responsibility includes
both locally generated and DIGITAL-supplied procedures and guides.
The responsible person should make sure that specified members of the
staff receive the most current system information.
In too many cases,
improper use of resources occurs when responsible individuals do not
have the latest information.

Disk Organization
System managers should understand that the organization of files on
disks is important.
Only with this knowledge can you make the best
use of all system resources.
The following section introduces you to
the concepts of disk and file structures and how to use them to best
advantage.

Types of Disks
RSTS/E supports two types of disks as part of its logical disk
structure: private and public.
The public disk structure consists of
a system disk (the one that was booted and contains the RSTS/E
monitor) and additional public disk packs or disk cartridges.
The
system disk must be physically on line and logically mounted whenever
the system is running; this way, users can gain access to the system
disk during time-sharing operations. All other public disks that
users may need to access must be physically on line and logically
mounted.
The system disk contains:
o

Monitor code

Initialization code

1-4

Overview of RSTS/E System Management
o

The primary run-time system and the default keyboard monitor
(DCL)

The command files for system start-up and crash recovery

Some installations may also use the system disk for storing active
user jobs that are temporarily swapped out of memory.
Remaining space on the public disk structure is used for:
o

Auxiliary run-time systems

Optional system files

System programs

User programs and data files

You can use disk drives not devoted to the public structure for
private disk packs or disk cartridges.
Unlike public disks, you can
logically and physically dismount and move private disks to other
drives during time-sharing operations.
In addition, private disks
make it possible to restrict disk storage to a defined set of users,
which can be a distinct advantage when numerous projects are in
progress.
The file structure of a private disk is the same as that of
a public disk.
In addition to private and public disks, both of which any job on the
system can share and access, you can logically mount a disk for use by
only one job.
In this case, only that job can access the disk. When
the job terminates (for example, by logging out), the disk is
logically dismounted.
See "MOUNT for Disks" in Chapter 15.

File Structures
The RSTS/E file structures let the monitor access system and user data
in an organized way.
RSTS/E currently supports three kinds of file
structures:
o

Level 0.0 -- Is for RSTS/E disks created before V8.0.
You
can mount disks with this structure as read-only, private
disks.
You cannot mount them as system or public disks.

Level 1.1 -- Is the structure created for V8.0.
You can
mount disks with this structure as read/write, private disks.
You cannot mount them as system or public disks.

Level 1.2 -- Is the structure created for V9.0.
You can
mount disks with this structure as read/write, system,
public, or private disks.
1-5

Overview of RSTS/E System Management
Note
If you are upgrading a single disk RSTS/E system to
V9.0, you can mount a Level 0.0 or Level 1.1 disk as
the system disk.
See the RSTS/E V9.0 Release Notes
for information on how to convert your pre-V9.0
system disk to the Level 1.2 structure.
The following three sections describe the three kinds of structures.
If you have a new RSTS/E V9.0 system with all new disks, you can skip
the sections that describe the disk structures before V9.0.
Furthermore, if you have pre-V9.0 disks, DIGITAL recommends that you
use the new DSKCVT disk conversion program to convert them to the new
disk structure (see the RSTS/E System Installation and update Guide).
To see which structure applies to disks on your system, type SHOW
DISKS as shown.
The "Level" column indicates the RSTS/E disk
structure level.
For example:
$ SHOW DISKS <RET)

Disk Structure:
Dsk Open
Size
DRI
66 131648
DR2
0 242576
DR3
33 500352
DR4
0 242572
DR5
0 500352

Free
Clu Err
29424 22%
4
0
33040 13%
8
0
57744 11%
0
8
17528
4
0
7%
76152 15%
0
8

Name
Level
BOWER
1.2
CRONIN 0.0
WOJTAS 1.1
MODNE
1.2
0.0
HOGAN

Comments
Pub, DLW
Pri, R-O, DLW
Pri, DLW
Pri, DLW
Pri, R-O, DLW

Level 0 Disk Structure (Pre-VS.O)
Pre-V8.0 users gained access to files on a RSTS/E system by a Master
File Directory (MFD) and by User File Directories (UFDs).
Figure 1-1
shows these structures.

1-6

Overview of RSTS/E System Management

UFOs

Files

[1,2]
MFO
(Located in [1,1])
[43,98]

Contains pointers
to files, as
well as to
UFOs, in a
"linked list"

[100,150]

[254,254]

MK-{)1027-{)O

Figure 1-1:

MFDs and UFDs in Level 0 File structure

As Figure 1-1 shows, each disk initialized for use on a RSTS/E system
contains an MFD, located in [1,1].
The system uses the MFD to catalog
other accounts on the disk.
The MFO on the system disk lists the
accounts that can be used to log in to the system.
On a private disk,
the MFO contains entries of accounts that can create files on that
disk.
Any user can access any file on any disk if the protection code
of the file permits.
Only users whose accounts are entered in the MFO
on a private disk can create files on that disk.
The system creates one UFO for each user account on a disk when the
manager sets up the account (or, optionally, when a user creates the
first file for the account).
The UFO catalogs all program and data
files under an account and maintains accounting and access information
for these files.
The UFO contains all retrieval information for the
files because each file is pure data and has no linkage or structural
information.

1-7

Overview of RSTS/E System Management
Levell Disk Structure (for VS.O and V9.0)
In V8.0 and V9.0, users access files on a RSTS/E system through the
use of three structures:
o

A Master File Directory (MFD)

A Group File Directory (GFD)

A User File Directory (UFD)

Figure 1-2 shows how these structures are related.
UFOs

Files

[1,1]
GFOs

MFO

[1, *]

[1,25]

[43,*]
[43,98]
Contains pointers
to GFOs by
"direct access"
[100,60]
[100,*]

[100,210]

[254,*]

[254,254]

MK-{)102!HlO

Figure 1-2:

MFD, GFDs, and UFDs in the Levell File Structure

As Figure 1-2 shows, the MFD contains pointers to the Group File
Directories (GFDs).
The GFDs point to UFDs within each group.
For
example, a pointer in the MFD could access the GFD for files in [43,*]
directories, from which it could access a specific UFD, such as
[43,98].
1-8

Overview of RSTS/E System Management
Differences Between Level 0, Level 1.1, and Level 1.2
The new disk structure (Level 1.2) differs from the previous disk
structures (Level 0 and Level 1.1) in the following ways:
o

The account data on Level 1.2 contains attribute blockettes
for the new or expanded attributes such as quotas, multiple
privileges, and long passwords.

The MFD on Level 1.1 and Level 1.2 is not associated with an
account number.
On Level 0, the MFD was located in [1,1], and had to be at
Block #1.
Now, Block #1 points to the location of the MFD,
allowing the MFD to be placed anywhere on the disk.

The MFD and GFDs on Level 1.1 and Level 1.2 do not store
files.
On Level 0, the MFD could store files as well as point to
accounts.

GFDs on Level 1.1 and Level 1.2 allow more direct access to
accounts.
On Level 0, the MFD contained a linked list of pointers to
all the UFDs.
UFDs were listed in the order in which they
were created with the REACT program; the MFD searched the
list of directories in sequence until it located a UFD.
Now, the MFD contains
point directly to any
UFDs remains the same
display accounts (for
accounts in ascending
creation.

direct pointers to GFDs, which in turn
UFD.
(However, the structure of the
as in Level 0.) Thus, DCL commands that
example, SHOW ACCOUNT) list the
order, rather than in order of

You can create up to 65,025 accounts with the Level 1.1 or
Level 1.2 structure.

with the Level
structure only 1735 accounts could be
created and referenced on a disk. Now, you can create
accounts for 255 groups, each with 255 users.
Only the disk
size restricts the number of accounts.
The users on your system should not see the differences between the
three structures.
Levell takes up a little more disk space.
There
are more pointers, because each group is handled separately, but
access to files is faster and the system can have more accounts.
The
linked list structure of the MFD is replaced by direct access to GFDs.

1-9

Overview of RSTS/E System Management
Disk Optimization
When a user tries to access a file on the public structure, the system
searches the directories on all disks that are part of the public
structure. The search verifies whether the file exists. You can
avoid the overhead of searching more than one disk by placing
frequently accessed files on a private disk. This technique is valid
for systems with a number of disks in the public structure, as well as
for a system whose public structure consists of only one disk. The
ability to place and preextend directories can also help you optimize
disks (see Chapter 7).
It is sometimes an advantage to dedicate an entire private disk to a
single large production file. Such organization ensures an efficient
directory structure and minimizes overhead to access file data. When
more than one file is on the same private disk, it is best to dedicate
a whole account to each production file. The system then spends less
time searching the directory for file information.
In general, you should keep volatile files and stable files in
separate accounts to avoid fragmentation. Where file entries in the
directory are spread across the face of the disk rather than being
confined to a few sequential blocks, fragmentation requires the disk
head to move more than is optimally efficient. Preextending
directories can ensure that the directory is in sequential blocks (see
Chapter 7). REORDR can restructure the directories on your system to
improve disk access time (see Chapter 11). You can also optimize disk
usage by separating frequently accessed files from those you use less
often.
In an environment where distinct data files must be accessed by the
same program, the optimal organization is to keep each file on a
different private disk. If a program must access more than one file
on the same disk, overhead is increased because of disk-head movement.
A large percentage of time is spent, therefore, in moving the head
back and forth. However, if each file referenced by the program
exists on a distinct private disk, head movement is not required
whenever a program references another file. Head movement is
restricted to locating the data itself. Positioning of directories
can also help reduce head movement (see Chapter 7).

System Operation Concepts
Immediately after logging in to the system, a user's terminal is under
the control of DCL (the system's default keyboard monitor). The
terminal is said to be at the system command level because you can
type a system command and the keyboard monitor processes it
accordingly. The terminal returns to the system command level when a
command or program completes executing, or when you enter a CTRL/C at
the terminal. When the terminal is at the system command level, the
1-10

Overview of RSTS/E System Management
keyboard monitor examines each ASCII text line entered and determines
whether that line is a system command.
System commands are executed
upon entry as described in the RSTS/E System User's Guide.
The user job area is initialized at log-in time and set to a size of
at least lK words (K = 1024).
The job area can grow in increments of
IK words to a maximum size set by the system manager at the start of
time-sharing operations.
The maximum size for any job image,
including memory used by the current run-time system of the job, is
64K words.
This is the maximum size that the PDP-II Instruction and
Data (I&D) architecture (PDP-Il/45,50,55,44,70,73) allows.
For a
PDP-II without I&D architecture (PDP-ll/23+,24,34,35,40,60) the
maximum size is 32K words.
Under the RSTS/E system, jobs run one at a time. A job runs until it
enters an Input/Output (I/O) wait state or until it exhausts the time
quantum assigned to it either by the system or the system manager.
When the current job stops running, the scheduler runs the next job
that is ready.
Meanwhile, the interrupt-driven I/O device handlers
are processing requested data transfers. After completing a transfer,
the scheduler marks the job that requested the transfer as ready to
run again and starts it from the point at which execution stopped.
RSTS/E tries to keep as many jobs in memory as possible. When a job
requires more memory than is available, the system moves some jobs out
of memory to temporary storage in one of up to four areas known as
swap files.
This operation is called swapping.
By convention, these
files are named SWAPO.SYS, SWAPl.SYS, SWAP.SYS, and SWAP3.SYS. When
memory becomes available for a job stored in a swap file, it is
swapped back into memory.
Jobs waiting for keyboard input and jobs
waiting for device I/O completion are most likely stored in the swap
files, while jobs currently running or involved in disk or magnetic
tape data transfers are stored in memory.
As the system processes each job, it maintains accounting information
in memory for that job. When the job is logged off the system, the
information is used to update the accounting information stored on the
system disk for that account.

Privilege
You must have a way to prevent general access to activities that can
damage the system.
The multiple privileges feature gives you finite
control over access to activities.
You can limit user access to just
those activities suitable to each job. Multiple privileges gives you
a tool to enhance both system performance and security.

1-11

Overview of RSTS/E System Management
Multiple Privileges
The multiple privilege feature groups similar system functions into
sets and defines a privilege to control access to each set of
functions.
A group of 34 privileges govern the entire set of RSTS/E
system functions.
The privileges given to an account determine the
range of functions available to the user.
Some privileges apply to
very specific functions, while others control functions within broader
classes of system use (see Chapter 6).

Classes of System Activities
The following sections divide some computer activities into general
classes of system functions and discuss the privileges that control
them.
They describe:
o

Account Management Activities

File Access Activities

Account Management Activities
One general class of system activity is account management. A user
accesses a computer through an account.
The individual account is a
member of a group, which contains all other accounts with the same
project number.
The group, in turn, is a subset of a world, which
contains all accounts on the system. Account management activities
include creating and deleting accounts, as well as changing passwords,
disk quotas, and expiration dates.
The following privileges control
account management:
GACNT

Group .Account Management -- Grants account management
privileges within the user's group.

WACNT

World Account Management -- Grants account management
privileges for all accounts.

SETPAS

Set Password -- Allows changing one's own password.

File Access Activities
Another general class of system activity is file access.
Users
routinely access files.
Some files are created by the user and reside
in the individual's account.
Other files reside in the accounts of

1-12

Overview of RSTS/E System Management
other users or in system accounts.
File access activities include
creating, deleting, renaming, reading, writing, and executing files.
Both the protection code of the file and the privileges granted to the
user can affect whether the system grants or denies file access.
In the case where no privileges are granted to a user, protection
codes control the types of ope~ations that a user can perform on a
file.
The SET PROTECTION command (or the /PROTECTION qualifier in the
RSTS/E file specification) passes a value to the system that sets bits
in the protection code byte.
Each bit specifies that the activity
named by that bit is prohibited or allowed.
Certain privileges also govern file access activities.
Some
privileges override protection codes completely.
The following
privileges grant a user the right to perform certain file access
activities, regardless of protection codes:
GREAD

Group Read -- Read any file within the group.
Also, execute
any program within the group, if the program's executable
bit is set.

WREAD

World Read -- Read any file on the system. Also, execute
any program on the system, if the program's executable bit
is set.

GWRITE

Group Write -- Create, delete, extend, modify, or rename any
file within the group.

WWRITE

World Write -- Create, delete, extend, modify, or rename any
file on the system.
Note
In addition to WWRITE, you need SYSIQ privilege to
create, delete, extend, modify, or rename any file
in group zero ([0,*]).

1-13

Overview of RSTS/E System Management
Multiple Privilege Masks
You assign a certain set of privileges to each account. The system
stores this set of privileges in privilege masks. A privilege mask is
a set of flag bits with one bit corresponding to each privilege.
For each active job, RSTS/E keeps 3 masks:
o

Authorized mask -- The set of privileges that you give to the
account. Users can use the SHOW ACCOUNT/FULL command to list
the set of privileges available to their own account.

Current mask -- The set of privileges now in effect for the
job. The system always references this mask when it performs
a privilege check. Users can raise or lower their privileges
(up to their authorized limit) with the SET JOB/PRIVILEGE
command.

Saved mask -- The saved record of the current privileges when
a job gains temporary privileges (see the section "Temporary
Privileges").

When a user attempts to perform an activity that is restricted by one
or more privileges, the system performs a privilege check. It
examines the current mask to determine if the requesting job has all
the privileges required to perform the activity. If the requesting
job has insufficient privilege to perform the activity, the system
returns one of the following errors:
o

?Protection violation

?Illegal SYS() usage

?privilege XXXX required

1-14

Chapter 2
starting, Halting, and Automatic Recovery of RSTS/E

This chapter describes how to start and halt a RSTS/E system and how
the system recovers automatically from catastrophic system errors.
This chapter also describes how to create the start-up conditions for
a RSTS/E system.
See the RSTS/E System Installation and Update Guide
for a description of all other initialization code options and their
functions.

starting up RSTS/E
To start a RSTS/E system, you must first load into memory a program
containing the initialization code (INIT.SYS) and then answer YES to
the 'Start timesharing?' question.
INIT.SYS is a large, stand-alone program that, once you transfer it
from the RSTS/E distribution kit, exists on the system disk.
INIT.SYS
can provide a number of important system functions, such as:
o

Creating the RSTS/E file structure

Creating system files

Installing a RSTS/E monitor

Setting system defaults

Creating start-up conditions for RSTS/E

INIT.SYS does some of these automatically; however, they can also be
done through the Option: prompt.
Before you can use the initialization code to start your RSTS/E
system, you must move the code into memory.
This is called
bootstrapping.
The following sections describe how to transfer the
intializat~on code into memory.

2-1

starting, Halting, and Automatic Recovery of RSTS/E
Bootstrapping RSTS/E with a Hardware Bootstrap Loader
The procedures for bootstrapping RSTS/E depend on the type of hardware
bootstrap loader and the type of disk you use as the system device.
You should make sure:
o

The system disk is physically mounted on a disk unit.

The drive on which the system disk is mounted has the READY
light on and is in the WRITE ENABLE condition.

All required units are running and READY.

The console terminal is on line.

Read the RSTS/E System Installation and update Guide for the proper
instructions on using the hardware bootstrap on your system.
After you use the bootstrap to load the initialization code, INIT.SYS
marks the successful completion of the bootstrap procedure by printing
an identification line that includes the RSTS version number, the
installation name, the disk unit bootstrapped, and the INIT version
number, followed by the Current date prompt.
Enter the date and press
RETURN.
INIT displays the Current time prompt.
Enter the time and
press RETURN.
INIT displays the start timesharing prrimpt.
For
example:
RSTS V9.0 installation-name (DMO) INIT V9.0
Current date <DD-MMM-YY>? l5-Jan-85<RET>
Current time <HH:MM AM/PM>? 8:15 AM<RET>
start timesharing <Yes>?
If the program does not
terminal is on line and
an error message on the
Installation and Update

print this information, make sure the console
try the operation again.
If the system prints
console terminal, see the RSTS/E System
Guide for recovery procedures.

If you want to enable the automatic restart facility, set the CPU
switch register so bit 0 is ON.
The automatic facility remains
enabled as long as the CPU switch register remains set in this way.
If your CPU does not have a switch register, the automatic restart
facility is always enabled.

Bootstrapping RSTS/E after a System Halt
When a RSTS/E system halts as a result of a catastrophic error, RSTS/E
displays the halt address in the address lights.
For central
processors that do not have console lights, for example the
2-2

starting, Halting, and Automatic Recovery of RSTS/E
11/23-PLUS, the 11/44, and CPUs with Remote Diagnostic Consoles
(RDCs), the system prints the address on the console terminal.
It is
essential that you record this address.
The exact procedure for
examining memory locations depends on the type of processor and front
panel of your system.
Your DIGITAL Software Specialist can describe
the procedure for your system.
Once you record this information,
bootstrap your system again using the procedures de~cribed in the
previous section.
See the section "Automatic Recovery and Restart
Facilities" for a description of catastrophic errors, system crashes,
and crash dumps.

starting Timesharing
After you bootstrap the system disk, RSTS/E loads the initialization
code (INIT.SYS) into memory.
INIT then prints an identification line
followed by the Start Timesharing <Yes>? prompt on the console
terminal.
You can answer in one of four ways:
o

Type YES or press RETURN to start the monitor named in the
INIT logo

Type START monitor-name and press RETURN to install and start
another monitor in [0,1] (not currently installed)

Type START and press RETURN to have INIT prompt you for a
monitor name.
For example:
Monitor name to start <default name>?
The default name is the name of the currently installed
monitor, or the first Save Image Library (SIL) file found in
the [0,1] directory.
Press RETURN to start the named
monitor.
Type a question mark (?) character to have INIT
display a directory of all SILs in [0,1].

Type NO to have INIT proceed to the Option prompt.
The program is ready to accept one of the options that Table
2-1 summarizes.
See the RSTS/E System Installation and
Update Guide for a complete summary of these options.

2-3

starting, Halting, and Automatic Recovery of RSTS/E
Table 2-1:

Initialization Option Summary

+ - - - - - - - - - - - + - - - .- - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
I Option
I Abbreviation I
Meaning
+- - - - - - - - - - -+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
! BOOT
BO
Bootstraps a magnetic tape or disk.

COpy

Transfers required files from the
distribution medium to a system disk
and bootstraps the system disk.

DATE

Resets the current date and time. Also,
establishes default date and time
formats.

DEFAULT

Establishes or changes a monitor's
start-up defaults such as the job and
swap maximum.

DSKINT

Initializes and optionally formats a
disk. It also checks for bad blocks.

HARDWR

Specifies device controller
characteristics.

IDENT

Prints INIT.SYS creation date and a
list of patches.

PATCH

Modifies RSTS/E system code to correct
program errors and to add new program
features.

REFRESH

creates and positions system swap
files, adds bad blocks to the bad block
file, and positions optional system
files on the system disk or any
auxiliary disk.

SAVRES

Backs up (SAVE), reconstructs
(RESTORE), or makes an image copy
(IMAGE) of a RSTS/E disk.

START sil

ST sil

Installs the specified Save Image
Library (SIL), assigns and checks
defaults, and starts the RSTS/E system.
If you do not enter a name for the SIL,
INIT prompts you for one.
+- - - - - - - - - - -+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

2-4

starting, Halting, and Automatic Recovery of RSTS/E
Halting the RSTS/E System
A system crash or setting the CPU console HALT/ENABLE switch to its
HALT position causes a RSTS/E system to halt.
RSTS/E considers the
PDP-ll/70 and PDP-ll/45 to be in a halt state when both the RUN and
PAUSE indicators on the CPU console panel are not lit.
For
PDP-ll/23-PLUS and PDP-ll/44 processors, the RUN light is off when the
system is in a halt state.
In all other cases, the CPU is running.
The SHUTUP program shuts down the RSTS/E system.
During this
operation, SHUTUP makes sure all files are properly closed and that
system accounting information is accurately updated.
If you want to
turn the power off, run SHUTUP, wait for INIT's Start timesharing?
prompt, and press the HALT/ENABLE switch.
See the section "Performing
System Shutdown: SHUTUP" in Chapter 4 for a complete description of
the SHUTUP program.
DIGITAL recommends that you do not halt RSTS/E during timesharing by
moving the HALT/ENABLE switch on the CPU console to its HALT position.
If you do this during system shutdown, SHUTUP may not have completed
clean-up operations; consequently, file data can become corrupted and
accounting information may be lost.
The only way to recover from such
a halt and to salvage file information is to do the following:
1.

Raise the HALT/ENABLE switch back to its ENABLE position
before you take any other action

Press the CaNT switch to return the RSTS/E system to the
state it was in before the halt

Automatic Recovery and Restart Facilities
This section describes how catastrophic errors occur and how your
system can automatically recover from them.
The section also points
out the need to include commands in the START. COM file to perform
critical system operations when the system restarts in automatic mode.

Catastrophic Errors and System Crashes
Catastrophic errors and system crashes result from unexpected error
traps.
(For information on error traps, see the related processor
handbook.) The processor can cauie unexpected error traps when it:
o

Refers to a nonexistent or nonresponding memory address (for
example, bus time-out trap)

2-5

starting, Halting, and Automatic Recovery of RSTS/E
o

Refers to an odd address with an instruction that requires a
word address

Attempts to execute a reserved or nonexistent instruction

Also,if the monitor detects a condition which it knows should not
normally occur, the monitor can force a software crash.
Catastrophic
errors and system crashes may occur as a result of three types of
problems:
o

Privileged job programming errors
RSTS/E system software is designed to protect itself against
programming errors occurring in nonprivileged jobs. When it
detects such an error, the system aborts execution of the
user request and returns a corresponding error message to the
user's program.
RSTS/E software is vulnerable to some types of errors caused
by jobs with certain privileges.
The privileges that require
special caution are SYSIO, SYSMOD, and WRTNFS.
Even though
most errors do not cause the system to crash, you should take
special care when programming with privileged system function
calls such as Poke memory SYS call (SYS -6).
See the RSTS/E

Programming Manual.
o

Hardware malfunctions
Hardware malfunctions can cause the system to crash.
If
system crashes or catastrophic errors occur that you cannot
explain (particularly on systems that have traditionally been
functioning well), it is likely that a hardware problem has
occurred.
You can diagnose hardware problems by examining
the output logged by the programs in the RSTS/E System Error
package.
See Chapter 10 for information on error logging.

System software malfunctions
Although every attempt has been made to detect and eliminate
system software errors, it is possible that RSTS/E software
can crash unexpectedly.
If a problem of this type is
discovered (it should be reproducible in a defined
environment and under defined conditions), contact a DIGITAL
Software Specialist. As problems of this type become known,
DIGITAL reports them in the "RSTS/E Software Dispatch" and
corrects them as soon as possible.

2-6

starting, Halting, and Automatic Recovery of RSTS/E
Automatic Recovery from Catastrophic Errors
The system takes action in one of two ways when an unexpected error
trap occurs:
o

A catastrophic error that affects only one user

A system crash for which some software or hardware problem
may be responsible

For a catastrophic error, the system determines which user was
responsible for the error.
It flags the user's job with a special
code; this causes the system to completely reinitialize that user's
job area when it is the user's turn to run.
The system prints an
error message on the user's terminal, followed by the text: ??Program
lost-sorry.
The system resumes normal time-sharing operations.
Note
Some run-time systems may issue other error messages.
When the system detects a condition from which it cannot recover, it
does the following:
1.

Writes an image of read/write memory and tables to the
CRASH.SYS file.

Bootstraps the system disk.

Loads the initialization code into memory.

Rebuilds the system disk.

Executes an automatic restart.
(This occurs if the CPU
switch register has bit 0 set and if at least one minute has
passed since start-up.)

If the CPU register does not have bit 0 set or if one minute has not
passed since start-up, the system does not perform an automatic
restart.
The system will only reboot; it will not restart.
In other
words, the automatic restart operation restarts timesharing using
commands in the START.COM file.
In contrast, a reboot merely loads
the initialization code (INIT.SYS) into memory.
INIT.SYS then prints
its Start timesharing? <Yes> prompt, to which you can answer by typing
any of the options in Table 2-1.
If the system restarts automatically, it bootstraps itself into memory
from the system disk. After the system is bootstrapped into memory,
control passes to the initialization routines.
The system recognizes
start-up was through an automatic restart rather than through normal
start-up.
Consequently, the system initializes itself in automatic
restart mode.
If an error trap occurs within one minute of system
2-7

Starting, Halting, and Automatic Recovery of RSTS/E
start-up or if two error traps occur within the same minute, the
system halts at address 54. During automatic restart the system
protects itself against an infinite loop or error traps and automatic
restarts caused by a repeating hardware malfunction.

Automatic Restart Mode Initialization
When the system is initialized in automatic restart mode, control
bypasses all parts of the initialization code that call for operator
intervention and initializes the system using parameters specified at
previous startup. The system:
1.

Logs job 1 in to the system onKBO: under account [1,2]

Invokes [O,l]SYSINI.COM

Executes [O,I]START.COM with the PI argument set to 'CRASH'
rather than 'START'

Performs specific operations appropriate for an automatic
restart

Power-Fail Hardware Used by RSTS/E
When power fails, a PDP-II processor traps through the vector at
location 24. When power is restored, you can configure the system to
do one of three things:
o

Halt.

Boot a specific device.
If the hardware is configured to boot the system disk,
INIT.SYS prints its identification line and the Start
timesharing <Yes>? prompt and wait for you to enter one of
the options from Table 2-1.

Trap again through the vector at location 24.
In this case, the system must have core memory or battery
backup. If memory contents are still valid (which means the
battery backup is not exhausted), RSTS/E performs an
automatic restart.

2-8

Chapter 3
The System Start-up Command Files

This chapter describes how you control system start-up with the system
start-up command file (START.COM).
start-up occurs when you answer
YES to the start timesharing <Yes>? prompt, use the START option of
the initialization code, or when the system restarts automatically.
At start-up, the monitor executes the command file [O,l]SYSINI.COM
which in turn executes [O,l]START.COM.
You can modify START.COM (but
not SYSINI.COM) to suit the requirements of your installation.
To control start-up efficiently, you should understand the conditions
at start-up time:
o

The monitor logically mounts only the system disk read/write

No output is made to any terminal (except the console)

The monitor logs the console terminal KBO: into the system
under the system library account [1,2]

The monitor assigns ALL privileges to this initial job
regardless of the privileges assigned to account [1,2]

The monitor loads the DCL run-time system

The monitor starts execution of the command file
_SYO:[O,l]SYSINI.COM at the console

Creating and Using Command Files
The SYSINI.COM command file contains commands necessary to initialize
your RSTS/E system properly.
This command file is reserved by
DIGITAL; do not edit this file in any way.
The START.COM file that
comes with the RSTS/E distribution kit is a sample only; it may not
execute properly on your system without modification. Make sure
3-1

The System Start-up Command Files
START. COM includes the necessary commands to initialize your
installation. Use a text editor on your system to modify the sample
START. COM file supplied with the RSTS/E kit.
Note
Be sure both command files are in account [0,1] on
the system disk.
The start-up control file should perform the following operations:
o

Mount public and private disks

Assign system-wide logicals

Run the ERRINT program to start error logging

Enable data caching (if selected at system installation)

Set default system characteristics

Install run-time systems

Install libraries

Set terminal characteristics

Define CCL commands

Set printer characteristics

Start Print/Batch Services (PBS) package

Start OPSER-based spooling package (optional)

Start error analysis if needed

Enable logins

Logout the initial start-up job

The order in which the operations are performed is critical. For
example, mounting all public disks ensures the integrity of the public
structure by making available all files on the system. You can mount
any private disks in a similar manner. The various steps tailor the
system according to your installation's requirements.

3-2

The System Start-up Command Files
System Start-up Command File: START.COM
A complete system start-up command file contains the required commands
to perform initialization for timesharing and to perform routine
operations.
The following sample shows a start-up command file:
$
PI - Type of startup (either START or CRASH)
$
$
$
*** Prompt to continue ***
$
$
$ S = "system startup"
$ if PI .eqs. "CRASH" then S = "crash restart"
$ _inquire/nopunc/exit=END/time_out=IO GO "Proceed with ,'S'? <YES>"
$ if f$instr(I,"YES",f$edit(GO,-2)) .eq. I then _goto START
$END:
$ exit
$START:
$ open/logfile/replace
'PI'.LOG
$ -set noecho/warning
$ -set verify
$ -write 0 ""
$ -write 0 " Beginning RSTS/E "S' ... "
$ -set noon
$ $
*** Mount the Disks ***
$
$ S = ""
$ if PI .eqs. "CRASH" then S = "and rebuilding"
Mounting "S'disks"
$ -write 0 f$time()+"
(If this is a crash recovery, MOUNT will rebuild
$
the disks if need be.)
$
examples:
$
$ mount/nowrite DR3:LIBRAR L:
$
$ mount DB2:LOOKUP
$
$
*** Assign (or Replace) System-wide Logicals ***
$
$
Assigning logical names"
$ write 0 f$time()+"
examples:
$
$ assign/system
_SY:[2,9]
FERN:
$
$ assign/system/replace _DB2:[0,3] ERROR$:
$

$
$
*** Start Error Logging ***
$
$ write 0 f$time()+"
Starting error logging"
$ -set job/priority=O
$ if PI .nes. "CRASH" then _goto CONTI
(continued on next page)

3-3

The System Start-up Command Files
If you have more than 128K you should
$
$ _run ERROR$:ERRINT
replace the next line with 100/LOCK
100
YES
$ EOD
$ -goto CONT2
$CONTl:
If you have more than l28K you should
$
$ _run ERROR$:ERRINT
replace the next line with 100/LOCK
100
NO
$ EOD
$CONT2:
$ _set job/priority=-8
$ !
$
*** Enable Caching and set Default System Characteristics ***
$
$ _write 0 f$time()+"
Setting system characteristics"
$ set cache/file/enable/keep=lS/clustersize=2
$ set system/date_format=alphabetic
$ set system/time format=am pm
$ set system/labeI=dos
$ set system/density=1600
$ set system/name="EDERE"
$ set system/powerfail_delay=300
$ set system/password_prompt=(network,dialup)
$
$
*** Install the Run-time Systems and Libraries ***
$
$ write 0 f$time()+"
Installing run-time systems"
$ =run $UTLMGR.TSK
install/runtime_system BASIC
install/runtime_system TECO$:TECO
install/library EDT$:EDT
install/library RMS$:RMSRES
install/library/noaddress RMS$:RMSLBA
install/library/noaddress RMS$:RMSLBB
install/library/noaddress RMS$:RMSLBC
install/library/noaddress RMS$:RMSLBD
install/library/noaddress RMS$:RMSLBE
install/library/noaddress RMS$:RMSLBF
install/library RMS$:DAPRES
$ EOD
$
$
*** Set Terminal Characteristics ***
$
$ write 0 f$time()+" 'Setting terminal characteristics"
$ -run $TERMGR.TSK
set terminal kbO:/device type=LA34/perm
! Hard copy-console.
(continued on next page)

3-4 '

The System Start-up Command Files
set terminal kbdO:/device type=LAIOO/perm
! Pseudo keyboard 0 for batch
!set terminal kbfO:/speed=9600/device_type=VTIOO/perm
! DHO line 0 as VT100 at 9600 baud
!set terminal kbgO:/speed=9600/device type=VTIOO/perm
! DZO line 0 as VT100 at-9600 baud
!set terminal kbg8:/speed=9600/device_type=VT240/perm
! DZI line 0 as VT240 at 9600 baud
$ EOD
$
$
*** Define System Commands ***
$
$ _write 0 f$time()+"
Defining system commands"
$ ! Install system commands (CCLs)
$ _run $UTLMGR.TSK
define/command/system ATT-ACH $LOGIN.* /priv/linenumber=CCL
define/command/system BCK- RMS$:RMSBCK.TSK /linenumber=O
define/command/system BPC-REF AUXLIB$:BPCREF.* /linenumber=CCL
define/command/system BYE- $LOGOUT.* /priv/linenumber=O
define/command/system CCL[O,l]DCL.RTS /priv/linenumber=8192
define/command/system DI-RECTORY $DIRECT.* /priv/linenumber=CCL
define/command/system DSP- RMS$:RMSDSP.TSK /linenumber=O
define/command/system EDT- EDT$:EDT.TSK /linenumber=O
define/command/system FIT- AUXLIB~:FIT. /priv/linenumber=CCL
define/command/system HELLO- $LOGIN.* /priv/linenumber=O
define/command/system HELP- HELP$:HELP.* /priv/1inenumber=CCL
define/command/system IFL- RMS$:RMSIFL.TSK /linenumber=O
define/command/system LBR- $LBR.TSK /linenumber=O
define/command/system LIBR- $LIBR.SAV /linenumber=8208
define/command/system LIN-K $LINK.SAV /linenumber=8208
define/command/system LOG-IN $LOGIN.* /priv/linenumber=O
define/command/system MACR-O $MACRO.SAV /linenumber=8216
define/command/system MAC$MAC.TSK /linenumber=O
define/command/system MAK-E TECO$:TECO.TEC /linenumber=3584
define/command/system MU-NG TECO$:TECO.TEC /linenumber=3584
define/command/system PAT- $PAT.TSK /linenumber=O
define/command/system PIP- $PIP.SAV /priv/linenumber=8208
define/command/system RST- RMS$:RMSRST.TSK /priv/linenumber=O
define/command/system SUB-MIT $QUE.* /priv/linenumber=CCL
define/command/system SW-ITCH $SWITCH.* /priv/linenumber=CCL
define/command/system SY-STAT $SYSTAT.* /priv/linenumber=CCL
define/command/system TE-CO TECO$:TECO.TEC /linenumber=3584
define/command/system TKB- $TKB.TSK /linenumber=O
$ EOD
$ *** Set Printer Characteristics ***
$
$ _write 0 f$time()+ "

$
$
$
$

Setting printer characteristics"
examples:
$ set printer LPO:/device_type=LP11
$ set printer LP1:/device_type=LA180
$ set printer LP2:/device_type=LN01
(continued on next page)
3-5

The System Start-up Command Files

$
*** start Spoolers ***
$
$ _write 0 f$time()+"
Starting spoolers"
$ ! Start PBS spooling package
$ _start/queue/manager
$ !
$
** OPTIONAL** Start OPSER (old) spooling package
$
$ _goto CONT3
! If OPSER is desired, delete this line.
$ ! Install related system commands
$ define/command/system PL-EASE OPSER$:PLEASE.* /priv/line=CCL
$ =define/command/system QU-EUE $QUE.* /priv/linenumber=CCL
$ run OPSER$:OPSER
LOG OPSER$:OPSER.LOGjALL
CHA KBO:
MESS ALL
OPER KB*:[1,2]
DETACH
$ run OPSER$:QUEMAN
DETACH/PRI:O/RUN:6
$ _set job/priority=-8
$ run OPSER$:SPOOL
LPO:/HEAD:2/RUN:9/WIDTH:80
$ _set job/priority=-8
$ _run OPSER$:SPOOL
LPI:/HEAD:I/RUN:9/WIDTH:132
$ set job/priority=-8
$ -run OPSER$:BATCH
BAO:/ERROR:FATAL/NOQUEUE/NODELETE
$ set job/priority=-8
$ -run OPSER$:BATCH
BAI:/ERROR:FATAL/NOQUEUE/NODELETE
$ EOD
$CONT3:
$
$
*** Start ANALYS if in Crash Recovery ***
$
$ if PI .nes. "CRASH" then _goto CONT4
$ =write 0 f$time()+"
Starting analysis"
$ run ERROR$:ANALYS
[O,I]CRASH.SYS
ERROR$:ANALYS.DMP
ERROR$:ERRCRS.FIL/DET
$ EOD
$CONT4:
$
$
*** Enable Logins ***
$
$ _set system/log ins
$ _broadcast/all "RSTS/E is on the air ... "
$ _close/logfile
(continued on next page)
3-6

The System Start-up Command Files
$ _set noverify
$ set echo
$ _logout/br
$ exit

Note
The start-up control files must be in [0,1] on the
system disk (_SYO:, the disk that was bootstrapped).

Mount All Disks
To ensure the integrity of the public structure by making available
all files on the system, you should mount all public disks.
You can
mount any private disks in a similar manner.
If this is a restart
from a system crash, MOUNT rebuilds the disks as required.
See
Chapter 15 for more information on mounting and initialization of
disks.

Assign System-Wide Logical Names
You can assign a system-wide logical name to a specified device type,
unit number, and PPN (optionally) with the ASSIGN/SYSTEM command.
See
Chapter 12 for more information on the use of system-wide logical
names.

Start Error Logging
It is important that you run the ERRINT program on your system.
This
program sets initial conditions for system error logging and runs the
ERRCPY program which transfers to a disk file all errors logged by the
RSTS/E monitor.
If ERRINT is the first program to be run (as DIGITAL
recommends), it will occupy job number 1 on the system and thus be
easily monitored.
Chapter 10 describes ERRINT and ERRCPY.
Note
If your system has more than l28K words of memory,
you should replace the first lines after the RUN
ERRINT command lines with 'IOO/LOCK' to keep ERRINT
resident at all times.

3-7

The System Start-up Command Files
Enable Caching (Optional)
The SET CACHE/FILE/ENABLE command enables caching of data files whose
UFD entry or OPEN MODE specifies caching. The /KEEP qualifier lets
you specify the time that an unused cache cluster is kept in memory_
The /CLUSTERSIZE qualifier controls the number of contiguous data.:
blocks that are copied from the disk to the cache whenever file data
is cached. Data caching is an optional. feature that you can select at
system installation. For more information on data and directory
caching, see the section "SET CACHE Command and Qualifiers" in Chapter
11.

Set Default System Characteristics
The SET SYSTEM command sets the default system characteristics.
the sample START.COM, for example:
0

The date format is alphabetic

The time format is AM PM

The magnetic tape label is DOS

The magnetic tape density is 1600 bpi

The system name is EDERE

The power fail delay is 300 seconds

NETWORK and DIALUP users must enter the system password

See Chapter 14 for more information on setting system default
characteristics.

Install

Run~Time

Systems

The INSTALL/RUNTIME SYSTEM command installs auxiliary run-time systems
(like BASIC) in memory. See the section "Run-time System Control" in
Chapter 12 for more information.

Install Libraries
The INSTALL/LIBRARY command installs resident libraries (like RMSRES)
in memory. See Chapter 12 for more information on resident library
control.

3-8

The System Start-up Command Files
Set Terminal Characteristics
At start-up time, the system sets the characteristics of all keyboard
lines (except line number 0) to hard copy, 80 column output at the
line speed of 300 baud. Thus, you need to use the SET TERMINAL
command to set the correct characteristics of your terminals. Chapter
8 contains detailed descriptions of the SET TERMINAL command
qualifiers.

Define System Commands
It is most convenient to define Concise Command Language (CCL) system
commands on the system at the start of timesharing using the
DEFINE/COMMAND/SYSTEM command. The abbreviations shown in the
definitions of the CCL commands reflect the way the RSTS/E
documentation describes the commands. As the system manager you can
redefine the abbreviations. You should not alter the fully defined
command because each program is coded to recognize the fully expanded
command_
Note that the abbreviation point should be the same as the one used by
DCL itself. For most DCL commands, the abbreviation point follows the
second character, but for some, the abbreviation point follows the
third or fourth character, to assure a unique abbreviation for each
command.
Use caution when you define system commands in this way. You may make
features of other keyboard monitors unavailable. This may happen if,
for example, you define PRINT as a CCL command. BASIC-PLUS users will
then not be able to use the immediate mode PRINT statement.
Two CCL commands duplicate commands the BASIC-PLUS keyboard monitor
recognizes: HELLO and BYE. The commands are shown here to point out
what BASIC-PLUS does by default. Other keyboard monitors may not
recognize the commands HELLO and BYE if they do not exist as CCL
commands.
Each CCL definition requires one small buffer. The buffer will be
allocated from the FIP small buffer pool. If this buffer pool is
full, however, the monitor allocates the buffer for the CCL definition
from the general buffer pool. See Chapter 12 for more information on
the DEFINE/COMMAND/SYSTEM command.

Set Printer Characteristics
Just as you did for terminals, you need to set the characteristics of
your printers. Minimally, you need to specify the device type of each
printer on your system. See Chapter 11 for more information about the
3-9

The System Start-up Command Files
qualifiers for the SET PRINTER command.

Start Print/Batch Services
The print/Batch Services package (PBS) provides printing services for
line printers or terminals, and batch processing.
The package is
started with a single command.
Chapter 9 contains detailed
descriptions of the DCL commands you can use to manage print/batch
services.

Start OPSER-Based Spooling Package (Optional)
The OPSER-based spooling package like PBS provides print and batch
services.
RSTS/E offers this optional package for compatibility with
previous versions of RSTS/E.
New applications should use PBS.
For
more information on OPSER, see Appendix A of this manual and the
RSTS/E utilities Reference Manual.

Start Error Analysis
Run the ANALYS program immediately after a system crash to recover
valuable diagnostic information.
See Chapter 10 for a description of
the ANALYS program.

Enable Logins
The SET SYSTEM/LOGINS command should appear after the commands that
perform all required and routine operations.
The SET SYSTEM/LOGINS
command activates all swap space added on the system and lets users
log in to the system.
You can then notify users that timesharing has
started.
See Chapter 13 for more information on job management.

Logout the Initial Start-up Job
You should always logout the initial start-up job, since it runs with
ALL privileges.
Failing to do so can create a security risk if the
system console is left unattended.

3-10

Chapter 4
Shutting Down the RSTS/E System

Performing System Shutdown: SHUTUP
The shutdown procedures for the RSTS/E system are critically
important.
If you are not careful in performing system shutdown,
valuable user data can be irretrievably lost.
To understand shutdown
procedures fully, you need to understand other RSTS/E system
procedures.
Chapter 11 describes these concepts such as controlling
logins, removing system files and resident libraries, sending messages
to all logged-in users, and forcing commands to unresponsive
terminals.

Running SHUTUP
You use the SHUTUP program to shut the system down in an orderly
manner.
SHUTUP is in the system library account $ ([1,2]).
SHUTUP
must be installed as a privileged program (protection code <232».
If
not, the system displays the following error message:
?Program must be privileged
To run SHUTUP, you must have SHUTUP privilege.
system displays the following error message:

If you do not, the

?SHUTUP privilege required
Finally, SHUTUP can only be run from the system console (KBO:).
not, the system displays the error message:
?SHUTUP must be run from the system console (KBO:)

4-1

Shutting Down the RSTS/E System
To verify that conditions are suitable for shutting down the RSTS/E
system, use any of the SHOW commands, such as:
o

SHOW JOBS

SHOW DISKS

SHOW BUSY

By executing these SHOW commands, you can determine what jobs are
active on the system and what disks and other peripheral devices are
in use.

SHUTUP Phases
As SHUTUP runs, it proceeds through the following 14 phases:
1.

Set-up dialogue

Warning message

DECnet/E shutdown (if necessary)

Initial job killing

Print/Batch Services (PBS) shutdown (if necessary)

OPSER (optional spooling package) shutdown (if necessary)

EVTLOG shutdown (if necessary)

ERRCPY shutdown (if necessary)

Final job killing (if necessary)

10.

EMT logging shutdown (if necessary)

11.

Unload and remove run-time systems and resident libraries

12.

Swap file removal

13.

Disk dismount

14.

Final shutdown

The following sections describe these phases, the operator
interactions required, and the expected results of the shutdown
operation.
possible results, which you may not expect are also
described.
Several sample runs of SHUTUP show th~ results of shutting
down the system.
4-2

Shutting Down the RSTS/E System
Set~p

Dialogue Phase

The set-up dialogue phase processes all questions relating to the
selection of options in running SHUTUP.
It also checks for the
presence of PBS or OPSER.
In response to questions that appear during 'this phase, you can press
the circumflex (~) key to return to the previous question.
Otherwise,
you should terminate your responses by pressing the RETURN key.
If the Print/Batch Services (PBS) package is present, SHUTUP prints
the following message:
Allow 'PBS' entries to complete (YES/NO) <YES>?
If you type NO, SHUTUP aborts all PBS entries that are in progress.
If you press RETURN or type YES, SHUTUP lets all currently running PBS
entries finish.
If OPSER is present and running, SHUTUP prints the following question:
Use 'OPSER' for utilities shutdown (YES/NO) <YES>?
SHUTUP operates in either of two modes:
o

without OPSE~ In this mode, regardless of whether OPSER is
running, the SHUTUP program treats all jobs in the system
alike during the shutdown procedure (except itself, the
print/Batch Services program, the DECnet/E EVTLOG program,
the EMT logger program, and ERRCPY).

with OPSER: In this mode SHUTUP allows OPSER to shut down its
controlled jobs before SHUTUP continues with the regular
shutdown procedures.

You should be familiar with the OPSER program and how it controls
various utility programs (such as QUMRUN and the OPSER spooling
package programs).
Press RETURN or type YES to have SHUTUP communicate with OPSER during
the shutdown procedures.
If you type NO, SHUTUP prints another
question to confirm your response:
Are you sure you don't want to use 'OPSER'

(YES/NO) <NO>?

Pressing RETURN or typing NO causes the program to repeat the previous
question so you can again decide to use or not to use OPSER during
shut down.
Otherwise, the program ignores OPSER during the shutdown
procedures.

4-3

Shutting Down the RSTS/E System
If you choose to use the OPSER program, SHUTUP prints the following
additional question:
Allow utilities to reach logical end point (YES/NO) <YES>?
If you press RETURN or type YES, the program directs OPSER to tell its
online jobs to shut down their operations at the next logical
breakpoint in their job streams.
For a line printer spooler, for
example, this breakpoint occurs between queued jobs.
If you type NO, the program directs OPSER to tell its online jobs to
abort and stop operations immediate~y.
You should abort in this way
only in an emergency: jobs being processed at the time of shutdown may
be lost unless you have previously halted queuing and spooling
operations and requeued these jobs.
SHUTUP then asks you to specify the number of minutes you want to
elapse before shutdown occurs:
Minutes until system shutdown (0-99) <S>?
This waiting period is called the "warning message phase" and may be
as short as 0 minutes or as long as 99 minutes.
Press RETURN to
select the default value of S minutes.
If you decide to bring the
system down immediately by typing 0, SHUTUP does not ask the two
questions about disabling logins and the DECnet/E network.
When you specify a shutdown period greater than 0 minutes, SHUTUP
allows you to select the amount of time that will elapse before
further logins are disabled:
Minutes until logins are disabled (0-99) <O>?
This question gives you the opportunity to select the amount of time
during which users can continue to log in to the system as shutdown
occurs.
Users can log in to the system (as if the system were not
shutting down) for the number of minutes you specify.
The ability to
allow users this flexibility is useful when you specify a long
shutdown period.
There will be times when you do not want to allow any more users on
the system.
In this case, accept the default response by pressing
RETURN.
Then, users can no longer log in to the system; however,
those already logged in remain unaffected.
Note
SHUTUP disables all logins at least one minute before
the initial job killing phase.

4-4

Shutting Down the RSTS/E System
The last message in the set-up dialogue phase allows you to choose the
number of minutes that will elapse before new network activity is
disabled:
Minutes until new network activity is disabled (0-99) <nn>?
The number of minutes SHUTUP selects for the default value <nn>
depends on your response to the system shutdown question. As in the
previous question, being able to specify when the network will shut
down allows users time to complete network tasks. If you choose to
allow no further logical links to be created, type 0, and then press
RETURN. Those still using the network can continue to work but no new
users are allowed access to the network.

Warning Message phase
At the beginning of the warning message phase, as well as in the
beginning of all other phases that SHUTUP may execute, a message
appears on the system console terminal (KBO:) in the following format:
########

########

SHUTUP prints:
o

The time that it issues the message in the format hh:mm
{AMI PM}

The date that it issues the message in the format dd-mmm-yy

The title of the current phase

SHUTUP prints the following message on the system console terminal
when the time specified for disabling logins has elapsed:
Further LOGINs are now disabled
The RSTS/E shutdown procedure requires that logins are disabled before
the monitor can perform the final shutdown operation. During the
following phases, SHUTUP continuously checks that logins remain
disabled.
If, for any reason, logins are not disabled, SHUTUP
immediately aborts all operations with the following message:
?Logins not disabled
??SHUTUP aborting - please try again later
You should determine the cause of the change, correct the problem, and
run SHUTUP again.

4-5

Shutting Down the RSTS/E System
If your system has DECnet/E support, the SHUTUP program prints the
following message when the time specified for disabling network
activity expires:
Further network activity is now disabled
The message tells you that no new logical links can be formed.
Those
links that are already active, however, can remain active until the
time to network shutdown has elapsed.
Before the network shuts down,
the DECnet/E program EVTLOG may print messages indicating the status
of the network.
The initial EVTLOG message marks the beginning of the
network shutdown phase.
The second message, issued later in the
shutdown process, indicates that the network has been shut off
completely.
See the section "SHUTUP Example: DECnet/E Shutdown" for
an example of these messages.
During the warning message phase, the program issues warning messages
indicating the system is shutting down.
These messages appear on most
keyboards in the system, including pseudo keyboards.
The following
keyboards are the exceptions:
OSC - The OPSER operator services console
KBO: - The system console terminal
The program issues warnings after an appropriate waiting period,
defined by the following formula:
waiting time

= (total time left)/5 + I

minutes

For an initial waiting period of 60 minutes, warning messages appear
at 60, 47, 37, 28, 22, 17, 13, 10, 7, 5, 3, 2, and 1 minute before
shutdown begins.
SHUTUP prints the following message on all system
terminals at each warning time:
hh:mm{~~}dd-mmm-yy

System going down in n minutes, please finish up

At the same time, the following message appears on the system console
terminal (KBO:):
n minute message sent
When the time to shutdown has expired or if the initial waiting period
is specified as 0, the final warning message appears:
hh:mm{~~}dd-mmm-yy

**** FINAL WARNING!!!!! System shutting down ****

At this point, the program enters the next phase.
SHUTUP prints the
time and date for both the SYSTEM GOING ,DOWN and the FINAL WARNING
messages.

4-6

Shutting Down the RSTS/E System
DECnet/E Shutdown phase (When Necessary)
The time to DECnet/E shutdown begins as soon as you enter the number
of minutes that should elapse before new network activity is disabled:
Minutes until new network activity is disabled (0-99) <nn>?
The number of minutes, shown in angle brackets <nn>, is the default
response.
It assumes the same value you typed in response to the
SHUTUP question:
Minutes until system shutdown (0-99) <nn>?
Rather than accept the default response (that is, to the network
activity question) and have new network activity disabled at the same
time the system shuts down, it is often better to disable new network
activity before shutdown occurs.
Entering a value less than the
number of minutes to shutdown establishes a period before shutdown in
which no new links can be created; it also allows time for those
already active to complete network tasks.
If you want new network
activity disabled immediately, type 0 and press RETURN. When the time
to disable network activity has elapsed (0 to 99 minutes), SHUTUP
prints a message to indicate no further network activity is allowed:
Further network activity disabled
SHUTUP disables new network activity by executing the equivalent of
the Network Control Program (NCP) command SET EXECUTOR STATE SHUT.
This prevents the creation of new logical links but does not affect
existing logical links.
In reality, a user can create new network
links until the network activity is disabled. After that period ends,
no new links can be created, but users already on the network can
continue working until the system shuts down.
The network remains up
until there are no links active or until the system shuts down.
As soon as all logical links have been disconnected by their users,
the network state changes automatically to OFF.
The state is
immediately set to OFF if no links existed at the time SHUTUP disabled
new network activity.
If the DECnet/E event logging program EVTLOG is
on and has event 2.0 enabled, it logs both the transition to SHUT and
the one to OFF.
(See the DECnet/E System Manager's Guide for a
description of EVTLOG.)
SHUTUP never sends special messages indicating the approach of a
DECnet/E shutdown. Users can tell that SHUTUP is shutting down the
system only from SHUTUP messages to all terminals and from the fact
that the network is in the SHUT instead of the ON state.
If the network has still not completely shut down at the end of the
warning message phase (because active links remain), SHUTUP explicitly
sets the network to OFF.
This action disconnects all remaining

4-7

Shutting Down the RSTS/E System
logical links.
SHUTUP then waits 15 seconds to allow affected jobs to
complete network tasks and exit, before it enters the job killing
phase.
If you decide not to shut the system down (thus, not shut off the
network) after you have started SHUTUP, entering a CTRL/C to stop the
execution of SHUTUP may reactivate the network. A CTRL/C causes
SHUTUP to print a message telling you the state in which the network
was left.
If the network is not in the state you want, you must use
NCP to place the network and the event logger (EVTLOG) in the desired
state.
See the DECnet/E System Manager's Guide for a description of
NCP.

Initial Job Killing Phase
In the initial job killing phase, SHUTUP begins to clear the system of
currently active jobs.
If SHUTUP finds there is only one job (itself)
running on the system, it skips this phase and then continues the
shutdown procedure at the unload and remove run-time systems and
resident libraries phase.
If SHUTUP is using PBS in the next phase, during this phase the
program ignores all jobs currently- associated with PBS (as indicated
by entries in PBS's on-line job table).
The program also ignores any
job whose primary keyboard is a pseudo keyboard.
Such a job is
probably being controlled by one of the batch servers.
SHUTUP further divides all other jobs active in the system into two
classes: attached and detached.
This classification depends on
whether they have an attached primary keyboard (KB:).
For all
attached jobs, SHUTUP forces the following text string to the keyboard
input buffer:
AC

$LOGOUT/BRIEF

For all detached jobs, SHUTUP issues the Kill job SYS call (SYS 8) to
remove the job.
SHUTUP makes two passes through the current active job table during
this phase.
In the first pass, the program terminates all active jobs
not being ignored. At the end of the first pass, it establishes the
number of attached jobs that were found and forced to logout.
SHUTUP
then waits for a specified period to allow the LOGOUT program to
complete operations on each of the attached jobs.
After the waiting period (if any) expires, the program makes a second
pass through the active job table.
During this pass, all jobs not
being ignored are removed with the kill job SYS call. At the end of

4-8

Shutting Down the RSTS/E System
the pass, the program checks the table.
If any jobs that should have
been killed were not, SHUTUP aborts operations with the following
error message:
?SHUTUP failed in initial job killing phase
??SHUTUP aborting - please try again later
You should determine why SHUTUP could not kill all jobs, correct the
problem, and run SHUTUP again.
If SHUTUP successfully removes all jobs during the phase, or if at any
time during either pass the number of active jobs becomes one (SHUTUP
only), the next phase begins.

Print/Batch Shutdown Phase (When Necessary)
The program skips the Print/Batch Services (PBS) shutdown phase if PBS
is not running on the system.
If PBS is not running, SHUTUP continues
with the next phase; no message is displayed.
If PBS is running, SHUTUP sends a message to QMAN telling QMAN to
shutdown PBS.
QMAN acknowledges the shutdown command by sending back
a confirmation message.
If SHUTUP does not receive the confirmation
message within two minutes after the offline request was sent, SHUTUP
aborts the shutdown operation and displays the following:
?No response from Print/Batch Services after 2 minutes
otherwise, SHUTUP displays the number of entries currently processing
in PBS in the following format:
print/Batch Services shutting down
Print/Batch Services shutting down

# jobs are completing.
# jobs are being terminated.

Then SHUTUP waits for PBSMGR to shutdown PBS.
The maximum wait period
is one hour if jobs are allowed to complete and one minute if jobs are
aborted.
If shutdown occurs in the specified time, SHUTUP displays
the following message and goes to the next phase:
Print/Batch Services shutdown complete at hh:mm am/pm
otherwise, SHUTUP aborts and displays the following error message:
?Print/Batch Services shutdown taking too long
??SHUTUP aborting - please try again later

4-9

Shutting Down the RSTS/E System
OPSER Shutdown phase (When Necessary)
The program skips the OPSER shutdown phase if:
o

OPSER is not running on the system

You elect not to use OPSER during the shutdown procedures

If you choose to use OPSER, SHUTUP immediately detaches from the
system console terminal (KBO:) to enable OPSER to reattach to the
terminal for use during OPSER's shutdown procedures. As the detach
occurs, the following messages appear:
DETACHING ...
'OPSER' ATTACHING
#
SHUTUP sends a message to OPSER directing it to begin its shutdown
procedures by selecting the appropriate mode of OPSER shutdown.
SHUTUP then waits 60 seconds to see if OPSER receives the message
and/or is functioning properly.
If OPSER does not respond properly
within that time, SHUTUP attempts to reattach to the system console
terminal (KBO:).
If the operation is successful, the following
message appears:
?OPSER not active
??SHUTUP aborting - please try again later
If the terminal is attached or assigned, SHUTUP waits for one second
and tries again.
You should take whatever steps are necessary to free
the system console terminal (KBO:) for use so SHUTUP can complete its
activities.
If OPSER is shutting down its online programs in the immediate mode,
it sends each program the appropriate message to stop operations.
OPSER pauses to make sure all programs have completed their
assignments.
OPSER then closes its files, prints the following
message on the system console (KBO:), and stops execution:
'OPSER' TERMINATING
SHUTUP allows OPSER 120 seconds to complete its shutdown in the
immediate shutdown mode.
If unsuccessful, SHUTUP aborts its
operations, signaling the failure as follows:
?OPSER shutdown taking too long
??SHUTUP aborting - please try again later
If OPSER is shutting down in the logical end mode, it proceeds to
shutdown successive levels in its online job table. Appropriate
system console messages signal the end of each job (see "SHUTUP
Operation Examples"). When all online OPSER jobs are gone, OPSER
4-10

Shutting Down the RSTS/E System
closes its files and kills itself, freeing the system console for
SHUTUP use again.
OPSER tells you when it finishes processing with
the message:
,'OPSER' TERMINATING
SHUTUP allows 60 minutes in the logical end mode for OPSER to complete
operations.
If the procedure is not successful, SHUTUP aborts
operations with the error message described previously.
Otherwise,
the shutdown of OPSER-related jobs and activities is complete and the
program enters the next phase.

EVTLOG Shutdown Phase (When Necessary)
The SHUTUP program enters the EVTLOG shutdown phase if it finds EVTLOG
in the message/receiver table.
(DECnet/E does not need to be active
for SHUTUP to perform this phase.) SHUTUP sends EVTLOG a special error
message that causes EVTLOG to log the shutdown occurrence on the
system console, perform various other shutdown operations, and kill
itself.
When SHUTUP detects that EVTLOG has completed its shutdown activities
and is no longer present, SHUTUP proceeds to the next phase.
SHUTUP
allows 60 seconds for EVTLOG to complete its tasks, and if failure
occurs, SHUTUP aborts operations with the following error message:
?EVTLOG failed to shutdown
??SHUTUP aborting - please try again later
See the DECnet/E System Manager's Guide for information about the
EVTLOG program.

ERRCPY Shutdown phase (When Necessary)
The program enters the ERRCPY shutdown phase if the system error
logging utility ERRCPY is present.
SHUTUP sends ERRCPY a special
message which causes ERRCPY to log the shutdown occurrence in the
system error log, close the file, and kill itself.
When SHUTUP detects ,that ERRCPY has completed its shutdown and is no
longer present, SHUTUP proceeds to the next phase.
SHUTUP allows 60
seconds for ERRCPY to complete its tasks.
If failure occurs, SHUTUP
aborts operations with the following error message:
?ERRCPY failed to shutdown
??SHUTUP aborting - please try again later

4-11

Shutting Down the RSTS/E System
Final Job Killing Phase (When Necessary)
If SHUTUP reaches this point, and is not the only job left running in
the system apart from the EMT logger, SHUTUP makes one last attempt at
killing all other remaining jobs.
If SHUTUP is successful, it enters
the next phase.
If not successful, SHUTUP aborts operations with the
following error message:
?SHUTUP failed in final job killing phase
??SHUTUP aborting - please try again later

EMT Logging Shutdown Phase (When Necessary)
The program enters the EMT logging shutdown phase if the EMT logging
utility is present.
(See Chapter 14 for a description of the EMT
logger.) SHUTUP sends a shutdown message to the EMT logger, informing
the EMT logger to stop.
If the EMT logger does not shut down in 60
seconds, SHUTUP aborts the EMT logger with the following warning
message:
%EMT logger failed to shutdown - killing EMT logger job = n
In this message, n is the job number of the EMT logger.

Remove Run-Time Systems and Resident Libraries Phase
During the remove run-time system and resident libraries phase, the
program removes all run-time systems and resident libraries from the
system tables.
SHUTUP does not attempt to remove the primary run-time
system.

Swap File Removal Phase
During the swap file removal phase, SHUTUP makes sure all installed
swap files are removed.

Disk Dismount Phase
During the dismount phase, the program dismounts all mounted disks,
both private and public, from the system.
The system disk always
remains mounted.

4-12

Shutting Down the RSTS/E System
If you have opened a file using the DeL commands OPEN or OPEN/LOG, or
if you are executing SHUTUP from an indirect command file, and the
file resides on a disk other than the system disk, an unexpected error
occurs when SHUTUP tries to dismount the affected disk.
SHUTUP aborts
and you must close the file before retrying the shutdown.

Final Shutdown Phase
SHUTUP enters the final shutdown phase to output the last status
message, clears the system console terminal (KBO:) buffers, and
executes the special System shutdown SYS call (SYS -16).
The monitor
transfers control to the system initialization code (INIT.SYS) and
bootstraps the system disk.
The monitor loads the initialization code
and INIT prints the start Timesharing <Yes>? prompt.

SHUTUP Operation Examples
Each of the following sections contains an example of a SHUTUP
operation.
These examples and the description of the SHUTUP program
should help you to shut down your system correctly and in orderly
fashion.

SHUTUP Example: Large RSTS/E System
The system in the following example is being shut down in a leisurely
fashion.
This gives system and network users enough time to complete
their tasks.
SHUTUP allows users to log in to the system during the
entire shutdown phase; logins are disabled at system shutdown, after 5
m1nutes. Those using the network can log in until the 5-minute mark,
after that time the system does not allow network access by users.
However, those on the network before new network activity is disabled
can continue to work until the system shuts down completely.
$ run shutup
SHUTUP V9.0 RSTS V9.0 EDERE

10:11 AM 28-May-85

########

Set-up Dialogue Phase

########

Type ,A, to any query to backup one question
Allow Print/Batch Services jobs to complete <YES>? yes
Use OPSER for utilities shutdown <YES>? yes
Allow OPSER utilities to reach logical end point <YES>? yes
Minutes until system shutdown (0-99) <5>? 15
(continued on next page)

4-13

Shutting Down the RSTS/E System
Minutes until logins are disabled (0-99) <O>? 5
Minutes until new network activity is disabled (0-99) <5>?

10:12 AM 28-May-85 ########
Warning Message Phase
15 minute warning message sent
11 minute warning message sent
Further LOGINs are not disabled
Further network activity is now disabled
8 minute warning message sent
6 minute warning message sent
4 minute warning message sent
3 minute warning message sent
2 minute warning message sent
1 minute warning message sent

########

10:27 AM 28-May-85

########

DECNET Shutdown phase

########

10:27 AM 28-May-85

########

Initial Job Killing Phase

########

10:27 AM 28-May-85 ########
Print/Batch Shutdown phase
Print/Batch Services shutdown complete at 10:27 AM

########

10:27 AM 28-May-85
Detaching ...

########

OPSER Shutdown Phase

########

'OPSER' ATTACHING
#
JOB #6 'BAISPL' TAKEN OFFLINE
#
JOB #7 'BA2SPL' TAKEN OFFLINE
#
JOB #5 'BAOSPL' TAKEN OFFLINE
#
JOB #4 'LPOSPL' TAKEN OFFLINE
#
JOB #3 , QUEMAN' TAKEN OFFLINE
#'OPSER' TERMINATING
Re-attaching ...
10:29 AM 28-May-85

########

EVTLOG Shutdown Phase

########

10:29 AM 28-May-85

########

ERRCPY Shutdown Phase

########

10:29 AM 28-May-85

########

Remove RTS/RES LIB phase

########

10:29 AM 28-May-85

########

SWAP File Removal phase

########

10:29 AM 28-May-85

########

Disk DISMOUNT Phase

########

10:29 AM 28-May-85

########

Final Shutdown Phase
########
(continued on next page)
4-14

Shutting Down the RSTS/E System
Please wait for system to re-boot itself
RSTS V9.0 EDERE (DRl) INIT V9.0
28-May-85 10:30 AM
start timesharing <Yes>?

SHUTUP Example: Small RSTS/E System
The following example shows a system shutdown when OPSER is not
present.
Except for the absence of the first OPSER-related question,
the example applies when OPSER is present but not used during
shutdown.
$ run shutup
SHUTUP V9.0 RSTS V9.0 EDERE

12:24 PM 22-May-85

########

Set-up Dialogue phase

########

Type ,A, to any query to backup one question
Allow Print/Batch Services jobs to complete <YES>? yes
Minutes until system shutdown (0-99) <5>?
5
Minutes until logins are disabled (0-99) <O>? 1
Warning Message phase

########

Initial Job Killing phase

########

12:25 PM 22-May-85 ########
Print/Batch Shutdown Phase
print/Batch Services shutdown complete at 12:25 PM

########

12:24 PM 22-May-85 ########
5 minute warning message sent
Further LOGINs are now disabled
3 minute warning message sent
2 minute warning message sent
1 minute warning message sent
12:24 PM 22-May-85

########

12:25 PM 22-May-85

########

EVTLOG Shutdown phase

########

12:25 PM 22-May-85

########

ERRCPY Shutdown phase

########

12:25 PM 22-May-85

########

Remove RTS/RES LIB phase

########

12:25 PM 22-May-85

########

SWAP File Removal Phase

########

12:25 PM 22-May-85

########

########
Disk DISMOUNT Phase
(continued on next page)

4-15

Shutting Down the RSTS/E System
12:25 PM 22-May-85

########

Final Shutdown Phase

########

Please wait for system to re-boot itself
RSTS V9.0 ED ERE (DR1) INIT V9.0
22-May-85 - 12:24 PM
start timesharing <Yes>?

SHUTUP Example: DECnet/E Shutdown
This example shows SHUTUP when OPSER is used to shut down a spooling
system of five spoolers.
It also illustrates how the network shuts
down when a system includes DECnet/E support and event logging by the
DECnet/E EVTLOG program has been enabled.

$ run shutup
SHUTUP V9.0 RSTS V9.0 ED ERE
12:39 PM 22-May-85
Type

,~,

########

set-up Dialogue Phase

########

to any query to backup one question

Allow Print/Batch Services jobs to complete <YES>? yes
Use 'OPSER' for utilities shutdown <YES>? yes
Allow OPSER utilities to reach logical end point <YES>? yes
Minutes until system shutdown (0-99) <5>? 5
Minutes until logins are disabled (0-99) <O>? 0
Minutes until new network activity is disabled (0-99) <5>? 2
12:40 PM 22-May-85 ########
Further LOGINs are now disabled
5 minute warning message sent

Warning Message Phase

########

Further network activity is now disabled
3 minute warning message sent
Event type 2.0, Local node state change
Occurred 22-May-85 12:42:05.0 on node 135 (OTHG)
Reason for state change: Operator command
Old node state = On
New node state = Off
2 minute warning message sent
1 minute warning message sent
12:45 PM 22-May-85

########

DECNET Shutdown Phase
########
(continued on next page)
4-16

Shutting Down the RSTS/E System
Initial Job Killing Phase

########

12:45 PM 22-May-85 ########
print/Batch Shutdown phase
Print/Batch Services shutdown complete at 12:45 PM

########

12:45 PM 22-May-85

12:45 PM 22-May-85
Detaching ...

########

OPSER Shutdown Phase

########

'OPSER' ATTACHING
#
JOB #6 'BA1SPL' TAKEN OFFLINE
#
JOB #7 'BA2SPL' TAKEN OFFLINE
#
JOB #5 'BAOSPL' TAKEN OFFLINE
#
MESSAGE
949 : 22-May-85 12:45 PM JOB:3 DET QUMRUN[1,2]
BA1SPL (6) REQUESTED OFF-LINE -- TAKEN OFF-LINE
#
MESSAGE
950 : 22-May-85 12:45 PM JOB:3 DET QUMRUN[1,2]
BA2SPL (7) REQUESTED OFF-LINE -- TAKEN OFF-LINE
#
MESSAGE
951 : 22-May-85 12:45 PM JOB:3 DET QUMRUN[1,2]
BAOSPL (5) REQUESTED OFF-LINE -- TAKEN OFF-LINE
#
JOB #4 'LPOSPL' TAKEN OFFLINE
#
MESSAGE
952 : 22-May-85 12:45 PM JOB:3 DET QUMRUN[1,2]
LPOSPL (4) REQUESTED OFF-LINE -- TAKEN OFF-LINE
#
JOB #3 , QUEMAN' TAKEN OFFLINE
#'OPSER' TERMINATING
Re-attaching ...
12:45 PM 22-May-85

########

EVTLOG Shutdown phase

########

Shutting down EVTLOG by operator request.
12:45 PM 22-May-85

########

ERRCPY Shutdown phase

########

12:45 PM 22-May-85

########

Final Job Killing Phase

########

12:45 PM 22-May-85

########

Remove RTS/RES LIB Phase

########

12:45 PM 22-May-85

########

SWAP File Removal Phase

########

12:45 PM 22-May-85

########

Disk DISMOUNT phase

########

12:45 PM 22-May-85

########

########
Final Shutdown Phase
(continued on next page)

4-17

Shutting Down the RSTS/E System
Please wait for system to re-boot itself
RSTS V9.0 EDERE (DR1) INIT V9.0
22-May-85 - 12:45 PM
start timesharing <Yes>?

Notes on SHUTUP Operation
You can help the users on your system by establishing administrative
procedures that govern the hours the system is in operation.
If you
have a fixed shutdown schedule, users can plan their work load and
complete tasks in the allotted hours of timesharing.
You can keep them informed by placing messages in the system
NOTICE. TXT file.
If the user selects to display it, the system prints
the contents of NOTICE.TXT each time a user logs in.
This is a
convenient way to make sure all users know about important system
operations.

Chapter 5
Managing Quotas

This chapter describes the quotas that limit the use of various system
resources.
You can assign quotas to a user when you create an
account.
RSTS/E quotas fall into three categories:
o

Disk quotas

Job quotas

Send/Receive quotas

The remainder of this chapter describes these quotas in detail.
Chapter 7 for information on assigning or changing an account's
quotas.

See

Disk Quotas
You can limit the amount of space available to individual users on
public or private disks by creating and maintaining quotas on those
disks.
Quotas are maintained and enforced on a per-disk basis, except
for the public structure where it is maintained across the structure.
You identify PPNs and assign quotas to them.
The system automatically
maintains usage counts during normal file.activities.
Each account that exists on a Level 1.2 disk, except for the [0,1]
account, has a disk quota attribute block associated with it. The
quota blocks have the following information:
o

Usage
files

Quotas
Maximum number of blocks on the disk that your
files can take up before the system issues an error message

Actual number of blocks on the disk taken up by your

5-1

Managing Quotas
Note
For level 1.2 disks, RSTS/E uses 24 bits .to store the
disk quotas.
Thus, quotas can be as large as the
size of the largest disk supported by RSTS/E.

Disk Quota Operations
For pre-V9.0 disk structures, RSTS/E could only enforce disk quota
limits at the time a user logged out.
Thus, as a system manager, you
could limit the amount of permanent disk space a user could have, but
you could not limit the amount of temporary disk space.
Now RSTS/E maintains, on level 1.2 disks only, two types of disk
related quotas: a logged-in quota and a logged-out quota.
If at least
one user is logged in to the file's account, the system automatically
checks the usage count against the logged-in quota as users create,
delete, and extend files.
If no one is logged in to the file's
account, then RSTS/E checks the usage count against the logged-out
quota.
The system also enforces the logged-out quota when a user logs
out.
If extending the file causes the total disk usage to exceed the quota,
RSTS/E rejects the operation and returns a ?Quota exceeded error
message. When checking for a possible quota violation, RSTS/E takes
into consideration the total write request.
So, a write request that
extends a file by multiple disk blocks is never only partially
completed.
To perform the quota checks, the monitor keeps a record of the number
of blocks that it allocates to each account on each disk.
For public
disks, this record is kept on a per disk basis, but, when quota checks
are made, the counts are added up across the public structure.
The
monitor keeps the usage information in memory and writes it back to
the disk when appropriate.
If the system crashes (leaving old
information on a disk), the disk rebuild operation (CLEAN) recomputes
the usage and writes the correct data on the disk.

Logged-In Disk Quotas
Logged-in disk quotas are the number of disk blocks that the system
lets a user allocate while logged in.
The number of blocks in use is
the total number of blocks allocated.
The allocation of any file is
its actual size in blocks, rounded up to the nearest full cluster.

5-2

Managing Quotas
A

The allowable values are 0 to 16,777,214 (2 24-2), and UNLIMITED.
Zero means that no disk storage is allowed. UNLIMITED is a special
value that means the monitor does not enforce the logged-in quota.
Logged-in quotas do not apply on:
o

Level 0 or Level 1.1 disk structures

Disks mounted using MOUNT/NOQUOTA (although the usage is
still kept up to date)

Disks mounted using MOUNT/NOWRITE (because no file extends
can take place on such a disk)

Logged-Out Disk Quotas
Logged-out disk quotas are the number of disk blocks that the system
lets a user retain at log-out time.
The logged-out quota is also
checked when a user tries to create or extend a file in a logged-out
account.
The allocation of any file is its actual size in blocks, rounded up to
the nearest full cluster.
The number of blocks in use by any user is
the total number of blocks allocated for all of the user's files.
The allowable values are 0 to 16,777,214 (2A24-2), or UNLIMITED.
Zero
means that no disk storage is allowed to remain allocated at logout
time.
UNLIMITED is a special value that means the monitor does not
enforce the logged-out quota.
When a job logs out, the monitor checks the logged-out disk quota of
each disk against the usage of that disk.
For the public structure,
the system disk quota is checked against the total usage on the public
structure.
If the quota is exceeded (and no other interactive jobs
are logged in under the same account) then the monitor rejects the
logout request.
Note
For level 0 and level 1.1 disk structures, the
logged-out quotas remain the same as pre-V9.0.
The
allowable values are 0 to 65,535, where zero means
UNLIMITED.

5-3

Managing Quotas
Job Quotas
For pre-V9.0 disk structures, there was no restriction on the number
of attached jobs that a user was allowed to run. Thus, a user who had
access to several terminals could gain control of a large number of
job slots. In V9.0, each account has a job quota.
The job quota specifies the total number of jobs (attached or
detached) that each account can have active at any time. If the user
attempts to exceed this quota, the system rejects the request and
returns the ?Quota exceeded error message. If the user attempts to
log in when the quota is reached, the system rejects the log-in
request (see the section "Job Quotas and Login").
The default job quota is UNLIMITED.

Detached-Job Quota
For pre-V9.0 disk structures, you could establish a system-wide quota
to control the number of jobs allowed to run detached under
nonprivileged accounts. This limit was set up as the ratio of
detached to attached jobs, which resulted in some problems when
server-type jobs are required to run detached under accounts that may
not have any attached jobs at all.
In V9.0, the detached job quota is an account attribute. It indicates
the actual number of jobs that are allowed to run detached under each
account. If detaching a job causes this quota to be exceeded, then
the system rejects the request and displays the following message:
?Quota exceeded
The quota check applies even if the user issuing the request is
running under some other account. The detached job quota does not
affect the automatic detaching operation that takes place when carrier
is lost on a dial-up line controlling a job. In that case the job is
unconditionally detached, but the quota is enforced ,when the user
attempts to log back on (see the section "Job Quotas and Login").
For compatibility with pre-V9.0 disk structures, the detached job
quota defaults to zero when you create an account.

5-4

Managing Quotas
Job Quotas and Login
When a user attempts to log in, the system checks the current list of
jobs under the account being logged in to against the quotas for that
account.
If either the detached job quota is exceeded or the job
quota would be exceeded, the system rejects the log-in request.
The
system returns the list of currently detached jobs in the usual
manner.
If a user attempts to log in to some account and the job quota has
been reached, the result depends on whether there currently are jobs
running detached under that account.
If there are none, the system
rejects in the log-in request.
If there are detached jobs, the system
lets the user attach to one of them.
If a user attempts to log in to some account and the detached job
quota for that account has been exceeded, the system rejects the
request but the user can attach to one of the detached jobs. Thus,
the monitor ensures that one user cannot create an unlimited number of
detached jobs.

Send/Receive Quotas
You can also limit the number of receiver ID blocks (RIBs) and the
number of messages that a job can have at any time.

RIB Quota
Specifies the maximum number of RIBs that a job running under an
account can set up for itself as a message receiver.
The allowable
range is 0 to 256 or UNLIMITED. UNLIMITED is a special keyword that
means no RIB quota is to be enforced.

Message Quota
Specifies the maximum total message quota that a job running under an
account can request when declaring itself as a receiver.
This maximum
total must be shared by however many RIBs (local and network) the job
wants to set up.
The allowable range is 0 to 65,535 or UNLIMITED.
UNLIMITED is a special keyword that means no message quota is to be
enforced.

5-5

Chapter 6
Managing Privileges

This chapter describes the privileges that you can assign to a user
when creating an account. Privileges restrict the performance of
certain system activities to certain users. These restrictions
protect the integrity of the operating system's performance and thus
the integrity of service provided to users. You should grant
privileges to each user on the basis of two factors:
o

Whether the user has a legitimate need for the privilege

Whether the user has the skill and experience to use the
privilege without disrupting the system

There are two types of privileges: RSTS/E-defined and user-defined.

RSTS/E-Defined Privileges
RSTS/E-defined privileges fall into several categories. The
categories are based on the level of impact the user has on the
system:
o

User -- Minimum privileges to use the system effectively

Group

Potential to affect users inside the same group

World

Potential to affect users outside the same group

System -- Potential to affect normal system operation

File -- Potential to read or write file data

All -- Potential to control the system

Users can use the DeL command SET JOB/PRIVILEGE to enable and disable
privileges for which they are authorized. Table 6-1 lists the
privileges by category and gives a brief definition.
6-1

Managing Privileges
The sections that follow Table 6-1 describe each privilege in
alphabetical order.
For a function-by-function description of
privilege requirements, see the RSTS/E Programming Manual, the RSTS/E
System Directives Manual, or the RSTS/E System User's Guide.
Table 6-1:

RSTS/E Privileges

+- - - - - - - - - -+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I category I Privilege I
Activity Permitted
I
+- - - - - - - - - -+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

User

Group

World

Files

none

Most normal activity except those listed
below

SETPAS

Change own password

GACNT

Management of all accounts in group

GREAD

Read access to all files in group

GWRITE

write access to all files in group

EXQTA

Exceed quotas

RDMEM

Read physical memory

WACNT

Management of all accounts

WREAD

Read access to all files

WWRITE

Write access to all files

DATES

Change file last access date

DEVICE

Access restricted devices

GREAD

Read access to all files in group

GWRITE

Write access to all files in group

INSTAL

Add/remove/list system files,
systems, libraries

WREAD

Read access to all files

WWRITE

write access to all files

6-2

run-time

Managing
Table 6-1:

priv~!eges

RSTS/E Privileges (Cont.)

+- - - - - - - - - -+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I category I Privilege I
Activity Permitted
I

+- - - - - - - - - -+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
System

All

DATES

Change system clock

HWCTL
JOBCTL
SWCTL

Perform system hardware control functions
Perform job control functions
Control logins and networking

HWCFG
SWCFG

Set device characteristics
Set system parameters

INSTAL

Add/remove/list eeL commands

MOUNT

Mount and dismount devices

PBSCTL

Control print/Batch services

SEND

Send to a restricted receiver, BROADCAST
messages

. SHUTUP

Shut down the system

TUNE

Alter priority, run burst, and swapping
mode

RDNFS

Perform read-only non-file-structured I/O

SYSIO

write files in [0,*]

SYSMOD

Modify the system

(with WWRITE)

WRTNFS
Perform read/write non-file-structured I/O
+- - - - - - - - - -+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

DATES Privilege
The DATES privilege lets you change the system date or time.
You also
need this privilege to change a file's date of last access or
modification.

DEVICE Privilege
The DEVICE privilege lets you allocate, read, or write data on a
restricted device.
6-3

Managing Privileges
EXQTA Privilege
The exceed quota privilege (EXQTA) lets the space taken by the user's
files on a given volume exceed any quota set for the user (as
determined by the PPN) on that volume. However, this privilege does
not let users exceed their logged-out quota when logging off the
system.
This privilege also lets users specify a priority,'page limit, CPU
limit, or time limit value with a PRINT or SUBMIT command that exceeds
the maximum value for the specified queue.
The primary use of EXQTA is by privileged programs that need to
perform certain operations regardless of user quotas.
Normally, you
would not assign EXQTA to users.
Instead, you should set the user's
quotas to get the effect you want.

GACNT Privilege
The group accounting privilege (GACNT) lets a user perform account
management functions, such as create/delete account and change
passwords/quotas for all accounts with the same project number (group)
as the user.
GACNT also lets a user create batch jobs in any account
in the user's group.

GREAD Privilege
The group read privilege (GREAD) allows the user's job read and
execute access to any file whose project number is the same as the
user's.

GWRITE Privilege
The group write privilege (GWRITE) gives the user's job create,
rename, and write access to all files that have the same project
number as the user's.

HWCFG Privilege
The hardware configuration privilege (HWCFG) lets you set terminal
characteristics for any terminal, declare a device as restricted, and
set line printer parameters.

6-4

Managing privileges
HWCTL Privilege
The hardware control privilege (HWCTL) lets you perform system control
functions, for example setting terminal characteristics, seizing
control of a device, or hanging up a modem line.

INSTAL Privilege
The install privilege (INSTAL) lets you add, remove, or list system
files.
You can also add or remove run-time systems, resident
libraries, system logical names, or system commands (CCLs).

JOBCTL privilege
The job control privilege (JOBCTL) lets you read the status of any
other job, kill a job, or remove the receiver ID block (RIB) of
another job.
You can also create a job even if logins are disabled.

MOUNT Privilege
The MOUNT privilege lets you mount shared disks, or use certain
restricted MOUNT command qualifiers.

PBSCTL privilege
The PBSCTL privilege lets you control the print/Batch Services.
For
example, you can start or stop servers, or change printer forms.

RDMEM Privilege
The RDMEM privilege lets you read memory (PEEK) and perform read-only
mapping of physical memory by executing the .PLAS system directive.

RDNFS Privilege
The RDNFS privilege lets the user's job perform read-only
non-file-structured I/O operations.

6-5

Managing Privileges
Note
This privilege lets a job access data anywhere on the
selected disk without the benefit of any file
structure. Grant it only to users who need it.
If
this privilege is given to unqualified users who do
not need it, the operating system and service to
other users can be disrupted.
Such disruptions can
include the exposure of confidential information to
unauthorized persons.

SEND Privilege
The SEND privilege lets you send a message to a restricted receiver.
You also need this privilege to BROADCAST a message to a terminal.

SETPAS Privilege
The SETPAS privilege lets users change their own password.
privilege enables the SET PASSWORD command.

This

SHUTUP privilege
The SHUTUP privilege lets you run the SHUTUP program to shut down the
system.

SWCFG Privilege
The SWCFG privilege lets you perform system configuration functions
such as:
o

Setting magnetic tape label defaults

Setting date/time presentation formats

Initializing queues and servers

Managing DECnet

6-6

Managing Privileges
SWCTL Privilege
The software control privilege (SWCTL) lets you enable or disable
logins.
You also need this privilege to perform operational network
management functions (for example, turning the network or individual
circuits ON and OFF).

SYSIO Privilege
The SYSIO privilege lets the user's job:
o

Create, modify,

rename, or delete files in [0,*]

Issue commands that write into files in [0,*] such as the
DUMP/SYSTEM command

Declare a network receiver that accepts inbound network
connection requests (a network server program)

Declare a receiver with a name that does not end with your
job number

Set the privilege bit in the protection code of a file

SYSMOD Privilege
The SYSMOD privilege lets you perform functions that could modify the
system:
o

Write memory with POKE

Map physical memory read/write

Map the I/O page

Perform non-file-structured reads and writes of a mounted
disk

6-7

Managing Privileges
Note
This privilege lets a job access data anywhere on the
selected disk without the benefit of any file
structure. Grant it only to users who need it.
If
this privilege is given to unqualified users who do
not need it, the operating system and service to
other users can be disrupted.
Such disruptions can
include the destruction of information on the system
device, the destruction of user data, and the
exposure of confidential information to unauthorized
persons.

TUNE Privilege
The TUNE privilege lets you:
o

Enable or disable disk caching

Enable or disable file caching

Lock your job in memory

Set the maximum size any job can occupy in physical memory
(SWAP MAX)

Set the maximum time any job can run when compute bound (run
burst)

Set the priority of any job

Change a batch server's priority and run burst

You can increase or decrease the priority of a job by executing the
UU.PRI system directive or the DCL command SET JOB/PRIORITY. With the
same privilege, a job can spawn another job with a priority other than
its own.
You can create such a job by using an optional argument to
the system directive UU.JOB.
The TUNE privilege also lets you control whether a job can be swapped
out of memory by executing the .SET system directive with the JFLOCK
bit set.
Because of their significant effect on system performance, the BACKUP
and RESTORE commands also require TUNE privilege.

6-8

Managing Privileges
Note
Do not grant the TUNE privilege widely; if
unqualified users have unrestricted ability to set
job priorities, the fair and orderly scheduling of
jobs for execution can be disrupted.
Grant the TUNE privilege only to users who need to
lock a job in memory for performance reasons.
(Typically, this will be a real-time application.) If
unqualified users have the unrestricted ability to
lock jobs in memory, physical memory may be held
unnecessarily, thus degrading system performance.

WACNT Privilege
The world accounting privilege (WACNT) lets you perform account
management functions, such as create/delete account and change
password/quotas, for all accounts. Also, to spawn jobs or run batch
jobs in any account on the system.
To affect or to examine other accounts inside its own project number,
a job needs only the GACNT privilege. But to affect or examine
accounts outside its own project number, a job needs the WACNT
privilege.

WREAD Privilege
The world read privilege (WREAD) gives you read and execute access to
any file.

WRTNFS Privilege
The WRTNFS privilege lets you perform read/write non-file-structured
I/O operations.
Note
This privilege lets a job access data anywhere on the
selected disk without the benefit of any file
structure. Grant it only to users who need it.
If
this privilege is given to unqualified users who do
not need it, the operating system and service to
other users can be disrupted.
Such disruptions can
include the destruction of information on the system
6-9

Managing Privileges
device, the destruction of user data, and the
exposure of confidential information to unauthorized
persons.

WWRITE Privilege
The world write privilege (WWRITE) gives you create, rename, and write
access to all files except those in [0,*]. For files in [0,*], you
need to have SYSIO privilege as well as WWRITE privilege.

User-Defined Privileges
The user-defined privileges (USERl-8) are eight privileges that have
been reserved for your own definition. Third-party and user software
can test them at the system program level to control various aspects
of their application programs, such as restricted functions or
restricted access to certain files. RSTS/E does not use these
privileges for any access or privilege checks.

Multiple Privileges and Jobs
The following sections describe how the monitor handles privilege
information during the life of a job. They describe:
0

Privilege Masks

Job Creation

Logout

Spawned Jobs

privilege Masks
A user's privileges are recorded in the job structure of the user's

job in three privilege masks: authorized, current, and saved. When a
user logs in to the system, the user's authorized and current
privilege masks are initialized from the job's account attributes.

6-1Q

Managing Privileges
The saved privilege mask is a copy of the current privilege mask upon
entry to a privileged program. When temporary privileges are dropped,
the current privilege mask is restored from the saved privilege mask.

Job creation
At job creation, the monitor initializes both the current mask and the
authorized mask, giving them all privileges except SYSMOD.

Login
When a job logs in, the system looks up the authorized mask in the
account attributes.
It copies this mask into the saved and authorized
masks, ORs it into the current mask, and sets the job status to
indicate the job has temporary privileges in effect.
If a program logs in, it now has all the privileges it originally had
plus possibly some new ones. When the program exits, the user has all
authorized privileges enabled; temporary privileges are dropped.
A user who logs in may not want all authorized privileges to be active
at login.
In that case the user can use a LOGIN.COM file to initially
drop some privileges.

Logout
When a job logs out, the monitor clears the group-related privileges
GACNT, GREAD, and GWRITE in all three privilege masks.
This is done
because the job is currently running with a project-programmer number
(PPN) of [0,0] effectively putting it in group zero.
The monitor
drops group privileges because the intent of these privileges is to
allow access to the user's group, not group zero.
Apart from losing group privileges, a job neither gains nor loses any
privileges as a result of logging out.

Spawned jobs
You can spawn a job using the UU.JOB system directive (see the RSTS/E
System Directives Manual). A spawned job can be either logged-in or
logged-out.
For jobs spawned logged-in, the monitor usually gives the
spawned job the set of authorized privileges for the account it logs
in to.
This is done before the program, if any, is run.
If the

6-11

Managing Privileges
program is a privileged program, the usual additional privilege
processing takes place (see the section "Running a Privileged
Program").
Jobs spawned logged-out are given the privileges of the job executing
the UU.JOB directive.
Both logged-out and logged-in jobs spawned to an account other than
the caller's require accounting privilege (GACNT/WACNT).
Spawning
therefore lets users with accounting privilege create jobs that have
some other account's privileges, possibly more than their own.

Running Programs Under Multiple Privileges
The following sections explain how the monitor handles privileges when
running programs.
They describe:
o

Running System Programs

Temporary Privileges

Designating a Program as Privileged

Running a Privileged Program

Program Exit

Running System Programs
System programs provide tools for performing common tasks, such as
managing files and developing programs.
Some programs are available
to all users and require no particular privileges to run.
They have a
protection code <104>.
EDT is an example of a nonprivileged system
program.
other system programs perform functions for privileged users. Most
privileged system programs have a protection code <104>, unless world
file access is required to successfully execute the program.
In that
case the protection code is <124>.
The difference between the
nonprivileged program and the privileged program that have the same
protection code is that the latter verifies that a user has the
required privileges before proceeding.
Some privileged system programs like SHUTUP have a protection code
<232> but require the user to have a particular privilege to gain
access.
In the case of SHUTUP, the user needs the SHUTUP privilege to
run the program.
6-12

Managing Privileges
Access to privileged system programs depends on the user's set of
privileges. When a user attempts to run a privileged program, the
program first performs a privilege check to determine if the user is
sufficiently privileged.
If the user has the correct set of
privileges, the program grants ~ccess.
See the individual description
of each'system program to determine what privileges are required to
gain access.

Temporary Privileges
A program that performs privileged functions for a nonprivileged user
rece.ives the special designation of privileged program. When run, it
gives the user temporary privileges, that is, all privileges except
SYSMOD. When the program exits, the monitor withdraws the extra
privileges from the user.
Temporary privileges give the user access
to privileged programs without compromising system security.
Sometimes programs need to perform privileged functions for
nonprivileged users.
For example, SHUTUP needs to PEEK at memory, an
activity that requires RDMEM privilege.
Because it is a program,
SHUTUP can PEEK in a controlled manner.
Therefore, it is not a
security risk.
On the other hand, unrestricted use of the RDMEM
privilege by a user can compromise system security.

Designating a Program as Privileged
A user designates an executable program as privileged by setting the
privilege bit (128) and the executable bit (64) in the protection
code.
Therefore, any program with a protection code of <192> or
higher is privileged.
The normal protection code associated with
privileged executable programs is <232>, granting execute access to
all, but restricting read/write access to the owner.
For security purposes, there are two restrictions regarding privileged
programs:
o

A user needs the SYSIO privilege to be able to designate a
program as privileged.

A privileged program cannot reside on a disk that is mounted
/NOSHARE.
This restriction prevents an outsider from
acquiring privileges by bringing in a privileged program on a
private pack.
To be able to mount a disk /SHARE, a user
needs tne MOUNT privilege.
Thus, it is important that users
who have the ability to mount disks /SHARE know the contents
of the disk they are mounting.

6-13

Managing privileges
Running a Privileged Program
When a user runs a privileged program, the monitor copies the
account's current privilege mask into the saved privilege mask, then
it ORs all privileges except SYSMOD into the current privilege mask,
giving the user temporary privileges (all but SYSMOD).
It is good programming practi~e to have privileged programs drop
privileges on entry, and raise them only when needed. This practice
provides better protection against programming errors damaging the
system. It thereby improves system security.

Program exit
Whenever a program exits or chains to another program, the monitor
performs the following privilege-related cleanup:
o

If temporary privileges are in effect, the monitor copies the
saved mask back into the current mask. This cancels the
temporary privileges.

The monitor cancels any third-party privilege check currently
in effect (see the RSTS/E programming Manual, SYS call 31, or
the RSTS/E System Directives Manual, general directive
UU.3PP).

If the job is currently logged out and does not have WACNT
privilege, and the program exits, then the monitor kills the
job. Passing control from one program to another program is
possible without restriction when a job is logged out, but
other operations that exit the current program result in a
self-kill.

If the program being exited is a privileged program, then the
monitor clears the job's memory and sets the job size to the
minimum size for the job's default keyboard monitor.

6-14

Chapter 7
Managing Accounts

This chapter gives background information on managing RSTS/E accounts.
and then describes the DCL commands you use to create and maintain
accounts.
Table 7-1 summarizes these commands.
Table 7-1:

DCL Commands for Managing Accounts

+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command

Description

+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
CREATE/ACCOUNT

Sets up a new account on a file-structured disk

DELETE/ACCOUNT

Deletes an account from a file-structured disk

SET ACCOUNT

Changes an account's attributes

SET PASSWORD

Changes an account's password

SHOW ACCOUNT

Displays account attributes

+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Accounts
An account is the structure by which RSTS/E recognizes a timesharing
user, and in which RSTS/E maintains usage and access data.
Each
account is identified by a PPN, and can exist on any disk -- public,
or private.
However, you can only log in to accounts that are defined
on the booted system disk.

7-1

Managing Accounts
The public disk structure can be one or more disks and collectively
these disk(s) are represented by the logical name, SY:. Within the
public structure, the booted disk is known as SYO:.
You can
explicitly create, delete, or modify accounts on SYO: or any private
disk, but not on other public disks.
The system automatically extends
accounts on public disks as needed.
The only command that lets you
specify a public disk in the device specification is SHOW ACCOUNT.
RSTS/E has two types of accounts:
o

User -- Contains files and login attributes

Nonuser -- Only contains files

The system decides which type account to create by the following
rules:
o

Explicitly by qualifier: /USER or /NOUSER

Implicitly by the presence of any qualifier that suggests a
user account such as /IN_QUOTA, /PRIVILEGES, /[NO]LOOKUP, or
/[NO]NETWORK

Neither of the above: /USER is assumed if the disk is SYO:,
/NOUSER is assumed if the disk is private

project-Programmer Number (PPN)·
RSTS/E identifies each account by a project-programmer number (PPN).
You can specify the project or programmer number as a single value or
a range of values. You assigri the PPN when you create the account.
The PPN cannot be changed. Valid PPNsare: [0,1-254] and
[1-254,0-254].
Note that [0,1-254] are legal PPNs for nonuser accounts only; they are
not legal PPNs for user accounts.
That is, no job can log in under
[0,*]. Account [0,1] is created when the disk is initialized, and
cannot be deleted. Also, [0,1-199] are reserved for DIGITAL software
and [0,200-254] are reserved for user software packages.

7-2

Managing Accounts
Account Access Privileges
There are three categories of access to account information.
different set of privilege flags control each category.
The
categories are:
o

Read information -- Read accounting data and account
attributes
None -- You can read and display accounting information
in the current account (except the password blockette)
GACNT -- You can read and display accounting information
of any account in your group
WACNT -- You can read and display accounting information
of any account

Set information -- Write accounting data and attributes to,
or create or delete accounts
GACNT
You can write accounting data of any account in
your group
WACNT -- You can write accounting data of any account on
the system

Set password -- Write (change) the passwords
SETPAS -- You can change your own password (using the SET
PASSWORD command, only)
GACNT -- You can change the password of any account in
your group
WACNT -- You can change the password of any account on
the system

The privileges are inclusive: that is, if you have sufficient
privilege to perform a given operation on any account in your group,
you can also perform that operation on your own account.
Similarly,
if you have sufficient privilege to perform a given operation on any
account on the system, you can perform that operation on any account
in your group (including your own account).

7-3

Managing Accounts
Account Data
The following sections describe the data an account has to manage
timesharing access and usage. Unless the section notes otherwise,
each account element is:
o

Initialized by CREATE/ACCOUNT

Changed by SET ACCOUNT

Displayed by SHOW ACCOUNT

Deleted by DELETE/ACCOUNT

Account Name
The account name can be 1 to 14 characters, chosen from the ASCII
character set whose decimal valu~s are 9, 32 through 126, and 161
through 254.
This field is di(played by the SHOW ACCOUNT command, by
PBS on job and file header pages, and by the BROADCAST command on
message headers.

Date/Time/Keyboard of Last Login
The date and time that the account was most recently logged in to, and
the keyboard at which that login occurred.
The monitor maintains
these data.
You cannot change these fields with account management
commands or monitor directives.

Date/Time of Last Password Change
The date and time that the account's password was most recently
changed.
The monitor maintains these data.
You cannot change these
fields with account management commands or monitor directives.

Password
Normally, the system stores an account's password on the disk in such
a way that it cannot be looked up.
You select this form of storage
with the /NOLOOKUP qualifier.
If you need compatibility with earlier
versions of RSTS/E, the /LOOKUP qualifier directs the system to store

7-4

Managing Accounts
an account's password on the disk in such a way that the UU.RAD
directive can be used to look it up (see the RSTS/E System Directives
Manual).
No DIGITAL-supplied program ·displays passwords.
For a /NOLOOKUP account, the password can be 6 to 14 characters long,
chosen from the ASCII character set whose decimal values are 9, 32 to
62, 64 to 126, and 161 to 254.
For a /LOOKUP account, the password
must consist of six alphanumeric characters.
A user can change an account's password using the SET PASSWORD command
if the user has SETPAS privilege.
An account can also be set to the special state /NOPASSWORD_PROMPT.
When this is so, LOGIN permits access to the account without requiring
(or prompting for) a password.
The password still exists; however, it
is not used until the special state is cleared by setting
/PASSWORD_PROMPT.

Interactive Flag
If set, the interactive flag lets a user log in under an account.
If
the interactive flag is not set, the system does not allow a job to be
logged in under this account's PPN, except by the create job directive
UU.CRE (see the RSTS/E System Directives Manual).
No logins (by use
of the UU.LIN system directive), interactive or otherwise, are
allowed.
Note
Batch jobs are still allowed even if the interactive
flag is not set.

Captive Account Flag
The captive account flag controls the way in which a job under a given
account exits.
If the captive flag is set, the system expects the job
to remain totally under the control of a predetermined procedure, such
as a login command procedure or a menu processor. Any attempt to exit
to the keyboard monitor signals either an error or some devious
action.
The monitor converts such an exit request into a self-kill
directive and removes the job.

7-5

Managing Accounts
Network Flag
The network flag, if set, lets you initiate a job under a given
account over a network connection. This flag allows or disallows any
network activity, for example, a remote COpy or SET HOST.

Dial~p

Flag

The dial-up flag, if set, lets you initiate a job under a given
account over dial-up lines.

Expiration Date
The expiration date specified by this field is the last date on which
you can initiate a job under the associated account.
The system can
be instructed (/EXPIRE without a date argument) never to allow
initiation of a job under the PPN of this account.
You can disable this field using /NOEXPIRE.
lets an account remain usable indefinitely.

The /NOEXPIRE qualifier

Authorized Privilege Mask
The authorized privilege mask specifies the maximum set of privileges
that a job running under this account can exercise (other than by
running privileged programs).
When a job logs in, all authorized privileges for the account are
copied to the job's current privilege mask.
You can use commands in
your LOGIN.COM file to turn off some privileges at log in.

Creation Date
The date that the account was created. You assign the creation date
when you create the account.
The creation date cannot be changed.

UFD Cluster Size
UFO cluster size is the number of 512-byte blocks that each cluster
allocated to the account's directory contains.
You assign the UFO
cluster size of a directory when you create an account. The UFO
cluster size cannot be changed.
7-6

Managing Accounts
An account can have a maximum of seven clusters; therefore, the UFD
clustersize affects the maximum number of files that can be stored in
the account.
This maximum value is further affected by the size of
each file, its cluster size and attributes.

Quotas
You can assign quotas on disk usage, job slots, and message receiver
slots when you create an account.
See Chapter 5 for a discussion of
these quotas.

System Data
The system account [0,1] on the system disk, is used to support
certain system parameters such as the system password.

Commands
The following sections describe the commands which you can use to
manage accounts. All parameters can be specified on the command line.

7-7

CREATE/ACCOUNT
CREATE/ACCOUNT Command
The CREATE/ACCOUNT command sets up a new account on a file-structured
disk.
CREATE/ACCOUNT requires GACNT or WACNT privileges.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

I Format
I
I

CREATE/ACCOUNT dev:[p,pn]

I Command Qualifiers
I

Defaults

/[NO]CAPTIVE
I /CLUSTER_SIZE=ufd-cluster-size
/DETACHED_JOB_QUOTA=detached-job-quota
/[NO]DIALUP
/[NO]EXPIRE=date-spec
/IN_QUOTA=logged-in-quota
/[NO] INTERACTIVE
/JOB_QUOTA=job-quota
/[NO]LOG
/[NO]LOOKUP
/MESSAGE_QUOTA=message-quota
/NAME="account name"
/[NO]NETWORK
/OUT_QUOTA=logged-out-quota
/[NO] PASSWORD_PROMPT
/POSITION=position
/PRIVILEGES=(priv, ... )
/RIB_QUOTA=rib-quota
/SIZE=ufd-size
/TEMPLATE=dev:[p,pn]
/[NO]USER
I

/NOCAPTIVE
/DETACHED JOB_QUOTA=O
/DIALUP
/NOEXPIRE
/IN_QUOTA=UNLIMITED
See discussion
/JOB_QUOTA=UNLIMITED
/LOG
/NOLOOKUP
/MES SAGE_QUOTA=l 2
/NETWORK
/OUT_QUOTA=UNLIMITED
/PASSWORD_PROMPT
/POSITION=INDEX
/PRIVILEGES=SETPAS
/RIB_QUOTA=3
/SIZE=l
See discussion

Prompts
Account:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
dev: [p, pn]
Device specification of a mounted device and the PPN for the
account to create.
You must specify either the device
specification or PPN.
The default value for dev: is SYO:.
The
default PPN is your PPN.
You can have wildcards and ranges in
the PPN specification.
The allowable values for the PPN depend
on the privileges you have.

7-8

CREATE/ACCOUNT
Command Qualifiers
/[NO]CAPTIVE
Indicates whether the account is to be a captive account.
The default is /NOCAPTIVE.
/CLUSTER_SIZE=ufd-cluster-size
The number of 5l2-byte blocks that each cluster in this account's
UFD contains. Acceptable values are 1, 2, 4, 8, or 16.
The
value cannot be less than the pack cluster size of the specified
disk.
/DETACHED_JOB_QUOTA=aetachea-job-quota
See Chapter 5.

The default is O.

/[NO]DIALUP
Indicate~

whether logins from dial-up terminal lines are allowed.

The default is /DIALUP.
/[NO]EXPIRE=date-spec
/NOEXPIRE means that the account is never to expire.
/EXPIRE=date-spec means that the account expires at the end of
the date you specify.
/EXPIRE without a date specification means that the account is to
be marked as "already expired," that is, unavailable for any job
to run or be created under its PPN.
The default is /NOEXPIRE.
/IN_QUOTA=logged-in-quota
See Chapter 5.
The allowable values are 0 to 16,777,214 and
UNLIMITED.
Zero means that no disk storage is allowed.
UNLIMITED is a special value that means the monitor does not
enforce the logged-in quota.
The default is UNLIMITED.

7-9

CREATE/ACCOUNT
/[NO] INTERACTIVE
This qualifier controls the way in which you can create a job
under this account.
If you set /NOINTERACTIVE, the system does
not allow jobs to be logged in under this account's PPN except by
the create job directive UU.CRE (see the RSTS/E System' Directives
Manual) .
The default is /INTERACTIVE.
/JOB_QUOTA=job-quota
See Chapter 5.

The default is UNLIMITED.

/[NO]LOG
If /LOG is in effect, the CREATE function logs the creation of
the new user or nonuser account with one of the following
messages:
User account dev:[p,pn] created at <device cluster number>
Non-user account dev:[p,pn] created at <device cluster number>
The default is /LOG.
/[NO]LOOKUP
/NOLOOKUP means that RSTS/E stores the password in such a way
that it cannot be looked up.
/LOOKUP means that RSTS/E stores
the password in a manner that follows the RSTS/E VS.O rules.
The default is /NOLOOKUP.
/MESSAGE_QUOTA=message-quota
See Chapter 5.
The allowable values can be from 0 to 65,535 or
UNLIMITED.
The UNLIMITED keyword means that the monitor does not
enforce the message quota.
The default is 12.
/NAME="accoun~

name"

Can be 1 to 13 characters, chosen from the ASCII character set
whose decimal values are 9, 32 to 126, and 161 to 254.
/[NO]NETWORK
Indicates whether logins over network connections are allowed.
The default is /NETWORK.

7-10

CREATE/ACCOUNT
/OUT_QUOTA=logged-out-quota
See Chapter 5.
The allowable values are 0 to 16,777,214 and
UNLIMITED.
Zero means that no disk storage is allowed to remain
at logout time.
UNLIMITED is a special value that means the
monitor does not enforce the logged-out quota.
The default is UNLIMITED.
/[NO] PASSWORD_PROMPT
/NOPASSWORD_PROMPT means that LOGIN is not to require or prompt
for a password for a user to gain access to the specified account
(that is, specifying the [p,pn] in response to User: is
sufficient to log a user in to the account).
The default is /PASSWORD_PROMPT.
/POSITION=position
The starting position of the account's UFD expressed in device
cluster numbers (DCNs).
Legal values are 1 through the maximum
DCN for the specified disk.
MIDDLE is a special value that means create the UFD for this
account as near as possible to the middle of the disk.
INDEX is
a special value that means create the UFD as near as possible to
the master file index.
The default is INDEX.
/PRIVILEGE=(priv, ... )
The possible values for each priv are: NONE, ALL, a privilege
keyword, or a privilege keyword with a NO prefix. ALL means all
privileges that the current user has enabled.
RSTS/E scans the list from left to right, with each successive
term adding or taking away privileges.
For example,
(ALL,NOWWRITE) means all privileges except WWRITE.
If you specify /TEMPLATE=dev:[p,pn], RSTS/E treats the template
account's privileges as though they appeared to the left of all
the entries in the /PRIVILEGE qualifier.
/RIB_QUOTA=rib-quota
See Chapter 5.
The allowable values can be from 0 to 256 or
UNLIMITED.
The UNLIMITED keyword means that the monitor does not
enforce the RIB quota.
The default is 3.
7-11

CREATE/ACCOUNT
/SIZE=ufd-size
The initial size of the new account's UFD expressed in clusters.
Acceptable values are 0 - 7.
The default is 1.
/TEMPLATE=dev:[p,pn]
If present, this qualifier indicates that the specified account's
parameters are to be used as defaults for the new account's
parameters.
You must specify either the device specification or
the PPN.
The default value for dev: is
PPN.

SYO:.

The default PPN is your

Note
The specified account's password, size, and
position are not part of the defaults for the new
account.
/[NO]USER
Indicates the type of account to create. /USER means create an
account with login attributes and file storage capabilities.
/NOUSER means create an account for file storage only.
The default is /NOUSER.

7-12

DELETE/ACCOUNT
DELETE/ACCOUNT Command
The DELETE/ACCOUNT command removes an account from a file-structured
disk.
DELETE/ACCOUNT requires WACNT or GACNT privilege and WWRITE or
GWRITE privilege.
You also need SYSIO privilege to delete a [0,*]
account.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
DELETE/ACCOUNT dev:[p,pn]
Command Qualifiers

Defaults

/[NO]LOG
/[NO]PURGE[=QUERY]
/[NO]QUERY
/[NO]RESET[=QUERY]
/[NO]USER

/LOG
See discussion
See discussion
See discussion
See discussion

prompts
Account:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Command Parameters
dev:[p,pn]
Device specification of a mounted disk, and the PPN of the'
account to delete from the specified disk. You can omit the
device specification (the default is _SYO:)i you must specify the
PPN.
The PPN field allows wildcards and ranges.
Unless you specify /NOQUERY, the system requests confirmation
that you really want to delete the account:
Really delete account dev:[p,pn] (NO> ?
Command Qualifiers
/[NO]LOG
If /LOG is in effect, the DELETE function logs the deletion of
the account:
Account dev:[p,pn] deleted
The default is /LOG.

7-13

DELETE/ACCOUNT
/[NO]PURGE[=QUERY]
This qualifier controls the actions to be taken if the account
contains files. When you specify /PURGE, DELETE/ACCOUNT deletes
any files which it finds, and then deletes the account.
If you
specify the optional argument (=QUERY), RSTS/E displays a warning
message that files exist for the specified account and requests
permission to proceed.
When you specify /NOPURGE, DELETE/ACCOUNT displays a warning
message if files exist in the account, skips the account, and
goes to the next account if a wildcard account was specified:
%Account dev:[p,pn] has n blocks of disk allocated
Account dev:[p,pn] not deleted
If you do not specify /PURGE, /NOPURGE, or if /PURGE=QUERY is
specified, DELETE/ACCOUNT proceeds if no files exist. Otherwise,
before proceeding, RSTS/E displays a prompt indicating that there
are files in the account:
Proceed (Y/N) <N> ?
Deleting files (either by /PURGE or by answering YES to the
prompt) requires GWRITE or WWRITE privilege.
If any file deleted
by DELETE/ACCOUNT has protected data (protection code = l28), the
system writes over the file with zeros before deletion.
/[NO]QUERY
Controls the action taken if the account has nonzero accounting
data or contains files.
/QUERY indicates that RSTS/E displays a 'prompt before deleting
any account. /NOQUERY indicates that RSTS/E only displays a
message if the account has nonzero accounting data or contains
files.
The default is /NOQUERY.
/[NO]RESET[=QUERY]
Controls the action taken if the specified account has nonzero
accounting data (CPU time, device time, connect time, or
kilo-core-ticks).
If you specify /RESET, RSTS/E deletes the
account even if it has nonzero accounting data.
If you specify
the optional argument (=QUERY), RSTS/E displays a warning message
that the specified account has nonzero accounting data and asks
for permission to proceed.

7-14

DELETE/ACCOUNT
If you specify /NORESET, DELETE/ACCOUNT displays a warning
message if the account has nonzero accounting data, skips the
account, and "goes to the next account if a wildcard account was
specified:
%Account dev:[p,pn] has nonzero accounting statistics
Account dev:[p,pn] not deleted
If you do not specify /RESET, /NORESET, or if /RESET=QUERY is
specified, the delete account operation proceeds if the
accounting data is zero.
Otherwise, RSTS/E displays a warning
message indicating that t~e specified account has nonzero data
and asks for permission to proceed.
/[NO]USER
You can restrict the search for a given account to a specific
type (user or nonuser) by using this qualifier.
The default is
to search all accounts.
Examples
o

To always delete an account regardless of its current state,
type:
DELETE/ACCOUNT/PURGE/RESET/NOQUERY

To never delete an account that has files or nonzero
accounting data, type:
DELETE/ACCOUNT/NOPURGE/NORESET

To always be prompted before deleting an account, type:
DELETE/ACCOUNT/QUERY

To only be prompted for an account that has files or nonzero
accounting data, type:
DELETE/ACCOUNT

7-15

SET ACCOUNT
SET ACCOUNT Command
The SET ACCOUNT command modifies account parameters on a
file-structured disk.
SET ACCOUNT requires GACNT or WACNT privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
I
I
I

Format
SET ACCOUNT dev:[p,pn]

Command Qualifiers

Defaults

/[NO]CAPTIVE
/DETACHED_JOB_QUOTA=detached-job-quota
/[NO]DIALUP
/[NO]EXPIRE[=date-spec]
/IN_QUOTA=logged-in-quota
/[NO] INTERACTIVE
/JOB_QUOTA=job-quota
/[NO]LOG
/[NO]LOOKUP
/MESSAGE QUOTA=message-quota
/NAME="account name"
/[NO]NETWORK
/OUT_QUOTA=logged-out-quota
/[NO] PASSWORD_PROMPT
/PRIVILEGES=(priv, ... )
/RIB_QUOTA=rib-quota
/[NO]USER

/LOG

Prompts
Account:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
dev:[p,pn]
Device specification of a mounted disk and the PPN of the account
to modify on the specified disk.
You can omit either the device
specification or the PPN, but not both.
The default device
specification is _SYO:.
The default PPN is the user's PPN.
You can have wildcards and ranges in the PPN specification.
RSTS/E uses all qualifiers that apply to a specific account and
displays the following informational message:
Account dev:[ppn] modified

7-16

SET ACCOUNT
If no qualifiers apply to a selected account, the system displays
the following warning message:
%Account dev:[ppn] not modified
Command Qualifiers
/[NO]CAPTIVE
Indicates whether the account is to be a captive account.
/DETACHED_JOB_QUOTA=detached-job-guota
See Chapter 5.
/[NO]DIALUP
Indicates whether logins from dial-up terminal lines are allowed.
/[NO]EXPIRE=date-spec
/NOEXPIRE means that the account is never to expire.
/EXPIRE=date-spec means that the account is to expire at the end
of the day specified.
/EXPIRE without a date specification means that the account is to
be marked as unconditionally expired, that is, unavailable for
any job to run under its PPN.
/IN_QUOTA=logged-in-quota
See Chapter 5.
/[NO] INTERACTIVE
This qualifier controls the way in which you can create a job
under this account.
If you set /NOINTERACTIVE, the system does
not allow jobs to be logged in under this account's PPN except by
the create job directive UU.CRE (see RSTS/E System Directives
Manual).
/JOB_QUOTA=job-guota
See Chapter 5.

7-17

SET ACCOUNT
/[NO]LOG
If /LOG is in effect, the SET ACCOUNT function logs the
modification of the account:
Account dev:[p,pn] modified
If /NOLOG is in effect, only warning messages are logged.
The default is /LOG.
/[NO]LOOKUP
/NOLOOKUP means that RSTS/E stores the password in such a way
that it cannot be looked up.
/LOOKUP means that RSTS/E stores
the password in a manner that follows the pre-V9.0 rules.
/MESSAGE_QUOTA=message-quota

See Chapter 5.
/NAME="account name"
Can be 1 to 13 characters, chosen from the ASCII character set
whose decimal values are 9, 32 to 126, and 161 to 254.
/[NO]NETWORK
Indicates whether logins over network connections are allowed.
/OUT_QUOTA=logged-out-quota
See Chapter 5.
/[N01PASSWORD_PROMPT
If you specify /NOPASSWORD_PROMPT, the account is set to not
require a password for logging in.
To resume password prompting,
specify /PASSWORD_PROMPTj the password is the same as it was
before /NOPASSWORD_PROMPT was specified.

7 -.18

SET ACCOUNT

/PRIVILEGE=(priv, ... )
This qualifier modifies the privileges currently assigned to the
account. A priv specification occurring in the positive form
adds the associated privilege to the account's authorized
privilege mask; a NOpriv specification removes the associated
privilege. Note that the change affects only future logins; jobs
already logged in are unaffected.
A positive specification (priv) is effective only if you are
authorized to have that privilege. However, any user with WACNT
or GACNT (as appropriate) can remove any privilege.
/RIB_QUOTA=rib-quota
See Chapter 5.
/[NO]USER
You can restrict the search for a given account to a specific
type (user or nonuser) with this qualifier.
The default is to search all

acco~nts.

7-19

SET PASSWORD
SET PASSWORD Command
The SET PASSWORD command lets you change the password of the specified
user account. When you issue this command, the system responds with:
New password:
You then enter the desired new password.
If the entry is invalid or a
null string (RETURN only), the system gives the error message ?Invalid
password, and returns to the New password prompt.
The system accepts
an oversize password string; however, it ignores the excess characters
and displays a warning message.
After you enter a new password, the system prompts:
New password again, for verification:
You then reenter the same password.
If the passwords do not match,
the system displays the error message ?Verification mismatch, does not
change the password, and returns to command level.
If the passwords
match, the system displays the /LOG message, if any, and returns to
command level.
Users need SETPAS (or either GACNT or WACNT) privilege to change their
own password. Users need GACNT or WACNT privilege to change another
account's password.
If you only have SETPAS, the system prompts you
for the old password:
Old password:
You must enter the correct current password for your account. A
mismatch results in the error message ?Old password validation error.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Format
SET PASSWORD [dev:[p,pn]]
Command Qualifiers

Defaults

/[NO]LOG

/LOG

/SYSTEM
Prompts
See description
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

7-20

SET PASSWORD
Command Parameters
dev:[p,pn]
Device specification of a mounted disk, and the PPN of the
account for which to change the password.
You can omit the
device specification, the PPN, or both.
The default device
specification is _SYO:.
The default PPN is the user's PPN.
If a nonuser account is specified, the system displays a warning
message:

% [ppn] is not a user account
You can have wildcards and ranges in the PPN specification.
wildcard or range specification includes a nonuser account,
RSTS/E skips the account and does not display a message.

If a

Note
Users who only have SETPAS privilege cannot
specify a dev:ppn parameter; in that case, RSTS/E
rejects the command and displays the following
error message:
?Need xACNT privilege to access dev:[ppn]
Command Qualifiers
/[NO]LOG
If /LOG is set, successful setting of a new password yields:
Password set for account dev:[p,pn]
The default is /LOG.
/SYSTEM
If you specify /SYSTEM, the new password replaces the old system
password.
You must have WACNT privilege to change the system
password.

7-21

SHOW ACCOUNT
SHOW ACCOUNT Command
The SHOW ACCOUNT command displays account attributes.
No privilege is
required to display your own account.
You need GACNT or WACNT
privilege to display other accounts.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
SHOW ACCOUNT dev:[p,pn]
Command Qualifiers

Defaults

/ACCOUNTING_DATA
/ALL
/BRIEF
/FULL
/OUTPUT=filespec
/[NO]RESET
/[NO]USER

See discussion
See discussion
/BRIEF
/NORESET
See discussion

Prompts
None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
dev: [p, pn]
Device specification of a mounted disk, and a PPN.
The PPN can
be a wildcard or range specification (for appropriately
privileged users).
You can omit both the device specification
and the PPN.
The default device specification is _SYO:.
The
default PPN is the user's PPN.
Command Qualifiers
/ACCOUNTING_DATA
Produces a one-line display of accounting data for the specified
accounts.
This qualifier conflicts with /BRIEF and /FULL.
If
you specify them in combination, the rightmost qualifier
overrides the others and execution proceeds without an error.
/ALL
Produces a display of all accounts on the specified disk.
If an
account is specified along with /ALL, the account specification
overrides /ALL.

7-22

SHOW ACCOUNT
/BRIEF
Produces a display that uses only one line per account. You
cannot use /BRIEF in combination with /RESET. When shown the
display, the letters IDNCLP indicate that the account has the
following attributes:
I
Interactive
D
Dial-up
N = Network
C
Captive
L = Lookup password
P
Password prompt
/FULL
Produces a complete display for the accounts specified.
/OUTPUT=filespec
If specified, the display is written to the file you specify.
/[NO]USER
Specifies which accounts are to be included in the display.
/USER means only display accounts with login attributes. /NOUSER
means only display accounts without login attributes.
The default is to display all accounts.
/[NO]RESET
Indicates whether the accounting data is reset after being
displayed. /RESET requires GACNT or WACNT privilege. You cannot
use /RESET in combination with /BRIEF.
If neither
/ACCOUNTING_DATA or /FULL is specified, /ACCOUNTING_DATA is
assumed.
The default is /NORESET.
Examples
The following are samples of the output from the SHOW ACCOUNT command
with different qualifiers.

7-23

SHOW ACCOUNT
$

SHOW ACCOUNT/BRIEF [*,194]

Account

Name

[1,194]
[2,194]
[3,194]
[4,194]
[10,194]

Blade Runner
JT Sysgen
JT PIP
JT ACTMGR

Allocation
6016
5080
4336
3280
752

IDNCLP Last Login
IDN
I
IDN
IDN

P KB26:
P KB32:
P KB32:
P

Expires

03-Dec-84 01:24 PM 15-AUG-88
12-Nov-84 02:56 PM
06-Nov-84 03:06 PM

5 accounts matching _SYO:[*,194]
Total allocation:
19464

Note
If an asterisk (*) character appears after the value
in the allocation field, it means the account is over
quota.
$

SHOW ACCOUNT/ACCOUNTING_DATA [*,194]

Account

Name

[1,194]
[2,194]
[3,194]
[4,194]
[10,194]

Blade Runner
JT Sysgen
JT PIP
JT ACTMGR

Allocation

KCT

CPU-time

Connect

Device

6016
5080
4336
3280
752

52377442
2215
859
797

58:23:24.9
00:00:17.5
00:00:08.6
00:00.09.7

903:25
00:15
00:17
00:02

214:35
00:00
00:00
00:00

5 accounts matching SYO:[*,194]
Total allocation:
19464

Note

If an asterisk (*) character appears after the value
in the allocation field, it means the account is over
quota.
$ SHOW ACCOUNT/FULL
"Blade Runner"

Created 09-May-85

Privileges:

GACNT WACNT
HWCFG HWCTL
USER2 USER3
SHUTUP SWCFG

GREAD GWRITE WREAD WWRITE DATES DEVICE EXQTA
INSTAL JOBCTL MOUNT PBSCTL RDMEM USERO USER1
SETPAS
USER4 USER5 USER6 USER7 RDNFS SEND
WRTNFS
SWCTL SYSIO SYSMOD TUNE

Attributes:

INTERACTIVE
NOLOOKUP

DIALUP
NETWORK
PASSWORD_PROMPT

_SYO:[1,214]

Quotas:

- Logged out:
Disk usage
Detached:
Job limits
RIB:
Send/Receive -

Accounting:

CPU Time:
Device Time:
Connect Time:

un1imi ted
un1imi ted
256

58:23:24.9
214:35
903:25

NOCAPTIVE
EXPIRES: 15-Aug-88
Logged in:
Total:
Message:

unlimited
3
unlimited

Ki1o-Core-Ticks:
UFD C1ustersize:
Blocks allocated:

52377442
16
6000

Last Password Change on 28-Nov-84 at 03:21 PM
Last login on _KB26: on 03-Dec-84 at 01:24 PM

Note
If an * appears after the value in any field in the
quotas section, it means the account is over quota.

7-24

Chapter 8
Managing Terminals

This chapter gives background information on managing terminals. The
RSTS/E operating system supports a variety of terminals. During the
generation of your system, you specify the number and types of
terminal interfaces that are to be part of your hardware
configuration. While you do specify terminal interfaces, you do not
assign specific terminal characteristics at that time. The RSTS/E
operating system automatically sets the default characteristics of all
interfaces to certain standard values:
o

Produces hard-copy output

Prints data up to 80 columns wide

Receives data at a baud rate of 9600

Sets autobaud detection on multiplexed lines

You must use the SET TERMINAL command to set the characteristics of
the terminals that do not have these standard default values.

understanding the SET TERMINAL Command
The SET TERMINAL command sets characteristics for terminals attached
locally to a RSTS/E system or for terminals connected by dial-up
lines. Users can use the SET TERMINAL command to set characteristics
for their own terminals. Only users with HWCFG privilege can use the
SET TERMINAL command to define characteristics for other terminals.
The /AUTOBAUD qualifier lets the system detect and set the baud rate
of any multiplexed terminal when the user logs in. As system manager,
you can include SET TERMINAL/NOAUTO/PERM commands in the START. COM
file for all multiplexed terminals you want to manually set the baud
rate.

8-1

Managing Terminals
There are two methods for setting the characteristics of dial-up
lines:
o

Nonprivileged user sets characteristics. All dial-up lines
start out with the standard default settings.
Consequently,
the user of a dial-up line must log in to the system at the
standard default settings, and then use the SET TERMINAL
command to set the characteristics of the terminal. Note
that the terminal characteristics revert to the standard
settings when the user logs out.

A user with HWCFG privilege sets permanent characteristics.
You can issue the SET TERMINAL/AUTOBAUD/PERMANENT command to
set the permanent characteristics.
This causes the system to
automatically use the characteristics you set, instead of the
standard values, each time a user logs in on a particular
dial-up line.
Note that the permanent characteristics remain
in effect for the current time-sharing session, unless you
issue a new SET TERMINAL command.

Terminal Line Speed Characteristics File: TERSPD.SYS
You need to create a special terminal line speed characteristics file
if you have these two circumstances:
o

You decide to restrict the valid line speeds at certain
terminals to a subset of the line speeds allowed by the
terminal interface.

You install an interface that has been modified so
nonstandard line speeds are substituted for one or more
standard interface line speeds.

The following guidelines can help you prepare a terminal line speed
characteristics file:
1.

Gather the information on the restrictions or modifications
and the keyboard numbers of the terminals affected

Create a file named TERSPD.SYS with a text editor

Include all of the information from step 1 in the file

Place the file in the system library account.

8-2

Managing Terminals
Note
The /AUTOBAUD qualifier does not honor the restricted
speeds in TERSPD.SYS.
You can use the file TERSPD.SYS to allow only certain speeds on
certain terminals.
The format for each line of the file is the
terminal device designator, a colon, and a list of speeds to allow for
that terminal; each speed separated by a comma.
For example:
KBF2: 300,1200, ...
The terminal device designator can be KBnn:, TTnn:, or KBcnn:.
The
old form (KBnn: or TTnn:) produces the same result as in pre-V9.0
RSTS/E.
In the new form (KBcnn:), c indicates the hardware controller
and nn is a subline on that type controller.
Table 8-1 lists
controller types that RSTS/E supports.
DIGITAL recommends that you use the new form to specify terminal
devices in the START.COM, TERSPD.SYS, and TERDFL.SYS files.
In this
way, if you change the number of pseudo keyboards, you do not have to
change those files.
The SHOW DEVICE command displays both forms of
the device designator for each keyboard.
Table 8·1:

RSTS/E Supported Controller Types

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Code I
Controller Type
I
+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
A
DLll A,B type single line interface

I
I
I
I
I
I
I
I
I
I
I
I
I
I

DLll C,D type single line interface

DLlIE type single line modem interface

Pseudo keyboards

DJ multiplexor

DH multiplexor

DZ/DZV/DZQ multiplexor

H
DHV/DHU multiplexor
+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
You can specify up to 16 speeds for each terminal.
You can specify a
range of terminals on one line as low-end terminal device designator,
an optional colon, dash, high-end terminal device designator,
mandatory colon, and then the list of speeds.

8-3

Managing Terminals
For example:
KBGO-KBH8: 300,1200, ...
When you specify a terminal number without any speeds after it, no
speeds are allowed and the speed cannot be changed.
You can use blank
lines, comment lines (lines beginning with an exclamation mark), and
comments at the end of lines to document the file.
An example of a TERSPD.SYS file follows:
T E R S PD. S Y S
This file is used by the system manager to define
those speeds which are allowed on each terminal.
The format is as follows:
KBn:list of speeds separated by commas.
KBFO:
!No speeds allowed for KBFO
KBF1:2400,9600
!KBFI can have either 2400 or 9600
KBF2:-KBF4:9600
!KBF2 to KBF4 can have 9600 only
KBF5:9600,EXTA,EXTB
!KBF5 can use 9600 & external speeds
KBF6:0,50,75,110,150,200,300,600,1200,l800,2400,4800,9600
KBF7:0,50,75,110,150,200,300,600,1200,1800,2400,4800,9600,EXTA,EXTB
KBF8-KBFI5:0,50,75,110,150,200,300,600,1200,1800,2400,9600
KBGO-KBH8:50,300,1200,2400,4800,9600
KBH9:0,50,75,110,150,200,300,600,1200,l800,2400,9600
KBHIO:-KBHI5:300,600,l200 !KBHIO to KBH15 are dial-up lines
Note
The DLllE-type interface and the individual local
interfaces (KLll and DL11A through DLIID) and the
DJII multiplexer do not have programmable baud rates.
For this reason, you cannot execute commands to
change baud rates on a keyboard line having any of
those interfaces (KBAnn, KBBnn, KBCnn, and KBEnn).

Setting Terminals Other Than Your Own
If you have HWCFG privilege, you can set the characteristics of other
terminals in the RSTS/E system with the SET TERMINAL com~and.
For
example, if you want to set the characteristics of a VT100 terminal
at KB32, type:
$ SET TERMINAL/VT100 KB32:
$

8-4

Managing Terminals
After you type the keyboard number and press the RETURN key, RSTS/E
immediately sets the characteristics of the line to those of a VT100
alphanumeric display terminal.
DCL prints the dollar sign ($) prompt
again to let you enter an6ther command.
You can also change specific characteristics of a terminal.
For
example, to limit the line length of the terminal at KB40, type:
$ SET TERMINAL/WIDTH=60 KB40:
$

Each time 60 characters print on KB40, the system performs a carriage
return and line feed.
Use the /PERMANENT qualifier to specify characteristics on a
logged-out terminal.
For example, you can use /PERMANENT to set an
initial WIDTH characteristic for a pseudo keyboard:
$ SET TERMINAL/WIDTH=70/PERMANENT KBDO:

User-Defined Terminal Characteristics File: TERMAC.SYS
Each line of TERMAC.SYS contains the unique name for a terminal type
and the command qualifiers that define the characteristics of that
terminal type.
The qualifiers are explained in the description of the
SET TERMINAL command at the end of this chapter.
The /TYPE=n qualifier assigns a unique 8-bit binary value to each
terminal type.
The values 0 to 128. are reserved for use by DIGITAL.
The values 129. to 255. are available for user-defined terminal types.
The SHOW TERMINAL command uses this value to locate a terminal's
characteristics.
An example of a TERMAC.SYS file follows:
T E R MAC . S Y S
VT125X/DEV=VTl25/WIDTH=80/SPEED=(300,9600)/TYPE=201
GIGI/DEV=VKIOO/SETUP=GREEN/TYPE=202
! VKIOO W/GREEN BACKGROUND
DIABLO/DEV=LA34/SPEED=9600/WID=80/SETUP=DIABLO/TYPE=203
LA34X/DEV=LA34/TAB/SPEED=9600/TYPE=204
VT52X/DEV=VT52/SPEED=1200/TYPE=205
FOO/DEV=BAR/WIDTH=132/TYPE=206
BAR/DEV=LA120/SETUP=NARROW/WIDTH=80/TYPE=207
For example, to define an LA120 that has only 80-column paper, place
the following line in the file:
MYLA120/DEVICE=LA120/WIDTH=80/TYPE=208
8-5

Managing Terminals
Then, use the following command to set KBI9: to these characteristics:
$ SET TERMINAL/DEVICE=MYLA120/PERMANENT KB19:

You can initialize your terminals to the known terminal types and
their default characteristics through the use of the TERMAC.SYS file.
You can use blank lines, comment lines (lines beginning with an
exclamation mark), and comments at the end of lines to document the
file.

Automatic Setting of Terminal Characteristics: TERDFL.SYS
The file TERDFL.SYS establishes default terminal characteristics for
nonstandard keyboards.
The file is used whenever the user executes
the SET TERMINAL/INQUIRE command and the system was unable to
determine the terminal type.
The system looks up the terminal number
in the file and, if found, sets the characteristics that are on that
line.
If the terminal number is not found, the system displays an
error message.
For most DIGITAL terminals, SET TERMINAL/INQUIRE can determine the
type.
The only supported exception is the LA36.
The same may apply
to older, unsupported terminals or terminals made by other
manufacturers.
If you want the SET TERMINAL/INQUIRE command to work for terminals
whose type cannot be determined, enter them in the TERDFL.SYS file.
(It is not necessary to put any other supported terminals in the
file.) If SET TERMINAL/INQUIRE can determine the type, it ignores any
entry in TERDFL.SYS.
An example of a TERDFL.SYS file follows:
T E R D FL. S Y S
KBHlO:-KBH15:/DEV=LA36
The format for each line of the file is the terminal device
designator, a colon, and then the command qualifiers that define the
characteristics of the keyboard. A range of terminals can be
specified on one line as the low-end terminal device designator, an
optional colon, a dash, the high-end terminal device designator, a
mandatory colon, and then the qualifiers.
You can use blank lines, comment lines (lines beginning with an
exclamation mark), and comments at the end of lines to document the
file.

8-6

Managing Terminals
Setting Permanent Terminal Characteristics
The /PERMANENT qualifier lets you set the permanent characteristics of
a terminal.
For example, to set the characteristics of the dial-up
line on keyboard 14 for the current time-sharing session, you log in
to an account that has HWCFG privilege and type the command:
$

SET TERMINAL/PERMANENT KB14:/DEV=LA36

When you include the /PERMANENT switch with the SET TERMINAL command,
the command takes effect immediately.
If you do not have HWCFG
privilege or the characteristics of the line conflict with the
command~ RSTS/E prints an error message and reprints the DCL prompt.
The characteristics set by executing a SET TERMINAL/PERMANENT command
are in effect until the next system shut down or until you change
them.
If you set characteristics without /PERMANENT, they revert to
the standard characteristics on logout.
Use the /PERMANENT qualifier with all SET TERMINAL commands in
START.COM.

Using the /NOBROADCAST and /BROADCAST Command Qualifiers
The /NOBROADCAST qualifier prevents your terminal or any terminal on
the system from receiving broadcasts sent by the BROADCAST command.
Use this when:
o

You need to print a document on a letter-quality printer and
do not want messages corrupting the printout

You are using a text editor in screen mode at a dial-up
terminal set at a low baud rate.
Repainting the screen each
time someone sends a message can be time consuming,
especially at 300 baud.

Use the /BROADCAST qualifier to allow your terminal to receive
messages again.
Use the /NOBROADCAST qualifier to keep messages from
printing on your own terminal.
For example:
$ SET TERMINAL/NOBROADCAST
$ SHOW TERMINAL/BRIEF
Terminal: KB29:
Device_Type: VT52

Break
CRFill=O
No Hostsync
Scope
Width=80
$

No Broadcast
No Delimiter
Interactive
Speed=9600

Control=(R,T,C)
No Eight_bit
Lowercase
Tab

8-7

No Control=X
No Form
Resume=Control C
TTSync

Managing Terminals
The SHOW TERMINAL command lets you verify that the command worked and
that the rest of the terminal settings are set properly.
If you
decide to reverse this condition, use the /BROADCAST qualifier.
For
example:
$ SET TERMINAL/BROADCAST
$ SHOW TERMINAL/BRIEF
Terminal: KB29:
Device_Type: VT52

Break
CRFill=O
No Hostsync
Scope
Width=80
$

Broadcast
No Delimiter
Interactive
Speed=9600

Control=(R,T,C)
No Eight_bit
Lowercase
Tab

No Control=X
No Form
Resume=Control C
TTSync

Your terminal can now receive BROADCAST messages.
You can also use the /NOBROADCAST and /BROADCAST qualifiers on other
terminals on your system.
Use the SET TERMINAL command as follows:
$ SET TERMINAL KB25:/NOBROADCAST/PERM

$ SHOW TERMINAL/BRIEF KB25:
Terminal: KB25:
Break
CRFill=O
Hostsync
Scope
Width=80
$

Device_Type: VT100
No Broadcast
No Delimiter
Interactive
Speed=9600

Control=(R,T,C)
No Eight_bit
Lowercase
Tab

No Control=X
No Form
Resume=Control C
TTSync

Error Messages
See Appendix D for a summary of the DCL error messages.

Commands
The following sections explain the commands available for managing
terminals: SET TERMINAL and SHOW TERMINAL.

8-8

SET TERMINAL
SET TERMINAL Command
The SET TERMINAL command sets characteristics for terminals attached
locally to a RSTS/E system or for terminals connected by dial-up
lines. Users can use the SET TERMINAL command to set characteristics
for their own terminals. You need HWCFG privilege to define
characteristics for other terminals.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SET TERMINAL [KB[c]nn[:]]
I
I Command Qualifiers

I /[NO]132_COLUMNS

Defaults
None

I /[NO]ADVANCED_VIDEO
/[NO]ALT_MODE
/[NO]ANSI
/[NO]AUTOBAUD
/[NO]BREAK
/[NO]BROADCAST
/BUFFER_QUOTA=n
/BUFFER_QUOTA=l80
/[NO]CONTROL=[(option[,option, ... ])]
/[NO]CRFILL[=n]
/[NO]DELIMITER[=c]
/[DEVICE_TYPE=]terminal type
/[NO]DIALUP
/[NO]EIGHT_BIT
/[NO]ESCAPE_SEQUENCE
/[NO] FORM_FEED
/HARDCOPY
/[NO]HOST_SYNC
/INQUIRE
/[NO] INTERACTIVE
/[NO]KATAKANA
/[NO] LOADABLE_CHARACTERS
/[NO]LOCAL_ECHO
/LOWERCASE[=INPUTIOUTPUT]
/[NO]PARITY[=option]
/PERMANENT
/[NO]PRINTER_PORT
/[NO]REGIS
/RESET
See discussion
/[NO]RESTRICT
/RESUME=[ANYICONTROL_C]
/SCOPE
/SELECT_ERASE
/SETUP=filename
/[NO]SIXEL
/SPEED=(input[,output)]
8-9

SET TERMINAL

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Qualifiers (Cont.)

Defaults (Cont.)

/[NO]TAB
/[NO]TTSYNC
/TYPE=n
/[NO]UP_ARROW
/UPPERCASE[=INPUTIOUTPUT]
/[NO]USER_DEFINED_KEYS
/WIDTH=n
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
[KB[c]nn[:]]
Indicates the terminal to set the characteristics for.
If you do
not specify a terminal, RSTS/E sets the the characteristics of
the terminal that issued the command.
You must have HWCFG
privilege to set the characteristics for another user's terminal.
Command Qualifiers
/[NO]132_COLUMNS
If you specify /132_COLUMNS, the terminal displays single-width
characters in an array of 24 lines by 132 columns.
If you
specify /N0132 COLUMNS, the terminal displays single-width
characters in an array of 24 lines by 80 columns.
/[NO]ADVANCED_VIDEO
If you specify /ADVANCED VIDEO, it means the terminal has the
advanced video option (AVO).
The advanced features include
character attributes (blinking, bolding, ... , and so on), screen
memory, and ROM sockets.
If you specify /NOADVANCED_VIDEO, it
means the terminal does not support AVO.
/[NO]ALT_MODE
If you specify /ALT_MODE, the system treats ASCII 027, 125, and
126 as ESCAPE.
If you specify /NOALT_MODE, the system treats
only ASCII 027 code as ESCAPE.
See /LOWERCASE for more information on the use of this qualifier.
/[NO]ANSI
If you specify /ANSI, it means the terminal supports ANSI escape
sequences.
If you specify /NOANSI, it means the terminal does
not support ANSI escape sequences.
8-10

SET TERMINAL
/[NO]AUTOBAUD
If you specify /AUTOBAUD, the system monitors the terminal line
to detect and set baud rates without requiring the user to
manually set or determine the terminal's speed.
If you specify
/NOAUTOBAUD, the system does not set the terminal line's speed
without manual intervention.
/[NO]BREAK
If you specify /BREAK, the system translates the BREAK key as a
CTRL/C character (ASCII 3).
If you specify /NOBREAK, the system
translates the BREAK key as a null character (ASCII 0).
/[NO]BROADCAST
The /BROADCAST qualifier enables the system broadcast capability
for the terminal.
That is, RSTS/E displays messages from the
SEND system function calIon the terminal.
The /NOBROADCAST
qualifier disables the system broadcast capability for the
terminal.
/BUFFER_QUOTA=n
Indicates the number of input characters that
before the system issues an XOFF character to
stop transmission.
The buffer quota value is
The allowable values range from 180 to 7650.
system uses a quota of 180 characters.

you can buffer
your terminal to
a multiple of 30.
By default, the

The system uses one small buffer for each 30 characters.
Thus,
the default buffer quota of 180 characters uses a maximum of six
small buffers for terminal input.
Changing a terminal's input
buffer quota is useful for high-speed input terminals.
However,
if there are not enough small buffers available, a terminal may
not be able to reach its full quota.
You need HWCFG privilege to use the /BUFFER_QUOTA qualifier.
/[NO]CONTROL=[(option[,option, ... ])]
If you specify /CONTROL=C, the system traps a CTRL/C typed by the
user and handles it accordingly.
If you specify /NOCONTROL=C,
the system ignores a CTRL/C typed by the user.
If you specify /CONTROL=R, the system enables the CTRL/R retype
facility.
If you specify /NOCONTROL=R, the system disables the
CTRL/R retype facility.
If you specify /CONTROL=T, the system enables the CTRL/T job
status display facility.
If you specify /NOCONTROL=T, the system
disables the CTRL/T job status display facility.
8-11

SET TERMINAL
If you specify /CONTROL=X, the system traps a CTRL/X typed by the
user and clears the user's entire type-ahead buffer.
If you
specify /NOCONTROL=X, the system interprets a CTRL/X typed by the
user as data.
If you want to set or reset more than one option on a single
command line, you can combine them in a list.
For example:
/CONTROL=(R,T,C) or /NOCONTROL=(C,X).
/[NO]CRFILL[=n]
If you specify /CRFILL, the system sets the carriage return fill
factor to n, where n is between 0 and 6.
If the argument is not
specified or is zero, or if /NOCRFILL is specified, the system
does not generate any fill characters.
/[NO]DELIMITER[=C]
If the argument is a character within quotation marks (for
example /DELIMITER="\"), the character within quotation marks
becomes the private delimiter.
If the argument is a number (for example /DELIMITER=9), the
private delimiter is the ASCII character whose decimal value is
the number.
This allows for any ASCII character whose decimal
value is between 1 and 127 to be a private delimiter.
If you specify /NODELIMITER, the system removes the private
delimiter that was previously set.
/[DEVICE_TYPE=]terminal type
Sets the default characteristics for the terminal type specified
or, if it is a name of a user-defined macro, sets the
characteristics defined in the macro.
This command recognizes the following terminal types:
LA12
LA34
LA36
LA38

LA50
LA100
LA120
LA180S

VKIOO
VT52
VT55
VT100

VTIOI
VT102
VTI05
VT125

VT131
VT132
VT220
VT240

See the section "User-Defined Terminal Characteristics:
TERMAC.SYS" for a description and example of the user-defined
macro file.
/[NO]DIALUP
Indicates if dial-up control is enabled for the specified
terminal.

8-12

SET TERMINAL

/[NO]EIGHT_BIT
If you specify /EIGHT BIT, it means the terminal supports eight
bit characters. If you specify /NOEIGHT BIT, it means the
terminal does not support eight bit characters.
/[NO]ESCAPE_SEQUENCE
If you specify /ESCAPE_SEQUENCE, the system treats an ESC
character (value 27) as an indication of an incoming escape
sequence. The system does not echo the character and or any of
the characters in the sequence. If you specify
/NOESCAPE SEQUENCE, the system treats an ESC character (value 27)
as a line-terminator and echoes it as a $ character.
/[NO] FORM_FEED
The /FORM_FEED qualifier indicates that the hardware has form
feed and vertical tab capabilities. The system transmits form
feed and vertical tab characters without translation. The
/NOFORM_FEED qualifier indicates that the hardware does not have
form feed and vertical tab capabilities. The system transmits
four line feed characters in place of a form feed or vertical tab
character.
/HARDCOPY
If you specify /HARDCOPY, it means the terminal is not a cathode
ray terminal (CRT) display device. The system echoes a DEL
character (RUBOUT) by printing a backslash (\) and the last
character typed and removes the last character typed from the
terminal input buffer. Later DEL characters cause the next to
last characters to be sequentially printed and removed from the
terminal input buffer until a character other than DEL is
received. As a result, the system echoes another \ to delimit
the erased characters and then echoes the correct character.
If you specify /HARDCOPY and /[NO]TTSYNC is not specified,
/NOTTSYNC is set by default.
/[NO]HOSTSYNC
Specify /HOSTSYNC if the terminal has special hardware that lets
the computer interrupt transmission of characters from the
terminal by sending the terminal an XOFF character (value 19).
Similarly, the computer instructs the terminal to resume
transmission of characters by sending the terminal an XON
character (value 17). The terminal hardware must respond to XOFF
and XON characters by stopping and resuming transmission.
Specify /NOHOSTSYNC if the terminal does not have the hardware
required for the HOSTSYNC feature.
8-13

SET TERMINAL

/INQUIRE
Queries the terminal by sending an ANSI ESCAPE identifying
sequence, then determines the terminal type and sets the
appropriate terminal characteristics. If the terminal does not
respond within five seconds, the system searches the file
TERDFL.SYS to see if there are default characteristics for this
terminal. If an entry is found, the system sets the specified
characteristics. If not, the system displays an error message
and the terminal characteristics are unchanged.
Note
This qualifier causes the terminal's type-ahead
buffer to be cleared. LA36 terminals do not
support this feature.
See the section "Automatic Setting of Terminal Characteristics:
TERDFL.SYS" for more information on using /INQUIRE with terminals
that do not respond to the identifying sequence.
/[NO] INTERACTIVE
Indicates that you can use the terminal to log in to the system.
If you specify /NOINTERACTIVE, the system ignores any characters
input from the terminal while it is not assigned to another job
or not opened. Use this attribute for KB devices set up as
printing devices.
/[NO]KATAKANA
Indicates that the terminal supports the Katakana character set.
/[NO] LOADABLE_CHARACTERS
Indicates that the terminal supports dynamically redefinable
character sets (for example, changing fonts).
/[NO]LOCAL_ECHO
If you specify /LOCAL_ECHO, the system does not echo characters
it receives from the terminal. This is only used for a terminal
that does its own local echo.
If you specify /NOLOCAL_ECHO, characters generated are sent only
to the computer. Therefore, the system echoes each character it
receives so the character is displayed locally and then
translates certain characters to perform the proper action. For
example, the system echoes a CR character as a carriage return
and line feed sequence.

8-14

SET TERMINAL
/LOWERCASE[=INPUTIOUTPUT]
The /LOWERCASE=INPUT qualifier indicates that the system enables
lowercase input from the terminal.
The /LOWERCASE=OUTPUT
qualifier indicates that the system enables lowercase output to
the terminal.
If you specify /LOWERCASE with no argument, the system enables
lowercase input and output.
If you specify /LOWERCASE or
/LOWERCASE=INPUT and /[NO]ALTMODE is not specified, the system
sets /NOALTMODE by default.
/[NO]PARITY=EVENIODD
If you specify /NOPARITY, the system ignores the parity bit on
characters it receives and treats the parity bit on characters it
transmits to the terminal as if the parity bit were a data bit.
If you specify /PARITY=EVEN, the system sends characters to the
terminal with the parity bit properly set for even parity but
ignores the parity bit on characters it receives.
If you specify /PARITY=ODD, the system sends characters to the
terminal with the parity bit properly set for odd parity but
ignores the parity bit on characters it receives.
/PERMANENT
If you specify /PERMANENT, the other qualifiers on the same
command line become the terminal's permanent characteristics.
Permanent characteristics are the characteristics of the terminal
when it is not in use.
The characteristics of the terminal
revert to the permanent characteristics when the user logs out.
You must use /PERMANENT to specify the characteristics of any
terminal, including dial-up controlled terminals.
You must have
HWCFG privilege to specify this qualifier.
/[NO]PRINTER_PORT
Indicates that the terminal has a printer port.
/[NO]REGIS
Indicates that the terminal supports the Remote Graphic
Instruction Set (ReGIS).
/RESET
Resets the terminal's characteristics to the permanent
characteristics.

8-15

SET TERMINAL
/[NO]RESTRICT
If you specify/RESTRICT, it means that only users with DEVICE
privilege can access the specified terminal.
If you specify
/NORESTRICT, it means that any users can access the specified
terminal.
This qualifier only reflects OPENs and ASSIGNs of the device:
not LOGINs.
/RESUME=[ANYICONTROL_C]
Defines the XON/XOFF processing.
The argument ANY enables type
out and echo when any character is typed after XOFF.
The
argument CONTROL_C enables type out and echo only when you type
XON or CTRL/C after XOFF.
/SCOPE
Specify /SCOPE if the terminal is a CRT display terminal that has
the following characteristics:
o

Conforms to synchronization as described under the /TTSYNC
command.

System echoes a DEL character (RUBOUT) as backspace, space,
and backspace sequence.

If you specify /SCOPE, and /[NO]TTSYNC is not specified, /TTSYNC
is set by default.
/[NO] SELECT_ERASE
Indicates if the terminal supports the selectively erasable
character attribute.
If the terminal supports this feature, the terminal recognizes
two forms of the erase in line and erase in display commands.
In
one form all characters within the set parameter are erased
regardless of logical attributes.
The second form changes all
characters designated with the selectively erasable character
attribute into spaces.
/SETUP=filespec
Sends the specified file's data to the terminal, in binary mode.
If you specify a file name only, the system assumes the file is
in the user's account on the system disk with a file type of
.ESC.
The user must have access to the file or an error results.
Use this command to initialize a terminal for which you can make
special software settings.

8-16

SET TERMINAL
/[NO]SIXEL
Indicates if the terminal supports Sixel Graphics.
Sixel
Graphics transfer binary graphic images between the host and the
terminal or the terminal and a printer.
/SPEED=(input[,output)]
Specifies the speed at which the terminal sends and receives
data.
You can specify the speed as a single value to set the input and
output baud rates to the same speed.
To specify a split speed
for input and output, specify /SPEED=(n,m), where the values n
and m indicate the input (terminal to host) and output (host to
terminal) baud rates, respectively.
Note
The /SPEED qualifier works on DH, DHV, DHU, and
DZ terminals.
Split speed only works on DH, DHV,
and DHU terminals.
You can use the keywords EXTA and EXTB to specify a baud rate
associated with the External Clock A and External Clock B baud
rates, respectively.
See the section "Terminal Line Speed Characteristics File:
TERSPD.SYS" for a description and example of the speed file.
/[NO]TAB
/TAB indicates the terminal hardware has tab capability.
system transmits TAB characters without translation.

The

/NOTAB indicates the terminal hardware does not have tab
capability.
To move to the next ~ab stop, the system transmits
the correct number of space characters instead of transmitting a
TAB character.
/[NO]TTSYNC
If you specify /TTSYNC, the terminal obeys the following
synchronization standard: if the terminal sends an XOFF character
(equivalent to the CTRL/S combination), the computer interrupts
transmission until the terminal sends either an XON character
(equivalent to the CTRL/Q combination) or a CTRL/C combination.
If you specify /NOTTSYNC, XON and XOFF characters sent by the
terminal have no special meaning.

8-17

SET TERMINAL

/TYPE=n
Specifies the value of the terminal's type code.
This type code
coincides with a particular terminal type and the SHOW TERMINAL
command uses it to display the terminal type.
This qualifier is
best used in the TERMAC.SYS file to associate a terminal with a
user-defined macro.
Allowable values are 0 to 255.
for DIGITAL use.

The values 0 to 128. are reserved

/[NO]UP_ARROW
If you specify /UP ARROW, the system echoes a control and graphic
character combination as the ~ character (value 94) followed by
the proper graphic character.
For example, CTRL/E prints out as
~E.

If you specify /NOUP_ARROW, the system echoes the control and
graphic character combination as is.
/UPPERCASE[=INPUTIOUTPUT]
The /UPPERCASE=INPUT qualifier indicates that the system disables
lowercase input from the terminal.
The /UPPERCASE=OUTPUT
qualifier indicates that the system disables lowercase output to
the terminal.
If you specify /UPPERCASE with no argument, the system disables
lowercase input and output.
If you specify /UPPERCASE or
/UPPERCASE=INPUT and /[NO]ALTMODE is not specified, the system
sets /ALTMODE by default.

Indicates if the terminal supports User Defined Keys (UDKs).
User Defined Keys let you save a full command string and invoke
it with a single key.

8-18

SET TERMINAL
/WIDTH=n
Sets the width of the print line for the terminal to n.
The
width can be between 1 and 254. As a result, the system
automatically generates a carriage return/line feed combination
if n printing characters have been printed or echoed without a
carriage return/line feed combination and another printing
character is to be transmitted.
If the terminal executing the program is in the VT100/200 family
and the print line width is changed, then the appropriate ESC
sequences are sent to the terminal to change the width of the
screen accordingly.
For example, if the width changes from 80 or
less to 81 or more, then the width of the screen is set to 132;
if the width changes from 81 or more to 80 or less, the width of
the screen is set to 80.

8-19

SHOW TERMINAL
SHOW TERMINAL Command
Displays the current characteristics of a specific terminal.
You can
change each of these characteristics with a corresponding option of
the SET TERMINAL command.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format

I
I

SHOW TERMINAL [KB[c]nn[:]]

Command Qualifiers

Defaults

/ALL
/BRIEF
/FULL
/[NO]PERMANENT

Current Terminal
/BRIEF
/BRIEF
/NOPERMANENT

I
I

I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
[ KB [ c ] nn [ : ] ]
Indicates the terminal for which to show the characteristics.
When you do not specify a terminal, the system displays the
characteristics of the terminal executing the command.
You must
have HWCFG privilege to specify another user's terminal.
Command Qualifiers
/ALL
Displays the characteristics of all the terminals configured on
the system.
If a terminal is specified along with /ALL, the
terminal specification overrides /ALL.
/BRIEF
If you specify /BRIEF, or neither /BRIEF nor /FULL, then a subset
of the full display is shown.
/FULL
If you specify /FULL, the full display is shown.
/[NO] PERMANENT
If you specify /PERMANENT, the system displays the permanent
characteristics of the terminal.
If you specify /NOPERMANENT,
the system displays the current characteristics of the terminal.

8-20

SHOW TERMINAL
Examples
The following examples show the output format for the SHOW TERMINAL
command:
$ SHOW TERMINAL/BRIEF
Terminal: KB26:
No Break
CRFill=O
Hostsync
Scope
Width=80

Device_Type: VT220
Broadcast
No Delimiter
Interactive
Speed=9600

Control=(R,T,C)
Eight_bit
Lowercase
Tab

No Control=X
No Form
Resume=Control_C
TTSync

$ SHOW TERMINAL/FULL
Terminal: KB26:
132 Columns
No Autobaud
Control=(R,T,C)
No Dialup
Hostsync
No Local_Echo
No ReGis
Select_Erase
TTSync

Device_Type: VT220
Advanced Video
No BreakNo Control=X
Eight bit
Interactive
Lowercase
Restricted
No Sixel
Up_Arrow

No Alt Mode
ANSI
Broadcast
Buffer Quota=l80
CRFill=O
No Delimiter
No Escape_Sequence No Form
No Katakana
Loadable Characters
No Parity
printer_port
Resume=Control C
Scope
Speed=9600
Tab
User_Defined_Keys Width=80

8-21

Chapter 9
Managing Print/Batch Services

This chapter gives background information on the print/Batch Services
(PBS) package.
PBS contains routines to help you manage your RSTS/E
V9.0 print and batch servers.
The chapter then describes the DCL commands for using PBS.
summarizes the DCL commands.
Table 9-1:

Table 9-1

DCL Commands for the Print/Batch Services Package

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command
Description
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
!
package-Related
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I START/QUEUE/MANAGER
Starts the Print/Batch Services package
I

I
I STOP/QUEUE/MANAGER

Shuts down the Print/Batch Services package
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Entry-Related
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I DELETE/ENTRY
Deletes one or more print or batch entries
selected by entry-spec or entry-number
PRINT

Queues a request for printing one or more
files

SET ENTRY

Modifies the attributes of one or more print
or batch entries

SHOW ENTRY

Displays the attributes and status of one or
more print or batch entries

SUBMIT

Queues a request for batch processing one or
more command files

9-1

Managing Print/Batch Services
Table 9-1:

DCL Commands for the print/Batch Services Package (Cont.)

+ - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
Description
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - ,; - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Queue-Related
I
+ - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
ASSIGN/QUEUE
Assigns a queue to a server

CLOSE/QUEUE

Closes a queue, preventing it from accepting
additional entries

DEASSIGN/QUEUE

Deassigns a queue from a server, or all
servers

DELETE/QUEUE

Deletes a queue

INITIALIZE/QUEUE

Defines a print or batch queue

OPEN/QUEUE

Opens a queue, allowing entries to be placed
on it

SET QUEUE

Modifies the attributes of one or more
queues

SHOW QUEUE

Displays the attributes and status of one or
more queues

START/QUEUE

Starts a queue, allowing entries to be
routed to servers for processing

STOP/QUEUE

stops a queue, preventing entries from being
routed to servers for processing
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Server-Related
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
DELETE/SERVER
Deletes a print or batch server
INITIALIZE/SERVER

Defines a print or batch server

SET SERVER

Modifies the attributes of one or more
servers

SHOW SERVER

Displays the attributes and status of one or
more servers

START/SERVER

Starts a print or batch server that was
stopped

STOP/SERVER

stops a print or batch server immediately or
when the indicated event occurs
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
9-2

Managing Print/Batch Services
Managing the print/Batch Services package
The Print/Batch Services (PBS) package provides several important
services for RSTS/E users and system managers. The major components
of PBS are:
o

Queue Manager

Print Servers

Batch Servers

User Interface

The Queue Manager accepts all user requests, controls all print and
batch queues, schedules jobs to run, and creates new jobs as needed to
process requests.
Print servers process print requests on selected printers. Both line
printers (LP) and terminals (KB) can be handled by print servers.
Batch servers control execution of submitted command procedures, using
the DeL command file processor (see RSTS/E Guide to writing Command
Procedures). You can establish multiple batch servers to process
several command procedures at the same time.
The user interface is how an application program communicates with
PBS. It lets the user program issue requests for print and batch
services. User Request Packets (see RSTS/E Programming Manual)
provide this link between PBS and the user application programs.

Queue Manager
The Queue Manager module is an integral part of PBS. The term queue
refers to a list of pending print or batch requests. The term entry
describes a request on a queue. Normally, PBS adds new entries to the
end or tail of a queue. PBS processes an entry when it reaches the
front or head of the queue.
PBS creates an entry on a queue in response to a user request for
print or batch services. The entry remains on a queue until its
requested job is completed, or until it is explicitly deleted by an
operator or user. PBS assigns a priority to every queue entry which
establishes its position on the queue relative to other entries. For
example, PBS inserts a high-priority entry in the queue ahead of
existing lower priority entries instead of at the end.

9-3

Managing Print/Batch Services
The system file PBS$:PBS.SYS contains all the queue definitions. You
define a new queue with the INITIALIZE/QUEUE command. Once you define
a queue it remains in the file until it is explicitly deleted.
You
delete a queue with the DELETE/QUEUE command.

Queue Types
PBS uses two types of queues:
o

The PRINT command creates entries in a print queue

Batch

The SUBMIT command creates entries in a batch queue

You can define several queues for each type, but each queue can only
have a single type associated with it. Note that once you define a
queue as a print or batch queue, you cannot change its type.

Queue Names
Every queue must have a unique name. This name can consist of I to 9
characters from the set A-Z, 0-9, $, and ,and must begin with an
alphanumeric character. PBS always forces lowercase characters in
queue names to uppercase.
You need a trailing colon when you include
the queue name in an entry specification. Otherwise, the colon is
optional.
Queue names must be unique, regardless of type.
For example, if you
define a print queue named SYSTEM, then you cannot also define a batch
queue with the name SYSTEM.

Default Queues
You can define one default print queue and one default batch queue.
When a user issues a PRINT or SUBMIT command and does not specify a
queue name, PBS places the request on the appropriate default queue.
You can change default queues at any time by using the SET QUEUE
command. As distributed, PBS defines the default print queue
SYS$PRINT and the default batch queue SYS$BATCH.
You do not have to define default queues.
However, if you do not, a
user must specify the queue on which to place each print or batch
request.

9-4

Managing print/Batch Services
Assigning Servers to Queues
Once you define a queue, users can submit requests to be placed on
that queue.
You must also indicate which servers are to process
requests on that queue. You can define servers with the
INITIALIZE/SERVER command.
In the simplest configuration, you assign each queue to a single
server, and you do not assign two queues to the same server.
Figure
9-1 shows this configuration.

+----------+
I

Queue LQ I

+-------------+
----?

+----------+
+----------+
I Queue BQ I
+- - - - - - - - - -+
Figure 9-1:

I Server LPO:

+-------------+
~

+-------------+
I Server BAO: I
+- - - - - - - - - - - --+

One-to-One Configuration

The one-to-one configuration is useful when users need to have their
print requests printed on a particular printer or their batch request
processed by a specific batch server.
In such cases, you can choose
the queue name to match its assigned server's name, such as print
queue LPO: or batch queue BAO:.
It may be useful to assign more than one server to a queue, an option
which is useful when multiple devices with the same characteristics
exist.
For example, at a site with two letter-quality printers (for
example, KBll: and KB12:), you could define one print queue named LQ
and assign it to servers controlling each device.
Figure 9-2 shows
this configuration.

+--------------+
I Server KBll: I
+--------------+

+----------+
I Queue LQ I
+----------+

+--------------+
I Server KB12: I
+--------------+
Figure 9-2:

One-to-Many Configuration

The one-to-many configuration is useful when one class of devices can
process similar jobs. When a user places a print request on the queue
9-5

Managing Print/Batch Services
LQ, the first available server assigned to that queue processes the
request.
To balance the use of servers, PBS uses a round-robin method
to determine which available server to use next.
That is, in deciding
which server to use next, the most recently used server is the last
one PBS examines.
You can also assign more than one queue to the same server.
For
example, suppose a batch queue named BAD is currently assigned to
batch server BAD:, while batch queue BAI is assigned to batch server
BAl:.
If you notice that queue BAD has many entries waiting for
processing while queue BAI is empty, you can assign queue BAD to both
servers.
Figure 9-3 shows this configuration.

+-----------+
I Queue BAD I
+-----------+

----~)

+-------------+
I S e r v e r BA 0 : I
+-------------+

+-----------+

+-------------+
I Queue BAI I
I Server BAI: I
+-----------+ ----~) +-------------+
Figure 9-3:

Many-to-One Configuration

Note that in Figure 9-3 entries on queue BAI are only processed by
server BAl:, while entries on queue BAD are processed by either
server.
The combination of a one-to-many and a many-to-one configuration is a
many-to-many configuration.
That is, you can assign any set of queues
to any set of servers.
Thus, you have complete control over
allocating resources (servers) for processing queue entries.
You can use SHOW QUEUE/FULL command to display the servers assigned to
a queue.
You can use the SHOW SERVER/FULL command to display the
queues assigned to a server.
The ASSIGN/QUEUE and DEASSIGN/QUEUE
commands let you assign and deassign each queue's servers.

Queue Priorities
You assign each queue a maximum priority and default priority in the
range I to 255.
The maximum priority of a queue defines the maximum
priority a user can specify when issuing a request for that queue.
The default priority of a queue defines the priority to assign to a
request issued with no explicit priority specified. These two
parameters let you set up queues so PBS processes all requests in one
queue ahead of all requests in another queue.

9-6

Managing print/Batch Services
Users with EXQTA privilege can submit PRINT or BATCH requests with a
priority greater than the queue's maximum.
See the section
"processing Requests" for more information on processing order.

Opening and Closing Queues
Normally, a queue accepts entries even if no servers are available to
process_the requests. At times, you may want to prevent PBS from
placing any additional requests on a queue.
This is called closing a
queue; existing entries continue moving toward the front of the queue
(if there are servers available to process them), but the queue does
not accept additional entries. You can close a queue with the
CLOSE/QUEUE command.
If a user issues a PRINT or SUBMIT command for a closed queue, PBS
returns an error and rejects the request. You can open a closed queue
with the OPEN/QUEUE command.

Starting and Stopping Queues
Entries move toward the head of a queue, and PBS processes them when
they reach the queue's head. You can stop a queue with the STOP/QUEUE
command to prevent any entries on the queue from being processed.
Users can place additional entries on a stopped queue, but PBS does
not process them. Any entries currently in process when you stop a
queue are not affected. You can restart a stopped queue with the
START/QUEUE command.
Note the distinction between stopping a queue and stopping a server
assigned to a queue. When you stop a queue, PBS does not process any
pending entries on that queue. When you stop a server, PBS does not
process any pending entries on any queue assigned to that server. The
two cases are similar in the one-to-one configuration. However, the
two cases are quite different in a many-to-many configuration.
For example, if you assign both queues A and B to the same server,
stopping queue A does not cause that server to become idle, since
processing can still continue from queue B. However, if you stop the
server, then processing stops on both queues.

Processing Requests
In the one-to-one or one-to-many configurations, PBS always processes
the entry at the head of the queue.
However, when you assign multiple
queues to the same server, there is no implied order to processing
entries; all of the entries at the front of each queue are, by
9-7

Managing Print/Batch Services
definition, eligible for servicing. PBS resolves any conflicts that
occur by checking the priority and age of the entries.
When several entries are waiting for processing, PBS chooses the one
with the highest priority.
If several entries have the same priority,
then PBS selects the one with the earliest entry date and time.
Before PBS can process an entry, it must be in the READY state.
means that the entry:

This

Is not in an AFTER state. An entry can be given an 'after'
date and time value, which prevents the entry from being
processed until the specified date and time has passed.

Is not in a HOLD state. An entry can also be prevented from
being processed until an operator or the entry's owner
explicitly releases it.

Once an entry is in the READY state, PBS processes it as soon as all
of the following conditions are met:
o

PBS cannot process any other READY entries of the same type
but with a higher priority

PBS cannot process any other READY entries of the same type
and the same priority but with an earlier entry date and time

A server assigned to the entry's queue is available to
process the entry.
That is, the server is not currently
processing any other entry.

For print entries, a server's controlled device is not
currently allocated or opened by any other job on the system.

For print entries, at least one device is available with the
entry's required forms installed on it.

For batch entries, at least one pseudo keyboard is currently
available (that is, not allocated to or opened by another job
on the system).

When all of the above conditions are met, PBS starts a print or batch
job on behalf of the entry.
PBS changes the entry's state to STARTED,
and records the name of the server processing the job in the entry.
Use the SHOW ENTRY/FULL command to display this information when an
entry is in process.
Since PBS always processes print entries and batch entries by
different servers, entries of a different type never compete with each
other for processing.

9-8

Managing Print/Batch Services
Accessing Entries on a Queue
Users must also be able to locate entries in a queue.
two methods for accessing entries in queues:

PBS provides

Entry number -- When PBS adds an entry to a queue as a result
of the PRINT or SUBMIT command, PBS assigns a unique entry
number to it.
Entry numbers are unique across all queues,
regardless of type.
Thus, each entry has a specific number
assigned to it, whether it is in a print queue or a batch
queue.
PBS uses this number to record the entry in its queue
file.

Entry specification -- You can also access an entry by
identifying some or all of the following attributes:
The name of the entry's queue
The PPN of the entry's owner
The name of the entry
These attributes are permanently established when you create
the entry; they cannot be modified once PBS adds the entry to
its queue.
Several commands (for example, DELETE ENTRY and SHOW ENTRY)
let you ideptify an entry or group of entries by specifying
an entry specification parameter with the command.
The
format of an entry specification is:
queue-name: [PPN]entry-name

Unlike entry numbers, entry specifications do not uniquely identify an
entry; several entries with the same attributes can exist at the same
time.
Therefore, be careful when using entry specifications with
commands to modify or delete queue entries, since doing so can cause
multiple entries to be modified or deleted inadvertently.

Job Limits for Queues
Each queue has maximum and default limits associated with it.
For
print jobs, you can define page limits; for batch jobs, you can define
both CPU and elapsed time limits.
The servers assigned to the queue
enforce these limits.
This arrangement lets you set up queues that do not accept requests
requiring many resources.
For example, you could assign a low maximum
page limit to a queue assigned to a server controlling a slow-speed
printer, thus restricting requests to relatively small print jobs.
9-9

Managing Print/Batch Services

Similarly, a queue assigned to a batch. server running jobs at low
priority could accept requests that include large CPU or elapsed time
limits.
Users with EXQTA privilege can submit print or batch requests with job
limits that exceed the maximum limits defined for the queues on which
their requests are placed.

Print Servers

Each print server must have a unique name. PBS always names print
servers after the devices they control (for example, server LPO:
controls device _LPO:, server KB4S: controls device _KB4S:, and so
on) .
Some commands permit wildcard print server names.
o

*: -- Means all servers

LP*:

Means all LP-type servers

KB*:

Means all KB-type servers

For example:

PBS does not allow the question mark character (ASCII 63) in print
server names.
PBS associates each entry on a print queue with a form name. This
name identifies the form that you must install on a printer before the
server controlling that device can start the job. If you issue a
PRINT command and do not specify a form name, PBS assigns the form set
up as the default for the queue on which the request is placed.

Device Ownership

A print server can retain ownership of its controlled device and
prevent other jobs on the system from accessing the device. Use the
/NOSHAREABLE qualifier with the INITIALIZE/SERVER and SET SERVER
commands to indicate that the server's device should be permanently
allocated to PBS. A device so allocated will be deallocated under any
of the following conditions:
o

An operator changes the server's NOSHAREABLE setting to
SHAREABLE

The device's server is deleted

PBS is shut down

9-10

Managing print/Batch Services
When PBS restarts after a shut down, it attempts to allocate any
device whose server is marked as NOSHAREABLE.
PBS continues to try
allocating any device that is in use by another job on the system.
PBS places such a server in the DEVICE-WAIT state indicating that the
server is trying to gain access to the device.
If you initialize a server with NOSHAREABLE and its device is not
available, PBS displays a warning message.
PBS allocates the device
as soon as it becomes available.
/SHAREABLE indicates that the device can be shared by other jobs on
the system, and PBS only allocates it when the server starts
processing a request.
The default is /SHAREABLE.

Job Copies and File Copies
Each print job consists of one or more files to be printed.
Qualifiers are available with the PRINT command to specify the number
of job or file copies to be printed.
The /JOB COUNT=n command qualifier specifies the number of copies of
the job to be printed.
The /COPIES=n qualifier specifies the number
of copies of a file to be printed.
The default for both qualifiers is
one copy.
If a print job consists of a single file, then the two qualifiers
produce the same result except for the header pages (see the next
section "Header Pages").
However, if a print job consists of more
than one file, then the qualifiers produce different results.
For example, if you issue the following command:
PRINT/COPIES=2 FILE1.LST,FILE2.LST
The order of the job output is:
Job header (1 of 1)
File header (1 of 2)
FILE1.LST
File header (2 of 2)
FILE1.LST
File header (1 of 2)
FILE2.LST
File header (2 of 2)
FILE2.LST

9-11

Managing Print/Batch Services
But, if you issue the following command:
PRINT/JOB_COUNT=2 FILE1.LST,FILE2.LST
The order of the job output is:
Job header (1 of 2)
File header (1 of 1)
FILE1.LST
File header (1 of 1)
FILE2.LST
Job header (2 of 2)
File header (1 of 1)
FILE1.LST
File header (1 of 1)
FILE2.LST

Header Pages
You can print special job and file header pages to identify the start
of a job or a file within a stack of listings. Header pages include
large block letters to help you locate the beginning of job and file
copies.
You can control the number of job or file header pages
printed by the JOB PAGES=n and FLAG PAGES=n attributes of the printer
form.
Header pages consist of fields printed in single-height and
double-height block letters and other information printed in six
repeated lines.
Three lines are printed at the top and bottom of each
header page.
These lines help you find the start of each job in a
large listing.
The job header pages contain the following information:
o

Owner's account name -- This field is in single-height block
letters

Entry name -- This field is in double-height block letters

Owner's PPN -- This field is in single-height block letters

The three lines at the top and bottom of each job header page
contain the following:

Current date
Current time
Entry entry-spec

9-12

Managing Print/Batch Services
Copy nnn of mmm
Printer device-name
Form form-name

Installation-name
The file header pages contain the following information:
o

Device name and PPN -- This field is in single-height block
letters

Filename -- This field is in double-height block letters

File type -- This field is in double-height block letters

Owner's PPN -- This field is in single-height block letters

The three lines at the top and bottom of each file header
page contain the following:
Current date
Current time
File filespec
Copy nnn of mmm
Printer device-name
Form form-name

Installation-name

Page Limits
You can limit each print job to a specified maximum number of pages.
The page limit can be:
o

User specified

The default for the queue

Unlimited

9 - .13

Managing Print/Batch Services
Print servers count the number of pages they print. When a print job
exceeds its page limit, PBS prints an error on the last page of the
job listing and terminates the job. Note that header pages do not
count toward a job page limit.
When the user specifies the page limit, the value can not exceed the
maximum limit for the queue. If the user does not specify the page
limit, PBS uses the default limit of the queue.

Control Characters and Escape Sequences
Some printers, such as the LNOl and LA2xx, can understand escape
sequences. In some cases, the action taken in response to a
particular escape sequence is device dependent. Therefore, you must
route files that contain escape sequences to the correct server. This
is best done by providing queues that assign jobs only to single
servers or to servers that all serve the same type of printer.
The /CONTROLS qualifier, provided with the INITIALIZE/SERVER and SET
SERVER commands, indicates how the server should process control
characters and escape sequences:
o

/CONTROLS -- Indicates that the server sends control
characters and escape sequences to its controlled device.
The action taken is dependent on the device's handling of
such characters. The print server does not update the form's
current horizontal and vertical position when sending such
characters to the printer.

/CONTROLS=UP ARROW -- Indicates that the server translates
control characters to an 'up arrow' format, consisting of a
circumflex (A) character followed by a printable character
that identifies the control character, and that the server
translates the ESC character to the dollar sign ($), causing
PBS to display all of the characters in the escape sequence.
This is the default.

/NOCONTROLS -- Indicates that the server does not process
control characters or escape sequences. PBS discards any
such characters.
Note
Control characters and escape sequences can cause a
print server to lose track of line and page
positioning. This is because print servers do not
know what action is taken by the printer in response
to such characters. Normally, form feed characters
correct positioning within a file unless the server.
9-14

Managing Print/Batch Services
is doing simulated form feed handling. In such
cases, it may be necessary manually to adjust the
printer alignment to correct positioning errors
introduced by control characters and escape
sequences.
DIGITAL recommends that servers processing control characters always
use forms with the NOSIMULATE attribute, to prevent positioning errors
between jobs.

Eight-Bit Characters
PBS passes eight-bit characters unchanged to printers designated as
eight-bit devices with the SET PRINTER/EIGHT_BIT or SET
TERMINAL/EIGHT_BIT commands.

Batch Servers
Batch servers are named BAn:, where n is a unit number in the range
0-31. Some commands permit wildcard batch server names, for example:
o

*: -- Means all servers

BA*: -- Means all batch servers

PBS does not allow the question mark character (ASCII 63) in bat~h
server names.

Executing Command Files
Batch servers use the DCL command file processor on pseudo keyboards
to create the batch job environment. Batch servers execute a batch
job by creating a temporary command file. This file:
o

Opens a log file (unless the you specify /NOLOG_FILE with the
SUBMIT command)

Initializes error handling

Executes LOGIN.COM files

Executes the individual user command files

PBS passes the parameters you specify with the SUBMIT command only to
the first command file in the batch job.

9-15

Managing Print/Batch Services
Because batch servers create their own command procedure to execut~
the user's command files, the number of levels of command nesting that
PBS allows is one less than the levels available when executing
command procedures at the interactive level (see RSTS/E Guide to
Writing Command Procedures).
The exit status that PBS reports in the batch log file is the status
of the most severe error occurring in the job, not just the last one.
The format of the exit status display is:
Exit status = <message>
Table 9-2 lists the possible exit status messages.
Table 9·2:

PBS Batch Job Exit Status Messages

+- - - - - - - - - - - - - - - - - _. - - -+- - - - - - - - - _. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message

Meaning

+- - - - - - - - - - - - - - - - - _ .. - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. - - - - - - --+

Entry cannot execute I Job could not be created
Entry deleted

Error

I
I Job was deleted during processing
I

An error message occurred in the job

Exceeded CPU limit

Job exceeded the CPU time limit

Exceeded time limit

Job exceeded the time limit

Severe error

A severe error message occurred in the job

Success

No errors or warnings encounted

Unknown

Job logged out or was killed (exit status
is unknown)

Warning

A warning message occurred in the job

+- - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

CPU and Time Limits
Batch servers also monitor their batch job to enforce CPU and time
limits and determine when the job is done. An active batch server
examines its controlled job's CPU and time usage approximately every
30 seconds. If either value exceeds the allowable limit for the batch
job, PBS terminates the job immediately. If you specify a log file
with the SUBMIT command, PBS includes an error message in the log
describing the reason for the job termination.

9-16

Managing print/Batch Services
Managing Forms for PBS
Printer forms are the physical paper you install in a line printer.
In some cases, forms are standard stock paper as normally used for
printing program listings.
In other cases, forms are customized,
preprinted paper, such as checks or invoices.
PBS identifies each form by name. A form name consists of 1-9
characters from the set {A-Z, 0-9, $, _}.
PBS converts lowercase
characters to uppercase.
When you define a print server, you can specify the name for the form
currently installed on the server's print device.
Each form
definition includes the form handling characteristics for the printer
to which it applies. A Forms Definition File (FDF), maintains all the
form characteristics for each server in PBS (see the next section).
When you issue a print request, you can specify the form name required
using the /FORMS=form-name qualifier.
If you do not include a form
name, PBS assigns the queue's default form name to the print request.
PBS verifies that the specified form name is in the FDF.
If not, PBS
returns an error and rejects the print request.
Before PBS can start a print request, a server assigned to the
request's queue must be available with the required form installed on
its printer.
If not, the request remains READY until you change forms
or until you assign a new server with the correct form name to the
request's queue.
You can define the same form name differently for different printers.
For example, NORMAL can have different characteristics for the printer
LPO: from those it has for LPl:. Generally, the physical dimensions
of a form page (length and width) should remain the same from one
printer to another, but the attributes that describe how a printer
should handle the form may be different, depending on the device.

Forms Attributes
PBS defines the following attributes for printer forms:
o

Form name -- A unique I
the form.

to 9 character name that identifies

Server name -- The name of the server to which the form
definition applies.
This can refer to a single server or
multiple servers of the same type (LP or KB).

Length -- The physical length of a form page, measured in
lines of print.
This value can be in the range 1 to 255.

9-17

Managing Print/Batch Services
o

Width -- The width of a form page, measured in characters
printed across the page. The val~e can be in the range 1 to
255.

Job pages -- The number of header pages to print at the start
of each new print job. The value can be in the range 0 to
127.

Flag pages -- The number of flag pages to print at the start
of each new file within a print job. The value can be in the
range 0 to 127.

Form-feed handling -- Depending on the form page length and
the hardware capability, the printer mayor may not be able
to correctly handle FF characters that position the form page
at the top of the next page. If not, then the server must
simulate the form feed action by outputting the proper number
of line feeds to reach the top of the next page.

Bottom margin
The number of lines to skip at the bottom of
each page. The value must be less than the form page length.

The Forms Definition File
PBS provides a Forms Definition File (FDF) to maintain all printer
form definitions. This file is a standard ASCII stream file, allowing
anyone with write access to add, delete, and update the form
definitions using a standard text editor. FDF defines form attributes
by using keywords (for example, LENGTH=66), to simplify definitions
further.
PBS treats lines beginning with an exclamation point (!) as comment
lines. Thus, you can include descriptions in the definitions file.
PBS also supports continuation lines. If a definition ends with a
hyphen (-), the definition is continued on the next line similar to
the DCL command line continuation feature (see the RSTS/E System
User's Guide).

Note
If a line to be continued contains a comment, the
hyphen must precede the comment (see the next section
"Forms Definition Keywords").
Blank lines are ignored. So, you can include blank
lines where you want to separate definitions for
readability.

9-18

Managing Print/Batch Services
The name of the Forms Definition File supplied on the RSTS/E
distribution kit is PBS$:FORMS.SYS. As distributed, this file
contains two definitions for the form named NORMAL: one is for
LP-class printers and one is for KB-class printers.
The file has a
protection code of <40>, allowing any user on the system to read it;
however, only users with WWRITE privilege can write to it.
The default print queue SYS$PRINT is initially set up with NORMAL as
its default form name. After you install PBS, you can change any of
these parameters. You can add additional definitions to the file as
needed.
The order of form definitions in the FDF is significant.
If you
initialize a print queue and you do not include the /FORMS qualifier,
PBS defaults to the first form definition.
Similarly, if you define a
print server and do not include the /FORMS qualifier, PBS defaults to
the first form definition that applies to that server.
PBS accesses the FDF for the following reasons:
o

When you include a /FORMS qualifier with the PRINT command,
PBS searches the FDF for the specified form name.

When you issue a INITIALIZE/SERVER or SET SERVER command that
includes a /FORMS qualifier for a print server, PBS searches
the FDF for the definition of the specified form name.

When you issue a INITIALIZE/QUEUE or SET QUEUE command that
includes a /FORMS qualifier for a print queue, PBS searches
the FDF for the specified form name.

If the form name is not found, then PBS returns an error and rejects
the request.

Forms Definition Keywords
A forms definition consists of:
o

Form name

Server name

One or more keywords that describe the form attributes

You can use spaces or tabs to separate the keywords within a form
definition. Any standard RSTS/E line terminator (CR, LF, FF)
terminates each definition.
For example, the definition of the

9-19

Managing Print/Batch Services
default form named NORMAL for LP-class servers is:
NORMAL= LP*:LENGTH=66WIDTH=132JOB_PAGES=2FLAG PAGES=2BOTTOM MARGIN=6NOSIMULATE

form NORMAL for all LP servers
66 lines per page
132 columns per line
2 job header pages
2 flag header pages
6 blank lines at the bottom of each page
hardware top-of-form

If a forms definition applies to a particular server, or class of
servers, the server name follows the form name and is separated from
it by an equal sign. The format of the server name in a forms
definition is:
form-name[=server-name[:]]
PBS does not permit embedded spaces or tabs between the form name and
the server name.
The server-name identifies the server(s) to which this definition
applies. If the definition only applies to a single server, then
specify the explicit server name. If the definition applies to a
class of servers (all LP or all KB devices), then specify
form-name= LP*: or form-name= KB*: (wildcard unit number). If the
definition-applies to all print servers, then specify form-name=*: or
omit this field from the definition. The default is all servers.
Note
If a server belongs to more than one definition for
the same form, place definitions that apply to
specific servers before any that apply to a general
class of servers. PBS searches the FDF sequentially
until it finds the first occurrence of the requested
form name with a matching server name.
You can abbreviate all forms definition keywords to their first two
characters. Note that the form name always appears first in the
definition and has no associated keyword. All other fields in the
definition can be in any order. If a keyword is not included in a
form definition, then PBS uses the keyword's default value.
You can include the following keywords in a forms definition:
LENGTH=n
Indicates the number of lines per printed page for the specified
form. The value n can range from 1 to 255. The default length
is 66; this is standard spacing for an 8-1/2 by II-inch form with
vertical spacing of 6 lines per inch.

9-20

Managing Print/Batch Services
Note
Some devices that print on single-sheet forms
cannot print on all physical lines of the form.
For example, the LNOI prints a maximum of 60
lines per page.
In such cases, the form length
should be set to the device's maximum print
lines; not the form's physical size.
WIDTH=n
Indicates the maximum number of characters that can appear in a
printed line for the specified form.
The value n can range from
1 to 255. The default width is 132.
The WIDTH value determines where a printed line will be truncated
(if the file is being printed with the /TRUNCATE qualifier of the
DCL PRINT command in effect) or wrapped around to a new line (if
the file is being printed with the /NOTRUNCATE qualifier in
effect).
[NO]SIMULATE
Determines whether PBS should, on encountering a FF character or
reaching the end of a page, send a FF character directly to the
device (NOSIMULATE), or simulate the form feed by transmitting
the proper number of line-feed characters (SIMULATE). The
default is SIMULATE.
JOB PAGES=n
Defines the number of job header pages to be printed at the
beginning of each job listing.
The value n can range from 0 to
127. Job header pages display informat~on about the job (job
name, PPN, and so forth), printed in large block letters.
Job
header pages make it easy to separate job listings.
The default
is JOB PAGES=l.
,

FLAG PAGES=n
Defines the number of file header pages to be printed at the
beginning of each file listing.
The value of n can range from 0
to 127. File header pages display information about the file
(file name, PPN, and so forth), printed in large block letters.
File header pages make it easy to separate printouts of files
within a job. The default is FLAG_PAGES=l.
Note
You can suppr~ss the printing of file header
pages by including the /NOFLAG_PAGES qualifier
with the file to be printed.
9-21

Managing Print/Batch Services
BOTTOM MARGIN=n
Defines the number of lines to skip at the bottom of each page of
the form.
The bottom margin value cannot exceed the form's
length. The default is BOTTOM_MARGIN=6.
Printers that use single-sheet paper (for example, the LNOl)
automatically end a page and start a new page when it reaches its
maximum print line.
Forms definitions for these devices should
normally specify BOTTOM_MARGIN=O.
Note
You can suppress the printing of the bottom
margin by including the /NOFEED qualifier with
the file to be printed.
This has no effect when
BOTTOM MARGIN=O.

Changing Forms
Whenever you need to change forms on a printer under the control of
PBS, perform the following steps:
1.

Use the STOP/SERVER/JOB END command to stop the server at the
end of any current print job.

Use the SHOW SERVER command to confirm that the server is
stopped and is not processing any print job.

Install the'desired form in the printer.

Use the SET SERVER/FORMS=form-name command to assign a new
form name to the server. Use the SHOW SERVER/FULL command to
inspect the new form attributes (LENGTH, WIDTH, and so on) as
needed.

Use the START/SERVER command to restart the server. When you
issue this command, PBS routes any jobs that are waiting for
the new form to be installed to the server.

Note that you can issue a SET SERVER/FORMS=form-name command without
stopping the server, although DIGITAL does not recommended this unless
the new form definition applies to the same physical form currently
installed in the printer. Any print job in progress at the time its
print server is assigned a new form name is not affected.
The form
name last assigned to the server determines the next job to be
processed by the server. Use the SHOW SERVER command to display the
name of the form most recently assigned.

9-22

Managing print/Batch Services
If you modify the FDF to change the definition of a form name which is
currently assigned to a server, you must perform a form change (using
the same form name) to cause the new form definition to be read from
the FDF.

Multiple Jobs
PBS consists of a single primary job and, optionally, one or more
secondary jobs, depending on the number and use of concurrent print or
PBS is designed to provide a compact and efficient
batch servers.
package across all of its jobs. This section provides some background
information on how the PBS package makes use of multiple jobs.

The Primary Job
Whenever you issue the START/QUEUE/MANAGER command, PBS creates its
primary job. This job runs detached.
It contains the queue manager
module and is always present when the package is running.
The primary job contains two print and two batch server slots. A slot
refers to a sub-job in the PBS job that provides print or batch
servic~s.
If the number of slots available to support the active
print or batch servers in the primary job is insufficient, PBS creates
secondary jobs.

Secondary Jobs
PBS creates secondary jobs when there are no print or batch server
slots available in the primary job to process a waiting request. PBS
attempts to activate only as many servers as necessary, depending on
the number of waiting requests ready to run, available devices, and so
on.
Each secondary job contains three print server slots and four
batch server slots.
When PBS starts, only the primary job is running. When a pending
request is ready to start, the queue manager first determines if a
slot is available on which to activate a server for the r~quest.
If
the primary job contains no available server slots of the correct type
(print or batch), then PBS automatically creates a secondary job.
Unlike the primary job, a secondary job remains present only while one
or more of its server slots is allocated to a server. Once all the
server slots in a secondary job become free (that is, there are no
active servers in the job) PBS automatically removes the job from the

9-23

Managing Print/Batch Services
system.
It is possible for several PBS secondary jobs to be present
on the system at the same time, depending on the number of active
servers that you require at any time.
Note
PBS secondary jobs contain only print and batch
server slots; they do not contain a queue manager
module.
Based on the configuration of PBS, the primary job is sufficient to
handle two concurrent print jobs and two concurrent batch jobs.
If
more than two print or two batch servers are active at the same time,
then PBS creates at least one secondary job. Each secondary job
allows for three more print jobs and four more batch jobs to be
started.
Thus, if your printing volume causes six print devices to be
active concurrently, you need a total of three RSTS/E jobs (one
primary and two secondary) to run PBS.
PBS uses an "idle job timer" to determine when to remove a secondary
job from the system. The idle job timer is set to five minutes.
That
is, PBS removes a secondary job when all of its servers have been idle
for five minutes.
This time is sufficient for PBS to start a server's
next job without having to recreate a secondary job.
PBS creates secondary jobs as needed, as long as job slots are
available on the system.
If none are available, then no secondary job
is created, and PBS waits until either a job slot becomes available,
or an existing server slot becomes free.
You can limit the number of secondary jobs required by controlling the
number of servers that can process requests. You can do this by
deassigning or stopping one or more servers.
Idle servers that are
stopped or not assigned to any queue cannot process a request.
Thus,
they do not require a server slot.

Descriptions of PBS's DCL Commands
The following sections contain descriptions of the PBS commands that
require special privileges.
See the RSTS/E System User's Guide for
descriptions of PRINT, SUBMIT, DELETE ENTRY, SET ENTRY, SHOW ENTRY,
and SHOW QUEUE commands.

9-24

ASSIGN/QUEUE
ASSIGN/QUEUE Command
The ASSIGN/QUEUE command assigns a server to a queue. Server
assignments are cumulative; any server assigned to a queue is added to
the set of assigned servers. A server named BAn: can only be assigned
to a batch queue. Likewise, a server named LPn: or KBn: can only be
assigned to a print queue. ASSIGN/QUEUE command requires PBSCTL
privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I

I
I
I

I
I Prompts
I
I Queue: queue-name[:]
I Server: server-name[:]

I
I
I
I
I

I ASSIGN/QUEUE queue-name[:] server-name[:]

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
queue-name[:]
Specifies the name of the queue to be assigned.
does not permit wildcard queue names.

This command

server-name[:]
Specifies the server to assign to the queue.
not permit wildcard server names.

9-25

This command does

CLOSE/QUEUE
CLOSE/QUEUE Command

This command closes a queue; that is, it prevents any additional
requests from being placed on the queue.
If the specified queue is
not open, RSTS/E ignores this command. CLOSE/QUEUE requires PBSCTL
privilege.
-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - --r

I
I Format
I
I CLOSE/QUEUE queue-name[:]
I
I Prompts
I
I Queue: queue-name[:]

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---r
Command Parameters
queue-name[:]
Specifies the name of the queue to be closed.
not permit wildcard queue names.

9-26

This command does

DEASSIGN/QUEUE
DEASSIGN/QUEUE Command
The DEASSIGN/QUEUE command deassigns a server from a queue. Any job
already started on a deassigned server is not affected. However, no
additional jobs are started on the server from the queue.
DEASSIGN/QUEUE requires PBSCTL privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I DEASSIGN/QUEUE queue-name[:] server-name[:],
I
I Command Qualifiers
Defaults
I
I /ALL
See Discussion
I
I prompts
I
I Queue: queue-name[:]
I Server: server-name[:]

I
I
I
I
I
I
I
I
I
I
I
I
I

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
queue-name[:]
Specifies the name of the queue to be deassigned.
does not permit wildcard queue names.

This command

server-name[:]
Specifies the name of the server to be deassigned.
This
parameter overrides the /ALL qualifier.
This command does not
permit wildcard server names.
Command Qualifiers
/ALL
Indicates that all servers currently assigned to the queue should
be deassigned.
If you specify /ALL, PBS does not prompt for a
server name.
If you specify a server name, PBS ignores /ALL.

9-27

DELETE/QUEUE
DELETE/QUEUE Command
The DELETE/QUEU~ command deletes a queue.
If you issue DELETE/QUEUE
for a queue that has one or more entries, RSTS/E marks the queue for
deletion and closes it. PBS deletes the queue as soon as it becomes
empty. You can still display queues marked for deletion using the
SHOW QUEUE command. DELETE/QUEUE automatically deassigns all servers
from the deleted queue. DELETE/QUEUE requires SWCFG privilege.

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --r

I
I Format
I
I

DELETE/QUEUE queue-name[:]

I
I

Prompts

I
I Queue: queue-name[:]
-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --r
Command Parameters
queue-name[:]
Specifies the name of the queue to be deleted.
not permit wildcard queue names.

9-28

This command does

DELETE/SERVER
DELETE/SERVER Command
This command deletes a print or batch server.
If the server you
specifY'is currently processing a job when you issue the command,
RSTS/E marks it for deletion.
PBS deletes the server when it becomes
idle.
DELETE/SERVER automatically deassigns the deleted server from
all assigned queues.
DELETE/SERVER requires SWCFG privilege.
+ - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

I
I Format
I
I DELETE/SERVER server-name[:]
I
I prompts
I
I Server: server-name[:]

I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
server-name[~]

Specifies the name of the server to be deleted.
does not permit wildcard server names.

9-29

This command

INITIALIZE/QUEUE
INITIALIZE/QUEUE Command
INITIALIZE/QUEUE defines a print or batch queue and establishes its
initial properties. Use the SHOW QUEUE command to display the queues
that are currently defined.
See the RSTS/E System User's Guide for
details on the SHOW QUEUE command.
When you initialize a queue, you also define its characteristics.
Print and batch queues have different characteristics. You can modify
any of a queue's characteristics later by using the SET QUEUE command.
Note that certain qualifiers for this command apply only to print
queues, while others apply only to batch queues. An error results if
you include both types of qualifiers in the same.command. PBS uses
the following criteria to determine whether a queue should be
initialized as a print queue or a batch queue:
o

If you give a /PRINT or /BATCH qualifier, it determines the
queue's type.

If you do not give either /PRINT or /BATCH, but you specify a
print queue only qualifier (for example, /PAGE_LIMIT) or a
batch queue only qualifier (for example, /CPU_LIMIT), that
qualifier determines the queue's type.

If you do not meet either of the previous conditions, the
queue's type defaults to a print queue.

PBS retains queue information in the queue file when the package is
shut down.
The system uses this information to automatically
reinitialize queues when it restarts the package.
INITIALIZE/QUEUE
requires SWCFG privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I
I Format
I
I INITIALIZE/QUEUE queue-name[:]
I
I Command Qualifiers
I
I /BATCH
I /CLOSE
I /CPU_LIMIT=(MAXIMUM=a,DEFAULT=b)
I /DEFAULT
I /FORMS[=form-name]
I /PAGE_LIMIT= (MAXIMUM=a ,DEFAULT=b)
I /PRINT
I /PRIORITY=(MAXIMUM=a,DEFAULT=b)
I /PRIVILEGES=("priv[, ... ]")

9-30

Defaults
See Discussion
See Discussion
See Discussion
See Discussion
See Discussion
See Discussion
. See Discussion
See Discussion
/PRIVILEGES=NONE

INITIALIZE/QUEUE
~

- - -- - - --- - - - - - - - -- -- - - - - --- - - - ----- -- -- - - - - - - - -- - --- - ---Command Qualifiers (Cont.)

Defaults (Cont.)

/TIME_LIMIT=(MAXIMUM=a,DEFAULT=b)

See Discussion

Prompts
Queue: queue-name[:]

I
I
I
I
I
I
I
I

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

Command Parameters
queue-name[:]
Specifies the name of the queue to be initialized.
does not permit wildcard queue names.

This command

Command Quailifiers
IBATCH
Indicates that the queue is a batch queue, and only accepts
entries with the SUBMIT command.
/CLOSE
Indicates that the queue should initially be closed, preventing
any PRINT or SUBMIT entries from being entered on the queue.
By
default, PBS initializes the queue as open.
/CPU_LIMIT= (MAXIMUM=a ,DEFAULT=b)
/CPU_LIMIT=n
Batch queues only.
Indicates the maximum and default CPU time
limits (in minutes) for each command file processed in a batch
job started from this queue. The maximum CPU limit is the
largest value that you can specify when issuing a request for the
queue.
The default CPU limit is the value that PBS assigns to a
request that had no limit specified. The keyword UNLIMITED
indicates that PBS does not enforce a CPU limit.
If you do not
specify the MAXIMUM argument, then PBS uses MAXIMUM=UNLIMITED.
If you do not specify the DEFAULT argument, then PBS uses the
maximum CPU limit as the default limit.
If you use the /CPU_LIMIT=n form, then PBS uses the value you
specify for both the maximum and default limits.
If you specify
a numeric argument, it must be in the range 1 to 65,535. The
default CPU limit cannot exceed the maximum CPU limit.
If you issue a SUBMIT command without an explicit CPU'limit, then
PBS uses the queue default CPU limit. When you issue a SUBMIT
9-31

INITIALIZE/QUEUE
command, you can specify a CPU limit up to, but not exceeding the
queue maximum CPU limit.
/DEFAULT
Indicates that the queue should be marked as the default queue
for its type (print or batch). You can define only one print
queue and one batch queue as a default queue.
If you specify /DEFAULT, then the queue becomes the default queue
for its type, and any queue currently defined as the default
queue of the same type no longer serves as the default queue.
By
default, PBS does not mark the queue as a default queue.
/FORMS=form-name
Print queues only.
Indicates if a default form name is defined
for the queue.
If you specify /FORMS=form-name, then PBS defines
the name you specify as the default form name for the queue.
If
you issue a PRINT command without a /FORMS qualifier, then the
queue's default form name is the first form name found in the
FDF.
/PAGE_LIMIT= (MAXIMUM=a, DEFAULT=b)
/PAGE_LIMIT=n
Print queues only.
Indicates the maximum and default page limits
for each file printed as part of a print job started from this
queue.
The maximum page limit is the largest value that you can
specify when issuing a PRINT request for this queue. The default
page limit is the value assigned to a request for this queue that
had no limit specified.
The keyword UNLIMITED indicates that no page limit is enforced.
If you do not specify the MAXIMUM argument, then PBS uses
MAXIMUM=UNLIMITED.
If you do not specify the DEFAULT argument,
then PBS uses the maximum page limit as the default limit.
If you use the /PAGE LIMIT=n form, then PBS uses the value you
specify for both the-maximum and default limits.
If you specify
a numeric argument, it must be in the range 1 to 4,294,967,295.
The default page limit can not exceed the maximum page limit.
If you issue a PRINT command without an explicit page limit, then
PBS uses the queue default page limit. When you issue a PRINT
command, you can specify a page limit up to, but not exceeding,
the maximum page limit of the queue.
/PRINT
Indicates that the queue is a print queue and only accepts
entries from the PRINT command.
9-32

INITIALIZE/QUEUE
/PRIORITY= (MAXIMUM=a ,DEFAULT=b)
/PRIORITY=a
Defines the maximum and default priorities for the queue, in the
range I to 255.
If you do not specify the MAXIMUM argument, then
PBS uses 255.
If you do not specify the DEFAULT argument, then
PBS uses the maximum value as the default priority.
If you use
the /PRIORITY=a form, then PBS uses the value you specify for
both the maximum and default priority.
The default priority
cannot exceed the maximum priority.
/PRIVILEGES=(priv, ... )
Specifies the set of privileges required for a user to place
entries on the queue. A user who issues a PRINT or SUBMIT
command must have all of the queue's privileges for the request
to be accepted.
By default, a user does not need any privileges
to place an entry on the queue.
The argument can be any of the RSTS/E privilege keywords, plus
the keywords ALL and NONE.
The /PRIVILEGES=ALL qualifier assigns
all defined privileges to the queue; /PRIVILEGES=NONE assigns no
privileges to the queue.
Note that you can specify any privilege
name with /PRIVILEGES, even those that you do not possess.
/TIME_LIMIT=(MAXIMUM=a,DEFAULT=b)
/TIME_LIMIT=n
Batch queues only.
Indicates the maximum and default elapsed
time limits (in minutes) for each command file processed in a
batch job started from this queue.
The maximum time limit is the
largest value that you can specify when issuing a request for
this queue.
The default time limit is the value that PBS assigns
to a request that had no limit specified.
The keyword UNLIMITED indicates that PBS does not enforce a time
limit.
If you do not specify the MAXIMUM argument, then PBS uses
MAXIMUM=UNLIMITED.
If you do not specify the DEFAULT argument,
then PBS uses the maximum time limit as the default limit.
If
you use the /TIMELIMIT=n form, then PBS uses the value you
specify for both the maximum and default limits.
If you specify
a numeric argument, it must be in the range I to 65,535.
The
default time limit cannot exceed the maximum time limit of the
queue.
If you issue a SUBMIT command without an explicit time limit,
then PBS uses the queue default time limit. When you issue a
SUBMIT command, you can specify a time limit up to, but not
exceeding, the maximum time limit of the queue.

9-33

INITIALIZE/SERVER
INITIALIZE/SERVER Command
The INITIALIZE/SERVER command defines a print or batch server.
Use
the SHOW SERVER command to display the servers that are currently
defined.
See the RSTS/E System User's Guide for details on the SHOW
SERVER command.
When you initialize a server, you also define its characteristic$.
Print and batch servers have different characteristics. You can
modify any of a server's characteristics later by using the SET SERVER
command.
PBS retains the server information' in the queue file when the package
is shut down.
The system uses this server information to initialize
servers automatically when you restart the package. This eliminates
the need to reinitialize servers each time you start PBS.
INITIALIZE/SERVER requires SWCFG privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
INITIALIZE/SERVER server-name[:]
Command Qualifiers

Defaults

/[NO]CONTROLS[=UP_ARROW]
/FORMS[=form-name]
/PRIORITY=n
/RUN_BURST=n
/[NO] SHAREABLE

See Discussion
See Discussion
See Discussion
See Discussion
/SHAREABLE

Prompts

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

Server: server-name[:]
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Parameters
server-name[:]
Specifies the name of the server to be initialized.
does not permit wildcard server names.

This command

Command Qualifiers
/[NO]CONTROLS[=UP_ARROW]
Print servers only.
Indicates how print servers should process
control characters and escape sequences.
The default is
/CONTROLS=UP_ARROW (see the section "Control Characters and
Escape Sequences").
9-34

INITIALIZE/SERVER
You must have PBSCTL privilege to specify this qualifier.
/FORMS[=form-name]
Print servers only.
Identifies the form currently installed on
the printer. The server only prints requests with this form
name.
PBS displays an error message if the form name does not
exist in the FDF.
If you omit this qualifier, then PBS initializes the printer with
the first form definition found in the FDF that applies to the
specified print server. You can later issue a SET SERVER command
to assign a different form to the server.
/PRIORITY=n
Batch servers only.
Indicates the priority at which to run
command procedures controlled by this server. RSTS/E permits any
value in the range -120 to +120; however, batch jobs cannot
exceed the priority of the PBS primary job. RSTS/E rounds the
priority down to a multiple of 8. The default is -8.
You must have TUNE privilege to specify this qualifier.

Batch servers only.
Indicates the run burst to assign to any
command procedures controlled by this server. RSTS/E permits any
value in the range 1 to 127. The default is 6.
/[NO] SHAREABLE
Specifies if the server's device should be shared with other jobs
on the system.
The default is /SHAREABLE.
If you specify /NOSHAREABLE, RSTS/E immediately allocates the
device to the PBS job, thereby preventing other jobs on the
system from gaining access to the device.
For batch servers,
RSTS/E allocates the next available pseudo keyboard to the
server.
The device remains allocated to the PBS job until you
delete its server (with the DELETE/SERVER command), or you shut
down PBS (with the STOP/QUEUE/MANAGER command).
You get a
warning message if you specify /NOSHAREABLE for a device
currently allocated to another job on the system; PBS allocates
the device when it becomes available.
If you specify /SHAREABLE, PBS allocates the device only when the
server is active.
The device is available to other jobs when the
server is idle.
The default is /SHAREABLE.

9-35

OPEN/QUEUE
OPEN/QUEUE Command
The OPEN/QUEUE command opens a queue for additional requests after it
has been closed.
If the specified queue is already open, RSTS/E
ignores this command. OPEN/QUEUE requires PBSCTL privilege.

- --- - -- - -- - ----- -------- - - -- - - - - - ----- - --- - - - ------ - - - - - - -~
I
I
I Format
I
I
I
I OPEN/QUEUE queue-name[:]
I
I
I
I Prompts
I
I
I
I Queue: queue-name[:]
I

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Command Parameters
queue-name[:]
Specifies the name of the queue to be opened.
permit wildcard queue names.

9-36

This command does not

SET QUEUE
SET QUEUE Command
The SET QUEUE command modifies the characteristics of one or more
queues.
Changing a queue's characteristic does not affect entries
already on the queue.
SET QUEUE requires PBSCTL privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SET QUEUE queue-name[:]
I
I Command Qualifiers
I
I
I

Defaults

/ALL
/BATCH
/CPU_LIMIT=(MAXIMUM=a,DEFAULT=b)
/[NO]DEFAULT
/FORMS[=form-name]
/PAGE_LIMIT=(MAXIMUM=a,DEFAULT=b)
/PRINT
/PRIORITY=(MAXIMUM=a,DEFAULT=b)
/PRIVILEGES=(" pr iv[, ... ]")
/TIME_LIMIT= (MAXIMUM=a ,DEFAULT=b)

I
I
I
I
I
I
I
I
I
I Prompts
I
I Queue: queue-name[:]

See Discussion
See Discussion
Attributes are unchanged
Attributes are unchanged
Attributes are unchanged
Attributes are unchanged
See Discussion
Attributes are unchanged
Attributes are unchanged
Attributes are unchanged

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
queue-name[:]
Specifies the name of the queue to be modified.
This command
permits wildcard queue names.
The rules for selecting queues
when using wildcards are:
o

If you specify /PRINT or a print queue only qualifier, then
PBS only selects print queues.

If you specify/BATCH or a batch queue only qualifier, then
PBS only selects batch queues.

If neither of the above rules are true, then PBS selects any
queue.

9-37

SET QUEUE
Command Qualifiers
/ALL
Indicates that all queues should be modified.
If you specify
/ALL, PBS omits the queue name prompt and uses the queue name
If you specify a queue name, PBS ignores this qualifier.

/BATCH
Indicates that only batch queues should be modified. When you
use /ALL with this qualifier, PBS modifies all batch queues.
/CPU_LIMIT=(MAXIMUM=a,DEFAULT=b)
/CPU_LIMIT=n
Batch queues only.
Indicates the maximum and default CPU time
limits (in minutes) for each command file processed in a batch
job started from this queue.
The maximum CPU limit is the
largest value that you can specify when issuing a request for the
queue.
The default CPU limit is the value that PBS assigns to a
request that had no limit specified.
The keyword UNLIMITED indicates that PBS does not enforce a CPU
limit.
If you do not specify the MAXIMUM argument, then PBS does
not change the maximum CPU limit.
If you do not specify the
DEFAULT argument, then PBS does not change the default CPU limit.
If you use the /CPU_LIMIT=n form, then PBS use the value you
specify for both the maximum and default limits.
If you specify
a numeric argument, it must be in the range I to 65,535.
The
default CPU limit cannot exceed the maximum CPU limit.
If you do not specify this qualifier, then PBS does not change
the queue's current default and maximum values.
/[NO]DEFAULT
Indicates whether the queue should serve as the default queue for
its type.
If you specify /DEFAULT, then PBS marks the queue as
the default queue for its type, and any queue already defined as
the defa~lt queue is no longer marked as being the default queue.
If you specify /NODEFAULT, then the queue is no longer marked as
being the default queue for its type.
PBS does not return an
error if you specify /NODEFAULT for a queue that is not currently
marked as the default queue.
If you do not specify this qualifier, then any current default
queue is not affected.

9-38

SET QUEUE
/FORMS=form-name
Print queues only.
Indicates if a default form name is defined
for the queue.
If you specify /FORMS=form-name, then the name
you specify becomes the default for the queue and replaces any
previous default form.
If you do not specify this qualifier, then the queue's current
default form name is not changed.
/PAGE_LIJ1IT=(MAXIMUM=a,DEFAULT=b)
/PAGE_LIMIT=n
Print queues only.
Indicates the maximum and default page limit
for each file printed as part of a print job started from this
queue.
The maximum page limit is the largest value that you can
specify when issuing a request for this queue.
The default page
limit is the value that PBS assigns to a request for this queue
that had no limit specified.
The keyword UNLIMITED indicates that no page limit is enforced.
If you do not specify the MAXIMUM argument, then PBS does not
change the maximum page limit.
If you do not specify the DEFAULT
argument, then PBS does not change the default page limit.
If
you use the /PAGE LIMIT=n form, then PBS uses the value you
specify for both the maximum and default limits.
If you specify
a numeric argument, it must be in the range 1 to 4,294,967,295.
The default page limit can not exceed the maximum page limit.
If you dot not specify this qualifier, then the queue's current
default and maximum values are not changed.
/PRINT
Indicates that only print queues should be modified. When you
use /ALL with this qualifier, PBS modifies all print queues.
/PRIORITY=(MAXIMUM=a,DEFAULT=b)
/PRIORITY=a
Defines the maximum and default priorities for the queue, in the
range I to 255.
If you do not specify the MAXIMUM argument, then
PBS does not change the current maximum priority.
If you do not
specify the DEFAULT argument, then PBS does not change the
current defauit priority.
If you use the /PRIORITY=a form, then
PBS uses the value you specify for both the maximum and default
priorities.
The default priority cannot exceed the maximum
priority.
If you do not specify this qualifier, then the queue's current
default and maximum values are not changed.

9-39

SET QUEUE
/PRIVILEGES=(priv, ... )
Specifies the set of privileges required for a user to place
entries on the queue. A user who issues a PRINT or SUBMIT
command must have all of the queue's privileges for the request
to be accepted. PBS accepts any of the RSTS/E keywords, plus the
keywords ALL and NONE.
The /PRIVILEGES=ALL qualifier assigns all defined privileges to
the queue; /PRIVILEGES=NONE assigns no privileges to the queue.
Note that you can specify any privilege name with /PRIVILEGES,
even those that you do not possess.
If you specify this qualifier, PBS replaces the queue's current
privileges with those in the argument list.
If you do not
specify this qualifier, the queue's current privileges are
unchanged.
/TIME_LIMIT=(MAXIMUM=a,DEFAULT=b)
/TIME_LIMIT=n
Batch queues only.
Indicates the maximum and default elapsed
time limits (in minutes) for each command file processed in a
batch job started from this queue.
The maximum time limit is the
largest value that a user can specify when issuing a request for
this queue.
The default time limit is the value PBS assigns to a
request that had no limit specified.
The keyword UNLIMITED indicates that PBS does not enforce a time
limit.
If you do not specify the MAXIMUM argument, then PBS does
not change the current maximum time limit.
If you do not specify
the DEFAULT argument, then PBS does not change the current
default time limit.
If you use the /TIME LIMIT=n form, theri PBS
use the value you specify for both the maximum and default
limits.
If you specify a numeric argument, it ,must be in the
range 1 to 65,535. The default time limit cannot exceed the
maximum time limit.
If you do not specify thi's qualifier, then the queue's current
default and maximum values (if any) are not changed.

9-40

SET SERVER
SET SERVER Command
The SET SERVER command changes the characteristics of one or more
servers. Use this command to change forms for print servers.
SET
SERVER requires PBSCTL privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I
I

Format
SET SERVER server-name[:]
Command Qualifiers

Defaults

/ALL
/BATCH
/[NO]CONTROLS[=UP_ARROW]
/FORMS[=form-name]
/PRINT
/PRIORITY[=n]
/RUN_BURST[=n]
/[NO] SHAREABLE

See Discussion
See Discussion
Attributes are unchanged
Attributes are unchanged
See Discussion
Attributes are unchanged
Attributes are unchanged
Attributes are unchanged

Prompts
Server: server-name[:]
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
server-name[:]
Specifies the name of the server to be modified.
permits wildcard server names.

This command

Command Qualifiers
/ALL
Indicates that all servers should be modified.
If you specify
/ALL, PBS omits the server name prompt.
If you specify a server
name, PBS ignores this qualifier.
/BATCH
Indicates that only batch servers should be modified. When you
use /ALL with this qualifier, PBS modifies all batch servers.

9-41

SET SERVER
![NO]CONTROLS[=UP_ARROW]
Print servers only.
Indicates how print servers should process
control characters and escape sequences.
If you do not specify
this qualifier, then PBS does not change the current CONTROLS
setting.
/FORMS=form-name
Print servers only.
Indicates the name of the form installed on
the printer.
The server only prints requests with the same form
name. PBS returns an error if the form name you specify for the
device does not exist in the FDF.
If you do not specify this qualifier, then the server's current
form is not changed.
/PRINT
~ndicates that only print servers are to be modified.
When you
use /ALL with this qualifier, PBS modifies all print servers.

/PRIORITY[=n]
Batch servers only.
Indicates the priority at which to run
command procedures controlled by this server.
This value cannot
exceed the priority of the PBS primary job. PBS accepts any
value in the range -120 to +120.
PBS rounds the value down to a
multiple of 8.
If you do not specify an argument /PRIORITY, the server's
priority is set to -8.
If you do not specify this qualifier,
then the batch server's priority is not changed.
/RUN_BURST[=n]
Batch servers only.
Indicates the run burst to assign to any
command procedures controlled by this server.
PBS accepts any
value· in the range 1 to 127.
If you do not specify an argument with /RUN_BURST, the server's
run burst is set 6.
If you do not specify this qualifier, then
the batch server's run burst is not changed.

9-42

SET SERVER

/[NO] SHAREABLE
Indicates if the device should be made shareable with other jobs
on the system.
If you specify /NOSHAREABLE, then PBS immediately allocates the
device, preventing other jobs from accessing the device.
The
device is deallocated whenever you delete the server (with the
DELETE/SERVER command) or shut down PBS (with the
STOP/QUEUE/MANAGER command).
If you specify /NOSHAREABLE and the
device is not currently available, PBS displays a warning message
and allocates the device as soon as it becomes available.
/SHAREABLE indicates that the device can be shared by other jobs
on the system and PBS only allocates it when the server is
active.
If you do not specify this qualifier, then the [NO]SHAREABLE
characteristic is not changed.

9-43

SHOW SERVER
SHOW SERVER Command
The SHOW SERVER command displays the status of one or more servers in
PBS.
The display includes information about the server's
characteristics, its current status, and the queues assigned to the
server.
The SHOW SERVER command requires no privileges.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
SHOW SERVER [server-name[:]]
Command Qualifiers

Defaults

/ALL
/ALL
/BATCH
/BRIEF
/BRIEF
/FULL
/PRINT
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
server-name[ :]
Specifies the name of the server to be displayed.
specify a server name, all servers are displayed.
does not permit wildcard server names.

If you do not
This command

Command Qualifiers
/ALL
Specifies that all servers are to be displayed. /ALL is the
default if no server name is specified.
If a server name is
specified, this qualifier is ignored.
/BATCH
Specifies that only batch servers are to be displayed.
/BRIEF
Specifies a brief display.
It is the default.
includes the following information:
o

The brief display

On-line or Off-line -- Print servers only.
Indicates the
current status of the server's print device.
Note that PBS
does not detect an off-line device until it attempts to print
on it; all devices are assumed to be on-line when PBS first

9-44

SHOW SERVER
starts.
KB-type printers are considered off-line when an
XOFF (CTRL/S) characters causes the device to stall for an
extended period of time.
o

Active -- Indicates that the server is currently processing a
request.

Idle -- Indicates that the server is not currently processing
a request.

Stopped -- Indicates that the server is currently stopped and
will not accept any new requests.
The server mayor may not
be active.

Job-wait -- Indicates that PBS is unable to create a
secondary job because no job slots are currently available.
PBS will keep trying to create the second job until it
succeeds.

Device-wait -- Indicates that PBS is unable to allocate a
device because the device is not available.
For print
servers, device-wait means that the printer controlled by the
server is allocated to or opened by another job.
For batch
servers, device-wait means that no pseudo-keyboards are
currently available.
PBS will keep trying to allocate the
device until it succeeds.

Shareable or Non-shareable -- Print servers only.
Shareable
means that the print device is available to other jobs on the
system when it is not in use by the server. Non-shareable
means that the print device is permanently allocated to the
server.

Form name -- Print servers only.
Indicates the name of the
forms currently installed, or "No forms" if no forms are
installed.

/FULL
Specifies a full display.
The full display includes all of the
information in the brief display, and also includes the following
information:
o

Current entry
If the server is active, PBS displays the
entry number and entry spec of the current entry.

Assigned queues -- PBS displays a list of the queues which
can route requests to the server.

/PRINT
Specifies that only printer servers are to be displayed.,
9 - 4.5

START/QUEUE
START/QUEUE Command
The START/QUEUE command starts a queue that was stopped with the
STOP/QUEUE command. Once you start a queue, PBS processes waiting
entries on the queue.
If you already started the specified queue, PBS'
ignores this command.
START/QUEUE requires PBSCTL privilege.
~

- -- - --- - -- - --- - - - - ----- -- ----- - - - - -- - - - - - - - ----- - - - - -- - -

--~

Format
START/QUEUE queue-name[:]
Prompts
Queue: queue-name[:]
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ':" - - - - - - - - - - --~
Command Parameters
queue-name[:]
Specifies the name of the queue to be started.
not permit wildcard queue names.

9-46

This command does

START/QUEUE/MANAGER
START/QUEUE/MANAGER Command
The START/QUEUE/MANAGER command starts PBS.
it:

Following this procedure,

Creates the PBS primary job as a detached job running in the
user's account.
RSTS/E initializes the job's priority and
run burst according to the package configuration parameters.

Compresses the PBS system file by removing any records that
are marked as deleted.
(This step reduces the overall size
of the file.) During this step, if RSTS/E finds an entry with
status STARTED, it retains the entry, placing it on HOLD.
This can happen if RSTS/E restarts the package after a system
crash.

Loads all queue definitions into memory from the PBS system
file.

Loads all server definitions into memory from the PBS system
file.
If a print server device is not a valid device on the
system, PBS marks the server DISABLED.

Assigns servers to queues based on the assignment information
maintained in the PBS system file.

Attempts to permanently allocate a device for any server
marked as NOSHAREABLE in its server's definition.
If the
allocation fails because the device is currently in use, PBS
marks the server DEVICE-WAIT and attempts to allocate the
device periodically until the allocation succeeds.

Confirms start-up has successfully completed by displaying a
message.

The start-up process can take from a few seconds to several minutes,
depending on the number of pending requests in the queue.
Most users
include the START/QUEUE/MANAGER command in their system start-up
command file so the time required for PBS start-up is added to normal
system start-up time.
START/QUEUE/MANAGER requires PBSCTL privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format

I START/QUEUE/MANAGER

I Command Qualifiers
I
I /PRIORITY=n
I /RUN_BURST=n

Defaults

/PRIORITY=-8
/RUN_BURST=6
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
9-47

START/QUEUE/MANAGER
Command Qualifiers
/PRIORITY=n
Specifies the priority of the detached PBS job and any secondary
jobs that PBS creates. Value must be in the range -120 to +120;
with any value specified rounded down to a multiple of 8. The
default is -8.

Specifies the run burst of the detached PBS job and any secondary
jobs that PBS creates. Value must be in the range 1 to 127. The
default is 6.

9-48

START/SERVER
START/SERVER Command
This command restarts a server that was stopped with the STOP/SERVER
command.
If the server has a stalled job when you issue the command,
the command either resumes the job or terminates it, depending on the
qualifiers you use.
For print servers, the job can be resumed at a specified page of the
current file copy.
PBS ignores this command if the specified server
is already started.
For batch servers, PBS releases the controlled
batch job from its held state.
START/SERVER requires PBSCTL
privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
START/SERVER server-name[:]
Command Qualifiers

Defaults

/BACKSPACE[=n]
/FORWARDSPACE[=n]
/NEXT_JOB
/PAGE=n
/RESTART
/TOP_OF_FILE

See
See
See
See
See
See

Discussion
Discussion
Discussion
Discussion
Discussion
Discussion

This command

Command Qualifiers
/BACKSPACE[=n]
Print servers only.
Indicates that printing should resume n
pages back in the current file listing.
If you do not include an
argument, then printing resumes one page before the current page.
If you specify an argument that extends beyond the beginning of
the file, then printing resumes at the beginning of the current
file copy.
PBS ignores this qualifier if the specified server is idle.
9-49

START/SERVER

/FORWARDSPACE[=n]
Print servers only.
Indicates that printing should resume n
pages forward in the current file listing.
If you do not include
an argument, printing resumes one page after the current page.
If you specify an argument that extends beyond the end of the
current file, printing resumes at the next file copy, if any.
PBS ignores this qualifier if the specified server is idle.

Indicates that the current job should be aborted and printing or
batch processing should resume at the next job, if any.
PBS ignores this qualifier if the specified server is idle.
/PAGE=n
Print servers only.
Indicates that printing should resume at
page n in the current file listing.
If you specify an argument
that extends beyond the end of the file, printing resumes at the
next file copy, if any. A value of 1 indicates the first page of
the file; PBS does not include header pages in the count.
PBS ignores this qualifier if the specified server is idle.
/RESTART
Print servers only.
Indicates that printing should resume at the
beginning of the current job copy.
If you submit the job with a
/JOB_COUNT qualifier argument larger than one, PBS only starts
the current job copy.
PBS ignores this qualifier if the specified server is idle.

Print servers only.
Indicates that printing should resume at the
beginning of the current file copy.
If the file being printed
was submitted with a /COPIES qualifier argument larger than one,
PBS only starts the current file copy.
PBS ignores this qualifier if the specified server is idle.

9-50

STOP QUEUE
STOP QUEUE Command
The STOP/QUEUE command stops a queue; that is, PBS prevents any
pending requests on the queue from being processed. Any requests that
are currently being processed are not affected.
STOP/QUEUE requires
PBseTL privilege.
PBS ignores this command if the specified queue is already stopped.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
STOP/QUEUE queue-name[:]
prompts
Queue: queue-name[:]
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
queue-name[:]
Specifies the name of the queue to be stopped.
not permit wildcard queue names.

9-51

This command does

STOP/QUEUE/MANAGER
STOP/QUEUE/MANAGER Command
The STOP/QUEUE/MANAGER command lets you shut down PBS, either
immediately (causing all currently active jobs to be terminated) or
when all servers become idle.
STOP/QUEUE/MANAGER requires PBSCTL
privilege.
You can shut down PBS in two ways:
o

As part of normal system shutdown. The SHUTUP program
includes a phase for automatically shutting down PBS, either
immediately or when all print or batch jobs currently in
progress complete.

Manually, using the STOP/QUEUE/MANAGER command.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I
I Format
I
I STOP/QUEUE/MANAGER
I
I Command Qualifiers
I
I /[NO]ABORT

Defaults

I
I
I
I
I
I
I
I

/NOABORT
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~+
Command Qualifiers
/[NO]ABORT

Indicates whether any print or batch jobs currently running
should be aborted before shutting down PBS. Use /ABORT to shut
down PBS immediately; use /NOABORT to let all currently running
print or batch jobs complete. The default is /NOABORT.

9-52

STOP/SERVER
STOP/SERVER Command
This command stops a print or batch server. The action taken depends
on whether the server is currently active or not.
For queues that are
assigned to only one server, stopping the server is equivalent to
stopping the queue.
For queues that are assigned to more than one
server, stopping one server does not prevent requests from being
routed to other active servers.
STOP/SERVER requires PBSCTL
privilege.
If you issue a STOP/SERVER command for a server that is not currently
processing a request, no additional requests are routed to that
server.
However, if you issue a STOP/SERVER command for a server that
is currently processing a request, the following action is taken
depending on the server:
o

Batch servers -- If you specify the /JOB END qualifier, PBS
lets the current batch job complete before stopping the
server. Otherwise, the server suspends the batch job by
assigning it a priority of -128. The server then waits until
PBS issues a START/SERVER command to either resume or
terminate the batch job.

Print servers -- If you specify the /PAGE_END, /FILE_END or
/JOB_END qualifier, PBS does not stop the server until it
completes the current page, file copy, or job copy.
If the
copy is the final copy of the job, PBS lets the job finish
before it stops the server.
If you do not specify any of the
qualifiers, PBS stops the server immediately.
When PBS directs the server to stop, the server stops sending
data to the printer. However, system buffers continue to be
printed on the device until they become empty. This is
necessary to prevent PBS from losing proper page positioning
on the printer.
The server then waits until you issue a
START/SERVER command to either resume or terminate the print
job.

9-53

STOP/SERVER

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I STOP/SERVER server-name[:]
I
I Command Qualifiers
I
I /FILE_END
I /JOB_END
I /PAGE_END
I

Defaults
See Discussion
See Discussion
See Discussion

Prompts

Server: server-name[:]
+ - - - ~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
server-name[:]
Identifies the server to be stopped.
permit wildcard server names.

This command does not

Command Qualifiers

Print servers only.
Indicates that printing should stop after
the current file copy is finished printing.
Note that this qualifier conflicts with /JOB_END and /PAGE_END.

For print servers, indicates that printing should stop after the
device has finished printing the current job.
For batch servers,
indicates that the server should stop when the current batch job
completes.
Note that this qualifier conflicts with /FILE_END and /PAGE_END.

Print servers only.
Indicates that printing should stop at the
end of the current page.
Note that this qualifier conflicts with /FILE_END and /JOB_END.

9-54

Chapter 10
Managing System Errors

The RSTS/E monitor automatically logs both hardware and system level
software errors.
To gain the full advantages of this error detection
capability, you must use the programs in the System Error package.
These programs fall into three main categories:
o

Extraction and retention of system errors

Extraction and retention of system errors not yet retrieved
at the time of a system crash

Compilation and formatting of saved system errors

When the monitor detects an error, routines save critical
error-related data and send a message to the ERRCPY program.
The
system invokes ERRCPY, which then retrieves the saved data, performs
minimal error message processing, and stores the error information in
a specially formatted disk file (ERRLOG.FIL).
Because RSTS/E limits
the number of messages that may be queued to ERRCPY, it should be run
at a higher priority than most jobs to prevent the loss of valuable
diagnostic information. A separate program, ERRINT, initializes and
validates the error logging file to minimize the size of ERRCPY.
Normally, you run ERRINT at the beginning of system start-up to start
ERRCPY.
When a system crash occurs and the system crash dump facility is
enabled, the monitor preserves the contents of certain critical parts
of the system in the system file [0,1] CRASH.SYS.
Run the ANALYS
program immediately following the recovery from a system crash to
extract and format key information from the crash file.
Normally,
this is done by the system start-up command file.
One of the
functions ANALYS performs is the creation of a separate error logging
file (by default, ERRCRS.FIL) containing errors that were not
processed by ERRCPY at the time of the crash and an ERRDIS report for
the errors.

10-1

Managing System Errors
Use of the Error Logging Programs: ERRINT and ERRCPY
The system program ERRCPY reads error-related information stored in
the monitor part of memory and writes it to a special disk file called
ERRLOG.FIL.
The error file initialization and validation program
(ERRINT) starts the ERRCPY program.
ERRINT performs various file
checking or generation functions and chains to ERRCPY.
You must make
sure the commands are in the START. COM file to start ERRINT (thus,
ERRCPY) and that ERRCPY is active during time-sharing operations.

Error Logging Initialization: ERRINT
When the RSTS/E system starts up, DCL executes commands in the
START.COM command file.
The following command starts ERRINT:
$ RUN ERROR$:$ERRINT

When the system executes the previous command, the ERRINT program
tries to locate the error file ERRLOG.FIL.
If it finds the file,
ERRINT checks certain critical control information in the file.
If
this information is invalid, ERRINT renames the file ERRLOG.TMP,
generates and initializes a new ERRLOG.FIL, and issues an
informational message:
Error File was found to be Invalid
Error File was generated and Invalid File renamed ERRLOG.TMP
If ERRINT does not find ERRLOG.FIL, it generates and initializes the
file.
Two other commands, corresponding to responses to ERRINT questions,
must also be present in the command file.
The two ERRINT dialogue
questions for which you must include responses are:
Change size to < 100 >?
Utilize crash file output (YES/NO) <NO>?
Once ERRINT validates or creates ERRLOG.FIL, it prints a message
telling you what percentage of the file has been used.
For example:
ERRLOG file is 8% full
ERRINT also prints a question that includes (in angle brackets) the
maximum number of blocks allowed for the file:
Change size to < 100 >?
You can accept the c~rrent size of the file (originally 100 blocks) or
change the maximum size if you want.
You can also specify an optional

10-2

Managing System Errors
switch, /LOCK.
If you include /LOCK in your response, ERRCPY runs
nonswappable.
The default is that ERRCPY can be swapped out.
Note
You should only specify /LOCK if your system has over
128K words of memory.
The program then asks if you want to append the contents of the
special error crash file ERRCRS.FIL to the contents of ERRLOG.FIL in
the question:
utilize crash file output (YES/NO) <NO>?
If you answer YES, ERRINT tries to find the file and add its contents
to the end of the main error logging file.
If it cannot find the
error crash file, ERRINT ignores the command and continues.
After it finishes processing all of its functions, ERRINT detaches and
chains to ERRCPY. At this point, the terminal on which ERRINT started
is free for other use.
The ERRINT program is usually located in the error library account
ERROR$.
To run ERRINT from this account, type RUN ERROR$:ERRINT and
press RETURN.
If you
You can run ERRINT only if ERRCPY is not currently running.
start up ERRINT while ERRCPY is running, then when ERRINT chains to
ERRCPY, the new version of ERRCPY hibernates and displays the message:
?Name or account now exists at line 1025 in IERRCPy"
Note that the version of ERRCPY that was running in a detached state
on the system continues to run.

Examples of ERRINT Dialogue
An example of the ERRINT dialogue follows:
$ run error$:errint<RET>
ERRINT V9.0 RSTS V9.0 EDERE
ERRLOG file is 8% full
Change size to < 100 >? 120<RET>
Utilize crash file output (YES/NO) <NO>? NO<RET>
Detaching
In this example, a valid error log file exists, has a maximum length
of 100 blocks, and is 8% full.
If you change the maximum size to 120
blocks but decide not to add the special ANALYS error log file to the
ERRINT error log file, the program detaches and chains to ERRCPY.
10-3

Managing System Errors
In the next example, ERRINT finds an invalid error log file, renames
the invalid file to ERRLOG.TMP, creates a new file, leaves the maximum
size at 100 blocks, and attaches the special error log file ERRCRS.FIL
to the error log file ERRLOG.FIL. Note that the 2% full message
indicates a file containing only control information; this is the
state of a newly generated error log file:
$ run error$:errint<RET>
ERRINT V9.0 RSTS V9.0 EDERE
Error file was found to be invalid
New file was generated and invalid file renamed ERRLOG.TMP
ERRLOG file is 2% full
Change size to < 100 >?<RET>
Utilize crash file output (YES/NO) <NO>? YES<RET>
Detaching

Error Logging: ERRCPY
You can start the ERRCPY program only by running ERRINT.
ERRCPY runs
detached, processes incoming error messages, and writes each message
as a variable-length record to a nonspanned sequential file
(ERRLOG.FIL). When its message queue is empty, ERRCPY enters the
receiver sleep state and may be swapped out.
The monitor queues messages to ERRCPY regardless of the presence or
absence of ERRCPY.
(If ERRCPY is not running, the messages are simply
left waiting, up to a limit of 40.) The first message the monitor
queues on start-up is always a "power fail/start up" message. On
receiving a special error message from the SHUTUP program, ERRCPY logs
the message, closes the error file, and kills itself.

Displaying Errors: ERRDIS
The error display program ERRDIS provides you with a convenient method
of displaying previously logged errors.
ERRDIS has four functions:
o

Provides a summary report by error type and unit number
(where applicable) of all errors logged to the error file

Provides a detailed report of one or all error types logged
between any two user-selected date and time pairs

10 -4

Managing System Errors
o

Zeros the contents of the error file following the generation
of a report

Provides a list of potentially bad disk blocks

ERROIS consists of two modules: ERROIS and ERROET.
The first module
performs the first and third functions.
To perform the other
functions, ERROIS chains to ERROET; control returns to ERROIS when
ERROET finishes processing.

Running ERRDIS
You can run the ERROIS program by typing:
$ RUN ERROR$:ERROIS
ERROIS V9.0 RSTS v9.0 EOERE
After ERROIS prints header information, you select optional modes of
operation by means of an interactive dialogue.
In the dialogue
description shown in Table 10-1, prompts are numbered for reference.
An answer enclosed in angle brackets «» indicates the default
response; select the default by pressing RETURN in response to a
program prompt.
You can abbreviate most responses with two
characters.
Optional characters are enclosed in square brackets [];
for example, HE[LP).
Table 10-1:

ERROIS Dialogue Explanation

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

i Step

Prompt and Description

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I
I
I
I
I
I

ERRDIS V9.0 RSTS V9.0 EOERE
ERROIS prints an identification line.

Input File <[O,3]ERRLOG.FIL>?
Enter a file specification for ERROIS to process. The file
must be formatted as an error logging file.

Output to <KB:ERROIS.OUT>?
Enter a file specification to which ERROIS should send the
report.

I
I
I

10-5

Managing System Errors
Table 10-1:

ERRDIS Dialogue Explanation (Cont.)

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I Step I

Prompt and Description

+- - - - - -+- - - _. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

He[lp], Ba[d Blocks], Su[mmary] or Fu[ll] Report <Summary>?
Select one of four possible reports:
o

He[lp]. Prints help a file, followed by a list of
mnemonics ,corresponding to all possible error types.

Ba[d Blocks]. Outputs a report of possible bad blocks
detected from the disk errors logged in the input file
entered in Step 2.

Su[mmary]. Outputs a report of the number of errors
detected for each error type and for each unit number
within a specific error type. The next dialogue step
is 10.

Fu[ll]. Outputs a report of the detailed contents of
each selected error record in the error file.
Selection of a specific record depends on the answers
to steps 5 through 9 in the ERRDIS dialogue.

Specific Error Type <All>?
Enter a two-character mnemonic identifying the specific
error type that you want ERRDIS to process. The default
answer selects all error types. Note that if you select
All, you may also attach the /NOTAPE switch if you want
magnetic tape errors to be omitted from the error listing.

Starting Date <First Error>?
Enter the date of the earliest error that you want ERRDIS
to process. The format is dd-mmm-yy. The default answer is
the date of the first error in the error log file. If you
press RETURN to select the default, the next step is 8.

Starting Time <First Error>?
Enter the time of the earliest error that you want ERRDIS
to process. The format is hh:mm. The default is the time of
the first error in the error log file on the selected date.

Ending Date <Last Error>?
Enter the date of the latest error that you want ERRDIS to
process. The format is dd-mmm-yy. The default is the date
of the last error in the error log file. If you select the
default, then the next dialogue step is 11.

10-6

Managing System Errors
Table 10-1:

ERRDIS Dialogue Explanation (Cont.)

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Step I
Prompt and Description

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
9
Ending Time <Last Error>?
I
Enter the time of the latest error that you want ERROIS to
process. The format is hh:mm. The default is the time of
the last error in the error log file on the selected ending
date. The next dialogue step is 11.

List Bad Blocks (Yes/No) <No>?
Press RETURN (or type No) if you do not want ERRors to
generate a list of possible bad blocks following the
summary report. Type Yes if you want a list of bad blocks.

Zero Error File upon completion (Yes/No) <No>?
Type Yes to have ERRors zero the previously specified error
log file after it successfully generates the desired
report. (You must type all three characters of Yes to zero
the file.)

+- - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

After you finish the dialogue, ERRors:
o

Processes the selected error records

Formats and generates the selected report

Zeros the error log file (if requested in step 11 of Table
10-1)

Returns to step 2 of Table 10-1.

At that point, you can enter CTRL/Z in response to any question to
return the terminal to the keyboard monitor prompt.

Help Report
The Help report prints information on the use of the ERROIS program
and then prints a list of the error mnemonics other programs use.
After you run ERROIS and select the Help report, the program prints
the Help text.

Summary Report
A summary report at the end of this section supplies general
information on all errors logged.
The first two columns list the
10-7

Managing System Errors
two-character error mnemonic and full error description.
The TOTAL
REC/LOG column lists the total errors received by the ERRCPY program
and the total it stored in the error file.
These two totals may
differ due to the limits on:
o

Th~

The size of the error file

number of errors that may be logged

The UNIT NUMBERS column lists the total number of errors generated by
each device on a controller.
The CONTROLLER ERRORS column indicates how many of the errors logged
under TOTAL REC/LOG are controller errors, as opposed to unit errors.
(Controller errors apply to the controller itself, while unit errors
apply to a specific unit being controlled.) If N/A appears under
CONTROLLER ERRORS, that means that ERRDIS is not keeping track of
CONTROLLER ERRORS for that particular ERROR CODE-DESCRIPTION.
The asterisk (*) next to 239/100 indicates that MM, under the ERROR
CODE-DESCRIPTION column, has exceeded the maximum number of errors
(100) that the Error Package logs for that particular error type.
After you run ERRDIS and select the SUMMARY report, the program prints
the summary as follows.
Note that the Summary Report now contains
fewer blank lines, to compress the display:

$ RUN ERROR$:ERRDIS <RET>
ERRDIS
V9.0 RSTS V9.0
EDERE
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
He[lp], Ba[d Blocks], Su[mmary] or Fu[ll] Report <Summary>? <RET>
List Bad Blocks (Yes/No) <No>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Summary Report taken on 29-May-85, 10:50 AM
Input File: {O,3]ERRLOG.FIL Output File: KB:ERRDIS.OUT
Reported Date/Time Range:
13-May-85, 12:21:22 AM through 28-May-85, 12:35:47 AM
ERROR
CODE-DESCRIPTION

TOTAL
REC/LOG

PF Power Fail/Start-up 1/1
DU MSCP Disks
7/7
DB RHl1/RP04-05-06
3/3
DL RLOI/RL02
3/3
MM RHll/TU16/TE16
* 239/100
SH MSG from SHUTUP
1/1

UNIT NUMBERS
2 3 4 5 6

1
49 7

3
2
5

Total of 115 Errors Logged out of 254 Received
34 out of 100 Blocks have been used in [0,3]ERRLOG.FIL

10-8

CONTROLLER
ERRORS
N/A
3
N/A
N/A
N/A
N/A

Managing System Errors

********************************************************************
Input File <[0,3]ERRLOG.FIL>?

Bad Block Report
The ERRDET program reports possible bad blocks that were detected by
the monitor by checking the error logging file for such entries.
The
criteria for a possible bad block depends on the type of disk.
Each bad block report includes:
o

The logical block number

The logical name or pack identification of the disk

The physical device name of the disk

Using the logical block number that ERRDIS prints, you can add the
possible bad block to the bad block file with the BADS suboption of
REFRESH.
See the RSTS/E System Installation and Update Guide for
information on adding bad blocks.
The following example shows a list of bad blocks that the ERRDIS
program prints:
$ RUN ERROR$:ERRDIS <RET>
V9.0 RSTS V9.0
EDERE
ERRDIS
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? BAD BLOCKS <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Bad Block Report taken on 29-May-85, 10:51 AM
Input File: [0,3]ERRLOG.FIL Output File: KB:ERRDIS.OUT
Requested Date/Time Range:
First Error through Last Error
[0,3]ERRLOG.FIL will not be zeroed upon completion
List of Possible Bad Blocks:
Logical Name
Physical Name
Logical Block Number

RAIDER
DM1:
3401

Logical Name
Physical Name

OFTHE
DR4:
10-9

Managing System Errors
Logical Block Number

237968

Logical Name
Physical Name
Logical Block Number

LOST
DR5:
432952

Logical Name
Physical Name
Logical Block Number

ARK
DM2:
8

Total Number of Possible Bad Blocks: 4
********************************************************************
Input File <[0,3]ERRLOG.FIL>? ~Z
Note
Use caution before adding possible bad blocks (that
ERRDIS reports) to the bad block file.
Instead of
corrupt disk surfaces, hardware controller or disk
drive problems may have caused the errors to occur.

Adding Bad Blocks to the-Bad Block File
The ERRDIS program prints a list of potential bad blocks.
If you
decide to add a block to the bad block file BADB.SYS on a disk, use
the BADS suboption of the REFRESH option in INIT.SYS (see the RSTS/E
System Installation and Update Guide).
In preparation for adding bad
blocks, which requires you to bring the system down, use the PIP
system program to copy the data in a bad file to a new file.
As your
system discovers bad blocks, PIP lets you collect this information in
a single file.
You can then use this file to add the bad blocks to
BADB.SYS when you normally take your system down.
Follow these steps to use PIP for this purpose:

Specify the /GO switch (along with other necessary switches,
such as /eL, and so forth) to ignore possible ?Data error on
device errors.
Rename the file that contains the bad block,
but do not delete it:
$ RUN $PIP
*FILE.TMP=FILE.OLD/GO
*FILE.BAD=FILE.OLD/RE
*FILE.OLD=FILE.TMP/RE

10-10

Managing System Errors
2.

When it is convenient, shut down the system and use the BADS
suboption of REFRESH to add any bad blocks to the disk's bad
block file.
Each new bad block is now allocated to two files
([O,l]BADB.SYS and FILE.BAD in the previous example).

The BADS suboption automatically rebuilds the allocation
tables.
It then tells you the file has a bad block and
allows you to delete the file (FILE.BAD in the previous
example).
The RSTS/E Installation and Update Guide describes
this operation.

When BADS deletes the file,
not bad.

it frees'the blocks in the file that are

You must modify the previous procedure if the bad block is in a file
directory.
In this case, use the BACKUP (or SAVE/RESTORE) program to
copy all accessible files in the account (or disk) to an archive
medium. When you add the bad block and clean the disk, you can delete
the account whose directory contains the bad block. After starting
timesharing, use SAVE/RESTORE to restore the entire disk, or use
BACKUP to restore the files from the archive medium.
The bad block report does not apply to MSCP disks; bad blocks on those
devices are recovered automatically.

Full Report
Each error displayed includes:
o

A title line containing the error code mnemonic

The error description

A sequence number

The date and time the error occurred

The monitor maintains the sequence numbers, starting at one, from
start-up to shutdown. A crash and subsequent automatic restart does
not reset these numbers.
There are four basic categories for individual errors displayed within
the full error report:
o

Nonperipheral errors such as processor traps and memory
parity·

Disk errors

10-11

Managing System Errors
o

Nondisk peripheral device errors such as magnetic tape errors

Other errors such as the shutdown message received from
SHUTUP or missed errors

The program automatically checks for and reports possible bad block~
for disk errors included in the scan. The following sections contain
partial listings of a FULL report.
When the monitor detects a hardware or software error, it sends
information about the error to the ERRCPY program. ERRCPY can accept
and file error information until the number of queued errors reaches
40. The monitor logs all errors it detects beyond this point as
"missed errors." Only after the queue begins to empty and the number
of errors queued to ERRCPY falls below the maximum of 40 can the
monitor begin to send the normal error information. This means that
while the queue is full, the monitor reports all subsequent errors as
"missed errors," rather than sending the usual error information to
ERRCPY.
The monitor also reports missed errors if it does not have a
sufficient number of general small buffers available to store error
information. When the number of general small buffers drops below 75,
the monitor reports any, detected error to ERRCPY as a "missed error."

User Description in Full Report
All errors except shutdown, missed errors, and some MSCP controller
errors usually include a user description. The name fields in the
user description relate to a specific job whose number appears in the
first field (Job number).
(Under certain conditions, a job number of
o is possible. In this case, the user description is not listed.)
The following example shows a complete error report for a tape device;
the report includes both a user d~scription and a detailed
description:
$ RUN ERROR$:ERRDIS <RET>
ERRDIS
V9.0 RSTS V9.0 ED ERE
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? <RET>
Starting Date <First Error>? 13-May-85 <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET> .
ERRDIS Full Report (All Types) taken on 29-May-85, 02:17 PM
Input File: [O,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT

10-12

Managing System Errors
Requested Date/Time Range:
13-May-85 (First Error) through Last Error
[0,3]ERRLOG.FIL will not be zeroed upon completion

********************************************************************
MM

RHll/TU16/TE16 Seq #92 Occurred on 28-May-85 at 02:11:44 PM

User Description:
Job Number
KB Number
Account
Program Name
User Job Physical Addr.
User Job Size
Control Parameters
RTS Name
RTS Physical Address

18
2

[1,170]
PASIKO
02310000
28K
200
RTll
01714000

Detailed Description:
Timeout Indicator
Physical Name

000
MMO:

DDB

017600
045471
000000
000056

CSR Address:

176700

173444
005171
147240
002004

104252
001630
000000
127311

Contents of Registers:
MTCSI
MTWC
MTBA
MTFC
MTCS2
MTDS
MTER
MTAS
MTCK
MTMR
MTDT
MTSN
MTTC
MTBAE
MTCS3

145270
000400
132444
000000
000100
150660
100000
000001
000000
000000
000000
000000
000000
000016
002000

TRE Xfer Err

PE Mode
COR/CRC

TU77 TM03

Table 10-2 summarizes the user description data.

10-13

000011
177400
001007

Managing System Errors
Table 10-2:

User Description Data

+- - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Heading
I
Meaning
I
+ - - - - - - - - -,- - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Job Number

For disk errors, the number of the job that
requested the I/O; for nondisk peripheral
errors, the job owning the device; for
nonperipheral errors, the job running at
the time of the error.

KB Number

The keyboard number of the job, followed by
DET if the job is detached.

Account

The PPN of the user who created the job.

Program Name

The name of the program running in the job
virtual address space (low segment).

User Job Physical
Address

The current physical memory address of the
job.

User Job Size

The size of the user program running in the
low segment of the job virtual address
space.

Control Parameters

Monitor control information.

RTS Name

The name of the run-time system mapped into
the highest segment of the user's virtual
address space.

RTS Physical Address

The address of the location in physical
memory where the run-time system resides.

+- - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I * A detailed description of this entry is beyond the scope of this I
I
manual. The entry is intended for use by DIGITAL personnel.
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Disk Error Detailed Description
A FULL report for a disk error includes three sections:
o

User description

Detailed description

Contents of register

10-14

Managing System Errors
Table 10-3 describes the information found in the detailed description
portion of a disk error report.
Before you refer to the table, study
the following example.
The example shows what a single complete disk
error looks like.
If the entire Full Report of DB type errors were
reproduced here, you would see two more identically structured error
messages following this one. As you can tell from the sample in the
section "Summary Report," there are three DB errors under TOTAL
REC/LOG.
T~e example follows:
$ RUN ERROR$:ERRDIS <RET>
V9.0 RSTS V9.0 EDERE
ERRDIS
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? DB <RET>
Starting Date <First Error>? l3-May-85 <RET>
Starting Time <First Error>? <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Full Report (DB only) taken on 29-May-85, 11:00 AM
Input File: [0,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT
Requested Date/Time Range:
13-May-85 (First Error) through Last Error
[0,3]ERRLOG.FIL will not be Zeroed upon completion

********************************************************************
DB

RH11/RP04-05-06 Seq #81 Occurred on 28-May-85 at 07:12:14 AM

User Description:
Job Number
KB Number
Account
Program Name
User Job Physical Addr.
User J,ob Size
Control Parameters
RTS Name
RTS Physical Address

17
33 (Det)
[1,100]
LOGOUT
02744000
11K
200
... RSX
00000000

Detailed Description:
I/O Status
Timeout Indicator
Offset Position
Overlapped Seek Ind.
Unit Size in DC's
Device Cluster Size
Pack Cluster Size
Logical Name
Physical Name
Logical Block Number

000
000
Previous
377
121510
8

8
D

DB2:
19272
10-15

Managing System Errors
DSQ

004500
045501
000000
000056

173442
006171
146300
002004

104252
064540
000000
127310

000011
174000
001000
001003

WCB

100000
146274
113570
005166

004442
000000
004550
005413

000002
000000
004551
005414

000021
001310
005165
005415

FCB

147040
064511
001300
000011

070560
077430
113570
000226

000544
037404
001270
000010

076725
000001
113570
146300

CSR Address:

176700

[1,100]
TEMP33.TMP

Contents of Registers:
RPCSI
RPWC
RPBA
RPDA
RPCS2
RPDS
RPERI
RPAS
RPLA
RPMR
RPDT
RPSN
RPOF
RPDC
RPCC
RPER2
RPER3
RPECI
RPEC2

145270
000400
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000
000000

TRE Xfer Err

Not Ready

Table 10-3 describes the information found in the detailed description
portion of the previous disk error report.
The program prints an
additional field if the error signalled a possible bad block.

10-16

Managing System Errors
Table 10-3:

Disk Error Detailed Description

+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Heading
I
Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I/O Status
Timeout Indicator

Offset Position

Overlapped Seek Ind.

unit Size in DC's

I
I
I
Timeout and I/O status are considered as a I
pair. One of the following states can
I
exist:
I
I
Timeout
I/O
I
status
Meaning
Indicator
I
I
I
Idle
o
o
I
SEEK in progress
x
1
I
Waiting for
1
o
I
Read/Write
I
Timeout
1
x
I
I
where x equals any nonzero value.
I
I
The contents of Offset Position for disks
I
having offset capabilities:
I
I
o = centerline position
I
20 ="+x offset
I
220 = -x offset
I
40
= +2x offset
I
240
-2x offset
I
60
= +3x offset
I
260 = -3x offset
I
100
offset unknown
I
I
where x equals the number of micro inches
I
of offset (a drive type parameter).
I
I
377 = overlap seek driver
I
000 = non-overlap seek driver
I
I
You determine which of these two values
I
appears during system installation.
I
I
Size (in octal) of the disk expressed as
I
See following Timeout Indicator.

the number of device clusters.
Device Cluster Size

Device cluster size for this drive.

Pack Cluster Size

Pack cluster size for this disk.

10-17

I
I
I
I

Managing System Errors
Table 10-3:

Disk Error Detailed Description (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Heading
I
Meaning
I
+ - - - - - - - - - - - - - -' - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Logical Name

The pack identification if no system wide
logical name was given at mount time or
the system logical name entered at mount
time.

Physical Name

The physical name and unit number.

Logical Block Number

The block number where the error occurred.

OSQ*

The disk request queue entry block.

WCB*

The WCB (Window Control Block) is present
for disk errors that resulted from a file
request by the user job.

FCB*

The File Control Block.

CSR Address

The CSR address is the base address of the
set of registers in the I/O page belonging
to the device that caused the error.

Contents of Registers

This section contains the name of each
readable device register, its contents
and, possibly, an abbreviated description
of various error bits that were found to
be set to one in the register. ERRDIS
stores a maximum of 21 error bits for each
error type. The data file ERRDAT.FIL
contains the register mnemonics, error bit
descriptions, and error code descriptions
for all error types. ERROIS requires this
file to run.
See the PDP-II Peripherals Handbook for a
detailed description of registers and bit
descriptions. The register mnemonics
displayed by ERROIS correspond to those
given in the manual.

+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I * A detailed description of this entry is beyond the scope of this I
manual. The entry is intended for use by DIGITAL maintenance
I
I
personnel.
I
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

10-18

Managing System Errors
MSCP Variations on the Full Report
For systems that support MSCP type disk hardware, (for example, the
RA80), there are two variations on the Full Report:
o

If there is a disk error, then the Full Report looks just
like the normal Full Report, except that it has an extra
section called the MSCP Description (see Example #1).
Therefore, the Full Report includes the following four
sections:
User Description
Detailed Description
Contents of Registers
MSCP Description

If there is a controller error, then the Full Report shows an
abbreviated error message.
The Full Report does not have a
User Description, and its Detailed Description is not as
large as in the normal Full Report (see Example #2).
The
Full Report includes the following three sections:
Detailed Description
Contents of Registers
MSCP Description

If you refer back to the sample report in the section "Summary
Report," you will notice that the first example that follows is the
error that was logged under UNIT NUMBER 1. The second sample error
message that follows is one of the three errors logged under
CONTROLLER ERRORS.
Example #1:
$ RUN ERROR$:ERRDIS <RET>
ERRDIS
V9.0 RSTS V9.0 EDERE
Input File <0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? DU <RET>
Starting Date <First Error>? <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Full Report (DU only) taken on 29-May-85, 02:17 PM
Input File: [0,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT
10-19

Managing System Errors
Requested Date/Time Range:
First Error through Last Error
[0,3]ERRLOG.FIL will not be zeroed upon completion

********************************************************************
DU

MSCP Disks

Seq #46 Occurred on 28-May-85 at 02:35:39 PM

User Description:
Job Number
KB Number
Account
Program Name
User Job Physical Addr.
User Job Size
Control Parameters
RTS Name
RTS Physical Address

12
16
[1,217]
PACKID
01610000
7K
000
BAS4F
01514000

Detailed Description:
I/O Status
Timeout Indicator
Offset Position
Overlapped Seek Ind.
Unit Size in DC's
Device Cluster Size
Pack Cluster Size
Logical Name
Physical Name
Logical Block Number

000
377
000
000
000000

o
o

DU7:
200806

DSQ

000000
001424
023000
000000
000003
003777

CSR Address:

160414

177430
010147
000400
000000
004000

103664
000367
000010
075576
000000

Contents of Register:
SA

000000

Controller On Line

10-20

Managing System Errors
MSCP Description:

- - - - - - - - - - - - - - - --

Packet Type"

End Message

MSCP Envelope

000060

000001

MSCP Packet

074130
000203
000000
020424
000007
000001

140416
000043
000000
001003
000000
003400

Command Reference Number
Drive Number
Message Flags
End Flags
Endcode
status/Event Code
First Bad Block

074130 140416
000007
000
000
GET UNIT STATUS command
203
000043
No vol mntd or r/s switch out
031431 020144

000007
000736
001624
031431
000037
000020

000000
000000
000000
020144
000001
002001

Example #2:
$ RUN ERROR$:ERRDIS <RET>
ERRDIS
V9.0 RSTS V9.0 EDERE
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? DU <RET>
Starting Date <First Error>? <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Full Report (DU only) taken on 29-May-85, 02:19 PM
Input File: [0,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT
Requested Date/Time Range:
First Error through Last Error
[0,3]ERRLOG.FIL will not be Zeroed upon completion

********************************************************************
DU

MSCP Disks

Seq #2 Occurred on 19-Apr-85 at 12:21:22 AM

Detailed Description:
I/O Status
Timeout Indicator

000
377

CSR Address:

172150

10-21

Managing System Errors
Contents of Register:
SA

000000

Controller On Line

MSCP Description:
Packet Type

Last Fail

MSCP Envelope

000030

000020

MSCP Packet

000000
000400
000000

000000
000012
000406

controller Class
Controller Model
Controller Hardware Version
Controller Software Version
UDA Internal Error Code

001
006
000
004
000013

Mass Storage
UDA50-A

000000
000000
000004

000000
000000
000013

ER.MST - Bus Master Error

Nondisk Peripheral Device Error Detailed Description
Table 10-4 lists the fields found in the detailed description portion
of the nondisk peripheral device error report.
Before you refer to
the table, study the following example.
The example shows a single
complete tape error. As you can tell from the example in the section
"Summary Report," this is one of the 239 tape errors that were
received.
This particular error was one of the 100 logged, and also
one of the seven logged under UNIT NUMBER 1.
The entire Full Report
contains 99 more tape error messages.
The example follows:
$ RUN ERROR$:ERRDIS <RET>
V9 . 0 RSTS V9. 0 EDERE
ERRDI S·
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? MM <RET>
Starting Date <First Error>? <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Full Report (MM only) taken on 29-May-85, 02:17 PM
Input File: [O,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT
Requested Date/Time Range:
First Error through Last Error
[0,3]ERRLOG.FIL will not be zeroed upon completion

********************************************************************
MM

RHll/TU16/TE16 Seq #44 Occurred on 28-May-85 at 05:51:08 AM
10-22

Managing System Errors
User Description:
Job Number
KB Number
Account
Program Name
User Job Physical Addr.
User Job Size
Control Parameters
RTS Name
RTS Physical Address

11
33 (Det)
[1,100]
BACKUP
02610000
15K
200
... RSX
00000000

Detailed Description:
Timeout Indicator
Physical Name

000000
MM1:

DDB

000016
000001
105536
000361
000000

CSR Address:

172440

000426
000000
120540
001002
007314

002102
000000
010004
010760
004400

100001
000000
000021
000053

Contents of Registers:
MTCS1
MTWC
MTBA
MTFC
MTCS2
MTDS
MTER
MTAS
MTCK
MTMR
MTDT
MTSN
MTTC

145260
000000
010004
000000
000100
150760
100000
000001
000010
001100
142011
060023
102301

TRE Xfer Err

PE Mode
COR/CRC

TU16/TE16

Table 10-4 describes the information found in the detailed description
portion of the previous nondisk peripheral device error report
example.

10-23

Managing System Errors
Table 10-4:

Nondisk Peripheral Device Format

+ - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.+
I
Heading
Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

I Timeout Indicator

Nonzero indicates that an expected
response was not received from the device
in the allotted time.

Physical Name

The physical name and unit number of the
device.

DDB*

The DDB (Device Data Block) contains
various parameters required by the system
to control the device.

DDB* Extension

Supplementary DDB information.

CSR Address

The CSR address is the base address of the
set of registers in the I/O page belonging
to the device that caused the error.

Contents of Registers

See the PDP-II Peripherals Handbook for a
detailed description of registers and bit
descriptions. The register mnemonics
displayed by ERRDIS correspond to those
given in the manual.
+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I * A detailed description of this entry is beyond the scope of this I
manual. The entry is intended for use by DIGITAL maintenance
I
personnel.
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Nonperipheral Error Detailed Description
See the related processor handbook for detailed descriptions of
nonperipheral error fields.
Table 10-5 gives an abbreviated
10-24

Managing System Errors
description of these items.
Before you refer to the table, study the
following example.
This example shows a single complete error message
extracted from the ERRLOG.FIL using ERRDIS to reproduce only the PF
type errors:
$ RUN ERROR$:ERRDIS <RET>
ERRDIS
V9.0 RSTS V9.0 ED ERE
Input File <[0,3]ERRLOG.FIL>? <RET>
Output to <KB:ERRDIS.OUT>? <RET>
Help, Bad Blocks, Summary or Full Report <Summary>? FULL <RET>
Specific Error Type <All>? PF <RET>
Starting Date <First Error>? <RET>
Ending Date <Last Error>? <RET>
Zero Error File upon completion (Yes/No) <No>? <RET>
ERRDIS Full Report (PF only) taken on 29-May-85, 02:21 PM
Input File: [0,3]ERRLOG.FIL
Output File: KB:ERRDIS.OUT
Requested Date/Time Range:
First Error through Last Error
[0,3]ERRLOG.FIL will not be zeroed upon completion

********************************************************************
PF

Power Fail/Start-up Seq #1 Occurred on 13-May-85 at 02:15:01 PM

Detailed Description:

RO
R1
R2
R3
R4
R5
Virtual PC
Physical PC
Processor Status
Stack Pointer
(SP)
(SP+2)
(PC-6)
(PC-4)
(PC-2)
(PC)
CPU ID
CPU ERR

000000
004200
000000
000002
004100
000000
000077
00000077
000000
002074
000002
000000
034156
004356
034156
004357
-1
000000

Table 10-5 describes the information found in the detailed description
portion of the previous example.

10-25

Managing System Errors
Table 10-5:

Nonperipheral Error Format

+ - - - - - - - - - - - - - - -' - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. +

Heading

Meaning

+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- -..;-+

RO-R5

I
I
I
I
The address (within the user virtual
I
address space) of the instruction being
I
executed at the time of the error.
I
I
The address (in the physical memory
I
address space) of the instruction being
I
executed at the time of the error.
I
I
The processor status word.
I
I
The address of the current top of stack.
I
I
The contents of the top two words in the
I
stack.
I
I
The contents of the three words preceding
I
the current program PC and the contents of I
the current PC.
I
I
I
If it exists, the contents of the CPU
I
identification register.
I
I
If it exists, the contents of the CPU
I
error register.
I
I
If it exists, the CPU has Maintenance
I
Examine/Deposit Instruction.
I
I
Certain nonperipheral errors include
I
contents of key registers. The format is
I
identical to the contents of registers for I
disk and nondisk peripheral errors.
I

Processor registers 0 through 5. Each
register is listed on a separate line.

Virtual PC

Physical PC

Processor status
stack Pointer
(SP)
(SP+2)

(PC-6)
(PC-4)
(PC-2)

(PC)
CPU ID
CPU ERR
MED X
Contents of Registers

+- - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Note
The PF error code is used for recording both start-up
and power fail recovery.
The error log for a normal
start-up has a sequence number of 1.
For a power
fail restart, the sequence number is greater than 1.

10-26

Managing System Errors
Analyzing System Crashes: ANALYS
Time-sharing operations halt when a crash occurs on a RSTS/E system.
The system then writes an image of read/write memory, tables, and XBUF
to the CRASH.SYS file in account [0,1].
The system bootstraps the
system disk, loads the initialization code into memory, and executes
an automatic restart if the CPU switch register has bit 0 set.
Unless you run the ANALYS program to save crash dump information, the
next system crash causes the CRASH.SYS file to be overwritten and the
information in the file to be lost.
Normally, this is done as part of
system start-up.
See Chapter 2 for a description of automatic system
recovery procedures.
The crash analysis program ANALYS consists of four modules:
o

ANALYS

ANALYl

ANALY2

ANALY3

For simplicity, the documentation refers to only one program, ANALYS,
which functionally includes the four modules.

Running the ANALYS Program
Run the ANALYS system program by typing the command:
$ RUN ERROR$:ANALYS<RET>
After you press RETURN, the ANALYS program prints an identification
line and three dialogue questions:
ANALYS V9.0 RSTS v9.0 EDERE
INPUT <[O,l]CRASH.SYS>? <RET>
OUTPUT <ANALYS.DMP>? <RET>
Crash error log filename<[0,3]ERRCRS.FIL>? <RET>
$

Table 10-6 explains how to answer the ANALYS program questions.

10-27

Managing System Errors
Table 10-6:

ANALYS Program Dialogue

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
!
Question and Response
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

I INPUT <[O,l]CRASH.SYS>?
I
I
I

I
I

I
I
I

I
I

I
I
I
I

Asks for the name of the file to be analyzed. Type the file
specification of the file you want ANALYS to analyze, which
by default is CRASH.SYS in account [0,1]. Press RETURN to
accept the default response. However, you may want to keep
copies of different crash files.
ANALYS uses the currently installed monitor SIL file to
extract symbolic references. If the crash file being
analyzed is not associated with the currently installed
monitor, you must append the /SIL: switch with the name of
the related monitor SIL. This switch allows DIGITAL to
analyze crash and .SIL files submitted with a Software
Performance Report (SPR).

I OUTPUT <ANALYS.DMP>?
I
I

Requests a disk file or a device designator for the output
medium. You can select the default output file ANALYS.DMP by
pressing RETURN. Enter another file specification if you do
not want ANALYS to place the output in the default account.
ANALYS always prints an annotated version of a memory dump
and automatically prints a memory dump in l32-column format
unless you:
o

Request output to your terminal (for example,
KB:ANALYS.DMP).

Append the /NARROW switch to a file specification (or
type /NARROW and press RETURN in response to the OUTPUT
question if you want ANALYS.DMP to be the output file).

Append the /NOSTB switch to produce a quick analysis
report. Do not use this switch when submitting an SPR.

In either case, you get the annotated output in BO-column
format, but with fewer memory locations printed on each
line. If you do not want a dump of memory, append the
/NODUMP switch to your response.

10-2B

Managing System Errors
Table 10-6:

ANALYS Program Dialogue (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -'- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Question and Response

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Crash error log filename<[0,3]ERRCRS.FIL>?
Asks for the file specification of the file you want to hold
certain error information from the crash file. Press RETURN
to have ANALYS write this information to the ERRCRS.FIL in
the error package account [0,3].

I
I
I
I
I
I
I

Note that the /DET qualifier causes ANALYS to detach.

ANALYS retrieves error information saved at the time of a
system crash but not written to the system error logging
file ERRLOG.FIL. The ERRDIS program accepts the file you
specify as input and produces an error log report from its
contents. To retain a single continuous error logging file,
use an ERRINT option.

I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Normally, ANALYS takes more than 15 minutes to run. When the output
stops, the program automatically terminates and returns to the
keyboard monitor prompt.

ANALYS Output
output of the ANALYS system program supplies valuable hardware and
software information that a software specialist can use to determine
possible causes of system crashes. It includes:
o

A report similar to SYSTAT

A memory dump of the critical contents of memory

A listing of all monitor symbols

The report also contains DECnet/E information if you configured your
system with DECnet/E. See the RSTS/E utilities Reference Manual for
an explanation of SYSTAT.
Table 10-7 shows the error codes that ANALYS reports in the crash dump
data.

10-29

Managing System Errors
Table 10-7:

System Crash Error Code

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Error Code (Octal) I
Meaning
I
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - -..: - - - - - - - - - - - - - - - --+

-1(177777}

Power fail error.

-2(177776}

Jump to O.

-3(177775}

This code is returned when RSTS/E does a
crash dump as a result of halting the CPU and
continuing from location 52 (octal).

-4(177774}

This code is returned when RSTS/E detects an
unrecoverable problem and forces a software
crash.

Trap to 4.

Trap to 10.

Trap to 250 (Memory management violation).

Kernel SP Stack overflow.

Trap to 114 (parity memory error).

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

To obtain crash information printouts automatically, include the
proper commands in the START. COM file.
The commands run ANALYS to
preserve the crash information and run ERRDIS to create a report.
See
Chapter 3 for a description of the commands you should include in the
START.COM file.

10-30

Chapter 11
Device Management and Caching Control

This chapter introduces the concepts of device management and caching
control on your RSTS/E system.
Later, it explains DCL commands
available to you in more detail.
Table 11-1 summarizes these DCL
commands.
Table II-I:

DCL Commands for Device Management and Caching Control

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
I
Meaning
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Device Management
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
ALLOCATE
Allocates a device and optionally assigns it a
I
logical name
I

DEALLOCATE

Deallocates the specified device

SET DEVICE

Sets the characteristics for the specified device

SET PRINTER

Set the characteristics of the specified line
printer

SHOW DEVICE

Displays information about the specified device

SHOW DISKS

Displays the status of all mounted disks

SHOW PRINTER

I
I
I
I
I
I
I
I
I
I
I
I
I
I

Displays the characteristics of the specified
printer
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Caching Control
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I SET CACHE
Enables data and directory caching
I

I
I SHOW CACHE

Displays the current cache settings
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

11-1

Device Management and Caching Control
Principles of Device Management
The SET DEVICE command can be used for all devices that were allowed
under the SET option of INIT. You need HWCTL privilege to use the SET
DEVICE command.
See the RSTS/E System Installation and update Guide
for a description of the SET option.
You can disable a specific device for the current time-sharing session
with the /DISABLE qualifier to the SET DEVICE command.
To disable a
device for subsequent sessions, use the SET DEVICE command in the
START.COM file.
To reenable a disabled device, use the /ENABLE
qualifier.
The /RESTRICT qualifier limits the use of the specified device to
users with DEVICE privilege.
The /NORESTRICT qualifier lets any user
allocate or open the specified device.

Optimizing Disk Directory structure: REORDR
The REORDR program can restructure the disk directories on your system
to improve disk access time.
This process begins once you run REORDR
and answer the set of questions in its dialogue.
The following
sections discuss:
o

Operations that REORDR performs

REORDR dialogue

Restructuring the public disk structure

Example of the entire process

Why Use REORDR?
The system catalogs RSTS/E files on disk in user file directories
(UFD). As you create, delete, and extend files, the file directory
entries become scattered across the surface of the disk.
This
scattering increases both the time to open files and the time to
retrieve data blocks.
The REORDR program can perform three operations to restructure disk
directories.
Each of these operations can improve the performance of

11-2

Device Management and Caching Control
your system. After you run the program and answer a sequence of
dialogue questions, REORDR performs the following:
1.

places the list of file names in as few physical disk blocks
as possible. This reduces the number of directory accesses
the system needs to make for a file open operation.

Attempts to place all directory information concerning the
physical location of file data (retrieval pointers) for a
file into contiguous disk blocks.
This reduces the number of
disk directory accesses required to perform disk read and
write operations.

Optionally sorts the file name list in one of four ways,
depending on how you answer the dialogue questions. This
reduces the number of directory accesses the system needs to
make for a file open operation.

When RSTS/E creates a new file in an account, it adds the file name at
the end of the current directory list.
That is, RSTS/E places files
last in the directory if, during disk initialization, you typed NO to
the DSKINT question NEW FILES FIRST (see the RSTS/E System
Installation and Update Guide).
This ordering, while not efficient
under most situations, may be more efficient for your installation.
You should have new files first only if users on your system do not
create many new files and their accounts are not large. Otherwise,
because of the way RSTS/E retrieves user directory information, it is
more efficient to have new files last. with the REORDR program, you
can choose to organize files by access date or creation date.
Note that because DCL always has its work file open while you are
logged in, you normally cannot reorder your own account's directory on
the system disk.

Dialogue Questions and Responses
The REOROR program prints a set of questions after you type RUN
AUXLIB$:REOROR:
$ RUN AUXLIB$:REORDR
REORDR V9.0 RSTS V9.0 EOERE
Sort Oirectory(s) (YES/NO) <NO>? YES
Order by CRE[ATION] or ACC[ESS] Date<CRE>? <RET>
In FOR[WARO] or REV[ERSE] Order<FOR>? <RET>
Device and UFO Specification(s)? OB1:[*,*],OB2:[*,*]

11-3

Device Management and Caching Control
Table 11-2 summarizes these questions and their responses.
Table 11-2:

REORDR Dialogue Questions

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
Question and Response
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Sort Directory(s) (YES/NO) <NO>?
Type NO or press RETURN to keep the existing order of the
account(s) you are processing. Either response causes REORDR
to skip the next two questions.
Type YES to have REORDR sort the account(s) you designate.
REORDR asks the next two questions to determine how you want
the account(s) sorted.
Order by CRE[ATION] OR ACC[ESS] Date<CRE>?
Type CRE or press RETURN to have REORDR sort the account(s)
by creation date.
Type ACC to have REORDR use ACCESS date to sort the
account(s). Depending on how the disk was initialized, the
access date can have one of two meanings. It can mean:
o

When the file was last accessed

When it was last modified

Note that the abbreviation DLW in the comments part of the
disk status report of SYSTAT or the VT50PY program shows
that a disk's access date is set to the date of last
modification.
In FOR[WARD] or REV[ERSE] Order<FOR)?
Type FOR or press RETURN if you want REORDER to sort oldest
files first.
Type REV to have REORDR create a sorted file with newest
files first.

11-4

Device Management and Caching Control
Table 11-2:

REORDR Dialogue Questions (Cont.)

I
I Device and UFO Specification(s)?
I

Enter the device mnemonic(s) and unit number(s) of the
device(s) you want REORDR to process. Include the account(s)
you are reordering with the device designator. For example,
the specification DBO:[1,210],DBl:[*,210] is a valid
response. Although SY: (indicating the entire public
structure) is not a valid device, SYO: (indicating the
system disk, the device that was bootstrapped) is acceptable
for the device response. An asterisk (*) is a valid
character in either or both of the project-programmer
account fields. It tells REORDR to process all project or
all programmer numbers on the device. You can also include
multiple specifications if you separate them with commas
(,). The account designators are:

[*,*]

Process all user file directories on the disk

[p, * ]
Process all user file directories with project number p
[*,pn]
Process all user file directories with programmer
number pn
[p,pn]
Process only the user file directory with project
number p and programmer number pn
NOTE
For disks initialized prior to VB.O, REORDR does not
order account [1,1], even though it may be implicit in
an account designation.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Reordering Your Disks
To reorder all disks in the public disk structure, you must include
the device designator for each disk and the account numbers of the
files you want reordered:
Device and UFD Specification(s)? DBO:[*,*], DBl:[*,*]

11-5

Device Management and Caching Control
REORDR orders all the directories in the UFD on RP04 unit 0 and then
all the directories in the UFO on RP04 unit 1. Make sure you
logically mount the disks with write access before running the
program.
To prevent damage to a directory, REOROR requires that all files in a
UFD be closed during the entire operation.
Note
REORDR verifies that no file is open when it starts
to process the UFO. However, it is unable to detect
file opening, creation, or deletion between the
initial check and the completion of the UFO
processing. REOROR can damage the file structure of
a disk if a file creation takes place during
reordering. For this reason, follow either of these
steps as a precaution:
o

Disable logins with the SET SYSTEM/NOLOGINS
command. Make sure that no other jobs (including
spoolers and detached jobs) are active on the
system.

oismount the disk to be reordered and remount it
using the /NOSHARE qualifier.

The only safe way to reorder a UFO on the public
structure is to disable logins and to make sure that
no other user is currently logged in. You should
reorder a UFD on a private disk only when you are
sure that no other job will access the account(s}
being reordered on that disk. If you follow the
second step, this is no problem.

Error and Processing Messages
During the reordering of a UFO, the REORDR program holds the reordered
UFO in a temporary file. At the conclusion of the ordering process,
REOROR copies the temporary file back to the original UFD. As REORDR
processes each UFO, it generates either a message indicating that the
reorder worked or one that tells why an attempted reorder did not
work. The messages REOROR prints in the attempt to reorder an account
are:
)

Directory dev:[m,n]
Directory dev:[m,n]
Directory dev:[m,n]
Directory dev:[m,n]

cannot be Reordered
does not exist
has been Reordered
is not Reordered - File filename.type is OPEN
11-6

Device Management and Caching Control
Directory dev:[m,n] is not Reordered - No write access to UFD
Directory dev:[m,n] is Null
I < - - - - - forma t - - - - > I I < - - - - - - - - - - - - - - - - t ext - - - - - - - - - - - - - - - - - - - - - > I
The general format and the example of the format contain a device
designator and an account number:
Directory dev:[m,n] I<-----text------->I
Directory DR3:[1,223] has been Reordered
Table 11-3 explains each message.
Table 11·3:

REORDR Message Text

+- - - - - - - - - - - _. - - - - - - - - - - - - - - - - - - _. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

REORDR Message and Response

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

cannot be Reordered
Account [0,1] contains open files during timesharing and
thus REORDR cannot reorder them.
does not exist
REORDR cannot find the account on the device.
has been Reordered
REORDR has successfully reordered the UFD.
is not Reordered - File filename.typ is OPEN
A user is accessing the UFD and thus REORDER leaves the UFD
intact.
is not Reordered

No write access to UFD

REORDER encounters a UFD to which it cannot gain write
access. It prints the error message and continues.
is Null
No UFD exists for the account. If REORDR encounters an
account without a UFD, it prints the IS NULL error message.

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _. - - - - _. - - - - - - - - - - - - - - - - - - - - - - - - --+

Fatal errors cause REORDR to print a message of the form:
?REORDR Fatal Error [code]

I<----message----->I AT LINE nnnnnn

11-7

Device Management and Caching Control
All fatal REORDR errors include the ?REORDR Fatal Error prefix, a
program error code, a message, and a program line number.
Code
represents the number of the program error that caused the fatal
condition to occur.
(DIGITAL uses the code number to determine the
reason for the fatal error.) REORDR prints a brief message to help
identify the error.
Finally, the error message includes the line
number at which the program came to an end.
Submit a Software
Performance Report (SPR) to DIGITAL whenever REORDR encounters a fatal
error.

REORDR Example
The following example shows the REORDR dialogue and the messages that
result from the reordering process:
$ RUN AUXLIB$:REORDR
REORDR V9.0 RSTS V9.0 EDERE

Sort Directory(s) (YES/NO) <NO>? YES
Order by CRE[ATION] or ACC[ESS] Date<CRE>? CREATION
In FOR[WARD] or REV[ERSE] Order<FOR>? REVERSE
Device and UFD Specification(s)? OB1:[*,*],DB2:[*,*]
Directory DBl:[O,l] cannot be Reordered
Directory DB1:[1,1] cannot be Reordered
Directory DBl:[1,3] has been Reordered
Directory DBl:[1,4] has been Reordered
Directory DB2:[1,8] has been Reordered
Directory DB1:[1,13] has been Reordered
Directory DB2:[1,44] is Null
Directory DB2:[1,77] is Null
Directory DB1:[1,200] has been Reordered
Directory DB1:[1,201] has been Reordered
Directory DB1:[1,202] has been Reordered
Directory DB2:[2,227] has been Reordered
Directory DB2:[2,240] has been Reordered
Directory DB2:[26,12] has been Reordered
Directory DB2:[100,100] has been Reordered
Directory DB1:[120,50] has been Reordered
Directory DB2:[120,54] is Null
Directory DB2:[210,203] has been Reordered
Directory DB2:[232,15] has been Reordered
Directory DB2:[232,13] has been Reordered
Directory DB2:[251,0] has been Reordered
Sort Directory(s) (YES/NO) <NO>? <CTRL/Z>
$

11-8

Device Management and Caching Control
Caching Control
Data caching stores blocks from a user file for direct memory access.
Directory caching stores the Master File Directory (MFD), the Group
File Directory (GFD), the User File Directory (UFD), monitor overlay
code, and other frequently accessed system files and directories.
When a user job executes a read request, the RSTS/E monitor performs a
disk access and transfers the requested block(s) of data from the disk
to the user job's buffer. With data (and/or directory) caching, the
monitor stores the most recently read data blocks in an area of memory
called the cache.
If a user job executes a read request for a data
(and/or directory) block in the cache, the monitor copies the
requested data directly from the cache into the job's buffer. Because
the system can thus retrieve data blocks from memory instead of disk,
physical disk access is decreased.
This can result in improved I/O
throughput and faster response time.
Data caching is only useful for read operations.
Every write
operation causes an actual write to the disk.
In a write operation
that modifies existing cached data, the data is updated, both in the
cache and on the disk.
You must specify explicitly a choice of caching during system
installation (see the RSTS/E System Installation and Update Guide).
You can generate two types of caching:
o

Directory caching only

Data and directory caching

Directory caching is automatically enabled at system start-up.
If you
select data caching, it is automatically enabled provided that at
least 2K words of XBUF are allocated.
You can also enable data caching with the DCL command SET CACHE.
Moreover, DCL commands let you specify caching for a particular file
because it lets you mark the file's UFD entry.
Under the BASIC-PLUS or MACRO programming languages, you can use MODE
values in the OPEN statement or monitor directives to open a file for
cached data access.
However, the use of caching MODE values and
monitor directives requires TUNE privilege. As system manager, you
can use the DCL command SET FILE (see Chapter 12) to designate a file
for caching by marking its UFD entry. Once you mark a file's UFD
entry for caching, it is cached on OPEN regardless of the user's
privilege, as long as caching is enabled on the system.
See the
RSTS/E Programming Manual for information on the BASIC-PLUS OPEN
statement and the RSTS/E System Directives Manual for information
about MACRO directives.

11-9

Device Management and Caching Control
When you select and enable data caching, the cache receives all data
transfer requests that are otherwise directed to the disk driver.
Read operations on data that is in the cache occur without placing a
load on the disk driver. The monitor constantly updates the cache so
that it contains the most recently requested data for cached files.

Size of the Cache
The RSTS/E monitor allocates space for the cache from the Extended
Buffer Pool (XBUF). You specify the amount of this allocation with
DCL command qualifiers that set the size of a cache cluster
(/CLUSTERSIZE=n) and the number of clusters in the cache (/MAXIMUM=n,
/DIRECTORY_MAXIMUM=n, and /DATA_MAXIMUM=n). The size of a cache
cluster (1, 2, 4, or 8 blocks) determines the amount of data that is
treated as a unit in a read request and, in many cases, the number of
read requests that can be resolved in the cache before access to the
disk driver is required.
For example, when the cache cluster size is eight blocks, any read
operation that installs data in the cache causes eight physically
contiguous blocks (including the requested blocks) to be installed.
To ensure that only requested data is read in to the cache, make the
cache cluster size equal to or less than the pack cluster size (set
during disk initialization) of the disk with the most files to be
cached.

Sequential and Random Caching Modes
You can cache the data in a file in two ways: sequential or random.
You can specify either of these modes for a particular file with the
SET FILE command qualifiers (see Chapter 12).
If a job executes a read operation on a cached file and the data is
not in the cache, that data is installed in the cache if there is free
space or if a current cache cluster is eligible for replacement.
A cluster is eligible for replacement if either of the following
conditions is in effect:
o

The last block of the cluster has been read in sequential
mode.

The cluster has been in the cache without being read for more
than the minimum residency time, which is set using the SET
CACHE command.

11-10

Device Management and Caching Control
Random Mode Caching
DIGITAL recommends caching a file in random mode if the file is RMS
index structured. with an RMS indexed file structure, the monitor
does not access the data in the file sequentially but must check the
file index each time it gets more data. Thus, it reads the index, the
data, and the index again.
As an example of random cache operation, consider a read operation
executed on a file whose UFD entry is marked for random caching. When
a read on the cached file occurs, the monitor examines the contents of
the cache to determine if the requested data is present. If the data
is in the cache, the data is copied from the cache cluster that
contains it. The data is made available to the program and the cache
cluster time of last access is updated.
If the requested data is not in the cache, the monitor first attempts
to allocate more of XBUF to install the new data (cache limits
permitting). If XBUF cannot accommodate more data or the request
exceeds the caching limits set with SET CACHE, then the monitor
examines the list of cache clusters to find one that is eligible for
replacement. If a cluster is not available, the monitor cannot
install the requested data in the cache; a normal disk read is
automatically performed. If the cache cluster is eligible for
replacement, the monitor installs the requested data in that cache
cluster and makes the data available to the program.

Sequential Mode Caching
DIGITAL recommends caching a file in sequential mode if you access the
contents of the file sequentially. As an example of sequential cache
operation, consider a read operation executed on a file whose UFD
entry is marked for sequential caching. When a read on the cached
file occurs, the monitor examines the contents of the cache to
determine if the requested data is present. If the data is in the
cache, the data is copied from the cache cluster that contains it.
The data is made available to the program. If, in the process, the
last block of a cache cluster was read, that cluster is made available
for replacement in the cache.
Furthermore, when you request a read operation on any block of a cache
cluster (except the last block), the monitor installs.a full cluster
of data in the cache. That is, if you use the SET CACHE command
qualifier /CLUSTERSIZE=n to set a cache cluster size of 8 blocks and
then execute a read on the first block of a file, the requested data
plus the next 7 blocks from the disk are read into the cache. Thus,
the contents of the next 7 reads can be satisfied from the cache.
When the last block of the cache cluster is read, the cluster is
immediately made available for the installation of new data as
requested by other read operations.
11-11

Device Management and Caching Control
When a read operation from a sequentially cached file causes more than
one cache cluster to be read, all of the requested data blocks are
made available to the program. However, no data is installed in the
cache for any cluster whose last block was read.
(That is, only the
last cluster can be installed and only if it was incompletely read.)
If the cache cluster size is defined as one block and sequential mode
is specified, no data blocks are installed in the cache. Thus, every
data block is the last block in a cache cluster.

Caching Guidelines
The relationship between cache cluster size, which you set with a SET
CACHE/CLUSTERSIZE=n command, and the pack cluster size of the file can
have an effect on the efficiency of caching. The cache cluster size
determines the number of blocks on a disk copied into the cache when a
cluster is installed.
If the cache and pack cluster sizes are equal,
there is direct correspondence between the data that will probably be
read and the data copied from the disk to the cache.
If the cache
cluster size is larger than the pack cluster size, the data you
request plus some additional (and possibly unrelated) data is copied
to the cache, wasting cache clusters.
If the cache cluster size is
less than the pack cluster size, a read request may require multiple
disk accesses to move all of the data into several different cache
clusters.
Figure 11-1 shows the flow of UFD entry and MODE value checks
performed by the monitor.
The result of these checks determines the
type of caching to be used on the file.

11-12

Device Management and Caching Control

Yes

No
Caching
Performed

Caching
Performed

Yes

H-MK-00075-00

Figure II-I:

Caching Mode Checks

The size relationship between the cache cluster and RMS indexed file
bucket is similar to the size relationship between the cache cluster
and the pack cluster.
Efficient caching is obtained when the cache
cluster and bucket sizes are equal because RMS always reads an entire
bucket at once.
Consider the following caching guidelines:
o

When setting defaults, the amount of XBUF you allocate to
data and directory caching should be as large as possible
while maintaining sufficient memory for user jobs, resident
libraries, and run-time systems. However, an exceptionally
large allocation can increase swapping activity, especially
on systems with less than 128K words of memory.

On systems that use RMS heavily, consider the use of the RMS
resident library and the library's effect on XBUF allocation.
Typically, on systems with less than 128K words of memory,
the resident library should receive priority in memory
11-13

Device Management and Caching Control
allocation, to the extent of limiting XBUF allocation. In
such a case, dat~ caching may become ineffective and you
probably should disable it.
o

To optimize directory caching, set all UFD cluster sizes to
16 blocks if possible.

Files that are frequently accessed sequentially (including
RMS sequential and relative files) should have their UFD
entries marked for sequential caching with the DCL command
SET FILE/CACHE=SEQUENTIAL.

Files that are frequently accessed randomly (including RMS
relative and indexed files) should have their UFD entries
marked for random caching with the DCL command SET
FILE/CACHE=RANDOM. Because of the way RSTS/E maintains RMS
indexed files, they should always be flagged as random even
if they are accessed sequentially. Where possible, RMS
indexed file bucket sizes should be a power of two to
correspond with caching cluster sizes.

Use data caching judiciously on RMS indexed files. You gain
the most benefit from caching an indexed file when it is
subject to many read requests and is open for long periods of
time. In addition, you should allocate more XBUF to
compensate for the lower caching "hit" rate (the probability
that the data you want to read is in the cache) on indexed
file data. The hit rate is generally lower on indexed files
than it is on sequential files or directory blocks.

Where possible, all files should be contiguous to reduce
window turning.
Where contiguous files are not possible, you should calculate
the file cluster size as follows:
1.

Divide the file size by seven

Round the resul t to the next higher power of' two (not
greater than 256 nor less than the pack cluster size)
Note
If you preextend the file, RSTS/E does this
calculation for you.

The minimum residency time is meant to keep some useful data
in the cache, even when the cache is very small. Minimum
residency time is also meant to make sure that if you want to
access previously accessed data the system will find it in
11-14

Device Management and Caching Control
the cache, rather than 'having to read information off disk
each time you request more.
For systems with large caches or
rapidly changing disk access patterns, it may be advantageous
to reduce the minimum residency time from its default value
of 60 seconds. Use the /KEEP=n qualifier to modify minimum
residency time.
Caching is not the most efficient data access method for all files
under all circumstances. But, in general, a high-access file is a
logical candidate for caching. A high-access file meets one or more
of the following conditions:
o

Accessed by more than one user at a time

Opened for long periods of time

Frequently accessed

Accessed sequentially (indexed files)

Primarily read

Is an overlaid program (such as a user program, TKB, or DTR)

However, because of the large number of different applications, you
must experiment to arrive at the best use of caching on your system.

DCL Command Descriptions
The following sections describe the DCL commands and qualifiers for
Device Management and Caching Control.

11-15

ALLOCATE
ALLOCATE Command
The ALLOCATE command allocates a device and optionally assigns it a
logical name. ALLOCATE does not require any privileges to allocate a
device to your own job.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
ALLOCATE dev:

[logical_name[:]]

Command Qualifiers

Defaults

/JOB=n
/SEIZE
Prompts

I
I
I
I
I
I
I
I
I
I
I
I
I

None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
dev:
Specifies the device to be allocated.
logical_name[:]

Specifies the logical name to be assigned to the device.
Command Qualifiers
/JOB=n
Allocates the device to the specified job.
privilege to use this qualifier.

You need HWCTL

/SEIZE
Reallocates a device currently allocated to another job. The
/SEIZE switch returns an error message if a file is open on the
device.
You need HWCTL privilege to use this qualifier.

11-16

DEALLOCATE
DEALLOCATE Command
The DEALLOCATE command deallocates the specified device.
does not require any privileges.

DEALLOCATE

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - -+

Format
DEALLOCATE dev[:]
Command Qualifiers

Defaults

/ALL
Prompts

I
I
I
I
I
I
I
I
I
I
I
I

None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
dev:
Specifies the device to be deallocated.
Command Qualifiers
/ALL

Deallocates all devices that were allocated to the current job.

11-17

SET CACHE
SET CACHE Command

The SET CACHE command and qualifiers let you set caching parameters
for the system as a whole. The SET CACHE command lets you enable data
and directory caching on the system. Note that commands in the system
start-up command file normally enable caching automatically. You need
TUNE privilege to use the SET CACHE command.
When you use SET CACHE with no qualifiers, the last settings specified
are applied.
The initial system defaults are:
/CLUSTERSIZE

4 blocks

/MAXIMUM

No limit on total cache allocation

/DIRECTORY_MAXIMUM

No limit on directory caching

/DATA_MAXIMUM

No limit on data caching

/KEEP

60 seconds

If you use SET CACHE/ALL, all read requests are cached. The type of
caching (sequential or random) for a particular file is determined by
the file's UFO entry as specified in the SET FILE command or by an
OPEN MODE specification.
If you use SET CACHE/FILE, a file is cached on the basis of its UFO
entry and/or the specified OPEN MODE. That is, a file is cached if
either the UFO entry or OPEN MODE specifies caching; it is cached
sequentially if either the UFO entry or OPEN MODE specifies
sequential.
If you use SET CACHE/NOFILE, RSTS/E does not cache files.
This
qualifier is used to enable directory caching but disable data caching
on the system.
Figure 11-2 shows the mechanism by which the monitor decides the
amount of caching to be performed. The figure shows the flow of DCL
commands and caching specifications examined by the monitor.

11-18

SET CACHE

Yes

Cache
Sequential

Yes

Cache
Random
H-MK-00076-00

Figure 11-2:

Monitor Caching Checks

The /BUFFERS and /NOBUFFERS qualifiers specify the use of general
small buffers for directory caching. These qualifiers are meaningful.
only if you did not select data caching at system installation time.
If you specify a SET CACHE/BUFFERS command on a system that has data
caching installed, the monitor prints the following error message:
?Missing special feature
If data caching is installed, you can not use small buffers for
caching.
Use the SET CACHE/CLUSTERSIZE=n command to specify the cache cluster
size as 1, 2, 4, or 8 blocks for each cluster. The cache cluster size
controls the number of contiguous data blocks that are copied from
disk to the cache whenever file data is cached. The cache cluster
size should be small enough to contain only the target blocks but
large enough to reduce the number of disk accesses. This means you
must anticipate data requests and ensure that the cache cluster size
is equal to the file cluster size of the files most frequently
accessed.
11-19

SET CACHE
The SET CACHE/MAXIMUM=n command (where n is in
UNLIMITED) specifies the total number of cache
directory and data caching. The default limit
means that cache cluster allocation is limited
XBUF available.

the range 0 to
clusters used by both
is UNLIMITED, which
only by the amount of

The SET CACHE/DIRECTORY MAXIMUM=n and SET CACHE/DATA_MAXIMUM=n
commands (where n is in-the range 0 to UNLIMITED) specify the cache
cluster allocation for directory and data caching, respectively. The
specified allocation is an upper limit. Thus, if a 40K-word XBUF is
defined at system installation and /DIRECTORY_MAXIMUM and
/DATA_MAXIMUM both specify a number of cache clusters equivalent to
25K, data can use space in the cache up to a maximum of 25K, which
leaves a 15K minimum for directory caching. The reverse is also true.
In this manner, data and d~,rectory caching are guaranteed a minimum
allocation and the amount of overlap is controlled, which permits the
cache to dynamically adjust to system and program requirements.
The SET CACHE/KEEP=n command specifies the 9ache replacement time in
seconds.
This is the amount of time that RSTS/E keeps an unused cache
cluster in memory before the monitor replaces it with another cache
cluster.
The SET CACHE/DISABLE command disables all data and directory caching
on the system.
If you reenable caching following a disable and do not
specify caching parameters (/CLUSTERSIZE, /MAXIMUM,
/DIRECTORY MAXIMUM, /DATA MAXIMUM, and /KEEP), the default parameters
are those that were in effect before the disable.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Format
SET CACHE
Command Qualifiers

Defaults

/ALL
/[NO]BUFFERS
/CLUSTERSIZE=n
/DATA_MAXIMUM=n
/DIRECTORY_MAXIMUM=n
/DISABLE
/ENABLE
/[NO]FILE
I /KEEP=n
,I /MAXIMUM=n

/BUFFERS
/CLUSTERSIZE=4
/ENABLE
/ENABLE
/FILE

I
I Prompts
I
I None
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

11-20

SET CACHE

Command Qualifiers
/ALL
Caches all data transfers.
/[NO]BUFFERS
Indicates whether general small buffers are used for directory
caching.
The default is /BUFFERS.
/CLUSTERSIZE=n
Specifies a cache cluster size of n with values equal to 1, 2, 4,
or 8 blocks.· The default is /CLUSTERSIZE=4.
/DATA_MAXIMUM=n
Specifies the maximum number of clusters (based on available
memory) used for data caching in the range 0 to UNLIMITED.
/DIRECTORY_MAXIMUM=n
Specifies the maximum number of cache clusters used for directory
caching in the range 0 to UNLIMITED.
/DISABLE
Disables data and directory caching.
/ENABLE
Enables caching on the system using the previous settings as the
defaults. The default is /ENABLE.
/[NO]FILE
Indicates if file data should be cached. The /FILE qualifier
indicates that file data is cached depending on their file
attributes or OPEN MODE.
The /NOFILE qualifier indicates that no
file data is cached. The default is /FILE.
/KEEP=n
Specifies the cache replacement time in seconds that an unused
cache cluster is kept in memory before the space can be used for
another cache cluster.
/MAXIMUM=n
Specifies the maximum number of cache clusters used for directory
and data caching in the range 0 to UNLIMITED.
11-21

SET DEVICE
SET DEVICE Command
The SET DEVICE command sets the characteristics for the specified
device.
SET DEVICE does not require any privileges.
~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

I
I Format
I
I SET DEVICE dev:
I
I Command Qualifiers
I
I /DISABLE
I /ENABLE
I /[NO]RESTRICT
I
I Prompts
I
I Device:

Defaults

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --iCommand Parameters
dev:
Specifies the device whose characteristics you want to change.
Command Qualifiers
/DISABLE
Disables the specified device.
specified with /DISABLE.

No other qualifiers can be

/ENABLE
Enables a device that has been disabled by the SET DEVICE/DISABLE
command.
/[NO]RESTRICT
Tells the system which users can open or allocate the specified
device.
The /RESTRICT qualifier "lets only users with DEVICE
privilege open or allocate the device.
The /NORESTRICT qualifier
lets any user open or allocate the device.

11-22

SET PRINTER
SET PRINTER Command
The SET PRINTER command sets the characteristics of the specified line
printer.
You need HWCFG privilege to use the SET PRINTER command.
~

- - - - - - - - - - - - - - - -- - - --- - - - - - - - - - - - --- - -- - - - - - - ----------- --~
Format
SET PRINTER dev[:]
Command Qualifiers

Defaults

/BACKSPACE[=mode]
/[NO]CONTROLS
/[NO]CR_PREFIX
/DEVICE_TYPE=type
/[NO]EIGHT_BIT
/[NO]EOT
/[NO]FILL
/LOWERCASE
/[NO]OMIT_CR
/PAGE_LENGTH=n
/[NO]SPECIAL_CHARACTER[=char]
/[NO]TAB
/UPPERCASE
/WIDTH

/BACKSPACE=REAL

Prompts
Printer:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --~

Command Parameters
dev [ : ]
Specifies the line printer whose characteristics you want to set.
Command Qualifiers
/BACKSPACE[=mode]
Tells the system how to handle backspace characters for this
printer. The possible modes are:
o

CONTROL -- Treats a backspace like other nonprinting
characters.

oREAL -- Uses the actual backspace feature on the specified
printer.

11-23

SET PRINTER

SIMULATE -- Simulates the action of backspace on the
specified printer by issuing a carriage return (CR) followed
by the appropriate number of spaces to position the print
head one column to the left of its original position.

The default is /BACKSPACE=REAL.
/[NO]CONTROLS
Tells the system how to handle nonprinting characters. /CONTROLS
sends nonprinting characters to the line printer. /NOCONTROLS
discards nonprinting characters or uses up arrow mode.

Tells the system how to handle line feed (LF), vertical tab (VT),
and form feed (FF) characters. The options are:
o

/CR_PREFIX inserts a CR before a LF, a VT, or a FF.

/NOCR_PREFIX tells the printer to do an implied CR before a
LF, a VT, or a FF.

/DEVICE_TYPE=type
Sets the characteristics of the line printer to the specified
type:
o

LA180 -- Sets the characteristics of the line printer to
those of an LA180.

LN01 -- Sets the characteristics of the line printer to those
of an LNOI.

LPll -- Sets the characteristics of the line printer to those
of an LP11.

/[NO]EIGHT_BIT
Tells the system how to handle 8-bit characters. The /EIGHT_BIT
qualifier lets you send 8-bit characters to the line printer.
The /NOEIGHT BIT qualifier does not let you send 8-bit characters
to the line ~rinter.
/[NO]EOT
Tell~ the system how to handle an end-of-transmission character.
The /EOT qualifier sends an end-of-transmission (CTRL/D) to the
line printer. The /NOEOT qualifier treats an end-of-transmission
(CTRL/D) like other nonprinting characters.

11-24

SET PRINTER
/[NO]FILL
Tells the system how to handle fill characters.
The /FILL
qualifier inserts fill characters after form feeds.
The /NOFILL
qualifier does not insert fill characters after form feeds.
/LOWERCASE
Sends lowercase characters to the line printer.

Instructs the system on how you want the CR character handled.
The /OMIT_CR qualifier tells the system to omit the CR if the
next character is a LF.
The /NOOMIT CR qualifier tells the
system to always send CR to the printer.
/PAGE_LENGTH=n
Sets the form length of the line printer to n.
can be in the range 1 to 255.

The form length

/[NO]SPECIAL_CHARACTER[=char]
Instructs the system on how you want the printer to handle its
special character.
The /SPECIAL CHARACTER=char qualifier tells
the printer to print its special-character whenever it receives
the specified char. Char can be given by its numeric value in
the range 0 to 255 or by enclosing the character in quotation
marks (") if it is printable.
The /NOSPECIAL_CHARACTER qualifier
tells the system to disable the special character feature for the
specified line printer.
/[NO]TAB
Instructs the system on how you want the TAB character handled.
The /TAB qualifier indicates that the printer has hardware TAB
capability.
The /NOTAB qualifier indicates that the printer does
not have hardware TAB capability and the system has to translate
TAB characters to the appropriate number of spaces.
/UPPERCASE
Tells the system to convert lowercase characters to uppercase
before sending them to the line printer.
/WIDTH=n
Sets the width of the line printer to n.
range 0 to 254.

11-25

The width can be in the

SHOW CACHE
SHOW CACHE Command
The SHOW CACHE command displays the current caching parameters for
your system.
SHOW DEVICE does not require any privileges.
The listing includes information on cluster sizes, data caching, and
whether general small buffers are used.
For example:
$ SHOW CACHE
Caching enabled for Directories and Data
Cache Keep timer = 60 seconds
Cluster size = 4
Data caching = File selectable

Cluster
Maximums
Usage
K Words

All
Unlimited
224
224.00

Directory
Unlimited
209
209.00

Data
Unlimited
15
15.00

K Words of Buffer usage for:
System
DCL
Quotas in
Logicals
Buffers
XBUF
0.56
0.00
0.44

Quotas in
Small Buffers

Overlays
4.19

In this example, SHOW CACHE reports that:
o

Directory and data caching were installed on the system
during system installation, and caching was enabled

The current cache cluster size is 4 blocks, only selected
files are cached, and general small buffers are not used

No limit is set on the use of XBUF for the cache

The cache keep timer is set to 60 seconds

209 K words are in use for directory caching

15 K words are in use for data caching

11-26

SHOW CACHE
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Format
SHOW CACHE
Command Qualifiers

Defaults

None
prompts

I
I
I
I
I
I
I
I
I
I
I
I

None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The SHOW CACHE command has no qualifiers or prompts.

11-27

SHOW DEVICB
SHOW DEVICE Command
The SHOW DEVICE command displays information about the specified
device.
If you do not specify a device, RSTS/E displays information
about all devices. SHOW DEVICE does not require any privileges.
~

-- -- --- - -- -- - --- - - -- - -- -- -- -- ------ - - - -- - ----- --- -- -----

--~

Format
SHOW DEVICE [dev[:]]
Command Qualifiers

Defaults

/ALL
/ALLOCATED

/ALL

Prompts
None

- -- - --- - - - - -- -- ---- - ---------- - - - - - - - ---- - - -- - - - - ------ - -

Command Parameters
dev[:]
Specifies the device whose characteristics you want to display.
Command Qualifiers
/ALL
Displays information about all devices configured on the system.
A device specification overrides the /ALL qualifier.
/ALLOCATED
Displays information about all devices that are currently open or
allocated. The display includes devices that are open as
non-file-structured devices.

11-28

SHOW DISKS
SHOW DISKS Command
The SHOW DISKS command displays the status of all mounted disks.
DISKS does not require any privileges.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
SHOW DISKS
Command Qualifiers

Defaults

None
Prompts
None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The SHOW DISKS command has no qualifiers or prompts.

11-29

SHOW

SHOW PRINTER
SHOW PRINTER Command
)

The SHOW PRINTER command displays the characteristics of the specified
printer.
SHOW PRINTER does not require any privileges.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SHOW PRINTER dev[:]
I
I Command Qualifiers
I
I /ALL
I
I Prompts
I
I None

Defaults
/ALL

I
I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
dev:
Specifies the printer whose characteristics you want to display.
Command Qualifiers
/ALL
Displays information about all the printers configured on the
system. A printer specification overrides the /ALL qualifier.

11-30

Chapter 12
Managing System Files and Logical Names

This chapter describes the DCL commands that you use to manage RSTS/E
syst~m files and logical names.
Table 12-1 lists and briefly
describes the DeL commands available to you.
The rest of the chapter
lists each command alphabetically and explains it in more detail.
Table 12-1:

DCL Commands for Managing System Files and Logical Names

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Run-Time System Control
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I INSTALL/RUNTIME_SYSTEM
I
I
I REMOVE/RUNTIME_SYSTEM
I
I

I
I
I
I
Removes the name of a run-time system
I
module as an entry in the run-time system I

Adds the named run-time system to the
list of installed run-time systems.

table.

I
I SHOW RUNTIME SYSTEM
I
I
I UNLOAD/RUNTIME_SYSTEM
I

Displays information about all installed
run-time system.

I
I
I
I
I
I

Unloads the named run-time system from·
memory.
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Resident Library Control
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
INSTALL/LIBRARY

Adds the named library to the list of
installed resident libraries~

REMOVE/LIBRARY

Removes the named file as a resident
library.

12-1

I
I
I
I
I
I

Managing System Files and Logical Names
Table 12-1:

DCL Commands for Managing System Files and Logical Names
(Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Resident Library Control (Cont.)
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I SHOW LIBRARY
I
I
I UNLOAD/LIBRARY

~,~

Displays informati6n about all installed
libraries.

I
I
I
I
I

Removes the named resident library from
memory.
I
+ - - - - - - - - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
System Logical Names Control
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

~ '"

ASSIGN/SYSTEM

Assigns a system-wide logical name to the
specified device type and unit. If you
include an account number, the
ASSIGN/SYSTEM command also associates
that PPN with the logical name.

DEASSIGN/SYSTEM

Removes the entire entry for the logical
name from the system logical table. It
can also remove logical names for devices
on your system. Device mnemonic names for
system devices have permanent entries in
the logical table. If you use the
DEASSIGN/SYSTEM command to remove a
logical name associated with a device,
only the logical name goes away, not the
device mnemonic. You can then assign a
new name to that device.

SHOW LOGICAL/SYSTEM

Displays information about a system-wide
logical name.
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
System~wide Command Language Control
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I DEFINE/COMMAND/SYSTEM
I
I
I DELETE/COMMAND/SYSTEM
I
I
I SHOW COMMAND/SYSTEM
I

I
I Creates or redefines a system-wide
I command.
I
I Deletes the specified command from the
I list of defined system-wide commands.
I
I Displays information about the specified
I system-wide command.

12-2

I
I
I
I
I
I
I
I
I

Managing System Files and Logical Names
Table 12-1:

DCL Commands for Managing System Files and Logical Names
(Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command

Meaning

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

System File Control

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

DUMP/SYSTEM

Records in the CRASH.SYS file the current I
state of the system so you or field
I
service has a way to investigate reasons
I
for system malfunctions.
I

INSTALL/ERROR_FILE

Installs the specified file as the system I
error message file.
I

INSTALL/OVERLAY_FILE

Installs the specified file as the system I
overlay file.
I

INSTALL/SWAP_FILE=n

Adds the specified file to the list of
installed swap files. Valid values of
swap-index are 0, 1, or 3.

REMOVE/ERROR_FILE

Removes the system error message file.

REMOVE/OVERLAY_FILE

Removes the system overlay file.

REMOVE/SWAP_FILE=n

Removes the specified swap file from the
list of installed swap files. Valid
values of swap-index are 0, 1, or 3.

SHOW FILE

Displays information about the specified
file(s).

I
I

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

User File Control

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

SET FILE

Sets the file characteristics.

I
I
I

SHOW LOGICALS

Displays information about a user-defined I
logical name.
I

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Run-Time System Control
A run-time system on RSTS/E is the common, shareable part of a user
job and, in some cases (for example, BASIC-PLUS), is the interface
between the user's executable code and the monitor. Run-time systems
control execution of jobs when the monitor allows the jobs to run.
12-3

Managing System Files and Logical Names
The monitor sets up jobs and establishes an environment in which a
run-time system can function. The BASIC-PLUS run-time system
interprets requests made by a user job, translates those requests into
a format the monitor understands, and transmits the requests of the
monitor. The monitor processes the requests and passes either data or
an error to the job. The run-time system decides whether to interpret
the data or log an error. Jobs running under the BASIC-PLUS run-time
system cannot make direct requests to the monitor.
other run-time systems may not be language interfaces in the same
sense that the BASIC-PLUS run-time system is. Jobs under their
control can make direct requests of the monitor. In such cases, the
major role of the run-time system is to load compiled programs to
handle system errors, and return control, on program termination, to
the job's keyboard monitor. Some of these run-time systems can also
emulate the action of certain system directives from other operating
systems, such as RTll.
A run-time system interprets user requests when it is a language
interface for a user job. A computer language provides a standard
means by which many users can define data, process it, and obtain
results. The language relieves each user of the need to learn the
workings of the monitor. The run-time system under which the language
operates is more efficient because multiple users can share the same
code. This ability to share code is more efficient for the system
because each user need not have a copy of the common code.
All RSTS/E installations have a primary run-time system and can
optionally have auxiliary run-time systems. The primary run-time
system:
o

Allows users access to system resources

Interprets system command requests

Performs housekeeping chores

An auxiliary run-time system:
o

Provides additional shared computer processing functions

Enables processing in other languages

Such an auxiliary run-time system may compile and/or execute
BASIC-PLUS-2, COBOL, DIBOL, FORTRAN-IV, FORTRAN-77, or other language
operations.
The system account [0,1] stores run-time systems as contiguous files
with .RTS file types. You must store the primary run-time system
(RSX.RTS) and DCL on the system disk because, at the start of
timesharing, the system disk is the only disk mounted on the system.
You can store auxiliary run-time systems on any disk~ either public or
12-4

Managing System Files and Logical Names
private.
(Auxiliary run-time system files can also be stored in
accounts other than [0,1].) All run-time system files are contiguous
because they must be loaded into memory in the fastest time possible.
The primary run-time system must be either DCL or RSX. Some
considerations that may help you decide which one to install as your
primary run-time system are:
o

RSX requires lK of reserved memorYi DCL requires 28K

If you have sufficient memory and do not need the RSX
keyboard monitor, install DCL as your primary runtime system.
Then, you can choose to not install the RSX run-time system.

If you have l24K or less of memory, use RSX as your primary
run-time system. You still need DCLi however, the system can
swap DCL out when it is not in use by other jobs on the
system.

Auxiliary run-time systems are created either during system
installation or afterwards. The monitor structures that describe
these run-time systems do not exist automatically at the start of
timesharing. ,Therefore, you must provide the commands to add monitor
structures for the auxiliary run-time systems that you want to make
available for any given time-sharing session. The structure for an
auxiliary run-time system is dynamic and can be removed during a
time-sharing session.
The DCL run-time system commands let you control operations of
auxiliary run-time systems. The DCL commands perform additional
processing for certain commands. To assist the system programmer, the
command descriptions distinguish between the monitor call action and
the DCL command action. Because run-time systems under development
need certain special controls, some features of run-time system
'
control are intended for DIGITAL personnel only. Nevertheless, all
features are described to give you a broader perspective.
DIGITAL recommends that you make auxiliary run-time systems available
by commands in the START. COM file. By reading the descriptions in
this section, 'you can understand what actions should 'occur for each
run-time system command.

Adding and Removing Auxiliary Run-Time Systems
Because the structures that define auxiliary run-time systems are
temporary, you must create them for each time-sharing session. The
INSTALL/RUNTIME SYSTEM command creates the necessary structure to
enable an aUXiliary run-time system to function.
INSTALL/RUNTIME_SYSTEM command qualifiers can alter predefined
characteristics of the run-time system.
12-5

Managing System Files and Logical Names
The INSTALL/RUNTIME_SYSTEM command creates a run-time system
description block with a general small buffer. A file with the name
of the run-time system and a file type of .RTS can be in any account
on the disk specified in the command. A run-time system with the same
name cannot already exist on the system. The system makes sure that
the file found is contiguous and has the proper format and parameters.
You can specify qualifiers to override predefined characteristics.
The INSTALL/RUNTIME SYSTEM command extracts information from the
run-time system file to establish the proper entries in the run-time
system description block. To establish the entries, the monitor opens
the file, reads it, and sets up the predefined characteristics to be
placed in the description block. You can change the predefined
characteristics by the qualifiers: /PREFIX=n, /[NO]UNLOAD,
/[NO]ERROR_LOGGING, /[NO]SHAREABLE, /[NO]READ_ONLY, and
/[NO] KEYBOARD_MONITOR.
You can also change the predefined characteristics by negating these
qualifiers. For example, if you were testing a run-time system with
no special command decoding capabilities, you would use the qualifiers
/NOSHAREABLE, /NOREAD ONLY, /NOERROR LOGGING, and /UNLOAD to add the
run-time system. The-/NOSHAREABLE makes sure that no other job tries
to share the untested code; /NOREAD_ONLY is necessary for setting
breakpoints with ODT; /NOERROR_LOGGING prevents false errors generated
by the run-time system from cluttering the system error log; /UNLOAD
makes sure that the run-time system's image is not left in memory but
is reloaded from disk immediately preceding every entry to it.
The qualifiers and negations of the qualifiers do not alter the
predefined characteristics in the run-time system file; only the
characteristics defined in the description block are altered. The
characteristics remain in effect until you remove the run-time system.
The /[NO]ADDRESS[=n] qualifier lets you take advantage of high speed
memory on the system or avoid fragmentation of memory. Without the
/ADDRESS=n qualifier, the monitor decides where to load the run-time
system each time residency is required. With the qualifier, the
monitor loads the run-time system at the specific lK-word section of
memory. You must include the /ADDRESS=n qualifier whenever you use
the /NOREAD_ONLY qualifier.
The /ADDRESS qualifier without an argument indicates that the monitor
should compute a starting address by finding the highest memory
segment large enough to hold the run-time system.
The /NOADDRESS qualifier lets the run-time system "float" in memory;
that is, RSTS/E computes a new address every time the run-time system
is loaded into memory. The default is /NOADDRESS.
Because 1K-word section numbering begins at 0 and ends at n-l (where n
is the total size of memory), the lK section number in the /ADDRESS=n
qualifier is one less than the physical section number. For example,
12-6

Managing System Files and Logical Names
to load the RTll run-time system (4K words in size) into the 61st
through 64th lK sections of memory, specify /ADDRESS=60.
The run-time
system is loaded from low memory to high memory at its defined
initialized size.
To be loaded without error, enough contiguous user
space must be available starting at that location.
The location specified in the /ADDRESS=n qualifier becomes the default
location at which the run-time :system is loaded during the current
time-sharing session. You need to change the location only if you
exchange the allocation of the section of memory with either the
DEFAULT or the START initialization options.
One precaution is necessary when specifying the address at which the
run-time system is loaded.
The section of memory you choose must not
fragment the user job space to prevent the run-time system from
executing a job.
For example, assume a system has 24K words of user
space available between the 36K and 60K sections of memory. Assume
also that a job requires 18K words of user space to run and that the
run-time system requires 4K words when resident.
If the loading
address is 36K, the space between 40K and 60K remains available for an
18K job to run.
If the loading address is 42K, the user space is
fragmented into two sections -- one from 36K to 42K and one from 46K
to 60K. An 18K-word job area is not available to execute a job using
this auxiliary run-time system.
The system verifies that the memory section given in the /ADDRESS=n
qualifier is reasonable.
If the entire range of memory starting at
the load address is not available, the system prints:
?Memory not available
You should consult a memory status report (for example, the report you
get with the SHOW MEMORY command) to select an available range of
memory.
If the range of memory results in fragmenting that may cause
a swapping violation, the system prints the error message:
?Memory would be fragmented
A swapping violation occurs if the memory to be occupied by the
run-time system does not allow enough contiguous space for a maximum
sized job to run.
Appendix D contains a summary of the errors that can occur when you
are installing a run-time system.
The /POSITION=n qualifier indicates the position in the linked list of
blocks in which the run-time system block is to be placed.
The
primary run-time system block is always first in the list.
If the
run-time system you are adding is to be accessed frequently, you can
reduce system overhead by placing it in the right position in the
list. Without the qualifier, the system adds the block to the end of
the list.
12-7

Managing System Files and Logical Names
If n in the /POSITION=n qualifier is one, the block is placed
immediately after that of the primary run-time system.
If n is zero
or a value greater than the number of currently defined run-time
systems, the block is added to the end of the list.
The default is
/POSITION=O.
The position of a run-time system description block in the linked list
affects how the system treats a RUN request for a file without a file
type.
On receiving such a RUN request, the system checks the
indicated directory for all files with the specified name and an
executable file type.
For example, if the directory contained three files of the same name
with file types .BAC, .TSK, and .SAV, the system checks for the
run-time system nearest the primary run-time system in the linked list
of description blocks.
If RSX was the primary run-time system (whose
block is always at the root), the system runs the .TSK version of the
file.
The /TYPE=filetype qualifier on the INSTALL/RUNTIME SYSTEM command
changes the default file type used for an executable file.
If you do
not specify this qualifier, the monitor extracts the file type defined
in the run-time system file.
The system applies this default file
type when a user types a RUN command for a program and does not
specify a file type.
The /MINIMUM=s and /MAXIMUM=s qualifiers alter the minimum and maximum
job sizes (in K words) defined in the file for the run-time system.
Generally, the minimum value allowed is one and the maximum is 32, but
a given run-time system may not allow this full range of job sizes.
For BASIC-PLUS, the minimum and maximum sizes are 2 and 16,
respectively.
The /LOCK qualifier makes the run-time system permanently resident.
Usually, an auxiliary run-time system is temporarily resident.
It
occupies memory as long as the currently active job is running under
its control.
The system frees the memory it occupies when that memory
is needed to load another run-time system or to load a job running
under another run-time system.
(Thus, the run-time system may be
nonresident if there are active jobs using it.) The system
automatically loads the run-time system when a user needs it. If you
specify the /LOCK qualifier, the auxiliary run-time system becomes
permanently resident, as the primary run-time system is.
The only way
to make such a run-time system nonresident is to use the DCL command
UNLOAD/RUNTIME_SYSYTEM.
The REMOVE/RUNTIME_SYSTEM command reverses the steps the
INSTALL/RUNTIME_SYSTEM command performs. Before you can shut down the
system, you must remove all auxiliary run-time systems.
The SHUTUP
program performs this removal operation automatically.
The system
checks to make sure that no jobs are currently running under control
of the run-time system to be removed.
If the usage count is zero, the
12-8

Managing System Files and Logical Names
description block is removed from the list and the run-time system
file is closed.
The UNLOAD/RUNTIME SYSTEM command frees the memory occupied by the
run-time system. If a job is currently resident or being loaded and
intends to use the run-time system, the system prints:
?Run-time system in use

Associating a File with a Run-Time System
The SET FILE/RUNTIME_SYSTEM=name command changes the name of the
run-time system associated with a file.
Every disk file on RSTS/E has
in its directory the name of the run-time system under which it was
created, except for files that are larger than 65,535 blocks.
On a
RUN request for the file, RSTS/E checks the name to find out what
run-time system to use for the job.
RSTS/E automatically passes
control to that run-time system which, in turn, executes the file.
To change the name, RSTS/E attempts to open the file to establish
write access.
If write access is denied, it prints:
?Protection violation
The name of the run-time system is written in the directory of the
file specified.
RSTS/E performs this naming operation during the
system library build procedures when a file designed to run under an
auxiliary run-time system is transferred from the distribution medium
using PIP.

Resident Library Control
A resident library is a collection of shareable routines or data that
the task builder links together into a task image file on disk.
The
MAKSIL program formats this disk file into Save Image Library (SIL)
format.
You can store resident libraries on any disk, either public
or private.
(Resident library files can be stored in accounts other
than [0,1].) All resident library files are contiguous because they
must be loaded into memory in the fastest time possible.
See the
RSTS/E Programmer's utilities Manual for more information on resident
libraries.
You then use the INSTALL/LIBRARY command to assign the task image
portion of the SIL file to a contiguous region of physical memory.
Note that you can also use monitor SYS call -18 to assign the task
image portion of the SIL file to memory. Once the body of shareable
routines or data is linked, formatted, and assigned to memory, it
12-9

Managing System Files and Logical Names
becomes a resident library that is accessible to user tasks as part of
their virtual address space.

Resident Library DCL Commands
You can use the DCL commands to install, remove, load, or unload a
resident library.
To distinguish between resident library operations
and run-time system operations that use the same command names, DCL
requires the keyword LIBRARY in its syntax for library operations.
You include the keyword LIBRARY in the DCL command line between the
operation keyword and the target resident library name.
For example, the DCL command to add a resident library is:
INSTALL/LIBRARY[/qualifiers] name
The name you include in the INSTALL/LIBRARY command identifies the
resident library.
To identify it in more detail, you can specify a
device, a PPN and a protection code in addition to the library name.
If you do not specify these variables, the device defaults to SY:, the
PPN becomes account [0,1], and the library's protection code defaults
to <42>.
You can also attach qualifiers to the INSTALL/LIBRARY
command.
The /[NO]ADDRESS[=n] qualifier locates the resident library at a
specific point in memory.
The n variable can be any number from the
lowest to the highest available memory locations in increments of
lK-word sections.
The /ADDRESS qualifier without an argument
indicates that the monitor should compute a starting address by
finding the highest memory segment large enough to hold the library.
The /NOADDRESS qualifier lets the library "float" in memory; that is,
RSTS/E computes a new address every time it loads the library into
memory.
However, this method of loading has the following
restrictions:
o

A program can only map one such library at any time

The program must be running under the RSX emulation run-time
system

The maximum size of the library is 28K words

The highest start address for mapping the library is 32K

The /LOCK qualifier lets you make a resident library permanently
resident. Usually, a resident library remains in memory only
temporarily; that is, it occupies memory only as long as currently
active jobs run under its control.
However, when you need to access
the library again, the system automatically reloads it.
To force the
12-10

Managing System Files and Logical Names
library to remain permanently in memory, you must specify the /LOCK
qualifier in the INSTALL/LIBRARY command.
If you want to remove a resident library from memory, delete the
monitor structure that defines the library, and close the library
file, use the DCL command:
REMOVE/LIBRARY name
Note that the REMOVE/LIBRARY command makes the resident library
inaccessible for sharing.
However, the /UNLOAD qualifier, which can
be used only with the INSTALL/LIBRARY command, only temporarily
removes the library from memory while it is not in use.
The UNLOAD/LIBRARY command removes a resident library from memory and
thus frees memory that can then be used to load another library or be
available for other system purposes.
If you attempt to unload a
resident library that is in the process of being loaded or is in use
by the currently running job, the system prints the message:
?Library in use
To prevent inadvertent loss of data, the monitor does not
automatically unload a library you have loaded with the /NOREAD_ONLY
qualifier.
Unloading a library removes it from memory but does not
write it back to disk.
This means the system discards the library and
retrieves a new copy from the disk when it is needed again.
Thus,
anything you write to a library that you mark read/write is lost after
you unload it with the UNLOAD/LIBRARY command.
You must use the
UNLOAD/LIBRARY command to unload a resident library that is designated
read/write.
Whether a library remains in memory depends on the qualifiers you
attach to the INSTALL/LIBRARY command. 'The /LOCK and /NOREAD_ONLY
qualifiers prevent the monitor from removing it automatically.
In
addition, the monitor does not remove a library to which a user job is
attached; instead, the system prints:
?Library in use

System Logical Names
RSTS/E lets users access devices by logical names as well as by
physical names.
Logical names that apply to all users are called
system logical names.
On all systems, users can refer to a disk by
its pack identification or by a name that replaces the pack
identification.
Thus, each disk unit configured on RSTS/E systems has
the capability of being accessed by a system logical name.
Logical
names that apply to a single job are called job-related logical names.

12-11

Managing System Files and Logical Names
You can define system logical names for nondisk devices and additional
names for disk devices.
The number of names is limited by the size of
XBUF.
Such a system logical name can have an account number
associated with it. Consequently, use of the name refers not only to
the related device but also to the account on the device.
The system
treats device names in the following manner:
1.

Checks the list of job-related logical names first.
Each job
can have up to four assigned logical names.
(If the logical
name has a $ character in it, this step is omitted.)

Scans the table of disk logical names for a matching pack
identification or equivalent.

Checks the additional names.

Checks the list of valid physical device names.

If individual users have not defined job-related logical names that
duplicate currently defined system logical names, all users have
access to devices by the logical names the system manager adds.
A system logical name must be unique. A pack identification or its
logical name cannot conflict with any other pack identification or
system logical name. However, you can define multiple system logical
names for the same device.
If the pack identification (or a logical name to replace the pack
identification) of a disk you are to mount is the same as an existing
system logical name, then RSTS/E mounts the disk with no system
logical name.
Unless you specify a different, unique name, the disk,
at mount time, has no logical name associated with the device and unit
being used.
System logical names apply for a single time-sharing session; however,
you can remove or change them during the session.
DIGITAL recommends
that you place the proper commands in START.COM to define names
automatically at system start-up time.
See the RSTS/E programming
Manual for'more details on system logical n~mes.

Assigning Logical Names
The ASSIGN/SYSTEM dev:[PPN] logical-name command defines a system
logical name for nondisk devices or an additional name for a disk
device.
You need INSTAL privilege to use ASSIGN/SYSTEM.
If the name
duplicates one currently defined and you specify the /REPLACE=QUERY
qualifier or you omit the /[NO)REPLACE qualifier, DCL prints a warning

12-12

Managing System Files and Logical Names
message and prompts to see if you want to replace the logical.
If you
specify /NOREPLACE and the logical name is already defined, DCL prints
the error message:
?Logical already installed
To change a currently defined name, use ASSIGN/SYSTEM/REPLACE command.
The logical name must contain from I to 9 alphabetic or numeric
characters.
You can include the dollar sign ($) character, however,
it must not be the first character.
If the name contains illegal
characters, DCL prints one of the the following error messages:
?Inva1id logical name
?Unexpected character pointing to the first nonalphanumeric
character
If there is no more room in XBUF, the system prints:
?No buffer space available
The device with which the name is associated must exist on the system.
If it does not, the system prints:
?Not a valid device

Removing Logical Names
The DEASSIGN/SYSTEM command deletes the association defined for the
logical name specified.
You need INSTAL privilege to use
DEASSIGN/SYSTEM.
Because a system logical name must be unique, you
need to specify only the name in the command.
If the name you include
is not currently defined, the system prints:
?Logical not found

If you use an illegally formed name, the system prints one of the
following:
?Invalid logical name
?Unexpected character pointing to the first nonalphanumeric
character
To delete all logical names for a device, you must use the
DEASSIGN/SYSTEM command for each currently defined name.

12-13

Managing System Files and Logical Names
Listing System Logical Names
The SHOW LOGICAL/SYSTEM command displays, for the specified logical
name, the device designation and unit number, any account number
associated with the logical name, and the logical name itself.
If you
do not specify a logical name, RSTS/E lists all the system logical
names.
RSTS/E displays the entries in the order in which they are
found in the monitor tables.

Defining Concise Command Language Commands
Concise Command Language (CCL) commands on RSTS/E let users type
system-level commands that load and run programs from disk. To take
advantage of this feature, you must code your programs to recognize a
CCL entry and to extract any command string passed to them.
The
RSTS/E programming Manual describes the operation and interpretation
of CCL commands.
Certain RSTS/E programs can interpret a standard set of eCL commands.
A RSTS/E installation can have any number of unique CCL commands.
You
make all CCL commands available to users by the DEFINE/COMMAND/SYSTEM
command which creates the'monitor structure required.
You need INSTAL
privilege to use the DEFINE/COMMAND/SYSTEM command.
Because the monitor structure that defines a CCL command is temporary,
CCL commands must be defined at the start of each time-sharing
session.
It is suggested that you place the proper command
definitions in the start and crash control files.
Each CCL command definition occupies one small buffer on the system.
All definitions are in a linked list of small buffers.
The system
executes a SYS call to add or remove CCL definitions and provides a
way to list all currently defined CCL commands.

Adding a CCL Definition
To add SY-STAT as a CCL command, execute the DEFINE/COMMAND/SYSTEM
command as follows:
$ DEFINE/COMMAND/SYSTEM SY-STAT [1,2]SYSTAT.*

This command adds the definition for the SYSTAT system program.
The
hyphen (-) designates the abbreviation point so typing SY runs the
SYSTAT program.
If you do not include a hyphen in your CCL
definition, the system places a hyphen at the end of the command and
allows no abbreviation.
RSTS/E assumes the public disk structure
(SY:) when you do not specify a device.
Programs you run with a CCL
command can reside on any disk device, but if it is not in the public

12-14

Managing System Files and Logical Names
structure, you must include the device in the command definition.
The
account designation [1,2] in the example means SYSTAT must reside in
the system library.
If you do not specify an account with the eCL
command, the system assumes the program is located in the account in
which the job (that is, the job of the user later invoking the CCL) is
running.
The asterisk (*) in SYSTAT.* indicates a wildcard file type.
In the
case of multiple versions of SYSTAT, the version of SYSTAT that is run
depends on the order of the run-time systems in your run-time system
list.
You can specify the line number at which execution starts by appending
the /LINE_NUMBER=n qualifier to the command.
The value of n can be
any integer from 0 to 32767.
There are standard entry points that you
can specify by the use of keywords:
o

CCL

30000

DCL

30500

CHAIN -- 31000

The system performs error checking before adding the CCL command.
the command is invalid, RSTS/E prints one of the following error
messages:

?Invalid command
?Unexpected character pointing to the first nonalphanumeric
character
A valid command can consist of:
o

A string of 1 to 9 alphanumeric characters

The first character must be a letter, or one of the following
single characters: @, $, #, %, or &

Lowercase letters are equivalent to uppercase in the definition and
use of CCL commands.
The $ CCL is reserved; it always pOints to DCL.
The command can have a maximum of nine characters.
If more than nine
characters are present, the system prints:
?Command too long
When you add two or more commands that begin with the same character
or set of characters, you must define the command with the largest
number of characters (to the left of the hyphen) first.
You then

12-15

Managing System Files and Logical Names
define the command with the next fewest characters to the left of the
hyphen, until you have made all the assignments.
For example, you
must define MACR-O before adding MAC-, or RSTS/E prints:
?Command not unique
This message also appears if you attempt to define a command that was
already defined.
If you need to add a longer CCL definition after you have already
added a similar but shorter one, you must first remove the shorter
entry.
You then add the longer CCL command which lets you reinstall
the ceL with the shorter command name.
For example, if you had
installed MAC- and at some later date needed to add MACR-O, you would
have to remove MAC-, install MACR-O, and then reinstall MAC-. The
section "Removing a CCL Definition" describes how to remove CCL
entries.

Listing Currently Defined eeL Commands
The SHOW COMMAND/SYSTEM command prints a listing of all currently
defined CCL commands. You can also list a single CCL command with the
SHOW/COMMAND/SYSTEM <name> command.
You need INSTAL privilege to
execute the SHOW COMMAND/SYSTEM command.
The list of CCL commands on
your system may contain some of the following:

$ SHOW COMMAND/SYSTEM
ATT-ACH
= SY: [ 1,2
BYE= SY: [ 1,2
DIR-ECTORY = SY: [ 1,2
DIS-MOUNT = SY: [ 1,2
EDT=
SY: [ 1,2
HELL-O
= SY: [ 1,2
HE-LP
= SY: [ 1,2
LBR=
SY: [ 1,2
LIBR= SY: [ 1,2
LIN-K
SY: [ 1,2
MACR-O
= SY: [ 1,2
MAC= SY: [ 1,2
MOU-NT
= SY: [ 1,2
PIP= SY: [ 1,2
PL-EASE
= SY: [ 1,2
QU-EUE
= SY: [ 1,2
SUB-MIT
= SY: [ 1,2
SY-STAT
= SY: [ 1,2
TE-CO
= SY: [ 1,2
TKB= SY: [ 1,2
$

]LOGIN *
/LINE=CCL
]LOGOUT.*
/LINE=O
/LINE=CCL
]DIRECT.*
]UMOUNT.*
/LINE=CCL
]EDT
.TSK /LINE=O
]LOGIN *
/LINE=O
/LINE=CCL
]HELP
*
]LBR
.TSK /LINE=O
]LIBR .SAV /LINE=B20B
]LINK .SAV /LINE=B20B
]MACRO .SAV /LINE=B216
]MAC
.TSK /LINE=O
] UMOUN'l1 . *
/LINE=CCL
]PIP
.SAV /LINE=B20B
]PLEASE.*
/LINE=CCL
/LINE=CCL
]QUE
*
/LINE=CCL
]QUE
*
]SYSTAT.*
/LINE=CCL
]TECO .TEC /LINE=35B4
]TKB
.TSK /LINE=O

12-16

/PRIVILEGE
/PRIVILEGE
/PRIVILEGE
/PRIVILEGE
/PRIVILEGE
/PRIVILEGE

/PRIVILEGE
/PRIVILEGE
/PRIVILEGE
/PRIVILEGE
/PRIVILEGE

Managing System Files and Logical Names
The system prints the commands in the order in which they were
defined.
If no CCL commands are currently defined, the system prints
the message:
%No Commands installed
Note
When you start the system, the monitor automatically
installs the $ CCL.
DIGITAL recommends that you do
not redefine the $ CCL.
The $ CCL lets you issue DCL commands from any
command environment.
For example, from BASIC-PLUS
you can type:
Ready

$ MOUNT DLO:MINDY/NOSHARE <RET>
Ready

Removing a CCL Definition
To remove a CCL definition, type the command DELETE/COMMAND/SYSTEM
followed by the definition.
You need INSTAL privilege to execute the
DELETE/COMMAND/SYSTEM command.
You can type either a full definition
or a valid abbreviation to indicate the command you plan to remove:
$ DELETE/COMMAND/SYSTEM MYPR-OG

If the definition does not currently exist, the system prints:
?Command not found
If the definition exists, the command removes the CCL definition
immediately.
You can delete all the CCL commands by appending the
/ALL qualifier to the DELETE/COMMAND/SYSTEM command.
For example:

$ DELETE/COMMAND/SYSTEM/ALL

System File Control
You allocate and position the following system files on
file-structured disks by executing the INSTALL/SWAP_FILE,

12-17

Managing System Files and Logical Names
INSTALL/OVERLAY_FILE, or INSTALL/ERROR_FILE commands:
o

SWAPO.SYS

SWAPl.SYS

SWAP3.SYS

OVR.SYS

ERR.SYS

These optional files optimize system performance by taking advantage
of higher speed disks and the characteristics of user jobs running on
the system.
Because the files are contiguous and contiguous space
becomes scarce as user files are created during timesharing,
preallocation and prepositioning are necessary.
The RSTS/E
Installation and Update Guide describes the planning considerations
for preallocating and positioning these system files.
RSTS/E does not automatically access these system files.
You control
RSTS/E access to these files with DCL commands.
Thus, the use of
these files during timesharing is dynamic.
If a hardware problem
occurs on a swap device, you can remove the device without stopping
timesharing.
To maintain the same amount of swap space, you can
designate a private disk as the swap device.
This section discusses the DCL commands that control system file
usage.
The commands in the start-up control file allow access to
system files at the start of time-sharing operations.

Adding and Removing Swap Files
The swap files SWAPO.SYS, SWAP1.SYS and SWAP3.SYS in account [0,1] are
standardized names for the three optional swap files.
While these
names are optional, DIGITAL recommends you use them because they
indicate the characteristics of the files.
You can, however, assign
any file name to these three swap files.
The system restricts the
file type to .SYS regardless of the file names you include in the DCL
commands.
The INSTALL/SWAP FILE command causes the system to access a specific
file (if a file-structured device is involved) or a specific device
(if a non-file-structured disk is involved).
You need INSTAL
privilege to execute the INSTALL/SWAP_FILE command.
Atypical command
sequence is:

$ INSTALL/SWAP FILE=O DR3:SWAPO
$ INSTALL/SWAP_FILE=l DRl:SWAPl
$ INSTALL/SWAP_FILE=3 DR4:SWAP3

12-18

Managing System Files and Logical Names
Note
When you specify a non-file-structured device in the
INSTALL/SWAP_FILE command, the monitor destroys any
existing file structure on that device.
The /SIZE=n qualifier of the INSTALL command allows online creation of
a swap file during timesharing.
The qualifier is most useful when you
want to add a swap file to a private disk that contains sufficient
contiguous space for the file.
The value n in the /SIZE=n qualifier
represents the number of blocks in the file.
RSTS/E attempts to
access the file with a file type of .SYS in account [0,1] on the
associated device.
If the file size differs from the size specified
in the /SIZE=n qualifier, RSTS/E prints a warning message in the
format:
NOTE

THE SIZE OF file.SYS IS x NOT n.

The value x is the actual size and n is the value in the /SIZE=n
qualifier.
If the file does not exist, the system attempts to create a contiguous
file of the size specified.
If there is not enough contiguous space
available to create the file, the system prints:
?Not enough contiguous space to create System file
The /POSITION=n qualifier lets you place the created swap file in a
particular location on the specified disk.
The monitor ignores this
qualifier if the already exists.
After you type the INSTALL/SWAP FILE command, the system tries to
install the particular file or device as the swap file.
If the system
finds any errors, RSTS/E prints an error message in the following
format:
Error text

in INSTALL SWAP FILE

Appendix D contains a list of the possible errors.
occur, the system installs the swap file.

If no errors

You can then activate the added swap file with the SET SYSTEM/LOGINS
command.
The SET SYSTEM/LOGINS command forces the system to examine
all swap file space and to calculate the number of jobs the system is
capable of running.

12-19

Managing System Files and Logical Names
During timesharing, the number of jobs that can run on the system
depends on:
o

The job maximum (JOB MAX) set at system generation

The amount of swap space added

The number of logins allowed through the SET SYSTEM/LOGINS
command

At the start of timesharing, the number of logins allowed is one. One
job is necessary for the DCL START. COM file to run.
You can increase
this number by using the SET SYSTEM/LOGINS command, but the number is
restricted by the swap space available and by JOB MAX. When you add
swap space with INSTALL/SWAP FILE commands, the capacity to handle
logins is increased.
The SET SYSTEM/LOGINS command sets the number of
logins to the maximum allowed.
This maximum cannot exceed JOB MAX.
RSTS/E lets you dynamically remove as well as add swap files 0, 1, and
3.
To remove a swap file or device, first decrease the number of
logins using the SET SYSTEM/NOLOGINS or SET SYSTEM/LOGINS n command.
The number of logins to be decreased depends on the capacity of the
swap file to be removed.
By decreasing the number of logins, you
allow the system to safely remove swap space.
The sequence of commands to remove a swap file is the reverse of the
sequence to add swap space.
For example, assume that a system is
running with a JOB MAX of 63 and is using a swap file with a capacity
of 16 jobs.
In this case, you must decrease the number of logins by
16 jobs before removing the swapfile.
The following sequence shows
this procedure:
$ SET SYSTEM/LOGINS~47
$ REMOVE/SWAP_FILE=l
$

In practice, it may take some time for the system to adjust
operations.
If the number of jobs currently running is greater than
47 or if the number of logins allowed is too large, the system prints
the error message:
?Too many logins allowed to remove Swap file
You must wait until users log out of the system.
The SHOW BUFFERS
command or the DISPLY program prints the number of jobs currently on
the system in the free buffer status report.
(The SHUTUP program
automatically removes swap files.)
It is possible to add more swap space than the system can use.
In
this case, you do not need to reduce logins to remove a swap file.
However, enough room must remain to swap all jobs currently logged in,
or to swap all jobs that can log in, whichever is greater.

12-20

Managing System Files and Logical Names
The SHOW FILE/SYSTEM command provides a way for you to verify that the
following files exist on your system:
o

Swap files (/SWAP_FILE)

Overlay file (/OVERLAY_FILE)

Error file (/ERROR_FILE)

DECnet/E Network Services Protocol (NSP) system file
(/NETWORK_FILE)

This command is most useful when you want to verify the addition or
removal of any of these files.
After adding a file, you can use the
SHOW FILE/SYSTEM/SWAP_FILE command to verify, for example, that you
gave the file the correct file specification, or that the file was
added properly.
If you add a swap file, such as DR3:[0,1]SWAPO.SYS,
execute the SHOW FILE/SYSTEM/SWAP_FILE command as follows:
$ SHOW FILE/SYSTEM/SWAP_FILE

Swapfile o: DR3:[0,1]SWAPO .SYS 10240 b1ks (40 jobs at 64K Swap max)
Swapfile 1 : None
Swapfile 2 : DR1:[0,1]SWAP
.SYS
256 blks ( 1 job at 64K Swap max)
Swapfile 3 : DR4:[0,1]SWAP3 .SYS 1000 blks ( 3 jobs at 64K Swap max)
$

RSTS/E prints None beside the files that do not exist. Note that the
system cannot add or remove the DECnet/E file but can only verify that
the file exists on your system.
There is no DCL command to add or
remove this file.
Refer to the SET SYSTEM and CLEAR SYSTEM commands
in the DECnet/E System Manager's Guide for further information.

Adding and Removing Overlay and Error Files
You can add and remove the overlay and error message files during
timesharing.
OVR and ERR are standardized names to denote the
separate file for the overlay code and the alternate file for the
default error message file.
Although you can use other file names,
DIGITAL recommends that you keep the standardized ones. Regardless of
the names you give the files, the system requires you to use a file
type of .SYS.
You need INSTAL privilege to use the INSTALL command.
The INSTALL/OVERLAY FILE command directs the system to use the
specified file for the system overlay code.
Similarly, the
INSTALL/ERROR_FILE command causes the system to use the specified file

12-21

Managing System Files and Logical Names
when it reads error messages.
To add these system files, specify the
commands as in the following example:
$ INSTALL/OVERLAY_FILE DU2:0VR
$ INSTALL/ERROR_FILE DBO:ERR

For the overlay file, the system copies the overlay code from the
monitor SIL to the file OVR.SYS on DU unit 2.
For the error message
file, the system copies into ERR.SYS on DB unit 0 the contents of the
error message file (ERR.ERR).
You must make sure that thel disk on
which an overlay or error file resides is mounted when you issue this
command. As with swap files, you can use the /SIZE and /POSITION
qualifiers for overlay and error files.
To install these files, the system make's sure that the files exist and
are properly formed.
If the system finds any errors, it prints the
error messages in the following format:
Error text
Error text

in INSTALL/OVERLAY_FILE
In INSTALL/ERROR_FILE

Appendix D contains the text of these errors.
If no errors occur, the
system has successfully added the file and is accessing it. You do
not need to enter any further commands.
You can remove these files at any time with the REMOVE/OVERLAY FILE
and REMOVE/ERROR FILE commands. Then, the system accesses theoriginal data. Note that the SHUTUP program automatically removes
both files.

Using the DUMP/SYSTEM Command
The DUMP/SYSTEM command lets you take an
monitor image executing in memory. When
command, RSTS/E copies the memory to the
account [0,1].
You need SYSIO privilege
command. Use the DUMP/SYSTEM command as
$

online dump of the current
you execute the DUMP/SYSTEM
crash dump file CRASH.SYS in
to use the DUMP/SYSTEM
follows:

DUMP/SYSTEM

Once the copy operation is complete, you can use the ANALYS program to
analyze the contents of the file (see Chapter 10).
The system returns the following error message if crash dump was not
enabled:
?Can't find file or account

12-22

Managing System Files and Logical Names
This can happen only if sufficient disk space was not available at
system start-up to allocate the CRASH.SYS file.
To correct this
condition, free up the necessary amount of disk space, shut down and
then restart the system.
If a user who does not have SYSIO privilege attempts to dump memory
with DUMP/SYSTEM, the system prints:
?Protection violation
Use of the DUMP/SYSTEM command may also return various device
dependent errors.
For example:
?Device hung or write locked

DCL Command Descriptions
The following sections describe the DCL commands for managing system
files and logical names.

12-23

ASSIGN/SYSTEM
ASSIGN/SYSTEM Command
The ASSIGN/SYSTEM command assigns a system-wide logical name to the
specified device type and unit.
If you include an account number, the
ASSIGN/SYSTEM command also associates that project-programmer number
with the logical name. ASSIGN/SYSTEM requires INSTAL privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Format
ASSIGN/SYSTEM dev:[p,pn] name[:]
Command Qualifiers

Defaults

/[NO]REPLACE[=QUERY]

/REPLACE=QUERY

Prompts
Device:
Logical name:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters

dey:
Specifies the device type and unit to which you want to assign a
system-wide logical name.
r.p,pn]
The optional PPN to which you want to assign a system-wide
logical name.
DCL does not allow any spaces between the device
specification and the PPN.
name [ : ]
The name that you want added to the system logical name table.
Command Qualifiers
/[NO]REPLACE[=QUERY]
Determines what action to take if the logical name already
exists. /REPLACE means replace the logical if it already exists.
RSTS/E displays an informational message.
/NOREPLACE means display an error message and do not replace the
logical if it already exists~' If neither is specified or if
/REPLACE=QUERY is specified, RSTS/E displays a warning message
and prompts to see if you want to replace the logical.
12-24

DEASSIGN/SYSTEM
DEASSIGN/SYSTEM Command
The DEASSIGN/SYSTEM command removes a specified logical name from the
system logical table.
It can also remove logical names for devices on
your system.
Device mnemonic names for system devices have permanent
entries in the logical table.
So, if you use the DEASSIGN/SYSTEM
command to remove a logical name associated with a device, only the
logical name goes away, not the device mnemonic.
You can then give a
new name to that device.
DEASSIGN/SYSTEM requires INSTAL privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I Format

I
I DEASSIGN/SYSTEM name[:]
I
I Command Qualifiers
I
I None
I
I Prompts

Defaults

I
I Logical name:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
name [ : ]
Specifies the logical name to be removed from the system logical
table.

12-25

DEFINE/COMMAND/SYSTEM
DEFINE/COMMAND/SYSTEM Command
The DEFINE/COMMAND/SYSTEM command creates or re-defines a system-wide
command (CCL).
DEFINE/COMMAND/SYSTEM requires INSTAL privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
DEFINE/COMMAND/SYSTEM command file-spec
Command Qualifiers

Defaults

/LINE_NUMBER=entry point
/[NO]PRIVILEGE
Prompts
Command:
Program name:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
command
Specifies the command you want to define.
file-spec
Specifies the file you want to associate with the command.
Command Qualifiers
/LINE_NUMBER=entry point
Defines the entry point in the command program as follows:
o

n -- Defines the entry point as the specified integer in the
range 0 to 32,767

CCL -- Defines the entry point as the CCL entry point (30000)

CHAIN -- Defines the entry point as the CHAIN entry point
(3l000)

DCL -- Defines the entry point as the DCL entry point (30500)

/[NO]PRIVILEGE
Specifies whether the program needs to retain its temporary
privileges (see Chapter 6).
12-26

DELETE/COMMAND/SYSTEM
DELETE/COMMAND/SYSTEM Command
The DELETE/COMMAND/SYSTEM command deletes the specified command from
the list of defined system-wide commands (CCLS).
DELETE/COMMAND/SYSTEM requires INSTAL privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

I Format
I
I DELETE/COMMAND/SYSTEM command
I

I Command Qualifiers
I
I

Defaults

/ALL

I
I Prompts
I

I Command:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
command
Specifies the command to be deleted from the list of defined
system-wide commands.
Command Qualifiers
/ALL
Deletes all system-wide commands.

12-27

DUMP/SYSTEM
DUMP/SYSTEM Command
The DUMP/SYSTEM command records in the CRASH.SYS file the current
state of the system so you or field service has a way to investigate
reasons for system malfunctions.
DUMP/SYSTEM requires SYSIO
privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - '- - - - - - - - - - - - - - - - - +
I

I Format
I

I DUMP/SYSTEM
I
I Command Qualifiers
I
I

Defaults

None

I Prompts

I
I None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The DUMP/SYSTEM command has no qualifiers or prompts.

12-28

INSTALL/ERROR_FILE
INSTALL/ERROR_FILE Command
The INSTALL/ERROR_FILE command installs the specified file as the
system error message file.
INSTALL/ERROR_FILE requires INSTAL
privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
INSTALL/ERROR_FILE file-spec
Command Qualifiers

Defaults

/POSITION=dcn
/SIZE=n
Prompts
Error file:

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameter
file-spec
Specifies the file to be installed as the system error message
file.
Command Qualifiers
/POSITION=dcn
Places the error file at the specified position on the disk.
You
must also specify the /SIZE=n qualifier.
The value of position
can be one of the following:
Meaning

Value
dcn

Locate the file at the first available position on
the device past the specified Device Cluster Number.

MIDDLE

Locate the file at the first available position past
the middle of the device.

INDEX

Locate the file at the first available position past
the Master File Directory (MFD) index.

/SIZE=n
Creates a system file with a size of n blocks.
The /SIZE=n
qualifier is required if the file does not already exist.
12-29

INSTALL/LIBRARY
INSTALL/LIBRARY Command
The INSTALL/LIBRARY command adds the named library to the list of
installed resident libraries.
INSTALL/LIBRARY requires INSTAL
privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Format
INSTALL/LIBRARY name
Command Qualifiers

Defaults

/[NO]ADDRESS[=n]
/[NO] ERROR_LOGGING
/[NO]LOCK
/PROTECTION=n
/[NO]READ_ONLY
/[NO] SHAREABLE
/[NO]UNLOAD

See discussion
/ERROR_LOGGING
/NOLOCK
/PROTECTION=42
/READ_ONLY
/SHAREABLE
/NOUNLOAD

Prompts
Library:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
name
Specifies the name of the library to add to the list of installed
resident libraries.
Command Qualifiers
/[NO]ADDRESS[=n]
Indicates that the resident library should be loaded into memory
in 1K-word sections beginning at address n.
Specifies the,
address in memory to load the resident library. Values can be in
the range 1K to 19l9K.
If n is omitted, RSTS/E computes the starting address by finding
the highest memory segment large enough to hold the named
library.
If this qualifier is omitted, RSTS/E computes a new
starting address each time it loads the named library into
memory.

12-30

INSTALL/LIBRARY
/[NO] ERROR_LOGGING
Indicates whether errors that occur within the resident library
should be recorded in the system error log.
The /ERROR_LOGGING
qualifier logs any errors that occur in the resident library to
the system error log.
The /NOERROR_LOGGING qualifier prevents
errors that occur within the resident library from being recorded
in the system error log. The default is /ERROR_LOGGING.
/[NO]LOCK
Indicates whether the resident library should remain in memory.
The /LOCK qualifier locks the resident library in memory.
The
/NOLOCK qualifier unlocks the resident library from memory.
The
default is /NOLOCK.
/PROTECTION=n
Sets the protection code of the resident library.
code is 42.

The default

/[NO]READ_ONLY
Indicates the allowable type of access to the resident library.
The /READ_ONLY qualifier allows read-only access to the resident
library.
The /NOREAD ONLY qualifier allows the resident library
to be mapped read/write.
The default is /READ_ONLY.
/[NO] SHAREABLE
Indicates how many users can access the resident library
simultaneously.
The /SHAREABLE qualifier lets more than one user
access this resident library at the same time.
The /NOSHAREABLE
qualifier lets only one user access the resident library at any
time.
The default is /SHAREABLE.
/[NO]UNLOAD
Indicates whether the resident library should remain in memory
wheri no jobs are using it.
The /UNLOAD qualifier removes the
resident library from memory whenever there are no jobs using it.
The /NOUNLOAD qualifier keeps the resident library in memory even
when there are no jobs using it. The default is /NOUNLOAD.

12 -.31

INSTALL/OVERLAY_FILE
INSTALL/OVERLAY_FILE Command
The INSTALL/OVERLAY_FILE command installs the specified file as the
system overlay file.
INSTALL/OVERLAY_FILE requires INSTAL privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
INSTALL/OVERLAY_FILE file-spec
Command Qualifiers

Defaults

/POSITION=dcn
/SIZE=n
Prompts

I
I
I
I
I
I
I
I
I
I
I
I
I

Overlay file:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
file-spec
Specifies the file to be installed as the system overlay file.
Command Qualifiers
/POSITION=dcn
Places the overlay file at the specified position on the disk.
The /SIZE=n qualifier is required.
The value of position can be
one of the following:
Value

Meaning

dcn

Locate the file at the first available position on
the device past the specified Device Cluster Number.

MIDDLE

Locate the file at the first available position past
the middle of the device.

INDEX

Locate the file at the first available position past
the Master File Directory (MFD) index.

/SIZE=n
Creates a system file with a size of n blocks.

12-32

INSTALL/RUNTIME_SYSTEM
INSTALL/RUNTIME_SYSTEM Command
The INSTALL/RUNTIME SYSTEM command adds the named run-time system to
the list of install~d run-time systems.
INSTALL/RUNTIME_SYSTEM
requires INSTAL privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Format
INSTALL/RUNTIME_SYSTEM name
Command Qualifiers

Defaults

/[NO]ADDRESS[=n]
/[NO] ERROR_LOGGING
/[NO] KEYBOARD_MONITOR
/[NO]LOCK
/MAXIMUM_SIZE=s
/MINIMUM_SIZE=S
/POSITION=n
/PREFIX[=x]
/[NO]READ_ONLY
/[NO] SHAREABLE
/TYPE=filetype
/[NO]UNLOAD

See discussion
/ERROR_LOGGING
/NOKEYBOARD_MONITOR
/NOLOCK
at end of list
/PREFIX=255
/READ_ONLY
/SHAREABLE
See discussion
/NOUNLOAD

prompts
Run-time system:
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
name
Specifies the name of the run-time system to be added to the list
of installed run-'time systems.
Command Qualifiers
/[NO]ADDRESS[=n]
Specifies the address in memory to load the run-time system.
The
value of n can be in the range lK to 19l9K.
If n is omitted,
RSTS/E computes the starting address by finding the highest
memory segment large enough to hold the name run-time system.
If the qualifier is omitted, RSTS/E computes a new starting
address each time it loads the name run-time system into memory.

12-33

INSTALL/RUNTIME_SYSTEM
/[NO] ERROR_LOGGING
Indicates whether the run-time system s.hould log errors occurring
under its control to the system error file.
The /ERROR_LOGGING
qualifier indicates that this run-time system should log errors.
The /NOERROR LOGGING qualifier indicates that it should not log
errors. The-default is /ERROR_LOGGING.
/[NO] KEYBOARD_MONITOR
Indicates whether the run-time system has a keyboard monitor.
The /KEYBOARD_MONITOR qualifier indicates that this run-time
system is a keyboard monitor.
The /NOKEYBOARD MONITOR qualifier
indicates that this run-time system is not a keyboard monitor.
/[NO]LOCK
Indicates whether the run-time system should reside permanently
in memory.
The /LOCK qualifier indicate~ that the run-time
system should reside permanently in memory. The /NOLOCK
qualifier indicates that the run-time system should not reside
permanently in memory. The default is /NOLOCK.
/MAXIMUM_SIZE=S
Uses s in K words as the maximum job size.
/MINIMUM_SIZE=S
Uses s in K words as the minimum size job allowed.
/POSITION=n
Places the run-time system block in position n after the primary
run-time system in the linked list. By default, RSTS/E positions
the run-time system at the end of the list. N can be any number
in the range from 0 to 255.
/PREFIX[=x]
Causes the run-time system to use the RSTS/E special prefix EMT
feature.
The value x can be any number from 0 to 255. RSTS/E
selects the code 255' by default if yoti do not specify a value for
x.
/[NO]READ_ONLY
Indicates whether the run-time system should allow read-only
memory access.
The /READ_ONLY qualifier indicates read-only
memory access. The /NOREAD_ONLY qualifier indicates read/write
memory access.
The default is /READ_ONLY.

12-34

INSTALLjRUNTIME_SYSTEM
/[NO] SHAREABLE
Indicates whether the run-time system supports multiple users.
The /SHAREABLE qualifier indicates that the run-time system
supports more than one user at the same time. The /NOSHAREABLE
qualifier indi~ates that the run-time system supports only one
job at a time. The default is /SHAREABLE.
/TYPE=filetype
Specifies the default file type for files executed under the
run-time system. By default, DeL uses the file type defined in
the run-time system file.
/[NO]UNLOAD
Specifies whether RSTS/E unloads the run-time system from memory
when no one is using it. The /UNLOAD qualifier removes the
run-time system from memory when all users are using another
run-time system or when no jobs are using the run-time system.
The /NOUNLOAD qualifier keeps the run-time system in memory even
when no jobs are using it. The default is /NOUNLOAD.

12-35

INSTALL/SWAP_FILE
INSTALL/SWAP_FILE Command
The INSTALL/SWAP FILE command adds the specified file to the list of
installed swap fIles.
Valid values of swap-index are 0, 1, or 3.
INSTALL/SWAP_FILE requires INSTAL privilege.'

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
INSTALL/SWAP_FILE[ =] swap- index file.- spec
Command Qualifiers

Defaults

/POSITION=dcn
/SIZE=n
Prompts
Swapfile number:
Swapfile name:

I
I
I
I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - -.; - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
swap-index
Specifies the index of the specified file.
1, and 3.

Valid values are 0,

file-spec
Specifies the file to add to the list of installed swap files.
You must specify the disk.

12-36

INSTALL/SWAP_FILE
Command Qualifiers
/POSITION=dcn
Places the created system file at the specified position on the
disk.
You must also specify the /SIZE=n qualifier.
The value of
position can be one of the following:
Value

Meaning

dcn

Locate the file at the first available position on
the device past the specified Device Cluster Number.

MIDDLE

Locate the file at the first available position past
the middle of the device.

INDEX

Locate the file at the first available position past
the Master File Directory (MFD) index.

/SIZE=n
Creates a system file with a size of n blocks. The /SIZE=n
qualifier is required if the file does not already exist.

12-37

REMOVE/ERROR_FILE
REMOVE/ERROR_FILE Command
The REMOVE/ERROR FILE command removes the syste~ error message file.
REMOVE/ERROR_FILE requires INSTAL privilege.
~

-------- - ---- - - - - - -- --- -- - - - - -- - - - --- -- -- - - - -- - - - - -- - ----

I
I Format
I
I REMOVE/ERROR_FILE
I
I Command Qualifiers
I
I None
I
I Prompts
I
I None
~ -

Defaults

This command has no qualifiers or prompts.

12-38

--i-

REMOVE/LIBRARY
REMOVE/LIBRARY Command

The REMOVE/LIBRARY. command removes the.named file as a resident
library. REMOVE/LIBRARY requires INSTAL privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Format
REMOVE/LIBRARY name
C.ommand Qualifiers

Defaults

None
prompts
Library:
+ - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Paramters
name
Specifies the file to remove from the list of resident libraries.

12-39

REMOVE/OVERLAY_FILE
REMOVE/OVERLAY_FILE Command
The REMOVE/OVERLAY_FILE command removes the system overlay file.
REMOVE/OVERLAY_FILE requires INSTAL privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I REMOVE/OVERLAY_FILE
I
I Command Qualifiers
I
I None
I
I Prompts
I
I None

Defaults

I
I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- --+
This command has no qualifiers or prompts.

12-40

REMOVE/RUNTIME_SYSTEM
REMOVEjRUNTIME_SYSTEM Command
The REMOVE/RUNTIME_SYSTEM command removes the named run-time system as
an entry' in the run-time system table. REMOVE/RUNTIME_SYSTEM requires
INSTAL privilege.

- - - - -- - ---- - - - - - - ------- - -- - - ---- - - - ---- -'- - -- - - - - - - ------ -;I
I Format
I
I REMOVE/RUNTIME_SYSTEM name
I
I Command Qualifiers
Defaults
I
I None
I
I Prompts
I
I Run-time system:
;- - ----------- - - --- - - - -------- - - - ------- - - - - - - - - - - - - - - - - - - --;-

Command Paramters
name
Specifies the name of the run-time system to remove from the list
of installed run-time systems.

12-41

REMOVE/SWAP_FILE
REMOVE/SWAP_FILE Command

The REMOVE/SWAP FILE command removes the specified swap file from the
list of installed swap files. Valid values of swap-index are 0, 1, or
3. REMOVE/SWAP_FILE requires INSTAL privilege.
~

--- ----- -- - ---- - - -- --- - - ----------- --- - --- - --- - -- --- ---- -

I
I Format
I
I REMOVE/SWAP_FILE[=]swap-index
I
I Command Oua1ifiers

Defaults

I
I None
I
I Prompts
I
I Swapfile number:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --~

Command Parameters

swap-index
Specifies the index of the swap file to remove.
0, 1, or 3.

12-42

Valid values are

SET·FILE
SET FILE Command
The SET FILE command changes the characteristics of the specified
file(s).
SET FILE requires read and write access to the file(s).
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
SET FILE file-spec
Command Qualifiers

Defaults

/[NO]CACHE
/NOCONTIGUOUS
/[NO]DELETABLE
/[NO]LOG
/[NO]PLACED
/PROTECTION=n
/RUNTIME_SYSTEM=name

/DELETABLE
/NOLOG

Prompts
Files:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Parameters
file-spec
Specifies the file whose characteristics you want to change.
Command Qualifiers
/[NO]CACHE[={SEQUENTIALIRANDOM}]
The /CACHE qualifier specifies that the file is automatically
cached when open. The type of caching depends on the file's UFD
entry and the specified OPEN MODE.
If you use /CACHE alone on a
file with no UFD setting or MODE specification, the default is
random caching.
TUNE privilege is required to use this
qualifier.
The optional arguments are:
o

SEQUENTIAL -- Causes RSTS/E to mark the file's UFD entry such
that, if the file is cached, it is cached sequentially.

RANDOM -- Causes RSTS/E to mark the file's UFD entry so, if
the file is cached, it is cached randomly. Note that you can
override the random cache UFD setting with a sequential
caching MODE specification.

12-43

SET FILE
The /NOCACHE qualifier specifies that the file is not
automatically cached when open.
To cache such a file, you must
specify SET CACHE/ALL or specify a MODE value (see the RSTS/E
Programming Manual).
/NOCONTIGUOUS
Lets you extend a contiguous file by changing it to
noncontiguous.
/[NO]DELETABLE
Indicates whether a file can be deleted or renamed during
timesharing.
In a directory listing, RSTS/E shows NODELETABLE
files with the flag P (protected) after their size. You need
SYSIO privilege to use this qualifier.
The default is
/DELETABLE.
/[NO]LOG
Indicates whether the file specification of each modified file is
displayed at the terminal.
If the file specification contains
any wildcards, the default is /LOG.
Otherwise, the default is
/NOLOG.
/[NO]PLACED
Indicates whether, after modification, a file is placed at its
present position on the disk.
/PROTECTION=n
Sets the protection code of a file.
The protection code must be
in the range 0 to 255.
You can also use the SET PROTECTION
command to perform this function.
You need SYSIO privilege to
set the privilege bit of the protection code.
/RUNTIME_SYSTEM=name
Associates a run-time system with the file.
The file-spec can be
any valid RSTS/E file specification. When the system tries to
execute this file, it uses the named run-time system to load the
executable file.
You need SYSIO privilege to use this qualifier
for file(s) whose protection code is 192 or higher.

12-44

SHOW COMMAND/SYSTEM
SHOW COMMAND/SYSTEM Command
The SHOW COMMAND/SYSTEM command displays information about the
specified system-wide command. SHOW COMMAND/SYSTEM requires INSTAL
privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SHOW COMMAND/SYSTEM command-name
I
I Command Qualifiers
I
I /ALL
I
I Prompts
I

Defaults
/ALL

I None

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Parameters
command-name
Specifies the system-wide command whose information you want
displayed.
If you do not include this parameter, RSTS/E displays
all system commands.
Command Qualifiers
/ALL
Displays information about all the system-wide commands.

12-45

SHOW FILE/SYSTEM
SHOW FILE/SYSTEM Command
The SHOW FILE/SYSTEM command displays information about the specified
system file(s).
The default is /ALL.
SHOW/FILE/SYSTEM does not
require any privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
SHOW FILE/SYSTEM
Command Qualifiers

Defaults

/ALL
/ERROR_FILE
/NETWORK_FILE
/OVERLAY_FILE
/SWAP_FILE[=swap-index]

/ALL

all swap files

Prompts
None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Qualifiers
/ALL
Displays information about all installed files.

Displays information about the system error message file.
/NETWORK_FILE
Displays information about the network database file.
/OVERLAY_FILE
Displays information about the system overlay file.
/SWAP_FILE[=swap-index]
Displays information about the specified swap file, where
swap-inde~ is 0, 1, or 3.
If no argument is given, RSTS/E lists
all swap files.

12-46

SHOW LIBRARY·
SHOW LIBRARY Command
The SHOW LIBRARY command displays information about all installed
libraries.
SHOW LIBRARY does not require any privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SHOW LIBRARY
I
I Command Qualifiers
I
I None
I
I Prompts
I
I None

Defaults

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The SHOW LIBRARY command has no qualifiers or prompts.
The following is an example of the SHOW LIBRARY display:
$

SHOW LIBRARY

~esident

Libraries:
Acct
Name Prot
HISTOG < 42>
1,2
[
]
]
CSPLIB < 42> DRl: [ 0,1
RMSRES < 42> DRl: [ 0,10 ]
RMSLBB < 42> DRl: [ 0,10 ]
RMSLBA < 42> DRl: [ 0,10 ]
RMSLBD < 42> DRl: [ 0,10 ]
RMSLBC < 42> DRl: [ 0,10 ]
RMSLBE < 42> DRl: [ 0,10 ]
RMSLBF < 42> DRl: [ 0,10 ]
DAPRES < 42> DRl: [ 0,10 ]
EDT
< 42> DRl: [ 0,11 ]
B2MRES < 42> DRl: [ 0,1
]

Size
36K
8K
4K
3K
4K
2K
2K
3K
4K
10K
38K
19K

12-47

Users
0
8
1
1
0
0
0
0
0
0
1
0

Comments
Perm, Addr:1628
Temp, Addr:117
Temp, Addr:1624
Temp, Addr:1621
Temp, Addr:1617
Temp, Addr:161S
Non-Res, Addr:1613
Temp, Addr:1610
Temp, Addr:1606
Temp, Addr:876
Temp, Addr:lS68
Temp, Addr:830

SHOW LOGICALS
SHOW LOGICALS Command
The SHOW LOGICALS command displays information about a user-defined
logical name.
SHOW LOGICALS does not require any privilege.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
SHOW LOGICALS name
Command Qualifiers

Defaults

/ALL

Prompts
None

I
I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - _. _. - - - .'- - - - - - - - - - - - - _. - - - - - - - - - - _. - - - - - - - - - - - - - --+

Command Parameters
name
Specifies the user-defined logical name whose information you
want displayed.
Command Qualifiers
/ALL
Displays information about all user-defined logical names.

12-48

SHOW LOGICAL/SYSTEM
SHOW LOGICAL/SYSTEM Command
The SHOW LOGICAL/SYSTEM command displays information about a
system-wide logical name. You need SYSIO privilege to use SHOW
LOGICAL/SYSTEM.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
SHOW LOGICAL/SYSTEM name
Command Qualifiers

Defaults

JALL

/ALL

Prompts

I
I
I
I
I
I
I
I
I
I
I
I

None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
name

Specifies the system-wide logical name whose information you want
displayed.
Command Qualifiers
/ALL
Displays information about all system-wide logical names.

12-49

SHOW RUNTIME_SYSTEM
SHOW RUNTIME_SYSTEM Command
The SHOW RUNTIME SYSTEM command displays information about all
installed run-time systems.
SHOW RUNTIME_SYSTEM does not require any
privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ',:. - - - - - - - - - - - - - - - - - - - - - - -+
Format
SHOW RUNTIME SYSTEM
Command Qualifiers

Defaults

None
Prompts

I
I
I
I
I
I
I
I
I
I
I
I

None
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

The SHOW RUNTIME_SYSTEM command has no qualifiers or prompts.
following is an example of the display:

The

$ SHOW RUNTIME_SYSTEM
Run~Time

Name
... RSX
RSX
DCL
RT11
TECO
BAS4AL
BAS4F
BASIC
FORTH
GMBODT
MOMODT

Systems:
Ext Dev
TSK
TSK DR1:
COM DR1:
SAV DR1:
TEC DR1:
BAC DR1:
BAC DRl:
BAC DRl:
4TH DRl:
COM ORO:
COM ORO:

Size
Users
0(64)K 14
o
1(28)K
28(4)K
8
4(28)K
o
10(20)K
o
o
17(12)K
o
16(16)K
l5(16)K
1
6(24)K
o
27(4)K
o
27(4)K
1

Comments
Monitor
Primary, Perm, Addr:76, KBM
Temp, Addr:77, OF KBM
Temp, Addr:l09, KBM, CSZ, EMT:255
Temp, Addr:383, KBM
Non-Res, KBM, CSZ
Temp, Addr:322, KBM, CSZ
Temp, Addr:133, KBM, CSZ
Temp, Addr:125, KBM, NER, CSZ
Non-Res, Addr:154l, KBM, IUS, R/W
T,emp, Addr: 849, KBM, IUS, R/W, NER

12-50

UNLOAD/LIBRARY
UNLOAD/LIBRARY Command
The UNLOAD/LIBRARY command removes the resident library you specify
from memory. UNLOAD/LIBRARY requires the INSTAL privilege.
-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --r

Format
UNLOAD/LIBRARY name
Command Oua1ifiers

Defaults

None
Prompts
Library:
-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---r

Command Parameters
name
Specifies the name of the resident library to remove from memory.

12-51

UNLOAD/RUNTIME_SYSTEM
UNLOAD/RUNTIME_SYSTEM Command
The UNLOAD/RUNTIME SYSTEM command unloads the named run-time system
from memory. UNLOAD/RUNTIME SYSTEM requires the INSTAL privilege.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I UNLOAD/RUNTIME_SYSTEM name
I
I Command Qualifiers
I
I None
I
I Prompts
I

Defaults

I Run-time system:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

Command Parameters
name
Specifies the name of the run-time system to remove from memory.

12-52

Chapter 13
Job z.1anagement

This chapter describes the DCL commands that you use to manage RSTS/E
jobs. Table 13-1 summarizes these commands.
The rest of this chapter
explains the commands in detail and gives examples of their use.
Table 13-1:

DCL Commands for Job Management

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
I
Description
I

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
ATTACH
I Attaches a terminal to a job.
BROADCAST
DETACH
FORCE

I
I Displays a message at the specified
I destination(s).
I
I Detaches a job from its terminal.
I
I Forces a "string" to the specified
I destination(s).

HANGUP

Disconnects the specified remote line.

Creates a job at the specified terminal, logs
your current job in under a different
account, or resets your current job to its
initial logged-in state.

REMOVE/JOB

Immediately terminates the specified user job
and logs it off.

SET JOB

Defines the characteristics of a job.

SET SYSTEM

Sets the default system characteristics.

SHOW JOB/PRIVILEGE

Displays the set of current privileges for
the current job.
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
13-1

Job Management
Controlling the Number of Logged-In Jobs
You can monitor and control system operation while logged in to a
RSTS/E system. With the SYSTAT or the DISPLY system program, you can
observe how the system is performing. If performance declines, you
can remedy the problem, in some cases, by preventing more users from
logging in to the system. You adjust the number of logged-in jobs
allowed with the SET SYSTEM/LOGINS, and SET SYSTEM/NOLOGINS commands.
SET S¥STEM/NOLOGINS sets to one the number of jobs that are allowed to
log ip to the system. After RSTS/E executes the SET SYSTEM/NOLOGINS
command, the system allows no more users to log in to the system. If
a user attempts to log in or to execute a logged-out command, the
monitor prints the following error message:
?No logins
Jobs already logged in to the system can continue running. However,
jobs such as BATCH that create logged in jobs c~nnot successfully
process further requests. (The SHUTUP system program also disables
further logins in preparing to shut down timesharing.)
To keep you from being locked out of the system, RSTS/E allows jobs to
be logged in at the system console terminal (KBO:), regardless of the
number of logins currently allowed.
(This feature is a special
characteristic of the terminal you designate as the system console;
the default is KBO:. By inst~lling a feature patch, you can change
the terminal which has this characteristic. However, only one
terminal on a system can have this capability.) This capability
remains in effect as long as a job slot is available to handle a new
job. You need SWCTL privilege to use the SET SYSTEM/NOLOGINS command.
The SET SYSTEM/LOGINS command places a ceiling on the number of users
that can log in to the system. This command is useful for limiting or
extending the load allowed on the system. For example:
$ SET SYSTEM/LOGINS=35
$

This command limits the number of logins to 35; if there are 35 or
more users logged in to the system, the next user who tries to log in
gets the error message ?No logins and must wait until enough users log
off before being allowed to log in.
The system does not let you set the number of logins to zero or to a
number greater than the value of JOB MAX set at system installation
time. If you specify zero in the command, RSTS/E sets the number to
one. The default number is JOB MAX. You need SWCTL privilege to use
the SET SYSTEM/LOGINS command.
The number of logins allowed can never exceed the capacity of the swap
space installed on the system or the value specified during system
13-2

Job Management
generation.
If you enter a number greater than the maximum allowed,
RSTS/E sets logins to the maximum possible.
The free buffer status
report of SYSTAT or the DISPLY program includes the maximum number of
logins currently allowed.
You normally use the SET SYSTEM/LOGINS command with the
INSTALL/SWAP FILE command to adjust the number of logins allowed.
After you add swap space to the system, the SET SYSTEM/LOGINS command
performs these steps:
1.

Recalculates the swap capacity

Factors in the currently allowed maximum swap size (SWAP MAX)

Increases the number of allowed logins

If you are preparing to remove swap space, use the SET SYSTEM/LOGINS
command to decrease the number of allowed logins.

Broadcasting Messages to Terminals
The BROADCAST command lets you communicate with one user or with all
users on the system.
You need SEND privilege to execute the BROADCAST
command.
This command places a specified text string in the output
buffer of a terminal, or of all terminals, and displays the text on
the terminal.
For example, if a user at terminal KB32: assigns a
peripheral device for an unreasonably long time, you can send a
message asking the user to deassign the device:
$ BROADCAST 1<B32: "Bob, can you deassign Ml·l0: for me j
AS1>l.P. "

I need it

By specifying /LOGGED IN instead of a terminal designator, you can
broadcast the message-to each online terminal in the RSTS/E system
(unless the terminal is set for NOBROADCAST).
For example:
$ BROADCAST/LOGGED_IN "Read $NOTICE.TXTj the system is coming
down! ! "
$
The system displays your message as follows:

*** From [1,214] "Account Name" on KB25: at 02:17 PM 27-May-85
** Read $NOTICE.TXTj the system is coming down!!
\

This message appears on all terminals that are on line and set to
BROADCAST, except your own.

13-3

Job Management
You can direct your message to specific users by substituting a PPN
for the destination specification. Wildcard characters are also
permissible. For example, to broadcast a message to all users logged
in under the same project number:
$ BROADCAST [20,*] "Please attend a meeting at 3:00 PM today"

You can send a multiline message with BROADCAST as follows:
1.

Press RETURN after the destination specification.
displays the prompt Message: on your terminal.

RSTS/E

Enter your message, terminate each line by pressing RETURN.

Enter CTRL/Z to send your message.

In a multiline message, you do not need to enclose the message in
quotes. For example:
$ BROADCAST/ALL<RET>
Message: The power will be shut off in the building this
weekend.<RET>
Message: Therefore, this system will be taken down Friday
night.<RET>
Message: No logins will be allowed after 5PM on Friday.<RET>
Message: <CTRL/Z>
$

Controlling Jobs
The FORCE command lets you send a text string to another terminal (or
all terminals). You need SYSIO privilege to use the FORCE command.
The system places the text string in the input buffer of the specified
terminal as if it were typed by the user. The command has the format:
FORCE destination "command"
If you want to send a CTRL/C to a terminal, KB32 in this case, to stop
the execution of whatever is running at the terminal and then to log
the user off the system, type:
$ FORCE KB32:
$

,,'" LOGOUT"

The circumflex (~) character before the command forces a CTRL/C to the
terminal, and the LOGOUT command logs the user off the system.

13-4

Job Management
You can also send only a CTRL/C (~C) to a terminal by placing a
circumflex character in the first position after the keyboard number.
For example:
$ FORCE KB32:
$

II~

Do not place any text after the circumflex if you want to send only a
CTRL/C to the terminal to stop the job that is running. RSTS/E sends
a CTRL/C to the terminal and returns control to the keyboard monitor
prompt.
For example:
... C

To force a control character combination (CTRL/Z for example) to a
terminal, enter the circumflex (~) character as the first character of
the text, followed by the proper control letter (such as Z).
For
example:
$ FORCE KB32:
$

II'"

Typing ~Z and pressing RETURN executes a CTRL/Z at KB32: No other
text should follow the control character combination.
If the
circumflex (~) is the first character of more than two characters of
text, however, RSTS/E forces a CTRL/C to the terminal before sending
the text that immediately follows the first character.
For e~ample:
$ FORCE KB32:
$

II"

!Harry, sorry but your job is out of control!"

The ... c characters appear on Harry's terminal to end the job he was
running and the system prints the text of the message on the following
line.
(The text after the first character can contain up to 80
characters.)

Removing Jobs
The REMOVE/JOB command lets you terminate a user's job and remove it
from the system. You need JOBCTL privilege to use the REMOVE/JOB
command. Before using REMOVE/JOB, use the SHOW USER command to learn
the user's job number, then type:

$ REMOVE/JOB 10
$

The monitor clears job 10 and frees it for other system use.
The user
is no longer logged in to the system and must log in again before
13-5

Job Management
attempting any other system activity. ;Use the SHOW USER command
immediately after issuing the REMOVE/JOB command to verify that the
job is no longer on the system.

Placing a Job on HOLD
There are times when you do not want to terminate a job, but rather
want to place it in a hold state, a state from which it can resume
normal processing. A job may be using up too many system resources,
or you may be running a batch job that you need to correct. The SET
JOB/HOLD command automatically sets the priority of a job to -128.
This causes the system to stop giving the job any time to run. Use
the SET JOB/HOLD command as follows:

$ SET JOB/HOLD 10
$
Job 10 stops processing but does not terminate.
SET JOB/HOLD always
sets the priority to -128, which means you cannot include a priority
number with the command. You must reset the priority of the job to
-120 or higher with the SET JOB/RELEASE command to reactivate the job.
Use the SET JOB/RELEASE command as follows when you want to restart
the job:

$ SET JOB/RELEASE 10
$
Now job 10 has the default priority of -8, which under normal system
load allows the job to successfully run to completion.
SET JOB/HOLD and SET JOB/RELEASE are the logical commands to use when
you want to stop a job temporarily and then start it again. You need
TUNE privilege to use the SET JOB/HOLD or the SET JOB/RELEASE
commands.

Setting Job Priority, Run Burst, and Maximum Size
The system lets you set the priority, run burst, and maximum size of
an existing job. You can change any of the current values to:
o

Increase or decrease the chance of gaining run time in
relation to other running jobs

Determine how much CPU time the job can have when it is
compute bound

Increase the area a job can occupy

13-6

Job Management
The system runs jobs on the basis of priority. The higher a job's'
priority, the better its chances of obtaining run time in relation to
other jobs that are running. Figure 13-1 shows how an 8-bit priority
byte determines priority.
x

Sign
Bit
Figure 13·1:

System-Definable
Portion

User-Definable
Portion
priority Byte Format

Using the SET JOB/PRIORITY command, you or another user can set the
user-definable portion of the priority byte for any job on the system.
Because the three system-definable bits are normally zero, standard
priorities are multiples of 8 between -120 (lowest priority) and +120
(highest priority). Zero is a legal priority. When the system
changes a priority, it truncates any value not a multiple of eight to
the next lowest legal priority. For example, if you specify a
priority of +10, RST/E sets the value to +8.
You need TUNE privilege to use the SET JOB/PRIORITY command.
All of the system-definable bits are normally off (zero). The least'
significant bit is set when a keyboard delimiter is typed and the job
is waiting for keyboard input or when any I/O completes. Keyboard
delimiters are Carriage Return (CR), Line Feed (LF), Form Feed (FF),
Control Z (CTRL/Z), and Escape Sequence Character (ESC). The next
significant bit is set whenever a CTRL/C is entered and can be set at
any time. Finally, a system function call sets the most significant
bit of the system-definable portion. RSTS/E clears all
system-definable bits when it chains to another program or when the
job is at the system command level.
The system-definable portion of the priority byte is always less
significant than the user-definable portion. Therefore, the
system-definable bits affect priority only within the user-definable
priority range. For example, if two jobs are running under priority
-8, the user who enters a CTRL/C has a higher priority (that is,
priority -6 in this case) than the user who does not. However, a
third user with priority 0 supersedes two users whose priorities are
-8 and -6.
When you log in, LOGIN runs with priority 0 and automatically sets
your job to priority -8. This is the default priority with which most
or all jobs are run. Do not assign priorities other than -8 except in
unusual circumstances (for example, compute-bound or detached jobs).

13-7

Job Management
On occasion, you may want to run a program that requires a great deal
of computation.
If time is nota factor in obtaining results, and you
have TUNE privilege, you can decrease the job priority of the
compute-bound job to improve efficiency for the other users on the
system.
On the other hand, infrequently used detached programs often
have higher priorities (typically priority 0) because they must run
quickly when needed but do not run compute bound for an extended
period and do not run often.
Run burst is the maximum time a job can run compute bound before
another job obtains access to the cPU.
On systems using the KWllL
line frequency clock, each unit of run-burst time is equal to 1/60th
or l/50th of a second, depending on the system's power line frequency.
Systems running with' the KWllP clock at crystal speeds, rather than at
line frequency, have a run-burst unit of 1/50th of a second.
If the
system is operating from a 60 Hz power line, one run-burst unit equals
1/60th of a second.
In that case, six units equal l/lOth of a second,
which is the run-burst default value.
If you assign a run burst of, six to a specific job that does not
require much compute-bound time, the system automatically transfers
control to the next user before the six units have been used. One
tenth of a second is generally considered the best run-burst time
period to ensure efficient overall system operation.
If a job is
guaranteed to become I/O bound (that is, I/O stalled) after a certain
amount of computation, use SET JOB/RUN_BURST to specify a run burst
larger than six.
In many cases, a run burst greater than six has a
significant effect on long computational programs.
Their percentage
of the overall cPU time would be increased.
You need TUNE privilege to use the SET JOB/RUN_BURST command.
The maximum size assigned to a job refers to the allowable memory
space.
You can let certain jobs run programs larger than 16K words by
assigning a job a maximum size up to 32K words (64K words for systems
with I/O space).
This assigned limit does not affect privileged,
compiled programs. Thus, a user with a small amount of space can
still run system programs that would normally exceed the memory limit.
To alter the maximum job size of job 14, use the SET JOB/SIZE command
as follows:
$ SET JOB/SIZE=32 14

You need the TUNE privilege to use the SET JOB/SIZE command.

13-8

Job Management
Controlling Keyboards and Remote Lines
If you determine that a dataset line is in use but no keyboard
activity is taking place (by using SYSTAT or the DISPLY program job
status report), you can disconnect the dataset. The HANGUP command
disconnects the remote line specified by the KBn: keyboard. The
hangup capability prevents a user from monopolizing the line without
being charged for connect time and frees the line for other remote
users. You need HWCTL privilege to use the HANGUP command.
The DETACH command frees a terminal from its job. If the job does not
have the terminal open on a nonzero channel, DETACH frees the terminal
for other use. The command normally forces the system to close all
nonzero channels on which the terminal is open. The /NOCLOSE switch
suppresses this action. When the job specified is currently detached,
the monitor prints the error message:
?Job number x is already detached.
You need JOBCTL privilege to use the DETACH command (except for your
current job).

DCL Command Descriptions
The following sections describe the DCL commands that you can use for
job management.

13-9

ATTACH
ATTACH Command
The ATTACH command attaches a terminal to a job.
not require any privileges.

This command does

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I ATTACH n
I
I Prompts
I
I Job number:

I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
n

The number of the job you want to attach to.

13-10

BROADCAST
BROADCAST Command
The BROADCAST command sends a message to:
o

A specified terminal (KBn:)

All users logged in under a specified PPN (the PPN can
contain wildcard characters)
Note
This command displays a message only on terminals
that are not set to NOBROADCAST.

You need SEND privilege to use BROADCAST.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
BROADCAST destination ["message"]
Command Qualifiers

Defaults

/ALL
/[NO]BELL
/[NO]HEADER
/LOGGED_IN

/NOBELL
/HEADER

Prompts

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

To:
Message:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Parameters
destination
The device(s) where the message is to be displayed.
"message"
The message to be displayed on the destination device(s).
If you
type RETURN after entering the destination specification, DeL
prompts you for each line of a message.
Enter CTRL/Z to send the
message. Note that when you enter a multi-line message in this
way, do not enclose the message in quotes.

13-11

BROADCAST
Command Qualifiers
/ALL
Broadcasts the message to all terminals.
/[NO]BELL
Broadcasts a ·BELL character before the message.
/NOBELL.

The default is

/[NO]HEADER
Broadcasts a header before the message.
format:

The header is in the

From ARK::[1,194] "Account Name" on KB52: at 11:52 AM 30-May-85
The default is /HEADER.

Broadcasts the message to all logged-in terminals.

13-12

DETACH
DETACH Command
The DETACH command detaches a job from its terminal. You need JOBCTL
privilege to detach any job other than your current job.

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
DETACH n
Command Qualifiers

Defaults

/[NO]CLOSE

/CLOSE

Prompts
Job number:
+ - - - - - - - -.- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -' ~ - - - - - - - - - - - - - +

Command Parameters
n

The number of the job you want to detach from its terminal.
Command Qualifiers
/[NO]CLOSE
Indicates whether the system closes all nonzero channels on which
the job's terminal is open before detaching. The default is
/CLOSE.

13-13

FORCE
FORCE Command
The FORCE command forces a string to:
o

A specified terminal

All users logged in under a specified PPN.
contain wildcards.

The PPN can

You need SYSIO privilege to use FORCE.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

I
I Format
I
I FORCE destination "string"
I
I Command Qualifiers
I
I /ALL
I /LOGGED_IN
I
I

Defaults

Prompts

I
I To:
I .Command:
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
destination
The device(s) that you want the "string" forced to.
"string"
The string that you want forced to the destination device(s).
Command Qualifiers
/ALL
Forces the string to all terminals.
/LOGGED_IN
Forces the string to all logged-in terminals.

13-14

HANGUP
HANGUP Command
The HANGUP command disconnects the specified remote line.
HWCTL privilege to use HANGUP.

You need

+ •••••••.••.• - - - - - - - - - • - - - - • - - - • - - - • - • - - - - - - - - - - - - - - - - - - - - -+

I
I Format
I
I HANGUP KBn:
I
I Prompts
I
I Keyboard:

I
I
I
I
I
I
I
I

+ - - - - - - - - - - - . - - - - - - - - - - - - - - - - - - - - - - - • - •• ,•••• - - - - - - - - - - - - - - -+

Command Parameters
KBn:
Specifies the remote line you want to disconnect.

13-15

Create a new job at the specified terminal. You can use this
feature in your system start-up procedure to log in various
users automatically. You need WACNT or GACNT privilege to
create a new job. If the terminal is restricted, you also
need DEVICE privilege.

Log your current job in under a different account. This
feature lets you switch between accounts without having to
first issue the LOGOUT command (see RSTS/E System User's
Guide).
You need WACNT or GACNT privilege to log in to a
different account without being prompted for that account's
password.

Reset your current job to its initial logged-in state (the
state your job was in after logging in). This feature is
useful for resetting logical assignments, DCL symbols,
prompts, and so on to their initial state. This feature does
not require any privilege.

- ----- - --- - - - - ---- - - ------ - --------- - - - - -- - ----- - - --- - -- - -;-

I Format
I
I LOGIN [p,pn]
I
I Command Qualifiers

I
I

Defaults

/[NO]OVERRIDE[=NOLOGINS]

/NOOVERRIDE

I /TERMINAL=terminal[:]
Your terminal
I
I Prompts
I
I Password:
~ --- -- - - - ---- - - - - --------- - - - - ---- - - -- - - ------ - -- - - - -- - - - - -~
Command Parameters
[p,pn]
The PPN for the account you want to log in to.
is your PPN.

13-16

The default PPN

LOGIN
Command Qualifiers
/OVERRIDE[=NOLOGINS]
/NOOVERRIDE
Indicates whether to create the new job if logins are currently
disabled.
Specify /OVERRIDE or /OVERRIDE=NOLOGINS to create the
new job even if logins are disabled'.
If you attempt to create a
new job with the /NOOVERRIDE qualifier and logins are disabled,
the monitor displays an error message. The default is
/NOOVERRIDE.
The /OVERRIDE qualifier requires that you also specify the
/TERMINAL qualifier.
NOTE
Even with /OVERRIDE in effect, you cannot create
a new job unless there are job slots available on
the system.
/TERMINAL=terminal[:]
Indicates that a new job should be created at the specified
terminal.
The terminal argument can be any valid device name
that refers to a keyboard device.
If the terminal you specify is
restricted, you must have DEVICE privilege. You must have WACNT
or GACNT to log in to another account on the specified terminal.
Examples
The following examples show the different features of LOGIN.
your job to its initial logged-in state, enter:

To reset

$ LOGIN

To log in to account [10,10] after you correctly supply the password
for that account:
$ LOGIN [10,10]
Password:

If you have WACNT or GACNT privilege and you are switching from any
[10,*] account, the monitor does not prompt you for the password.
To log in user [100,3] at terminal KBl1: enter the following:
$ LOGIN/TERMINAL=_KBll:

[100,3]

You must have WACNT privilege, or have GACNT privilege and be logged
in to [100,*] account to execute the previous command.

13-17

REMOVE/JOB
REMOVE/JOB Command
The REMOVE/JO~ command immediately terminates the specified user job
and logs it out. You need JOBCTL privilege to use this command.
+ - - - - - - - - - - - - - - - - - - - •• - • -' ~ - - - ••• '•• - .'. ~,;~, ~ '•••• - - ~ • - - - - - - ~ • - - •. +

I
I
I
I
I
I
I
I

Format
REMOVE/JOB n
Prompts

Job number:
+-. _. -. - - _. _•• - - - _•.•.•• _.•..• - - - _. _•... - - - - - - - - _. - - - _. - - --+
Command Parameters
n

Specifies the job to remove.

13-18

SET JOB
SET JOB Command
The SET JOB command defines the characteristics of the specified job.
The /KEYBOARD_MONITOR and /PRIVILEGE qualifiers can only be used for
the current job.
If you specify those qualifiers with a job number
other than your own, RSTS/E displays the following error message:
?Only current job allowed.
You need TUNE privilege to use any of the qualifiers except
/KEYBOARD_MONITOR and /PRIVILEGE.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I
I

Format
SET JOB n
Command Qualifiers

Defaults

/HOLD
/KEYBOARD_MONITOR[=name]
/PRIORITY=p
/PRIVILEGE=(priv,priv, ..• )
/RELEASE
/RUN_BURST=q
/SIZE=q

No change

Prompts
None
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
n

Specifies the job whose characteristics you want to define.

13-19

SET JOB
Command Qualifiers
/HOLD
Sets the priority of job n to -128.
used for the current job.

This qualifier cannot be

/KEYBOARD_MONITOR[=name]
Sets the current job's keyboard monitor to name. The allowable
values of name are any installed run-time system that has a
keyboard monitor. Use the SHOW RUNTIME SYSTEM command to list
the run-time systems on your system.
II you omit the optional
argument, the system default keyboard monitor becomes the current
job's keyboard monitor.
/PRIORITY=p
Sets the priority of the specified job. Priority can be any
number from -128 to +120.
The system rounds the priority down to
a multiple of eight.
(For example, if you select a priority of
-19, the system sets the priority to -24.)
/PRIVILEGE=(priv,priv, ... )
Modifies the set of current privileges for the current jbb only.
/RELEASE
Resumes job n at priority of -8.

Changes the run burst of the specified job to q.
can be any number from 1 to 127.

The value for q

/SIZE=q
Changes the maximum size of the specified job to q.
q to a maximum of 32K.

13-20

You can set

SET SYSTEM
SET SYSTEM Command
The SET SYSTEM command sets the default system characteristics.
need SWCTL privilege to use the SET SYSTEM command.

You

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

Format
SET SYSTEM
Command Qualifiers

Defaults

/[NO]LOGINS[=n]

See Discussion

prompts
None

I
I
I
I
I
I
I
I
I
I
I
I

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---r

Command Qualifiers
/[NO]LOGINS[=n]
Defines the maximum number of users who can log in to the system
at one time.
Set /LOGINS=n to the number of user jobs that can
log in to the system at one time. The default is JOB MAX.
Specify /NOLOGINS if you want to ~revent users from logging in to
the system by setting the number of 10gins to one.
See Chapter 14 for additional SET SYSTEM command qualifiers.

13-21

SHOW JOB/PRIVILEGE
SHOW JOB/PRIVILEGE Command
The SHOW JOB/PRIVILEGE command displays the set of current privileges
for the specified job. You need JOBCTL privilege to display the
privileges of another job.

------ ---- --- - ---- -- ---- --- - ------ -- ---- -- --- --- --- -- -- -- -~
I
I
I Format
I
I
I
I SHOW JOB/PRIVILEGE [n]
I
I
I
I Prompts
I
I
I
I None
I
~ --- --- --- - --- -- - -- - - - -- ---- ---- - -- --- - - - - - -- - - ---- -- - -- -- -~

Command Parameters
[n]

Specifies the job whose current privileges you want to display.
The default is the current job.

13-22

Chapter 14
Miscellaneous System Management Functions

This chapter describes miscellaneous DCLcommands that you use to
manage your RSTS/E system. Table 14-1 summarizes the DCL commands
available to you.
The rest of this chapter explains each command in
more detail.
.
Table 14-1:

DeL Commands for Miscellaneous System Functions

+- - - - - - - - - - - - - - - -+- -. - - - - - -. - _. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
I
Description
+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

LOAD/OVERLAY

Loads one or more monitor overlays in memory.

SET DATE

Sets the RSTS/E system date to the value you
specify. Optionally, you can specify a new value
for the system time.

SET SYSTEM

Sets the default system characteristics.

SET TIME

Sets the RSTS/E 24-hour clock to the value you
specify. Optionally, you can set the system date
to the value you specify.

SHOW SYSTEM

Displays the system-default characteristics.

UNLOAD/OVERLAY
Unloads one or more monitor overlays from memory.
+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Loading and Unloading Monitor Overlays
The LOAD/OVERLAY and UNLOAD/OVERLAY commands let you load and unload
monitor overlays during timesharing. You can use these commands in
conjunction with the DISPLY program and the SHOW CACHE command to

14-1

Miscellaneous System Management Functions
monitor the effects on your system's performance of making certain
overlays resident or nonresident.
The monitor overlays that you can specify with these commands are:
o

ATTRIBUTE -- Performs file and account attribute read/write
operations

DCL -- Performs file-related operations for DCL

DELETE RENAME -- Performs file deletion and renaming

DIRECTORY -- Performs disk file lookup operations

SYSTEM CALLS -- Performs specific monitor directives

TERMINAL -- Performs terminal attribute read/write operations

Suspending System Operations
The SET SYSTEM/HOLD and SET SYSTEM/RELEASE commands let you
temporarily suspend all disk I/O and other system operations. When
you issue the SET SYSTEM/HOLD command, all jobs on the system are
suspended, except for the job issuing the command. Operations resume
when you issue the SET SYSTEM/RELEASE command.
The SET SYSTEM/HOLD and SET SYSTEM/RELEASE commands are used primarily
on systems where the system disk is an RC25.
The main reason for
using these commands is to suspend operations when you need to stop
the fixed disk drive so you can mount a different disk cartridge (both
disks share the same spindle). With SET SYSTEM/HOLD and SET
You need
SYSTEM/RELEASE, a total system shutdown is not necessary.
HWCTL privilege to use the SET SYSTEM/HOLD and SET SYSTEM/RELEASE
commands.
To use the commands, type:
$ SET SYSTEM/HOLD
System now on hold
$

The system displays the message System now on hold to show that the
suspend is in effect. When the disk stops, you can change the
removable cartridge. When you are ready to resume system operations,
type:
$ SET SYSTEM/RELEASE
System released
$

14-2

Miscellaneous System Management Functions
Changing System Date and Time
The SET DATE and SET TIME commands let you change the system date and
the 24-hour clock. These commands are important on systems where
strict accounting data is kept and incorrect values may have been
entered at system start-up time.
You can enter the date in either of
two formats:
SET DATE dd-mmm-yy
SET DATE yy.mm.dd
The following example shows how to enter the date using the first
format:
$

SET DATE 30 -~lAY- 85

You can enter the same date in the second format as well:
$

SET DATE 85.05.30

Be sure to place a space between the DATE command and the beginning of
the date field when entering a date with either format.
You need
DATES privilege to use the SET DATE or SET TIME command.
You can enter the time in either of two formats:
SET TIME 01:30PM
SET TIME 13:30
You change the date and/or the time with either command as follows:
For SET DATE;
$
$

SET DATE 30-NAY-8S
SET DATE 30-MAY-8S:01:30PM

For SET TIME;
$
$

SET TINE 01:30PM
SET TIME 30-MAY-8S:01:30PM

Note that when you specify both parameters, you must first enter the
date and separate the two parameters with a colon.
You can also specify a relative date and time with the SET DATE
command.
For example:
SET DATE -lDAY
SET TIME +lHOUR
The first command, when executed, sets the system date back a day.
The second command, when executed, adjust the system time ahead one
14-3

Miscellaneous System Management Functions
hour.
You can use relative values to make minor adjustments in the
system date or time. Relative date and time syntax is as follows:
+nnDAYS
+nnHOURS
+nnMINUTES
You can string the keywords together in any order and you can
abbreviate them to one character.
If you specify an absolute date and
time, it must appear first in the date-time specification. An example
of mixed absolute and relative date and time would be:
SET DATE lO-MAY-8S:4:00PM+3DAYS+2HOURS-4SMINUTES
This would be equivalent to:
SET DATE 13-MAY-8S:S:1SPM

Recording System Activities:

EMT

Logging

An EMT is a PDP-II assembly language instruction through which a
program requests services from the monitor (for example, opening and
closing a file, performing I/O, and logging in or out.) EMT logging is
an optional feature that provides a "window" on the process by which
timesharing jobs request and receive services from the RSTS/E monitor.
Thus, EMT logging lets you gather information about the activity on
your system.
For example, you might want to know the following information about
your system:
o

The number of logins on a particular terminal

How many files are accessed on a certain drive

Which nonresident FIP overlays get the heaviest use

Such information can help you improve system performance, identify
bottlenecks, establish fee setting algorithms, and watch for potential
security problems.
.
This section describes the EMT logging feature, how it works, and how
to include it in your system.
However, because of the wide variety of
RSTS/E systems, you must decide which data is most useful in your
environment, and how to collect and use the data the EMT logger
provides.
EMT logging includes optional code in the monitor, uses XBUF to pass
information, and requires an EMT logging program (which you must
14-4

Miscellaneous System Management Functions
supply), running as a timesharing job.
The use of EMT logging can
affect performance.
This effect depends on which EMTs you decide to
log, for which jobs you log them, and how much processing your logging
program does for eachEMT.
EMT logging provides information on timesharing activity in terms of
what the monitor sees.
The data returned to your logging program is
in terms of FIRQB and XRB contents, regardless of the programming
environment of the job that issues the directives.
See the RSTS/E
System Directives Manual for information on the FIRQB and XRB, as well
as descriptions of the MACRO form of system directives.

programming for the EMT Logger
To use EMT logging, you must:
o

Include optional code in your monitor at system installation
time.

Supply a program to process the data extracted by the monitor
code.
This program retrieves extracted data by send/receive
calls.

During the system installation dialogue, RSTS/E asks you:
EMT
Logging?
Answer YES to create a monitor that can extract EMT
information and pass it to your program.
Your logging program is a normal time-sharing job.
program to do such activities as:
o

Select pertinent data

Maintain a log file

Signal events on one or more terminals

Control your system while it is running

You can design the

RSTS/E never logs EMTs for certain jobs, including the Error Logger
(ERRCPY) and your EMT logging program itself; in addition the monitor
does not allow you to log certain EMTs.

How EMT Logging Works
If EMT logging is available and active, the monitor inspects each EMT
as it is received.
("Available" means installed in the system;
"active" means that your EMT logging program has properly declared
itself as a receiver.) If the newly-received'EMT is one that RSTS/E
14-5

Miscellaneous System Management Functions
logs, the monitor builds a packet of information about the directive
and stores the packet in XBUF. Note that EMT logging does not use
small buffers for message transfer.
The packet contains:
o

Context data, such as date and time, user job number, and
keyboard number

Directive data, such as information from the job's FIRQB
and/or XRB

When the directive is complete, additional information (for example,
the RSTS/E error code) is added to the packet. The packet is then
made available to your program. Your program can inspect the
parameters passed from the user's job to the monitor, determine the
relevance of the directive being logged from the packet, and take the
appropriate action.
Your program retrieves EMT logging packets by issuing message receive
calls. Parameters in the declare receiver call of your program
specify:
o

How many packets constitute a message

How many packets can be outstanding at any time

How much XBUF the EMT logger can use

Each message received by your logging program consists of the packets
(one per selected EMT) plus control information. This control
information includes a count of EMTs tha~ may have been lost because
one or more of the limits you set up at declare time has been
exceeded.
See the RSTS/E Programming Manual for a description of the use of
message send/receive calls as well as specific information about the
send/receive calls used for EMT logging.

Data Returned by EMT Logging
The meaning of the data returned by the logging program you write
depends on the internal functioning of the monitor. For this reason,
both the format and meaning of data returned are subject to change in
future releases of RSTS/E. DIGITAL reserves the right to change
internal mechanisms and, therefore, makes no commitment to continue
providing any specific part of the data described for this "release of
RSTS/E.

14-6

Miscellaneous System Management Functions
EMT Logging and System Security
The information that EMT logging provides may be helpful in checking
and maintaining system security. However, the use of EMT logging as a
system security tool depends on many site-specific factors:
o

The types of events that can be watched for

The degree of security required

The way that EMT logging is set up

The experience and judgment of the system manager who sets up
EMT logging and interprets its data

The general security practices of the site

In summary, although EMT logging does not guarantee improved system
security, it can provide a very useful tracking mec~anism.

Monitoring System Status: SYSTAT
During normal timesharing, there are many occasions when you need to
monitor the status of your system. RSTS/E provides two system
programs for this purpose:
DISPLY

Automatically displays system status information on your
terminal. By default, the program displays the system
status every 15 seconds; however, you can specify a
different interval. See the following section for a
description of the DISPLY program.

SYSTAT

Displays the status of different parts of the system when
you use various program switches. See the RSTS/E utilities
Reference Manual for a complete description of SYSTAT and
the switches associated with it.

The description of SYSTAT in this section gives a set of guidelines
for using the SYSTAT program for more effective system management.
Use SYSTAT to:
o

Prepare for system shut-down to learn what jobs are active
and which disk devices and assignable devices are in use.

Determine when the number of general small buffers becomes
too low. You can then decide whether to use the DCL commands
SET SYSTEM/NOLOGINS and SET SYSTEM/LOGINS to restrict the
number of users that can log in to the system. Note that you
can also use the SHOW BUFFERS command to display the number
of available general small buffers.
14-7

Miscellaneous System Management Functions
o

Check on the amount of free disk space. The disk status
report in SYSTAT reflects the apparent number of free blocks
on each disk on the system. For practical purposes, however,
such as for allocating a file on the device, all free blocks
that SYSTAT reports may not be usable. You may get the
message ?No room for user on device when SYSTAT reports there
are free blocks available. Note that you can also use the
SHOW DISKS command to display the amount of free disk space.
The file cluster size or the number of clusters you need can
prevent a file from fitting on a device. For example, a file
whose cluster size is 16 and whose length is 10 blocks may
not fit on a device that SYSTAT reports to have 50 free
blocks of file space remaining. The cluster size of 16
demands that 16 contiguous blocks of free space exist on the
device before the file can be allocated to the device. In
some cases, 16 contiguous blocks do not exist on a device and
RSTS/E does not allow a file to extend to another physical
device even though SYSTAT can give you some indication of the
availability of free disk space.

Follow the progress of user jobs. You can determine if a job
is stalled, waiting for resources on your system. If you
notice that a run-time value of a job is not increasing (the
value is printed in a job status report), it indicates that
the job is stalled and waiting for an I/O device. One user
job can allocate a device or keep an assignable device locked
by having one file open. You can dete~mine who the user is
by examining the device status report that associates the
busy device with the job number of the user controlling that
device. You can then ask the user to free the device or, if
that is not possible, you can use DCL commands to force the
. job off the system (FORCE) or seize the device
(ALLOCATE/SEIZE). Note that you can also use the SHOW USERS
and SHOW JOBS commands to display user job status.

Follow the progress of detached jobs. When SYSTAT reports a
detached job in the HB (hibernate) state, you know the
detached job is attempting to communicate with its terminal.
In this case, log in to the system at a free terminal, and
then use the ATTACH command to attach the job to the
terminal. Once you attach to the detached job, RSTS/E can
display the messages from the job. Note that you can also
use the SHOW JOBS/DETACHED command to display the status of
detached jobs.

Check on the number of jobs on the system. The free status
report lists the number of jobs currently logged in to the
system and the maximum number of jobs allowed. These numbers
are useful when you are adding and removing swap files.
After adding the swap files and raising the logins allowed,
you can check the free status report to confirm the success
14-8

Miscellaneous System Management Functions
of the procedure. Before removing a swap file, check this
report to make sure that the number of logins allowed is low
enough to enable you to remove the swap file at some later
time. Note that you can also use the SHOW SYSTEM command to
display the number of jobs on the system.

Dynamic Display of System Status: DISPLY
The DISPLY system program displays the system status on VT52, VT100,
and VT200 series terminals. After you start the program and decide
how frequ~ntly you want it to update the system status on the screen,
the program runs until you interrupt its execution.
The information
DISPLY prints is similar to that of the SYSTAT program.
Commands you
type during the execution of the program can alter the information
displayed on the screen.
These commands let you choose only those
portions of the system status you need to see.
The program resides in the AUXLIB$: account with the protection code
of <232>.
This protection code lets all users run the program.
If
you want to restrict running the SYSTAT program to users that have the
same project number as the owner, change the protection code to <120>.

Running the DISPLY Program
The program prints an identification line and a question after you
type the command line RUN AUXLIB$:DISPLY.
They appear as follows:
$ RUN AUXLIB$:DISPLY
DISPLY V9.0 RSTS V9.0 EDERE
Interval?
If you want updates to occur every 15 seconds, press RETURN to accept
the default. Otherwise, type the number of seconds you want to elapse
between 'screen updates.
You can include any combination of the
switches in Table 14-2 in your response.
If you select a program
switch but do not specify an interval, the program again assumes the
default and updates the screen every 15 seconds.
Table 14-2 lists the
DISPLY program switches.

14-9

Miscellaneous System Management Functions
Table 14-2:

DISPLY Program Switches

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
I
Meaning
+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

/[NO]DCA

Indicates if the terminal can use direct cursor
addressing to position the cursor on the screen. By
default, DISPLY uses /DCA.

/DET

Detaches the jo~ from this terminal or from the
terminal you specify.

/ECHO *

Indicates that the terminal should use echo control
features. The program disables echoing while it
updates the screen and spurious characters do not ruin
the screen display. By default, DISPLY does not use
ECHO.

/KBn:

Prints the output at keyboard unit n if it is
available. If you specify the /DET switch, the program
runs detached.

Specifies the number of lines to display. The value of
n can range from 12 to 24. By default, DISPLY displays
24 lines.

/PRIORITY

Runs the program at a special priority instead of at
the normal -8 priority. Requires TUNE privilege.

/[NO]TAB

Indicates if the terminal can correctly process TAB
characters. By default, DISPLY uses /TAB.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I * Echo control is an optional feature of the RSTS/E monitor and
I
may not be available on your system.
I
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
When you include the /DET switch in response to the INTERVAL question
to run the -program detached, you interrupt execution and you can use
the terminal for other work. As soon as you enter CTRL/C to interrupt
the display, the program prints a message telling you the terminal is
available. When you release the terminal by logging out, the program
automatically displays the status information on the screen as if it
had not been interrupted.
Use CTRL/C to stop the execution of the DISPLY program. The procedure
you follow after stopping the program depends on whether you were
running the program attached or detached.
If you are running the
program attached, entering CTRL/C to end the program returns control

14-10

Miscellaneous System Management Functions
to the keyboard monitor. When running the program detached, entering
CTRL/C causes the program to print the following message before
terminating:
The terminal is all yours now
You must then attach the job running .the program to the terminal as
follows:
HELLO 1,2 <RET>
PASSWORD:
Jobs detached under this account:
Job What Size State
Run-time
10 DISPLY 16
SL
5.6
Job number to attach to? <RET>

RTS
... RSX

$ Continue <Yes>? N<RET>
When the program attaches to the terminal as a result of the HELLO
command, it prints the CONTINUE question.
Finally, type NO or any
other string not beginning with Y and press RETURN to terminate the
program.
The program displays on your terminal an identification line at the
top line of the screen, skips a line, and fills the left portion of
the screen with job status information and the right side with
information about:
0

Busy devices

Disks

Run-time systems

Message receivers

Free buffers

Resident libraries

After the screen is full, the program moves the cursor to the first
character on the second line of the screen.
The program is then idle,
waiting to·cycle through the display again.
At the specified interval, the program checks the system tables and
updates the status information on the screen with any changed data.
While executing routines to extract update information, the program
prints the message:
WORKING ...

14-11

Miscellaneous System Management Functions
It leaves the cursor to the right of the message. After the update is
complete, the cursor returns to its idle position.
While the cursor is in the idle position, you can type commands to
modify the contents and arrangement of items on the screen. You can
end any command by pressing the ESCAPE key. Although any line
terminator works, ESCAPE leaves the cursor positioned on the blank
line.
The program prints no message or takes no action on invalid
statements.
Some commands that add items to the screen take the minus (-) sign as
a prefix. A command with a minus sign preceeding it causes DISPLY to
delete rather than add a display of the information that would
normally appear without the minus sign.
That is, the minus sign
negates the effect of the command.
Table 14-3 lists the commands you use (usually while the cursor is in
its idle position) to delete or add system status information.
Table 14-3:

DISPLY Program Commands

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Type
Format and Description
I
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

General

c
Clears the screen and displays new status.
Sn
Displays memory status in place of job
status. Starts with the 8K-word section less
than or equal to n. If n is not given, starts
at the beginning of memory.
J

Displays job status in the standard manner.
In
Displays job status starting with active job
n+l. Overcomes physical limitation of the
screen.
Xn
Changes the interval to n seconds.

xO
updates the display with an interval of 0
seconds (that is, runs continuously) but
lowers the priority so that other jobs are
not stalled.

14-12

Miscellaneous System Management Functions
Table 14-3:

DISPLY Program Commands (Cont.)

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command Type
I
Format and Description
+ - - - - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Job status
I
I
I

I
I T
I Displays total CPU time each job has used.
I The time is displayed as number of hours,

I
I
I
1
minutes, seconds, and tenths of seconds under I
the RUN-TIME column.
I
I
+
I
Displays the increment of CPU time each job
I
has used since the display program last
updated the screen. The user can return to
total CPU time by typing T.
%

Displays the amount of CPU time each job has
used as a percent of the total CPU time
expended. The user can return to total or
increment of CPU time by typing,
respectively, T or +.

J-D
Does not display detached jobs.
J+D
Includes detached jobs in display.
JD
Displays only detached jobs.
J-S

Does not display sleeping jobs.
J+S
Includes sleeping jobs in display.
N

Indicates the program name in the WHAT
column.
-N

Removes the program name from the WHAT column
and replaces it with name of the RTS under
which the job is running.
p

Indicates, under the Pr column, the exact
priority (modulo 8) of the jobs.
14 -.13

Miscellaneous System Management Functions
Table 14-3:

DISPLY Program Commands (Cont.)

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command Type
I
Format and Description
I
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Job Status (Cont.)

-p

Indicates, under the Pr column, the relative
priority of the jobs. See the section "Job
Status Statistics."

I
I
I
I
I
I
I
I
I

w
Indicates, under the STATE column, the last
WAIT state rather than actual state.

-w
Removes the last WAIT state and indicates the
actual state of each job.
K

Displays, under the SIZE column, the amount
of memory occupied by each job.
-K

Displays, under the SIZE column, the amount
of memory remaining for each job.
Disk Structure

D, Dn,

-D

Displays disk structure statistics. If n is
1, places the item first on the screen. A
preceding minus sign removes the disk
structure statistics from the screen.
L,

-L

Displays, under the COMMENTS column, the
logical name of each device. The preceding
minus sign replaces logical names with
standard PUB, PRI, NFS, or LCK notations.
Busy Devices

B, Bn,

-B

Displays busy device statistics. If n is 1,
the program places the statistics first on
the screen. A preceding minus sign removes
busy device statistics from the screen.
Free Buffer

F, Fn,

-F

Displays free buffer statistics. If n is 1,
the program places the statistics first on
the screen. A preceding minus sign removes
free buffer statistics from the screen.

14-14

Miscellaneous System Management Functions
Table 14-3:

DISPLY Program Commands (Cont.)

I
I Message
I
I
I
I
I

M, Mn,

-M

Displays message receiver statistics. If n is
1, the program places the statistics first on
the screen. A preceding minus sign removes
message receiver statistics from screen.

! Run-Time System

R, Rn,

Displays run-time system data. If n is 1, the
program places the data first on the screen.
A preceding minus sign removes run-time data
from the screen.

I
I
I
I Resident Libraries
I
I

H, Hn,

-R

-H

Displays resident library data. If n is 1,
the program places the data first on the
screen. A preceeding minus sign removes the
I
resident library data from the screen.
I
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Screen Layout
The program divides the screen into four major sections:
Header line

Contains the RSTS/E version number, the name
of the system, the current date and time of
day, and the number of hours, minutes, and
seconds since the start of time-sharing
operations (termed "up-time"). The header
line appears on the first line of the
display.

Total statistics line

Tells the percentage of time that is expended
by users (User), input and output processing
(I/O), and the monitor (Exec) as well as the
amount of idle time (Idle) and lost time
(Lost).
The statistics print on the line
below the header line but are replaced at the
interval you specify by the WORKING ...
message.
(The statistics are only printed if
the system was installed with statistics and
the switch register is set correctly.)

14-15

Miscellaneous System Management Functions
Left-hand portion

contains either the job status statistics or,
if you use the S command, the memory usage
status.

Right-hand portion

contains statistics for busy devices, the
disk structure, run-time systems, message
receivers, system buffers, and resident
libraries.

The DISPLY program prints information similar to the information
SYSTAT includes in its status reports. The description of the major
sections of the dynamic status report includes information about how
the DISPLY program reports differ from those of the SYSTAT program.
If you need a more complete description of SYSTAT, see the RSTSIE
utilities Reference Manual.
The following example displays all four divisions. While the example
does not represent an actual log of the DISPLY program, it does give
you a picture of how information is displayed. 'When you run the
program on your system, not all the illustrated information will fit
on your terminal screen. You will often need to use commands
described in Table 14-3 to delete reports so unseen portions of the
display become visible. The example lets you see an entire display,
unhindered by screen limitations (usually 24 rows).

14-16

Miscellaneous System Management Functions

RSTS V9.0
EDERE
status on 15-May-85 05:31 PM Up: 41:55:19
1. 6%Lost
10.0%Id1e,
78.0%User
6.0%Exec,
5.4%1/0
Job Who Where What Size state Run-time Pr
BUSY Deyices
1
1,2
Det
+ Dev Job Why Dev Job Why
ERRCPY 5 SR
8 Open
2
1,2
PKO 11 A+Op PK1
Det
OPSRUN 16 SL
.8
1,2
3
3.4 +
Det
QUMRUN 16 SL
Disk Structure
1,2
4
Det
SPLIDL 16 SL
0 pri,R-O
1524 4
DKO 0
5. 1,2
Det
BATIDL 13 SL D25
0 Pri,DLW
1,2
DRO 0 19772 4
6
Det
BATIDL 13 SL D26
2 Pub,DLW
1720 4
1,2
DR1 43
7
Det
EVTLOG 22 SL
0 pri,R-O
1,2
DR2 0 12496 4
8
Det
NPKDVR 9 SL
3 Pri,DLW
1,2
DR3 9
9720 8
9
Det
SYSMAN 8 SL
3204 4
1 pri,DLW
DR4 1
11
1,210 KB32 ATPK
8 SL
12
1,210 POJ11 DISPLY 16 RN Lck
13
1,223 KB51 SYSTAT 12 "c
1.8
Run-time Systems
15
1,104 KB31
.•• EDT 7 KB
9 Prm,KBM,CSZ
DCL
16
1,226 KB17 NONAME 2 ,.c
15K
1 Tmp,KBM,CZR
RT11
4K
20
1,253 KB42 VTEDIT 14 KB
o Tmp
21
7,214 KB21 VTEDIT 24 RN
RSX
8K
o Non-res,KBM
BAS4AL 16K
22
1,248 KB29 PIP
16 KB
o Tmp,KBM,CSZ
23
226,0 P1J8 NONAME 2 ,.c A09
BASIC
15K
24
1,250 KB33 ONLPAT 15 KB
26
1,243 KB43 NONAME 2 ,.c
27
1,247 KB30 NET
Message Receivers
16 SL
0/40
1 0
28
8,254 KB72
ERRLOG(prv)
•.. EDT 7 HB
2 0
0/30
OPSER (Loc)
0/60
3 0
QUEMAN(Loc)
4 0
0/5
LPOSPL(Prv)
BA1SPL(prv)
5 0
0/5
0/16
EVTLSN(prv,Nt) 7 0
7 1
0/32
EVTLOG(prv)
8 0
0/16
NWPK08(Nt)
12 0
0/5
NWTT12(Nt)
Gen FIP Jobs
315 62 14/50

TTY
0

Err
3

Resident Libraries
BASICS
8K
0 Non-res,Rem
EDT
21K
2 Tmp,Rem
1 Non-res,Rem
RMSRES
4K
4K
RMSLBA
0 Non-res,Rem
4K
1 Non-res,Rem
RMSLBB
3K
0 Non-res,Rem
RMSLBC
RMSLBD
2K
0 Non-res,Rem
RMSLBE
4K
0 Non-res,Rem
4K
RMSLBF
0 Non-res,Rem
DAPRES 10K
0 Non-res,Rem

Job status Statistics
The job status report displays information in eight separate columns
on the left-hand portion of your terminal. The report is similar to
the information the SYSTAT program prints in its display of job
status. Unlike the SYSTAT program, the job status report does not
include the name of the run-time system under which the job is running
14-17

Miscellaneous System Management Functions
but does include abbreviations indicating the priority of the running
job. The titles that the DISPLY program prints at the top of a job
status report have the following meanings:
Job

Job number that the system assigns when the job starts
timesharing activities.

Who

Account number under which each job runs.
If the job
is not logged in to the system, **,** appears in this
column.

Where

Keyboard number of the job. DET appears in place of
the keyboard number for jobs that run detached from
the keyboard.
The abbreviation PxJy can appear fora
job running on a pseudo keyboard.
The .va1ue Px
identifies pseudo keyboard unit Xi and the value Jy
denotes job number y, under which the controlling job
is running.

What

Program name that the job is executing.

Size

Current size in K words of the job.

State

Current state of the job indicated by the set of
abbreviations in Table 14-4.

Run-time

Hours, minutes, seconds, and tenths of seconds of
central processor (CPU) time the job has consumed.

The job status report includes a PR column, which is not displayed by
SYSTAT, that identifies the priority of the running job. The PR
column can display the following abbreviations:
If .p is in effect:

Higher than normal priority
Lower than normal priority

Special run priority
CTRL/C temporary priority

Keyboard delimiter temporary priority

If P is in effect:

positive priority n * 8

Zero priority

-n

Negative priority n

* 8

14-18

Miscellaneous System Management Functions
Table 14-4 contains a brief description of the abbreviations that can
appear in the STATE column of the job status report. The following
status descriptions can appear after one or more of the job state
abbreviations in Table 14-4:
Lck

Job is locked in memory for the current operation.

Nsw

Job has requested that it not be swapped from memory
and cannot be swapped unless it requests additional
memory.

Swi

Job is currently being swapped into memory.

Swo

Job is currently being swapped out of memory.

Xnn

Job is swapped out and occupies slot nn in swap file Xi
file is denoted A, B, C, D to represent files 0 through
3 of the swap structure.

Table 14-4:

STATE Column Attributes

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - _. - - - - - - - - - - - - - - - - - - - - - - - - --+
I Abbreviation I
Meaning
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - _. - - - - - - - - _. - - - - - - - - - - - _. - --+

I
I ??
I
I BF
I
I
I '" C
I
I
I CR
I
I DK,DM,DB,DP,
I DL,DR,DU
I
I DT
I
I DX
I
I FP
I
I
I HB
I
I
I KB
I
I LP

Job's state cannot be determined.
Job is waiting for buffers (no space is available
for I/O buffers).
Job is in CTRL/C state, awaiting keyboard monitor
input.
Job is waiting for card reader input.
Job is waiting to perform disk I/O.
Job is waiting for DECtape I/O.
Job is waiting for floppy diskette I/O.
Job is waiting for file processing action by the
system (opening or closing a file, file search).
Job is detached and waiting to perform I/O to or
from a terminal.
Job is waiting for input from a terminal.
Job is waiting to perform line printer output.
14-19

Miscellaneous System Management Functions
Table 14·4:

STATE Column Attributes (Cont.)

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Abbreviation I
Meaning
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

MT,MM, or MS

Job is waiting for magnetic tape I/O.

Job is waiting to perform output on the high-speed
paper tape punch.

Job is waiting for input from the high-speed paper
tape reader.

Job is waiting for RJ2780 I/O.

Job is running or waiting to run.

Job is waiting for residency.

Job is sleeping.

Job is sleeping and is a message receiver.

Job is waiting to perform output to a terminal.

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

BUSY Devices

The busy device report lists the devices that are assigned or opened
by a specific user. Items reported are the device specification, the
job owning that device, and the condition of the device. The disk
status information reports assigned disk units. The busy device
report prints on the right-hand side of the screen and looks as
follows:
Dev Job
PKO 11

Busy Devices
Why Dev Job
Open Pkl
8

Why
Open

The DISPLY program reports the same information as SYSTAT reports in
its busy device report, except that DISPLY prints two side-by-side
reports to accommodate the limited screen space. Table 14-5 contains
the abbreviations that can appear in the WHY column of the busy device
report.

14-20

Miscellaneous System Management Functions
Table 14-5:

Busy Devices Status Abbreviations: WHY Column

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Abbreviation I
Meaning
I
+ - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. - - - - - - - - - - +

I
I AS
I
I INIT
I
I DOS
I
I ANSI
I

I
I Device is explicitly assigned to a job.
I
I Device is open on a channel.
I
I Magnetic tape is assigned with DOS labeling format.
I
I Magnetic tape is assigned with ANSI standard
I labeling format.

I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Disks
The disks report describes each disk in use on the system. The report
contains the same information that SYSTAT/D displays.
The DISPLY
program prints the following information; however, because of screen
limitations, it does not print column headings or as much detail as
SYSTAT does:
o

Disk device specification

Number of open files

Number of free 512-byte blocks

Pack cluster size

Disk hardware error count

Comments on the status of the disk

Pack identification name or system logical names (if any)
assigned for the devices in use on the system

The disks report appears on the right-hand side of your terminal and
looks as follows:
Disk Structure
DRO 0 17252 4
0 pri,DLW
DR1 42
3044 4
2 Pub,DLW
DR2 0 12496 4
0 Pri,R-O
DR3 5 32144 8
3 Pri,DLW
DR4 1
3272 4
I Pri,DLW
DR5 0 532032 16
6 Pri,R-O

14-21

Miscellaneous System Management Functions
To display the pack identification names or system logical names, you
must use the L command described in Table 14-3. This command displays
the disk label information in place of the comments that the program
normally displays. For example:
Disk Structure
DRO 0 17252 4
0 ROGER
2 SYS
DR1 42
3044 4
DR2 0 12496 4
0 ZEBRA
DR3 5 32144 8
3 ABLE
1 MIKE
DR4 1
3272 4
6 YOKE
DR5 o 532032 16
If you want to display the comments again, use the -L command. The
limited size of the screen requires the use of the Land -L commands.
Table 14-6 lists the abbreviations in the COMMENT column of the disks
report.
Table 14·6:

Disk Status Abbreviations: COMMENT Column

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I Abbreviation I

Meaning

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Pub

Cartridge or pack is public.

Pri

Cartridge or pack is private.

NFS

Disk is open as a non-file-structured device.

R-O

Disk unit is read-only (write-locked)

DLW

Date of last write (modify), rather than date of
last access, is stored in file accounting entries.

Lck

Disk is in a locked state.

NFF

New files on this disk are put at the beginning of
the directory.

I
I

+ - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

14-22

Miscellaneous System Management Functions
Message Receivers
The message receivers report:
o

Provides the job name of the receiving job

Provides the job number of the receiving job

Includes the number of messages queued for the job

Gives the declared maximum number of messages the job can
queue

Tells whether local and network senders are allowed

Indicates whether local senders must be privileged

The message receivers report appears on the right-hand portion of the
screen and often does not appear until you delete the disk and
run-time system reports with the -D and -R commands, respectively. A
sample of the message receivers report is:
Message receivers
ERRLOG(prv)
I
OPSER (Loc)
2
QUEMAN(Loc)
3
LPOSPL(Prv}
4
BAOSPL(Prv}
5
BA1SPL(Prv}
6
EVTLSN(Prv,Nt} 7
EVTLOG(Prv}
7

0
0
0
0
0
0
0
1

0/40
0/30
0/60
0/5
0/5
0/5
0/16
0/32

Due to limited space on the screen, some of the abbreviations are
shorter than those printed by the /M switch of SYSTAT. The receiver
report does not include the:
o

Receiver Identification Block (RIB)

Object type

Number of links used and the maximum links allowed.

Table 14-7 describes the abbreviations found in the message receiver
status report.

14-23

Miscellaneous System Management Functions
Table 14-7:

Message Receivers Abbreviations

+- - - - - - - - - - - - - -+- - - -:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I Abbreviation I
Meaning
I
+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Loc

Local senders are allowed for this receiver ID.

Prv

Local senders must have SEND privilege to send to
this receiver ID.

Network senders are allowed for this receiver ID.

Receiver can handle one and only one link.

Both of the above. Network senders are allowed for
this receiver ID. Receiver can handle one and only
one link.

+ - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - '- - - - +

Free Buffers
The free buffers report provides the following information:
o

Number of general small (16-word) buffers not currently in
use

Number of FIP buffers not currently in use

Number of jobs currently running

Maximum number of jobs allowed to run

Number of hung terminal errors

Total number of errors logged on the system

The report prints the same information the /F switch of the SYSTAT
program produces. An example of a free buffers report is:
Gen FIP Jobs
183
1 14/50

TTY

Err
9

14-24

Miscellaneous System Management Functions
Run-Time Systems
DISPLY shows the run-time systems report on the right-hand portion of
the screen.
The report includes the same information as SYSTAT/R
displays, except for:
o

The maximum size in K words that a job running under the
run-time system can take

Some information in the comments column because of limited
screen space

The run-time systems report prints:
o

Name of each run-time system

Size of the run-time system in K words

Number of user jobs currently executing under the control of
the run-time system

Comments regarding the status of the run-time system

A sample run-time systems report is:
Run-time systems:
Name
Ext
Dev
•.. RSX Tsk
RSX
Tsk
DRl:
DCL
Com
DRl:
TECO
Tec
DR1:
RTll
Sav
DRl:
BAS4AL Bac
DR1:
BAS4F
Bac
DR1:
BASIC
Bac
DR1:
FORTH
4th
DR1:

Size
O(32)K
l(28)K
27(4)K
lO(20)K
4(28)K
l7(l2)K
l5(l6)K
13(16)K
6(24)K

Users Comments
Monitor
22
o Primary, Perm, Addr:71, KBM
Temp, Addr:385, DF KBM
7
o Temp, Addr:298, KBM
o Temp, Addr:104, KBM, CSZ, EMT:255
o Temp, Addr:416, KBM, CSZ
o Temp, Addr:ll4, KBM, CSZ
o Temp, Addr:200, KBM, CSZ
o Temp, Addr:108, KBM, NER, CSZ

Table 14-8 contains a list and description of each abbreviation that
DISPLY prints in the COMMENTS column.

14-25

Miscellaneous System Management Functions
Table 14-8:

Run-Time Systems and Resident Libraries Report
Abbreviations

+ - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I Abbreviation I

Meaning

+ - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I
I
I
Run-time system or library is being loaded into
I
memory.
I
I
Run-time system or library is removed from memory
I
when not being used.
I
I
Run-time system or library stays in memory when not I
being used.
I
I
Run-time system or library is nonresident.

Non-res
Loading
Temp
Perm
Addr: xxx

The value of xxx denotes the starting address of
the run-time system or library.

[DF] KBM

Run-time system or library can serve as a keyboard
monitor. The optional prefix DF indicates default
keyboard monitor.

IUS

Run-time system or library can serve only one user.

R/W

Run-time system or library allows read/write
access.

NER

Errors occurring within the run-time system or
library are not sent to the system error log.

Rem

Run-time system or library is removed from memory
as soon as all of its jobs switch to another
run-time system or library.

CSZ

Proper job image size (in K words) to run a program
can be computed as K-size=(file size+3)/4.

EMT:yyy

Denotes the EMT code for special EMT prefix_

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Resident Libraries
The resident libraries report includes:
o

Name of the resident library

14-26

Miscellaneous System Management Functions
o

Protection code of the resident library

Size of the resident library

Number of user jobs currently executing under its control

Comments regarding the status of the resident library

DISPLY shows the resident libraries report on the right-hand portion
of the screen.
The report shows the same information as SYSTAT/L
displays.
Some information in the COMMENTS column may be omitted due
to limited space on the screen.
See Table 14-8 for a description of
the abbreviations used in the COMMENTS column.

Memory Status
The S command causes the program to print a table that shows the use
of each lK-word portion of memory.
The memory status report replaces
the job status report on the lefthand half of the screen. Use the J
command to display the job information again.
Type the S command to have DISPLY print the memory status report as in
this example:
Memory usage (starting at OK)
o MON MON MON MON MON MON
8 MON MON MON MON MON MON
16 MON MON MON MON MON MON
24 MON MON MON MON MON MON
32 MON MON MON MON MON MON
40 MON MON MON MON MON MON
48 MON MON MON MON MON MON
56 *1* *1* *1* *1* *1* *1*
64 *1* *1* *1* *1* *1* *1*
72 XBF XBF XBF XBF XBF XBF
80 XBF XBF XBF XBF XBF XBF
88 XBF XBF XBF XBF XBF XBF
96 XBF XBF XBF XBF XBF XBF
104 XBF XBF XBF XBF XBF XBF
112 XBF XBF XBF XBF XBF XBF
120 XBF XBF XBF XBF XBF XBF
128 XBF XBF XBF XBF XBF XBF
136 XBF XBF XBF XBF XBF XBF
144 XBF XBF XBF XBF XBF XBF
152 7
7
7
7
7
7
160 7
7
7
7
7
7

MON
MON
MON
MON
MON
MON
MON
*1*
*1*
XBF
XBF
XBF
XBF
XBF
XBF
XBF
XBF
XBF
7
7
7

Due to limited screen space, the program may not be able to display
all memory status information simultaneously.
The Sn command lets the
user determine the starting 8K section.
The display program prints
14-27

Miscellaneous System Management Functions
the starting section number for the row and eight abbreviations per
row.
Each of the abbreviations relates to the status of a lK section
of memory.
The number of rows the program prints and the extent of
memory covered is limited by the terminal . . The program indicates the'
starting 1K section by printing a header line in the following format:
MEMORY USAGE (STARTING AT nK)
Table 14-9 contains a description of the abbreviations the memory
status report uses.
Table 14-9:

Memory Status Report Abbreviations

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Abbreviation I
Meaning
I
+ - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. - - - - - - - - - - - - - - - - - - - - - - - +
MON

Occupied by the RSTS/E monitor.

*n*

Occupied by run-time system n, where n is the
position in the run-time system list. (A question
mark is printed if the run-time system name cannot
be determined.)

-n-

Occupied by resident library n, where n is the
position in the resident library list.

Occupied by job number n.

nLK

Job number is locked in this lK portion.

Job number n is being swapped out of memory.

nSI

Job number n is being swapped into memory.

NXM

Memory space is nonexistent.

END

End of physical memory for user jobs.

LCK

Memory is locked.

XBF

Memory is reserved for the extended buffer pool
(XBUF) •

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

DCL Command Descriptions
The following sections describe the DeL commands for the miscellaneous
system functions.
14-28

LOAD/OVERLAY
LOAD/OVERLAY Command
The LOAD/OVERLAY command lets you load monitor overlays in memory
during timesharing.
By making certain monitor functions resident in
memory, you can improve the system's performance at the cost of
increased memory (XBUF) usage.
LOAD/OVERLAY requires SWCFG privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
LOAD/OVERLAY overlay-name[, ... ]
Command Qualifiers

Defaults

/ALL
Prompts

I
I
I
I
I
I
I
I
I
I
I
I

Overlay: overlay-name[, ... ]
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
overlay-name

Specifies the monitor overlay that you want to load into memory.
The allowable values are:
o

ATTRIBUTE -- Indicates the monitor overlay that performs file
and account attribute read/write operations.

DCL -- Indicates the monitor overlay that performs
file-related operations for DCL.

DELETE RENAME -- Indicates the monitor overlay that performs
file deletion and renaming.

DIRECTORY -- Indicates the monitor overlay that performs disk
file lookup operations.

14-29

LOAD/OVERLAY
o

SYSTEM_CALLS -- Indicates the monitor overlay that performs
all of the following monitor directives:
Get monitor tables (parts 1, 2, and 3)
Return open file information
Date and time conversion
Return job status

TERMINAL -. Indicates the monitor overlay code that performs
terminal attribute read/write operations.

Command Qualifiers
/ALL
Indicates that all possible overlays should be loaded into
memory.
If you specify this qualifier, RSTS/E does not allow any
overlay names.

14-30

SET DATE
SET DATE Command
The SET DATE command sets the RSTS/E system date to the value you
specify. Optionally, you can specify a new value for the system time.
You can specify relative values for the date or time.
SET DATE
requires the DATES privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SET DATE date[:time]
I
I Prompts
I
I None

I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Paramters
date
Specifies the system date.
Insert a space between the date field
and the DeL command.
You can specify a relative date with the
keyword DAYS.
[ : time]
Specifies the system time. You can specify a relative time with
the keywords; HOURS and MINUTES.
Insert a colon (:) between the
date and time fields.
Note
When you specify the AM/PM suffix, there is no
space between the minutes and the suffix. For
example:
SET TIME 1:30PM

14-31

SET SYSTEM
SET SYSTEM Command
The SET SYSTEM command sets the default system characteristics. You
need one or more privileges to use this command (see the discussion
for each command qualifier).

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format

I
I

SET SYSTEM
Command Qualifiers

Defaults

/DATE_FORMAT=format
/DENSITY=default
/HANGUP={DELAYEDIIMMEDIATE}
/HOLD
/LABEL=default
/NAME="installation name"
/[NO]PASSWORD_PROMPT[=(type[, ... ])]
/POWERFAIL_DELAY=n
/RELEASE
/TIME_FORMAT=format

See Discussion
See Discussion
/HANGUP=DELAYED
See Discussion
See Discussion
See Discussion

I
I
I

I
I

I
I
I
I
I

Prompts

None
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Qualifiers
/DATE_FORMAT=format
Sets the default date format:
o

ALPHABETIC -- Sets the default date format to alphabetic
(DD-MMM-YY)

NUMERIC -- Sets the default date format to numeric (YY.MM.DD)

You need SWCFG privilege to specify this qualifier.
/DENSITY=default
Sets the default magnetic tape density:
o

800 -- Sets the default magnetic tape density to 800 bpi

1600 -- Sets the default magnetic tape density to 1600 bpi

You need HWCFG privilege to specify this qualifier.

14-32

SET SYSTEM

/HANGUP={DELAYEDIIMMEDIATE}
Sets whether or not the system delays hanging up dial-up lines
,when carrier is dropped.
The default is DELAYED, which means the
system waits approximately five seconds before hanging up a
dial-up line.
Setting IMMEDIATE means the system hangs up a dial-up line as
soon as the carrier is dropped.
IMMEDIATE is mainly used for
European dial-up lines.
You need SWCFG privilege to use this
qualifier.
/HOLD
stops execution of all jobs except the one issuing the command.
You need HWCTL privilege to use this qualifier.
/LABEL=default
Sets the default magnetic tape label:
o

ANSI -- Sets the default magnetic tape label to ANSI

DOS -- Sets the default magnetic tape label to DOS

You need SWCFG privilege to use this qualifier.
/NAME="installation name"
Sets the system name to the name you specify. You can specify up
to 15 characters in the name. You need SWCFG privilege to use
this qualifier.
/[NO]PASSWORD_PROMPT[=(type[, ... ])]
Specifies the types of users that must enter the system password.
If you do not specify any types, all users must enter the
password.
If you want to limit prompting to remote users, use
the types NETWORK and DIALUP.
You need WACNT privilege to use
this qualifier.
/POWERFAIL_DELAY=n
Sets the power fail delay to n. When a power failure occurs, the
system waits n seconds before rebooting the system.
The value of
n can range from 1 to 300.
You need SWCFG privilege to use this
qualifier.
/RELEASE
Resumes execution of all jobs on the system.
privilege to use this qualifier.

14-33

You need HWCTL

SET SYSTEM

/TIME_FORMAT=format
Sets the default time format:
o

AM PM -- Sets the default time· format to AM/PM time (01:30PM)

24 HOUR -- Sets the default time format to 24-hour time
(13:30)

You need SWCFG privilege to use this qualifier.

14-34

SET TIME
SET TIME Command
The SET TIME command sets the RSTS/E 24-hour clock to the value you
specify. Optionally, you can set the system date to the value you
specify. You can specify relative values for the date or time. SET
TIME requires the DATES privilege.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I SET TIME [date:]time
I
I Prompts
I
I None

I
I
I
I
I
I
I
I

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
[da te: ]
Specifies the system date.
If you specify this optional field,
insert a space between the DeL command and the date field and
insert a colon between the date and time fields.
You can specify
a relative date with the keyword DAYS.
time
Specifies the system time. You can specify a relative time with
the keywords; HOURS and MINUTES.
Note
When you specify the AM/PM suffix, there is no
space between the minutes and the suffix.
For
example:
SET TIME 1:30PM

14-35

SHOW SYSTEM
SHOW SYSTEM Command
The SHOW SYSTEM command displays the system default characteristics as
follows:
System name:
Date format:
Time format:
Magtape label default:
Magtape density default:
Power fail restart delay:
Hangup:

RSTS V9.0 EDERE
Alphabetic
AM PM
ANSI
1600 BPI
300 seconds
Delayed

Job limit:
Current jobs:

Password Prompting:

Network and Dialup users

The SHOW SYSTEM command does not require any privileges.

+ - - - - - - - - - - - - - - - - - - - - - - - - ;. - - - - - - - - - - - .;. - - - - - - - - - - - - - - - - - - - --+
Format
SHOW SYSTEM
Command Qualifiers

Defaults

None
Prompts
None
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The SHOW SYSTEM command has no qualifiers or prompts.

14-36

UNLOAD/OVERLAY
UNLOAD/OVERLAY Command
The UNLOAD/OVERLAY command lets you unload monitor overlays that were
loaded into memory with the LOAD/OVERLAY command. UNLOAD/OVERLAY
requires SWCFG privilege.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
UNLOAD/OVERLAY overlay-name[, ... ]
Command Qualifiers

Defaults

/ALL
prompts

I
I
I
I
I
I
I
I
I
I

Overlay: overlay-name[, ... ]
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
overlay-name

Specifies the monitor overlay that you want to unload from
memory.
The allowable values are:
o

ATTRIBUTE -- Indicates the monitor overlay that performs file
and account attribute read/write operations.

DCL -- Indicates the monitor overlay that performs
file-related operations for DCL.

DELETE RENAME -- Indicates the monitor overlay that performs
file deletion and renaming.

DIRECTORY -- Indicates the monitor overlay that performs disk
file lookup operations.

14-37

UNLOAD/OVERLAY
o

TERMINAL -- Indicates the monitor overlay code that performs
terminal attribute read/write operations.

Command Qualifiers
/ALL
Indicates that all possible overlays should be unloaded from
memory. If you specify this qualifier, RSTS/E does not allow any
overlay names.

14-38

Chapter 15
lolanaging Disks and Tapes

This chapter describes the DCL commands that you use to manage RSTS/E
disks and tapes.
First, Table 15-1 lists and briefly describes the
DCL commands available to you. Then, the chapter provides background
information about disk and tape handling on RSTS/E.
Finally, the
chapter lists each command alphabetically and explains it in more
detail.
Some functions of INITIALIZE, MOUNT, and DISMOUNT require privilege.
This manual describes all the functions.
The RSTS/E System User's
Guide also describes those functions that do not require any
privileges.
Table 15-1:

DCL Commands for Disk and Tape Handling

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command
I
Meaning
I
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I INITIALIZE
I
I
I MOUNT
I
I
I
I DISMOUNT
I
I

I
I Initializes a disk or magnetic tape. Use this command
I to prepare the medium for writing new files.
I
I Logically mounts a disk or magnetic tape. Use this
I command after you physically mount the disk or tape
I on the device.
I
I Logically dismounts a disk or magnetic tape. Use this
I command before you physically dismount the disk or
I tape from the device.

I
I
I
I
I
I
I
I
I
I
I

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Working with Disks and Tapes
The system manager or operator is often responsible for mounting and
dismounting disk packs and magnetic tapes.
Indeed only a user with
15-1

Managing Disks and Tapes
MOUNT privilege can load disks on the public structure. Thus, you
need to be familiar with commands that prepare tapes and disks for
use: INITIALIZE, MOUNT, and DISMOUNT.

Initializing Disks and Tapes
Initializing a disk or tape makes it "like new." You should consider
initializing if you have:
o

An old disk or tape to recycle; you initialize it to
eliminate any existing files that it contains.

A new disk or tape; you initialize it to perform all the
necessary actions that make it usable on your system.
(The
INITIALIZE command descriptions explain these necessary
actions.)

Certain disks require formatting before they are initialized.
Formatting writes timing and sense marks onto the disk and destroys
any information that the disk contains. You format disks using the
DSKINT option of INIT.SYS; for a description see the RSTS/E

Installation and update Guide.
You must shut the system down to format the following disks before
using them on a RSTS/E system: RK05, RK05F, RP02, and RP03.
Note
These disks need to be formatted only once. All
other disks have been formatted at the factory and
need not be formatted again.
The DSKINT option also creates a RSTS/E file structure on the disk.
You can later use the DCL INITIALIZE command to clear the disk of
files and recreate the RSTS/E file structure.
The INITIALIZE command:
o

Has different qualifiers for disk initialization from those
for tape initialization.

Requires WRTNFS privilege when used for disks.

The section "INITIALIZE Command for Tapes" describes tape
initialization.
See the RSTS/E System User's Guide for nonprivileged
uses of the INITIALIZE command.

15-2

Managing Disks and Tapes
Mounting and Dismounting Tapes and Disks
Whenever you want to use.a different tape or disk from that which is
mounted, you must logically dismount the current disk or tape (using
the DISMOUNT command), and physically remove the disk or tape from the
drive.
Then you physically mount the new disk or tape on the drive
and place the drive on line.
After physically mounting and activating the medium, you must
logically mount the new disk or tape (using the MOUNT command). This
allocates the drive for appropriate use.
For example, a tape drive is
allocated for use only through your account. A disk drive with a pack
initialized and mounted as public becomes part of the public
structure.
It can be used by anybody on the system.
The MOUNT command prepares an initialized disk or tape for processing
by system commands or user programs. The DISMOUNT command releases a
disk or tape that was previously accessed with a MOUNT command. Both
MOUNT and DISMOUNT have different qualifiers when used with disks or
tapes.

DeL Command Descriptions
The following sections describe the DeL commands for managing RSTS/E
disks and tapes.

15-3

DISMOUNT (Disks)
DISMOUNT Command for Disks
The DISMOUNT command for disks releases a disk previously accessed
with a MOUNT command. You issue this command before you take the
drive off line or before you physically dismount the disk. You can
dismount any disk with MOUNT privilege. Without MOUNT privilege, you
can only dismount a disk mounted /NOSHARE for your job.
The DISMOUNT command deallocates the disk if it was allocated to you.
You cannot DISMOUNT a device if there are open files on it. If you
try, the system displays the error message:
?Account or device in use
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format
I
I DISMOUNT disk-device-name[:] [pack-id]
I
I Command Qualifiers
Defaults
I
None
I /PUBLIC
I
I Prompts
I
I Device: device-name[:]
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Parameters
disk-device-name[:]
The physical or logical name of the disk unit containing the pack
to be dismounted.
If you do not specify a unit number, the
following error message appears:
?Unit number needed
pack-id
The pack-id specified when the disk was initialized and mounted.
The pack-id is deassigned as a system-wide logical. The pack-id
is optional.

15-4

DISMOUNT (Disks)
Command Qualifiers
/PUBLIC
You need MOUNT privilege to dismount a public disk.
must have been mounted and initialized as public.)

(The disk

If you do not specify /PUBLIC, the system assumes that the disk
was mounted as private.
If you try to dismount a public disk
without the /PUBLIC qualifier, you get the error message:
?Disk is mounted public
If you try to dismount a disk by using the /PUBLIC qualifier and
the disk was mounted as private, you get the error message:
?Disk is mounted private
If you do not have MOUNT privilege you can only dismount private
disks if they were mounted /NOSHARE.
If you try to dismount a
public disk, you get the error message:
?You have MOUNT privilege to dismount a public disk
If the disk was mounted with the /NOSHARE qualifier, and any
unprivileged job except the one to which the disk is assigned
attempts to dismount it, the following error message appears:
?Account or device in use

15-5

DISMOUNT(Tapes)
DISMOUNT Command for Tapes
The DISMOUNT command for tapes releases a tape previously accessed
with a MOUNT command. You issue this command before you take the
drive off line or before you physically dismount the tape. The
DISMOUNT command deal locates the tape drive if it was allocated to
you.
You cannot DISMOUNT a tape if there are open files on it. Any
attempt to do so returns the error message:
?Account or device in use
When used for tapes, the DISMOUNT command does not require any
privileges.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
DISMOUNT tape-device-name[:] [label]
Command Qualifiers

Defaults

/[NO]UNLOAD

/UNLOAD

Prompts
Device: device-name[:]
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Command Parameters
tape-device-name[:]
Specifies the physical or logical name of the drive on which the
tape is to be dismounted.
If you do not specify a unit number
with a physical device name, the default is unit O.
label
Specifies the label on an ANSI tape. Note that it is not
necessary to specify a label with the DISMOUNT command. However,
if you are using a hard-copy terminal, you can specify a label to
keep a 10g of the tape being dismounted. The label you specify
is ignored; it is not checked against the label on the tape.
Command Qualifiers
/[NO]UNLOAD
Specifies whether to unload the tape from the drive. Once a tape
is unloaded, it must be manually loaded before it can be mounted
again. The default is /UNLOAD.
15-6

INITIALIZE (Disks)
INITIALIZE Command for Disks
The
is,
(Be
the

INITIALIZE command creates a RSTS/E file structure on a disk; that
it prepares a disk so files can be written to it and read from it.
aware that INITIALIZE overwrites any data previously written to
disk unless you specify the /NOEXERCISE/NOERASE qualifier.)

In creating a RSTS/E file structure for the disk, INITIALIZE writes
several structures to the disk.
For example, INITIALIZE creates a
User File Directory (UFD) for account [0,1] that contains entries for
the files SATT.SYS (the storage allocation table) and BADB.SYS (the
bad block file).
Note
When you issue the INITIALIZE command, the disk
should only be physically mounted in the drive; it
should not be logically mounted.
When used for disks, the INITIALIZE command requires WRTNFS, RDNFS,
and WREAD privileges.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
INITIALIZE disk-device-name[:] pack-id
Command Qualifiers

Defaults

/CLUSTER_SIZE=n
/DATE=ACCESSED
/DATE=MODIFIED
/[NO]ERASE
/[NO]EXERCISE=n
/INDEX=position
/MFD_CLUSTER_SIZE=n
/PRIVATE
/PUBLIC
/[NO]QUERY
/[NO]RETAIN
/[NO]WRITE

n=device cluster size
/DATE=MODIFIED
/DATE=MODIFIED
/ERASE
/EXERCISE=FULL
/INDEX=MIDDLE
n=16
/PRIVATE
/PRIVATE
/QUERY
/RETAIN
/WRITE

Prompts
None
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

15-7

INITIALIZE (Disks)
Command Parameters
disk-device-name[:]
Specifies the name of the drive on which the disk is physically
mounted.
pack-id
One- to six-alphanumeric characters to be used when logically
mounting the disk. By default, RSTS/E uses this pack-id as a
system-wide logical name for the mounted disk.
Command Qualifiers
/CLUSTER_SIZE=n
Declares the pack cluster size, which is the m~n~mum allocation
unit, in 512-byte blocks, for the disk. All files written to
this· disk use multiples of n blocks, where n is the pack cluster
size.
In general, the cluster size specified (n) must be a power of 2
(1, 2, 4, 8, 16), equal to or greater than the device cluster
size, but not greater than 16. If you do not specify a cluster
size, RSTS/E assumes the device cluster size.
The /CLUSTER_SIZE=n option affects performance.
In general, a
large pack cluster size speeds disk I/O operations, but wastes
disk space.
For example, if you declare /CLUSTER_SIZE=16 for a
disk, a file consisting of 8193 bytes (16 512-byte blocks plus
one byte) requires 2 pack clusters, or 32 blocks. A
/CLUSTER_SIZE=8 for the same file would require three clusters,
or 24 blocks, of disk storage.
Table 15-2 lists the device cluster sizes for the disks that
RSTS/E supports.
Table 15-2:

Disk Size and Cluster Size

+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+
Device
Acceptable Pack
Total
Disk
Cluster
Cluster Size
Device Size
Type
Size
(/CLUSTER.SIZE)
(Blocks)
+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+
I

Rx50
I RKO 5 I
RK05F
I

RL01

1
1
1
1

1, 2, 4, 8, 16
1, 2, 4, 8, 16
1, 2, 4, 8, 16

I, 2, 4, 8, 16
15-8

800
4800
4800 for each unit;
2 units per drive
10220

I
I
I
I

INITIALIZE (Disks)
Table 15-2:

Disk Size and Cluster Size (Cont.)

+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+
I
I Device I Acceptable Pack I
Total
I
I
Device Size
I
I Disk I Cluster I Cluster Size
I (/CLUSTER_SIZE) I
(Blocks)
I
I Type I Size
+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+
1, 2, 4 , 8, 16
1
I RL02
I 20460
1
1, 2, 4, 8, 16
I RD51
I 21600
2,
4
,
RD52
1
1,
8,
16
I 60479
I
4
,
1,
2,
8,
RC25
1
16
I
I 50902 for each unit;
2 units per drive
I
4
,
1,
2,
8,
16
27104
RK06
1
I
1,
2,
4,
8
,
53768
RK07
1
16
I
2,
40000
2
4,
8,
16
I RP02
2, 4, 8, 16
80000
2
I RP03
4, 8, 16
131648
4
I RM02
131648
4, 8, 16
4
I RM03
4, 8, 16
171796
4
I RP04
4,
8,
RP05
4
16
171796
I
8,
RA80
4
4,
237208
16
I
4,
8,
242575
RM80
4
16
I
8,
340664
8
16
RP06
I
8
8,
400175
16
I RA60
500352
8
8, 16
I RM05
888012
16
16
I RA81
+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+

/DATE=ACCESSED
/DATE=MODIFIED
Lets you specify whether to record a file's date of last access
(=ACCESSED) or of last modification (=MODIFIED).
The default is
/DATE=MODIFIED.
/[NO]ERASE
Indicates whether the data on the specified disk is erased.
/NOERASE qualifier applies only if you specify /NOEXERCISE.
default is /ERASE.
Note
Using /NOERASE may cause sensitive data to remain
on the disk.
If the disk contained files marked
as 'erase on delete' (protection code of 128 or
higher), you should not use /NOERASE unless you
are sure that no security problems will result.

15-9

The
The

INITIALIZE (Disks)
/EXERCISE=n
/NOEXERCISE
Controls whether to check for bad blocks by "exercising" the
disk.
This means that the number of patterns you select (n) are
written to the disk, and then each block is read to make sure
that the patterns were written correctly.
If the patterns read
do not match the patterns written, RSTS/E assumes the block is
bad.
RSTS/E adds any bad blocks found to the "bad block" file
(BADB.SYS in account [0,1] on the disk). RSTS/E does not store
data in any blocks allocated to the BADB.SYS file.
You can have the INITIALIZE command run from zero to three
patterns by specifying 0, I, 2, or 3 for n.
Each pattern
consists of three octal words; the pattern used for each of these
numbers is:
Pattern

Three Octal Words

155555 133333 066666

133333 066666 155555

066666 155555 133333

For example, /EXERCISE=2 causes pattern 1 to be written to and
read from the disk, followed by pattern 2 being written to and
read from the disk.
You can.also select the default, /EXERCISE=FULL, which uses all
three patterns, one at a time.
That is, each block is written to
and read from the disk three times, each time with a different
pattern. Using the FULL argument increases the probability that
all bad blocks are found, and decreases the probability that you
will lose information later by writing into a bad block.
(Note
that /EXERCISE=FULL is equivalent to /EXERCISE=3.)
The /NOEXERCISE qualifier indicates that you do not want to check
for bad blocks. For example, if you previously initialized the
disk and feel that the current bad block file is accurate, you
can save time by specifying the /NOEXERCISE qualifier. This
still writes one pattern allover the disk unless you specify
/NOERASE, but it does not read it back in.
(Note that
/NOEXERCISE is equivalent to /EXERCISE=O.)
/INDEX=position
Positions the SATT.SYS file on the disk.
SATT.SYS is the storage
allocation table created in account [0,1] during initialization.

15-10

INITIALIZE (Disks)
The position argument can be:
BEGINNING

Puts SATT.SYS at the beginning of the disk, which
avoids fragmenting the disk.
That way, more
contiguous space is available to store other files
on the disk.

MIDDLE

Puts SATT.SYS in the middle of the disk.
For
moving-head disks, it helps to locate SATT.SYS
near the middle of the disk, which reduces average
seek times for the disk heads. MIDDLE is the
default if you do not specify the /INDEX option.

Puts SATT.SYS at device cluster number n, where n
can range from 1 to the total device size divided
by the device cluster size.
See Table 15-2 for
these values.

Declares the minimum allocation unit, in S12-byte blocks, for the
Master File Directory (MFD).
The MFD is a special "catalog"
structure that RSTS/E creates during disk initialization. Along
with other key structures, RSTS/E update the MFD each time users
add or delete accounts and files on the disk. Because RSTS/E
must access the MFD frequently, you increase performance when the
MFD cluster size is large. On the other hand, a small MFD
cluster size can save some disk space.
The MFD cluster size (n) can be 4, 8, or 16; it must be greater
than or equal to the value entered for the CLUSTER SIZE
qualifier.
The default is /MFD_CLUSTER_SIZE=16. /PRIVATE
Allows only users who have accounts on a disk to access it.
you do not specify /PUBLIC or /PRIVATE, then RSTS/E assumes
/PRIVATE.

You can create a system disk by initializing the disk as /PRIVATE
and then using the CREATE/ACCOUNT command to create and position
accounts [1,1] and [1,2].
In this case, note that you must
transfer files to the disk and use the HOOK utility to make it a
RSTS/E system disk.
/PUBLIC
Allows anyone with an account on the system to access the disk.
You can use /PUBLIC to identify any disk on the system as public,
except the system disk. When the disk is mounted, it is
considered part of the public structure. You need MOUNT
15-11

INITIALIZE (Disks)
privilege to mount a public disk. After you mount it, the disk
is a logical extension of the system disk; thus, any user can
create files on it.
In general, DIGITAL recommends against using /PUBLIC, because it
can degrade performance over time. Consider the following points
if you decide to select /PUBLIC for disks on your system:
o

If your system disk is nearly full, and you want to dedicate
one or more additional disks to general file storage, you
might add public disks to your system. Users are not
generally aware of whether their files are on the system disk
or a public disk.

A public disk is an extension of the system disk; therefore,
it should always remain mounted during timesharing. In
addition, you must remount it every time you restart the
system. If you dismount the disk during timesharing, some
users' files will mysteriously (to them) disappear.
Dismounting a public disk causes disruption unless you
transfer all of the files on the disk to the system disk or
to some other public disk.

Before adding a public disk to your system, consider the
alternative of adding a private disk for use by specific
users. DIGITAL recommends this alternative because it yields
significantly better system performance. However, this means
that you must create accounts explicitly on the private disk.
In addition, users who have accounts on the disk must refer
explicitly to that disk in file specifications.

Because of these considerations, the system provides several
safety checks on initializing and mounting a public disk. First,
you must have MOUNT privilege to do so. Second, you must specify
/PUBLIC two times: when you initialize the disk, and when you
mount the disk.
/QUERY
/NOQUERY
When you use the /QUERY qualifier, INITIALIZE displays the
characteristics of a disk you have selected that already has a
RSTS/E file structure, and asks if you still want to initialize
the disk.
Thus, /QUERY lets you verify that you are initializing the disk
you intended, thereby keeping you from accidentally wiping out
the wrong disk. If you specify /NOQUERY, INITIALIZE simply
displays the characteristics of the disk before overwriting its
contents. The default is /QUERY.

15-12

INITIALIZE (Disks)
The display of disk characteristics is similar to:
This disk pack appears to be a RSTS/E formatted
disk with the following characteristics:
Pack ID :
Pack Cluster Size
Pack is currently

THELMA
4

Private,
Level 1.2

Proceed (Y or N)?
You must respond to the prompt with YES or NO, or some
abbreviation of these. NO cancels the initialization; YES
requests that it proceeds. There is no default response to the
prompt.
/RETAIN
/NORETAIN
Controls whether to use a previously initialized disk's bad block
file. A disk that has not been previously initialized has no bad
block file.
In this case, /RETAIN and /NORETAIN are meaningless,
and are ignored if specified. /RETAIN is the default on a
previously initialized disk.
If you use both the /RETAIN and /EXERCISE qualifiers, the
INITIALIZE command keeps the old bad block file and adds any
additional bad blocks it finds while it is checking the disk for
bad blocks.
If you specify /NOEXERCISE, then you should use /RETAIN. Because
/NOEXERCISE does not exercise the disk for bad blocks, you should
use /RETAIN to keep the existing bad block information.
The /NORETAIN qualifier is useful if problems with a disk drive
have been causing apparent bad blocks on a disk. After you learn
that the problem is with the drive, you can recover space on the
disk by using /NORETAIN.
/WRITE
/NOWRITE
Determines whether the disk should default to read-only
(/NOWRITE) or read/write (/WRITE) access when it is mounted.
This is useful when you initialize a disk that is usually mounted
read-only.
The default is /WRITE.
When mounting a disk, you can override the read-only access by
specifying the /WRITE qualifier with the MOUNT command.

15-13

INITIALIZE (Tapes)
INITIALIZE Command for Tapes
The INITIALIZE command for tapes prepares a new tape or recycles a
used tape that contains no useful files.
The INITIALIZE command for
tapes makes any existing data on the tape unavailable to
file-structured access.
For ANSI tapes, it also writes a label that
RSTS/E uses to identify the tape iri a MOUNT command (ANSI tapes
require a label).
INITIALIZE allocates the tape drive if it is not
already allocated.
When used for tapes, the INITIALIZE command does not require any
special privilege unless the device is restricted.
If so, DEVICE
privilege is required.
;- - - -

- -- - - - - - - - -- - - - - - -- - - - - - - - - - - - --- - -- - ---- - --- -- - - -- -- --;-

Format
INITIALIZE tape-device-name[:] [label]
Command Qualifiers

Defaults

/DENSITY=nnn
/FORMAT=ANSI
/FORMAT=DOS

See Discussion
See Discussion
See Discussion

prompts
Device: magtape[:]
Label: label (if ANSI)
Proceed (Y or N)?

- - - --- - - - - - -- - - - - - - - --- - --- - -------- - - ------------ - - --- - --;-

Command Parameters
tape-device-name[:]
Specifies the name of the drive on which the tape is physically
mounted.
[label]
Specifies the identification label to be encoded on the tape.
The label can consist of a maximum of six alphanumeric
characters.
An ANSI-format tape requires a label; RSTS/E prompts you for a
label if you do not specify one. RSTS/E checks this label
against the label you specify when you later use the MOUNT
command (see the section "MOUNT Command for Tapes").

15-14

INITIALIZE (Tapes)
DOS tapes do not allow labels: RSTS/E ignores any label you
specify for them and displays a warning message.
Command Qualifiers
/DENSITY=nnn
Specifies the density in bits per inch (bpi) at which the tape is
to be written. You can specify a density of either 800 or 1600
bpi if the tape drive supports it.
The default density is the value specified using the DCL command,
SET SYSTEM/DENSITY= (see Chapter 14), unless the controller does
not support that density.
/FORMAT=ANSI
/FORMAT=DOS
Specifies the tape format.
If you do not specify a format, the
system uses the current system default (SHOW SYSTEM command
displays the cur~ent system defaults).
You can change the
default format using the DCL command, SET SYSTEM/LABEL= (see
Chapter 14). As mentioned earlier, ANSI format requires a label;
DOS format ignores any label specified.

15-15

MOUNT (Disks)
MOUNT Command for Disks
The MOUNT command prepares an initialized disk for processing under
timesharing.
To mount a disk, you must:
1.

Physically mount the disk on a device drive

Put the drive on line

Use the MOUNT command to logically mount' the disk

You need the MOUNT privilege to mount a disk that has been initialized
as public.
For users with MOUNT privilege, the MOUNT command rebuilds
a "dirty" disk -- one that has been physically dismounted (removed
from the drive) or taken off line without being logically dismounted
first with the DISMOUNT command. This is the only time that a disk's
"dirty" bit is set, although you may choose to rebuild the disk at
other times to maintain integrity of its structure.
If MOUNT discovers the disk needs rebuilding, it displays the message:
Disk is being rebuilt - wait ...
The rebuild operation proceeds and the disk is logically mounted when
the dollar prompt ($) for the next DCL command appears. However, if
the rebuild operation discovers blocks that have been allocated to
more than one file (doubly allocated blocks), MOUNT displays a message
asking which file to allocate each doubly allocated block to. You can
choose a file at that point or stop and mount the disk without
rebuilding, which lets you examine the situation further.

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Format
MOUNT disk-device-name[:] pack-id [logical-name[:]]
Command Qualifiers

Defaults

/PRIVATE
/PUBLIC
/[NO]QUOTA
/[NO]REBUILD
/[NO]RESTRICT
/[ NO] SHARE [=n]'
/[NO]WRITE

/PRIVATE
/PRIVATE
See Discussion
See Discussion
/NORESTRICT
See Discussion
See Discussion

Prompts
Device: device-name[:]
Pack-id: pack-id
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
15-16

MOUNT (Disks)
Command Parameters
disk-device-name[:]
Specifies the physical or logical name of the drive containing
the disk you want to logically mount.
pack-id
Specifies the one to six character alphanumeric pack
identification label written to the disk during initialization.
(See the INITIALIZE command description in the section
"INITIALIZE Command for Disks.") MOUNT then verifies that the
pack-id written on the disk is the same as the label you
specified in the MOUNT. This process helps make certain that you
physically mounted the right disk.
You must include a pack-id to mount a disk.
pack-id, the system prompts you for it.

If you omit the

[logical-name[:]]
Lets a user with INSTAL privilege assign a system-wide logical
name to the disk drive specified by a device name.
If you do not
specify a logical name and you have INSTAL privilege, the system
uses the pack-id label as a system-wide logical name for the
drive.
You may want to use this logical name to keep the pack-id
from unauthorized users. Unauthorized users can see logical
names assigned to devices in SYSTAT. RSTS/E ignores the
specification of a logical name by an unauthorized user (without
INSTAL privilege), but the mount succeeds.
Command Qualifiers
/PRIVATE
/PUBLIC
Declares that the disk you are mounting is accessible to all
users on the system (a public disk), or only accessible to users
who have accounts on the disk (a private disk).
The default is
/PRIVATE.
The action taken for /PRIVATE and /PUBLIC depends on two things:
o

Whether you have MOUNT privilege when issuing the MOUNT
command

Whether you initialized the disk as public or private

In general, the disk is safeguarded, even against a user with
MOUNT privilege, from being inadvertently made available for
public use.

15-17

MOUNT (Disks)
For Users with MOUNT privilege
If you have MOUNT privilege, you can MOUNT a disk initialized as
private. You can explicitly declare the usage with the /PRIVATE
or /SHARE qualifier, but this is not required. You can also
mount the disk with the /NOSHARE=n qualifier, to make the disk
accessible only to job n (see the discussion for /NOSHARE[=n]).
Table 15-3 summarizes the possibilities of the /PUBLIC, /PRIVATE,
and /[NO]SHARE qualifiers.
(If none of these qualifiers is
specified, RSTS/E assumes /PRIVATE.)
Table 15-3:

The /PUBLIC, /PRIVATE, and /[NO]SHARE Qualifiers for the
MOUNT Command

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
INITIALIZE for disk was:
I
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - --+
I Privi.leges I
Public
Private
I
+ - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I
I User does
I not have
I MOUNT
I privilege

I
I Any MOUNT returns an
I error.
I
I

I
I Only a MOUNT/NOSHARE
I succeeds.
I
I

I
I
I
I
I

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - --+

User has
MOUNT
privilege

MOUNT with /PUBLIC
succeeds: the disk is
accessible to all users.
MOUNT with /PRIVATE or
/SHARE succeeds: the disk
is accessible to only
those users with an
account on the disk.

MOUNT/PUBLIC returns an
e~ror. MOUNT with no
qualifier or with
/PRIVATE, /SHARE, or
/NOSHARE succeeds.

MOUNT with /NOSHARE[=n]
succeeds; the disk is
accessible only to job n
(the user's job, by
default) .
MOUNT with no qualifier
succeeds as private disk:
the disk is accessible to
only those users with an
account on the disk:
RSTS/E displays a warning
message.
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - -+-. - - - - - - - - - - - - - - - - - - - - - - - --+
15-18

MOUNT (Disks)
/QUOTA
/NOQUOTA
controls whether quota checking is performed when the disk is
mounted. This qualifier applies only to Level 1.2 disks. The
default is /QUOTA.
/REBUILD
/NOREBUILD
controls the rebuilding of a disk, regardless of whether the disk
was initialized as read/write or read-only. A dirty disk is one
that has been physically dismounted (removed from the drive)
without being logically dismounted first by a DISMOUNT command.
A DISMOUNT checks to see that no files are currently open on a
disk.
If files are open, the DISMOUNT does not succeed. If
someone makes a mistake and physically removes a disk pack from a
disk drive while programs are still using files on the disk, the
usual "clean-up" operations that the RSTS/E monitor performs may
not have occurred.
For example, the monitor keeps the file
SATT.SYS (the storage allocation table for the disk) in memory
and updates it when files are added to or deleted from the disk.
If someone physically dismounts a disk before the monitor has
written SATT.SYS back to disk, the data in the old SATT.SYS will
probably be incorrect.
Rebuilding a disk requires MOUNT privilege. This operation
performs necessary clean-up before the disk can be used again.
Specifically, a rebuild operation:
o

Locates blocks that have been allocated to more than one
file.
The system displays a message listing the files to
which such blocks have been allocated, and asks you to delete
all but one of the files.

Deletes invalid directories.

Deletes all files that have the type .TMP, are -marked for
deletion, or have no accounting entry.

Builds a new storage allocation table (SATT.SYS), to show
current file allocations (after deletions accomplished by
rebuilding).

Zeroes all blocks that were in the old storage allocation
table (SATT.SYS), but not in the new one. This is done as a
security precaution: in case these blocks belonged to files
with a protection code of <128> or higher (which are always
zeroed when they are deleted).

15-19

MOUNT (Disks)
A MOUNT operation for disk automatically checks to see if the
disk is dirty. If so, and you have MOUNT privilege, a rebuild
occurs automatically, regardless of whether you specify /REBUILD.
The following message appears to indicate that the disk is being
rebuilt:
Disk is being rebuilt - wait ...
However, if a user without MOUNT privilege tries to mount a dirty
disk, RSTS/E displays the error message:
?Disk needs rebuilding but you do not have MOUNT privilege
The /REBUILD qualifier forces a rebuild on a disk. It lets the
user with MOUNT privilege rebuild a disk that the system has not
identified as "dirty." For example, some programs leave temporary
files in the user's account, rather than deleting them before the
program exits. Such a disk is not flagged as dirty. If you want
to get rid of the temporary files on a disk, you can mount the
disk using the /REBUILD qualifier.
If you specify /REBUILD and the drive is write-protected, RSTS/E
displays the following error message:
?Can't rebuild disk because device is write-protected
If a user without MOUNT privilege specifies /REBUILD, RSTS/E
displays the following error message:
?You must have MOUNT privilege to rebuild the disk
The /NOREBUILD qualifier overrides an automatic rebuild of a
dirty disk. You may not want to take the time to rebuild the
dirty disk. Or, the disk may have doubly allocated blocks, and
you do not want to risk deleting them. In this case, you can
mount the disk with the /NOREBUILD qualifier (thus granting only
read-only access) and try to correct the situation. For example,
you could use the COpy command to copy the files to new locations
(where they do not contain doubly-allocated blocks) and try to
sort out the situation from there.

15-20

MOUNT (Disks)
If you have MOUNT privilege, and specify /NOREBUILD to mount a
dirty disk, the disk is mounted restricted and read-only, and two
warning messages appear:
%Disk needs rebuilding
%Disk is restricted and mounted no-share, read-only
Thus, the disk is accessible only to the job that mounted it.
When a user without MOUNT privilege specifies /NOREBUILD to ,mount
a "clean" (rebuilt) disk, the mount succeeds and the disk is
uneffected.
/[NO]RESTRICT
Indicates whether the disk is restricted.
If you specify the
/RESTRICT qualifier in the MOUNT command line, only users with
DEVICE privilege can access the specified disk. The default is
/NORESTRICT.
/SHARE
/NOSHARE[=n]
Controls whether to limit disk access to:
o

Job n (/NOSHARE=n)

The job that mounted the disk (/NOSHARE)

Any user with an account on the disk (/SHARE)

A disk mounted as shared is the same as a disk mounted as
private. A user with MOUNT privilege can mount a private or
public disk as shared or nonshared.
If you do not specify /PRIVATE, /PUBLIC, or /[NO]SHARE, then the
default action is to mount the disk as private (shared).
The /NOSHARE qualifier conflicts with either /PUBLIC or /PRIVATE.
You can use /SHARE with either /PUBLIC or /PRIVATEi its presence
in the same command line as the other two qualifiers has no
effect.

15-21

MOUNT (Disks)
/WRITE
/NOWRITE
controls whether data can be written to the mounted disk.
If you specify /NOWRITE, the disk is write-protected~ which means
that no users can write to the disk.
The /NOWRITE qualifier
protects files on the disk; they can only be read from, not
writ~en to.
If you specify /WRITE, users who access the disk can write to it.
When you do not specify /WRITE or /NOWRITE, the default depends
on whether the disk was initialized as read/write or read-only,
and whether the disk is clean or dirty.
For disks initialized as
read-only, the default is to give read-only access (/NOWRITE) to
the disk.
For disks initialized as read/write, there are a few
more conditions to consider.
If the disk is clean or can be
rebuilt (/NOREBUILD was not specified), and the drive is not
write-locked, /WRITE is the default.
If the disk is clean and
the drive is write-locked, /NOWRITE is the default, and the
following warning message appears:
%Device write protected
If the disk is dirty and /NOREBUILD was specified, the disk is
mounted read-only, noshare.

15-22

MOUNT (Tapes)
MOUNT Command for Tapes
The MOUNT command for tapes verifies that the tape is properly loaded
onto the unit and checks an ANSI tape for the label specified in the
MOUNT command (ANSI tapes must have labels). You issue a MOUNT
command after you have physically mounted a tape on a tape unit and
placed it on line.
If the device is restricted, you need DEVICE privilege to use the
MOUNT command.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
MOUNT tape-device-name[:][label]
Command Qualifiers

Defaults

/DENSITY=nnn
/FORMAT=argument
/[NO]WRITE

See Discussion
See Discussion
See Discussion

prompts
Device: device-name[:]
Label: label
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Command Parameters
tape-device-name[:]
Specifies the physical or logical name of the drive on which the
tape is physically mounted.
If you do not specify a unit number
with a physical device name, RSTS/E assumes unit O.
[label]
This parameter is necessary only for ANSI tapes.
If you try to
mount an ANSI tape without specifying a label, RSTS/E prompts you
for a label.
A label is not required (and is ignored) when you mount a tape in
DOS or foreign format.
In this case, RSTS/E displays a warning
message:
%Label ignored

15-23

MOUNT (Tapes)
The label specifies the one- to six-character alphanumeric label
written to the tape when it was initialized (see the INITIALIZE
command description in the section "INITIALIZE Command for
Tapes"). MOUNT then verifies that the label on the tape 'is the
same as the one you specified in the MOUNT command. This process
helps make certain that you have mounted the right tape.

Command Qualifiers
/DENSITY=nnn
Specifies the density in bits per inch (bpi) at which the tape
will be read or written. You can specify 800 or 1600 if the tape
drive supports it. Note that some kinds of drives support only
one type of density; for example, the Tu80 supports only 1600
bpi.
The density defaults to that which is currently on the tape.
this density is not supported by the tape drive, you get the
error message:

?Data error or incorrect density
If you specify a density other than the one with which the tape
was initialized, you get the error message:
?Incorrect density or uninitialized tape
/FORMAT=ANSI
/FORMAT=DOS
/FORMAT=FOREIGN
Indicates whether the tape is in a standard format used by the
RSTS/E operating system. The default format is the current
system default (see SHOW SYSTEM, Chapter 14).
The RSTS/E System User's Guide describes ANSI and DOS formats.
tape is FOREIGN if it is not in ANSI or DOS format.

Note
If you mount a tape with /FORMAT=FOREIGN, the
program you use to read the tape must know what
types of labels there are on the tape or be able
to process any labels on the tape.

15-24

MOUNT (Tapes)
/WRITE
/NOWRITE
RSTS/E checks to see whether the tape is read/write (the write
ring is present) or read-only (the write ring is not present).
If the write ring is not present and you specify /WRITE, RSTS/E
displays the following error message:
?Device is write protected
If the write ring is not present and you do not specify either
qualifier, RSTS/E displays the following warning:
%Device is write protected

15-25

Chapter 16
Backing Up and Restoring Files

Backing up disk files and accounts means copying the contents of the
disk to another volume or set of volumes. Backing up disks is a
precautionary measure to let you recover from the loss or destruction
of valuable information.
Most sites establish a policy and a schedule for regularly backing up
"disk files.
This chapter provides the operating procedures for
backing up both selected files and entire disks.
It is just as desirable to back up information on private disks as it
is to back up public disks. However, responsibility for backing up
the files on private disks could be left to the individual owners of
those files and disks.
There are two kinds of backups of disk files:
o

Incremental, or partial backups

Full, or all-inclusive, backups

In either case, the backup medium can be disk or magnetic tape.
Incremental backups save only those files that have been modified
recently.
Periodic full backups are necessary to provide the basis
for reconstruction of an entire disk.
As a rule, incremental backups are undertaken more frequently than
full backups. After consulting with users of the system, you decide
how often to back up files and volumes and how long to retain backup
media.
Generally, you are responsible for setting up a schedule for backing
up files and accounts, and for maintaining this schedule. The

16-1

Backing Up and Restoring Files
following schedule for backing up public disk volumes on magnetic tape
affords adequate protection of data for many installations:
o

Daily -- An incremental backup retained for seven days. This
schedule requires seven daily tapes (or sets of tapes) that
are rotated once a week.

Weekly -- An incremental backup retained for four weeks.
This schedule requires four weekly sets of tapes that are
rotated once every four weeks.

Monthly -- An all-inclusive backup retained for a year.
schedule requires twelve monthly sets of tapes that are
rotated once a year.

This

Despite all precautions, there is always the risk of losing a file.
Frequent backups and longer retention periods reduce this risk. You
may also want to consider an off-site storage facility for the monthly
save sets.
You can perform full backups to magnetic tape or to another disk.
Each has its advantages and disadvantages. The advantage of using
magnetic tape for backups is the much lower media and storage cost,
which may permit you to retain backups longer than keeping full
backups on disk.
However, there are several advantages to keeping copies on disk, which
in some cases outweigh the higher cost. Disks exhibit better data
reliability than magnetic tapes. Furthermore, disks tend to degrade
less in storage.

DCL Command Descriptions
You can use two DCL commands: BACKUP and RESTORE. Files created by
BACKUP are called Backup sets. A Backup set is a RSTS/E file that can
be copied just like any other RSTS/E file. However, only BACKUP and
RESTORE can interpret the data in a Backup set. The rest of this
chapter describes BACKUP and RESTORE in detail.
Note
Because the BACKUP and RESTORE operations can use
significant amounts of system resources, TUNE and
INSTALL privileges are needed to use these commands.
Additional privileges may be required to use certain
qualifiers (for example, /ACCOUNT_DATA requires GACNT
or WACNT privilege). If you want to delegate the
responsibility for backing up certain files (for
example, files on private disks) to the individual
owners, they will need the necessary privileges.
16-2

BACKUP
BACKUP Command
The BACKUP command creates a Backup set on a specified disk or
magnetic tape from one or more RSTS/E disk files.
Once the BACKUP
utility determines the syntactical validity of the. command
specification and issues any warning message relative to either the
command or the environment, BACKUP prompts with:
Please mount volume 1 of Backup set backup-set-name
Where can this volume be located <default>?
At the prompt, enter the device name to write the Backup set to. The
default is the output device you specified in the BACKUP command line.
You can use the /INITIALIZE and /NOINITIALIZE qualifiers to control
initialization of the output device.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Format

I BACKUP input-file-spec output-backup-set-spec

I Command Qualifiers
I
I /[NO]ACCOUNT DATA
I /BLOCK_SIZE=value
I /BUFFER SIZE=n
I /CREATED=(date/time or range)

I IMODIFIED=(date or range)
I /DENSITY=n
I /END=[NO]REWIND

[,[NO]DISMOUNT]
I
I /EXCLUDE[=(filespec list)]

I /[NO] FILE_DATA
I /[NO]GROUP SIZE[=n]

I /INCLUDE=(filespec list)

I /IN_LABEL=name
I /[NO]INITIALIZE
I /[NO]LIST_FILE[=filespec]
I /OUT_LABEL=name
I /[NO]PROMPT
I /[NO]QUERY
I /[NO]REWIND
I /[NO]VERIFY
I

Defaults
/NOACCOUNT_DATA
/BLOCK_SIZE=2048
See Discussion
ALL if neither /CREATED
or /MODIFIED is present
Highest available
/END=DISMOUNT
None excluded
/FILE_DATA
/GROUP_SIZE=lO
None included
Volume ID is not checked
See Discussion
/LIST FILE=KB:
See DIscussion
/PROMPT
/NOQUERY
/NOREWIND
/NOVERIFY

I prompts
I

I See Discussion

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

16-3

BACKUP
Command Parameters
input-file-spec
Identifies the files to be backed up.
The file specification
should be a standard RSTS/E file specification or a list of
specifications separated by the plus (+) sign or a comma (,):
dev:[p,pn]filename.typ, ...
You must specify the device.
The PPN is optional and defaults to
the user's current account.
The file specification is optional
and defaults to *.*. You can use standard wildcards.
If you specify a filename but not the type, BACKUP assumes a *
type.
If the filename ends with a period, BACKUP assumes a null
type.
If you specify a file type, you must also specify a
filename.
output-backup-set-spec
Identifies the device where the Backup set is to be created.
Backup set specification should be a standard RSTS/E device
specification of the format:

The

dev:[PPN]filename.typ
You must specify the device.
PPN is optional and defaults to the
user's current account.
The file specification is optional and
defaults to BACKUP.BCK.
If the backup operation needs more than one volume in the Backup
set, BACKUP prompts for subsequent volumes as follows:
Please dismount volume 1 of Backup set backup-set-name
Please mount volume 2 ot Backup set backup-set-name
Where can this volume be located <default>?
Command Qualifiers
/[NO]ACCOUNT_DATA
If you specify /ACCOUNT DATA and you have the necessary
privileges (GACNT or WACNT), BACKUP preserves all pertinent
information about the account (quotas, password, privileges, and
so on).
RSTS/E uses this data to create accounts during a
RESTORE.
If you do not have accounting privileges (GACNT or WACNT), BACKUP
only saves the attributes of your account that you have access
to.
In particular, you can not access the password attribute or
restricted user attributes.

16-4

BACKUP
If you specify /NOACCOUNT DATA, RESTORE cannot create accounts
that do not exist in the Backup set. The default is
/NOACCOUNT_DATA.
/BLOCK_SIZE=value
The /BLOCK SIZE qualifier lets you select the block size used for
the output-Backup set. You must specify the value argument.
Value can be in the range 2048 to 4080 bytes for tape, and 2048
to 7680 bytes for disk.
Further, the value must be a multiple of
16 for tape and 512 for disk.
If you do not specify /BLOCK_SIZE, BACKUP uses 2048 bytes.
Note
Use of this qualifier can affect the performance
and reliability of BACKUP.
If you use large
values, BACKUP operates faster and can store more
data into a volume.
Smaller values cause less
data to fit into a given volume; however, they
can increase the reliability (see the description
of the /GROUP_SIZE qualifier).
/BUFFER_SIZE=value
The /BUFFER_SIZE=value qualifier controls the size of the dynamic
region used by BACKUP.
The valid range is 3 to 127. The value
represents the number of K-words of memory to be used by BACKUP
as buffer space.
In general, the larger you specify n, the
faster BACKUP performs. However, large numbers increase the
system loading and resource usage, and can seriously impact other
users.
If /BUFFER SIZE=value is omitted, BACKUP uses the minimum buffer
space consistent with the other qualifiers.
If the amount of
memory requested is not available, BACKUP uses as much memory as
possible and displays an informational message.
/BUFFER_SIZE=MAXIMUM uses as much available memory as possible
without displaying any message.
/CREATED=(BEFORE=date-time, AFTER=date-time)
/CREATED=date-time
/MODIFIED=(BEFORE=date, AFTER=date)
/MODIFIED=date
The /CREATED and /MODIFIED qualifiers let you select the files to
be backed up, as chosen by the file specification criteria (see
the input-file-spec description), based on the creation date/time
and/or revision date.
If no file specification criteria exist,

16-5

BACKUP

these qualifiers apply to all files on the input volume for this
operation. You can use /CREATEDand /MODIFIED in conjunction
with each other; they are not mutually exclusive.
To be
selected, a file has to satisfy all the criteria you specify.
You can specify an exact date or range of dates for either
qualifier.
In the range format, each qualifier must take an
argument of one or both of the subqualifiers BEFORE or AFTER.
The subqualifier order in the argument is immaterial.
The date-time argument is of the standard form (for example,
dd-mmm-yy or yy.mm.dd and hh:mm A/PM or hh:mm). You must specify
the date.
If you do not specify the time, it defaults to 00:00.
In addition, if you specify the time, you must be separate it
from the date by a colon (:).
The following generic terms can be used in the subqualifier:
o

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

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

When used with /CREATED, the generic terms also accept a time
argument.
If you do not specify either /CREATED or /MODIFIED, BACKUP
selects all specified files for transfer to the Backup set.
Note
Files transferred by BACKUP retain their original
creation and revision dates (that is, the dates
on the source volume).
You need DATES privilege
to alter the Backup set dates.
/DENSITY=n
Specifies the recording density to be used on the output volume.
The default value is the highest density available on the drive
addressed.
If you select a density that is not valid for the drive
addressed, BACKUP displays a warning message:
Density of <density> BPI not available, using <density> BPI
instead
You can only specify this qualifier for the first volume of a
Backup set. Subsequent volumes are written at the same density
as the first volume unless the addressed drive is different from
16-6

BACKUP
the first drive and the original density is not available on the
-addressed drive.
In this case, the density is the highest
density available for the addressed drive.
/END={REWINDI NOREWIND I DISMOUNT I NODISMOUNT}
(For magnetic tapes only) REWIND causes the magnetic tape to be
rewound to the load point and dismounted following successful
completion of the BACKUP operation. NOREWIND causes the magnetic
tape to remain positioned after the most recent Backup set.
The
default is NOREWIND.
If you want the Backup set's device to remain mounted at the end
of the BACKUP operation, specify NODISMOUNT in·the command line.
The default is DISMOUNT.
/EXCLUDE=(filespec list)
Lets you specify files that you want excluded from the BACKUP
operation (for example, [O,l]SWAP.SYS). You can include a list
of file' specifications in the command line up to the maximum
length of a DCL command line.
/[NO]FILE_DATA
Controls the transfer of file data during a backup operation.
If
you specify /FILE_DATA, the operation proceeds with actual file
data being transferred to the Backup set from the RSTS/E volume.
If you specify /NOFILE DATA, no files are written to the Backup
set. Use /NOFILE DATA-with /ACCOUNT DATA to back up only
accounting data. The default is /FILE_DATA.
/[NO]GROUP_SIZE[=n]
Specifies the group size for XOR redundancy.
The optional
argument can be a decimal number from 0 to 100.
If you specify
zero (equivalent to /NOGROUP SIZE), BACKUP creates the Backup set
without XOR redundancy.
The-default is /GROUP_SIZE=lO.
The /GROUP_SIZE qualifier causes additional error recovery data
to be stored in the Backup set. RSTS/E uses this information to
recover from media errors during a RESTORE operation.
The smaller the number, the greater the chance of recovering from
data errors on RESTORE.
Note that a smaller number also makes
the Backup set larger.
RESTORE can recover from one error in each group.
So, for
example, if you specify /GROUP SIZE=20, RESTORE can recover from
one error in every 20 blocks. -That is, with /GROUP_SIZE=20,
16-7

BACKUP
RESTORE cannot recover from 2 or more errors every 20 blocks.
Note that the /BLOCK_SIZE qualifier sets the size of each Backup
set block.
So, if RESTORE cannot recover 2 blocks of data, you
lose 2 blocks of that size.
In general, if something cannot be
recovered, you lose less data with a smaller /BLOCK_SIZE.
/INCLUDE=(filespec list)
Lets you specify files or accounts that you want to be
unconditionally processed. You can include a list of file
specifications in the command line up to the maximum length of a
DCL command line.
Files in this set override those excluded with the /EXCLUDE
qualifier.
/IN_LABEL=name
Specifies the name to be compared to the source volume ID.
If
you use this qualifier, the source volume ID must equal the
specified name before the BACKUP can be perform the requested
operation.
/[NO]INITIALIZE
Specifies the disposition of the output media prior to the data
transfer operation and sets the default device specification in
the Where can this volume be located <default>? prompt.
For disk volumes, /INITIALIZE specifies that any file structure
on the disk is to be disregarded and the volume is to be
reinitialized with a RSTS/E file structure as if it were done
with the INITIALIZE command.
BACKUP also creates a nonuser account on the disk to hold the
Backup set.
That account is the account explicitly specified in
the output specification, or implicitly specified as the current
account of the caller.
The pack cluster size is 16, the UFD
cluster size is 16, and the file cluster size for the save set is
set to the amount of free space on the disk divided by 100,
rounded up to the next highest power of two. BACKUP does not
define any accounting data for the created account.
For magnetic tape volumes, /INITIALIZE specifies that BACKUP
initializes the tape as a standard ANSI tape.
You can only specify /NOINITIALIZE when doing a BACKUP to tape to
create a new Backup set to be appended to the end of a tape
containing other files (possibly other Backup sets).

16-8

BACKUP
/[NO]LIST_FILE[=filespec]
Controls the production of a directory-like listing file that
catalogs the sequence of events in the BACKUP operation. The
file specification can be any valid RSTS/E file specification
(wildcards are not allowed). The default is your terminal.
You can use this qualifier to produce a listing of files in the
Backup set, and then copy that file onto the backup volume.
In
this way, each backup volume has at least two files; the Backup
set and a listing of the contents of the Backup set.
/OUT_LABEL=name
Specifies the desired name for the output volume 10. The
resultant name can vary depending on the interaction between
/OUT_LABEL and /[NO]INITIALIZE.
Table 16-1 summarizes the possible outcomes of the interaction of
/[NO]INITIALIZE and /OUT_LABEL during BACKUP.
Table 16-1:

/INITIALIZE and /OUT_LABEL Interaction During BACKUP

+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Qualifiers
I
I
I
Specified
I
Output Volume ID
I
+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I /OUT_LABEL=name
I /INITIALIZE
I
I /OUT_LABEL=name
I /NOINITIALIZE
I
I
I /INITIALIZE
I (only)
I
I /NOINITIALIZE
I (only)

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

I
I
I
I
I
I
I
I
I
I
I
I
I

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

16-9

BACKUP
/[NO]QUERY
Causes BACKUP to prompt the user for each file that meets the
selection criteria as to whether or not the file should be
transferred. A Y[ES] response effects the transfer. A response
of N[O] or pressing RETURN bypasses the file. Any other response
causes the prompt to be reissued.
The default is /NOQUERY.
/[NO]REWIND
Specifies the disposition of a magnetic tape Backup set volume
before processing.
The default is /NOREWIND.
If you
at the
If you
set on

specify /REWIND, the tape is rewound and processing begins
first Backup set on the volume or the named Backup set.
specify /NOREWIND, processing begins at the next Backup
the volume or the named Backup set.

If the logical end-of-tape on the volume is found before locating
the desired Backup set, BACKUP rewinds the tape and displays an
error message at your terminal.
/[NO]VERIFY
The /VERIFY qualifier specifies that a comparison operation is to
be performed on all data transferred.
This post-process
verification reports the presence of any data differences.
For
any differences found, BACKUP displays the PPN, file name, and
file type at the user's terminal.
The default is /NOVERIFY.
Restrictions
Backup sets produced by the BACKUP utility are not bootable.
They can be used to recover a dead system by booting a
maintenance volume (for example, the distribution media) which
contains the BACKUP code (see the RSTS/E System Installation and
Update Guide).
Examples
Table 16-2 shows command formats for BACKUP operations and some
of the qualifiers associated with a backup operation.

16-10

BACKUP
Table 16·2:

BACKUP Quick Reference Table

+-. - - - _. - - - - -- - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -"- - - - - - - - - --+
I
Command Action
Command Example
I
+_. - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Save a file to a
save set on tape

BACKUP DR1:PAYROL.DAT MTO:PAYROL.BCK

Save a disk to a
save set on tape

BACKUP/ACCOUNT_DATADU1:[*,*]*.* MMO:1409MA.BCK

Save a list of
files to a save
set on tape

BACKUP DR2:PAYROL.DAT,DUl:BENEFI.DAT,VACATI.DAT MTO:DAT17M.BCK

Full backup of a
disk

BACKUP/LIST_FILE=928FEB.LOG/ACCOUNT_DATADR1:[*.*]*.* MMO:928FEB.BCK

Incremental backup
of a disk
(following earlier
full backup)

BACKUP/LIST_FILE=101SMA.LOG/ACCOUNT_DATA/CREATED=AFTER=4-FEB-8S:9:28DR1:[*.*]*.* MMO:101SMA.BCK

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

16-11

RESTORE
RESTORE Command
The RESTORE command restores a RSTS/E disk or subset thereof from a
tape or disk Backup set. Once RSTS/E determines the syntactic
validity of the command specification and issues any warning message
relative to either the command or the environment, RESTORE prompts
with:
Please mount volume 1 of Backup set backup-set-name
Where can this volume be located <default>?
At the
accept
as the
prompt

prompt, enter the device to use or press RETURN or LINE FEED to
the default value. The default value is the device specified
input parameter. If you specify /NOPROMPT, RESTORE omits the
message.

If you are doing a partial restore, and you know what volume to start
with, start with that volume (although you may start with any volume).
RESTORE issues a confirmation message and starts with the volume you
specify. Note that RESTORE may issue a warning message in this case.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Format
RESTORE input-backup-set-spec output-file-spec
Command Qualifiers

Defaults

/[NO]ACCOUNT_DATA
/BUFFER_SIZE=n
/CREATED=(date/time or range)
/MODIFIED=(date or range)
/END=[NO]REWIND
[,[NO]DISMOUNT]
/EXCLUDE=(filespec list)
/[NO]FILE DATA
/INCLUDE=(filespec list)
/IN_LABEL=name
/[NO]INITIALIZE
/[NO]LIST_FILE[=filespec]

/ACCOUNT_DATA
See Discussion
ALL if neither /CREATED
or /MODIFIED is present
/END=DISMOUNT

/OCCURRENCE=n~mber

/[NO]OPTIMIZE[=(list)]
/OUT_LABEL=name
/PLACED_POSITION[=keyword]
/[NO]PROMPT
/[NO]QUERY
/[NO]REPLACE[=QUERY]
/[NO]REWIND

None excluded
/FILE DATA
None Included
Volume ID is not checked
See Discussion
/NOLIST_FILE
/OCCURRENCE=l
See Discussion
See Discussion
/PLACED_POSITION=INDEX
/PROMPT
/NOQUERY
/REPLACE=QUERY
/NOREWIND

16-12

RESTORE
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Command Qualifiers (Cont.)
I
I /SELECT=(filespec list)
I /[NO]VERIFY
I
I Prompts
I
I See Discussion

Defaults (Cont.)
See Discussion
/NOVERIFY

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.- - - - - - - - - - - - - - - - - - - - - - -+

Command Parameters
input-backup-set-spec
Identifies the device where the first volume of the Backup set is
mounted. The Backup set specification should be a standard
RSTS/E device specification of the format:
dev:[pPN]file-spec
You must specify the device. PPN is optional and defaults to the
user's current account. File-spec is optional and defaults to
BACKUP.BCK.
If the Backup set has more than one volume, RESTORE prompts you
for subsequent volumes as follows:
please dismount volume I of Backup set backup-set-name
please mount volume 2 of Backup set backup-set-name
Where can this volume be located <default>?
output-file-spec
Identifies where to put the files or accounts to be restored.
The file specification should be a standard RSTS/E file
specification of the format:
dev:[PPN]file-spec
You must specify the device. PPN is optional and defaults to the
account you logged in to. File-spec is optional and defaults to
the file specification(s) recorded on the Backup set.
If you specify a PPN, RESTORE transfers all selected files to
that account, even if the Backup set has multiple accounts,
assuming you have sufficient privilege to create files in that
account (GWRITE or WWRITE). If file name conflicts occur as a

16-13

RESTORE

result of the RESTORE (for example, TEMP.BAS exists in two or
more accounts on the Backup set), the second and subsequent
transfers require operator intervention unless you specify the
/REPLACE qualifier.
If you specify a wildcard PPN, RESTORE transfers all selected
files to:
o

[*,*]

the same accounts as on the Backup set

[n,*]
forces the project number to n, uses the programmer
number as on the Backup set

[*,n] -- forces the programmer number to n, uses the project
number as on the Backup set

If the accounts do not exist and you specify /ACCOUNT_DATA,
RESTORE creates them with the same characteristics as they have
on the Backup set, providing you have the necessary privilege to
create the accounts (GACNT or WACNT).
.
Command Qualifiers

/[NO]ACCOUNT_DATA
If you have sufficient privilege (GACNT or WACNT), this qualifier
determines what level of information from a UFD is restored from
a Backup set.
Use /ACCOUNT_DATA to restore all accounting data that is recorded
in the Backup set both to existing and to newly created accounts.
Use /NOACCOUNT DATA to inhibit the creation of accounts and
restoration of-UFD data. The default is /ACCOUNT_DATA.
Note
If an account already exists, RESTORE supersedes
the accounting data when restoring to the
original account.
/BUFFER_SIZE=value
The /BUFFER_SIZE=value qualifier controls the size of the dynamic
region that RESTORE uses. The valid range is 3 to 127. The
value represents the number of K-words of memory that RESTORE can
use as buffer space. If you omit /BUFFER_SIZE=value, RESTORE
uses the minimum buffer space consistent with the other
qualifiers.
The larger value you specify, the faster RESTORE performs.
However, note that large values cause a greater impact to other
users.
16-14

RESTORE
If the amount of memory you request is not available, RESTORE
uses as much memory as possible and displays an informational
message.
If you specify /BUFFER_SIZE=MAXIMUM, RESTORE uses as
much memory as possible; however, it does not display any
message.
/CREATED=(BEFORE=date-time, AFTER=date-time)
/CREATED=date-time
/MODIFIED=(BEFORE=date, AFTER=date)
/MODIFIED=date
The /CREATED and /MODIFIED qualifiers let you select the files to
be restored, as chosen by the file selection criteria (see the
output-file-spec description), based on the creation dates/times
and/or revision dates.
If no file selection criteria exist,
these qualifiers apply to all files on the input volume to which
you have access for this operation. You can use /CREATED and
/MODIFIED in conjunction with each other; they are not mutually
exclusive.
To be selected, a file has to satisfy all the
criteria you specify.
You can specify an exact date or a range of dates for either
qualifier.
In the range of dates format, each qualifier must
take an argument of one or both of the subqualifiers, BEFORE or
AFTER.
The order of the subqualifiers in the argument is
immaterial.
If you specify both BEFORE and AFTER dates for
either one of the qualifiers, the AFTER date must be earlier than
the BEFORE date.
If you do not use either /CREATED or /MODIFIED, all specified
files are selected for transfer from the Backup set.
Note
BACKUP retains both the creation and revision
dates as they were on the source volume for the
files transferred if you have DATES privilege.
/END={REWIND I NOREWIND I DISMOUNT I NODISMOUNT}
(For magnetic tapes only) REWIND causes the magnetic tape to be
rewound to the load point and dismounted following successful
completion of the RESTORE operation. NOREWIND causes the
magnetic tape to remain positioned after the most recent Backup
set.
The default is NOREWIND.
If you want the Backup set's device to remain mounted at the end
of the BACKUP operation, specify NODISMOUNT in the command line.
The default is DISMOUNT.

16-15

RESTORE
/EXCLUDE=(filespec list)
Lets you specify files that you want to be excluded from the
RESTORE operation.
You can include a list of file specifications
in the command line up to the maximum length of a DCL command
line.
/[NO] FILE_DATA
Controls whether file data is transferred during a RESTORE
operation.
If you specify /FILE DATA, RESTORE transfers the file
data from the Backup set to the RSTS/E volume.
If you specify
/NOFILE_DATA, RESTORE proceeds without restoring any of the
specified files.
The default is /FILE_DATA.
If you have accounting (GACNT, WACNT) privileges, you can use
/NOFILE DATA with the /ACCOUNT DATA qualifier to restore only
account-information from a Backup set.
/INCLUDE=(filespec list)
Lets you specify files that you want to be unconditionally
processed.
You can include a list of file specifications in the
command line up to the maximum length of a DCL command line.
Files in this set override those specified with the /EXCLUDE
qualifier.
/IN_LABEL=name
Specifies the name to be compared to the source volume ID.
If
you use this qualifier, the source volume ID must equal the
specified name before the RESTORE operation can be performed.
/[NO]INITIALIZE
Specifies the disposition of the output media prior to the data
transfer operation.
The /INITIALIZE qualifier specifies that RESTORE should disregard
any file structure on the disk and reinitialize the volume with a
RSTS/E file structure as if it were done with the INITIALIZE
command.
RESTORE takes the characteristics from the source device summary.
(If the device cluster size of the original volume is too small,
the next higher valid cluster size is used for the output
volume.)

16-16

RESTORE
You can only specify /NOINITIALIZE when the RESTORE operation is
from a Backup set to an existing RSTS/E disk.
In this case,
RESTORE places the files on the existing file structures instead
of replacing them.
/[NO]LIST_FILE[=file-spec]
Generates a directory-like listing file, cataloging the sequence
of events in the RESTORE operation.
If you specify /LIST_FILE,
you must include the file specification.
It can be any legal
RSTS/E file specification (wildcards are not allowed).
The
default is /LIST_FILE=KB:.
/OCCURRENCE=number
Indicates the particular occurrence of a named Backup set to use
when more than one Backup set of the same name,exists on a
magnetic tape. You must specify the argument which refers to the
position relative to either the current tape position or the
beginning of the tape depending on the use of /[NO]REWIND.
RSTS/E Backup sets are interchangeable with VAX Backup sets.
However, VAX Backup set names can be greater than six characters,
while RSTS/E looks at only the first six characters.
Therefore,
RSTS/E cannot distinguish between two VAX names that have the
same first six characters (for example, ABCDEF and ABCDEFG).
To
transfer ABCDEFG, you must use ABCDEFjOCCURRENCE=2.
The default is /OCCURRENCE=lj the first occurrence of the named
Backup set.
/[NO]OPTIMIZE[=(list)]
The /[NO]OPTIMIZE=(list) qualifier controls RESTORE's
optimization of the directory structure.
Two optimizations are
available:
o

Directories can be extended to the size they were on the
original volume

File cluster sizes can be increased to the maximum necessary
to minimize calls to the file processor

The /NOOPTIMIZE qualifier inhibits these optimizations.
The
/OPTIMIZE qualifier selects all optimizations.
The default is
/OPTIMIZE.

16-17

RESTORE
The /OPTIMIZE=(list) qualifier selects optimizations from the
following:
o

CLUSTERSIZE --Optimize cluster size

DIRECTORY -- optimize directory size

In general, you would want to perform these optimizations to
increase overall system performance. However, if there is not
much contiguous disk space available, you would not want to make
all executable files contiguous.
Similarly, if there is little
free disk space, you would not want to optimize cluster sizes
because this takes more disk space.
/OUT_LABEL=name
Specifies the desired name for the output volume ID.
The
resultant name can vary depending on the interaction between
/OUT_LABEL and /[NO]INITIALIZE.
Table 16-3 summarizes the possible outcomes from the interaction
of /[NO]INITIALIZE and /OUT_LABEL during RESTORE.
Table 16-3:

/INITIALIZE and /OUT.LABEL Interaction During
RESTORE

+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I

Qualifiers
I
I
Specified
I
Output Volume ID
I
+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
/OUT_LABEL=name
/INITIALIZE

The specified name.

/OUT_LABEL=name
/NOINITIALIZE

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

/INITIALIZE
(only)

The destination volume name is the same as
the source volume name.

The name is unchanged.
/NOINITIALIZE
(only)
+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
/PLACED_POSITION[=keyword]
Controls the placement of files that were marked as placed on the
source disk.

16-18

RESTORE
The /PLACED_POSITION qualifier takes one of the following keyword
arguments:
o

INDEX -- place close to the storage allocation table and
master file directory

MIDDLE -- Place close to the middle of the disk

ORIGINAL -- place close to the original position on the
source disk.

The default is INDEX
The rules for contiguity apply first and foremost; that is,
RESTORE sacrifices placement in the interest of contiguity.
The
first sufficient contiguous space closest to the selected
position is the first choice for positioning the file on the
output volume.
If no contiguous space of sufficient size exists on the output
volume, then the first cluster(s) of the file are positioned as
close to the original address as possible and the remaining
clusters are positioned as required.
/[NO]PROMPT
Normally, the BACKUP utility issues a MOUNT prompt for each
RESTORE operation even if the Backup set's device is already
mounted.
You can eliminate the prompt for the first volume by
including the /NOPROMPT qualifier in your command line.
The
default is /PROMPT.
/[NO]QUERY
Causes RESTORE to prompt you as to whether each file that meets
the selection criteria should be transferred. A Y[ES] response
effects the transfer. A response of N[O] or pressing RETURN
bypasses the file. Any other response causes RESTORE to reissue
the prompt.
The default is /NOQUERY.
/[NO]REPLACE[=QUERY]
The /REPLACE qualifier specifies that if a file being transferred
in a restore operation already exists on the destination disk,
the file from the Backup set replaces the one already on the
disk.
The /REPLACE=QUERY qualifier tells RESTORE to query the
user before replacing a file.
The /NOREPLACE qualifier specifies that if a name conflict
occurs, the file transfer is not to take place under any
circumstances.

16-19

RESTORE

The default is /REPLACE=QUERY.
/[NO]REWIND
Specifies the disposition of a magnetic tape Backup set volume
before processing.
The default is /NOREWIND.
If you specify /REWIND, the search for the Backup set begins at
the beginning of the tape.
The /NOREWIND qualifier means the
search starts at the present position.
If the logical end-of-tape on the volume is found before the
desired Backup set, the tape is rewound and an error message
appears at the terminal.
/SELECT[=(filespec list)]
Lets you select specific files from the input Backup set to be
restored.
You can use the /SELECT qualifier in conjunction with
the /EXCLUDE qualifier and/or the /INCLUDE qualifier.
If you use
/SELECT in combination with other qualifiers, the file transfer
candidates are chosen according to the following steps:
1.

All files on the volume for which the user has read access
privilege are initially considered

If you use the /CREATED or /MODIFIED qualifiers, only those
files from step I which meet the time bracket criteria are
considered

If you use the /SELECT qualifier, only those files from step
2 that match one of the /SELECT file specifications are
considered

If you use the /EXCLUDE qualifier, any files from step 3 that
match one of the /EXCLUDE file specifications are removed
from consideration

If you use the /INCLUDE qualifier, RESTORE also considers any
files meeting the inclusion criteria, provided that you have
access to them.
Note that RSTS/E does not consider the
/CREATED, /MODIFIED, /SELECT, or /EXCLUDE qualifiers when
processing the /INCLUDE list.

/[NO]VERIFY
The /VERIFY qualifier specifies that a comparison operation is to
be performed on all data transferred.
This post-process
verification (for multi-volume Backup sets, all volumes are
transferred before any volume is verified) reports the presence
of any data differences.
For any differences found, RESTORE
16-20

RESTORE
displays the PPN, file name, and file type at the user's
terminal.
The default is /NOVERIFY.
Restrictions
If you have sufficient privilege and you specified /ACCOUNT_DATA
in the RESTORE command, and if the Backup set contains accounting
information, BACKUP creates accounts if they did not previously
exist. The account characteristics are the same as they were for
the Backup set accounts.
If the account already exists, BACKUP
replaces the existing account characteristics.
Restored volumes can be made bootable by HOOK.SAV if the file
[O,l]INIT.SYS is restored.
See the RSTS/E System Installation
and Update Guide for further details.
Examples
Table 16-4 shows command formats for RESTORE operations and some
of the qualifiers associated with restore operations.
Table 16-4:

RESTORE Quick Reference Table

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command Action
Command Example
I
+,;. - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

.Restore a file
from a save set on
tape

RESTORE/SELECT=PAYROL.DATMTO:PAYROL.BCK DR1:*.*

Restore a disk
from a save set on
tape

RESTORE MMO:1409MA.BCK DU1:[*,*]*.*

Restore a list of
files from a save
set on tape

RESTORE ,TO:DAT17M.BCK/SELECT=rAYROL.DAT,BENEFI.DAT,VACATI.DAJDR2:[*.*]*.*

Restore a disk
RESTORE/LIST_FILE=928FEB.LOGfrom a save set,
/ACCOUNT_DATA MMO:928FEB.BCK DR1:[*.*]*.*
if file exists,
replace it.
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

16-21

Appendix A
Managing the OPSER Spooling Package

This appendix describes the OPSER-based spooling package. This
package, like the new Print/Batch Services (PBS) package (see Chapter
9), provides print and batch services. Most of the programs require
SWCFG privilege to run. General aspects of related user programs,
such as QUE and BATCH, are mentioned only briefly in this appendix.
See the RSTS/E utilities Reference Manual for a full description.
The information presented here is for backwards compatibility only.
New applications should use the PBS package. Move existing
applications to PBS over time. PBS is:
o

More efficient

More flexible

Easier to manage

Handles DCL command files

Pe~mits

Has job limits

a-bit and control characters on printers

A-I

Managing the OPSER Spooling package
Overview of Operator Services
Operator services on RSTS/E involve the OPSER program and controlled
programs in OPSER tables. Controlled (online) programs are:
0

QUEMAN

SPOOL

BATCH

RESTOR

SPOOL and BATCH are spooling programs executing queued requests for
either a line printer device or batch processor. QUEMAN is the queue
manager program that passes queued requests to spooling programs and
adds, updates, and deletes requests in the various queues. RESTOR is
the optional system data restoring package that OPSER can control.

OPSER Program Overview
The OPSER program establishes interjob communication for all of ~ts
controlled programs. OPSER declares itself a message receiver with a
system-wide identification that the controlled programs can recognize.
When a controlled program starts, it declares itself a message
receiver and supplies OPSER with certain data by means of the system
message send/receive SYS call. OPSER places the program in its table
of online jobs. See the RSTS/E Programming Manual for information
about SYS calls.
The identification that OPSER uses to communicate with online programs
is called the message receiver identification, or simply, the receiver
identification. Each identification exists in the system message
receiver table and must be unique. Because of this uniqueness, only
one copy of OPSER can be running on your system. Additionally,
because all control and interjob communication of spooling jobs
depends on OPSER, the operator services program must be running before
any controlled jobs can be run.
After it establishes initial interjob communication, OPSER makes it
possible for an operator to interact with the controlled jobs. OPSER
becomes the main interface between the operator and a system
controlled program. Figure A-I shows the interaction among system
controlled programs and the operator.

A-2

Managing the OPSER Spooling Package
OPSER broadcasts information to the operator through a terminal
designated as the Operator Services Console (OSC).
For flexibility,
the operator can make any keyboard line on the system the the OSC. To
isolate the keyboard control from unwarranted tampering, OPSER itself
does not need to be connected to the OSC, but may broadcast data on
the physical keyboard line. Given that intermittent output is
generated on the OSC, any other user (including the operator) could be
logged into the system on that terminal.
OPSER itself establishes a data base by which it controls online jobs.
The data base resides in the OPSER package account OPSER$: and
consists of three work files:
o

OPSERO.WRK -- Contains the curient activities and message
control directory tables

OPSERl.WRK -- Has the table of jobs on line to OPSER, the
valid operator table, and tables of messages and legal
commands

OPSER.LOG (which can be optionally renamed) -- Provides a
history of operating activity

To provide a nonvolatile data base during a time-sharing session, as
well as continuity of operations between time-sharing sessions, OPSER
stores the work file information on disk.
Thus, if the system crashes
or if OPSER alone unexpectedly terminates, the work files retain the
most current processing information.
Similarly, these files maintain
data continuity from one time-sharing session to another.
Whenever OPSER starts, it examines its files to determine whether
entries in the online job and valid operator tables are still valid.
Generally, OPSER retains active and valid entries and purges any
entries that do not satisfy validation requirements. Upon restarting,
therefore, OPSER attempts to preserve data from its previous
operational state.
The most convenient way to interact with OPSER is through the PLEASE
program.
PLEASE transmits commands to the OPSER program. OPSER
checks that the sender is a valid operator and, if so, takes the
requested action. Because of PLEASE, the operator need never directly
run or attach to OPSER to perform operator functions on controlled
jobs.
See the section "Operator Communication Program: PLEASE" for a
description of the PLEASE program.

A- 3

Managing the OPSER Spooling Package

OPSER$:QUEUE,WRK OPSER$:TEMPnn.QUE
File
File

RJ2780

.---------:_B_~.,...~S.,..bP-l---l~----U
OPSER$:BATDCD.DCD
File

L---r-r----.J
I I

-== =:::.:::_"::.";:

I
L ::::...-::...-_-_-_-::..-

QUEMAN
Job

LPmSPL
Job

I
QUE
Program

OPSER$:QUEUE.SYS
File

OPSER$:CHARS.QUE
File

OPSER

-=--=-.:: =--=--=--=-:..-:..-=.,- - - - - - - ----,1

detached)

r---I--_,

K~~~~~~d

BACKUP.PRM
File

PLEASE
Program

Figure A-I:

OPSER$:OPSER.LOG
OPSER$:OPSERO.WRK'
File
File
OPSER$:OPSER1.WRK
File
I-MK-00077-01

Communication method:

-----

(detached)

l}- L. _R_E_~a_~O_a~_ht_:r-~~o~~;a~m~~------I (" "_- L.J_Ob-'- _._L. . ,~ U
-----z....-

Operator
Services
Console

broadcast
message send/receive
direct access

System Controlled Programs and Operator Interaction

OPSER provides processing checks for online jobs.

OPSER makes sure
that all online jobs are still active, are still valid receivers, and
are not hibernating. If any job is found to be hibernating, OPSER
notifies the operator, who can attach the job to a terminal, remedy
the cause of the hibernation, and/or restart the job.

A-4

Managing the OPSER Spooling Package
OPSER interaction between a controlled job and the operator is
recorded in one of three ways:
o

As a message -- A message is specifically formatted data to
which OPSER assigns a sequence number for operator reference.

As an action request -- An action request is a special
message that requires operator action and a response before a
controlled job can resume processing. A request usually
involves both performing an action (such as mounting a
volume) and typing an answer (such as a device designator or
program interrupt command) in direct response to the request.

As an information line -- An information line is a free form
report of some internal operation performed.
Information
lines are typically not important to the operator function
but merely provide a history of online events.

QUEMAN Program Overview
The QUEMAN program manages the system queue file OPSER$:QUEUE.SYS.
The file retains all pending user requests and can store requests
between time-sharing sessions. Users make requests of spooling
programs through the QUE system program.
To form a request for a
user, QUE builds a message and sends it to QUEMAN, which updates the
QUEUE.SYS file.
QUEMAN maintains a table of online spooling programs in a work file,
QUEUE.WRK, which is stored in the OPSER package library (OPSER$:).
The program passes a queued request to a destination spooling job not
currently busy with a request. As a spooling job completes a request,
it notifies QUEMAN, which updates the queue and work files and checks
for another request to pass to the spooling job.
A spooling program typically handles one request at a time from
QUEMAN.
If no request is pending for a spooling program, the job
enters an indefinite sleep state. The job is not awakened until the
system queues a message for it.
The message is the result of QUEMAN
or OPSER transmitting data to the spooling job by means of the system
message send/receive mechanism.
To retain as much data as possible between time-sharing sessions,
QUEMAN, like OPSER, examines its files upon restarting. After
restarting, QUEMAN should resume processing with no loss of data from
its previous run. QUEMAN examines the queue file structure and
contents and reestablishes synchronization with any spooling jobs
already on line and active.

A-5

Managing the OPSER Spooling Package
SPOOL Program Overview
The SPOOL program handles requests made for line printer output.
SPOOL maintains dual communication paths: one with QUEMAN and one with
OPSER.
QUEMAN transmits queued requests to SPOOL.
SPOOL interacts
with QUEMAN only to notify it that a transmitted request is completed.
Under normal circumstances, communication between SPOOL and OPSER is
necessary only when an operator requires some special action (for
example, aligning forms) of the spooling job.
To identify output of a user's queued request, SPOOL prints heading
burst pages.
The program accesses the character generation file
OPSER$:CHARS.QUE to form the large, easily readable letters necessary
to distinguish discrete requests and files within a request.

BATCH Program Overview
The BATCH program executes user requests by running a job for a user
on a pseudo keyboard. By using a pseudo keyboard, BATCH eliminates
the requirement for a physical terminal and relieves the user from
typing by processing commands from a.disk file.
BATCH, like SPOOL, maintains dual communication paths: one with QUEMAN
and one with OPSER. QUEMAN sends a message to BATCH to process a job
request.
BATCH interacts with QUEMAN only to notify it that a
transmitted request is completed.
BATCH typically depends on OPSER to
form requests for operator action.
To mount a user volume, for
example, BATCH notifies OPSER.
In turn, OPSER generates the request
for the operator and processes the response from the operator.
To process commands from a user-queued disk file, BATCH requires the
command decoding file OPSER$:BATCH.DCD.
The BATCH.DCD file contains
all the codes and parameters BATCH needs to decode user-specified
control statements, perform syntax checking, and form a special
intermediate file (BAnJmm.COM) of encoded BATCH commands.
Both the SP90L and BATCH programs charge processing (execution) time
to the account under which the user queues the request.
Overhead
time, used to set up a request, is charged to the account under which
the program is running.

RJ2780 Program Overview
The RJ2780 program is an optional layered product. Unlike BATCH and
SPOOL, RJ2780 maintains only one communication path. QUEMAN .sends a
message to RJ2780 to process the next request (send a file).
The

A-6

Managing the OPSER Spooling Package
RJ2780 program can also send a message to QUEMAN requesting that SPOOL
print a file that RJ2780 has received.
RJ2780 has no communication
with OPSER.

Controlling RESTOR with OPSER
An operator can control the RESTOR program through OPSER.
If RESTOR
runs detached, control through OPSER is the only means by which the
operator can communicate with the RESTOR job. RESTOR, when detached,
transmits all operator requests through OPSER and receives responses
only from OPSER.

Overview of OPSER Shutdown
The entire operator services package is designed to terminate in a
controlled manner using a "shutdown level." The defined shutdown level
for each job determines the order in which OPSER terminates controlled
jobs during system shutdown.
The SHUTUP system program can be run so
OPSER terminates controlled jobs with the lowest shutdown level first.
OPSER informs each job at a certain level to complete processing at a
logical end point.
Only after OPSER shuts down all jobs at a given
level does it proceed to shut down all jobs at the next highest level.
SHUTUP itself does not proceed with final system shutdown until OPSER
terminates all of its controlled jobs and kills itself.
By using the
controlled shutdown of OPSER, you can ensure continuity of processing
user requests from one time-sharing session to another.
Since RJ2780 does not communicate with OPSER, OPSER does not
automatically shutdown RJ2780 as it does SPOOL and BATCH.

Operator Services Program: OPSER
The operator services program OPSER consists of two modules:
o

OPSER -- Establishes the initial conditions on start-up,
checks initial conditions upon restart, and chains to the
second module, OPRUN

OPRUN -- Executes commands and periodically checks status.

Each module is stored in the OPSER Package Library (OPSER$:), has a
protection code of <232>, and requires SWCFG privilege to run.
For
simplicity, this appendix refers only to one program, OPSER, which
functionally includes the two modules.

A-7

Managing the OPSER Spooling Package
You must run the OPSER program before the queue manager and spooling
programs. If your applications need to use the OPSER package, you
should start OPSER by including the RUN command in your system
start-up command file. To start OPSER, type the following command:
RUN OPSER$:OPSER
OPSER V9 RSTS V9

TIMESHARING

At this point, the OPSER program performs a number of checks before it
prints the number sign (#) prompt. The remaining portion of this
section describes these initial program checks. Once you are familiar
with this procedure, you can learn about OPSER operator commands,
described in the following sections.
If the you have SWCFG privilege, the program prints an identification
line at the terminal to indicate it is running. If you do not have
SWCFG privilege, OPSER displays an error message to indicate that you
do not have access to OPSER.
OPSER tests for the presence of its two work files (OPSERO.WRK and
OPSERl.WRK) in OPSER$:. If the work files are not present, OPSER
prints the warning message:
%OPSER files not found - will initialize
OPSER then initializes all its tables. At this point, the valid
operator table has a single entry that allows the current user (on any
terminal) to communicate through OPSER. If ERRCPY is active, the
online job table has ERRCPY as its only entry.
When OPSER finds the work files, it makes sure that it has write
access to the files. Should another job have write access to the
files, OPSER prints the following warning message and terminates:
%OPSER does not have write privileges to its files
To allow OPSER to gain write access, the operator must terminate the
job currently having write access and run OPSER again.
The program performs further special processing for currently existing
work files. The processing makes sure of data integrity in case OPSER
is being restarted after a system crash. A check is made of the
entries in the online job and valid operator tables.

A-8

Managing the OPSER Spooling package
FO~ ,each entry in the online job table, OPSER checks the following
conditions:
'0

The job number indicated in the entry must be active on the
system.

The receiver identification in the entry must exist in the
system message receiver table for that job number.

The account in the entry must be a valid account number.

An entry for an inactive or otherwise illegitimate job is removed from
the online job table.
For each active and legitimate job, OPSER
requests retransmission of the job's last message when processing
begins. When processing begins, OPSER generates a command to display
the online job table.
OPSER checks the entries in the valid operator table. Additional
actions take place depending on whether jobs found in the online job
table are active.
If the online job table has no active jobs and a
meaningless entry is in the valid operator table, OPSER clears the
table and sets initial conditions.
The resulting operator table has
one entry that allows, as valid operators, the current user from any
keyboard.
If the online job table has an active job, the program
merely removes those entries that have no meaning from the valid
operator table.
To signal a change in the current table, OPSER
creates an internal command to print the valid operator list when
processing begins.
After processing of the work files is complete, the program attempts
to declare OPSER as a receiving job.
If the declaration fails, the
program prints the error message:
?OPSER cannot declare itself a receiver
This message indicates that another copy of OPSER has been run and
must be properly terminated to allow the current copy to run
successfully.
OPSER establishes the current keyboard as the Operator Services
Console (OSC) and a file named OPSER.LOG as the default log file.
OPSER.LOG is optional, but OPSER uses it until an explicit command
closes it or assigns another log file.
When OPSER begins normal
operation, it executes any internally generated commands to list
online jobs and valid operators. After executing the commands, OPSER
is ready to accept data sent to it by any program. OPSER prints the
number sign (#) character to show that it is ready to accept commands.

A-9

Managing the OPSER Spooling Package
OPSER Operator Commands
You can abbreviate a valid OPSER command to three or more characters
and separate the command from any operands by a space character~· No
embedded spaces are allowed within a command. Delimiters within the
text of the operands are the semicolon (i) and colon (:) characters
and must be present to delimit elements of text.
Throughout the
following discussion, n~te that square brackets enclose optional
items.
Table A-I summarizes the commands and formats.
Note that the
circumflex (A) character marks the location of a required space.
Table kl:

OPSER Commands

+- - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Command Name I
Syntax and Meaning
+- - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ANSWER
I
I
I
I
I CHANGECONSOLE
I
I
I
I
I
I DELETE
I
I
I
I
I
I
I
I
I
I
I DETACH
I
I
I

ANS[WER]Amsgnumber:text
Conveys the text following the colon as a response
to an action request denoted by message number.
Also deletes the action request.
CHA[NGECONSOLE]~KBn:

Changes the operator services console to the
keyboard unit designated by n. The unit should be
on line but need not be free. It must also be set
for /BROADCAST (see Chapter 8).
DEL[ETE]~msgnumber

Deletes from an OPSER internal table an unanswered
action request denoted by its message number.

I DEL[ETE]A#m[:n]
I Deletes the n oldest (from 1 to 32) action
I requests for a given job. The command requires the
I number sign (#), the number (m) of the sending
I job, a colon (:), and the number (n) of requests
I to delete.
I
I DET[ACH]
I Detaches the OPSER program from its keyboard,

I after which the operator can run PLEASE to
I . communicate with OPSER.

A-lO

Managing the OPSER Spooling Package
Table A-l:

OPSER Commands (Cont.)

+- - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Command Name I
Syntax and Meaning
I
+ - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

EXIT

INTERRUPT

LIST

LOGFILE

I
I EXI[T]
I Closes the log file and work files, removes OPSER
I from the system message receiver table, and
I terminates the program. If the job is attached,
I the program returns you to the keyboard monitor
I prompt. If detached, the program broadcasts a
I message to the system console terminal (KBD:) and
I kills itself.
I
I INT[ERRUPT]Arcvrid:text
I INT[ERRUPT]A#n:text
I Sends the unsolicited text to an on-line job
I specified either by its message receiver
I identification or by #n (where n is the number of
I the job under which the on-line program is
I running). The LIST JOBS command listing gives job
I numbers and receiver identifications.
I
I LIS[T]AJO[BS]
I LIS[T]AOP[ERATORS]
I Prints a listing of all jobs on line to OPSER or a
I listing of valid operator accounts and keyboards.
I
I LOG[FILE]A [file];[msglevel]
I Establishes, as the OPSER log file, the specified
I file or device and sets the message level to the
I value specified. If a file or device is not
I specified, a semicolon followed by a level simply
I changes the message level of the open log file. If
I neither a file nor message level is specified,
I OPSER closes the current log file and records
I nothing more.
I
I LOG[FILE]A [file] ;AL[L]
I ALL records all messages and action requests.
I
I LOG[FILE]A [file];RE[QUESTS]
I REQUESTS records only action requests.
I
I LOG[FILE]A [file];NO[NE]
I NONE records no messages, action requests, or
I OPSER information lines.

A-II

Managing the OPSER Spooling Package
Table A-I:

OPSER Commands (Cont.)

+- - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command Name I
Syntax and Meaning
I
+- - - - - - - - - - - - -'- -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _. - --+

I
I MES[SAGE]A [level]
I Sets the level of messages for the OSC. The level

MESSAGE

controls what types of messages are printed at the
OSC. If no level is included in the command, an
error is generated.
MES [ SAGE]" AL [L]
ALL includes all messages, action requests, and
OPSER information lines.
MES[SAGE]ARE[QUESTS]
REQUESTS includes only action requests and
information lines and excludes messages.
MES[SAGE]ANO[NE]
NONE means that nothing is printed on the OSC.
(See the section "Message Types" for a discussion
of message level.)
OPERATOR

OPE[RATOR]AKBn:[p,pn]
Updates the valid operator list with the
designated keyboard unit and account combination.
The asterisk (*) character can replace the
keyboard unit, project number(p), and programmer
number (pn) to include all of that element.
OPE[RATOR]A -KBn:[p,pn]
If a minus (-) sign precedes the specification,
that specific element is deleted from the list.

RETYPE

RET[YPE]Amsgnumber
Reprints, at the requesting terminal, an
unanswered action request denoted by its
associated message number.

RET[YPE]A [#n[ :n]]
Several unanswered action requests can be printed
by giving the number of the sending job. If :n is
given with the job number, the n oldest (from I to
32) action requests are printed for that job.
+ - • - .' - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - . - - - - .. - - - +
,Note
Entering an account that does not have SWCFG
privilege in the OPSER operator table with the
A-12

Managing the OPSER Spooling Package
OPERATOR command allows anyone logged in to that
account access to all accounts. You must use caution
when deciding which accounts you place in the OPSER
operator table.

Message Types
OPSER displays two types of information on the Operator Services
Console (OSC): messages and action requests. Messages are simply
informative.
For example, a message might tell you that a control
file has been queued for batch processing. Action requests require an
operator to perform some action before the job continues (for example,
mounting a tape).
The MESSAGE command lets you define the level of information displayed
at the OSC.
For example:
o

MESSAGE ALL -- You want both messages and action requests
displayed at the OSC.

MESSAGE REQUESTS -- You want only action requests displayed
at the OSC. Messages are held in a table until you specify
MESSAGE ALL.

MESSAGE NONE -- You do not want any messages displayed at the
OSC. Messages and requests are held in a table until you
specify MESSAGE ALL or MESSAGE REQUESTS and then the RETYPE
command.

When OPSER starts, the default is MESSAGE ALL.
If you suspend the
display 'of messages, or messages and requests, by typing MESSAGE
REQUESTS or MESSAGE NONE, the suspended items are held in a table.
The table can hold a maximum of 32 messages or requests.
(The actual
number held depends on the length of the messages and requests.) If
OPSER receives a message or request after the table is full, the new
message or request is added to the table, and the oldest message or
request is deleted.
Thus, you should not suspend message printing for long, or you may
lose messages and requests. When you want to see messages and
requests again, type MESSAGE ALL. Then use RETYPE to print the
messages and requests currently held in the table.
If you see "Message Table Full" displayed at the OSC, it means that a
message was received, and the table was full.
Some unknown number of
old messages and requests had been lost while MESSAGE NONE or MESSAGE
REQUESTS were in effect.

A-13

Managing the OPSER Spooling Package
To help you distinguish between messages and action requests on the
OSC, output appears in distinct formats. A single TAB character
denotes message text; two TAB characters denote action request text.
Message requests have the format:
MESSAGE

nnnnn : date time JOB:NN KB:MM jobname [p,pn]
text

If the first character of the message text is a question mark (?)
character, the words FATAL MESSAGE replace MESSAGE in the
identification line.
Action requests have the format:
REQUEST

nnnnn : date time JOB:NN jobname [p,pn] rcvrid
text

In an action request, the first character of text is a CTRL/G (BEL)
that sounds a bell in the terminal to alert the operator.
Table A~2
summarizes the contents of messages and action requests.
Table A-2:

OPSER Message and Action Request Contents

+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Item I
Meaning
+ - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

nnnnn

Sequence number of message starting at 1 and incremented
by 1 during processing; use with the ANSWER command to
respond to a specific action request. After restarting
with currently existing work files, OPSER rounds the
last assigned sequence number up to the next multiple of
10. This number is the next assigned sequence number.

date

Current system date.

time

Current system time of day.

JOB:nn

Job number under which sending program is running; use
it, preceded by the number (#) sign, to refer to the job
in an INTERRUPT, DELETE, or RETYPE command.

KB:mm

The keyboard number of the job that sent the message.
The KB:mm field is displayed as DET if the job was
detached, and as KB:?? if OPSER is unable to determine
the keyboard number. Typically, the KB:?? message
appears when the job has terminated.

A-14

Managing the OPSER Spooling Package
Table A-2:

OPSER Message and Action Request Contents (Cont.)

+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Item I
Meaning
I
+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

jobname

Name of the program that an online sending job is
running; this name is printed for information purposes.
OPSER prints six question marks, ??????, in place of the
jobname if it is unable to determine the jobname.
Typically, the ?????? message appears when the job has
terminated.

[p,pn]

Project-programmer number (PPN) under which the sending
online job is running.

rcvrid

For action requests only. The message receiver
identification given to the job when it is started. The
identification can be standard (LPnSPL for the SPOOL
program or BAnSPL for the BATCH program) or can be
optional (as specified in the NAME start-up switch for
SPOOL or BATCH). Use the receiver identification with
the INTERRUPT command to refer to the spooling program.
+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
An action request is the result of a spooling job's requesting
interaction with the operator: the spooling job sends a message to
OPSER.
The spooling job performs no further processing until operator
action is taken or until the condition that generated the action
request is satisfied. OPSER broadcasts action requests on the OSC
unless the message level is set to NONE.
To respond to an action request, the
Because OPSER usually runs detached,
valid operator terminals to send the
command requires a message number to
which the operator is responding.

operator uses the ANSWER command.
an operator can run PLEASE at
response to OPSER.
The ANSWER
identify the action request to

OPSER sends the text in the ANSWER command to the spooling program and
deletes the action request.
If the response satisfies the request,
the program resumes processing.
If the response does not satisfy the
request, the spooling program still expects an appropriate response.
The operator must then send such a response by means of the INTERRUPT
command (see the section "Operator INTERRUPT Command").

A-IS

Managing the OPSER Spooling Package
Valid Operator and Online Job Lists
The LIST command displays data concerning the valid operator list or
the online job table maintained by OPSER:
o

LIST OPERATORS displays the keyboard number and PPN
combinations currently defined as valid operators.
The
OPERATOR command updates the valid operator list.
Initially,
only users with SWCFG privilege can update the valid operator
list.

LIST JOBS prints the header ONLINE JOB and then prints data
concerning online jobs in the following format:
#n [p,pn] 'rcvrid' SL=n

Table A-3 describes the items in the online job list.
Table A-3:

OPSER Online Job List

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Item
Meaning
I
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

The job number under which the online program is
running.

[p,pn]

The PPN under which the online job is running.

'rcvrid'

The message receiver logical identification used to
identify the online program in INTERRUPT commands.

SL=n

The OPSER shutdown level used when SHUTUP notifies
OPSER to terminate spooling operations in an orderly
fashion.

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
The job data listed is important to the operator.
For example,
certain OPSER commands require either a receiver identification or job
number to communicate with a spooling program.

Operator INTERRUPT Command
The INTERRUPT command sends unsolicited messages and special commands
to spooling programs. OPSER accepts any text in the INTERRUPT command
and sends it to the destination job. Only the destination job
interprets the text.
If a response to an INTERRUPT command is
generated, it is displayed on the OSC.
Tables A-6, A-12, and A-IS
summarize special text interpreted by spooling programs as commands.
A-16

Managing the OPSER Spooling Package
The INTERRUPT command allows an operator to control and to monitor
spooling programs. Each spooling program recognizes commands that can
be divided into three sets:

OPSER

Commands that have no direct effect on how the program itself
processes a request queued by a user.
Included in this set
of commands are PAUSE, CONTINUE, NOTICE, LAST, and STATUS.
They allow the operator to control the program in general and
to gain information about the program.

Commands that do have a direct effect on program operation
but are uniform for all spooling programs.
END, ABORT, and
OFFLINE represent this type of command which directly
influences the job.

Commands that are unique to the individual spooling program.
A command for forms control on a line printer is an example.

Start~p

Procedure

Use commands in the system start-up control file to start the OPSER
program.
See "System Start-Up Command File: START. COM" in Chapter 3
for information about creating a start-up control file.
This section
describes the commands you should include in that start-up file.
The following is a typical sequence of start-up file commands to start
OPSER:
$ RUN OPSER$:OPSER
LOG OPSER$:OPSER.LOGjALL
CHA KBO:
MESS ALL
OPER KB*:[1,2]
DETACH
The LOGFILE, CHANGECONSOLE, MESSAGE, OPERATOR, and DETACH commands
establish initial operating conditions for OPSER.
The LOGFILE and
MESSAGE commands set conditions normally established as defaults and
are shown for clarity. An explanation of these commands follows:
o

The LOGFILE command retains the file OPSER$:OPSER.LOG with a
message level of ALL. As a result, all messages, action
requests, OPSER information lines, and operator responses are
written to the file to provide a complete historical
reference.

The terminal on which OPSER starts is automatically defined
as the OSC.
You can change this definition by placing the
CHANGECONSOLE command in the start-up procedure. Any valid
A-17

Managing the OPSER Spooling Package
operator may also alter the assignment of the OSC. It is
most convenient to keep keyboard unit 0 as the OSC because,
regardless of the number of logins currently allowed on the
system, the operator can always use the system console
terminal to communicate with OPSER.
o

The MESSAGE command specifies that all messages, action
requests, and OPSER information lines are printed at the osc.
Normally, the operator is concerned only with action
requests. If the operator is concerned with any unanswered
action request, the RETYPE command can be issued. In
addition, the log file can be closed with the LOG command and
printed at any time to recover recorded information.

The OPERATOR command updates the valid operator list with
user [1,2] on any keyboard. Allowing the operator to
communicate from any terminal on the system gives flexibility
to those who are performing operator functions.

The DETACH command causes OPSER to detach itself from the
terminal on which it is running. At the start of
timesharing, this terminal is usually the system console
terminal (KBO:). While OPSER runs detached, it is immune
from tampering by unauthorized users. The operator can
communicate with OPSER through the PLEASE program.

OPSER Action Under Various start-Up Conditions
OPSER start-up actions depend on the way OPSER last terminated:
o

When OPSER runs after you have shut down operator services in
an orderly fashion through SHUTUP, a normal start-up
procedure occurs. When shutting down in an orderly fashion,
OPSER removes all entries from its online job table and
closes all files properly. On restarting, OPSER finds all
data valid. The online job table is empty, and entries in
the valid operator table are legal and therefore retained.

When OPSER starts after a system crash, it may find entries
in its online job table. Because OPSER starts before other
online jobs, none of the jobs in the table is active;
therefore, the program clears the entries from the table. If
any entries in the valid operator table are illegal, OPSER
clears that table and sets one valid operator entry: the
current user from any keyboard.

When OPSER starts after an unexpected termination, it may
find entries in its online job table for jobs still active on
the system. In this instance, the program sends a command to
A-18

Managing the OPSER Spooling package
each active job having an entry in the online job table.
The
command requests the job to retransmit the last me~sage it
sent to OPSER. OPSER does not wait for a response.
If any
job in the online job table does not meet OPSER's integrity
checks, OPSER removes its entry from the table (takes the job
off line) and generates an internal LIST JOBS command. OPSER
also scans the entries in the valid operator table.
If any
entry is illegal, the program removes it.
If OPSER removes
any entry, it generates an internal LIST OPERATORS command.

Queue Manager Program: QUEMAN
The queue manager program QUEMAN maintains the file of queued requests
(QUEUE.SYS in the OPSER$: account and communicates with spooling
programs to execute queued requests. Queue management involves two
modules stored in the OPSER Package Library: QUEMAN and QUMRUN. Both
modules have a protection code of <232>, and require SWCFG privilege
to run.
QUEMAN:
o

Sets initial conditions on starting

Checks initial conditions after restarting

Chains to QUMRUN

QUMRUN:
o

Executes commands

Manages the queues

For simplicity, the documentation refers only to one program, QUEMAN,
which functionally includes the two modules.
The QUEMAN program runs only if the job has SWCFG privilege and the
OPSER program is running (that is, only if the name OPSER is in the
system table of message receivers).
Starting QUEMAN is a prerequisite
to starting the spooling programs. To start QUEMAN, type the
following command while logged into the system under an account SWCFG
privilege:
RUN OPSER$:QUEMAN
QUEMAN V9 RSTS V9 TIMESHARING
STARTED AT: 01:52 PM ON 03-MAR-85
If you do not have SWCFG privilege, the system displays an error
message to indicate that you do not have access to QUEMAN.
A-19

Managing the OPSER Spooling Package
If the job· has enough privilege, the program prints its identification
line and st~rt-up lines and begins preliminary error checking.
QUEMAN tests for the presence of OPSER which must be started before
QUEMANcan run.
If OPSER is not running, QUEMAN prints an
informational message and terminates:
QUEMAN cannot run without 'OPSER' active
QUEMAN opens the files QUEUE.WRK, OPSERl.WRK, and QUEUE.SYS in the
OPSER$: account.
If QUEUE.WRK does not exist, the program prints the
following informational message and creates the file:
'QUEUE.WRK' not found - will initialize
If OPSERl.WRK does not exist, the program prints the following
informational message and terminates:
OPSERl.WRK not found --- can't run
To recover, the operator must start the OPSER program before starting
QUEMAN.
If QUEUE.SYS does not exist, the program creates and
initializes it. QUEMAN signals this action by generating the
informational message:
No queue file found -- will initialize
If QUEUE.SYS exists, QUEMAN makes sure that it has write access to the
file.
If another program has write access to the QUEUE.SYS file,
QUEMAN generates the following message:
Queue file opened by another program
Try again (YIN) <N>?
The operator must determine which job has the file QUEUE.SYS open and
must terminate that job.
If you type Y in response to the question,
QUEMAN retries the open operation.
Typing N terminates QUEMAN.
When the OPEN operation successfully gains write access to QUEUE.SYS,
QUEMAN declares itself a message receiver on the system.
If QUEMAN is
already declared by a different job, the program prints the message:
QUEMAN cannot declare itself as a receiver

can't run

The operator must terminate the other job so it is removed from the
message receiver table.
To make sure that the previous QUEMAN job closed the currently
existing QUEUE.SYS file properly, the program checks a flag value in

A-20

Managing the OPSER Spooling package
the file.
If the flag is not properly set, the program prints the
following informational message:
Queue file not closed properly

now checking data for consistency

A later informational message signals that all integrity checks were
successful:
Queue file data checked for consistency
If the flag is properly set, QUEMAN performs consistency checking but
does not print any messages unless it finds problems.
If any problems
are found, QUEMAN generates the following informational messages:
Queue file data inconsistent - will initialize
Initialized
The INITIALIZED message indicates that QUEMAN has set all entries in
the QUEUE.SYS file to their initial conditions and has removed all
queued requests from the queues.
See the section "QUEMAN Consistency
Checking" for a description of the queue file consistency checks
QUEMAN performs.
After completing all initial checks, QUEMAN prints the number sign (#)
prompt indicating its readiness to accept a start-up command or
switch.

QUEMAN Start-up Commands and Switches
Table A-4 lists the start-up commands that QUEMAN recognizes.
Table A-4:

QUEMAN start-up Commands

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command
Syntax and Meaning
I
+~ - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I

I
I
I

I
DETACH

i
I

I
I
I

INI[TIALIZE]
Sets all the entries in the QUEUE.SYS file to their
I
I initial conditions and sets initial. conditions for
I
the spooling queues. Any currently queued requests
I
I are lost.
I
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

INITIALIZE

DET[ACH]
I Detaches QUEMAN from the terminal. You should run
I QUEMAN detached.
I

A- 21

Managing the OPSER Spooling Package
Before QUEMAN executes the INITIALIZE command, it checks its online
spooler table.
If the table has an entry for a spooling job, QUEMAN
prints the following informational message:
Spoolers on line -- can't initialize
#
QUEMAN also recognizes start-up switches.
One or more switches may
appear following a command or may appear alone on a line in response
to the prompt.
Table A-5 lists the start-up switches that QUEMAN allows.
Table A-5:

QUEMAN Start-up Swi tches

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Option I
Syntax and Meaning
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I

I PRIORITY I /PRI[ORITY]:nnn
I
I Sets the job priority to nnn, where nnn can be from
I
I -120 to +120. Without the switch, the program
automatically sets the priority to O. You must have
I
TUNE privilege to specify this qualifier.
I
I
I RUNBURST
/RUN[BURST]:nnn
I
Sets the job run burst to nnn, where nnn can be from 1

to 127. Without the switch, the run burst value
currently assigned is used. You must have TUNE
privilege to specify this qualifier.
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I

If any data entered in response to the number sign prompt are not
valid commands or options, QUEMAN prints the following informational
message:
Invalid response -- text
The text is the data entered.

The program prints the # prompt again.

To detach QUEMAN, the operator types the DET command in response to
the prompt.
For example:
#DET
Detaching ...
The program then prints the DETACHING message and detaches itself from
the keyboard.
Note that you should always run QUEMAN detached.

A-22

Managing the OPSER Spooling Package
While detached, the job receives commands from the operator through
OPSER (se~ the following section). At no time should the operator
enter CTRL/C to the QUEMAN program; this may corrupt the QUEUE.SYS
file.

QUEMAN Interrupt Commands
QUEMAN recognizes interrupt commands that allow an operator, through
the INTERRUPT command of OPSER, to get information on queue manager
processing and to control program operation.
Table A-6 summarizes these interrupt commands.
Table A-6:

QUEMAN Interrupt Commands

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
1
Command
Option and Meaning
1
+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

DIS[ABLE]

QUE[UING]<text>
1
I
SPO[OLING]<text>
1
I ALL<text>
1
I Disables QUEUING or SPOOLING or both operations with
1
I
the ALL switch. When you specify DISABLE QUEUING, the
1
I
program QUE stops sending messages to QUEMAN and stops 1
listing the queue. Any jobs already sent to QUEMAN are 1
processed. If you specify DISABLE SPOOLING, QUEMAN
1
prevents any further jobs from being sent to any
I
spooler. Jobs sent to a spooler prior to the DISABLE
1
command are processed to completion. Specifying
1
DIS [ABLE] ALL tells QUEMAN to terminate both QUEUING
1
and SPOOLING. You can include a message to the user
1
while specifying the DISABLE command. Type the
1
command, the switch, and then a space followed by the
1
message. After QUEMAN processes the command, it prints "I
the <text> message in one of the following formats:
1
1

o
o
o

Further QUEUING DISABLED <text>
Further SPOOLING DISABLED <text>
Further QUEUING AND SPOOLING DISABLED <text>

1
1
1
1

If you ignore the <text> field, QUEMAN prints the
default text, "by operator." The message appears when
you try to queue a file.

A- 23

1
1
1

Managing the OPSER Spooling Package
Table A-6:

QUEMAN Interrupt Commands (Cont.)

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Command

option and Meaning

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
ENA[BLE]

QUE[UING]<text>
SPO[OLING]<text>
ALL<text>
Enables QUEUING or SPOOLING or both operations with
the ALL option. When you specify ENABLE QUEUING, the
program QUEUE begins to send messages to QUEMAN and
starts listing the queue. If you specify ENABLE
SPOOLING, QUEMAN begins to send jobs to the spoolers.
Specifying ENABLE ALL tells QUEMAN to start both the
QUEUING and SPOOLING functions. Use the <text> field
to send messages to the user. Type the command, the
switch, and then a space followed by the text of the
message. After QUEMAN processes the command, it prints
the message in one of the following formats:
o
o
o

QUEUING ENABLED - <text>
SPOOLING ENABLED - <text>
QUEUING AND SPOOLING ENABLED - <text>

The default <text> message is "by operator." The
message appears when you try to queue a file.
END

Terminates QUEMAN in an orderly manner and disables
queuing and spooling. If any spooling programs are on
line to QUEMAN, END sends to OPSER the informational
message "Spoolers still online - will clear table" and
clears the online spooler table. END then sends a
command to OPSER that takes the QUEMAN entry out of
OPSER tables. QUEMAN closes its work files and removes
its job from the system.

LAS[T]

Sends to OPSER the most recent message generated by
QUEMAN.

NEX[T]

quenam=reqnam
Places the pending user request identified by reqnam
at the head of the queue specified by quenam. A
request name can contain a job name, PPN, and sequence
number. Request names are found in the listing
generated by the QUE program command L dev:, where
dev: is the appropriate queue name. For example, LP:,
BA:, or RJ: are valid queue names.

A-24

Managing the OPSER Spooling package
Table A-6:

QUEMAN Interrupt Commands (Cont.)

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Command I
Option and Meaning
+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I OFF[LINE]
I
I
I STA[TUS]
I

I
I Terminates QUEMAN as the END command does but does not
I generate a notification message.
I
I Prints a brief report of spooling jobs on-line to
I QUEMAN.

+- - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -: - - - - - - - - - --+

When a command is received from the operator through OPSER, QUEMAN
performs the action requested and either generates a message or an
information line.
OPSER formats the message or information line and
displays it on the Osc. An example of this interaction between an
operator, QUEMAN and the OPSER program is shown using the STATUS
command.
The following example assumes the operator is running the
PLEASE program and the OSc is the keyboard on which PLEASE is running:
#/INT # 6: STATUS
COMMAND SENT TO 'OPSER'

#
MESSAGE
29 : 10-MAR-85 10:48 AM
1 SPOOLER(S) ON LINE (25) LPlSPL LP1: FORMS=NORMAL;

JOB:6 DET QUMRUN[1,2]

PLEASE passes the full command line to OPSER and notifies the operator
before it reprints the prompt. OPSER recognizes the text INT as a
request to send unsolicited text to a spooling job. The characters
"#6" in the command line are recognized as the number of the
destination job to which the text must be sent. QUEMAN receives the
text STATUS, generates a response, and sends the response back to
OPSER. OPSER formats a message and displays it on the OSC for the
operator.
The STATUS command itself is the operator's way of getting information
about jobs that are on line to QUEMAN. QUEMAN'S status printout gives
the number of spooling jobs currently on line and supplies data on
each job (job number within parentheses, receiver identification,
physical unit being spooled, and program default conditions).
If the
particular spooling job is processing a request, the data in the
printout includes the following information about the request: its
name, the PPN under which it is queued, and its sequence number. The
STATUS command also tells you if SPOOLING or QUEUING is disabled.

A- 25

Managing the OPSER Spooling Package
The NEXT command allows the operator to place a job request at the
head of a queue.
Job requests are identified by the name, account,
and sequence number under which the request is queued. A request·
moved to the head of a queue is the next one QUEMAN sends to a
spooling program servicing that queue.
See the RSTS/E utilities
Reference Manual for a description of the NEXT format in the QUE
program discussion.
If QUEMAN detects an error in the NEXT command, it generates an error
message in the format:
'NEXT' CMD: string - text
The string is the command you entered.
error texts.
Table A-7:

Table A-7 lists the possible

NEXT Command Error Text

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Text
Meaning
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

ILLEGAL PARAMETERS

Only a queue name and request name,
separated by an equal (=)sign, are
allowed in the NEXT command.

ILLEGAL SYNTAX

A space or an = character is missing.

JOB IN PROCESS

The specified job request has already
been sent to the spooling program.

MULTIPLE JOB SPECIFIED

The specified request name matches two or
more jobs in the queue.

NO MATCH FOR JOB

The request name does not match any job
in queue.
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

QUEMAN start-up Procedure
You should place commands in the system start-up command file to start
the QUEMAN program.
See "Creating and Using Command Files" in Chapter
3 for information about creating a start-up command file.
The following are typical commands to start QUEMAN:
$ RUN OPSER$:QUEMAN
/PRIORITY:O/RUNBURST=6
DETACH
A-26

Managing the OPSER Spooling Package
The priority is set to zero because most jobs on RSTS/E run at
priority minus eight and QUEMAN, running at priority zero, can more
readily process the queue file.
Include the DET command to make
QUEMAN run detached on your RSTS/E system.
Note
without the PRIORITY switch, QUEMAN automatically
sets its priority to zero.
You can explicitly
specify the switch to provide a record of what the
program does automatically.
Because QUEMAN examines the QUEUE.SYS file when it starts, there is no
need explicitly to initialize the file.
If the file contains bad
data, QUEMAN resets all entries to initial states. Therefore, you
should specify the INI command only in situations in which you want to
explicitly initialize the queue file.

QUEMAN Action Under Various Start-up Conditions
QUEMAN start-up actions depend on the way QUEMAN last terminated:
o

When QUEMAN runs after you shut down operator services in an
orderly fashion through SHUTUP, a normal start-up procedure
occurs. QUEMAN finds that the QUEUE.SYS file was closed
properly.
The program performs consistency checking but does
not print any messages unless it finds problems.
If the data
is consistent, QUEMAN retains all job requests in the queue
file and examines each request for completeness and status.
Because QUEMAN normally starts before any spooling programs,
there are no entries in the online spooler table.
QUEMAN
checks to see that this table is clear of entries.

When QUEMAN starts either after the system crashes or after
QUEMAN itself terminates unexpectedly, it finds the queue
file improperly closed and generates a message to that
effect.
The program performs consistency checking on the
queue file structure and on the data in the QUEUE.SYS file
itself, generates messages telling the results, and
reestablishes communication with all spooling jobs.

QUEMAN Consistency Checking
The QUEUE.SYS file has room for 250 queued requests.
QUEMAN creates
an entry for a queued request from an entry in a free list. A request
for a line printer or batch queue requires one entry from the free

A-27

Managing the OPSER Spooling Package
list. A request queued· with an AFTER date and time, however, requires
two entries from the free list -- one for the proper queue and one for
the AFTER queue.
In performing consistency checking on the QUEUE.SYS file, QUEMAN
initializes all entries if it finds one of the following conditions:
o

An entry in the free list is also in a queue or AFTER list

The root of the free list is outside the legal range

A request queued with an AFTER date and time that has not
expired does not have an entry in the AFTER queue

For other inconsistencies, QUEMAN either may remove a single entry or
perform some related action.
If an entry in the AFTER queue has no
corresponding entry in a spooling queue, QUEMAN removes the AFTER
entry.
If an entry in either an AFTER or spooling queue is not
completely set up, the program removes the entry.
(QUEMAN may have
terminated while it was processing the request.) To signal this event,
QUEMAN generates a message in the format:
%LPn:

'reqnam'

[p,pn]iQUEUED JOB INCOMPLETE - REMOVED FROM QUEUE

If an entry to be killed still remains, QUEMAN removes it and
generates a message in the format:
%LPn: 'reqnam'
QUEUE

[p,pn]iQUEUED JOB IN 'KILL' STATUS - REMOVED FROM

If QUEMAN finds that an entry has been processed (sent to a spooling
program) but not yet completed, it places the request in a hold status
and generates text in the format:
%LPn: 'reqnam' [p,pn]iJOB PREVIOUSLY SENT TO SPOOLERi
WILL BE PUT INTO HOLD STATUS
The requester can remove the job request from hold status.
QUEMAN checks the online spooler table in the QUEUE.WRK file for
consistency.
If the program finds the table empty, it generates the
informational message:

# SPOOLERS ON LINE = 0; WILL CLEAR TABLE
1£ the program finds that the count of online spooling jobs is larger
than the limit (16), it clears the table and generates the
informational message:
ONLINE SPOOLER TABLE CORRUPT - WILL CLEAR TABLE

A-28

Managing the OPSER Spooling package
If QUEMAN clears the online spooler table but spooling jobs are still
running, the operator must terminate those jobs through OPSER and
restart each spooling program.
This action allows QUEMAN to put each
spooling job on line again properly.
For each spooling program found in the online job table, QUEMAN
removes the entry and generates the informational message:
'rcvrid' (nn) FOUND ON LINE TAKEN OFF LINE
QUEMAN sends the job a message requesting that it declare itself on
line to QUEMAN again.
The spooling job does not respond to the
message while it is processing a queued request.
The answering
message indicating that the job is again on line to QUEMAN does not
appear until the job completes the current request. When QUEMAN
receives the online declaration from a spooling job, it generates the
informational message:
'rcvrid'

(nn) PUT ONLINE

Line Printer Spooling Program: SPOOL
The line printer spooling program SPOOL runs without operator
intervention and executes queued requests to transfer disk files to a
line printer or terminal.
The program consists of three modules:
o

SPOOL -- Establishes initial conditions on start-up and
checks initial conditions upon restart

SPLIDL

Executes when no job is being printed

SPLRUN

Prints any spooled file

Each module is stored in the OPSER package account OPSER$:, has a
protection code of <232>, and requires SWCFG privilege to run.
For
simplicity, this appendix refers only to one program, SPOOL, which
functionally includes the three modules.
The SPOOL program runs only if the user has SWCFG privilege and the
OPSER and QUEMAN programs are running.
To start SPOOL, type the
following command while logged in to the system under an account with
SWCFG privilege:
$ RUN OPSER$:SPOOL
SPOOL V9 RSTS V9 TIMESHARING
#
Typically, this is done in the system start-up file.

A-29

Managing the OPSER Spooling Package
At this point, the SPOOL program performs a number of preliminary
checks before it prints the number sign (#) prompt. The remaining
portion of this section describes these initial program checks. Once
you are familiar with this procedure, you can then learn the options
SPOOL accepts in response at its program prompt. A description of
these SPOOL program checks follows.
If you do not have SWCFG privilege, the system displays an error
message to indicate that you do not have access to SPOOL.
If the job has SWCFG privilege, SPOOL runs and prints its
identification line and the # prompt.
In response to the prompt, give
a specification in the following format:
# logical device:/start-up switch(es)

The logical device is the name of the queue and the unit number within
that queue from which this copy of SPOOL takes job requests to
execute.
This name ordinarily corresponds to the physical device on
which SPOOL prints the requests; the physical device, however, may be
changed by the PHYSICAL start-up option (see the following section
"SPOOL Start-up Options").
The logical device name must have the form LPn: or LP:, where n is a
unit number from 0 to 7.
If the name is LPn:, the spooling job prints
only requests queued either to that explicit unit or to the general
spooling queue LP:.
If you specify LP:, this copy of SPOOL prints
requests in the printer queue regardless of the unit to which they
were originally queued.
The logical device specified as the queue
name must be a line printer; the device name given must not have a
logical assignment to some other device.
Note
The general spooling queue LP: is useful only on
systems having line printers with similar
characteristics.
You can use any combination of the start-up switches described in the
following section to condition the operation of the SPOOL program. A
switch is formed by a slash (/) character and an option that may take
an operand or other switches.

A- 30

Managing the OPSER Spooling Package
SPOOL Start-up Options
start-up options alter default processing conditions.
options to:
0

Spool output to a different physical device

Change form information

Control job environment

You use these

Table A- 8 summarizes these options. Note that the symbol
underline character and not a space.

Table A-a:

(-)

is an

SPOOL Start-up Options

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Option
Syntax and Meaning
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ASSIGN
I
I
I
FORM

/ASS[IGN]
Reserves the physical device for this job. Without this
option, SPOOL retries continually whenever it cannot
gain access to the unit and is ready to print a job.
/FOR[M]:name switch
Defines the current form according to a name (NORMAL is
the default name) and switches as follows:
/ALI[GN]
Causes SPOOL to execute a forms alignment
procedure before processing any further queued
requests.
/DFL[ENGTH]:nnn
Declares the device form length as nnn lines,
where nnn is a number from 1 to 127. The length is
that understood by the hardware of the output
device. For example, on a line printer in the
United States, the standard length is usually 66
lines per page.
/HEA[DINGS]:n
Causes SPOOL to print n (from 0 to 3) heading
burst pages preceding each job request. Unless /NH
accompanies a file specification in the QUE
command, SPOOL also prints n burst pages preceding
each file in a job request. The default value is
1.

A- 31

Managing the OPSER Spooling Package
Table ~8:

SPOOL Start-up Options (Cont.)

+ - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I Option I
Syntax and Meaning
I
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
FORM
(Cant. )

/LEN[ GTH] : n
Defines the length of software form as n lines per
page, where n is a number from 1 to 127. If this
switch is not given, SPOOL assumes 66 lines per
page.
/PAG[E EJECT]:YES
Indicates that the device to which this copy of
SPOOL directs output has a hardware top of form
capability and that the device interprets the
formfeed character (ASCII 12) as a top-of-form
command. This condition is the default case for
line printer devices.
/PAG[E EJECT]:NO
Conditions the software to translate a formfeed
character (ASCII 12) into the proper number of
linefeed characters because the hardware does not
recognize the character as a top-of-form command.
This condition is the default case for SPOOL
output directed to terminal devices by the
PHYSICAL option.
/WID[ TH] : n
Defines the width of the heading burst page as n
characters per line. The default value is 132.

LPFORM

/LPF[ORM]:YES
Indicates that LPFORM characters are interpreted by the
system software for the output device. During normal
transfer, the program passes LPFORM characters
unmodified to the device. This condition is the default
for line printer devices.
/LPF[ORM] :NO
Indicates that the system software does not interpret
LPFORM characters. During normal transfer, the program
converts each LPFORM character to an appropriate number
of line feed characters. This condition is the default
for terminal devices.
Note that this option affects only jobs queued with the
/LPFORM switch. The SPOOL program does not
automatically invoke /LPFORM processing.

A- 32

Managing the OPSER Spooling Package
Table A-a:

SPOOL

Start~p

Options (Cont.)

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Option

Syntax and Meaning

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I NAME
I
I
I
I
I
I
I
I PHYSICAL
I
I

PRIORITY

/NAM[E]:rcvrid
places the specified identification in the system
message receiver table and in OPSER's online job table.
This identification rather than the default
identification is used by the operator in OPSER
commands to access this spooling job. This
identification must not be in use by some other job.
/PHY[SICAL]:dev:
Uses this device as the physical device for this
spooling program. Requests in the queue specified by
the logical device are printed on this device. The
default value is the logical device specified as the
queue name.
/PRI[ORITY]:nnn
Sets the job priority to nnn, where nnn is a number
from -120 to 120. Without this option, the priority
remains as set by LOGIN. You must have TUNE privilege
to specify this qualifier.
Do not use /PRIORITY after a/FORM, /NAME, or /PHYSICAL
option, or after an LPn: designator.

RUNBURST

/RUN[BURST]:nnn
Sets the job run burst to nnn, where nnn is a number
from 1 to 127. Without this option, the run burst
remains as set by LOGIN. You must have TUNE privilege
to specify this qualifier.
+ - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -. - - - - - - - - - - - - - - - - - +
The PHYSICAL option alters the physical device on which queued
requests are printed.
For example, requests queued for line printer
unit I could be processed on another line printer unit or on a
keyboard unit.
In any event, the actual device differs from the one
for which the requests were queued.
The ASSIGN option reserves the actual spooled device to the job.
Without this option, SPOOL periodically tries to gain access to the
spooled device whenever SPOOL is ready to print and another job has
ownership of the device. When SPOOL terminates, it deassigns the
device.
The NAME option allows the receiver identification to be different
from that normally assigned by SPOOL.
The identification should be
from one- to six-alphanumeric characters and must not exist in the
A- 33

Managing the OPSER Spooling Package
system message receiver table. The identification must not begin with
a number because the operator uses either this identification or a job
number to identify a spooling job.
The FORM option allows the default form information to be altered.
For example, individual characteristics of the NORMAL form can be
altered, a new form with a different name can be defined, or a forms
alignment can be requested. A forms alignment can be r~quested by
itself or in conjunction with a form alteration. When a form name
other than NORMAL is in effect, user's queuing requests must
explicitly specify the form name to.have files printed with its
characteristics.
To alter the default characteristics of the NORMAL form, the operator
can specify the appropriate auxiliary switches without the /FORM:
switch.
For example, to change the number and width of heading burst
pages for line printer unit 0, type:
LPO:/HEADINGS:2/WIDTH:80
When executed, this command causes SPOOL to output two heading burst
pages with a width of 80 characters per line print for each job
request and each file within a request.
The width used applies only
to the burst pages, not to the data being printed.
Specifying a form with a name other than NORMAL usually means that the
operator must load special paper in the output device. The /ALIGN
switch with the FORM option requests a forms alignment.
The operator
then must align the form at system start-up time. A SPOOL interrupt
command with the /ALIGN switch can request a form alignment during
timesharing.
The section "Changing and Aligning Forms" describes the
forms alignment procedure.
The following message can occur when the line printer queues are
~mpty, but jobs with nondefault form names exist:
NO JOBS WAITING WITH FORMNAME 'XXXXXX' FOR SPOOLER 'LPn:'
OTHER JOB(S) WAITING.
***PLEASE INSPECT QUEUE AND TAKE APPROPRIATE ACTION***
The operator must then decide whether or not to use an interruption
command to change the form name so the other jobs can be queued.
The PAGE EJECT option determines whether the SPOOL program counts
lines to-effect forms control.
(The DFLENGTH option can modify the
effect of the PAGE_EJECT option.) A value of NO with the PAGE_EJECT
option indicates that the output device (driver) does not understand a
formfeed character; that is, a formfeed character does not cause the
device to position itself at top of the (paper) form. with NO in
effect, SPOOL counts lines to effect forms control. A response of YES
with the PAGE_EJECT option indicates that the device (hardware)
translates the formfeed character to an appropriate number of line
A-34

Managing the OPSER Spooling Package
skips to place the device at top of form. With YES in effect, SPOOL
need not count lines and may be able to pass all forms control data
unaltered to the device driver.
(The DFLENGTH option can modify the
effect of YES.)
Note
SPOOL issues three forms-control characters:
o

Form feed character (ASCII 12)

Carriage return character (ASCII 13)

Line .feed character (ASCII 10)

No other forms-control characters are used.
SPOOL
has no provisions for changing or extending the set
of control characters for any special device(s).
The terms line feed and line skip are not synonymous.
Line feed refers only to the linefeed character,
which either SPOOL or the device driver sends to a
device.
Line skip refers to the movement of paper
that the device itself effects.
If NO is in effect for the PAGE_EJECT option, SPOOL ignores any value
specified in a DFLENGTH option.
The operator should specify
/PAGE_EJECT:YES for any terminal device that has a top-of-form
capability.
SPOOL uses the value specified in the DFLENGTH option only if
/PAGE EJECT:YES is in effect.
The /PAGE EJECT:YES switch can be in
effect either through default (on a line-printer) or by explicit
specification (for a terminal device having the form feed capability).
The operator may specify the DFLENGTH option either at start-up time
in a SPOOL start-up switch or during processing in a FORM interrupt
command.
For proper formatting, the DFLENGTH value must be the
maximum number of lines that the output device skips when it receives
a formfeed command.
The number of lines is called the device form
length. This number may differ from the length of the paper form
being used.
Different devices have different form lengths.
show how the device form lengths vary:
o

Three examples can

The LA1BO device has a switch labeled "Length of Form," which
has settings for 4, B.5, and 11 inches.
These settings
correspond to 24, 51, and 66 lines per form.
(The number of
lines per form given for each setting assumes the standard 6
lines per inch on the LAlBO.) If, when starting the spooling
job, the operator sets the switch on the LAIBO to B.5 inches,
the operator should also specify the DFLENGTH switch with a
A- 35

Managing the OPSER Spooling Package
value of 51.
If, at some later time, the operator changes
the setting on the LA180 to 4 inches, the operator should
also specify a new.DFLENGTH option with a value of 24 in a
FORM interrupt command to the spooling job.
o

Many line printers have only one form length.
If the
hardware length is 66, the value in the DFLENGTH switch
should be 66.
If the hardware form length is 51, the
operator should specify DFLENGTH=51 when starting the
spooling job.
(The default value for DFLENGTH is 66.)

Some printing devices have an adjustable top-of-form. On
these devices, the operator can adjust the device to execute
an arbitrary number of line skips when it receives a formfeed
character. This adjustment is made most often on
terminal-type devices with high quality print
characteristics. When resetting the top-of-form for this
type of device, the operator should also specify the DFLENGTH
and LENGTH options with the new form length information.
The
operator should also request a forms alignment for each new
form.

The effect of the DFLENGTH option on the SPOOL program differs for
line printers and terminal devices:
o

For a line printer, the DFLENGTH value affects only the
procedure SPOOL invokes when it receives an ABORT command
while it is processing a job request.
If the DFLENGTH value
equals the current length of paper form, the program issues a
formfeed character to position the device at the top of the
next form.
If the values are not equal, the program
automatically invokes the forms alignment procedure to
reestablish the top-of-form position . .
The automatic forms alignment procedure requires operator
action to align the form and to respond to requests SPOOL
makes.
This is necessary only when the program has no way to
determine where the top-of-form lies after an ABORT
operation.

For a terminal, the DFLENGTH value controls the way SPOOL
keeps its place on a form and the way the operator handles
recovery procedures.
If the value of the PAGE_EJECT option
is YES, the equality of the device form length and the paper
form length is important.
If the device form length and
paper form length values are not equal, the SPOOL program
counts lines to maintain a record of its position on a form
and issues an appropriate number of linefeed characters to
simulate form feed.
If these values are equal, SPOOL does
not count lines and simply sends a formfeed character to
position the paper at top-of-form.

A-36

Managing the OPSER Spooling Package
Note
A line printer is a device whose interface to the
computer is through a line printer controller and
whose designation is in the form LPn:. A terminal is
a device whose interface to the computer is through a
keyboard line and whose designation is in the form
KBn:.
This distinction is critical because some
devices such as the LAIBO are called printers but may
be connected to the computer through a keyboard line.
If the value in effect for DFLENGTH does not correctly match the
setting of the hardware device, two undesirable conditions exist:
o

SPOOL must incur the overhead of counting lines.

Forms alignment may be lost during processing.

For these reasons, DIGITAL highly recommends that the operator supply
a new value of DFLENGTH when changing the hardware setting on the
device.

Line Printer Spooling
If the physical device specified at start-up time is a line printer
unit, SPOOL applies the default values.
Table A-9 lists these default
values.
Table A-9:

SPOOL Line Printer Default Values

+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
I
Result
+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I /DFLENGTH:66
I
I
I
I
1

I /FORM:NORMAL
I
/HEADINGS:l
I
/LENGTH:66
I
/WIDTH:l32

I
I The device form length is 66 unless otherwise
I specified. If you have patched the monitor to
I apply a different default form length, you must
I always specify the correct value in a DFLENGTH
I option.
I

I The values shown are used as the form
I definition.
I
I

A- 37

I
I
I
I
I.
I
I

I
I
I
I

Managing the OPSER Spooling Package
Table A-9:

SPOOL Line Printer Default Values (Cont.)

+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
I
Result
I
+ - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I /LPFORM:YES
I
I
I
I

For any line printer, SPOOL assumes that the
device driver properly processes the special
LPFORM characters (see the RSTS/E Programming
Manual) •

/PAGE_EJECT:YES

I
I
I
I
I
I
I
I

For any line printer, SPOOL assumes that the
device driver properly processes top of form
characters.
I
+ - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
You can also set the characteristics of a line printer with the SET
PRINTER command (see Chapter 11).

Keyboard Spooling
If the physical device specified at start-up is a keyboard device,
SPOOL applies the default values.
Table A-IO lists these default
values.
Table A-lO:

SPOOL Keyboard Default Values

+- - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
Result
I
+ - - - - - - • - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - •• - - - . - - - . - - - - - '. - - - - - - - - • +

I
I /DFLENGTH:66
I
I
I /FORM:NORMAL
/HEADINGS:l
I
/LENGTH:66
I
/WIDTH:132
I
I
I /LPFORM:NO
I
I
I
I
I /PAGE __ EJECT:NO
I
I
I

DFLENGTH has no effect unless PAGE EJECT is
explicitly specified as YES.
The values shown are used as the form
definition.

The terminal driver does not process LPFORM
characters. For any file that contains LPFORM
characters, SPOOL simulates the LPFORM effect by
issuing linefeed characters.

Most terminals do not have a hardware
top-of-form capability. SPOOL simulates
top-of-form by issuing the correct number of
linefeed characters.
+- - - - - - - -. - - - - - _. -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _. - - - --+
A- 38

Managing the OPSER Spooling Package
For terminals with the hardware top-of-form capability:
o

Set the value of PAGE EJECT to YES.

Set the value for DFLENGTH to the actual device form length
(see "SPOOL Start-up Options").

Set the proper characteristic of the device that accepts and
processes a form feed.
Use the SET TERMINAL command to
perform this operation (see Chapter 8).

Start~p

Error processing

If you make an error when responding to the number sign (#) prompt,
SPOOL prints a message and the unparsed command line in the format:
?ERROR MESSAGE
unparsed command line
The unparsed command line is the right-hand part of the response
beginning at the element causing the error. Table A-II summarizes the
possible messages.
Table A-II:

SPOOL Syntax Error Messages

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
?Can't parse remaining string
Something illegal or undefined was found in the command
line. An undefined switch or missing slash (/) character
causes this error.
?Duplicate switch
Two occurrences of the same switch were found in the command
line.
?Illegal logical device
The logical device specified was not in the form LP: or LPn:
(where n is a number from 0 to 7).

A- 39

Managing the OPSER Spooling Package
Table A-II:

SPOOL Syntax Error Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - -;;.~: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- --+
?Illegal operand
An illegal operand was found in an option or switch. For
example, specifying nonnumeric characters in a switch that
requires a number (/WIDTH:n) generates this error.
?Illegal physical device
The device specified in the PHYSICAL option is not a line
printer or keyboard device.
?Missing operand
A switch requiring an operand was specified without one. For
example, if a receiver identification is missing from the
NAME option, this error is generated.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

If SPOOL encounters no syntax errors in the response, it begins
setting initial conditions. SPOOL reports errors in this phase by
printing a message in the format:
ERROR IN SOME OPERATION
error message

RESTARTING

The program reprints its identification line and the prompt.
An error message ?Duplicate receiver ID means that the receiver
identification, either the default one or the one specified in a NAME
option, is already defined for another job. The operator should type
the command line again and specify a unique receiver identification in
the NAME option.
The error message ?No room in receiver table means that a general
small buffer is not available to let SPOOL declare itself a receiving
job. A later retry with the same command line should succeed.
The following message means that SPOOL attempted to send a message to
that program and failed:
*****OPSER HUNG***** or *****QUEMAN HUNG*****
Either the named program does not have an entry in the system message
receiver table or the program is not processing its messages and its
message limit has been reached. The operator must determine the cause
of the problem and restart the named program.
A- 40

Managing the OPSER Spooling Package
SPOOL Interrupt Commands
The operator communicates with a SPOOL job by means of INTERRUPT
commands sent through the operator services: program OPSER. Note that
any responses to an INTERRUPT command are displayed on the Operator
Services Console.
Table A-12 summarizes these SPOOL interrupt commands. Note that the
circumflex (~) character marks the location of a required space.
Table A-12:

SPOOL Interrupt Commands

+ - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -"- - - - - - - - - - - - - - - - +
I
Command Syntax
I
Meaning
I
+ - - -"- - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

ABO[RT]

Immediately terminates the current process
and removes the request from the queue.

CON[TINUE]

Wakes up the spooling job to continue
processing after a PAUSE command.

END

Closes out processing after completing the
current request. The operator must then run
the spooling program again to process further
requests.

FOR[M]~name/switch

Changes the current output form to one
identified by name and defined by switches.
These switches change current form
characteristics; those characteristics not
changed by an option remain at their current
definitions. See the start-up option FORM
description in Table A-8 for the allowable
options. Alignment is done only if the /ALIGN
switch is included.

FOR[M]

Displays characteristics of the current form
if no name or options are in the command.

FOR[M]~ /ALIGN

Requests a forms alignment procedure for the
current form.

LAS[T]

Prints the most recent message generated by
the spooling job.

OFF[LINE]

Immediately terminates all processing by this
spooling job (same as ABORT followed by END).

A- 41

Managing the OPSER Spooling Package
Table A-12:

SPOOL Interrupt Commands (Cont.)

+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Command Syntax
Meaning
I
+- - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I PAU[SE]

I
I places the spooling job in a sleep state,
during which it responds to most commands and
resumes normal processing in response to a
CONTINUE command.*

REQ[UE]

stops processing the current request and
replaces the request in the queue so that
processing later resumes at the terminating
point.

RES [TART]

Reprints the current copy of a file from the
beginning, including heading burst pages.

RES[TART]" JOB

Reprints the current iteration of the job,
including heading burst pages.

RES[TART]" :n

Reprints the current copy of the file
starting at page n. If n is 0, restarts from
the beginning of the file but omits the
heading burst pages.

STA[TUS]

Prints a status report for the spooling job.

* Note that processing continues if any job modification command
such as ABORT or REQUE is sent.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

SPOOL Start-up Examples
This section shows four examples of the start-up procedure.
represent typical cases.

Line Printer Start-up with All Defaults
In response to the SPOOL program prompt, the operator types:
#LPO:

If SPOOL finds no errors, it prints the message:
DETACHING ...

A-42

They

Managing the OPSER Spooling Package
SPOOL detaches itself and leaves the terminal logged off the system.
The following are the characteristics of this copy of SPOOL:
o

The program prints only job requests that were queued to line
printer unit 0 with a form name of NORMAL or queued to the
general line printer queue with a form name of NORMAL.

The program prints on line printer unit O.

The program prints one heading burst page before each job
and, unless a file is queued with /NH, prints one heading
burst page before each file. The width of the burst page is
132 columns, and the form length is 66 lines.

The program assumes the device driver handles LPFORM
characters.

The program assumes the device handles top-of-form.

The program assumes the device form length is 66 lines.

The run burst and priority of SPOOL are those in effect when
the job starts.

When the program receives a job from QUEMAN, it attempts to
assign the printer. If the assignment fails, the program
retries periodically until it succeeds. When it finishes
processing a job request, the program deassigns the device.

The operator may later change all form characteristics (name, length,
width, device form length, and headings count) through appropriate
interrupt commands.

Line Printer Start-up with Narrow Width
In response to the prompt, the operator types the command line:
#LPl:/FORM:NARROW/WIDTH:80/RUNBURST:12/ASSIGN
The following are characteristics of this copy of SPOOL:
o

The program prints only jobs queued with a form name of
NARROW and queued to either unit 1 or the general line
printer queue.

The program prints on the line printer 1 device.

The program prints one heading page of width 80 columns; form
length is 66.
A-43

Managing the OPSER Spooling Package
0

The program assumes the device handles top-of-form.

The program assumes the device driver handles LPFORM
characters.

The program assumes the device form length is 66.

The priority of the job remains unchanged.
the run burst to 12.

The program does not begin spooling until it can assign line
printer unit 1 and does not deassign the device until it
terminates.

The program sets

In this example, assume that line printer unit 1 is a relatively slow
device and that the SPOOL program can generate output data for this
unit faster than the device can print. Optimal use of the device
results if the unit keeps running at full speed for the entire job
request it is printing.
To effect optimal use, it is sometimes necessary to raise either the
priority or run burst of the SPOOL program. The priority of. a job
generally affects how often it runs, whereas the run burst affects the
length of time the job runs once it starts running. Because the SPOOL
program is usually I/O bound and waiting for the device to complete
printing, there is little reason for it to' run more often. Changing
the priority is usually unnecessary and ineffective. Changing the run
burst, however, may improve processing.
When SPOOL starts executing, it remains in the run state until one of
the following events occurs:
o

The job's run burst expires. That is, the job actually
executes for its full run burst.

The job requests some type of I/O and the system cannot
immediately satisfy the request.

For the spooling program, the second event is much more likely because
the system buffers only a fixed amount of data before it refuses to
satisfy further requests for output. When the refusal occurs, the
system activates another job and the spooler must wait until the
system sends at least some of the already buffered data to the output
device.
(This wait condition shows as an LP or TT STATE on a SYSTAT
listing.)
As long as the buffers for the device are never completely emptied,
the system keeps the device running at or near full speed. To a
certain point, raising the spooling job's run burst makes it more
likely that the job will continue running until it completely fills
the buffers for its output device. After a certain point, raising the
run burst has little benefit because the job can run only until the
A-44

Managing the OPSER Spooling Package
buffers are full. Conversely, decreasing the run burst causes the
system to deactivate the program before the buffers are full. It is
more likely that the printer can empty the buffers before the system
reactivates the job.
If a spooling job spends a significant time in the RN state while it
is actually printing, the run burst is too low. DIGITAL recommends
that you raise the run burst to a value at which the job spends most
of its time in an output wait state.

Keyboard Start-up on an LA36
For this example, assume that keyboard unit 5 is an LA36 terminal.
the prompt, the operator types a command line as follows:

# LP2 :/PHYSICAL: KB5 :/HEADINGS: O/ASSIGN

The following are the characteristics of this copy of SPOOL:
o

The program prints only jobs queued with a form name of
NORMAL and queued to the unit 2 or the general line printer
queue.

The program prints on keyboard unit 5.

The program prints no heading burst pages.
is 66.

The program assumes that keyboard unit 5 does not handle
top-of-form; therefore, it counts lines as it prints them to
simulate top-of-form.

The program assumes the device driver does not handle LPFORM
characters; therefore, it simulates LPFORM with line feeds.

The run burst and priority remain unchanged.

The program assigns keyboard unit 5 at start-up and keeps it
assigned until it terminates.

The form length

Because the LA36 is a slow device, processing is not slowed any
further with burst pages. The /HEADINGS:O switch suppresses printing
of burst pages.
To retain any forms alignment on the LA36, the device is permanently
assigned to the spooling job. This assignment prevents any other job
from using the device and leaving the carriage at a position other
than the top of form position. When the spooler starts processing a
request, it must assume the device is at its top of form position
A- 45

Managing the OPSER Spooling Package
because the program has no way to force the device to advance to some
known position.
If the form is not aligned properly when SPOOL starts
the output, the entire output is misaligned.

Keyboard Start-up on an LA180
For this example, keyboard unit 2 is a serial LAIBO DECprinter.
This
terminal has a hardware top-of-form capability.
In addition, the form
length selector switch on the terminal is set to B.5 inches (51 lines
per form) and the paper form is also 51 lines per page.
In response to the prompt, the operator types a command line as
follows:
#LP3:/PHYSICAL:KB2:/PAGE_EJECT:YES/DFLENGTH:51/LENGTH:51MORE>
/WIDTH:40/FORM:SPECIAL
The following are the characteristics of the SPOOL copy:
o

The program prints only requests queued with a form name of
SPECIAL and queued to either the unit 3 or the general line
printer queue.

The program prints on keyboard unit 2.

The program prints one heading page that is 40 columns wide
and 51 lines in length.

The program assumes the device handles top of form.

The program assumes that the device driver does not handle
LPFORM characters.
The program therefore simulates LPFORM
with line feeds.

The run burst and priority remain unchanged.

The program assigns the keyboard before it prints each
request and deassigns it after printing the request.

Because:
o

The LAIBO is a much faster device than the LA36, SPOOL can
print a small number of burst pages to simplify
distinguishing jobs and files.
The narrowest width for the
burst page is 40 columns.

A-46

Managing the OPSER Spooling Package
o

The paper form length and the device form length are equal,
SPOOL can position the device to top-of-form by issuing a
formfeed character.

The program can position to top-of-form, it does not need to
keep the unit assigned.

The ASSIGN option, therefore, does not appear in the example.
If the
paper form length did not equal the hardware setting, however, SPOOL
should keep the device assigned to preserve the top-of-form position.

Recovery from Line Printer Errors
The interaction between the spooling job and the OPSER program
controls error handling in the SPOOL program.
For example, if the
paper runs out or jams, SPOOL receives the error message:
?Device hung or write locked
SPOOL discontinues processing and sends OPSER a message.
generates a message for the operator:

OPSER

MESSAGE

3 : 28-MAR-85 04:33 PM JOB:21 DET SPLRUN[I,IOO]
LPO
: HUNG
JOB: [220,40]USERI
(PUT DEVICE ONLINE TO CONTINUE)

The message tells the operator that the spooling job for line printer
unit 0 has a problem and that the device needs to be made ready again
before processing can continue.
For a SPOOL program servicing a line printer, there are certain errors
from which you can easily recover.
The device handler for the line
printer tests the ready status of an offline unit every 10 seconds.
If the operator corrects the error (for example, fixes a paper jam)
and puts the line printer on line again, the software detects the
ready status and continues printing buffered characters. The SPOOL
program finds that the error condition is cleared and continues
processing.
If a special form is being processed and SPOOL receives an error,
SPOOL may request the operator to realign the forms before it
continues processing on its own.
If the operator cannot correct the error or wants to perform some
other operation, the spooled device may be left off line. This
prevents the software from reprinting before the program processes an
operator request.
The operator uses the INTERRUPT command with the
proper text to access the spooling job~

A-47

Managing the OPSER Spooling Package
SPOOL allows the operator several ways to control the restart of a
queued request.
The RESTART command can restart:
o

The current copy of a queued request (RESTART JOB)

The current copy of a file in a queued request (RESTART)

The current copy of a file at a specific page (RESTART:nnn)

The REQUE command can reenter the current job in the queue for later
processing. On receiving a RESTART command, the program waits for any
currently buffered data to be printed before actually restarting.
The REQUE command causes SPOOL to remember the point at which
processing was interrupted. After resuming the requeued request,
SPOOL scans for the page on which processing terminated and continues
printing at the start of that page. An error may occur·if a user
modifies the requeued request before SPOOL can resume the printing.
If the operator responds to an error condition with an ABORT command,
which terminates the job, SPOOL clears the output buffers on the line
printer unit.
If the device is a terminal, SPOOL prints any buffered
data.
The program then issues a message to show that it is
terminating.
Before terminating a queued request, the SPOOL program make sure that
all buffers have been emptied successfully.

Line Printer Output
SPOOL generates job header and file header burst pages to identify
print requests and files within a print request.
Both types of header
page contain identification and general accounting information as
follows:
o

The identification consists of large, easily readable block
letters created from the character generation file CHARS.QUE.
The job identification contains the account number of the
user requesting the job and the name of the job.
If no job
name appeared in the QUE command, SPOOL prints the name of
the first file in the request as the job name.
The file
identification shows the file name and type.

A-48

Managing the OPSER Spooling Package
o

General accounting information for the job header is on the
burst page and is offset from the identification by two rows
of special characters.
The accounting information contains
five lines of data:
The first line gives the job name, current date, current
time of day, and the requester's account number.
The second line gives the date and time of day of the
request and the device for which the request was queued.
The third line gives the system name.
The fourth line gives the QUE options used to process the
request.
The fifth line gives the job copy number.
The accounting information for the file header burst page
appears below the identification and is framed (above and
below) by two rows of special characters.
The first line of
information gives the job name used when SPOOL printed the
file and shows the current date, time of day, and account as
the job header burst page does.
The second line gives the
copy number, the QUE options used on the file, and the
complete specification of the file.
The third line gives the
record type and carriage control format used to print the
file.

If SPOOL does not print the file because of an error, file header'
identification and accounting information is replaced by an error
message framed (above and below) by five rows of special characters.
The error message is standard RSTS/E error text.

Error Messages During User Output
SPOOL reports errors it receives during printing in the line printer
output.
SPOOL differentiates the error message from requested output
by framing the text (above and below) with five rows of special
characters.
Table A-l3 shows the possible SPOOL error messages and related
meanings.

A-49

Managing the OPSER Spooling Package
Table A-13:

SPOOL User Requested Output Error Messages

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - +

Message and Meaning

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

?Can't find file or account
The related file was deleted between the time it was queued
and the time SPOOL tried to print it.
?File restart requested on page n
The operator requested a restart at the indicated page or
placed the job request back in the queue with the REQUE
command. If the operator restarted the job request, SPOOL
scans the file to find the correct page and continues
printing on a new page following the message. If the
operator requeued the job, this message appears when SPOOL
restarts the job.
?Job aborted
Either the operator terminated the job request with an ABORT
command or the K command of the QUE program was issued while
the job was being printed.
?Job aborted because of file error(s)
Errors in some file in the job prevented SPOOL from printing
the remainder of this job.
?Job requed at page n
The operator placed this job request back in the queue with
the REQUE command. SPOOL later continues the job request
with a new header burst page and the text FILE RESTART
REQUESTED ON PAGE n, where n is the same page number shown
in the REQUE message.
?<error text>
SPOOL encountered the RSTS/E error shown, aborted processing
the request, and cleared the request from the queue.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

A- 50

Managing the OPSER Spooling Package
Changing and Aligning Forms
The FORM command can:
o

Inform the spooler of a change in form on its device

Request an alignment operation on the device

Display information about the current form

Switches with the command specify the new form definition and request
alignment.
The command may request alignment when a new form is
specified.
To request a form change, the operator sends the FORM command with the
form name and the switches to define the form to the related spooling
job.
If an alignment is wanted for the current form, the operator can
include the /ALIGN switch with the FORM command.
The SPOOL program
does not recognize the form change request until it becomes idle. 'If
it is processing a queued request, it completes the processing before
it performs the forms change.
(To make the change immediately,
request that SPOOL requeue the current request.
The program requeues
the request and becomes idle.)
To perform only an alignment, specify the FORM command without any
form name and with only the /ALIGN switch. Again, the command takes
effect only when SPOOL becomes idle.
The program follow these steps:
1.

Prints characters to delineate left and right margins, and
prints the text TOP OF FORM centered on the same line.

Generates characters to position the paper on the last line
of the form.

Prints characters to delineate the left and right margins,
and prints the text END OF FORM centered on the same line.

Positions the paper at top of the next form.

SPOOL generates an action request and awaits a response.
The operator
may inspect the alignment and type one of two responses to the action
request.
If the alignment is not correct, the operator can adjust the
hardware and send the response RETRY back to the spooler.
In response
to RETRY, the spooler performs steps 1 through 4 again and generates
another action request. When the alignment is accurate, the operator
types GO as a response to the action request.
The spooler returns to
normal processing.
Whenever SPOOL processes any FORM command, it sends a message to the
operator indicating that the new form characteristics in effect.
In
any FORM command, only those options specified in the command change

A-51

Managing the OPSER Spooling Package
the form characteristics. Thus, if the operator sends a FORM command
alone, without a form name or any options, the spooler displays the
characteristics of the current form on the Operator Services Console.

Batch Processor Program: BATCH
The BATCH system program runs without user intervention ahd executes
files of standardized commands queued for either a specific or the
general Batch Processor.
The program consists of four modules:
o

BATCH sets initial conditions for batch processing.

BATIDL checks status when no requests are being handled.

BATDEC decodes and performs error checking on command files.

BATRUN executes the decoded batch commands.

For simplicity, this appendix refers only to one program, BATCH, which
functionally includes the four modules.
Each module is stored in the
OPSER package account OPSER$:, has a protection code of <232>, and
requires SWCFG privilege to run.
To run BATCH, type the following command while logged in to the system
under an account with SWCFG privilege:
RUN OPSER$:BATCH
BATCH V9 RSTS V9
#

TIMESHARING

Typically, this start-up of BATCH is done in the system start-up file.
If you do not have the SWCFG privilege, the system displays an error
message indicating that you do not have access to BATCH.
If you have the SWCFG privilege, BATCH runs and prints its
identification line and the number sign (#) prompt.
In response to
the # prompt, enter a specification in the following format:
logical device:/start-up switch(es}
The logical device is the name of the queue and the unit number within
that queue from which this copy of BATCH takes job requests.
This
name does not specify the pseudo keyboard on which BATCH executes
requests.
The PHYSICAL start-up option can spe~ify the pseudo
keyboard unit on which BATCH executes.
The logical name must have the
form BA: or BAn: where n is a unit number from 0 to 7.
If BAn: is
specified, the Batch Processor executes requests queued to either that

A-52

Managing the OPSER Spooling Package
explicit unit or the general batch queue BA:.
If BA: is specified,
the program executes job requests in the batch queue regardless of the
unit to which they are queued.
Note
The general batch spooling queue, BA:, is useful only
on systems with Batch Processors running with the
same default conditions.
The logical device specified as the queue name must be a Batch
Processor; the device name given must not have a logical assignment to
some other device.
If only a queue name is given in response to the prompt and BATCH
finds no errors, the program establishes default processing
conditions, prints the DETACHING message, and detaches itself from the
terminal.
BATCH forms the default receiver identification from the queue name.
BATCH also establishes other default conditions:
o

BATCH tolerates no errors and terminates any queued request
encountering a fatal or warning error.

User log files are queued to the system default line printer
with deletion specified.

The run burst remains unchanged.

The priority remains unchanged.

At start-up, BATCH performs the same error checking and processing
SPOOL performs.
See the section "Start-up Error Processing" for the
description of SPOOL start-up error processing.

BATCH Start-up Options
Include options with the BATCH processor designator to control its
operation.
Table A-14 summarizes these options, which are in the form of
switches.

A-53

Managing the OPSER Spooling Package
Table A-l4:

BATCH Start-up Options

+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Option I
Syntax and Meaning
I
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

ASSIGN

/ASS[IGN]
Reserves a pseudo keyboard device to this job.

ERROR

/ERR[OR]:severity
Sets the error severity default for this processor so
that errors of that severity are tolerated and queued
requests having that or lesser severity end
successfully.
/ERR[OR]:FAT[AL]
Tolerates all errors.
/ERR[OR]:WAR[NING]
Tolerates only warning errors.
/ERR[O]R:NON[E]
Tolerates no errors (fatal and warning errors terminate
queued requests). This is the default severity.

DELETE

/DEL[ETE]
Deletes user log files after printing. This is the
default condition unless the NODELETE option is
specified.

NAME

/NAM[E]:rcvrid
Places, in the system message receiver table, the
specified receiver identification for this job instead
of the default identification. The default for a Batch
Processor is BAnSPL for specific processors and BASPL
for the general processor.

NODELETE

/NODEL[ETE]
Does not delete user log files after printing. Without
this option, all log files are deleted. Requester may
override this option with the /NOQUE switch in the $JOB
command.

NOQUEUE

/NOQUE[UE]
Does not queue user log files for printing. Without
this option, all log files are queued without a queue
name and with deletion unless changed by the /QUEUE and
/DELETE switches. Requesters cannot override this
option.

A-54

Managing the OPSER Spooling Package
Table A-14:

BATCH

Start~p

Options (Cont.)

+ - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Option I
Syntax and Meaning
I
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

PHYSICAL I /PHY[SICAL]:dev:
I Uses the pseudo keyboard (for example, PKI:) as the
I device on which this processor executes user batch
I jobs.

PRIORITY I /PRI[ORITY]:nnn
I Sets the job priority of BATCH to nnn, where nnn is a
number from -120 to 120. Without this option, the
priority remains unchanged. You need TUNE privilege to
specify this qualifier.

I
I
I
I
I
I
I

I
I
I
I

Do not use /PRIORITY after a /NAME, or /PHYSICAL
switch, or after a BAn: designator.
QUEUE

/QUE[UE]:[quenam]
Queues all user log files to the specified spooling
queue (LPO: through LP7:) rather than to the general
print queue. If no queue name is specified, all jobs
are queued to the general print queue. Files are
deleted after printing. Requesters may override queuing
with the /NOQUE switch in the $JOB command. Deletion of
the files by the SPOOL program may be overridden by
including /NODELETE as a start-up switch.

RUNBURST

/RUN[BURST]:nnn
Sets the job run burst of BATCH to nnn, where nnn is a
number from 1 to 127. Without this option, the run
burst remains unchanged. You need TUNE privilege to
specify this qualifier.
+- - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

BATCH Interrupt Commands
The operator uses interrupt commands sent through the operator
services program OPSER to communicate with a Batch Processor. Note
that any responses to an interrupt command are displayed on the
Operator Services Console.
T~ble

A-IS summarizes these BATCH interrupt commands.

A- 55

Managing the OPSER Spooling Package
Table A-lS:

BATCH Interrupt Commands

+ - - - - - - - - - - - .;. - - - - + - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

I Command Syntax I

Meaning

+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

ABO[RT]
CON[TINUE]

I
I Immediately terminates the current process and
I removes the request from the queue.
I
I Wakes up the Batch Processor to continue normal
processing after either a PAUSE command or after
a user request for operator action (for example,
in the $MESSAGE/WAIT command).

END

Terminates processing after completing the
current request. The operator must then run the
Batch Processor again to process further
requests.

LAS[T]

Prints the most recent message generated by this
Batch Processor.

NOT[ICE] text

Inserts the specified text in the user log file
and precedes it with the heading: NOTICE FROM
OPERATOR.

OFF[LINE]

Immediately terminates all processing by this
Batch Processor (same as END followed by ABORT).

PAU[SE]

Places the Batch Processor in a sleep state,
during which it responds to most commands and
resumes normal processing in response to a
CONTINUE command.

STA[TUS]

Prints a status report for this Batch Processor.
+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.;. - - - - - - - - - - - - --+

BATCH Start-up Procedure
BATCH is most conveniently started by commands in the system start-up
command file. See the section "Creating and Using Command Files" in
Chapter 3.

Operator Action Requests from BATCH
The BATCH program, in processing certain commands in a user command
file, generates requests for operator action. These requests come
through OPSER as action requests that require some operator action and
A- 56

Managing the OPSER Spooling Package
a typed answer before the Batch Processor continues processing. These
action requests result from commands requiring the operator either to
mount and dismount volumes or to respond to a special message with
which a stall is involved.
The operator answers an action request
with the ANSWER command through OPSER.
On a mount request, BATCH asks the operator to mount a device by an
action request with text in the following format:
MOUNT xx:'logical id'/'vid'/WRITE/NOWRITE/DEN:nn/PAR:nn
DEVICE?
If a specific volume is involved, its identification appears as text
replacing 'vid.' This text is the visual identification used to
distinguish the volume.
Table A-16 lists the specific device type given by xx:.
Table A-16:

BATCH Device Type Designators

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Designator I
Meaning
I
+ - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - - - - - - - - - - +

CD
CR

CDII punched card reader
CRII high speed punched card reader or the CMII
marked-sense card reader
DB
RP04, RP05 or RP06 disk pack drive
DK
RK05 or RK05F disk cartridge drive
DM
RK06/RK07 disk cartridge drive
DL
RLOI/RL02 disk pack drive
DP
RP02 or RP03 disk pack drive
DR
RM02/RM03/RM05/RMBO disk pack drive
DT
TU56 DEC tape drive
DU
All MSCP disks: RA60, RABO, RABI, RD51, RD52, RC25,
Rx50
DX
RXOI/RX02 floppy disk drive
LP
Any line printer
MM
TU16, TEI6, TU45, or TU77 magnetic tape drive
MS
TSII, TSV05, TK25, or TUBO magnetic tape drive
MT
Any magnetic ,tape drive
PP
High speed paper tape punch
TT
Any keyboard line
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
If the text of the action request indicates a specific volume, the
operator should mount the medium on a free unit of the device type
specified by xx:.
If a volume is not involved, the operator should
make sure a unit of the type specified by xx: is ready and on line.

A- 57

Managing the OPSER Spooling Package
When the unit is ready, the operator must type the device
specification (device type and unit number followed by colon) as text
in the ANSWER command for that action request number. BATCH assigns
that unit and continues processing the user's queued request.
When BATCH is done with the device, it generates an action request to
dismount the volume or device. If the request involves a volume, the
operator must remove the volume from the device specified and place
the unit off line. To continue the BATCH processing, the operator
types the CONTINUE command as text in the ANSWER command to OPSER for
that action request number. This response tells BATCH to deassign the
unit and to continue processing.

Operator Communication Program: PLEASE
The PLEASE program communicates directly with the operator services
program OPSER and, when OPSER is not running, sends text to the system
console terminal (KBO:). The program PLEASE is stored in the OPSER
package account OPSER$: with protection code of <232>.
Any user can run PLEASE, but only users with SWCFG privilege or users
defined as valid operators in the operator table can issue OPSER
commands.
You, as the system manager or assigned operator, can run PLEASE to
send commands to OPSER. Users who do not have SWCFG privilege and are
not valid operators may run PLEASE to send text to the Operator
Services Console.
Note
If you want to restrict PLEASE to only be run by
users with WREAD privilege, change its protection
code to <124>.

Running and Terminating PLEASE
To run PLEASE, type the following command:
RUN OPSER$:PLEASE
PLEAsE V9 RSTS V9

TIMESHARING

PLEASE prints its identification line and the number sign (#)
character as a prompt to indicate it is ready to accept text.

A-58

Managing the OPSER Spooling Package
PLEASE accepts one line of text terminated with the RETURN key. A
line of text exceeding the maximum length (255 characters) causes the
program to print the error message ?Line too long and reprint the
prompt.
If the first character of text is not a slash (/) character,
PLEASE tries to send the text as a message to OPSER.
If the first
character of text is a slash, PLEASE tries to send the text as a
command to OPSER. To show the operator that it is sending the message
or command, PLEASE prints one of the following messages:
Message sent to 'OPSER'
Command sent to 'OPSER'
The program prints the # prompt again, after which the operator can
type another line of text.
Entering CTRL/Z in response to the prompt
terminates the program.
When OPSER is not active, PLEASE broadcasts messages on the system
console terminal; however, it does not send commands.
In these
situations, the program notifies the user with one of two messages:
%OPSER not active - message broadcast to KBO:
%OPSER not active - command not sent
The message printed on keyboard unit 0 is preceded by the text:
%MSG for 'OPSER' but it is not active:

OPSER Commands through PLEASE
Any user ~ith SWCFG privilege or defined as a valid operator can
communicate with OPSER and with jobs on line to OPSER by typing a
command through PLEASE. The user denotes an OPSER command by typing
the slash (/) character as the first character in the line of text.
Table A-I? summarizes these PLEASE commands to OPSER. Note that the
circumflex (A) character marks the location of a required space.

A-59

Managing the OPSER Spooling Package
Table A-l7:

PLEASE Commands to OPSER

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- --+
I
Command Syntax
I
Meaning
I
+- - - - - - - - - - - - - - - - - - .. - -+- - - - - - - - - - - - - - - - - _ .. - - .. - _ .. - - - - - - - - - - - - - - - _ .. - - --+
/ANS~msgnumber:text
/CHA~KBn:

/DEL~msgnumber
/DEL~#nn:n

/DET
/EX1
/1NT~rcvrid:text

/L1S" JO
/L1S~ OP

/LOG~file;msglevel

/LOG" ;msglevel
/LOG
/MES"msglevel
/OPE"KBn:[nnn,nnn]
/OPE" -KBn:[nnn,nnn]
/RET"msgnumber
/RET" m:n

I
I
I
Changes operator services console to
I
keyboard unit n.
I
I
Deletes outstanding action request.
I
I
Deletes n oldest action requests for job
I
number inn.
I
I
Detaches OPSER from the OSC.
I
I
Terminates OPSER.
I
I
Sends unsolicited text to online job.
I
I
Prints online job table.
I
I
Prints valid operator table.
I
I
Creates log file and sets message level.
I
I
Changes message level of current log file.
I
I
Closes current log file and stops recording. I
I
Sets message level for OSC.
I
I
Adds keyboard and account combination to
I
valid operator table.
I
I
Removes keyboard and account combination
I
from valid operator table.
I
I
Prints associated message.
I
I
Prints oldest m action requests for job
I
nu'mber in.
I

Responds to an action request.

+- _ .. _ .. - .. - _ .. _ .. - - - - .... - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - .. - - - - - _ .. - - - - - - - --+

A-60

Managing the OPSER Spooling Package
When OPSER receives a command from PLEASE, it makes sure that the user
has SWCFG privilege or that the user's keyboard and account numbers
are present in the valid operator table.
If not, OPSER broadcasts the
error message ?Invalid oper on the terminal from which the command was
made.
Commands sent by a valid operator can be executed by OPSER itself or
by a program on line to OPSER.
If OPSER itself executes the command,
any response from the command is broadcast on the originating
terminal.
For example, because OPSER itself processes the LIST JOBS
command, the online job list generated appears on the originating
terminal.
An INTERRUPT command, however, passes text to another program. Any
response from the other program is displayed on the OSC and not on the
originating terminal.
To see a message or response from an INTERRUPT
command, the operator should change the osc to the current keyboard
(the line on which PLEASE is running) before transmitting the command.
Action requests and messages (responses to commands or text sent to
OPSER) are displayed only if the current message level allows.

PLEASE as a CCL Command
If you install PLEASE as a CCL command, the operator can type PLEASE
followed by a text line to send commands to OPSER.
PLE is the
standard abbreviation for the ceL command.

Terminating Operator Services and Spooling
Usually you terminate OPSER and programs on line to OPSER by running
the SHUTUP program.
SHUTUP, however, terminates time-sharing
operations.
If it is necessary to terminate operator services and
spooling without shutting the system down, the operator can type a
sequence of commands to stop spooling operations in an orderly
fashion.
To understand the sequence, you must know about OPSER
shutdown levels.

OPSER Shutdown Levels
When OPSER receives a command from SHUTUP to perform an orderly
shutdown in logical end mode, OPSER sends an END command to each
online job in a fixed, logical sequence. OPSER selects by shutdown
level the order in which jobs are ended. Online jobs at the lowest

A-6l

Managing the OPSER Spooling Package
level terminate first. When all jobs at one level have terminated and
have been removed from OPSER'S internal tables, OPSER begins sending
END commands to jobs at the next highest level. When all online jobs
have properly terminated, OPSER kills itself and SHUTUP proceeds with
the system shutdown.

OPSER Manual Shutdown Procedure
You may need to shut down the SPOOL program without shutting down the
entire system. The two possible procedures are as follows:
o

The operator can issue the END command to the spooler at any
time.
This command causes the spooler to shut itself down
the next time it is ready to get a new job. Thus, if the
spooler is printing a job, it completes the job's output
before shutting down.
If SPOOL is waiting for a job, it
shuts down immediately.
The operator can use the ABORT
command to terminate the job if the operator wants the job
currently printing to end.
For example, to manually shut down the LPOSPL spooler in
logical end mode, use the command:
PLE/INT LPOSPL:END
At the completion of the current job, the spooler kills
itself.
This shutdown procedure merely mimics what OPSER
does on command from SHUTUP.
The operator sends the END
command, in turn, to jobs at each shutdown level.
The output
of the LIST JOBS command gives the shutdown levels for each
online job. When OPSER displays END messages for all jobs at
one shutdown level, the operator can send the END command to
all jobs at the next highest shutdown level. After the
online job table is clear and OPSER has generated END
messages for all jobs, the operator can send the EXIT command
to OPSER.

A second way of shutting down the spooler is with an OFFLINE
command.
The OFFLINE command immediately stops any job that
is printing and prints an ABORT message on the listing to
indicate the action taken.
The OFFLINE command also causes
SPOOL to shut down after the current job finishes.
For example, to manually shut down the BAOSPL job
immediately, use the command:
PLE/INT BAOSPL:OFFLINE
BAOSPL aborts the current job, clears it from QUEUE.SYS, and
kills itself.
A-62

Managing the OPSER Spooling package
If the operator wants to terminate a printing job for shutdown or any
other reason, the line printer must be on line. Under no
circumstances does the spooler consider a job completed until all the
data that the spooler tries to print (including termination messages)
is actually printed.
If the operator abbrts the job with the ABORT
command, the spooler deletes (at the first opportunity) whateve~r data
is already buffered; the line printer must be on line to allow this.
If the operator wants no further output, use the REMOVE/JOB command to
remove the spooler job.
In this case, no clean-up can be performed.
This process may be necessary when certain hardware fails (for
example, if the line printer interface does not raise the READY flag).
It should only be used in a crisis.
The job that was being printed
should be killed from the queue file by a QUE/K command from the
operator.

RESTOR as an OPSER Controlled Program
The RESTOR program runs as a job on line to OPSER only after it has
finally detached from its terminal. When RESTOR is running detached,
the operator can send commands to it through OPSER.
If, after having
been detached, RESTOR is later attached to a terminal again, the
operator can communicate with RESTOR either at its terminal or through
the OPSER program.
Table A-18 summarizes the commands that RESTOR recognizes.
Note that
the circumflex (A) character marks the location of a required space.
Table A-18:

RESTOR Commands through OPSER

+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Command Syntax I
Meaning
I
+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ABO[RT]
I
I
I CON[TINUE]
I
I
I

Terminates the RESTOR run immediately and removes I
RESTOR from OPSER internal tables.
I
Wakes up the RESTOR program to continue
processing after a PAUSE command or continues
processing after an operator has performed some
requested action.

A-63

I
I
I
I
I

Managing the OPSER Spooling Package
Table A-IS:

RESTOR Commands through OPSER (Cont.)

I
I DET[ACH]
I
I
I
I

Valid only under these conditions:

If RESTOR is attached

OPSER is running

The RESTOR listing file is not on the
terminal to which RESTOR is attached

No messages are currently pending for the
specific RESTOR job

I
I
I

If these conditions are met, RESTOR detaches and
is given a receiver identification of BACKnn
where nn is its job number. All further
interaction with RESTOR is done through OPSER.
END

Finishes transferring the current file and
terminates processing.

LAS[T]

At the OSC, prints the most recent message
generated by this RESTOR job.

LEG[AL]

At the OSC, prints a list of commands that can
legally be given for this phase of the RESTOR
run.

NOT [ ICE]" text

Inserts the specified text in the RESTOR listing
file. Precedes the text with the heading NOTICE
FROM OPERATOR.

PAU[SE]

Places RESTOR in a sleep state, during which it
responds to mo~t commands, continues normal
processing in response to a CONTINUE command, and
terminates processing on an ABORT command.

STA[TUS]
Prints a status report for this RESTOR job.
+- - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
While RESTOR is running detached, it generates all of its requests for
operator interaction through OPSER as messages.
The operator uses the
INTERRUPT command to respond to such requests.
See the RSTS/E
utilities Reference Manual for the proper responses to RESTOR
requests.

A- 64

AppendiJc B
Number Conversion

Many applications require a number based on bit values in a PDP-II
word.
Table B-1 lists the octal and decimal values for each bit in
the PDP-II word.
Table B-1:

Bit Values in the PDP-II Word

+- - - - - - - -+- - - - - - - - -+- - - - - - - --+

Bit
Octal I Decimal I
Number
Value I
Value I
+- - - - - - - -+- - - - - - - - -+- - - - - - - --+

o
1
2
3
4
5
6
7
8
9

10
11
12
13
14
15

1
2
4

10
20
40
100
200
400
1000
2000
4000
10000
20000
40000
100000

1
2
4
8

16
32
64
128
256
512
1024
2048
4096
8192
16384
32768

+- - - - - - - -+- - - - - - - - -+- - - - - - - --+

B-1

Appendilc C
Disk Device Sizes

Table C-l lists the device cluster size and device size (in 512-byte
blocks) for each disk that RSTS/E supports. All values are in
decimal.
Table C-l:

Disk Device Sizes

+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+

I
I Disk
I Type

I Device I
I Cluster I
I Size
I

Total
Available
Blocks

+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+

I Rx50 I
I RK05 I
I RK05F
I
I RLOI
I RL02
I RD51
I RD52
I RC25
I

1
1
1

799
4800
4800 for each unit;
2 units per drive
1
10220
1
20457
1
21599
1
60479
1
'50901 for each unit;
2 units per drive
RK06
1
27104
RK07
.1
53761
RP02
2
39998
RP03
2
79998
RM02
4
131648
RM03
4
131648
RP04
4
171796
RP05
4
171796
RA80
4
237208
RM80
4
242572
RP06
8
340664
RA60
8
400168
RM05
8
500352
RA81
16
891056
+- - - - - - -+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - --+
C-l

Appendix D
General RSTS/E Messages

This appendix lists the general messages that you may encounter when
using RSTS/E. Table D-l also indicates the probable cause of the
error in your use of a command or system program.
If you perform DECnet/E operations, you may receive messages that are
described in DECnet/E documentation but not in this appendix. In
addition, the utility programs that support DCL can produce messages
not all of which are listed here. Those messages are listed in the
RSTS/E utilities Reference Manual.

Special Characters Used in Error Messages
The question mark (1), double question mark (11), and percent sign (%)
characters preceding a message indicate its severity. A single
question mark precedes standard error messages, which means that the
command failed to do what you asked but you can continue. For
example:
?Too many parameters
In this case, the command failed because you included too many
parameters.
A double question mark precedes severe error messages, which means

that the command failed to do what you asked and you cannot continue.
For example:
??Fatal system I/O failure
By contrast, the percent sign identifies a warning message, which
means that the command may not have worked as you intended. For
example:
%Logical name has not been assigned

D-l

General RSTS/E Messages
In this case, the MOUNT command worked but no logical name was
assigned to the device.
Informational messages do not have a preceding character; they provide
extra details about the effects of a command.
For example:
Queue file being reorganized - please wait ...
This message informs you that, as a result of your command, the file
is being reorganized.
Angle brackets ( < »
surrounding text indicate a place holder for
what the system inserts when an error message occurs.
Table D-1 lists the messages that you can get when using RSTS/E and
the probable causes.
Table D-l:

General RSTS/E Messages

I
I ?Account or device in use
I
The device cannot be mounted or dismounted because it is
I
open or has one or more open files. This error can also
I
occur when a user attempts to access a non-shared disk from
I
a job other than the one specified in the /NOSHARE=n
I
command.
I
I
I ?Additional argument required
I
You did not specify enough arguments in the DeL function.
I
I
I ?Additional qualifier required
I
You did not include a qualifier required in a command.
I
I
I %AII volumes must be of the same media type
I
f
You attempted to write a Backup set on both disk and tape.
I
I.
I ?Ambiguous keyword
I
You abbreviated a keyword to short; DeL cannot distinguish
I
it from other keywords.
I

D-2

General RSTS/E Messages
Table D-1:
~

I
~

General RSTS/E Messages (Cont.)

- - - - - - - - - ---- - -- - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - --- - - - - - - - - - - -- - Message and Meaning
I
--- - - - ---- - - - --- - - - - - - - - - - - - - - - - - - - - -- - -- - - - - ------ - - --- - --- - - ----~

--~

%An unrecognized character was typed - try again
There were extra characters in the command line that BACKUP
did not recognize as meaningful.
?Argument not allowed
You used an argument with a qualifier that does not accept
one.

I
I
I
I
I
I
I
I
I

?Argument required
An argument was not supplied with a qualifier which required
one. For example, /SINCE=, without an argument, would
generate this error.
The user did not supply an argument to a DCL function that
required one.
??Bad directory for device
The directory of the device referenced is in an unreadable
format. For example, the tape format differs from the format
you specified with the MOUNT command.
%Block header CRC error detected for block
Although this block was read successfully by the source
device, BACKUP discovered that there was an error in the
block. BACKUP will attempt to recover the data using
recovery data if possible.

I
I
I
An invalid blocksize was specified. Blocksize must be a
I
multiple of 16 for tape and 512 for disk.
I
I
?Can't access terminal <error text>
I
I
An error occurred while attempting to access the terminal to I'
send the setup file using the SET TERMINAL command.
I
I
?Can't find file or account
I
I
Either the account or file does not exist, or you typed a
I
file .. specification incorrectly.
I
?Blocksize must be a multiple of <16 or 512>

D-3

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

?Can't mount a private disk as public
You tried to mount as public (using the MOUNT command's
/PUBLIC qualifier) a disk that was initialized as private.
?Can't rebuild disk because device is write protected
A user with MOUNT privilege attempted to rebuild a disk

(using the MOUNT command's /REBUILD qualifier), and the
drive is write protected. Therefore, the mount and rebuild
operations fail.
?Command not installed
You typed a DCL command that has not been installed on your
system. The DeL keyboard monitor could not find the utility
needed to carry out your command. This message can also be
displayed if you type a remote file specification in a
command that allows remote file specifications, but your
system does not have DECnet/E.
?Command requires <privilege> privilege
The user does not have the appropriate privileges to
complete an operation.
?Command too long
The length of the command, including continuation lines,
exceeds the maximum allowed for the command.' Or, the length
of the translated command string exceeds the maximum allowed
for the command.
For example, this message occurs with the LINK command in
either of two cases:
o

The text you typed in response to the $ prompt and the
Files: or Root files: prompt added up to more than 127
characters after translation.

with LINK/COBOL, the text was longer than 80 characters
after translation.

D- 4

I
I
I
I

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

- - - - ---- - - ----------- - ------- - - - - - - - - - - - - -- - - --- - - ------- - ------- - --~
Message and Meaning
I
~ ------- - - - - -- - -- - - - - ----- - ----- - - - -- - -- - - - - - - - - - - - - -- - -- - -- - ---- - - - -~
~

%Command will proceed as requested
The user's symbol tables could not be written out to the DCL
work file, but the command will be processed. The user may
be over quota. Corrective action should be taken before the
user continues processing.
?Comma required
A DCL function required two or more arguments and .they were
not separated by a comma.
?Conflicting arguments
Multiple arguments to a qualifier conflict. For example,
both an AFTER date and an exact date were specified to the
/CREATED qualifier.
?Conflicting elements
You specified qualifiers or parameters in a command that do
not agree in type (for example, a print qualifier with a
batch server).
?CPU limit exceeds queue's maximum
You specified a /CPU LIMIT value in a SUBMIT command larger
than the maximum allowed for the queue.
?Data error on device
One or more characters may have been transmitted incorrectly
due to a parity error, bad punch combination on a card, or
similar error.
?Data error or incorrect density
This message occurs for one of the following reasons:
o

You specified the incorrect density.

The data on the tape is damaged.

The tape drive is faulty.

D-S

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

i- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~

Message and Meaning

i- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~

?Default macro for KBn: does not exist
The /INQUIRE command could not recognize the terminal and
there was no default macro specified for this keyboard in
the default file, TERDFL.SYS. You should supply a default
macro for the keyboard. Until that is done, the keyboard's
characteristics have to be set manually.
Density of <density> BPI not available, using <density> BPI
instead
The requested density was not available on the drive. BACKUP
reports the density that is being used.
?Device does not exist
The device name you specified does not exist on your system.
%Device hung or write locked
%Dismount will proceed as requested
You attempted to dismount a disk that has been physically
dismounted. However, the logical dismount will succeed.
?Device hung or write locked
Check the hardware condition of the device requested.
possible causes of this error include:
o

A line printer out of paper

A disk drive being off line

A disk is dual-ported and is not write-protected

%Device in use
You specified /NOSHAREABLE in an INITIALIZE/SERVER command;
however,the print server's device is not available or no
pseudo-keyboards are currently available for the batch
server. PBS allocates the device as soon as it becomes
available.

D-6

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -.- - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

?Device is not a terminal
A device other than a terminal was specified. Only specify

keyboards.
?Device is restricted
This message occurs when a user without DEVICE privilege
attempts to open files on a disk restricted to users with
DEVICE privilege.
?Device must be disk
You specified a file on a nondisk device, where a disk
device is required.
?Device must be disk or tape
The device specified was not a disk or tape, and only disk
or tape is valid.
?Device name may not be specified
A device name is not valid at this point, but one was
specified.
?Device not available
The specified device exists on the system, but an attempt to
allocate or use it is prohibited for one of the following
reasons:
o

The device is currently reserved by another job.

The device requires privilege for ownership and you do
not have the necessary privilege.

The device or its controller has been disabled by the
system manager.

The device is a keyboard line for pseudo keyboard use
only.

D-7

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+ - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - ,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

?Device not file-structured
An attempt was made to access a device, other than a disk
drive or magnetic tape drive, as a file-structured device.
?Device not write protected
You specified the /NOWRITE qualifier when you tried to mount
a magnetic tape, but the device is not write protected.
Write protect the device by removing the plastic ring from
the magnetic ~ape hub.
?Device offline
You tried to use a tape or disk, but the device is off line.
%Device write protected
The magnetic tape or disk is protected against write access.
Therefore, you can only read files on the device, but cannot
write (perform output) to the device. If you want to write
to the device, first write enable the device, next dismount
the device, and then mount the device again.
?Device write protected
You requested write access to a device that is write
protected. Write enable the device and then retype the
command.
%Directory attributes verification failure for directory
<directory>
The directory attributes stored in the Backup set are
different from the directory attributes as stored in the
directory structure. This is a verification mismatch.
?Directory does not exist
A file specification indicates a directory that does not
exist on the particular private disk. Or, a wildcard
directory specification failed to produce a match on the
disk specified. This error can occur only with' private
disks.

D-8

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
??Disk error during swap
A hardware error occurs when your job is swapped into or out
of memory. The contents of the job area are lost, but the
job remains logged in to the system and returns to DCL.
Report such occurrences to the system manager.
Disk is being rebuilt - wait ...
This informational message is displayed when a user attempts
to rebuild a disk. The disk is logically mounted when the
rebuilding operation is complete.
?Disk is mounted non-shared
A user attempted to dismount a disk that was mounted as
nonshared (by a different job) by specifying /PUBLIC in the
DISMOUNT command.
?Disk is mounted private or non-shared
A user attempted to dismount a disk that was mounted as
nonshared (by the same job) or private by specifying /PUBLIC
in the DISMOUNT command.
?Disk is mounted public
A user with MOUNT privilege attempted to dismount a public
disk that was mounted as public, without specifying /PUBLIC
in the DISMOUNT command, so the dismount fails.
%Disk is mounted read-only
This warning occurs if you do not specify either read or
write access (/NOWRITE or /WRITE) when mounting a disk
initialized as read-only. Therefore, you are granted read
access only.
?Disk is NOSHARE to another job; can't verify pack-id
A user with MOUNT privilege attempted to mount a disk that
is mounted /NOSHARE to another job.

D-9

General RSTS/E Messages
Table 0-1:
~

I
~

General RSTS/E Messages (Cont.)

- - - - - -- - - - - - -- - - -- - - - -- - - - - - - - - - - - - - - - - - - - -- - - - - - - - -- - - - -- - ----- - -Message and Meaning
I
-- - ---- - - - - -- - -- - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - -- - - - ------------- - -

-~
-~

%Disk is restricted and mounted non-shared, read-only
A user specified /NOREBUILD (to suppress rebuilding) and
/NOSHARE in the MOUNT command and the disk was dirty.
Therefore, the disk is mounted nonshared and restricted, and
read-only access is granted. ("Restricted" means that access
is allowed only to users with DEVICE privilege.)
%Disk is restricted and mounted private, read-only
A user specified /NOREBUILD (to suppress rebuilding) and
/SHARE in the MOUNT command and the disk was dirty.
Therefore, the disk is mounted nonshared and restricted, and
read-only access is granted. ("Restricted" means that access
is allowed only to users with DEVICE privilege.)
?Disk needs rebuilding but device is write protected
A user with MOUNT privilege attempted to mount a dirty disk
(and did not specify /REBUILD or /NOREBUILD), but the device
is write protected and the automatic rebuilding cannot be
performed. Therefore, the mount fails.
?Disk needs rebuilding but you do not have MOUNT privilege
This message occurs when a user without MOUNT privilege
tries to mount a private disk that was not logically
dismounted. The system manager can correct the situation by
rebuilding the disk.
?Disk needs rebuilding, so it can not be NORESTRICT
This message occurs when a user with MOUNT privilege tries
to mount a dirty disk with both /NOREBUILD and /NORESTRICT
qualifiers.
?Disk pack is not mounted
The DISMOUNT command was attempted, but the disk pack was
not mounted on the specified disk drive.
??Disk pack mount error
Fatal disk mounting error. The disk is corrupt and cannot be
successfully mounted with the MOUNT command.

D-10

General RSTS/E Messages
Table 0-1:

General RSTS/E Messages (Cont.)

I
I ?Division by zero
I
The expression specified by the user attempted to divide by
I
zero.
I
I
I ?Do not specify file name or type
I
This message can occur with the first parameter of the
I
ASSIGN
command. Remember to use a space between the first
I
parameter (the string you assign) and the second parameter
I
(the name you assign it). For example, "ASSIGN DR3: X", not
I
"ASSIGN DR3:x".
I
I
I %Dual-ported disk, may still be mounted on another system
I
You specified a disk in a DISMOUNT command that is
dual-ported. So, it may still be mounted on another system.

?Equal sign required
You used a qualifier that requires an argument, but you did
not give an argument.
?Error assigning Backup set device
The RSTS/E monitor reported an error in response to BACKUP's
request to assign the Backup set device. This message will
be followed by another message describing the problem.
?Error closing Backup set
The'RSTS/E monitor reported an error in response to BACKUP's
request to close the Backup set. A message detailing the
problem will follow.
?Error creating directory <directory>
The RSTS/E monitor reported an error in response to BACKUP'S
request to create a directory. A message detailing the
problem will follow.
?Error creating disk initialization command file
The RSTS/E monitor reported an error in response to BACKUP's
request to create the command file used to initialize disks.
A message detailing the problem will follow.
D-11

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

i- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~

I
~

Message and Meaning

-- - -- - - - - - - - -- - -- - - - - - - - - - -- - - - - - - - - -- - - - - - - - ---- - - -- - - - ---- - - - ---?Error creating dynamic region
The RSTS/E monitor reported an error in response to BACKUP's
request to create a dynamic region. A message detailing the
problem will follow.
?Error creating job to initialize disk
The RSTS/E monitor reported an error in response to BACKUP's
request to create a job, used to initialize disks. A message
detailing the problem will follow.
?Error creating output directory
The RSTS/E monitor reported an error in response to BACKUP's
request to create a directory. A message detailing the
problem will follow.
?Error deassigning Backup set device
The RSTS/E monitor reported an error in response to BACKUP's
request to deassign the Backup set device. A message
detailing the problem will follow.
?Error dismounting disk to initialize it
The RSTS/E monitor reported an error in response to BACKUP's
request to dismount a disk so that it can be reinitialized.
A message detailing the problem will follow.
?Error in forms definition <forms-name>
<error message>
An error, as the error message in the second line describes,
was discovered in the forms definition displayed.
?Error initializing Backup set
The RSTS/E monitor reported an error in response to BACKUP'S
request to initialize the Backup set. This message will be
followed by another message detailing the problem.

D-12

I
-~

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

I
I ?Error mounting output disk
I
This message indicates that the monitor has reported an
I
error as a result of BACKUP's mount request. It will be
I
followed by an error detailing the problem.
I
?Error mounting Backup set
The RSTS/E monitor reported an error in response to BACKUP's
request to mount the Backup set. A message detailing the
problem will follow.
?Error number nn
An I/O error occurred while the system was attempting to
retrieve an error message. Possible causes could be that the
device containing the system error file (ERR.SYS) is off
line, or that the system error file contains a bad block.
This is a serious error, and should be reported to the
system manager.
?Error obtaining file flags for file <filename> for verification
The RSTS/E monitor reported an error when BACKUP requested
to find out what the file flags for a file to verify were
set to. This message will be followed by another message
describing the problem.
?Error opening disk non-file-structured to initialize it
<error message>
This message occurs when BACKUP is requested to initialize a
disk and the RSTS/E monitor is unable to open it in
non-file-structured mode. This generally happens because a
disk unit is off line or no disk is mounted in the drive.
This can also occur for other reasons, such as no access to
non-file-structured disks or other device specific errors.

D-13

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

;- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --r

Message and Meaning

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -, - - - - - - - - - - -;-

?Error opening file <filename> for input - skipping rest of
directory
The RSTS/E monitor reported an error in response to BACKUP's
request to open a file in the directory (note that since the
filename is unknown at the time, this may contain
wildcards). A message detailing the problem will follow.
Since BACKUP scans the directory sequentially, the rest of
the directory will be skipped.
?Error opening file <filename> for output
The moni tor' reported an error to BACKUP when it was trying
to create a file. This message will be followed by a message
describing the problem.
?Error opening file <filename> for verification
The RSTS/E monitor reported an error in response to BACKUP's
request to open a file for verification. This message will
be followed by another message detailing the problem.
?Error opening PBS file <file-spec>
<error message>
An error, as the error message in the second line describes,
occurred opening the PBS file indicated.
?Error opening Backup set
The RSTS/E monitor reported an error in response to BACKUP's
request to open the Backup set. Another message will follow,
describing the problem.
?Error opening Backup set non-file structured
The RSTS/E monitor reported an error in response to BACKUP's
request to open the Backup set device for control purposes.
An error follows which will detail the problem.
?Error performing PPN lookup
The RSTS/E monitor reported an error in response to BACKUP's
request to look up PPNs to back up. A message detailing the
problem will follow.

0-14

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

I ?Error reading accounting data for directory <directory>
I

I
I
I

The RSTS/E monitor reported an error in response to BACKUP's
request to read the accounting data for a directory. A
message detailing the problem will follow.

I ?Error reading directory attributes for directory <directory>
I
The RSTS/E monitor reported an error in response to BACKUP's
I
request to read directory attributes. A message detailing
I
the problem will follow.
I
I
I ?Error reading file attributes for file <filename>
I
The RSTS/E monitor reported an error in response to BACKUP's
I
request to read file attributes for a file being backed up.
I
A
message detailing the problem will follow.
I
?Error reading file <filename> block <block>
The RSTS/E monitor reported an error in response to BACKUP's
request to read file data. A message detailing the problem
will follow.
?Error reading output volume label
The monitor reported an error to BACKUP in response to a
request to determine the volume label of the output device.
This message will be followed by a message detailing the
problem.
?Error reading Backup set
This message indicates that an error was reported by the
monitor to BACKUP when attempting to read the Backup set. It
will be followed by a device specific error message
describing the problem. In addition, it may be followed by
other messages if BACKUP is unable to recover from the lost
data.
?Error reading Backup set attributes
The RSTS/E monitor reported an error in response to BACKUP's
request to read the Backup set attributes. An error follows
which will detail the problem.

D-15

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ?Error reading Backup set volume label
I
The RSTS/E monitor reported an error in response to BACKUP'S
I
I
I
I

request to read the Backup set label. A message detailing
the problem follows.

I ?Error restoring file dates for file <filename>

The RSTS/E monitor reported an error in response to BACKUP's
attempt to restore file dates. Another message describing
the problem follows this message.
?Error rewinding Backup set
BACKUP encountered an error when asking the monitor to
rewind the Backup set. A message det~iling the problem
follows.
?Error setting end-of-volume flag
The RSTS/E monitor reported an error in response to BACKUP'S
request to set the end-of-volume flag. A message detailing
the problem follows.
?Error setting file flags for file <filename>
The RSTS/E monitor reported an error in response to BACKUP's
attempt to set file flags (caching, protected, etc.).
Another message describing the problem follows this message.
?Error setting RTS name for file <filename>
The RSTS/E monitor reported an error in response to BACKUP's
attempt to set the runtime system name for a file. Another
message describing the problem follows this message.
<error text> opening setup file <filename>
An error occurred while trying to gain access to the setup
file.
<error text> opening speed file
An error occurred while trying to gain access to the speed
file. The speed is not set and the rest of the SET TERMINAL
command is executed.
D-16

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - .:. - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~ - - - - - --+
<error text> opening/reading default file
An error occurred while processing the default file.
<error text> reading setup file <filename>
An error occurred while processing the setup file.
<error text> reading speed file
An error occurred while processing the speed file. The speed
is not set and the rest of the SET TERMINAL command is
executed.
?Error verifying directory attributes for directory <directory>
The RSTS/E monitor reported an error in response to BACKUP's
request to read directory attributes for verification.
Another message describing the problem follows this message.
?Error verifying directory <directory>
The RSTS/E monitor reported an error in response to BACKUP's
request to obtain directory information for verification.
Another message describing the problem follows this message.
?Error writing directory attributes for directory <directory>
The RSTS/E monitor reported an error in response to BACKUP's
request to write directory attributes. Another message
describing the problem follows this message.
?Error writing file attributes for file <filename>,
The monitor reported an error to BACKUP when it was trying
to restore file attributes. Another message describing the
problem follows this me~sage.
?Error writing Backup set
The "RSTS/E monitor reported an error in response to BACKUP's
request to write to the Backup set. Another message
describing the problem follows this message.

D-17

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

I ?Error writing Backup set attributes
I
The RSTS/E monitor reported an error in response to BACKUP's
I
I
I

request to write the Backup set attributes. Another message
describing the problem follows this message.

I ?Error writing to disk initialization command file

The RSTS/E monitor reported an error in response to BACKUP's
request to write to the command file used to initialize
disks.Another message describing the problem follows this
message.
?Error writing to list file
The RSTS/E monitor reported an error in response to BACKUP's
request to write to the list file. Another message
describing the problem follows this message.
?Extra file data found in file <filename> - ignoring it
There were file data blocks for blocks beyond the written
end of file. If this was not accompanied by other messages,
submit a SPR with a copy of the ~ackup set.
??Fatal system I/O failure
An I/O error has occurred on the system level. The results
of the last command are unpredictable. This error is caused
by a hardware condition. Report such occurrences to your
system manager.
?File attributes for file <filename> may be incorrect
If BACKUP has used recovery data to restore a file, there is
a chance that the file attributes may not be correct. If
this is a possibility, BACKUP informs the user with this
message.
?File data block for file <filename> duplicated in Backup set
A file block was found to be duplicated in the Backup set.
If this was not accompanied by other errors, submit a SPR
containing a copy of the Backup set.

D-18

Ge'neral RSTS/E Messages
rable 0-1:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~
I
Message and Me~ning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~

?File data block for file <filename> missing in Backup set
A file block was found to be missing in the Backup set. If
this was not accompanied by other errors, submit a SPR
containing a copy of the Backup set.
?File data in file may be incorrect
This message can occur if there are several missing blocks
from a Backup set. It should be accompanied by other
messages, describing the cause of the problem. If not,
submit a SPR with a copy of the Backup set.
?File does not exist
This message occurs,for one of the following reasons:
o

An input file that must be present is not present.

A wildcard file specification does not match any files.

A file is not accessible because of its assigned
protection code.

File <filename> not replaced
This is an informational message, which reports that a file
was not restored because there was a file of the same name
already existing and you did not use the /REPLACE qualifier.
File <filename> restored as non-contiguous
The RSTS/E monitor was unable to locate contiguous space to
restore a contiguous file as contiguous.
?File name attribute invalid - skipping file
If this Backup set was written by RSTS/E BACKUP, submit a
SPR containing a copy of the Backup set. If this Backup set
was written by any other operating system, it indicates that
the file name could not be mapped into a RSTS/E name, and
was skipped. Rename the file on the source system to
something which will fit into the RSTS/E file naming scheme.

D-19

I
I
I
I
I
I
I

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

I
I
I
Submit a SPR with a copy of the Backup set.
I
I
?File name required
I
I
A file specification you typed does not include a file name, I
but one is needed.
I
I
?File specification required
I
I

?File name attribute missing - skipping file

This error occurs if you specify node:: without a file
I
specification (except with DIRECTORY). It also occurs if you I
have two commas with no characters between them in a file
I
specificat~on list.
I

?Files cannot be on different nodes
This message occurs with network operations. Each input file
specification you include in a network command must be on
the same node.
?Form <form-name> does not exist
The form name you specified was not defined by the system
manager. See your system manager to find out what form names
are available.
?Forms Definition File does not exist
The forms definition file, PBS$:FORMS.SYS does not exist.
See your system manager.
?Forms not defined [for server <server-name>]
The forms you specified could not be found in the forms
definition file. See your system manager.
%ID label ignored
You mounted a tape in DOS format and specified an 1D label.
Identification labels are not encoded on DOS tapes;
therefore, the label you specified is not recognized by the
MOUNT command.

D-20

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

%ID label should be specified when you mount an ANSI tape
You mounted a tape in ANSI format, but did not specify the
'tape identification label. DIGITAL recommends that you
specify the identification label. Thus, the MOUNT command
can verify that the tape you selected has been mounted.
?ID labels don't match
The identification label you specified does not match the
identification label encoded on the tape. To correct the
problem, specify the correct identification label. If you do
not know what identification label is encoded on the tape,
you can omit the ID label from the MOUNT command.
?Illegal byte count for I/O
The range of memory starting at the load address given is
not available. Refer to the memory status report of a
display program (SYSTAT or DISPLY) to select an available
range of memory. Note that you can also use the SHOW MEMORY
command.
?Illegal filename
The file name given in the command contains characters other
than alphabetic or numeric characters.
?Illegal switch usage
A eeL command contains an error in an otherwise valid eeL
switch (qualifier). For example, you cannot use the /SI:n
switch without a value for n or a colon; or you cannot
specify more than one of the same type of eeL switch.
?Illegal value - n
The swap file number specified is not 0, 1, or 3. (The swap
file 2 already exists on the system disk and can not be
added. )

D-21

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
I

I
I
I
I

?Impossible density for this device
You tried to mount or initialize a tape, but specified a
density not available on the tape drive you used. To correct
the problem, use another drive or specify a different
density.
?Incorrect density
You specified a density different from the tape's density.
?Incorrect density or uninitialized tape
This message can occur for the following reasons:
o

You tried to mount a tape that had not been
initialized.

You specified an incorrect density.

If the tape has not been initialized, use the INITIALIZE
command. Otherwise, specify the correct density.
?Invalid account
The account specified was not valid either containing
invalid characters (for example, [~~~]) or an invalid format
(for example, [1,2345]).
?Invalid argument
This error can occur when you use a qualifier in the form
The qualifier you used is spelled
properly, and the equal sign (=) or colon (:) is present;
however, the argument is either missing or syntactically
invalid.

/qu~lifier=argument.

RSTS/E displays this error message when there is no more
specific message to describe the syntax error.
?Invalid at interactive level
You specified a command that is invalid at the interactive
level. (For example, GOTO LABEL)

D-22

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and M~aning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ?Invalid attribute length - attribute skipped
I
I
If you get this message, submit an SPR with a copy of the
Backup set that generated the error.
I
I
I ?Invalid attribute - attribute skipped
I
This message indicates that the version number of a record
I
was higher than the highest version known to BACKUP. If this
I
error occurs trying to restore a Backup set written by a
I
I
newer version of BACKUP on an older version of BACKUP, the
operation may not work properly. If the version of BACKUP
writing the tape is older or the same as the one doing the
RESTORE, submit an SPR with a copy of the Backup set that
generated the error.
?Invalid BATCH command
Although the command is valid in interactive mode, the
command is not a valid BATCH command because it implies or
requires interaction with the user. (For example, INQUIRE,
SET NODATA)
?Invalid CCL command
You used the CCL prefix followed by a command that is not
installed as a CCL command on your system.
?Invalid channel number
The I/O channel number specified was invalid. Channel
numbers can range from 1 to 13 on OPEN~ READ and CLOSE
commands, and from 0 to 13 on WRITE commands.
?Invalid character
You typed an invalid punctuation character.
?Invalid command
The command name you gave is not a DCL command, and is not
defined on your system as a CCL command. ·Or, the line begins
with a punctuation character rather than with a keyword.

0-23

I
I
I
I
I
I
I
I
I
I
I
I

General RSTS/E Messages
Table 0-1:
~

I
~

General RSTS/E Messages (Cont.)·

-- - - ----- - -- - --- - - - - - - - - -- - --- - - - - - -- - --- - - --- - --- - ------ - ---- - ---Message and Meaning
I
-- - -- - - - - - - - -- - - -- - - - - - --- - - - - - - - - -- - - - - - - ---- - - - - - - - ----------- - --~

I
I ?Invalid date
I
I
I
I

A date either has improper syntax, represents a nonexistent
date (for example, 30-Feb), or represents a date before 1970
or after 1999.

I ?Invalid density - n
I

You tried to mount or initialize a tape, but specified a

Specify a valid device.

density other than 800 or 1600 bpi. The n is the density you
I
specified.
I
I
I ?Invalid device
I
The device specified could not be found in the list of
I
standard devices or in the user-defined macros (TERMAC.SYS).
I

I
I %Invalid directory attribute record - skipping
I
This message indicates that a directory attribute code found
I
in a Backup set was unknown to BACKUP. If this error occurs
I
trying
to restore a Backup set written by a newer version of
I
BACKUP
on
an older version of BACKUP, the operation may not
I
work
properly.
If the version of BACKUP writing the tape is
I
older or the same as the one doing the RESTORE, submit an
I

I
I

SPR with a copy of the Backup set that generated the error.

The entry name you specified is invalid.

I ?Invalid entry name
I

I
I ?Invalid expression
This covers a range of expression problems. The most common
of these is an expression ending in an operator without
supplying a second operand (for example, A = B *).
?Invalid file specification
A local file specification has improper syntax.
?Invalid fill factor
A fill factor was specified that was less than 0 or greater
than 6.
D-24

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
?Invalid form definition
The definition of the specified form contains an invalid
keyword or keyword argument.
?Invalid form name
The form name you specified is either longer than six
characters or consists of one or more nonalphanumeric
characters.
?Invalid function name
The function name specified after F$ is invalid. The minimum
abbreviation point is not met for the function (for example,
F$LE is not valid because of F$LEFT and F$LEN).
%Invalid keyboard numbers n , n in default file
The numbers you specified in the default file were less than
0, greater than 127, or the first number of the range is
greater than the second number of the range.
%Invalid keyboard numbers n , n in speed file
The numbers you specified in the speed file were less than
0, greater than 127, or the first number of the range is
greater than the second number of the range.
?Invalid keyword
The keyword is not recognized. This error occurs with
keywords that are not qualifiers and are not command names.
(For example, it can occur with the options of SET and SHOW,
and with qualifier values that are keywords.)
?Invalid label
The label specified in the command procedure contains
invalid characters.
?Invalid node name
The node name field of the file specification contained
invalid characters.

D-25

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

i- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

I
Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --i-

I
I ?Invalid operation on system disk
I
You specified an operation on the system disk which is
I
invalid (for example, DISMOUNT).
I
I
I ?Invalid operator
I
I

I
I

The operator you specified in the expression is not a
defined logical, arithmetic, string, arithmetic comparison
or string comparison operator.

?Invalid PPN
The project-programmer number (PPN) you specified does not
have valid syntax.
?Invalid print device
The device you specified is not a valid print device because
it is not a line printer or terminal.
?Invalid private delimiter
The delimiter you specified was not in one of the correct
formats.
?Invalid qualifier
The qualifier keyword is not valid in the command you typed.
(This message may indicate an error in spelling or typing.)
?Invalid qualifier for disk
This message occurs when you specify an invalid qualifier
for disks. For example, /FORMAT=ANSI (applies only to
magnetic tapes).
?Invalid qualifier for tape
This message occurs when you specify an invalid qualifier
for tapes. For example, /PRIVATE (applies only to disks).
?Invalid queue name
The queue name you specified is invalid.

D-26

I
I

General RSTS/E Messages
Table 0-1:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -,- - - - - - - - - - - - - - - - - -+
?Invalid record length in Backup set - record skipped
If you get this message, submit an SPR with a copy of the
Backup set that generated the error.
%Invalid Backup set attributes - can't use it
The Backup set does not have the attributes correct for a
BACKUP Backup set.
?Invalid server name
The server name you specified is invalid.
?Invalid speed
The speed specified was not a valid speed for the interface
of the terminal. Only specify speeds that the interface
supports.
?Invalid symbol name
You specified a symbol name that contains invalid
characters.
?Invalid time
A time either has improper syntax or represents a
nonexistent time (like 25:00 or 13:00PM).
?Invalid width
You specified a width that was less than 1 or greater than
254.
?Invalid with network file specification
You gave a network file specification in one of the commands
that accepts them (RENAME, COPY, and so on), but you also
gave a qualifier that can be used only with local
operations.

D-27

General RSTS/E Messages
Table D-I:
~

General RSTS/E Messages (Cont.)

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

Message and Meaning

- - ---- - - - - - - --- - - -- - - - - - - - - - - - - - - - - - - ---- - - - - - - - - - - ---- - -- - - -- - - -

--~

?I/O to detached keyboard
This message can result from one of two actions:
o

You tried to perform I/O with a terminal line that is
used for dial-up terminals, but nobody was dialed in.

Your job became detached (perhaps because you were
dialed in and your line was later hung up) and then
tried to perform I/O with the terminal.

The second situation either causes the job to hibernate or
causes this error condition, after which the job hibernates.
You see this message when you subsequently attach to the
job.
?Keyword required
You typed nonalphanumeric characters when a keyword is
needed instead. (If you type alphanumeric characters without
a valid keyword, you receive the error message, ?Invalid
keyword. )
?Label already defined

A label was defined more than once in an indirect command
procedure.
?Label too long
The label you specified in the indirect command procedure
was longer than 255 characters.
?Log file already open

A log file was already currently open when you attempted to
open another log file using the OPEN/LOG_FILE command.
?Log file not currently open
You attempted to enable or disable logging using the SET
LOG_FILE command, and a log file did not exist.

D-28

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -;,. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ?Log file print queue closed
I
The print queue required for a SUBMIT command's /LOG QUEUE
I
qualifier
is closed or marked for deletion. Use a different
I
print
queue
for the log file.
I
I
I ?Log file print queue does not exist
I
The print queue you specified with the /LOG QUEUE qualifier
I
in a SUBMIT command does not exist. Specify-a different
I
queue.
I
I
I %Logical name has not been assigned
I
This warning can be displayed for one of two reasons:
I
I
o You had INSTAL privilege and specified a logical name
I
that was not assigned as a system logical. (This means
I
that neither the alternate logical name nor the pack-id
I
label
were assigned.)
I
I
o
You did not have INSTAL privilege and specified an
I
alternate logical name when attempting to mount a disk.
I
I
The mount succeeds in both cases, but the logical name is
I
not assigned.
I
I
I ?Magtape record length error
I
When performing input from magnetic tape, the record on tape
I
was found to be longer than the buffer designated to handle
I
I

the record.

I
I ?Magtape select error
I
When access to a magnetic tape drive was attempted, the
I
selected unit was found to be off line. This error can occur
I
when
you transfer data to or from a tape.
I
I
I ?Map or executable file required
I
With LINK, you specified /NOEXECUTABLE and did not specify a
I
map file.
I

D-29

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
??Maximum memory exceeded
This is a nonrecoverable RSTS/E error caused by the
following conditions:
o

While loading a program into memory, the job's private
maximum memory size was reached.

While executing a program, the system required more
memory for string or I/O buffer space, and the job's
private maximum memory size or the system maximum was
reached.

?Missing closing apostrophe
The user did not specify matching apostrophes (' ...
requesting apostrophe substitution.

when

?Missing closing bracket
This error can occur in a local or remote file
specification. There is a left bracket ([) or left angle
bracket «), but no right bracket (]) or right angle bracket

( >) •
?Missing closing quote
A quotation mark (") is not matched with another quotation
mark. (This error can occur in remote file specitications.)
?Missing device or file name
The command must contain either a device specification or a
device and file name specification. If you use the /SI:n
switch, a file name must be present.
?Missing open parenthesis
You did not specify an open parenthesis [(] when one was
expected.
%More than 16 speeds specified for <terminal>
While processing the TERSPD.SYS file, a terminal was found
that had more than 16 speeds specified. Only the first 16
speeds are used.
D-30

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
I
+ - - - - - - - - - :. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
?MOUNT privilege is required
You attempted an operation that requires MOUNT privilege.
For example, a user without MOUNT privilege can mount only
private disks.
?MOUNT privilege required to dismount a public disk
A user without MOUNT privilege tried to dismount a disk
initialized as public. A user without MOUNT privilege can
dismount only private disks.
?MOUNT privilege required to rebuild a disk
This message occurs when a user without MOUNT privilege
attempts to rebuild a private disk with the /REBUILD
qualifier of the MOUNT command. Have your system manager
rebuild the disk.
?Name 'or account now exists
You attempted either to COpy to or RENAME an existing file.
This error can occur with RENAME if you do not specify
/REPLACE and the output file already exists. It can also
occur with COpy if you specify /NOREPLACE and the output
file already exists.
?Network node names must be the same
Different node names were specified on input file
specifications.
?No buffer space available
The system is overloaded and cannot complete your command
because small buffers are currently unavailable. Try the
command again later.
?No channels available
An I/O or DCL command file channel is not available. You may
have issued the at (@) command or an OPEN command, but a
channel is not available.

D-3l

I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I

General RSTS/E Messages
Table n-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - -, - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
?No default {Print,Batch} queue
You did not specify a queue name with the PRINT or SUBMIT
command, and no default ~ueue exists.
?No default print queue for log file
The /LOG QUEUE qualifier in a SUBMIT command was specified
without an explicit queue name; however, no default print
queue exists. Use an explicit queue name for the log file.
?No file name or type permitted
A device:ppn syntax was expected and you supplied a full
file specification which included either a file name or
type.
?No logins
This message can be displayed when you try to log in, for
one of two reasons:
o

The system is full, so it cannot accept additional
users.

The system manager has disabled logins.

(Possibly, logins are disabled because the system will be
shut down shortly.)
?Non-executable file
This error occurs if the file you are trying to run is a
source file; for example, .BAS. You need to compile and link
the file before you run it. (Note that an executable file
includes the value 64 in its protection code.)
?Non-printable character
You typed a control character.

0-32

I
I
I
I
I

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I ??Non-res run-time system
I
This message generally indicates hardware problems. For
I
example, the run-time system referenced has not been loaded
I
into memory and cannot be loaded for some reason, and is
I
therefore
nonresident.
I
I

I %No owner rights to {print,batch} entry <entry-spec>
I
The entry shown is not your own and you do not have
I
sufficient privilege to delete it or modify it.
I
I
I ?NO prefix not allowed
I
You used the INO prefix improperly.
I
I
I %No {Print,Batch} entry <entry-spec> found
I
No entries matching the entry-spec you specified in a SHOW
I
ENTRY or SET ENTRY command were found.
I
I
%No {Print,Batch} queue <queue-name> found

No queues matching the queue name you specified in a SHOW
QUEUE or SET QUEUE command were found.
%No {Print,Batch} server <server-name> found
No servers matching the server name you specified in a SHOW
SERVER or SET SERVER command were found.
?No qualifiers allowed
The user specified a qualifier on a command that does not
allow qualifiers.
%No qualifiers are valid for RESTORE
You attempted to enter a qualifier to the RESTORE mount
qualifier. No qualifiers are valid.

D-33

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

?No {read,write,or read/write} access to file <file-spec> [by
owne r]
The file specifications in a PRINT or SUBMIT command)
requires access that you or the specified owner does not
have.
?No room for user on device
In attempting to create a file on a device, or write
information to a device, you exceeded some size limit. If it
was a nondisk device, this error indicates that the device
was full. If it was a disk device, this error indicates one
of three conditions:
o

The disk as a whole is full.

You attempted to create a contiguous file, and there is
not enough space on the disk. (However, the /CONTIGUOUS
qualifier for the commands COpy and CREATE produce only
a warning if there is not enough contiguous space.)
If you attempted to create a contiguous file but were
unable to, try to create a noncontiguous file of the
same size. If you are able to create a noncontiguous
file then you can conclude the problem is lack of
contiguous space.

If you have eliminated the first two conditions, then
the disk directory has reached its capacity. This
capacity is independent of your disk quota. The number
varies, depending on the directory cluster size that
the system manager assigned when creating the directory
and the sizes of the files in it. Large files fill up a
directory faster than small files, especially if the
large files have small cluster sizes. Also, if the
directory itself has a large cluster size, it can hold
more files and larger files.

?No run-time system
This error can occur if the program you are trying to run
requires a run-time system that is not installed.

D-34

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
I

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I ?Not a valid device

I
I

I
I
I

The device name that you gave is invalid for any of the
following reasons:
0

It is not assigned as a system-wide or user logical
name.

It is not a physical device name of any device that is
installed on your system.

The device name i·s valid, but not with this command.
For example, "INITIALIZE TT:" (you cannot initialize a
terminal).

I
I

?Not enough available memory
An attempt was made to load a executable program that is too
large to run, given the job's private maximum memory size.
Either the program must be allowed to expand above a private
maximum memory size, or the system manager must increase the
job's private memory size maximum to accommodate the
program.
?Not enough free memory to create dynamic region
There is not enough memory on the system to create a dynamic
region of sufficient size for the operation. If this is a
BACKUP, reducing the BLOCKSIZE parameter may correct the
problem.
?Number not in range <low> or <high>
You typed a number where one is allowed, but the number is
not in the valid range. The valid range is from <low> to
<high>.
I

?Number too big
You typed a number where one is allowed, but the number is
too large. Refer to the command description to find out the
largest acceptable value.

D-35

I
I

I
I
I

General RSTS/E Messages
Table D-I:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
I ?Number too small
I
You typed a number where one is allowed, but the number is
I
I

too small. Refer to the command description to find out the
smallest acceptable value.

I
I
I ?Pack-id labels don't match
I
The identification code for the specified disk pack does not
I
match the identification code already on the pack. This
I
message can occur when you try to mount or dismount a disk.
I
I
I ?Page limit exceeds queue's maximum
I
You specified a /PAGE LIMIT value in a PRINT command larger
I
than the maximum allowed for the queue.
I
I

I ?Parameter or argument too long
I
I
I
I

This message occurs if a file specification, text string, or
qualifier argument exceeds 255 characters.
.,

I %Please answer "YES" or "NO"
I
I
I

Valid responses to the given prompt are YES and NO only.

I %Please specify only a device name
I
You specified something other than a device name when only a
I
device
name was valid.
I
I
I ?PPN does not exist
I
The project-programmer number (PPN) you specified as part of
I
the job specification does not exist.
I
I
, ?PPN needed

,
I

The command you typed requires that a PPN be specified.

I
, Previous. logical name assignment replaced
,
An informational message to indicate that an ASSIGN command
I
,
redefined a previously defined user logical.

D-36

,
,
,
,
,
,
,
,
,

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

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

I
I {Print,Batch} entry <entry-number> <entry-spec> created
I
Acknowledgment message to PRINT or SUBMIT command.
I
I
I {print,Batch} entry <entry-spec> - <error text>
I
For SET ENTRY, indicates that an entry was not modified for
I
the reason stated in the error text.
?print/Batch Services already started
You issued the START/QUEUE/MANAGER command; however, the
Print/Batch Services (PBS) package is already started.
?Print/Batch services not running
You issued a command that requires action by PBS; however,
the package is not running.
{Print,Batch} queue <queue-name> assigned to server <server-name>
Acknowledgment message for ASSIGN/QUEUE command.
{Print,Batch} queue <queue-name> deassigned from server
<server-name>
Acknowledgment message for DEASSIGN/QUEUE command.
{Print,Batch} queue <queue-name> closed
Acknowledgment message for CLOSE/QUEUE command.
{print,Batch} queue <queue-name> deleted
Acknowledgment message for DELETE/QUEUE command.
%{Print,Batch} queue <queue-name> - <error text>
For SET QUEUE, indicates that a queue was not modified for
the reason stated in the error text.
{print,Batch} queue <queue-name> marked for deletion
Acknowledgment message for DELETE/QUEUE command when the
queue you specified still has entries on it. The queue is
deleted as soon as it becomes empty.
D-37

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
{Print,Batch} queue <queue-name> opened
Acknowledgment message for OPEN/QUEUE command.
{Print,Batch} queue <queue-name> started
Acknowledgment message for START/QUEUE command.
{Print,Batch} queue <queue-name> stopped
Acknowledgment message for STOP/QUEUE command.
{Print,Batch} server <server-name> {deleted,marked for deletion
Acknowledgment message for DELETE/SERVER command.
%{Print,Batch} server <server-name> - <error text>
For SET SERVER, indicates that a server was not modified for
the reason stated in the error text.
{Print,Batch} server <server-name> initialized [non-]shareable
[with forms <form-name>]
Acknowledgment message for INITIALIZE/SERVER command.
{Print,Batch} server <server-name> modified
Acknowledgment message for SET SERVER command.
{Print,Batch} server <server-name> started
Acknowledgment message for START/SERVER command.
{Print,Batch} server <server-name> stopped
Acknowledgment message for STOP/SERVER command.
Print/Batch Services started at <time>
Acknowledgment message when you issue the
START/QUEUE/MANAGER command to be,gin print/Batch Services.

D-38

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ':" - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Message and Meaning
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I Print/Batch Services stopped at <time>
I
Acknowledgment message for STOP/QUEUE/MANAGER command if no
I
jobs are being processed.
I
I
I Print/Batch Services will stop after {completing,aborting} <n>
job[s]
Acknowledgment message for STOP/QUEUE/MANAGER command if any
jobs are currently in progress.
?priority exceeds queue's maximum
You specified a priority for a PRINT or SUBMIT entry larger
than the maximum allowed for the queue.
?<privilege> privilege required
You typed a command that requires some privilege, and you do
not have it.
??Program failure in <program-name>
This message reports a problem in the software. It is
followed on the next line by an explanation of the problem.
You should verify that the failing program is correctly
installed. If necessary, you should then submit an SPR. The
SPR should show the dialogue that preceded the message, the
exact text of the message, and a list of patches that have
been installed in the failing program.
?Program PBS$:PBS.TSK does not exist
The Print/Batch Services (PBS) program was not found when
you issued the START/QUEUE/MANAGER command.
?Protection violation
This error can occur for reasons similar to the following:
o

You typed a CCL command that your system manager has
protected against general use.

You tried to run a program to which you do not have
execute access.

D-39

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
Message and Me~ning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I
I
I
I
I

You tried to read a file to which you do not have read
access.

You tried to write to or delete a file to which you do
not have write access.

If this message occurs because of a protection violation
with one of your own files, you can use the SET PROTECTION
command to change the file's protection code. (However, this
error can also occur because of other conditions.)
%Public disk mounted as private
A user with MOUNT privilege mounted a disk initialized as
public without specifying /PRIVATE, /PUBLIC, /SHARE, or
/NOSHARE. The system mounts the disk as private.
?Qualifier conflicts with file type
You specified the /APPEND qualifier and the file has RMS
attributes.
?Qualifier conflicts with parameter
You typed a parameter and a qualifier that should not be
present together. For example, with the DEASSIGN command,
you specified the /ALL qualifier and a logical name.
?Queue already assigned to server
You issued an ASSIGN/QUEUE for a queue already assigned to
the server you specified. Use the SHOW QUEUE/FULL command to
see which servers are assigned to a queue.
?Queue does not exist
You specified the name of a queue that does not exist.
?Queue is {closed,deleted}
A PRINT or SUBMIT command entry could not be created on a
queue because the qu~ue is clos~d or marked for deletion.
Use a different queue.

D-40

I
I

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

i- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

Message and Meaning

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

I
I ?Queue is privileged
I
The queue you specified in a PRINT or SUBMIT command
I
requires one or more privileges that you do not have. Use
I
1
1

the SHOW QUEUE/FULL command to display the privileges that
the queue requires.

!
?Queue manager message queue full
There is no room for additional messages to be sent to PBS
at this time. Reissue the request.
?Quoted string expected
A quoted string or character was expected and was either
missing or was not enclosed in quotes.
%Record too long, line truncated
The record on a READ command was too long. The assignment
occurred; however, onl~ the first 255 characters were
processed.
?Reserved symbol name
The user attempted to define a local or global symbol which
began with a reserved prefix of $, F$ or f$, or delete a
reserved global symbol from the symbol table that began with
the dollar sign ($).
?Backup set does not contain a valid ANSI label
The Backup set to restore is not a valid ANSI tape.
%Backup set volume label is not <volume-name>
The Backup set volume name does not match the volume name
specified by the user.
?Server already exists
You issued the INITIALIZE/SERVER command to define a server
that already exists.

D-41

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
Message and Meaning
I
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
?Server does not exist
You specified the name of a print or batch server that does
not exist. Use the SHOW SERVER command to list the defined
servers.
?Single character expected
A single character inside quotes was expected and more than
one character was supplied (for example, SET
DATA/END_OF_DATA = U$$U).
?Some file data in file <filename> may be missing
The Backup set did not contain the number of file blocks
which it was supposed to contain. If there were other
errors, then this indicates that the file is missing data.
If there are no other errors, submit a SPR with a copy of
the Backup set.
?Source device must be the same
Two different source devices were specified for the
operation.
?Speed is not allowed for <terminal>
The speed specified is not one of the speeds allowed for
this terminal in the TERSPD.SYS file.
??Stack overflow
This message indicates a system problem. The system manager
should send in an SPR, giving the dialogue that preceded the
message, the text of the message, and a list of patches that
have been installed.
?String too long
While in an expression, a string became too long to fit in
the 255 available bytes.

0-42

General RSTS/E Messages
rable 0-1:
~

I
~

General RSTS/E Messages (Cont.)

-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - -- - - - - - - - - - Message and Meaning
I
- - - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~

I
I
I

?Substitution too complex
The user's request for apostrophe substitution was rejected
because the substitution was too complex (it reached the
maximum number of substitution iterations allowed on one
command).
?Summary record not first record of Backup set
This problem indicates that the Backup set was not written
correctly. Submit a SPR including a copy of the Backup set.
?Symbol name conflicts with <symbol-name>
The user specified an assignment whose symbol name or
abbreviation point conflicted with an existing symbol
definition in the same symbol table.
?Symbol name too long
The symbol name specified by the user exceeded 255
characters.
%Symbol table almost full
This warning is issued when your local or global symbol
table has less than 100 free bytes.
??Symbol table full
You attempted to define a label or symbol when the local or
global symbol table was already full. Note that if you are
in a command procedure when your symbol table gets full, the
command procedure aborts.
?Syntax error
The command has improper syntax. This occurs when there is
not a more specific message describing the syntax error.
?THEN clause required
The action clause was missing on the IF <expression> THEN
command or on the ON <severity-level> THEN command.

D-43

I
I

I
I
I

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

-- - - - - --- - - ---- - -- - - - ---- - - - -- - - - - - - - ----- - - - - - --- - - ---------- - - - -- -;Message and Meaning
;- - - --- - - - - - - - - --- - - - -- - - - - - -- - - - - - - - - - - - - - - -- - ----- - - - ---- - - - - - -- - - -;;-

I
I ?THEN keyword required
I
The THEN keyword was missing on the IF <expression> THEN
I
command or on the ON <severity-level> THEN command.
I
I

I ?This is not the correct output volume
The volume ID of the mounted output volume does not match
the volume name specified in the /OUT_LABEL qualifier.
?Time limit exceeds queue's maximum
You specified a /TIME LIMIT value in a SUBMIT command larger
than the maximum allowed for the queue.
?Too many arguments
You used the notation /qualifier=(arg,arg, ... ) with a
qualifier that accepts only a single argument.
?Too many elements in list
In a list of file specifications or other items (separated
by commas or plus signs), you indicated more file
specifications than are allowed. For example, you exceeded
one of the following limits:
o

The DIBOL, RENAME, DELETE, and SET PROTECTION commands
allow six file specifications.

The COpy command allows six input file specifications
and one output file specification.

The PRINT and SUBMIT commands allow up to 11 file
specifications.

?Too many files or parameters
You specified too many file specifications in a PRINT or
SUBMIT command, or a parameter string in a SUBMIT command is
too long to be handled by PBS. Reduce the number of file
specifications or use a shorter parameter string.

D-44

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
?Too many logical names assigned
with the ASSIGN command, you exceeded the maximum number of
logical names. You can only assign up to four logical names
(only three logical names if any of the logical assignments
includes a PPN).
?Too many open files on unit
You specified the same magnetic tape or DEC tape drive both
as input and output files on COpy or APPEND.

I
I
I
I
I
I
I

I
I
I
I
I
I

?Too many parameters

I
I
This message occurs if you specify more command parameters
I
than the command can accept. For example, you specified more I
than eight parameters with the /PARAMETERS qualifier.
I
I
?Too many printers initialized
I
I

The device you specified could not be initialized because
the maximum number of spooling devices has already been
initialized.
?Unable to copy tape command file to disk
The user specified an indirect command file on magnetic
tape, and some error occurred when attempting to copy it to
a temporary disk file for processing.
??Unable to create DCL work file
DCL's work file for storing the user's symbol tables could
not be created on disk. The user may be over quota.
Corrective action should be taken before the user continues
processing.
??Unable to read DCL work file
The user's symbol tables could not be read in from the DCL
work file. If RSTS/E is processing an indirect command file,
then control immediately returns to the interactive level.

D-45

I
I
I

I
I
I
I

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Message and Meaning
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

?Unable to recover part of Backup set
This message indicates that BACKUP was unable to recover
part of the Backup set, after trying to use error recovery
data. There will also be other messages indicating what data
(if any) was detected to be missing.
?Unable to start Print/Batch Services
<error message>
Some external condition, as the error message on the second
line describes, prevented PBS from being started.
??Unable to write DCL work file
The user's symbol tables could not be written out to the DCL
work file. The user may be over quota. Corrective action
should be taken before the user continues processing. If
RSTS/E is processing an indirect command file, then control
immediately returns to the interactive level.
?Unbalanced parentheses
Parentheses do not match up (for example, A=((S)+6).
?Undefined label <label>
The label specified on the GOTO command does not exist in
the indirect command procedure being executed.
?Undefined symbol
The symbol name specified is not defined in the global or
local symbol tables.
?Unexpected character
A character was encountered in a qualifier or a parameter
that was not expected. For example, in SET
TERMINAL/WIDTH=80FOO, the "F" of "FOO" would be an
unexpected character.

D-46

General RSTS/E Messages
rable n-l:

General RSTS/E Messages (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -~
?Unexpected error verifying file data for file <filename>
The RSTS/E monitor reported an error in response to BACKUP's
request to verify data. Another message describing the
problem follows this message.
?Unexpected error writing to output file <filename>
The RSTS/E monitor reported an error when writing to the
specified file. Another message describing the problem
follows this message.
?Unit number required
This message occurs when you specify a device-name without a
device-number (for example, OM: instead of OMO:).
?Unsupported record structure level - record skipped
This message indicates that the version number of a record
was higher than the highest version known to BACKUP. If this
error occurs trying to restore a Backup set written by a
newer version of BACKUP on an older version of BACKUP, the
operation may not work properly. If the version of BACKUP
writing the tape is older or the same as the one doing the
RESTORE, submit an SPR with a copy of the Backup set that
generated the error.
?User macros nested too deep
There were more than 50 nested user macros or a user macro
called itself.
%Valid qualifiers are /INITIALIZE- and /NOINITIALIZE
You entered a qualifier other than /INITIALIZE and
/NOINITIALIZE and those were the only valid qualifiers.
?Verification
<tilename>

failu~e

for directory information for file

There was a difference between the directory information
(file size, file flags, etc) stored on the Backup set and in
the directory structure.

0-47

General RSTS/E Messages
Table D-l:

General RSTS/E Messages (Cont.)

~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

Message and Meaning

~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --i-

?Verification failure for file attributes for file <filename>
There was a difference between the file attributes stored on
the Backup set and in the directory structure.
?Verification failure for file data for file <filename>
The file data stored on the Backup set is different from the
file data stored on disk.
%Volume has not been initialized
The initialization request failed, so the output device is
not in an initialized state. BACKUP reprompts for an input
device.
?Wildcard entry name not allowed
The command you specified does not allow wildcard entry
names. Specify the name of a single entry instead.
?Wildcards not allowed
You included a wildcard in a file specification, where
wildcards are not allowed.
?Wildcard PPN not allowed
The command you specified does not allow wildcard PPNs.
Specify the name of a single PPN instead.
?Wildcard queue name not allowed
The command you specified does not allow wildcard queue
names. Specify the name of a single queue instead.
%XOR block missing from Backup set
If this error occurs without any other messages, submit an
SPR with a copy of the Backup set. If there are other
messages, this has probably occurred because a block of the
Backup set was unreadable.

D-48

General RSTS/E Messages
Table D-1:

General RSTS/E Messages (Cent.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - '- - - - - - - - - - - - - - - - - - - - - - - - +
I
Message and Meaning
I
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -, - - - - - - - - - - - - - - - - - - - - - - - - - - -+

%XOR verification failed - group may be unreliable
This message indicates that BACKUP, during a verify
operation, concluded that the recovery data for a group of
data blocks does not match the data found in the blocks. If
this was not accompanied by other messages, submit a SPR. If
it was, consider the data in the Backup set to be
unreliable.
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

D-49

.. r

Appendix E
SAVE/RESTORE System Program

The RSTS/E SAVE/RESTORE system program is a disk backup and copy
utility that has four operational functions:
o

SAVE backs up a disk to tape or disk.

RESTORE recreates a disk from tape or disk.

IMAGE makes a copy of a disk.

IDENTIFY extracts label information from a SAVE/RESTORE
volume or RSTS/E disk.

When to Use SAVE/RESTORE
SAVE/RESTORE and BACKUP perform similar system functions but differ in
their objectives.
SAVE/RESTORE provides a nonselective, fast-volume
restore and copy capability that requires few operator responses
during the operational dialogue. Unlike BACKUP, SAVE/RESTORE
processes entire volumes only and does not allow selective file
transfers. When SAVE/RESTORE finds bad blocks, it requires no
operator intervention.
For these reasons, use the SAVE/RESTORE
program when you need to:
o

Create a fast,

reliable copy of an entire RSTS/E disk

Make a fast copy to a disk containing bad blocks that may not
be reflected in the BADB.SYS file

Make a recdvery medium (bootable) for a system disk in-case
of catastrophic errors

E-l

SAVE/RESTORE System Program
Definitions of SAVE/RESTORE Terms
To understand this appendix, you should know these terms:
o

SAVE format: The format of the output written by a SAVE
operation and read by a RESTORE operation.

SAVE Set: The set of magnetic tapes or disks created by a
SAVE operation. A SAVE Set must be composed entirely of
disks or tapes; it cannot be a combination of the two device
types.
However, you can mix different drive types within one
set, for example, two RK05's and one RK06.

SAVE volume: One of the magnetic tapes or disks of a SAVE
Set.

SAVE Set Name: One- to six-alphanumeric characters used to
identify a SAVE set.
By default, the SAVE set name is the
same as the Pack ID from which it was created.
However, you
can specify another name for the SAVE Set.

LIKE Disks: Like disks are units of the same device size
(that is, the same number of data blocks).
SAVE/RESTORE
considers the following devices alike:
Two RP06 disks
An RM02 and an RM03
An RP04 and an RP05
An RK05 (RK05J) and one unit of an RK05F
Therefore, if you copied an RM02 to a SAVE Set, the SAVE Set
can later be restored either to an RM03 or another RM02.

Running SAVE/RESTORE
You use the SAVE/RESTORE program off line while running the system
initialization code INIT.SYS.
In reply to the INIT OPTION prompt,
type SAVRES.
SAVE/RESTORE asks for the current date and time and then
responds with the SAV/RES FUNCTION prompt.
For example:
Option: SAVRES
DD-MMM-YY? 14-MAY-85
HH:MM? 12:15
SAV/RES Function:
E-2

SAVE/RESTORE System Program
Note
You must run SAVE/RESTORE off line to copy (SAVE or
IMAGE) or restore (RESTORE) the ~ystem disk with
which you are currently running on line.
You can also use SAVE/RESTORE on line, during timesharing. When you
do, you must not logically mount the RSTS/E disk(s} on which
SAVE/RESTORE operates.
This ensures the integrity of the data on the
disk(s}.
To run SAVE/RESTORE on line, type RUN $SAVRES.
SAVE/RESTORE
then prints its program prompt:
$ RUN $SAVRES<RET>
SAV/RES Function:
After the SAV/RES FUNCTION prompt appears, as a result of running
SAVE/RESTORE either off line or on line, you are under the control of
SAVE/RESTORE and are ready for restore processing.
Next, select from Table E-l one of the four operational functions:
o

SAlVE]

RE[STORE]

IM[AGE]

ID[ENTIFY]

Unless you need to exit SAVE/RESTORE (by pressing LINE FEED, or
entering CTRL/Z) or need further help (by typing HE[LP] or pressing
the RETURN key), type one of the four functions on your terminal in
response to the SAV/RES FUNCTION prompt.
For example:
SAV/RES Function: RESTORE<RET>
This starts the SAVE/RESTORE program, which immediately prints the
first of .several dialogue questions.
The section "SAVE/RE~TORE
Dialogue" contains sample dialogues for each of the operational
functions.
Table E-l lists the possible responses to the SAVE/RESTORE prompt.

E-3

SAVE/RESTORE System Program
Table E-l:

SAVE/RESTORE Functions

+ - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
.1
Function
I
Description
I
+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I SAlVE]
I

I
I Creates a copy of a RSTS/E tile-structured disk. The
I SAVE function backs up to disk or tape.
I
I Recreates a RSTS/E file-structured disk from a SAVE
I Set.

RE[STORE]

I Copies a RSTS/E file-structured disk to a like disk.

IM[AGE]

ID[ENTIFY]

Prints label information and other volume
characteristics of a SAVE volume or a RSTS/E
file-structured disk.

HE[LP]

Prints a table of SAVE/RESTORE functions.

Exits the SAVE/RESTORE program. If you run
SAVE/RESTORE with a RUN command, pressing LINE FEED
returns you to your keyboard monitor. If you are
running SAVE/RESTORE off line with INIT.SYS, pressing
LINE FEED returns you to the INIT OPTION prompt.

RET

Displays the "Type HELP for help" message on your
terminal.

CTRL/C

Produces the same result as pressing the LINE FEED
key.

CTRL/Z

Produces the same result as pressing the LINE FEED
key.

other

Produces the same result as pressing the RETURN key.

+- - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - ~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Your response to the SAV/RES FUNCTION prompt determines the type of
dialogue SAVE/RESTORE performs. You can respond to the prompt in
several ways:
o

With the function name, such as SAVE or RESTORE, or by
pressing a key such as RETURN, as shown in Table E-l.
If you
enter only a function, the full dialogue follows.
See the
section "SAVE/RESTORE Dialogue."

With the function name and various switches.
SAV/RES Function:

For example:

SAVE/EXP:lO-MAY-86

If you include switches with the function, the dialogue
E-4

SAVE/RESTORE System Program
questions follow only for the devices to be used and the
unspecified switches.
See the following section.
o

With a full function command line.

For example:

SAV/RES Function: IMAGE DMl:=DMO:MYPAK/VER/NOERR
If you enter a complete command line, SAVE/RESTORE does not
ask any dialogue questions.
See the section "Full Function
Command Line."
SAVE/RESTORE prints messages on your terminal to tell you its status.
Some messages are for information only; other messages are error
conditions that may require your attention during the dialogue, mount,
transfer, or verification phases of SAVE/RESTORE.
When the program finds an error during a dialogue or mount operation,
it asks you to correct the problem and to retype the appropriate
command.
Such errors never affect the integrity of the data being
transferred.
However, errors that occur while SAVE/RESTORE is transferring or
verifying data can jeopardize data.
In this case, SAVE/RESTORE
resolves the problem, aborts the run, or asks you whether to continue
or to abort the program.
The program gives you information to help
you protect your data by printing informational messages and error
messages on your terminal.
Finally, SAVE/RESTORE prints an optional summary report about SAVE,
RESTORE, or IMAGE operations at the end of the run.
This report
describes:
o

The operation performed

Device information

Start date and time statistics

Run total statistics, which includes the number of errors
found during the operation.

SAVE/RESTORE Switches
You can include SAVE/RESTORE switches in a function response or in a
full function command line.
There are two types of switches:
o

The expiration and verification switches correspond to
questions in the SAVE/RESTORE dialogue and have default
settings.
If you do not include the switches in a function
E-5

SAVE/RESTORE System Program
response, the dialogue asks you for that information. For
example, if you do not include the /EXPIRATION switch, the
dialogue asks:
Expiration Date<DD-MMM-YY>?
If you include one of the switches in a function response,
SAVE/RESTORE does not ask- the corresponding question but does
ask the question for the switch you did not specify. For
example, if you include the /EXPIRATION switch but not
/VERIFY, SAVE/RESTORE does not prompt you for an expiration
date but does ask the verification question.
If you do not include the switches in the full function
command line, SAVE/RESTORE assumes the default settings. For
example, if you do not include the /VERIFY switch,
SAVE/RESTORE assumes /NOVERIFY.
This means if you do not
explicitly include the /VERIFY switch in a full function
command line, SAVE/RESTORE does not compare the data
transfer.
o

The /STATS and /ERROR switches have no corresponding dialogue
questions but do have default settings.
Therefore, if you do
not specify these switches in a function response or command
line, SAVE/RESTORE assumes the default settings.

Table E-2 lists the allowable SAVE/RESTORE switches
Table E-2:

SAVE/RESTORE Switches

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
Default and Description
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

EX[PIRATION][:date]
NOEX[PIRATION]

EXPIRATION
SAVRES warns you of any attempt to overwrite
the volume(s) any time before the specified
date. The date argument is the date after
which you may overwrite the destination
volume. You can use this switch only for a
SAVE operation.
If you specify /EX[PIRATION] with no date
argument, SAVRES uses one year after the
current date as the the expiration date.
If you specify /NOEX[PIRATION], SAVRES uses
the current date as the expiration date.

E-6

SAVE/RESTORE System Program
Table E-2:

SAVEjRESTORE Switches (Cont.)

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Switch
I
Default and Description
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - _. - - - - - - - - - - - - - - - - - - - - - - - --+

VE[RIFY]
NOVE[RIFY]

NOVERIFY
I
You can use this switch only for a SAVE,
I
RESTORE, or IMAGE operation. If you specify
I
the /VE[RIFY] switch, SAVRES compares the
I
volume(s) to make sure that the transfer was I
accurate.
I

ST[ATS]
NOST[ATS]

STATS
SAVRES does not automatically print a
summary report at the end of a run, unless
you specify the /ST[ATS] switch with either
a function response or a full function
command line. See the section "SAVRES
Summary Report. II

ER[ROR]
NOER[ROR]

I
I
I
I
I
I
I
I
I
ERROR
I
If you do not include the /ERROR switch and
I
a nonfatal error occurs during a SAVRES run, I
SAVRES prints an error message and continues I
processing. This is the default condition.
I
I

You must specify explicitly the /NOERROR
I
switch if you want SAVRES to print an error
I
message and terminate as a result of any of
I
the errors described in Table E-12.
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

SAVE/RESTORE Dialogue
The SAVE/RESTORE dialogue begins after you run the SAVE/RESTORE
program and respond to the SAV/RES FUNCTION prompt.
If you type SAVE,
RESTORE, IMAGE, or IDENTIFY, the program asks a set of dialogue
questions, which have either a short or a long form.
The short form
appears automatically while the long form prints only if you press the
RETURN key in response to the short form question.
The long form
gives you information to help you answer the questions.
Tables E-S
through E-8 show the text of each of the long form questions in
quotation marks (").
Some of the questions have default values which the program prints in
angle brackets.
You can select the default value by pressing the LINE
FEED key or by typing the proper default response." If you press LINE
FEED in response to a question that has no default, SAVE/RESTORE
repeats the question.
E-7

SAVEjRESTORE System Program
There are two valid responses to a SAVE/RESTORE program that can
change its operating status:
o

CTRL/Z

CTRL/C

If you enter CTRL/Z at any point in the dialogue, SAVE/RESTORE returns
to the previous question. A CTRL/C response aborts the run
immediately and returns you to the INIT OPTION prompt if you are
running off line under the control of the INIT.SYS program, or to your
keyboard monitor prompt if you are running SAVE/RESTORE on line.
SAVE/RESTORE automatically returns to the SAV/RES FUNCTION prompt
after the execution of a specified function when you are operating
either on line or off line. Exit from the INIT version of
SAVE/RESTORE to the OPTION prompt by pressing LINE FEED.
Type CTRL/Z
to the SAV/RES FUNCTION prompt to exit the online version of
SAVE/RESTORE.

SAVE Volumes
You can perform SAVE/RESTORE operations on disks and tapes.
The SAVE
Set, a set of tapes or disks created from a SAVE operation, cannot
include both disks and tapes. However, the SAVE Set can include one
or more volumes of the same class.
In other words, a tape volume SAVE
Set could consist of two MM devices and one MT device or one RP04 and
two RKOS disks.
A legal SAVE disk device is any disk supported by RSTS/E that meets
the following requirements:
o

All disks must be formatted; that is, contain sector and
track information.

All disks used by the online version of SAVE/RESTORE must
have a valid RSTS/E file structure; that is, the disk device
must be formatted by DSKINT prior to its use. The one
exception to this rule is the disk you have used as a SAVE
Set volume.
It does not have the RSTS/E file structure (and'
cannot be logically mounted) but can be used for SAVE/RESTORE
operations.

The first 16 blocks plus the device cluster size blocks on a
disk must not contain any bad blocks.

A RSTS/E output disk can contain no more than 161 bad
clusters (the RSTS/E limit).

E-8

SAVEjRESTORE System Program
Magnetic tape is the only valid SAVE/RESTORE tape medium; DECtape and
cassette are unacceptable.
The following statements define what
constitutes a valid tape in the SAVE/RESTORE package:
o

The magnetic tape must be long enough to contain:
The SAVE Set label and header information
A bootstrap
INIT.SYS that is on the first volume only
Two copies of the RSTS/E disk file SATT.SYS
At least 16 blocks of data from the RSTS/E disk

A bad block is considered to be the end-of-tape (EDT) volume
during the SAVE operation.

The default density is the lowest density allowed by the
drive on which the first volume is mounted.
Later volumes
cannot be written at any other density.
You must make sure
the density used on the first volume is compatible with all
other tape drives you plan to use.

Device Specifications
SAVE/RESTORE requires you to use device specifications as responses to
several dialogue questions.
The general format is:
<device>[:[<id>]][<switch(es»]
Device is a two-character device type (for example DU) followed by a
single-digit unit number in the range 0 to 7.
The identification can
be either a SAVE Set Name or a disk pack identification; the switches
are any of those from Table E-3.

E-9

SAVE/RESTORE System Progr~m
Table E-3:

SAVE/RESTORE Device Specification Switches

+ - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - '- -' - +

Switch

Description

+ - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - -: - - - - - - - - - - - - - - - - - - - - - - - - ,- - - - - +

I
I /SCR[ATCH]
I
I
I
I
I
I
I
I
I
I
I /DEN [ S I TY] : [ 800]
I [1600]
I
I
I

The /SCRATCH switch is legal only on an output
volume device specification. If you use the
/SCRATCH switch, SAVRES by-passes most volume
label checking. The program always checks the
label to see if an output volume contains a
SAVE Set written at the current density and
make sure that it is not a volume from the
SAVE Set currently being written. It also
checks destination disks for bad block
information.
The /DENSITY switch is legal only for magnetic
tape. With this switch, you can specify the
density at which the tape is to be written or
read. If SAVRES cannot read the tape at the
specified density, it tries to read the tape
,at the other legal density setting.

+- - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Privileges Required
You need RDNFS, WRTNFS, and SYSMOD privileges to gain read/write
non-file-structured access to a disk. If a device is restricted, you
also need DEVICE privilege to gain access to that device.

Checking the Input Volume
SAVE/RESTORE checks the input volume before transferring any actual
data and warns you of any problem it foresees in saving, restoring, or
copying the volume. All of the input volume error messages that are
printed at this point are warning messages only; you can recover from
them by following appropriate procedures.
Table E-4 lists and describes the error messages that result from a
problem with an input volume.

E-IO

SAVE/RESTORE System Program
Table E-4:

SAVE/RESTORE Input Volume Error 11essages

+ - -,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +

Message and Meaning

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

I
I
I
I
The input disk has very few clusters that are not allocated. I
There must be at least as many good pack clusters on an
I
output RSTS/E disk as there are clusters to be transferred
I
from the original input disk. This message indicates that
I
you may encounter problems copying or restoring the disk.
I
I
Type NO or press RETURN to return to the previous device
I
prompt. If you type YES, SAVRES proceeds with the SAVE or
I
IMAGE operation. The program also checks the output volume
I
to see if the transfer can be made (see the section
I
"Checking the Output Volume"). At this point, you may want
I
to free up space on the input disk by deleting unnecessary
I
files. This increases your chances of eventually completing I
a successful RESTORE.
I
I
%%% This is not the correct volume.
I
I
The pack ID or SAVE Set Name you included with the input
I
device specification does not match the name already written I
on the volume. If SAVRES finds that the names do not match,
I
it prints the warning message and then issues the input
I
device prompt again. A dismount request follows the warning I
message and lists useful information from the volume label
I
of a SAVE Set or a RSTS/E file-structured disk.
I
I
%%% This volume has no label.
I
I
The input volume is not a RSTS/E disk or a SAVE Set. SAVRES I
prints the input device prompt again after issuing the
I
warning message.
I
I
%%% Input disk should be rebuilt.
I
I
You removed a disk from a drive without logically
I
dismounting it and then attempted to -remount it. Perform the I
clean operation with the ONLCLN program or the REFRESH
I
option of INIT.SYS. See the RSTS/E System Installation and
I
Update Guide for information on REFRESH. See the RSTS/E
I
utilities Reference Manual for information on ONLCLN.
I

%%% Input disk has only nn% free clusters.
Mount it anyway <NO>?

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+

E-ll

SAVE/RESTORE System Program
Checking the Output Volume
SAVE/RESTORE checks the output volume before restoring or copying a
RSTS/E disk to make sure that each operation ends with the least
chance of error. After checking the output volume, SAVE/RESTORE
displays messages about the expiration date, the label, and the
available data space on the destination device.
Some of the messages
are only for your information; the rest warn you of serious output
device problems.
When the expiration date of an output volume, labeled as a SAVE Set,
has passed, SAVE/RESTORE prints this series of messages and proceeds
to the next dialogue question:

*** The volume on dev: is SAVE Set <xxxxxx>
Density
nnn
Creation date : day-of-week, dd-mmm-yy
Expiration date
: day-of-week, dd-mmm-yy
If you decide not to use the expired date volume, enter CTRL/Z to
return to the TO DEVICE output question.
If the output volume is labeled as a SAVE Set and its expiration date
has not passed, SAVE/RESTORE prints this series of messages:

*** The volume on dev: is SAVE Set <xxxxxx>
Density
: nnn
Creation date
: day-of-week, dd-mmm-yy
Expiration date: day-of-week, dd-mmm-yy
%%% Its expiration date has not passed
Mount it anyway <NO>?
If you type NO or press LINE FEED to the mount question, SAVE/RESTORE
returns to the previous device prompt.
SAVE/RESTORE goes to the next
question if you type YES.
If you press RETURN, SAVE/RESTORE prints:

*** This is your last chance to prevent the
*** loss of any data on the output volume.
Mount it anyway <NO>?
When the output volume you are using is labeled a RSTS/E disk,
SAVE/RESTORE prints the message:

*** The volume on dev: is a RSTS disk

*** Pack ID is <xxxxxx>
*** Pack will be reinitialized

Mount it anyway <NO>?
If you type NO or press LINE FEED, SAVE/RESTORE returns to the
previous output prompt. A YES response indicates you want to use the
present volume.

E-12

SAVEjRESTORE System Program
If you restore (RESTORE) or copy (IMAGE) a disk, SAVE/RESTORE checks
whether the total number of clusters on the output disk minus the
known bad blocks is greater than or equal to the number of allocated
clusters on the original source disk.
If there is not enough space
and the transfer cannot be made, it prints the following message and
then returns to the previous device prompt:
%%% Too many bad blocks on output disk.
However, if the program decides there are very few free blocks, it
prints:
%%% Only nn% of the output disk clusters are available for
relocation.
Mount it anyway <NO>?
You must decide whether the number of free clusters is large enough to
permit a successful SAVE/RESTORE operation.
If you decide it is not,
type NO or press LINE FEED to return to the output prompt. Type YES
if you want SAVE/RESTORE to continue the operation.
Note
Whenever you get this warning message, DIGITAL
recommends you use another disk for output. If you
do not, there is a greater than normal chance the
operation will not succeed.
SAVE/RESTORE normally transfers each allocated pack cluster from the
original source disk to the same cluster on the output RSTS/E disk.
If SAVE/RESTORE finds the output cluster is bad, it tries to relocate
the data.
If the cluster size of the item being moved is larger than
the pack cluster size, there must be enough contiguous free pack
clusters on the output disk to accommodate the entire source cluster.
If there is not, SAVE/RESTORE aborts the operation.
If the specified output is not a RSTS/E disk, the program prints the
new SAVE Set Name and proceeds without further notice.
It does not
check the output volume label if you specified the /SCRATCH switch,
except to determine whether it is a volume of the SAVE Set that is
currently being created.
It always attempts to recover bad block
information from a RSTS/E file-structured and SAVE disk.

E-13

SAVE/RESTORE System Program
Saving a RSTS/E Disk using the SAVE Dialogue
The SAVE function backs up an entire RSTS/E-formatted disk to either
tape or disk.
The output volumes created by this operation are
collectively called the SAVE Set and are written by SAVE/RESTORE in
the SAVE format.
You can recreate the original disk only by using the
RESTORE operation. You cannot use other RSTS/E software, such as
BACKUP or PIP.SAV to restore a SAVE Set. Note that you must use SAVE
if the output medium is different from the input medium.
Once you determine that the disk you are to save and the output SAVE
Set device(s) are valid media, type SAVE to start the SAVE dialogue
described in Table E-S.
Note
When SAVE/RESTORE creates a SAVE Set, it includes an
extra set of directory blocks on the output volume in
case some directory blocks are found to be bad during
a RESTORE operation.
These additional blocks are
r~flected in the total block count for a SAVE Summary
Report. Because the extra blocks are needed only
when bad blocks are found during a RESTORE operation,
it is unnecessary for SAVE/RESTORE to transfer these
blocks to the restored volume.
Thus, you will notice a discrepancy between the
number of blocks transferred for a SAVE operation and
the number transferred during a RESTORE.
Furthermore, because the extra directory blocks are
not transferred to the restored volume, under certain
circumstances you may restore your data to one less
volume than existed in the SAVE Set.
The Pack ID of the input disk is the default SAVE Set Name of the
output volumes. After you answer the From RSTS Disk? question,
SAVE/RESTORE tells you the output SAVE Set Name it intends to use.
The general format is:

*** Pack 1D/default SAVE Set Name is <xxxxxx>
If you do not want the output volume(s) to have this SAVE Set Name,
specify a different Pack ID in the <devspec> response to the To
Device? question. After you select the 1D and answer the question,
SAVE/RESTORE prints:

*** SAVE Set Name is <xxxxxx>
SAVE/RESTORE warns you if the output volume contains a SAVE Set that
has an expiration date that has not passed. You can proceed or
respecify the output volume (see "Checking the Output Volume").

E-l4

SAVE/RESTORE System Program
Table E-S lists the SAVE dialogue questions. An example of a
SAVE/RESTORE procedure follows the dialogue description.
Table E-5:

SAVE Dialogue Questions

+- - - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I From RSTS Disk?
I
I
I
I
I

<devspec>
Data is transferred from the specified
disk. If you include a Pack ID in the
device specification, SAVE/RESTORE
checks whether it matches the one on the
disk. When it does not, the program
prints a warning message (see section
"Checking the Input Volume") and prints
the From RSTS Disk? question again.
Type 2 characters to specify the input
device type, followed by a single digit
(0-7) to specify the unit number.
Include a Pack ID if you want
SAVE/RESTORE to make sure it matches the
one on the volume. The disk must be
physically (but not logically) mounted
and should ~e write-locked.

To Device?

<devspec>
All data is transferred from the
previously specified input disk to this
tape or disk. If you do not specify a
SAVE Set Name in the <devspec>,
SAVE/RESTORE gives the SAVE Set the same
name as the input disk.
Type 2 characters to specify the output
device type, followed by a single digit
(0-7) to specify the unit number.
Include a SAVE Set Name if you want to
override the default. This drive should
have a SCRATCH volume mounted, and mustbe write-enabled.

E-l5

I
I
I
I
I

SAVE/RESTORE System Program
Table E-5:

SAVE Dialogue Questions (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - - - - - +
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Expiration Date
<DD-MMM-YY>?

<DD-MMM-YY>
This is the dia+ogue form of the
/EXPIRATION switch (see section
"SAVE/RESTORE Switches"). If you do not
specify a date, SAVE/RESTORE creates an
expiration date for the SAVE Set that is
one year from the date that it was
created.

I
I
I
I
I
I
I
I

Type the desired expiration date or
press the LINE FEED key to accept the
date printed.
Verify (Yes or NO)
<NO>?

Y[ES] or N[O]
This is the dialogue form of the /VERIFY
switch (see section "SAVE/RESTORE
Switches"). If you type YES, the output
is then compared to the input at the end
of each volume of the SAVE Set.
Type YES if you want SAVE/RESTORE to
compare the input and output volumes at
the end of each output volume. Type NO
or press LINE FEED if you do not want
SAVRES to perform this verification.

Proceed (Yes or No)?

Y[ES] or N[O]
This question lets you either double
check your dialogue responses, and abort
the operation if you have made any
errors, or proceed with the SAVE
operation.
Type YES to proceed with the operation.
Type NO to abort and return to the
SAV/RES Function: prompt.

+ - - - - - - - - -, - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
The following SAVE example shows the backup of an RM03 disk to tape.
The letters are keyed to the explanation that follows this sample.
The SAVE steps are:
1.

Physically mount the RM03 source disk on drive DR1:,
write-locked.

E-16

SAVEjRESTORE System Program

Physically mount the destination tape on drive MMl:,
write-enabled.

Type RUN $SAVRES and then press RETURN.

RUN $SAVRES<RET>

SAV/RES Function: SA<RET>

From RSTS disk? DRl:<RET>

*** Pack ID/default SAVE Set Name is JOEM
d

To Device? MMl:SAVSET<RET>

*** SAVE Set Name is SAVSET
e

Expiration Date <10-May-85>? 10-May-86<RET>

Verify (Yes or No) <NO>? <RET>

Proceed (Yes or No)? Y<RET>

*** Initializing first SAVE volume
*** Begin SAVE from DRl: to MM1: at 08:07 PM
h

Dismount Device:
Set Name:
Seq #:
Density:
Creation date:
Expiration date:

MMl:
SAVSET
1

800
Friday, 10-May-85
saturday, 10-May-86

Please label this volume
i

Mount volume # 2 of SAVE Set SAVSET
Device? MM2<RET>

Proceed (Yes or No)? Y<RET>

*** Begin SAVE from DR1: to MM2: at 08:14 PM
Dismount Device:
Set Name:
Seq #:
Dens"i ty:
Creation date:
Expiration date:

MM2 :
SAVSET
2

800
Friday, 10-May-85
saturday, 10-May-86

Please label this volume
E-17

SAVE/RESTORE System Program
--- SAVE operation completed at 08:22 PM
Summary Report

SAVE of DRl:JOEM to SAVE Set SAVSET
Input Device:
Pack 10:
Pack C1ustersize:
Creation date:
Output Device:
Set Name:
# of volumes:
Density:
Creation date:
Expiration date:

OR1:
JOEM
8

Saturday, 6-Apr-85
Magtape
SAVSET
2

800
Friday, 10~May-85
Saturday, 10-May-86

SAVE started on Tuesday, 10-May-85, at 08:07 PM
Run Statistics

Transfer Totals:
Total of 55192 blocks transferred
Error Totals:
Total of

o new bad blocks encountered on source.

Timing Totals:

Total elapsed time:

0 hrs. ,

14 mins.,

41 secs.

Total wait

time:

0 hrs.,

0 mins.,

19 secs.

Total process time:

0 hrs. ,

14 mins. ,

22 secs.

SAV/RES Function: <CTRL/Z>
$

The explanation of the SAVE example follows:
a

Type RUN $SAVRES, then press RETURN to run the SAVE/RESTORE
program.

After you press RETURN, SAVE/RESTORE prints its initial program
prompt. Because you need to perform a backup operation of an
RM03, you select the SAVE function of SAVE/RESTORE by typing SA
and pressing RETURN.

SAVE/RESTORE asks for the device name and unit number of the
E-18

SAVE/RESTORE System Program
disk from which you are extracting data.
indicating unit 1 of the RM03 disk.

You respond with OR1:,

As an option, you could have included a Pack 10 with the device
specification.
If you had, SAVE/RESTORE would have compared
your Pack 10 response to the 10 currently on the disk.
By not
specifying a Pack 10, SAVE/RESTORE accepts the current 10.
After you terminate your response to this question by pressing
RETURN, the program shows you the name of the SAVE Set.
d

You specify the medium to which SAVE copies the input data.
Because you want the SAVE Set to reside on tape, you type MM1:.
Rather than allow SAVE to give the SAVE Set the same name as the
input disk, you give the SAVE Set its own.
If you assign the
input and output media separate names, you can better
differentiate their identity (with IDENTIFY) at a future date.
Once you end your response, SAVE stores the name you specified
on the output medium and then prints the SAVE SET NAME IS SAVSET
message.

SAVE creates a default expiration date equal to the current date
plus one year. This represents the date after which you can
write over the data. Rather than accept the default by pressing
LINE FEEO, you specify your own date and press RETURN.

You choose not to have SAVE/RESTORE verify the transfer. A YES
or Y response causes SAVE to perform a verify pass after it
completes the data transfer process.
In the verify pass, SAVE
compares the input data with the data it transfers to the output
medium. As an alternative, if you know that you need to verify
the transferred data, you can attach the /VERIFY switch to the
SAVE/RESTORE function and thus suppress the VERIFY (YES or NO)
question.

You have made no errors in the dialogue sequence; therefore, you
can type Y to have SAVE proceed with the operation. Because no
default exists for this question, you must type either a YES or
a NO response.
Once you terminate your answer, SAVE notifies
you that it is initializing the first SAVE volume. Only the
first volume of the SAVE Set is initialized. When that
operation is complete, SAVE prints a message indicating that the
transfer process has begun, which devices are involved, and the
time the operation began~

The dismount report summarizes the label information found on
the initial SAVE Set volume.
If SAVE/RESTORE requires another
volume, it asks you to mount the next volume in the SAVE Set
after the first volume is ~xhausted.

You respond to the OEVICE question with the device name and unit
number of the second SAVE Set volume, then press RETURN.
E-19

SAVE/RESTORE System Program
j

Again, you have the option to proceed or to abort the operation.
Because there is no reason to abort, you type Y and press RETURN
to proceed. SAVE then notifies you, as it did for the first
volume, that the SAVE operation has begun, that the data is
being transferred, and that 08:14 was the time the SAVE
operation began. As soon as SAVE finishes the transfer, it
issues the dismount message for the second volume of the SAVE
Set, informs you that the SAVE operation is complete, and the
time it finished.

The SAVE Summary Report appears by default and can only be
suppressed by attaching the /NOSTATS switch (or by making
/NOSTATS the default) to a SAVE/RESTORE function.
The report
includes the Pack ID and SAVE Set names, label information for
both the input and output volumes, and the date of the SAVE
operation.

The Run Statistics Report prints the number of blocks
transferred, the number of bad blocks encountered, and elapsed
times. Note that the blocks transferred includes an extra set
of , directory blocks stored at the end of the SAVE Set. The
additional set of directory blocks are included to make sure
that SAVE/RESTORE has a valid directory to read when' it attempts
to restore from the SAVE Set.

When the SAVE operation is complete, SAVE/RESTORE returns to its
initial SAV/RES FUNCTION prompt.
If you want to return to your
keyboard monitor prompt (DCL in this example), enter CTRL/Z.

Restoring a RSTS/E Disk using the RESTORE Dialogue
To recreate a RSTS/E file-structured disk from a SAVE Set, you must
perform the RESTORE operation. Because SAVE/RESTORE writes the SAVE
Set in the SAVE format, no other RSTS/E software can perform this
rebuild process. Before transferring any data, SAVE/RESTORE tries to
extract bad block information from the destination disk and, if it
finds any bad blocks, incorporates them into the new BADB.SYS file.
The SAVE/RESTORE program may find bad blocks during a RESTORE run. If
it does, it scans the SATT.SYS file to determine if there is a place
where the block corresponding to a bad block can be relocated.
If a
large enough area exists on the destination disk, the program simply
moves the data to the new location and modifies the directory
information accordingly.
The relocat~on of b16cks may require RESTORE to change a file's
characterrstics.
For example, this can occur if the program finds a
bad cluster while transferring a contiguous file.
To relocate the
cluster that falls on the bad block, SAVE/RESTORE must make the file
/

/
E-20

SAVEjRESTORE System Program
noncontiguous.
Changes of this type can cause problems, but RESTORE
preserves the data and informs you of these adjustments.
The operation ends if there is no way RESTORE can relocate the data
cluster. This can occur if:
o

No unallocated pack cluster remains on the disk

The file cluster size is larger than the pack cluster size
and there is not an equivalent number of contiguous pack
clusters left on the disk

Normally, SAVE/RESTORE uses the name of the input SAVE Set as the Pack
ID of the output volume. After you answer the From Device? question,
SAVE/RESTORE prints a message showing you the name it plans to use.
The general format is:

*** SAVE Set name/Default Pack ID is xxxxxx
After you successfully respond to the TO RSTS DISK question,
SAVE/RESTORE prints the message:

*** Pack ID is xxxxxx
Table E-6 lists the RESTORE dialogue questions. An example of a
RESTORE procedure follows the dialogue description.
Table E-6:

RESTORE Dialogue Questions

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
1
Question
1
Response and Description
1
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
1

From Device?

<devspec>
1
Data is transferred from the specified
1
device. If you include a SAVE Set Name in 1
the device specification (see section
1
"Device Specifications"), SAVE/RESTORE
1
checks whether it matches the name on the 1
device. If it does not, the program
,I
prints a warning message (see section
1
"Checking the Input Volume") and prints
1
the From Device? question again.
1
1

Type 2 characters to specify the input
device type, followed by a single digit
(0-7) to specify the unit number. Include
a SAVE Set Name if you want SAVE/RESTORE
to make sure it matches the one on the
volume. The device must be physically
mounted and write-locked.
E-2l

1
1

1
1
1

SAVE/RESTORE System program
Table E-6:

RESTORE Dialogue Questions (Cont.)

+ - - - - - - - - - - - - - - - - - ,- - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I To RSTS Dx: Disk?

<devspec>
Data from the previously specified SAVE
Set is restored to this disk. If you
include a Pack 10 in the device
specification, it becomes the Pack ID of
the restored disk. Otherwise,
SAVE/RESTORE uses the SAVE Set Name
(which may also be the Pack 10 of the
original source disk). Physically mount
and write-enable the disk.
Type 2 characters to specify the output
device type, followed by a single digit
(0-7) to specify the unit number. Include
a Pack ID if you want to override the
default. This drive should have a SCRATCH
volume mounted, and must be
write-enabled.

I Verify(Yes or No)<NO>?

Y[ES] or N[O]
This is the dialogue form of the /VERIFY
switch. If you type YES, SAVE/RESTORE
compares the output with the input at the
end of each input volume to make sure the
volumes are equivalent.
Type YES if you want SAVRES to compare
the input and output volumes at the end
of each input volume. Type NO or press
LINE FEED if you do not want SAVRES to
perform this verification.

Proceed(Yes or No)?

Y[ES] or N[O]
This question lets you either double
check your dialogue responses and abort
the operation if you have made errors, or
proceed with the RESTORE operation.
Type YES to proceed with the operation.
Type NO to abort and return to the
SAV/RES Function: prompt.

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

E-22

SAVEjRESTORE System Program
Note
If you are using the output of a RESTORE operation as
a system disk, you must use the INIT.SYS INSTALL
option to reinstall the desired monitor Save Image
Library (SIL). You must also reenter any necessary
HAROWR suboptions (such as changing Hertz) because
the INSTALL option clears various items set up by the
HAROWR suboptions. This procedure is necessary
because a disk can be saved with SAVE from one system
disk and restored with RESTORE on a system with a
different hardware configuration.
The following RESTORE example shows the restoration of an RM03 disk
from the tape SAVE Set created in the previous example. The letters
are keyed to the explanation that follows this sample.
The RESTORE steps are:
1.

Mount the two SAVE Set volumes on drive MMl: and MM2:,
write-protected.

Mount the destination disk on ORl:, write-enabled.

Type RUN $SAVRES and press RETURN.

$ RUN $SAVRES<RET>

SAV/RES Function: RESTORE<RET>

From device? MMl:<RET>

*** SAVE Set Name/default Pack IO is SAVSET
d

To RSTS DR: Disk? ORl:TSTPAK<RET>

*** The volume on ORl: is a RSTS disk
*** Pack IO is MYPAK
*** Pack will be reinitialized
Mount it anyway <NO>? Y<RET>
*** Pack IO is TSTPAK
e

Verify (Yes or No) <NO>? <RET>

E-23

SAVE/RESTORE System Program
f

Proceed (Yes or No)? Y<RET>

*** Begin RESTORE from MMl: to DRl: at 08:28 PM
Dismount Device:
Set Name:
Seq #:
Density:
Creation date:
Expiration date:

MMl:
SAVSET
1
800
Friday, 10-May-85
Saturday, 10-May-86

Mount volume # 2 of SAVE Set .SAVSET
Device? MM2:<RET)
Proceed (Yes or No)? Y<RET>

*** Begin RESTORE from MM2: to DRl: at 08:32 PM
Dismount Device:
Set Name:
Seq #:
Density:
Creation date:
Expiration date:

MM2:
SAVSET

Dismount Device:
Pack ID:
Pack Clustersize:
Creation date:

DRl:
TSTPAK
8
Monday, l5-Apr-85

800
Friday, 10-May-85
Saturday, 10-May-86

Please label this volume!
RESTORE operation completed at 08:37 PM
g

Summary Report
RESTORE of SAVE Set SAVSET to DRl:TSTPAK
Input Device:
Set Name:
# of volumes:
Density:
Creation date:
Expiration date:

Magtape
SAVSET
2
800
Friday, 10-May-85
Saturday, 10-May-86

output Device:
Pack ID:
Pack Clustersize:
Creation date:

DRl:
TSTPAK
8
Monday, l5-Apr-85

RESTORE started on Friday, 10-May-85, at 08:28 PM

E-24

SAVEjRESTORE System Program
h

Run Statistics
Transfer Totals:
Total of 54184 blocks transferred
Error Totals:
Total of

o new bad blocks encountered on destination.

o files structurally altered.
Timing Totals:
Total elapsed time:

o hrs.,

9 mins.,

36 secs.

Total wait

o hrs.,
o hrs.,

o mins.,

16 secs.

9 mins.,

20 secs.

time:

Total process time:
i

SAV/RES Function: <CTRL/Z>

$
The explanation of the RESTORE example follows:
a

Type RUN $SAVRES, and then press RETURN to run the SAVE/RESTORE
program.

Begin the RESTORE operation by typing RESTORE and pressing
RETURN in response to the initial SAVE/RESTORE prompt. Because
you need to recreate an RM03 from a tape SAVE Set, you select
the RESTORE function.

The RESTORE dialogue begins when it prints the From Device?
question.
In response, you specify the device name and the unit
number of the SAVE Set medium and press RETURN.
Because the
input medium is tape, mounted on drive number 1, you enter MMl:.
If you had included a SAVE Set Name in the device specification,
RESTORE would have checked it against the name already on the
set.
If they had not matched, RESTORE would have issued a
warning message informing you of the discrepancy. After you
terminate your response by pressing RETURN, RESTORE reads the
SAVE .Set Name from the input medium and displays it on your
terminal.

Because in this RESTORE operation you are recreating an RM03
disk, you ~espond to the To RSTS DR: Disk? question by typing
DRl:TSTPAK. By your response, you indicate that the device
mnemonic of the RM03 is DR, that it is mounted on drive number
1, and that you want it to have a Pack ID of TSTPAK. After
pressing RETURN, RESTORE checks the Pack ID of the output disk.
E-25

SAVE/RESTORE System Program
It then prints a message showing you that the disk is a RSTS/E
disk, has a Pack ID of MYPAK, and that RESTORE will reinitialize
it. RESTORE issues a Mount It Anyway? question that gives you
the option to mount the disk or not. Because the data on the
disk is no longer valuable, answer Y and press RETURN. RESTORE
then initializes the disk with the new 'Pack ID.
e

The comparison of the ,input data to the data already transferred
to the destination disk is not essential during this particular
run; therefore, you press RETURN to accept the No default. When
you ask RESTORE to verify the transferred data, you are
essentially requesting that RESTORE perform two operations
rather than one. That is, you make the program perform two
passes on the data, once for the transfer and once for the
comparison.

No mistakes were made during the dialogue phase; therefore,
RESTORE proceeds with the operation in reply to your Y response.
After you press RETURN" RESTORE displays a message to indicate
it has begun the transfer. After RESTORE completes the first
volume, it prints input medium information, asks you to mount
the next volume, and asks if you want to continue the operation.
Again, because there are no errors in the dialogue, RESTORE
proceeds. RESTORE moves the remaining data to the second
volume, issues the input and output dismount me~sages, and
informs you that the operation is completed.

The Summary Report prints the SAVE Set Name, the Pack ID, and
label information for both the input and output medium, in
addition to the date and time of the RESTORE operation.

The Run Statistics Report prints the number of blocks
transferred, the number of bad blocks encountered, and the times
required to perform various operations.

RESTORE returns to the SAV/RES FUNCTION prompt when the
operation has ended. Enter CTRL/Z, to return to your default
keyboard monitor (DCL in this example).

Copying a RSTS/E Disk using the IMAGE Dialogue
The IMAGE function lets you make an equivalent copy of a RSTS/E
file-structured disk; however, only disk-to-LIKE-disk transfers are
legal when using the IMAGE operation. LIKE disks are units that have
exactly the same device size. The SAVE/RESTORE program handles bad
block recovery during an IMAGE operation in the same way as RESTORE.
Table E-7 lists the IMAGE dialogue questions.
operation follows the dialogue description.

E-26

An example of the IMAGE

SAVEjRESTORE System Program
Note
If you are using the output of an IMAGE operation as
a system disk, you must use the tNIT.SYS INSTALL
option to reinstall the desired monitor Save Image
Library (SIL). You must also reenter any necessary
HARDWR suboptions (such as changing Hertz) because
the INSTALL option clears various items set up by the
HARDWR suboptions. This procedure is necessary
because you can make a copy of a disk on one system
and use the copied disk on another.

Table E-7:

IMAGE Dialogue Questions

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
From RSTS Disk?

<devspec>
SAVE/RESTORE transfers all data from the
disk specified in the device
specification response. If you include a
Pack ID in the device specification,
SAVE/RESTORE checks to see if it matches
the one actually on the disk. If it does
not, the program prints a warning message
(see section "Checking the Input Volume")
and prints the From RSTS Disk? question
again.
Type 2 characters to specify the input
device type, followed by a single digit
(0-7) to specify the unit number. Include
a Pack ID if you want SAVE/RESTORE to
make sure it matches the one on the
volume. This device must be physically
mounted and write-locked.

To RSTS Dx: Disk?

<devspec>
SAVE/RESTORE transfers all information
from the previously specified source disk
to this disk. If you include a Pack ID in
the device specification, it becomes the
Pack ID of the output disk. Otherwise,
SAVE/RESTORE uses the Pack ID of the
source disk.

E-27

SAVEjRESTORE System Program
Table E-7:

IMAGE Dialogue Questions (Cont.)

+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - _.- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

To RSTS Dx: Disk?
(Cont. )

Type 2 characters to specify the output
device type, followed by a single digit
(0-7) to specify the unit number. Include
a Pack ID if you want to override the
default. This drive should have a SCRATCH
volume mounted, and· must be
write-enabled.
Note that the device mnemonic you specify
in response to the From RSTS Disk?
question appears in place of the Dx in
the To RSTS Dx: Disk? question. In some
cases, in your device specification
response to the To RSTS Dx: Disk?
question, you may specify a device
mnemonic other than the one that appeared
for Dx. See the discussion of LIKE disks
in the section "Def~nitions of
SAVE/RESTORE Terms."

Verify(Yes or No)<NO>?

Y[es] or N[O]
This is the dialogue form of the VER[IFY]
switch. If you type YES, SAVE/RESTORE
compares the output with the input at the
end of each output volume to ensure that
the volumes are equivalent. If you type
NO, SAVE/RESTORE moves on to the next
question without performing a verify
pass.
Type YES if you want SAVE/RESTORE to
compare the input and output volumes at
the end of the IMAGE copy operation. Type
NO or press LINE FEED if you do not want
SAVE/RESTORE to perform the verification.

Proceed(Yes or No)?

Y[ES] or N[O]
This question lets you either double
check your dialogue responses and abort
the operation if you have made any errors
or proceed with the IMAGE operation.

Type YES to proceed with the operation.
Type NO to abort and return to the
SAV/RES Function: prompt.
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
E-28

SAVEjRESTORE System Program
After you answer the From RSTS Disk? qu~stion, th~ program prints a
message in the following general format to tell you the Pack ID it
intends to use:

*** Input Pack ID/default Output Pack ID is xxx xxx
If you do not want the output disk to have the same name as the input
volume, specify a different Pack ID in the <devspec> response to the
To RSTS DX: Disk? question. After you select the Pack ID and answer
the question, SAVE/RESTORE prints:

*** Output Pack ID is xxx xxx
The following procedure describes an IMAGE operation that copies an
RA80 to an RA80 and verifies the transfer in the same pass. The
letters are keyed to the explanation that follows this sample.
The IMAGE function steps are:
1.

Mount the source disk on drive DUO:, write-locked.

Mount the destination disk on drive DUl:, write-enabled.

Type RUN $SAVRES and press RETURN.

$ RUN $SAVRES<RET>

SAV/RES Function: IMAGE/NOERROR<RET>

From RSTS disk? DUO:<RET>

*** Input Pack ID/default Output Pack ID is SOURCE
d

To RSTS DU: Disk? DUl:DESTIN<RET>

*** The volume on DU1: is a RSTS disk
*** Pack ID is OUTPUT
*** Pack will be reinitialized
Mount it anyway <NO>? YES<RET>
*** Output Pack ID is DESTIN
e

Verify (Yes or No) <NO>? YES<RET>

Proceed (Yes or No)? YES<RET>

*** Begin IMAGE copy from DUO: to DU1: at 11:02 AM
*** Begin VERIFY pass from DUO: to DU1: at 11:04 AM
*** 0 differences found

E-29

SAVE/RESTORE System Program
Dismount Device:
Pack ID:
Pack Clustersize:
Creation date:

DU1:
DESTIN.
8
"Friday, 10-May-85

Please label this volume!
IMAGE copy operation completed at 11:07 AM
Summary Report

IMAGE copy of DUO:SOURCE to DU1:DESTIN
Input Device:
Pack ID:
Pack Clustersize:
Creation date:

DUO:
SOURCE

Output Device:
Pack ID:
Pack Clustersize:
Creation date:

DU1:
DESTIN
8
Friday, 10-May-85

Friday, 10-May-85

IMAGE copy started on Friday, 10-May-85, at 11:02 AM
h

Run Statistics
Transfer Totals:
Total of 24400 blocks transferred
Error Totals:
Total of

o bad compares.

Total of

o new bad blocks encountered on sou~ce.
o new bad blocks encountered on destination.

Total of

o files structurally altered.
Timing Totals:

Total elapsed time:

o hrs.,

5 mins.,

22 sees.

Total wait

time:

o hrs.,

o mins.,

o sees.

Total process time:

o hrs.,

5 mins.,

22 sees.

SAV/RES Function: <CTRL/Z>
$

E-30

SAVE/RESTORE System Program
The explanation of the IMAGE example •. follows:
a

Type RUN $SAVRES and press RETURN to run the SAVE/RESTORE
program.

SAVE/RESTORE prints the SAV/RES FUNCTION prompt to determine
which function you want to perform. To create a copy of an
RA80, select the I~ffiGE function by typing IM/NOERROR and
pressing RETURN. Attach the /NOERROR switch to insure that no
data is lost.
The /NOERROR switch causes SAVE/RESTORE to end
the operation whenever the program finds a run-time error.
Before the program aborts, it prints an error· message indicating
the source of the problem.

In reply to the From RSTS Disk? question, specify the disk from
which you are to· extract the data.
Enter the device name and
unit number of the input disk and end the response by pressing
RETURN. After this response, IMAGE reads the Pack ID from the
input disk and displays it on your terminal.

IMAGE requests the device name and unit number of the output
disk.
Type DBl:DESTIN to indicate that the RA80 is on drive 1
and you want DESTIN to be the new Pack ID. As soon as you press
RETURN, SAVE/RESTORE tells you that the output medium is a
RSTS/E disk, its Pack ID is OUTPUT, and it will be initialized.
SAVE/RESTORE initializes the disk when you type Y and press
RETURN in response to the Mount it anyway? question. A message
that SAVE/RESTORE prints informs you that the disk was
initialized to the specified Pack ID.

To insure against losing data, type YES to have IMAGE determine
if the input data equals the data that was transferred to the
output disk.
If IMAGE· finds that the data is not equivalent, it
informs you of these differences.

You are satisfied that you made no errors in the dialogue
sequence and feel that the operation should proceed. After you
press RETURN, IMAGE informs you when it begins to transfer data
and when it begins the verify pass. After completing the data
comparison, IMAGE prints the number of differences found between
the two devices.
It then issues the output device dismount
message.
Immediately after IMAGE prints the dismount request,
it prints a message to show you the copy operation ended
successfully.

IMAGE prints the Summary Report unless you suppress it by using
the /NOSTATS switch. The report includes the Pack ID and label
information of each disk, in addition to the date and time that
the IMAGE operation was run.

E-31

SAVE/RESTORE System Program
h

The Run Statistics Report provides a total figure for the number
of blocks transferred, the errors encountered, and the times
required to perform the IMAGE operation.

SAVE/RESTORE returns you to the SAV/RES FUNCTION prompt when the
operation ends.
Enter CTRL/Z to return to your keyboard monitor
(DCL in this example).

IDENTIFY Dialogue
If you want label information from a SAVE Set volume or a RSTS/E
file-structured disk, use the IDENTIFY function.
SAVE/RESTORE asks
only one question before the IDENTIFY operation begins.
Table E-8 lists the IDENTIFY dialogue question.
IDENTIFY operation appear after the table.
Table E-8:

Examples of the

IDENTIFY Dialogue Question

+ - - - - - - - - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -+
I
Question
I
Response and Description
I
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
From Device?

I
I <devspec>
SAVE/RESTORE prints the device label
characteristics of the SAVE Set or RSTS/E
file-structured disk for the device
specified in the dialogue response. If
you include a SAVE Set Name or Pack ID,
SAVE/RESTORE checks to see if it matches
the name on the device. If it does not,
the program prints a warning message (see
the section "Checking the Input Volume")
and then prints the From Device? question
again.

Type 2 characters to specify the input
device, followed by a single digit (0-7)
to specify the unit number. Include a
SAV~ Set Name or Pack ID if you want
SAVE/RESTORE to make sure it matches the
one on the volume. You must mount and
write-lock the device (for protection)
before responding to the From Device?
question.
+- - - - - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

E-32

SAVEjRESTORE System Program
'The following IDENTIFY example shows the label characteristics of both
a SAVE Set and a RSTS/E disk. The letters are keyed to the
explanation that follows this sample.
The IDENTIFY procedures are:
1.

Mount a SAVE Set volume on MMl:, write-locked.

Mount the RSTS/E disk on drive DRl:, write-locked.

Type RUN $SAVRES and press RETURN.

$ RUN $SAVRES<RET>

SAV/RES Function: ID MMl:<RET>

Device:
Set Name:
Seq #:
Density:
Creation date:
Expiration date:

1600
Friday, 10-May-8S
Saturday, 10-May-86

SAV/RES Function: ID DRl:<RET>
Device:
Pack 10:
Pack Clustersize:
Creation date:

MMl:
SAVSET

DRl:
TSTPAK
8
Monday, IS-Apr-8S

SAV/RES Function: <CTRL/Z>

$
a

Type RUN $SAVRES and press RETURN to run the SAVE/RESTORE
program.

The SAVE/RESTORE program prints the SAV/RES FUNCTION prompt.
You respond to it with the first two letters of the IDENTIFY
function and with the device name and unit number of the medium
you want to identify.
Include a Pack 10 if you want
SAVE/RESTORE to compare the ID you specify with the one on the
input volume.

IDENTIFY prints label information for the tape SAVE Set.

SAVE/RESTORE returns to the SAV/RES FUNCTION prompt.
In
response, you ask SAVE/RESTORE to identify the disk pack mounted
on DRl:. SAVE/RESTORE prints the information as soon as you end
your response.
E-33

SAVE/RESTORE System Program
e

Enter CTRL/Z to return to your keyboard monitor (DCL in this
example) .

Full Function Command Line
Use the full function command line format if you do not want to answer
each dialogue question separately. The general format is:
SAV/RES Function:<function><outdevspec>=<indevspec>[<switch(es»]
Function can be SAlVE], RE[STORE], IM[AGE], or ID[ENTIFY] and the
switches can be any of those listed as valid with the associated
function (see section "SAVE/RESTORE Switches"). Seethe section'
"Device Specifications" for an explanation of the device
specifications.
If you specify a full command in response to the SAV/RES FUNCTION
prompt, SAVE/RESTORE prints only the PROCEED question (except during
an IDENTIFY question):
Proceed (Yes or No)?
You must type either YES or NO to this question. Type YES to have
SAVE/RESTORE begin the operation; type NO to abort.
SAVE/RESTORE does the same standard volume label checking during the
full function command line operation as it does during the longer
dialogue procedure.
If a discrepancy occurs, SAVE/RESTORE prints the
error message and then returns to the SAV/RES FUNCTION prompt. At
that point, you must type the full function command line again.

SAVE/RESTORE and Booting
SAVE/RESTORE always attempts to create bootable media.
The output of
a RESTORE or IMAGE copy operation is bootable if the original disk
contained an INIT.SYS file in [0,1] (even if the original disk was not
bootable). The first output volume that the SAVE operation produces
is always bootable because SAVE/RESTORE copies the INIT.SYS file from
the system disk and HOOKs it on this volume. Note that only the first
volume in a SAVE Set is bootable.

E-34

SAVEjRESTORE System Program
If a SAVE volume is booted, a portion of INIT.SYS is loaded, allowing
you to perform the following INIT options:
o

SAVE/RESTORE

DSKINT

BOOT

HARDWR option specifying the LIST suboption

The types of SAVE/RESTORE operations you can perform depend on the
type of device you boot from.
You can run all four SAVE/RESTORE
options if you boot from a RSTS/E disk. However, you can perform only
an IDENTIFY, IMAGE, or RESTORE operation if you boot from a RSTS/E
magnetic tape or SAVE volume.
If you boot a SAVE volume and then
perform a RESTORE operation, SAVE/RESTORE prints a message at
completion of the run:

*** Please boot from the system disk
Boot device?
You must specify the device name and unit number of a boatable device.
Table E-9 summarizes the SAVE/RESTORE operations you can perform while
booting various devices.

Table E-9:

Booting RSTS/E and SAVE Set Volumes

+- ...... - _ .... _ .. _ .. - - - - -+- .. - - - - - - _.. - - - _.... - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - --+
I
I
SAVE/RESTORE
I
SAVEjRESTORE
I
Device Booted
I
Operations You
I
Operations You Can
I
I
I
From
I
Can Perform
I
Perform Afterwards
I
+ - .... - .. - .. - - - .. - - - - - - + - .. - - - - - .. - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - -+
RSTS/E Magnetic
Tape

IDENTIFY, IMAGE, RESTORE

SAVE Set Volume
(Disk or Tape)

IDENTIFY,IMAGE

SAVE Set Volume
(Disk or Tape)

RESTORE

RSTS/E Disk

I
I
I
I
IDENTIFY,IMAGE,RESTORE
I
I
I
None -- You receive a
I
message that states you I
must boot from the
I
system disk.
I
I
SAVE,RESTORE,IMAGE,
I
IDENTIFY
I
IDENTIFY, IMAGE, RESTORE

SAVE , RESTORE , IMAGE,
IDENTIFY
+- - - - - - _ .. _ .. - - - - - - -+- - - - - - - - - - - - .... - - - - _ .. - _ .. -+_ .... - - - - - _ .. - - - - - - - - - - - - - --+
E-35

SAVE/RESTORE System Program
Note
You cannot use the console bootstrap to boot a
magnetic tape SAVE Set if:
o

The tape has a density of 1600 bpi.

The drive the tape is mounted on has a TM02
formatter.
(Use the HARDWR LIST suboption of
INIT to determine the type of formatters on your
drives.)

However, you can boot a 1600 bpi tape on a drive with
a TM02 formatter if you use the BOOT OPTION prompt of
INIT.SYS. That is, you can boot under these
circumstances using software but not hardware boot
procedures. As an additional restriction, you can
boot a magnetic tape SAVE Set only on the following
drives: TSll, TU45, TuaO, TU16, TU77, and TE16.

Operator Interface During Processing
SAVE/RESTORE requires operator intervention at certain points during
processing. The operator must mount and dismount devices, reset hung
devices, and abort operations when necessary. The following sections
describe these procedures.

Mounting and Dismounting Volumes
A SAVE Set can contain more than a single volume. Because you may be
processing multivolume SAVE Sets, the SAVE/RESTORE program contains
procedures that allow you to mount the additional volumes in a set.
When SAVE/RESTORE needs an additional volume to complete a SAVE or
RESTORE operation, it prompts you with the message:
Mount volume inn of SAVE Set <setnam>
Device?

Proceed (Yes or No)?

E-36

SAVEjRESTORE System Program
The letters nn represent the volume sequence number and <setnam>
indicates the SAVE Set Name and unit number of the drive on which the
next volume has been readied.
If you mount a device of the same type,
you can respond to this prompt only with a unit number. After you
press RETURN to terminate your device specification, SAVE/RESTORE
performs volume label checking (see sections "Checking the Input
Volume" and "Checking the Output Volume"). At this point, if the
additional volume you mount violates any SAVE/RESTORE rule, the
program prints the error message immediately after the Device?
question.
SAVE/RESTORE prints a dismount message when:
o

SAVE/RESTORE completes a SAVE Set volume during a SAVE or
RESTORE operation

SAVE/RESTORE completes the data transfer to the output volume
in an IMAGE copy operation

You mount an incorrect volume

Note that the dismount message SAVE/RESTORE generates for a SAVE Set
(Format 1) differs from a dismount message printed for a RSTS/E disk
(Format 2):
Format 1
Dismount Device:
Set Name:
Seq #:
Density:
Creation Date:
Expiration Date:

Format 2
Dismount Device:
Pack ID:
Pack Clustersize:
Creation Date:

The <device> field represents. a two character device mnemonic followed
by a single digit unit number.
The SAVE Set Name replaces <setnam>,
and the disk pack identification replaces <packid> during a valid
SAVE/RESTORE operation. Density figures are. printed only for magnetic
tape SAVE Sets.
Finally, if SAVE/RESTORE has just written to the
volume, it prints the PLEASE LABEL THIS VOLUME message immediately
after the dismount message of the volume.

E-37

SAVE/RESTORE System Program
Re~ccessing

Devices

During an operation you may find that SAVE/RESTORE does not have
access to a previously accessible device.
If a device does become
hung or is write-protected, the program notifies you in the warning
message:
%%% Device hung or write-locked
Retry (Yes or No)?

Correct the condition causing the problem if possible, and then type
YES to attempt to gain access to the device. Type NO to abort the
attempt . .

Aborting SAVE/RESTORE
To end a SAVE/RESTORE operation at any time, enter CTRL/C. This
returns control to your keyboard monitor if you running SAVE/RESTORE
on line.
If you are running under the control of the INIT.SYS program
and the operation ends, INIT.SYS returns you to its OPTION prompt. An
abort during a SAVE, RESTORE, or IMAGE operation leaves the output
volume unusable. However, you do not jeopardize any IDENTIFY volumes
if you choose to abort this operation.

SAVE/RESTORE Summary Report
SAVE/RESTORE prints a Summary Report at the end of RESTORE, and IMAGE
operations. The report identifies the operation that was run, lists
characteristics of the input and output devices, and generates a list
of data tra~sfer, error, and timing statistics. It also documents the
time and date of the operation.
Summary Report Format and Example
The format of the Summary Report varies with the operation. At times
the Input Device characteristics (see Figure E-l) identify a SAVE Set,
as in the case of a RESTORE operation. Thus, depending on the
operation, the SAVE Set format may be represented under either the
Input or Output Device category. The RSTS/E disk format may be
printed also under the Input or Output Device categories.

E-38

SAVE/RESTORE System Program
Figure E-l shows the general format of the SAVE/RESTORE Summary
Report.
SAVE
IMAGE
RESTORE

disk<packid>
SAVE Set <setnam>

Input Device:
Pack ID:
Pack Clustersize:
Creation date:
output Device:
Set Name:
# of volumes:
Density:
Creation date:
Expiration date:

disk<packid>
SAVE Set<setname>

<device>
<packid>
nn
*RSTS/E disk format
<day of week, dd-mmm-yy>
[magnetic tape]
[disk]
<setnam>
*SAVE Set format
nn
[ 800]
[1600]
<day of week, dd-mmm-yy>
<day of week, dd-mmm-yy>

Run Statistics
Transfer Totals:
Total of nnnnnnn blocks transferred
Error Totals:
Total of nnn bad compares.
Total of nnn new bad blocks encountered on source.
Total of nnn new bad blocks on destination disk.
Total of nnn files structurally altered.
Timing Totals:
Total elapsed time:
Total wait
time:
Total process time:
Figure E-l:

nn hrs.,
nn hrs.,
nn hrs.,

Summary Report Format

E-39

nn mins.,
nn mins.,
nn mins.,

nn secs.
nn secs.
nn secs.

SAVE/RESTORE System Program
Summary Report Run Statistics
Table E-IO lists and describes the run statistics that appear at the
end of a SAVE, RESTORE or IMAGE operation. Because each SAVE/RESTORE
operation prints its own set of run statistics, Table E-IO also
identifies the operations in which each run statistic is printed. The
operations are identified according to the following conventions:
S = SAVE operation
R = RESTORE operation
I

= IMAGE operation

Table E-IO:

Summary Report Run Totals

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Type of Statistic
Operation and Description
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Transfer Statistics
Total of blocks
transferred

This number refers to the total number of
blocks transferred (directory blocks, file
blocks). In a SAVE operation an extra set of
directory blocks is stored at the end of a
SAVE Set. The total number of blocks
transferred includes these extra blocks.
[SRI]

Error Statistics
Total of bad
compares

The total number of errors that occurred
during the VERIFY phase. [SRI]

Total of new bad
block errors
encountered on
source

The number of previously unreported bad
blocks encountered on the source disk. [SRI]

Total of bad block
errors on
destination disk

The number of previously unreported bad
blocks encountered on the destination disk.
[SRI]

Total of files
structurally
altered

The number of files that were structurally
altered to enable relocation on the
destination disk. (~his means contiguous
files were made noncontiguous or placed
files were moved.) [RI]

E-40

SAVE/RESTORE System Program
Table E-IO:

Summary Report Run Totals (Cont.)

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - _ .. - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
I Type of Statistic I
Operation and Description
I
+ - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - - - - - - - - - - - - - - - - -' - - - - - - - - - - - - - - - - - - +
Time Statistics
Total elapsed time
(TE)
, Total wai t time
(TW)

The total amount of real clock time that
elapsed during the run. [SRI]
The amount of real clock time that elapsed
while waiting for operator responses and
magnetic tape rewinds. [SRI]

I
I
I
I
I
I
I
I
I
I
I
I

Total process time
The amount of real clock time that was used
(TP)
for processing (TE-TW=TP). [SRI]
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

SAVEjRESTORE Error Handling
SAVE/RESTORE issues dialogue, mount, transfer, and verification error
messages. When you find an error message during a dialogue or a
mount, SAVE/RESTORE asks you to correct the condition, where
appropriate, and then asks you to reenter the command. Errors you
encounter during either of these phases never affect the integrity of
the data being transferred.
Note
When SAVE/RESTORE reports an error during a transfer
or verification phase, it has detected a problem that
might corrupt the data being transferred. Depending
on the nature of the error, a single file, or perhaps
an entire volume, might be affected. Generally, you
encounter fewer critical errors during a dialogue or
mount phase than in a transfer or verification
operation .
. SAVE/RESTORE does not report an error when it finds a bad block on the
output device, unless it is unable to reallocate that block in a way
that is transparent to you.
For instance, the one-block file
SHIFT.LES is moved without notice if a free cluster can be found.
On
the ·other hand, the program issues an error message if it must move
the placed file, MOVEME.NOT.
The /NOERROR switch causes SAVE/RESTORE to abort the run if it finds
any condition that warrants an error message.
If you do not specify
the /NOERROR switch, the program takes whatever action necessary.

E-41

SAVE/RESTORE System Program
SAVE/RESTORE always informs you of any corrective action taken so you
have the option of aborting the operation.
The most important problem that SAVE/RESTORE encounters during a
RESTORE or IMAGE copy operation is finding a bad block on a RSTS/E
file-structured disk when it wants to write to that block. The
program attempts to correct the problem by performing the following
actions in the order listed:
1.

Marks a contiguous file as noncontiguous and relocates the
bad cluster but not the entire file.

Marks the file as nonplaced if the bad cluster occurs at the
beginning of a placed file.

Finds enough contiguous free pack clusters on the output disk
to hold the number of clusters that must be moved. In other
words, if the cluster size of a file is 16, SAVE/RESTORE
finds 16 free contiguous blocks for the cluster. It proceed~
if the reallocation worked and aborts if it has not worked.

SAVE/RESTORE always tells you about the changes it makes to a file
that are caused by this bad block processing. If there is no way to
relocate a cluster, the program aborts the operation. Unless you
specify the /NOERROR, SAVE/RESTORE never terminates an operation when
it finds a bad block that results in a nonfatal error (see the section
"SAVE/RESTORE Switches").

General SAVE/RESTORE Error Messages
Table E-ll describes the errors that can occur. during SAVE/RESTORE
operations.
Table E-ll:

General SAVE/RESTORE Error Messages

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Message and Meaning

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
I %%% Bad block in first n blocks of output volume
I
I
~he current volume is unusable. Sufficient space must be
available at the beginning of a SAVE Set to store certain
I
critical information necessary for a SAVE/RESTORE operation.
I
I
I
Mount a different volume and try again.

E-42

I
I
I
I
I
I
I
I

SAVE/RESTORE System Program
Table E-ll:

General SAVE/RESTORE Error Messages (Cont.)

-- ---- ---- ----- -- --- -- - - ---- -- --- ----- ---- ------ -- ---- ---- - - - --- - - - -~
Message and Meaning
I
~ - - - - -- - - - ---- -- - -- - - - - - ------ - - --- -- - -- - - - ----- - - -- -- --- - - - - --- - - -- -~
~

??? Bad block in MFD
SAVE/RESTORE aborts the operation when it finds a bad block
in the Master File Directory (MFD).
%%% Bad block in SATT.SYS

There is a bad block in the input SATT.SYS file.
SAVE/RESTORE does not use an input disk that has a corrupt
SATT.SYS file.

??? Bad block on magtape - can't continue
SAVE/RESTORE requires a magnetic tape SAVE Set volume to be
long enough to contain a bootstrap, label information, and
INIT.SYS. Whenever the program finds a bad block before it
transfers all required information, it aborts the current
operation.
%%% Bad data:
in [MFD]
[<[P,PN] FILENAME.TYPE>]
[UFD [P,PN]]
[GFD, nnn]

A cluster contained in the described account or file could
not be relocated due to a fatal read error on the output
volume.

??? Bad directory for device
SAVE/RESTORE discovered a bad link or bad block in the input
or output directory structure.
%%% Bad INIT.SYS on system disk

SAVE/RESTORE found a bad block in INIT.SYS while
transferring it from the system disk to a SAVE Set volume.
%%% Can't mix device types in SAVE Set

A SAVE Set cannot be composed of both tapes and disks. Only
all disk or all tape SAVE Sets are legal.

E-43

SAVE/RESTORE System Program
Table E-ll:

General SAVE/RESTORE Error ,Messages (Cont.)

- - ---- - --- ~ --- --------- - -- -- ---- - -------- - -- --- - -- ---- --- -- - - - ----- -~
Message and Meaning
I
~ - - --- - ---- -- - -- - --- -- -- - -- - - --- - - -- - - - - - --- --- -- - ---- -- - -- - - - - - ---- -~

I
I %%% Can't read bad block file
I
SAVE/RESTORE could not read the bad block file on a RSTS/E
I
disk or a SAVE Set volume.
I
I
I ??? Can't read SAVE Set volume SATT

A nonrecoverable I/O error occurred while SAVE/RESTORE
attempted to read the Storage Allocation table on the SAVE
Set volume.
%%% Can't write boot

The bootstrap could not be written to the first block of the
output disk.
%%% Can't write INIT.SYS

SAVE/RESTORE found a fatal bad block while transferring
INIT.SYS to SAVE Set volume.
%%% Device hung or write-locked
Retry (Yes or No)?

The output device is off line or is write-locked. Correct
the condition and try again. Type YES to continue or type NO
to abort.
%%% Device mnemonic must be specified

Enter the device name along with the unit number.
%%% Disk must be DSKINTed

When you are running SAVE/RESTORE on line, the output disk
must be RSTS/E file-structured or a SAVE Set volume. Use the
DSKINT option of INIT.SYS to reinitialize the disk. See the
RSTSIE System Installation and Update Guide for a
description of the DSKINT option.
%%% Duplicate switches

You specified the same switch more than once.

E-44

I
I

SAVEjRESTORE System Program
Table E-ll:
~

General SAVEjRESTORE Error Messages (Cont.)

-- --- - -- ---- - --- -- - - ------------ - ----- - -- - ----- - -- ---- - --- - -- -- --- Message and Meaning

-~
1

~ - - - - - - - - - - - - ~ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -i-

??? Error in BADB.SYS allocation
SAVE/RESTORE was unable to rebuild the bad block file
(BADB.SYS) after completing the current operation.

??? Fatal output bad block
A bad block was found at a critical position, preventing
SAVE/RESTORE from completing the current operation.
%%% Illegal command
Your response to a prompt was in an unacceptable format.
%%% Illegal command:
no output device specified
1
1

The full function line command you specified did not include
an output device specification.

1
1

I
1
1

%%% Illegal date
The date you specified was in an unacceptable format or was
included where none was acceptable.

I
1
1
1

%%% Illegal density
The density you specified was in an unacceptable format, was
included where none was acceptable, or specified an illegal
density value.

1
1

%%% Illegal option

1
1
1

When booting from a SAVE Set volume, you can use only the
RESTORE, IMAGE, and IDENTIFY options.

I
1

%%% Illegal switch

I
1

You used a switch in an unacceptable way.

1
1

%%% Illegal switch combination

1
1

You specified conflicting switches.

E-45

SAVE/RESTORE System Program
Table E-ll:

General SAVEjRESTORE Error Messages (Cont.)

-r - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - ---r

Message and Meaning

+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ---r

%%%#Input disk has only nn% free clusters.
Mount it anyway <No>?
SAVE/RESTORE discovers the input disk has very few clusters
that are not allocated and ,may find problems copying or
restoring the disk. You may want to delete some unnecessary
file to increase the chances that SAVE/RESTORE can
eventually complete a successful RESTORE.
%%% Input disk should be rebuilt
The disk you mounted is "dirty." The SATT.SYS file may be
corrupt. SAVE/RESTORE requires a valid SATT.SYS; therefore,
rebuild the disk using the REFRESH option of INIT or the
ONLCLN program. See the RSTS/E System Installation and
Update Guide for a description of REFRESH. See the RSTS/E
utilities Reference Manual for information about ONLCLN.
%%% Its expiration date has not passed
Mount it anyway (Yes or No)?
A SAVE Set on an output volume contains an expiration date
that has not expired. SAVE/RESTORE prints the SAVE Set Name
and expiration date before issuing this message.
Confirm whether you should use this volume or mount a
different volume if appropriate.
%%% Magtape select error
Retry (Yes or No)?
When access to a magnetic tape drive was attempted the
selected unit was off line.
%%% No default-type <cr> for more information
You typed a LINE FEED in response to a question which has no
default.
??? No INIT.SYS on system disk
There is no INIT.SYS in account [0,1] on the system disk.

E-46

SAVE/RESTORE System Program
Table E-ll:

General SAVE/RESTORE Er ror Messages (Cont.)

- - -------------- -- - - - - ----- - - - - - - - - - - -- - - ------------ - - --- - -------Message and Meaning
I
~ - - --- - - - - - -- - -- - - - - - -- - - --- - --- - - - - - - - - -- - - - - - ------------ - ----- --- -~
~

I
I
I
You attempted to return to the previous question but it no
I
longer exists.
I
I
%%%Non-existent or hung device
I
I
You specified a disk or magnetic tape that does not exist on I
your system or is not on line.
I
I
Check your configuration or the device type again and retry. I
I
??? Non-recoverable I/O error
I
I
SAVE/RESTORE found a fatal error condition while trying to
I
recover from a DEVICE HUNG OR WRITE LOCK error. SAVE/RESTORE I
aborts the current operation and returns you to the SAV/RES
I
FUNCTION prompt.
I
I
%%% Not a valid device
I
%%% No previous question - type <cr> for more information

You specified an unacceptable device type in response to the
question. This may occur if you specify:
o

A device other than magnetic tape or disk

A tape rather than a disk (or vice versa)

A wrong disk type on an IMAGE

A device without including a unit number, for example,
DK: instead of DKO:

%%% Only nn% of the output disk clusters are available for
relocation
Mount it anyway <No>?
SAVE/RESTORE finds there are few free blocks available for
relocation on the output disk.
??? Operation aborted at user request
You specified the /NOERROR switch and one of the errors
described in Table E-12 occurred, or you typed NO to a RETRY
(Yes or No)? question.

E-47

SAVE/RESTORE System Program
Table E-ll:
~

General SAVE/RESTORE Error Messages (Cont.)

--- -'- ---------- - - - - - - - - - - - - - - - - - - - -- - - -- - - - - -- - - - - - - - - --- - -- - - -- - - --~
Message and Meaning

~- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

%%% Same device specified
You designated the same device for both input and output.
Specify the correct output device.
%%% Tape won't respond to density XXXX
SAVE/RESTORE attempted to set the density of the specified
magnetic tape to XXXX but the hardware rejected the request.
Specify a density setting that is legal for that device, or
use a different device.
%%% Tape won't respond to any density
The input volume cannot be read at any legal density
setting.
%%% This is not the correct volume
The SAVE Set or Pack ID you specified does not match that on
the mounted device. A DISMOUNT DEVICE message follows the
error message and identifies the volume if it is a SAVE Set
or a RSTS/E file-structured disk.
This message also occurs if SAVE/RESTORE requests the next
volume of a SAVE Set and you specify a device containing a
volume that is not part of the current SAVE Set or is not
the correct sequential volume of the current SAVE Set.
Mount the correct volume.
%%% This volume has no label
SAVE/RESTORE did not find a valid SAVE Set label or Pack ID
on the specified input volume.
%%% Too many bad blocks on input disk
The number of bad clusters on the input disk exceeds the
RSTS/E limit.

E-48

SAVE/RESTORE System Program
Table E-ll:

General SAVE/RESTORE Error Messages (Cont.)

The number of allocated clusters on the original source disk
exceeds the number of available clusters on the output disk
or the number of bad clusters on the output disk exceeds the
RSTS/E limit (161 bad clusters).
Use a different disk pack.
%%% Unrecognized switch

You have specified an invalid switch.
??? Volume is full
There was not enough room for the relocation of data
clusters due to the blocks found on the output volume.
%%% Wrong size disk

The output volume of an IMAGE or RESTORE must be the same
size as the original source. See the discussion of LIKE
disks in the section "Definitions of SAVE/RESTORE Terms."
%%% You will be writing to the booted device

If you write to this device, you need to reboot when you are
finished with SAVE/RESTORE.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

Transfer Errors-Fatal and Nonfatal
Transfer errors you may find in a SAVE/RESTORE operation can be fatal
or nonfatal.
Fatal transfer errors cause an immediate termination of
the current operation. Nonfatal errors, if the /NOERROR switch is not
in effect, let the operation continue despite the problem. On the
other hand, if you specify the /NOERROR switch and one of the errors
in Table E-l2 occurs, SAVE/RESTORE terminates the operation
immediately (which indicates the output is not a valid medium).
In
other words, the nonfatal errors listed and described in Table E-12
become fatal if the /NOERROR is attached to the function response.
Whether or not you specify /NOERROR, the error message ???Volume is
full occurs if SAVE/RESTORE cannot relocate a file due to a bad block
E-49

SAVEjRE'STORE System Program
on the output device. The relocation does not take place because
SAVE/RESTORE cannot find any additional clusters available or does not
find as many free clusters as it needed. This results from too many
bad blocks on the output volume.
Table E-12 contains a description of all nonfatal transfer errors that
can occur if you do not specify /NOERROR.
Table E-12:

SAVEjRESTORE Nonfatal Transfer Errors

+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

I
Message and Meaning
+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -' - - --+
I
I %%% Bad block on input, PCN=nnnnnn
I
I
A bad block was found on an allocated cluster on the input
volume. A copied version of the data in that block might be
corrupt.
%%% Bad block on input, output peN's affected:
A bad block was found on the input SAVE Set volume, which
will affect certain pack clusters on the output disk. A
copied version of the data in that block might be corrupt.
%%% Bad block on input:
in MFO [PCN=nnnnnn]
in UFO [P,PN] [, PCN=nnnnnn]
in GFO, nnn [, PCN=nnnnnn]
in file [P,PN]FILENAME.TYPE,[PCN=nnnnnn]
A bad'block was found on an allocated cluster on the input
volume. A copied version of the data in that block might be
corrupt.
%%% Bad Compare, PCN=nnnnnn
The data on the input volume did not compare with the
corresponding data on the output volume. (See the
explanation following this table.)
%%%Bad compare on input:
in MFO[PCN=nnnnnn]
in UFO [P 1 PN] [, PCN=nnnnnn]
in GFO, nnn [, PCN=nnnnnn]
in file [P,PN]FILENAME.TYPE,[PCN=nnnnnn]
The data on the input volume did not compare with the
corresponding data on the .output volume. (See the
explanation following this table.)
E-50

SAVE/RESTORE System Program
Table E-12:

SAVE/RESTORE Nonfatal Transfer Errors (Cont.)

- -- - - -- -------- - - ---------- - -- - ------- - -- - ---- - - - - ----- - ---------- Message and Meani~g
I
~ - ------------------- - - -- - ------- - - --- - -- - - - - - - ----- - -- - ----- ~ ---- - - -~

I
I
I
SAVE/RESTORE found a bad block in the output area for file
I
XXXXXX. To complete the transfer, one or more blocks of the I
file were relocated.
I
I
Consider the consequences of this change and proceed
I
accordingly.
I
I
%%% Placed file XXXXXX has been moved from aaaaaa to bbbbbb
I
I
A bad block was found in the output area for file xxxxxx. To I
complete the transfer, one or more blocks of the file were
I
relocated.
I
I
Consider the consequences of this change and proceed
I
accordingly.
I
~ - ------- - - - ------- - - -- ~ - --- - - ----- - - - --- - - --- - - - -- - -- - - - -- - ------- - -~
%%% File XXXXXX has been changed to noncontiguous

During a verification pass, SAVE/RESTORE may detect differences
between the input and output. If there are differences, SAVE/RESTORE
informs you with two types of messages:
%%%Bad compare, PCN=nnnnn
%%%Bad compare in [MFD [, PCN=nnnnn]]
[UFD [p,pn] [, PCN=nnnnn]]
[GFD, nnn [, PCN=nnnnnn]]
[file [p,pn]filenam.typ [, PCN=nnnnnn]]
SAVE/RESTORE first prints a general error message and then, after some
additional processing, prints the second error message telling you
more specifically the accounts and/or files in which the bad
comparisons occurred.
If you request transfer verification, SAVE/RESTORE checks (after the
initial transfer phase) whether the data it has written matches the
corresponding data it read. If there is a difference, SAVE/RESTORE
prints:
%%%Bad compare in [MFD

[, PCN=nnnnn]]

The SAVRES program transfers only clusters that are marked as
allocated in the Storage Allocation Table. During the actual transfer
and verify pass, it can tell only which Pack Cluster Number (PCN) it
has completed. If /NOERROR is in effect and you are performing a SAVE
E-Sl

SAVE/RESTORE System Program
or IMAGE copy, SAVE/RESTORE then tries to pinpoint the problem by
scanning the input directory structure before aborting.
If you are
doing a RESTORE, SAVE/RESTORE simply aborts.
This difference exists
because SAVE/RESTORE must have a complete directory to scan in order
to find accounts and/or files that caused the problems.
In the case
of a RESTORE, the output volume is not yet complete and SAVE/RESTORE
cannot scan it.
If /NOERROR is not in effect, SAVE/RESTORE stores each PCN that caused
a problem in an internal table as it continues with the verify pass.
If SAVE/RESTORE finds more entries than can be stored in the table, it
prints the message:
"Affected file will not be reported"
This means there is no more room to store the information. At the end
of the verification pass, SAVE/RESTORE prints the total number of
variations found in the form:
%%% nn differences found
After completing the transfer, SAVE/RESTORE scans the input (SAVE or
IMAGE) or (RESTORE) volume directories to find the accounts and/or
files in which the bad comparisons occurred.
Then, it displays one or
more of the following messages:
%%%Bad compare in [MFO [, PCN=nnnnn]]
[UFO [p,pn] [, PCN=nnnnn]]
[GFO, nnn [, PCN=nnnnnn]]
[file [p,pn]filenam.typ [, PCN=nnnnnn]]

E-S2

AppendixF
Device Testing package (DEVTST)

The Device Testing Package (DEVTST) exercises hardware on the RSTS/E
system during normal time-sharing operations. You can use DEVTST to
simulate hardware errors on the system.

Introduction to DEVTST

DEVTST is a package of programs that provides the customer, System
Manager, or DIGITAL Field Service personnel with tests that verify the
reliability of RSTS/E-supported hardware. Execution of any DEVTST
program is limited to users with WREAD privilege. As distributed,
DEVTST is in TEST$: (by default, [0,5]).
This appendix explains operational data, conventions, complete device
testing information, and error messages. After execution of
individual DEVTST exercisers, you should check the System Error Log
for additional errors; for more information on the System Error Log,
see Chapter 10.
The DEVTST exercisers are tests that can be initiated whenever you
suspect hardware trouble.
These device. exercisers generate excess
activity in an attempt to make the hardware fail during operation.
Use the DEVTST package in conjunction with the RSTS/E error package
(see Chapter 10). The Error Logging facility provides the means for
determining detailed information on hardware errors. In addition, the
DEVTST programs return error messages that may be useful in
determining the failure; however, these messages are not as specific
as the information provided by the System Error Log.

F-l

Device Testing Package .(DEVTST)
The following conventions are used throughout the DEVTST package
dialogue:

< >

Indicates the default answer.
Shows all possible-replies.
Gives an optional reply; for example, ASC [II] means
enter ASC, ASCI, or ASCII.

Either key moves the program back one question.
If you
press either key as a response to the first question,
DEVTST will stop execution and return to the RSTS/E
command level.

Pressing CTRL/Z causes the program to stop execution and
return to RSTS/E command level. CTRL/Z is detected only
when the system checks for new input.

Pressing CTRL/C causes the program to stop execution
immediately and return to a command level.

<RET>

Use the RETURN key to terminate the input line.

Detach <NO>

All of the device exercisers have the ability to detach;
this allows you to_run an exerciser while keeping your
terminal free for other operations.

-1

Negative one, when used as a value for number of
iterations, pages, or lines, tells the program to run
indefinitely, or until you press CTRL/C.

DEVTST Operating Procedures
To run a DEVTST program, type:
RUN TEST$:program name
For example:
RUN TEST$:KBEXER

F-2

Device Testing Package (DEVTST)
Table F-l lists the program names and the hardware they test.
Table F-l:

DEVTST Programs

+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - --+
I Program I
Hardware Tested
I
+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - --+

I
I CPEXER
I CPUTST
I DSKEXR
I DSKSEK
I DTEXER

I
I CPU
I CPU
I File-structured disk
I Non-file-structured disk
I DEC tape

I DXEXER

I Diskette

I KBEXER
I LPEXER
I MTEXER
I PPEXER

I Terminal
I Line printer
I Magnetic tape
I Paper tape punch

I PREXER I paper tape reader
+- - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - --+
Table F-2 gives a complete list of RSTS/E supported hardware,
including designators and the associated devices.
Table F-2:

RSTS/E Device Designators

+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
Device Designator
I
Device
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
DK:, OL:, OM:, OP:,
OR:, OB:, DU:, SY:

I RSTS/E public disk structure
I
I

SYO:

I System disk (the unit that was bootstrapped)

OVO:

I Virtual disk, unit 0 only
I·

OKO: to OK7:
OLO: to OL3:
OMO: to OM7:
oPO: to OP7:
ORO: to OR7:
OBO: to OB7:

I RKOS/RKOSF disk cartridge units 0 to 7

I RLOl/RL02 diak cartridge units 0 to 3
I
I RK06/RK07 disk cartridge units 0 to 7
I
I RP02/RP03 disk pack units 0 to 7
I
I RM02/RM03/RMOS/RM80 disk units 0 to 7
I
I RP04/RPOS/RP06 disk pack units 0 to 7

F-3

Device Testing Package (DEVTST)
Table F-2:

RSTS/E Device Designators (Cont.)

+ - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - - -. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
I Device Designator I
Device
I
+- - - - - - - - - - - - - - - - - - - - -+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+
DUO: to DU7:

RA60, RA80, RA81, RC25, RD51, RD52, RX50
disk units 0 to 7

PR:

High-speed paper tape reader

PP:

High-speed paper tape punch

CR:

CRII punched or CMII mark sense card reader

CD:

COlI punched card reader

MTO: to MT7:

TEIO/TUIO/TS03 magnetic tape units 0 to 7

MSO: to MS3:

TSII/TSV05/TK25/TU80 magnetic tape units 0
to 3

MMO: to MM7:

TEI6/TUI6/TU45/TU77 magnetic tape units 0 to
7

LPO: to LP7:

Line printer units 0 to 7

DTO: to DT7:
Tu56 DECtape units 0 to 7
+ - - - - - - - - - - - - - - - - - - - - -+ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --+

DEVTST Dialogue Errors
Table F-3 lists the error messages that can occur in DEVTST programs.

F-4

Device Testing Package (DEVTST)
Table F-3:
~

DEVTST Error Messages

---------- - ------ - - - - - ---- - --- - - - - - --- - -- - - - - --- - - - - ---- - - - - ---- - -Message and Meaning

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

%Warning: <device name> is a logical device: <device name> will be I
used.
I

I
I
I
I
I
?Illegal device: <device name> specified.
I
I
The device name given by the user is either incorrect or is a
I
logical device name that cannot be translated (for example,
I
incorrect characters or the wrong type of device). Retry the
I
operation with the correct device name.
I
I
?OPEN failure on <device name>:
I
(Followed by an error message from Appendix A of the RSTS/E System I
DEVTST determines that the device name given is a logical name
for another device. DEVTST performs a logical device
translation and the translated device name is used.

Installation and Update Guide.)

This error message can mean one of the following:
o
o
o
o
o

The device specified does not exist
No volume was mounted on that device
Another user has assigned the device
The volume on the device has not been formatted
The device is not on-line or the device is not
write-enabled

To resolve: retry the operation using the correct option as
determined by the error message received.
?Illegal number of iterations selected.
Retry the

ope~ation

using the correct number of iterations.

--------- - - - - - -- - - - - ------ - - --- - - - -- - - - --- - - - - - ---- - -------- ---- - -

CPEXER
The central processor exerciser is designed to put a heavy load on the
Central Processing Unit (CPU). CPEXER runs compute bound for bursts
and then sleeps for five seconds so the average processor loading does
not appreciably degrade the performance of the system.

F-5

Device Testing Package (DEVTST)
CPEXER was specifically designed to test the Floating Point Processor
(FPP) option, but also serves to verify general CPU integrity and the
Extended Instruction Set (EIS) operation. There is also a test of the
PEEK function for kernel addresses 0 through 22000.
The next section itemizes the tests performed by CPEXER.
In most of
the tests, CPEXER compares the results to known correct values. Two
heavily compute-bound tests are included to verify consistent results
of duplicate calculations. Finally, CPEXER includes tests that verify
FPP divide by zero trap, integer divide by zero trap, integer
conversion error, arid EIS operation.

CPEXER Tests
The CPEXER program includes the following 13 CPEXER tests:
Test

Description

SIN(X)

Uses SIN(X) extended function

SIN(X)

Uses polynomial approximation to SINE function

LOG(X)

Uses LOG(X) extended function

EXP(X)

Uses EXP(X) extended function

SQR(X)

Uses SQR(X) extended function

SQR(X)

Uses Newton-Raphson method to determine the square
root

LOG(EXP(X»

Compute-bound test

ATN(TAN(X»

Compute-bound test

A=l.O/O.O

Verifies FPP divide by zero trap

A%=l%/O%

Verifies integer divide by zero trap

A%=60000

Verifies integer conversion error

INT(40.662l*100+0.5)/100=40.66 Verifies EIS operation
PEEK(X)

Verifies operation of PEEK

F-6

fun~tion

Device Testing Package (DEVTST)
CPEXER Dialogue
The following is an example of the CPEXER dialogue:

$ RUN TEST$:CPEXER CPEXER V9.0 RSTS V9.0 ED ERE
How many minutes to run <IS>?
Detach <No>?

11.9 seconds of CPU time used in 1 pass.
CPEXER finished at 03:36 PM
$

Note
The CPEXER program will build correctly only if the
version of BASIC-PLUS or BASIC-PLUS-2 includes TRIG
and LOG. These mathematical functions must be
included during system installation of BASIC-PLUS or
the installation of BASIC-PLUS-2.

CPEXER Errors
This program reports four types of errors:
1.

Instructions failed to execute.

Errors failed to trap.

Computation errors.

Computation consistency checks failed.

Check the System Error Log for reported errors.
indicate hardware problems.

These errors may

When type one errors (instruction errors) occur, CPEXER prints a
two-line message:
the first line gives the test that was being
performed and the exact error message, and the second line indicates
that the test is continuing. For example:
?CPEXER PEEK failed at memory location m.
-(Error Messag~)
continuing ..... .
F-7

Device Testing Package (DEVTST)
where:
(Error Message)

is the RSTS/E error message from Appendix A
of the RSTS/E System Installation and update

Guide.

is the memory location at which the PEEK
function failed.

Examples of type 2 errors (trap failure) are:
?CPEXER Floating point divide by 0 didn't trap
continuing .....
?CPEXER Integer divide by 0 didn't trap
Continuing .....
?CPEXER Forced integer conversion didn't trap
Continuing .....
?CPEXER (INT(40,6621*100=0.5))/100< >40.66
Continuing .....
Type three errors (computation errors) give the type of test
(SIN,PLYNOM, LOG, EXP, SQR, or NEWTON SQR), the error in the computed
value, and the location of the possible error.
For example:
?CPEXER - SIN test failed for the following cases:
?CPEXER - Computed value of SIN(40) was .643, should be .64
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
?CPEXER - PLYNOM SIN test failed for the following cases:
?CPEXER - Computed value of PLYNOM SIN (40) was .643, should be .64
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
?CPEXER - LOG test failed for the following cases:
?CPEXER - Computed value of LOG (140) was 4.942, should be 4.939
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
?CPEXER - EXP test failed for the following cases:
?CPEXER - Computed value of EXP (4) was 54.598, should be 54.599
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...

F-8

Device Testing Package (DEVTST)
?CPEXER - SQR test failed for the following cases:
?CPEXER - computed value of SQR (500) was 22.361, should be 22.362
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
?CPEXER - NEWTON SQR test failed for the following cases:
?CPEXER - Computed value of NEWTON SQR (500) was 22.361, should be
22.362
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
Type four errors (consistency failure) in the CPEXER are shown in the
following examples:
?CPEXER - EXP/LOG Consistency check failed for the following cases:
?CPEXER - EXP(LOG( ... ( 1 »»»»»
<> EXP(LOG( ... ( 1»»»»»
?CPEXER - EXP(LOG( ... ( 4 »»»»»
<> EXP(LOG( ... ( 4»»»»»
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...
?CPEXER - ATN/TAN Consistency check failed for the following cases:
?CPEXER - ATN ( TAN ( ... ( -1 . 5 »»»»»
<> ATN ( TAN ( .•. ( -1.5 »»»»»
?CPEXER - CPU,EIS,FIS,FPP,MUL,DIV or SHIFT Error
Continuing ...

CPUTST
The CPUTST dialogue'first asks how many minutes you want the test to
run.
The program then:
1.

Checks for expiration of this request time at eight strategic
points during each run sequence

Clears and/or sets three 2-dimensional arrays to specified
values

Transposes Matrix A and places the result in Matrix B

If no errors are found, returns to Step 2

If an error is found, reports the error and aborts the test

The program repeats this prqcess until the run time expires, at which
time it prints the CPU time in seconds of expended job time.

F-9

Device Testing Package (DEVTST)
CPUTST Dialogue
The following is an example of CPUTST dialogue:

$ RUN TEST$:CPUTST
CPUTST V9.0 RSTS V9.0 EDERE
How· many minutes to run <15>? 1
Detach <No>? NO
6.9 seconds of CPU time used.
CPUTST Finished at 10:59 AM
$

CPUTST Errors
This device exerciser reports errors as shown in the following
examples:
?CPUTST·Error in matrix transposition routine.
?(Error message) at line mm in CPUTST V9.0.
where:
(Error Message)

is the RSTS/E message in Appendix A of the RSTS/E
System Installation and Update Guide for the error
that occurred.

is the BASIC-PLUS line number in CPUTST where the
error occurred.

Check the System Error Log for reported errors.
indicate hardware problems.

These errors may

If your hardware does not include a floating point processor (FPP),
submit a Software Performance Report (SPR) to DIGITAL whenever errors
appear.

DSKEXR
This disk exerciser tests the normal operation of all file-structured
disks.
It is possible to run several copies of DSKEXR in order to
test several drives simultaneously or to put a heavier load on any
single drive.
The disk must be physically and logically mounted.

Device Testing Package (DEVTST)
DSKEXR begins by asking questions to determine the disk drive to be
"tested and the number of test iterations to be performed.
After this dialogue, the exerciser:
1.

Opens and extends a temporary file to a predetermined size
that is dependent upon disk size and the number of free
blocks

Loads a pattern buffer with one of four patterns (alII's and
D's or a pattern of alternating l's and D's)

writes the file

Reads each block and compares it for each of the patterns.

Upon completion of all iterations for each drive you specify, DSKEXR
prints a status report.
Note
This write operation does not use current disk files
to read and write.
The temporary file will always be
deleted after use, regardless of how the DSKEXR
program is terminated. Be sure to turn off data
caching before you run this test.

DSKEXR Dialogue
The following is an example of DSKEXR dialogue:
$ RUN TEST$:DSKEXR
DSKEXR V9.0 RSTS V9.0 EDERE
Disk drive to test? DBl:

Number of test iterations <8>? 1
Detach <No>? NO
No errors detected on

DBl:

F-ll

Device Testing Package (DEVTST)
DSKEXR Errors
DSKEXR reports errors as shown in the following examples:
?(Error message) error at line mm in DSKEXR V9.0
?nn" errors detected on DBn.
where:
(Error message)

is the RSTS/E message in Appendix A of the RSTS/E
System Installation and Update Guide for the error
that occurred.

is the line number where the error occurred in the"
DSKEXR program.

is the number of errors detected by DSKEXR.

When DSKEXR detects errors, do the following:
1.

Check to make sure that the volume is physically mounted and
write-enabled.

Check to make sure that the volume is logically mounted.
This may be verified by the use of the SHOW DISKS command.
If the disk is not mounted, use the MOUNT command (see
Chapter 15).
Caution
Note the following to avoid damage to the system:
o

Packs mounted as unlocked public disks will be
available to other system users for creation and
storage of their files.
Subsequent removal of a
public disk may result in the elimination of
these user files from the system. For this
reason, DIGITAL recommends the use of a private
pack if a nonsystem disk is to be tested.

Never mount a potentially bad disk on another
drive until you are sure that the drive and pack
are free of physical damage.

Persistent errors may be due to bad blocks on the pack. Any
potentially bad blocks will be flagged in the System Error Log
following unsuccessful access, to prevent further access to the INIT
option.

F-12

Device Testing Package (DEVTST)
DSKSEK
This disk exerciser tests the normal operation of non-file-structured
disks by randomly reading blocks from the disk.
It is possible to run
several copies of DSKSEK in order to test several drives
simultaneously or to put a heavier load on any single drive.
If the
disk being tested is a mounted RSTS/E file-structured disk, DSKSEK
will not read the known bad blocks.
If an error occurs on a read
operation, DSKSEK reports it will be reported by DSKSEK and logs it
into the System Error Log.
Note
This is a read-only operation.
before you run this test.

Turn off data caching

DSKSEK Dialogue
The following is an example of DSKSEK dialogue:
$ RUN TEST$:DSKSEK
DSKSEK V9.0 RSTS V9.0 EDERE
Disk drive to test?

DBO:

Number of test iterations <30>?
Detach <No>?

No bad block detections in 1000 sets from

DBO:

DSKSEK Errors
Errors detected by DSKSEK are displayed as

follows~

?(Error message) error at line mm in DSKSEK V9.0.
where:
(Error Message)

is the RSTS/E message in Appendix A of the RSTS/E
System Installation and Update Guide'.

is the BASIC-PLUS line number where the error
occurred in the DSKSEK program.

F-13

Device Testing Package (DEVTST)
When DSKSEK detects errors, do the following:
1.

Check to see if the volume on the testing device is
physically mounted.

If it is, mount another scratch volume on the drive and retry
the operation.
caution
Never mount a potentially bad disk on another
drive until you are sure that the drive and
pack are free of physical damage.

If the test continues to fail, check the System Erro~ Log to
see if bad blocks are recorded.

If bad blocks are recorded, add them to the bad block list on
the disk using the REFRESH BADS suboption of INIT. This can
only be done if the disk has been initialized (DSKINTed) as a
RSTS/E disk.
(See the RSTS/E System Installation and Update
Guide for information on BADS.)

If the problems continue, get a complete listing of the
System Error Log (using the ERRDIS program).

DTEXER
The DEC tape exerciser tests the normal operation of the TCll DECtape
control and TU56 DECtape drives.
DTEXER opens a file on the drive
being tested and fills the file with floating point numbers.
The
program writes 420 blocks (of a possible 578 blocks) on the tape.
Numbers written on the tape are read and checked, keeping a count of
incorrect values.
If at the end of the test the error count is not ·0,
DTEXER prints the error count.
caution
Any information previously contained on the DECtape
used for this test will be destroyed.

F-14

Device Testing Package (DEVTST)
DTEXER Dialogue
The following is an example of DTEXER dialogue:
$ RUN TEST$:DTEXER
DTEXER V9.0 RSTS V9.0 EDERE
Warning: This exerciser will destroy data on the tested DECtape.
Dectape drive to test? DTl:
Number of iterations <2>? 1
Detach <No>? NO
No errors detected on

DTl:

DTEXER Finished at 04:13 PM
$

DTEXER Errors
This device exerciser shows the number of errors found during
operation, as shown in this example:
?mm errors on DTn during iteration nne
where:
mm

is the number of errors detected by the DTEXER program.

DTn

is the name of the device being tested.

is the number of the iteration during which the error
occurred.

When DTEXER detects errors, do the following:
1.

Check to see if the DEC tape on the testing device is
physically mounted and write-enabled.

If it is, mount another scratch DECtape on the drive and
retry the operation.

Check to make sure that the tape path and heads are free of
oxide.

F-15

Device Testing Package (DEVTST)
DXEXER
This exerciser tests the normal operation of the diskette controller
and the specified diskette drives. DXEXER starts by opening the
floppy and writing 420 blocks of floating point numbers to it.
These
are written on the drive being tested, then read back and verified.
The program then displays the number of words written and read, and
the number of errors detected.

caution
DXEXER destroys any information previously contained
on the diskette used for this test.

DXEXER Dialogue
The following is an example of DXEXER dialogue:
$ RUN TEST$:DXEXER
DXEXER V9.0 RSTS V9.0 ED ERE

Warning: This exerciser will destroy data on the tested flexible
diskette.
Flexible drive to test? DXO:
Number of iterations <20>? 2
Detach <No>? NO
Flexible diskette DXEXER I/O data
Device
_DXO:

Words
76.8 K

DXEXER Finished at 10:53 AM

F-16

writes
300

Words
76.8 K

Device Testing Package (DEVTST)
DXEXER Errors
DXEXER shows the number of errors detected during operation as shown
in this example:
?mm errors on DXn during iteration nne
where:
mm

is the number of errors detected by the DXEXER program.

DXn

is the name of the device being tested.

is the number of the iteration during which the error
occurred.

When DXEXER detects errors, do the following:
1.

Check to see if the flexible diskette on the testing device
is physically mounted and the door closed.

If it is, mount another scratch flexible diskette on the
drive and retry the operation.

KBEXER
The keyboard exerciser (KBEXER) is used to test local and remote
terminals connected to the RSTS/E system.
The three terminal tests
are as follows:
o

The Space Test -- Verifies that the terminal carriage will
return reliably from any position

The ASCII Pattern Test -- Verifies that the terminal will
print the standard ASCII character set in all print positions

The Repeat Test -- Repeats everything typed, one line at a
time
Note
You can terminate the tests at any time by pressing
CTRL/C.
You can obtain HELP by typing HELP in answer
to any dialogue question.

F-l7

Device Testing Package (DEVTST)
KBEXER Dialogue
The following is an example of KBEXER dialogue:
$ RUN TEST$:KBEXER
KBEXER V9.0 RSTS V9.0 EDERE
Keyboard to test

< KB68:>? <RET>

Test (SPA[CE), ASC[II), WOR[ST), REP[EAT), HEL[P))? ASC
Number of test iterations <8>? 1
Detach <No>? NO

*** ROTATING ASCII CHARACTERS TEST ***
#$%&' ( ) *+, _ ./0123456789: ; <=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ [\)A
1 "#$%&
"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\];:- 1"*$%
1"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\.];:- 1"#$
1"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\);:- !"#
!"*$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\];:- 1"
;:- !"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\);:- 1
];:- !"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\];:\.);:- !"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\];:[\];:- 1"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\];:Z[\];:- !"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]
YZ[\);:-_ !"#$%&'()*+,-./0123456789:i<=>? @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\

KBEXER Finished at 10:33 AM

KBEXER Errors
Errors detected by KBEXER appear as errors in the keyboard test
patterns. Visually check the patterns for errors.

LPEXER
This exerciser prints a rotating pattern of ASCII characters on a
specified number of pages and is used to test any line printer.

F-18

Device Testing Package (DEVTST)
LPEXER Dialogue
The following is an example of LPEXER dialogue:
$ RUN TEST$:LPEXER
LPEXER v9.0 RSTS V9.0 EDERE

Line printer to test?

LPO:

Number of pages to output <4>?
Detach <No>?

LPEXER finished at 11:38 AM
$

LPEXER Errors
Problems found on the line printer appear as errors in the print-out
of ASCII characters. Visually check the line printer listing and if
an error message is printed by LPEXER, check to make sure that the
·line printer selected is on-line and not out of paper.

MTEXER
The magnetic tape exerciser checks normal operation of the TMll or
TSll magnetic tape controller, the RHll/RH70/TM02/TM03 controller, and
the specified number of 9-track TE1o., TUlO, TS03, TSl1, TUl6, TE16,
TU4S, or TU77 drives. MTEXER allows you to select the drive to be
tested, the length of tape to be written and the number of iterations
to be performed.
For each iteration, MTEXER initializes the tape,
opens a file and writes data until the specified length of tape has
been used. MTEXER then rewinds the tape, opens the file for input,
reads and verifies the data.
If errors are detected, MTEXER prints a
count of the number of bytes found to be incorrect; MTEXER then
proceeds to the next iteration.
The data pattern used is a worst case NRZI pattern for 9-track drives.
The pattern is loaded into a Sl2-byte buffer, and successively greater
numbers of records are written to the magtape until the requested
length of tape has been written.
Furthermore, the pattern base varies
with X so that the contents of the pattern buffer also varies on
successive iterations.

F-l9

Device Testing Package (DEVTST)
Caution
This exerciser overwrites data contained on the
magnetic tape used for the test.

MTEXER Dialogue
The following is an example of MTEXER dialogue:
$ RUN TEST$:MTEXER
MTEXER V9.0 RSTS V9.0 EDERE

Warning:

This exerciser will destroy data on the tested magtape.

Magtape drive to test?

MT2:

Density (800 or 1600) <800>?

<RET>

Number of feet to test <100>?

<RET>

Number of iterations <2>?

Detach <No>?
Magtape MTEXER I/O Data
Device
MT2:

words
99.072 K

Writes
387

Words
99.072 K

No errors detected on _MT2:
$

MTEXER Errors
Magtape errors are reported in these formats:
?~agtape

select error at line nn in MTEXER V9.0.

?MTEXER-Selection error occurred.
where:
nn

is the line number in MTEXER at which the error occurred.

F-20

Device Testing package (DEVTST)
When MTEXER detects errors, do the following:
1.

Check to see if the volume on the testing device is
physically mounted, write-enabled, and assigned to you.

If it is, mount another scratch volume on the drive and retry
the operation.

Check to make sure that the tape path and heads are free of
oxide.

PPEXER
This program tests the normal operation of the paper tape punch by
punching random patterns on the paper tape for input into the PREXER.

PPEXER Dialogue
The following is an example of PPEXER dialogue:
$ RUN TEST$:PPEXER
PPEXER V9.0 RSTS V9.0 EDERE

This test will punch a binary count pattern tape.
The tape will be equivalent to MAINDEC-OO-D2G4 entitled
Special Binary Count Pattern Tape.
Detach <No>? NO
The generated paper tape may be used to test the paper tape
reader.
PPEXER finished at 11:23 AM
$

PPEXER Errors
Problems in the paper tape punch results in an incorrectly generated
paper tape, which is detected byPREXER when the tape is read. If
PPEXER prints an error message, check to see that the paper tape punch
is on line and not out of paper tape.

F-21

Device Testing Package (DEVTST)
PREXER
This program tests the normal operation of the paper tape reader by
reading the paper tape pun~hed by the PPEXER program.

PREXER Dialogue
The following is an example of PREXER dialogue:
$ RUN TEST$:PREXER
PREXER V9.0 RSTS V9.0 EDERE
Load MAINDEC-OO-D2G4-PT or the binary count pattern
tape generated by the punch exerciser into the reader
with the leader under the read station.
Detach <No>? NO
No errors detected on paper tape.
PREXER finished at 11:29 AM
$

PREXER Errors
PREXER reports any errors in this format:
?nn errors detected on paper tape
where:
nn

is the number of errors detected by the PREXER program.
Note
If the paper tape was loaded backwards and the reader
is operating correctly, the following error message
is printed:
?l5360 errors detected on paper tape

Any other errors that PREXER detects may indicate a hardware problem

F-22

INDEX

-A-

ABORT command
OPSER, A-63
SPOOL, A-36, A-48
/ABORT qualifier
STOP/QUEUE/MANAGER command,
9-52
Accessing entries
entry number, 9-9
entry specification, 9-9
Account
associated with system logical
name, 12-12
nonuser, 7-2
programming error in privileged,
2-6
user, 7-2
Account attribute
captive flag, 7-5
dial-up flag, 7-6
network flag, 7-6
Account management
GACNT privilege, 6-4
WACNT privilege, 6-9
Account management, DCL commands,
7-1t
/ACCOUNT_DATA qualifier
BACKUP command, 16-4
RESTORE command, 16-14
/ACCOUNTING_DATA qualifier
SHOW ACCOUNT command, 7-22
Action requests
BATCH, A-57
OPSER, A-13
table of, A-13
/ADDRESS qualifier
INSTALL/LIBRARY command, 12-30
INSTALL/RUNTIME_SYSTEM command,
12-33
/ADVANCED_VIDEO qualifier
SET TERMINAL command, 8-10
AFTER state, processing entries,
9-8
/ALIGN switch, SPOOL, A-51
/ALL qualifier
BROADCAST command, 13-12
DEALLOCATE command, 11-17

/ALL qualifier (Cont.)
DEASSIGN/QUEUE command, 9-27
DELETE/COMMAND/SYSTEM command,
12-27
FORCE command, 13-14
LOAD/OVERLAY command, 14-30
SET CACHE command, 11-21
SET QUEUE command, 9-38
SET SERVER command, 9-41
SHOW ACCOUNT command, 7-22
SHOW DEVICE command, 11-28
SHOW FILE/SYSTEM command, 12-46
SHOW LOGICAL/SYSTEM command,
12-49
SHOW LOGICALS command, 12-48
SHOW PRINTER command, 11-30
SHOW SERVER command, 9-44
SHOW TERMINAL command, 8-20
UNLOAD/OVERLAY command, 14-38
ALLOCATE command, 11-16
/ALLOCATED qualifier
SHOW DEVICE command, 11-28
/ALT MODE qualifier
SET TERMINAL command, 8-10
ANALYS
crash dump data, 10-29
crash error code, 10-29t
CRASH.SYS, 12-22
create error logging file, 10-1
dialogue questions, 10-29t
output, 10-29
run, 10 - 27
running after crash, 3-10
START. COM commands, 10-30
use, 10-27
/ANSI qualifier
SET TERMINAL command, 8-10
ANSWER command
BATCH, A-57
OPSER, A-IS
ASSIGN option, SPOOL, A-33
ASSIGN/QUEUE command, 9-25
ASSIGN/SYSTEM command~ 12-13,
12-24
ATTACH command, 13-10
Attributes, printer forms, 9-17
/AUTOBAUD qualifier
SET TERMINAL command, 8-1, 8-11

Index-1

/AUTOBAUD qualifier (Cont.)
TERSPD.SYS file, 8-3
Automatic restart
after power fail, 2-8
procedures, 2-3
RSTS/E system, 2-3
system initialized, 2-7
Auxiliary run-time system, 12-4
adding, 12-5
creation of, 12-5
removing, 12-6
START.COM, 12-5
-B-

/BACKSPACE qualifier
SET PRINTER command, 11-23
START/SERVER command, 9-49
BACKUP command, 16-3 to 16-11
quick reference table, l6-1lt
Backup sets
restrictions, 16-10
BACKUP, comparison with
SAVE/RESTORE, E-1
Bad blocks
adding to BADB.SYS, 10-10
adding, caution, 10-10
criteria, 10-9
during RESTORE, E-20
end of file, E-9
ERRDIS example, 10-9
ERRDIS prints list, 10-10
ERRDIS report, 10-9
list of potential, 10-5
report content, 10-9
SAVE/RESTORE file changes, E-42
SAVE/RESTORE output, E-41
BADB.SYS file
adding bad blocks, 10-10
Base priority
SET JOB/PRIORITY command, 6-8
TUNE privilege, 6-8
UU.PRI system directive, 6-8
BASIC-PLUS
keyboard monitor, 1-2
run-time system, 12-4
BATCH, A-2
ANSWER command, A-57
answering action requests, A-57
communication paths, A-6
CONTINUE command, A-58
default conditions for, A-53

BATCH (Cont.)
default receiver identification,
A-53
device type designators, A-57t
dismount a volume, A-58
error checking, A-53
interrupt commands, A-56t
logical device name, A-52
modules, A-52
mount requests, A-57
OPSER communicate with, A-55
OPSER package, A-52
overview, A-6
processing command file, A-57
processor, A-52
pseudo keyboard, A-52
requests for operator action,
A- 56
run, A-52
start-up options, A-54t
start-up procedures, A-56
Batch jobs, exit status messages,
9-16
/BATCH qualifier
INITIALIZE/QUEUE command, 9-31
SET SERVER command, 9-41
SHOW SERVER command, 9-44
Batch servers
CPU limits, 9-16
Print/Batch Services (PBS), 9-3,
9-15
pseudo keyboards, 9-15
time limits, 9-16
wildcard names, 9-15
BATCH.DCD file
command decoding, A-6
/BELL qualifier
BROADCAST command, 13-12
Bit 0, setting, 2-7
/BLOCK SIZE qualifier
BACKUP command, 16-5
Bootable medium, create with
SAVE/RESTORE, E-34
Bootstrap
RSTS/E after system halt, 2-3
RSTS/E into memory, 2-2
Bootstrap 'procedure, 2-2
/BREAK qualifier
SET TERMINAL command, 8-11
/BRIEF qualifier
SHOW ACCOUNT command, 7-23
SHOW SERVER command, 9-44

Index-2

/BRIEF qualifier (Cont.)
SHOW TERMINAL command, 8-20
BROADCAST command, 13-3, 13-11
SEND privilege, 6-6
/BROADCAST qualifier
SET TERMINAL command, 8-11
/BROADCAST qualifier, permits
receiving broadcasts, 8-7
Bucket size
cache, 11-13
RMS, 11-14
Buffer status report, SHOW
BUFFERS command, 12-20
/BUFFER_QUOTA qualifier
SET TERMINAL command, 8-11
/BUFFER_SIZE qualifier
BACKUP command, 16-5
RESTORE command, 16-14
/BUFFERS qualifier
SET CACHE command, 11-21
Burst pages, A-34
BYE command, CCL, 3-9
-C-

Cache
clusters in, 11-10
data block, 11-9
size of, 11-10
space for, 11-10
updated by the monitor, 11-10
Cache cluster
eligible for replacement, 11-11
last block in, 11-11
size of, 11-10, 11-19
specify size of, 11-20
/CACHE qualifier
SET FILE command, 12-43
Caching

see also Data caching
see also Directory caching
checks by monitor, 11-19f
directory, 11-9
efficiency of, 11-13
guidelines, 11-13, 11-14
MODE checks, 11-13
optimize directory, 11-14
override UFD entry, 11-13
random mode, 11-11
RMS indexed file, 11-14
sequential mode, 11-11
types, 11-9

Caching (Cont.)
UFD entry marked for, 11-11
Caching Control, DCL commands,
II-It
Captive account flag, 7-5
/CAPTIVE qualifier
CREATE/ACCOUNT command, 7-9
SET ACCOUNT command, 7-17
Catastrophic error, 2-3, 2-7
automatic recovery, 2-7
automatic recovery from, 2-5
cause, 2-5, 2-7
handling, 2-7
recovery, 2-7
CCL (Concise Command Language)
adding CCL commands, 12-14
adding in. sequence, 12-16
BYE command, 3-9
command definition, 3-9'
defined at start of ti~e
sharing, 12-14
definition, 1-1
error checking, 12-15
HELLO command, 3-9
listing, 12-16
PLEASE, A-61
redefining, 3-9
removing CCL commands, 12-17
run RSTS/E programs, 12-14
use of small buffers, 3-9
CCL command, definition, 12-14
Central processing Unit

see CPU
CHANGECONSOLE command
OPSER, A-17
CHARS.QUE file, A-48
character generation, A-6
/CLOSE qualifier
DETACH command, 13-13
INITIALIZE/QUEUE command, 9-31
CLOSE/QUEUE command, 9-26
Cluster size
cache and pack, relationship,
11-12
cache and RMS bucket size,
11-13
disk type, 15-8t
/CLUSTER SIZE qualifier
CREATE/ACCOUNT command, 7-9
INITIALIZE command, 15-8
/CLUSTERSIZE qualifier
SET CACHE command, 11-21

Index-3

/132_COLUMNS qualifier
SET TERMINAL command, 8-10
Command file
QUEMAN start-up, A-26
system start-up, 3-3
Command level
system, 1-11
terminal at, 1-11
Command line, full function
(RESTORE), E-34
Commonly Used System Program
see CUSP
Concise Command Language
see CCL
Console terminal
ability to log on to, 13-2
change, 13-2
run SHUTUP from, 4-1
CONTINUE command
BATCH, A-58
/CONTROL qualifier
SET TERMINAL command, 8-11
Controlled access
privilege, 1-11
/CONTROLS qualifier
INITIALIZE/SERVER command, 9-34
SET PRINTER command, 11-24
SET SERVER command, 9-42
CPEXER program
CPU exerciser, short, F-5
CPU integrity test, F-6
EIS operation test, F~6
example dialogue, F-7
FPP test, F-6
LOG feature requirement, F-7
PEEK function test, F-6
tests performed, F-6
TRIG feature requirement, F-7
type four errors, F-9
type one errors, F-7
type three errors, F-8
type two errors, F-8
CPU (Central Processing Unit)
determine the state of, 2-5
CPU exerciser, F-5
CPU integrity test
CPEXER program, F-6
/CPU_LIMIT qualifier
INITIALIZE/QUEUE command, 9-31
SET QUEUE command, 9-38
.CPUTST program, F-9
errors, F-I0

CPUTST program (Cont.)
example dialogue, F-IO
/CR PREFIX qualifier
SET PRINTER command, 11-24
Crash
analyzing system, 10-27
causes of system, 2-7
documenting system, 10-27
error code, 10-29
handling of system, 2-7
memory dump, annotated version,
10-29
OPSER starts after system, A-18
random system, 2-7
running QUEMAN after system,
A-27
system, 2-3, 2-7
Crash file
CRASH.SYS, 12-22
information from, 10-1
CRASH.SYS file, 10-1, 10-27
crash dump, 12-22
Create access
GWRITE privilege, 6-4
WWRITE privilege, 6-10
CREATE/ACCOUNT command, 7-8
/CREATED qualifier
BACKUP command, 16-5
RESTORE command, 16-15
/CRFILL qualifier
SET TERMINAL command, 8-12
CTRL/C
do not use in QUEMAN, A-23
FORCE, 13-4
SAVE/RESTORE dialogue, E-8
typed at terminal, 1-11
CTRL/Z
FORCE command, 13-5
SAVE/RESTORE dialogue, E-8
CUSP (Commonly Used System
Program)
definition, 1-3
-D-

Data access, cached, 11-11
Data block
cache, 11-9
retrieval pointer, 11-3
Data caching

Index-4

see also caching
cache clusters used, 11-20

Data caching (Cont.)
control, 11-9
disabling, 11-20
enable on the system, 11-18
guidelines, 11-12
memory access, 11-9
minimum residency time, 11-15
MODE values, 11-9
monitor directives, 11-9
read operations, 11-9
restriction with DSKSEK program,
F-13
RMS files, 11-14
support for, 11-9
write operations, 11-9
XBUF allocation, 11-10
/DATA MAXIMUM qualifier
SET-CACHE command, 11-21
/DATE qualifier
INITIALIZE command, 15-9
/DATE_FORMAT qualifier
SET SYSTEM command, 14-32
DATES privilege
system clock, 6-3
DCL (DIGITAL Command Language)
caution when defining, 3-9
CCL commands, 3-9
definition, 1-1
keyboard monitor, 1-2
DCL command descriptions
account management, 7-7 to 7-25
BACKUP, 16-3 to 16-11
caching control, 11-15 to 11-30
device management, 11-15 to
11-30
disk handling, 15-3 to 15-25
job management, 13-9 to 13-22
managing logical names, 12-23
to 12-52
managing system files, 12-23 to
12-52
Print/Batch Services Package
(PBS), 9-24 to 9-54
RESTORE, 16-12 to 16-21
system functions, 14-28 to
14-38
tape handling, 15-3 to 15-25
terminal management, 8-8 to
8 - 21 .
DCL commands
account management, 7-1t
disk handling, 15-1t

DCL commands (Cont.)
job management, 13-1t
logical names, managing, 12-1t
Print/Batch Services package
(PBS), 9-1t
system files, managing, 12-lt
system functions, 14-1t
tape handling, IS-It
DEALLOCATE command, 11·-17
DEASSIGN/QUEUE command, 9-27
DEASSIGN/SYSTEM command, 12-25
logical name, 12-13
DECnet/E
crash analysis, 10-29
disabling
during shutdown, 4-5, 4-7
logins, 4-4
EVTLOG
program, 4-7
shutdown phase, 4-11
interrupt shutdown, 4-8
Network Services Protocol file,
12-21
resetting shutdown status, 4-8
shutdown, 4-7
example, 4-16
phase, 4-7
use of NCP, 4-8
DECnet/E Network Services
Protocol
see NSP
DECtape Exerciser program
see DTEXER program
/DEFAULT qualifier
INITIALIZE/QUEUE command, 9-32
SET QUEUE command, 9-38
Default queues
Print/Batch Services, 9-4
DEFINE/COMMAND/SYSTEM command,
12-14, 12-26
/DELETABLE qualifier
SET FILE command, 12-44
DELETE/ACCOUNT command, 7-13
DELETE/COMMAND/SYSTEM command,
12-17, 12-27
DELETE/QUEUE command, 9-28
DELETE/SERVER command, 9-29
Delimiter·
keyboard, 13-7
/DELIMITER qualifier
SET TERMINAL command, 8-12

Index-5

/DENSITY qualifier
BACKUP command, 16-6
INITIALIZE command, 15-15
SET SYSTEM command, 14-32
/DENSITY switch, SAVE/RESTORE,
E-10
Description block, run-time
system, 12-6, 12-8
DETACH command, 13-9, 13-13
OPSER, A-17
QUEMAN, A-22
Detached job
check with SYSTAT, 14-8
SHOW JOBS/DETACHED command,
14-8
Detached-job quota, 5-4
/DETACHED_JOB_QUOTA qualifier
CREATE/ACCOUNT command, 7-9
SET ACCOUNT command, 7-17
Device designators, F-3t
table of BATCH, A-57t
Device management, DCL commands,
II-It
DEVICE privilege
restricted device, 6-3
Device sizes, disk type, C-1t
Device testing package
definition, F-1
Device Testing Programs
see DEVTST programs
/DEVICE_TYPE qualifier
SET PRINTER command, 11-24
SET TERMINAL command, 8-12
DEVTST programs, F-3t
conventions, F-2
error messages, F-5t
how to run, F-2
/DFLENGTH switch
effect on line printer, A-36
effect on terminals, A-36
SPOOL, A-35
Dial-up flag
account attribute, 7-6
dial-up line
ring characteristics, 8-7
set characteristics, 8-7
/DIALUP qualifier
CREATE/ACCOUNT command, 7-9
SET ACCOUNT command, 7-17
SET TERMINAL command, 8-12
Digital Command Language
see DCL

Directory
fragmentation, 1-10
minimize search overhead, 1-10
reducing accesses, 11-3
restructure with REORDR, 11-2
Directory caching, 11-9
see also Caching
cache clusters used, 11-20
enable on the system, 11-18
GFD, 11- 9
MFD, 11- 9
optimize, 11-14, 12-18
overlay code, 11-9
UFD, 11-9
Directory structure
optimizing on disk, 11-3
prevent a damaged, 11-6
/DIRECTORY MAXIMUM qualifier
SET CACHE command, 11-21
Dirty disk
rebuilding with MOUNT, 15-19
when dirty bit is set, 15-16
/DISABLE qualifier
SET CACHE command, 11-21
SET DEVICE command, 11-22
Disk
copy to one that contains bad
blocks, E-1
copying with IMAGE, E-26
create bootable system, E-l
create fast copy, E-l
differences between Level 0 and
Level 1, 1-9
directory entries scattered,
11-2
dismount under SHUTUP, 4-12
formatting with DSKINT option
of INIT.SYS, 15-2
free space, 14-8
IMAGE output as system, E-27
legal with IMAGE,E-26
MFD on system, 1-10
optimizing, 1-10
directory structure, 11-3
organization, 1-4
options, 1-4
private, 1-5, 1-10
rebuilding a dirty disk with
MOUNT, 15-16
rebuilding with MOUNT com~and,
15-19
reorder disk structure, 11-5

Index-6

Disk (Cont.)
reorder in public structure,
11-5
restoring, E-20
restructure directories, 11-2
SAVE Set, E-2
statistics (DISPLY), 14-21
status statistics, 14-21
stopping an RC25, 14-2
system, 1-3, 1-4
types, 1-4
Disk characteristics, INITIALIZE
display, 15-12
Disk exerciser test
DSKEXR program, F-IO
Disk handling, DCL commands,
IS-It
Disk Quota
operations, 5-2
Disk quota
attribute block, 5-1
logged-in, 5-2
logged-out, 5-2, 5-3
Disk Quotas, 5-1
Disk quotas, 5-1
Disk size, disk type, 15-8t
Disk type, device sizes, C-1t
Diskette controller test
DXEXER program, F-16
DISMOUNT command
disks, 15-4
tapes, 15-6
Display program
see DISPLY
DISPLY
abbreviations in DISPLY report,
14-18
account location, 14-9
buffer status report, 12-20
busy device statistics, 14-20
commands, 14-12t to 14-15t
detached, 14-10
disk status abbreviations,
14-22t
disk structure statistics,
14-21
example, 14-16
free buffers, 14-24
information displayed, 14-11
INTERVAL question, 14-9
job status statistics, 14-18
memory status, 14-27

DISPLY
memory status (Cont.)
abbreviations, 14-28t
message receivers, 14-23
abbreviations, 14-24t
resident libraries, 14-27
abbreviations, 14-26t
restrict use, 14-9
run-time systems, 14-25
abbreviations, 14-26t
running, 14-9
screen layout, 14-15
STATE column abbreviations,
14-19t
stop execution, 14-11
switches, 14-10t
titles used in report, 14-18
use, 14-7
WHY column abbreviations,
14-21t
DSKEXR program
disk exerciser test, F-10
errors, F-12
example dialogue, F-11
DSKSEK program
data caching restriction, F-13
error messages, F-13
example dialogue, F-13
non-file~structured disks test,
F-13
DTEXER program
error messages, F-15
example dialogue, F-15
TCl1 DEC tape test, F-14
DUMP/SYSTEM command, 12-22, 12-28
DXEXER program
diskette controlle~ test, F-16
error messages, F-17
example dialogue, F-16
-E-

/EIGHT BIT qualifier
SET PRINTER command, 11-24
SET TERMINAL command, 8-13
EIS operation test
CPEXER program, F-6
EMT
definition, 14-4
that cannot be logged, 14-5
EMT logging, 14-4
data contained in packet, 14-6

Index-7

EMT logging (Cont.)
data returned, 14~6
how to program, 14-5
packet, 14-6
reasons for using, 14-4
shutdown under SHUTUP, 4-12
system security, 14-7
/ENABLE qualifier
SET CACHE command, 11-21
SET DEVICE command, 11-22
END command, OPSER, A-62
/END qualifier
BACKUP command, 16-7
RESTORE command, 16-15
Entry number, accessing entries,
9-9
Entry specification, accessing
entries, 9-9
/EOT qualifier
SET PRINTER command, 11-24
/ERASE qualifier
INITIALIZE command, 15-9
ERR.SYS file
allocate and position, 12-18
ERRCPY
activating, 10-2
active during time sharing,
10-2
error message from SHUTUP, 10-4
messages queued, 10-4
minimize size, 10-1
number of messages queued, 10-1
processing error messages, 10-4
shutdown procedures, 4-11
shutdown under SHUTUP, 4-11
total errors received, 10-12
use, 10-2
ERRCRS.FIL
error logging file, 10-1
ERRDET
criteria for bad blocks, 10-9
report content, 10-9
ERRDET module
ERRDIS, 10-5
ERRDIS
bad blocks, 10-10
example, 10-9
potentially, 10-5
report, 10-9
categories of errors, 10-11
detailed report, 10-4
dialogue explanations, 10-st

ERRDIS (Cont.)
disk error description, 10-16t
error code mnemonic, 10-11
error file, zero contents, 10-5
error sequence number, 10-11
error title line, 10-11
full report, 10-11
examples, 10-12 to 10-25
functions, 10-4
modes, optional, 10-5
modules, 10-5
nondisk peripheral device
format, 10-22, 10-23t
nonperipheral error
description, 10-24
format, 10-26t
running, 10-5
summary report, 10-4, 10-8
user description data, 10-12,
10-13t
ERRINT
chains to ERRCPY, 10-3
change the maximum size, 10-3
command file, 10-2
example of dialogue, 10-3, 10-4
location of program, 10-3
run, 10 - 2
run at start-up, 3-7
validates error file, 10-1
ERRLOG.FIL file, 10-2
stores error messages, 10-1
Error file
adding, 12-22
initialization, 10-2
removing, 12-22
SHOW FILE/SYSTEM command, 12-21
validation, 10-2
zero, 10-5
Error logging, 2-7
creation of file, 10-1
ERRCPY, 10-4
hardware errors, 10-1
initial conditions for system,
3-7
initialization, 10-2
software errors, 10-1
use of programs, 10-2
Error messages
processing, 10-1
processing with ERRCPY, 10-4
SAVE/RESTORE, E - 42t,
nonfatal transfer, E-sO

Index-8

Error messages (Cont.)
SPOOL, A-49
syntax, A-39, A-39t
Error package
programs in System, 10-1
Error trap
infinite loop, 2-7
two categories, 2-7
unexpected, 2-7
/ERROR_FILE qualifier
SHOW FILE/SYSTEM command, 12-46
/ERROR_LOGGING qualifier
INSTALL/LIBRARY command, 12-31
INSTALL/RUNTIME_SYSTEM command,
12-34
Errors
catastrophic, 2-3, 2-7
automatic recovery, 2-7
causes, 2-7
handling, 2-7
categories of reported (ERRCPY),
10-11
checking eCL command, 12-15
detailed report, 10-4
detection in RSTS/E monitor,
10-1
disk (ERROIS), 10-11
displaying, 10-4
example of MSCP in full report
(ERROIS), 10-19 to 10-22
logging, 10-1
missed (ERRCPY), 10-12
MSCP in full report (ERROIS),
10-19
nondisk peripheral device,
10-12
nonperipheral, 10-11, 10-24
privileged job programming, 2-6
recovery from line printer,
A- 47
SAVE/RESTORE, E-41
SAVE/RESTORE input volume,
E-11t
summary report, 10-4
summary report (ERROIS), 10-8
total received by ERRCPY, 10-12
/ESCAPE_SEQUENCE qualifier
SET TERMINAL command, 8-13
Event logger
OECnet/E, 4-8
EVTLOG program
OECnet/E example, 4-16

EVTLOG program (Cont.)
DECnet/E shutdown, 4-7
resetting shutdown status, 4-8
shutdown phase, 4-11
/EXCLUDE qualifier
BACKUP command, 16-7
RESTORE command, 16-16
Execute access
GREAD privilege, 6-4
WREAD privilege, 6-9
Executive
definition, 1-2
/EXERCISE qualifier
INITIALIZE command, 15-10
Exit status, Batch jobs, 9-16
/EXPIRE qualifier
CREATE/ACCOUNT command, 7-9
SET ACCOUNT command, 7-17
EXQTA privilege
logged-in quota, 6-4
logged-out quota, 6-4
Print/Batch Services (PBS), 9-7
Extended buffer pool
see XBUF
Extended Instruction Set
see EIS
-F-

FDF
form characteristics, 9-17
/FORMS qualifier, 9-17
Print/Batch Services (PBS),
9-18
File
accounting information, A-48
add swap file, 12-18
bad block, 10-10
bad cluster while transferring
contiguous, E-21
'caching, 11-14
contiguous, 11-14
random mode, 11-11
sequential mode, 11-11
cannot remove or add NSP, 12-21
commands
start-up, A-17
directory entries, 11-2
disk structure, 1-5, 1-10
high access (definition), 11-15
minimize access overhead in
data, 1-10

Index-9

File (Cont.)
Network Services Protocol,
12-21
read from sequentially cached,
11-11
remove swap file, 12-18, 12-20
run request with no file type,
12-8
SIL, 12-9
structures, 1-5
swap file, 1-11
system control, 12-17
File access
SYSIO privilege, 6-7
/FILE qualifier
SET CACHE command, 11-21
/FILE_DATA qualifier
BACKUP command, 16-7
RESTORE command, 16-16
/FILE_END qualifier
STOP/SERVER command, 9-54
/FILL qualifier
SET PRINTER command, 11-25
FIP small buffer
DISPLY report, 14-24
use for CCL, 3-9
FORCE
CTRL/C, 13-4
example, 13-5
FORCE command, 13-4, 13-14
Form characteristlcs
Forms Definition File (FDF),
9-17
FORM command
SPOOL, A-51
Form length
line printer, A-36
FORM option
SPOOL, A-34
/FORM_FEED qualifier
SET TERMINAL command, 8-13
/FORMAT qualifier
INITIALIZE command, 15-15
Formatting
disks requiring system shutdown,
15-2
Forms alignment
changing, A-51
during time sharing, A-34
procedures, A-34
Forms control, A-35

Forms Definition File

see FDF
/FORMS qualifier
Forms Definition File (FDF),
9-17
INITIALIZE/QUEUE command, 9-32
INITIALIZE/SERVER command, 9-35SET QUEUE command, 9-39
SET SERVER command, 9-42
/FORWARDSPACE qualifier
START/QUEUE/MANAGER command,
9-50
FPP test
CPEXER program, F-6
/FULL qualifier
SHOW ACCOUNT command, 7-23
SHOW SERVER command, 9-45
SHOW TERMINAL command, 8-20
-G-

GACNT privilege
account management, 6-4, 6-9
General small buffer
DISPLY report, 14-24
missed errors, 10-12
SPOOL error, A-40
use for CCL, 3-9
GFD (Group File Directory)
with MFD and UFDs in Level 1,
1-8f
GREAD privilege
execute access, 6-4
read access, 6-4
/GROUP SIZE qualifier
BACKUP command, 16-7
GWRITE privilege
create access, 6-4
rename access, 6-4
write access, 6-4
-H-

HANGUP command, 13-9, 13-15
/HANGUP qualifier
SET SYSTEM command, 14-33
/HARDCOPY qualifier
SET TERMINAL command, 8-13
Hardware
malfunctions, 2-6
Hardware controller
terminal device designator, 8-3

Index-10

Hardware errors
logging, 10-1
/HEADER qualifier
BROADCAST command, 13-12
Heading burst pages, A-34
HELLO command, CCL, 3-9
Help report
ERRDIS (example), 10-7
/HOLD qualifier
SET JOB command, 13-20
SET SYSTEM command, 14-33
HOLD state
processing entries, 9-8
/HOSTSYNC qualifier
SET TERMINAL command, 8-13
HWCFG privilege
SET TERMINAL command, 8-4
system manager function, 6-4
terminal characteristics, 8-4
HWCTL privilege
system control, 6-5
-1-

IDENTIFY, E-4t
dialogue, E-32t
example, E-33
IMAGE, E-4t
dialogue, E-27t
example, E-29 to E-32
extracting pack ID, E-32t
output from, as system disk,
E-27
run statistics, E-40
SAVE/RESTORE, E-26
Immediate mode
shutting down OPSER, 4-10
/IN LABEL qualifier
BACKUP command, 16-8
RESTORE command, 16-16
/IN_QUOTA qualifier
CREATE/ACCOUNT command, 7-9
SET ACCOUNT command, 7-17
/INCLUDE qualifier
BACKUP command, 16-8
RESTORE command, 16-16
/INDEX qualifier
INITIALIZE command, 15-10
Indexed file
caching, 11-14
INIT
command, 2-7

INIT (Cont.)
start OPSER, A-17
INIT.BAS program
OPSER shutdown conditions, 4-10
INIT.SYS file
copies to disk, E-34
SAVE/RESTORE tape, E-9
INIT.SYS program
control file, 3-1
DSKINT option to format disks,
15-2
use, 2-1
Initialization code
bootstrapped, 2-1
RSTS/E, 2-2
START option, 3-1
Initialization options
discussion, 1-4
requesting, 2-3
summary, 2-3t
INITIALIZE command
/DENSITY qualifier, 15-15
disks, 15-7 to 15-13
display of disk characteristics,
15-12
/FORMAT qualifier, 15-15
QUEMAN, A-2l
tapes, 15-14
/INITIALIZE qualifier
BACKUP command, 16-8
RESTORE command, 16-16
INITIALIZE/QUEUE command, 9-30
INITIALIZE/SERVER command, 9-34
Initializing disks
INITIALIZE command, 15-7 to
15-13
overview, 15-2
Initializing tapes
INITIALIZE command, 15-14
overview, 15 - 2
/INQUIRE qualifier
SET TERMINAL command, 8-14
INSTAL privilege
defining CCLS, 12-14
system commands, 6-5
system files, 6-5
system logical names, 6-5
INSTALL/ERROR_FILE command, 12-22,
12-29
INSTALL/ERRORFILE command, 12-18
INSTALL/LIBRARY
DCL command, 12-10, 12-11
Index-II

INSTALL/LIBRARY (Cont.)
/LOCK qualifier, 12-11
/[NO]ADDRESS[=n] qualifier,
12-10
INSTALL/LIBRARY command, 12-30
INSTALL/OVERLAY FILE command,
12-18, 12-21, 12-32
INSTALL/RUNTIME_SYSTEM
/ADDRESS=n qualifier, 12-6
/LOCK qualifier, 12-8
/MAXIMUM=s qualifier, 12-8
/MINIMUM=s qualifier, 12-8
/[NO]ERROR_LOGGING qualifier,
12-6
/[NO]KEYBOARD_MONITOR qualifier,
12-6
/[NO]READ_ONLY qualifier, 12-6
/[NO]SHAREABLE qualifier, 12-6
/[NO]UNLOAD qualifier, 12-6
/POSITION qualifier, 12-7
/PREFIX=n qualifier, 12-6
INSTALL/RUNTIME SYSTEM command,
3-8, 12-5, 12-6, 12-33
errors, 12-7
INSTALL/RUNTIME SYSYTEM
/TYPE qualifier, 12-8
INSTALL/SWAP_FILE
errors, 12-20
/SIZE=n qualifier, 12-19
INSTALL/SWAP_FILE command, 12-18,
12-36, 13-3
/INTERACTIVE qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-17
SET TERMINAL command, 8-14
INTERRUPT command
OPSER, A-IS, A-16, A-23t, A-61
response to, A-16
Interrupt commands
BATCH, A-56t
SPOOL, A-41
-J-

Job
accounting information, A-48
check detached, 14-8
check number of, 14-9
compute bound, 13-8
definition, 1-2
executing a read request, 11-3
header, A- 48

Job (Cont.)
keyboard monitor, 1-2
limit of spooling, A-28
maximum (JOB MAX), 12-20
maximum assigned size, 13-8
number allowed, 12-20
OPSER checks online, A-7
OPSER table, A-2
priority, 13-8
run burst, A-44
set maximum size, 13-6
setting priority, 13-6
status statistics, 14-18
suspend, 13-6
Job area
size, 1-11
user, 1-11
Job control
SHOW USER command, 13-6
JOB MAX
restricts jobs, 12-20
/JOB qualifier
ALLOCATE command, 11-16
Job quota, 5-4
detached-job, 5-4
log-in request, 5-5
Job quotas, 5-1
Job run burst, 13-7
Job status, SYSTAT, 14-8
Job table, SHUTUP, 4-8
/JOB END qualifier
STOP/SERVER command, 9-54
/JOB QUOTA qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-17
JOBCTL privilege
system control, 6-5

/KATAKANA qualifier
SET TERMINAL command, 8-14
KBEXER program
errors, explanation, F-18
example dialogue, F-18
local terminals test, F-17
remote terminals test, F-17
terminal tests, F-17
/KEBOARD MONITOR qualifier
SET JOB command, 13-20
/KEEP qualifier
SET CACHE command, 11-21

Index-12

/KEEP=n qualifier
minimum residency time, 11-15
Keyboard
controlling, 13-9
default SPOOL values, A-38
delimiter, 13-7
monitor, 1-11
spooling, A-38
start-up on LA180, A-46
start-up on LA36, A-45
Keyboard monitor, 3-9
change with SWITCH, 1-2
default (definition), 1-2
definition, 1-2
job, 1- 2
process command, 1-10
/KEYBOARD_MONITOR qualifier
INSTALL/RUNTIME_SYSTEM command,
12-34
KILL
UTILTY program, A-63
-L-

LA180
form length, A-36
start-up keyboard on, A-46
LA36
start-up keyboard on, A-45
/LABEL qualifier
SET SYSTEM command, 14-33
Label, specified for tapes
DISMOUNT command, 15-6
INITIALIZE command, 15-14
MOUNT command, 15-23
Level 0, 1-7f
compared to Levell, 1-9
Level 1
compared to Level 0, 1-9
three structures involved, 1-8
Library
remove resident, 12-11
resident, 12-9
LIBRARY keyword, 12-10
Line printer
default SPOOL values, A-37
/DFLENGTH switch effect, A-36
distinction from terminal, A-37
form length, A-36
output, A-48
recovery from errors, A-47
requests for output, A-6

Line printer (Cont.)
spooling, A-29, A-37
start-up
all defaults, A-42
narrow width, A-43
Line printer test
LPEXER program, F-18
/LINE_NUMBER qualifier
DEFINE/COMMAND/SYSTEM command,
12-26
LIST command
OPSER, A-16
LIST JOBS command
OPSER, A-16, A-61
LIST OPERATORS command
OPSER, A-16
/LIST FILE qualifier
BACKUP command, 16-9
RESTORE command, 16-17
Load address
run-time system, 12-6
LOAD/OVERLAY command, 14-29
/LOADABLE_CHARACTERS qualifier
SET TERMINAL command, 8-14
Local terminal test
KBEXER program, F-17
/LOCAL_ECHO qualifier
SET TERMINAL command, 8-14
/LOCK qualifier
INSTALL/LIBRARY command, 12-31
INSTALL/RUNTIME_SYSTEM command,
12-34
/LOG qualifier
CREATE/ACCOUNT command, 7-10
DELETE/ACCOUNT command, 7-13
SET ACCOUNT command, 7-18
SET FILE command, 12-44
SET PASSWORD command, 7-21
LOGFILE command
OPSER, A-17
Logged-in quota, 5-2
EXQTA privilege, 6-4
Logged-out quota, 5-2, 5-3
EXQTA privilege, 6-4
/LOGGED_IN qualifier
BROADCAST command, 13-12
FORCE command, 13-14
Logical device
BATCH, A-52
SPOOL, A-30
Logical end mode
shutdown of OPSER, 4-10

Index-13

Logical name
account number associated,
12-12
adding new, 12-13
ASSIGN/SYSTEM command, 12-13
DEASSIGN/SYSTEM command, 12-13
job related, 12-11
l~st, 12-14
system, 12-11
system defined, 12-12
unique, 12-12
Logical Names
managing with DCL commands,
12-lt
LOGIN
set priority, 13-7
LOGIN command, 13-16
Login command file
LOGIN.COM, 6-11
LOGIN. COM
login command file, 6-11
Logins
decrease the number of, 12-20
limit, 13-2
limit for DECnet/E, 4-5
limit under SHUTUP, 4-5
limiting, in SHUTUP, 4-5
restrict, 13-2
restricted by swap space, 12-20
swap file space affects, 12-20
SWCTL privilege, 6-7
/LOGINS qualifier
SET SYSTEM command, 13-21
LOGOUT command, 13-16
/LOOKUP qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-18
/LOWERCASE qualifier
SET PRINTER command, 11-25
SET TERMINAL command, 8-15
LPEXER program
errors, explanation, F-19
example dialogue, F-19
line printer test, F-18
-M-

Magnetic tape
density for Save Set, E-37
/DENSITY switch, E-I0
lowest density allowed, E-9
SAVE Set, E-2, E-36

Magnetic tape (Cont.)
SAVE/RESTORE requirements, E-9
valid medium (SAVE/RESTORE),
E-9
Magnetic tape exerciser
See MTEXER program
MAKSIL' program
formats disk file, 12-9
Management
RSTS/E system, 1-3
Mass Storage Control Protocol
see MSCP
Master File Directory
see MFD
/MAXIMUM qualifier
SET CACHE command, 11-21
/MAXIMUM SIZE qualifier
INSTALL/RUNTIME_SYSTEM command,
12-34
Memory
adding resident library, 12-11
available range of, 12-7
avoiding fragmentation, 12-6
dump, 10-27
fragmentation, 12-7
high, 12-7
low, 12-7
status statistics, 14-27
Memory access
data caching, 11-9
Memory dump
annotated version, 10-29
critical contents, 10-29
MESSAGE command
OPSER, A-13, A-17
Message quota, 5-5
Message receiver
OPSER, A-2
QUEMAN declares self, A-20
Message receivers
abbreviations (DISPLY), 14-24
statistics (DISPLY), 14-23
/MESSAGE QUOTA qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-18
Messages
% characters, D-l
? characters, D-l
general, D-l, D-2t to D-49t
informational, D-2
severe error, D-l
standard error, D-l

Index-14

Messages (Cont.)
warning, D-1
MFD (Master File Directory)
and UFDs in Level 0, 1-7f
with GFDs and UFDs in Levell,
I-Sf
/MFD_CLUSTER_SIZE qualifier
INITIALIZE command, 15-11
Micro/RSTS spooler

see also SPL
/MINIMUM_SIZE qualifier
INSTALL/RUNTIME_SYSTEM command,
12-34
Missed errors
reported to ERRCPY, 10-12
MODE values
data caching, 11-9
/MODIFIED qualifier
BACKUP command, 16-5
RESTORE command, 16-15
Monitor
caching checks, 11-19f
control of run-time system,
12-4
default keyboard, 1-2
definition, 1-2
directives (data caching), 11-9
error detection, 10-1
job keyboard, 1-2
keyboard, 1-2
symbols (list), 10-29
take online dump, 12-22
update cache, 11-10
MOUNT command (disks), 15-16
/[NO]QUOTA qualifier, 15-19
/[NO]REBUILD qualifier, 15-19
/[NO]RESTRICT qualifier, 15-21
/[NO]SHARE qualifier, IS-1St,
15-21
/[NO]WRITE qualifier, 15-22
/PRIVATE qualifier, 15-17,
IS-1St
/PUBLIC qualifier, 15-17,
IS-1St
MOUNT command (tapes), 15-23
/DENSITY qualifier, 15-24
/FORMAT qualifier, 15-24
/[NO]WRITE qualifier, 15-25
MOUNT privilege
public disk, 15-16
shared disks, 6-5

Mounting disks
DISMOUNT (disks), 15-4
MOUNT command (disks), 15-16 to
15-22
overview, 15-3
Mounting tapes
DISMOUNT (tapes), 15-6
MOUNT (tapes), 15-23
overview, 15-3
MSCP
ERRDIS full report, 10-19
example, 10-19 to 10-22
MTEXER program
error messages, F-20
example dialogue, F-20
magnetic tape controllers test,
F-19
magnetic tape drives test, F-19
-N-

NAME option
SPOOL, A-34
INAME qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-1S
SET SYSTEM command, 14-33
NCP
network shutdown, 4-S
Network
shutdown of DECnet/E, 4-7
Network Control Program
see NCP
Network management
SWCTL privilege, 6-7
/NETWORK qualifier
CREATE/ACCOUNT command, 7-10
SET ACCOUNT command, 7-1S
Network Services Protocol

see NSP
/NETWORK FILE qualifier
SHOW FILE/SYSTEM command, 12-46
NEXT command
error in, A-26
error text, A-26t
QUEMAN, A-26
/NEXT_JOB qualifier
START/QUEUE/MANAGER command,
9-50
/NOBROADCAST qualifier, prevents
receiving broadcasts, 8-7

Index-IS

/NOCONTIGUOUS qualifier
SET FILE command, 12-44
Non-file-structure disk test
DSKSEK program, F-13
Non-file-structured I/O
RDNFS privilege, 6-5
WRTNFS privilege, 6-9
Nonuser account, ?-2
NORMAL option
changing in SPOOL, A-34
SPOOL, A-34
NSP (Network'Services protocol)
cannot remove or add, 12-21
Number conversion, bit position,
B-1
-0-

/OCCURRENCE qualifier
RESTORE command, l6-l?
Octal Debugging Tool
see ODT
ODT (Octal Debugging Tool)
setting breakpoints with, 12-6
/OMIT_CR qualifier
SET PRINTER command, 11-25
ONLCLN
perform disk cleaning, E-ll
OPEN/QUEUE command, 9-36
Operating system
definition, 1-2
OPERATOR command
OPSER, A-I?
Operator communication program,
A- 58
Operator services
BATCH, A-2
flowchart, A-4f
OPSER, A-2, A-?
overview, A-2
QUEMAN, A-2
RESTOR, A-2
SPOOL, A-2
Operator Services Console
see OSC
Operator table
OPSER, A-8
OPSER
ABORT command, A-63
action requests, A-13
contents, A-14t
ANSWER command, A-IS

OPSER (Cont.)
cause INIT to start, A-I?
CH'ANGECONSOLE command, A-I?
changes OSC, A-18
checks for on line jobs, A-4,
A-8
checks operator table, A-8
commands
from PLEASE, A-60t
from SHUTUP, A-6l
START.COM, A-I?
communicates
three ways, A-5
with BATCH, A-55
communicates with SHUTUP, 4-3
controlled program, A-2
controlling RESTOR, A-?, A-63
DETACH command, A-I?
END command, A-62
immediate shutdown mode, 4-10
initial operating conditions
for, A-I?
interaction with action request,
A- 5
interaction with information
line, A-5
interaction with message, A-5
INTERRUPT command, A-IS, A-16,
A-23t, A-61
LIST command, A-16
LIST JOBS command, A-16, A-61
LIST OPERATORS command, A-16
LOGFILE command, A-I?
logical end mode, 4-10
message
contents, A-14t
formats, A-14
levels, A-IS
receiver identification, A-2
MESSAGE command, A-13, A-I?
online job list, A-16t
OPERATOR command, A-I?
operator commands, A-lOt
operator communicate with, A-59
operator table, A-8
overview, A-2
RESTOR commands, A-63t
restrictions of, A-2
RETYPE command, A-13
running with SHUTUP, 4-3
send command to QUEMAN, A-25
shutdown, A-?

Index-16

OPSER (Cont.)
shutdown in SHUTUP, 4-10
shutdown procedures, 4-10
start after system crash, A-IS
start-up procedure, A-17, A-IS
starting, A-S
table of online jobs, A-2
terminating with SHUTUP, A-7,
A-61
valid operators, A-l6, A-6l
ways terminated, A-IS
work file, A-S
OPSER package
BATCH, A-52
OPSER Package Library
QUEMAN, A-l9
OPSER.LOG file
default log file, A-9
/OPTIMIZE qualifier
RESTORE command, 16-17
Options
INIT program, 2-7
OSC (Operator Services Console)
INTERRUPT responses, A-16
OPSER broadcasts messages to,
A- 3
OPSER changes, A-IS
output formats, A-14
send text to, A-5S
/OUT_LABEL qualifier
BACKUP command, 16-9
RESTORE command, 16-lS
lOUT_QUOTA qualifier
CREATE/ACCOUNT command, 7-11
OUT_QUOTA qualifier
SET ACCOUNT command, 7-lS
/OUTPUT qualifier
SHOW ACCOUNT command, 7-23
Overlay file
adding, 12-21
removing, 12-22
SHOW FILE/SYSTEM command, 12-21
/OVERLAY_FILE qualifier
SHOW FILE/SYSTEM command, 12-46
/OVERRIDE qualifier
LOGIN command, 13-17
OVR.SYS file
allocate and position, 12-lS

-P-

Pack identification
extracting with SAVE/RESTORE,
E-32t
/PAGE qualifier
START/QUEUE/MANAGER command,
9-50
/PAGE EJECT switch
SPOOL, A-35
/PAGE END qualifier
STOP/SERVER command, 9-54
/PAGE LENGTH qualifier
SET-PRINTER command, 11-25
/PAGE LIMIT qualifier
INITIALIZE/QUEUE command, 9-32
SET QUEUE command, 9-39
Paper tape punch test
PPEXER program, F-21
Paper tape reader test
PREXER program, F-22
/PARITY qualifier
SET TERMINAL command, S-15
/PASSWORD PROMPT qualifier
CREATE/ACCOUNT command, 7-11
SET ACCOUNT command, 7-1S
SET SYSTEM command, 14-33
Patch kits

see Update kits
Patches

see also Updates
PBS
batch servers, 9-3
default queues, 9-4
Forms Definition File (FDF),
9-lS
print servers, 9-3, 9-10
queue manager, 9-3
queue names, 9-4
queue priorities, 9-6
queue types, 9-4
treatment by SHUTUP, 4-S
user interface, 9-3
PBSCTL privilege
Print/Batch Services (PBS), 6-5
PDP-II word
decimal values, B-1
octal values, B-1
PEEK function test
CPEXER program, F-6
/PERMANENT qualifier
SET TERMINAL command, S-7, S-15

Index-17

/PERMANENT qualifier (Cont.)
SHOW TERMINAL command, 8-20
Physical device names, 12-11
PHYSICAL option
SPOOL, A-33
/PLACED qualifier
SET FILE command, 12-44
/PLACED_POSITION qualifier
RESTORE command, 16-18
.PLAS system directive
RDMEM privilege, 6-5
PLEASE
CCL command, A-61
commands through OPSER, A-60t
commands to OPSER, A-59
message broadcast, A-59
OPSER commands through, A-59
restrict use, A-58
run, A-58
talks to OPSER, A-3
terminate, A-58
/POSITION qualifier
CREATE/ACCOUNT command, 7-11
INSTALL/ERROR FILE command,
12-29
INSTALL/OVERLAY FILE command,
12-32
INSTALL/RUNTIME SYSTEM command,
12-34
INSTALL/SWAP FILE command,
12-37
Power fail
automatic restart after, 2-8
/POWERFAIL_DELAY qualifier
SET SYSTEM command, 14-33
PPEXER program
errors, explanation, F-21
example dialogue, F-21
paper tape punch test, F-21
/PREFIX qualifier
INSTALL/RUNTIME SYSTEM command,
12-34
PREXER program
error messages, F-22
example dialogue, F-22
paper tape reader test, F-22
Primary run-time system, 12-4
position, 12-7
system disk, 1-5
/PRINT qualifier
INITIALIZE/QUEUE command, 9-32
SET QUEUE command, 9-39

/PRINT qualifier (Cont.)
SET SERVER command, 9-42
SHOW SERVER command, 9-45
Print servers
Print/Batch Services (PBS), 9-3,
9-10
wildcard names, 9-10
print/Batch Service (PBS)
ASSIGN/QUEUE command, 9-25
INITIALIZE/QUEUE command, 9-30
print/Batch Services
see PBS

PBSCTL privilege, 6-5
print/Batch Services (PBS)
CLOSE/QUEUE command, 9-26
DEASSIGN/QUEUE command, 9-27
DELETE/QUEUE command, 9-28
DELETE/SERVER command, 9-29
INITIALIZE/SERVER command, 9-34
many-to-one configuration, 9-6
one-to-many configuration, 9-5
one-to-one configuration, 9-5f
OPEN/QUEUE command, 9-36
SET QUEUE command, 9-37
SET SERVER command, 9-41
START/QUEUE command, 9-46
START/QUEUE/MANAGER command,
9-47
START/SERVER command, 9-49
STOP QUEUE command, 9-51
STOP/QUEUE/MANAGER command,
9-52
print/Batch services (PBS)
STOP/SERVER command, 9-53
print/Batch Services Package
(PBS)
DCL commands, 9-lt
managing, 9-3 to 9-16
Printer servers
ownership, 9-10
/PRINTER PORT qualifier
SET TERMINAL command, 8-15
printing device
adjustable top of form, A-36
Priority
basis, 13-7
byte, 13-7
format, 13-7f
decrease for job, 13-8
description, 13-6
LOGIN, 13-8
processing entries, 9-8

Index-l8

Priority (Cont.)
raise for SPOOL, A-44
setting job, 13-6
/PRIORITY qualifier
INITIALIZE/QUEUE command, 9-33
INITIALIZE/SERVER command, 9-35
SET JOB command, 13-20
SET QUEUE command, 9-39
SET SERVER commarid, 9-42
START/QUEUE/MANAGER command,
9-48
/PRIORITY switch
QUEMAN, A-22t
Private disk, 1-5, 1-10
/PRIVATE qualifier
INITIALIZE command, 15-11
Privilege
controlled access, 1-11
system damage, 1-11
Privilege mask
authorized, 6-10
current, 6-10
saved, 6 -10
/PRIVILEGE qualifier
CREATE/ACCOUNT command, 7-11
SET ACCOUNT command, 7-19
SET JOB command, 13-20
Privileged job
programming error, 2-6
/PRIVILEGES qualifier
DEFINE/COMMAND/SYSTEM command,
12-26
INITIALIZE/QUEUE command, 9-33
SET QUEUE command, 9-40
Processing entries
AFTER state, 9-8
HOLD state, 9-8
priority, 9-8
READY state, 9-8
Program
system, 1- 3
Program development, 1-3
Programming errors
causing crash, 2-6
/PROMPT qualifier
BACKUP command, 16-9
RESTORE command, 16-19
/PROTECTION qualifier
INSTALL/LIBRARY command, 12-31
SET FILE command, 12-44
Pseudo keyboard
BATCH, A-52

Pseudo keyboard (Cont.)
use with BATCH, A-6
Pseudo keyboards
batch servers, 9-15
Public disk structure, 1-4
/PUBLIC qualifier
DISMOUNT command, 15-5
INITIALIZE command, 15-11
Public structure, 1-3
/PURGE qualifier
DELETE/ACCOUNT command, 7-14
-Q-

QUE, A-5
QUE command
SPOOL, A-48
QUEMAN
command received through OPSER,
A-25
commands
start-up, A-26
consistency checks, A-21, A-27
DETACH command, A-22
do not CTRL/C, A-23
entry in AFTER queue, A-28
error in NEXT command, A-26
initial conditions for spooling
queues, 1\.-21
INITIALIZE command, A-22
integrity checks, A-21
message receiver declaration,
A-20
modules, A-19
OPSER package Library, A-19
requirements for running, A-19
resets to initial states, A-27
running
after SHUTUP, A-27
after system crash, A-27
running detached, A-22, A-26
start, A-19
start-up
command file, A-26
commands, A-21t
switches, A-22t
STATUS command, A-25
status printout, A-25
table of online spooling
programs, A-5
/QUERY qualifier
BACKUP command, 16-10

Index-19

/QUERY qualifier (Cont.)
DELETE/ACCOUNT command, 7-14
INITIALIZE command, 15-12
RESTORE command, 16-19
Queue limits, 9-9
Queue management, A-19
Queue manager
print/Batch Services (PBS), 9-3
Queue names
print/Batch Services (PBS), 9-4
Queue priorities
Print/Batch Services (PBS), 9-6
Queue types
Print/Batch Services (PBS), 9-4
QUEUE.SYS file, A-5
clear all entries from, A-21
consistency checking on, A-27
corrupt, A-23
flag value, A-21
initial conditions, A-21
number of queue requests, A-27
Queues
starting, ·9-7
stopping, 9-7
Quota
message, 5-5
RIB (Receiver 10 Block), 5-5
Quotas
Disk, 5-1
Job, 5-1
send/receive, 5-1
-R-

Random data caching, 11-10, 11-11
RC25
stopping, 14-2
RDMEM privilege
memory mapping, 6-5
read memory, 6-5
RDNFS privilege
non-file-structured I/O, 6-5
RDS (RSTS/E Disk Structure)
levels, 1-5
.
SYSTAT, 1-6
Read access
GREAD privilege, 6-4
WREAD privilege, 6-9
/READ_ONLY qualifier
INSTALL/LIBRARY command, 12-31
INSTALL/RUNTIME_SYSTEM command,
12-34

READY state
. processing entries, 9-8
Rebuilding dirty disks with MOUNT,
15-19
Receiver identification, A-34
/REGIS qualifier
SET TERMINAL command, 8-15
/RELEASE qualifier
SET JOB command, 13-20
SET SYSTEM command, 14-33
Remote line, controlling, 13-9
Remote terminal test
KBEXER program, F-17
REMOVE/ERROR_FILE command, 12-22,
12-38
REMOVE/JOB command, 13-18
example, 13-5
REMOVE/LIBRARY command, 12-39
REMOVE/OVERLAY_FILE command,
12-22, 12-40
REMOVE/RUNTIME_SYSTEM command,
12-9, 12-41
REMOVE/SWAP_FILE command, 12-20,
12-42
Rename access
GWRITE privilege, 6-4
WWRITE privilege, 6-10
REORDR
account designators, 11-5
dialogue, 11-3
questions, 11-4t
directory restructuring
functions, 11-3
error messages, 11-6
example, 11-8
fatal errors, 11-7
messages, 11-7t
precautions on use, 11-6
processing messages, 11-6
restructure directories, 11-2
run, 11- 3
/REPLACE qualifier
ASSIGN/SYSTEM command, 12-24
RESTORE command, 16-19
REQUE command
SPOOL, A-48
/RESET qualifier
DELETE/ACCOUNT command, 7-14
SET TERMINAL command, 8-15
SHOW ACCOUNT command, 7-23
Resident libraries
DISPLY program status, 14-27

Index-20

Resident library, 12-10
memory location, 12-10
permanently resident, 12-11
remove, 12-11
removing
under SHUTUP, 4-12
RMS, 11-14
XBUF allocation, 11-14
RESTART command
SPOOL, A-48
/RESTART qualifier
START/QUEUE/MANAGER command,
9-50
RESTOR
attached to a terminal, A-63
commands through OPSER, A-63t
running detached, A-7, A-64
RESTORE, E-4t
aborting, E-38
bad blocks, E-20
dialogue questions, E-2lt
example, E-23 to E-26
output used for system disk,
E-23
relocation of blocks, E-21
restoring a RSTS/E disk, E-20
run statistics, E-40
SAVE Set format, E-2
RESTORE command, 16-12 to 16-21
quick reference table, 16-21t
restrictions, 16-21
/RESTRICT qualifier
SET DEVICE command, 11-22
SET TERMINAL command, 8-16
Restricted device
DEVICE privilege, 6-3
Restricted receiver
SEND privilege, 6-6
Restrictions
Backup sets, 16-10
RESTORE command, 16-21
/RESUME qualifier
SET TERMINAL command, 8-16
/RETAIN qualifier
INITIALIZE command, 15-13
Retrieval pointers
information for data blocks,
11-3
RETYPE command, OPSER, A-13
/REWIND qualifier
BACKUP command,16-10
RESTORE command, 16-20

RIB (Receiver ID Block), 6-5
quota, 5-5
/RIB QUOTA qualifier
CREATE/ACCOUNT command, 7-11
SET ACCOUNT command, 7-19
Ring characteristics, 8-2
RJ2780 program
communication paths, A-7
shutdown, A-7
RMS (Record Management System)
caching files, 11-14
indexed file bucket sizes,
11-14
resident library, 11-14
RSTS/E
bootstrapping after system halt,
2-3
bootstrapping procedures~ 2-2
disk structures, 1-4
file structure, 1-5
halting, 2-1
initialization code, 2-1
initialization options, 2-1
management, 1-3
monitor error detection, 10-1
run-time systems, 12-4
shutdown procedures, 4-2
starting up, 2-1
RSTS/E disk structure
see RDS
RSTS/E Error Package
use with DEVTST package, F-1
RSTS/E Privileges, 6-3t
RSX, keyboard monitor, 1-2
RT11, keyboard monitor, 1-2
Run burst
decrease, A-44
default value, 13-8
definition, 13-8
raise on SPOOL, A-44
set, 13-6
system operation, 13-8
RUN command
how system treats, 12-8
no file type specified, 12-8
Run-time system, 1-3
auxiliary, 12-4, 12-5
BASIC-PLUS, 12-4
change default file type, 12-8
control, 12-4, 12-5
DCL command, 12-6
definition, 12-4
Index-21

Run-time system (Cont.)
description block, 12-6
DISPLY report, 14-25
installing, 3-8
language interface, 12-4
loading a, 12-7
permanently resident, 12-8
placement of, 12-7
position of primary, 12-7
primary, 1-3, 12-4
removing
auxiliary, 12-6
from system, 12-9
under SHUTUP, 4-12
.RTS file type, 12-5
specifying load address, 12-6
storage of, 12-5
temporarily resident, 12-8
use, 12-4
/RUN_BURST qualifier
INITIALIZE/SERVER command, 9-35
SET JOB command, 13-20
SET SERVER command, 9-42
START/QUEUE/MANAGER command,
9-48
/RUNBURST switch
QUEMAN, A-22t
/RUNTIME SYSTEM qualifier
SET FILE command, 12-44
-S-

SATT.SYS file
SAVE/RESTORE tape, E-9
SAV/RES
full function command ~ine,
E-34
SAV/RES FUNCTION
prompt, E-2, E-4
SAVE
requirements of disk devices,
E-8
run statistics, E-40
Save Image Library
see SIL
SAVE Set, E-20
default name, E-2
dismount message, E-37
extract label information from,
E-32t
format, E-2, E-20
identify, E-2

SAVE Set (Cont.)
magnetic tape, E-36
magnetic tape density, E-37
processing multi-volume, E-36
recreate disk, E-20
requirements, E-8
volume, E-8
booting RSTS/E, E-35t
by-pass label checking, E-10
SAVE/RESTORE, E-2
SAVE/RESTORE
bad blocks, E-1
output device, E-41
processing, E-41
changes caused by bad blocks,
E-42
checking
input volume, E-10
output volume, E-12
comparison with BACKUP, E-1
c~eate bootable medium, E-1,
E-34
CTRL/C in dialogue, E-8, E-38
CTRL/Z in dialogue, E-8
definition of terms, E-2
device specification switches,
E-10t
dialogue, E-3
defaults, E-7
disks, like, E-2
dismount message, E-37
dismount~ng volumes, E-36
error messages, E-12
/ERROR switch, E-6, E~6t
errors, E-5
dialogue, E-41
handling, E-41
messages, E-42t
transfer phase, E-41
verification phase, E-41
exit, E-3
/EXPIRATION switch, E-6, E-6t
fatal transfer errors, E-49
full function command line, E-6
function response, E-4
functions, E-1, E-4t
IDENTIFY
dialogue, E-32t
example, E-33
IMAGE
dialogue, E-27t
example, E-29 to E-32

Index-22

SAVE/RESTORE
IMAGE (Cont.)
function, E-26
input volume errors, E-llt
long form dialogue, E-7
magnetic tape, E-9
message types, E-5
mounting volumes, E-36
/NOERROR switch, E-6t, E-42,
E-49
/NOEXPIRATION switch, E-6t
nonfatal transfer errors, E-49,
E-50t
nonselective backup, E-l
/NOSTATS switch, E-6t
/NOVERIFY switch, E-6, E-6t
operator intervention during
processing, E-36
output volume expiration date,
E-12
perform, on disk and tape, E-8
prompt, E-3
reaccessing devices, E-38
requirements of SAVE disk, E-8
RESTORE
dialogue questions, E-21
example, E-23 to E-26
output as system disk, E-23
processing, E-3
RESTORE function, E-20, E-21
run, E- 2
off line, E-2
on line, E-3
SAVE Set
name, E-2
volume, E-2
SAVE set, E-2
short form dialogue, E-7
/STATS, E-6t
/STATS switch, E-6
summary infor~ation, E-5
summary report, E-38
format, E-39f
totals, E-40t
switch types, E-5
transfer errors, E-49
use, E-l
/VERIFY switch, E-6, E-6t
volume label checking, E-34
/SCOPE qualifier
SET TERMINAL command, 8-16

/SCRATCH switch
SAVE/RESTORE, E-IO
/SEIZE qualifier
ALLOCATE command, 11-16
/SELECT qualifier
RESTORE command, 16-20
/SELECT_ERASE qualifier
SET TERMINAL command, 8-16
SEND privilege
BROADCAST command, 6-6
restricted receiver, 6-6
Send/receive quota, 5-5
message, 5-5
RIB (Receiver ID Block), 5-5
Send/Receive quotas, 5-1
Sequential data caching, 11-10,
11-11
example, 11-11
Servers
assigned to queues, 9-5
SET ACCOUNT command, 7-16
SET CACHE command
/ALL qualifier, 11-18
/BUFFERS qualifier, 11-19
/CLUSTERSIZE qualifier, 11-19
/DATA_MAXIMUM qualifier, 11-20
/DIRECTORY_MAXIMUM qualifier,
11-20
/DISABLE qualifier, 11-20
/FILE qualifier, 11-18
/KEEP qualifier, 11-20
/MAXIMUM qualifier, 11-20
/NOFILE qualifier, 11-18
qualifiers, 11-18
TUNE privilege, 11-18
SET DATE command, 14-3, 14-31
SET DEVICE command
/DISABLE qualifier, 11-2
/ENABLE qualifier, 11-2
/NORESTRICT qualifier, 11-2
/RESTRICT qualifier, 11-2
SET FILE command, 12-43
SET FILE/RUNTIME_SYSTEM=name
command, 12-9
SET JOB command, 13-19
SET JOB/HOLD command, 13-6
SET JOB/RELEASE, 13~6
SET JOB/PRIORITY command, 13-7
SET JOB/RUN BURST command, 13-8
SET JOB/SIZE command, 13-8
SET PASSWORD command, 7-20
SETPAS privilege, 6-6

Index-23

SET PRIVILEGE command, 6-1
SET QUEUE command, 9-37
SET SERVER command, 9-41
SET SYSTEM command, 13-21, 14-32
SET SYSTEM/HOLD command, 14-2
SET SYSTEM/LOGINS command, 12-20,
13-2, 13-3
SET SYSTEM/NOLOGINS command, 13-2
SET SYSTEM/RELEASE command, 14-2
SET TERMINAL command, ·8-9
/AUTOBAUD qualifier, 8-1
/BROADCAST qualifier, 8-8
dial-up lines, 8-2
HWCFG privilege, 8-4
/NOBROADCAST qualifier, 8-8
/PERMANENT qualifier, 8-7
START.COM, 8-1, 8-7
SET TIME command, 14-3, 14-35
SETPAS privilege
SET PASSWORD command, 6-6
Setting job priority, 13-7
Setting job size, 13-7
/SETUP qualifier
SET TERMINAL command, 8-16
/SHAREABLE qualifier
INITIALIZE/SERVER command, 9-35
INSTALL/LIBRARY command, 12-31
INSTALL/RUNTIME SYSTEM command,
12-35
SET SERVER command, 9-43
SHOW ACCOUNT command, 7-22
sample output, 7-24
SHOW BUFFERS command, buffer
status report, 12-20
SHOW BUSY
use for shutdown, 4-2
SHOW CACHE command, 11-26'
SHOW COMMAND/SYSTEM command,
12-16, 12-45
SHOW DEVICE command, 11-28
SHOW DISKS
use for shutdown, 4-2
SHOW DISKS command
free space, 14-8
SHOW FILE/SYSTEM command, 12-46
SHOW JOB/PRIVILEGE command, 13-22
SHOW JOBS
use for shutdown, 4-2
SHOW JOBS command
job status, 14-8
SHOW JOBS/DETACHED command, 14-8
SHOW LIBRARY command, 12-47
I

SHOW LOGICAL/SYSTEM command,
12-14, 12-49
SHOW LOGICALS 'command, 12-48
SHOW RUNTIME_SYSTEM command,
12-50
SHOW SERVER command, 9-44
SHOW SYSTEM command, 14-9, 14-36
SHOW TERMINAL command, 8-8, 8-20
sample output, 8-21
SHOW USER command
job control, 13-6
SHOW USERS command
job status, l4~8
Shutdown
disabling DECnet/E during, 4-5
ERRCPY, 4-11
EVTLOG program, 4-11
final, under SHUTUP, 4-13
formula for waiting period, 4-6
manual procedure, A-62
normal (example), 4-13
OPSER, 4-10, A-7
performing system, 4-2
RSTS/E system, 4-1
specify waiting period, 4-4
SHUTUP
attached jobs, 4-8
communicate with OPSER, 4-3
detached jobs, 4-8
disable DECnet/E, 4-5
disabling logins, 4-5
disk dismount phase, 4-12
EMT logging shutdown phase,
4-12
ERRCPY shutdown phase, 4-11
error message to ERRCPY, 10-4
example
DECnet/E shutdown, 4-16
final job killing phase, 4-12
final shutdown phase, 4-13
formula for waiting period, 4-6
initial job killing phase, 4-8
limit logins, 4-5
limit network activity, 4-5
operational phases, 4-3
OPSER shutdown phase, 4-10
perform shutdown with, 4-2
phases of, 4-2
removing swapping files, 12-20
resident library removal phase,
4-12
run from console termin~l, 4-3

Index-24

SHUTUP (Cont.)
run with OPSER, 4-3
run without OPSER, 4-3
run-time system removal phase,
4-12
running QUEMAN after, A-27
set up dialogue phase, 4-3
shutdown of DECnet/E, 4-5
specify shutdown wait period,
4-4
swap file removal phase, 4-12
terminating OPSER, A-7, A-61
treatment of PBS, 4-8
unexpected errors, 4-12
use from KBO:, 4-1
use of, 2-5
warning message, 4-6
SHUTUP example
large RSTS/E system, 4-13
small RSTS/E system, 4-15
SHUTUP privilege
system control, 6-6
SIL (Save Image Library)
format, 12-9
MAKSIL program, 12-9
Simulation of hardware errors
device testing package, F-1
/SIXEL qualifier
SET TERMINAL command, 8-17
/SIZE qualifier
CREATE/ACCOUNT command, 7-12
INSTALL/ERROR_FILE command,
12-29
INSTALL/OVERLAY_FILE command,
12-32
INSTALL/SWAP_FILE command,
12-37
SET JOB command, 13-20
Small buffers
DISPLY report, 14-24
FIP, not used for caching,
11-19
general (SYSTAT), 14-7
general, not used for caching,
11-19
SHOW BUFFERS command, 14-7
Small spooler

see SPL
Software errors
logging, 10-1
/SPECIAL_CHARACTER qualifier
SET PRINTER command, 11-25

/SPEED qualifier
SET TERMINAL command, 8-17
SPOOL,. A- 2
ABORT command, A-36, A-48
/ALIGN switch, A-51
ASSIGN option, A-33
changing NORMAL form, A-34
compiled version of, A-29
default form, A-34
default keyboard values, A-38
default line printer values,
A- 37
/DFLENGTH switch, A-35
error handling, A-47
error messages, A-49
error text in user output,
A-50t
file header, A-48
FORM command, A-51
FORM option, A-34"
forms control characters, A-35
interrupt commands, A-41, A-41t
job header, A-48
line printer errors, A-47
logical device name, A-30
modules, A-29
NAME option, A-34
NORMAL option, A-34
/PAGE EJECT switch, A-35
PHYSICA,L option, A- 33
QUE command, A-48
raise priority, A-44
raise run burst, A-44
REQUE command, A-48
RESTART command, A-48
restart queued request, A-48
run, A-29
start-up
error processing, A-39
examples, A-42
options, A-31t
syntax error messages, A-39,
A- 39t
terminate
queued request, A-48
without shutting down, A-61
Spooling
determining number of job~,
A-25
initial conditions for, queues,
A-19
keyboard, A-38

Index-25

Spooling (Cont.)
line printer, A-37
Spooling Package Library, A-29
Spooling programs
commands, A-16
controlling, A-17
line printer, A-29
messages, A-16
monitoring, A-17
SPOOL, A-29
SPOOL and BATCH, A-2
table of in QUEMAN, A-5
Start-up
BATCH options, A-54t
BATCH procedures, A-56
CCL command definitions, 3-9
controlling system, 3-1
SPOOL options, A-31t
terminal characteristics, 3-9
Start-up control file
order of operations, 3-2
START. COM
automatic restart, 2-5
memory image, 2-7
sample, 3-3
SET TERMINAL command, 8-1, 8-7
START.COM file
ANALYS, 10-30
commands auxiliary run-time
system, 12-5
contents, 3-2
logical names, 12-12
replace, 3-2
START/QUEUE command, 9-46
START/QUEUE/MANAGER command, 9-47
START/SERVER command, 9-49
Statistics
abbreviations in DISPLY report,
14-18
busy device, 14-20
job status, 14-18
SAVE/RESTORE run total, E-40t
STATUS command
QUEMAN, A-25
STOP/QUEUE command, 9-51
STOP/QUEUE/MANAGER command, 9-52
STOP/SERVER command, 9-53
Summary report
. ERRDIS, 10-8
run totals, E-40t
Swap file, 1-11
add, 12 -18

Swap file (Cont.)
affects logins, 12-20
online creation, 12-19
removing, 12-18, 12-20
under SHUTUP, 4-12, 12-20
SHOW FILE/SYSTEM command, 12-21
Swap space, 13-3
restricting logins, 12-20
SWAPO.SYS file
allocate and position, 12-18
SWAPl.SYS file
allocate and position, 12-18
SWAP3.SYS file
allocate and position, 12-18
/SWAP_FILE qualifier
SHOW FILE/SYSTEM command, 12-46
Swapping, 1-11
Swapping mode
TUNE privilege, 6-8
SWCFG privilege
system manager function, 6-6
SWCTL privilege
Logins, 6-7
Network management, 6-7
SWITCH program
change keyboard monitor, 1-2
SYO:
system disk, 1-3
SYS functions
programming, 2-7
SYSIO privilege
file access, 6-7
write access, 6-10
SYSMOD privilege
system modification, 6-7
SYSTAT
free disk space, 14-8
guidelines, 14-7
use, 14-7
System
automatic restart RSTS/E, 2-3
commands, 1-11
EMT logging to record
activities, 14-4
enable data caching, 11-18
enable directory caching, 11-18
halt, after bootstrapping
RSTS/E, 2-3
hal ting the RSTS/E, -2 - 5
initialization options, 1-4
initialized in restart mode,
2-7

Index-26

System (Cont.)
monitoring status, 14-8
operational concepts, 1-10
shutdown, 4-1
start-up, 3-1
suspending operations, 14-2
System clock
DATES privilege, 6-3
System commands
INSTAL privilege, 6-5
System control
HWCTL privilege, 6-5
JOBCTL privilege, 6-5
SHUTUPprivilege, 6-6
System crash, 2-3
ANALYS program, 3-10
causes, 2-6
handling, 2-7
randomly occurring, 2-6
System disk, 1-3
access, 1-4
contents, 1-5
System error log, F-1
System Error Package
programs, 10-1
System errors
compilation, 10-1
extraction, 10-1
formatting, 10-1
retention, 10-1
System Files
managing with DCL commands,
12-1t
System files
INSTAL privilege, 6-5
System logical. names
INSTAL privilege, 6-5
System manager function
HWCFG privilege, 6-4
SWCFG privilege, 6-6
System modification
SYSMOD privilege, ·6-7
System programs, 1-3
/SYSTEM qualifier
SET PASSWORD command, 7-21
System restart
START.COM, 2-7
System security
EMT logging, 14-7
System start-up
command file, 3-3
conditions at, 3-1

System start-up (Cont.)
controlling, 3-1
crash recovery, 3-10
-T-

/TAB qualifier
SET PRINTER command, 11-25
SET TERMINAL command, 8-17
Tape handling, DCL commands,
IS-It
TCll DEC tape operation test
DTEXER program, F-14
/TEMPLATE qualifier
CREATE/ACCOUNT command, 7-12
TERDFL.SYS
terminal characteristics, 8-6
TERMAC.SYS
terminal characteristics, 8-5
Terminal
at system command level, 1-11
/BROADCAST command qualifier,
8-7
CTRL/C typed at, 1-11
/DFLENGTH switch effect, A-36
distinction from line printer,
A- 37
FORCE command, 13-4
hardware top of form, A-39
line speed characteristics file,
8-2
/NOBROADCAST command qualifier,
8-7
OSC, A-18
running SHUTUP from console,
4-1
setting characteristics, 8-1
top of form capability, A-35
Terminal characteristics
HWCFG privilege, 8-4
Start-up, 3-9
TERDFL.SYS, 8-6
TERMAC.SYS, 8-5
Terminal device designator, 8-3
Terminal line
dial-up lines, 8-1
local, 8-1
TERSPD.SYS file
account location, 8-2
/AUTOBAUD qualifier, 8-3
why create, 8-2
Index-27

/TIME_FORMAT qualifier
SET SYSTEM command, 14-34
/TIME_LIMIT qualifier
INITIALIZE/QUEUE command, 9-33
SET QUEUE command, 9-40
Timesharing, start, 2-3
/TOP_OF_FILE qualifier
START/QUEUE/MANAGER command,
9-50
/TTSYNC qualifier
SET TERMINAL command, 8-17
TUNE privilege
alter base priority, 6-8
SET CACHE command, 11-18
swapping mode, 6-8
/TYPE qualifier
INSTALL/RUNTIME SYSTEM command,
12-35
SET TERMINAL command, 8-18
-U-

UFD (User File Directory)
and MFD in Level 0, 1-7f
mark file for caching, 11-11
reorder, 11-6
with MFD and GFDs in Levell,
1-8f
/UNLOAD qualifier
DISMOUNT command, 15-6
INSTALL/LIBRARY command, 12-31
INSTALL/RUNTIME SYSTEM command,
12-35
UNLOAD/LIBRARY command, 12-11,
12-51
UNLOAD/OVERLAY command, 14-37
UNLOAD/RUNTIME SYSTEM command,
12-8, 12-52
/UP_ARROW qualifier
SET TERMINAL command, 8-18
Updates
see also Patches
/UPPERCASE qualifier
SET PRINTER command, 11-25
SET TERMINAL command, 8-18
User account, 7-2
User File Directory
see UFD
User interface
Print/Batch Services (PBS), 9-3
User job
area, 1-11

/USER qualifier
CREATE/ACCOUNT command, 7-12
DELETE/ACCOUNT command, 7-15
SET ACCOUNT command, 7-19
SHOW ACCOUNT command, 7-23
User-defined privileges
USERl-8 privileges, 6-10
USERl-8 privileges
'User-defined privileges, 6-10
/USER DEFINED KEYS qualifier
SET-TERMINAL command, 8-18
UTILTY program
KILL, A-63

-v/VERIFY qualifier
BACKUP command, 16-10
RESTORE command, 16-20
Volumes
dismounting SAVE/RESTORE, E-36
mounting SAVE/RESTORE, E-36

-ti-

WACNT privilege
account management, 6-9
/WIDTH qualifier
SET PRINTER command, 11-25
SET TERMINAL command, 8-19
Window turning
reducing, 11-14
Work file
OPSER stores, A-3
WREAD privilege
execute access, 6-9
read access, 6-9
Write access
GWRITE privilege, 6-4
SYSIO privilege, 6-10
WWRITE privilege, 6-10
/WRITE qualifier
INITIALIZE command, 15-13
WRTNFS privilege
non-file-structured I/O, 6-9
WWRITE privilege
create access, 6-10
rename access, 6-10
write access, 6-10

Index-28

-x-

(Cont.)
resident library allocation,
11-14

XBUF

caching allocation, 11-9, 11-11,
11-13

Index-29

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT TELEPHONE ORDERS
In Continental USA
and Puerto Rico
call 800-258-1710

In Canada
call 800-267-6146

In New Hampshire,
Alaska or Hawaii
call 603-884-6660

DIRECT MAIL ORDERS (U.S. and Puerto Rico*)
DIGITAL EQUIPMENT CORPORATION
P.O. Box CS2008
Nashua, New Hampshire 03061

DIRECT MAIL ORDERS (Canada)
DIGITAL EQUIPMENT OF CANADA LTD.
940 Belfast Road
Ottawa, Ontario, Canada K1 G 4C2
Attn: A&SG Business Manager

INTERNATIONAL
DIGITAL EQUIPMENT CORPORATION
A&SG Business Manager
c/o Digital's local subsidiary
or approved distributor

Internal orders should be placed through the Software Distribution Center (SOC), Digital
Equipment Corporation, Northboro, Massachusetts 01532
* Any prepaid order from Puerto Rico must. be placed

with the Local Digital Subsidiary:

809-754-7575

RSTS/E
System Manager's Guide
AA-2 762 F-Te

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
D
D
D
D
D
Name

Assembly language programmer
Higher-level language programmer
Occasional programmer (experienced)
User with little programming experience
Student programmer
Other (please specify) _______________________________________________
Date ________________________________

Organization __________________________________________________________
Street ______________________________________________________________
Code
City _____________________ State ___________ Zip or
Country

I
I
I
I
I
I
I

,-------Do Not Tear - Fold Here and Tape - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1~

111111

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPL V MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

AnN: Office Systems Publications MK01-2/E02
RSTS/E Documentation
DIGITAL EQUIPMENT CORPORATION
CONTINENTAL BOULEVARD
MERRIMACK, N.H. 03054

·-------Do Not Tear - Fold Here and Tape ---------~---------------------------