com.ibm.etools.iseries.rse.util.evfparser
Class QSYSEventsFileProcessorBlock
java.lang.Object
com.ibm.etools.iseries.rse.util.evfparser.QSYSEventsFileProcessorBlock
public class QSYSEventsFileProcessorBlock
- extends Object
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
QSYSEventsFileProcessorBlock
public QSYSEventsFileProcessorBlock(QSYSEventsFileProcessorRecord record,
IFile eventsFile)
getInputFile
public QSYSEventsFileFileIDRecord getInputFile()
setInputFile
public void setInputFile(QSYSEventsFileFileIDRecord file)
addFile
public void addFile(QSYSEventsFileFileIDRecord file)
throws SystemMessageException
- Throws:
SystemMessageException
closeFile
public void closeFile(QSYSEventsFileFileEndRecord file)
throws SystemMessageException
- Throws:
SystemMessageException
getOutputFile
public QSYSEventsFileFileIDRecord getOutputFile()
setOutputFile
public void setOutputFile(QSYSEventsFileFileIDRecord file)
getMappingTable
public QSYSEventsFileMapTable getMappingTable()
isProcessorIDZero
public boolean isProcessorIDZero()
addErrorInformation
public void addErrorInformation(QSYSEventsFileErrorInformationRecord record)
processorEnded
public void processorEnded()
throws SystemMessageException
- Throws:
SystemMessageException
setPreviousProcessor
public void setPreviousProcessor(QSYSEventsFileProcessorBlock previous)
createMarkers
public void createMarkers(String type,
String project,
String connection,
String profile)
throws CoreException,
SystemMessageException
- Throws:
CoreException
SystemMessageException
modifyErrorInformation
public void modifyErrorInformation(QSYSEventsFileErrorInformationRecord error)
throws CoreException,
SystemMessageException
- Throws:
CoreException
SystemMessageException
addMarkerToFile
public void addMarkerToFile(QSYSEventsFileErrorInformationRecord error)
throws CoreException
- Throws:
CoreException
Copyright 2009 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.