Imported from previous forum
Dear All,
I had come across one problem with the 270 tag value. We are using FIX4.2 protocol in our Muscat Securities Exchange. Now a days, their Banking Index went up 10000. And, we are using this index value from message type U00B1 - Real-Time Data for Index (MSM specific message). The index value is set in tag,270. Upto 10,000 index data where correct. After, index crossed 10000, the value set to 270 is one decimal place shifted to left. For eg., if index value is: 10214.56 then the value set to 270 field is like : 1021.45.
Is this the problem with the Exchange or any other problem related to FIX engine. If anyone can provide more clarrification to this matter, are welcomed.
regards,
Rajesh KR
Hi Rajesh,
Tune the fix engine you should solved the issue.
Joel
Dear All, I had come across one problem with the 270 tag value. We are
using FIX4.2 protocol in our Muscat Securities Exchange. Now a days,
their Banking Index went up 10000. And, we are using this index value
from message type U00B1 - Real-Time Data for Index (MSM specific
message). The index value is set in tag,270. Upto 10,000 index data
where correct. After, index crossed 10000, the value set to 270 is one
decimal place shifted to left. For eg., if index value is: 10214.56 then
the value set to 270 field is like : 1021.45.Is this the problem with the Exchange or any other problem related to
FIX engine. If anyone can provide more clarrification to this matter,
are welcomed.regards, Rajesh KR
Hello Joel,
I checked this problem by simulating acceptor and initiator. By setting 270 field at initiator side with value = 123456.12345 and sending it to acceptor. Acceptor is coded to replay with the same data that i send to it. And I got the correct data. So, I think its not due to any problem with FIX Engine.
Anyway, if you think its problem with FIX Engine tuning, can you tell me what I need to fix it!
regards,
Rajesh KR
Hi Rajesh,
Tune the fix engine you should solved the issue.
Joel
Dear All, I had come across one problem with the 270 tag value. We are
using FIX4.2 protocol in our Muscat Securities Exchange. Now a days,
their Banking Index went up 10000. And, we are using this index value
from message type U00B1 - Real-Time Data for Index (MSM specific
message). The index value is set in tag,270. Upto 10,000 index data
where correct. After, index crossed 10000, the value set to 270 is one
decimal place shifted to left. For eg., if index value is: 10214.56
then the value set to 270 field is like : 1021.45.Is this the problem with the Exchange or any other problem related to
FIX engine. If anyone can provide more clarrification to this matter,
are welcomed.regards, Rajesh KR