iSeries Remote Systems
v6.0.1

Package com.ibm.etools.iseries.core.resources

Interface Summary
IISeriesMarker This interface provides constants that are used for iSeries markers.
IISeriesRemoteEditConstants  
IISeriesRemoteEditPersistanceConstants  
IISeriesSaveAsQSYSDialog  
 

Class Summary
InternalDownloadMemberRunnable Internal class for downloading member
InternalUploadMemberRunnable Internal class for uploading member
ISeriesDebuggerMarkerAnnotationModel  
ISeriesEditableSrcPhysicalFileManager Manages files that have been persisted locally for editing
ISeriesEditableSrcPhysicalFileMember A representation of a remote iSeries source member for the purpose of local editing
ISeriesEditorCompareActionSrcPhysicalFileMember Ensure member is downloaded to compare directory
ISeriesEditorDecorationsContributor  
ISeriesEditorGetFileActionSrcPhysicalFileMember Ensure member is downloaded to get directory
ISeriesEditorLpexActionSrcPhysicalFileMember Class for integrating with the Lpex actions - compare, get to handle downloading our members correctly
ISeriesIFSEditorProfile  
ISeriesLinkedResourceMapper  
ISeriesMbrLockDialog Dialog to handle a member that has been locked.
ISeriesMemberTransfer  
ISeriesMixedCCSIDHandler This class handles records of members that have mixed CCSID.
ISeriesPropertyDialog The class is used to override the prefernece dialog so that we can display our own title for properties instead of the default perference
ISeriesQSYSEditorProfile  
ISeriesReadOnlySrcPhysicalFileMember Class that represents a source physical file that is downloadable to a special temp IFile
ISeriesRemoteCompareAction  
ISeriesRemoteEditRegistry  
ISeriesRemoteGetFileAction  
ISeriesSaveAsQSYSDialog  
ISeriesSaveAsQSYSForm  
 


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.