t l business systems manager -...

Tivoli® Business Systems Manager

Release Notes (Revised January 2005)

Version 3.1

GI11-4029-00

��

Note

Before using this information and the product it supports, read the information in “Notices” on page 49.

Third edition (January 2005)

This edition applies to Version 3, Release 1 of IBM Tivoli Business Systems Manager and to all subsequent releases

and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2000, 2005. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

Chapter 1. About this release . . . . . 1

New in this release . . . . . . . . . . . . 2

Provide knowledge to business executives . . . 2

Improve productivity of the operator . . . . . 2

Continue support of IT investments for the

systems operations manager . . . . . . . . 4

Improve serviceability, reliability and performance 6

Improve time to value and tighter integration for

the system administrator and operator . . . . . 7

Documentation notes . . . . . . . . . . . 9

Documentation changes . . . . . . . . . 9

Documentation updates . . . . . . . . . 10

Updates to the Installation and Configuration

Guide . . . . . . . . . . . . . . 10

Changes to the “Installation CDs” section 10

Changes to the “Event Enablement

Specifications” section . . . . . . . . 10

Updates to the Administrator’s Guide . . . . 11

Addition to the “Percentage Based

Thresholds” section . . . . . . . . . 11

Changes to the “Creating the Automated

Business Systems Configuration File”

section . . . . . . . . . . . . . 11

Changes to the “Creating Default and

Override Preferences” section . . . . . 12

Interim Fix Updates . . . . . . . . 13

Updates to the Task Assistant . . . . . . 18

Product fix history . . . . . . . . . . . . 18

Backward compatibility . . . . . . . . . . 18

Product compatibility . . . . . . . . . . . 19

Chapter 2. Installation, upgrade, and

configuration information . . . . . . . 21

Hardware and software requirements . . . . . . 21

Installation and configuration notes . . . . . . 21

Installing base services . . . . . . . . . 21

Installing the console . . . . . . . . . . 22

Installing National Language Support . . . . 22

Upgrade notes . . . . . . . . . . . . . 22

Uninstallation information . . . . . . . . . 23

Chapter 3. Known limitations,

problems, and workarounds . . . . . 25

Limitations . . . . . . . . . . . . . . 25

Tivoli Business Systems Manager console . . . 25

Web console . . . . . . . . . . . . . 25

Executive dashboard . . . . . . . . . . 25

Console server . . . . . . . . . . . . 25

User Registries . . . . . . . . . . . . 25

Automated Business Systems . . . . . . . 26

Monitoring SNA/APPN resources . . . . . . 26

Intelligent Monitor for Tivoli NetView . . . . 26

Problems and workarounds . . . . . . . . . 26

Tivoli Business Systems Manager console . . . 26

Web console . . . . . . . . . . . . . 27

Executive dashboard . . . . . . . . . . 28

Console server . . . . . . . . . . . . 28

Health monitor service . . . . . . . . . 29

Problem request processor . . . . . . . . 29

XML toolkit . . . . . . . . . . . . . 29

Agent listener . . . . . . . . . . . . 29

Data maintenance jobs . . . . . . . . . . 29

Common listener adapter for Tivoli Workload

Scheduler . . . . . . . . . . . . . . 30

Event processing . . . . . . . . . . . 30

Ownership . . . . . . . . . . . . . 30

Task server . . . . . . . . . . . . . 30

RODM . . . . . . . . . . . . . . . 30

Crystal Enterprise Server Reports . . . . . . 30

Historical reports . . . . . . . . . . . 31

Operational reports . . . . . . . . . . . 31

Internationalization issues . . . . . . . . 31

Limitation using the console in Hebrew and

Arabic . . . . . . . . . . . . . . 31

Limitation using the executive dashboard in

Hebrew and Arabic . . . . . . . . . . 32

Limitation using the task assistant in Hebrew

and Arabic . . . . . . . . . . . . 32

Console locale limitation . . . . . . . . 32

Running the console in different locales . . . 32

Running the console in a non-English

language . . . . . . . . . . . . . 33

Running the console using Israel Daylight

Time . . . . . . . . . . . . . . . 33

Time zone display in console preferences . . 33

Using the Web console in traditional Chinese 33

Kanji translation of messages and help

windows . . . . . . . . . . . . . 33

Accessibility problems . . . . . . . . . . 33

Appendix. APARs corrected in version

3.1 . . . . . . . . . . . . . . . . 35

Support information . . . . . . . . . 45

Searching knowledge bases . . . . . . . . . 45

Search the information center on your local

system or network . . . . . . . . . . . 45

Search the Internet . . . . . . . . . . . 45

Obtaining fixes . . . . . . . . . . . . . 45

Contacting IBM Software Support . . . . . . . 46

Determine the business impact of your problem 47

Describe your problem and gather background

information . . . . . . . . . . . . . 47

Submit your problem to IBM Software Support 47

Notices . . . . . . . . . . . . . . 49

Trademarks . . . . . . . . . . . . . . 50

© Copyright IBM Corp. 2000, 2005 iii

iv IBM Tivoli Business Systems Manager: Release Notes (Revised January 2005)

Chapter 1. About this release

The IBM Tivoli® Business Systems Manager Release Notes provides important

information about the Tivoli Business Systems Manager product. These Release

Notes are the most current information for the Tivoli Business Systems Manager

product and take precedence over all other documentation. Review these Release

Notes thoroughly before installing or using this product.

Note: The IBM Tivoli Business Systems Manager Release Notes might be updated

from time to time. You can find the most current version of these Release

Notes at the following Web site:

http://www.ibm.com/software/tivoli/library/

Release Notes change history

This table details the changes that have been made to the IBM Tivoli Business

Systems Manager Release Notes.

Table 1. Release Notes change history

Date Change made

December 2004 Tivoli Business Systems Manager Interim Fix 3.1.0.0-TIV-BSM-IF0003 introduces Event Enablement support for Linux. See

“Changes to the “Event Enablement Specifications” section” on

page 10 for details about supported platforms.

December 2004 An MKS Toolkit hot fix is available to solve a Health Monitor

server memory leak. See“Health monitor service” on page 29 for

details on this hot fix.

January 2005 The IBM Tivoli Business Systems Manager Translated Documentation

CD is available. See “Changes to the “Installation CDs” section”

on page 10 for details about this CD.

January 2005 In “Documentation changes” on page 9, the name and description

of the Tivoli Business Systems Manager, Version 3.1, Guide for

Warehouse Pack, Version 3.2.0.0, using Tivoli Data Warehouse, Version

1.2 publication was updated.

January 2005 The section “Interim Fix Updates” on page 13 was added as a

result of changes introduced by Interim Fix

3.1.0.0–TIV–BSM–IF0004.

January 2005 The following information was added to the Problems and

workarounds section:

v “Crystal Enterprise Server Reports” on page 30

v “Historical reports” on page 31

v “Operational reports” on page 31

January 2005 A section on Percentage Based Thresholds best practices was

added. See “Addition to the “Percentage Based Thresholds”

section” on page 11 for information on best practices.

© Copyright IBM Corp. 2000, 2005 1

http://www.ibm.com/software/tivoli/library/

New in this release

This section includes the following information:

v “Provide knowledge to business executives”

v “Improve productivity of the operator”

v “Continue support of IT investments for the systems operations manager” on

page 4

v “Improve serviceability, reliability and performance” on page 6

v “Improve time to value and tighter integration for the system administrator and

operator” on page 7

v “Documentation notes” on page 9

Provide knowledge to business executives

v A new executive dashboard view gives business unit executives a high-level view

of the availability of the services and business systems that they own. Refer to

the IBM Tivoli Business Systems Manager Introducing the Consoles and IBM Tivoli

Business Systems Manager Administrator’s Guide for more information.

v Tivoli Business Systems Manager is closely integrated with Tivoli Service Level

Advisor. Tivoli Service Level Advisor events and violations are forwarded to the

agent listener through Tivoli Enterprise Console® and displayed in the executive

dashboard. Services created within Tivoli Business Systems Manager can be

referenced by Service Level Agreements within Tivoli Service Level Advisor.

Refer to the IBM Tivoli Business Systems Manager Installation and Configuration

Guide and the IBM Tivoli Business Systems Manager Administrator’s Guide for more

information.

v The executive dashboard application programming interface provides an

interface to the Tivoli Business Systems Manager database. You can use this

application programming interface to integrate Tivoli Business Systems Manager

executive dashboard data into your own Web applications. Refer to the IBM

Tivoli Business Systems Manager Administrator’s Guide for more information on the

executive dashboard application programming interface.

Improve productivity of the operator

v The Web console has been redesigned and is hosted by the WebSphere®

Application Server. You can view business systems, events, resources, critical

resources, and resource properties. Most of these views are refreshed

automatically. It provides advanced filtering for events, resources, and business

systems and there is an enhanced search facility. You can also create problem

tickets and Ownership, Problem, and Information notes. Refer to the IBM Tivoli

Business Systems Manager Administrator’s Guide and IBM Tivoli Business Systems

Manager Introducing the Consoles for more information on the Web console.

v You can use the same user ID and password for the console, the Web console,

the reporting system, and the executive dashboard.

v There is a new concept called Business System Shortcuts. Previously, when copies

of resources were made in the business system tree, the console displayed the

original resource because the properties of the original resource and its copies

could not be changed independently. You can configure the copy differently

from the original resource. The copy is called a shortcut. There is a visual

indicator on the shortcut icon and you can change shortcut settings, or you can

restore its properties to those of the original. Some operations are only allowed

with non-shortcuts. Refer to the IBM Tivoli Business Systems Manager

2 IBM Tivoli Business Systems Manager: Release Notes (Revised January 2005)

Administrator’s Guide and the information in the Task Assistant for more

information about business system shortcuts.

v In the console, the Business System Topology view displays business system

resources instead of physical resources. In addition, when there are business

system shortcuts, the shortcuts are displayed instead of the source business

systems. Any existing links or connections created between physical resources or

source business systems are displayed in the view. Refer to IBM Tivoli Business

Systems Manager Introducing the Consoles for a more complete description of the

Business System Topology view.

v Improvements have been made to notes, including a new consolidated notes

view, a full notes history, a properties notebook, the ability to add remarks to a

note, and the ability to clear alerts from resources when taking ownership. Refer

to the IBM Tivoli Business Systems Manager Administrator’s Guide for more

information.

v There is a new Search menu on the console. The old Find menu under the Edit

menu is relocated to the Search menu. The Search All Resources submenu

enables you to find resources with known names or of known resource types

without navigating to them manually. Refer to the Task Assistant and the IBM

Tivoli Business Systems Manager Introducing the Consoles for information.

v When you open or save a workspace in the console, Tivoli Business Systems

Manager remembers which tree branches were expanded and which were

collapsed the last time you saved your workspace.

v There is an additional column in the physical tree to identify the ancestors of

objects and events.

v You can view either the full name or the user name of an operator.

v The following enhancements were made to the reporting system:

– Authentication uses local operating system groups or LDAP repository

through the WebSphere Application Server.

– Web application supports multi-level logging.

– Business System Availability and Shift Turnover reports have been added to

the report set.

– Landscape printing is supported.

– GIF images are synchronized with the console.

– Improved Excel exporting.

– Improved National Language Support.

Refer to the IBM Tivoli Business Systems Manager Administrator’s Guide and IBM

Tivoli Business Systems Manager Introducing the Consoles for more information on

the reporting system.

v There is a new Tivoli Business Systems Manager Topology view for DB2® and

IMS™ resources. It helps operators isolate DB2 and IMS problems by graphically

showing DB2 relationships, IMS relationships and the following relationships:

– Relationships between resources on different operating systems in the same

Sysplex.

– Relationships between IRLM regions in the same IRLM group, CQS regions in

same CQS group, and all regions within the same IMSPlex.

– Relationships between parent resources and child resources.

– Relationships to other feed resources. For example, a DB2 Topology view for

a DB2 subsystem shows related IMS subsystems and CICS® regions.

Refer to IBM Tivoli Business Systems Manager Introducing the Consoles for more

information on the Topology view for DB2 and IMS resources.

Chapter 1. About this release 3

v Using resource level propagation, you can set exception and child event

thresholds for individual resources. It allows different thresholds for resources in

the physical tree and for each copy of the resource in a business system. You can

configure resource level propagation using the console, a command line interface

command, the XML toolkit, or Automated Business Systems. Refer to the IBM

