Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm.interfaces
Interface IISeriesSQLStatementHeader

All Known Implementing Classes:
ISeriesSQLStatementHeader

public interface IISeriesSQLStatementHeader

This interface encapsulates the information returned by QSQCHKS API to check the SQL Statement on the iSeries.

See Also:
ISeriesSyntaxCheckSQLStatements

Field Summary
static String copyright
           
 
Method Summary
 String getMessageFileLibraryName()
          Message File Library Name
 String getMessageFileName()
          Message File Name
 int getNumberStatements()
          Number of Statements Processed
 List getStatementInfoList()
          Statement Information returned
 void setMessageFileLibraryName(String name)
           
 void setMessageFileName(String name)
           
 void setNumberStatements(int number)
           
 void setStatementInfoList(List stmtInfoList)
           
 

Field Detail

copyright

static final String copyright
See Also:
Constant Field Values
Method Detail

setMessageFileName

void setMessageFileName(String name)
Parameters:
Message - File Name

setMessageFileLibraryName

void setMessageFileLibraryName(String name)
Parameters:
Message - File Library Name

setNumberStatements

void setNumberStatements(int number)
Parameters:
Number - of Statements Processed

setStatementInfoList

void setStatementInfoList(List stmtInfoList)
Parameters:
List - containing the Statement Information returned

getMessageFileName

String getMessageFileName()
Message File Name


getMessageFileLibraryName

String getMessageFileLibraryName()
Message File Library Name


getNumberStatements

int getNumberStatements()
Number of Statements Processed


getStatementInfoList

List getStatementInfoList()
Statement Information returned


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.