HP-UX SNAplus2 R7 NOF Programmer's Guide

NOF API Verbs
DEFINE_NODE
AP_NONE
Use the normal processing.
AP_OVERRIDE_ERP
Process all ACTPU requests as ACTPU(cold).
cp_create_parms.ptf[2]
BIS support. SNAplus2 normally uses the BIS protocol prior to deactivating a limited resource LU 6.2 session.
Set this byte to one of the following values:
AP_NONE
Use the normal processing.
AP_SUPPRESS_BIS
Do not use the BIS protocol. Limited resource LU 6.2 sessions are deactivated immediately using
UNBIND(cleanup).
cp_create_parms.ptf[3]
APINGD support. SNAplus2 normally includes a partner program for the APING connectivity tester. This
byte allows you to disable the APING Daemon within the node, so that requests by an APING program
arriving at the node will not be processed automatically. Set this byte to one of the following values:
AP_NONE
Include APINGD support within the node (the normal processing).
AP_EXTERNAL_APINGD
Disable APINGD within the node.
cp_create_parms.ptf[4]
LU 0–3 RU checks. This byte is used to provide workarounds for host systems that send non-standard SNA
data; it should be set to AP_NONE unless you have encountered the specific problem described below.
To use SNAplus2’s normal checking on LU 0–3 RUs, set this parameter to AP_NONE.
To relax specific checks on LU 0–3 RUs, specify the following value:
AP_ALLOW_BB_RQE
The SNA protocols state that BB !EB RUs on LU 0–3 PLU-SLU sessions must be RQD. Several hosts
send RQE BB !EB CD - a protocol violation which SNAplus2 always tolerates. If this value is set,
SNAplus2 will tolerate RQE BB !EB !CD EC RUs as well.
cp_create_parms.ptf[5]
Security checking for received Attaches.
If a local invokable TP is defined not to require conversation security, or is not defined and therefore defaults
to not requiring conversation security, the invoking TP need not send a user ID and password to access it.
If the invoking TP supplies these parameters and they are included in the Attach message that SNAplus2
receives, SNAplus2 normally checks the parameters (and rejects the Attach if they are not valid) even though
the invokable TP does not require conversation security. This parameter allows you to disable the checking.
Set this byte to one of the following values:
AP_NONE
Always check security parameters if they are included on a received Attach, regardless of the security
requirements of the invokable TP (the normal processing).
AP_LIMIT_TP_SECURITY
222