Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm.interfaces
Class ISeriesHostDisplayFileRecord

java.lang.Object
  extended by com.ibm.etools.iseries.comm.interfaces.ISeriesHostFormatDefinition
      extended by com.ibm.etools.iseries.comm.interfaces.ISeriesHostDisplayFileRecord
All Implemented Interfaces:
IISeriesHostDisplayFileRecord, IISeriesHostFormatDefinition

public class ISeriesHostDisplayFileRecord
extends ISeriesHostFormatDefinition
implements IISeriesHostDisplayFileRecord

IISeriesHostDisplayFileRecord is an interface which represents an iSeries display file record format. This interface is used by the ISeriesRetrieveDisplayFileDescription.


Field Summary
static String Copyright
           
 
Constructor Summary
ISeriesHostDisplayFileRecord()
           
 
Method Summary
 
Methods inherited from class com.ibm.etools.iseries.comm.interfaces.ISeriesHostFormatDefinition
getCCSID, getDescription, getFields, getFile, getID, getLength, getLibrary, getName, hasDBCSorGraphicData, setCCSID, setDBCSorGraphicData, setDescription, setFields, setFile, setID, setLength, setLibrary, setName
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 
Methods inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostFormatDefinition
getCCSID, getDescription, getFields, getFile, getID, getLength, getLibrary, getName, hasDBCSorGraphicData, setCCSID, setDBCSorGraphicData, setDescription, setFields, setFile, setID, setLength, setLibrary, setName
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

ISeriesHostDisplayFileRecord

public ISeriesHostDisplayFileRecord()

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.