Digital PDFs

AA-CJ39B-TE

August 1985

52 pages

Original

23MB

view download

OCR Version

19MB

view download

Document:	VAX-11 RSX Installation Guide and Release Notes Version 2.0
Order Number:	AA-CJ39B-TE
Revision:	0
Pages:	52
Original Filename:

OCR Text

Installation Guide
and Release Notes
Order Number: AA—-CJ39B-TE

V2.0

August 1985

Revision/Update Information:

This is a revised manual.

Operating System and Version:

VAX/VMS Version 4.2

Software Version:

VAX-11 RSX Version 2.0

digital equipment corporation
maynard, massachusetts

MicroVMS 4.2

First Printing, September 1984
Revised, August 1985

The information in this document is subject to
not be construed as a commitment by Digital

change without notice and should

Equipment Corporation. Digital

Equipment Corporation assumes no responsibility

in this document.

for any errors that may appear

The software described in this document is furnish

ed 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 reliabili
ty of software on equipment
that is not supplied by Digital Equipment Corpora
tion or its affiliated companies.

The postpaid READER'S COMMENTS form on the

requests the user’s critical evaluation to assist

The following are trademarks of Digital Equipment
DEC

DEC/CMS

DEC/MMS
DECnet

DECsystem—-10
DECSYSTEM-20
DECUS

DECwriter

DIBOL

EduSystem

IAS
MASSBUS

PDP

last page of this document

in preparing future documentation.

Corporation:

UNIBUS
VAX

VAXcluster
VMS

PDT
RSTS

RSX

di gQ

N
ZK-2906

This document was prepared using an in-house document

ation production system. All

page composition and make-up was performe
d by TgX, the typesetting system developed

by Donald E. Knuth at Stanford University. TgX is a
registered trademark of the American

Mathematical Society.

Contents
vii

PREFACE

VAX-11 RSX INSTALLATION GUIDE

1-1

1.1

INTRODUCTION

1.2

IDENTIFYING THE VAX-11 RSX KIT

1-1

1.3

GETTING STARTED

1-2

1.4

INSTALLING VAX—11 RSX

1.5

AFTER INSTALLATION

1-8

1.6

A SAMPLE VAX-11 RSX INSTALLATION

1-9

2.1

MESSAGE FORMAT

2-1

2.2

MESSAGE SUMMARY

2-2

3ECTION 2

VAX-11 RSX VERSION 2.0 RELEASE NOTES
3-1

3.1

3.1.1

VAX-11 RSX PDP-11 Instruction Set Emulator

3.1.2

Changes to MCR

3.1.2.1

3.1.2.2

3.1.3

New Commands * 3-1

3-1

”

New or Revised Keywords and Parameters ® 3-2

Changes to DCL
3.1.3.1
Enhancement to the DCL Command MCR ¢ 3-2
3.1.3.2
New LINK/RSX11 Qualifiers ® 3-2

3-2

Contents

3.2

3.1.4

Changes to the Indirect Command Processor (Indirect)
3.1.4.1
New Directives ¢ 3-3
|
3.1.4.2
New Symbol ¢ 3-3

3-3

3.1.5

Support for New VAX-11 RSX Executive Directives

3-4

ENHANCEMENTS TO EXISTING VAX-11 RSX FEATURES
3.2.1
Support for SYSCOMMON System Disks
Performance Enhancements to the ALUNS and ELP$

3.2.3

$$N Translation Caching

3.2.4

Terminal Driver Enhancements

3.2.5

Reactivating RSX—11 Images

3-7

3.2.6

Reporting CRF Subprocess Errors

3.2.7

3-7

EXSTS Directive Behavior Change

3.2.8

DECnet—-11M and DECnet—11M-PLUS NETGEN

3-8

Directives

3-6
3-6
3-7

Support

3-8

Changes to the Indirect .TESTPARTITION and

GPRTS$ Directives

3-8

3.2.10

Enhancements to VAX—11 RSX Error Messages
3.2.10.1
New Error Message * 3-9

3.2.11

BOMS Directive Error Messages

3.2.12

3-9

Named Directory Support

3-9

VAX-11 RSX SOFTWARE RESTRICTIONS

3-9

3.3.1

Defining SYSSLOGIN

3.3.2

Differences Between VAX—11 RSX Memory
Management Directives and RSX—-11 Memory
Management Directives
3.3.2.1
Region Creation ® 3-10
3.3.2.2
Region Deletion ® 3-10
3.3.2.3
Region Attachment e 3-11
3.3.2.4
Displaying Region Information * 3-11
3.3.2.5
Region Checkpointing ® 3-11

3.3.2.6

3.3.2.7

3.3.2.8

3-6
3-6

3.2.2

3.2.9

3.3

___

3-8

3-10

Memory Management Granularity ® 3-12
Compatibility Between VAX-11 RSX Memory
Management and RSX—11 Memory Management ® 3-12
VAX-11 RSX Memory Management Privilege
Requirements » 3-12

3.3.3

Removal of Restrictions to Installing Compatibility Mode
Tasks

3.3.4

3-13

EXTKS Directive Behavior Change

3.3.5

Changes Required to User-Created RSXUSR.EXE
Images

3-13

3.3.6

Restrictions on Passing Device Names to Other Tasks

3.3.7

3-15

Restrictions for Indirect Using MCR on VAX-11 RSX
3.3.7.1
Logical Name Handling ® 3-16
3.3.7.2
Process Context ® 3-16

3-16

3.3.8

Differences Between VAX—11 RSX Indirect and
RSX-11M-PLUS Indirect

3-13

3-17

Contents

3.4

TECHNICAL CHANGES TO THE VAX-11 RSX
DOCUMENTATION

3-18

SECTION 4 'RMS—11 VERSION 2.0 RELEASE NOTES
4.1

BUILDING RMS—11 APPLICATIONS ON VAX-11 RSX

4.2

NEW UTILITIES FEATURES
4.2.1

4.2.2
4.3

4.4

RMSCNV

RMSBCK, RMSDSP, and RMSRST

RMS-11 SOFTWARE RESTRICTIONS

4-2

4-3
4-3

4.3.1

RMSDES

4.3.2

RMSIFL

4-3

4.3.3

RMSCNV and RMSIFL

4-4

REPORTING RMS—11 PROBLEMS

APPENDIX A THEDIGITAL EQUIPMENT COMPUTER USERS
SOCIETY (DECUS)
A.1

DECUS GOALS

A.2

DECUS ACTIVITIES

INDEX

4-1

4-4

Preface

Manual Objective
The VAX-11 RSX Installation Guide and Release Notes provides the system
manager with a step-by-step procedure for installing VAX-11 RSX on a
VAX/VMS or MicroVMS operating system. It also includes information
pertaining to the Version 2.0 release of VAX-11 RSX.

Intended Audience |
This manual is intended for system managers and system users familiar with
both VAX/VMS and RSX-11 operating systems.

Structure of This Manual
This manual is divided into four sections and one appendix.
Section 1 describes the procedures that the system manager must follow to
copy the files from the distribution kit and to install and verify the VAX-11
RSX software on a VAX/VMS system.

Section 2 describes the error messages displayed if the installation or
verification fails and suggests possible user action.

Section 3 contains release notes for VAX-11 RSX. It describes the technical
changes made in Version 2.0 as well as any information that supplements the
VAX-11 RSX Compatibility Mode Reference Manual.
Section 4 contains release notes for RMS-11. It describes the technical
changes made in Version 2.0 of VAX-11 RSX.
|

Appendix A contains information about DECUS, the Digital Equipment

Computer Users Society, including details on how you can become a member.

Associated Manuals
The following manuals provide information that may help you during the
VAX-11 RSX installation:
e

Guide to VAX/VMS Software Installation

Guide to VAX/VMS System Management and Daily Operations

VAX-11 RSX Compatibility Mode Reference Manual

VAX/VMS Utilities Reference Volume

vii

Preface

Conventions Used in This Manual
The following conventions are obser

ved in this manual.

Convention

Meaning

CTRL/x

A symbol that indicates the CTRL key; it must

be held down while

another key is pressed. For example, CTRL/
C means hold down

CTRL while pressing C.

[xx]

A one- to three-character key symbol. For
example,
the RETURN key.

indicates

A lowercase n; indicates a variable for a number
.

A comma; separates parameters in commands.
A period; separates the file name from the file

specification.

type in a file

A semicolon; separates the file type from the file
version number in
a file specification.
Horizontal ellipsis; indicates that You can enter addition
al parameters,
values, or other information.
Vertical ellipsis; indicates that not all the statem
ents in an example
or figure are shown.

The explicit prompt of the Monitor Console Routine
(MCR), which
is the command interpreter provided by VAX-11
RSX. The MCR

prompting character appears whenever

control is returned to the

compatibility mode terminal and you can type input.

The VAX/VMS DIGITAL Command Language (DCL)
prompting
character. (Whenever control is returned to the native
mode terminal
and you can type input, this prompt appears.)
red ink

In interactive examples, what the user types is printed

black ink

In examples, black ink indicates what the system

term

Boldface term; indicates that the term is being defined.

in red.

prints or displays.

1.1

Introduction
VAX-11 RSX is a VAX/VMS and MicroVMS layered product that allows you
to execute RSX-11 tasks on VAX processors. The VAX-11 RSX Installation
Guide and Release Notes details the procedures necessary to install, verify, and
maintain the VAX-11 RSX Version 2.0 software on VAX/VMS Version 4.2
and MicroVMS Version 4.2.

ifying the VAX—11 RSX Kit

VAX-11 RSX Version 2.0 is distributed on the following types of media:

Magnetic tape (1600 bpi)

RLO2 disks

RC25 removable disks

RX50 diskettes

TK50 tape cartridges

Each distribution kit contains three files that are backup save sets. The
following list describes each save set and its contents:

RSX020.A

Contains the command files needed to perform both

the software installation and the Installation Verification
Procedure (IVP).

NOTE:

RSX020.8
|

Contains the task images, libraries, and other files that
constitute VAX-11 RSX Version 2.0.

RSX020.C

Contains the VAX~-11 RSX PDP-11 Instruction Set

Emulator. This save set is installed on systems that do
not have compatibility mode hardware or microcode.

Before you install VAX-11 RSX on a MicroVMS system, the MicroVMS
Base System must be installed. However, the following MicroVMS
optional components may also be required, depending on your
application:

Common Utilites Option—For utilities available from MCR (for
example, MAIL, DIFFERENCES, or SEARCH)

VAX-11 RSX Installation Guide

Secure User Option—For /SP (spooling) with certain utilities

example, PIP /SP)

