5. DATABASE FILES › 5.3 NVS Information Area › 5.3.5 NLDM Route File (NVSRTE) › 5.3.5.3 Usage Considerations
5.3.5.3 Usage Considerations
This section identifies special considerations or techniques
related to using the NVSRTE File. In addition, a retrieval
example is provided to facilitate the use of this file.
In the examples, a SAS macro variable is used to specify the
DDname part of the CA MICS file name. These macro variables
are a standard part of CA MICS and are available for all
files. The macro variable name has the form &diiit, where d
is the database identifier, iii is the information area
name, and t is the timespan. For the examples, a database
identifier of P is used. The identifier is installation
dependent, so you should find out what the identifiers are at
your installation.
Special Considerations/Techniques
1. 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 Chapter 6 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 Option.
o 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
o 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.
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, refer
to the CA MICS data element RTENRTRE, Total Number of
Route Elements Traversed.
2. Care must be exercised in using the special date and time
data elements contained in each CA MICS file. As file
granularity increases in higher timespans, certain fields
lose significance and should not be used in those cases.
o HOUR should not be used in MONTHS.
o DAY and DAYNAME should not be used in WEEKS or MONTHS.
o WEEKS should not be used in MONTHS.
3 The following data elements are user-defined. The value
in each depends on user-selected options or user-supplied
SAS code:
o NETWRKID - Network Identifier. A one to eight-character
descriptive name for each network represented in the
data. NETWRKID is set in the Network Identifier Exit
Routine, SNTNIDRT, discussed in Chapter 7.
o TMOFFSET - TIME OFFSET applied to the data in the file.
The user can associate a TIME OFFSET with each unique
NETWRKID/SYSID combination. This offset is used to
adjust data times when data from multiple time zones is
brought together in the CA MICS database. To determine
the original time at which the data was recorded,
subtract TMOFFSET from the value. TIME OFFSET is
assigned in the SNTOPS member of prefix.MICS.PARMS,
discussed in Chapter 7.
4. The following data elements lose significance once
summarization has been performed, unless they are used in
the summarization sequence as a result of being included
in one of the accounting fields (i.e., SNTACT1, SNTACT2,
etc.).
NLDMVRRL - NLDM Version and Release ID
PLU - Primary Logical Unit
SLU - Secondary Logical Unit
SLULINK - SLU Link
TMOFFSET - TIME OFFSET
RTEELNAx - Route Element x Name
RTETGNMx - Transmission Group (out) x
RTEXDMN - Cross-domain Session (Y or N)
5. For TSO sessions, both NetView and CA NetMaster record
multiple values for the primary logical unit (PLU) for
sessions with a single TSO system. These duplicate values
are carried over into the CA MICS data for TSO sessions in
the element PLU. This can greatly increase the size of
the file if PLU is chosen as one of the account codes.
This problem can be circumvented by the user-coded routine
in prefix.MICS.PARMS(SNTPLURT), which sets the multiple
values for PLU to a single value for each TSO system.
Refer to Section 7.10 for information about SNTPLURT.
6. If you are processing CA NetSpy Virtual Route Activity
data, you should also look at the SNTNVR file for response
time information for the virtual route.
Retrieval Example
Show connect time by virtual route number using the data from
yesterday.
/* SET THE SUMMARY MACROS */
%LET BY = NETWRKID SYSID RTEVRRTE;
%LET BREAK = RTEVRRTE;
PROC SORT DATA=&PSNTX..NVSRTE01 OUT=SORTED;BY &BY;
DATA SUMMED (RENAME=(RTECONTM=ACTIVE));
SET SORTED;
%RTESUM; /* SUM THE DATA */
RUN;
PROC PRINT; VAR RTEVRRTE ACTIVE;
BY NETWRKID SYSID;
TITLE 'DETAIL NVSRTE01, VIRTUAL ROUTE CONNECT TIME';
RUN;
Copyright © 2014 CA.
All rights reserved.
|
|