IBM Tivoli Business Service Manager V4.2.1 Interim Fix 4(4.2.1.3-TIV-BSM-IF0004)

Download Description

Title:
------

IBM® Tivoli® Business Service Manager Interim Fix Version
4.2.1.3-TIV-BSM-IF0004

**************************************************************
* A change introduced by this Interim Fix might negatively
* affect existing product function.
* The problem description is as follows:
* Non-leaf services created via autopopulation rules, for templates
* without EDSA rules, are deleted.
* APAR is IV36399.
*
* 4.2.1.3-TIV-BSM-IF0006 should be installed immediately after this
* Interim Fix to avoid any problems.
*
*************************************************************

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

Date:
-----
August 02, 2012

====================================================================
Copyright Notice:
-----------------

© Copyright IBM Corp. 2011 All Rights Reserved.

US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.

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

Contents:
---------

* Files that are included in this Interim Fix:

- This README file (4.2.1.3-TIV-BSM-IF0004.README)
- 4.2.1.3-TIV-BSM-IF0004-linux.tar
- 4.2.1.3-TIV-BSM-IF0004-solaris.tar
- 4.2.1.3-TIV-BSM-IF0004-zlinux.tar
- 4.2.1.3-TIV-BSM-IF0004-aix.tar
- 4.2.1.3-TIV-BSM-IF0004-windows.zip

For TBSM ITM Agent:

- r9v421c8-120719.aix.tar
- r9v421c8-120719.sun.tar
- r9v421c8-120719.ilinux.tar
- r9v421c8-120719.zlinux.tar
- R9C421C8-120719.Windows.zip


The following files have been replaced by this Interim Fix.

Replaced files on the Data Server:
ncsagent.jar
RAD_agentService.props
av.jar
setTraceLevel.jy
CreateDBPoller.jsp
ncs.jar
ncsi.jar
scriptedAPIStartup.bsh
TimeSeriesViewIFRAME.jsp
itmdataclient.jar
LaunchTBSM.nova
maintcli.jar
RAD_Consistency.props


If you have made changes to the above mentioned files you will
find your copy of the file under:

- The copy of the files can be found in the following
directory:
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/data/sla.war


Replaced files on the Dashboard Server:

CreateDBPoller.jsp
ncs.jar
ncsi.jar
av.jar
setTraceLevel.jy
TimeSeriesViewIFRAME.jsp
itmdataclient.jar


If you have made changes to the above mentioned files you will
find your copy of the file under:
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/dash/sla.war


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

About this Interim Fix:
------------------------------------

This Interim Fix addresses problems reported in IBM Tivoli
Business Service Manager 4.2.1.3


* Pre-Requisite

Please ensure ITM is upgraded to a minimum of 6.2.2 FP6 prior to installing this interim fix.


* APARS that are included new in Interim Fix 4.

IV22664 DYNAMICAWARESERVICEINSTANCEBEAN.JAVA THE CHILD IS NOT REMOVED
When an ESDA parent is removed from the SQL source, the ESDA children services are not deleted. Instead they are moved to the root of the tree. And it's not possible to remove them by validation or re-triggering any esda rules. They can only be manually removed/or when their lifetime expires/or when the data server is restarted (if non-persistent).

IV23345 QUERY BUILDER FAILS WITH CTGBA0049E WHEN DB2 QUERY CONTAlNS MIXED CASE
DB2 query fails when the column and or tablenames are mixed case, the query fails unless they are put in double quotes.

For this APAR please do the following:

1) Back up and edit the $TIP_HOME/profiles/TBSMProfile/installedApps/TBSMCell/tbsm.ear/sla.war/etc/rad/RAD_<datasourceName>.ds file i.e RAD_cvtwin14db.ds.
2) Add the following at the end of the .ds file:
For the Sybase DSA's:
<datasourceName>.Sybase.NUMDSPROPERTIES=1
<datasourceName>.Sybase.DSPROPERTY.1.NAME=REPEAT_READ
<datasourceName>.Sybase.DSPROPERTY.1.VALUE=true
Replace <datasourceName> with the actual name.
3) Restart the TBSM server.

