rpc_svc_err(3N) 														   rpc_svc_err(3N)

NAME

       rpc_svc_err:  svcerr_auth(),  svcerr_decode(), svcerr_noproc(), svcerr_noprog(), svcerr_progvers(), svcerr_systemerr(), svcerr_weakauth() -
       library routines for server side remote procedure call errors

SYNOPSIS


DESCRIPTION

       These routines are part of the RPC library which allows C language programs to make procedure calls on other machines across the network.

       These routines can be called by the server side dispatch function if there is any error in the transaction with the client.

       The HP-UX implementation of RPC only supports the X/Open Transport Interface (XTI).  Applications that  are  written  using  the  Transport
       Layer Interface (TLI) and wish to use RPC, must convert their application to XTI.

   Routines
       See rpc(3N) for the definition of the data structure.

       Called by a service dispatch routine that refuses to perform
	      a remote procedure call due to an authentication error.

       Called by a service dispatch routine that cannot successfully
	      decode the remote parameters (see in rpc_svc_reg(3N)).

       Called by a service dispatch routine that does not implement
	      the procedure number that the caller requests.

       Called when the desired program is not registered with the
	      RPC package.  Service implementors usually do not need this routine.

       Called when the desired version of a program is not registered with
	      the  RPC package.  low_vers is the lowest version number, and high_vers is the highest version number.  Service implementors usually
	      do not need this routine.

       Called by a service dispatch routine when it detects a system
	      error not covered by any particular protocol.  For example, if a service can no longer allocate storage, it may call this routine.

       Called by a service dispatch routine that refuses to perform
	      a remote procedure call due to insufficient (but correct) authentication parameters.  The routine calls

MULTITHREAD USAGE

       Thread Safe:	     Yes
       Cancel Safe:	     Yes
       Fork Safe:	     No
       Async-cancel Safe:    No
       Async-signal Safe:    No

       These functions can be called safely in a multithreaded environment.  They may be cancellation points in that they call functions that  are
       cancel points.

       In a multithreaded environment, these functions are not safe to be called by a child process after and before These functions should not be
       called by a multithreaded application that supports asynchronous cancellation or asynchronous signals.

SEE ALSO

       rpc(3N), rpc_svc_calls(3N), rpc_svc_create(3N), rpc_svc_reg(3N).

																   rpc_svc_err(3N)