Only perform a cold start if you cannot restart the queue manager any other way. Performing a cold start enables you to recover your queue manager and your object definitions; you will not be able to recover your message data. 1. Delete all logs of your current queue manager 2. Create a dummy queue manager 3. move all logs from dummy queue manager to current queue manager directory 4. restart the current queue manager 5. delete dummy queue manager When you have restarted, all your WebSphere® MQ objects are defined and available for use, but there is no message data. Note: Do not reinitialize a queue manager while it is part of a cluster. You must first remove the queue manager from the cluster (using RESET CLUSTER commands on the other queue managers in the cluster), then reinitialize it, and finally reintroduce it to the cluster as a new queue manager. This is because during re-initialization, the queue manager identifier (QMID) is changed, so any cluster object with the old queue manager identifier must be removed from the cluster.