webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  IDL Extractor for NATURAL

    Posted Thu January 09, 2020 02:25 AM

    [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.jpghttps://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files3/030402b060ff17b2c57f60d33a2d6965b36643d5_2_901x750.jpeg 1.5x, https://higherlogicdownload.s3.amazonaws.com/IMWUC/webMethods/Files/030402b060ff17b2c57f60d33a2d6965b36643d5.jpeg 2x" data-dominant-color="F3F4F4">
    error message.jpg1140×948 105 KB


    #webMethods
    #EntireX
    #Mainframe-Integration


  • 2.  RE: IDL Extractor for NATURAL

    Posted Thu January 09, 2020 04:40 AM

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


    #Mainframe-Integration
    #EntireX
    #webMethods


  • 3.  RE: IDL Extractor for NATURAL

    Posted Fri January 10, 2020 01:42 AM

    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


    #webMethods
    #Mainframe-Integration
    #EntireX


Related Content