Use the attributes in the following table to control the transformation.
The Virtual attributes control the format of the payload as it is sent/received over the protocol (PeSIT/OFTP). It’s not a physical file, that why we call it virtual file. The Local attributes control the format of the file as stored/to be stored on trading engine disk.
Note: Replace the "x" with either Virtual or Local. For example, VirtualFileFormat or LocalFile Format.
Attribute | Value | Comment |
---|---|---|
LocalFileCharSet |
« ASCII »/ « EBCDIC »/ Free |
This is the name of the character set used in the local file |
LocalFilePaddingChar | 0x00…0x7F | The padding character used in the local file |
LocalFileRecordFormat |
FIXED_BINARY/ VARIABLE_BINARY/ FIXED_TEXT/ VARIABLE_TEXT/ OCTET_STREAM |
OCTET_STREAM will turn off transcoding |
LocalFileRecordLength | bytes | Size/ max size of a local file record |
VirtualFileCharSet |
« ASCII »/ « EBCDIC »/ Free |
This is the name of the character set for the file flowing over the network |
VirtualFilePaddingChar | 0x00…0x7F | The padding character used in the file over the network |
VirtualFileRecordFormat |
FIXED_BINARY/ VARIABLE_BINARY/ FIXED_TEXT/ VARIABLE_TEXT/ OCTET_STREAM |
OCTET_STREAM will turn off transcoding |
VirtualFileRecordLength | bytes | Size/ max size of a file record over the network |
message.attributes.template .in/out | –– | Indicates the Message Attribute Template applied on reception/ on sending |