User Claims

Normal multi-write databases require the user to claim an element before changing it. This is known as a user claim. Depending on how the database is set up when it is created, user claims can be implicit or explicit, and in either case, when a new element is created, it will be claimed to the user who created it.

Note:
In a Global project, we recommend that multi-write databases should be created with EXPLICIT claim mode, unless all the children are primary at the same location.

User claims can be explicitly released (unclaimed) by the user during a session, and elements are always unclaimed when the user changes or exits from a module.

The commands for user claims are:

CLAIM . . .

UNCLAIM . . .

Extract Users can check daemon availability before claiming or flushing using the following command line syntax:

Q COMMS (TO) <loc>

Q COMMS (TO) <loc> PATH

PING <loc>

Q ISOLAT AT <loc>

Q PROJ LOCK AT <loc>

These commands are now available in Model and other modules. This is particularly useful to Claiming/Flushing, since commands fail if the connection is down.