
OMEGAMON(R) XE for Mainframe Networks V4.1.0 Fix Pack 2 Interim Fix 3

4.1.0.2-TIV-ITM_KN3-IF0003.README

© Copyright IBM Corporation 2005, 2010.
  All Rights Reserved.

=========================================================================
CONTENTS
=========================================================================

1.0 About this Interim Fix
  1.1 Product fix history
  1.2 New or updated modules
  1.3 Backward compatibility with prior version of this product
  1.4 Cross-Product compatibility
  1.5 Known issues and limitations 
2.0 Installation and configuration
  2.1 Hardware and Software requirements
  2.2 Installation
  2.3 Installation using a response file (silent install):	
  2.4 Configuration
3.0 Uninstallation Information
4.0 Support Information
  4.1 Using IBM Support Assistant
  4.2 Obtaining Fixes
  4.3 Receiving weekly support updates
  4.4 Contacting IBM Software Support
5.0 Notices and Trademarks
  5.1 Notices
  5.2 Trademarks

=========================================================================
1.0 ABOUT THIS INTERIM FIX 
=========================================================================

Set the font to monospace to better view this file.

This maintenance update is Fix Pack 2 Interim Fix 3 for Tivoli OMEGAMON 
XE for Mainframe Networks V4.1.0 for use with ITM v6.1 Fixpack 7 or
greater.  It includes the APAR fix(es) listed below. 

A z/OS prereq (or coreq) PTF fix is also required.  
See Section 1.3 for details.



=========================================================================
1.1 Product fix history
=========================================================================

This maintenance update contains:
  OA28205 KCIIN0065W COULD NOT COPY CAT OR ATTR FOR KN3 AGENT

  Summary:

	1. KN3.BAROC and KN3.MAP each contain a copyright header that 
	contains a non-ASCII character. If the CandleSeed java code   
	(which is invoked by the itmcmd support command) is run in a  
	locale that does not use ISO 8859-1, then Java will recognize 
	this copyright symbol as an invalid character and throw an    
	exception.                                                    
	2. Interim Fix 4.1.0.2-TIV-ITM_KN3-IF0001 does not contain the
	information necessary to update the application support       
	version for the fix.
        3. The kn3_resources.jar file has been resigned with an updated
        certificate.

  Conclusion:
	1. KN3.BAROC, and KN3.MAP have been changed to prevent a Java 
	exception during the Candleseed operation.  In addition,      
	KN3.ATR, KN3.CAT and DOCKN3 are updated by this APAR.         
	2. This new Interim Fix will update the version of
	the application support for Mainframe Networks to the correct 
	value.
        3. This maintenance update includes a renewed Java certificate
        (Valid from: 6/15/10 8:00 PM until: 6/09/13 7:59 PM).  If you
        have previously installed a language pack image, you must install
        the corresponding language pack image with the matching
        certificate. 

        Refer to technote #1269613 to locate the current language pack
        image: http://www-1.ibm.com/support/docview.wss?uid=swg21269613

        Refer to the "Recommended Maintenance" technote #1290883 to
        locate the full list of IBM Tivoli OMEGAMON product maintenance
        deliverables which contain the renewed Java certificate:
        http://www-01.ibm.com/support/docview.wss?uid=swg21290883

	Note: The host changes for this fix are included in the
	following PTF: UA46881.  This Interim Fix must be installed
	along with PTF UA46881. See section 1.3 for further details.
                                                              

========================================================================
1.2 New or updated modules
========================================================================

Not all of these files will be present, depending on which components
are installed on a system. Files under the CMS directory will only be 
present if the Tivoli Enterprise Monitoring Server component is 
installed.


New Modules:
-----------

Windows directory structure:

________Module______________                 ____Date/Time____ ___Size__

None



UNIX and Linux directory structure:

________Module______________                 ____Date/Time____ ___Size__

None



Replaced Modules:
----------------

Windows directory structure:

Note:  <install_dir> defaults to C:\IBM\ITM
 
________Module______________                ____Date/Time____ ___Size__

<install_dir>\CMS\ATTRLIB\
kn3.atr                                       05/01/2009 02:03  316,611

<install_dir>\CMS\RKDSCATL\
kn3.cat                                       05/01/2009 02:03  370,948


<install_dir>\CMS\TECLIB\

