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
Full-Duplex Protocol
Envoy Application Programming Manual—427159-001
6-4
Full-Duplex/NASDAQ Line Requirements
•
When you configure an Envoy DEVICE that is type (7,30) or type (7,32) you must
specify UNIT 0. UNIT 0 indicates outgoing (write) line.
•
When you configure an Envoy DEVICE that is type (7,31) or type (7,33) you must
specify UNIT 1. UNIT 1 indicates incoming (read) line.
In addition to specifying the UNIT attribute, you must specify the following profile
modifiers when you add these types of DEVICEs:
•
ONEUNIT
•
DEDICATED
Normally, you can configure only one DEVICE per line on a SWAN concentrator.
However, when you configure a full-duplex Envoy DEVICE, you configure two
DEVICES per line on the SWAN concentrator: one DEVICE for outgoing data (UNIT
0) and one DEVICE for incoming data (UNIT 1).
You must also specify the MULTI attribute on the read (UNIT 1) DEVICE. The MULTI
attribute must be set to the name of the write DEVICE: for example, MULTI $LINE1.
Following is an example of the configuration of a normal full-duplex line. Notice that
both DEVICEs use CLIP 1, LINE 0 on the SWAN concentrator named S01. Also notice
that the ONEUNIT and DEDICATED modifiers are specified and that the MULTI
attribute is used on the read (UNIT 1) DEVICE.
Example 6-1
shows a configuration of a NASDAQ full-duplex line. Notice that both
DEVICEs use CLIP 1, LINE 1 on the SWAN concentrator named S01. Also notice that
the ONEUNIT and DEDICATED modifiers are specified and that the MULTI attribute
is used on the read (UNIT 1) DEVICE.
When you start one of the multi devices (for example, $ZZWAN.#LINE1), the other
multi device also starts. Similarly, if you start one of the LINE objects (for example,
LINE 1), the other LINE object also starts. The examples given above demonstrate this.
Example 6-1. Configuration of a NASDAQ Full-Duplex Line
-> ADD PROFILE $ZZWAN.#PENVBSC, FILE $SYSTEM.SYS00.PENVBSC
-> ADD DEVICE $ZZWAN.#LINE3, TYPE (7,32), &
IOPOBJECT $SYSTEM.SYS00.OENVOY,&
PROFILE PENVBSC, ADAPTER S01, CLIP 1,&
LINE 1, PATH A, CPU 0, ALTCPU 1, RECSIZE 1024,&
UNIT 0, ONEUNIT, DEDICATED
-> ADD DEVICE $ZZWAN.#LINE4, TYPE (7,33),&
IOPOBJECT $SYSTEM.SYS00.OENVOY,&
PROFILE PENVBSC, ADAPTER S01, CLIP 1,&
LINE 1, PATH A, CPU 0, ALTCPU 1, RECSIZE 10234,&
UNIT 1, ONEUNIT, DEDICATED, MULTI $LINE3
-> START DEVICE $ZZWAN.#LINE3
-> START LINE $LINE3