Sub-entry point interface architecture for change management...

Details Sub-entry point interface architecture for change management... Sub-entry point interface architecture for change management...

1997-08-13

2001-11-06

Follansbee, John A. (Department: 2154)

Electrical computers and digital processing systems: multicomput

Computer network managing

Computer network monitoring

C717S152000

Reexamination Certificate

active

06314462

ABSTRACT:

This invention relates generally to communications with distributed nodes in a computer network, and more specifically with change management in a computer network.
BACKGROUND OF THE INVENTION
One of the main objectives of change management in a computer network is to control the installation and updates to microcode and software application programs at multiple nodes from a central site through telecommunications lines which interconnect them to each other. Typical change management tasks include microcode engineering change and microcode fix distribution; configuration/customization data retrieval, manipulation and distribution; microcode engineering change installation, activation and removal controls; and status reporting for each function.
The central site processor is usually larger and more powerful than the processors at the remote nodes. Skilled data processing personnel are located at the central site, while the remote nodes usually run unattended. When changes have to be made, it is more practical to have them broadcast from the central site to the various distributed sites. Thus, the remote nodes are able to work independently from the host computer at the central site, while at the same time remaining connected to the host computer for file transfer and access to other applications.
In a typical network architecture such as the system network architecture (SNA) of IBM, a remote node called an entry point sends network management data about itself and the resources it controls to a central site called a focal point. Appropriate change management commands are issued from the focal point to the remote nodes. This change management in SNA is well documented in the prior art. For example, see the following: “Managing Changes in SNA Networks”, IBM Systems Journal, Vol. 28, No. 2, pp. 260-273 (1989); “SNA Network Management Directions”, IBM Systems Journal, Vol. 27, No. 1, pp. 3-14 (1988); and “System-Independent File Management and Distribution Services”, IBM Systems Journal, Vol. 28, No. 2, pp. 241-259 (1989). However, in such prior art networks, it has not been practical to have multiple applications serviced by a single entry point. Instead, each application had its own entry point connected through at least one dedicated telecommunications line to a focal point node.
The specifications which describe the format and protocol for the GDS (general data stream) and for the related hierarchy of identifiers for SNA data objects is well known. For example, see “SNA: Format and Protocol Reference Manual: Management Services” SC30-3346; “SNA: Format and Protocol Reference Manual: File Services”, SC31-6807; “SNA: Format and Protocol Reference Manual: Distribution Services”, SC30-3098; and “SNA: Formats”, GA27-3136 (See appendix A respecting description of GDS's). The problem was to utilize these known SNA protocols and formats in connection with SNA/DS, SNA/MS and SNA/FS without having to create all the software/hardware overhead required to establish an entry point for every application in the network.
A previous conventional entry point implementation for SNA was the IBM 3174 communications controller, which implemented a complete SNA solution using SNA/DS, SNA/MA and SNA/FS at the 3174 entry point. However, this previous implementation did not include any sub-entry points.
OBJECTS AND BRIEF SUMMARY OF THE INVENTION
Accordingly, it is an object of the present invention to provide multiple sub-entry points connected to a single entry point so that for purposes of change management, each sub-entry point derives the same functional benefit as an entry point. A related object is to have such a single entry point connected to a central site focal point node with only one telephone line.
Another object of the invention is to create an interface architecture between entry points and sub-entry points which allows widespread network data distribution and processing without creating excessive numbers of entry point nodes. A related object is to minimize the resources that are normally required in an entry point by off-loading portions of the SNA entry point functions to one or more sub-entry points.
An additional object of the invention is to provide flexibility for future enhancements of the architecture. A related object is to make the identifiers passed to a sub-entry point a subset of the actual identifiers received by the entry point, and conversely make the response identifiers passed from a sub-entry point back to an entry point a subset of the actual identifier transmitted back to a focal point.
Still another object is to provide an interface with a sub-entry point which remains unchanged without regard to the type of application receiving the data objects, and without regard to the configuration of the target computer systems on the network.
More specifically, in its preferred form the invention provides a protocol that leaves the SNA/DS (distribution services) function with an entry point, but partitions the SNA/MS (management services) and the SNA/FS (file services) functions between the entry point and a sub-entry point. An application such as VM/DSNX (virtual machine/distributed systems node executive) is provided at the entry point which would handle all change management data and commands that come down over a LU 6.2 conversation from NetView DM (distribution manager). Such a conversation or session involves communications between a focal point node and one or more entry point nodes. After performing the SNA/DS functions of getting the data or command to the node, DSNX would recognize when the data or command pertained to microcode (which DSNX does not know how to handle) and would off-load it via the new interface architecture to a target system service processor or I/O device acting as the application at the sub-entry point. Such application would then perform the majority of the SNA/MS and SNA/FS functions. After the MS and FS processing is completed at the sub-entry point, a communication is sent back to DSNX over the new interface architecture and DSNX would then perform the SNA/DS function of communicating the results back to NetView DM at the focal point node.
The aforementioned objectives and advantages as well as other benefits from the invention will be understood by those skilled in the art in view of the following detailed description and accompanying drawings.


REFERENCES:
patent: 5084816 (1992-01-01), Boese et al.
patent: 5089954 (1992-02-01), Rago
patent: AO290924 (1988-11-01), None
Data and Computer Communications, by Stallings, pp. 400-403, 1985.*
IBM Systems Journal, vol. 28, No. 2, 1989, pp. 260-273, XP212406, Ballard et al., “Managing Changes in SNA Networks”, Armonk, New York.
IBM Systems Journal, vol. 27, No. 1, 1988, pp. 32-44, Ahmadi et al., “Netview/PC”, Armonk, New York.
IBM Systems Journal, vol. 28, No. 2, 1989, “Managing Changes In SNA Networks”, C. P. Ballard et al., pp 260-273.
IBM Systems Journal, vol. 28, No. 2, 1989, “System-Independent File Management and Distribution Services”, J.C. Ashfield et al., pp 241-259.
IBM Systems Journal, vol. 27, No. 1, 1988, “SNA Network Management Directions”, D.B. Rose et al., pp 13-14.

Affiliated with

Also associated with

Rating

Sub-entry point interface architecture for change management... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Sub-entry point interface architecture for change management..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Sub-entry point interface architecture for change management... will most certainly appreciate the feedback.

Rate now

Comments { 0 }

Profile ID: LFUS-PAI-O-2588442