Topic
12 replies Latest Post - ‏2012-01-05T12:18:21Z by SystemAdmin
SystemAdmin
SystemAdmin
253 Posts
ACCEPTED ANSWER

Pinned topic Trouble starting up 1090

‏2011-11-10T17:48:33Z |
Hi All

I'm trying a new installation of RDz UT. As soon I issue the awsstart command, I get an error. Please find the startup log and my devmap below:
Startup log:

ibmsys1@rc-mf2:/usr/z1090/bin> awsstart aprof13 --clean     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-2.41.23.01, build date - 09/20/10 

for Linux on SuSE 64bit   AWSSTA014I Map file name specified: aprof13 AWSSTA090I All zPDT log files purged as requested AWSSTA204I zPDT started in directory 
'/usr/z1090/bin'. AWSSTA146I Starting independent 1090 instance 
'ibmsys1' OSA code level = 0x4101   TUNSETIFF failed: Operation not permitted Socket Create error - no root authority? 1 allocate tunnel error Lan driver Init Failure !!! Lan driver Init Failure !!! Chpid Number F0 Has stopped - Max retry exceeded !! Chpid Number A0 Has stopped - Max retry exceeded !! AWSSTA125I System shutdown in progress ... AWSEMI314I CPU 0 zPDTA License Obtained AWSSTA052E Initialization of OSA failed, RC=-4 AWSSTA143I Shutdown complete AWSSTA140E Initialization failure 
{/code
}   Devmap:


#ADCD z/OS 1.11 summer 2010
system
memory 4096m
processors 1
3270port 3270

manager
name aws3274 0002 # define a few 3270 terminals
device 0700 3279 3274 mstcon
device 0701 3279 3274 tso
device 0702 3279 3274 tso
device 0703 3279 3274 tso
device 0704 3279 3274 tso

manager
name awsckd 0001
device 0a80 3390 3990 /z/SBRES1
device 0a81 3390 3990 /z/SBRES2
device 0a82 3390 3990 /z/SBSYS1
device 0a83 3390 3990 /z/SBUSS1
device 0a84 3390 3990 /z/SBBBN1
device 0a85 3390 3990 /z/SBBBN2
device 0a86 3390 3990 /z/SBPRD1
device 0a87 3390 3990 /z/SBPRD2
device 0a88 3390 3990 /z/SBPRD3
device 0a89 3390 3990 /z/SBDIS1
device 0a8a 3390 3990 /z/SBDIS2
device 0a8b 3390 3990 /z/SBDIS3
device 0a8c 3390 3990 /z/SBDIS4
device 0a8d 3390 3990 /z/SBDIS5
device 0a8e 3390 3990 /z/SBDIS6
device 0a8f 3390 3990 /z/SARES1
device 0a90 3390 3990 /z/SBWAS1
device 0a91 3390 3990 /z/SBWAS2
device 0a92 3390 3990 /z/SBWAS3
device 0a93 3390 3990 /z/SBDB91
device 0a94 3390 3990 /z/SBDB92
device 0a95 3390 3990 /z/SBDB93
device 0a96 3390 3990 /z/SBCIC1
device 0a97 3390 3990 /z/SBIMS1
device 0a98 3390 3990 /z/SBIMS2
device 0a99 3390 3990 /z/SBIMS3
device 0ab0 3390 3990 /z/PUBLIC
device 0ab1 3390 3990 /z/USER00
device 0ab2 3390 3990 /z/SYSUT1
manager
name awsosa 0024 --path=A0 --pathtype=OSD --tunnel_intf=y
device 400 osa osa
device 401 osa osa
device 402 osa osa

manager
name awsosa 0022 --path=F0 --pathtype=OSD
device 404 osa osa
device 405 osa osa
device 406 osa osa
{/code}
Can you please help me in identifying the issue?

