*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->HP-UX 11i man pages              
Title
Content
Arch
Section
 
 tt_message_sender_ptype(3) -- retrieve the sender ptype attribute from a message
    The tt_message_sender_ptype function retrieves the sender ptype attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_sender_ptype_set(3) -- set the sender ptype attribute for a message
    The tt_message_sender_ptype_set function sets the sender ptype attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The ptid argument is the type of process that is sending this message.
 tt_message_send_on_exit(3) -- set up a message to send upon unexpected exit
    The tt_message_send_on_exit function requests that the ToolTalk service send this message if the process exits unexpectedly. The message is sent to the ToolTalk service, which queues the message internally until either of two events occur: 1. The procid that sent the tt_message_send_on_exit message to the ToolTalk service calls tt_close(3). In this case, the queued message is deleted. 2. The conne...
 tt_message_session(3) -- retrieve the session attribute from a message
    The tt_message_session function retrieves the session attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_session_set(3) -- set the session attribute for a message
    The tt_message_session_set function sets the session attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The sessid argument is the identifier of the session in which the process is interested.
 tt_message_state(3) -- retrieve the state attribute from a message
    The tt_message_state function retrieves the state attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_status(3) -- retrieve the status attribute from a message
    The tt_message_status function retrieves the status attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_status_set(3) -- set the status attribute for a message
    The tt_message_status_set function sets the status attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The status argument is the status to be stored in this message.
 tt_message_status_string(3) -- retrieve the character string stored with the status attribute for a message
    The tt_message_status_string function retrieves the character string stored with the status attribute for the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_status_string_set(3) -- set a character string with the status attribute for a message
    The tt_message_status_string_set function sets status string of the specified message. The m argument is the opaque handle for the message involved in this operation. The status_str argument is the status string to be stored in this message.
 tt_message_uid(3) -- retrieve the user identifier attribute from a message
    The tt_message_uid function retrieves the user identifier attribute from the specified message. The ToolTalk service automatically sets the user identifier of a message with the user identifier of the process that created the message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_user(3) -- retrieve the user information associated with a message object
    The tt_message_user function retrieves the user information stored in data cells associated with the specified message object. The user data is part of the message object (that is, the storage buffer in the application); it is not a part of the actual message. The application can, therefore, only retrieve user information that the application placed in the message. The m argument is the opaque han...
 tt_message_user_set(3) -- stores user information associated with a message object
    The tt_message_user_set function stores user information in data cells associated with the specified message object. The user data is part of the message object (that is, the storage buffer in the application); it is not part of the actual message. Data stored by the sending process in user data cells is not seen by handlers and observers. The application can use arguments for data that needs to b...
 tt_message_xarg_add(3) -- add an argument with an XDR-interpreted value to a message object
    The tt_message_xarg_add function adds an argument with an XDRinterpreted value to a message object. To change existing argument values, the application must use only modes TT_OUT or TT_INOUT. Adding arguments when replying to a message produces undefined results. The m argument is the opaque handle for the message involved in this operation. The n argument specifies who (sender, handler, observers...
 tt_message_xcontext_set(3) -- set the XDR-interpreted byte-array value of a message's context
    The tt_message_xcontext_set function sets the XDR-interpreted bytearray value of a message's context. The m argument is the opaque handle for the message involved in this operation. The slotname argument describes the slotname in this message. The value argument is the byte string with the contents for the message argument. The xdr_proc argument points to the XDR procedure to be used to serialize...
<<  [Prev]  126  127  128  129  130  131  132  133  134  135  136  137  138  139  140  141  142  143  144  145  146  
147  148  149  150  151  152  153  154  155  156  157  158  159  160  161  162  163  164  165  166  [Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service