Software Product Description ___________________________________________________________________ PRODUCT NAME: HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 DESCRIPTION HP X.25 for OpenVMS enables appropriately configured systems to con- nect to an X.25 Packet Switched Data Network (PSDN) via an X.25 Re- lay node on the same Local Area Network (LAN), via a DNA Phase IV X.25 connector node, or directly using a synchronous controller card for Alpha. The product supports communication via PSDNs conforming to ITU/TSS rec- ommendation 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. HP X.25 V2.0 supports OpenVMS Operating System for Alpha version 8.2 and I64 version 8.2 and 8.2-1. X.25 V2.0 for OpenVMS Alpha contains synchronous device drivers and is required when using synchronous com- munications options. Note: HP X.25 for OpenVMS I64 does not support synchronous device drivers and synchronous communications options. HP X.25 for OpenVMS also provides the device drivers and specific data link protocol support for HP's synchronous communications options for OpenVMS Alpha systems. HP X.25 for OpenVMS software allows the system to: o Connect to other X.25 implementations using RFC 1613 (also known as XOT) via a TCP/IP wide area network. o Act as a Gateway Access Protocol (GAP) server for Phase V GAP Clients July 2005 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o Act as an X.25 Connector system for DECnet-Plus X.25 Access sys- tems 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. o Act as a combination of the above, chosen on a per-DTE basis. The following restrictions of HP X.25 for OpenVMS software should be noted: o Phase IV GAP Clients (or access nodes) are not supported. o P.S.I. Access (Phase IV) clients are not supported. 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. o HP X.25 for OpenVMS I64 does not support synchronous device drivers and synchronous communications options. The LAPB configuration is not supported on I64. HP X.25 for OpenVMS supports the following functions: o Process-to-process (HP X.25) communication. X.25 for OpenVMS allows application programs to access X.25 net- work services via the standard OpenVMS QIO system service. 2 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o Process-to-terminal (X.29) communication. Through the X.29 QIO programming interface, users of the OpenVMS system may make outgoing calls to other HP or non-HP systems or suit- able network PADs accessible via a PSDN. o Terminal-to-process (X.29) communication. Remote terminals connected to the PSDN may access the OpenVMS 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 for HP UNIX[R], X.25 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. Note: This function is not applicable for X.25 for OpenVMS I64. o X.25 Relay allows an appropriately configured OpenVMS 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). 3 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o X.25 GAP Server allows remote Phase V GAP clients to connect to a PSDN via the GAP Server node using the DECnet NSP protocol. The re- mote X.25 client (or access node) communicates with the X.25 Server or X.25 Gateway/Connector node using the Gateway Access Protocol (GAP) via a DECnet session connection. o The multi-host mode of operation provides the features offered by VAX P.S.I. Native and also allows VAX P.S.I. Access systems to con- nect to a PSDN as though directly connected. o XOT or X.25 over TCP/IP allows X.25 applications on an appropri- ately configured OpenVMS System to communicate with other RFC 1613 implementations over a TCP/IP Wide Area Network. Features Conformance to Standards HP X.25 for OpenVMS 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 HP X.25 for OpenVMS offers communication over both Permanent Virtual Circuits (PVCs) and Switched Virtual Circuits (SVCs), and supports 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 HP X.25 for OpenVMS. Virtual circuits may use X.25 protocol over a LAN connection, over a WAN synchronous communications connection, or may use HP 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 HP X.25 Client for OpenVMS Alpha Systems with DECnet Gateway Access protocol 4 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 connector nodes. See the HARDWARE REQUIREMENTS section for details of GAP connector nodes and ISO relay nodes supported. Process-to-Process Communication The HP X.25 for OpenVMS programming interface allows application pro- grams 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 Ser- vices to communicate with complementary X.25 software on other HP or non-HP systems. Terminal Communications HP X.25 for OpenVMS supports terminal communications according to ITU/TSS recommendations X.3, X.28, and X.29. Only those terminal parameters defined in the X.3 recommendation are explicitly supported. Network- specific enhancements or extensions to the X.3 parameters are avail- able at both the X.29 programming and the host-based PAD user inter- face. Terminal processes that depend on these extensions may not func- tion 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 ter- minals (character-mode DTEs) connected to the network to communicate with the OpenVMS system in a manner similar to local terminals. The maximum number of terminals supported on a OpenVMS Alpha system (both local and X.29 remote) cannot exceed the number for which the system has been configured. 5 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 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 signaling 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 (out- going 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 HP X.25 for OpenVMS and DECnet-Plus. NCL provides network management facilities to: o Define outgoing call destinations o Define incoming call handling 6 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o Modify X.25 frame and packet levels parameters 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) pro- vided with the OpenVMS operating system. CTF enables the user to trace and analyse frames passing between the PSDN and the X.25 \for OpenVMS systems. In V1.5, the Common Trace Facility (CTF) for OpenVMS X.25 func- tionality has been updated to match the functionality of PSI Trace for the OpenVMS VAX X.25 product. This includes the following capabili- ties: o The ability to trace a circuit given the NWA device name o The ability to trace an X.29 port o The ability to trace an individual X.25L3 circuit Communications Interfaces for Alpha 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 HP X.25 for OpenVMS Alpha Systems, as well as a list of the relay/connector nodes that may be used as X.25 gateways to the LAN. Note: X.25 on I64 does not support synchronous device drivers and syn- chronous communications options. 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 or via TCP/IP using RFC 1613. 7 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 Wide Area Network (WAN) Device Drivers The WAN device drivers included in X.25 for OpenVMS Alpha Systems sup- port synchronous communications. The device drivers all offer a sup- ported 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. Supported controllers for Alpha 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 HP X.25 for OpenVMS supports. Support for any facility is dependent on the PSDN used. The product documentation describes specific facility availability for supported PSDNs. 8 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ 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 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 9 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU/TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 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 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 ___________________________________________________________________ [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. 10 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU/TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 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 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 ___________________________________________________________________ [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. 11 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU/TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 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 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 ___________________________________________________________________ [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. 12 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_1_(Cont.):__Optional_User_Facilities_Support_________________ ITU/TSS X.25 (1988) ref- er- Sup- ence_____Optional_User_Facility_____port[1]________________________ 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 HP recommends that a customer's first purchase of this software prod- uct include HP Installation Services. These services provide for in- stallation of the software product by an experienced HP Software Spe- cialist. Only customers experienced with HP's X.25 products should at- tempt installation. Customer Responsibilities In some cases, the X.25 network supplier may impose restrictions, lim- itations, or requirements on the proposed HP 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 HP's communi- cation equipment. 13 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 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 system to the PSDN and back to the X.25 for OpenVMS system). Systems in Closed User Groups only, or where the PSDN does not support calls to the originating DTE ad- dress, require specially negotiated arrangements for HP to install the product. o Make available for a reasonable period of time, as mutually agreed by HP and the customer, all hardware, communication facilities and terminals that are to be used during a HP supervised installation. HARDWARE REQUIREMENTS Please reference the OpenVMS Alpha and I64 Software Product Descrip- tion (SPD 41.87.XX) for supported hardware. This section lists the Alpha processors that are supported by Open- VMS Alpha Version 8.2. DEC 4000 Model 600/700 series [1] DEC 7000 Model 600 [1] DEC 10000 Model 600 [1] DEC 3000 Model 300/300L/300LX/300X [2] System Memory Required for Alpha In addition to the memory requirements of OpenVMS Alpha and user ap- plications, the minimum memory requirements of HP X.25 for OpenVMS Alpha Systems are: o 2.5 Mbytes for software and data structures ____________________ [1] No synchronous communication option available. Connection available only via LLC2. [2] Only standard workstation configurations support use of the SCC. 14 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 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 o 7 Kbytes for each DTE configured to use XOT System Memory Required for I64 In addition to the memory requirements of OpenVMS I64 and user appli- cations, the minimum memory requirements of HP X.25 for OpenVMS I64 Systems are: o 6.25 Mbytes for software and data structures o 10 Kbytes for each active virtual circuit in a directly connected configuration o 120 Kbytes for each DTE configured to use XOT 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 prod- uct will require less memory than quoted. However, an underconfigured system will display reduced performance, not only for X.25 communi- cations but also for other processes. Communication Devices Required for Alpha HP X.25 for OpenVMS Alpha Systems 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 HP system using DECnet-Plus over DEC-HDLC. The devices available on the supported processors are listed in Ta- ble 4. For additional information on the configuration and performance of these devices see the CONFIGURATION GUIDELINES section. 15 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 For operation using the ISO 8802-2 protocol (LLC2) the product requires a Local Area Network (LAN) device. The product supports HP's ISO 8802- 3 (CSMA/CD) and ISO 9341 (FDDI) devices for use with the LLC2 proto- col. 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 HP UNIX (SPD 42.47.xx) con- figured 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.3 (or later) for OpenVMS VAX configured for X.25 multi- host operation (SPD 25.03.xx). o DECnet-Plus V8.2 (or later) for OpenVMS Alpha (SPD 50.45.xx) For operation using RFC 1613 for X.25 over TCP/IP (XOT), the product requires specific versions of OpenVMS, DECnet-Plus, and TCP/IP Ser- vices for OpenVMS software. See the SOFTWARE REQUIREMENTS section. The TCP/IP software must provide support for the PWIP driver. TCP/IP Ser- vices for OpenVMS and some third-party TCP/IP products provide PWIP driver support. A communication controller appropriate for the TCP/IP software will also be required. For additional information on the configuration and performance of these relay nodes, consult your local hardware service provider and rele- vant Software Product Descriptions. X.25 V2.0 for OpenVMS I64 systems Methods for Communication The X.25 V2.0 release for OpenVMS I64 system provides support for com- munication via: o GAP (X.25 over DECnet) o LLC2 (X.25 over LAN) 16 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o XOT (X.25 over TCP/IP) These methods require an external machine to act as a gateway or re- lay to the X.25 connection or PSDN. This machine provides the inter- face for the actual synchronous line and may be implemented using an OpenVMS Alpha system with a PBXDP or PBXDD synchronous communication controller, or a third party dedicated router. X.25 native communication using a synchronous communication controllers on OpenVMS I64 system will not be supported. For more information please refer to the HP X.25 for OpenVMS-Configuration manual. Disk Space Required ___________________________________________________________________ Table_2:__Disk_Space_Required______________________________________ Alpha The disk space required for installation and use of the product is 15,000 Blocks (7.5 Mbytes) I64 The disk space required for installation and use of the __________product_is_28,752_Blocks_(14.03_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. 17 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 SOFTWARE REQUIREMENTS o OpenVMS Operating System for Alpha Version 8.2 and I64 Versions 8.2 and 8.2-1 o DECnet-Plus for OpenVMS Version 8.2 and 8.2-1 o OpenVMS Alpha and I64 TCP/IP Services V5.5 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 3 shows the public PSDNs supported by the product in the coun- tries shown. In addition, certain private PSDNs have been tested by HP and appropriate profiles have been included with the product. For more detail, consult your local HP office. ___________________________________________________________________ Table_3:__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 ___________________________________________________________________ [1 ]Trademarks under which these services are offered are propri- etary to the respective PTTs. 18 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_3_(Cont.):__Supported_Public_Networks________________________ Country____________Public_Networks[1]______________________________ Eire Eirpac Finland Datapak France Transpac Germany Datex-P Hong Kong Datapak, Inet, Intelpak Indonesia SKDP Ireland Ciepac Italy Itapac 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. 19 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_3_(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 HP X.25 for OpenVMS Systems: o PBXDD-Ax - A range of single slot multi-port (2 and 4) serial synchronous communications PCI adaptors. o PBXDP-Ax (retired December 2000) o PBXDI-Ax - A range of single slot dual port serial synchronous communica- tions ISA adapters. 20 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 o DNSES - Single slot dual port serial synchronous communications EISA adapter. o WANcontroller 720 (DSYT1) - Single slot dual port TURBOchannel serial synchronous communi- cations adapter. - For systems with no available TURBOchannel slots, an extender box may be required. o Integral SCC device - A single port multi-function device on the system motherboard. Only the synchronous communications function is supported. - Limited modem signaling capabilities. Local and remote loopback 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 4. The operational characteristics of each device are given in Table 5. 21 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_4:__Synchronous_Controllers_for_Alpha________________________ System___________________Devices_supported_________________________ DEC 2000 Models DNSES 300/500 DEC 3000 Model 300L SCC [1] DEC 3000 Models SCC [1], DSYT1 300/300LX/300X DEC 3000 Models SCC, DSYT1 400/400S DEC 3000 Models SCC, DSYT1 500/500S/500X DEC 3000 Models SCC, DSYT1 600/600S DEC 3000 Models SCC, DSYT1 700,700LX DEC 3000 Models SCC, DSYT1 800/800S DEC 3000 Models SCC, DSYT1 900,900LX DEC 4000 Models N/A [2] 600/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 ___________________________________________________________________ [1]Only standard Workstation configurations support use of the SCC. [2]No synchronous communication option available. Connection available only via LLC2. 22 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_4_(Cont.):__Synchronous_Controllers_for_Alpha________________ System___________________Devices_supported_________________________ AlphaServer 300 4/266 PBXDI-Ax, PBXDP-Ax AlphaServer 400 PBXDI-Ax 4/166/ 4/233 AlphaServer 800 PBXDP-Ax 5/333, 5/400, 5/500 AlphaServer 1000 DNSES, PBXDP-Ax 4/233, 4/266, 5/300 AlphaServer 1000A DNSES, PBXDP-Ax 4/233, 4/266, 5/266, 5/333, 5/400, 5/500 AlphaServer 1200 DNSES, PBXDP-Ax 5/333 AlphaServer 2100 DNSES, PBXDP-Ax 4/200, 4/233, 4/266, 4/275, 5/250, 5/300 AlphaServer DNSES, PBXDP-Ax 2100A/2100A LP 4/275, 5/250, 5/300 AlphaServer 4000 DNSES, PBXDP-Ax 5/300, 5/300E, 5/400, 5/466 AlphaServer 4100 DNSES, PBXDP-Ax 5/300, 5/400 AlphaServer 8200 DNSES, PBXDP-Ax 5/300, 5/350, 5/400, 5/440, 5/625 AlphaServer 8400 DNSES, PBXDP-Ax 5/300, 5/350, 5/400, 5/440, 5/625 23 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_4_(Cont.):__Synchronous_Controllers_for_Alpha________________ System___________________Devices_supported_________________________ AlphaServer DS10, PBXDP-Ax, PBXDD-Ax DS10L AlphaServer DS20 PBXDP-Ax, PBXDD-Ax AlphaServer DS20E PBXDP-Ax, PBXDD-Ax AlphaServer ES40, PBXDP-Ax, PBXDD-Ax ES45 AlphaServer GS40 PBXDP-Ax, PBXDD-Ax AlphaServer GS60, PBXDP-Ax, PBXDD-Ax GS60E AlphaServer GS80 PBXDP-Ax, PBXDD-Ax AlphaServer GS140 PBXDP-Ax, PBXDD-Ax AlphaServer GS160 PBXDP-Ax, PBXDD-Ax AlphaServer GS320 PBXDP-Ax, PBXDD-Ax Digital 2100 Server DNSES, PBXDP-Ax A500MP, A600MP DIGITAL Personal PBXDP-Ax, PBXDI-Ax Workstations 500au, 433au, 600au AlphaStation 200 PBXDI-Ax, PBXDP-Ax 4/100, 4/166, 4/233 AlphaStation 250 PBXDI-Ax, PBXDP-Ax 4/266 AlphaStation 255/233, PBXDI-Ax, PBXDP-Ax 255/300 AlphaStation 400 PBXDI-Ax, PBXDP-Ax 4/166, 4/233, 4/266 AlphaStation 500/266, PBXDP-Ax 500/333, 500/400, 500/500 24 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_4_(Cont.):__Synchronous_Controllers_for_Alpha________________ System___________________Devices_supported_________________________ AlphaStation 600 DNSES, PBXDP-Ax 5/266, 5/333 AlphaStation 600A DNSES, PBXDP-Ax 5/500 AlphaStation XP1000 PBXDP-Ax 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________________________ 25 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_5:__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 PBXDD- 2x2400, 8300 4096 EIA-232 EIA-449 Ax 4x2400 EIA-530 PCI X.11 V.24/V.35 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. ___________________________________________________________________ 26 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 DISTRIBUTION MEDIA This software and documentation are available on the HP CD-ROM Soft- ware Library for OpenVMS. The software documentation is also avail- able in hardcopy format. ORDERING INFORMATION Alpha: Software Licenses: QL-0THA9-** Software Media/Documentation: QA-03XAA-H8 Software Documentation (hardcopy): QA-0THAA-GZ Software Product Services: QT-0THA*-** I64: Software Licenses: BA390AC Software Media/Documentation: BA390AA Software Documentation (hardcopy): BA390MN * Denotes variant fields. For additional information on available li- censes, services, and media, refer to the appropriate price book. SOFTWARE LICENSING Specific functions of the HP X.25 for OpenVMS product is enabled by the licenses described in Table 6. ___________________________________________________________________ Table_6:__Software_Licenses________________________________________ License____________Function_Enabled________________________________ DECnet-Plus CONS over LAPB, LLC2, GAP, or XOT. CLNS over DEC-HDLC. HP X.25 for All functions over LAPB, LLC2, and XOT. OpenVMS 27 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 ___________________________________________________________________ Table_6_(Cont.):__Software_Licenses________________________________ License____________Function_Enabled________________________________ HP X.25 Client All functions over LAPB and LLC2. for OpenVMS Alpha_Systems______________________________________________________ This software is furnished only under a license. For more information about HP's licensing terms and policies, contact your local HP office. Note: Customers who purchased the HP X.25 Client product (see SPD 46.37.xx) for an OpenVMS Alpha system may upgrade it to HP X.25 for OpenVMS Al- pha Systems, Version 2.0 at no additional cost. HP X.25 for OpenVMS Alpha Systems, Version 2.0 can be installed and enabled using the same product authorization key (PAK) received for HP X.25 Client for OpenVMS Alpha. Thus the software upgrade of an OpenVMS Alpha system from DEC- net and HP X.25 Client to DECnet-Plus and X.25 requires no new license purchases. This condition in no way supersedes or invalidates HP's li- censing terms and policies. 28 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 License Management Facility Support: This layered product supports the OpenVMS Alpha License Management Fa- cility. 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 HP. For more infor- mation, contact your local HP office. SOFTWARE WARRANTY This software is provided by HP with a 90 day conformance warranty in accordance with the HP warranty terms applicable to the license pur- chase. HP has designed or adapted this software product to operate with equip- ment conforming to the ISO standards 7776/8208 and with the public net- works in the associated countries and with certain private PSDNs that have been tested and approved by HP. HP cannot offer its standard warranty for this software unless it has been tested with such networks and the software configured appropri- ately. Such a testing service is available from HP on request, and will permit both full HP support of the X.25 for OpenVMS product and also ensure that X.25 for OpenVMS is optimally configured against the PSDN concerned. The presence of a network/country combination in the list of supported public PSDNs indicates HP's commitment to support X.25 for OpenVMS when using that public X.25 service. It does not necessarily imply that net- work certification by the particular networking authority has been granted 29 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 for all or any hardware devices supported by the X.25 for OpenVMS soft- ware product. Please contact your local HP office for up-to-date in- formation regarding supported configurations and certification sta- tus. © Copyright 2005 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for pos- session, use or copying. Consistent with FAR 12.211 and 12.212, Com- mercial Computer Software, Computer Software Documentation, and Tech- nical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional war- ranty. HP shall not be liable for technical or editorial errors or omis- sions contained herein. 30 HP X.25 for OpenVMS Alpha and I64 Systems, V2.0 SPD 47.37.16 31