code: private boolean initializationOutstanding(RecoveryAgent recoveryAgent, FailureScope failureScope) {
          if (tc.isEntryEnabled())
              Tr.entry(tc, "initializationOutstanding", new Object[] { recoveryAgent, failureScope, this });
  
          boolean outstanding = false;
  
          synchronized (_outstandingInitializationRecords) {
              // Extract the set of failure scopes that the corrisponding client service is currently
              // processing.
              final HashSet failureScopeSet = _outstandingInitializationRecords.get(recoveryAgent);
  
              // If there are some then determine if the set contains the given FailureScope.
              if (failureScopeSet != null) {
                  outstanding = failureScopeSet.contains(failureScope);
              }
          }
  
          if (tc.isEntryEnabled())
              Tr.exit(tc, "initializationOutstanding", outstanding);
          return outstanding;
      }
docs: <p>
  Internal method to determine if there is an outstanding 'serialRecoveryComplete'
  call that must be issued by the client service represented by the supplied
  RecoveryAgent for the given failure scope.
  </p>
  
  <p>
  Just prior to requesting a RecoveryAgent to "initiateRecovery" of a
  FailureScope, the addInitializationRecord method is driven to record the
  request. When the client service completes the serial portion of the recovery
  process and invokes serialRecoveryComplete, the removeInitializationRecord method
  is called to remove this record.
  </p>
  
  <p>
  This allows the RLS to track the "serial" portion of an ongoing recovery process.
  </p>
  
  <p>
  [ SERIAL PHASE ] [ INITIAL PHASE ] [ RETRY PHASE ]
  </p>
  
  @param recoveryAgent The RecoveryAgent.
  @param failureScope The FailureScope.
  
  @return boolean true if there is an oustanding recovery request, otherwise false.