About this task
Before you perform an upgrade or uninstall, install a fix pack, or perform maintenance activities, ensure that all
Tivoli Workload Scheduler processes and services are stopped. Follow these steps:
- If you have jobs that are currently running on the workstation, wait for them to finish. To determine which are not finished, check for jobs that are in the exec state. When there are no jobs in this state, and you have allowed sufficient time for all events to be distributed in your network, you can continue with the rest of the procedure.
- If the workstation that you want to stop is not the master domain manager, unlink the workstation by issuing the following command from the command line of the master domain manager:
conman "unlink workstationname;noask"
- All Tivoli Workload Scheduler processes on the workstation must then be stopped manually. From the command line, while logged on as the <TWS_user>, use the following command:
conman “stop;wait”
- From the command line, stop the netman process as follows:
- UNIX
- Run:
conman “shut"
Note: Do not use the UNIX kill command to stop Tivoli Workload Scheduler processes.
- Windows
- Run the shutdown.cmd command from the Tivoli Workload Scheduler home directory.
- If the workstation is at V8.4 or higher, stop the SSM agent, as follows:
- On Windows, stop the Windows service: Tivoli Workload Scheduler SSM Agent (for <TWS_user>).
- On UNIX, run stopmon.
- If you are updating an agent, remove (unmount) any NFS mounted directories from the master domain manager.
- If you are upgrading an installation that includes the connector, stop the connector.
- Stop the WebSphere® Application Server using the conman stopappserver command (see Starting and stopping the application server and appservman)
To verify if there are services and processes still running, complete the following steps:
- UNIX
- Type the command:
ps -u <TWS_user>
Verify that the following processes are not running: netman, mailman, batchman, writer, jobman, JOBMAN, stageman, logman, planman, monman, ssmagent.bin, and appservman.
- Windows
- Run Task Manager, and verify that the following processes are not running: netman, mailman, batchman, writer, jobman, stageman, JOBMON, tokensrv, batchup, logman, planman, monman, ssmagent, and appservman.
Also, ensure that no system programs are accessing the directory or subdirectories, including the command prompt and Windows Explorer.