Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm.interfaces
Interface IISeriesHostMemberNameOnly

All Superinterfaces:
IISeriesHostObjectNameOnly
All Known Subinterfaces:
IISeriesHostMemberBasic, IISeriesHostMemberBrief, IQSYSDataMember, IQSYSMember, IQSYSSourceMember
All Known Implementing Classes:
ISeriesHostMemberBasic, ISeriesHostMemberBrief, ISeriesHostMemberNameArray, ISeriesHostMemberNameOnly, QSYSHostDataMember, QSYSHostMember, QSYSHostSourceMember, QSYSRemoteDataMember, QSYSRemoteMember, QSYSRemoteSourceMember

public interface IISeriesHostMemberNameOnly
extends IISeriesHostObjectNameOnly

This interface represents the simplest of host member list requests, returning only the name. Well, actually the name plus the library and file name the member is in. This context info is important when doing multi-generic list requests so you can tell where the member name came from. Note we inherit get/set for Library and Name, so only need to supply File.


Field Summary
static String Copyright
           
 
Method Summary
 String getFile()
           
 void setFile(String name)
           
 String toString()
           
 void writeObjectInfo(PrintWriter writer)
           
 
Methods inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostObjectNameOnly
getLibrary, getName, setLibrary, setName
 

Field Detail

Copyright

static final String Copyright
See Also:
Constant Field Values
Method Detail

setFile

void setFile(String name)

getFile

String getFile()

toString

String toString()
Specified by:
toString in interface IISeriesHostObjectNameOnly
Overrides:
toString in class Object

writeObjectInfo

void writeObjectInfo(PrintWriter writer)
Specified by:
writeObjectInfo in interface IISeriesHostObjectNameOnly

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.