RDC Recovery (Regulatory Drop Copy Processes)

RDC Purpose:

RDC processes receive order and execution drop copies from Away Market Destination Firms and Vendors and send them to BPLX.

Use the following hyperlinks to jump to the desired section of RDC documentation:

RDC_Recovery_Considerations

RDC_NTM_Control_Commands

RDC_Troubleshooting_Table

RDC_Monitoring_Considerations

RDC Recovery Considerations:

Stopping/Restart Processes:

- Use NTM Control Utility - Service Control - Process Controller to stop/restart processes.

- When moving between nodes:

o ALTERNATE NODES are not defined for RDC services.

o DR NODES must be allocated un-natted nodes.

No node can support more than one natted address at the same time.

- When stopping/restarting RDC processes:

1) Notify the associated vendor or order management service firm and work in cooperation with them, as appropriate to situations.

2) Notify Tech Services if moving RDC processes to DR nodes and NAT addresses need to change to accommodate move.

3) Stop the RDC process.

4) If NOT moving RDC to new node, skip to step 5.

a) If moving the RDC to a new node, copy the day’s RDC FIX engine files to alternate node:

a) Copy: \chx\data\{RDC}\*.log, *.body, *.header, *.seqnums, *.session file created for the day to the alternate node.

b) Copy: \chx\data\{RDC}\Global.* file created for the day to the alternate node.

c) If the target folder does not exist on the new node, you must first either create the folder, or copy the entire folder.

d) If these files are not moved before the process restarts on the new node, there will be a chance of sequence number miscommunications between the order sending firm involved and CHX.

5) Start the RDC process.

6) Open the channel for the process affected and confirm order sending firm connects as expected.

RDC NTM Control Commands:

Open OSF Channel:

- Use NTM Control Utility – Service Control - RDC – Open OSF Channel to make OSF connection possible.

Close OSF Channel:

- Use NTM Control Utility – Service Control - RDC – Close OSF Channel to make OSF connection impossible.

Set Inbound Sequence Number:

- Use NTM Control Utility – Service Control - RDC – Set Inbound Sequence Number to set CHX Inbound Sequence Number.

Set Outbound Sequence Number:

- Use NTM Control Utility – Service Control - RDC – Set Outbound Sequence Number to set CHX Outbound Sequence Number.

Enable 29West Stats:

- Use NTM Control Utility – Service Control - RDC – Enable 29West Stats to start collection and display of LBM related stats.

Disable 29West Stats:

- Use NTM Control Utility – Service Control - RDC – Disable 29West Stats to stop collection and display of LBM related stats.

RDC Troubleshooting Table:

RDC Symptom	Impacts	Response
Firm disconnects or Logs out of session Evidenced by: - EMT message saying {firm} is disconnected and/or {firm} is logged out. - Stats monitor shows disconnected in status column. {Firm} will be further identified in EMT message by including “LocalFixId” and “RemoteFixID” as configured in RDCServices.xml file within the disconnect message.	IB is no longer able to receive drop copy related messages from Away Market Destination Vendor or Order Management Service.	1) Contact firm. 2) Work with firm and/or Technical Services as necessary to isolate cause of issues and resolve them. 3) Stop/Restarts of affected application service may help resolve the issue.

RDC Monitoring Considerations:

Stats Monitors: RDC App Connect Stats	To Start:	Key Indicators to Monitor:	Symptom:	Response:
Processes facilitate drop copy communications from Away Market Destinations and Brokerplex via RDC fix engine. Monitor shows connection status between CHX fix engines and Away Market Destinations as well as processing statistics.	PROD MENU: Firmswitch Monitoring Menu To Exit: Close Window	- Color of data in columns - Status, - OutMsgs, - InMsgs	Data is RED.		Process is either down or multicast data is not being received by monitor. 1) Check status of process 2) If process is up, call Technical Services.
			Status is Disconnected or Open		Firm is not connected. 1) Use NTM Control Utility RDC Service Controls to Open Channels. 2) Call Production Control if needed.
			InMsgs value is not relatively close to, or far greater than OutMsgs value. Generally, all messages (in and out) are heartbeats traded between sides with the exception of drop copies received from the firms.		We may not be processing as expected. 1) Check RDC FIX message files to confirm inbound messages match outbound messages. 2) Work with Brokers and RDC Firms if necessary.