If an error condition is encountered while a multi-note delete request is being processed, it could be the case that some, none, or all of the selected notes were deleted.

For example, suppose a delete notes request needs to send two delete operations to the coupling facility to delete all of the selected notes. After the first operation successfully deletes half the selected notes, the second operation could encounter a quiescing condition (or some other failure). The delete notes request completes with a return and reason code indicating that the request failed (in this example, due to a quiescing condition). In this particular case, some but not all of the intended notes were deleted.

If the failure is recognized before the first delete operation is processed, no notes would have been deleted. If the failure was recognized after the last delete operation is processed, all of the selected notes would have been deleted. If a new maximum tag value was to be set per the MAXTAG specification, the designated tag value might not have been set.

If an answer area is provided, the multi-note details (mapped by ixcynote_tDetailsNotes) might not be reported. If they are reported, the count of the number of notes that were deleted might be lower than the number of notes that were actually deleted.

You might need to reissue the delete request to be sure that all of the relevant notes are deleted.