Digital PDFs

AA-N435B-TK

January 1984

120 pages

Original

4.9MB

Document:	RTEM-11 Users Guide Version 2
Order Number:	AA-N435B-TK
Revision:	0
Pages:	120
Original Filename:	http://bitsavers.org/pdf/dec/pdp11/rsx11m_s/AA-N435C-TK_RTEM-11_Ver_2_Users_Guide_Jan84.pdf

OCR Text

RTEM-11 User's Guide
AA-N435C-TK

January 1984

This manual describes the use of RTEM-11 software, which emulates
the RT-11 program development system on RSX-11 and VAX/VMS
operating systems.
This manual supersedes the RTEM-11 User's Guide, AA-N435B-TK.

Operating Systems:

Software:

RSX-11 M Version 4
RSX-11 M-PLUS Version 2
VAX/VMS Version 3

RTEM-11 Version 2

To order additional documents from within DIGITAL, contact the Software Distribution
Center, Northboro, Massachusetts 01532.
To order additional documents from outside DIGITAL, refer to the instructions at the back
of this document.

digital equipment corporation · maynard, massachusetts

First Printing, August 1982
Revised, April 1983
Revised, January 1984

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 l;ithis 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.

All Rights Reserved.
Printed in U.S.A.
A postage-paid READER'S COMMENTS form is included on the last page of this
document. Your comments will assist us in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:

~D~DDmDTM
DEC
DECmate
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter
DIBOL

MASSBUS
PDP
P/OS
Professional
Rainbow
RSTS
RSX

M24300

UNIBUS
VAX
VMS
VT
Work Processor

CONTENTS

Page
PREFACE
CHAPTER

vii
1

INTRODUCTION TO RTEM-ll

1-1

1.1
1.2
1.2.1
1.2.2
1.2.3
1.2.4
1.2.5
1.3

RTEM-11 FEATURES
RSX-ll CONVENTIONS
Logging In
Logging Off
RSX-ll File Management
RSX-ll Device Usage
HELP Command
SPECIAL CONSIDERATIONS FOR RTEM-ll, RSX-ll
USERS
Task or Job?
Files-II or RT-11 Directory Structure?
Multiuser or Single User?
Device Driver or Handler?
Device or Volume?
CTRL/C or CTRL/Z?
RSX-ll DOCUMENTATION REFERENCES
VAX/VMS CONVENTIONS
Logging In
Logging Off
VAX/VMS File Management
VAX/VMS Device Usage
HELP Command
SPECIAL CONSIDERATIONS FOR RTEM-ll, VAX/VMS
USERS
Process or Job?
Files-II or RT-ll Directory Structure?
Multiuser or Single User?
Device Driver or Handler?
Device or Volume?
CTRL/C or CTRL/Y?
VAX/VMS DOCUMENTATION REFERENCES

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

1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.6
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.7
CHAPTER

2
2.1
2.2
2.2.1
2.2.2
2.3
2.3.1
2.3.2
2.4
2.4.1
2.4.2
2.4.3
2.5

1-5
1-6
1-6
1-6
1-6
1-7
1-7
1-7
1-8
1-8
1-8
1-8
1-10
1-11
1-11
1-11
1-11
1-12
1-12
1-12
1-12
1-13

RTEM-ll SYSTEM CONCEPTS AND OPERATING
PROCEDURES

2-1

RTEM-l1 MONITOR
RTEM-l1 SYSTEM DEVICE
Virtual System Device
Foreign Volume System Device
RTEM-ll TERMINAL COMMUNICATION CONVENTIONS
prompt Characters
Special Function Keys
START-UP PROCEDURE
Start-up from Virtual System Device
Start-up from Foreign Volume System Device
Exiting from RTEM-ll
RTEM-ll START-UP COMMAND OPTIONS

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

iii

2.5.1

2.7.5
2.7.5.1
2.7.5.2
2.7.5.3
2.7.5.4
2.7.5.5
2.8

Specifying an Abort Character Code
( / [ - ] AB [ : n 1 )
Extending the Private Area (/EX[:n])
Displaying HELP Text (/HE)
Displaying Version Identifier (/10)
Changing Line Printer Spool
Device (/LP)
Specifying Private Area of Virtual System
Device (/PR[:n[:m]])
Making System Device Read-Only (/RO)
Specifying a Foreign Volume System
Device (/RT)
Specifying the Shared Area (/SH)
Invoking RTEM-11 from Default Virtual
System Device (/VS)
PERIPHERAL DEVICE NAMES AND USAGE
Foreign Devices Supported by RTEM-ll
Differences in Device Naming Conventions
Line Printer Support
RP02/RP03 Device Support on RSX-l1
RESTRICTIONS ON USING RT-ll FEATURES
Using DATE and TIME Commands
Using COPY/BOOT Command
Using COPY/DEVICE Command
Debugging with Virtual Debugging
Technique (VDT)
Summary of Restrictions
Keyboard Monitor Commands
RT-ll Utility Programs
RT-ll Programmed Requests
Unsupported RT-ll Devices
Unsupported Control Characters
COMMAND-LINE ERROR MESSAGES

EXTENDED COMMAND STRING INTERPRETER (ECSI)

3-1

3.1
3.2
3.3

CALLING ECSI
ECSI SYNTAX
WILDCARD USAGE

3-1
3-1
3-3

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)

4-1

4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.2.6
4.2.7

