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


Errors detected during validation process

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

Errors detected during validation process

During the validation process, HCD checks that the definitions being migrated do not cause any conflicts with existing definitions in the IODF and with other definitions being migrated. HCD also checks that the contents of the input data sets is valid. The errors are shown in the message list and migration log.

Figure 141 shows error messages in the migration log.

Figure 141. Example: HCD Migration Log
I/O Configuration Migration                Time: 11.39    Date: 94-11-26    Page:    1
MVS/ESA HCD V 5.2

(1) DSN=BBEI.IOCP01.CTL     1 
(2) DSN=BBEI.MVSCP01.CTL

Statement  Orig  Sev  Msgid   Message Text

      9    (1)  E  CBDA230I  Duplicate unit address F0 on channel path 01 of processor BOEHCD.

      5    (2)  W  CBDA265I  Type of control unit 0131 assumed as 3880-13 to attach device 01F0.

                I  CBDA516I  No output written to IODF. VALIDATE processing forced due to errors.

Total Messages   Terminating   Error   Warning   Informational
          3           0          1         1             1

Return Code was   8

The messages are sorted according to their severity, and within a certain severity level according to their occurrence.

The value in the  Orig  column points to the input data set that caused this error. At the top of the migration log you find a reference list that shows the values with the names of the input data sets (see the line marked  1 ).

In Figure 141 the first message line means, that the statement number 9 in the input data set 1 (data set BBEI.IOCP01.CTL) is the cause of the error message.

The following examples show common validation errors and explain their causes.

Example 1

Statement Orig Sev  Msgid   Message Text

      7    (1)  E  CBDA154I  Channel path type CNC is not supported by channel
                             path ID 3A.

This message is issued, because an ESCON channel is defined although the support level was defined in the IODF as having only parallel channels installed for the specified CHPID. To resolve this, either change the channel type in the IOCP input data set, or change the processor type or support level in the IODF.

Example 2

Statement Orig Sev  Msgid   Message Text

      4    (1)  E  CBDA234I  Unknown type 38823 of control unit 0000
                             specified.

This message is issued, because HCD does not know the control unit type 38823. Select the Query supported hardware and installed UIMs from the Primary Task Selection panel or use the Query action bar choice for information on valid control unit and device types.

Example 3

Statement Orig Sev  Msgid     Message Text

     228   (1)   W  CBDA265I  Type 3800-3 assumed for control unit DD32
                              to attach the device 0828.
     227   (1)   I  CBDA534I  Control unit DD32 is assumed as 3800-1.

These messages are issued, because HCD has to choose the control unit type among several models.

The control unit model 3800-1 is indicated as default model in the UIM (information message CBDA534I is issued). As processing goes on, it is necessary to change the default model (3800-1) to another model (3800-3) to attach a device type which is not supported by the default control unit model (warning message CBDA265I is issued).

Note:
The sequence of messages is shown in reverse order in the migration log file since the messages are sorted according to decreasing severities. To resolve this, either include the model in the IOCP input data set, map the control unit types via HCD profile entries, or update the IODF using the HCD dialog, if HCD has made an incorrect assumption.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014