# Natural Editors

**URL:** <https://techcommunity.softwareag.com/t/natural-editors/208062>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-on-Mainframes, Natural-on-Windows-Unix\
**Created:** [April 28, 2020, 2:13pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062 "2020-04-28T14:13:07Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrzej\_Wierzbowski](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@Andrzej\_Wierzbowski](https://techcommunity.softwareag.com/u/Andrzej_Wierzbowski)\
**Post date:** [April 28, 2020, 2:13pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/1 "2020-04-28T14:13:07Z")

</div>

Hello,  
Since Natural 9.1 program/data/map editors are disabled and substituted by the NaturalONE editors. Is it possible to unblock old editors and use both editing mechanisms, i.e. mainframe editors and NaturalONE editors in parallel, depending on the preferences of the end user?

Thanks in advance

---

<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:** [April 28, 2020, 4:50pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/2 "2020-04-28T16:50:54Z")

</div>

We have been doing this for years with Natural mainframe and Natural for Windows. I believe it is also possible with Natural ONE, but it is not recommended by Software AG, and likely frowned upon.

Technically, access to the mainframe editors is controlled by your license key. You would have to make a compelling case with SAG as to why you need a new license key with editor access.

One day soon, the editors will be gone rather than hidden, and even a license key won’t help.

---

<div class="post-metadata">

**Author:** ![George\_Cooper](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/george_cooper/32/7831_2.png) [@George\_Cooper](https://techcommunity.softwareag.com/u/George_Cooper)\
**Post date:** [April 28, 2020, 7:53pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/3 "2020-04-28T19:53:52Z")

</div>

One option may be the “Software AG Editor”, SAG’s ISPF clone. I once heard it would still be available, but I guess no guarantees for the long term.

Cheers.

---

<div class="post-metadata">

**Author:** ![Andrzej\_Wierzbowski](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@Andrzej\_Wierzbowski](https://techcommunity.softwareag.com/u/Andrzej_Wierzbowski)\
**Post date:** [April 29, 2020, 12:54pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/4 "2020-04-29T12:54:08Z")

</div>

Thanks Ralph and George for helpful suggestions!

At first I need to ask Software AG for a license key to unlock old editors.

Meanwhile I foound an article by Karlheinz Kronauer „Get ready for Natural 9” at Techcommunity. I’m worried about the following concerned with source transfered from repository to Fuser on mainframe:

„The Natural source code is temporarily saved in the Fuser file and cataloged. After the catalog process is complete, the source code is deleted from Fuser. This avoids possible inconsistencies between the source code in Fuser with the source code in the repository.”

It suggest I can’t use both editors at the same time.

Best regards  
Andrzej

---

<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:** [April 29, 2020, 5:16pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/5 "2020-04-29T17:16:20Z")

</div>

SAG recommends moving all source code from your mainframe-based FUSER to a server-based source code control system, such as GIT, SVN, or CVS. A rather drastic move, but it gets you into the brave new world of DevOps. If you do this, the mainframe editor won’t be able to reach the source code.

If you implement the “traditional” approach, the official source code remains on the mainframe FUSER and is copied temporarily to your NaturalONE workstation for editing. So, the source is available to both old and new editors.

---

<div class="post-metadata">

**Author:** ![Andrzej\_Wierzbowski](https://avatars.discourse-cdn.com/v4/letter/a/aca169/32.png) [@Andrzej\_Wierzbowski](https://techcommunity.softwareag.com/u/Andrzej_Wierzbowski)\
**Post date:** [April 29, 2020, 5:38pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/6 "2020-04-29T17:38:28Z")

</div>

Great thanks Ralph!  
It is I have looked for. Due to some environmental reasons we want to start NAT 9.1 with old and new editors.  
Cheers  
Andrzej

---

<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:44pm UTC](https://techcommunity.softwareag.com/t/natural-editors/208062/7 "2021-04-02T15:44:35Z")

</div>


