ibm tivoli business systems manager: release...

IBM Tivoli Business Systems Manager

Release NotesVersion 2.1.1

SC23-4841-01

��

NoteBefore using this information and the product it supports, read the information in Appendix B, “Notices”, on page 51.

March 2003

©This edition applies to Version 2, Release 1.1 of IBM Tivoli Business Systems Manager (product number5698–BSM) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2001, 2003. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Preface . . . . . . . . . . . . . . . vInformation Road Map . . . . . . . . . . . v

Accessing publications online. . . . . . . . vOrdering publications . . . . . . . . . . vi

Contacting customer support . . . . . . . . viParticipating in newsgroups . . . . . . . . . viConventions Used in This Document. . . . . . vii

Typeface Conventions . . . . . . . . . . viiOperating system-dependent variables and paths vii

Chapter 1. About the 2.1.1 Release . . . 1Overall Product Enhancements for 2.1.1 . . . . . 1Defects Fixed . . . . . . . . . . . . . . 3

Chapter 2. Installation and UpgradeNotes . . . . . . . . . . . . . . . . 7System and Software Requirements . . . . . . . 7Installation Notes . . . . . . . . . . . . . 7

IBM Tivoli Business Systems Manager WarehouseEnablement Pack . . . . . . . . . . . . 8

Chapter 3. Software Limitations,Problems, and Workarounds . . . . . . 9Software Limitations. . . . . . . . . . . . 9Software Problems and Workarounds . . . . . . 9Software Problems and Workarounds for the WebConsole. . . . . . . . . . . . . . . . 10

Chapter 4. Enhancements in 2.1.1 . . . 11ASG-Zeke Discovery Processing . . . . . . . 11

Bulk Discovery . . . . . . . . . . . . 11Event Discovery . . . . . . . . . . . . 14

Understanding Critical Resource Lists . . . . . 14Deleting Resources from a CRL. . . . . . . 14

Browsing Log and Data Files . . . . . . . . 15Using the Log File Browser Utility. . . . . . 15

Starting The Log File Browser Application . . 15Using the Data File Browser Utility . . . . . 15Starting The Data File Browser Application . . . 15

Resources and the Maintenance State . . . . . . 16Maintenance Window Messages . . . . . . 18

Stages of the Maintenance State . . . . . . 21Controlling the Number of Resources in theMaintenance State . . . . . . . . . . . 22

Viewing Resources in Maintenance Mode . . 22Working With Ownership of Notes and Events . . 23

Taking Ownership Without Removing Alerts . . 23Note Ownership Customization Issues . . . . 24

Intelligent Monitor for Tivoli NetView (IMfNetView) 25Performing a Bulk Upload . . . . . . . . 25Multiple Tivoli NetView Management Sources. . 26Launching the Tivoli NetView Console fromTivoli Business Systems Manager . . . . . . 27Troubleshooting Intelligent Monitor for TivoliNetView (IMfNetView) Failures . . . . . . 27

Chapter 5. Documentation Notes . . . 29Documentation Problems and Corrections . . . . 29

Chapter 6. Internationalization Notes 31Installation and Upgrade Notes. . . . . . . . 31Software Limitations, Problems and Workarounds 31Documentation Problems and Corrections . . . . 31Internationalization Issues . . . . . . . . . 31

Console. . . . . . . . . . . . . . . 32Intelligent Monitoring . . . . . . . . . . 33Untranslated Text in the User Interface . . . . 33

Appendix A. New and ChangedCommands and Messages for 2.1.1 . . 35New Commands . . . . . . . . . . . . 35

gtmmaint . . . . . . . . . . . . . . 36wimadiscovery . . . . . . . . . . . . 39

Changed Commands . . . . . . . . . . . 41ee_config . . . . . . . . . . . . . . 42wimasetup . . . . . . . . . . . . . 44

New Messages . . . . . . . . . . . . . 47Changed Messages . . . . . . . . . . . . 48

Appendix B. Notices . . . . . . . . . 51Trademarks . . . . . . . . . . . . . . 52

© Copyright IBM Corp. 2001, 2003 iii

iv IBM Tivoli Business Systems Manager: Release Notes

Preface

This document provides important information about IBM® Tivoli® BusinessSystems Manager Version 2.1.1. These release notes are the most currentinformation for the product and take precedence over all other documentation.

Information Road MapThe following documents are available in the IBM Tivoli Business SystemsManager library for Version 2.1.1:v Installation and Configuration Guide, GC32-0800-01, describes how to install IBM

Tivoli Business Systems Manager and do the initial configuration.v Release Notes, SC23-4841-01, describes what is new for this release and also

includes last minute changes and workarounds for IBM Tivoli Business SystemsManager.

The following documents are available in the IBM Tivoli Business SystemsManager library for Version 2.1:v Getting Started, GC32-0801-00, provides an introduction to Tivoli Business

Systems Manager.v Administrator’s Guide, GC32-0799-00, describes administrative tasks for Tivoli

Business Systems Manager.v User’s Guide, GC32-0798-00, describes how to use Tivoli Business Systems

Manager to monitor the resources in your enterprise.v Messages, GC32-0797-00, describes the messages for Tivoli Business Systems

Manager.v Diagnosis Guide, SC23-4840-00, describes troubleshooting problems that might

occur with Tivoli Business Systems Manager.

Accessing publications onlineThe product CD contains the publications that are in the product library. Theformat of the publications is PDF, HTML, or both. To access the publications usinga Web browser, open the infocenter.html file. The file is in the appropriatepublications directory on the product CD.

IBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Software InformationCenter Web site. The Tivoli Software Information Center is located at the followingWeb address:

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Click the IBM Tivoli Business Systems Manager link to access the product library.

Note: If you print PDF documents on other than letter-sized paper, select the Fit topage check box in the Adobe Acrobat Print dialog. This option is availablewhen you click File → Print. Fit to page ensures that the full dimensions of aletter-sized page print on the paper that you are using.

© Copyright IBM Corp. 2001, 2003 v

http://publib.boulder.ibm.com/tividd/td/tdprodlist.html

Ordering publicationsYou can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, see the following Web site for a list of telephone numbers:

http://www.ibm.com/software/tivoli/order-lit/

Contacting customer supportIf you have a problem with any Tivoli product, refer to the following IBM SoftwareSupport Web site:

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

If you want to contact customer support, see the IBM Software Support Guide at thefollowing Web site:

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

The guide provides information about how to contact IBM Software Support,depending on the severity of your problem, and the following information:v Registration and eligibilityv Telephone numbers and e-mail addresses, depending on the country in which

you are locatedv Information you must have before contacting IBM Software Support

Participating in newsgroupsUser groups provide software professionals with a forum for communicating ideas,technical expertise, and experiences related to the product. They are located on theInternet, and are available using standard news reader programs. These groups areprimarily intended for user-to-user communication, and are not a replacement forformal support.

To access a newsgroup use the following instructions.

If you use Netscape Navigator as your browser:1. Open a Netscape Navigator browser.2. From the Edit menu, click Preferences. The Preferences window is displayed.3. In the Category view, click Mail & Newsgroups to display the Mail &

Newsgroups settings.4. Select the Use Netscape mail as the default mail application check box.5. Click OK.6. Close your Netscape Navigator browser and then open it again.

vi IBM Tivoli Business Systems Manager: Release Notes

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi

http://www.ibm.com/software/tivoli/order-lit/


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

7. Cut and paste this newsgroup addressnews://news.software.ibm.com/ibm.software.tivoli.business-systems-managerinto the browser Address field, and press Enter to open the newsgroup.

If you use Microsoft® Internet Explorer as your browser:1. Open an Internet Explorer browser.2. From the Tools menu, click Internet Options.3. On the Internet Options window, click the Programs tab.4. In the Newsgroups list, click the Down Arrow and then click Outlook Express.5. Click OK.6. Close your Internet Explorer browser and then open it again.7. Cut and paste this newsgroup address

news://news.software.ibm.com/ibm.software.tivoli.business-systems-managerinto the browser Address field, and press Enter to open the newsgroup.

Conventions Used in This DocumentThis document uses several conventions for special terms and actions, operatingsystem-dependent commands and paths, and command syntax.

Typeface ConventionsThe following typeface conventions are used in this document:

Bold Lowercase and mixed-case commands, command options, andflags that appear within text appear like this, in bold type.

Graphical user interface elements (except for titles of windows anddialogs) and names of keys also appear like this, in bold type.

Italic Variables, values you must provide, new terms, and words andphrases that are emphasized appear like this, in italic type.

Monospace Commands, command options, and flags that appear on a separateline, code examples, output, and message text appear like this, inmonospace type.

Names of files and directories, text strings you must type, whenthey appear within text, names of Java™ methods and classes, andHTML and XML tags also appear like this, in monospace type.

Operating system-dependent variables and pathsThis document uses the UNIX® convention for specifying environment variablesand for directory notation.

When using the Windows® command line, replace $variable with % variable% forenvironment variables and replace each forward slash (/) with a backslash ( \) indirectory paths.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

Preface vii

news://news.software.ibm.com/ibm.software.tivoli.business-systems-manager

news://news.software.ibm.com/ibm.software.tivoli.business-systems-manager

viii IBM Tivoli Business Systems Manager: Release Notes

Chapter 1. About the 2.1.1 Release

This chapter lists new features for IBM Tivoli Business Systems Manager 2.1.1.

Overall Product Enhancements for 2.1.1Overall product enhancements include:v ASG-Zeke discovery processing. See “ASG-Zeke Discovery Processing” on

page 11 for more information about this enhancement.v Critical resource lists. See “Understanding Critical Resource Lists” on page 14 for

more information about this enhancement.v Browsing log and data files. See “Browsing Log and Data Files” on page 15 for

information about this enhancement.v Resources and the maintenance state. See “Resources and the Maintenance State”

on page 16 for information about this enhancement.v Note ownership customization. See “Working With Ownership of Notes and

Events” on page 23 for information on this enhancement.v Intelligent Monitor for Tivoli NetView® (IMfNetView) discovery. See “Intelligent

Monitor for Tivoli NetView (IMfNetView)” on page 25 for more information.v Event enablement support of IBM Tivoli Monitoring by way of the Tivoli

Enterprise Console® ihstztec exit. This exit maps the Tivoli Enterprise Consoleslots contained in an IBM Tivoli Monitoring event to values equivalent to thosethat would have been sent by Tivoli Distributed Monitoring Version 3.7.1. Thisenables the customer to use the ihstztec exit for both IBM Tivoli Monitoring andTivoli Distributed Monitoring Version 3.7 events.

v An optional -q flag has been added for the ihstetec command. The ihsteteccommand queries Tivoli Management Environment® for the label of a resource.The -q flag indicates that Tivoli Management Environment should not bequeried for the label.

v Table-based enumerations; Problem Ticket and Change Request performanceenhancements.An option is provided for loading large volumes of drop down list values(enumerations) into the Problem Ticket and Change Request console displays. Ifyour cumulative total of drop-down list values exceeds 100 entries, this optionprovides a considerable performance improvement.For configuration details see the ″Program User Exist and Code Samples″document at the following address:http://www.ibm.com/software/sysmgmt/products/support/From the Select a Product drop-down list, click IBM Tivoli Business SystemsManager and click GO. From the Self Help group, click Solutions -> ProgramUser Exits Guide and Code Samples.

v IMS™ Enhancements:– Improved processing of IMS Connect messages oriented to one datastore only– Improved error handling when IMS OTMA Call Interface SVC is not enabled– IMS Connect 1.2 regions now discovered at NetView startup– Output from IMS commands issued from Tivoli Business Systems Manager

console improved when no output is received from IMS– Improved IMS log and log archive job monitoring

© Copyright IBM Corp. 2001, 2003 1


– Improved IMS subsystem monitoring– Improved rediscovery of external subsystems– Reliance on OTMA and MCS/EMCS during IMS rediscovery reduced– OTMA Call Interface/MCS no longer used for program, transaction, and

database polling monitorsv A new implementation of IMfAppMgrSv for NetIQ AppManager, which is

