Multi-User mode is required to execute this command. To confirm a table's constraints, execute DBUTLTY with the command:
►►─ CONFIRM DBID=n,TABLE=ttt ─┬───────────────────────┬───────────────────────► └─ ,DELETE= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘ ►─┬──────────────────────┬─┬────────────────────────────┬────────────────────► └─ ,FORCE= ─┬─ NO ◄ ─┬─┘ └─ ,EXCEPT=authid.tablename ─┘ └─ YES ──┘ ►─┬───────────────────────┬──────────────────────────────────────────────────►◄ └─ ,VERIFY= ─┬─ NO ◄ ─┬─┘ └─ YES ──┘
Command
Invokes the function to verify the integrity constraints for a table.
Required Keywords
Identifies the database containing the table.
DATACOM-ID of the database containing the table
(No default)
Identifies the table to be verified.
DATACOM-NAME of the table
(No default)
Optional Keywords
Specifies whether invalid records (rows) in the table are to be deleted.
NO or YES
NO
Specifies an SQL table into which the rows found to violate constraints are inserted. If DELETE=YES is also specified, the records (rows) are saved into this table before they are deleted from the table being confirmed.
The name of an existing SQL table whose definition matches that of the table being confirmed. You must specify an AUTHID.
(No default)
Allows you to bypass constraint verification and move the table from CHECK PENDING to usable status regardless of the underlying data. Use of this option is recorded in the FORCED OFF field of the HISTORY CHECK PENDING section of the CXX Report. Use of this option is valid only when the user is certain that the data contained in the table conforms to all constraints.
NO or YES
NO
Indicates that you want the data to be checked, even if the table is not in CHECK PENDING status.
For example, you may have executed the CONFIRM function, specifying FORCE=YES which does not check the data, but indicates that you have forced the CONFIRM. When you use the VERIFY option, the system confirms the data, checking for integrity constraints.
NO or YES
NO
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|