PI08308: DFHDS0002 SEVERE ERROR (CODE X'0067') AND DFHTD0180 MESSAGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CICS region abended following these messages:
  .
  DFHDS0002 A severe error (code X'0067') has occurred in module
             DFHDSSR.
  DFHTD0180 Unexpected response (code X'04') and reason
             (code X'06') from a DFHDSSRM call.
  .
  Task 1 is reading a logically recoverable TD queue. It has the
  DCT lock and the READQ ENQ to serialise READQs against the
  queue. Meanwhile task 2 has been writing to the queue. It had
  the DCT lock around the WRITEs and it has the WRITEQ ENQ to
  serialise against other tasks writing to the queue. Task 2
  issues a syncpoint and needs the DCT lock held by task 1.
  .
  Meanwhile, task 1 (in intra_get_lr) has issued the DSSRI call
  to get its default suspend/resume token. It needs this as the
  task has tried to read an uncommitted record on the queue
  (written by task 2 earlier). Task 1 has to wait until task 2
  has committed its WRITEQs and resumes any READQs waiting on the
  records. The token is returned, and put into
  TDDCT_SUSPEND_TOKEN. Then the DCT lock is released before
  task 1 issues its suspend.
  .
  This allows task 2 to run and complete its commit work. This
  includes resuming any waiters - it does this by resuming the
  TDDCT_SUSPEND_TOKEN, then clearing this token field in the DCT
  to 0. A bit later on, task 1 gets to issue its suspend.
  Dispatcher gets the suspend token of 0 and rejects it with the
  DS0002 invalid suspend token error (SUSP_INVALID_SUSP_TOK).
  .
  Additional Symptom(s) Search Keyword(s):
  KIXREVSLD
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: DFHDS0002 severe error (CODE X'0067')   *
  *                      followed by DFHTD0180 message.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Task 1 is reading a logically recoverable TD queue. It has the
  DCT lock and the READQ ENQ to serialise READQs against the
  queue. Meanwhile task 2 has been writing to the queue. It had
  the DCT lock around the WRITEs and it has the WRITEQ ENQ to
  serialise against other tasks writing to the queue. Task 2
  issues a syncpoint and needs the DCT lock held by task 1.
  Meanwhile, task 1 (in intra_get_lr) has issued the DSSRI call
  to get its default suspend/resume token. It needs this as the
  task has tried to read an uncommitted record on the queue
  (written by task 2 earlier). Task 1 has to wait until task 2
  has committed its WRITEQs and resumes any READQs waiting on the
  records. The token is returned, and put into
  TDDCT_SUSPEND_TOKEN. Then the DCT lock is released before
  task 1 issues its suspend.
    This allows task 2 to run and complete its commit work. This
  includes resuming any waiters - it does this by resuming the
  TDDCT_SUSPEND_TOKEN, then clearing this token field in the DCT
  to 0. A bit later on, task 1 gets to issue its suspend.
  Dispatcher gets the suspend token of 0 and rejects it with the
  DS0002 invalid suspend token error (SUSP_INVALID_SUSP_TOK).
  KEYWORDS: msgdfhtd0180 dfhtd0180 td0180 td 0180 180
            msgdfhds0002 dfhds0002 ds0002 ds 0002 002 02 2
  

Problem conclusion

• DFHTDB has been changed to preserve the suspend/resume token in
  lifo so that it is still valid when the task issues a
  suspend upon it.
  

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:

  UI15115

Modules/Macros

• DFHTDB
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UI15115

     UP14/02/20 P F402

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.