IMS AMS - Advanced Message Service

Implement IMS functionality to support MQ Series Advanced Message Services (AMS) for transactions using the IMS-bridge connection.
IMS applications are already today able explore this functionality if the design is to use MQ explicit access to the MQ queue. But explicit access to MQ comes with some limitations and increased cost.
Limitations such as that a transactions need to be executed serialized since the trigger mechanism in MQ is based on the MQ queue and an application by default reads one triggered queue.
Compared to IMS were one or more instances of a program reads the same queue and therefor by default can access transactions from the IMS queue in parallel.
The increased cost is introduced with the extra MQI calls needed since the application now have to access the data from the MQ queue (using MQCONN, MQOPEN, MQGET, MQCLOSE and MQDISCON).
With this overhead execution- and responsetimes can also be increased so much that an IMS transactions that would benefit of 'AMS' takes to long to execute.
If the 'AMS' functionality can be supported by IMS (OTMA), the IMS applications will be able to use 'AMS' fuctionality to a lower cost and for applications that need to be scalable.
Two options/places to have the encrypted data terminated.
1st option is when data is delivered from OTMA, before it gets written to the IMS queue.
2nd option is to have data encrypted all the way to the application and decrypt at GU/GN time.
With the second option we will get an end-to-end secure connection between the client and application.