High Availability Monitors Version A.03.02 Release Notes

NOF API Verbs (ACTIVATE_SESSION to OPEN_FILE)
DEFINE_TN3270_ACCESS
Chapter 3 375
primary_rc AP_PARAMETER_CHECK
secondary_rc Possible values are:
AP_UNKNOWN_CLIENT_ADDRESS
The specified name or alias could not be mapped to a
fully qualified name.
AP_CLIENT_ADDRESS_CLASH
The fully qualified name, resolved from the
client_address parameter, clashes with one that has
already been defined.
AP_TCPIP_PORT_IN_USE
The TCP/IP port number cannot be used by TN server
because it is already in use by a different program.
AP_INVALID_TN3270_SUPPORT
The tn_3270_support parameter for one or more
sessions was not set to a valid value.
Appendix A, “Common Return Codes,” lists further secondary return
codes associated with AP_PARAMETER_CHECK, which are common to all
NOF verbs.
Returned Parameters: Other Conditions
Appendix A, “Common Return Codes,” lists further combinations of
primary and secondary return codes that are common to all NOF verbs.
Using the Telnet Daemon's TCP/IP Port
If you are setting up TN server for use with a TN3270 program that uses
TCP/IP port number 23, you will need to set up the HP-UX computer
where the node owning this TN server runs, to share this port number
between TN server and the Telnet daemon program. To do this, take the
following steps:
Step 1. Ensure that the SNAplus2 software is stopped on the HP-UX computer.
Step 2. Log on to the HP-UX computer as root.
Step 3. Edit the file /etc/inetd.conf, and find the line beginning with telnet.
Make a note of the executable name and any supplied parameters for the