Digital PDFs

AA-DO15D-TE

May 1982

84 pages

Original

5.9MB

Document:	VAX/VMS Release Notes Version 3.0
Order Number:	AA-DO15D-TE
Revision:	0
Pages:	84
Original Filename:

OCR Text

VAX/VMS
Release Notes
Version 3.0
Order No. AA-D015D-TE

SOTT14/Q

VAX/VMS
Release Notes
Version 3.0
Order No. AA-D015D-TE

May 1982
This document contains information not included elsewhere in the documentation set. Typically, this information covers software and/or documenlate in the
tation errors that were discovered or changes that were made

development cycle, plus hints concerning system installation and operation.
This document should be read before the system is installed or used.

REVISION/UPDATE INFORMATION:

This new document supersedes the

VAX/VMS Release Notes, Version 2.0
(Order No. AA-D015C-TE), the

VAX/ VMS Release Notes, Version 2.1
(Order No. AA-K055A-TE), the

VAX/VMS Release Notes, Version 2.2
(Order No. AA-K760A-TE), the

VAX/VMS Release Notes, Version 2.3
(Order No. AA-L286A-TE), and the

VAX/VMS Release Notes, Version 2.4
(Order No. AA-L836A-TE).

VAX/VMS Release Notes, Version 2.5
(Order No. AA-M439A-TE).

SOFTWARE VERSION:

VAX/VMS Version 3.0

digital equipment corporation • maynard,massachusetts

First Printing, August
Revised, February
Revised, March
Revised, May

1978
1979
1980
1982

The information in this document is subject to change without notice
and
should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility
for any errors that may appear in this document.
The software described in this document is furnished under a license
and may be used or copied only in accordance with the terms of such
license.
No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by Digital Equipment Corporation or its

affiliated companies.

1978,

1979,

1980, 1982 by Digital Equipment Corporation
All Rights Reserved.

Printed in U.S.A.

The postpaid READER'S COMMENTS form on the last page of this document
requests the user's critical evaluation to assist in preparing future

documentation.
The following are trademarks of Digital Equipment Corporation:

DEC

DEC/CMS
DECnet
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter

DIBOL
EduSystem

RSX
UNIBUS
VAX
VMS
VT

IAS

MASSBUS
PDP

PIMM

PDT
RSTS

SD'Dl

ZK2210

HOW TO ORDER ADDITIONAL DOCUMENTATION
In

Continental USA and Puerto Rico call

New Hampshire, Alaska, and Hawaii call 603-884-6660

Canada call

800-258-1710

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

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

DIRECT MAIL ORDERS (CANADA)
Digital Equipment of Canada Ltd.
940 Belfast Road

Ottawa, Ontario K1G 4C2
Attn:

A&SG Business Manager

DIRECT MAIL ORDERS (INTERNATIONAL)
Digital

Equipment Corporation

A&SG Business Manager
c/o Digital's local subsidiary or

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

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

2/tt-IS

CONTENTS

Page

CHAPTER

HOW TO INSTALL VAX/VMS VERSION 3.0

1.,1

IDENTIFYING THE VAX/VMS VERSION 3.0 KIT
VAX-11 OPTIONAL SOFTWARE PRODUCTS
.
.
BEFORE INSTALLING THE KIT
Minimum Real Memory Requirement
INSTALLING THE VAX/VMS VERSION 3.0 DISTRIBUTION
KIT
AUTOGEN PROCEDURE CONFIGURES VAX/VMS VERSION 3.0
AFTER INSTALLING THE VAX/VMS VERSION 3.0 KIT ...
Installing VAX-11 BLISS-32 Version 2.1 on
VAX/VMS Version 3.0

1. 2
1.,3
1..3. 1

1.,4

1.,5
1..6
1. 6. 1

CHAPTER

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

1-3
1-3
1-4

1-4

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS
VERSION 2.5

CI780 AND COMPUTER CLUSTERS
Hardware Components and Installation
2..1,.2
Software Components
2..1..2. 1
CI Port Driver
2..1,.2. 1.1
Configuration Poller
2..1,.2. 1.2
System Communications Services
2..1,.2. 2
DECnet Class Driver
2..1..3
SYSGEN Parameters
2..1..4
Nonpaged Pool Requirements
2..1,.5
Cluster Maintenance Considerations
2.,1.,5. 1
Power Failures
2..1.,5. 2
Port Hardware Errors
2.,1..5. 3
Path Recovery
2.,1.,5. 4
System Rebootstrap
2.,2
CHANGES TO THE DOCUMENTATION KIT
2.,3
COMMAND LANGUAGE AND SYSTEM MESSAGES
2.,3.,1
Assignment Statements
2. 3.,2
Substring Assignment Statements
2.,3.,3
Character String Comparison
2. 3.,4
Character String to Integer Conversion
2.,3. 5
String Operators
2. 3..6
COPY Command Modified
2. 3.,7
Incorrect LRL Computation in COPY and APPEND .
2. 3. 8
CTRL/T Implemented in DCL to Display Process
Statistics
2. 3. 9
DIFFERENCES Facility Rewritten in Native Mode
2. 3. 10
DUMP Facility Rewritten in Native Mode
2. 3. 11
EDIT/SUM Command Default
2. 3. 12
EXIT Command Modified to Exit with Status
.
.
2. 3. 13
HELP Command with Interactive Option
2. 3. 14
INQUIRE Command Modified
2. 3. 15
LIBRARY/RSX/LIST Command Modified
2. 3. 16
READ Command Enhanced
SEARCH Command
2. 3. 17
2,.1

2,.1..1

iii

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

2-8
2-8
2-8
2-9
2-9
2-9
2-9
2-9
2-9
2-9

CONTENTS
Page

2.3.18
2.3.19
2.3.20
2.3.21
2.3.22
2.3.23
2.3.24
2.3.25
2.3.26
2.3.27
2.3.28
2.3.29
2.3.30
2.3.31
2.3.31.1
2.3.31.2
2.3.31.3
2.3.32

2.3.33
2.3.34
2.3.35
2.3.36
2.3.37
2.3.38
2.3.39
2.3.40
2.4
2.4.1
2.4.2
2.5
2.5.1
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.5.11
2.5.12
2.5.13
2.5.14
2.5.15
2.5.16
2.5.17
2.5.18
2.5.19

2.5.20
2.5.21

2.5.22
2.5.23
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.6.6

SET UIC Command Modified
2-10
SHOW Command
2-10
New SHOW MEMORY Features
2-10
SPAWN Command
2-10
TYPE Command
2-11
USERS Replaced by SHOW USERS
2-11
Directory Protection
2-12
Execute Protection on Directories
2-12
File Protection Defaults Modified
2-12
SHOW PROCESS/CONTINUOUS Utility
2-12
Disabling CTRL/Y
2-13
Locking Passwords
2-13
LOGINOUT: Behavior Change
2-13
Image Restrictions
2-13
.
Privileged Images and Logical Names
2-13
Foreign Terminals and Privileged Images
2-13
CLIs Must Be Installed
2-13
Wild Cards Not Allowed in Library File
Specifications
2-14
Interrupting Privileged Images
2-14
Time Specifications
2-14
F$MODE Lexical Function Enhancement
2-14
New Lexical Functions
2-14
F$FILE_ATTRIBUTES Lexical Function Restriction 2-14
Symbol Substitution within Comments
2-15
ISAM File Support
2-15
VAX/VMS Message Manual Expanded
2-15
TEXT EDITORS AND FORMATTERS
2-15
EDT Replaces SOS as Default Editor
2-15
EDT Editor Manual
2-15
PROGRAM DEVELOPMENT TOOLS
2-17
VAX-11 SORT/MERGE User's Guide: New /STATISTICS
Qualifier
2-17
BACKUP Restriction: Restoring Directories . .
2-17
VAX-11 Utilities Reference Manual
2-18
Obsolete Images Removed
2-18
Command Definition Utility
2-19
Accounting Record Formats
2-19
Image Level Accounting
2-19
ANALYZE Command Notes
2-20
Synonym Directory Entries on System Disk . . .
2-20
AUTHORIZE Command String Length Restriction .
2-20
Null Passwords Implemented
2-20
AUTHORIZE String Delimiter Restrictions . . .
2-21
AUTHORIZE Qualifier /MAXACCTJOBS Unimplemented 2-21
INSTALL Restriction
2-21
Monitor Utility Notes
2-21
Disabling Dialup and Network Access
2-21
New Quota: ENQLM
2-21
Lock Management Services
2-22
Elimination of /SHARE=COPY and GSMATCH=NEVER
Linker Options
2-22
SYSGEN AUTOCONFIGURE Modifications
2-23
Restriction in Activating Privileged Shareable
Images
2-23
VAX-11 Linker Reference Manual
2-23
Watchpoint Implementation Restriction in DEBUG 2-24
SYSTEM SERVICES AND I/O
2-25
New System Status Codes
2-25
$GETMSG System Service Restrictions
2-26
$ENQ System Service Documentation Error
2-27
.
.
.
/NOMODEM Default for Terminals
2-27
2-27
/AUTOBAUD Default for Terminals
New Terminal Driver Error Code
2-27

....
.

CONTENTS
Page

2.6.7

2.6.8
2.6.9
2.6.10
2.6.11
2.6.12
2.6.13
2.6.14
2.7
2.7.1

2.7.2
2. 7. 3
2.,7. 4
2.,7. 5
2.,7. 6
2,,7..7
2.,8
2.,8.,1
2..8.,2
2.,8.,3
2.,8.,4

2..8.,5
2..8.,6
2,,8.,7
2,.8.,8
2..8..9
2,.8..10
2,.8..11

Read Outstanding Required for Remote Device
2 ~ 28
Communication
2-28
Change in Default Terminal Protection
2 ~ 28
Device Information
2-28
Modified
$CREPRC System Service
2-29
.
Names
Bit
.
Privilege
Service
System
$CREPRC
2-29
$SETPRI System Service
2-29
Interfaces
Undocumented System Service
2-29
VAX/VMS I/O User's Guide Documentation Change
2 ~ 29
RUN-TIME LIBRARY
Library
VAX-11 Common Run-Time Procedure
2 " 30
Modifications
String Descriptors Require Valid Class and
2 ~^1
Datatype
2-31
Enabling and Disabling CTRL/T
2-31
Restrictions
LIB$SPAWN
Changes to VAX-11 RTL Routines for BASIC String
2 ~31
Arithmetic
2-32
Unit
FORTRAN
for
Obtaining RAB Pointer
2-32
OLB
.
STARLET.
in
Included
Longer
No
Procedures
2-33
VAX-11 RECORD MANAGEMENT SERVICES (VAX-11 RMS) .
2-33
EDIT/FDL Error Message
2-33
Restriction
CONVERT/FAST_LOAD
2-33
EDIT/FDL Utility Treats Keys as Non-Segmented
2-34
EDIT/FDL Utility Ignores EDF$MAKEFDL
File
VAX/VMS
and
ANSI-"a" File Names
2 ~;? 4
Specifications
2-35
Relative Version Addressing
2-35
Uppercased
Now
Magnetic Tape Volume Identifiers
2-35
.
Behavior Change for RT-11 Tapes on VAX/VMS
MOUNT, Logical Volume Names, and Concealed
2-35
Devices
Length
Specification
VAX-11 RMS File Name
2 " 36
Modified
Control
VAX-11 RMS Modification of Carriage
•
•
Processing
\~\^
2-37
Files-11 ACP Modifications: Window Handling
Network
VAX-11 RMS Record Size Limits for
2-37
Operations
Network
for
Option
Limit
RMS
Key
VAX-11
2 ~ 38
Operations
VAX-11
Native-Mode
RMS-11 Utilities Replaced by
2 ~ 38
RMS Utilities
2-38
Prologue 3 Files Not Supported by RMS-11 .
2-38
File Version Handling Modified
2-39
COMPATIBILITY MODE
2-39
VAX-11/RSX-11M User's Guide
Compatibility Mode Support for Negative Version
2 * 40
Numbers
2-41
Modified
Software
Mode
VAX/VMS Compatibility
2-41
COM
STARTUP.
by
.
Installed
Longer
No
RSX AME
Rooted Directory Restriction in Compatibility
2 " 41
Mode
2 ~ 42
SYSTEM PROGRAMMING
" 42
2
TM03 FCO Required
Driver
Remote Terminals Support New Terminal
2 " 43
Features
2-43
Reassemble and Relink All Drivers
Device-Dependent IOSB Field by Disk Drivers:
2 " 44
New Behavior
All DDT and FDT Addresses Relocated by Driver
2-44
Loading Procedures
2-44
Driver
Multiple Modules in a Device
2-44
UNIBUS Memory on a UNIBUS Adapter

....

•

2.,8. 12
2.,8.,13

2.8.14

2.8.15
2. 8.16
2. 8.17
2. 9
2. 9.1
2..9.2
2.,9.3
2.,9.4
2.,9.5
2.,10
2.,10.1
2..10.2
2..10.3
2..10.4

2.10.5
2.10.6
2.10.7

CONTENTS
Page

2.10.8

Autoconf iguration Default Units and Unit
Delivery
2-45
2.10.9
ANALYZE/CRASHJDUMP (SDA) Help Text Not Updated 2-45
2.11
SYSTEM MANAGEMENT AND OPERATION
2-45
2.11.1
System Directories Have Moved
2-45
2.11.2
SYS$EXAMPLES Points to VAX/VMS Examples .
2-47
2.11.3
WSQUOTA and WSEXTENT for User Accounts
2-47
2.11.4
Bootstrapping with an Alternate STARTUP Command
Procedure
2-47
2.11.5
Installation on Multiple UNIBUS Systems
2-47
.
2.11.6
Librarian Shareable Image (LBRSHR) Increased .
2-47
2.11.7
VAX/VMS Version 3.0 SYSGEN Parameters
2-47
2.11.7.1
SYSGEN Parameter AWSMAX No Longer Needed 2-48
2.11.7.2
SYSGEN Parameter RMSJ)CMBIDX Changed
2-48
2.11.7.3
SYSGEN Parameter MPW_HILIM Changed
2-48
2.11.7.4
SYSGEN
Parameters
MPWJHLIMIT
and
MPW_WAITLIMIT
2-48
2.11.7.5
SYSGEN Parameters DIALTYPE and
TTYSCANDELTA Changed
2-48
2.11.8
SWAPFILE.SYS and PAGEFILE.SYS
2-48
2.11.9
Mount Verification Canceling
2-49
2.11.10
Mount and Dismount Notification Messages .
2-50
.
2.11.11
OPCOM Request Canceled
2-50
2.11.12
VAX-11 COBOL-74: System-wide Logical Name
Assignments
2-50
2.11.13
VAX-11 DIBOL Installation Restriction
2-51
2.11.14
Bootstrapping with a VAX/VMS Version 2.0 VMB .
2-51
2.11.15
Installing EDTCAI on VAX/VMS Version 2.5
Systems
2-51
2.12
NETWORKING
2-52
2.12.1
DECnet-VAX System Manager's Guide
2-52
2.12.2
DECnet-VAX Events Not Downward Compatible . .
2-52
2.12.3
DMP11 Default Parameter Settings
2-53
.

....
.

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

....

APPENDIX A

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

INDEX

CHAPTER

HOW TO INSTALL VAX/VMS VERSION 3.0

operating
VAX/VMS Version 3.0 is a major release of the JAX/VMS
kit to
distribution
3.0
Version
the
use
customers
Current
system.
New
system.
upgrade their VAX/VMS Version 2.5 system to a Version 3.0
3.0
Version
VAX/VMS
a
install
cSstomers use the distribution kit to
system.

necessary to install
This section is an overview of the information
The definitions of and
system.
3.0
upgrade to) a VAX/VMS Version
(or
upgrades for your
system
and
installations
procedures for system
provided
processor are found in the VAX-11 Software Installation
for
method
the
describes
guide
installation
The
with this kit.
system.
3.0
Version
a
to
system
2.5
upgrading a VAX/VMS Version

Gu^

1.1

IDENTIFYING THE VAX/VMS VERSION 3.0 KIT

distribution kits:
Current customers will receive one of the following

VAX-11/780

VAX-11/750

Magnetic Tape Upgrade

Magnetic Tape

STAND/ALONE Backup
Floppy Diskettes

STAND/ALONE Backup
TU58 Cartridges

Blank Floppy Diskette

Blank TU58 Cartridge

RK07 Upgrade

RK07 Upgrade
1

RK07 Disk Pack

Blank Floppy Diskettes

Blank TU58 Cartridges

kits:
New customers will receive one of the following distribution

Magnetic Tape
Installation

Magnetic Tape

STAND/ALONE Backup
Floppy Diskettes

Blank Floppy Diskette

VAX-11/730

VAX-11/750

VAX-11/780

RL02 Primary
Installation
Kit

Magnetic Tape

RL02 Disk Pack

STAND/ALONE Backup
TU58 Cartridges

Blank TU58
Cartridges

Blank TU58 Cartridge

1-1

HOW TO INSTALL VAX/VMS VERSION 3.0
RK07 Installation

RK07 Installation

RK07 Disk Pack

Blank Floppy Diskettes

Blank TU58 Cartridges
NOTE

DECnet-VAX customers will receive
a
floppy
diskette
TU58 cartridge
or
installation kit in addition to the
items listed above.
Note that an optional RL02 distribution kit is available
for
VAX-11/730 customers.
This optional kit contains one RL02 disk pack
and no console media.

1.2

VAX-11 OPTIONAL SOFTWARE PRODUCTS

This kit does not contain updates to any VAX-11 optional software
product.
Documentation for an optional software product is shipped
with that product.

1.3

BEFORE INSTALLING THE KIT

To
ensure successful
installation
distribution kit, do the following:
1.

Read the VAX-11
processor.

Software

the

VAX/VMS

Installation

Guide

Version

3.0

for

your

The software installation guide is the basic document for
understanding how to install, upgrade, or update a VAX/VMS
system.
2.

Read this document, the VAX/VMS Release Notes (Version 3.0).

This document contains necessary information to
ensure
successful
installation of (or upgrade to) a VAX/VMS Version
3.0 system.

1.3.1

Examine the System Identification Register
(SID).
See the
VAX-11 Software Installation Guide for your processor for
information describing how and why to examine the System
Identification Register.

If you are a
current customer, ensure that your current
system is a VAX/VMS Version 2.5 system. The VAX/VMS Version
3.0 distribution kit will only upgrade a VAX/VMS Version 2.5
system.

Minimum Real Memory Requirement

The minimum real memory requirement for VAX/VMS Version 3.0 is
512
kilobytes.
If you bootstrap either the system or standalone BACKUP on
a configuration with less memory than 512 kilobytes, the
results are
unpredictable and correct operation cannot be guaranteed.

1-2

HOW TO INSTALL VAX/VMS VERSION 3.0

1.4

INSTALLING THE VAX/VMS VERSION 3.0 DISTRIBUTION KIT

To install VAX/VMS Version 3.0, follow the instructions in the VAX- 11
Software Installation Guide that is provided with this kit. Current
new customers
Version 2.5 customers will perform a system upgrade;

will perform

system installation.

kit does not contain any
If your VAX/VMS Version 3.0 distribution
stand-alone back-up media
create your own after you install or
upgrade to VAX/VMS Version 3,0.
See the VAX- 11 Software Installation
Guide specific for your processor for information on creating your own
stand-alone back-up media.
,

NOTE

follow the
If you have
VAX-11/730,
a
system installation procedure, not the
The system
system upgrade procedure.
upgrade procedure will not execute on a
VAX-11/730 processor.

1.5

AUTOGEN PROCEDURE CONFIGURES VAX/VMS VERSION 3.0

VAX/VMS Version 3.0 provides an AUTOGEN procedure that configures and
tunes VAX/VMS for your hardware configuration.
This AUTOGEN procedure
does the following:
•

Creates the necessary system files (paging, swapping, and dump
files)

default list of installed images

•

Creates

•

Sets the SYSGEN
parameters
(system generation)
estimated for your hardware configuration.

This procedure replaces the VAX/VMS Version
files for estimating SYSGEN parameters.

2.0

use

best

nnUSER.PAR

When generating the system, the AUTOGEN procedure can recommend file
sizes for the paging, swapping or dump file that will not fit on the
system disk.
is
This can occur during an upgrade if the system disk
nearly full or has a very large paging file.
It may also occur during
an installation if the system disk is an RK07.
In
these cases, the
AUTOGEN procedure prints out the recommended size and does nothing to
the existing file.
The system manager should decide on the correct
action.

Certain layered products such as DBMS or DATATRIEVE will require
additional adjustments of some SYSGEN parameters. See the appropriate
layered products installation guides for more information.
The system manager can still

use
the
AUTOGEN procedure after the
system is operational.
If
you are generating a system disk on a
machine that is different from the target machine, which the disk will
eventually be run on, you must run the AUTOGEN procedure manually on
the target machine.
Refer to Chapter 12 of the VAX/VMS System
Management and Operations Guide for more information.

successfully bootstrap the system after manually using
AUTOGEN procedure, or after installing VAX/VMS Version 3.0,
attempt to bootstrap the system using default values for all SYSGEN
If you cannot

the

1-3

HOW TO INSTALL VAX/VMS VERSION 3.0
parameters. To do this, do a conversational bootstrap, as documented
your
software installation guide, and when SYSBOOT prompts, enter
the following commands:

SYSBOOT> USE DEFAULT
SYSBOOT> CONTINUE
This should allow bootstrapping on any hardware configuration.

1.6

AFTER INSTALLING THE VAX/VMS VERSION 3.0 KIT

New customers should install optional software
VAX/VMS Version 3.0 system has been installed.

products

after

the

After completing the system upgrade, current customers must:
1.

Reassemble any code using SYS$LIBRARY:LIB.MLB
user-written device drivers).

