HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_TN3270_ACCESS
For each user name in the list, up to the number specified in num_users,a
security_user_data
structure is required
with the following information:
user_name
Name of the user. This is a user ID defined using the DEFINE_USERID_PASSWORD verb.
3.43.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
3.43.4 Returned Parameters: Parameter Check
If the verb does not execute because of a parameter error, SNAplus2 returns the following parameters:
primary_rc
AP_PARAMETER_CHECK
secondary_rc
Possible values are:
AP_INVALID_LIST_NAME
The list_name parameter contained a character that was not valid.
AP_INVALID_USER_NAME
One or more of the specified user names was not valid.
Appendix B, Common Return Codes lists further secondary return codes associated with
AP_PARAMETER_CHECK,
which are common to all NOF verbs.
3.43.5 Returned Parameters: Other Conditions
Appendix B, Common Return Codes lists further combinations of primary and secondary return codes that are
common to all NOF verbs.
3.44 DEFINE_TN3270_ACCESS
DEFINE_TN3270_ACCESS defines TN3270 access details for a particular client (or default TN3270 access details
for all clients).
Each verb specifies details for one or more sessions. Each session is uniquely identified by the client address and
the server port number. The DEFINE_TN3270_ACCESS verb can be used to define a new client, to define new
sessions for use by an existing client, or to modify the session parameters. (To delete sessions from an existing
client, use DELETE_TN3270_ACCESS.)
3.44.1 VCB Structure
The DEFINE_TN3270_ACCESS verb contains a variable number of tn3270_session_def_data structures; these define
the user’s sessions. The session structures are included at the end of the
def_data structure; the number of these
structures is specified by the num_sessions parameter.
254