Digital PDFs

AA-JG66A-TN

May 1986

92 pages

Original

0.8MB

Document:	MicroVMS 4.5 Release Notes
Order Number:	AA-JG66A-TN
Revision:	0
Pages:	92
Original Filename:	MicroVMS%204.5%20Release%20Notes.pdf

OCR Text

MicroVMS
Release Notes, Version 4 5
..

Order Number: AA-JG66A-TN

September 1986

This document describes Version 4.5 of the MicroVMS operating system and explains
the method for updating a Version 4.4 system to Version 4.5. It lists and discusses
system changes, new features, corrected problems, and restrictions in the use of the
system. It also describes changes and corrections to the MicroVMS documentation
set.

Revision/Update Information:

This is a new manual, which adds to and corrects
information contained in the MicroVMS Release

Notes Version 4.4, Order Number AA-HL72A-TN,
published April 1986.

Operating System and Version: MicroVMS Version 4.5
Software Version:

digital equipment corporation
maynard, massachusetts

MicroVMS Version 4.5

September 1986

The information in this document is subject to change without notice and should not
be construed as a commitment by Digital Equipment Corporation. Digital Equipment
Corporation assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may be used or
copied only in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not
supplied by Digital Equipment Corporation or its affiliated companies.
Copyright ©1 986 by Digital Equipment Corporation
All Rights Reserved.
Printed in U.S.A.
The postpaid READER'S COMMENTS form on the last page of this document requests the
user's critical evaluation to assist in preparing future documentation.
The following are trademarks of Digital Equipment Corporation:
DEC
DEC/CMS
DEC/MMS
DECnet
DECsystem-1 0
DECSYSTEM-20
DECUS
DECwriter

DIBOL
EduSystem
lAS
MASS BUS
PDP
PDT
RSTS
RSX

UNIBUS
VAX
VAXcluster
VMS
VT

�D�DlJ5j0
ZK-3309

HOW TO ORDER ADDITIONAL DOCUMENTATION
DIRECT MAIL ORDERS
USA & PUERTO RICO*

CANADA

INTERNATIONAL

Digital Equipment Corporation
P.O. Box CS2008
Nashua, New Hampshire
03061

Digital Equipment
of Canada Ltd.
1 00 Herzberg Road
Kanata, Ontario K2K 2A6
Attn: Direct Order Desk

Digital Equipment Corporation
PSG Business Manager
cfo Digital's local subsidiary
or approved distributor

In Continental USA and Puerto Rico call 800-258-1 71 0.
In New Hampshire, Alaska, and Hawaii call 603-884-6660.
In Canada call 800-267-621 5.

* 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 (SOC), Digital Equipment Corporation,
Westminster, Massachusetts 01 473.
This document was prepared using an in-house documentation production system. All page composition and
make-up was performed by TEX. the typesetting system developed by Donald E. Knuth at Stanford University.
TEX. is a trademark of the American Mathematical Society.

Contents
Preface
Chapter 1

vii

Installing the Version 4.5 Update Kit

The Version 4.5 Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1
Optional Software Products . . . . . . . . . . . . . . . . . .
1.1.1
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2

1-1
1-1
1-2

1.2

Preparing to Update Your System . . . . . . . . . . . . . . . . . . .

1-4

1.3

Installing the Version 4 .5 Update . . . . . . . . . . . . . . . . . . . .

1-8

1.4

Tasks to Perform After the Version 4.5 Update . . . . . . . . . . .

1-13

1.5

Printing Patches Applied by the Update Kit . . . . . . . . . . . . .

1-15

Chapter 2

New and Changed Features

2 .1
System Manager Information . . . . . . . . . . . . . . . . . . . . . .
Using Standalone BACKUP from an Alternate System
2 .1.1
Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 .1.1.1
Building Standalone BACKUP on the Alternate System Root
SYSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Booting Standalone BACKUP from an Alternate System
2 .1.1.2
Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MicroVAX II Large Memory Systems . . . . . . . . . . . . . . . .
2 .1.2
ADD_ Records for Numeric SYSGEN Parameters Allowed in
2 .1.3
AUTOGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 -1
2 -1
2 -1
2 -2
2 -2
2 -3

Contents

Chapter 3

Problems, Restrictions, and Notes

General User Information . . . . . . . . . . . . . . . . . . . . . . . . .
3.1
VAXTPU GET_INFO Command . . . . . . . . . . . . . . . . . . .
3.1.1
VAXTPU and Terminal Widths . . . . . . . . . . . . . . . . . . . .
3.1.2

3-1
3-1
3-2

System Manager Information . . . . . . . . . . . . . . . . . . . . . .
3.2
Recommendation to Start Error Logging on MicroVAX
3.2 .1
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Documentation Correction: Normal System Startup . . . . . .
3.2 .2
Starting Up the System If Halts Are Enabled . . . . . . . . . .
3.2 .2 .1
Starting Up the System If Halts Are Disabled . . . . . . . . .
3.2 .2 .2
3.2 .3
Documentation Correction: Additional MicroVAX I Bootstrap
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the Console Diskette . . . . . . . . . . . . . . . . . . .
3.2 .3.1
Copying
the MicroVMS Operating System to the New
3.2 .3.2
System Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bootstrapping from the New System Disk . . . . . . . . . . . .
3.2 .3.3
Error Count for Remote (RTAn:) Devices . . . . . . . . . . . . .
3.2 .4
SDA COPY Command Marks SYSDUMP.DMP As Empty . .
3.2 .5

3-2
3-3
3-3
3-3
3-5
3-5
3-6
3-7
3-8
3-9
3-9

Application Programmer Information . . . . . . . . . . . . . . . . .
3.3
3-9
SS$__NOENTRY Error Reported in XABPRO Block for
3.3.1
ACL-Protected Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Ethemet/802 Drivers: Promiscuous Mode Change
3.3.2
Planned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Ethernet Controller: List of Expected Errors . . . . . . . . . . . 3-10
3.3.3
Documentation Correction: IO$M_OUTBAND . . . . . . . . . 3-11
3.3 .4
Documentation Correction: FORTRAN IBITS Function . . . . 3-11
3.3.5
Documentation Corrections: SMG$SETJEYPAD_MODE and
3.3. 6
SMG$READ_STRING . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
SCNRTL Problems Corrected . . . . . . . . . . . . . . . . . . . . . 3-12
3.3.7
Debugging Shareable Images-Change in Behavior from
3.3.8
Pre-Version 4.4 Releases . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Debugger Window-Change in Behavior from MicroVMS
3.3.9
V4 .4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Failure of VAX BASIC SET INITIAL CHOICE Statement . . . 3-13
3.3.10
SYS$CREMBX and Process-Private Logical Names . . . . . . . 3-14
3.3.11
3.4
System Programmer Information . . . . . . . . . . . . . . . . . . . . 3-14
NETACP Verification of MOP Messages . . . . . . . . . . . . . . 3-15
3.4.1
Behavior of Zero-Length and Negative Byte Counts Submitted
3.4.2
in $QIO Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Contents

Appendix A

MicroVMS Version 4.5 Update
Description

Appendix B

Preparing an RD51 -Based
MicroVAX I System for an Update

Index
Tables
1-1

Approximate Disk Block Utilization for Version
4.5 Installation Procedure . . . . . . . . . . . . .

1 -4

Preface
The MicroVMS Release Notes, Version 4.5 manual describes Version 4.5 of the
MicroVMS operating system and explains the method for updating a Version 4.4
system to Version 4.5. It lists and discusses changes to the system, new features,
corrected problems, and restrictions in its use. It also describes changes and
corrections to the documentation set.
All system users may find information of interest in this manual. Chapters 2 and 3
contain notes that discuss aspects of the Version 4.5 operating system of concern to
the general user, system manager, application programmer, and system programmer.
There are three major sections and two appendixes.
•

Chapter 1 contains instructions for installing the Version 4 .5 update kit.

•

Chapter 2 briefly summarizes each new and changed system feature.

•

Chapter 3 details Version 4.5 fixes to known problems in the operating system
and published documentation. It describes restrictions that should be applied to
the use of MicroVMS Version 4.5 and contains miscellaneous technical notes as
well.

•

Appendix A lists the contents of the update kit.

•

Appendix B describes special procedures that MicroVAX I systems with RD51
disks must perform before applying the Version 4.5 update.

Apart from the documents for which corrections and additions are published in
Chapters 2 and 3, you may find the following documents helpful while reviewing
the new material presented in this manual:
•

Installing or Upgrading MicroVMS From Diskettes or Installing or Upgrading
MicroVMS From a Tape Cartridge

•

The MicroVMS Release Notes Version 4.4

•

The MicroVMS User's Manual

•

The MicroVMS Operating System, Version 4.5 Software Product Description (SPD
28.05.08)

•

The System Software Ordering Table (SPD 28.98.xx)

viii

Preface

MicroVMS users have the option of purchasing any or all manuals of the full
VAX/VMS documentation set.
The following conventions are observed in this manual:
Convention

Meaning

RET

A symbol with a one- to six-character abbreviation
indicates that you press a key on the terminal, for example,
RET.

$ SHOW TIME
1 1 -NOV- 1986 1 1 :55:22

Command examples show all output lines or prompting
characters that the system prints or displays in black
letters. All user-entered commands are shown in red
letters.

$ TYPE MYFILE.DAT

Vertical series of periods, or ellipsis, means either that not
all the data that the system would display in response to
the particular command is shown or that not all the data a
user would enter is shown.

file-spec, ...

Horizontal ellipsis indicates that additional parameters,
values, or information can be entered.

[logical-name]

Square brackets indicate that the enclosed item is optional.
(Square brackets are not, however, optional in the syntax
of a directory name in a file specification or in the syntax
of a substring specification in an assignment statement.)

quotation marks ( )
apostrophe ( )
11

The term quotation marks is used to refer to double
quotation marks ( 11 ). The term apostrophe ( ) is used to
refer to a single quotation mark.
1

Chapter

I nstalli ng the Version 4.5 U pdate Kit
This chapter outlines the procedures necessary to install the Version 4 .5 update to
the MicroVMS operating system. When you install the update kit, a Version 4.5
system is produced.

1.1

The Version 4.5 Kit

The MicroVMS Version 4.5 update kit consists of documentation, patches, and
replacement files. It includes the following components:
•

The MicroVMS Operating System, Version 4.5 Software Product Description (SPD
28.05 .08)

•

The MicroVMS Release Notes, Version 4.5

•

Distribution media: Five diskettes or one tape cartridge

Appendix A lists the patches, new images, and miscellaneous fixes contained in the
Version 4.5 update kit.

1 .1 . 1 Optional Software Products
The Version 4.5 kit does not contain updates to any MicroVMS optional software
products except DECnet-VAX. For more information about optional software
products, see the System Software Ordering Table (SPD 28.98.xx). Documentation
for a specific optional software product is shipped with that product.

1-2

Installing the Version 4.5 Update Kit

1 . 1 .2 Requirements
The following cautions and restrictions must be observed for this update:
•

The system must be running Version 4 . 4 prior to the application of the Version
4.5 update kit:
If the system being updated is not currently running MicroVMS Version 4.4,
you must upgrade it to Version 4.4 before installing the Version 4.5 update
kit.
If you are installing MicroVMS on a new system, you must install Version 4.4
before applying the Version 4.5 update.
Installing or Upgrading MicroVMS From Diskettes and Installing or Upgrading
MicroVMS From a Tape Cartridge contain instructions for installing or upgrading

your system to MicroVMS Version 4.4 and for installing MicroVMS options.
•

You must reapply the MicroVMS Version 4.5 update if you install any of the
MicroVMS options (PROG, SYSP, USER, and UTIL) or the DECnet-VAX optional
software product after you have installed the Version 4.5 update.
Because the MicroVMS Version 4.4 "Common Utilities Option" (UTIL) is
necessary to perform the required rebuilding of standalone BACKUP when
the update procedure completes, that option must be installed prior to performing
the Version 4.5 update.

•

Because MicroVMS Version 4.5 contains an update for DECnet-VAX, certain
steps must be followed when installing DECnet-VAX and Version 4 .5, depending
on the installation scenario as follows:
Case

Action(s)

System currently has both
MicroVMS Version 4.4 and
DECnet-VAX Version 4.4
installed and MicroVMS
Version 4.5 is to be installed

Install MicroVMS Version 4 .5. This will upgrade both
MicroVMS and DECnet-VAX to Version 4.5 .

System is currently running
MicroVMS Version 4.4 and
both DECnet-VAX Version
4.4 and MicroVMS Version
4.5 are to be installed

1. Install DECnet-VAX o n the system.

Installing the Version 4.5 Update Kit

Case

1-3

Action(s)

2. Install MicroVMS Version 4.5.
This will upgrade both MicroVMS and DECnet-VAX to
Version 4 .5.
System currently has
MicroVMS Version 4.5
installed and DECnet-VAX
Version 4.4 is to be installed

1. Install DECnet-VAX Version 4.4, but do not install the
MicroVMS Version 4.4 mandatory update. (The Version
4.4 mandatory update will not install on a MicroVMS
Version 4 .5 system.) All DECnet-VAX patches that
were in the V 4.4 mandatory update are included in the
MicroVMS V4.5 kit.
2. Reinstall MicroVMS V4.5 so that DECnet-VAX will be
upgraded to Version 4.5.

•

If you are updating a MicroVAX I with an RD51 disk, you must remove all
MicroVMS operating system options from the disk to make room for the update
procedure. However, because the update procedure requires the "Standalone
BACKUP on System Disk" and "DIFF Utility" suboptions of the UTIL option, you
must install (or retain) these suboptions before proceeding with the update. (See
Appendix B for instructions for performing this procedure.)
For MicroVAX I systems with RD51 disks, MicroVMS Version 4.5 updates only
the MicroVMS base system, and none of the operating system options. After the
update has completed, if you wish to install or reinstall a Version 4 .4 MicroVMS
operating system option or suboption, refer to the MicroVMS Operating System,
Version 4.5 Software Product Description (SPD 2 8.05.08) for the number of disk
blocks required by each option. See Chapter 5 of the Installing or Upgrading
MicroVMS From Diskettes for instructions for installing a MicroVMS option or
suboption.

•

If you are installing the update on a system running the VAX Ada optional
software product, you must install VAX Ada Version 1.3 after applying the
update.

1 -4

Installing the Version 4.5 Update Kit

1 .2

Preparing to Update Your System

This section describes the activities you must perform before applying the Version
4 .5 update to your system. You should read this entire section before proceeding
with the update.
Perform these steps to prepare your system for the update:
1.

Back up and restore the system disk.

By backing up the system disk, you preserve the original system disk in the
event that a system failure at a critical point in the update results in unusable or
deleted files. Restoring the system disk improves disk performance by making all
free space on the disk contiguous.
CAUTION: If you elect not to back up your system disk, a system failure at
a critical point of the update procedure may cause the previous contents of the
disk to become irretrievable.

To back up and restore the system disk, use standalone BACKUP as described in
Section 4.1.1 of Installing or Upgrading MicroVMS From Diskettes or Installing or
Upgrading MicroVMS From a Tape Cartridge.

Reserve space for the update files.

The MicroVMS Version 4 .5 update procedure requires that a minimum number
of free blocks be available on the system disk so that the procedure can properly
perform the update. To ensure that there are sufficient free blocks to meet
the update procedure's peak disk block utilization (see Table 1-1), perform the
following actions:
a.

Confirm the number of free blocks on the system disk by entering the
following DCL command:
$ SHOW DEVICE SYS$SYSDEVICE :

Compare the number of free blocks shown on the display against the required
peak disk block utilization shown in Table 1-1.

Table 1-1

Approximate Disk Block Utilization for Version 4.5 Installation
Procedure

Peak disk block utilization

1 0000

Net disk block utilization if files
are purged during the update

3000

If you have fewer blocks available than the peak disk block utilization figure, you
must reduce the number of used disk blocks to acquire enough free space for the

Installing the Version 4.5 Update Kit

1 -5

Version 4.5 update. DIGITAL recommends that you use the following procedure
to gain the needed disk space:
a.

Log in to an account with sufficient privileges to create space on the system
disk. DIGITAL recommends that you do not log in to the SYSTEM account.
The SYSTEM account, which has all privileges (including BYPASS), is
intended only for software installation, bootstrapping, and system problem
diagnosis. You can avoid problems by creating another account and
assigning it the minimum privileges required.

Delete or purge all unwanted or redundant files from the system disk.

If there still is not enough available space, copy the following files to another
media and delete them from the system disk:
•
All files with JNL, MAP, LOG, and STB1 extensions
•

