Instructions

UM-0085-B09 DT80 Range User Manual Page 108
RG
URI Escape Characters
If any of the following characters are used within an FTP or email URI component (FTP user name, FTP password, FTP
folder or file name, email recipient, email subject or email body), after applying any replaceable parameter substitutions,
then they must be replaced with "escape sequences", as follows. This prevents them being confused with the characters
used to separate
the various parts of a URI.
Character
Replace with
&
%26
/
%2F
:
%3A
;
%3B
=
%3D
?
%3F
@
%40
Limits
Be aware of the following command length limits when crafting complex unload commands. These limits apply to the
resultant string after substituting any replaceable parameters:
Element
Max number of characters
Complete command line 1023
FTP credentials and host name, or email recipient(s)
255
FTP path and filename 255
Option list: priority, session, subject, body
511
Email subject
255
Email message body 255
Other Options
The final COPYD option is delete=. If this is set to Y then following a successful unload, the records just unloaded will
be deleted from the source DBD file.
In most cases there is no benefit in doing this, and it would also mean that for example the
start=new2 feature would
no longer work because the data will no longer be present on the logger.
This option may however be useful if you have a
NOV (no overwrite) store file, or if you want to create archive files
(possibly in response to events) where there is no overlap between successive archive files.
Option Conflicts
Certain combinations of COPYD options are invalid, and will result in a "parameter/option conflict" error message. In
particular:
If format=dbd then the step= option is not supported. All records in the specified time range will be
unloaded.
If format=dbd then dest=stream is not valid: DBD format data can only be output to a file (either local or
on an FTP server). If DBD format output is specified then the default value of
dest is B: rather than stream.
If
merge=n then dest=stream is invalid.
If
start=new or end=new (or new2) then the job= option is invalid: tracking of the last unloaded record is
only supported for the current job.
If delete=y then the start= option is invalid: data are always deleted from the start of the storefile