server based instead of agent based. Only one copy of this intelligent monitor isrequired to monitor objects under a particular NetIQ managed server. A newcommand, wimadiscovery, is used to perform bulk and manual deltadiscoveries against the NetIQ AppManager repository. See Appendix A, “Newand Changed Commands and Messages for 2.1.1”, on page 35 for moreinformation about the wimadiscovery command.

v The wimasetup command has added new options for the event enablementprocess. See Appendix A, “New and Changed Commands and Messages for2.1.1”, on page 35 for more information.

v Two new options have been added to the ee_config command. See Appendix A,“New and Changed Commands and Messages for 2.1.1”, on page 35 for moreinformation.

v New messages:– GTMCP0013I– GTMCP0014I– GTMCP0015I– GTMCP0016E– GTMJC0704E– GTMZE0018E– IHS604I– IHS605I– IHS683W– IHS811I– IHS812E

See Appendix A, “New and Changed Commands and Messages for 2.1.1”, onpage 35.

v Changed messages:– GTMCP0036I– IHS321I– IHS413E– IHS426E– IHS452I– IHS487E to IHS487W– IHS489I– IHS727E– IHS742I– IHS751I– IHS752I

See Appendix A, “New and Changed Commands and Messages for 2.1.1”, onpage 35.

v Deleted messages:– GTMJC0572E– IHS341I

2 IBM Tivoli Business Systems Manager: Release Notes

Defects FixedThe following defects have been corrected:v OA01552: Object created by way of Global Enterprise Manager DM MAP or

Global Enterprise Manager GEN POD are not listedv OA01579: Health monitor SQL response times windows often shows three

entries as redv OA01592: Orphaned event caused by Delete Old Exceptionsv OA01623: Omegamon DB2® exceptions not being reportedv OA01624: Health monitor MVS™ status view is not getting all data about queuesv OA01641: Events that are acknowledged in Tivoli Enterprise Console and have

the same timestamp in the agent listener are discarded byGEMSP_PROCESSAPMGENERICMSG

v OA01649: Program user exit large enumeration list caused the system to runvery slowly, making the response time very slow

v OA01693: TWS jobs disappearing from view batch management summaryv OA01716: In reporting system some objects are missing from the physical tree

objects option comparing them to the consolev OA01766: SEL pause when deadlock + warning messagev OA01781: Properties Current Events date column filter doesn’t work and breaks

the other columns filtersv OA01818: Bulk SC closes get tossed by SELv OA01871: Staged event loader chosen as deadlock victimv OA01919: Missing line of business links in business impact viewv OA01926: Make the Resolution field visible on the closure screen invisiblev OA01936: Tivoli Enterprise Console Events-->Common Listener w/CIDv OA01943: Too many operational tasks, they are not displayed properly because

you can not see them allv OA02027: Error in a propagation of an event on a line of business with priority

set at IGNORE.v OW54142: Log browser utility does not workv OW54406: Icons: Batch schedule Set shows general icon in Reporting System

Hyperviewv OW54845: IMS discovery load job errorv OW54955: Bringing down a CDRM, the object is displayed in yellow state, and

the parent object is redv OW55278: Right mouse on IMS TM/DB to display IMS resources changes the

name to an error messagev OW55373: Completed Schedule Poll job is not marked as a CA-7 job,

documentation should reflect that it can be used for CA7v OW55441: Automation events should not undelete objects in Tivoli Business

Systems Manager databasev OW55471: Error in MVS event handler logv OW56158: ATTACHDATABASES.SQL should verify that the database servers

specified are validv OW56191: Status of a region changes to inactive when an ACCESS02 message is

received upon registration into a Sysplexv OW56278: Integration fields table is never deleted nor purged

Chapter 1. About the 2.1.1 Release 3

v OW56279: Job restore databases for reporting system is failing on step 1v OW56312: Patch 35 implemented system managed storage samples, creates

system managed storage complex - PLEX1, resets system managedstorageinterval registration profile

v OW56332: PA log error VIOLATION OF PRIMARY KEY CONSTRAINT’ASH_PK’. CANNOT INSERT DUPLICATE KEY IN OBJECTALERTSTATEHISTORY

v OW56385: Error in the CICS® job process pending state transitionsv OW56387: Staged event loader pauses when CICS message DFHAC2236 has an

abend code containing the single quotation signv OW56487: Data base error :515 < CANNOT INSERT THE VALUE NULL INTO

COLUMN ’CHILD_OBJ_NAME’, TABLE TEMPDB.DBO. IMIRv OW56493: Problems in CICSPlex® discoveryv OW56524: After patch 35, if you take ownership of an event, and a repeating

event comes in, it is system closedv OW56616: Health monitor client should be able to run on a desktop that doesn’t

have administrative access to the health monitor serverv OW56634: SQL memory usage increases quickly when processing staged Zeke

eventsv OW56847: Operators can edit menu items in the reporting systemv OW56872: Error installing Tivoli Business Systems Manager V2.1 health monitorv OW56874: Cannot override the timeout value in GEMSP_INVOKETASK.SQL

using the SystemConfiguration tablev OW56886: TME® task authentication doesn’t check for passwordv OW56888: Owned event can be closed by operatorv OW56889: The selected events are deselected by the refreshv OW56904: When saving changes to an existing workspace, this clears the setting

AUTOMATICALLY OPEN THIS WORKSPACE ON CONSOLE STARTUPv OW56932: Two users allowed to open TSD tickets on the same eventv OW57090: Violation of primary key constraintv OW57144: Object registration process hangs when too many traps definedv OW57169: Abstest -e must be run for all the objects already present in the

databasev OW57174: Problem renaming line of business linked objectsv OW57183: Delete unused DB2 data sharing groupsv OW57191: Line of business reports timeout from reporting systemv OW57205: Batch job to line of business doesn’t workv OW57271: Mempattern column in the table GEM_INSTFILTERING has a

maximum length of about 65 charactersv OW57273: Code should be change to support GRBE changes and avoid SEL

backlogv OW57321: MakeMVSComponents.ksh creates wrong registry entriesv OW57324: Multiple exceptions of same type are stowed in the event tablev OW57493: When you delete a batch job and you try to create another with the

same name, you get an error messagev OW57570: CICS scheduled state database jobs not deleted when the CICS region

gets deleted


v OW57583: Tivoli Business Systems Manager propagation backlog...events taketoo long to show on the line of business

v OW57594: Tivoli Business Systems Manager 2.1 with EDI when object namelonger than 16 chars

v OW57619: Parameter DesiredStateId in a scheduled task newly created is clearedwhen checking the task again after creation

v OW57692: Users with Tivoli Business Systems Manager Operator authority candelete components

v OW57701: Problem when customer runs bulk upload on NetView distributedserver

Chapter 1. About the 2.1.1 Release 5

Chapter 2. Installation and Upgrade Notes

This chapter describes changes and upgrade notes for installing IBM TivoliBusiness Systems Manager.

System and Software RequirementsThe IBM Tivoli Business Systems Manager: Installation and Configuration Guide liststhe system and software requirements.

Installation NotesThe following installation notes apply to Tivoli Business Systems Manager 2.1.1:v Problem: Because the release cycles for the Tivoli Business Systems Manager

2.1.1 product and the National Language Support resources for Tivoli BusinessSystems Manager 2.1.1 product are not simultaneous, you can initially installonly the Tivoli Business Systems Manager 2.1 National Language Resources withthe Tivoli Business Systems Manager 2.1.1 product.When installing Tivoli Business Systems Manager 2.1 National LanguageResources on a Tivoli Business Systems Manager 2.1.1 system, the installationprogram for the National Language Resources does not correctly detect theinstallation location of the Tivoli Business Systems Manager 2.1.1 Console.Instead, you are presented with a default installation location.Workaround: Do one of the following:– Manually enter the correct installation location for the Console in the

directory input field provided.– Click the Browse button to the right of the directory input field and select the

correct installation location for the Console. Then, continue the installationprocess for the National Language Resources as usual.

Once the National Language Support is available for Tivoli Business SystemsManager 2.1.1, this workaround will no longer be necessary.

v The Tivoli Business Systems Manager installation installs a copy of the IBMObject REXX program on the Tivoli Business Systems Manager database server.If this system does not currently have a copy of the IBM Object REXX program,the PATH environment variable must be updated to include this program. TheIBM Object REXX program is installed in the %SystemDrive%\ProgramFiles\ObjREXX directory. After updating the PATH environment variable, themachine must be restarted.

v When installing the console onto a non-English system, you no longer need toopen a command prompt and enter:set JAVA2D_USEAWTFONTS=0

You can start the installation by clicking setup.exe from the install CDs.v Silent installation and silent uninstall of the console are not supported on Linux.v To upgrade the console from 2.1 to 2.1.1 on the AIX® and Solaris Operating

Environment platforms, run the following command to remove the 2.1 codebefore installing the 2.1.1 version:_itbsmUninst/uninstall

v Upgrading the console from 1.5 to 2.1.1 is not supported on Linux.


v If the same DB2 subsystem is to be monitored from different NetView systemsand these NetView systems have different NetView started task user IDs, thenthe GRANT step in IHSBTBND must be run separately using each of theNetView started task user IDs as the authorized IDs. Refer to the IBM TivoliBusiness Systems Manager: Installation and Configuration Guide for moreinformation.

v Problem: Some Tivoli Business Systems Manager services might not be removedduring the uninstall process.Workaround: If any Tivoli Business Systems Manager services are present afteruninstalling the Tivoli Business Systems Manager program and restarting, runthe following command from a korn shell prompt to remove them:sclist | awk ’/ASI/ {system("sc delete " $2)}’

IBM Tivoli Business Systems Manager Warehouse EnablementPack

IBM Tivoli Business Systems Manager provides a set of extract, transform, andload (ETL) utilities to extract and move data from IBM Tivoli Business SystemsManager to a central Tivoli Enterprise™ Data Warehouse database. These utilitiesare shipped in the etl directory on CD2 (Tivoli Enterprise Console eventenablement, fonts, IM monitors, etls).

Previously, the ETL was shipped with the Tivoli Enterprise Data Warehouseproduct and required a patch for the IBM Tivoli Business Systems Manager 1.5product. The version of the ETL shipped with IBM Tivoli Business SystemsManager 2.1.1 replaces the ETL shipped with Tivoli Enterprise Data Warehouseand the patch is not needed for the 2.1.1 version of IBM Tivoli Business SystemsManager.

Information about the ETL and installation instructions are on the second CD,under etl\gtm\pkg\v210\doc.


Chapter 3. Software Limitations, Problems, and Workarounds

This chapter describes software limitations, problems, and workarounds.

Software LimitationsThe following software limitations are present in Tivoli Business Systems Manager2.1.1:v Creating business systems could affect all consoles that are logged-on at the

time. It is recommended that you create business systems during off-peak hours.v The maximum number of resources to drag and drop or to copy and paste at

one time is 20.v Having feeds coming from more than one Resource Object Data Manager

(RODM) could present some problems. Examples of problems are:– When you discover SNA resources from one operating system, this works

correctly. Then, when you attempt to discover SNA resources from a secondoperating system, the resources of the first system disappear.

– Because there is a single folder for Graphic Monitor Facility host subsystem(GMFHS) resources, you can assign only one managing operating system.While this might or might not preclude you from discovering GMFHSresources from a second RODM, there will likely be a problem with namecollisions.

Software Problems and Workaroundsv Problem: When CICS alerts are coming in through the PPI before the CICSPlex

folder is created, the objects are created under the OS folder. After the CICSPlexfolder is created and bulk discovery runs, it does not pick up the already createdobjects under the OS and does not move the discovered objects.Workaround: Create the CICSPlex folder before the pump has a connection.

v Problem: After stopping the Tivoli Business Systems ManagerMVSUPLoadRuleSvc service on Windows NT®, an access violation could occur.Workaround: Perform the following steps:1. Copy the start_services.ksh script from the Tivoli Business Systems

Manager installation directory of the event handler server, which is usually<drive>:\Tivoli\Manager\bin to a start up folder, which is usually<drive>:\WINNT\Profiles\All Users\Start Menu\Programs\Startup.

2. Shut down and reboot the machine.3. Log on and verify that all of the services dependent on DBValidater started