Relink any user-coded software linked with SYS$SYSTEM:SYS.STB
(for
example, user-written device drivers or user-written
system services)

Reinstall all optional software.

Update optional software that has been superseded.

(for

example,

NOTE
See the DECnet-VAX Software Installation
provided with this distribution
kit for procedures on how to
install a
DECnet-VAX
license to operate in a
multinode environment.
If
you are an
existing DECnet-VAX customer, you will
have received either a floppy diskette
or a TU58 cartridge installation kit.

Guide

1.6.1

Installing VAX-11 BLISS-32 Version 2.1 on VAX/VMS Version 3.0

LIB.REQ has been modified for Version 3.0 of VAX/VMS.
To
ensure the
successful
installation of VAX-11 BLISS-32 Version 2.1, perform the
three steps outlined below.
1.

Before installing the VAX-11 BLISS-32 Version 2.1 kit,
the command:
$

issue

APPEND/NEW SYS$LIBRARY: STARLET. REQ, LIB.REQ SYS$LIBRARY: LIB.REQ

Install the VAX-11 BLISS-32 Version 2.1 kit

Remove the concatenated version of LIB.REQ to
prevent
problems when attempting to install the VAX-11 BLISS-32
Version 3.0 kit by entering the following command line:
$

DELETE SYS$LIBRARY: LIB.REQ;

You do not need to perform the three
installing VAX-11 BLISS-32 Version
system.

1-4

steps

previously

listed

when

3.0 on your VAX/VMS Version 3.0

CHAPTER 2

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

Because VAX/VMS Version 3.0 is a major release of the VAX/VMS
operating system, there are many changes and new features. The
purpose of this section is to highlight some of them: changes and new
features are described completely in the software documentation set
for this release.

2.1

CI780 AND COMPUTER CLUSTERS

new high speed serial bus.
is
a
Interconnect)
The CI (Computer
VAX-11/780 processors interface to the CI through CI780 ports. The
bus supports up to sixteen nodes and is used to create clusters of
Each node contains an independent VAX/VMS
VAX-11/780 processors.
system.
Users on the individual systems in the cluster use DECnet-VAX
to communicate.

Hardware Components and Installation

2.1.1

The hardware components of a typical CI installation are listed below:
•

Two or more VAX-11/780 or VAX-11/782 processors

•

One CI780 port per system

•

A set of four connecting cables
length of 45 meters per cable)

•

One STAR coupler

per

port

