7. PARAMETERS › 7.3 Unit-level Parameters › 7.3.9 PLU Identification Routine (SNTPLURT)
7.3.9 PLU Identification Routine (SNTPLURT)
This section explains how to code the Primary Logical Unit
(PLU) Identification Routine (SNTPLURT) in prefix.MICS.PARMS.
The SNTPLURT routine is not necessary for data collected by
the CA NetSpy NCP interface (except for network session
accounting/network gateway accounting data). Moreover, the
routine should not be necessary for data collected by the CA
NetSpy VTAM interface, as long as you have correctly
specified the ALIAS parameter in the CA NetSpy initialization
parameters. See the CA NetSpy documentation for additional
information.
Why and When You Need to Code SNTPLURT
--------------------------------------
Some VTAM applications, such as TSO and TAF (Terminal Access
Facility, which runs under NetView or NCCF), have multiple
application (APPL) statements defined to VTAM. This results
in multiple names for a single application in NetView Session
Monitor, CA NetMaster NTS, and NPM session data, causing two
special problems for data in the CA MICS Network Analyzer
files.
The first problem applies to NetView, CA NetMaster, NPM
session, and NPM or CA NetSpy network session
accounting/network gateway accounting data for any
application with multiple APPL statements defined.
If an application has multiple APPL statements defined, the
CA MICS element Primary Logical Unit (PLU) contains different
values for different sessions with this application. This
can greatly increase the size of files that have PLU as a
sequence/summary element. NPM and its session data
collection function, if properly tailored, circumvent this
problem (discussed below); which NetView and CA NetMaster do
not. The affected files are SNTPSY, SNTPSU, SNTNPL, SNTNAC,
NVSLSY, NVSVBF, NVSNSA, NVSNSC, NVSRTE, and NVSRTM.
The second problem is unique to NetView accounting and
availability data and CA NetMaster accounting data for TSO
sessions.
Two sessions are recorded by NetView and CA NetMaster for
every TSO user session: one for the initial session with
TCAS and one for the session with a TSO address space. This
number is carried in the CA MICS element Number of Sessions
(NSCNMSES). Although NSCNMSES is technically accurate, you
may find it more useful for accounting purposes to think of
it as only one session.
You can code the CA MICS Network Analyzer routine SNTPLURT in
prefix.MICS.PARMS to convert the multiple PLU values to a
single PLU name for the application in NetView, CA NetMaster,
CA NetSpy or NPM network session accounting data, and, if
required, in NPM session data. SNTPLURT also increments
NSCNMSES by one only for each TSO user session.
As indicated earlier, NPM session data collection eliminates
the problem of incurring multiple values for the PLU element
for applications that have multiple application statements
defined. See the parameters SYN, SYNCOUNT, and SYNMASK in
the APPL initialization statement in the NPM documentation.
Coding the Exit
---------------
SNTPLURT is invoked for the following NPM files if you code
the SAS statement IF COMPT= 'SNT NPM' THEN DO; in the
routine:
o NPM User Activity (SNTPSU) File
o NPM System Activity (SNTPSY) File
o NPM Link Activity (SNTNPL) File
o NCP Network Accounting (SNTNAC) File
SNTPLURT is invoked for the following NLDM files (which may
contain NetView Session Monitor/NLDM or CA NetMaster NTS
data) if you code the SAS statement IF COMPT= 'SNT NLDM' THEN
DO; in the routine:
o NLDM System Activity (NVSLSY) File
o NLDM Link Activity (NVSNLL) File
o NLDM Session Accounting (NVSNSA) File
o NLDM Session Connectivity (NVSNSC) File
o NLDM Response Time (NVSRTM) File
o NLDM Route (NVSRTE) File
o NLDM VTAM BIND Failure (NVSVBF) File
SNTPLURT is written in the SAS language. The testing and
accuracy of the process is the responsibility of the user.
However, the CA MICS Network Analyzer provides a sample
SNTPLURT exit routine and certain program aids to help verify
the accuracy of your modifications to the routine. The
worksheet for structuring the SNTPLURT exit routine is shown
in Figure 7-12.
To code the SNTPLURT exit for an application, review the
major node definitions in SYS1.VTAMLST that contain the APPL
statements for that application. See the IBM VTAM
documentation for information on defining applications to
VTAM.
Below are examples of how APPL statements could appear for
two TSO systems on two different hosts, and of two
alternative examples for coding SNTPLURT:
** Note: The first APPL statement below is for TCAS **
TSO10 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO
** Note: The additional APPL statements below are for **
** as many users as will be logged on to TSO10 at one time.**
TSO1001 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0001
TSO1002 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0002
- - -
- - -
- - -
TSO1060 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0060
** Note: The first APPL statement below is for TCAS **
TSO15 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO
** Note: The additional APPL statements below are for **
** as many users as will be logged on to TSO15 at one time.**
TSO1501 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0001
TSO1502 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0002
- - -
- - -
- - -
TSO1540 APPL AUTH=AUTH(NOACQ=PASS,NVPACE,TSO,NOPO), X
EAS=1,ACBNAME=TSO0040
In the first example below, the SNTPLURT routine does the
following:
o Sets the value of PLU to TSO10 for all synonym values of
TSO10 (that is, TSO1001 thru TSO1060).
o Sets the value of PLU to TSO15 for all synonym values of
TSO15 (that is, TSO1501 thru TSO1540).
o Prevents the NVSNSA file element, Number of Sessions
(NSCNMSES) from being incremented for TCAS sessions using
TSO10 and TSO15, by setting the Number of Sessions counter
to zero for all TCAS sessions in the DETAIL timespan.
* THIS ROUTINE IS USED TO SET THE VALUE OF PLU FOR
* APPLICATIONS, SUCH AS TSO, THAT HAVE SYNONYMS DEFINED.
*
*
* EXAMPLE 1:
;
IF COMPT='SNT NPMS' THEN DO; /* NPM SESSION DATA*/
IF PLU=:'TSO10' THEN PLU='TSO10 ';
IF PLU=:'TSO15' THEN PLU='TSO15 ';
END;
/* NETVIEW SESSION MONITOR OR CA NetMaster NTS DATA*/
IF COMPT='SNT NLDM' THEN DO;
IF PLU='TSO10' THEN NSCNMSES=0;
ELSE IF PLU=:'TSO10' THEN PLU='TSO10 ';
IF PLU='TSO15' THEN NSCNMSES=0;
ELSE IF PLU=:'TSO15' THEN PLU='TSO15 ';
END;
The SNTPLURT routine in the second example is similar to the
routine shown in the first example in that NSCNMSES is not
incremented for TCAS sessions in TSO10 and TSO15. However,
instead of setting NSCNMSES to zero for TCAS sessions, the
routine deletes the observations for the TCAS session
altogether.
* EXAMPLE 2:
;
IF COMPT='SNT NPMS' THEN DO; /* NPM SESSION DATA*/
IF PLU=:'TSO10' THEN PLU='TSO10 ';
IF PLU=:'TSO15' THEN PLU='TSO15 ';
END;
/* NETVIEW SESSION MONITOR OR CA NetMaster NTS DATA */
IF COMPT='SNT NLDM' THEN DO;
IF PLU='TSO10' THEN DO;
EXITS=BLANKS;
GOTO OPTN_DEL;
END;
IF PLU='TSO15' THEN DO;
EXITS=BLANKS;
GOTO OPTN_DEL;
END;
+------------------------------------------------------------------------------+
| INSTALLATION PREPARATION WORKSHEET: PLU Identifier Exit Routine |
| Definition |
| PARMS Library Member is SNTPLURT |
| Reference Section: 7.3.9, CA MICS Network Analyzer Guide |
+------------------------------------------------------------------------------+
| |
| /* ----------------------------------------------------------------- */ |
| /* THIS ROUTINE IS USED TO SET THE VALUE OF PLU FOR APPLICATIONS, */ |
| /* SUCH AS TSO, THAT HAVE SYNONYMS DEFINED. */ |
| /* */ |
| /* */ |
| /* FOR EXAMPLE: */ |
| /* */ |
| /* IF COMPT='SNT NPMS' THEN DO; /* NPM SESSION DATA*/ */ |
| /* IF PLU=:'TSO10' THEN PLU='TSO10 '; */ |
| /* IF PLU=:'TSO15' THEN PLU='TSO15 '; */ |
| /* END; */ |
| /* IF COMPT='SNT NLDM' THEN DO; /* NETVIEW SESSION MONITOR DATA*/ */ |
| /* IF PLU='TSO10' THEN NSCNMSES=0; */ |
| /* ELSE IF PLU=:'TSO10' THEN PLU='TSO10 '; */ |
| /* IF PLU='TSO15' THEN NSCNMSES=0; */ |
| /* ELSE IF PLU=:'TSO15' THEN PLU='TSO15 '; */ |
| /* */ |
| /* END; */ |
| /* */ |
| |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| ________________________________________________________________________ |
| |
| |
+------------------------------------------------------------------------------+
| ....5...10...15...20...25...30...35...40...45...50...55...60...65...70.. |
+------------------------------------------------------------------------------+
Figure 7-12. PLU Identifier Exit Routine Definition Worksheet
Copyright © 2014 CA.
All rights reserved.
|
|