Digital PDFs

AD-L034A-32

July 1986

122 pages

Original

8.7MB

view download

OCR Version

9.1MB

view download

Document:	VAX/VMS Systems Dispatch
Order Number:	AD-L034A-32
Revision:	000
Pages:	122
Original Filename:	ad-l034a-32.pdf

OCR Text

VAX/VMS

Systems Dispatch
July 1986

A e

AD-L034A-32

soffLAIe
dlilgliltlall

VAX/VMS SYSTEMS DISPATCH

Published by
Corporate Administrative Services Group, Software Services
Digital Equipment Corporation

129 Parker Street (PKO2/E49)

Maynard, MA 01754
The VAX/VMS Systems Dispatch contains new and revised Software Product Descriptions, programming notes, software problems statements and responses. Much of the material is developed
from Software Performance Report (SPR) answers significant to the general audience and is
printed here to supplement the maintenance updates.

DECnet-VAX
DECtype/VMS

VAX CORAL-66
VAX DATATRIEVE

VAX SPM
VAX TDMS

VAX ReGIS Graphics Library

VAX DBMS

VAX 2780/3780 Protocol

RTEM-11

VAX DECalc

VAX Ada

VAX DECOR

VAX ADE

VAX DIBOL

VAX BASIC

VAX DSM

Emulator
VAX 3271 Protocol
Emulator
FORTRAN IV/VAX to RSX

VAX BLISS

VAX

VAX C

VAX FORTRAN

(Cross Compiler)

VAX CDD

VAX MUX200

VAX COBOL

VAX PASCAL

VAX SORT/MERGE

VAX

PDP DATATRIEVE/
VAX

VAX PL/I

DISTRIBUTION

The VAX/VMS Systems Dispatch is directed to one software contact for each software product. No
mailing will be made to addresses without a software contact name. Address change requests
should be sent to the nearest DIGITAL field office. Include the new address and mailing label from
the most recently received publication.

Software binary and sources are provided under licenses only. The standard Terms and Con-

ditions, OEM Agreement, and/or Quantity Discount Agreement contain the licenses for all binaries
other than DECsystem-10.

Barbara Scollan, Associate Editor
Copyright
© Digital Equipment Corporation 1986. All Rights Reserved.
The material is this document is for information purposes only. Digital

believes the information in this publication is accurate as of its publication
responsible for any inadvertent errors. Comments on the contents of this
publication should be directed to your local Digital Field Office
TRADEMARKS of DIGITAL EQUIPMENT CORPORATION
Maynard, Massachusetts

DEC
DECUS

DECnet

DECsystem-10
DECSYSTEM-20

DECwriter

DIBOL
EDUsystem
1AS

RSX
RT
ULTRIX

PDP
PDT

VAX
VMS

MASSBUS
RSTS

UNIBUS
vT

date; such information is subject to change without notice. Digital is not

VAX/VMS

Systems

Dispatch,

July

1986

TABLE OF CONTENTS

HELPFUL HINTS

FOR WRITING SPRs

Component/

Product

Seq. No.
NEWS

RUN-TIME

LIBRARY

BULLETIN

DOCUMENTATION CORRECTION

1.1,7

KNOWN PROBLEMS AND RESPONSES

sys
PRIVILEGED

5.20.18

GETLKI MISHANDLED USER BUFFER OVERFLOW

IMAGE ACCESS TO MESSAGE

5.20.19

SWAPPER TRIMS

5.20,20

WORKING SETS

FILES

UNNECESSARILY

LOGINOUT
FILTER

LINE

FEEDS

OUT

LOW BYTE LIMIT CRASHES

PASSWORD

SYSTEM

11.15.4

11,15.5

11.30.2

15,15.5

SYSBOOT

SYSBOOT MIGHT MISTAKENLY LOWER

PQLDWSQUOTA

JOBCTL.
SHOW ACCOUNTING REPORTS

ENABLED WHEN

DISABLED

PRTSMB
VIRTUAL MEMORY USED BY

15.30.17

15.30,18

20.5.9

TOPS-20 TERMINAL PAUSE CHARACTER NOT REASSIGNABLE

25.65.2

TERMINAL CHARACTERISTICS

25.65.3

REMOTE SET TERMINAL/PERMANENT MIGHT FAIL

25.65.4

TOPS-10 TO

25.65.5

31.55.2

33.5.3

33,20,11

EXTRA FORM

FEEDS

SYMBIONT

INCREASES

PRINTER SETUP

DL
NOECHO DATA IN

RECALL LIST

RTPAD

VMS

NOT RESTORED

PROTOCOL ERROR

TMDRIVER
END-OF-FILE

NOT

RECOGNIZED ON

TE16

CTDRIVER
OUT-OF-BAND CHARACTER NOT CHECKED

TTDRIVER
SECONDARY TRANSMITTED SIGNAL

NOT SET ON

DMF-32

VAX/VMS

Systems

Dispatch,

July

1986

TABLE OF CONTENTS

(Continued)

Component/
Product

Seq,

No,

Page

LCDRIVER
LCDRIVER CAUSING SYSTEM CRASHES

34.16.2

34.20,2

40.45,19

40.45,20

40,45,21

45.1.3

55.5.3

LPDRIVER
UPPERCASE CHARACTER SUPPORT

RMS

LONG UICs

TRUNCATED OVER NETWORK ACCESS

RMS

RECORD LOCK CONVERSION

RMS

FAILS WITH RMS$ ENQ/SS$ CVTUNGRANT

PROBLEMS

RTL

EMBEDDED BLANKS NOT PERMITTED IN UICs

ANALYZE

RECOVERED FILES HAVE
ERRORS

INCORRECT BACKLINKS

DURING BOOTSTRAP LOG

INCORRECT DATE/TIME

55.5.4

55.5.5

55.5.6

55.50.9

56.30.11

56.30,12

564809

56.80.10

56.85,7

VALID VALUES FOR SET TERMINAL/WIDTH

65,5,41

RUNNING REMOTE

65.5,42

DOCUMENTATION ERROR FOR QUEUE IDLE BIT IN GETQUI

65.5,43

SET PROTECTION CANNOT MODIFY A REMOTE FILE

65,5.44

ANALYZING ERRORS FOR RA81

DISK

/INCLUDE & /EXCLUDE KEYWORD VALUES MISINTERPRETED

DEBUG
DEBUGGER RESERVED OPERAND FAULT WHILE USING PL/I

MAIL
MAIL ATTACH/PARENT COMMAND FAILS
REMOTE

FORWARDING CAN CAUSE

MAIL TO

HANG

SET
SET HOST/DTE/LOG IS

INACCURATE

SET TERMINAL/INQUIRE RESETS MULTINATIONAL

SHOW QUEUE
DESCRIPTION TRUNCATED IN

SHOW QUEUE/FORM/FULL

DOCUMENTATION

IMAGES REQUIRES

READ ACCESS

VAX/VMS Systems Dispatch, July 1986

TABLE OF CONTENTS

(Continued)

Component/

Product

CUMULATIVE

INDEX

COMPONENTS

LIST

SOPTWARE

PROBLEMS OR ENHANCEMENTS

DIGITAL SOPTWARE

111

LICENSING

DIGITAL EQUIPMENT COMPUTER

113

USERS

SOCIETY

(DECUS)

115

HELPFUL HINTS

FOR WRITING
SPRs

VAX/VMS Systems Dispatch

1 of 13

HINTS FOR WRITING SPRS

1Introduction

1.0

Software Performance Reports (SPRs) exist to
DIGITAL.

They

benefit

provide informaton to customers and

customers

well

feedback to DIGITAL about

software problems.
The following descriptions provide guidelines

for

DIGITAL so that SPR problems can be solved.

Some information is common to all

SPRs;

submitting

information

other information is requested for only certain types of problems.

2.0 SPR Priority Levels
The following explanations of

SPR priorities should be used as a guideline for

determining
the
priority
of
an
SPR.
Please
note
that
the
priority
determination should be based on the system
or
facility behavior
that
has
actually
beea
experienced
at
the
site
and
should
not
be
based on the
perception of the impact of a potential problem.

Priority

Explanation

MOST
PRODUCTION
WORK
CANNOT
BE
RUN e.g.,
important
production
software
is
unusable, the system will not boot, necessary peripherals
cannot be used as intended, no workaround exists.

SOME
PRODUCTION WORK CANNOT
BE RUN e.g., certain functions or
jobs
are
not
usable,
level
of
performance
1is
not
as expected or some
documented feature does not work as expected but there is a workaround.

ALL

PRODUCTION

significant

WORK

manual

CAN

BE RUN

WITH

SOME

intervention is required,

IMPACT

USER

e.g.,

performance has degraded

but work can still be done.

ALL
PRODUCTION WORK
CAN
BE RUN WITH NO SIGNIFICANT IMPACT
ON
USER
e.g., problem can be patched easily, simple bypass procedure exists.

SYSTEM

MODIFICATIONS

NEEDED

suggestion,

consultation,

documentation error or inquiry.

TO RETURN TO NORMAL PRODUCTION e.g.,

3.0 General Guidelines
This

section covers

Depending

upon

the

the information that

problem,

this

snould be

information

provided

will

vary

content.

Remember that the more pertinent information that is

easier it

for DIGITAL to resolve the problem.

with

all

SPRs.

in quantity and
included,

the

VAX/VMS Systems Dispatch

2 of

3.1 Scenario
A complete scenario

should

supplied,

usually in

the

form

batch

1log

console listing or SET HOST/LOG output file that shows exactly how the problem
is produced.

The

Supplying only the output

entire

produced by

scenario of what was done by the user

be caused by an interaction between various

devices,

SYSGEN parameters,

displays generated by the

DCL symbols

the

problem is

is needed.

system events,

or logical

following commands may

software

names.

not

enough.

The problem may
packages,

Some or all of the

required

for

different

problems:

$ SHOW LOGICAL/ALL/FULL

$ SHOW SYMBOL/ALL/GLOBAL
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN>

USE ACTIVE

SYSGEN>

SHOW/ALL

SYSGEN>

SHOW/SPECTAL

SYSGEN>

EXIT

3.2 Limit Problem Scope

As much as possible,
example,

the

eliminate all extraneous elements from the scenario.

execution of

a very large program causes

the program to include only the code that
program

that demonstrates

the problem.

causes
This

a problem,

the preblem or write a

action has

small

two benefits:

logic errors may be discivered;
second,
the
maintainer
problem does not have to comprehend unnecessary material.

looking

For

shorten
first,

into

the

This

may

3.3 Machine-readable Files
If possible,

supply any software needed

include source programs,

names etc.

image

files,

to reproduce the

sample

data,

If source programs are submitted,

require

files

referenced.

These

files must

format.

Console medium or ANSI magtape are

also include
be

problem.

command procedures,

any

logical

libraries

provided in machine-readable

the best media to include with the

SPR.
If

the

problem involves a system crash,

The data should be written to an ODS-2
example,

the

following

commands

include the
format

will

system dump.

disk or

copy the

magtape:

$ INIT MTAO:

DUMPS

$ MOUNT/FOREIGN MTAO:
$ BACKUP/IGNORE=NOBACKUP SYS$SYSTEM:SYSDUMP.DMP —
$ MTAO:DUMPS/SAVE

S DISMOUNT MTAO:

ANSI

magtape.

system dump file

For

to an ANSI

VAX/VMS Systems Dispatch

3 of 13

NOTE

Since

the system dump file is

frequently marked

NOBACKUP (telling the BACKUP utility to copy the
file attributes but not its contents), the
dump
file be must copied with:

BACKUP/ IGNORE=NOBACKUP
This will insure
copied,
as well

that
the
file
contents
as
the file attributes.

are
The

commands used to write the media should also

provided with the SPR.

On a MicroVAX, where there is no console block storage device, use one of

floppy
the SPR.

diskette

the

drives to create machine-readable medium to be included with

The following commands can be used to copy files:
$ INIT
$FLOPPYl: SPRDATA
$ MOUNT
$FLOPPYl: SPRDATA

$ CREATE/DIRECTORY $FLOPPY!:[DUMP]
$ BACKUP MYDATA.DAT,MYIMAGE.EXE $FLOPPYI:[DUMP]SPRDATA/SAVE
$ DISMOUNT

$FLOPPYL:

On a full VAX, where there is a console block storage

device,

the

scratch

volume

following

commands can be used to copy machine-readable data:
$ RUN SYS$SYSTEM:SYSGEN
SYSGEN>

CONNECT CONSOLE

SYSGEN>

EXIT

(At this time, remove the console medium and place a

the

console block storage device.)
$ INIT CSAl:

$ MOUNT CSAl:

SPRDATA

$ CREATE/DIRECTORY CSAL:[DUMP]
$ BACKUP MYDATA.DAT,MYIMAGE.EXE CSAl:[DUMP]SPRDATA/SAVE
$ DISMOUNT CSAl:

It is important to use BACKUP to
write
the media
submitted with an
SPR.
Transferring files in a save set produced by BACKUP is much more reliable than
copying files

to the media.

When machine-readable data is not provided in BACKUP save-set format,
include
the exact commands that were used to write the data and the commands used for
reading it.

Other

formats are discouraged, since they may cause problems.

VAX/VMS Systems Dispatch

4 of 13

All machine-readable media

submitted

with

SPRs

will

returned

the

customer.

3.4 System Environment
Every computer site runs a different
appear

under

classes of
problems

certain

users

type of

conditions.

different

base

workload.

example,

priorities.

that other sites do not.

in resolving the problem,

For
This

especially

Some

problem

with

should

accessing

local

These

for system hangs

If any patches other

than

included.

symbols

numbers of DEBUG and all relevant
those

only

sites

may

encounter

information can be extremely important
or

system crashes.

Describe any special software packages that are being used.
foreign hardware devices or user-written drivers.
Software version numbers

problems

some sites give different

For

during

Also,

example,

there

a DEBUG session,

compilers/assemblers

mention any

the version

should be specified.

from maintenance updates

are being used,

they

should be mentioned in the SPR.

