6. DATA SOURCES › 6.3 Correlating Data Sources › 6.3.10 Determining Number of Route Element/TG Names

6.3.10 Determining Number of Route Element/TG Names

Although the NLDM Route (NVSRTE) File can carry up to nine
route element names (RTEELNAx) and nine transmission group
names (RTETGNMx) in each observation, the file is shipped
with only three route element names (RTEELNA1 - RTEELNA3) and
three transmission group names (RTETGNM1 - RTETGNM3)
activated to minimize its size.  If a significant number of
logical unit to logical unit (LU-LU) sessions in your network
span more than three route elements or transmission groups,
you may wish to increase the number of route element and
transmission group names in the NVSRTE file.

A simple way to determine if this increase is necessary is to
examine the content of the element Number of Route Elements
in Table (RTENRRE).  If the value of this element is greater
than three for a large number of the virtual routes in your
network, you should increase the number of route element and
transmission group names in the file.

You can change the number of RTEELNAx and RTETGNMx members in
each observation in the NLDM Route File by modifying the
RTEELNAx and RTETGNMx statements in the SNTGENIN member in
sharedprefix.MICS.GENLIB.  Refer to Section 6.2.1.1.2, Adding
New Data Elements, in the CA MICS System Modification Guide
for complete instructions.  In the example below, the number
of route element names is increased from three to four by
activating Route Element 4 Name.  To accomplish this,

   o  Modify the name statement for RTEELNA4 in
      sharedprefix.MICS.GENLIB(SNTGENIN) by replacing each N
      with 0 in the DETAIL, DAYS, WEEKS, and MONTHS
      timespans, and

   o  Run the component generator for the CA MICS Network
      Analyzer.

1.  RTEELNA4 before the change (inactive in all timespans)

                      TIME-SPAN
                      X D W M Y
                      _________
ALIAS RTEELNAX
NAME RTEELNA4     00  N N N N N   Route Element 4 Name

2. RTEELNAX  after the change (active in DETAIL, DAYS, WEEKS,
   and MONTHS timespans)

                      TIME-SPAN
                      X D W M Y
                      _________
ALIAS RTEELNAX
NAME RTEELNA4     00  0 0 0 0 N   Route Element 4 Name

Note:  Replacing N with 0 in the YEARS timespan would have
       no effect because the NLDM Route File is not supported
       in the YEARS timespan.  Route Element 4 Name must be
       activated in the DETAIL timespan if it is to be
       activated in any of the higher timespans.  The value
       of the RTEELNAx in the higher timespans is derived
       from its value in the DETAIL timespan.

       You should note that NetView does not necessarily
       record the names of all of the route elements
       traversed in the route element table.  In some cases
       one or more of the route elements will be defined in
       the configuration data portion of the SMF type 39
       records and will not be restated in the route element
       table.  The CA MICS data element RTENRRE reflects the
       number of elements defined in the route element table.
       To know the actual number of route elements traversed,
       you should refer to the CA MICS data element RTENRTRE,
       Total Number of Route Elements Traversed.