z/OS HCD User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


How to invoke the incremental update

z/OS HCD User's Guide
SC34-2669-00

How to invoke the incremental update

  1. Specify your objects with IOCP, MVSCP, or HCPRIO control statements. Note that you can add additional parameters and SWITCH statements to exploit the extended migration as described under Changing I/O configurations by editing data sets).
  2. Select Migrate configuration data on the Primary Task Selection panel and on the resulting screen select the Migrate IOCP/OS data option.
  3. On the following Migrate IOCP / MVSCP / HCPRIO Data dialog (see Figure 132), enter the required data and change the incremental update to Yes.
  4. After the input has been accepted, HCD issues a message informing you that the migration of input data sets is in process.

Example 1: Adding a partition

In this example, you specify a partition in your input data set that does not yet exist in the IODF. The attached control units and devices are already defined in the IODF for another processor.

The following figure illustrates the result after the incremental update:

Figure 133. Partial Migration of an IOCP Input Data Set. A new partition is added. Control units and devices are mapped.
         IODF          IOCP Input Data Set             Resulting IODF

*----------*----------*    *---------*        *----------*----------*----------*
| Part 1   |  Part 2  |    | Part 3  |        | Part 1   |  Part 2  |  Part 3  |
*----*-----*-----*----*    *----*----*        *----*-----*-----*----*----*-----*
     1           1              2                  1           1         2
     1           3              1                  1           3 *-------1
     |           |              |                  |           | |
*----*----* *----*----*    *----*----*        *----*----* *----*-*--*
|   100   | |   200   |    |   200   |        |   100   | |   200   |
| 3880-3  | | 3990-3  |    | 3990-3  |        | 3880-3  | | 3990-3  |
*----*----* *----*----*    *----*----*        *----*----* *----*----*
     |           |              |                  |           |
     |           |              |                  |           |
*----*----* *----*----*    *----*----*        *----*----* *----*----*
| 06C0,32 | | 05C0,32 |    | 05C0,32 |        | 06C0,32 | | 05C0,32 |
|  3380   | |  3390   |    |  3390   |        |  3380   | |  3390   |
*---------* *---------*    *---------*        *---------* *---------*
                         RESOURCE PART=(PART3)
                         CHPID    PATH=21,TYPE=CNC,PART=(PART3)
                         CNTLUNIT CUNUMBR=200,UNIT=3990,PATH=(13,21)
                         IODEVICE ADDRESS=(5C0,32),UNIT=3390
                                  CUNUMBR=200

The partition is added and the control unit and devices are mapped. For a detailed description when control units and devices are mapped, refer to Migrating additional IOCP input data sets.

Example 2: Replacing a channel path and attached control unit

In this example, you specify a channel path with attached control unit and devices in an IOCP input data set. The channel path, the control unit, and one device already exist in the IODF.

The following figure illustrates the result after the incremental update:

Figure 134. Partial migration of an IOCP input data set. The whole logical control unit (control unit 100 and 200 and connected devices) are replaced by control unit 100 and its connected devices.
             IODF            IOCP Input Data Set   Resulting IODF

*----------*----------------*   *-----------*  *---------*-----------*
| Part 1   |    Part 2      |   |   Part 1  |  |  Part 1 |  Part 2   |
*---*------*--*---------*---*   *---*-------*  *---*-----**-------*--*
    0         1         1           0              0      1       1
    1         1         2           1              1      1       2
    |         |         |           |              |      |       |
*---*---* *---*---* *---*---*   *---*---*      *---*---* -*- *----*-*
| 100   | | 200   | | 300   |   | 100   |      | 100   |     | 300  |
|3990-3 | |3990-3 | |3990-3 |   |3990-3 |      |3990-3 |     |3990-3|
**----*-* **----*-* **------*   **------*      **------*     **-----*
 *--* |*---*  *-*    |           |              |             |
    | *+---*  |      |           |              |             |
   **--** **--**    **---*      **---*         **---*        **---*
   |05C0| |06C0|    |07C0|      |05C0|         |05C0|        |07C0|
   |3390| |3390|    |3380|      |3390|         |3390|        |3880|
   *----* *----*    *----*      *----*         *----*        *----*

                         CHPID    PATH=01,TYPE=CNC,PART=PART1
                         CNTLUNIT CUNUMBR=100,UNIT=3990,PATH=01,...
                         IODEVICE ADDRESS=(5C0,32),UNIT=3390,
                                  CUNUMBR=100

