How mangling affects CICS

Although the support for IIOP within CICS® contains code that implements the mangling rules, there is very little visible effect on the way you configure and use your CICS system. There are just two situations in which you need to be aware that mangling takes place. They are:
When defining REQUESTMODELs
REQUESTMODEL resource definitions map inbound IIOP request to CICS transactions. When an inbound request initiated by a Java remote method invocation is received, the OPERATION attribute in the REQUESTMODEL is compared with the mangled name in the inbound request to determine if the REQUESTMODEL matches the request. If it is possible that mangling can take place, do not specify a method name in the OPERATION attribute of the REQUESTMODEL, but specify a generic operation instead.
When creating debugging profiles for Java programs
Debugging profiles specify which program instances are to run under the control of a debugger. When an inbound request initiated by a Java remote method invocation is received, the method field of the debugging profile is compared with the mangled name in the inbound request to determine if the profile matches the request. If it is possible that mangling can take place, do not specify a method name in the debugging profile, but specify a generic method instead.
CAUTION: Although - in theory - its is possible to deduce the mangled names corresponding to each method, it is not a simple task, and is not advisable. To do so, you will need a thorough knowledge of the mangling rules, and of all the method names used in your application. There is also a risk that small changes to an application can change a mangled name.