PH72239: ORIGIN DATA INCORRECTLY SENT FOR SYSTEM TASKS DURING A REMOTE EXEC CICS LINK

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When a system task (such as CPLT) issues an EXEC CICS LINK to a
  remote region over MRO, CICS incorrectly attempts to construct
  and send an Origin Data Record (ODR) even though no origin
  data exists for the task.
  
  The absence of origin data for the system task is confirmed when
  the monitoring domain reports GET_ODR returning NOT_FOUND:
  
  QR    MN 0B0A MNOD  ENTRY GET_ODR
  QR    MN 0B0B MNOD  EXIT  GET_ODR/EXCEPTION   NOT_FOUND
  
  However, CICS does not account for this case when constructing
  the outbound EXEC CICS LINK request. It incorrectly includes an
  ODR field and populates it with residual data left behind by
  previous application processing.
  
  The receiving region accepts this invalid data as legitimate
  origin data and processes it accordingly. This can lead to
  the corrupt origin data setting flags incorrectly in the
  receiving task's origin data causing unexpected behaviour.
  
  In one case, the corrupt origin data causes OTRANFLG(6) in the
  tasks transaction monitoring area (TMA) to contain x'C7', with
  bit 6 set, which causes the receiving CSMI task to have SRR
  (Security Request Recording) incorrectly activated.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Residual data is incorrectly sent for   *
  *                      tasks which do not contain any origin   *
  *                      data.                                   *
  ****************************************************************
  System tasks, such as CPLT, do not contain origin data, and so
  should not send an Origin Data Record (ODR) when executing an
  EXEC CICS LINK to a remote region. In some cases, CICS correctly
  identifies that no ODR can be located which can be observed
  via the following monitoring domain trace:
  
  QR    MN 0B0A MNOD  ENTRY GET_ODR
  QR    MN 0B0B MNOD  EXIT  GET_ODR/EXCEPTION   NOT_FOUND
  
  Further processing then leads to the task constructing an ODR
  populated with residual data and sending this to the remote
  region. As a result the remote region then receives corrupt
  data which can lead to unexpected behaviours.
  

Problem conclusion

• CICS has been updated to ensure residual data does not get
  interpreted and sent as origin data.
  

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:

  UO08939 UO08940 UO08941

Modules/Macros

• DFHXFP   DFHXFQ
  

Fix information

• Fixed component name

  CICS TS Z/OS V6

• Fixed component ID

  5655YA100

Applicable component levels

• R400 PSY UO08941

     UP26/08/14 P F608

• R500 PSY UO08940

     UP26/08/13 P F608

• R600 PSY UO08939

     UP26/08/13 P F608

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.