kn3.baroc                                     05/01/2009 02:03   82,870
kn3.map                                       05/01/2009 02:03  209,564


<install_dir>\CNPS\

dockn3                                        05/01/2009 02:03  751,901


<install_dir>\CNPS\cmsatr\

kn3.atr                                       05/01/2009 02:03  316,611


<install_dir>\CNPS\RKDSCATL\

kn3.cat                                       05/01/2009 02:03  370,948


<install_dir>\CNB\classes\

kn3_resources.jar                             08/18/2010 08:46  134,303
kn3.inf                                       08/18/2010 15:25       27


<install_dir>\CNP\         

kn3_resources.jar                             08/18/2010 08:46  134,303
kn3.inf                                       08/18/2010 15:25       27


UNIX and Linux directory structure:

Note: <install_dir> defaults to /opt/IBM/ITM 
Where <ms_name> is the name of the monitoring server
      $hostname is the network node hostname and $platform is one
      of the following :

   li6243 or li6263 for Intel Linux
   ls3263 for zSeries Linux
   aix513 or aix533 for AIX.
   sol283 for Solaris



________Module______________                ____Date/Time____ ___Size___

<install_dir>/tables/cicatrsq/ATTRLIB/ 

kn3.atr                                       05/01/2009 02:03  316,611

<install_dir>/tables/cicatrsq/RKDSCATL/ 

kn3.cat                                       05/01/2009 02:03  370,948

<install_dir>/tables/<hostname>/ATTRLIB/

kn3.atr                                       05/01/2009 02:03  316,611


<install_dir>/tables/<hostname>/RKDSCATL/ 

kn3.cat                                       05/01/2009 02:03  370,948



<install_dir>/unix/n3/tables/ATTRLIB/

kn3.atr                                       05/01/2009 02:03  316,611


<install_dir>/$platform/cq/data/

dockn3                                        05/01/2009 02:03  751,901


<install_dir>/$platform/cq/tables/ATTRLIB/

kn3.atr                                       05/01/2009 02:03  316,611



<install_dir>/tables/<ms_name>/TECLIB/ 

kn3.baroc                                     05/01/2009 02:03   82,870
kn3.map                                       05/01/2009 02:03  209,564


<install_dir>/$platform/cw/classes/

kn3_resources.jar                             08/18/2010 08:46  134,303


<install_dir>/$platform/cw/

kn3.inf                                       08/18/2010 15:25       27


<install_dir>/$platform/cj/

kn3_resources.jar                             08/18/2010 08:46  134,303
kn3.inf                                       08/18/2010 15:25       27


Note that the date and time values listed above will be adjusted on your
system based on your local time zone settings. All of the above times 
are United States Eastern Standard Time (EST).


=========================================================================
1.3 Backward-Product compatibility
=========================================================================

This maintenance update requires installation of IBM Tivoli OMEGAMON XE
for Mainframe Networks V410 APAR OA28205. 

=========================================================================
1.4 Cross-Product compatibility
=========================================================================

- IBM Tivoli Monitoring Version 6.1.0 Fix Pack 7 (6.1.0-TIV-ITM-FP0007)
  or greater.

- Refer to technote #1290883  for a complete list 
  of recommended maintenance levels.
  http://www-1.ibm.com/support/docview.wss?uid=swg21290883

=========================================================================
1.5 Known issues and limitations
=========================================================================

The following are known issues with this maintenance update:

1. You may see fewer rows of data in the Tivoli Enterprise Console or in 
   Tivoli Netcool/OMNIbus for an event than you see in the Tivoli 
   Enterprise Portal situation alert. There is an internal buffer that 
   limits the amount of data that is sent/received between the Tivoli 
   Enterprise Monitoring Server and the event server.


=========================================================================
2.0 Installation and configuration
=========================================================================

=========================================================================
2.1 Hardware and Software Requirements
=========================================================================

This maintenance update requires:
- IBM Tivoli OMEGAMON XE for Mainframe Networks V410 APAR OA28205.

- IBM Tivoli Monitoring Version 6.1.0 Fix Pack 7 (6.1.0-TIV-ITM-FP0007)
  or greater.


=========================================================================
2.2 Installation steps:
=========================================================================

1. If any z/OS prereq (or coreq) PTF fixes are required, use SMP/E to 
   confirm that the PTFs have been installed before proceeding.