(for

System Programming Option—To use Files-11 ODS-1 ACP for

read/write operations to RSX-11 compatible disks

1.3

Getting Started
This section describes the steps you should take before installin
g VAX-11
RSX Version 2.0.

Be sure that the values in the SYSTEM account authorization
record are
equal to or greater than the default values in the following
list:
Buffered byte count (BYTLM)

20480

Enqueued quota (ENQLM)

* Direct 1/0 limit (DIOLM)

Buffered 1/0 limit (BIOLM)

—

Open file quota (FILLM)

AST limit (ASTLM)

Also make sure that the SYSTEM account does not have the
DEFCLI
option specified. When set, this option prevents the user of the
SYSTEM
account from logging in under a command interpreter (CLI) other
than
the DIGITAL Command Language (DCL), and causes the VAX=11
RSX
Installation Verification Program (IVP) to fail.
"

To check these limits, run the VAX/VMS Authorize Utility

following commands:
$
$

SET DEFAULT SYS$SYSTEM
RUN AUTHORIZE

The system responds with the User Authorization File (UAF) prompt
(UAF> ). At the prompt, enter the following command:

UAF>

SHOW SYSTEM

The Authorize Utility displays the current values of the SYSTEM
account’s
authorization record.

If necessary, you can change these values by entering the MODIFY

command in response to the UAF prompt as shown in the following

command line:
UAF>

MODIFY SYSTEM/limit=new-value

For example:
UAF>

MODIFY SYSTEM/DIOLM=12

To modify the DEFCLI option, enter the following command in
response
to the UAF prompt:
UAF>

MODIFY SYSTEM/FLAGS=NODEFCLI

-y

by entering the

VAX-11 RSX Installation Guide

Re-enter the SHOW command to verify that the new values have been
set:

UAF>

SHOW SYSTEM

To exit from the Authorize Utility, enter the EXIT command at the UAF
prompt. You must then log out and log back in for the changes to take
effect.

If you are installing VAX-11 RSX Version 2.0 on a VAX processor that
supports compatibility mode hardware, be sure that your system has at
least 9 unused global sections and at least 200 unused global pages.

If you are installing VAX-11 RSX on a VAX processor that does not
support compatibility mode hardware or microcode, you must have at
least 11 unused global sections and at least 3704 unused global pages. To
determine how many global sections and global pages are available, enter
the following commands:
¢

RUN SYS$SYSTEM:INSTALL

INSTALL>

/GLOBAL

If you have the VAX /VMS Version 4.0 Install Utility (INSTALL) defined

as a foreign command in your SYSTARTUP.COM file, use the following
command:
¢

INSTALL LIST/GLOBAL

Read the last line of the screen display and note the following;:
*

The number of global sections USED

The number of global pages USED

The number of global pages UNUSED

To determine the unused global section count, invoke the VAX/VMS
System Generation Utility (SYSGEN) as follows:
¢

RUN SYS$SYSTEM:SYSGEN

SYSGEN> USE CURRENT
SYSGEN> SHOW GBLSECTIONS

The number in the first column of the SYSGEN display is the current
number of global sections. Subtract the number of used global sections
(which was shown by INSTALL) from the current number of global
sections (which is shown by the SYSGEN display). The difference is the
unused global section count.

Once you know how many unused global sections and global pages are
available, use the following steps to modify the necessary parameters, as
appropriate.(The procedure is similar if you are installing VAX-11 RSX on
a VAX processor without compatibility mode hardware.)
e

If the unused global section count is less than 9, increase the
GBLSECTIONS parameter with the following command:
SYSGEN> SET GBLSECTIONS new-value

To compute the new value, add 9 to the number of used global sections
shown by INSTALL.

VAX-11 RSX Installation Guide

If the number of unused global pages displayed by the

INSTALL

/GLOBAL command is less than 200, increase the GBLPAGES

parameter with the following command:
SYSGEN>

SET GBLPAGES new-value

To compute the new value, add 200 to the number of used global

pages.

If you have modified either parameter (GBLPAGES or GBLSECTIONS),
enter the following commands to write the new values into SYSGEN
and
exit:
SYSGEN>
SYSGEN>

WRITE CURRENT
EXIT

Note: Neither GBLPAGES nor GBLSECTIONS is a dynamic paramete

r. You
must rebootstrap your system before installing VAX-11 RSX Version
2.0 for the new value to take effect.

Remove all unwanted or redundant files from the appropriate media
to
make sure there are enough free blocks to install VAX-11 RSX.

The following summary indicates the approximate disk block utilization

requirements for VAX-11 RSX Version 2.0:

Disk Block Utilization

With Emulator

Without
Emulator

Peak disk block utilization:

10000 blocks

5500 blocks

Net disk block utilization:

8900 blocks

5400 blocks

Note: To preserve space on the system disk, DIGITAL recommends
that
you do not log in under the SYSTEM account. (The SYSTEM
account,
which has all privileges (including BYPASS), is intended
only for
software installation, bootstrapping, and system problem diagnosi
s.)
You can avoid a shortage of space by creating another account
and
assigning to it the minimum privileges you require.
A significant number of system disk blocks are used to contain
the
work files required for the installation and the files to be read
from
the distribution volume. The number of blocks (5500 blocks) used
during
the installation is called the peak disk block utilization. DIGITAL

recommends that you make enough blocks available on the

system disk
to cover peak utilization. If you choose not to do so, VMSINS
TAL will
operate in an alternate mode that reduces the peak utilizatio
n.

If a system failure occurs in the alternate mode, the installation will
fail.
To recover from this system failure, you must provide more
free blocks
and begin the installation again.
When the installation is complete, the system disk returns
to its normal
state. However, many disk blocks are permanently used
up as a result of

the installation process. The number of used disk blocks will be
greater
than the number in use before you began the installation. This
number
(5400 blocks) is called the net disk block utilization.

After you rebootstrap the system, you can recover additiona
l disk blocks
by purging system files that VMSINSTAL cannot purge during
the
installation.

VAX-11 RSX Installation Guide

Confirm the free block count by entering the following DCL command:
¢ SHOW DEVICE system-device-name

4 Back up your system disk using the Backup Utility. To invoke the utility,
enter the following command and information:
¢ BACKUP
From:
To:

indev:

outdev:

A system failure at a critical point during the installation may result

in unusable files. Therefore, you should always back up your system
disk before you attempt any software installation. You should use the
copy created from the backup operation for the installation. For more
information on the VAX/VMS Backup Utility, see the VAX/VMS Utilities
Reference Volume.

5 Invoke an editor to modify SYSTARTUP.COM and perform the following:.
e

Insert the following command line:
$ OSYS$MANAGER:VAX11RSX [spool_device]

This indirect command invokes VAX11RSX.COM. The command
file VAX11RSX.COM installs VAX-11 RSX each time your system is
bootstrapped, and establishes the environment in which VAX-11 RSX
works.

During the installation of VAX-11 RSX, VAX11RSX.COM is placed in
the system manager’s account [SYSMGR]. The spool_device parameter,
if specified, defines the logical device names SP and SP0. If this
parameter is not specified, these logical device names are defined as
LPAO.

The installation procedure also creates the command file
VAX11RSX$DEVICE_NAMES.COM in the system manager’s account

(if the file did not already exist from a previous installation of VAX-11
RSX). This file initially defines $$n logical names for the disk and
magnetic tape devices that were configured at the time of installation.
It also defines $$n names for SYS$SPECIFIC and SYS$COMMON to
allow references to them. The file is invoked by the VAX11RSX.COM
command procedure. You may modify VAX11RSX$DEVICE_
NAMES.COM to do any of the following:

— Add additional devices or rooted directories

— Delete definitions that are not needed (for example, $$n logical
names)

— Modify the $$n name unit number to improve clarity or efficiency
(by giving the lowest unit numbers to the most frequently used
devices)

You can include the systemwide page-length value that RSX-11
utilities (for example, the Task Builder (TKB) and the PDP-11
MACRO-11 Assembler (MACRO-11)) use to determine the number of
lines per page for a printed listing. If you want to specify this value,
include the following line in the definition table of SYSTARTUP.COM:
$ DEFINE/SYSTEM SYSSLP_LINES [page-length-value]

VAX-11 RSX Installation Guide

SYS$LP_LINES is used by the $PGLEN run-time library routine,
which computes the default number of lines on a printer page. This
routine can be used by any task that paginates and

produces listing

files.

The new page-length value range for SYS$LP_LIN

ES is 30 to 99 lines

per page. If you do not specify a value, the page-length
value will be
66 lines per page by default.
®

Remove any (CL, CO, and LB) logical name definiti

ons from the file.

Also, remove any start-up commands that install compatib

lity mode

components. VAX11RSX.COM specifies all the necessar
y logical

definitions and compatibility mode start-up commands.

other account that has the SETPRV privilege).

(or any

Be sure that all users are logged out and that all batch jobs are complet
ed
by entering the following commands:
¢

SHOW USERS

SHOW QUEUE/BATCH

Enter the following command to prevent users from gaining access

system:
$

name

to the

SET LOGINS/INTERACTIVE=0

Make sure DECnet-VAX is turned off. If you are not sure whether
DECnet-VAX is running on your system, enter the followin

g command:

SHOW NETWORK

If the message “Network unavailable” appears, proceed to
1.4. If
DECnet-VAX is running, turn it off by entering the followin
g comman

RUN SYS$SYSTEM:NCP

The system responds with the Network Control Program
(NCP) prompt
(NCP> ). At the prompt, enter the following commands:
NCP>
NCP>

1.4

SET EXECUTOR STATE SHUT
EXIT

Installing VAX-11 RSX
If you successfully completed all the steps in 1.3, you are
ready to install
VAX-11 RSX Version 2.0. The installation takes approxi
mately 30 minutes to
complete. At any time during the execution of VMSINS
TAL, you can type a
question mark (?) for help. Proceed in the following
manner:

VAX-11 RSX Installation Guide

2 Enter the following command line to initiate the installation:
s QSYS$UPDATE : VMSINSTAL RSX020 ddcu:

where:

ddcu:

is the drive in which you have placed the VAX-11 RSX distribution kit.
The installation procedure is performed in two phases: the first phase
copies the files and the second phase verifies that the VAX-11 RSX
utilities are working (see step 4 in this section).

3 At the start of the first phase, you must answer the following question:
* Are you satisfied with the backup of your system disk (YES]?

Assuming that you have performed the backup as recommended in 1.3,
step 4, press the RETURN key (YES is the default response).

4 Next, VMSINSTAL prompts you as follows:
Please mount the first volume of the set on ddcu:
* Are you ready?

Physically mount the distribution software in the appropriate drive (if you
have not already done so) and then answer YES.

A prompt will appear to request each additional volume. Enter YES after
you insert each volume. When all the volumes have been copied, remove
the last volume from the drive.

5 VMSINSTAL prompts you as follows:
Please select one of the following actions:
1)

Perform the installation

Both of the above

Create a file with a description of the installation

» What would you like to do [3]:7

Choose option 1 if you want to perform the installation without creating a
file that contains a description of the installation.

Choose option 2 if you do not want to perform the installation, but want
the description file.

Choose option 3 (the default) if you want both to perform the installation
and create a description file.

If you choose either option 1 or 3, VMSINSTAL responds ‘with the
following questions:

+ Do you want to install the MCR help library [YES]?

This library supplies help for VAX-11 RSX MCR commands and for the
RSX-11 utilities supplied with VAX-11 RSX. The library requires 2000
additional disk blocks. If you want the library, answer YES.
+ Do you want to purge files replaced by this installation [YES]?

