Rational Developer for Power Systems Software
V7.6

Package com.ibm.etools.iseries.rse.ui.propertypages

Class Summary
AbstractJobPropertyPage Base abstract class for Job Property Pages.
CommandExecutionPropertyPage This property page is for properties related to command execution, including compiles and user-defined commands and actions.
EnvironmentVariablesPropertyPage Property page for editing persistent environment variables for an RSE connection.
FieldPropertyPage The property page for iSeries fields This is an output-only page.
IBMiSystemConnectionSubSystemsPropertyPage The property page for subsystem properties when accessed from the connection property page.
JobDefinitionPropertyPage Property page for Jobs - Definition properties.
JobInternationalPropertyPage Property page for Jobs - International properties
JobRunPropertyPage Property page for Jobs - Run properties
JobStatusPropertyPage Property page for Jobs - Status properties
LibPropertyPage The property page for filter string properties.
LibQualifiedComboBoxFieldEditor Uniquely for IBM i, a preference field editor that allows a library qualified prompt as in:
LibraryListPropertyPage This is the Communications Property Page that is common among all iSeries subsystems.
MbrPropertyPage The property page for filter string properties.
MessageDescriptionPropertyPage  
MessagePropertyPage  
ObjAdvancedDiskPropertyPage The property page for advanced properties (eg, Exhaustive) of a remote iSeries object.
ObjAdvancedPropertyPage The property page for advanced properties (eg, Exhaustive) of a remote iSeries object This is an output-only page.
ObjAdvancedSourcePropertyPage The property page for advanced properties (eg, Exhaustive) of a remote iSeries object.
RecordPropertyPage The property page for iSeries records, with information common to both database and device file records.
 


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.