com.ibm.etools.iseries.core
Interface IISeriesFilterTypes
- public interface IISeriesFilterTypes
Our qsys file system filters are typed. The type is just a string,
which is stored permanently in the filter. These constants are for
those types.
Copyright
public static final String Copyright
- See Also:
- Constant Field Values
FILTERTYPE_LIBRARY
public static final String FILTERTYPE_LIBRARY
- See Also:
- Constant Field Values
FILTERTYPE_LIBRARYLIST
public static final String FILTERTYPE_LIBRARYLIST
- See Also:
- Constant Field Values
FILTERTYPE_OBJECT
public static final String FILTERTYPE_OBJECT
- See Also:
- Constant Field Values
FILTERTYPE_MEMBER
public static final String FILTERTYPE_MEMBER
- See Also:
- Constant Field Values
FILTERTYPE_COMMAND
public static final String FILTERTYPE_COMMAND
- See Also:
- Constant Field Values
FILTERTYPE_JOB
public static final String FILTERTYPE_JOB
- See Also:
- Constant Field Values
FILTERTYPE_IFS
public static final String FILTERTYPE_IFS
- See Also:
- Constant Field Values
FILTERTYPE_LIBRARY_PROMPT
public static final String FILTERTYPE_LIBRARY_PROMPT
- See Also:
- Constant Field Values
FILTERTYPE_LIBRARYLIST_PROMPT
public static final String FILTERTYPE_LIBRARYLIST_PROMPT
- See Also:
- Constant Field Values
FILTERTYPE_OBJECT_PROMPT
public static final String FILTERTYPE_OBJECT_PROMPT
- See Also:
- Constant Field Values
FILTERTYPE_MEMBER_PROMPT
public static final String FILTERTYPE_MEMBER_PROMPT
- See Also:
- Constant Field Values
FILTERTYPE_COMMAND_PROMPT
public static final String FILTERTYPE_COMMAND_PROMPT
- See Also:
- Constant Field Values
FILTERTYPE_JOB_PROMPT
public static final String FILTERTYPE_JOB_PROMPT
- See Also:
- Constant Field Values
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.