IBM Tivoli Monitoring for Applications: mySAP.com: Limitations...

IBM Tivoli Monitoring for Applications: mySAP.com

Limitations and Workarounds SupplementVersion 5.1.0

SC23-4811-00

��

jolewis

(Revised February 2003)

IBM Tivoli Monitoring for Applications: mySAP.com

Limitations and Workarounds SupplementVersion 5.1.0

SC23-4811-01

��

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

Second Edition (January 2003)

This edition applies to Version 5.1.0 of IBM® Tivoli® Monitoring for Applications: mySAP.com and to all subsequentreleases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2003. All rights reserved. US Government UsersRestricted Rights — Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Limitations and workarounds . . . . . 1Installation limitations and workarounds . . . . . 1Other limitations and workarounds. . . . . . . 2On Windows NT, changes made on the Loggingdialog are not saved after clicking Apply Changesand Close . . . . . . . . . . . . . . . 4

Installing and configuring mySAP 5.1Tivoli Enterprise Data WarehouseCollector . . . . . . . . . . . . . . 5

Installing the mySAP 5.1 Tivoli Enterprise DataWarehouse Collector . . . . . . . . . . . . 5Configuring the mySAP 5.1 Tivoli Enterprise DataWarehouse Collector . . . . . . . . . . . . 6Messages . . . . . . . . . . . . . . . 12

Notices . . . . . . . . . . . . . . 19Trademarks . . . . . . . . . . . . . . 21

iii

iv IBM Tivoli Monitoring for Applications: mySAP.com: Limitations and Workarounds Supplement

Limitations and workarounds

This supplement provides the latest information about known product limitationsand workarounds. IBM updates the Limitations and Workarounds Supplement asneeded at the Tivoli Information Center Web site to ensure that the information iscurrent. On the Web page, select the name of the product you want to reference toaccess the supplement and other Tivoli product documentation:http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

The following sections of this supplement contain the limitations and workaroundsinformation:v Installation limitations and workaroundsv Other limitations and workaroundsv Additional information on specific limitations and workarounds

Installation limitations and workaroundsTable 1 contains a list of the known limitations for IBM Tivoli Monitoring forApplications: mySAP.com that you might experience during the installation processand describes the applicable workaround for each limitation. The information inthe table is presented in the following categories: General, Internationalization,Documentation, and Patch.

Table 1. Installation limitations and workarounds

Limitations Workarounds

General

When you are installing in an interconnected Tivolimanagement region, the installation might hang if youtry to mount the CD on another Tivoli managementregion machine.

The installation media must be mounted on the CD driveof the Tivoli management region machine where you areinstalling the product.

APAR 26383–IBM Tivoli Monitoring for Applications:mySAP.com automatically updates all R3Systemobjects by stopping all adapters (CCMS, Syslog, andIDOC), updating the code, and reconfiguring theadapters. Because the CCMS, Syslog, and IDOC eventadapters are replaced, the event adapters are stoppedduring the upgrade process and you will not receiveevents from your R/3 systems.

After the upgrade process completes, you must start theCCMS, Syslog, and IDOC event adapters that are installedon UNIX. The CCMS, Syslog, and IDOC event adaptersthat are installed on Windows are automatically startedeven if the event adapters were not previously running.

APAR IY26436–You must add authorizations if youhave the RFC security check enabled on your system.

Add the following authorizations:

J_8C1_SYSLOG_READERS_RFC,TYPE=FUGR,RFC_NAME=J8C4,ACTVT=16S_RFC,TYPE=FUGR,RFC_NAME=SLST,ACTVT=16

Internationalization

There are no known Internationalization limitations.

Documentation

1

http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST.html

Table 1. Installation limitations and workarounds (continued)


APAR IY36464–An incorrect directory reference ismade in Step 3 of the Installing the Web HealthConsole manually procedure in the installation guide.

Change Step 3 of the Installing the Web Health Consolemanually procedure in the installation guide to read asfollows:

Step 3. Copy the contents of the HCONSOLE directory ofJava resource bundle language class files from one of thefollowing component software CDs:

v For the English language, copy the class files from theIBM Tivoli Monitoring for Applications: mySAP.comComponent Software, Version 5.1.0 CD.

v For other languages, copy the class files from the IBMTivoli Monitoring for Applications: Language Support CD.

Patch

There are no known patch limitations.

Other limitations and workaroundsTable 2 contains a list of the known limitations for IBM Tivoli Monitoring forApplications: mySAP.com that you might experience outside of the installationprocess and describes the applicable workaround for each limitation. Theinformation in the table is presented in the following categories: General,Internationalization, Documentation, and Patch.

Table 2. Other limitations and workarounds


General

If you are running the OS Collect Informationtask, some values are returned as 1–.

There is no workaround. The parameters with 1– values are notsupported by mySAP.com servers on some platforms.