2. Confirm that IBM Tivoli Monitoring 6.1.0 Fixpack 7 (or greater) has 
   been installed by using the Help --> About function from the Tivoli 
   Enterprise Portal.

3. Ensure that Tivoli Enterprise Portal Server (TEPS) is running.

4. Backup the Tivoli Enterprise Portal Database. To do this:
   
   On Windows systems:

     Navigate to the CNPS subdirectory and enter this command:

       migrate-export

     This script generates a file named saveexport.sql in the 
     c:\ibm\itm\CNPS\sqllib subdirectory. It contains all the Tivoli 
     Enterprise Portal Server data.

     Note: Running the migrate-export process stops the Tivoli 
     Enterprise Portal Server if it is currently running.


   On UNIX or Linux systems:

     Navigate to /opt/IBM/ITM/bin and run the following command:

       ./itmcmd execute cq "runscript.sh migrate-export" 

     This script generates a file named saveexport.sql in the 
     /opt/IBM/ITM/$platform/cq/sqllib subdirectory. It contains all 
     the Tivoli Enterprise Portal Server data, where $platform is one 
     of the following:
   
       li6243 or li6263 for Intel Linux
       ls3263 for zSeries Linux 
       aix513 or aix533 for AIX
       sol283 for Solaris

5. Make a backup copy of all files listed above under the heading
  "Replaced Modules."

6. Copy the maintenance update zip or tar file to the Tivoli Enterprise 
   Monitoring Server(s) and Tivoli Enterprise Portal Server system(s).

7. Extract the maintenance update zip or tar file, using a command 
   such as:


   On Windows systems:
     unzip -v 4.1.0.2-TIV-ITM_KN3-IF0003.zip

   On UNIX or Linux systems: 
     - if the version of tar used supports z, then
       tar -zxvf 4.1.0.2-TIV-ITM_KN3-IF0003.tar.gz


     - if the version of tar used does not support z, then
       gunzip 4.1.0.2-TIV-ITM_KN3-IF0003.tar.gz
       tar -xvf 4.1.0.2-TIV-ITM_KN3-IF0003.tar

   This action should create a directory structure that contains the
   fix patches and this readme file.

8. Start the Application Support Installer GUI to install the Fixpack. 
   The GUI can be started by using the following command from within 
   the Fixpack directory
    
     java -jar setup.jar	

   Note that you need to have a JVM in your path.  When prompted by the 
   Application Support Installer for the patch directory, select the 
   maintenance update directory, NOT the component directory, as in these
   examples:


   On Windows systems: c:\temp\4.1.0.2-TIV-ITM_KN3-IF0003

   On UNIX or Linux systems: /temp/4.1.0.2-TIV-ITM_KN3-IF0003


   The installer can install updates for multiple components at the same 
   time, which is why you need to select the parent directory.

NOTE: Steps 9-11 apply to UNIX and Linux ONLY. The commands in these steps 
   must be executed from the bin subdirectory of the IBM Tivoli 
   Monitoring V6.1.0 installation:


9. Stop the portal server by running the following command:

     ./itmcmd agent stop cq 


10. Run the following command to configure the portal server with the 
    new agent information:

      ./itmcmd config -A cq 

    Complete the configuration as prompted. For information about
    configuring the portal server, refer to the latest version of IBM 
    Tivoli Monitoring: Install and Setup Guide, found at this Web 
    address:

    http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp?
    toc=/com.ibm.omegamon.mn.doc/toc.xml


11. Restart the portal server by running the following command:

      ./itmcmd agent start cq 


NOTE: Step 12 applies to Windows, UNIX, and Linux systems.

12. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal
    Browser were running when the update was installed, the Tivoli 
    Enterprise Portal Desktop or Tivoli Enterprise Portal Browser must
    be restarted.

=========================================================================
2.3 Installation using a response file (silent install):
=========================================================================

You can install the application support files on the IBM Tivoli 
Monitoring components through the silent install method using a response 
file. 

Note: If your UNIX or Linux computer does not have X-Windows, you must 
use the silent installation method. 

1. Perform Steps 1 through 7 as described under "Installation steps."

2. In the same directory with the extracted files, create a text file 
   named response.txt that contains the following lines: 

# IBM Tivoli Monitoring installation directory
-W Directories.itmhome="/opt/IBM/ITM"

# Directory where the application support media is located
-W Directories.mediaLocation=""