The logical control unit in the IOCP input data set replaces the whole logical control unit in the IODF.

Example 3: Replacing a channel path with a new control unit

In this example, you specify channel paths with control unit and device in the input data set. The channel paths are already defined in the IODF, but connect to another control unit.

The following figure illustrates the result after the incremental update:

Figure 135. Partial migration of an IOCP input data set. CHPIDs are defined as in the IOCP input data set
       IODF               IOCP Input Data Set          Resulting IODF

*--------------------*   *--------------------*   *----------------------*
|       PROC 1       |   |       PROC 1       |   |       PROC 1         |
**--*--*--*----------*   *--*----*------------*   *------*--*----*----*--*
 0  0  0  0                 0    0                       0  0    0    0
 1  2  3  4                 1    2                       3  4    1    2
 |  |  |  |                 |    |                       |  |    |    |
**--*--*--**             *--*----*--*             *------*--***--*----*--*
|   100    |             |   200    |             |   100    ||   200    |
| 3990-3   |             | 3880-3   |             | 3990-3   || 3880-3   |
*-*-----*--*             *-*--------*             *-*-----*--**-*--------*
  |     |                  |                        |     |     |
  |     |                  |                        |     |     |
*-*--**-*--*             *-*--*                   *-*--**-*--**-*--*
|05C0||06C0|             |07C0|                   |05C0||06C0||07C0|
|3390||3390|             |3380|                   |3390||3390||3380|
*----**----*             *----*                   *----**----**----*

                   CHPID    PATH=01,TYPE=BL
                   CHPID    PATH=02,TYPE=BL
                   CNTLUNIT CUNUMBR=200,UNIT=3880,PATH=(01,02),..
                   IODEVICE ADDRESS=(7C0,32),UNIT=3380,
                            CUNUMBR=200

The channel paths in the IODF are deleted and newly defined as they are defined in the IOCP input data set.

Example 4: Replacing a control unit that attaches to two processors

In this example, you want to replace existing control units and devices by another type. The control units and devices are attached to two processors.

The incremental update must be done in several steps:

  1. Specify another control unit number in your IOCP input data set than the one in the existing IODF. Specify the CHPID, CNTLUNIT, and IODEVICE control statements.
  2. Migrate your input data set for the first processor.
    Figure 136. Partial migration of an IOCP input data set. Control unit defined for two processors is migrated to the first processor.
             IODF             IOCP Input Data Set         Resulting IODF
    
    *---------* *---------*       *---------*          *---------* *---------*
    | PROC 1  | | PROC 2  |       | PROC 1  |          | PROC 1  | | PROC 2  |
    *----*----* *----*----*       *----*----*          *----*----* *----*----*
         2           2                 2                    2           2
         1--*     *--1                 1                    1           1
            |     |                    |                    |           |
          *-*-----*-*             *----*----*          *----*----* *----*----*
          |   100   |             |  A100   |          |  A100   | |   100   |
          | 3880-3  |             | 3990-3  |          | 3990-3  | | 3880-3  |
          *----*----*             *----*----*          *----*----* *----*----*
               |                       |                    |           |
               |                       |                    |           |
          *----*----*             *----*----*          *----*----* *----*----*
          | 05C0,32 |             | 05C0,32 |          | 05C0,32 | | 05C0,32 |
          |  3380   |             |  3390   |          |  3390   | |  3380   |
          *---------*             *---------*          *---------* *---------*
                               CHPID    PATH=21,TYPE=CNC,...
                               CNTLUNIT CUNUMBR=A100,UNIT=3990,...
                               IODEVICE ADDRESS=(5C0,32),UNIT=3390,
                                        CUNUMBR=A100
  3. Migrate your input data set again for the second processor.
    Figure 137. Partial migration of an IOCP input data set. Control unit defined for two processors is migrated to the second processor.
             IODF             IOCP Input Data Set          Resulting IODF
    
    *---------* *---------*       *---------*          *---------* *---------*
    | PROC 1  | | PROC 2  |       | PROC 2  |          | PROC 1  | | PROC 2  |
    *----*----* *----*----*       *----*----*          *----*----* *----*----*
         2           2                 2                    2           2
         1           1                 1                    1--*     *--1
         |           |                 |                       |     |
    *----*----* *----*----*       *----*----*                *-*-----*-*
    |  A100   | |   100   |       |  A100   |                |  A100   |
    | 3990-3  | | 3880-3  |       | 3990-3  |                | 3990-3  |
    *----*----* *----*----*       *----*----*                *----*----*
         |           |                 |                          |
         |           |                 |                          |
    *----*----* *----*----*       *----*----*                *----*----*
    | 05C0,32 | | 05C0,32 |       | 05C0,32 |                | 05C0,32 |
    |  3390   | |  3380   |       |  3390   |                |  3390   |
    *---------* *---------*       *---------*                *---------*
                               CHPID    PATH=21,TYPE=CNC,...
                               CNTLUNIT CUNUMBR=A100,UNIT=3990,PATH=(21)
                               IODEVICE ADDRESS=(5C0,32),UNIT=3390,
                                        CUNUMBR=A100