When viewing output from Remote FunctionCall calls, you might see extra text referencingthe table TPDB.

There is no workaround. The references to table TPDB in RFCcalls is documented in OSS note 511655. This extra text does notaffect the IBM Tivoli Monitoring for Applications: mySAP.comfunctionality.

Uninstall fails for Windows endpoints with thathave the error message tiv_spawn failed in thetask output.

You cannot run the uninstall process against an endpoint that hasnever been used by IBM Tivoli Monitoring for Applications:mySAP.com

When you are using the software in adouble-byte environment, you might seemessages displayed in task output windowsthat have an extra character at the end of eachline. This character might be seen as a carriagereturn character or a garbled character.

This problem occurs when the Tivoli desktop is running on aUNIX system, and the task generating the output is running on aWindows endpoint. The Windows environment adds a carriagereturn character to the end of each line, assuming that the outputwill be displayed on a Windows system. This output is notexpected on UNIX, so UNIX displays the extra character. Refer toAPAR IY32315 for current status.

mySAP.com files not deleted when running theuninstall process.

The following files in the%LCF_DATDIR%\LCFNEW\ITM\PACS directory have not beendeleted because they are in use. These files can be manuallydeleted after the machine is rebooted.

When you view SAP_RFC_ERROR_SYSLOGevents on the event console, the message slotmight contain rectangle symbols in the messagetext.

There is no workaround.

2 IBM Tivoli Monitoring for Applications: mySAP.com: Limitations and Workarounds Supplement

Table 2. Other limitations and workarounds (continued)


Clearing events might not be sent forSAP_Job_Status events after the jobs changestate or are removed from the mySAP.comsystem.

There is no workaround. This occurs when there are no jobs in themySAP.com system with the requested status. The clearing eventwill be sent when a new job enters the requested state.

Data supplied to Tivoli Enterprise DataWarehouse differs from performance dataavailable from mySAP.com.

There is no workaround. Tivoli reports data with validtransactions or program information only, but mySAP.comperformance data is based on all dialog steps.

Tivoli Manager for R/3 Version 2.2.0performance monitors do not returninformation from mySAP.com Version 6.1.0systems.

There is no workaround. These monitors function based on theMIB functionality provided by earlier releases of Tivoli Managerfor R/3. This functionality has been removed in mySAP.comVersion 6.1.0.

After migrating to IBM Tivoli Monitoring forApplications: mySAP.com Version 5.1.0, theCCMS event adapter continues to run againstmySAP.com systems running releases prior tomySAP.com Version 4.5.

If you configured the CCMS Adapter to run against applicationservers running mySAP.com releases prior to Version 4.5, and thenmigrated from Tivoli Manager for R/3 to IBM Tivoli Monitoringfor Applications: mySAP.com, you will be able to run the CCMSAdapter on these application servers. Even though the adapterwill run, it will not read any events since it is not supported onreleases prior to mySAP.com Version 4.5.

After migrating to IBM Tivoli Monitoring forApplications: mySAP.com Version 5.1.0, theTivoli Manager for R/3 Version 2.2.0performance monitors can fail.

Redistribute the Tivoli Manager for R/3 Version 2.2.0 monitors tothe new mySAP.com application server objects.

After migrating to IBM Tivoli Monitoring forApplications: mySAP.com Version 5.1.0 fromTivoli Manager for R/3 Version 2.2.0, entries forautodiscovery can exist in the crontab on UNIXsystems and in the Windows task scheduler.

These entries are no longer needed with IBM Tivoli Monitoringfor Applications: mySAP.com Version 5.1.0. Remove the TivoliManager for R/3 Version 2.2.0 entries by running the TivoliManager for R/3 Version 2.2.0 Remove Autodiscovery tasks.

When running the witmsettrace command, youmust set the Windows system PATHenvironment variable to include the location ofthe java.exe executable file.

There is no workaround.

TCPIP port conflicts occur when multiple Tivoliproducts using JLOG 3.X run on the samemachine and use the default JLOG port. Thiscan occur when Tivoli Enterprise DataWarehouse and IBM Tivoli Monitoring run onthe same machine. When this occurs, ajava.net.BindException is generated in the IBMTivoli Monitoring trace log. This exceptionprevents resource models that use JLOG fromrunning correctly.

1. Stop Tivoli Enterprise Data Warehouse and any other Tivoliproduct that is using the default JLOG port.

2. Restart IBM Tivoli Monitoring.

Running the wdmdistrib command with the -Joption to distribute the JRE does not work onWindows 2000 systems.

You must install the JRE locally and link the JRE using theDMLinkJre task.

On Windows NT, changes made in the Loggingdialog are not saved after clicking ApplyChanges and Close.