3.5 User Analysis
Optionally,
miscellaneous

(Optional)
analysis

information

the

problem

should be

may

included,

the problem could not be reproduced" or

such as,

included.

"On version Vx.y,

not occur."

Any

useful

"Without xyz happening,

this

problem

does

4.0 Problem-specific Information to
Resolution of

different

of additional

information.

classes

Include
problems

generally requires

different kinds

NOTE
For those

items

that

are

identified

with

single
asterisk
(%),
the
raw data
file
(SYS$ERRLOG : ERRLOG. SYS) ,
not
the
formatted
output from the ANALYZE/ERROR utility, should be
included.
include

Formatted output
all

the

frequently does

not

information needed to resolve

the problem.

For those
items
that
are
double
asterisk
(*%),

(SYS$SYSTEM: SYSDUMP.DMP),

identified
with
a
the
raw data
file

not

output from the SDA utility,
Formatted output usually does
the

information needed

the

formatted

should be included.
not

include

all

to resolve the problem.

VAX/VMS Systems Dispatch

5 of

Problem

Information to

Include

System Bugcheck/Crash

A machine-readable copy of

the system

dump file must be included.** (Output
from the SDA utility should not be
sent since it usually does not include
enough information to resolve

the

problem).
A copy of

the error log at

the time

of the error should also be included
because many system problems are

triggered by hardware errors.*
Machine-check:

On a machine check,

include a machine-

readable copy of the error log, not
output from the error log generator.*

A machine-readable copy of the system
dump file should also be included. **
System Hang:

When a system appears "hung" (no
response on any terminals),

the

system should be manually crashed

and the system dump file included
with the SPR.
When the system is
way,

shut

down in this

the console listing is very

important and should be

included

with the SPR.

On VAX-11/730, VAX-11/780, VAX-11/782,
VAX-11/785, and VAX 8600 primary console
terminals,

enter:

(do nothing on the

attached processor”s console)
SP,
HALT

@CRASH

VAX/VMS Systems Dispatch

6 of 13

On VAX-11/750 console terminal,

>
OopDEmEEE®RE
L]
LX)
]

enter:

F FFFFFFFF
1F0000

On MicroVAX I:

Push the HALT button on the front
panel of

the CPU box

twice,

so that

the button is latched out (the red
light

the

center of

the button

the

console terminal,

is out).
Then,

enter:

EP
E/I
/10
E +

E +
E +

E +
D/G
/G

F FFFFFFFF

1F0000

c (Then wait
Note:

a minute or so)

If a CRT is being used,

the displayed values
commands to paper and

copy

from the examine
submit

them with

the SPR.

On MicroVAX II:
Enable

the HALT button via

back panel

the

switch

the CPU box.

Push the HALT button on the front
of the CPU box twice,
button is latched out

panel

so that the
(the red light

the center of the button is out).

VAX/VMS Systems Dispatch

7 of 13

Then,

on the console terminal,

enter:

A
+H

PSL

EEEE
UMM
D

PC FFFFFFFF
1F0000

C (Then wait a minute or so)
Note:

If a CRT is being used,

the displayed values

copy

from the examine

commands to paper and submit them with
the SPR.

The preceding command sequences cause
the VAX or MicroVAX system to bugcheck in a
manner

that

recognized by VMS developers

as a forced crash.
Also

include

a description

the

currently

running workload.

VAXclusters:
If

all machines

in a VAXcluster are

"hung" for a reason other than an
explainable

lack of quorum,

coordinated

set

console
may be

of dumps

listings
required

coordinated

plus

from all machines
for diagnosis.

set

dumps

from every machine in

a dump

the cluster

taken in a way that ensures

that

the lock and other data structures
are consistent
To

between all dumps.

take a coordinated

halt

dump,

first

every VAX in the cluster. The

last machine must

be halted no more

than 99 seconds after
machine is halted.
machines

the first

After all

have been halted,

crash

each machine as directed under
SYSTEM HANG, and provide all of
dumps

and all of

with your SPR.

the

the console logs

VAX/VMS Systems Dispatch

Executive:

8 of

If it appears that

there is a problem

with the executive code,
active values of

the

include the

system parameters.

These can be obtained by invoking

SYSGEN and entering both the

SHOW/ALL and SHOW/SPECIAL commands.
A machine-readable copy of the
source program showing the problem
plus libraries,
build

require files,

files should

also

and

included,

if possible.

Also include a copy of the machinereadable error log at the time of
the problem.
Devices:

For any suspected device or device
driver error,
error

log at

problem.

Corrupted RMS Files:

include a copy of
the

time of

the

When an RMS file

by software,

becomes corrupted

an SPR should always

be submitted.

Items

include

with the SPR are:

1) A copy of the corrupted file.
2) Any programs

(preferably with

sources) and data that are necessary
to reproduce

the corruption.

Note

the distinction between programs that
merely demonstrate
corrupt,

causes

as opposed

that
to

the corruption

the file is
a

program

to occur.

that

Please

try to trim down the program to isolate
the specific

operations

that

led to the

corruption.

3) A description of how the file is
being processed when the corruption
occurs.

For example,

how many users

are accessing the file,
operations

what kind of

are being performed on

file ($UPDATEs,

the

$PUTs, $DELETEs, etc.).

Sometimes accessing a corrupted file
can cause nonfatal

bugchecks.

If it

VAX/VMS Systems Dispatch

9 of 13

appears that a process

is continually

disappearing from the system,

check

the error log for nonfatal bugchecks.
If

this

is the case,

dump with the SPR.

include a crash

To obtain a crash

dump (assuming the system manager has
given permission),
procedure below.

perform the
Since

will crash the system,

this procedure
it is suggested

that it be performed during off-peak

hours.

Be sure to give adequate

warning if

there are any users on the

system.

$ RUN SYS$SYSTEM: SYSGEN
SYSGEN>

USE ACTIVE

SYSGEN>

SET BUGCHECKFATAL

SYSGEN>

WRITE ACTIVE

SYSGEN>

EXIT

$ RUN PROGRAM
THAT BUGCHECKS

Intermittent:

For a problem that is intermittent
or

that

is not reproducible,

include

a copy of the machine-readable error
log at

the time of

the problem.

Command Language
Interpreters:

When submitting an SPR on

language interpreter,
to show all
defined on

symbols
the

a command

it is

important

and logical names

system by using

the

following commands:

SHOW SYMBOL/ALL/GLOBAL
SHOW SYMBOL/ALL/LOCAL
SHOW LOGICAL/ALL/FULL
Also,

indicate whether private or

modified command tables are being used.
Job Controller:

the job controller process

encounters
it aborts

itself

a fatal error condition,
execution and restarts

(as a new process).

restart,

Upon

the system job queue

file

is not reopened automatically;

a START/QUEUE/MANAGER command and

VAX/VMS Systems Dispatch

10 of

appropriate START/QUEUE commands
must be manually issued to restart
batch and print

processing for that

node.

For this

type of controller problem,

include a copy of

the console

log

error message and a machine-readable
copy of the job controller process
dump written by the system to
SYS$SYSTEM: JOBCTL.DMP.

In addition,

if the START/QUEUE/MANAGER command
fails because of a corrupted system job
queue file,

also

include a machine-

readable copy of

the queue file.

The default queue

file name is

SYS$SYSTEM: JBCSYSQUE. DAT.

Print Symbiont:
Print symbiont process dump:
If the print symbiont exits,
from the job controller is
on the console,

a message

printed

together with an error

message from the print

symbiont.

Also,

a symbiont process dump is written

to SYS$SYSTEM:PRTSMB.DMP.

Include a

copy of these console log messages and
a machine-readable

copy of

the symbiont

Also include copies of

process dump.

the displays:

SHOW QUEUE/FULL/ALL
SHOW PRINTER (for all
printer execution queues)

SHOW QUEUE/FORM/FULL
SHOW TERMINAL (all terminal
execution queues)
If a file was

involved,

include a

DIRECTORY/FULL of the file and, if
possible,
file.

a machine-readable copy of the

If at all

possible,

attempt

explain the conditions which directly
preceded the symbiont exit,

such as

commands used or attempted, and/or a
detailed description of
behavior

prior

the symbiont

to exiting.

Unexpected format or output generated with print
symbiont:

VAX/VMS Systems Dispatch

11 of 13

If the print symbiont problem exists in
the formatting or output of data, include
a machine-readable

copy of

the

file

and

the lihrary modules in use when printing.

Include a DIRECTORY/FULL display of the
file and a copy of
the

following

the displays using

commands:

SHOW QUEUE/FULL/ALL
SHOW QUEUE/FORM/FULL
SHOW PRINTER and/or SHOW TERMINAL
(whichever is applicable)
Along with a description of
PRINT

command,

the explicit

include qualifiers and a

copy of the

FILE TRAILER page.

provide all

information required

duce

Please
to repro—

the behavior consistently.

User-written and user-modified

symbiont

problems:

Describe the problem as completely as
possible,

including the intent of the user

symbiont.

Supply all

details surrounding

the problem and include

a well-commented

listing of the user-supplied symbiont or
routine.

the

problem is

the specification of
characteristics,
to

associated with

the queue,

parameters,

the DCL command line,

form,

or other input

include

a log

file

or a description of the PRINT command which
demonstrates
LIBRARIAN:

If there

the problem.
a problem with the

LIBRARIAN,

include the following material:
1.

A machine-readable

copy of

the

library

itself
2.

Machine-readable copies
files

the

of all input

library

Information (DIRECTORY/FULL)

on the

library file

Information (LIBRARY/LIST/FULL) on the
library contents

the problem can be duplicated at will,

include

the scenario and any command files

used.

VAX/VMS Systems Dispatch

LINKER:

12 of 13

If there is a

problem with the LINKER,

include machine-readable copies of
object

files,

shareable images,

libraries used in the link,

the

and

along with a

full map (LINK/MAP/FULL).

Debugger:

Include sources, objects, and images for the
program being debugged.
large,

the program is

it would be very helpful

the size of

same problem.

Also

DECnet:

that

reduce

include a log of

debugging session and include
file

the program to demonstrate
the

the

DEBUG.LOG

the debugger produces.

For a DECnet

problem,

supply configurations

of the systems involved in the problem.
This information should include the version
numbers of the operating systems and DECnet,
the hardware on both systems,

and the patch

level of the DECnet software on the non-VMS
system, if applicable.
Depending on the
nature of the problem, it might also be
applicable

to supply hard-copy display of

executor,

line or circuit parameters and/or

counters.

Terminals:

If there is a problem with the terminal
driver,
1.

provide the following information:

A list

terminal

characteristics

(SHOW TERMINAL)
2. The type of terminal

3. The type of modem (if any)
4. Any special front-end equipment
5. Any unusual
If the

terminal configuration

problem involves

is often useful

know if

the

same or

remote

file access,

for the maintainer to
similar operation can

be performed from a different account,
with the source

and destination nodes

reversed.

Compiler/Assembler:

If there is a problem with the assembler
or a compiler,

include the source program

that caused the problem.
important

(It is very

include all require files

and libraries

that are referenced by the

source program).

VAX/VMS Systems Dispatch

13 of 13

is especially important to limit

scope of the problem when submitting
on

the

SPRs

compilers.

Include

the version number of

and the version number of
system.

the compiler

the operating

NEWS BULLETIN

VAX/VMS

Systems

Dispatch,

July 1986
Seq.

The

VAX/VMS

error

Run-Time

Library

Version

4.4

the

documentation

instructions

Library Routines Reference
The

update

0ld

Page

0ld

page

for

through

it with

the

package

the

contains

VAX/VMS

Run-Time

Manual.

includes

the

RTL-663/664

following

line:

Page

RTL-645/646

through RTL-663/664

following:

Page

New Page

RTL-645/646

RTL-645/646
through RTL-663/664

RTL-659/660

through

RTL-663/664

RTL-659/660

Correction

update

updating

New

RTL-645/646

Replace

notice

Documentation

1.1.7

The consequence of having followed the instructions is that you
might have deleted pages RTL-647
through RTL-658, which remain
unchanged
in Version 4.4.
Since these 12 pages have not been
modified since Version 4.2, they were not included in the Version
4.4 update package.
We are republishing these pages; if you have
deleted them from your manual, remove the following 12 pages from

the

VAX/VMS

Systems

Dispatch

and

Library Manual.

insert

them

into

your

Run-Time

Run-Time Library Routines
SMGSINSERT_LINE

EXAMPLE
o+

C This FORTRAN example program demonstrates the use

of SMGS$INSERT_LINE.

C Include the SNG definitions. In particular, we want SMGSN_BORDER,
C SHGSN_UNDERLINE, and SMGSM_UP.
c-

INCLUDE * ($8MGDEF)
INTEGER SMGSCREATE_VIRTUAL_DISPLAY, SMGSCREATE_PASTEBOARD
INTEGER SMGSPASTE_VIRTUAL_DISPLAY,

SNGSPUT_CHARS,

SMGSERASE_DISPLAY.
INTEGER DISPLAY1, PASTE1, ROWS, COLUMNS

C Use SMGSCREATE_VIRTUAL_DISPLAY to create a virtual display
C with a border.
c-

BOWS = 7
COLUMNS = 50
ISTATUS = SMGSCREATE_VIRTUAL_DISPLAY

(ROWS, COLUMNS, DISPLAY1, SNGSM_BORDER)
IF (.NOT. ISTATUS) WRITE (6, 900) 'SNGSCREATE_VIRTUAL_DISPLAY',

ISTATUS

C Call SHGICREATE_PASTEBUARD to create the pasteboard.
c-

ISTATUS = SMGSCREATE_PASTEBOARD (PASTEL)
IF (.NOT.

ISTATUS) WRITE (6, 900)

'SMGSCREATE_PASTEBOARD',

ISTATUS

SNGSPUT_CHARS to put data in the virtual display.