If you do not have sufficient free disk space or you do not want the old
copies of the files, answer YES.

/AX~-11 RSX

Installation Guide

6 After you decide whether to install the library, the second phase of
the installation begins with a VMSINSTAL question concerning the
Installation Verification Procedure (IVP):
|
* Do you want to run the IVP after the installation [YES]?

IVP tests the various VAX-11 RSX components to make sure that each
component was installed correctly and is working properly. IVP is not
meant to be a comprehensive test of the components, but it does test some
of the features of each component. For example, IVP tests LBR by having
it create an object library, extract a module from that library, delete the
module in the library, and then reinsert the extracted module into the
library. Note that you can invoke IVP only while running VMSINSTAL.

When IVP is running and, for example, testing SLP, the following
messages appear:
XRSX020-I-IVPSTART, Installation Verification Procedure starting

- XRSX020-I-TESTSTART, SLP testing started at 10:17:18
XRSX020-8-TESTSUCCESSLP
S, testing completed successfully at 10:17:27
|
%RSX020-8-IVPSUCCESS, the installation verification of VAX-11 RSX Version 2.0 succeeded

Various compatibility mode images tested during the IVP may produce
status messages that are not in standard VAX/VMS format. However, if
an error occurs, IVP will detect it and produce the error message in the
standard VAX/VMS format.

Refer to 2.2 if an error message is displayed during the Installation
Verification Procedure (IVP). There you will find a description of each
error message and information on how to correct the error.

At this point, you have answered all the questions necessary to install
VAX-11 RSX successfully. The VMSINSTAL procedure will complete
your VAX-11 RSX Version 2.0 installation. See the Guide to VAX/VMS
Software Installation for more information about VMSINSTAL. |

When the installation is complete, VMSINSTAL invokes the start-up
procedure SYSSMANAGER:VAX11RSX.COM (which VMSINSTAL
copied from the distribution software into the system manager’s account
(SYSTEM)), and then exits. You can now use VAX-11 RSX Version 2.0.

8 For a complete description of the new images and files that VAX-11

RSX uses (if you chose either option 2 or option 3 in step 5), please read
SYS$UPDATE:RSX020.TXT.

1.5

After Installation
This section lists the steps that you should follow after the installation of
VAX-11 RSX.
|
|

Read the console listing carefully. Look for warning or error messages that

indicate steps you must perform manually. Many informational messages
will also be displayed. Be sure to read them.
»
mental backup of the system disk.

3 Establish minimum user account quotas for individual users (for example,
set quotas for open file, paging file, working set size, and subprocess
creation).
«

1-8

VAX-11 RSX Installation Guide

1.6

A Sample VAX-11 RSX Installation

The following example contains the text of a typical VAX-11 RSX Version 2.0
installation on VAX/VMS Version 4.0, using the RK07 distribution kit.

Username: SYSTEM
Password:

Welcome to BABBLE!

Last interactive login on Thursday, 19-SEP-1985 09:45
Last non-interactive login on Monday, 16-SEP-1985 20:00

$ OSYS$UPDATE:VMSINSTAL RSX020 DMO:

VAX/VMS Software Product Installation Procedure V4.0

It is 19-SEP-1985 at 10:01.

Enter a question mark (?) at anytime for help.

*+ Are you satisfied with the backup of your system disk (YES]?

Please mount the first volume of the set on DMO:
* Are you ready [YES]?
The following products will be processed:
RSX

V2.0

Beginning installation of RSX V2.0 at 10:02
YVMSINSTAL-I-RESTORE, Restoring product saveset A...
Please select one of the following actions:
1)

Perform the installation

Both of the above

Create a file with a description of the installation

* What would you like to do [3]:

An optional help library is provided for use with the MCR CLI.
This library supplies help for commands supported by MCR and for
the RSX utilities supplied with VAX-11 RSX. This 1library will
require approximately 2000 additional disk blocks. If you wish to
install this library on your system, answer yes to the following
question:

’

+ Do you want to install the MCR help library [YES]?
* Do you want to purge files replaced by this installation [YES]1?
*+ Do you want to run the IVP after the installation [(YES]?

|RET

VAX11RSX.COM, the startup command procedure, is used to set up
the environment for VAX-11 RSX. During the installation it will

be placed in the [SYSMGR] directory of the system root on which
Your system startup
this installation is being performed.
procedure should be modified to invoke this procedure when the
system boots. However, it will not be necessary to reboot the
system after the installation, since this procedure is invoked
as part of the installation. See the VAX-11 RSX Installation
Guide and Release Notes, or the procedure itself for information.
The installation procedure has no further questions to ask and
The rest
can continue from this point without user assistance.
of the installation will take approximately 10 minutes. If you
chose to run the IVP, it will take an additional 10 minutes.
%VMSINSTAL-I-RESTORE, Restoring product saveset B...

Note:

The following text will be displayed only if you are installing VAX-11

RSX on a VAX processor (for example, a MicroVAX) that does not contain
compatibility mode hardware or microcode.

** PDP-11 Instruction Set Emulator *x

Since your VAX processor does not include support for compatibility
mode within hardware or microcode, the VAX-11 RSX PDP-11 Imstruction
Set Emulator is being installed.

YVMSINSTAL-I-RESTORE, Restoring product saveset C...

- VAX-11 RSX Installation Guide

Note: The following text will be displayed only if you are install

ing VAX-11

RSX on a SYSCOMMON system (that is, SYS$SYSROO
T is a searchlist
directory on a VAXcluster running on a common system
disk).
‘#* VAXcluster common uyatam disk setup
*»

It you intend to execute VAX-11 RSX on other
nodes in your VAXcluster
which share this common system root, and you
have the appropriate
software license, you must ensure that SYS$
MANA
: VAX11RSX
GER
.COM is
executed on each node to define the appropri
ate logical names and to
create the system directory synonyms required
by RSX-11

software.

** System $$n logical names *»
RSX-11 tasks running under VAX-11 RSX can only
access VAX/VMS rooted
directories through the use of logical names
having a format which
resembles that of an RSX-11 physical device
name.

Similarly,

many VAX/VMS

Physical devices (including any device on a VAXcluste
r) can only be
accessed by RSX-11 tasks through the use of these
logical names.

VAX-11 RSX uses several standard system-wide logical
names, as well as
internal "logical names" (such as SY and TI)
for this purpose. See
the VAX-11 RSX Compatibility Mode Reference Manual
(Section 2.7) for

s,
|

more detailed information on VAX-11 RSX device
name mapping.

The system directory root (SYS$SYSROOT) is always
mapped by the VAX-11i
RSX logical name LB. However, other devices and
root directories should
be mapped by "$$n" logical names, with the string
"$$" followed by

an octal unit number from O to 377.

Note that even though $$n

logical names are not strictly necessary (except
for rooted directories)

on non-VAXcluster systems,

RSX-11 task performance

(particularly the ALUN$ and ELP$ directives) will be
improved through

their use.

This installation will create $$n names for
all the disk
and tape devices currently present on your system.

ARSX-I-$8N, the following $$n logical names will be
defined:

$$n

VAX/VMS device

$$0
$$1
$$2

BABBLE$DMAO:
BABBLESDMAI:
BABBLES$DRAO:

$8$3
$3$4
$$5

BABBLES$DRA1:
BABBLE$DRA2:
BABBLE$MFAOQ:

The file SYS$MANAGER:VAX11RSX$DEVICE_NAMES.COM
contains DEFINE commands

to create each of the $$n logical names listed
above. The VAX11RSX.COM
startup procedure will execute VAX11RSX$DEVICE_NA
MES.COM automatically
when it runs following this installation, and
during future system

startups.

If there are devices which were not displayed above,
which will be

commonly accessed by compatibility mode tasks
on your system,

you may

add $$n names to VAX11RSX$DEVICE_NAMES.COM. You may
also delete $$n

names which you do not want to be defined system-wi
de from this file.

Additionally, you should define $$n names for any rooted
directories
which will be commonly accessed look at the current
definition of LB
with the command "SHOW LOGICAL/FULL LB", for an
example of this.
You may also want to consider defining the logical
name

RSX$DEVICE_CACHE to comtrol VAX-11 RSX use of $$n
names:

it is

described more fully in the VAX-11 RSX Installat
ion Guide and Release
Notes, and in the VAX-11 RSX Compatibility Mode
Reference Manual.

Additionally,

to improve performance,

you may wish to reorganize the

$3$n names which have been defined, so that those which are most commonly

used have the lowest unit numbers.

Currently, they have been defined

in the order in which SHOW DEVICE displays them.

VAX11RSX$DEVICE_NAMES.COM will not be modified
on subsequent
installations of VAX-11 RSX. If you wish to perform
a future
installation that will require changes to the VAX11RSX
$DEVICE_NAMES
.COM
file, the old file must be deleted first. The installati
on will then
create a new copy of VAX11RSX$DEVICE_NAMES.COM.

ARSX-I-DESCRIBE, The installation is described in
SYS$UPDATE:RSX020.TXT

1-10

—

VAX-11 st Installation Guide

1) BACKTRANS (new image)

2) BCK (new image)
3) BRU (new image)
4) CNV (new image)
6) CRF (new image)
6) DEF (new image)
7) DES (new image)

8) DMP (new image)

9) DSC1 (new image)

10) DSP (new image)
11) EDI (new image)
12) FLX (new image)

13) FCSRES (new image)
14) ICM (new image)
16) IFL (new image)
16) INDSYS (new file)
17) LBR (new image)

18) LINK (miscellaneous)
19) MAC (new image)
20) MCR (new image)

21)

MCRHELPLIB (new file)

22) MCRTABLES (miscellaneous)

23) MFT (new image)
24) ODT (new file)

26) OLDSYLIB (miscellaneous)

26) OLDTKB (miscellaneous)
27) PAT (new image)

28) PIP (new image)

29) QIOSYM (new file)
30) RMS110DL (new file)

31) RMSDES (new file)
32) RMSLIB (new file)

33) RMSMAC (new file)

34) RST (new image)

36) RSX (new image)

36) RSXMAC (new file)
37) RSXSHR (new image)
38) RSXUSR (new image)

39) SLP (new image)
40) SYSLIB (new file)
41) TKB (new image)

42) VAX11iRSX (new file)

43) VMLIB (new file)
44) ZAP (new image)

Note: For VAX/VMS Version 4.0 and Version 4.1 host systems, the LINK
command definition has been modified to support the new LINK/RSX11
qualifiers.

Also, if the PDP-11 Instruction Set Emulator is installed, the
CEMSEMULATOR image file is also included.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...
%RSX020-I-IVPSTART, Installation Verification Procedure starting

1-11

- VAX-11 RSX Installation Guide

The Installation Verification Procedure
(IVP) tests
that VAX-11i
correctly by
testing various
compatibility mode

RSX installed
utilities.

This serves as a test of the utilities themselves and
Also, when DCL commands exist for compatibility

of the RSX AME.

mode utilities (i.e. LIBRARY/RSX for LBR), these will be used
test the

