NATIONAL STOCK EXCHANGE OF INDIA LIMITED DEPARTMENT : CAPITAL MARKET SEGMENT. Download Ref No : NSE/CMTR/35163 Date : June 21, 2017

Transcription

1 NATIONAL STOCK EXCHANGE OF INDIA LIMITED DEPARTMENT : CAPITAL MARKET SEGMENT Download Ref No : NSE/CMTR/3563 Date : June 2, 207 Circular Ref. No : 36/207 All Members, Tick by Tick market data via This is further to Exchange circular NSE/CMTR/34986 dated May 30, 207. The revised details of market data broadcast for Tick by Tick order trade data via are provided in Annexure. Members may kindly note the below summary of changes their respective effective dates. Sr. Change Effective date Replacing Source 2 with (delayed feed) July 0, Changes in recovery of tick by tick data July 0, Discontinuation of Source July 2, Discontinuation of broadcast of files August 05, 207 Important Notes:. Market participants are advised to subscribe migrate to New Source at the earliest for better experience as compared to existing Source (delayed feed) shall have a lag as compared to New Source. 3. Further, market participants are also advised to monitor adequately size their infrastructure systems while subscribing to these feeds. For on behalf of National Exchange of India Limited Khushal Shah Chief Manager Toll Free No Fax No id msm@nse.co.in Regd. Office : Exchange Plaza, Bra Kurla Complex, Bra (E), Mumbai Page of 5

2 A) Master Files for MTBT Annexure Tick by Tick order trade data via (MTBT) Members may kindly note that the below changes shall be effective from August 5, 207. Exchange provides MTBT files for mapping information about the stre id token number of the security/contract on specified extranet paths as well as via broadcast. The updated files shall continue to be available on the path given below. However, based on process review member feedback, it has been decided to discontinue the dissemination of information via broadcast. Segment Extranet path File ne CM /ftp/common/tbt_s cm_contract_stre_info.csv FO /faoftp/faocommon/tbt_s fo_spd_contract_stre_info.csv fo_contract_stre_info.csv /cdsftp/cdscommon/tbt_s cd_contract_stre_info.csv cd_spd_contract_stre_info.csv B) Segment wise details of IP address port are as below: Members are requested to make note of the following changes:- ) Replacing Source 2 with (delayed feed) w.e.f July 0, 207 2) Source shall be discontinued w.e.f EOD of July 2, 207 Market participants are advised to subscribe migrate to New Source at the earliest for better experience as compared to existing Source 2. Further, market participants are also advised to monitor adequately size their infrastructure systems while subscribing to these feeds CM bwidth Mbps Mbps Mbps Mbps Regd. Office : Exchange Plaza, Bra Kurla Complex, Bra (E), Mumbai Page 2 of 5

3 FO bwidth Nifty options NIFTY contracts all other Index option contracts (other than NIFTY BANKNI FTY) starting S to Z) starting I to L) BANKNI FTY options starting A to B) Mbps Mbps Mbps Mbps Mbps Mbps Mbps Regd. Office : Exchange Plaza, Bra Kurla Complex, Bra (E), Mumbai Page 3 of 5

4 8 starting C to H) starting M to R) Mbps All currency pairs interest rate bwidth Kbps Note: The approximate bwidth mentioned above is current of each stre will vary as per market activity. With respect to using Exchange data, Member s may kindly take note of Exchange circular NSE/MEM/26958 dated June 9, 204. Exchange data can be used by Member s clients who are registered for trading with the member on the Exchange in any segment. C) Tick agent Tick Agent application is an optional utility provided by the exchange can be installed at client end server for receiving tick data. Tick data which consists of orders trades is received from the exchange on multicast by tick agent. The tick agent forwards the se data to client end applications on multicast. Tick Agent also provides tick data recovery on TCP. If the client application loses tick data on multicast, it can request the tick agent for recovering the missed tick data on TCP. Client end applications can receive multicast tick data directly without using tick agent. They can also recover missed tick data from the exchange directly on TCP. The TICK Agent application file is available for members on extranet on the below path- Segment Tick Agent Setup Path on Extranet CM /common/tbt_linux/tick_agent_linux_.0.3 /common/tbt_windows/tick_agent_windows_.3 FO /faoftp/faocommon/tbt_linux/tick_agent_linux_.0.3 /faoftp/faocommon/tbt_windows/tick_agent_windows_.3 /cdsftp/cdscommon/tbt_linux/tick_agent_linux_.0.3 /cdsftp/cdscommon/tbt_windows/tick_agent_windows_.3 Regd. Office : Exchange Plaza, Bra Kurla Complex, Bra (E), Mumbai Page 4 of 5

5 D) Recovery of tick by tick data Members are requested to note that the below change shall be effective from July 0, 207. Tick by tick data is available for recovery on TCP. At the exchange end the recovery requests are managed serviced through a setup consisting of a load balancer server multiple recovery servers. If the client end application misses any tick data it can recover the missed ticks by sending request on TCP to the server IP provided by the exchange (segment wise IPs ports are provided below). The response messages will be provided on TCP. The TCP connections for recovering messages are not persistent. A new connection has to be made for each every recovery request. Client end applications using tick agent can recover missed tick data on TCP by sending recovery request to the tick agent. Also, the recovery requests are served from file stored in recovery server. Due to these factors, there is a lag / delay in the tick data from recovery servers, as compared to direct multicast feed. Segment CM FO Regd. Office : Exchange Plaza, Bra Kurla Complex, Bra (E), Mumbai Page 5 of 5