VAX DEC/CMS
VERSION 2.2
RELEASE NOTES
Release 2.2 of DEC/CMS is a maintenance release, containing
bug fixes and documentation updates. These release notes
contain descriptions of the changes for both 2.1 and 2.2.
Disk requirements for V2.2 of DEC/CMS are as follows: 4500
blocks of free disk space needed during installation; 1800
blocks are used after installation.
1 Bug Fixes for 2.2 . . . . . . . . . . . . . . . . . 1
1.1 Lost lines of text . . . . . . . . . . . . . . . . 2
1.2 Reference copy incorrectly deleted . . . . . . . . 2
1.3 Create library without access privileges causes
crash . . . . . . . . . . . . . . . . . . . . . . 2
2 Problems identified in V2.2 . . . . . . . . . . . . 3
2.1 Resource exhaustion during library transactions . 3
2.2 Virtual memory exhaustion in callable interface
usage . . . . . . . . . . . . . . . . . . . . . . 3
2.3 Deletion of history control records . . . . . . . 3
3 Bug Fixes for V2.1 . . . . . . . . . . . . . . . . . 3
3.1 Concurrent Reservations . . . . . . . . . . . . . 3
3.2 Long History Lines . . . . . . . . . . . . . . . . 4
3.3 CMS SHOW GROUP/CONTENTS=ALL . . . . . . . . . . . 4
3.4 The CMS /MERGE Qualifier . . . . . . . . . . . . . 4
3.5 Callable Routines . . . . . . . . . . . . . . . . 4
3.6 Diagnostic Messages . . . . . . . . . . . . . . . 4
4 Corrections to the VAX DEC/CMS Reference Manual . . 4
4.1 Removal of /CONTENTS qualifier . . . . . . . . . . 5
4.2 Inclusion of GENERATION in INSERT command . . . . 5
4.3 Inclusion of wildcard file specification . . . . . 5
4.4 V1 Library Conversion ACLs . . . . . . . . . . . . 5
4.5 Removal of "remark" field on the ANNOTATE command 5
4.6 Incorrect parameters for conversion utility . . . 5
5 Corrections to the VAX DEC/CMS Callable Interface
Manual . . . . . . . . . . . . . . . . . . . . . . . 6
5.1 CMS$SHOW_GENERATION return code . . . . . . . . . 6
5.2 Reference copy parameter needed in callback
routine . . . . . . . . . . . . . . . . . . . . . 6
Page 2
1 Bug Fixes for 2.2
The following changes have been made in DEC/CMS V2.2:
1.1 Lost lines of text
Under certain conditions (large files with heavy variant activity
involving large blocks of text added and deleted) lines of text
were getting lost.
There was no sign of the error at the moment that it occurred.
In some cases, a subsequent FETCH or RESERVE would detect the
error as a checksum error and issue the BADCRC message. In other
cases there was no indication that the output of RESERVE was
different from the input to the previous REPLACE, except through
differences.
This problem occurred only if all three of the following
conditions were met:
1. The element contained a variant line of descent.
2. The element was large enough to exceed the capacity of an
internal buffer.
3. A very large change of at least several hundred lines was
made.
The buffer holds at least 800 data and control records, or 20,000
characters. Even if all three conditions were true, the problem
would only appear if certain lines appeared at certain places in
that large internal buffer.
The CMS development group is aware of fewer than ten instances of
the problem. The cause of the problem was identified to be in
code that had not been changed since CMS V1.
This problem has been fixed in V2.2.
1.2 Reference copy incorrectly deleted
When an element file was deleted, the reference copy was not
always deleted properly.
This problem has been fixed in V2.2.
Page 3
1.3 Create library without access privileges causes crash
An attempt to create a CMS library without having the correct
access privileges caused an access violation.
This problem has been fixed in V2.2.
2 Problems identified in V2.2
The following problems have been identified in DEC/CMS V2.2:
2.1 Resource exhaustion during library transactions
A CMS library may be left in an inconsistent state if resources
become exhausted during library transactions. The most common
exhausted resources are disk space and disk quota. This problem
typically occurs when users write to their library, i.e., replace
a file, or make a reservation.
This problem is very visible, and is usually signaled by an error
message. The best way to avoid this problem is to insure that
quotas and resources are adequate for all users. Section C.3 of
the CMS Reference Manual identifies several quota requirements.
2.2 Virtual memory exhaustion in callable interface usage
There is a problem in the internal allocation of virtual memory
which may cause virtual memory to become fragmented and exhausted
when using the callable interface. This problem may show up, for
example, in doing a large number of CMS$FETCH calls.
2.3 Deletion of history control records
If a file is reserved with the /HISTORY option, CMS will go into
an infinite loop during replacement if one of the history control
records that bracket the history section has been deleted during
editing.
In the event of a deletion of either the beginning or ending
history control records, the user should replace it with a copy
of the remaining one, since they are identical.
We plan to address these problems in subsequent releases.
Page 4
3 Bug Fixes for V2.1
The following changes have been made in DEC/CMS V2.1:
3.1 Concurrent Reservations
In V2.0, multiple, concurrent reservations could result in the
loss of some reservations if the elements were not replaced in
the reverse order in which they were reserved. Note that this
caused a loss of reservations, not of elements.
This problem has been corrected in V2.1.
3.2 Long History Lines
History lines that are longer than 132 characters are now split
into multiple lines. This avoids compiler errors that occurred
when they were longer than 132 characters.
3.3 CMS SHOW GROUP/CONTENTS=ALL
In V2.0, not all of the files assigned to all groups were shown
when the user issued the CMS SHOW GROUP/CONTENTS=ALL command.
This problem has been corrected in V2.1.
3.4 The CMS /MERGE Qualifier
There was a problem when a FETCH or RESERVE done with the /MERGE
qualifier was followed by another FETCH or RESERVE transaction.
Memory was not re-initialized in the non-merge transaction and
this resulted in failure of the second transaction.
There was also a problem if variants which deleted the same lines
of text were merged. Lines of data were included in the output
file that should not have been there.
These problems have been corrected in V2.1.
3.5 Callable Routines
The callable SHOW routines (CMS$SHOW_CLASS,...) now return a
value of CMS$_NORMAL as documented in the Callable Interface
Manual, rather than SS$_NORMAL.
Page 5
3.6 Diagnostic Messages
The CMS command SHOW RESERVATIONS [element-expression] now
generates the correct message when the element you specify exists
but is not reserved.
4 Corrections to the VAX DEC/CMS Reference Manual
4.1 Removal of /CONTENTS qualifier
On page 3-6, Section 3.3.3, the /CONTENTS qualifier should be
removed from the CMS SHOW ELEMENT command.
4.2 Inclusion of GENERATION in INSERT command
On page 3-7, Section 3.4.2, the examples showing user input in
red should include the word GENERATION after the CMS INSERT
command. For example, the first item should be:
$ CMS INSERT GENERATION INIT.FOR INTERNAL_RELEASE.
4.3 Inclusion of wildcard file specification
On page 8-9, Example 1, which shows user input in red, should
include the target wildcard file specification, ie:
$ CMS COPY ELEMENT *.* *.* /LIBRARY=[PROJLIB] "loading
elements"
4.4 V1 Library Conversion ACLs
The following note should be added to Notes on Library Conversion
on page A-2:
5. All ACLs on V2 library files should be checked after
conversion to assure that they are consistent with those for
the V1 library and updated if not.
4.5 Removal of "remark" field on the ANNOTATE command
On page 8-2, on the CMS ANNOTATE command, the "remark" field
should be removed, that is, the command should appear as follows:
$ CMS ANNOTATE element-expression
Page 6
4.6 Incorrect parameters for conversion utility
On page B-1, Section B.1, the description of the parameters on
the command line is incorrect. The command parameters P2 through
P4 should be described as follows:
P2: Output file specification; the default is CONVERTED.COM.
P3: Summary file specification; the default is CONVERTED.SUM.
P4: For library specific conversion; the directory
specification
of the CMS library that the command file works upon.
5 Corrections to the VAX DEC/CMS Callable Interface Manual
5.1 CMS$SHOW_GENERATION return code
On page 2-105, delete CMS$_NOGEN as a return code for
CMS$SHOW_GENERATION.
5.2 Reference copy parameter needed in callback routine
In Appendix B, which contains examples using the callable routine
CMS$SHOW_ELEMENT, the declaration for the the callback routine
does not contain the reference_copy parameter. You should change
the examples to include this parameter.
For example, the FORTRAN code on page B-8 should include
reference_copy as the next to last parameter:
50 END
INTEGER*4 FUNCTION OUTPUT_ROUTINE (FIRST_CALL,LIBDB,USER_PARAM,
1 ELEMENT_ID,REMARK_ID,HISTORY_ID,NOTES_ID,POSITION,ACCESS,
1 REFERENCE_COPY,GROUP_LIST_ID)
The examples for each of the programming languages in Appendix B
should be corrected to include reference_copy as a parameter for
the callback routine. The text description of the callback
routine parameters for CMS$SHOW_ELEMENT on pages 2-96 and 2-97 is
correct.