5. DATABASE FILES › 5.3 NVS Information Area › 5.3.2 NLDM Session Accounting File (NVSNSA) › 5.3.2.3 Usage Considerations

5.3.2.3 Usage Considerations

This section identifies special considerations or techniques
related to using the NVSNSA File.  In addition, several
retrieval examples are 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. 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. 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.

3. 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
   NSAXDMN  - Cross-domain Session (Y or N)

4. 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.
   You can circumvent this problem with 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.

Retrieval Example

Report connect time last week for the applications TSO08,
TSO09, DBDCCICS, and IMSPROD by zone.

   DATA SELECTED (RENAME=(PLU=APPL NSACONTM=CONNECT));
   SET &PNVSW..NVSNSA01;
   IF PLU='TSO08' OR PLU='TSO09' OR PLU='DBDCCICS' OR
      PLU='IMSPROD';
   IF DAYNAME NE 'SAT' OR DAYNAME NE 'SUN';
   ZONENAM=PUT(ZONE,$ZONENM.);

   PROC PRINT DATA=SELECTED; VAR DAYNAME CONNECT;
   BY NETWRKID SYSID ZONENAM;
   TITLE 'WEEKS NVSNSA01, MON-FRI APPL CONNECT TIME ';