3.8 Creating New Binary Event Log Files
You can filter the contents of existing binary event logs and create a new binary event log file containing a subset of the events from the originals. When you create a new binary log file, SEA checks the events in the original binary event log file against the filter statement. All the events that meet the criteria specified by the filter statement are added to the new binary event log file. The new binary event log file can then be used for analysis, translation, or any other SEA process. The syntax for creating new binary event log files using the new common syntax is shown here:
wsea bin [input inputfile(s)] out outputfile [filterstatement] [skipconfig]For information on creating a new binary event log file with another syntax, refer to Appendix E.
By default, the system event log is used as the input file. If you want to process a different binary log file or files, you must specify the input file location and name.
See Section 3.9.1 for more information on working with input files.
You must specify a file name and location where the new binary output file will be saved. The output file parameter is mandatory when you are creating a new binary event log file.
You can specify the events from a binary event log file that you want to include in the new log file by defining a filter. If you do not define a filter, the new log file will contain all the events in the existing log file. For more information on filtering refer to Section 3.9.3.
Skipping Configuration Entries
If you are using the new common syntax, you can keep configuration entries from being automatically inserted by adding the skipconfig modifier to your command. This modifier prevents configuration entries from the original log files that are needed for analysis from being inserted into the new log file if they would normally be filtered out.