Rational Developer for Power Systems Software

Package com.ibm.etools.iseries.subsystems.qsys.commands

Interface Summary
IQSYSCommandConstants Message related constants for QSYS subsystem.
IQSYSCommandSubSystemConfiguration An interface representing factories for creating RemoteProcessSubSystem objects.
IRemoteCommandContext This interface represents a place to hold contextual information stored within each remote object.
IRemoteCommandContextProvider Interface for objects that can provide a remote context.

Class Summary
InteractiveJob This class encapsulates the functions for the interactive job support.
QSYSCLParameterTokenizer Helper class for tokenizing CL parameter string and return each parameter as a token.
QSYSCommandLineParameterHandler This class handles the merging of the command string to be executed and the parameter string that is specified on the table view command line
QSYSCommandResources Message bundle class for QSYSObjectSubSystem.
QSYSCommandsUtil Utility class that can be used to get the correct command for the passed Object Supported Commands: Change Change Text Change Type Copy Delete Merge Rename Restore Save
QSYSEventFileInformation This class encapsulates event file information when an event-file-generating command is submitted to run.
QSYSNfsCommandHandler Helper class for running remote commands and refreshing the tree or table views if required.
QSYSParameterToken Help class to contain the information of a parameter to be used when adding the adding the command line parameters to the command
RemoteCommandContext Context provider for QSYS based objects, members, procedures, fields, etc...

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.