See “On Windows NT, changes made on the Logging dialog arenot saved after clicking Apply Changes and Close” on page 4 fordetailed workaround information.

Internationalization

Double-byte character set (DBCS) message flowand execution group names are not correctlydisplayed.

There is no workaround. DBCS names for message flows andexecution groups are not supported in this release of this product.

Documentation

Limitations and workarounds 3

Table 2. Other limitations and workarounds (continued)


Instructions for installing and configuringmySAP 5.1 Tivoli Enterprise Data WarehouseCollector were left out of the IBM TivoliMonitoring for Applications: mySAP.comInstallation and Setup Guide.

See “Installing and configuring mySAP 5.1 Tivoli Enterprise DataWarehouse Collector” on page 5 for the missing information.

Patch

You cannot type in the Discover dialog if youhave the Tivoli desktop from TivoliManagement Framework Version 3.7.1 patch 32,59, or 74 installed.

Use the Tivoli desktop from the base Tivoli ManagementFramework Version 3.7.1 or from patch 89. See APAR IY29760 formore information.

When running the uninstall script on zLinuxendpoints, you get the message perl: not found.

If you are using zLinux, you must also install Tivoli ManagementFramework patch 3.7–TMF-0035.

On Windows NT, changes made on the Logging dialog are not savedafter clicking Apply Changes and Close

On Windows NT, changes made on the Logging dialog are not saved after clickingApply Changes and Close. To correct this behavior, perform the following steps:1. Open the IBM Tivoli Monitoring Profile dialog box by doing the following:

a. Open the Tivoli desktop.b. Double-click the policy region icon to display the policy region.c. Double-click the profile manager icon to display the profile manager.d. Double-click the profile icon in which you want to customize a resource

model.2. Select the resource model that you want to customize.3. Click Edit to open the Edit Resource Model dialog box.4. Click Logging to open the Logging dialog box.5. Select the Enable Data Logging check box in the Data Logging Settings panel

to enable logging.6. Deselect the Aggregate Data check box.7. Select Raw or TEDW.8. Click Apply Changes and Close.

After you perform this procedure, the software behaves as expected andsubsequent changes to the logging parameters are saved normally.


Installing and configuring mySAP 5.1 Tivoli Enterprise DataWarehouse Collector

The mySAP 5.1 Tivoli Enterprise Data Warehouse Collector component for IBMTivoli Monitoring for Applications: mySAP.com is a data warehouse system thatreports the performance of your mySAP installations. The mySAP 5.1 TivoliEnterprise Data Warehouse Collector component collects data through remotefunction calls (RFCs) from R/3 application servers. You configure the mySAP 5.1Tivoli Enterprise Data Warehouse Collector component using the mySAP 5.1 TivoliEnterprise Data Warehouse Collector GUI.

The repository database is a staging area where data is maintained for insertion intothe Tivoli Enterprise Data Warehouse. Using an extraction transform and load step(ETL), data from the repository database is moved into the Tivoli Enterprise DataWarehouse. After the collected data is moved into the repository database, it isaggregated and data retention time frames are applied. Using a second ETL step,the data is moved into data marts that provide for application reporting acrossTivoli products. See the Tivoli Enterprise Data Warehouse documentation for moreinformation.

The GUI components of the mySAP 5.1 Tivoli Enterprise Data Warehouse Collectorcomponent include the wr3config.exe, reporting interface, and DB2 data warehousecenter. This document describes the configuration procedures for the mySAP 5.1Tivoli Enterprise Data Warehouse Collector using wr3config.exe.

The mySAP 5.1 Tivoli Enterprise Data Warehouse Collector collects the followingtypes of data from R/3 application servers:v Dialog statistic recordsv Performance recordsv LAN datav CPU datav Disk datav Application server availability data

The mySAP 5.1 Tivoli Enterprise Data Warehouse Collector collects the followingtypes of custom configuration data from R/3 application servers:v Service level agreementsv Custom transaction groupsv Transactions, programs, and IDs to excludev Scheduling of collection intervalsv Application serversv Repository database locationv Data retention period

Installing the mySAP 5.1 Tivoli Enterprise Data Warehouse Collector

ObjectiveTo install the mySAP 5.1 Tivoli Enterprise Data Warehouse Collector for IBM TivoliMonitoring for Applications: mySAP.com.

5

Background informationThe GUI components of the mySAP 5.1 Tivoli Enterprise Data Warehouse Collectorcomponent include the wr3config.exe, reporting interface, and the DB2 datawarehouse center. Of these three GUIs, the reporting interface and the DB2 datawarehouse centers are documented in the user guides distributed with theseproducts. Use this procedure to install the mySAP 5.1 Tivoli Enterprise DataWarehouse Collector wr3config.exe command.

Required authorization roleinstall_product

