Preparing additional input data sets for migration

This section describes what to consider when migrating more than one MVSCP, IOCP, or HCPRIO input data set into one IODF.

When you migrate additional input data sets into an IODF that already contains definitions, these input data sets may contain control units and devices that are already defined in the existing IODF. HCD assumes that added control units that already exist in the IODF, refer to the same physical control unit, and that the control unit is shared between processors. The following sections describe the rules when a control unit or device is mapped to an existing one and when it is newly defined.

Migrating additional IOCP input data sets

When migrating additional IOCP input data sets, the mapping of control units and devices depends on whether the attached control units are already defined in the IODF or not.

The same control unit number is already defined in the IODF

The control unit is mapped, if both:

• the control unit type is the same, and
• the number and type of attached devices are the same.

If one of these conditions is not fulfilled, the control unit definition is rejected. Figure 123 to Figure 125 show examples of how control units are mapped. These examples do not show more than two control units attached to devices, but the same rules also apply if more control units are attached.

Figure 123. IOCP Migration. Control units and devices are mapped, because they already exist in the IODF.

Figure 124. IOCP Migration. Control units and devices are mapped, although the devices also attached to another control unit in the IODF.

The following example shows the same control units in the IODF and IOCP input data set, but the attached devices are shared in the IOCP input data set. In this case, the devices are merged and will be shared after the migration (only if the control units do not connect to the same processor configuration).

Figure 125. IOCP Migration. Control units and devices are mapped (only if the control units do not connect to the same processor configuration).

The same control unit number is not yet defined in the IODF

In this case:

• a new control unit is defined.
• a new device is defined, unless
  • the device in the input data set is attached to a control unit, to which it is already attached in the IODF. In this case, the new device is mapped to the existing one and attached to both control units (see Figure 126.)
  • or -
  • a device with same device number and type already exists in the IODF and is not attached to any control unit. In this case, the new device is mapped to the existing one and attached to the new control unit (see Figure 127).

  If none of these conditions is fulfilled, a new device is defined (see Figure 128).

Figure 126. IOCP Migration. Devices are mapped, because one attached control unit is already defined in the IODF.

Figure 127. IOCP Migration. Devices are mapped, because the attached control unit is not yet defined in the IODF.

Figure 128. IOCP Migration. Devices are not mapped, because the control unit number does not exist in the IODF.

Migrating additional MVSCP or HCPRIO input data sets

A device can only be mapped if the device number and device type are the same. If the device number or type is not the same, a new device is defined.

If the device number and type are the same, HCD maps the device according to the following rules:

1. If you specify an associated processor and partition on the Migrate IOCP / MVSCP / HCPRIO Data dialog or with the batch migration utility, HCD maps the new device to a device with the same device number and type connected to this processor and partition (provided that such a device exists).
2. If you do not specify an associated processor and partition or the new device does not attach to the specified processor and partition, HCD checks if the device is attached to a control unit. The device in the input data set is mapped, if:
   • the device in the IODF is attached to the same control unit
   • or -
   • the device in the IODF is not attached to any control unit.

   This is illustrated in Figure 129.

   Figure 129. MVSCP Migration. Devices are mapped, because the devices are not attached to a control unit in the IODF.

   
3. If the new device is not attached to a control unit, the device is mapped to the first device found with the same device number and type.

   If the IODF contains several devices with the same device number and type, the device of the MVSCP input data set can be erroneously mapped to a wrong device. To avoid this, you can specify the associated processor and partition on the Migrate IOCP / MVSCP / HCPRIO Data dialog.

   Figure 130. MVSCP Migration. Devices are mapped to the first devices found with the same type and number.

   

If only a subset of devices in the input data set is already defined in the IODF, this subset is mapped to the existing devices and the remaining new definitions are added.

Figure 131. MVSCP Migration. 32 devices are mapped, the other 32 devices are newly defined.