[This message was posted by William Hooper of NA <[email protected]> to the "FAST Protocol" discussion forum at http://fixprotocol.org/discuss/46. You can reply to it on-line at http://fixprotocol.org/discuss/read/78b37d54 - PLEASE DO NOT REPLY BY MAIL.]
This does not make sense... you are saying the fist bit in the presence map is always the template id copy bit... But here is my template: <template name="Heartbeat" id="2"> <typeRef name="Heartbeat"/> <string name="BeginString" id="8"><constant value="FIX.4.4"/></string> <int32 name="BodyLength" id="9"><copy/></int32> // BIT ONE <string name="MsgType" id="35"><constant value="0"/></string> <string name="SenderCompID" id="49"><copy/></string> // BIT TWO <string name="TargetCompID" id="56"><copy/></string> // BIT THREE <uInt64 name="MsgSeqNum" id="34"><increment/></uInt64> // BIT FOUR <string name="SendingTime" id="52"><delta/></string> // BIT FIVE <string name="TestRequestId" presence="optional" id="112"><copy/></string> // BIT SIX <string name="CheckSum" id="10"><copy/></string> // BIT SEVEN </template> And here is a log od my fist message from ebs live: rcv message 2 -------------------------------------------------------------- 0023 , 125 , 7d(fd) , 11111101 , } =pmap 0024 , 002 , 02(82) , 10000010 , HeatBeat message 0025 , 056 , 38(b8) , 10111000 , 8 =BodyLength 0026 , 069 , 45(45) , 01000101 , E 0027 , 066 , 42(42) , 01000010 , B 0028 , 083 , 53(53) , 01010011 , S 0029 , 070 , 46(46) , 01000110 , F 0030 , 105 , 69(69) , 01101001 , i 0031 , 120 , 78(78) , 01111000 , x 0032 , 083 , 53(53) , 01010011 , S 0033 , 101 , 65(65) , 01100101 , e 0034 , 114 , 72(72) , 01110010 , r 0035 , 118 , 76(76) , 01110110 , v 0036 , 101 , 65(65) , 01100101 , e 0037 , 114 , 72(f2) , 11110010 , r =SenderCompID 0038 , 048 , 30(b0) , 10110000 , 0 =TargetCompID 0039 , 001 , 01(81) , 10000001 , =MsgSeqNum 0040 , 000 , 00(80) , 10000000 , =SendingTime 0041 , 050 , 32(32) , 00110010 , 2 0042 , 048 , 30(30) , 00110000 , 0 0043 , 048 , 30(30) , 00110000 , 0 0044 , 057 , 39(39) , 00111001 , 9 0045 , 048 , 30(30) , 00110000 , 0 0046 , 049 , 31(31) , 00110001 , 1 0047 , 049 , 31(31) , 00110001 , 1 0048 , 054 , 36(36) , 00110110 , 6 0049 , 045 , 2d(2d) , 00101101 , - 0050 , 048 , 30(30) , 00110000 , 0 0051 , 055 , 37(37) , 00110111 , 7 0052 , 058 , 3a(3a) , 00111010 , : 0053 , 049 , 31(31) , 00110001 , 1 0054 , 056 , 38(38) , 00111000 , 8 0055 , 058 , 3a(3a) , 00111010 , : 0056 , 052 , 34(34) , 00110100 , 4 0057 , 049 , 31(31) , 00110001 , 1 0058 , 046 , 2e(2e) , 00101110 , . 0059 , 050 , 32(32) , 00110010 , 2 0060 , 056 , 38(38) , 00111000 , 8 0061 , 048 , 30(b0) , 10110000 , 0 =SendingTime 0062 , 049 , 31(31) , 00110001 , 1 0063 , 050 , 32(32) , 00110010 , 2 0064 , 057 , 39(b9) , 10111001 , 9 =CheckSum That was a Heartbeat Message Notice here the first bit of the presence map is not the template id. I know this (a) because the template needs seven bits and is sent in one byte (b) The TestRequestId correctly has a zero maked in the place it sould be if the template id is omitted. The message I get is another heartbeat and looks like this: rcv message 3 -------------------------------------------------------------- 0065 , 001 , 01(81) , 10000001 , =pmap 0066 , 008 , 08(88) , 10001000 , must be Sending Time delta 0067 , 057 , 39(39) , 00111001 , 9 0068 , 058 , 3a(3a) , 00111010 , : 0069 , 052 , 34(34) , 00110100 , 4 0070 , 049 , 31(31) , 00110001 , 1 0071 , 046 , 2e(2e) , 00101110 , . 0072 , 050 , 32(32) , 00110010 , 2 0073 , 056 , 38(38) , 00111000 , 8 0074 , 051 , 33(b3) , 10110011 , 3 must be Sending Time string 0075 , 049 , 31(31) , 00110001 , 1 0076 , 051 , 33(33) , 00110011 , 3 0077 , 052 , 34(b4) , 10110100 , 4 must be Checksum Yet here we are getting only one bit in the template id and two fields changing - again impossible according to my understanding of the spec. [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
