IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.

 View Only
  • 1.  Error Code 139 - Command Server

    Posted Mon November 07, 2016 09:32 AM

    Originally posted by: jdavee


    Running a map using WTX Command Server v8.403 on an HP-UX system.  Map was built and runs fine under Development Studio on Windows, but under Command Server execution returns error code 139.

    Of course, there is no code 139 listed in the documentation.

    Does anyone know what this code means?  Other references in the forum dealt with Launcher and bad/corrupt MSL files.  That not the case here, but we are looking at a rebuild of the map.

    Thanks!


    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: Error Code 139 - Command Server

    Posted Mon November 07, 2016 10:44 AM

    Originally posted by: Laurent(Satisco)


    If I remember correctly, codes above 128 are 128 + Unix error code.

    In your case, it would mean 11, dubbed as "segmentation fault".

    My first bet in this case would be to rebuild the map and redeploy it.


    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 3.  Re: Error Code 139 - Command Server

    Posted Mon November 07, 2016 11:34 AM

    Originally posted by: jdavee


    Thanks!  I don't remember seeing that anywhere in the documentation.  It seems applicable since the problem looks like a pathing change in the script so some files and locations are not resolving properly when building the map execution line.


    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 4.  Re: Error Code 139 - Command Server



  • 5.  Re: Error Code 139 - Command Server

    Posted Tue November 08, 2016 02:00 PM