Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.generator.model
Class FieldDSpec

java.lang.Object
  extended by com.ibm.etools.iseries.edit.generator.model.RPGCommon
      extended by com.ibm.etools.iseries.edit.generator.model.RPGDSpec
          extended by com.ibm.etools.iseries.edit.generator.model.FieldDSpec

public class FieldDSpec
extends RPGDSpec

Represents a Field Definition Specification in RPG.


Field Summary
static String copyright
           
 
Fields inherited from class com.ibm.etools.iseries.edit.generator.model.RPGCommon
fieldName, purpose
 
Constructor Summary
FieldDSpec()
           
 
Method Summary
 RPGFieldType getField()
           
 RPGDSpecKeywords getKeyword()
           
 void setField(RPGFieldType type)
           
 void setKeyword(RPGDSpecKeywords keywords)
           
 
Methods inherited from class com.ibm.etools.iseries.edit.generator.model.RPGDSpec
getCodeLoc, getConstant, getLength, getType, setCodeLoc, setConstant, setLength, setType
 
Methods inherited from class com.ibm.etools.iseries.edit.generator.model.RPGCommon
getMessages, getName, getPurpose, isValid, setFieldName, setPurpose
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

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

FieldDSpec

public FieldDSpec()
Method Detail

getField

public RPGFieldType getField()
Returns:

getKeyword

public RPGDSpecKeywords getKeyword()
Returns:

setField

public void setField(RPGFieldType type)
Parameters:
type -

setKeyword

public void setKeyword(RPGDSpecKeywords keywords)
Parameters:
keywords -

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.