---------------------------------------------------------------------------- The Florida SunFlash SunLink SNA Peer-to-Peer 7.0 SunFLASH Vol 36 #15 December 1991 ---------------------------------------------------------------------------- For End Users: - SNA Peer-to-Peer provides a platform for popular 3rd-party applications to communicate with IBM systems (Sybase OpenServer, Spectrum Concepts XCOM 6.2, SNA Solutions Connect400, Oracle SQL NET, and more). For System Administrators: - Protocol Conversion Application (PCA) between SunNet Manager and IBM's Network Management Platform: NetView - A SunNet Manager Agent for the SNA Peer-to-Peer Gateway For Developers: - IBM Node Type 2.0 or 2.1 emulation on any Sun workstation using SDLC or Token Ring connections to IBM systems - APPC basic, mapped, and control operator verbs - Gateway/Client architecture - Support of Parallel Sessions - Conversation-Level Security - 250 Transaction Programs per Gateway - Document Interchange Architecture API (DIA) - Compatibility with AS/400's - Link speeds up to 250Kbps using HSI/S - API for communication with NetView Introduction SunLink(R) SNA Peer-to-Peer allows Sun systems to communicate with IBM and IBM-compatible mainframes. SNA Peer-to-Peer complements SunLink SNA 3270 by providing a comprehensive set of SNA(R) services (LU6.2, DIA, and NetView support) between Sun workstations and IBM environments. SNA Peer-to-Peer and SNA 3270 are part of a family of connectivity solutions from SunConnect, a Sun Microsystems Incorporated Business, and available through SMCC. The gateways are designed to integrate Sun systems into existing computer networks to create heterogeneous computing environments. ---------------------------------------------------------------------- Features Benefits ----------------------------------------------------------------------- Integration of SunNet Manager and Customers can manage large enterprise IBM's NetView networks that are SNA and TCP/IP-based SunNet Manager Agent for SNA Sun administrator can conveniently Peer-to-Peer Gateway manage the IBM/Sun gateway link Node Type 2.0 or 2.1 emulation Connectivity to host-based LU6.2 applications, as well as AS/400 and PC LU6.2 applications. Gateway/Client Architecture Optimized performance over enterprise networks; ease of configuration Document Interchange Architecture API Integration with IBM's DISOSS (now called OfficeVision/MVS) NetView API Platform for 3rd Party network integrators to communicate with NetView Support of Serial or Token Ring links Ability to distribute applications across LANs or WANs supporting large numbers of users; ease of connectivity over commonly-used building wiring AS/400 Connectivity Connectivity to the industry's most popular midrange platform 250Kbps Serial Link Support Convenient, cost-effective way to provide 3270 access to large numbers of users in remote locations 250 sessions/gateway Cost effective configurations; ease of administration SNA PEER-TO-PEER 7.0 FEATURE DETAIL ----------------------------------- Node Type 2.0/2.1 over Token Ring or SDLC: The SNA Peer-to-Peer gateway can emulate both a node type 2.0 physical unit, or a 2.1 physical unit. The 2.1 emulation is optimal for communication between peer devices such as AS/400's or PC's running APPC/PC. It is also valuable for Sun-to-Sun LU6.2 communication over an SNA backbone via independent LU's. Gateway/Client Architecture: The SNA Peer-to-Peer gateway is a process that maintains a connection to an SNA host. It is responsible for the node type (PU) 2.0 or 2.1 emulation and communicates over a Token Ring connection or SDLC connection. The client is called a "Transaction Program" and communicates to the gateway over a TCP/IP connection. This connection can be over Ethernet, Token Ring, FDDI, SunLink X.25, or any IP routing technology. This client Transaction Program is built using the API supplied with SNA Peer-to-Peer. Parallel Sessions: Support of parallel sessions requires node type 2.1 emulation and permits a single Transaction Program to "multiplex" more than one communication path over a single logical unit. Conversations are differentiated from one another by a unique conversation ID. Conversation Level Security: Conversation Level Security allows the developer of a Transaction Program to specify a user profile, user name, and user password upon allocation of a given session. Various levels can be applied to the above parameters to suit the security requirements of the corresponding application and environment. 250 Transaction Programs per Gateway: Each gateway process can support up to 250 client Transaction Programs. And each gateway system can run multiple gateway processes. However, the system adminstrator should configure only the number of gateways and clients that will meet their performance requirements. For example, while 250 client Transaction Programs can be supported by a single gateway, it would be inappropriate to attempt to run 250 Transaction Programs over a 9600bps serial link. Multiple SNA Peer-to-Peer gateway processes are supported per machine. This might be used to support multiple SDLC connections or connections to multiple hosts over a single Token Ring interface. Document Interchage Architecture: SNA Peer-to-Peer also provides an API that supports the Document Library Services and Document Distribution Services function sets of DIA. Specifically, functions sets 2, 5, 8 and 10 are supported with this API. AS/400 Connectivity: An SNA Peer-to-Peer Transaction program has the ability to communicate not only to a mainframe system and PC, but also to IBM's midrange AS/400. This represents an ideal platform for distributed applications between an AS/400 and a Sun workstation. Network Management Features --------------------------- NetView (PUMS) API: SNA Peer-to-Peer comes with an API that uses Physical Unit Management Services (PUMS) to establish a link to NetView. PUMS is part of SNA Management Services (SNA/MS), and part of SAA. This API is ideal for Network Integrators who wish to customize Sun-based applications and communicate to NetView. Support for NetView ``runcmd'' is also provided. This allows the NetView operator to issue a SunOS command on a Sun node, perhaps as a result of a forwarded event. Protocol Conversion Application: The Protocol Conversion Application (PCA) is responsible for forwarding alerts and events defined in SunNet Manager to NetView. PCA allows the system administrator to describe what subset of SNM events are to be forwarded. Also, the administrator has the ability to specify what NetView code point should be used (for each event), what the probable cause is, and what the recommended action is (among other things). SunNet Manager Agent: The SNA Peer-to-Peer product is well-integrated with SunNet Manager. Both the gateway and an individual Transaction Program can be managed by SunNet Manager. Manageable parameters include: Gateway, Physical Unit, Data Link, Local LU, Partner LU, Session Mode, Session, Transaction Program, and Conversation. HARDWARE CONSIDERATIONS ---------------------------------- - SPARCsystem or Sun4 (for the gateway) - CPU serial ports can be used for the gateway's SDLC links on all systems except SPARCstation IPC or IPX. HSI/S must be used on IPC or IPX systems requiring SDLC links (via telephone lines) to the host. - SunLink MCP can be used for the gateway's SDLC links in systems with an aviailable VME slot. Maximum speed supported is 56Kbps. - SunLink HSI/S can be used for the gateway's SDLC links in systems with an available SBus slot. Maximum speed supported is 256Kbps (single link only). - SunLink TRI/S can be used for the gateway's Token Ring connections in systems with an available SBus slot. SOFTWARE CONSIDERATIONS ---------------------------------- - SunOS 4.1 - 2.5 Mbytes of disk space U.S. PRICING AND ORDERING INSTRUCTIONS -------------------------------------- The End-User and Reseller price lists will contain the following entries (please see the actual price list for specific product notes): Discount Description Order Numbers List Price Category Service Price ========================================================================== SunLink SNA P2P 7.0 PTP-7.0-4.1-4-21 $6,600 A $100 on CD. Supports Token Ring (TRI/S), HSI/S, CPU Serial Ports, and MCP board. SNA P2P 7.0 Doc PTP-7.0-X-X-9 $150 A N/A NOTE 1: SNA Peer-to-Peer is a platform for many 3rd-party applications. The most notable is Sybase OpenServer which provides access to IBM host databases (DB2, CICS/VSAM/IMS). Other popular applications include SNA Solutions Connect400 (an AS/400 connectivity product with 5250 emulation, file transfer, and printer emulation), and Spectrum Concepts XCOM 6.2 (file transfer using the SNA LU6.2 protocol), and Oracle's SQL*NET. NOTE 2: Per-incident software upgrade price for P2P 7.0 will be announced separately prior to FCS. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For information send mail to info-sunflash@sunvice.East.Sun.COM. Subscription requests should be sent to sunflash-request@sunvice.East.Sun.COM. Archives are on solar.nova.edu and paris.cs.miami.edu. All prices, availability, and other statements relating to Sun or third party products are valid in the U.S. only. Please contact your local Sales Representative for details of pricing and product availability in your region. Descriptions of, or references to products or publications within SunFlash does not imply an endorsement of that product or publication by Sun Microsystems. John McLaughlin, SunFlash editor, flash@sunvice.East.Sun.COM. (305) 776-7770.