High Availability Monitors Version A.03.02 Release Notes

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Chapter 1 77
To define and manage the LUs associated with this PU, see “3270
Communications”, “RJE Communications”, or “LUA Communications”,
earlier in this section.
To start the PU (to request an ACTPU from the host) in order to use the
LUs or to stop it when applications are no longer using the LUs, use the
following verbs:
• START_INTERNAL_PU, STOP_INTERNAL_PU
To delete the PU when it is no longer required, use the following verb:
• DELETE_INTERNAL_PU
To set up defaults to simplify DLUR configuration and reduce the
information required on other DLUR verbs, use the following verb:
• DEFINE_DLUR_DEFAULTS
To obtain information about PUs and LUs currently using DLUR , or
about the DLUS nodes they are using, use the following verbs:
• QUERY_DLUR_PU, QUERY_DLUR_LU, QUERY_DLUS
Managing TN Server
If TN3270 users will be using the TN server feature on a SNAplus2 node
to communicate with host systems, you need to define the
communications link to the host. For more information, see “Getting
Started”. The definition of the LS to the host must include the name of a
local PU to own the 3270 LUs and must have the
solicit_sscp_sessions parameter set to AP_YES.
You then need to define LUs that can be used for 3270 emulation and
optionally group these LUs into LU pools. For more information about
defining LUs and users, see “3270 Communications”.
To define the TN3270 users that can access TN server and assign them
to SNAplus2 3270 LUs, use the following verb:
• DEFINE_TN3270_ACCESS
To obtain information about the configuration of TN3270 users, use the
following verb:
• QUERY_TN3270_ACCESS_DEF
To delete TN3270 usersso that they can no longer use TN server for 3270