*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_address(3) -- retrieve the address attribute from a message
    The tt_message_address function retrieves the address attribute from the specified message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_address_set(3) -- set the address attribute for a message
    The tt_message_address_set function sets the address attribute for the specified message. The m argument is the opaque handle for the message involved in this operation. The a argument specifies which message attributes form the address to which the message will be delivered. The following values are defined: TT_HANDLER The message is addressed to a specific handler that can perform this operation...
 tt_message_args_count(3) -- return the number of arguments in the message
    The tt_message_args_count function returns the number of arguments in the message. The m argument is the opaque handle for the message involved in this operation.
 tt_message_arg_add(3) -- add a new argument to a message object
    The tt_message_arg_add function adds a new argument to a message object. The application must add all arguments before the message is sent. 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 s...
 tt_message_arg_bval(3) -- retrieve the byte-array value of a message argument
    The tt_message_arg_bval function retrieves the byte-array value of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be retrieved. The first argument is numbered zero. The value argument is the address of a character pointer to which the ToolTalk service is to point a string that contains the co...
 tt_message_arg_bval_set(3) -- set the byte-array value and type of a message argument
    The tt_message_arg_bval_set function sets the byte-array value and the type of the nth message argument. This function also changes the value of an existing nth message argument to a byte string. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to set. The first argument is numbered zero. The value argument is the byte str...
 tt_message_arg_ival(3) -- retrieve the integer value of a message argument
    The tt_message_arg_ival function retrieves the integer value of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be retrieved. The first argument is numbered zero. The value argument is a pointer to an integer where the ToolTalk service is to store the contents of the argument.
 tt_message_arg_ival_set(3) -- add an integer value in a message argument
    The tt_message_arg_ival_set function adds an integer value in the nth message argument. This function also changes the value of an existing nth message argument to an integer. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be set. The first argument is numbered zero. The value argument is the contents for the message ...
 tt_message_arg_mode(3) -- return the mode of a message argument
    The tt_message_arg_mode function returns the mode of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be returned. The first argument is numbered zero.
 tt_message_arg_type(3) -- retrieve the type of a message argument
    The tt_message_arg_type function retrieves the type of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be retrieved. The first argument is numbered zero.
 tt_message_arg_val(3) -- return a pointer to the value of a message argument
    The tt_message_arg_val function returns a pointer to the value of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be returned. The first argument is numbered zero.
 tt_message_arg_val_set(3) -- change the value of a message argument
    The tt_message_arg_val_set function changes the value of the nth message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be changed. The first argument is numbered zero. The value argument is the contents for the message argument.
 tt_message_arg_xval(3) -- retrieve and deserialize the data from a message argument
    The tt_message_arg_xval function retrieves and deserializes the data from a message argument. This function uses an XDR routine that is supplied by the client. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be returned. The first argument is numbered zero. The xdr_proc argument points to the XDR procedure to be used t...
 tt_message_arg_xval_set(3) -- serialize and set data into an existing message argument
    The tt_message_arg_xval_set function serializes and sets data into an existing message argument. The m argument is the opaque handle for the message involved in this operation. The n argument is the number of the argument to be changed. The first argument is numbered zero. The xdr_proc argument causes tt_message_arg_xval_set to serialize the data pointed to by value and store it as a byte string v...
 tt_message_barg_add(3) -- add an argument to a pattern
    The tt_message_barg_add function adds an argument to a pattern that may have a byte-array value that contains embedded nulls. 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 (...
<<  [Prev]  122  123  124  125  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  [Next]  >>
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service