Rational Developer for Power Systems Software
V7.6

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

java.lang.Object
  extended by com.ibm.etools.iseries.rse.ui.actions.QSYSChangePasswordHelper
All Implemented Interfaces:
Runnable

public class QSYSChangePasswordHelper
extends Object
implements Runnable


Field Summary
static String copyright
           
 
Constructor Summary
QSYSChangePasswordHelper(SubSystem subsystem)
          Constructor
 
Method Summary
static void changePassword(Shell shell, SubSystem subsystem)
          Central place for the code that handles changing an iSeries password and updating the stored local passwords if required.
 void run()
           
 
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

QSYSChangePasswordHelper

public QSYSChangePasswordHelper(SubSystem subsystem)
Constructor

Parameters:
Subsytem - for the connection that needs the password changed.
Method Detail

run

public void run()
Specified by:
run in interface Runnable

changePassword

public static void changePassword(Shell shell,
                                  SubSystem subsystem)
Central place for the code that handles changing an iSeries password and updating the stored local passwords if required. This method must be called on the UI thread. If you are not on the UI thread they create an instance of this class and pass it to Display.syncExcec(...) or Display.asyncExec(...).

Parameters:
subsystem - The Subsystem which represents the remote system where the password should be changed.

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.