Cisco Technology, Inc.

Michael Boe

Derek W Bolton

Barry K Chan

Prasannakumar Murugesan

Gary Gitelson

Aniruddha Khare

Karunakar Reddy Parne

Techniques for selectively restarting processes based on API changes are provided. Information is stored that can be accessed to identify processes that are affected by an API change. The stored information can be modified to reflect the API change and the processes that are affected can be restarted. Thus, processes that are not affected by the API change need not be restarted.

Selective process restart based on API changes

A method for dynamic linking of software modules includes detecting an event during the execution of a computer program that resides in a first memory, ascertaining whether there is at least one required property associated with the event if the event is detected, determining a property identifier for the at least one required property and loading at least one code module from a second memory into the first memory based upon a property identifier configured with the executable code module. According to one aspect, the loading includes loading the at least one executable code module into the first memory if it is not in the first memory. According to another aspect, the at least one executable code module includes at least one dynamic link library (DLL). According to another aspect, the event includes the addition of a hardware device and the required property includes a hardware device PROM identifier.

Run-time property-based linking of software modules

A TN3270 server (,) that forwards a,data stream from a Systems Network Architecture (&ldquo;SNA&rdquo;) connection (,) to a Transmission Control Protocol (&ldquo;TCP&rdquo;) connection (,) monitors the TCP connection for segments that acknowledge thereby-transmitted bytes. It also keeps track of the unacknowledged-byte window sizes specified by received TCP-connection -segments. It responds with a pacing response to a pacing-request-containing SNA message only when forwarding of previously received information from the SNA can be completed without resulting in a number of unacknowledged bytes that exceeds the specified window size.

Mapping SNA session flow control to TCP flow control

To determine the name that specifies the Systems Network Architecture logical-unit-characteristics set that a host (12) systems services control point is to associate with a TN3270 server (18) logical-unit process that is to represent a client terminal (14), the server (18) generates the name from the client's device type algorithmically, i.e., without looking the name up in a server-maintained table entered by using the device type as the key. This eliminates the need for server updates when new device types are introduced. Additionally, the algorithm used to generate the name depends on whether the client has negotiated to receive a copy of the data transmitted in the BIND message by which another logical unit initiates a session with the logical unit that will represent the client. In that way, the host's systems services control point can send the client data streams in the form that it expects, and the server is relieved of the need to perform any translation.

Display-model mapping for TN3270 client

When a TN3270 client (14) uses the Transmission Control Protocol/Internet Protocol ('TCP/IP')to initiate contact with a TN3270 server (18) to obtain access to an applications program running on a host (12) with which the server (18) employs the Systems Network Architecture ('SNA')protocol to communicate, the server's SNA physical-unit process sends the host's systems service control point an SNA NMVT message that includes a physical-location subfield in a product-set-attributes subvector of a product-set-ID vector. The physical-location subfield includes the client's IP address and TCP port number so that host management applications can determine individual clients' usages without interrupting communications with the server.

Communications gateway mapping internet address to logical-unit name

A TN3270 server (26) that forwards a 3270 data stream from a Systems Network Architecture ('SNA') connection (28) to a Transmission Control Protocol ('TCP') connection (24) monitors the TCP connection for segments that acknowledge thereby-transmitted bytes. It also keeps track of the unacknowledged-byte window sizes specified by received TCP-connection segments. It responds with a pacing response to a pacing-request-containing SNA message only when forwarding of previously received information from the SNA can be completed without resulting in a number of unacknowledged bytes that exceeds the specified window size.

Growing community of inventors

San Francisco, CA, United States of America

Michael Boe