HP-UX SNAplus2 R7 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
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
If the invokable TP requires conversation-level security, you need to define user IDs and passwords that remote TPs
can use to access SNAplus2 TPs. To define user IDs and passwords, check the current definitions, or delete user
IDs and passwords when they are no longer required, use the following verbs:
• DEFINE_USERID_PASSWORD, QUERY_USERID_PASSWORD, DELETE_USERID_PASSWORD
To restrict the use of the TP to a specific list of authorized user IDs, check the current list of authorized user IDs,
or delete a list of user IDs when it is no longer required, use the following verbs:
• DEFINE_SECURITY_ACCESS_LIST, QUERY_SECURITY_ACCESS_LIST,
DELETE_SECURITY_ACCESS_LIST
1.5.8 CPI-C Communications
CPI-C applications use the same resources as APPC applications; the information in Section 1.5.7, APPC
Communications, applies to CPI-C as well as to APPC.
In addition, you can set up side information entries for use by CPI-C applications; each entry defines a particular
partner application and the information required to access it. The local CPI-C application can then identify its
partner application simply by the name of a side information entry, instead of having to specify explicit partner LU
and TP names, mode name, and conversation security requirements. To define side information entries, check the
current definitions, or delete entries when they are no longer required, use the following verbs:
• DEFINE_CPIC_SIDE_INFO, QUERY_CPIC_SIDE_INFO, DELETE_CPIC_SIDE_INFO
1.5.9 Managing PU Concentration
If the node supports PU concentration (the pu_conc_support parameter on the DEFINE_NODE verb), to enable
type 0–3 LUs on downstream computers to communicate with host systems using LUs defined on the SNAplus2
node, you must first define the following:
• A DLC, port, and LS from SNAplus2 to the downstream computer. For information about defining these
components, see Section 1.5.2, Getting Started. The LS must be defined with the following parameters:
solicit_sscp_sessions =NO
dspu_services = PU_CONCENTRATION
dspu_name = the name of the PU serving the LUs on the downstream computer
pu_name = all zeros
• One or more type 0–3 LUs on the SNAplus2 node (and optionally an LU pool containing these LUs) for
communications with the host. For information about defining LUs and LU pools, see Section 1.5.3, 3270
Communications.
You then define the LUs on the downstream computer and map these to the LUs on the SNAplus2 node. To define
the downstream LUs, use the following verbs:
55