[This message was posted by Kingshuk Bandyopadhyay of <kings...@gmail.com> to the "India" discussion forum at http://fixprotocol.org/discuss/54. You can reply to it on-line at http://fixprotocol.org/discuss/read/a214b702 - PLEASE DO NOT REPLY BY MAIL.]
The execution report also has ExecType set to Rejected. So looks like your order was rejected. Though why they set the OrdStatus to 3 I can't say. > Folks, I am trying to send a NewOrderSingle to the NSE-FIX-Test-Environment > and I always receive a response with OrdStatus (39): 3 (DONE FOR DAY), any > idea why ? Needless to say, I am able to login & the test-market is OPEN. > > Thanks in advance, Sanjay > ----------------------------------------------------- > Order message sent > > No. Time Source Destination Protocol Info > 4952 1876.170065 192.168.50.56 192.168.10.1 FIX > NewOrderSingle > > Frame 4952: 301 bytes on wire (2408 bits), 301 bytes captured (2408 bits) > Ethernet II, Src: IntelCor_f0:55:38 (00:1c:c0:f0:55:38), Dst: > HewlettP_4e:cb:5e (00:02:a5:4e:cb:5e) > Internet Protocol, Src: 192.168.50.56 (192.168.50.56), Dst: 192.168.10.1 > (192.168.10.1) > Transmission Control Protocol, Src Port: lam (2040), Dst Port: 9652 (9652), > Seq: 652, Ack: 677, Len: 247 > Financial Information eXchange Protocol > BeginString (8): FIX.4.2 > BodyLength (9): 224 > MsgType (35): D (ORDER SINGLE) > MsgSeqNum (34): 60 > SenderCompID (49): XXXXX > SendingTime (52): 20101006-14:18:46.056 > TargetCompID (56): NSE_TAP_FO > Account (1): XXXXX > ClOrdID (11): 18001 > HandlInst (21): 1 (AUTOMATED EXECUTION ORDER PRIVATE) > OrderQty (38): 10 > OrdType (40): 2 (LIMIT) > Price (44): 6500 > SecurityID (48): 37215 > Side (54): 1 (BUY) > Symbol (55): NIFTY > TransactTime (60): 20101006-14:18:46.056 > SecurityType (167): FUT (FUTURE) > MaturityMonthYear (200): 112010 > CustomerOrFirm (204): 1 (FIRM) > MaturityDay (205): 25 > ComplianceID (376): XXXXX > ClearingAccount (440): XXXXX > Product (460): 7 (INDEX) > CheckSum (10): 079 [correct] > > ORDER RESPONSE > > > No. Time Source Destination Protocol Info > 4955 1876.232761 192.168.10.1 192.168.50.56 FIX > ExecutionReport > > Frame 4955: 446 bytes on wire (3568 bits), 446 bytes captured (3568 bits) > Ethernet II, Src: HewlettP_4e:cb:5e (00:02:a5:4e:cb:5e), Dst: > IntelCor_f0:55:38 (00:1c:c0:f0:55:38) > Internet Protocol, Src: 192.168.10.1 (192.168.10.1), Dst: 192.168.50.56 > (192.168.50.56) > Transmission Control Protocol, Src Port: 9652 (9652), Dst Port: lam (2040), > Seq: 677, Ack: 899, Len: 392 > Financial Information eXchange Protocol > BeginString (8): FIX.4.2 > BodyLength (9): 369 > MsgType (35): 8 (EXECUTION REPORT) > MsgSeqNum (34): 161 > SenderCompID (49): NSE_TAP_FO > SendingTime (52): 20101006-14:19:05.484 > TargetCompID (56): XXXXX > OnBehalfOfLocationID (144): 2 > OnBehalfOfSendingTime (370): 20101006-14:18:37 > Account (1): XXXXX > AvgPx (6): 0 > ClOrdID (11): 18001 > CumQty (14): 0 > ExecID (17): 2231OR20101006000022360000018001 > ExecTransType (20): 0 (NEW) > HandlInst (21): 1 (AUTOMATED EXECUTION ORDER PRIVATE) > SecurityIDSource (22): 8 (EXCHANGE SYMBOL) > OrderID (37): 2010100600002236 > OrderQty (38): 10 > OrdStatus (39): 3 (DONE FOR DAY) > OrdType (40): 2 (LIMIT) > Price (44): 6500 > SecurityID (48): 37215 > Side (54): 1 (BUY) > Symbol (55): NIFTY > Text (58): 16273 > TimeInForce (59): 0 (DAY) > TransactTime (60): 20101006-14:18:37 > PositionEffect (77): O (OPEN) > StopPx (99): 0 > MaxFloor (111): 0 > ExecType (150): 8 (REJECTED) > LeavesQty (151): 10 > SecurityType (167): FUT (FUTURE) > MaturityMonthYear (200): 198001 > CustomerOrFirm (204): 1 (FIRM) > MaturityDay (205): 01 > ClearingAccount (440): XXXXX > Product (460): 7 (INDEX) > CheckSum (10): 222 [correct] > [You can unsubscribe from this discussion group by sending a message to mailto:unsubscribe+100932...@fixprotocol.org] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to fix-proto...@googlegroups.com. To unsubscribe from this group, send email to fix-protocol+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
