Verifying that you can start and stop the monitoring server

At this point in the configuration, you can verify that the monitoring server can be started and stopped.

Procedure

Start the hub monitoring server.
If your hub is on a z/OS® system, start the monitoring server started task (by default, IBMDS):
```
S IBMDS
```
If your hub is on a distributed system, see the IBM Tivoli Monitoring Installation and Setup Guide.
If you have configured remote monitoring servers on z/OS, start the started task for each server:
```
S IBMDS
```

In the RKLVLOG for the monitoring server address space, look for the following messages to indicate successful startup:

KDSMA001   Tivoli Enterprise Monitoring Server (TEMS) data collection server started.
KO4SRV032  Tivoli Enterprise Monitoring Server (TEMS) startup complete.

Look also for the following messages to indicate successful establishment of a communications path by the local location broker:
```
KDSNC007   Local Location Broker is active
KDSNC004   Bind of local location broker complete= protocol_name:address
```
If the monitoring server is a hub, additional messages indicate successful establishment of a communications path by the global location broker:
```
KDSNC004   Bind of global location broker complete= protocol_name:address
KDSNC005   Bind of global location broker complete at address protocol_name:address on port number
KDSNC008   Global Location Broker is active
```
For a remote monitoring server, look for a message similar to this one to indicate a successful connection with the hub:
```
KDS9141I   The TEMS RTEname:CMS is connected to the hub TEMS protocol_name:address
```
The number of messages depends on the number of protocols defined.
Stop the monitoring server started task:
```
P IBMDS
```
If you encounter problems starting or stopping the monitoring server, refer to IBM Tivoli Monitoring: Troubleshooting Guide.