Skip to content
#

fixprotocol

Here are 66 public repositories matching this topic...

jvirtanen
jvirtanen commented Jan 8, 2019

Philadelphia Terminal Client can run scripts nowadays. For testing FIX acceptors, an expect command would be useful. The syntax of the command could be similar to the syntax of the send command. For example:

expect 35=A|98=0|108=30

On the other hand, it should also be possible to skip the expectation for a specific field value, such as the OrderID(37) and ExecID(17) values here:
`

danjmarques
danjmarques commented Jan 30, 2020

Section 7.3.1.1 states that

"The Sequence, Context, EstablishmentAck and Retransmission messages are sequence forming. They turn the message flow into a sequenced mode since they have the next implicit sequence number."

The Establish message is not on that list. Is that omission deliberate? If it is, then the client (with a recoverable flow) would need to send a Sequence after send

salsferrazza
salsferrazza commented Nov 27, 2016

From the specification:

'JSON encoding does not include a “CheckSum” field since it is unlikely to be useful at best, and likely
to be incorrect at worst (e.g. if copied over from another FIX encoding).'

The example output provided from the Java encoder includes the Checksum tag within the trailer:

...
	"Trailer":{
		"CheckSum": "041"
	}
...

Presumably, per the spec, the

Improve this page

Add a description, image, and links to the fixprotocol topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the fixprotocol topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.