(with

maximum

The CI780 port consists of the following components:
•

A card cage, to be installed in either
cabinet or a SBI expander cabinet

•

Optionally, a H1700A power supply

•

Two bulkhead connectors with coax cables

•

Four boards comprising the port hardware

the

VAX-11/780

main

Two DIP switches are located in the upper half of one of the boards.
These switches are used to set the port number (also known as the
station address) . Each port on a cluster must have a unique port
through 15. Unless otherwise indicated,
in
the range of
number
Both
field service should assign port numbers starting at zero.
switches must contain the same number.

2-1

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
There are four coax cables between each port and the STAR coupler.
These cables should have plastic labels on each end identifying the
cables as follows:
R
T
R
T

A - Receive path A
A - Transmit path A
B - Receive path B
B - Transmit path B

There
label.
In addition, the port number should be written on each
marked connection on both the bulkhead connectors and the STAR
is
a
coupler that corresponds to each cable.
a
STAR coupler is a passive connector box that contains
power
or
requires
no
It
network.
attentuator
and
splitter
transformer
operator intervention and should be located near the center of a
cluster.

The

Software Components

2.1.2

VAX/VMS support of the CI consists of the following two device
drivers:
(1) The CI port driver, which performs basic port operations
(SCS);
and a set of services called System Communications Services
and (2) A DECnet class driver, which implements a set of QIO functions
compatible with those implemented by the DMC11 and DMP11 device
drivers.

Its driver
2.1.2.1 CI Port Driver - The CI port is called device PA.
Device PA is a single unit device and an adapter on
is
PADRIVER.EXE.
Normally,
Only one CI780 adapter per system is permitted.
the SBI.
is configured with the SYSGEN>AUTOCONFIGURE ALL command in
the CI780
configured this
If it is not automatically
your SYSTARTUP.COM file.
way, use the following SYSGEN command to configure the device driver:

SYSGEN>CONNECT PAAO/ADAPTER=CIO
The CI port uses microcode in control store, which is not sustained
When VAX/VMS is bootstrapped, the bootstrap
failure.
over a power
from the console
pool
into nonpaged
microcode
CI
the
program loads
microcode file on the console block
(The
block storage device.
present, but the
CI
is
a
If
storage device is named CI780.BIN.)
the console block
on
file
microcode
the
find
cannot
bootstrap program
storage device, a warning message is printed on the console terminal
Therefore, if the microcode file
and the bootstrap program continues.
autoconf igured but remains
be
may
driver
is missing, the CI port
offline because the device initialization fails.
The microcode resides permanently in nonpaged pool to be accessible in
case the system recovers from a power failure.

When the PA driver is autoconf igured or connected, it initializes
CI780 by performing the following steps:

•

Builds port-specific data structures.

•

Loads the microcode into the port.

•

Starts the microprogram.

•

Starts the port driver configuration poller.

any of these steps fail, device PA remains offline.
2-2

the

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
sends
PADRIVER
2.1.2.1.1 Configuration Poller - Periodically
For
each node that responds,
datagrams to all sixteen nodes.
PADRIVER attempts to exchange several
including the local node,
datagrams containing information about the remote port and remote
is
made for the
an entry
system.
If the exchange is successful,
remote system in a configuration database maintained in nonpaged pool.
r

the
(path A and
path B)
Because the CI has redundant paths
configuration poller makes one pass probing all sixteen nodes over
so
and
on,
path A, then makes a pass later probing over path B,
that
is
the only VMS software
paths.
The poller
alternating
explicitly selects one path or the other. Normally, the port selects
a path that is usable and not currently busy with traffic.
,

The port keeps an internal record of paths for each possible node to
which the last transmission has succeeded and paths for which the last
transmission failed. When automatically selecting a path, the port
However, the poller directs an
will not try a path marked failed.
explicit path selection and the port will try the selected path even
If the path succeeds, the port
is
if
it
currently marked failed.
revises its record to show the path usable and that path can be used
in
automatic path selection. Thus, the configuration poller restores
formerly unusable paths.

2.1.2.1.2 System Communications Services - PADRIVER supports no QIO
PADRIVER contains a collection of subroutines
functions.
Instead,
that the DECnet class driver can use called System Communications
SCS includes the services listed below:
Services (SCS)
.

•

Allows DECnet class drivers on different systems to
close fork-process to fork-process connections.

•

(Datagrams are packets of
Sends datagrams over a connection.
information addressed to a specific port without quaranteed
delivery.)

•

Queues buffers in which datagrams are received.

•

Gives the class driver notification of received datagrams.

•

Gives the class driver notification
interfork process connection.

failure

open

and

the

is
a
driver
2.1.2.2 DECnet Class Driver - The DECnet-CI class
software-only driver named CNDRIVER.EXE that serves as the interface
between the QIO/IRP oriented interface of the NETDRIVER and the SCS
interface of the port driver. Use the following SYSGEN command to
the
to
(You can add this command
load CNDRIVER.EXE into the system.
installation's SYS $MANAGER: SYSTARTUP.COM file.)

SYSGEN>CONNECT CNAO/NOADAPTER
When the port driver is up and running, and CNDRIVER is loaded, you
can add the CI to the network with the following commands using the
NCP facility:

NCP>SET LINE CI-0 [REC BUF x] STA ON
NCP>SET CIRC Cl-O.y TRIB y COST 1 STA ON
In the above command lines, the value for "x" is the number of receive
to be allocated from the LRP list for each circuit on the CI.

buffers

2-3

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
(The NCP default per line is four, but you should use six for the CI).
for "y" is the port number (station address) of the remote

The value
node.

network is
To avoid reentering the above SET commands every time the
This
SET,
DEFINE
for
substituting
restarted, enter the same commands,
data
permanent
network's
the
into
circuit
and
will put the CI line
base.

SYSGEN Parameters

2.1.3

Some of the parameters that control CI and SCS behavior are listed
For more detailed information about all parameters, see the
below.
VAX/VMS System Management and Operations Guide .

SCSSYSTEMID

A number in the range of 1 through 255 which
It
DECnet node number of the system.
is
the
must be unique for each node.

PAPOLLINTERVAL

The number of seconds between passes through
Ten to twenty
configuration poller.
the
seconds is adequate for most applications, but
It
the value can be changed dynamically.
should be set short enough to recognize a new
system on the cluster within a reasonable
time, but not so short that excessive CPU time
is used polling.

PASTIMOUT
PASTRETRY

initial exchange of
retries on the
Control
datagrams between two nodes. PASTIMOUT is the
retries and
between
seconds
number
of
retries
of
number
total
the
is
PASTRETRY
The product of PASTIMOUT*PASTRETRY
attempted.
to
equal
or
than
greater
must
be
PAPOLLINTERVAL or configuration pollers may be
If
systems.
new
recognize
unable
to
increase
increased,
is
PAPOLLINTERVAL
PASTIMOUT by the same factor.

Nonpaged Pool Requirements

2.1.4

configuration contains a CI at system installation time, the
AUTOGEN system generation procedure sets approximate requirements for
then
running system,
If a CI is added to an already
nonpaged pool.
either use the AUTOGEN procedure manually or the SYSGEN utility to add
requirements
DECnet nonpaged pool
extra nonpaged pool to the system.
and NCP
SYSGEN/SCS
for a CI cluster with three nodes using the default
below:
parameter settings are listed
If your

SYSGEN Parameter

Parameter Settings

NONPAGEDYN

35 kilobytes

LRPCOUNT

IRPCOUNT

SRPCOUNT

2-4

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.1.5

Cluster Maintenance Considerations

The following sections discuss power failures, port
path recovery, and system rebootstrap.

hardware

errors,

the
power,
2.1.5.1 Power Failures - When the CI780 port loses
microcode must be reloaded and the device must be reinitialized. When
the cluster configuration
the system recovers from a power failure,
database is cleared and any DECnet class driver connections to remote
systems are broken. The configuration poller then reidentifies remote
systems allowing connections to be reestablished. This process may
take as long as several poller intervals.

2.1.5.2 Port Hardware Errors - The CI780 port has retry logic to
However, there are
recover
from many types of transmission errors.
several kinds of port errors (such as parity error) that the port does
In these cases, the port driver employs
recover from.
not try to
limited retries. On each retry it reinitializes the port as if a port
If no retries are left, the port is shut
power failure had occurred.
activity is possible on the CI
further
offline
and
no
and
set
down
port
each
Following
system.
the
rebootstrapping
without
reinitialization, a small amount of nonpaged pool may be permanently
lost.
Other systems in the cluster should continue normally except
that they must reestablish connections to the failed port following
reinitialization and will be unable to reestablish
each successful
connections following the final shutdown of the failed port.

2.1.5.3 Path Recovery - If one of the redundant CI paths is removed
activity will continue over the
star coupler,
from the port or
remaining path. When the path is reattached, the port continues to
assume that path is unusable until it is selected by the configuration
seconds.
This action can take up to 2*PAP0LLINTERVAL
poller.
Therefore, do not detach the remaining usable path for at least that
period of time.
removed from the
are
If both paths are removed, all remote systems
configuration database and associated SCS connections are broken.
When
Otherwise, all systems in the cluster continue to run normally.
one path is reinstated, the poller rebuilds the configuration database
and connections may be reestablished.

2.1.5.4 System Rebootstrap - A cluster of systems knows when one of
its systems or ports shuts down because either:
(1) traffic addressed
it
to it will not be delivered, or (2) configuration pollers see that
As the other systems in the cluster notice the
longer responds.
no
failed system from their
shut down system or port, they remove the
configuration databases and break DECnet class driver connections.
Their configuration
The other systems continue to
run normally.
pollers detect when a system is rebootstrapped and connections can be
reestablished.

2.2

CHANGES TO THE DOCUMENTATION KIT

new manuals and
The VAX/VMS V3.0 Documentation Kit includes several
revisions to current manuals. To find the information you need, read

2-5

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
the VAX-11 Information Directory and Index that is provided with this
kit.
information directory describes the intended audience and
TFHe
features of each manual in the documentation kit and now contains a
master index to the entire documentation set. The new master index is
a merger of the indexes from each of the individual books.

Each manual that has been revised for VAX/VMS Version 3.0 contains a
summary of technical changes. The purpose of these summaries is to
point you quickly to portions of the documentation that were changed
or added to describe new Version 3.0 features.

General
information about
following documentation:

2.3

Version

VAX/VMS

3.0

•

VAX- 11 Information Directory and Index

•

VAX/VMS Summary Description and Glossary

•

VAX/VMS Primer

•

VAX/VMS Release Notes

found

the

COMMAND LANGUAGE AND SYSTEM MESSAGES

the
The following sections contain notes on changes and additions to
system message facility.
(DCL)
and
Language
DIGITAL
Command
Documentation describing DCL and system messages is found in the
following manuals:

2,3.1

•

VAX/VMS Command Language User's Guide

•

VAX/VMS Guide to Using Command Procedures

•

VAX/VMS System Messages and Recovery Procedures Manual

Assignment Statements

You can now use the - and == assignment operators to define both
Note that this generalization of the
symbols.
integer
string and
assignment operator does not apply to assignment operators used for
For example, the following line will generate
substring substitution.
an error:
A[4,8] = "B"
the VAX/VMS
information.

See

2.3.2

Guide

Using

Command

Procedures

for

Substring Assignment Statements

The bitfield assignment operator has been modified for Version 3.0 of
VAX/VMS in an effort to be compatible with previous releases. The =
and == bitfield assignment operators no longer insert an integer value
into
a string.
If the previous value type into which the bitfield is
being inserted is integer, then the value resulting from the insertion
If the previous value type is character string,
will be an integer.
or if the symbol was previously undefined, the resulting type will be,
as in previous versions, a character string.

2-6

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
This change could affect command procedures that contain the following
command sequences
$

X =

X[0,32]=28
Y = »F$CVUI(0, 16, X)

Previous type is integer
Value is now integer 28
Extract the first 16 bits of X

In previous Versions of VAX/VMS, X would have had a string value,
and
this code segment would
In Version
assign Y the decimal value 28.
function
Since the F$CVUI lexical
integer symbol.
3,0, X is an
operates on strings, this means that DCL must convert the integer
value of X to a character string value before performing the lexical
function.
This results in the integer 28, which has a hexadecimal
representation of 0000001C, being converted to the character string
"28",
Thus, when the
which has a hexadecimal representation of 3832.
extraction is performed, it yields a decimal integer result of 14386,
or hexadecimal 3832.

Character String Comparison

2.3.3

DCL no longer disregards trailing blanks when performing string
comparisons.
When comparing strings of unequal length, DCL inserts
null characters
the
(binary 0)
at
the
end of
shorter string.
Therefore, the expression "ABC" .EQS. "ABC " is considered false by
DCL.

Character String to Integer Conversion

2.3.4

Numeric character strings are converted to their integer equivalents.
Character strings beginning with the letters T,t,Y, or y are converted
to integer 1.
All other character strings are converted to integer 0.
Integers are converted to
decimal equivalents.

character

the VAX/VMS
information.

See

2.3.5

Guide

Command

strings

Procedures

using

for

their

ASCII

additional

String Operators

Two new string operators are now available with VAX/VMS Version 3.0.
See
the VAX/VMS Guide
Using Command Procedures for information
to
(-)
string
reduction
about these new string concatenation
and
(+)

operators.
Note that because the "+" and "-" operators now have two different
meanings within expressions, depending on the types of their operands,
some expressions will evaluate differently in Version 3.0 than they
For
example, consider the
did
in
previous versions of VAX/VMS.
following three command lines.
$
$

:= 3

b := 4
$ sum = a+b
In previous versions, sum is the arithmetic sum of 3 and 4,
which is
In Version 3.0, sum is the result of concatenating the strings "3"

and "4V

2-7

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
COPY Command Modified

2.3.6

is
The DCL command COPY has changed how an output file version number
defaulted when a version number is not specified for the output file
(There is no change if the input
and is specified for the input file.
file version number is defaulted or is a wild card character.)

COPY would always
In the past when the following command was given,
create a file, NAME2.TY2 in [DIR2] with a version number one higher
than the highest existing version number for NAME2.TY2:
,

COPY [DIR1]NAME1.TY1;V [DIR2]NAME2.TY2

input
file version
COPY now tries to create NAME2.TY2;V, using the
If this file already exists, an error
number for the output file.
message is issued and the copy fails.

2.3.7

Incorrect LRL Computation in COPY and APPEND

When you use the DCL command COPY or APPEND to concatenate more than
files
into a single output file, the longest record length (LRL)
two
The LRL of the output file
field of the output file may be incorrect.
input file, depending on
last
first
or
the
is set to the LRL of either
if
an
The LRL of the output file will be incorrect
which is larger.
input
file other than the first or last file contains the largest LRL
of all the input files.
To avoid this problem, use the DCL command APPEND to
input files one at a time.

2.3.8

concatenate

the

CTRL/T Implemented in DCL to Display Process Statistics

Pressing CTRL/T during an interactive session in which CTRL/T is
enabled will cause DCL to momentarily interrupt execution of the
current command or image and display a single line of process
To enable CTRL/T handling you must use the SET CONTROLS
statistics.
command.
(See the VAX/VMS Command Language User's Guide for details.)
To
enable or disable CTRL/T processing by DCL during the execution of
routines
RTL
VAX-11
new
the
use
program
user-written
a
LIB$DISABLE CTRL and LIB$ENABLE CTRL.

2.3.9

DIFFERENCES Facility Rewritten in Native Mode

The previously
DIFFERENCES has been rewritten in native mode.
inplemented output formats have been modified and a new side-by-side
output format has been added. Also, the facility now exits with a
severity status that can be tested to determine the results of the
facility's execution.

2.3.10

DUMP Facility Rewritten in Native Mode

DUMP has been rewritten in native mode.
of the options have been modified.

2-8

The output formats

and

some

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.3.11

EDIT/SUM Command Default

The VAX/VMS Command Language User's Guide and the VAX- 11 Utilities
Reference Manual state that the default for the EDIT/SUM command is
/OUTPUT.
This is incorrect, the default is /NOOUTPUT.
You must use
/OUTPUT if you want an updated copy of the input file.

2.3.12

EXIT Command Modified to Exit with Status

The EXIT command now exits with status
from all command levels,
including command level 0, (for example, interactive and batch command
levels).
Therefore, batch jobs in which several command procedures
are being executed but in which one terminates with an error status,
will terminate at the point of the error.

2.3.13

HELP Command with Interactive Option

The DCL command HELP now has an interactive option that allows you to
move forward and backward through the help file in a tree-structured
fashion.
You can also specify that HELP paginate
its output.
In
addition, you can use logical names to specify your own set of default
HELP libraries.

The /[NO]LIBLIST qualifier for the DCL command HELP is not implemented
for VAX/VMS Version 3.0.
By default, HELP assumes that /LIBLIST has
been specified.

2.3.14

INQUIRE Command Modified

The INQUIRE command now enforces the restriction that a prompt string
containing embedded blanks must be enclosed in quotation marks.

2.3.15

LIBRARY/RSX/LIST Command Modified

For VAX/VMS Version 3.0, the following command is slightly modified:

LIBRARY/RSX/LIST=file-spec library-name
For Version 2.0 of VAX/VMS,
file was written
the
in
the current
default directory. Now, the file is written in the same directory as
the library.
Therefore you must explicitly specify the device and
directory for the listing file.

2.3.16

READ Command Enhanced

The maximum size of a readable record
characters to 1024 characters.

2.3.17

has

been

increased

from

132

SEARCH Command

The DCL command SEARCH allows you to search
for one or more strings.

2-9

file, or group of files,

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.3.18

SET UIC Command Modified

The DCL command SET UIC now affects only the user identification code
(UIC) of your process.
It does not modify your default directory.

2.3.19

SHOW Command

The output format of several
SHOW displays
several new displays have been added.

2.3.20

has

been

modified

and

New SHOW MEMORY Features

The SHOW MEMORY command displays additional
information and accepts
qualifiers.
Enter
the
following command for information about each
qualifier:

HELP SHOW MEMORY QUALIFIERS
The details of the output
Language User's Guide .

2.3.21

are

described

the

VAX/VMS

Command

SPAWN Command

The following restrictions apply both to the DCL command SPAWN and the
LIB$SPAWN run-time library routine.
•

The use of the DCL command SPAWN within command procedures

unsupported.
•

You must manage input or output streams shared by multiple
processes.
For example,
you must manage the terminal while
the
DCL command SPAWN/NOWAIT DIRECTORY,
issued
at
an
interactive command level,
is
sending its output to the
terminal.

•

The SPAWN command does not manage terminal
characteristics.
For
example,
SPAWN does not save and restore hardware
characteristics such as VT100 terminal scrolling regions, or
software characteristics such as terminal width.

•

You cannot spawn a subprocess that receives its input from the
same terminal as its parent if the parent process has an
associated terminal mailbox.

•

CTRL/C and out-of-band ASTs established in the parent process
are not disabled by a SPAWN command.
Therefore, appropriate
ASTs will be delivered to the parent process at subprocess
completion time, if the appropriate asynchronous condition was
raised in the subprocess.

•

You cannot use per-process concealed logical names when
specifying file specifications for the input or output record
streams.

•

SPAWN will not copy symbols containing
characters to a spawned subprocess.

2-10

than

245

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

interpreter
A spawned subprocess uses the default command
spawn a
you
If
record.
file
authorization
your
in
specified
subprocess with a default CLI other than DCL, you will receive
unpredictable results.
More than one process will simultaneously attempt to use the
input or output stream when several processes share the
same
same stream and you terminate a subprocess to which you are
not currently attached (or a process that is not spawned from
the process to which you are currently attached).

Unpredictable behavior will result if the following two
(1) A SPAWN command line begins with an
conditions are met:
supplied for the last
is
A value
and
(2)
at sign (@)
qualifier to the SPAWN command. An example of a command line
meeting these two criteria is shown below:
,

SPAWN/PROC=TESTSUB

@ [TEST. OBJ]

use /WAIT or /NOWAIT
To avoid this problem,
for example:
command,
qualifier to the SPAWN
$

SPAWN/PROC=TESTSUB/WAIT

last

@ [TEST. OBJ]

The following behavior of the SPAWN command is not documented
VAX/VMS Command Language User's Guide .
•

the

command for the spawned subprocess to
a
specify an input stream, SPAWN uses the
not
do
but
execute,
as the default input stream.
null device, NL:
If you

specify

•

suppresses
qualifier
/NOLOG
informational SPAWN messages, but
requests.

The

the
does

all
of
output
not affect ATTACH

See the descriptions of the DCL commands SPAWN and ATTACH
VAX/VMS Command Language User's Guide for more information.

2.3.22

the

TYPE Command

enable CTRL/O to suspend
The DCL command TYPE has been modified to
being typed. When
currently
rather than terminating the file
output,
the file^ while
of
display
the
halts
CTRL/0
a file is being displayed,
A
the file.
through
read
to
continues
software
command
TYPE
the
the
at
resume
to
subsequent CTRL/O causes the display of the file
This change enables you to "skip
location the software is reading.
file.
long
a
ahead" when displaying
suspend the display and do not reenter CTRL/O
before the software reaches the end of the file, the next file
requested (if any) is displayed.
If you enter CTRL/O to

2.3.23

USERS Replaced by SHOW USERS

is
USERS, which was an unsupported utility until VAX/VMS Version 3.0,
now supported as SHOW USERS. Note that, if SHOW is installed with
Otherwise,
SETPRV, then SHOW USERS will show all users on the system.
users
other
have
to
privilege
WORLD
or
GROUP
you must have either
displayed.

2-11

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.3.24

Directory Protection

It is now impossible
delete a directory that contains files.
to
Attempting to delete such a directory results in an SS$_DIRNOTEMPTY
error status. No privilege overrides this protection.
In
order to
delete the directory, you must either remove or delete all the files
listed in it.
Or, you must use the SET FILE/NODIRECTORY command
to
change the directory file from a directory to a file.

2.3.25

Execute Protection on Directories

VAX/VMS Version 3.0 implements execute access as a restricted
read permission.
When you are granted execute access, but
access, to a directory, you may not do wild card operations
directory.
All
the files may not be listed, but a specific
be accessed by name.

2.3.26

form of
not read
on that
file may

File Protection Defaults Modified

For VAX/VMS Version 3.0, file protection defaults have been modified
become more restrictive. When you use the DCL command INITIALIZE,
the system files created on the volume by default receive the
to

following protection:
The Master File Directory (MFD):

All others:

S:RWED, 0:RWED, G:RE, W:E

S:RWED, 0:RWED, G:RE, W:N0 ACCESS

The SYSGEN parameter RMS_FILEPROT has been added to
set
the
initial
process default file protection for all users. This value is normally
set to the following:

S:RWED, 0:RWED, G:RE, W:N0 ACCESS

You may override the setting of RMS_FILEPROT by including a SET
PROTECTION
/DEFAULT
command in your L0GIN.COM file.
However,
RMS_FILEPROT always determines the protection assigned to batch and
network log files since these files are created before your L0GIN.COM
is executed.

When processes are created, the current default file protection of the
creator is given to the new process. For example, processes created
with the SPAWN or RUN commands will run with the current default file
protection of the creator.

2.3.27

SHOW PROCESS/CONTINUOUS Utility

INFO, which was an unsupported utility before VAX/VMS Version 3.0,
is
now supported as SHOW PROCESS/CONTINUOUS. Note the following behavior
changes:
•

Previously, INFO could be invoked without GROUP or WORLD
privileges;
this is no longer true. When you enter the DCL
command SHOW PROCESS/CONTINUOUS, you must have either GROUP or
WORLD privilege to display information about a process other
than the current process
(or
subprocesses of the current
process) .

2-12

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

you
if
Since process names are implicitly qualified by UIC,
want to view a process with a group UIC different from that of
process
the
specify
UIC,
group
the current process
the
using
name
process
the
of
instead
(PID)
identification
following format:
$

2.3.28

SHOW PROCESS/CONTINUOUS/ID=process-id

Disabling CTRL/Y

To disable CTRL/Y, you must set both the CAPTIVE flag and the
flag in the UAF record.

2.3.29

DISCTLY

Locking Passwords

To lock a password, you must set the LOCKPWD flag in the UAF record.

2.3.30

LOGINOUT: Behavior Change

LOGINOUT has been modified with Version 3.0 of
The behavior of
you created a detached
if
Before VAX/VMS Version 3.0,
VAX/VMS.
input
lines of the
two
first
the
LOGINOUT,
running
process from DCL,
Now, when you
file (DET.COM) had to contain a user name and password.
create a detached process, running LOGINOUT, you no longer need to
specify a user name and password in the input file (DET.COM). Note
that the process login command file will not be invoked although the
system-wide command file will be invoked.

2.3.31

Image Restrictions

The following three subsections document
for Version 3.0 of VAX/VMS.

several

image

restrictions

restrictions
2.3.31.1 Privileged Images and Logical Names - Several
shareable images
All
executing privileged images.
when
exist
In addition, any logical
referenced by such images must be installed.
the process or group
either
in
images
name redirection for these
ignored.
is
table
logical name

2.3.31.2 Foreign Terminals and Privileged Images - An image that is
mapped to provide support for foreign terminals must be installed if
it is used with MAIL or SHOW or any other image that is installed with
privilege.

2.3.31.3 CLIs Must Be Installed - Because the LOGINOUT image that
these
installed with privilege,
is
interpreters
command
maps
CLIs.
all
restrictions (shown below) apply to

2-13

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

All command interpreters must be installed.

•

Any logical name redirection that does not appear
in
the
system name table is ignored when the CLI is mapped into PI
space.

2.3.32

Wild Cards Not Allowed in Library File Specifications

Wild card characters are not allowed in library file specifications
with Version 3.0 of VAX/VMS.
Therefore, disregard all documentation
in the VAX/VMS Command Language User s Guide that mentions the use
of
wild card characters with library file specifications in the DCL
command LIBRARY.
1

2.3.33

Interrupting Privileged Images

DCL no longer runs down privileged images that have been interrupted
with a CTRL/Y.
However, after interrupting a privileged image, you
can make DCL run down your image by issuing any DCL command other than
CONTINUE, SPAWN, or ATTACH.

2.3.34

Time Specifications

Various DCL commands use time qualifiers
(for
example, /BEFORE and
/SINCE)
that previously required the specification of an absolute
time.
Now these qualifiers will accept an absolute time, delta time,
or
a
combination of absolute and delta time. For example, the DCL
command $ PRINT/AFTER="+5" FILE specifies that FILE be printed 5 hours
from the current time.
See Chapter 5 of the VAX/VMS Command Language
User's Guide for more information.

2.3.35

F$MODE Lexical Function Enhancement

The F$MODE lexical function has been enhanced to
return the string
"NETWORK"
for network jobs, in addition to "BATCH" and "INTERACTIVE".
See Chapter 5 of the VAX/VMS Guide to Using Command Procedures
for
more information.

2.3.36

New Lexical Functions

The following new lexical functions have been added
DCL.
to
See
Chapter 5 of the VAX/VMS Guide to Using Command Procedures for more
information.

F$CVTIME
F$GETDVI
F$INTEGER
F$PRIVILEGE
F$STRING

2.3.37

F$FA0
F$GETJPI
F$PARSE
F$SEARCH

F$FILE_ATTRIBUTES
F$GETSYI
F$PID
F$SETPRIV

F$FILE_ATTRIBUTES Lexical Function Restriction

The F$FILE_ATTRIBUTES lexical function
information about relative files.

2-14

cannot

used

retrieve

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

2.3.38

Symbol Substitution within Comments

symbol substitution was performed
In previous versions of VAX/VMS,
within comments whenever a symbol was preceded by an apostrophe.
(This was an undocumented feature of DCL.) For VAX/VMS Version 3.0,
substitution within comments is no longer
this kind of symbol
lexical function F$VERIFY().
the
with
except
supported

2.3.39

ISAM File Support

allow random
The DCL commands OPEN and READ have been enhanced to
See the descriptions of
indexed sequential (ISAM) files.
access to
these commands in the VAX /VMS Command Language User's Guide and
Chapter 8 of the VAX/VMS Guide to Using Command Procedures for more
information.

2.3.40

VAX/VMS Message Manual Expanded

The VAX/VMS System Messages and Recovery Procedures Manual is expanded
with Version 3.0 of VAX/VMS to include documentation for messages
See Table 1 of the VAX/VMS System
generated by numerous facilities.
for a complete list of these
Manual
Messages and Recovery Procedures
facilities.

2.4

TEXT EDITORS AND FORMATTERS

the
The following sections contain notes on changes and additions to
3.0.
Version
VAX/VMS
by
supported
formatters
and
editors
text
Documentation describing text editors and formatters is found in the

following manuals:
•

VAX- 11 SOS Text Editing Reference Manual

•

EDT Editor Manual

•

VAX-11 DIGITAL Standard Runoff User's Guide (new manual)

EDT Replaces SOS as Default Editor

2.4.1

EDT is now the default editor invoked for VAX/VMS Version 3.0 when you
invoke the SOS editor, specify
To
EDIT.
DCL command
the
enter
EDIT/SOS.

EDT Editor Manual

2.4.2

The following information, problems, and restrictions apply to EDT for
VAX/VMS Version 3.0 (this information is not VTlOO-specif ic)
•

CTRL/C Restrictions:
-

end of a
the
If you press CTRL/C when inserting text at
line
in keypad mode, the CTRL/C echoes as "C, interrupting
screen, press CTRL/W
To refresh the
the screen display.

after pressing CTRL/C.

2-15

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

EDT may leave
truncated output file because the operation is writing
the file.
avoid
(CTRL/C aborts the current operation.) To
this result, do not type CTRL/C during the EXIT command.
If you press CTRL/C during the EXIT command,

If you press CTRL/C to abort an operation,

a
example,
for
EDT's journal
file becomes invalid, making
search,
subsequent recovery impossible. Therefore, you should type
EXIT and reinvoke EDT to continue editing the file.

long

•

The following command line writes the current select range
a file:

WRITE file-spec SELECT
•

Hard-copy keypad mode is not described in the manual.

•

TRUNCATE,
of
and
the
In hard-copy keypad mode, the setting
reflected in the text
values of SHL and SHR,
are not
displayed.

•

TYPE)
that
After entering a line mode command (for example,
takes a multiline range (for example, 5:10), the first line of
the range becomes the current line.
For example:

TYPE 5:10

After the lines are displayed, line 5 will be the current
line.
If
you specify ALL instead of a line range, the first
line of the buffer becomes the current line.
•

When you edit a file using a directory to which you do not
have write access, specify that the output and journal files
are to be written to a directory to which you have write
access.

•

Use the range specifier ".", which is defined
buffer, instead of the range specifier LAST.

•

When you use the RESEQUENCE line mode command from keypad mode
(using
<G0LD>
the
informational message that the
7),
RESEQUENCE command prints causes the screen to scroll.
Press
CTRL/W to refresh the screen.

•

To enable the word-wrapping feature of the EDT editor, set the
screen to at least two characters wider than the word-wrapping
point you want.
issue the
For example, on a VT52 you can
commands SET SCREEN 82 and WRAP 80, or SET SCREEN 80 and WRAP
78.

•

EDT runs on VT52,
VT102,
VT132,
VT101,
VT100,
and VT125
terminals.
EDT treats the VT101, VT102, VT132 and the VT125
as VT100 terminals.
Advanced
If you have a VT100 without the
Video Option (AVO) or if you have a VT101:
(1) do not use SET
SCREEN 132 and (2) set the cursor to "block".
EDT treats all
other terminals as hard-copy terminals.

•

If a

local

each

EDT numbers them
file has more than 42949 lines,
incorrectly and line mode will work incorrectly after line

42949.
•

When you use the SUBSTITUTE command,
apostrophe (')r a quotation mark ("), or
the delimiter.

2-16

you cannot use an
percent sign (%) as

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

macro using
C command.
the
using
mode
the macro cannot enter keypad

•

If you undelete a line that is

If you define a key to execute a line-mode

EXT,

longer,
128 characters long or
the
example,
For
lines.

multiple

you may not undelete
following command would not work:
<G0LD>

and
L>,
If you delete a <CR> using <DEL C>, <DEL W>, or <DEL
If
the <CR> is turned into a line break.
it,
then undelete
preserved.
you use CUT, the <CR> is

•

After performing a RECOVER operation, verify
correct, and EXIT from the file.
is
buffer
that your edited file is preserved.

•

that your main
This will ensure

EDT does not support stream files.

•

2.5

PROGRAM DEVELOPMENT TOOLS

the
The following sections contain notes on changes and additions to
tools
development
Program
system components used to develop software.
are documented in the following manuals:
•

VAX- 11 Utilities Reference Manual

•

VAX/VMS Magnetic Tape User's Guide (new manual)

•

VAX- 11 SORT/MERGE User's Guide

•

VAX- 11 MACRO Language Reference Manual

•

VAX- 11 Linker Reference Manual

•

VAX- 11 Symbolic Debugger Reference Manual

VAX-11 SORT/MERGE User's Guide: New /STATISTICS Qualifier

2.5.1

The /STATISTICS qualifier has been added (for use with SORT only) with
Version 3.0 of VAX/VMS. You must specify this qualifier to cause SORT
A
to display a statistical summary at the end of your sort operation.
statistical summary will no longer be displayed by default after a
completed sort.

BACKUP Restriction: Restoring Directories

2.5.2

version of BACKUP prior to Version
VAX/VMS using the selection file specification [000000...]
without the /FAST qualifier, the directory specifications stored in
example,
for
[000000];
leading
a
contain
set
save
the
[000000. SYSEXE].
If a save set was created with a

3.0

You must take this into consideration if you selectively restore
you must specify
For example,
directories from such save sets.
because the
[SYSEXE]
/SELECT=[000000. SYSEXE] to restore directory
directory
recorded
the
select
not
does
[SYSEXE]
qualifier /SELECT=
to
qualifier
/LIST
the
use
can
You
.
SYSEXE]
[000000.
specification
determine whether the recorded directory specifications in the save
set you want to process contain a leading [000000].
2-17

)

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

In save sets created with Version 3.0 of BACKUP, the leading
[000000]
is
not present.
Therefore, to restore directory [SYSEXE], specify

/SELECT=[SYSEXE].

VAX-11 Utilities Reference Manual

2.5.3

Version 3.0 of the VAX-11 Utilities Reference Manual is expanded to
include documentation for all utilities supported by VAX/VMS.
The
following utilities are new with Version 3.0:
•

Accounting Utility (ACCOUNTING)

•

Command Definition Utility (SET COMMAND)

•

Monitor Utility (MONITOR)

•

Phone Utility (PHONE)

•

Verify Utility (ANALYZE/DISK_STRUCTURE)

The following utilities contain major enhancements with Version 3.0 of
VAX/VMS:
•

Authorize Utility (AUTHORIZE)

•

Backup Utility (BACKUP)

•

Install Utility (INSTALL)

•

Librarian Utility (LIBRARY)

•

Message Utility (MESSAGE)

•

Personal Mail Utility (MAIL)

•

RMS Share Utility (RMSSHARE)

•

SYE Utility (SYE)

•

System Generation Utility (SYSGEN)

2.5.4

Obsolete Images Removed

The images listed below have been removed for VAX/VMS Version 3.0:
•

SYS$LIBRARY:VMLIB.OLB (RSX virtual memory support routines)

•

SYS$SYSTEM:DISPLAY.EXE (replaced by MONITOR)

•

INFO
(previously
PROCESS/CONTINUOUS

•

MDL (never supported)

•

SETNAME
(previously
PROCESS/NAME=)

•

SFA
(previously
ANALYZE/IMAGE)

•

TALK (previously unsupported, replaced by PHONE)

unsupported,

replaced

unsupported,

2-18

replaced

SHOW

replaced

SET

new

DUMP

and

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

VFY1 (replaced by ANALYZE/DISK_STRUCTURE)

•

VFY2 (replaced by ANALYZE/DISK_STRUCTURE)

•

WHO (not supported)

Command Definition Utility

2.5.5

For VAX/VMS Version 3.0 r a new command definition utility has been
See Chapter 5 of the VAX- 11 Utilities Reference Manual
added to DCL.
for instructions on how to use this utility to define DCL commands, to
request that DCL parse your commands, and to retrieve information from
DCL about your commands.

Accounting Record Formats

2.5.6

The accounting record formats have changed for Version 3.0 of VAX/VMS.
This was done to include new information and make future enhancements
easier while maintaining upward compatibility.

Version
an
processes
utility
This
CNVACC.
Utility,
the Conversion
use
3.0,
formats of
input file containing either Version 3.0 formats or
previous versions of VAX/VMS and produces an output file whose records
are in the former format (that is, the format described on page 174 of
To convert
the Version 2.0 VAX /VMS System Services Reference Manual .
following command
the
use
an accounting file to the former format,
sequence:
If you require record formats of versions of VAX/VMS prior to

)

CNVACC :== $CNVACC

CNVACC <input-file-spec> <output-f ile-spec>

The Conversion Utility will prompt for any arguments not supplied.
The default
The default input file specification is "ACCOUNTNG.DAT" .
the
read
can
CNVACC
"ACCOUNTNG.OLD"
.
is
output file specification
current accounting file without first having to render it inactive.

Image Level Accounting

2.5.7

Image level accounting, a new feature for Version 3.0, is by default
may be enabled or disabled with the $SNDACC system
It
disabled.
service or with the DCL command SET.

$SNDACC system
the
To enable or disable image level accounting with
the job type code, ACC$KIMGTRM, which is defined in the
use
service,

$ACCDEF macro.
To enable or disable image level accounting with the DCL command
use the following format:
$

SET ACCOUNTING /ENABLE=IMAGE

SET ACCOUNTING /DISABLE=IMAGE

2-19

SET,

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
ANALYZE Command Notes

2.5.8

The DCL command
ANALYZE,
used with
performs the indicated functions:

the

qualifiers

below,

listed

•

ANALYZE/CRASH_DUMP - Invokes the System Dump Analyzer (SDA) to
analyze a VAX/VMS crash dump file.

•

ANALYZE/DISK_STRUCTURE - Invokes the Verify Utility to analyze
and
optionally repair a disk structure, or to generate a
binary usage file.

•

ANALYZE/IMAGE

Generates

formatted listing of the

contents

of an image file.

formatted listing of the contents

•

ANALYZE/OBJECT - Generates
of an object file.

•

ANALYZE/RMS_FILE - Performs
with an interactive option.

•

ANALYZE/SYSTEM - Invokes the System
examine the running system.

structure analysis of RMS

Dump

Analyzer

files

(SDA)

Synonym Directory Entries on System Disk

2.5.9

following synonym
Two files, SYSBOOT.EXE and SYSMAINT.DIR, have the
entries on a normally functioning VAX/VMS Version 3.0
system:

directory

[SYSEXEJSYSBOOT.EXE
[SYSEXEMIN] SYSBOOT. EXE
[SYSO. SYSEXE] SYSBOOT. EXE

[000000]SYSMAINT.DIR
[SYSO] SYSMAINT.DIR
will
ANALYZE/DISK_STRUCTURE
utility
report
Therefore,
the
%VERIFY-I-BACKLINK error messages for these files. These messages are
entirely normal.

2.5.10

AUTHORIZE Command String Length Restriction

For Version 3.0 of VAX/VMS, AUTHORIZE uses the new Command
Definition
Utility to interpret a command string after placing the string into an
internal buffer. AUTHORIZE command strings cannot be greater than 508
characters in length (excluding hyphens for continuation) because the
Command Definition Utility will not process command buffers longer
than 508 bytes.
If
a command string exceeds this limit, divide it
into two or more command strings.

2.5.11

Null Passwords Implemented

You can now use the DCL command SET PASSWORD or the qualifier
/PASSWORD with the AUTHORIZE command to specify null passwords. When
you have a null password, you only need to enter your username to log
in
because LOGIN does not perform a password prompt or verification.
See the AUTHORIZE chapter of the VAX- 11 Utilities Reference Manual or
Chapter 2 of the VAX/VMS System Management and Operations Guide for
more information.

2-20

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

2.5.12

AUTHORIZE String Delimiter Restrictions

When using the AUTHORIZE command, you must delimit all strings with
double quotation marks (") that contain embedded blanks. For example,
the following command is in the correct form:

UAF>MODIFY DOE /OWNER="JANE DOE"

2.5.13

AUTHORIZE Qualifier /MAXACCTJOBS Unimplemented

The /MAXACCTJOBS qualifier for the Authorize Utility is not
for VAX/VMS Version 3.0 and should not be used.

2.5.14

supported

INSTALL Restriction

INSTALL prints an incorrect value for the size of the image headers of
A future version of
installed HEADER_RESIDENT.
images that are
VAX/VMS will correct this problem.

2.5.15

Monitor Utility Notes

The following items apply to the Monitor Utility for

VAX/VMS

Version

3.0:
•

•

2.5.16

When a recording file containing a comment string is played
back, the comment is included in the heading of the display or
summary.
When a VAX-11/782 attached processor is started or stopped
with a START/CPU or STOP/CPU command during execution of a
MONITOR MODES request, data collected for the interval during
which the operation takes place may contain incorrect MODES
data.

Disabling Dialup and Network Access

through
to
in
To prevent an account in SYSUAF.DAT from being logged
"SET HOST node" command or through a dialup, use the
of a
the
use
following two new login flags for primary and secondary days as shown
in the following AUTHORIZE command:

UAF>MODIFY <USER> /PFLAGS= (DISDIALUP, DISNETWORK)
/SFLAGS= (DISDIALUP, DISNETWORK)

2.5.17

New Quota: ENQLM

new quota
a
The VAX/VMS Version 3.0 lock management services use
the
represents
quota
called the enqueue quota (ENQLM). The enqueue
Version
own.
can
subprocesses
its
and
process
a
locks
total number of
2.0 of VAX/VMS provides the authorization file with a field for ENQLM
The
However, this field has always been zero.
in each user record.
runs
that
section
a
contains
procedure
VAX/VMS Version 3.0 upgrade
However,
AUTHORIZE and changes every account to have a nonzero ENQLM.
you must do this manually for any additional authorization files that
AUTHORIZE.
in
Use the MODIFY command
your installation maintains.

2-21

DIFFERENCES BETWEEN VAX/VMS VERSION 3,0 AND VAX/VMS VERSION 2.5
This command has been enhanced to support the use of wild card
characters to make this procedure easier. For example, to set the
following command to
the
issue
ENQLM to 10 for every account,
AUTHORIZE:

MODIFY */ENQLM=10
To set the ENQLM to 20 for a group,

issue the following command:

MODIFY [11,*]/ENQLM=20
Then, individually set any accounts that require

different ENQLM.

You may receive the SS$ EXENQLM error message if your process performs
extensive RMS file sharing without sufficient enqueue quota.

2.5.18

Lock Management Services

VAX-11 RMS
For Version 3.0 of VAX/VMS,
services to synchronize shared files,
for
taken out
locks.
One lock will be
buffer, and outstanding record lock.

lock management
uses the
global buffers, and record
global
file,
each shared

If your system performs extensive VAX-11 RMS file sharing, the default
(LOCKIDTBL
setting of the SYSGEN parameter LOCKIDTBL may be too low.
If
controls the maximum number of locks allowed on the system.)
LOCKIDTBL is set too low, programs will receive the SS$_N0L0CKID error
message.

you
Please note that if you increase the SYSGEN parameter LOCKIDTBL,
See the VAX/VMS
must also
increase the SYSGEN parameter RESHASHTBL.
System Management and Operations Guide for more information about
these parameters.

2.5.19

Elimination of /SHARE=COPY and GSMATCH=NEVER Linker Options

Version 3.0 of VAX/VMS no longer supports the /SHARE=COPY linker
This option enabled you to store a shareable image in an
option.
executable image file and activate the entire entity as a single
image.
you
linker,
If you specify the /SHARE=COPY option to the Version 3.0
will
receive a warning message and the image will be linked as if the
In
order to
=COPY option to the /SHARE qualifier was not present.
executable
the
another,
system
to
transport an application from one
image and all shareable images referenced by that image must be moved.
(The
ANALYZE/IMAGE/FIXUP command gives a list of all shareable images
referenced by an executable image.)

Although the GSMATCH=NEVER option is accepted by the linker, the
executable image that is produced when linking with such an image will
to
not execute.
A future version of VAX/VMS will correct the linker
disallow GSMATCH=NEVER.
earlier)
(or
Note that images linked under VAX/VMS Version 2.5
the /SHARE=COPY option will continue to activate successfully.

2-22

with

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
SYSGEN AUTOCONFIGURE Modifications

2.5.20

floating
the algorithm for computing
VAX/VMS
slightly
been
has
devices
UNIBUS
for
(CSR)
control/status registers
effected
Devices at the high end of floating space could be
changed.
DRllWs)
and
DRllBs
LPAlls after the first, as well as
example,
(for
Manual
Reference
Utilities
If you encounter problems, see the VAX-11
SHOW/UNIBUS,
commands
5YSGEN
ni^
the
about
information
for
(You can use the CONFIGURE command
SHOW/CONFIGURATION, and CONFIGURE.
controller on a UNIBUS.)
to calculate the addresses necessary for each
For Version 3.0 of

VAX/VMS are
Some SYSGEN AUTOCONFIGURE modifications for Version 3.0 of
listed below:
•

TU58 cartridges are now autoconf igured in
reserved for KLlls.

•

DUPlls will not autoconfigure because
driver name for SYSGEN to reference.

•

The DC11 vector alignment has changed from

•

The

•

2.5.21

the

there

slot

formerly

standard

to 8.

DRUB vector alignment has changed from 8 to 4.

RX211
or
All devices that AUTOCONFIGURE finds where an RX11
proper
the
causes
This
should be, are assumed to be RX211s.
driver to be loaded.

Restriction in Activating Privileged Shareable Images
are not

permitted

In VAX/VMS Version 3.0, privileged shareable images
image
make outbound calls. This means that a privileged shareable
to
image.
shareable
other
some
in
defined
symbols
cannot reference global

activation of an image that references such an illegal privileged
shareable image will fail with the SS$_NOSHRIMG error message.

The

qualifier with the
To work around this restriction, use the /NOSYSSHR
modules in the
object
the
and explicitly include all
DCL command LINK
privileged shareable image.

2.5.22

VAX-11 Linker Reference Manual

the VAX-11
The following technical changes are new with Version 3.0 of
contain
that
or
2.1
2.0
Version
under
linked
images
Shareable
Linker.
relinked.
be
must
sections
copy always image
•

•

References to shareable images that do not use general
and
MACRO,
VAX-11
in
(G*
mode
addressing
ADDRESSING MODE (GENERAL) in VAX-11 BLISS-32) will cause an
.LONG references to
Also,
error message at link time.
shareable
a
of
creation
the
in
found
addresses
relocatable
However, these images should execute
be flagged.
image will
correctly.
.ASCID in a
Use of the VAX-11 MACRO directives .ADDRESS and
nonshareable.
section
program section makes that program
or
Thus, if multiple processes must access a code section
not
do
directives
these
that
ensure
section,
read-only data
appear in the sections.

2-23

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

The linker map format has changed slightly.
lines with embedded carriage control.

•

In a linking operation that creates a shareable image, if
the
linker encounters the object language equivalents of the
VAX-11 MACRO assembler directives .ADDRESS or .ASCID or their
equivalent,
it
includes a fix-up image section in the image.
The fix-up image section contains information that allows
the
image activator to make these position-dependent references
position independent.
In this way, a shareable
image, which
would otherwise be position dependent,
is
made position
independent.

•

Position independent shareable images can now be placed at a
specified address in virtual memory by means of the CLUSTER=
option.

•

Sharing of a single COMMON data area (such as those used
in
VAX-11 FORTRAN,
VAX-11 BASIC,
and VAX-11 PL/I) by multiple
shareable images can now be achieved without sacrificing the
independence of any of the shareable images.

•

In resolving symbolic references, the linker now searches
the
system default shareable image library IMAGELIB.OLB after
searching any user-defined default libraries.
IMAGELIB.OLB
contains VMSRTL.EXE, a shareable image library that the linker
previously searched by default.

•

In an options
file,
an
empty cluster may be defined by
specifying the CLUSTER= option without including one or more
files as input to the cluster.

•

In an options file,

There

are

input files no longer need to be specified

first.
•

The CHANNELS= option is no longer available or needed.

•

The GSMATCH=NEVER

•

When specifying a base address with the /SYSTEM qualifier, the
linker
rounds the specified address to the next highest page
boundary only when the /HEADER qualifier is also specified;
otherwise it uses the specified address. Before Version 3.0
of VAX/VMS, the linker always rounded to the next highest page
boundary.

•

Images created under VAX/VMS Version 3.0 cannot be
versions of VAX/VMS systems prior to Version 3.0.

•

If
a
specific common area is defined
in
shareable images, the linker reports an error.

•

If a common area in an input object module is
larger than a
common area
(with
the
same name) in a shareable image, the
linker will report an error.

2.5.23

option should not be
resulting executable image will not run.

used

because

two

used

the

different

Watchpoint Implementation Restriction in DEBUG

When you are using watchpoints in DEBUG on a VAX-11/730 processor,
DEBUG may go
into
an infinite loop if the following conditions are
true:

2-24

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
have set two or more watchpoints

•

If you

•

If a pair of the

•

If an

watchpoints lie on adjacent pages of memory

instruction is executed whose target lies on both

those

pages
This infinite loop will cause your program to hang after you
STEP or GO command.

issue

watchpoint
one
problem, do not set more than
A future
processor.
simultaneously when using DEBUG on a VAX-11/730
version of VAX/VMS will correct this problem.
To

avoid

this

SYSTEM SERVICES AND I/O

2.6

to
The following sections contain information on changes and additions
topics
these
for
documentation
The
I/O.
VAX/VMS system services and
is found in the following manuals:

2 # 6.1

•

VAX/VMS System Services Reference Manual

•

VAX/VMS I/O User's Guide (Volume

1)_

•

VAX/VMS I/O User's Guide (Volume

New System Status Codes

With Version 3.0 of VAX/VMS, the following new system status codes are
represent specific
by certain new system services to
returned
nonprivilege and quota-exceeded errors:
Exceeded Quota

Nonprivilege
SS$_NOCMKRNL

SS$_NOSYSNAM

SS$_NOTMPMBX

SS$_EXASTLM

SS$_NOALLSPOOL

SS$JNOBUGCHK

SS$_NOBYPASS

SS$_EXBIOLM

SS$ NOCMEXEC

SS$ NODETACH

SS$_NODIAGNOSE

SS$_EXBYTLM

SS$_NOEXQUOTA

SS$_NOGROUP

SS$_NOGRPNAM

SS$_EXDIOLM

SS$_NOLOGIO

SS$_NOMOUNT

SS$_NONETMBX

SS$_EXENQLM

SS$_N0ACNT

SS$_N00PER

SS$_NOPFNMAP

SS$_EXFILLM

SS$_N0PHYI0

SS$_NOPRMCEB

SS$_NOPRMGBL

SS$_EXPGFLQUOTA

SS$_NOPRMMBX

SS$_NOPSWAPM

SS$_NOALTPRI

SS$_EXPRCLM

SS$_NOSETPRV

SS$_NOSHMEM

SS$_NOSYSGBL

SS$ EXTQELM

SS$_NOSYSLCK

SS$ NOSYSPRV

SS$ NOVOLPRO

SS$ NOWORLD

services
The VAX/VMS System Services Reference Manual identifies
codes.
status
new
use these

that

error codes
All VAX/VMS system services that returned the general^
to do so.
continue
3.0,
Version
before
SS$_EXQUOTA
or
NOPRIV
SS$

2-25

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
These will change, however,
in
a
major release of VAX/VMS after
Version 3.0,
return the explicit privilege or quota status codes
to
listed above.

Therefore, after you install VAX/VMS Version 3.0, modify any programs
that
explicitly check for SS$_N0PRIV or SS$_EXQUOTA.
Use
the
following four symbols to discover whether the status code is within
the range of the specific codes:
Status Code

Definition

SS$_NOPRIVSTRT

Start of specific no privilege status codes

SS$_NOPRIVEND

End of specific no privilege status codes

SS$_EXQUOTASTRT

Start of specific exceeded quota status codes

SS$_EXQUOTAEND

End of specific exceeded quota status codes

Example:

Change from:

To:

CMPW
BEQL

R0, SS$JNOPRIV

CMPW
BEQL
CMPW
BLSSU
CMPW
BLEQU

R0, SS$_NOPRIV
NOPRIV ERROR
R0, SS$_NOPRIVSTRT

N0PRIV_ERR0R
;As existed

;before, adding

10$
R0, SS$_NOPRIVEND

NOPRIV_ERROR

10$:

NOTE
You do not need to modify programs that
check
status
codes for success or
failure
only.
For
example,
the
following codes will continue to be
correct:

CMPL
BEQL

SS$_N0RMAL
SUCCESS

R0,

BLBC

2.6.2

R0, ERROR

$GETMSG System Service Restrictions

The following restrictions apply to the $GETMSG system service:
•

$GETMSG does not check the length of the argument list and
therefore
cannot
return
the
SS$_INSFARG
(insufficient
arguments) error status code.
If the service does not receive
enough arguments, you may not get the desired results.

•

$GETMSG will not generate exceptions when failures
system service failure mode is enabled.

2-26

occur

and

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.6.3

$ENQ System Service Documentation Error

The description of the $ENQ system service
in
the VAX/VMS System
Services Reference Manual states that the SS$_N0L0CKID error message
is returned if lock identifications are
not available and
resource
wait mode
is disabled.
This is incorrect.
SS$_N0L0CKID is returned
whether resource wait mode is enabled or disabled.

2.6.4

/NOMODEM Default for Terminals

For Version 3.0 of

VAX/VMS,
the default modem characteristic
for
terminals is /NOMODEM.
If
lines connected to
you have terminal
modems, change this setting to /MODEM in your start-up command file.
If
you do not change the setting,
VAX/VMS will ignore all modem
control signals, producing undesired effects.
For example, improperly
defined lines for automatic answer modems will prevent the modem from
answering incoming calls.
If you have non-dial in terminals set to
/MODEM,
feature of login will assume that terminal is
restricted accounts from being logged into.

2.6.5

then the DISDIALUP
dialup, and prevent

/AUTOBAUD Default for Terminals

For Version 3.0 of VAX/VMS, the default speed detection characteristic
for terminals is /AUTOBAUD.

A terminal that
not receive broadcast
is
set to /AUTOBAUD will
messages if it is not logged in or attached to a process as an
application terminal. The system will avoid writing messages to such
a terminal until the proper transmission speed has been determined.
Thus, a terminal
/AUTOBAUD will not receive the initial
set
to
REPLY/ALL you may have placed in your SYSTARTUP command file notifying
users that the system is up.
If you have terminals on fixed lines
that always
run
at
the
same
speed,
they will not benefit from the automatic speed detection
provided by /AUTOBAUD and you should specify their permanent speed in
the SYSTARTUP command file.

For example, if line TTAO is connected to a VT100 that is set
to
run
at
9600
baud,
then place the following command in the SYSTARTUP

command file before any REPLY /ALL command:
SET TERMINAL TTAO:
/DEVICE_TYPE=VT100
/PERMANENT /NOAUTOBAUD /SPEED=9600

Such terminals will have known transmission speeds, and the system
will
send
broadcast messages to them even though they are not logged
in.

2.6.6

New Terminal Driver Error Code

For VAX/VMS Version 3.0, the following new READ error
defined for terminal READ operations:
SS$ DATAOVERUN

2-27

code

has

been

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
This error will be returned if an overrun condition occurs in the
terminal controller input SILO, or if the typeahead buffer overflows.
SS$_PARITY was returned for these
(Before Version 3.0 of VAX/VMS
conditions.)
r

Read Outstanding Required for Remote Device Communication

2.6.7

When a terminal line is used as a communications mechanism to some
remote device, ensure that the program using that line contains a read
By
outstanding to the device whenever an input stream is expected.
the
create
to
driver
doing this, your program forces the terminal
type-ahead buffer at the time the read is started.
^

input
Failure to supply this read outstanding can cause some
of a
creation
the
in
problem
characters to be lost because of a timing
type-ahead buffer.

Change in Default Terminal Protection

2.6.8

improve system security, the default protection for unallocated
terminals has changed. Terminals cannot be allocated by an existing
This protection is
process but can be logged in to a new process.
the protection
change
To
TTYJ>R0T.
parameter
SYSGEN
controlled by the
process
general
for
available
be
to
need
that
lines
for terminal
allocation, use the DCL command SET PROTECTION/DEVICE.
To

Device Information

2.6.9

The following three system services can be used to obtain
about devices:
•

Get Device/Volume Information ($GETDVI)

•

Get Channel Information ($GETCHN)

•

Get Device Information ($GETDEV)

information

as
categories
such
The information obtained includes
characteristics, device type, error count, and operation
$GETDVI also returns information about the volume set.

device
count.

system
the $GETDVI
of
It is recommended that new programs make use
$GETDVI returns all the
service to obtain device information.
However, only $GETDVI
information returned by $GETCHN and $GETDEV.
$GETCHN are unchanged
and
($GETDEV
future.
in the
will be extended
See the VAX/VMS System Services
from Version 2.0 of VAX/VMS).
Reference Manual for information about $GETDVI.

2.6.10

$CREPRC System Service Modified

The Create Process ($CREPRC) system service
following
The
Version 3.0 of VAX/VMS.
privilege:
service now require DETACH

BATCH

used to be nonpr ivileged

NETWRK

used to require NETMBX privilege

2-28

has
two

been modified with
status flags to this

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2,6.11

$CREPRC System Service Privilege Bit Names

have been
Two new privilege bit names, PRV$V_ACNT and PRV$V_ALTPRI,
Their values are equal to those of
added to the $PRVDEF macro.
PRV$V_NOACNT and PRV$V_SETPRI, respectively. These new bit names have
been added to provide PRV names that are consistent with the names
used by AUTHORIZE and DCL.
For compatibility,
the old names are still defined by $PRVDEF.
However,
it is strongly recommended that the new names be used in all
future programs.

2.6.12

$SETPRI System Service

For VAX/VMS Version 3,0, the $SETPRI system service allows a process
that does not have ALTPRI privilege to lower its priority and later
raise priority back to the value
in
its authorization
indicated
record.

2,6.13

Undocumented System Service Interfaces

The use of the $IMGACT procedure and
reserved to DIGITAL as stated below:
•

the

item

JPI$_IMAGECOUNT

Image Activator
The system procedure that prepares images for execution is not
called in the same fashion as the VAX/VMS Version 2.0 image
is
activator.
reserved to
The use of the $IMGACT procedure
DIGITAL.
DIGITAL reserves the right to continue to make
changes to this interface.

•

JPI$_IMAGECOUNT
There is an undocumented item that can be returned from the
$GETJPI system service called JPI$_IMAGECOUNT. The use of
this item is reserved by DIGITAL.

2.6.14

VAXAMS I/O User's Guide Documentation Change

Section 9.2.4 (Escape Sequences) of the terminal driver chapter of
VAX/VMS I/O User's Guide
(Vol.
1), the sentence in the third
paragraph that reads "The remaining characters are transmitted on the
next read." should be replaced with the following statement:
In

the

If SS$_PARTESCAPE is returned, the application program must issue
enough single character reads, without timeout, to read the rest
of the characters in the escape
sequence, while parsing the
syntax of the rest of the escape sequence.

2.7

RUN-TIME LIBRARY

The following sections contain notes on changes and additions to the
VAX-11 Common Run-Time Procedure Library. The VAX-11 Run-Time Library
is documented in the following manuals:

2-29

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

VAX- 11 Run-Time Library User's Guide

•

VAX- 11 Run-Time Library Reference Manual

•

VAX- 11 Guide to Creating Modular Library Procedures

•

VAX- 11 Run-Time Library Language Support Reference Manual

2.7.1

VAX-11 Common Run-Time Procedure Library Modifications

For VAX/VMS Version 3.0 of the Run-Time
Library,
the VAX-11 RTL
manuals have been reorganized for VAX/VMS Version 3.0. The VAX-11
Run-Time Library User's Guide contains detailed explanations of string
handling, condition handling, the screen package and other concepts.
The procedure descriptions in the VAX-11 Run-Time Library Reference
Manual are now in alphabetical order.
In addition, there is online
help for the language independent procedures (HELP RTL) of the VAX-11
Run-Time Library.

New procedures have been added for the following:
•

Analyzing string descriptors (LIB$ANALYZE_SDESC)

•

CLI

•

Handling faults (LIB$DECODE_FAULT)

•

Manipulating binary trees
LIB$TRAVERSE_TREE)

•

Performing file lookups (LIB$FILE_SCAN, LIB$FIND_FILE)

•

General-purpose conversions (LIB$CVT_DX_DX)

•

New screen-oriented procedures (LIB$PUT_LINE,
LIB$SET_SCROLL, LIB$UP_SCROLL)

•

Translation tables that provide
from
ASCII
to
EBCDIC
and
LIB$AB_EBC_ASC_REV)

•

Callable procedures that make
additional
VAX-11
MACRO
instructions available to a high-level language (LIB$CALLG,
LIB$MOVC3, LIB$M0VC5, LIB$EMUL, LIB$EDIV)

•

String arithmetic enhancements (new entry point STR$DIVIDE)

•

New math procedures that provide the following:

callback
routines
(LIB$GET_SYMBOL,
LIB$SET_SYMBOL,
LIB$DELETE_SYMBOL,
LIB$SET_LOGICAL,
LIB$DELETE_LOGICAL,
LIB$ENABLE_CTRL, LIB$DISABLE_CTRL, LIB$SPAWN, LIB$ATTACH)

(LIB$INSERT TREE,

LIB$LOOKUP TREE,

LIB$SET_OUTPUT,

reversible transformation
back
(LIB$AB ~ASC EBC REV,

Hyperbolic arctangent (MTH$ATANH,
MTH$HATANH)

MTH$DATANH,

MTH$GATANH,

Base 2 logarithms
MTH$HLOG2)

MTH$DLOG2,

MTH$GL0G2,

Sine and cosine
MTH$HSINCOS)

MTH$DSINCOS,

MTH$GSINCOS,

New math trigonometric procedures that take
sine
results
in
degrees to complement
procedures that use radians.

arguments or
the
existing

(MTH$AL0G2,

(MTH$SINCOS,

2-30

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

2.7.2

String Descriptors Require Valid Class and Datatype

Because new descriptor classes are supported in VAX/VMS Version 3,0,
most VAX-11 Run-Time Library procedures that take string parameters
check the string descriptor class and datatype fields for validity.
Previous versions of these procedures did not examine these fields
were
because the only supported string classes (static and dynamic)
often equivalent.
or
If you create string descriptors while programming in VAX-11 MACRO
VAX-11 BLISS-32, ensure that you initialize the class and datatype
fields to appropriate values.
You can specify a zero class and
datatype and indicate a static text string. Failure to do so may give
The most
incorrect results, or the error "invalid string descriptor".
common source of this type of error is a VAX-11 BLISS-32 program that
declares the descriptor to be LOCAL, thereby allocating it on the
fields are not filled in, the
If
stack.
the class and datatype
previous contents are used, causing errors.

MACRO
If you are using strings in a high-level language or the VAX-11
directive .ASCID, the class and datatype fields are already being
correctly filled in. See Appendix C of the VAX-11 Run-Time Library
Reference Manual and the VAX-11 Run-Time Library User's Guide for more
information.

2.7.3

Enabling and Disabling CTRL/T

new VAX-11 Run-Time Library procedures, LIB$ENABLE_CTRL and
LIB$DISABLE_CTRL, allow you to enable and disable CLI interception of
control characters. The description of these procedures in the VAX-11
Run-Time Library Reference Manual only mentions their use for enabling
and disabling CTRL/Y interception.
These procedures actually permit
enabling and disabling of any control character supported by the CLI
being used.
For DCL, CTRL/T and CTRL/Y are supported.
For MCR,
only
CTRL/Y is supported.
Two

The symbol LIB$M_CLI_CTRLT is defined as the bit mask for CTRL/T,
in
See the
addition to the documented definition of LIB$M CLI_CTRLY.
VAX-11 Run-Time Library Reference Manual for more Information.

2.7.4

LIB$SPAWN Restrictions

LIB$SPAWN is a new Run-Time Library procedure that makes the DCL
command SPAWN available as a callable procedure. Because it actually
LIB$SPAWN is subject to any
calls DCL to perform its function,
limitations and restrictions placed on the SPAWN command. However, if
the SPAWN command displays an informational message warning you of a
violated restriction
(such as a symbol whose value is too long), a
program calling LIB$SPAWN will not receive any indication of the
warning.
Ensure that you understand all of the limitations of SPAWN
before using LIB$SPAWN.
For more information, see the VAX/VMS Command
Language User's Guide and the VAX-11 Run-Time Library Reference
Manual.

2.7.5

Changes to VAX-11 RTL Routines for BASIC String Arithmetic

The interpretation of the P% parameter (the rounding and truncation
parameter)
has been changed to be compatible with the interpretation
found in VMS BASIC-PLUS-2.
The following tables are an extraction of

2-31

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
those tables provided in the reference manuals for VMS BASIC-PLUS-2
Note where the differences occur; the new behavior
and VAX-11 BASIC.
results found
of the VAX-11 BASIC run-time routines will reflect the
in the VMS BASIC-PLUS-2 tables.

Input value = 12345.67898
Result for
VMS BASIC-PLUS-2

Effect

-5
-4
-3
-2
-1

100,000s
10,000s
1000s
100s

Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number

rounded
rounded
rounded
rounded
rounded
rounded
rounded
rounded
rounded
rounded
rounded

9995
9996
9997
9998
9999
10 r 000
10,001
10,002
10,003
10,004
10,005

Number
Number
Number
Number
Number
Number
Number
Number
Number
Number
Number

truncated
truncated
truncated
truncated
truncated
truncated
truncated
truncated
truncated
truncated
truncated

2.7.6

Obtaining RAB Pointer for FORTRAN Unit

2
3

to
to
to
to
to
to
to
to
to
to
to

123

10s

units
tenths
hundredths
thousandths
ten-thousandths
hundred- thousandths
to
to
to
to
to
to
to
to
to
to
to

100,000s
10,000s
1000s
100s

1235
12346
12345.7
12345.68
12345.679
12345.6789
12345.67891

123
1234

10s
units

12345

tenths
hundredths
thousandths
ten-thousandths
hundred-thousandths

12345..6

12345.67
12345.678
12345.6789
12345.67891

Old Result for

VAX-11 BASIC

10000
12000
12300
12350
12346
12345.7
12345.68
12345.679
12345.6789
12345.67891

10000
12000
12300
12340
12345
12345.6
12345.67
12345.678
12345.6789
12345.67891

A new VAX-11 Run-Time Library procedure makes it possible for a
FORTRAN program to obtain the address of the VAX-11 RMS Record Access
Block (RAB) for a FORTRAN logical unit (LUN) without using a USEROPEN
The RAB can be accessed or modified as necessary to use
procedure.
RMS features that are not directly supported by FORTRAN.
The calling format of the procedure is:

RAB.wa.v = F0R$RAB (LUN.rl.r)
LUN is the FORTRAN logical unit number for which the address of
is to be returned, and is passed as an integer by reference.
RAB
unit must be open.

the
The

for
See the VAX-11 RTL Language Support Procedures Reference Manual
guidelines to follow when manipulating VAX-11 RMS data structures used
by the VAX-11 Run-Time Library.

2.7.7

Procedures No Longer Included in STARLET. OLB

Several undocumented procedures that were included in the VAX/VMS
Version 2.0 STARLET. OLB are not included in the VAX/VMS Version 3.0
distribution kit.

2-32

DIFFERENCES BETWEEN VAX/VMS VERSION 3,0 AND VAX/VMS VERSION 2.5

Module Name

Entry Point

CALLIMAGE
CREMAPSEC
LIB$EXECUTE_CLI
LIB$MERGE
LIBACP

LIB$CALL_IMAGE
LIB$_CREMAPSEC
LIB$EXECUTE_CLI
LIB$_P1MERGE
LIB$CHECK DIR
LIB$CREATE_DIR
LIB$FID_TO_NAME
LIB$SET_PROT
LIB$UNLOCK
PRV$SETPRIV

SETPRIV
(*)

(*)

See the VAX-11 Run-Time Library procedure LIB$SPAWN.

2.8

VAX-11 RECORD MANAGEMENT SERVICES (VAX-11 RMS)

The following sections contain notes that describe changes and
additions to the VAX-11 Record Management Services. Documentation on
VAX-11 RMS is found in the following manuals:

2.8.1

•

Introduction to VAX-11 Record Management Services

•

VAX-11 Record Management Services Tuning Guide (new manual)

•

VAX-11 Record Management Services Utilities
(new manual)

•

VAX-11 Record Management Services Reference Manual

Reference

Manual

EDIT/FDL Error Message

The EDIT/FDL facility will return the following error
invalid date/time string is specified:

message

FDL-W-INVDATIM, invalid date/time on line n
Ensure that the date/time string has a valid format as documented in
the description of the SYS$BINTIM system service in the VAX /VMS System
Services Reference Manual.

2.8.2

CONVERT/FAST_LOAD Restriction

When you use the /FAST_L0AD qualifier with the CONVERT command to load
an indexed file with key DUPLICATES enabled, the Maximum Key Length is
251 bytes.
This is due to a SORT-32 restriction when doing a "stable"
sort.
Use the /NOFAST L0AD/N0S0RT qualifiers with the DCL command CONVERT to
avoid this problem.

2.8.3

EDIT/FDL Utility Treats Keys as Non-Segmented

treat all
For Version 3.0 of VAX/VMS, the new EDIT/FDL Utility will
keys as nonsegmented
redesign, or optimize
(only during design,
scripts). The other VAX-11 RMS utilities will always treat segmented
keys normally.

2-33

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

2.8.4

EDIT/FDL Utility Ignores EDF$MAKEFDL

EDF$MAKEFDL
For VAX/VMS Version 3.0, the EDIT/FDL Utility ignores the
SET
command
DCL
the
use
Therefore,
defined.
is
it
if
logical name
PROTECTION instead to control access to FDL files.

2.8.5

ANSI-"a" File Names and VAX/VMS File Specifications

file
full
(in
VAX-11 RMS now supports a file name field format
This
characters.
ANSI-"a"
that consists of up to 17
specifications)
new file name format is supported only for magnetic tape devices.

characters include uppercase letters,
The ANSI-"a"
through 9, and the following special characters:

!"%*•()* + -*•

;

the

digits

(including the "space" character)
The full file specification format describing this new file name field
has the following form:

Device: [Directory] "Quoted ANSI-a string". ;Version

quotation
If you use this format, you must place the file name within
when
specification,
your
in
type
file
a
include
cannot
You
marks.
using this file name format. You can, however, include the file type
You can also include a version delimiter (;) as well
delimiter
(.).
number, in your file specification.
version
as a specific
The following file specification would be a legitimate instance
specification using the new file name format:

MTA1: [SMITH] "AIKL U02%SCZ.W" . ;

This file specification, containing the new file name format, can
used to describe files residing on magnetic tape devices only.

Lowercase characters within a quoted string file name field will be
converted to uppercase by VAX-11 RMS. No other modifications will be
made to your original specification.
part
as
The quotation mark (") is a legal character, and can be used
marks
quotation
use
to
wish
If you
file name specification.
of the
within your quoted string file name, you must include two consecutive
("") for each quotation mark that you intend to use.
quotation marks
VAX-11 RMS will ignore the first quotation mark (within the string),
thereby treating the two consecutive quotation marks as a single
quotation mark.

string file name
with a maximum of
field
name
file
valid
a
have
can
you
specification,
For example, a file name consisting of all quotation
36 characters.
marks would contain quotation marks at the beginning and end of the
characters
the
17
(for
file name as well as 34 quotation marks
In this case, the file
permitted) within the quoted string file name.
name field would appear as follows:
If you use only quotation marks within your quoted

Note that this new file name format should not be confused with the
Network Quoted string format. The ANSI-"a" quoted string file name
field is part of a full file specification while the network quoted
string immediately follows a node specification.
2-34

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
Relative Version Addressing

2.8.6

VAX/VMS Version 3,0 supports a new feature called relative version
This feature uses negative version numbers to address
addressing.
If you specify version
file versions relative to the latest versions.
-n,
you will obtain the next most recent version of the file. For
-1,
example, when you specify zero r you obtain the latest version;
is
n
where
-n
specify
If
you
on.
so
and
version,
latest
the next
greater than the number of versions of the file, a file not found
error will occur.
Relative version addressing is fully supported by VAX-11 RMS, native
mode utilities, and most compatibility mode utilities (such as PIP,
Relative
disks only.
2
SOS, and FLX) on Files-11 structure level
1.
level
structure
supported
on
is
not
version addressing

Magnetic Tape Volume Identifiers Now Uppercased

2.8.7

the Magnetic Tape ACP and the tape
For Version 3.0 of VAX/VMS,
Initialize Utilities will uppercase all
and
Mount
the
of
portions
(Label strings passed in quotation marks will also be
label strings.

uppercased.)
The Mount Utility and Magnetic Tape ACP will also uppercase the V0L1
Volume Identifier field for comparison to the input. Before
label,
VAX/VMS Version 3.0, lowercase letters were allowed in tape volume
In order to conform to ANSI standards, VAX/VMS will no longer
labels.
create tapes with lowercase letters in the Volume Identifier field or
distinguish between cases during Volume Identifier verification.
If an ANSI magnetic tape volume label contains characters that are not
example, the ANSI-"a" punctuation
(for
valid VMS name characters
MOUNT will not be a useable
by
produced
name
logical
the
marks),
In these cases, you should supply an
logical name for VAX-11 RMS.
explicit volume logical name. For example,

MOUNT MTAO: volume-name TAPE

Behavior Change for RT-11 Tapes on VAX/VMS

2.8.8

When RT-11 writes to tape a file name which is fewer than six bytes
VAX/VMS MTAACP reads this file name,
Thus,
adds blanks.
it
long
interpreting it as an ANSI file name. There are two results (1) When
you perform a directory on the RT-11 generated tape, all the file
card
(2) Wild
names fewer than six bytes long will appear in quotes.
(In order
copy operations of these files from tape to disk will fail.
to copy the file, you must specify a VAX/VMS output file name.)

MOUNT, Logical Volume Names, and Concealed Devices

2.8.9

When you mount a disk or a tape, MOUNT produces a special logical name
called a "logical volume name" that you can use to reference the
volume. When you dismount the volume, the logical name is deleted.
For
example, the following command produces the logical volume name
"
DRA1:".
USER and equates it to the concealed device name string
$

MOUNT /SYSTEM DRA1:

USERFILES USER

which physical
If you use this logical name, you do not need to know
If you continue to use this logical
drive the volume is mounted on.
2-35

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
name, you avoid building physical device names into programs and
if DRA1 is used for another volume,
Therefore r
command procedures.
you will not inadvertently reference the wrong volume.

The logical volume name produced by MOUNT differs from the
name produced by the following command in one important way:
$

logical

DEFINE /SYSTEM USER _DRA1:

The logical name produced by MOUNT is pointed to by a Mounted Volume
This linkage
List Entry which in turn points to the physical device.
and
allows:
(1) DISMOUNT to find and delete the logical volume name,
the $GETDVI system service to return this logical name when asked
(2)
for the LOGVOLNAM item for the device DRA1.
The print symbiont displays this logical name on the banner page of
listings. This logical volume name is also used by SHOW DEVICE /FILES
and SHOW MEMORY /FILES.
If you want the volume name to be displayed
demonstrated in the following example.

in full, use the

commands

Example
that
A data volume is produced once a month and given a volume label
The users want to refer to the
includes the date it was created.
volume as DATA:, but the dated volume name should be the device name
actually displayed. The following commands accomplish this.
$
$

MOUNT /SYSTEM DRA2: DATA14APR82
DEFINE /SYSTEM DATA DISK$DATA14APR82:

or
disks)
(for
Note that MOUNT defaults to DISK$volume_name
logical
explicit
given
an
not
is
if it
tapes)
(for
TAPE$volume_name
volume name.

Also, note that DATA will translate to a physical device only if the
would be
DRA2:
Defining DATA as
data disk is actually mounted.
less desirable for the following reasons:
1.

Other volumes are sometimes mounted instead of the data disk.

Consistent display of logical device names is desirable.

2.8.10

VAX-11 RMS File Name Specification Length Modified

For VAX/VMS Version 3.0, the value of the symbol NAM$C_MAXRSS has been
increased from 128 to 252 to accommodate VAX-11 RMS support for
(NAM$C_MAXRSS defines a buffer length for a file
concealed devices.
It is defined by the MACRO $NAMDEF.)
specification.
If your program encounters RMS$_ESS or

RMS$_RSS

resultant string
size of the expanded and
NAM$C MAXRSS, and recompile the program.

2,8.11

errors, change the
buffers to the value

VAX-11 RMS Modification of Carriage Control Processing

treated all unit-record
In previous versions of VAX/VMS, VAX-11 RMS
devices (terminals, line printers, mailbox devices, "foreign" magnetic
carriage
as
tape devices, card readers, and network task-to-task)
carriage
FORTRAN
specified
if
you
example,
For
control devices.

2-36

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
control (RAT=FTN), then the first character of each record was removed
"foreign"
and
For mailbox devices,
used
carriage control.
for
magnetic tape devices, card reader devices, and network task-to-task
devices, this behavior was incorrect.
For VAX/VMS Version 3.0, VAX-11 RMS performs this carriage control
operation only for the carriage control devices, terminal devices, and
the device characteristics).
in
line printers, (DEV$V__CCL is set
Modify any user programs that had compensated for this erroneous
behavior.

2.8.12

Files-11 ACP Modifications: Window Handling

In VAX/VMS Version 3.0,
any file that is handled by the memory
uses
Sections or Executable images)
(Global
management
system
is
segmented (cathedral) windows.
In addition, your Byte Count Quota
now charged for all windows created by your process.

Cathedral windows are necessary to correct deadlock conditions that
existed in earlier versions of VAX/VMS. While cathedral windows with
it
is
more than one window segment are very rare, when they appear,
usually an indication that the disk is very fragmented and should be
compressed with BACKUP.
The following considerations should be noted about the window handling
by the ACP for Version 3.0 of VAX/VMS:
•

While it is not necessary to make any code changes, to avoid
overhead, specify that cathedral windows are to be generated
Specify a window
when a file is opened for section access.
size of 255
file is
FAB parameter RTV if the
(by
the
opened/created by VAX-11 RMS or the FIB$B_WSIZE field in the
is
explicitly opened using Files-ACP QIO
FIB
if
file
the
calls)
If you do not make this specification, the Create and
Map Section System Service will request the ACP to remap the
file using cathedral windows,
thus causing an extra ACP
operation.
.

•

Extends to the window of a file open with cathedral windows
are not done at the time of the extend operation, but rather
when the first I/O is performed on the newly extended portion
of the file.
As a result, it is possible to receive the error
status SS$JEXBYTLM on read or write operations.

•

Because all users are charged for any newly created windows,
it
increase the byte limit quota (the
may be necessary to
AUTHORIZE parameter BYTLM) for those users affected.

2.8.13

VAX-11 RMS Record Size Limits for Network Operations

The following record size restrictions exist for network access
the VAX-11 RMS routines $GET, $PUT, and $UPDATE:
•

using

For remote file access, the maximum record size
supported by
VAX-11 RMS is 512 bytes.
This limit includes the record
header for files having variable with fixed control
(VFC)
format.
However, files with records larger than 512 bytes may
be accessed in block mode using the $READ and $WRITE services.
For
example, the DCL command COPY uses block I/O mode to
transfer files from one VAX/VMS node to another when both the
source and destination devices are disks.

2-37

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

records up to 4096
For intertask communication,
length can be exchanged between VAX/VMS programs.

2.8.14

VAX-11 RMS Key Limit Option for Network Operations

bytes

option of
For network access of an indexed file, the LIM (key limit)
If this
supported.
not
(record options) field of the RAB is
the ROP
the
$FIND,
and
$GET
routines
RMS
bit is set on calls to the VAX-11
ignored.
be
will
option

2.8.15

RMS-11 Utilities Replaced by Native-Mode VAX-11 RMS Utilities

The functions of the compatibility-mode RMS-11 utilities have been
superseded by new native-mode VAX-11 RMS utilities. These utilities
See the VAX-11
are also callable from VAX-11 native-mode programs.
and the VAX-11
Manual
Reference
Record Management Services Utilities
A
Information.
complete
for
Guide
ServicesTuning
Management
Record
list of equivalent capabilities follows.

RMS-11

Capability

VAX-11 RMS

File design
and tuning:

N/A

EDIT/FDL

File specification
and creation:

RMSDFN, RMSDEF

CREATE/FDL

File Loading:

RMSCNV, RMSIFL

CONVERT

File space
reclamation:

N/A

CONVERT/RECLAIM

File inspection:

RMSDSP

ANALYZE/RMS_FILE

File analysis and
verification:

2.8.16

Prologue

ANALYZE/RMS_FILE
RMSANLZ
(unsupported utility)

Files Not Supported by RMS-11

VAX-11 RMS has implemented a new type of indexed files, designated
Prologue 3 format. These files cannot be processed by either RMS-11
The behavior of the RMS-11
programs or by the RMS-11 utilities.
VAX-11 RMS utilities must
native-mode
the
Utilities is unpredictable;
be used.

2.8.17

File Version Handling Modified

For Version 3.0 of VAX/VMS, file version handling has been modified.
The previous limit (of roughly 60 versions per file) has been removed.
Now, you can create versions of a file up to Files-11 architectural
You can still limit the number of versions of a file
32767.
limit,
DIRECTORY/VERSION_LIMIT
SET
and
FILE/VERSION_LIMIT
with the SET
commands.

The previous version limit was imposed by the maximum number of file
versions that would fit into one directory block. Directory logic
modifications in the file system now permit versions of a file to span

2-38

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
multiple blocks by using multiple records, each
name and type.
The versions of the file
descending lexical order.

containing the same
are still arranged in

This feature is an upward, but not downward, compatible change in
Files-11.
Downward compatibility does exist with the exception of the
following two results that may occur when disks are transported from
VAX/VMS Version 3.0 systems to earlier systems:
1.

On an earlier system, DIRECTORY and wild card operations will

return
multiple versions of a file that has multiple
directory records when you ask for wild card name or type and
latest version.
Other file operations on the directory will
function correctly.
2.

In previous versions of Files-11, versions
of a
file were
prevented from overflowing one block by setting the version
limit of the file to a value between 60 and 62, depending on
the length of the file name.
VAX/VMS Version 3.0 will create
new files with a version limit of 32767 (or the version limit
specified for the directory).
If you transport a disk written on VAX/VMS Version 3.0 to
an
earlier version of VAX/VMS, a directory may become corrupted
if you attempt to create more versions of a
file than will
fit
into one directory block.
Thus, some files will have
more than one directory entry.
If this
occurs,
remove all
the duplicate entries with the DCL command SET FILE/REMOVE.

VAX/VMS Version 2.5 contains a patch to the ACP that detects
the overflow correctly and exits cleanly with an error
leaving the directory intact. You can avoid this problem by
not exceeding 60 versions. Another work-around is to do a
SET FILE/VERSION_LIMIT=60 [*...]*.* on a disk that will be
transported to an old system. Note that the SET FILE command
must be executed on a new system;
it does not
exist on an
old system.
Note that existing files will not automatically benefit from
extended version limit of 60 because they were created by the
version of the file system (with a version limit of 60).
Thus,
new file system will continue to enforce this version limit.
increase the maximum versions of an old file,
use
the
FILE/VERSION LIMIT command.

2.9

the
old
the
To

SET

COMPATIBILITY MODE

The following sections contain notes on changes and additions to
functions that affect compatibility-mode programming on a VAX/VMS
Version
3.0
operating
system.
Documentation
describing
compatibility-mode programming is found in the following manuals:

2.9.1

•

VAX-11/RSX-11M User's Guide

•

VAX-11/RSX-11M Programmer's Reference Manual

VAX-11/RSX-11M User s Guide
f

Refer to the VAX-11/RSX-11M User's Guide for information about new
VAX/VMS MCR command qualifiers and indirect command file directives.

2-39

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
The following commands have been added to MCR:

RENAME
SET DAY
SET DIRECTORY
SET FILE

SET VOLUME
SHOW ERROR
SHOW MEMORY
SHOW USERS

It still affects
The SET /UIC command now has new behavior.
only if you have Change Mode
(UIC)
identification code
you do
if
(CMKRNL) privilege, but a message now appears
Your
sufficient privilege to change the UIC default.
default is always changed.

the

user

to Kernel

not have
directory

is
it
When the SET /UIC=[uic] command is echoed in a command file,
echoed as SET UIC [uic] without the slash and the equal sign, which
are stripped during parsing.

The APPEND, COPY, and TYPE commands each have
consistent with their VAX/VMS counterparts.

new

syntax

that

MCR supports the VAX/VMS Personal Mail Utility.
The following MCR commands used for native
are no longer supported by VAX/VMS MCR:

mode

•

LIBRARY - native mode Library utility

•

LINK - native mode linker

•

MACRO - native mode assembler

program

development

MCR supports neither the CTRL/T keyboard action nor the SET C0NTR0L=T
command that have been added to VAX/VMS DCL since VAX/VMS Version 2.0.
user authorization
the
If your default command interpreter (CLI) in
file
MCR and you log in requesting /CLI=DCL, do not use the DCL
is
command SPAWN or the Create Process ($CREPRC) system service to create
a subprocess specifying LOGINOUT as the image.

/BRIEF and /FULL are no
(qualifiers)
The LOGOUT command keywords
When you log out from an interactive
longer supported under MCR.
terminal session, the brief format appears. When a batch job logs
out, it writes the full format to the log file.

2.9.2

Compatibility Mode Support for Negative Version Numbers

Most compatibility mode utilities now support negative version numbers
Please note that VAX/VMS and RSX-11M
for Version 3.0 of VAX/VMS.
For example,
numbers are used.
version
differ as to how negative
the oldest (numerically
as
(-1)
RSX-11M interprets a negative 1
smallest) version number. Whereas, VAX/VMS interprets negative 1 (-1)
as the next most recent version number.

VAX/yMS
the
implement
correctly
Most RSX-11M utilities will
interpretation of negative version numbers. The ones that do not will
display a syntax errror for a negative version number.
All RSX-11M code using the standard RSX-11M Command String Interpreter
relinked against the new copies in
that
is
(CSI1
CSI2)
and
LB: [l,l]SYSLIB.OLB will work correctly.

2-40

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.9.3

VAX/VMS Compatibility Mode Software Modified

VAX/VMS compatibility mode software has been modified for Version 3.0
to
allow
RSX-11M
Version
3.2
programs, which meet certain
requirements, to run under VAX/VMS.
The VAX/VMS equivalent of the RSX-11M Disk Driver now supports the
Write Physical Block with Deleted Data Mark function, IO.WDD, for RX01
and RX02 diskettes.
Note that your process must have LOG_IO privilege
to
issue
this function.
When reading this type of physical block
using the Read Physical Block function, the success status of the I/O
is
IS.RDD instead of IS.SUC.
The VAX/VMS equivalent function for
IO.WDD is 10$ WRITEPBLK!IO$M DELDATA and the equivalent of IS.RDD is
SS$JRDDELDATA.
The VAX/VMS equivalent of the RSX-11M Terminal Driver now supports the
function SF.SMC to set the terminal type, TC.TTP characteristic, for
the following terminals:
LA36, LA120, LA34, LA38, VT05,
VT52,
VT55,
VT100,
VT101,
VT105,
VT102,
VT125, VT131,
and VT132.
The SF.SMC
function also supports the TC.BIN characteristic where no characters
are interpreted as control characters (PASSALL)

RSX-11M features added since RSX-11M
Version
3.2,
that
is,
functionality associated with RSX-11M Version 4.0 and RSX-11M-PLUS,
are generally not supported
for
other VAX/VMS compatibility mode
components.

RSX AME No Longer Installed by STARTUP.COM

2.9.4

SYS$SYSTEM:STARTUP.C0M no longer installs the RSX AME.
If
you have
compatibility mode applications that are installed with elevated
privileges, you must install SYS$SHARE:RSXSHR and SYS$SHARE:RSXUSR in
your SYSTARTUP.COM file.

2.9.5

Rooted Directory Restriction in Compatibility Mode

Compatibility mode programs, such as the File Transfer Utility (FLX)
and
user-written compatibility mode executable images, may not
recognize certain files in rooted directories.
In the following example, the default directory is
not apparent from the output of the DIR command:
$

rooted,

which

SHOW LOGICAL SYS$SYSR00T
SYS$SYSR00T =
DBA4: [SYSO.
SET DEF SYS$SYSR00T: [SYSTEST]
DIR FILE*.
]

$
$

Directory SYS$SYSR00T: [SYSTEST]
FILE1.;1

FILE2.;1

In the following command line, FLX will fail to find FILE2 because
of
an
interaction between the implementation of rooted directories and
the file control system (FCS) processing of device names.:
$ MCR FLX TI:=FILE1.,FILE2./RS
FLX
Invalid RSX file spec
SY:FILE2.C0M
No such file

—

2-41

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
and the
The logical unit number's (LUN) default assignment of SY:
no
because
files
input
the
for
used
are
current directory [SYSTEST]
explicit device and directory are specified. The problem occurs when
you have a rooted directory in a compatibility mode program, because
name that describes not
is a logical
the implicit device name SY:
FCS
above as [SYSO.]).
(shown
directory
root
the
only the device, but
specification
file
first
the
resolves
correctly
FLX
in
FCS assigns the LUN to
to DB4: [SYSO. SYSTEST] FILE1.
SY: [SYSTEST]FILE1
But, in parsing the
copied.
correctly
is
file
device DB4:. The first
default device is
the
LUN,
same
the
using
specification,
second file
The default
nowDB4:, because of the previous LUN assignment.
of
specification
file
a
yielding
used,
directory of [SYSTEST] is still
The
information.
"[SYSO.]"
the
lost
FCS
has
[SYSTEST]FILE1.
DB4:
second file is actually named DB4: [SYS0.SYSTEST]FILE2 and is therefore
not found.
To avoid this problem, explicitly state a device, either a real device
For example, FLX
logical name that resolves to a device name.
a
or

will correctly execute the following command line because
is stated:
(SY:

the

device

)

MCR FLX TI:=SY:FILE1.,FILE2./RS

This rooted directory problem can also occur with user-written
programs. When the default directory is rooted, and FCS parses two or
more file specifications on the same LUN, without specifying an
explicit device and directory, only the first file specification will
be correctly parsed.
Again, to avoid this problem, explicitly name a device in both file
in a MACRO-11 program by using a
You can do this
specifications.
default file name block specifying device SYO:.

SYSTEM PROGRAMMING

2.10

following sections contain notes that describe changes and
The
additions to the system components used by VAX/VMS system programmers.
The documentation for system programming under VAX/VMS Version 3.0 is
found in the following manuals:
•

VAX/VMS Real-Time User's Guide

•

VAX/VMS Guide to Writing

•

VAX/VMS System Dump Analyzer Reference Manual

•

VAX- 11 PATCH Utility Reference Manual

2.10.1

Device Driver

TM03 FCO Required

Read the following information if you have
drive installed on your system.

TE16, TU45, OR TU77

tape

Version 3.0 of VAX/VMS contains a new TMDRIVER. When you use this new
in conjunction with a hardware FCO to the TM03 tape formatter,
driver
you will correct a problem that used to cause the system to hang until
(1) completed the rewind, or (2) was
rewinding tape drive either:
a
manually put offline. The system manager should ensure that the FCO
installed before you install VAX/VMS Version 3.0 to enable the
is
manager does not
If the system
updated software to work correctly.

2-42

2.5
DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION

unclearable
install the FCO before installing VAX/VMS Version 3.0,
(The
terminates.
system hangs will occur until a rewind in progress
2.0
Version
VAX/VMS
previous
the
FCO will not adversely affect
TMDRIVER.)
Installations in the field have one
The FCO number is M8909YA-R-0006.
in their TM03 tape formatters:
boards
M8909YA
the
of three versions of
a
is applied to
revision H, revision J, or revision K. When this FCO
is
it
when
and
HI;
level
to
board
the
brings
it
revision H board,
The
level Jl.
applied to a revision J board, it brings the board to
revision
because
board
K
FCO does not need to be applied to a revision
K boards already have the FCO built into them.

2.10.2

Remote Terminals Support New Terminal Driver Features

are supported
For Version 3.0 of VAX/VMS, all terminal driver features
by the remote terminal driver.

VAX/VMS Version 2.0
However, the server system (of systems supporting
features when
following
the
remote terminal protocol) does not support
command:
performing the SET HOST
•

Out-of-band ASTs

•

Extended characteristics
SET MODE or SET CHARACTERISTICS
For the P2 parameter of a
If 12
zero or eight bytes.
supports
server
function, the
the
but
returned,
is
INCOMPAT
SS$
the
requested,
bytes are
The
RTTDRIVER.
by
additional longword is saved in the host
the
in
set
are
bits
if
returned
be
SS$ INCOMPAT code will also
for
defined
not
are
that
characteristics
of
second longword
(for
(Note that for informational bits,
VAX/VMS Version 2.0.
12-byte SET MODE will function as
the
ANSI),
example,
the bit is maintained in RTTDRIVER
because
is
This
expected.
indicate to the program that the terminal has the
and will
ANSI characteristic even though the server is not aware of the
bit.)

•

Terminal maintenance functions

that the
The RTTDRIVER at the Version 3.0 host system recognizes
with
function
the
completes
server cannot support the new features and
an alternate success code, SS$_INCOMPAT.

2.10.3

Reassemble and Relink All Drivers

all
current customer, you must reassemble and "link
Device
3.0.
Version
VAX/VMS
install
you
user-written drivers after
reassembled
drivers that you have in your distribution kit have been
with every
relinked
Drivers must be reassembled and
relinked.
and
version
"Pa ate s
because
updates,
version upgrade but not with version
and
reassembled
a
not
EXE),
(SYS.
image
system
include a patched
relinked executive.
If you are a

modified with
The sizes of the CRB and device-independent UCB are
instead
Version 3.0 of VAX/VMS. Therefore, drivers that use constants
the
until
properly
function
of CRB$L INTD and UCB$K LENGTH, will not
their
of
sizes
new
the
reflect
to
updated
constant? have been
not use constants in place of
Do
respective data structures.
symbolically defined data structure offsets and values.

2-43

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
2.10.4

Device-Dependent IOSB Field by Disk Drivers: New Behavior

For user-written disk drivers note and conform to the new IOSB format
described in the VAX/VMS I/O User's Guide.
,

2.10.5

All DDT and FDT Addresses Relocated by Driver Loading Procedures

The SYSGEN driver loading procedures now relocates all driver-relative
offset-addresses in the driver dispatch table and the function
decision table to system virtual addresses.
Device drivers do not
normally use these tables. User-written drivers that use the address
information in these tables
assume
and
the
values
to
be
driver-relative offsets, will not work properly under VAX/VMS Version
3.0.
(Before Version 3.0 of VAX/VMS, the correct method for using DDT
and
FDT addresses allowed for both driver-relative offset-addresses
and
system virtual addresses.)
The following code segment from
IOC$INITIATE, which locates and transfers control to a driver's
start-I/0 routine, is an example of how DDT and FDT addresses should
be handled:

20$:

M0VL
ADDL3
BLSS
SUBL
JMP

..., R0

DDT$L_START(R0) ,R0,R1
20$
R0 r Rl
(Rl)

;GET ADDRESS OF DRIVER DISPATCH TABLE
;CALCULATE ADDRESS OF START ENTRY POINT
;IF LESS, CORRECT ADDRESS CALCULATED
;ELSE, DDT ADDRESS WAS SYSTEM VIRTUAL
;TRANSFER TO START I/O ROUTINE

Beginning with VAX/VMS V3.0, the following will be equivalent.
MOVL
JMP

. . .

,R0

;GET ADDRESS OF DRIVER DISPATCH TABLE
; TRANSFER
TO START I/O ROUTINE

$DDT$L START (R0)

Beginning with VAX/VMS V3.0, however, the following will not work.
MOVL
ADDL3
JMP

2*10.6

..,R0

DDT$L_START(R0),R0,R1
(Rl)

Multiple Modules in

;GET ADDRESS OF DRIVER DISPATCH TABLE
;CALCULATE ADDRESS OF START ENTRY POINT
;TRANSFER TO START I/O ROUTINE

Device Driver

you have multiple modules
in
a
device driver, ensure that
invocations of the DPTAB, DDTAB, and FUNCTAB MACROS occur within the
same module.
If they do not occur
within the same module, system
failures will occur when the driver is loaded initially or when the
first QIO request is processed.
If

2.10.7

UNIBUS Memory on a UNIBUS Adapter

VAX/VMS now allows you to have UNIBUS memory on a UNIBUS adapter.
This support includes the ability to bootstrap VAX/VMS from a UNIBUS
device on the same adapter as the memory and is subject to the
following restrictions:
•

All memory on an adapter must be contiguous.

•

The starting memory address must be zero.

•

The total amount of memory must be less than or equal
kilobytes.

2-44

124

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
from a UNIBUS
For the VAX-11/750, if you are bootstrapping
must use the
you
memory,
the
as
adapter
same
the
on
device
BOOT58 routines on the console media. The internal boot ROM
will function incorrectly with the UNIBUS memory installed.

•

VMB (the primary bootstrap) probes all the UNIBUS address space of the
UNIBUS adapter from which the system is bootstrapped in 2 kilobyte
the
VMB disables
For each bank of memory responding,
steps.
to
transfers
UNIBUS
allowing
thus
registers,
mapping
corresponding
the
initialized,
When VAX/VMS is
take place at higher addresses.
initialization routines again probe UNIBUS address space for
adapter
each UNIBUS adapter present, disabling the corresponding mapping
In addition, the information stored in the adapter control
registers.
updated to reflect the permanent
is
block (ADP) for each adapter
allocation of these registers.
For user-written software that accesses this UNIBUS memory,
need to allocate the required SPTs and map the memory.

you

only

Autoconfiguration Default Units and Unit Delivery

2.10.8

UNIBUS
The SYSGEN autoconfiguration facility provides two features for
A
routines.
action
unit-delivery
and
(2)
devices:
(1) default units
of
configuration
automatic
the
control
can
features
these
using
driver
Parameters stored in the driver prologue
services.
it
the devices
the VAX/VMS
See
table control the exact operation of both features.
information.
complete
for
Driver
Device
a
Guide to Writing

ANALYZE/CRASHJMJMP (SDA) Help Text Not Updated

2.10.9

reflect new features
The help text for ANALYZE/CRASH_DUMP does not
System Dump Analyzer
VAX/VMS
the
See
2.0.
Version
VAX/VMS
since
added
Reference Manual for information on new features.

SYSTEM MANAGEMENT AND OPERATION

2.11

following sections contain notes that describe changes and
additions to system features that affect VAX/VMS system management and
The documentation for these features can be found in the
operations.
manuals:
following

The

•

VAX-11/730 Software Installation Guide

•

VAX-11/750 Software Installation Guide

•

VAX-11/780 Software Installation Guide

•

VAX/VMS System Management and Operations Guide

•

VAX/VMS UETP User's Guide

•

VAX-11/782 User's Guide

2.11.1

System Directories Have Moved

has been changed
In VAX/VMS Version 3.0, the system disk organization
a single disk.
on
be
to
systems
bootable
separately
to allow multiple,

2-45

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
This feature is implemented by placing a level of directory between
the
Master File Directory and the system directories, [SYSERR]
[SYSEXE],
[SYSHLP]
[SYSLIB]
[SYSMAINT] ,
[SYSMGR] ,
[SYSMSG]
[SYSTEST]
[SYSUPD] .
and
VAX/VMS Version 2.0, these system
(In
directories were all cataloged in the Master File Directory (MFD)
along with any user/installation management directories.)
f

In VAX/VMS Version 3.0, the system directories are moved
out of the
and
in their place is one or more system root directories of the
form SYSx, where x is the hexadecimal digit 0-F.
A system root

MFD

directory catalogs all the system directories for that system. These
system directories are now referenced through the new rooted device
name SYS$SYSROOT.
They may no longer be referenced by such names as
DRAO: [SYSMGR]

With the advent of System Root Directories in Version 3.0, two logical
names replace SYS$SYSDISK
(formerly the name of the system disk
containing system directories
and
user/installation
management
directories)
1.

SYS$SYSDEVICE is the physical device containing the user
installation management directories.

and

SYS$SYSROOT is the device and root directory
currently running set of system directories.

the

for

DIGITAL software no longer requires the logical name SYS$SYSDISK.
If
you used this logical name, you used it in one of the following ways:
1.

To
reference
system
SYS$SYSDISK: [SYSMGR].

To reference user and installation management directories
the system disk, for example, SYS$SYSDISK: [PUBLIC]

For both of the above.

directories,

example,

for

The STARTUP.COM command procedure has the definition:
$

DEFINE /SYSTEM SYS$SYSDISK SYS$SYSR00T:

This definition will make the first type of reference work correctly.
If
you used
SYS$SYSDISK in the second way, modify the installation
SYSTARTUP.COM to redefine SYS$SYSDISK as follows:
$

DEASSIGN /SYSTEM SYS$SYSDISK
DEFINE /SYSTEM SYS$SYSDISK SYS$SYSDEVICE:

If you used SYS$SYSDISK in the third way, eliminate one
of the ways
you use SYS$SYSDISK.
If you do not need the logical name SYS$SYSDISK,
deassign it in SYSTARTUP.COM.

You will no longer be able to access the system directories using
names such as DRAO: [SYSMGR]
All system directories that did not have
logical names in Version 2.0 of VAX/VMS have been given logical names
for Version
3.0.
See
the VAX/VMS System Management and Operations
Guide for these logical names.
.

The compatibility mode directories [1,1] and [1,2], which are synonyms
for
[SYSLIB]
and [SYSMSG], respectively, have also moved.
This will
be transparent to compatibility mode software
that references these
directories on the conventional logical device LB (or LB0).
The System Root Directory F (SYSF) is reserved for
use
upgrade procedures.
It must not be used by customers.

2-46

VAX/VMS

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
Because the system directories are no longer at the same level as the
installation and user directories in the directory tree, you should
ensure that command procedures correctly reference both kinds of
the command procedure SYSTARTUP.COM may
For example,
directories.
contain references to the installation directory [SYSMGR] and the user
Therefore,
Your default device is SYS$SYSR00T.
directory [PUBLIC].
[PUBLIC]
SYS$SYSDEVICE:
form
the
take
should
the reference to [PUBLIC]
since SYS$SYSR00T: [PUBLIC] does not exist.

2.11.2

SYS$EXAMPLES Points to VAX/VMS Examples

For VAX/VMS Version 3.0, the system-wide logical name SYS$EXAMPLES has
been created to point to the directory of VAX/VMS examples (formerly,
the
It is similar to SYS$SYSTEM, which points to
[SYSHLP. EXAMPLES]) .
images.
VAX/VMS
of
directory

2.11.3

WSQUOTA and WSEXTENT for User Accounts

VAX/VMS Version 3.0 now supports working sets larger
Use WSEXTENT for the upper limit on working set sizes.

than

WSQUOTA.

lower the value of
upgrading from a Version 2.5 system,
than the original
larger
WSEXTENT
of
value
the
make
WSQUOTA and
WSQUOTA value.
If you are

2.11.4

Bootstrapping with an Alternate STARTUP Command Procedure

bootstrap your system and want to avoid autoconf iguring
devices or invoking SYS$MANAGER: SYSTARTUP.COM, bootstrap, stop in
SYSB00T, and issue the following command:
If you need to

all

SYSBOOT>SET/STARTUP SYS$SYSTEM: STARTUP. MIN
Note that the start-up file
directory, such as SYS$SYSTEM.

2.11.5

must

have

explicit

device

and

Installation on Multiple UNIBUS Systems

During software installation, ensure that each UNIBUS (up to the one
has exactly one disk controller of the same type
being bootstrapped)
as the one being bootstrapped.

2.11.6

Librarian Shareable Image (LBRSHR) Increased
(LBRSHR)

has

been

Therefore, you must relink images under VAX/VMS Version 3.0
linked with LBRSHR.

that

are

The size of the VAX/VMS Librarian shareable image
increased for Version 3.0.

2.11.7

VAX/VMS Version 3.0 SYSGEN Parameters

Version 3.0 of VAX/VMS, the xxUSER.PAR,
MINIMUM. PAR files are no longer distributed.
For

2-47

and
VIRT32MB.PAR,
A general mechanism

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
is
file using the autogen procedure)
(which edits the params.dat
SYSGEN will
included for setting the values of SYSGEN parameters.
still read old customer parameter files and provide a way to create
new files.
Many of the SYSGEN parameter default values and minimum
SYSGEN to display these new
Use
and maximum values have changed.
values.

SYSGEN
2.11.7.1 SYSGEN Parameter AWSMAX No Longer Needed - The
parameter AWSMAX has been removed for Version 3.0 of VAX/VMS. You can
accomplish the same function by adjusting the working set extent on a
process-by-process basis.

2.11.7.2 SYSGEN Parameter RMS_DCMBIDX Changed - The SYSGEN
RMS_DCMBIDX has been changed to RMS_DFMBIDX.

parameter

MPW_HILIM Changed - The SYSGEN

parameter

2.11.7.3

SYSGEN

Parameter

MPWJHLIM has been changed

to MPW_HILIMIT.

MPW_WAITLIMIT - If
and
MPW_HILIMIT
Parameters
2.11.7.4 SYSGEN
MPW_HILIMIT is increased MPW_WAITLIMIT may also need to be increased
because a system deadlock will occur if MPW_WAITLIMIT is less than
MPW_HILIMIT.
(The value of MPW_HILIMIT is normally equal to the value
of MPW WAITLIMIT.)
,

2.11.7.5 SYSGEN Parameters DIALTYPE and TTYSCANDELTA Changed - The
SYSGEN parameters DIALTYPE and TTYSCANDELTA have been changed to
TTY DIALTYPE and TTY SCANDELTA.

2.11.8

SWAPFILE.SYS and PAGEFILE.SYS

During software installation or upgrade, the files SWAPFILE.SYS
PAGEFILE.SYS have been set to sizes appropriate for your system.

and

If you are upgrading your system, your new PAGEFILE.SYS may be smaller
than the previous PAGEFILE.SYS.
In this case, purge the previous file
after the upgrade is complete.

The PAGEFILE.SYS size is also important for a correctly operational
system.
If this file is too small for your typical workload, overall
system performance will suffer. As performance becomes significantly
affected, the message %SYSTEM-W-PAGEFRAG is printed on the system
significantly underconf igured for
console.
If paging file space is
the message %SYSTEM-W-PAGECRIT is printed on the system
system load,
console and a system hang could result.

specific
and your
The guidelines given here are initial guidelines,
needs may vary significantly from the given formulas. You can further
understand your needs related to paging and swapping files by using
the
DCL command SHOW MEMORY with the system under load and looking at
the usage of these files.
SHOW
a
For SWAPFILE.SYS the file size is too small if the results of
MEMORY command indicate that the total space in the swapfiles is more
than three-fourths used.

2-48

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
SHOW
For PAGEFILE.SYS the file size is too small if the results of a
MEMORY command indicate that the total space in the page files is more
than one-half used.
If these file sizes are overconf igured,

the only consequence

lost

disk space.

2.11.9

Mount Verification Canceling

VAX/VMS Version 3.0 supports a new feature called Mount Verification,
which permits the system to recover from errors such as a disk going
and
suspended,
I/O to the disk is
offline or becoming wr ite-locked.
messa ges are issued to the system console and operator terminals to
alert the operator of the problem. When the problem is corrected, I/O
operations to the disk are resumed.
operation is in
If a disk goes into mount verification while a file
if this ACP is
possible for the file ACP to hang;
is
it
progress,
will
operation
system
also the file ACP for the system disk, most
in
back
disk
defective
the
you should put
this case,
In
hang.
follows:
as
process,
verification
mount
the
service, or cancel
specific to your processor, on the
Issue the following commands,
mount verification canceling
a
invoke
commands
(These
console.
routine.)

VAX-11/780

VAX-11/750

-p

>»HALT
»>D/I 14 C

VAX-11/730
-p

>»D/I

>»D/I 14 C
>»C0NT

14 C

>>>C0NT

>>>>CONT
This prompt indicates that the
You will then receive the prompt IPO.
Issue
is
ready to accept input.
routine
canceling
mount verification
any of the following three commands: C device, X, or *Z (CTRL/Z)

Command

Function

C DBAO:

Cancels any pending mount verification on the
specified device (in this case, DBAO:) or issues a
warning if there was no mount verification in
progress for the specified device.

Transfers control to XDELTA if XDELTA has been
(XDELTA must be loaded at
loaded with the system.
to
the VAX/VMS Guide
See
time.
system bootstrap
Writing a Device Driver for more information.) If
XDELTA has not been loaded, the prompt IPO will
be issued again.

Causes the verification canceling routine to exit
transfers control back to what was previously
and
in progress.

There are some special characteristics of the command processor
the mount verification canceling routine that should be noted.
•

All lowercase characters are converted to uppercase.

•

All illegal characters (such as most control characters)
not typed and are signaled by the terminal s "bell".
1

2-49

for

are

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

•

All leading spaces are ignored and not echoed.

•

Multiple spaces are compressed into a single space.
(This
is
done by ignoring any consecutive space characters after the
first.)
NOTE

Mount verification will automatically be
canceled
SYSGEN
if
the
parameter
MVTIMEOUT is set before the disk goes
into
mount
verification.
(This
parameter is the amount of time to wait
before canceling a mount verification.)
Please note that mount verification does
not time out for write-lock errors.
To
cancel write-lock
verification,
use
either the mount verification canceling
routine outlined above or write-enable
the disk.

2.11.10

Mount and Dismount Notification Messages

A new feature has been added for VAX/VMS Version 3.0 to aid system
managers and operators in determining when disks and magnetic tapes
are mounted and dismounted.

You can enable mount and dismount messages by setting the SYSGEN
parameters MOUNTMSG and DISMOUMSG to one, respectively. To disable
these messages, set the SYSGEN parameters to zero.

Because of the method in which these messages are sent to the enabled
operators, there may be as much as a thirty second delay before the
message is sent.
In addition, the message will always
indicate that
the user sending the message is SYSTEM.

2.11.11

OPCOM Request Canceled

image issues an operator request that requires a reply
(through
$SND0PR system service)
and
the
is
image
run down without
explicitly canceling the request, the request will still appear to be
active.
However,
if an operator makes a reply to the request, OPCOM
will detect that the request has been canceled,
and
issue an
informative message.
If an

the

2.11.12

VAX-11 COBOL-74: System-wide Logical Name Assignments

For Version 3.0 of VAX/VMS, the system-wide logical name assignments
made in SYS$SYSTEM :STARTUP.COM for VAX-11 COBOL-74 have been removed.
If you are running VAX-11 COBOL-74 Version 4.3 or an earlier
version,

2-50

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
you will need to edit SYS$MANAGER: SYSTARTUP.COM and add the
logical name definitions:
$
$

$
$

!
!

Assign COBOL systemwide logical names

ASSIGN
ASSIGN
ASSIGN
$ ASSIGN
$ ASSIGN
$ ASSIGN
$ ASSIGN
$
$

2.11.13

following

/SYSTEM
/SYSTEM
/SYSTEM
/SYSTEM
/SYSTEM
/SYSTEM
/SYSTEM

SYS$INPUT: C0B$INPUT
SYS$OUTPUT: C0B$0UTPUT
SYS$ERR0R: C0B$C0NS0LE
SYS$INPUT: COB$CARDREADER
SYS$INPUT: COB$PAPERTAPEREADER
SYS$OUTPUT: COB$LINEPRINTER
SYS$OUTPUT: COB$PAPERTAPEPUNCH

VAX-11 DIBOL Installation Restriction

When you install VAX-11 DIBOL on the current system disk, assign the
Likewise, when you install
logical name SYS$SYSDISK to SYS$SYSR00T.
rooted
directory
the
include
VAX-11 DIBOL on another disk,
specification in the reassignment of SYS$SYSDISK (as described in the
installation guide)

2.11.14

Bootstrapping with

VAX/VMS Version 2.0 VMB

support
Version 2.0 of VAX/VMS does not
in
The VMB released
bootstrapping the rooted directory structure of VAX/VMS Version 3.0.
Therefore, two special directories and a synonym have been added to
and [SYSEXEJSYSBOOT.EXE
[SYSEXEMIN] , [SYSEXE]
the
installed system:
These alternate names
[SYS0.SYSEXElSYSBOOT.EXE).
(a
synonym for
provide a way for Version 2.0 VMBs to locate the Version 3.0 SYSBOOT
image and bootstrap the system.
,

However, the next major release of VAX/VMS will remove these
and the Version 2.0 VMB will no longer bootstrap VAX/VMS.

2.11.15

synonyms

Installing EDTCAI on VAX/VMS Version 2.5 Systems

If you already have EDTCAI
installed on your VAX/VMS Version 2.5
system,
and you upgrade your system from Version 2.5 to Version 3.0,
convert your roster
the installation of EDTCAI on Version 3.0 will
file to the Version 3.0 format.

However, before you install EDTCAI, ensure that the definition of the
If
logical name EDT$CAI
correct for your Version 3.0 system.
is
([SYSLIB])
in
EDT$CAI was equated to the system library directory
Version 2.0,
use
the following command to change it to SYS$LIBRARY:
on your Version 3.0 system:
$

DEFINE EDT$CAI SYS$LIBRARY:

Then, you can perform the installation of EDTCAI.

Note that the logical name EDT$CAI will not be needed on your Version
Therefore, you can remove it from your SYSTARTUP.COM.
3.0 system.
(The EDTCAI files are found in SYS$INSTRUCTION on Version 3.0.)

2-51

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5

NETWORKING

2.12

rules
The following sections contain notes that describe networking
information
more
providing
documentation
The
for VAX/VMS Version 3.0.
is located in the following manuals:
•

DECnet-VAX System Manager's Guide

•

DECnet-VAX User's Guide

•

DECnet-VAX Cross-System Notes

•

DECnet-VAX Software Installation Guide

2.12.1

DECnet-VAX System Manager's Guide

The following formulas apply to the DMP for Version 3.0 of
complete description of these parameters, see
For
a
Synchronous Controller Technical Manual .

Line retransmit timer

20000

VAX/VMS.
the DMP

(in msec):

MAX MESSAGE SIZE

RTT =

+ RTS/CTS MODEM DELAY

LINE SPEED IN BPS
NOTE: The Request to Send/Clear to Send
coax lines can be ignored.
2.

(RTS/CTS) modem delay for

Line dead timer (in msec):
1000

MAXIMUM DELAY IN SECONDS BEFORE A NODE IS RECOGNIZED

DET »

MAXIMUM NUMBER OF DEAD TRIBUTARIES
NOTE: For best results this should be set as high as possible.
3.

Line delay timer

(in

msec):

DEL =
FOR COAX.
;
DEL = 50 ; FOR MULTIPOINT EIA LINES.
DEL = 200 ; IF ANY SOFTWARE IMPLEMENTATIONS OF DDCMP ARE
ON THE MULTIPOINT LINE.
;
NOTE: In the event that more than one condition is true, the largest
value must then be applied.

2.12.2

DECnet-VAX Events Not Downward Compatible

The format of DECnet-VAX event records that can be transmitted between
if
you log
Therefore,
DECnet-VAX
systems
has been extended.
DECnet-VAX events to a previous version of the DECnet-VAX event
logging process, this previous version may not recognize certain newer
The event logging
events, such as "circuit down" or "circuit up".
process will not be able to process a "circuit" because "circuits" did
not exist in previous versions of DECnet-VAX.

are only sent
To avoid such problems, ensure that DECnet-VAX events
between nodes of the same version. For example, in the following

2-52

DIFFERENCES BETWEEN VAX/VMS VERSION 3.0 AND VAX/VMS VERSION 2.5
situation, ensure that the VAX2 sink node is using the same version of
DECnet-VAX software as the current node.
NCP> SET LOGGING MONITOR SINK NODE VAX2 KNOWN EVENTS

2.12.3

DMP11 Default Parameter Settings

The VAX/VMS Version 3.0 default line parameter settings for the
device driver are listed below:

NCP KEYWORD

DEFAULT

Protocol
Duplex
Controller
Receive buffers
Stream timer
Scheduling timer
Dead timer
Delay timer
Retransmit timer

DDCMP point
full
normal

DMP11

6000 (milliseconds)
50 (milliseconds)
10000 (milliseconds)
(milliseconds)
3000 (milliseconds)

The VAX/VMS Version 3.0 default tributary parameter settings
DMP11 device driver are listed below:

NCP KEYWORD

DEFAULT

Polling state
Babble timer
Transmit timer
Maximum buffers
Maximum transmits
Active base
Active increment
Inactive base
Inactive increment
Inactive threshold
Dying base
Dying increment
Dying threshold
Dead threshold

automatic
6000 (milliseconds)
(milliseconds)

for

the

255
4

255

64
8

16
2

In order to perform a down line load, the EXECUTOR BUFFER SIZE must be
least as large as the Secondary Loader file which will be used in
at
device
For example, if the remote load
the down line load operation.
The
bytes.
512
least
at
be
must
SIZE
BUFFER
EXECUTOR
is
a DMC11, the
Loader
Secondary
the
of
each
for
needed
size
the
gives
list
following

files:

REMOTE DEVICE

SIZE IN DECIMAL BYTES

DMC11
DUP11
DUV11
DU11
DP11
DMP11
DQ11

512
576
576
576
576
640
768

2-53

APPENDIX A
PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

This appendix contains listings of the journal files for patches
applied to the VAX/VMS Version 3.0 system after the source Microfiche
Kit was manufactured.

A-l

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE] AUTHORIZE, EXE; 1"
"DISK$RES26APR: [SYSEXE] AUTHORIZE. JNL; 1"
3-MAY-1982 15:38:05.98

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>SET ECO 1
PATCH>SET MODE BYTE
PATCH>DEP 3C5A==11
0FB
00003C5A:
old:
00003C5A:
11
new:
PATCH>DEP 3C5B=13
00003C5B:
03
old:
00003C5B:
13
new:
PATCH>DEP 5F57==01
00005F57:
00
old:
00005F57:
01
new:
PATCH>DEP 5F64=27
00005F64:
26
old:
27
00005F64:
new:
PATCH>DEP 634A==01
0000634A:
00
old:
0000634A:
01
new:
PATCH>DEP 6357==27
26
00006357:
old:
00006357:
27
new:
PATCH>DEP 6714==01
00006714:
00
old:
00006714:
01
new:
PATCH>DEP 6721 =27
00006721:
26
old:
27
00006721:
new:
PATCH>DEP 6B50 ==01
00006B50:
00
old:
00006B50:
01
new:
PATCH>DEP 6B5D=27
00006B5D:
26
old:
00006B5D:
27
new:
PATCH>UPDATE
Updating image file DISKSRES26APR: [SYSEXE JAUTHORIZE.EXE;
PATCH>EXIT
=

A-

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF * PATCH:

"DISK$RES26APR: [SYSEXE1CNDRIVER.EXE;
"DISK$RES26APR: [SYSEXE]CNDRIVER.JNL;1"
4-MAY-1982 13:34:37.61

Image does not contain local symbols
PATCH>SET ECO 1
PATCH>REPL/INST 958
OLD> "BBSS #09,B*5C(R4),97F"
OLD> EXIT
NEW> "BBSS #09,B*5C(R4),96B"
NEW> EXIT
#09,B"5C (R4) ,0000097F
BBSS
00000958:
"idA
#09,B 5C (R4) ,0000096B
BBSS
00000958:
new
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE1CNDRIVER.EXE;
PATCH>EXIT
;

A-3

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
PATCH Version 3-00 15-Mar-1982
IMAGE PILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXEJDUDRIVER.EXE;1"
"DISK$RES26APR: [SYSEXEJDUDRIVER. JNL;l f
3-MAY-1982 15:39:23.51

Image does not contain local symbols
PATCH>SET ECO 1
PATCH> replace/word A x8 - A xlD97
NEW> A xlE00
NEW> exit
.$$ABS$$.+8:
.$$ABS$$.+8:

old:
new:

PATCH>replace/long
A
NEW>
x60
NEW> exit

xlD98 *

old:
new:

PATCH>replace/long
NEW> "xlDAO
NEW> exit

1D97
1E00

00001D98:
00001D98:

00000000
00000060

00001D9C:
00001D9C:

00000000
00001DA0

xlD9C =

old:
new:

PATCH>set patch_area 1D98
PATCH>replace/instruction
NEW>
'pushl
NEW>
beql
NEW> exit

•

xOFD7+ x58

•pushl b 20(r5)*
A
b 20(r5)'
A
A
xl000+ x58'
A

0000102F:
B 20(R5)
PUSHL
BRW
PAB
0000102F:
A
PAB:
PUSHL
B 20(R5)
BNEQ
00001DA3:
00001DA8
00001DA5:
BRW
00001058
00001DA8:
BRW
00001032
A
A
PATCH>verify/instruction x484+ x58 = *addl3 rl f §#80002858, 18 (rO)
A
Rl, $#80002858,
000004DC: ADDL3
old:
18 (R0)
A
A
PATCH>replace/ instruct ion xlA00+ x58 = 'addl2 r5,r0'
NEW> »addl2
r5,r0«
A
NEW>
b 18(rO),r3'
•movl
A
A
A
NEW>
xlAE9+ x58,b lC(r3)'
movab
A
NEW>
movzwl
b 2A(rO),rl'
A
NEW>
'addl3
rl,e#80002858,b 18(r3)*
NEW> exit
00001A58:
ADDL2
R5,R0
old:
new:
BRW
00001DAB
00001A58:
new:
00001DAB: ADDL2
R5,R0
A
00001DAE:
MOVL
new:
B 18(R0),R3
A
A
new:
00001DB2:
MOVAB
L 00001B41,B 1C(R3)
A
new:
00001DBA:
MOVZWL B 2A(R0),R1
A
Rl, §#80002858,
new:
00001DBE:
ADDL3
18(R3)
BRW
00001A5B
00001DC7:
new:
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXEJDUDRIVER. EXE;
PATCH>EXIT
old:
new:
new:
new:
new:
new:

•

A-4

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
PATCH Version 3-00 15-Mar -1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE] F11AACP. EXE ;
"DISK$RES26APR:[SYSEXE]FllAACP,JNLjl"
3-MAY-1982 15:40:03.49

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>DEFINE EC01_DIRACC«0
symbol "EC01JURACC" defined as 00000000
PATCH>DEFINE ECOl MRKINC»0
symbol "EC01_MRKlFTC" defined as 00000000
PATCH>DEFINE ECOl_MRKCTH=0
symbol "ECOl MRKCTH" defined as 00000000
PATCH>SET EC5 1
PATCH>REPLACE 48F0»0
NEW> 0F8
NEW> EXIT
00000000
000048FO:
old:
000000F8
000048F0:
new:
PATCH>REPLACE 48F4«0
NEW> 48F8
NEW> EXIT
00000000
000048F4:
old:
000048F8
000048F4:
new:
PATCH>SET PATCH AREA 48F0
PATCH>DEFINE ECtfl DIRACC-1AD4
symbol "ECOl DIRA^C" redefined from 00000000 to 00001AD4
PATCH>REPLACE/I ECOl DIRACC+0DC
'MOVL R0,W~23C T
OLD>
OLD> EXIT
•MOVL R0,W*23C
NEW>
NEW> •BNEQ ECOl DIRACC+0E1'
NEW> •CHMU #2Al7'
•RET*
NEW>
NEW> EXIT
R0,VT0000023C
MOVL
00001BB0:
old:
PAB
BRW
00001BB0:
new:
NOP
00001BB3:
new:
00001BB4: NOP
new:
R0 r VT0000023C
MOVL
PAB:
new:
00004902
BEQL
000048FD:
new:
00001BB5
000048FF: BRW
new:
I2A14
CHMU
00004902:
new:
RET
00004906:
new:
00001BB5
BRW
00004907:
new:
PATCH>DEFINE ECOl MRKINC-4A00+2DD
symbol "EC01_MRKINC" redefined from 00000000 to 00004CDD
PATCH>REPLACE/I EC01_MRKINC+30
MTPR #7, #12
OLD>
•MOVL BnOtRDfRO*
OLD>
•ADDL3 #10,B*4(AP),Rl
OLD>
OLD> EXIT
'MOVL B*10(R1),R0'
NEW>
NEW> •ADDL3 lOrB^APKRl
NEW> •MTPR #7, #12*
NEW> EXIT
MTPR
#07, #12
00004D0D:
old:
B*10(R1),R0
MOVL
00004D10:
old:
#10,B*04 (AP) ,R1
ADDL3
00004D14:
old:
A
B 10(R1),R0
MOVL
00004D0D:
new:
(AP) ,Rl
#10,B*04
ADDL3
00004D11:
new:
#07, #12
MTPR
00004D16:
new:
PATCH>REPLACE/I EC01_MRKINC+52
*BRB EC01_MRKINC+37
OLD>
OLD> EXIT
'BRB ECOl MRKINC+3C
NEW>
f

A-5

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
NEW>

EXIT

old:
new:

00004D2F:
00004D2F:

BRB
BRB

00004D14
00004D19

PATCH>DEFINE EC01 MRKCTH-4F00
symbol "ECOIJIRKCTH" redefined from 00000000 to 00004F00
PATCH>REPLACE/I EC01_MRKCTH+2
0LD>
'MTPR #7, #12'
OLD>
•MOVL B*4(AP),R0'
OLD> EXIT
NEW> •MOVL B"4(AP),R0*
NEW> •MTPR #7,112'
NEW> EXIT
old:
00004F02:
MTPR
#07, #12
old:
00004F05:
MOVL
B*04(AP),R0
new;
00004F02: MOVL
B*04(AP),R0
new:
00004F06: MTPR
#07, #12
PATCH>REPLACE/I ECOl MRKCTH+1E+2
0LD>
•MTPR #7, #12'
0LD> EXIT
NEW> •MTPR #0,#12'
NEW> EXIT
old:
00004F20:
MTPR
#07, #12
new:
00004F20:
MTPR
#00, #12
PATCH>REPLACE/I ECOl MRKCTH+3B+2
0LD>
•MTPR #7, #12'
OLD>
•MOVL B*4(AP) # R0
OLD> EXIT
NEW>
•MOVL B*4(AP),R0'
NEW> •MTPR #7, #12'
NEW> EXIT
Old:
00004F3D:
MTPR
#07, #12
old:
00004F40:
MOVL
B*04(AP),R0
new:
00004F3D:
MOVL
B*04(AP),R0
new:
00004F41:
MTPR
#07, #12
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE]FllAACP.EXEj?2
I

A-6

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

,•

'•DISK$RES26APR:[SYSEXE]F11BACP.EXE;1
1"
"DISK$RES26APR: [SYSEXE]F11BACP. JNL;
15:40:32.66
3-MAY-1982

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>DEFINE ECOl_MRKINC«0
symbol "EC01_MRKINC" defined as 00000000
PATCH>DEFINE ECOl MRKCTH=0
symbol "ECOlJtoKCTH" defined as 00000000
PATCH>SET ECO 1
PATCH>DEFINE ECOl MRKINC=8A00+2FD
symbol "ECOl MRKINC" redefined from 00000000 to 00008CFD
PATCH>REPLACf/I EC01_MRKINC+30
'MTPR #7, #12'
0LD>
•MOVL B~10(R1),R0'
OLD>
•ADDL3 #10,8*4^)^1'
0LD>
OLD> EXIT
•MOVL B"10(Rl) r R0
NEW>
•ADDL3 #10,B*4(AP),R1'
NEW>
•MTPR #7, #12'
NEW>
NEW> EXIT
#07, #12
00008D2D: MTPR
old:
B*10(R1),R0
MOVL
00008D30:
old:
#10,B*04(AP),R1
ADDL3
00008D34:
old:
Bn0(Rl),R0
MOVL
00008D2D:
new:
#10,B*04(AP),R1
ADDL3
00008D31:
new:
MTPR
#07, #12
00008D36:
new:
PATCH>REPLACE/I EC01_MRKINC+52
'BRB ECOl_MRKINC+37'
OLD>
OLD> EXIT
'BRB EC01_MRKINC+3C'
NEW>
NEW> EXIT
00008D34
BRB
00008D4F:
old:
00008D39
BRB
00008D4F:
new:
PATCH>DEFINE ECOl MRKCTH-8FF0
«^^«„
A
symbol "EC01_MRKCTH" redefined from 00000000 to 00008FF0
PATCH>REPLACE/I EC01_MRKCTH+2
'MTPR #7, #12'
OLD>
A
•MOVL B 4(AP),R0'
OLD>
OLD> EXIT
NEW> •MOVL B*4(AP),R0'
NEW> •MTPR #7, #12'
NEW> EXIT
MTPR
#07, #12
00008FF2:
Old:
B*04(AP),R0
MOVL
00008FF5:
old:
B*04(AP),R0
MOVL
00008FF2:
new:
MTPR
#07, #12
00008FF6:
new:
PATCH>REPLACE/I EC01_MRKCTH+lE+2
'MTPR #7 ,#12*
OLD>
OLD> EXIT
NEW> 'MTPR #0,#12'
NEW> EXIT
MTPR
#07, #12
00009010:
old:
MTPR
#00, #12
00009010:
new:
PATCH>REPLACE/I EC01_MRKCTH+3B+2
'MTPR #7, #12'
OLD>
'MOVL B*4(AP),R0'
OLD>
OLD> EXIT
'MOVL B*4(AP),R0'
NEW>
NBW> 'MTPR #7, #12*
NEW> EXIT
MTPR
#07, #12
0000902D:
Old:
B*04(AP),R0
MOVL
00009030:
old:
B~04(AP),R0
MOVL
0000902D:
l

new:

A-7

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
MTPR
#07 f #12
00009031:
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXEJF11BACP.EXE;
PATCH>EXIT

new:

A-8

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXEJLOGINOUT. EXE;1"
"DISK$RES26APR: [SYSEXE]LOGINOUT. JNL;!"
3-MAY-1982 15:41:02.50

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>SET ECO 1
PATCH>REPLACE/INSTRUCTION 0D98
0LD>
*BRB 0DD7'
OLD> EXIT
NEW>
»BRB ODDC*
NEW> EXIT
old:
00000D98:
BRB
O0O0ODD7
new:
00000D98:
BRB
00000DDC
PATCH>REPLACE/INSTRUCTION 0DA7
OLD>
*BRB 0DD7
OLD> EXIT
NEW> »BRB ODDC'
NEW> EXIT
old:
00000DA7:
BRB
00000DD7
new:
00000DA7:
BRB
O00O0DDC
PATCH>REPLACE/INSTRUCTION 0DB7
OLD> 'BNEQ 0DD7*
OLD> EXIT
NEW> 'BNEQ ODDC
NEW> EXIT
old:
00000DB7:
BNEQ
O0000DD7
new:
00000DB7:
BNEQ
00000DDC
PATCH>REPLACE/INSTRUCTION 0DC8
OLD>
'BBS #01,§#7FFE7C12,0DD7
OLD> EXIT
NEW>
•BBS #01,§#7FFE7C12,0DDC
NEW> EXIT
old:
00000DC8:
BBS
#01 r §|7FFE7C12,00000DD7
new:
00000DC8:
BBS
#01 f §#7FFE7C12 r 00000DDC
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXElLOGINOUT.EXE;
PATCH>EXIT
1

A-9

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar -1982
IMAGE PILE BEING PATCHED:
JOURNAL PILE:
DATE/TIME OP PATCH:

"DISK$RES26APR: [SYSEXEJMP.EXE ; 1"
•DISK$RES26APR: [SYSEXEJMP. JNL;1"
3-MAY-1982 15: 41: 25,99

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>DEPINE ECOl INT »
symbol "ECOl INT"~def ined as 00000000
PATCH>SET ECO 1
PATCH>DEP ECOl INT-~X00000D90
symbol "ECOl~INT* redefined from 00000000 to 00OOOD9O
PATCH>RE /I
LOO *X00000P8F
OLD>
•CMPB R2,R3»
•BEQL "X00000F99
0LD>
0LD>
•MOVB R2,R3'
OLD> •BRB "X00000P6A*
OLD> EXIT
•ADAWI #*X00000000,(R4)'
NBW>
NEW> •CMPL RljB^XOOOOOOlO^)
NEW> •BNEQ ECOl INT+1DA
NEW> EXI
00000F8F: CMPB
old:
BEQL
00000F92:
old:
MOVB
00000F94:
old:
BRB
00000P97:
old:
00000P8F: ADAWI
new:
00000P92: CMPL
new:
BNEQ
00000F96:
new:
00000F98: NOP
new:
PATCH>U
Updating image file DISK$RES26APR: [SYSEXEJMP. EXE; 2
PATCH>EXI
1

A-10

R2,R3
00000P99
R2,R3
00000F6A
#00, (R4)

R1,B*10<R4)
00000P6A

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE]PUDRIVER.EXE;1"
"DISK$RES26APR:[SYSEXE]PUDRIVER.JNL;l i
5-MAY-1982 18:16:09.81

Image does not contain local symbols
PATCH>SET ECO 1
PATCH> replace/word *x8 = "xOB2A
NEW> "xOCOO
NEW> exit
old:
new:

PATCH>replace/long ~x0B2C =
NEW> *x00C0
NEW> exit
old:
new:

.$$ABS$$,+8:
.$$ABS$$.+8:

0B2A
0C00

00000B2C:
00000B2C:

00000000
000000C0

00000B30:
00000B30:

00000000
00000B34

PATCH>replace/long *x0B30 =
NEW> ~xOB34
NEW> exit
old:
new:

PATCH>set patch_area 0B2C
PATCH>replace/instruction *x094D+'*x5C * 'jsb @#8000B4C3»
NEW>
'pushl
r3'
NEW> 'pushl
r5'
NEW> •movb
b*3F(r5),rO'
NEW> 'movl
w"00C0(r4) f r5
NEW>
•movl
b-20(r5),r3'
NEW> 'movb
r0,b~37(r3)'
NEW>
§#80002EE8'
•jsb
NEW> •clrb
b~37(r3)'
NEW> •movl
(sp)+,r5«
NEW> •movl
(sp)+,r3«
NEW> •jsb
e#8000B4C3'
NEW> exit
000009A9:
§#8000B4C3
old:
JSB
new:
000009A9:
BRW
PAB
new:
000009AC: NOP
new:
000009AD: NOP
new:
000009AE: NOP
new:
PAB:
PUSHL
R3
new:
00000B36
PUSHL
R5
new:
00000B38
MOVB
B*3F(R5),R0
new:
00000B3C
MOVL
VT00C0(R4),R5
B"20(R5),R3
MOVL
00000B41
new:
MOVB
R0,B*37(R3)
00000B45
new:
00000B49
@#80002EE8
new:
JSB
B"37(R3)
new:
00000B4F
CLRB
MOVL
OOO0OB52
(SP)+,R5
new:
00000B55:
MOVL
(SP)+,R3
new:
new:
§#8000B4C3
00000B58:
JSB
000009AF
BRW
new:
00000B5E<
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE] PUDRIVER.EXE ?2
PATCH>EXIT
l

•

A-ll

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE]RMS.EXE/1"
"DISK$RES26APR: [SYSEXEJRMS. JNL; 1"
4-MAY-1982 13:34:10.86

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>DEFINE ECO01 * "X0B420
symbol "ECO01" defined as 0000B420
PATCH>SET ECO 1
PATCH>REPLACE/INST
LOO ECO01+04A
R0,ECO01+0A4'
OLD>
'BLBC
0LD> EXIT
RO^ECOOl+OA?
NEW> *BLBC
NEW> EXIT
0000B46A: BLBC
old:
BLBC
0000B46A:
new:
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE]RMS,EXE;2
PATCH>EXIT
1

A-12

RQ,0000B4C4
R0,0000B4C7

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE] SCSLOA.EXE ;
"DISK$RES26APR: [SYSEXE] SCSLOA.JNL;l"
4-MAY-1982 13:35:13.91

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>SET ECO 1
A
PATCH>replace/word x0 = "x720
NEW> *x800
NEW> exit
0720
PA A:
old:
0800
PAA:
new:
PATCH>replace/word ~x8 = ~x720
NEW> ~x800
NEW> exit
0720
00000008:
old:
0800
00000008:
new:
A
PATCH>replace/long x71C =
NEW> "xODC
NEW> exit
00000000
0000071C:
old:
O0OO00DC
0000071C:
new:
PATCH>replace/long ~x720 =
NEW> *x724
NEW> exit
00000000
00000720:
old:
00000724
00000720:
new:
PATCH>set patch_area 71C
•movl #l,r0'
PATCH>replace/instruction "x223
#l,r0'
'movl
NEW>
'movab
NEW>
0*30^3)^34^3)'
•movab
NEW>
0*38^3)^38^3)'
•movab
NEW>
b^S^^b^Ct^)'
movab
NEW>
NEW> exit
#01, R0
MOVL
00000223:
old:
PAB
BRW
00000223:
new:
#01, R0
MOVL
PAB:
new:
B~30(R3),B*30(R3)
MOVAB
00000727:
new:
B~30(R3),B*34(R3)
MOVAB
0000072C:
new:
B~38(R3),B~38(R3)
MOVAB
00000731:
new:
B*38(R3),B*3C(R3)
MOVAB
00000736:
new:
00000226
BRW
0000073B:
new:
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE] SCSLOA.EXE;
PATCH>EXIT

