hpux man page for t_error

t_error(3)						     Library Functions Manual							t_error(3)

NAME
       t_error() - produce error message

SYNOPSIS
DESCRIPTION
       The function produces a language-dependent message on the standard error output which describes the last error encountered during a call to
       a transport function.  The argument string errmsg is a user-supplied error message that gives context to the error.

       The error message is written as follows:

	      First if errmsg is not a null pointer and the character pointed to be errmsg is not the null character, the  string  pointed  to	by
	      errmsg is written followed by a colon and a space.

	      Then  a  standard  error	message  string for the current error defined in is written.  If has a value different from [TSYSERR], the
	      standard error message string is followed by a newline character.  If, however, is equal to [TSYSERR], the string is followed by the
	      standard error message string for the current error defined in followed by a newline.

       The  language for error message strings written by is implementation-defined.  If it is in English, the error message string describing the
       value in is identical to the comments following the codes defined in The contents of the error message strings describing the value in  are
       the same as those returned by the function with an argument of

       To simplify variant formatting of messages, the array of message strings is provided; can be used as an index in this table to get the mes-
       sage string without the newline.  The variable is the largest message number provided for in the table.

       The error number, is only set when an error occurs and it is not cleared on successful calls.

   Valid States
       All - apart from

   Fork Safety
       is not fork-safe.

RETURN VALUE
       For XTI, upon completion, a value of 0 is returned.  TLI does not return a value.

ERRORS
       No errors are defined for the function.

EXAMPLES
       If a function fails on transport endpoint fd2 because a bad address was given, the following call might follow the failure:

       The diagnostic message to be printer would look like:

       where identifies the specific error that occurred, and tells the user which function failed on which transport endpoint.

FILES
       NLS message catalog for TLI

SEE ALSO
       thread_safety(5).

STANDARDS CONFORMANCE
																	t_error(3)