Previous Topic: 7.3.1.9 NETSPY SMF and DEFAULT NETSPY SMF StatementsNext Topic: 7.3.1.11 DELETEMS and DEFAULT DELETEMS Statements


7.3.1.10 NETTCP SMF and DEFAULT NETTCP SMF Statements


NETTCP SMF
----------
This statement is required only when you have coded NTCP on
the DATA SOURCE statement, you must override the default
record type for CA NetMaster for TCP/IP that is defined with
DEFAULT NETTCP SMF. The purpose of this statement is to
define the SMF record type that your CA NetMaster for TCP/IP
product generates. Each statement uniquely identifies the SMF
record number from a specific system that will be processed
and saved in a CA MICS database.

You can specify multiple statements (only one per ORGSYSID
group) if you have more than one CA NetMaster for TCP/IP
product running on different systems, each generating SMF
records that you want to process with CA MICS Network
Analyzer.

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 NETTCP SMF statement has the following format:

NETTCP SMF = nnn

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


DEFAULT NETTCP SMF
------------------
Use this optional statement to specify a default SMF record
type for data produced by CA NetMaster for TCP/IP. Omit this
statement if your data center does not use NetTCP or if you
do not want to process NetTCP 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 NETTCP SMF record type for each
  DATA SOURCES statement that includes NTCP, UNLESS
  overridden with a NETTCP SMF nnn statement that follows the
  DATA SOURCES statement.

The DEFAULT NETTCP SMF statement has the following format:

DEFAULT NETTCP 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 statement 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).