content_image/1005689.jpg content_image/1005698.jpg
<img src='content_image/1005689.jpg'>

The next windows shows how the new configuration will look like. If the proposed configuration matches the expectation, we confirm by clicking on “NEXT”. After the changes were successfully applied, the message ACT39295I is displayed and the new roles are active. 

## 4.2.5 Deconfiguring a CTN 

If a CTN is no longer needed, it can be deconfigured. All roles from the servers in the CTN are removed. In this example a single server CTN will be deconfigured, leaving LEPUS in unsynchronized state (STP stratum 0). We select the CTN ID to be deconfigured, then we choose “Deconfigure CTN” under STP ACTIONS, as shown in Figure 4-15 on page 105. 

<img src='content_image/1005698.jpg'>

Note:  If the CTN is restricted, it must be switched to unrestricted before deconfiguring the CTN. Also server role changes can be performed only if the CTN is unrestricted. 

The next pop-up window appears stating that the “Deconfigure CTN” task is disruptive. Enter the password of the HMC user and click on APPLY. After the progress pop-up disappeared, message ACT39285I confirms the successful execution of the “Deconfigure CTN” task. LEPUS is now unsynchronized (STP Stratum 0). 

Attention:  Any sysplex operations will be suspended and any z/OS systems running in STP mode will go into a disabled wait  state if CTN deconfiguration is performed. This is a HIGHLY DISRUPTIVE action. 

