t_error(3)t_error(3)NAMEt_error() - produce error message
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 char‐
acter. If, however, is equal to [TSYSERR], the string is fol‐
lowed 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
message string without the newline. The variable is the largest mes‐
sage number provided for in the table.
The error number, is only set when an error occurs and it is not
cleared on successful calls.
All - apart from
is not fork-safe.
For XTI, upon completion, a value of 0 is returned. TLI does not
return a value.
No errors are defined for the function.
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.
NLS message catalog for TLI