Checking Parts of the Design
- Last UpdatedNov 14, 2025
- 1 minute read
Keywords:
CHECK ATTACHECK
Description:
The CHECK command initiates a full Component-by-Component data consistency check of specified parts of the Design. Up to 10 elements may be specified in a single CHECK command.
ATTAs will be checked in the same way as normal components if the ATTACHECK ON option is in force. They will be ignored if ATTACHECK OFF is in force.
You can store error references and (optionally) error codes in PML arrays, if required. If you do this, you can then use the ENHANCE command to highlight the problems on the display. See the Software Customization Guide for further information on PML and arrays.
|
Examples: |
|
|---|---|
|
CHECK /ZONE-1 |
Generates full consistency report on every component in the named Zone. |
|
CHECK /BRAN1 /BRAN2 /BRAN3 |
Generates selective report on the named Branches only. |
|
TOL ATTACHECK OFF |
ATTAs will be ignored in subsequent checks. |
Command Syntax:
.----<-----.
/ |
>-- CHeck --*-- <sgid> --+-- <varid1> -- [<varid2>]--.
| |
‘---------------------------+---->
>-- TOLerance ATTACheck --+-- ON* --.
| |
‘-- OFf --+-->
Where <varid1> is the PML array used to store references of any elements with errors, and the (option) <varid2> is the array that stores the error codes.
Querying:
>-- Query TOLerance ATTACheck -->