Before you beginYou must install Tivoli Enterprise Data Warehouse and a DB2 client on a WindowsNT Version 4.0 operating system before you can install and run the mySAP 5.1Tivoli Enterprise Data Warehouse Collector. There are no restrictions on the lengthof any of the strings entered in the installation dialog.

When you finishPerform the configuration as described in “Configuring the mySAP 5.1 TivoliEnterprise Data Warehouse Collector” on page 6.

ProcedureTo perform the installation in silent mode, run the following command from thecommand line:source\Collect\Setup.exe -s

where source is the installation directory.

To perform the installation using the GUI from a Windows NT desktop, performthe following steps:1. Click Start → Run Collect\Setup.exe from the install screen of the installation

media. The Welcome dialog is displayed.2. Click Next. The Choose Destination Location dialog is displayed.3. Click Browse to select an installation path other than the default path.4. Click Next. The Select Program Folder dialog is displayed.5. Select the default folder or another existing folder.6. Click Next. The Start Copying Files dialog is displayed.7. Click Next. The Setup Complete dialog is displayed.

Configuring the mySAP 5.1 Tivoli Enterprise Data Warehouse Collector

ObjectiveTo configure the mySAP 5.1 Tivoli Enterprise Data Warehouse Collector for usingwith IBM Tivoli Monitoring for Applications: mySAP.com.

Background informationYou can configure the following functions with the Tivoli Enterprise DataWarehouse mySAP 5.1 Tivoli Enterprise Data Warehouse Collector:

Repository database locationConfigure settings for insertion and aggregation of the DB2 repositorydatabase.

Target server selectionConfigure application servers from which to collect data.


Data retention periodConfigure how many days to keep data in the repository database.

ReportsConfigure reports to exclude transactions, programs, and IDs.

Service level agreement (SLA)Create a custom group and assign an SLA and transactions to that group.You can implement the SLA on an application level or on the wholesystem.

ScheduleSchedule the collection of statistic records, such as statistic and indicatordata. The indicator enables you to configure which days of the week tocollect operating statistics and set the polling interval.

Special runRecover data from collection periods and application servers that were notprocessed due to a failed attempt to collect data.

Note: Special run is only available for statistic records.

The following logs and traces are available to view different logs of the datacollectors:

Statistics logDisplays information about the collection, insertion, and aggregation stepsof statistics records

Indicator logDisplays information about the insertion and aggregation steps of wr3snaprecords. The collection is not displayed because the collection of data bythe wr3snap.exe command occurs at constant time intervals that rangefrom 1 to 1800. The insertion and aggregation of wr3snap.exe data occursduring the first run of a new day.

Statistics collection traceDisplays messages sent to the log from the wr3stati.exe NT service.

Indicator collection traceDisplays messages sent to the log from the wr3snap.exe NT service.

Statistics load traceThe Statistics Load Log is a DB2 load log. Verify that no records wereskipped or rejected.

Indicator load traceA DB2 load log.

Statistics aggregation traceA DB2 aggregation log. Verify that the commands complete successfully.

Indicator aggregation traceA DB2 aggregation log.

Database load setting traceDisplays a list of settings and messages generated by the wr3loader.execommand. These settings and messages help you determine load andaggregation problems.

Required authorization roleadmin

Installing and configuring mySAP 5.1 Tivoli Enterprise Data Warehouse Collector 7

Before you beginYou must install a DB2 client on the operating system that is running this program.

When you finishNo action is required after completing the configuration steps for the mySAP 5.1Tivoli Enterprise Data Warehouse Collector.

Installing the Repository databaseThe repository database is an installation of the Monitoring for mySAP repositorydatabase on a DB2 server. It is recommended that the repository database beinstalled on a separate machine from the machine where the Tivoli Enterprise DataWarehouse Collector is installed. To install the repository database, do thefollowing:1. In line

create database r3twh on /db2 dft_extent_sz 2;

Modify the DB2 path.2. In the lines

create regular tablespace r3twh_data managed by database using(file ’/db2/tablespace/r3twh_data’ 15000);

create regular tablespace r3twh_load managed by database using(file ’/db2/tablespace/r3twh_load’ 20000);

modify the path to the table space storage containers.3. In line

import from <path>\wr3_trans_data.dat of del messages <path>\wr3_trans_data.loginsert into r3_tcode_group;

add the path information.

Procedure1. Click the Current Configuration folder on the left side of the dialog box to

display the current configuration options.

2. Double-click the Initial configuration folder to expand the tree.


3. Click Repository database.4. Configure the following options:

Data sourceSpecify the name of the repository database.

User IDSpecify the database user ID.

PasswordSpecify the database user ID password.

DB2 InstanceSpecify the alias of the DB2 client to the remote database.

5. Click OK to save the Repository database configuration.6. Click Server to display the Target server selection.7. Perform the following steps to configure the Target server selection options:

a. Optional. Select the File location check box to specify the location of thenetworked application server file. The networked application server file iscreated by the List RFC Information task in the mySAP Configuration Taskslibrary. For additional information about the task used to create this file, seethe IBM Tivoli Monitoring for Applications: mySAP.com User’s Guide.1) Specify the drive, folder, and file location.2) Click OK to save the changes and return to the Target server selection

dialog box.b. Optional. Create a server by doing the following:

1) Click Create to display the dialog box to create and configure the RFCconnection to the R/3 application server. All of the fields on this dialogare associated with an RFC logon to the remote R/3 system.

Server Enter the fully qualified name of the server. Maximum length is100 characters.

ID Enter an ID. Maximum length is 30 characters.

PasswordEnter a password. Maximum length is 30 characters.

LanguageSelect a language from the drop-down menu.

SID Maximum length of 3 characters.

Instance #Maximum length of 2 characters.

Client #Maximum length of 3 characters.

2) Click OK to save the changes.c. Optional. Edit a server by doing the following:

1) Select a server from the list of application servers2) Click Edit to edit an existing Target server selection.

d. Optional. Delete a server by doing the following:1) Select a server from the list of application servers.2) Click Delete to delete an existing Target server selection.

8. Click OK to save changes you make in the Target server selection dialog box.


9. Click Repository Data Retention period to configure the number of days inwhich to retain the data as follows.a. Enter the number of days between 15 and 356.b. Click OK to save the changes.

10. Double-click Report Configuration to expand the tree and display thefollowing filters. Configuration options are the same for all three filters. Datais removed from Tivoli Enterprise Data Warehouse reports by adding filtersthrough the Report Configuration folder. The creation of filters is notretroactive and is applied from creation time forward. The follow exampledescribes how to configure programs to exclude.

a. Click Create to create a new entry and display the Exclude Programsdialog.

b. Type the name of the program to exclude.

Notes:

1) Maximum length for a program name is 30 characters.2) Maximum length for a transaction code is 20 characters.3) Maximum length for an ID is 20 characters,

c. Click OK to save the changes.11. Double-click the Service level agreement to expand the tree.


v Click Application SLA and do the following:

a. Click Add on the top left of the form to display the Add/Editapplication name dialog.

b. Type the application group name in the Application text box.c. Type a value in SLA in seconds text box.d. Click OK.e. Select the newly created group by clicking on it.f. Click Add in the Transactions frame to add transaction codes to the

application group you just created. The Add/Edit Applicationstransaction dialog is displayed.

g. Type the transaction you want to associate with the application group inthe text box. Separate multiple entries with a comma.

h. Click OK to save the changes.v Click All transaction SLA and do the following to set an SLA for all

transaction codes:– Type a value between 0.1 and 10 seconds in the All transactions SLA

text box.– Click OK to save the changes.

12. Double-click Schedule to expand the tree and configure schedule options.a. Click Monitoring for mySAP Statistics to create and add a scheduled run.

A scheduled run refers to the time when the Windows NT wr3stati servicecollects data.

b. Type the time in the Time: HH:MM text box.c. Click OK to save the changes. You can create a maximum of 90 scheduled

runs.d. Click Monitoring for mySAP Indicator to configure the polling interval

for the wr3snap Windows NT service.e. Select the boxes next to the day of the week on which you want to collect

statistics.f. Type a time interval in seconds to specify how often the data collection

occurs.


g. Click OK to save the changes.13. Optional. Click Special run to recover data from collection periods and

application servers that were not processed. You might need to use the Specialrun feature if an attempt to collect data failed.

a. Specify the following information:v Start datev End datev Start timev End time

b. Select an application server from the Available servers list box.c. Click the right arrow to move the server to the Selected servers list box.

Repeat for multiple entries.d. Click OK to save the changes. The data is collected from the selected

servers for the time spans configured, inserted, and aggregated in thedatabase.

Messages

ABH7000W Potential loss of data or data duplicationcan occur. Continue?

Explanation: When editing the Schedule statisticsdialog, potential gaps or overlaps might occur resultingin duplicated data or lost data.

Operator Response: None.

ABH7001E Error encountered

Explanation: A file handling error occurred. Thismessage is displayed in conjunction with messagesABH7002E or ABH7070E.

Operator Response: Review the associated error

messages and take appropriate action.

ABH7002E Error number =

Explanation: An operating system error has occurred.

Operator Response: Consult your operating systemdocumentation for information related to thecorresponding error number.

ABH7004W IDs have a maximum length of 12characters

Explanation: You have entered an invalid ID. IDs arelimited to a maximum length of 12 characters.

ABH7000W • ABH7004W


Operator Response: Correct the ID to contain 12characters or less and try again.

ABH7005W Programs have a maximum length of 30characters

