Abstract
Systems Network Architecture (SNA) is no longer a strictly hierarchical networking environment. The introduction of advanced peer-to-peer networking (APPN) provides for more flexibility: end user systems attaching to an SNA network are no longer controlled by a mainframe host. This new flexibility creates challenges for SNA/Management Services (SNA/MS), however, since the previous hierarchical relationship provided a vehicle for network management as well as network control. The SNA/MS architecture has been extended to meet the needs of this peer-to-peer environment, providing a management infrastructure which replaces the previous SSCP to PU relationship, and at the same time provides for much greater flexibility. This new infrastructure provides a mechanism for negotiating manager and agent (referred to as focal point and entry point in SNA/MS) roles between systems, and a transport technique for management services data which exploits advanced program-to-program communication (APPC).
Access this article
Rent this article via DeepDyve
Similar content being viewed by others
References
IBM Corp.,SNA Management Services Reference, SC30-3346. Provides detailed information about SNA/MS architecture.
Michael O. Allen and Sandra L. Benedict, SNA Management Services Architecture for APPN Networks,IBM Systems Journal, Vol. 31, No. 2, pp. 336–352, 1992. Describes network management architecture for APPN.
Robert E. Moore, Utilizing the SNA Alert in the management of multivendor networks,IBM Systems Journal, Vol. 27, No. 1, pp. 15–31, 1988. Describes the SNA Alert and gives an overview of SNA/MS message structures, such as the Network Management Vector Transport (NMVT).
IBM Corp., SNA Technical Overview, GC30-3073. The capability of type 2.1 nodes to attach directly one another using peer-to-peer protocols is referred to as low-entry networking (LEN).
IBM Corp., SNA Management Services Reference, SC30-3346. The Common Operations Services function set provides for segmentation of certain major vectors across a series of NMVTs, thus bypassing the SSCP to PU session restriction on message length.
IBM Corp.,Client/Server Computing: The New Model for Business, IBM Corp., February 1992.
Steven T. Joyce and John Q. Walker II, Advanced Peer-to-Peer Networking (APPN): An Overview,ConneXions—The Interoperability Report, Vol. 6, No. 10, pp. 2–9, October 1992.
Steven T. Joyce and John Q. Walker II, Advanced Peer-to-Peer Networking (APPN): An Overview,IBM Personal Systems Technical Solutions, No. G325-5014-00, pp. 67–72, January 1992.
IBM Corp.,APPN Architecture and Product Implementations Tutorial, GG24-3669. Tutorial on APPN, with an overview of various product implementations.
IBM Corp.,APPN/Subarea Networking Design and Interconnection, GG24-3364. A guide for planning interconnection of APPN and SNA subarea networks.
System Strategies Inc.,APPN Primer: A Guide to Advanced Peer-to-Peer Networking, 0293-5M. An introduction to APPN concepts.
IBM Corp., AS/400 APPN with PS/2 APPN, 3174 APPN, 5394 and Subarea Networking, GG24-3717. Provides several scenarios of interaction of these nodes including sample definitions and traces.
Robert A. Sultan, Parviz Kermani, George A. Grover, Tsippi P. Barzilai, and Alan E. Baratz, Implementing System/36 Advanced Peer to Peer Networking,IBM Systems Journal, Vol. 26, No. 4, pp. 429–452, 1987.
P. E. Green, R. J. Chappuis, J. D. Fisher, P. S. Frosch, and C. E. Wood, P. Perspective on Advanced Peer to Peer Networking,IBM Systems Journal, Vol. 26, No. 4, pp. 414–428, 1987.
IBM Corp.,SNA LU 6.2 Reference: Peer Protocols, SC31-6808. Architecture reference for LU 6.2 protocols.
IBM Corp.,SNA LU 6.2 Reference: Peer Protocols, SC31-6808. A conversation is a logical connection between two transaction programs using an LU 6.2 session.
IBM Corp.,SNA Technical Overview, GC30-3073. Describes CP-CP sessions.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Allen, M.O., Benedict, S.L. & Peters, M.L. Meeting the challenge of a peer-to-peer network: An SNA management services infrastructure for APPN. J Netw Syst Manage 1, 189–212 (1993). https://doi.org/10.1007/BF01035887
Issue Date:
DOI: https://doi.org/10.1007/BF01035887