The files SYS$ERRORLOG:ERRLOG.SYS and
SYS$MANAGER:ACCOUNTNG.DAT

•

All files in the directories [SYSHLP .EXAMPLES] and [SYSTEST]

If you cannot make a sufficient number of free blocks available on the system
disk to meet peak utilization requirements, the update procedure will operate
in an alternate mode that reduces these requirements. However, if a system
failure occurs while the procedure is operating in this alternate mode, you must
restore the Version 4.4 system disk from a backup copy, and restart the update
procedure from the beginning.
3.

Confirm the quotas and limits o f the SYSTEM account.

Because you will later install the update from the SYSTEM account, you must
ensure that the account has sufficient quotas and limits to successfully complete
the update. To do so, perform the following actions:
a.

Run the Authorize Utility (AUTHORIZE) by entering the following
commands:
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> SHOW SYSTEM

1 Once the Version 4.5 update is installed, DIGITAL recommends that you copy all STB files back to
their original directories, except RMS.STB (for which Version 4.5 supplies a new file).

Installing the Version 4.5 Update Kit

1 -&

Compare the SYSTEM account's limits and quotas to the following values:
Open file quota (Fillm)
Buffered 1/0 limit (BIOlm)

Direct 1/0 limit (DIOlm)

AST limit (ASTlm)

Enqueue quota (Enqlm)

Buffered byte quota count (Bytlm)

20480

Adjust the corresponding UAF parameters, as appropriate, to ensure that
they are equal to or greater than the required values. You can change each
value by entering the following command:
UAF> MODIFY SYSTEM/ l imit=new_value

For example:
UAF> MODIFY SYSTEM/DIOLM=18

Return to DCL command level by issuing the following command:
UAF> EXIT

f.
4.

If you have adjusted any of the SYSTEM account's values, log out and log in
again so that the new values take effect.

Reserve sufficient global pages.

The installation procedure requires at least 10 unused global sections and 200
unused global pages. Ensure that sufficient unused global sections and global
pages are available to the procedure by performing the following operations:
a.

Display the number of used global sections, and used and unused global
pages, by issuing the following commands:
$ INSTALL : == $ INSTALL/COMMAND_MODE
$ INSTALL
INSTALL> LIST/GLOBAL/SUMMARY
INSTALL> EXIT

Determine the current number of global sections by invoking the System
Generation Utility (SYSGEN) and proceeding as follows:
$ RUN SYS$SYSTEM : SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SHOW GBLSECTI ONS

Determine the number of unused global sections by subtracting the number
of used global sections (determined in step a from the INSTALL display)
from the current number of global sections (determined in step b from the
SYSGEN display).

Installing the Version 4.5 Update Kit

1 -7

If the number of unused global sections is less than 1 0, increase the

GBLSECTIONS parameter, 1 using the following command:

SYSGEN> SET GBLSECTIONS new-value

To compute new-value, add 10 to the number of used global sections
(determined in step a from the INSTALL display).
e.

If the number of unused global pages (determined in step a from the
INSTALL display) is less than 200, you must increase the GBLPAGES
parameter. 1 Use the following command:
SYSGEN> SET GBLPAGES new-value

To compute new-value, add 200 to the number of used global pages
(determined in step a from the INSTALL display).
f.

Save the modified values and exit from SYSGEN using the following
commands:
SYSGEN> WRITE CURRENT
SYSGEN> EXI T

If you have modified either of the SYSGEN parameters GBLPAGES or
GBLSECTIONS, use the SYS$SYSTEM:SHUTDOWN.COM command
procedure to shut down the system. Reboot the system so that the new
SYSGEN parameter values take effect.

Isolate the system from users.

Make sure that nobody but you is logged in to the system. This is a twofold
procedure:
a.

Notify current users that they must log out.

Ensure that no new user can log in. The following command prevents users
from logging in:
$ SET LOGINS/INTERACTIVE=O

Shut down the network.

Perform this task only if your system is running DECnet-VAX. If you are not
sure whether your system includes DECnet-VAX, enter the following command:
$ SHOW NETWORK

1 DIGITAL recommends that you also edit SYS$SYSTEM:MODPARAMS.DAT to reflect the modified
system parameters. (Refer to the procedures described in Section 1.6 of the MicroVMS User's Manual
whenever you change SYSGEN parameters.)

Installing the Version 4.5 Update Kit

1-8

If the message "%SHOW-I-NONET, network unavailable" appears, skip to step
7. If your system includes DECnet-VAX, shut it down by issuing the following
commands:
$ RUN SYS$SYSTEM:NCP
NCP> SET EXECUTOR STATE OFF
NCP> EXIT

Stop all batch and print queues.

To do so, perform the following tasks:
a.

Enter the following command to determine the state of all system queues:
$ SHOW QUEUE/DEVICE/BATCH/FULL/ALL

Stop each active queue by issuing the command
$ STOP/QUEUE/NEXT queue_name

The NEXT qualifier allows the current job to complete before the system
stops the queue. If this job may take a long time to complete, you may want
to ensure that it is safe to stop it prior to completion.
8.

Review special considerations. Under various circumstances and within certain
configurations, you may be required to perform other actions before proceeding
with the update. See Section 1 .1.2 to determine if any special requirements apply
to your system.

1.3

Installing the Version 4.5 Update

After completing the procedures described in Section 1.2, perform the steps in this
section to install the Version 4.5 update kit.
1.

Invoke the VMSINST AL command procedure.

Use the following command:
$ �SYS$UPDATE:VMSINSTAL VMS045 devic e-name

where device-name is the physical name of the device holding the update
distribution media. Specify device-name, using the format ddcu as follows:
dd specifies the type of device.
c refers to the controller number.
u refers to the device unit number.

For example, if your MicroVAX has one fixed disk and the distribution diskette is
in diskette drive 1, you would enter the following command:
$ �SYS$UPDATE:VMSINSTAL VMS045 DUAl:

Installing the Version 4.5 Update Kit

1 -9

If you are updating from a tape cartridge, you would enter the following
command:
$ @SYS$UPDATE : VMSINSTAL VMS045 MUAO :

(See Appendix B of Installing or Upgrading MicroVMS From Diskettes or Installing
or Upgrading MicroVMS From a Tape Cartridge for a list of the physical names of

MicroVAX devices.)
If the VMSINSTAL command fails, determine whether either of the following
conditions occurred:
•

If VMSINSTAL displays the message "%VMSINSTAL-E-NOPRODS, None
of the specified products were found", it is likely that you specified the letter
"0" in the product name "VMS045" instead of a zero.

•

If VMSINSTAL displays an "invalid device" error message, it will issue
prompts for a device name until you specify the correct name of a device
existing on the system. Remember to terminate the device name with a
colon ( : ).

When the command succeeds, VMSINSTAL displays the following message:
VAX/VMS Software Product Installat i on Proc edure V4 . 5
It is (dat e ) at (time ) .
Ent er a quest ion mark (?) at any t ime f or help .

Reply to VMSINSTAL prompts.

As the update procedure begins, VMSINSTAL presents its first prompt:
* Are you sat i sf i ed with the backup of your syst em disk [YES] ?

If you are content with the current backup of the system disk, press the RETURN
key and continue.
If you have not yet backed up your system disk or are otherwise dissatisfied with
the current backup, perform the following operations:
a.

Enter NO and press the RETURN key. VMSINSTAL returns to DCL level to
permit you to perform the backup.

Back up and restore your system disk using standalone BACKUP as described
in Section 4 . 1 .1 of either Installing or Upgrading MicroVMS From Diskettes or
Installing or Upgrading MicroVMS From a Tape Cartridge.

Restart the update procedure at step 1 when the backup is completed.

Installing the Version 4.5 Update Kit

1 -1 0

As it proceeds, VMSINSTAL may request additional information from you or
display various messages. For instance, if you did not specify the name of a load
device in the command that invoked VMSINSTAL in step 1, VMSINSTAL will
prompt for the name of the device holding the distribution volume:
* Where will the distribution volume be mounted :

To respond, enter the physical name (as described in Appendix B of Installing
or Upgrading MicroVMS From Diskettes or Installing or Upgrading MicroVMS From
a Tape Cartridge) of the device that will hold the distribution media during the
update operation.
VMSINSTAL displays informational messages that describe the actions it is
performing. During the entire process, look for error and warning messages
that indicate tasks you must perform manually. Many informational messages
will be displayed; these messages can usually be ignored. For instance, if you
are installing from an operator�s terminal, you will receive a message after each
mount operation if the SYSGEN parameter MOUNTMSG is set and after each
dismount operation if the SYSGEN parameter DISMOUMSG is set. Each message
will appear within 30 seconds of its associated operation.
3.

Mount the first (or only) volume o f the update kit.

VMSINSTAL next displays the following prompt:
Pl eas e mount the first volume of the s et on ddcu : .
* Are you ready?

To respond, perform the following actions:
a.

Insert the first (or only) distribution volume into the load device. If you
are installing from diskettes, insert the first volume in the drive. If you
are installing from a tape cartridge, insert the cartridge into the drive. See
Chapter 2 of either Installing or Upgrading MicroVMS From Diskettes or
Installing or Upgrading MicroVMS From a Tape Cartridge for instructions on
inserting media into a drive.

After you have inserted the first (or only) volume into the appropriate drive,
enter Y and press RETURN.

VMSINSTAL then displays the following information:
%MOUNT- I -MOUNTED , VMS045 mount ed on _ddcu :
The following products will be pro c e ssed :
VMS V4 . 5
Beginning installation of VMS V4 . 5 at (time )

Installing the Version 4.5 Update Kit

1- 1 1

Select an update option.

Shortly after it has copied the first save set from the installation volume (or
volumes), VMSINSTAL displays the following menu:
1)
2)
3)

Apply al l f ixes to t h e system
Creat e a f i le with the descript i ons of all f ixes
Both of the above

* What would you like to do [3] :
•

Under option 1 , VMSINSTAL performs only the update.

•

Under option 2, VMSINSTAL does not perform the update. It simply creates
the update description file, SYS$UPDATE:VMS045 .TXT. (Appendix A lists
the contents of this file.)

•

Under option 3, VMSINSTAL both performs the update and creates the
update description file.

Type one of these option numbers and press RETURN.
If you choose option 2 or 3, VMSINSTAL issues the following prompt:
%VMS - I -FIXDESC , The f ixes are described in SYS$UPDATE : VMS045. TXT

Proceed with the update.

If you elect to proceed with the update by specifying option 1 or 3, VMSINSTAL
displays the following question:
* Do you want to purge f i l e s replac ed by this instal lation [YES] ?

If you want VMSINSTAL to automatically purge files replaced by the update,
press RETURN. (Refer to Section 1 .4 for additional details on other ways to
economize on disk space after the update has completed.) Answer N if you
do not want these files purged. When VMSINSTAL receives your reply to this
prompt, it restores the remainder of the update save sets and continues the copy
operation from the specified drive.
If you are installing the update from a set of diskette volumes, VMSINSTAL
automatically requests, as it completes its operations from one volume, that you
remove the current volume and insert the subsequent one.
If you are installing from a tape cartridge, there is only one tape for you to insert.
When VMSINSTAL completes the restoration of the save sets, it begins to
apply the update to the system disk. During this time, ensure that the last (or
only) volume of the update media remains mounted until the update is fully
completed.

1 -1 2

Installing the Version 4.5 Update Kit

As VMSINSTAL proceeds, it displays the name of each image that is patched or
installed, plus various informational messages describing the characteristics of
the patches and images. You should be aware of the following situations which
result in messages:
•

The Patch Utility will commonly generate the following informational
messages:
%PATCH- I -NOLCL , image does not contain local symbols
%PATCH - I - NOGBL , s ome or al l global symbols not acc essible

These messages are a normal result of the construction of some update
patches and should be ignored.
•

When updating the NETACP .EXE image, VMSINSTAL displays the
following:
%PATCH-I -BRTOOFAR , destination FFFFFF74 is too far f or branch operand

This message simply informs you that a JMP instruction was used in the
code generating the patch instead of a BRB or BRW instruction. The message
is informational only and does not affect the validity of the patch.
•

When updating an image that has already been patched, VMSINSTAL will
display the following informational message:
%PATCH- I -ECOSET , e c o level nn already set in ' xxx$ROOT : f ilename '

This message indicates that a patch has previously been applied, most likely
during the application of the Version 4.4 mandatory update. For this reason,
you can ignore messages of this sort.
If all of the supplied patches in an image have already been applied,
VMSINSTAL additionally displays the warning message:
%VMSINSTAL-W-NOFILE , New f ile ' Fi lename ' doe s not exist .

In other words, if all the necessary patches have already been made to the
file, there is no need for VMSINSTAL to create a new version of the file.
•

Each time it attempts to add a new image, replace an existing image, or patch
an image that is part of a MicroVMS operating system option that is not
installed on the system disk, VMSINSTAL generates a warning message of
the following form:
%VMSINSTAL-W-NOFILE , New f i l e ' Filename ' doe s not exi st .

At its completion, VMSINSTAL will advise you to review the various fixes
in which it encountered the ''NOFILE" warning message. For the previously
described reasons, you can usually ignore these messages.

Installing .the Version 4.5 Update Kit

•

1 -1 3

If you reapply the Version 4.5 update (that is, in order to update a MicroVMS
option installed after a prior application of the update), you will encounter
the following error message when the standalone BACKUP image is patched:
%VMSINSTAL-E-TAMPER , File VMI$ROOT : [SYSUPD] STABACKIT . COM has been
tampered with .

This message is normal and should be ignored.
VMSINSTAL also creates a journal file (with a file extension of .JNL) for each
image that is patched during the update process. (See Section 1 . 5 for additional
information on the .JNL files produced by the Version 4.5 update.)
When it completes the update, VMSINSTAL displays the following message:
Installat ion of VMS V4 . 5 compl et ed at (time)

and performs an orderly shutdown of the system.

1.4

Tasks to Perform After the Version 4.5 Update

After VMSINSTAL has completed its installation of the Version 4 .5 update kit,
DIGITAL recommends that you perform the following tasks:
1.

Reboot the system. Manually reboot the system as described in Section 2 .4.4
of Installing or Upgrading MicroVMS From Diskettes or Installing or Upgrading
MicroVMS From a Tape Cartridge.

Free u p disk space.

VMSINSTAL permanently uses a certain number of disk blocks (as described in
Table 1 - 1 ) called the net disk block utilization. This figure can vary, depending
on whether you chose (in step 4 of Section 1 .3) to purge the old copies of system
files that are replaced during the update.
Use the following methods to free up disk space:
a.

Confirm the free block count by issuing the command
$ SHOW DEVICE SYS$SYSDEVICE :

Purge those files that the Version 4.5 update procedure cannot purge. In
this manner you can recover approximately 2 1 00 disk blocks. Use the
PURGE command to remove old versions of the following files (files that
are part of Micro VMS options and the DECnet-VAX optional software are so
designated):
•

SYS$LIBRARY:CONVSHR.EXE

•

SYS$LIBRARY:ERFCTLSHR.EXE (Common Utilities Option)

•

SYS$LIBRARY:ERFSHR.EXE (Common Utilities Option)

Installing the Version 4.5 Update Kit

1 -1 4

•

SYS$LIBRARY:ERFSHR2.EXE (Common Utilities Option)

•

SYS$LIBRARY:LBRSHR.EXE

•

SYS$SYSTEM:BACKUP.EXE

•

SYS$SYSTEM:DCL.EXE

•

SYS$SYSTEM:ERFBRIEF.EXE (Common Utilities Option)

•

SYS$SYSTEM:ERFPROC1.EXE (Common Utilities Option)

•

SYS$SYSTEM:F1 1BXQP.EXE

•

SYS$SYSTEM:MTAAACP .EXE (System Programming Option)

•

SYS$SYSTEM:NETACP.EXE (DECnet-VAX Optional Software Product)

•

SYS$SYSTEM:JOBCTL.EXE

•

SYS$SYSTEM:NODRIVER.EXE (DECnet-VAX Optional Software
Product and Common Utilities Option)

•

SYS$SYSTEM:PUDRIVER.EXE

•

SYS$SYSTEM:RMS.EXE

•

SYS$SYSTEM:RUNDET .EXE

•

SYS$SYSTEM:SYS.EXE

•

SYS$SYSTEM:SYSBOOT.EXE

•

SYS$SYSTEM:TTDRIVER.EXE

•

SYS$MANAGER:WELCOME.TXT

•

