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

7.3.1.8 IBMTCP SMF and DEFAULT IBMTCP SMF Statements

IBMTCP SMF
----------
This statement is required only when you have coded TCP on
the DATA SOURCE statement, and you must override the default
TCP SMF record type that is defined with DEFAULT IBMTCP SMF.

The purpose of this statement is to define the SMF record
type, 118 or 119, so that the z/OS Communication Server is
configured for generation. Each statement uniquely identifies
the SMF record type from a specific system that will be
processed and saved in the CA MICS database. You can specify
a unique SMF record type for an ORGSYSID that will allow you
to process SMF record type 118 for one ORGSYSID while
processing SMF record type 119 for another.

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

IBMTCP SMF = nnn

where nnn is SMF record type 118 or 119.


DEFAULT IBMTCP SMF
------------------
Use this optional statement to specify a default SMF record
type for data produced by the z/OS Communication Server for
TCP/IP network. TCP/IP can be configured to generate SMF
record type 118, SMF record type 119, or both simultaneously.

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 IBMTCP SMF record type for each
  DATA SOURCES statement that includes TCP, UNLESS overridden
  with an IBMTCP SMF nnn statement that follows the DATA
  SOURCES statement.

The DEFAULT IBMTCP SMF statement has the following format:

DEFAULT IBMTCP SMF = nnn

where nnn is SMF record type 118 or 119.

Notes:

The SMF record type must either be 118 or 119, and, if coded,
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).