com.ibm.etools.iseries.subsystems.qsys.comm
Class WaitForTimeout
java.lang.Object
  
java.lang.Thread
      
com.ibm.etools.iseries.subsystems.qsys.comm.WaitForTimeout
- All Implemented Interfaces: 
 - Runnable
 
public class WaitForTimeout
- extends Thread
 
 
 
 
 
 
 
| Methods inherited from class java.lang.Thread | 
activeCount, checkAccess, countStackFrames, currentThread, destroy, dumpStack, enumerate, getAllStackTraces, getContextClassLoader, getDefaultUncaughtExceptionHandler, getId, getName, getPriority, getStackTrace, getState, getThreadGroup, getUncaughtExceptionHandler, holdsLock, interrupt, interrupted, isAlive, isDaemon, isInterrupted, join, join, join, resume, setContextClassLoader, setDaemon, setDefaultUncaughtExceptionHandler, setName, setPriority, setUncaughtExceptionHandler, sleep, sleep, start, stop, stop, suspend, toString, yield | 
 
 
copyright
public static final String copyright
- See Also:
 - Constant Field Values
 
WAIT_REQUESTED
public static final int WAIT_REQUESTED
- See Also:
 - Constant Field Values
 
CANCEL_WAIT_REQUESTED
public static final int CANCEL_WAIT_REQUESTED
- See Also:
 - Constant Field Values
 
done
protected boolean done
targetThread
protected Thread targetThread
waitTime
protected int waitTime
WaitForTimeout
public WaitForTimeout(boolean quiet,
                      QSYSObjectSubSystem system,
                      int waitTime)
- Constructor
 
run
public void run()
- Thread run method
- Specified by:
 run in interface Runnable- Overrides:
 run in class Thread
 
 
 
setDone
public void setDone(boolean done)
- setDone(boolean)
 
 
getQSYSCommunicationsDiagnostic
protected QSYSCommunicationsDiagnostic getQSYSCommunicationsDiagnostic()
 
fireEvent
protected void fireEvent(ISystemResourceChangeEvent event)
 
Copyright © 2011 IBM Corp. All Rights Reserved. 
 Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.