Envoy Application Programming Manual
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Application Programming With Envoy
- 7 ADM-2 Multipoint Supervisor Protocol
- 8 TINET Multipoint Supervisor Protocol
- 9 Burroughs Point-To-Point Protocol
- 10 Asynchronous Line Supervisor Protocol
- A ASCII Character Set
- B ASCII to EBCDIC Code Conversion
- C File-System Procedures
- D Statistics Messages
- E S-Series Changes to Envoy
- NonStop™ Himalaya S-Series Server Architecture
- G-Series Migration Considerations
- CBSENSEON and CFSENSEON Modifiers
- LEOTRESYN and NOLEOTRESYN Modifiers
- Treatment of Characters After the Termination Character
- Number of SYN Characters
- DTR Drop
- Reporting of Parity Error
- Half-Duplex Support for Asynchronous Lines
- Controller Replacement
- SYSGEN and COUP
- Unit Numbers
- FDX Line Changes
- No Support for Auto-Call Unit
- Glossary
- Index
Application Programming With Envoy
Envoy Application Programming Manual—427159-001
1-8
Using a Programmatic Interface
Sections 3 through 10 describe how Envoy supports the various types of protocols,
including information on the protocol-specific message formats, usage of Guardian 90
file-system procedures, and error handling. For information on how to configure these
different protocols, refer to the Envoy Configuration and Management Manual.
Using a Programmatic Interface
In some situations, it is desirable to use a programmatic interface rather than an
interactive interface to manage a subsystem such as Envoy for the following reasons:
•
It is efficient to transfer as many routine network-management tasks as possible to
programs running on the computer network, freeing operators and other network-
management personnel to do the work that requires judgment and creativity.
•
Information obtained through programmatic interfaces can be translated directly into
procedures, reports, and so forth.
An application that uses the programmatic interfaces to subsystems can perform tasks
that once required the use of several different interactive interfaces. In addition, the
capability to write your own management applications allows you to tailor them to the
needs and configuration of your network.
For example, you could write a management application that obtains statistics on line
traffic then compare the statistics you just obtained to other statistics about the total
number of transactions. This comparison could determine what percentage of the total
transaction load represents network transactions. Your applications can also
communicate with other subsystems as well as with the Envoy subsystem.
Table 1-1. Protocols, Line Configurations, and Concentrator Types
Protocol Line Configuration Concentrator Type
ADM-2 Multipoint supervisor Asynchronous*
Asynchronous Generalized supervisor Asynchronous
BISYNC (IBM, BSC) Multipoint (supervisor or tributary) Byte-synchronous
BISYNC (IBM, BSC,
SWIFT)
Point-to-point (primary or second-
ary)
Byte-synchronous
Burroughs Point-to-point (primary or second-
ary)
Asynchronous or Byte-
synchronous
Full-Duplex Point-to-point Byte-synchronous
TINET Multipoint supervisor Asynchronous
* Envoy also supports Burroughs multipoint configurations, using either the asynchronous
or byte-synchronous concentrator. Burroughs multipoint asynchronous lines are configured
as ADM-2 lines. Burroughs multipoint byte-synchronous lines are configured the same as
regular BISYNC multipoint supervisor lines.