In this section we provide examples of CTN reconfiguration operations: In this sample we add the System MUSCA to the existing CTN  CTN_New . MUSCA is part of  the inactive CTN CTN3 and is therefore ready to be added to  CTN_New . We select the CTN ID  CTN_New  to be the receiving CTN. Then we click on “Add systems to  CTN” under STP ACTIONS. A window with all available Systems and their corresponding  CTNs is shown. In our case only MUSCA CPC is available. We select MUSCA by clicking on  its name and then continue (NEXT), as shown in Figure 4-16. Note:  A server must be part of a CTN (active or inactive) to be added to an existing CTN. A window which shows the target configuration will then be shown. We accept this by clicking  APPLY. The next window provides an overview of the system(s) that will join.  The message shown in Figure 4-17 on page 107 informs that the CTN ID for the server  selected to join the existing CTN will change to match the target CTN ID. 4.3.1 Adding a server to an existing CTN and re-assigning roles 4.3 CTN reconfigurations Draft Document for Review January 6, 2020 11:23 pm 8480ch04.fm GLYPH<SM590000> Adding a server to a CTN and re-assigning server roles GLYPH<SM590000> Splitting a CTN GLYPH<SM590000> Merging two CTNs Figure 4-16 Add a server to an existing CTN - selecting the server 106  IBM Z Server Time Protocol Guide