Rational Developer for Power Systems Software
V7.6

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

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.QSYSVerifyConnectionAction

public class QSYSVerifyConnectionAction
extends QSYSSystemBaseAction


Field Summary
static String copyright
           
 
Constructor Summary
QSYSVerifyConnectionAction(Shell shell)
          Constructor.
 
Method Summary
 void run()
           
 void run(SubSystem subsystem)
          Run method to allow the action to be run in the context of an existing connection without the user first having to select the connection.
 
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

QSYSVerifyConnectionAction

public QSYSVerifyConnectionAction(Shell shell)
Constructor.

Parameters:
shell - Shell of parent window, used as the parent for the dialog. Can be null, but be sure to call setParent before the action is used (ie, run).
Method Detail

run

public void run()
See Also:
SystemBaseAction#run()

run

public void run(SubSystem subsystem)
Run method to allow the action to be run in the context of an existing connection without the user first having to select the connection.

Parameters:
subsystem - The subsystem to use to retrieve the remote system's hostname

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.