DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: OpenVMS[TM] SNA, SPD 27.01.10 Version 2.3 DESCRIPTION OpenVMS[TM] SNA is a layered software product that allows suitably configured OpenVMS VAX[TM] systems to directly participate in an IBM[R] Systems Network Architecture (SNA) networking environment. After installing the OpenVMS SNA software and one or more DECnet[TM] SNA access routines, users can perform functions such as accessing IBM application programs or other system resources, act as a 3270 display station, exchange data files and documents with an IBM host, and im- plement distributed application programs that run between the OpenVMS VAX and IBM systems. Architecturally, an OpenVMS VAX system running OpenVMS SNA appears to the SNA network as a Physical Unit Type 2 node, and is attached to the SNA network through a synchronous communications device to an IBM 37xx Communications Controller. The OpenVMS SNA software supports one syn- chronous communications line at speeds of 9.6 Kbps to 64 Kbps, depend- ing on the communications device being used. The OpenVMS SNA software supports a maximum of 16 to 64 concurrent SNA logical unit sessions, depending on the VAX CPU on which it is running. Both local and re- mote connections are supported from OpenVMS SNA into the IBM SNA net- work, using switched or leased lines in point-to-point or multipoint environments. OpenVMS SNA also supports connections over X.25 switched virtual circuits using Qualified Logical Link Control (QLLC). VAX Packetnet System Interface (VAX P.S.I.) or VAX P.S.I. Access is required for SNA over X.25 connections. September 1998 AE-ET77L-TE OpenVMS SNA can send Record Formatted Maintenance Statistics (RECFMS) messages to the IBM system. These messages contain counters requested by the IBM NetView[R] Hardware Monitor using Request Maintenance Statis- tics (REQMS) messages. Not all RECFMS messages are supported by OpenVMS SNA. Refer to the OpenVMS SNA user documentation for more information. Users on one or more DIGITAL systems can simultaneously perform func- tions such as accessing IBM application programs or other system re- sources, act as a 3270 display station, perform data transfer between DIGITAL and IBM file systems, exchange electronic documents and mail messages, submit jobs to IBM batch subsystems acting as a Remote Job Entry workstation, and implement distributed, task-to-task applica- tion programs that run between DIGITAL and IBM systems. The DECnet SNA Transport product set provides a means of connecting DECnet and SNA networks that can be used by a wide variety of DIGITAL- supplied access routines running on OpenVMS Alpha and OpenVMS VAX op- erating environments. Devices supported by OpenVMS SNA include the DMB32, DSB32, DPV11, DSV11, DST32, DSH32, DSW41, DSW42, DSW21, and DSF32. All VAX P.S.I. supported devices for VAXBI[TM] and Q-bus[TM] based systems are supported when communicating with X.25 networks using QLLC circuits, except for UNIBUS[TM] devices. If you are using DECnet/OSI for OpenVMS VAX, refer to the DEC- net/OSI for OpenVMS VAX Software Product Description (SPD 25.03.xx). Each device supports different configurations. Refer to Table 1 in the Minimum Recommended Configuration section of this product's Software Product Description for information about each supported device. Circuits can be set full duplex. Data can be sent and received simul- taneously on full-duplex lines. This setting corresponds to DATMODE=FULL in the IBM ACF/NCP PU macro. Whether the connection is via X.25 or Synchronous Data Link Control (SDLC), the functions provided by the OpenVMS SNA software are com- parable to those provided by the DECnet SNA Gateway product. Systems 2 wishing access to the SNA environment must be configured with the ap- propriate DECnet SNA for OpenVMS access routines. For additional in- formation on which access routines are supported with OpenVMS SNA, see the Optional Software section of this Software Product Description. OpenVMS SNA supports connections over X.25 switched virtual circuits (QLLC) as well as SDLC circuits. The QLLC circuit can be configured to use either incoming or outgoing X.25 switched virtual circuits (SVCs). OpenVMS SNA does not support X.25 permanent virtual circuits (PVCs). OpenVMS SNA requires the IBM Network Packet Switched Interface (NPSI) in order to use QLLC circuits. The IBM NPSI software should be gen- erated to support "Boundary Network Node, Qualified Logical Link Con- trol" (BNN QLLC) type-3 switched virtual circuits. OpenVMS SNA also supports the following optional facilities for QLLC circuits: o Flow Control Negotiation o Closed User Groups o Reverse Charging OpenVMS SNA Management Utilities OpenVMS SNA provides the management utilities SNANCP and SNAEVL. SNANCP is used to manage and monitor OpenVMS SNA components such as line, cir- cuit, physical unit (PU), and logical unit (LU). SNANCP provides the human interface for the DIGITAL[TM] System Manager to monitor, con- trol, and troubleshoot OpenVMS SNA and its IBM SNA environment. All management functions pertaining to OpenVMS SNA are performed on VAX systems. The SNANCP commands allow users to display and modify infor- mation pertaining to the line, circuit, PU, LUs, and access names. On- line help is provided. SNAEVL is used to log events generated by these components. Management of the OpenVMS SNA node should be viewed as part of the DIGITAL environment; the management of the line connecting the OpenVMS VAX system to the IBM system is a joint responsibility of the IBM and DIGITAL system managers. 3 OpenVMS SNA Problem Isolation and Determination Tools The Common Trace Facility (CTF) is the problem-determination tool that provides frame-level tracing of a circuit to help in debugging appli- cation programs and identifying system problems. A privileged DECnet /OSI user can run a trace at the PU level, SDLC level, QLLC level, or session level. The trace feature is helpful for identifying an error for remedial action. The OpenVMS SNA Installation Verification Procedure (IVP), SNAVMS$IVP, is also useful for problem isolation. SNAVMS$IVP is run separately from any access routine, and can be used to verify connectivity to specific IBM applications over specific LU sessions. In failure cases, SNAVMS$IVP displays an expanded error text that attempts to diagnose the cause of the failure. INSTALLATION DIGITAL recommends purchase of the OpenVMS SNA Installation Service for the first DIGITAL node connected to each IBM host. Only experi- enced customers should attempt to install second or subsequent nodes running the OpenVMS SNA software. Customer Responsibilities Before the OpenVMS SNA Installation Service is performed, the customer must: o Previously have installed all prerequisite hardware and software, including terminals. o Obtain, install, and demonstrate as operational any modems and other equipment and facilities necessary to interface to DIGITAL's com- munications equipment. o Perform configuration and test the operational status of the syn- chronous modems for the communications line. o Have generated, to DIGITAL's satisfaction, any necessary IBM host software that will be communicating with the OpenVMS SNA software. 4 o Have installed DECnet-Plus for OpenVMS VAX (on systems running OpenVMS V7.1) or DECnet/OSI for OpenVMS VAX (on systems running OpenVMS V6.2). For installation requirements, refer to the DECnet- Plus for OpenVMS VAX Software Product Description (SPD 25.03.xx). o Have completed any additional requirements as described in the OpenVMS SNA Installation Service. o Make available for a reasonable period of time, as mutually agreed on by DIGITAL and the customer, all hardware, communications facilities, and terminals that are to be used during installation. o Be prepared to work with the DIGITAL and IBM system managers in the preinstallation activities outlined in the OpenVMS SNA Installation Service. o Be prepared to modify IBM component generation parameters to sup- port the OpenVMS SNA software. Delays caused by any failure to meet these responsibilities will be charged at the then prevailing rate for time and materials. Customer Installation Only customers experienced with IBM Interconnect products should attempt to install second or subsequent nodes running the OpenVMS SNA software. Any OpenVMS SNA software installations performed by customers are required to be validated by DIGITAL prior to customer purchase of OpenVMS SNA Service Contracts. Validation is performed by DIGITAL soft- ware specialists. HARDWARE REQUIREMENTS Processors Supported OpenVMS SNA supports the following processors and session maximums for local user connections, and an additional 128 sessions for DECnet con- nections. Restrictions are based on processor memory. For information about supported processors, refer to the OpenVMS Operating System for Alpha and VAX Software Product Description (SPD 25.01.xx). 5 ___________________________________________________________________ Processors 16 Sessions ___________________________________________________________________ MicroVAX[TM]: MicroVAX[TM] II; MicroVAX 2000; MicroVAX 3100 Models 10E, 20E, 88, and 98 VAXstation[TM]: VAXstation II; VAXstation 3200; VAXstation 3500; VAXstation 3520; VAXstation 3540 VAXserver[TM]: VAXserver 3100 Models 10E and 20E; VAXserver 3300; VAXserver 3400; VAXserver 3500; VAXserver 3600; VAXserver 3602; VAXserver 3800; VAXserver 3900; VAXserver 4000 Models 200 and 300 ___________________________________________________________________ 32 Sessions ___________________________________________________________________ VAX: VAX 4000 Models 100, 106A, 108, 200, 505, 505A, and 705A; VAX 8200[TM]; VAX 8250[TM]; VAX 8300[TM]; VAX 8350[TM]; VAXft[TM] Model 110 MicroVAX: MicroVAX 3100 Models 30, 40, 80, and 90; MicroVAX 3300; MicroVAX 3400; MicroVAX 3500; MicroVAX 3600; MicroVAX 3800; MicroVAX 3900 VAXstation: VAXstation 4000 Models 60, 90, and 96 VAXserver: VAXserver 6000 Models 210 and 310 ___________________________________________________________________ 48 Sessions ___________________________________________________________________ VAX: VAX 4000 Model 300; VAX 6000[TM] Models 210, 220, 230, 310, 320, 330, 410, and 510; VAX 8500[TM]; VAX 8530[TM]; VAX 8550[TM]; VAX 8700; VAX 8810; VAXft Models 310, 410, 610, and 612 VAXserver: VAXserver 6000 Models 220, 320, 410, 420, 510, and 520 6 ___________________________________________________________________ 64 Sessions ___________________________________________________________________ VAX: VAX 4000 Models 106A, 108, 505A, and 705A; VAX 6000 Models 240, 340, 350, 360, 400 Series (except Model 410), 500 Series (except Model 510), and 600 Series; VAX 7000 Models 810, 820, 830, 840, 850, and 860; VAX 8800; VAX 8820; VAX 8830; VAX 8840; VAX 9000[TM] Models 110, 210, 310, and 400 Series ___________________________________________________________________ Users can configure their IBM line to activate more logical units (LUs) than the maximum number of sessions allowed for the processor. The max- imum number of active LUs is twice the number of maximum sessions. For example, 64 LUs can be activated on a MicroVAX 3600. Minimum Recommended Configuration A minimum hardware system configuration includes: o One RZ[TM]-series or RA[TM]-series disk o A load device (TK50, TK70, 1600 BPI Magtape, or CD-ROM) o 6 MB memory o Modems or modem eliminators o A supported synchronous device listed in Table 1 7 Table 1: Devices Supported by OpenVMS SNA ___________________________________________________________________ EIA- Maximum 232-D Line Device VAX CPU NRZI[1] V.24 V.35 Speed ___________________________________________________________________ DMB32 BI[TM] Yes Yes Yes 38.4 Kbps DSB32 BI Yes Yes Yes 64 Kbps DPV11 Q-bus No Yes No 9.6 Kbps DSV11 Q-bus Yes Yes Yes 64 Kbps DST32 MV2000 Yes Yes No 19.2 Kbps DSH32 MV2000 Yes Yes No 19.2 Kbps DSW41 MV3100 Yes Yes No 64 Kbps DSW42 MV3100 Yes Yes No 64 Kbps DSW21 VS4000 Yes Yes Yes 64 Kbps DSF32 VAXft Yes Yes Yes 64 3000 Kbps ___________________________________________________________________ [1]NRZI support means the signaling mode for the lines from Open- VMS SNA to the IBM system can be set to NORMAL or NRZI (non- return-to-zero-inverted) so the line characteristics can match those set in the IBM ACF/NCP LINE macro. ___________________________________________________________________ 8 Disk Space Requirements (Block Cluster Size = 1) Disk space required for 8,000 blocks installation: (4 MB) Disk space required for use 6,500 blocks (permanent): (3.25 MB) These counts refer to the disk space required on the system disk. The sizes are approximate; actual sizes may vary depending on the user's system environment, configuration, and software options. OPTIONAL HARDWARE None SOFTWARE REQUIREMENTS Table 2 summarizes the software dependencies and operating system sup- port for OpenVMS SNA V2.3. Table 2: OpenVMS SNA Software Requirements ___________________________________________________________________ DECnet OpenVMS DECnet Data Additional Soft- Phase Version Software Link ware Required ___________________________________________________________________ V V7.1 DECnet- SDLC None Plus V7.1 V6.2 DECnet/OSI SDLC None V6.3 QLLC PSI V5.0[1] ___________________________________________________________________ [1]Packaged with DECnet/OSI, but a separate PSI license is re- quired. ___________________________________________________________________ 9 SOFTWARE LICENSING This software is furnished only under a license. For more information about DIGITAL's licensing terms and policies, contact your local DIGITAL office. Restrictions/Comments Cluster licenses are not available for this product; a Single-Use License is necessary for each CPU on which this product will be used. License Management Facility Support This layered product supports the OpenVMS License Management Facility. License units for this product are allocated on a CPU-capacity basis. For more information on the License Management Facility, refer to the OpenVMS Operating System for Alpha and VAX Software Product Descrip- tion (SPD 25.01.xx) or the License Management Facility manual of the OpenVMS Operating System documentation set. CLUSTER ENVIRONMENT This layered product is fully supported when installed on any valid and licensed VAXcluster[TM]* configuration with the following restric- tions: o OpenVMS SNA must be configured and run on each node containing a synchronous device connected to the SNA network for SDLC circuits. o The access routine software must run on the node configured with OpenVMS SNA. The Hardware Requirements section of this Software Product Descrip- tion details any special hardware required by OpenVMS SNA. 10 * VAXcluster configurations, including CI[TM], Ethernet, and Mixed In- terconnect configurations, are fully described in the VAXcluster Soft- ware Product Description (SPD 29.78.xx). OpenVMS TAILORING CLASSES The following OpenVMS classes are required for full functionality of this layered product: o OpenVMS Required Saveset o Network Support o Utilities IBM SUPPORTED CONFIGURATIONS OpenVMS SNA is warranted with the IBM software configurations listed in Table 3. Table 3: IBM Software Configurations ___________________________________________________________________ Software Product Version Release ___________________________________________________________________ MVS/SP[TM] (MVS 2 2.3 /XA[TM]) MVS/ESA[TM] SP 4 2.0, 3.0 VM/XA SP 1 2.1 VM/ESA[R] 2 2.0 VSE/SP 3 2.0 ACF/VTAM[TM] 4 2.0, 3.0, 4.0 ACF/NCP/VS (for the 6 3.0 3745) 7 3.0, 4.0, 5.0, 6.0 NetView[R] 2 3.0, 3.1 OS/390[R] 1 2.0, 3.0 ________________________2___________4.0____________________________ 11 For X.25 support (P.S.I.), OpenVMS SNA requires the IBM NPSI and NCP software configurations listed in Table 4. Table 4: IBM Software Required for X.25 Support ___________________________________________________________________ NPSI NCP Version Release Version Release ___________________________________________________________________ 3 4.0 5 4.0 3 6.0 6 3.0 3 8.0 7 3.0, 4.0, 5.0, 6.0 ___________________________________________________________________ FUJITSU SUPPORT The Fujitsu hardware and software environments listed below are sup- ported with the following restrictions: These configurations are supported by DIGITAL Japan for installations in the Country of Japan ONLY and ONLY with the "F" version access rou- tines listed below, which are available from and supported by DIGITAL Japan. Only SDLC circuits are supported with Fujitsu configurations. Please contact DIGITAL Japan for additional information. Hardware o FUJITSU FACOM M-series Mainframe o FUJITSU F2806G front end 12 Software o FUJITSU NCP-G V10L20 (similar to IBM's ACF/NCP) o FUJITSU OS IV/F4 MSP E20 (similar to IBM's MVS/XA) o FUJITSU VTAM-G V10L20 (similar to IBM's VTAM) "F" Access Routines The following products provide local language support and are supported by DIGITAL Japan for use with Fujitsu environments in Japan. ___________________________________________________________________ F Access Routines Version SPD (Japan) ___________________________________________________________________ F6650 Terminal Emulator 1.0 27.J3.xx F6650 Data Stream 1.0 27.J4.xx Programming Interface DECwindows[TM] F6650 1.0 27.T7.xx Terminal Emulator for VMS F-RJE 1.0 27.J5.xx F-PRE 1.0 26.T8.xx ___________________________________________________________________ OPTIONAL SOFTWARE The following list indicates a few access routines that are available for use with OpenVMS SNA. For information on these products, consult the respective Software Product Descriptions. o Digital SNA APPC/LU6.2 Programming Interface for OpenVMS (SPD 26.88.xx) o DECnet SNA Application Programming Interface for OpenVMS (SPD 26.86.xx) o Digital SNA Data Transfer Facility for OpenVMS (SPD 27.85.xx) o Digital SNA Printer Emulator for OpenVMS (SPD 26.70.xx) o Digital SNA Remote Job Entry for OpenVMS (SPD 26.85.xx) 13 o Digital SNA 3270 Data Stream Programming Interface for OpenVMS (SPD 26.87.xx) o Digital SNA 3270 Terminal Emulator for OpenVMS (SPD 26.84.xx) o DECwindows DECnet SNA 3270 Terminal Emulator (SPD 31.58.xx and SPD 62.63.xx) o DIGITAL SNA APPC/LU6.2 Programming Interface for DIGITAL UNIX (SPD 56.11.xx) o RUMBA[R] products 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. DISTRIBUTION MEDIA 9-track 1600 BPI Magtape This product is also available as part of the OpenVMS VAX Software Product Library on CD-ROM. The software documentation for this product is also available as part of the OpenVMS VAX Online Documentation Library on CD-ROM. YEAR 2000 READY The product was installed on a test machine and the system date was set so that the rollover to 1-JAN-2000 and date handling in the twenty- first century were observed to work correctly. 14 SOFTWARE WARRANTY This software is provided by DIGITAL with a 90-day conformance war- ranty in accordance with the DIGITAL warranty terms applicable to the license purchase. Warranty Limitations IBM Supported Configurations This product has been designed to operate with the IBM software subsystems as specified in the IBM Supported Configurations section earlier in this product's Software Product Description. While this soft- ware may function correctly with other IBM software and equipment, and with software other than that supported by IBM, DIGITAL cannot offer its standard warranty for this software unless it has been tested with such equipment and software configurations and found acceptable to DIGITAL. For a complete list of IBM application subsystems that the various ac- cess routines have been certified against and that are supported con- figurations by DIGITAL, please consult the respective access routine Software Product Descriptions. (See the Optional Software section of this product's Software Product Description.) ORDERING INFORMATION Software Licenses: QL-362A*-** Software Media: QA-362A*-** Software Documentation: QA-362A*-GZ Software Product Services: QT-362A9-I9 (On-Site Initial Installation) QR-SM362-BA (On-Site Additional Node Installation) QR-SM362-BN (Remote New Installation) QT-362A*-L* (Layered Product Service) * Denotes variant fields. For additional information on available licenses, services, and media, refer to the appropriate price book. 15 The above information is valid at time of release. Please contact your local DIGITAL office for the most up-to-date information. SOFTWARE PRODUCT SERVICES A variety of service options are available from DIGITAL. For more information, contact your local DIGITAL office. [R] IBM, NetView, OS/390, and VM/ESA are registered trademarks of International Business Machines Corporation. [R] RUMBA is a registered trademark of Wall Data, Incorporated. [R] UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. [TM] MVS/ESA, MVS/SP, MVS/XA, and VTAM are trademarks of International Business Machines Corporation. [TM] BI, CI, DEC, DECnet, DECwindows, DIGITAL, MicroVAX, MicroVAX II, OpenVMS, Q-bus, RA, RZ, TK, UNIBUS, VAX, VAX 6000, VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550, VAX 9000, VAXBI, VAXcluster, VAXft, VAXserver, VAXstation, VMS, and the DIGITAL logo are trademarks of Digital Equipment Corporation. All other trademarks and registered trademarks are the property of their respective holders. © Digital Equipment Corporation 1998. All rights reserved. 16