| FIX Support » Tag not defined error in SecurityListRequest Apr 18, 2024 @ 12:27 AM (Total replies: 5) | |||||
|
We've not received any email containing OECFIX44 data dictionary, nor it is available in documentation. Please provide this dictionary. Thanks |
|||||
| FIX Support » Tag not defined error in SecurityListRequest Apr 16, 2024 @ 05:30 AM (Total replies: 5) | |||||
|
As you suggested, we have disable our dictionary and now getting different error (Tag appear more than once for field number 1644). Request: 8=FIX.4.4|9=101|35=x|34=2|49=*****|52=20240416-10:04:50.852|56=OEC_TEST|58=GGC|320=10430536|559=0|12051=1|12052=0|10=107| Response: 8=FIX.4.4|9=116|35=3|34=3|49=*****|52=20240416-10:04:51.069|56=OEC_TEST|45=2|58=Tag appears more than once|371=1644|372=y|373=13|10=177| our configurations are set as follows: [DEFAULT] DefaultApplVerID=FIX.4.4 ConnectionType=initiator FileLogPath=./Logs/ StartTime=00:00:00 EndTime=00:00:00 UseDataDictionary=N ReconnectInterval=60 LogoutTimeout=5 LogonTimeout=30 ResetOnLogon=Y ResetOnLogout=Y ResetOnDisconnect=Y SendRedundantResendRequests=Y SocketNodelay=N ValidateUserDefinedFields=N ValidateFieldsOutOfOrder=N # Session configs [SESSION] BeginString=FIX.4.4 SenderCompID=***** UseDataDictionary=N TargetCompID=OEC_TEST HeartBtInt=30 SocketConnectPort=9300 SocketConnectHost=api.gainfutures.com FileStorePath=./Sessions/ |
|||||
| FIX Support » Tag not defined error in SecurityListRequest Apr 15, 2024 @ 01:55 AM (Total replies: 5) | |||||
|
Hi, We are facing issues while using the SecurityListRequest. Here is the request we are sending: Request: 8=FIX.4.4|9=101|35=x|34=2|49=*****|52=20240405-07:23:40.463|56=OEC_TEST|58=GGC|320=73102103|559=0|12051=1|12052=0|10=104 And this is what we are getting in response Response: 8=FIX.4.4|9=125|35=3|34=5|49=*****|52=20240405-07:25:05.949|56=OEC_TEST|45=4|58=Tag not defined for this message type|371=126|372=y|373=2|10=113 To counter the issue mentioned in the response in tag 58 & 371, we added ExpireTime(126) tag in the request also and tried again. But it still says tag 126 not defined. Request: 8=FIX.4.4|9=123|35=x|34=2|49=*****|52=20240405-11:23:53.986|56=OEC_TEST|58=GGC|126=20250226-21:00:00|320=80797968|559=0|12051=1|12052=0|10=200 Response: 8=FIX.4.4|9=125|35=3|34=5|49=*****|52=20240405-11:25:22.166|56=OEC_TEST|45=4|58=Tag not defined for this message type|371=126|372=y|373=2|10=098 Edited by ABandali on Apr 15, 2024 01:55 AM |
|||||
| FIX Support » QuickFix Dictionary is incompatible with SecurityList Aug 29, 2023 @ 03:51 AM (Total replies: 2) | |||||
|
Any update on this issue?? I am facing the same. |
|||||
| FIX Support » Logon request not returning FastHashCode Jun 23, 2023 @ 05:18 AM (Total replies: 0) | |||||
|
I am using quickfix (a python library) to implement the GF fix protocol. I am facing some issue while using the logon api after a successful connection. The Logon request is not returning FastHashCode, while the socket connection was successful. Can anyone please guide. Thanks. |
|||||
| FIX Support » UUID for FIX APIs Jun 15, 2023 @ 09:11 AM (Total replies: 0) | |||||
|
We are trying to use FIX APIs, could you pls explain / provide UUID ? Reference https://gainfutures.com/GFAPI/ UUID The UUID identifies the connecting application. GAIN Futures allows one connection per user per UUID. You can obtain a UUID from Customer Service. |
|||||