translation of

DCL

commands to

MCR

syntax for these

utilities.

Several of the compatibility mode utilities will log their normal

actions to

any error

SYS$OUTPUT.

not be in the
occurs,

the

These informational messages

as well as

messages that may be produced by these utilities, will

the

standard
IVP

standard

VAX/VMS

message

will detect it and

VAX/VMS

format.

If an

error

produce an error message in

The

IVP

will

also

produce

informational and success messages in the standard format.

%RSX020-1-TESTSTART, DMP testing started at 10:12:32
DMP -- DMP Version M08.01

(ANSI)

%RSX020-I1-TESTSUCCESS, DMP testing completed successfully at 10:13:27
%RSX020-I-TESTSTART, LBR testing started at 10:13:27
Modules deleted:

0BJ3
Module "0BJ1

" replaced

Module "0BJ2

" replaced

Entry points deleted:

ENT$AL
ENT$B2
ENT$A3
Modules deleted:

MCLBR3
Module "MCLBR1" replaced

Module "MCLBR2" replaced

%RSX020-S-TESTSUCCESS, LBR testing completed successfully at 10:16:52

%RSX020-I-TESTSTART, PAT testing started at 10:15:53
%RSX020-5-TESTSUCCESS, PAT testing completed successfully at 10:15:58
*R8X020-I-TESTSTART, PIP testing started at 10:15:58
PIP -- PIP Version M1600 (ANSI)

%R8X020-S-TESTSUCCESS, PIP testing completed successfully at 10:17:14

%RSX020-I-TESTSTART, FLX testing started at 10:17:14
FLX -- FLX Version 16.07

XRSX020-5-TESTSUCCESS, FLX testing completed successfully at 10:17:18

%RSX020-I-TESTSTART, SLP testing started at 10:17:18

%XRSX020-8-TESTSUCCESS, SLP testing completed successfully at 10:17:27
%XRSX020-8-IVPSUCCESS, the installation verification of VAX-11 RSX Version 2.0 succeeded
Installation of RSX V2.0 completed at 10:17
VMSINSTAL procedure done at 10:17

1-12

This section describes the messages that are displayed during the VAX-11
RSX installation and verification procedure, and suggests possible user action,
if appropriate. Messages are displayed or printedin both uppercase and
lowercase characters (when the output deviceis capable of displaying or

printing lowercase characters).

In this section, the fixed and variable portions of the text of a message
are dxsnngmshed by enclosing the variable portions in apostrophes (single

- quotation marks).

Messages displayed by VAX-11 RSX have the following format:
YFACILITY-L-IDENT, TEXT

[-FACILITY-L-IDENT,
TEXT]

‘where:
is a VAX-11 RSX facility or component name. A percent sign (%) prefixes
the first message issued, anda hyphen ( -) prefixes each subsequent message.
For the VAX-11 RSX kit installation procedure, the facility name is R5X020.
L

is a severity level indicator with one of the following values:

'fl!‘flé"“(fi

5mrity I.mml

Meaning

Success
Information
Warning
Error

Fatal, or severe error

is an abbreviation of the message text; the message descriptions are
alphabetized by this abbreviation.
TEXT

is the explanation of the message.

2-1

VAX-11 RSX Installation and Verification Messages

2.2

Message Summary
CONSOLE,

console device CSA1: not configured; definin'g%n anyway

Explanation: The installation program has assigned the console mass storage
device a $$n name even though the console has not been connected to
the

system (using the system generation CONNECT CONSOLE command)

User Action: None.

DESCRIBE,

the instanation is described in SYS$UPDATE:RSXvvu.TXT

Explanation: Indicates where the installation description can be found after

the installation is complete.
User Action: None.
ERRORS,

of the “nn” action listed above, the following “nn” should be reviewed:

Explanation: If errors occur during the software installation, this message
will summarize the points at which the errors occurred.

User Action: Review the specified actions.
IVPFAILURE,

the installation verification of VAX-11 RSX “version” failed

Explanation: The installation did not pass the software Installation
Verification Procedure (IVP). Previous error messages should have indicated
the specific reason(s) for the failure.

User Action: Submit a Software Performance Report (SPR) describing the

problem and include the console listing of the software installation.
IVPSTART,

starting installation verification procedure

Explanation: IVP is beginning.
User Action: None.
IVPSUCCESS,

the installation verification of VAX-11 RSX “version” succeeded

Explanation: IVP did not detect any errors in the software installation.

User Action: None.
KEEPOLD,

retaining previous SYSSMANAGER:VAX11RSX$DEVICE_
NAMES.COM

Explanation: A $$n name definition file already exists for your system.
It will not be superseded.
User Action: None.

NOBLOCKS, RSX “version” requires “n” additional blocks after installation
Explanation: After installation, the specified version of VAX-11 RSX will use
the specified number of blocks on the system disk. If the specified number of
blocks is not available, the installation will fail.
User Action: Purge or delete unnecessary files from the system disk.

2-2

VAX-11 RSX Installation and Verification Messages

NO$$N,

unable to read device information to create $$n names

Explanation: An error occurred while attempting to access the SHOW
DEVICE command output.

User Action: You must manually add $$n name definitions to the

VAX11RSX$DEVICE_NAMES.COM command file.

SOME,

unable to collect all device information

Explanation: An error occurred during the processing of device information
while creating $$n names.

User Action: You must manually complete the list of $$n definitions in the
VAX11RSX$DEVICE_NAMES.COM command file.
TESTERROR,

“utility” fail test of “test description”

Explanation: An error occurred while performing the specified utility test

during the IVP.

User Action: Submit an SPR describing the problem and include the console
listing of the software installation.
TESTSTART,

“utility” testing started

Explanation: IVP has begun testing the specified utility.
User Action: None.

TESTSUCCESS,

“utility” testing completed successfully

Explanation: IVP detected no errors.
User Action: None.

VERSION,

RSX “version” must be installed on existing VAX/VMS “version”
system

Explanation: This version of VAX-11 RSX can be installed only on the
specified version of VAX/VMS.

User Action: You have the wrong version of either VAX-11 RSX or
VAX/VMS. You must obtain the correct version.
$$N,

the following $$n logical names will be defined:

Explanation: The installation will list the $$n names created for disks and
magnetic tapes on your system.

User Action: None.

2-3

3.1

VAX-11 RSX Softwam Roloaso Note
This section contains a brief de&mptwn of all new and modified ¢
features for VAX-11 RSX Version 2.0. Many of these features are more
completely dwumenwdin the VAX-11 RSX Compatibility Mode Reference

Manual.

3.1.1

P-1 1 Instructlon Set Emulator
VAX—11 RSX PDF
- The VAX-11 RSX distribution software consists of the following three save
sets:

RSX020.A, which contains the command files needed to perform both the
software install;ation and the Instaallation Verification Procedure (IVP).

2 RSXO:EQB, which contains the task images, libraries, and other files that
constitute VAX-11 RSX Version 2.0.

3 RSX020.C, which contains the VAX-11 RSX PDP-11 Instruction Set
Emulator.

‘During the installation process, the VAX-11 RSX PDP-11 Instruction Set
Emulator save set will be installed on your system disk if your VAX processor
does not includehardware or microcodesupport for compatibility mode. See

Section 10 of the VAXmll RSX Compatszlzty Mmie Reference Manual for more
informationabout the Emulator.

3.1.2

Changes to MCR
The followmg sectmm desmbe changes to the Monitor Console Routine
3.1.2.1

‘ New Commands

| DELETE/INTRUSIONMRECORO
Remwea an entry from t ne break-in database.
SHOW INTRUSION

Displays the contents of the break-in database.

VAX-11 RSX Version 2.0 Release Notes

3.1.2.2

New or Revised Keywords and Parameters
RUNOFF
/DEVICE=(option],...])—Controls whether DSR (Digital Standard Runoff)

generates an output file (LNI) that is suitable for printing on LN01, LNO1E, or

LNO3 laser printers.

/REVERSE_EMPHASIS—Directs DSR to change the order in which flagged
text is underlined on an output device.

3.1,3

Changes to DCL
The following sections describe changes to the DIGITAL Command Language
(DCL) documentation for VAX-11 RSX Version 2.0.

3.1.3.1

Enhancement to the DCL Command MCR

The DCL command MCR enables RSX-11 components top be run in a
manner that is compatible with the RSX-11 operating system. If you wish,
may include a component name on the MCR command line to invoke
that component. However, you may enter only an RSX-11 or VAX/VMS

component and a command line for that component.

If you type the command MCR and press the RETURN key, the MCR
command interpreter (CLI) prompts for command input, placing you in

prompting mode. This mode allows access to all the commands in the MCR
CLI To exit from MCR, press CTRL/Z. You will be returned to DCL.
Commands that are issued in this mode have their input device (SYS$INPUT)
assigned to a mailbox. Native mode images that read from SYS$INPUT (TI)
should not be used in this mode (for example, HELP or the EDT editor).
RSX-11 tasks which read from TI may be used, but only if they perform
~simple line-oriented read operations (such as the command prompting mode

of most RSX-11 utilities).

3.1.3.2

New LINK/RSX11 Qualifiers

The following command qualifiers have been added to the list of qualifiers
supported by the DCL command LINK/RSX11:
|

/INOJICHECKPOINT=keyword

Allows a task image to be checkpointed (that is, the task may be swapped
out). (Only one keyword, SYSTEM or TASK may be specified.)

/INOJCOMPATIBLE

Aligns memory-resident overlays on 512~byte boundaries to correspond to

VAX/VMS memory management allocations.

/ERROR_LIMIT[=n]
-

Causes the Task Builder to exit after n errors have occurred. When n is not
specified, the default is 1. This qualifier is a synonym for /EXIT[=n].

/LONG
Refers to map size. This qualifier is a synonym for /FULL.

3-2

/AX-11 RSX Version 2.0 Release Notes

/OPTIONS-fiIospoc

Allows you to specify the name of a file containing Task Bmlder options.
This qualifieris a synonym for /TASK..OPTIONS
/INOJRECEIVE

Allows the default task to receive messages from the Executive Send Data

|(SDATS) directive.

/INOJRESIDENT_OVERLAYS
Builds memory-resident overlays intotheimage by usmg the memoryresident overlay operator.

/INOJSEGREGATE

Allocates virtual address space containing contiguous program sections first
to the read-write (RW) program sections and then to the read-only (RO)
program sections.

/SHAREABLE=keyword

Instructs the Task Builder to build a shareable common, a shareable library,
or a shareable task image. (Only one keyword, COMMON, LIBRARY, or
TASK may be specified.)

/SLOW

Invokes the Slow Task Builder, which is used to build more complex task
images.

3.1.4

Changes to the Indirect C: ommand Processor (Indirect)
The following sections describe the changes for the Indirect Command
Processor (Indirect) thatis supported under VAX-11 RSX. These changes
include new directives and a new symbol

3.1.4.1

New Directives |

.ENABLE CLI

Passes commands that are not processed by Indirect to your command

interpreter (CLI).

.ENABLE DELETE