Tivoli Business Systems Manager Administrator’s Guide for more information.

v Percentage Based Thresholds (PBT) is a new propagation concept. It enables a

business system folder or business system shortcut to have its state derived from

the collective state of the resources it contains. You can configure Percentage

Based Thresholds using the console, command line interface, XML, or

Automated Business Systems. Refer to the IBM Tivoli Business Systems Manager

Administrator’s Guide and IBM Tivoli Business Systems Manager Command Reference

for more information.

v The Task Assistant can be launched in a separate browser. Refer to IBM Tivoli

Business Systems Manager Introducing the Consoles for information.

v Hebrew and Arabic translations are added to the languages supported by Tivoli

Business Systems Manager. Refer to the National Language Support chapter in

the IBM Tivoli Business Systems Manager Installation and Configuration Guide for

more information.

Continue support of IT investments for the systems

operations manager

v Changes to the IMS data source include the following enhancements:

– New resources for IMSPlex and IMS V8.1 support

– IMS Operations Manager (OM), Resource Manager (RM), Structured Call

Interface (SCI), and Java™ Dependant regions (new in IMS V8.1) are

monitored by Tivoli Business Systems Manager. Java Dependant regions

appear as MPP or BMP regions.

– IMS Connect regions running on different operating systems to connected

IMS regions have connections represented on Tivoli Business Systems

Manager console views.

– IRLM, CQS and IMS Connect are children of the operating system resource

instead of an IMS systems resource and remain under the various IMS

systems. This is useful when creating these objects in the business systems

views.

– New commands in the console for the display of DD names and Dataset

names for Databases, DEDB Areas, IMS Partitions, and IMS Logs.

– IMS DEDB MADS are supported.

– The monitoring of IMS RECON messages is enhanced.

– The performance of rediscovery and poll monitors is enhanced.

– IMS events for nonexistent objects automatically create the object with a

parent of *UNKNOWN* if the event does not contain the intermediate parent

information. Previously, these were ignored.

– Exclusion processing is enhanced.

– The initial discovery procedure has been simplified and enhanced. Initial

discovery runs on the target z/OS® image, and automatically detects IMS

systems, related regions, and IMS resources. The discovery jobs used in

previous releases are no longer supported.

– You can defer programs, transactions, and databases (including areas and

partitions).


– Transaction polling processing is enhanced to detect any transactions queued

because no IMS Message Processing Region of the correct class is running.

– IMS ESAF and IMS WADS are automatically discovered.

– Console administrator commands have been added for enhanced control of

Tivoli Business Systems Manager for IMS operation. An administrator can

request a rediscovery of an IMS system, all IMS systems matching a named

pattern, or all active IMS systems currently running on a z/OS system.

– Tivoli Business Systems Manager v3.1 discovers and monitors IMS V9

systems the same as previous releases of IMS systems. However, it does not

support IMS V9 new messages or new functions.

Refer to the IBM Tivoli Business Systems Manager Administrator’s Guide for more

information on IMS.

v Changes to the DB2 data source include the following enhancements:

– DB2 V8 support

– DB2 PE support

– Usability enhancements which include consolidated DB2 Tablespace and

Index partition resources.

– Batch discovery uses the same code as online rediscovery.

– There is a new interface that accepts a specific subsystem name, or a generic

pattern of subsystem names, to generate one or more rediscovery requests.

– Performance of rediscovery and poll monitors is enhanced.

– DB2 events for nonexistent resources automatically create the resource with a

parent of UNKNOWN if the event does not contain the intermediate parent

information. Previously, these were ignored.

– Exclusion performance is enhanced.

– The initial discovery procedure has been simplified and enhanced. Initial

discovery runs on the target z/OS image, and automatically detects DB2

subsystems, related address spaces, and DB2 resources. The discovery jobs

used in previous releases are no longer supported.

– You can defer low-level resource rediscoveries.


information on DB2.

v Changes to the System Automation for z/OS data source include the following

enhancements:

– Tivoli Business Systems Manager supports System Automation for OS/390

V2.1 and 2.2 and SA/390 CPSM.

– There are Tivoli Business Systems Manager Monitoring Level Profiles and

automation indicators in the console.

– In the console, right-click a resource to run System Automation for z/OS

commands.


information on System Automation for z/OS.

v Changes to the Tivoli Enterprise Console data source include the following

enhancements:

– If event enablement is not working, you can cache events forwarded by the

Tivoli Enterprise Console application to a file.

– You can organize distributed resources based on any resource attribute.


– You can modify Tivoli Enterprise Console event attribute values before

forwarding them to Tivoli Business Systems Manager so you do not have to

call a script from the Tivoli Enterprise Console application.

– Generic events can provide a value for Tivoli Business Systems Manager to

map to a resource class.


information on the Tivoli Enterprise Console.

v The following enhancements have been made to the Tivoli Data Warehouse:

– You can export business system folders (including business systems shortcuts

and their state), services, relationships between service resources, and

business system resources.

– There are two additional states. The Maintenance Window state is Unmanaged

in the Tivoli Data Warehouse and resources with an open Ownership note

have a state of Repaired.

Refer to IBM Tivoli Business Systems Manager Guide for Warehouse Pack, Version

3.1.0.0, using Tivoli Data Warehouse, Version 1.2 for more information on the Tivoli

Data Warehouse.

v Hewlett-Packard Openview Network Node Manager for Solaris and

Hewlett-Packard Openview Network Node Manager for HP/UX integrate

directly into Tivoli Business Systems Manager through the common listener and

support bulk and delta discovery of network resources such as routers, switches,

subnets, and segments. Hewlett-Packard network resources are mapped to the

equivalent Tivoli Business Systems Manager resources which are based on

NetView®-defined resources. Refer to the IBM Tivoli Business Systems Manager

Administrator’s Guide for more information.

v Problem and Change Management integration offers more configuration options

and more input information on the events that create problem tickets and

change requests. The Auto Ticketing process is improved by eliminating some

processing overhead and a new batch mode is available. Refer to the IBM Tivoli

Business Systems Manager Problem and Change Management Integration Guide for

more details.

v For a complete list of supported data sources, refer to IBM Tivoli Business Systems

Manager Installation and Configuration Guide.

Improve serviceability, reliability and performance

v The console server runs on WebSphere Application Server Version 5.0.2, which is

provided with Tivoli Business Systems Manager v3.1 and is installed at the same

time. Refer to IBM Tivoli Business Systems Manager Installation and Configuration

Guide for more information.

v WebSphere Application Server allows for encrypted sessions between consoles

and the console server using Secured Socket Layer (SSL). Refer to the IBM Tivoli


v The WebSphere Application Server provides two security options for

authorization and authentication: LocalOS and LDAP. Refer to the IBM Tivoli

Business Systems Manager Administrator’s Guide and IBM Tivoli Business Systems

Manager Installation and Configuration Guide for more information.

v There is no longer a propagation server. Propagation is run through the staged

event loader. This improves Tivoli Business Systems Manager performance. Refer

to IBM Tivoli Business Systems Manager Installation and Configuration Guide for

more information.


v Preferences are stored in the database. This enables administrators to set

site-wide preferences that override operator preferences. Refer to the IBM Tivoli


v Agent listener performance is improved. It processes Tivoli Enterprise Console

events in groups instead of one at a time.

v Automated Business Systems performance has improved. Business systems are

created using the common listener and there are improved Automated Business

Systems triggers. You can configure Resource Level Propagation, Percentage

Based Thresholds, and alert state change notification to the Tivoli Enterprise

Console application using Automated Business Systems. Refer to the IBM Tivoli

Business Systems Manager Administrator’s Guide for more information on

Automated Business Systems.

v The following components are monitored by the health monitor:

– WebSphere Application Server on the console server

– Common Listener service

– Agent Listener service

– Enabled Microsoft® SQL jobs

– Primary and secondary database log shipping

– Multiple event handlers

Refer to the IBM Tivoli Business Systems Manager Administrator’s Guide for

information on the health monitor.

v Many usability enhancements have been made to the Failover process. Refer to

the IBM Tivoli Business Systems Manager Administrator’s Guide for information.

v Problem ticket and change requests process in the background. Use the Task

Monitor to check the problem status. You can also change the preferences to

allow foreground processing. Refer to the Task Assistant and the IBM Tivoli

Business Systems Manager Problem and Change Management Integration Guide for

information.

v The Cancel Query console menu item cancels a refresh or query operation. This

is useful if an update is inadvertently requested, it is taking too long to load, or

if you decide to reset the filter criteria and do not want to wait for the refresh

function to complete. Refer to the Task Assistant for more information.

v You can specify your current Performance Monitor profiles. You are no longer

required to create a Performance Monitor profile specifically for Tivoli Business

Systems Manager. Refer to the IBM Tivoli Business Systems Manager

Administrator’s Guide and IBM Tivoli Business Systems Manager Installation and

Configuration Guide for information.

v You can develop request processors that run the automatic ticket integration

function in either the non-batch or batch mode. For more information, refer to

IBM Tivoli Business Systems Manager Problem and Change Management Integration

Guide.

Improve time to value and tighter integration for the system

administrator and operator

v You can send Tivoli Enterprise Console events when there is a state change in

any business system or resource. The events are sent to the Tivoli Enterprise

Console application using the Tivoli Event Integration Facility (EIF). You can

configure this using the console, a command line interface command, XML, or

Automated Business Systems. Refer to the IBM Tivoli Business Systems Manager

Administrator’s Guide for more information.

v Using the new XML toolkit, you can do the following tasks:

– Send XML files to Tivoli Business Systems Manager


– Query the status of an XML transaction

– Create business systems automatically

– Configure business systems, including Resource Level Propagation thresholds,

Percentage Based threshold rules and linking, Tivoli Enterprise Console event

notification of business system alert state changes, defining business system

folders as services, and associating services with executive dashboard users.

– Populate business systems with existing resources

– Backup and restore business systems


information on how to use the XML Toolkit. Refer to IBM Tivoli Business Systems

Manager Installation and Configuration Guide for information on installation.

v The following changes have been made to the z/OS discovery process:

– CICS: CICS resources can be discovered without CICSPlex® SM (CPSM)

installed. Resources include regions, files, transactions, CORBA servers, DJAR

files, and DB2 connections. Discovery is performed using a batch job which

uses a generic EXCI interface to detect resources online, or extracts the

resources from the appropriate CICS CSD.

– IMS: You can no longer send tapes to IBM® and have IBM perform initial

discovery for you. Instead, you can run a NetView batch job. You can set this

batch job to be an automated batch job so it can run off-hours. Initial

discovery finds some additional IMS address spaces such as CQS and IRLM

which were not previously discovered using Tivoli Business Systems Manager

v2.1.1 Batch NetView.

– DB2: You can discover new resources within DB2, DB2 V8 support. You can

also configure automatic rediscovery.v Changes to distributed feeds include the following enhancements:

– Physical placement rules - These rules give you more control of the placement

of resource in the physical hierarchy. The earlier table-based approach only

allowed placement based on the TCP/IP hostname. The physical placement

rules allow different slot and attribute values to be used to identify the

various levels of the physical hierarchy.

– Time To Value Items and samples - Sample scripts and Tivoli Enterprise

Console rules that can be used to map resources to the following Tivoli

Business Systems Manager resource classes:

- Hub

- Novell Server

- Router

- Server

- Switch

- UNIX® Server

- Windows® Server

Rules are provided for events from the following applications:

- Tivoli Distributed Monitoring

- IBM Tivoli Monitoring (not including PAC events)

- NetView

- HP OpenView

These rules and scripts provide a base which can be built on by further

customizing the scripts to fit your environment.

– Optional Version and Manufacturer for distributed classes - Distributed

classes no longer must specify a version. Classes can be created with only the

product name.


– Add Profiles and Heartbeat behavior for Generic class - Generic distributed

classes (ihstttec) support heartbeat function and profiling. Profiling allows

mapping between the DM and ITM profiles and a distributed class, similiar to

the function that previously existed in the ihstztec DM command. The

heartbeat function allows for the acceptance of heartbeats for generic

resources and the generation of events if a heartbeat is not received within a

specified timeframe.

– TCP Hostname Manipulation - The TCP hostname can be further manipulated

prior to sending the value to Tivoli Business Systems Manager. The name can

be truncated using the beginning or end of the name, shortening the name to

reflect only relevant information. The display name can be built dynamically

using the operating system type as well as the shortened or full length

