Name-mangling of the OPERATION field

The OPERATION field of the REQUESTMODEL definition is used to supply the name of the remote method that is to be matched by this request model. The GIOP request received at run-time includes an operation field which is compared to the OPERATION field on the request model. However, the value of the operation field is not always the same as the method name, as used on the stateless CORBA object or enterprise bean. If RMI-IIOP is being used (as always happens with enterprise beans and may happen with stateless CORBA objects), the method name undergoes a process known as “mangling” to change the method name into a canonical form suitable for transmission using IIOP. This mangled method name may not be the same as the original method name. The operation field in the REQUESTMODEL must supply the mangled version of the method name (or a pattern, using wildcard characters, that matches it).

The CICS-supplied CREA transaction can be used to create REQUESTMODEL definitions for enterprise beans that automatically deal with this name-mangling issue.

This mangling and de-mangling knowledge is compiled into the application's stub and tie classes generated using the RMI compiler (RMIC).

For more information about mangling, see Name mangling for Java.