6. DATA SOURCES › 6.3 Correlating Data Sources › 6.3.8 Establishing a Single Value for PLU (SNTPLURT)

6.3.8 Establishing a Single Value for PLU (SNTPLURT)

Some VTAM applications, such as TSO and TAF (Terminal Access
Facility, which run under NetView or NCCF), have multiple
application (APPL) statements defined to VTAM.  Multiple
names for a single application in NetView Session Monitor, CA
NetMaster NTS, and NPM session data can result, causing two
special problems for data in the CA MICS Network Analyzer
files:

o The first problem applies to NetView, CA NetMaster, NPM
  session, and NPM/CA NetSpy network session
  accounting/network gateway accounting data for any
  application with multiple APPL statements defined.

o The second problem is unique to NetView accounting and
  availability data and to CA NetMaster accounting data for
  TSO sessions.

  These problems are discussed below.

   o  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, circumvents this problem (discussed below);
      NetView and CA NetMaster do not address the problem.
      The affected files are SNTPSY, SNTPSU, SNTNPL, SNTNAC,
      NVSLSY, NVSVBF, NVSNSA, NVSNSC, NVSRTE, and NVSRTM.

    o Two sessions are recorded by NetView and CA NetMaster
      during 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 can think of it,
      for accounting purposes, 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/NPM network session accounting data, and, if
required, in NPM session data.  SNTPLURT also increments
NSCNMSES by one only for each TSO user session.  See Chapter
7 for information on how to code SNTPLURT and for examples of
how the APPL statements for TSO and TAF are likely to appear
in the major node that contains their definitions in
SYS1.VTAMLST.

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 SYNCOUNT and SYNMASK in
the APPL initialization statement in the NPM documentation.

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.