Use this task to stop a cluster and any application servers that
are members of that cluster.
Before you begin
If you use the Windows® Services facility to start and
stop application servers that are part of a cluster, remember that the cluster
state does not always update correctly. For example, if a cluster is running
and you stop a cluster member through the Services GUI, the cluster state
remains as Started even though the server is no longer running.
About this task
You can stop all application servers that are members of the same
cluster at the same time by stopping the cluster.
Procedure
- Click in the console navigation
tree to access the Server
Cluster page.
- Select those clusters whose members you want stopped.
- Click Stop or Immediate Stop.
- Stop halts each server in a manner that allows the server to finish
existing requests and allows failover to another member of the cluster.
When the stop operation begins the cluster state changes to partially
stopped. After all servers stop, the cluster state becomes Stopped.
- Immediate Stop brings down the server quickly without regard to
existing requests. The server ignores any current or pending tasks. When
the stop operation begins, the cluster state changes to partially stopped.
After all servers stop, the cluster state becomes Stopped.
Results
All application servers in the sysplex associated with
this cluster are issued a request to stop. In addition, a
stop can
be issued against each individual server from the MVS™ console. To shut down the product environment
on a specific system, stop that system daemon. Stopping the system daemon
brings down all other server instances on the system. To bring the product
down on all of your systems, stop the daemons on all systems. When you stop
the location service daemon on one system, it does not bring down the servers
on the other systems.
What to do next
See
Balancing workloads for more information
about the tasks you can complete with clustering.