dadOpenDB

f77:  Call dadOpenDB( Id, Name, Dataflow, Port, OpenFlags, err ) 
      integer Id, Port, OpenFlags, err
      character *(*)Name
      character *(*)Dataflow
  or
C:    int dadOpenDB( int *Id, char *Name, char *Dataflow, int Port,
		       int OpenFlags, int *err );      

• The variable Id returns a handle which will be used in later calls to the Dad library to specify the opened connection.
• The Name either contains the name of the host where the server is expected to be running or the name of a local UNIX socket filename.
• The Port contains the port number of the external host where the server is listening for clients or 0 in the case of a local connection.
• The Dataflow is the name of the dataflow that is expected to be served by the server.
• The Openflags specify the operation mode for the database access. You use a sum of
  • CAC_READ for reading a information from the server
  • CAC_WRITE for writing information to the server
  • CAC_UPDATE for the updating scheme
  • CAC_BOOK for booking new information (messages) on the server
  • CAC_GENTABLES if the metatable information on the server shall be used to generate the Adamo tables in the library while connecting to the server.
  • CAC_KEYTABLE for access to the keytable. Here the keytable may be read but only fields besides ID, cName, iTimeStart, iTimeEnd and LocalId may be changed by the client on the current record. Changes to the current keytable entry can only be made if the keytable contains the above mentioned update fields are part of the table. See examples on keytable manipulation.
  • CAC_NOSYNC No Time synchronization is done even if the system time of client and host differ.
  • CAC_KEEPEXEC Keep a file handle of the server connection also in exec'ed processes.
• The Err is set to 0 if the call was successfull or contains a Dad error number.