dat_cno_wait(3dat) [sunos man page]

dat_cno_wait(3DAT)				     Direct Access Transport Library Functions					dat_cno_wait(3DAT)

NAME

       dat_cno_wait - wait for notification events

SYNOPSIS

       cc [ flag... ] file... -ldat [ library... ]
       #include <dat/udat.h>

       DAT_RETURN
	   dat_cno_wait (
	   IN	 DAT_CNO_HANDLE    cno_handle,
	   IN	 DAT_TIMEOUT	   timeout,
	   OUT	 DAT_EVD_HANDLE    *evd_handle
	   )

PARAMETERS

       cno_handle      Handle for an instance of CNO

       timeout	       The duration to wait for a notification. The value DAT_TIMEOUT_INFINITE can be used to wait indefinitely.

       evd_handle      Handle for an instance of EVD

DESCRIPTION

       The dat_cno_wait() function allows the Consumer to wait for notification events from a set of Event Dispatchers all from the same Interface
       Adapter. The Consumer blocks until notified or the timeout period expires.

       An Event Dispatcher that is disabled or in the "Waited" state does not deliver notifications. A uDAPL Consumer  waiting	directly  upon	an
       Event Dispatcher preempts the CNO.

       The consumer can optionally specify a timeout, after which it is unblocked even if there are no notification events. On a timeout, evd_han-
       dle is explicitly set to a null handle.

       The returned evd_handle is only a hint. Another Consumer can reap the Event before this Consumer can get around to checking the Event  Dis-
       patcher. Additionally, other Event Dispatchers feeding this CNO might have been notified. The Consumer is responsible for ensuring that all
       EVDs feeding this CNO are polled regardless of whether they are identified as the immediate cause of the CNO unblocking.

       All the waiters on the CNO, including the OS Wait Proxy Agent if it is associated with the CNO, are unblocked with the NULL handle  returns
       for an unblocking EVD evd_handle when the IA instance is destroyed or when all EVDs the CNO is associated with are freed.

RETURN VALUES

       DAT_SUCCESS	       The operation was successful.

       DAT_INVALID_HANDLE      The cno_handle parameter is invalid.

       DAT_QUEUE_EMPTY	       The operation timed out without a notification.

       DAT_INVALID_PARAMETER   One  of the parameters was invalid or out of range, a combination of parameters was invalid, or the timeout parame-
			       ter is invalid.

       DAT_INTERRUPTED_CALL    The operation was  interrupted by a signal.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard: uDAPL, 1.1, 1.2    |
       +-----------------------------+-----------------------------+
       |MT-Level		     |Safe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       libdat(3LIB), attributes(5)

SunOS 5.10							    16 Jul 2004 						dat_cno_wait(3DAT)

Check Out this Related Man Page

dat_evd_set_unwaitable(3DAT)			     Direct Access Transport Library Functions			      dat_evd_set_unwaitable(3DAT)

NAME

       dat_evd_set_unwaitable - transition the Event Dispatcher into an unwaitable state

SYNOPSIS

       cc [ flag... ] file... -ldat [ library... ]
       #include <dat/udat.h>

       DAT_RETURN
	   dat_evd_set_unwaitable(
	   IN	 DAT_EVD_HANDLE    evd_handle
	   )

PARAMETERS

       evd_handle    Handle for an instance of Event Dispatcher.

DESCRIPTION

       The  dat_evd_set_unwaitable()  transitions the Event Dispatcher into an unwaitable state. In this state, calls to dat_evd_wait(3DAT) return
       synchronously  with  a  DAT_INVALID_STATE  error,  and  threads	already  blocked  in  dat_evd_wait()  are  awakened  and  return  with	 a
       DAT_INVALID_STATE  error  without  any  further	action	by  the  Consumer.  The actual state of the Event Dispatcher is accessible through
       dat_evd_query(3DAT) and is DAT_EVD_UNWAITABLE after the return of this operation.

       This call does not affect a CNO associated with this EVD at all. Events arriving on the EVD after it is set unwaitable  still  trigger  the
       CNO  (if  appropriate), and can be retrieved with dat_evd_dequeue(3DAT). Because events can arrive normally on the EVD, the EVD might over-
       flow; the Consumer is expected to protect against this possibility.

RETURN VALUES

       DAT_SUCCESS	     The operation was successful.

       DAT_INVALID_HANDLE    The evd_handle parameter is invalid.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard: uDAPL, 1.1, 1.2    |
       +-----------------------------+-----------------------------+
       |MT-Level		     |Safe			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       dat_evd_clear_unwaitable(3DAT), dat_evd_dequeue(3DAT), dat_evd_query(3DAT), dat_evd_wait(3DAT), libdat(3LIB), attributes(5)

SunOS 5.11							    16 Jul 2004 				      dat_evd_set_unwaitable(3DAT)

Linux and UNIX Man Pages

dat_cno_wait(3dat) [sunos man page]

Check Out this Related Man Page