HP-UX SNAplus2 R7 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Because APPN can locate a partner LU dynamically when a local application needs to start a session to it, normally
you do not need to define partner LUs. However, you may need to define partner LUs if you need to enforce the
use of particular APPC features such as conversation security. To define a partner LU, use the following verb:
• DEFINE_PARTNER_LU
To obtain information about the current status of a partner LU or about its definition if it was explicitly defined,
use the following verbs:
• QUERY_PARTNER_LU, QUERY_PARTNER_LU_DEFINITION
If the local application communicates with its partner using one of the standard SNA-defined modes, you do not
need to define a mode. However, you may want to define additional modes for applications that have particular
requirements not covered by the standard modes. To define a mode, use the following verb:
• DEFINE_MODE
To define or query the default mode, which specifies parameters that will be used for any unrecognized mode name,
use the following verbs:
• DEFINE_DEFAULTS, QUERY_DEFAULTS
The class of service (COS) used for a mode is normally one of the standard SNA-defined classes of service. However,
the node can be configured to support mapping each mode to a specific COS (the
mode_to_cos_map_supp parameter
on the DEFINE_NODE verb). In this case, you may want to define additional COSs for applications that have
particular requirements not covered by the standard COSs. To define a COS, use the following verb:
• DEFINE_COS
To specify the default COS to which any unrecognized modes will be mapped, use the following verb:
• DEFINE_MODE
To obtain information about the definition or current usage of a mode, about the COS used by a mode, or about the
definition of a COS, use the following verbs:
• QUERY_MODE_DEFINITION, QUERY_MODE, QUERY_MODE_TO_COS_MAPPING
• QUERY_COS, QUERY_COS_NODE_ROW, QUERY_COS_TG_ROW
If the local and partner LUs use session-level security, you need to define the password used to establish a session
between the local LU and partner LU. To define the password, check the current definition, or delete the password
when it is no longer required, use the following verbs:
• DEFINE_LU_LU_PASSWORD, QUERY_LU_LU_PASSWORD, DELETE_LU_LU_PASSWORD
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 and conversations, use the following verbs:
• QUERY_SESSION, QUERY_ISR_SESSION, QUERY_CONVERSATION
• 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
and a 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
54