Question & Answer
Question
The Defense Manager Daemon (DMD) cannot be started. On DMD startup, the following message sequence is written to the MVS console:
EZD1610I THE DEFENSE MANAGER DAEMON INITIALIZATION SEQUENCE HAS BEGUN
EZD1617I AN ERROR OCCURRED WHILE READING THE DEFENSE MANAGER DAEMON CONFIGURATION FILE
/etc/security/dmd.conf - RETURN CODE 2
EZD1604I THE DEFENSE MANAGER DAEMON SHUTDOWN SEQUENCE HAS BEGUN
EZD1605I THE DEFENSE MANAGER DAEMON SHUTDOWN SEQUENCE HAS COMPLETED
Answer
The message sequence indicates that the DMD configuration file cannot be read.
The configuration file must exist and the DMD must have the right permissions to read it.
If the configuration data is not in the default location (that is, /etc/security/dmd.conf), ensure that the environment
variable DMD_FILE is set to the name of the MVS data set or z/OS UNIX file that contains the configuration data.
If the DMD is defined with a non-zero UID, ensure that the DMD has permission to read the configuration file. This requires that the DMD user has both read access to the configuration file, as well as access to the directory containing the configuration file.
Tip: The /var/dm directory must be set up to allow DMD to create, delete, read, and write files to it. You might
want to create the configuration file in the /var/dm directory and use the DMD_FILE environment variable
to specify the configuration file.
Product Synonym
ZOSCS COMMSERVER
Was this topic helpful?
Document Information
Modified date:
07 September 2015
UID
dwa1212567