HP-UX SNAplus2 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Chapter 172
To delete local LUs, partner LUs, modes, or COSs when they are no
longer required, use the following verbs:
• DELETE_LOCAL_LU, DELETE_PARTNER_LU
• DELETE_MODE, DELETE_COS
SNAplus2 negotiates session limits with the partner LU automatically
when sessions are established. If you need to manage session limits
between a local LU and its partner LU explicitly, use the following verbs:
• INITIALIZE_SESSION_LIMIT, CHANGE_SESSION_LIMIT,
RESET_SESSION_LIMIT
To manage individual sessions, use the following verbs:
• QUERY_SESSION
• ACTIVATE_SESSION, DEACTIVATE_SESSION,
DEACTIVATE_CONV_GROUP
Normally you do not need to define SNAplus2 invokable TPs if they are
operator-started. If a TP is to be automatically started by SNAplus2
when a remote TP allocates a conversation to it, if it is to be
operator-started anda broadcast queued TP (which means that incoming
conversation requests can be routed dynamically to the TP wherever it is
running), or if it is to be operator-started and requires a specific
Receive_Allocate timeout value, you need to specify it in the SNAplus2
invokable TP data file. For more information about this file, refer to the
HP-UX SNAplus2 Administration Guide.
In addition, if a TP (either operator-started or auto-started) needs to be
restricted to particular values for conversation security, confirm
synchronization, or conversation type (mapped or basic), or if you need to
limit the number of instances of the TP that can be running at any time,
you need to define the TP. Use the following verb:
• DEFINE_TP
To obtain information about the definition of a TP, about its current
usage, or about currently active invokable TPs, use the following verbs:
• QUERY_TP_DEFINITION, QUERY_TP, QUERY_AVAILABLE_TP
To delete a defined TP when it is no longer required, use the following
verb:
• DELETE_TP