successfully.v Problem: If the event handler server is running Windows NT (rather than

Windows 2000), after restarting the event handler server, theASIMVSUPloadRuleSvc service might timeout while waiting for theASIDBValidater service.Workaround: You can check for this by issuing the following command:sclist | grep -i asi

Both ASIMVSUploadRuleSvc and ASIDBValidater should be running. IfASIMVSUploadRuleSvc is not running, start it with the following command:


sc start ASIMVSUPloadRuleSvc

For future restarting of the event handler server, copy the start_services script,which is located in the \bin subdirectory, to the All Users Startup folder onWindows NT.

v Problem: When running the MakeMVSComponents shell script, predefinedspecial characters cause failures.Workaround: Parameters used in MakeMVSComponents components must bespecified in uppercase.

v Problem: Processing a full IMS discovery concurrent with the processing of IMSevents could cause the full IMS discovery to fail due to deadlocking issues.Workaround: Pause or stop the staged event loader before performing a full IMSdiscovery, then continue or start the staged event loader after the full IMSdiscovery processing completes.

Software Problems and Workarounds for the Web Consolev Problem: For some actions the Web console does not show processing feedback.

These actions are:– Actions that are performed from the business impact tree– Opening and closing problem tickets

Workaround: Move the mouse pointer over the browser title bar. Doing thisshows the hourglass icon while an action is processing.

v Problem: Notebook tabs might not display when you:– Create or edit a filter– Display resource properties

Workaround: Click the refresh button on the bottom right of the consolewindow.

v Problem: When you create or update a note, you might get an error messagesaying the Subject or the Resolution field is required even through you entered avalid value in the field.Workaround: Disregard the message and click OK again to complete the action.

v Problem: Text does not display correctly in entry fields or ID=xxxxxxxx isdisplayed next to the entry field. This can occur if text in the entry field containsHTML characters, such as the less than and greater than symbols (< and >). Thetext displays correctly when the task is first opened. However if you switch toanother task and then switch back, the text might not display correctly.This problem does not cause data that is maintained by the server to bedamaged.Workaround: Close and then reopen the task.

v Problem: Data in some of the columns on the child events page of the resourceproperties does not display correctly.Workaround: None

v Problem: The workspace support that is listed on the portfolio is part ofPresentation Services and is not supported by the Web console.Workaround: None


Chapter 4. Enhancements in 2.1.1

This chapter includes detailed information about some of the enhancements addedto Tivoli Business Systems Manager version 2.1.1. The following enhancements aredetailed in this section:v “ASG-Zeke Discovery Processing”v “Understanding Critical Resource Lists” on page 14v “Browsing Log and Data Files” on page 15v “Resources and the Maintenance State” on page 16v “Working With Ownership of Notes and Events” on page 23v “Intelligent Monitor for Tivoli NetView (IMfNetView)” on page 25

ASG-Zeke Discovery ProcessingZeke data feed has the same object bulk and delta discovery process as CA-7. Bulkdiscovery is based on the Zeke report file sent from the mainframe to Windows NTusing ASIMVSIPListenerSvc service. A bcp file will be created in a temp directoryon a Tivoli Business Systems Manager database server and an entry inDiscoveryBatch will be inserted for this Zeke format type.

Bulk DiscoveryBulk discovery is performed by the following steps:1. Generate Zeke reports. More then one report can be generated under different

conditions. A report file can be marked as KEY, non-KEY, or EXCLUDE withthe designated priority in the next parsing step. The report files marked asEXCLUDE are used as object creation filters.

2. Parse report files. The following information is extracted from report filesusing the ZEKEPARS REXX program (TBSM.SGTMEXEC):v APPLICATION_NAMEv EARLY_TIMEv EVENT_NAMEv EVENT_NUMBERv GROUP_IDv HIT_DATEv SELDATEv LATE_TIMEv MUST_ENDv NOT_AFTERv SCHEDULE_TIMEv SYSTEMv VERSIONv AVERAGE_DURATIONv JOBNAMEv KEY_FLAGv EXCLUDE_FLAGv PRIORITY

The List Events and List Plan reports will be parsed by the GTMZEKED REXXprogram (TBSM.SGTMEXEC). This program uses up to three parameters:v The first parameter, which is required, is the input dataset name.


v The second parameter, which is optional, can be KEY, EXCLUDE or nothing.KEY identifies ″KEY″ jobs in this input file. EXCLUDE indicates that youwant to exclude the jobs in this input file. Supplying no parameter indicatesthat jobs in this input file are non-KEY.

v The last parameter is used to prioritize the reports. This parameter can havea value of any whole number (for example, 1, 2, or 7).

Suppose job TESTJOBA is included in the report for all Zeke jobs, in the reportfor key jobs, and in the report for exclude jobs. If you give a priority of 1 to thereport containing all Zeke jobs, a priority of 2 to the report containing key jobs,and a priority of 3 to the report containing the list of jobs to exclude, thenTESTJOBA will be excluded from being monitored by Tivoli Business SystemsManager because the exclude report has the highest priority.

For example, if Tivoli Business Systems Manager needs to monitor all Zekejobs, then run a Zeke Schedule of Events report(PREFIX.ZEKE.ZEKESSN.INPUT1) for all jobs monitored by Zeke. Assign thisreport a priority of 1. If some of these jobs are considered ″KEY″, run anotherreport (PREFIX.ZEKE.ZEKESSN.INPUT2) containing only these ″KEY″ jobs.Assign this report a priority of 2. If some Zeke jobs need to be excluded frombeing monitored by Tivoli Business Systems Manager, run anotherreport(PREFIX.ZEKE.ZEKESSN.INPUT3) containing only these excluded jobs.Assign that report a priority of 3. If jobs with the same name are in all threereports, they will be excluded from being monitored by Tivoli Business SystemsManager because the exclude report has the highest priority.

For the example, the parse program (GTMZEKED) would be called with thefollowing parameters by report type:

Table 1.

Zeke Input Dataset Parameters Type ofReport

%GTMZEKED PREFIX.ZEKE.ZEKESSN.INPUT1 parameters List Events

%GTMZEKED PREFIX.ZEKE.ZEKESSN.INPUT2 1 List Plan

%GTMZEKED PREFIX.ZEKE.ZEKESSN.INPUT3 KEY 2 List Plan

%GTMZEKED PREFIX.ZEKE.ZEKESSN.INPUT4 EXCLUDE 4 List Plan

When Tivoli Business Systems Manager Zeke discovery is done, jobs in thePREFIX.ZEKE.ZEKESSN.INPUT3 dataset are marked as KEY jobs (in the TivoliBusiness Systems Manager GUI) and all other jobs are treated as NON-KEY.Jobs in the PREFIX.ZEKE.ZEKESSN.INPUT4 dataset will not be shown in TivoliBusiness Systems Manager.

The information discovered in PREFIX.ZEKE.ZEKESSN.INPUT1 is displayed inTivoli business system views in the Tivoli Business Systems Manager GUI.

3. Send Zeke.<subsystem name>.bcp to Windows NT in text EBCDIC formatusing ASIMVSIPListenerSvc. This file will be stored in the<TivoliManager>\data\zeke directory. It also can be verified fromDiscoveryBatch table.

4. Load Zeke.<subsystem name>.bcp into database by the SQL scheduled tasknamed ZEKE Discovery Load. The SQL Scheduled task (ZEKE Discovery


Load) will load the data into a pre_zeke_bcp table. The old data inpre_zeke_bcp table will be deleted before loading the new data with the ZEKEDiscovery Load job.Before running the ZEKE Discovery Process job, you should create all schedulesthat include EVENT_DISCOVER. If any schedule set was not created, the list ofnon-created schedule sets will be shown in the job history and the transactionwill be rolled back.

5. Setup KEY/non-KEY object specifications and filters in Tivoli BusinessSystems Manager database. Tivoli Business Systems Manager can exclude thespecific object creation by schedule set, schedule, and batch-job namingconversions in bulk object discovery. The naming conversions are setup bycustomers either using report files or BJDiscoveryFilter_Lookup table of theTivoli Business Systems Manager database. The exclusive processing rule isapplied to both KEY/non-KEY categorization and naming convention filtersaccording to the priority from high to low.For example, suppose one naming convention (test1) has KEY_FLAG = 1 andpriority 3, another naming convention (test2) has EXCLUDE_FLAG = 1 andpriority = 2, a job AAA is qualified to both test1 and test2, and then job AAAwill be created as KEY job followed the high priority rule. If a job qualifies toboth KEY_FLAG = 1 and EXCLUDE_FLAG = 1 specification with the samepriority, the EXCLUDE_FLAG will be considered first.All the entries in BJDiscoveryFilter_Lookup for Zeke data source are used onbulk object discovery, including exclude flag and key flag. For event objectdiscovery, only exclude flag with specific job-name conversions are usedbecause events do not have any information about schedule set name andschedule name. For example, if the BJDiscoveryFilter_Lookup table has theentries shown in Table 2, then all entries are used for bulk object discovery andonly the third row is subject to event object discovery:

Table 2. Example of BJDiscoveryFilter_Lookup Table

name_schedule_set name_schedule name_job data_source enabled priority excluded key_flag

%test% %test% %test% ZEKE 1 2 1 0

%test% %test% %test% ZEKE 1 3 0 1

ALL ALL %TEST% ZEKE 1 1 1 0

ALL ALL %TEST% ZEKE 1 2 0 1

The _SetBJDiscoveryFilter and _GetBJDiscoveryFilters methods are definedto set and get data from the BJDiscoveryFilter_Lookup table in Tivoli BusinessSystems Manager database, respectively. For more information about usingthese two methods, refer to the IBM Tivoli Business Systems Manager: Installationand Configuration Guide. Initially there is no entry in theBJDiscoveryFilter_Lookup table for Zeke data source.

6. Setup System Configuration Variable. A system configuration variable,autoDiscoveryFlag, is defined for the purpose of filtering Zeke objects andevents.The default value for autoDiscoverFlag is 1. This value indicates that jobs whichare not discovered during a bulk discovery process will be discovered as Keyjobs. Those jobs will be placed under UNKNOWN schedule ofEVENT_DISCOVER schedule set during event processing.If autoDiscoverFlag = 0, objects will not be created based on their events and theevents will be sent to the Zeke_autid_events table.

Chapter 4. Enhancements in 2.1.1 13

The _SetSystemConfiguration and _GetSystemConfiguration methods aredefined to set and get this information, respectively. For more informationabout using these two methods, refer to the IBM Tivoli Business SystemsManager: Installation and Configuration Guide.

7. Discover objects by SQL schedule task ZEKE Discovery Process. Thescheduled task (ZEKE Discovery Process) processes the data in pre_zeke_bcptable and create the objects. The SYSTEM column is used as the schedule setname and the APPLICATION column is used as the schedule name.The following rules are in effect during bulk discovery process:v Jobs are exclusively evaluated according to the defined priorities from high

to low.v If objects have the same priority, the EXCLUDE flag is evaluated first and

then the KEY flag.v Only the most recent job is created for Multi-scheduled Jobs in different

days.v Only one object is created for jobs running multiple times a day. The job with

the earliest SCHEDULE_TIME is used to create the object.

Event DiscoveryIf an object does not exist and autoDiscoveryFlag = 1, the object is created in anUNKNOWN schedule under EVENT_DISCOVER schedule set. These objects willbe remapped to the designated place, if it is in the report file in the next bulkdiscovery process.

Understanding Critical Resource ListsYou monitor and work with the resources that are in a folder called MyResources -userid (where userid is your user ID). MyResources - userid is your critical resourcelist (CRL). A console administrator creates CRLs from the resources that are in theconsole database.

Restricted Operators cannot change their CRL. Only Super Administrators areauthorized to add resources to, and delete resources from, Restricted OperatorCRLs.

Operators are not allowed to alter existing Business Systems. Operators can addresources to their CRL by pasting or dropping resources onto their MyResources -userid folder (the root resource of their CRL). These resources can only be added asimmediate children of the MyResources - userid folder.

Deleting Resources from a CRLOnly Super Administrators are authorized to delete resources from RestrictedOperator CRLs.

