Browse Prior Art Database

DISPLAY/LIST MESSAGES

IP.com Disclosure Number: IPCOM000059876D
Original Publication Date: 1986-Feb-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 2 page(s) / 14K

Publishing Venue

IBM

Related People

Koch, LM: AUTHOR

Abstract

A method is described which changes the way queued messages are handled in the IBM 5520 administrative system. The old message key function appears unchanged to the operator, but in fact a specified number of message are saved for possible re-display.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 2

DISPLAY/LIST MESSAGES

A method is described which changes the way queued messages are handled in the IBM 5520 administrative system. The old message key function appears unchanged to the operator, but in fact a specified number of message are saved for possible re-display.

The Display/List Messages function performs the message key function in a more useful and more efficient manner. Instead of presenting each message one at a time on the message line, all messages are formatted into a document that may be viewed, stored, and/or printed. This function also provides the ability to review those messages which have already been viewed, but which are saved. Currently, an operator of the 5520 system may receive messages from the system at the bottom of the display. The system sends messages of two types; immediate and queued (delayed). Immediate messages generally appear on the message line of a display station when the system has detected a situation which precludes proceeding, for example, when a parameter on a menu is missing or invalid. Queued (or delayed) messages are generally status information. For example, job completion messages inform operators when their asynchronous tasks have completed. Queued messages are always queued to a profile. This may be an operator profile, display station profile, or the SYSTEM profile. Messages queued to a specific operator profile cause the Operator Message indicator to turn on when that operator signs on. If that operator is the 'System Operator,' messages queued to the SYSTEM profile can also cause the operator message indicator to turn on. Since queued Communications messages do not turn anyone's message light on, a System message is generated when the Communication Message Queue goes from empty to non-empty, and whenever the queue passes a depth divisible by 16. There are two areas where messages are stored: an area for those which are 'New,' that is, they have been sent, but no action to view them has been performed, and an area for those which are 'Old,' that is, some action to view them has already been performed. The area for 'New' messages can grow to the limit of disk space. However, the area for 'Old' messages is fixed to a predefined number of messages and contains those most recently viewed. For device messages the limit is 10, for operator messages the limit is 20, and for SYSTEM and Communications messages the limit is 100. 'New' Device Messages are purged...