Some message formats insist that the final message in a record set has no trailing delimiter. However, in most cases, you can safely leave this parameter set to Yes.

The configured default setting is Yes.

The value entered is interpreted as a sequence of one or more bytes. If there are multiple bytes in the delimiter, each must be separated by a comma. You can enter the delimiters in the following formats:

• ASCII Characters: The adapter supports all ASCII characters.Example: *,*,* (records separated by ***)Example: | (records separated by a |)

• Escaped ASCII: The adapter supports \r, \n, \t, and \f.Example: \r,\n (records separated by CR NL)Example: \n (records separated by NL only)

• Hex: The adapter supports 0x00 to 0x7EExample: \0x0D,\0x0A (records separated by CR NL)

• Octal: The adapter supports 000 to 0177.Example: \015,\012 (same as \0x0D,\0x0A)

  Note - When using character delimiters with DBCS data, use single byte character, or equivalent hex values that do not coincide with either byte of the double byte characters. When using escaped ASCII, Hex, or Octal, the “\” character is required.

Each payload contains zero or more records. Using this and related parameters, you can pass records individually to another component within the Service Bus. Available options:

• Delimited: The records are separated by the delimiter specified under the Record Delimiter parameter.

• Fixed: The records are all of a given size, specified by the Record Size parameter.

• Single Record: If the payload is to be processed “as-is,” select this option.

• User Defined: This option is not supported.

The configured default is Delimited.