Table of Contents
rmtUpDATA - remote - update a DATA record
rmtUpDATA posts
a DATA record update to
dbman. It does not wait for an answer.
There are
two versions of this function. One version updates and posts to the normal
que list. The other updates and posts to the fast que list.
The request is
passed in remote mode.
This function is part of librmt.
int rmtUpDATA(
/*
update a post to normal que list */
int fo,
int RecId,
unsigned int Value,
unsigned int status,
int verbosity
);
int rmtUpDATAF( /* update a post to fast que list */
int fo,
int RecId,
unsigned int Value,
unsigned int status,
int verbosity
);
The file descriptor for the connection to dbman.
DATA.RecId
The new value
DATA.DeviceStatus
Defines the amount of
messages to print. This value is passed on to SendRec. A value of 0 produces
no messages. See the SendRec manpage for full details on available values.
ERRok is returned if the transaction is successful.
The error code from the transaction is returned if there is a communications
error.
There are four functions in this family and knowing which one
to call can be difficult. It depends somewhat on the nature of the data
being processed by the I/O manager, the desired precision and the range
of the data.
For example, an A/D convertor returns an integer value. DATA.DTkey
is usually set to U or N in this case. Therefore, it makes sense to call
rmtUpDATA() or rmtUpDATAF().
A hall probe controller on the other hand returns
a string representing a floating point value (i.e 1.0000 T). DATA.DTkey is
usually set to F in this case. Therefore, it makes sense to call rmtUpDATAf()
or rmtUpDATAFf().
librmt(3rmt)
$Id: rmtUpDATA.3,v
1.2 2008/08/22 16:23:09 mcnamer Exp $
Table of Contents
NARA 5SDH-2
