Is there an instrument of indirection between a CICS TRAN and a load module ?
What I want is some tool / facility that operates in a CICS address space that can dynamically select the matched load module based on ... user group / racf / whatever.
The motivation behind this is that we have a limited number of CICS regions that we are able to use : this can't be increased in the short term. We need to have two separate versions of an application running in one environment : two (CICS) application plans, each having (obviously) a different packageset/collection. But critically, two separate, distinct application libraries with NO change to existing TRAN codes and NO change to existing application code.
CICS transaction definition is fixed to the initial program.
How your regions are configured for a given environment comes into play.
Without changing existing code in a single environment, the transaction could be defined to execute a new program which could EXEC CICS LINK dynamically to either of the two target programs based on whatever criteria you specify.
The difficulty, then, may be using different plans for those target programs. This might be done if the separate target programs execute in different AORs by having different DB2 definitions for each AOR.
Joined: 13 Jun 2012 Posts: 127 Location: United States
I ran into this situation at another client site in the past. The solution was to create mini-CICS regions. Stripped down versions of CICS that supported just a few transactions and only ran when needed... just like any batch job.