IBM Sterling Transformation Extender

Sterling Transformation Extender

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

 View Only

  • 1.  Map did not fail with incomplete FTP

    Posted Thu February 05, 2009 09:36 AM

    Originally posted by: rarw


    Hi,

    We had a map ftp to another server where there was insufficient disk space on the remote server to ftp the entire file. The map did not fail as we had expected (ftp adapter return =0).

    We use a fail map command in the rule, but apparently this is not sufficient to actually fail the map for this situation. What else do we need to do to fail the map?

    Also, is there a file size limit on what the ftp adapter can transfer?

    Listed below is some information pertinent to the problem.
    Thanks for your help - Becky

    Map Rule

    =VALID(RUN("MAR509_PROC.mmc"," -OAFTP1 '-T %LOGGING%MAR509_USER.mtr

    %FTP_LOGIN%%FTP_DIR%%CCH01S%" + ";type=ASCII'"),
    FAIL ("Failure on RUN (" + TEXT (LASTERRORCODE ( ) ) + "):" + LASTERRORMSG ( ) ) )
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Map Audit trace excerpts

    Run Audit Log
    <ExecutionSummary MapStatus="Valid" mapreturn="0" ElapsedSec="10.129" BurstRestartCount="0">
    <Message>Map completed successfully</Message>
    <CommandLine>/opt/IBM/WTx_workdir/PRD/MAPS/MAR509_PROC.mmc -OAFTP1 '-T

    %LOGGING%MAR509_USER.mtr %FTP_LOGIN%%FTP_DIR%%CCH01S%;type=ASCII'</CommandLine>

    ...
    <TargetReport card="1" adapter="FTP" bytes="8493504" adapterreturn="0">
    <Message>OK</Message>
    <Settings>-T /opt/IBM/WTx_workdir/PRD/LOGS/MAR509_USER.mtr *****

    (%FTP_LOGIN%)xxxxx/yyy/zzzzz/5022;type=ASCII</Settings>
    <TimeStamp>00:29:59 February 3, 2009</TimeStamp>
    </TargetReport>

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Excerpt from FTP trace
    ...

    Connecting to '111.222.333.444'.
    Socket Opened.
    Connected.
    <STOR 5022

    >550 xxxxx/yyy/zzzzz/5022: 8,no space for file on device pk (F)
    Socket Closed.
    Connection closed.
    <ABOR

    >226 No Transfer Currently Running. (S)
    Data in /tmp/ftpAAAaxaGyP deleted.
    Run Terminated at 00:30:00.496 on 02/03/09.
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 2.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 03:26 AM

    Originally posted by: cemeinz


    Hello!

    Best would be a complete ftp trace file.

    Map completed successfully, because the last code sent back from the adapter was 226, which is one of the codes for WTX for a successfully action.

    Let's have a look into the description:

    Line: ----

    Fail (-FAIL) is an optional command that allows you to specify particular error codes that cause the adapter to fail and disconnect from the FTP server. The default behavior of the FTP adapter is to pass 100 and 200 level error codes and to fail only on 300, 400, and 500 level error codes as defined in RFC 959. Any other error codes returned are ignored. By using the Fail adapter command, you can specify the error codes, such as from third-party data, for which the adapter fails.

    Line: ----

    Nevertheless, mapping should fail. As said before, please post a complete ftp trace stack. Thanks.
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 3.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 03:30 AM

    Originally posted by: janhess


    Which version of WTX are you using? Are you using the websphere ftp adapter or the deprecated ftp adapter?
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 4.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 03:45 AM

    Originally posted by: janhess


    The error is reported in the line
    550 xxxxx/yyy/zzzzz/5022: 8,no space for file on device pk (F)

    I would guess that you are using the websphere ftp adapter and therefore it's probably a bug. It should give a fail result not 226. It looks as though the 226 is generated as a result of the ABORT being successful.
    226 - Closing data connection. Requested file action successful (for example, file transfer or file abort).

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


  • 5.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 06:18 AM

    Originally posted by: cemeinz


    @janhess: my suggestion in other words. waiting for some answer now. :)
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 6.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 08:28 AM
      |   view attached

    Originally posted by: rarw


    Hi,

    Thank you for your responses cemeinz and janhess.

    We are currently on WTx 8.1.0.2 (build 38).

    The complete FTP trace is attached. Thank you for your help. - Becky
    #IBMSterlingTransformationExtender
    #DataExchange
    #IBM-Websphere-Transformation-Extender

    Attachment(s)

    txt
    attachment_14213937_trace_for_forum020609.txt   1 KB 1 version


  • 7.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 09:56 AM

    Originally posted by: janhess


    It looks like the ABOR is giving the 226. I would raise a PMR as the underlying problem needs to generate an error.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 8.  Re: Map did not fail with incomplete FTP

    Posted Fri February 06, 2009 10:04 AM

    Originally posted by: rarw


    Thank you for your reply janhess, I appreciate your help.

    I will submit a PMR.

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


  • 9.  Re: Map did not fail with incomplete FTP

    Posted Sat February 07, 2009 03:34 PM

    Originally posted by: paul.brett


    The map you are running, 'MAR509_PROC.mmc', needs to have certain settings on the output card. The OnFailure setting needs to be 'Commit'. The RUN() function should then trigger the fail if the FTP does not work.

    It does sound odd, but do try it - it works.

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


  • 10.  Re: Map did not fail with incomplete FTP

    Posted Sun February 08, 2009 05:22 AM

    Originally posted by: janhess


    Yes I'd forgotten about that. It does work. Just shows what happens when you stop working with WTX regularly.
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange