dadInit
dadInit defines the connection parameters for further calls to
dadConnect. dadInit calls before
dadHost can be overwritten by definitions
from dadHost and a dadInit call after
dadHost can overwrite
dadHost definitions.
dadInit reads in a file named dadinit.cnf in either the
current directory ( ./ ) or in $DAD_LIB or in
$HERMES_LIB (in that order). The syntax of dadinit.cnf
looks like
# comments start with a # on the line
#
# -----------------------------------
hermes.desy.de INET 10600 calBC rw
hermes.desy.de INET 10605 online rwu
namely it consists of comments which start with an # sign and of
lines in the same syntax as the dadHost
call: The lines start with the
name argument which is either a filename or a hostname followed
by the connection type (see above) and the port number. Afterwards
the dataflow name and the connection flags are given. It is not
possible to give no connection flags! The following flags are
supported:
- r for CAC_READ
- u for CAC_UPDATE
- w for CAC_WRITE
- b for CAC_BOOK
- g for CAC_GENTABLES
- n for CAC_NDELAY
- k for CAC_KEYTABLE
- t for CAC_NOSYNC
f77: Call dadInit
or
C: int dadInit( void );
This page is maintained by Wolfgang Wander