Compaq Software Product Description ___________________________________________________________________ PRODUCT NAME: X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 DESCRIPTION X.25 for OpenVMS Alpha Systems enables appropriately configured sys- tems to connect to an X.25 Packet Switched Data Network (PSDN) via an X.25 Relay node on the same Local Area Network (LAN), via a DNA Phase IV X.25 connector node, or directly using a synchronous controller card. The product supports communication via PSDNs conforming to ITU/TSS recommendation X.25 1980,1984, and 1988, or to international standard ISO 8208. Refer to the SUPPORTED PUBLIC NETWORKS section for the list of supported PSDNs. X.25 for OpenVMS Alpha Systems also provides the device drivers and specific data link protocol support for Compaq Computer Corporation's synchronous communications options for OpenVMS Alpha systems. X.25 for OpenVMS Alpha allows an OpenVMS Alpha system to: o Act as a packet-mode DTE connected to a supported PSDN. o Support ISO 8208 DTE to DTE point-to-point operation. o Act as a packet-mode DTE connected to a LAN. o Act as an X.25 Relay node conforming to ISO Technical Report 10029. o Provide an X.25 sub-network for DECnet-Plus CONS and CLNS opera- tion. o Provide a DEC-HDLC point-to-point data link for DECnet-Plus CLNS operation. April 1999 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 o Act as a combination of the above, chosen on a per-DTE basis. The following restrictions of X.25 for OpenVMS Alpha should be noted: o The multi-host mode of operation available in the VAX P.S.I. prod- uct is not provided. o DCE mode is supported for the purposes of point-to-point operation as described in ISO 8208; DCE mode for emulation of a PSDN is not supported. o Use of the D bit in data packets is not supported. X.25 for OpenVMS Alpha supports the following functions: o Process-to-process (X.25) communication. X.25 for OpenVMS Alpha allows application programs to access X.25 network services via the standard OpenVMS QIO system service. o Process-to-terminal (X.29) communication. Through the X.29 QIO programming interface, users of the OpenVMS Alpha system may make outgoing calls to other Compaq or non-Compaq systems or suitable network PADs accessible via a PSDN. o Terminal-to-process (X.29) communication. Remote terminals connected to the PSDN may access the OpenVMS Al- pha host running X.25 by means of an X.29 Switched Virtual Circuit (SVC) call. o DECnet-Plus Connectionless Network Service. The product supports the use of the DEC-HDLC and X.25 protocols as sub-networks for the OSI Connectionless-mode Network Service (CLNS). o DECnet-Plus Connection Oriented Network Service. The product supports the OSI Connection Oriented Network Service (CONS) for OSI Transport over X.25 sub-networks. o X.25 Mail. The X.25 Mail utility allows communication across a PSDN via elec- tronic mail between two systems running the Mail-11 protocol over X.25. Systems that support Mail-11 over X.25 include WAN Support 2 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 for Compaq UNIX[R], X.25 for OpenVMS Alpha, X.25 Client for OpenVMS, and X.25 installations of DECnet-Plus for OpenVMS VAX. o Wide Area Network (WAN) Device Drivers The WAN device drivers support synchronous communications and of- fer a supported user ($QIO) interface. This version also includes a pseudodriver (WANDRIVER) that provides a programming interface to the Data Link level for the LAPB, DEC-HDLC, and LLC2 protocols and an interface to the physical layer of the synchronous commu- nication devices supported by the product. o X.25 Relay allows an appropriately configured Alpha system to re- lay X.25 packets between a Local Area Network (LAN) and a synchronous communications link to a Packet Switched Data Network (PSDN). Features Conformance to Standards X.25 for OpenVMS Alpha complies with the following standards: o ITU/TSS recommendations-X.25 (1980, 1984, or 1988), X.3, X28, X.29 o International standards ISO-8208, 7776, 8881, 8802/2, 8878, 8473 Virtual Circuits X.25 for OpenVMS Alpha offers communication over both Permanent Vir- tual Circuits (PVCs) and Switched Virtual Circuits (SVCs), and sup- ports up to 4096 virtual circuits per system. One virtual circuit is used for each incoming or outgoing X.29 terminal connection, for each X.25 call, and for each DECnet-Plus routing circuit and transport connection. The use of PVCs for X.29 communication is not defined by the 1980 and 1984 ITU/TSS recommendations, and is not available with X.25 for OpenVMS Alpha. Virtual circuits may use X.25 protocol over a LAN connection, over a WAN synchronous communications connection, or may use DIGITAL X.25 ClienT for OpenVMS Alpha Systems over a DECnet circuit to a DECnet Gateway Access Protocol (GAP) connector node. NOTE that there is no support for use of more than 512 of the available virtual circuits by DIGITAL 3 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 X.25 Client for OpenVMS Alpha Systems with DECnet Gateway Access pro- tocol connector nodes. See the HARDWARE REQUIREMENTS section for de- tails of GAP connector nodes and ISO relay nodes supported. Process- to-Process Communication The X.25 for OpenVMS Alpha programming interface allows application programs to access X.25 packet level services via the standard OpenVMS QIO interface. Functions include the establishment and clearing of network connec- tions, data transmission and reception, sending and receiving of in- terrupt messages, and resetting of virtual circuits. The interface alsO provides for the segmentation and recombination of messages that are longer than the packet size selected for the circuit. This interface enables an application program using OpenVMS System Services to communicate with complementary X.25 software on other Compaq or non-Compaq systems. Terminal Communications X.25 for OpenVMS Alpha supports terminal communications according to ITU/TSS recommendations X.3, X.28, and X.29. Only those terminal pa- rameters 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 programming and the host-based PAD user interface. Terminal processes that depend on these extensions may not function correctly when used on other PSDNs or when accessing one PSDN via another (for example, international access). The X.29 interactive terminal interface allows remote asynchronous terminals (character-mode DTEs) connected to the network to communicate with the OpenVMS Alpha system in a manner similar to local terminals. The maximum number of terminals supported on an OpenVMS Alpha system (both local and X.29 remote) cannot exceed the number for which the system has been configured. 4 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 When using applications designed for interactive, local terminal op- erations, transmission delays or PAD parameter settings can cause in- consistencies between incoming X.29 traffic and the application's op- eration. It may be necessary to make modifications to the application user interface or alter PAD parameter settings. The X.29 interface includes a programming capability for the support of specific X.29 signalling requirements, including modification of PAD parameters. Accounting Accounting information is collected and is made available to the user via a report writing utility. For incoming X.29 calls, no information can be retrieved relating to the process or account onto which a user is logged. Security An extensive security facility is provided. Control of remote access to the system (incoming security) and local access to the network (outgoing security) are supported. Incoming and outgoing security can be based on any combination of: o Normal or reverse charging o DTE number o Network (PSDN) o Process (or user) making the outgoing call o Application handling the incoming call Network Management The Network Control Language (NCL) is provided for the management of X.25 for OpenVMS Alpha and DECnet-Plus. NCL provides network manage- ment facilities to: o Define outgoing call destinations o Define incoming call handling o Modify X.25 frame and packet levels parameters 5 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 o Define security parameters o Modify network configuration o Monitor connection statistics o Perform network maintenance functions The network manager can be notified of significant network events such as security violations or network failures through the event logging facility. Problem solving is facilitated by the Common Trace Facility (CTF) provided with the OpenVMS operating system. CTF enables the user to trace and analyse frames passing between the PSDN and the X.25 for OpenVMS Alpha system. Communications Interfaces Refer to the tables in this Software Product Description and consult your local hardware service provider for complete information on the synchronous controller cards supported by X.25 for OpenVMS Alpha, as well as a list of the relay/connector nodes that may be used as X.25 gateways to the LAN. In addition to the devices listed in this Software Product Descrip- tion, operation over CSMA/CD (ISO 8802/3) and FDDI (ISO 9314) networks is supported via the LLC2 protocol. Wide Area Network (WAN) Device Drivers The WAN device drivers included in X.25 for OpenVMS Alpha Systems support synchronous communications. The device drivers all offer a supported user ($QIO) interface. The device drivers all support full-duplex HDLC framing. In all cases, the data throughput over the synchronous lines is de- pendent on the user applications and system environment. The device drivers support modem control signals (DTR, DCD, DSR, RTS and CTS) where these signals are provided by the selected electrical interface. 6 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 Supported controllers are listed in Table 4. WAN device drivers include a pseudodriver (WANDRIVER) that provides a programming interface to the Data Link level for the LAPB, DEC-HDLC, and LLC2 protocols. The pseudodriver also provides an interface to the physical layer of the synchronous communications devices supported by the product. The physical layer interface provides the ability to read and write HDLC formatted frames (leading/trailing flag, HDLC frame check sequencing, HDLC bit stuffing), but protocol interpretation of the frames must be provided by the user application using the interface. Optional Facility Support Table 1 describes the Optional User Facilities of the 1988 ITU/TSS X.25 recommendations that X.25 for OpenVMS Alpha supports. Support for any facility is dependent on the PSDN used. The product documentation describes specific facility availability for supported PSDNs. ___________________________________________________________________ Table_1:__Optional_User_Facilities_Support_________________________ ITU /TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 6.1 On-line facility regis- no tration 6.2 Extended packet se- yes quence numbering ___________________________________________________________________ [1]Refers to those features of a facility that are relevant to the operation of a DTE. "n/a" refers to DCE facilities requiring no action from the DTE. 7 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU /TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 6.3 D bit modification n/a 6.4 Packet retransmission no 6.5 Incoming calls barred n/a 6.6 Outgoing calls barred n/a 6.7 One-way logical channel yes outgoing 6.8 One-way logical channel yes incoming 6.9 Non-standard default yes packet sizes 6.10 Non-standard default yes window sizes 6.11 Default throughput yes class assignment 6.12 Flow control parameter yes negotiation 6.13 Throughput class nego- yes tiation 6.14.1 Closed User Group (CUG) yes 6.14.2 CUG with outgoing yes access ___________________________________________________________________ [1]Refers to those features of a facility that are relevant to the operation of a DTE. "n/a" refers to DCE facilities requiring no action from the DTE. 8 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU /TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 6.14.3 CUG with incoming yes access 6.14.4 Incoming calls barred n/a within a CUG 6.14.5 Outgoing calls barred n/a within a CUG 6.14.6 CUG selection yes 6.14.7 CUG with outgoing yes access selection 6.15.1 Bilateral Closed User yes Group (BCUG) 6.15.2 BCUG with outgoing n/a access 6.15.3 BCUG selection yes 6.16 Fast select yes 6.17 Fast select acceptance n/a 6.18 Reverse charging yes 6.19 Reverse charging accep- n/a tance 6.20 Local charging preven- n/a tion ___________________________________________________________________ [1]Refers to those features of a facility that are relevant to the operation of a DTE. "n/a" refers to DCE facilities requiring no action from the DTE. 9 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU /TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 6.21.3 NUI selection yes 6.22 Charging information yes 6.23.2 RPOA selection yes 6.24 Hunt group no[2] 6.25.1 Call redirection n/a 6.25.2.2 Call deflection selec- no tion 6.25.3 Call redirection or yes call deflection notifi- cation 6.26 Called line address no modified notification 6.27 Transit delay selection yes and indication 6.28 TOA/NPI address selec- no tion and indication 7.1 Non-X.25 facilities yes G.3.1 Calling Address Exten- yes sion ___________________________________________________________________ [1]Refers to those features of a facility that are relevant to the operation of a DTE. "n/a" refers to DCE facilities requiring no action from the DTE. [2]The individual DTEs must be assigned addresses independent of the hunt group address. 10 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU /TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ G.3.2 Called Address Exten- yes sion G.3.3.1 Minimum throughput yes class G.3.3.2 End-to-end transit yes delay G.3.3.3 Priority yes G.3.3.4 Protection yes G.3.4 Expedited data negotia- yes tion ___________________________________________________________________ [1]Refers to those features of a facility that are relevant to the operation of a DTE. "n/a" refers to DCE facilities requiring no action from the DTE. ___________________________________________________________________ INSTALLATION Compaq recommends that a customer's first purchase of this software product include Compaq Installation Services. These services provide for installation of the software product by an experienced Compaq Software Specialist. Only customers experienced with Compaq's X.25 products should attempt installation. Customer Responsibilities 11 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 In some cases, the X.25 network supplier may impose restrictions, limitations, or requirements on the proposed Compaq network configuration. The customer must ensure these are understood and adhered to for each network. Before installation of the software, the customer should: o Install all requisite software and hardware, including terminals. o Obtain, install, and demonstrate as operational any modems and other equipment and facilities necessary to interface to Compaq's communication equipment. o Demonstrate equivalence of operation for modems other than Bell 208A, 208B, 209, 212A synchronous modems, or, in Europe, employ only PTT approved modems. o Subscribe to the Open User Group and to at least two SVCs to com- plete the product's installation checkout (this test loops infor- mation from the X.25 for OpenVMS Alpha system to the PSDN and back to the X.25 for OpenVMS Alpha system). Systems in Closed User Groups only, or where the PSDN does not support calls to the originating DTE address, require specially negotiated arrangements for Compaq to install the product. o Make available for a reasonable period of time, as mutually agreed by Compaq and the customer, all hardware, communication facilities and terminals that are to be used during a Compaq supervised in- stallation. HARDWARE REQUIREMENTS Alpha processors listed in the OpenVMS Alpha Software Product Description (SPD 41.87.xx) are supported with the following exceptions: DEC 4000 Model 600/700 series [1] DEC 7000 Model 600 [1] DEC 10000 Model 600 [1] ____________________ [1] No synchronous communication option available. Connection available only via LLC2. 12 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 DEC 3000 Model 300/300L/300LX/300X [2] System Memory Required In addition to the memory requirements of OpenVMS Alpha and user ap- plications, the minimum memory requirements of X.25 for OpenVMS Al- pha are: o 2.5 Mbytes for software and data structures o 40 Kbytes for each active virtual circuit in a Client configura- tion o 10 Kbytes for each active virtual circuit in a directly connected configuration These figures represent an upper bound only and should be used as a guide to sizing a system to provide adequate X.25 performance. The product will require less memory than quoted. However, an underconfigured system will display reduced performance, not only for X.25 communications but also for other processes. Communication Devices Required X.25 for OpenVMS Alpha requires one or more synchronous controller cards when directly connected to one of the following: o a PSDN via the X.25 protocol; o another system using DECnet-Plus over X.25; or o another Compaq system using DECnet-Plus over DEC-HDLC. The devices available on the supported processors are listed in Ta- ble 3. For additional information on the configuration and performance of these devices see the CONFIGURATION GUIDELINES section. For operation using the ISO 8802-2 protocol (LLC2) the product requires a Local Area Network (LAN) device. The product supports Compaq's ISO 8802-3 (CSMA/CD) and ISO 9341 (FDDI) devices for use with the LLC2 protocol. ____________________ [2] Only standard workstation configurations support use of the SCC. 13 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 For operation over LLC2 to an X.25 relay node, the supported relay nodes are o DEC Network Integration Server (DECNIS) 500/600 (SPD 36.05.xx) o Alpha system running WAN Support for Compaq UNIX (SPD 42.47.xx) configured for X.25 relay For operation over DECnet (using the Gateway Access Protocol, GAP), the supported connector nodes are: o DEC Network Integration Server (DECNIS) 500/600 (SPD 36.05.xx); o DECnet-Plus V7.1 (or later) for OpenVMS VAX configured for X.25 multihost operation (SPD 25.03.xx). For additional information on the configuration and performance of these relay nodes, consult your local hardware service provider and relevant Software Product Descriptions. Disk Space Required The disk space required for installation and use of the product is 15,000 Blocks (7.5 Mbytes). This size is approximate. The actual size will vary depending on the user's system environment, configuration, and software options. OPTIONAL HARDWARE Additional communications devices, subject to limitations described in the CONFIGURATION GUIDELINES section of this SPD. SOFTWARE REQUIREMENTS OpenVMS Alpha Operating System V7.1 or later (SPD 41.87.xx) DECnet-Plus V7.1 or later for OpenVMS Alpha (SPD 50.45.xx). 14 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 GROWTH CONSIDERATIONS The minimum hardware and software requirements for any future version of this product may be different from the requirements for the cur- rent version. SUPPORTED PUBLIC NETWORKS Table 2 shows the public PSDNs supported by the product in the coun- tries shown. In addition, certain private PSDNs have been tested by Compaq and appropriate profiles have been included with the product. For more detail, consult your local Compaq office. ___________________________________________________________________ Table_2:__Supported_Public_Networks________________________________ Country____________Public_Networks[1]______________________________ Argentina Arpac Australia Austpac Austria Datex-P Belgium DCS Brazil Renpac Canada Datapac, Infoswitch Chile VTRnet Denmark Datapak Eire Eirpac Finland Datapak France Transpac Germany Datex-P Hong Kong Datapak, Inet, Intelpak Indonesia SKDP Ireland Ciepac Italy Itapac ___________________________________________________________________ [1 ]Trademarks under which these services are offered are propri- etary to the respective PTTs. 15 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_2_(Cont.):__Supported_Public_Networks________________________ Country____________Public_Networks[1]______________________________ Japan CC-VAN, DDX-P 80/84, Jaisnet, Tymnet[R], Venus LP Luxembourg Luxpac Malaysia Maypac Mexico Telepac Netherlands Datanet 1 New Zealand Pacnet Norway Datapak Pakistan Paknet Philippines Datanet Portugal Telepac Singapore Telepac South Korea Dacomnet Spain Iberpac Sweden Datapak, Datapak II Switzerland Telepac Taiwan Pacnet Thailand Thaipak Turkey Turpak United Kingdom PSS[2], Postgem, Mercury ___________________________________________________________________ [1 ]Trademarks under which these services are offered are propri- etary to the respective PTTs. [2 ]PSS is supported only when the Extended Facilities option has been subscribed. 16 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_2_(Cont.):__Supported_Public_Networks________________________ Country____________Public_Networks[1]______________________________ United States Accunet, Autonet[R], Bell Atlantic CompuServe[R], ConnNet FedexITC, FreedomNet II Impacs, Infonet Mark*Net Extended Service Pacific Bell PPSnet Pulsenet, Sprintnet Telenet[R], Tymnet US West Digipac Western Union PTN-1 Worldnet ___________________________________________________________________ [1 ]Trademarks under which these services are offered are propri- etary to the respective PTTs. ___________________________________________________________________ CONFIGURATION GUIDELINES For direct connection of the Alpha system to the PSDN, operation of the product requires the use of one or more synchronous controller cards. The following devices are supported by X.25 for OpenVMS Alpha Systems: o PBXDP-Ax o A range of single slot multi-port serial synchronous communi- cations PCI adapters. o PBXDI-Ax o A range of single slot dual port serial synchronous communica- tions ISA adapters. o DNSES o Single slot dual port serial synchronous communications EISA adapter. 17 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 o WANcontroller 720 (DSYT1) o Single slot dual port TURBOchannel serial synchronous communi- cations adapter. o For systems with no available TURBOchannel slots, an extender box may be required. o Integral SCC device o A single port multi-function device on the system motherboard. Only the synchronous communications function is supported. o Limited modem signalling capabilities. Local and remote loop- back signals and DTE-sourced clock are not provided. Additional factors to consider when configuring hardware devices for use with the product are: o Hardware configuration limits, such as power supply, backplane space, bus throughput, mapping registers, and any other restrictions on the number of devices per CPU or per bus must be observed. Consult your local hardware service provider for further information. o CPU utilization. Ensure sufficient CPU power will be available to drive the required number of lines at the desired speeds and leave sufficient margin for application processing. The supported devices available on each system are given in Table 3. The operational characteristics of each device are given in Table 4. ___________________________________________________________________ Table_3:__Synchronous_Controllers__________________________________ System___________________Devices_supported_________________________ DEC 2000 Models 300 DNSES /500 18 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_3_(Cont.):__Synchronous_Controllers__________________________ System___________________Devices_supported_________________________ DEC 3000 Model 300L SCC [1] DEC 3000 Models 300 SCC [1], DSYT1 /300LX/300X DEC 3000 Models 400 SCC, DSYT1 /400S DEC 3000 Models 500 SCC, DSYT1 /500S/500X DEC 3000 Models 600 SCC, DSYT1 /600S DEC 3000 Models SCC, DSYT1 700,700LX DEC 3000 Models 800 SCC, DSYT1 /800S DEC 3000 Models SCC, DSYT1 900,900LX DEC 4000 Models 600 N/A [2] /700 DEC 7000 Model 600 N/A [2] DEC 10000 Model 600 N/A [2] Digital 2100 Server DNSES, PBXDP-Ax A500MP Digital 2100 Server DNSES, PBXDP-Ax A600MP AlphaServer 300 4/266 PBXDI-Ax, PBXDP-Ax AlphaServer 400 4/166 PBXDI-Ax / 4/233 ___________________________________________________________________ [1]Only standard Workstation configurations support use of the SCC. [2]No synchronous communication option available. Connection available only via LLC2. 19 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_3_(Cont.):__Synchronous_Controllers__________________________ System___________________Devices_supported_________________________ AlphaServer 800 5 PBXDP-Ax /333, 5/400, 5/500 AlphaServer 1000 4 DNSES, PBXDP-Ax /233, 4/266, 5/300 AlphaServer 1000A DNSES, PBXDP-Ax 4/233, 4/266, 5/266, 5/333, 5/400, 5/500 AlphaServer 1200 5 DNSES, PBXDP-Ax /333 AlphaServer 2000 4 DNSES, PBXDP-Ax /233, 4/275, 5/250, 5/300 AlphaServer 2100 4 DNSES, PBXDP-Ax /200, 4/233, 4/266, 4/275, 5/250, 5/300 AlphaServer 2100A DNSES, PBXDP-Ax /2100A LP 4/275, 5 /250, 5/300 AlphaServer 4000 5 DNSES, PBXDP-Ax /300, 5/300E, 5/400, 5/466 AlphaServer 4100 5 DNSES, PBXDP-Ax /300, 5/400 AlphaServer 8200 5 DNSES, PBXDP-Ax /300, 5/350, 5/400, 5/440, 5/625 AlphaServer 8400 5 DNSES, PBXDP-Ax /300, 5/350, 5/400, 5/440, 5/625 Digital 2100 Server DNSES, PBXDP-Ax A500MP, A600MP 20 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_3_(Cont.):__Synchronous_Controllers__________________________ System___________________Devices_supported_________________________ DIGITAL Personal PBXDP-Ax, PBXDI-Ax Workstations 500au, 433au, 600au AlphaStation 200 4 PBXDI-Ax, PBXDP-Ax /100, 4/166, 4/233 AlphaStation 250 4 PBXDI-Ax, PBXDP-Ax /266 AlphaStation 255/233, PBXDI-Ax, PBXDP-Ax 255/300 AlphaStation 400 4 PBXDI-Ax, PBXDP-Ax /166, 4/233, 4/266 AlphaStation 500/266, PBXDP-Ax 500/333, 500/400, 500/500 AlphaStation 600 5 DNSES, PBXDP-Ax /266, 5/333 AlphaStation 600A DNSES, PBXDP-Ax 5/500 Alpha 21064/21064A PBXDP-Ax, PBXDI-Ax PCI reference board (EB64+) Alpha 21164 PCI PBXDP-Ax, PBXDI-Ax reference board (EB164) Alpha PC64 reference PBXDP-Ax, PBXDI-Ax board (APC64) Alpha 4/233 PICMG SBC PBXDP-Ax, PBXDI-Ax Alpha 4/266 PICMG SBC PBXDP-Ax, PBXDI-Ax Alpha 5/366 PICMG SBC PBXDP-Ax, PBXDI-Ax Alpha_5/500_PICMG_SBC____PBXDP-Ax,_PBXDI-Ax________________________ 21 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_4:__Synchronous_Controller_Characteristics___________________ Max. Max. HDLC Max.X.25 line data data speed size size Supported interface stan- Device_____(Kbps)___(bytes)__(bytes)[1]dards_______________________ PBXDP- 2x2400, 8300 4096 EIA-232 EIA-422 Ax 4x2400 EIA-423 EIA-530 PCI or V.24/V.28 8x1200 V.35 X.21[2] EIA-485 PBXDI- 2x2400, 8300 4096 EIA-232 Ax 4x2400 EIA-530 ISA V.24/V.28 V.35 X.21[2] DNSES 2x64 4080 2048 EIA-232 EISA or EIA-422 EIA-423 1x2000 V.10/V.11 V.24/V.35 DSYT1 2x64 4080 2048 EIA-232 Turbo or EIA-422 EIA-423 Channel 1x2000 V.10/V.11 V.24/V.35 SCC 19.2 1018 512 EIA-232 V.24 ___________________________________________________________________ [1]Fragmentation of larger data sizes is supported. [2]X.21 electrical levels and connector in data-leads only commu- nication. X.21 call control is not supported. ___________________________________________________________________ 22 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 DISTRIBUTION MEDIA This software and documentation are available on the Compaq CD-ROM Software Library for OpenVMS Alpha. The software documentation is also available in hardcopy format. ORDERING INFORMATION Software Licenses: QL-0THA9-** Software Media/Documentation: QA-03XAA-H8 Software Documentation (hardcopy): QA-0THAA-GZ Software Product Services: QT-0THA*-** * Denotes variant fields. For additional information on available licenses, services, and media, refer to the appropriate price book. SOFTWARE LICENSING Customers who purchased the DIGITAL X.25 Client product (see SPD 46.37.xx) for an OpenVMS Alpha system may upgrade that processor to X.25 for OpenVMS Alpha Version 1.3 at no additional cost. X.25 for OpenVMS Alpha Systems Version 1.3 can be installed and enabled using the same produce authorization key (PAK) received for Compaq X.25 Client for OpenVMS Alpha. Thus the software upgrade of an OpenVMS Alpha system from DECnet and DIGITAL X.25 Client to DECnet-Plus and X.25 requires no new license purchases. This condition in no way supersedes or invalidates Compaq's licensing terms and policies. Specific functions of the X.25 for OpenVMS Alpha product are enabled by the licenses described in Table 5. 23 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 ___________________________________________________________________ Table_5:__Software_Licenses________________________________________ License____________Function_Enabled________________________________ DECnet-Plus CONS over LLC2 and CONS over GAP. CLNS over DEC-HDLC. X.25 for All functions over LAPB and LLC2. OpenVMS Alpha DIGITAL X.25 All functions over LAPB and LLC2. Client for OpenVMS_Alpha______________________________________________________ This software is furnished only under a license. For more information about Compaq's licensing terms and policies, contact your local Compaq office. License Management Facility Support: This layered product supports the OpenVMS Alpha License Management Facility. License units for this product are allocated on an Unlimited System Use basis. For more information on the License Management Facility, refer to the OpenVMS Alpha Operating System Software Product Descrip- tion (SPD 41.87.xx) or documentation. SOFTWARE PRODUCT SERVICES A variety of service options are available from Compaq. For more in- formation, contact your local Compaq office. 24 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 YEAR 2000 READY This product is Year 2000 Ready. "Year 2000 Ready" products are defined by Compaq as products capable of accurately processing, providing and/or receiving date data from, into and between the twentieth and the twenty-first centuries, and the years 1999 and 2000, including leap year calculations, when used in accordance with the associated Compaq product documentation and provided that all hardware, firmware, and software used in combinatio with such Compaq products properly exchange accurate date data with the Compaq products. For additional information visit Compaq's DIGITAL Products Year 2000 Ready website located at http://ww1.digital.com/year2000/status.asp. To ensure that this product is Year 2000 Ready, the following test- ing process/methods were utilized: o Source code was examined manually and with Y2K compliance tools. o Interfaces were tested during a rollover to year 2000. SOFTWARE WARRANTY This software is provided by Compaq with a 90 day comformance warranty in accordance with the Compaq warranty terms applicable to the license purchase. Compaq has designed or adapted this software product to operate with equipment conforming to the ISO standards 7776/8208 and with the pub- lic networks in the associated countries and with certain private PS- DNs that have been tested and approved by Compaq. Compaq cannot offer its standard warranty for this software unless it has been tested with such networks and the software configured appro- priately. Such a testing service is available from Compaq on request, 25 X.25 V1.3 for OpenVMS Alpha Systems SPD 47.37.11 and will permit both full Compaq support of the X.25 for OpenVMS Al- pha product and also ensure that X.25 for OpenVMS Alpha is optimally configured against the PSDN concerned. The presence of a network/country combination in the list of supported public PSDNs indicates Compaq's commitment to support X.25 for OpenVMS Alpha when using that public X.25 service. It does not necessarily imply that network certification by the particular networking authority has been granted for all or any hardware devices supported by the X.25 for OpenVMS Alpha software product. Please contact your local Compaq office for up-to-date information regarding supported configurations and certification status. The above information is valid at time of release. Please contact your local Compaq office for the most up-to-date information. [R] Autonet is a registered trademark of Sanders Associates, Inc. [R] CompuServe is a registered trademark of CompuServe, Inc. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [R] Telenet is a registered trademark of GTE Telenet Communica- tions Corporation. [R] Tymnet is a registered trademark of British Telecommunica- tions PLC. [TM] The Compaq Logo, DEC, DECnet, DECNIS, Digital, OpenVMS, VAX, and VMS are trademarks of Compaq Computer Corporation. ©1999 Digital Equipment Corporation. All Rights Reserved. 26 /* DEC/CMS REPLACEMENT HISTORY, Element X25_V13_SPD.TXT*/ /* *2A1 8-APR-1999 13:43:04 GIBSON "X25_V700_0102 baselevel code freeze"*/ /* *2 8-APR-1999 13:42:57 GIBSON "X25_V700_0102 baselevel code freeze"*/ /* *1 8-APR-1999 13:09:38 GIBSON "Added for V1.3 release kit"*/ /* DEC/CMS REPLACEMENT HISTORY, Element X25_V13_SPD.TXT*/