DBchange/CM Reflects Consistency Across Data Management Tools [ COMMUNICATOR 3000/XL XL RELEASE 2.1 ] MPE/iX Communicators
COMMUNICATOR 3000/XL XL RELEASE 2.1
DBchange/CM Reflects Consistency Across Data Management Tools
by Peg Ray/Mark Boronkay
Data Management Systems Divison
Several changes have been incorporated into DBchange/CM (B.00.15) that
bring DBchange/CM in line with DBSCHEMA.PUB.SYS processing, and also
increase the usability of DBchange/CM. The following describes these
changes.
ADD SET/ADD ITEM
All new items and sets added with DBchange/CM with no explicitly defined
security will follow the same default security that is currently used in
DBSCHEMA.PUB.SYS. This default security assures that all user classes
will have read access to the new item or new set while only the database
creator will have write access. This default security is equivalent to
the default security when using a null or absent list in DBSCHEMA.PUB.SYS
REVIEW SECURITY/CHANGE SECURITY
The Review Security/Change Security function will still display "R" (for
read access) for all 64 user classes when an item has been defined with
default security. The change occurs when the user attempts to modify
security. Previously, the user would press the Change Security key and
receive an error message indicating the user class is undefined (if any
of the 64 user classes ARE NOT defined). This error message will no
longer be displayed. That is, a user class may be granted Read or Write
access to a data item or set regardless of whether the user class has
been defined. Again, this is consistent with DBSCHEMA.PUB.SYS.
DELETE PASSWORD
The Delete Password function has been modified to separate the task of
deleting a user class from the task of modifying item or set security
read/write class lists. When a password is deleted from a user class,
the read/write class lists will remain unchanged.
MPE/iX Communicators