SYS$UPDATE:VMSINSTAL.COM

Rebuild standalone BACKUP.

MicroVMS Version 4 .5 contains several corrections to images that are part
of the standalone BACKUP procedure. To include these corrections, rebuild
a standalone BACKUP kit after you install Version 4.5 . Section 1 .4.7 of the
MicroVMS User's Manual explains how to use SYS$UPDATE:STABACKIT.COM
to generate a copy of standalone BACKUP on diskettes or tape cartridge.
If your system has more than one fixed disk, you may also choose to build
standalone BACKUP in an alternate system root, as described in Section 2. 1 .1 of
these Release Notes.

Installing the Version 4.5 Update Kit

1 -15

Adjust system parameters.

Run the AUTOGEN procedure to adjust system parameters, issuing the
command
$ @SYS$UPDATE:AUTOGEN SAVPARAMS SHUTDOWN

If, in step 4 of Section 1 .2, you modified the values of GBLSECTIONS and
GBLPAGES and stored their old values in SYS$SYSTEM:MODPARAMS.DAT,
you may want to restore these values at this time.

1 .5

Printing Patches Applied by the Update Kit

If you select either option 2 or 3 as an update option (in step 4 of Section 1 . 3),
VMSINSTAL produces the update description file, SYS$UPDATE:VMS045.TXT.
This file lists the patches, new images, and miscellaneous fixes that are part of the
Version 4.5 update kit. If you print this file, you will obtain the listing that appears
in Appendix A of these release notes.
If you select either option 1 or 3, VMSINSTAL produces a journal file (with the
extension .JNL) for each image that is patched during the update. Journal files
contain a record of each patch made to these images but do not contain information
about modules that are replaced.
If you want a listing of the patches produced by the update process, print the journal
files using the following steps:
1.

Complete the update procedure that installs Version 4.5, including rebooting the
system as described in Section 2.2.4 of either Installing or Upgrading MicroVMS
From Diskettes or Installing or Upgrading MicroVMS From a Tape Cartridge.

Log in to any account that has SYSPRV privilege and issue the following
command:
$ PRINT SYS$SYSTEM:* . JNL , SYS$LIBRARY : * . JNL

The journal files produced by the Version 4.5 update procedure occupy approxi
mately 700 blocks. If you must conserve disk space, you may want to delete these
files from the system disk after you print them.

:hapter

"ew and Changed Features
'his chapter discusses features of MicroVMS Version 4 .5 primarily of interest to a
ystem manager. To find specific topics, consult the index in the back of this manual.

!.1

System Manager Information

�he following section describes the new features of MicroVMS Version 4.5 of interest
o the system manager. It also discusses changes to the operating system since
lersion 4.4.

! . 1 .1 Using Standalone BACKUP from an Alternate System Root
)ection 1 .4.7 of the MicroVMS User's Manual describes procedures for using diskettes
md tape cartridges to build a standalone BACKUP kit. You can also build a
•tandalone BACKUP kit in the alternate root SYSE on the system disk. It is much
·aster to boot standalone BACKUP from SYSE than from diskettes, and slightly faster
han booting from a tape cartridge. The only disadvantage of booting standalone
3ACKUP from SYSE is that you cannot restore files to the same disk from which you
JOot standalone BACKUP. Therefore, if your MicroVAX is a single disk system, there
s no reason to build standalone backup on an alternate system root.
!.1.1.1 Building Standalone BACKUP on the Alternate System Root SYSE

Jse the STABACKIT command procedure to build standalone BACKUP in the
1lternate system root SYSE. First, log in to the system manager's account, SYSTEM.
fhen, enter the following command:
� �SYS$UPDATE : STABACKIT SYS$SYSDEVICE :

Be sure to enter the command exactly as shown. The STABACKIT command
procedure automatically builds standalone BACKUP in the alternate system root
5YSE. When the following message appears on the screen, the kit has been built.
fhe kit is complet e .

2-2

New and Changed Features

2.1.1.2 Booting Standalone BACKUP from an Alternate System Root

In order to boot standalone BACKUP from the alternate system root SYSE, the halt
enable/disable switch on a MicroVAX II must be set to the enable position. (Because
MicroVAX I systems have no halt enable/disable switch, halts are permanently
enabled on a MicroVAX I.)
Boot standalone BACKUP from alternate system root SYSE as follows:
1.

Enter the following command to shut down the system:
$ @SYS$SYSTEM : SHUTDOWN

Respond t o the questions output b y the SHUTDOWN command procedure by
pressing the RETURN key.

A s the shutdown continues, the console terminal prints several informational
messages. When the console terminal prints the following message, the
shutdown is completed:
SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM

Halt the processor by pressing the HALT button twice.

Enter the following command to boot standalone BACKUP from SYSE:
>>> B/EOOOOOOO ddcu

where E is followed by seven zeros and ddcu is the device name of the system
disk.
6.

When it has booted, standalone BACKUP identifies itself and displays the dollar
sign ( $ ) prompt:
%BACKUP - I - IDENT , Standalone BACKUP V4 . 4; the date is <dd-mmm -yyyy hh : mm>
$

2. 1 .2 MicroVAX II Large Memory Systems
MicroVMS Version 4 .5 supports MicroVAX II systems with up to 16 megabytes of
main memory. Earlier versions of MicroVMS only support up to 9 megabytes of main
memory. If you would like to run MicroVMS V4.4 with more than 9 megabytes of
memory, you may do so, but you may experience the following cosmetic problems:
•

AUTOGEN sets the PQL _DWSDEFAULT SYSGEN parameter to a value which
is too small, resulting in the following error message every time you boot the
system:
%SYSBOOT-W-WS , default and quota rai sed to PHD+MINWSCNT

There is no actual harm because of the low SYSGEN parameter value. However,
you can work around the error message by raising the value of the PQL_
DWSDEFAULT SYSGEN parameter.

New and Changed Features

•

2-3

The MicroVMS SHOW MEMORY display will report up to 2 bad pages of
memory, when in fact all the pages are good. There is no workaround for this
problem.

If the output volume is the first volume in the backup operation, only QUIT and
CONTINUE are available as valid recovery options. If the output volume is some
subsequent volume in the backup operation, then RESTART is also available.
RESTART causes BACKUP or standalone BACKUP to restart the backup operation at
the beginning of the current save set volume. As of Version 4 .5, the utility unloads
the current tape from the drive as soon as the RESTART option is taken and then
prompts for a replacement volume. It is important that the operator not load the new
tape until the utility has prompted for it.
Prior to Version 4.5, if more than a threshold number of errors were detected on the
output tape and the operator wanted to select the RESTART option, the operator had
to remove the tape from the drive before replying to the BACKUP prompt.

2.1 .3 ADD_ Records for Numeric SYSGEN Parameters Allowed in
AUTOGEN
With Version 4.5, AUTOGEN allows ADD_ records to be included in
SYS$SYSTEM:MODPARAMS.DAT for all numeric SYSGEN parameters. Previous to
this release, an ADD_ record would affect only those parameters that AUTOGEN
itself calculated, the amount specified by the record being added to AUTOGEN's
calculated value.
In Version 4.5, the value specified in an ADD_ record for a parameter that
AUTOGEN does not calculate will be added to that parameter's default value.
For example, if AUTOGEN encounters the record "ADD_WSINC=SO" in
MODPARAMS.DAT, WSINC will be set to 200 (the default of 150 plus the specified
50) after the next boot.

:hapter

