SYSTEM_IMODE_TOO_LARGE runtime error

[Former Member]

Hi,

Our consultants are getting this short dump during IDOC processing. According to note 548845, their session is trying to use more than 2GB of memory. We are on 4.6C and the only way to get around this seems to be to change the profile parameters ztta/roll_extension and abap/heap_area_nondia to allow sessions to use 4GB of memory. Does anyone have any experience with this kind of situation? Is it safe to do this? and also, do we need to change any more profile parametsrs.

Thanks

Cyrus

[Former Member]

Hi Cyrus,

Enter the following parameter in the STARTUP profile of the Central Instance and every Dialog Instance

“abap/max_imode = four_gb”

This will allow the system to address up to 4GB of memory. When you analyze the IMODE short dumps in your system, you will see that they typically occur during an APPEND statement.

The above profile parameter fixed this IMODE error on our system (4.6c on 64-bit platform)

Frank

[Former Member]

are you on 64 bit? whats the total memory you have? I dont think you can go to > 2gb in 4.6c systems .. Did you try to optimize the code to use memory efficiently?

Thanks,

Prince