7. PARAMETERS › 7.2 Complex-level Parameters › 7.2.1 Analyzer Definition Statements (SNTGENIN)

7.2.1 Analyzer Definition Statements (SNTGENIN)

A generation definition statement member is provided for the
CA MICS Network Analyzer in
sharedprefix.MICS.GENLIB(SNTGENIN).  The content of SNTGENIN
members is described in Chapter 4 of the CA MICS System
Modification Guide.

If you process CA NetSpy data, you must update the
INPUTSOURCE statement.  You can enter one or more CA NetSpy
SMF record numbers to process in DAY056.

Code an OPTION statement to specify the types of data you
will provide to CA MICS.

INPUTSOURCE Statement
---------------------

o  CA MICS Network Analyzer processes data from IBM TCP/IP
   Communication Services.  The TCP/IP can be configured to
   generate two SMF record types: 118 and 119.  Your data
   center may generate SMF record type 118 from one system
   and 119 from another or generate both record types
   simultaneously from a single system.  The
   sharedprefix.MICS.GENLIB(SNTGENIN) member INPUTSOURCE
   statement must specify both record types if your data
   center needs to process all TCP/IP generated data.

o  The CA MICS Network Analyzer processes data from CA
   NetSpy.  CA NetSpy writes a single SMF record with a
   user-defined SMF record type ranging from 128 to 255
   (decimal).

   Your CA NetSpy administrator selects a record type and
   codes it as "SMF=record number" in the INITPRM member in
   the NETSPY.CNTL library. The default for this parameter is
   SMF=0, which prevents CA NetSpy from recording SMF data,
   so your CA NetSpy administrator must explicitly specify
   this value to effect SMF recording.

   If your data center has defined multiple CA NetSpy SMF
   record numbers, then you must specify all of those numbers
   on the INPUTSOURCE statement in
   sharedprefix.MICS.GENLIB(SNTGENIN).  Select only those CA
   NetSpy SMF record numbers that you want to process with
   DAY056.

Submit sharedprefix.MICS.CNTL(SNTCGEN).  After the SNTCGEN
completes successfully, edit prefix.MICS.PARMS(JCLGENU) so
that it contains no keywords (becomes a blank member) and
then submit prefix.MICS.CNTL(JCLGENU).

OPTION Statement
----------------

The OPTION statement indicates which groups of data elements
are going to be kept in the database.

The valid keywords are:

  NTRI/NONTRI     - Network Token Ring Interface
  SESMGR/NOSESMGR - Session Manager
  TIC3/NOTIC3     - Token Ring Interface Coupler
  X25/NOX25       - X.25 Network
  FRLY/NOFRLY     - Frame Relay
  TCP/NOTCP       - Transport Communication Protocol

You must specify one keyword from each pair.  The keywords
can be specified in any order and must be separated by
one or more blanks.