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


IOCP input data sets using extended migration

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

IOCP input data sets using extended migration

As described in Updating parts of a configuration by migrating input data sets, HCD introduces an extended migration to allow you to define your complete configuration without using the ISPF front end dialog.

For example, the extended migration allows you to define a switch with its ports or define serial numbers and descriptions for devices and control units by editing your input data sets and migrating them into HCD.

Analogously, when building an IOCP input data set from an IODF, information is generated that describes the additional parameters of the configuration objects (if the prerequisites under Prerequisites to exploit the extended migration are met). Within the generated IOCP input data set, the additional parameters and control statements are shown as comments with special HCD tags so that they can be processed by the IOCP program. When re-migrating such an IOCP input data set to HCD, the tagged comments are identified by HCD and migrated correspondingly.

If you want to use the input data set for both, IOCP processing and HCD migration, the new records must apply to the following rules, so that they can be processed by both programs:

  • The new parameters start with the string *$HCDC$ in column 1.
  • The new SWITCH statement starts with the string *$HCD$ in column 1.
  • The IOCP statement does not have any comment.
  • The additional HCD tagged records follow immediately the last record of the corresponding IOCP statement.
  • The first keyword starts at column 16.
  • The last operand is not followed by a comma.
  • There is no comment to the right of the operand.

Prerequisites to exploit the extended migration

To generate the additional keywords during IOCP data set build, note the following prerequisites:

  • Specify the following entry in the HCD profile: 
    MIGRATE_EXTENDED = YES
    When you specify MIGRATE_EXTENDED = NO (which is default), the additional keywords are not generated during IOCP build. In addition, when remigrating the IOCP input data sets, the migration function ignores the commented '*$HCDC$' and '*$HCD$' tags.

    The HCD profile is explained in Defining an HCD profile.

  • When building IOCP input data sets, you have to set the option Input to Stand-alone IOCP to No on the Build IOCP Input Data Set panel. See Build an IOCP input data set for a description of the new option.

Example of an IOCP input data set

Figure 96 shows you an example of a generated IOCP input data set with the new parameters. Note that each new parameter starts with an *$HCDC$ in column 1. The new switch control statement starts with *$HCD$ in column 1.

Figure 96. Example of an input data set for migration enhancements 
         ID    MSG1='IOCDSNAM',MSG2='BOKA.IODF03 - 95-07-21 16:00',     *
               TOK=('TWO',0000000190009672160057040095202F00000000,0000*
               0000,'95-07-21','16:00:57','BOKA','IODF03')
*$HCDC$        DESC='Cluster(099) test floor'
*$HCDC$        SERIAL='1044009672'
*$HCDC$        SNAADDR=(USIBMSC,TWO)
         RESOURCE PARTITION=((CF001,3),(MVSSMAL,2),(PRIME,1))
*$HCDC$        DESCL=('Coupling facility','MVS 5.2.0 System1','Producti*
               on CF image')
         CHPID PATH=(10),PARTITION=((CF001),(CF001)),TYPE=CFR
*$HCDC$        DESC='Receiver'
         CHPID PATH=(13),PARTITION=((PRIME),(PRIME)),TYPE=CFS
*$HCDC$        TPATH=(TWO,10,FFFE,FFFE)
*$HCDC$        DESC='Sender'
         CHPID PATH=(20),PARTITION=((MVSSMAL),(MVSSMAL)),SWITCH=AB,    *
               TYPE=CNC
*$HCDC$        SWPORT=((AA,C0))
*$HCDC$        DESC='Channel for DASD'
         CHPID PATH=(21),PARTITION=((MVSSMAL),(MVSSMAL)),TYPE=CNC
*$HCDC$        DESC='Channel for DASD'
         CHPID PATH=(25),PARTITION=((PRIME),(PRIME)),TYPE=CNC
*$HCDC$        SWPORT=((AB,80))
*$HCDC$        DESC='Switch connection'
         CHPID PATH=(26),PARTITION=((MVSSMAL),(MVSSMAL)),TYPE=CNC
*$HCDC$        SWPORT=((AA,C5))
*$HCDC$        DESC='Switch connection'
         CNTLUNIT CUNUMBR=0005,PATH=(25),UNITADD=((00,001)),UNIT=9032-3
*$HCDC$        SWPORT=((AB,FE))
*$HCDC$        SERIAL='1021-CU511'
*$HCDC$        DESC='SWITCH AB'
         CNTLUNIT CUNUMBR=0006,PATH=(26),UNITADD=((00,001)),UNIT=9033
*$HCDC$        SWPORT=((AA,FE))
*$HCDC$        SERIAL='1021-CU510'
*$HCDC$        DESC='SWITCH AA'
         CNTLUNIT CUNUMBR=000F,PATH=(20,21),UNITADD=((08,008)),        *
               LINK=(A1,A2),CUADD=3,UNIT=3995-151
*$HCDC$        SWPORT=((AA,C3),(AB,82))
*$HCDC$        SERIAL='5512003330'
*$HCDC$        DESC='DASD on Q4-B3'
         CNTLUNIT CUNUMBR=FFFE,PATH=(13),UNIT=CFS
         IODEVICE ADDRESS=(080,004),MODEL=151,UNITADD=08,              *
               CUNUMBR=(000F),STADET=Y,UNIT=3995
         IODEVICE ADDRESS=110,MODEL=3,UNITADD=00,CUNUMBR=(0005),       *
               STADET=Y,UNIT=9032
*$HCDC$        SERIAL='1021-CU511'
*$HCDC$        DESC='SWITCH AB'
         IODEVICE ADDRESS=120,UNITADD=00,CUNUMBR=(0006),STADET=Y,      *
               UNIT=9033
*$HCDC$        SERIAL='1021-CU510'
*$HCDC$        DESC='SWITCH AA'
         IODEVICE ADDRESS=(FFFE,002),CUNUMBR=(FFFE),UNIT=CFS
*$HCD$   SWITCH   SWID=AA,SERIAL='1021-CU510',DESC='SWITCH AA',        *
               PORT=((C0,CE),(FE,FE)),SWPORT=((CA,AB,C6)),UNIT=9033
*$HCD$   SWITCH   SWID=AB,SERIAL='1021-CU511',DESC='SWITCH AB',        *
               PORT=((80,F0),(FE,FE)),SWPORT=((C6,AA,CA)),MODEL=3,     *
               UNIT=9032

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014