# Select "true" to install monitoring server support files
-W ComponentSelectionPanel.temsSelected="true"

# Select "true" to install portal server support files
-W ComponentSelectionPanel.tepsSelected="true"


# Select "true" to install portal desktop client support files
# IMPORTANT: set this to true if you have the portal desktop 
# client installed.
-W ComponentSelectionPanel.tepdSelected="false"


# Comma-separated list of directories with the application media
# location to install.These are directories that contain the
# product support files and are sub-directories under the specified
# media location.
# e.g. -W ProductSelectionPanel.products="kn3_v410,km5_v410"
-W ProductSelectionPanel.products=""

# Set this flag to "true" if you want to re-install if the
# specified product is already installed. This overwrites
# any previously installed support files for this product.
-W ProductSelectionPanel.reinstall="true"

# Setting this flag to "true" confirms that you have purchased
# an OMEGAMON DE license. If any product requires a DE LICENSE
# and this flag is "false" installation will fail
-W ProductSelectionPanel.deLicense="false" 

3. Launch the installation program by running the following command 
   from within the install CD-ROM directory: 

     java -jar setup.jar -silent -options response.txt 

   Note that you need to either have the IBM Java JRE v1.4.2 in 
   your path or invoke the JRE executable directly by specifying 
   the path to it on the command line. To invoke the JRE executable 
   directly, issue the following command: 

     Java_installDir\java -jar setup.jar -silent -options response.txt 

   Where Java_installDir is the location where the JRE (provided 
   by IBM Tivoli Monitoring) is installed on your monitoring server. 

   To locate the JRE that is being used by IBM Tivoli Monitoring 
   on UNIX or Linux, run the following command: 

     find ITM_installDir -name java 

   Where ITM_installDir is the location where IBM Tivoli Monitoring is 
   installed on your monitoring server.

   To ensure that the level of JRE is 1.4.2, run the following command 
   from the directory where the JRE is installed: 

     ./java -version 

   If the JRE level is not 1.4.2, you must download the IBM Java JRE 
   v1.4.2 from the IBM Software Support Web site. 


4. Validate the silent install by examining the installation log file:

   On Windows systems: A location defined by the TEMP environment variable

   On UNIX and Linux systems: /tmp/ ITM_AppSupport_SilentInstall.log


5. Perform Steps 9 through 12 as described under "Installation steps."

6. See section 2.2.1 for updating Eclipse Help if you are using IBM
   Tivoli Monitoring Version 6.2.

=========================================================================
2.4 Configuration
=========================================================================

If you are using IBM Tivoli Enterprise Console (TEC) or IBM Tivoli 
Netcool/OMNIbus, in addition to IBM Tivoli Monitoring, to manage events 
in your enterprise, you can now forward events reported by OMEGAMON XE 
for Mainframe Networks monitoring agents to these event management 
products. The benefits of these products and the details of how they can 
be integrated with IBM Tivoli Monitoring are described in the 
'Integrating event management systems' section of IBM Tivoli Monitoring: 
Installation and Setup Guide. Before events can be forwarded, event 
forwarding must be enabled on the hub monitoring server, and a default 
destination server must be defined.

In addition, the TEC or Netcool/OMNIbus server (the event server) must 
be configured to receive the events, a situation update forwarding 
process must be installed on the event server, and, for events forwarded 
to TEC a baroc file for the agent must be installed and imported on the 
event server. The IBM Tivoli Monitoring: Installation and Setup Guide 
provides detailed instructions for enabling event forwarding from a 
distributed Tivoli Enterprise Monitoring Server and for configuring TEC 
and OMNIbus to receive the events, including the installation of the 
event synchronization component and installing the .baroc files. IBM 
Tivoli Monitoring: Configuring IBM Tivoli Enterprise Monitoring Server 
on z/OS provides instructions for configuring a hub monitoring server 
on z/OS and locating the agent baroc files. 

After situation forwarding is enabled, by default all situation events 
are forwarded to the specified event server. However, you can customize 
which situation events are forwarded and to which event server, using the 
Situation editor in the Tivoli Enterprise Portal. You may also need to 
assign an event status compatible with the target event server. For 
information on specifying which situation events to forward, see the 
Tivoli Enterprise Portal online help and the IBM Tivoli Monitoring: User 
Guide.

=========================================================================
3.0 Uninstallation information
=========================================================================

