Rational Developer for Power Systems Software
V7.6

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

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

public class QSYSCompileSingleProgramAction
extends QSYSSystemBaseAction


Field Summary
static String Copyright
           
 
Fields inherited from class com.ibm.etools.iseries.rse.ui.actions.QSYSSystemBaseAction
copyright
 
Constructor Summary
QSYSCompileSingleProgramAction(String label, String tooltip, ImageDescriptor image, Shell parent)
          Constructor for ISeriesCompileSingleProgramAction
 
Method Summary
 void process(IQSYSProgram element)
          Process
 void run()
          Runs 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

Copyright

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

QSYSCompileSingleProgramAction

public QSYSCompileSingleProgramAction(String label,
                                      String tooltip,
                                      ImageDescriptor image,
                                      Shell parent)
Constructor for ISeriesCompileSingleProgramAction

Method Detail

run

public void run()
Runs the action


process

public void process(IQSYSProgram element)
Process


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.