                            Software           Product            Description   J           ________________________________________________________________  H           PRODUCT NAME:  VAX Packetnet System Interface     SPD 27.78.02-                          Access, Version  4.3              DESCRIPTION   G           The VAX Packetnet System Interface Access (VAX P.S.I. Access) J           product allows a suitably configured DECnet-VAX system in a DEC-I           net environment to make logical connections to Packet Switching G           Data Networks (PSDNs) by using one or more connector node(s). G           VAX P.S.I. Access, with the connector node providing physical I           connection(s) to a PSDN(s), enables process-to-process and ter- G           minal communications between the Access system and the remote (           Data Terminal Equipment (DTE).  9           The connector node may be any of the following:   H           o  An X25router 2000 product (refer to X25router 2000 Software0              Product Description SPD 28.86.xx ).  E           o  VAX P.S.I.  configured in Multi-host mode (refer to VAX  K              Packetnet System Interface P.S.I. Software Product Description               SPD 25.40.xx).   H           DECnet logical links are established by VMS to connect the VAXG           P.S.I. Access node to the connector node. These links may use I           any supported DECnet communications path between the VAX P.S.I. I           Access node and the connector node, provided they themselves do H           not use an X.25 connection. VAX P.S.I. Access uses these linksJ           to transmit X.25 or X.29 messages between the connector node and%           the VAX P.S.I. Access host.       J                                        DIGITAL                   July 1990  J                                                                AE-KK33C-TE         J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      H           Note that successful use of an X.29 connection, either for in-E           coming X.29 calls or by means of the host-based PAD utility H           supplied with VAX P.S.I. Access, depends on the DECnet circuitF           between the Access and connector nodes having a low responseJ           time. This requires high-speed DECnet connections and few inter-            mediate routing nodes.  D           A single VAX P.S.I. Access host can connect to one or moreD           connector nodes concurrently, and hence access all PSDN(s)J           accessible from those connector nodes. When VAX P.S.I. Access isH           installed, one of these connector nodes/PSDN combinations mustH           be established as the default gateway for outbound and inbound           traffic.             Features  G           VAX P.S.I. Access is a VMS layered product and can be used in            the following ways:   4           o  Process-to-process (X.25) communication  5           o  Process-to-terminal (X.29) communication   5           o  Terminal-to-Process (X.29) communication   (           o  Open System Interconnection  1           Process-to-process (X.25) Communication   I           VAX P.S.I. Access supports access for VMS user programs written G           in VAX MACRO and native mode high-level languages such as VAX I           FORTRAN. Programs executing in PDP-11 compatibility mode cannot             use VAX P.S.I. Access.  H           The VAX P.S.I. Access programming interface allows applicationJ           programs to access the service interface to the packet level viaG           the standard VMS QIO interface. Functions include the setting G           up and breaking of network connections, data transmission and I           reception, sending and receiving of interrupt messages, and re- J           setting of virtual circuits. The interface also allows splitting  +                                           2          J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      F           and recombining of messages which are longer than the packet(           size selected for the circuit.  H           The programming interface enables an application program usingH           VMS System Services to communicate with complementary softwareG           on other systems (Digital or non-Digital DTEs) accessible via            the X.25 connection.  G           Process-to-terminal and Terminal-to-process (X.29) Communica-            tion  I           VAX P.S.I. Access supports terminal communications according to 8           CCITT recommendations X.3, X.28, and X.29 for:  &           o  Outgoing terminal traffic  D              VAX P.S.I. Access host users may make outgoing calls toH              other Digital or non-Digital CPUs, or suitable network PADsH              accessible via a PSDN, using the X.29 programming interfaceI              or by using the host-based Packet Assembly/Disassembly (PAD) F              supplied with VAX P.S.I. Access. The PAD facility accepts7              DCL-style commands or CCITT X.28 commands.   &           o  Incoming terminal traffic  H              The X.29 Interactive Terminal Interface allows remote asyn-F              chronous terminals (character-mode DTEs) connected to theH              network to communicate with the VAX P.S.I. Access host in aJ              manner similar to local terminals. Dissimilarities may appearH              as a result of delays caused by the PSDN(s) and the variousI              PAD parameter settings chosen by the user or peculiar to the I              PSDN(s). In this case, the remote PAD must perform code con- H              versions between ASCII and the code the terminal uses. NoteH              that there may be some restrictions imposed by the PSDN(s).  G           Terminal parameters defined in the X.3 recommendation are ex- I           plicitly supported. Network-specific enhancements or extensions J           to the X.3 parameters are available at both the X.29 programmingH           interface and the host-based PAD user interface. Terminal pro-H           cesses that depend on these extensions may cause problems when  +                                           3          J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      I           used on other PSDNs or when accessing one PSDN via another (for )           example, international access).   I           The X.29 terminal interface is compatible with the local termi- H           nal interface, except for those facilities where the PSDN doesH           not provide adequate support. The X.29 interface includes sup-F           port for specific X.29 signaling. For example, the break keyI           can be used to disable output, and the interrupt message can be 9           mapped directly to the VMS interrupt character.   H           The host-based PAD employs a DCL-style command syntax offeringI           the ability to reference the CCITT PAD parameters symbolically, E           as well as an interface that conforms to the standard CCITT H           command signals. The host-based PAD also offers the capabilityJ           of running multiple X.29 sessions using the VMS SPAWN and ATTACHH           commands. The host-based PAD supports reception of reselectionG           messages to allow X.29 calls to be redirected to another DTE.   I           The X.29 programming interface is similar to the X.25 interface F           and allows a VMS process to control the virtual circuit (forF           example, to modify PAD parameters or clear a call). The X.29I           programming interface can also be used to make an outgoing call I           to a remote PAD. The programming interface allows generation of #           PAD reselection messages.   J           The maximum number of terminals supported (both local and remoteD           X.29) must not exceed the number supported by VMS. The useE           of PVCs for X.29 connections is not defined by the 1980 and I           1984 CCITT recommendations and is not available with VAX P.S.I.            Access.   %           Open System Interconnection   G           VAX P.S.I. Access may be used for Open System Interconnection E           (OSI) communication using the OSI Applications Kernel prod-_G           uct (OSAK). Refer to the VAX OSI Applications Kernel Softwaren-           Product Description (SPD 27.47.xx).     +                                           4          J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      G           VAX P.S.I. Access may also be used with VAX FTAM for managing C           files on open systems (refer to VAX FTAM Software Product D           Description SPD 29.86.xx), and with the VAX Message RouterH           X.400 Gateway to enable message exchange with other X.400 sys-I           tems in X.400 public or private networks. Refer to the VAX Mes- E           sage Router X.400 Gateway Software Product Description (SPD            27.50.xx).  I           VAX P.S.I. Access also provides features of X.25 which permit a I           Connection Oriented Network Service (CONS) over X.25, accordinge           to ISO 8348.             Virtual Circuits  D           VAX P.S.I. Access supports both Permanent Virtual CircuitsH           (PVCs) and Switched Virtual Circuits (SVCs) from the connectorI           node, and supports up to 512 virtual circuits in total per hostb8           machine. One virtual circuit is used for each:  :           o  Incoming or outgoing X.29 terminal connection  2           o  X.25 call, using either an SVC or PVC  E           VAX P.S.I. and VAX P.S.I. Access Running on the Same Systemm  E           In a network consisting of more than one connector node in-tE           volving one or more VAX P.S.I. Multi-host nodes, users on anI           Multi-host node may need to gain access to PSDN(s) connected to I           another connector node. This is accomplished by installing both J           VAX P.S.I. and VAX P.S.I. Access on the same node in combination           mode.k             Configurations  F           VAX P.S.I. Access provides a configuration procedure to con-H           figure a VAX P.S.I. Access system locally. This allows networkH           managers to create a configuration after initial installation,<           or subsequently when reconfiguration is necessary.      +                                           5  i       J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02                 Network Management  E           VMS provides a Network Control Program (NCP) for managementeG           of both DECnet-VAX and VAX P.S.I. This program allows networkhH           managers to define the line(s) and PSDN(s) to which the systemE           is connected, select the mode (DTE or DCE) of each, specifydG           destinations for incoming calls, access counters, and perform &           other maintenance functions.             Problem Solvingu  J           The TRACE utility assists problem solving by tracing and analyz-J           ing information at various stages as it passes between the PSDN,J           the connector node and the VAX P.S.I. Access node. Event logging9           is available by means of normal VMS mechanisms.s             P.S.I. Accountingo  E           The P.S.I. Accounting utility enables the system manager torH           obtain information on VAX P.S.I. Access and network usage. TheI           P.S.I. Accounting utility can extract the information collectedcI           and display the information directly on a terminal or write the J           information to a file. Information can be extracted for selectedI           records or a summary produced. The P.S.I. Accounting utility ist5           compatible with the VMS Accounting utility.d  J           In the case of incoming X.29 calls, no information can be storedI           relating to the process/account on which a user is logged; thisfJ           can be obtained through correlation with VMS accounting records.  D           On a VAX P.S.I. Access node, the P.S.I. Accounting utilityJ           records details of calls to and from the Access node only. ReferG           to the appropriate SPD for the connector node for  details of ,           the accounting features available.  G           If the connector node is a VAX P.S.I. Multi-host node, P.S.I.oI           Accounting should also be used at the Multi-host node to gatheraD           comprehensive accounting data. Refer to the VAX P.S.I. SPDH           (25.40.xx) for more information about the available accounting           features.   +                                           6o n  t    J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02                 P.S.I. Securitya  G           The P.S.I. Security utility allows control of both remote DTEoG           access to VAX P.S.I. Access, and access to the PSDN(s) by VMSsJ           processes. The Security utility allows for access control on the           basis of:i  D           o  The remote DTE numbers involved, either on the basis ofH              individual DTE numbers or groups of DTE numbers with common              leading digitsm  D           o  The process making the outgoing call or the application'              handling the incoming calle  C           o  Whether or not the call is normally or reverse chargedc  G           On a VAX P.S.I. Access node, the P.S.I. Security utility per-hE           forms security checks for calls to and from the Access nodeeG           only. Refer to the appropriate SPD for the connector node ford5           details of the security features available.n  G           If the connector node is a VAX P.S.I. Multi-host node, P.S.I.eH           Security should also be used at the Multi-host node to provideH           comprehensive security. P.S.I. Security on a VAX P.S.I. Multi-I           host node checks both incoming and outgoing calls for the rightnF           to communicate with the VAX P.S.I. Access node. Refer to theI           VAX P.S.I. Software Product Description (SPD 25.40.xx) for morev<           information about the available security features.             P.S.I. Mailn  H           The P.S.I. Mail utility allows communication across a PSDN viaH           electronic mail between two VMS systems running VAX P.S.I. or L           VAX P.S.I. Access, using the VMS Mail facility even in the absenceJ           of any DECnet communications between the two DTEs. Refer to the J           VMS Operating System Software Product Description (SPD 25.01.xx)/           for more  information about VMS Mail.t  "           Conformance to Standards  +                                           7     o    J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      D           Please refer to appropriate SPD for the connector node forB           details of the standards and protocol options supported.             PREREQUISITE SUPPORT  I           The customer and Digital must jointly prepare a Network Profile E           and Customer Support Plan covering all the intended networkyH           nodes, their usage of SVCs, PVCs and other network facilities,F           and their support. Without this Network Profile and CustomerG           Support Plan, Digital cannot support the network connections.P  F           Support services for VAX P.S.I. Access require that a corre-E           sponding or a greater level of service are obtained for the !           connector node(s) used..             INSTALLATION  I           Digital requires that a customer's first purchase of this soft-oH           ware product include Digital Installation Services. These ser-F           vices provide for installation of the software product by an2           experienced Digital Software Specialist.  H           Only customers experienced with Digital's X.25 products shouldH           attempt second or subsequent installations. Digital recommendsG           that all other customers purchase Digital's Installation Ser-b           vices.  #           Customer Responsibilities   A           Before installation of the software, the customer must:d  J           o  Previously have installed all required software and hardware,!              including terminals.   J           o  Obtain, install and demonstrate that both the connection fromH              the connector node to the PSDN and the DECnet connection to0              the connector node are operational.  G           o  Check the requirements for the connector node installation 5              from the appropriate connector node SPD.k  +                                           8  7  2    J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      H           o  Make available for a reasonable period of time, as mutuallyG              agreed by Digital and the customer, all hardware, communi-.G              cation facilities and terminals that are to be used duringe              installation.  H           Delays caused by any failure to meet the responsibilities willJ           be charged, at the then prevailing rate, for time and materials.  '           Courtesy Installation Serviceh  H           This software product will be installed by Digital at no addi-H           tional charge if purchased concurrently with a Startup ServiceH           Package that includes installation service. Both the operatingF           system and this product must be installed concurrently. This8           service may not be available in all countries.             HARDWARE REQUIREMENTSr  I           VAX, MicroVAX, VAXstation, or VAXserver configuration as speci-i?           fied in the System Support Addendum (SSA 27.78.02-x).P  !           SOFTWARE REQUIREMENTS *S  !              VMS Operating Systemm  :              DECnet-VAX (either end-node or full-function)  F           *  Refer to the System Support Addendum (SSA 27.78.02-x) forI              availability and required versions of prerequisite software.n             ORDERING INFORMATION  (           Software Licenses: QL-061A*-**%           Software Media: QA-061A*-**P-           Software Documentation: QA-061AA-GZ 0           Software Product Services: QT-061A*-**  I           *  Denotes variant fields. For additional information on avail- H              able licenses, services and media, refer to the appropriate              price book.  +                                           9  s  e    J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02                 SOFTWARE LICENSING  F           This software is furnished under the licensing provisions ofG           Digital's Standard Terms and Conditions. For more informationPF           about Digital's licensing terms and policies, please contact$           your local Digital office.      %           LICENSE MANAGEMENT FACILITY)  G           This layered product support the License Management Facility.oH           License units for this product are allocated on a CPU-capacity           basis.  H           For more information on the License Management Facility, referG           to the VMS Operating System Software Product Description (SPD 1           25.01.xx) or the VMS documentation set.s  H           For more information about Digital's licensing terms and poli-2           cies, contact your local Digital office.  #           SOFTWARE PRODUCT SERVICES   G           A variety of service options are available. For more informa- 9           tion, please contact your local Digital office..             SOFTWARE WARRANTYe  H           Warranty for this software product is provided by Digital withE           the purchase of a license for the product as defined in the 1           Software Warranty Addendum of this SPD.c  E           Use of the VAX P.S.I. Access software in conjunction with aeI           connector node for which Digital support has not been purchasedgE           and/or is not available invalidates any warranty or supporti           offered in this SPD.    +                                          10g ;  i    J           VAX Packetnet System Interface Access, Version 4.3  SPD 27.78.02      I           Use of the VAX P.S.I. Access software and a connector node with I           a PSDN which Digital has not tested invalidates any warranty or J           support offered in this SPD. This software warranty applies onlyJ           to those PSDN(s) which are fully supported by the connector node           software.d    D           [R]  The DIGITAL Logo is a registered trademark of Digital%                Equipment Corporation.c  J           [TM] DECnet, MicroVAX, VAX, VAXserver, and VAXstation are trade-6                marks of Digital Equipment Corporation.                                                      +                                          11t