Negotiating Application And Presentation Contexts - HP A4500A - VMEbus Single Board Computer 744 Motherboard Programmer's Manual

ap_set_env(fd,AP_BIND_PADDR,paddress)
Note that rebinding the presentation address is not supported in this
release. Binding can only be done in the AP_UNBOUND state.
A/P supports extended addressing which provides for the maximum
address lengths for each selector in the presentation address as shown in
the following table:
Table 4-1 Selector Maximum Lengths
NOTE Other OSI services implementations (non-HP) may not support the same
maximum length for the presentation selector. If your system needs to
communicate with other OSI services, make sure to check the maximum
size supported for the presentation selector.
The NSAP cannot be NULL. NSAPs used for ACSE/Presentation
applications must be configured by the network administrator. T he
NSAP must be unique for the system. The presentation address used by
your ACSE/Presentation application must be different than any other
presentation addresses used by other application services on your system
if you plan to operate these applications at the same time.
For example, if the HP 9000 FTAM service is being used, the address you
create for A/P applications must be different than the FTAM addresses.
See the Installing, and Administering the OSI Transport Services/9000
manual for more information o n presentation addresses.
Negotiating Application and Presentation
Contexts
Both application contexts (specified using the AP_CNTX_NAME
attribute) and presentation contexts (AP_PCDL attribute) must be
negotiated by A/P associations.
Chapter 4
Selector Bytes
Presentation 16
Session 16
Transport 32
NSAP 20
Programming Guide
2. Manage the A/P Environment
51