�roblems, Restrictions, and Notes
['his chapter discusses problems that have been corrected in Version 4.5 of the
�1icroVMS operating system. It also describes any restrictions that may apply to the
1se of the Version 4.5 operating system, and contains other information concerning
he release.
�or ease of reference, the material in this chapter is arranged under the following
:ategories:
Section 3 . 1-General User Information
Section 3 .2-System Manager Information
Section 3 .3-Application Programmer Information
Section 3 .4-System Programmer Information
ro find specific topics, consult the index in the back of this manual.

3.1

General User Information

rhis section describes problems resolved in MicroVMS Version 4.5, lists known
·estrictions, and contains other information about the release of interest to the
;eneral user.

� . 1 . 1 VAXTPU GET_IN FO Command
version 4.5 corrects a VAXTPU problem in which the GET_INFO built-in procedure
Nould cause an access violation when too few arguments were passed to it.
::;ET_INFO code has been fixed to check the number of parameters properly.

3-2

Problems, Restrictions, and Notes

3.1 .2 VAXTPU and Terminal Widths
Version 4.5 corrects a problem that occurred when VAXTPU set up a terminal width
other than 80, 1 32, or 84. Until this release, VAXTPU forced to 80 a terminal width
less than or equal to 80. VAXTPU forced to 1 32 a terminal width greater than 80,
and treated a device type of VKlOO as a special case of a terminal width of 84. This
behavior is undesirable on such systems as the VAXstation, which permits terminal
widths other than 80 and 1 32 .
The Version 4.5 replacement image TPU$CCTSHR.EXE corrects this problem for
terminal widths other than 80 or 1 3 2 by preserving the terminal width at startup. If
a terminal width other than 80 or 132 is specified, in either a SET WIDTH command
issued through the EVE interface or a SET SCREEN command issued through the
EDT emulator interface, VAXTPU will not send an escape sequence to the terminal to
change the width to 80 or 1 32 . (This caused the character size to change on a VT1 00
or VT200, and the font to change on a VAXstation.)
For a terminal width of 80 or 1 32, there is no change in behavior.
If, for some applications, it is important to preserve the old behavior, you can
access both the EVE interface and the EDT emulator interface sources in directory
SYS$LIBRARY. Change the interface accordingly:
•

If the terminal width to be set is less than 80, first set the width to 80. Then set
it to the desired width.

•

If the terminal width to be set is greater than 80, first set the width to 132. Then
set it to the desired width.

Remember to record any changes you make to the EVE interface or EDT emulator
interface sources. Future releases of the operating system may supply new versions
of the sources and require that you redo your edits.

3.2

System Manager Information

This section describes problems resolved in MicroVMS Version 4 .5, lists known
restrictions, and contains other information about the release of interest to the system
manager.

Problems, Restrictions, and Notes

3-3

3.2. 1 Recommendation to Start Error Logging o n MicroVAX
Systems
DIGITAL recommends that the error logging process always be started on a
MicroVAX system with RA-series disks. The information contained in the error
log is essential to DIGITAL field service personnel.
To have the error logging process start automatically each time the system is
bootstrapped, edit the site-independent startup procedure,
SYS$MANAGER:SYSTARTUP.COM. Delete the comment delimiter (!) from the
following line:
$! @SYS$SYSTEM : STARTUP ERRFMT

See the comments in the template site-specific startup command procedure,
SYS$MANAGER:SYSTARTUP .COM, for additional information.
The error logging process may be started at any time after the system has been
bootstrapped using the following DCL command:
$ @SYS$SYSTEM : STARTUP ERRFMT
NOTE:

To conserve disk space, managers of small MicroVAX configurations (less
than 5,000 free blocks on the system disk) may prefer not to start up the error
logging process.

3.2.2 Documentation Correction: Normal System Startup
The instructions for Normal System Startup (booting) were inadvertently omitted
from Chapter 1 of the Version 4.4 edition of the MicroVMS User's Manual. They
should appear on page 1 - 1 as follows:
Before starting the system for the first time, the base system must be installed.
See Installing or Upgrading MicroVMS From Diskettes and Installing or Upgrading
MicroVMS From a Tape Cartridge for installation instructions.
3.2.2.1 Starting Up the System If Halts Are Enabled

The MicroVAX I system does not have a halt enable J disable switch. Therefore,
halts are always enabled on a MicroVAX I system and you should always use
this procedure to start up a MicroVAX I. All MicroVAX II systems have a halt
enable/disable switch, which is described in Section 2 . 1 .2.2 of Installing or Upgrading
MicroVMS From Diskettes or Installing or Upgrading MicroVMS From a Tape Cartridge.
If the halt enable switch is set to the enable position, use this procedure to start up
the system. If the halt enable switch is set to the disable position, use the procedure
described in Section 3 . 1 . 2 .2.

Problems, Restrictions, and Notes

3-4

To start up (boot) the system, turn on the console terminal if it is not already on.

Turn on the processor by pressing the power switch to the 1 (ON) position.
Make sure the control panel is set for normal operations (only the Ready button
and the DC OK light should glow).

If the console-mode prompt ( > > > ) does not appear o n the console terminal
screen, press the Halt button on the processor control panel twice.

Enter the following command at the console-mode prompt and press RETURN:
>>> B

The message ATTEMPTING BOOTSTRAP will appear on your screen, followed
by a message stating the version number of the operating system. If your
processor is a MicroVAX I, or if your MicroVAX II has been turned off for more
than 240 hours, the system will prompt you to enter the date and time:
PLEASE ENTER THE DATE AND TIME (DD-MM-YYYY HH : MM)

Enter the date and time in exactly the following format and press RETURN:
dd-mmm-yyyy hh : mm
dd

Day of the month (one or two digits)

mmm

Month (first three letters of the month's name)

yyyy

Year (four digits)

Hour of the day in 24-hour format (one or two digits)

Minute of the hour (two digits)

You must follow the format exactly or you will be prompted again. The hyphens,
space, and colon must appear as shown and you must use four digits for the year.
For example, September 25, 1986, at 3 :30 P.M. is typed as follows:
25-SEP - 1986 15 : 30

You do not have to be exact in the value of the date and time. However, you
should be as close as possible. Otherwise, file activity, security-related events,
and accounting data will not be recorded properly. If you will be performing
incremental backups, starting up the system with the correct time is essential.
Startup takes several minutes. You will see several console-mode and MicroVMS
messages. The final message reads as follows:
SYSTEM

Job terminated at dd-mmm-yyyy hh : mm : ss . ss

You have successfully started up (booted) your system. You can now log in.

Problems , Restrictions, and Notes

3-5

3.2 .2.2 Starting Up the System If Halts Are Disabled

If the halt enable/disable switch, which is described in Section 2 . 1 .2.2 of Installing or
Upgrading MicroVMS From Diskettes or Installing or Upgrading MicroVMS From a Tape
Cartridge, is set to the disable position, use this procedure to start up the system.
1.

Tum on the console terminal.

Tum on the processor by pressing the power switch to the 1 (ON) position.
Make sure the control panel is set for normal operations, only the Ready button
and the DC OK light should glow.

The system will boot automatically, and will prompt you to enter the date and
time only if power has been turned off for more than 240 hours.

Startup takes several minutes. You will see several console-mode and MicroVMS
messages. The final message reads as follows:
SYSTEM j ob terminat ed at dd-mmm- yyyy hh : mm : ss . ss

You have successfully started up (booted) your system. You can now log in.

3.2.3 Documentation Correction: Additional MicroVAX I Bootstrap
Support
A description of MicroVAX I bootstrap support was inadvertently omitted from
Chapter 1 of the Version 4.4 edition of the MicroVMS User's Manual. It should
appear as follows:
REQUIRES THE COMMON UTILITIES OPTION

The MicroVAX I bootstrap �OM can only bootstrap a system disk attached to the
first Mass Storage Control Protocol (MSCP) controller. If you want to bootstrap a
system disk on another MSCP controller, you must first install MicroVMS Version
4 . 1 or greater on the system disk, and then create a special diskette to be used as a
console diskette.
If you have an RC25 disk drive with one fixed and one removable disk, DIGITAL
recommends that you use the removable disk as the system disk. The physical device
name of this removable disk is DABO: . In this way, when you perform backups, you
can remove the system disk and back up the fixed disk (containing user files) to a
spare removable disk. If there are user files on the system disk, you can back them
up to diskettes.

3-6

Problems , Restrictions, and Notes

3.2.3.1 Creating the Console Diskette

Take the following steps to create the console diskette. This example assumes that
the first RC25 disk attached to the second MSCP controller (DABO:) will be the new
system disk.
1.

Check the first diskette drive to ensure that it is inactive. If there is a diskette
in the drive, remove it following the procedure described in Section 2.2.3.2 of
Installing or Upgrading MicroVMS From Diskettes.

Label a scratch diskette CONSOLE DISKETTE. A scratch diskette is a new
diskette or a diskette that contains no information that you wish to save.

Enter the following command to invoke the command procedure that creates a
console diskette for a MicroVAX I:
$ @SYS$UPDATE : VMBUVAX1
What syst em disk do you want to be abl e to boot from? DABO :

Ignore the informational messages that are displayed on your terminal screen.
The system will then prompt you for the name of the diskette drive on which
the intermediate media (console diskette) will be mounted . In this example, the
media is mounted in diskette drive 1 (DUAl :).
Where will the int ermedi at e RX50 media be mount ed? DUAl :

You will then be prompted to insert a diskette into drive 1 and asked if you are
ready. Insert the diskette labeled CONSOLE DISKETTE into drive 1 and enter
YES in response to the following prompt:
Are you ready? YES

When it has finished building the console diskette, the system will display the
following message:
The media on DUAl may now be used to boot device DABO .

After you create the console diskette, write-protect it in order to prevent anyone from
accidentally overwriting the contents. To write-protect a diskette, cover the square
notch in the upper right corner of the diskette with a silver tab.
Note that in order to bootstrap the system, the console diskette must be in diskette
drive 1 .
You may wish to add the following command to the end of the
SYS$MANAGER:SYSTARTUP.COM command procedure to mount the console
diskette automatically every time you bootstrap the system. This will prevent other
users from removing the diskette thinking that the drive is not in use.
$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMEDIATE

Problems , Restrictions, and Notes

3-7

3.2.3.2 Copying the MicroVMS Operating System to the New System Disk

Take the following steps to copy the MicroVMS operating system to a disk on the
second MSCP controller.
CAUTION:

This procedure will destroy the previous contents of the new system

disk.
1.

Load the system disk in the drive and spin i t up. See the user's guide for the
disk drive for instructions.

Insert the console diskette into diskette drive 1 and mount it.
$ MOUNT/SYSTEM/FOREIGN $FLOPPY1 INTERMED IATE

Notify current users to log out. Ensure that no new user can log in. The
following command prevents users from logging in:
$ SET LOGINS/ INTERACTIVE=O

Shut down the network if it is running. Perform this step only if your system
is running DECnet-VAX. If you are not sure whether your system is running
DECnet-VAX, enter the following command:
$ SHOW NETWORK

If the following message appears, your system is not running DECnet-VAX.
%SHOW-I-NONET , network unavai lable

If your system is running DECnet-VAX, turn off the network by entering the
following commands:
$ RUN SYS$SYSTEM : NCP
NCP> SET EXECUTOR STATE OFF
NCP> EXIT

Stop all batch and print queues. To do so, perform the following tasks:
a.

Enter the following command to determine the state of all queues:
$ SHOW QUEUE/DEVICE/BATCH/ALL

Stop each active queue by entering the following command:
$ STOP/QUEUE/NEXT queue-name

where queue-name is the name of an active queue.
7.

Enter the following commands to copy MicroVMS and all other files on the old
system disk to the new system disk:
$ INITIALIZE new-disk MICROVMS
$ MOUNT/FOREIGN new-disk
$ BACKUP/ IMAGE/VERIFY/I GNORE=INTERLOCK old-disk : new-disk :

3-8

Problems , Restrictions , and Notes

where old-disk is the physical device name of the disk that currently serves as
your system disk and new-disk is the physical device name of the disk that will
serve as your new system disk.
For example, if your current system disk is DUAO: (the fixed RDS l or RD52 disk)
and you want your new system disk to be DABO:, enter the BACKUP command
as follows:
$ BACKUP/IMAGE/VERIFY/ IGNORE=INTERLOCK DUAO : DABO :

Ignore any error messages that report specific files not copied by BACKUP.
8.

To complete this procedure, enter the following command to dismount the new
system disk.
$ DISMOUNT/NOUNLOAD new-di sk

where new-disk is the physical device name of your new system disk.
3.2.3.3 Bootstrapping from the New System Disk

Take the following steps to bootstrap the system from the new system disk.
1.

Make sure that the console diskette is loaded in diskette drive 1 .

If the system is running, enter the following command to shut it down:
$ @SYS$SYSTEM : SHUTDOWN

Reply to the prompts output by the shutdown procedure by pressing RETURN.
If the system is not running, halt the system. Press the HALT button on the
processor control panel twice to enter console mode; the console-mode prompt
( > > > ) should appear on the console terminal.
3.

Bootstrap the system by entering the following command:
>>> B ddcu

where ddcu is the name of the diskette drive that contains the console diskette.
For example, if the console diskette is in diskette drive 1, enter the following
bootstrap command:
>>> B DUAl
4.

Continue with normal system startup.

When you are satisfied that your new system disk is working properly, delete all the
Micro VMS files from the old system disk. If you do not delete the Micro VMS files
from your old system disk, the system might accidentally use the old system disk if
the console diskette is not loaded in the drive.

Problems, Restrictions, and Notes

3-9

3.2.4 Error Count for Remote (RTAn:) Devices
The error count for remote terminals may be randomly incremented due to a software
protocol error. You can observe the error count by using the DCL command SHOW
DEVICE RTAn: . The increase in error count, however, does not reflect a hardware
error or any other data corruption.
This problem will be fixed in a future release of the operating system.

3.2.5 SDA COPY Command Marks SYSDUMP.DMP As Empty
The correct behavior of the System Dump Analyzer (SDA) COPY command varies
depending on whether the crash dump is in PAGEFILE. SYS or SYSDUMP.DMP. In
the former case, page file pages should be released (that is, the copy of the dump in
PAGEFILE.SYS is lost) when the copy completes. In the latter, the original dump in
SYSDUMP .DMP should be retained until the next time the system crashes or is shut
down.
In Version 4.5, SDA incorrectly marks SYSDUMP.DMP as empty after a successful
copy, indicating that the data in SYSDUMP.DMP is no longer accessible to SDA. The
dump should be analyzed using the dump file created by the SDA COPY command.
This problem will be corrected in a future release.

3.3

Application Programmer I nformation

This section describes problems resolved in MicroVMS Version 4.5, lists known
restrictions, and contains other information about the release of interest to the
application programmer.

3.3. 1 SS$_NOENTRY Error Reported in XABPRO Block for
ACL-Protected Files
In Versions 4.4 and 4.5 of MicroVMS, files that have access control lists (ACLs)
associated with them will get a status return of SS$_NOENTRY in the XAB$L _
ACLSTS field of the XABPRO block if this XABPRO block was associated with the
file when it was opened.
There are two suggested workarounds:
1.

Ignore the status and check the size of the access control list (XAB$W_ACLLEN)
returned by RMS to ensure that the user buffer size was large enough to contain
the ACL.

Perform a $DISPLAY operation after opening the file. This will correctly return
the status in XAB$L _ACLSTS.

3-1 0

Problems, Restrictions, and Notes

This problem will be corrected in a future release of the operating system.

3.3.2 Ethernet/802 Drivers: Promiscuous Mode Change Planned
Software that currently utilizes the promiscuous mode feature of the Ethernetj802
drivers may need to be modified to run properly on future releases of the operating
system. Since the Ethernet/802 drivers now allow a wide variety of packets to be
transmitted and received, some restrictions will be placed on channels that turn on
the promiscuous mode (NMA$C_pCLJ_pRM) parameter. When this parameter is
turned on, the following rules will apply:
•

Both Ethernet and IEEE 802 formatted packets will be received. The PS buffer, if
specified, must be at least 1 6 bytes long.

•

Only one type of packet may be transmitted: either Ethernet or IEEE 802. The
value of the NMA$C_pCLIJMT parameter will be used to determine which
format will be used for transmissions.

•

The NMA$C_pCLI_pAD parameter will be ignored during READ operations on
channels that are running in promiscuous mode.

•

The promiscuous mode channel may not be put into SHARED access mode.
Attempts to put the promiscuous mode channel into shared mode will result in
an SS$_BADP ARAM error.

Applications using the promiscuous mode feature should note these planned
restrictions. Those applications should be modified to run within these restrictions
before the restrictions are applied and shipped in the VMS Ethernet/802 drivers.

3.3.3 Ethernet Controller: List of Expected Errors
Certain Ethernet controllers support features that allow them to communicate with
the hardware outside the VAX system to detect hardware failures. If the hardware
connected to the Ethernet controller does not support these "hardware failure
detection" features, then the controller and driver will report errors which are not
true errors.
To facilitate the detection of true errors, use the following list of "expected" errors
to eliminate those errors which are caused by the lack of hardware failure detection
support.
•

When using the DEQNA with the DECOM transceiver, a "Send failure" with
reason code "Short circuit" will be reported for each packet transmitted.

•

When using the DEUNA or DELUA with broadband, a "Collision detect check
failure" will be reported for each packet transmitted.

Problems, Restrictions, and Notes

3-1 1

3.3.4 Documentation Correction: IO$M_QUTBAND
Please replace the description of IO$M_OUTBAND on page QI0-25 of the
MicroVMS Programming Support Manual with the following text:

IO$M_OUTBAND [.OR. IO$M_INCLUDE] [.OR. IO$M _TT_
AB ORT ]

Delivers an AST for the process if the user enters any control character
specified in P2. Only one AST can be queued. An out-of-band AST
is a repeating AST and will remain queued until explicitly disabled.
Specify 0 for P1 if the AST entered on the channel is to be canceled.
The optional IO$M_INCLUDE modifier includes the control character
in the data stream. The optional IO$M_TT__ABORT modifier aborts the
current 1/0 operation.

3.3.5 Documentation Correction: FORTRAN IBITS Function
On page FOR-1 28 of the MicroVMS Programmer's Manual, please correct the
argument list for the IBITS function so that
IBITS(start_position,encLposition,integer)
is replaced by
IBITS(integer,start_position,end_position)

3.3.6 Documentation Corrections: SMG$SET_KEYPAD_MQDE and
SMG$READ_STRING
In the description of SMG$SET_KEYPAD_MODE on page RTL-233 of the MicroVMS
Programming Support Manual, please reverse the mode values in the table so that 0
indicates numeric mode and 1, applications mode.
In the description of SMG$READ_STRING on page RTL- 2 1 8 of the same manual,
please add the following term-code values to those listed:

3-1 2

Problems, Restrictions, and Notes

Keyname

Code

FIND

31 1

INSERT

312

REMOVE

313

SELECT

314

PREY

315

316

3.3.7 SCNRTL Problems Corrected
Version 4.5 corrects the following VAX SCAN Run-Time Library (SCNRTL)
problems:
•

A PRUNE statement causing an access violation, depending on the order in
which nodes have been added to the tree that is being pruned.

•

A call to SCN$GET_TOKEN__NAME resulting in an access violation during
virtual memory cleanup.

•

Specification of VARYING STRING as the input stream resulting in data
corruption, because of the length being improperly determined from the
descriptor.

3.3.8 Debugging Shareable Images-Change in Behavior from
Pre-Version 4.4 Releases
If, prior to Version 4.4, you linked your shareable images using the LINK/SHARE
command, you should be aware that linking shareable images in this manner will
now result in traceback information being passed to the shareable image.
When you debug your program, and execution is suspended within that shareable
image, the debugger will set the image automatically. This is called dynamic image
setting.
This will result in different symbolic information being made available. For example,
the display for SHOW CALLS will look different. In contrast to module setting, the
symbol information for only the currently set image is available at any one time.
If you prefer the old behavior, you can link your shareable image with the command
LINKJSHAREJNOTRACE. Traceback information will not be present in the image
and DEBUG will not set the image.

Problems , Restrictions , and Notes

3-1 3

To take full advantage of the new shareable image support, you should link your
shareable image with the command LINK/SHARE/DEBUG. Then full symbol table
information will be available, the debugger will set the image, and you can perform
symbolic debugging of that shareable image.

3.3.9 Debugger Window-Change in Behavior from M icro VMS V4.4
Prior to MicroVMS Version 4.5, if the debugger detected that it was running on
a VAXstation, it would create a separate emulated terminal window for its own
input and output. This meant that terminal I/0 performed by the program was
logically and physically separated from the debugger's I/0- an arrangement that
was particularly helpful in debugging screen mode applications.
In order to remove a potential problem on the VAXstation, the method that the
debugger uses to control the separate window has been changed. Previously, the
debugger controlled the separate window with UIS$xxx calls. It now uses the new
Operating System Command (OSC) sequences to communicate control functions to
the terminal emulator.
With this update, the debugger's behavior is slightly different. It will still create a
separate window, but only if the VAXstation meets both of the following conditions:
•

It must be running the SDC release of VWS 3.0 (or higher).

•

You must have defined the system logical name UIS$VT_ENABLE_OSC_
STRINGS as follows:
$ DEF INE /SYSTEM/EXEC

UIS$VT_ENABLE_OSC_STRINGS

TRUE

This patch also includes fixes for several other non-VAXstation bugs.

3.3.1 0 Failure of VAX BASIC SET I NITIAL CHOICE Statement
In VAX BASIC Version 3 .0, the SET INITIAL CHOICE statement will fail when it is
used with a choice array with no count specified. To avoid this problem, specify a
count clause when you use this statement.
This problem will be corrected in a future software release.

3-1 4

Problems , Restrictions , and Notes

3.3. 1 1 SYS$CREMBX and Process-Private Logical Names
Version 4.4 introduced a change to the behavior of logical names that are
automatically created as a part of mailbox creation or when a volume is mounted.
Specifically, if a logical name table has been redirected to point to a process-private
name table, the logical name is no longer deleted when the mailbox disappears or
the volume is dismounted. (See the MicroVMS Release Notes Version 4.4 for details of
this change.)
Version 4.5 completes the decoupling of associated logical names from their
creator when the names are placed into a process-private table. This change may
affect a small number of programs that use the Create Mailbox system service
(SYS$CREMBX).
Programs will only be affected under the following set of circumstances.
•

The associated logical name table (LNM$TEMPORARY_MAILBOX or
LNM$PERMANENT_MAILBOX) has been redefined to point to a process-private
table.

•

The program issues several $CREMBX calls from several threads of execution,
using the same logical name.

The new behavior is that each call to $CREMBX under these circumstances will cause
a new mailbox unit to be created and assigned to a new channel.
Note that applications that place mailbox names into shared name tables are
unaffected by this change. That is, the second and succeeding calls to $CREMBX
will assign new channels to the existing mailbox unit.
Note further that applications using several cooperating processes are also unaffected,
even if the names are placed into a process-private table. (If the names existed in a
process-private table, they were invisible to other processes even before this change
was made.)

3.4

System Programmer I nformation

This section describes problems resolved in MicroVMS Version 4 .5, lists known
restrictions, and contains other information about the release of interest to the system
programmer.

Proble m s , Restriction s , and Notes

3-15

3.4. 1 NETACP Verification of MOP Messages
Version 4.5 of the network ancillary control program (NETACP) performs some
verification before it starts up a maintenance operation module (MOM) process to
service an incoming maintenance operation protocol (MOP) request.
NETACP will only start up a MOM process under the following conditions:
•

The request is not directed at a multicast address.

•

The source node specified in the MOP request is defined in NETACP's node
database.

•

The MOP message requests an operating system and contains the software
identification of the file to be loaded.

•

The MOP request is not for a load or dump.

If NETACP does not start up a MOM process, it will generate an event message
of type 0. 7 (aborted service request, Line open error). The Ethernet address of the
source node will also be displayed with the message.

3.4.2 Behavior of Zero-Length and Negative Byte Counts Submitted
in $QIO Requests
Version 4 . 4 introduced a change into function-decision table (FDT) routines that
prevented negative byte counts from being passed to the Queue-I/O Request system
service (SYS$QIO) and its support subroutines. This check also disallowed byte
counts of zero. While this change did not affect any drivers that are part of the VMS
kit, it may have caused problems for user-written drivers.
Version 4.5 relaxes the restriction. While negative byte counts still cause an error
return of SS$_BADP ARAM, zero-length byte count transfers are again allowed.

Appendix

MicroVMS Version 4.5 Update Description
This appendix contains a listing of the patches, new images, and miscellaneous
fixes contained in Version 4.5 update kit. This listing is obtained from the text file
SYS$UPDATE:VMS045.TXT that is produced by the installation procedure if option
2 or 3 is selected, as described in step 4 of Section 1 .3.
1 ) ADARTL (patch image)
ADARTL . EXE
EC001

SBL
23-Apr- 1 986
MODULE : ADA$END_OF_FILE (X-3)
SPR : 1 1 -87184
An uninitial ized variable prevent ed END_OF_FILE from
returning a consi stent value when used in packages
DIRECT_IO or DIRECT_MIXED_IO .

2) AGEN (mi s c ellaneous f ix)
AUTOGEN . VUG
EC001

23-May - 1 986
GHC0002
MODULE : AUTOGEN
Set up to use the appropri at e AUTOGEN update f i l e based
on which version of AUTOGEN currently exists on the
system .

3) AUTOGEN ( edit text f i l e )
AUTOGEN . COM
EC001

