Server Failure (by Application Service)
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A1	APP01 Services include: APP01 Client Service Types include: APP01	- No CRITICAL INTERRUPTION considerations necessary. - IT Operations are only users. - No alternate nodes. - Live without functionality until server is reactivated and confirmed healthy. - Service requires FireDaemon setup.	- No CRITICAL INTERRUPTION considerations necessary. - IT Operations are only users. - No alternate nodes. - Live without functionality until server is reactivated and confirmed healthy. - Service requires FireDaemon setup.	- No CRITICAL INTERRUPTION considerations necessary. - IT Operations are only users. - No alternate nodes. - Live without functionality until server is reactivated and confirmed healthy. - Service requires FireDaemon setup.	- No CRITICAL INTERRUPTION considerations necessary. - IT Operations are only users. - No alternate nodes. - Live without functionality until server is reactivated and confirmed healthy. - Service requires FireDaemon setup.	- No CRITICAL INTERRUPTION considerations necessary. - IT Operations are only users. - No alternate nodes. - Live without functionality until server is reactivated and confirmed healthy. - Service requires FireDaemon setup.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A2	APP02 Services MAY include any of the following: APP01, Instrument/System Activity Reader, and related database loader. Service Types MAY include any  of the following: APP02, APP03 and APP04	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP01 users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP03, APP02, APP04	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP01 users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP03, APP02, APP04	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP01 users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP03, APP02, APP04	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP01 users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP03, APP02, APP04	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP01 users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP03, APP02, APP04
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A3	APP03 Services include: Apache Tomcat Services	- No CRITICAL INTERRUPTION considerations necessary. - Ask APP03users to access hot backup node, either in CH2 or NY4 data center until affected server is reactivated and confirmed healthy.	- No CRITICAL INTERRUPTION considerations necessary. - Ask APP03users to access hot backup node, either in CH2 or NY4 data center until affected server is reactivated and confirmed healthy.	- No CRITICAL INTERRUPTION considerations necessary. - Ask APP03users to access hot backup node, either in CH2 or NY4 data center until affected server is reactivated and confirmed healthy.	- No CRITICAL INTERRUPTION considerations necessary. - Ask APP03users to access hot backup node, either in CH2 or NY4 data center until affected server is reactivated and confirmed healthy.	- No CRITICAL INTERRUPTION considerations necessary. - Ask APP03users to access hot backup node, either in CH2 or NY4 data center until affected server is reactivated and confirmed healthy.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A4	APP04 Services include: APP04 and related database loaders Service Types include: APP04, APP05	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP04 client connections.  These files must be changed to allow APP04 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP04, APP05	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP04 client connections.  These files must be changed to allow APP04 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP04, APP05	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP04 client connections.  These files must be changed to allow APP04 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP04, APP05	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP04 client connections.  These files must be changed to allow APP04 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP04, APP05	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP04 client connections.  These files must be changed to allow APP04 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP04, APP05
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A5	APP05 Services MAY include any of the following: APP05, APP06, APP10, Nespr and related database loaders Service Types MAY include any of the following: APP05, APP06, APP07 and APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify  Management that  MESSAGEs may be manual. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of APP05 configurations when related APP05 APP06 or APP05 APP10 change hosts. These files must be changed to allow APP05-to-APP06 or APP05-to-APP10 connectivity. - Nespr is never failed over to another node.  We live without redundancy in these situations. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP06, APP10, APP05, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify  Management that  MESSAGEs may be manual. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of APP05 configurations when related APP05 APP06 or APP05 APP10 change hosts. These files must be changed to allow APP05-to-APP06 or APP05-to-APP10 connectivity. - Nespr is never failed over to another node.  We live without redundancy in these situations. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP06, APP10, APP05, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify  Management that  MESSAGEs may be manual. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of APP05 configurations when related APP05 APP06 or APP05 APP10 change hosts. These files must be changed to allow APP05-to-APP06 or APP05-to-APP10 connectivity. - Nespr is never failed over to another node.  We live without redundancy in these situations. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP06, APP10, APP05, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify  Management that  MESSAGEs may be manual. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of APP05 configurations when related APP05 APP06 or APP05 APP10 change hosts. These files must be changed to allow APP05-to-APP06 or APP05-to-APP10 connectivity. - Nespr is never failed over to another node.  We live without redundancy in these situations. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP06, APP10, APP05, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify  Management that  MESSAGEs may be manual. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of APP05 configurations when related APP05 APP06 or APP05 APP10 change hosts. These files must be changed to allow APP05-to-APP06 or APP05-to-APP10 connectivity. - Nespr is never failed over to another node.  We live without redundancy in these situations. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP06, APP10, APP05, APP09
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A6	APP06 Services MAY include any  of the following: Away Market Destination, APP04 Drop Copy, DAS (order sending firm), Drop Copy (for order sending firm), APP10 (order sending firm), Regulatory Drop Copy (for APP04 Users). Service Types MAY include any  of the following: APP06, APP07, APP06, APP08, APP10, APP09	- No CRITICAL INTERRUPTION considerations necessary. - Notify affected USERS. - Move all applications to DR nodes with cooperation of Technical Services and necessary NAT changes. - All hosts are pre-defined.  No configuration changes necessary. - All Fix Engine files need to be moved ahead of any service restarts. Restart order (as applicable by server): APP06, APP10, APP08, APP09, APP06, APP07 - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations necessary. - Notify affected USERS. - Move all applications to DR nodes with cooperation of Technical Services and necessary NAT changes. - All hosts are pre-defined.  No configuration changes necessary. - All Fix Engine files need to be moved ahead of any service restarts. Restart order (as applicable by server): APP06, APP10, APP08, APP09, APP06, APP07 - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations necessary. - Notify affected USERS. - Move all applications to DR nodes with cooperation of Technical Services and necessary NAT changes. - All hosts are pre-defined.  No configuration changes necessary. - All Fix Engine files need to be moved ahead of any service restarts. Restart order (as applicable by server): APP06, APP10, APP08, APP09, APP06, APP07 - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations necessary. - Notify affected USERS. - Move all applications to DR nodes with cooperation of Technical Services and necessary NAT changes. - All hosts are pre-defined.  No configuration changes necessary. - All Fix Engine files need to be moved ahead of any service restarts. Restart order (as applicable by server): APP06, APP10, APP08, APP09, APP06, APP07 - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations necessary. - Notify affected USERS. - Move all applications to DR nodes with cooperation of Technical Services and necessary NAT changes. - All hosts are pre-defined.  No configuration changes necessary. - All Fix Engine files need to be moved ahead of any service restarts. Restart order (as applicable by server): APP06, APP10, APP08, APP09, APP06, APP07 - Confirm all data accounted for around move.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A7	APP07 Services include: APP07 and all related database loaders. ServiceTypes include: APP07, APP08 and APP09	- No CRITICAL INTERRUPTION considerations necessary. - No  users. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - G requires linux server WAR file deployment. - Database loader files can be concatenated after end of day shutdown. Restart order: APP07, APP08, APP09.	- No CRITICAL INTERRUPTION considerations necessary. - No  users. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - G requires linux server WAR file deployment. - Database loader files can be concatenated after end of day shutdown. Restart order: APP07, APP08, APP09.	- No CRITICAL INTERRUPTION considerations necessary. - No  users. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - G requires linux server WAR file deployment. - Database loader files can be concatenated after end of day shutdown. Restart order: APP07, APP08, APP09.	- No CRITICAL INTERRUPTION considerations necessary. - No  users. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - G requires linux server WAR file deployment. - Database loader files can be concatenated after end of day shutdown. Restart order: APP07, APP08, APP09.	- No CRITICAL INTERRUPTION considerations necessary. - No  users. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - G requires linux server WAR file deployment. - Database loader files can be concatenated after end of day shutdown. Restart order: APP07, APP08, APP09.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A8	APP08 Services MAY include any  of the following: APP08 and/or APP09, APP10 ServiceTypes MAY include any  of the following: APP08, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify USERSthat APP09 is affected. - Notify APP04 Users that APP08 is affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP08 and APP09 client connections.  These files must be changed to allow APP08 and APP09 client connectivity. Restart order (as applicable by server): APP08, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify USERSthat APP09 is affected. - Notify APP04 Users that APP08 is affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP08 and APP09 client connections.  These files must be changed to allow APP08 and APP09 client connectivity. Restart order (as applicable by server): APP08, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify USERSthat APP09 is affected. - Notify APP04 Users that APP08 is affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP08 and APP09 client connections.  These files must be changed to allow APP08 and APP09 client connectivity. Restart order (as applicable by server): APP08, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify USERSthat APP09 is affected. - Notify APP04 Users that APP08 is affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP08 and APP09 client connections.  These files must be changed to allow APP08 and APP09 client connectivity. Restart order (as applicable by server): APP08, APP09	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify USERSthat APP09 is affected. - Notify APP04 Users that APP08 is affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP08 and APP09 client connections.  These files must be changed to allow APP08 and APP09 client connectivity. Restart order (as applicable by server): APP08, APP09
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A9	APP09 Services include: APP09, APP10, and related database loaders Service Types include: APP09, APP10 and APP11, APP12	- CRITICAL INTERRUPTION will occur automatically upon APP09 restarts; However, production stocks do not open for trading until 6am.  - Restart APP09s as soon as possible.  - Notify participants immediately if CRITICAL INTERRUPTION occurred. - Confirmation of systems integrity and deference to EXECUTIVE instructions are required before resuming trading, if trading was suspended. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP10, APP09, APP11, APP12 - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION will occur automatically upon APP09 restarts.   will be exposed until APP09 restarts if trading was not already halted at time of shutdown.  - Restart APP09s as soon as possible.  - Notify participants of CRITICAL INTERRUPTION immediately.  - Confirmation of systems integrity and deference to EXECUTIVE instructions are required before resuming trading. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP10, APP09, APP11, APP12 - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION will occur automatically upon APP09 restarts.   will be exposed until APP09 restarts if trading was not already halted at time of shutdown.  - Restart APP09s as soon as possible.  - Notify participants of CRITICAL INTERRUPTION immediately.  - Confirmation of systems integrity and deference to EXECUTIVE instructions are required before resuming trading. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP10, APP09, APP11, APP12 - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION will occur automatically upon APP09 restarts.   will be exposed until APP09 restarts if trading was not already halted at time of shutdown.  - Restart APP09s as soon as possible.  - Notify participants of CRITICAL INTERRUPTION immediately.  - Confirmation of systems integrity and deference to EXECUTIVE instructions are required before resuming trading. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP10, APP09, APP11, APP12 - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations necessary. - Only MESSAGE corrections from APP03community may be at risk, if they have not finished for the day. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts are pre-defined.  No configuration changes necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP10, APP09, APP11, APP12 - Confirm all data accounted for around move.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A10	APP10: APP10 (MESSAGING), Services include: SITE 1 MESSAGE Processor, SITE 1 MESSAGE Processor, SITE 2 MESSAGE Processor, SITE 2 MESSAGE Processor Service Types include: APP10, APP11, APP12, APP13	- No CRITICAL INTERRUPTION considerations are necessary unless redundant data is lost between two different servers. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. Restart order: APP10, APP12, APP11, APP13	- No CRITICAL INTERRUPTION considerations are necessary unless redundant data is lost between two different servers. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. Restart order: APP10, APP12, APP11, APP13	- No CRITICAL INTERRUPTION considerations are necessary unless redundant data is lost between two different servers. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. Restart order: APP10, APP12, APP11, APP13	- No CRITICAL INTERRUPTION considerations are necessary unless redundant data is lost between two different servers. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. Restart order: APP10, APP12, APP11, APP13	- No CRITICAL INTERRUPTION considerations are necessary unless redundant data is lost between two different servers. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. Restart order: APP10, APP12, APP11, APP13
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A11	APP11: APP11 ( for MESSAGING) Services include: Readers and Loaders for MESSAGING, MESSAGE Montage, MESSAGING Montage Service Types include: APP11, APP12, APP13, and APP14, APP15, APP16	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify Post Trading Technology that Market Data Loading is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP13, APP11, APP12, APP16, APP14, APP15	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify Post Trading Technology that Market Data Loading is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP13, APP11, APP12, APP16, APP14, APP15	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify Post Trading Technology that Market Data Loading is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP13, APP11, APP12, APP16, APP14, APP15	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify Post Trading Technology that Market Data Loading is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP13, APP11, APP12, APP16, APP14, APP15	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify Post Trading Technology that Market Data Loading is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined.  No configuration changes are necessary. - Database loader files can be concatenated after end of day shutdown. Restart order: APP13, APP11, APP12, APP16, APP14, APP15
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A12	APP12 (MESSAGING) Services MAY include any  of the following: MESSAGING, SITE PROCESSORS, SITE PROCESSORS and SITE PROCESSORS and all related database loaders. ServiceTypes MAY include any of the following: APP12, APP13, APP14, APP15, APP16, SITE PROCESSORS and APP17, APP18, APP19, APP20	- CRITICAL INTERRUPTION should only be considered if recovery goes past 6am.  CRITICAL INTERRUPTION decision requires EXECUTIVE deference. - Notify SITESs, APP16 and/or SITE PROCESSORSs affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined.  No configuration changes necessary. - APP16 and SITE PROCESSORS Fix Engine files need to be moved ahead of service restart. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP12, APP14, APP13, APP16, APP15, SITE PROCESSORS then database loaders. - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION should only be considered if recovery will take longer than 5 minutes.  CRITICAL INTERRUPTION decision requires EXECUTIVE deference. - Notify SITESs, APP16 and/or SITE PROCESSORSs affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined.  No configuration changes necessary. - APP16 and SITE PROCESSORS Fix Engine files need to be moved ahead of service restart. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP12, APP14, APP13, APP16, APP15, SITE PROCESSORS then database loaders. - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION should only be considered if recovery will take longer than 5 minutes.  CRITICAL INTERRUPTION decision requires EXECUTIVE deference. - Notify SITESs, APP16 and/or SITE PROCESSORSs affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined.  No configuration changes necessary. - APP16 and SITE PROCESSORS Fix Engine files need to be moved ahead of service restart. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP12, APP14, APP13, APP16, APP15, SITE PROCESSORS then database loaders. - Confirm all data accounted for around move.	- CRITICAL INTERRUPTION should only be considered if recovery will take longer than 5 minutes.  CRITICAL INTERRUPTION decision requires EXECUTIVE deference. - Notify SITESs, APP16 and/or SITE PROCESSORSs affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined.  No configuration changes necessary. - APP16 and SITE PROCESSORS Fix Engine files need to be moved ahead of service restart. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP12, APP14, APP13, APP16, APP15, SITE PROCESSORS then database loaders. - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify SITESs, APP16 and/or SITE PROCESSORSs affected. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and NAT addresses are pre-defined.  No configuration changes necessary. - APP16 and SITE PROCESSORS Fix Engine files need to be moved ahead of service restart. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP12, APP14, APP13, APP16, APP15, SITE PROCESSORS then database loaders. - Confirm all data accounted for around move.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A13	APP13 Services MAY include any  of the following: APP13, APP14, APP15, APP16, APP17 Service Types MAY include any  of the following: APP13, APP14, APP15, APP16, APP17, and APP18, APP19, APP20	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users that APP16 connectivity between APP04 and ME is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP13 client connections.  These files must be changed to allow APP13 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP14 (followed by confirmation of monitoring integrity), APP16, APP15, DCSR, APP13, then database loaders. - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users that APP16 connectivity between APP04 and ME is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP13 client connections.  These files must be changed to allow APP13 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP14 (followed by confirmation of monitoring integrity), APP16, APP15, DCSR, APP13, then database loaders. - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users that APP16 connectivity between APP04 and ME is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP13 client connections.  These files must be changed to allow APP13 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP14 (followed by confirmation of monitoring integrity), APP16, APP15, DCSR, APP13, then database loaders. - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users that APP16 connectivity between APP04 and ME is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP13 client connections.  These files must be changed to allow APP13 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP14 (followed by confirmation of monitoring integrity), APP16, APP15, DCSR, APP13, then database loaders. - Confirm all data accounted for around move.	- No CRITICAL INTERRUPTION considerations are necessary.  - Notify APP04 Users that APP16 connectivity between APP04 and ME is compromised. - Move all applications to alternate nodes. - If alternate nodes not available, move to DR nodes. - All hosts and host specific configurations are pre-defined, outside of JNLP requirements for APP13 client connections.  These files must be changed to allow APP13 client connectivity. - Database loader files can be concatenated after end of day shutdown. Restart order (as applicable by server): APP14 (followed by confirmation of monitoring integrity), APP16, APP15, DCSR, APP13, then database loaders. - Confirm all data accounted for around move.
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
A14	APP10 Services include: APP10 (FireDaemon) NOTE: There are two pairings of APP10s in each data center.  1) APP12 Data Store, storing data from ME, to APP13, to APP14, to APP12, and 2) FS Data Store, storing data from APP16 to ME, to APP10, to DCSR, to APP15	- No CRITICAL INTERRUPTION considerations necessary. - No alternate nodes. - Live without redundancy until server is reactivated and confirmed healthy. - Service requires FireDaemon setup. - Confirm APP10 failover occurred as expected and systems integrity of affected data.	- No CRITICAL INTERRUPTION considerations necessary. - No alternate nodes. - Live without redundancy until server is reactivated and confirmed healthy. - Service requires FireDaemon setup. - Confirm APP10 failover occurred as expected and systems integrity of affected data.	- No CRITICAL INTERRUPTION considerations necessary. - No alternate nodes. - Live without redundancy until server is reactivated and confirmed healthy. - Service requires FireDaemon setup. - Confirm APP10 failover occurred as expected and systems integrity of affected data.	- No CRITICAL INTERRUPTION considerations necessary. - No alternate nodes. - Live without redundancy until server is reactivated and confirmed healthy. - Service requires FireDaemon setup. - Confirm APP10 failover occurred as expected and systems integrity of affected data.	- No CRITICAL INTERRUPTION considerations necessary. - No alternate nodes. - Live without redundancy until server is reactivated and confirmed healthy. - Service requires FireDaemon setup. - Confirm APP10 failover occurred as expected and systems integrity of affected data.
	MESSAGEs from  to SITES
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
B1	cannot send MESSAGEs to the SITES due to connectivity issue to SITES	- Work to resolve issue by 6am.	- Contact SITES, zero MESSAGEs.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm the most recent affected MESSAGEs are sent to the SITES, and any residual APP14, APP12 andMESSAGING processing is accounted for.	- Contact SITES, zero MESSAGEs.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm the most recent affected MESSAGEs are sent to the SITES, and any residual APP14, APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm any residual APP14, APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm any residual APP14, APP12 andMESSAGING processing is accounted for.
B2	cannot send MESSAGEs to the SITES for reasons other than connectivity issues to SITES	- Work to resolve issue by 6am.	- Zero MESSAGEs if able.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm the most recent affected MESSAGEs are sent to the SITES, and any residual APP14, APP12 andMESSAGING processing is accounted for.	- Zero MESSAGEs if able.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm the most recent affected MESSAGEs are sent to the SITES, and any residual APP14, APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm any residual APP14, APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm any residual APP14, APP12 andMESSAGING processing is accounted for.
	MESSAGEs from  to SITES
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
C1	cannot send MESSAGEs to the SITES	- Work to resolve issue by 6am.	- If not resolved in 15 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm all MESSAGEs not reported during outage are resent to the SITES as "sold", and any residual APP12 andMESSAGING processing is accounted for.	- If not resolved in 15 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm all MESSAGEs not reported during outage are resent to the SITES as "sold", and any residual APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm all MESSAGEs not reported during outage are resent to the SITES as "sold", and any residual APP12 andMESSAGING processing is accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm all MESSAGEs not reported during outage are resent to the SITES as "sold", and any residual APP12 andMESSAGING processing is accounted for.
	Clearing Records from  to SITES
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
D1	cannot sendMESSAGING records to APP16 due to connectivity issue to APP16	- If not resolved by 5:45am, defer to EXECUTIVE on decision to suspend trading. - If trading is suspended, notify participants. - If scenario resolved, confirm allMESSAGING processing has been accounted for.	- If not resolved within 5 minutes, defer to EXECUTIVE on decision to suspend trading. - If trading is suspended, notify participants. - If scenario resolved, confirm allMESSAGING processing has been accounted for.	- If not resolved within 5 minutes, defer to EXECUTIVE on decision to suspend trading. - If trading is suspended, notify participants. - If scenario resolved, confirm allMESSAGING processing has been accounted for.	- If not resolved within 5 minutes, defer to EXECUTIVE on decision to suspend trading. - If trading is suspended, notify participants. - If scenario resolved, confirm allMESSAGING processing has been accounted for.	- Work to resolve issue in time forMESSAGING goodnight message. - If scenario resolved, confirm allMESSAGING processing has been accounted for.
	MESSAGEs from SITES to
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
E1	cannot process MESSAGEs from the SITES in APP09s	- Work to resolve issue by 6am.	- If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm market data is being processed in ME.	- If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants.  - If scenario resolved, confirm market data is being processed in ME.	- Work to resolve issue by 6am, the following trading day.	- Work to resolve issue by 6am, the following trading day.
	MESSAGEs from SITES to
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
F1	cannot process MESSAGEs from the SITES in APP09s	- Work to resolve issue by 6am.	- If not resolved in 5 minutes, manually open IPO issues as dictated by other Financial Market Data Vendor information.  - Enable Market IOC processing for affected symbols.  - If scenario resolved, confirm market data is being processed in ME.	- If not resolved in 5 minutes, manually open IPO issues as dictated by other Financial Market Data Vendor information.  - Enable Market IOC processing for affected symbols.  - If scenario resolved, confirm market data is being processed in ME.	- Work to resolve issue by 6am, the following trading day.	- Work to resolve issue by 6am, the following trading day.
	Order Processing between USERS and
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
G1	experiences firm specific issues where  cannot process orders, order cancels, order cancel-changes, or order executions between USERS and APP09s.	- If not resolved by 5am, notify affected firm and implement alternative connection, if possible.	- Notify affected firm, and implement alternative connection, if possible. - If resolved, confirm all inbound and outbound messages have been accounted for.	- Notify affected firm, and implement alternative connection, if possible. - If resolved, confirm all inbound and outbound messages have been accounted for.	- Notify affected firm, and implement alternative connection, if possible. - If resolved, confirm all inbound and outbound messages have been accounted for.	- Notify affected firm, and implement alternative connection, if possible. - If resolved, confirm all inbound and outbound messages have been accounted for.
G2	experiences APP09 specific issues where  cannot process orders, order cancels, order cancel-changes, or order executions between USERS and APP09s.	- Work to resolve issue by 6am.	- Notify affected USERS.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants. - If resolved, confirm all inbound and outbound messages for all affected USERS have been accounted for.	- Notify affected USERS.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants. - If resolved, confirm all inbound and outbound messages for all affected USERS have been accounted for.	- Notify affected USERS.  - If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  - If trading is suspended, notify participants. - If resolved, confirm all inbound and outbound messages for all affected USERS have been accounted for.	- Work to resolve issue in time forMESSAGING goodnight message.
	Claims Self Help Against Another Market Center
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
H1	recognizes another Market Center's issue with their MESSAGE and/or MESSAGING processing.	- Work with affected market center to confirm problem.  - If not resolved, exclude affected market center from  BBO calculations. - If resolved, include affected market center in  BBO calculations.	- Work with affected market center to confirm problem.  - If not resolved, exclude affected market center from  BBO calculations. - If resolved, include affected market center in  BBO calculations.	- Work with affected market center to confirm problem.  - If not resolved, exclude affected market center from  BBO calculations. - If resolved, include affected market center in  BBO calculations.	Not applicable.	Not applicable.
	Network Issues Compromise  Data Center Connectivity
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
I1	recognizes network issue compromising  Data Center connectivity.	- Work to resolve issue by 6am. If scenario resolved, confirm: - all system monitoring is available. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - after 5am, all APP05 testing is working without issue. - after 5:05am, all MESSAGEs being sent to SITES are current. - after 5:05am, all MESSAGEs being sent to SITES are current or marked "sold". - after 6am, confirmMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	- If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  If trading is suspended, notify participants.  If scenario resolved, confirm: - all system monitoring is available. - all APP05 testing is working without issue. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	- If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  If trading is suspended, notify participants.  If scenario resolved, confirm: - all system monitoring is available. - all APP05 testing is working without issue. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	- If not resolved in 5 minutes, defer to EXECUTIVE on decision to suspend trading in affected symbols.  If trading is suspended, notify participants.  If scenario resolved, confirm: - all system monitoring is available. - all APP05 testing is working without issue, until 3:30pm. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	- Work to resolve issue in time forMESSAGING goodnight message. If scenario resolved, confirm: - all system monitoring is available. - all database loading is up to date for application startups. - all APP04 testing is working without issue, until APP04 Users are done for the day. - all MESSAGEs being sent to SITES are current or marked "sold", until APP04 Users are done for the day. - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for, until APP04 Users are done for the day. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.
	Loses Data Center Database Access
