____________________________________________________
VMS Version 5.5-1 Release Notes
June 1992
These release notes describe the VMS Version 5.5-1
operating system.
Revision/Update Information: This is a new manual.
Software Version: VMS Version 5.5-1
Digital Equipment Corporation
Maynard, Massachusetts
________________________________________________________________
June 1992
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.
© Digital Equipment Corporation 1992.
All Rights Reserved.
The postpaid Reader's Comments forms at the end of this
document request your critical evaluation to assist in
preparing future documentation.
The following are trademarks of Digital Equipment
Corporation: ALL-IN-1, CDA, CI, DEC, DECnet, DEC PHIGS,
DECwindows, Digital, HSC, KLESI, LAT, PATHWORKS, RSX,
UNIBUS, VAX, VAXcluster, VAX DOCUMENT, VAX 6000, VAX RMS,
VMS, and the DIGITAL logo.
The following are third-party trademarks:
Apple is a registered trademark of Apple Computers, Inc.
IBM is a registered trademark of International Business
Machines Corporation.
Macintosh is a trademark of Apple Computers, Inc.
Motif is a registered trademark of the Open Software
Foundation, Inc.
Open Software Foundation is a trademark of the Open
Software Foundation, Inc.
PostScript is a registered trademark of Adobe Systems
Incorporated.
ZK6093
This document was prepared using VAX DOCUMENT, Version 2.0.
_________________________________________________________________
Contents
Preface................................................... v
1 VMS Version 5.5-1 Release Notes
1.1 AUTOGEN Displays SYSMAN Error: Parameter Out
of Range-Suggested Workaround................. 1-1
1.2 Batch and Print Queuing System................ 1-2
1.2.1 ALL-IN-1 and Batch and Print Queuing
System-Problems Corrected................. 1-2
1.2.2 Batch and Print New System Messages ...... 1-3
1.2.3 CPU Maximum Limit for Queues-Problem
Corrected................................. 1-5
1.2.4 DEFINE/CHARACTERISTIC Allows Only One Name
to a Number-Suggested Workaround.......... 1-5
1.2.5 DQS (VAX Distributed Queuing Service Print
Symbiont)-Suggested Workaround............ 1-6
1.2.6 Generic Queues with Implicit Target
Lists-Change in Behavior.................. 1-8
1.2.7 Queue Record Corruption and Detection..... 1-9
1.2.8 SYMDEL Queue Manager Message-Problem
Corrected................................. 1-10
1.2.9 SYNCHRONIZE Command-Problem Corrected..... 1-10
1.3 Debugging Programs with LCK$M_DEQALL
Modifier-Suggested Workaround................. 1-11
1.4 DECwindows X11 Server......................... 1-11
1.4.1 Dashed Lines Were Incorrectly
Drawn-Problem Corrected................... 1-11
1.4.2 Horizontal Line Drawing Caused Server
Failure-Problem Corrected................. 1-12
1.4.3 IncludeInferiors Subwindow Mode
Ignored-Problem Corrected................. 1-12
1.4.4 Tiled Operations Drawn in Wrong
Window-Problem Corrected.................. 1-12
iii
1.4.5 xoffset Field Ignored-Problem Corrected... 1-12
1.5 Disk Class Drivers............................ 1-13
1.5.1 DSA Multiple Controllers Timeout
Errors-Problem Corrected.................. 1-13
1.5.2 MSCPCLASS Error-Problem Corrected......... 1-13
1.5.3 Opcode for MSCP Message Improperly
Set-Problem Corrected..................... 1-13
1.5.4 Shutdown Error While Copy Operation in
Progress-Problem Corrected................ 1-13
1.5.5 Volume Shadow Set Members Race
Condition-Problem Corrected............... 1-14
1.6 LATSYM ACCVIO Error During Hangup Event....... 1-14
1.7 Lock Manager.................................. 1-14
1.7.1 Block Transfer to an Unavailable Node
Caused System Failure-Problem Corrected... 1-14
1.7.2 Lock Range Value Corruption-Problem
Corrected................................. 1-14
1.7.3 Remastering Routine Race Condition-Problem
Corrected................................. 1-15
1.7.4 RSPFATAL Status That Was Incorrectly Set
Caused System Failure-Problem Corrected... 1-15
1.8 Mailbox Driver EXE$SNDEVMSG Routine Error..... 1-15
1.9 Mount Utility (MOUNT)......................... 1-16
1.9.1 Bound Volume Set Problem Using Volume
Shadowing Phase I and II-Suggested
Workaround................................ 1-16
1.9.2 MOUNT Commands Hung Other Nodes-Problems
Corrected................................. 1-17
1.9.3 MOUNT Command Caused CPUs to Halt-Problem
Corrected................................. 1-17
1.9.4 Shadow Sets Improperly Allowed-Problem
Corrected................................. 1-17
1.9.5 Shadow Set Failure with Two-Member Volume
Shadow Set-Problem Corrected.............. 1-18
1.9.6 Shadow Set Logical Names Were Improperly
Defined-Problem Corrected................. 1-18
1.9.7 Shadow Set Members Failed-Problem
Corrected................................. 1-18
1.9.8 Tape Compaction Problems for
TA90E/91-Problem Corrected................ 1-18
1.9.9 Tape Density Improperly Set-Problem
Corrected................................. 1-18
1.10 PATHWORKS Support............................. 1-19
iv
1.11 System Management Utility (SYSMAN) Server
Hang.......................................... 1-19
1.12 Verify Utility (VERIFY)....................... 1-19
1.12.1 File Header Identifier Error-Problem
Corrected................................. 1-19
1.12.2 Lost File Header Repair Caused Corruption
of Data-Problem Corrected................. 1-20
1.13 XQP and File System........................... 1-20
1.13.1 Erase-on-Delete Data Blocks Not
Erased-Problem Corrected.................. 1-20
1.13.2 File Truncation-Problem Corrected......... 1-21
1.13.3 Lock-Conversion Condition Caused System
Failure-Problem Corrected................. 1-21
1.13.4 Null-Mode Lock Request Caused System
Failure-Problem Corrected................. 1-21
1.14 Tape Class Driver............................. 1-21
1.15 VAX 6000-600 Warm Start for Systems with
Battery Backup................................ 1-21
1.16 VAX 62xx and 63xx Systems with KLESI or UNIBUS
Adapters...................................... 1-22
1.17 Volume Shadowing Phase II..................... 1-22
1.17.1 Member Addition to Single-Member Shadow
Set Produced Inappropriate Error-Problem
Corrected................................. 1-22
1.17.2 Member Loss While Rebooting
Mixed-Interconnect (MI) Clusters-Problem
Corrected................................. 1-22
1.17.3 Volume Shadowing Phase II INVEXCEPTN
Error-Problem Corrected................... 1-22
1.18 Workstation and Server Failure After Memory
Error......................................... 1-23
2 VMS Version 5.4 to Version 5.5 Queue Database Upgrade
Problem Resolution
2.1 Problem Information........................... 2-1
2.2 Problem Resolution............................ 2-2
v
Index
vi
_________________________________________________________________
Preface
Version 5.5-1 is an update to Version 5.5 of the VMS
operating system. Version 5.5-1 includes corrections to
problems encountered in VMS Version 5.5.
There are two versions of VMS Version 5.5 software:
o V5.5-Runs the single, clusterwide batch and print
queuing system (QUEUE_MANAGER and JOB_CONTROL)
introduced in Version 5.5.
o A5.5-Runs the batch and print queuing system
(JBCSYSQUE.DAT) that was available in previous versions
of the VMS operating system.
To apply the Version 5.5-1 update, you can be running
either VMS Version V5.5 or A5.5 on your system.
Intended Audience
The VMS Version 5.5-1 Release Notes are intended for all
system users. Read the release notes before applying the
Version 5.5-1 update.
Document Structure
This manual contains two chapters as follows:
o Chapter 1 describes the release information, workarounds
to problems, and corrections to the VMS Version 5.5
operating system and DECwindows server software that are
contained in VMS Version 5.5-1.
o Chapter 2 describes a workaround for a problem with
upgrading the queuing system from VMS Version 5.4 or
earlier to the new Version 5.5 design. If your system
is currently running VMS Version V5.5, this information
v
does not apply to you. It applies only during the VMS
Version 5.5 upgrade procedure.
Conventions
The following conventions are used in this manual:
( ) In format descriptions, parentheses
indicate that, if you choose more than
one option, you must enclose the choices
in parentheses.
[ ] In format descriptions, brackets indicate
optional elements. You can choose one,
none, or all of the options. (Brackets
are not optional, however, in the
syntax of a directory name in a VMS file
specification, or in the syntax of a
substring specification in an assignment
statement.)
italic text Italic text emphasizes important
information, indicates variables, and
indicates complete titles of manuals.
Italic text also represents information
that can vary in system messages (for
example, Internal error number), command
lines (for example, /PRODUCER=name), and
command parameters in text.
UPPERCASE TEXT Uppercase text indicates a command, the
name of a routine, the name of a file,
the name of a file protection code, or
the abbreviation for a system privilege.
- A hyphen in code examples indicates that
additional arguments to the request are
provided on the line that follows.
vi
numbers All numbers in text are assumed to
be decimal, unless otherwise noted.
Nondecimal radixes-binary, octal, or
hexadecimal-are explicitly indicated.
vii
1
_________________________________________________________________
VMS Version 5.5-1 Release Notes
This chapter describes the release information, workarounds
to problems, and corrections to the VMS Version 5.5
operating system and DECwindows server software that are
contained in VMS Version 5.5-1. Release notes are arranged
alphabetically.
1.1 AUTOGEN Displays SYSMAN Error: Parameter Out of
Range-Suggested Workaround
If you run AUTOGEN through the SETPARAMS phase, it might
display the following error:
%SMI-E-OUTRANGE, parameter is out of range
%AUTOGEN-I-ERROR, SETPARAMS phase was aborted due to an unexpected error.
This error occurs when one of the parameters is above
the maximum or below the minimum value allowed for that
parameter. When AUTOGEN invokes the System Management
Utility (SYSMAN) to set the parameter value, SYSMAN
corrects the problem. For example, if a parameter is to
be set above its maximum value, SYSMAN sets the parameter
at the maximum value and continues. When SYSMAN completes,
AUTOGEN detects that an error has occurred and displays the
abort message. If you review the parameter values set by
AUTOGEN, you will see that they have been set correctly.
To identify which parameter is causing the problem, create
a command procedure similar to the following one and
include the file SYS$SYSTEM:SETPARAMS.DAT:
1-1
VMS Version 5.5-1 Release Notes
1.1 AUTOGEN Displays SYSMAN Error: Parameter Out of Range-Suggested
Workaround
$!
$ SET VERIFY
$!
$ RUN SYS$SYSTEM:SYSMAN
$!
$! Include the file SYS$SYSTEM:SETPARAMS.DAT here.
$!
$ EXIT
When you execute the command procedure, the parameter names
will be displayed, allowing you to find the out-of-range
parameter.
To fix the cause of the problem, define the maximum or
minimum value for the parameter in the AUTOGEN parameter
file SYS$SYSTEM:MODPARAMS.DAT by using the MAX_ or MIN_
prefix as follows:
MIN_parameter-name = minimum-value
MAX_parameter-name = maximum-value
For example, to specify a maximum value of
400000 for PAGEDYN, add the following line to
SYS$SYSTEM:MODPARAMS.DAT:
MAX_PAGEDYN = 400000
For information about the MAX_ and MIN_ prefixes and
MODPARAMS.DAT, see the Guide to Setting Up a VMS System.
1.2 Batch and Print Queuing System
This section describes release information for the VMS
batch and print queuing system for VMS Version V5.5-1.
1.2.1 ALL-IN-1 and Batch and Print Queuing System-Problems
Corrected
In VMS Version V5.5, there were interaction problems
between the new batch and print queuing system and the
ALL-IN-1 software that caused the OA$FORMATTER queue to
function improperly and occasionally caused the queue
manager process to abort.
This problem has been corrected.
1-2
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
1.2.2 Batch and Print New System Messages
This section alphabetically lists and describes new system
messages for the following facilities:
o JBC, Job Controller
o QMAN, Queue Manager
INVSMBMSG, invalid data in message from symbiont on queue
'queue-name' is being ignored
Facility: QMAN, Queue Manager
Explanation: A minor break of symbiont or queue manager
protocol has occurred. The queue manager has explicitly made
adjustments to compensate for the break. The symbiont will
continue to process work.
This message is intended to alert symbiont writers to
problems in symbiont code. In most cases, users other than
symbiont writers need not be concerned when this message
appears.
User Action: General users should report the occurrence of
this message to the symbiont developer, or ask the system
manager to do so.
Symbiont developers should review the symbiont code and the
SMB and PSM utility routines in the VMS Utility Routines
Manual to determine what activity is causing this message.
Ensure that no improper state changes are being requested,
such as stalling a starting queue or pausing a stopping
queue. Check that all required messages are being provided
and that no unnecessary messages are being issued.
JOBCTLABORT, request failed because job controller aborted
Facility: JBC, Job Controller
Explanation: A system service or DCL command has failed
because the queue manager or job controller process
terminated execution. If the queue manager or job controller
encounters a fatal system error or internal logic error, the
queue manager aborts and is restarted. The command or system
service call that returns this message may or may not have
caused the queue manager to abort.
User Action: Contact your system manager and report this
error along with the command or system service call that
returned the error. Digital recommends that you do not
1-3
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
reissue the command or system service call that returned
this error until the problem is resolved.
The system manager should submit a Software Performance
Report (SPR) and include the following information:
o The dump file SYS$SYSTEM:QMAN$QUEUE_MANAGER.DMP from the
node on which the queue manager was previously running
or the dump file SYS$SYSTEM:JBC$JOB_CONTROL.DMP from the
node on which the job controller failed
o A copy of any messages written to the console or the
operator log file with the QUEUE_MANAGE or JOB_CONTROL
user name
For information on how to submit an SPR, see the chapter on
batch and print operations in the Guide to Maintaining a VMS
System.
QUEDISABLED, disabled queue cannot be modified, nor can a job
be submitted to it
Facility: JBC, Job Controller
Explanation: The queue you are trying to modify or to which
you are trying to submit a job has been disabled. You cannot
modify or submit jobs to a disabled queue.
This message can also indicate a corrupt queue record.
User Action: If you are trying to submit a job, submit it
to another queue and notify the system manager about the
disabled queue.
If you are a system manager, search the operator log file
for the following message:
QMAN-I-QUEDISCOR, queue 'name' has been disabled due to database corruption
This message indicates a corrupt queue record for the named
queue. If you find this message, follow the instructions
provided in the documentation for that message.
1-4
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
QUEDISCOR, queue 'name' has been disabled due to database
corruption
Facility: QMAN, Queue Manager
Explanation: The queue manager has detected corruption in
a queue record of the queue database. The related queue
has been disabled in order to isolate the corruption. This
message is written on the console and in the operator log
file.
User Action: Notify the system manager.
If you are a system manager, submit a Software Performance
Report (SPR) and include copies of the queue file and master
file of the queue database. To copy the files while the
queuing system is running, use the CONVERT/SHARE command.
For complete instructions, see the chapter on managing
queues in the Guide to Maintaining a VMS System.
After you create copies of these files, delete the disabled
queue and create a new queue to replace it. If references
to the corrupt queue exist (for example, the corrupt queue
might be named as the target of a generic queue), be sure to
remove those references before you delete the queue.
1.2.3 CPU Maximum Limit for Queues-Problem Corrected
In VMS Version 5.5, if a queue was assigned a maximum CPU
limit (with INITIALIZE/QUEUE/CPUMAXIMUM=time), that limit
was ignored if either of the following conditions was true:
o No /CPUDEFAULT time was assigned to the queue (with
INITIALIZE/QUEUE/CPUDEFAULT=time).
o The job was submitted with an infinite CPU time
(SUBMIT/CPUTIME=INFINITE).
This problem has been corrected.
1.2.4 DEFINE/CHARACTERISTIC Allows Only One Name to a
Number-Suggested Workaround
In VMS versions prior to Version 5.5, you could define
more than one characteristic name to a number with the
DEFINE/CHARACTERISTIC command. However, this capability
was not supported because the result of defining multiple
characteristic names to a number was unpredictable.
1-5
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
With VMS Version 5.5, you can define only one
characteristic name to a number using the
DEFINE/CHARACTERISTIC command. If your queue configuration
requires you to have more than one characteristic name for
a single number, you can define logical names to achieve
the same result as defining more than one characteristic
name to a number. For example, you can enter the following
commands:
$ DEFINE/CHARACTERISTIC SECOND_FLOOR 2
$ DEFINE/SYSTEM/EXECUTIVE_MODE SALES_FLOOR SECOND_FLOOR
$ DEFINE/SYSTEM/EXECUTIVE_MODE SALES_DEPT SECOND_FLOOR
In this example, the characteristic name SECOND_FLOOR
is assigned to the characteristic number 2. The logical
names SALES_FLOOR and SALES_DEPT are then defined as
equivalent to the characteristic name SECOND_FLOOR. As
a result, the logical names SALES_FLOOR or SALES_DEPT
are equivalent to the characteristic name SECOND_FLOOR
and the characteristic number 2. These logical names can
be specified as the characteristic-name value for any
/CHARACTERISTIC=characteristic-name qualifier.
In a VAXcluster environment, you must define the logical
names on every node that requires them.
For more information about the DEFINE/CHARACTERISTIC
command, see the VMS DCL Dictionary. For information
about using characteristics with queues, see the Guide
to Maintaining a VMS System.
1.2.5 DQS (VAX Distributed Queuing Service Print
Symbiont)-Suggested Workaround
Under certain conditions, a problem exists with the VAX
Distributed Queuing Service (DQS) Version 1.2 and VMS
Versions V5.5 and V5.5-1.
If DQS is installed as a client only, no problem
exists. However, print queues might fail if DQS is
installed as a server and you have initialized any print
queues with the DQS print symbiont as the processor
(INITIALIZE/QUEUE/PROCESSOR=DQS$PRTSMB.EXE).
1-6
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
If the print queues fail, perform the following steps:
1. If the system is hanging because the DQS print symbiont
is looping, manually stop the DQS print symbiont process
that is using the DQS$PRTSMB.EXE image, as follows:
a. Enter the SHOW SYSTEM command to show the DQS print
symbiont process that is looping. The process state
is COM. The process name is SYMBIONT_xxx. Take note
of the process identifier (pid); you will use this
hexadecimal value to stop the symbiont process.
b. Enter the STOP/ID=pid command to stop the DQS print
symbiont process. Stopping the process will clear
the hanging condition. You do not need to reboot your
system.
2. Replace the DQS print symbiont with the standard VMS
print symbiont as follows:
a. Enter the STOP/QUEUE/NEXT command and stop all queues
that use the DQS$PRTSMB image as a processor.
b. Enter the START/QUEUE/PROCESSOR=PRTSMB command
for all queues that use the DQS$PRTSMB image as a
processor. You can find which queues are using the
DQS$PRTSMB image by specifying the SHOW QUEUE/FULL
command. Check the value of the /PROCESSOR qualifier
in the resulting display.
You do not need to reboot your system to reinitialize
your queues.
If you perform these steps, DQS continues to function using
the VMS print symbiont, with the following exceptions:
o Flag, burst, and trailer pages will not display the node
and name of the remote user.
o Flag, burst, and trailer pages will display the local
job number rather than the remote job number.
o The header line and the flag, burst, and trailer pages
will display the time that the local job was entered
rather than the entry time of the remote job.
1-7
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
1.2.6 Generic Queues with Implicit Target Lists-Change in
Behavior
A generic queue has an implicit target list if the queue
is created with the INITIALIZE/QUEUE/GENERIC command and
no queues are listed as values for the /GENERIC qualifier.
(Although you can create a generic queue with an implicit
list, you should normally specify explicit target lists for
generic queues so that you can control where jobs execute.)
In VMS Version 5.4, queues with implicit target lists
considered only similar queues as potential targets. That
is, a generic terminal, server, printer, or batch queue
could feed only a like execution queue.
In VMS Version 5.5, this behavior changed. Now, generic
batch queues can still feed only batch execution queues,
but any other type of generic queue can feed any symbiont
execution queue (terminal, server, or printer).
The original behavior will be restored in a future release.
Until then, this change in behavior might cause a problem
if you use layered products that create server queues or
devices that create terminal queues. To work around the
problem, do one of the following:
o Explicitly specify target queues for your generic
queues. To do so, specify the target queues with the
/GENERIC qualifier for the START/QUEUE or INITIALIZE
/QUEUE command in the following format:
INITIALIZE/QUEUE/GENERIC=(target-queue-name[,...]) queue-name[:]
o Set the NOENABLE_GENERIC flag for those execution queues
that should not receive jobs from the generic queue. To
set this flag, use the /NOENABLE_GENERIC qualifier with
the SET QUEUE, START/QUEUE, or INITIALIZE/QUEUE command
in the following format:
INITIALIZE/QUEUE/NOENABLE_GENERIC queue-name[:]
For more information about the SET QUEUE, START/QUEUE, or
INITIALIZE/QUEUE command and qualifiers, see the VMS DCL
Dictionary.
1-8
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
1.2.7 Queue Record Corruption and Detection
Every time the queue manager process starts up, it verifies
the database to ensure that no corruption exists. If any
corruption exists in a queue record, the queue manager
isolates the record by disabling the queue.
For VMS Version V5.5-1, the cases in which a queue record
could become corrupt have been eliminated. However, should
similar problems occur, new messages have been added
to alert the system manager to the necessary corrective
action. See Section 1.2.2 for information about these new
messages.
The following examples show how the queue record could have
become corrupted:
o When an executor queue being referenced by a generic
queue was deleted, the queue manager failed when it
tried to recover the database. The database must be
deleted and a new one created.
o The queue manager database became corrupted when
starting a batch job with EPID. When the database is
corrupted this way, the queue manager is stopped and any
attempt to start it causes the QUEUE_MANAGER process to
terminate.
The queue manager now detects the corruption and starts up
the database by making the queue unusable. The following
message is recorded in the operator log file when this
condition occurs:
QMAN-I-QUEDISCOR, queue 'queue_name' has been disabled due
to database corruption
Further attempts to access this disabled queue will return
the following informational message:
QUEDISABLED, disabled queue cannot be modified nor can a
job be submitted to it
1-9
VMS Version 5.5-1 Release Notes
1.2 Batch and Print Queuing System
1.2.8 SYMDEL Queue Manager Message-Problem Corrected
In VMS Version 5.5, when you shut down a node, in some
situations where many queues were stopped within a very
short time span, the queue manager displayed (probably more
than once) the following messages:
%QMAN-E-SYMDEL, unexpected symbiont process termination
-SYSTEM-S-NORMAL, normal successful completion
These messages were also accompanied by a message similar
to the following:
%QMAN-I-QUEAUTOOFF, queue TEST_QUEUE is now autostart inactive
This message indicated that the queue was inactive for
autostart if the symbiont had been a processor for an
autostart queue.
In VMS Version 5.5-1, this problem has been corrected.
SYMDEL messages no longer appear when symbiont processes
terminate normally, and autostart queues remain active for
autostart when their symbiont processes terminate normally.
1.2.9 SYNCHRONIZE Command-Problem Corrected
In VMS versions prior to Version 5.5, the SYNCHRONIZE
command did not perform as documented. The VMS DCL
Dictionary describes the behavior as follows:
If you specify the job-name parameter, the default queue
is SYS$BATCH.
However, the command incorrectly found the job with the
specified job name on any batch queue.
With VMS Version 5.5, the SYNCHRONIZE command performs as
documented.
In addition, if the job was submitted to a generic queue
and that queue is specified, the SYNCHRONIZE command now
searches for the specified job in the generic queue and in
its target queues.
1-10
VMS Version 5.5-1 Release Notes
1.3 Debugging Programs with LCK$M_DEQALL Modifier-Suggested Workaround
1.3 Debugging Programs with LCK$M_DEQALL Modifier-Suggested
Workaround
When an application includes the LCK$M_DEQALL modifier
in a $DEQ system service call, the modifier breaks the
communication links between the portion of the debugger in
the user process (the kernel) and in the main process. The
result is that the user's process stays in hibernate (HIB)
state.
To work around this problem, debug the application using
the limited one-process mode rather than the default or
multiprocess mode. To set up one-process mode, issue the
following command:
$ DEFINE DBG$PROCESS NONE
1.4 DECwindows X11 Server
_______________ Note to DEC PHIGS Users _______________
If you install DEC PHIGS Version 2.3A after installing
VMS Version 5.5-1, you will overwrite some of the
files. Because DEC PHIGS Version 2.3A contains
some DECwindows X11 server files, you will have to
reinstall VMS Version 5.5-1 to recover the DECwindows
X11 server corrections.
______________________________________________________
This section describes problems that were fixed in the
DECwindows X11 server for the base system graphics on the
VAXstation 4000 Model 60 and Model VLC computers. These
problems did not affect any other workstations.
1.4.1 Dashed Lines Were Incorrectly Drawn-Problem Corrected
In the VMS Version 5.5 X11 server for VS4000 base system
graphics, there was a problem with wide on and off dashed
lines and segments that were drawn using the following
logical functions:
GXandReverse
GXxor
GXnor
GXequiv
GXinvert
1-11
VMS Version 5.5-1 Release Notes
1.4 DECwindows X11 Server
GXorReverse
GXnand
The visual effect was that the lines were drawn randomly.
There may also have been math errors reported in the server
error log file. The errors in the logical functions have
been corrected.
1.4.2 Horizontal Line Drawing Caused Server Failure-Problem
Corrected
Drawing many horizontal thin solid lines or segments caused
the server to fail with an ACCVIO error. The problem
was caused by a miscalculation in the code when handling
horizontal lines. The calculation has been corrected.
1.4.3 IncludeInferiors Subwindow Mode Ignored-Problem Corrected
The value of IncludeInferiors subwindows mode was ignored
for certain graphics context (GC)/drawable combinations.
The visual effect was that drawing operations that were
expected to be drawn over the top of one or more subwindows
were instead drawn under those subwindows.
This problem has been corrected.
1.4.4 Tiled Operations Drawn in Wrong Window-Problem Corrected
In the VMS Version 5.5 X11 server for VS4000 base system
graphics, a problem in certain tiled operations caused
objects to be drawn into the wrong window. The visual
effect was that an object to be drawn in one window was
instead drawn into a window that was on top of the intended
window.
This problem has been corrected.
1.4.5 xoffset Field Ignored-Problem Corrected
The xoffset field in an image was ignored by XPutImage.
Certain applications that used the xoffset field exhibited
an image that appeared to be shifted to the right of where
it would normally be located. The xoffset field is no
longer ignored.
1-12
VMS Version 5.5-1 Release Notes
1.5 Disk Class Drivers
1.5 Disk Class Drivers
This section describes the corrections to DUDRIVER and
DSDRIVER.
1.5.1 DSA Multiple Controllers Timeout Errors-Problem Corrected
Configurations that have multiple Digital Storage
Architecture (DSA) controllers that are idle for extended
periods of time can log false host access timeout errors.
When multiple DSA controllers are configured on one bus,
more time is needed to poll inactive controllers to prevent
false access timeout errors from occurring. More time has
been added to allow for these configurations.
1.5.2 MSCPCLASS Error-Problem Corrected
A device configured with a path to both a served controller
and a hierarchical storage controller (HSC) could have,
upon failover (from the served controller to the HSC port),
occasionally caused an improper MSCPCLASS bugcheck to
occur. An additional check has been made to prevent this
situation.
1.5.3 Opcode for MSCP Message Improperly Set-Problem Corrected
Under certain error recovery conditions, the opcode for a
mass storage control protocol (MSCP) message would not be
set properly and would cause unpredictable results. The
opcode field is now set properly.
1.5.4 Shutdown Error While Copy Operation in Progress-Problem
Corrected
During system shutdown, if a phase I shadow set member
volume control block (VCB) was deallocated while a copy
operation was in progress, the driver might have attempted
to access fields in the now deallocated structure. Doing so
could have resulted in a system failure with an INVEXCEPTN
error. An additional check has been added to prevent the
system failure while a shutdown is pending.
1-13
VMS Version 5.5-1 Release Notes
1.5 Disk Class Drivers
1.5.5 Volume Shadow Set Members Race Condition-Problem Corrected
While a phase I volume shadow set member was experiencing
a high rate of recoverable errors, a race condition could
occur between an operator-requested DISMOUNT command and
the spontaneous removal of the member by the class driver.
Further checks have been added to prevent this condition.
1.6 LATSYM ACCVIO Error During Hangup Event
LATSYM could have failed with an ACCVIO error when a LAT
device it was controlling received a hangup event. This may
have occurred if the symbiont process was driving multiple
queues. LATSYM no longer causes an ACCVIO error because it
now correctly sets the queue status bits during a hangup
event.
1.7 Lock Manager
This section describes the corrections to the VMS
distributed lock manager.
1.7.1 Block Transfer to an Unavailable Node Caused System
Failure-Problem Corrected
A block transfer to a node whose VMS$VAXcluster connection
breaks caused a CNXMGRERR bugcheck at CLUSTRLOA+3766. If
the connection between two nodes was disrupted in the
middle of a cluster server process (CSP) block transfer,
and the block transfer completed while the connection was
broken, the last message sent had a response identifier
(RSPID) value of zero. The zero RSPID resulted in a system
failure. The loss of the connection now causes the block
transfer to be redone.
1.7.2 Lock Range Value Corruption-Problem Corrected
Noncontiguous fields caused a lock range value corruption
that caused a LOCKMGRERR bugcheck at CLUSTRLOA+8DF8. This
problem has been corrected.
1-14
VMS Version 5.5-1 Release Notes
1.7 Lock Manager
1.7.3 Remastering Routine Race Condition-Problem Corrected
A race condition occurring in the remastering routine
caused a LOCKMGRERR bugcheck at CLUSTRLOA+5F24.
If a new master failed during a remaster operation, and
a rebuild message was sent before the new master received
a shutdown message, the system would fail. The rebuild
messages no longer cause a system failure.
1.7.4 RSPFATAL Status That Was Incorrectly Set Caused System
Failure-Problem Corrected
A new status called RSPFATAL was introduced in VMS Version
V5.5. The status is sent to a remote node that has sent
invalid data. The result is a system crash on both of the
nodes involved in a locking operation.
The status field was not being filled in. When the field
was checked later, if the old data in the status byte
happened to equal the value of RSPFATAL, the system failed.
The status field is now set to have the correct status.
1.8 Mailbox Driver EXE$SNDEVMSG Routine Error
________________________ Note ________________________
This problem is mentioned in the Cover Letter
Supplement for VMS Version 5.5 (part number
AV-PMX6A-TE) under the heading "Mailbox Driver Problem
and ACMS."
______________________________________________________
If you had ACMS installed on your system running VMS
Version 5.5, you were unable to log into ACMS through
controlled terminals except for LAT-dedicated service
ports. On other controlled terminals, after you started the
ACMS terminal subsystem, you would have seen the "Connected
to ACMS" and "Press <RET> to continue . . . " messages, but
you would not get any response from ACMS due to the problem
with the mailbox driver.
An error in the mailbox driver's EXE$SNDEVMSG routine
caused the driver to write a string count one byte longer
than the actual string. If the application expected a $QIO
read request to return data sent by EXE$SNDEVMSG, and the
1-15
VMS Version 5.5-1 Release Notes
1.8 Mailbox Driver EXE$SNDEVMSG Routine Error
application does one or more of the following, the extra
byte caused a problem:
o Created the mailbox with MAXMSG set to the exact size of
the string that it expected EXE$SNDEVMSG to write.
o Used the length returned by the $QIO read request to,
for example, compare strings or simply to verify that
the length was an expected value.
VMS Version 5.5-1 enables you to log into ACMS through all
controlled terminals.
1.9 Mount Utility (MOUNT)
This section describes corrections and one suggested
workaround for the VMS Mount Utility.
1.9.1 Bound Volume Set Problem Using Volume Shadowing Phase I and
II-Suggested Workaround
A mount request for a shadowed bound volume set may result
in a fatal error if more than 5 units are specified. For
example:
$ MOUNT/SYSTEM/BIND=PROD_B -
DSA4100:/SHADOW=($1$DUA12),DSA4101:/SHADOW=($1$DUA14), -
DSA4102:/SHADOW=($1$DUA16),DSA4103:/SHADOW=($1$DUA13), -
DSA4104:/SHADOW=($1$DUA20),DSA4105:/SHADOW=($1$DUA28) -
BR0,BR1,BR2,BR3,BR4,BR5
%MOUNT-F-MAXDEV, too many devices
When a multiple-member virtual unit configuration is
required, a workaround can be implemented. For example,
to initially create the bound volume set, enter a command
similar to the following:
$ MOUNT/BIND=DATADISK DSA1001:/SHADOW=$1$DUA1: DATA1
This device becomes the root volume of the volume set.
Additional members of the volume set may then be created
and mounted as follows:
$ MOUNT/BIND=DATADISK DSA1002:/SHADOW=$1$DUA2: DATA2
$ MOUNT/BIND=DATADISK DSA1003:/SHADOW=$1$DUA3: DATA3
$ MOUNT/BIND=DATADISK DSA1004:/SHADOW=$1$DUA4: DATA4
1-16
VMS Version 5.5-1 Release Notes
1.9 Mount Utility (MOUNT)
1.9.2 MOUNT Commands Hung Other Nodes-Problems Corrected
If you used the following command, MOUNT incorrectly
computed the number of devices being mounted and then
compared it against the number of labels specified:
$ MOUNT/SYSTEM DSA1313:/SHADOW=$254$DUA92: label
When the number of devices did not match the number of
labels specified, MOUNT issued an error that resulted in a
device lock being left in protected write (PW) mode. As a
result, the next MOUNT/CLUSTER command for the same shadow
set would hang the cluster server process (CSP) waiting for
the device lock to be dequeued.
Also, when you used a MOUNT command and, as in the
following example, specified only one of the shadow
set members, MOUNT tried to add the second member
automatically.
$ MOUNT/CLUSTER DSA1313:/SHADOW=$254$DUA92: label
Because of a software error, the lock to the device being
automatically included was left in PW mode. As a result,
the next MOUNT/CLUSTER command for the same shadow set
would hang the CSP waiting for the device lock to be
dequeued.
This problem has been corrected.
1.9.3 MOUNT Command Caused CPUs to Halt-Problem Corrected
When mounting a multimember phase II volume shadow set in
a CI- or NI-based cluster, all CPUs in the cluster were
halted except for the CPU that issued the command. In VMS
Version 5.5-1, CPUs are not halted.
1.9.4 Shadow Sets Improperly Allowed-Problem Corrected
Physical units in phase II volume shadow sets could be made
members of two different shadow sets. Physical units can
now be part of only one shadow set.
1-17
VMS Version 5.5-1 Release Notes
1.9 Mount Utility (MOUNT)
1.9.5 Shadow Set Failure with Two-Member Volume Shadow
Set-Problem Corrected
Mounting a two-member phase II volume shadow set by
specifying only one of the disks failed if you specified
the second member first. For example, if a shadow set
consisted of DEV1 and DEV2, then the following command
failed to mount the shadow set:
$ MOUNT/SYSTEM DSA1/SHAD=DEV2 LABEL
%MOUNT-F-DEVCOUNT, number of devices must match number of volumes
This problem has been corrected.
1.9.6 Shadow Set Logical Names Were Improperly Defined-Problem
Corrected
Logical names were not defined correctly for shadow sets.
The logical names DISK$label and LOGICAL_NAME (if given
on the command line) both pointed to the last physical
device in the shadow set. The logical names are now defined
correctly.
1.9.7 Shadow Set Members Failed-Problem Corrected
Binding shadow sets into a volume set did not work
correctly when members were automatically included.
This problem has been corrected.
1.9.8 Tape Compaction Problems for TA90E/91-Problem Corrected
The Mount Utility changed the expected data compaction
behavior of TA90E/91 tape devices so that the compaction
operation would not be enabled properly. The Mount Utility
has been fixed to properly enable the tape drive data
compaction operation.
1.9.9 Tape Density Improperly Set-Problem Corrected
The MOUNT/FOREIGN command would incorrectly set the
magnetic tape density to the low density. Magnetic tape
density for multiple density drives is now set properly.
1-18
VMS Version 5.5-1 Release Notes
1.10 PATHWORKS Support
1.10 PATHWORKS Support
VMS Version 5.5-1 provides "Blank Page" support for the
PATHWORKS software to better support printing on Apple
Macintosh and IBM personal computers. Prior to VMS Version
V5.5-1, PATHWORKS had to supply a replacement symbiont
library (SMBSRVSHR).
1.11 System Management Utility (SYSMAN) Server Hang
The System Management Utility (SYSMAN) could hang in
some instances, particularly when certain operations were
interrupted with Ctrl/C or Ctrl/Y. A SYSMAN hang can cause
the CLUSTER_SERVER process to stop running which can cause
a system bottleneck. The SYSMAN logic has been updated to
improve the interaction between the SMISERVER process and
the CLUSTER_SERVER process, which eliminates a possible
system bottleneck.
1.12 Verify Utility (VERIFY)
This section describes the corrections to the Verify
Utility.
1.12.1 File Header Identifier Error-Problem Corrected
The Verify Utility mishandled file headers for files whose
file identifier (FID) is a multiple of 64K. For example:
$ ANALYZE/DISK/REPAIR dka300:
%ANALDISK-W-BADHEADER, file (65536,0,1) .;0
invalid file header
-ANALDISK-I-BAD_STRUC_LEVEL, STRUCLEV field is bad
-ANALDISK-I-INVHEADER_BUSY, invalid file header marked "busy"
in index file bitmap
Certain FIDs, which are multiples of 65536 (that is, 64K;
FIDs whose low-order 16 bits are all 0), are considered
reserved and are never used. These files are reserved to
maintain compatibility with the RSX operating systems.
VERIFY did not recognize these files as reserved.
When VERIFY passed over the INDEXF.SYS file, it did not
treat these file headers as a special case and incorrectly
marked them as invalid file headers. In doing so, VERIFY
generated error messages that caused users to question
the integrity of their data. If VERIFY was then invoked
1-19
VMS Version 5.5-1 Release Notes
1.12 Verify Utility (VERIFY)
to repair the disk, it would also deallocate these
reserved FIDs in the index file bitmap, allowing them to
be allocated.
This problem has been corrected.
1.12.2 Lost File Header Repair Caused Corruption of Data-Problem
Corrected
A file system error was introduced in VMS Version 5.4
that sometimes caused the creation of lost extension file
headers when a multiheader file was extended. After running
ANALYZE/DISK_STRUCTURE/REPAIR on a disk with these lost
file headers, VERIFY would leave many multiply allocated
blocks on the disk.
The error was caused by VERIFY correctly finding lost
extension headers and then putting them into the "lost"
directory. But while doing this, VERIFY also attempted to
update some dates in the ident area of these headers: the
creation date, last modified date, and so on.
The ident area of a file header is a variable-length field
and is shorter than normal in extension file headers. When
VERIFY updated the date fields, it did so without checking
the length of the ident area. The result was that VERIFY
overwrote the map area of the file header. VERIFY now
checks the length of the ident area, and the map area is
no longer overwritten.
1.13 XQP and File System
This section describes the corrections to erase-on-delete,
file truncation, and locking.
1.13.1 Erase-on-Delete Data Blocks Not Erased-Problem Corrected
If a file marked for erase-on-delete was moved by
IO$_MOVEFILE, then the old data blocks were not erased,
even if the volume was marked for erase-on-delete. The old
data blocks are now erased.
1-20
VMS Version 5.5-1 Release Notes
1.13 XQP and File System
1.13.2 File Truncation-Problem Corrected
Incorrect file truncation was caused by invalid lock value
block data. Two lock routines used data from a lock value
block without first checking to see whether the lock value
block was valid. The result was an inappropriate truncation
of the file in question. The data check has been corrected.
1.13.3 Lock-Conversion Condition Caused System Failure-Problem
Corrected
A rare lock-conversion condition in the XQP caused a system
failure. If a lock conversion was granted between the time
the request was queued and a dequeuing was requested, the
returned status from the dequeuing request caused an error.
This problem has been corrected.
1.13.4 Null-Mode Lock Request Caused System Failure-Problem
Corrected
A null-mode lock request in the XQP caused a system
failure. If a null-mode lock request was not immediately
granted, an error status was returned to the requesting
routine, which then issued an error that caused a system
failure. Null-mode lock requests are now properly granted.
1.14 Tape Class Driver
A problem that randomly occurred while mounting tapes
controlled by TUDRIVER has been fixed. The problem would
result in a system failure during the mount operation.
1.15 VAX 6000-600 Warm Start for Systems with Battery Backup
If your VAX 6000-600 system contains a battery backup
unit and recovered successfully from a power failure,
the system halted at the next occurrence of any system
error, even if the error was potentially recoverable. This
halt prevented nonrecoverable hardware-related errors from
causing bugcheck crashes.
This problem has been corrected.
1-21
VMS Version 5.5-1 Release Notes
1.16 VAX 62xx and 63xx Systems with KLESI or UNIBUS Adapters
1.16 VAX 62xx and 63xx Systems with KLESI or UNIBUS Adapters
In VMS Version 5.5, the primary CPU backup cache on VAX
62xx and 63xx systems with KLESI or UNIBUS adapters was
disabled. Having this cache disabled resulted in a 50%
reduction in performance. The cache is now enabled.
1.17 Volume Shadowing Phase II
This section describes problems that were fixed for
volume shadowing (SHDRIVER and SHADOW_SERVER). Additional
volume shadowing fixes are described in Section 1.5 and
Section 1.9.
1.17.1 Member Addition to Single-Member Shadow Set Produced
Inappropriate Error-Problem Corrected
A SSRVEXCEPT error occurred within an error recovery thread
when a new member was added to an existing single-member
volume shadowing phase II set.
This problem has been corrected.
1.17.2 Member Loss While Rebooting Mixed-Interconnect (MI)
Clusters-Problem Corrected
The sporadic loss of one member of a multiple-member shadow
set while rebooting a mixed-interconnect (MI) cluster has
been corrected.
While multiple nodes of an MI cluster would leave or enter
the cluster, one or more members of a multiple-member
shadow set could occasionally be removed from the set.
This behavior would occur at random on any mounted shadow
set, including the system disk.
1.17.3 Volume Shadowing Phase II INVEXCEPTN Error-Problem
Corrected
Under certain circumstances, while adding a member to an
existing virtual unit, an INVEXCEPTN error could occur. If
this condition occurs now, a SHADDETINCON error is issued
instead of the INVEXCEPTN error.
Once a virtual unit had been mounted in a cluster, any
node that had the virtual unit mounted was eligible to add
new members to the set. If a new unit was added that was
unknown to another node (that is, there was no unit control
1-22
VMS Version 5.5-1 Release Notes
1.17 Volume Shadowing Phase II
block [UCB] in its I/O database), that cluster member would
fail with the INVEXCEPTN error.
1.18 Workstation and Server Failure After Memory Error
A problem has been fixed on servers for VAXstation 3100
Model 80 and VAXstation 4000 Model 60 workstations that
would cause a system failure every 11 minutes after
memory errors until the system (or power) was turned
off. The failures would be a machine check caused by an
unrecoverable memory error.
1-23
2
_________________________________________________________________
VMS Version 5.4 to Version 5.5 Queue Database Upgrade Problem
Resolution
This chapter describes a workaround for a problem with
upgrading the queuing system from VMS Version 5.4 or
earlier to the new Version 5.5 design. If your system is
currently running VMS Version V5.5, this information does
not apply to you. This problem will not be an issue in
future releases of VMS.
2.1 Problem Information
During phase 6 of the VMS Version 5.5 upgrade, users are
not able to convert to the new queue manager because the
queue conversion fails no matter how the following question
is answered:
"Do you wish to upgrade to the new JOB_CONTROL at this time [NO]?"
If you answer NO, you will not upgrade to the new job
controller. If you answer YES, the job controller starts,
but conversion of the queues fails with the following
messages:
Starting the new job controller...
Starting the new queue manager...
%JBC-E-QMANDEL, unexpected queue manager process termination
-SYSTEM-F-PROTINSTALL, protected images must be installed
%JBC-E-QMANDEL, unexpected queue manager process termination
-SYSTEM-F-PROTINSTALL, protected images must be installed
%JBC-E-QMANNOTSTARTED, queue manager could not be started
The queue conversion fails because the IPC$SHARE image is
not installed.
2-1
VMS Version 5.4 to Version 5.5 Queue Database Upgrade Problem Resolution
2.2 Problem Resolution
2.2 Problem Resolution
To work around this problem, perform the following steps:
1. Before upgrading to VMS Version 5.5, issue the following
command to display all queues and jobs in the system:
$ SHOW QUEUE/ALL/FULL/OUTPUT=QUEUES.TXT
If some of the queues have been corrupted, you can
notify users if their jobs are not transferred during
the upgrade. Likewise, the following commands may also
be useful:
$ SHOW QUEUE/FORM/FULL/OUTPUT=QFORMS.TXT
$ SHOW QUEUE/CHARACTERISTIC/FULL/OUTPUT=QCHAR.TXT
Corruption issues are resolved in the new queuing
system. Therefore, queuing system database corruption
will not be an issue in future releases of VMS.
2. During phase 6 of the VMS Version 5.5 upgrade, answer NO
to the following question:
"Do you wish to upgrade to the new JOB_CONTROL at this time [NO]?" NO
3. Let the upgrade run to completion. AUTOGEN will run and
the system will reboot. Once the system is rebooted, the
IPC$SHARE image is installed.
4. Log in to the system account.
5. Make sure the disks are mounted. Disks holding queue
database files and disks holding users' files must be
available to start the new queue manager and to restore
batch and print jobs that were previously submitted.
6. Disable the job controller's "cold start" verification
of its database as follows:
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN> SET JOBCTLD 1
SYSGEN> WRITE ACTIVE
SYSGEN> EXIT
2-2
VMS Version 5.4 to Version 5.5 Queue Database Upgrade Problem Resolution
2.2 Problem Resolution
Setting this undocumented system parameter allows the
data in the former queue database (JBCSYSQUE.DAT) to be
saved for transfer to the VMS Version 5.5 queue database
(even if corruption exists in the former database). You
can use the System Generation Utility (SYSGEN) to change
this parameter, because it is an isolated and temporary
change.
7. Redefine any queues, forms, and characteristics that may
not be transferred due to corruption. See Step 1.
If there is minor corruption in the JBCSYSQUE.DAT
file, the uncorrupted data will be transferred to
the new database. If there is major corruption in the
JBCSYSQUE.DAT file, the transfer of data to the new
database might fail.
8. Execute the command procedure
SYS$UPDATE:VMS$UPGRADE_A55_V55.COM. Answer YES to the
following question:
"Do you wish to convert queues now ? (YES,NO,ABORT)" YES
Answering YES upgrades your system to VMS Version 5.5[1]
with the new job controller and queue manager. It also
transfers information from the former queue database
(JBCSYSQUE.DAT) to the new queue database. When you
enter the START/QUEUE/MANAGER command, the new queue
manager is started.
Answering NO upgrades your system to VMS Version 5.5
with the new job controller and queue manager, but
it does not transfer information from the former
queue database (JBCSYSQUE.DAT) to the new queue
database. When you start the new queue manager with the
START/QUEUE/MANAGER command, the new queue database will
be empty (that is, it will not contain any information
about queues or jobs).
____________________
[1] VMS Version V5.5 and V5.5-1 use the new queue manager
(process name QUEUE_MANAGER) and job controller
(process name JOB_CONTROL); VMS Version A5.5 and
A5.5-1 use the previous queue manager, which is a
function of the previous job controller (process name
JOB_CONTROL).
2-3
VMS Version 5.4 to Version 5.5 Queue Database Upgrade Problem Resolution
2.2 Problem Resolution
Answering ABORT leaves your system as VMS Version A5.5.
Your system continues to run the former job controller
and queue manager and uses the former queue database
(JBCSYSQUE.DAT).
_______________________ Caution _______________________
The new queue manager is in a stopped state upon
completion of the upgrade. After answering YES to
the queue conversion question, do not include the /NEW
qualifier on the START/QUEUE/MANAGER command; this
qualifier effectively erases the queuing database. For
information about the queuing system, see the Guide to
Maintaining a VMS System.
______________________________________________________
2-4
_________________________________________________________________
Index
A______________________________ C______________________________
ACCVIO error, 1-12, 1-14 Cache, 1-22
ACMS, 1-15 Characteristic names, 1-5
ALL-IN-1 CNXMGRERR bugcheck, 1-14
and batch and print queuing Controlled terminals, 1-15
system, 1-2 Converting queues, 2-3
AUTOGEN, 1-1 Corrupted queue database, 2-2
CPU maximum limit
B______________________________ for queues, 1-5
Batch and print queuing system Ctrl/C and Ctrl/Y interrupts,
, 1-2 1-19
and ALL-IN-1, 1-2
CPU maximum limit, 1-5 D______________________________
DEFINE/CHARACTERISTIC command Dashed lines incorrectly drawn
, 1-5 in DECwindows, 1-11
DQS print symbiont, 1-6 DEC PHIGS, 1-11
new system messages, 1-3 DECwindows X11 server, 1-11
SYMDEL message, 1-10 dashed lines incorrectly
SYNCHRONIZE command, 1-10 drawn, 1-11
Batch job DEC PHIGS, 1-11
SYNCHRONIZE command, 1-10 horizontal lines problem,
Blank page support, 1-19 1-12
Block transfer to a down node, IncludeInferiors subwindow
1-14 mode, 1-12
tiled operations, 1-12
xoffset field, 1-12
Index-1
DEFINE/CHARACTERISTIC command,
1-5 I______________________________
Defining multiple Implicit target lists for
characteristic names, 1-5 generic queues, 1-8
Digital Storage Architecture IncludeInferiors subwindow
See DSA mode, 1-12
Disk class driver, 1-13 INVEXCEPTN, 1-13
DSA, 1-13 INVEXCEPTN error, 1-22
DQS print symbiont, 1-6 IPC$SHARE image, 2-1
DSA (Digital Storage
Architecture), 1-13 J______________________________
controllers, 1-13 JBCSYSQUE.DAT, 2-3
E Job controller
_______________________________ new system messages, 1-3
Erase-on-delete, 1-20 JOB_CONTROL, 2-1
_______________________________ K______________________________
FID (file identifier), 1-19 KLESI adapter, 1-22
File identifier
See FID L______________________________
Files LATSYM
truncating, 1-21 ACCVIO error, 1-14
File system and XQP, 1-20 Lock conversion condition in
lock conversion condition, file system and XQP, 1-21
1-21 Lock manager, 1-14
null-mode lock request, 1-21 LOCKMGRERR bugcheck, 1-15
lock range value corruption,
H______________________________ 1-14
Hierarchical storage SMISERVER process, 1-14
controller SYSMAN, 1-14
See HSC Lost file header repair, 1-20
Horizontal lines problem in
DECwindows, 1-12
HSC (hierarchical storage
controller), 1-13
Index-2
M______________________________ P______________________________
Mailbox driver, 1-15 PATHWORKS, 1-19
Mass storage control protocol Print
See MSCP queuing system, 1-2
Memory error, 1-23 symbiont for DQS, 1-6
MI (mixed-interconnect)
clusters, 1-22 Q______________________________
MOUNT/FOREIGN command, 1-18 Queue
Mount Utility, 1-16 conversion, 2-3
bound volume set, 1-16 CPU maximum limit, 1-5
CPU halt caused, 1-17 database corrupted, 2-2
hung other nodes, 1-17 implicit target lists, 1-8
logical names improperly record corruption and
defined, 1-18 detection, 1-9
multimember volume shadow SYNCHRONIZE command, 1-10
set, 1-17 Queue manager, 1-10, 2-1
shadow set failure, 1-18 new system messages, 1-3
shadow sets improperly SYMDEL message, 1-10
allowed, 1-17 workaround for, 2-1
tape compaction problem, 1-18
tape density, 1-18 R______________________________
two-member volume shadow set, Race condition, 1-14, 1-15
1-18 Remastering routine race
MSCP (mass storage control condition, 1-15
protocol) message, 1-13 RSPFATAL status error, 1-15
MSCPCLASS error, 1-13
Multiple characteristic names, S
1-5 _______________________________
Shadow set, 1-18
N adding member to single-
_______________________________ member, 1-22
Noncontiguous fields failure of two-member, 1-18
and lock range value improperly allowed by MOUNT,
corruption, 1-14 1-17
Null-mode lock request, 1-21 member loss during reboot,
1-22
MOUNT, 1-18
Index-3
Shadow set (cont'd)
phase II INVEXCEPTN error, U______________________________
1-22 UCB (unit control block), 1-22
phase I race condition, 1-14 UNIBUS adapter, 1-22
problem with bound volume Unit control block
set, 1-16 See UCB
SHADOW_SERVER image, 1-22
SHDRIVER image, 1-22 V
SSRVEXCEPT error, 1-22 _______________________________
SMISERVER process, 1-14 VAX
Symbiont for DQS, 1-6 6000-600 and 6000-500
SYMDEL message, 1-10 warm start, 1-21
SYNCHRONIZE command, 1-10 6200/6300 performance, 1-22
System Management Utility, VAXstation
1-1, 1-14, 1-19 3100
System messages Model 80, 1-23
new for batch and print 4000
queuing system, 1-3 Model 60, 1-11, 1-23
Model VLC, 1-11
T VCB (volume control block),
_______________________________ 1-13
TA90E/91 tape drives, 1-18 Verify Utility, 1-19
Tape file headers, 1-19
class driver, 1-21 lost file header repair, 1-20
compaction problem with MOUNT VMS Version 5.5-1
, 1-18 components, 1-1
density improperly set with Volume control block
MOUNT/FOREIGN, 1-18 See VCB
Terminals Volume shadow set
controlled, 1-15
Tiled operations for See Shadow set
DECwindows X11, 1-12
Timeout errors for DSA W______________________________
multiple controllers, 1-13 Warm start, 1-21
Workaround for queue manager,
2-1
Workstation failure, 1-23
Index-4
XQP
X______________________________ and file system, 1-20
X11 server for DECwindows, erase-on-delete, 1-20
1-11 lock conversion condition,
xoffset field, 1-12 1-21
XPutImage, 1-12 null-mode lock request, 1-21
truncating files, 1-21
Index-5