5. DATABASE FILES › 5.3 NVS Information Area › 5.3.6 NLDM Response Time File (NVSRTM) › 5.3.6.3 Usage Considerations

5.3.6.3 Usage Considerations

This section identifies special considerations or techniques
related to using the NVSRTM 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. To ensure that the NVSRTM file's response time information
   is meaningful above the DETAIL timespan, be sure that
   PERFCLSS is defined in an account code for this file.

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.

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

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
   NLDRVAL1 - NLDM Response Distribution Limits 1
   NLDRVAL2 - NLDM Response Distribution Limits 2
   NLDRVAL3 - NLDM Response Distribution Limits 3
   NLDRVAL4 - NLDM Response Distribution Limits 4
   PERFCLSS - Performance Class (NLDM)
   PLU      - Primary Logical Unit
   SLU      - Secondary Logical Unit
   SLULINK  - SLU Link
   TMOFFSET - TIME OFFSET
   RTMCNTR  - Objective Counter Number
   RTMPCOBJ - Objective Percentage
   RTMRDEF  - Response Definition
   RTMROBTM - Objective Response Time
   RTMXDMN  - 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 CA MICS data for TSO sessions in the
   element PLU.  The duplicate PLU values 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 Examples

1. Assume that the data center response time objectives state
   that 90 percent of all total responses must be less than
   five seconds and that NLDM is parameterized for
   Performance Class (PERFCLSS) 'TSO' so that NLDRVAL2
   (response time limit bucket 2) is set at five seconds.
   Select those sessions that do not meet the stated
   objective.  List each session and any relevant
   information.

   DATA WKFILE
     (RENAME=(PLU=APPL SLU=TERMINAL RTMAVTTM=RESPONSE
              RTMPCOBM=PCT_MET));
   SET &PNVSX..NVSRTM01;
   IF PERFCLSS = 'TSO';
   IF RTMPCTR2 LT 90; /* SELECT LESS THAN 90 % */
     PROC PRINT DATA=WKFILE;
   BY NETWRKID SYSID;
   VAR APPL SLULINK TERMINAL RESPONSE PCT_MET;
   TITLE 'RESPONSE OBJECTIVE # 3 LESS THAN 90 %';
   RUN;

2. Produce a report showing by hour those applications
   missing their response objectives using today's data.

   DATA WKFILE (RENAME=(PLU=APPL));
   SET &PNVSX..NVSRTM01;
   IF RTMNRROM=0; /* =1 IN DETAIL IF OBJ MET */

   PROC FREQ DATA=WKFILE;
   TABLES APPL * HOUR / NOROW NOCOL NOCUM;
   TITLE 'DETAIL NVSRTM01, RESPONSE OBJECTIVE MISSED';
   RUN;