		      Linux System Event Log Viewer - Release Notes
		         Copyright (c) 2008, Intel Corporation
			          All Rights Reserved
			             August 31, 2008

The system event log (SEL) viewer utility is a Linux based application program 
used for displaying data from the BMC's system event log.


RELEASE NOTES FOR SEL Viewer VERSION 2.0.1 Build 4

A. SUPPORTED PLATFORMS

   Tylersburg platforms.

B. DEPENDENCIES
   
   1. Executes with GUI under the Linux XServer and as a Command Line Interface on 
   Shell.

   2. JRE must be installed. Most of the GNU/Linux distributions come with
   a default JRE installation. It does not support the java UI (Swing) libraries. 
	So a proper SUN JRE must be installed. SUN JRE can be downloaded from 
   http://www.java.com/en/download/manual.jsp#lin. After installing JRE, make
   sure that java would point to the newly installed JRE. This can be done by 
   creating a soft link (by using "ln -s <JRE_INSTALLATION_DIR>/bin/java /usr/bin/java") 
   or by adding JRE installation directory to the system path 
   ("export PATH=<JRE_INSTALLATION_DIR>/bin:$PATH") where <JRE_INSTALLATION_DIR> is the 
   path of the directory where JRE is installed.

   3. Operating systems supported are: RHEL5-32 bit, RHEL5-EM64T, SLES10-32 bit 
   and SLES10-EM64T.

   4. All the files in the folder should have executable permission.

   
C. CHANGES SINCE THE PREVIOUS RELEASE

	Beta-1 bug fixing.


D. Installation Procedure and how to use SEL Viewer utility

The SEL Viewer is meant to be used as an application on a Linux server. 

Now user can run SEL Viewer application either from the USB key or any external 
disk containing SEL Viewer release binaries. Also user can't save the SEL 
entries to a file if the SEL Viewer application is running from CD ROM or if 
the release folders have read-only attribute. User must check this before 
trying save operation.

The following is the procedure to execute the SEL Viewer utility in Linux 
environment:


   1. Command-line interface

      The SEL Viewer can be run either as a GUI based application or a 
command-line application. GUI provides all the functionality as the CLI 
provides, including clearing the SEL or saving SEL contents to a file.

	Selview [Options] [SEL File Name]  or ./cli [Options] [SEL File Name]

      a. To start the SEL Viewer GUI
				
		Selview

      b. To view the command-line help:

		Selview /h or ./cli /h

      c. To save the SEL entries to a file in text format:

		Selview /save log.sel or ./cli /save log.sel
		
      d. To save the SEL entries to a file in hex format:

		Selview /save /hex log.sel or ./cli /save /hex log.sel

****Note: End user needs to ensure that read-only attribute is disabled for 
SEL Viewer utility's release folders before running SEL Viewer utility 
application.

If still user couldn't able to save the SEL entries to a file, it is wise to do 
the following:
   1. Create a directory on your USB key or external hard disk,
   2. Copy SEL Viewer release files to the above created directory.
   3. Ensure that all the files are available in the folder. See 
   section E for reference.
   4. Run SEL Viewer application.
****

      e. To clear the SEL entries:

		Selview /clear or ./cli /clear

* In place of '/', user can use '-' also.


E. Required Files


The SEL Viewer utility SHOULD contain the following files and sub directories 
in the directory from which it is running.

	Selview
	cli (commad-line version of Selview)
	hrs.ini
	selenus.str
	ReleaseNotes.txt
	ui/gui.jar
	ui/appframework-1.0.3.jar
	ui/beansbinding-1.2.1.jar
	ui/swing-worker-1.1.jar
   

F. KNOWN ISSUES

	None

G. UNSUPPORTED FEATURES

   State persistence feature is not supported yet. This is usually implemented
using SEL.ini file.

H. INSTRUCTIONS TO END USER
*	Server needs to be updated with the appropriate latest FRUSDR package. 
SDR repository is essential in translating SEL entries to a Human Readable SEL 
description.

*	HRS.ini file (in the current directory where SEL Viewer application is 
running) shouldn't be modified. Any modifications to this file may cause the 
behavior of SEL Viewer utility un-predictable.

*	If SDR record is not found in the server’s SDR repository for the given
 SEL event's (Sensor Type, Generator ID and Sensor number) combination, then SEL 
Viewer utility displays sensor type along with sensor number in place of sensor 
name field in Human Readable SEL Description. If SDR record is found then SDR 
string available in SDR record is displayed as sensor name value.

*	If SDR record is not found for the given SEL event's (Generator ID, 
Sensor number and sensor type) combination then SEL Viewer displays sensor 
reading and threshold reading values as unspecified in Human Readable SEL 
description.

*	SDR look up for the given SEL event in SDR repository is based on SEL 
event's (sensor number, generator id and sensor type) combination. That means 
if SEL Viewer couldn't able to locate SDR record for the given SEL event's 
(sensor number, generator id and sensor type) combination, then SEL Viewer 
utility won't display Sensor Name/SDR String in GUI as part of decoded SEL 
string.

*	If SEL Viewer utility couldn't able to find the description string for 
the given SEL event (sensor type, offset, evd1, evd2 and evd3) combination, then
 SEL Viewer utility displays the event description for that event as 
"Unknown Event". If end user feels there should be a valid description for that 
combination, it should be informed to the developer/TME. Then appropriate string
 information is added as part of hrs.ini file.


*	HR_SEL.log file contains the information on Type 02 SEL events, which 
couldn't able to decode by SEL Viewer application. This file is created in the 
same folder where SEL Viewer application is running. DBGLOG.txt file will be 
created containing debug information.

*	In case of OEM events, Utility decodes events of type C0 and C1 only.

*	Third-party brands and names are the property of their respective owners.
