Common DFOS tools:
|dfos = Data Flow Operations System, the common tool set for DFO|
|make printable||new:||see also:|
|- this tool is depricated and replaced by dataLoader!
||autoDaily (uses dataclient for automatic downloads)|
|dfosCron (supports background header downloads with dataclient -t h )|
This is a historical tool which is not used anymore in DFOS, except for the header download of the last 24 hours. All other functions of this tool are provided by dataLoader and should not be used operationally. Check out here for a comparison between dataclient and dataLoader. Use the tool only for downloading the current headers.
This tool is designed to download fits headers from the last 24 hours (the ones not yet available from SAFIQ). It is used within autoDaily and calChecker. It has two parameters: -t[ype] and -d[ate]. Type is h[eader]. -d[ate] is the operational date in DFO format (e.g. 2009-07-30).
The tool connects to the archive database. It downloads the header files for the specified date into $DFO_HDR_DIR/<date>, as text files with extension .hdr. There is an option to have complete headers, or hdr files per extension. The tool also writes a list_hdr_<date> file into $DFO_MON_DIR. The header download is almost instantaneous.
Type dataclient -H for on-line help. There is an extended manpage here.
The typical call for headers is:
dataclient -t header -d 2009-07-30
Do not call the tool on the command line.
dataclient.cfg has a tool syntax which is aligned with fitsreport.cfg but differs from the dfos tools. It contains the following information:
|Section 1: general|
|Enable broken template shifting:||Y||a template is broken if, by application of the standard $DFO_OFFSET variable, some part of the file set is shifted to the next (or previous) date; if enabled, the otherwise broken template is completely shifted to day+1|
|Enable extension downloading:||N||if Y, headers come as one file per extension|
Upon installation, you have to run once the helper tool dataclientsetup which is also part of the delivery. You are prompted for your operational password which is then returned in encrypted form. Paste the returned line into your .dbrc file. This procedure needs to be repeated every time you change your password. It is required to permit the archive server access to your machine for the file delivery.
The tool comes with the standard DFS installation.
The tool logs onto the command line and into the dataclient.log. The log level is configurable (0 to 5). With v1.3, logging is done for the whole process, not file by file anymore.
dataclient in mode 'header' writes the status flag 'hdr_Exist' (or 'hdr_Notexist') into $DFO_MON_DIR/DFO_STATUS.
Headers downloaded by dataclient are not updated!