12-May - 1 986
GHC0005
MODULE : AUTOGEN
All ow ADD_ , MIN_ , MAX_ symbols in MODPARAMS . DAT f or any
numeric SYSGEN paramet er . Start the MSCP s erver early in
the boot cycle .

A-2

MicroVMS Version 4.5 U pdate Description

4) BACKUP (pat c h image)
BACKUP . EXE
EC0006

KGW00021
30-May - 1 986
MODULE : TAPEUTIL
Pat ch MUST be appl ied to VMS V4 . 4 syst ems ONLY .
Exc essive parity errors on a TA78 would result in
ac c ess to the tape being lost .
Repair thi s by unloading the tap e if the RESTART
opt ion is taken from the error handler .

5) BASRTL (pat c h image)
BASRTL . EXE
EC001

04 -Mar - 1 986
JCW1003
MODULE : BAS$POWHH
F ix SPR 1 1 -8476 1 . Routine sometimes incorrectly
returned a negat ive result .
07-Apr- 1986
KC2009
MODULE : BAS$CTRLC
Clear ASTs only if the user is trapping CTRL/Cs .
KC20 1 1
18 -Apr- 1986
MODULE : BAS$ERROR
Change OPTION HANDLE semant i c s .
20-Apr- 1986
KC 1 1 19
MODULE : BAS$0PEN
OPEN_HANDLER should free the wildcard c ont ext that
get s al located .

EC002

15 -May- 1986
KC 1080
MODULE : BAS$$UDF_WL
Fix SPR 1 1 -87232 . PRI NT 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10
c orre ct ly does not repeat the ninth el ement .
15 -May- 1986
KC 1019
MODULE : BAS$$EXIT_HANDL
PUTMSG and UNWIND inst ead of resignaling c onditions .
15 -May- 1986
KC 1012
MODULE : BAS$$PUR_I O_BUF
If the RAB IS! is zero , do not try to purge the
dirty buff er .

MicroVMS Version 4.5 Update Description

A-3

16-May- 1986
KC1 1 19
MODULE : BAS$0PEN
Fix quad-key test .
EC003

19-May- 1986
KC1063
MODULE : BAS$CVT_OUT
Fix PRINT USING and FORMAT$ packed decimal bug .

EC004

1 6 - Jun- 1986
KC201 2
MODULE : BAS$ERROR
Fix an ON ERROR GO BACK bug .
non-BASIC errors .

Fix handling of

KC 1 120
24- Jun - 1 986
MODULE : BAS$0PEN
Fix OPEN_HANDLER so it doe s not de stroy the
expanded string name .
6) BASRTL2 (patch image )
BASRTL2 . EXE
EC0001

Bundled f ixes for V4 . 5 .
25-Feb- 1986
KC1010
MODULE : BAS$GR_OUTPUT_MISC
Complain if the user spec i f i ed one point , did not have a
s emicolon , and the b eam was not previously on .
25-Feb - 1 986
KC1005
MODULE : BAS$GR_I NIT_INP
For cho ic e , verify that the c ount specif i ed is within the
size of the array .
25-Feb- 1986
KC1006
MODULE : BAS$GR_SET_ECHO_AREA
For cho ic e , call the routine that handle s INQ_CHO ICE_STATE .
27-Feb- 1986
KC1008
MODULE : BAS$GR_ASK_ECHO_AREA
For choi c e , call the routine that handles INQ_CHO ICE_STATE .
02-Mar- 1986
KC1015
MODULE : BAS$GR_ASK_MI SC
Change ASK TEXT ANGLE formula .

A-4

MicroVMS Version 4.5 Update Description

KC1010
02-Mar - 1 986
MODULE : BAS$GR_ASK_CAP
ASK MAX COLOR should return NPREIDX - 1 .

EC0002

KC1019
02-Mar - 1 986
MODULE : BAS$MAT_ASSIGN
Correct c onversion to double precisi on to handl e scaling
properly .
More bundled f ixes for V4 . 5 .
06-Mar - 1 986
KC1007
MODULE : BAS$GR_INIT_INP
Fix earl i er patch for edit KC1007 to ref lect the source
f ix .
KC1 0 1 1
06-Mar- 1986
MODULE : BAS$GR_ERROR
In SCAN_ERROR , only scan the l ist if the l ist was
spec i f i ed .

EC0003

More bundled f ixes for V4 . 5 .
15 -Mar - 1 986
KC1 009
MODULE : BAS$GR_ASK_ECHO_AREA
For string input , make sure the string descriptor has a
A nul l string is not valid .
nonzero pointer .
KC 1019
15-Mar - 1 986
MODULE : BAS$$GR_UTIL
Change the exit handler to be a special routine that
calls GKS$EMERGENCY_CLOSE .
17-Mar- 1986
KC1 006
MODULE : BAS$GR_INIT_INP
For point , ini tialize RET_S IZE to work around a GKS bug .

EC0004

More V4 . 5 bundled f ixes .
19-Apr- 1986
KC1005
MODULE : BAS$ INKEY
If we get a CTRL/C then signal CTRL/C .

EC0005

More V4 . 5 bundled fixes .
KC1015
15-May - 1 986
MODULE : BAS$GR_CTRL
CLEAR_WS should updat e the workstat i on .

MicroVMS Version 4.5 Update Description

A-5

15-May- 1986
KC101 1
MODULE : BAS$GR_OUTPUT
If the c ount spec if i ed is larger than the size of
the arrays then signal an error .
15-May - 1986
KC 1007
MODULE : BAS$GR_ INIT_ INP
If the count spec if i ed is larger than the size of the
arrays , then signal an error .
Also , DIM paramet er should
be read/write storage not read-only . Also , f or valuator ,
check that the initial value is within the range .
KC 1013
15-May- 1986
MODULE : BAS$GR_INPUT
LOCATE VALUE should check that the init i al value is within
the range , if one is spec ified .
16-May- 1986
KC 1012
MODULE : BAS$GR_OUTPUT
Correctly handle cases where the user spe c if i ed too f ew
c oordinat es .
16-May - 1 986
KC 1010
MODULE : BAS$GR_SET_VIEWING
Fix SET_INP_PRIO .
16-May - 1986
KC1012
MODULE : BAS$GR_ERROR
Translat e some new messages .
EC0006

More V4 . 5 f ixes .
20-May- 1986
KC1008
MODULE : BAS$GR_ASK_WS
Check that the t ext extent arrays are at l east four
elements long .
KC1013
22-May - 1 986
MODULE : BAS$GR_ERROR
Translat e some more messages .
27-May - 1 986
KC1008
MODULE : BAS$GR_INIT_ INP
Correct KC1007 .
27 -May - 1 986
KC1014
MODULE : BAS$GR_INPUT
Correct KC 10 1 3 .

A-6

MicroVMS Version 4.5 U pdate Description

EC0007

More V4 . 5 f ixes .
KC1014
16-Jun- 1986
MODULE : BAS$GR_ERROR
Fix the trans lat i on table .

7) COBRTL (patch image)
COBRTL . EXE
EC001

MDL
0 1 -Apr- 1986
MODULE : COB$ACCEPT , routine COB$ACC_SCR
Zero FIRST_CHARS_READ when there is a conversion
error in the case of NO BLANK CONVERSI ON .
Otherwise
corrupt data can b e returned on a reprompt .

EC002

MDL
14-Apr - 1986
MODULE : COB$ACCEPT , routine COB$ACC_SCR
Reset ACC_S IZE in the same situati on as above (EC00 1 ) .

EC003

MDL
14-Apr- 1986
MODULE : COB$ACCEPT , rout ine COB$$ILLEGAL_TERM
Subtract off F IRST_CHARS_READ when f iguring remaining
number of charact ers to get aft er an i llegal terminator
has b e en ent ered and the f i eld is not full yet .

EC004

MDL
1 2 -May - 1986
MODULE : COB$ACCECV , routine COB$$NUMERIC_CONV
Fix stripping of trailing zeros after the dec imal point .
This is a c orrection to edit 1 -002 , introduc ed in V4 . 4 .

8) CONVSHR (patch image)
CONVSHR . EXE
ECO 1

JWT0238
23 -Apr- 1986
MODULE : RECL$REC
CONVERT/RECLAIM can leave behind part ially
rec laimed buckets under the same c ircumstances
as the earli er problem discovered with the
reclaiming of records with key c ompression .
If any nondeleted record is encountered in
the bucket , don ' t modify the bucket .

MicroVMS Version 4.5 Update Description

A-7

9) CTDRIVER (new image)
CTDRIVER . EXE
1 1 -Mar - 1 986
EC00001 DSS003
Add quota checking to prevent RWAST state . Add OOB
INCLUDE checking .
10) DCL (new image)
DCL . EXE
EC001

HWS0002
1 6-May- 1986
F ix various DCL problems .

1 1 ) DCLTABLES (mi s c e llaneous f ix)
DCLTABLES
EC001

HWS0001
1 6-May- 1986
Updat e the c ommand def init ion f or SET .

12) DEBUG (patch image)

DEBUG . EXE
EC001

RT001
Apr- 1986
Part of the patch to turn DEBUG V4 . 4 into DEBUG V4 . 5 .
Thi s ECO f ixes two bugs in the shareable image support .

EC002

RT002
Apr- 1986
Part of the patch to turn DEBUG V4 . 4 into DEBUG V4 . 5 .
Thi s ECO f ixes two more bugs : a bug with examining
arrays who s e elements are larger than 2* * 1 6 byt es , and
a bug in which the debugger inf init e - loops if an Ada a
program has BPT instruct ion in it which was not plac ed
there by the debugger .

EC003

RT003
May- 1986
Correction to f ix #1 . Make sure we set the SEC$M_WRT
bit as well as the SEC$M_CRF bit .

EC004

RT004
May- 1986
Fix a problem where DEBUG fails with UIS V3 . 0 on VAX
stati ons if the default VT220 window size i s set to
anything other than 24 by 80 .

A-8

M icroVMS Version 4.5 Update Description

EC005

RT005
Jun- 1 986
Fix error in EC004 .

EC006

RT006
Jul - 1 986
Change the method DEBUG uses to control the s eparat e
window it creates on a VAXstat ion to using the terminal
emulator OSC sequenc es . This avoids a pot ent i al VAXstat ion
hang or crash situat ion .

13) DTKRTL (miscellaneous f ix)
DTKMSG . OBJ
1 -002

TS
1 1 -Apr - 1 986
MODULE : DTK$MSGDEF
Add the error messages f or the DTK$
fac i lity to STARLET . OLB so users can
ac c ess them from their s ourc e code .

14) DTKSHR (new image)
DTKSHR . EXE
1 -003

TS
1 1 -Apr - 1 986
MODULE : DTK$UTIL
Fix to an int ernal rout ine , DTK$$GET_STATUS
for a t iming probl em with reading back a phone
status from the DECtalk .

MicroVMS Version 4.5 Update Description

A-9

15) DUDRIVER (new image)
DUDRIVER . EXE
EC003

MAS0065
27 -May- 1 986
Fix conne ct i on walking bug that leads to spurious host
c lears of HSCs f o l l owing virtual c ircuit fai lures during
fai lover . Corre ct other mi scel laneous probl ems involving
host and controller t imeouts . Relevant modu l e audit
versi ons are DUDRIVER (X-27) and DUTUSUBS (X-30) .

EC002

16 -May- 1986
PRD0226
MODULE : DUDRIVER
Relink with new DUTUSUBS so image matches V4 . 5 stream .

EC001

26 -Apr - 1 986
ROW0560
MODULE : DUDRIVER
Fix the SSM test aft er RECORD_UNIT_STATUS in IO$_PACKACK
proc essing to us e R3 (the UCB address) inst ead of R5
(the CORP address) .

16) ERFBRIEF (patch image)
ERFBRIEF . EXE
EC001

SAR0496
17 -Apr - 1986
MODULE : BRIEF_C_DI SPATCHER
Enable VAXBI port communicat i ons control ler support .
MODULE : BRIEF_DEVI CE_ENTRY_ROUTINES
Enable VAXBI port communicat i ons controll er support .

17)
ERFBUS . EXE
EC001

SAR0500
16-Apr- 1986
MODULE : DECODE_PA_PB_DRIVER_ENTRIES
Correct output of PMDATR and control store value .
Updat e PESR MISC t ext as per new CI code s .

A-1 0

MicroVMS Version 4.5 Update Description

18) ERFCTLSHR (patch image)
ERFCTLSHR . EXE
EC001

23-Apr- 1986
RAP0093
MODULE : RECSELECT . B32
Current ly when /BEFORE is selected and we are pro cessing
a rec ord lat er than the date spec if i ed ERF exits
prematurely . This patch al lows ERF to continue proc essing
subsequent rec ords .

EC002

23-Apr- 1986
RAP0095
MODULE : ERFCONTRL . B32
Initial ize SYE$L_OPTIONS with ' S ' before call ing
FULL_DISPATCHER . Updat e the version numb er of
ANALYZE/ERROR_LOG .

1 9 ) ERFLIB (new f i l e )
ERFLIB . TLB
EC001

15 -Apr- 1986
SAR0505
MODULE : N/A
Enabl e AIE-NI support .

20) ERFPROC1 (patch image)
ERFPROC1 . EXE
EC00 1

09-Apr- 1986
RAP0092
MODULE : MSCPTXT . B32
Text change : RETRIES <-- RETRIES LEFT
Thi s f i eld was incorrectly translated as the number of
retri es l eft .

EC002

29-Apr - 1 986
SAR0503
MODULE : PADRIVER_LOGMESSAGE
Updat e port t ext rout ine .

EC003

RAP0 103
06- Jul - 1 986
MODULE : RAXXDVDP . B32
Only call DECODE_HSC_REQUESTOR if controller is an HSC .
MODULE : MSCPDTDSP . B32
Change the known length of SDI format packet from 56
to 49 .

MicroVMS Version 4.5 Update Description

2 1 ) ERFSHR (patch image)
ERFSHR . EXE
EC001

SAR0502
29-Apr - 1 986
MODULE : DECODE_PA_PB_SHARE
Add AIE-NI support .

EC002

28-Apr- 1986
RAP0094
MODULE : LOGGER . B32
Add 8700 and 8550 support .

22) ERFSHR2 (patch image )
ERFSHR2 . EXE
EC001

SAR0499
22-Apr- 1 986
MODULE : DECODE_BI IC_REGISTERS
Correct the AIE/AIO DTYPE values and the index
cal culat i on for the NSLAVE_RTN tabl e .

23) ETDRIVER (new image)
ETDRIVER . EXE
EC001

02-Apr - 1 986
RBH0001
MODULE : ETDRIVER
Add support for VAXB I port c ommuni cat ions devi c e .

EC002

16-May - 1 986
RBH0002
MODULE : ETDRIVER
Inc lude support for IEEE 802 protocol and multiport
synchronization .

A-1 1

A-12

MicroVMS Version 4.5 U pdate Description

24) F 1 1AACP (patch image)
F1 1AACP . EXE
EC001

ACG052 1
20- Jun-1986
MODULES : NONE
Bui ld a pat ch descriptor f or the remaining unused spac e
in the image f i l e .

EC002

20- Jun- 1986
ACG052 1
MODULES : DISPAT , IODONE
Correct the di spatching of IO$_DSE (data security erase)
functions when they are sent to the f i l e syst em f or a
window turn .

25) F 1 1BXQP (patch image)
F 1 1BXQP . EXE
EC00 1

ACG05 1 9
08-May- 1986
MODULE : CREATE
Correct a probl em that could result in noncont i guous
space allocation on F i l es- 1 1 subset 0 volume s ets .

EC002

1 1 - Jun- 1 986
LMP0331
MODULE : DEACCS
Undo the change made in LMP033 1 to enable the prot ection
check on the wri t e attribut es call .

EC003 ,
EC004

20- Jun- 1986
ACG0521
MODULES : DISPAT , IODONE
Correct the di spatching of IO$_DSE (data s e curity erase)
funct i ons when they are sent to the f i l e syst em for a
window turn .

EC005

14-Jul- 1986
ACG0523
MODULE : DIRSCN
Correct a problem that resulted in new vers ions of
f i l e s created on a volume set sometimes acquiring
incorrect prot ection and ownership attribut es .

EC006

1 5 - Jul - 1986
ACG0524
MODULE : DELFIL
When a multivo lume f i l e is del et ed , ensure that the
f i l e ID of the primary header is rel eased on the right
volume . This probl em occasionally caus es HDRNOTMAP
bugchecks when operating on volume sets .

