7. PARAMETERS › 7.3 Unit-level Parameters › 7.3.1 Processing Options (SNTOPS) › 7.3.1.9 NETSPY SMF and DEFAULT NETSPY SMF Statements

7.3.1.9 NETSPY SMF and DEFAULT NETSPY SMF Statements

NETSPY SMF
----------
The purpose of this statement is to define the SMF record
type that CA NetSpy generates.  You can use it to override
the default NETSPY SMF record type that is defined with
DEFAULT NETSPY SMF. You can also use it to define the SMF
record type when there is no DEFAULT NETSPY SMF statement.

You can specify multiple statements (only one per ORGSYSID
group) if you have more than one CA NetSpy product running on
different systems, each generating SMF records that you want
to process with the CA MICS Network Analyzer product.  Each
statement uniquely identifies the SMF record number from a
specific system that will be processed and saved in the CA
MICS database.

This statement must follow the DATA SOURCE statement and
precede another NETWORK ID or ORGSYSID statement.  An error
message is issued if the statement is not coded in the proper
order.

The NETSPY SMF statement has the following format:

NETSPY SMF = nnn

where nnn is a valid SMF record type in the range of 128 to
255 and cannot be blank.


DEFAULT NETSPY SMF
------------------
Use this optional statement to specify a default SMF record
type for data produced by CA NetSpy. Omit this statement if
your data center does not use CA NetSpy or you do not want to
process CA NetSpy data in the unit.

The following rules apply regarding this statement:

o This keyword must be coded after the first NETWORK ID
  statement and before the first ORGSYSID statement.

o If this keyword is coded, the specified SMF record type
  (nnn) will be used as the NETSPY SMF record type for each
  DATA SOURCES statement that includes NSPY, UNLESS
  overridden with a NETSPY SMF nnn statement that follows the
  DATA SOURCES statement.

The DEFAULT NETSPY SMF statement has the following format:

DEFAULT NETSPY SMF = nnn

where nnn is a valid SMF record type in the range of 128 to
255 and cannot be blank.

Notes:

If you specify SMF record types using either of these
statements in prefix.MICS.PARMS(SNTOPS), you must ensure that
the same SMF record types are present on the INPUTSOURCE
statement in sharedprefix.MICS.GENLIB(SNTGENIN).

If you update the SNTGENIN, do the following:

1. Submit sharedprefix.MICS.CNTL(SNTCGEN).

2. Edit prefix.MICS.PARMS(JCLGENU) so that it contains no
   values. If values are present, remove them.

3. Submit prefix.MICS.CNTL(JCLGENU).

4. Submit prefix.MICS.CNTL(SNTPGEN).