5. DATABASE FILES › 5.3 NVS Information Area › 5.3.3 NLDM Session Connectivity File (NVSNSC) › 5.3.3.3 Usage Considerations

5.3.3.3 Usage Considerations

This section identifies special considerations or techniques
related to using the NVSNSC 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
   PLDOMAIN - PLU Domain Name
   PLU      - Primary Logical Unit
   PLUPU    - Primary Logical Unit Physical Unit
   PLUSAPU  - PLU Subarea Physical Unit
   PRIMLINK - Primary Link (NLDM)
   SESTYPE  - Session Type
   SLDOMAIN - SLU Domain Name
   SLU      - Secondary Logical Unit
   SLULINK  - SLU Link
   SLUPU    - SLU Physical Unit
   SLUSAPU  - SLU Subarea Physical Unit
   TMOFFSET - TIME OFFSET
   NSCCOS   - Class of Service
   NSCEXRTE - Explicit Route Number
   NSCRVER  - Reverse Explicit Route Number
   NSCTRPTY - Transmission Priority
   NSCVRRTE - Virtual Route Number
   NSCXDMN  - Cross-domain Session (Y or N)
   NSCXNET  - Cross-network Session

4. The following are two special problems regarding TSO
   sessions and the element PLU.  These two problems are as
   follows:

   o Both NetView and CA NetMaster record two sessions for
     every TSO user session.  This number is carried in the
     CA MICS element Number of Sessions (NSCNMSES).

   o The PLU element carries multiple values for sessions
     with a single TSO system.  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.

Retrieval Example

Report the prime shift application statistics for yesterday.

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

   PROC SORT DATA=&PNVSD..NVSNSC01 OUT=SORTED;BY &BY;
   RUN;

   DATA SUMMED (RENAME=(PLU=APPL NSCCONTM=CONNECT
                  NSCNMSES=SESSIONS NSCNRTCH=TRAFFIC));
   SET SORTED;
   %NSCSUM;           /* SUM THE DATA */
   RUN;

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

   PROC PRINT;VAR APPL SESSIONS CONNECT TRAFFIC;
   TITLE 'DAYS NVSNSC01, PRIME SHIFTE APPL STATISTICS';
   RUN;