Operators can delete resources from their CRL, but only if the resource is a firstlevel child of their MyResources - userid folder. Deleting a resource removes theresource and all of its children from the CRL.


Browsing Log and Data FilesTwo utilities are shipped with Tivoli Business Systems Manager, which you can useto browse the log (*.log) and data (*.dat) files. These are described in the followingsections:v “Using the Log File Browser Utility”v “Using the Data File Browser Utility”

Using the Log File Browser UtilityThe log file browser application is used to view log files generated by TivoliBusiness Systems Manager base services. The log file browser files are located inthe <TivoliManager>\log folder on any machine on which the Tivoli BusinessSystems Manager base services have been installed. This application is usedprimarily for diagnostics and debugging. It provides the following functions:v Locating log files on both local and remote drivesv Viewing multiple log files at the same timev Filtering log views by message type, and date and time rangesv Saving the log view to a filev Viewing and setting registry log levelsv Printing log views to a default printerv Navigating to the default log folder at startupv Viewing both standard and nonstandard log files

Starting The Log File Browser ApplicationTo start the log file browser, run the asilogbrowser.exe file from the<TivoliManager>\log folder where <TivoliManager> is the drive and folder whereTivoli Business Systems Manager is installed. When the application starts, it locatesthe install folder for Tivoli Business Systems Manager and opens the standard logfolder. For field information on the interfaces provided with the log file browser,see the online help.

Using the Data File Browser UtilityThe data file browser application is used to view data files generated by TivoliBusiness Systems Manager base services. The data file browser files are located inthe <TivoliManager>\log folder on any machine on which the Tivoli BusinessSystems Manager base services have been installed. This application is usedprimarily for diagnostics and debugging. It provides the following functions:v Locating data files on both local and remote drivesv Viewing multiple data files at the same timev Filtering data views by format type, action type, and date and time rangesv Saving the data view to a filev Printing data views to a default printerv Navigating to the default data folder at startup

Starting The Data File Browser ApplicationTo start the data file browser, run the datfilebrowser.exe file from the<TivoliManager>\log folder where <TivoliManager> is the drive and folder whereTivoli Business Systems Manager is installed. When the application starts, it locatesthe install folder for Tivoli Business Systems Manager and opens the standard datafolder. For field information on the interfaces provided with the data file browser,see the online help.


Resources and the Maintenance StateThe maintenance window provides a way to determine which resources are inmaintenance mode. This is important because when resources are in maintenancemode, Tivoli Business Systems Manager does not generate alerts for any eventsreceived on these objects.

Resources are put in maintenance mode using the GTMMAINT generic messageevent. Once you specify the target resource object, options provide the ability toplace the following into maintenance mode:v The target object and its children in the physical treev The target object, only if it exists in the business systemv The target object and its children if they each exist into a business system

The gtmmaint command also enables the maintenance window function. SeeAppendix A, “New and Changed Commands and Messages for 2.1.1”, on page 35for more information about the gtmmaint command.

For diagnostic purposes, the MaintTrueState table maintains a list of all resourcesthat are either currently in maintenance state, or are scheduled to go intomaintenance state. Table 3 provides field information for the MaintTrueState table.

Table 3. MaintTrueState

Column name Data type Null? Description

enabled TINYINT not NULL v 1 (one) indicates that the resource isin maintenance mode

v 0 (zero) indicates that the resource isnot in maintenance mode

originCID ClassID not NULL For future use

originID ObjID not NULL For future use

cid ClassID not NULL (cid, id) Primary key of resource in orscheduled to be in maintenance mode

id ObjID not NULL ObjID of resource in, or scheduled to bein, maintenance mode

baseCID ClassID not NULL ClassID of target resource (used whencid column contains LOB)

baseID ObjID not NULL ObjID of target resource (used when cidcolumn contains LOB)

startTime DATETIME not NULL Timestamp that determines when theresource is to go into maintenancemode

endTime DATETIME NULL Timestamp that determines when theresource is to be removed frommaintenance mode. A value of NULLindicates that the resource shouldremain in maintenance mode until aGTMMAINT OFF message is received.

AlertState TINYINT NULL Current calculated AlertState (used torestore the AlertState when the resourceis removed from maintenance mode)


Table 3. MaintTrueState (continued)

Column name Data type Null? Description

CurrentState INT NULL Current calculated CurrentState (usedto restore the AlertState when theresource is removed from maintenancemode)

messageText NVARCHAR(225) NULL The GTMMAINT ON message text thatwas last applied to the resource

For diagnostic purposes, the MaintTrueChildEvent table maintains all the childevents received by the objects currently in maintenance mode. This enables thechild events to be processed when the objects are no longer in maintenance mode.Table 4 provides field information for the MaintTrueChildEvent table.

Table 4. MaintTrueChildEvent

Column name Data type Null?

Id ObjID Not NULL

Name ObjName Not NULL

description NVARCHAR(255) NULL

deleted TINYINT Not NULL

_AlertState INT Not NULL

_ChildCID ClassID Not NULL

_ChildID ObjID Not NULL

_Direction SMALLINT Not NULL

_EventCID ClassID Not NULL

_EventCount ObjID Not NULL

_EventDetail NVARCHAR(255) Not NULL

_NumOwned INT Not NULL

_Priority INT Not NULL

_SumDirection INT Not NULL

_nCHVH INT Not NULL

_ParentCID ClassID Not NULL

_ParentID ObjID Not NULL

View the MaintErrors table to see error messages that are generated when aGTMMAINT message is processing.

Note: The messages are written to the MaintErrors table only. No interfacedisplays them in any other format.

Table 5 provides information about the fields in the MaintErrors table. See“Maintenance Window Messages” on page 18 for an explanation of possiblemessages.

Table 5. MaintErrors

Columnname

Data type Null? Description

id INT IDENTITY(1,1) Not NULL Incremental counter

timestamp DATETIMEGETDATE()

Not NULL The time the message was written tothe table


Table 5. MaintErrors (continued)

Columnname


message NVARCHAR(225) NULL Original GTMMAINT message text

reason NVARCHAR(2000) Not NULL Error message text

To see serialized processing of the asip_maintTask SQL procedure, view theMaintLock table. Table 6 provides information about the fields in the MaintLocktable.

Table 6. MaintLock

Columnname


lock INT Not NULL PRIMARY KEY (write access lock)

Maintenance Window MessagesThe following messages can be displayed:v 61000

Messageasisp_process_MaintOutageRequest: message is invalid - all parametersnot received

ExplanationAll required parameters for the GTMMAINT message were notprovided.

System actionThe GTMMAINT message is logged in the MaintErrors table, but notprocessed any further.

User responseCorrect the GTMMAINT message syntax.

v 61001

Messageasisp_process_MaintOutageRequest: cid is an invalidUnique-Parent-Object-Type value

cid Class identifier.

ExplanationThe specified CID is not valid.


User responseCorrect the CID.

v 61002

Messageasisp_process_MaintOutageRequest: cid is an invalid Target-Object-Typevalue

cid Class identifier


ExplanationThe specified CID is not valid


User responseCorrect the CID.

v 61003

Messageasisp_process_MaintOutageRequest: On-Off-Indicator indicator is notON or OFF

indicatorOn-Off-Indicator value

ExplanationThe On-Off-Indicator must be the value ON or OFF.


User responseCorrect the On-Off-Indicator value.

v 61004

Messageasisp_process_MaintOutageRequest: duration_period is an invalidDuration-Of-Maintenance value

duration_periodThe length of time an object is to be in maintenance.

ExplanationThe Duration-Of-Maintenance parameter is not valid. The value for thisfield must be 0–2147483647.


User responseCorrect the Duration-Of-Maintenance parameter.

v 61005

Messageasisp_process_MaintOutageRequest: Desired-Effect-Indicator valueindicator_value is not 0, 1, 2, or 3

indicator_valueThe Desired-Effect-Indicator value.

ExplanationThe Desired-Effect-Indicator parameter is not valid.


User responseCorrect the Desired-Effect-Indicator parameter.


v 61006

Messageasisp_process_MaintOutageRequest: GMT-Start-Time value gmt_time isnot in the format YYYYMMDDHHMMSS

gmt_timeThe start time in Greenwich Mean Time (GMT) time format.

ExplanationThe GMT-Start-Time parameter does not follow theYYYYMMDDHHMMSS format


User responseCorrect the GMT-Start-Time parameter.

v 61007

Messageasisp_process_MaintOutageRequest: hosttime host_time is not in theformat YYYYMMDDHH:MM:SS.tttttt

host_timeobject server timestamp

ExplanationThe host object server timestamp is not in a valid format.


User responseCorrect the object server timestamp.

v 61008

Messageasisp_process_MaintOutageRequest: no matching objects

ExplanationEither the target object of the GTMMAINT message does not exist, orthe target object, in combination with the specified unique parent, doesnot exist.


User responseCorrect the target object name, or the the unique parent object name, orboth.

v 61009

Messageasisp_process_MaintOutageRequest: multiple matching objects

ExplanationThe target object was not uniquely identified, and more than oneresource matched the name or the name in combination with the unique


parent name, or both. Either a unique parent was needed and was notspecified, or a unique parent was specified but it was not actuallyunique.


User responseCorrect the unique parent name or target object name, or both, to ensureunique identification.

v 61010

Messageasisp_process_MaintOutageRequest: value is an invalidTarget-Object-Native-Key value

value The Target-Object-Native-key value.

ExplanationThe format of the Target-Object-Native-key value was not valid. It mustcontain 10 hexadecimal digits (upper or lower case allowed).


User responseCorrect the Target-Object-Native-Key value.

Stages of the Maintenance StateWhen Tivoli Business Systems Manager resources are put in the maintenance state,in maintenance, the following occurs:v The AlertState is set to green.v The current state of the object is set to In Maintenance.v The desired state of the object is not affected.v An indicator (for example, the ownership indicator) is applied to these objects in

both the physical and any business system views in which the object appears.v The object continues to receive events, but no alerts are propagated to parents

(either physical or logical).v Though state changes are calculated from any events received while in

maintenance mode, these state changes are not reflected in the console displayuntil the object is out of maintenance mode.

v Active alerts propagated to parents prior to the object being put in themaintenance state are removed from the parent object (with typical consequencesfor the parents).

v If the resource going into maintenance mode is the target (or root) resource ofthe GTMMAINT message, then an informational message that indicates howmany resources entered maintenance (MaintComplete) is posted to the resource.

v If the number of resources entering maintenance exceeds the maximum numberof resources allowed, then a MaintNotComplete informational message event isposted to the resource. This informational message provides the details abouthow many resources actually went into maintenance and how many resourcesdid not.


When the resource is in maintenance mode, existing messages or exceptions (orboth) are still visible, though they can be filtered. New messages or exceptions (orboth) are processed but they do not affect the alert state of the object and themessages or exceptions (or both) are not propagated to any parent resource.

When a resource is removed from the maintenance state, the following occurs:v The object resumes propagating alerts and the state of the object is set to the

state it would have been in if it had not been in maintenance mode. Thishappens because, while the object is in maintenance mode, events cause statechanges, but the state changes are not reflected immediately. The changes arerestored when the object comes out of maintenance mode.

v The in maintenance indicator is removed from any client views.v An informational message event (maintEnd) is posted to the resource.

Controlling the Number of Resources in the MaintenanceState

You can place a limit on the number of resources that can be placed intomaintenance mode using a single GTMMAINT event. An entry in theSystemConfiguration table in the Tivoli Business Systems Manager database. Thegroupname value for this entry is set to Maintenance and the propertyname valueis set to MaintenanceLimit. To disable future GTMMAINT messages from puttingany resources into maintenance mode, set the MaintenanceLimit value to 0 (zero)as in the following example:MaintenanceLimit=0

If the total number of resources going into maintenance mode exceeds the limit setwith the MaintenanceLimit value, then a limiting scheme is applied to theresources. This limit does not apply to resources coming out of maintenance mode.

To determine the number of resources being put in maintenance mode, begin withthe root object. The target object is the root object. Each child of that object, in agiven generation, is at the same level. Partial levels of objects are not placed intomaintenance mode. Only whole levels can go into maintenance mode.

