Rules for CF connections

Moving a CF connection to a target object (processors, CSSs or partitions) must not influence objects on the target. Therefore, in certain cases, CF connections cannot be copied because this operation would affect other connections.

If one of the CF connection CHPIDs is not copied (deselected in the Map CHPIDs page), then the CF connection is not copied and the physical connectivity is also kept on the source CF connection.

The following rules apply for the different object types:

• Copying a processor
  • All CF connections which are not deselected in the Map CHPIDs page are copied to the new target processor.
  • For CF connections within the processor, both source and target of the connection are moved to the new processor.
  • If the CF connection to be copied is completely within the same processor, the source connection is kept in the source processor. Otherwise, if both ends of the connections are in different processors, the origin of the connection is moved to the target and disconnected in the source.
• Copying a CSS
  • All CF connections are copied to the new target CSS, with the following exceptions:
    • Connections established with spanned CHPIDs in the source CSS are not copied.
    • If a CSS with internal CF connections is copied to another processor, both connection ends must be within the same CSS. Otherwise, the CF connections are not copied.
  • If both connection ends of the source CF connection are within the source CSS, the source connection is kept. Otherwise, if the connection target is in a different CSS, the source connection is moved to the target and disconnected in the source.
• Copying a partition
  • All CF connections using dedicated CHPIDs are moved to the target partition.
  • If a source OS partition that you want to copy within the same CSS is involved in CF connections, then the following applies:

    A CF connection using a spanned, shared or reconfigurable CHPID is copied if the CHPID is not mapped to a different CHPID in the target. Shared or spanned source CHPIDs must not be spanned to different CSSs in the target (then the same physical cable is used and the copy operation just enhances the access list).

  • A CF connection using a spanned, shared or reconfigurable CHPID is not copied if the target partition is in a different processor or CSS. A CF connection is also not copied if the copied partition is a CF or CF/OS partition.
  • Internal CF connections are not copied if the partition is copied to a different processor.
  • If the partition is copied within the same CSS, the source connection is kept, except for a dedicated CHPID. Otherwise, if the partition is copied to a different processor/CSS, the source connection is moved to the target and disconnected in the source.