TNS/E Native Application Conversion Guide

Converting Programs With Guardian API Calls
TNS/E Native Application Conversion Guide—529659-003
10-3
CHECKPOINT
These procedures include sigactioninit(), sigactionrestore(), and
sigactionsupplant() in C and SIGACTION_INIT_, SIGACTION_RESTORE_,
and SIGACTION_SUPPLANT_ in pTAL.
The HP signals extensions are provided as convenience tools that allow native
processes to catch signals corresponding to trap conditions in TNS processes. The HP
signals extensions provide shortcuts to the same base functions provided by the
standard signals API.
If you are concerned about conforming to the POSIX.1 standard and application
portability, use the standard functions. If you are mainly interested in the performance
gains of converting from TNS to native processes but want to focus on handling those
signals known as trap conditions in TNS processes, use the signals extensions.
For more information on writing signal handlers, see the Guardian Programmer’s
Guide .
CHECKPOINT
The CHECKPOINT procedure is called by a primary process to send information about
its current executing state to its backup process.
Native processes cannot call the CHECKPOINT procedure. Replace calls to the
CHECKPOINT procedure with calls to the CHECKPOINTX procedure. CHECKPOINTX
is the same as CHECKPOINT, except for an additional optional parameter to allow
checkpointing data in extended data segments.
Because of differences between TNS and TNS/E native stack architecture, additional
changes might be required. For details, see the CHECKPOINTX procedure in the
Guardian Procedure Calls Reference Manual .
CHECKPOINTMANY
The CHECKPOINTMANY procedure is called by a primary process to send information
about its current executing state to its backup process. The CHECKPOINTMANY
procedure is used in place of the CHECKPOINT procedure when more than 13 pieces
of information need to be sent.
Native processes cannot call the CHECKPOINTMANY procedure. Replace calls to the
CHECKPOINTMANY procedure with calls to the CHECKPOINTMANYX procedure.
CHECKPOINTMANYX is the same as CHECKPOINTMANY, except for an additional
optional parameter to allow checkpointing data in extended data segments.
Because of differences between the TNS and native stack architecture, additional
changes might be required. For details, see the CHECKPOINTMANYX procedure in
the Guardian Procedure Calls Reference Manual .