5. DATABASE FILES › 5.2 SNT Information Area › 5.2.16 NCP Network Accounting File (SNTNAC) › 5.2.16.3 Usage Considerations

5.2.16.3 Usage Considerations

This section identifies special considerations or techniques
related to using the SNTNAC File.  In addition, a retrieval
example is provided to facilitate the use of this file.

CA MICS network session accounting/network gateway accounting
supports the following versions of CA NetSpy, IBM Tivoli
NetView Performance Monitor (NPM), and Network Control
Program (NCP), or higher:
 
o CA NetSpy Release 6.0 and later
o NPM Version 2 and later
o ACF/NCP Version 5 Release 2.1 and later
 
To prevent potentially serious problems with missing or
duplicate data, do NOT use versions, releases, or revisions
previous to those specified above.




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. 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.


2. Avoid collecting redundant network session accounting and
   network gateway accounting data from either NPM or CA
   NetSpy.  This is especially important if you input this
   data into the CA MICS Accounting and Chargeback product.
   The following SNTNAC elements can assist you in detecting
   redundant data:

     NACCOLPT - NCP Collection Point
     FUNCTION - Product Function
     NACANPLU - Adjacent NETID PLU Side (NGA)
     NACANSLU - Adjacent NETID SLU Side (NGA)
     USESSIDC - Unique Session ID

   An example of redundant data collection occurs when
   multiple gateway NCPs are traversed by a terminal to
   application session and each of these NCPs collects
   gateway accounting data for that session.  In this case,
   the redundant data can be detected by the presence of
   multiple observations in the DETAIL timespan with
   identical Unique Session IDs, but different values for
   Adjacent NETID PLU Side or Adjacent NETID SLU Side.  Refer
   to Section 8.1.3.3 of this guide, Redundant Information
   Issues, for further information on how to detect and
   eliminate duplicate network accounting data.

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 of this guide.

   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 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 of this guide.

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.).

     ACTLDEV  - Locally Attached Device (Y or N)
     ACTXDMN  - Cross-Domain Session (Y or N)
     ACTXNET  - Cross-Network Session (Y or N)
     NETGROUP - Network Service Group
     PLU      - Primary Logical Unit
     SAMPLES  - Number of Samples
     SLU      - Secondary Logical Unit
     SLULINK  - SLU Link
     SLUSAPU  - SLU Subarea Physical Unit
     TMOFFSET - TIME OFFSET

Retrieval Example

Report total traffic volumes and connect time for PLU for
yesterday.  This example is designed for a site that has
defined SNTACT1 as PLU in sharedprefix.MICS.PARMS(SNTACRT).
If your site has set a different account code for PLU, for
example SNTACT2, change all references to SNTACT1 to the
account code your site has defined as PLU.

   /* SET THE BY AND BREAK SUMMARY MACROS */
   %LET BY = NETWRKID SYSID SNTACT1;
   %LET BREAK = SNTACT1;

   PROC SORT DATA=&PSNTD..SNTNAC01 OUT=SORTED;BY &BY;
   RUN;

   DATA SUMMED (RENAME=(NACCONTM=CONNECT
          NACNRTBY=BYTES NACNRTPI=PIUS));
   SET SORTED;
   %NSCSUM;           /* SUM THE DATA */
   RUN;

   DATA SUMMED;
   SET SUMMED;
   IF 9 GE HOUR LE 17;  /* SELECT PRIME SHIFT */

   PROC PRINT; VAR PLU CONNECT BYTES PIUS;
   TITLE 'DAYS SNTNAC01, PRIME SHIFT PLU STATISTICS';
   RUN;