Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

How to Find Out What You Can Claim

  • Last UpdatedJan 26, 2022
  • 2 minute read

This section explains what different users will see as a result of Q CLAIMLIST commands.

For this example, take the case of a database PIPE/PIPE, accessed by USERA, with two extracts. Users USERX1 and USERX2 are working on the extracts.

USERA creates a Pipe and flushes the database back to the parent database, PIPE/PIPE. The results of various Q CLAIMLIST commands by the three Users, together with the extract control commands which they have to give to make the new data available, are shown in the following diagram.

Note that:

Q CLAIMLIST EXTRACT

tells the user what can be flushed; and:

Q CLAIMLIST OTHERS

tells the user want cannot be claimed

To query the extract claimlist for a named database. The database can be the current one or its parent:

Q CLAIMLIST EXTRACT DB dbname

When you create an element, it is only seen as a user claim, not an extract claim, until a SAVEWORK. It will then be reported as an extract claim (as well as a user claim, if it has not been unclaimed).

Note that a change in the claim status of an existing element will be shown by the appropriate Q CLAIMLIST command as soon as appropriate updates take place, but a user will have to GETWORK as usual to see the changes to the MODEL model data.

We recommend that:

  • Databases that are going to own extracts which are primary at other locations, should be created with explicit claim mode.

  • Before you make an extract claim, you should do an EXTRACT REFRESH (or an EXTRACT FULLREFRESH, if necessary) and GETWORK.

  • If you need to claim many elements to an extract, it improves performance if the elements are claimed in a single command, for example, by using a collection:

    EXTRACT CLAIM ALL FROM !COLL

The Global daemon will only be involved in the claiming process if the user is claiming an element from a secondary database / extract to their current primary extract. In this instance, the user will be warned that the element is now being claimed by the Global daemon. The user will know when the claim is completed, by using GETWORK and checking the claim list.

TitleResults for “How to create a CRG?”Also Available in