Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.verifiers.comm.bridge
Class FDINStruct

java.lang.Object
  extended by com.ibm.etools.iseries.edit.verifiers.comm.bridge.FDINStruct

public class FDINStruct
extends Object

This class corresponds to the CODE comm FDIN struct defined in evfcsys.h typedef struct { CHAR library[11]; Data base library name CHAR file[11]; Data base file name CHAR record[11]; Data base record name CHAR field[11]; Data base field name CHAR valCheck; Data base validity check } FDIN;


Field Summary
static String copyright
           
 
Constructor Summary
FDINStruct(CToJavaInputStream in)
          Constructor for FDINStruct.
 
Method Summary
 String getField()
          Returns the field.
 String getFile()
          Returns the file.
 String getLibrary()
          Returns the library.
 String getRecord()
          Returns the record.
 char getValCheck()
          Returns the valCheck.
 
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

FDINStruct

public FDINStruct(CToJavaInputStream in)
           throws IOException
Constructor for FDINStruct.

Throws:
IOException
Method Detail

getField

public String getField()
Returns the field.

Returns:
String

getFile

public String getFile()
Returns the file.

Returns:
String

getLibrary

public String getLibrary()
Returns the library.

Returns:
String

getRecord

public String getRecord()
Returns the record.

Returns:
String

getValCheck

public char getValCheck()
Returns the valCheck.

Returns:
char

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.