Creating an OFTP partner DSN Inbound

  1. Select COMMUNICATION > Partner Management.
  2. Edit an OFTP/IP, OFTP/ISDN, OFTP/X25, or OFTP/X31D 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.
    Specify a data set name. This way, the complete set of information can be assigned to a send request.
    Specify a description of the data set name.
    Use Alias Partner
    Select this check box to specify an alias partner name in the Alias Partner field.
    Alias Partner
    Specify an alternative partner name that can be used to send a send job. Thus, jobs can be sent using this logical name. In the partner overview, the alias partner is displayed in gray. It can be used if a partner (Gateway Partner) performs services for other companies.
    Alias Unit
    Specify a unit for the alias partner.
  5. On the OFTP tab, specify this information:
    Specify an Originator SFID, that is a local sender address.
    Specify the destination SFID which serves as the target address at the partner’s side.
    Virtual file name
    Specify the OFTP file name agreed upon.
    Note: "*" means that all names are allowed.
    Specify a description of the selected virtual file name.
    Note: The description is not transmitted.
    Separator for V+T formats

    Specify a delimiter for the reception of V and T formats. The delimiter is added after each OFTP record. The information must be specified in hexadecimal format. If no delimiter is inserted (for example, Opel DELFOR with V80), this field remains blank.

    Note: With U and R formats this delimiter has no effect.
    Receive Systems
    This field shows the receive system that is assigned to routing.
  6. On the Certificates tab, specify this information:
    • Force signing: Select the check box to force the partner to use file signing when sending.
    • Force encryption: Select the check box to force the partner to use file encryption when sending.
    • Signed EERP expected: Select the check box to ensure that the partner expects a signed EERP (End To End Response).
    See Certificate Management for the handling of certificates.
  7. On the Extended Settings tab, specify this information:
    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.
    Individual Receive Directory
    Select the check box and specify a receive directory in the provided field.
    Select the check box and select Individual Archive Directory to specify the archive directory in the provided field.