code: public void force() throws InternalLogException
    {
      if (tc.isEntryEnabled()) Tr.entry(tc, "force", this);
  
      // If the parent recovery log instance has experienced a serious internal error then prevent
      // this operation from executing.
      if (_recLog.failed())
      {
        if (tc.isEntryEnabled()) Tr.exit(tc, "force",this);
        throw new InternalLogException(null);
      }
  
      try
      {
        this.write();
      }
      catch(InternalLogException exc)
      {
        FFDCFilter.processException(exc, "com.ibm.ws.recoverylog.spi.SQLRecoverableUnitSectionImpl.force", "509", this);
        if (tc.isEntryEnabled()) Tr.exit(tc, "force", exc);
        throw exc;
      }
  
      if (tc.isEntryEnabled()) Tr.exit(tc, "force");
    }
docs: <p>
  Forces to the underlying recovery log any information in the target recoverable
  unit section that has not already been written by a previous call. This ensures
  that the recovery log contains an up to date copy of the information retained
  in the target recoverable unit section.
  </p>
  
  <p>
  The information is written to the underlying recovery log and forced
  through to persisent storage. After this call, the information is
  guaranteed to be retrieved during any post-failure recovery processing.
  </p>
  
  <p>
  This call my be used as part of an optomization when several recoverable unit
  sections need to be pushed to disk. For example, the following sequence will
  ensure that recoverable unit sections 1 through 4 are all persisted to
  physical storage:-
  </p>
  <p>
  <ul>
  <li>RecoverableUnitSection1.writeSection()</li>
  <li>RecoverableUnitSection2.writeSection()</li>
  <li>RecoverableUnitSection3.writeSection()</li>
  <li>RecoverableUnitSection4.forceSection()</li>
  </ul>
  </p>
  
  @exception InternalLogException An unexpected error has occured.