Explanation: You have entered an invalid programname. Program names are limited to a maximumlength of 30 characters.

Operator Response: Correct the program name usinga name containing 30 characters or less and try again.

ABH7006W Transaction codes have a maximumlength of 20 characters

Explanation: You have entered an invalid transactioncode. Transaction codes are limited to a maximumlength of 20 characters.

Operator Response: Correct the transaction codeusing a name containing 20 characters or less and tryagain.

ABH7007E Start date is invalid. Format is’yyyymmdd’. Cannot be greater thancurrent date and must be 8 digits.

Explanation: You have entered an invalid start date.The correct date format is yyyymmdd. The date cannotbe greater than current date and must contain 8 digits.

Operator Response: Enter a valid start date that isless than or equal to the current date and try again.

ABH7008E Start time is invalid. Format is’hhmmss’. Cannot be greater thancurrent time and must be 6 digits.

Explanation: You have entered an invalid start time.The correct time format is hhmmss. The time cannot begreater than the current time and must contain 6 digits.

Operator Response: Enter a valid start time that isless than or equal to the current time and try again.

ABH7009E End date is invalid. Format is’yyyymmdd’. Cannot be greater thancurrent date and must be 8 digits.

Explanation: You have entered an invalid end date.The correct date format is yyyymmdd. The date enteredcannot be greater than the current date and must be 8digits.

Operator Response: Enter a valid end date that is lessthan or equal to the current date and try again.

ABH7010E End time is invalid. Format is ’hhmmss’.Cannot be greater than current time andmust be 6 digits.

Explanation: You have entered an invalid end time.The correct time format is hhmmss. The time enteredcannot be greater than the current time and must be 6digits.

Operator Response: Enter a valid end time that is lessthan or equal to the current time.

ABH7011E Duplicate application groups notallowed

Explanation: You have added an application groupwith a name that already exists.

Operator Response: Enter a unique application groupname and try again.

ABH7012E Sleep interval must be between 1 and1800 seconds

Explanation: The polling interval for the Scheduleindicator dialog must be between 1 and 1800 seconds.

Operator Response: Select a polling interval within 1and 1800 seconds and try again.

ABH7013E Interval is incorrect

Explanation: You have entered a polling interval thatis not numeric.

Operator Response: Enter a polling interval with avalid number between 1 and 1800 and try again.

ABH7014E Duplicate time entered

Explanation: You have entered a schedule time thatalready exists in the schedule statistics dialog.

Operator Response: Enter a unique schedule time andtry again.

ABH7015E Time is invalid,

Explanation: You have entered an invalid 24-hourclock time in the Schedule statistics dialog.

Operator Response: Enter a valid 24–hour clock timeand try again.

ABH7016E Maximum number of entries exceeded,

Explanation: You have exceeded the maximumnumber of entries for the Schedule statistics dialog. Themaximum number of entries is set to 90 and no furtherentries can be added.

Operator Response: The maximum number of entrieshas been reached for the schedule statistics dialog. Nofurther entries can be added.

ABH7005W • ABH7016E


ABH7017E Only whole numbers are permitted,

Explanation: You must use a valid whole numberbetween 15 and 365 in the Repository databaseretention period text box.

Operator Response: Enter a valid whole numberbetween 15 and 365 in the repository database retentiontext box and try again.

ABH7018E The number of days to maintain Hourlysummary data must be between 15 and365 days,

Explanation: Retention periods entered in therepository database retention period dialog mustbetween 15 and 365 days.

Operator Response: Enter a valid number between 15and 365 and try again.

ABH7019E The number of days to maintain data inthe database must be numeric,

Explanation: You have entered an invalid value in therepository database retention period dialog. Therepository database retention period must be a wholenumber between 15 and 365.

Operator Response: Enter a value, in whole numbersbetween 15 and 365, and try again.

ABH7019W Value to add not found,

Explanation: You have entered an invalid value orfailed to enter a value in the All transaction SLA dialog.The All transaction SLA dialog requires a value to beentered between 0.1 and 10 seconds.

Operator Response: Enter a value between 0.1 and 10seconds and try again.

ABH7020W Value to update not found,

Explanation: You have entered an invalid value, orfailed to enter a value, in the Application or SLA textboxes in the Add/edit application name dialog.

Operator Response: Enter valid values, in seconds, inthe appropriate text boxes and try again.

ABH7021E Service level agreement number ofseconds must be numeric and greaterthan 0.1 and less than 10 seconds,

Explanation: The All transaction SLA dialog and theAdd/edit application name dialog require a value to beentered between 0.1 and 10 seconds.

Operator Response: Enter a valid value, in seconds,and try again.

ABH7022E Duplicate ID entered,

Explanation: You have entered an ID name thatalready exists. The Exclude user ID dialog requiresunique IDs.

