com.ibm.etools.iseries.comm.interfaces
Class ISeriesHostFieldNameOnly
java.lang.Object
com.ibm.etools.iseries.comm.interfaces.ISeriesHostObjectNameOnly
com.ibm.etools.iseries.comm.interfaces.ISeriesHostRecordNameOnly
com.ibm.etools.iseries.comm.interfaces.ISeriesHostFieldNameOnly
- All Implemented Interfaces:
- IISeriesHostFieldNameOnly, IISeriesHostObjectNameOnly, IISeriesHostRecordNameOnly
- Direct Known Subclasses:
- ISeriesHostFieldBasic
public class ISeriesHostFieldNameOnly
- extends ISeriesHostRecordNameOnly
- implements IISeriesHostFieldNameOnly
This class represents a single field on the AS/400.
It stores the name of the field, plus the library, file and record it is part of.
Note library, file and name properties are inherited we need only
worry here about the record property.
Copyright
public static final String Copyright
- See Also:
- Constant Field Values
record
protected String record
ISeriesHostFieldNameOnly
public ISeriesHostFieldNameOnly()
setRecord
public void setRecord(String name)
- Set the record name.
- Specified by:
setRecord
in interface IISeriesHostFieldNameOnly
getRecord
public String getRecord()
- Get the record name.
- Specified by:
getRecord
in interface IISeriesHostFieldNameOnly
toString
public String toString()
- For printing to a stream file
- Specified by:
toString
in interface IISeriesHostFieldNameOnly
- Specified by:
toString
in interface IISeriesHostObjectNameOnly
- Specified by:
toString
in interface IISeriesHostRecordNameOnly
- Overrides:
toString
in class ISeriesHostRecordNameOnly
writeObjectInfo
public void writeObjectInfo(PrintWriter writer)
- For debugging purposes
- Specified by:
writeObjectInfo
in interface IISeriesHostFieldNameOnly
- Specified by:
writeObjectInfo
in interface IISeriesHostObjectNameOnly
- Specified by:
writeObjectInfo
in interface IISeriesHostRecordNameOnly
- Overrides:
writeObjectInfo
in class ISeriesHostRecordNameOnly
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.