VAX DEC/CMS
VERSION V3.2-00
RELEASE NOTES
11 April 1989
Page ii
CONTENTS
1 Introduction . . . . . . . . . . . . . . . . . . . . 1
2 Computer Based Training . . . . . . . . . . . . . . 2
3 New Functionality in This Release . . . . . . . . . 4
3.1 The /[NO]DECWINDOWS qualifier on the DCL CMS
command . . . . . . . . . . . . . . . . . . . . . 4
3.2 CMS now supports the License Management Facility
(LMF) . . . . . . . . . . . . . . . . . . . . . . 4
3.3 File Revision Time Options . . . . . . . . . . . . 4
4 Problems Resolved in This Release . . . . . . . . . 7
4.1 Misleading messages from SET ACL . . . . . . . . . 7
4.2 Incorrect event handling on REPLACE . . . . . . . 7
4.3 REPAIR access did not allow VERIFY . . . . . . . . 7
4.4 GENSTKOVF fatal error . . . . . . . . . . . . . . 7
4.5 Event handling on certain commands . . . . . . . . 8
4.6 REMARK/UNUSUAL . . . . . . . . . . . . . . . . . . 8
4.7 Return status in LDB . . . . . . . . . . . . . . . 8
4.8 CMS$SHOW_LIBRARY incorrectly required an output
routine. . . . . . . . . . . . . . . . . . . . . . 8
4.9 CMS$CMS not resignaling unrecognized signals . . . 8
4.10 Virtual memory leaks . . . . . . . . . . . . . . . 8
4.11 CMS$DIFFERENCES sometimes gives CMS$_QUALCONFLICT 9
4.12 Problem with sequenced elements . . . . . . . . . 9
4.13 Illegal data records in element data file . . . . 9
4.14 Callable routines not returning CMS$_USERERR . . 10
4.15 Creating elements from illegal files . . . . . . 10
5 Known Problems and Restrictions - CMS Proper . . . 11
5.1 CMS V2 should not be used on CMS V3 libraries . 11
5.2 DELETE GENERATION/ARCHIVE and sequenced files . 11
5.3 Callback Routine Parameters . . . . . . . . . . 11
5.4 Merging Binary Files . . . . . . . . . . . . . . 11
5.5 Depth of Library Directories . . . . . . . . . . 11
5.6 Wildcard Indicator in Notification Messages . . 11
5.7 Restriction on CMS$FETCH_OPEN and Library Search
Lists . . . . . . . . . . . . . . . . . . . . . 12
5.8 Restriction on DIFFERENCES and Library Search
Lists . . . . . . . . . . . . . . . . . . . . . 12
5.9 Input File Deletion . . . . . . . . . . . . . . 12
5.10 COPY ELEMENT with Many Elements/Generations . . 12
5.11 COPY ELEMENT/LIBRARY Messages . . . . . . . . . 13
5.12 Reference Copy Messages . . . . . . . . . . . . 13
5.13 VERIFY/RECOVER on Valid Library . . . . . . . . 13
5.14 SET ACL/DELETE with Nonexistent Identifier . . . 13
5.15 Syntax Errors on SET ACL and SHOW ACL . . . . . 13
5.16 Severity of Summary Messages . . . . . . . . . . 13
5.17 Parameters on Negated Qualifiers . . . . . . . . 14
6 Known Problems and Restrictions - DECwindows
Interface . . . . . . . . . . . . . . . . . . . . 15
6.1 Access violations when virtual memory is
exhausted . . . . . . . . . . . . . . . . . . . 15
6.2 Problem with horizontal scrolling in views . . . 15
6.3 Text insertion cursor . . . . . . . . . . . . . 15
6.4 Help Key will not bring up the Help Overview
frame . . . . . . . . . . . . . . . . . . . . . 15
Page iii
6.5 Cancel Operation Button response is not immediate 15
6.6 Modify Library has an unused text widget . . . . 16
6.7 Create Element/Class/Group do not allow selection 16
6.8 Maximum of 65,536 characters can be copied to the
Clipboard . . . . . . . . . . . . . . . . . . . 16
6.9 Maximum of 256 characters on a line in a view . 16
6.10 Help Dialog Box . . . . . . . . . . . . . . . . 16
6.11 DECW$DISPLAY Logical Name . . . . . . . . . . . 16
6.12 Messages from some operations don't appear in
message boxes . . . . . . . . . . . . . . . . . 16
6.13 Command error checking is not robust . . . . . . 17
7 Installation Procedure Requirements . . . . . . . 18
8 User Account Quotas and Privileges . . . . . . . . 19
9 Library Conversion . . . . . . . . . . . . . . . . 20
10 Documentation Errata . . . . . . . . . . . . . . . 22
10.1 CMS$SHOW_RESERVATIONS Callback Parameters . . . 22
10.2 CMS$SHOW_ACL needs CMS$_USERERR documented . . . 22
10.3 Width specification for DIFFERENCES . . . . . . 22
10.4 File revision time features are not yet
documented . . . . . . . . . . . . . . . . . . . 22
Page 1
1 Introduction
These are the release notes for VAX DEC/CMS V3.2-00. It
introduces the DECwindows interface for CMS and provides
other new features beyond those available in V3.0 and V3.1,
as listed in Section 3 below.
You can invoke the CMS DECwindows interface by typing the
CMS/DECWINDOWS command at the DCL prompt. To successfully
run the CMS DECwindows interface, the DECW$DISPLAY logical
name must point to an accessible and appropriately
configured system. You can still invoke the CMS
command-line interface by issuing the CMS command with the
/NODECWINDOWS qualifier (default) at the DCL prompt.
The following sections contain information about computer
based training, requirements for installing and using CMS,
information about library conversion, restrictions and
outstanding problems, and a list of documentation errors.
NOTE
The DECwindows interface in this release requires a
minimum of VMS V5.1 running DECwindows V5.1. CMS
proper requires a minimum of VMS V5.0.
Before installing and using any version of CMS V3
(V3.0, V3.1, or V3.2) on a system that is using any
version of CMS V2 (V2.0, V2.1, V2.2, or V2.3), you
MUST use the (CMS V2) VERIFY command on ALL existing
(CMS V2) libraries and correct any reported problems
(the CMS VERIFY/REPAIR command should be used if
necessary) before proceeding.
CMS V2 libraries which do not verify correctly may
not be convertible to V3. It is extremely important
to verify ALL V2 libraries BEFORE V3 is installed,
as the V3 installation procedure will remove CMS V2
from the system. This is a precaution to prevent
the accidental corruption of CMS V3 libraries by
operating on them with CMS V2, as CMS V2 does not
recognize V3 libraries.
CMS V3 will properly recognize V2 libraries, and
will not operate on them. For more information on
library conversion please refer to the "Library
Conversion" section in this document.
You do not need to install CMS V3.0 or V3.1 prior to
installing CMS V3.2. CMS V3.2 is also capable of
converting CMS V2 libraries to CMS V3 format.
Page 2
2 Computer Based Training
Computer based training is available for VAX DEC/Code
Management System, VAX DEC/Module Management System and VAX
Language-Sensitive Editor.
To order the "Using VAX DEC/CMS and VAX DEC/MMS" computer
based training (CBI) or the "Using the VAX
Language-Sensitive Editor" (CBI) please call the most
convenient location listed below. Information on other
training available from Digital Equipment Corporation in
CBI, lecture/lab and other formats can also be obtained at
these numbers.
Order numbers and media for these courses are:
Using VAX DEC/CMS Using the VAX Language
Media and VAX DEC/MMS Sensitive Editor
RX50 EY-8267E-RX EY-3491E-RX
1600bpi EY-8267E-MT EY-3491E-MT
TK50 EY-8267E-TK EY-3491E-TK
In the US and Canada call toll free 1-800-332-5656.
In Europe contact your local training center at the
following telephone numbers:
Training Center Country Telephone
Barcelona Spain [34] (93) 2035200
Brussels Belgium 02/242.50.95
Copenhagen Denmark +45-2-88.96.66
Evry France 60.76.50.05
Geneva Switzerland [41] (+22) 31 56 55
Highfield England, UK [44]-(734)-868008
Nieuwegein Holland [31]-(3402)-65654
Madrid Spain [34] (91) 7347002
Manchester England [44]-061-865-0831
Milan Italy [39]-(2)-617961
Munich Germany [49]-(89)-95072281
Reading England, UK [44]-(734)-868711
Zurich Switzerland [41]-(1)-3120555
In the General International Area contact training centers
at the following telephone numbers:
Training Center Location Telephone
Digital Equipment Corp Brisbane [61] (07) 221 6000
(Australia) Canberra [61] (62) 47 3654
Melbourne [61] (03) 895 9595
Sydney [61] (02) 412 5252
Dig Eq do Brasil Ltda Rio de Janeiro [55] (21) 297-1122
Page 3
Sao Paulo [55] (11) 575-0088
Digital Eq of Canada Montreal (514) 340-7811
Ottawa (613) 723-3634
Toronto (416) 597-3429
Vancouver (604) 276-6902
Digital Eq Caribbean Puerto Rico (809) 754-7575
Digital Eq Hong Kong Wanchai [852] (5) 861 4283
Nihon Digital Eq Corp Osaka [81] (06) 206-2771
(Japan) Tokyo [81] (03) 989-7180
Digital Eq de Mexico Mexico (905) 687-6671
Digital Equipment Corp Auckland [64] (09) 393 940
(New Zealand)
Digital Eq Corp PRC Beijing [86] (1) 890721
Digital Eq Corp Taiwan Taiwan [886] (2) 776 8888
Digital Eq Singapore Singapore [65] 336 3588
Page 4
3 New Functionality in This Release
3.1 The /[NO]DECWINDOWS qualifier on the DCL CMS command
The DCL CMS command now accepts a new qualifier:
/DECWINDOWS - Specifies that the CMS DECwindows
interface should be invoked.
/NODECWINDOWS - Default, specifies that the CMS
DECwindows interface should not be
invoked (and the command-line
interface should be used instead).
3.2 CMS now supports the License Management Facility (LMF)
3.3 File Revision Time Options
To allow the user to specify options for the revision time
of files retrieved from CMS libraries, a new qualifier has
been added on the CMS commands CREATE LIBRARY and MODIFY
LIBRARY:
/REVISION_TIME=option
where valid options are:
ORIGINAL - Default, specifying that the original
revision time of files placed in a CMS
library should be restored unchanged
upon their retrieval. That's how CMS
has always behaved until now.
STORAGE_TIME - Specifies that the time when a file was
stored in a CMS library (through a CREATE
ELEMENT or REPLACE operation) should be
substituted for its original revision
time upon retrieval or when queried.
As mentioned in the description of the ORIGINAL option
above, our handling of the file revision time upon retrieval
has always been the same. One important thing did change
however between CMS V2.3 and V3.0: reference copy files are
now being actually fetched from the library rather than
created through an RMS COPY or RENAME operation directly
from the files being stored. Thus, in CMS V3.0 and V3.1,
their original revision time is being preserved rather than
reset to the storage time.
While the current, V3 behavior is generally considered to be
correct, there are cases where the V2 handling of file
revision time is more desirable. This in particular
Page 5
pertains to MMS builds. Please note that the new
/REVISION_TIME qualifier allows the user to control the
revision time of any files retrieved from a CMS library, and
not just of reference copy files.
The CMS SHOW LIBRARY/FULL command now shows the current
setting of the file revision time option. Also, the CMS
SHOW GENERATION/FULL shows the revision time consistently
with the setting, i.e., the original file revision time or
the storage transaction time.
Corresponding additions have been made to the
CMS$CREATE_LIBRARY and CMS$MODIFY_LIBRARY callable routines
as well as to the CMS$SHOW_LIBRARY routine's callback
routine. All three now have an additional flag argument
added at the end of each respective argument list.
If this additional flag argument, revision_time (type:
longword_signed, access: read, mechanism: by reference),
is omitted from a CMS$CREATE_LIBRARY call, or if a value of
0 (zero) is passed, then the original file revision time is
used. A value of 1 is used to specify that the storage time
of files should be substituted for their revision time upon
retrieval.
If the revision_time argument is omitted from a
CMS$MODIFY_LIBRARY call, then the current setting of the
revision time option remains unchanged. By passing a value
of 0 (zero), you specify that the original file revision
time should be used, and by passing a value of 1, that the
file storage time should be used for the revision time upon
retrieval.
The additional revision_time parameter of the
CMS$SHOW_LIBRARY routine's callback routine returns (by
reference) a value of 0 (zero) for the original file
revision time setting, and a value of 1 for the storage time
setting of the revision time option.
Similarly to the SHOW GENERATION/FULL command,
CMS$SHOW_GENERATION's callback routine returns the storage
time for the revision time if /REVISION_TIME=STORAGE_TIME is
in effect.
Corresponding additions have also been made to the CMS
DECwindows interface.
Whenever the MODIFY LIBRARY/REVISION_TIME command is issued
to change the setting of the file revision option for a
library that has a reference copy directory, all reference
copy files are automatically re-fetched with their correct
revision times.
Because of the CMS V3.2 documentation production cycle, the
above new revision time features can only be documented in
Page 6
the Release Notes. Their description will be included in
the CMS documentation in future releases.
Page 7
4 Problems Resolved in This Release
4.1 Misleading messages from SET ACL
Previous versions of CMS would issue misleading messages if
the SET ACL command was used, and the user did not have
EXECUTE access to that command. The first message stated
that the user did not have EXECUTE access to the SET ACL
command, but was missing the name of the object whose ACL
was being modified. The second message incorrectly stated
that CMS could not find the object. This has been corrected
to issue the proper messages.
4.2 Incorrect event handling on REPLACE
Previous versions of CMS contained two errors in REPLACE
event handling. First, event handling was being done
regardless of whether the operation succeeded or failed.
Event handling should only occur when the operation
succeeds. Second, event handling for the REPLACE command
(as opposed to the elements being replaced) was only being
done once for multiple replacements. It should be done once
for each element successfully replaced. These problems have
both been corrected.
4.3 REPAIR access did not allow VERIFY
REPAIR access in an ACL now allows you to do either a VERIFY
or a VERIFY/REPAIR. Previous versions of CMS required the
VERIFY access type before a simple VERIFY operation was
allowed.
4.4 GENSTKOVF fatal error
It was possible, under rare circumstances, for earlier
versions of CMS to create an element data file containing
generation edits that were nested more deeply than the
maximum allowed. Subsequent attempts to fetch or reserve
such an element would result in the "GENSTKOVF, generation
stack overflow" fatal error.
This problem has been corrected in this release in two ways.
First, the size of CMS's internal generation stack has been
increased by one, allowing any elements that had reached the
GENSTKOVF state to be successfully fetched. Second, CMS
will now detect during the REPLACE operation that the
resulting element data file would contain too many nested
generation edits, and disallow the REPLACE from completing.
The message "GENTOODEEP, generation edits are nested too
deeply" will be issued in such cases.
Page 8
Corrective action for GENTOODEEP is to use the DELETE
GENERATION command to delete old or unneeded generations,
then enter the REPLACE command again. Alternatively, you
can use the reserved generation to create a new element.
The generation contained in the old element can then be
unreserved.
4.5 Event handling on certain commands
The following commands were not having their ACLs checked
for event handling: MODIFY GENERATION, REMOVE GENERATION,
and SET ACL when /OBJECT_TYPE=LIBRARY was specified. Event
handling now occurs as expected on these commands.
4.6 REMARK/UNUSUAL
The /UNUSUAL qualifier on the REMARK command was until now
ignored by CMS.
4.7 Return status in LDB
The return status was not being placed in the second
longword of the library data block after calling
CMS$DIFFERENCES. This bug was introduced in CMS V3.0. This
has been corrected.
4.8 CMS$SHOW_LIBRARY incorrectly required an output routine.
The output routine argument is now again optional, as
documented.
4.9 CMS$CMS not resignaling unrecognized signals
CMS$CMS was calling the user-specified routine for signals
it didn't recognize. It now resignals instead.
4.10 Virtual memory leaks
A few virtual memory leaks have been eliminated. They were
primarily affecting binary file access and the
CMS$SHOW_GENERATION routine.
Page 9
4.11 CMS$DIFFERENCES sometimes gives CMS$_QUALCONFLICT
The CMS$DIFFERENCES callable routine would sometimes give a
CMS$_QUALCONFLICT error when the nooutput argument was
specified. This has been corrected.
4.12 Problem with sequenced elements
If an element was created using a non-VFC file (that is, a
file with a record format other than VFC), and a subsequent
generation was created using a VFC file with a 0 or 2 byte
header (what CMS calls a "sequenced" file), the element
would become corrupted. Such corruption can be identified
by extra data appearing in fetched copies, usually at the
beginning of each record.
This problem has been corrected such that it will no longer
occur, as long as the element had not been previously
corrupted. However, previously corrupted elements cannot be
repaired by CMS. VERIFY will detect these problems and
issue a SEQMISMAT error. VERIFY/REPAIR will correct any
other problems that may exist in the element, but it will
not correct this problem, as indicated by the NOREPSEQDATA
message. Under these circumstances a backup copy of the
element should be used.
4.13 Illegal data records in element data file
Previous versions of CMS could generate an illegal element
data file under certain circumstances. If a record read in
from an input file was 249*n-1 characters long, where n is 2
or greater, CMS would create an illegally formatted data
record. Such a record would cause CMS to bugcheck with an
ILLDATREC error when the element was fetched.
This error has been corrected so that newly created elements
will not have this problem. In addition, VERIFY and
VERIFY/REPAIR will detect and correct the problem in
existing element data files. The error VERILLDATREC from
VERIFY indicates that an element contains one or more
illegally formatted data records. Using VERIFY/REPAIR on
such an element will correct those records, as indicated by
the REPILLDATREC message.
Note that if two or more consecutive records were corrupted,
REPAIR will concatenate them into one record, as it is
unable to determine the boundary between them. Such cases
may be indicated by the presence of a BADCRC error from
VERIFY, in addition to the VERILLDATREC error. These will
need to be corrected manually by reserving the element and
separating the affected records. If no BADCRC error is
seen, it is likely that the element has been repaired
correctly, although this should be verified by manual
Page 10
inspection.
4.14 Callable routines not returning CMS$_USERERR
Starting with CMS Version 3.0, the callable routines that
could return a value of CMS$_USERERR if a user-supplied
input or output routine returned an error value to CMS,
stopped doing so. This has been fixed.
4.15 Creating elements from illegal files
Previous versions of CMS would allow elements to be created
from certain types of illegal files. Namely, if a file
contained a record longer than the maximum allowed for that
record format, and the file had characteristics causing it
to be handled using record I/O, CMS would not detect any
problems and would create the element. Elements with this
problem could not be fetched, because RMS could not handle
the illegal record size.
This has been corrected so that CMS will detect a record
with an illegal size, and issue an error. The illegal file
will not be placed in the CMS library.
Page 11
5 Known Problems and Restrictions - CMS Proper
5.1 CMS V2 should not be used on CMS V3 libraries
CMS V2 attempts to operate on a CMS V3 library, despite
having incompatible formats. This may result in a corrupted
V3 library.
5.2 DELETE GENERATION/ARCHIVE and sequenced files
An archive file may not be created correctly by the CMS
DELETE GENERATION/ARCHIVE command if it is performed on
generations that have been created from sequenced files.
5.3 Callback Routine Parameters
CMS$CREATE_LIBRARY, CMS$MODIFY_LIBRARY, and callback output
routines for CMS$SHOW_GENERATION, CMS$SHOW_GROUP, and
CMS$SHOW_RESERVATIONS are called with additional parameters.
Applications written in BASIC, DIBOL, or any other language
which performs run-time argument count checking, will have
to be updated for use with this version of CMS.
5.4 Merging Binary Files
Merging of binary files, while allowed, will usually not
produce meaningful results.
5.5 Depth of Library Directories
CMS libraries cannot be in 8th-level directories, since the
first CREATE ELEMENT attempt will be unable to create a
subdirectory. CREATE LIBRARY and CONVERT LIBRARY will
detect this condition and signal an error.
5.6 Wildcard Indicator in Notification Messages
The history line sent to the CMS event handler and seen in
notification messages will contain the letter 'W' after the
transaction time field if the transaction resulted from a
wildcard operation. This information should be suppressed,
as it is by the SHOW HISTORY command.
Page 12
5.7 Restriction on CMS$FETCH_OPEN and Library Search Lists
CMS$FETCH_OPEN, the callable routine that begins a
line-by-line fetch transaction, cannot be used with a
library search list. The directory argument may not contain
wildcard characters, nor may it be a comma list of directory
specifications, nor may it be a search list logical name.
5.8 Restriction on DIFFERENCES and Library Search Lists
The following restrictions apply to the CMS DIFFERENCES
command when used with a CMS library search list.
If both file_1 and file_2 are element generation
specifications, then both of the elements must reside in the
same library of the library search list.
CMS DIFFERENCES will emit %CMS-E-NOFETCH (or other messages
returned by CMS$FETCH_OPEN) if it cannot locate a specified
element generation. In a library search list, this may
occur if one or both of the specified elements do not exist
in the first library. These messages will be issued for
each library of the library search list in which the element
is not found. The exact sequence of such messages depends
on the values of the /OCCLUDE qualifier. In such cases, a
%CMS-E-NOFETCH message may be followed by a %CMS-S-IDENTICAL
or %CMS-W-DIFFERENT message. The latter message indicates
the actual status of the operation, whereas the intervening
%CMS-E-NOFETCH messages are a side-effect of the library
search list traversal.
The same considerations apply to the callable routine,
CMS$DIFFERENCES. CMS$DIFFERENCES uses the callable fetch
routines, CMS$FETCH_OPEN, CMS$FETCH_GET, and
CMS$FETCH_CLOSE. Conditions may be signaled from these
routines during the operation of CMS$DIFFERENCES.
5.9 Input File Deletion
If CMS is unable to delete the input file after a CREATE
ELEMENT or REPLACE operation, no message will be issued to
inform the user of the problem.
5.10 COPY ELEMENT with Many Elements/Generations
Using the COPY ELEMENT command to copy either a large number
of elements or an element with a large number of generations
may cause CMS to fail with an error diagnostic.
Page 13
5.11 COPY ELEMENT/LIBRARY Messages
When the /LIBRARY qualifier is used with the COPY ELEMENT
command, CMS will emit CMS-I-LIBIS, CMS-I-LIBINSLIS, and
CMS-I-LIBREMLIS diagnostics as it references the specified
library. The current default library context is not
modified.
5.12 Reference Copy Messages
When using CMS library reference copies, certain file system
related messages, such as RMS-F-DEV or RMS-E-PRV, may refer
to the reference copy directory. The CMS messages do not
make this explicit in some cases. When such problems are
encountered, you should check that you have the required
access to the reference copy.
5.13 VERIFY/RECOVER on Valid Library
If you use the VERIFY/RECOVER command on a library that does
not need recovery, the VERIFY operation will fail with an
error diagnostic, RECNOTNEC, stating that the library does
not need recovery.
5.14 SET ACL/DELETE with Nonexistent Identifier
When using the SET ACL/DELETE command to delete a list of
ACEs from an ACL, the operation will terminate if it
encounters an identifier that does not exist on the system.
The correct behavior is to continue the operation with the
remaining ACEs specified.
5.15 Syntax Errors on SET ACL and SHOW ACL
Certain syntax errors are not detected by the command parser
in the SET ACL and SHOW ACL commands. This may result in
the repetitious display of the illegal syntax error message
for each object specified for the operation.
5.16 Severity of Summary Messages
The severity of CMS success summary messages may be changed
from the documented value of SUCCESS to INFORMATIONAL in
some cases. This will be corrected in a future release of
CMS.
Page 14
5.17 Parameters on Negated Qualifiers
Certain qualifiers that should only accept parameters in
their non-negated form are also accepting them in their
negated form, and the qualifier is then treated as if it
were not negated. For example, the qualifier
/NOHISTORY="#H" should be disallowed, but is being treated
as /HISTORY="#H".
Page 15
6 Known Problems and Restrictions - DECwindows Interface
6.1 Access violations when virtual memory is exhausted
In the case of virtual memory being exhausted when updating
the contents of a CMS View, if the view is iconified an
access violation will occur when CMS attempts to bring up a
caution box. If the view is not iconified, after
acknowledging the box, the cursor will remain in a "watch"
shape and attempting to bring up a dialog box can result in
an access violation. It is recommended that you take
advantage of the Customize Restrict functionality (new with
this release) to avoid this problem. You will find that
Restrict History, by default, will show you only the
previous 30 days' history.
6.2 Problem with horizontal scrolling in views
As a result of a problem in the Structured Visual Navigation
widget used for CMS views, it is possible to get shifted
text overwritten on top of what was the pre-shifted text.
Updating the view or iconifying and then de-iconifying the
application will generally clear up the problem.
6.3 Text insertion cursor
Text insertion cursor is not set to the first sensitive
widget.
6.4 Help Key will not bring up the Help Overview frame
To access the Overview frame for CMS, you must use the Help
menu Overview entry.
6.5 Cancel Operation Button response is not immediate
In order for a "push" of the Cancel Operation button to be
detected, DECWindows events must be processed and once a
call has been made to the CMS Callable interface, this won't
occur until CMS emits a message for any reason. Thus, if
message logging has been customized to None, the Cancel
Operation button may not be recognized until after the
operation has been completed.
Page 16
6.6 Modify Library has an unused text widget
Modify Library has a text widget to hold a library name.
The library name is not written into this field.
6.7 Create Element/Class/Group do not allow selection
These operations do not allow selection of the library or
libraries into which to do the creation.
6.8 Maximum of 65,536 characters can be copied to the Clipboard
A maximum of 65,536 characters can be copied from a CMS view
to the DECWindows Clipboard.
6.9 Maximum of 256 characters on a line in a view
A maximum of 256 characters can be displayed on any one line
in a view. If one of the items in the line is a very long
remark string, for example, the string will not be entirely
displayed.
6.10 Help Dialog Box
The Help dialog box cannot be used if there is an Options or
Occlude dialog box active. The Options or Occlude box must
be removed before Help can be used. This will be changed
for a later release.
6.11 DECW$DISPLAY Logical Name
No check is currently made if the DECW$DISPLAY logical name
is defined. Note that this logical must be defined and
point to an accessible, appropriately configured system for
any DECwindows application to work.
6.12 Messages from some operations don't appear in message boxes
Some informational messages resulting from opening or
closing libraries will appear on the terminal where the CMS
DECwindows interface was invoked rather than in the output
window. This also occurs when manipulating a reserved
element or an element under review.
Page 17
6.13 Command error checking is not robust
As an example, trying to Fetch the elements denoted by:
"a.a,,b.b" will result in elements A.A and B.B being
fetched, followed by a caution box stating: "Error fetching
element a.a,,b.b Group not found."
Page 18
7 Installation Procedure Requirements
The installation should take approximately 10 to 45 minutes,
depending on the type of media and your system
configuration. If you do not have a license registered and
loaded for CMS, you will be able to install the kit but will
not be able to run either the IVP or CMS itself until you
have done so. Before installing CMS, you must have the
following privileges and resources:
o SETPRV privileges, or CMKRNL, WORLD, and SYSPRV
privileges
o A minimum of 6600 blocks of free disk space during
installation; 3600 blocks are used after installation
(when both CMS proper and the CMS DECwindows interface
are being installed).
o A minimum of 1400 + size of SYS$LIBRARY:DCLTABLES.EXE
free global pages at installation
o A minimum of 12 free global sections at installation
NOTE
You must ensure that your system has the necessary
global page and global section SYSGEN quotas for the
installation. Failure to do so could cause the DCL
tables to be corrupted in some situations.
See the VAX DEC/Code Management System Installation Guide
for more details on installation procedure requirements.
During the installation, the CMS Installation Verification
Procedure (IVP) is moved to the SYS$TEST directory. To run
the IVP at any time after the installation, enter
@SYS$TEST:CMS$IVP.COM at the DCL prompt. Please note that
for the IVP to run successfully, your current default
directory must not be specified as a DCL search list (which,
for example, is typically the case with SYS$MANAGER).
Page 19
8 User Account Quotas and Privileges
To use CMS, each account must have a minimum of TMPMBX and
NETMBX privileges and the following minimum requirements:
o AST limit (ASTLM) of 14
o Buffered I/O byte count quota (BYTLM) of 14,000
o Enqueue quota (ENQLM) of 1
o Open file limit (FILLM) of 6
o Timer queue entry limit (TQELM) of 1
See the VAX DEC/Code Management System Installation Guide
for more details on user account quotas and privileges.
Please also refer to the "Installation Guide Additions and
Corrections" section below.
Page 20
9 Library Conversion
NOTE
The following description of CMS V3.0 library
conversion also applies to CMS V3.2. It is not
necessary to install CMS V3.0 or V3.1 before
installing CMS V3.2. CMS V2 libraries may be
converted to V3 format using CMS V3.2.
The CMS data base has been reorganized in V3.0 for
performance reasons. In addition, the CMS library has been
reorganized to store element data files in subdirectories,
named CMS$nnn, of the CMS library directory. These changes
require that libraries created with any V2 version of CMS be
converted to the new format. Conversion of V1 libraries is
no longer supported.
To convert a library, you must use the CMS CONVERT LIBRARY
<v2 library> <v3 library> command, specifying the existing
library and an empty directory to receive the new library.
The original library is not altered by the conversion.
NOTE
The CMS CONVERT LIBRARY command is only available
through the DCL interface. It is not available in
the DECwindows interface.
Conversion time depends highly on the number of classes in
the library, the number of generations in those classes, and
the size of the 00CMS.CMS file in the original library. For
example, a 3000-block 00CMS.CMS file with 125 classes each
holding approximately 300 generations will take about five
hours on a VAX 11/785 to convert. The converted library
will take up about the same amount of disk space as the
original library, although the new 00CMS.CMS is likely to be
10 to 20% larger.
Note that CMS does not propagate the security attributes of
existing CMS V2 library files to the new CMS V3 library.
The owner, UIC-based protection, and access control lists
(ACLs) of the files in the new CMS V3 library are determined
by the default values for the process performing the
conversion or by the ownership and access control list
(specifically, access control entries (ACEs) with the
OPTIONS=DEFAULT clause or DEFAULT_PROTECTION ACEs) on the
CMS V3 directory file itself.
You may establish default ACEs on the CMS library directory
before performing the CMS CONVERT LIBRARY operation. All
element files and element file subdirectories created during
Page 21
conversion will automatically inherit the specified
protection and default ACEs. This is the recommended
procedure. If you set the security attributes on files in
an existing CMS V3 library (i.e., after conversion),
remember that you must VERIFY/REPAIR the library afterwards,
so that CMS can restore the element data file headers. See
Section 9.2.2 of the Guide to VAX DEC/Code Management System
for more information on using VERIFY/REPAIR.
If you had used file security attributes to restrict or
control access to your CMS V2 library, you may wish to
review these in view of the functionality provided by the
new CMS internal security mechanisms, which allow you to
specify ACLs on CMS elements, groups, classes, and library
entities, such as the library history, the CMS commands, and
the class, element, and group lists. For more information
refer to Chapter 7 of the Guide to VAX DEC/Code Management
System.
Page 22
10 Documentation Errata
10.1 CMS$SHOW_RESERVATIONS Callback Parameters
The new optional reservation-identification-number argument
has been added at the end of the argument list for both the
CMS$SHOW_RESERVATIONS routine as well as for its output
callback routine. Only the first addition has been
documented.
10.2 CMS$SHOW_ACL needs CMS$_USERERR documented
In the VAX DEC/Code Management System Callable Routines
Reference Manual (V3.0), the following addition should be
made in the description of the CMS$SHOW_ACL callable
routine:
CMS$__USERERR User routine returned Error
an error to CMS.
10.3 Width specification for DIFFERENCES
In the Guide to VAX DEC/Code Management System (V3.2), in
the description of the /WIDTH=n qualifier for DIFFERENCES,
"The value n can be a character from 48 to 511" should be
changed to "The value n is required and must be an integer
in the range 48 to 511".
In the VAX DEC/Code Management System Callable Routines
Reference Manual (V3.0), the description of the width
argument for CMS$DIFFERENCES states its range incorrectly as
48 to 500, instead of 48 to 511.
10.4 File revision time features are not yet documented
As described above in Section 3.3, the new file revision
time features are not yet documented.