Rational Developer for Power Systems Software

Class ISeriesDataTableViewRecordUpdateAction

  extended by SystemBaseAction
      extended by com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseAction
          extended by com.ibm.etools.iseries.rse.ui.actions.datatableview.ISeriesDataTableViewRecordUpdateAction

public class ISeriesDataTableViewRecordUpdateAction
extends QSYSSystemBaseAction

This action deletes the selected items when Delete is pressed

Field Summary
static int ADD_RECORD
static String copyright
static int DELETE_RECORD
static int UPDATE_RECORD
Constructor Summary
ISeriesDataTableViewRecordUpdateAction(Shell parent, ISeriesDataTableView target, int type)
          Constructor for ISeriesTableViewShowAllAction
Method Summary
 void run()
          Run the action
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


public static final String copyright
See Also:
Constant Field Values


public static final int ADD_RECORD
See Also:
Constant Field Values


public static final int UPDATE_RECORD
See Also:
Constant Field Values


public static final int DELETE_RECORD
See Also:
Constant Field Values
Constructor Detail


public ISeriesDataTableViewRecordUpdateAction(Shell parent,
                                              ISeriesDataTableView target,
                                              int type)
Constructor for ISeriesTableViewShowAllAction

Method Detail


public void run()
Run the action

Rational Developer for Power Systems Software

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.