CICSPlex/SM DPL Dynamic Routing Target Scope program name based

When a dynamic DPL is executed from a CICS region, the criteria CICSPlex/SM uses to decide the CICS System Group (or CICS region) scope is mirror transaction name based, not based in the name of the remote program defined with Dynamic(YES).

In this customer environment, a Requesting/Routing region issues a dynamic DPL with an EXEC CICS LINK PROGRAM(PROGRAM1) TRANSID(TRN1) statement. In this Requesting/Routing region, it is necessary to have the accurate CICSPlex/SM definitions in order to send the DPL request to a Target Region belonging to a specific CICS System Group. The Workload Definition includes the Transaction Group Name and the Target Scope. But inside the Transaction Group it's only possible put transaction names, not program names. So, the choice of the CICS regions scope for the execution of the remote dynamic program is performed according to the asociated mirror transaction (TRN1), not to the name of the dynamic program (PROGRAM1).

In the nomenclature rules of this customer, the name of the mirror transaction (TRN1 in this example) only depends on the name of the application that issues the EXEC CICS LINK in the Requester/Router region. So, this transaction name is the same for any program called in the EXEC CICS LINK statement issued by a specific customer application. And customer needs different target AORs for different programs although the application originating the EXEC CICS LINK to be the same. So, this customer needs that CICSPlex/SM includes the ability to choose the Target Scope of the dynamic DPL taking in account the name of the dynamic program called in the EXEC CICS LINK statement and not only the associated transaction name.