For example, resource A has children B and C in the physical tree. Resource B haschildren D and E in the physical tree. Resource C has children F and G in thephysical tree. If the MaintenanceLimit is set to 10, then all resources are put inmaintenance mode if they match the GTMMAINT criteria. If the MaintenanceLimitvalue is 6, only resources A, B and C are put in maintenance mode if they meet theGTMMAINT criteria. If the value of MaintenanceLimit is 2, only resource A is putin maintenance mode.

Viewing Resources in Maintenance ModeThe Tivoli Business Systems Manager console visually shows objects inmaintenance mode. The user help panels that accompany the Tivoli BusinessSystems Manager console provide information about resources in maintenancemode. On the Tivoli Business Systems Manager console, there are two tooltips thatcontain the In Maintenance information:v In Maintenance decorator iconv The aggregate tooltips contains CurrentState

An option for the In maintenance tooltip appears in the tooltip options inAdministrator Preferences. When the option for In maintenance is on, the tooltip


appears for the In maintenance decoration icon and appears as a value of theCurrent State tooltip within the aggregate tooltip as well.

Note: In maintenance appears as the current state in the aggregate tooltip based inthe In maintenance tooltip option. It is not based on the current state tooltipoption.

To enable tooltips, add the following line to theTivoliManager\ConsoleServer\Servers.properties file:com.tivoli.tbsm.InMaintenanceSupported=1

Working With Ownership of Notes and EventsThere are several ways to work with ownership notes or events.

Taking Ownership Without Removing AlertsWhen a user takes ownership of events, the alerts are negated. The Administratorcan change this behavior so that the alerts which are owned events are not negatedand the event is still shown as belonging to the user who took ownership. TheSystemConfiguration table entries in the Tivoli Business Systems Manager databaseallow the Tivoli Business Systems Manager Administrator to control the defaultbehavior of the feature and the Tivoli Business Systems Manager console user tochange the behavior of any ownership notes they create. The AdministratorPreferences window allows Administrators to configure this function from theTivoli Business Systems Manager console. The Administrator Preferences windowprovides functions to be enabled or disabled that allow:v an Operator to create a problem ticket for an existing ownership notev an Administrator or Operator to update the following specific fields in a note:

– Subject– Description– Assignee– Clear alerts from resources

v an Administrator or operator to clear alerts from resources

For complete field level information on the Administrator Preferences window, seethe User Assistance on this window from the Tivoli Business Systems Managerconsole.

Table 7 on page 24 provides information on editing the SystemConfiguration tableto control the note ownership behavior when Tivoli Enterprise Console operatorstake note ownership from the Tivoli Enterprise Console console.


Table 7. SystemConfiguration table in the Tivoli Business Systems Manager database

groupname propertyname Description

TEC_EVENT-OWNERSHIP

CLEAR_ALERTS_ON_OWNERSHIP_DEFAULT

Controls the defaultprocessing for TivoliEnterprise Console operatorswhen the note ownership istaken from the TivoliEnterprise Console console.Valid values are YES and NOwhere:

v YES indicates that the alertsare cleared

v NO indicates that alerts arenot cleared

The default value is YES.

Note Ownership Customization IssuesWhen a user takes ownership of events, any alerts to those events are negated. TheAdministrator can change this behavior so that the alerts sent to owned events arenot negated and the event is still shown as belonging to the user who tookownership. To determine how the clear alerts function is currently configured,perform the following SQL query:SELECT propertyname, propertyvalueFROM SystemConfigurationWHERE groupname = ’Ownership’

This query returns results in the following form:propertyname propertyvalue--------------------------- -------------AdminClearAlertsDefault 1AdminClearAlertsModify 0OperatorClearAlertsDefault 1OperatorClearAlertsModify 0

To determine how the TEC Operator Clear alerts feature currently configured,perform the following SQL query:SELECT propertyname, propertyvalueFROM SystemConfigurationWHERE groupname = ’TEC_EVENT_OWNERSHIP’AND propertyname = ’CLEAR_ALERTS_ON_OWNERSHIP_DEFAULT’

This query returns results in the following form:propertyname propertyvalue--------------------------- -------------AdminClearAlertsDefault YES | NO

To determine if a particular ownership note should have cleared alerts, do one ofthe following:v See the Clear alerts check box on the Note Editor dialog for the note.v See the Note_V entry for the note in the database. Notes that have the clear

alerts behavior can be identified by issuing the following query:SELECT *FROM Note_VWHERE _Flags & 1 = 1


Note that there are visual limitations within the console when using the option tonot clear alerts on ownership. The parent resources of a child might have a red oryellow alert state with no indicator that the child event that caused the alert isalready owned. In all views other than event view and properties page, this will bethe behavior. There will be no visual alert state indicator for parent resources todistinguish between those with owned child events versus unowned. However, ifthe child resource is within the view, the ownership icon will appear on it.

Intelligent Monitor for Tivoli NetView (IMfNetView)Notes:

1. For prerequisite information, refer to the IBM Tivoli Business Systems Manager:Installation and Configuration Guide.

2. IMfNetView is only supported in English for 2.1.1.

Tivoli Business Systems Manager is initially populated with IP topology data fromthe Tivoli NetView program by way of a bulk upload initiated from a command onthe Tivoli NetView server. This data consists of all managed resources, subnets,segments, and other information identifying the Tivoli NetView server from whichthe resources came.

Then, each Tivoli NetView server maintains its own data within Tivoli BusinessSystems Manager. This is referred to as a delta upload. When a resource is added,deleted, or its attributes change, Tivoli NetView notifies Tivoli Business SystemsManager by way of the Intelligent Monitor in the form of a Tivoli BusinessSystems Manager event, and updates the resource data, adding or deletingresources as necessary.

For example, when the status of a router changes, an event for the new interfacestatus is sent to Tivoli Business Systems Manager. Tivoli Business Systems Managerthen propagates the hierarchy with that status. When a new router is discovered,Tivoli NetView creates new Tivoli Business Systems Manager resources for therouter, the interfaces, and any new segments and subnets, and populates thoseresources through the Common Listener service.

If the Tivoli Business Systems Manager server is unavailable, the data istransparently queued on the server.

Performing a Bulk UploadTo perform a bulk upload, do the following:1. From the Tivoli NetView console, click Tools -> TBSM Adapter Manager: Bulk

Upload

2. From a command prompt, issue the following:From a UNIX platform:/usr/OV/bin/tbsmbulkupload.ksh

From a Windows platform:\usr\ov\bin\tbsmbulkupload.bat

You can perform the initial bulk upload, then perform subsequent bulk uploadswhen the Intelligent Monitor for Tivoli NetView is stopped.


Multiple Tivoli NetView Management SourcesThis section guides you in setting up multiple Tivoli NetView feeds to achieve thedesired result in Tivoli Business Systems Manager.

The following is supported:v Multiple Tivoli NetView sites around the world managing the network of the

enterprise under a single Tivoli Business Systems Manager hierarchy.v Each Tivoli NetView site can consist of two Tivoli NetView systems in a failover

configuration.v Each Tivoli NetView site manages a subsection of the total network, and Tivoli

Business Systems Manager must handle duplicate IP addresses (for example,10.*.*.* type networks) and possible duplicate resource names across the entirenetwork. Some of these will represent the same overlapping resource and somewill be different resources.

v Each Tivoli NetView site must maintain and refresh their resources in TivoliBusiness Systems Manager.

The key elements for site and instrumentation identification that satisfy theserequirements are as follows:

NVID:– Defined in the nvid.conf file in the /usr/OV/conf/ directory.– The NVID property must be unique to each Tivoli NetView server or failover

pair. The NVID must be no more than 15 characters and cannot contain anyspaces.

– The NVID can be descriptive of the Tivoli NetView site. For example,Boston, MainTrunk, Customer_Site.

– The NVID must be shared with a redundant Tivoli NetView site managingthe same network.

NetworkID:– Defined in the nvid.conf file in the /usr/OV/conf/ directory.– The networkID property must be unique to the management site of the

Tivoli NetView server.– The networkID is appended to all resource names so it should be short in

length.– This value can be used by other management applications such as the Tivoli

Enterprise Console.InstrumentationID:– Used by the Common Listener to identify the data source.– The Intelligent Monitor for Tivoli NetView creates this ID by concatenating

the string Tivoli Business Systems Manager Instrumentation for TivoliNetView with the NVID value of NetViewDistributed.

– The Common Listener tags each resource with the InstrumentationID. Thisdefines the set of resources to be refreshed by a bulk upload. Note that abulk upload updates existing resources in its set, adds any new resources,and deletes resources that were not present in the bulk upload.

TBSM table object.CL_AutoPlacement:– This table is used by the Common Listener to map instrumentations (data

sources) with a top level enterprise.– The _in column is a LIKE clause for matching against the InstrumentationID.


– The _out column is the name of the enterprise resource that thisinstrumentation is feeding.

Typically all of the Tivoli NetView sources will upload IP data for one TivoliBusiness Systems Manager enterprise, but the resources of each individual TivoliNetView program will be differentiated by the networkID defined in the nvid.conffile.

Launching the Tivoli NetView Console from Tivoli BusinessSystems Manager

From the Tivoli Business Systems Manager Console, select a host machinemanaged by the Tivoli NetView program, then right-click to select a launch menuitem from the main Launch menu. Each of the menu items will launch to a TivoliNetView Web Console running on the same machine. Menus are context sensitive,so they will only contain active menu items appropriate for the selected resource.The following menu items are available:

Launch->NetView Web ConsoleDisplays the Tivoli NetView Submap Explorershowing the resource in focus on a topology map.This menu item appears for all host type resources.

Launch->NetView DiagnosticsDisplays the Diagnostics dialog for the resourceselected, allowing the operator to perform any ofthe diagnostic functions available from the TivoliNetView program. This menu item appears for allhost type resources.

Launch->NetView Object PropertiesDisplays the Object Properties dialog for theresource in focus. This menu item appears for allhost type resources.

Note that a separate Tivoli NetView Web Console will be launched for eachdifferent Tivoli NetView server. So, if three Tivoli NetView servers contribute toTivoli Business Systems Manager, there will be up to three separate Tivoli NetViewWeb Consoles active. The result of selecting the Launch menu items will be toeither start a new Tivoli NetView Web Console if none is yet connected to thatserver, or to change the context of the active Tivoli NetView Web Console alreadyconnected to that server. Context is defined as the function plus the resource infocus.

Troubleshooting Intelligent Monitor for Tivoli NetView(IMfNetView) Failures

You can use the following log files to help you in resolving problems with theIntelligent Monitor for Tivoli NetView:

Table 8.

/usr/OV/log/BaseClientTrace.log Tracing from the local adapter transportcode, tbsmadapter.

/usr/OV/log/tbsma.log Logging from the local adapter code,tbsmadapter.

/usr/OV/log/tbsmatopo.log Logging from the tbsmtopo process.

/usr/OV/log/tbsmatrap.log Logging from the tbsmtrap process.


Table 8. (continued)

/usr/OV/log/BaseClientLogging.log Output in XML format whenlistenerlog=true is specified in thetopxtbsmagent.properties file.

/usr/OV/log/tbsmatrace.log The tbsmtopo process begins tracing on thisfile when the/usr/OV/log/tbsmatrace.trigger file iscreated.


Chapter 5. Documentation Notes

This chapter includes known documentation problems and corrections.

Documentation Problems and CorrectionsFollowing are known documentation problems and solutions:v Problem: Documentation APAR OW57169: abstest -e must be run for all the

objects already present in the database.Solution: In Appendix A of the IBM Tivoli Business Systems Manager:Administrator’s Guide, subsection Creating the Automated Business SystemsConfiguration File, list item 13 was changed as follows:Create the business systems on the production implementation by using theabsTest.ksh command using both the discovery and queuing options andselecting the combination of pattern, criteria, or path operators that isappropriate for the change to the configuration file. This will create theappropriate business systems for those resources that already exist in TivoliBusiness Systems Manager. It might be necessary to repeat this step multipletimes to exercise all of the pattern, criteria, or path updates that have occurred.

