You can start DMD in any of the following ways:
- By using an MVS™ procedure
from the MVS operator console.
A sample start procedure is provided in SEZAINST(DMD).
- By issuing the dmd command from the z/OS® UNIX shell.
- By using the COMMNDxx member of parmlib.
This member enables the DMD to be automatically started after an IPL
of the system. For information about configuring and using the COMMNDxx member of parmlib, see z/OS MVS Initialization and Tuning Reference.
- By using the AUTOLOG statement in the TCP/IP profile. For information
about the AUTOLOG statement, see z/OS Communications Server: IP Configuration
Reference.
Tips: - Do not start the DMD using the AUTOLOG statement in a stack's
profile if you are running in a CINET environment with more than one
stack configured. If a stack is configured using AUTOLOG to start
and stop the DMD each time the stack starts and stops, it is difficult
to maintain a stable running instance of the DMD in a multi-stack
environment. In a multi-stack environment, you should use another
method to automate starting the DMD when the system is started, such
as using the COMMNDxx member of parmlib.
- When you start the DMD from an MVS procedure,
set the environment variables using the STDENV DD statement in the
DMD procedure.
- If you start the DMD from the z/OS shell
and you stop the shell environment from scrolling, when the daemon
needs to display data to the shell, it might stop and wait indefinitely
for the shell to scroll and make output buffer space available for
the data.
Restriction: Only one instance of the DMD can run on a z/OS image. If you attempt to start
a second instance, the second DMD will fail.