CALLING AND TERMINATING JOAT
JOAT Command String
HELP Command
JOAT COMMAND OPTIONS
Attaching a Physical Device (/A)
Creating a Virtual Device (/C[:nl)
Detaching a Device (/D)
Exiting from RTEM-ll (/E[:n])
Listing RTEM-ll Device Usage (/L)
passing Commands to RSX-ll (/M)
Ordering Files on a Virtual System
Device (/o[:xxxl)
Creating a Shared Area (/S)
Extending a Virtual Device (/T:n)
Updating a Virtual Device (/U)
Attaching a Virtual Device (/V[:VSn])
Write-protecting a Volume (/W(:NO])
Suppressing Query Message (/Y)
Creating Temporary Virtual Device (/Z)
JOAT ERROR MESSAGES

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

2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.8
2.5.9
2.5.10
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.7
2.7.1
2.7.2
2.7.3
2.7.4

CHAPTER

4.2.8
4.2.9
4.2.10
4.2.11
4.2.12
4.2.13
4.2.14
4.3

2-9
2-9
2-10
2-10
2-10
2-10
2-12
2-13
2-15
2-15
2-16
2-16
2-23
2-23
2-24
2-25
2-25
2-25
2-26
2-26
2-26
2-27
2-28
2-29
2-30
2-30
2-31

4-9
4-11
4-11
4-12
4-12
4-13
4-13
4-13
4-14

CHAPTER

FILE INTERCHANGE PROGRAM (FIP)

5-1

5.1
5.1.1
5.1.2
5.2
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
5.2.7
5.2.8
5.2.9
5.2.10

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

5.2.11
5.2.12
5.2.13
5.3

CALLING AND TERMINATING FIP
HELP Command
FIP Command String
FIP COMMAND OPTIONS
Copying in ASCII Mode (/A[:n])
Copying in Binary Mode {/B[:n]}
Creating Contiguous Output Files {/C}
Specifying Files-II Transfers {IF}
Copying New Files (/G)
Copying in Image Mode (/I[:n])
Copying Without Replacing (IN)
Excluding Files {/p}
Copying with Ouery (/O)
Copying STREAM Files, Creating FORTRAN
IV Files (IT)
Logging While Copying (/W)
Copying System Files (/Y)
Default Values
FIP ERROR MESSAGES

MODIFYING THE VIRTUAL SYSTEM DEVICE

6-1

6.1
6.1.1

MODIFICATION PROCEDURE
Establish Shared Area as a Temporary
File
Update and Compress the Virtual Device
(JOAT IU)
Add, Delete, or Modify Files on the Virtual
Device
Create a New Shared Area (JOAT IS)
Establish the Order of Files in
Shared Area (JOAT IO[:XXX])
Maintain the Host System
SAMPLE MODIFICATION

6-1

6.1.2
6.1.3
6.1.4
6.1.5
6.1.6
6.2
GLOSSARY

5-6
5-6
5-7
5-7
5-7

6-1
6-2

6-2
6-2

6-3
6-4
6-4

Glossary-l

INDEX

Index-l

TABLES
TABLE

2-1
2-2

Foreign Devices Supported by RTEM-ll
SET Options for RTEM-ll Devices

2-17
2-18

PREFACE

This manual introduces you to RTEM-ll, the RT-ll emulator.
The main
purpose of RTEM-II
is to let you develop and debug RT-II programs,
using the facilities of a multiuser system such as RSX-II or VAX/VMS.
This manual gives you the information you need to do this.
DIGITAL recommends that you consult the RTEM-ll Release Notes that is
shipped as part of the RTEM-ll documentation set. The release notes
contain information on the latest features of RTEM-II.
Intended Audience
To use this manual you should have some experience using RT-II,
but
you don't need to know too much about the host system (RSX-II or
VAX/VMS). All you need to know is some host system commands such as
DIRECTORY, SHOW DEFAULTS, ALLOCATE, and MOUNT, and conventions for
interacting with your host system through the terminal.
These
subjects are summarized in Chapter 1.
Chapter Summary
Chapter 1 lists RTEM-II features and
concepts and conventions.
Chapter 2 tells you how to invoke
operating conditions.

describes
RTEM-Il

RSX-II

and

VAX/VMS

alter

the

default

and

Chapter 3 describes the extended command string interpreter (ECSI).
Chapter 4 describes the jack-of-all-trades (JOAT)
utility prog(am,
which performs many diverse operations specific to RTEM-II
such as securing additional devices, exiting
from RTEM-II,
and gaining the attention of RSX-il or VAX/VMS.
Chapter 5 describes the RTEM-II file interchange program (FIP), which
transfers files between RT-II volumes and RSX-II or VAX/VMS
volumes.
Chapter 6 describes RTEM-II maintenance procedures.
A glossary defines RTEM-Il terms and compares RT-II terms
of RSX-II and VAX/VMS.

with

those

install

Associated Documents
RTEM-II Installation Guide -- This document describes how
and update RTEM-II.

vii

RTEM-ll Release Notes -- This document summarizes the features that
differentiate
RTEM-ll VI.l from RTEM-ll V2.
It also includes
technical information regarding RTEM's RT-ll monitor configuration and
information on any known software problems.
Documentation Conventions
Certain typographical devices are used in the
different kinds of information:

manual

distinguish

RED PRINT

User input. Where necessary, user input is
distinguish it from computer output.

<RET>

indicates
A carriage return.
Unless
the
manual
otherwise,
terminate all commands with a carriage
return. The carriage return is not displayed on your
terminal.

CTRL/x

A control character. To produce certain characters, you
must type a combination of keys concurrently. For
example, to produce CTRL/C, press the CTRL key and type
C at the same time.

UPPERCASE

Required characters.
In examples of command
capital letters represent the command name.

lowercase

Variable characters.
In examples of command syntax,
lowercase letters represent a variable, for which you
must supply a value.

(]

Optional item. You may include or omit the item in
square brackets. However, the brackets are not part of
the command and should not be included in the command
line. The only exception to this rule is the syntax for
a directory specification, described next.

(directory]

A directory specification. The directory specification
is two numbers in the form [group,member] representing
an account. When you type a directory specification in
a command line, you must enclose it in brackets.

filespec

A file specification. The file specification includes a
device name, a directory specification, a file name, and
if applica~le, a version number.

red

syntax,

The vertical or horizontal ellipsis represents omission
of optional repetitive information. You can repeat the
item that precedes the ellipsis.
)

In a command line,
the right angle bracket prompt
indicates the line is valid only on an RSX-ll system.

In a command line, the dollar sign prompt indicates that
the line is valid on RSX-ll and VAX/VMS systems unless
otherwise noted.

Block numbers are in decimal notation.
The term RSX-ll indicates RSX-llM or RSX-llM-PLUS;
system indicates an RSX-il or VAX/VMS system.

viii

the

term

host

CHAPTER 1
INTRODUCTION TO RTEM-ll

RTEM-ll provides the RT-ll program development environment under the
RSX-IIM, RSX-IIM-PLUS, and VAX/VMS operating systems. Thus, RTEM-ll
allows many concurrent users to develop RT-ll applications on an
RSX-ll or VAX/VMS host system.
These application programs can be
created, edited, assembled, linked, and debugged under RTEM-ll and
then executed on RT-l1.
This chapter introduces RTEM-ll
(Section 1.1), the RSX-ll host
(Sections 1.2 through 1.4), and the VAX/VMS host (Sections 1.5 through
1 .7) •

1.1

RTEM-ll FEATURES
•

RT-ll keyboard monitor commands and indirect command files

•

Support for RT-ll programs:
BATCH

EDIT

MACRO

SLP

BINCOM

FILEX

PAT

SPLIT

BUP

HELP

PIP

SRCCOM

CREF

IND

QUEMAN

TECO

DATIME

KED/K 52

QUEUE

TERMID

DIR

LET

RESORC

TRANSF

DUMP

LIBR

SETUP

UCL

DUP

LINK

SIPP

VDT

The DUP and FILEX programs are supported with restrictions, as
described in Section 2.7.5.
•

Two RTEM-ll utilities:
File interchange program
(FIP), which
files between RT-ll and host system

enables

transfer

Jack-of-all-trades (JOAT) program, which performs a variety of
system and device operations useful for application program
development

1-1

INTRODUCTION TO RTEM-ll
•

1.2

Multiple terminal RT-ll foreground/background
support for console terminal only

monitor

with

RSX-ll CONVENTIONS

The main difference between RSX-ll and RT-ll is that RSX-ll is a
multiuser system, which means that two or more people can be using it
at the same time~
In multiuser systems, you need to protect your work
from the work of other users.
RSX-ll does this through system
protection facilities, such as logging in and out, and through file
protection features.

1.2.1

Logging In

If you are authorized to use RSX-ll, you have a name and password that
RSX-ll will recognize.
To gain access to the system, you log in by
typing your name and password at an RSX-ll terminal.
As you start, the terminal should be displaying a right-angle bracket
(»
at its left margin.
This prompt informs you that RSX-ll is ready
to accept input.
Press CTRL/C.

You should now see a three-letter prompt in the form:

MCR>
MCR stands for monitor console routine.

Respond by typing HELLO.

The system asks you to identify yourself.
were given by the system manager.

Type the account

name

you

The system asks for your password.
Type the password
account. The log-in dialog is similar to the following:

for

your

MCR>HELLO
ACCOUNT OR NAME: JONES
PASSWORD: (type password)
After you are logged in, set your terminal
language) by typing:

DCL

(DIGITAL

SET /DCL=TI:
The remainder of this manual uses DCL in examples.

1.2.2

Logging Off

When you are through using the system, log off by typing:
>LOGOUT
You'll get a response similar to the following:
HAVE A GOOD MORNING
2l-MAY-83 10:25 TT6:

LOGGED OFF

1-2

command

INTRODUCTION TO RTEM-ll
In addition to logging you off, LOGOUT terminates your active tasks
and returns allocated resources to the system. RSX-11M-PLUS systems
with resource accounting provide additional information about your use
of the system.

1.2.3

RSX-ll File Management

Every user on RSX-11 is assigned a directory for private file storage.
Your directory is stored with other user directories on a volume.
When you log in, you automatically have access to files stored in your
directory. You do not have to name the device and directory to access
a file. The file name alone is enough.
You can display your current default disk and directory by issuing the
SHOW DEFAULTS command after you log in. For example:
>SHOW DEFAULTS
DMl: [230, 72]
In this example, the default user storage volume on the RSX-ll host is
device DMI. The directory is [230,72].
The DIRECTORY command displays information about files listed in
directory.

y~ur

>DIRECTORY
The following example shows the output from a DIRECTORY command.
Bracketed numbers denote lines explained in the following text.
[1]

DIRECTORY DMl: [230,72]
l8-APR-82 10:33

[2]

SUM.BAS;4
DEMO.MAC;l
STARS.MAC;l
LOGIN.CMD;3

[3 ]

1.
4.
5.
2.

ll-FEB-83 12:10
06-APR-83 16:20
30-SEP-82 12:30
l8-AUG-82 10:20

TOTAL OF 12./50. BLOCKS IN 4. FILES

The DIRECTORY command produces a listing of all files stored on a
particular mass storage device under the default account.
.The
directory shown above is in the standard format and shows a directory
listing for the default account, identified by the SHOW DEFAULTS
command.
[1]

The directory heading identifies the name of the mass storage
device where files are held. In this example, the device is DMI.
The heading also identifies the directory in which files are
stored. In this example, the directory is [230,72].

[2]

Each file in the directory listing is identified by name, type,
and version number, and the date and time the file was placed in
the directory. The number between the file specification and the
date indicates how many blocks of disk space the file occupies.
File names can include numbers or letters, but not other
characters.
File names are from one to nine characters long.
The period (.) separates the file name from the file type.
File
types can be from zero to three numbers or letters. The
semicolon (i) separates the file type from the version number.

1-3

INTRODUCTION TO RTEM-ll
~SX-ll assigns version numbers to
all files created.
Version
numbers can be from one to five octal digits. The lowest version
number is 1 and the highest is 77777. When you create a file, it
is assigned version number 1. If you later create another file
with the same name, the new file is version 2. Version 1 of the
file remains on the mass storage volume. As new versions of the
file are created, their predecessors remain on the volume until
you delete them.

[3]

At the bott6m of the directory is a decimal count of all the
blocks used by files in the directory and of the number of files
in the directory. The block count is given as two numbers
separated by a slash (I) to indicate the number of blocks needed
for the files and the number of blocks allocated.

A full RSX-ll file specification consists of a device name, a
directory code, a file name, a file type, and a version number in the
following form:
dev:[directory] filename.typ;version
All punctuation marks (colon, square brackets, period, semicolon) are
required.
These marks separate the various components of the file
specification.
The five elements
of
the
file
specification
distinguish one file from all others on the system.
Various parts of the file specification, such as the device and
directory, are automatically included (defaulted) by the system if you
do not supply them. You listed ~hesedefaults earlier with the SHOW
DEFAULTS command.
If you want to specify a file that is not in your
default directory or on your default device, include the explicit
device name or directory in the file specification.
If you omit the version number, the system will read the highest
numbered version of the file. The system will also create a new file
by incrementing the highest existing version number by 1.

1.2.4

RSX-Il Device Usage

In addition to establishing private files, RSX-ll offers protections
to users of individual devices.
These protections include the
ALLOCATE command and the MOUNT command.
The ALLOCATE command establishes a device as your private device, and
prevents access to it by other users. Device allocation is optional
but recommended.
You can place a volume in the drive before or after issuing the
ALLOCATE command. The ALLOCATE command ensures that no other user can
gain access to the device, so common practice is to place the volume
in the drive after allocating it. The following example shows the
simplest form of the ALLOCATE command:
ALLOCATE ddnn:
For RSX-ll, the device specification (ddnn:) contains two fields. The
first field is the device code (dd). The device code describes the
type of device you are allocating; for example, DY identifies an RX02

1-4

INTRODUCTION TO RTEM-ll
diskette.
The second field is the unit number of the device to be
allocated (nn).
If you omit this number, the system defaults to unit
0. The following command allocates RK05 unit 2:
>ALLOCATE DK2:
After allocating the device and placing a volume in the drive, use the
MOUNT command to mount the volume. Mounting is the mechanism that
provides a link between a volume, a device, and your process or task.
On RSX-ll, you can access a volume that contains system programs and
user directories without mounting it yourself. However, if you want
exclusive use of a volume (for example, an RT-ll system volume)
you
must mount it.
RSX-llM-PLUS requires you to use the /FOREIGN option when you mount a
volume that does not use the standard RSX-llM-PLUS format.
The volume
is foreign, although it can be accessed through RTEM-ll.
RSX-llM will
ignore your use of the /FOREIGN option with MOUNT. Specify the volume
with the device code you used in the ALLOCATE command.
For example:
>MOUNT/FOREIGN DK2:
When you no longer need access to files on a device,
release the
volume with the DISMOUNT command.
Specify the device with the code
used in the MOUNT command.
For example:
>DISMOUNT DK2:
If you allocated the device before using it, deallocate it so other
users can obtain access to it. Specify the device with the code you
used in the ALLOCATE command.
Logging off the system automatically
cancels the effects of MOUNT and ALLOCATE commands issued from your
terminal. To promote the efficiency of the system,
however, you
should immediately deallocate any devices you no longer need.
>DEALLOCATE DK2:
For more information about allocating and mounting
Introduction to RSX-1IM/M-PLUS.

1.2.5

volumes,

see

the

how

HELP Command

The HELP command displays information on your terminal
use the system. Type the command:

about

>HELP
RSX-ll will display a list of commands, and information about how to
log in to the system and how to issue further commands. HELP is the
only command you can issue before logging in. You should issue the
command at least once to know the nature of the information it offers.
Section 2.5.3 describes how to display the RTEM-ll HELP text.

1.3

SPECIAL CONSIDERATIONS FOR RTEM-ll, RSX-ll USERS

You should be aware of the following differences
RTEM-ll.

1-5

between

RSX-ll

and

INTRODUCTION TO RTEM-ll'
1.3.1

Task or Job?

Everything that is done on or by an RSX-ll system is done by a task or
group of tasks. RTEM-ll is itself a task that executes on the RSX-ll
operating system. A task is the fundamental executable unit i~ RSX-ll
just as a job .is the fundamental executable unit in RT-ll. When this
document refers to a task, it is referring to the executable unit on
RSX-ll.
When it refers to a job, it is referring to the executable
unit controlled by the RTEM-ll monitor.

1.3.2

Files-II or RT-Il Directory Structure?

Files are organized in directories, and directories are
volumes using structures known to the operating system.

organized

RSX-ll uses the Files-II file structure and assumes that
all
file-structured volumes are organized identically. The INITIALIZE
command creates the Files-II structure on disk or tape.
RTEM-II uses the RT-Il directory structure to store files.
To enable
RTEM-ll users to transport files between operating systems, RTEM-ll
includes the file interchange program
(FIP).
With FIP,
you can
transfer files between RT-Il directory structured volumes and host
system volumes without exiting from RTEM-ll.

1.3.3

Multiuser or Single-User?

RSX-11 systems are available to many simultaneous users. RT-ll is a
single-user system, available to one user at a time.
Most of the time
you are using RSX-11, you will feel as though you are the ~nly user.
Since you are one of many active users, however, RSX-Il provides
protection facilities to prevent users from interfering with one
another.
One of the device protections is the ALLOCATE command,
already
discussed.
RTEM-11 lets you pass a command line, such as ALLOCATE
DXI:, to the RSX-1l command line interpreter. This lets you allocate
a device directly from RTEM-II.
You should always allocate a device
when using RTEM-11.

1.3.4

Device Driver or Handler?

RSX-11 includes device drivers for transmitting data between main
memory and peripheral devices (for example, disks and line printers) •
A device driver performs functions that
enable
physical
I/O
ope rat ion s •
RTEM-ll includes device handlers (also known as drivers). To perform
I/O under RTEM-ll', the RTEM-1l handlers issue RSX-11 directives that
cause RSX-l1 device drivers to perform physical I/O.

1-6

INTRODUCTION TO RTEM-ll
1.3.5

Device or Volume?

These terms are often used synonymously. This document identifies a
device as a hardware unit such as a line printer, disk drive, or
magtape drive.
Device codes identify each device unit on a system.
For example, the common device code for an RL02 disk in unit 1 is
DLl:. This document identifies a volume as a mass storage medium that
can be treated as host system or RTEM-ll file-structured data storage.
For example, a diskette with structured data on it is a volume.
RT-ll and RSX-ll use different device names for certain physical
devices.
Only one of these devices is supported under RSX-ll and
RTEM-ll -- the RK05 disk. Under RSX-ll the code for an RK05 is DK,
and under RT-ll the code for an RK05 is RK.
Further, the device code
DK under RT-ll denotes the default storage volume. This conflict is
discussed further in Section 2.6.

1.3.6

CTRL/C or CTRL/Z?

On RTEM-ll and RT-ll, CTRL/C terminates job execution or cancels a
command during processing. However, on RSX-ll, CTRL/Z performs these
functions;
CTRL/C has a different purpose on RSX-ll.
If you are running a task such as PIP, you can use CTRL/C to suspend
PIP and invoke the command line interpreter. Then you can type a
single command before control returns to PIP. You can also use CTRL/C
on RSX-II to invoke the command line interpreter when no other task is
running.

1.4

RSX-ll DOCUMENTATION REFERENCES

The RSX-II documentation set provides full explanations of all
procedures mentioned here. This chapter provides a quick way to start
using the host system. As you become comfortable using RSX-ll,
you
should expand your knowledge and experience with the system to make
full use of it.
Further reading will prove helpful.
The RSX-IIM/M-PLUS Documentation Directory describes each manual
included in the system documentation.
The system documentation
includes a master index.
The Introduction to RSX-llM/M-PLUS is designed for any new user of the
operating system.--This manual uses terminal sessions to introduce and
explain system conventions. RT-llusers who are new to RSX-llM are
encouraged to work through this manual.
Under its close supervision,
you can learn how to experiment safely with the system while being
taught fundamental concepts.
The RSX-IIM/M-PLUS Command Language Manual describes
command language (DCL) and illustrates how to use it.

the

DIGITAL

The RSX-IIM/M-PLUS MCR Operations Manual contains information on the
system from the operator's point of view. This manual describes the
monitor console routine (MCR) which is an alternative command line
interpreter to DCL.
The RSX-11 Utilities Manual describes each RSX-llM utility program
detail.

1-7

INTRODUCTION TO RTEM-ll
1.5

VAX/VMS CONVENTIONS

The main difference between VAX/VMS and RT-ll is that VAX!VMS is a
multiuser system, which means that two or more people can be using it
at the same time.
In multiuser systems, you need to protect your work
from the work pf other users.
VAX/VMS does this through system
protection facilities, such as logging in and out, and through file
protection features.

1.5.1

Logging In

Press the <RET) key or CTRL/Y keys to signal the system that you want
to log in. The system responds by prompting you for your user name.
Enter your user name followed by a carriage return. The system then
prompts you to enter your password.
After typing your password, press
the carriage return. This is an example of a log-in sequence:
Username:
SMITH
Password:
Welcome to VAX/VMS Version V3.n on Node EMANON
$

The dollar sign is a system prompting symbol;
when this character
appears on the far left of the terminal, it indicates that the log-in
was successful and you can begin entering commands to the system.
If
your log-in sequence is entered incorrectly, the system displays an
error message and you must repeat the log-in procedure.

1.5.2

Logging Off

When you are through using the system, log off by typing:

$ LOGOUT
You will get a response similar to the following:
SMITH logged out at ll-DEe-1983 12:43:10.38

1.5.3

VAX/VMS File Management

Every user on VAX/VMS is assigned a directory for private file
storage.
Your directory is stored with other user directories on a
volume. When you log in,
you automatically have access to files
stored in your directory.
You do not have to name the device and
directory to access a file.
The file name alone is enough.
You can display your current default device and directory
the SHOW DEFAULT command after you log in.
For example:

issuing

$ SHOW DEFAULT
ORAl: [SMITH]
The example shows the default user storage volume as device ORAl:.
The directory is named [SMITH]. The device mnemonic is discussed in
the next section.
If the device ORAl:
holds directories for most of
the users on the system, it may be assigned the logical name USER.
The SHOW DEFAULT command would then display the default device and
directory as USER: [SMITH] •
1-8

INTRODUCTION TO RTEM-ll
The following example shows the use of and output from the DIRECTORY
command. The DIRECTORY command produces a listing of all files stored
on a particular mass storage device under the default account.
The
example directory is in the standard format and shows a directory
listing for the default account, identified by the SHOW DEFAULT
command.
$ DIRECTORY
[I]

directory

$ RTEM DRBl: [WORRALL]/LP
$ RTEM DL1: [200,200]/LP

A spooled device (affects only the RTEM-II LP handler):
Example:
Note:

optional

$ RTEM LP4:/LP

Spooled devices do not exist under RSX-lIM.

Any record device (affects only the RTEM-Il LS handler):
Examples

$ RTEM TT4:/LP
$ RTEM TTB3:/LP
$ RTEM LP4:/LP

(Non-spooled line printer)

See Section 2.6.3 for a description of the RTEM-li LP handler
and the RTEM-II LS handler.

2.5.6

Specifying Private Area of Virtual System Device (/PR[:n[:m]])

The /PR option invokes RTEM-Il from the virtual system device using
the specified file as the private area. Specify the file with a host
system file specification.
If the file does not exist,
it will be
created.
The default private area is the file RTIIPR.DSK in your
default directory.

2-10

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
The /PR[:n] option is used with a host system file specification.
The
first optional value
(n)
indicates the size of the file in blocks.
Use this value when you want to create a private area with a size
other than the default set by your system manager. The value for n
must be at least eight blocks, which the initial part of the directory
needs for
itself.
This value cannot exceed the maximum number of
available blocks, which can be calculated in three steps:
1.

Get into RTEM-ll

Attach the shared virtual system file with JOAT.

Use the RT-ll DIRECTORY/SUMMARY command.

The following example illustrates this procedure:
$ RTEM/VS
?RTEM-I-File not found; creating new private file
RTEM-ll (Host type)

DB~:[5,5]RTllPR.DSK;~

V~2.xx

RT-1IFB V~5.xx
?KMON-F-File not found DK:STARTM.COM
.RUN SY:JOAT LB:[l,l]RTllSH/V/W
.RUN SY:JOAT SYS$LIBRARY:RTllSH/V/W
?JOAT-I-Attached to VS1:
• DIR/SUM VS 1:
l4-Jun-82

;Under RSX-ll
;Under VAX/VMS

72 Files in segment 1
72 Files in segment 2
~

Files in segment 3

3 Available segments,

3 in use

71 Files, 1744 blocks
~ Free blocks
.RUN SY:JOAT /E/Y
$

In the above example, 1744 blocks are already in use by the shared
area of the virtual system device. To find the maximum number of
blocks that are still usable for your private file, you subtract 1744
(blocks used)
from 65535 (total blocks usable) and get 63791 (blocks
I eft to use).
If you use the maximum number of blocks available for your private
area
of
the
virtual system device,
and your system manager
subsequently rebuilds and increases the size of the shared area,
then
you will no longer be able to use your private area.
In other words,
if the combined total number of blocks in use for the shared and the
private areas of the virtual system device exceeds 65535, RTEM-ll will
give the following error message when you try to call your private
file:
?RTEM-F-Virtual system device too large filespec

2-11

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
To use your private area of the virtual system device, you will have
to reenter RTEM-ll by specifying another private area of the virtual
system device or by creating one. To do this, you must use the RTEM
command line and a different file name from the one you have been
using.
For example:

$ RTEM filespec/PR
Then you attach the old file by using
described in Section 4.2.11.

the

JOAT

utility

command

If the file specified with the IpR option is not found,
RTEM-ll
assumes you want to create a new private area. To create the private
area, respond Y to the query:
?RTEM-I-File not found; creating new private file
dev:[directory]RTllPR.DSK;0 Are you sure?
You might choose to use the IPR option when you want a separate area
for the development of BASIC-ll/RT-ll or FORTRAN IV/RT-ll programs.
For example, the shared area of your virtual system device might
contain the FORTRAN IV compiler, object time system, and other system
files essential to FORTRAN IV program development, and the private
area might contain only FORTRAN IV user programs. The following
command line invokes RTEM-ll using such a private area
(the file
RTIIF4.DSK).
The file resides in the current default directory.

$ RTEM RTIIF4/PR
The IPR option can be combined with the IRO or lEX option.
The second value (m) is an optional number of directory segments.
Use
this when you require a value different from the default. The default
number of directory segments is based on the creation size of the file
as follows:
File Size
In Blocks
Up to 512
513 to 2048
2049 to 12288
12289 or more

2.5.7

Default Number Of
Directory Segments
1
4

16
31

Making System Device Read-Only (/RO)

To make the system device read-only,
invoke RTEM-ll with the IRO
option.
If the system device is a foreign volume, the entire system
device is write-protected.
You cannot write to it after using IRO.
If
it is a virtual system device, the mark zone is not affected, but
the shared and private areas are write-protected.
The IRO option can
be combined wi th the IpR, ISH, Ivs, or IRT opt ions.
Do not combine
IRO with the lEX option.

2-12

R~EM-ll

SYSTEM CONCEPTS AND OPERATING PROCEDURES

You can invoke RTEM-II with the /RO option
command:

typing

the

following

$ RTEM /RO

A list of current device usage (displayed with the JOAT /L option)
will show that the entire virtual system device is read-only. See
Section 4.2.5 for a description of the JOAT /L option.

2.5.8

Specifying a Foreign Volume System Device (/RT)

The /RT option specifies an RT-II directory-structured volume as the
foreign volume system device.
Table 2-1 indicates which RTEM-li
supported devices can serve as foreign volume system devices. Specify
the device with the host system device name (for example, DKnn:
for
an RK05) as shown in Table 2-1.
To serve as an RTEM-llsystem device, the RT-Il volume you specify
must contain the RTEM-ll monitor file (RTEMFB.SYS), the swap file
(SWAP.SYS), the RTEM-II jack-of-all-trades utility (JOAT.SAV), and the
device handler (XXM.SYS, where xx identifies the device).
If you need
to manipulate host system files while running RTEM-li from the foreign
device, the RT-II volume must also contain the FIP.SAV program.
If
your RT-il volume does not contain these files:
1.

Allocate it using the host system ALLOCATE command.

Mount it using the host system MOUNT/FOREIGN command.

Invoke RTEM-ll from the virtual system device.

Attach your RT-il volume using the JOAT utility /A command.

Copy the required files to the volume.

Thereafter, you can use the
RTEM-II.

RT-Il

volume

system

device

for

The /RT option can be combined with the /RO option.
The following example shows how the RTEM-ll files are added to a
bootable RT-ll binary distribution volume residing in RL02 unit 1 on
the host system:
Procedure
[1]

$ MOUNT/NOSHARE/FOREIGN DLI:

[2J

$ RTEM DLl:/RT

?RTEM-F-File not found DLI:RTEMFB.SYS
(3]

$ RTEM/VS
RTEM-ll (RSX-llM/+) V02.xx
RT-llFB V05.xx

[4J

.RUN SY:JOAT DLI:/A

2-13

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
[5]

.COPY SY:RTEMFB.SYS,SY:SWAP.SYS,SY:RKM.SYS,SY:JOAT.SAV OLl:*.*
Files copied:
SY:RTEMFB.SYS to OL1:RTEMFB.SYS
?PIP-E-Protected file already exists OLl:SWAP.SYS
SY:RKM.SYS
to OL1:RKM.SYS
to DL1:JOAT.SAV
SY:JOAT.SAV

[6]

.COPY SY:FIP.SAV OL1:*.*
Files copied:
SY:FIP.SAV
to DLl:FIP.SAV

[7]

.RUN SY:JOAT IE/Y

[8]

$ RTEM OL1:/RT
RTEM-ll (RSX-IIM/+) V02.xx
RT-llFB V05.xx

[9 ]

[10]

• 0 I R *. S YS
15-Ma r-8 3
TT
.SYS
2P l2-Mar-83
DX
.SYS
3P 12-Mar-83
DD
.SYS
5P 12-Mar-83
VM
.SYS
3P 12-Mar-83
RF
.SYS
3P 12-Mar-83
RK
.SYS
3P 12-Mar-83
RTllSJ.SYS
73P 12-Mar-83
DU
.SYS
4P l2-Mar-83
DM
.SYS
5P 12-Mar-83
MM
.SYS
9P 12-Mar-83
CT
.SYS
6P 12-Mar-83
LS
.SYS
2P 12-Mar-83
CR
• SYS
3P 12-Ma r-8 3
RTllAI.SYS
73P 12-Mar-83
LDX
.SYS
8P 12-Mar-83
DYX
.SYS
4P 12-Mar-83
VMX
.SYS
2P 12-Mar-83
DLX
.SYS
5P l2-Mar-83
DMX
.SYS
5P 12-Mar-83
MMX
.SYS
10P 12-Mar-83
LPX
.SYS
2P 12-Mar-83
NLX
.SYS
2P 12-Mar-83
MMHD .SYS
4P 12-Mar-83
RTIIBL.SYS
71P 12-Mar-83
SLX
.SYS
l6P 12-Mar-83
SWAP .SYS
26P 12-Mar-83
52 Files, 737 Blocks
532 Free blocks

LO
.SYS
DY
• SYS
PO
.SYS
DT
.SYS
DS
.SYS
DL
.SYS
RTIIFB.SYS
DP
.SYS
MT
.SYS
MS
.SYS
LP
• SYS
PC
• SYS
NL
• SYS
RT1IXM.SYS
DXX
.SYS
DDX
• SYS
RKX
.SYS
DUX
.SYS
MTX
.SYS
MSX
.SYS
LSX
.SYS
MTHD • SYS
MSHD .SYS
SL
• SYS
RKM
• SYS
RTEMFB.SYS

12-Mar-83
12-Mar-83
12-Mar-83
12-Mar-83
12-Mar-83
12-Mar-83
l2-Mar-83
12-Mar-83
12-Mar-83
12-Mar-83
12-Mar-83
l2-Mar-83
12-Mar-83
l2-Mar-83
4 P 12 -M a r - 8 3
5P 12-Mar-83
3P 12-Ma r-8 3
4P 12-Mar-83
9P 12-Mar-83
lIP 12-Mar-83
3 P 12 -M a r - 8 3
4P 12-Mar-83
5P l2-Mar-83
13P l2-Mar-83
3P 14-Mar-83
88P l4-Mar-83

8P
4P
3P
3P
3P
4P
86P
3P
9P
10P
2P
2P
2P
97P

.RUN SY:JOAT IE/Y
$

Explanation
[1]

The user mounts the RT-ll volume
command.

[2]

The user attempts to use the RT-ll volume as an RTEM-ll system
device, without first copying the required files to the volume.
An error message results.

2-14

using

the

host

system

mount

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
[3]

The user enters RTEM-ll using the virtual system device
mode.

[4]

The user attaches the RT-ll volume using the
command.

[5]

The user copies the required RTEM-ll system files to the RT-ll
volume. The error copying SWAP.SYS occurs because it was already
pres.ent on the user's RT-ll volume.

[6]

The user also copies the RTEM-ll utility
volume.

[7]

The user exits RTEM-ll using the JOAT utilities /E command.

[8 ]

The user enters RTEM-ll using the RT-ll format volume in DLl:
the system device.

[9]

The user takes a directory of all the system files.

JOAT

FIP.SAV

start-up

utilities

the

RT-ll

[ 10] The user exits RTEM-ll using the JOAT utilities /E command.

2.5.9

Specifying the Shared Area (/SH)

The ISH option specifies a Files-II file to be used as the shared area
of the virtual system device. The default shared area is the file
LB:[l,l]RTllSH.DSK on RSX-ll systems and SYS$LIBRARY:RTllSH.DSK on
VAX/VMS systems.
If you do not specify a file type, the default type
is SYS.
RTEM-ll lets you create virtual system devices for specific purposes,
such as FORTRAN IV development.
For example, you can create a private
area that contains all your FORTRAN IV user programs and a shared area
that contains the RTEM-ll monitor and handlers, necessary utilities,
FORTRAN IV compiler and object time system, and assorted libraries.
The following command invokes RTEM-ll specifying a FORTRAN IV-specific
virtual system device:
$ RTEM RTSHF4/SH,RTPRF4/PR
The first file
is RTSHF4.DSK in your default directory.
It is
specified as the shared area of the virtual system device with the ISH
option. The second file is RTPRF4.DSK in the same directory.
It is
specified as the private area of the virtual system device with the
/PR option.

2.5.10

Invoking RTEM-ll from Default Virtual System Device (/VS)

The RTEM-ll monitor file and system device handler must reside on
virtual system device before you invoke the program.

the

When you invoke RTEM-ll from a virtual system device, RTEM-ll opens
the shared and private areas and copies the mark zone to a temporary
file in your directory.

2-15

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
The first time you invoke RTEM-ll from the default virtual system
device, RTEM-ll creates a private file storage area for you. RTEM-ll
file
displays
the
message
?RTEM-I-Creating
default
private
dev:[directory]RTllPR.DSK;~ to inform you of this.
The virtual system device is unit

of the virtual device set

(VS~:).

To invoke RTEM-ll from the default virtual system device, type:

$ RTEM /VS
The /VS option cannot be combined with the /RT option. The /VS option
is ignored if it is combined with the /PR or the ISH option.

2.6

PERIPHERAL DEVICE NAMES AND USAGE

The following sections describe host system devices that are supported
by RTEM-ll as foreign devices. Some devices supported by RT-1l are
not supported by RTEM-ll. Section 2.6.1 summarizes RTEM-11 device
support.

2.6.1

Foreign Devices Supported by RTEM-ll

Table 2-1 lists the physical names of
RTEM-ll running under RSX-ll or VAX/VMS.
supplied:

host devices supported by
The following information is

Device Name
This is the host system's name for the foreign device. This name is
used initially by an RTEM-ll user to attach or boot the foreign
device. The variable nn indicates one of the unit numbers ~ though 77
on an RSX-11 host or A~ through F7 on a VAX/VMS host.
RT-II Name
This is the RT-11 device name for the foreign device. RT-11 programs
use this name to refer to the host physical device. The variable n
may be one of the unit numbers ~ though 7.
In some cases, the host
device name is not the same as the RT-Il device name. These
differences are discussed in Section 2.6.2.
Host
Not all devices are supported by all RTEM-11 host systems.
This
column shows which host system supports each device. An ent~y of All
indicates that RSX-ll and VAX/VMS support that device.
System Device
This indicates whether or not you can use the host device as an
RTEM-1l foreign system device.
If Yes, you can boot the device as
your system volume using the RTEM-ll command line option /RT
(see
Section 2.5.8).
If No, you can use the device only as a data device,
by attaching it using the host device name with the JOAT /A command
described in Chapter 4.

2-16

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
Device Type
This column shows the hardware name of the device.
Devices DU, MF, MM and MT include RT-ll SET options.
and their default values are listed in Table 2-2.

These

options

When building a shared virtual system device file, JOAT copies all
RTEM-ll handlers with SET options into the read/write mark zone. The
SET option defaults in effect at that time will be in effect each time
a user starts RTEM-ll using that shared virtual system device file.
Table 2-1
Foreign Devices Supported by RTEM-ll
Device
Name

RT-ll
Name

Host

System
Device

BA:

All

RT-Il batch handler

CSnn:

DDn:
DXn:

VAX/VMS

No
Yes

TU58 DECtape I I
RX0l disk

DDnn:

DDn:

All

TU58 DECtape I I

DKnn:

RKn:

RSX-II

Yes

RK05 disk

DLnn:

DLn:

All

Yes

RL01, RL02 disk

DMnn:

DMn:

All

Yes

RK06, RK07 disk

DPnn:

DPn:
DQn:

RSX-II

Yes
Yes

RP02, RP03 disk

DQnn:

DLn:

VAX/VMS

Yes

RL02 disk

DSnn:

DSn:

RSX-II

Yes

RS03, RS04 disk

DTnn:

DTn:

RSX-II

Yes

DECtape

DUnn:

DUn:

All

Yes

MSCP class disks RA80,
RA81,

DXnn:

DXn:

RSX-Il

Yes

RX0l diskette

DYnn:

DYn:

RSX-II

Yes

RX02 diskette

LDn:

All

RT-II logical disk handler

LP0:

LP:

All

Line printer

LP0:

LS:

All

Line printer

MFnn:

MFn:

All

TU78 magtape

MMnn:

MMn:

RSX-Il

TEI6/TU16/45/77/79
magtape

Device
Type

...

(Continued on next page)

2-17

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
Table 2-1 (Cont.)
Foreign Devices Supported by RTEM-ll
Device
Name

RT-ll
Name

Host

System
Device

MSnn:

MSn:

All

TSll or TSV~5 magtape
drive

MTnn:

MTn:

All

TU/TEl~ tape drive under
RSX-ll or
TE16/TU16/45/77/78
magtape drive under VAX!VMS

NL~:

NL:

All

Null device

SL:

All

RT-ll single-line editor

Device
Type

* The handler does not access host system devices and therefore has no
equivalent host system device name.

Table 2-2
SET Options for RTEM-ll Devices
Permanent
Name of
Device

Set
Option

DUn:

PART=x

Defines partition of a disk on which
device unit n resides. Variable x is an
integer in the range 0-266, depending on
size of disk device (each partition is 64K
blocks). Default for x is~.
See the
RT-ll Software suPaort Manual for more
information on MSCP1Sk partitioning.

LD:

CLEAN

Verifies and corrects, if necessary, all
current
logical
disk
assignments by
checking them against the files on volumes
that are mounted. This option is useful
if you have moved or removed files on a
volume, or have removed a volume from a
device. If a logical disk file has been
moved, the new location is noted so you
can continue to use that logical disk. If
you have deleted a logical disk or the
volume containing a logical disk file is
n~
longer
mounted, the logical disk
assignment is disconnected. For a volume
you have removed, the disconnect is only
temporary.
You
can
reestablish
the
assignment when you remount the volume by
using the SET LD CLEAN command again. The
keyboard
commands
SQUEEZE
and
BOOT
automatically perform the SET LD CLEAN
operation.

Description

(Continued on next page)
2-18

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
Table 2-2 (Cont.)
SET Options for RTEM-II Devices
Permanent
Name of
Device

Set
Option

LOn:

WRITE

Used during disk subsetting;
defines
logical disk unit n as being write-enabled
(read/write allowed). The value n must be
an integer in the range 0 through 7.

LOn:

NOWRITE

Used during disk subsetting;
defines
logical disk unit n as being write-locked
(read-only access allowed). The value n
must be an integer in the range 0 through

Description

7.
LS:

Sends carriage returns to printer.
To
allow overstriking on the printer, use CR
(the default) for any FORTRAN program that
uses formatted input and output. Also use
CR for any LSII or LP05 line printer to
prevent loss of the last line in the
buffer.

LS:

NOCR

Prevents handler from sending carriage
returns to the printer. This setting can
produce significant increases in printing
speed on some line printers, where the
printer controller causes a line feed to
perform
the
functions of a carriage
return.
Default is CR.

LS:

CTRL

Passes
all
characters
including
nonprinting
control characters to the
printer.
Use CTRL to pass the
bell
character to the LA180 printing terminal.
Default is NOCTRL.

LS:

NOCTRL

Ignores nonprinting
This is the default.

LS:

FORM

Declares that line printer has hardware
form feeds,
causing line printer handler
to send form feeds to the controller.
Line printer handler sends the form feed
character to printer each time handler
encounters a
form feed.
This is the
default.

control

characters.

(Continued on next page)

2-19

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
Table 2-2 (Cont.)
SET Options for RTEM~ll Devices
Permanent
Name of
Device

Set
Option

LS:

NOFORM

Causes line printer handler to simulate
hardware form feeds by sending one or more
line feeds to printer. Use the LENGTH=x
setting and position paper at top of form
(that is, at page perforation) before you
start to use the printer.
NOFORM is
useful for preprinted forms that have
nonstandard lengths.
You must use this
setting
if
your
printer
does
not
accommodate form feeds.
FORM is default
setting.

LS:

FORM0

Issues form feed before request
block 0. This is the default.

LS:

NOFORM0

Turns off FORM0 (the default) •

LS:

Lets line printer handler send lowercase
characters to printer. Use this condition
if printer has lowercase character set.
This is the default.

LS:

NOLC

Translates
lowercase
characters
to
uppercase before printing. The default is
LC.

LS:

LENGTH=x

Causes the printer to use x as number of
lines per page. The default is 66. Use
this option with
NOFORM
and
SKIP=x
settings.

LS:

SKIP=x

Causes line printer handler to send a form
feed to printer when it comes within x
lines of the bottom of the page. Use this
setting
to
prevent the printer from
printing over page perforations.
The
value for x should be an integer from 0 to
maximum number of lines on the paper.
If
you set SKIP=0, the handler sends lines to
the printer regardless of the position of
paper.
When you use this setting, you
must also use LENGTH=x setting.
Default
is SKIP=0.

LS:

TAB

Lets line printer
handler
send
tab
characters to printer. Default is NOTAB.

LS:

NOTAB

Expands tabs by sending multiple spaces to
printer. This is the default.

Description

(Continued on next page)

2-20

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
Table 2-2 (Cont.)
SET Options for RTEM-II Devices
Permanent
Name of
Device

Set
Option

MFn:/MMn:/MTn:

DENSE=x

Description
Sets density for 9-track tape handler. Do
not alter the density setting within a
volume.
Valid
density
settings
for
9-track tape are:
Sets 800 bits/in. Default for
MT and MM handlers.
Sets 1600 bits/in, parity odd.
Default for MF handler.
Sets 6250 bits/in, parity odd.
Valid for MF handler only.

800
1600
6250

for 9-track tape.
this setting
{the

MFn:/MMn:/MTn:

ODDPAR

Sets parity to odd
DIGITAL
recommends
defaul t) •

MFn:/MMn:/MTn:

NOODDPAR

Sets parity to even for 9-track tape.
DIGITAL does not recommend this setting
for normal operation, and provides it only
for compatibility with other systems.

SL:

ASK

Lets single-line editor determine type of
terminal you are using,
so SL can use
proper escape sequences.
SL prints on
console the type of terminal you are using
and the type of support SL will provide.
If SL does not support the terminal, SL
prints an error message.

SL:

LEARN

Helps you learn to use the single-line
editor
by letting you lock the help
display on the top half of screen.
You
can use the bottom of screen to type
command lines and display console output.
After you issue the commands SET SL ON and
SET SL LEARN, type the PF2 key to display
the help frame and lock it on the screen.
This option is valid for VT100-compatible
terminals only.

SL:

NOLEARN

Unlocks help display and lets it scroll
off the screen so you can use the entire
input
and
screen to display console
This is the default. SET SL OFF
output.
performs an automatic SET SL NOLEARN.

SL:

Loads and enables the single-line editor.

SL:

OFF

Unloads
editor.

and

disables

the

sing 1 e-l i ne

(Continued on next page)

2-21

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
Table 2-2 (Cont.)
SET Options for RTEM-ll Devices
Permanent
Name of
Device

Set
Option

SL:

TTYIN

Lets you edit responses to prompts printed
by system utilities. When SET SL TTYIN is
enabled, the prompt prints on one line and
your response appears on the following
line.
(This option allows SL to intercept
and edit input requests from .TTYIN. SL
always intercepts and edits input requests
from .CSIGEN, .CSISPC and .GTLIN).

SL:

NOTTYIN

Disables your ability to edit responses to
prompts printed by system utilities. When
SET SL NOTTYIN is enabled, the prompt and
your response appear on the same line.
{This option prevents SL from intercepting
and editing input requests from .TTYIN.
SL still intercepts and
edits
input
requests
from
.CSIGEN,
.CSISPC
and
.GTLIN}. This is the default.

SL:

VTxxx

Tells the single-line editor which type of
terminal you are using, so SL can send the
proper
escape
sequences.
DIGITAL
recommends that you use SET SL ASK instead
of this option.

Description

This
option
terminals:
VT52
VT62
VT100
VTl01
VTl02

supports

the

fo llowi ng

(SET SL VT52)
(SET SL VT62)
(SET SL VT100)
(SET SL VT101)
(SET SL VT102)

The default setting is SET SL VT100.
SL:

WIDTH=x

Allows you to set the width of
the
terminal.
The variable x represents the
maximum number of characters on a single
line.
The maximum allowable width of a
line you can input at the terminal is:
n - (width of prompt string including
monitor prompt) - I
For example, if you issue SET SL WIDTH=50,
and
the prompt consists of only the
keyboard monitor prompt (.), then the
maximum number of characters you can type
as input on one line is:
50 - I - I = 48 characters
The default for x is 79.

2-22

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
2.6.2. Differences in Device Naming Conventions
Some host device names are different from their equivalent RT-ll
device names. Always use the host device name when specifying command
lines to RTEM-Il or when attaching a host device by means of the JOAT
IA command ~OAT is described in Chapter 4) •
When RTEM-ll or JOAT detects a device naming conflict during an attach
operation, an informational message is printed. An example of this is
the RSX-ll host device DK. The RT-II name for this device is RK. The
following example displays both RTEM-ll's and JOAT's reaction to using
the host device name.
>RUN $RTEM
RTEM> DKI:/RT
?RTEM-I-Host device DKI:

attached as RT-II device RKI:

RTEM-II V02.xx
RT-IIFB V0S.xx
.DIRECTORY RKI:
SWAP
MTHD

.SYS
.SYS

2SP 21-Feb-82 PIP
4P 21-Jul-82 MT

.SAV 23 21-Feb-82
.SYS 9P 21-Jul-82

GRAPH .FOR
2 IS-Aug-82 DEMOXI.LST 9
RTSJ .MAP 16P 02-Aug-82 DEMOBG.OBJ I
202 Files, 4333 Blocks
429 Free blocks

07-Aug-82
13-,Jun-82

.R JOAT
*DK2: IA
?JOAT-I-Host device DK2: attached as RT-II device RK2:

*/L
RKI:
RW
RK2:
RW
*RK2: IDlY
*"'C

(DKI: )
(DK2: )

Note that while the host device name must be used to attach
devices,theRT-II deviee name must be used to detach them.

2.6.3

foreign

Line Printer Support

RTEM-II uses two device handlers to support the RT-II line printer
interface.
The first device handler
(LP),
is a file-structured
handler.
It takes the data written to the RT-II LP device, and stores
it in a host system file for spooling by the host system's queue
manager. The second device handler
(LS),
is a non-file~structured
handler.
It takes the data written to the RT-II LS device, and
transmits it directly to a host system terminal or line printer.

2-23

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
Which handler you use depends on your host system configuration.
If
your system runs the normal queue manager package supplied by DIGITAL,
then the LP handler will always work. If your system does not run the
queue manager package, you can use the LS handler to do I/O directly
to a terminal or line printer.
When you enter RTEM-II, the LP handler or the LS handler (but not
both)
will be installed in the running RT-II system, depending on the
device type specified by the dev:/LP command line option.
The default device for the dev:/LP option depends on the host ~ystem.
For RSX-IIM systems the default device is SY: [UIC]. This means that
the RT-II LP device will always be installed by default on an RSX-IIM
system.
For all other host sy,stems, the default device is LP0. This
means that either the RT-II LP or LS device handler could be
installed, depending on the pointing characteristics of device LP0.
If LP0 points at a file-structured or spooled device, the LP handler
is installed.
If LP0 points directly at a line printer or terminal,
the LS handler is installed.
Because the RTEM-ll LP handler uses the host system's queue manager
for spooling, it has no SET options. The RTEM-ll LS handler supports
the standard line printer options described in Table 2-2.

2.6.4

RPB2/RPB3 Device Support on RSX-II

RTEM-Il's support of RP02 and RP03 devices differs from RT-Il's
support of these devices, as described in the following paragraphs.
The RT-ll file structure can accommodate a
blocks.
The RP02 disk contains 40000
treats it as a single logical unit.
The
blocks, which RT-Il treats as two logical
That is, an RP03 appears to be two RP02s.

maximum of 65536
(decimal)
(decimal) blocks, and RT-ll
RP03 disk contains 80000
units of 40000 blocks each.

An RP03 disk on physical unit n is identified as logical units DPn and
DPn+4.
For example, an RP03 in unit 0 is DP0 and DP4, and an RP03 in
unit I is DPI and DP5. Each logical unit h~s its own directory and
data space.
RT-II can support up to eight RP02s or four RP03s. You
can mix RP02s and RP03s, as long as the total number of units
(physical drives) on the system does not exceed four.
RSX-li supports up to eight units of a combination of RP02s and RP03s.
This additional support of physical drives allows RTEM-ll to support
four additional units or up to eight units of a combination of RP02s
and RP03s. RTEM-ll uses the DQn handler to accommodate the additional
four units.
If you have a mixture of RP02s and RP03s, four additional units are
available.
RTEM-Il device names DP0 through DP3 refer to RSX-II DP0
tbrough DP3. RTEM-ll device names DQ0 through DQ3 refer to RSX-ll
device units DP4 through DP7. As in RT-ll, if any of these drives are
RP03s, the device names refer to the first half of the volume only.
In this case, RTEM-ll DP4 through DP7 and DQ4 through DQ7 are used to
indicate the second half of their respective RP03s.

2-24

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
If you have RP02s only, you can access eight units as in RT-ll,
al though they are addressed differently.
Refer to the first four
units as DP0 through DP3, and to the second four as D00 through D03.
The following table lists examples of RP02/RP03 usage.
Physical
RP02
RP03
RP02
RP03
RP02
RP03

2.7

in
in
in
in
in
in

Unit
unit 0
unit 0
unit 3
unit 2
unit 7
unit 5

DP0
DP0 and DP4
DP3
DP2 and DP6
DP7
No support

RTEM-ll Logical Unit
DP0
DP0 and DP4
DP3
DP2 and DP6
DP7
DOl and DOS

RESTRICTIONS ON USING RT-Il FEATURES

The following sections
features by RTEM-ll.

2.7.1

RT-II Logical Unit

summarize

restrictions

imposed

RT-ll

Using DATE and TIME Commands

You cannot use the DATE and TIME commands to change the RTEM-ll
values, because these values are obtained from the host system. The
date and time are automatically initialized when you invoke RTEM-ll.
The correct date and time appear in volume directories and listings
produced by t~e various language processors and utility programs.
You can obtain the date and time at your terminal by typing the
DATE and TIME commands.

2.7.2

RT-ll

Using COPY/BOOT Command

The COPY/BOOT command is not restricted under RTEM-ll;
however,
should carefully consider its effects before you use it.

you

Under RT-ll, COPY/BOOT copies the bootstrap information from a monitor
and handler file to blocks 0 through 5 of a direct-access volume,
permitting you to use that volume as a system volume. Under RTEM-ll,
you can use COPY/BOOT for the same purpose.
On virtual devices, COPY/BOOT copies the bootstrap information from
the specified monitor and handler files, which reside in the shared
area, to blocks 0 through 5 of the private area.
The monitor and
system handler files must reside in the shared area. You can rename
the monitor file and copy the bootstrap blocks to a private area as
long as the monitor file resides in the shared area.
RTEM-ll does not require you to alter the bootstrap blocks of a
foreign system volume.
You can use a bootable RT-Il volume as an
RTEM-ll system volume and subsequently boot RT-il as a stand-alone
system from the same volume. The only requirement in this case is
that the RT-Il volume contain an RTEM-li monitor and system device
handler as well as the RT-Il monitor and handlers.

2-25

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
If you use COPY/BOOT to copy the bootstrap of the RTEM-ll monitor,
RTEMFB.SYS, to an RT-ll directory-structured foreign volume, you will
not be able to boot the volume as a stand-alone RT-ll system.
If you use COPY/BOOT to copy the bootstrap of an RT-ll monitor file to
a virtual device, you will not be able to invoke RTEM-ll from the
virtual device.

2.7.3

Using COPY/DEVICE Command

After using the monitor COPY/DEVICE command to copy a device to a
virtual device, you must use JOAT (/U) to reformat the virtual device.
After using the /U option, you must compress the volume with SQUEEZE.
Section 4.2.10 describes how to use JOAT (/U) to
device copied from another device.

2.7.4

reformat

virtual

Debugging with Virtual Debugging Technique (VDT)

Instead of using ODT (on-line debugging technique) to debug programs,
use VDT
(virtual debugging technique). Use VDT.OBJ the same way you
The
use ODT.OBJ;
link it with the program you want to debug.
transfer address is O.ODT, which is the same as the transfer address
for ODT.
The command syntax for VDT is the same as the syntax for ODT.
Refer
to the RT-ll System Utilities Manual for instructions on using ODT.
VDT is part of the RT-ll distribution kit.

2.7.5

Summary of Restrictions

RTEM-ll supports nearly every feature supported under the RT-ll
multiterminal
FB
monitor.
This section lists unsupported and
restricted RT-ll features.
In addition to unsupported and restricted RT-ll features, two features
operate differently under RTEM-ll and RT-ll:
Under RTEM-ll, the BATCH program runs from a read-only virtual
system
device.
Under
RT-ll,
the system volume must be
read/write.
Under RTEM-ll, compressing the virtual system device with the
SQUEEZE command causes an exit to the host system at command
level.
The following subsections summarize unsupported
and
restricted
keyboard monitor commands, utility programs, programmed requests,
devices, and terminal control characters.

2-26

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
2.7.5.1

Keyboard Monitor Commands -

Unsupported
Monitor Command

Comments

FORMAT

Requires direct access to I/O
page.
Use host system utilities
to format.

Graphics display hardware is
supported.

SRUN

System jobs are not supported.
Two DIGITAL-supplied system jobs
are Error
Logger
and
Queue
program.
Queue program can be
run as a foreground job.

Restricted
Monitor Command

not

Restricted
Option

BOOT

Returns user to
command level.

host

/TOPS

Requires
page.

access

/INTERCHANGE

Requires physical I/O
RTEM-ll/VAX only.

DATE

dd-mmm-yy

Host operating system maintains
date
and time,
therefore you
cannot set date under RTEM-ll.

DELETE

/INTERCHANGE

Requires physical I/O
RTEM-ll/VAX only.

directory

?RTEM-F-Directive rejected while trying to attach dev:
An internal RTEM-ll error occurred.
A directive was rejected
for
reasons other than lack of dynamic memory.
This error message
includes the error code value and may include the error code text.
Try to invoke RTEM-II again. Try installing RTEM-II again, using your
distribution kit.
If the error persists, submit an SPR to DIGITAL.
Include with the SPR a description of the host system hardware
configuration, the version number of your host system, and the version
number of RTEM-Il.
?RTEM-F-Directory file not found dev:[directory]
The specified directory does not reside on the specified volume.
Check your command line for typing errors.
?RTEM-F-Directory input error dev:
An error occurred while the directory of the RTEM-II system device was
being read.
This error message includes the error code value and may
include the error code text.
Check for a bad block in the directory of the RTEM-Il system device.
If the RTEM-II system device is a virtual system device, check the
directories of the shared and private areas.
To do this:
invoke
RTEM-II with alternate shared and private areas, attach the former
shared and private areas with JOAT, and use DIRECTORY/BAD on the
former areas.
Check for hard error conditions, such as device off-line.
2-32

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Directory output error filespec
An error was detected while the directory of the newly created private
area was being initialized.
This error message includes the error
code value and may include the error code text.
Ask the system manager to scan the host system device (on which your
directory resides)
for bad blocks. Retry tne operation, specifying
for the private area an explicit size that is different from the
default or that is different from the explicit size originally
specified.
?RTEM-F-Directory too large filespec
The file specified as the shared and/or private area
system device contains too many directory segments.

the

virtual

Try to invoke RTEM-ll with a different private and/or shared area.
Use the JOAT /V option (Section 4.2.11) to access the original private
area as a nonsystem virtual device (VS1: to VS7:) and use SQUEEZE to
try to compress the original private area. If the error persists, the
directory of the shared or private file may have become corrupted or
linked circularly.
The total number of active directory segments in
the shared and private areas cannot exceed 31 (decimal).
?RTEM-F-Duplicate options
The same valid option was used more than once in the command line
RTEM-ll. The command line is printed below the error message.

Check the command line for errors and retry the operation.
?RTEM-F-Error closing file filespec
An error was detected while the newly created file that will serve as
the private area of the virtual system device was being closed. This
error message includes the error code value and may include the error
code text.
Retry the operation.
Try installing RTEM-ll again, using your
distribution kit~
Try to invoke RTEM-ll again specifying that a
different size private file be created. If the error persists, submit
an SPR to DIGITAL.
Include with the SPR a description of the host
system hardware configuration, the version number of the host system
you are using, and the version number of RTEM-ll.
?RTEM-F-Error during extend filespec
An error was detected while RTEM-ll was extending the virtual device
file specified. This error message includes the error code value and
may include the error code text.
?RTEM-F-Error from PARSE filespec
An error was returned from the system PARSE subroutine while parsing
the file specification given. This error message includes the error
code value and may include the error code text.

2-33

RTEM-li SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Failed to attach dev:
RTEM-II could not attach the device specified as the foreign volume
system device.
This error message includes the error code value and
may include the error code text.
It is likely that another u~er has allocated the specified device.
If
the device is allocated, you cannot use it until it is deallocated.
If the device is not allocated, allocate it, mount it as foreign,
and
try to invoke RTEM-ll again.
?RTEM-F-Failed to delete spool file filespec
An error was returned when RTEM-ll attempted to delete the temporary
line printer spool file. This error message includes the error code
value and may include the error code text.
?RTEM-F-Failed to mark read/write temporary file for delete filespec
An error was returned when RTEM-ll attempted to mark the read/write
temporary file for deletion. This error message includes the error
code value and may include the error code text.
?RTEM-F-Failed to obtain system date and time
An internal system error causes this error.
The message indicates
that the directive to obtain the host system date and time was
rejected. This error message includes the error code value and may
include the error code text.
Try to invoke RTEM-ll again. Try installing RTEM-Il again, using your
distribution kit.
If the error persists, submit an SPR to DIGITAL.
Include with the SPR a description of the host system hardware
configuration, the version number of the host system you are using,
and the version number of RTEM-li.
?RTEM-F-File already in use;

cannot open filespec

The file cannot be opened because another user is writing to it.
Try the operation again when the file is free.
?RTEM-F-Filename is invalid with /LP
The /LP option was used to specify an invalid RSX-llM line printer
spool device.
The invalid command is displayed below the error
message.
Do not specify a file or RTEM-ll foreign volume with the /LP option.
?RTEM-F-Filename or directory is invalid with /RT
foreign
The /RT option was used to specify a device that is not a
volume.
The invalid command line is displayed below the error
message.
Use the /RT option to specify that a foreign volume will be used as
the
RTEM-ll
system device.
Do not use a file or directory
specification with the /RT option.

2-34

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-File not found filespec
A required system file was not found on the RTEM-II system device.
This message is displayed if the monitor file RTEMFB.SYS, the swap
file SWAP.SYS, or the system device handler file xxM.SYS does not
reside on the system device. Another cause of this error is failure
to locate a specified shared or private file.
Check for typing errors in the command line typed to the RTE prompt.
If necessary,
retype the command.
Use the format described in this
chapter for the command.
Make sure the necessary RTEM-II system files
reside on the system device. Be sure to specify existing files to be
used as shared or private files.
?RTEM-F-File too large filespec
The highest block number of the shared and/or
virtual system device is larger than one word.

private

file

the

RTEM-li cannot represent block numbers this large in its
I/O
structures.
Use a different shared or private file.
Try to truncate
the file to not more than a single word (65535 decimal) •
?RTEM-F-File too small DEV:SWAP.SYS
The SWAP.SYS file on the RTEM-ll system device is too small for the
current version of RT-li.
The SWAP.SYS file must be at least 26
blocks for RT-Il V5.0.
Delete and recreate the SWAP.SYS
blocks. Then retry the command.

file

with

the

proper

number

?RTEM-F-Bome block input error filespec
An error was detected when RTEM-Il tried to read the home block of the
foreign volume system device or of the virtual system device private
file.
The device or file may have a bad block in the home block
(physical block I
of foreign volumes, virtual block 2 of virtual
devices). This error message includes the error code value and may
include the error code text.
Retry the operation.
If you are using a virtual system device,
try
copying the private file using the host system COpy command.
If you
are using a foreign volume,
invoke RTEM-Il from a virtual system
device
(using /VS) and access the volume as a nonsystem device using
JOAT.
?RTEM-F-Bome block output error filespec
An error was detected when RTEM-li tried to write to the home block of
the private file just created. This error message includes the error
code value and may include the error code text.
Ask the system manager to scan the host system device (on which your
directory resides)
for bad blocks. Retry the operation, specifying
for the private area an explicit size that is different from the
default or from the explicit size originally specified.

2-35

RTEM-II SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Bost system device driver not loaded dev:
The host system device driver for the RTEM-ll
device is not resident in memory.

foreign

Ask the system manager to load the correct host
retry the operation.

volume

system

driver,

then

?RTEM-F-Input error creating read/write temporary file filespec
The read/write temporary file is created by copying SWAP.SYS and all
the files after it in the shared directory to a temporary file.
An
error was detected while these flIes were being copied from the
virtual system device to the temporary file.
This error message
includes the error code value and may include the error code text.
Ask the system manager about the error code value.
If the
manager cannot correct the 'error, submi t an SPR to DIGITAL.

system

?RTEM-F-Input error filespec
A hard error occurred while the specified file or
read.
This error message includes the error
include the error code text.

device was being
code value and may

See the section on hard error conditions in the RT-ll
Manual.

System

Message

?RTEM-F-Invalid command line
An invalid command was entered.
error message.

The

command

printed

below

Check for a missing device or file name in the command line.
the syntax of the command and retype it.

the

Correct

?RTEM-F-Invalid directory dev:
The specified RTEM-ll system device does not
format directory structure.

contain

valid

RT-ll

If you are using a foreign volume system device, it must have a
RT-ll directory structure.

valid

?RTEM-F-Invalid option combination
An invalid combination of options was specified in the command
The invalid command is displayed below the error message.

line.

Check this chapter for valid combinations of options that are directed
to the bootstrap task.
?~TEM-F-Invalid

private ditectory filespec

The file specified as the private area of the
does not contain a valid RTEM-ll directory.
Check for typing errors in the command line.

2-36

virtual

system

device

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Invalid shared directory filespec
The file specified as the shared area of the
does not contain a valid RTEM-ll directory.

virtual

system

device

corresponding

device

Check for typing errors in the command line.
?RTEM-F-Missing device specification
The /RT or /LP option was specified
specification.

without

Use the /RT option to specify an RTEM-ll foreign volume as the system
device.
Use the /LP option to specify a Files-II device for use as
the default line printer spooling device.
?RTEM-F-Missing option
An option is missing from a
directory, or file name.
error message.

command line that includes a device,
The command line is displayed below the

Retype the command line, including an appropriate option.
?RTEM-F-Monitor version mismatch filespec
An attempt was made to boot an RT-Il monitor that does
RTEM-II bootstrap module or is out of date.

not

have

the

Install RTEM-ll again, using your distribution kit.
?RTEM-F-Non-bootable handler xxM.SYS
The specified system device handler is not a bootable
handler does not contain a primary bootstrap routine.

handler.

The

Invoke RTEM-ll from a bootable device.
?RTEM-F-Output error creating read/write temporary file filespec
The read/write temporary file is created by copying SWAP.SYS and all
the files after it in the shared directory to a temporary file.
An
error was detected while writing these files to the temporary file.
This error message includes the error code value and may include the
error code text.
Ask the system manager about the error code value.
If the
manager cannot correct the error, submit an SPR to DIGITAL.

system

?RTEM-F-Private file directory may be corrupt filespec
The directory segments corresponding to the private area indicate that
the Files-II file is larger than it actually is. The private area may
have become corrupted.
Invoke RTEM-ll from a different private area. Use the JOAT /V option
(Section 4.2.11)
to attach the corrupted file as a nonsystem virtual
device.
Examine the device's directory.
If the directory
is
corrupted,
try to copy all the RTEM-ll files to another virtual
device.

2-37

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Private file too large
The virtual system device private file is too large.
the file is extended by a large amount.
Truncate the private file to not more
available for RTEM-II file storage.

than

the

This
number

occurs
of

blocks

?RTEM-F-Shared directory not squeezed !ilespec
The shared directory was not squeezed after bei~
files in the shared directory are not protected.

extended,

some

Tell your system manager about the problem.
See Chapter 6 for
information about modifying the virtual system device shared area.
Follow the procedures in that chapter for invoking RTEM-Il from a
different shared area,
attaching
the original shared area as a
nonsystem device, and using JOAT and FIP to make the original shared
area a valid RTEM-I) shared file.
Alternatively, try creating a new
shared area using JOAT /S and copying all the files from the original
shared area to it.
?RTEM-F-Timed out before attaching dev:
1.

After waiting for the specified foreign volume system device to be
attached, RTEM-li returns this error message.
If no one else is using the device, retry the operation.

Another user may
allocating it.

have

attached

the

specified

device

without

Try again when the device is free.
3.

This error can also occur if the system is heavily loaded, and the
RTEM-li timeout period expires before the host system processes
the attach request.
Try again.

?RTEM-F-Unable to assign LUN to dev:
The logical unit number (LUN) for the RTEM-ll system device
(SY:)
is
in use, or the specified device is not a valid RTEM-li system devi~e.
This error message includes the error code value and may include the
error code text.
Check the syntax of your command and retry the operation.
?RTEM-F-Unable to get LUN information
An internal error occurred.
Information about the logical unit number
(LUN)
for the specified foreign volume system device should be
available to RTEM-ll. This error message includes the error code
value and may include the error code text.
Try installing RTEM-II again, using your distribution kit.
If the
error persists, submit an SPR to DIGITAL.
Include with the SPR a
description of the host system hardware configuration, the version
number of the host system you are using, and the version number of
RTEM-li.

2-38

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-F-Unable to open filespec
This error message includes the error code value and may
error code text.

include

the

The file specified as the shared or private file
system device could not be opened.

Check the command line for typing errors. Check the
directories to make sure the specified file exists.
2.

the

virtual

appropriate

The line printer spool file could not be opened.
Make sure that the specified
corresponding to your UIC.

device

contains

directory

?RTEM-F-Unable to open for output filespec
An error occurred when RTEM-ll attempted to open the specified file
for output. This error message includes the error code value and may
include the error code text.
Ask the system manager about the error code value.
If the
manager canrrot correct the error, submit an SPR to DIGITAL.

system

?RTEM-F-Unable to specify SREX$ abort ast
RTEM-ll was unable to execute the RSX-ll di(ective SREX$.
This error
occurs when RTEM-ll
is running under the wrong version of RSX-ll or
when the RSX-ll system has not been generated with the SREX$
directive.
Have your system manager update your RSX-ll operating system with
correct version and/or system generation options.
?RTEM-F-Use of

'*' or '='

the

is invalid

The entered command contained an asterisk
(*) or equal sign (=).
These symbols are invalid in commands directed to the bootstrap task,
RTE. The invalid command is displayed below the error message.
Check the command line for typing errors and retry the operation.
?RTEM-F-Virtual device too small filespec
An attempt was made to create a virtual device file with an initial
allocation of less than eight blocks.
If allowed, this would create a
file with no free blocks, as the boot blocks and directory take up at
least eight blocks.
?RTEM-F-Virtual system device too large filespec
The file specified as the shared or private area of the virtual system
device is too large, or the combined sizes of the shared and private
files produce a virtual system device that is too large.
You can
still access the file by using the JOAT utilities /A command,
discussed in Section4.2.1.
See Section 2.5.6 for information on calculating the maximum size of
the virtual system device.
Make sure the directory of the shared or
private file is not corrupted.

2-39

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-I-Cannot open for write;

opening read-only filespec

You do not have read/write access to the specified file.
RTEM-ll
tries to open the same file read-only. Your system manager may h~ve
built the RTEM-ll task so it prompts "Are you sure?" before openlng
the file read-only.
If the file is opened read-only, the resulting
virtual system device will be permanently write-locked.
This is an informational message.
If your message is followed by "Are
you sure?", type Y to open the file read-only.
?RTEM-I-Extending private file filespec
The virtual system device private file is being extended
to the /EX command line option.

response

This is an informational message.
?RTEM-I-File not found; creating new private file
dev:[directory]RTllPR.SYS;0
The default virtual system device private file was not located.
This is an informational message indicating that
being created for you.

private

file

?RTEM-I-File not found; creating new private file
dev:[dir]RTllPR.SYS;0
Are you sure?
The specific file requested as the private area could not be located.
Type Y to create a file with the specified name;
will prevent creation of the file.
?RTEM-I-Host device Dev:

any

other

response

attached as RT-Il device Dev:

This message informs you that, after booting the host device named,
you must use the RT-ll device name to refer to it under RTEM-ll. See
Table 2-1 for more information on device naming conventions.
This is an informational message.
?RTEM-I-/LP switch ignored
The /LP option was specified on a command line while running under
RSX-llM-PLUS or VAX/VMS.
The /LP option is meaningful only under
RSX-llM.
This is an informational message.
?RTEM-I-Virtual device should be squeezed
dev:[directory]filename.ext;ver
The /EX option to extend
subsequent SQUEEZE command.

virtual

device

was

used

without

This message reminds you to use the SQUEEZE command with the virtual
device, so the RT-ll directory can be updated correctly with the new
file size.

2-40

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-U-Aborted via directive, CLI, or user
RTEM-ll has closed all open files and devices and has returned control
to the host operating system. This message can indicate one of the
following conditions:
1.

RTEM-ll encountered the abort character code specified
RTEM-ll command line option lAB (Section 2.5~1).

the

RTEM-II encountered the default abort character code specified by
the system manager during RTEM-Il installation (Section 2.5.1).

RTEM-II was aborted by the RSX-Il MCR ABORT command.
If the abort
was accidental, invoke RTEM-Il again with the appropriate command
line.

?RTEM-U-Command file input error dev: [directory] filename.ext;ver
The specified file containing the RTEM-II command line could not be
opened.
The message could indicate, for example, that the command
line $ RTEM @FOO.CMD was given, and that the Files-II file FOO.CMD
could not be found in the default directory.
Make sure the filespec is correct and retry the operation.
?RTEM-U-Error reading KMON
RTEM-ll detected an error while reading the keyboard monitor
from the RTEMFB.SYS file on the RTEM-Il system device.

(KMON)

Copy the RTEMFB.SYS file from your distribution kit onto your
system device, then try to invoke RTEM-li again.

RTEM-ll

?RTEM-U-Extend task directive failed
RTEM-Il was unable to extend itself to the proper size for correct
operation.
This error message includes the error code value and may
include the error code text.
Check with your system manager to ensure that RTEM-II was installed as
checkpointable. Try having your system manager reinstall RTEM-II from
your distribution kit.
If the error persists,
submit an SPR to
DIGITAL.
Include
a
description of the host system hardware
configuration, the version number of the host system, and the version
number of RTEM-li.
?RTEM-U-Insufficient memory
The RTEM-li bootstrap program does not have enough memory to boot the
RTEM-ll monitor. RTEM-ll needs at least 24K (decimal) words to run.
Have your system manager try to install RTEM-ll again.
persists, submit an SPR to DIGITAL.

?RTEM-U-Invalid host system
RTEM-Il was invoked on an invalid host system.
RTEM-ll will not run on RSX-IID, RSX-IIS, lAS, or RSTS/E.

2-41

the

error

RTEM-lISYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-U-Not installed properly
RTEM-II was invoked before being successfully installed. The message
could indicate, for example, that the RTEM-II file was copied by hand,
directly from the distribution medium, and then run.
Refer to the RTEM-II Installation Guide for instructions on installing
RTEM-ll.
?RTEM-U-RTEM-ll system halt
A fatal error occurred within an RTEM-ll system routine.
In this
case, the RTEM-ll monitor aborts. This error also occurs if the stack
overflows in a user program, and there is no user-specified initial
stack value (location 42 in SYSCOM) to reset the stack.
Make sure the system volume is mounted and ready.
Invoke
using a new copy of the monitor from your distribution kit.

RTEM-ll

?RTEM-U-System error
A fatal internal error occurred in RTEM-ll.
Try having your system manager
reinstall
RTEM-ll
from
your
if the error persists,
distribution kit.
Invoke RTEM-ll again;
submit an SPR to DIGITAL.
Include a description of the host system
hardware configuration, the version number of the host system, and the
version number of RTEM-ll.
?RTEM-U-Unable to attach terminal
The terminal initiating the RTEM-II bootstrap could not be attached by
the program. This error message includes the error code value and may
include the error code text.
Try

includes

the

Make sure a task is not attached to the initiating terminal.
invoke RTEM-li again.
?RTEM-U-Unable to get task parameters
An internal system error occurred. This error message
error code value and may include the error code text.

Try installing RTEM-ll again, using your distribution kit.
If the
error persists, submit an SPR to DIGITAL.
Include with the SPR a
description of the host system hardware configuration, the version
number of the host system you are using, and the version number of
RTEM-ll.
?RTEM-U-Unable to specify SST vector table
An internal system error occurred. The directive to set up a vector
table for fielding synchronous traps failed.
This error message
includes the error code value and may include the error code text.
Try installing RTEM-ll again, using your distribution kit.
If the
error persists, submit an SPR to DIGITAL.
Include with the SPR a
description of the host system hardware configuration, the version
number of the host system you are using, and the version number of
RTEM-li.

2-42

RTEM-ll SYSTEM CONCEPTS AND OPERATING PROCEDURES
?RTEM-W-Required terminal driver options missing
The host system's terminal driver has not been through a system
generation to include all the support RTEM-II requires. This message
is a warning, since RTEM-Il's terminal service generally will not work
properly.
Have your system manager include the correct support in
system, as described in the RTEM-II Installation Guide.

your

host

?RTEM-W-Unable to get terminal driver options
RTEM-II was unable to execute the SF.GMC QIO to get the host system
terminal driver options. This implies that the host system's terminal
driver was not generated with the SYSGEN option "Get terminal driver
options".
This is only a warning, as RTEM-ll's terminal service may
not work correctly. This error message includes the error code value
and may include the error code text.
Have your system manager include the correct support in
system, as described in the RTEM-li Installation Guide.

your

host

?RTEM-W-Unable to set terminal characteristics
This error occurred when RTEM-Il attempted to set the terminal to
PASSALL mode.
PASSALL mode is required for the RTEM-li/RT-ll terminal
service to work correctly under VAX/VMS. This is a warning,
as the
RTEM-ll terminal service will not work correctly. This error message
includes the error code value and may include the error code text.
Have your system manager include the correct support in
system, as described in the RTEM-ll Installation Guide.

2-43

your

host

CHAPTER 3
EXTENDED COMMAND STRING INTERPRETER (ECSI)

RTEM-ll provides two command string
interpreters:
CSI and ECSI.
RTEM-ll's CSI is the same as RT-ll's CSI. ECSI (extended command
string interpreter) allows RTEM-Il's utility programs (FIP and JOAT)
to gain access to files on RSX-ll.
The main difference between ECSI and CSI is that ECSI supports the
host system file specifications as well as RT-ll file specifications.
FIP and JOAT require ECSI because they run solely in the RTEM-ll
environment and directly access host system files. RT-ll utility
programs, such as MACRO and PIP, do not require ECSI because they do
not directly access host system files.

3.1

CALLING ECSI

To invoke a utility program, respond to the keyboard monitor prompt
(.)
by typing R followed by a utility program name and a carriage
return. This example calls the RTEM-ll file
interchange program
(FIP) :
.R FIP

*
ECSI prompts for input by printing an asterisk (*) at the left margin
of the terminal.
To enter valid input, you must obey ECSI's syntax
rules described in the following sections.

3.2

ECSI SYNTAX

Input specifications to ECSI must be in the following syntax:
output-filespecs/option=input-filespecs/option
The syntax for output-filespecs is:
dev: [dir] filename.tYP[i v] [n] , •••
The syntax for input-filespecs is:
dev: [dir] filename.tYP(iV], ••.

3-1

EX~ERDED

COMMAND STRING INTERPRETER (BCSI)

The syntax for /option is:
/o[ :ova1]
or
/o[:dva1.]
Each syntactic element is described in the following paragraphs.
dey:
The logical or physical device name.
For RTEM-11 input or output, a
one- to three-character name from Table 2-1.
For RSX-11 input or
output, a two- to four-character name
(see the RSX-11M/M-PLUS MCR
operations Manual).
For VAX!VMS input or output, a physical device
name'of up to 15 characters from the list of supported devices in the
VAX!VMS Command Language User's Guide.
If you do not supply a device name,
FIP uses the default storage
volume OK:
for the RTEM-11 device or the default user volume for the
Fi1es-11 device.
If you specify a device, it becomes the default device for subsequent
files
in the specification list until you specify a different device
name.
[dir]
The directory specification.
The directory contains the Files-II
input file or will contain the Fi1es-11 ohtput file.
If the input or
output device is an RT-ll format volume, the directory specification
is ignored.
If you omit the directory specification and input or
output is from a Files-II volume,
the default is the current
directory.
The directory specification must be a pair of octal values for RSX-11.
For VAX/VMS it can be a pair of values or an alphabetic string.
If you specify a directory,
it becomes the default directory for
subsequent files in the specification until you specify a different
directory. The following example uses FIP to transfer files from unit
1 of an RSX-ll RP02 to unit 1 of an RT-11 format diskette:
*OXl: A. BAS, B. OAT, C. OBJ=OP 1: [120,40] A. BAS, B. OAT, (240,40] C • OBJ /F
This command is interpreted as follows:
*DXl:A.BAS,B.DAT,C.OBJ=DPl: [120,40]A.BAS,DPl: [120,40]B.DAT,DPl: [240,40]C.OBJ/F

In this example, the RSX-11 input files A.BAS and B.OAT reside in
[120,40]
and the file C.OBJ resides in [240,40]. These files are
transferred under the same names from the RSX-l1 volume on OPl:
to
the RT-ll format foreign volume on OXl:.
filename
The file name, an alphanumeric string of one to nine characters.
You
can include as many as three output file names and six input file
names. RTEM-ll accepts up to six characters in a file name.
VAX!VMS
and RSX-ll accept up to nine characters in a file name.
FIP truncates
RTEM-ll output file names to six characters if necessary.

3-2

EXTENDED COMMAND STRING INTERPRETER (BeSI)
.typ
The file type. A one- to three-character file type preceded by a
period.
If you omit the period and the file type, the running program
may apply a default file type.
[ 1V]

The version number.
An octal or decimal number,
preceded by a
semicolon,
that distinguishes host system files that have the same
name and type. The default for host system input files is the highest
existing version number.
For output files, it is one number higher
than the highest existing version number.
[n]

Optional:
indicates the number of blocks (n) needed for an RTEM-II
output file.
The value n is a decimal number (up to 65535) enclosed
in square brackets~ immediately following the output file to which it
applies.
/o[:oval] or /o[:dval.]
One or more options whose functions vary according to the program you
are uSlng.
The value oval is an octal number or one to three
alphanumeric characters (the first of which must be alphabetic).
The
value dval. is a decimal number followed by a decimal point. You can
use a minus sign (-) to denote negative octal or decimal numbers.
These options and their values should follow the device and file name
to which they apply. You can mix octal, Radix-50, and decimal values.
=

A delimiter that separates the output and input fields.
the delimiter if there are no output files.

3.3

You can

omit

apply

under

WILDCARD USAGE

Rules governing the use of wildcards under RT-II
RTEM-II. This section summarizes wildcard usage.

also

Some commands accept wildcards (% and *) in place of the file name,
file type, or characters in the file name or file type. The system
ignores the contents of the wildcard field and selects all the files
that match the remalnlng fields. The percent sign (%) ignores the
contents of one character in the field;
the asterisk (*) ignores the
contents of any number of characters in the' field.
An asterisk (*) can replace a file name:
*.MAC
All files on device DK that
regardless of their name.

have

.MAC

file

type

are

selected,

An asterisk (*) can replace a file type:
TEST.*
All files on device DK that are named TEST are selected, regardless of
their file type.

3-3

EXTENDED COMMAND STRING INTERPRETER (BCSI)
An asterisk (*) can replace both name and type:
*.*
All files on device DK are selected.
An embedded asterisk (*) can replace any number of characters
input file name or file type:

the

A*B.MAC
All files on device DK with a file type of .MAC whose file names start
with A and end with B are selected. For example, AB.MAC, AXB.MAC, and
AXYB.MAC are selected.
The percent symbol (%)
is always considered to be an embedded
wildcard. It can replace a single character in the input file name or
file type:
A%B.MAC
All files on device DK with a file type of .MAC whose file names
three characters long, start with A and end with B, are selected.
example, AXB.MAC, AYB.MAC, and AZB.MAC are selected.

3-4

are
For

CHAPTER 4
JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)

The jack-of-all-trades (JOAT) utility program performs a variety of
system and device operations.
For example, while you can do most
program development using just the system device, console terminal and
line printer, you may occasionally require other peripheral devices.
JOAT lets you use any host system device supported by RTEM-ll.
You
can also use JOAT to terminate RTEM-ll, to suspend RTEM-ll and pass
command lines to RSX-ll, and to show current device usage.

4.1

CALLING AND TERMINATING JOAT

To call JOAT, type:
• R ,]OAT
JOAT prints an asterisk and waits for a command string.
To terminate JOAT and return control to RTEM-ll, type CTRL/C when JOAT
prompts for
input. You can type two CTRL/Cs to terminate JOAT while
it is executing a command. To restart JOAT, type R JOAT.

