Browse Prior Art Database

Automatic Routing of X.25 Virtual Calls

IP.com Disclosure Number: IPCOM000100334D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 2 page(s) / 75K

Publishing Venue

IBM

Related People

Geise, DM: AUTHOR [+4]

Abstract

The OS/2* Extended Edition Version 1.2 Communications Manager provides an X.25 Applications Programming Interface (hereafter referred to as the "API") which allows you to write programs that can communicate with other computers or workstations that are attached to an X.25 packet- switched data network. This API allows programs to place X.25 virtual calls in a configuration independent fashion.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Automatic Routing of X.25 Virtual Calls

       The OS/2* Extended Edition Version 1.2 Communications
Manager provides an X.25 Applications Programming Interface
(hereafter referred to as the "API") which allows you to write
programs that can communicate with other computers or workstations
that are attached to an X.25 packet- switched data network. This API
allows programs to place X.25 virtual calls in a configuration
independent fashion.

      As shown in the figure, a PS/2* workstation with OS/2 Extended
Edition Version 1.2 may be connected to one or more X.25 networks
with one or more physical links to each network. The workstation
appears as a separate DTE on each X.25 physical link.

      When a program places an X.25 virtual call, it must normally
specify the following parameters:
       .   physical link id
       .   called address (address of the remote DTE)
       .   calling address (optional address of the local
           DTE)
       .   called address extension (optional address
           extension of the remote DTE)
       .   calling address extension (optional address
           extension of the local DTE)

      The X.25 API simplifies this task by optionally allowing
programs to place virtual calls by specifying the names of the remote
and local DTEs. A "Directory" associates these names with X.25
physical links and addresses. The system administrator creates and
maintains the directory during Communication Manager configuration.
When a program instructs the API to place a virtual call,...