HP-UX SNAplus2 NOF Programmer's Guide

Introduction to the NOF API
NOF Verbs to Manage Specific SNAplus2 Functions
Chapter 168
5250 Communications
If SNAplus2 users will be using 5250 emulation to communicate with
AS/400 systems, you need to define the communications link to the
AS/400. For more information, see “Getting Started”.
You then need to define local LUs that can be used for 5250 emulation.
To define LUs, use the following verb:
• DEFINE_LOCAL_LU
If the 5250 emulation program identifies a partner LU by its LU alias,
you need to define the partner LU to associate the alias with an LU
name. (If the program identifies a partner LU by its LU name, this step
is not required.) To define partner LUs, use the following verb:
• DEFINE_PARTNER_LU
To obtain information about the configuration or current status of local
LUs, the current status of partner LUs, or the definition of partner LUs,
use the following verbs:
• QUERY_LOCAL_LU
• QUERY_PARTNER_LU, QUERY_PARTNER_LU_DEFINITION
To delete LUs when they are no longer required, use the following verb:
• DELETE_LOCAL_LU, DELETE_PARTNER_LU
RJE Communications
If SNAplus2 users will be using RJE to submit jobs to host systems for
processing, 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 LUs required for
RJE and must have the solicit_sscp_sessions parameter set to
AP_YES.
You then need to define LUs that can be used for RJE and the RJE
workstations that can access these LUs.
To define LUs, use the following verbs:
• DEFINE_LU_0_to_3, DEFINE_LU_0_TO_3_RANGE
To obtain information about the configuration or current status of LUs,
use the following verb: