Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.services.qsys.api
Interface IQSYSDeviceFileRecordFormat

All Superinterfaces:
IISeriesHostObjectNameOnly, IISeriesHostRecordBasic, IISeriesHostRecordDevice, IISeriesHostRecordNameOnly, IQSYSFileRecordFormat

public interface IQSYSDeviceFileRecordFormat
extends IISeriesHostRecordDevice, IQSYSFileRecordFormat

Interface representing an IBM i device record format.


Field Summary
static String copyright
           
 
Fields inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostRecordDevice
Copyright
 
Method Summary
 
Methods inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostRecordDevice
getBufferSize, getHasSeparateIndicatorArea, getHasStartingLineNumber, getLowestResponseIndicator, getType, setBufferSize, setHasSeparateIndicatorArea, setHasStartingLineNumber, setLowestResponseIndicator, setType
 
Methods inherited from interface com.ibm.etools.iseries.services.qsys.api.IQSYSFileRecordFormat
getAbsoluteName, getField, getParent, setParent
 
Methods inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostRecordBasic
getDescription, getFieldCount, getID, getLength, setDescription, setFieldCount, setID, setLength
 
Methods inherited from interface com.ibm.etools.iseries.comm.interfaces.IISeriesHostRecordNameOnly
getFile, getFileType, setFile, setFileType, toString, writeObjectInfo
 
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

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.