Command Syntax
- Last UpdatedFeb 15, 2023
- 2 minute read
The command syntax for handling extract claims in Model is as follows:
>- EXTRACT -+- CLAIM --------.
| |
|- FLUSH --------|
| |
|- FLUSHW -------|
| |
|- RELEASE ------|
| |
|- ISSUE --------| .-----<---.
| | / |
|- DROP ---------+-*- element -+- HIERARCHY -.
| | | |
| | ‘-------------|
| | |
|- FULLREFRESH --| |
| | |
|- REFRESH ------+--- DB dbname -------------+--->
|
‘- FLUSH RESET ------ DB dbname ----------------->‘
|
CLAIM |
Claims the element or the whole database to the extract. |
|
FLUSH |
Writes the changes back to the parent extract. The Extract claim is maintained. The extract is refreshed with changes that have been made to its owning database. |
|
FLUSHW |
Writes the changes back to the parent extract. The Extract claim is maintained. The extract is not refreshed. |
|
FLUSH RESET |
Resets the database after a failed EXTRACT FLUSH command. (See note below under Flushing Changes.). |
|
REFRESH |
Refreshes an extract with changes that have been made to its parent extract. |
|
FULLREFRESH |
Refreshes an extract and all its ancestors. A full refresh takes place from the top of the database hierarchy downwards, ending with a refresh of the extract itself. Each extract is refreshed with changes that have been made to its parent extract. |
|
ISSUE |
Writes the changes back to the owning extract, and releases the extract claim. |
|
RELEASE |
Releases the extract claim: this command can only be used to release changes that have already been flushed. |
|
DROP |
Drops changes that have not been flushed or issued. The user claim must have been unclaimed before this command can be given. |
The HIERARCHY keyword must be the last on the command line. It will attempt to claim to the extract all members of the elements listed in the command which are not already claimed to the extract.
The elements required can be specified by selection criteria, using a PML expression. For example:
EXTRACT CLAIM ALL PIPE WHERE (:OWNER EQ ‘USERA’) HIERARCHY