Browse Prior Art Database

Generic Alerts for X.25 Logical Link Control Level Errors

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

Publishing Venue

IBM

Related People

Emami, K: AUTHOR [+3]

Abstract

The OS/2 Extended Edition Version 1.2 Communication Manager (CM) allows all of its SNA applications (e.g., 3270 Emulation, 5250 Work Station Feature, file transfer) and APIs (e.g., APPC, EHLLAPI, SRPI, LU A) to communicate through an X.25 packet-switched data network using the Qualified Logical Link Control (QLLC) protocol.

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

Generic Alerts for X.25 Logical Link Control Level Errors

       The OS/2 Extended Edition Version 1.2 Communication
Manager (CM) allows all of its SNA applications (e.g., 3270
Emulation, 5250 Work Station Feature, file transfer) and APIs (e.g.,
APPC, EHLLAPI, SRPI, LU A) to communicate through an X.25
packet-switched data network using the Qualified Logical Link Control
(QLLC) protocol.

      The CM has defined eleven C&SM (Communication and Subsystem
Management) Generic Alerts for reporting QLLC errors (see the next
page).  When the CM detects a QLLC error, it dynamically builds the
appropriate alert and stores it in the local error log. If the CM is
connected to a C&SM focal point product (typically a System/370
host), the alert is forwarded to that product. These alerts contain
the information a communications network operator needs to do remote
problem determination. Typically, a network operator will be running
an application program (e.g., Netview) that interprets the alert and
displays the network address of the failing DTE and information about
the failure condition. It also suggests corrective actions and, when
applicable, displays the following information about a failing
virtual circuit:  the logical channel number, the called address, the
calling address, and whether the failing DTE or its partner initiated
the virtual circuit connection.

      The QLLC alerts contain the following information (for details
on the precise encoding of each of the QLLC alerts, please refer to
the "IBM Operating System/2 Extended Edition Version 1.2 Programming
Services and Advanced Problem Determination for Communications"
manual):
         .  Alert major vector
         . Generic Alert subvector
         . Probable Causes subvector
         . User Causes subvector (if required)
         . Install Causes subvector (if required)
         . Failure Causes subvector
         . Recommended Actions subfields
         . Product Set ID Index subfield
         . Detailed Data subf...