4.1.1

JOAT Command String

JOAT commands vary in form according to their purpose.
Thus, a
command can include a file name,
a device code, and an option
specification, or any combination of these elements.
In general,
the
syntax of a JOAT command is:
[filespec] [=] [dev:] [/0]
where filespec

represents the output file name.
is the delimiter between the input side and the output
side of the command string.

dev:

represents a device code.

represents an option.

4-1

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
HELP Command

4.1.2

To display information about JOAT command syntax, type HELP JOAT when
you see the keyboard monitor prompt. Note that the RT-ll HELP.SAV
program must reside on the current RTEM-ll system device for the HELP
command to work •
• HELP JOAT
JOAT

Does various and sundry useful things.

SYNTAX
dev:/option
filespec/option
filespec=dev:/option
/option

4.2

/A, /0, /L, /U, /W
/C, /C/Z, Iv, /V/T, /V/U
IS, /S/O
/E, /M, /L

JOAT COMMAND OPTIONS

JOAT command options are divided into three categories:
file options,
device options, and options that take no specification. JOAT options
can be placed on the input or output side of a command string.
The
following table summarizes JOAT options. The options and their syntax
are described in Sections 4.2.1 through 4.2.14.

Explanation

Option
/A

Attaches an RT-ll format device for use by an
RTEM-ll user or program. /A is the only JOAT
option that requires a host system device
specification.
(See Section 4.2.1.)

