PK35274: DFHXFX IS NOT CHECKING THE FROM DATA AND LENGTH PARAMETERS ON AN EXEC CICS START WITH DYROPTER=N

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When DYROPTER=N, and an EXEC CICS START command is shipped over
  to a region, DFHXFX does not check the FROM data and the LENGTH.
  This causes the associated fields EIAARG4 and EIAARG5 not to be
  setup. In the customer scenario, these values were zero.
  This causes the transactions issuing the EXEC CICS START command
  to abend.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: FROM data not passed on non-terminal    *
  *                      START for a remote transaction.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A TOR transaction repeatedly issues non-terminal
  START TRANSID() FROM() requests for a transaction
  defined with DYNAMIC(YES) and ROUTABLE(YES). The AOR system is
  defined with Long Running Mirror (MROLRM=YES) tasks so the same
  mirror receives and processes all the requests.
  DYROPTER (re-invoke DFHDSRP at transaction termination) is
  initially set to N for the first START but changed to Y for the
  second START to facilitate the collection of additional
  diagnostics. Both START requests complete normally. DYROPTER is
  then reset to N for the third START, although the target
  transaction runs on the AOR it is not passed the START data. The
  RETRIEVE command gets a NORMAL response but the LENGTH is 10
  (instead of 20) and data unreadable. The RETRIEVE command does
  not fail but the bad data causes later application problems.
  The XFRRTDST flag is set in working storage for the mirror task
  when DYROPTER=Y is in use. The error on the third START is due
  to XFRRTDST being left on residually after the second START
  causing the wrong path to be taken through the transformer 2
  unwrap code run as part of mirror processing on the AOR. The
  code to setup the EIAARG4 and EIAARG5 (FROM data and length)
  fields in the EXEC parameter list for the START was not run
  leaving them with nulls values.
  The problem only occurs when the mirror on the back end is
  long running.
  
  Additional keywords: XRQARG0 CDST CSMI DFHXFX XFX XFORM2
  

Problem conclusion

• Transformer 2 unwrap processing in DHFXFX has been changed to
  initialize flag XFRRTDST for a non-terminal START with a FROM.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK34928

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

  UK20514

Modules/Macros

•    DFHXFX
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK20514

     UP06/12/19 P F612

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.