pfm_init(3ncs) [ultrix man page]

pfm_init(3ncs)															    pfm_init(3ncs)

Name
       pfm_init - initialize the PFM package

Syntax
       #include <idl/c/base.h>
       #include <idl/c/pfm.h>

       void pfm_$init(flags)
       unsigned long flags;

Arguments
       flags

	      pfm_init_signal_handlers
		     Currently	the  only  valid flag value.  A flag's variable must be set to contain this value or the call will perform no ini-
		     tialization .  A call to pfm_init_signal_handlers causes C signals to be intercepted and converted to PFM signals.  On ULTRIX
		     and VMS systems, the signals intercepted are SIGINIT, SIGILL, SIGFPE, SIGTERM, SIGHUP, SIGQUIT, SIGTRAP, SIGBUS, SIGSEGV, and
		     SIGSYS.

Description
       The call to establishes a default set of signal handlers for the routine.  The call to should be made prior to the application's use of all
       other  runtime RPC routines. This enables the RPC runtime system to catch and report all fault and/or interrupt signals that may occur dur-
       ing normal operation.  Additionally, the user may provide a fault processing clean-up handler for application-specific exit handling.

Files
See Also
       intro(3ncs), pfm_cleanup(3ncs)

																    pfm_init(3ncs)

pfm_enable_faults(3ncs) 												   pfm_enable_faults(3ncs)

Name
       pfm_enable_faults - enable asynchronous faults

Syntax
       #include <idl/c/base.h>
       #include <idl/c/pfm.h>

       void pfm_$enable_faults()

Description
       The routine enables asynchronous faults after they have been inhibited by a call to causes the operating system to pass asynchronous faults
       on to the calling process.

       While faults are inhibited, the operating system holds at most one asynchronous fault.  Consequently, when returns, there can  be  at  most
       one  fault waiting on the process.  If more than one fault was received between routines to and the process receives the first asynchronous
       fault received while faults were inhibited.

Diagnostics
       This section lists the status codes for errors returned by this routine.

       pfm_$bad_rls_order  Attempted to release a clean-up handler out of order.

       pfm_$cleanup_not_found
			   There is no pending clean-up handler.

       pfm_$cleanup_set    A clean-up handler was established successfully.

       pfm_$cleanup_set_signalled
			   Attempted to use pfm_$cleanup_set as a signal.

       pfm_$invalid_cleanup_rec
			   Passed an invalid clean-up record to a routine.

       pfm_$no_space	   Cannot allocate storage for a clean-up handler.

Files
See Also
       intro(3ncs), pfm_enable(3ncs), pfm_inhibit_faults(3ncs)

															   pfm_enable_faults(3ncs)