com.ibm.etools.iseries.services.qsys.commands
Class QSYSInteractiveJobStatusMonitor
java.lang.Object
com.ibm.etools.iseries.services.qsys.commands.QSYSInteractiveJobStatusMonitor
- All Implemented Interfaces:
- IQSYSInteractiveJobStatusMonitor
public class QSYSInteractiveJobStatusMonitor
- extends Object
- implements IQSYSInteractiveJobStatusMonitor
|
Method Summary |
String |
getMessage()
|
boolean |
isDone()
Notifies that the work is done; that is, either the main task is completed
or the user cancelled it. |
void |
setDone(boolean value)
Sets the done state to the given value. |
void |
setMessage(String message)
|
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
QSYSInteractiveJobStatusMonitor
public QSYSInteractiveJobStatusMonitor()
getMessage
public String getMessage()
- Specified by:
getMessage in interface IQSYSInteractiveJobStatusMonitor
isDone
public boolean isDone()
- Description copied from interface:
IQSYSInteractiveJobStatusMonitor
- Notifies that the work is done; that is, either the main task is completed
or the user cancelled it. This method may be called more than once
(implementations should be prepared to handle this case).
- Specified by:
isDone in interface IQSYSInteractiveJobStatusMonitor
setDone
public void setDone(boolean value)
- Description copied from interface:
IQSYSInteractiveJobStatusMonitor
- Sets the done state to the given value.
- Specified by:
setDone in interface IQSYSInteractiveJobStatusMonitor
- Parameters:
value - true indicates that this operation has finished
false clears this flag- See Also:
IQSYSInteractiveJobStatusMonitor.isDone()
setMessage
public void setMessage(String message)
- Specified by:
setMessage in interface IQSYSInteractiveJobStatusMonitor
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.