Imported from previous forum
Specially for message āJā, our business side is trying to test the
limit, to see how many allocations can be handled in one message. The
machine resources always have the limit, however what is the FIX
standard for the maximum length of a message?
Thanks,
Jue Wang
From FIX.4.4 onwards, Allocation messages ^35=J^ supported
Tag 892 : TotNoAllocs (int)
Total number of NoAlloc entries across all messages. Should be the sum of all NoAllocs in each message that has repeating NoAlloc entries related to the same AllocID or AllocReportID. Used to support fragmentation.
Tag 893 : LastFragment (Boolean)
Indicates whether this message is the last in a sequence of messages for those messages that support fragmentation, such as Allocation Instruction, Mass Quote, Security List, Derivative Security List
So application need to worry about maximum number of allocations in one FIX message only FIX.4.3 and less, FIX.4.4 and later version engines would handle that for the application
Specially for message āJā, our business side is trying to test the
limit, to see how many allocations can be handled in one message. The
machine resources always have the limit, however what is the FIX
standard for the maximum length of a message?Thanks,
Jue Wang