LIMIT_SPECS_ALL

# List of limits on real, integer, statistical, compostion, 
# or property variables which will 
# terminate the mode when all limitis are
# simulataneously being violated

#   This keyword is similar to @LIMIT_SPECS except that the exit path
#   is taken only when all of the limit specifications are satisfied.
#   Not only must they all be satisfied, but they must all be satisfied
#   simultaneously. 
   
   
@LIMIT_SPECS_ALL

   #exit path (mode #, procedure file, MODE_TERMINATE, or RETURN)
   MODE_TERMINATE
   
   #list of limits (up to 16)
   #variable      value       Upper/Lower       interval    period(optional)
   cmp_in_p       10[in_hg]   U                 SLO         0[s]
   cmp_ot_p       mylimit     U                 SLO
   

# Note that the "value" field may be a constant, variable, or expression.   


# Two string variables can be specified to give the operator feedback
# on the state of this specification.  These variables are specified in
# the header file for each instance of gp_test (usually /specs/gp/gp_header).

# The default version of this file in //1/specs.def/gp/gp_header contains
# the variable names TrmLIM_waiting and TrmLIM_done.  These two variables
# are created in the file /cell/display_strings.  For other instances of
# gp_test, different variable names will have to be used or they can be
# left out of the spec file.

# The TrmLIM_waiting variable will contain a list of the specifications
# which are currently not in violation and TrmLIM_done will contain a 
# list of the variables which are violating their limit.  For example,
# in the example specification above, if neither cmp_in_p nor cmp_ot_p
# where above 10[in_hg], then the string TrmLIM_waiting would contain
# "cmp_in_p cmp_ot_p" and the TrmLIM_done variable would be blank.