{"id":91406,"date":"2021-03-12T15:25:50","date_gmt":"2021-03-12T21:25:50","guid":{"rendered":"https:\/\/tradingtechno3.wpenginepowered.com\/?post_type=support&p=91406"},"modified":"2021-03-12T15:40:16","modified_gmt":"2021-03-12T21:40:16","slug":"cme-mandatory-ilink-3-binary-order-entry-protocol-for-msgw-sgx-new-product-additions-and-more","status":"publish","type":"support","link":"https:\/\/tradingtechnologies.com\/support-updates\/cme-mandatory-ilink-3-binary-order-entry-protocol-for-msgw-sgx-new-product-additions-and-more\/","title":{"rendered":"CME Mandatory iLink 3 Binary Order Entry Protocol for MSGW, SGX New Product Additions and More"},"content":{"rendered":"\n

<\/span>CME: Mandatory iLink 3 Binary Order Entry Protocol for MSGW <\/strong><\/span><\/h4>\n\n\n\n

iLink 3 is now supported in Production. Please contact your Onboarding Manager when you are ready to migrate. All GTC\/GTDs should be cancelled prior to migrating to iLink3.<\/p>\n\n\n\n\n\n\n\n

iLink 2 and iLink 3 for MSGW will run in parallel until February 26, and at that time will incur <\/em><\/strong>additional charges by CME<\/em><\/strong> for continued iLink2 connections<\/em><\/strong>. On March 28, iLink 2.0 for MSGW will be decommissioned. <\/p>\n\n\n\n

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. All GTC\/GTDs should be cancelled prior to migrating to iLink3.<\/p>\n\n\n\n

Customers who wish to utilize CME\u2019s Self Match Prevention functionality should associate their existing SMP IDs to their account, or create a new SMP ID.<\/p>\n\n\n\n

X_TRADER\u00ae Platform Impact<\/strong>
<\/strong>X_TRADER will not support iLink 3.0.<\/p>\n\n\n\n

TT\u00ae Platform Impact<\/strong>
<\/strong>TT now supports iLink 3.0 in UAT and Production.<\/p>\n\n\n\n

<\/span>SGX: New Product Additions – SGX FTSE China Free H50 Index Options <\/strong><\/span><\/h4>\n\n\n\n
March 15<\/strong><\/h5>\n\n\n\n

SGX is introducing the below contracts for the trade date of Monday, March 15. Additional SGX FTSE China Free H50 Index Futures contracts will also be added.<\/p>\n\n\n\n

X_TRADER Impact<\/strong>
To trade this product, apply an updated pMerge file to all SGX Gateways:<\/p>\n\n\n\n

  1. Copy the SGX.pmg file to <drive letter>:\\tt\\config.<\/li>
  2. Stop GuardServer.<\/li>
  3. Navigate to <drive letter>:\\tt\\bin.<\/li>
  4. Double-click pMerge.exe. The Enter Exchange Name window appears.<\/li>
  5. Specify the exchange name and flavor and click OK. The Open Guardian product table merge file window appears.<\/li>
  6. Navigate to <drive letter>:\\tt\\config and select the SGX.pmg file. pMerge will update the existing Guardian Product Table with the correct values. After pMerge completes its tasks, the pMerge status bar displays Finished.<\/li>
  7. Close the pMerge status bar.<\/li>
  8. Start GuardServer.<\/li><\/ol>\n\n\n\n

    The above listed steps need to be repeated for each SGX Gateway<\/p>\n\n\n\n

    After pMerge runs, verify that the Guardian Product Table contains the following values:<\/p>\n\n\n\n

    Product Name<\/td>Product Symbol<\/td>Point Value<\/td><\/tr>
    SGX FTSE China Free H50 Index Options<\/td>FCH<\/td>2<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    TT Platform Impact<\/strong>
    No action required; products will be added automatically.<\/p>\n\n\n\n

    <\/span>[UPDATED] Refinitiv: RIC Code Changes – Postponed Until March 28<\/em><\/strong><\/span><\/h4>\n\n\n\n
    March 28<\/strong><\/h5>\n\n\n\n

    Refinitiv will remove the prefix \u201c1\u201d from RIC codes for CME futures and spreads, effective March 28. With this change, Refinitiv will only support Composite (no prefix) RICs. <\/p>\n\n\n\n

    Examples<\/em><\/p>\n\n\n\n