Record format cannot be set to Fixed 128

By sunnyzhang on Thu, 11/03/2022 - 05:05

Hi Guys,
I meet following problem in OFTP 1.0 Build 37 to sent out files to partner.
Set Record format(SFIDFMT) to 'F' and Length(SFIDLRECL) to '128' in partner configuration, But logs show:
[Transmission 491] The record format of the transmission has been changed to U (unstructured binary file), this is outbound the only supported format that supports signature, compression and encryption.
Attachment for reference.
Confirmed from partner, they received the file 'Unformatted',SFIDFMT=U, SFIDLRECL=00000.

Is there any guy give me some advice?

Forum
OFTP2

Comments

Profile picture for user service

Submitted by service on Fri, 11/04/2022 - 09:28

"The record format of the transmission has been changed to U (unstructured binary file), this is outbound the only supported format that supports signature, compression and encryption."

--> If you setup signature, compression and encryption you cannot chose the format F, this is only supported in format U by the OFTP2 protocol. Please refer to https://www.rfc-editor.org/rfc/rfc2204.html

Regards

Submitted by sunnyzhang on Fri, 03/10/2023 - 13:55

After removing signature, compression and encryption, it works fine for a while. Recently, below error happened (also attachment)
[Mar 10, 2023 5:04:45 PM] [Session 20230310170443-111] Waiting for receipt acknowledgement (EERP/NERP)
[Mar 10, 2023 5:04:46 PM] [Session 20230310170443-111] The outbound transmission has been interrupted.
Would anyone help me?

File attachments
outbound error.png

Submitted by sunnyzhang on Mon, 03/13/2023 - 03:56

Hi,
After setting format to 'U', EERP could be received sucessfully.
But our partner insist that they need Fixed 128 and they are not having problems with lot of other suppliers.
I have no idea.

File attachments
config.png
log.png