PM55314: EXEC CICS START REQUEST TIMES OUT WITH AZIG ABEND LOOPS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The customers application issues an EXEC CICS START request
  for transaction ABCD that is defined as dynamic.  The request
  is shipped to the selected target AOR which is currently at
  maxtask.  While waiting for a response from the other side, a
  timeout occurs.  This results in an AZIG abend that is cause by
  the applications HANDLE ABEND and the EXEC CICS START is
  retried.  CPSM is being used and this continues in a loop until
  CPSM exceeds the number of WNLE MAS list elements and issues an
  EYUWG0106E message with a dump.  As a victim, the CPSM dump
  occurs because it never gets called for the route complete or
  route terminate to free the WNLE.  However, the real problem is
  the application timing out the EXEC CICS START request for
  a transaction that is sent to a region that is at maxtask.
  
  Additional Keyword(s) and Symptom(s):
  KIXREVGJT
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Failure to call the distributed routed  *
  *                      exit program following abend AZIG.      *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the reported problem, an application issued an EXEC CICS
  START for a transaction defined as DYNAMIC and ROUTABLE. The
  distributed routed exit program, EYU9XLOP, was called to select
  a target region. The start request was routed successfully to
  the target region but was unable to run because it was at
  MAXTASK. This caused a TIMEOUT AZIG abend which was handled by
  the application. There was no call to the router exit as part of
  this.
  
  The application contained HANDLE logic to reissue itself and
  this was driven but the AOR was still at MAXTASK and the request
  abended and the process repeated itself. Message EYUWG0106E was
  eventually issued.
  
  The exit program should have been called with a route abend
  function code as part of abend processing.
  

Problem conclusion

• DFHEIIC has been amended, its recovery routine will issue
  a route_abend call to the AOR for routed dynamic transactions
  initiated via a START.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  UK77487 UK77488

Modules/Macros

•    DFHEIIC
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R600 PSY UK77487

     UP12/04/11 P F204

• R700 PSY UK77488

     UP12/04/11 P F204

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.