5. DATABASE FILES › 5.3 NVS Information Area › 5.3.7 NLDM VTAM BIND Failure File (NVSVBF) › 5.3.7.3 Usage Considerations

5.3.7.3 Usage Considerations

This section identifies special considerations or techniques
related to using the NVSVBF 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 time-spans, certain fields
   lose significance and should not be used in those cases.

   - HOUR should not be used in MONTHS.
   - DAY and DAYNAME should not be used in WEEKS or MONTHS.
   - 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 TMFFSET - 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 data base. 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.  These data elements
   should be referenced only when the last observed value in
   a summarization interval is significant.

   NLDMVRRL - NLDM Version and Release ID
   SESTYPE  - Session Type
   SLULINK  - SLU Link
   TMOFFSET - TIME OFFSET
   VBFCAUSE - BIND Failure/UNBIND Reason
   VBFXDMN  - Cross-domain Session (Y or N)
   VBFXNET  - Cross-network 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 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 CA MICS
   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

List the frequency of VTAM UNBIND codes by application from
today's data.

      PROC FREQ DATA=&PNVSX..NVSVBF01;
      TABLES PERFCLSS * VBFRCODE / NOROW NOCOL NOCUM;
      TITLE 'DETAIL NVSVBF01, PERF CLASS BY UNBIND CODE';
      RUN;