Thread: AW: [Quickfix-developers] Allocation
Brought to you by:
orenmnero
From: Bill R. Hr. <bil...@ra...> - 2004-08-05 11:14:58
|
Hi Ilyas Tag 12 appears in a group (78 NoAllocs). Is it possible that tag 439 = doesn't appear in the description of the group? If this is the case (I have no 4.2 description on my desk), the group = is closed and tag 12 is found in the wrong context (outside of the group). = The second message doesn't contain tag 439 and tag 12 is seen in the = context of 78 NoAllocs. Regards Robert -----Urspr=FCngliche Nachricht----- Von: ili...@bn... [mailto:ili...@bn...]=20 Gesendet: Donnerstag, 5. August 2004 11:47 An: qui...@li... Betreff: [Quickfix-developers] Allocation QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html QuickFIX FAQ: http://www.quickfixengine.org/quickfix/doc/html/FAQ.html QuickFIX Support: http://www.quickfixengine.org/services.html Hi all, I'm trying to receive FIX 4.2 Allocation, but for some reason some = messages don't make it through the validation (they are rejected right away) = whereas some other don't. I'm receiving: 8=3DFIX.4.2 9=3D543 35=3DJ 34=3D111 49=3DAAA 56=3DBBB 43=3DN 50=3DXXX 52=3D20040805-08:36:25.181 70=3DA00114731HK004@4 71=3D5 73=3D1 11=3D28804 37=3D00173659HK 54=3D1 55=3D2897.JP 48=3DJP3675600005 107=3DNISSIN FOOD PRODUCTS CO LTD 22=3D4 207=3DT 53=3D100.0 6=3D1.25 15=3DJPY 75=3D20040805 60=3D20040805-16:36:23 63=3D6 64=3D20040810 381=3D125.0 118=3D126.0 58=3DCOMPLETE $$ Indicative Business Terms, Official Confirmation to = follow. $$ JP 78=3D1 79=3D214764 80=3D100.0 76=3DBNP PARIBAS PEREGRINE 439=3DBNPAJPJ2 109=3DDPB 12=3D1.0 13=3D3 153=3D1.25 154=3D126.0 119=3D126.0 120=3DJPY 136=3D2 137=3D0.0 138=3DJPY 139=3D4 137=3D0.0 138=3DJPY 139=3D7 10=3D168 Which generates this message: 8=3DFIX.4.2 9=3D123 35=3D3 34=3D115 49=3DBBB 52=3D20040805-08:36:25 56=3DAAA 45=3D111 58=3DTag not defined for this message type 371=3D12 372=3DJ 373=3D2 10=3D020 But this allocation cancellation is accepted: 8=3DFIX.4.2 9=3D542 35=3DJ 34=3D115 49=3DAAA 56=3DBBB 43=3DN 50=3DXXX 52=3D20040805-08:37:32.282 70=3DA00114731HK004@4@C 71=3D2 72=3DA00114731HK004@4 73=3D1 11=3D28804 37=3D00173659HK 54=3D1 55=3D2897.JP 48=3DJP3675600005 107=3DNISSIN FOOD PRODUCTS CO LTD 22=3D4 207=3DT 53=3D100.0 6=3D1.25 15=3DJPY 75=3D20040805 60=3D20040805-16:36:23 63=3D6 64=3D20040810 381=3D125.0 118=3D126.0 58=3DCOMPLETE $$ Indicative Business Terms, Official Confirmation to = follow. $$ JP 78=3D1 80=3D100.0 76=3DBNP PARIBAS PEREGRINE 109=3DDPB 12=3D1.0 13=3D3 153=3D1.25 154=3D126.0 119=3D126.0 120=3DJPY 136=3D2 137=3D0.0 138=3DJPY 139=3D4 137=3D0.0 138=3DJPY 139=3D7 10=3D069 I'm using QF 1.6.0, and I've downloaded the latest FIX42.xml data dictionary. Do you have any idea what could cause this behaviour? Many thanks, Ilyas This message and any attachments (the "message") is intended solely for the addressees and is confidential.=20 If you receive this message in error, please delete it and=20 immediately notify the sender. Any use not in accord with=20 its purpose, any dissemination or disclosure, either whole=20 or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message.=20 BNP PARIBAS (and its subsidiaries) shall (will) not=20 therefore be liable for the message if modified.=20 --------------------------------------------- Ce message et toutes les pieces jointes (ci-apres le=20 "message") sont etablis a l'intention exclusive de ses=20 destinataires et sont confidentiels. Si vous recevez ce=20 message par erreur, merci de le detruire et d'en avertir=20 immediatement l'expediteur. Toute utilisation de ce=20 message non conforme a sa destination, toute diffusion=20 ou toute publication, totale ou partielle, est interdite, sauf=20 autorisation expresse. L'internet ne permettant pas=20 d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce=20 message, dans l'hypothese ou il aurait ete modifie. ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source = Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Quickfix-developers mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfix-developers |
From: Joerg T. <Joe...@ma...> - 2004-08-05 11:56:59
|
Hi both, > Tag 12 appears in a group (78 NoAllocs). Is it possible that tag 439 doesn't > appear in the description of the group? Yes, the tag is only part of ExecutionReport, NewOrderSingle, OrderCancelReplaceRequest and the NoOrders group of SettlementInstructions. Starting with FIX 4.3, this field is replaced anyway. > If this is the case (I have no 4.2 description on my desk), the group is > closed and tag 12 is found in the wrong context (outside of the group). The > second message doesn't contain tag 439 and tag 12 is seen in the context of > 78 NoAllocs. So this analyis is correct. Cheers, Jörg -- Joerg Thoennes http://macd.com Tel.: +49 (0)241 44597-24 Macdonald Associates GmbH Fax : +49 (0)241 44597-10 Lothringer Str. 52, D-52070 Aachen |