The IDFS data retrieval software has been bundled for distribution.
The compressed tar file IDFSDataAccess.tar.Z contains the source code
for the programming examples that are provided in the IDFS Programmers
Manual, along with the source code for the libraries that are utilized.
In order to compile the source code, the environment variable SDDAS_HOME
must be set.  If the SDDAS display system has been installed on the 
target machine, the tar file should be untarred under the SDDAS_HOME
directory.  If the SDDAS display system has not been installed on the
target machine, the SDDAS_HOME environment variable must be set to the
directory where the tar file has been untarred.  In either case, the
following steps must be executed to produce the executables for the
programming examples and to utilize the IDFS data retrieval routines.
In step one, directory refers to the full pathname for the location of
the software.  Step two basically turns off the need for a ranlib to be
performed on the individual libraries that are created.  If your system
requires that ranlib be performed after the library is updated/created,
set the environment variable RANLIB appropriately.  In addition, since
the "ar" archive library command is utilized, be sure to add the path
for this command (/usr/ccs/bin) to your PATH environment variable.

(1) setenv SDDAS_HOME directory

(2) setenv RANLIB ":"

(3) mkdir lib                   (if subdirectory does not already exist)

(4) mkdir bin                   (if subdirectory does not already exist)

(5) mkdir include               (if subdirectory does not already exist)

(6) uncompress IDFSDataAccess.tar.Z

(7) tar xvf IDFSDataAccess.tar

(8) rm IDFSDataAccess.tar

At this point, there should be fourteen directories, an Imakefile file and one 
Imake rules file (SDDAS.rules) which can be placed in the system wide Imake
config files location or one can set the IMAKEINCLUDE environment variable
(see imake (1)).  The installer should review and possibly modify the 
contents of this rules file (SDDAS.rules) to tailor the compilation of the 
source for the target machine.  This must be done prior to compilation of 
source code.

Twelve of the 14 directories contain source code for libraries that support 
the IDFS paradigm.  These twelve directories are (1) libant, (2) libdB, 
(3) libdbSQL, (4) libCfg, (5) libserver, (6) libPromote, (7) libVIDF,
(8) libbase_idfs, (9) libIDFSMath, (10) libIDFSFill, (11) libIDFSTensor,
and (12) libtrec_idfs.  The compilation of the code for all these libraries
can be achieved by performing the following sequence of commands:

(9) xmkmf

(10) make Makefiles

(11) make release

At this point, there should be twelve libraries in the lib subdirectory under 
the SDDAS_HOME base directory.  At this point, the example programs found in 
the IDFS Programmers Manual can be compiled, linked and run.  To do this, the 
following steps are to be executed:

(12) cd IDFS_EXAMPLES

(13) xmkmf

(14) make module_name

where module_name is replaced by either all_example, rtime_one, rtime_all,
pback_one or pback_all.  An executable by the same name will be generated.
Provided an IDFS database has been set up on the target machine, the programs
can be run to dump the contents of the specified data sources for the designated
time periods.