Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dat_evd_modify_cno(3dat) [opensolaris man page]

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

NAME
dat_evd_modify_cno - change the associated CNO for the Event Dispatcher SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_evd_modify_cno ( IN DAT_EVD_HANDLE evd_handle, IN DAT_CNO_HANDLE cno_handle ) PARAMETERS
evd_handle Handle for an instance of the Event Dispatcher. cno_handle Handle for a CNO. The value of DAT_NULL_HANDLE specifies no CNO. DESCRIPTION
The dat_evd_modify_cno() function changes the associated CNO for the Event Dispatcher. A Consumer can specify the value of DAT_HANDLE_NULL for cno_handle to associate not CNO with the Event Dispatcher instance. Upon completion of the dat_evd_modify_cno() operation, the passed IN new CNO is used for notification. During the operation, an event arrival can be delivered to the old or new CNO. If Notification is generated by EVD, it is delivered to the new or old CNO. If the EVD is enabled at the time dat_evd_modify_cno() is called, the Consumer must be prepared to collect a notification event on the EVD's old CNO as well as the new one. Checking immediately prior to calling dat_evd_modify_cno() is not adequate. A notification could have been generated after the prior check and before the completion of the change. The Consumer can avoid the risk of missed notifications either by temporarily disabling the EVD, or by checking the prior CNO after invok- ing this operation. The Consumer can disable EVD before a dat_evd_modify_cno() call and enable it afterwards. This ensures that any notifi- cations from the EVD are delivered to the new CNO only. If this function is used to disassociate a CNO from the EVD, events arriving on this EVD might cause waiters on that CNO to awaken after returning from this routine because of unblocking a CNO waiter already "in progress" at the time this routine is called. If this is the case, the events causing that unblocking are present on the EVD upon return from the dat_evd_modify_cno() call and can be dequeued at that time RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE Invalid DAT handle. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.11 16 Jul 2004 dat_evd_modify_cno(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.10 16 Jul 2004 dat_evd_set_unwaitable(3DAT)
Man Page