1 :Info: mrds.scope.changes: mrds.scope:  1981-08-05  mrds.scope
 2 
 3 Notes on scope changes:
 4 The scope mode encodings for version 4 databases has changed for MR9
 5 MRDS.
 6 
 7 Previously the values 0, 1, 2 used for the permit and prevent ops in
 8 a call to dsl_$set_scope had meanings of null, retrieve, and update.
 9 
10 Now the encodings have changed.  They are 0, 1, 2, 4, 8 with meanings
11 of null, read_attr, append_tuple, delete_tuple, modify_attr.  These
12 correspond exactly to the old (pre MR8) encoding meanings of null,
13 read, store, delete, modify.  The names were changed to agree with
14 the new attribute level security access operation names.
15 
16 
17 When MR9 MRDS is installed, version 4 database users will not be able
18 to open their databases until after they have their database
19 administrator do an "adjust_mrds_db path -reset" on the database.
20 This operation will convert the concurrency control mechanism to use
21 the new scope modes.
22 
23 PL/I programs that have been running against version 4 databases
24 using the scope mode encodings for r-u, rather than r-s-m-d of pre
25 MR8 MRDS will have to be changed.  The users of exec_coms with
26 mrds_call will not have to change.  The u encoding will still mean
27 all update operations.  In addition, the encodings for mrds_call will
28 include a (or s), d, and m.  LINUS users will not notice a change
29 after the adjust_mrds_db is done.
30 
31 
32 To see if your database is using the latest version scope modes, the
33 command "display_mrds_db_status path -long" can be used.  The latest
34 concurrency control version (for the r-a-m-d modes) is version 5.
35 
36 
37 :hcom:
38 /****^  HISTORY COMMENTS:
39   1) change(2020-12-15,GDixon), approve(2021-02-22,MCR10088),
40      audit(2021-05-27,Swenson), install(2021-05-27,MR12.6g-0056):
41       A) Fix errors reported by the new verify_info command.
42                                                    END HISTORY COMMENTS */