|
|
DataMuseum.dkPresents historical artifacts from the history of: Rational R1000/400 Tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about Rational R1000/400 Tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: R T
Length: 1352 (0x548)
Types: TextFile
Names: »READ_ME«
└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
└─⟦5cb1d1d7f⟧ »DATA«
└─⟦3b1ee7bd8⟧
└─⟦this⟧
This software supports the notion of check-out to person. The preferred solution is to allocate one subpath to each person and use access control separately on each subpath. In cases where this is impossible, this software can support the following protection among the developers in the subsystem. All developers are divided into groups 1) Users in a specific group may only check-out certain units. 2) Once a user checks out a unit, only that user may edit that unit. 3) Once a user checks out a unit, only that user may check that unit back in. Initially, all groups are given RW access to all units allowing them to visit, demote, and promote all units. Note that they cannot edit the unit because it is controlled and they must check it out first. When a user checks a unit out, RW access is reduced to that user only, thus allowing only that user to edit it. The check_in command check the CMVC database to see if the same user has check the unit out. If this is not true, the command fails. The package Authorization_List defines which groups have access to which units. Wildcards are used to define groups of units. This can be disabled if not useful to your project. The package Local_Cmvc is a "skin" that enforces this check-out / check-in policy and passes through all other commands to the environment cmvc interface.