com.ibm.etools.iseries.core.evfparser
Interface IISeriesEventsFileRecordType
- All Known Implementing Classes:
- ISeriesEventsFileErrorInformationRecord, ISeriesEventsFileFeedbackCodeRecord, ISeriesEventsFileFileEndRecord, ISeriesEventsFileFileIDRecord, ISeriesEventsFileMapDefineRecord, ISeriesEventsFileMapEndRecord, ISeriesEventsFileMapStartRecord, ISeriesEventsFileProcessorRecord, ISeriesEventsFileProgramRecord, ISeriesEventsFileTimestampRecord
- public interface IISeriesEventsFileRecordType
This interface should be implemented by all classes that represent
records in an events file.
Copyright
public static final String Copyright
- See Also:
- Constant Field Values
TIMESTAMP
public static final String TIMESTAMP
- See Also:
- Constant Field Values
PROCESSOR
public static final String PROCESSOR
- See Also:
- Constant Field Values
FILE_ID
public static final String FILE_ID
- See Also:
- Constant Field Values
FILE_CONT
public static final String FILE_CONT
- See Also:
- Constant Field Values
FILE_END
public static final String FILE_END
- See Also:
- Constant Field Values
ERROR_INFORMATION
public static final String ERROR_INFORMATION
- See Also:
- Constant Field Values
PROGRAM
public static final String PROGRAM
- See Also:
- Constant Field Values
MAP_DEFINE
public static final String MAP_DEFINE
- See Also:
- Constant Field Values
MAP_START
public static final String MAP_START
- See Also:
- Constant Field Values
MAP_END
public static final String MAP_END
- See Also:
- Constant Field Values
FEEDBACK_CODE
public static final String FEEDBACK_CODE
- See Also:
- Constant Field Values
getRecordType
public String getRecordType()
- Get the record type.
- Returns:
- the record type.
Copyright © 2005 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.