# Mainframe ADABAS/Natural riding into the sunset

**URL:** <https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-on-Windows-UNIX, Adabas-Add-on-Products, Adabas-Administration-and-Monitoring\
**Created:** [March 1, 2019, 8:46am UTC](https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013 "2019-03-01T08:46:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Echanove](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@Michael\_Echanove](https://techcommunity.softwareag.com/u/Michael_Echanove)\
**Post date:** [March 1, 2019, 8:46am UTC](https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013/1 "2019-03-01T08:46:26Z")

</div>

After 4+ decades of production work our IBM mainframe environment is scheduled to be replaced in the summer of 2020. I have been asked to provide input as to what the best options might be to still have our ADABAS data read accessible (somewhere else) after our cut over for data that was not brought forward.

Any input is appreciated.

Michael Echanove  
Washington State University  
Pullman, WA  
(509) 335-0512

---

<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:** [March 1, 2019, 4:47pm UTC](https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013/2 "2019-03-01T16:47:36Z")

</div>

Why not Adabas/Natural on PCs?

---

<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:** [March 1, 2019, 8:42pm UTC](https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013/3 "2019-03-01T20:42:04Z")

</div>

When my client sunsets its mainframe Adabas/Natural system in a few years, a read-only version will be running on a Windows server, accessible via a browser interface. All the major components have been fully tested:

- copy database contents to a Windows server (Adabas LUW)

- copy and adapt the Natural application under Natural for Windows

- access the Natural application via IE, Firefox, or Chrome

For data access you could consider replacing Natural with Adabas SQL Gateway or Adabas Client for Java, neither of which I have tested.

---

<div class="post-metadata">

**Author:** ![Michael\_Echanove](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@Michael\_Echanove](https://techcommunity.softwareag.com/u/Michael_Echanove)\
**Post date:** [March 4, 2019, 6:45am UTC](https://techcommunity.softwareag.com/t/mainframe-adabas-natural-riding-into-the-sunset/203013/4 "2019-03-04T06:45:43Z")

</div>

Thank you both for the reply. Since our objective is simply to keep a static, read-only copy of ADABAS available after the cutover your advice seems to fit the bill. Might you know what a ballpark cost of ADADAS for Windows (or perhaps Linux) might be?

Michael

---

<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/mainframe-adabas-natural-riding-into-the-sunset/203013/5 "2021-04-02T15:42:24Z")

</div>