Operator Response: Enter a unique ID in the Excludeuser ID dialog and try again.

ABH7023E Duplicate program entered,

Explanation: You have entered a program name thatalready exists. The Exclude programs dialog requiresunique program names.

Operator Response: Enter a unique program and tryagain.

ABH7024E Duplicate transaction entered,

Explanation: You have entered a duplicate transaction.The Exclude transactions dialog unique transactions.

Operator Response: Enter a unique transaction andtry again.

ABH7025E Duplicate servers not allowed,

Explanation: You have entered an invalid applicationserver name. The Target server selection dialog requiresthat you enter only unique application server names.

Operator Response: Enter a unique application servername and try again.

ABH7026E You must enter a server,

Explanation: You did not enter a server name. TheTarget server selection dialog requires a server name.

Operator Response: Enter a server name in the Targetserver selection dialog and try again.

ABH7027E You must enter an ID,

Explanation: You did not enter a user ID. The Targetserver selection dialog requires that you enter a userID.

Operator Response: Enter a valid user ID in theTarget server selection dialog and try again.

ABH7028E You must enter a password,

Explanation: You have not entered a password orentered an invalid password. The Target serverselection dialog requires that you enter a validpassword.

Operator Response: Enter a valid password and tryagain.

ABH7017E • ABH7028E


ABH7029E You must enter an SID,

Explanation: You have not entered a valid systemidentifier (SID) or entered an invalid SID. The Targetserver selection dialog requires that you enter a validSID.

Operator Response: Enter a valid SID and try again.

ABH7030E You must enter an instance number,

Explanation: You have not entered an instancenumber, or have entered an invalid instance number inthe Target server selection dialog.

Operator Response: Enter a valid instance number inthe Target servers selection dialog and try then .

ABH7031E Instance number must be numeric,

Explanation: You have entered an invalid instancenumber in the Target server selection dialog. The Targetserver selection dialog requires a valid numericinstance number.

Operator Response: Enter a valid numeric instancenumber in the Target servers selection dialog and tryagain.

ABH7032E Instance number must be greater than orequal to zero,

Explanation: You have entered an invalid instancenumber in the Target server selection dialog. You mustenter an instance number that is greater than zero.

Operator Response: Enter a valid instance numberand try again.

ABH7033E You must enter a client number,

Explanation: You have entered an invalid clientnumber, or failed to enter a client number in the Targetserver selection dialog.

Operator Response: Enter a valid client number in theTarget server selection dialog and try again.

ABH7034E Client number must be numeric,

Explanation: The Target server selection dialogrequires that you enter a client number that is numeric.

Operator Response: Enter a numeric client numberand try again.

ABH7035E Cannot open file, another process haslocked it

Explanation: The file being accessed is currentlylocked by another process.

Operator Response: Close all non-essentialapplications and retry the process.

ABH7036E Error processing special run.

Explanation: An unspecified error has occurred whileattempting to process a special run.

Operator Response: Retry the special run.

ABH7037E Required file not found, DB2 clientcomponent db2cmd.exe not installed oris not in the path. Please refer to therelease notes

Explanation: The data collection facility requires theDB2 client to be installed properly.

Operator Response: Ensure that the DB2 client isinstalled and that a database alias to the repositorydatabase has been configured. After ensuring that theDB2 client is properly installed, check that the currentuser’s path statement is correct and includes the pathshowing the locations for the DB2 executable files.

ABH7039E End date must be greater than or equalto start date

Explanation: The Special run dialog requires that theend date be greater than or equal to the start date.

Operator Response: Correct the start and end dates inthe Special run dialog so that the end date is greaterthan or equal to the start date and try again.

ABH7040E No servers selected for special run

Explanation: The Special run dialog requires that atleast one server is selected from the Available serverslist box.

Operator Response: Select a server from the Availableservers list box in the Special run dialog by selectingthe server name and then clicking the right arrowbutton to move the selected server into the Availableservers list box and then try again

ABH7041E Start time cannot be greater than endtime and same day run

Explanation: The Special run dialog requires that theend date and start date are equal. The start time mustnot be greater than the end time.

Operator Response: Adjust the start and end datefields so that the start time is not greater than the endtime and try again.

ABH7042E Special run already running

Explanation: A special run is currently running. Youcannot submit a special run request until the currentrun is complete.

Operator Response: Wait for the current special run tocomplete and submit a new request.



ABH7043W Log does not exist

Explanation: A log file has not been generated.

Operator Response: Try again after a log file has beengenerated.

ABH7044E Server data file is locked by anotherprocess

Explanation: The server data file is locked by anotheruser or application and cannot be accessed.

Operator Response: User Response: Close allnon-essential applications and try again.

ABH7045E Decryption returned a null string

Explanation: The decryption process is not performingcorrectly.