IV23498 STACK OVERFLOW/THREAD HANG/OOM.
If the Client UpdateHandler Publisher thread is stopped then the updates (status changes and config changes) backup on the data server as they cannot be published to the Dashboard. This usually happens if the Agent is running and there are circular references in the model, then this situation can occur.

A New property is required for RAD_agentservice.props

# Maximum number of parents which the agent will traverse when retrieving the path for a service.
# The path is sent for Service Status Events.
# The default value is 50.
# Uncomment the value below to set a different value for this parameter.
# impact.agentservice.maxlevelsdeep=50

Please restart the server after making this change.


IV24088 TBSM DATA SERVER AND AGENT DO NOT RECONNECT ON RESTART OF AGENT:
If the TBSM Agent is stopped when the TBSM Custom Provider Code (Agent portion within TBSM) tries to connect, the connection will fail on the CP port (typicaly 2092). In this case, TBSM will not continue to try and connect to the Agent.

IV21843 ATTRIBUTE VALUE FROM DATAFETCHER IS NOT CLEARED
The Data fetcher is not updating results because of an invalid state change.

IV16156 DATA DISPLAY ISSUE WITH DOJO 1.4
When creating a new data fetcher the Query Data window does not populate. This is due to a change in the ITM code

IV12419 CUSTOM BIRT REPORT ISSUE ON CHARTING PORTLET: DOC
The documentation for creating and connecting a BIRT based chart to TBSM is outdated and is missing some vital information. There is currently no information on setting up the environment for the BIRT charts, no information of creating a basic birt chart, and there is no information on connecting a parameter based birtchart to TBSM.

IV12942 CONSISTENCY CHECKER CORRECTION NOT PASSED TO DASHBOARD
If the consistency checker detects that the service affecting events shown in the GUI are not consistent with the those in theobjectserver it corrects this but does not update the dashboard server and the GUI does not change.

IV10214 DATA SERVER TO HANDLE INVALID CLIENT REQUEST BETTER.
Search instance window is not functioning as required.

IV15692 TBSM REGISTERS INTERIM STATES AT RESTART FOR SERVICE IN MAINT.
On Server restart, Rows are sent to the Agent for events received during Server Down - for Services which are in Maintenance. This is incorrect. Customers are not expecting to see status events for Services in Maintenance

IV09219 JAVA.LANG.NULLPOINTEREXCEPTION WHEN PROCESSING EVENTS.
The stateModelNode is being returned as null - i.e. it does not exists in the map in the GlobalInstanceStore. To fix this we must check when the state model is null and attempt to create it if necessary.

IV08771 EXCLUDE FILTER ON CUSTOM VIEW FAILS TO FILTER
When the user created a child and parent service of the same name and tried filtering out the child it would not work. Child still appeared.

IV13276 TWA MENU ACTION SHOW->COMPARE SERVICE METRICS THROWS OOM
When showing TimeWindowAnalyzer page, user got OutOfMemory error on client. The issue intermittently happens only on IE6/8.

IV10312 CUSTOM CANVAS UNWANTED RESIZING ON SOME SHAPE INDICATOR
In a custom canvas a single click (or a mouse pointer passing over dots right next to the indicator image) to a circle or triangle indicator, can cause unwanted resizing to happen. (the shape grows, gets larger).

IV14463 DURING FAILOVER, WHEN LOADING TIP CHARTS THROWS EXCEPTION
During failover, dashboard system has to connect to the secondary Data server in the cluster and if there is an exception when doing that other than not being able to connect to the primary data server, it starts a never ending loop until either we can connect with the primary data server in our cluster or we can connect to the TIP Charts.

IV15036 BEFORE TBSM AGENT SENDS ASCII CHARACTERS
When characters such as à are written to the KR9 table, it takes more than one byte to store the character.But the Parent column in the table is only 127 bytes. If by chance, the 127 cutoff happens to be between the first and second byte of Ã, then the Warehouse Proxy produces an error and falls over