TCP/IP hostname. The display name can optionally have @tcphostname

appended to it. In earlier versions of Tivoli Business Systems Manager, this

was always appended.

– Optional DNS / OS Type Lookup - Setting that optionally uses DNS to look

up the fully qualified TCP/IP hostname. This optional setting can either

disable DNS lookup completely, or it can allow one lookup on a resource,

after which further lookups are not performed on that resource.

– Event Caching - Events from Tivoli Enterprise Console are cached when the

event enablement daemon is not running, reducing the chance of lost events

if the daemon is recycled.

– Substitutions on ihstttec flags - Symbolic variables can be used to dynamically

build the display name, class name, and instance id names. These variables

include the following:

- OS type

- fully qualified TCP/IP hostname

- manipulated TCP/IP hostname.– Customizable display names - The display name can be built dynamically

through the use of symbolic variables using the operating system type as well

as the shortened or full length TCP/IP hostname. The display name can

optionally have @tcphostname appended to it. In earlier versions of Tivoli

Business Systems Manager, this was always appended.

Refer to the IBM Tivoli Business Systems Manager Administrator’s Guide and IBM

Tivoli Business Systems Manager Installation and Configuration Guide for

information on distributed feeds.

Documentation notes

This section describes changes made to the Tivoli Business Systems Manager v3.1

library, and it provides information that was identified after the documentation

was finished.

Documentation changes

This section provides information about documentation changes for the Tivoli

Business Systems Manager v3.1 library.

v The new Tivoli Business Systems Manager Information Center is located on the

Tivoli Business Systems Manager support page at

http://publib.boulder.ibm.com/infocenter/tiv3help/index.jsp?toc=/com.ibm.tivoli.itbsm.doc/toc.xml

v To open the Information Center on the Tivoli Business Systems Manager

Documentation CD, double-click the infocenter.html file.




v The new IBM Tivoli Business Systems Manager Planning Guide provides an

introduction to Tivoli Business Systems Manager. It also contains planning and

design information to consider when implementing Tivoli Business Systems

Manager.

v The new IBM Tivoli Business Systems Manager Introducing the Consoles provides an

introduction to the Tivoli Business Systems Manager console, Web console,

executive dashboard, and reporting system.

v The new IBM Tivoli Business Systems Manager Problem and Change Management

Integration Guide replaces the Tivoli Business Systems Manager Program User Exits

book. It describes how to write request processors to enable the problem,

change, and automatic ticket integration function provided with Tivoli Business

Systems Manager to work with problem and change management applications.

v The document Tivoli Business Systems Manager, Version 3.1, Guide for Warehouse

Pack, Version 3.2.0.0, using Tivoli Data Warehouse, Version 1.2 replaces the

document called IBM Tivoli Business Systems Manager Guide for Warehouse Pack,

Version 3.1.0.0, using Tivoli Data Warehouse, Version 1.2 issued in October, 2004. It

describes how to use the warehouse enablement pack to extract data from the

Tivoli Business Systems Manager database and load it into the Tivoli Data

Warehouse database, where it can be accessed using reporting and data analysis

tools. It also describes the Tivoli Business Systems Manager reports generated

from the data mart.

v To search for a term across the entire library, use the Tivoli Business Systems

Manager Information Center at


Documentation updates

This section provides information that was identified after the documentation was

finished.

Updates to the Installation and Configuration Guide

This section describes updates to the IBM Tivoli Business Systems Manager

Installation and Configuration Guide.

Changes to the “Installation CDs” section: The IBM Tivoli Business Systems

Manager Translated Documentation CD is available. It contains translated versions of

the Tivoli Business Systems Manager library in the following languages:

v Spanish

v Brazilian Portuguese

v German

v French

v Italian

v Japanese

v Korean

v Simplified Chinese

v Traditional Chinese

v Arabic

Changes to the “Event Enablement Specifications” section: With Tivoli Business

Systems Manager Interim Fix 3.1.0.0-TIV-BSM-IF0003, the following Linux releases

are now supported for Event Enablement:

v Tivoli Enterprise Console 3.9 with Fix Pack 2

– United Linux for IA32 (SLES 9)

– United Linux for zSeries (SLES 9) - v 1.0




v Tivoli Enterprise Console 3.9

– Red Hat Enterprise Linux 2.1 (IA32)

– Red Hat 3.0

– Red Hat 3.0 for zSeries

– United Linux 1 (SLES 8)

– United Linux 1.0 (SLES 8) for zSeriesv Tivoli Enterprise Console 3.8

– Red Hat Enterprise Linux 2.1 (IA32)

– United Linux 1 (SLES 8)

– United Linux 1.0 (SLES 8) for zSeries

Updates to the Administrator’s Guide

This section describes updates to the IBM Tivoli Business Systems Manager

Administrator’s Guide.

Addition to the “Percentage Based Thresholds” section: The information in this

section should be added to the “Percentage Based Thresholds” section.

Percentage Based Thresholds Best Practices: It is important to understand how

propagation processes events and determines whether to trigger an alert or not

when designing Percentage Based Threshold (PBT) events. Make sure you

thoroughly understand propagation before you set up PBTs. The following best

practices can help you design PBTs:

v Create PBTs in pairs. Create one PBT to trigger an alert and another PBT to clean

up the alert when the triggering criteria is no longer met. For ease of design, set

the criteria for the trigger and the cleanup PBTs to reverse conditions to ensure

they function properly together. For example, if you want to have the parent

resource turn Red when 40% or more of its child resources are Yellow or Red,

set the following as your triggering PBT criteria:

Trigger PBT: Min %: 60 Max%: 100 Min Alert: Yellow Max Alert: Red

To ensure your cleanup PBT resolves the event sent by the triggering PBT, set

the following as your cleanup PBT:

Cleanup PBT: Min %: 0 Max%: 59 Min Alert: Yellow Max Alert: Red

v Within PBT pairs, give events the same name. Make sure the event name is

unique from any other PBT pair.

v Consider disabling standard propagation. When using PBTs, you might not want

to continue using standard propagation for determining the Alert State of the

parent resource. Because child events from child resources may trigger alerts at

the parent and compete with the PBT at the parent, consider disabling standard

propagation by doing the following steps:

1. Lower the Resource Priority for all children to High, Medium, or Low.

2. Raise the both the Red and Yellow Child Event thresholds at the parent

resource to an extremely high number, such as 999.

Changes to the “Creating the Automated Business Systems Configuration File”

section: The following information replaces the information for CriteriaToPattern:

CriteriaToPattern

Establishes relationships between patterns. This is useful for identifying a group of

resources that requires several patterns to differentiate it from other resources. The

related patterns can be for the same resource or different resources. If the related


patterns are for resources that are of different classes, the automated business

system creation process searches either up or down the resource hierarchy for the

related resource.

Note: The following resource types can only be related to a resource above the

D2DG resource type in the hierarchy by referencing a common D2DG

resource:

v D2DB - DB2 Database

v D2TS - DB2 Tablespace

v D2TB - DB2 Table

v D2IX - DB2 Index

v D2IP - DB2 Index Partition

v D2TP - DB2 Tablespace Partition

For example,

Pattern

Pattern Class Attribute When Operator Operand1 Operand2

1 OS name Current LIKE MVSA %

2 D2DG name Current LIKE DB2DG %

3 D2TS name Current LIKE DB2TS %

CriteriaToPattern

Criteria Pattern PatternRelated

1001 1 1

1001 2 1

1001 3 2

Changes to the “Creating Default and Override Preferences” section: The

following information replaces the information in the “Creating Default and

Override Preferences” section:

Use the following steps to create the preferences.default file:

1. Log in to the Tivoli Business Systems Manager console as an Administrator.

2. Open Console –> Preferences and set values for the preferences that you want

to make the default values. Click OK to save your preferences.

3. Run the startimportexport command. See ″Using the Import/Export Utility″ for

more information on this utility.

4. Export the preferences for the user you logged in as in step 1.

5. Rename the exported username.prefs file to preferences.default

6. Edit the preferences.default file by replacing <name>Administrator</name> with

<name>preferences.default</name> assuming the preferences file you are

exporting is for the Administrator user name.

7. Run the startimportexport command again. Import the preferences.default file.

You now have a preference named preferences.default which is applied

automatically whenever a new set of preferences is created for a user.

Use the following steps to create the preferences.override file:

1. Log in to the Tivoli Business Systems Manager console as an Administrator.

2. Open Console –> Preferences and set values for the preferences that you want

to make the default values. Click OK to save your preferences.

3. Run the startimportexport command. See ″Using the Import/Export Utility″ for

more information on this utility.

4. Export the preferences for the user you logged in as in step 1.

5. Rename the exported username.prefs file to preferences.override


6. Edit the preferences.override file by replacing <name>Administator</name> with

<name>preferences.override</name> assuming the preferences file you are

exporting is for the Administrator user name.

7. Run the startimportexport command again. Import the preferences.override file.

You now have a preference named preferences.override which is applied

automatically whenever an operator logs in or saves preferences.

Interim Fix Updates: A number of changes were made as a result of interim fix

3.1.0.0–TIV–BSM–IF0004. These changes are documented in this section.

Operational Reports: You can install four Tivoli Business Systems Manager

Operational reports on your Crystal Enterprise Server. These reports contain

up-to-the-minute information because the data comes from the Tivoli Business

Systems Manager production database server. The installation of these reports is

optional and does not require the Tivoli Business Systems Manager 3.2.0.0

Warehouse Pack. These reports use stored procedures that are defined in the Tivoli

Business Systems Manager Object database.

Installing Operational reports: To install Operational reports, do the following steps

on the Crystal Enterprise Server:

1. Run the setup program located in the file installed by 3.1.0.0–TIV–BSM–IF0004.

The installation process uses the default TEMP directory as a working directory.

If there is not enough disk space in your file system containing that directory,

install using the following command:

setup -is:tempdir name of another directory

If Crystal Enterprise Server is not installed, an error message is displayed and

installation stops.

2. When the InstallShield program opens, a language selection window opens.

Select a language and click OK. Or click Enter to select the default language of

your operating system.

3. A Welcome window is displayed. Click Next.

4. From the Software License Agreement window, select I accept the terms in the

license agreement. Click Next.

5. In the Directory Name text box, type the directory for your installation or click

Browse to install in a different directory.

The default installation directory is C:\Program

Files\Tivoli\tbsm\operational_reports.Click Next.

6. In the Crystal Enterprise Server Hostname text box, the name of the Crystal

Enterprise Server host is displayed. Type the user ID and password. Click Next.

7. In the IBM Tivoli Business Systems Manager Database Server Hostname text

box, type the name of the database server host. Type the database user ID and

password. Click Next.

8. The Summary window states the location of the installation, the components

that will be installed, and the size. Click Next. A window is displayed, showing

the installation progress.

9. A successful installation message is displayed. Click Finish to exit the

installation.

Uninstalling Operational reports: If you want to uninstall Operational reports, do

the following steps:

1. From the Windows taskbar, click Start –> Settings –> Control Panel –>

Add/Remove Programs.


2. Click IBM Tivoli Business Systems Manager Operational Reports. Click

Change/Remove.

3. Select a language. Click OK.

4. The uninstallation Welcome window is displayed. Click Next.

5. The preinstallation summary window displays the location where the console

code is installed. Click Next.

6. The Summary window opens, which lists any errors. Click Finish.

If you uninstall operational reports, reports still display in ePortfolio and need to

be manually deleted from ePortfolio. To delete Operational reports from ePortfolio,

from the Tivoli Data Warehouse information center, do a search for deleting reports

and follow the instructions. For more information regarding the administration and

maintenance of your Crystal Enterprise Server, refer to the Tivoli Data Warehouse

information center.

Operational reports descriptions: This section describes the four operational reports

included in 3.1.0.0–TIV–BSM–IF0004.

Business System Alert State:

Description of the report

This report displays all of the resources within a selected business system

with the selected alert values. This report contains the following columns:

Main report:

v Resource Name

v Resource Path

v View Alert State

Sub report:

v Resource Path

v Resource Type Name

v Complex/Region

v OS/Location

v Alert State

v Priority

Purpose of the report

This report can be used to view logical resources and their alert states.

Parameters of the report

Main report:

v Resource Name

v Alert State

Sub report: none

Stored procedures for the report

Main report:

ObjectEvents..ObjPatheCache_V

Sub report:

ObjectEvents..gtm_lobalertstate

