iSeries Remote Systems
v6.0.1

Package com.ibm.etools.iseries.core.ui.actions.cmds

Class Summary
AbstractISeriesNewObjectAction The abstract base action for New->XXX actions, which launch wizards for creating new objects (vs file or members say).
ISeriesAddLiblEntryAction This is the action for putting up a dialog allowing users to add a library to the library list
ISeriesAddToLiblAction This is the action adding the selected library to the library list.
ISeriesChangeMessageDescriptionAction Change action for iSeries message description
ISeriesChangeObjAction Generic Change...
ISeriesChgCurLibAction This is the action for putting up a dialog allowing users to change their current library
ISeriesMoveDownLibraryAction The action allows users to move the currently selected library down in the library list
ISeriesMoveLiblEntryAction This is the action for putting up a dialog allowing users to move a library within the library list
ISeriesMoveUpLibraryAction The action allows users to move the currently selected library up in the library list
ISeriesNewDataAreaAction The action for New->Data Area, when a library object is selected.
ISeriesNewDataQAction The action for New->Data Queue, when a library object is selected.
ISeriesNewLibraryAction The action for New->Library, when a library filter is selected.
ISeriesNewMemberAction The action for New->Member, when a file object is selected.
ISeriesNewMessageDescriptionAction  
ISeriesNewMsgFileAction The action for New->Message File, when a library object is selected.
ISeriesNewOtherAction The action for New->OTHER.
ISeriesNewSourceFileAction The action for New->Source Physical File, when a library object is selected.
ISeriesRemoveLiblEntryAction The action allows users to remove the currently selected library from the library list
ISeriesSaveRestoreAction Save Restore action
 


iSeries Remote Systems
v6.0.1

Copyright © 2005 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.