A-13

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED
PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR:[SYSEXE]SYS,EXE,-1"
"DISK$RES26APR:[SYSEXE]SYS.JNL;1
3-MAY-1982 15:42:32.11

Image does not contain local symbols
Some or all global symbols not accessible
PATCH>DEFINE ECO 2_40$ symbol "ECO 2_40?" defined as 00000000
PATCH>DEFINE EC0_2_SETUP =
PATCH>SET ECO 1
PATCH>EX/ASCII 800028F0
800028F0:
PATCH>DEP/ASCII 800028F0= V3. 0'
800028FO:
old:
800028F0:
new:
PATCH>EX/ASCII 8001C0F1
•XlJY
8001C0F1:
PATCH>DEP/ASCII eOOlCOFl-'VS.O*
8001C0F1:
old:
8001C0F1:
new:

XUY

•X1JY
•V3.0'

•X1JY
•V3.0

PATCH>UPDATE
!
1

ECO

I
I

Module SWAPPER

.PSECT $AEXENONPAGED

Base address = "X80004530

PATCH>SET ECO 2
Nonpaged read/write area to avoid JMP
PATCH>SET PATCH AREA "X80002FB0
Line 1079
PATCH>DEFINE ECO 2_40$ « "X80004530 + "X0624
symbol "ECO 2 40?" redefined from 00000000 to 80004B54
patch>repla?e7instruction
'
Line 1052
"X05C5
LOO "X80004530
A
W *X80002608,R4'
•MOVAL
OLD>
OLD> EXIT
A
Branch to line 1079
#"X02 f W "X800026F0 f ECO-2_40$
NEW> •BBC
R4
W"X80002608
•MOVAL
NEW>
NEW> EXIT
VT80002608,R4
MOVAL
80004AF5:
old:
PAB
BRW
80004AF5:
new:
NOP
80004AF8:
new:
NOP
80004AF9:
new:
A
#02,W 800026F0,80002FC1
BBS
PAB:
new:
ECO_2_40$
BRW
80002FBE:
new:
W*80002608,R4
MOVAL
80002FC1:
new:
80004AFA
BRW
80002FC6:
new:
PATCH>VERIFY/INSTRUCTION
Line 1079
LOO ECO_2_40$
rx02,rX0012
'MTPR
0LD>
0LD> EXIT
MTPR
#02, #12
ECO_2_40$:
old:
A
Line 1100
PATCH>DEFINE ECO 2 SETUP = X80004530 + "X064E
symbol "EC0_2 SETU?" redefined from 00000000 to 80004B7E
patch>replace7instruction
Line 1086
LOO "X80004530 + "X063D
#*X07,#*X0012»
•MTPR
OLD>
OLD> EXIT
#"X07 #"X0012
•MTPR
NEW>
Branch to line 1100
#"X02,W"X800026FO r ECO_2_SETUP
•BBC
NEW>
NEW> EXIT
MTPR
#07, #12
80004B6D:
old:
80002FC9
BRW
80004B6D:
new:
#07 r #12
MTPR
80002FC9:
new:
#02,W*800026F0,80002FD5
BBS
80002FCC:
new:
ECO_2_SETUP
BRW
80002FD2:
new:
80004B70
BRW
80002FD5:
!

