PM77543: TRANSACTION EXECUTED IN TOR INSTEAD OF AORS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Transaction executed in TOR instead of AORs
  Scenario:
  One TOR and several AOR regions and CPSM.
  Runs a program in one of the AOR's which issues the command
  EXEC CICS START TRANSID(TEST) SYSID(TOR).
  The START request is function shipped to the TOR and
  then routed via CPSM to one of the AOR target regions.
  This works fine before PM56051 installed.
  The behavior has changed in this case that the transaction
  TEST runs now in the TOR region and is not routed to
  a target AOR.
  
  PM56051: UK78670 R600 UK78671 R700.
  

Local fix

• No
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A START request is statically routed    *
  *                      from region 1 to region 2 from where it *
  *                      should be dynamically routed to another *
  *                      region. However the dynamic routing     *
  *                      program is not invoked on region 2 and  *
  *                      the transaction runs locally.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A transaction is defined as DYNAMIC and ROUTABLE on all regions.
  A start request is issued on region 1 specifying the SYSID of
  region 2. The SYSID option causes the START to be statically
  routed to region 2, the dynamic routing program is invoked on
  region 1 for notification of the STATIC route, DYRFUNC = '3'.
  DFHEIIC running on region 1 ships the first 6 bytes of the
  dynamic routing commarea over to region 2 to notify region 2 of
  the DYROPTER setting. On region 2 receipt of the dynamic routing
  commarea causes the incoming request to be treated as if it had
  been dynamically routed from region 1, when in fact it was
  statically routed. Dynamically routing more than once is not
  permitted, so region 2 assumes the START is no longer eligible
  for dynamic routing and, as the transaction definition does not
  specify a remote SYSID, runs the START locally on region 2. The
  dynamic routing program on region 2 is not invoked for route
  selection.
  
  Additional keywords: CDST DFHDSRP
  

Problem conclusion

• CICS has been changed for the reported problem so that the first
  6 bytes of the commarea are no longer sent along with the START
  request to the target region, and the dynamic routing program is
  invoked on the target region for route selection (DYRFUNC=0).
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM75335

• APAR is sysrouted TO one or more of the following:

  UK91697

Modules/Macros

• DFHEIIC  DFHICP   DFHIC
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UK91697

     UP13/02/22 P F302

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.