1. Stop the Tivoli Enterprise Portal Server.

2. Restore your Tivoli Enterprise Portal database. To do this:
  
   On Windows systems:

   Navigate to the CNPS subdirectory and enter this command:

     migrate-import

   Note: Running the migrate-export process stops the Tivoli 
   Enterprise Portal Server if it is currently running.


   On UNIX or Linux systems:

   Navigate to /opt/IBM/ITM/bin and run the following command:

     ./itmcmd execute cq "runscript.sh migrate-export" 

   This script generates a file named saveexport.sql in the 
   /opt/IBM/ITM/$platform/cq/sqllib subdirectory. It contains all the 
   Tivoli Enterprise Portal Server data, where $platform is one of 
   the following:
   
     li6243 or li6263 for Intel Linux
     ls3263 for zSeries Linux 
     aix513 or aix533 for AIX 
     sol283 for Solaris

3. Copy the backed up files from Step 5 of the installation steps to 
   the corresponding directories under your \IBM\ITM (Windows) or 
   /opt/IBM/ITM/ (UNIX or Linux) directory.

4. Rebuild the presentation files by issuing the following commands: 

   On Windows systems:

   Navigate to the CNPS subdirectory and enter this command:

     InstallPresentation

   On UNIX or Linux systems:

   a. Navigate to /opt/IBM/ITM/bin and run the following command to 
      stop the portal server:

        ./itmcmd agent stop cq 

   b. Run the following command to configure the portal server with 
      the new agent information:

        ./itmcmd config -A cq 

      Complete the configuration as prompted. For information about
      configuring the portal server, refer to the latest version of 
      IBM Tivoli Monitoring: Install and Setup Guide, found at this 
      Web address:

      http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/
      index.jsp?toc=/com.ibm.omegamon.mn.doc/toc.xml

   c. Restart the portal server by running the following command:

        ./itmcmd agent start cq 

=========================================================================
4.0 SUPPORT INFORMATION
=========================================================================

If you have a problem with your IBM software, you want to resolve it
quickly. This section describes options for obtaining support for IBM
software products.

=========================================================================
4.1 Using IBM Support Assistant
=========================================================================

The IBM Support Assistant is a free, stand-alone application that you can
install on any workstation. You can then enhance the application by
installing product-specific plug-in modules for the IBM products you use.

The IBM Support Assistant saves you time searching product, support, and
educational resources. The IBM Support Assistant helps you gather support
information when you need to open a problem management record (PMR), 
which you can then use to track the problem.

The product-specific plug-in modules provide you with the following
resources:
- Support links
- Education links
- Ability to submit problem management reports

For more information, see the IBM Support Assistant Web site at: 
 
            http://www.ibm.com/software/support/isa

If your product does not use IBM Support Assistant, use the links to
support topics in your information center. In the navigation frame, check
the links for resources listed in the ibm.com and related resource
section where you can search the following resources:
- Support and assistance (includes search capability of IBM technotes
  and IBM downloads for interim fixes and workarounds)
- Training and certification
- IBM developerWorks
- IBM Redbooks
- General product information

If you cannot find the solution to your problem in the information
center, search the following internet resources for the latest
information that might help you resolve your problem:
- Forums and newsgroups
- Search engines

=========================================================================
4.2 Obtaining Fixes
=========================================================================

A product fix might be available to resolve your problem. To determine
what fixes are available for your IBM software product, follow these
steps:
- Go to the IBM Software Support Web site at
  http://www.ibm.com/software/support
- Under Find product support, click "All IBM Software (A-Z). This opens
  the software product list.
- In the software product list,
  click "IBM Tivoli OMEGAMON XE for Mainframe Networks". This opens the
  "IBM Tivoli OMEGAMON XE for Mainframe Networks" support site.
- Click the name of a fix to read the description and optionally download
  the fix. You can also search for a specific fix; for tips on refining
  your search, click "Search tips".
- In the "Find downloads and drivers by product" section, select one
  software category from the "Category" list.
- Select one product from the "Sub-category" list.
- Type more search terms in the "Search within results" if you want to
  refine your search.
- Click "Search".
- From the list of downloads returned by your search, click the name of
  a fix to read the description of the fix and to optionally download
  the fix.

For more information about the types of fixes that are available, see the
IBM Software Support Handbook at

  http://techsupport.services.ibm.com/guides/handbook.htm

