Creating an FTP partner DSN inbound for FTP server

  1. Select COMMUNICATION > Partner Management.
  2. Edit an FTP partner.
  3. In the DSN Inbound area, click New.
    A DSN named 'Unnamed DSN' is created.
  4. Specify the information in the General DSN Details dialog. The available fields depend on the selected connection type.
    DSN
    Specify a data set name. This way, the complete set of information can be assigned to a send request.
    Description
    Specify a description of the data set name.
  5. On the FTP tab, specify this information:
    FTP server (Receipt Files from Partner)
    Select this option to determine that the DSN is to act as an FTP server. The files are made available for download.
    Local FTP directory
    Specify the virtual path under which the files are provided on the integrated FTP server.
    Local FTP File Name
    Specify the file template under which the files are accepted.

    Example: *.d01

    Local FTP file name
    Specify a pattern for the remote file name under which it is stored on the FTP server. For this purpose, you can use these parameters.
    • $XTNUMBER: Unique sending number
    • $QENTRYID: Unique internal job number
    • $FREMDID: Reference to the external application placing the job
    • $FW_<column name from XRFILES>: Additional information from a received file.

      Example: If you specify $FW_VFILENAME the virtual filename of the received file is inserted when a received OFTP file is routed to this DSN.

    Minimum Transaction Security
    Specify an option.
    None The file is displayed by its 'local FTP filename'. When fully downloaded, the file is moved to the send archive.
    Temporary Transfer Name The file is transferred under a temporary file name. After a successful transfer, the FTP Client must rename the file to 'Local FTP filename' to indicate that the file has been completely transferred.
  6. On the Extended settings tab, specify this information:
    Conversion
    Specify the conversion to be performed by Exchange Services before transmission.
    These options are available: None, ASCII to EBCDIC, EBCDIC to ASCII.
    Subsequent processing
    Click Add to specify the type of processing.
    Processing type
    • Routing program: one or more routing programs
    • HTTP: one or more HTTP sub processes
    • Forwarding to External: one or more forwarding sub processes
    • EDX: one or more EDX sub processes
    Category name Select the category name from the list or specify a new category name manually. Categories that are inserted manually are added to the drop-down list.
  7. Click OK.