Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.actions
Class QSYSRemoveLiblEntryAction

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.QSYSAbstractLiblAction
              extended by com.ibm.etools.iseries.rse.ui.actions.QSYSRemoveLiblEntryAction
Direct Known Subclasses:
ISeriesTableViewRemoveLiblEntryAction

public class QSYSRemoveLiblEntryAction
extends QSYSAbstractLiblAction

The action allows users to remove the currently selected library from the library list


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSAbstractLiblAction
conn400, connection, parentFilter
 
Constructor Summary
QSYSRemoveLiblEntryAction(Shell parent)
          Constructor
 
Method Summary
 void run()
          This is the method called when the user selects this action.
 
Methods inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSAbstractLiblAction
checkObjectType, getSelectedLibrary, setAS400Connection, setParentFilter
 
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

QSYSRemoveLiblEntryAction

public QSYSRemoveLiblEntryAction(Shell parent)
Constructor

Method Detail

run

public void run()
This is the method called when the user selects this action.

See Also:
Action#run()

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.