IBM Sterling Transformation Extender

Sterling Transformation Extender

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


#Sterling
#Supplychain
 View Only
  • 1.  Exit call failed

    Posted 11/09/05 06:22 AM

    Originally posted by: SystemAdmin


    Hi,

    When I run a TX map on a HP-UX server with the commad dstx, I have this kind of ouput:

    In #28: 27877800 Out # 1: 340 Time: 2:50 Exit call failed
    In #28: 27877800 Out # 1: 655 Time: 14:41 Exit call failed
    In #28: 27877800 Out # 1: 914 Time: 26:16 Exit call failed
    In #28: 27877800 Out # 1: 1445 Time: 38:12 Exit call failed
    In #28: 27877800 Out # 1: 1962 Time: 44:35 Exit call failed
    In #28: 27877800 Out # 1: 4266 Time: 55:29 Exit call failed
    ...

    The job runs OK but I don't know why it says: "Exit call failed".

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


  • 2.  Re: Exit call failed

    Posted 11/10/05 06:54 AM

    Originally posted by: SystemAdmin


    Would need to see the map and it's rules. Open a Support SCase.
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: Exit call failed

    Posted 11/10/05 07:17 AM


  • 4.  Re: Exit call failed

    Posted 11/10/05 11:53 AM

    Originally posted by: SystemAdmin


    It is very possible you have a RUN() statement in your rules that needs to be wrapped as =VALID(RUN(), FAIL()). When an EXIT condition fails, the FAIL statement should kick in.

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