84.4.4.4 STANDARD > DNF > BINARY

Export Scope
The DNF Binary export is very similar to the Imagine Binary export, but it has fewer parameters and the extension of the exported file is .DNF (YYYYMMDDddd.DNF).
Export Parameters
In order to use this export function, it is required to compile the following parameters:
Export tab

5064_Export_standard_dnf_binary_1

•Period: Indicate the interval of days to be exported, one file will be created for each day within the period.
•Alternative schedules: Here it will be possible to change the schedule to be exported, which by default is the real schedule, this by selecting one of the 10 alternative schedule managed by Etere.
Parameters tab

5065_Export_standard_dnf_binary_2

•Export path: In the parameters section, the export path needs to be specified.
•Export filename: Here it is possible to insert up to 4 numbers (e.g. the station reference) to be appended at the start of the exported filename, the rest of the filename will be made up of the date (i.e. yyyymmdd) and day (i.e. yyyymmdd) in question (e.g. 1234yyyymmdd.LST).
•Insert alternative schedule in the filename: In case an alternative schedule is exported, the filename will contain -as a suffix- the number related to the exported alternative schedule.
•Export for: It allows to define which code will be exported to detail the asset to which an event is related, available types are:
- Event code: It will be exported the code with which the event has been scheduled.
- Media code : It will be exported the code of the media file linked to the event. It is suggested, in order to avoid ambiguity, to have events with just one linked media.
•Warn if the tape is missing:  A warning message will be given if an asset code has no tape linked to it.
Errors tab
The errors tab will detail to the operator all issues encountered during the exporting process.
Launch the export
Once the export has been configured, it can be started just by pressing the <Export> button.