Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only

  • 1.  Unable to IPL a ZD&T environment

    Posted Tue April 11, 2017 08:29 AM

    A customer is trying to start for the first time a   ZD&T instance , cloned from a mainframe ,   and they are facing the following message error during the IPL command:

    AWSEMI307I warning ! Disabled wait CPU 0 = 00020000 00000000 0000000 003000B1

    I'm still trying to find the message error in the MVS system codes but without success

    I've suggested to the customer to verify if all volumes are available  in the linux directory.

    Does anyone have other suggestions ?

     

     

     

    gius


  • 2.  Re: Unable to IPL a ZD&T environment

    Posted Tue April 11, 2017 08:43 AM

    This is a wait state PSW.  The waitstate code is in the right most 3 bytes, in this case, 0B1.  From pub:  MVS System Codes V2R1 - SA38-0665-00, p. 127:

     

    0B1

    Explanation: System initialization cannot continue because of a problem in the LOADxx member, the I/O definition file (IODF) data set, or a device.

    The right-most four bytes of the program status word (PSW) have the following format:

    xrr00www

    where:
    x Irrelevant information.
    rr A hexadecimal reason code indicating the reason for the failure. www The wait state code.

    The reason code (rr) is one of the following:

    1. 01  The required data set was not found.

    2. 02  The IODF occupies more than one extent.

    3. 03  A required device is not defined.

    4. 04  MSCH instruction failed for a required device.

    5. 05  The IODF is not valid for an IPL.

    6. 06  The configuration ID specified in the LOADxx member does not match any I/O configuration contained in the IODF.

    7. 07  The LOADxx member contains blanks as the configuration ID. If there is only one I/O configuration defined in the IODF, then the system ignores the blanks and uses the I/O configuration. In this case, the IODF contains multiple definitions and the system requires that you specify a valid configuration ID in the LOADxx member.

    8. 08  The IODF suffix is not valid.

    9. 09  The IODF data set name high level qualifier is not valid.

    0A The IODF is not valid for an IPL. It must be a VSAM data set.

    Note: This wait state can also occur because of an invalid IODF statement. In addition to incorrect data entries this wait state can also be caused by incorrect keyword filtering using the HWNAME, LPAR NAME, and VMUSERID keywords.

    System action: The system enters nonrestartable wait state X'0B1'. The system issues the following messages with the following wait state reason codes:

    Code Accompanying Message

    1. 01  IEA513W.

    2. 02  IEA514W.

    3. 03  IEA515W, to display the device number.

    4. 04  IEA516W, to display the device number.

    5. 05  IEA517W.

    0B1

    1. 06  IEA518W.

    2. 07  None.

    3. 08  IEA512W.

    4. 09  None.

    Operator response:

    Notify the system programmer.

     

    So, in  your case, you have a problem with a required device, I'm guessing either the IPL device or the parms device.  IEA515W should tell you which one.

    RDzJohn


Related Content