=========================================================================
4.3 Receiving weekly support updates
=========================================================================

To receive weekly e-mail notifications about fixes and other software
support news, follow these steps: 

- Go to the IBM Software Support Web site at

    http://www.ibm.com/software/support. 

- Click "My support" in the upper right corner of the page. 
- If you have already registered for "My support", sign in and skip to
  the next step. If you have not registered, click "register now".
  Complete the registration form using your e-mail address as your
  IBM ID and click "Submit". 
- Click "Edit profile". 
- In the "Products" list, select "Software". A second list is displayed. 
- In the second list, select a product segment, for example,
  "Systems Management". A third list is displayed. 
- In the third list, select a product sub-segment, for example,
  "System Performance". A list of applicable products is displayed. 
- Select the products for which you want to receive updates, for example,
  IBM Tivoli OMEGAMON XE for Mainframe Networks. 
- Click Add products. 
- After selecting all products that are of interest to you, click
  Subscribe to email on the Edit profile tab. 
- Select Please send these documents by weekly email. 
- Update your e-mail address as needed. 
- In the Documents list, select Software. 
- Select the types of documents that you want to receive information
  about. 
- Click Update.

If you experience problems with the My support feature, you can obtain
help in one of the following ways: 

Online:
Send an e-mail message to erchelp@ca.ibm.com, describing your problem. 

By phone:
Call 1-800-IBM-4You (1-800-426-4968). 

=========================================================================
4.4 Contacting IBM Software Support
=========================================================================

IBM Software Support provides assistance with product defects.

Before contacting IBM Software Support, your company must have an active
IBM software maintenance contract, and you must be authorized to submit
problems to IBM. The type of software maintenance contract that you need
depends on the type of product you have: 

- For IBM distributed software products (including, but not limited to
  Tivoli, Lotus, and Rational products, as well as DB2 and WebSphere
  products that run on Windows, or UNIX operating systems),
  enroll in Passport Advantage in one of the following ways: 

  Online 
     Go to the Passport Advantage Web site at

     http://www.lotus.com/services/passport.nsf/
            WebDocs/Passport_Advantage_Home

     and click "How to Enroll".
 
  By phone 
     For the phone number to call in your country, go to the
     IBM Software Support Web site at

     http://techsupport.services.ibm.com/guides/contacts.html

     and click the name of your geographic region.
 
- For customers with Subscription and Support (S & S) contracts, go to
  the Software Service Request Web site at

  https://techsupport.services.ibm.com/ssr/login.
 
- For customers with IBMLink, CATIA, Linux, S/390, iSeries,
  pSeries, zSeries, and other support agreements, go to the IBM
  Support Line Web site at

  http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.
 
- For IBM eServer software products (including, but not limited to,
  DB2 and WebSphere products that run in zSeries, pSeries, and iSeries
  environments), you can purchase a software maintenance agreement by
  working directly with an IBM sales representative or an IBM Business
  Partner. For more information about support for eServer software
  products, go to the IBM Technical Support Advantage Web site at

  http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need,
call 1-800-IBMSERV (1-800-426-7378) in the United States. From other
countries, go to the contacts page of the IBM Software Support Handbook
on the Web at

  http://techsupport.services.ibm.com/guides/contacts.html

and click the name of your geographic region for phone numbers of people
who provide support for your location.

To contact IBM Software support, follow these steps:

- Determining the business impact

  When you report a problem to IBM, you are asked to supply a severity
  level. Therefore, you need to understand and assess the business
  impact of the problem that you are reporting. Use the following
  criteria: 

  Severity 1 
      The problem has a critical business impact. You are unable to use
      the program, resulting in a critical impact on operations. This
      condition requires an immediate solution. 

  Severity 2 
      The problem has a significant business impact. The program is
      usable, but it is severely limited. 

  Severity 3 
      The problem has some business impact. The program is usable, but
      less significant features (not critical to operations) are
      unavailable. 

  Severity 4 
      The problem has minimal business impact. The problem causes little
      impact on operations, or a reasonable circumvention to the problem
      was implemented. 
 
