HP rp5400 ACSE/Presentation and ROSE Interface Programmer's Guide
HP rp5400 Manual
View all HP rp5400 manuals
Add to My Manuals
Save this manual to your list of manuals |
HP rp5400 manual content summary:
- HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 1
ACSE/Presentation and ROSE Interface Programmer's Guide Edition 4 32070-90032 HP9000 Networking 05/97 Printed in: United States © Copyright 1997 Hewlett-Packard Company. All rights reserved. - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 2
product and replacement parts can be obtained from your local Sales and Service Office. Restricted Rights Legend. Use, duplication or disclosure by the COMPANY 3000 Hanover Street Palo Alto, California 94304 U.S.A. Use of this manual and flexible disk(s) or tape cartridge(s) supplied for this pack is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 3
©copyright 1980, 1984, 1986 Novell, Inc. ©copyright 1986-1992 Sun Microsystems, Inc. ©copyright 1985-86, 1988 Massachusetts Institute of Technology. ©copyright 1989-93 The Open Software Foundation, Inc. ©copyright 1986 Digital Equipment Corporation. ©copyright 1990 Motorola, Inc. ©copyright 1990, - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 4
4 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 5
14 File Naming 14 What is the HP ACSE/Presentation and ROSE Interface 15 ACSE/Presentation 15 ROSE 15 Support for Multi-Threaded Applications 15 Standards Supported 17 Limitations 18 Who Should Use This Manual 20 2. Supported ACSE/Presentation and ROSE Calls ACSE/Presentation Calls and - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 6
Release the Association 42 Requesting the Release 42 Confirm the Release Request 42 Step 5: Closing the Communication Endpoint 44 4. Programming Guide Summary of Programming Tasks 46 1. Prepare the System 48 2. Manage the A/P Environment 49 Determine Initiator and Responder Roles 49 Determine - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 7
Running ACSE/Presentation Applications 64 Multi-threaded ACSE/Presentation Example 64 ACSE/Presentation Example 65 Program using ROSE 66 5. Troubleshooting Your Application Using A/P API Tracing 68 A/P API Tracing Using Environmental Variables 68 Tracing Using Global Variables 70 Selecting - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 8
Contents A. ACSE/Presentation Reference Pages ACSE/Presentation Primitives 82 Glossary 8 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 9
extensive changes are made. Manual updates may be issued between editions to correct errors or document product changes. To ensure that you receive the updated or new editions, you should subscribe to the appropriate product support service. See your HP sales representative for details. Edition - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 10
10 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 11
using the ACSE/ Presentation (A/P) interface. Chapter 5 "Troubleshooting Your Application" describes API tracing for ACSE/Presentation followed by API tracing for ROSE. Appendix A "ACSE/Presentation Reference Pages" includes a list of the supported ACSE/Presentation attributes and a glossary of - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 12
12 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 13
1 APRI Overview This chapter provides an overview of what the HP ACSE/Presentation and ROSE interface provides. 13 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 14
programmatic interface is provided with the HP OTS/9000 product on HP 9000 systems. ASN.1 Support If your application requires encoding/decoding abstract application programs. File Naming To use the MAN feature on systems that support a maximum file length of 14 characters, the ACSE/Presentation and - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 15
ACSE/Presentation provides the request/reply service which is useful in building distributed applications. Note that ROSE cannot be used independently of the ACSE/Presentation interface. Support for Multi-Threaded Applications This version of HP OTS/9000 supports multi-threaded applications to be - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 16
APRI Overview What is the HP ACSE/Presentation and ROSE Interface #define ap_errno _ap_errno() • Any multi-threaded application program, which also includes osi_lib.h, should include it after the threads-specific - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 17
APRI Overview Standards Supported Standards Supported The interface provided is based on the services defined in the ISO ACSE and Presentation Service Definitions (ISO 8649 and ISO 8822) and ROSE (ISO 9072). The HP OTS/9000 subset implementation of the ACSE/Presentation library interface is based on - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 18
Figure 1-1 APRI Overview Standards Supported OSI MODEL - ACSE Presentation and ROSE APPLICATION PROCESS Layer 7 Layer 6 Layer 5 Layer 4 Layer 3 Layer 2 Layer 1 ACSE/Presentation & ROSE Interface ACSE ROSE PRESENTATION SESSION TRANSPORT NETWORK - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 19
primitives used in ACSE/Presentation calls: A subset of the defined primitives are supported. Chapter 2 provides a list of the supported primitives. ROSE: • Reliable Transfer Service (RTS) including operation class is not supported. • Priority is not implemented for this release. Chapter 1 19 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 20
is provided for application programmers who need to use ACSE/Presentation and ROSE services. It is expected that the user of this manual is an experienced applications programmer with knowledge of the HP-UX operating system and programming environment, the X.25 protocol, OSI transport, session, and - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 21
2 Supported ACSE/Presentation and ROSE Calls This chapter provides lists and brief descriptions of the supported ACSE/ Presentation and ROSE calls and primitives. 21 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 22
descriptions or references made in this manual. The manpages are accessible online with the manpage function of HP-UX. Included here are tables of rst by task, then by call in alphabetic order in Table 2-1. The supported primitives are described in Table 2-2. A/P Functions The A/P calls can be - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 23
Release a communication endpoint. Returns an error message. Free memory for the A/P data structures. Retrieve the value of an A/P environment attribute. Initialize the A/P environment. Establish a communication endpoint to support an instance of the A/P environment. Provides an interface for - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 24
association. User data may be associated with the primitive. Table 2-2 ACSE/Presentation Primitives The following table lists the supported ACSE/Presentation layer service primitives. These primitives are used with the ap_rcv() and ap_snd() calls as described below. Some of the primitives contain - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 25
Supported () to indicate an association has been abnormally released because of problems below the application layer. Used with ap_snd() to request the of an association. Used with ap_rcv() to indicate that the remote service user wants to release the association. Used with ap_snd() to respond - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 26
Supported ACSE/Presentation and ROSE Calls ACSE/Presentation Calls and Primitives Primitives P_RESYNC_CNF P_SYNCMINOR_REQ P_SMINOR_REQ P_SYNCMINOR_IND P_SMINOR_IND P_SYNCMINOR_RSP P_SMINOR_RSP P_SYNCMINOR_CNF P_SMINOR_CNF P_TOKENGIVE_REQ P_TOKENGIREQ P_TOKENGIVE_IND P_TOKENGIIND P_TOKENPLEASE_REQ - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 27
refer to the man page RO_INTRO(5) for general information about ROSE. ROSE Calls ROSE only supports two calls as listed below. ROSE is used to provide ROSE provider services to an application using the ACSE/Presentation interface. Rose Calls ROSE Calls Description ro_bind() ro_unbind() Enable - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 28
Supported ACSE/Presentation and ROSE Calls ROSE Calls and Primitives Primitives RO_REJECTP_IND RO_REJ_P_IND RO_REJECTU_REQ RO_REJ_U_REQ RO_REJECTU_IND RO_REJ_U_IND RO_RESULT_REQ RO_RESULTREQ RO_RESULT_IND RO_RESULTIND Description ROSE provider rejection indication. - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 29
3 Using ACSE/Presentation This chapter provides a sample session using ACSE/Presentation between two processes in synchronous mode. 29 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 30
the section, "Using Synchronous vs. Asynchronous Mode" in chapter 4 for more information. In order to use the ACSE/Presentation service, the processes do the following: 1. Create a communication endpoint. 2. Establish an association that requires: a. Initializing the ACSE/Presentation environment - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 31
Using ACSE/Presentation Summary of Calls Table 3-1 Summary of Calls A summary of the ACSE/Presentation calls are described in the following sections. ACSE/Presentation Call Summary Process A Process B ap_open() ap_init_env() ap_open() ap_init_env() ap_set_env() (*initiator*) ap_set_env() (* - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 32
Using ACSE/Presentation Summary of Calls Process A ap_poll() - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 33
Using ACSE/Presentation Step 1: Create a Communication Endpoint Figure 3-1 Step 1: Create a Communication Endpoint Process A and Process B must both create communication endpoints as shown in Figure 3-1, using the call ap_open(). A communication endpoint is a file descriptor (fd) which is returned - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 34
are described below. Initialize the A/P Environment To use the A/P services, each process must initialize the ACSE/Presentation environment by calling ap_init_env(). (See Figure 3-2.) The ap_init_env() call allocates memory for the environment attributes, and sets the attributes to default values - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 35
Figure 3-3 Using ACSE/Presentation Step 2: Establish an Association Establish Initiator and Responder Roles Process A and Process B establish initiator and responder roles using the attribute, AP_ROLE_ALLOWED in a call to ap_set_env(). In this example, Process A is the initiator, and Process B is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 36
supports the binding of the local presentation address without specifying a network address. This allows a single responder to receive association indications for any of the subnetworks configured on an OTS/ 9000 address to a communication endpoint is not supported in this release. Binding to the - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 37
Figure 3-5 Using ACSE/Presentation Step 2: Establish an Association Process A calls ap_set_env() using the AP_CNTX_NAME attribute to identify the application context name. Process A then calls ap_set_env() using the AP_PCDL attribute to propose transfer syntaxes for each proposed abstract syntax - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 38
set its transfer syntax. Process B sets the res field in the structure ap_cdrl_t to ACCPT and the transfer syntax pointer to the supported transfer syntax object id. Process B then calls ap_snd() using the A_ASSOC_RSP primitive to accept the association request. (See Figure 3-7.) Process A must wait - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 39
Figure 3-7 Using ACSE/Presentation Step 2: Establish an Association Process B can reject the connection if the proposed transfer syntax is not supported by setting the res field in structure ap_cdrl_t to USER_REJ or PROV_REJ and prov_rsn is the reason for the reject. If the process cannot accept - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 40
Process B uses ap_poll() to monitor events. The data received by ap_rcv() is indicated by the P_DATA_IND primitive. Note that the AP_ALLOC option is not supported. The buffer pointed to by ubuf must be allocated by the user. If the data received is more than the allocated buffer, the flags parameter - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 41
Figure 3-8 Send Data Process A AP Environment A AP_DCS,dcs AP_PCDRL,pcdrl ap_get_env() ap_set_env() Using ACSE/Presentation Step 3. Exchanging Data Process B AP Environment B Initiator Communication Endpoint A ap_snd() data Responder Communication Endpoint B ap_poll() ap_rcv() Chapter 3 41 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 42
Using ACSE/Presentation Step 4: Release the Association Figure 3-9 Step 4: Release the Association Processes must cooperate to ensure that no data is lost when the association is released. This can be accomplished by requesting a release, accepting the release, then terminating the association. - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 43
ap_poll() and receives the response by calling ap_rcv(). If an association is released abnormally, for example, if a lower layer problem occurs, a provider abort (A_PABORT_IND primitive) may be received. Response to Release Process A Process B AP Environment A AP Environment B ap_poll() ap_rcv - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 44
Using ACSE/Presentation Step 5: Closing the Communication Endpoint CAUTION Figure 3-11 Step 5: Closing the Communication Endpoint Finally, both processes use ap_close() to close down the communication endpoint (file descriptor) and A/P environment resources (see Figure 3-11). If the association is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 45
4 Programming Guide This chapter provides information to assist you in writing and executing applications using the ACSE/Presentation (A/P) interface. 45 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 46
in more detail in the following sections. 1. Prepare system. Make sure HP OTS/9000 h as been installed, configured, and started successfully. (See the Installing and Administering OSI Transport Services manual for information.) 2. Manage the A/P environment. To establish and maintain connections - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 47
Programming Guide Summary of Programming Tasks 5. Decide if multiple associations need to be supported. The process accepting multiple a new version of HP OTS/9000, you must re-link your programs with the new library. 8. Troubleshoot your application. If you have problems, you can use API - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 48
Guide 1. Prepare the System 1. Prepare the System Before you use the ACSE/Presentation interfaces, make sure that the following has been done: • Verify HP OTS/9000 configuration file. • Verify that HP OTS/9000 h as been started either manually using osiadmin or at start-up time. 48 Chapter 4 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 49
Programming Guide 2. Manage the A/P Environment 2. Manage the A/P Environment The ACSE/ a specified attribute. When you use ap_get_env() for attributes which are stored as data structures, memory is allocated for you. When you have finished using the information from the data structure, must use - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 50
Guide n optional network service access point (NSAP). APRI also supports the binding of the local presentation address without specifying a network address. This allows a single responder to receive association indications for any of the subnetworks configured on an HP OTS/9000 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 51
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 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 52
Guide 2. Manage the A/P Environment Application Contexts (AP_CNTX_NAME) Associations must negotiate the application contexts used. The initiator proposes a service or services implementation currently only supports one. However, as the A/P specification evolves, others may be supported. • In future - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 53
Programming Guide 2. Manage the A/P Environment • Isolate the allocations and freeing of memory passed to the A/P library to a single function. For example: void *ubuf_ptr; user_get_osi_buf (&ubuf_ptr, len,"data to put in ubuf"); ap_snd (.., ubuf_ptr); • Do not statically initialize a - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 54
Programming Guide 3. Managing Data 3. Managing Data ACSE/ and transfer syntax selected. Control Data Control data is associated with the supported ACSE/Presentation primitives and is managed by the A/P library. Control data AP_MORE bit to indicate the end of the data. For example: 54 Chapter 4 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 55
Programming Guide 3. Managing Data 1) First ap_snd() 2) Additional ap_snd()'s 3) Last ap_snd() set AP_MORE, and send data set AP_MORE, and send data re-set AP_MORE, and send last data - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 56
Programming Guide 4. Using Synchronous vs. Asynchronous Mode 4. Using Synchronous vs. Asynchronous Mode ACSE/Presentation supports both synchronous and asynchronous mode execution of calls. In synchronous mode, an ACSE/Presentation call blocks until the call can be completed. While blocked, no - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 57
Programming Guide 4. Using Synchronous vs. Asynchronous Mode If ap_rcv() is called in is lost. Note that ap_rcv() may still be blocked by running in asynchronous mode in memory shortage situations such as when using large numbers of connections. Changing Modes Once a communication endpoint - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 58
Programming Guide 5. Managing Multiple Connections 5. Managing Multiple Connections Before writing an guaranteed (as previously described), the following situation could occur: • The initiator process is servicing endpoint B which has just sent out a connection request (A_ASSOC_REQ) and is waiting - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 59
Guide 5. Managing Multiple Connections packets and is waiting for the release indication (A_RELEASE_IND) while endpoint D is in AP_IDLE state waiting for the connection indication (A_ASSOC_IND). Multiple Connections Scenario Initiator Process Responder Process servicing servicing service - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 60
NOTE Programming Guide 5. Managing Multiple Connections Connection memory shortage on the remote side of the connection request. To handle this situation, an application can implement a connection retry mechanism to re-send the request again. Keep in mind that this type of resource shortage problem - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 61
Guide 5. Managing Multiple Connections Note that if an ACSE/Presentation call (such as ap_open()) fails because of temporary memory shortage, the application may want to retry the same call later. System Maximums OTS supports pacing should avoid possible timing problems. Process Maximums It is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 62
file system calls such as exec(2), dup(2), read(2), write(2), ioctl(2), or select(2) with HP OTS/9000 A CSE/Presentation file descriptors. Note that fork(2) can be used, but do not use fork(2) with exec(2). A communication endpoint is returned when the ACSE/Presentation - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 63
Programming Guide 6. Other Tasks Signal handlers can be written to capture signals and errors you can access using ap_error() is included in the ap_intro manpage. For determining where problems occur, you can also use API tracing which is described in Chapter 5,Ttroubleshooting your Application. - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 64
Programming Guide 7. Before Running ACSE/Presentation Applications 7. Before Running ACSE/Presentation Applications In order to run ACSE/Presentation applications between two processes or systems, make sure: • your - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 65
NOTE Programming Guide ACSE/Presentation Example ACSE/Presentation Example Sample programs are included online in the /opt/ots/apli/demo directory. You'll also find: • A readme file describing - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 66
Programming Guide Program using ROSE Program using ROSE Additional programs are included online in /opt/ots/rose/demo which exercise the ROSE library functions and provide an - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 67
5 Troubleshooting Your Application This chapter describes API tracing for ACSE/Presentation followed by API tracing for ROSE. 67 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 68
Troubleshooting Your Application Using A/P API Tracing Using A/P API Tracing You enable tracing in your application program and the tracing output is printed to a trace file. Different - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 69
Troubleshooting Your Application Using A/P API Tracing environment variables on the first valid APRI call (always ap_open) and then set the global API trace variables according to - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 70
Troubleshooting Your Application Using A/P API Tracing AP_TRACE_MAX_UDATA:. The maximum amount of user data (in bytes) that will be displayed when parameters are displayed. Default = 16. Tracing - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 71
Troubleshooting Your Application Using A/P API Tracing API_TR_ENTRY_EXIT API_TR_INPUT API_TR_OUTPUT back to your program. Enables internal tracing. Use if directed to do so by your HP support representative. Enables external and internal error tracing. Recommended that users turn this tracing on at - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 72
Troubleshooting Your Application Using A/P API Tracing 2. Within your program, enable tracing and select the level of tracing you want by modifying the value of the ap_trace - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 73
Troubleshooting Your Application Using A/P API Tracing 15:53:38 len = 4 val->buf = (4/4) 52 01 00 04 R.... • The amount of data displayed is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 74
Troubleshooting Your Application Using A/P API Tracing >>> thread-id = 6 >>> > pathname = /dev/osipi > oflags = 0x0 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 75
Troubleshooting Your Application Using ROSE API Tracing Using ROSE API Tracing Tracing is enabled in your application program and the tracing output is printed to a trace fi - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 76
Table 5-1 Troubleshooting Your Application Using ROSE API Tracing AP_TRACE_FILE: The name of the file that is to receive tracing results. Default = stderr. AP_TRACE_MAX_UDATA: The maximum amount of - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 77
Troubleshooting Your Application Using ROSE API Tracing Table 5-2 ROSE Tracing Types passing back to your program. Enables internal tracing. Use if directed to do so by your HP support representative. Enables external and internal error tracing. Recommended that users turn this tracing on at all - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 78
Troubleshooting Your Application Using ROSE API Tracing 2. Within your program, enable tracing and select the level of tracing you want by modifying the value of the - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 79
Troubleshooting Your Application Using ROSE API Tracing • The amount of data displayed is based on the value set for rose_trace_max_udata. For example, if rose_trace_max_udata is set - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 80
Troubleshooting Your Application Using ROSE API Tracing 80 Chapter 5 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 81
A ACSE/Presentation Reference Pages This appendix includes a list of the supported ACSE/Presentation attributes and a glossary of terms 81 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 82
long or'd bits: AP_ACSEVER1 bit values: AP_ACSEVER1 always only in states: AP_UNBOUND AP_IDLE AP_BIND_PADDR Presentation address to which the stream supporting this instance of the A/P-Library is bound ap _paddr_t N.A. Any allowed by the C type always ap_paddr_t only in state AP_UNBOUND - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 83
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_CLD_AEQ Called application entity qualifier any_t None Any - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 84
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_CLG_APID Calling application process invocation identifier long - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 85
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_DPCN Default presentation context name AP_DPCR Default - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 86
of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_MODE_AVAIL Specifies the modes in which the ACSE services may operate unsigned long AP_MODE_SEL Specifies the mode in - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 87
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_PFU_SEL Bitmask indicating which Presentation Layer functional - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 88
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_ROLE_CURRENT Indicates whether the library user is the - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 89
bit values: AP_SESSVER1 AP_SESSVER2 always never AP_SESS_OPT_AVAIL Bitmask indicating whether certain optional capabilities of the session layer are supported by the underlying protocol provider unsigned long AP_SESS_SEL Bitmask indicating which version of the ISO Session Layer protocol is - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 90
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_SFU_AVAIL Bitmark indicating which Session Layer functional - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 91
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_STATE unsigned Current state of the long A/P- Library - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 92
Name of attribute/ Purpose Data Type Default value of attribute Values legal for this attribute (* = not supported by current release) Readable states (value of AP_STATE attribute) Writable states (value of AP_STATE attribute) AP_TOKENS_AVAIL Bitmark indicating which session tokens are - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 93
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 93 Table A-2 Primitive A_ABORT_IND A_ASSOC_IND AP_RCV Table of Attributes This primitive valid in states Ap_env attribute that must be set May change attributes all except: AP_UNBOUND AP_IDLE AP_IDLE none AP_STATE AP_BIND_PA DDR - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 94
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 94 Primitive A_ASSOC_CNF A_PABORT_IND A_RELEASE_IND A_RELEASE_CNF P_DATA_IND P_RESYNC_IND This primitive valid in states Ap_env attribute that must be set May change attributes AP_WASSOCcnf_ASSOCreq none all except: AP_UNBOUND - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 95
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 95 Primitive P_RESYNC_CNF P_SYNCMINOR_IND P_SYNCMINOR_CNF P_TOKENGIVE_IND This primitive valid in states Ap_env attribute that must be set May change attributes AP_WRESYNcnf_RESYNreq none AP_DATA_XFER none AP_DATA_XFER none - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 96
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 96 Primitive RO_REJECTU_IND RO_RESULT_IND This primitive valid in states Ap_env attribute that must be set May change attributes AP_DATAXFER none AP_WRELcnf_RELreq AP_WSYNCMAcnf_SYNCMAreq AP_WACTEcnf_ACTEreq AP_DATAXFER none - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 97
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 97 Table A-3 Primitive A_ABORT_REQ A_ASSOC_REQ A_ASSOC_RSP AP_SND Table of Attributes This primitive, valid in states Ap_env attributes that may be set (must be set in BOLD) May change attributes Next state (values of AP_STATE - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 98
Primitive This primitive, valid in states Ap_env attributes that may be set (must be set in BOLD) May change attributes Next state (values of AP_STATE attribute) A_PABORT_REQ A_RELEASE_REQ A_RELEASE_RSP P_DATA_REQ P_RESYNC_REQ P_RESYNC_RSP all except: AP_UNBOUND AP_IDLE AP_DATAXFER - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 99
Primitive This primitive, valid in states Ap_env attributes that may be set (must be set in BOLD) May change attributes Next state (values of AP_STATE attribute) P_TOKENGIVE_REQ AP_DATAXFER none AP_WSYNCHMAcnf_SYNCMAreq AP_WACTEcnf_ACTEreq AP_WSYNCMArsp_SYNCMAind AP_WACTErsp_ACTEind - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 100
ACSE/Presentation Reference Pages ACSE/Presentation Primitives 100 Appendix A - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 101
model; the user interface to network services and applications that provides services to directly support users. provided by ACSE, Presentation and remote operation service element (ROSE). ARPA See DARPA. ACSE Association Control Service Element. The service element in the OSI Application layer - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 102
layer that provides datagrams to transmit data. Connection oriented network service. The layer 3 network layer that provides end-to-end connection (virtual circuit) to transmit data. CONS See Connection oriented network service. Corporation for Open Systems a non- profit, multinational consortium of - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 103
emerging Application Layer standard for the electronic exchange of business data. ES End system. EWOS European Workshop on Open Systems. FDDI Fiber Distributed Data implement a networking standard so that their products can Integrated Services Digital Network a developing standard whose goal is to - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 104
identifier (AFI) and the initial domain identifier (IDI). IDP spaces are managed by organizations such as AFNOR, ANSI and NIST. ISDN See Integrated Services Digital Network migration the non-disruptive replacement of proprietary networks with standards-based networks. MMS Manufacturing Messaging - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 105
transport selectors) and one or more NSAPs. Optionally, it can include the application entity (AE) title which is a unique name identifying an OSI service such as FTAM. Presentation Layer Layer 6 of the OSI model; where data are put into usable form. proprietary networking networking that uses the - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 106
-to-end data integrity between processes. X.400 CCITT standard for electronic message handling systems (e.g., electronic mail) in multivendor environments. X.500 Directory Services An international OSI standard for distributed directory services for multivendor OSI environments. Directory Services - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 107
/Presentation before running applications, 64 calls, 23 calls not supported, 19 calls, summary, 23 functions by task, 22 22 audience for manual, 20 B binding endpoints, 35 binding p-address, 51 C changing modes, 57 client,server, 49 close data, 55 dynamic memory allocation, 60 Index 107 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 108
supported, 17 initialize the A/P environment, 34 initiator roles, 49 L limitations, 18 ACSE/Presentation, 19 M manpages A/P calls, 22 A/P primitives, 22 short names for, 14 memory programming guide, 45 programming tasks summary, 46 provider abort, 43 p-selector max. size, 51 R reference manuals, 20 - HP rp5400 | ACSE/Presentation and ROSE Interface Programmer's Guide - Page 109
, 17 X.410, 17 synchronous mode, 56 description, 56 system maximums, 61 system support 14 character file names, 14 systems supported, 14 W What is ACSE/Presentation, 15 What is ROSE, 15 who should use this manual, 20 X X.410, 17 XAP migration guidelines, 52 migration to, 52 T tracing A/P APIs
ACSE/Presentation and ROSE Interface
Programmer’s Guide
Edition 4
32070-90032
HP9000 Networking
05/97
Printed in: United States
© Copyright 1997 Hewlett-Packard Company. All rights reserved.