Resource type TDEPLOCK: waits for transient data extrapartition requests

If you have a task suspended on resource type TDEPLOCK, with a resource name that corresponds to a transient data queue name, the task has issued a request against an extrapartition transient data queue. Another task is already accessing the same queue, and the waiting task cannot resume until that activity is complete.

If the wait is prolonged, it could be for either of the following reasons:
  • A task needs to change TCB mode to open and close a data set. The task must relinquish control while this happens, and, depending on the system loading, this might take several seconds. This contributes to the wait that the second task, suspended on resource type TDEPLOCK, experiences.
  • CICS® uses the access method QSAM to write data to extrapartition transient data destinations. QSAM runs synchronously with tasks that are requesting its services. This means that any task that invokes a QSAM service must wait until the QSAM processing is complete. If QSAM enters an extended wait for any reason, the requesting task also experiences an extended wait.

    An extended wait might occur when QSAM attempts to access an extrapartition data set. QSAM uses the MVS™ RESERVE volume-locking mechanism to gain exclusive control of volumes while it accesses them, which means that any other region that attempts to write to the same volume is forced to wait.

If tasks frequently get suspended on resource type TDEPLOCK, you need to determine which other transactions write data to the same extrapartition destination. You might then consider redefining the extrapartition destinations.



dfhs11t.html | Timestamp icon Last updated: Monday, 5 June 2017