DFS2643I NUMBER OF CI'S USED BY SEQUENTIAL DEPENDENT SEGMENTS xxxxxxx


or

DELETE STOPPED PREMATURELY ON CI OWNED BY PARTNER id

Explanation

There are two forms of this message.

The first form of the message shows the number of control intervals (CIs) used by the sequential dependent segments listed in the message text.

The second form of the message is issued only if a DEDB Sequential Dependent Delete utility does not delete up to the user-specified CI RBA or the default CI RBA.

Processing of the DEDB Sequential Dependent Delete utility stopped because the identified IMS sharing partner holds an SDEP CI. This situation can occur when:
  • A partner IMS failure retains a CI for its emergency restart.
  • A partner IMS is not inserting SDEP segments into the area at a rate that fills the preallocated CI encountered by the Delete utility.
  • A program or transaction is stopped after an abend.

System action

Utility processing stops.

System programmer response

Determine why the partner is holding the CI. Issue a /DISPLAY AREA or QUERY AREA command to show the SDEP CI utilization for one partner. The IMS partner might be waiting for some resource (for example, a log data set, a resource with which to schedule a program, a DBRC request, or a lock). The hardware and operating system on which the IMS partner is executing might be constrained or not have sufficient capacity to keep up with the rest of the sharing group.

To make the CIs following the held CI available to the Delete utility, you can take one of these actions:
  • Use the QUITCI option of the Database Scan or Delete utility to cause the IMS partner that owns the CI to release the CI.

    Make sure that any SDEP segments contained in this CI are retrieved by the SCAN utility and put in an output file before rerunning the DELETE utility after the QUITCI option was used.

    Attention: After a CI is deleted, any data that it contained is not accessible.
  • Wait until the partner releases the CI and run the Delete utility again.