Rational Developer for i
7.5.0

com.ibm.etools.iseries.rse.util
Class ShowEventsFileInErrorListView

java.lang.Object
  extended by com.ibm.etools.iseries.rse.util.ShowEventsFileInErrorListView

public class ShowEventsFileInErrorListView
extends Object

Licensed Materials - Property of IBM (c) Copyright IBM Corporation 2008. All Rights Reserved. Note to U.S. Government Users Restricted Rights: Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.


Field Summary
static String Copyright
           
 
Constructor Summary
ShowEventsFileInErrorListView(Shell shell, IProgressMonitor monitor, QSYSEventFileInformation evfInfo)
          Call this after successfully reading the LDA (non-batch) or setting the event file name (batch) Retrieve and show events file.
 
Method Summary
protected  IRunnableContext getRunnableContext(Shell shell)
          Get an IRunnable context to show progress in.
 
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

ShowEventsFileInErrorListView

public ShowEventsFileInErrorListView(Shell shell,
                                     IProgressMonitor monitor,
                                     QSYSEventFileInformation evfInfo)
Call this after successfully reading the LDA (non-batch) or setting the event file name (batch) Retrieve and show events file.

Parameters:
shell - - shell to host error message dialog in case something goes wrong.
Method Detail

getRunnableContext

protected IRunnableContext getRunnableContext(Shell shell)
Get an IRunnable context to show progress in. If there is currently a dialog or wizard up with a progress monitor in it, we will use this, else we will create a progress monitor dialog.


Rational Developer for i
7.5.0

Copyright 2009 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.