DISTATUS = SMG$PUT_CHARS ( DISPLAY1,
'

This virtual display has 7 rows and 50 coluans

ISTATUS = SNGSPUT_CHARS ( DISPLAY1,

' This is a bordered virtual display.'. 4, 1)

1
1

ISTATUS = SNGSPUT_CHARS ( DISPLAY1,
* SHGSPUT_CHARS puts data in this virtual display.', 6,
)

C Paste the virtual display by calling SHGSPASTE_VIRTUAL DISPLAY.
c-

ISTATUS = SMGSPASTE_VIRTUAL_DISPLAY ( DISPLAY1, PASTEL, 4, 16)
900

FORMAT (' Routine ', A,

' returned a

status of ', Z8)

C Call SMGSINSERT_LINE to add a line of text after line 6 and scroll
C the display. Also,

underline the new

characters.

Bar

ISTATUS = SMGSINSERT_LINE ( DISPLAY1, 7,
'This is a new line.', SMGSM_UP, SMGSN_UNDERLINE)
END

The initial output generated by this FORTRAN program is shown in
Figure RTL-25.

RTL-647
21

Run-Time Library Routines
SMGSINSERT_LINE

Figure RTL-25

Output Generated Before the Call to

SMGSINSERT_LINE

nd 50 columns

N
xanszes

The output generated after the call to SMG$INSERT_LINE is shown in
Figure RTL-26.

Figure RTL-26

Output Generated After the Call to

SMGSINSERT_LINE

sal disp

puts data in this

virlual

display.

RTL-648
22

Run-Time Library Routines
SMGSINVALIDATE_DISPLAY

SMGSINVALIDATE_DISPLAY—Mark a

Display As
Invalid

SMGS$INVALIDATE_DISPLAY marks a display as invalid and causes
the entire display to be redrawn.

FORMAT
RETURNS

SMGSINVALIDATE_DISPLAY display-id
VMS Usage: cond_value

type:

access:

mechanism:

ARGUMENT

longword (unsigned)

write only
by value

display-id
VMS Usage:

longword_unsigned

access:

read only

type:

mechanism:

longword (unsigned)
by reference

Specifies the virtual display affected. The display-id argument is the address
of an unsigned longword that contains the display identifier.
Display-id is returned by SMG$CREATE_VIRTUAL-DISPLAY.

DESCRIPTION SMGSINVALIDATE_DISPLAY marks a display as invalid, and redraws the
entire display. You would normally use this routine after you determine

that output has been written to the display without benefit of the Screen
Management Facility.

CONDITION
VALUES
RETURNED

SS$_NORMAL
SMGS$_INVDIS_ID

Normal successful completion.
Invalid display-id.

RTL-649
23

Run-Time Library Routines
SMGS$LABEL_BORDER

SMGS$LABEL_BORDER—Label A Virtual
Display Border

SMGS$LABEL_BORDER supplies a label for a virtual display’s border.

FORMAT

SMGS$LABEL_BORDER display-id [,label-text]
[.position] [,units]
[rendition_set]
[.rendition-complement]
[.char-set]

RETURNS

ARGUMENTS

VMS Usage:

cond..value

mechanism:

by value

type:
access:

longword (unsigned)
write only

display-id
VMS Usage:

longword_unsigned

mechanism:

by reference

type:
access:

longword (unsigned)
read only

Specifies the virtual display affected. The display-id argument is the address

of an unsigned longword that contains the display identifier.
Display-id is returned by SMG$CREATE_VIRTUAL_DISPLAY.

label-text
VMS Usage:

char_string

access:

read only

type:

mechanism:

character string
by descriptor

The new label for this display’s border. The label-text argument is the
address of a descriptor pointing to the label text. If omitted, the display

becomes unlabeled.

position
VMS Usage:

longword_unsigned

mechanism:

by reference

type:
access:

longword (unsigned)
read only

Specifies which of the display’s borders contains the label. The position
argument is the address of an unsigned longword that contains the position

code.

Valid positions are as follows:
*

SMG$K_TOP

SMG$K_BOTTOM

RTL-650
24

Run-Time Library Routines
SMGSLABEL_BORDER

SMG$K_RIGHT

SMG$K_LEFT

If this argument is omitted, the label is displayed on the top border.

units
VMS Usage:

longword_signed

access:

read only

type:

mechanism:

longword integer (signed)
by reference

Specifies the character position at which the label begins within the border.
The units argument is the address of a signed longword integer that contains
the character position. If omitted, the label is centered in the specified border.

rendition-set
VMS Usage:
type:

mask_longword
longword (unsigned)

mechanism:

by reference

access:

read only

Mask which denotes video attributes for the drawn line. The rendition-set
argument is the address of an unsigned longword that contains a video
attributes mask. Each bit attribute in this argument causes the corresponding
attribute to be set in the display.
Video attributes which can be manipulated in this manner are as follows:

SMG$M_BLINK

Displays blinking characters

SMGS$M_BOLD

Displays characters in higher-than-normal intensity

SMG$M_REVERSE

Displays characters in reverse video, that is, using
the opposite default rendition of the virtual display

SMG$M_UNDERLINE

Displays underlined characters

If the same bit is set in both the rendition-set and rendition-complement
arguments, the Screen Management Facility applies the rendition-set

attribute followed by the rendition-complement attribute. Using these two
arguments, the caller can exercise independent control over each attribute in
a single call.

rendition-complement
VMS Usage:

type:
access:

mechanism:

mask_longword

longword (unsigned)
read only
by reference

A mask which denotes video attributes for the line drawn. The renditioncomplement argument is the address of an unsigned longword that contains
a video attributes mask. Each bit attribute in this argument causes the
corresponding attribute to be set in the display. Video attributes which can
be manipulated in this manner are the same as those for the rendition-set
argument.

The following table shows the action taken by the Screen Management

Facility for various combinations of rendition-set and rendition-complement
attributes.

RTL-651
25

Run-Time Library Routines
SMGSLABEL_BORDER

Set

Complement

Action

[

Attribute unchanged

Attribute on

Attribute set to complement of default setting

Attribute off

char-set
VMS Usage: longword_unsigned
type:

longword (unsigned)

mechanism:

by reference

access:

read only

Specifies the default character set for all text in this virtual display. The
char-set argument is the address of an unsigned longword that contains
the character set code. At this time, the only valid value is SMG$C_ASCII,
which is also the default.
_——

DESCRIPTION SMGSLABEL_BORDER lets you specify text to label a virtual display. If the
specified virtual display does not already have the border display attribute

(SMG$M_BORDER), then this attribute is forced. If the laberstring is

supplied, it replaces the current label text for this border. If you supply an
empty (null) label string, the border becomes unlabeled. If the label text
(as positioned within the border) does not fit within the border, this routine

returns SMG$_INVARG.
Position and units together specify the starting position of the label text
within a border. If position is omitted, the default is the top border. If units
is omitted, this routine chooses a starting position so as to center the text
either horizontally or vertically, depending on the implicit or explicit position
argument. If both position and units are omitted, the text is centered in the
top border.
Units specifies the label’s starting row or column position in the border.

CONDITION
VALUES

RETURNED

SS$_NORMAL

Normal successful completion.

SMGS$_INVDIS_ID
SMG$_INVARG

Invalid display-id.
Invalid argument. The combination of position,
units, and label-text arguments resulted in a
position outside the border area.

SMG$_WRONUMARG

Wrong number of arguments.

EXAMPLE
c

C This FORTRAN example program demonstrates the use of SNGSLABEL_BORDER.
c-

C Include the SNG definitions.. In particular, we want SMG$M_BORDER,
C SMGS$K_TOP, SNGSK_BOTTOM, and SMG$K_RIGHT.
c-

INCLUDE ' ($5MGDEF)*

INTEGER SNGS$CREATE_VIRTUAL_DISPLAY, SMGSCREATE_PASTEBOARD

RTL-652

Run-Time Library Routines
SMGSLABEL_BORDER

INTEGER SNGSPASTE_VIRTUAL_DISPLAY,

SHGSPUT_CHARS

INTEGER DISPLAY1, PASTEL
INTEGER DISPLAY2, PASTE2
INTEGER DISPLAY3, PASTE3,

ROWS,

COLUMNS

C Call SNGSCREATE_VIRTUAL DISPLAY to create virtual display mumber 1.
C Give it a border.
e

BOWS = 4
COLUMNS = 30
ISTATUS = SMGSCREATE_VIRTUAL_DISPLAY

(ROWS, COLUMNS, DISPLAY1, SMG$M_BORDER)

C Call SMGSCREATE_VIRTUAL_DISPLAY to cre

virtual display nusber 2.

C Give it a border.
c-

ROWS = 3
COLUMNS = 30
ISTATUS = SNGSCREATE_VIRTUAL_DISPLAY

(ROWS, COLUMNS, DISPLAY2, SMG$M_BORDER)

ce
C Create virtual display number 3. Do HOT give it a border.
o3

ROWS = 4
COLUMNS

= 36

ISTATUS = SMGSCREATE_VIRTUAL_DISPLAY
(ROWS, COLUMNS, DISPLAY3)

C Use SMGSCREATE_PASTEBOARD to create the pasteboard.
c-

ISTATUS = SMGSCREATE_PASTEBUARD (PASTE1)

ce
C Call SNGSPUT_CHARS to put data into the virtual displays.
c-

ISTATUS = SMGSPUT_CHARS ( DISPLAYL
* A bordered virtual displa;

ISTATUS = SNGSPUT_CHARS ( DISPLAY2,

C Call SNGSLABEL_BORDER to label the virtual display borders.
c-

1
1

ISTATUS = SHGSLABEL_BORDER ( DISPLAY1,
ISTATUS = SMGSLABEL_BORDER ( DISPLAY2,
SMGSK_BOTTOM, 1)
ISTATUS = SMGSLABEL_BORDER ( DISPLAYS,
SMGSK_TOP)

'Side’, SNGS$K_RIGHT)

'LABEL Bottom',
'Forced bordering ',

C Call BMGSPASTE_VIRTUAL_DISPLAY to paste the virtual displays.
c-

ISTATUS = SMGOPASTE_VIRTUAL_DISPLAY ( DISPLAY1, PASTE1, 2, 10)
ISTATUS = SMGSPASTE_VIRTUAL_DISPLAY ( DISPLAY2, PASTE1, 2, 46)
ISTATUS = SMGSPASTE_VIRTUAL_DISPLAY ( DISPLAY3, PASTE, 10, 6)
900

FORMAT ('

Routine

returned a status of ',

28)

END

The output generated by this program is shown in Figure RTL-27.

RTL-653

Run-Time Library Routines
SMGS$LABEL_BORDER

Figure RTL-27

Output Generated by Program Calling
SMGSLABEL_BORDER

2carzres

RTL-654
28

Run-Time Library Routines
SMGS$LIST_KEY_DEFS

SMGSLIST_KEY_DEFS—List Key
Definitions
SMGSLIST_KEY_DEFS returns the definition (equivalence string)

associated with a specified key in a specified key table.

FORMAT

RETURNS

SMGS$LIST_KEY_DEFS key-table-id ,context
[ key-name] [ if-state]
[.attributes] [,equiv-string]
[.state-string]
VMS Usage: cond_value

type:

fongword (unsigned)

mechanism:

by value

access:

ARGUMENTS

write only

key-table-id
VMS Usage: longword_unsigned
type:

longword (unsigned)

mechanism:

by reference

access:

read-only

Specifies the key table from which you are extracting a key definition. The

key-table-id argument is the address of an unsigned longword that contains

the key table identifier.

Key-table-id is returned by the SMG$CREATE_KEY_TABLE routine.

context
VMS Usage:
type:

context
longword integer (signed)

mechanism:

by reference

access:

modify

Provides a means to extract a series of key definitions from a key table. The
context argument is the address of a signed longword integer that contains

the context variable. For the first call to this routine, you should set the
context argument to zero.

Context is incremented by the SMG$LIST_KEY_DEFS routine so that the
next call returns the next key definition.

key-name
VMS Usage:
type:

access:

mechanism:

char_string
character string

modify

by descriptor

Identifies the key whose value you are listing. The key-name argument is
the address of a descriptor pointing to the key name.

RTL-655

Run-Time Library Routines
SMGSLIST_KEY_DEFS

if-state
VMS Usage:
type:

char_string
character string

mechanism:

by descriptor

access:

write only

Receives the state name which qualifies the next definition in the key table.

The if-state argument is the address of a descriptor pointing to the storage
into which the state name is written.

attributes

VMS Usage: longword_unsigned
longword (unsigned)
type:

access:

mechanism:

write only

by reference

Attributes of this key definition. The attributes argument is the address of an

unsigned longword into which is written the key attributes.
Possible attributes are as follows:

SMG$V_KEY_NOECHO (Bit 0)

If set, this bit specifies that equiv_
string is not to be echoed when

this key is pressed; if clear, equiv_

string is echoed. If SMGSV_KEY_
TERMINATE is not set, SMG$V_
KEY_NOECHO is ignored.

SMG$V_KEY_TERMINATE (Bit 1)

If set, this bit specifies that when

this key is pressed (as qualified by
if-state), the input line is complete
and more characters should not be
accepted. If clear, more characters
may be accepted.

SMGS$V_KEY_LOCKSTATE (Bit 2)

If set, and if state-string is specified,
the state name specified by statestring remains the current state until

explicitly changed by a subsequent

keystroke whose definition includes a
state-string. If clear, the state name
specified by state-string remains in

effect only for the next defined key
stroke.

SMG$V_KEY_PROTECTED (Bit 3)

If set, this bit specifies that this key
definition cannot be modified or

deleted. If clear, the key definition
can be modified or deleted.

The remaining bits are undefined.

equiv-string
VMS Usage: char_string

type:

character string

mechanism:

by descriptor

access:

write only

The character string into which is written the equivalence string for the next

key definition. The equiv-string argument is the address of a descriptor

pointing to the storage into which the equivalence string is written.

RTL-656
30

Run-Time Library Routines
SMGSLIST_KEY_DEFS

state-string
VMS Usage: char_string
type:

character string

mechanism:

by descriptor

access:

write only

A string into which is written the new state name, if any, which is set by the

next key definition. The state-string argument is the address of a descriptor
pointing to the storage into which the state name is written. If this key
definition sets a state, the attributes flag SMG$V_KEY_SETSTATE is set.

_—

DESCRIPTION SMGSLIST_KEY_DEFS, when called repeatedly, lets you examine all the
definitions in a key table.

CONDITION
VALUES
RETURNED

SS$_NORMAL
SMGS$_INVKTB_ID

Normal successful completion.
Invalid key-table-id.

SMG$_NOMOREKEYS

No more keys in this table.

Any condition value returned by LIBSCOPY_DXDX.

RTL-657

Run-Time Library Routines
SMG$LOAD_KEY_DEFS

SMGSLOAD_KEY_DEFS—Load Key

Definitions

SMGSLOAD_KEY_DEFS loads a file of key definitions (DEFINE/KEY

commands) into a specified key table.

FORMAT

SMGSLOAD_KEY_DEFS

key-table-id ,filespec

[.default-filespec]
[.lognam-flag]
RETURNS

VMS Usage: cond_value

type:

longword (unsigned)

mechanism:

by value

access:

ARGUMENTS

write only

key-table-id
VMS Usage:
type:

access:

mechanism:

longword_unsigned
longword (unsigned)

read only

by reference

Specifies the key table into which you are loading key definitions. The

key-table-id argument is the address of an unsigned longword that contains
the key table identifier.

Key-table-id is returned by SMG$CREATE_KEY_TABLE.

filespec
VMS Usage:

char_string

type:

character string

mechanism:

by descriptor

access:

read only

Strinélcontaining the file specification for the file of DEFINE/KEY commands.
The
filespec argument is the address of a descriptor pointing to the file
specification.

default-filespec
VMS Usage:

char_string

type:

character string

mechanism:

by descriptor

access:

read only

String containing the default file specification for the file of DEFINE/KEY

commands. The default-filespec argument is the address of a descriptor
pointing to the default file specification. If omitted, the null string is used.

RTL-658
32

KNOWN PROBLEMS AND RESPONSES

VAX/VMS

Systems

Dispatch,

July

1986

OPERATING SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

Privileged

image

access

1Mo

V4.1

fX2

Seq.

5.20.18

installed

message

SYS

to message

files

PROBLEM
STATEMENT

access

message /file_name=sys$disk:[]pl7incmsg spr
link /notrace sprmain,spr
message /nosymbols spr
link /notrace /shareable=pl7incmsg

image cannot gain
in the example:

A privileged
file as shown

pli

run

sprmain

$INCYTE-F~-ALREADYALLOC,
INCYTE monitor

$ mcr

spr

sprmain

install

terminal

already

process

allocated

the

sys$disk:[]lsprmain /privilege=world

$ mcr install sys$disk:[]pl7incmsg
$ run sprmain
$NONAME-F-NOMSG,

Message

number

0801800C

RESPONSE

When a process is running an image installed with privilege, the
image activator behaves differently than when it is running
unprivileged

images.

There

are

two parts

this

names

to be

behavior.

All

images
. must be installed.
(There is no need for any privileges
or other attributes of known images.
All that is required is
that the system manager or other privileged user pass judgment on
the image in question.)
In addition, the image activator tells

RMS

that only

"trusted"

logical

are

used

when

RMS

VAX/VMS

Systems

performing
names

are

Dispatch,

the

file

names

July

lookup

created

1986

Page

the

associated

with

image

file.

Trusted

logical

access

mode

EXEC

KERNEL
.

The previous example can be modified in several ways so
message is displayed by an image running with privilege.
o

The

message

image

P17INCMSG.EXE

SYS$MESSAGE

directory.

Modify

file

the

can

specification

placed

the

that

the

MESSAGE

command

from:

MESSAGE

/FILE_NAME=SYS$DISK:[]P17INCMSG SPR

MESSAGE

/FILE_NAME=P17INCMSG

to:

and

place

the

system

EXEC
name

mode

logical

table

that

SPR

name

called

locates

the

P17INCMSG
message

file

P17INCMSG.EXE.
o

Also,

place

shared

the

modification
has

two

the

system

the

process,

EXEC

Another

name

not

into

name

table.

for

name

P1l7INCMSG

table.

LNMSFILE_DEV.

This

name

EXEC

mode

name

points

supervisor

mode

name

group,

logical

and
name

system
that

another
requires

tables.
includes

usually
only

points

Also,

create

the

table

P17INCMSG.

option

create

suitably modify

recommend

the

job,

mode

SYS$DISK and
do

name

logical

translations.

containing
o

logical

private

system

putting

name

executive

mode

LNMS$FILE_DEV.

modified

SYS$DISK

name

(Note

for

that we

logical

name

table.)

Of these options, the first two are the simplest.
The third
option,
while
a
1little
more
complicated,
is
probably
more
flexible and reduces the interaction between this application and
other parts of the system.
We do not recommend explicit use or
manipulation of the name SYS$DISK.

VAX/VMS

Systems Dispatch,

OPERATING

1986

SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

GETLKI

July

mishandled

user

V4.1

Seq.

of:

5.20.19

SYS

buffer

overflow

PROBLEM

STATEMENT

The system service
as documented for

$GETLKI does not report
item codes LKI$_LOCKS,

LKI$_BLOCKING.

all

these

cases,

user buffer overflow
LKI$_BLOCKEDBY, and

bit

the

returned

length value is not set when the user-supplied buffer is too
small to hold the requested data.
1In the case of LKI$_LOCKS for
a locally mastered lock, the entire returned length longword is
invalid.

RESPONSE

expect

partially

that

fix

correct

the

other cases listed above,
as documented, except that
The

complete

fix

Until
the bit
suggestion for

will

update

LKISLOCKS

is
if

user

buffer

size

low

word

returned

length

that

Version

future

release

4.4

behaves

will

longword

the
is

VAX/VMS.

corrected,
we offer the following
the user buffer size is inadequate:

The

the

i.e., the returned length
bit 31 is never set.

appear

31 problem
determining

after VAX/VMS

case

might

greater

inadequate

length
than

supplied.

and

the

size

the

high
of

the

sum

the

word

the

user

buffer

1l of 1

VAX/VMS Systems Dispatch, July 1986

OPERATING SYSTEM:
PRODUCT:

COMPONENT:

VAX/VMS V4.1

Seq.

5.20.20

VAX/VMS
SYS

SWAPPER

SWAPPER trims working sets unnecessarily

PROBLEM
STATEMENT

Wwhen the swapper is invoked because of a lack of balance set
slots, processes are trimmed back to quota before one is swapped.
This is not necessary if there are sufficient free pages.

RESPONSE

Under these circumstances, the swapper should check whether there
are sufficient free pages before trimming.
We

expect

to eliminate

the

unnecessary trimming

update of VAX/VMS.

in a

future

VAX/VMS Systems Dispatch,

OPERATING SYSTEM:
PRODUCT:

COMPONENT:

Filter

line

feeds

July 1986

VIoEHL

VAX/VMS V4.1

Seq.

VAX/VMS

11.15.4

LOGINOUT

out of password

PROBLEM
STATEMENT

When

not

spurious password

user's

the

failures.

password, line-feed characters are
characters read.
This results in

RESPONSE

The

that

VMS

terminal

send

anomalous

service

line-feed

behavior

not designed

characters

can

result

after

deal with

return.

various

cases.

terminals
result,

When

line

editing is enabled, the line-feed character is interpreted as a
delete word command, and therefore, is harmlessly swallowed when

it appears at the beginning of a line.
However, line editing is
disabled during noecho reads (for example, during the reading of
the user's password), and therefore, the line-feed character is
allowed

Although

sense

come

this

to make

through.

general

special

line-editing

filtering

This

problem

fixed

case

terminal

applied

service

correction

in other cases.

in Version

4.4.

problem,

because

makes

the

VAX/VMS

Systems

Dispatch,

OPERATING

July

SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

Low

byte

limit

1986

crashes

V4.2

Seq.

11.15.5

LOGINOUT

system

PROBLEM
STATEMENT

Setting
100)

a user's BYTLM field to a very small value (for example,
causes the system to crash when a user attempts to log in.

RESPONSE

Critical

VMS

functions

stop

working

are

reduced below minimum reasonable
BYTLM of 100
is too small to permit

function

the

after

file

at
a

context

This

file

system.

various

having

set

image

bugcheck.
close

the

open

the

rundown

This
file,

the

user's

the

fatal

file

with

process

problem

fixed

when

LOGINOUT

quotas.

The

event

that

condition

remains

open

account

in VAX/VMS

certain

process

quotas

values.

In this example, a
the process to issue a QIO
result,
it becomes impossible

files

when

for

attempts

failure

triggers

the

Version

4.4.

exit

FILCNTNONZ

because if rundown
indefinitely in the
it.

cannot
system

VAX/VMS

Systems

Dispatch,

OPERATING

July

1986

SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

SYSBOOT

SYSBOOT might mistakenly

V4.1

Seq.

11.30.2

lower PQL_DWSQUOTA

PROBLEM
STATEMENT

SYSBOOT

should

calculate

new

value

for

PQL_DWSDEFAULT

based

interactions with other SYSGEN parameters as described
in
the
VAX/VMS System Generation Utility Reference Manual.
When it is
necessary

change

for PQL_DWSQUOTA
lowered.

this

value,

ensuring

that

the

new

value

PQL_DWSQUOTA

should

being

also

raised,

RESPONSE

We expect

fix

this problem

in a

future

update of VAX/VMS.

used

not

VAX/VMS

Systems

Dispatch,

July

OPERATING

SYSTEM:
PRODUCT:

VAX/VMS
VAX/VMS

COMPONENT:

SHOW ACCOUNTING

reports

1986

1 ofi:

V4.2

Seq.

15.15.5

JOBCTL

enabled

when

disabled

PROBLEM
STATEMENT

If accounting is disabled by the job controller because a write
operation failed,
the Show Accounting Utility (SHOW ACCOUNTING)
does

not

reflect

the

new

(disabled)

state

accounting.

RESPONSE

The

job

used

to determine

controller

This

problem

disregarded

whether

fixed

the

accounting

value

was

in VAX/VMS Version

which

enabled

4.4.

SHOW

ACCOUNTING

or disabled.

VAX/VMS Systems

Dispatch,

OPERATING

1986

SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

Virtual memory

July

used

Doy s |

V4.1

Seq.

15.30.17

PRTSMB

by symbiont

increases

PROBLEM
STATEMENT

Each time the
virtual memory
with

the

file,

print symbiont processes a file,
it allocates
used to store internal data structures associated
but

does

finished.

not

deallocate

the

RESPONSE

This

problem

fixed

in VAX/VMS

Version

4.4.

virtual

memory

when

VAX/VMS Systems Dispatch,

OPERATING SYSTEM:

VAX/VMS V4.2

PRODUCT:

Seq.

VAX/VMS

COMPONENT:

Extra

July 1986

of1l

15.30.18

PRTSMB

form feeds on printer

setup

PROBLEM
STATEMENT

Extra blank pages are generated by the print symbiont when
setup or reset sequence is specified for the current print job.

VAX/VMS

Version

4.2,

1is

possible

create

library

setup/reset modules which are output to the device during the
processing of the current print job.
Setup/reset modules might
be output before a specific file, before all files, or after the
current job is completed.
Device-control library modules that
insert printable text are followed by a form feed.
No form feed
is inserted after a recognized escape sequence, device control
sequence, or operating system specific command string.
We realize that certain limitations are imposed for output
devices that require control sequences in the ASCII range of

printable
those

characters.

devices

that

Certain

allow

the

limitations

user

might

reposition

also

exist

output

for
the

top-of-page after inserting printable text.
We believe this area
of the symbiont might require additional flexibility beyond that
which is currently provided.
We are presently investigating

mechanisms

that would allow such

flexibility.

RESPONSE

VAX/VMS

Systems

Dispatch,

July

1986

OPERATING SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

recall

V4.1

Seq.

20.5.9

DCL

COMPONENT:

NOECHO data

list

PROBLEM
STATEMENT

command

entered

procedure,

TERMINAL/NOECHO,

into

when

data entered

the

recall

using the up-arrow function.

Data

entered

when

into the recall

echo

list.

has

terminal

echo

buffer.
been

This

disabled

data

disabled

in VAX/VMS Version 4.4.

can

should

RESPONSE

This problem is fixed

into DCL variables via

via

SET

viewed

INQUIRE DATA

not

entered

VAX/VMS

Systems

Dispatch,

OPERATING SYSTEM:
PRODUCT:

July

VAX/VMS V4.1
VAX/VMS

COMPONENT:

TOPS-20

1986

Seq.

ofiyl

25.65.2

RTPAD

terminal pause character not

reassignable

PROBLEM
STATEMENT

When a user logs into a VAX/VMS Version 4.n system and issues a
SET HOST command to a TOPS-20 Version 6.1 system, setting the
terminal

image

command

pause

exit

character

with

the

reserved

TOPS-20

operand

system

fault

causes

when

the

RTPAD

following

issued:

TERMINAL

PAUSE

CHARACTER

RESPONSE

Although

not

plan

VAX/VMS after Version

4.4.

allow

the

user

reassign

the

terminal pause character when connected to a TOPS-20 system, we
do expect to correct the image exit problem in a future update of

VAX/VMS

Systems

Dispatch,

OPERATING

July

SYSTEM:

VAX/VMS

PRODUC

V4.3

Seq.

25.65.3

machine

running

VAX/VMS

COMPONENT:

Terminal

1986

characteristics

RTPAD

not

restored

PROBLEM
STATEMENT

When

user

VAX/VMS

issues

Version

4.3

SET

and

terminal

characteristics

restored

their

HOST

command

subsequently

original

altered

from

logs
the

off

remote

the

remote

session

node,

are

not

state.

Currently,

RESPONSE

terminal

remote session.
consider changing

characteristics

are

not

restored

after

This
is a reasonable suggestion,
and we will
this behavior in a future update of VAX/VMS.

VAX/VMS

Systems

Dispatch,

OPERATING

July 1986

SYSTEM:

VAX/VMS V4.2

PRODUCT:

Seq.

25.65.4

remote

VAX/VMS

COMPONENT:

RTPAD

Remote SET TERMINAL/PERMANENT might

fail

PROBLEM
STATEMENT

user

has

SET

HOST

from

VAX/VMS

system

system and issues the DCL command SET TERMINAL/PERMANENT in
combination with any other qualifier, the command may or may not
work, depending on the user's privileges on both the local and
remote

nodes.

the

local

user

and

the

has

LOG_IO

PHY IO

remote

nodes,

the

command

user

remote

does

node,

not

the

have

command

the

privileges
executes

proper

both

privileges

terminates

the

properly.

with

the

error

message:

$SYSTEM-F-NOPRIV,
3.

the

user

has

no privilege

proper

privileges

lacks
those
privileges on
the
terminates with an insufficient
as well as:
SREM-E-QIOERR,

Internal

QIO

for
on

attempted
the

remote

operation
node,

but

local
node,
the
command
privilege error message,

error

RESPONSE

Although LOG_IO or PHY IO will
and
remote
nodes
in order to

always be
issue
the

command,

the

update

future

expect
of

to eliminate
VAX/VMS.

required on both local
SET TERMINAL/PERMANENT

REM-E-QIOERR error message

VAX/VMS Systems Dispatch, July 1986

OPERATING SYSTEM:
PRODUCT:
COMPONENT:

VAX/VMS V4.1
VAX/VMS

Seq.

of1l

25.65.5

RTPAD

error

TOPS-10 to VMS protocol

PROBLEM

STATEMENT

When a user performs a SET HOST from a machine running VAX/VMS
Version 4.0 to a remote node running TOPS-10 Version 7.03, the
connection terminates with the following error message:
$REM-E-PROTERR,

internal

protocol error

RESPONSE

This

problem was

Version

7.03.

fixed

in VAX/VMS

Version

4.2

and

in TOPS-10

VAX/VMS

Systems

OPERATING

Dispatch,

July

SYSTEM:

Seq.

31.55.2

VAX/VMS

COMPONENT:

not

1 of

VAX/VMS V4.1

PRODUCT:

End-of-file

1986

TMDRIVER

recognized

on TEl6

PROBLEM

STATEMENT

The

SENSEMODE

MT$M_EOF

bit

The SENSEMODE
bpi.

function

when

TEl6

tape

1600-bpi

tape

function

for

works

drive

fails

positioned

properly

for

tapes

sense

tape

written

the

mark.
at

800

incorrect behavior occurs because there is a problem in
tape formatter which controls TE16 and TU77 tape units.

the

RESPONSE

This
TMO3

I/O

function

causes

tape

motion

that

ends

the MT$M_EOF bit is properly set.
However,
if
function causes no tape motion
(a SENSEMODE,
for

the

tape

erroneously

written
cleared

This problem
Version 4.4.

will

and

1600
the

fixed

bpi,

the

MT$M_EOF

tape

bit

future

mark
not

update

tape

mark,

the next
example),

I/O
and

information

set.

VAX/VMS

after

VAX/VMS

Systems

Dispatch,

July

1986

OPERATING SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

Out-of-band

character

not

V4.1

Seq.

)

33.5.3

CTDRIVER

checked

PROBLEM
STATEMENT

user

Version

CTRL/Y

does

4.2,

CTDRIVER

runs

SET
an

out-of-band

delivers

for that character.

HOST
image

to
on

remote

even

character,

CTRL/Y

machine

that

AST

and

types

node

running
which

CTRL/Y

IO$M_INCLUDE

VAX/VMS
declares

character,

not

set

RESPONSE

CTDRIVER,
CTRL/Y or

the remote terminal driver, does not check whether
CTRL/C is supposed to be included in the data stream

associated

attention ASTs,

when

those

characters

are

declared

out-of-band;

delivers

the

regardless.

In a future update of VAX/VMS after Version 4.4, we plan to
modify CTDRIVER to screen control
characters according
to the
same

rules

that TTDRIVER follows.

VAX/VMS Systems Dispatch, July 1986

OPERATING SYSTEM:
PRODUCT:

COMPONENT:

VAX/VMS V4.1

1 o £

Seq. 33.20.11

VAX/VMS
TTDRIVER

Secondary transmitted signal not set on DMF-32

PROBLEM
STATEMENT

The VAX/VMS I/0 User's Reference Manual, Part I, states that the
secondary transmitted data signal may be set via the set modem
This is normally pin 14 according to
function modifier on $QIO.
the RS-232 standard.
shown that pin 19,

However, on a DMF-32 controller tests have
Secondary Request to Send, is actually

activated.

RESPONSE

Because the DMF-32 does not provide the secondary transmitted
data signal, the driver sets Secondary Request to Send instead.
The desired results can be obtained by using a jumper cable
between pins

and

19.

The VAX/VMS I/0 User's Reference Manual, Part I, which notes the
difference in operation for this controller, is fixed in VAX/VMS
Version 4.4.

VAX/VMS

Systems

Dispatch,

OPERATING

July

SYSTEM:

VAX/VMS

PRODUCT:

VAX/VMS

COMPONENT:

LCDRIVER

1986

causing

system

V4.0

Seq.

34.16.2

LCDRIVER

crashes

PROBLEM
STATEMENT

VAX/VMS

Version

powerfail.
DMF-32

and

printer

4.0,

4.1,

crash

might

battery

port

the

system

problem

was

VAX/VMS

Version

produced

Version

the

customers

reported

that

printers

connected

determined

that

must

crash

the

tab

the

output

might

VAX

crash

after

equipped

with

investigation

the

use

shows

the

replacement

kit.

replacement

4.2

the

that

time

LCDRIVER

the

to occur.

update

and

systems
if

Further

corrected

4.1,

4.2

occur

DMF-32

4.3

containing

4.0,

and

backup.

for

powerfail
This

The

addition,

LCDRIVER

systems.

Upon

expansion

was

printer
device

for

SPR

kits

use

installing
no

longer

VAX/VMS

the

kits,

exhibited

port

the

not

the

point of

the
were

DMF-32.

was

failure.

RESPONSE

The
tab
expansion
problem
associated
with
installing
the
replacement LCDRIVER occurs only on systems using a DMF-32 with
microcode revision level earlier than 4K28.
Tab expansion is not
performed in the LCDRIVER.
Rather, tab expansion is performed
by the DMF-32 microcode.
The replacement LCDRIVER distributed to
correct problems
after powerfail
includes
bit-sensing
changes.
These changes are required to support modifications included in
version 4K28 of the DMF-32 microcode.

VAX/VMS

Versions

4.0

and

4.1

not

reflect

definitions for tab expansion and line
the DCL commands SET PRINTER/TAB and
perform

expected

the

VAX/VMS

replacement

LCDRIVER

used.

4.2

advantage

the

printer

take

Versions

Customers

correct

characteristics.

the

correct

system

truncation.
Consequently,
SET PRINT/TRUNCATE do not
4.0

must

system

and

4.1

update

definitions

when

the

Version

for

these

VAX/VMS

Systems Dispatch,

July

1986

The following checklist describes the requirements for correcting
problems with tab expansion, truncation, and powerfail associated

with the

DMF-32 and

the VAX/VMS

operating system prior to Version

4.2.

VAX/VMS Version

The latest
This might

4.2 must

installed

level equals or exceeds

The replacement
VAX/VMS Version
This

requires

The

following

for

correcting

associated

action

with

the

system.

level of DMF-32 microcode must be installed.
require DMF-32 hardware replacement.

(Diagnostics should be performed

microcode

revision

level

the

4K28.)

SPR kit for the LCDRIVER distributed
4.2 must be installed on the system.

that

the

item

problems

the

to ensure that

DMF-32

system be

rebooted.

checklist

describes

with

tab

expansion

later

must

and

for

the VAX/VMS

the

requirements

and

Version

4.3

truncation
operating

system.

VAX/VMS

Version

4.3

DMF-32

installed

the

system.

The
This

latest

level

might

require

microcode

DMF-32

must

hardware

installed.

replacement.

(Diagnostics should be performed to ensure that the
microcode level equals or exceeds revision level 4K28.)

VAX/VMS

Systems

Dispatch,

July

OPERATING

SYSTEM:
PRODUCT:

VAX/VMS V4.1
VAX/VMS

COMPONENT:

Uppercase

character

1986

150

)

Seq.

34.20.2

not

convert

LPDRIVER

support

PROBLEM
STATEMENT

The

line

printer

attached

LP11l

controller

does

certain
characters
to
their
respective
uppercase
equivalents.
The opening brace character ({) and the closing brace character
(1)
are
not
properly
converted
to
uppercase
character
equivalents: the opening bracket ([) and the closing bracket (]).

RESPONSE

expect

Version

fix

this

problem

4.4.

future

update

of VAX/VMS

after

VAX/VMS

Systems

Dispatch,

July 1986

OPERATING

SYSTEM:
PRODUCT:

VAX/VMS V4.1
VAX/VMS

COMPONENT:

Long

UICs

truncated

over

TYOE

Seq.

40.45.19

RMS

network

access

PROBLEM
STATEMENT

RMS does not correctly £i11 in the UIC field in the protection
XAB

lower

the

word

file

the

remote

DECnet

group and member

accessed

fields

node.

Only

the

supplied.

RESPONSE

Both RMS and the file access listener (FAL) were incorrectly
formatting the UIC field prior to transmitting it to the remote
system.
This was fixed in VAX/VMS Version 4.3.

VAX/VMS Systems

Dispatch,

July 1986

OPERATING SYSTEM:
PRODUCT:

VAX/VMS V4.1
VAX/VMS

COMPONENT:

RMS

record

lock

lof1l

Seq.

40.45.20

RMS

conversion

problems

PROBLEM

STATEMENT

Manual
the

record

locking

following

does

A
user
executes
allowing readers.
same

record,

second

not

appear

work

expected

under

circumstances:

a $FIND,
locking
The same user then

locking

user

can

for

still

the
record
for
read,
executes a $GET on the

exclusive

execute

access.

$FIND on

the

this

point,

record.

RESPONSE

the

user

attempts

currently
change

request.

For

currently

held

the

user

the

instance,
record

lock

attempting

successfully

without

This

problem

holding
mode

fixed

from

altering

lock

that

attempt

READ

the
the

in VAX/VMS

record
to

record

RMS

made

exclusive,

above
current

Version

lock,

example,
record
4.4.

ignores

to
RMS

the

change

which

lock.

file

what

returns

VAX/VMS

Systems

Dispatch,

OPERATING

July

SYSTEM:

with

Seq.

40.45.21

VAX/VMS

COMPONENT:

fails

VAX/VMS V4.2

PRODUC

RMS

1986

RMS

RMS$_ENQ/SS$_CVTUNGRANT

PROBLEM
STATEMENT

program

that

asynchronous

status
an

attempt

RMS$_ENQ
to

accessing

multi-streamed

and

convert

record

STV

shared

code

ungranted

file

operations

lock.

problem

fixed

in VAX/VMS

Version

4.4.

extensive

with

SS$_CVTUNGRANT

RESPONSE

This

using

fails

error

indicating

VAX/VMS

Systems

OPERATING

Dispatch,

SYSTEM:

PRODUCT:
COMPONENT:

Embedded

blanks

not

July

1986

VAX/VMS V4.1

Seq.

f) 1

45.1.3

VAX/VMS
RTL

permitted

UICs

PROBLEM
STATEMENT

The
Disk Quota Utility
(DISKQUOTA)
does
not
recognize
certain
forms of symbolic UIC expressions that are recognized correctly
by other commands and utilities.

RESPONSE

This problem is caused by the system's central UIC and identifier
parsing logic which does not permit embedded blanks in the UIC
expression.
In all commands and utilities other than DISKQUOTA,
the command processing strips the blanks out of the command line,
masking the problem.
This

problem

fixed

in VAX/VMS

Version

4.4.

VAX/VMS

Systems

Dispatch,

July

OPERATING

SYSTEM:
PRODUC

VAX/VMS
VAX/VMS

COMPONENT:

Recovered

files

have

1986

V4.0

Seq.

55.5.3

ANALYZE/DISK

incorrect

backlinks

PROBLEM
STATEMENT

Files

recovered

[SYSLOST]

by VERIFY have

incorrect

backlinks.

the

correctly

RESPONSE

VERIFY
update

will be fixed
of VAX/VMS

set

backlinks

future

VAX/VMS

Systems

Dispatch,

OPERATING SYSTEM:
PRODUCT:
COMPONENT:

Errors

during

bootstrap

July

1986

VAX/VMS V4.1
VAX/VMS
ANALYZE/ERROR_LOG

log

incorrect

Seq.

55.5.4

date/time

PROBLEM
STATEMENT

The

generated

by Version

4.1

incorrect date of

report

4-JAN-1978

09:54:55.37.

of ANALYZE/ERROR_LOG

produces

RESPONSE

ANALYZE/ERROR_LOG

correctly

logged

for

the

entries.

Errors

can

logged

system is booting.
initialized to the
If

the

entry

current

value

representing

future

operating

have been
logged.

documentation

before

the

describing

the

operating

those

system

locations

sets

contain

09:54:55.37.

VAX/VMS,
error

that

VAX/VMS

contents

4-JAN-1978

revision

time

VAX/VMS

logged

the

the date/time that

The system date/time may or may not
current date/time when the entry was

date/time,

during

interpreting

logging

note
time

will

stamps.

added

the

VAX/VMS

Systems Dispatch,

OPERATING SYSTEM:

PRODUCT:
COMPONENT:

Analyzing errors

for RA81

July 1986

ALECsE

VAX/VMS V4.2

Seq.

]

55.5.5

VAX/VMS
ANALYZE/ERROR

disk

PROBLEM
STATEMENT

When

trying to analyze disk errors on an RA81, ANALYZE/ERROR_LOG

gets an access

violation and causes

a forced

image

RESPONSE

This problem was

corrected

in VAX/VMS Version 4.3.

exit.

VAX/VMS

Systems

Dispatch,

OPERATING

SYSTEM:

July

VAX/VMS

PRODUCT:
COMPONENT:

/INCLUDE

/EXCLUDE

1986

V4.2

Seq.

55.5.6

VAX/VMS
ANALYZE/ERROR

keyword

values

misinterpreted

PROBLEM
STATEMENT

ANALYZE/ERROR LOG/EXCLUDE= (VOLUME_CHANGES, CONTROL ENTRIES,TAPES)
does not function as documented. ~ Report output is not produced

if certain combinations of keywords are used in the /INCLUDE and
/EXCLUDE qualifier value.
If a combination of VOLUME with either
device

lists

selection

for

either

required entries
For

example,

are

when

device

/INCLUDE
selected

/INCLUDE

(VOLUME CHANGES,TAPES)

volume entries

are

output;

error

output.

entries

specified

has

class

selection

/EXCLUDE,

for

then

used

the

not

all

the

output.

(VOLUME_CHANGES,DISKS)

specified for
however,
The

neither

order

/INCLUDE

ANALYZE/ERROR LOG,

the

disk

nor

the

tape

which

the

keywords

are

impact.

If
either
/EXCLUDE
=
(VOLUME_CHANGES,TAPES)
or
/EXCLUDE
=
(VOLUME_CHANGES ,DISKS)
is
specified
to
ANALYZE/ERROR _LOG,
the
volume “entries

entries
If

the

are

output

keywords

documented.
for /INCLUDE

not

output,

but

the

disk

and

tape

error

inappropriately.
are

Problems

specified

occur only

individually,

when

both

they

keywords

are

work

or /EXCLUDE.

RESPONSE

This

problem will

corrected

future

update

specified

of VAX/VMS.

VAX/VMS

Systems

Dispatch,

OPERATING SYSTEM:
PRODUCT:

reserved

1986

VAX/VMS V4.2
VAX/VMS

COMPONENT:

Debugger

July

of:d

Seq.

55.50.9

function that

returns

DEBUG

operand

fault while

using

PL/I

PROBLEM
STATEMENT

If
a

the debugger

is used

character string,

to step over a PL/I

reserved

operand fault might

occur.

RESPONSE

This behavior
the debugger

functions

debugger

stems from an incorrect interaction between the way
implements STEP/OVER and the way PL/I
implements

that

return

implements

enter

the

routine,

fault

occurs

character

modifying

the

strings.

STEP/OVER by using

return,

the
and

stack

the

trapping

Specifically,

hardware

T-bit

the

that a

reserved

operand

that

reserved

operand

fault.
However, in some cases, PL/I moves stack frames in such a
way that the debugger no longer recognizes the reserved operand
fault as

being

This problem

the

one

fixed

that

caused.

in VAX/VMS Version

4.4.

VAX/VMS

Systems

OPERATING

Dispatch,

SYSTEM:

PRODUCT:
COMPONENT:

MAIL ATTACH/PARENT command

July

1986

Inofail

VAX/VMS V4.2

Seq.

56.30.11

VAX/VMS
MAIL

fails

PROBLEM

STATEMENT

The ATTACH/PARENT command in the Mail Utility
(MAIL)
causes an
image-forced exit if the UIC of the parent process does not match
the default UIC,

specified

the

UAF

entry

RESPONSE

This

problem was

fixed

in VAX/VMS

Version

4.3.

for

the

account.

VAX/VMS

Systems

Dispatch,

OPERATING SYSTEM:
PRODUCT:

forwarding

can

VAX/VMS V4.2
VAX/VMS

COMPONENT:

Remote

July 1986

Seq.

56.30.12

MAIL

cause

MAIL

to hang

PROBLEM
STATEMENT

The MAIL prompt never returns to the user who is sending MAIL to
two recipients on a remote node if one remote recipient has his
mail

forwarded

Under

the

following

other

recipient.

circumstances,

when

user

sends mail

on node

NODEA:

and
on

SET PROCESS/PRIVILEGE=SYSNAM

MAIL

MAIL>

SET

FORWARD user2/USER=userl

user

node

NODEA,

BAR

attempts

follows,

MAIL

send

never

message

returns

addressees

control

the

user.

$ MAIL
MAIL>

SEND SYS$SLOGIN:LOGIN.COM

To:

NODEA: :USER1 ,NODEA:
: USER2

Subj:

The MAIL

utility never

returns

the

MAIL>

prompt

RESPONSE

correct

MAIL
uses
restriction

this

future major

problem,

necessary

to modify

to
send
remote
messages.
At
remains; we will consider changing
release of VAX/VMS.

the

protocol

this
time,
the protocol

this
in a

VAX/VMS

Systems

Dispatch,

OPERATING

SYSTEM:
PRODUCT:
COMPONENT:

SET HOST/DTE/LOG

July

1986

irofad

VAX/VMS V4.1
VAX/VMS
SET HOST/DTE

Seq.

56.80.9

inaccurate

PROBLEM

STATEMENT

SET HOST/DTE/LOG does

not accurately

record

the

terminal

session,

specifically:
1.

Blank

Recording

Lines
as

lines

are missing

ends

that

are

separate

too

the

log

early -

the

logout

supposed

file.
line

overprinted

omitted.

are

recorded

lines.

RESPONSE

Problem

will

fixed
be

unlikely

in VAX/VMS
corrected

that

Version

4.4.

future

problem

will

update

VAX/VMS.

corrected

the

near

future since implementation will require a new file format.
will, however, consider this suggestion for a future release
VAX/VMS
.

We
of

VAX/VMS Systems Dispatch,

OPERATING SYSTEM:

PRODUCT:

COMPONENT:

SET TERMINAL/INQUIRE

July 1986

VAX/VMS V4.0

Seq.

VAX/VMS
SET

56.80.10

TERMINAL

resets multinational

PROBLEM
STATEMENT

The

SET TERMINAL/INQUIRE

terminal,

changes

the

command,

when

setup NATIONAL

issued

VT200-series

to MULTINATIONAL.

RESPONSE

When a VT200-series terminal is detected, SET TERMINAL/INQUIRE
sends out escape sequences to ensure that the device is in the

correct state for 8-bit characters and 7-bit control sequences.
These sequences cause a soft reset of the terminal; a soft reset

is an operation that occurs

in the microcode of

the device.

This

soft reset is setting NATIONAL to MULTINATIONAL.
Unfortunately,
there is no way for SET TERMINAL/INQUIRE to avoid the effect of
this reset or to change it afterwards.
Therefore, we suggest

that

you

immediately

either

avoid

correct your

the

setup

use

following

SET

its

TERMINAL/INQUIRE
issue.

VAX/VMS

Systems

Dispatch,

OPERATING SYSTEM:
PRODUCT:
COMPONENT:

Description

truncated

July

1986

VAX/VMS V4.1
VAX/VMS

LI'Sf"

Seq.

56.85.7

SHOW QUEUE

in SHOW QUEUE/FORM/FULL

PROBLEM
STATEMENT

The
the

output of the DCL command SHOW QUEUE/FORM/FULL
entire 255-character description.

does

not

show

RESPONSE

Although the job controller stores and returns the entire message
in the queue file, the DCL command SHOW QUEUE only displays the
first 34 characters.
We will consider your suggestion in a
future functional update of VAX/VMS.

VAX/VMS

Systems Dispatch,

OPERATING SYSTEM:
PRODUCT:
COMPONENT:

Valid values

July 1986

VAX/VMS V4.1

Seq.

65.5.41

VAX/VMS
DOCUMENTATION

for SET TERMINAL/WIDTH

PROBLEM

STATEMENT

Both the VAX/VMS DCL Dictionary and the HELP text state that SET
TERMINAL/WIDTH = n accepts values n = 0 to 255.
In: fact, SET
TERMINAL/WIDTH accepts values in the range 1 to 511.

RESPONSE

expect

DCL Dictionary

fix

and

this

error

the HELP

text.

future

revisions

the VAX/VMS

VAX/VMS

Systems

Dispatch,

OPERATING

SYSTEM:
PRODUC

remote

images

1986

VAX/VMS

V4.2

Seq.

65.5.42

DECNET

COMPONENT:

Running

July

DOCUMENTATION

requires

READ

access

PROBLEM
STATEMENT

Using the DCL command RUN
network with EXECUTE access

to
to

execute an image over
the image file fails.

the

DECnet

RESPONSE

provide

secure

computing

environment,

READ

access

required to execute an image across the network.
This fact was
was not clearly stated in the description for the RUN command.
This information will be emphasized in a future revision of the

VAX/VMS

DCL_Dictionary.

VAX/VMS

Systems

Dispatch,

July 1986

OPERATING

SYSTEM:
PRODUCT:

VAX/VMS
VAX/VMS

COMPONENT:

Documentation

error

1of

V4.2

Seq.

65.5.43

DOCUMENTATION

for QUEUE_IDLE

bit

in GETQUI

PROBLEM
STATEMENT

The

documentation

QUI$_QUEUE_STATUS
Queue

for

the

in system

contains

This implies that if the
jobs.
However, this is

QUI$SV_QUEUE_IDLE
service
job

$GETQUI

flag

item

code

states:

requests

bit is set, the
not how $GETQUI

queue in question has
interprets the bit.

RESPONSE

The

documentation
Queue

This statement
documentation.

misleading.

contains

no executing

will

corrected

should

read:

jobs

future

revision

the

VAX/VMS

Systems

Dispatch,

July

OPERATING

SYSTEM:
PRODUCT:

VAX/VMS
VAX/VMS

COMPONENT:

SET PROTECTION

1986

V4.2

Seqg.

65.5.44

DOCUMENTATION

cannot modify

remote

file

PROBLEM
STATEMENT

The

DCL

command

SET

PROTECTION

does

not

behave

expected

when

using a DECnet node name in the file specification.
An error
message is returned indicating an invalid file specification.

RESPONSE

not

intended

FILE/PROTECTION
node

name.

This

restriction

future

that

modify

revision of

will

either

DCL

command

file

the

documented

the VAX/VMS

SET

under

both

DCL Dictionary.

PROTECTION

specification

SET

includes

commands

CUMULATIVE INDEX

VAX/VMS SYSTEMS DISPATCH

CUMULATIVE

INDEX FOR VAX/VMS V4.n
JULY

1986

Following is a cumulative listing of articles for VAX/VMS V4.n and layered products.

The following list is designed so that in future issues it can be expanded.,

Consequently, there are

several numbers "reserved” for that purpose, Also, within each category the numbering scheme allows for
expanding the primary category to include related subsets., For example, under 55,0, Utilities, 55,35 is
used for the COPY utility, 55.60 is used for the DIFFERENCES utility, etc. Periodically, the components
list is reviewed to insure that it accommodates the current software needs.

R = indicates a republished article
F = indicates problem was fixed in one of the Versions between 4.0 and 4

Component/

Sequence

Product

Number
1.0

NEWS BULLETIN

Operating
stem

Title of Article

Mon/¥r

NEWS BULLETIN SECTION

1.1.1

IMPORTANT VAX/VMS VERSION 4.2 INFORMATION

vd.2

1.1.2

IMPORTANT VAX/VMS VERSION 4,2 INFORMATION

V4.2

1.1.3

IMPORTANT VAX/VMS VERSION 4.2 INFORMATION

V4.2

1.1.4

PATCH KIT FAILS TO INSTALL AFTER VERSION 4.2
V4.2

UPGRADE

1.1.5

PROBLEM IN VAX/VMS DATA ENCRYPTION FACILITY

1.1.6

IMPORTANT VAX/VMS VERSION 4.n INFORMATION

Vé.n

1.1.7

RUN-TIME LIBRARY DOCUMENTATION CORRECTION

vd.4

5.0

EXECUTIVE & SYSTEM SERVICES SECTION

IMAGE ACTIVATOR

5.5.1

IMAGE INSTALLED AS /SHARE REQUIRES WORLD:R ACCESS

V4.0

sys

5.20.1

F$GETDVI INFORMATION INVALID IF DISK NOT MOUNTED

V4.0

EXCESSIVE MODIFIED PAGE LIST WRITING

V4.0

5.20.3

GETJPI PROC_INDEX VALUE

V4.0

5.20.4

SHUTDOWN WITH REBOOT CHECK CAN FAIL

V4.0

5.20.5

TODR DEPINITION REMOVED IN VAX/VMS VERSION 4.0

V4.0

85 F

5.20.6

SCREEN MANAGEMENT SYMBOLS DEFINED INCORRECTLY

V4.0

Jul 85 F

5.20.7

TEMPORARY MAILBOX LOGICAL NAMES

V4.0

5.20.8

LACK OF DISK QUOTA CAUSES ERRFMT TO FAIL

V4.0

5.20.9

GETJPI ("","TERMINAL") TRUNCATES NAMES

V4.0

85 F

5.20.10

CANNOT ALLOCATE OFFLINE DEVICE

V4.0

5020411

DETACHED PROCESSES FAIL TO ACTIVATE

V4.1

5.20,12

MISSING .EXTERNAL DIRECTIVE IN $FAQ_S MACRO

V4.0

5.20.13

F$LOGICAL AND USER-CREATED NAME TABLES

V4.0

5.20.14

RSX,EXE AND IMAGE ACCOUNTING

va.1

5.20,15

MAILBOXES AND LOGICAL NAMES

V4.0

542016

CLUSTER $BRKTHRU FUNCTION

V4.1

5020417

P1V PARAMETER DOES NOT FUNCTION CORRECTLY

V4.1

86 F

5.20.2

Component/

Sequence

Product

Number

Title of Article

System

Mon/Yr

5.20,18

PRIVILEGED IMAGE ACCESS TO MESSAGE FILES

V4.1

Jul 86

5.20.19

GETLKI MISHANDLED USER BUFFER OVERFLOW

V4.1

Jul 86

5420,20

SWAPPER TRIMS WORKING SETS UNNECESSARILY

V4,1

Jul

7.0

STARLET

Operating

SYSTEM LIBRARIES SECTION

7.30.1

EXAMPLE PROGRAM GETS LINK ERRORS

V.1

Nov 85

Sequence
Number

Title of Article

Operating
system

Mon/¥r

Jul 85

TOP

Component/
Product.

10,0

ACCOUNTING

STARTUP

SYSBOOT

SYSGEN

SYSINIT

VMSINSTAL

SECURITY SECTION

PROBLEMS WITH ACCOUNTING SELECTION BY UIC

V4.0

10.5.2

USER RECORD DISPLAYS SCROLL OFF SCREEN

V4,0

Jul 85

10.5.3

IMAGE NAMES NOT CLEARED IN ACCOUNT/FULL

V.1

Mar 86

10,15.1

TERMINAL LOGICAL NAMES IN UVSTARTUP,COM

V4,0

Sep 85

10.15.2

ERROR IN MicCroVMS SYSTARTUP

V4.0

Nov 85

Sep 85

OPERATIONS SECTION

11,15,1

INCORRECT VALIDATION OF MAXJOBS

V4,0

11.15.2

DEFCLI

V4,0

Sep 85

11.15.3

NETWORK JOBS NOT COUNTED AGAINST MAXJOBS

va.1

Sep

11,15.4

FILTER LINE FEEDS OUT OF PASSWORD

V4.1

Jul 86

11.15.5

LOW BYTE LIMIT CRASHES SYSTEM

V.2

Jul 86

11,30,1

TOPSYS SYSTEM ROOT IS INCORRECT

V4.0

Sep 85

11,30,2

SYSBOOT MIGHT MISTAKENLY LOWER PQL_DWSQUOTA

V4,1

Jul 86

11,35.1

DISCREPANCY

V4.0

Jul

11.35.2

LONG PILE SPECIFICATION CORRUPTS DDB

V4.0

Jan 86

11.35,3

WRONG MESSAGE SETTING SYSGEN PARAMETER TOO LOW

V4,1

Jan 86

Jul 85

PROHIBITS CLI TABLE CHANGE IN SPAWN

IN SCSNODE NAME LENGTH

11,40,1

QUOTA CACHING DISABLED ON THE SYSTEM DISK

V4.0

11,40,2

SYSUAF,DAT REDEFINED POR BYPASS AT LOGIN

V4.0

Sep 85

11,40,3

DUPLICATE SYSTEM

V4,0

May

12,0

UPGRADE

OPERATIONS &

10,5.1

11,0

LOGINOUT

SYSTEM MANAGEMENT,

DISK LABEL NAMES

PREVENT BOOTING

SOPTWARE INSTALLATION SECTION

12.10,1

CVTUAF DOES NOT COPY USER DATA AREA

V4.0

Jul 85

12,10.2

VMSINSTAL FAILS DURING VERSION 4.0 UPGRADE ON TUB1 V4.0

Jul 85

12,15,1

VMIBCKERR,TMP INADVERTENTLY PLACED IN SAVE SET

V4,0

Jul 85

12,15,2

'VMSINSTAL GET OPTION FAILS ON VERSION 4 UPDATE

V4.0

Sep 85

12,15,3

VMSINSTAL OPTION G INITIALIZES INCORRECTLY

V.1

Mar 86

SECURITY

13,5.1

15,0
JOBCTL

PRINT SYMBIONT

QUEMAN

Article

System

Mon,

V4.0

Nov

SECURITY SECTION

ACL PROTECTION OF GLOBAL SECTIONS

BATCH,

PRINT,

JOB CONTROLLER SECTION

15,15,1

SNDSMB WITH FILESIZ OPTION FAILS

V4.0

15.15.2

JOB CONTROLLER SIGNALS AN INVALID BLOCK ERROR

V4.1

15.15.3

NO PROCESS SLOTS CAUSES JOBCTL TO ABORT

V4.1

15,15.4

SET QUEUE/ENTRY/RELEASE COMMAND WORKS INCORRECTLY

V4.2

15.15.5

SHOW ACCOUNTING REPORTS ENABLED WHEN DISABLED

V4.2

15,25,1

SYMBIONT ISSUES BLANK PAGES WITH /SETUP

V4.0

15.25,2

SUGGESTION FOR DEFAULT PORM FOR EACH QUEUE

V4.0

15,25,3

PRINT/NOFLAG DOES NOT OVERRIDE /SEPARATE=FLAG

V4,0

15,30,1

HOW TO PRINT HEADERS

V4.0

15.30.2

UNEXPECTED SYMBIONT PROCESS TERMINATION

V4.1

15,30,3

CANNOT BYPASS ALL FORMATTING IN PRINT SYMBIONT

V4.0

15,30.4

PRINT SYMBIONT ALLOCATES OUTPUT DEVICE

V4.0

15,30,5

MULTIPLE PAGE HEADERS GENERATED BY PLOT

V4.1

15,30.6

LOSS OF PRINT JOB WHEN CARRIER IS

V4.1

15,30,7

FILE

LEFT OPEN BY PRINT SYMBIONT

V4.1

15.30,8

IMPLICIT SPOOLING RESTRICTS USER

V4.0

15,30,9

PRINT SYMBIONT PERFORMS TAB EXPANSION

V4.0

15,30,10

PRINT SYMBIONT PROCESS TERMINATION

V4.1

15,30,11

PRINT SYMBIONT ENTERS COMPUTE LOOP

V4.1

15,30,12

MISCELLANEOUS PROBLEMS IN PRINT SYMBIONT

V4.1

15,30,13

SERIAL PRINTERS ON DMF DISCONNECT

V4.0

15,30,14

PRINTER SUPPORT FOR ESCAPE SEQUENCE CHARACTER

V4,0

15,30,15

PROBLEMS MODIFYING SYMBIONT INPUT FILTER

V.1

15,30,16

IMPLICIT SPOOLING IS INFLEXIBLE

V4.1

15,30,17

VIRTUAL MEMORY USED BY SYMBIONT INCREASES

V4,1

15,30,18

EXTRA FORM FEEDS ON PRINTER SETUP

va.2

15,35.1

INCORRECT OPERATION OF SUBMIT/AFTER/PRIORITY

V4.1

20,0

80-COLUMN FORMAT

DROPPED

DCL_SECTION

20.5.1

CAPTIVE ACCOUNT CAUSES LOGINOUT ACCESS VIOLATION

V4.0

20.5.2

CANNOT CHANGE/EXAMINE LOGICAL NAME TABLE

V4.0

20.5.3

LGICMD=NL:

DISABLES VERIFICATION

V4.0

20.5.4

RUN/INTERVAL DOES NOT WORK IF TIME > 24 HOURS

20,5.5

CTRL/T TRUNCATES LONG FILE NAMES

V4.1

20,5.6

LIBSSPAWN

Vd.1

20.5.7

REDEFINING SYSSOUTPUT LOCKS

vé.1

('RUN/DELAY,,..') DOES NOT WORK
PILE

PROT

20,5.8

DATA STREAM NOT TREATED AS INPUT DATA

V4,1

20,5.9

NOECHO DATA IN RECALL LIST

V4.1

86
Jul

13.0

Operating
Title of

Number

Sequence

Product

mmmmomomy

Component/

Sequence

Product

Number

25,0

DECnet

Operating
Title of Article

System

Mon/Yr

V4.0

Jul 85

DECnet SECTION

25.5.1

NETWORK JOBS USE DEFAULT DCLTABLES

25,5.2

SPURIOUS NODE UNREACHABLE ERRORS

V4.0

Jul 85

25.5.3

STARTNET,COM INCORRECTLY PARSES NODE ADDRESS

V4.0

Jul 85

25.5.4

STARTNET,COM FAILS TO CHECK FOR ALTPRI PRIVILEGE

V4.0

Jul 85

25.5.5

STREAM_LF

PARTNERS

V4,0

Sep 85

25.5.6

DECnet GIVES INCORRECT ERROR ON INVALID USER NAME

V4,1

Sep 85

25.5.7

PROXY ACCOUNT CHANGE

V4.0

25.5.8

RECEIVE BUFFERS AND STATIC ASYNCHRONOUS

FILE TRANSFER HANGS TO NON-VMS

DELAYED
LINES

Nov

Nov 85

25.5.9

RMS CANNOT ALWAYS

25,5.10

ACCESS VIOLATION RETURNED ON READ REQUEST

Jan 86

25,5.11

AREAS LEFT UNREACHABLE

Jan 86

25,5.12

ASYNCH

25,5.13

INVALID ALARM FROM DECnet

PARSE SYSSNET

Nov

LINE OR CIRCUIT PARAMETERS VANISH

Mar

Mar 86

25,5.14

DECnet

25,5.15

NODES

BVL

25.20.1

EVL EXITS WITH RESULTANT STRING OVERFLOW ERROR

V4.1

Nov 85

NCP

25.45.1

NCP SHOW KNOWN LOGGING ACCESS VIOLATION

V4.2

Mar 86

RTPAD

TFDRIVER

TMDRIVER

TUDRIVER

UP WHEN TIME

IS SET BACK

May 86

DIFFERENT AREAS ARE UNREACHABLE

May 86

25,65.1

CTERM

25.65.2

TOPS-20 TERMINAL PAUSE CHARACTER NOT REASSIGNABLE

25.65.3

TERMINAL CHARACTERISTICS NOT RESTORED

V4.3

Jul 86

25.65.4

REMOTE SET TERMINAL/PERMANENT MIGHT PAIL

V4.2

Jul

25.65,5

TOPS-10 TO VMS PROTOCOL ERROR

V4.1

Jul 86

31.0

DDDRIVER

HANGS
IN

DISK &

ESCAPE AND CTRL/E ECHOING

V4.1

Jan

V4,1

Jul

TAPE DRIVERS SECTION

31,10.1

TUS8 TIMES OUT WHEN /DATA CHECK=WRITE IS USED

v4.0

Sep 85

31.10.2

VAX-11/750 CONSOLE TUS58 OCCASIONALLY TIMES OUT

V4.1

Nov 85

31.50.1

INCORRECT POSITION AFTER ERROR RECOVERY

V4.1

May 86

31.50.2

INCORRECT DENSITY QUALIFIER YIELDS NO ERROR

V4,2

May 86

31.55.1

EOT BIT NOT PROPERLY SET IN DEVDEPEND

vé.1

May 86

31.55.2

END-OF-FILE NOT RECOGNIZED ON TE16

V4.1

Jul 86

31.65.1

DENSITY CHANGES ON MULTIVOLUME SET

V4.0

May 86

31.65.2

MULTIVOLUME BACKUP ON TMSCP DRIVES

V4.1

May

32,0

NET DRIVERS

SECTION

NETDRIVER

32,15.1

ACCESS VIOLATION WITH LARGE NETWORK BUFFER

V4.1

Nov 85

NODRIVER

32.20.1

DECnet LINES ENTER ON-SYNCHRONIZING STATE

V4,0

Nov 85

XDDRIVER

32.25.1

DEVICE FULL ERROR WHEN INITIALIZING DMP-11

V4.0

Jul 85

32,25.2

XDDRIVER LINK CANCELLATION CRASHES SYSTEM

V4.1

May 86

Component/

Sequence

Product

Number

Title of Article

XEDRIVER

32,30.1

VARIOUS

32.30.2

32.45.1

YODRIVER CORRUPTS NONPAGED POOL

YODRIVER

33.0

CTDRIVER

TTDRIVER

YCDRIVER

LPDRIVER

LTDRIVER

PADRIVER

XFDRIVER

EDIT/FDL

XEDRIVER

V4.0

Jan

VARIOUS PROBLEMS WITH XEDRIVER

V4.0

Jan

V4.0

Jul 85

PROBLEMS WITH

TERMINAL DRIVERS SECTION

RWAST STATE AFTER DEASSIGN OR HANGUP

va.1

Jan

33,5.2

REMOTE PROCESS

Va1

May

33.5.3

OUT-OF-BAND CHARACTER NOT CHECKED

V4.1

Jul

33,20.1

VT200 NOT

$DCDEF

V4.0

Jul

33,20.2

DMA NOT SET ON

LINES

V4,0

Jul 85

XON/XOFF

ENTERS AN RWAST STATE

DEFINED IN
DMF-32

33.20.3

DMF32

V4,0

Jan 86

33,20.4

SET TERMINAL/INQUIRE ON VT102

V4.2

Mar

33,20.5

TT$M_MBXDSABL IGNORED

V4,0

Mar 86

33,20.6

STATUS

V4.0

Mar 86

33,20.7

EXTRA CHARACTERS WITH TIMEOUT READ

V4.1

Mar

33,20,8

READ/VERIFY WITH CLEAR CHARACTER FROM FMS

V4,1

Mar 86

SLOW TO

PROCESS

RETURN FROM MODEM

HANGUP

33,20.9

PRAME SIZE CHARACTERISTIC

33,20,10

AUTOBAUDING WRITES

33,20.11

SECONDARY TRANSMITTED SIGNAL NOT SET ON

33,25.1

DMF32 REQUIRES CARRIER

LINE

NOT SET TO

0
DMF-32

va.1

May 86

V4.1

May 86

V4,1

Jul 86

V4.0

Mar

OTHER DRIVERS SECTION

34,16.1

PRINTER PROBLEMS AFTER POWER

V4,0

Nov

34.16,2

LCDRIVER CAUSING SYSTEM CRASHES

V4,0

Jul

34.20,1

SYSTEM~F-EXQUOTA

V4,0

Jul

34,20,2

UPPERCASE CHARACTER SUPPORT

V4.1

Jul

34,25.1

LAT SERVER AND DEVICE NAMES

34,25.2

LAT HOST RATING RESTRICTION

V4,1

Jan

34,40.1

V4,1

Jan

34.40.2

SYSTEMS COMMUNICATION SERVICES HANG

vd.1

May

34.54,1

PARITY ERROR WHEN

V4,0

Jan 86

35.0

EDIT/ACL

Mon/¥r

33,5.1

34,0

LCDRIVER

Operating

System

ERROR ON

VIRTUAL CIRCUIT HUNG

FAILURE

PRINTOUT

UNAVAILABLE

Nov 85

IN VC_FAIL STATE

LOADING MICROCODE FOR

DR32

EDITORS SECTION

35.5.1

EDIT/ACL DELETES ACE GRANTING ACCESS

V4.0

Sep

35.5.2

PROBLEM IN REPRESH

v4.0

sep 85

35.5.3

MISSING STATUS RETURN

V4.0

Sep

35.5.4

VARIOUS PROBLEMS WITH THE ACL EDITOR

Vi1

Jan

35.5.5

CURSOR POSITION INCORRECT AFTER LINE SPLIT

V4,1

Mar 86

35,5.6

INCORRECT PROTECTION ON JOURNAL FILE

V4.1

Mar

35,10.1

<RETURN> AND <CTRL/Z> RETURN TO MAIN MENU

va.1

Nov 85

LOGIC CAUSES ACCESS VIOLATION

40.0

Title of Article

FILE SYSTEMS AND RMS SECTION
va.1

40.2,2

PROBLEMS WITH XQP-GENERATED ACE
ERROR MESSAGE POSITIONING IS INCORRECT

V4.1

40.2.3

XQP-GENERATED ACE NOT ALWAYS ADDED

V4.1

40.5.1

CONVERT/RECLAIM MAY ACCESS VIOLATE

V4.0

40,5.2

CONVERT CAN INCORRECTLY REPORT DUP AND SEQ ERRORS

V4.0

40.5.3

CONVERT INCORRECTLY RETURNS RTL ERROR

V4.0

40.5.4

SIMULTANEOUS CONVERT OPERATIONS MIGHT FAIL

V4.1

P11AACP

40,10,1

MOUNT VERIFICATION FAILS FOR ODS-1 VOLUMES

V4.1

MOUNT

40,30.1

MOUNT ALLOCATES DEVICE TO PARENT PROCESS

V4,0

40,30.2

MOUNT/NOLABEL FAILS WITH BAD PARAMETER ERROR
MOUNTING MAGNETIC TAPES WITHOUT PROPER ACCESS

V4.1

40,30.3

V4.1

40,30,5

MOUNTING TAPE WITH ACCESSIBILITY CHARACTER
MOUNT IGNORES DEVICE ACCESS CONTROL LISTS

vd.1

MTAAACP

40.40.1

MTAAACP PROCESSES ANSI TAPES INCORRECTLY

V4.0

RMS

40,45.1

READ FROM SYSSOUTPUT FAILS

V4.0

40,45,2

COPY/OVERLAY FAILS IF DESTINATION WRITE-PROTECTED

V4.0

40.45.3

CONFUSION ON $CREATE USING SEARCH LISTS

va.0

40.45.4

RENAME RETURNS INCORRECT ERROR MESSAGE

V4,0

40,45.5

ACCESS CONTROL STRING PARSED INCORRECTLY

V4.0

40.45.6

FILE CORRUPTION WITH GLOBAL BUFFERS

V4,0

40.45,7

SYSSRMSRUNDWN RETURNS INCORRECT STATUS

V4.0

SEARCH LIST QUESTIONS

V4.0

40.45,9

REMOTE COMMAND PROCEDURES FAIL

V4.0

40,30.4

40,45.10

VERSION 4 COPY WILL NOT COPY VERSION 3 ISAM FILES

V4.1

40,45,11

RMS FILE PARSE PROBLEM WITH LEVEL 8 DIRECTORIES

V4.0

40.45.12

FILE LOCKED ERROR CONFUSION

V4.1

V4.0

40.45.8

40,45.13

FILESCAN DOCUMENTATION ERRORS

40.45.14

ERROR REPORTED FROM SYS$RMSRUNDOWN

V4.1

40.45.15

RMS BUGCHECKS DURING BATCH JOB DELETION

V4.1

40.45.16

RMS DOES NOT SEND MXV TO FCS FAL
APPEND PROBLEM WITH RMS EXTEND SIZE

vd.1

V4.1

40.45.18

SYS$SETDDIR ALTERS DEFAULT DIRECTORY ONLY

V4.1

40.45.19

LONG UICs TRUNCATED OVER NETWORK ACCESS

vd.1

40.45.20

RMS RECORD LOCK CONVERSION PROBLEMS

V4.1

40.45,21

RMS FAILS WITH RMS$ENQ/SS$_CVTUNGRANT

V4.2

40,45,17

45,0

RTL

45.1.1

RTL SECTION

VAX BASIC PROGRAMS RETURN AN INCORRECT ERL FOR
ERRORS

45.1,2

45.,1.3

50 AND 52

RENAME FAILS IF TARGET FILE ON REMOTE NODE

EMBEDDED BLANKS NOT PERMITTED IN UICs

V4.0

V4.1

Nov 85

V4.1

Jul 86

®E

CONVERT

40.2,1

ACL

Mmoo

Number

Operating
System

Product

Sequence

Component/

Component/
Product

Sequence
Number

55.0

ANALYZE

AUTHORIZE

copy

DEBUG

System

Mon/Yr

UTILITIES SECTION

55.5.1

ANALYZE/IMAGE REPORTS INCORRECT LINK DATE AND TIME V4,0

Jul 85

55.5.2

ANALYZE/ERROR/INCLUDE=CPU PROBLEM

V4.1

Jan 86
Jul 86

55.5.3

RECOVERED FILES HAVE INCORRECT BACKLINKS

V4.0

55.5.4

ERRORS

V4.1

Jul

55,5.5

ANALYZING ERRORS FOR RA81

ALTY

Jul

55.5.6

/INCLUDE & /EXCLUDE KEYWORD VALUES MISINTERPRETED

V4.2

Jul 86

55,10,1

AUTHORIZE HAS TROUBLE PARSING /<ACCESS> QUALIFIERS V4.0

Jul 85

55.,10.2

BACKUP

Operating

Title of Article

DURING BOOTSTRAP LOG

INCORRECT DATE/TIME

DISK

REVOKE/IDENTIFIER DOES NOT REMOVE UICS

V4.0

Jul 85

55,10,3

CLARIFICATION OF ADD/NETWORK

V4.0

Sep 85

55.10.4

AUTHORIZE AND DISKQUOTA DO NOT RETURN STATUS

V4.0

Sep 85

55.10,5

PROBLEM WITH SHOW/ID FOLLOWED BY MOD/ID

V4.0

Sep 85

55.10.6

DATE HANDLED IMPROPERLY BY /NOPWDEXPIRED QUALIFIER V4,0

Nov 85

55,10.7

WILDCARD SPECIFICATION NOT ALLOWED

V4.0

Nov 85

55.10.8

AUTHORIZE CAPITALIZES QUOTED STRINGS

V4.0

Nov 85

55,10,9

UIC

V4.0

Nov 85

[0,0]

IS RESERVED

55.,10,10

RUN/INPUT=FILE CAUSES AUTHORIZE TO HANG

V4.1

Nov 85

55.10.11

AUTHORIZE DOES NOT SUPPORT USE OF WILDCARDS

Va1

Nov 85

55,10.12

va.1

Mar 86

55.10,13

MISCELLANEOUS QUESTIONS ABOUT IDENTIFIERS

V4.1

Mar 86

55.10,14

MAIL RECORD REMAINS,

V4.1

55.10,15

PRIVILEGE CATEGORY MUST CONSIDER DEFAULT PRIVILEGE V4,1

May 86

USER REMOVED FROM UAF

Mar

55.20,1

PROBLEM BOOTING STANDALONE BACKUP

V4,0

Jul 85

55,20.2

NEGATIVE VERSION NUMBERS DO NOT WORK IN BACKUP

V4.0

Nov 85

55420,3

INCORRECT ACL ON CREATED DIRECTORIES

V4,0

Nov 85

55.20.4

NO END-OF-FILE CHECK

V4.0

Nov 85

55,205

INVALID QUALIFIERS ARE IGNORED

V4.1

Nov 85

55.20,6

IMAGE RESTORE OF ODS-1

V4.1

Nov 85

55.20,7

FILE SELECTION INAPPLICABLE IN INCREMENTAL RESTORE V4,1

Nov 85

55.20,8

FILES WITH MULTIPLE DIRECTORY ENTRIES

Jan 86

RESTORE /VERIFY

DISK FAILS

vé.1

55,20.9

LARGE ACLs

V4.1

Mar 86

55.20,10

TMSCP~CLASS TAPE CANNOT RESTART

V4.0

May

55.20.11

ENHANCE BACKUP TO DETECT DIRECTORY PROBLEMS

V4.1

Mar 86

55,20,12

INTERCHANGE DOES NOT SUPPRESS DIRECTORY COPYING

V4.0

May 86

55.20,13

OPCOM

V4.0

May

55.20,14

DENSITY CHANGES ON MULTIVOLUME SAVE

V4.0

May

55.20,15

BACKUP JOURNAL FILE CORRUPTION

V4.0

May 86

55.20,16

INCORRECT ERROR MESSAGE FROM

V4.2

May

CAUSE BACKUP TO ACCVIO

REPLY/ABORT FAILS

TO ABORT BACKUP
SET

BACKUP

55.35,1

EXPLICIT DIRECTORY COPY FAILS

V4.0

Nov 85

55.35,2

COPY FAILS WITH RMS MBC ERROR

vé.1

Nov

55.50,1

SET MODULE COMMAND TAKES TOO LONG

V4.0

Sep 85

55.50,2

COMMA LISTS ON

V4.1

Sep 85

55.50,3

INTERNAL DEBUG ERROR ON

55,50.4

PROBLEM WITH SCREEN WIDTH LARGER THAN

55.50,5

DEPOSIT NOT ALLOWED

V4.1

Nov 85

V4.1

Jan

DEBUG FAILS TO PROCESS FILES

V4.0

Jan 86

55.50,6

INCORRECT SCREEN SIZE

V4.2

Mar 86

55.50,7

DECLARE COMMAND IN C

V4.2

Mar

RESERVED OPERAND FAULT

IN SCREEN MODE

132

Component/

Sequence

Product

Number

Title of Article

System

55.50.8

EVALUATE/HEX NUMBER IN PL/I

V4.2

55.50.9

DEBUGGER RESERVED OPERAND FAULT WHILE USING PL/I

V4.2

Jul 86

55.65.1

DIRECTORY OUTPUT MISSING TOTAL LINE

V4.0

Jul 85

55.65.2

DIRECTORY MAY DISPLAY NONEXISTENT FILES

V4.0

Jul

DISK QUOTA

55,7041

DISK QUOTA ERROR CAUSED BY

V4.0

DUMP

55.85.1

PROBLEM WITH 8-BIT

vd.1

EXCHANGE

55.90.1

RT-11 MAGNETIC

55,90,2

EXCHANGE

55.90,3

EXCHANGE PRODUCES INTERNAL

HELPTEXT

55,961

INCORRECT EXAMPLE

INITIALIZE

56.5.1
56.5.2

INSTALL

56.10.1

INABILITY TO

LIBRARIAN

56.15.1

PROBLEM

LINKER

MAIL

MONITOR

PURGE

PROPAGATION

CHARACTERS

PRINTERS

V4.1

V4.0

V4.1

INITIALIZE/INDEX:BLOCK=N NOT RECOGNIZED

V4.0

INITIALIZE

V4.1

V4.0

DOES

TAPE SUPPORT
NOT HANDLE

DOES

LONG RT-11

LOGIC

ERROR

175

MAIL COMMAND

NOT USE SOFTWARE

INSTALL

RECORDS

EXECUTABLE

DECOMPRESSING A

BAD BLOCK AREA

IMAGES

LIBRARY

56.20.1

LINKER OPEN FILE

V4.0

56420,2

LINKER REJECTS VALID FILE NAMES IN OPTIONS FILES

V4.0

5642043

VERSION 4,0

V4.0

56.30.1

MAIL CANNOT RUN ON

56.30.2

PRINTING

56.30.3

MAIL REPORTS

56,30,

MAIL COMMAND COMPRESS

LIMIT

IMAGES

IN MAIL

PROBLEM

LARGER THAN VERSION 3.0 IMAGES

A GIGI

TERMINAL

IGNORES PAGE ATTRIBUTES

INCORRECT ERROR ON

DOES

LOCKED DISK

NOT RECLAIM SPACE

V4.0

V4.1

56430.5

PROBLEMS WITH TERMINAL SET TO SCOPE/PAGE=0

V4.1

56.30.6

MAIL SENDS

V4.1

56.30,7

MAIL ERROR SENDING NONSPAN

FILES

V4.1

56.30.8

PASSWORD OF

STRING NOT MASKED

V4.0

V4.1

V4.2

RUNOFF OUTPUT

ACCESS

FILES

CONTROL

INCORRECTLY

56.30,9

MAIL ALLOWS BAD FORWARDING ADDRESS

56,30,10

MAIL SCROLLS

56.30,11

MAIL ATTACH/PARENT COMMAND FAILS

V4.2

56,30,12

REMOTE

V4.2

INCORRECTLY WITH

FORWARDING CAN CAUSE

LONG

LINES

MAIL TO HANG

V4.0

PROBLEMS WITH VIRTUAL MEMORY

va.1

56.40.4

PROBLEM WITH XQP DATA

V4.1

56.40.5

INTERVAL

V4.1

56.52.1

PURGE CAN

56.52.2

PURGE HANDLES RELATED FILES

56,7541

56.40.1

FOREIGN

56,40,2

MONITOR'S

56.40.3

TERMINAL SUPPORT

DOES

VIRTUAL MEMORY USAGE

DOES

NOT WORK

NOT WORK
GROWS CONTINUOUSLY

DOCUMENTED

INCORRECTLY DELETE FILES

DISPLAYS

CONTROL

INCORRECTLY

CHARACTERS

IMPROPERLY

V4.0

vé.1

V4.0

ASCII

OWNER

Mon,