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 channel security exit will operate with IBM MQ v5.3.1 v6.0, v7.0, v7.1, v8.0, v9.0, v9.1, v9.2, v9.3 and v9.4 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 Connection Inspector for z/OS
The MQ Channel Connection Inspector for z/OS (z/MQCCI) is a solution that allows a company to track and/or audit what information a client application or remote queue manager is exchanging with the local queue manager when a connection is made. z/MQCCI is comprised of an MQ Channel Security Exit. A channel security exit is ONLY invoked/called by the queue manager's MCA (Message Channel Agent) for MQCONN/X and MQDISC API calls (so it is very light-weight).
The channel security exit is provided in the native z/OS load-module for z/OS v1.4 or higher. The pricing of Capitalware's z/MQCCI 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, v9.0, v9.1, v9.2, v9.3 and v9.4 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.