EZD1807I

Explanation
 The Communications Server SMTP (CSSMTP) application
could not initialize because it detected an error. 
 In the
message text:  jobname
The job name of the task that started the CSSMTP application. 
reason
The reason the initialization failed: CANNOT ACCESS JESSPOOL
The CSSMTP application is not defined for access to SAF JESSPOOL
resources.
CANNOT ACCESS SERVAUTH
The CSSMTP application is not defined for access to SAF SERVAUTH
resources.
CONFIGURATION FILE ERRORS
The CSSMTP application found an error in the configuration file.

CONFIGURATION FILE NOT AVAILABLE
The CSSMTP application cannot open the configuration file. 
CSSMTP JOBNAME ALREADY STARTED
Only one copy of the CSSMTP application can be started with this
job name and one copy is already started.
EXTERNAL WRITER NAME extWrtName ALREADY IN
USE
 Only one copy of the CSSMTP application can be started with this
external writer name.
extWrtName is the external writer name.

INTERNAL ERRORS 
Indicates an internal error in the application.
INVALID LOG FILE TYPE
The log file format PDS or PDSE is not allowed.
JES NOT AVAILABLE
The CSSMTP application cannot use the functions of  JES2 or JES3
subsystems.
LOGFILE NOT AVAILABLE
The CSSMTP application cannot open the log file.  
NOT STARTED AS STARTED PROCEDURE
The CSSMTP application can be started only as a started procedure.
START OPTION ERRORS
The CSSMTP application found an error in a start options parameter
in the started procedure. 

System action
 The application ends.

Operator response
 The operator response is based on the reason value:
 CSSMTP JOBNAME ALREADY STARTED
Start this CSSMTP application with a different job name.    For
example, you could use this form of the start command: s cssmtp.newJobName

All other reason values
Contact the system programmer.

System programmer response
 The system programmer response is
based on the reason value:  CANNOT ACCESS JESSPOOL
Define CSSMTP with ALTER access to the local-node.** JESSPOOL
class resource. See the information about optional
security for CSSMTP in z/OS Communications Server: IP Configuration
Guide for details about defining the JESSPOOL class
profile for the CSSMTP application.
CANNOT ACCESS SERVAUTH
Define CSSMTP with READ access to the EZB.CSSMTP.** SERVAUTH class
resource. See the information about optional
security for CSSMTP in z/OS Communications Server: IP Configuration
Guide for details about defining SERVAUTH class
profile for the CSSMTP application.
EXTERNAL WRITER NAME extWrtName ALREADY IN
USE
Start this CSSMTP application with a different external writer
name.    See the information about the ExtWrtName
statement in z/OS Communications Server: IP Configuration
Reference for information about configuring the CSSMTP
application.
CONFIGURATION FILE NOT AVAILABLE
Ensure that the correct configuration file is configured in the
CONFIG DD statement.    See the information about the CSSMTP sample started procedure in z/OS Communications Server: IP Configuration
Reference for information about configuring CONFIG
DD for the CSSMTP application.
JES NOT AVAILABLE
Ensure that the JES subsystem is configured correctly.   See the
information about configuring and starting
CSSMTP in z/OS Communications Server: IP Configuration
Guide for information about configuring JES subsystems.
CONFIGURATION FILE ERRORS 
Examine the log file for the configuration error and correct it.
   See the information about the Communications
Server SMTP application in z/OS Communications Server: IP Configuration
Reference for information about configuring the CSSMTP
application.
START OPTION ERRORS
Examine STDOUT and correct the start options parameter that is
incorrect.    See the information about starting
the CSSMTP application in z/OS Communications Server: IP Configuration
Reference for information about the start options for
the CSSMTP application.
LOGFILE NOT AVAILABLE
Ensure that the correct log file is configured in the LOGFILE
DD statement.   See the information about the CSSMTP
sample started procedure in z/OS Communications Server: IP Configuration
Reference for information about configuring LOGFILE
DD for the CSSMTP application.
INVALID LOG FILE TYPE
On the LOGFILE DD statement, define a log file type that is not
PDS or PDSE.  See the information about the CSSMTP
sample started procedure in z/OS Communications Server: IP Configuration
Reference for information about configuring LOGFILE
DD for the CSSMTP application.
INTERNAL ERRORS
Examine the log file for the internal error and correct the error
if possible. 
NOT STARTED AS STARTED PROCEDURE
Start the CSSMTP application as a started procedure.    See the
information about configuring and starting
CSSMTP in z/OS Communications Server: IP Configuration
Guide for details about starting the CSSMTP application.

 See the information about gathering
diagnostic information about CSSMTP  problems in z/OS Communications Server: IP Diagnosis Guide to determine what  documentation you should
obtain before contacting IBM® Service.

User response
 Not applicable.

Problem determination
 See the system programmer response.

Source
 z/OS® Communications
Server TCP/IP: CSSMTP

Module
 ezamlmn

Routing code
 10

Descriptor code
 12

Automation
 This message is written to the system console and
log file for CSSMTP.  This message is a good candidate for automation.
Automation can alert you if the CSSMTP  application initialization
fails.

Example
  EZD1807I CSSMTP1 ERROR IN INITIALIZATION : CONFIGURATION FILE NOT AVAILABLE