HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_CPIC_SIDE_INFO
XC_SECURITY_PROGRAM_STRONG
As for XC_SECURITY_PROGRAM, except that the local node must not send the password across the
network in clear text format. This value can be used only if the remote system supports password
substitution.
XC_SECURITY_SAME
The target TP uses conversation security, and can accept an “already verified” indicator from the local
TP. (This indicates that the local TP was itself invoked by another TP, and has veri
fied the security user
ID and password supplied by this TP.) The
security_user_id parameter specified below will be used to
access the target TP; no password is required.
def_data.side_info.security_user_id
User ID used to access the partner TP. This parameter is not required if the conversation_security_type
parameter is set to XC_SECURITY_NONE.
def_data.side_info.security_password
Password used to access the partner TP. This parameter is required only if the conversation_security_type
parameter is set to XC_SECURITY_PROGRAM or XC_SECURITY_PROGRAM_STRONG.
def_data.side_info.lu_alias
The alias of the local LU used to communicate with the target TP. This alias is a character string using any
locally displayable characters.
3.15.3 Returned Parameters: Successful Execution
If the verb executes successfully, SNAplus2 returns the following parameters:
primary_rc
AP_OK
3.15.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
AP_INVALID_SYM_DEST_NAME
The sym_dest_name parameter contained a character that 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.15.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.
123