MicroVMS Version 4.5 Update Description

A-1 3

26) FORRTL (pat ch image)
FORRTL . EXE
EC001

KC 1018
12-May - 1 986
MODULE : FOR$ INQUIRE
Fix QAR 1 7 1 from the V4 . 4 databas e .
INQUIRE should
be sure to dispens e with the wildcard context
c reat ed for use by RMS .

27) JOBCTL (pat ch image)
JOBCTL . EXE
EC001

02 -Apr - 1 986
JES000 1
MODULE : ACCOUNTNG
Remove call to CLEAR_ACCOUNTING_FLAGS from rout ine
CLOSE_ACCOUNTING_F ILE to fix bug where a SET ACCOUNTING
/NEW would unint ent ionally turn off acc ount ing .
Add a call to CLEAR_ACCOUNTING_FLAGS in rout ine
WRITE_ACCOUNTING_FILE to turn off ac c ounting if there
is an error whil e trying to writ e to the acc ounting f il e .

EC002

JES002
02-Apr - 1 986
MODULE : SNDJBC
Add a call to CLEAR_ACCOUNTING_FLAGS to fix c ommand
Previously thi s c ommand would
SET ACCOUNTING/DISABLE .
have had no eff ect . Now ac c ount ing is turned on with
all opt ions as stat ed in the doc umentat i on .

EC003

16-Apr - 1 986
JES003
MODULE : SNDJBC
Check status aft er call to ENQUEUE_JOB in routine
ALTER_JOB . If an error is returned do not rewrite the
j ob r e c ord .

EC004

16-Apr - 1 986
JES004
MODULE : SCHEDULER
Check status aft er call to ENQUEUE_JOB in routine
AFTER_NONAST . If an error is returned do not rewrit e the
j ob r e c ord .

EC005

16-Apr- 1 986
JES005
MODULE : SYMBIONT
Check status aft er call to ENQUEUE_JOB in routine
PROCESS_SYMBIONT_MESSAGE .
If an error is returned do not
r ewrit e the j ob rec ord .

A-1 4

MicroVMS Version 4.5 Update Description

EC006

JES006
12-May - 1 986
MODULE : EXECUTOR
Cal l FIND_PENDING_JOBS in RESUME_EXECUTION rout ine to f ix
bug where j obs that c ould execut e aft er a queue had b e en
start ed remained pending .

EC007

12 -May - 1 986
JES007
MODULE : SCHEDULER
Call EXECUTOR_ACCEPTS_JOB a f inal time in FIND_AVAILABLE
_EXECUTOR to ensure that the j ob ' s f orm is c orrect .

EC008

2 1 -Aug- 1 986
JES008
MODULE : CONTROL
Null ify use of VMSD2 paramet ers by c l earing the
FLAGS_V_READ_VMSD2 bit .

28) LBRSHR (new image)
SYS$LIBRARY : LBRSHR
ROP0084
02-Apr- 1986
Correct truncat i on of help text .
29) LIB (mi s c e llaneous f ix)
LIB . MLB
EC002

EJL004
13-May- 1986
MODULES : $ADPDEF , $BVPDEF
Add VAXBI VAX Port definit ions .

EC001

EJL003
24-Apr- 1986
MODULE : $CIBDTDEF
Correct CI BOT alignment .

30) LPDRIVER (new image)
LPDRIVER . EXE
03-Mar- 1986
EC00001 RRB0001
Fix byt e c ount quota prob l ems when I/0 fails . Support
uppercase charact ers for open and c lose brac e characters .

MicroVMS Version 4.5 Update Description

A-1 5

3 1 ) MAIL (pat ch image)
MAI L . EXE
ECO 1

12- Jun- 1986
ROP0095
Check f or nodes in a c luster when
running as a server .

32) MONI TOR (patch image)
MON ITOR . EXE
EC0001

28-Apr- 1986
MODULE : COLLECTION_EVENT/CLASS_INIT
During class initializat ion , check to
det ermine whether we are monitoring a mult iproc es sor .
If we are , larger data buff ers are needed for the
modes c lass . Thi s code path was being taken more than
onc e if more than one dual pro c essor was being monitored .
This result ed in a divide-by-zero error with the CLUSTER
c lass and bogus data f or MODES and SYSTEM classes .

33) MTAAACP (patch image)
MTAAACP . EXE
EC00 1

1 6-May - 1 986
JWT024 1
MODULE : END_OF_VOL
When encountering a serious exc ept ion , clear
it bef ore c al ling START_VIO . Failure to c lear
the s erious exc ept ion f or HSC tapes was causing
the pro cess to hang and lock up the drive .

34) NCP (patch image)
NCP . EXE
EC000 1

12-May- 1986
SFN004
MODULE : NCPTABLES
Modify the ASCI I string as soc i at ed with the line BUFFER
SIZE paramet er .
It used to read "UNA device buffer size " ,
change to read "Devi c e buffer size " .

A-1 &

MicroVMS Version 4.5 Update Description

35) NETACP (pat ch image)
NETACP . EXE
* * * NOTE : ECOs 14 through 16 were from the V4 . 4 mandatory
updat e . ECO 17 was assigned a number and we then dec ided
to start renumbering from ECO 1 .
Onc e all ECOs ( i . e . . up
t o and inc luding 13) are used , we must skip up to ECO 18 .

EC0014

PRB014
27-Mar- 1986
MODULE : NETACPTRN
Work around problem of misaligned LTB structure .
For now , save size of structure when allocated , and
restore it j ust before it ' s deallocat ed . Also f ix type
f i eld .

EC0015

27-Mar- 1986
PRB015
MODULE : NETACPTRN
Copy al ias l ink regi on to new LTB when enlarging LTB on
the f ly .

EC0016

PRB016
01 -Apr- 1986 ( ignore impli cations )
MODULE : NETCLUSTR
Dequeue lock to a node ' s ILR when dequeuing its IDL .
Otherwi se , as nodes come and go in the c lust er , NETACP ' s
ENQLM i s slowly eroded .

EC0 17

1 1 -Apr- 1986
BAS
MODULE : NETCNFDLL
Change the DEVTRN entry for DSV to al low mult iple units
on a contro l l er .

EC001

LY
30-Apr- 1986
MODULE : NETTRN - code , NETTRN - NET_IMPURE psect
Change timer handl ing to use delta time instead of
absolut e .

EC002

08-May- 1986
PRB
MODULE : NETCONF IG
Change versi on number for V4 . 5 .

EC003

08-May- 1986
PRB
MODULE : NETCNFDLL
Fix problem where NETACP would remember the volat i l e
s etting o f t h e PS I paramet er MICROCODE DUMP from o n e call
to the next .

MicroVMS Version 4.5 U pdate Description

A-1 7

EC004

PRB
09-May- 1986
MODULE : NETDLLTRN
Don ' t allocate c ost/hops buffer in end node on designat ed
rout er trans it ion .

EC005

SN
14-May- 1986
F ix the DSV devi ce table entry in module NETCNFDLL .

EC006

MMD394
1 6-May- 1986
Fix the NET$PROC_XWB such that , if an error o ccurred while
pro c essing the f i e lds in the CI message , the logi cal link
is not created and the XWB is deleted .

EC007

SN
1 6-May- 1986
Add algorithm into NETACP such that NETACP will not start
up MOM unle s s 1 ) the request ing node is in the database ,
2) the MOP mes sage has a software ID in it , 3 ) the request
is not for the multi c ast address .

EC008

16-May- 1986
SN
Add new formatting routine to NETEVTLOG to account for the
event to be output if NETACP chooses not to start up MOM .

EC009

0 1 - Jun- 1986
PRB
MODULE : NETACPTRN
Fix problem with LTB getting corrupt ed when number of
local links is decreased whi le number of alias links i s
increas ed .

EC0 10

PRB
14-Jul- 1986
** reserved * *

EC0 1 1

23- Jul - 1986
PRB
* * reserved * *

EC0 12

06-Aug- 1986
LMP0384
MODULE : NETCNFDLL . MAR
Ensure that the Ethernet obj ect ' s UCB is appropriat ely
prot ect ed .

36) NETCONFIG ( edit text f i l e )
NETCONFIG . COM
EC001

26-Mar - 1 986
TRC0041
Re-add the line for PA that got dropped in X-5 .

A-1 8

M icroVMS Version 4.5 Update Description

37) NETDRIVER (patch image)
NETDRIVER . EXE
EC003

PRB03
27-Mar- 1986
MODULES : NETDRVNSP . MAR , NETDRVXPT . MAR
If packet is marked "return to sender" , use the sourc e
link ID , not the destination link ID , in sel ect ing whi ch
node in the c luster should get the packet . This prevent s
unwarrant ed link t imeouts ( inst ead o f timely notification)
when attempting to access an unreachable node with an
obj ect with OBJECT ALIAS OUTGOING enab l ed , which results
if the returned packet is misdirected within the c luster .

38) NMLSHR (patch image)
NMLSHR . EXE
EC001

10-Apr-1986
BAS
MODULE : NMLSEDEST
Correct database IDs f or s ix dest ination parameters of
the X29-SERVER databas e : SDTE , ROTE , COTE , IDTE , RED ,
and NET .

39) NODRIVER (patch image)

! NODRIVER . EXE
EC003

MMD0381
08-Apr - 1 986
Fix to the DDCMP ' s REQUEUE_XMT routine to save R2
around the call to DDCMP$SETCRC .

40) PATCH (patch image)
PATCH . EXE
EC001

16-May-1986
JAK0001
02-Apr - 1 986
JMS0001
MODULE : PATWRT
Fix l ogic which comput es the next block address for
mult iblock image headers when updat ing the bas e VBN
in the ISDs .

MicroVMS Version 4.5 Update Description

A-1 9

4 1 ) PBDRIVER (new image)
PBDRIVER . EXE
EC001

WCY0050
01 -May- 1986
MODULE : PBDRIVER
Change the BDT alignment from quadword to octaword
in FPC$ INITIAL routine .

42) PUDRIVER (new image)
PUDRIVER . EXE
EC001

14-May - 1986
RLRPURHANG
MODULE : PUDRIVER
Software workarounds for two problems that sometimes
cause UDA port s to hang .
1 . Introduc e abi l ity to alleviat e " lo st interrupts "
b y calling POLL_RSPRING from PU$SA_POLL under appropriate
conditions .
2 . In I SR (PU$ INT) copy PDT$W_CMDINT and PDT$W_RSPINT to
UCB$W_PU_CMD INT and UCB$W_PU_RSPINT respectively and only
test for PURGE requests if b oth these flags are zero .
This corrects a timing error in UDA50 that sometimes
leaves UDA50 hanging waiting f or a signal that purge has
been done .
27-Aug- 1986
RLRGLBPAGE
Fix probl em encountered when doing unaligned I/0
to or from a global page . F ix is in SETUP_COPY_SEGx
routines .

43) REMACP (patch image)
REMACP . EXE
EC001

DSS0001
17-Mar- 1986
MODULE : REMPROTCL
Set the UCB for a remote dev i c e online only aft er
the address of CTDRIVER has been inserted .

A-20

MicroVMS Version 4.5 U pdate Description

4 4 ) REMOVE ( edit text f i l e )
REMOVE . COM
EC001

05-May- 1986
JES0001
Fix bug where the ent ire system would be r emoved
if SEARCH . EXE did not exist .
Fix bug where a given bad subopt ion would
result in an undef ined symbol error .
Fix bug where a list of opti ons is given f or
delet ion and only the f irst opt ion gets del et ed .

45) RMS (new image)
RMS . EXE
EC0 1

EJ030 1
01 -Apr - 1 986
MODULE : RMOSTALL
Che ck for fai lure in the $DCLAST call in order
to avoid hanging a number of pro c esses wait ing
for a lock .
07-Apr- 1986
PJH0001
MODULE : RM1GETINT
Timeouts on record locks for shared sequent ial f i l e
can c ause proc ess to b e deleted . Probl em o c curs when
wait-on-t imeout must give up bucket lock and do esn ' t
go back and get bucket lock after record l ock i s granted .
Patch is to go back and get bucket lock .
KPS03 1
09-Apr- 1986
MODULE : RMSORNDWN
Ensure that rundown wi l l check to see if a rundown
is already active before pro c e eding with the rundown . The
problem was that batch j obs in rundown that were deleted
with a DELETE/QUEUE/ENTRY c ommand would somet imes incur an
executive mode bugcheck because two rundown threads w ere
active at the same t ime .
KPS032
09-Apr- 1986
MODULE : RMSOSETDD
Ensure that SYS$SETDDIR wi l l set and c lear the
RMS active bit around operat ions in its internal pars e
routines that allocate RMS data structures . This prevents
an execut ive mode bugcheck that was possible if SETDD IR

MicroVMS Version 4.5 Update Description

A-21

was active when a call was made to RMS rundown . Thi s most
c ommonly would occur in batch j obs that were deleted by
the j ob c ontrol l er s ending an execut ive mode AST to the
target proc ess .
29-Apr - 1 986
JWT0236
Use diff erent key buffer for scratch area . RMS was
using key buffer 5 and destroying the value there .
29-Apr - 1 986
JWT0237
Fix " $UPDATE Corrupt er . " RMS does a scan to
determine the optimal split point . As is the usual
pract ic e , RMS saves a little bit of state at each
potent ial split point and go es on to evaluat e the
next potent i al split point . Onc e the current spl it
point is evaluated as less optimal than the
previous , things can only go downhill .
So RMS rest ores
the stat e from the previ ously evaluated split point
and spl its there .
RMS was not restoring all of the saved state info
from the previous split point , however . Spe c if ically ,
SAVE_REC_W_LO , a f lag that indicates whether or not
the new record ends up in the new (hi ) or old ( lo)
bucket was not being restored .
This was leaving
strange c onf igurati ons of index records and
continuat ion buckets when lots of dupli cat es were
present .
29-Apr - 1 986
PJH002
Fix deadlock in the RMS last chanc e handler when a proc es s
i s run down a s a result of a STOP/ ID o n the process . The
deadlock is possible only on a process whi ch has a f i l e
using global buff ers opened b y more than one FAB within
the process .
JEJ0294
18-Mar - 1 986
MODULE : RMOSETDID
RMS was inc orrectly handl ing full 16-directory-deep
request s .
This was due t o a directory path c ache that
was one element too short . The directory path cache
pruning code went bers erk when it found this .
Correct
it by allocat ing a larger directory path c ache .
09-May- 1 986
JEJ03 10
MODULE : RMOBUFMGR
Further opt imize the disk buffer c learing logic in
order to speed up $CONNECT .

A-22

MicroVMS Version 4.5 U pdate Description

JEJ03 1 1
1 1 -May - 1 986
MODULE : NTOCREATE
Properly propagate UP! sharing opt ion to RSX-based
remot e partners .
JEJ03 12
12-May - 1 986
MODULE : NTOLNKCSH
Add support for t iming out cached logi c al links .
If the
l ink is not reused within 30 s e c onds of being cached , it
is deac c es sed and deassigned .
EC02 :

1 4 - Jul - 1 986
JEJ0340
MODULE : RM 1GET
Bucket locks may not be returned if a $GET encount ers
end- o f - f i l e at the wrong moment .
JEJ0342
2 1 - Ju l - 1 986
MODULE : RMSOREWIN
$REWI ND incorrect ly dropped shared sequential f il es out
of " c onnected f or append" mode , thus c ausing later
append operations to pot ential ly c orrupt the data f i l e .
JEJ0344
22 -Jul- 1 986
MODULE : RMOCACHE
An $EXTEND operat ion may inc orrectly fail on a shared
s equent ial f i l e if VBN 1 had b e en previously cached with
def erred writ eback enabled .
JEJ0347
29-Jul- 1 986
MODULE : RM1GETINT
Sett ing USZ to zero would fail to r eset the BDB point er
before exit ing with an error .

46) RUNDET (patch image)
RUNDET . EXE
EC0 1

ROP0094
15-May - 1 986
Correct LIB$CVT_DTIME call to c orre ctly deal with delta
t imes great er than 24 hours .

MicroVMS Version 4.5 Update Description

A-23

47) SCNRTL (pat ch image)
SCNRTL . EXE
EC001

MIZ
05-May - 1 986
MODULE : SCN$START
Use proper l ength for string input stream descriptor .

EC002

05-May - 1 986
MIZ
MODULES : SCN$UTIL , SCN$DBGEXT , SCN$ERROR
Return dynamic string , if requested , from
SCN$GET_TOKEN_NAME . Init ialize output descriptor in calls
to SCN$GET_TOKEN_NAME .

