High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DEFINE_TP
Chapter 3 383
DEFINE_TP
The DEFINE_TP verb provides information that SNAplus2 needs to
start a TP as a result of an incoming attach from a partner LU. This verb
can also be used to modify one or more fields on a previously defined TP.
The standard parameters for invoked TPs are defined in the invokable
TP information file (for more information, see the HP-UX SNAplus2
Administration Guide). DEFINE_TP is required only if you need to
specify additional parameters thatcannot be set in the file: to restrict the
TP to use particular options for conversation security, confirm
synchronization, or conversation type (mapped or basic), or to restrict the
number of instances of the TP that can be running at any time.
VCB Structure
typedef struct define_tp
{
AP_UINT16 opcode; /* verb operation code */
unsigned char reserv2; /* reserved */
unsigned char format; /* reserved */
AP_UINT16 primary_rc; /* primary return code */
AP_UINT32 secondary_rc; /* secondary return code */
unsigned char tp_name[64]; /* TP name */
TP_CHARS tp_chars; /* TP characteristics */
} DEFINE_TP;
typedef struct tp_chars
{
unsigned char description[32]; /* resource description */
unsigned char security_list_name[14]; /* security access list name */
unsigned char reserv1[2]; /* reserved */
unsigned char conv_type; /* conversation type */
unsigned char security_rqd; /* security support */
unsigned char sync_level; /* synchronisation level support */
unsigned char dynamic_load; /* dynamic load (AP_YES) */
unsigned char enabled; /* is the TP enabled? */
unsigned char pip_allowed; /* program initialization */
/* parameters supported */
unsigned char reserv3[9]; /* reserved */
AP_UINT16 tp_instance_limit; /* limit on currently active TP */
/* instances */