Example 5: Updating an operating system

In this example, you update an operating system by adding and changing EDTs, generics, esoterics, and console devices.

Figure 138. Partial migration of an MVSCP input data set
            IODF                                    MVSCP Input Data Set
                                              IODEVICE ADDRESS=(800,8),UNIT=...,MODEL=...

EDT ID=01                                     EDT ID=01
UNITNAME=POOL1,UNIT=((700,8),(900,8))         UNITNAME=POOL1,UNIT=((800,8)),VIO=YES
UNITNAME=POOL2,UNIT=((100,16))                UNITNAME=POOL3,UNIT=((0270,16))
UNITNAME=TAPES,UNIT=((A80,4))                 UNITNAME=9345,VIO=YES

NIPCON DEVNUM=(40,41,42)                      EDT ID=02
                                              UNITNAME=TAPES,UNIT=((180,4))

                                              NIPCON DEVNUM=(40,50,60)


                     Resulting IODF
              IODEVICE ADDRESS=(800,8),UNIT=...,MODEL=...

              EDT ID=01
              UNITNAME=POOL1,UNIT=((700,8),(800,8),(900,8)),VIO=YES
              UNITNAME=POOL2,UNIT=((100,16))
              UNITNAME=POOL3,UNIT=((0270,16))
              UNITNAME=TAPES,UNIT=((A80,4))
              UNITNAME=9345,VIO=YES

              EDT ID=02
              UNITNAME=TAPES,UNIT=((180,4))

              NIPCON DEVNUM=(040,050,060)
 

You can either migrate the changes with a combined input data set or with an MVSCP only input data set. With a combined input data set, you can make CSS and operating system changes at the same time.

If you migrate an MVSCP only input data set, specify a processor and partition, with which device definitions in the input data sets will be associated in the IODF, on the Migrate IOCP / MVSCP /HCPRIO Data panel. HCD uses this information to map devices correctly if the IODF contains duplicate device numbers. For more information about this mapping, refer to Migrating additional MVSCP or HCPRIO input data sets.

The result after the migration is as follows:

  • The definition of EDT input statements replaces the definition in the IODF, new definitions are added. That means in the example above, EDT 01 is replaced and EDT 02 is added.
  • Devices are added. To add devices, you also have to newly define the esoterics to which the devices are to be assigned.
  • Devices in a UNITNAME statement are added to the devices already defined for the esoteric.
  • The list of consoles is replaced.
Note:
If an EDT statement is missing or specified without EDT ID, the EDT ID for esoterics and generics is taken from the ID of the IOCONFIG statement. If the IOCONFIG statement is also not available, the EDT ID will be assumed as '00'.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014