v Problem: The IBM Tivoli Business Systems Manager: Administrator’s Guide does notspecify the amount of time that automated business system creation can take.Solution: The automated business system implementation is meant to be abackground process and it is typical for the creation process to take 45 secondsto create each business system. Consider this timing issue if you plan to create alarge number of business systems utilizing the automated business systemfunction.

v Problem: When using the automated business system function, the absTest.kshcommand is able to successfully discover and create business systems, butautomatic discovery based on new or changed attributes of a resource using theautomated business system (ABS) Discovery Process job does not occur.Solution: Sometimes the necessary triggers and tables for automatic businesssystem creation are not created for a specific class. To correct this situation, runthe following queries using SQL to create the appropriate triggers and tables forthe appropriate class:EXEC asisp_add_ev_worktable ’cid’EXEC asisp_add_EV_triggers ’cid’

Where cid is the class ID composed of a 2–4 character string.v Problem: The IBM Tivoli Business Systems Manager: Administrator’s Guide does not

state a performance preference for pattern operators used in automated businesssystems.Solution: The performance of the EGREP pattern operator is less than the LIKEand LIKE LIST pattern operators. The EGREP pattern operator was provided forbackwards compatibility. All EGREP pattern operator usage should be convertedto LIKE or LIKE LIST for best performance.

v Problem: Support by Tivoli Business Systems Manager for system managedstorage includes the ability to automatically discover and rediscover datasets,catalogs, and catalog entry resources. These resources do not receive events butthey are available for viewing and searching through use of a variety of filters.Initially, the system managed storage data collection routines collect everything,


and unless significant filters are used when discovering these resources, the sizeof the Tivoli Business Systems Manager database system can be adverselyaffected.Solution: Either filtering must be applied through options available in systemmanaged storage collection jobs to insure that only critical system managedstorage resources are discovered, or these features should not be used. Becausesystem managed storage often does not provide clearing events for itsexceptions, exceptions of the same category can overlay each other. This canresult in the grouping of several exceptions to a single exception display in theTivoli Business Systems Manager system. Use the reporting system to see thedifferent actual events that have been received.

v Problem: The IBM Tivoli Business Systems Manager: Administrator’s Guide statesthat the automated business system discovery and creation processes should bestopped before loading a new configuration file. Instructions for doing this arenot included.Solution: Instructions for stopping business system discovery and creationprocesses follow:To stop automated business system discovery and creation processes:1. In the SQL Server Enterprise Manager, go to the Job Management section,

located in Console Root\Microsoft SQL Servers\SQL ServerGroup\<database server name>\Management\SQL Server Agent\Jobs.

2. Right click the automated business system (ABS) Discovery Job row and clickDisable Job.

3. Right click the ABS Creation Job row and click Disable Job.4. Right click the ABS Discovery Job row and click Refresh Job. If the status is

Not Running, continue to Step 5. If the status is something other than NotRunning, click Refresh Job. Continue doing this until the status is NotRunning.

5. Right click the ABS Creation Job row and click Start Job.6. Right click the ABS Creation Job row and click Refresh Job. If the status is

Not Running, continue to Step 7. If the status is something other than NotRunning, click Refresh Job. Continue doing this until the status is NotRunning.

7. Load the ABS configuration file.


Chapter 6. Internationalization Notes

This chapter describes specific requirements, notes, problems, and corrections forinternational versions of Tivoli Business Systems Manager.

Installation and Upgrade Notesv Problem: Because the National Language Support resources for Tivoli Business

Systems Manager 2.1.1 product are not available at the time the Tivoli BusinessSystems Manager 2.1.1 product is shipped, the Tivoli Business Systems ManagerConsole location is not detected by the installation program.Workaround: See the information in “Installation Notes” on page 7 for details onthis workaround.

v Problem: After installation of the language pack, some column titles in thehealth monitor client windows are still in English. This does not affect healthmonitor functions.Workaround: None

Software Limitations, Problems and WorkaroundsProblem: Neither the bldgemtasks.sh script nor the bldgemsc.sh script supports filenames that contain characters from the Double Byte Character Set (DBCS) whenspecifying an SQI input file using the -f option.

Workaround: Use a file name with alphanumeric characters from the Single ByteCharacter Set (SBCS).

Documentation Problems and CorrectionsProblem: Some changes were made to the user interface and online informationafter the product was translated, so this information is not yet available in thetranslated versions of IBM Tivoli Business Systems Manager 2.1.1.

Workaround: None. Changes from 2.1.1 are completed and these changes will beincorporated into the Language Packs during the next release.

Internationalization IssuesThis section describes important items related to internationalization in this release.It describes items related to Tivoli Enterprise Console integration, the console,untranslated text in the user interface, and Tivoli Global Enterprise Managercommand-line utilities.

The Tivoli Enterprise Console rule engine calls the ihstttec command to send ageneric event to the Tivoli Business Systems Manager server. If the generic eventincludes DBCS, the DBCS must be defined with UTF-8 encoding due to TivoliEnterprise Console rule design. The DBCS generic event sent with non-UTF-8encoding shows unreadable output in the table GEM_APMGenericMaps ofdatabase Object. Therefore, if you want to handle DBCS directly in TivoliEnterprise Console rule file (use Japanese product name for example), you mustwrite it with UTF-8 in the Tivoli Enterprise Console rule file.


Following are sample Tivoli Enterprise Console BAROC and rule files to use DBCSproduct name. In this case, the wpostemsg command converts a DBCS productname to UTF-8 from the machine locale.1. Define the BAROC to add the product info slot.

TEC_CLASS :TMW_Generic_DBCS_Event ISA TMW_EventDEFINES {

product_dbcs : STRING; };END

2. Define the following rule set to associate the new slot above.rule:tec_generic_dbcs:

