code: private void removeDuringLogRead()
      {
          if (tc.isEntryEnabled())
              Tr.entry(tc, "removeDuringLogRead", new Object[] { this, String.valueOf(_payloadAdded) });
  
          // Inform the recovery log of the reduction in the data payload due to this unit being deleted.
          // We should not have any unwritten data at this juncture BUT play it safe - do what remove does.
          // The reason we don't simply call remove is partly because _storedOnDisk will be true and we
          // don't want to write out another deletion record.  More significant is that it is possible that
          // the RU hasn't actually added any payload - that will only have happened if a DataItem in a RU Section
          // has been processed for this RU so we check this via new instance variable _payloadAdded
  
          if (_payloadAdded)
          {
              if (_unwrittenDataSize > 0)
              {
                  _recLog.payloadDeleted(_totalDataSize + _totalHeaderSize, _unwrittenDataSize + _totalHeaderSize);
              }
              else
              {
                  _recLog.payloadDeleted(_totalDataSize + _totalHeaderSize, _unwrittenDataSize);
              }
          }
          // Next, "forget" all stored recoverable unit sections. See comments in remove method but in reality
          // since nothing holds a reference to this RU anymore this just helps garbage collection.
          if (tc.isEventEnabled())
              Tr.event(tc, "Remove during log read completed for recoverable unit " + _identity + ". Clear internal state");
          _recoverableUnitSections.clear();
          _totalDataSize = 0;
          _unwrittenDataSize = 0;
  
          if (tc.isEntryEnabled())
              Tr.exit(tc, "removeDuringLogRead", this);
      }
docs: <p>
  Informs the recoverable unit that it is being deleted during initial read of the logs.
  This method DOES NOT write anything to the logs it is merely used to discard any payload
  associated with the RU from the totalDataSize of the log.
  </p>
  
  <p>
  There is NO NEED to hold the shared lock before invoking this method because we only call this
  while opening the logs - this method is private and should not be called at ANY other point.
  </p>