Thanks,
Juzer
Updated on 2012-01-05T12:18:21Z at 2012-01-05T12:18:21Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    253 Posts
    ACCEPTED ANSWER

    Re: Trouble starting up 1090

    ‏2011-11-21T17:02:54Z  in response to SystemAdmin
    Hello,

    We still have trouble starting 1090. Solution(s) anyone ??

    Regards,

    Aamir.
  • JavaPoet
    JavaPoet
    11 Posts
    ACCEPTED ANSWER

    Re: Trouble starting up 1090

    ‏2011-11-26T15:37:42Z  in response to SystemAdmin
    The error

    AWSSTA052E Initialization of OSA failed, RC=-4

    Would indicate to me that you don't have authority to the program that runs the OSA communications. Try the command:

    $ ls -l /usr/z1090/bin/eDMosa

    And see what group the program is in. The userid that is trying to start the RDz UT should be in the same group. If the group is root then the following procedure is suggested for customers who are concerned about z1090's eDMosa file allowing any userid to execute it.

    After z1090 install (using root id)
    create a unique group ie : groupadd <your_group>
    change group_owner of eDMosa ie: chgrp <your_group> /usr/z1090/bin/eDMosa
    set eDMosa permissions to 4750 ie: chmod 4750 /usr/z1090/bin/eDMosa
    VERY IMPORTANT : It must be understood that : any naitive Linux userid that wants to use z1090 OSA, needs to be added to <your_group>

    Let me know if this helps or not
    • SystemAdmin
      SystemAdmin
      253 Posts
      ACCEPTED ANSWER

      Re: Trouble starting up 1090

      ‏2011-11-28T12:51:01Z  in response to JavaPoet
      Hello,

      I followed the steps that you mentioned and still receive the same. I believe that the TUNSETIFF is caused because of no TUN / TAP adapter creation, this probably has to do with openvpn or something as there is no socket creation.

      ibmsys1@rc-mf2:/usr/z1090/bin> awsstart aprof13 --clean
      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-2.41.23.01, build date - 09/20/10 for Linux on SuSE 64bit

      AWSSTA014I Map file name specified: aprof13
      AWSSTA090I All zPDT log files purged as requested
      AWSSTA204I zPDT started in directory '/usr/z1090/bin'.
      AWSSTA146I Starting independent 1090 instance 'ibmsys1'
      OSA code level = 0x4101

      TUNSETIFF failed: Operation not permitted
      Socket Create error - no root authority? 1
      allocate tunnel error
      Lan driver Init Failure !!!
      Lan driver Init Failure !!!
      Chpid Number F0 Has stopped - Max retry exceeded !!
      Chpid Number A0 Has stopped - Max retry exceeded !!
      AWSSTA125I System shutdown in progress ...
      AWSEMI314I CPU 0 zPDTA License Obtained
      AWSSTA052E Initialization of OSA failed, RC=-4
      AWSSTA143I Shutdown complete
      AWSSTA140E Initialization failure


      Aamir.
  • keithvb
    keithvb
    23 Posts
    ACCEPTED ANSWER

    Re: Trouble starting up 1090

    ‏2011-11-29T21:17:07Z  in response to SystemAdmin
    Hello,

    I did not see the output for command: ls -l /usr/z1090/bin/eDMosa . The install should have set the permission to: -rwsr-xr-x 1 root root . If it did not then you can manually do the following:
    • using root id
    • chown 0:0 /usr/z1090/bin/eDMosa
    • chmod 4755 /usr/z1090/bin/eDMosa

    This sets the permissions so that all users can access the eDMosa code as root id via the setuid bit.

    If you want to see if z1090 comes up without the tunnel connection, you could edit your devmap and comment out lines:
    #manager
    #name awsosa 0024 --path=A0 --pathtype=OSD --tunnel_intf=y
    #device 400 osa osa
    #device 401 osa osa
    #device 402 osa osa

    I look forward to learning how things go for you.
    Regards,
    Keith
    • SystemAdmin
      SystemAdmin
      253 Posts
      ACCEPTED ANSWER

      Re: Trouble starting up 1090

      ‏2011-12-02T13:42:32Z  in response to keithvb
      Hello Keith,

      Thanks a lot the chown and chmod command initialized the subsystems perfectly. I will definitely share the messages/output in my next thread. The other problem that I am facing right now is when I give the command "x3270 -port 3270 mstcon@localhost"
      I get the message: "connect to localhost port 3270: network is unreachable"

      If I change "x3270 -port 3270 mstcon@localhost" to "x3270 -port 3270 mstcon@127.0.0.1" the x3270 terminal comes up with text in it but then I cannot proceed with ipl,so to do so I open another terminal to that location and do ipl but then that does not work as well.

      Will appreciate your help.

      Thank you,

      Aamir.
      • RDzJohn
        RDzJohn
        268 Posts
        ACCEPTED ANSWER

        Re: Trouble starting up 1090

        ‏2011-12-02T14:05:34Z  in response to SystemAdmin
        Aamir,

        Assuming you are still using the dvemap you appended earlier, the 3270 definitions look good there.

        I suggest using a startup script like the following called startpdt.sh:

        echo "Start of RDz-UT setup"
        awsstart aprof1 --clean
        sleep 4
        echo "RDz-UT started"
        x3270 -port 3270 mstcon@localhost &
        sleep 2
        x3270 -port 3270 localhost &
        sleep 2
        echo "Terminals defined"
        echo "End of RDz-UT setup"
        echo "Issue ipl 0a80 parm 0a82xx command"

        Put this script and aprof1 in your /home/ibmsys1 (or whatever your userid is) directory. Login to ibmsys1 and open a terminal window.
        Issue the command ./startpdt.sh which executes the above script.

        RDzJohn
        • SystemAdmin
          SystemAdmin
          253 Posts
          ACCEPTED ANSWER

          Re: Trouble starting up 1090

          ‏2012-01-03T10:57:58Z  in response to RDzJohn
          Hello Jon,

          Below is the output for eDMosa that you had earlier for.

          rc-mf2:/usr/z1090/bin> ls -l /usr/z1090/bin/eDMosa
          -rwsr-xr-x 1 root root 5286294 Sep 21 2010 /usr/z1090/bin/eDMosa

          Jon, I made the script like you asked me to but still the 3270 terminal comes up and does not connect to mstcon@localhost it displays the message "mstcon@localhost: Servname not supported for ai_socktype".

          I checked for opening some ports related to x11 which would be TCP port 6000 and UDP port 177 which did not help either.

          Help!

          Aamir
          • RDzJohn
            RDzJohn
            268 Posts
            ACCEPTED ANSWER

            Re: Trouble starting up 1090

            ‏2012-01-04T13:05:38Z  in response to SystemAdmin
            Aamir,
            Please append the startup log and any other messages from the terminal window you used to start the emulator.

            RDzJohn
            • SystemAdmin
              SystemAdmin
              253 Posts
              ACCEPTED ANSWER

              Re: Trouble starting up 1090

              ‏2012-01-05T12:13:07Z  in response to RDzJohn
              Hello John,

              On running the script this is what gets displayed in the terminal.

              rc-mf2:~> ./startpdt.sh
              Start of RDz-UT setup
              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-2.41.23.01, build date - 09/20/10 for Linux on SuSE 64bit

              AWSSTA014I Map file name specified: aprof33
              AWSSTA015E 1090 already running
              AWSSTA140E Initialization failure
              RDz-UT started
              Terminals defined
              End of RDz-UT setup
              Issue ipl 0a80 parm 0a82dc

              Aamir.
  • keithvb
    keithvb
    23 Posts
    ACCEPTED ANSWER

    Re: Trouble starting up 1090

    ‏2012-01-04T14:45:42Z  in response to SystemAdmin
    Aamir,

    It would also be helpful for us to know the following:
    -what is base Linux you are running and its level.
    -Are you running on the base machine or a virtual machine ?
    -please provide the output of ifconfig command .
    -is it possible for you to try running with your firewall disabled and SELINUX set to permissive (if you run with it set to "enforcing" )

    Thank you,
    Keith
    • SystemAdmin
      SystemAdmin
      253 Posts
      ACCEPTED ANSWER

      Re: Trouble starting up 1090

      ‏2012-01-05T12:18:21Z  in response to keithvb
      Hello Keith,

      Linux is being run on base machine and firewall is completely disabled. Below is the output of ifconfig and host file that you asked for.

      rc-mf2:~> ifconfig
      eth0 Link encap:Ethernet HWaddr 2C:41:38:04:F8:9C
      inet addr:192.168.32.130 Bcast:192.168.39.255 Mask:255.255.248.0
      UP BROADCAST MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
      Interrupt:47 Base address:0x6000

      lo Link encap:Local Loopback
      inet addr:127.0.0.1 Mask:255.0.0.0
      UP LOOPBACK RUNNING MTU:16436 Metric:1
      RX packets:12390 errors:0 dropped:0 overruns:0 frame:0
      TX packets:12390 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:1685147 (1.6 Mb) TX bytes:1685147 (1.6 Mb)

      tap0 Link encap:Ethernet HWaddr 52:90:DE:9F:DD:5D
      inet addr:10.1.1.1 Bcast:10.1.1.255 Mask:255.255.255.0
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:500
      RX bytes:0 (0.0 b) TX bytes:3434 (3.3 Kb)

      wlan0 Link encap:Ethernet HWaddr D0:DF:9A:1D:76:39
      inet addr:192.168.1.133 Bcast:192.168.1.255 Mask:255.255.255.0
      UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:11860 errors:0 dropped:0 overruns:0 frame:0
      TX packets:5408 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:7545054 (7.1 Mb) TX bytes:990874 (967.6 Kb)


      /etc/hosts

      1. special IPv6 addresses
      ::1 localhost ipv6-localhost ipv6-loopback
      127.0.0.2 rc-mf2.rckhi rc-mf2
      192.168.32.130 rc-mf2.rckhi rc-mf2

      Aamir.
  • keithvb
    keithvb
    23 Posts
    ACCEPTED ANSWER

    Re: Trouble starting up 1090

    ‏2012-01-04T20:18:22Z  in response to SystemAdmin
    Aamir,

    Also please provide the contents of your /etc/hosts file.
    Thanks,

    Keith