Bean-to-bean communication

If your bean uses bean-to-bean communication with the same transaction id within the same AOR, setting MAXACTIVE to one will result in the communication not working. This is because the execution of the second transaction will be suspended waiting for a slot in which to execute, and the original bean will then experience a “timeout” condition. The way to avoid this is to take one of the following actions:

Note: When a bean is running inside a request processor, CICS® will only utilize requestmodels (and therefore start a new CICS transaction under the new transaction ID) if a remote method call made by that bean cannot be satisfied in the current request processor. A method call cannot be satisfied locally in the current request processor if: