System and method for performing external procedure calls from a client program to a server program while both are operating in a heterogenous computer

• US 6,192,418 B1
• Filed: 06/25/1997
• Issued: 02/20/2001
• Est. Priority Date: 06/25/1997
• Status: Expired due to Term

• Current Assignee: Unisys Corporation
• Original Assignee: Unisys Corporation
• Inventors: Smith, Norman Roy, Hale, J. Calvin, Rentmeesters, Mark Joseph
• Primary Examiner(s): Oberley, Alvin E.
• Assistant Examiner(s): BULLOCK JR, LEWIS ALEXANDER
• Application Number:
  US08/882,641
• Time in Patent Office: 1,336 Days
• Field of Search: 395/684, 395/200.32, 395/200.31, 709/304, 709/300, 709/312, 709/310, 709/330, 709/213
• US Class Current: 719/312
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

There is provided a system and method in a heterogeneous multiprocessing system for performing external procedure calls from a Client Program to a Server Program, both of which are stored in a common memory. The Client Program is executed by a first CPU under control of a first operating system and the Server Program is executed by a second CPU under control of a second operating system. The first and second operating systems are also stored in the common memory. The Client Program includes a Proxy Procedure for invoking a Server program function, and a Stub Procedure for converting parameter and result data from the first to the second operating system. The Client Program further includes a Protocol Procedure for passing data between the Client and Server CPUs.

Claims

1. In a heterogeneous computer system having at least two CPUs and a common memory completely accessible by at least one of said CPUs and being disposed for storing at least two different operating systems that actively run and control resources of said heterogeneous computer system, a method for performing function calls from a Client Program stored in said common memory and being executed by a first one of said CPU'"'"'s under control of a first of said two operating systems to a Server Program operating stored in said common memory and being executed by a second one of said CPU'"'"'s under control of a second one of said two operating systems, said method comprising the steps of:

a. said Client Program initiating said Server Program by sending initialization signals to said Server Program via a CPU-to-CPU signal bus between said at least two CPS'"'"'S;

b. after successfully initiating said Server Program, said Client Program storing parameters in a Client program stack stored in said common memory;

c. said Server Program fetching said parameters directly from said Client program stack;

d. a stub procedure within said Server Program converting said parameters from a format compatible with said first operating system to a format compatible with said second operating system;

e. said Server Program processing said parameters according to said specific function;

f. said Server Program converting results of the preceding step (if any) from a format compatible with said second operating system back to a format compatible with said first operating system;

g. said Server Program storing in a Server program stack within said common memory said results converted in the previous step; and

,

h. said Client Program fetching said results from said Server program stack in said common memory.

2. The method as in claim 1 wherein said step of initiating said Server Program further includes said Client program calling a protocol procedure and passing thereto an identification of said Server Program.

3. The method as in claim 2 wherein said step of initiating further includes indicating to said Client Program if said Server program fails to respond to an attempt to initiate operation thereof.

4. The method as in claim 3 further including said Client program continuing with processing without accessing said Server Program.

5. The method as in claim 1 further including the step of said Client Program suspending operation while awaiting an indication that processing of said parameters has been completed.

6. The method as in claim 5 wherein said step of converting results further includes said protocol procedure calling a stub procedure for performing the step of converting said results.

7. The method as in claim 1 wherein step c thereof further including the step of calling a proxy procedure for the fetching of said parameters from said Client program stack.

8. The method as in claim 7 further including said proxy procedure calling a protocol procedure for invoking said Server Program to perform said specific function with said parameters.

9. A method as in claim 1 further including the step of repeating steps b through h for each occurrence that said first program makes calls to said second program to perform a specific function.

10. The method as in claim 1 and following step f thereof, further including the step of terminating operation of said Server Program if there are no more pending calls thereto.

11. In a heterogeneous computer system having at least two CPU'"'"'s and a common memory completely accessible by at least one of said CPUs and being disposed for storing at least two different operating systems that actively run and control resources of said heterogeneous computer system, a method for performing function calls from a Client Program stored in said common memory and being executed by a first one of said CPU'"'"'s under control of a first of said two operating systems to a Server Program stored in said common memory and being executed by a second one of said CPU'"'"'s under control of a second one of said two operating systems, said method comprising the steps of:

a. said Client Program calling a protocol procedure and passing thereto an identification of said Server Program;

b. said Client Program attempting to initiate said Server Program identified in the preceding step and if successful indicating the same to said Client Program;

c. said Client Program calling a proxy procedure for storing parameters in a Client program stack within said common memory;

d. said Server Program fetching said parameters from said Client program stack within said common memory;

e. said proxy procedure calling a protocol procedure for invoking said Server Program to perform a specific function with said parameters;

f. a stub procedure within said Server Program converting said parameters from a format compatible with said first operating system to a format compatible with said second operating system;

g. said Server Program performing said specific function;

h. said stub procedure converting results of the preceding step (if any) from a format compatible with said second operating system back to a format compatible with said first operating system;

i. said Server Program storing said results in a Server program stack within said common memory; and

,

j. said Client Program fetching said results from said Server program stack within said common memory.

12. A method as in claim 11 wherein said step of attempting to initiate said Server Program is unsuccessful and indicating such result to said Client Program.

13. A method as in claim 12 wherein said Client Program continuing with processing without accessing said Server Program.

14. A method as in claim 11 further including the step of said Client Program suspending operation while awaiting an indication that processing of said parameters has been completed.

15. A method as in claim 11 further including the step of repeating steps c through j for each occurrence that said Client Program makes a call to said Server Program to perform a function.

16. A method as in claim 11 and following step j thereof, further including the steps of said second operating system attempting to terminate said Server Program;

determining if the preceding step was successful; and

if so, said Server Program performing any required termination processing and returning an indication to said first operating system that termination was successful and said Server Program exiting operation.

17. A method as in claim 16 further including the said Client Program resuming normal processing.

18. A method as in claim 17 wherein said Client Program terminating function calls to said Server Program.

19. A method as in claim 18 further including the step of determining if more Server Program calls are required by said Client Program, and if so, repeating all the steps of claim 11.