

5. DATABASE FILES › 5.2 SNT Information Area › 5.2.12 NLDM Service File (SNTNSV) › 5.2.12.3 Usage Considerations
5.2.12.3 Usage Considerations
This section identifies the special considerations or
techniques related to using the SNTNSV File. Additionally,
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 the
files 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 WEEK 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. These data elements
should only be referenced when the last observed value in
a summarization interval is significant.
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
PLDOMAIN - PLU Domain Name
PLU - Primary Logical Unit
PLUSAPU - PLU Subarea Physical Unit
SLDOMAIN - SLU Domain Name
SLU - Secondary Logical Unit
SLULINK - SLU Link
SLUPU - SLU Physical Unit
SLUSAPU - SLU Subarea Physical Unit
TMOFFSET - Time Offset
NSVCNTR - Objective Counter Number
NSVCOS - Class of Service
NSVEXRTE - Explicit Route Number
NSVPCOBJ - Objective Percentage
NSVRDEF - Response Definition
NSVROBTM - Objective Response Time
NSVRVER - Reverse Explicit Route Number
NSVSTYPE - Session Type
NSVTRPTY - Transmission Priority
NSVVRRTE - Virtual Route Number
NSVXNET - Cross-network Session
Retrieval Examples
1. Assume that the data center response time objectives
state that 90% of all total responses must be less than
five (5) seconds. Assuming NLDM is parameterized for
Performance Class (NSVPCLSS) 'TSO' such that NLDRVAL2
(response time limit bucket 2) is set at 5 seconds, select
those sessions not meeting the stated objective. List
each session and relevant information.
DATA WKFILE;
SET &PSNTX..SNTNSV01;
IF NSVPCLSS = 'TSO';
IF NSVPCTR3 LT 90; /* SELECT LESS THAN 90 % */
PROC PRINT DATA=WKFILE;
ID NETWRKID SYSID;
VAR PLU SLULINK SLU NSVAVTTM;
2. Produce a report showing a count of terminal (SLUs) by
application (PLU) missing their response objectives using
today's data.
DATA WKNSV;
SET &PSNTX..SNTNSV01;
IF NSVNRROM=0; /* =1 IN DETAIL IF OBJ MET */
PROC FREQ DATA=WKNSV;
TABLES PLU * SLU / NOROW NOCOL NOCUM;
Copyright © 2014 CA.
All rights reserved.
 
|
|