SQL for the report

Main report:


SELECT ObjPathCache_V.resourcepath, ObjPathCache_V.resource,

ObjPathCache_V.id, ObjPathCache_V.cid

FROM ObjectEvents.dbo.ObjPathCache_V ObjPathCache_V

WHERE ObjPathCache_V.resource LIKE N’{?resource_name}’

AND ObjPathCache_V.cid=N’LOB’

Sub report:

{CALL ObjectEvents.dbo.gtm_lobalertstate;1(@parlobid, @alertstatelist}

Current MVS Messages/Exceptions:


This report displays events for any resource class that may be contained

within a MVS operating system. This report is grouped by OS Name,

Resource Type, Resource Name and Event Type. This report contains the

following columns:

Main report:

v Alert State

v Priority

v Event Name

v Event Detail

v Event Date/Time


This report can provide a focused view of the events for resources that are

contained within a MVS™ operating system.


Main report:

v Resource Type

v OS

v Resource Name

v Alert State

v Priority

v Beginning Date/Time

v Ending Date/Time

v Detail


Main report:

ObjectEvents..gtm_livemvsmsgexc

SQL for the report

Main report:

{CALL ObjectEvents.dbo.gtm_livemvsmsgexc;1(@classlist,@oslist,

@objname,@alertstatelist,@prioritylist,@begdate,@enddate,@eventopt,@detail)}

Global Business System Alert State:


This report displays events for all of the resources within an enterprise.

This report contains the following columns:

Main report:

v Resource Path

v Resource Type

v Complex/Region

v OS/Location

v Alert State

v Priority



This report can show a wide view of all of the logical resources and their

alert states.


Main report:

v Alert State


Main report:

ObjectEvents..gtm_lobalertstateglobal

SQL for the report

Main report:

{CALL ObjectEvents.dbo.gtm_lobalertstateglobal;1(@alertstatelist)}

Shift Turnover:


This report displays the events that occurred during a given shift, whether

or not ownership was taken, and what action has been taken. This report is

grouped by resource class id and resource name. This report contains the

following columns:

Main report:

v Event Type

v Event Name

v Event Date/Time

v Event Description

v Alert State Priority

v Event Owner

v Owned Date/Time


This report provides a focused list of distressed resources that need

priority attention by the upcoming operations shift.


Main report:

v Shift Length

v Shift End Date/Time

v Event Status


Main report:

ObjectEvents..gtm_shiftturnover

SQL for the report

Main report:

{CALL ObjectEvents.dbo.gtm_shiftturnover;1(@shiftlength,

@datetime,@ownership)}

Configuring the historical reporting target URL: In the Tivoli Business Systems

Manager console, two reports can be launched from the context menu of a

resource. From a physical resource, you can run the Physical Resource Event

report. From a logical resource, you can run the Business System Event report. By

default, these two reports are launched from the reporting system that can be

installed as part of Tivoli Business Systems Manager. If you want to launch the

reports from the Crystal Enterprise ePortfolio application on the Crystal Enterprise

Server, you must configure the URLs within a table in the Tivoli Business Systems


Manager Object database. Use the gtm_setreportappurl stored procedure in the

Tivoli Business Systems Manager Object database to configure the URLs. Table 2

lists the parameters for the gtm_setreportappurl stored procedure.

Table 2. gtm_setreportappurl stored procedure parameters

Name Type Description

@report_server_name nvarchar(255) The name of either the

Microsoft Internet

Information Services server

or the Crystal Enterprise

Server

@report_app_name nvarchar (255) A value that indicates if the

URL should launch to the

Internet Information

Services-based reporting

application or the Crystal

Enterprise ePorfolio

application. The only valid

values are IIS or ePortfolio.

These values are not case

sensitive.

@ssl_enabled tinyint A value of 1 to indicate that

https should be used rather

than http.

@verbose int The flag to activate more

detailed debugging and trace

information when the

procedure is executed.

@err int An output parameter that can

be used to capture error code

returned from the procedure.

A value of 0 indicates the

procedure executed without

error.

Note: This procedure will replace the existing URLs in the MenuItem table with

new URLs based on the parameter values passed to the procedure. The

procedure does not save or backup the existing rows in the table. If for any

reason the URLs within the MenuItem table have been configured to meet

some installation requirement, you might need to save the values before

running this stored procedure.

To configure the Tivoli Business Systems Manager v3.1 console to connect to either

the Internet Information Services-based reporting system or the Crystal

Enterprise-based reporting system, do the following steps:

1. Start Microsoft SQL Serve Query Analyzer and connect to the Tivoli Business

Systems Manager v3.1 database server.

2. Make sure that the Object database is the default database by either selecting it

from the database list in the tool bar or executing the following SQL

statements:

Use Object

Go

3. To configure the launch URL, execute the following SQL statement:

exec gtm_setreportappurl server name,app name,ssl


where server name is the name of your reporting system server, app name is

either iis or eportfolio, and ssl is either 0 or 1.

Example:

To configure the URL to a IIS server named Reporting which does not use SSL

communications, issue the following SQL command:

exec gtm_setreportappurl ‘Reporting’,’iis’,0

To configure the URL to a Crystal Enterprise server named Crystal which does

not use SSL communications, issue the following SQL command:

exec gtm_setreportappurl ‘Crystal’,’eportfolio’,0

You can only launch reports from either the Crystal Enterprise ePortfolio

application or the Tivoli Business Systems Manager reporting system application

but not both.

Updates to the Task Assistant

The following information was identified after the Task Assistant was completed:

v The Business Impact view uses the HyperView row limit to control how many

rows are displayed.

Product fix history

See “APARs corrected in version 3.1,” on page 35 for a list of APARs that have

been corrected for this release of the Tivoli Business Systems Manager product.

Backward compatibility

v Tivoli Business Systems Manager v3.1 is compatible with all supported z/OS

versions of Source/390.

v Tivoli Business Systems Manager v3.1 is compatible with the v2.1.1 Fix Pack 6

versions of Event Enablement and the Intelligent Monitor and NetView adapter

endpoints.

v Tivoli Business Systems Manager v2.1.1 consoles are not compatible with the

v3.1 console server.

v Tivoli Business Systems Manager v3.1 consoles are not compatible with the

v2.1.1 console server.

v You can install the v3.1 console on a workstation with the v2.1.1 console and

each can communicate with its respective console server.

v Tivoli Business Systems Manager v3.1 no longer supports the Windows NT®

operating system. Servers are run on Windows 2000 Server / Advanced Server

with Service Pack 4 or Windows 2003 Standard/Enterprise Edition.

v Microsoft SQL Server 7.0 is no longer supported. You must upgrade to SQL

Server 2000. Refer to IBM Tivoli Business Systems Manager Installation and

Configuration Guide for instructions.

v Tivoli Business Systems Manager v3.1 no longer supports AIX® 4.3.3 as a client

platform.

v Tivoli Business Systems Manager v3.1 requires MKS Toolkit v8.6 or v8.7. Refer to

IBM Tivoli Business Systems Manager Installation and Configuration Guide for the

latest software and hardware requirements.


Product compatibility

Refer to IBM Tivoli Business Systems Manager Installation and Configuration Guide for

a list of supported data sources.


Chapter 2. Installation, upgrade, and configuration information

This chapter describes installation and upgrade changes for IBM Tivoli Business

Systems Manager Version 3.1.

Hardware and software requirements

Refer to the IBM Tivoli Business Systems Manager Installation and Configuration Guide

for the hardware and software requirements for installing Tivoli Business Systems

Manager.

Installation and configuration notes

This section describes installation changes for Tivoli Business Systems Manager

Version 3.1.

Installing base services

This section describes installation changes for Tivoli Business Systems Manager

Version 3.1 base services.

v Tivoli Business Systems Manager v3.1 automatically verifies that you installed

prerequisite software.

v Tivoli Business Systems Manager v3.1 installs WebSphere V5.0.2 when it installs

the console server.

v The console server runs on the WebSphere Application Server. The security uses

the WebSphere Application Server registry and is based on either LDAP or Local

OS.

v There is no longer a propagation server. Propagation is handled by the database.

v There is a new EIF Sender service. It sends Tivoli Business Systems Manager

state change events to the Tivoli Enterprise Console application.

v We do not support using a WebSphere Application Server other than the one

installed by Tivoli Business Systems Manager.

v Tivoli Business Systems Manager is not supported in a clustered environment.

Components should not be installed on clustered servers.

v If your installation directory contains a space and you run the installation

program more than two times, any previously installed Tivoli Business Systems

Manager v3.1 components might not be selected in the Select Components

window during installation. Do not select the components that you know are

already installed. Select only the new components that you want to install.

If your installation directory does not contain a space, and you are adding

additional components to an existing Tivoli Business Systems Manager v3.1

system, then some files are overwritten during your installation. To install Tivoli

Business Systems Manager successfully, do the following steps:

1. Go to the bin directory and back up the following files if they exist:

– enqueuecl.ksh

– enqueuecl.properties

– querycltran.ksh

– querycltran.properties2. Back up the global.asa file in the ASIReports\ASIWeb directory if it exists.

3. Install additional Tivoli Business Systems Manager components.


4. Restore all backed up files.

Installing the console

This section describes installation changes for the Tivoli Business Systems Manager

Version 3.1 console.

v Tivoli Business Systems Manager Version 3.1 automatically verifies that you

have enough space to install the console.

v You can install the console manually, using silent installation, or using a Tivoli

Configuration Manager Software Package Block.

Installing National Language Support

The National Language Support chapter in the IBM Tivoli Business Systems Manager

Installation and Configuration Guide mentions a National Language Support CD and a

Language Support CD. The correct name of the CD is Tivoli Business Systems Manager

Language Pack.

Upgrade notes

The following upgrade notes apply to Tivoli Business Systems Manager v3.1:

v Refer to the Upgrading Checklist in the IBM Tivoli Business Systems Manager

Installation and Configuration Guide for instructions on how to upgrade Tivoli

Business Systems Manager v3.1.

v You no longer need to install Microsoft Internet Information Server on the

console server.

v The health monitor client workspace is not migrated to v3.1. The v3.1 health

monitor client works with the v3.1 or 2.1.1 health monitor server.

v The health monitor SQL Response Time view has been deleted. The Idle Since

column of the Staged Event Status views indicates the response times of critical

database procedures.

v After upgrading Tivoli Business Systems Manager, use the import/export utility

to save your v2.1.1 preferences and workspace settings. You can also send the

exported files to IBM Software Support for customer assistance. Refer to the IBM

Tivoli Business Systems Manager Administrator’s Guide and IBM Tivoli Business

Systems Manager Installation and Configuration Guide for information.

v If your installation directory contains a space and you run the installation

program more than two times, any previously installed Tivoli Business Systems

Manager v3.1 components might not be selected in the Select Components

window during installation. Do not select the components that you know are

already installed. Select only the new components that you want to install.

If your installation directory does not contain a space, and you are adding

additional components to an existing Tivoli Business Systems Manager v3.1

system, then some files are overwritten during your installation. To install Tivoli

Business Systems Manager successfully, do the following steps:

1. Go to the bin directory and back up the following files if they exist:

– enqueuecl.ksh

– enqueuecl.properties

– querycltran.ksh

– querycltran.properties2. Back up the global.asa file in the ASIReports\ASIWeb directory if it exists.

3. Install additional Tivoli Business Systems Manager components.

4. Restore all backed up files.


v As part of the upgrade process, the values of propertynames

AdminClearAlertsDefault, REQUEST_CLEAR_EVENTS, and

CLEAR_ALERTS_ON_OWNERSHIP_DEFAULT in the SystemConfiguration table

are updated to be consistent with your setting of OperatorClearAlertsDefault as

described in Table 3. If you edited these values, after upgrading they will reflect

the value of OperatorClearAlertsDefault.

Table 3.

groupname propertyname Description

Note OperatorClearAlertsDefault This is the default behavior for operators

when taking ownership from Tivoli

Business Systems Manager.

Note AdminClearAlertsDefault This is the default behavior for

administrators when taking ownership

from Tivoli Business Systems Manager.

REQUEST_AUTOTICKET REQUEST_CLEAR_EVENTS This is the default option for autoticket

event clear/do not clear.

TEC_EVENT_OWNERSHIP CLEAR_ALERTS_ON_OWNERSHIP

_DEFAULT

This is the default option for Tivoli

Enterprise Console event clear/do not

clear.

v See “Backward compatibility” on page 18 for more information on upgrading

Tivoli Business Systems Manager.

Uninstallation information

The IBM Tivoli Business Systems Manager Installation and Configuration Guide lists

uninstallation information.

Chapter 2. Installation, upgrade, and configuration information 23

Chapter 3. Known limitations, problems, and workarounds

This chapter describes software limitations, problems, and workarounds.

Limitations

The following software limitations are present in Tivoli Business Systems Manager

3.1:

Tivoli Business Systems Manager console

v The Actions menu on the console shows the actions available on a selected

resource in a view. When the Event view is open, the Actions menu provides

the actions available on the selected resource in the parent view, not on the

selected event in the Event view. To perform actions against an event in the

Event view, right-click the event and select an action from the context menu.

Web console

v After a period of inactivity, WebSphere Application Server will timeout and close

your session. The default timeout setting is 30 minutes. If you want to change

the timeout value, see the WebSphere Information Center at

http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp

Click All Topics by activity –> Administering –> Applications –> Web

modules –> Configuring session management by level. Do not disable the

timeout feature because it cleans up sessions that are ended improperly.

Executive dashboard

v When an IT Executive role user opens the Service Status Details view, the

information detailing the problem resource is duplicated for each of its unique

paths within the business system tree.

Console server

v Uninstalling the console server requires 400 MB free disk space. If you do not

provide this much free space before uninstalling, parts of Tivoli Business

Systems Manager might not get uninstalled. If this occurs, uninstall the

ITBSMConsoleServer application using the WebSphere Application Server

Administrative Console.

v Although Tivoli Business Systems Manager supports the use of multiple

WebSphere Application Servers for supporting multiple console servers, these

servers cannot use different user registries. This user registry may be used by

multiple servers for redundancy or load balancing purposes but must represent

a single logical LDAP directory or domain.

User Registries

v Due to discrepancies in LightWeight Directory Access Protocol (LDAP) and local

authentication systems, do not use character combinations that include multiple

contiguous spaces or the equal sign (=) followed by spaces in Tivoli Business

Systems Manager user IDs.


http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp

Automated Business Systems

v When using the abstest.ksh command to evaluate patterns and criteria,

performance is directly related to how specific the patterns and criteria are. The

more unambiguous the patterns and criteria used in configuring Automated

Business Systems, the better performance is when evaluating with the

abstest.ksh command.

v If an attribute of a resource is in both the Pattern and the CriteriaToPath sections

of the automated business system configuration file and that attribute is changed

to match the criteria again, then a business system is created. This happens

regardless of previous business system creations.

v The automated business system discovery processing monitors resource creation

and attribute changes but does not monitor changes in relationships or linkage.

Monitoring SNA/APPN resources

v Tivoli Business Systems Manager is only capable of monitoring SNA/APPN

resources from a single RODM at a time. To allow for maintenance of the

operating system supporting RODM, it is possible to switch SNA/APPN

monitoring from a primary operating system to a secondary operating system.


information about RODM failover.

Intelligent Monitor for Tivoli NetView

v When configuring Intelligent Monitor for Tivoli NetView, do not use the

following characters as part of the NVID:

– less than sign (<)

– greater than sign (>)

– ampersand (&)

– single quote (’)

– double quote (″)

Refer to the IBM Tivoli Business Systems Manager Installation and Configuration

Guide for more information about adapter configuration.

Problems and workarounds

Tivoli Business Systems Manager console

v Problem: If a v2.1.1 console was configured to open a default workspace, the

workspace might not open automatically after you upgrade to v3.1.

Workaround: Click Console –> Open Workspace. Click the workspace and

select the Automatically open the selected workspace when the console is

started check box. The workspace will open when you start the console.

v Problem: In the User Names drop-down list, typing the first letter of a name

does not select that name. This drop-down list appears on the Take Ownership,

Note Properties, and Transfer windows.

Workaround: Use the mouse to select the user name from the drop-down list.

v Problem: The Tivoli Business Systems Manager console cannot be launched from

the NetView Management Console on AIX.

Workaround: Install a more recent version of the NetView Management Console

to be able to launch the console. The NMC client can be downloaded from the

IBM website by doing the following steps:

1. From a Web browser, go to http://www.ibm.com/software/support/


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

2. Click Support & downloads.

3. Click Downloads & drivers under the Downloads.

4. Search for netview management console.

5. Click NetView Management Console Topology Console from the download

search results.

6. Download the instructions and package for your platform. Use the most

recent version.v Problem: The Owner column filter for tables like the Event View does not allow

you to enter text. You can only select from the list of current users. If events are

generated with an owner name that is not defined in Tivoli Business Systems

Manager, you are unable to filter on this unrecognized owner.

Workaround: Instead of using the Owner filter, click on the Owner column

header to sort all events by owner. This makes it easy to locate events and

perform actions against them.

v Problem: If you migrate from the LocalOS user registry to LDAP, existing notes

do not appear in the Notes View because the Owner column filter uses the

LocalOS form of the user ID.

Workaround: To fix the Owner column filter, do the following steps:

1. Right-click the header of the Owner column and click Context –> Filter –>

Edit Filter.

2. Select your user ID from the list in the Edit Filter window and click OK. Do

this for each console.

For an Operator to modify this filter, on the Notes tab in Administrator

Preferences, select Allow Operators to: View all notes in Notes View.

Web console

v Problem: Changes to shared filters on the Web console are not applied to other

users until they log off and log on. Also, if the filter is already open in another

view on the current Web console, the changes are not applied to that view.

Workaround: To view the changes to the filters, other Web console users must

log off and log on. To see changes to the filter name or criteria, the other Web

console users must close and reopen any open filter views.

v Problem: In the v2.1.1 Web console, if you created a resource or event filter with

wildcard characters in the Owner ID field, the filter runs correctly in v3.1.

However, when you edit the filter, the Owner ID is not displayed in the

drop-down list.

Workaround: If you want to search for resources and events by multiple Owner

IDs, create a filter criteria for each owner.

v Problem: In the console, you are required to type resolution text when closing a

note. The Web console does not enforce this restriction, allowing you to close

notes without typing resolution text.

Workaround: Type resolution text when closing notes on the Web console.

v Problem: When using Microsoft Internet Explorer 6, users experience random

authentication failures when logged onto the Web console and reporting system.

These failures often occur after timeouts while logging back on.

Workaround: This problem is a result of a Microsoft Internet Explorer defect.

The fix for this problem is documented at

http://support.microsoft.com/?kbid=831167.

Chapter 3. Known limitations, problems, and workarounds 27

http://support.microsoft.com/?kbid=831167

Executive dashboard

v Problem: When a user is deleted from the executive dashboard list, the change

is not apparent in the list until you manually refresh the view.

Workaround: To manually refresh the view, click the refresh button in the lower

right corner of the executive dashboard list window.

v Problem: Occasionally because of server workload, a No Services warning

message is incorrectly displayed and no services show up in the executive

console view.

Workaround: Exit the executive dashboard and log in again.

v Problem: If you click Switch Back from a details screen or from the drop-down

list, context is lost and a There are no services configured for this user

message is displayed.

Workaround: Click Go to Problem for one of your services. This resets the

context.

v Problem: Executive dashboard users are not transferred if their role changes.

This applies to users changing from the Executive role to the IT Executive role

and vice versa.

Workaround: To move a user from one executive dashboard role to another, do

the following steps:

1. Remove the user from the first role using the WebSphere Application Server,

LDAP, or local OS group depending on how you are maintaining your lists.

2. From the Tivoli Business Systems Manager console, click Administrator

Preferences –> User Names then click Refresh Cache.

3. Refresh the executive dashboard Lists view using the context menu. The user

is marked as deleted.

4. Open the context menu for the user ID marked as deleted and click Remove.

5. Add the user to the second role using the WebSphere Application Server,

LDAP, or local OS group depending on how you are maintaining your lists.

6. From the Tivoli Business Systems Manager console, click Administrator

Preferences –> User Names then click Refresh Cache.

7. Refresh the executive dashboard Lists view using the context menu. The user

is displayed.

8. Add the appropriate services to the user under the new group, because the

user’s services from the old role are longer associated. Refer to the IBM Tivoli

Business Systems Manager Administrator’s Guide for more information about

working with the List view and executive dashboard user IDs.

Console server

v Problem: The Message WARNING: Cannot set header. Response already

committed warning message might appear repeatedly in the WebSphere log file

as a result of users logging onto the console.

Workaround: These messages can be ignored.

v Problem: If you are using LDAP, and an LDAP Common Name (CN) contains a

comma, it may be displayed in the console with the comma preceded by a

backslash (\).

Workaround: How the name is formatted depends on your LDAP configuration.

Ignore the preceding backslash (\).


Health monitor service

v Problem: The Health Monitor service slowly consumes memory resources at the

rate of approximately 3.9 MB per day because of an underlying issue with the

sh.exe program. The Health Monitor might stop working after a few weeks

because of this memory shortage. This is a result of an issue with MKS Toolkit

and is addressed by problem CFS 25008 with the MKS Toolkit Resolution group.

Workaround: Install MKS Toolkit 8.7 Patch 3 on the machine where you

installed the Health Monitor server. You can get MKS Toolkit 8.7 Patch 3 from

the MKS Web site at http://www.mkssoftware.com/support/patches.asp#tk87.

You can request a patch for MKS Toolkit 8.6 from the MKS Toolkit group.

If you do not want to install MKS Toolkit Patch 3, stop and start the Health

Monitor service every two weeks to release the consumed memory resources.

Problem request processor

v Problem: When using the sample problem ticket request processor, problem

tickets created from the physical resource hierarchy cannot be found in the

business system hierarchy when you click Problem Ticket –> Find.

Workaround: Find problem tickets by clicking Notes –> Find or click Problem

Ticket –> Find on the physical hierarchy. In general, management of resources

including problem tickets should be implemented using the logic or business

system implementation of a resource.

XML toolkit

v Problem: When verifying an XML file using either the -o or -v option of the

enqueuecl.ksh command, if the schema location value contains spaces the

validation fails. This type of failure only occurs on validation, so if the command

is run without the the -o or -v option it will process normally.

Workaround: In the enqueuecl.properties file in the install_dir/bin directory,

replace every space in the TBSMSchemaLocation value with %20. For example:

TBSMSchemaLocation = D:/Program Files/Tivoli/xml

is changed to

TBSMSchemaLocation = D:/Program%20Files/Tivoli/xml

v Problem: If you use object priority on business systems, do not use the XML

toolkit to restore your business systems.

Workaround: Contact IBM Software Support for customer assistance.

Agent listener

v Problem: When the Agent Listener loses a connection to event enablement, it

will try to regain connection for only 2 minutes.

Workaround: If the network connection is lost for more than 2 minutes, restart

the Agent Listener. To avoid this problem, modify the time interval with the -t

parameter and number of retries with the -n parameter of the gemeeconfig

command.

Data maintenance jobs

v Problem: The Delete Old ObjectEvent Records Job does not run successfully. By

default this job is disabled. This problem occurs only if it is re-enabled.

Workaround: Disable the Delete Old ObjectEvent Records job because this job is

no longer required for maintenance.


http://www.mkssoftware.com/support/patches.asp#tk87

Common listener adapter for Tivoli Workload Scheduler

v Problem: The common listener adapter that ships with Tivoli Workload

Scheduler Distributed has integration issues with Tivoli Business Systems

Manager.

Workaround: Refer to http://www.ibm.com/software/support/ for further

information about this issue.

Event processing

v Problem: Event processing errors occur when local time reverts from Daylight

Time to Standard Time. Daylight Time is also known as Advanced Time,

Summer Time, or Legal Time. Standard Time is also known as Winter Time.

Workaround: There is no workaround at this time. This problem will be fixed

when the next fix pack is released.

Ownership

v Problem: An unowned event indicator does not display on a newly created

Business System after a drag operation when the resource receives an event after

the original ownership was taken.

Workaround: Work directly with the resource to see the unowned event. The

unowned event indicator is visible on the resource from which the new resource

was dragged. This problem is cleared the next time ownership is taken on the

business system.

Task server

v Problem: After some network outages, the connection from the Task Server to

NetView is lost and not recovered. The operator receives the following error

message:

GTMJC0682E Your access information cannot be validated because of a problem

with the NetView connection. Verify that the NetView connection is active

and retry the operation.

Workaround: Stop and start the Task Server, then issue the NETCONV start

command to reactivate the communications session between NetView and Tivoli

Business Systems Manager.

RODM

v Problem: If a RODM SNA Network (SNNT) resource is deleted, and a

subsequent RODM discovery performed before the Update ObjPathCache job

runs, registration might not work for RODM objects.

Workaround: After deleting a RODM SNA Network resource run the Update

ObjPathCache job from the SQL Enterprise Manager before performing a new

RODM discovery.

v Problem: When monitoring the RODM data source, propagation problems can

occur when resources are deleted and then rediscovered.

Workaround: Contact IBM Software Support for available updates before

upgrading to Tivoli Business Systems Manager v3.1.

Crystal Enterprise Server Reports

v Problem: When attempting to view or schedule Tivoli Business Systems

Manager reports, the following Crystal Server error message might display:

Maximum processing time or maximum records limit reached.


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

This error message is displayed when the number of database records returned

from a report exceeds the maximum number allowed by the Crystal Page Server.

The default value is 20,000 records.

Workaround: Change the maxdbresultrecords command line parameter in the

Crystal Page Server. To change this value, do the following steps:

1. From the Crystal Enterprise Launchpad, click Administrator’s Guide under

the Documentation section.

2. Go to the Server Command Lines, Page Server and Cache Server section for

instructions on how to change the maxdbresultrecords command line

parameter.

3. Change the maxdbresultrecords command line parameter.

Historical reports

v Problem: If you use the DHTML Viewer as the preferred report viewer when

viewing the parameter page in the Crystal ePortfolio application for the MVS

Message/Exception report, the Resource Type drop-down list does not display

some options. There is a 50-item limitation in the DHTML drop-down list.

Workaround: Either type the desired class identifier (CID) in the text box

provided, or change the preferred viewer to one that does not have this

limitation. The ActiveX viewer does not have this limitation.

Each viewer behaves differently when it comes to displaying and prompting for

parameter values. For example, the DHTML Viewer automatically passes the

user’s preferred time zone value to reports that have been time zone enabled.

The ActiveX viewer prompts for the time zone value. Check the Crystal

Enterprise documentation for details on all of the available viewers.

Operational reports

v Problem: One of the parameters for the Current MVS Messages/Exceptions

report is the operating system (OS) under which the resources belong. This

parameter is the numerical ID of the OS and not the name of the OS.

Workaround: For the OS parameter, use the numerical ID. For example, if an

instance of an OS is named My OS and has an ID of 123, use 123 as the

parameter value.

Internationalization issues

Limitation using the console in Hebrew and Arabic

v Problem: If you use a bidirectional language, the following problems occur:

– When you start up the console, question marks (?) appear in the progress

window.

– Window titles are displayed incorrectly. Sometimes the text is aligned on the

left instead of the right side of the window. The text might also be displayed

in left-to-right ordering instead of right-to-left ordering. The alignment and

ordering of text in window titles cannot be controlled by the Tivoli Business

Systems Manager console. This depends on the operating system, Java

version, default locale and keyboard locale.

You can set the text to be right-aligned if the default keyboard locale is set as

Hebrew, however the text ordering might still be incorrect.

Workaround: There is no workaround at this time.

v Problem: Some menu items may not be addressable with mnemonics. This is

due to Java defect #4374402.


Workaround: Use the F10 key to enable the menu bar and use the arrow keys to

navigate to the menu option.

v Problem: Clicking the clock icon on the Create Time filter while refining the

search of the notes view, opens an inoperable JavaScript helper panel.

Workaround: To provide a time filter, type the time value directly in the time

field.

Limitation using the executive dashboard in Hebrew and Arabic

Problem: The Flash version of the executive dashboard in Hebrew and Arabic does

not display text correctly.

Workaround: To be able to use the executive dashboard, use the HTML version.

Refer to the IBM Tivoli Business Systems Manager Installation and Configuration Guide

for information on how to launch and use the HTML version of the executive

dashboard.

Limitation using the task assistant in Hebrew and Arabic

Problem: When viewing the Task Assistant in Hebrew and Arabic, you might

notice the following issues:

v In the same Arabic word some characters are bold and others are not bold.

v Some of the dots that appear under some of the Arabic characters are not

directly under the character but instead are shifted to the bottom.

v Sentences that contain some special characters (for example, the hyphen (-) or

that contain images in the middle of the sentence cause the Arabic segments to

be ordered in the wrong way.

v Brackets that are found at the end of the sentence are reordered in the wrong

location.

Workaround: Launch the Task Assistant in an external browser. To enable the Task

Assistant in a separate browser, do the following steps:

1. Go to Console –> Preferences –> General and click Use a specific web

browser.

2. Click Enable Launching of Task Assistant in an External Browser.

The next time you click on the question mark, you will see Launch Accessible

Content at the top of the panel. Click the button to use the Task Assistant. If the

button displays Browser Not Configured, go back to the Console Preferences dialog

and make sure you enter a fully qualified executable file name or the launch

button will display a message instead.

Console locale limitation

Problem: Each Tivoli Business Systems Manager userid can be used only in a

single locale.

Workaround: If you need to change the locale for a userid, do one of the following

steps:

v Log off the userid and wait at least 30 minutes

v Restart the WebSphere Application Server that hosts the console server.

Running the console in different locales

Problem: The title bar of the console might display view and resource names

incorrectly if the console is running in a different locale than that of the resource

name. This is a limitation of the Windows operating system and affects only the

display of the title bar, not the operation of the console.



Running the console in a non-English language

Problem: When running the console in non-English languages, the welcome image

might be displayed with vertical spaces in the image. This problem is cosmetic

only and does not affect any console functions.

Workaround: After you open a workspace, or if a workspace is opened

automatically when the console is started, the welcome image is correctly replaced

by the workspace.

Running the console using Israel Daylight Time

Problem: Because start and end dates for Israel Daylight Time vary from year to

year, your operating system may not support Israel Daylight Time. On these

unsupported systems, manually adjusting your system clock during Daylight

Savings Time may cause timestamps displayed in the console to be incorrect by the

amount of the adjustment.

Workaround: Use Console Preferences to select a time zone that matches your local

time.

Time zone display in console preferences

Problem: On the General tab of the Console Preferences window, you can select

the current time zone using the time zone drop-down list. This list displays the

available time zones, including description and common cities. Depending on your

locale, these descriptions might be displayed in the English language and not the

current language. This is a system limitation that does not affect the actual times

displayed throughout the console, only the descriptions displayed in the Console

Preferences window.


Using the Web console in traditional Chinese

Problem: When refining the search of notes, the Create Time field dialog is

formatted improperly.

Workaround: To provide a filter time, ignore the time chooser window and type

the time directly.

Kanji translation of messages and help windows

Problem: The Kanji translation of Tivoli Business Systems Manager messages and

help windows that are displayed on the NetView z/OS console are shipped on the

Tivoli Business Systems Manager tape media. Previously they were shipped as part

of a NetView z/OS release or PTF.

Workaround: Refer to IBM Tivoli Business Systems Manager Installation and

Configuration Guide for instructions on how to customize the Tivoli Business

Systems Manager installation to include these translations.

Accessibility problems

v Problem: When using an Accessibility screen reader with the Web console, after

you tab to many drop-down lists, you hear the screen reader start reading the

page over from the beginning.

Workaround: Press ALT + the down arrow key to open the drop-down list.

Press the down arrow key to select the preferred value. Press Enter.


v Problem: Some versions of JAWS for Windows are incompatible with the built-in

screen reader included in Tivoli Business Systems Manager. JAWS takes over the

sound driver and you cannot hear the instructions.

Workaround: Quit the JAWS application before installing Tivoli Business

Systems Manager using the screen reader.


Appendix. APARs corrected in version 3.1

The following APARs have been corrected for this release of the Tivoli Business

Systems Manager product. The APAR number precedes the description of the

defect.

v OA01855.2: The ObjectQueues database grows large. The notification queue

accumulates data and is never cleaned up.

v OA02000: The input_bom files are allocated into the winnt system32 directory

instead of TEMP directories and are never deleted.

v OA02118: The event viewer takes a very long time to refresh.

v OA02217: Even though the state of the Common Listener service is running,

internal problems or network problems can stop events from being processed.

The Common Listener service must be monitored.

v OA02320: When using a bidirectional Tivoli Enterprise Console-Tivoli Business

Systems Manager connection, closing an open tbsmstatus does not close the

Tivoli Enterprise Console event. The status stays ack.

v OA02343: The staged event loader (StagedEventLoader) causes deadlocks in the

Tivoli Business Systems Manager database, resulting in timeout messages for

SQL statements issued by Tivoli Business Systems Manager console sessions.

v OA02353: The wrong alert state is received when a new message is added for

some class objects.

v OA02410: The menuitemcache cleanup job does not end and uses half of the

processor resources.

v OA02455: A source/390 tab needs to be added to the properties notebook for the

GOBJ (generic object resource) resource class.

v OA02598: The open DB2 resources function on business systems times out.

v OA02621: The health monitor fails with version 8.1 of MKS Toolkit for

administrators. The MKS version of the SORT command and the Windows

version of AT are needed.

v OA02646: When running the event viewer from the IPNW object class, the

″Invalid column name ’IDPATH’″ error message is received.

v OA02654: The ″String or binary data would be truncated″ error message is

received when the tree structure is expanded in the LOB Object Tree option in

the reporting system.

v OA02669: Exceptions cannot be owned from parent object levels in hyperview

and in the tree view.

v OA02679: The DUPLICATE_AGE setting under AUTO_PROBLEM in the system

configuration does not change the duplicate age.

v OA02684: The Staged Event Loader does not process SA390 records because of a

violation of the primary key constraint ’IMSS_IMPG_ASHL_PK’.

v OA02717: Tivoli Business Systems Manager cannot sign on to Tivoli

OMEGAMON®.

v OA02809: Error message ″Caught unknown exception processing event message″

logged in iposlistener log.

v OA02842: The staged event loader (StagedEventLoader) pauses after a PRINT

statement within asisp_discoverD2DGChildObjs.

v OA02872: CL_ATTRTOSTR does not work.


v OA02899: The propagation dispatcher service runs slowly and causes the

propagation dispatcher queue to grow.

v OA02933: Duplicate Tivoli Enterprise Console events are received for the same

object at the same time and the close event processing does not close the event.

v OA02959.1: The Update ObjPathCache job fails waiting for another Update

ObjPathCache job to complete, and repeated ″asisp_logObjPathCacheRun:

Waiting for 7 seconds for run ID nnnn to finish before starting run ID nnnn″

messages are shown.

v OA02975: After changing to daylight-saving time, distributed events show up on

the console one hour later than the real time.

v OA03013: The ″Cannot insert the value null into column ’GEN’...″ error message

is received when running the _GetManagedObjects process from Query

Analyzer.

v OA03054: Bulk common listener discovery creates excessive events, causing a

propagation agent backlog.

v OA03088: The propagation agent processes bulk load events slowly.

v OA03106: ″Network unreachable″ event from NetView distributed request for

information arrives at Tivoli Enterprise Console but is not sent to Tivoli Business

Systems Manager.

v OA03120: The GTM_CDW_DROP_TRIGGERS.SQL and

GTM_CDW_TRIGGERS.SQL scripts are missing from the ETL code for Tivoli

Data Warehouse.

v OA03205: Data corruption due to faulty insertion of a Windows CR+LF in

secondary properties from database.

v OA03234: The results from the filter output in the view IMS resources window

are wrong.

v OA03243: The cleanup procedure to remove all IMS objects from the database

erroneously adds resources before applying 2.1-BSM-0002-E13.

v OA03253: The Cleanup Deleted LOBs job fails.

v OA03314: DB2 up/down events create many child events, affecting performance.

v OA03360: The attachhistorydatabases.sql script does not work with Microsoft

SQL Server 2000 directories.

v OA03369: The SQL job cleanup discovery batches fails.

v OA03381: The addapplaunchermenuitem.sh and addapplauncherentry.sh

scripts have problems due to errors with backslashes (\) in scripts.

v OA03402: IHSTTTEC call does not return any return code.

v OA03408: After running the resetdb script, the following error message is

displayed: Procedure asisp_resetfiles, line update statement conflicted w/

column check constraint.

v OA03429: LOBL links are deleted during bulk upload of data from NetView.

v OA03430: Ownership notes are attached to green events.

v OA03434: From a NetView resource in Tivoli Business Systems Manager, clicking

on Launch, then NetView console, gets the nvservernotfound hostname error.

v OA03452: The TLLPARSER.SH script fails when there is a space in the task

name.

v OA03464: UMASK causes problems with TBSMTRAP.

v OA03466: Agent Listener log crash.

v OA03468: The Staged Event Loader processes very slowly into the

asisp_forwarddb2tablespaceevents stored procedure when processing some DB2

events.


v OA03486: The UpdateObjPathCache job runs slowly after new LOBs are added.

It used to take one minute and now takes more than one hour.

v OA03512: The bldgemtasks.sh command replaces ″index″ with ″-1″.

v OA03559: The ABSCreation process deadlocks while running with another

process.

v OA03562: Tivoli Business Systems Manager checks extra quote.

v OA03611: The asisp_processstagedcpsmevents command fails.

v OA03624: TNG object discovery service allocates a lot of memory during

processing.

v OA03626: Batch jobs discovered through the Common Listener have the

potential of being sent to the pump for registration on MVS.

v OA03628: The cl_allocatetrids script fails on Microsoft SQL Server 2000.

v OA03631: The mvsupload rule server service loops.

v OA03633: Component communications failure running in NetView daemon

mode.

v OA03662: Batch jobs discovered through Common Listener do not allow

multiple jobs with the same name.

v OA03761: When a large amount of data is processed, deadlocks can occur on

worktables like IMSTransaction_C_EV_WorkTable,

IMSDatabase_C_EV_WorkTable, LineOfBusiness_A_EV_WorkTable, and

IMSProgran_C_EV_WorkTable. Sometimes these errors lead to problems with the

PropagationAgent process.

v OA03769: When asking for a report on an IMS subsystem by selecting all events

including child events, only events related to the IMS subsystem are returned

and no child event is included in the report.

v OA03778: When resources are deleted, they are marked as being deleted but are

not removed from the database.

v OA03791: The MVS upload queue is sometimes corrupted which leads to

unpredictable results for event processing.

v OA03873: Staged Event Loader performance is affected when it tries to process

IMS events when the event flow contains non-contigous records with the same

ActionType.

v OA03875: PendingTECExportEvent table is not cleared even if Job Cleanup Old

DB Queue Entries is run.

v OA03887: After the automation discovery batch file is successfully loaded by the

Automation Discovery Load SQL job, the resulting tables are processed by the

Automation Discovery Process SQL job. This job takes a long time to run, causes

excessive database blocking, and holds up the Staged Event Loader, console

server and other SQL jobs.

v OA03913: Using NetView Distributed, heartbeat fails due to more than one user

trying to start processes.

v OA03937: Some auto ticket events stop having the correct value for

EXCEPTION_OCCURANCE_COUNT in the input data stream.

v OA03949: Customer asked for an explanation of why hyperview behavior

changes depending on the way it is invoked. Also why workspaces do not save

the status expanded/collapsed of resources showed in the view.

v OA04016: Failover does not transfer copies of user preferences between the

primary and the failover system (and back again) which means when

administrators and operators sign on, they are not presented with the same

workspaces.

Appendix. APARs corrected in version 3.1 37

v OA04085: The steps required to properly handle the message IEFC452I are not

documented.

v OA04099: Database migration from 2.1 to 2.1.1 fails at step 97968.SQL with ″The

specified @SERVER_NAME (’XXX’) does not exist.″ error.

v OA04130: Bad performance when users try to locate DB2 components into the

DB2 Managed Resource View.

v OA04161: If a business system is renamed, and the old and new names, when

combined, have a length greater than 54 characters, a String or Binary value

will be truncated error message is generated when the object is displayed by

some of the Reporting System Utility reports.

v OA04188: The tbsmtopo command crashes if Tivoli Business Systems Manager

class of the object is unknown.

v OA04223: Error: CL_PROCESSNEXTTRANS SQLEXCEPTION error code 16915.

v OA04232: Restore Database for Reporting System SQL daily job sometimes puts

the w3svc service in stop pending status and cannot restart.

v OA04263: Reporting system does not generate reports for events that are open

and unowned.

v OA04275: When running CICSPlex discovery with CICSPlex system groups that

are contained in more than one CICSPlex system group, the discovery fails with

a primary key constraint on the containment table.

v OA04289: The adapters register to the common listener using its backup NIC

instead of the correct NIC.

v OA04306: The reporting system seems to hang when requesting a Business

System Events report when the sort order option is set to ″(Machine/System),

Object type, Object name, Date/Time″.

v OA04346: After a priority change by the console or with the set_bsv_change.ksh

command, propagation gets the new event, but the clearing event leaves a

propagation on the MyResources LOB. The event exists in the childevent table

but it does not exist at the child object.

v OA04363: With Tivoli Business Systems Manager resources created by Tivoli

Enterprise Console events, both generic events (ihstttec) and DM events

(ihstztec) do not have the description attribute set on the resource. The

description attribute is the _Desc attribute in the database. This attribute is

displayed both on the properties dialog and optionally in the fly-over text.

v OA04384: The Staged Event Loader is paused because CA7 events cause

violations of unique/primary key.

v OA04488: Wildcard match fails on at_rule when using object name.

v OA04525: Worktables for a newly created class are not being created. This causes

the Agent Listener to crash when an event for such a class is received.

v OA04535: SQL pattern value set on path column of the event viewer is not

resolved at workspace reopening even if still set.

v OA04541: Violation of primary key constraint processedautomationevent_pk

cannot insert duplicate key in the processedautomationevent resource.

v OA04563: MVS Message/Exception option does not return data for CICS

regions.

v OA04572: The Reporting System hangs when running the Ownership Reports

and sorting by owner.

v OA04576: In the DB2 Resources and IMS Resources views, selecting ″Clear All

Filters″ causes a null pointer exception and it appears that the console is hung.

The table never displays the cleared filters.


v OA04602: When a CPSM file discovery event is sent to Tivoli Business Systems

Manager, the status of the file is updated and a message is sent to the CICS file

regardless of the Registration value. It is also not possible to set the priority

based upon the open and enabled status of the file.

v OA04614: When using the ihstttec command with -b parameter value such as ;;

the Agent Listener crashes.

v OA04629: In the failover script, the disablejobs entry is set to Req but under the

-Y parameter it should be set to Opt.

v OA04638: ABSConfig hangs when the currently loaded config file is big. Also if

the new config file is really small, ABSConfig goes in deadlock with some ABS

tables.

v OA04883: Events forwarded to Tivoli Business Systems Manager from Event

Enablement may arrive out of order if more than one event is received in the

same second.

v OA04927: Performance problems processing large volumes of events for

Automatic Ticketing and Automatic Notification because the function was

processing one event at a time when calling the an external request processor,

then waiting for the results to create the Note.

v OA05059: TNG delta discoveries take a long time to reach the console when the

number of events within the transaction is high.

v OA05078: Problem is that if customers have an ABS config file that has pattern

being used in multiple paths (in CriteriaToPath section), the ABS Creation

Process job fails stating duplicate @LinkedCID is issued.

v OA05158: The Staged Event Loader goes into a PAUSED state when it receives a

IEFC452I message because it cannot determine where to send it.

v OA05201: When running the detach/attach script, the systasks table is not

saved.

v OA05292: Delete unused DB2 data sharing groups fails.

v OA05340: Some OK events sent from Automation get missed for the GOBJ

resource.

v OA05371: The wrench icon does not appear on the object put in maintenance

mode.

v OA05374: Write more information in the exception (CL log).

v OA05395: The event_PK index does not exist on table History..eventhist.

v OA05435: Even if you set more than 1 file (e.g. 5) for Transport log in the

ASICommonListener.properties, each time you recycle the CL service it rewrites

the Transport log without adding a new one.

v OA05439: Only EXCP and MESG options are supported for Autoticketing.

CHVH and CHEV are non-supported classes.

v OA05447: There are 3 Automatic Ticketing design defects. There is no way to

enable or disable Automatic Ticketing SQL jobs. There is no way to reset

Automatic Ticketing queue control values. There is no way to adjust Automatic

Ticketing Health Monitor threshold values as it applies to a given production

environment.

v OA05461: Getting errors while running the Discover Active Address Space

utility. Problem is related to jobs that have a parameter that contains a single

quote.

v OA05485: When a registration record is sent from Windows NT to the Object

Pump at the same time as the initial registration records, and the record is

smaller than one of the initial registration records, the ASIMVSIPSenderSvc

osname does not send all the global variables required to complete the


initialization process in the Object Pump. The ASIMVSIPSendersvc has been

changed to improve the handling of sending the global variables when they are

sent from the ASIMVSIPSenderSvc osname service to the Object Server.

v OA05531: The list_lobc.pl script did not take into account business systems that

are linked to other business systems through LOBL links. The fix is to include in

the output list of the list_lobc.pl script any business systems that are linked to

other business systems with LOBL links.

v OA05649: Tivoli Business Systems Manager should handle point-point NetView

devices and does not.

v OA05650: In APAR OA03526/defect 115753/LAFix 2.1.1-BSM-0001-E75 (included

in Fix Pack 1), we changed the link_type of PHYC to GEPC between NLOC

(Network Locations) and other NetView resources, including

NODE/UNIX/NTSR. When making the change, it was assumed

NODE/UNIX/NTSR were only NetView distributed resources, but this is

incorrect.

v OA05653: Tivoli Business Systems Manager assumed that IDMS jobs would

always be run as a started task. Tivoli Business Systems Manager now traps the

messages however the IDMS is run.

v OA05696: If a problem ticket exists for an event and a second event comes in

that is identical, the same problem ticket number is assigned. For closure, all

events with the same problem ticket number should be closed.

v OA05712: While creating Automated Business Systems, absasisp_createlob fails

with errors on parameters @linkedcid and @name supplied multiple times.

v OA05756: Dr. Watson fails on the IM.exe process (TBSM Adapter, Object

Discovery service).

v OA05757: Tivoli Business Systems Manager does not delete NetView objects

correctly.

v OA05849: The task server does not talk to NetView over an SNA connection.

v OA05896: Initial registration fails immediately after initial program load.

v OA06011: New CICS objects are created unexpectedly when CPSM SAMOPS

exceptions containing an incorrect CICSPlex name are processed.

v OA06013: When a lowercase WebServer hostname is used in the control_id field

of the Object..MenuItem table, the failover script has problems updating it to the

target WebServer during failover execution.

v OA06050: When moving an LPAR between two machine objects, childevents are

not moved to the new object. This incorrect behavior of the _MoveObject stored

procedure leads to wrong propagation. Even if the child LPAR is red, the MACH

object remains green.

v OA06062: If you try to unregister files on a CICS region, they do not unregister.

CICS regions created before mid-2002 may have inaccurate registered file counts.

If the count is 0, it prevents unregister from working.

v OA06063: The tbsmconn command has trouble reading the input file. It only

executes the last line in the file.

v OA06078: The gemsp_delete_product script fails.

v OA06113: The common listener does not shutdown when it receives a transport

exception 100.

v OA06114: The PendingEvent table contains many rows with old data. A cleanup

job is needed to delete them.

v OA06124: The Health Monitor is dependant on Microsoft’s RKIll. Microsoft has

acknowledged a problem with that code, but it is not a supported API and will

not be fixed.


v OA06131: Tivoli Business Systems Manager v2.1.1 introduced two new resource

indicators: Automation is running and Automation has abended. A customer noticed

several objects in the busc that have been marked as Automation has abended

although the properties page shows that they are not abended.

v OA06153: The TNG Object Discovery service (the im.exe process) stops suddenly

and processes no other events. The last rows in the log shows the message

Trying to open DB.

v OA06160: After Tivoli Business Systems Manager v3.1 Fix Pack 6 is applied,

distributed objects are created under a new node.

v OA06161: Incorrect trap registration after the asisp_tws_disable script runs.

v OA06170: After restarting Tivoli Enterprise Console 3.8, the event enablement

server starts with the following error: IHS0227E: An operating system error

occurred during initialization. The Tivoli Business Systems Manager

daemon was unable to attach to the required shared memory or was unable

to allocate required semaphores.

v OA06199: Long messages received exceeding cellsize in the Tivoli Business

Systems Manager event handler queues causes Tivoli Business Systems Manager

to stop processing events.

v OA06206: When the 211bsm0006history.upg script runs and the default database

is set to master, the proc report_lobtree_explode script will fail with errors.

v OA06210: Errors within common listener log.

v OA06224: Propagation Agent failure caused by deadlocks on LineOfBusiness_A

and OpenEventCount tables.

v OA06225: Infinite basetesttrace.log log file.

v OA06239: Once a Systems Automation for OS/390 resource is uncategorized,

reclassified back to CICS, and then deleted, it is not rediscovered.

v OA06255: Data inconsistency between the NetworkNode class table and the

general link table. There are ten NetworkNode resources that are deleted in the

link table but are marked undeleted in the NetworkNode class table. The

CleanupDistributedResources procedure keeps showing duplicates, even though

there are none.

v OA06295: When exporting a report to Microsoft Excel, the text field gets

truncated.

v OA06315: The resetdb script does not clean up the SyncEvent table.

v OA06316: Duplicate ASIPAgent detected: program_name= PA ROOT, hostname=

fatal error.

v OA06323: Adapter hangs if the remote queue is removed.

v OA06379: Java clients hung caused by deadlocks on table Message_A involving

staged event loader and Java client processes.

v OA06397: The Installation Guide or Administration Guide has to include details

about Systems Automation for OS/390 discovery process.

v OA06447: Trouble ticket automation currently allows the creation of multiple

ownership notes on an object. This is unweieldy and creates difficulty for

management. Adding the current ownership state and problem ticket number to

the .in file would alleviate this problem.

v OA06467: There is no way to clean up old ignore exceptions.

v OA06509: There is no process to empty the failedautomationevent table.

v OA06520: The exceptions sent to the JCL ERRORS FOR IEFC452I generic object

are Yellow-High and their AlertState-Priority cannot be changed. The values for

that pair are hardcoded in the asisp_Process_MVS_Event even if it seems like it

is possible to change them from the ResourceTypes panel.


v OA06529: The CA-7 message SMF0-20 regular expression definition is missing

from the CA7EventMap table. This prevents Tivoli Business Systems Manager

from posting this message to the CA-7 jobs.

v OA06542: A flood of closeout events coming from Tivoli Enterprise Console and

passing through the AgentListener caused a slowdown of performance.

v OA06616: Performance problems are caused by the stored procedure

asisp_uploadGetOSJobs always being the oldest transaction, running the DBCC

OPENTRAN and DBCC INPUTBUFFER commands.

v OA06639: A customer used the properly customized

REMOVE_MESSAGE_DESCRIPTION script to remove a large number of

message previously defined for CICS objects. It took a more than 4 hours to

remove 400 messages.

v OA06659: IMS shows Connecting , but never Connected. The GTM7912D

message which informs Tivoli Business Systems Manager that the OMEGAMON

is connected is handled properly for IMSS type objects.

v OA06723: Error: Violation of PRIMARY KEY constraint.

v OA06765: If a Tivoli task is run from the Tivoli Business Systems Manager

Operational Task menu item, the output is truncated.

v OA06821: Unable to monitor an OS resource. When the customer sets up the OS

Heart Beat Monitor feature, an exception to the OS stating no response received

from the OS resource causes the OS resource to receive a red alert.

v OA06823: The staged event loader log loses its carriage control and continues

logging on a single line.

v OA06829: The ASIMVSIPSenderSvc service is not connecting to the object server.

v OA06863: The remove_exception_type script did not remove the exception

added with the asisp_defineexceptiontype.sql script.

v OA06902: When using the Tivoli Business Systems Manager console on a

Windows XP system, the NetView web console does not start.

v OA06915: The maintenance window is slow when using the -E1 option on the

gtmmaint command and if the object has a lot of children.

v OA06921: The MVSUploadRule service stops processing when one of the upload

queues is filled.

v OA07000: There is a probem which prevents the sender queue status from being

shown. There is also a problem with the enqueue/dequeue age.

v OA07148: We need to allow EDI exceptions to go from one operating system to

another if they participate in a sysplex.

v OA07168: The gtmmaint command adds an extra hour to the start maintenance

time during the daylight saving time mode.

v OA07198: Several errors when using the scheduled tasks on a CICS.

v OA07209: When unknown SQL errors occur, the command thread terminates but

the service continues. The Agent Listener service does not process any new work

but appears to be active.

v OA07274: The deletednotedependent, deletedownedevent and alertstatehistory

tables are never cleaned up and their size increases. A housekeeping job is

requested to keep the size of the above tables low. Also, deletenotedependent

and the deletedownedevent need to be added to asisp_resetdb procedure.

v OA07401: In the original 2.1.1 code, any BSVs created prior to Fix Pack 1 have

the priority of DB2 and IMS objects of Ignore. Change the object values to

inherit from the event.


v OA07460: After an ACK event causes TakeOwnership of the related event on a

resource, if the CLOSE event arrives with another OPEN event, the original

ownership note is not closed because a new one is opened and closed instead.

v OA07463: If the subsource is longer than 64 chars then every threshold event

generates a new instance of the same object.

v OA07521: After upgrading to Tivoli Business Systems Manager 2.1.1 Fix Pack 6

plus LA Fixes required, there is partial information and then an error on the

displayobj output.

v OA07621: The following message is displayed after running the at_resetqueues

command: The specified job_name (’auto ticketing process output files’)

does not exist.

v OA07714: Restricted operators need Business Impact View.

v OA07748: When you try to stop the Object discovery service on NT4 server

CORE TNG, sometimes there is a DRWATSON trap on the im.exe module. The

problem seems to happen when the TNG Object Discovery service is stopped

while the status of any TNG object is being changed.

v OA07761: Operational tasks cannot be differentiated instance by instance

(instance id or display name), only by class.

v OA07763: On systems with a new installation (not migrated) of Framework 4.1.1,

IHSFFTAS.exe fails when it incorrectly attempts to load the libtas.dll instead of

the libtas60.dll.

v OA07833: The gtmmaint command cannot run on HP-UX even though it is the

supported platform for Event Enablement. Although the code exists for HP-UX,

it was never built.

v OA07853: The CICS discovery process job fails with Violation of primary key

constraint ’containment_pk’ error.

v OA07855: Cannot start the asilcommonlistener service.

v OA07918: During the upgrade of the history server from v1.5 to v2.1.1, the

historyserversetup.ksh fails due to SQL Server 2000 being installed in the

Program Files directory instead of a directory.

v OA07932: FLCI028E: Topology agent busy.

v OA08034: The automation icon is not removed from the console when the event

is closed.

v OA08082: Tivoli Business Systems Manager ETL inserts duplicate data points

into Tivoli Warehouse during daylight savings time change. The ETL inserts 25

data points for a day with 24 hours instead of 24 data points for the Line of

Business.

v OA08118: Take ownership database failure using non-English console. Error

message GTMJC0506E returns.

v OA08129: Incorrect output of CICS to DB2 connections in a CICSPlex

configuration.

v OA08244: The Eventviewer filter doesn’t work properly for the owned by column.

v OA08250: Automated Business Systems issues: BUSC to be added as a

supported class plus ABS errors when processing more than ten levels.

v OA08346: Select statement in asisp_processstagedautomationgroups causes

staged event loader log to be corrupted when verbose=1.

v OA08448: Receive violation of primary key error when running the abstest.ksh

command.

v OA08571: Tivoli Business Systems Manager is sending an event back to Tivoli

Enterprise Console that the event which was closed on Tivoli Enterprise Console

is closed by Tivoli Business Systems Manager.


v OA08813: Event Enablement (ihstdmai process) fails with core dump.

v OW57580: Bad performance and event handler deadlocks when large numbers

of events come from CICS on different MVS systems.


Support information

This section describes the following options for obtaining support for IBM

products:

v “Searching knowledge bases”

v “Obtaining fixes”

v “Contacting IBM Software Support” on page 46

Searching knowledge bases

If you have a problem with your IBM software, you want it resolved quickly. Begin

by searching the available knowledge bases to determine whether the resolution to

your problem is already documented.

Search the information center on your local system or

network

IBM provides extensive documentation that can be installed on your local

computer or on an intranet server.

An index is provided for searching the Tivoli Business Systems Manager library. If

you have Adobe Acrobat on your system, you can use the Search command to

locate specific text in the library. For more information about using the index to

search the library, see the online help for Acrobat.

Search the Internet

If you cannot find an answer to your question in the information center, search the

Internet for the latest, most complete information that might help you resolve your

problem. To search multiple Internet resources for your product, expand the

product folder in the navigation frame to the left and select Web search. From this

topic, you can search a variety of resources including:

v IBM technotes

v IBM downloads

v IBM Redbooks™

v IBM developerWorks®

v Forums and newsgroups

v Google

Obtaining fixes

A product fix might be available to resolve your problem. You can determine what

fixes are available for your IBM software product by checking the product support

Web site:

1. Go to the IBM Software Support Web site

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

2. Under Products A - Z, click I. When the list of products is displayed, click IBM

Tivoli Business Systems Manger for z/OS. This opens the product-specific

support site.


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

3. Under Search our support knowledge base for IBM Tivoli Business Systems

Manger for z/OS, type your text in the search field and click the Submit

button. You can limit your search by selecting Solve a problem, Download, or

Learn, or any combination. For tips on refining your search, click Search

assistance.

4. When you find the list of fixes, fix packs, or other service updates that you are

looking for, click the name of a fix to read the description and optionally

download the fix.

To receive weekly e-mail notifications about fixes and other news about IBM

products, follow these steps:

1. From the support page for any IBM product, click My support in the

upper-right corner of the page.

2. If you have already registered, skip to the next step. If you have not registered,

click register in the upper-right corner of the support page to establish your

user ID and password.

3. Sign in to My support.

4. On the My support page, click Edit profiles in the left navigation pane, and

scroll to Select Mail Preferences. Select a product family and check the

appropriate boxes for the type of information you want.

5. Click Submit.

6. For e-mail notification for other products, repeat Steps 4 and 5.

For more information about types of fixes, see the Software Support Handbook

(http://techsupport.services.ibm.com/guides/handbook.html).

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:

v 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 page

(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

(http://techsupport.services.ibm.com/guides/contacts.html) and click the

name of your geographic region.v 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 page (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 or, from other countries, go to


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

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

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

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

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

the contacts page of the IBM Software Support Handbook on the Web

(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.

Follow the steps in this topic to contact IBM Software Support:

1. Determine the business impact of your problem.

2. Describe your problem and gather background information.

3. Submit your problem to IBM Software Support.

Determine the business impact of your problem

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

you are reporting. Use the following criteria:

Severity 1 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 Significant business impact: The program is usable but is

severely limited.

Severity 3 Some business impact: The program is usable with less

significant features (not critical to operations) unavailable.

Severity 4 Minimal business impact: The problem causes little impact on

operations, or a reasonable circumvention to the problem has

been implemented.

Describe your problem and gather background information

When explaining 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:

v What software versions were you running when the problem occurred?

v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.

v Can the problem be re-created? If so, what steps led to the failure?

v Have any changes been made to the system? (For example, hardware, operating

system, networking software, and so on.)

v Are you currently using a workaround for this problem? If so, please be

prepared to explain it when you report the problem.

Submit your problem to IBM Software Support

You can submit your problem in one of two ways:

v Online: Go to the ″Submit and track problems″ page on the IBM Software

Support site (http://www.ibm.com/software/support/probsub.html). Enter

your information into the appropriate problem submission tool.

v By phone: For the phone number to call in your country, go to the contacts page

of the IBM Software Support Handbook on the Web

(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

Support information 47

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

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

Report (APAR). The APAR describes the problem in detail. Whenever possible,

IBM Software Support provides a workaround for you to implement until the

APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the

IBM product support Web pages daily, so that other users who experience the

same problem can benefit from the same resolutions.

For more information about problem resolution, see Searching knowledge bases

and Obtaining fixes.


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.

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.

Trademarks

IBM, the IBM logo, AIX, CICS, CICSPlex, DB2, developerWorks, eServer, IMS,

iSeries, Lotus, MVS, NetView, OMEGAMON, Passport Advantage, pSeries,

Rational, Redbooks, Tivoli, the Tivoli logo, Tivoli Enterprise Console, WebSphere,

z/OS, and zSeries are trademarks or registered trademarks of International

Business Machines 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, Windows NT, and Windows are registered 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, other countries, or both.

UNIX 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.


��

Printed in USA

GI11-4029-00

t l business systems manager -...

Documents