This describes steps you must follow to start your deployment manager
on an MVS image different from the one on which it was originally configured.
About this task
The ability to start your deployment manager on an MVS image different
from the one on which it was originally configured is handy if your original
system becomes unavailable, either through a planned outage or a system failure.
This way, you can still start and stop applications, make configuration updates,
utilize monitors that use the PMI interface, perform other control functions,
and so on. Perform the following steps to start your deployment manager on
a different MVS image and ensure that client requests will successfully find
the deployment manager at its new location.
Note: This works only if the deployment
manager on the original MVS image is down. WebSphere Application Server for
z/OS allows only one copy of the deployment manager to run at one time for
any given cell.