EC003

MIZ
05-May- 1986
MODULE : SCN$PRUNE
Fix bug in pruning algorithm f or interior tree nodes .

48) SDA (patch image)
SDA . EXE
EC001

SJF450 1
16-May - 1 986
MODULE : CRASH
Corre ct error message f or new members of 8NN CPU fami ly .

49) SETPO (patch image)
SETPO . EXE
EC001

ACG0516
28 -Mar - 1 986
MODULE : SETPASSWORD
Correct a problem that c ould cause o c c asional ac c ess
violat i on f aults in the proc essing of SET PASSWORD
commands .

EC002

0 1 -Aug- 1986
LMP0366
MODULE : SETPWD
Correct severity of "no privilege" mes sage in
unsuccessful attempts to set the syst em password .

A-24

MicroVMS Version 4.5 Update Description

5 0 ) SETRIGHTS (new image)
SETRIGHTS . EXE
EC001

1 1 - Jun- 1986
Provide the SETRIGHTS image that was missing from the
base MicroVMS syst em . Thi s el iminates the noise
message that appears when the system is boot ed .

5 1 ) SMBSRVSHR (new image)
SMBSRVSHR . EXE
EC00001 RRB0001
07-May - 1 986
Fix problem with f i les left open .
Spe c i f i cally . devic e
c ontrol library modules , main input files . F ixes yet
another instance of unexpect ed symbiont proc ess
t erminat ion .
52) SMGRTL (mi s c e llaneous f ix)
SMGDEF . SDI
1-002

TS
01 -May- 1986
MODULE : $SMGDEF
Provide $SMGDEF as one module inst ead
of two appended modul es .

53) STABACKIT ( edit t ext f i l e )
STABACKIT . COM
EC001

CWH4005
16-Apr- 1986
Make sure that WRITEBOOT is on the syst em bef ore
using it , because MicroVMS has VMB but not WRITEBOOT .

54) STABACKIT2 ( edit t ext f i l e )
STABACKIT . COM
ECOnn

27-Feb - 1 986
J J00022
Provide hooks to build RX50 kits whi ch can be removed
when boot ing standalone BACKUP . Track the SYSBOOT change
whi ch removes the need to us e B/20000 when booting from
TK50s .

MicroVMS Version 4.5 U pdate Description

A-25

55) STABACKUP (patch image)
STABACKUP . EXE
EC0007

KGW00022
30-May- 1986
MODULE : TAPEUTIL
Patch MUST be applied to VMS V4 . 4 systems ONLY .
Exc essive parity errors on a TA78 would result in
ac c ess to the tape being lost .
Repair this by unloading the t ape if the RESTART
opt ion is taken from the error handler .

56) STARLET (mi s c e llaneous f ix)
LIB . MLB
EC001

13-May - 1 986
JLV001
MODULE : $MSGDEF
Add symbols for VAX Workstation VT220 emulator
mai lbox message s .

EC002

MMD
15-May- 1986
MODULE : $DCDEF
Add new device type symbol .

EC003

CBD
19-May- 1986
MODULE : $PRDEF
Add 8550/8700 proc essor symbol s .

57) SUBMIT (patch image)
SUBMIT . EXE
EC001

16-Apr- 1986
JES0001
MODULE : SUBMIT
F ix the /NOKEEP qual if i er .
Change call to parse /KEEP quali f i er from PARSE_IF_TRUE
t o PARSE_IF_TRUE_FALSE so that the pres enc e of a /NOKEEP
qualif ier would get sent to the j ob controller .

A-26

MicroVMS Version 4.5 Update Description

58) SYS (pat ch image)
SYS . EXE
EC097

JAY
02 - Jun- 1986
MODULES : MDAT , SYSPARAM
Increase the size of the nonpaged read-only patch area
by 512 bytes to ac commodate large patches .

EC060

24-Feb- 1986
DWT82638
MODULE : SYSGETLKI
Correct handling of buff er overf low for $GETLKI item
LKI $_LOCKS for a locally mastered lock .

EC063

2 1 - Jan- 1986
DAS/PMV
MODULE : CMODSSDSP
Change RUF servi ce vectors to do CHMEs instead of CHMKs
so that RUF wi l l run in executive mode . Also change the
r egister save mask to also save regi st ers R7 through R11 .

EC064

CJM/TBE
18-Jul- 1986
MODULES : INIT , SYSCOMMON
S et version to X4 . 5 .

EC065

2 1 -Apr- 1 986
L JK4026
MODULE : SYS IMGACT
Use correctly calculated ac c ess mode when de let ing
address spac e mapped as part of a failed act ivation .

EC066

J JW/ JAY
14-May - 1 986
MODULE : !NIT
Che ck for the exist enc e of a subport driver .
If one
exists , create the appropri ate data structures in the
I /O database .
16-May - 1 986
CWH0045
MODULE : SYSGETDVI
Use spare item code to return MSCP unit number .
04-Jun- 1986
CWH0045 . 1
MODULE : SYSGETLKI
F ix synchronization problem in $GETLKI .
04 - Jun - 1 986
WES0045
MODULE : SYSENQDEQ
Clear R9 in DEQALL loop to avo id value block corrupt ion
under obscure c ircumstanc e s .

MicroVMS Version 4.5 Update Description

A-27

EC067

CJM
03-Sep - 1 986
MODULE : INIT , SYSCOMMON
Set version to V4 . 5 .

EC068

05-May - 1 986
LJK4027
MODULES : DISMOUNT , MBDRIVER
The check f or an assoc iated name must be synchronized
with possible parallel explicit deletion of the logic al
name .

EC069

ACG0520
16-May - 1 986
MODULE : SYSCRMPSC
Correct a stack overflow problem in the audit ing of
ac c esses to global sections that can c ause a
" kernel stack not vali d " bugcheck .

EC070

16-May - 1 986
CBD0015
Change NOTRULUCB BUGCHECK to FATMEMERR .

EC07 1

WMC0001
08- Jul - 1986
F ix to ECO 30 to transf er data in correct direction .

EC072

10- Jun- 1986
LJK4029
MODULE : SYSQIOFDT (really it ' s ECO 62)
Allow a byt e c ount of zero to pass l imit checks in
EXE$READCHKR and EXE$WRITECHKR . Only disallow very large
byt e c ounts (with bit 31 set) .
2 1 -Aug - 1 986
LJK4030
MODULE : SYSLNM
Eff ectively eliminate point er from logi c al name block
to UCB or MTL (by changing its index from - 127 t o - 125) .
When coupled with ECO 55 , this compl et ely de couples the
l ogical name structure s from e ither a UCB or a MTL ,
preventing spurious channel as signment s .

EC073

22-Aug- 1986
TCM0001
MODULE : SYSUPDSEC
F ix $UPDSEC to fault in page table pages when updat ing a
global sect ion .
25-Aug- 1986
CWH4004
Increase item JPI$_PROC_INDEX to longword from byte .

A-28

MicroVMS Version 4.5 Update Description

59) SYSBOOT (new image)
SYSBOOT . EXE
EC001

10-Feb- 1986
JJ0002 1
Add hooks that allow the RX50 to be removed when
booting standalone BACKUP . Also remove the need
to use B/20000 f or boot ing TK50 standalone BACKUP .

EC002

12-May- 1986
JAY0001
Add support to proc e ss EXE$GL_AUXDRLIST in
BOOTDRIVR .

EC003

CBD00 12
16-May - 1 986
Add 8550/8700 name support .

60) SYSGEN (new image)
SYSGEN . EXE
EC001

1 6-Apr- 1986
EMB0001
MODULES : AUTOCONFG , LOADER , SHOWADAP
Minor bug f ixes f or VAXBI devi c es .

EC002

14-May- 1986
WCY0052
MODULE : AUTOCONFG
Add devi c e support f or BVPSSP port s in syst ems
als o c ontaining UQSSP ports .

EC003

1 5-May- 1986
EMB02 19
MODULES : AUTOCONFG , CONF IG
Correctly c onfigure LDP devi c es and add a devic e entry
to the UNIBUS devi c e li st .

EC004

WCY0056
16-May- 1986
MODULE : AUTOCONFG
Correct bug introduc ed in WCY005 1 .

MicroVMS Version 4.5 Update Description

A-29

6 1 ) SYSLOA8SS (new image)
SYSLOA8SS . EXE
16-May- 1986
WCY0054
Add suppqrt for BVPSSP ports in CALC_CTRLLTR .
09-May- 1986
EMB0001
Correct ly set up the hardware type in the syst em
block (SB) to di st inguish between an 8200 and an
8300 .
09-Apr-1986
EJL0052
Fix ADPSUB to wait two mi lliseconds after initiat ing
s elf t est on the CIBCI .
62) SYSLOAUV1 (pat ch image)
SYSLOAUVl . EXE
EC001

15-May-1986
ROW0562
MODULE : MOUNTVER
Fix VALIDATE_HOME t o handle c lust erwide inconsist enc i es
creat ed by SET VOLUME/LABEL .
Most of the c ode to handle
thi s problem already exi sts . However . VALIDATE_HOME
renders it use less because it improperly returns an
error status .

63) SYSLOAUV2 (patch image)
SYSLOAUV2 . EXE
EC001

15-May- 1986
ROW0562
MODULE : MOUNTVER
Fix VALIDATE_HOME t o handl e c lust erwide inconsist enc ies
creat ed by SET VOLUME/LABEL . Most of the c ode to handl e
However , VALIDATE_HOME
this problem already exi st s .
renders it us e l ess because it improperly returns an
error status .

EC002

09- Jun-1986
DGB0158
Work around VMB problem , where two bad pages of memory
are report ed on 16MB MicroVAX II systems .

A-30

MicroVMS Version 4.5 Update Description

64) SYSLOAWS1 (patch image)
SYSLOAWS 1 . EXE
EC001

1 5-May-1986
ROW0562
MODULE : MOUNTVER
F ix VALIDATE_HOME to handl e c lusterwide inconsist enc i es
creat ed by SET VOLUME/LABEL . Mo st of the c ode to handle
thi s problem already exi st s . However , VALIDATE_HOME
renders it useless because it improperly r eturns an
error status .

65) SYSLOAWS2 (patch image)
SYSLOAWS2 . EXE
EC001

ROW0562
1 5-May- 1986
MODULE : MOUNTVER
Fix VALIDATE_HOME to handl e c lusterwide inc onsist enc i es
c reat ed by SET VOLUME/LABEL . Most of the c ode to handl e
this problem already exi sts . However , VALIDATE_HOME
renders it useless because it improperly r eturns an
error status .

EC002

1 2 - Jun- 1 986
DGB0 160
Work around VMB problem , where two bad pages of memory
are report ed on 1 6MB MicroVAX I I syst ems .

66) SYSLOAWSD (patch image)
SYSLOAWSD . EXE
EC001

1 5-May- 1986
ROW0562
MODULE : MOUNTVER
Fix VALIDATE_HOME to handle c lusterwide inc onsist enc i es
c reat ed by SET VOLUME/LABEL .
Most of the c ode to handle
However , VALIDATE_HOME
this probl em already exi sts .
renders it useless because it improperly returns an
error status .

EC002

DGB01 6 1
1 2 - Jun- 1986
Work around VMB problem , where two bad pages of memory
are report ed on 1 6MB MicroVAX II systems .

MicroVMS Version 4.5 Update Description

A-31

67) SYSMSG (patch image)
SYSMSG . EXE
EC001

KC0001
1 6-Apr- 1986
MODULE : BASMSG
Pat ch the t ext of various me ssages f or use by
BASIC V3 . 0 and BASRTL .

EC002

16-May - 1 986
KC0002
MODULE : BASMSG
More message text change s .

EC003

KC0003
2 1 -May - 1 986
MODULE : BASMSG
More message text changes .

EC004

1 6 - Jun- 1986
KC0004
MODULE : BASMSG
Change text of FROLINOEG , add ILLCOLMIX .

68) TPU$CCTSHR (new image)
SYS$LIBRARY : TPU$CCTSHR
14 -May- 1986
STL0001
Fix support of t erminal widths .
69) TPUSHR (patch image)
TPUSHR . EXE
EC00 1

BMT0001
02-Apr- 1986
MODULE : TPUSHR . EXE
Change the prot ection mask spe c i f i ed for the mai lboxes
used to communicat e with the TPU subprocesses to allow
only owner access .

EC002

BMT002
10-Apr- 1986
MODULE : TPUSHR . EXE
Add check to GET_INFO bui lt - in to check for suf f i c i ent
paramet ers .

A-32

MicroVMS Version 4.5 Update Description

70) TRACE (new image)
TRACE . EXE
EC001

14-May - 1 986
MODULE : TBKDPC . B32
Thi s module c ontains a f ix for handling BASIC statement
and line numbers c orrectly in trac ebacks .

7 1 ) TTDRIVER (new image)
TTDRIVER . EXE
EC002

MIR07 13
Fix some workstation probl ems with CTRL/Y and CTRL/C
ASTs and subproc esses . Add several port control bits
to disable modem and connect/disconnect for a parti cular
l ine us ing a port c ontrol f i eld .

72 ) TUDRIVER (new image)
TUDRIVER . EXE
EC002

MAS0065
27-May- 1 986
Fix connect ion walking bug that leads to spurious host
clears of HSCs fol lowing virtual c ircuit fai lures during
fai lover . Correct other miscellaneous probl ems involving
host and controller t imeouts . Rel evant modul e audit
versions are TUDRIVER (X-23) and DUTUSUBS (X-30) .

EC001

PRD0227
16-May - 1 986
MODULE : TUDRIVER
Add support for stat i c dualporting .
Rec ognize unit flags upon syst em boot .

MicroVMS Version 4.5 U pdate Description

A-33

73) VAXCRTL (patch image)
VAXCRTL . EXE
EC001

CHH0061
10-Apr- 1 986
MODULE : C$VAXCIO (06 1 )
Miscalculating the end-o f -f i l e byt e offs et and block
number in subroutine WRITE_OUTPUT .

EC002

28-Apr- 1 986
CHH0023
MODULE : SHELL$CLINT (002 ) and C$$MAIN (023)
Int ernal buffer overf low can happen in the SHELL$GET_ARGV
routine when trying to get " argv" and " argc " under
DEC/SHELL .

EC003

CHH0013
0 1 -May - 1 986
MODULE : SHELL$FROM_VMS ( 0 13)
Add che cks in SHELL$TRANSLATE_VMS rout ine and COPY_TOKEN
routine to avoid buffer overf low .

EC004

CHH0018
01 -May- 1 986
MODULE : SHELL$TO_VMS (018)
Modif y SHELL$TO_VMS rout ine to avoid buf f er overf low
and to handle the foreign f i l especs corr ectly .

EC005

13-May- 1 986
CHH0031
MODULE : C$$DOPRINT (03 1 )
Fix f or SPR 87940 . Modify C$$DOSCAN rout ine to match a
character string pattern correctly .

EC006

13-May- 1 986
CHH0062
MODULE : C$VAXCIO (062)
Fix for SPR 87940 . Modify READ_STREAM subroutine to
avo id overwriting an int ernal buff er .

EC007

27-May- 1 986
CHH0063
MODULE : C$VAXCIO (063)
Fix for SPR 88853 . Modify the LSEEK funct i on to return
the correct byte off set after a write operation f or
rec ord f i l e .

EC008

28-May - 1 986
CHH0063
MODULE : C$VAXCIO (063)
Fix in the CHDIR funct ion . SYS$DISK is not a terminal
logi cal name .

A-34

MicroVMS Version 4.5 Update Description

EC009

07-Aug- 1986
CJN0064
MODULE : C$VAXCIO (064)
Fix in WRITE_TRANSFER to check f or zero - l ength transf er
and to do nothing if such i s f ound .

EC0 10

CJN0064
07-Aug- 1986
MODULE : C$VAXC IO (064)
Fix in WRITE funct ion to not f lush buffer if devi ce i s
a SHELL pipe .

EC0 1 1

07-Aug-1986
CJN064
MODULE : C$VAXC IO (064)
Fix in _FLSBUF_STREAM , to remove optimization of no
pre load of next block if read ac c e ss is not permitt ed .

74) VAXCRTLG (patch image)
VAXCRTLG . EXE
EC001

10-Apr - 1 986
CHH0002
MODULE : C$ECVT (002)
Passing 0 to FCVT function fails with ACCVIO .

EC002

