Method for handling multiple program exceptions across heterogeneous systems

1. In a computer system including at least one mainframe server and one client, a method for handling a suspended task, said method comprising the steps of:

(a) performing a security check on said mainframe server, wherein said step of performing a security check on said mainframe server includes the steps of:

(a1) determining if a database control file exists on said mainframe server, and if not, returning an error;

(a2) determining if said client has a privilege to access said mainframe server, and if not, returning an error;

(a3) determining if said client has a permission to access said database, and if not, returning an error;

(b) detecting a response from said suspended task;

(c) monitoring said response wherein said step of monitoring said response includes the steps of:

(c1) determining if said response is from said mainframe server, and if so, notifying said client of said response;

(c2) determining if said response is from said client, and if so;

(c3) determining if a server response has been issued, and if so, canceling said response from said client;

(d) handling said response wherein said step of handling said response includes the steps of:

(d1) sending said response from said client to a service program on said mainframe server;

(d2) sending said response from said service program to a server program on said mainframe server;

(d3) making an operating system call on said mainframe server to submit said response for said suspended task to said client;

(e) activating said suspended task with said response.

2. The method as in claim 1 wherein said suspended task may have resulted from a program exception.

3. A storage medium encoded with machine-readable computer program code enabling a method for handling a suspended task and notifying a client, said method comprising the steps of:

(a) performing a security check on said mainframe server

(a1) determining if a database control file exists on said mainframe server, and if not, returning an error;

(a2) determining if said client has a privilege to access said mainframe server, and if not, returning an error;

(a3) determining if said client has permission to access said database, and if not, returning an error;

(b) detecting a response from said suspended task;

(c) monitoring said response wherein said step of monitoring said response includes the steps of:

(c1) determining if said response is from said mainframe server, and if so, notifying said client of said response;

(c2) determining if said response is from said client, and if so, notifying said client;

(c3) determining if a server response has been issued, and if so, canceling said response from said client;

(d) handling said response wherein said step of handling said response includes the steps of:

(d1) sending said response from said client to a service program on said mainframe server;

(d2) sending said response from said service program to a server program on said mainframe server;

(d3) making an operating system call on said mainframe server to submit said response for re-activating said suspended task;

(e) activating said suspended task with said responses.

4. In a network where multiple client PC's can initiate program tasks and operate in communication with a mainframe server and database storage means, wherein said server includes a service program which connects said client PC and said server, a system for handling a suspended task comprising:

(a) means to connect to said server;

(b) means to execute a security check on said server;

(c) means for detecting a response from said server;

(d) means to send a suspension message to said service program to indicate a suspended task (exception);

(e) means to monitor any response from said client-PC or said server;

(f) means to handle said response that was monitored;

(g) means to activate said suspended task;

wherein each I/O Read/Write operation or each interlock between participating programs using a shared resource is designated as an event and wherein said means (a) to connect includes:

(a1) means for setting a lock for single threading;

(a2) means to initiate a child event which involves a task initiated by a parent event;

(a3) means to initiate a parent event which sets up a separate stack for a process.

5. The system of claim 4 wherein said means (b) to execute a security check includes:

(b1) means to check if a database control file is in existence, and, if so;

(b2) means to check if said client-PC has privilege to access said database storage means and if so;

(b3) means to check if said client-PC has permission to access said database storage means, and if so;

(b4) means to enable said means for detecting a response.

6. The system of claim 4 wherein said means (e) to monitor any response includes:

(e1) means to determine if there is a response to a suspended task (exception), and if so;

(e2) means to check if said response is from a client-PC, and if so;

(e3) means to check if there was also a server response, and if so;

(e4) means to cancel said client-PC response;

(e5) means to handle said server response;

(e6) means to inform said client-PC of said server response.

7. The system of claim 6 wherein said means (e3) to check for a server response shows that no server response was indicated, then said means (e3) includes:

(e31) means to handle said client response.

8. The system of claim 4 wherein said means (f) to handle said response that was monitored includes:

(f1) means to send said response from said client-PC to said service program;

(f2) means to send said response from said service program to said server;

(f3) means to call the operating system in said server to submit a response, for the suspended task, to said client-PC.