1. In a chafing dish including a supporting frame and a cover element mounted for rotation about an axis passing through the body of said cover, improved means for progressively counter-balancing said cover comprising: a pair of pintles supporting said cover for movement about said axis, a lever extending laterally from at least one of said pintles, and fixed thereto at a first end thereof, a link having first and second ends, a first end being pivotally connected to said lever at a second end of said lever, a spring having first and second ends, said first end being connected to said second end of said link, said second end of said spring being connected to a peripheral location on said frame; whereby movement of said cover element from closed to open position results in progressive tensioning of said spring to provide a variable counter-balancing force to said lever as said link progressively approaches said pintle; said link surrounding said pintle after 180 degree rotation to cancel the counter balancing force of said spring.
2. Improved means in accordance with claim 1, said spring being of a longitudinally tensioning type.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1 A method for monitoring messages in a distributed data processing system, the method comprising:
putting a message containing a monitoring token on a queue on a server;
receiving a call to get the message from the queue on the server;
determining, with an API exit running on the server, whether the call to get the message is made by a process running on a remote client or by a process running on the server; and
if the call to get the message is made by a process running on the server, removing the monitoring token from the message with the API exit.
2. The method of claim 1 further comprising removing the monitoring token from the message with a channel exit running on the remote client, if the call to get the message is made by a process on the remote client.
3. The method of claim 1 further comprising inserting, with a channel exit running on a remote client, the monitoring token in the message.
4. The method of claim 3 wherein inserting, with a channel exit running on a remote client, the monitoring token in the message further comprises calling an ARM API.
5. The method of claim 1 further comprising inserting, with an API exit running on the server, the monitoring token in the message.
6. The method of claim 5 wherein inserting, with an API exit running on the server, the monitoring token in the message further comprises calling an ARM API.
7. A system for monitoring messages in a distributed data processing system, the system comprising:
means for putting a message containing a monitoring token on a queue on a server;
means for receiving a call to get the message from the queue on the server;
means for determining, with an API exit running on the server, whether the call to get the message is made by a process running on a remote client or by a process running on the server; and
means for removing the monitoring token from the message with the API exit.
8. The system of claim 7 further comprising means for removing the monitoring token from the message with a channel exit running on the remote client.
9. The system of claim 7 further comprising means for inserting, with a channel exit running on a remote client, the monitoring token in the message.
10. The system of claim 9 wherein means for inserting, with a channel exit running on a remote client, the monitoring token in the message further comprises means for calling an ARM API.
11. The system of claim 7 further comprising means for inserting, with an API exit running on the server, the monitoring token in the message.
12. The system of claim 11 wherein means for inserting, with an API exit running on the server, the monitoring token in the message further comprises means for calling an ARM API.
13. A computer program product for monitoring messages in a distributed data processing computer program product, the computer program product comprising:
a recording medium;
means, recorded on the recording medium, for putting a message containing a monitoring token on a queue on a server;
means, recorded on the recording medium, for receiving a call to get the message from the queue on the server;
means, recorded on the recording medium, for determining, with an API exit running on the server, whether the call to get the message is made by a process running on a remote client or by a process running on the server; and
means, recorded on the recording medium, for removing the monitoring token from the message with the API exit.
14. The computer program product of claim 13 further comprising means, recorded on the recording medium, for removing the monitoring token from the message with a channel exit running on the remote client.
15. The computer program product of claim 13 further comprising means, recorded on the recording medium, for inserting, with a channel exit running on a remote client, the monitoring token in the message.
16. The computer program product of claim 15 wherein means, recorded on the recording medium, for inserting, with a channel exit running on a remote client, the monitoring token in the message further comprises means, recorded on the recording medium, for calling an ARM API.
17. The computer program product of claim 13 further comprising means, recorded on the recording medium, for inserting, with an API exit running on the server, the monitoring token in the message.
18. The computer program product of claim 17 wherein means, recorded on the recording medium, for inserting, with an API exit running on the server, the monitoring token in the message further comprises means, recorded on the recording medium, for calling an ARM API.