INGEST_SVC(1)
NAME
ingest_svc - ingest data into the DSDS
SYNOPSIS
Used in a pe map file as p=ingest
DESCRIPTION
ingest_svc is run in the pipeline to do various types of
ingest of data into the DSDS
DISCUSSION
* Strategy level module /home/soi/CM/src/pipe/ingest_svc_proc.c
*
* This ingests data from the given input wd into the given output wd.
* All ingested data will be owner and group writtable.
* If the map file specified DSDSOUT then the data is ingested into
* DSDS storage. Also, typically, the map file will have the archive
* flag set. If ingested into DSDS storage the group will be SOI.
* There are three types of ingestion according to the "type" given.
*
* type=tlm (default)
* Will assume that this is Lockheed telemetry and ingest only the
* tfr & tfd files.
* A new feature added 1/13/95 is that an index file will be made
* from the tfr file, giving the DPC locations in the tfr file.
* type=misc
* Will recursively ingest the entire input wd.
* type=file
* Will assume that the selector of each dataset is the file
* name(s) of that ds to ingest (sel:file1,file2). If the ds is
* just specified as a string, then it is the filename
* (in=/tmp/file1;/tmp/file2).
* Unlike the other types which have a one to one in to out
* relationship, for type=file you can have multiple in ds but only
* one out. This is used as a gather of many in files to a common
* output ds.
*
* match=string
* If type=misc, then will only ingest those files in the input wd
* that have "string" at the start of their name. This is typically
* used for hk data where string might be "6106", so only the files
* named for 1996 day 106 will be ingested. The last matching
* filename detected is returned in the return keylist as AUXINFO.
*
* links=follow
* The default is to not copy through links.
* Use this to follow links.
*
* nonrecursive=1
* Obsolete. All ingests are only recursive. Retained on call for
* compatibilty with old map files. Will have no operational effect.
*
* Another optional argument is "text" which will also ingest the
* file given. This is typically some README type file that you want
* as part of the ds.
*
* This will handle multiple input and output datasets
* (datacollections) but assumes that they are matched, i.e. in_0_wd
* goes to out_0_wd. Aborts if there are a different number of input
* and output datasets.
* The exception is for type=file which can only have one output ds.
SEE ALSO
pe (1)
AUTHOR
Jim Aloise
HISTORY
1999-11-04 SOI Version 4.4