               0                                          DIGITAL              Software             Product            Description  N            ___________________________________________________________________  >            PRODUCT NAME:  X.25 V1.0g for OpenVMS Alpha Systems            SPD 47.37.08               DESCRIPTION  N            X.25 for OpenVMS Alpha Systems is a layered product for OpenVMS Al-N            pha systems. It enables appropriately configured systems to connectP            to an X.25 Packet Switched Data Network (PSDN) via an X.25 Relay nodeP            on the same Local Area Network (LAN), via a DNA Phase IV X.25 connec-E            tor node, or directly using a synchronous controller card.   R            The product supports communication via PSDNs conforming to ITU/TSS rec-N            ommendation X.25 1980, 1984, and 1988, or to international standardP            ISO 8208. Refer to the SUPPORTED PUBLIC NETWORKS section for the list            of supported PSDNs.  N            X.25 for OpenVMS Alpha Systems also provides the device drivers andR            specific data link protocol support for Digital Equipment Corporation'sH            synchronous communications options for OpenVMS Alpha systems.  D            X.25 for OpenVMS Alpha allows an OpenVMS Alpha system to:  E            o  Act as a packet-mode DTE connected to a supported PSDN.   C            o  Support ISO 8208 DTE to DTE point-to-point operation.   :            o  Act as a packet-mode DTE connected to a LAN.  Q            o  Provide an X.25 sub-network for DECnet/OSI CONS and CLNS operation.   Q            o  Provide a DEC-HDLC point-to-point data link for DECnet/OSI CLNS op-                eration.  K            o  Act as a combination of the above, chosen on a per-DTE basis.   N                                                                   October 1996           N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    P            The following restrictions of X.25 for OpenVMS Alpha should be noted:  P            o  The multi-host mode of operation available in the VAX P.S.I. prod-"               uct is not provided.  P            o  DCE mode is supported for the purposes of point-to-point operationO               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.  Q            o  Programming interfaces to the data links and device drivers are not                supported.  C            X.25 for OpenVMS Alpha supports the following functions:   6            o  Process-to-process (X.25) communication.O               X.25 for OpenVMS Alpha allows application programs to access X.25 K               network services via the standard OpenVMS QIO system service.   7            o  Process-to-terminal (X.29) communication. N               Through the X.29 QIO programming interface, users of the OpenVMSR               Alpha system may make outgoing calls to other Digital or non-DigitalE               systems or suitable network PADs accessible via a PSDN.   7            o  Terminal-to-process (X.29) communication. O               Remote terminals connected to the PSDN may access the OpenVMS Al- P               pha host running X.25 by means of an X.29 Switched Virtual Circuit               (SVC) call.   8            o  DECnet/OSI Connectionless Network Service.P               The product supports the use of the DEC-HDLC and X.25 protocols asR               sub-networks for the OSI Connectionless-mode Network Service (CLNS).  =            o  DECnet/OSI Connection Oriented Network Service. N               The product supports the OSI Connection Oriented Network Service>               (CONS) for OSI Transport over X.25 sub-networks.              o  X.25 Mail.P               The X.25 Mail utility allows communication across a PSDN via elec-O               tronic mail between two systems running the Mail-11 protocol over N               X.25. Systems that support Mail-11 over X.25 include WAN Support  -                                             2            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    P               for Digital UNIX[R], X.25 for OpenVMS Alpha, X.25 Client for Open-H               VMS, and X.25 installations of DECnet/OSI for OpenVMS VAX.                Features   #            Conformance to Standards   H            X.25 for OpenVMS Alpha complies with the following standards:  P            o  ITU/TSS recommendations-X.25 (1980, 1984, or 1988), X.3, X28, X.29  N            o  international standards ISO-8208, 7776, 8881, 8802/2, 8878, 8473              Virtual Circuits   O            X.25 for OpenVMS Alpha offers communication over both Permanent Vir- N            tual Circuits (PVCs) and Switched Virtual Circuits (SVCs), and sup-R            ports up to 4096 virtual circuits in total per system. One virtual cir-O            cuit is used for each incoming or outgoing X.29 terminal connection, Q            for each X.25 call, and for each DECnet/OSI routing circuit and trans- Q            port connection. The use of PVCs for X.29 communication is not defined R            by the 1980 and 1984 ITU/TSS recommendations, and is not available with"            X.25 for OpenVMS Alpha.  O            Virtual circuits may use X.25 protocol over a LAN connection, over a S            WAN synchronous communications connection or may use Digital X.25 Client N            for OpenVMS Alpha Systems over a DECnet circuit to a DECnet GatewayN            Access Protocol (GAP) connector node. NOTE that there is no supportN            for use of more than 512 of the available virtual circuits by Digi-O            tal X.25 Client for OpenVMS Alpha Systems with DECnet Gateway Access Q            protocol connector nodes. See HARDWARE REQUIREMENTS for details of GAP 9            connector nodes and ISO relay nodes supported.   +            Process-to-Process Communication   N            The X.25 for OpenVMS Alpha programming interface allows applicationO            programs to access X.25 packet level services via the standard Open-             VMS QIO interface.     -                                             3            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    N            Functions include the establishment and clearing of network connec-O            tions, data transmission and reception, sending and receiving of in- R            terrupt messages, and resetting of virtual circuits. The interface alsoO            provides for the segmentation and recombination of messages that are @            longer than the packet size selected for the circuit.  R            This interface enables an application program using OpenVMS System Ser-N            vices to communicate with complementary X.25 software on other sys-0            tems, whether Digital or non-Digital.  "            Terminal Communications  O            X.25 for OpenVMS Alpha supports terminal communications according to O            ITU/TSS recommendations X.3, X.28, and X.29. Only those terminal pa- O            rameters defined in the X.3 recommendation are explicitly supported. P            Network-specific enhancements or extensions to the X.3 parameters areQ            available at both the X.29 programming and the host-based PAD user in- N            terface. Terminal processes that depend on these extensions may notQ            function correctly when used on other PSDNs or when accessing one PSDN ;            via another (for example, international access).   R            The X.29 interactive terminal interface allows remote asynchronous ter-O            minals (character-mode DTEs) connected to the network to communicate P            with the OpenVMS Alpha system in a manner similar to local terminals.N            The maximum number of terminals supported on a OpenVMS Alpha systemN            (both local and X.29 remote) cannot exceed the number for which the&            system has been configured.  O            When using applications designed for interactive, local terminal op- P            erations, transmission delays or PAD parameter settings can cause in-P            consistencies between incoming X.29 traffic and the application's op-P            eration. It may be necessary to make modifications to the application:            user interface or alter PAD parameter settings.  O            The X.29 interface includes a programming capability for the support N            of specific X.29 signalling requirements, including modification of            PAD parameters.              Accounting     -                                             4            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    P            Accounting information is collected and is made available to the user(            via a report writing utility.  O            For incoming X.29 calls, no information can be retrieved relating to >            the process or account onto which a user is logged.              Security   O            An extensive security facility is provided. Control of remote access R            to the system (incoming security) and local access to the network (out-O            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)  8            o  Process (or user) making the outgoing call  4            o  Application handling the incoming call              Network Management   O            The Network Control Language (NCL) is provided for the management of N            X.25 for OpenVMS Alpha and DECnet/OSI. 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  (            o  Define security parameters  *            o  Modify network configuration  +            o  Monitor connection statistics   3            o  Perform network maintenance functions   -                                             5            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    Q            The network manager can be notified of significant network events such O            as security violations or network failures through the event logging             facility.  Q            Problem solving is facilitated by the Common Trace Facility (CTF) pro- Q            vided with the OpenVMS operating system. CTF enables the user to trace O            and analyse frames passing between the PSDN and the X.25 for OpenVMS             Alpha system.  $            Communications Interfaces  O            Refer to the tables in this Software Product Description and consult O            your local hardware service provider for complete information on the O            synchronous controller cards supported by X.25 for OpenVMS Alpha, as O            well as a list of the relay/connector nodes that may be used as X.25             gateways to the LAN.   N            In addition to the devices listed in this Software Product Descrip-Q            tion, operation over CSMA/CD (ISO 8802/3) and FDDI (ISO 9314) networks .            is supported via the LLC2 protocol.  $            Optional Facility Support  R            Table 1 describes the Optional User Facilities of the 1988 ITU/TSS X.25@            recommendations that X.25 for OpenVMS Alpha supports.  N            Support for any facility is dependent on the PSDN used. The productO            documentation describes specific facility availability for supported             PSDNs.                         -                                             6            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    N            ___________________________________________________________________  N            Table_1:__Optional_User_Facilities_Support_________________________              ITU            /TSS             X.25             (1988)             ref- 0            er-                              Sup-N            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   /            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  N            ___________________________________________________________________M            [1]Refers to those features of a facility that are relevant to the J            operation of a DTE. "n/a" refers to DCE facilities requiring no            action from the DTE.   -                                             7            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_1_(Cont.):__Optional_User_Facilities_Support_________________              ITU            /TSS             X.25             (1988)             ref- 0            er-                              Sup-N            ence____Optional_User_Facility___port[1]___________________________  /            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   /            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   N            ___________________________________________________________________M            [1]Refers to those features of a facility that are relevant to the J            operation of a DTE. "n/a" refers to DCE facilities requiring no            action from the DTE.   -                                             8            N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_1_(Cont.):__Optional_User_Facilities_Support_________________              ITU            /TSS             X.25             (1988)             ref- 0            er-                              Sup-N            ence____Optional_User_Facility___port[1]___________________________  /            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   1            6.24    Hunt group               no[2]   /            6.25.1  Call redirection         n/a   .            6.25.2.2Call deflection selec-   no                    tion   /            6.25.3  Call redirection or      yesf*                    call deflection notifi-                    cation_  .            6.26    Called line address      no(                    modified notification  /            6.27    Transit delay selection  yes4!                    and indication   N            ___________________________________________________________________M            [1]Refers to those features of a facility that are relevant to the J            operation of a DTE. "n/a" refers to DCE facilities requiring no            action from the DTE.l  K            [2]The individual DTEs must be assigned addresses independent ofi"            the hunt group address.  -                                             9n t         N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_1_(Cont.):__Optional_User_Facilities_Support_________________              ITU            /TSSi            X.25i            (1988)             ref-n0            er-                              Sup-N            ence____Optional_User_Facility___port[1]___________________________  .            6.28    TOA/NPI address selec-   no&                    tion and indication  /            7.1     Non-X.25 facilities      yesN  /            G.3.1   Calling Address Exten-   yesn                    sion   /            G.3.2   Called Address Exten-    yes                     sionr  /            G.3.3.1 Minimum throughput       yesL                    class  /            G.3.3.2 End-to-end transit       yeso                    delay  /            G.3.3.3 Priority                 yesi  /            G.3.3.4 Protection               yes   /            G.3.4   Expedited data negotia-  yes                     tion6N            ___________________________________________________________________M            [1]Refers to those features of a facility that are relevant to thelJ            operation of a DTE. "n/a" refers to DCE facilities requiring no            action from the DTE. N            ___________________________________________________________________              INSTALLATIONe  O            Digital recommends that a customer's first purchase of this software P            product include Digital Installation Services. These services provide  .                                             10 c  t      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    S            for installation of the software product by an experienced Digital Soft-eP            ware Specialist. Only customers experienced with Digital's X.25 prod-,            ucts should attempt installation.  $            Customer Responsibilities  Q            In some cases, the X.25 network supplier may impose restrictions, lim- O            itations, or requirements on the proposed Digital network configura- Q            tion. The customer must ensure these are understood and adhered to for             each network.  D            Before installation of the software, the customer should:  P            o  Previously have installed all requisite software and hardware, in-                cluding terminals.  R            o  Obtain, install, and demonstrate as operational any modems and otherO               equipment and facilities necessary to interface to Digital's com- #               munication equipment.h  S            o  Demonstrate equivalence of operation for modems other than Bell 208A,-P               208B, 209, 212A synchronous modems, or, in Europe, employ only PTT               approved modems.  O            o  Subscribe to the Open User Group and to at least two SVCs to com-fO               plete the product's installation checkout (this test loops infor- P               mation from the X.25 for OpenVMS Alpha system to the PSDN and backR               to the X.25 for OpenVMS Alpha system). Systems in Closed User GroupsO               only, or where the PSDN does not support calls to the originating N               DTE address, require specially negotiated arrangements for Digi-.               tal installation of the product.  P            o  Make available for a reasonable period of time, as mutually agreedN               by Digital and the customer, all hardware, communication facili-P               ties and terminals that are to be used during a Digital supervised               installation.           .                                             11 i  -      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08                 HARDWARE REQUIREMENTS              Processors Supported   *            Alpha:   DEC 2000 Model 300/5007                     DEC 3000 Model 300/300L/300X/300LX,i,                     DEC 3000 Model 400/400S,1                     DEC 3000 Model 500/500S/500X,c,                     DEC 3000 Model 600/600S,'                     DEC 3000 Model 700,r,                     DEC 3000 Model 800/800S,&                     DEC 3000 Model 9005                     DEC 4000 Model 600/700 series [1]n5                     DEC 7000 Model 600/700 series [1]e6                     DEC 10000 Model 600/700 series [1]*                     AlphaServer 8200 5/300*                     AlphaServer 8400 5/3004                     Digital 2100 Server Model A500MP4                     Digital 2100 Server Model A600MP;                     AlphaServer 2100 4/{200/233/275}, 5/250O0                     AlphaServer 2000 4/{200/233}0                     AlphaServer 1000 4/{200/233})                     AlphaServer 400 4/166 *                     AlphaStation 600 5/300*                     AlphaStation 400 4/233*                     AlphaStation 250 4/2664                     AlphaStation 200 4/{100/166/233}N            ___________________________________________________________________L            [1]No synchronous communication option available. Connection only            available via LLC2.  !            System Memory Requiredc  O            In addition to the memory requirements of OpenVMS Alpha and user ap-tN            plications, the minimum memory requirements of X.25 for OpenVMS Al-            pha are:   :            o  2.5 Mbytes for software and data structures;      .                                             12 s  c      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    N            o  40 Kbytes for each active virtual circuit in a Client configura-               tion; andc  O            o  10 Kbytes for each active virtual circuit in a directly connectedn               configuration.  N            These figures represent an upper bound only and should be used as aS            guide to sizing a system to provide adequate X.25 performance. The prod-oP            uct will require less memory than quoted. However, an underconfiguredN            system will display reduced performance, not only for X.25 communi-0            cations but also for other processes.  )            Communication Devices Requiredd  S            X.25 for OpenVMS Alpha requires one or more synchronous controller cardse;            when directly connected to one of the following:t  +            o  A PSDN via the X.25 protocol;   ;            o  Another system using DECnet/OSI over X.25; ora  D            o  Another Digital system using DECnet/OSI over DEC-HDLC.  N            The devices available on the supported processors are listed in Ta-Q            ble 3. For additional information on the configuration and performancelE            of these devices see the CONFIGURATION GUIDELINES section.i  R            For operation using the ISO 8802-2 protocol (LLC2) the product requiresP            a Local Area Network (LAN) device. The product supports Digital's ISOR            8802-3 (CSMA/CD) and ISO 9341 (FDDI) devices for use with the LLC2 pro-            tocol.   S            For operation over LLC2 to an X.25 relay node, the supported relay nodesh            are  4            o  DEC X.25gateway 100/500 (SPD 32.97.xx)  L            o  DEC Network Integration Server (DECNIS) 500/600 (SPD 36.05.xx)  N            o  Alpha system running WAN Support for Digital UNIX (SPD 42.47.xx)'               configured for X.25 relaya  .                                             13 s         N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    N            For operation over DECnet (using the Gateway Access Protocol, GAP),-            the supported connector nodes are:n  5            o  DEC X.25gateway 100/500 (SPD 32.97.xx);   M            o  DEC Network Integration Server (DECNIS) 500/600 (SPD 36.05.xx);   A            o  X25router 2000 or X25router 100 (SPD 28.86.xx); andy  S            o  DECnet/OSI V6.2 (or later) for OpenVMS VAX configured for X.25 multi-d,               host operation (SPD 25.03.xx).  S            For additional information on the configuration and performance of thesenN            relay nodes, consult your local hardware service provider and rele-.            vant Software Product Descriptions.              Disk Space Required  T            The disk space required for installation and use of the product is 15,000            Blocks (7.5 Mbytes).   O            This size is approximate. The actual size will vary depending on the J            user's system environment, configuration, and software options.              OPTIONAL HARDWARE  N            Additional communications devices, subject to limitations described?            in the CONFIGURATION GUIDELINES section of this SPD.a               SOFTWARE REQUIREMENTS  =            OpenVMS Alpha Operating System V6.2 (SPD 41.87.xx) D            DECnet/OSI V6.2 or V6.3 for OpenVMS Alpha (SPD 50.45.xx).               GROWTH CONSIDERATIONS  P            The minimum hardware and software requirements for any future versionN            of this product may be different from the requirements for the cur-            rent version.    .                                             14           N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    $            SUPPORTED PUBLIC NETWORKS  O            Table 2 shows the public PSDNs supported by the product in the coun-2N            tries shown. In addition, certain private PSDNs have been tested byP            Digital and appropriate profiles have been included with the product.>            For more detail, consult your local Digital office.  N            ___________________________________________________________________  N            Table_2:__Supported_Public_Networks________________________________  N            Country___________Public_Networks[1]_______________________________  "            Argentina         Arpac$            Australia         Austpac$            Austria           Datex-P             Belgium           DCS#            Brazil            Renpac 0            Canada            Datapac, Infoswitch#            Chile             VTRnet $            Denmark           Datapak#            Eire              Eirpac $            Finland           Datapak%            France            TranspacX$            Germany           Datex-P4            Hong Kong         Datapak, Inet, Intelpak!            Indonesia         SKDP #            Ireland           CiepacO#            Italy             Itapac N            Japan             CC-VAN, DDX-P 80/84, Jaisnet, Tymnet[R], Venus LP#            Luxembourg        Luxpacb#            Malaysia          Maypace$            Mexico            Telepac&            Netherlands       Datanet 1#            New Zealand       Pacnetf$            Norway            DatapakN            ___________________________________________________________________L            [1 ]Trademarks under which these services are offered are propri-(            etary to the respective PTTs.    .                                             15           N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_2_(Cont.):__Supported_Public_Networks________________________  N            Country___________Public_Networks[1]_______________________________  #            Pakistan          Paknet_$            Philippines       Datanet$            Portugal          Telepac$            Singapore         Telepac%            South Korea       Dacomnets$            Spain             Iberpac0            Sweden            Datapak, Datapak II$            Switzerland       Telepac#            Taiwan            Pacnet $            Thailand          Thaipak#            Turkey            Turpakl5            United Kingdom    PSS[2], Postgem, Mercuryc?            United States     Accunet, Autonet[R], Bell AtlanticO3                              CompuServe[R], ConnNetm4                              FedexITC, FreedomNet II,                              Impacs, Infonet6                              Mark*Net Extended Service0                              Pacific Bell PPSnet0                              Pulsenet, Sprintnet/                              Telenet[R], Tymneta,                              US West Digipac0                              Western Union PTN-1%                              Worldnet   N            ___________________________________________________________________L            [1 ]Trademarks under which these services are offered are propri-(            etary to the respective PTTs.  L            [2 ]PSS is only supported when the Extended Facilities option has            been subscribed. N            ___________________________________________________________________          .                                             16 F  l      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    #            CONFIGURATION GUIDELINES   N            For direct connection of the Alpha system to the PSDN, operation ofT            the product requires the use of one or more synchronous controller cards.Q            The following devices are supported by X.25 for OpenVMS Alpha Systems:   !            o  Integral SCC deviceu  O               o  A single port multi-function device on the system motherboard.iK                  Only the synchronous communications function is supported.l  N               o  Limited modem signalling capabilities. Local and remote loop-E                  back signals and DTE-sourced clock are not provided.1  '            o  WANcontroller 720 (DSYT1)   O               o  Single slot dual port TURBOchannel serial synchronous communi- !                  cations adapter.   N               o  For systems with no available TURBOchannel slots, an extender%                  box may be required.c              o  DNSES.  V               o  Single slot dual port serial synchronous communications EISA adapter.              o  PBXDI-Ax  O               o  A range of single slot dual port serial synchronous communica-_$                  tions ISA adapters.              o  PBXDP-Ax  N               o  A range of single slot multi-port serial synchronous communi-&                  cations PCI adapters.  O            Additional factors to consider when configuring hardware devices for #            use with the product are   S            o  Hardware configuration limits, such as power supply, backplane space,_N               bus throughput, mapping registers, and any other restrictions onP               the number of devices per CPU or per bus must be observed. ConsultK               your local hardware service provider for further information.   .                                             17 s  F      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    O            o  CPU utilisation. Ensure sufficient CPU power will be available tonP               drive the required number of lines at the desired speeds and leave;               sufficient margin for application processing.   O            The supported devices available on each system are given in Table 3. O            The operational characteristics of each device are given in Table 4..  N            ___________________________________________________________________  N            Table_3:__Synchronous_Controller_Cards_____________________________  N            System__________________Devices_supported__________________________  $            DEC 10000 Model 6*0     -            /7*0m  $            DEC 7000 Model 6*0      -            /7*0s  $            DEC 4000 Model 6*0      -            /7*0   1            AlphaServer 8400,       DNSES/PBXDP-Ax_            8200_  -            DEC 3000 Model 900      SCC, DSYT1a  -            DEC 3000 Model 800      SCC, DSYT1a            /800S  -            DEC 3000 Model 700      SCC, DSYT1   -            DEC 3000 Model 600      SCC, DSYT1i            /600S  -            DEC 3000 Model 500      SCC, DSYT1t            /500S/500X   -            DEC 3000 Model 400      SCC, DSYT1             /400S  1            DEC 3000 Model 300      SCC [1], DSYT1             /300X  1            DEC 3000 Model 300LX    SCC [1], DSYT1_  N            ___________________________________________________________________I            [1]Only standard Workstation configurations support use of the             SCC.   .                                             18           N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_3_(Cont.):__Synchronous_Controller_Cards_____________________  N            System__________________Devices_supported__________________________  *            DEC 3000 Model 300L     SCC [1]  (            DEC 2000 Model 300      DNSES  (            DEC 2000 Model 500      DNSES  1            Digital 2100 Server     DNSES/PBXDP-Ax             A500MP   1            Digital 2100 Server     DNSES/PBXDP-Ax             A600MP   1            AlphaServer 1000        DNSES/PBXDP-Ax   1            AlphaServer 2000        DNSES/PBXDP-Ax   1            AlphaServer 2100        DNSES/PBXDP-Ax_  4            AlphaServer 400         PBXDI-Ax/PBXDP-Ax  +            AlphaStation 200        PBXDI-Ax   +            AlphaStation 250        PBXDI-Ax.  4            AlphaStation 400        PBXDI-Ax/PBXDP-Ax  1            AlphaStation 600        DNSES/PBXDP-Ax_N            ___________________________________________________________________I            [1]Only standard Workstation configurations support use of thew            SCC.pN            ___________________________________________________________________  N            ___________________________________________________________________  N            Table_4:__Synchronous_Controller_Card_Characteristics______________                                Max.,                      Max.   HDLC    Max.X.25(                      line   data    data(                      speed  size    sizeN            Device____(Kbps)_(bytes)_(bytes)[Supported_interface_standards_____  8            SCC       19.2   1018    512     EIA-232 V.24  N            ___________________________________________________________________>            [1]Fragmentation of larger data sizes is supported.  .                                             19           N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_4_(Cont.):__Synchronous_Controller_Card_Characteristics______                                Max.,                      Max.   HDLC    Max.X.25(                      line   data    data(                      speed  size    sizeN            Device____(Kbps)_(bytes)_(bytes)[Supported_interface_standards_____  3            DSYT1     2x64   4080    2048    EIA-232 ;                      or                     EIA-422 EIA-423s5                      1x2000                 V.10/V.11o5                                             V.24/V.35c  3            DNSES     2x64   4080    2048    EIA-232f;                      or                     EIA-422 EIA-423 5                      1x2000                 V.10/V.11e5                                             V.24/V.35t  3            PBXDI-    2x2400, 8300   4096    EIA-232 3            Ax        4x2400                 EIA-530r5                                             V.24/V.28 0                                             V.354                                             X.21 [2]  ;            PBXDP-    2x2400, 8300   4096    EIA-232 EIA-422n;            Ax        4x2400                 EIA-423 EIA-530d5                      or                     V.24/V.28n0                      8x1200                 V.358                                             X.21 EIA-485N            ___________________________________________________________________>            [1]Fragmentation of larger data sizes is supported.  L            [2]X.21 electrical levels and connector in data-leads only commu-8            nication. X.21 call control is not supported.N            ___________________________________________________________________              DISTRIBUTION MEDIA0  N            This software and documentation are available on the Digital CD-ROMQ            Software Library for OpenVMS Alpha. The software documentation is also )            available in hard-copy format.1  .                                             20 s  ]      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08                ORDERING INFORMATIONS  )            Software Licenses: QL-0THA9-**a4            Software Media/Documentation: QA-03XAA-H89            Software Documentation (hardcopy): QA-0THAA-GZh1            Software Product Services: QT-0THA*-**S  Q            *  Denotes variant fields. For additional information on available li- O               censes, services, and media, refer to the appropriate price book.               SOFTWARE LICENSING   U            Customers who purchased the Digital X.25 Client product (see SPD 46.37.xx)_S            for an OpenVMS Alpha system may upgrade that processor to X.25 for Open-oN            VMS Alpha at no additional cost. X.25 for OpenVMS Alpha Systems canO            be installed and enabled using the same license management key (PAK)eP            received for Digital X.25 Client for OpenVMS Alpha. Thus the softwareQ            upgrade of an OpenVMS Alpha system from DECnet and Digital X.25 ClientrN            to DECnet/OSI and X.25 requires no new license purchases, presumingO            the original licenses are within warranty or covered by Digital ser- Q            vice contract. This condition in no way supersedes or invalidates Dig-o/            ital's licensing terms and policies.o  O            Specific functions of the X.25 for OpenVMS Alpha product are enabled 0            by the licenses described in Table 5.  N            ___________________________________________________________________  N            Table_5:__Software_Licenses________________________________________  N            License___________Function_Enabled_________________________________  M            DECnet/OSI        CONS over LLC2 and CONS over GAP. CLNS over DEC- "                              HDLC.  >            X.25 for Open-    All functions over LAPB and LLC2.            VMS Alpha        .                                             21 t  t      N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08  N            ___________________________________________________________________  N            Table_5_(Cont.):__Software_Licenses________________________________  N            License___________Function_Enabled_________________________________  >            Digital X.25      All functions over LAPB and LLC2.            Client forTN            OpenVMS_Alpha______________________________________________________  P            This software is furnished only under a license. For more informationP            about Digital's licensing terms and policies, contact your local Dig-            ital office.   /            License Management Facility Support:n  Q            This layered product supports the OpenVMS Alpha License Management Fa-             cility.  N            License units for this product are allocated on an Unlimited SystemN            Use basis. For more information on the License Management Facility,P            refer to the OpenVMS Alpha Operating System Software Product Descrip-0            tion (SPD 41.87.xx) or documentation.  $            SOFTWARE PRODUCT SERVICES  P            A variety of service options are available from Digital. For more in-8            formation, contact your local Digital office.              SOFTWARE WARRANTY  R            Warranty for this software product is provided by Digital with the pur-Q            chase of a license for the product as defined in the Software Warranty0             Addendum of this SPD.  P            Digital has designed or adapted this software product to operate withP            equipment conforming to the ISO standards 7776/8208 and with the pub-P            lic networks in the associated countries and with certain private PS-=            DNs that have been tested and approved by Digital.       .                                             22 D         N            X.25 V1.0g for OpenVMS Alpha Systems                   SPD 47.37.08    N            Digital cannot offer its standard warranty for this software unlessP            it has been tested with such networks and the software configured ap-O            propriately. Such a testing service is available from Digital on re- Q            quest, and will permit both full Digital support of the X.25 for Open- O            VMS Alpha product and also ensure that X.25 for OpenVMS Alpha is op- 9            timally configured against the PSDN concerned.6  Q            The presence of a network/country combination in the list of supportedxP            public PSDNs indicates Digital's commitment to support X.25 for Open-O            VMS Alpha when using that public X.25 service. It does not necessar-rP            ily imply that network certification by the particular networking au-P            thority has been granted for all or any hardware devices supported byO            the X.25 for OpenVMS Alpha software product. Please contact your lo-EQ            cal Digital office for up-to-date information regarding supported con- 0            figurations and certification status.  Q            The above information is valid at time of release. Please contact youreD            local Digital office for the most up-to-date information.  L            [R] Autonet is a registered trademark of Sanders Associates, Inc.  G            [R] CompuServe is a registered trademark of CompuServe, Inc.r  L            [R] UNIX is a registered trademark in the United States and otherK                countries, licensed exclusively through X/Open Company, Ltd.   N            [R] Telenet is a registered trademark of GTE Telenet Communications                Corporation.   M            [R] Tymnet is a registered trademark of British Telecommunicationsh                PLC.   L            [TM]The DIGITAL Logo, DEC, DECnet, DECNIS, Digital, OpenVMS, VAX,G                and VMS are trademarks of Digital Equipment Corporation.   E             1995 Digital Equipment Corporation. All Rights Reserved.o          .                                             23