IV08556 NULLPOINTEREXCEPTION ERROR WHEN STARTING SERVICE AVAILABILITY
When starting Service Availability window, the following error appears: TIPMSG1000E An error occurred while processing the request to the server. Detail: NullPointerException. The NullPointerException happens because right after the hotlistportlet is opened it it trying to get an update but the hotlist isn't created.

IV14966 ITM POLICY DATA FETCHERS- LOOP CODE FOR POPULATING DESCRIPTION
A bug existed whereby the query description variable was not being cleared after each call.

IV08828 INCORRECT SERVICE STATE BASED ON EVENT
Service states are lingering (marginal or critical) without any events associated. We have an incoming status rule (ISR) defined and consistency checker turned on and running at the default interval (every 5 minutes). There are 2 issues here: A. ISR is not clearing the state of the instance when a clear comes in. This is where consistency checker is expected to run and clear the state of these instances, but it does not which leads to the problem listed in B. Consistency checker should be clearing the service states if there are no matching events.

IV10039 TBSM DATA SERVER PROCESS SHUTDOWN ITSELF IF GETTING EXCEPTION
TBSM data server process shutdown itself if getting exception when checking db status through "rad_db status".

IV09266 LAUNCH TBSM' TOOL SHIPPED WITH TBSM DOES NOT WORK FOR SLAM
When trying to launch from a TBSM generated Service Event into TBSM using the 'Launch TBSM' tool shipped with TBSM, nothing happens.

IV08012 RAD_ADD_MAINT - DATE PARAMETERS MONTH VALUE NOT INTERPRETED
The command rad_add_maint has 2 parameters that expect a date inthe format YYYYMMDDHHMM, however the month value MM does not translate to a 'real' month number e.g. 05 = May as stated in the docs, it translates to the java month number 00=January to 11=December.

IV07914 TBSM CONSISTENCY CHECKER CONSUMES MUCH OF OS CONNECTION TIME
When ConsistencyChecker is enabled, ObjectServer *prof* logs shows RAD_Impact user taking up over 45 secs consistently. - Consistency checker was doing a lot of activity.

IV08563 DATA SERVER STOPS LOADING POLICIES IF A .IPL FILE IS MISSING
When the data server starts it goes through the process of loading all the policies in the RAD_policylist. If it encountersa missing .ipl file, it seems to stop loading the remaining policies. If the user then tries to edit one of the 'not loaded' policies it appears to be empty (just the default commented outcontent) and throws an error.

IV03927 UNABLE TO CREATE NEW TEMPLATES. TREE TEMPLATE EDITOR IS SLOW
Opening the tree template editor takes 10 - 15 minutes to display

IV03630 SETTRACELEVEL DOES NOT PERSIST NUMBER OF LOG FILES
When customers change the max number of log files and size of log files using the CLI $TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setTraceOutputToFile 30 40 These options do not persist when calling: $TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setstartup When the server is restarted, the setttings go back to what is defined in server.xml

IV07234 RADSHELL EXPORT ISSUE USING ACCENTED CHARACTERS IN ESDA SQL
If ESDA rules, contain SQL with french characters - these characters are not exported to radshell.

IV26446 SECONDARY DATA SERVER GOES DOWN WHILE SYNCHING.
Secondary server goes down a few hours after it has started. This occurs every time after the server has been restarted.


====================================================================
This TBSM Interim Fix includes the latest TIP fix.

PM58383 PORTLET IS BEING DISPLAYED -VERY NARROW.

When a user creates a new page with the Service details across the bottom and the Service Viewer taking up
most of the remaining space (in the middle), with a Service tree on the left and 3 Charting portlets on the right the 3 Charting portlets expand to use just over half the page, leaving a little skinny Service Viewer in the centre.


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

Installation, migration, upgrade and configuration information:
---------------------------------------------------------------

* Hardware and software requirements:

