{"id":90600,"date":"2020-11-02T09:20:08","date_gmt":"2020-11-02T15:20:08","guid":{"rendered":"https:\/\/tradingtechno3.wpenginepowered.com\/?post_type=support&#038;p=90600"},"modified":"2020-11-02T09:20:09","modified_gmt":"2020-11-02T15:20:09","slug":"sgx-open-position-migration-from-msci-tw-to-ftse-twn-cme-changes-to-cross-functionality-for-certain-cbot-and-cme-products-cme-ilink-enhancements-for-location-id-and-display-quantity-and-more","status":"publish","type":"support","link":"https:\/\/tradingtechnologies.com\/support-updates\/sgx-open-position-migration-from-msci-tw-to-ftse-twn-cme-changes-to-cross-functionality-for-certain-cbot-and-cme-products-cme-ilink-enhancements-for-location-id-and-display-quantity-and-more\/","title":{"rendered":"SGX Open Position Migration from MSCI TW to FTSE TWN, CME Changes to Cross Functionality for Certain CBOT and CME Products, CME iLink Enhancements for Location ID and Display Quantity, and More"},"content":{"rendered":"\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"sgx-open-position-migration-from-msci-tw-to-ftse-twn\"><\/span><strong>SGX: Open Position Migration from MSCI TW to FTSE TWN<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>October 30<\/strong><\/h5>\n\n\n\n<p>SGX will be migrating all open positions in MSCI TW after the end of the T Session on Friday, October 30, to FTSE TWN. TT will not support this programmatically, so customers who wish to take advantage of this will need to carry out the process manually by completing the following:<\/p>\n\n\n\n<!--more-->\n\n\n\n<p><strong>X_TRADER\u00ae Platform Impact<\/strong><br>Customers should create SOD records manually in FTSE TWN that correspond to all open positions in MSCI TW. Additionally, all open positions for MSCI TW should be offset by publishing new MSCI TW SOD records such that the resulting net qty becomes zero. Customer back office records will reflect the migration when they get their clearing statement.\u00a0<\/p>\n\n\n\n<p>In order to create SODs, the X_Risk application, along with Administrative credentials is needed. Customers who do not currently use X_Risk should contact their Customer Success Manager for assistance.<\/p>\n\n\n\n<p><strong>TT\u00ae Platform Impact<\/strong><br>Customers should create SOD records manually in FTSE TWN that correspond to all open positions in MSCI TW. Additionally, all open positions for MSCI TW should be offset by publishing new MSCI TW SOD records such that the resulting net qty becomes zero. Customer back office records will reflect the migration when they get their clearing statement.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"cme-changes-to-cross-functionality-for-certain-cbot-and-cme-products\"><\/span><strong>CME: Changes to Cross Functionality for Certain CBOT and CME Products<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>November 8<\/strong><\/h5>\n\n\n\n<p>Effective Sunday, November 8 (trade date Monday, November 9), and pending all relevant regulatory review periods, with the exception of dairy products, the R-Cross functionality for CME and CBOT agriculture futures and CBOT agriculture options on CME Globex will not be supported. CME will support C-Cross functionality for these products, which is not yet supported by TT.<\/p>\n\n\n\n<p><strong>X_TRADER and TT Platform Impacts<\/strong><br>R-Cross functionality will only be available for dairy products.<\/p>\n\n\n\n<p><em>Additional Resources<\/em><br><a href=\"https:\/\/www.cmegroup.com\/notices\/electronic-trading\/2020\/10\/20201019.html#ccfc\" target=\"_blank\" rel=\"noreferrer noopener\">Globex Notice October 22, 2020<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"cme-ilink-enhancements-for-location-id-and-display-quantity\"><\/span><strong>CME: iLink Enhancements for Location ID and Display Quantity<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>November 15<\/strong><\/h5>\n\n\n\n<p>Effective Sunday, November 15 (trade date Monday, November 16), CME Group will implement iLink changes to Location ID and Displayed Quantity Order Modification for both Convenience Gateway(CGW) and Market Segment Gateway(MGSW) sessions. These changes as described below are available in DDE and UAT for customer testing.<\/p>\n\n\n\n<p><em>Location ID<\/em><br>To accurately reflect Location ID sent by client system, CME Globex will return the Location ID value on the <a href=\"https:\/\/www.cmegroup.com\/confluence\/display\/EPICSANDBOX\/iLink+3+Execution+Report+-+Cancel\">iLink Execution Report &#8211; Cancel<\/a> (tag 35-MsgType=8 &amp; tag 39-OrdStatus =4) message from the Location ID on the Order Cancel Request (tag 35-MsgType=F) message. Currently, the <a href=\"https:\/\/www.cmegroup.com\/confluence\/display\/EPICSANDBOX\/iLink+3+Execution+Report+-+Cancel\">iLink Execution Report &#8211; Cancel<\/a> contains the Location ID value from the original order.&nbsp;<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact\u00a0<\/strong><br>Tag 143-TargetLocationID on the ER-Cancel message will contain the locationID value from the Order Cancel Request message.<\/p>\n\n\n\n<p><strong>TT Platform Impact\u00a0<\/strong><br>Tag 143-TargetLocationID on iLink2 and Tag 9537-Location on iLink3 on the ER-Cancel message will contain the locationID value from the Order Cancel Request message.<\/p>\n\n\n\n<p><em>Displayed Quantity Order Modification<\/em><br>To better align with BrokerTec markets, iLink customers will no longer be able to modify the resting Displayed Quantity orders to the Non-Displayed Quantity orders, and vice versa. &nbsp; Currently, CME Globex allows this Displayed Quantity order modification for Futures and Options markets.&nbsp; With the change, CME Globex will validate display quantity value on&nbsp; iLink messages. &nbsp; Any resting Displayed Quantity order modified to become a Non-Display Quantity order, and vice versa, will be rejected. CME Globex will send an Execution Report-Reject (tag 35-MsgType=8, tag 39-OrdStatus=8) message including tag 103-OrdRejReason=5102 and tag 58-Text=&lt;Modification of orders from Iceberg to Non-iceberg &amp; vice-versa is not allowed&gt;.<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact\u00a0<\/strong><br>Tag 210-MaxShow will be impacted as noted above.<\/p>\n\n\n\n<p><strong>TT Platform Impact\u00a0<\/strong><br>Tag 210-MaxShow on iLink2 and Tag 1138-DisplayQty on iLink3 will be impacted as noted above.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"updated-cme-mandatory-ilink-3-binary-order-entry-protocol-for-msgw-and-brokertec-migration\"><\/span><strong>[UPDATED] CME: Mandatory iLink 3 Binary Order Entry Protocol for MSGW and BrokerTec Migration<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>Q4&nbsp;<\/strong><\/h5>\n\n\n\n<p>CME Group will be launching iLink 3, a new order-entry protocol for trading futures, options and BrokerTec products on CME Globex. All customers connected via Market Segment Gateway (MSGW) are encouraged to migrate to iLink 3 as early as possible prior to the iLink decommission. iLink 2 and iLink 3 for MSGW will run in parallel until February 26, 2021, and at that time will incur additional charges by CME. On March 28, 2021, iLink 2.0 for MSGW will be decommissioned.&nbsp;<\/p>\n\n\n\n<p>BrokerTec products will migrate to CME in Production on December 7 and will only be available on iLink 3 MSGW. Customers will need to obtain a dedicated iLink Session ID to be used for only the BrokerTec market segment. CGW will remain on iLink 2 and will not be impacted.<\/p>\n\n\n\n<p>MSGW iLink3 for CME products is now available in UAT for customer testing. BrokerTec products will be available in upcoming weeks and communicated in future updates.<\/p>\n\n\n\n<p>CME will be holding Saturday Mock Sessions for BrokerTec. We plan to participate in testing in Production on the following dates:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Saturday, November 7<\/li><li>Saturday, November 21<\/li><li>Saturday, December 5<\/li><\/ul>\n\n\n\n<p>Customers who wish to participate should register with the CME via this link: <a href=\"https:\/\/go.cmegroup.com\/l\/502091\/2020-08-19\/2lfnymf\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/go.cmegroup.com\/l\/502091\/2020-08-19\/2lfnymf<\/a> and contact your Onboarding\/Customer Success Manager to confirm with TT. Any change to participation in Mock Sessions will be provided in a future update.<\/p>\n\n\n\n<p>For the iLink 2 to 3 migration, CME Group does not require customers to obtain new iLink sessions. Customers will have the ability to migrate their existing iLink sessions from iLink 2 to 3 within the CME Request Center. For all existing migrated sessions, standard Session Policy Charges will apply.&nbsp;<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact<\/strong><strong><br><\/strong>X_TRADER will not support iLink 3.0 for MSGW or BrokerTec products that will migrate to CME on December 7.&nbsp;<\/p>\n\n\n\n<p>Customers keeping Link 2.0 MSGW connections will need to move their connections to CGW to maintain access to CME. Customers are strongly encouraged to migrate to the TT platform prior to the end of Q4.<\/p>\n\n\n\n<p><strong>TT Platform Impact<\/strong><strong><br><\/strong>We will support both the iLink 3.0 upgrade and the BrokerTec US migration to CME on the TT platform. iLink 3.0 for CME products is currently available in UAT for customer testing. BrokerTec products will be available in UAT the first week in November.<\/p>\n\n\n\n<p><em>Additional Resources<\/em><br><a href=\"https:\/\/www.cmegroup.com\/notices\/electronic-trading\/2020\/09\/20200928.html#decilink\" target=\"_blank\" rel=\"noreferrer noopener\">Globex Notice October 1, 2020<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"sgx-titan-dtdc-service-release-7\"><\/span><strong>SGX: Titan DTDC Service Release 7<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>November 9<\/strong><\/h5>\n\n\n\n<p>SGX is deploying Titan Service Release 7 to Production on November 9. Customers should be aware of the following change to the password rule:&nbsp; Instead of not more than 1 duplicate character, the new password rule does not allow more than 3 duplicate characters.<\/p>\n\n\n\n<p>As a recap, these are the password rules:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Minimum password length is 10 characters<\/li><li>All user-chosen passwords must contain at least one alphabetic character, one special character and one digit character.<\/li><li>Do not use the following special characters: asterisk, percentage and backslash.<\/li><li>Passwords must not have more than 3 duplicate characters.<\/li><\/ul>\n\n\n\n<p><strong>X_TRADER and TT Platform Impact<\/strong><br>Since the new password rule change is less restrictive than the existing rule, no impact to customers is expected. However, customers should verify their password meets the requirements of the above rules.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"eurex-t7-90-upgrade\"><\/span><strong>Eurex: T7 9.0 Upgrade<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>November 23<\/strong><\/h5>\n\n\n\n<p>Eurex will move forward with the T7 9.0 upgrade on November 23. Key dates are:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>September 14: Simulation start<\/li><li>November 23: Production launch<\/li><\/ul>\n\n\n\n<p>Please note that Eurex Simulation will be unavailable from September 1 to September 14.<\/p>\n\n\n\n<p>Details on Eurex T7 Release 9.0 are now available on the exchange website at <a href=\"https:\/\/www.eurexchange.com\/exchange-en\/technology\/t7\/release9\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/www.eurexchange.com\/exchange-en\/technology\/t7\/release9<\/a>.<\/p>\n\n\n\n<p><em>Trading Capacity<br><\/em>Note that With T7 Release 9.0, a new validation will verify whether the usage of the trading capacity with Agency is compliant with the client service authorization of the corresponding trading participant. As a consequence, any on-book or TES trading transaction requiring the specification of the trading capacity (e.g. on-book order add, TES trade approval) will be rejected in case a trader is using the trading capacity with valid value Agency but the business unit he belongs to is not compliant with the client service authorization. For full details, please see the <a href=\"https:\/\/www.eurex.com\/resource\/blob\/2220726\/859064cc5a35f075ff550e3df058589e\/data\/T7_Release_9.0_-_Final_Functional_Technical_Release_Notes_Eurex.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">T7 Release 9.0 Release Notes<\/a>.<\/p>\n\n\n\n<p>Tag 1031 (Execution Source Code \/ Customer Order Handling Instruction) Changes<\/p>\n\n\n\n<p>With the introduction of T7 Release 9.0, the entry of the Execution Source Code will be mandatory in case of Agency business execution (Trading Capacity A) according to valid values as specified by FIA (see Eurex Release 9.0 Notes). If no value for the Execution Source Code is entered to an on-book order or TES approval, the order respective TES trade will not be rejected but a default value (D) for the Execution Source Code will be added automatically instead. In case an invalid value is entered, the order respective TES trade will be rejected.<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact<\/strong><br>On September 14, Eurex simulation became available on the T7 9.0 API. Access in DDE is now available for customer testing.<\/p>\n\n\n\n<p>Please note that FIX Tag 1031 is not supported on the X_TRADER platform on the TT Eurex Gateway.&nbsp;<\/p>\n\n\n\n<p><strong>TT Platform Impact<\/strong><strong><br><\/strong>On September 14, Eurex simulation became available on the T7 9.0 API. Development of compatible software is in progress, and details on future availability in UAT to be published in the near future.<\/p>\n\n\n\n<p>On the TT platform, tag 1031 is supported at the Account level. For information on configuring tag 1031, please refer to <a href=\"https:\/\/library.tradingtechnologies.com\/user-setup\/eur-adding-a-eurex-account.html\">the documentation<\/a>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"euronext-oslo-bors-optiq-migration\"><\/span><strong>Euronext: Oslo B\u00f8rs Optiq Migration<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>November 30<\/strong><\/h5>\n\n\n\n<p>Following Euronext\u2019s acquisition of Oslo B\u00f8rs in June 2019, Oslo B\u00f8rs\u2019 trading systems across asset classes will migrate from the Millennium Exchange and SOLA systems to the Euronext Optiq systems. The migration timeline is as follows:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>April 13: Availability in p-EUA<\/li><li>November 14 and 21: Dress rehearsals in Production<\/li><li>November 30: Production go-live<\/li><\/ul>\n\n\n\n<p>The Oslo B\u00f8rs Migration Guidelines and Guide to New Trading System documents are available in the <a href=\"https:\/\/connect2.euronext.com\/it-documentation-library\/by-project?project_target_id=1714\">IT Documentation<\/a> section of the Euronext Connect customer portal.<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact<\/strong><strong><br><\/strong>Oslo B\u00f8rs products will not be supported on the X_TRADER platform.<\/p>\n\n\n\n<p><strong>TT Platform Impact<\/strong><br>Oslo B\u00f8rs products are available for customer testing in UAT.&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"tt-fix-ssl-certificate-update\"><\/span><strong>TT: FIX SSL Certificate Update<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>December 11<\/strong><\/h5>\n\n\n\n<p>For customers whose FIX engine natively supports SSL encryption, or who have implemented FIX session encryption using STunnel, TT provides a TTFIX.crt file with the public certificates used by the TT platform FIX endpoint.&nbsp;<\/p>\n\n\n\n<p>On October 5, 2020, TT updated the <strong>stunnel.zip<\/strong> file located in the <a href=\"https:\/\/download.tradingtechnologies.com\/File\/Detail\/28739\">Download Center<\/a> in order to update the soon-to-be-expired certs from the TTFIX.crt bundle. <strong><em>All customers who use STunnel will need to download a new zip file and apply it by December 11, 2020.<\/em><\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Added TT platform STAR.TRADE.TT expiry September 20, 2021 (DC)<\/li><\/ul>\n\n\n\n<p><em>Additional Resources<\/em><em><br><\/em><a href=\"https:\/\/download.tradingtechnologies.com\/File\/Detail\/28739\">Stunnel.zip file<br><\/a><a href=\"https:\/\/library.tradingtechnologies.com\/tt-fix\/Managing_FIX_Sessions.html\">Directions for configuring stunnel with TTFIX.crt<\/a>&nbsp;<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"hkex-new-product-additions-%e2%80%93-msci-asia-and-emerging-market-index-futures-and-options\"><\/span><strong>HKEX: New Product Additions &#8211; MSCI Asia and Emerging Market Index Futures and Options&nbsp;<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>Q4<\/strong><\/h5>\n\n\n\n<p>HKEX continues to add MSCI Asia and Emerging Market Index futures and options. Remaining products to be launched are listed below. Launch dates will be provided when finalized by the exchange.<\/p>\n\n\n\n<p><strong>X_TRADER Platform Impact<\/strong><strong><br><\/strong>The<strong> <\/strong>Pmerge file will be added in a future update.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Launch Date<\/strong><\/td><td><strong>Contract<\/strong><\/td><td><strong>Product Code<\/strong><\/td><td><strong>Point Value<\/strong><\/td><\/tr><tr><td>Q4<\/td><td>MSCI Taiwan (USD) Index Options<\/td><td>MTW<\/td><td>100<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p><strong>TT Platform Impact<\/strong><strong><br><\/strong>No action is required; products will be available automatically.<\/p>\n\n\n\n<p><em>Additional Resources<br><\/em><a href=\"https:\/\/www.hkex.com.hk\/-\/media\/HKEX-Market\/Services\/Circulars-and-Notices\/Participant-and-Members-Circulars\/HKFE\/2020\/MKS_EQD_07_20_e.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">Exchange Notice, June 1, 2020<\/a><\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"fia-execution-source-code-schema-initiative-tag-1031\"><\/span><strong>FIA: Execution Source Code Schema Initiative (Tag 1031)&nbsp;<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<h5 class=\"wp-block-heading\"><strong>Timeline varies by exchange<\/strong><\/h5>\n\n\n\n<p>Multiple exchanges, in cooperation with the FIA Execution Source Code Schema Initiative, are moving forward with plans to implement FIX tag 1031 (CustOrderHandlingInst) on their APIs.<\/p>\n\n\n\n<p><em>Exchange-Specific Plans<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>CME: <\/strong>Tag 1031 is supported and is mandatory.<\/li><li><strong>ICE: <\/strong>Tag 1031 is supported, but not required.&nbsp;<\/li><li><strong>Eurex: <\/strong>Tag 1031 is supported, but not required.&nbsp;<\/li><li><strong>CurveGlobal\/IDEM<\/strong>: Tag 1031 is supported with the SOLA 14 Upgrade on February 3, but is not required.<\/li><\/ul>\n\n\n\n<p><strong>X_TRADER Platform Impact<\/strong><strong><br><\/strong>For CME, tag 1031 is now available in production. Customers should enter a valid value in the FFT6 field in Customer Defaults and\/or FIX Account Defaults. For FIX Order Routing applications, FFT6 maps to tag 16903. If no value is set, a default value of \u201cY\u201d will be sent. CME Gateway 7.18.49 was released on October 18.&nbsp;<\/p>\n\n\n\n<p>For ICE, tag 1031 is now available with ICE Gateway 7.18.29. Customers should use FFT6 to send the value to the exchange. The field is optional for ICE.<\/p>\n\n\n\n<p><strong>TT Platform Impact<\/strong><strong><br><\/strong>For CME, tag 1031 is now available for use in Production. Customers should select a valid value in Setup or set Order Tag Defaults.&nbsp;<\/p>\n\n\n\n<p>For ICE, tag 1031 is now available for use in Production. Customers should select a valid value in Setup or set Order Tag Defaults to send the value to the exchange. Customers can choose not to select any value as this is an optional field for ICE.<\/p>\n\n\n\n<p>For Eurex, support of tag 1031 on the TT platform is now available. Customers should select a valid value in Setup or set Order Tag Defaults to send the value to the exchange. Customers can choose not to select any value as this is an optional field for Eurex. On the X_TRADER platform, tag 1031 is not currently supported.<\/p>\n\n\n\n<p>For CurveGlobal and IDEM, support for tag 1031 was added on February 3 for both exchanges.<\/p>\n\n\n\n<p><em>Additional Resources<\/em><br><a href=\"https:\/\/www.fia.org\/sites\/default\/files\/2019-05\/FIA-Indirect-Clearing-Infosheet.pdf\" target=\"_blank\" rel=\"noreferrer noopener\">FIA Indirect Clearing Documentation<\/a><\/p>\n\n\n\n<p><strong>PRODUCT RELEASES<\/strong><br>No new products were released this week.<\/p>\n","protected":false},"author":6,"parent":0,"template":"","class_list":["post-90600","support","type-support","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/support\/90600","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/support"}],"about":[{"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/types\/support"}],"author":[{"embeddable":true,"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/users\/6"}],"version-history":[{"count":0,"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/support\/90600\/revisions"}],"wp:attachment":[{"href":"https:\/\/tradingtechnologies.com\/wp-json\/wp\/v2\/media?parent=90600"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}