Rational Developer for Power Systems Software
V7.6

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


public interface IISeriesMessageDescription


Field Summary
static String Copyright
           
 
Method Summary
 String getAbsoluteName()
          From base class.
 String getFileName()
          Returns the name of the message file which contains this message description.
 String getHelp()
          Retrieve the message help
 String getID()
          Retrieve the message id
 String getLibraryName()
          Returns the library name where the message file containing this message description is located
 String getMessage()
           
 String getSeverity()
          Retrieve the message severity Not implemented yet!
 String getText()
          Retrieve the message text
 

Field Detail

Copyright

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

getAbsoluteName

String getAbsoluteName()
From base class.

Return the absolute object name, which should be the same as calling getAbsoluteName on this object's remote adapter.

We return lib/msgf MSGID(id)


getText

String getText()
Retrieve the message text


getHelp

String getHelp()
Retrieve the message help


getID

String getID()
Retrieve the message id


getSeverity

String getSeverity()
Retrieve the message severity Not implemented yet!


getMessage

String getMessage()

getLibraryName

String getLibraryName()
Returns the library name where the message file containing this message description is located


getFileName

String getFileName()
Returns the name of the message file which contains this message description.


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.