Refer to the TBSM 4.2.1 Release Notes for a full description
of all the hardware and software requirements.

You will need 1019 MB of disk space in order to install this
Interim Fix. Please check the amount of space you have before you
install, as the installation will fail if you run out of
space.

* Dependencies:

This Interim Fix must be installed on each server(s) that is running
the TBSM data server and TBSM dashboard server.

This Interim Fix requires TBSM 4.2.1 FP3 to be installed.


* Special considerations:

1) A copy of the sla.war files will be made and placed in:
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/data/sla.war
and
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/dash/sla.war

2) All TBSM and TIP processes or services must be stopped prior
to the update install.

On Linux/Unix: perform the following

1. To stop the TBSM Data server issue the following command:
$TIP_HOME/profiles/TBSMProfile/bin/stopServer.sh server1 -username <adminuser> -password <adminpassword>

2. To stop the TBSM Dashboard server, issue the following command:
$TIP_HOME/profiles/TIPProfile/bin/stopServer.sh server1 -username <tipadminuser> -password <adminpassword>
By default, username is tipadmin and password
is the tipadmin password.

On Windows:

1. In the Start menu, click Settings -> Control Panel
-> Administrative Tools -> Services.
The Services window opens. Depending on what services
you have installed, the available services are as follows:

Tivoli Business Service Manager - TBSMProfile_Port_17310.
This is the Data server.
Tivoli Integrated Portal - TIPProfile_Port_16310.
This is the Dashboard server.


2. Right-click the service that you want to stop and click Stop.


3) The installer will backup the script files to the following
location. These files are being backed up because the TIP
fix in this Interim Fix will replace some of
these files.

[InstallDirectory]/tip/systemApps/isclite.ear/isclite.war/
secure/isclite/scripts_BACKUPIF4

4) All non-vital programs should be closed prior to installation of
the Interim Fix. Other processes accessing the [InstallDirectory],
tip directory or it's sub-directories may cause conflicts with the
Interim Fix installation. A reboot may be necessary to ensure no rogue
processes are accessing the install directory.


* Extracting this Interim Fix:
Non-Windows

1. Copy the file 4.2.1.3-TIV-BSM-IF0004-<os>.tar to a
temporary location on your TBSM Server.
2. Untar the file on each server that you need to install on.
tar -xvf 4.2.1.3-TIV-BSM-IF0004-<os>.tar


Windows
1.Copy the file 4.2.1.3-TIV-BSM-IF0004-windows.zip to a
temporary location on your TBSM server.
2. Unzip the file on each server that you need to install on.

After untarring/unzipping the file you will have 1 directory:
TBSM --TBSM data server and dashboard server updates, TIP updates



* Installing this Interim Fix:

[Interim Fix] Refers to the directory where this Interim Fix
resides (after you have extracted it from the zip/tar file).

On the Tivoli Business Service Manager server system:

Navigate to the [Interim Fix] directory where the files
were extracted.

Install the Interim Fix with the same user that was used to
install TBSM 4.2.1 GA.
Note: the Interim Fix cannot be installed as "root".

All TBSM Servers
===================================================
1.)Navigate to the TBSM directory.
2.)To install Interim Fix 4,
If you are on a Windows operating system, for console mode run the following
command from a prompt:

setup-windows.exe -i console

If you are on a Unix operating system, run the following
command from a prompt:

setup-<unixplatform>.bin -i console

NOTE: There is no GUI mode for this Interim Fix. It
can only be installed in console mode or silent install.

For console mode:
For example ./setup-linux.bin -i console
or setup-windows.exe -i console


To install from silent mode:


a. Copy setupIF.rsp from the TBSM directory of the extracted
IF file to a location it can be edited (/tmp).
b. Update the file to match your environment by following
the comments in the file text.
c. Run:

UNIX :install.sh -f /tmp/setupIF.rsp

or

Windows: setup-windows.exe -f C:\tmp\setupIF.rsp

Note: The response file needs to have a fully qualified
path.



To Install in a failover environment

