Rational Developer for Power Systems Software
V7.6

Package com.ibm.etools.iseries.util.evfparser

Interface Summary
IMarkerCreator  
IQSYSEventsFileProcessor This interface defines a backbone for processing Events File Records.
As the Events File Format gets more complex and more used, the parsing logic should be seperated from the processing logic.
IQSYSEventsFileRecordType This interface should be implemented by all classes that represent records in an events file.
 

Class Summary
EventsFileParserCore This is an operation that parses an event file, and opens it in the Error List view
QSYSEventsFileErrorInformationRecord This class represents a Error Information record in an events file.
QSYSEventsFileExpansionProcessorCore  
QSYSEventsFileExpansionRecord This class represents an Expansion record in an Events File.
QSYSEventsFileFeedbackCodeRecord This class represents a Feedback Code record in an events file.
QSYSEventsFileFileEndRecord This class represents a File End record in an events file.
QSYSEventsFileFileIDRecord This class represents a File ID record in an events file.
QSYSEventsFileMapDefineRecord This class represents a Map Define record in an events file.
QSYSEventsFileMapEndRecord This class represents a Map End record in an events file.
QSYSEventsFileMapStartRecord This class represents a Map Start record in an events file.
QSYSEventsFileMapTable  
QSYSEventsFileProcessorBlockCore  
QSYSEventsFileProcessorRecord This class represents a Processor record in an events file.
QSYSEventsFileProgramRecord This class represents a Program record in an events file.
QSYSEventsFileTimestampRecord This class represents a Timestamp record in an events file.
 


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.