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.  AWSSTART Fails with AWSSTA052E

    Posted Mon August 27, 2012 11:27 PM
    I am attempting to start z1090 with ADCD for VM 6.1 for the first time. AWSSTART is failing with message AWSSTA052E Initialization of OSA failed, RC=-4. I have verified ownership of /usr/z1090 and subsequent directories and all are owned by ibmsys1:zpdt. I have also tried with ownership root:root. All sysctl changes recommended in March 2012 Redbook (volume 2) have been verified.

    awsstart devmapvm
    IBM System z Personal Development Tool (zPDT)
    Licensed Materials - Property of IBM
    5799-ADE
    (C) Copyright IBM Corp. 2007 All Rights Reserved.

    z1090, version 1-3.43.20, build date - 03/09/12 for Linux on SuSE 64bit
    AWSSTA014I Map file name specified: devmapvm
    AWSSTA204I zPDT started in directory '/usr/z1090'.
    AWSSTA146I Starting independent 1090 instance 'ibmsys1'
    OSA code level = 0x4301
    AWSSTA125I System shutdown in progress ...
    AWSSTA143I Shutdown complete
    IBM System z Personal Development Tool (zPDT)
    Licensed Materials - Property of IBM
    5799-ADE
    (C) Copyright IBM Corp. 2007 All Rights Reserved.

    z1090, version 1-3.43.20, build date - 03/09/12 for Linux on SuSE 64bit

    AWSSTA052E Initialization of OSA failed, RC=-4
    AWSSTA140E Initialization failure.

    Here is the content of my devmapvm file
    system
    memory 1500m
    3270port 3270
    processors 1
    manager
    name aws3274 1
    device 0700 3279 3274 L700
    device 0701 3279 3274 L701
    device 0702 3279 3274 L702
    manager
    name awsckd 8
    device 0A80 3390 3390 /z/610RES
    device 0A81 3390 3390 /z/610W01
    device 0A82 3390 3390 /z/610W02
    device 0A83 3390 3390 /z/610SPL
    device 0A84 3390 3390 /z/610PAG
    device 0A85 3390 3390 /z/PRODPK
    device 0A86 3390 3390 /z/VTAMPK
    manager
    name awsosa 38 --path=f0 --pathtype=OSD
    device 1D00 osa osa --unitadd=0
    device 1D01 osa osa --unitadd=1
    device 1D02 osa osa --unitadd=2

    I am running on base openSUSE 12.0.

    Thanks in advance for any assistance.
    Summer2012


  • 2.  Re: AWSSTART Fails with AWSSTA052E

    Posted Tue August 28, 2012 07:27 AM
    We do not currently support running zVM with RDz-UT or RD&T.

    RDzJohn
    RDzJohn


  • 3.  Re: AWSSTART Fails with AWSSTA052E

    Posted Thu November 15, 2012 05:07 PM
    Resolved
    Summer2012


  • 4.  Re: AWSSTART Fails with AWSSTA052E

    Posted Mon May 20, 2013 11:33 AM

    Hello, I am receiving exactly the same message OSA Code level = 0x4301.

    How did you solve it?

     

    Thank you in advance.

    SergioDataAdviser


  • 5.  Re: AWSSTART Fails with AWSSTA052E

    Posted Thu April 20, 2017 12:55 AM

    Hello,

     

    What have you done for 

    OSA code level = 0x4301

    AWSSTA125I System shutdown in progress ...
    AWSSTA052E Initialization of OSA failed, RC=-4
    AWSSTA143I Shutdown complete
    AWSSTA140E Initialization failure

     

    Regards,

    Tamil

     

    mktamil


  • 6.  Re: AWSSTART Fails with AWSSTA052E

    Posted Tue May 02, 2017 09:47 AM

    According to the devmap file from Summer, it seems that he changed the OSA addresses from  the original ADCD configuration. it does not match to the IODF config file in the z/OS disks.

    ame awsosa 38 --path=f0 --pathtype=OSD
    device 1D00 osa osa --unitadd=0
    device 1D01 osa osa --unitadd=1
    device 1D02 osa osa --unitadd=2

    Those addresses have to be in the range from 0400 to 406.

     

    AdilsonColombo


Related Content