If you are installing the Interim Fix in an environment with a failover
pair of TBSM data servers, you must install using the failover steps
described in the upgrade chapter of the TBSM Installation Guide.

https://www.ibm.com/developerworks/wikis/display/tivolidoccentral/
Tivoli+Business+Service+Manager



3.)During the install you will be asked to to verify
path names to the TIP install.

4.)Notes and Post-Install Considerations:

a)For the latest TIP fixes to take effect,
after this Interim Fix has been installed, clear the browser
cache on the machine where you run your BROWSER. This
will allow the browser to pick up changes to the javascript
files.

For example, in Firefox, select Tools --> Clear Private Data,
and select "Cache".
In Internet Explorer, select Tools --> Delete Browsing History,
and click "Delete" for "Temporary Internet Files".



b) After installation is complete, you may remove
[Interim Fix] to save space.


5.)Restart all servers.



* Uninstalling the Interim Fix:

Before uninstalling the Interim Fix all TBSM processes should be
STOPPED. The interim fix will NOT stop any TBSM process for the user.
The user must manually stop the TBSM processes, before the install
of the Interim Fix and before the uninstall of the Interim Fix.

On the Tivoli Business Service Manager server system:

1.Navigate to the TBSM directory
<installDir>/_uninst/TBSM_IF4

Uninstall the Interim Fix with the same user that was used
to install TBSM 4.2.1 GA.


2. If you are on a Unix operating system, run the following
command from a prompt.

./uninstall -i console


If you are on a Windows operating system, run the following
command from a prompt:

uninstall.exe -i console

3.Upon uninstalling, check if the following maintenance folder exists:

[InstallDirectory]/tip/logs/tbsm/maintenance

If it does exist, check the TBSMUninstall-00.log file for <warningCount>
(found normally towards the bottom of the log).If the warningCount
is not 0,and if the error message has 'ACUASI0196E Encountered
problem trying to delete file', replace the sla.war directory on
the system with the backup sla.war found under:

On the Data Server:
the sla.war directory can be found under:
[InstallDirectory]/
tip/profiles/TBSMProfile/installedApps/TBSMCell/tbsm.ear

the backup sla.war can be found under:
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/data

On the Dashboard Server:
the sla.war directory can be found under:
[InstallDirectory]/
tip/systemApps/isclite.ear

the backup sla.war can be found under:
[InstallDirectory]/
tip/logs/tbsm/maintenance/backup/4.2.1.3/IF0004/dash

The TBSMUninstall-00.log file can be found in the user's home
directory.

4.Delete the maintenance folder as follows before reinstalling
[InstallDirectory]/tip/logs/tbsm/maintenance

5.Restart the Data Server and Dashboard Server

6. On Unix operating systems, uninstalling the Interim Fix may remove
execute permissions from the versioninfo file, in the <INSTALL DIR>/tbsm/bin
directory. To determine if this is the case, change to the
directory and use ls -l versioninfo* command, as below:

cd <INSTALL DIR>/tbsm/bin
ls -l versioninfo*

The permissions should show execute (x) for the file,
for all groups.

-rwxr-xr-x 1 <user> <user group> 1374 Oct 18 2010 versioninfo


If required, use chmod 755 to update the permission for required the file.
i.e. chmod 755 versioninfo



* Installing the TBSM agent:
The following packages are available for download in the
Interim Fix 4.

r9v421c8-120719.aix.tar
- r9v421c8-120719.sun.tar
- r9v421c8-120719.ilinux.tar
- r9v421c8-120719.zlinux.tar
- R9C421C8-120719.Windows.zip


1)Download the appropriate agent code for your platform.
2)Untar or unzip the file.
3)Install the agent according to the directions in the TBSM
Installation Guide. This is a complete install package
for the TBSM agent support and can be used for a fresh
install of the agent.


====================================================================
Documentation Changes

IV12419: CUSTOM BIRT REPORT ISSUE ON CHARTING PORTLET

1.1 JDBC Drivers

