Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 HP 9000 Networking: Installing and Administering OSI Transport Services > Chapter 1 HP OTS /9000 Resources

Supported Services and Functionality
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

spacerspacerspacer
spacer
spacer
  		 
 

The OTS/9000 product includes the following:

  • ACSE/Presentation services (ISO 8649 and ISO 8822)

  • ROSE Service (ISO 9072-1, CCITT X.219)

  • OSI Session protocol and services (ISO 8326, 8327; CCITT X.215, X.225, T.62)

  • OSI Transport protocol and services (ISO 8072, 8073, 8602; CCITT X.214, X.224 and T.70 for Teletex terminals)

  • OSI Network services: CONS over X.25; CLNS over X.25, FDDI and IEEE 802.3 LANs; ES/IS routing (ISO 8348, 8473, 8878, 9542)

  • RFC1006 - OSI Services over TCP/IP

  • Multi-System Distributed System Gateway (MSDSG) - OSI Services over TCP/ IP (ISO/IEC TR10172)

  • X/Open Transport Interface (XPG.4) (For more information, refer to the XTI Programmer's Reference Guide)

  • APRI (ACSE/Presentation and ROSE Interface) - see the ACSE/Presentation and ROSE manual

ACSE/Presentation Functionality

The ACSE/Presentation and ROSE Interface (APRI) provides a programmatic interface to the Association Control Service Element (ACSE), Remote Operation Service Element (ROSE) and Presentation layer protocols.

The ACSE/Presentation interface enables two or more application processes on the same or different computers to:

  • establish an association (connection) with another application process

  • exchange (send and receive) information

  • shutdown the association (connection)

Using ROSE with ACSE/Presentation provides the request/reply service that is useful in building distributed applications. ROSE cannot be used independently of the ACSE/Presentation interface.

Session Functionality

The Session layer provides cooperating applications with a standard protocol to organize and synchronously exchange user data, and to map user-oriented Session addresses to network-oriented Transport addresses. The Session layer corresponds to layer 5 of the OSI reference model.

OTS/9000 offers the following Session functionality:

  • Session Protocol Version 1 and Version 2 with extended concatenation for half/ full duplex and minor synchronization functional units. The Session version is negotiated at connection establishment. It defaults to Version 1 when either side is unaware of the negotiation or when Version 1 is proposed by one side.

    NOTE: While Version 2 allows extended user data on calls that were not allowed with Version 1, OTS/9000 limits extended user data size to 10 Kilobytes maximum per Session primitive.

  • Infinite Session service data unit (SSDU) size for normal and typed data.

  • The following functional units:

    • Kernel

    • Half-duplex

    • Duplex

    • Expedited data

    • Typed data

    • Minor synchronize

    • Major synchronize

    • Resynchronize

    • Activity management

    • Capability data

    • Exceptions

OTS/9000 does not support negotiated release or symmetric synchronization through the Session API.

Transport Functionality

The Transport layer corresponds to layer 4 of the OSI reference model. As with the Session layer, the Transport layer provides cooperating applications with a standard protocol to organize and exchange user data. Unlike Session, the Transport is implemented with a greater knowledge of the underlying network configuration. Therefore, its definition involves details hidden from the Session layer entity.

The level of Transport sophistication and capabilities are divided into classes of operation, 0 through 4. OTS/9000 implements the following:

  • An application using the Connectionless Network Service (CLNS) must use TP (Transport) class 4.

  • An application using the Connection-Oriented Network Service (CONS) can use TP classes 0, 2, or 4.

  • OTS supports Transport (TP) classes 0, 2, and 4 over CONS/X.25 and TP class 4 over a CLNS IEEE 802.3 or FDDI LAN and CLNS/X.25.

  • TP 0 is the only alternate class OTS supports.

When an administrator configures a class parameter for CONS communications, they can force the use of class 0 only or offer a preferred multiplexing class (TP 2 or TP 4). On the connect request, the transport user can select the preferred class, with or without class 0 as an alternative, or simply select class 0. For example, if an application requests an alternate class of 0 and multiplexing, OTS/9000 may propose TP 2 with an alternate of TP 0 and send the connect request. If the remote does not allow TP 2, TP 0 is used to make the connection.



How HP OTS/9000 Establishes a Connection
  		 


How OTS/9000 Finds a Remote End System  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© © 1989, 1991, 1992, 1995, 1996 Hewlett-Packard Development Company, L.P.