VOLUME 20 - BULLETIN #125
TO:
|
ALL CLEARING MEMBERS
|
FROM:
|
BUSINESS SYSTEMS GROUP
|
DATE:
|
April 26, 2000
|
SUBJECT:
|
Customer Network
|
In October 1999, the Clearing Corporation published Volume 19 – Bulletin #283 announcing the construction of a New Customer Network. The major goal of the new network is to enhance communications between the Clearing Corporation and its member firms. This will take place by utilizing the TREX record format with MQM TCP/IP communications technology and FTP (File Transfer Protocol). Currently, the Clearing Corporation offers MQM transmissions of matched trades and give-up transactions (GAPI) in the TREX record format. All new development in clearing will utilize the TREX format with MQM as the standard method of data communication. This will include SLEDS (please refer to Volume 20-Bulletin #72) and Eurex.
The Clearing Corporation plans to have all clearing members utilizing and benefiting from the new Customer Network by Friday, September 1, 2000. In order for a smooth transition to the new network, a phased approach has been adopted.
By Monday, June 12, 2000, firms will be switched to the New Customer Network for the following applications:
1. MQM trade submission using the TREX record format
2. TN3270 terminal emulation from PC's
3. IP network printing.
Dumb terminals that provide access to OTIS will no longer be supported. Firms will be required to use TN3270 emulation from a PC. Report distribution will be through the new network allowing firms the capability to print reports to any IP address printer on their network. Xerox printers leased from the Clearing Corporation will no longer be supported.
As a reminder, the new ACT system for one sided entry of EFP transactions will be implemented on June 12 (see Volume 20-Bulletin #109). RJE files for EFP trade data will not be supported. Firms will be required to receive MQM messages from Clearing to process EFP transactions in their bookkeeping system. As a back-up, the Clearing Corporation will offer an ‘end of day’ FTP of trade data in the TREX record format.
On Friday, September 1, 2000, the Clearing Corporation plans to be completely switched to the New Customer Network. Firms will be required to send and receive trade data in the TREX record format using MQM protocol. The Clearing Corporation will no longer support RJE data file transport. Data file transport will be converted to FTP
Volume20 - Bulletin #125 Page 2
protocol. The RJE files to be converted to FTP include Give up Duplication, Trade duplication, Large Trader, Open Interest, Related Accounts, SPAN, RISK, Settlement
Prices, Register Data, GAINS, and ATOM. Please see the attached, Firm Impact for RJE to FTP conversions, and Volume 20 - Bulletin #88 for detail on the New Customer Network test plan.
To ensure that your firm is ready for the new network, firms should complete the Member Firm Installation/Test Request form that was attached to Volume 20 - Bulletin #87 and return to BSG as soon as possible.
Should you have any questions, please call or e-mail one of the following Business Systems Analysts:
|
|
|
|
|
|
|
|
|
|
|
|
GiveUp Data
|
Firm RJE submits request for GiveUp data to BOTCC. The firm's GiveUp data is sent to the firm via RJE.
At month end, BOTCC executes GVUPXXXP jobs that send month end GiveUp data to firms via RJE.
|
BOTCC will support the use of the GiveUp API to receive and send GiveUp data through MQ Series.
If requested, firms can have BOTCC create an end of day GiveUp data file that can be retrieved via FTP. The Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) file: CHPD.TR.CBTXXX.GVUPOUT. |
Daily
|
6/1/2000
|
|
|
|
|
|
|
Trade Dupes
|
Firms enter requests APS, Project A or other trades duplication files via OTIS or RJE. The firm's data is sent via RJE.
|
BOTCC will support the use of the time feeds to send trade duplication through MQ Series.
|
Daily
|
6/1/2000
|
|
|
|
|
|
|
Load Clearing / Regulatory Data
|
Firm sends data to BOTCC via RJE. The input file containing Large Trader and Long Delivery Position records are processed. A load report, processing messages, and related account files are sent back to the firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm writes the records (FTP Put) to file named CHPD.TR.CBTXXX.LOADIN. BOTCC processes data and writes output to files named: CHPD.TR.CBTXXX.LOADRPT, CHPD.TR.CBTXXX.LOADMSG and CHPD.TR.CBTXXX.RELAOUT.
Firm connects to BOTCC and retrieves (FTP Get) files: CHPD.TR.CBTXXX.LOADRPT, CHPD.TR.CBTXXX.LOADMSG and CHPD.TR.CBTXXX.RELAOUT. |
On Request
Turnaround time is 10 minutes during regular processing hours. |
|
|
|
|
|
|
|
Load Open Interest
|
Firm sends data to BOTCC via RJE. The Open Interest data is processed. A Risk report and processing messages are sent back to the firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm writes the records (FTP Put) to file named CHPD.TR.CBTXXX.LINTIN. BOTCC processes data and writes output to files named: CHPD.TR.CBTXXX.LINTRPT and CHPD.TR.CBTXXX.LINTMSG.
Firm connects to BOTCC and retrieves (FTP Get) files: CHPD.TR.CBTXXX.LINTRPT and CHPD.TR.CBTXXX.LINTMSG. |
Daily
Turnaround time is 10 minutes during regular processing hours.
|
9/1/2000
|
|
|
|
|
|
|
Risk (SAFE/SPAN)
|
Firm sends data to BOTCC via RJE. The Risk data is processed. A report is sent back to the firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm writes the records (FTP Put) to file named CHPD.TR.CBTXXX.RISKIN.
BOTCC processes data and writes output to files named: CHPD.TR.CBTXXX.RISKRPT and CHPD.TR.CBTXXX.RISKMSG.
Firm connects to BOTCC an retrieves (FTP Get) files: CHPD.TR.CBTXXX.RISKRPT and CHPD.TR.CBTXXX.RISKMSG. |
Daily
Turnaround time is 15 minutes during regular processing hours.
|
9/1/2000
|
|
|
|
|
|
|
Register Data
|
Firms RJE requests for register data to BOTCC. The firm's register data is sent to the firm via RJE.
BOTCC also schedules the creation of register data files after final clearing processing has completed, approximately 9:00 PM. The register data files are sent to each firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) file: CHPD.TR.CBTXXX.REGDOUT.
|
Preliminary (5:30 PM CST).
Final (9:00 PM CST, 10:00 PM for early trade checking sessions). |
9/1/2000
|
|
|
|
|
|
|
Settlement Prices
|
BOTCC schedules the creation of settlement price data files at approximately 4:30 PM. The settlement price files are sent to each firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) files: CHPD.TR.UA.SETTFOUT (Futures) and CHPD.TR.UA.SETTOOUT (Options).
|
|
9/1/2000
|
|
|
|
|
|
|
GAINS Data
|
Firms submit request for GAINS files. The GAINS data is sent to the firms via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm connects to BOTCC and retrieves (FTP Get) the daily GAINS file: CHPD.TR.CBTXXX.GAINXOUT. |
|
9/1/2000
|
|
|
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm connects to BOTCC and retrieves (FTP Get) the preliminary month end GAINS file: CHPD.TR.CBTXXX.GAINYOUT.
|
|
9/1/2000
|
|
|
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm connects to BOTCC and retrieves (FTP Get) the final month end GAINS file: CHPD.TR.CBTXXX.GAINZOUT.
|
|
9/1/2000
|
|
|
|
|
|
|
SPAN Arrays - Preliminary
|
BOTCC schedules the creation of preliminary SPAN Arrays at approximately 2:30 PM. The SPAN Array files are sent to each firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) files: CHPD.TR.UA.SPNPPOUT (Packed Data) and CHPD.TR.UA.SPNUPOUT (Unpacked Data). |
|
9/1/2000
|
|
|
|
|
|
|
SPAN Arrays - Final (5:00 PM)
|
BOTCC schedules the creation of final SPAN Arrays at approximately 4:30 PM. The SPAN Array files are sent to each firm via RJE.
|
Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) files: CHPD.TR.UA.SPNPFOUT (Packed Data) and CHPD.TR.UA.SPNUFPOUT (Unpacked Data). |
|
9/1/2000
|
Note for ' CBTXXX' designation: 'XXX' Denotes Firm Number/Service Bureau(001, 020, etc…)
|
|
|
|
|
|
Printer
Friendly Version