Instructions

UM-0085-B09 DT80 Range User Manual Page 99
RG
Each row of the report describes a store. A store is a set of logged data or alarm records for a particular schedule. Each
store is contained within a store file (.DBD file). There can be multiple stores in the one store file.
There are two different types of store file: live (
Live) and archive (Arc).
 Live Store Files
Live store files are the files to which data and alarm records are written, as they are sampled. Each schedule (that has
loggable channels) has a live store file called DATA_s.DBD, which contains one data store and/or one alarm store. In
the above example, there are three live stores listed:
• schedule A's data store, which currently contains 46 logged data records out of a capacity of 34952
• schedule B's data store, which currently contains 23 logged data records
• schedule B's alarm store, which currently contains 3 logged alarm records
In this example schedule A does not have any alarms defined, so it does not have an alarm store in its live store file.
For each live store, the following information is listed:
•
Ov (Overwrite) column: indicates whether old records will be overwritten by new ones. (This is controlled by the
OV and NOV schedule options, see Schedule Options (P49))
• Lg (Log) column: indicates whether logging is currently enabled for this schedule. (This is controlled by the
LOGON and LOGOFF commands, see LOGON and LOGOFF Commands (P94))
•
Go column: indicates whether the schedule is currently running. (This is controlled by the G and H commands,
see Halting & Resuming Schedules (P59))
•
Recs column: current number of logged records
• Capacity column: maximum number of records that can be stored. (This is controlled by the DATA and
ALARMS schedule options, see Schedule Options (P49))
• First column: timestamp of the oldest logged record in the store
•
Last column: timestamp of the newest logged record in the store
•
File column: name of the store file that contains this store
 Archive Files
An archive file contains a "snapshot" of a live store file. Archive files have the same format (.DBD) as live store files,
except that all empty space is removed for each store.
Archive files are created by using the COPYD command to unload data from a live store file in .DBD format and save it to
a file. By default, archive files have an automatically generated file name which indicates the date and time at which they
were created.
An "archive file" is therefore really just an unload output file, as is a CSV file. The difference is that because it is still in
the logger's native .DBD format, the DT80 knows exactly what is in it – which schedules, channels, time ranges and so
on. Archive files will therefore appear in a LISTD report, whereas CSV format files will not. You can also selectively
unload data from an archive file the same as you would from a live store file.
In the sample LISTD output shown above, one archive file has been created, named 002_20100311T193043.DBD. The
name indicates that it was created on 11-Mar-2010 at 19:30:43. The file name does not indicate anything about the time
range covered by the records therein – this information is obtained from the LISTD report.
In this case the archive file contains three stores:
• a snapshot of schedule A's data store, which contains 38 data records
• a snapshot of schedule B's data store, which contains 19 data records
• a snapshot of schedule B's alarm store, which contains 2 alarm records
Notice that for an archive file, the number of records in each store is always equal to the capacity.
Also note that the Ov, Lg and Go columns are not applicable for archive files, as you cannot log new data to an archive
file.
 Orphans
You may occasionally see the word [orphan] displayed at the end of a row in a LISTD report. This indicates that the
job used to generate the data in the file is no longer present on the DT80. In other words, the store file has lost the
"parent" job that created it – hence the name.
For example:
B:\JOBS\WEST3\000_20100312T143919.DBD [orphan]
indicates that version of the
WEST3 job that created the data saved in this archive file no longer exists – it may have
been modified or deleted.