Home » MQ Products for z/OS

MQ Authenticate User Security Exit for z/OS

The MQ Authenticate User Security Exit for z/OS (z/MQAUSX) is a solution that allows a company to fully authenticate a user who is accessing an IBM MQ resource. It authenticates the user's UserID and Password against the server's native z/OS system or an encrypted MQAUSX FBA file.

The security exit will operate with IBM MQ v5.3.1 v6.0, v7.0, v7.1, v8.0 and v9.0 in z/OS v1.4 or higher environments. It works with Server Connection, Client Connection, Sender, Receiver, Server, Requester, Cluster-Sender and Cluster-Receiver channels of IBM MQ queue manager. The pricing of Capitalware's z/MQAUSX solution is on a 'per queue manager' basis.

MQ Channel Encryption for z/OS

The MQ Channel Encryption for z/OS (z/MQCE) provides encryption for MQ message data. z/MQCE is a solution that allows a company to encrypt message data, which flows between IBM MQ resources. z/MQCE operates with IBM MQ for z/OS v5.3.1, v6.0, v7.0, v7.1, v8.0 and v9.0 in z/OS v1.4 or higher environments. It operates with Sender, Receiver, Server, Requester, Cluster-Sender, Cluster-Receiver, Server Connection and Client Connection channels of the MQ for z/OS queue managers.

The encryption exit is provided in the native z/OS load-module for z/OS v1.4 or higher. The pricing of Capitalware's z/MQCE solution is on a 'per queue manager' basis.

MQ Standard Security Exit for z/OS

The MQ Standard Security Exit for z/OS (z/MQSSX) is a solution that allows a company to control and restrict who is accessing an IBM MQ resource. The security exit will operate with IBM MQ v5.3.1, v6.0, v7.0, v7.1, v8.0 and v9.0 in z/OS v1.4 or higher environments. It works with Server Connection, Receiver, Requester and Cluster-Receiver channels of IBM MQ queue manager.

The MQ Standard Security Exit for z/OS solution is comprised of a server-side security exit.

The server-side security exit is provided in the format of a native z/OS load-module for z/OS v1.4 or higher. The pricing of Capitalware's z/MQSSX solution is on a 'per queue manager' basis.