# Natural crashes hard while DISPLAY #TAB(\*) with \>6000 Lines

**URL:** <https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Linux\
**Created:** [January 10, 2019, 1:10pm UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398 "2019-01-10T13:10:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\
**Post date:** [January 10, 2019, 1:10pm UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398/1 "2019-01-10T13:10:36Z")

</div>

Hello all!

the following 6 lines of code causes my Natural on Solaris to crash. It’s a normal natural-session on a 80x24 screen.

```auto
>> -----------Columns 001 072 << Program Zeilen 6 Name MYUSER
Kommando ==> run Modus Struct Bib SYSTEM
************************************ top of data *****************************
000010 define data local
000020 1 #tab (A4/1:6094) init all <'X'>
000030 end-define
000040 ON ERROR DISPLAY *ERROR-NR END-ERROR
000050 display notitle nohdr #tab(*)
000060 end
********************************** bottom of data ****************************
        Natural Run-Time Error: 36

        Invalid move area
$
```

OK, I got a rather old Natural-Version (V 6.3.14 PL 0). Plus there is a simple Workaround using a for-loop. But my question is (just for interest): Is it reproduceable on a newer Version of Natural?

Thanks

Matthias

---

<div class="post-metadata">

**Author:** ![Ralph\_Zbrog](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/ralph_zbrog/32/78_2.png) [@Ralph\_Zbrog](https://techcommunity.softwareag.com/u/Ralph_Zbrog)\
**Post date:** [January 10, 2019, 2:34pm UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398/2 "2019-01-10T14:34:32Z")

</div>

With Natural 8.3.3, 8.4.1, and 9.1.1 (all under Win10), there is no run-time error, but the report cuts of in the middle (vertically) of occurrence1820.

---

<div class="post-metadata">

**Author:** ![Matthias1](https://avatars.discourse-cdn.com/v4/letter/m/9fc348/32.png) [@Matthias1](https://techcommunity.softwareag.com/u/Matthias1)\
**Post date:** [January 11, 2019, 9:35am UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398/3 "2019-01-11T09:35:20Z")

</div>

Thanks Ralph,

seems to be an Solaris/Linux-issue.  
I got an old Nat 6.3.9 PL 0 @ WinServer 2003. No Crash there…

---

<div class="post-metadata">

**Author:** ![Steve\_Robinson](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/steve_robinson/32/107_2.png) [@Steve\_Robinson](https://techcommunity.softwareag.com/u/Steve_Robinson)\
**Post date:** [January 11, 2019, 12:05pm UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398/4 "2019-01-11T12:05:06Z")

</div>

Matthias;

> [@](#):
>
> I got an old Nat 6.3.9 PL 0 @ WinServer 2003. No Crash there…

Does that mean it works? or, it produces an error message?

Would be interesting to know if a table (of each line) was overflowing or if the number of lines is the problem.

I played a bit converting 6094 and 1820 and (4\*1820) to hex/binary to see if there were any numbers close to a typical table size (e.g. 8k) . No luck.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:42pm UTC](https://techcommunity.softwareag.com/t/natural-crashes-hard-while-display-tab-with-6000-lines/202398/5 "2021-04-02T15:42:06Z")

</div>