Browse Prior Art Database

Message-Handling Program

IP.com Disclosure Number: IPCOM000047783D
Original Publication Date: 1983-Dec-01
Included in the Prior Art Database: 2005-Feb-08
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Hoflich, MA: AUTHOR [+2]

Abstract

A message-handling program allows a clustered data processing system user to specify the routing of messages relating to the operation of the system, rather than requiring the designation of a device service operator to route or reassign messages. In this clustered data processing system, three types of queued messages are contemplated: (a) information messages, (b) non-priority action messages, and (c) priority action messages. A message queue is maintained for each operator and each workstation. Each of the message queues can hold an indefinite number of messages. The messages are not destroyed at log-off or log-on. Messages may be queued for an operator even when the operator is not logged-on or for a workstation when the workstation is not powered on.

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

Page 1 of 2

Message-Handling Program

A message-handling program allows a clustered data processing system user to specify the routing of messages relating to the operation of the system, rather than requiring the designation of a device service operator to route or reassign messages. In this clustered data processing system, three types of queued messages are contemplated: (a) information messages, (b) non-priority action messages, and (c) priority action messages. A message queue is maintained for each operator and each workstation. Each of the message queues can hold an indefinite number of messages. The messages are not destroyed at log-off or log-on. Messages may be queued for an operator even when the operator is not logged-on or for a workstation when the workstation is not powered on. Messages queued for a workstation can be displayed even if no operator is logged-on at the workstation. When an operator is logged-on at a workstation, all queued messages from the operator's message queue and the workstation's message queue are merged. Action messages generated by queued jobs are added to the message queue for the appropriate operator or workstation, as defined during the configuration of the system in the device profile for the device being used. Since there may be situations in which a particular operator or workstation is not currently available (operator not logged-on or workstation not powered on) the device profile specifies a message destination succession list for action messages generated by the queued job using the device. When an action message is generated by a queued job, the message destination succession list in the device profile is searched until an available destination for the action message is found. The action message is then added t...