- Describing problems and gathering information

  When describing a problem to IBM, be as specific as possible. Include
  all relevant background information so that IBM Software Support
  specialists can help you solve the problem efficiently. To save time,
  know the answers to these questions: 

  - What software versions were you running when the problem occurred? 
  - Do you have logs, traces, and messages that are related to the
    problem symptoms? IBM Software Support is likely to ask for this
    information. 
  - Can you re-create the problem? If so, what steps were performed to
    re-create the problem? 
  - Did you make any changes to the system? For example, did you make
    changes to the hardware, operating system, networking software, and
    so on. 
  - Are you currently using a workaround for the problem? If so, be
    prepared to explain the workaround when you report the problem.
 
- Submitting problems

  You can submit your problem to IBM Software Support in one of two ways:

  Online 
      Click Submit and track problems on the IBM Software Support site
      at

        http://www.ibm.com/software/support/probsub.html.

      Type your information into the appropriate problem submission form.
  
  By phone 
      For the phone number to call in your country, go to the contacts
      page of the IBM Software Support Handbook at

        http://techsupport.services.ibm.com/guides/contacts.html

      and click the name of your geographic region.
 
  If the problem you submit is for a software defect or for missing or
  inaccurate documentation, IBM Software Support creates an
  Authorized Program Analysis Report (APAR). The APAR describes the
  problem in detail. Whenever possible, IBM Software Support provides a
  workaround that you can implement until the APAR is resolved and a fix
  is delivered. IBM publishes resolved APARs on the Software Support
  Web site daily, so that other users who experience the same problem
  can benefit from the same resolution.

=========================================================================
5.0 NOTICES AND TRADEMARKS
=========================================================================

-----------------------
5.1 Notices:
-----------------------

This information was developed for products and services offered in the
U.S.A. IBM may not offer the products, services, or features discussed in
this document in other countries. Consult your local IBM representative
for information on the products and services currently available in your
area. Any reference to an IBM product, program, or service is not
intended to state or imply that only that IBM product, program, or
service may be used. Any =functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be
used instead. However, it is the user’s responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document does
not give you any license to these patents. You can send license
inquiries, in writing, to:

    IBM Director of Licensing 
    IBM Corporation
    North Castle Drive
    Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact
the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:

    IBM World Trade Asia Corporation
    Licensing
    2-31 Roppongi 3-chome, Minato-ku
    Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in 
certain transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own
risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
 
Licensees of this program who wish to have information about it for the 
purpose of enabling: (i) the exchange of information between
independently created programs and other programs (including this one)
and (ii) the mutual use of the information which has been exchanged,
should contact:

    IBM Corporation
    2Z4A/101
    11400 Burnet Road
    Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and
conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material 
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Program License Agreement or any equivalent
agreement between us.

Any performance data contained herein was determined in a controlled 
environment. Therefore, the results obtained in other operating
environments may vary significantly. Some measurements may have been made
on development-level systems and there is no guarantee that these
measurements will be the same on generally available systems.
Furthermore, some measurement may have been estimated through
extrapolation. Actual results may vary. Users of this document should
verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers
of those products, their published announcements or other publicly
available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to
non-IBM products. Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to
change or withdrawal without notice, and represent goals and objectives
only.

This information may contain examples of data and reports used in daily 
business operations. To illustrate them as completely as possible, the
examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the
names and addresses used by an actual business enterprise is entirely
coincidental.

COPYRIGHT LICENSE:

This information may contain sample application programs in source
language, which illustrate programming techniques on various operating
platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using,
marketing or distributing application programs conforming to the
application programming interface for the operating platform for which
the sample programs are written. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or imply
reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment
to IBM for the purposes of developing, using, marketing, or distributing
application programs conforming to IBMs application programming
interfaces.

-----------------------
5.2 Trademarks:
-----------------------

IBM, CICS, OMEGAMON, Tivoli, Tivoli Enterprise, z/OS, zSeries, pSeries,
AIX, IBMLink, S/390, ibm.com, IBM developerWorks, Passport Advantage,
Rational, Lotus, eServer, and IBM Redbooks are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both.

Intel and Pentium  are trademarks of Intel Corporation in the United
States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other
countries, or both.

Microsoft(R) and Windows are registered trademarks of Microsoft
Corporation in the United States, other countries, or both.

Solaris(TM), Java(TM) and all Java-based trademarks and logos are 
trademarks or registered trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.

UNIX(R)is a registered trademark of The Open Group in the United States
and other countries.

Other company, product, and service names may be trademarks or service
marks of others.

=========================================================================