Configuring the Copp Clark schedule to import calendars

Important: Configuring Horizon: Copp Clark via Scheduler is now deprecated:

• If you are setting up Horizon: Copp Clark for the first time, we recommend following these instructions to configure Horizon: Copp Clark using the Integrations dashboard.
• If you currently use Scheduler to maintain Horizon: Copp Clark, please contact support for assistance on migrating to the Integrations dashboard.

 

Horizon: Copp Clark runs a schedule daily in your LUSID domain to provide you with the latest market holiday data.

• On Day 1, you must configure the schedule to import at least one calendar and then enable the schedule.
• Subsequently, you can reconfigure the schedule at any time to import different calendars.

Configuring the Copp Clark schedule arguments

 You can configure the schedule to:

• Import Copp Clark calendar types, such as Payment Systems, Financial Centers, Exchange Trading and Exchange Settlement.
• Import only a subset within these calendar types, or remove some of these calendar types or subsets.

To do this:

1. Sign in to the LUSID web app using the credentials of a LUSID administrator.
2. From the top left menu, select Jobs & Scheduling > Schedules:
   
3. In the Schedules page, select Menu on the Copp Clark schedule and then Edit:
   
4. Select Next on the Specify Job tab to reach the Arguments tab:
   

Here you can configure the arguments (using the table below as a guide) to determine which data is imported into your LUSID domain when the schedule next runs:

Calendar type	Argument name	Value	Imported calendar code
Currency FX Markets	--calendars	Currencies	<ISO>__C
	--accepted-currencies	ISO codes for required currencies e.g. AUD,GBP,USD
Payment Systems	--calendars	PaymentSystems	<ISO>__P
	--accepted-currencies	ISO codes for required payment systems e.g. AUD,GBP,USD
Financial Centers	--calendars	FinancialCentres	<LOCODE>__B
	--financial-centre-codes	LOCODE (default), FpML or FpML,LOCODE
	--accepted-financial-centres	LOCODEs and/or FpMLs for required countries/cities separated with /, -, _  or nothing, e.g. AU/SYD,GB-LON,USNYC,KR_SEL Note: Coverage for FpML is smaller than coverage for LOCODE. We recommend including LOCODE if you want to be sure all business centres are covered.
Exchange Trading	--calendars	ExchangeTrading	<ISOMIC>__T
	--accepted-exchanges	ISO Market Identifier Code for required exchanges e.g. XASX,XLON,XNYS,XSTU
Exchange Settlement	--calendars	ExchangeSettlement	<ISOMIC>__S
	--accepted-exchanges	ISO Market Identifier Code for required exchanges e.g. XASX,XLON,XNYS,XSTU

For example, we can set the --calendars argument to Currencies and --accepted-currencies to AUD,GBP,USD to request the schedule only imports data for the AUD, GBP and USD Currency FX Markets:

Note the following:

• You can specify multiple --calendars values by separating each value with a comma and no space, e.g. PaymentSystems,FinancialCentres,ExchangeTrading.
• Values for --accepted-…  should be comma-separated with no spaces and are case-insensitive.

Understanding calendar codes and which calendar type your data originates from

Some calendar types take in the same identifiers:

• Currencies and PaymentSystems both use ISO codes and could import two calendars with the same code, e.g. AUD
• ExchangeSettlement and ExchangeTrading both use ISO MICs and could import two calendars with the same code, e.g. XASX

To help you know exactly which calendar data you are using, each imported calendar code is qualified (that is, suffixed) with a letter that identifies which  --calendars type the data comes from. The qualifying letter for each calendar is:

Calendar type value	Code suffix	Example
Currencies	__C	AUD__C
PaymentSystems	__P	AUD__P
FinancialCentres	__B	AU/SYD__B
ExchangeTrading	__T	XASX__T
ExchangeSettlement	__S	XASX__S

We recommend using qualified calendars to avoid confusion with your dataset, but you can choose to import your market holiday data unqualified by configuring the following arguments:

• For Currencies calendars, set the --unqualified-iso-currency argument value to Currencies. This imports two of each calendar with codes <ISO>__C and <ISO>. 
• For PaymentSystems calendars, set the --unqualified-iso-currency argument value to PaymentSystems. This imports two of each calendar with codes <ISO>__P and <ISO>. 
• For FinancialCentres calendars, set the --unqualified-locode and/or --unqualified-fpml arguments to FinancialCentres. This imports two of each calendar with the codes <LOC/FPML>__B and <LOC/FPML>.
• For ExchangeTrading calendars, set the --unqualified-iso-mic argument value to ExchangeTrading. This imports two of each calendar with the codes <ISOMIC> and <ISOMIC>__T.
• For ExchangeSettlement calendars, set the --unqualified-iso-mic argument value to ExchangeSettlement. This imports two of each calendar with the codes <ISOMIC> and <ISOMIC>__S.

Troubleshooting a failed schedule

You can check the status and configuration of every schedule that has run by navigating to Jobs & Scheduling > History from the top left menu in the LUSID web app:

If you configure the Copp Clark schedule to import a large volume of data (e.g. all calendars from all calendar types), you may find the schedule fails with the following error message:

You can split the data import into multiple schedules, such as creating one schedule per calendar type, to alleviate this issue. To do this:

1. From the top left menu in the LUSID web app, navigate to Jobs & Scheduling > Jobs:
   
2. In the Jobs page, select the Menu icon on the Copp Clark job then select Create a schedule:
   
3. Specify a Scope, Code, Schedule name, and Description for your schedule:
   
4. You can then configure the Optional Arguments and Triggers as usual and click Save to create your new schedule.

If a schedule fails and the steps above do not resolve the issue, contact Technical Support.