Starting CSSMTP

Use the S CSSMTP command on an MVS™ console or System Display and Search Facility (SDSF) to start CSSMTP.

Rules:

You must start CSSMTP from a started procedure. A sample started procedure is included in member CSSMTP in SEZAINST. A configuration file is required. A sample CSSMTP configuration file is included in member CSSMTPCF in SEZAINST.
Multiple instances of CSSMTP with different job names can be started with or without stack affinity. Each instance of CSSMTP that is running must be configured with a different external writer name. See ExtWrtName statement for more information.

The following options (in the started procedure) apply to CSSMTP:

-p | -P tcpipJobName

The tcpipJobName parameter is used in a common INET configuration to choose a socket stack for CSSMTP. It is also used for resolver functions. The environment variable _BPXK_SETIBMOPT_TRANSPORT can also specify the tcpipJobName. The -p start option overrides the environment variable. If neither form is used to set the tcpipJobName, then no affinity is used in a common INET configuration.

Results: In a Common INET configuration, there might be more than one TCP/IP stack. CSSMTP acts as a TCP/IP client. In this type of environment, you might want to associate CSSMTP with a specific stack, especially when there are multiple instances of CSSMTP to be started.

The following list shows the priority for establishing TCPIP affinity for socket functions:
1. Start option -p (CSSMTP sets affinity before any socket or resolver calls are made)
2. Environment variable _BPXK_SETIBMOPT_TRANSPORT
3. No affinity
The following list shows the priority for establishing TCP/IP affinity for resolver functions:
1. Application affinity.
2. _BPXK_SETIBMOPT_TRANSPORT.

For resolver affinity information, see z/OS Communications Server: IP Configuration Guide.

-f |-F

This start option indicates that CSSMTP performs a cold start and flushes any checkpoint records from the previous execution of CSSMTP. To use checkpointing, you must set the CHKPOINT DD statement in the started procedure. The default is to use the checkpoint records to restart JES spool files at their last known status.

Tip: Member CSSMTPVL in SEZAINST is a sample job that you can use to allocate a VSAM linear data set that CSSMTP can use for checkpointing.

Result: If a valid CHKPOINT DD statement is not configured, checkpointing is not performed.

For resolver affinity, see z/OS Communications Server: IP Configuration Guide.

If CSSMTP cannot successfully parse the start options, log output is written to stdout and the application exits.

If you want time values that are generated by CSSMTP to appear in local time, you must set the TZ environment variable. If you do not set the TZ environment variable, timestamps created by CSSMTP are in Universal Time Coordinated (UTC) by default.

Set the TZ and configuration code page environment variables in one of the following ways:

Specify TZ using the ENVAR parameter on the PARM statement in the started procedure. For example, use the following code:
```
// PARM=('POSIX(ON) ALL31(ON)', 
// 'ENVAR("CSSMTP_CODEPAGE_CONFIG=IBM-1047"', 
// '"TZ=EST5EDT")/')
```
Export the TZ and configuration code page environment variables in a file specified with the STDENV DD statement. For example, use the following code:
```
//STDENV DD PATH='/etc/cssmtp.env',PATHOPTS=(ORDONLY)
```
In the /etc/cssmtp.env file, use the following code:
```
TZ=EST5EDT
CSSMTP_CODEPAGE_CONFIG=IBM-1047
```

See z/OS Language Environment Programming Guide for more information about specifying runtime options and environment variables. See z/OS UNIX System Services Command Reference for details about setting the TZ environment variables.