Login Search
 
 
About Us Careers Contact Us Press Center
 
Login
Delivery Info
Open Interest Reports
Web OTIS Access
 
Bulletins
Clearing Member Info
Newsletters
Related Links
 
 
 
 
Clearing Corp Bulletins Printer Friendly Version Printer Friendly Version
VOLUME 20 - BULLETIN #174

TO:

ALL CLEARING MEMBERS

FROM:

BUSINESS SYSTEMS GROUP

DATE:

June 6, 2000

SUBJECT:

Customer Network Test Schedule

As previously announced in Volume 20 - Bulletin #125 the new customer network will be implemented on September 1, 2000. Firms are advised to set-up a test date as soon as possible. Communications testing and application testing are estimated to take one business week to complete provided that the appropriate firm support is available on the firm's scheduled test dates. The Clearing Corporation can support 3 firms testing per business day from 6:30 a.m. until 4:00 p.m.

The Clearing Corporation is in the process of reserving a test date and time for firms to test the new Customer Network. The first round of network testing is a connectivity test, to ensure that IP addresses and router configurations are in place. It is the Clearing Corporation's goal to complete a communications test of MQM, WEB access through the New Customer Network, TN3270 Emulation, and IP printing within a two-hour time frame. In order to achieve this goal, the Clearing Corporation is requesting firms have the appropriate staff on hand while testing with expertise in the following areas:

•Network

– Knowledge with the Firms LAN and its network

 

components, with the ability to configure and troubleshoot the firms network.

• Firewall

– Knowledge and experience to configure and troubleshoot

 

the firms firewall.

•MQM

– Knowledge and a good understanding of how MQM works, with the

 

ability to configure MQM queues and channels.

Firms are reminded that the Customer Network Member Firm Profile found in Volume 20 - Bulletin #87 must be completed and returned 3 days prior to the assigned test date. Once a successful communications test is accomplished, applications testing can begin. Please refer to Volume 20 – Bulletin # 154 for details regarding applications testing.

Firms not converted to the new customer network by September 1, 2000 will not be able to perform specific system functionality detailed in Volume 20 - Bulletin #166. Firms will also be charged a premium to be connected to the old SNA network after the implementation date.

Attached, please find a sample diagram of a member firms network connectivity. Also, attached please find a recent version of the RJE to FTP spreadsheet.

Should you have any questions, please call or e-mail one of the following Business Systems Analysts:

Jennifer Campbell

786-5739

jennifer.campbell@botcc.com

John Compall

786-5795

john.compall@botcc.com

Shawn Gebbia

786-5748

shawn.gebbia@botcc.com

Marc MacQuarrie

786-5732

marc.macquarrie@botcc.com

Beth Minnick

786-3804

beth.minnick@botcc.com

Matt Walsh

786-5731

matt.walsh@botcc.com

     

Thomas Andrews

Manager

thomas.andrews@botcc.com

Diane Schuering

Vice President

diane.schuering@botcc.com

     

Business Systems Group E-Mail Address

BSG@botcc.com

BOTCC Web Site

http://www.botcc.com

         

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.

For disaster recovery purposes, firms can have BOTCC create an end of day GiveUp data file in TREX format 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

9/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.

For disaster recovery purposes, firms can have BOTCC create an end of day GiveUp data file in TREX format 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.TRDUPOUT.

Daily

9/1/2000

         

Large Trader & Related Accounts Data

Firm sends data to BOTCC via RJE. The input file containing Large Trader and Related Account 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.LGTRIN. BOTCC processes data and writes output to files named: CHPD.TR.CBTXXX.LGTRRPT, CHPD.TR.CBTXXX.LGTRMSG and CHPD.TR.CBTXXX.RELAOUT.

Firm connects to BOTCC and retrieves (FTP Get) files: CHPD.TR.CBTXXX.LGTRRPT, CHPD.TR.CBTXXX.LGTRMSG and CHPD.TR.CBTXXX.RELAOUT.

On Request

Turnaround time is 10 minutes during regular processing hours.

9/1/2000

         
         

Long Delivery Position Data

Firm sends data to BOTCC via RJE. The input file containing Long Delivery Position records is processed. A load report and processing messages 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.DELVIN. BOTCC processes data and writes output to files named: CHPD.TR.CBTXXX.DELVRPT and CHPD.TR.CBTXXX.DELVMSG.

Firm connects to BOTCC and retrieves (FTP Get) files: CHPD.TR.CBTXXX.DELVRPT and CHPD.TR.CBTXXX.DELVMSG.

On Request

Turnaround time is 10 minutes during regular processing hours.

9/1/2000

         

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 finalclearing processing has completed, approximately 9:00 PM. The register data files are sent to each firm via RJE.

BOTCC creates the preliminary register data file at 5:30 PM and the final register data file at 9:00 PM each business day. 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.

BOTCC creates the futures and options settlement price files at 5:00 PM each business day. 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).

Daily (5:00 PM CST).

9/1/2000

         

GAINS Data

Firms submit request for GAINS files. The GAINS data is sent to the firms via RJE.

BOTCC creates the GAINS data file at 10:00 PM each business day. 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.

Daily (10:00 PM CST).

9/1/2000

   

BOTCC creates the preliminary month end GAINS data file at 10:00 PM. 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.

Monthly (10:00 PM CST).

9/1/2000

   

BOTCC creates the final month end GAINS data file at 10:00 PM. BOTCC creates the GAINS data file at 10:00 PM each business day. 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.

Monthly (10:00 PM CST).

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.

BOTCC creates the preliminary SPAN Arrays data file at 3:00 PM. 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).

Daily (3:00 PM CST).

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.

BOTCC creates the final SPAN Arrays data file at 5:00 PM. 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.SPNUFOUT (Unpacked Data).

Daily (5:00 PM CST).

9/1/2000

         

Broker Edit File

BOTCC schedules the creation of final Broker edit file at approximately 3:30 PM. The Broker edit file is sent to each firm via RJE.

BOTCC creates the final Broker edit file at 3:30 PM each business day. Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) file: CHPD.TR.UA.BROKOUT.

Daily (3:30 PM CST).

9/1/2000

         

Firm Summary File

BOTCC schedules the creation of final Firm Summary file at approximately 3:30 PM. The Firm Summary file is sent to each firm via RJE.

BOTCC creates the Firm Summary file at 3:30 PM each business day. Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) file: CHPD.TR.UA.FIRMSOUT.

Daily (3:30 PM CST).

9/1/2000

         

Delegate Fee File

Firms RJE requests for the Delegate Fee file to BOTCC. The Delegate Fee file is sent to the firm via RJE.

BOTCC creates the Delegate Fee at 3:30 PM each business day. Firm connects to BOTCC via FTP. Firm logs onto BOTCC using an id CBTXXX and the password. Firm retrieves (FTP Get) file: CHPD.TR.UA.DLGFEOUT.

Daily (3:30 PM CST).

9/1/2000

         

ATOM Data

BOTCC creates the ATOM file at month end and on the third business day. The ATOM file is sent to the firm via RJE.

BOTCC creates the ATOM data file at month end and on the third business day at 11:30 PM. 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.ATOMOUT.

Month End & Third Business Day (11:30 PM CST).

9/1/2000

         

Note for ' CBTXXX' designation: 'XXX' Denotes Firm Number/Service Bureau(001, 020, etc…)