The TCP/IP profile record provides profile information
for the TCP/IP stack. The
first or only record always contains the following sections:
- SMF header
- Self-defining section with 21 section triplets
- TCP/IP identification section
- Profile information common section
- Profile information data set name section
See Table 1 for a list of all the sections of information that can be
provided in this SMF record.
This record is created as an event record during the following
processing:
- During the initialization of the stack. In this case, the record
contains the complete profile information for the stack.
- If the profile is changed by the use of the VARY TCPIP,,OBEYFILE
command. In this case, the record contains only changed profile information.
- The NMTP_PICOSecChanged flag bits in the profile information common
section indicate which sections actually contain changed information.
- In the self-defining section, the triplet field values are zero
for sections for which no information was changed, or for those sections
which all the information was deleted from the stack's configuration.
- If deprecated profile statements were specified in the VARY TCPIP,,OBEYFILE
command data set, field NMTP_PicoDepChanged indicates which statements
were processed. If only deprecated statements were processed, the
profile information common and data set name sections are the only
sections of information provided in the SMF record. See Table 1 for
an explanation of deprecated profile statements.
- For the sections that changed, the section in the SMF record contains
all of the information for the section. For example, if a network
interface was added, the whole interface section is included in the
SMF record. Applications need to compare the interface section in
the new record with the interface section in the previous record to
determine which interface was added.
- If the profile data set referenced by the VARY TCPIP,,OBEYFILE
command changed the SMFCONFIG setting from PROFILE to NOPROFILE, one
final SMF event record is created and written to the MVS™ SMF data sets to record this change.
- If the profile data set referenced by the VARY TCPIP,,OBEYFILE
command changed the NETMONITOR SMFSERVICE setting from PROFILE to
NOPROFILE, one final SMF event record is created and written to the
real-time SMF data network management interface (NMI) to record this
change. For more information about the real-time SMF NMI, see Real-time TCP/IP network monitoring NMI.
The SMF record might be created even if some errors occurred
during processing the VARY TCPIP,,OBEYFILE command. Application programs
that process these records must compare the sections of changed information
to the previous profile settings to determine if profile changes actually
occurred.