Topic
  • 4 replies
  • Latest Post - ‏2014-02-24T12:32:18Z by Acc_Rdz
Acc_Rdz
Acc_Rdz
6 Posts

Pinned topic AWSEMI001T Insufficient Memory for 1090 to start AWSSTA050E Initialization of CPU failed, RC=-4

‏2014-02-19T09:52:22Z |

Hi,

We have configured RD&T on two Linux servers. We have put 12G memory on startup profile.

Please find the prof1 first 4 lines below.

[system]
memory 12G
3270port 3270                 # port number for non-SNA (coax) 3270
processors 3

One systems starts properly but the other system fails with the below message.

Load parm: BK,  Devmap: /rdt/rdtv9/prof1,  Port: 3270
stopping previous instance
AWSSTP002E 1090 is not running
x3270: no process killed
awsstart /rdt/rdtv9/prof1 --clean

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-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

AWSSTA014I Map file name specified: /rdt/rdtv9/prof1
AWSSTA090I All zPDT log files purged as requested
AWSSTA204I zPDT started in directory '/home/ibmsys1'.
AWSSTA146I Starting independent 1090 instance 'ibmsys1'
AWSEMI001T Insufficient Memory for 1090 to start.
AWSSTA050E Initialization of CPU failed, RC=-4
AWSSTA125I System shutdown in progress ...
AWSSTA143I Shutdown complete
AWSSTA140E Initialization failure

No completed startup message was found.
***************************************
*** runzpdt terminated with errors. ***
***************************************

Please find free -m output below

                            total       used        free     shared    buffers     cached
Mem:              15951      11559       4392          0         13        427
-/+ buffers/cache:          11118       4833
Swap:                2015          0       2015

 

We tried changing 12G to 10G and 8G, faced the same issue, Insufficient memory.

If we change the prof1 memory from 12G to 6G, we are able to start the base system without DB2, IMS and CICS,etc.

When we start all the sub systems with 6G memory, our system starts and goes down in between. It shows the below message

AWSSTA081E Process ID 28532, component CPU, has terminated
AWSSTA086E ... system wide log out in progress
AWSSTA125I System shutdown in progress ...
eDMosaF0 terminating
eDMosaA0 terminating
AWSSTA141E System failure

We would like to use 12G in prof1 to start our RD&T.

Please let us know if more information required from our end. Please let us know what could be the problem and what's blocking on Linux side.

 

Regards,

Sathya
 

 

 

 

Updated on 2014-02-19T10:05:34Z at 2014-02-19T10:05:34Z by Acc_Rdz
  • RDzJohn
    RDzJohn
    4 Posts

    Re: AWSEMI001T Insufficient Memory for 1090 to start AWSSTA050E Initialization of CPU failed, RC=-4

    ‏2014-02-20T14:41:31Z  

    I am a little confused by your append.  It sounds like you start one instance of RD&T on the machine and it comes up cleanly.  You then start a second instance of RD&T using the same devmap and it fails with insufficient memory?  Is the start of the second instance on the same physical hardware?  Are you using the same awsstart command from the same user?  When the emulator starts, it reserves all of the available memory specified in the devmap for its use.  It you are starting the second instance on the same hardware while the first instance is already running, your results are what I would expect.

     

    RDzJohn

  • Acc_Rdz
    Acc_Rdz
    6 Posts

    Re: AWSEMI001T Insufficient Memory for 1090 to start AWSSTA050E Initialization of CPU failed, RC=-4

    ‏2014-02-21T05:31:12Z  
    • RDzJohn
    • ‏2014-02-20T14:41:31Z

    I am a little confused by your append.  It sounds like you start one instance of RD&T on the machine and it comes up cleanly.  You then start a second instance of RD&T using the same devmap and it fails with insufficient memory?  Is the start of the second instance on the same physical hardware?  Are you using the same awsstart command from the same user?  When the emulator starts, it reserves all of the available memory specified in the devmap for its use.  It you are starting the second instance on the same hardware while the first instance is already running, your results are what I would expect.

     

    RDzJohn

    Hi RDzJohn,

     

    We are starting two Instance of RD&T on two Linux Box. Not Two instance of RD&T on Same Linux box.

    We have Two Linux servers having 16GB. In one Linux server RD&T comes up without any problem. We are facing the the above mentioned error on the other Linux server. We believe something task or process is using the memory on the 2nd Linux, which is not releasing/not available to zPDT/RD&T while its starting..

    We have asked our Linux Team to check as well and compare two Linux process/activity.

     

    Regards,

    Sathya

     

     

  • RDzJohn
    RDzJohn
    4 Posts

    Re: AWSEMI001T Insufficient Memory for 1090 to start AWSSTA050E Initialization of CPU failed, RC=-4

    ‏2014-02-21T13:31:12Z  
    • Acc_Rdz
    • ‏2014-02-21T05:31:12Z

    Hi RDzJohn,

     

    We are starting two Instance of RD&T on two Linux Box. Not Two instance of RD&T on Same Linux box.

    We have Two Linux servers having 16GB. In one Linux server RD&T comes up without any problem. We are facing the the above mentioned error on the other Linux server. We believe something task or process is using the memory on the 2nd Linux, which is not releasing/not available to zPDT/RD&T while its starting..

    We have asked our Linux Team to check as well and compare two Linux process/activity.

     

    Regards,

    Sathya

     

     

    Ok.  That seems like a reasonable approach.  You can see from the free -m command that you issued that there is indeed some process that is sucking up the memory before you attempt to start the emulator.  Just be aware that when the emulator starts, it reserves the entire memory footprint that you've coded in the devmap.  All of this storage is then made available to the hosted operating system.  Please let us know what you find.

    RDzJohn

  • Acc_Rdz
    Acc_Rdz
    6 Posts

    Re: AWSEMI001T Insufficient Memory for 1090 to start AWSSTA050E Initialization of CPU failed, RC=-4

    ‏2014-02-24T12:32:18Z  
    • RDzJohn
    • ‏2014-02-21T13:31:12Z

    Ok.  That seems like a reasonable approach.  You can see from the free -m command that you issued that there is indeed some process that is sucking up the memory before you attempt to start the emulator.  Just be aware that when the emulator starts, it reserves the entire memory footprint that you've coded in the devmap.  All of this storage is then made available to the hosted operating system.  Please let us know what you find.

    RDzJohn

    Thanks RDzJohn

    Our Linux Team had found that One of the Module of VMware tool is the culprit for the High Memory Utilization. They had removed that module and we are able to start the RD&T without any issues now..

    -----Sathya