- Introduction To X_TRADER®
- TT Login
- Workspace Management
- Control Panel Icon And Menu Descriptions
- Trading And The Market Explorer
Trading And The Market Window
- Introduction to the Market Window
- Order Pane
- Submitting an Order using the Order Pane
- Launching an OTA from the Order Pane
- Selecting an Order Gatewayor Broker in the Market Window
- Applying Routing Rules in the Market Window
- Confirming Your Order in the Market Window
- Customizing the Quantity Buttons
- Order Pane Field Descriptions
- Algo Order Pane Field Descriptions
- Order Pane Context Menu
- Market Grid in the Market Window
- Using the Instrument Explorer in the Market Grid
- Market Grid Pane Field Descriptions
- Generating an RTD Formula
- Highlighting in the Market Grid
- Viewing Price Trend Indicators in the Market Grid
- Viewing Live-Only Contracts
- Viewing your Estimated Position In Queue
- Cloning Contract Rows
- Trading Eurodollar Options
- Launching an Algo in the Market Grid
- Market Grid Context Menu
- Viewing Market Depth
- RFQ Overview
- RFQ MiFID II
- Calculating Implieds
- Calculating Implied Ins
- Calculating Implied Outs
- Calculating Implied Quantities
- Calculating Implieds From Implieds
- Implied Functionality by Market
- Setting Implieds
- Viewing Implieds
- Managing Links
- Keyboard Trading in the Market Window
Trading And MD Trader
- Introduction to MD Trader
- MD Trader Field Descriptions
- Using the Instrument Explorer in MD Trader
- MDTrader - Order Entry
- MD Trader - Order Management
- MD Trader and Managing Links
- MD Trader - Displaying Market Data
- MD Trader - Configuration
- Using the MD Trader Context Menu
- Keyboard Trading in MD Trader
Orders And Fills Window
- Introduction to the Orders and Fills Window
- Order Modification Pane
- Order Toolbar
- Orders Pane
- Performing Order Status Inquiries
- Deleting an Order
- Canceling and Replacing an Order
- Holding Orders
- Pausing Synthetic Orders
- Changing Trigger Price Orders
- Recognizing Orders in an Unknown State
- Modifying Running Algo Variables
- Launching an OMA
- Keyboard Functions
- Fills Pane
- Adding a Manual Fill
- Deleting a Manual Fill
- Confirming Fills
- Changing Fill Account Information
- Start of Day Fills
- Fills Alert Dialog Box
- Using the Fills Pane Context Menu
- Fills Pane Column Descriptions
- Summary Pane
- Displaying Profit and Loss
- Position and Summary Pane Grouping
- Using the Summary Pane Context Menu
- Summary Pane Column Descriptions
- Introduction to the Position Window
- Position Pane
- Displaying Profit and Loss in the Position Pane
- Position Pane Context Menu
- Calculating Profit and Loss
- Orders and Fills Pane Context Menu
- Understanding Credit and Margin
- Position Pane Grouping
- Position Pane Column Descriptions
- Orders and Fills Pane
- Order Status Inquiries
- Deleting an Order from the Position Window
- Confirming Fill Orders in the Position Window
- Holding Orders in the Position Window
- Pausing Synthetic Orders in the Position Window
- Recognizing Orders in the Unknown State
- Orders and Fills Pane Column Descriptions
- Keyboard Functions and the Position Window
- Order Passing
- Quote Board
- Depth Window
- Introduction to the Spread Matrix
- Launching the Spread Matrix
- Navigating the Spread Matrix
- Customizing the Spread Matrix
- Displaying the Butterfly-Condor Matrix
- Butterfly Condor Matrix Overview
- Trading with the Spread Matrix
- Spread Matrix Calculations
- Butterfly Matrix Calculations
- Spread Matrix Context Menu
- Creating Strategies
- Audit Trail
- Floating Windows Overview
- Floating Order Book Overview
- Using the Floating Order Book
- Managing Algos in the Floating Order Book
- Keyboard Trading in the Floating Order Book
- Floating Order Book Column Descriptions
- Floating Depth Window
- Floating Net Position Window
- Using Floating Order Entry
- Using Multiple Floating Order Entry Windows
- Trading with the Order Bar
- Launching via the Net Position Field
- Seeding the Floating Order Entry
- X_TRADER Order Types
- Cross Orders
- Triggered Orders
- Iceberg Orders
- If Touched
- Triggered If Touched Orders
- Triggered Stop Orders
- Limits on Market Orders
- Machine Gun
- Market On Auction (MOA)
- Market On Close (MOC)
- Market On Open (MOO)
- Minimum Volume
- Submitting a Mutual Offset Order
- On Behalf Of Orders
- Order Cancels Order
- Duration Orders
- Time Sliced Orders
- Timed Orders
- Trailing If Touched Orders
- Trailing Limit Orders
- Trailing Stop Orders
- Volume Duration
- Volume Sliced Orders
- Best Limit
- Managing Saved Orders
- Saved Orders MiFID II
- Synthetic Orders on X_TRADER
- Introduction to Staged Orders
- Staged Order Creation
- Entering Related Child Orders
- Staged Order Management
- Staged Order Ownership
- Permissions and Risk
- Staged Orders Properties
- Introduction to Wholesale Trading
- SupportedTypes of Wholesale Trades
- Wholesale Orders MiFID II
- BVMF Cross Trades
- CME Cross Trades
- Eurex Wholesale Trades
- GMEX Wholesale Trades
- HKEx Wholesale Trades
- ICE Wholesale Trades
- LSE Cross and Committed Trades
- MX Cross and Committed Trades
- MEFF Cross Trades
- NYSE Liffe Wholesale Trades
- NYSE Liffe U.S. Wholesale Trades
- OSE J-NET Trades
- SFE Block Trades
- SGX Trade Reporting: One Sided Trades
- TFX Block Trades
Automated Trading Windows
- Automated Trading Overview
- Introduction to the Algo Dashboard
- Deploying Algos
- Algo Order Management
- Sharing Algos in the Algo Explorer Pane
- Renaming Algos in the Algo Explorer Pane
- Deleting Algos in the Algo Explorer Pane
- Launching Algos in the Algo Variable Pane
- Updating Algos in the Algo Explorer Pane
- Setting Favorite Algos in the Algo Explorer Pane
- Managing Algo Templates
- Algo Behavior at Market Close
- Algo Behavior When the Algo SE Server is Restarted
- Algo Variable Pane
- Algo Explorer Pane
- Algo Orders Pane
- Algos Dialog Box
- Algo Dashboard Column Descriptions
- Algo Orders Pane Context Menu
- Algo Explorer Pane Context Menus
- Order Management
- Order Book
Parent Order Book
- Introduction to the Parent Order Book
- Parent Order Book Toolbar Field Descriptions
- Managing Autospreader Orders in the Parent Order Book
- Managing Staged Orders in the Parent Order Book
- Managing Synthetic Orders in the Parent Order Book
- Managing Algo Orders in the Parent Order Book
- Viewing Child Orders
- Parent Order Book Context Menus
- Algo Variable Pane in the Parent Order Book
- Introduction to the Fill Window
- Fill Window Fills Pane
- Fill Window Fills Pane Column Descriptions
- Fill Window Fills Pane Context Menu
- Fill Window and Start of Day Fills
- Managing Manual Fills in the Fill Window
- Changing Fill Account Information in the Fill Window
- Fill Window Position Pane
- Displaying Profit and Loss in the Fill Pane
- Fill Window Position Pane Column Descriptions
- Analytic Windows
- Alerts Manager
- Time And Sales
- Settings And Global Properties
- Introduction to the Customer Defaults
- Creating a Customer Defaults Profile
- Changing a Customer Defaults Profile
- Deleting a Customer Defaults Profile
- Setting Customer Defaults to Read-Only
- Sharing your Customer Defaults Profile
- Using the Customer List
- Customer Defaults for MiFID II
- Algo Defaults for MiFID II
- Customer Defaults Dialog Box Field Descriptions
- Order Defaults
- Risk Parameters
- Routing Rules
- Login Gateway
- Global Properties
- TT Minimizer
- Screen Configuration
- Customizing Fonts
- Filtering And Sorting Data
- Formatting Grids
- Resizing And Printing Windows
- Tabbed Windows
OSE J-NET Trades
You are viewing X_TRADER Version 7.17 and higher. For earlier versions, click here
You can use the Wholesale Order window to submit the following types of J-NET orders on OSE:
- J-Net One Sided: J-NET orders that are only posted to the Participant listed as the order’s counterparty. J-Net One-sided Orders are only executed after the counterparty submits a matching J-NET One-Sided order.
- J-Net Cross: J-NET orders where the bid-side Participant and
an ask-side Participant are set within the same order message (MO76).
Both sides of the order are then executed as a cross order.
Note: Currently, TT does not support J-NET combo trades.
How to Match a J-Net One-Sided Trade
J-NET One-sided Orders are only executed after both traders submit a matching J-NET One-Sided order. The exchange uses the following values to match J-NET One-Sided trades:
- Both orders must match the same series, price and quantity.
- The Trading Type field must match.
- One order must be set to Sell order while the matching order must be set to Buy.
- Both counterparty Participants have set the other Participant as its Counterparty.
How to Enter Cross Trades
You can use the Wholesale Order window to make cross trades on OSE when connected to a OSE Gateway Version 7.17 or higher. For entering cross trades on earlier gateway versions, refer to Cross Orders.
Users may enter cross trades as either a J-NET One-Sided trade which is matched to an order submitted by a counterparty or, as a standalone J-NET Cross trade where the user enters both sides of the trade.
To enter a J-NET One-Sided cross trade, select One Side in the Order Type pane and complete the fields as listed below. You must verify that the counterparty enters a matching J-NET One-Sided trade.
To enter both sides of a J-NET Cross trade, select Cross in the Order Type pane. When submitting a J-NET Cross trade, the user must populate the Buyer and Seller sides of the trade.
Submitting J-NET Trades
Prior to submitting a J-NET trade, you should know the Counterparty’s Participant Code and the trade purpose (e.g., Arbitrage, Combination, etc).
To submit a J-NET Trade:
- Open the product you wish to trade in a Market Grid window.
- In the Market Grid, right-click
the row containing the product and select Wholesale Orders from
the context menu.
Note: The Wholesale Orders options is grayed-out if:
- Your administrator has not enabled wholesale trades in TT User Setup.
- The product/exchange does not support wholesale trades.
- Select either One Sided in the Order Types pane or Cross if submitting a cross order with another participant. Also, set the quantity and price for the trade.
- In the Order Details section, complete the remaining
fields as listed below.
OSE J-NET Trades
A drop-down list of available Customers.
Only customers selected in the X_TRADER Customer Defaults window appear in the Customer field list.
This is an optional field.
When a customer selection is made, the Account Number field is populated with the customer’s account number.
Note: Any changes to customer defaults (e.g., select another customer) requires a relaunch of the Wholesale Order window to pick up the most recent changes.
User Account Number
You may optionally provide a user Account Number in this field. This value is forwarded to the exchange API in the ex_client_s field.
Note: The exchange does not allow the * and % characters to be used as part of the account number.
A1, A2, and A3:Client/Agent
P1, P2, and P3:House/Principal
G1: Client/Agent; Giveup
G2: House/Principle; Giveup
Sets the type of account the trade that will be used to submit the trade. This value is forwarded to the exchange API as part of exchange_info_s field.
Users may configure custom account code mappings for all trades, including One Sided trades, in the hostinfo.cfg file. The list at the right shows the default mapping for OSE Gateways 7.16 and higher.
If submitting a Giveup, the user must populate FFT3 with the Customer Identification Number.
Carrying Participant Code
Sets the five-digit Carrying Participant Code provided by the securities code committee.
This field is mandatory when submitting a Giveup order and is forwarded to the exchange API as part of ex_customer_s field.
Customer specific information
Sets the customer specific information. This field is optional and can be used for back office reconciliation.
This value, if present, is forwarded to the exchange API in the exchange_info_s field.
Customer Identification Number
Sets the Customer Identification Number.
This field is mandatory when submitting a Giveup order and forwarded to the exchange API as part of customer_info_s field.
Counterparty Participant Code
Sets the Counterparty Participant Code and is mandatory for all One Sided trades.
Exchange for Physical
Sets the intention of the trade. Refer to the exchange’s documentation on the requirements for reporting the trade purpose.
Note: Select Cross Trade to enter a J-NET One-Sided cross trade. This will require the counterparty to submit a matching trade.
To enter a J-NET Cross trade, select Cross in the Order Type pane and populate credentials for both the Buyer and Seller sides of the trade.
Sets the trading session which the order applies.
Select VWAP (volume-weighted average price) to apply the trade across both trading sessions.
- Once the fields are complete, press the Send button.