new:

A-14

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH>VERIFY/INSTRUCTION
rnrs vrn
<5RTUP
BSffvT
OLD>
OLD> EXIT
*>

Line 1101
'X80004530 + *X0A13'
1

ECO_2_SETUP:

PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXEJSYS.EXE;
PATCH>EXIT

A-15

BSBW

BSBW OSINIT

80004F43

PATCHES MADE AFTER MICROFICHE KIT MANUFACTURED

PATCH Version 3-00 15-Mar-1982
IMAGE FILE BEING PATCHED:
JOURNAL FILE:
DATE/TIME OF PATCH:

"DISK$RES26APR: [SYSEXE]XGDRIVER.EXE;1"
"DISK$RES26APR: [SYSEXE]XGDRIVER. JUL;!"
3-MAY-1982 15:43:07.06

Image does not contain local symbols
PATCH>SET ECO 01
PATCH>ex/i 0e4+78
0000015C: MOVAL
VT0274 <R5) ,R0
PATCH>ex/b 15d
0000015D:
0C5
PATCH> rep/byte .
OLD> 0c5
OLD> exit
NEW> OcO
NEW> exit
old:
new:

0000015D:
0000015D:

0C5
OCO

PATCH>ex/i 15c
0000015C: MOVAL
VT0274 (R0) ,R0
PATCH>UPDATE
Updating image file DISK$RES26APR: [SYSEXE] XGDRIVER.EXE;
PATCH>EXIT

A-16

VAX/VMS Release Notes
Version 3.0

AA-D015D-TE

READER'S COMMENTS
NOTE: This form is for document comments only. DIGITAL will use comments submitted on this form at the
company's discretion. If you require a written reply and are eligible to receive one under Software
Performance Report (SPR) service, submit your comments on an SPR form.

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

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

Please indicate the type of user/reader that you most nearly represent.

Assembly language programmer
Higher-level language programmer

Occasional programmer (experienced)

User with little programming experience

Student programmer

D Other (please specify)
Name

Date

Organization

Street

City

State

Zip Code __
or Country

— — — Do Not Tear Fold Here and Tape
-

No Postage
Necessary
if Mailed in

the

United States

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

POSTAGE WILL BE PAID BY ADDRESSEE

BSSG PUBLICATIONS ZK1-3/J35
DIGITAL EQUIPMENT CORPORATION
110 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03061

Do Not Tear

Fold Here

1
§
9