You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(13) |
Jun
(21) |
Jul
(14) |
Aug
(29) |
Sep
(39) |
Oct
(47) |
Nov
(70) |
Dec
(27) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(43) |
Feb
(50) |
Mar
(90) |
Apr
(96) |
May
(84) |
Jun
(40) |
Jul
(58) |
Aug
(55) |
Sep
(55) |
Oct
(52) |
Nov
(38) |
Dec
(75) |
| 2008 |
Jan
(49) |
Feb
(72) |
Mar
(49) |
Apr
(55) |
May
(21) |
Jun
(31) |
Jul
(47) |
Aug
(59) |
Sep
(59) |
Oct
(77) |
Nov
(51) |
Dec
(54) |
| 2009 |
Jan
(52) |
Feb
(57) |
Mar
(17) |
Apr
(27) |
May
(44) |
Jun
(46) |
Jul
(69) |
Aug
(38) |
Sep
(39) |
Oct
(45) |
Nov
(38) |
Dec
(37) |
| 2010 |
Jan
(49) |
Feb
(35) |
Mar
(21) |
Apr
(33) |
May
(52) |
Jun
(28) |
Jul
(39) |
Aug
(34) |
Sep
(21) |
Oct
(82) |
Nov
(36) |
Dec
(20) |
| 2011 |
Jan
(28) |
Feb
(64) |
Mar
(93) |
Apr
(75) |
May
(151) |
Jun
(77) |
Jul
(35) |
Aug
(53) |
Sep
(56) |
Oct
(36) |
Nov
(94) |
Dec
(59) |
| 2012 |
Jan
(105) |
Feb
(43) |
Mar
(68) |
Apr
(91) |
May
(45) |
Jun
(18) |
Jul
(103) |
Aug
(77) |
Sep
(45) |
Oct
(59) |
Nov
(58) |
Dec
(43) |
| 2013 |
Jan
(48) |
Feb
(65) |
Mar
(63) |
Apr
(22) |
May
(41) |
Jun
(60) |
Jul
(43) |
Aug
(17) |
Sep
(20) |
Oct
(20) |
Nov
(42) |
Dec
(43) |
| 2014 |
Jan
(54) |
Feb
(34) |
Mar
(34) |
Apr
(20) |
May
(31) |
Jun
(39) |
Jul
(66) |
Aug
(22) |
Sep
(52) |
Oct
(22) |
Nov
(67) |
Dec
(70) |
| 2015 |
Jan
(18) |
Feb
(5) |
Mar
(40) |
Apr
(32) |
May
(62) |
Jun
(28) |
Jul
(86) |
Aug
(44) |
Sep
(61) |
Oct
(65) |
Nov
(8) |
Dec
(19) |
| 2016 |
Jan
(50) |
Feb
(22) |
Mar
(38) |
Apr
(55) |
May
(30) |
Jun
(42) |
Jul
(11) |
Aug
(9) |
Sep
(4) |
Oct
(51) |
Nov
(38) |
Dec
(31) |
| 2017 |
Jan
(40) |
Feb
(40) |
Mar
(23) |
Apr
(35) |
May
(121) |
Jun
(55) |
Jul
(37) |
Aug
(16) |
Sep
(27) |
Oct
(109) |
Nov
(67) |
Dec
(23) |
| 2018 |
Jan
(52) |
Feb
(6) |
Mar
(23) |
Apr
(28) |
May
(32) |
Jun
(20) |
Jul
(20) |
Aug
(22) |
Sep
(8) |
Oct
(33) |
Nov
(32) |
Dec
(13) |
| 2019 |
Jan
(16) |
Feb
(29) |
Mar
(17) |
Apr
(16) |
May
(1) |
Jun
(2) |
Jul
(25) |
Aug
(50) |
Sep
(17) |
Oct
(29) |
Nov
(16) |
Dec
(7) |
| 2020 |
Jan
|
Feb
|
Mar
(29) |
Apr
(64) |
May
(25) |
Jun
(49) |
Jul
(15) |
Aug
(10) |
Sep
(37) |
Oct
(20) |
Nov
(19) |
Dec
(9) |
| 2021 |
Jan
(33) |
Feb
(10) |
Mar
(67) |
Apr
(40) |
May
(70) |
Jun
(33) |
Jul
(14) |
Aug
(10) |
Sep
|
Oct
(7) |
Nov
(6) |
Dec
(16) |
| 2022 |
Jan
(27) |
Feb
(2) |
Mar
(5) |
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(6) |
Oct
(2) |
Nov
|
Dec
(10) |
| 2023 |
Jan
(1) |
Feb
(2) |
Mar
(21) |
Apr
(3) |
May
(15) |
Jun
(3) |
Jul
(4) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(1) |
| 2024 |
Jan
(7) |
Feb
(2) |
Mar
(8) |
Apr
(11) |
May
(6) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2025 |
Jan
(10) |
Feb
(4) |
Mar
(9) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: andre m. <an...@gm...> - 2007-04-10 21:21:45
|
Hey All, how can i set the SenderSubID in [SESSION] configuration? this doesn't seem to send the sendersubid correctly to my counterparty. [SESSION] BeginString=FIX.4.4 SenderCompID=Foo SenderSubID=Bar TargetCompID=Baz -- View this message in context: http://www.nabble.com/SenderSubID-in--SESSION--configuration--tf3555943.html#a9928945 Sent from the QuickFIX/J mailing list archive at Nabble.com. |
|
From: Toli K. <to...@ma...> - 2007-04-09 20:36:02
|
Hey all, I have a question about the way you think that UtcTimeStampField should preserve milliseconds. This is related to bug qfj-146: http://www.quickfixj.org/jira/browse/QFJ-146. I'm testing the QFJ-1.1 RC1 candidate, and i noticed that the way i've implemented the fix for the bug makes the milliseconds be created only if it is specified, and the default behaviour is not to preserve milliseconds. I'm starting to think that's incorrect behaviour - and that it may make more sense to *always* preserve milliseconds. So I would make appropriate changes to the UtcTimeStampField. Any other thoughts on this? Is there a particular backwards-compatibility use case where we don't want to make that change? -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: Alvin W. <AW...@FF...> - 2007-04-03 20:27:55
|
Hi Robert,
I believe CFI Code should be used for option and futures. Hope this helps.
Alvin
"Robert
Brueckmann"
<rbrueckmann@merl To
insecurities.com> <qui...@li....
Sent by: net>
quickfixj-users-b cc
ou...@li...
ceforge.net Subject
Re: [Quickfixj-users] FIX 4.3
SecurityType
04/03/2007 04:15
PM
Please respond to
quickfixj-users@l
ists.sourceforge.
net
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
My email was sent in HTML format originally so I apologize for the
duplicate emails but here's the text-version:
-----
I'm getting an ExecutionReport message from a vendor and they're sending
me a FIX4.3 message with 167=OPT, which translates to SecurityType of
Option...but according to the FIX4.3.xml file for the version of
Quickfix/J I'm using (1.0.3), it's rejecting the message because OPT
isn't a viable SecurityType...but it is in FIX 4.2...is this fixed in
the newer engine release? Do I just manually update the FIX4.3.xml file
and re-jar it up? I haven't looked at the official 4.3 specs but is
this a valid rejection or does 1.0.3 have an invalid data dictionary for
4.3? I didn't see anything in JIRA related to this...that I could
search for successfully, anyway...
Thanks for any help,
rlb
-----
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
*******************************************************************************
This e-mail message is intended solely for the use of the addressee.
The message may contain information that is privileged and
confidential.
Disclosure to anyone other than the intended recipient is prohibited.
If you are not the intended recipient, please do not disseminate,
distribute or copy this communication, by e-mail or otherwise. Instead,
please notify us immediately by return e-mail(including the original
message with your reply) and then delete and discard all copies of the
message. We have taken precautions to minimize the risk of transmitting
software viruses but nevertheless advise you to carry out your own
virus checks on any attachment to this message. We accept
no liability for any loss or damage caused by software viruses.
*******************************************************************************
|
|
From: Robert B. <rbr...@me...> - 2007-04-03 20:23:18
|
Oh man...I should have just checked the official FIX protocol specs before submitting this question...I answered my own question by doing so...and for those out there wondering, the official 4.3 specs state: Futures and Options should be specified using the CFICode[461] field instead of SecurityType[167] (Refer to Volume 7 - Recommendations and Guidelines for Futures and Options Markets.") Sorry for the unnecessary emails! Thanks, robert l. brueckmann vice president merlin securities 712 fifth avenue new york, ny 10019 p: 212.822.4821 f: 212.822.4820 -----Original Message----- From: qui...@li... [mailto:qui...@li...] On Behalf Of Robert Brueckmann Sent: Tuesday, April 03, 2007 4:15 PM To: qui...@li... Subject: Re: [Quickfixj-users] FIX 4.3 SecurityType QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ My email was sent in HTML format originally so I apologize for the duplicate emails but here's the text-version: ----- I'm getting an ExecutionReport message from a vendor and they're sending me a FIX4.3 message with 167=3DOPT, which translates to SecurityType of Option...but according to the FIX4.3.xml file for the version of Quickfix/J I'm using (1.0.3), it's rejecting the message because OPT isn't a viable SecurityType...but it is in FIX 4.2...is this fixed in the newer engine release? Do I just manually update the FIX4.3.xml file and re-jar it up? I haven't looked at the official 4.3 specs but is this a valid rejection or does 1.0.3 have an invalid data dictionary for 4.3? I didn't see anything in JIRA related to this...that I could search for successfully, anyway... =20 Thanks for any help, rlb ----- ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE= VDE V _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users |
|
From: Robert B. <rbr...@me...> - 2007-04-03 20:15:34
|
My email was sent in HTML format originally so I apologize for the duplicate emails but here's the text-version: ----- I'm getting an ExecutionReport message from a vendor and they're sending me a FIX4.3 message with 167=3DOPT, which translates to SecurityType of Option...but according to the FIX4.3.xml file for the version of Quickfix/J I'm using (1.0.3), it's rejecting the message because OPT isn't a viable SecurityType...but it is in FIX 4.2...is this fixed in the newer engine release? Do I just manually update the FIX4.3.xml file and re-jar it up? I haven't looked at the official 4.3 specs but is this a valid rejection or does 1.0.3 have an invalid data dictionary for 4.3? I didn't see anything in JIRA related to this...that I could search for successfully, anyway... =20 Thanks for any help, rlb ----- |
|
From: Robert B. <rbr...@me...> - 2007-04-03 20:10:46
|
I'm getting an ExecutionReport message from a vendor and they're sending me a FIX4.3 message with 167=3DOPT, which translates to SecurityType of Option...but according to the FIX4.3.xml file for the version of Quickfix/J I'm using (1.0.3), it's rejecting the message because OPT isn't a viable SecurityType...but it is in FIX 4.2...is this fixed in the newer engine release? Do I just manually update the FIX4.3.xml file and re-jar it up? I haven't looked at the official 4.3 specs but is this a valid rejection or does 1.0.3 have an invalid data dictionary for 4.3? I didn't see anything in JIRA related to this...that I could search for successfully, anyway... =20 Thanks for any help, =20 robert l. brueckmann vice president merlin securities 712 fifth avenue new york, ny 10019 p: 212.822.4821 f: 212.822.4820 =20 |
|
From: Mohammad K. L. <kam...@gm...> - 2007-03-30 11:33:32
|
Hi there!! What configurations do I need on client and server side to avoid the *MsgSeqNum too low* error? Please mention the tags I need for it.Moreover do I need to do anything in the code to set the values for MsgSeqNum on both sides? Thanks in advance, Kamran. |
|
From: Steve B. <st...@te...> - 2007-03-30 03:53:38
|
Hi Stacy, > 2-For testing purposes is there a way to read a FIX message defined in the > code or a text file? In the upcoming QFJ 1.1 release the FIXMessageDecoder can be used to extract messages from a file that can also contain any other content. You can request a list of messages to be returned or you can have the messages streamed to you if the file is so large that memory might be a problem. Steve |
|
From: Naresh B. <NB...@sa...> - 2007-03-29 20:37:51
|
That's the best explanation of FIX version differences I have seen thus = far. Somehow, it did not come across from the FIX manuals. Thanks so = much J=F6rg! =20 Naresh ________________________________ From: qui...@li... on behalf of Joerg = Thoennes Sent: Thu 3/29/2007 3:56 PM To: qui...@li... Subject: Re: [Quickfixj-users] Can DataDictionary be used to create = messages? QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ Hi Naresh, On 03/29/07 14:48, Naresh Bhatia wrote: > Just out of curiosity, are message types and field tags compatible = between the various FIX > versions? I understand that messages and fields may be added / removed = between various versions, > but is it possible that the same message can have a different MsgType = or the same field can have > a different field tag? Actually, field tags are never removed, just deprecated. Sometimes the = names change, ie from IDSource in FIX 4.2 to SecurityIDSource in FIX 4.4, but the tag value = stays the same. In addition, the tags are independent from the message type: The same = tag value has the same meaning in every message which uses it. So if you upgrade from one FIX version to the next, either a tag is = continued to be used with the same meaning (possibly a changed name) or it is deprecated (not used any = longer). Hope that makes thing clearer for you. Cheers, J=F6rg -- Joerg Thoennes http://www.macd.com <http://www.macd.com/> Tel.: +49 = (0)241 44597-24 Macdonald Associates GmbH Gesch=C3=A4ftsf=C3=BChrer: Roger = Macdonald Lothringer Str. 52, D-52070 Aachen Amtsgericht Aachen, HRB 8151, = Ust.-Id DE813021663 -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share = your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users |
|
From: Joerg T. <Joe...@ma...> - 2007-03-29 19:56:35
|
Hi Naresh, On 03/29/07 14:48, Naresh Bhatia wrote: > Just out of curiosity, are message types and field tags compatible between the various FIX > versions? I understand that messages and fields may be added / removed between various versions, > but is it possible that the same message can have a different MsgType or the same field can have > a different field tag? Actually, field tags are never removed, just deprecated. Sometimes the names change, ie from IDSource in FIX 4.2 to SecurityIDSource in FIX 4.4, but the tag value stays the same. In addition, the tags are independent from the message type: The same tag value has the same meaning in every message which uses it. So if you upgrade from one FIX version to the next, either a tag is continued to be used with the same meaning (possibly a changed name) or it is deprecated (not used any longer). Hope that makes thing clearer for you. Cheers, Jörg -- Joerg Thoennes http://www.macd.com Tel.: +49 (0)241 44597-24 Macdonald Associates GmbH Geschäftsführer: Roger Macdonald Lothringer Str. 52, D-52070 Aachen Amtsgericht Aachen, HRB 8151, Ust.-Id DE813021663 |
|
From: Toli K. <to...@ma...> - 2007-03-29 19:32:19
|
Stacy, > 1 - If I use Message Cracker when receiving a message, does that mean that I > must define ALL the fields that might be in the FIX message I'm receiving? > Or only the ones I care about. I looked at the documentation and the section > called 'receiving messages' and I'm still not clear on this. You can only override the methods you are interested in. Look at the Ordermatch example, it's only dealing with incoming NewOrderSingle messages: http://quickfixj.svn.sourceforge.net/viewvc/quickfixj/trunk/examples/src/main/java/quickfix/examples/ordermatch/Application.java?revision=464&view=markup I'm not sure i understand your question. What do you mean by "define all fields that may be in FIX message"? You only "subscribe" to the kinds of messages you want (by overriding the right onMessage functions) and deal with them, extracting whatever fields you want. > 2-For testing purposes is there a way to read a FIX message defined in the > code or a text file? You can use the Message(String text) constructor to create a message from an existing string (so you can iterate over your file): Here's an example of it in our code: http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/main/java/org/marketcetera/spring/JMSFIXMessageConverter.java#L58 and an example in the test code in QFJ (line 85): http://quickfixj.svn.sourceforge.net/viewvc/quickfixj/trunk/core/src/test/java/quickfix/MessageTest.java?revision=601&view=markup You can also take a look at our OrderLoader code that reads orders from a file and sends them to our OMS: http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/orderloader/src/main/java/org/marketcetera/orderloader/OrderLoader.java and if you want to try it out (sorry, this is a plug) you can just download the entire Marketcetera platform and mess with our code directly, it may be a better way to get started by looking at examples: http://trac.marketcetera.org -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: stacyann_1 <sta...@gs...> - 2007-03-29 18:57:42
|
I a super newbie with QuickFix/J, so please bear with me. 2 Questions 1 - If I use Message Cracker when receiving a message, does that mean that I must define ALL the fields that might be in the FIX message I'm receiving? Or only the ones I care about. I looked at the documentation and the section called 'receiving messages' and I'm still not clear on this. 2-For testing purposes is there a way to read a FIX message defined in the code or a text file? Thanks, Stacy -- View this message in context: http://www.nabble.com/Message-Cracker-and-Testing-tf3488232.html#a9740394 Sent from the QuickFIX/J mailing list archive at Nabble.com. |
|
From: Toli K. <to...@ma...> - 2007-03-29 17:51:15
|
Mohammad,
The log file you've attached doesn't show the same errors that you
mentioned, only errors about MsgSeqNum resets.
Your message looks almost right:
> > Date date=new Date();
> > NewOrderSingle order = new NewOrderSingle();
> > order.setField(new MsgType("D"));
you don't need this - creating a NewOrderSignle sets the MsgType
already. Also, you need to set it in the header:
order.getHeader().setField(new MsgType(MsgType.ORDER_SINGLE));
> > order.setField(new HandlInst('2'));
> > order.setField(new HeartBtInt(30));
> > order.setField(new BeginString("FIX.4.2"));
> > order.setField(new SenderCompID("client1"));
> > order.setField(new TargetCompID("ifkaar"));
These also need to go into the message header:
order.getHeader().setField(new SenderCompID("client1"));
order.getHeader().setField(new TargetCompID("ifkaar"));
> > order.setField(new OrdType(OrdType.LIMIT));
> > order.setField(new ClOrdID("clor"));
> > order.setField(new Symbol("symbol"));
> > order.setField(new Side('c'));
Looking at Side class, i'm not seeing anything with the 'c' value. Is
this a typo or are you setting some custom value? There's
Side.OPPOSITE but that's an upper-case 'C'
> > order.setField(new TransactTime(date));
> > order.setField(new Text("New Order"));
> > Session.sendToTarget(order,"sender","target");
Your senderCompID and targetCompID should match between what you've
set in the message and what you pass to the sendToTarget() function.
currently, they don't.
I was able to take the above code and send it through, didn't have any
problems with ClOrdID or Side fields.
> > I have attached the messages log file as well,, according to which my
> ClOrdID and Side fields are missing in the message but you can see I have
> included them in my order,,can u plz help me sort it out?
Again, the attached logs didn't show anything so you'll need to send
me the right logs.
good luck.
--
Toli Kuznets
http://www.marketcetera.com: Open-Source Trading Platform
download.run.trade.
|
|
From: Naresh B. <NB...@sa...> - 2007-03-29 12:48:58
|
Thanks Toli. I have added an enhancement request to JIRA: QFJ-159. =20 Just out of curiosity, are message types and field tags compatible = between the various FIX versions? I understand that messages and fields = may be added / removed between various versions, but is it possible that = the same message can have a different MsgType or the same field can have = a different field tag? =20 Thanks. Naresh ________________________________ From: qui...@li... on behalf of Toli = Kuznets Sent: Thu 3/29/2007 2:40 AM To: qui...@li... Subject: Re: [Quickfixj-users] Can DataDictionary be used to create = messages? QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ QuickFIX/J Support: http://www.quickfixj.org/support/ Ah, the context helps. Now it makes sense. Looking at the DataDictionary, it seems that it doesn't actually track msgTypeName -> msgType mappings. But it can be easily done in the DataDictionary.addValueName() function You should file an RFE: http://www.quickfixj.org/jira/, including your use case. It's pretty easy to implement, but i'd defer to Steve Bate to make a decision on whether or not and how to implement this, or to perhaps suggest an alternative work flow. On 3/28/07, Naresh Bhatia <NB...@sa...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Maybe I need to give some more context. The requirement I have is to = be > able to change the message metadata dynamically. For example, if a > custom field tag value is wrong in a running system, then I should be > able to correct it without bouncing the system. Hence message creation > and parsing should be completely metadata driven (no hard coding is > allowed in code). I think message parsing can be completely driven by > the DataDictionary, but I am not sure if message creation can be = driven > by the same metadata, especially due to issue #1. What I need is a > simple method on the DataDictionary that returns a msgType given the > message name. For example, > > String getMsgType(String msgName); > > Thus dd.getMsgType("NewOrderSingle") will return "D". > > I think the DataDictionary has this information, I just don't see a > method to get it out of there. > > Naresh > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of = Toli > Kuznets > Sent: Wednesday, March 28, 2007 8:47 PM > To: qui...@li... > Subject: Re: [Quickfixj-users] Can DataDictionary be used to create > messages? > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Naresh, > > Maybe i'm not understanding what you ultimately want to do. > > > 1) Given a message name (e.g. "NewOrderSingle"), how can I get the > msgType > > (e.g. "D") using the DataDictionary? I do not readily see an method = to > do > > this. > The usual pattern is to use a MessageFactory to create a message: > factory.create(MsgType.ORDER_SINGLE) > > > 2) Is it safe to create fields using code like new ClOrdID("321")? I > see > > that the constructor of ClOrdID hard codes the field tag to "11". = Are > these > > tags values same across all FIX versions? I am thinking of this > alternate > > approach to pick up the tag value from the data dictionary - does it > make > > sense or is it needlessly complicated? > > The ClOrdID.FIELD value is the same across all FIX versions. the > quickfix.field.xxx objects are auto-generated from the FIX4x.xml data > dictionary files so the values should be constant. > > > new StringField(dd.getFieldTag("ClOrdID"), "321") > > so this may be better written as: new ClOrdID("321") or new > StringField(ClOrdID.FIELD, "321") if you don't want to be specific. > > If you are adding your own custom fields to the FIX4x.xml file, then > go ahead and create the objects for them - that's what we did, you can > see the example at > = http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/m > = ain/java/org/marketcetera/quickfix/customfields/NoMarketDataSnapshots.ja > va > > hope this helps. > > -- > Toli Kuznets > http://www.marketcetera.com: Open-Source Trading Platform > download.run.trade. > > = ------------------------------------------------------------------------ > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to = share > your > opinions on IT & business topics through brief surveys-and earn cash > = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE > V > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > = -------------------------------------------------------------------------= > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to = share your > opinions on IT & business topics through brief surveys-and earn cash > = http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. -------------------------------------------------------------------------= Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share = your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDEV _______________________________________________ Quickfixj-users mailing list Qui...@li... https://lists.sourceforge.net/lists/listinfo/quickfixj-users |
|
From: BEDARD G. <Gui...@sg...> - 2007-03-29 09:36:02
|
Hi, =20 What is the recommended way to handle scheduled sequence number resets (initiated by the counterparty once per day) ? =20 I would greatly appreciate a few pointers. =20 Thanking you in advance. =20 Guillaume Ce message et toutes les pieces jointes (ci-apres le "message") sont confid= entiels et etablis a l'intention exclusive de ses destinataires.=20 Toute utilisation ou diffusion non autorisee est interdite.=20 Tout message electronique est susceptible d'alteration.=20 Societe Generale Asset Management et ses filiales declinent toute responsab= ilite au titre de ce message s'il a ete altere, deforme ou falsifie.=20 =20 Decouvrez l'offre et les services de Societe Generale Asset Management sur = le site www.sgam.fr=20 =20 ********=20 =20 This message and any attachments (the "message") are confidential and inten= ded solely for the addressees.=20 Any unauthorised use or dissemination is prohibited.=20 E-mails are susceptible to alteration.=20 Neither Societe Generale Asset Management nor any of its subsidiaries or af= filiates shall be liable for the message if altered, changed or falsified.=20 =20 Find out more about Societe Generale Asset Management's proposal on www.sga= m=2Ecom |
|
From: Mohammad K. L. <kam...@gm...> - 2007-03-29 08:25:38
|
Hi Toli,,
Thanks it all works now but am being faced by an unexpected error,,
here's my code,,
*Date date=new Date();
NewOrderSingle order = new NewOrderSingle();
order.setField(new MsgType("D"));
order.setField(new HandlInst('2'));
order.setField(new HeartBtInt(30));
order.setField(new BeginString("FIX.4.2"));
order.setField(new SenderCompID("client1"));
order.setField(new TargetCompID("ifkaar"));
order.setField(new OrdType(OrdType.LIMIT));
order.setField(new ClOrdID("clor"));
order.setField(new Symbol("symbol"));
order.setField(new Side('c'));
order.setField(new TransactTime(date));
order.setField(new Text("New Order"));
Session.sendToTarget(order,"sender","target");
*
I have attached the messages log file as well,, according to which my *
ClOrdID* and *Side* fields are missing in the message but you can see I have
included them in my order,,can u plz help me sort it out?
Hope I'm not disturbing you by asking questions so often,,,
Thanks for your kind help...
On 3/29/07, Toli Kuznets <to...@ma...> wrote:
>
> QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
> QuickFIX/J Support: http://www.quickfixj.org/support/
> Oh, my bad. my misunderstanding.
>
> you can do something like this:
> order.setField(new OrdType(OrdType.LIMIT
>
> You want to use quickfix.OrdType not OrderType.
>
> See the newLimitOrder() function in the Marketcetera code:
>
> http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/main/java/org/marketcetera/quickfix/FIXMessageFactory.java#L127
>
> > Secondly can u plz clarify what's the difference between a message and
> an
> > order?
>
> Oh, there's no difference. I'm assuming the order is of
> quickfix.Message type, so i used the words interchangeably.
>
> --
> Toli Kuznets
> http://www.marketcetera.com: Open-Source Trading Platform
> download.run.trade.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Quickfixj-users mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfixj-users
>
|
|
From: Toli K. <to...@ma...> - 2007-03-29 07:02:34
|
Oh, my bad. my misunderstanding. you can do something like this: order.setField(new OrdType(OrdType.LIMIT You want to use quickfix.OrdType not OrderType. See the newLimitOrder() function in the Marketcetera code: http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/main/java/org/marketcetera/quickfix/FIXMessageFactory.java#L127 > Secondly can u plz clarify what's the difference between a message and an > order? Oh, there's no difference. I'm assuming the order is of quickfix.Message type, so i used the words interchangeably. -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: Mohammad K. L. <kam...@gm...> - 2007-03-29 06:45:33
|
Hi Toli, In fact I'm trying to set the OrderType to LIMIT not the MsgType,,can't find a way to do that,,here's the code line for it but it gives me an error,, *order.set(new OrderType(OrderType.LIMIT));* Secondly can u plz clarify what's the difference between a message and an order? Thanks. ** On 3/29/07, Toli Kuznets <to...@ma...> wrote: > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Hey, > > You can use MessageFactory.create(MsgType.<your msg type>) to create > your message > or you can do > Message msg = new Message() > msg.getHeaders().setField(new MsgType(MsgType.some_type)) > > You can use FIXopaedia to check what the required fields are, choose > the appropriate FIX version. Pick the message you are interested in, > and look at the "required" field in the table: > http://www.btobits.com/fixopaedia/fixdic42/index.html > > On 3/28/07, Mohammad Kamran Liaqat <kam...@gm...> wrote: > > QuickFIX/J Documentation: > > http://www.quickfixj.org/documentation/ > > QuickFIX/J Support: http://www.quickfixj.org/support/ > > > > Hi there!! > > > > Can anybody please help me what code to use to set the ordertype for my > > order?Moreover,what fields are mendatory to be set for an outgoing > order? > > > > Thanks. > > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveys-and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Quickfixj-users mailing list > > Qui...@li... > > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > > > > > > -- > Toli Kuznets > http://www.marketcetera.com: Open-Source Trading Platform > download.run.trade. > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > |
|
From: Toli K. <to...@ma...> - 2007-03-29 06:40:23
|
Ah, the context helps. Now it makes sense. Looking at the DataDictionary, it seems that it doesn't actually track msgTypeName -> msgType mappings. But it can be easily done in the DataDictionary.addValueName() function You should file an RFE: http://www.quickfixj.org/jira/, including your use case. It's pretty easy to implement, but i'd defer to Steve Bate to make a decision on whether or not and how to implement this, or to perhaps suggest an alternative work flow. On 3/28/07, Naresh Bhatia <NB...@sa...> wrote: > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Maybe I need to give some more context. The requirement I have is to be > able to change the message metadata dynamically. For example, if a > custom field tag value is wrong in a running system, then I should be > able to correct it without bouncing the system. Hence message creation > and parsing should be completely metadata driven (no hard coding is > allowed in code). I think message parsing can be completely driven by > the DataDictionary, but I am not sure if message creation can be driven > by the same metadata, especially due to issue #1. What I need is a > simple method on the DataDictionary that returns a msgType given the > message name. For example, > > String getMsgType(String msgName); > > Thus dd.getMsgType("NewOrderSingle") will return "D". > > I think the DataDictionary has this information, I just don't see a > method to get it out of there. > > Naresh > > -----Original Message----- > From: qui...@li... > [mailto:qui...@li...] On Behalf Of Toli > Kuznets > Sent: Wednesday, March 28, 2007 8:47 PM > To: qui...@li... > Subject: Re: [Quickfixj-users] Can DataDictionary be used to create > messages? > > QuickFIX/J Documentation: http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > Naresh, > > Maybe i'm not understanding what you ultimately want to do. > > > 1) Given a message name (e.g. "NewOrderSingle"), how can I get the > msgType > > (e.g. "D") using the DataDictionary? I do not readily see an method to > do > > this. > The usual pattern is to use a MessageFactory to create a message: > factory.create(MsgType.ORDER_SINGLE) > > > 2) Is it safe to create fields using code like new ClOrdID("321")? I > see > > that the constructor of ClOrdID hard codes the field tag to "11". Are > these > > tags values same across all FIX versions? I am thinking of this > alternate > > approach to pick up the tag value from the data dictionary - does it > make > > sense or is it needlessly complicated? > > The ClOrdID.FIELD value is the same across all FIX versions. the > quickfix.field.xxx objects are auto-generated from the FIX4x.xml data > dictionary files so the values should be constant. > > > new StringField(dd.getFieldTag("ClOrdID"), "321") > > so this may be better written as: new ClOrdID("321") or new > StringField(ClOrdID.FIELD, "321") if you don't want to be specific. > > If you are adding your own custom fields to the FIX4x.xml file, then > go ahead and create the objects for them - that's what we did, you can > see the example at > http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/m > ain/java/org/marketcetera/quickfix/customfields/NoMarketDataSnapshots.ja > va > > hope this helps. > > -- > Toli Kuznets > http://www.marketcetera.com: Open-Source Trading Platform > download.run.trade. > > ------------------------------------------------------------------------ > - > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE > V > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: Toli K. <to...@ma...> - 2007-03-29 06:23:22
|
Hey, You can use MessageFactory.create(MsgType.<your msg type>) to create your message or you can do Message msg = new Message() msg.getHeaders().setField(new MsgType(MsgType.some_type)) You can use FIXopaedia to check what the required fields are, choose the appropriate FIX version. Pick the message you are interested in, and look at the "required" field in the table: http://www.btobits.com/fixopaedia/fixdic42/index.html On 3/28/07, Mohammad Kamran Liaqat <kam...@gm...> wrote: > QuickFIX/J Documentation: > http://www.quickfixj.org/documentation/ > QuickFIX/J Support: http://www.quickfixj.org/support/ > > Hi there!! > > Can anybody please help me what code to use to set the ordertype for my > order?Moreover,what fields are mendatory to be set for an outgoing order? > > Thanks. > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Quickfixj-users mailing list > Qui...@li... > https://lists.sourceforge.net/lists/listinfo/quickfixj-users > > -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. |
|
From: Mohammad K. L. <kam...@gm...> - 2007-03-29 06:13:22
|
Hi there!! Can anybody please help me what code to use to set the ordertype for my order?Moreover,what fields are mendatory to be set for an outgoing order? Thanks. |
|
From: Naresh B. <NB...@sa...> - 2007-03-29 01:46:14
|
Maybe I need to give some more context. The requirement I have is to be
able to change the message metadata dynamically. For example, if a
custom field tag value is wrong in a running system, then I should be
able to correct it without bouncing the system. Hence message creation
and parsing should be completely metadata driven (no hard coding is
allowed in code). I think message parsing can be completely driven by
the DataDictionary, but I am not sure if message creation can be driven
by the same metadata, especially due to issue #1. What I need is a
simple method on the DataDictionary that returns a msgType given the
message name. For example,
String getMsgType(String msgName);
Thus dd.getMsgType("NewOrderSingle") will return "D".
I think the DataDictionary has this information, I just don't see a
method to get it out of there.
Naresh
-----Original Message-----
From: qui...@li...
[mailto:qui...@li...] On Behalf Of Toli
Kuznets
Sent: Wednesday, March 28, 2007 8:47 PM
To: qui...@li...
Subject: Re: [Quickfixj-users] Can DataDictionary be used to create
messages?
QuickFIX/J Documentation: http://www.quickfixj.org/documentation/
QuickFIX/J Support: http://www.quickfixj.org/support/
Naresh,
Maybe i'm not understanding what you ultimately want to do.
> 1) Given a message name (e.g. "NewOrderSingle"), how can I get the
msgType
> (e.g. "D") using the DataDictionary? I do not readily see an method to
do
> this.
The usual pattern is to use a MessageFactory to create a message:
factory.create(MsgType.ORDER_SINGLE)
> 2) Is it safe to create fields using code like new ClOrdID("321")? I
see
> that the constructor of ClOrdID hard codes the field tag to "11". Are
these
> tags values same across all FIX versions? I am thinking of this
alternate
> approach to pick up the tag value from the data dictionary - does it
make
> sense or is it needlessly complicated?
The ClOrdID.FIELD value is the same across all FIX versions. the
quickfix.field.xxx objects are auto-generated from the FIX4x.xml data
dictionary files so the values should be constant.
> new StringField(dd.getFieldTag("ClOrdID"), "321")
so this may be better written as: new ClOrdID("321") or new
StringField(ClOrdID.FIELD, "321") if you don't want to be specific.
If you are adding your own custom fields to the FIX4x.xml file, then
go ahead and create the objects for them - that's what we did, you can
see the example at
http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/m
ain/java/org/marketcetera/quickfix/customfields/NoMarketDataSnapshots.ja
va
hope this helps.
--=20
Toli Kuznets
http://www.marketcetera.com: Open-Source Trading Platform
download.run.trade.
------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDE
V
_______________________________________________
Quickfixj-users mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfixj-users
|
|
From: Toli K. <to...@ma...> - 2007-03-29 00:47:34
|
Naresh,
Maybe i'm not understanding what you ultimately want to do.
> 1) Given a message name (e.g. "NewOrderSingle"), how can I get the msgTyp=
e
> (e.g. "D") using the DataDictionary? I do not readily see an method to do
> this.
The usual pattern is to use a MessageFactory to create a message:
factory.create(MsgType.ORDER_SINGLE)
> 2) Is it safe to create fields using code like new ClOrdID("321")? I see
> that the constructor of ClOrdID hard codes the field tag to "11". Are the=
se
> tags values same across all FIX versions? I am thinking of this alternate
> approach to pick up the tag value from the data dictionary =96 does it ma=
ke
> sense or is it needlessly complicated?
The ClOrdID.FIELD value is the same across all FIX versions. the
quickfix.field.xxx objects are auto-generated from the FIX4x.xml data
dictionary files so the values should be constant.
> new StringField(dd.getFieldTag("ClOrdID"), "321")
so this may be better written as: new ClOrdID("321") or new
StringField(ClOrdID.FIELD, "321") if you don't want to be specific.
If you are adding your own custom fields to the FIX4x.xml file, then
go ahead and create the objects for them - that's what we did, you can
see the example at
http://trac.marketcetera.org/trac.fcgi/browser/platform/trunk/core/src/main=
/java/org/marketcetera/quickfix/customfields/NoMarketDataSnapshots.java
hope this helps.
--=20
Toli Kuznets
http://www.marketcetera.com: Open-Source Trading Platform
download.run.trade.
|
|
From: Naresh B. <NB...@sa...> - 2007-03-28 23:39:01
|
Hi,
=20
I am just starting out with QuickFIX/J and was wondering if the
DataDictionary can be used to create messages. I want to use a different
DataDictionary for every targetComp in my system - these dictionaries
will store customizations for each targetComp. I have two questions:
=20
1) Given a message name (e.g. "NewOrderSingle"), how can I get the
msgType (e.g. "D") using the DataDictionary? I do not readily see an
method to do this.
=20
2) Is it safe to create fields using code like new ClOrdID("321")? I see
that the constructor of ClOrdID hard codes the field tag to "11". Are
these tags values same across all FIX versions? I am thinking of this
alternate approach to pick up the tag value from the data dictionary -
does it make sense or is it needlessly complicated?
=20
new StringField(dd.getFieldTag("ClOrdID"), "321")
=20
Thanks.
Naresh
=20
|
|
From: Steve B. <st...@te...> - 2007-03-28 12:10:33
|
Chris and Alex, I've create a wiki page describing the QFJ failover support and how to configure it. http://www.quickfixj.org/confluence/x/dAI If there's problems with it, please post some related issues or bugs on the Jira site and we can improve on it in future releases. Feel free to edit the wiki page if the instructions are clear (or if there is some error in the description). Regards, Steve |