/C[:n]

Creates a file for use as a virtual device.
The optional value n is the size of the file
in blocks. The default size is 494 blocks.
Specify the file with a host system file
specification.
(See Section 4.2.2.)

previously
Detaches a device
that
was
attached with /A, IV, or /C. Specify the
(See
device with an RT-ll device name.
Section 4.2.3.)

/E[:n]

Exits from RTEM-ll.
Control ~eturns to host
system.
The optional value n specifies the
RTEM-ll task exit status that is returned to
the host system. Default value is 1.
(See
Section 4.2.4.)

Lists current
4.2.5.)

gives
Temporarily interrupts RTEM-ll and
(See section
control to RSX-ll host system.
4.2.6.)

device

usage.

(See

Section

(Continued on next page)

4-2

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
/O[:xxx]

Used with /S to establish the order of files
in read/write area of a shared virtual device
file.
Options for :xxx are ADD, NEW, SAV,
UPD.
The
system manager uses /0 when
modifying the virtual system device.
(See
Section 4.2.7.)

creates a shared area from an RT-l1 format
volume or an existing virtual device. The
system manager uses /S when modifying the
virtual system device.
(See Section 4.2.8.)

/T:n

Used with /V to extend a virtual device by
(octal) blocks.
(See Section 4.2.9.)

Converts a shared area into a
private area
for update purposes.
Use /U after using
COPY/DEVICE. The system manager uses it to
mod i fy
the vi rtual system devi ce.
(See
Section 4.2.10.)

/V [:VSn]

Specifies a host system file to be used as a
virtual device by RTEM-ll.
Units 0 through 6
may be specified (n).
(See Section 4.2.11.)

/W[ : NO]

Write-protects a device.
To write-enable the
device,
use :NO. Specify the device with an
RT-ll device name.
(See Section 4.2.12.)

Suppresses queries that appear before an /A,
/0 or /E option is executed.
(See Section
4.2.13.)

Used with /C to create a virtual device
temporary file.
The file is automatically
deleted when detached by the /0 option or
when you exit RTEM-ll.
(See Section 4.2.14.)

4.2.1

Attaching a Physical Device (/A)

JOAT lets you use additional devices for mass storage.
When you invoke RTEM-ll,
the RTEM-ll program attaches to your
terminal.
To acquire additional storage, you must attach devices to
your terminal.
The /A option attaches a physical device. You can use /A to attach
RT-l1 format foreign volumes to your terminal and acquire more storage
space. You can attach any device supported by RTEM-ll and installed
on the host operating system.
(Table 2-1 lists the devices RTEM-ll
supports. )
Because you are attaching a volume that is foreign to the host
operating system, you must allocate and mount the volume before using
/A. You can use the /A option with the /L or /W options.

4-3

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
The /A option is the only JOAT option that
device name.
The syntax of the command is:

requires

host

system

dev:/A
If you are attaching an RK05, remember to use the RSX-II device
DKn. The following example attaches RK05 unit 0 under RSX-II:

name

• R JOAT
*DK0:/A
RT-II can accommodate up to eight units of one type of device.
The
host operating system, however,
permits access to more than eight
devices of one type. JOAT lets you access all devices on the host
system by truncating host device unit numbers to the unit number range
o through 7. Host device units above 7 are mapped by JOAT to unit
numbers in the range of 0 through 7. This is shown for device xx in
the following table.
RSX-II
Unit

VAX/VMS
Unit

RT-il
Unit

xx0

xxA0

xx0

xx7
xxl0
xxII

xxA7
xxB0
xxBI

xx7
xx0
xxi

You cannot simultaneously use two devices of the same type if their
unit numbers map to the same value.
For example, you cannot use xx0
and xx10 at the same time.

4.2.2

Creating a Virtual Device (/C[:n])

You can use the Ie option to create a file and attach it to a virtual
device unit. The Ie option can be combined with IL, IV, IW, or IZ.
Specify the file with a host system file specification.
You can
specify the size of the virtual device with any value n between 8 and
65535 blocks. While you can create a virtual device file of any size
up to 65535 blocks, you may not be able to use a large virtual device
file as the private area of the virtual system device pair.
See
Section 2.5.6 for informat-ion about calculating the maximum size of a
private area of the virtual system device. The default size is set by
the system manager during RTEM-II installation. The default location
for the file is the current account.
The syntax of the command is:
f ilespecle [: n]
After it is created, the file is attached
RTEM-li.
JOAT assigns the first free
device and displays the message:

as a virtual device to
un i t numbe r to the virtual

?JOAT-I-Attached to VSn:
This message tells you which unit was assigned.

4-4

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
Before you use IC, you should use the JOAT IL option to list the
device units currently in use.
If no virtual device units are
available when the file is created, RTEM-11 displays the following
message:
?JOAT-F-No VS unit available
Detach a virtual device and retry the operation.
To override JOAT's unit assignment, combine the /V:VSn option with the
IC option, specifying a value for n (unit number). Unit numbers range
from 0 to 7. Do not use unit number 0 if you are running from a
virtual system device. The virtual system device is VS0.
The following command creates the file NEWRTFILE.DSK and
as virtual device unit 3:

attaches

*NEWRTFILE.DSK/C/V:VS3
The following command also creates the file NEWRTFILE.DSK,
but this
file
is deleted automatically when it is detached or when you exit
RTEM-l1.
*NEWFILE.DSK/C/V:VS3/Z
When JOAT initializes the virtual device file, the default number of
directory segments is based on the size of the virtual device as
follows:
File Size
in Blocks

Default Number of
Directory Segments

Up to 512
513 to 2048
2049 to 12288
12289 or more

1
4
16
31

If you require some other number of directory segments, use the RT-11
INITIALIZE command after creating the virtual device with the JOAT /C
option.

4.2.3

Detaching a Device (/D)

You can use /D to detach a foreign or virtual device
After you detach a virtual device,
the unit is
reassignment. You can use /D with the /L option.

4-5

from RTEM-ll.
available for

JACK-OF-ALL~YRADES

UTILITY PROGRAM (JOAT)

Specify the device to be detached with an
Table 2-1. When you use /0, JOAT prints:
?JOAT-I-dev:/Oetach;

RTEM-ll

device

name

from

Are you sure?

You must type Y<RET> to execute the command.
The syntax of the command is:
dev:/O
The following example detaches unit 1 of an RL~l:
.R JOAT
*OLl:/O
?JOAT-I-DLl:/Detach; Are you sure? Y

*
If you attempt to detach the
error message is displayed.

RTEM-ll

system

device,

the

following

?JOAT-F-Cannot detach RTEM system device dev:
Always detach any foreign RT-ll RK~6/RK~7 and RL~1/RL~2 disk volumes
using /0 before you switch the disk cartridges. After yqu have
inserted a new cartridge and turned on the disk drive, attach th~ new
device with the /A option.
RT-ll supports bad block replacement on these disks.
Since the
RTEM-ll device haridlers have bad block information in memory and
cannot tell when power is turned off to a disk pack, failure to detach
any foreign volumes may result in the corruption of data on the
substituted disk pack(s).

4.2.4

Exiting from RTEM-ll (/E[:n])

Use the /E option to exit from
queries:
?JOAT-I-/Exit RTEM-Il;

RTEM-ll.

After

you

type

/E,

JOAT

Are you sure?

Respond with a Y to exit from RTEM-ll.

For example:

.R JOAT
*/E
?JOAT-I-/Exit RTEM-ll; Are you sure?
$

The prompt ($) indicates the host operating system is ready to accept
a command.
At this point, all RTEM-Il devices are detached and all
files, including files serving as RTEM-ll virtual devices, are closed.
The optional value n specifies the exit status that is returned to the
host operating system when RTEM-ll exits. The default value is 1.

4-6

JACK-OP-ALL-TRADES UTILITY PROGRAM (JOAT)
4.2.5

Listing RTEM-ll Device Usage (/L)

The IL option lists all devices currently attached to RTEM-ll.
Use
this option to find out what devices are attached to RTEM-ll before
you attach or detach a device, or create a virtual device.
The IL option accepts no file or device specifications.
combined with any other JOAT option except /E and 1M.

can

The listing consists of two sections. The first section lists all
attached virtual device files;
the second lists all attached foreign
devices. The first section has five columns:
Virtual device file (VS0:

through VS7:)

Access code, RW (read/write) or RO (read-only)
Temporary-file marker (/TMP) indicating the file was created by
means of JOAT's /Z option, and will be deleted automatically when
detached or on exit from RTEM-ll.
Number of blocks in virtual device file (decimal)
Host system file to which the RT-ll virtual device is attached
The second section of the listing has three columns:
RT-ll physical device name
Access code (RW or RO)
Host device name,. if it differs from RT-ll device name (see Table
2-1)
The listing format is illustrated in the following example •
• R JOAT
*/L
VS0:
VSl:
VS2:
DL0:
OXl:
*

RO
RW
RO
RW/TMP
RO
RW

[3092]
[10320]
[1000)

OR0: [SYS0.SYSLIB]RTllSH.OSK;1
OB0: [SMITH]RTllPR.OSKil
OB0: [SMITH.RTEM]FORTRAN.OSK;l
OB0: [SMITH]TEMP.OSK;l

(CSl:)

In the example, three virtual devices are attached. The first
(VS0:)
is the virtual system device, consisting of two files. The first file
listed comprises the shared area and is assigned read-only access
(RO) •
The second file comprises the private area and is assigned
read/write access (RW). The number of blocks in the virtual system
device pair (3092) represents the combined size of the shared file and
the private file.
The second virtual device (VSl:) is attached read-only to
OB0: [SMITH.RTEM]FORTRAN.DSKil.
It comprises 10320 blocks.

the

file

file
to
the
The third virtual device
(VS2:)
is
attached
OB0: [SMITH]TEMP.OSKil.
It
is assigned read-write access, and is
VS2:
marked /TMP to indicate it was created by JOAT's /Z option.
will be deleted when detached or on exit from RTEM~ll.

4-7

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
Two foreign devices are attached. The first
is RL01/RL02 unit 0,
attached with read-only access.
The second is the VAX/VMS console
diskette, attached with read/write access.
Because the host device
name (CS1:) differs from RT-ll's (DX1:), the host device name is shown
in parentheses.

4.2.6

Passing Commands to RSX-ll (/M)

The /M option temporarily suspends RTEM-ll and gains the attention of
the RSX-ll command interpreter.
By using this option, you can perform
RSX-ll functions without exiting from RTEM-ll.
The /M option accepts no file or device specification.
/M, JOAT first returns the following message:

When

you

use

after

you

have

?JOAT-I-Returning to host system

A second message tells you how

to
performed the required operations:

restart

RTEM-ll

?JOAT-I-Type "DCL>START taskname" or "MCR>UNSTOP
continue

t~skname"

The command to restart RTEM-ll
includes
the
task
identifier
"taskname".
Depending on the system you are using, this is either
RTETn (n being your terminal number) or ••• RTE.
If you're not sure which command
interpreter is running at your
terminal,
type CTRL/C when the implicit prompt (» appears after you
suspend RTEM-ll.
The explicit prompt DCL> or MCR> will be displayed.
If your
terminal is set to DCL, type START taskname when you want to
restart RTEM-ll.
If your terminal is set to MCR, type UNSTOP taskname
to restart RTEM-ll.
The following example uses the /M option to get a
directory listing of the host system directory:
• R JOAT

*/M
?JOAT-I-Returning to host system
?JOAT-I-Type "DCL>START RTET4" or "MCR>UNSTOP RTET4" to continue
>OIR
DIRECTORY DMl: [230,72]
16-0CT-81 11:04
FLY. TXT; 1
RTIlPR.SYS;4
RTFILE.SYS;3
RTF4.SYS;6

2.
494.
494.
494.

12-0CT-82
20-AUG-82
16-SEP-82
02-NOV-82

10:23
15:10
13:15
12:00

TOTAL OF 1484./2000. BLOCKS IN 4. FILES
>START RTET4

*
The asterisk indicates that JOAT is ready to accept another command.
DCL command syntax is described in the RSX-lIM/M-PLUS Command Language
Manual.
MCR command syntax
is described in the RSX-lIM/M-PLUS MCR
Operations Manual.

4-8

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
4.2.7

Ordering Files on a Virtual System Device (/O[:xxx])

Use the /0 option with /S to establish the order of files in the
shared area of a virtual system device. The system manager uses the
/0 option to update the virtual system device.
Section 6.1.5
describes the /0 option as one step in the modification procedure.
The following command line illustrates the use of the /0 option:
*output-filespec=input-device:/S/O[:xxx]
The values for xxx are ADD, NEW, SAY, and UPD.
ADD causes files that reside in the mark zone
(all blocks following
SWAP.SYS)
to remain unchanged, and prompts for additional files to be
copied to this area. When you see the prompt File?, type the names of
files you want to move from the read-only area of the volume to the
mark zone. The ADD option is the operational equivalent of the SAY
and NEW options.
Files added to the volume are positioned in the
order in which they are specified.
NEW is the default for /0. Option /0 adds files you specify to the
mark zone. The files are added after SWAP.SYS, BAM.SYS, and IND.SAV.
The NEW option prompts File?
Type the names of files that you want
to move from the read-only area to the mark zone.
Files added to the
volume are positioned in the order in which they are specified.
SAY causes the position of files
SWAP.SYS to remain unchanged.

that

reside

blocks

following

UPD lists every file in the mark zone following the SWAP.SYS file and
prompts "Include file filnam.typ?" for each file.
Type Y followed by
a carriage return if you want the specified file to remain in the mark
zone. Type N followed by a carriage return if you want the file to be
moved to the read-only area.
N is the default. After all files
in
the mark zone have been listed, the prompt File?
is displayed. Type
the names of files you want to move from the read-only area of the
volume to the mark zone.
Files added to the volume are added in the
order in which they are specified.
The following example illustrates the /O:UPD option:

Procedure
[1] $ RTEM/VS
RTEM-ll (Host type) V02.xx
RT-IIFB V05.xx
[2]

.R ,JOAT
*INPUT.DSK/V:VSI
* .. C

4-9

JACK-OP-ALL-TRADES UTILITY PROGRAM (JOAT)
[3]

[4]

.DIR VS1:/FAST
22-Apr-82
RTEMFB.SYS
DDM
.SYS
DTM
DQM
.SYS
.SYS
RKM
VSM
.SYS
• SYS
FIP
.SAV
JOAT .SAV
SIPP .SAV
VDT
.OBJ
SRCCOM.SAV
LIBR .SAV
DIR
.SAV
RESORC.SAV
SWAP .SYS
BAM
.SYS
38 Files, 901 Blocks
o Free blocks

DMM
.SYS
DYM
.SYS
MSM
.SYS
KED
.SAV
DUMP .SAV
CREF .SAV
SYSMAC.SML

DPM
.SYS
NLM
.SYS
WRITE .SAV
HELP .SAV
BINCOM.SAV
MACRO .SAV
SYSLIB.OBJ

DLM
• SYS
DXM
• SYS
LPM
• SYS
KED
• SAY
DUMP .SAV
CREF .SAV
SYSMAC.SML
WRITE .SAV

DMM
• SYS
DYM
• SYS
MSM
• SYS
HELP .SAV
BINCOM.SAV
MACRO .SAV
SYSLIB.OBJ

DPM
• SYS
NLM
• SYS
FIP
.SAV
SIPP .SAV
SRCCOM.SAV
DIR
.SAV
SWAP • SYS

.R JOAT
*OUTPUT.DSK=VSl:/S/O:UPD
?JOAT-I-Attached to VS2:
Include file BAM
.SYS? YES
Include file IND
File? WRITE.SAV
File?
*"'C

[5 ]

.SYS
.SYS
.SYS
.SAV
.SAV
.SAV
.SAV
.SAV

DLM
DXM
LPM
DUP
BATCH
LINK
PIP
IND

• SAY? YES

.DIR VS2:/FAST
22-Apr-82
RTEMFB.SYS
DDM
.SYS
DQM
.SYS
DTM
.SYS
RKM
.SYS
VSM
.SYS
JOAT .SAV
DUP
.SAV
VDT
.OBJ
BATCH .SAV
LIBR .SAV
LINK .SAV
PIP
.SAV
RESORC.SAV
BAM
.SYS
IND
.SAV
38 Files, 901 Blocks
o Free blocks

Explanation
[1] The user enters RTEM-ll from the host system command level.
[2] The user invokes JOAT and attaches the input virtual file on unit
VS1:.
[3] A directory of the input virtual file shows the current
of the files.

ordering

[4] Using JOAT, the user creates the shared file OUTPUT.DSK, with the
input virtual device file INPUT.DSK on unit VS1:. Responding to
the prompts presented through the /O:UPD option,
the user
includes the files BAM.SYS, IND.SAV, and WRITE.SAV in the
read/write mark zone of the output shared file OUTPUT.DSK.
[5] A directory of the newly created shared file shows that the file
WRITE.SAV was included in the read/write mark zone. Remember
that the read/write mark zone of a shared virtual device file is
defined as all files including and following the file SWAP.SYS.

4-10

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
4.2.8

Creating a Shared Area (/S)

The /S option creates a shared area from an existing virtual device or
RT-ll format foreign volume.
After modifying a shared area, the
system manager uses /S to modify the directory. The following command
line illustrates the use of the /S option:
*output-fi1espec=input-device:/S
Use of the /S option with the /0 option is described in Section 4.2.7.
Section 6.1.4 describes the /S option as a part of the modification
procedure.

4.2.9

Extending a Virtual Device (/T:n)

Use the /T option with /V to extend a virtual device by adding storage
space.
You must specify the number (n) of blocks to be added to the
device. There is no default extension value. The /T option must be
used with /V and may be combined with /L or /W.
The command syntax is:
fi1espec/V[:VSn]/T:n
You must compress the volume (with the monitor SQUEEZE command)
or
initialize it
(with the monitor INITIALIZE command) to obtain the
correct size of the volume.
For example:
*RTFILE.DSK/V/T:50
?JOAT-I-Virtual device should be squeezed RTFILE.DSK;l
?JOAT-I-Attached as VS2:
A DIRECTORY/FREE command'shows the free blocks
volume was extended:

VS2:

before

the

.DIRECTORY/FREE VS2:
22-0CT-80
<UNUSED>
4
<UNUSED>
3
<UNUSED>
445
o Files, o Blocks
452 Free blocks
After the volume is squeezed, a DIRECTORY/FREE command shows
size of the volume:
• SQUEEZE VS2:
VS2:/SQUEEZEi Are you sure? Y
.DIRECTORY/FREE VS2:
l6-0CT-80
<UNUSED>

492

o Files, 0 blocks
492 Free Blocks

Chapter 6 shows how to extend the virtual system device.

4-11

the

new

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
4.2.10

Updating a virtual Device (/U)

The /U option converts a shared area into a private area where you can
add, delete, move or modify files. This option also reformats the
virtual device specified as the target in a COPY/DEVICE command.
The
virtual device that is the copy must be reformatted with /U after
COPY/DEVICE is used.
The syntax of the command is:
*dev:/U
After you copy a device to a virtual device with the COPY/DEVICE
command, use /U to reformat the virtual device. After using the /U
option, you must compress the volume (with SQUEEZE). For example:
.COPY/DEVICE VS2: VS4:
VS4:/Copy; Are you sure? Y
• R ,JOAT
*VS4 :/U

*.. C

.SQUEEZE VS4:
VS4:/Squeeze; Are you sure? Y
The system manager uses the /U option to
device (see Chapter 6) •

4.2.11

modify

the

virtual

system

Attaching a Virtual Device (/V(:VSn])

The IV option attaches a Files-II file to RTEM-ll as an RTEM-ll
virtual device. If you do not specify a value, JOAT attaches the file
to the first free virtual device unit. JOAT displays a message to
tell you which unit was assigned. You can combine the IV option with
/C, /L, /0, IS, IT, /W, or /Z.
Once specified, VSn is an
specify eight different
VSn.

RTEM-ll physical device name.
You can
virtual device units (VS0 through VS7) with

The syntax of the command is:
f i 1 e s p e c /V [ : VS n ]
The following command specifies the file RTFILENAM.DSK in the default
directory to be used as virtual device unit 2. The specified file is
opened for read/write access as device VS2.
*RTFILENAM.DSK/V:VS2
If a virtual device file was attached to unit VS2 when the above
command was executed, JOAT asks for verification of the command with
the following prompt:
?JOAT-I-VS2:/Attach supersedes existing assignment; Are you sure?

4-12

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
If you want to complete the operation, enter Y or YES.
If you enter
anything else, the operation will abort. By specifying the option /Y
with the RTFILENAM.DSK/VS2 command, you can suppress the verification
query.
With the /Y option, JOAT will attach the superseding device
without question.
If you are using a virtual system device, it is always VS0.
Do not
reassign VS0 in this case.
If you are using a foreign volume system
device, you can attach VS0 as a storage device.

4.2.12

Write-Protecting a Volume (/W[:NO)

Use the /W option to write-protect a volume. This option prevents a
volume from being accidentally corrupted. Specify the volume with an
RT-ll device name. The /W option cannot be combined with /0, /E, or

/M.
To write-enable a volume, use /W with the :NO option.
the command is:

The

syntax

dev:/W[:NO)
For example, to write-protect the system device:
.R JOAT
*SY:/W
You can also specify the virtual system device as VS0.

4.2.13

Suppressing Query Message (/Y)

Use the /Y option with the /A, /D, /E, or /V:VSn
the query message:

option

suppress

Are you sure?
If you specify /Y, JOAT executes the command immediately. It does not
wait for you to confirm your
intentions.
A command such as the
following causes JOAT to exit without asking if you are sure you wish
to do so:
*/E/Y
$

4.2.14

Creating Temporary Virtual Device (/Z)

Use the /Z option with the /C[:n1 option to create a temporary virtual
device file.
A temporary virtual device file will be deleted
automatically when you:
Detach the device with the JOAT /D option or
Exit RTEM-l1.

4-13

JACK-OP-ALL-"RADES UTILITY PROGRAM (JOAT)
The JOAT /L option identifies temporary virtual devices with the
/TMP.

flag

The following commands illustrate the creation of a temporary virtual
device and a listing displaying it.
After the temporary virtual
device has been detached, an attempt to reattach it fails. The device
file has been deleted automatically on detachment.
*TEMP.DSK/C:l00./Z
?JOAT-I-Attached to VS2:
*/L
RO
RW
VSl:
RW
VS2:
RW/TMP
*VS2 :/D/Y
*TEMP.DSK/V
?JOAT-F-File not
* .. C
.
VS0:

4.3

[3092]
[932]
[100]

DR0: [l,l]RTllSH.DSK;3
DB0: [230,72]RTllPR.DSK;3
DB0: [230,72]RTFILEl.DSK;l
DB0: [230,72]TEMP.DSK;l

found DR0:TEMP.DSK;0

JOAT ERROR MESSAGES

?JOAT-P-Cannot detach RTEM-ll device dev:
An internal JOAT error occurred.
Exit using JOAT IE.
Invoke RTEM-ll and retry the operation. Try the
operation again, using your distribution kit.
If the error persists,
submit an SPR to DIGITAL, including a ~escription of the host system
hardware configuration and version number, and the version number of
RTEM-ll and JOAT.
?JOAT-P-Cannot detach RTEM-ll system device dev:
The device specified with the /D option is the RTEM-ll system device.
You cannot detach the system device.
If you meant to detach a device
other than the system device, type the command again and specify the
appropriate device.
?JOAT-P-Channel in use dev:
An internal JOAT error occurred.
Exit using JOAT IE.
Invoke RTEM-ll and retry the operation. Try the
operation again, using your distribution kit.
If the error persists,
submit an SPR to DIGITAL, including a description of the host system
hardware configuration and version number, and the version number of
RTEM-ll and JOAT.
?JOAT-P-Channel not open dev:
An internal error occurred in JOAT.
Exit using JOAT IE.
Invoke RTEM-ll and retry the operation.
Try to
use a copy of the distribution kit.
If the error persists, submit an
SPR to DIGITAL. Include with the SPR a description of the host system
hardware configuration, the version number of the host system you are
using, and the version number of RTEM-ll and JOAT.

4-14

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT).
?JOAT-F-Device in use dey:
The device specified with the /A option is attached
program. The device was not attached to your terminal.

another

Retype the request to attach the device, or type CTRL/C to
the RTEM-ll keyboard monitor.

return

?JOAT-F-Device not mounted dey:
A device specified with /A was not mounted
use of /A.

(with MOUNT) prior

the

Issue a MOUNT/FOREIGN command to the host system command interpreter.
?JOAT-F-Directive error code n.

*error text*

JOAT could not interpret an error received from a
operating system.

call

the

host

The system manager should take corrective action using the I/O error
codes listed in the RSX-IIM/M-PLUS I/O Drivers Reference Manual.
?JOAT-P-Directory input error dev:
A hard error occurred while the directory of the specified device
being read.
Make sure the device is on-line and write-enabled.
for bad blocks.

Check

the

was

device

?JOAT-P-Directory not found dev:[DIRECTORY]
The directory
located.

specified

the

file

Check the device name and directory
again.

specification

could

not

your

line

and

try

command

?JOAT-P-Directory output error dey:
An error occurred while JOAT was writing to the device.
Make sure the device is on-line and write-enabled.
for bad blocks.

Check

the

devjce

another

task.

?JOAT-P-Pailed to attach dey:
The device specified with the /A option is attached to
The device was not attached to your terminal.

Retype the request to attach the device, or type CTRL/C to
the RTEM-ll keyboard monitor.

return

?JOAT-P-Pailed to detach TT:
JOAT could not detach your terminal after /M was issued.
internal JOAT error or a system error.

4-15

This

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
Exit from RTEM-ll and try the operation again.
Try to invoke JOAT
using a copy of JOAT from your distribution kit. If the error
persists, submit an SPR to DIGITAL.
Include with the SPR
a
description of the host system hardware configuration, the version
number of the host system you are using, and the version number of
RTEM-ll and JOAT.
?JOAT-F-FCS error code n.

*error text*

JOAT received an error from a call to RSX-ll FCS
interpreted.

that

could

not

The system manager should take corrective action using the I/O error
codes listed in the RSX-llM/M-PLUS I/O Drivers Reference Manual.
?JOAT-F-Fetch error dev:
The copy of JOAT.SAV,
the monitor
handler may be corrupted on disk.

file,

the

specified

device

Exit from RTEM-ll using JOAT /E.
Invoke RTEM-ll again.
If the error
persists, obtain a new copy of JOAT.SAV, the specified device handler,
and resubmit the disk.
?JOAT-F-File not found dev:

SWAP.SYS

The SWAP.SYS file was not found
command line.

the

device

specified

SWAP.SYS must reside on the shared area of the virtual system device.
?JOAT-F-File not found filespec
The specified file could not be found.
Check for a typing error in the command line.

Retry the operation.

?JOAT-F-Insufficient memory
There was not enough memory space to complete the requested operation.
The system manager should increase the
system, then install RTEM-ll again.

address

space

the

host

?JOAT-F-Invalld command
An invalid command was used.
Check for a typing error and retype the command.
?JOAT-F-Invalld device dev:
The specified device is not a valid device for this operation.
The
device is not installed in the RTEM-ll monitor device tables, the
volume is not loaded in the device, the device is not a valid device
for the option used, or you specified an invalid unit number.
Check the appropriate section in this chapter for a list of valid
devices for the option you are using.
Make sure the device is
installed and the volume loaded. Valid unit numbers fall in the range
o to 7.
The device must have a corresponding host system device
handler to be accessed by JOAT.

4-16

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
?JOAT-F-Invalid directory dev:
The volume in the specified device does
directory structure.

not

contain

valid

RT-II

With a virtual device, /S can be used only on a private area. With a
foreign volume, initialize the volume before you use it with RTEM-II.
?JOAT-F-Invalid option
An invalid option or option combination was specified in
line.
Check for a typing error in the command line.
that are valid for the JOAT program.

the

command

Use only those

options

?JOAT-F-Invalid option value
A value outside the valid range was specified.
Check for a typing error in the command line. Refer to the list
valid JOAT options and the range of valid values for each option.

?JOAT-F-No LUN available
For each foreign or virtual device to be attached to RTEM-Il, one host
system logical unit number
(LUN)
is used. The /A, IV, /C, and /S
options each use one LUN to attach a device.
Use the JOAT /0 option to detach a device and free a LUN. The task is
installed with a certain number of LUNs, and RTEM-li uses five in
addition to those you might use.
?JOAT-F-No VS unit available
The virtual device could not be attached because virtual device
o through 7 are already attached to RTEM-II.

units

Use JOAT /0 to detach a virtual device and free a unit.
?JOAT-F-Output error dev:
A hard error occurred while JOAT was writing to a volume.
Make sure the device is on-line
blocks on the volume.

and

write-enabled.

Check

fo r

bad

?JOAT-F-Privilege violation
The specified file does not reside in the current directory.
cannot be opened for read or write.

The file

Copy the file to the current directory to access it.
?JOAT-F-RT-li device already attached Dev:
You attempted to attach a foreign device using the /A command, but the
RT-ll device was already attached by a previous command.
Oetach the RT-ll device using
command.

the

4-17

command.

Then

reissue

this

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
?JOAT-P-Too .any mark zone files
This error occurs when the /S/O options are used and you attempt to
insert more than 32 files into the read/write mark zone of a shared
file. No more than 32 files are allowed in the mark zone of a shared
virtual device file.
?JOAT-F-Wrong version of RTEM-II
The RTEM-ll monitor is corrupted, or you tried to run
RT-ll monitor or an outdated RTEM-Il monitor.

JOAT

under

Exit from RTEM-ll and retry the operation. Do not attempt to run JOAT
under monitors not distributed in the RTEM-ll kit.
?JOAT-I-Attached to V:VSn:
The device specified with /e, IS, or IVSn is attached
specified in this message.

the

device

This is an informational message.
?JOAT-I-dev:/Attach supersedes existing assignment;

Are you sure?

The specified virtual device unit is already attached to a file.
Detach the device or respond Y to proceed.
?JOAT-I-dev:/Detach;

Are you sure?

You must confirm your intention to detach the device.
Respond
Yes if you want to detach the specified device from RTEM-ll.

?JOAT-I-dev:[directory]filename.ext;ver/Cannot open for write Opening read-only; Are you sure?
JOAT has been unable to gain write access to the Files-II file
attached with the IV option.
If you answer Y to the prompt "Are you
sure?," you will be unable to write to the virtual device attached.
If you do not answer Y, JOAT will not attach the virtual device. You
can override this prompt by specifying the /Y option along with the /V
option.
?JOAT-I-/Exit RTEM-ll;

Are you sure?

You must confirm your intention to exit from RTEM-II.
Type a Y or Yes to exit from RTEM-II.
?JOAT-I-Foreground job loaded
If you are running a foreground job, JOAT prints this
executing the options /A, /0, and /E.

message

before

This is an informational message. Respond NO to the Are you sure?
queries printed with /A, /0 and /E if you want to unload the
foreground job before execution.

4-18

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
?JOAT-I-Bost device Dev:

attached as RT-ll device Dev:

This message is provided because some host device names and unit
numbers may require JOAT to convert the host device name into an RT-11
device name. It informs you that, after the IA command,
further
references to the device attached must be made using the RT-11 device
name given in this message. See JOAT IA for more information.
This is an informational message.
?JOAT-I-Returning to host system
?JOAT-I-Type wDCL>START taskname w or -MCR>UNSTOP taskname w to continue
After you suspend RTEM-ll with 1M,
restart RTEM-ll.

this

message

tells

you

how

You can direct terminal input to any RSX-ll task or
command
interpreter at this point. Taskname is either RTETn (where n is your
terminal number) or ••• RTE.
If your terminal is set to DCL,
type
START taskname.
If your terminal is set to MCR, type UNSTOP taskname.
?JOAT-I-Virtual device should be squeezed
dev:[directory]filename.ext;ver
The IT option to extend a virtual device has been used. This message
reminds you to use the SQUEEZE command with the virtual device, so the
RT-ll directory can be updated correctly with the new file size.
?JOAT-U-Failed to attach TT:
JOAT cannot reattach your terminal to RTEM-ll after
taskname or START taskname.
RTEM-ll exits.

you

type

UNSTOP

serious

You must invoke RTEM-ll again.

?JOAT-U-System error
An attempt was made to use a
system error has occurred.

d~vice

not in the system,

Make sure the device you want to use is loaded or installed.
Check
the directory of the system device to ensure that the necessary system
programs are intact. Exit from RTEM-11 and invoke it, retrying the
operation.
Try to invoke JOAT using a copy of JOAT from your
distribution kit.
If the error persists, submit an SPR to DIGITAL.
Include a description of the host system hardware configuration and
version number, and the version numbers of RTEM-ll and JOAT.
?JOAT-U-Unknown error code
This error is usually combined with:
?JOAT-F-FCS error code n.

*error text*

or
?JOAT-F-Directive error code n.

*error text*

If the message appears alone, it indicates an error in JOAT.
Try to
invoke JOAT again,
using your distribution kit.
If the error
persists, submit an SPR to DIGITAL.
Include a description of the host
system hardware configuration and version number, and the version
numbers of RTEM-ll and JOAT.

4-19

JACK-OF-ALL-TRADES UTILITY PROGRAM (JOAT)
?JOAT-W-Cannot open for write; opening read-only
dev:(directory]filename.ext;ver
JOAT has been unable to gain write access to the Files-II file
attached with the IV option. This message informs you that you will
be unable to write to the virtual device attached.
Specify a virtual device that may be opened for
option.

write

using

the

attach

?JOAT-W-Device not attached dey:
The specified device is not attached to RTEM-II.
Use JOAT /v to attach a virtual device.
physical device.

4-20

Use

JOAT

CHAPTER 5
FILE INTERCHANGE PROGRAM (FIP)

You can use the file interchange program (FIP) to transfer files
in
Files-II format between RTEM-ll and host operating system devices.
FIP does not support RT-Il to RT-ll file transfers or RT-ll mag tapes.
Use
the RT-il PIP.SAV program
(RT-II COpy command)
for
these
functions. The RSX-IIM/M-PLUS MCR Operations Manual lists devices
supported by RSX-ll.
The VAX/VMS Command Language User's Guide lists
devices supported by V~X/VMS.

5.1

CALLING AND TERMINATING FIP

To call FIP, type:
.R FIP
FIP prints an asterisk at the left margin of the
for you to type a command string.

terminal

and

waits

To halt FIP and return control to the RTEM-ll monitor,
type CTRL/C
when FIP is waiting for input from the console terminal. You can type
two CTRL/C commands to abort FIP at any other time.
To restart FIP,
type R FIP.

5.1.1

HELP Command

To display information about FIP command syntax, type HELP FIP when
you see the keyboard monitor prompt. Note that the RT-ll HELP.SAV
program must reside on the current RTEM-ll system device for the HELP
command to work •
• HELP FIP
FIP

Transfers files between RT-ll volumes and Files-II volumes

SYNTAX
f il espec [/opt ions] =f il espec [/opt ions] [, f il espec [/opt ions] ••• ]

5-1

FILE INTERCHANGE PROGRAM (FIP)
5.1.2

FIP Co•• and String

Chapter 3 describes the general syntax of a FIP command line.
All variations of the wildcard construction are valid for
specifications.

input

Output file specifications cannot contain embedded wildcards. If
use any wildcard character in an input file specification,
corresponding output file name or file type must be an asterisk,
the output file specification must ·contain no wildcards. In
latter case, FIP creates the output file as a concatenation of all
input files. The following example shows wildcard usage:

file
you
the
or
the
the

*.B=A%B.MAC
In this example, the embedded percent character (%) represents any
single valid file-name character. In the output file specification,
the asterisk tells the system to use files with names that are the
same as the corresponding input file.
FIP ignores all files with the file type .BAD unless you explicitly
specify both the file name and file type in the command string. No
message is printed if FIP does not include .BAD files in the transfer.
FIP transfers files between RTEM-II, which accepts up to
six
characters in a file name, and the host operating system, which
accepts up to nine characters in a file name.
When you copy a
Files-II file to RTEM-II, FIP truncates the file name to six
characters if necessary.
For example, the
host
system
file
EMPLOYEES.BAS is copied to RTEM-II as EMPLOY.BAS.
If you omit the version number, FIP always copies the highest numbered
version of the input file, or creates an output file with a version
number that increments the highest existing version number (of the
same name and type) by one.

5.2

FIP COMMAND OPTIONS

FIP command options, summarized below, let you specify how files are
copied between RTEM-II and the host operating system. You can put
command options at the end of the command string or after any file
name in the string.
Operations involving Files-II devices are an
exception; you must specify the /F option on the same side of the
command string (input or output) as the Files-II device.
Option

Function

/A[:n]

Copies all files in ASCII mode regardless of
file type.
In transfers to Files-II format,
fixed-length records of length n are generated
if you speci fy a value fo r n.
(See Sect ion
5.2.1.)

/B [: n]

Copies all files in formatted binary mode
regardless of file type.
In transfers to
Files-II
format,
if
n
is
specified,
fixed-length records of length n are generated.
(See Section 5.2.2.)
(Continued on next page)

5-2

PILE INTERCHANGE PROGRAM (PIP)

Specifies that Files-II output files will be
created as contiguous.
(See Section 5.2.3.)

Specifies that input volume, output volume, or
both are in Files-II format.
(See Section
5.2.4.)

Specifies that only files having current
as their creation date will be copied.
Section 5.2.5.}

II [ : n]

Copies all files in image mode regardless of
file type.
In transfers to Files-II for~at, if
n is specified, fixed-length records of length
n are generated.
The default value is 512
blocks.
(See Section 5.2.6.)

Specifies that a file will not be copied if a
file
of
the same name
(and version for
(See
Files-II)
exists on output
device.
Section 5.2.7.}

Copies all files except those specified.
Section 5.2.8.)

Prints file name of each file to be included in
the copy.
You must respond with a Y to copy
the file.
(See Section 5.2.9.)

Copies Files-II input files in STREAM mode
regardless of file type.
In transfers to
Files-II, output files will have the FORTRAN IV
carriage control file attribute. The FD.FTN
bit is set in the file data block of the
Files-II output file.
(See Section 5.2.10.)

Logs (displays) on the console
names
of all files copied.
5.2.11.)

