Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.subsystems.qsys.api
Class QSYSReturnCodeException

java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by com.ibm.etools.iseries.subsystems.qsys.api.QSYSReturnCodeException
All Implemented Interfaces:
Serializable

public class QSYSReturnCodeException
extends Exception

See Also:
Serialized Form

Field Summary
static String copyright
           
 
Constructor Summary
QSYSReturnCodeException()
          Constructor for QSYSReturnCodeException
QSYSReturnCodeException(String message)
          Constructor for QSYSReturnCodeException
QSYSReturnCodeException(String message, int returnCode)
          Constructor for QSYSReturnCodeException
 
Method Summary
 int getReturnCode()
           
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

copyright

public static String copyright
Constructor Detail

QSYSReturnCodeException

public QSYSReturnCodeException()
Constructor for QSYSReturnCodeException


QSYSReturnCodeException

public QSYSReturnCodeException(String message)
Constructor for QSYSReturnCodeException


QSYSReturnCodeException

public QSYSReturnCodeException(String message,
                               int returnCode)
Constructor for QSYSReturnCodeException

Method Detail

getReturnCode

public int getReturnCode()
See Also:
ReturnCodeException#getReturnCode()

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.