How to Debug a Migration Problem

Depending on errors in the IOCP input file, HCD may create the following files:

CBDSMIGR MESSAGES A
CBDSMIGR MSGLOG   A
CBDSMIGR LISTING  A

If HCD creates an assembler listing, it may show more error details. Correct the error and run CBDSMIGR again. Now HCD just creates the MESSAGES and MSGLOG files.

Let us assume, you coded an IODEVICE statement for a 3270 device without a required MODEL=X specification:

incorrect IODEVICE statement:
         CNTLUNIT CUNUMBR=0003,PATH=((CSS(0),0C),(CSS(1),0C)),UNIT=OSC
         IODEVICE ADDRESS=(090,016),UNITADD=00,CUNUMBR=(0003),         *
               UNIT=3270

same IODEVICE statement corrected:
         CNTLUNIT CUNUMBR=0003,PATH=((CSS(0),0C),(CSS(1),0C)),UNIT=OSC
         IODEVICE ADDRESS=(090,016),MODEL=X,UNITADD=00,CUNUMBR=(0003), *
               UNIT=3270

In such a case, HCD writes the following message into the related MESSAGES file:

Figure 1. CBDSMIGR MESSAGES A1

HCD                                      Time: 14:06 Date: 09-07-09  Page:    1
z/VM 5.4.0 HCD

(1) FILE=IOCPVM1 IOCP A  1 


Statement Orig Sev  Msgid    Message Text

     54   (1)   E  CBDA297I  Control unit 0003 of type OSC cannot attach device 0090 of type 3270.
                I  CBDA516I  No output written to IODF. VALIDATE processing forced due to errors.


Total Messages  Terminating     Error     Warning  Informational
          2                       1                       1

Return Code was   8  2

The message points to an error in file IOCPVM1 IOCP A 1 and shows the assembler processing return code 2 .