terminal the
(See Section

Specifies that .SYS files may be
the copy.
(See Section 5.2.12.)

included

5.2.1

date
(See

(See

Copying in AS.CII Mode (/A[ :n])

Use the IA option to transfer all files in the 7-bit ASCII mode.
Rubouts, nulls, and vertical tabs are removed from records in the
input file.
When an RTEM-II volume is the output volume, each record
is terminated by a <CR><LF> pair.
FIP treats CTRL/Z (32 octal) as the
logical end-of-file in the input file.
In transfers to Files-II volumes, the <CR><LF> pair is removed.
If
you specify a size value (n), fixed-length records of that size are
generated, padded with nulls if required.
If you omit the size value
or if you specify it as zero, variable-length records are generated.

5-3

FILE INTERCHANGE PROGRAM (FIP)
The following example transfers all .MAC files from the RTEM-II
default storage device (logical name OK) to DR0, a Files-II volume:
*DR0: [200,200]*.*/F=*.MAC/A
The files are transferred in
records.

5.2.2

Files-II

format

with

variable

length

Copying in Binary Mode (/B[:n])

Use the /B option to add formatted binary headers and checksums to
files transferred to RTEM-II volumes, and to remove formatted binary
headers from files transferred to Files-II volumes.
In transfers to Files-II volumes, the size value
(n)
specifies that
fixed-length records of that size will be generated.
If the size
value is omitted or 0
is specified, variable-length records are
generated.
The following example transfers all
.OBJ files from
format RK05 in unit 0 to the RTEM-II volume on DXl:.

the

Files-II

*OXl:*.*=RK:*.OBJ/B/F
The /F option indicates that the input files are in Files-II format.
The /B option specifies that the files will be transferred in
formatted binary mode.
If you need to copy a binary file from RTEM-II
execution on RT-Il, copy it in image mode (/1[:n]).

Files-II

for

Do not use the /B option to copy OBJ libraries. Use the /QUERY or PIP
/Q option to selectively copy files, and type NO for each OBJ library.

5.2.3

Creating Contiguous Output Files (/C)

Use the /e option to specify that the Files-II output file will
contiguous file.

The following example transfers the data file OLDFIL.DAT from the
RTEM-ll default storage device DK:. The file is renamed NEWFILE.DAT
and copied to directory [10,20] on a Files-II volume mounted on DBI:.
*OBl: [l0,20]NEWFILE.DAT/F=OLDFIL.DAT/I/C
The Files-II output file will be a contiguous file,
as specified by
the /C option, with fixed-length records of 512 bytes. The file is
transferred in image mode as specified by the /I option, and the
record length defaults to 512 because no value was specified.
If a file is transferred with /C and ASCII mode
(explicitly or by
default), the output file may not be contiguous because the difference
in record formats precludes an exact determination of the output file
size.

5-4

FILE INTERCHANGE PROGRAM (FIP)
Specifying Files-II Transfers (IF)

5.2.4

Use the IF option to specify that the input volume(s), output volume,
or both are Files-II volumes. This option applies only to the side of
the command string (input or output) on which it appears.
The following command copies the highest numbered version of A.MAC
from directory [230,72]
to a file of the same name on the RTEM-II
default storage volume.
*A.MAC=[230,72]A.MAC/F

Copying New Files (/G)

5.2.5

The IG option copies all files with the current date as their creation
date.
Specify IG only once in the command line;
it applies to all
file specifications in the command.
The following example copies all files having the current date to
RSX-Il directory [230,50].
This is an efficient way to back up all
new files after a session at the computer.
*[230,50]*.*/F=*.*/G

5.2.6

Copying in Image Mode (/I[:n])

Use the /1 option to specify that all files will
record translations.

copied

with

In transfers to Files-II volumes, if the size value (n) is specified,
fixed-length records of that size are generated.
If no value or 0 is
specified, fixed-length records of 512 bytes are generated.
*STATUS.SAV/F=STATUS.SAV/I

Copying Without Replacing (/N)

5.2.7

Use the ~ option to prevent the transfer of a file if a file with the
same name, type, and version number exists on the output volume. The
following example uses /N to prevent replacement of an existing file:
**.SAV/F=*.SAV/N
?FIP-I-Output file not superseded [220,31]STATUS.SAV;1

*
The file STATUS.SAV is not copied to the host system directory because
a file of the same name resides there. All other files with the .SAV
file type are copied.

5.2.8

Excluding Files (/P)

The /P option copies all files except those named.
**.OBJ=*.OBJ/F/P

5-5

FILE INTERCHANGE PROGRAM (FIP)
All host files in the cur~ent directory except
extension are copied by this command.

those

with

the

.OBJ

Copying with Query (/0)

5.2.9

Use the /Q option to list all flIes and request confirmation before
copying individual files.
Type Y<RET> to copy a listed file. Type
N<RET> to prevent the file from being copied.
*[230,50]*.*/F=*.OBJ/Q
Files copied:
DK:SYSLIB.OBJ to SY: [230,50]SYSLIB.OBJ;1?
DK:VDT.OBJ to SY: [230,50]VDT.OBJ;0? Y

*
5.2.10

Copying STREAM Files, Creating FORTRAN IV Files (/T)

Use the /T option when the input Files-II file(s) are in VFC, STREAM
or PRINT FILE format.
When /T is used on a Files-II output file
specification, the output file(s) will contain FORTRAN IV carriage
control.
**.*=FORT.DAT/F/T

*
This command copies the FORTRAN
system's current directory.

5.2.11

VFC

file

FORT.DAT

from

the

host

Logging While Copying (/W)

The /W option creates a log on the console terminal of the names of
all files copied. This option is useful if you want to keep a record
of all files copied.
The following example copies all Files-II files with the fiie type
.MAC to the default RTEM-ll storage volume. The log of files copied
is printed on the terminal.
**.MAC=*.MAC/F/W
Files copied:
SY: [230,50]HIYA.MAC;1
SY: [230,50]NEWHI.MAC;2
SY: [230,50]EMPLOYEES.MAC;6

to DK:HIYA.MAC
to DK:NEWHI.MAC
to DK:EMPLOY.MAC

5-6

FILE INTERCHANGE PROGRAM (FIP)
5.2.12

Copying System Files (/Y)

Use the IY option to implicitly include system files (.SYS) in a copy
operation.
Files with the file type .SYS are not copied with an
implicit copy command unless you use the IY option.
FIP prints a
message (?FIP-W-No .SYS action) if you omit the IY option in a command
that would implicitly operate on .SYS files.
FIP copy commands that
explicitly reference system files will work without the /Y switch.

* * • *= * • * IY IF

This command copies all files from the current
including those files with the .SYS file type.

5.2.13

host

directory

Default Values

If you do not specify a copy mode option in a command line, the copy
mode options default to lA, IB, II or IT, depending on the file type
of each input file copied.
If a copy mode option is specified, all files are copied in that
regardless of file type.

mode

The following table shows the default copy mode that is used to
transfer files of specific types when the copy mode option is omitted.
Default Copy Mode

File Types

IA:0

.BAR
.BAS
.BAT
.B28
.CBL
.CMD

.COM
.COR
.DAT
.DBL
.DDF
.DIF

.DIR
.DMP
.DOC
.FOR
.FTN
.LOG

.LST
.MAC
.MAP
.ODL
.Pl\S
.RNO

18: 0

.BIN

.LDA

• OBJ

.STB

II:512

All other file types

5.3

.SLP
.SRC
.TEC
• TXT

FIP ERROR MESSAGES

?FIP-F-Channel in use
An error occurred in the FIP program.
Exit from RTEM-ll using JOAT IE.
Invoke RTEM-ll again and try the FIP
operation again, using a copy of your distribution kit.
If the error
persists, submit an SPR to DIGITAL.
Include a description of the host
system hardware configuration and software version number, and the
version numbers of RTEM-ll and FIP.

5-7

FILE INTERCHANGE PROGRAM (FIP)
?FIP-F-Channel not open
An error occurred in the FIP program.
Exit from RTEM-ll using JOAT /E.
Invoke RTEM-ll and try the FIP
operation again, using a copy of your distribution kit. If the error
persists, submit an SPR to DIGITAL. Include a description of the host
system hardware configuration and software version number, and the
version numbers of RTEM-ll and FIP.
?FIP-F-Checksum error dev:filename.typ
A checksum error occurred during
RTEM-ll.

formatted

binary

t·ransfer

from

Check for a typing error in the command line. Make sure the correct
file is being transferred.
Data may have been lost from the input
file.
?FIP-F-Device full dev:filnam.typ
The output device did not have enough room to
file, although preceding files were copied.
Squeeze the output
operation again.

device

increase

contain

storage

the

specified

space.

Try

the

host

?FIP-F-Device in use dey:
Another job is using the specified device.
Try the operation again when the other job is finished.
?FIP-F-Directive 'error code n.

*error text*

FIP could not interpret an error received from
operating system.

call

The system manager should take corrective action using the I/O error
codes listed in the RSX-IIM/M-PLUS I/O Drivers Reference Manual.
?FIP-F-Directory input error
An error occurred while the directory of the input
read.

device

was

being

Make sure the input device has a valid directory structure.
?FIP-F-FCS error code n.

*error text*

FIP received an error from a call to RSX-II
interpreted.

FCS

that

could

not

The system manager should take corrective action using the I/O error
codes listed in the RSX-IIM/M-PLUS I/O Drivers Reference Manual.
?FIP-F-Fetch error dey:
A serious system or FIP internal error occurred. The copy of FIP.SAV,
the monitor file, or the specified device handler may be corrupted on
disk.

5-8

FILE INTERCHANGE PROGRAM (rIP)
Exit from RTEM-II using JOAT /E.
Invoke RTEM-II again and retry the
operation.
If the error persists, obtain a new copy of FIP.SAV and
the device handler specified in the error message.
Retry the
operation.
If the error recurs, submit an SPR to DIGITAL.
Include a
description of the hardware configuration, the version number of your
host operating system, and the version numbers of RTEM-II and FIP.
?FIP-F-File not found dev:filename.typ
The input file specified was not found, or no input files with
expected name or type were found when a wildcard was defined.

the

Check for a typing error in the command line, verify that the file
exists as entered in the command line, and try the operation again.
?FIP-F-Insufficient memory
Memory overflow occurred, caused by too many
specifications (usually in wildcard operations) •

device

and/or

file

Try copying the files one at a time without using wildcards.
?FIP-F-Invalid command
The command line is incorrect. An option that is not compatible
the command may have been used.

with

Check for a typing error. Verify that
correct and try the operation again.

are

the

format

and

syntax

?FIP-F-Invalid device dey:
An invalid or nonexistent device was specified.
Check for a typing error in the command line.
indicated is loaded in the device drive.

Verify that the

device

?FIP-F-Invalid directory
The specified device does not contain a valid directory.
Make sure the device is a valid input or output device and contains
valid directory. Try to transfer the files again.

?FIP-F-Invalid option
An invalid option was used in the command line.
Check for a typing error in the command line.
listed as valid for FIP.
~FIP-F-Invalid

Use only those

options

use of wildcards dev:filename.typ

The output file specification contained embedded wildcards (* or %) as
in A*B.MAC and A%B.MAC.
Correct any errors in the use of wildcards.
use of wildcards.

5-9

RT-II rules apply in

the

PILE INTERCHANGE PROGRAM (PIP)
?PIP-P-Ro LUM available
In a transfer to or from a Files-II device,
(LUN) was available.

logical

unit

T.o free a LUN for the current operation, use JOAT to detach
that was previously attached with JOAT.
?PIP~P-Output

device

error dev:filnam.typ

An unrecoverable error occurred while FIP was transferring a file.
Check the procedures for recovery from hard
described in the RT-ll System Message Manual.

number

error

conditions

There was not enough room on the device to transfer the specified
file.
In a multiple file operation, execution was successful on
files preceding the one interrupted by the error.
In a transfer to RTEM-ll, squeeze the device. In a transfer to
the host operating system, delete files to create more storage
space.

?FIP-P-Output file full dev:filnam.typ
The output file was too small to receive the input file.
Make sure there is enough space on the output device
file.
Try to transfer the file again.

receive

the

?FIP-P-Protected file already exists
FIP tried to create an RTEM-II output file with a name already
associated with an existing protected file.
No new file is created.
Use the monitor RENAME/NOPROTECT command or the PIP /Z option to
change the protection status of the existing file, or use a different
name to create the new file.
?PIP-P-System error
An attempt was made to use a device not on the system,
error occurred.

serious

Make sure the device you want to use is loaded. Check the directory
of the relevant device to ensure that the necessary system programs
are intact. Exit from RTEM-ll, invoke it again, and try the operation
again.
?FIP-P-Too many output files
More than one output file was specified in the command line.
Limit the number of output files on the command line to one.
?FIP-P-Wrong version of RTEM-ll
The RTEM-li monitor is corrupted, or an attempt was made
under an RT-ll monitor or an outdated RTEM-ll monitor.

5-10

run

FIP

FILE INTERCHANGE PROGRAM (FIP)
Exit from RTEM-II, invoke it again, and try the operation again.
Do
not attempt to run FIP under monitors not distributed in the RTEM-li
kit.
?FIP-I-Output file not superseded dev:filename.typ
A file of the same name as specified resides on the output vol~e.
FIP /N was used to prevent copying files of the same name (and version
for Files-II output).
This is an informational message.
?FIP-W-File created:

protected file already exists dev:filnam.typ

A protected RTEM-ll file exists along with a newly created unprotected
file of the same name.
List the directory, unsorted.
If the unprotected file appears before
the protected file in the directory listing, delete or rename it.
If
the protected file appears first, rename it or change the protection
code with the PIP /Z option or the monitor RENAME/NOPROTECT command.
?FIP-W-Library file not copied dev:filnam.typ
An OBJ library is an input file in a FIP /8 transfer command.
The
file name is shown in the message. The transfer is not completed.
Do not use the /8 option to copy OBJ libraries. Use the /QUERY or PIP
/Q option to selectively copy files, and type NO for each OBJ library.
?FIP-W-No .SYS action
The /Y option was not included in a command aimed at implicitly
copying files of type .SYS.
A wildcard transfer will most likely
cause this message. The command is executed for all files but those
of the .SYS file type.
Use /Y to implicitly copy files of type .SYS.

5-11

CHAPTER 6
MODIFYING THE VIRTUAL SYSTEM DEVICE

This chapter tells host system managers how to add and delete files in
the shared area of the virtual system device.
You can modify the virtual system device to include RT-ll utility
programs and any other files RTEM-ll users may want to share. You can
select specific files to copy from your RT-ll distribution kit to the
shared area or create a shared area from the entire volume.
The directory for the shared area of the virtual system device is
expandable to accommodate additional system programs. This chapter
shows how to make additional utilities, libraries, and data files
available to all RTEM-ll users by copying new files to the shared area
and extending it if necessary.
To reserve space for future expansion in the shared area of the
virtual system device,
the directory contains directory fillers.
Directory fillers are unique to RTEM-ll and are removed to convert a
shared area to a private area. The basic difference between a shared
and private area is the presence of directory fillers in the former.
For an overview of the virtual system device, see Section 2.2.
Section 6.1 summarizes the procedure for modifying the shared area of
the virtual system device.
Section 6.2 provides an example that
illustrates this procedure.

6.1

MODIFICATION PROCEDURE

This section summarizes the steps required to create a shared area or
to add, delete, or modify files that reside in an existing shared area
of the virtual system device.
To create or modify a shared area, work from a privileged account but
not from the account in which the shared file will reside. The
default location for the shared file
is LB:[l,l]RTllSH.DSK on an
RSX-ll system or SYS$LIBRARY:RTllSH.DSK on a VAX/VMS system.

6.1.1

Establish Shared Area as a Temporary File

First, copy the shared area to a temporary file.
You can modify this
copy while the original shared area serves as part of the virtual
system device.
$ COpy LB:[l,l]RTllSH.DSK output-filename.TMP

6-1

MODIFYING THE VIRTUAL SYSTEM DEVICE
Invoke RTEM-ll from the default virtual system device.
$ RTEM/vs

Use JOAT Iv to attach the temporary file as a virtual device.
To
the device, you must use IT:n at this time. The value (n)
specifies the number of blocks (in octal) by which the file will be
extended. This value should include the number of blocks in the files
you will add to the shared area. If you do not plan to add files, you
can omit IT:n. There is no default value.

~xtend

*filename.TMP/V:VSn/T:n

6.1.2

Update and Compress the Virtual Device (JOAT IU)

The IU option converts a shared area into a private area. Thereafter,
you can modify the device.
By removing directory fillers, Iu
transforms a shared area into a private one.
Files may be added,
deleted, moved or modified after the IU option is used. You can
combine IU with Iv and IT in the previous step or use IU separately.
Either way, specify the shared area with the virtual device name and
unit to which it was previously attached.
1\VSn: IU
You must compress the volume (with SQUEEZE)
INITIALIZE) after using the IU option •

initialize

(with

•SQUEEZ E VSn:

6.1.3

Add, Delete, or Modify Files on the Virtual Device

Perform all modifications to files that reside in the former shared
area.
At this time, you may copy files to the shared area from your
RT-ll distribution kit or working volume. You may also delete old
files from the shared area to be replaced with updated ones. Access
the former shared area as the virtual device (VSn:) to which it was
attached with the JOAT IV option.
If you need to delete, modify, or replace a file from the former
shared area, you must first disable the file's protected status •
•UNPROTECT VSn:filespec
.DELETE VSn:filespec

6.1.4

Create a New Shared Area (JOAT IS)

The IS option creates a shared area from an existing virtual device or
RT-ll foreign volume.
After using IU to convert a shared area to a
private area, use IS to return it to a shared area.

6-2

MODIFYING THE VIRTUAL SYSTEM DEVICE
When you use /S to create a shared area, the position of files in the
shared area is established. All files are moved to the read-only area
leaving SWAP.SYS, BAM.SYS, IND.SAV, and all RTEM-ll device handlers
including SET options
(respectively) in the mark zone. You can use
the /0 option to order the files differently. Read about /0
(Section
6.1.5) before you use IS.
*output-filespec=input-device:/S
specify the input device as the virtual device to which the shared
area was attached with the JOAT /V option.
If you did not update an
existing shared area but are creating a shared area from a foreign
volume, specify the foreign volume with an RTEM-ll device mnemonic.
If you intend to use the new shared area as a virtual system device,
certain files must reside on it. The files are RTEMFB.SYS, VSM.SYS,
and SWAP. SYS.
Use a host system file specification for the output file name.
If you
omit the file type, .SYS is assumed. The size of the output file is
the total number of blocks in use on the input device.
The /S option automatically attaches the shared area as the first free
virtual device unit. Automatic unit assignment cannot be overridden.
JOAT displays the message:
?JOAT-I-Attached to VSn
This message tells you which virtual device unit was assigned.

6.1.5

Establish the Order of Files in Shared Area (JOAT /O(:XXX])

You can use the /0 option with /S to establish the order of
the shared area of a virtual system device.

files

When you use /S to convert a private area to a shared area, the
position of files on the volume is established. All files are moved
to the read-only area leaving SWAP.SYS, BAM.SYS, IND.SAV, and all
RTEM-Il device handlers including SET options (respectively) in the
mark zone. Use /0 with /S to transfer files from the read-only area
to the mark zone.
*output-filespec=input-device:/S/O(:xxx]
The values for xxx are ADD, NEW, SAY, and UPD.
ADD causes files that reside in the mark zone
(all blocks following
SWAP.SYS)
to remain unchanged, and prompts for additional files to be
copied to this area. When you see the prompt File?, type the names of
files you want to move from the read-only area of the volume to the
mark zone. The files you specify must reside on the input device.
The ADD option is the operational equivalent of the SAY and NEW
options. Files added to the volume are positioned in the order in
which they are specified.
NEW is the default for /0. This option adds files you specify to the
mark zone. The files are added after SWAP.SYS, BAM.SYS, IND.SAV, and
all RTEM-ll device handlers including SET options.
The NEW option
prompts File?
Type the names of the files you want to move from the
read-only area to the mark zone.
Files added to the volume are
positioned in the order in which they are specified.

6-3

MODIFYING THE VIRTUAL SYSTEM DEVICE
SAV causes the position of files
SWAP.SYS to remain unchanged.

that

reside

blocks

following

UPD lists every file in the mark zone following the SWAP.SYS file and
prompts Include file filnam.typ? for each file. Type Y[ES] followed
by a carriage return if you want the specified file to remain in the
mark zone.
Type N[O] followed by a carriage return if you want the
file to be moved to the read-only area. NO is the default. After all
files in the mark zone have been listed, the prompt File? is
displayed. Type the names of files you want to move from the
read-only area of the volume to the mark zone. Files added to the
volume are added in the order in which they are specified.

6.1.6

Maintain the Host System

After you have performed all modifications to the shared area, exit
from RTEM-11.
Then copy the modified shared area to the library
account
(copy
it
to
LB:[1,1]RTIISH.DSK
on
RSX-II
or
SYS$LIBRARY:RT1ISH.DSK on VAX/VMS).
Protect the new shared area so
all RTEM-II users may access it. Delete all temporary files created
during the modification process, test the new shared file, and then
purge previous versions of the shared file from the library account.
(See items [9] through [13] of Section 6.2.)

6.2

SAMPLE MODIFICATION

This section contains a sample modification procedure.
The example
shows how to copy files to the shared area from both an RT-II format
foreign volume (an RK05, unit 0) and from a file
(RTIIV5.DSK).
The
numbered steps are explained in the text following the example.
If you are copying from a foreign volume, place your volume in the
device and issue the ALLOCATE and MOUNT /FOREIGN commands before you
invoke RTEM-11.
Procedure
[1]

$ COpy LB: [1 ,1]RT1ISH.DSK RTlISH.TMP

[2]

$ RTEM/VS
?RTEM-I-Creating default private file DMI: [l,224]RTIIPR.OSK;0
RTEM-II (host type) V02.nn
RTIIFB V05.xx
?KMON-F-File not found DK:STARTM.COM

[3]

.R JOAT
*RTlISH.TMP/V:VS1/T:2000./U
?JOAT-I-Virtual device should be squeezed OMl: [1,224]RTIlSH.TMPil

6-4

MODIFYING THE VIRTUAL SYSTEM DEVICE
(4]

*DK0: /A/W
or
*RTllV5/V:VS2/W
*"'C

(5]

.SQUEEZE/NOQUERY VS1:

(6]

.RENAME/NOPROTECT VS1:DEMOX1.OBJ VS1:*.*
.DELETE VS1:DEMOXl.OBJ

(7]

.COPY RK0:QUEMAN.SAV VS1:

.COPY RK0:RESORC.SAV VS1:
or
.COPY VS2:QUEMAN.SAV VS1:

.COPY VS2:RESORC.SAV VS1:
(8]

• R JOAT
*RTllSH=VS1:/S
?JOAT-I-Attached to VS3:

[9]

* /E/Y

[10] $ COpy RT11SH.DSK LB: [1,1]RT11SH.DSK
[11]

VAX/VMS:
$ SET PROTECTION=(GROUP:R,WORLD:R) LB:[1,1]RTl1SH.DSK

RSX-11:
>SET PROTECTION LB: [1,1]RT11SH.DSK (GROUP:R,WORLD:R)
[12] $ DELETE RTl1SH.TMP;0,RT11SH.DSK;0
[13] $ PURGE LB:[1,1]RT11SH.DSK
Explanation
[1]

Copy the shared
(RTllSH.TMP) •

area

[21

Invoke RTEM-11 from the default virtual system device.

[3]

Attach the temporary file as a virtual device with JOAT /V:VSn.
At the same time, extend the file by 2000 (decimal) blocks.
Also, use /U to convert the shared area to a private area to
allow for modification.

6-5

modified

temporary

file

MODIPYING THE VIRTUAL SYSTEM DEVICE
[4]

Attach the volume on which the files to be copied
volume is either DK0:
or VS2:.

[5]

Squeeze the virtual device attached in
extended space specified with /T:n.

[6]

If you need to delete, modify, or replace files from the former
shared area, you must first unprotect the file or the operation
will fail.

[7]

Modify the virtual device squeezed in step 5 with
or VS2:.

[8]

Create a new shared area from the modified virtual device.

[9]

Exit from RTEM-ll.

step

reside.
to

reflect

fil~s

This
the

from RK0:

[10] Copy the new shared area to the library account.
[11] Protect the new shared area so all RTEM-ll users may access it.
[12] Delete all temporary files.
[13] Purge the library account.

6-6

GLOSSARY

Command line interpreter
See DCL and MCR.
Compatibility mode
Provided by VAX!VMS to enable
programs.

development

and

execution

RSX-II

Control characters
Typed at the terminal to control terminal hardware and program
execution;
combine the CTRL key and another key. Referred to as
special function keys in RT-II terminology.
DCL
DIGITAL command language; provides a means of communication between
the user and the operating system. DCL is easier to use than MCR
because the commands are English words and you are prompted for the
information required to complete the command.
Despooling
Passing output to a low-speed peripheral, such as a line printer, from
a queue maintained on a volume.
Compare with Spooling.
Device driver
See Device handler.
Device handler
Software that handles physical input and output to a device.
Each
device included in the system has a device handler. Device handlers
(used in RT-II) are referred to as device drivers in RSX-II or
VAX/VMS.
RTEM-II device handlers don't handle physical I/O. They
convert RTEM-II I/O requests into equivalent host operating system QIO
requests.
The host system drivers then issue the QIO requests to the
appropriate host system device.
Directory filler
A special entry for reserving space in the
RTEM-II virtual system device's directory.

shared

portion

the

Directory-structured devices
File-structured devices that have a series of directory segments at
the beginning of the device. The device directory begins at block 6.
File-structured devices store information in files under assigned
names.
Executive
The RSX-II system program that directs program execution and maintains
the integrity of the entire operating system. The executive monitors
and coordinates all activities in the system including real-time and
multiprogramming task execution, user communication, supervision of
input and output (I/O), and resource allocation.
File
An owner-named area on a volume.

Glossary-l

Files-II
The on-disk structure used by RSX-II and VAX!VMS.
Foreign volume
An RSX-II or VAX/VMS volume that is not in Files-II
example, an RT-II directory-structured volume.
Host system
The system on which a program executes.
VAX/VMS are host systems for RTEM-II.

RSX-IIM,

format;

RSX-IIM-PLUS,

for

and

Implicit prompt
On an RSX-II system, indicates that a program is ready to accept a
command. The right angle bracket (»
is the implicit prompt displayed
by the command line interpreter. Type a carriage return to display
the implicit prompt or a CTRL/C to display the explicit prompt. The
explicit prompt indicates which system program is currently waiting
for
input.
For example, the explicit prompt MCR> indicates that MCR
is waiting for input.
Installation
The site at which software and hardware components combine to form a
computer system.
Also,
the process of installing software and
hardware.
Job
An RT-II executable program.

Compare with Process and Task.

Logical name
A user-specified name for any portion or all of a file specification.
Mapped system
A system with memory management hardware that intercepts a 16-bit
virtual address generated by the processor and converts it to an
18-bit physical address.
This process
associating a virtual
address with a physical address -- is called mapping. RTEM-II runs on
mapped systems only.
Mark zone
A section of the shared area of the virtual system device.
Files that
reside in the mark zone are read/write.
Files in the remainder of the
shared area are read-only.

MeR
Monitor console routine; on an RSX-II system,
provides a means of
communication between the user and the system utilities and installed
tasks.
Most MCR commands use initials or abbreviations in strict
syntax, rather than English words as in DCL.
Node
A computer system connected to other systems by hardware and software
to form a computer network. A computer network consists of multiple
nodes.
Option
An element of a command or command string that lets the user select
from among several alternatives associated with the command.
In
RT-II, an option consists of a slash character
(/)
followed by the
option name and, if necessary, a colon (:) and value. The RT-II term
option is equivalent to the RSX-IIM/M-PLUS term switch.

Glossary-2

Password
A protective keyword required in a log-in sequence to gain access to
the operating system.
The password is not displayed on the terminal
when you type it.
Private area

A part of the virtual system device that holds user files.
Process
On a VAX/VMS system, the basic entity scheduled by system software for
execution.
A process consists of an address space and both hardware
and software contexts. Compare with Job and Task.
RTEM-ll
The set of programs that provide the RT-II
environment under RSX-IIM/M-PLUS and VAX/VMS.

program

development

Shared area
A section of the virtual system device that holds files shared
RTEM-II users. The shared area is read-only. See Mark Zone.
Spooling
Receiving input in a queue on a volume
peripheral.
Compare with Despooling.

for

output

System prompt
Indicates the system is ready for you to enter a command.
prompts are:
RTEM-II:
RT-II:
RSX-IIM/M-PLUS:
VAX/VMS:

low-speed

The

system

a pe r i od (.)
a per iod (.)
the letters MCR) or DCL> or an angle bracket (»
a dollar sign ($)

Task
The fundamental executable unit of an RSX-II program.
The term
in RSX-IIM/M-PLUS is equivalent to the term "job" in RT-II.

task

Task builder
An RSX-IIM/M-PLUS utility program.
Once a task
is assembled or
compiled
into an object format, it is built into a task image by the
task builder (TKB). The linker (LINK) is the RT-II equivalent of the
task builder.

Ule
User identification code;
an account number that identifies an
authorized system user.
The UIC consists of a group number and a
member number separated by a comma.
Virtual device
A Files-II file that appears to be a volume to RTEM-II.
The volume
has a home block and directory segments defining its dimensions. The
virtual system device is a pair of Files-II files that are treated as
a single system volume by RTEM-II.
The Files-II files that make up a
virtual system device can be copied using
the host system copy
command, but the RTEM-II files within this device can be accessed only
through RTEM-ll.

Glossary-3

Virtual machine
The environment provided by RTEM-ll. With the exception of the I/O
page, a user program running under RTEM-ll appears to be running on a
stand-alone PDP-II with RT-II.

Volume
The largest logical unit of the file structure. The term volume is
often used as a synonym for the term device because you specify a
device name to access a volume. However, the device name you supply
in a file specification is the name of the device on which the volume
resides.
In RT-Il, a volume is a physical medium, such as a diskette or
magtape, that you load into a device drive. A device or device drive
is the unit that holds the volume and is attached to the peripheral
housing.

Glossary-4

INDEX

/A option
FIP utility, 5-3
JOAT utility, 4-3
/AB, RTEM-ll start-up command
option, 2-9
ABORT command
RSX-ll, 2-7
ADD option, 4-3
ALLOCATE command
RSX-ll, 1-4
VAX!VMS, 1-10, 1-11
Attach a physical device, 4-3
Attach a virtual device, 4-12

RTEM-l1, 1-7
summary, 2-4
VAX/VMS,· 1-12
CTRL/Y
VAX/VMS, 1-12
CTRL/Z
RSX-ll, 1-7
RTEM-l1, 2-3
VAX!VMS, 2-5

/0 option

/B option
FIP utility, 5-4
.BAD files, 5-2
Bootstrap
RTEM-ll# 2-25
Bootstrap,RTEM-ll, 2-2
/C option
FIP utility, 5-4
JOAT utility, 4-4, 4-6
Change line printer spool device,
2-10
Copy in ASCII mode, 5-3
Copy in binary mode, 5-4
Copy in image mode, 5-5
Copy new files, 5-5
Copy stream files, 5-6
Copy system files, 5-7
Copy with query, 5-6
Copy without replacing, 5-5
COPY/BOOT command
RT-11, 2-25
RTEM-11, 2-25
COPY/DEVICE command
RTEM-11, 2-26, 4-3, 4-12
Create a shared area, 4-11
Create a virtual device, 4-4
Create contiguous output files,
5-4
Create FORTRAN IV files, 5-6
Create temporary virtual device,
4-13
CTRL/C
FIP utility, 5-1
JOAT utility, 4-1
RSX-11 logging in, 1-2
RT-11, 1-12

JOAT utility, 4-5
DATE command
RTEM-l1 restrictions, 2-25
DCL (DIGITAL command language) ,
1-2
DEALLOCATE command
RSX-ll, 1-5
VAX/VMS, 1-11
Despool ing, 6-7
Detach a device, 4-5
Device definition
RSX-l1, 1-7
RTEM-l1, 1-7
VAX/VMS, 1-12
Device driver
RSX-l1, 1-6
VAX!VMS, 1-12
Device name
name changing conventions, 2-23
RSX-11, 1-4
RT-11, 1-12
VAX/VMS, 1-12
Device usage
RSX-ll, 1-4
VAX/VMS, 1-10
DIRECTORY command
RSX-l1, 1-3
VAX/VMS, 1-9
DIRECTORY/FREE command, 4-11
DIRECTORY/SUMMARY command
RT-11, 2-11
DISMOUNT command
RSX-ll, 1-5
VAX/VMS, 1-10
Display version identifier, 2-10
Documentation references
RSX-l1, 1-7
VAX/VMS, 1-13

Index-l

INDEX

ECSI (extended command string
i nte rpr ete r)
call ing, 3-1
comparison with CSI, 3-1
definition, 3-1
required for JOAT and FIP, 3-1
syntax, 3-1
/EX, RTEM-ll start-up command
option, 2-9
Exclude files, 5-5
Exiting RTEM-ll, 4-6
Extend a virtual device, 4-11
Extend private area, 2-9
/F option
FIP utility, 5-5
File management
RSX-ll, 1-3
VAX/VMS, 1-8
File specification
RSX-ll, 1-4
VAX/VMS, 1-9
Files-II directory structure
RSX-ll, 1-6
VAX/VMS, 1-11
FIP utility
call and terminate, 5-1
command options, 5-2 to 5-7
copy in ASCII mode, 5-3
copy in binary mode, 5-4
copy in image mode, 5-5
copy new files, 5-5
copy stream files, 5-6
copy system files, 5-7
copy without query, 5-6
copy without replace, 5-5
create contiguous output
files, 5-4
create FORTRAN IV files, 5-6
exclude files, 5-5
log while copying, 5-6
specify files-ll transfers,
5-5
command string, 5-2
default values, 5-7
definition, 5-1
error messages, 5-7 to 5-11
HELP command, 5-1
wildcard usage, 5-2
/FOREIGN option
RSX-ll, 1-5
VAX!VMS,1-10
Foreign volume system device, 2-2
/G option
FIP utility, 5-5
Glossary, G-l to G-4

/HE, RTEM-ll start-up command
option, 2-10
HELP command
FIP utility, 5-1
JOAT utility, 4-2
RSX-ll, 1-5
VAX!VMS, 1-11

/10, RTEM-ll start-up command
option, 2-10
INITIALIZE command
RSX-ll, 1-6
RTEM-ll, 4-5
VAX!VMS, 1-11
Invoke RTEM-ll from default
virtual system device, 2-15
JOAT utility
call and terminate, 4-1
command options, 4-2 to 4-14
attach physical device, 4-3
attach virtual device, 4-12
create shared area, 4-11
create temporary virtual
device, 4-13
create virtual device, 4-4
definition, 4-2
detach device, 4-5
exit RTEM-ll, 4-6
extend virtual device, 4-11
list device usage, 4-7
order files on virtual system
device, 4-9
pass commands to RSX-ll, 4-8
suppress query message, 4-13
table, 4-2
update virtual device, 4-12
write-protect volume, 4-13
command string specification,
4-1
definition, 4-1
error messages, 4-14 to 4-20
HELP command, 4-2
Keyboard monitor
commands,unsupported, 2-27

/L option
JOAT utility, 4-7
Line printer support, 2-23
List RTEM-ll device usage, 4-7
Log while copying, 5-6

Index-2

INDEX

Logging in
RSX-ll, 1-2
VAX/VMS, 1-8
Logg ing off
RSX-ll, 1-2
VAX!VMS, 1-8
LOGOUT command
RSX-ll, 1-3
LP, line printer handler, 2-23
/LP, RTEM-ll start-up command
option, 2-10
LS, line printer handler, 2-23

/Q option
FIP utility, 5-6

/M option
JOAT utility, 4-8
Make system device read-only,
2-12
Ma rk zone, 2-2
Modify virtual system device
add,delete,modify files, 6-2
create new shared area, 6-2
establish order of files in
shared area, 6-3
establish shared area as
temporary file, 6-1
explanation, 6-1
maintain host system, 6-4
procedure, 6-1
sample modification, 6-4
explanation, 6-5
procedure, 6-4
update and compress, 6-2
MOUNT command
RSX-ll, 1-5
VAX/VMS, 1-10
MOUNT/FOREIGN command
RT-ll, 2-13
/N option
FIP utility, 5-5
NEW option, 4-3

/0 option
JOAT utility, 4-9
ODT (on-line debugging technique)
see VDT
Ordering files on virtual system
device, 4-9

/p option
FIP utility, 5-5
Pass commands to RSX-ll, 4-8
/PR, RTEM-ll start-up command
option, 2-10
Private area, 2-2, 2-6, 2-9, 2-10

/RO, RTEM-ll start-up command
option, 2-12
RP02/RP03 device support on
RSX-ll, 2.24
RSX-ll
Conventions, 1-2
device names, 1-7
Device usage, 1-4
Documentation references, 1-7
file management, 1-3
File specification, 1-4
Files-II directory structure,
1-6
Logg ing in, 1-2
Logging off, 1-2
MCR (monitor console routine)
prompt, 1-2
special function keys, 2-3
TASK, 1-6
/RT, RTEM-ll start-up command
option, 2-13
RT-ll
special function keys, 2-3
RTEM-l1
command-line error messages,
2-31 to 2-43
device handlers, 1-12
device names, 1-7
differences, 2-23
Directory structure, 1-6
ex i t ing
nonprivileged, 2-7
pr iv ileged, 2-7
Features, 1-1
FIP utility
See FIP utility
foreign device support, 2-16
table, 2-17 to 2-18
JOAT utility
see JOAT utility
JOB, 1-6
line printer support, 2-23
Monitor definition, 2-1
prompt characters, 2-3
restrictions
BATCH program, 2-26
COPY/BOOT command, 2-25
COPY/DEVICE command, 2-26
DATE command, 2-25
keyboard monitor
commands,unsupported,
2-27

Index-3

INDEX

nonsupport of ODT, 2-26
programmed
requests,unsupported,
2-29
RT-ll devices, unsupported,
2-30
SQUEEZE command, 2-26
summary, 2-26
TIME command, 2-25
unsupported control
characters, 2-3"
utility programs,unsupported,
2-28
RP02/RP03 device support on
RSX-11, 2-24
SET options for devices
table, 2-18 to 2-22
special function keys, 2-3
start-up command options, 2-8
to 2-16
start-up procedure
foreign volume system device,
2-6
virtual system device, 2-6
system device, 2-1
foreign volume system device,
2-2
virtual system device, 2-2
wildcard usage, 3-3
RTEMFB.SYS file, 2-6, 2-13
RUN command
RSX-ll, 2-6
VAX/VMS, 2-6

/S option
JOAT utility, 4-11
SAV option, 4-3
ISH, RTEM-l1 start-up command
option, 2-15
Shared area, 2-2
SHOW DEFAULT command
VAX/VMS, 1-8
SHOW DEFAULTS command
RSX-11, 1-3
Special function keys, 2-3
Specify abort character code, 2-9
Specify files-ll transfers, 5-5
Specify foreign volume system
d ev i ce, 2 -1 3
Specify private area of virtual
system device, 2-1~
Specify the shared area, 2-15
Spool device, 2-10
Spool ing, 2-23

SQUEEZE command
RTEM-ll restrictions, 2-26
Start-up command options, 2-8 to
2-16
change line printer spool
device, 2-10
display HELP text, 2-10
display version identifier,
2-10
extend private area, 2-9
invoke RTEM-11 from default
virtual system device, 2-15
make system device read-only,
2-12
specify abort character code,
2-9
specify foreign system device,
2-13
specify foreign volume system
device
.
explanation, 2-14
procedure, 2-13
specify private area of virtual
system device, 2-10
specify shared area, 2-15
STOP command
VAX!VMS, 2-7
Suppress query message, 4-13
/T option
FIP utility, 5-5, 5-6
JOAT utility, 4-11
TIME command
RTEM-ll restrictions, 2-25
/U option
JOAT utility, 4-12
UIC (user identification code),
2-24
UNSTOP command
RSX-11, 4-8
UPD option, 4-3, 4-9
Update a virtual device, 4-12
/V option
JOAT utility, 4-12
VAX!VMS
conventions, 1-8
device definition, 1-12
device driver, 1-12
device usage, 1-10
documentation references, 1-13
file management, 1-8
file specification, 1-9
files-II directory structure,
1-11

Index-4

INDEX

10gg ing in, 1-8
logging off, 1-8
process, 1-11
special considerations, 1-11
special function keys, 2-3
VDT (virtual debugging technique),
2-26
Virtual system device, 2-2
/VS, RTEM-11 start-up command
option, 2-15

/W option
FIP utility, 5-6
JOAT utility, 4-13
Write-enabling a volume, 4-13
Write-protecting a volume, 4-13
/Y option

FIP utility, 5-7
JOAT utility, 4-13
/Z option
JOAT utility, 4-13

Index-5

HOW TO ORDER
ADDITIONAL DOCUMENTATION
From

Call

Write

Chicago

312-640-5612

Digital Equipment Corporation
Accessories & Supplies Center
1050 East Remington Road
Schaumburg, IL 60195

8:15 A.M. to 5:00 P.M. CT

San Francisco

408-734-4915
8:15 A.M. to 5:00 P.M. PT

Alaska, Hawaii

603-884-6660
8:30 A.M. to 6:00 P.M. ET

Digital Equipment Corporation
Accessories & Supplies Center
632 Caribbean Drive
Sunnyvale, CA 94086

or 408-734-4915
8:15 A.M. to 5:00 P.M. PT

New Hampshire

603-884-6660
8:30 A.M. to 6:00 P.M. ET

Rest of U.S.A.,
Puerto Rico*

1-800-258-1710
8:30 A.M. to 6:00 P.M. ET

Digital Equipment Corporation
Accessories & Supplies Center
P.O. Box CS2008
Nashua, NH 03061

·Prepaid orders from Puerto Rico must be placed with the local DIGITAL subsidiary (call 809-754-7575)

Canada
British Columbia

1-800-267-6146
8:00 A.M. to 5:00 P.M. ET

Ottawa-Hull

613-234-7726
8:00 A.M. to 5:00 P.M. ET

Elsewhere

Digital Equipment of Canada Ltd
940 Belfast Road
Ottawa, Ontario K1G 4C2
Attn: A&SG Business Manager

112--800-267-6146
8:00 A.M. to 5:00 P.M. ET

Elsewhere

Digital Equipment Corporation
A&SG Business Manager·
·c/o DIGITAL's local subsidiary or approved distributor