In order to run a BIRT based report the following JDBC drivers must be installed
http://pic.dhe.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=%2Fcom.ibm.tivoli.itbsm.doc_4.2.1.3%
2Finstallguide%2Fbsmi_t_procedure_for_customizing_postgres.html

1.2 Creating a Birt Chart

For further information on how to create a chart in BIRT please refer to
www.birt-exchange.org


1.3 Setting up the TBSM Data source in the BIRT Designer Tool

To set up a data source the following steps are required:

- Download the JDBC driver to the BIRT Designer Tool machine -This can be found at: <TIP_HOME>/systemApps/isclite.ear/sla.war/WEBINF/lib/postgresql-8.1dev-400.jdbc3.jar

- In the Data Explorer tab, right click on Data Sources and select New Data Source. In the New Data Source dialog, choose JDBC Data Source and enter “TBSM Postgres” as Data Source Name.

- In the New JDBC Data Source Profile panel, click on the Manage Drivers.. button. Click on Add..

- In the file selection dialog that appears, navigate to and select postgresql-8.1dev-400.jdbc3.jar and click OK.

- Now, back on the New JDBC Data Source Profile dialog, select org.postgresql.Driver (v8.1) from the Driver Class dropdown

- For database url, enter jdbc:postgresql://<Postgres_Host>:<Postgres_Port>/<Postgres_ DB_NAME>

- For username, enter the postgres username

- For password, enter the postgres password

- Leave JDNI URL blank

- Click on Test Connection. If all of the above is correct and TBSM is running on the data server, it should say Test Successful.

- Click on Finish


1.4 Parameters


In the BIRT Data Explorer, right-click Report Parameters and click New Parameter.
In the name field, type ServiceInstanceName. Do not complete the remaining fields. Click OK.
To ensure that data is passed from TBSM to BIRT:
In the Data Explorer tab, right-click Data Sets and click New Data Set.
Select the TBSM Postgres dataset.
In the Data Set Name field, type ServiceInstanceName.
Click Next.
Edit the SQL to include the following:

where displayname < ?
order by displayname

where < ? is the parameter that is passed from TBSM to BIRT.
Click Finish.
In the Data Explorer tab, expand the Data Sets node, right-click your data set and click Edit.
Click Parameters and then click New.
Select ServiceInstanceName from the Linked to report parameter list. Accept the default values for the remaining fields and click OK.
Click OK to exit the Edit Parameter dialog box and then click OK.




IV08635 NEED TO IMPROVE DOCUMENTATON FOR SETTRACELEVEL.SH

More information is supplied on each parameter used in SetTraceLevel.sh on page titled: Using the setTraceLevel CLI

Using the setTraceLevel CLI
About this task
There is a TBSM CLI for setting trace levels.

Start this tool by invoking the following command:

* For UNIX®: $TBSM_HOME/bin/setTraceLevel.sh <WAS Admin userid> <WAS Admin password> < dashboard |data > [options]
* For Windows®: %TBSM_HOME%\bin\setTraceLevel.bat <WAS Admin userid> <WAS Admin password> <dashboard | data > [options]

Both of these commands call a Jython script called setTraceLevel.jy to invoke eWAS admin functions.
The online help consists of the following options:

-usage
This displays the various options available and their usage.
-display
Shows the current runtime trace settings.
e.g.
com.ibm.tbsm.*=fine
com.ibm.tivoli.twa.marker.*=fine
com.micromuse.*=fine

-resetall
Sets all runtime tracing to the default installation level
-none
Disables runtime trace for all TBSM components
-fine
Enables FINE runtime trace for all TBSM components
-finer
Enables FINER runtime trace for all TBSM components
-finest
Enables FINEST runtime trace for all TBSM components
-showstartup
Shows the current startup trace settings
-setstartup
Sets the startup trace settings using the current runtime trace settings. This output is similar to "-display" if the tracing is set on startup.

-addtrace
Adds the following trace specifications to the runtime trace settings.
For example:
-addtrace "com.micromuse.common.chartcomponent.*=finest:com.ibm.debug=fine"

