APPGROUP01 Recovery (Binary – BLBD, BLFM, BLLM, BLOC, BLQM)

Binary APP12 Purpose:

APPGROUP01 read files created by associated applications, and load all messages into databases for historical reference.

Use the following hyperlinks to jump to the desired section of Binary APP12 documentation:

Binary_APP12_Recovery_Considerations

Binary_APP12_NTM_Control_Commands

Binary_APP12_Troubleshooting_Table

Binary_APP12_Monitoring_Considerations

Binary APP12 Recovery Considerations:

Stopping/Restart Processes:

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

- Use appropriate nodes for associated application only when moving between nodes. (See associated application sections for reference.)

- When stopping/restarting APPGROUP01 processes:

1) Stop the associated application that is responsible for writing to the affected APPGROUP01 file.

2) Confirm the APPGROUP01 has completed loading all data.

3) Stop the APPGROUP01.

4) If NOT moving the APPGROUP01 to a new node, skip to step 5.

a) APPGROUP01 files should only be moved if “pre-move” database loading cannot be completed without doing so.

b) If moving APPGROUP01 files:

Copy :\chx\data\*bin*.log and *bin*.pos files (created on day) for each APPGROUP01 process moving to alternate node.

5) Start the associated application that writes the APPGROUP01 file.

6) Start the APPGROUP01.

7) If APPGROUP01 moved to alternate nodes WITHOUT moving APPGROUP01 files, concatenate APPGROUP01 files:

a) These steps are only critical for End-Of-Day Post Trade Technology procedures that depend on the affected APPGROUP01 files existing on a given node, and including the entire day’s records. These steps can be left for the End-Of-Day, as long as they are completed prior to the End-Of-Day Post Trade Technology procedures that require them.

b) In Windows Explorer:

i) Go to server and folder where first set of APPGROUP01 files exist.

ii) Rename all *.log files involved (created on the day) from *.log to *A.log

iii) Copy second server versions of the all *.log files involved (created on the day) to original server and folder.

iv) Rename all newly copied files involved (created on the day) from *.log to *B.log

b) On original server, using DOS command prompt:

i) Go to folder where APPGROUP01 files exist.

ii) COPY *A.log + *B.log *.log

Binary APP12 NTM Control Commands:

See APPGROUP01 Reject Processing Documentation for NTM Control Commands utilized for this purpose.

APPGROUP01 Options:

- Use NTM Control Utility – Utilities – APPGROUP01 Options.

- User will see list of reject files to be processed, if there are any.

- For any reject files the user wishes to process, they highlight the file and then right-click and select Create New Reject File.

- Once a reject file has been processed, a reload file will be shown.

- For any reload file the user wishes to process, they highlight the file and then right-click and select Replay Reload File.

Binary APP12 Troubleshooting Table:

Binary APP12 Symptom	Impacts	Response
There are Database Loading Rejects Evidenced by: - Stats monitor shows non-zero values in reject column. - Oracle reject errors are seen in EMT.	Historical data will not be retained as expected, nor be available to applications that may need to act further against the data.	1) Use APPGROUP01 Reject Replay Procedures to examine reasons for rejects and replay data as appropriate.

Binary APP12 Monitoring Considerations:

Stats Monitors: APPGROUP01	To Start:	Key Indicators to Monitor:	Symptom:	Response:
Processes read data files and load the records into the databases. Monitor shows processing stats of each loader. DC= tradeon DE = etradeon HC = toss HE = etoss	PROD MENU: DB Loader Monitoring Menu To Exit: Close Window	- Color of data in columns - Rejects, - Percent Complete, - Records remaining, - Insert Rate, - Minutes to Finish	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.
			Reject File Size column shows positive value (non-zero).	Rejects have occurred. Process rejects per procedures.
			Percent Complete and Records Remaining columns showing non-zero values and not reducing as expected. Insert Rate is zero or lower than expected rate.	Process is either down or hung, or database is not responding. 1) Check status of process 2) If process is up, check CPU and memory utilization to see if process is hung. 3) If process is up and not hung, call Database Technologies.