Scenario ID	Scenario	12:00 AM - 6:00 AM	6:00AM - 8:30 AM	8:30 AM - 3:15 PM	3:15 pm - 4:00pm	4:00 pm - 12:00 AM
J1	recognizes loss of Database Access in one data center, and decision is made to run all applications using one data center's database only.	Work to redirect all necessary processing to healthy database as quickly as possible, by: - redirecting oracle TNS names and production server local environment variables to healthy data center. - stopping any database loading to unhealthy database. - stopping/restarting any java application, including APP04, APP13, APP08, APP09 and APP15. - restarting any stopped non-java application as necessary.	Work to redirect all necessary processing to healthy database as quickly as possible, by: - redirecting oracle TNS names and production server local environment variables to healthy data center. - stopping any database loading to unhealthy database. - stopping/restarting any java application, including APP04, APP13, APP08, APP09 and APP15. - restarting any stopped non-java application as necessary. - Suspension of trading will not be required unless ME requires restart.	Work to redirect all necessary processing to healthy database as quickly as possible, by: - redirecting oracle TNS names and production server local environment variables to healthy data center. - stopping any database loading to unhealthy database. - stopping/restarting any java application, including APP04, APP13, APP08, APP09 and APP15. - restarting any stopped non-java application as necessary. - Suspension of trading will not be required unless ME requires restart.	Work to redirect all necessary processing to healthy database as quickly as possible, by: - redirecting oracle TNS names and production server local environment variables to healthy data center. - stopping any database loading to unhealthy database. - stopping/restarting any java application, including APP04, APP13, APP08, APP09 and APP15. - restarting any stopped non-java application as necessary. - Suspension of trading will not be required unless ME requires restart.	Work to redirect all necessary processing to healthy database as quickly as possible, by: - redirecting oracle TNS names and production server local environment variables to healthy data center. - stopping any database loading to unhealthy database. - stopping/restarting any java application, including APP04, APP13, APP08, APP09 and APP15. - restarting any stopped non-java application as necessary.
		After database redirection is completed, confirm: - all system monitoring is available. - all database loading to healthy database is up to date for application startups. - all APP04 servers have been restarted using healthy database and testing is working without issue. - all administrative clients (APP13, APP08) have been restarted using healthy database and are working without issue. - after 3am, all MESSAGEs and MESSAGEs from SITES are processed by ME. - after 5am, all APP05 testing is working without issue. - after 5:05am, all MESSAGEs being sent to SITES are current. - after 5:05am, all MESSAGEs being sent to SITES are current or marked "sold". - after 5:05am, all firm connections are up. - after 6am, all APP16 connections are up. - confirm post-MESSAGE processing is readied for one data center processing.	If ME restart was involved and trading was suspended, defer to EXECUTIVE to resume trading in affected symbols.  If trading is suspended, notify participants.  After database redirection is complete, confirm: - all system monitoring is available. - all APP05 testing is working without issue. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	If ME restart was involved and trading was suspended, defer to EXECUTIVE to resume trading in affected symbols.  If trading is suspended, notify participants.  After database redirection is complete, confirm: - all system monitoring is available. - all APP05 testing is working without issue. - all database loading is up to date for application startups. - all APP04 testing is working without issue. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	If ME restart was involved and trading was suspended, defer to EXECUTIVE to resume trading in affected symbols.  If trading is suspended, notify participants.  After database redirection is complete, confirm: - all system monitoring is available. - all APP05 testing is working without issue, until 3:30pm. - all database loading is up to date for application startups. - all APP04 testing is working without issue, until APP04 Users are done for the day. - all MESSAGEs and MESSAGEs from SITES are processed by ME. - all MESSAGEs being sent to SITES are current or marked "sold". - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.	After database redirection is completed, confirm: - all system monitoring is available. - all database loading is up to date for application startups. - all APP04 testing is working without issue, until APP04 Users are done for the day. - all MESSAGEs being sent to SITES are current or marked "sold", until APP04 Users are done for the day. - all firm connections are up and all inbound and outbound messages for all USERS have been accounted for, until APP04 Users are done for the day. - all administrative clients (APP13, APP08) are working in healthy data center. - allMESSAGING records to APP16 are accounted for. - post-MESSAGE processing is readied for one data center processing.