| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 21.1 | Deutsche SPD VAX FTSIE 1.3 | ECCGY4::STROHMAIER | | Wed May 31 1989 11:35 | 369 |
| AE-JY95D-TE
Februar 1989
-----------------------------------------------------------------------------
Software Version 1.3
Produkt
Beschreibung
-----------------------------------------------------------------------------
VAX FTSIE Version 1.3 SPD-Nr. C0.92.03
Datei�bertragung VMS - SIEMENS/BS2000
Produktbeschreibung
VAX FTSIE (File Transfer with SIEMENS) dient zur Datei�bertragung (mit der
M�glichkeit der anschlie�enden Folgeverarbeitung) zwischen SIEMENS/BS2000- und
VMS-Systemen unter Verwendung der ISO/OSI-Protokolle bis zur Transportebene
(Schicht 1 - 4) und von SIEMENS genormter File-Transfer-Protokolle. Die
verwendeten SIEMENS-Protokolle f�r die Anwendungsschichten 5 bis 7 sind:
- FJAM-BS2000 (File Job Access Method)
- NDMS-BS2000 (Network Data Management System)
- DAS-BS2000 (Data Access Services)
Die Implementierung der OSI-Transportebene wird als Teil von VAX FTSIE auf
getrenntem Medium und mit eigener Dokumentation als VOTS V 2.0 (VAX OSI
Transport Service) ausgeliefert. Hier wird das "Programming Interface" nicht
unterst�tzt.
Die Kopplung des lokalen und des entfernten Rechners kann �ber das Paketver-
mittlungsnetz DATEX-P erfolgen. Im Nahbereich ist die Kopplung daneben auch
�ber Modem-Eliminatoren (X.25) oder Ethernet m�glich.
X.25 Fern-Kopplung:
VMS SIEMENS
BS2000
+----------+ +---------+
|VAX FTSIE | | |
| | PDN | FT- |
| (VOTS) | +----+ | BS2000 |
+----------+ +-----+ +-----+ | | +---------+
|VAX P.S.I.+--+MODEM+-- ... -+ +- ... --+MODEM+--+X.25+-+ DCAM V9 |
+----------+ +-----+ | | +-----+ +----+ +---------+
| |
+-+-------+-+
| | Leitungsgeschwindigkeit
| DATEX-P | maximal 48 kbit/s
| |
+-----------+
X.25 Nah-Kopplung:
VMS SIEMENS
BS2000
+----------+
|VAX FTSIE | +---------+
| | | FT- |
| (VOTS) | PDN | BS2000 |
+----------+ +------------------+ +-------+ +---------+
|VAX P.S.I.+-------+ Modem-Eliminator +------+ X.25 +--+ DCAM V9 |
+----------+ +------------------+ +-------+ +---------+
Leitungsgeschwindigkeit
maximal 64 kbit/s
Ethernet-Kopplung:
VMS SIEMENS
BS2000
+----------+
|VAX FTSIE | LAN- +---------+
| | Kanal-| FT- |
| (VOTS) | adaptor| BS2000 |
+-----+----+ +-----+---------+
| Ethernet |9632 | DCAM V9 |
+-------------------------------------------+-----+---------+
Leitungsgeschwindigkeit max. 10 Mbit/s
VAX FTSIE bietet die folgenden Funktionen:
- �bertragen einer Datei mit der M�glichkeit einer anschlie�enden
Folgeverarbeitung. Die Folgeverarbeitung kann im lokalen System und im
Zielsystem erfolgen; es k�nnen eigene Folgeverarbeitungen f�r den Fall
einer erfolgreichen und einer nicht erfolgreichen �bertragung angesto�en
werden.
- Die Initiative zur Datei�bertragung kann sowohl vom lokalen wie auch vom
entfernten Rechner ausgehen.
- Steuern der Datei�bertragung: Abbrechen, Anhalten und Wiederanlauf.
- Synchrone und asynchrone Auftragsbearbeitung.
Bei der synchronen Daten�bertragung wartet der Auftraggeber auf den
Abschlu� der �bertragung, beim asynchronen Betrieb erfolgt ein Eintrag in
ein "Auftragsbuch" und die �bertragung wird zeitlich unabh�ngig von der
Eingabe des Auftraggebers durchgef�hrt.
- Datei�bertragung �ber Kommandos auf der DCL-Ebene (sowohl f�r synchronen
als auch asynchronen Betrieb).
- Automatische Konvertierung bei �bertragung von Textdateien von ASCII nach
EBCDIC und umgekehrt. Es kann zwischen unterschiedlichen Tabellen gew�hlt
werden (z.B. Multinational Characterset vs. EBCDIC national/international).
- Simultane Abarbeitung mehrerer Datei�bertragungsauftr�ge.
- Diagnosefunktionen zur �berpr�fung der h�heren Protokolle durch ein
Traceauswerteprogramm.
Funktionen der OSI-Transport-Implementierung (VOTS V 2.0):
VOTS ist eine Implementierung der OSI-Transporotschicht entsprechend den
ISO-Standards 8072, 8073 und bietet Internet-Dienste und -Protokolle nach
ISO-Standard 8473; es werden die Transportklassen 0,2 und 4 unterst�tzt. VOTS
stellt die End-zu-End-Verbindung zwischen �ber OSI kommunizierende Systemen
her und setzt die Dienste der Ebenen 1 bis 3 voraus. Es erlaubt den
gleichzeitigen Zugriff auf Local-Area-Netzwerke (IEEE802.3) und
X.25-Datennetze.
Folgende Management-Werkzeuge stehen zur Verf�gung:
- Installation Verification Program (IVP)
- Transport Implementation Control program (OSI$CONTROL)
- Transport Implementation Tracing Utility
- Transport Implementation Event Logging
Merkmale
VAX FTSIE �bertr�gt und empf�ngt ausschlie�lich sequentielle Dateien und
unters�tzt dabei die Satzformate "VARIABLE" und "STREAM_LF".
Bei sequentiellen Dateien kann zwischen dem Format TEXT (hier erfolgt eine
Konvertierung von ASCII nach EBCDIC) und BIN�R gew�hlt werden.
Die L�nge der S�tze der zu �bertragenden Dateien kann bis zu 4000 Bytes
betragen.
VAX FTSIE kann nicht die VAXcluster-Funktionalit�t nutzen. Es kann innerhalb
eines VAXclusters nur auf einer dedizierten Maschine verwendet werden.
Installation
DEC installiert das Softwareprodukt betriebsbereit beim Kunden innerhalb der
Bundesrepublik Deutschland und West-Berlins, sofern die Installation
vereinbarungsgem�� im Preis inbegriffen oder vom Kunden gesondert in Auftrag
gegeben worden ist. Die verf�gbaren 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 Softwareprodukts durch einen erfahrenen Software-
spezialisten von Digital Equipment.
Mindest-Hardwarekonfiguration
Die VAX-, MicroVAX- oder VAXstation-Konfigurationen sind in "Hardware- und
Softwareumgebung" beschrieben.
Erforderliche Software
Betriebssystem VMS oder MicroVMS
VAX P.S.I. oder VAX P.S.I. Access f�r die Kopplung �ber X.25 (DATEX-P oder
Nahkopplung)
N�here Informationen zur Verf�gbarkeit von erforderlicher oder zus�tzlicher
Software und der jeweils erforderlichen Version finden Sie in "Hardware- und
Softwareumgebung".
Zus�tzliche unterst�tzte Software
keine
Bestellinformation
Die Produktkennung f�r das Software-Produkt ist VUQG
Die Basis-Bestellnummer f�r dieses Produkt hat das Format Q*-VUQG*-**
Softwarelizenzierung
F�r dieses Softwareprodukt einschlie�lich Folgeversionen gelten die
Bestimmungen des Abschnitts Softwarelizenz der Allgemeinen
Gesch�ftsbedingungen von Digital Equipment.
Dienstleistungen
Digital Equipment bietet umfangreiche Software-Dienstleistungspakete an. F�r
n�here Informationen wenden Sie sich bitte an die n�chstgelegene
Gesch�ftsstelle von Digital Equipment.
Gew�hrleistung
Art, Umfang und Dauer der Softwaregew�hrleistung sind in dem Abschnitt
'Gew�hrleistung f�r Softwareprodukte' in den Allgemeinen Gesch�ftsbedingungen
der Digital Equipment GmbH geregelt.
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 Unterst�tzung des Kunden durch Digital Equipment behandeln.
Hardware- und Softwareumgebung
VAX FTSIE Version 1.3 SPD-Nr. C0.92.03-A
Mindest-Hardwarekonfiguration
o Unterst�tzte Prozessoren (Hostsystem)
VAX-11/750, VAX-11/780, VAX-11/785, VAX 6210, VAX 6220, VAX 6230, VAX 6240,
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX
8600, VAX 8650, VAX 8700, VAX 8800
MicroVAX 2000, MicroVAX II, MicroVAX 3500/3600/3602,
VAXstation II, VAXstation 2000, VAXstation 3200/3500
o nicht unterst�tzte Prozessoren
VAXstation I, MicroVAX I, VAX-11/725, VAX-11/782
o Unterst�tzte Prozessoren (Zielsystem)
- SIEMENS 7.5XX (z.Zt. nicht Modellreihe C30)
o Einschr�nkungen
Bei einer Kopplung �ber X.25 gelten die genannten Prozessoren von VAX P.S.I.
V 4.2 SPD Nr. 25.40
o Zus�tzliche erforderliche Hardware
Hostsystem VMS
Bei Ethernet-Kopplung:
F�r den Betrieb von VAX FTSIE auf der Basis von Ethernet ist die
erforderliche Hardware identisch mit der von VAX OSI Application Kernel V
1.1 (SPD-Nr. 27.47)
- DEUNA oder DELUA f�r UNIBUS-basierende Systeme oder BI-BUS-Systeme mit dem
entsprechenden UNIBUS-Adapter
- DEBNA f�r BI-BUS-basierende Systeme. VAX FTSIE unters�tzt nicht DEBNT
- DEQNA, DESQA, oder DELQA f�r Q-BUS-basierende Systeme
- DESVA f�r MicroVAX 2000 oder VAXstation 2000
Dar�ber hinaus ist ein passendes Ethernet Transceiver Kabel notwendig um den
Ethernet Controller an das Local Area Network anzuschlie�en (Siehe Network
and Communication Buyers Guide f�r die genauen Bestellnummern).
Bei X.25 Kopplung:
Hier gelten sind die Hardware-Voraussetzungen VAX P.S.I. Version 4.2
(SPD-Nr. 25.40):
Anschlu� an das Paketvermittlungsnetz mit einer DTE-Nummer, die die
Verwendung von Subadressen erlaubt,
oder
eine Direktkopplung beider Systeme mit einem entsprechenden Kabel und
einem handels�blichen Modem-Eliminator, der �ber einen Taktgeber und �ber
die M�glichkeit der galvanischen Trennung verf�gt.
Zielsystem (Siemens/BS2000)
Bei X.25-Kopplung
- Vorrechner: alle DVR, CVR und IVR des TRANSDATA-Systems
- HDLC-Blockpuffer (abh�ngig von Geschwindigkeit und Schnittstellen)
Bei Ethernet-Kopplung
LAN Kanaladapter 9632
o Erforderlicher Plattenplatz
Erforderliche Magnetplattenkapazit�t (Block-Cluster-Gr��e = 1):
Erforderliche Plattenspeicherkapazit�t 3000 Bl�cke
f�r die Installation: 1540 KByte
Erforderliche Plattenspeicherkapazit�t 3000 Bl�cke
f�r die Installation VOTS: 1536 KByte
Erforderliche Plattenspeicherkapazit�t 1500 Bl�cke f�r die Anwendung
(permanent): 770 KByte
Erforderliche Plattenspeicherkapazit�t 3000 Bl�cke f�r die Anwendung
(permanent)f�r VOTS: 1536 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 und zus�tzlicher Software ab.
Zus�tzliche unterst�tzte Hardware
Keine
VAXcluster-Umgebung
VAX FTSIE unterst�tzt nicht die VAXcluster-Umgebung. Es kann innerhalb eines
Clusters auf einer dedizierten Maschine betrieben werden.
Erforderliche Software
o Erforderliche(s) Betriebssystem(e) und unterst�tzte Versionen
VAX/VMS oder MicroVMS ab Version 5.0
o Zus�tzliche erforderliche Softwareprodukte und unterst�tzte Versionen
- Bei Fernkopplung �ber DATEX-P oder Nahkopplung via Modem bzw.
Modemeliminator VAX P.S.I. V 4.2 oder VAX P.S.I. Access V 4.2
o Erforderliche Software f�r Siemens/BS2000
- BS2000 ab Version 7.5
- DCAM ab Version 9.0 (ISO/OSI-konforme Schnittstelle)
- FT-BS2000 ab Version 2.1
- Bei Fernkopplung �ber DATEX-P oder Nahkopplung via Modem bzw. Modem-
eliminator PDN Version 8.0 C und X.25 Port Version 2.1 oder PDN Version 9.0
und X.25 Port Version 2.2
Zus�tzliche unterst�tzte Software
keine
K�nftiger Bedarf
Die Mindest-Hardware- und Softwareerfordernisse f�r zuk�nftige Versionen
dieses Produkts k�nnen von den f�r diese Version erforderlichen abweichen.
Verteilermedien
Magnetbandkassette TK50
Magnetband 1600 BPI
Bestellinformation
Softwarelizenzen: QL-VUQG*-AA
Software-Verteilermedien: QA-VUQG*-**
Softwaredokumentation: QA-VUQG*-GZ Dies umfa�t nur die Dokumentation
f�r VAX FTSIE. Zus�tzliche Dokumen-
tation zu VOTS �ber QA-VD9AA-GZ
Software-Dienstleistungen: QT-VUQG*-**
Das Zeichen * steht f�r variable Felder.
Diese Informationen sind g�ltig zum Zeitpunkt des Erscheinens der vorliegenden
Version. F�r aktuellere Informationen wenden Sie sich bitte an die
n�chstgelegene Gesch�ftsstelle von Digital Equipment.
|
| 21.2 | Deutsche SPD f�r VAX FTSIE 1.2 | ECCGY4::STROHMAIER | | Wed May 31 1989 11:35 | 341 |
| AE-JY95C-TE
Januar 1989
------------------------------------------------------------------------------
Software Version 1.2
Produkt
Beschreibung
------------------------------------------------------------------------------
VAX FTSIE Version 1.2 SPD-Nr. C0.92.02
Datei�bertragung VMS - SIEMENS/BS2000
Produktbeschreibung
VAX FTSIE (File Transfer with SIEMENS) dient zur Datei�bertragung (mit der
M�glichkeit der anschlie�enden Folgeverarbeitung) zwischen SIEMENS/BS2000- und
VMS-Systemen unter Verwendung der ISO/OSI-Protokolle bis zur Transportebene
(Schicht 1 - 4) und von SIEMENS genormter File-Transfer-Protokolle. Die
verwendeten SIEMENS-Protokolle f�r die Anwendungsschichten 5 bis 7 sind:
- FJAM-BS2000 (File Job Access Method)
- NDMS-BS2000 (Network Data Management System)
- DAS-BS2000 (Data Access Services)
Die OSI-Transportebene wird durch das Produkt VAX OSI Transport Service (VOTS)
implementiert.
Die Kopplung des lokalen und des entfernten Rechners kann �ber das Paketver-
mittlungsnetz DATEX-P erfolgen. Im Nahbereich ist die Kopplung daneben auch
�ber Modem-Eliminatoren (X.25) oder Ethernet m�glich.
X.25 Fern-Kopplung:
VMS SIEMENS
BS2000
+----------+ +---------+
|VAX FTSIE | | |
+----------+ PDN | FT- |
|VOTS | +----+ | BS2000 |
+----------+ +-----+ +-----+ | | +---------+
|VAX P.S.I.+--+MODEM+-- ... -+ +- ... --+MODEM+--+X.25+-+ DCAM V9 |
+----------+ +-----+ | | +-----+ +----+ +---------+
| |
+-+-------+-+
| | Leitungsgeschwindigkeit
| DATEX-P | maximal 48 kbit/s
| |
+-----------+
X.25 Nah-Kopplung:
VMS SIEMENS
BS2000
+------------+
| VAX FTSIE | +---------+
+------------+ | FT- |
| VOTS | PDN | BS2000 |
+------------+ +------------------+ +-------+ +---------+
| VAX P.S.I. +-----+ Modem-Eliminator +------+ X.25 +--+ DCAM V9 |
+------------+ +------------------+ +-------+ +---------+
Leitungsgeschwindigkeit
maximal 64 kbit/s
Ethernet-Kopplung:
VMS SIEMENS
BS2000
+------------+
| VAX FTSIE | LAN- +---------+
+------------+ Kanal-| FT- |
| VOTS | adaptor| BS2000 |
+-----+------+ +-----+---------+
| Ethernet |9632 | DCAM V9 |
+-------------------------------------------+-----+---------+
Leitungsgeschwindigkeit max. 10 Mbit/s
VAX FTSIE bietet die folgenden Funktionen:
- �bertragen einer Datei mit der M�glichkeit einer anschlie�enden
Folgeverarbeitung. Die Folgeverarbeitung kann im lokalen System und im
Zielsystem erfolgen; es k�nnen eigene Folgeverarbeitungen f�r den Fall
einer erfolgreichen und einer nicht erfolgreichen �bertragung angesto�en
werden.
- Die Initiative zur Datei�bertragung kann sowohl vom lokalen wie auch vom
entfernten Rechner ausgehen.
- Steuern der Datei�bertragung: Abbrechen, Anhalten und Wiederanlauf.
- Synchrone und asynchrone Auftragsbearbeitung.
Bei der synchronen Daten�bertragung wartet der Auftraggeber auf den
Abschlu� der �bertragung, beim asynchronen Betrieb erfolgt ein Eintrag in
ein "Auftragsbuch" und die �bertragung wird zeitlich unabh�ngig von der
Eingabe des Auftraggebers durchgef�hrt.
- Datei�bertragung �ber Kommandos auf der DCL-Ebene (sowohl f�r synchronen
als auch asynchronen Betrieb).
- Automatische Konvertierung bei �bertragung von Textdateien von ASCII nach
EBCDIC und umgekehrt. Es kann zwischen unterschiedlichen Tabellen gew�hlt
werden (z.B. Multinational Characterset vs. EBCDIC national/international).
- Simultane Abarbeitung mehrerer Datei�bertragungsauftr�ge.
- Diagnosefunktionen zur �berpr�fung der h�heren Protokolle durch ein
Traceauswerteprogramm.
Merkmale
VAX FTSIE �bertr�gt und empf�ngt ausschlie�lich sequentielle Dateien und
unters�tzt dabei die Satzformate "VARIABLE" und "STREAM_LF".
Bei sequentiellen Dateien kann zwischen dem Format TEXT (hier erfolgt eine
Konvertierung von ASCII nach EBCDIC) und BIN�R gew�hlt werden.
Die L�nge der S�tze der zu �bertragenden Dateien kann bis zu 4000 Bytes
betragen.
VAX FTSIE kann nicht die VAXcluster-Funktionalit�t nutzen. Es kann innerhalb
eines VAXclusters nur auf einer dedizierten Maschine verwendet werden.
Installation
DEC installiert das Softwareprodukt betriebsbereit beim Kunden innerhalb der
Bundesrepublik Deutschland und West-Berlins, sofern die Installation
vereinbarungsgem�� im Preis inbegriffen oder vom Kunden gesondert in Auftrag
gegeben worden ist. Die verf�gbaren 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 Softwareprodukts durch einen erfahrenen Software-
spezialisten von Digital Equipment.
Mindest-Hardwarekonfiguration
Die VAX-, MicroVAX- oder VAXstation-Konfigurationen sind in "Hardware- und
Softwareumgebung" beschrieben.
Erforderliche Software
Betriebssystem VMS oder MicroVMS
VAX OSI Transport Service (VOTS)
VAX P.S.I. oder VAX P.S.I. Access f�r die Kopplung �ber X.25 (DATEX-P oder
Nahkopplung)
N�here Informationen zur Verf�gbarkeit von erforderlicher oder zus�tzlicher
Software und der jeweils erforderlichen Version finden Sie in "Hardware- und
Softwareumgebung".
Zus�tzliche unterst�tzte Software
keine
Bestellinformation
Die Produktkennung f�r das Software-Produkt ist ZHC
Die Basis-Bestell-Nummer f�r dieses Produkt hat das Format Q*ZHC-**
Softwarelizenzierung
F�r dieses Softwareprodukt einschlie�lich Folgeversionen gelten die
Bestimmungen des Abschnitts Softwarelizenz der Allgemeinen
Gesch�ftsbedingungen von Digital Equipment.
Dienstleistungen
Digital Equipment bietet umfangreiche Software-Dienstleistungspakete an. F�r
n�here Informationen wenden Sie sich bitte an die n�chstgelegene
Gesch�ftsstelle von Digital Equipment.
Gew�hrleistung
Art, Umfang und Dauer der Softwaregew�hrleistung sind in dem Abschnitt
'Gew�hrleistung f�r Softwareprodukte' in den Allgemeinen Gesch�ftsbedingungen
der Digital Equipment GmbH geregelt.
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 Unterst�tzung des Kunden durch Digital Equipment behandeln.
Hardware- und Softwareumgebung
VAX FTSIE Version 1.2 SPD-Nr. C0.92.02-A
Mindest-Hardwarekonfiguration
o Unterst�tzte Prozessoren (Hostsystem)
VAX-11/750, VAX-11/780, VAX-11/785, VAX 8200, VAX 8250, VAX 8300, VAX 8350,
VAX 8500, VAX 8530, VAX 8550, VAX 8600, VAX 8650, VAX 8700, VAX 8800,
MicroVAX 2000, MicroVAX II, MicroVAX 3500/3600/3602
VAXstation II, VAXstation 2000, VAXstation 3200/3500,
o Unterst�tzte Prozessoren (Zielsystem)
- SIEMENS 7.5XX (z.Zt. nicht Modellreihe C30)
o Einschr�nkungen
Bei einer Kopplung �ber Ethernet gelten die genannten Prozessoren von VAX
OSI Transport Service 1.2 SPD Nr. 27.15
Bei einer Kopplung �ber X.25 gelten die genannten Prozessoren von VAX P.S.I.
V 4.1 SPD Nr. 25.40
o Zus�tzliche erforderliche Hardware
Hostsystem VMS
Bei X.25 Kopplung:
Hier gelten die Hardware-Voraussetzungen von VAX P.S.I. Version 4.1
(SPD-Nr.25.40):
Anschlu� an das Paketvermittlungsnetz mit einer DTE-Nummer, die die
Verwendung von Subadressen erlaubt,
oder
eine Direktkopplung beider Systeme mit einem entsprechenden Kabel und
einem handels�blichen Modem-Eliminator, der �ber einen Taktgeber und �ber
die M�glichkeit der galvanischen Trennung verf�gt.
Bei Ethernet-Kopplung:
F�r den Betrieb von VAX FTSIE auf der Basis von Ethernet sind die
Hardware-Voraussetzungen identisch mit der von VAX OSI Transport Service V
1.2 (SPD-Nr. 27.15)
Zielsystem (Siemens/BS2000)
Bei X.25-Kopplung
- Vorrechner: alle DVR, CVR und IVR des TRANSDATA-Systems
- HDLC-Blockpuffer (abh�ngig von Geschwindigkeit und Schnittstellen)
Bei Ethernet-Kopplung
LAN Kanaladapter 9632
o Erforderlicher Plattenplatz
Erforderliche Magnetplattenkapazit�t (Block-Cluster-Gr��e = 1):
Erforderliche Plattenspeicherkapazit�t 3000 Bl�cke
f�r die Installation: 1540 KByte
Erforderliche Plattenspeicherkapazit�t 1500 Bl�cke f�r die Anwendung
(permanent): 770 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 und zus�tzlicher Software ab.
Zus�tzliche unterst�tzte Hardware
Keine
VAXcluster-Umgebung
VAX FTSIE unterst�tzt nicht die VAXcluster-Umgebung. Es kann innerhalb eines
Clusters auf einer dedizierten Maschine betrieben werden.
Erforderliche Software
o Erforderliche(s) Betriebssystem(e) und unterst�tzte Versionen
VMS oder MicroVMS Version 4.7
o Zus�tzliche erforderliche Softwareprodukte und unterst�tzte Versionen
- VOTS Version 1.2
- Bei Fernkopplung �ber DATEX-P oder Nahkopplung via Modem bzw.
Modemeliminator VAX P.S.I. V 4.1 oder VAX P.S.I. Access V 4.1
o Erforderliche MicroVMS-Komponenten
Bei Systemen unter MicroVMS V4.x sind s�mtliche MicroVMS-Komponenten f�r die
Verwendung des Softwareprodukts in seinem vollen Funktionsumfang
erforderlich.
o Erforderliche Software f�r Siemens/BS2000
- BS2000 ab Version 7.5
- DCAM ab Version 9.0 (ISO/OSI-konforme Schnittstelle)
- FT-BS2000 ab Version 2.1
- Bei Fernkopplung �ber DATEX-P oder Nahkopplung via Modem bzw. Modem-
eliminator PDN Version 8.0 C und X.25 Port Version 2.1 oder PDN Version 9.0
und X.25 Port Version 2.2
Zus�tzliche unterst�tzte Software
keine
K�nftiger Bedarf
Die Mindest-Hardware-und Softwareerfordernisse f�r zuk�nftige Versionen
dieses Produkts k�nnen von den f�r diese Version erforderlichen
abweichen.
Verteilermedien
Magnetbandkassette TK50
Magnetband 1600 BPI
Bestellinformation
Softwarelizenzen: Q*ZHC-UZ
Software-Verteilermedien: Q*ZHC-H5
Q*ZHC-HM
Softwaredokumentation: QLZHC-GZ
Software-Dienstleistungen: Q*ZHC-**
Das Zeichen * steht f�r variable Felder.
Diese Informationen sind g�ltig zum Zeitpunkt des Erscheinens der vorliegenden
Version. F�r aktuellere Informationen wenden Sie sich bitte an die
n�chstgelegene Gesch�ftsstelle von Digital Equipment.
|
| 21.3 | English SPD VAX FTSIE 1.3 | ECCGY4::STROHMAIER | | Wed May 31 1989 11:38 | 365 |
| Attention:
This is not an official SPD - VAX FTSIE as a product is only available
with German documentation; there is no support available outside Germany.
-----------------------------------------------------------------------------
Software
Product
Description
-----------------------------------------------------------------------------
PRODUCT NAME: VAX FTSIE Version 1.3 SPD: C0.92.03
DESCRIPTION
VAX FTSIE (File Transfer with SIEmens) provides a filetransfer between VAX/VMS
Systems and SIEMENS/BS2000 systems with the ability of remote and local
postprocessing. The implementation uses the ISO/OSI protocols up to layer 4
(transport layer) and specific SIEMENS communication protocols for layer 5
through 7:
o NDMS-BS2000 (Network Data Management System)
o DAS-BS2000 (Data Access Services)
o FJAM-BS2000 (File Job Access Method)
The connection between local and remote system is established via X.25 using
PSDN. For connecting local systems X.25 (PSDN as well as modem-eliminators) as
well as ethernet can be used.
The Transport implementation includes the Transport and Network layers. It is
shipped as part of VAX FTSIE on separate media and with separate documentation
labeled VOTS V 2.0. Note that the use of the VOTS programming interface is not
a supported part of the VAX FTSIE product.
+-----------------------------------------------------------------------------+
| X.25 remote connection: |
| |
| VAX/VMS SIEMENS |
| BS2000 |
| +----------+ +---------+ |
| |VAX FTSIE | | | |
| | | PDN | FT- | |
| | (VOTS) | +----+ | BS2000 | |
| +----------+ +-----+ +-----+ | | +---------+ |
| |VAX P.S.I.+--+MODEM+-- ... -+ +- ... --+MODEM+--+X.25+-+ DCAM V9 | |
| +----------+ +-----+ | | +-----+ +----+ +---------+ |
| | | |
| +-+-------+-+ |
| | PSDN | Speed max. 48 Kbit/s |
| |( DATEX-P) | |
| | | |
| +-----------+ |
+-----------------------------------------------------------------------------+
+------------------------------------------------------------------------------+
| X.25 local conection: |
| |
| VAX/VMS SIEMENS |
| BS2000 |
| +------------+ |
| | VAX FTSIE | +---------+ |
| | | | FT- | |
| | (VOTS) | PDN | BS2000 | |
| +------------+ +------------------+ +-------+ +---------+ |
| | VAX P.S.I. +-----+ Modem-Eliminator +------+ X.25 +--+ DCAM V9 | |
| +------------+ +------------------+ +-------+ +---------+ |
| |
| Speed max. 64 Kbit/s |
+------------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| Ethernet-Connection: |
| |
| VAX/VMS SIEMENS |
| BS2000 |
| +------------+ |
| | VAX FTSIE | +---------+ |
| | | Kanal- | FT- | |
| | (VOTS) | adaptor| BS2000 | |
| +-----+------+ +-----+---------+ |
| | Ethernet |9632 | DCAM V9 | |
| +-------------------------------------------+-----+---------+ |
| 10 Mbit/s |
+-----------------------------------------------------------------------------+
VAX FTSIE has the following features:
o transferring sequential files from or to a SIEMENS/BS2000 system in two
modes, synchronously or asynchronously. For asynchronous transfers a queue
("Auftragsbuch") is set up.
o postprocessing capability, both on the remote and/or on the local system,
both in case of success or failure.
o controlling the file transfer: starting, terminating and continuing it
automatically after loss of the network connection.
o simultaneous execution of several file transfer requests.
o commands are entered at DCL-level.
o automatic conversion from ASCII to EBCDIC and vice versa when transferring
text files. It can be chosen from various conversion tables (eg.
multinational characterset vs. EBCDIC national/international)
o protocol trace capability for diagnostic purposes.
Special attributes of VAX FTSIE
VAX FTSIE transfers and receives sequential files only and supports the record
format "VARIABLE" and "STREAM-LF".
The sequential files can have the attribute TEXT (with conversion ASCII -
EBCDIC) and BINARY (no conversion).
A record can be and up to 4000 byte long.
VAX FTSIE cannot use VAXcluster functionality. Within a VAXcluster VAX FTSIE
can only be started on one dedicated VAX/VMS system.
VAX FTSIE includes detailed DCL-structured help in English language.
Functionality of the OSI-transport layer implementation (VOTS V2.0):
VOTS implements the forth layer in the OSI seven-layer Reference Model. The
transport protocol is specified by ISO 8073:1986. It provides reliable
ent-to-end transfer of data between cooperation applications; it supports the
transport classes 0,2 and 4. It depends on the service provided by the Network
Layer. It can connect to to one or more ISO 8802-3 (IEEE 802.3) Local Area
subnetworks. It can also be connected to one or more X.25 subnetworks using
DIGITAL's packet switching product range. The implementation allows concurrent
access to both types of subnetworks.
The following management tools are available:
- Installation Verification Program (IVP)
- Transport Implementation Control Program (OSI$CONTROL)
- Transport Implementation Tracing Utility
- Transport Implementation Event Logging
HARDWARE REQUIREMENTS
VAX, MicroVAX, or VAXstation configuration as specified in the System Support
Addendum.
SOFTWARE REQUIREMENTS
For Systems Using Terminals (No DECwindows Interface):
^ VMS Operating System or MicroVMS Operating System
For Workstations Running VWS:
^ VMS Operating System or MicroVMS Operating System
^ VMS Workstation Software
Refer to the System Support Addendum for availability and required versions of
prerequisite software
ORDERING INFORMATION
Software Licenses: QL-VUQG*-**
Software Media: QA-VUQG*-**
Software Documentation: QA-VUQGAA-GZ
Software Product Services: QT-VUGQ*-**
* 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
VOTS supports the VMS License Management Facility.
License units for VAX FTSIE are allocated on a per-CPU basis and are not
dependent on CPU-capacity or User/Activity.
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 "Allgemeine Gesch�ftsbe-
dingungen".
May 1989
SYSTEM SUPPORT ADDENDUM
PRODUCT NAME: VAX FTSIE Version 1.3 SPD: C0.92.03-A
MINIMUM HARDWARE REQUIRED
Processors Supported:
VAX:
VAX-11/750, VAX-11/780, VAX-11/785, VAX 6210, VAX 6220, VAX 6230, VAX 6240, VAX
8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 8600, VAX
8650, VAX 8700, VAX 8800
MICROVAX:
MicroVAX 2000, MicroVAX II, MicroVAX 3500/3600/3602,
VAXstation :
VAXstation II, VAXstation 2000, VAXstation 3200/3500
Processors Not Supported:
VAXstation I, MicroVAX I, VAX-11/725, VAX-11/782
Siemens:
SIEMENS 7.5XX (z.Zt. nicht Modellreihe C30)
Limitations:
For a connection via X.25 processors of VAX P.S.I. V 4.2 SPD Nr. 25.40 and VAX
P.S.I Access are valid.
Additional Hardware required:
Hostsystem VMS
For Local Area Subnetwork Usage the required hardware is identical with VAX OSI
Application Kernel V 1.1 (SPD 27.47):
^ A DEUNA or DELUA for operation on a UNIBUS-based VAX, or BI-BUS with the
appropriate UNIBUS adapter
^ A DEBNA for operation on a BI-BUS based VAX. VAX OSI Applications Kernel
does not support DEBNT
^ A DEQNA, DESQA, or DELQA for operation on a Q-bus based VAX
^ A DESVA for operation with a MicroVAX 2000 or VAXstation 2000
In addition, a suitable Ethernet Transceiver cable is needed to connect the
Ethernet Controller to a tap on the Local Area Network. Refer to the NAC
Buyers Guide for appropriate part numbers.
For the X.25 connection the minimum hardware requirements are identical with
requirements for VAX P.S.I. (SPD 25.40) and:
^ Connection to the PSDN with a DTE-number that allows the use of subaddresses
or
^ direct link with the appropriate cables and modem-eliminatores that provide
an external clock and electrical isolation.
Hostsystem Siemens/BS2000
For a X.25 connection
^ Preprocessor: all DVR, CVR and IVR of the TRANSDATA-Systems
^ HDLC-Blockpuffer (depending on speed and interface)
For an ethernet connection
- LAN Kanaladaptor 9632
Block Space Requirements (Block Cluster Size = 1):
Disk space required for installation of VAX FTSIE: 3000 blocks (1540 bytes)
Disk space required for installation of VOTS: 3000 blocks (1536 bytes)
Disk space required for use (permanent) of VAX FTSIE: 1500 blocks (770 bytes)
Disk space required for use (permanent) of VOTS: 3000 blocks (1536 bytes)
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.
VAXCLUSTER ENVIRONMENT
This layered product does not supported clustr fuctionality. It has to be
installed on one dedicated machine within a cluster.
SOFTWARE REQUIREMENTS
^ VMS Operating System V 5.0
VMS Tailoring
For VMS V5.x systems, the following VMS classes are required for full
functionality of this layered product:
VMS Required Saveset
Network Support
For more information on VMS classes and tailoring, refer to the VMS
Operating System Software Product Description (SPD 25.01.xx).
Siemens/BS2000
^ BS2000 Version 7.5/7.6/8.0
^ DCAM Version 9.0/9.1
^ FT-BS2000 Version 2.1
X.25 connection
^ PDN Version 8.0 B,C and X.25 Port-F Version 2.1
or
PDN Version 9.0 and X.25 Port Version 2.2
Ethernet connection
none
OPTIONAL SOFTWARE
For use over a X.25 subnetwork VAX P.S.I. V 4.2 and/or VAX P.S.I. Access V 4.2
are required.
GROWTH CONSIDERATIONS
The minimum hardware and software requirements for any future version of this
product may be different from the minimum hardware and software requirements
for the current version.
DISTRIBUTION MEDIA
Tape : 9-track 1600 BPI Magtape (PE), TK50 Streaming Tape
ORDERING INFORMATION
Software Licenses: QL-VUQG*-**
Software Media: QA-VUQG*-**
Software Documentation: QA-VUQGAA-GZ This is VAX FTSIE documentation only.
Additional documentation for VOTS can be
ordered with QA-VD9AA-GZ
Software Product Services: QT-VUGQ*-**
* 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 most up-to-date information.
May 1989
|
| 21.4 | English Handbook VAX FTSIE 1.3 | ECCGY4::STROHMAIER | | Wed May 31 1989 11:38 | 821 |
|
Short English Hanbook
VAX FTSIE Version 1.3
The commands of VAX FTSIE (File Transfer with SIEmens) provide the user and
operator interfaces for accessing the functions implemented in the VAX/VMS
Operating System to transfer files to or from SIEMENS/BS2000 systems.
Files are transferred in accordance with the four lower OSI layers and with
the special SIEMENS communication protocols FJAM (NEABF.S) and NDMS (NEABD.S).
The file transfer with SIEMENS is
o symmetrical. The transmission can be initiated in the local system as well
as in the remote system.
o reciprocal. Files can be both sent and received.
VAX FTSIE has the following features:
o Transferring sequential files from or to a SIEMENS/BS2000 system in
synchronous or aynchronous mode
o Postprocessing capability, both on the remote and/or on the local system,
both in case of success or failure
o Controlling the file transfer: starting, terminating and restarting it
automatically after loss of the network connection
o Simultaneous execution of several asynchronous file transfer requests
o Automatic encoding from ASCII to EBCDIC and vice versa when transferring
text files
o Protocol trace capability for diagnostic purposes
You can use VAX FTSIE in two alternative ways:
o By entering the command FTSIE at DCL level, the system branches to a
sub-command mode. The prompt FTSIE> is displayed and you can use all FTSIE
commands. To leave this mode, enter EXIT or press CTRL/Z.
o By entering a full FTSIE command from DCL level, this command will be
transferred to FTSIE and executed. After execution the system returns to DCL.
English Handbook VAX FTSIE V 1.3 Page 2
-------------------------------------------------------------------------------
ADD
Requires the operator privilege (OPER). Defines a symbolic name for a remote
partner address in the address book.
Format: FTSIE ADD option
Option:
PARTNER
Defines a symbolic name for a remote partner address in the address book.
Format: FTSIE ADD PARTNER symbolic-name
Parameters:
symbolic-name: The symbolic name may not be longer than 8 characters and
should not start with the character $. To obtain the station name of the
remote BS2000 system contact the BS2000 system manager.
Command_Qualifiers:
/PARTNER_ADDRESS=partner-address
The partner address is the physical address which must be known to the VAX OSI
Transport Service. The respective symbolic name specified in the command FTSIE
COPY is replaced by this physical address. To obtain the physical address (DTE
number) of the remote BS2000 system contact the BS2000 system manager.
/TSAP-ID=tsap-id
The tsap-id is equivalent to the application name of the remote BS2000 File
Transfer system. To obtain the tsap-id or application name of the remote
BS2000 system contact the BS2000 system manager.
/PROTOCOL_CLASS={2|4}
This qualifier defines the protocol class of the OSI Transport Layer
protocols. Possible values for the protocol class are 2 and 4. You have to use
class 2 when you communicate through the public PSDN (for example DATEX-P)
with your remote partner system. If you are in a Local Area Network, you have
to use class 4.
Examples
$ FTSIE ADD PARTNER SIEMENS1
-/PARTNER_ADDRESS=X25_DATEXP%12345678901
-/TSAP-ID=$FJAM -/PROTOCOL_CLASS=2
Adds the remote partner SIEMENS1 with the DATEX-P address 12345678901 and the
tsap-id $FJAM to the address book. Class 2 of the transport protocol has to be
used.
English Handbook VAX FTSIE V 1.3 Page 3
-------------------------------------------------------------------------------
CANCEL
Cancels asynchronous requests which are being executed or which are waiting in
the file transfer request queue. The operator privilege (OPER) enables the
system manager to delete any request from the request queue. A user without
the OPER privilege is only able to cancel requests which have been entered
under his own user identification.
Format: FTSIE CANCEL transfer-identifier
Parameters
transfer-identifier Number of the request to be deleted. The transfer
identifier is displayed in two instances:
o In the confirmation of the transfer request when issuing the copy command
o In the column TID of the information table issued on entering the command
SHOW QUEUE
Examples
$ FTSIE CANCEL 3
The request with the TID number 3 will be interrupted, if the transfer is
active. It will be marked as 'waiting' ('W') in the queue.
For proper termination of the request, it will only be deleted from the
request queue after it has automatically been reactivated by the system. If
the transfer request was waiting ('W') in the queue, the appropriate entry in
the file transfer request queue will be deleted.
English Handbook VAX FTSIE V 1.3 Page 4
-------------------------------------------------------------------------------
COPY
Designates the sending of a file to a remote system or the receiving of a file
from a remote system.
Format: FTSIE COPY source-file-spec target-file-spec [/qualifier...]
Parameters
source-file-spec
For sending a file to a remote system, this parameter is the local file
specification. If the device or directory is not specified, your current
default device and directory will be used.
For receiving a file from the remote system, this parameter must have the
following format: symbolic-name"remote-login-information"::source-filename
target-file-spec
For sending a file to a remote system, this parameter must have the following
format: symbolic-name"remote-login-information"::target-filename. For
receiving a file from the remote system, this parameter is the local file
specification. If the device or directory is not specified, your current
default device and directory will be used.
remote-login-information
For executing a file transfer with the remote system, you have to specify
valid login information for the remote system in the following format:
"username account-number[ password]"
This format is in accordance wtih the conventions of the target
BS2000 system.
file-spec
Specifies the file name. If the directory is not specified, your current
default device and directory will be used. The use of wildcard characters is
not permissible.
symbolic-name
A symbolic address of the remote system. You must define this name in the
address book (see VAX FTSIE command ADD PARTNER). The name may not be longer
than 8 characters.
Command_Qualifiers:
/CODE_TABLE=table-name
When transferring text files, the code conversion table specified under the
value table-name will be used. This specification is only valid in synchronous
transfer mode. If you do not specify a table name, the default value for
asynchronous transfers will be used. The current default value for
asynchronous transfers is defined by the system manager. The user can obtain
the names of the code conversion tables that are available from the system
manager. The system default is SRVS10.
/COMPRESS
You can specify this qualifier if you want consecutive characters to be
transferred in compressed form.
/FORMAT=type
English Handbook VAX FTSIE V 1.3 Page 5
-------------------------------------------------------------------------------
VAX FTSIE uses the qualifier /FORMAT=type to define the target file format.
Possible values for 'type' are:
o TEXT (default)
Identifies a text file (ASCII-characters) with variable-length records
according to the conventions of the respective target system. The maximum
record size is 4000 bytes.
o BINARY
Identifies a file containing structured binary data with variable-length
records according to the RMS conventions of the local system. The maximum
record size is 4000 bytes.
o UNDEFINED
Identifies a file containing non-structured sequences of sequences of
binary data. The file format under VMS is Stream_LF.
/LOG (default) /NOLOG
Controls whether or not the VAX FTSIE command COPY will display detailed
information about the processing of the command. The default value is /LOG.
Using the qualifier /NOLOG suppresses the output of detailed
information.
/MAIL_NOTIFICATION
Specifies that you want to be notified of the result of the transfer by way of
electronic mail. This qualifier is not valid for synchronous file transfers.
/OVERLAY (default)
If a version number has been included in the file specification, the target
file will be overwritten. If this version does not exist, a new file will be
created. If no version number is specified, a new version will be created. If
the file does not exist, a new file with version number 1 will be created.
/APPEND
If a version number has been included in the file specification, the target
file will be extended. If the target file does not exist, a new file will be
created. If no version number is specified, the highest version of the file
will be extended.
/NEW_FILE
The version number has no effect. The target file will be created. No file of
the same name may previously exist, since the COPY command would be rejected
in this case.
/PASSWORD=password
This qualifier has to be used if the file in the remote BS2000 system is
protected by a password. The password has to be specified according to the
conventions of the BS2000 system and must be enclosed in quotation marks.
/RECORD_SIZE=n
Determines the maximum record size. Using this qualifier you can transfer
records that are longer than usual. Note that not all record sizes are
supported in the partner system. Possible values for the record size n are
from 128 to 4000 bytes. The default value is 1024 bytes. This qualifier cannot
be used together with the qualifier /FORMAT=UNDEFINED.
/SUCCESS_ACTION=(LOCAL="local-command",REMOTE="remote-command")
With these qualifiers you can specify a command that is to be executed after
the file transfer has completed successfully. The specification
English Handbook VAX FTSIE V 1.3 Page 6
-------------------------------------------------------------------------------
LOCAL="local-command" is only valid during asynchronous file transfers. You
can specify postprocessing commands for your local and/or for the remote
system:
o local-command
After a successful asynchronous file transfer, the specified command will
be executed in the local system under your login account. You can use any
valid DCL command enclosed in quotation marks.
o remote-command
After successful completion of a file transfer, the specified command will
be executed in the remote BS2000 system under the specified remote login.
You can use any valid BS2000 JCL command that starts with a slash (/) and
is enclosed in quotation marks.
/FAILURE_ACTION=(LOCAL="local-command",REMOTE="remote-command")
With these qualifiers you can specify a command that is to be executed after a
file transfer has failed. The specification LOCAL="local-command" is only
valid during asynchronous file transfers. You can specify commands for your
local and/or for the remote system.
o local-command
If the asynchronous file transfer fails, the specified command will be
executed in the local system under your login account. You can use any
valid DCL command enclosed in quotation marks.
o remote-command
If the file transfer fails, the specified command will be executed in the
remote BS2000 system under the specified remote login. You can use any
valid BS2000 JCL command that starts with a slash (/) and is enclosed in
quotation marks.
/TRANSFER_MODE=SYNCHRONOUS
/TRANSFER_MODE=ASYNCHRONOUS (default)
Specifies whether the file transfer is to be executed synchronously or
asynchronously. Only one of these qualifiers can be specified at a time.
If you use the qualifier /TRANSFER_MODE=ASYNCHRONOUS, your request is entered
in the file transfer request queue and will be executed independently of your
further system use, i. e. you can continue your work on DCL level.
If the network connection breaks down during the file transfer, the transfer
will be continued after establishing a new connection.
If you specify the qualifier /TRANSFER_MODE=SYNCHRONOUS, the transfer is
executed immediately. After completion of your request you can enter further
DCL commands.
Examples
1. $ FTSIE COPY MYFILE.TXT SIEMENS1"NAME1 ACC1 PASSW1"::REMFILE.TXT -
/TRANSFER_MODE=ASYNCHRONOUS -
/FORMAT=TEXT/MAIL_NOTIFICATION
The text file MYFILE.TXT is transferred asynchronously to the remote system
with the symbolic name SIEMENS1.The filename in the target system will be
REMFILE.TXT. In the remote system, the login will be performed under the user
name NAME1, account number ACC1, and password PASSW1. The user is notified of
the success or failure of the COPY command by means of electronic mail.
2. $ FTSIE COPY SIEMENS2"NAME2 ACC2 PASSW2"::REMFILE.EXE -
MYFILE.EXE/FORMAT=BINARY -
/SUCCESS_ACTION=(LOCAL="run myfile")
English Handbook VAX FTSIE V 1.3 Page 7
-------------------------------------------------------------------------------
The binary file REMFILE.EXE is transferred asynchronously from the remote
system with the symbolic name SIEMENS2. The filename in the local system will
be MYFILE.EXE. The symbolic name SIEMENS2 has to be defined in the address
book. In the remote system, the login will be performed under the user name
NAME2, account number ACC2, and password PASSW2. After a successful transfer,
the command "run myfile" will be executed in the local system.
3. $ FTSIE COPY DEC_NODE"NAME3 DUMMY PASSW3"::MYFILE.TXT -
SIEMENS3"NAME3 ACC3 PASSW3"::REMFILE.TXT
The DECNET file MYFILE.TXT is transferred asynchronously to the system with
the symbolic name SIEMENS3. The filename in the target system will be
REMFILE.TXT. If DEC_NODE is a system under VMS, a dummy value has to be
entered for the account-number due to the syntax of the COPY command. At the
target system, the login will be performed under the user name NAME3, account
number ACC3, and password PASSW3.
English Handbook VAX FTSIE V 1.3 Page 8
-------------------------------------------------------------------------------
DELETE
Operator privilege (OPER) required. Deletes an entry in the address book.
Format: FTSIE DELETE option
Option:
PARTNER
Deletes an address book entry.
Format: FTSIE DELETE PARTNER symbolic-name
Parameters
symbolic-name
Deletes the address book entry with the respective symbolic name. A symbolic
name may not comprise more than 8 characters and may not be preceded by the
character $.
Examples
$ FTSIE DELETE PARTNER SIEMENS1
Deletes the entry with the symbolic name SIEMENS1 in the address book.
English Handbook VAX FTSIE V 1.3 Page 9
-------------------------------------------------------------------------------
HELP
The HELP command provides on-line user information on VAX FTSIE.
Format: FTSIE HELP [topic ... ]
English Handbook VAX FTSIE V 1.3 Page 10
-------------------------------------------------------------------------------
MODIFY
Operator privilege (OPER) required. Modifies an address book entry.
Format: FTSIE MODIFY option
Option:
PARTNER
Modifies an entry in the address book.
Format: FTSIE MODIFY PARTNER symbolic-name
Parameters
symbolic-name
Symbolic partner name of the address book entry to be modified.
Command_Qualifiers:
/PARTNER_ADDRESS=partner-address
The partner address is the physical address which must be made known to the
VAX OSI Transport Service. The respective symbolic name specified in the FTSIE
COPY command is replaced by this physical address. To obtain the physical
address (DTE-Number) of the remote BS2000 system contact the BS2000 system
manager.
/TSAP-ID=tsap-id
The tsap-id is equivalent to the application name of the remote BS2000 file
transfer system. To obtain the tsap-id or application name of the remote
BS2000 system you have to contact the BS2000 system manager.
/PROTOCOL_CLASS={2|4}
This qualifier defines the protocol class of the OSI Transport Layer
protocols. Possible values for the protocol class are 2 and 4. You have to use
class 2 when you communicate through the public PSDN (for example DATEX-P)
with your remote partner system. If you are in a Local Area Network, you have
to use class 4.
Examples
$ FTSIE MODIFY PARTNER SIEMENS1 -
/TSAP-ID=APPL1
Modifies the entry of the remote partner system SIEMENS1 with the new tsap-id
APPL1.
English Handbook VAX FTSIE V 1.3 Page 11
-------------------------------------------------------------------------------
RESET
Clears the file transfer request queue in the case of an error condition.
Format: FTSIE RESET symbolic-name
Parameters
symbolic-name
The symbolic-name is specified as listed in the column REMSYS of the display
obtained with the VAX FTSIE command SHOW QUEUE. The asterisk wildcard
character (*) can be used to delete all entries from the file transfer request
queue.
Command_Qualifiers
/APPLICATION_NAME=application-name
Using this qualifier you can delete a request queue entry by specifying a
remote application name. You can obtain a list of all requests by using the
VAX FTSIE command SHOW QUEUE. The remote application names are listed in the
column REMAPP of the display.
Examples
1. $ FTSIE RESET *
Deletes all entries in the file transfer request queue.
2. $ FTSIE RESET REMSYS1/APPLICATION_NAME=$FJAM
Deletes all entries of the remote partner REMSYS1 with the application name
$FJAM.
English Handbook VAX FTSIE V 1.3 Page 12
-------------------------------------------------------------------------------
SET
Operator privilege (OPER) required. The SET command is used for the following
purposes:
o Defining installation-dependent parameters such as the name of the local
station, and the local transport identification
o Defining VAX FTSIE system parameters such as the number of asynchronous
requests that can be executed simultaneously, the size of the blocks to be
transferred, the name of the current code conversion table, and the
transfer mode
o Starting and terminating the protocol trace function
Format: FTSIE SET option
Options:
1. BLOCKSIZE
Modifies the maximum length of file transfer blocks.
Format: FTSIE SET BLOCKSIZE=block-size
block-size Specifies the maximum length of the file transfer blocks. Possible
values for the block-size parameter range from 128 to 4096. The default value
is 2052.
Example:
$ FTSIE SET BLOCKSIZE=1024
Sets the maximum size of file transfer blocks to the value of 1024.
2. CODE_TABLE
Specifies the name of the code conversion table to be used for asynchronous
file transfers or the name of the default table for synchronous transfers. The
current value is displayed in the output of the VAX FTSIE command SHOW
PARAMETER.
Format: FTSIE SET CODE_TABLE=table-name
table-name Specifies the name of the table on which you want the code
conversion to be based. The system default is SRVS10 (for conversion between
MCS and EBCDIC.SRV.S10). Other available names are INT (conversion between MCS
and EBCDIC.DF.03/International), and GER (between MCS and EBCDIC.DF.03/German).
Example
$ FTSIE SET CODE_TABLE=INT
Defines the code table INT as the default value for asynchronous file
transfers.
3. JOB_LIMIT
Modifies the maximum number of inbound and outbound file transfer requests
which can be active at the same time.
Format: FTSIE SET JOB_LIMIT [/qualifier ...]
Command_Qualifiers
English Handbook VAX FTSIE V 1.3 Page 13
-------------------------------------------------------------------------------
/INCOMING=m
Specifies the maximum number m of inbound file transfer requests which can be
active at the same time. Possible values for m range from 0 to 16. Note that
the total number of inbound and outbound file transfer requests may not exceed
16.
/OUTGOING=n
Specifies the maximum number n of outbound file transfer requests which can be
active at the same time. Possible values for n range from 0 to 16. Note that
the total number of inbound and outbound file transfer requests may not exceed
16.
Examples
$ FTSIE SET JOB_LIMIT /INCOMING=4 /OUTGOING=8
Sets the total number of inbound and outbound server processes to 12.
4. LOCAL_PARTNER_ADDRESS
Defines the local partner address which is the identification of your local
system or your local station name. To obtain the local station name contact
the BS2000 system manager.
Format: FTSIE SET LOCAL_PARTNER_ADDRESS=local-station-name
local-station-name
The local station name may not be longer than 8 characters and should not
start with the character $.
Examples
$ FTSIE SET LOCAL_PARTNER_ADDRESS=MYSYSTEM
Sets your local station name to MYSYSTEM.
5. LOCAL_TRANSPORT_IDENTIFICATION
Defines your local transport identification. To obtain your local transport
identification contact the BS2000 system manager.
Format: FTSIE SET LOCAL_TRANSPORT_IDENTIFICATION=local-tsap-id
local-tsap-id
The local tsap-id may not be longer than 8 characters. It is used by the
inbound file transfer requests to select the FTSIE application and start the
Inbound File Transfer Server Process.
Examples
$ FTSIE SET LOCAL_TRANSPORT_IDENTIFICATION=$FJAM
Sets the local transport identification to $FJAM.
6. MODE
Switches between link modes.
Format: FTSIE SET MODE={TRANSPARENT|STANDARD}
TRANSPARENT (default)/STANDARD
These are the two possible values for the link type. When the link type is set
to TRANSPARENT, the local partner address and the local transport
English Handbook VAX FTSIE V 1.3 Page 14
-------------------------------------------------------------------------------
identification that are sent to the partner system are not encoded. When using
the link type STANDARD, these specifications are encoded before the
transmission starts. This version does not support the link type STANDARD.
Examples
$ FTSIE SET MODE=TRANSPARENT
Sets the link mode to TRANSPARENT.
7. TRACE
Switches the FTSIE protocol trace of the FJAM protocol on or off.
Format: FTSIE SET TRACE [/qualifier]
/PROTOCOL=FULL (default)
/PROTOCOL=BRIEF
/NOPROTOCOL
Specifies whether detailed or brief trace messages will be output. There is no
difference between FULL and BRIEF in this version of VAX FTSIE. If this
qualifier is omitted, the default value /PROTOCOL=FULL is used. The qualifier
/NOPROTOCOL turns off the protocol trace function.
Examples
$ FTSIE SET TRACE
Switches the FTSIE protocol trace on.
English Handbook VAX FTSIE V 1.3 Page 15
-------------------------------------------------------------------------------
SHOW
Displays information about the following items:
o Current parameter values of VAX FTSIE
o Current addresses of remote partner systems defined in the address book o
Asynchronous file transfer requests:
a) Users with the operator privilege (OPER) can obtain complete information
about all asynchronous requests or about all asynchronous requests of a
user under a specific UIC.
b) A user without the operator privilege (OPER) can obtain the following
information:
- Full description of requests initiated in the local system with his/her
own identification
- Full description of requests received from the remote system for his/her
own identification
Note: If the qualifier /USER=own-username is not specified, only the
username will be printed for all other requests in the file transfer
request queue. Any other information about those requests will be replaced
by an asterisk (*).
Format: FTSIE SHOW [option]
Option:
PARAMETER
The following parameter values will be listed:
o Status of synchronous and asynchronous file transfer modes ('started or
'not started')
o FTSIE protocol trace is active
o FTSIE link type is 'transparent' or 'standard'
o Local system identification
o Local tsap-id or application name
o Maximum size of file transfer blocks
o Maximum number of simultaneous outbound requests
o Maximum number of simultaneous inbound requests
o Number of requests initiated in the local system
o Number of requests initiated in the remote system
Format: FTSIE SHOW PARAMETER
/OUTPUT=file-spec
Writes the output of the SHOW PARAMETER command to the file specified under
the value file-spec.
Example $ FTSIE SHOW PARAMETER
Displays information about all FTSIE parameters in the form of a table.
PARTNER
Displays the following information concerning each entry in the address book:
o Symbolic name of the remote system
o Physical partner address of the remote system (host name)
o Tsap-id (Transport Service Access Point Identifier) or application name of
the remote file transfer application
o Protocol class used in OSI Transport Layer 4
Format: FTSIE SHOW PARTNER
English Handbook VAX FTSIE V 1.3 Page 16
-------------------------------------------------------------------------------
/OUTPUT=file-spec
Writes the output of the SHOW PARAMETER command to the file specified under
the value file-spec.
Examples
$ FTSIE SHOW PARTNER
Displays all entries of the address book.
QUEUE
Displays the following information about asynchronous requests:
o Transfer identifier (TID)
FTSIE identifies each request by means of an entry number.
o <-> transfer direction
-> designates an outgoing file
<- designates an incoming file
o S Status of the file transfer:
A - active
W - waiting
L - locked
C - cancelled
o BYTE Specifies the number of bytes transferred. This counter is updated
after a predetermined period of time.
o I If this column is empty, the request has been initiated in the local
system. Otherwise, the column will contain an asterisk (*).
o USERID
User identification of the file transfer request in the local system.
o L_FILE
Local file name.
o REMSYS
Symbolic name of the remote system.
o REMAPP
Application name of the remote file transfer system.
Format: FTSIE SHOW QUEUE
Command_Qualifiers:
/OUTPUT=file-spec
Writes the output of the SHOW PARAMETER command to the file specified under
the value file-spec.
/USER=username
This qualifier is only valid in combination with the command FTSIE SHOW QUEUE.
Users without the operator privilege (OPER) may only view their own requests.
Users with the OPER privilege can obtain a list of all requests of a specified
user.
Examples
1. $ FTSIE SHOW QUEUE
Displays all information about the File Transfer Request Queue.
2. $ FTSIE SHOW QUEUE /USER=HUGO
Displays information about the request queue entries of the user HUGO.
English Handbook VAX FTSIE V 1.3 Page 17
-------------------------------------------------------------------------------
START
Requires the operator privilege (OPER). The command allows you to start the
synchronous or the asynchronous file transfer mode or both.
Format: FTSIE START [transfer-mode]
[transfer-mode]
Specifies the desired file transfer mode. Valid parameter
values are:
ASYNCHRONOUS (default)
SYNCHRONOUS
ASYNCHRONOUS,SYNCHRONOUS
If no parameter has been specified, the default value ASYNCHRONOUS will be
used. Specifying the value ASYNCHRONOUS creates the permanent process
FTSIE$PP. To place requests in the file transfer request queue you can now
enter the command COPY/TRANSFER_MODE=ASYNCHRONOUS. Specifying the value
SYNCHRONOUS enables you to transfer files synchronously with the command
COPY/TRANSFER_MODE=SYNCHRONOUS. If you specify both values in one command, you
have to separate them by a comma.
Examples
1. $ FTSIE START ASYNCHRONOUS
Starts the asynchronous file transfer mode and creates the process FTSIE$PP.
2. $ FTSIE START SYNCHRONOUS
Starts the synchronous file transfer mode.
3. $ FTSIE START ASYNCHRONOUS,SYNCHRONOUS
Starts the synchronous and asynchronous file transfer modes.
4. $ FTSIE START
Starts only the asynchronous file transfer mode.
English Handbook VAX FTSIE V 1.3 Page 18
-------------------------------------------------------------------------------
TERMINATE
Requires the operator privilege (OPER). Terminates the synchronous or the
asynchronous file transfer mode or both.
Format: FTSIE TERMINATE [transfer-mode]
[transfer-mode]
Specifies the selected file transfer mode. Valid parameter values are:
ASYNCHRONOUS (default)
SYNCHRONOUS
ASYNCHRONOUS,SYNCHRONOUS
If no parameter has been specified, the default value ASYNCHRONOUS will be
used. Specifying the value ASYNCHRONOUS terminates the asynchronous file
transfer mode (process FTSIE$PP). If you specify the value SYNCHRONOUS, you
can no longer issue synchronous file transfer requests.
Examples
1. $ FTSIE TERMINATE ASYNCHRONOUS
Terminates the asynchronous file transfer mode and thus the process FTSIE$PP.
2. $ FTSIE TERMINATE SYNCHRONOUS
Terminates the synchronous file transfer mode.
3. $ FTSIE TERMINATE ASYNCHRONOUS,SYNCHRONOUS
Terminates the synchronous and asynchronous file transfer modes.
4. $ FTSIE TERMINATE
Terminates only the asynchronous file transfer mode.
|
| 21.5 | Network-address for documentation | ECCGY4::STROHMAIER | | Mon Jun 05 1989 12:08 | 6 |
|
The network-address for the documentation in POSTSCRIPT-format is
MUNTRA::FTSIE$PUBLIC
|
| 21.6 | MUNTRA::FTSIE$PUBLIC is empty. | KETJE::PACCO | | Tue Aug 22 1989 16:29 | 4 |
| Seems that all files are gone from MUNTRA::FTSIE$PUBLIC
Can anybody tell where the postscript files are actually !
|
| 21.7 | Docu on MUNTRA::FTSIE$PUBLIC | ECCGY4::STROHMAIER | | Fri Aug 25 1989 15:42 | 25 |
|
Dominique,
the files are in MUNTRA::FTSIE$PUBLIC - if you have problems copying
please contact me again.
Regards
Elisabeth
Directory MUNTRA::TRANS$USER1:[FTSIE$PUBLIC]
FTSIE012_CLUSTER_INFO.PS;1
55 6-JUN-1989 10:24:09.00
FTSIE012_RN.PS;1 118 6-JUN-1989 10:45:07.00
FTSIE013_RN.PS;1 106 6-JUN-1989 10:48:48.00
FTSIE_INST_GUIDE_V12_V13.PS;1
199 5-JUN-1989 09:11:46.00
FTSIE_SYSMAN_GUIDE_V12_V13.PS;1
494 5-JUN-1989 09:12:39.00
FTSIE_USER_GUIDE_V12_V13.PS;1
288 5-JUN-1989 09:10:51.00
REMOVE_FTSIE.COM;5 3 9-MAR-1989 08:36:55.00
Total of 7 files, 1263 blocks.
|
| 21.8 | Error in .5 !! | MUNTRA::SCHIMMEL | The Answer Is 42 | Wed Aug 30 1989 11:06 | 13 |
| error in note .5 !!!!
Don't forget the ":" after "FTSIE$PUBLIC" - otherwise "FTSIE$PUBLIC"
will be considered as the name of a file on MUNTRA DECnet default
directory ...
So, please enter
e.g.
$DIR MUNTRA::FTSIE$PUBLIC:
to see the names of the documentation files ...
Helmut
|