Restriction File Usage

The restriction file does not, as its name indicates, restrict any part of the functionality from being accessed. Instead, this is the means by which the system manager can tailor the tool by setting a few global options. The restriction file in itself is indicated by the environment variable

SB_PPPT_RESTRICT

and its contents can be used to rule the following:

• DATA_TYPE=<number>
  Sets the profile data type as used by these tools to <number>. Default is 90.

• ASSEMBLY_OPT=<YES/yes>
  Allows the user to neglect to specify assembly information in the main form.

• BLOCK_OPT=<YES/yes>
  Allows the user to neglect to specify block belonging in the main form.

• EXCESS_OPT=<YES/yes>
  Allows the user to neglect to specify excess information (for both ends) in the main form.

• BEVEL_OPT=<YES/yes>
  Allows the user to neglect to specify bevel information (for both ends) in the main form.

• POS_OPT=<YES/yes>
  Allows the user to neglect to specify positions number in the main form.

Comment in the file are allowed in any of two ways, either if the line starts with a '#' or '!', or as anything that follows after a blank on each line. This means that all the possible options listed above must be supplied as a consecutive word (that means, no internal spacing allowed).

The restriction file can contain any or all of these options in any internal order. In case any option is not specified or no restriction file exists, defaults will rule the user.