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
Expand all | Collapse all

AWSSTA052E Initialization of OSA failed, RC=-4

  • 1.  AWSSTA052E Initialization of OSA failed, RC=-4

    Posted Mon November 23, 2015 06:27 AM

    Hello,

    I installed RD&T 9.1 on Opensuse 13.2 and everything works fine apart from TCP/IP connectivity that I try to add using the awsosa driver.

     

    When I start the emulator I get these messages:

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

    z1091, version 1-5.47.16, build date - 08/30/14 for Linux on SuSE 64bit


    AWSSTA014I Map file name specified: devmap21
    AWSSTA204I zPDT started in directory '/z/zos-2.1-adcd'.
    AWSSTA146I Starting independent 1090 instance 'marcel'
    AWSEMI314I CPU 0 zPDTA License Obtained
    AWSEMI314I CPU 2 zPDTA License Obtained
    AWSEMI005I Waiting for 1090 license
    AWSEMI314I CPU 1 zPDTA License Obtained
    OSA code level = 0x4301
    AWSSTA125I System shutdown in progress ...
    AWSSTA052E Initialization of OSA failed, RC=-4
    AWSSTA143I Shutdown complete
    AWSSTA140E Initialization failure

     

     

    I added this to my devmap:

     

    [manager]



    name awsosa 0009 --path=F0 --path=OSD --interface=eth0

    device 400 osa osa --unitadd=0

    device 401 osa osa --unitadd=1

    device 402 osa osa --unitadd=2

     

    Output of find_io:

             Interface         Current          MAC                IPv4              IPv6           
     Path    Name              State            Address            Address           Address        
    ------   ----------------  ---------------- -----------------  ----------------  --------------
      F0     eth0              UP, RUNNING      00:1b:21:a8:51:7e  192.168.1.112     2a02:1205:5052:470:64c3:bee9:292b:457c  
      F1     eth1              DOWN             f4:ce:46:b0:7d:62  *                 *               
      F2     eth2              DOWN             f4:ce:46:b0:7d:63  *                 *               
    .
      A0     tap0              UP, NOT-RUNNING  8a:08:c7:50:47:40  192.168.200.2     *               
      A1     tap1              DOWN             02:a1:a1:a1:a1:a1  *                 *               
      A2     tap2              DOWN             02:a2:a2:a2:a2:a2  *                 *               
      A3     tap3              DOWN             02:a3:a3:a3:a3:a3  *                 *               
      A4     tap4              DOWN             02:a4:a4:a4:a4:a4  *                 *               
      A5     tap5              DOWN             02:a5:a5:a5:a5:a5  *                 *               
      A6     tap6              DOWN             02:a6:a6:a6:a6:a6  *                 *               
      A7     tap7              DOWN             02:a7:a7:a7:a7:a7  *                 *

     

    z1090instcheck reveals:

    Checking zPDT prerequisites ....

     For more information about this script, issue : z1090instcheck  -?

     1. SUSE os level at 42.1 which is
            greater the minimum level                               OK
     2. SUSE kernel.shmmax of 18000000000 is greater than min.      *NOTE*
            shmmax should be greater than 1.1 times the sum
            of z memory (as specified in your devmap) for
            ALL your 1090 instances.
     3. SUSE (kernel.shmall * PAGE_SIZE) is 4722366482869644165120
            which is greater/equal to kernel.shmmax which is        OK
     4. SUSE kernel.msgmni of 32000 is greater than min.    OK
     5. SUSE kernel.msgmax is 65536 which is                        OK
     6. SUSE kernel.msgmnb is 65536 which is                        OK
     7. SUSE net.core.rmem_default of 12582912 is greater than min.         OK
     8. SUSE net.core.rmem_max of 12582912 is greater than min.     OK
     9. SUSE kernel.core_uses_pid is 1 which is                     OK
    10. SUSE kernel.core_pattern is /corefiles/core-%e-%p-%t which is                       BAD
    11. SUSE ulimit -c is set to unlimited                          OK
    12. SUSE ulimit -d is set to unlimited                          OK
    13. SUSE rpm libstdc++6-32bit-(x86_64) is installed             OK
    14. SUSE sntl-sud-7.5.2-0.i386 rpm is greater than required     OK
    15. SUSE zpdt-shk-server-1.3.1.2-2.x86_64 rpm is equal to required level        OK
    16. SUSE dmidecode-2.12-7.1.x86_64 rpm is greater than required         OK
    17. SUSE rpm beagle is not installed which is                   OK
    18. SUSE rpm zmd is not installed which is                      OK


    Running uimcheck ...

    The UIM client is configured in local mode.

    Local Serial Number... 4309
    UIMCHECK: No local errors

     

     

    eDMosa should be fine:

     

    marcel@linux-njop:/z/zos-2.1-adcd> ls -l /usr/z1090/bin/eDMosa
    -rwsr-xr-x 1 root root 1182656 Aug 31  2014 /usr/z1090/bin/eDMosa

     

    What else could be wrong in my setup ?

     

    Thanks in advance for any hints.

     

    Regards,

    Marcel

    970V_Marcel_Schmidt


  • 2.  Re: AWSSTA052E Initialization of OSA failed, RC=-4

    Posted Tue December 01, 2015 12:34 PM

    Marcel,

           We see this problem most often when the directory from which you are starting RD&T (in your case /z/zos-2.1-adcd) is not owned or modifiable by the Linux userid that is issuing the awsstart. Make sure your userid has permissions to the folder where you are starting RD&T.  

     

         I also see that when you ran z1090instcheck, one of the values is bad.

    10. SUSE kernel.core_pattern is /corefiles/core-%e-%p-%t which is                       BAD

        This makes me think that you did not issue the /usr/z1090/bin/aws_bashrc command running under the userid that you wish to run RD&T with. We have seen customers on occasion incorrectly run this from userid root. If run from the userid where you intend to start RD&T, that command should set all values correctly. Run this command under the userid that will run RD&T, then perform the z1090instcheck. If the z1090instcheck shows everything as OK, then try awsstart from a folder that is modifiable by that userid. Let us know if you still have problems after that.   

     

                 Bebe

    RDTBebe