(description: ’invoke ihstttec’,event: _event of_class ’TMW_Generic_DBCS_Event’

where [source: equals ’TMNT’,hostname: _hostname,origin: _origin,modelname: _modelname,severity: _severity,msg: _msg,product_dbcs: _product_dbcs /* Put DBCS into a variable

],

reception_action:(exec_program(_event,

’../../TDS/EventService/ihstttec’,’ -b "%s" -i "%s" -q "%s" -p "%s" -s "%s" -o "%s" -t "%s" \

-m "%s"’,[_product_dbcs, _hostname, _origin, _modelname, _severity, \

’3’,’EXCEPTION’, _msg],’YES’))

).

3. Import above BAROC and rule files to your Tivoli Enterprise Console rule baseand load it into Tivoli Enterprise Console server.

4. Send an event using the new slot value. The wpostemsg command convertsDBCS parameters to UTF-8 internally, so you can specify the DBCS in themachine locale.wpostemsg -m "WARNING - GenericTest" -r WARNING hostname=aix59 \modelname=TMW_Generic \profilename=GenericTest product_dbcs="DBCS_Chars;1.0" \TMW_Generic_DBCS_Event TMNT

ConsoleInternationalization issues for the console are as follows:v Accelerator key labels shown in English: Accelerator key labels in the menus

are displayed in English. These labels are controlled by the Java RuntimeEnvironment (JRE) and not by the Tivoli Business Systems Manager productitself, and the JRE shipped with Tivoli Business Systems Manager has limitedsupport for localized accelerator key labels.


Intelligent Monitoringv Traditional Chinese bold and italic font display problems: When installing

Intelligent Monitoring in Traditional Chinese environments, some characters candisplay damaged. The problem is caused by a font problem in the Java RuntimeEnvironment on Windows systems.Correct the problem as follows:1. IBM World Type Fonts are on CD2: Tivoli Enterprise Console event

enablement, fonts, IM monitors, etls. Install the fonts on the affected systemsas follows:a. From the Windows desktop, click Start, Settings, Control Panel.b. From the Control Panel window, double click the Fonts folder.c. From the File menu, click Install new font.d. From the Drives menu, select the CD ROM drive.e. From the Folders listing, click \fonts\IBMWorldType.f. Click Monotype Sans WT TC from the list of fonts, and click OK to install

the font.2. Change to the installation directory of the JRE that you are using.3. In the font properties file (lib/font.properties.zh_TW):

– Change these lines to display as follows:serif.italic.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETserif.bold.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETsansserif.italic.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETsansserif.bold.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETmonospaced.italic.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETmonospaced.bold.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETdialog.italic.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETdialog.bold.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETdialoginput.italic.1=Monotype Sans WT TC,CHINESEBIG5_CHARSETdialoginput.bold.1=Monotype Sans WT TC,CHINESEBIG5_CHARSET

– Add this line to the #font filename section:filename.Monotype_Sans_WT_TC=mtsans_t.ttf

Untranslated Text in the User InterfaceInternationalization issues relating to untranslated text in the user interface are asfollows:v Discovered object classes and associated text strings: For any Tivoli Global

Enterprise Manager object classes dynamically loaded into the Tivoli BusinessSystems Manager database, a new set of user interface text strings is generated.This set of strings represents both generic object class functions and functionsspecific to the new object class. Tivoli Business Systems Manager does notdynamically generate the translations for the new user interface text strings.Translation of these strings is limited to the translated resources that areprovided by the user and loaded using the message catalog import utilityprovided with Tivoli Business Systems Manager.

v Text in received events: Text in events received by Tivoli Business SystemsManager is displayed in the language of the event source rather than in thelanguage matching the workstation locale.

v Text from integrated products: Untranslated text can be displayed in the TivoliBusiness Systems Manager interface for integrated products that provide datadirectly into the interface and have more limited language support than TivoliBusiness Systems Manager.

Chapter 6. Internationalization Notes 33

v Presentation Services uninstall interface: This interface has not been translatedand is available in English only.


Appendix A. New and Changed Commands and Messages for2.1.1

The following sections contain the new and changed commands and messages thathave been added for this release.

New Commands


gtmmaint

PurposeThe gtmmaint command is an Event Enablement command. This command placesresources into maintenance mode. A target object is specified and the followingoptions are provided:v To place only the target object into maintenancev To place the target object and all its children in the the physical treev To place only the target object if it exists into a business systemv To place the target object and its children if they each exist in a business system

Format

�� gtmmaint -a 01

-d duration -e effect-g gmttime-l localtime

�

�-z delimeter

(1)-c CID -o name

-p parentCID -n parentnames-c type -h tivolihostname

-t tcphostname-c type -t tcphostname

-h tivolihostname-c type -i instanceID

��

Notes:

1 This is a shell script. On Windows platforms, specify sh gtmmaint or tservergtmmaint.

Parameters-a The On-Off-Indicator field, which specifies whether outage notification

occurs if the value for the GMT-Start-Time field is not specified. Validvalues are 0 (off) or 1 (on).

0 If a value of 0 is specified, the Duration-of-Maintenance andGMT-Start-Time fields are ignored. This value is an optional meansfor exiting the outage condition if an exit is required before thescheduled duration has expired, or if there was a duration equal to 0.

1 If a value of 1 is specified, the outage notification immediately occursif the value for the GMT-Start-Time field is not specified, or starts atthe specified time.

-c The Target-Object-Type field, which specifies the Tivoli Business SystemsManager object type (CID) of the root resource targeted for maintenance.Up to nine CIDs can be specified. If paired with the -i, -h, or -t options,this can be either the CID, the CID name, or the product and version.

-d The Duration-of-Maintenance field , which is specified in minutes. Themaintenance window begins at the time specified by the Object Servertimestamp, unless the GMT-Start-Time (last field) is specified and is clearedautomatically by Tivoli Business Systems Manager when the duration hasexpired. The value of 0 in this field indicates the duration should be ineffect until further notice. The maximum value is 2 147 483 647.


-e Indicates the scope of objects to be placed into maintenance mode. Validvalues are as follows:

0 Only the object specified in the Target-Object-Name field will beplaced into maintenance mode (in both the physical tree and in anybusiness system which has a view of this object).

1 The object specified in the Target-Object-Name field, and all of itschildren in the physical tree, will be placed in maintenance mode (inboth the physical tree and in any business system which has a viewof the object being placed into maintenance mode).

2 If the object specified in the Target-Object-Name field displays in abusiness system, then only the object specified by theTarget-Object-Name will be placed into maintenance mode (in boththe physical tree and in any business system which has a view of thisobject).

3 The object specified in the Target-Object-Name field, and any of itschildren in the physical tree, will be placed in maintenance mode (inboth the physical tree and in any business system which has a viewof the object being placed into maintenance mode) if they alsodisplay in any business system.

-g The GMT-Start-Time field, which indicates the start time in the GMT(Greenwich Mean Time) format of YYYYMMDDHHMMSS.

-h The Tivoli host name field of the DM resource, which will display in thehost name slot of a Tivoli Enterprise Console event.

-i The instance identifier representing the generic resource.

-l The Local-Start-Time field, which indicates the start time that will beconverted to the GMT (Greenwich Mean Time) format ofYYYYMMDDHHMMSS and sent to the SQL server.

-n The Unique-Parent-Object-Name field, which is required unless the valuefor the Message-Format-Indicator field is 2. This field specifies the name ofan object within the parent hierarchy of the object targeted formaintenance. This object will be used to uniquely identify the target object(which can be blank if no parent object is required to uniquely identify thetarget object).

-o The Target-Object-Name field, which is required unless the value for theMessage-Format-Indicator field is 2. This field specifies the name of theroot object targeted for maintenance, and can be equal to the unique parentobject name.

-p The Unique-Parent-Object-Type field, which is required unless the value forthe Message-Format-Indicator field is 2. This field specifies the TivoliBusiness Systems Manager Class Identifier (CID) of an object in the parenthierarchy (which can be blank if no parent object is required to uniquelyidentify the target object).

-t Specifies the short or fully qualified TCP/IP host name of the DMresource, as seen on the icon label of the parent node in the physical tree.

-z A delimiter that separates the values specified with the -p and -n options.If not specified, the dollar sign ($) character is used. If resource names cancontain the dollar sign character, then you must specify a different value.

UsageConsider the following when using the gtmmaint command:

Appendix A. New and Changed Commands and Messages for 2.1.1 37

v For host messages, the object server timestamp is utilized as the starting time ifthe GMT-Start-Time field is not provided, and the same time zone is assumed.

v If the Duration-of-Maintenance field has the value of 0, then the maintenancewindow continues until a subsequent message containing an On-Off-Indicatorvalue of OFF is received. The value in the Desired-Effect-Indicator field shouldmatch in both the ON and OFF messages, otherwise some objects might be leftin maintenance mode. In the current design, the client GUI does not contain away to turn on or shut off maintenance mode.

v The latest maintenance window always supersedes any previous maintenancewindow in effect. For example, if an object is currently in a maintenancewindow, and there are 10 minutes left in the window, and a new gtmmaintmessage is received by the object indicating a maintenance window starting nowand ending in five minutes, then the maintenance window will expire in fiveminutes instead of in 10 minutes.

v Since the Desired-Effect-Indicator values of 1 and 3 can result in an unknownnumber of resources going into maintenance mode, a limiting function isprovided to limit the total number of resources that can be put into maintenancemode from a single gtmmaint message.


wimadiscovery

PurposeThe wimadiscovery command is a new command for Intelligent Monitor forAppManager. This command is used to perform a bulk or manual delta discoveryagainst the NetIQ AppManager repository. This command extracts all instances ofsupported object types and resources from this repository. The object types andresources can be saved locally in a file, or be provided to the listening service to besent to Tivoli Business Systems Manager.

Format

�� wimadiscovery Performance-verbose-h

��

Performance:

-ps normal

-ps maximumnormalminimum

-log-lf logfile_name

-verbose

Parameters-ps Use this option to specify the degree of performance saving

required, which you specify with one of the following mutuallyexclusive attributes.

maximum The discovery process takes a relatively long time,but avoids increasing system overhead andreducing performance.

normal The discovery process takes an average time,performing an average performance saving. This isthe default value.

minimum The discovery process is relatively fast, but systemperformance can be reduced.

-log The collected data is logged in a file, instead of being transmitteddirectly to Tivoli Business Systems Manager. Data is logged in aspecial format that can be understood by the Common Listenerservice. If you do not specify a log file name, data is logged in afile called AppManagerLst_LoggingModeFile.log and located in theproduct directory. If you specify the file name, you can also specifyan absolute path. If you do not specify a path, the log file iscreated in the directory where the command is located.

-verbose The discovery process details are displayed on the screen while theprocess is running.

-h The usage of the discovery command is displayed.


Examplesv The following command runs a manual bulk discovery that queries the

AppManager repository in order to extract all instances of currently supportedobject types and instances:wimadiscovery

v The following command performs a manual bulk discovery with minimumperformance impact to the system and with a detailed report of the event:wimadiscovery -ps minimum -verbose

v The following command performs a manual bulk discovery and logs the resultsof this discovery in a log file named pafirst_data.log:wimadiscovery -log -lf pafirst_data.log


Changed Commands


ee_config

PurposeThe ee_config command is used to configure the event enablement process. Theevent enablement process must be recycled for changes to take effect.

Format

�� ee_config-h

-a -d-e

-l d

-l dlu

-ssize

�

�(1)

-t number��

Notes:

1 This is a bash script. On Windows platforms, specify bash ee_config ortserver ee_config.

Parameters-a If defined, use the alias for the host name. Host names defined in the

etc/hosts directory can contain an alias by specifying a second host namefor an address. If the –a option is specified, then the alias name is put intothe hostname slot before an event is sent to Tivoli Business SystemsManager.

-d Disable the event cache. Disabling the cache does not allow for events tobe saved during periods that the Tivoli Business Systems Manager AgentListener service is down.

-e Enable the event cache. Events are saved in the cache during times that theTivoli Business Systems Manager Agent Listener service is down, andretrieved from the cache and sent to the Agent Listener when the service isactivated. When the Agent Listener is started, it sends the timestamp fromthe last event that it processed. Event enablement will retrieve all eventsfrom the cache with a timestamp older than the Agent Listener timestampand send them to the Agent Listener. If the timestamp sent by the AgentListener is not within the range of events stored in the cache, then noevents are retrieved from the cache. If the Agent Listener sends atimestamp with the value -1, then the entire cache is sent to the AgentListener.

-h Use the official host name of the host, as opposed to the alias. This is thedefault value.

-l Specifies whether the TCP host name should be in upper or lowercasebefore being sent to the agent listener.

d Use the casing provided by the domain name service. This is thedefault value.

l Send the host name in lowercase form.

u Send the host name in uppercase form.


-s Specifies, in megabytes, the size of the cache. If a size is not specified, then100 megabytes of disk space is used.

size The size of the cache. The value is in megabytes (for example, 100 is 100megabytes).

-t Specifies whether the TCP host name should be truncated before beingsent to the agent listener. This enables sending the short name instead ofthe fully-qualified name. The valid values for number are as follows:

0 Do not truncate the name. This is the default value if the -t option isnot configured at all.

1–5 Truncate the name after the first, second, third, fourth, or fifth periodin the name, respectively. The default value is 1 if the -t option isspecified without a value.

ExamplesThe following example specifies that the cache size is 25 megabytes:ee_config -s 25

The following example truncates the TCP host name john.bp.xyz.com to john:ee_config -t 1


wimasetup

PurposeThe wimasetup command is a command for Intelligent Monitor for AppManager.This command is used to configure the integration with Tivoli Business SystemsManager.

Format

�� wimasetup-log on

-lf log_file_nameoff

-reqport request_port_number-resport response_port_number-svrport server_port_number-svraddress server_address

file-lqs memory

file-rqs memory-instrefresh refresh_time-evtrefresh refresh_time-subnetmask: network subnet_mask-subnetmask: network remove

-setdbconn-h

��

Parameters-log on The collected data is logged in a file, instead of being transmitted

directly to Tivoli Business Systems Manager. If you do not specifya file name, data is logged in a file calledAppManagerEventLst_LoggingModeFile.log and located in theproduct directory.

-log off The collected data is not logged in any file. It is directlytransmitted to Tivoli Business Systems Manager.

-lf This option is valid only if log option is set to on. Here you specifythe file name where you want to log your data. You can alsospecify an absolute path. If you do not specify a path, the log fileis created in the directory where the command is located.

-reqport This is the workstation port number used by Intelligent Monitoringto receive requests from the Common Listener service.

-resport This is the workstation port number used by Intelligent Monitoringto receive responses by the Common Listener service. It can be thesame port specified in the reqport option, if you use the same portto receive requests and responses.

-svrport This is a port of the server where the Common Listener service isinstalled. It must be the same port that the Common Listenerservice uses to receive data from Intelligent Monitoring.

-svraddress This is the IP address of the server where the Common Listenerservice is installed.

-lqs This option enables you to choose where to store the incomingqueued data.


memory Incoming data is kept in memory. The process isrelatively fast, but if the application fails, you losedata.

file Incoming data is kept in a file. The process isrelatively slow, but if the application fails, you canstill retrieve the data. This is the default value.

-rqs This option enables you to choose where to store the outgoingqueued data.

memory Outgoing data is kept in memory. The process isrelatively fast, but if the application fails, you losethe data.

file Outgoing data is kept in a file. The process isrelatively slow, but if the application fails, you canstill retrieve the data. This is the default value.

-instrefresh This is the time interval you want to elapse between successivediscoveries for object instance changes. It is specified in seconds.The default interval is 60.

-evtrefresh This is the time interval you want to elapse between successivediscoveries for events. It is specified in seconds. The defaultinterval is 60.

-subnetmask Subnet mask for the network to which the host belongs.

-subnetmask removeRemoves the subnet mask for the network.

-setdbconn Performing a setup with this option enables how you will establisha connection to the database. The user will be prompted for adatabase user ID and password. This parameter is exclusive andshould not be used with other parameters.

UsageThis command configures the integration with Tivoli Business Systems Manager.You can use this command to customize the settings you have specified during theinstallation procedure and some general integration settings. To display the currentvalues of the variables that can be set with this command, launch the commandwithout specifying any options. An example of the output is the following:wimasetup

Output similar to the following is received:Logging mode falseLog File Name AppManagerLst_LoggingModeFile.logRequest Port Number 9988Response Port Number 9988Server Port Number 8082Server Address x.xx.xx.xxxLocale Queue Store fileRemote Queue Store fileEvent Refresh Time 13Instance Refresh Time 60No subnet mask was set. Default subnet mask will be used -> CLASS A: 255.0.0.0,CLASS B: 255.255.0.0, CLASS C: 255.255.255.0


Examplesv The following command specifies that the collected data is logged in a file

named myFile.log, the server port number is 8082 and IP address istbsmserver.rome.tivoli.com.wimasetup -log on -lf myFile.log -svrport 8082 -svraddress tbsmserver.rome.tivoli.com

v The following command specifies that incoming and outgoing queued data isstored in memory. Instance refresh time is set to 40 seconds.wimasetup -lqs memory -rqs memory -instrefresh 40

v The following command establishes a connection to the database:wimasetup -setdbconn

Output similar to the following is received:Insert User Name:my-db-user-idInsert Password:******Type Password Again:******Testing database connection


New Messages

GTMCP0013I CPSM SUBNAME ENTERED,CICSPLEXNAME=plexnameSUBNAME=subname

Explanation: The CICSPlex being processed is definedto Tivoli Business Systems Manager with a subname.

Message Variables: plexname - The name of theCICSPlex as known to CICSPlex System Manager(CPSM)

subname - The subname used to qualify the CICSPlex inTivoli Business Systems Manager

System Action: Processing continues.

GTMCP0014I CICSPLEX CMAS cmasname ISUNAVAILABLE. UNABLE TOCONTINUE.

Explanation: The batch discovery program is unableto connect to the CMAS. This message indicates thatthere is no CMAS of this name on this system at therelease level being used for this connection.

Message Variables: cmasname - The name of theCMAS used for this connection

System Action: The batch discovery program endswith an abend code of U0008.

User Response: Verify that the CMAS name andoperating system specified in the CICSPlex propertieson the Tivoli Business Systems Manager consolematches the Maintenance point CMAS for theCICSPlex. Also, verify that the SEYUAUTH libraryconcatenated to the discovery job matches the versionof CICSPlex System Manager used by the CMAS.

GTMCP0015I CICSPLEX plexname IS NOT KNOWNto CMAS cmasname

Explanation: CICSPlex SM indicated that the CICSPlexis not known to the CMAS.

Message Variables: plexname - The name of theCICSPlex being processed

subname - The name of the CMAS used for thisconnection


User Response: Verify that the CMAS name andoperating system specified in the CICSPlex propertieson the Tivoli Business Systems Manager consolematches the Maintenance point CMAS for theCICSPlex. Also, verify that the SEYUAUTH libraryconcatenated to the discovery job matches the versionof CICSPlex System Manager used by the CMAS.

GTMCP0016E UNABLE TO OBTAIN SUFFICIENTVIRTUAL STORAGE. AMOUNTREQUESTED WAS length.

Explanation: The batch discovery program is unableto obtain sufficient virtual storage for a data buffer.

Message Variables: length - The length of storagerequested


User Response: Ensure that the region parameter doesnot restrict the storage available to the program.

GTMJC0704E The object you are attempting to pasteor drop is not valid for this view.

Explanation: An object is being pasted or droppedinto a view. It is not a valid object for this view. OnlyTivoli Business Systems Manager resources can bepasted or dropped into a view. Furthermore, resourcescannot be copied or pasted across different instances ofthe Tivoli Business Systems Manager Console.

System Action: The paste or drop operation ends.

User Response: From the same Tivoli BusinessSystems Manager Console as the target view, copy theTivoli Business Systems Manager resource or resourcesto the clipboard or drag the resource or resources. Thenperform the paste or drop operation again.

GTMZE0018E ZEKE FILE NOT SUPPORTED

Explanation: The ZEKE input file used for the bulkdiscovery process does not contain valid data.

User Response: Change the input file to use thecorrect LIST PLAN or LIST EVENTS report providedby the ZEKE reporting system. Run the Zeke bulkdiscovery job again.

IHS604I STARTED PROCESSING database ATtime optional_data

Explanation: IHSBDSCO has started processing one ofthe input databases.

Message Variables: database - The name (DD name) ofthe input database.

time - The local time in hours, minutes, and seconds inthe format hh:mm:ss.

optional_data - Additional data items that might be ofinterest. For example, if the database is processedmultiple times, this indicates which pass is in process.

Administrators Response: This message can be usedto help monitor IHSBDSCO processing rates. For


example, SYSVIEWS database processing is slower thanthe other three databases.

IHS605I PROCESSING BLOCK num AT time

Explanation: IHSBDSCO is working through an inputdatabase, which was identified in the precedingIHS604I message.

Message Variables: num - The block number, inincrements of 1 000

time - The local time in hours, minutes, and seconds inthe format hh:mm:ss

Administrators Response: This message can be usedto help monitor IHSBDSCO processing rates. Forexample, SYSVIEWS database processing is slower thanthe other three databases.

IHS683W pgm WARNING: SQL QUERYRETURNED num LINES FOR v1 v2 v3v4 v5 v6 v7

Explanation: A call to IHSBSQL did not return theexpected number of lines.

Message Variables: pgm - The name of the module.

num - The number of lines returned by IHSBSQL.

v1...v7 - Variable data which specifically identifies therelevant object.

System Action: Further processing of the object isbypassed.

Administrators Response: It might be necessary toexamine the historical behavior of the relevant object inorder to evaluate the significance of the number of linesreturned. For example, if the object was flagged as anexception in one polling cycle and is deleted (ordropped) before the next polling cycle, no lines mightbe returned during the resolution process for thatobject. Further processing is bypassed and, for thisspecific example, the exception remains unresolvedunless the SQL server agent job Delete Old IMS andDB2 Objects is run. If number of lines returned is twoor greater, contact Customer Support.

IHS811I DISCOVER NAME=name TYPE=type –status

Explanation: An IHSSDJLJ batch job, or PumpDISCOVER modify command, has started orcompleted.

Message Variables: name - The value of the Nameparameter used by this Discover request. This is awildcard mask that is compared against the names ofeach active Address Space.

type - The value of the Type parameter used by thisDiscover request. Values are STC, JOB, or ALL.

status - The status of this Discover request. Values areSTARTED or COMPLETED.


IHS812E ERROR IN IHSSDJL – reason

Explanation: The IHSSDJLJ batch job, or PumpDISCOVER modify command, has failed.

Message Variables: reason - The following reasons canexist:

IHSSDJL CAN ONLY BE INVOKED FROM A PUMPENVIRONMENT

The IHSSDJL program was incorrectly startedfrom outside of the Pump environment. Forexample, this program cannot be started fromthe NetView program.

UNKNOWN PARAMETER 'parm'. VALID ARE:NAME=namemask TYPE=STC|JOB|ALLDDNAME=bcpdd

The DISCOVER parameters were not valid.

NO REPLY FROM D J,L COMMANDThere was no reply from the D J,L command

UNEXPECTED MESSAGE messageThe reply from the D J,L command was notmessage IEE114I.

WRITE TO DDNAME ddname FAILEDA write to the data definition failed. There willbe other messages that provide moreinformation on the failure.

System Action: The Discovery process ends.

Administrators Response: Investigate the reason forthe failure. If you cannot determine the problem, addthe option DEBUG to the DISCOVER requestparameter string, and review the IHS402I debugmessages in the AOPLOG data definition. If you stillcannot determine the problem, contact CustomerSupport.

Changed Messages

GTMCP0036I CICSPLEX CMAS cmasname ISUNAVAILABLE. UNABLE TOMONITOR CICSPLEX plexname

Explanation: The source/390 object pump is unable toconnect to the CMAS. This message indicates that there

is no CMAS of this name on this system at the releaselevel being used for this connection.

Message Variables: cmasname - The name of theCMAS used for this connection


plexname - The name of the CICSPlex being processed

System Action: The CICSPlex is not monitored.

User Response: Verify that the CMAS name andoperating system specified in the CICSPlex propertieson the Tivoli Business Systems Manager consolematches the Maintenance point CMAS for theCICSPlex. Also verify that the SEYUAUTH libraryconcatenated to the source/390 object pump matchesthe version of CICSPlex System Manager used by theCMAS.

IHS321I output_text

Explanation: A Tivoli Business Systems Manager useris able to submit requests to the host system with theGUI right mouse-click function. Output from thesecommands (or messages stating that no values will beoutput) is prefixed with IHS321I.

Message Variables: output_text - The output textreceived from the host system


Administrators Response: There might be instanceswhere a request to the Host system might fail or returnan unexpected response. Details of the error should bevisible in the text that follows the IHS321I prefix.Review these messages in the appropriate messagesmanual. Also check the active NetView netlog forerrors. If unable to determine the problem, contactCustomer Support.

IHS413E RC20 FROM IMS WITHOUT DFS™

MESSAGE

Explanation: IMS returned a code of 20 (errorcondition) in response to an attempt to send acommand to IMS using the OTMA interface, but didnot provide an IMS message (prefixed by DFS) toindicate the cause of the IMS error.

System Action: Tivoli Business Systems Managerreports the error for diagnostic purposes.

Administrators Response: This is usually caused byproblems with the IMS OTMA interface. Check theNetView netlog for messages IHS332E, IHS359E,IHS410I, IHS411E, IHS412E, and IHS426E. Check theIMS Secondary MTO for the target IMS region for othermessages. Check that the OTMA interface has been setup and started correctly for the target IMS region. Ifyou are unable to resolve the problem, contactCustomer Support.

IHS426E OTMA TIMED OUT module jobname

Explanation: This is issued when the time taken tocomplete an IMS command, using the IHSIOTMAmodule, exceeds the allowed time limit.

Message Variables: module - The name of the module

that started the IHSIOTMA module.

jobname - The job name of the IMS Control Region.

Administrators Response: Ensure the IMS controlregion with which NetView program is attempting tocommunicate is up and has the OTMA interfacestarted. If the message occurs repeatedly, increase thevalue of the IHS$PARM parameterIHSI.OTMA.TIMEOUT in the SGTMSAMP data set,and refresh IHS$PARM by starting the NetViewprogram again. If this does not resolve the problem,contact Customer Support

IHS452I resource STATUS status AT NETVIEWINITIALIZATION

Explanation: This message indicates the status of theresource specified at NetView initialization.

Message Variables: resource - The name of theresource, which is typically the job name of an IMSregion, or the name of an ESAF link or similar resource.

status - The state in which the resource was found,which is either UP or DOWN.

IHS487W ims_jobname IS IMS RELEASE release -THIS RELEASE IS NOT SUPPORTEDBY IBM TIVOLI BUSINESS SYSTEMSMANAGER.

Explanation: The IMS region indicated by its IMS ID(Subsystem Identifier) or its Control Region job name isan IMS release that is not supported.

Message Variables: ims_jobname - The job name of theIMS control region or the IMS ID (SubsystemIdentifier).

release - The release number that is not supported.

System Action: No processing or monitoring occursfor this IMS region.

Administrators Response: If you require this IMSregion to be supported, upgrade to an IMS release thatis supported.

IHS489I name text current_value unit

Explanation: Indicates the current value of a thresholdor interval.

Message Variables: name - The name of the thresholdor interval.

text - Either THRESHOLD IS or INTERVAL IS.

current_value - The current value of the threshold orinterval.

unit - The unit of the threshold or interval (only occursin some cases).

Administrators Response: The threshold names are


documented within the IHS$PARM SGTMSAMPmember.

IHS727E MSG NUMBER IS NOT IN RANGE 300TO upper_limit – msg_number

Explanation: The internal routine IHS$MSG attemptedto issue a message outside the allowed range.

Message Variables: upper_limit - The highest IHSnumber message issued

msg_number - The message number in error

System Action: The request is rejected and processingcontinues.

Administrators Response: This is an internal error.Contact Customer Support.

IHS742I module – UNEXPECTED OUTPUTRECEIVED FROM IMS (jobname)DISPLAY COMMAND

Explanation: The module issued an IMS displaycommand and the output received did not contain theexpected text.

Message Variables: module - The name of the REXXmodule.

jobname - The Job Name of the IMS Control Region.

System Action: All processing requiring the outputfrom this display command is stopped and processingcontinues. This message is usually followed by messageIHS332E or IHS750I with the text of the outputreceived.

IHS751I COMMAND IN module_name TIMEDOUT

Explanation: The routine module_name received noresponse from an attempt to issue a command toanother subsystem (usually MVS or IMS) within themaximum time period specified by memberIHSI.$CORRWAIT.

Message Variables: module_name - The name of themodule

Administrators Response: Edit member IHS$PARM inthe SGTMSAMP data set and increase the delay valuefor member IHSI.$CORRWAIT. In the NetViewprogram, refresh IHS$PARM by restarting yourNetView region. If this does not resolve the problem,contact Customer Support.

IHS752I DEFAULT VALUE nn USED FOR cglobal

Explanation: This is issued when cglobal has no valueor an incorrect value defined in member IHS$PARM. Adefault value of nn is used and saved in that commonglobal variable.

Message Variables: nn - The default value being used

cglobal - The common global variable

Administrators Response: Edit member IHS$PARM inthe SGTMSAMP data set and correct the value of thecglobal entry. Refresh IHS$PARM by starting yourNetView region again. Note that this new valueoverrides the default value.


Appendix B. 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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

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

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

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

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

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

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, 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 beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct 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 itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, 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 materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

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

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

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

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not appear.

TrademarksIBM, the IBM logo, Tivoli, the Tivoli logo, AIX, CICS, CICSPlex, DB2, DFS, IMS,MVS, NetView, Tivoli Enterprise, Tivoli Enterprise Console, Tivoli ManagementEnvironment, and TME are trademarks of International Business MachinesCorporation in the United States, other countries, or both.


UNIX is a registered trademark of The Open Group in the United States and othercountries.

Microsoft, Windows, and Windows NT are registered trademarks of MicrosoftCorporation in the United States, other countries, or both.

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

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

Appendix B. Notices 53

��

Printed in U.S.A.

SC23-4841-01

ibm tivoli business systems manager: release...

Documents