The manner in which a dynamic VIPA IP address should be moved to another stack. A value of none(1) indicates that moveable status does not apply to this DVIPA. This value would be set for entries where backup is set as the value for the ibmMvsDVIPAOrigin and ibmMvsDVIPAStatus objects. For DVIPA IP addresses activated as the result of a VIPADEFINE configuration statement, a value of immediate(2) means that this dynamic VIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by executing a VIPADEFINE for the same dynamic VIPA. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new owning stack. A value of whenIdle(3) means that this dynamic VIPA can be moved to another stack when there are no connections for this dynamic VIPA on this stack. While there are existing connections, any new connection requests will continue to be directed to this stack. For DVIPA IP addresses activated as the result of a VIPARANGE configuration and a subsequent SIOCSVIPA IOCTL or BIND, a value of nonDisruptive(4) means that this DVIPA can be moved to another stack as soon as the other stack requests ownership of the DVIPA by creating the same DVIPA via a subsequent BIND or SIOCSVIPA IOCTL. Any existing connections on this stack will be maintained by the new owning stack until the connections are closed. All new connection requests will be directed to the new stack. A value of disruptive(5) means that one of two different behaviors will occur: - In the case of a subsequent BIND by an application on another stack, no movement of the DVIPA will occur the second application will presumably be disrupted because the BIND fails. (The first application is unaware that another BIND occurred.) - In the case of a subsequent SIOCSVIPA IOCTL, the DVIPA will move to another stack but connections to the DVIPA on this stack will be broken.