Steps for configuring SMF records for CSSMTP (optional)

You can use SMF to record CSSMTP events.

Before you begin

CSSMTP can write System Management Facilities (SMF) records for the following cases:

When the configuration has been initialized or modified by a MODIFY REFRESH command, a MODIFY LOG,LEVEL command, or a MODIFY USEREXIT command. A CSSMTP application configuration record (CONFIG subtype 48) is written.
At the end of a connection with a target server, a CSSMTP application connection record (CONNECT subtype 49) is written.
At the end of the processing for each mail message, a CSSMTP application mail message record (MAIL subtype 50) is written.
At the end of the processing of a spool file when all the mail messages have been completed, a CSSMTP application spool file record (SPOOL subtype 51) is written.
When statistical information about the CSSMTP processing at the SMF intervals is required, a CSSMTP application statistical record (STATS subtype 52) is written.

Procedure

Perform the following steps to write SMF records to both the MVS™ SMF data sets and the real-time SMF NMI. Writing SMF records to the MVS SMF data sets and writing SMF records to the real-time SMF NMI are two independent functions and are controlled by different configuration parameters.

Add a SMF119 statement to the CSSMTP configuration file. This configuration parameter controls which SMF record types are written to the MVS SMF data sets. For example:
```
SMF119 
	{
	CONFIG YES
	SPOOL YES
	MAIL NO
	CONNECT YES
	STATS YES
	}
```
In this example, the CONFIG, SPOOL, CONNECT and STATS records will be written to MVS SMF data sets and not the MAIL record.
Restart the CSSMTP task or issue a MODIFY REFRESH command to dynamically update CSSMTP with the new SMF119 statement values.
Update the TCP/IP profile NETMONITOR statement to forward all of the CSSMTP SMF records that are associated with the CONFIG, SPOOL, CONNECT, and STATS types to an application using the real-time SMF NMI, SYSTCPSM. These record types are both connection oriented and non-connection oriented (see 5). For more information about SYSTCPSM, see z/OS Communications Server: IP Programmer's Guide and Reference.
```
NETMONITOR SMFSERVICE CSSMTP
```
For the descriptions of the SMF records see z/OS Communications Server: IP Programmer's Guide and Reference.
Update the TCPIP profile NETMONITOR statement to forward all the CSSMTP SMF records associated with the MAIL type to an application using the real-time SMF NMI, SYSTCPSM.
```
NETMONITOR SMFSERVICE CSMail
```
For more information about SYSTCPSM, see z/OS Communications Server: IP Programmer's Guide and Reference.
Special considerations for CSSMTP application and NETMONITOR in a CINET environment:
- The CSSMTP application can be started with the -p parameter to set stack affinity. This enables that all of the SMF records will be written to the real-time SMF NMI associated with the stack whose name was specified on the -p parameter. This forces connection oriented SMF records (CONNECT) and non-connection oriented SMF records (CONFIG, SPOOL, MAIL and STATS) to go to the same stack. The CSSMTP and CSMAIL NETMONITOR parameters should be specified in the profile data sets of the stack name to match the name specified on the -p parameter.
- If the CSSMTP application is started without the -p parameter and multiple stacks are active, then a network management application can not determine the stack that records will be written to. The CSSMTP and CSMAIL NETMONITOR parameters should be specified in the profile data sets of all stacks, so that network management applications can obtain all the records. The network management application will not get redundant records. In this case CSSMTP writes the records to the first stack with an active SMFService application and with the appropriate SMFSERVICE CSMAIL or CSSMTP parameter set.