Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.actions.errorlist
Class QSYSErrorListViewRemoveAction

java.lang.Object
  extended by SystemBaseAction
      extended by com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseAction
          extended by com.ibm.etools.iseries.rse.ui.actions.errorlist.QSYSErrorListViewRemoveAction

public class QSYSErrorListViewRemoveAction
extends QSYSSystemBaseAction

This class is used to remove lists from the error list view.

Since:
5.1

Field Summary
static String Copyright
           
 
Fields inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseAction
copyright
 
Constructor Summary
QSYSErrorListViewRemoveAction(String label, String tooltip, ImageDescriptor image, Shell parent, boolean removeAll, QSYSErrorListViewPart view)
          Constructor for ISeriesErrorListViewRemoveAction
 
Method Summary
 void run()
           
 
Methods inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseAction
getIBMiConnection, isAvailableOffline, updateSelection
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

QSYSErrorListViewRemoveAction

public QSYSErrorListViewRemoveAction(String label,
                                     String tooltip,
                                     ImageDescriptor image,
                                     Shell parent,
                                     boolean removeAll,
                                     QSYSErrorListViewPart view)
Constructor for ISeriesErrorListViewRemoveAction

Method Detail

run

public void run()
See Also:
IAction

Rational Developer for Power Systems Software
V7.6

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.