DECmessageQ for UNIX[R], Version 3.0 SPD 39.25.03

DESCRIPTION

DECmessageQ for UNIX is the UNIX Operating System implementation of a generic software message queuing bus that provides easy-to-use, ef- ficient task-to-task communications among processes using DECmessageQ on OpenVMS, DEC OSF/1[R] AXP, ULTRIX, HP-UX[TM], 88open[R], AIX[R], MS[R]-Windows[TM], Windows NT[R], Macintosh[R], Solaris[R] and SunOS.

A common call interface allows messages to be delivered via local in- terprocess communications for intra-CPU applications, or via Trans- mission Control Protocol/Internet Protocol (TCP/IP) and DECnet (Open- VMS, DEC OSF/1, ULTRIX, Windows NT and MS-Windows) for inter-CPU ap- plications. Applications can be designed so client applications can be redeployed easily anywhere within the DECmessageQ network config- uration, whether in a standalone node, a local area network (LAN), or a wide area network (WAN).

• High speed local message delivery using local interprocess commu- nications
• Remote message delivery via TCP/IP or DECnet for OpenVMS, DEC OSF /1, ULTRIX, Windows NT, and MS-Windows.
• Remote message delivery via TCP/IP for HP-UX, SunOS, Solaris, AIX, 88open, and Macintosh.
• Fully asynchronous and synchronous receipt of messages
• Message sizes up to 32,000 bytes
• Priority queuing of messages
AE-PNACD-TK
• Selective reception of messages by queue number or priority
• Shared input queues using Multi-Reader Queues (MRQ)
• Use of intra-CPU naming through a local naming service
• Set of message delivery options
• A maximum of 999 queues per DECmessageQ Group
• A maximum of 32,000 DECmessageQ Groups
• User-settable timers with timer expiration delivered via messages placed in the user's primary queue
• Utilities for monitoring the network configuration and flow of mes- sages
• Dynamic addition of CPUs to the communications network
• Message interface for retrieving DECmessageQ configuration infor- mation on line
• Portable call interface
• Connectivity to DECmessageQ implementations on OpenVMS, DEC OSF/1, ULTRIX, HP-UX, 88open, AIX, Windows NT, MS-Windows, Macintosh, So- laris and SunOS.

DECmessageQ for UNIX can also be used as an integration tool to merge many external events with the message queuing bus. In addition to in- tegrating messages from local processes and remote processes, DECmes- sageQ also provides facilities for the integration of other events such as:

• Timer settings
• Simulated messages
• Other external events such as special hardware I/O

DECmessageQ Queues

• Primary Queue (PQ) - Each process that attaches to the message queu- ing bus is assigned a Primary Queue. This queue is used to receive messages from processes using DECmessageQ.
• Secondary Queue (SQ) - Any process may attach to one or more sec- ondary queues. These queues can also be used to receive messages. The order in which queues are scanned for messages is defined by the DECmessageQ selection rules.
• Multi-Reader Queue (MRQ) - A Multi-Reader Queue is a single shared queue that can be shared by any number of simultaneous readers.

Message Recovery Services (MRS)

Message Recovery Services increase the robustness of DECmessageQ by providing applications with the ability to recover from message de- livery failures due to:

• Application program abort
• Communication line failure
• System crash

Some of the application requirements addressed by MRS are:

• Sender wishes to insure delivery of messages when the receiving pro- cess is available but does not wish to monitor the delivery.
• Sender wishes to know that a message is recoverable to avoid the cost of reconstructing it but does not care when it is finally de- livered.
• Receiver wishes to maintain a journal of all messages received by it for audit trail or reprocessing.

Message Recovery Services are primarily implemented by an MRS server, a non-privileged program attached to the DECmessageQ Message Bus. MRS actions are invoked by standard DECmessageQ send and receive message calls.

MRS is oriented toward messages, not processes; not all messages sent from or directed to a particular process need to be processed by MRS. This allows applications to selectively incur the additional process- ing imposed by MRS for just those messages that are not easily recov- ered. Message recovery characteristics are set by the sending pro- cess.

Delivery Options

• Datagram - A non-recoverable attempt is made to deliver a message. If the message cannot be delivered to a target, then an error is logged.
• Blocking and non-blocking enqueue - The sending process will be no- tified when the message is written to the target queue. A return status will indicate if the message successfully enqueued to the queue.
• Blocking and non-blocking dequeue - The sending process will be no- tified when the message is read from the target queue. A return sta- tus will indicate if the message successfully dequeued from the queue.
• Blocking and non-blocking Acknowledge - The sending process will be notified when the target process confirms the message. A return status will indicate if the message was successfully confirmed by the target.
• Blocking and non-blocking Recoverable - The sending process will be notified when the recovery system has accepted the message. A return status will indicate if the message was successfully jour- nalled by the recovery system.
• Blocking and non-blocking Recoverable Acknowledge - The sending pro- cess will be notified when the target process has confirmed the re- coverable message. A return status will indicate if the message was successfully confirmed by the target process.

DECmessageQ Scripts Facility

• Capture - DECmessageQ scripts can be used to capture messages sent or received from a process. These messages can be displayed on the output device or collected in a disk file. The messages are dis- played in an ASCII file using the DECmessageQ scripts syntax.
• Simulation - A disk file containing DECmessageQ scripts commands can be used to simulate message traffic to a process. The commands use the DECmessageQ scripts syntax. The process will receive these messages after any DECmessageQ queue is scanned for receivable mes- sages.
• Replay - A replay is the simulation of messages previously captured.

HARDWARE REQUIREMENTS

SOFTWARE REQUIREMENTS

• DEC OSF/1 Operating System Version 1.2 or higher
• ULTRIX Operating System, Version 4.2 or higher
• HP-UX (HP9000-3xx, -4xx, -7xx, -8xx) Operating System, Version 8.xx or higher
• AIX Operating System Version 3.2 or higher
• Any 88open Binary Compatibility Standard - Compliant Operating Sys- tem
• SunOS Operating System Version 4.1.x or higher
• Solaris Operating System Version 2.1 or higher

GROWTH CONSIDERATIONS

DISTRIBUTION MEDIA

• 9-track 1600 BPI Magtape, TK50 Streaming Tape
DECmessageQ for HP-UX (HP9000-3xx,-4xx), DECmessageQ for 88open and DECmessageQ for SunOS, DECmessageQ for Solaris, and DECmessageQ for AIX:
• QICtape
DECmessageQ for HP-UX (HP9000-7xx,-8xx):
• 4MM DAT
DECmessageQ for DEC OSF/1 AXP and DECmessageQ for AIX:
• CD-ROM

ORDERING INFORMATION
Development Option

For DECmessageQ HP-UX (HP9000-7xx,8xx Platform) and AIX (RS6000 Plat- form) Version 2.2 products, purchased under YR-DMQ*X-** part numbers, call (203) 258-5235 for a free upgrade to the QL-2W*A*-AA Version 3.0 products that include the Message Recovery Services option. A valid Digital Order number and YR-DMQ*X-** part number are required to ob- tain the free upgrade. Layered Product Services ongoing support for these Version 3.0 upgrades must be purchased separately under the QT- 2W*A*-** part numbers.

SOFTWARE LICENSING

SOFTWARE PRODUCT SERVICES

SOFTWARE WARRANTY