Check Optimization
This command is used to check the specified optimization with name optimization
name
.
Errors are reported by highlighting issues that prevent Solve from being performed. Possible errors:
- Syntax errors of optimization text
- Properties which must be explicitly locked
- Properties which must be explicitly posted
- Properties which contain posted functions containing an expression.
- For example,
A = PUSH(B + C, N)
, where A, B and C are posted, is not allowed.
- For example,
For each Class in the Class model, each Property listed with a message which indicates the property applicable for the Optimization. These are the possible categories:
- Posted
- Explicitly Locked
- Derived locked
- Posted and Explicitly Locked
- Posted and Derived Locked
- Not posted
- Not posted and subject to change
- Syntax
-
Check Optimization: <optimization name>;
- Log message
- This table lists the messages that are logged after successful execution of the
macro:
Scenario Message To indicate the solver check has started for the given optimization name
.APACS292=Check optimization started for optimization "{0}".
{0} = Name of optimization.
Each class in the Class Model is logged. APACS296="{0}".
{0} = Name of class.
In each Class, for each Property of that Class, a message is logged. -
APACS299="{0}" is posted.
-
APACS298="{0}" is locked.
-
APACS335="{0}" is locked (derived).
-
APACS297="{0}" is posted and locked.
-
APACS334="{0}" is posted and locked (derived).
-
APACS300="{0}" is not posted.
-
APACS336="{0}" is not posted, but subject to change.
{0} = Name of the property.
To indicate the solve check has completed for the given optimization name
.APACS293=Check for optimization "{0}" completed successfully
{0} = Name of optimization
To indicate the solve check completed with errors. APACS339=Check for optimization "{0}" completed with errors.
-