? LIST NETWORK


LIST NETWORK is used to obtain a routing list of any Netline networks  in  a
drawing, plus an optional list of components associated to the network.  

The  network  route  or  from-to  list  is  made up of 3 components; source,
network label, and destination. The source and destination are obtained from
the terminating ends of each network. This can be the name on a Symbol, text
obtained from a Tnode or the Terminal at the network end, or the name of  an
associated  network  if  the  reported network starts or ends on a different
network.  

If a network starts or terminates at a non-juntion Terminal, then the source
or destination description is formatted

   Item_name-Terminal_name

where  Item_name  is  taken  from  the  Text related to a Tnode related to a
Symbol related to the terminating Terminal. If the  Symbol  related  to  the
Terminal  has  more  than  1 associated Tnode, then the Tnode containing the
attribute ITEMNAME is used to obtain the network end description.  

Terminal_name is taken from any Text  entity  related  to  the  network  end
Terminal.  

   NETWORK TRACING

The  limits  of each indivdual network can be defined in 3 different ways: A
single terminal to which only a single Netline is attached; a Terminal  with
the attribute NETBREAK; or a junction at which the network flow is halted.  

Network  flow across junctions can be defined explicitly, or can be left for
the command  to  decide.  When  a  junction  of  more  than  2  Netlines  is
encountered,  the  Netline  that  starts or ends at the junction Terminal is
examined for the BRANCH attribute.  If  this  attribute  exists,  then  this
network is assumed to start or end at this junction. If the BRANCH attribute
does not exist, the network  flow  is  routed  along  any  other  non-BRANCH
Netline  associated  to  the  junction  whose flow direction matches that of
current Netline. If there is more than one valid Netline to choose  from  in
this  case,  then  the  in-coming and out-going Netlines across the junction
Terminal must be colinear.  

Thus to avoid ambiguity, the BRANCH  attribute  should  be  used  to  decide
network  flow  across  junctions.  In  the  simple  case  of  a "T" junction
containing no Netlines with the BRANCH attribute, the network flow is always
across the bar of the "T" if the flow direction match.  

The default description of a network route is in the format

   SOURCE      LINE-LABEL     DESTINATION

If the network contains more than one label, then the output format changes
to

   SOURCE      LINE-LABEL-1
               LINE-LABEL-2
                    :
               LINE-LABEL-n   DESTINATION

Each  section  of the network using a different line label must be delimited
by a Terminal containg the attribute NETCHANGE.  If  this  Terminal  is  not
found, then any one of the multiple labels will be used to tag the network.  

   COMPONENT SCHEDULE

The  component list option will generate for each network, a schedule of all
components that belong to the network. A component is  a  Symbol  containing
one  or  more  Terminals  linked into the network. Components that should be
excluded from the schedule - such as TEEs etc - should  have  the  attribute
NOREPORT.  

The  component  schedule  is  made  up  of 4 optional parts: Component type,
component description; component name; and the label of the section  of  the
network in which the component is situated.  

The  component  type  is  extracted  as  the value of the COMPTYPE attribute
associated with the component Symbol. The component description is extracted
from  the  COMPDESC  attribute  associated  with  the  component Symbol. The
component name is taken from the text related to a Tnode having the COMPNAME
attribute.  This  Tnode must be related to the component Symbol. The network
label is the first label encountered downstream from the component.  


   COMMAND FORMAT

      #LIST NETWORK [modifiers] :Netline d1 ... dn

One or more Netline entities are identified via IDENTS.


   MODIFIERS

TO             Specifies the name of the output file to which the network
               and component schedule is written. If this modifier is
               not used, the schedule is printed to the text window.

SOURCE         Specifies the column position in the report to place the
               source description.

LABEL          Specifies the column position in the report to place the
               network label name.

DESTINATION    Specifies the column position in the report to place the
               destination description.

COMPONENT      This modifier is used as a flag to indicate that a
               component schedule is required. If non of the lower level
               modifiers are used, all 4 fields of the component schedule
               are listed at their default column positions.

.TYPE          Specifies the column position in the report to place the
               component type text. If a value of zero is entered, this
               field is excluded from the component schedule.

.DESC          Specifies the column position in the report to place the
               component description text. If a value of zero is entered,
               this field is excluded from the component schedule.

.NAME          Specifies the column position in the report to place the
               component name text. If a value of zero is entered, this
               field is excluded from the component schedule.

.LINE          Specifies the column position in the report to place the
               component line label text. If a value of zero is entered,
               this field is excluded from the component schedule.

HEADER         A toggle used to specify if a header is required for the
               report.