10-Apr - 1 986
CHH0061
MODULE : C$VAXCIO (06 1 )
Miscalculating the end-of - f i l e byt e offs et and block
number in subroutine WRITE_OUTPUT .

EC003

28-Apr - 1 986
CHH023
MODULE : SHELL$CLINT (002) and C$$MAIN (023 )
Internal buffer overf low can happen in the SHELL$GET_ARGV
rout ine when trying to get " argv " and " argc " under
DEC/SHELL .

EC004

01 -May- 1986
CHH00 13
MODULE : SHELL$FROM_VMS (013)
Add checks in SHELL$TRANSLATE_VMS rout ine and COPY_TOKEN
rout ine to avoid buffer overf l ow .

EC005

01 -May - 1986
CHH00 18
MODULE : SHELL$TO_VMS (018)
Modify SHELL$TO_VMS routine t o avo id buffer overf low
and to handle the f oreign f i le specs correctly .

EC006

13-May - 1 986
CHH0031
MODULE : C$$DOPRINT (03 1 )
F i x for SPR 87940 . Modify C$$DOSCAN routine to match a
charact er string pattern correctly .

MicroVMS Version 4.5 Update Description

A-35

EC007

CHH0062
13-May - 1 986
MODULE : C$VAXCIO ( 062)
F ix f or SPR 87940 .
Modify READ_STREAM subroutine to
avoid overwriting an internal buff er .

EC008

27-May - 1 986
CHH0063
MODULE : C$VAXCIO ( 063)
Fix f or SPR 88853 .
Modify the LSEEK funct ion to return
the corre ct byte off s et after a write operat ion f or
record f i le .

EC009

CHH0063
28-May - 1 986
MODULE : C$VAXCIO ( 063)
Fix in the CHDIR funct ion . SYS$DISK is not a terminal
logical name .

EC0 1 0

07-Aug-1986
CJN0064
MODULE : C$VAXCIO ( 064)
Fix in WRITE_TRANSFER to check f or zero-length transf er
and to do nothing if such is f ound .

EC0 1 1

07-Aug- 1986
CJN0064
MODULE : C$VAXCIO ( 064)
Fix in WRITE funct ion to not f lush buffer if devi c e i s
a SHELL pipe .

EC01 2

07-Aug-1986
CJN064
MODULE : C$VAXCIO ( 064)
Fix in _FLSBUF_STREAM , to remove optimizat ion of no
preload of next block if read ac cess is not permitted .

75) VMB (new image)
VMB . EXE
EC002

05 -May- 1986
CBD0010
MODULE : VMB
Output a me ssage when great er than 10 perc ent of main
memory t e sts bad .

EC001

EJL0002
23-Apr- 1986
MODULE : PABTDRIVR
Correct errors in new devi c e support .

A-36

MicroVMS Version 4.5 Update Description

76) VMSINSTAL ( edit text f i l e )
VMSINSTAL . COM
EC001

2 1 -Apr- 1986
JES0001
Option C
Fix problem with PROVIDE_F ILE opti on C .
ignored if system disk not ident i c al to target disk .
Fix bug with printing of rel ease not es in callback
RELEASE_NOTES .
Add /PAGE to TYPE command in RELEASE_NOTES callback .
Fix bug in PROVIDE_IMAGE , where we were not checking
status aft er a VMI $FIND call .
Add c ode f or low- end c lust er layered product the abi lity
to install in the spec ific root .

77 ) WELCOME (mi s c e llaneous f ix)
WELCOME . TXT
EC001

CJM
05 -May- 1986
Updat e the MicroVMS version number in
SYS$MANAGER : WELCOME . TXT . Thi s patch only applies to
MicroVMS syst ems .

Appendix

Preparing an RD5 1 -Based Micro VAX I System
for an Update
If you are updating a MicroVAX I with an RDS l disk, you must remove all
Micro VMS operating system options from the disk to make room for the update
procedure. However, because the update procedure requires the "Standalone
BACKUP on System Disk" and "DIFF Utility" suboptions of the UTIL option, you
must install (or retain) these suboptions before proceeding with the update.
To determine whether your MicroVAX I has an RDS l disk, enter the following
command:
$ SHOW DEVICE/FULL SYS$SYSDEVICE

The device type appears on the first line of the display output by the system.
If your MicroVAX I has an RDS l disk, you must remove any Version 4.4 MicroVMS
options that are installed on your system by using the SYS$UPDATE:REMOVE.COM
command procedure.
Perform the following steps:
1.

Log into the system manager's account, SYSTEM, and enter the following
command to invoke the REMOVE.COM command procedure:
$ @SYS$UPDATE : REMOVE . COM

The following display appears on your screen:
Thi s command proc edure r emoves ent ire options or sub -opt i ons of the
MicroVMS kit . Help may be obtained for any of the prompts by
typing HELP .

The command procedure lists the options and suboptions that may be removed
and prompts you for the options that you want to remove.
What layered VMS options ( s ) do you want to remove .
Opt ions must be separat ed by c ommas , e . g . , USER , UTIL , SYSP :

Preparing an RD51 -Based MicroVAX I System for an U pdate

B-2

If the UTIL option is installed on your system, delete most suboptions and retain
those needed for installation (suboptions D and L) by performing these actions:
a.

Respond to the prompt by entering UTIL and pressing RETURN.

Enter N in response to the prompts that ask you if you wish to remove the
entire option.

Respond to the prompt asking for the suboptions that you want removed
from option UTIL as follows: (You will delete all suboptions except
suboptions D and L.)
What sub-options (s) do you want removed for opt ion UTIL .
Sub-options must be separat ed
by commas . e . g . , A , C , F : A , B , C , E , F , G , H , I , J , K , M , N , O

If any of the USER, NET, PROG, and SYSP options are installed on your system,
remove each by reinvoking REMOVE.COM for each option to be deleted. (This
is contrary to the prompt in REMOVE.COM which suggests that you can enter
the name of more than one option to be removed.)
Remove these four options in their entirety by answering Y to the prompt asking
if you wish to remove the entire option.
REMOVE.COM displays informational messages in the following format when it
has successfully removed an option.
* * * * * SYSP removed * * * * *

If the UTIL option is not installed on your system, you must install the Version 4.4
"DIFF utility" and "Standalone BACKUP on system disk support" suboptions of the
UTIL option. You will need the Version 4.4 distribution diskettes to install these
suboptions.
1.

Back up and restore your system disk, following the steps provided in Section
4.4 of Installing or Upgrading MicroVMS From Diskettes, before you install these
suboptions.

Invoke the VMSINSTAL command procedure:
$ @SYS$UPDATE : VMS INSTAL DUAl :

The following will appear on your screen:
VAX/VMS Software Product Instal lat i on Proc edure V4 . 4
It is dd-mmm-yyyy at hh : mm .
Ent er a que st i on mark (?) at any t ime for help .

Next, VMSINSTAL will ask if you are satisfied with the backup of your system
disk:
* Are you satisfied with the backup of your syst em disk [YES] ?

Preparing an RD51 -Based MicroVAX I System for an Update

B-3

Enter NO and press the RETURN key. VMSINSTAL returns to DCL level to
permit you to perform the backup.

Back up and restore your system disk using standalone BACKUP as described
in Section 4.1.1 of Installing or Upgrading MicroVMS From Diskettes.

Restart the update when the backup is completed.

VMSINSTAL will then prompt you to mount on DUA l : the first volume of
the set. Insert the first of the nine diskettes of the Version 4.4 UTIL option in
diskette drive 1 . Enter Y and press RETURN.
The following display will appear:
The following products will be pro c essed :
UTIL V4 . 4
Beginning instal lat ion of UTI L V4 . 4 at hh : mm
%VMSINSTAL- I_RESTORE , Restoring product saveset A . . .

Enter N in response to this prompt:
*Do you want to install the ent ire kit :

Enter N in response to all but these two prompts:

*Do you want to install the DIFF uti lity : Y
*Do you want to install the Stand-alone backup on system disk support : Y

Respond to the prompts of the installation procedure. To install the Version 4.4
"DIFF utility" and "Standalone BACKUP on system disk support" suboptions of
the UTIL option, you need only to load the first five diskettes of the UTIL option.

1 0 . The following display will appear when you have successfully completed the
installation:
Installat i on of UTIL V4 . 4 c ompleted at hh : mm

1 1 . If VMSINSTAL displays the following prompt, type EXIT and press RETURN.
Ent er the products to be pro c essed from the next distribution volume s et .
*Products :

1 2. Proceed with Section 1 .2 of these release notes.

B-4

Preparing an RD51 -Based MicroVAX I System for an Update

After the update has completed, if you wish to install or reinstall a Version 4 .4
MicroVMS operating system option or suboption, refer to the MicroVMS Operating
System, Version 4.5 Software Product Description (SPD 28.05 .08) for the number of
blocks required by each option. See Chapter 5 of Installing or Upgrading MicroVMS
From Diskettes for instructions for installing a MicroVMS option or suboption.

Index
A

Ethernet communications controller (cont'd.)

Access control list, 3-9
AST (asynchronous system trap)
out of band, 3-1 1
AUTOGEN, 1 - 1 5
calculations, 2-3

B
Backup of console disk, 1 -9
Backup of system disk, 1 -4

D
Debugger, 3 - 1 2
window, 3- 1 3
DELUA communications controller
with broadband, 3 - 1 0
DEQNA communications controller
with DECOM transceiver, 3- 1 0
DEUNA communications controller
with broadband, 3 - 1 0
Disk space
freeing, 1 - 1 3
Dynamic image setting, 3- 1 2

E
Error logger
starting on MicroVAX system, 3-3
Ethernet communications controller
expected errors, 3 - 1 0

promiscuous mode restriction on driver
code, 3- 1 0

FORTRAN
IBITS function, 3- 1 1

G
Global pages
required for installation, 1 -6 to 1 - 7
Global sections
required for installation, 1 -6 to 1 - 7

I
IEEE 802 formatted packets, 3- 1 0
Installation, 1 - 1 to 1 - 1 5
completing, 1 - 1 3 t o 1 - 15
from diskette, 1 - 1 0
from RD5 1 disk, B - 1 to B-4
from tape, 1 -1 0
global pages required, 1 -6 t o 1 - 7
global sections required, 1 -6 t o 1 - 7
making space for, 1 -4 t o 1 -5
messages, 1 - 1 1
performing, 1 - 8 to 1 - 1 3
preparing the system for, 1 -4 t o 1 -8
required limits for SYSTEM account, 1 -5
to 1 -6
selecting an update option, 1 -1 0 to 1 - 1 1
specifying a device name, 1 - 1 0

lndex-2

Installing
optional software product, 1 - 1
IO$M_OUTBAND, 3 - 1 1

p
Patch
printing Version 4 .5 listing, 1 - 1 5
Peak disk block utilization, 1-5
Promiscuous mode, 3-10

Journal file, 1 - 1 5

L
LINK/SHARE/DEBUG command, 3 - 1 3
LINK/SHARE/NOTRACE command, 3 - 1 2
Linker
shareable image, 3-12
Logical name table
process-private, 3 - 1 4

M
MicroVAX
system startup, 3-3 to 3-5
MicroVAX I
bootstrapping, 3-5 to 3-8
MicroVMS optional software product, 1 - 1

N
NETACP (network ancillary control
program)
verification of MOP messages, 3-15
Net disk block utilization, 1 -5, 1 - 1 3
Network
shutting down, 1 -7
NMA$CJCLIJMT parameter, 3 - 1 0
NMA$CJCLIJAD parameter, 3 - 1 0
NMA$CJCLIJRM parameter, 3 - 1 0

0
Optional software, 1 - 1

R
RD5 1 disk
installation procedure, B- 1 to B-4
Remote terminal
error count, 3-9

s
SCAN
VARYING STRING input stream, 3 - 1 2
SCNRTL, 3-1 2
SET (WIDTH, . . . ) built-in procedure, 3-2
SET SCREEN command, 3-2
Shareable image
traceback information passed to, 3 - 1 2
SHOW DEVICE command, 3-9
Shutdown command procedure
SHUTDOWN.COM, 2-2
SMG$READ_STRING, 3-1 1
SMG$SETJEYPAD-MODE, 3 - 1 1
STABACKIT.COM command procedure, 2- 1
Standalone BACKUP, 1 -4
alternate system root SYSE, 2-1
booting from alternate root SYSE, 2-2
rebuilding, 1 - 1 4
SYS$CREMBX, 3 - 1 4
SYS$MANAGER:SYSTARTUP.COM, 3-3
SYS$QIO
zero-length transfer, 3-15
SYS$UPDATE:VMS045.TXT, 1 - 1 1 , 1 - 1 5 ,
A- 1 t o A-36
SYSGEN
See System Generation Utility
SYSTEM account
required limits, 1 -5 to 1 -6
System Generation Utility (SYSGEN), 2-3

lndex-3

System shutdown procedure, 2-2

XABPRO block
XAB$L _ACLSTS field, 3-9

Tailored system
update j ournal file, 1 - 1 5
Terminal
error count, 3-9
Traceback
information passed to shareable image,
3-12

u
Update
disk block utilization, 1 -5
media, 1 - 1
options, 1 - 1 0 t o 1 - 1 1
Update description file, 1 - 1 1 , 1 - 15, A - 1 to
A-36
Update kit
contents, 1 - 1 , A-1 to A-36

v
VAX BASIC
SET INITIAL CHOICE statement, 3- 1 3
VAX SCAN
PRUNE statement, 3 - 1 2
SCN$GET_TQKEN_NAME, 3 - 1 2
VAX Text Processing Utility
See VAXTPU
VAXTPU (VAX Text Processing Utility), 3-2
GET_INFO built-in procedure, 3 - 1
VMSINSTAL
alternate mode, 1 -5
automatic purge, 1 - 1 1
selecting an update option, 1 - 1 0 to 1 - 1 1

MicroVMS Release Notes,
Version 4 . 5
AA-JG6 6A-TN

R EADER'S
COMM ENTS

Note: This form is for d ocu ment comme nts only.
DIGITAL will use comments su bmitted o n this form
at the company's d iscretio n . If you requ ire a written
reply and are eligible to receive one u nder Software
Performance Report (SPR) service, submit your
comments on an S PR form .

Did you fi nd this manual understa ndable, usable, and well o rganized? Please make
suggestions fo r im provement.

Did you fi nd errors i n this manual? If so, spec ify the error and the page nu mber.

Please indicate the type of u ser /reader that you most nea rly represent:

D Assembly language programmer
D H ig her-level language prog ra mmer
D Occasional progra mmer (experienced)
D User with l ittle programming experie n ce
D Student programmer
D Other (please specify)
Name ---- Date ---Organ ization

----

Street ---City

----

State ____ Zip Code
or Cou ntry

___

Do Not Tear - Fold Here and Tape -

No Postage
Necessary
if Mailed in the
U n i ted States

B U S I N ESS R E P LY M A I L
F I RST CLASS PE R M IT N0.33 MAYNARD MASS.
POST AGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1 -3/J35
DIGITAL EQUIPMENT CORPORATION
1 1 0 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

111.....11.11....11....1.11.1••1.1• • 1.1••11• • • • •1.11

- D o Not Tear - Fold Here

M icroVMS Release Notes,
Version 4 . 5
AA-JG66A-TN

R EAD ER ' S
COM M E NTS

Note: This form is for document comm ents only.
DIGITAL will use com ments submitted o n this form
at the company's discretio n . If you require a written
reply and are eligible to receive one under Software
Performance Report (SPR) servi ce, submit your
com ments on an SPR form .

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

Did you fi nd errors in this manual? If so, specify the error and the page nu mber.

Please indicate the type of u ser/ reader that you most nea rly represent:

D Assembly language progra m mer
D Higher-level language programmer
D Occasional p rogrammer (experienced)
D U ser with little programming experience
D Student program mer
D Other (please s pecify)
Name

____

Orga nization
Street

Date ___________

----

City ____ State ____ Zip Code ____
or Country

Do Not Tear - Fold Here and Tape -

No Postage
Necessary
if Mailed in the
United States

B U S I N ESS RE PLY M A I L
F I RST CLASS PE R M IT N0.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

SSG PUBLICATIONS ZK1 -3/J35
DIGITAL EQUIPMENT CORPORATION
1 1 0 SPIT BROOK ROAD
NASHUA, NEW HAMPSHIRE 03062-2698

1 1 1 • • • • • 1 1 . 1 1 • • • • 1 1 • • • • 1 . 1 1 . 1 • • 1 . 1 • • 1 . 1 .. 1 1 • • • • • 1 . 1 1

- Do Not Tear - Fold Here