PH51406: Abend ACRP when attempting to dynamically route over a previously unused LU6.2 connection

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The client has 2 TORs and they have an lu6.2 connection
  defined between them. Under certain circumstances the
  dynamic routing routing exit, DFHDYP, running in the
  first TOR, selects the second TOR to route a request to.
  If the connection has not been used before (work has not
  previously flown between the systems in this CICS lifecycle)
  then an abend ACRP is seen.
  
  
  This is because the routing code checks an internal flag,
  tcse_routable_start, in order to determine whether or not
  the remote end supports routed start requests. This bit is
  only set on when the two sides have their initial
  conversation - i.e. not when the connection is established.
  
  If the routing code finds that the bit has not been set then
  it doesn't route there and the abend is triggered.
  

Local fix

• Issue a CRTE SYSID=connectionid - after that, the routing
  works properly.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Abend ACRP can be seen when attempting  *
  *                      to dynamically route a terminal related *
  *                      START request over an LU6.2 connection. *
  ****************************************************************
  When attempting to route a terminal related START request
  dynamically using the Enhanced Method of routing, an ACRP abend
  can be seen if the LU6.2 connection between the systems has not
  previously been used.
  This is because an internal flag is used to check that the
  other side of the connection supports routable start requests
  before work is attempted to be routed. This flag is set the
  first time the systems communicate and not when the connection
  is established.
  As it is not known at this point if the other side of the
  connection supports this type of request, CICS avoids sending
  work there and abends ACRP.
  

Problem conclusion

• All currently in service releases of CICS TS support routable
  starts, making the flag to check for this support redundant.
  The check for this flag has been removed.
  

Temporary fix

Comments

APAR Information

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

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

  UI90651

Modules/Macros

• DFHAPRT
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R300 PSY UI90651

     UP23/02/23 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.