NOTE: ".*" should be added ONLY if a child component is available. Otherwise remove the ".*" e.g.
-addtrace "com.micromuse.sla.beans=finest:com.ibm.debug=finest"

-settrace
Replaces the runtime trace specifications with the following trace settings.
For example:
-settrace "com.micromuse.common.chartcomponent.*=finest:com.ibm.debug=fine"

NOTE: ".*" should be added ONLY if a child component is available. Otherwise remove the ".*" e.g.
-settrace "com.micromuse.sla.beans=finest:com.ibm.debug=finest"

-rmtrace
Removes the following trace settings from the runtime trace specification.
For example:
-rmtrace "com.micromuse.common.chartcomponent.*=finest:com.ibm.debug=fine"

NOTE: ".*" should be added ONLY if a child component is available. Otherwise remove the ".*" e.g.
-rmtrace "com.micromuse.sla.beans=finest:com.ibm.debug=finest"

-getRingBufferSize
Prints ring buffer size in units of 1000 entries.
-setRingBufferSize
Resets ring buffer size in units of 1000 entries.
For example:

-setRingBufferSize 20

-clearRingBuffer
Deletes current contents of ring buffer.
-dumpRingBuffer
Copies contents of ring buffer to a file.
For example:

-dumpRingBuffer /tmp/ringBuffer.out

-setTraceOutputToRingBuffer
Sends trace output to in-memory ring buffer. The trace type must be "basic", "advanced" or "loganalyzer".
Two parameters are needed here -
MB Size and Type.
For example:
-setTraceOutputToRingBuffer 20 basic

-setTraceOutputToFile
Sends trace output to trace.log. Three parameters are needed here; MB size, Number of Files and Trace type. The trace type must be "basic", "advanced" or "loganalyzer".
For example:

-setTraceOutputToFile 20 20 basic


-getTraceFileName
Prints current trace file name.
-getTraceRuntimeConfig
Prints current trace configuration parameters.

Example
For example, the following sequence of setTraceLevel CLIs sets the startup tracing level to FINE for all TBSM Loggers:

setTraceLevel.sh tipadmin tippassword data -fine
setTraceLevel.sh tipadmin tippassword data -setstartup
setTraceLevel.sh tipadmin tippassword dashboard -fine
setTraceLevel.sh tipadmin tippassword dashboard -setstartup




IV07914: TBSM CONSISTENCY CHECKER CONSUMES MUCH OF OS CONNECTION TIME: 421:DOC

In TBSM Administrator's Guide -> Reference -> Important configuration files -> RAD_consistency.props files, add new property in table as below :

Property name : impact.consistency.maxforbatch
Description : Specifies max number for batch query, used when checking events existence when service dependency information is subject to repairs by consistency checking.
Default : 100



====================================================================
Additional Information



====================================================================
Troubleshooting/Known Issues


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

Notices and trademarks:
-----------------------

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 IBM's application programming interfaces.


Trademarks:

The following terms are trademarks of International Business
Machines Corporation in the United States, other countries, or
both: IBM, IBM logo, Tivoli, Tivoli logo, AIX®, AOC/MVS™, APPN,
CICS®, CICSPlex®, CICS/ESA®, DB2®, DB2 Universal Database™,
DFSMShsm™, Domino®, DB2 Universal Database, IMS™, IMS/ESA®,
Informix®, MQSeries®, MVS, MVS/ESA™, NetView®, NWays, OS/390®,
RACF®, RMF™, SNA/APPN, SecureWay®, Tivoli Enterprise™, Tivoli
Enterprise Console®, Tivoli Management Environment, TME 10™,
VTAM®, WebSphere®, z/OS®.

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

Microsoft®, Windows, Windows NT®, and the Windows logo are
trademarks of Microsoft Corporation in the United States, other
countries, or both.

Java™ and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United
States and other countries.

Pentium® is a registered trademark of Intel® in the United States
and other countries. Other company, product, or service names may
be trademarks or service marks of others.

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