Operator Response: Shut down the application,restart, and try again.

ABH7046E Encryption returned a null string

Explanation: The encryption process is not performingcorrectly.

Operator Response: Shut down the application,restart, and try again.

ABH7047W Loading server data

Explanation: A warning message displayed while theapplication loads the server file into memory.


ABH7048I Status: Running

Explanation: Information message indicating that aspecial run is currently running.


ABH7049I Status: Submitted —OR— IBM Tivolimonitoring for applications 5.1.0 -mySAP.com

Explanation: If you received Status: Submitted forthis message number, this is an Information messageverifying that a special run was submitted.

If you received IBM Tivoli monitoring forapplications 5.1.0 - mySAP.com for this messagenumber, it is an informational message stating currentIBM Tivoli product name and version.

Operator Response: Operator response for either ofthese messages is none.

ABH7050E Status: Action failed

Explanation: The special run you initiated failed.

Operator Response: Review the log files to determinethe cause of failure, resolve the problem, and resubmitthe special run.

ABH7051I Status: Ready

Explanation: Informational message stating thatselected action is complete and system is ready.


ABH7052I Action successful

Explanation: Informational message stating that theaction selected completed successfully.


ABH7053W No value set

Explanation: The data retention period has not beenconfigured.

Operator Response: Enter a valid value in theRepository database retention dialog.

ABH7053W No value set

Explanation: The value for the data retention periodhas not been configured.

Operator Response: Enter a valid value for the dataretention period in the Repository database retentiondialog.

ABH7054W Action cancelled

Explanation: Warning message stating that the currentaction was cancelled and modifications will not besaved


ABH7055E Registry Error: Corrupt registry database

Explanation: A registry database error related to youroperating system has occurred.

Operator Response: Consult your operating systemmanuals to correct and then try again

ABH7056E Registry Error: Key name is bad

Explanation: A key name error related to youroperating system has occurred.

Operator Response: Consult your operating systemmanuals to correct and try again.

ABH7043W • ABH7056E


ABH7057E Registry Error: Unable to open key

Explanation: An open error related to your operatingsystem settings has occurred.


ABH7058E Registry Error: Unable to read key

Explanation: A read error related to your operatingsystem settings has occurred.


ABH7059E Registry Error: Unable to write key

Explanation: A write error related to your operatingsystem settings has occurred.


ABH7060E Registry Error: Out of memory

Explanation: A registry error related to memorystorage space settings for your operating system hasoccurred.


ABH7061E Registry Error: Registry access is denied

Explanation: A Registry access error related to youroperating system settings has occurred.

Operator Response: Consult your operating systemmanuals to correct and then try again

ABH7062E Registry Error: Invalid parameters

Explanation: You selected invalid parameters for youroperating system.

Operator Response: Consult your operating systemmanuals, select valid parameters, and try again.

ABH7063E Registry Error: No more items

Explanation: A registry error related to your operatingsystem has occurred.


ABH7070E This file will need to be deletedmanually.

Explanation: You must delete the file namedwr3SpecRunServList.dat in the data collection facilitymanually.

Operator Response: Use standard methods for youroperating system to manually delete the file namedwr3SpecRunServList.dat in the data collection facility.

ABH7071I Not a standard SAP transaction code.Would you still like to add it?

Explanation: You attempted to enter a non-standardSAP transaction code. The data collection facilitiestransaction code verification process does not know thetransaction code you selected.

Operator Response: If you entered a valid transactioncode for your system, you can ignore this message andcontinue. If the transaction code is not valid, enter astandard SAP transaction code and try again.

ABH7072E Application server must be fullyqualified

Explanation: The target server selection dialogrequires that the application server name be fullyqualified.

Operator Response: Enter a fully-qualified applicationserver name and try again.

ABH7073E Wrong application server file selected.Must select wr3server.dat

Explanation: You attempted to select a non-standardnetworked application server file.

Operator Response: Select the networked applicationserver file named wr3server.dat and try again. .



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 Licensing

IBM Corporation

North Castle Drive

Armonk, 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 Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 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.

19

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 Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

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

The licensed program described in this document and all licensed 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.


TrademarksAIX, IBM, the IBM logo, Tivoli, the Tivoli logo, DB2, OS/400, and Tivoli EnterpriseConsole are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both.

Lotus, Lotus Notes, and Domino are trademarks or registered trademarks of LotusDevelopment Corporation in the United States or other countries, or both.

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

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

Solaris Operating Environment, Java, and all Java-based trademarks are trademarksof Sun Microsystems, Inc. in the United States, other countries, or both.

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

Notices 21

��

Printed in U.S.A.

SC23-4811-01

IBM Tivoli Monitoring for Applications: mySAP.com: Limitations...

Documents

Transcript of IBM Tivoli Monitoring for Applications: mySAP.com: Limitations...