# IDL Extractor for NATURAL

**URL:** <https://techcommunity.softwareag.com/t/idl-extractor-for-natural/206843>\
**Category:** Forum\
**Tags:** Mainframe-Integration, EntireX\
**Created:** [January 9, 2020, 7:24am UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-natural/206843 "2020-01-09T07:24:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Farmer](https://avatars.discourse-cdn.com/v4/letter/m/f04885/32.png) [@Mike\_Farmer](https://techcommunity.softwareag.com/u/Mike_Farmer)\
**Post date:** [January 9, 2020, 7:24am UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-natural/206843/1 "2020-01-09T07:24:46Z")

</div>

[img]I have setup a NATURAL RPC Server running on mainframe (VSE) with Broker also on mainframe.  
When I try to connect and extract IDL I get a garbage screen. No error, no library listings.  
I can ping Broker from my PC. I have added 4 libs to Steplib for SYSTEM: SYSIDL, SYSRPC, SYSEXT, SYSLIBS.  
What am I missing? Thanks  
Popup box says IDL Extractor for NATURAL as title. Body has a RED X and text "For input string “xxxx”. where xxxx are some weird characters.

 ![error message.jpg](https://global.discourse-cdn.com/techcommunity/original/2X/0/030402b060ff17b2c57f60d33a2d6965b36643d5.jpeg)

---

<div class="post-metadata">

**Author:** ![Rolf\_Bahlke](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/rolf_bahlke/32/109_2.png) [@Rolf\_Bahlke](https://techcommunity.softwareag.com/u/Rolf_Bahlke)\
**Post date:** [January 9, 2020, 9:40am UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-natural/206843/2 "2020-01-09T09:40:05Z")

</div>

Hi MIke,  
maybe you forgot to enable conversion for this service in the attribute file.

---

<div class="post-metadata">

**Author:** ![Bernhard\_Fricke1](https://avatars.discourse-cdn.com/v4/letter/b/a9a28c/32.png) [@Bernhard\_Fricke1](https://techcommunity.softwareag.com/u/Bernhard_Fricke1)\
**Post date:** [January 10, 2020, 6:41am UTC](https://techcommunity.softwareag.com/t/idl-extractor-for-natural/206843/3 "2020-01-10T06:41:33Z")

</div>

Hi,  
If you have a supported Natural version, you do not need to configure STEPLIBs. To configure steplibs for IDL extraction is a really old thing. It was kicked out in EntireX 15-20 years ago. Maybe your setup causes the problem. Try a simple Natural RPC Server. As Rolf mentioned, keep an eye on conversion.  
Regards Bernhard

---

<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/idl-extractor-for-natural/206843/4 "2021-04-02T15:44:04Z")

</div>


