Name
rulecomp - Bartels Rule System Compiler
Synopsis
rulecomp srcfile [-l]
Description
The
rulecomp compiler is used for translating Bartels Rule Specification source code.
rulecomp accepts the rule specification source file name
srcfile as first argument. This file must have an extension of
.rul, but this extension must not be included with the command line.
rulecomp translates the rule specification source file and stores the defined rules and/or rule sets to a file named
brules.vdb in the BAE programs directory. These rules can be applied by certain in-built BAE system functions and/or customer-defined
User Language programs.
Options
Command line options of the Rule System Compiler consist of the dash
(-) start character followed by the option specification. Single-character option specifications optionally followed by a mode or toggle number are often known as switches or flags.
Listing Option [-l]
The
-l option is used to control the listing file output. Omitting this option suppresses listing output. The
-l option generates a rule compilation listing file. The listing output file name is derived from the corresponding source code file name, with the original file name extension replaced by
.lst. The listing file is for user information purposes only, i.e., it is not required by system.
Examples
Compilation of the rules defined in
routstd.rul; the compiled rules are stored with the name
routstd to the
brules.vdb file of the BAE programs directory:
> rulecomp routstd 
Compilation of the rules defined in
routstd.rul with listing file output (to
routstd.lst); the compiled rules are stored with the name
routstd to the
brules.vdb file of the BAE programs directory:
> rulecomp routstd -l
Files
brules.vdb -- BAE rules data file (in BAE programs directory)
See also
Bartels AutoEngineer User Manual - Chapter 6
Diagnosis
The error messages issued by
rulecomp are intended to be self-explanatory.
Warnings
rulecomp is a powerful software tool for implementing rules for automatically generating and/or manipulating
Bartels AutoEngineer design data. It is strongly recommended to test each new rule in a non-critical environment (test software installation, test jobs, backup of real jobs, etc.) until confidence in the rule is established for unrestricted use on real designs.
