Using the ExtData/History tool: Difference between revisions

← Older edit Newer edit →

@@ Line 14: / Line 14: @@
 ::
 </pre>
+The CAP.rc for each cases is a little different than the normal cap and looks like so.
+<pre>
+ROOT_NAME: Root
+ROOT_CF: AGCM1.rc
+HIST_CF: HISTORY1.rc
+EXTDATA_CF: EXTDATA1.rc
+BEG_DATE:     20040101 210000
+JOB_SGMT:     00001200 000000
+HEARTBEAT_DT:   3600
+RUN_TIMES::
+20040115 210000
+20040215 210000
+20040315 210000
+20040415 210000
+20040515 210000
+20040615 210000
+20040715 210000
+20040815 210000
+20040915 210000
+20041015 210000
+20041115 210000
+20041215 210000
+::
+</pre>
+The CAP in the application will run a clokc from the BEG_DATE for the JOB_SGMT length at a HEARTBEAT_DT interval. ExtData, History, and the application component only run at the times listed in run time. This is a bit clunky but unfortunately History uses alarms which will only go off if a clock advances. This is very unfortunate as it adds confusion to the application.