Dayfile.txt: Difference between revisions

684 bytes added ,  09:22, 17 December 2016
m
→‎How Cumulus uses the daily log: Add mention of SQL feature in MX
m (→‎How Cumulus uses the daily log: Added note about my use of parameter for daily command)
m (→‎How Cumulus uses the daily log: Add mention of SQL feature in MX)
Line 9: Line 9:
*Back ups of all the files mentioned here are copied to the 'cumulus\backup\daily' folder.
*Back ups of all the files mentioned here are copied to the 'cumulus\backup\daily' folder.
*There are no updates to dayfile.txt at any other times, but the contents of the file are read and processed for many of the display and edit menu options selected from the main Cumulus screen.
*There are no updates to dayfile.txt at any other times, but the contents of the file are read and processed for many of the display and edit menu options selected from the main Cumulus screen.
*The system routines that Cumulus uses to access dayfile.txt require exclusive use of that file, so if you have any other process trying to access that file at end of the (meteorological) day, or when a relevant option is selected from View or Edit menus, one or other may fail. You can use the '''Daily''' box in the bottom left of the ''Sites/Options'' frame within the ''Internet'' options screen from the '''Configuration''' menu to safely take a copy of 'dayfile.txt' after it is updated.  See Cumulus '''Help''' for information on using this feature, I add a redirection ">daily_batch.log" in the parameter box alongside so that any output from my "T:\Cumulus\daily_batch_all.cmd" in the main box is sent to a log file overwritten in each run; this enables me to see the reason for any failure.
 
== How you can use the daily log ==
*If you want to run scripts that use the daily log, it is best if you take a copy first, I take a copy that is put onto my web server by using the '''Daily''' box in the bottom left of the ''Sites/Options'' frame within the ''Internet'' options screen from the '''Configuration''' menu to safely take a copy of 'dayfile.txt' after it is updated.  See Cumulus '''Help''' for information on using this feature, I add a redirection ">daily_batch.log" in the parameter box alongside so that any output from my "T:\Cumulus\daily_batch_all.cmd" in the main box is sent to a log file overwritten in each run; this enables me to see the reason for any failure.  My Cumulus 1 batch command also runs PHP to create SQL to update a database table version of the log, but my database table version also contains some additional information from the daily backup '[[today.ini]]' log.
*The system routines that Cumulus uses to access dayfile.txt require exclusive use of that file, so if you have any other process trying to access that file at end of the (meteorological) day, or when a relevant option is selected from View or Edit menus, one or other may fail.
*You can find examples of code that uses the daily log elsewhere in this Wiki and on the support forum.
*Cumulus MX includes the ability to generate SQL to update a database table version of the log. Using that database table avoids any clash with the Cumulus MX update of the daily summary log.


== Viewing or Editing the daily log within Cumulus ==
== Viewing or Editing the daily log within Cumulus ==
5,838

edits