UM-0085-B09
DT80 Range User Manual
Page 100
RG
Orphaned live store files should normally never occur, because the DT80 will refuse to load a job if logged data exists
that was generated by a different job with the same name. Note however that any archive files that may be lying around
are not checked, so if you change the contents of an existing job then its archive files will become orphans.
Orphan store files are ignored by
COPYD
, so if you wish to keep the data in them you will need to manually copy the files
using the
COPY
command, or retrieve them using an FTP client.
LISTD Options
The LISTD command supports a number of options which can be used to filter the results, so the report will only list
information for the data and alarm stores that you are interested in.
Job
By default,
LISTD
will show details for the currently loaded job only. If there is no currently active job and you just type
LISTD
then an error message will be returned.
To show details for all jobs present on the logger, use the
job=*
option. So continuing the previous example:
LISTD job=*
Job Sch Type Ov Lg Go Recs Capacity
======== === ========== == == == ======== ========
*SAMPLE A Data Live Y Y N 46 34952
*SAMPLE A Data Arc 38 38
*SAMPLE B Data Live Y Y N 23 52428 —
*SAMPLE B Alarm Live Y Y N 3 1455
*SAMPLE B Data Arc 19 19
*SAMPLE B Alarm Arc 2 2
CONFIG A Data Live 204 52428
CONFIG B Data Live 204 34952
First Last File
=================== =================== ===========================================
2010-03-01 09:54:23 2010-03-11 19:32:00 B:\JOBS\SAMPLE\A\DATA_A.DBD
2010-03-01 09:54:23 2010-03-04 18:50:55 B:\JOBS\SAMPLE\002_20100311T193043.DBD
2010-03-01 09:54:24 2010-03-11 19:32:00 B:\JOBS\SAMPLE\B\DATA_B.DBD
2010-03-01 09:54:40 2010-03-11 19:32:00 B:\JOBS\SAMPLE\B\DATA_B.DBD
2010-03-01 09:54:24 2010-03-04 18:50:55 B:\JOBS\SAMPLE\002_20100311T193043.DBD
2010-03-01 09:54:40 2010-03-01 09:54:48 B:\JOBS\SAMPLE\002_20100311T193043.DBD
2010-02-19 14:35:25 2010-02-21 00:10:25 B:\JOBS\CONFIG\A\DATA_A.DBD
2010-02-19 14:35:25 2010-02-21 00:10:25 B:\JOBS\CONFIG\B\DATA_B.DBD
The list is now longer because it contains details for another job that happens to be present on the logger, called
CONFIG
.
Notice also that the job
SAMPLE
is prefixed by an asterisk (
*
) to indicate that it is the currently active job. The
Ov
,
Lg
and
Go
columns are not shown for the
CONFIG
job, as they only have meaning for the currently active job.
You can also specify an explicit job name for this option, e.g.
LISTD job=config
Schedule
By default,
LISTD
returns details for all schedules. If you are only interested in a particular set of schedules then the
sched= option can be used. For example:
LISTD job=config sched=B
Job Sch Type Ov Lg Go Recs Capacity
======== === ========== == == == ======== ======== —
CONFIG B Data Live 204 34952
First Last File
=================== =================== ===========================================
2010-02-19 14:35:25 2010-02-21 00:10:25 B:\JOBS\CONFIG\B\DATA_B.DBD
The value for the
sched
option is actually a list of schedules to include, e.g.
LISTD sched=ABK
would include details for schedules A, B and K only.
Data and Alarms
By default,
LISTD
returns details for both data and alarm stores. You can restrict it to one or other of these store types
using the data= and alarms= options. These are both yes/no options so you can select just data, just alarms, or both
(selecting neither, i.e. data=N alarms=N, is generally not useful!)