[This message was posted by Citadel Bank of Confidential <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/8de44dd0 - PLEASE DO NOT REPLY BY MAIL.]
Would it be a terrible idea to just return PriceType with the SecurityDefinition as an added field for FIX4.2 clients? I don't really want to force clients to use FIX5.0 and I also don't want someone to submit an order thinking he is specifying price when we are expecting yield. Right now the plan is to require the PriceType be set in the NewOrderSingle message and if the type does not match the expected type we reject the order and the OrdRejReason text field will supply the proper PriceType, but of course that is less than ideal since the client has no reasonable way to divine what PriceType we expect except by assuming conventional pricing. > Actually, PriceType is included in the SecurityDefinition message but it > is a little hard to find. > > With FIX 5 SP1, the area of reference data was significantly extended to > capture all kinds of information related to the trading of securities. > Previously, this kind of information all had to be documented somewhere > whereas you can now convey it electronically. Also, the concept of > market segments was introduced. You need to associate the security with > at least one market segment to define the default PriceType as follows. > > Each market segment contains SecurityTradingRules which consist of > BaseTradingRules and TradingSessionRules. The base rules contain the > PriceType field among a lot of other information. > > Your SecurityDefinition message only needs to have the following: > > 48 SecurityID = <identifier> 22 SecurityIDSource = <domain for > SecurityID> 1310 NoMarketSegments = 1 1301 > MarketID = <MID code> > (recommended to use when defining a segment) 1300 > MarketSegmentID = > <your segment name> > 423 > PriceType = <default price type for the security> > > You can then define in your rules of engagement that this default value > may be overridden by a value in the order level messages. I do not know > whether you allow your clients to tell you the price type they are using > or if you set the price type by sending out reference data. > > Regards, Hanno. > > > Hi All, > > > > I'm wondering why the PriceType (423) field is not included in the > > SecurityDefinition message. Wouldn't it be useful to specify how a > > security is priced? [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]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=.
