| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 114.1 | Endg�ltige SPD f�r DEC FTSIE for ULTRIX V1.0 | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE | Thu Aug 29 1991 15:11 | 326 |
| -----------------------------------------------------------------------------
Software
Produkt
Beschreibung
-----------------------------------------------------------------------------
PRODUKTNAME: DEC FTSIE for ULTRIX Version 1.0 SPD: 36.47.00
Kopplungsm�glichkeiten mit DEC FTSIE
X.25 Fernkopplung (nur mit XTI und OSI Transport
for ULTRIX Unterst�tzng)
ULTRIX SNI
BS2000
+----------+ +---------+
|DEC FTSIE | | |
+----------+ PDN | FT- |
| (XTI) | +------+ +----+ | BS2000 |
+----------+ |X.25- | +-----+ +-----+ | | +---------+
|X25 ACCESS+---+Router+---+MODEM+-..-+ +-..-+MODEM+---+X.25+-+ DCAM V9 |
+----------+ +------+ +-----+ | | +-----+ +----+ +---------+
| |
+---+---+--+
| PSDN |
|(DATEX-P) | Leitungsgeschwindigkeit
| | maximal 48 kbit/s
+----------+
X.25 Nahkopplung (nur mit XTI and OSI Transport
for ULTRIX Unterst�tzung)
ULTRIX SNI
BS2000
+------------+
| DEC FTSIE | +---------+
+------------+ | FT- |
| (XTI) | PDN | BS2000 |
+------------+ +-------+ +------------------+ +-------+ +---------+
| X25 ACCESS +---+ X.25- +---+ Modem-Eliminator +----+ X.25 +---+ DCAM V9 |
+------------+ | Router| +------------------+ +-------+ +---------+
+-------+
Leitungsgeschwindigkeit
maximal 48 kbit/s
Ethernet-Kopplung
ULTRIX SNI
BS2000
+------------+
| DEC FTSIE | +---------+
+------------+ Kanal- | FT- |
| (XTI) | adapter| BS2000 |
+-----+------+ +-----+---------+
| Ethernet |9632 | DCAM V9 |
+-------------------------------------------+-----+---------+
Leitungsgeschwindigkeit max. 10 Mbit/s
1 Produktbeschreibung
DEC FTSIE (Filetransfer with Siemens Nixdorf) dient zur Datei�ber-
tragung (mit der M�glichkeit der anschlie�enden Folgever-
arbeitung) zwischen SNI-BS2000- und ULTRIX-Systemen unter
Verwendung der ISO/OSI-Protokolle bis zur Transportebene
(Schicht 1 - 4 des ISO/OSI-Referenzmodells) und von SNI genormten
Filetransfer-Protokollen. In den Schichten 5 bis 7 werden
die FTNEA-Protokolle (SN 77309 und SN 77312) von SNI ver-
wendet:
Die Implementierung der OSI-Transportebene wird mit eigener
Dokumentation ausgeliefert.
Die Kopplung des lokalen und der entfernten Rechner kann
�ber ein Paketvermittlungsnetz (PSDN) z.B. DATEX-P erfol-
gen. Im Nahbereich ist die Kopplung auch �ber Modem-Eliminatoren
(X.25) oder Ethernet m�glich (siehe Abbildung Seite 1).
1.1 Beschreibung der Funktionen
- �bertragen einer Datei mit der M�glichkeit einer anschlie�en-
den Folgeverarbeitung. Die Folgeverarbeitung kann im lokalen
System und im Zielsystem erfolgen; es k�nnen eigene Fol-
geverarbeitungen f�r den Fall einer erfolgreichen und
einer nicht erfolgreichen �bertragung angesto�en wer-
den.
- Steuerung der Datei�bertragung: Abbrechen, Anhalten und
automatischer Wiederanlauf nach Unterbrechung.
- Synchrone und asynchrone Auftragsbearbeitung.
Bei der synchronen Daten�bertragung wartet der Auftragge-
ber auf den Abschlu� der �bertragung, beim asynchronen
Betrieb erfolgt ein Eintrag in ein 'Auftragsbuch' (max.
220 Auftr�ge) und die �bertragung wird zeitlich unab-
h�ngig von der Eingabe des Auftraggebers durchgef�hrt.
- Die Initiative zur Datei�bertragung kann sowohl vom lokalen
als auch vom entfernten Rechner ausgehen.
- Datei�bertragung �ber Kommandos auf Shell-Ebene (sowohl
f�r synchronen als auch f�r asynchronen Betrieb).
- �bertragung von Text- und Bin�rdaten.
- Automatische Konvertierung bei �bertragung von Textdateien
von ASCII nach EBCDIC und umgekehrt.
- Simultane Abarbeitung mehrerer Datei�bertragungsauftr�ge.
- Diagnosefunktionen zur �berpr�fung der h�heren Protokolle
durch ein Trace-Auswertungsprogramm.
- Mit folgenden FT-Produkten ist eine Zusammenarbeit m�glich:
- FT-BS2000
- FT-SINIX
Voraussetzung f�r die Kommunikation zweier hetero-
gener FTNEA-Systeme ist, da� auf allen Ebenen des OSI-
Schichtenmodells die einwandfreie Zusammenarbeit zwis-
chen den entsprechenden Instanzen (Peers) gew�hrleis-
tet ist.
Diese Bedingung wird in den Ebenen 5-7 durch die FT-
Produkte erf�llt. F�r die Ebenen 1-4 ist die Funk-
tionalit�t der unterst�tzten Kommunikationsprodukte
ma�geblich.
Mit diesen Einschr�nkungen sind auch �bertragungen
von und zu den folgenden FT-Produkten m�glich:
- FT-MSP (nur X25-Kopplung)
- SNFT
- SINEC FTS (nur Ethernet-Kopplung)
2 Installation
DEC installiert das Softwareprodukt betriebsbereit beim Kun-
den innerhalb der Bundesrepublik Deutschland, sofern die
Installation vereinbarungsgem�� im Preis inbegriffen oder
vom Kunden gesondert in Auftrag gegeben ist. Die verf�g-
baren Installationsdienstleistungen sind in der DEC-Preis-
und -Produktliste aufgef�hrt.
Im Interesse einer einwandfreien Funktion wird dem Kunden
empfohlen, den Installationsservice von Digital Equipment
zu erwerben. Dieser Service umfa�t die Installation des Soft-
wareprodukts durch einen erfahrenen Softwarespezialisten
von Digital Equipment.
3 Mindest-Hardwarekonfiguration
Die VAX-, MicroVAX-, VAXstation-, VAXserver-, DECstation-
, oder DECsystem-Konfigurationen sind in Hardware- und Soft-
wareumgebung (SSA 36.47.00-A) beschrieben.
4 Erforderliche Software
Kommunikationssoftware:
Das Software-Produkt DEC FTSIE for ULTRIX unterst�tzt die
Implementierung der Transportebene durch das Software-Produkt
XTI and OSI Transport for ULTRIX.
HINWEIS
Auf Systemen mit DECnet/OSI for ULTRIX V5.0 kann f�r
die Unterst�tzung von FTSIE das Software-Produkt XTI
and OSI Transport for ULTRIX nicht verwendet werden.
- Bei Unterst�tzung von XTI/OSI Transport ist folgende Soft-
ware erforderlich:
o XTI and OSI Transport for ULTRIX
Bei Unterst�tzung von X.25-Verbindungen ist folgende
Software zus�tzlich erforderlich:
o DECnet ULTRIX bis einschl. Version 4.2
o DEC X.25 ACCESS for ULTRIX
Abh�ngig vom eingesetzten X.25-Connector-Knoten wird
folgendes ben�tigt:
o X25router 2000 oder
o VAX Packetnet System Interface (P.S.I)
Betriebssystem-Software:
F�r Timesharing-Systeme
Betriebssystem ULTRIX V4.2
F�r Workstations
ULTRIX Worksystem Software: UWS
5 Bestellinformation
Die Produktkennung f�r DEC FTSIE f�r VAX ULTRIX ist XNJ und
f�r RISC ULTRIX XNH.
VAX-Systeme:
Softwarelizenz: QL-XNJG*-**
Software-Verteilermedien:
QA-XNJGA-H5
QA-XNJGA-HM
QA-XNJGA-GZ
RISC-Systeme:
Softwarelizenz: QL-XNHG*-**
Software-Verteilermedien:
QA-XNHGA-H5
QA-XNHGA-HM
QA-XNHGA-GZ
* Das Zeichen * steht f�r variable Felder.
6 Softwarelizensierung
F�r dieses Softwareprodukt einschlie�lich Folgeversionen
gelten die Bestimmungen des Abschnitts Softwarelizenz der
Allgemeinen Gesch�ftsbedingungen von Digital Equipment.
7 Unterst�tzung der License Management Facility
Dieses Softwareprodukt unterst�tzt die ULTRIX License Man-
agement Facility (LMF).
Lizenzeinheiten f�r dieses Produkt werden auf der Grund-
lage von CPU-Kapazit�ten vergeben.
N�here Informationen zur License Management Facility finden
Sie in der Software-Produktbeschreibung zu ULTRIX (SPD 26.40.xx)
oder im Handbuch zur License Management Facility, das Be-
standteil der Dokumentation zum Betriebssystem ULTRIX ist.
8 Dienstleistungen
Digital Equipment bietet umfangreiche Software-Dienstleistungs-
pakete an. F�r n�here Informationen wenden Sie sich bitte
an die n�chstgelegene Gesch�ftstelle von Digital Equipment.
9 Gew�hrleistung
Art, Umfang und Dauer der Softwaregew�hrleistung sind in
dem Abschnitt Gew�hrleistung f�r Softwareprodukte der All-
gemeinen Gesch�ftsbedingungen von Digital Equipment geregelt.
10 Customer Support Plan
Dem Kunden obliegt es, gemeinsam mit Digital Equipment einen
Customer Support Plan zu erstellen. Dieser Plan soll alle
Fragen der Einf�hrung, der Installation, der technischen
und organisatorischen Auswirkungen und der weiteren Unter-
st�tzung des Kunden durch Digital Equipment behandeln.
|
| 114.2 | Final SPD - DEC FTSIE for ULTRIX V1.0 | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE | Thu Aug 29 1991 15:13 | 298 |
|
Software
Product
Description
________________________________________________________________
Product Name: DEC FTSIE for ULTRIX, Version 1.0 SPD36.46.00
Filetransfer with SIEMENS NIXDORF
X.25 Remote Connection (only with XTI and OSI
Transport for ULTRIX support)
ULTRIX SNI
BS2000
+----------+ +---------+
|DEC FTSIE | | |
+----------+ PDN | FT- |
| (XTI) | +------+ +----+ | BS2000 |
+----------+ |X.25- | +-----+ +-----+ | | +---------+
|X25 ACCESS+---+Router+---+MODEM+-..-+ +-..-+MODEM+---+X.25+-+ DCAM V9 |
+----------+ +------+ +-----+ | | +-----+ +----+ +---------+
| |
+---+---+--+
| PSDN | Speed max. 48 Kbit/s
|(DATEX-P) |
| |
+----------+
X.25 Local Connection (only with XTI and OSI
Transport for ULTRIX support)
ULTRIX SNI
BS2000
+------------+
| DEC FTSIE | +---------+
+------------+ | FT- |
| (XTI) | PDN | BS2000 |
+------------+ +-------+ +------------------+ +-------+ +---------+
| X25 ACCESS +---+ X.25 +---+ Modem Eliminator +----+ X.25 +---+ DCAM V9 |
+------------+ | Router| +------------------+ +-------+ +---------+
+-------+
Speed max. 48 Kbit/s
Ethernet Connection
ULTRIX SNI
BS2000
+------------+
| DEC FTSIE | +---------+
+------------+ Channel| FT- |
| (XTI) | Adaptor| BS2000 |
+-----+------+ +-----+---------+
| Ethernet |9632 | DCAM V9 |
+-------------------------------------------+-----+---------+
Speed max. 10 Mbit/s
1 Product Description
DEC FTSIE (Filetansfer with Siemens Nixdorf) is a file trans-
fer with postprocessing capabilities, based on ISO/OSI pro-
tocols up to the transport layer (layer 1 to 4 of the ISO/OSI
reference model) and SNI FTNEA protocols (SN 77309 and SN
77312) for layers 5 to 7.
The implementation of the OSI transport layer is available
with separate documentation.
The local and remote systems can be connected via X.25 based
packet switched data network (PSDN) e.g. DATEX-P. The lo-
cal connection can be effected via modem eliminators (X.25)
or via Ethernet (see figure page 1).
1.1 Functionality
- Transferring sequential files from or to a SNI system
synchronously or asynchronously.
- Postprocessing capability, both on the remote and/or on
the local system, both in case of success or failure.
- Controlling the file transfer: Cancel, stop and auto-
matic recovery of file transfer jobs.
- The file transfer can be initiated from the local and
from the remote system.
- File transfer can be effected via commands on shell level
(for synchronous and for asynchronous service).
- Transfer of text and binary files.
- Automatic conversion from ASCII to EBCDIC and vice versa.
- Simultaneous execution of several file transfer requests.
- Protocol trace capability for diagnostic purposes.
- Transfer possibility with the following FT products:
- FT-BS2000
- FT-SINIX
For two heterogenous FTNEA systems to communicate,
it must be guaranteed that the corresponding peers
in each level of the OSI model work together correctly.
This is provided by the FT products themselves in lay-
ers 5, 6 and 7. For layers 1, 2, 3 and 4 this depends
on the communication products supported by each of
the FT products.
Within these constraints transfers with the follow-
ing FT products may also work:
- FT-MSP (X.25 connection only)
- SNFT
- SINEC FTS (Ethernet connection only)
2 Installation
Digital Equipment will instal the software product at the
customer's site within Germany if agreed and included in
the price or if specially ordered by the customer. The avail-
able installation services are described in the Digital price
and procuct list.
In order to guarantee faultless operation of the software,
Digital recommends it's installation service.
3 Hardware Requirements
VAX-, MicroVAX-, VAXstation-, VAXserver-, DECstation-, or
DECsystem configurations as specified in the System Sup-
port Addendum (SSA 36.46.00-A).
4 Software Requirements
Communication Software:
The DEC FTSIE for ULTRIX kit provides transport layer sup-
port for the software product XTI and OSI Transport for UL-
TRIX.
NOTE
On systems running DECnet/OSI for ULTRIX V5.0, the
software product XTI and OSI Transport for ULTRIX can
not be used for FTSIE support.
- The following software is required for support of XTI/OSI
transport:
o XTI and OSI Transport for ULTRIX
The following software is additionally required for
support of X.25 connections:
o DECnet ULTRIX up to and including V4.2
o DEC X.25 ACCESS for ULTRIX
Depending on the X.25 connector node used, the fol-
lowing is required:
o X25router 2000 or
o VAX Packetnet System Interface (P.S.I)
Operating System Software:
For Timesharing Systems
ULTRIX Operating System
For Workstations
ULTRIX Worksystem Software: UWS
5 Ordering Information
The UPI for DEC FTSIE for VAX ULTRIX is XNJ and for RISC
ULTRIX XNH.
VAX-based Systems:
Software License: QL-XNJG*-**
Software Media:
QA-XNJGA-H5
QA-XNJGA-HM
QA-XNJGA-GZ
RISC-based Systems:
Software License: QL-XNHG*-**
Software Media:
QA-XNHGA-H5
QA-XNHGA-HM
QA-XNHGA-GZ
* Denotes variant fields. For additional information on
available licenses, services and media refer to the ap-
propriate price book.
6 Software Licensing
This software is furnished under the licensing provisions
of Digital's Standard Terms and Conditions. For more in-
formation about Digital's licensing terms and policies, con-
tact your local Digital office.
7 License Management Facility Support
This layered product supports the ULTRIX License Manage-
ment Facility (LMF).
License units for this product are allocated on a CPU-capacity
basis.
For more information on the License Management Facility,
refer to the ULTRIX Operating System Software Product De-
scription (SPD 25.40.xx) or the License Management Facil-
ity manual of the ULTRIX Operating System documentation set.
8 Software Product Services
A variety of service options are available from Digital.
For more information, contact your local Digital office.
9 Software Warranty
Warranty for this software product is provided by Digital
with the purchase of a license for the product as defined
in Digital's Standard Terms and Conditions.
10 Customer Support Plan
The customer may make up a Customer Support Plan together
with Digital Equipment in order to clarify any questions
regarding introduction, installation as well as technical
and organizational matters and further support by Digital
Equipment.
|
| 114.4 | Final SSA - DEC FTSIE for ULTRIX V1.0 | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE | Thu Aug 29 1991 15:23 | 199 |
|
1 Hardware Requirements
Processors Supported:
VAX-based Processors
VAX: VAX 6000 Model 200 Series, VAX 6000 Model 300 Se-
ries,
VAX 6000 Model 400 Series, VAX 6000 Model 500 Se-
ries
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500,
VAX 8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700,
VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840
VAX 9000 Model 210, Model 410, & Model 420
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX: Microvax II, Microvax 2000,
MicroVAX 3100, MicroVAX 3300/3400,
MicroVAX 3500, MicroVAX 3600,
MicroVAX 3800, MicroVAX 3900
VAXstation: VAXstation II, VAXstation II/GPX,
VAXstation 2000, VAXstation 3100,
VAXstation 3200, VAXstation 3500,
VAXstation 3520, VAXstation 3540
VAXserver: VAXserver 2000, VAXserver 3100,
VAXserver 3300, VAXserver 3400,
VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800,
VAXserver 3900,
VAXserver 6000 Model 210, VAXserver 6000 Model 220,
VAXserver 6000 Model 310, VAXserver 6000 Model 320,
VAXserver 6000 Model 410, VAXserver 6000 Model 420,
VAXserver 6000 Model 510, VAXserver 6000 Model 520
RISC-based Processors
DECstation: DECstation 2100, DECstation 3100,
DECstation 3100s, DECstation 5000 Model 120/125,
DECstation 5000 Model 120/125CX, DECstation 5000
Model 120/125PX, DECstation 5000 Model 120/125PXG,
DECstation 5000 Model 120/125PXG TURBO, DECstation
5000 Model 200, DECstation 5000 Model 200CX,
DECstation 5000 Model 200PX, DECstation 5000
Model 200PXG, DECstation 5000 Model 200PXG TURBO
DECsystem: DECsystem 3100, DECsystem 5000 Model
100 & Model 200, DECsystem 5100, DECsystem 5400,
DECsystem 5500, DECsystem 5810, DECsystem 5820,
DECsystem 5830, DECsystem 5840
Additionally Required Hardware:
When using DEC X.25 Access for ULTRIX, V2.0, the follow-
ing is required:
A X.25 Connector Node. (This can be a X25router 2000/100
or any VAX configured with P.S.I. in a multi host mode.)
For more information see the Software Product Description
(SPD 26.E6.01), and/or the Software Support Addendum (SSA
26.E6.01-A) for DEC X.25 Access for ULTRIX, V2.0.
Disk Space Required:
VAX-based Systems:
Disk space capacity required for installation:
Root System:/ 0 KByte
Other System/usr 1300 KByte
/var 200 KByte
Disk space capacity required (permanent):
Root System:/ 0 KByte
Other System/usr 1300 KByte
/var 1500-1700 KByte
RISC-based Systeme:
Disk space capacity required for installation:
Root System:/ 0 KByte
Other System/usr 2000 KByte
/var 200 KByte
Disk space capacity required (permanent):
Root System:/ 0 KByte
Other System/usr 2000 KByte
/var 1500-1700 KByte
These counts refer to the disk space required on the sys-
tem disk. The sizes are approximate; actual sizes may vary
depending on the user's system environment, configuration,
and software options.
2 Software Required
Communication Software:
The DEC FTSIE for ULTRIX kit provides transport layer sup-
port for the software product XTI and OSI Transport for UL-
TRIX.
NOTE
On systems running DECnet/OSI for ULTRIX V5.0, the
software product XTI and OSI Transport for ULTRIX can
not be used for FTSIE support.
- The following software is required for support of XTI/OSI
transport:
o XTI and OSI Transport for ULTRIX V1.1 (SPD 34.14.00)
The following software is additionally required for sup-
port of X.25 connections:
o DECnet ULTRIX up to and including V4.2 (SPD 26.83.xx)
o DEC X.25 ACCESS for ULTRIX (SPD 26.E6.01)
Depending on the X.25 connector node used, the follow-
ing is required:
o X25router 2000 (SPD 28.86.01) or
o VAX Packetnet System Interface (P.S.I) (SPD 25.40.xx)
Operating System Software:
For Timesharing Systems
ULTRIX V4.2 Operating System (SPD 26.40.xx)
For Workstations
ULTRIX Worksystem Software: UWS V4.2 (SPD 28.22.xx)
3 Growth Considerations
The minimum hardware and software requirements for future
versions of this product may differ from the values valid
for this version.
4 Distribution Media
Tape : 9-track 1600 BPI Magtape (PE) (VAX processors only),
TK50 Streaming Tape
5 Ordering Information
VAX-based Systems:
Software License: QL-XNJG*-**
Software distribution media:
QA-XNJGA-H5
QA-XNJGA-HM
QA-XNJGA-GZ
RISC-based Systems:
Software License: QL-XNHG*-**
Software distribution media:
QA-XNHGA-H5
QA-XNHGA-HM
QA-XNHGA-GZ
* Denotes variant fields. For additional information on
available licenses, services and media refer to the ap-
propriate price book.
The above information is valid at time of release. Please
contact your local DIGITAL office for most up-to-date in-
formation.
|
| 114.5 | Endg�ltige SSA - DEC FTSIE for ULTRIX V1.0 | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE | Thu Aug 29 1991 15:33 | 219 |
|
1 Hardware-Voraussetzungen
Unterst�tzte Prozessoren:
VAX-Prozessoren
VAX: VAX 6000 Modell 200, VAX 6000 Modell 300,
VAX 6000 Modell 400, VAX 6000 Modell 500,
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500,
VAX 8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700,
VAX 8800, VAX 8810, VAX 8820, VAX 8830, VAX 8840
VAX 9000 Modell 210, 410, 420
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX: Microvax II, Microvax 2000,
MicroVAX 3100, MicroVAX 3300/3400,
MicroVAX 3500, MicroVAX 3600,
MicroVAX 3800, MicroVAX 3900
VAXstation: VAXstation II, VAXstation II/GPX,
VAXstation 2000, VAXstation 3100,
VAXstation 3200, VAXstation 3500,
VAXstation 3520, VAXstation 3540
VAXserver: VAXserver 2000, VAXserver 3100,
VAXserver 3300, VAXserver 3400,
VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800, VAXserver 3900,
VAXserver 6000 Modell 210, VAXserver 6000 Modell 220,
VAXserver 6000 Modell 310, VAXserver 6000 Modell 320,
VAXserver 6000 Modell 410, VAXserver 6000 Modell 420,
VAXserver 6000 Modell 510, VAXserver 6000 Modell 520
RISC-Prozessoren
DECstation: DECstation 2100, DECstation 3100,
DECstation 3100s,
DECstation 5000 Modell 120/125,
DECstation 5000 Modell 120/125CX,
DECstation 5000 Modell 120/125PX,
DECstation 5000 Modell 120/125PXG,
DECstation 5000 Modell 120/125PXG TURBO,
DECstation 5000 Modell 200,
DECstation 5000 Modell 200CX,
DECstation 5000 Modell 200PX,
DECstation 5000 Modell 200PXG,
DECstation 5000 Modell 200PXG TURBO
DECsystem: DECsystem 3100, DECsystem 5000 Modell 100
& Modell 200, DECsystem 5100, DECsystem 5400,
DECsystem 5500, DECsystem 5810, DECsystem 5820,
DECsystem 5830, DECsystem 5840
Zus�tzlich erforderliche Hardware:
Beim Einsatz mit DEC X.25 Access for ULTRIX, V2.0 ist ein
X.25-Connector-Knoten erforderlich.
Dabei kann es sich um einen X25router 2000/100 oder jede
beliebige im Multi-Host-Modus konfigurierte VAX mit P.S.I.
handeln.
N�here Informationen dazu finden Sie in der Software Prod-
uct Description (SPD 26.E6.01), bzw. im Software Support
Addendum (SSA 26.E6.01-A) zu DEC X.25 Access for ULTRIX,
V2.0.
Erforderlicher Plattenplatz:
VAX-Systeme:
Erforderliche Plattenspeicherkapazit�t f�r die Installa-
tion:
Root-System: / 0 KByte
Andere Systeme: /usr 1300 KByte
/var 200 KByte
Erforderliche Plattenspeicherkapazit�t (permanent):
Root-System: / 0 KByte
Andere Systeme: /usr 1300 KByte
/var 1500-1700 KByte
RISC-Systeme:
Erforderliche Plattenspeicherkapazit�t f�r die Installa-
tion:
Root-System: / 0 KByte
Andere Systeme: /usr 2000 KByte
/var 200 KByte
Erforderliche Plattenspeicherkapazit�t (permanent):
Root-System: / 0 KByte
Andere Systeme: /usr 2000 KByte
/var 1500-1700 KByte
Diese Angaben beziehen sich auf den Speicherplatz, der auf
der Systemplatte ben�tigt wird und sind lediglich N�herungswerte.
Der im Einzelfall erforderliche Speicherplatz h�ngt von der
jeweiligen Systemumgebung, der Konfiguration sowie zus�tz-
licher Software ab.
2 Erforderliche Software
Kommunikationssoftware:
Das Software-Produkt DEC FTSIE for ULTRIX unterst�tzt die
Implementierung der Transportebene durch das Software-Produkt
XTI and OSI Transport for ULTRIX.
HINWEIS
Auf Systemen mit DECnet/OSI for ULTRIX V5.0 kann f�r
die Unterst�tzung von FTSIE das Software-Produkt XTI
and OSI Transport for ULTRIX nicht verwendet werden.
- Bei Unterst�tzung von XTI/OSI Transport ist folgende Soft-
ware erforderlich:
o XTI and OSI Transport for ULTRIX V1.1 (SPD 34.14.00)
Bei Unterst�tzung von X.25-Verbindungen ist folgende
Software zus�tzlich erforderlich:
o DECnet ULTRIX bis einschlie�lich Version 4.2 (SPD 26.83.xx)
o DEC X.25 ACCESS for ULTRIX (SPD 26.E6.01)
Abh�ngig vom eingesetzten X.25-Connector-Knoten wird
folgendes ben�tigt:
o X25router 2000 (SPD 28.86.01) oder
o VAX Packetnet System Interface (P.S.I) (SPD 25.40.xx)
Betriebssystem-Software:
F�r Timesharing-Systeme
Betriebssystem ULTRIX V4.2 (SPD 26.40.xx)
F�r Workstations
ULTRIX Worksystem Software: UWS V4.2 (SPD 28.22.xx)
3 K�nftiger Bedarf
Die Mindest-Hardware- und Softwareerfordernisse f�r zuk�n-
ftige Versionen dieses Produkts k�nnen von den f�r diese
Version g�ltigen Werten abweichen.
4 Verteilermedien
Magnetbandkassette TK50, Magnetband 1600 BPI (nur VAX-Prozessoren)
5 Bestellinformation
VAX-Systeme:
Softwarelizenz: QL-XNJG*-**
Software-Verteilermedien:
QA-XNJGA-H5
QA-XNJGA-HM
QA-XNJGA-GZ
RISC-Systeme:
Softwarelizenz: QL-XNHG*-**
Software-Verteilermedien:
QA-XNHGA-H5
QA-XNHGA-HM
QA-XNHGA-GZ
* Das Zeichen * steht f�r variable Felder.
Diese Informationen sind g�ltig zum Zeitpunkt des Erscheinens
der vorliegenden Version. F�r aktuellere Informationen wen-
den Sie sich bitte an die n�chstgelegene Gesch�ftstelle von
Digital Equipment.
|
| 114.7 | Prerequisite Software - DEC X25 ACCESS for ULTRIX V2 | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE and Interleaf | Mon Oct 14 1991 16:17 | 522 |
|
SOFTWARE PRODUCT DESCRIPTION
Product Name: DEC X.25 Access for ULTRIX, Version 2.0 SPD 26.E6.01
DESCRIPTION
DEC X.25 Access for ULTRIX is a layered ULTRIX software product which allows an
ULTRIX/UWS system to connect to an X.25 network. It provides the following
functions:
- Support for TCP/IP over an X.25 network. This allows an ULTRIX/UWS system
to transmit IP datagrams over an X.25 network to:
* A remote ULTRIX system providing the same IP-X.25 capability
* Any system supporting TCP/IP protocols providing the same IP-X25
capability.
DEC X.25 Access for ULTRIX implements the Internet Specification "Request
For Comments" (RFC) 877 which specifies how to transport IP messages over
an X.25 network.
- An Application Programming Interface, which allows user applications or
third party software to be used over X.25 networks.
- X.29 server capability. This allows remote terminals connected to a
Packet Switched Data Network (PSDN), via a PAD, to connect to an ULTRIX
system.
- A PAD facility to allow ULTRIX users to communicate with remote Data
Terminal Equipment (DTEs) over a PSDN.
The connection is made via Ethernet to an X.25 connector node which performs
the actual connection to the X.25 network. This X.25 connector node can be one
of the following:
* An X25router 2000
* An X25router 100
* Any VAX running VAX Packetnet System Interface (VAX P.S.I.) configured
in multi-host mode.
For each virtual circuit, a DECnet session is opened between the ULTRIX host
and the X.25 connector node.
SUPPORT for TCP/IP over an X.25 NETWORK
---------------------------------------
The TCP/IP support over X.25, provided by DEC X.25 Access for ULTRIX, allows
the following applications to communicate with other ULTRIX/UNIX systems over
an X.25 network:
- The standard Arpanet applications which use the TCP/IP protocols (Telnet,
FTP, SMTP)
- The Berkeley BSD "r" commands such as rlogin, rsh, ...
- Any user application using the Internet domain socket interface.
From the viewpoint of routing, the X.25 network is seen by the ULTRIX/UWS
system (hereafter referred to as an IP-X25 gateway) as one communication
interface.
This interface must be assigned a specific Internet address. Therefore, the
IP-X25 gateway must be configured as an Internet gateway by the system manager.
All the IP traffic coming from the local LAN will be routed to remote systems
through the IP-X25 gateway according to its internal routing table.
Remote systems can be
* Systems directly connected to the X.25 network
* Systems reachable through an Internet gateway connected to the X.25
network.
All the systems directly connected to the X.25 network must have the same
subnet address.
In order to accept incoming calls from a remote system, the IP-X25 gateway must
be declared as a DECnet object (that is, a new destination in the X25-server
module) in the X.25 connector node. More than one IP-X25 gateway can coexist on
the same LAN provided they are declared as different DECnet objects in the X.25
connector node.
Configuration file
------------------
The mapping of remote IP addresses to remote DTE addresses is declared in a
configuration file. This file contains a static definition of all the circuits
which can be used. This definition includes the various parameters to be used
when issuing a call request (such as network name, X.25 connector name,
closing timeout, facility field to be sent, user data to be sent) and the
various parameters used to validate an incoming call (such as incoming DTE
address, subaddress, incoming user data).
The ASCII configuration file can be edited by standard editors (for example,
vi).
Management
----------
A management utility allows the system manager to establish or clear virtual
circuits. It also gives some information about the state and the counters of
the declared circuits.
Tracing
-------
A tracing utility allows a system manager to store in a disk file:
- The level 2 X.25 traffic
- The level 3 X.25 traffic
- The GAP messages within the X.25 connector node (GAP is the protocol
used between the IP-X25 gateway and the X.25 connector node).
The trace output can be displayed on the screen or directed to a file.
VIRTUAL CIRCUIT MANAGEMENT
A virtual circuit is opened when an IP datagram is transmitted to a remote DTE
that is not yet connected, or when a remote system asks for a connection.
They may also be opened by initiating a call from the Management Utility.
Virtual circuits are closed down after a certain period of inactivity (the
timer is configurable on a per circuit basis).
Secure access to or from the IP-X25 gateway relies on:
- The X.25 connector node setting
- The IP-X25 gateway configuration file setting.
Incoming calls are first filtered at the X.25 connector node using the called
DTE subaddress and/or the userdata field and/or the extended address. They are
then filtered by the IP-X25 gateway according to the parameters of the
corresponding circuit, as defined in the IP-X25 configuration file.
Facilities requested in incoming call requests are not processed by the IP-X25
gateway.
Facilities requested in an outgoing call request can be set on a per circuit
basis in the IP-X25 configuration file.
APPLICATION PROGRAMMING INTERFACE
---------------------------------
DEC X.25 Access for ULTRIX supports access for ULTRIX user programs
written in C for the VAX C, VAX CC or MIPS CC compilers.
The DEC X.25 Access for ULTRIX programming interface allows application
programs to access the service interface to the packet level via a
library of routines. Functions include
- The setting up and breaking of network connections
- Data transmission and reception
- Sending and receiving of interrupt messages
- Resetting of virtual circuits.
The Programming Interface also provides for the splitting and recombining of
messages which are longer than the packet size selected for the circuit.
This interface enables an application program to communicate with complementary
software on other systems (Digital or non-Digital) accessible via the
X.25 connection.
X.29 SERVER and PAD CAPABILITY
------------------------------
Remote terminals connected to an X.25 network may access the ULTRIX host,
running DEC X.25 Access for ULTRIX, by means of an X.25 Packet Assembly
Disassembly (PAD) capability.
Users of the ULTRIX host may make outgoing calls, using the host-based PAD
supplied with DEC X.25 Access for ULTRIX, to other DIGITAL or non-DIGITAL CPUs,
or to suitable network PADs accessible via the X.25 network or networks.
The host-based PAD employs a shell-like command syntax, offering the ability
to reference the CCITT PAD parameters symbolically, as well as an interface
that conforms to the standard CCITT command signals.
Terminal Communications
-----------------------
DEC X.25 Access for ULTRIX supports terminal communications according to CCITT
recommendations X.3, X.28, and X.29.
Only those terminal parameters defined in the X.3 recommendation are
explicitly supported; network-specific enhancements or extensions to the
X.3 parameters are available at both the X.29 and the host-based PAD user
interface.
Terminal processes that depend on these extensions may cause problems
when used on other PSDNs or when accessing one PSDN via another (for
example, international access).
- Outgoing terminal traffic
Using the Host-Based Packet Assembly/Disassembly (PAD) facility, terminals
connected locally (logically or physically) to the UTRIX system may
communicate with remote DTEs over the PSDN(s). Such terminals may connect
to remote DTEs in a manner identical to the way in which remote terminals
can connect over a PSDN.
- Incoming terminal traffic
DEC X.25 Access for ULTRIX allows remote asynchronous terminals
(character-mode DTEs) connected to the network to communicate with the ULTRIX
system in a manner similar to local terminals.
Dissimilarities may appear as a result of delays caused by the PSDN(s) and the
various PAD parameter settings chosen by the user or peculiar to the PSDN(s).
In this case, the remote PAD must perform code conversions between ASCII and
the code the terminal uses. (There may be some restrictions imposed by the
PSDN(s) itself.)
The interface an X.29 terminal uses is compatible with the interface a local
terminal uses, except for those facilities where the PSDN does not provide
adequate support. The X.29 interface includes support for specific X.29
signaling. For example, the break key can be used to disable output, and the
interrupt message can be mapped directly to the ULTRIX interrupt character.
LIMITATIONS
- IP broadcast messages are not sent over virtual circuits.
- One IP-X25 gateway can connect to only one X.25 connector node.
- One IP-X25 gateway can access only one X.25 network.
Several IP-X25 gateways can be configured on the same Ethernet (in the case
where access to several X.25 connector nodes or several X.25 networks is
required). These restrictions concern only the IP-X25 gateway and they do not
exist for the application programming interface and the X.29 server and PAD.
- Permanent circuits are not supported.
- There are no X.25 Accounting capabilities.
- The application programming interface supports up to 62 virtual circuits
in total per process.
- The IP-X25 gateway supports up to 59 virtual circuits at a time.
- Up to 62 Incoming terminal connections at the same time are
supported.
- The tracing utility cannot analyze the X.25 Level 2 Extended format.
- The X.25 level 3 trace is provided in a dump format only.
- The tracing utility can trace only X25router activity. If VAX P.S.I. has
to be traced, the VMS NETTRACE utility can be used.
- All ULTRIX applications which might use broadcasting features, or which
could be impacted by timing problems or loss of IP messages are NOT
SUPPORTED (such as NFS, BIND, YP, rwho, ruptime).
- DECwindows over X.25 is not supported.
SOURCE CODE INFORMATION
No source kit is available
HARDWARE REQUIREMENTS
VAX, MicroVAX, VAXstation, VAXserver, DECsystem or DECstation configuration as
specified in the System Support Addendum (SSA 26.E6.01-A).
SOFTWARE REQUIREMENTS
For Systems Using Terminals:
^ ULTRIX-32 Operating System
^ DECnet-ULTRIX
For Workstations:
^ ULTRIX Worksystem Software
^ DECnet-ULTRIX
Refer to the ULTRIX-32 Software Cross Reference Table or the System Support
Addendum (SSA 26.E6.01-A) for availability and versions of required software.
ORDERING INFORMATION
VAX-Based Systems
Software Licenses: QL-YP3E*-**
Software Media: QA-YP3EA-**
Software Documentation: QA-YP3EA-GZ
Software Product Services: QT-YP3E*-**
RISC-Based Systems
Software Licenses: QL-YP3E*-**
Software Media: QA-YP3EB-**
Software Documentation: QA-YP3EA-GZ
Software Product Services: QT-YP3E*-**
* Denotes variant fields. For additional information on available
licenses, services and media, refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of Digital
Equipment Corporation's Standard Terms and Conditions. For more
information about Digital's licensing terms and policies, contact your
local Digital office.
License Management Facility Support
-----------------------------------
This layered product does not support the ULTRIX License Management Facility.
For more information on the License Management Facility, refer to the ULTRIX
Operating System Software Product Description (SPD 26.40.xx) or the Guide to
Software Licensing in the ULTRIX Operating System documentation set.
SOFTWARE PRODUCT SERVICES
A variety of service options are available from Digital. For more
information, contact your local Digital office.
SOFTWARE WARRANTY
Warranty for this software product is provided by Digital with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation.
(TM) VAX, VMS, MicroVAX, VAXstation, VAXserver, VAXcluster, ULTRIX,
ULTRIX-32, DECstation, DECsystem and DECnet are trademarks of Digital
Equipment Corporation.
August 1990
AE-PCJXB-TE
SYSTEM SUPPORT ADDENDUM
Product Name: DEC X.25 Access for ULTRIX, Version 2.0 SSA 26.E6.01-A
HARDWARE REQUIREMENTS
Processors Supported
--------------------
VAX-Based Processors:
VAX :
VAX 6000-210, VAX 6000-220, VAX 6000-230, VAX 6000-240, VAX 6000-310,
VAX 6000-320, VAX 6000-330, VAX 6000-340, VAX 6000-350, VAX 6000-360,
VAX 6000-410, VAX 6000-420, VAX 6000-430, VAX 6000-440, VAX 6000-450,
VAX 6000-460
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550,
VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830,
VAX 8840
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3100, MicroVAX 3300,
MicroVAX 3400, MicroVAX 3500, MicroVAX 3600, MicroVAX 3800,
MicroVAX 3900
VAXstation :
VAXstation II, VAXstation II/GPX, VAXstation 2000, VAXstation 3100,
VAXstation 3200, VAXstation 3500, VAXstation 3520, VAXstation 3540
VAXserver :
VAXserver 100, VAXserver 2000, VAXserver 3100, VAXserver 3300,
VAXserver 3400, VAXserver 3500, VAXserver 3600, VAXserver 3602,
VAXserver 3800, VAXserver 3900
VAXserver 6000-210, VAXserver 6000-220, VAXserver 6000-230, VAXserver 6000-240,
VAXserver 6000-310, VAXserver 6000-320, VAXserver 6000-330, VAXserver 6000-340,
VAXserver 6000-350, VAXserver 6000-360, VAXserver 6000-410, VAXserver 6000-420,
VAXserver 6000-430, VAXserver 6000-440, VAXserver 6000-450, VAXserver 6000-460
RISC-Based Processors:
DECstation :
DECstation 2100, DECstation 3100, DECstation 3100s, DECstation 5000 Model 200,
DECstation 5000 Model 200CX, DECstation 5000 Model 200PX
DECsystem :
DECsystem 3100, DECsystem 5000 Model 200, DECsystem 5400, DECsystem 5810,
DECsystem 5820, DECsystem 5830, DECsystem 5840
Other Hardware Required
-----------------------
An X.25 connector node is needed. This could be an X25router 2000/100 or
any VAX running P.S.I. configured in multi-host mode. Note that Digital
requires that a customer's first purchase of the corresponding software
products includes Digital Installation Services. These services provide for
installation of the software product by an experienced DIGITAL Software
Specialist.
Only customers experienced with DIGITAL's X.25 products should attempt second
or subsequent installations. DIGITAL recommends that all other customers
purchase DIGITAL's Installation Services.
Special packages are offered. Some packages include the DEC X.25 Access
for ULTRIX software and both prerequisite Hardware and Software
necessary to run it. Contact your local Digital office for further
information.
Disk Space Requirements
-----------------------
For VAX-Based Systems:
Disk space required for installation:
^ Root file system: / 2000 Kbytes
^ Other file systems:
/usr 500 Kbytes
/var 500 Kbytes
Disk space required for use (permanent):
^ Root file system: / 1000 Kbytes
^ Other file systems:
/usr 500 Kbytes
/var 500 Kbytes
For RISC-Based Systems:
Disk space required for installation:
^ Root file system: / 5000 Kbytes
^ Other file systems:
/usr 1000 Kbytes
/var 1000 Kbytes
Disk space required for use (permanent):
^ Root file system: / 2500 Kbytes
^ Other file systems:
/usr 1000 Kbytes
/var 1000 Kbytes
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's system
environment, configuration, and software options.
SOFTWARE REQUIREMENTS
DECnet-ULTRIX V4.0 (SPD 26.83.08)
Depending on the X.25 connector node: X25router 2000 V1.1 (SPD 28.86.01)
or VAX Packetnet System Interface (P.S.I.) V4.3 (SPD 25.40.xx)
For Timesharing Systems
-----------------------
ULTRIX-32 Operating System: ULTRIX V4.0 (SPD 26.40.19)
For Workstations
----------------
ULTRIX Worksystem Software: UWS V4.0 (SPD 28.22.13)
Special packages are offered. Some packages include the DEC X.25 Access
for ULTRIX software and both the prerequisite hardware and software
necessary to run it. Contact your local Digital office for further
information.
GROWTH CONSIDERATIONS
The minimum hardware/software requirements for any future version of
this product may be different from the minimum requirements for the
current version.
DISTRIBUTION MEDIA
TK50 Streaming Tape, 9-Track 1600 BPI Magtape (VAX processors only)
ORDERING INFORMATION
VAX-Based Systems
Software Licenses: QL-YP3E*-**
Software Media: QA-YP3EA-**
Software Documentation: QA-YP3EA-GZ
Software Product Services: QT-YP3E*-**
RISC-Based Systems
Software Licenses: QL-YP3E*-**
Software Media: QA-YP3EB-**
Software Documentation: QA-YP3EA-GZ
Software Product Services: QT-YP3E*-**
* Denotes variant fields. For additional information on available
licenses, services and media, refer to the appropriate price book.
The above information is valid at time of release. Please contact your
local Digital office for the most up-to-date information.
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation.
(TM) VAX, VMS, MicroVAX, VAXstation, VAXserver, VAXcluster, ULTRIX,
ULTRIX-32, DECstation, DECsystem and DECnet are trademarks of Digital
Equipment Corporation.
August 1990
AE-PCJYB-TE
|
| 114.8 | XTI/OSI Transport V1.1 - SPD | MUNLEG::GOETZ | Ulrike G�tz, Product Manager FTSIE and Interleaf | Tue Apr 07 1992 16:12 | 451 |
| SOFTWARE PRODUCT DESCRIPTION
PRODUCT NAME: XTI and OSI Transport for ULTRIX, Version 1.1 SPD: 34.14.01
DESCRIPTION
XTI and OSI Transport for ULTRIX is a Digital Distributed Software (DDS)
product for ULTRIX/UWS systems. It is based on the OSIAM_C product developed
by MARBEN and provides the following functions:
- A user interface to OSI Transport Layer functions via a library conforming
to the X/Open Transport Interface (XTI). This interface is described in the
X/Open Portability Guide Version 3 (XPG3), Volume 7, Networking Services.
- OSI Transport Layer software conforming to ISO standards 8072 and 8073,
providing classes 0,2,4 over a Connection Oriented Network Service (CONS),
and class 4 over a Connection-Less Network Service (CLNS).
Features include:
- TPDU size from 128 bytes to 8 kbytes.
- Data Transfer Optimization.
- User data in connection and disconnection phases.
- Infinite TSDU supported.
- Implicit or explicit flow control in class 2.
- Quality of service parameters.
- Connection Oriented Network Service (CONS), conforming to ISO standards
8878 and 8208. This supports networks conforming to either X.25(80) or
X.25(84).
If access to the X.25 network is required, then DEC X.25 Access for ULTRIX,
Version 2.0 must be installed as a pre-requisite. This product provides
connection, via Ethernet, to an X.25 connector node which performs the
actual connection to the X.25 network.
This X.25 connector node can be one of the following:
- An X25router 2000
- An X25router 100
- Any VAX running VAX Packetnet System Interface (VAX P.S.I.) configured
in multi-host mode.
- Connection-Less Network Service (CLNS), as defined by the Internet Protocol
(ISO 8473). This protocol supports the following functions:
- All subsets (but only one at a time): Inactive Network Layer protocol,
Non-segmenting protocol and Full protocol.
- Connection over LAN using Logical Link Control (ISO 8802/2) over Ethernet
(ISO 8802/3). Access to Ethernet is implemented via the Data Link
Interface (DLI) provided with the ULTRIX operating system.
- Connection over WAN, using X.25 Packet Level Protocol (ISO 8208) over an
X.25 network (ISO 7776).
- The ES to IS routing exchange protocol (ISO 9542). In OSIAM_C, this is
implemented in two parts:
1. The ES to IS protocol, which provides a method of dynamically
updating routing information.
2. A Routing Information Base (RIB), and associated management commands,
which holds all routing information. In addition to ES/IS and LAN
operation, the RIB is also used for storing routing information for
IP over X.25 and CONS.
Since IP is implemented over Ethernet and X.25, this provides a LAN/WAN
gateway using CLNS.
Note:
The following functions are not supported but can be made available to
a customer on a project basis (please refer to your local sales
representative):
- Transport Relay known as Multi System Distributed System Gateway (MSDSG).
This provide a Transport LAN/WAN Gateway that can connect a CONS transport
user to a CLNS transport user and vice-versa.
This gateway is based on the MAP and TOP recommendations for CONS/CLNS
internetworking.
- Transport class 3 over Connection Oriented Network Services (CONS)
XTI Library
-----------
The XTI library is a procedure-call implementation.
All the mandatory functions are provided:
Function Description
-------- -----------
t_accept() accept a connect request
t_bind() bind an address to a transport endpoint
t_close() close a transport endpoint
t_connect() establish a connection with another transport user
t_listen() listen for a connect request
t_look() look at the current event on a transport endpoint
t_open() establish a transport endpoint
t_rcv() receive normal or expedited data
t_rcvconnect() receive confirmation from a connect request
t_rcvdis() retrieve information from disconnect
t_snd() send normal or expedited data
t_snddis() send disconnect request
t_sync() synchronise transport library
t_unbind() disable a transport endpoint
The following optional functions are provided:
Function Description
-------- -----------
t_alloc() allocate a library structure
t_error() produce an error message
t_free() free a library structure
The following optional functions are not provided:
Function Description
-------- -----------
t_getinfo() get protocol-specific service information
t_getstate() get the current state
t_optmgmt() manage options for a transport endpoint
t_rcvudata() connectionless transport function
t_rcvuderr() connectionless transport function
t_sndudata() connectionless transport function
t_sndrel() orderly release function
t_rcvrel() orderly release function
Since the XTI library is implemented in user space, the parameter `fd' returned
by the t_open function is not a real file descriptor, but rather a variable
identifying the transport end-connection. This restriction can have a
significant impact on the way in which an application is developed, since it
means that the following standard Ultrix functions cannot be used with the `fd'
provided by t_open:
dup()
open()
close()
fcntl()
Although `fd' is not a file descriptor, it will still be inherited (like
any other variable) by a child process after a fork() system call. In this
way, the child process can share the `fd' with its parent, but it is the user's
responsibility to synchronise access.
To alleviate the above problem, two extra routines have been provided:
Function Description
-------- -----------
t_fcntl() simulates fcntl() for an XTI file descriptor
t_fork() performs a standard fork() function and child process
synchronisation; used before exec() to save the XTI context
Event Management:
Each call to an XTI routine will generate a request to the Transport layer
which will answer either:
1. synchronously, which means that the call will only return when an event
arrives.
2. asynchronously, which means that the return will be immediate, even if no
events are available. It will then be the responsibility of the application
to look for events.
The asynchronous monitoring of events can be done using the additional
function:
Function Description
-------- -----------
t_genlook() looks at the current event on several transport endpoints
LIMITATIONS
The maximum number of simultaneous X.25 virtual circuits varies depending upon
the customer configuration. With a full configuration of four X.25 lines, IP
over X.25 and two applications using the XTI library, a typical maximum would
be of the order of 50 virtual circuits.
INSTALLATION
The software is customer installable, but the customer is recommended to
contact DIGITAL for the first installation.
HARDWARE REQUIREMENTS
VAX, MicroVAX, VAXstation, VAXserver, DECstation, or DECsystem configuration
as specified in the System Support Addendum (SSA 34.14.00-A).
SOFTWARE REQUIREMENTS
For Timesharing Systems:
ULTRIX Operating System (SPD 26.40.xx)
For Workstations:
ULTRIX Worksystem Software (SPD 28.22.xx)
Refer to the System Support Addendum (SSA 34.14.00-A) for availability and
versions of required software.
If X.25 connection is required, then:
DECnet-ULTRIX (SPD 26.83.xx)
DEC X.25 Access for ULTRIX (SPD 26.E6.xx)
Depending on the X.25 connector node: X25router 2000 (SPD 28.86.01)
or VAX Packetnet System Interface (P.S.I.) (SPD 25.40.xx)
ORDERING INFORMATION
VAX-Based Systems
Software Licenses: QL-GHGA*-**
Software Media: QA-GHGA*-**
Software Documentation: QA-GHFAA-GZ
Software Product Services: QT-GHGA*-**
RISC-Based Systems
Software Licenses: QL-GHFA*-**
Software Media: QA-GHFA*-**
Software Documentation: QA-GHFAA-GZ
Software Product Services: QT-GHFA*-**
* Denotes variant fields. For additional information on available licenses,
services and media refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of DIGITAL's
Standard Terms and Conditions. For more information about DIGITAL's licensing
terms and policies, contact your local DIGITAL office.
LICENSE MANAGEMENT FACILITY SUPPORT
This layered product does not support the Ultrix License Management Facility.
For more information on the License Management Facility, refer to the ULTRIX
Operating System Software Product Description (SPD 26.40.xx) or the Guide to
Software Licensing in the ULTRIX Operating System documentation set.
For more information about DIGITAL's licensing terms and policies,
contact your local DIGITAL office.
SOFTWARE PRODUCT SERVICES
A variety of service options are available from DIGITAL. For more information,
contact your local DIGITAL office.
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL with the purchase of
a license for the product as defined in the Software Warranty Addendum of this
SPD.
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation.
(TM) VAX, VMS, MicroVAX, VAXstation, VAXserver, VAXcluster, ULTRIX,
ULTRIX-32, DECstation, DECsystem and DECnet are trademarks of Digital
Equipment Corporation.
OSIAM_C is a trademark of MARBEN PRODUIT.
March 1991
AE-PFLLB-TE
SYSTEM SUPPORT ADDENDUM
PRODUCT NAME: XTI and OSI Transport for ULTRIX, Version 1.1 SSA: 34.14.01-A
HARDWARE REQUIREMENTS
Processors Supported:
VAX-Based Processors:
VAX :
VAX 6000-210, VAX 6000-220, VAX 6000-230, VAX 6000-240,
VAX 6000 Model 300 Series, VAX 6000 Model 400 Series,
VAX 6000 Model 500 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550,
VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830,
VAX 8840
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3100, MicroVAX 3300/3400,
MicroVAX 3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation :
VAXstation II, VAXstation II/GPX, VAXstation 2000, VAXstation 3100,
VAXstation 3200, VAXstation 3500, VAXstation 3520/3540
VAXserver :
VAXserver 100, VAXserver 2000, VAXserver 3100, VAXserver 3300/3400,
VAXserver 3500, VAXserver 3600/3602, VAXserver 3800, VAXserver 3900
VAXserver 6000-210, VAXserver 6000-220, VAXserver 6000-310,
VAXserver 6000-320, VAXserver 6000-410, VAXserver 6000-420,
RISC-Based Processors:
DECstation :
DECstation 2100, DECstation 3100, DECstation 3100s, DECstation 5000 Model 200,
DECstation 5000 Model 200CX, DECstation 5000 Model 200PX, DECstation 5000
Model 200PXG, DECstation 5000 Model 200PXG TURBO
DECsystem :
DECsystem 3100, DECsystem 5000 Model 200, DECsystem 5100, DECsystem 5400,
DECsystem 5500, DECsystem 5810, DECsystem 5820, DECsystem 5830, DECsystem 5840
Processor Restriction
A TK50 Tape Drive is required for standalone MicroVax 2000 and
VAXstation 2000 systems.
Other Hardware Required:
If access to the X.25 network is required, then an X.25 connector node is
needed. This could be an X25router 2000/100 or any VAX running P.S.I.
configured in multi-host mode. Please refer to the DEC X.25 Access for
ULTRIX hardware requirements (SPD 26.E6.xx).
Note that Digital requires that a customer's first purchase of the
corresponding software products includes Digital Installation Services.
These services provide for installation of the software product by an
experienced DIGITAL Software Specialist.
Only customers experienced with DIGITAL's X.25 products should attempt second
or subsequent installations. DIGITAL recommends that all other customers
purchase DIGITAL's Installation Services.
Disk Space Requirements
For VAX-Based Systems:
Disk space required for installation:
^ Root file system: / 0 Kbytes
^ Other file systems:
/usr 2500 Kbytes
/var 0 Kbytes
Disk space required for use (permanent):
^ Root file system: / 0 Kbytes
^ Other file systems:
/usr 2500 Kbytes
/var 0 Kbytes
For RISC-Based Systems:
Disk space required for installation:
^ Root file system: / 0 Kbytes
^ Other file systems:
/usr 2500 Kbytes
/var 0 Kbytes
Disk space required for use (permanent):
^ Root file system: / 0 Kbytes
^ Other file systems:
/usr 2500 Kbytes
/var 0 Kbytes
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's system
environment, configuration, and software options.
SOFTWARE REQUIREMENTS
For Timesharing Systems :
ULTRIX Operating System: V4.0, V4.1 (SPD 26.40.xx)
For Workstations:
ULTRIX Worksystem Software: V4.0, V4.1 (SPD 28.22.xx)
If X.25 connection is required, then:
DECnet-ULTRIX V4.0 (SPD 26.83.xx)
DEC X.25 Access for ULTRIX Version 2.0 (SPD 26.E6.xx)
Depending on the X.25 connector node: X25router 2000 V1.1 (SPD 28.86.01)
or VAX Packetnet System Interface (P.S.I.) V4.3 (SPD 25.40.xx)
GROWTH CONSIDERATIONS
The minimum hardware/software requirements for any future version of this
product may be different from the minimum requirements for the current version.
DISTRIBUTION MEDIA
TK50 Streaming Tape, 9-track 1600 BPI Magtape (VAX Processors only)
ORDERING INFORMATION
VAX-Based Systems:
Software Licenses: QL-GHGA*-**
Software Media: QA-GHGA*-**
Software Documentation: QA-GHFAA-GZ
Software Product Services: QT-GHGA*-**
RISC-Based Systems:
Software Licenses: QL-GHFA*-**
Software Media: QA-GHFA*-**
Software Documentation: QA-GHFAA-GZ
Software Product Services: QT-GHFA*-**
* Denotes variant fields. For additional information on available licenses,
services and media refer to the appropriate price book.
The above information is valid at time of release. Please contact your
local DIGITAL office for the most up-to-date information.
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation.
(TM) VAX, VMS, MicroVAX, VAXstation, VAXserver, VAXcluster, ULTRIX,
ULTRIX-32, DECstation, DECsystem and DECnet are trademarks of Digital
Equipment Corporation.
OSIAM_C is a trademark of MARBEN PRODUIT.
March 1991
AE-PFLMB-TE
|