com.ibm.etools.iseries.rse.util.evfparser
Class QSYSEventsFileExpansionProcessor
java.lang.Object
com.ibm.etools.iseries.util.evfparser.QSYSEventsFileExpansionProcessorCore
com.ibm.etools.iseries.rse.util.evfparser.QSYSEventsFileExpansionProcessor
- All Implemented Interfaces:
- IQSYSEventsFileProcessor
public class QSYSEventsFileExpansionProcessor
- extends QSYSEventsFileExpansionProcessorCore
Methods inherited from class com.ibm.etools.iseries.util.evfparser.QSYSEventsFileExpansionProcessorCore |
determineAndSetMappingSupport, doPreProcessing, getAllErrors, getAllFileIDRecords, processErrorRecord, processExpansionRecord, processFeedbackCodeRecord, processFileEndRecord, processFileIDRecord, processMapDefineRecord, processMapEndRecord, processMapStartRecord, processProcessorRecord, processProgramRecord, processTimestampRecord |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
QSYSEventsFileExpansionProcessor
public QSYSEventsFileExpansionProcessor(IFile eventsFile)
doPostProcessing
public boolean doPostProcessing()
throws SecondLevelHelpException
- Description copied from interface:
IQSYSEventsFileProcessor
- After parsing all records in the Events File, this method will be called to
process the records.
- Specified by:
doPostProcessing
in interface IQSYSEventsFileProcessor
- Overrides:
doPostProcessing
in class QSYSEventsFileExpansionProcessorCore
- Returns:
true
if post-processing was succesful. false
otherwise.
- Throws:
SecondLevelHelpException
constructEventsFileProcessorBlock
protected QSYSEventsFileProcessorBlockCore constructEventsFileProcessorBlock(QSYSEventsFileProcessorRecord record)
- Overrides:
constructEventsFileProcessorBlock
in class QSYSEventsFileExpansionProcessorCore
setProjectName
protected void setProjectName(String projectName)
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.