Deletes the current command line whan Indirect processes the last command
linein the file.

.TRANSLATE

Allows a command file to expand a local or global logical name assignment.
3.1.4.2

New Symbol
< SYTYP>

Contains the “VAX-11 RSX” system indentification string.

3-3

VAX-11 RSX Version 2.0 Release Notes

3.1.5

Support for New VAX-11 RSX Executive Directives
VAX-11 RSX Version 2.0 includes support for a subset of the RSX-11

memory management (sometimes referred to as Program Logical Address

-Space (PLAS)) directives. VAX-11 RSX now supports the following RSX-11
memory management directives:

ATRGS

Attaches a regicm
CRAWS
Creates an address window

CRRG$
Creates a region

DTRGS
Detaches a region

ELAWS
Eliminates an address window

GMCXS$

Gets the mapping context
GREGS
Gets the region parameters

MAPS
Maps an address window

UMAPS
Unmaps an address window

This support allows RSX-11 task images running on the VAX/VMS operating

system to use RSX-11 memory management directives. VAX-11 RSX
memory management includes the following RSX-11 features:

3-4

Task and library memory-resident overlays

Shared resident libraries and commons

C(Cluster libraries

Virtual sections

Shared data commons with VAX/VMS native images

VAX-11 RSX Version 2.0 Release Notes

Additionally, VAX-11 RSX now supports the following logical name
directives that are new to RSX-1 lePLUS Version 3.0 and Micro/RSX

Version 3.0:

ACHNS
Assigns channels to a logical name

CLONS (CLOGS)
Creates a logical name

DLONS (DLOGS)

Deletes a logical name
RLONS (RLOGS)
Recursive translation of a logical name

TLONS (TLOGS)
Translates a logical name

GDIRS
Gets the default directory

FEATS
Tests for a system feature

SDIRS
Sets the default directory
Because it supports these directives, VAX-11 RSX is fully compatible with
RSX-11M/M-PLUS and Micro/RSX operating systems in the following areas:

Support of static and dynamic regions

Support of shared regions

Support of memory-resident overlaid tasks

Support of tasks linked to memory-resident overlaid libraries (including

Support of tasks linked to cluster libraries

Support of virtual sections

Support of FORTRAN-77 virtual arrays

FCSRES)

Note: Because FCSRESis vectored, tasks can be transported between VAX-11

RSX Version 2.0 and RSX-11M-PLUS Version 3.0, Micro/RSX Version 3.0,
and RSX-11M Version 4.2

FORTRAN-77 tasks using virtual arrays may be transferred between
VAX-11 RSX and any RSX-11 operating system. VAX-11 RSX places no
restrictions on the use of FORTRAN-77 virtual arrays.

3-5

VAX-11 RSX Version 2.0 Release Notes

3.2

Enhancements to Existing VAX-11 RSX Features
The following sections describe the enhancements to VAX-11 RSX. Many
of these features are also documented in greater detail in the VAX-11 RSX
Compatibility Mode Reference Manual.

3.2.1

Support for SYSCOMMON System Disks
The Applications Migration Executive (AME) has been enhanced to support
device name and file-handling operations. These operations now perform
compatibly with SYSCOMMON system disks or with any VAX/VMS search
as long as the logical name (and its translation strings) has been repetitively
translated until either of the following conditions occur:
®

Translations are marked with the TERMINAL attribute

(LNM$M_TERMINAL).

Strings that have no translations are reached on all branches of the search
list.

Each of these final strings must contain only a physical device name, or a
physical device name combined with a rooted directory name.
Note that if a file is opened by file identification rather than by file name, or
if a file is spooled using the PRINT$ routine, there is a small possibility that

an incorrect file will be found. This may occur if the terminal translations
of the VAX/VMS logical name used as a “device” are on different physical
devices and if the specified DID and FID exist on a device prior to the
intended one. To avoid such an occurrence, DIGITAL recommends that
you do not use search lists spanning multiple devices. However, file access
by directory and file name (the normal case) is no more susceptible to this
problem than native mode utilities using search lists. (In other words, if the
directory and file name exist on a device prior to the intended one, both
R5X-11 and VAX/VMS programs will find the same “incorrect” file.)

3.2.2

Performance En hancements to the ALUNS and ELP$ Directives
For VAX-11 RSX Version 2.0, the software that assigns, parses, and maps
device names has been redesigned and reimplemented, resulting in a
significant performance improvement for most tasks that use the Assign
Logical Unit Number (ALUN$) and Extended Logical Parse (ELP$) directives.

3.2.3

$$N Translation Caching
Individual users should define $$n names for their own use with high

$$n unit numbers (starting at 347 (8) and descending to lower numbers).

However, because $$n names defined dynamically by programs have unit
numbers beginning at 350 (8) and ascending to higher unit numbers, you
may have to attempt many translations before you arrive at these values.
As a result, the VAX-11 RSX Version 2.0 AME will cache the translation of

LB, SP, and $$n names the first time it translates them. After caching the

translation, the AME will no longer have to translate those particular names.
The AME will always attempt to translate $$n names with units higher than
350 (8) since these may be dynamically defined by other programs while the

VAX-11 RSX Version 2.0 Release Notes

task is running, and even names that were already translated may change
during task execution.

The implication of this caching for users is that, with the exception of
dynamic $$n names, any changes to $$n names after the task begins may
not affect the operation of the task. However, this behavior may be altered.
See the VAX-11 RSX Compatibility Mode Reference Manual for a description of
RSX$DEVICE_CACHE for more information.

3.2.4

Terminal Driver Enhancements
Enhancements have been made to the VAX-11 RSX terminal driver, which
allow the driver to operate like the RSX-11 terminal driver. The terminal
driver contains the following new or modified features:

Break-through Write Function
Maps the RSX-11 function code IO.WBT to the VAX/VMS function,
IO_WRITELBLK!IO$M_BREAKTHRU.

TC.RAT Terminal Characteristic

Maps the RSX-11 characteristic TC.RAT (Type-ahead buffer) to the
VAX/VMS characteristic TTSM_NOTYPEAHD.
10.RAL Function Code

Maps the RSX-11 function code IO.RAL to the VAX/VMS function code
IO$_TTYREADALL. By using IO$_TTYREADALL, no interpretation of data
will occur.

10.RLB Function Code

When this code is combined with both the subfunction bits TF.RAL (Read
All) and T.RST (Read Special Terminators), VAX-11 RSX will not ignore the
TF.RST subfunction. The special characters terminate the read operation.

” " 3.2.56

Reactivating RSX—11 Images
On VAX-11 RSX Version 2.0, the AME restores all necessary initial context so
‘that it is possible to reactivate RSX-11 task images (for example, when using
the RUN/INTERVAL=delta-time command).

3.2.6

Reporting CRF Subprocess Errors
VAX-11 RSX Version 2.0 provides a way of reporting Cross-Reference
Processor (CRF) subprocess errors. A procedure has been created that allows
a subprocess task to write to a mailbox owned by the main process. This
procedure is referrred to as output chaining. The Applications Migration
Executive (AME) then writes this data to its SYSSOUTPUT file, which, in
turn, allows the CRF task to report errors.

Note that any task that is spawned with the parent’s terminal input
pseudodevice (TI), when the output half of TI is a Record Management

Services (RMS-11) file, will automatically and transparently make use of

output chaining to write data to TL

3-7

VAX-11 RSX Version 2.0 Release Notes

3.2.7

EXSTS$ Directive Behavior Change
In VAX-11 RSX, the Exit With Status (EXST$) directive now uses an RSX-11
status passback procedure to provide the parent process with the full RSX-11
status word. However, because the VAX-11 RSX passback procedure is a
protocol initialized between the AME running in the parent process and the
MCR CLI running in the subprocess, this full word status passback is used
only for tasks activated as the result of a spawned MCR CLI command. The
enhancement, to the Exit With Status directive allows Indirect command
procedures to use the <EXSTAT> symbol to access the full RSX-11 status
word from any MCR commands executed.

3.2.8

DECnet-11M and DECnet—11M-PLUS NETGEN Support
Because VAX-11 RSX supports the return of the full RSX-11 status word of
a spawned CLI command to an Indirect command procedure, it is possible
to perform NETGEN operations for DECnet-11M and DECnet-11M-PLUS.
To do this, however, you must have DECnet-11M Version 4.2 or
DECnet-11M-PLUS Version 3.0

3.2.9

Changes to the Indirect . TESTPARTITION and GPRTS Directives
The .TESTPARTITION directive allows a command file to acquire information
about any region known to VAX-11 RSX. The Get Partition Parameters
—
(GPRTS$) directive allows a task to acquire information about any region
known to VAX-11 RSX. Any of the following are considered known regions:

The GEN partition, which is the task region of the current task

A group-global section created by VAX-11 RSX

A group-global section created by a VAX/VMS native mode image

A system-global section created by the VAX/VMS Install Utility

A valid image file of a resident library or common located in

SYS$LIBRARY

A valid image file of a resident library or common to which the region’s
name translates (if the latter is defined as a logical name)

3.2.10 Enhancements to VAX—11 RSX Error Messages
Along with changes made to some existing VAX-11 RSX error messages,
there are some new error messages that have been added for Version 2.0 of
VAX-11 RSX. See Section 10 of the VAX-11 RSX Compatibility Mode Reference
Manual and Section 2 of this manual for a description of these messages.
Unlike the previous version of VAX-11 RSX, in which most errors caused the
AME to display a single error message, the AME now displays a sequence
of one to three error messages. The first line of the message indicates the
general area of the error. The second line gives provides more detailed
information, and the final line notes the VAX/VMS error status that caused
the failure. The following is a typical illustration of this sequence:

%RSX-F-ERRINILIB,

unable to initialize library /common \FCSRES\

VAX-11 RSX Version 2.0 Release Notes

-RSX-F-CRSCERR,

error creating the “RSX$FCSRES” global section

-SYSTEM-F-GPTFULL,

3.2.10.1

global page table is full

New Error Message

Under VAX-11 RSX Version 2.0, the incorrect use of a high-level language
subroutine or an error detected during the loading of an overlay segment
results in task termination by means of a breakpoint (BPT) instruction. The
task aborts and one of the following error messages is displayed:

%RSX-F-ERRLANGIN,

error in high level language interface

%RSX-F-ERRLODOVR,

load overlay failure

Both errors are followed by the message:

%RSX-F-IMAGETERM, \Process name,\ terminated, \date\ \time\

3.2.11 BOMS Directive Error Messages
For compatibility with RSX-11M-PLUS Version 3.0 and Micro/RSX Version
3.0, VAX-11 RSX includes the overlay control error (ALERR) and high-level
language interface error (XERR) routines in SYS$LIBRARY:SYSLIB.OLB.
These routines use the Breakpoint Or Message (BOMS$) directive which is
not documented. The BOM$ directive may simulate a breakpoint (BPT)
instruction or cause the printing of an error message before task termination.
One of the following error messages is returned by the BOM$ directive:

%RSX$S_ERRLANGIN,

Error in a high level language interface

%RSX$S_ERRLODOVR,

Load overlay failure

%RSX$S_INVBOMCOD,

Invalid BOMS$ directive parameter

~. 3.2.12 Named Directory Support
Software enhancements made to RSX-11M-PLUS Version 3.0 for directory
formats of Files-11 Structure Level 1 devices are now supported by VAX-11
RSX and all its utilities except the Disk Save and Compress Utility (DSC1)
and the File Transfer Utility (FLX).
Directories may have the following format:
[utd]

where:

ufd
is 1 to 9 alphanumeric characters (A to Z, 1 to 9) as well as the UIC directory
format ([g,m]).
'

~. 3.3

VAX-11 RSX Software Restrictions
The following sections describe the software restrictions for VAX-11 RSX
Version 2.0. Many of these restrictions are also documented in greater detail
in the VAX-11 RSX Compatibility Mode Reference Manual.

3-9

VAX-11 RSX Version 2.0 Release Notes

3.3.1

Defining SYSSLOGIN
The system logical name SYS$SYLOGIN points to the systemwide login
command file SYSSMANAGER:SYLOGIN.COM (unless specified otherwise).
This file is invoked as part of the login procedure used by the DCL command

interpreter (CLI). SYLOGIN.COM contains DCL commands that usually
cannot be executed by Indirect (ICM). However, if you log in on the system
using the Monitor Console Routine (MCR) command interpreter, you may
wish to create a systemwide login command file that contains Indirect
commands. You can do this by creating a SYSSMANAGER:SYLOGIN.CMD
file and then defining the logical name SYS$LOGIN as follows:
¢ DEFINE/SYSTEM/EXECUTIVE SYS$SYLOGIN SYS$MANAGER:SYLOGIN

By doing this, SYLOGIN.COM is invoked when you log in using DCL and
SYLOGIN.CMD is invoked when you log in using MCR.

3.3.2

Differences Between VAX-11 RSX Memory Management
Directives and RSX-11 Memory Management Directives

—

The following sections describe differences between VAX-11 RSX memory
management directives and RSX-11 memory management directives.

3.3.2.1

Region Creation
VAX-11 RSX Version 2.0 static regions may be created in one of the following
ways:

By using the VAX/VMS Install Utility to make a compatibility mode
image known to the system and by creating a global section (if the image
has read-only sections or is a memory-resident library or common). For

example:

~—

¢ INSTALL CREATE USER$: (MIKEE]RESLIB.EXE/SHARED

NOTE: To create a static region with read-only access, enter the following
command:
¢ INSTALL CREATE USER$: [MIKEE)RESLIB.EXE/NOWRITEABLE/SHARED

By defining the name of a region as a logical name. This translates to the
file specification of a compatibility mode image of a resident library or
common. For example:

¢ DEFINE RESLIB USER$: [MIKEE]RESCOM.EXE

VAX-11 RSX Version 2.0 dynamic regions can be defined by issuing the

Create Region (CRRGS$) directive in a compatibility mode image.

3.3.2.2

Region Deletion
VAX-11 RSX also allows you to delete a static region. To do this, use the
VAX/VMS Install Utility (if the region was created by the Install Utility) by
entering the following command:
¢ INSTALL DELETE USER$: [MIKEE]RESLIB.EXE

To deassign the logical name for the static region, enter the following:
¢ DEASSIGN RESCOM

3-10

—

VAX-11 RSX Version 2.0 Release Notes

Region Attachment

3.3.23

A compatibility mode task image can attach to any region created by VAX-11
RSX. It can also attach to any existent global section created by the VAX/VMS5
Install Utility or by a VAX/VMS native mode image, if the desired access
is allowed. For regions created by VAX-11 RSX, the protection check is

the same as it is for RSX-11 systems. For global sections created by the

VAX/VMS Install Utility or native mode images, the check is the same as it is
for VAX/VMS systems.

Displaying Region Information

3.3.24

The following list describes how to display information about R5X-11 regions.

The VAX/VMS Install Utility can be used to display the names and the
characteristics of the global sections that are associated to static or dynamic
RSX-11 regions by entering either of the following:
$

INSTALL LIST /GLOB

INSTALL LIST /GLOB/FULL

NOTE: For compatibility with RSX-11 systems, VAX-11 RSX creates regions
that have a zero length (R.GSIZ=0 in the Region Definition Block
(RDB)), but it does not asscociate a global section to it. Therefore,
names of such regions cannot be displayed with the VAX/VMS Install
Utility.

The DCL command SHOW can be used to display the image files of
resident libraries or commons that were defined as regions by using logical
names. For example:
$

SHOW LOG RESCOM

RESCOM = USERS$: [DIREC.LIBRARIES]RESCOM.EXE
or

W
LOG RES#*
SHO

RESLIB = USERS: [DIREC.LIBRARIES]RESLIB.EXE
RESCOM = USERS$: [DIREC.LIBRARIES]RESCOM.EXE

3.3.2.5

Region Checkpointing

VAX-11 RSX Version 2.0 does not support the Checkpoint Common Region

(CPCRS$) directive. However, region checkpointing does exist. The only
difference is when checkpointing occurs, which cannot be controlled. VAX-11

RSX memory management creates a global section on behalf of the shared
common region, using the compatibility mode image file as a section file. If
the common region is accessed read/write and was built with checkpointing
allowed (using the /CP switch or the /CHECKPOINT qualifier), the section
file is updated each time pages from the common region are swapped out. At
the end, when the common is detached and the region deleted, the section
file contains all the modifications made in the common region.

NOTE:

To make sure that a compatibility mode image file of a common region
accessed for read/write operations is not being updated during the
mapping session, build the common region as noncheckpointable. For
a noncheckpointable common region file, VAX-11 RSX creates a Copy on
Reference global section, and the pages are swapped into the system’s
page file rather than into the section file.

3-11

VAX-11 RSX Version 2.0 Release Notes

3.3.2.6

Memory Management Granularity
VAX-11 RSX memory management must comply with the VAX /VMS

memory management. Thus, under VAX-11 RSX, a page is a set of
256

contiguous word locations which VAX/VMS uses as a unit for memory

mapping and protection. The following requirements apply:

Window alignment—Compatibility mode task images running on
VAX/VMS and issuing memory management mapping directives must
specify the window offset W.NOFF in the Window Definition Block as a
multiple of 8 (256-word window alignment). If this requirement is not
satisfied, VAX-11 RSX rejects the mapping attempt, returning an IE.ALG
error code.
|

/CM switch—Compatibility mode images of memory-resident overlaid
libraries (that are accessed for read/write operations) must task build with
the /CM switch or link with the /COMPATIBILTY qualifier. In this way,
the Task Builder generates 256-word aligned windows for the memoryresident overlays. When VAX-11 RSX detects that a resident library does

not satisfy this requirement, it displays an error message on SYS$ERROR
and aborts the task. A task has read/write access to a memory-resident
library or common when one of the following options was specified at
task-build time:

— RESCOM = name /RW
— RESLIB = name /RW

— COMMON = name :RW
= LIBR = name :RW

— CLSTR = name, name:RW
NOTE: The VAX-11 RSX Task Builder has the default set to /CM.

3.3.2.7

Compatibility Between VAX-11 RSX Memory Management and
RSX-11 Memory Management

Tasks that use memory management and that are developed and tested
on
VAX-11 RSX can be transported to RSX-11, and conversely. Additional
ly,
VAX-11 RSX provides better performance for shared regions accessed
as readonly than it does for regions accessed for read/write operations. Therefore,
tasks that do not write data in resident libraries or commons should access
them as read-only, by specifying any one of the following TKB options
while
the task is being built:

3.3.2.8

LIBR = library:RO

RESLIB = library/RO

CLSTR = library:RO

VAX-11 RSX Memory Management Privilege Requirements
To emulate the region attach/detach mechanism, the global sections created
by the VAX-11 RSX memory management must be permanent. Therefore,
the PRMGBL privilege is required for compatibility mode task images using

memory management directives, or linking against memory-resident
libraries
or commons. To satisfy this requirement, RSX.EXE is installed at
VAX-11

RSX startup time with the PRMGBL privilege.

3-12

e
TM

VAX-11 RSX Version 2.0 Release Notes

3.3.3

Removal of Restrictions to Installing Compatibility Mode Tasks
To share read-only sections of tasks built with the /MU qualifier and installed
~ with the VAX/VMS Install Utility, VAX-11 RSX Version 1.0 required that
the task name be the same as the task file name. VAX-11 RSX Version 2.0
removes this restriction. Tasks built with the /MU qualifier can now have
any name and still share read-only sections.

3.3.4 EXTK$ Directive Behavior Change
VAX-11 RSX does not change the current address mapping of a memoryresident overlaid task that issues an Extend Task (EXTK$) directive. However,
if the task has no memory-resident overlays, VAX-11 RSX attempts to modify
the mapping of the task to its region by the specified number of 32-word
locks.
|
NOTE: Because VAX/VMS memory management acts on 256-word pages instead

of on 32-word blocks, VAX-11 RSX will map an entire page when the
task requests an extension equal to a fraction of a page. VAX-11 RSX also
leaves the mapping unchanged if the task requests a contraction but still
needs access to a fraction of the last page.
The following restrictions apply to the Extend Task directive:

3.3.5

A task cannot extend itself beyond 32k words.

A task that has memory-resident overlays cannot reduce its size to less
than the size of the highest window in the task region.

Changes Required to User-Created RSXUSR.EXE Images
The following information applies only to systems that have their own

RSXUSR.EXE image if it was not changed for VAX-11 RSX Version 1.0. Note
that if the image was changed, you do not have to do it again for VAX-11
RSX Version 2.0.

The VAX-11 RSX AME consists of the following four images:
*

RSXSHR.EXE

RSXUSR.EXE

RSX.EXE

BACKTRANS.EXE

The shareable images RSXSHR.EXE and RSXUSR.EXE constitute the actual
AME, and the executable images RSX.EXE and BACKTRANS.EXE provide
shell functions that are invoked by the current command interpreter (CLI)
when VAX-11 RSX tasks are run.

On the previous version of VAX-11 RSX a change in the structure of the
AME required changes to the RSXUSR.EXE shareable image. If you created
your own RSXUSR.EXE image (and you have not already modified it for
VAX-11 RSX Version 1.0), you must modify it before attempting to use
it with VAX-11 RSX Version 2.0.
Changes affecting RSXUSR.EXE are as
follows:

RSXUSR.EXE supports user-defined RSX-11 directives. When the AME
encounters an RSX DIC code that it does not support, it dispatches
3-13

VAX-11 RSX Version 2.0 Release Notes

control to RSXUSR through the transfer vector RSX$UNKNOWN to allow
emulation of the directive user-supplied code. The RSXUSR.EXE image
supplied with VAX-11 RSX supplies the directive error status IE.SDP
(DIC or DPB size invalid). You can substitute a user-written RSXUSR.EXE
image for the supplied image by defining the logical name RSXUSR to
the full file name of the desired replacement or by replacing the image

SYS$SHARE:RSXUSR.EXE.

Prior to VAX-11 RSX Version 1.0, all compatibility mode images were

linked against base addresses. The base address for the RSXUSR.EXE
shareable image was 21000 (16). This address placed size constraints on
the RSXSHR.EXE shareable image. With the new software features added,
the location of the RSXUSR.EXE image had to be modified. For Version
1.0 of VAX-11 RSX, RSXSHR.EXE and RSXUSR.EXE were converted to
unbased shareable images, which means that the images are placed in
the process virtual address space at image activation time (by VAX/VMS),
regardless of how large either image may become in the future.
®

To use your own RSXUSR.EXE shareable image with the VAX-11 RSX
AME, you must modify the source code and the data to be PositionIndependent Code (PIC). You must then link the object files as an unbased
shareable image (by removing the “BASE=n" statement in the option file
for the DCL command LINK).

When converting your source code and data to PIC, be sure that your
RSXUSR.EXE adheres to the following rules:
— Any data references to addresses must use the MACRO-32 .ADDRESS
directive rather than the .LONG directive. Address references using
.LONG cannot be modified at run time by the image activator and,
therefore, can prevent the shareable image from being relocated
properly.
— Any code references to addresses outside the RSXUSR.EXE shareable
image must use the G" (general) addressing mode. Doing so allows the
image activator to modify the target address at run time. References to
addresses within the RSXUSR.EXE image must use either G" or relative
(L", W7, or B") addressing mode. General addressing mode allows the
image activator to modify the target addresses at run time. Relative
addressing mode within a shareable image is PIC and works correctly
wherever the image is located.
In particular, be careful to make sure that the RSXUSR.EXE transfer
vector uses relative addressing for the “jump” to the DIC Dispatch

routine.

— Do not use labels in the RSXUSR.EXE image as displacements, because
the image activator will not be able to relocate the references properly.
Use of labels is common when an offset into a static data structure
must be calculated. However, the offset could be calculated in a
register, so the data can be referenced using the data structure label as
a displacement to the register. Change such code to use index mode
rather than displacement mode.
— Do not use immediate mode when referencing labels.

Note: For more detailed information, refer to the VAX/VMS Utilities Reference

Volume.

3-14

VAX-11 RSX Version 2.0 Release Notes

There are some applications that may pass information on devices (for
example, SY or TI) to another task. For example, the MACRO-11 and
TKB tasks pass a file specification to the CRF task when the /CR switch is
supplied.

When a device name is passed to another task, that device name must be a

name that is usable by the second task. In particular, the device name must

be either a physical device name, or a logical name that is shared by both
tasks. If both tasks are in the same application, the device name could be a
jobwide logical name.

In VAX-11 RSX Version 2.0, RSX-11 tasks infrequently use physical device
N

names. Because most VAX/VMS device names cannot be represented
accurately in RSX-11 format, VAX-11 RSX returns a logical name if at all

possible.

The logical names LB and SP are defined systemwide by the VAX-11 RSX

startup command procedure and are accessible to all tasks on the system. If
either name matches the VAX/VMS device name being used, VAX-11 RSX
returns it to the RSX-11

task.

However, if the device name does not match either the LB or SP logical
names, there is no guarantee of finding a representation that can be used by
another task. Under these circumstances, VAX-11 RSX uses an algorithm that
grants this control to the system manager and to the user. VAX-11 RSX will
translate the $$n logical names to find one that matches the device. A $$n
name may be defined in any logical name table that is included in the logical name search list “LNMS$FILE_DEV” and, therefore, may be systemwide,
groupwide, jobwide, or process-local.

If no $$n name matches the device, VAX-11 RSX may use internal logical
names, such as $I or SY. These are not actual VAX/VMS logical names;

they are understood only by the AME, which assigns them. Therefore, these

names should not be passed to a different task. If passed to a native mode
task, the names will simply be meaningless. If passed to another RSX-11
~ task, they will be meaningful, but probably will not mean the same thing that
they mean to the task that passed them. For example, each task has a TIL.
However, each task will take TI to mean its own TI, even though the actual
terminals may be different.

When the AME assigns a logical unit number (LUN) to SY, it will attempt to
find a VAX/VMS logical name (such as LB or a $$n name) that refers to the
same device. If the AME finds the VAX/VMS logical name, then the RSX-11

pseudodevice name SY will have the RSX-11 physical device name LB, $$0,
~ or whichever name was found. If the process default disk is not LB or a $$n
name, the physical device name for SY is SY0.

If a $$n name is not defined for the process terminal, the physical name for
all terminal pseudodevices (TI, CL, CO) will be $10. If a $$n name is defined,
it can be passed to another task, provided that the $$n name is defined in
a table to which both tasks have access. If SYS$INPUT, SYS$COMMAND,
SYS$OUTPUT, or SYSSERROR are actually files rather than a terminal
device, $$n names cannot be used. (They cannot be shared with another task
in any case.)

3-15

- VAX-11 RSX Version 2.0 Release Notes

3.3.7

Restrictions for Indirect Using MCR on VAX—11 RSX
For Version 2.0, the Indirect Command Processor (Indirect) spawns a
command line to MCR and that command line is executed by a subprocess
with the MCR CLI. Command exit status and process-context information
changed by the command are moved to the main process when the command
completes in the subprocess. The following sections describe the restrictions
imposed by this implementation.

3.3.7.1

Logical Name Handling
The following list describes restrictions to logical name handling:
*

If you redefine SYSSOUTPUT in a command procedure, the new definition
remains in effect only through the execution of the command procedure.
When the command procedure exits, SYSSOUTPUT reverts to the original
definition specified for your process.

If you create process-local logical name tables in a command procedure,
the tables are created in the MCR subprocess but do not exist in your main
process when the command procedure exits.

3.3.7.2

If, during a command procedure, you create logical names in a processlocal table that you created, for example, a process-iocal table other
than LNM$PROCESS, the logical names are not available after the
~command procedure completes. However, if you create logical names
in the LNM$PROCESS table or any table that is not process-local, the
logical names are available after the command procedure exits.

Process Context
The following list describes restrictions to the process context:
*

Because MCR commands included in command procedures are actually
executed in a subprocess, the output of a SHOW PROCESS command in
a command procedure gives information on the subprocess. The process

name, Process Identification Number (PID), and the deductible quotas are
different from those of the main process in which Indirect is running. The
remaining information looks the same.

If you include the SET TERMINAL command in a command procedure,

you must specify the terminal name, even if the terminal used is your
own.

In a command procedure, the SET PROCESS/NAME command changes
only the name of the subprocess being used to execute the MCR
commands within the command procedure. When the command
procedure exits, your main process will have the same process name it
had when you invoked the command procedure.

If you include the following VAX/VMS-specific MCR commands from
an indirect command procedure, changes in context are lost when the
command procedure exits:

— SET COMMAND

— SET MESSAGE
— SET RMS_DEFAULT
— SET WORKING_SET

3-16

ion 2.0 Release Notes

All MCR commands included in an indirect command procedure are
executed within a subprocess. Most of the commands that alter process-

context information move that information to the main process to make it
available after the subprocess exits. The four commands shown do not do
this.

NOTE: If you allocate a device during a command procedure and do not mount
or deallocate the device during the procedure, the device is automatically
deallocated when the command procedure exits.

3.3.8 Differences Between VAX—11 RSX Indirect and RSX—11M—-PLUS
Indirect

|
The VAX-11 RSX Indirect Command Processor (Indirect) does not support

the following directives included in the RSX-11M-PLUS Version 3.0 Indirect
Command Processor:

FORM

XQT

.WAIT

The .FORM directive is ndt included because the FMS/RSX-11 driver is

not supported under VAX-11 RSX. Complexities in correctly handling the
asynchronous .XQT and .WAIT directives prevent their implementation in
VAX-11 RSX Indirect for Version 2.0.

A few Indirect directives have minimal effect in the VAX/VMS environment
and, as a result, they have been set to standard values that allow most
command files to operate as expected. These directives include the following:
e

IFACT/.JFNACT

IFINS/.IFNINS

IFLOA/.JFNLOA

.TESTPARTITION

The .TESTPARTITION directive can return information on RSX-11 regions,
but partitions do not exist in the VAX/VMS environment.

The .TESTDEVICE directive returns the device-independent characteristics
in the RSX-11 format, but the device-dependent characteristics it returns in
words 2 and 3 of the device characteristics words are a VAX/VMS devicedependent longword.

A few of the special symbols are also slightly different due to the constraints
and differences in the VAX/VMS environment. The following symbols,
which can have varying values for RSX-11M-PLUS, have constant values for
VAX-11 RSX:
e

<LOCAL>

3-17

VAX-11 RSX Version 2.0 Release Notes

<ZCLI>

<FMASK>

Refer to Section 5 of the VAX-11 RSX Compatibility Mode Reference Manual
for
more details on indirect command file processing.

3.4

Technical Changes to the VAX-11 RSX Documentation
This section describes technical changes affecting the VAX-11 RSX
documentation.
In the previous version of the VAX-11 RSX Installation Guide and Release
Notes, Section 3.2.11 displayed the following command lines inaccurately:

MCR:
> SET TERMINAL/NOLINE_EDITING

DCL:
$ SET TERMINAL/NOLINE_EDITING

3-18

RMS-11 Version 2.0 Release Notes
Sections 4.1 and 4.2 describe new or modified software features for and
restrictions to RMS-11 Version 2.0.

Building RMS—11 Applications on VAX-11RSX

The RMSLIB object library provided on VAX-11 RSX contains four versions
of the ROEXEC programming module. The default version (ROEXEC) of
this module is sufficient for most situations, however, you may wish to use

another version depending on your requirements. A list of the modules and
their features follows.
Module

ROEXEC

Function

Asynchronous/synchronous executive with RMS—11 software

that allows execution of a task when the task is transported to an
RSX-11 system.

ROEXSY

ROEXEV

Synchronous executive with RMS—11 software that allows execution

of a task when the task is transported to an RSX-11 system.

VAX-11RSX version only; Asynchronous/synchronous executive

optimized for size (no RMS—11 software is included). If the task is

transported to an RSX-11 system, ROEXEV will report ERSENV
(Feature not in selected RMS-11 environment) error messages on all
RMS-11 operations except $WAIT.

ROEXSV

VAX-11RSX version only; synchronous executive optimized for

size (no RMS—11 software included). If the task is transported to
an RSX—11 system, ROEXSV will report ERSENV (Feature not in
selected RMS—11 environment) error messages on all RMS-11
operations except SWAIT.

New Utilities Features
Enhancements have been made to the following RMS-11 utilities:
*

File Definition Utility (RMSCNYV)

File Back-Up Utility (RMSBCK)

File Restoration Utility (RMSDSP)

Indexed File Load Utility (RMSRST)

The following two subsections describe the enhancements made to these
utilities.

RMS-11 Version 2.0 Release Notes

4.2.1

RMSCNV
The RMSCNV Utility supports the RMS-11 /ER switch. This
switch
allows RMSCNYV to continue processing a file after an exceptio
n record is
encountered. This switch uses the following format:
/ER:filename

If the /ER switch is not specified, RMSCNV will terminate immediat

ely after

encountering the first exception record. An error message
indicating the type

of exception record will be returned.

If the /ER:filename switch is specified, RMSCNV will continue
processing the
file. If exception records are encountered, the exception records
will be placed
in that file.
.

4.2.2

RMSBCK, RMS DSP, and RMSRST
The RMSBCK, RMSDSP, and RMSRST Utilities include
enhancements to
increase performance and decrease task size. The following
switches have
been added to the RMSBCK Utility:
RMSBCK Switch
/NOQU

Function
Disables query mode

/NV

Creates a new version of the output file

/CD:date: A

Interprets the creation date as after (:A) the specified date,

in normal creation/revision date format

/CD:date:B
/RD:date: A

Interprets the creation date as before (:B) the specified
date, in normal creation/revision date format
Interprets the revision date as after (:A) the specified date,

in normal creation/revision date format

/RD:date:B

Interprets the revision date as before (:B) the specified
date, in normal creation/revision date format

The following switches have been added to the RMSDSP Utility:
RMSDSP Switch

Function

/BR

Briefly displays file attributes

/SU

Supersedes existing output file

The following switches have been added to the RMSRST
RMSRST Switch

Utility:

Function

/NOCV

Disables version radix conversion

/NV

Creates new version of output file

These utilities process file specifications that include the two
wildcard
characters, the asterisk (*) and percent sign (% ). These two
wildcard
characters can be used in any position within the directory,
file name,

type, and file version number fields.

4-2

file

RMS-11 Version 2.0 Release Notes

4.3

RMS-11 Software Restrictions
This section describes software restrictions to RMS-11 Version 2.0.
Suggestions for preventing or correcting problems are also included.

4.3.1

RMSDES
RMSDES has the following restrictions:

When the record size is greater than 1024 bytes, RMSDES selects
area bucket sizes that are not large enough. Consequently, the file is
successfully created, but is unusable. To bypass this restriction, specify the
bucket size with the correct value before creating the file.
*

When the number of duplicates exceeds the available bucket space,
RMSDES allocates more space than necessary. (See Chapter 6 of
the RSX-11M/M-PLUS RMS-11 User’s Guide for more information on
calculating this number.) This can be corrected in either of two ways:

e Use the RMSDES SET command to override this allocated space.
e

Reduce the number of duplicates to allow RMSDES to allocate space
more conservatively.

RMSDES never prompts for the length of a packed decimal key field. A
subsequent Create operation returns the error message “Invalid Key Field
Specified for File.” Therefore, if you select a packed decimal key you must
explicitly set the segment length.

RMSDES uses the system device as the default device on a GET FILE
DAT command. This default may be inconvenient if your login device is
not the system device, or if you have set your default device to something
other than the system device by issuing the DCL or MCR command
SET DEF. To bypass this restriction, supply the device name in the file
specification.

4.3.2

RMSIFL
RMSIFL has the following restrictions:

e RMSIFL aborts with a memory management violation when more than

one file is processed in the same RMSIFL session and the /DE switch is
used. A temporary solution to this problem is to invoke RMSIFL for each
file.

RMSIFL uses a sort algorithm that does not, when called upon to sort on
a key, preserve the first in, first out (FIFO) ordering of duplicates. For

alternate keys, this problem can be avoided by using RMSCNV. If your

input file is an indexed file or a file sorted on primary key, you may use

RMS IFL /NOSO provided that you wish only to order duplicates of the

primary key.

4-3

RMS-11 Version 2.0 Release Notes

4.3.3

RMSCNV and RMSIFL
RMSCNYV and RMSIFL have the following restrictions:
RMSCNV and RMSIFL ignore user-provided area extension quantities
when loading a file. Instead, they use values that are large enough to
reduce the number of file extensions.

4.4

Reporting RMS-11 Problems
Software Performance Reports (SPRs) allow you to report any software
problems directly to DIGITAL.
The following additional information should be submitted with SPRs
for
RMS-11 software:
Include the version number and patch level of the RMS-11 that you
are
using.

Indicate whether you are using a programming language to process
the file(s) and, if so, include the version number and patch level of the
language.
Include a Postmortem Dump and a map of the task involved, if RMS-11
aborts (or if some other task crashes and RMS-11 appears to be the cause).

Include a copy or copies of the file(s) involved, in RMSBCK format.

Include copies of the files that can cause the error, if the errors can be

reproduced. If you cannot reproduce the problem, include a
copy of the
corrupt file, if possible.

Include a description of the command line(s) or interactive session
that led
to the error (for RMS-11 utilities).

Include a listing of the actual error, if possible.

quipment Computer Users

Society (DECUS)

DECUS, the Digital Equipment Computer Users Society, is one of the largest
and most active user groups in the computer industry. It is a nonprofit
association, supported and administered by DIGITAL, but actively controlled
by members. DECUS headquarters, located in Marlborough, Massachusetts,
administers all international policies and activities. Members include
individuals who have purchased, leased, ordered, or used a DIGITAL
computer, or anyone who has an interest in DECUS. Membership is free and
voluntary.

A.1

DECUS Goals
The primary goals of DECUS are as follow:

To advance the art of computation through mutual education and

exchange of ideas and information

To establish standards and provide channels to facilitate the exchange of

computer programs

To provide feedback to DIGITAL regarding hardware and software

customer needs

To advance the effective use of DIGITAL computers, peripherals, and

software by promoting the interchange of information

To further these goals, DECUS serves its members by holding symposia

and maintaining a program library. An association newsletter, technical
newsletters, and books are also published. DECUS includes support for a
number of Special Interest Groups (SIGs).

A.2

DECUS Activities

Local, regional, and national DECUS organizations give members the
opportunity to meet other DIGITAL customers and employees in an informal

setting. From the monthly local meetings to the national symposia, members
can discuss their ideas, learn what others are doing, and give DIGITAL

valuable feedback for future product development.

Often, the national meetings in the various countries also provide the
stage for major new product announcements as well as a showplace for
developments in both hardware and software technology. At any meeting,
members might describe ideas and programs they have implemented or
fine-tuning that has been achieved for a particular application. Members
present papers, participate in panel discussions, lead workshops, and conduct
demonstrations for the benefit of other members.

Many of the technical papers and presentations from each symposium
are published as a book, the DECUS Proceedings. Copies of the DECUS
Proceedings are supplied to symposia attendees and can be purchased by

DECUS members. DECUS also publishes newsletters focusing on special
interests and a society newsletter.

A-1

The Digital Equipment Computer Users Society (DECUS)

DECUS has a Program Library, which contains over 1700 software
packages
that are written and submitted by users. A wide range of softwar
e is offered,
including languages, editors, numerical functions, utilities,
display routines,

games, and other types of application software. Library
catalogs are available

that contain program descriptions and ordering information.
The programs
are available for a nominal service charge that covers the
cost of reproduction
and media.

Many DECUS members derive additional benefits from joining
a DECUS
Special Interest Group (SIG). SIGs often meet as subsets of
regional and

national meetings. They may also meet on their own to
discuss their special

field, such as operating systems, languages, processors, and
applications.
There are at least 25 SIGs in the United States alone. Many
of the SIGs print

newsletters and disseminate valuable technical informa

tion to members.

To obtain a membership form for DECUS, contact a DIGITA
L sales

representative or the nearest DECUS chapter office.

A-2

Directives (cont'd.)

TLON$ ¢ 3-5

UMAPS$ ¢ 3-4

Distribution media® 1-1

Compatibilty mode tasks®3-13
CRF subprocess errors® 3-7

Error messages® 2-1 to 2-3, 3-8
Escape sequences®3-18

DCLe® 3-2
LINK/RSX11 command® 3-2
MCR command® 3-2

gig:::: : m:gcgSe3-8

lndirgfl ;Iommand Processor (Indirect)® 3-3, 3-16,

Digital Equipment Computer Users Society

directives ® 3-3

(DECUS)® A-1

logical name handling® 3-16

Directives
ACHNS » 3.5
ALUNS

,
process
a:ontaxt*3-1
3-16

3.6

symbols ® 3-3

.TESTPARTITION® 3-8

ATRG$*3-4

Installation procedure® 1-1 to 1-12

BOMS *3-9

‘

CLOG$*3-5

CLON$ *3-5

CRAWS$e3-4
CRRG$*3-4
DLOG$*3-5

DLON$ ¢ 3-5

Mcczr:nar;;nds*BJ

DTRG$ *3-4

keywords ® 3-2

ELAWS ¢ 3-4

ye r

parameters ® 3-2

ELP$
*3-6
|
EXST$3-8

ranularity ® 3-12

EXTK$ *3-13

granufartty
===
privilege requirements ® 3-12

FEAT$*3-5

RSX-11 compatibility ® 3-12

GDIR$ * 3-5

GMCX$+3-4

GPRT$ 3-8

GREG$*3-4

Memory management® 3-10

PRI

‘

MAP$3-4

RLOG$ *3-5
RLON$ ¢ 3-5

SDIR$ * 3-5

TLOG$ *3-5

$$N translation caching® 3-6
.

Named directories ® 3-9

NETGEN support® 3-8

Index-1

Index

Passing device names® 3-15

VAX/VMS utilities

PDP-11 Instruction Set Emulatore 3-1

Authorize Utility® 1-2
Backup Utility® 1-5
Install Utilitye 1-3

Network Control Program (NCP)e 1-6

System Generation Utilitye 1-3
Record Management Services (RMS-11)#4-1 to
4-4

utilities

BCKe4-2
CNVe4-2, 4-4
DESe*4-3
DSPe4-2
IFL®4-3

RSTe4-2
Region
attaching® 3-11

checkpointing® 3-11
creating® 3-10

deleting® 3-10
displaying information® 3-11

RSX-11 images®3-7
RSXUSR.EXE images®3-13 to 3-14

S
Save sets
RSX020.A* 1-1
RSX020.B* 1-1

RSX020.Ce 1-1

SYS$LOGIN® 3-10
SYSCOMMON system disks ® 3-6

Terminal drivere 3-7

Index—2

VAX-11 RSX
Installation Guide
and Release Notes
AA-CJ39B-TE

READE“' s

COM MENTS
|
o

Note: This form is for document comments only. DIGITAL will use comments

submitted‘on this form at the company’s discretion. If you require a written reply
and are eligible to receive one under Software Performance Report (SPR) service,
submit your comments on an SPR form.

Did you find this manual understandable, usable, and well organized? Please make suggestions for

improvement.

Did you find errors in this manual? If so, specify the error and the page number.

Please indicate the type of user/reader that you most nearly represent:
(] Assembly language programmer
[0 Higher-level language programmer

[0 Occasional programmer (experienced)
[J User with little programming experience
[0 Student programmer

(0 Other (please specify)

Name

Date

Organization

Street

City

State

Zip Code

or Country

No Postage
Necessary
if Mailed in the

United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.

POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD

NASHUA, NEW HAMPSHIRE 03062-2698

=—

Do Not Tear - Fold Here

mmmmmm

mmmm

Cut Along Dotted Line

—