Enable application programs to communicate with each other
IBM® WebSphere® MQ for z/VSE® is part of the IBM WebSphere MQ (formerly MQSeries®) family of products. It extends the reach of a service-oriented architecture (SOA) messaging backbone to the z/VSE computing platform. It provides application programming services that enable application programs to communicate with each other using message queues.
WebSphere MQ for z/VSE provides:
- Assured delivery to reduce the risk of data loss when networks fail.
- Time-independent applications with message queuing and synchronous applications.
- A consistent application program interface (API) across supported platforms.
- Chained message exit, channel batch interval and server and requester channels.
- Helps ensure that data being moved is not duplicated and completes as a single unit of work or transaction.
- Provides event-driven processing with applications that can be automatically triggered by messages arriving on a queue.
- Enables applications to be stopped when the message or messages have been processed.
- Enables time-independent message exchange between the sending and receiving programs.
- Allows an application to wait for a message to arrive on a queue—the server application can wait for request messages and send reply messages as requests are processed.
A consistent application program interface
- Helps make integrated programs portable, simpler and focused on application logic.
- Offers API crossing exits that enable you to write code that changes the behavior of WebSphere MQ API calls—then inserts that code before or after those calls automatically.
- Provides the ability for the queue manager to drive the exit code at registered points.
- Supports a chain of up to eight API exits.
Chained message exit, channel batch interval and server and requester channels
- Calls channel-exit programs at defined places in the processing carried out by Message Channel Agent (MCA) programs.
- Facilitates remote queuing to other queue managers and client connectivity.
- Supports a chain of up to eight send, receive and message exits.
- Keeps a batch open even if there are no messages on the transmission queue to enhance customer control of sender and server channel operation.
- Allows queue managers to request messages from remote systems—messages can accumulate on a remote system until they are needed.