IBM Tivoli Advanced Audit for DFSMShsm Monitoring …publib.boulder.ibm.com/tividd/td/ITAAfDFSM/SC27-2349-01/en_US/PDF… · Capacity planning for historical data logged by Advanced

Tivoli® IBM Tivoli Advanced Audit for DFSMShsm Monitoring AgentVersion 2.3

User's Guide

SC27-2349-01

��

Tivoli® IBM Tivoli Advanced Audit for DFSMShsm Monitoring AgentVersion 2.3

User's Guide

SC27-2349-01

��

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

This edition applies to version 2.3 of IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent (product number5698–B12) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2010.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Chapter 1. Overview of the IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent . . . . . . . . . . . . . . . . . . . . . . . 1

IBM Tivoli Monitoring overview . . . . . . . . . . . . . . . . . . . 1Features of the monitoring agent . . . . . . . . . . . . . . . . . . . 1Functions of the monitoring agent . . . . . . . . . . . . . . . . . . 1New in this release . . . . . . . . . . . . . . . . . . . . . . . . 2Components of the IBM Tivoli Monitoring environment . . . . . . . . . . . 2User interface options . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Requirements for the monitoring agent . . . . . . . . . . . 5Requirements for the monitoring agent . . . . . . . . . . . . . . . . 5Installing language packs . . . . . . . . . . . . . . . . . . . . . 6

Windows systems . . . . . . . . . . . . . . . . . . . . . . . 6UNIX or Linux systems . . . . . . . . . . . . . . . . . . . . . 6

Chapter 3. Workspaces reference . . . . . . . . . . . . . . . . . . 9About workspaces . . . . . . . . . . . . . . . . . . . . . . . . 9More information about workspaces. . . . . . . . . . . . . . . . . . 9Predefined workspaces . . . . . . . . . . . . . . . . . . . . . . 9Agent Navigator items . . . . . . . . . . . . . . . . . . . . . . 10

IBM Tivoli Advanced Audit for DFSMShsm Navigator item . . . . . . . . 10Agent Status Summary Navigator item . . . . . . . . . . . . . . . 10Backup Control Data Set Error Summary Navigator item . . . . . . . . 11HSEND List Event Information Navigator item . . . . . . . . . . . . 11HSM Tape Error Summary Navigator item . . . . . . . . . . . . . . 11LISTCAT Event Information Navigator item. . . . . . . . . . . . . . 11Migration Control Data Set Error Summary Navigator item . . . . . . . . 11Offline Control Data Set Error Summary Navigator item . . . . . . . . . 12

Chapter 4. Attributes reference . . . . . . . . . . . . . . . . . . 13About attributes . . . . . . . . . . . . . . . . . . . . . . . . 13More information about attributes . . . . . . . . . . . . . . . . . . 13Attribute groups and attributes for the IBM Tivoli Advanced Audit for DFSMShsm

Monitoring Agent . . . . . . . . . . . . . . . . . . . . . . . 13Agent Status Summary attribute group . . . . . . . . . . . . . . . . 16Backup Control Data Set Error Summary attribute group . . . . . . . . . 17BCDS Error Group1 attribute group . . . . . . . . . . . . . . . . . 18BCDS Error Group2 attribute group . . . . . . . . . . . . . . . . . 20BCDS Error Group3 attribute group . . . . . . . . . . . . . . . . . 22BCDS Error Group4 attribute group . . . . . . . . . . . . . . . . . 23BCDS Error Group5 attribute group . . . . . . . . . . . . . . . . . 25BCDS Error Group6 attribute group . . . . . . . . . . . . . . . . . 26BCDS Error Group7 attribute group . . . . . . . . . . . . . . . . . 27BCDS Error Group8 attribute group . . . . . . . . . . . . . . . . . 29HSEND List Event Information attribute group . . . . . . . . . . . . . 30HSM Tape Error Summary attribute group . . . . . . . . . . . . . . . 32HSMTAPE Error Group1 attribute group. . . . . . . . . . . . . . . . 33HSMTAPE Error Group2 attribute group. . . . . . . . . . . . . . . . 34LISTCAT Event Information attribute group . . . . . . . . . . . . . . 35MCDS Error Group1 attribute group . . . . . . . . . . . . . . . . . 36MCDS Error Group2 attribute group . . . . . . . . . . . . . . . . . 38

© Copyright IBM Corp. 2010 iii

MCDS Error Group3 attribute group . . . . . . . . . . . . . . . . . 39MCDS Error Group4 attribute group . . . . . . . . . . . . . . . . . 40MCDS Error Group5 attribute group . . . . . . . . . . . . . . . . . 41MCDS Error Group6 attribute group . . . . . . . . . . . . . . . . . 42MCDS Error Group7 attribute group . . . . . . . . . . . . . . . . . 44Migration Control Data Set Error Summary attribute group . . . . . . . . . 45OCDS Error Group1 attribute group . . . . . . . . . . . . . . . . . 47OCDS Error Group2 attribute group . . . . . . . . . . . . . . . . . 48OCDS Error Group3 attribute group . . . . . . . . . . . . . . . . . 49OCDS Error Group4 attribute group . . . . . . . . . . . . . . . . . 50OCDS Error Group5 attribute group . . . . . . . . . . . . . . . . . 52Offline Control Data Set Error Summary attribute group . . . . . . . . . . 53Performance Object Status attribute group. . . . . . . . . . . . . . . 54Product Advice attribute group . . . . . . . . . . . . . . . . . . . 57Disk capacity planning for historical data . . . . . . . . . . . . . . . 58

Chapter 5. Situations reference . . . . . . . . . . . . . . . . . . 61About situations . . . . . . . . . . . . . . . . . . . . . . . . 61More information about situations . . . . . . . . . . . . . . . . . . 61Predefined situations. . . . . . . . . . . . . . . . . . . . . . . 62IBM Tivoli Advanced Audit for DFSMShsm Navigator item . . . . . . . . . 62Agent Status Summary Navigator item . . . . . . . . . . . . . . . . 63Backup Control Data Set Error Summary Navigator item . . . . . . . . . 63

KRG_BCDS_Critical_Error situation . . . . . . . . . . . . . . . . 63HSEND List Event Information Navigator item . . . . . . . . . . . . . 63HSM Tape Error Summary Navigator item . . . . . . . . . . . . . . . 63

KRG_HSM_Tape_Critical_Errors situation . . . . . . . . . . . . . . 63LISTCAT Event Information Navigator item . . . . . . . . . . . . . . 64Migration Control Data Set Error Summary Navigator item . . . . . . . . . 64

KRG_MCDS_Critical_Error situation . . . . . . . . . . . . . . . . 64Offline Control Data Set Error Summary Navigator item . . . . . . . . . . 65

KRG_OCDS_Critical_Error situation . . . . . . . . . . . . . . . . 65

Chapter 6. Take Action commands reference . . . . . . . . . . . . . 67About Take Action commands . . . . . . . . . . . . . . . . . . . 67More information about Take Action commands . . . . . . . . . . . . . 67Predefined Take Action commands . . . . . . . . . . . . . . . . . 67HSEND_LIST_DSNAME action . . . . . . . . . . . . . . . . . . . 68HSEND_LIST_TTOC action . . . . . . . . . . . . . . . . . . . . 69LISTCAT_ENT action . . . . . . . . . . . . . . . . . . . . . . 70

Chapter 7. Policies reference . . . . . . . . . . . . . . . . . . . 73About policies . . . . . . . . . . . . . . . . . . . . . . . . . 73More information about policies . . . . . . . . . . . . . . . . . . . 73Predefined policies . . . . . . . . . . . . . . . . . . . . . . . 73

Chapter 8. Troubleshooting. . . . . . . . . . . . . . . . . . . . 75Gathering product information for IBM Software Support. . . . . . . . . . 75Built-in troubleshooting features. . . . . . . . . . . . . . . . . . . 75Problem classification . . . . . . . . . . . . . . . . . . . . . . 75Trace logging . . . . . . . . . . . . . . . . . . . . . . . . . 76

Overview of log file management . . . . . . . . . . . . . . . . . 76Principal trace log files . . . . . . . . . . . . . . . . . . . . . 76Setting RAS trace parameters . . . . . . . . . . . . . . . . . . 79

Problems and workarounds . . . . . . . . . . . . . . . . . . . . 81Installation and configuration troubleshooting . . . . . . . . . . . . . 81

iv IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent: User's Guide

Remote deployment troubleshooting . . . . . . . . . . . . . . . . 83Agent troubleshooting . . . . . . . . . . . . . . . . . . . . . 84Workspace troubleshooting . . . . . . . . . . . . . . . . . . . 85Situation troubleshooting . . . . . . . . . . . . . . . . . . . . 87Take Action commands troubleshooting . . . . . . . . . . . . . . . 90Tivoli Common Reporting troubleshooting . . . . . . . . . . . . . . 90

Support information . . . . . . . . . . . . . . . . . . . . . . . 90Informational, warning, and error messages . . . . . . . . . . . . . . 91

Message format . . . . . . . . . . . . . . . . . . . . . . . 91IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent messages . . . 92

Appendix A. IBM Tivoli Enterprise Console event mapping . . . . . . . 109

Appendix B. Documentation library . . . . . . . . . . . . . . . . 119IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent library . . . . . 119Prerequisite publications . . . . . . . . . . . . . . . . . . . . . 119Related publications . . . . . . . . . . . . . . . . . . . . . . 120Other sources of documentation . . . . . . . . . . . . . . . . . . 120

Appendix C. Accessibility . . . . . . . . . . . . . . . . . . . . 121Navigating the interface using the keyboard . . . . . . . . . . . . . . 121Magnifying what is displayed on the screen . . . . . . . . . . . . . . 121

Appendix D. Notices . . . . . . . . . . . . . . . . . . . . . . 123Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 124

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contents v

vi IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent: User's Guide

Tables

1. Capacity planning for historical data logged by Advanced Audit for DFSMShsm . . . . . . . . 592. Information to gather before contacting IBM Software Support . . . . . . . . . . . . . . 753. Trace log files for troubleshooting agents . . . . . . . . . . . . . . . . . . . . . . 774. Problems and solutions for installation and configuration . . . . . . . . . . . . . . . . 825. General problems and solutions for uninstallation . . . . . . . . . . . . . . . . . . . 836. Remote deployment problems and solutions . . . . . . . . . . . . . . . . . . . . . 847. Agent problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . 848. Workspace problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . 869. General situation problems and solutions . . . . . . . . . . . . . . . . . . . . . . 87

10. Problems with configuring situations that you solve in the Situation Editor . . . . . . . . . . 8811. Problems with configuration of situations that you solve in the Workspace area . . . . . . . . 8912. Take Action commands problems and solutions . . . . . . . . . . . . . . . . . . . 9013. Tivoli Common Reporting for IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent

problems and solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

© Copyright IBM Corp. 2010 vii

viii IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent: User's Guide

Chapter 1. Overview of the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent

The IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent provides you withthe capability to monitor IBM Tivoli Advanced Audit for DFSMShsm, and to performbasic actions with IBM Tivoli Advanced Audit for DFSMShsm. This chapter providesa description of the features, components, and interface options for the IBM TivoliAdvanced Audit for DFSMShsm Monitoring Agent.

IBM Tivoli Monitoring overviewIBM Tivoli Monitoring is the base software for the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent. IBM Tivoli Monitoring provides a way to monitor theavailability and performance of all the systems in your enterprise from one orseveral designated workstations. It also provides useful historical data that you canuse to track trends and to troubleshoot system problems.

You can use IBM Tivoli Monitoring to perform the following tasks:

v Monitor for alerts on the systems that you are managing by using predefinedsituations or custom situations.

v Establish your own performance thresholds.

v Trace the causes leading to an alert.

v Gather comprehensive data about system conditions.

v Use policies to perform actions, schedule work, and automate manual tasks.

The Tivoli Enterprise Portal is the interface for IBM Tivoli Monitoring products. Byproviding a consolidated view of your environment, the Tivoli Enterprise Portalpermits you to monitor and resolve performance issues throughout the enterprise.

See the IBM Tivoli Monitoring publications listed in “Prerequisite publications” onpage 119 for complete information about IBM Tivoli Monitoring and the TivoliEnterprise Portal.

Features of the monitoring agentThe IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent software canidentify, notify you of, and correct common problems with the application that itmonitors. The software includes the following features:

v Monitoring

v Data gathering

v Event management

v Operations management

Functions of the monitoring agentThe IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent provides thefollowing functions:

Advanced Audit for DFSMShsm TEP EnablementProvide TEP enablement for Advanced Audit for DFSMShsm

© Copyright IBM Corp. 2010 1

New in this releaseFor version 2.3 of the IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent,the following enhancements have been made since version 2.2, including the fixpacks:

v New attribute group: Product Advice. This attribute group provides detailedinformation regarding Advanced Audit Error IDs and suggestions for correctiveactions.

Components of the IBM Tivoli Monitoring environmentAfter you install and set up the IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent, you have an environment that contains the client, server, andmonitoring agent implementation for IBM Tivoli Monitoring that contains thefollowing components:

v Tivoli Enterprise Portal client with a Java™-based user interface for viewing andmonitoring your enterprise.

v Tivoli Enterprise Portal Server that is placed between the client and the TivoliEnterprise Monitoring Server and enables retrieval, manipulation, and analysis ofdata from the monitoring agents. The Tivoli Enterprise Portal Server is the centralrepository for all user data.

v Tivoli Enterprise Monitoring Server that acts as a collection and control point foralerts received from the monitoring agents, and collects their performance andavailability data. The Tivoli Enterprise Monitoring Server is also a repository forhistorical data.

v Tivoli Enterprise Monitoring Agent, IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent. This monitoring agent collects and distributes data to a TivoliEnterprise Portal Server.

IBM Tivoli Enterprise Console is an optional component, which acts as a centralcollection point for events from a variety of sources, including those from otherTivoli® software applications, Tivoli partner applications, custom applications,network management platforms, and relational database systems. You can viewthese events through the Tivoli Enterprise Portal (using the event viewer), and youcan forward events from IBM Tivoli Monitoring situations to the IBM Tivoli EnterpriseConsole component.

User interface optionsInstallation of the base software and other integrated applications provides thefollowing interfaces that you can use to work with your resources and data:

Tivoli Enterprise Portal browser client interfaceThe browser client interface is automatically installed with the TivoliEnterprise Portal Server. To start the Tivoli Enterprise Portal browser clientin your Internet browser, enter the URL for a specific Tivoli Enterprise Portalbrowser client installed on your Web server.

Tivoli Enterprise Portal desktop client interfaceThe desktop client interface is a Java-based graphical user interface (GUI)on a Windows® or Linux® workstation.

IBM Tivoli Enterprise ConsoleAn event management application that integrates system, network,database, and application management to help ensure the optimalavailability of an IT services for an organization.

2 IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent: User's Guide

Manage Tivoli Enterprise Monitoring Services windowThe window for the Manage Tivoli Enterprise Monitoring Services utility isused for configuring the agent and starting Tivoli services not alreadydesignated to start automatically.

Chapter 1. Overview of the IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent 3


Chapter 2. Requirements for the monitoring agent

This chapter contains information about the requirements for the IBM TivoliAdvanced Audit for DFSMShsm Monitoring Agent.

To install and configure the IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent, use the procedures for installing monitoring agents in the IBM TivoliMonitoring Installation and Setup Guide.

If you are performing a silent installation using a response file, see the informationabout performing a silent installation in the IBM Tivoli Monitoring Installation andSetup Guide.

Requirements for the monitoring agentIn addition to the requirements described in the IBM Tivoli Monitoring Installationand Setup Guide, the IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agenthas the following requirements:

v The monitoring agent runs on any of these operating systems:

– Windows 2003 Server SE (32 bit) with Service Pack 1 or higher

If running this monitoring agent on a Windows operating system, the User IDmust have Administrator privileges.

Note: For the most current information about the operating systems that aresupported, see http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html.

v This agent monitors the following versions:

– IBM Tivoli Advanced Audit for DFSMShsm 2.3

v A single computer that hosts the hub monitoring server, portal server, and amonitoring agent requires approximately 300 MB of space. A computer that hostsonly the monitoring agent requires approximately 30 MB of space, including thespecific enablement code for the monitoring agent. More space is required foreach additional monitoring agent that you deploy on the monitoring computer.

v The monitoring agent must be connected to the following software:

– IBM Tivoli Monitoring V6.2

After you install the prerequisite software, install the following software, which isrequired for the IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent tooperate:

– IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent

– IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent for TivoliEnterprise Monitoring Server support

– IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent for TivoliEnterprise Portal Server support

– IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent for TivoliEnterprise Portal Desktop Client support

– IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent for TivoliEnterprise Portal Browser Client support


http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

http://www-306.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

Installing language packsTo install a language pack, first make sure that you have already installed theproduct in English, then perform the following steps depending on which operatingsystem you are using.

Windows systems1. Double-click lpinstaller.bat in the language pack CD to launch the installation

program.

2. Select the language of the installer and click OK.

3. Click Next on the Introduction panel.

4. Click Add/Update and click Next.

5. Select the folder in which the National Language Support package(NLSPackage) files are located.

Note: Usually the NLSPackage files are located in the nlspackage folderwhere the installer executable is located.

6. Select the language support for the agent of your choice and click Next.

Note: Hold down the Ctrl key for multiple selections.

7. Select the languages that you want to install and click Next.

8. Examine the installation summary page and click Next to begin installation.

9. Click Finish after installation completes to exit the installer.

10. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server,and Eclipse Help Server if any of these components are installed.

UNIX or Linux systems1. Run the following command to create a temporary directory on the computer.

Make sure that the full path of the directory does not contain any spaces:mkdir dir_name

2. Mount the language pack CD to the temporary directory you just created.

3. Run the following command to launch the installation program:cd dir_namelpinstaller.sh -c ITM Home Directory

Where ITM Home Directory is where you installed IBM Tivoli Monitoring.Usually it is /opt/IBM/ITM for AIX and Linux.

4. Select the language of the installer and click OK.

5. Click Next on the Introduction panel.

6. Click Add/Update and click Next.

7. Select the folder in which the National Language Support package(NLSPackage) files are located.

Note: Usually, the NLSPackage files are located in the nlspackage folderwhere the installer executable is located.

8. Select the language support for the agent of your choice and click Next.

Note: Hold down the Ctrl key for multiple selections.

9. Select the languages that you want to install and click Next.

10. Examine the installation summary page and click Next to begin installation.


11. Click Finish after installation completes to exit the installer.

12. Restart Tivoli Enterprise Portal Desktop Client, Tivoli Enterprise Portal Server,and Eclipse Help Server if any of these components are installed.

Chapter 2. Requirements for the monitoring agent 7


Chapter 3. Workspaces reference

This chapter contains an overview of workspaces, references for detailedinformation about workspaces, and descriptions of the predefined workspacesincluded in this monitoring agent.

About workspacesA workspace is the working area of the Tivoli Enterprise Portal application window.At the left of the workspace is a Navigator that you use to select the workspace youwant to see. As part of the application window, the right side of the status barshows the Tivoli Enterprise Portal server name and port number to which thedisplayed information applies, and the ID of the current user.

When you select an item in the Navigator tree, a default workspace is displayed.When you right-click a Navigator item, a menu that includes a Workspace item isdisplayed. The Workspace item contains a list of workspaces for that Navigatoritem. Each workspace has at least one view. Some views have links to otherworkspaces.

This monitoring agent provides predefined workspaces. You cannot modify or deletethe predefined workspaces, but you can create new workspaces by editing themand saving the changes with a different name.

A table view within a workspace corresponds to a group of attributes; the columnsin the table view show some or all of the attributes available in the attribute group.

More information about workspacesFor more information about creating, customizing, and working with workspaces,see the Tivoli Enterprise Portal User's Guide.

For a list of the predefined workspaces for this monitoring agent and a descriptionof each workspace, refer to the Predefined workspaces section in this chapter andthe information in that section for each individual workspace.

Some attribute groups for this monitoring agent might not be represented in thepredefined workspaces or views for this agent. For a full list of the attribute groups,see the Attributes reference section.

Predefined workspaces

The IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent provides thefollowing predefined workspaces, which are organized by Navigator item.

v IBM Tivoli Advanced Audit for DFSMShsm Navigator item

– IBM Tivoli Advanced Audit for DFSMShsm workspace

v Agent Status Summary Navigator item

– Agent Status Summary workspace

v Backup Control Data Set Error Summary Navigator item

– Backup Control Data Set Error Summary workspace

v HSEND List Event Information Navigator item

– HSEND List Event Information workspace


v HSM Tape Error Summary Navigator item

– HSM Tape Error Summary workspace

v LISTCAT Event Information Navigator item

– LISTCAT Event Information workspace

v Migration Control Data Set Error Summary Navigator item

– Migration Control Data Set Error Summary workspace

v Offline Control Data Set Error Summary Navigator item

– Offline Control Data Set Error Summary workspace

Agent Navigator itemsThis section contains descriptions of predefined workspaces. The workspaces areorganized by the Navigator item to which the workspaces are relevant.

IBM Tivoli Advanced Audit for DFSMShsm Navigator itemIBM Tivoli Advanced Audit for DFSMShsm workspace

This workspace provides a graphical summary of DFSMShsm errorsreceived.

This workspace contains the following views:

HSM Tape Error SummaryGraphical summaries of DFSMShsm errors

BCDS Error SummaryGraphical summaries of DFSMShsm errors

MCDS Error SummaryGraphical summaries of DFSMShsm errors

OCDS Error SummaryGraphical summaries of DFSMShsm errors

Agent Status Summary Navigator itemAgent Status Summary workspace

Error message report summary.


Agent Object StatusReport summaries of DFSMShsm errors received.

BCDS Error IDs Exceeding Message LimitReport summaries of DFSMShsm errors received.

MCDS Error IDs Exceeding Message LimitReport summaries of DFSMShsm errors received.

OCDS Error IDs Exceeding Message LimitReport summaries of DFSMShsm errors received.

HSM Tape Error IDs Exceeding Message LimitReport summaries of DFSMShsm errors received.


Backup Control Data Set Error Summary Navigator itemBackup Control Data Set Error Summary workspace

This workspace contains report and graphical information on DFSMShsmBCDS errors.


Backup Control Data Set Error SummaryReport and graphical information of DFSMShsm BCDS errors.

BCDS Error SummaryReport and graphical information of DFSMShsm BCDS errors.

HSEND List Event Information Navigator itemHSEND List Event Information workspace

HSEND List Event Information workspace provides information on eventdetails.

This workspace contains the following view:

HSEND List Event InformationShows HSEND commands issued as a result of Take Action.

HSM Tape Error Summary Navigator itemHSM Tape Error Summary workspace

The Return Code Summary workspace provides summary information forHSM Tape Error.


HSM Tape Error SummaryHSM Tape Error Summary.

LISTCAT Event Information Navigator itemLISTCAT Event Information workspace

LISTCAT Event Information workspace provides results from the LISTCATTake Action.


LISTCAT Event InformationShows LISTCAT commands and their output issued as a result ofTake Action.

Migration Control Data Set Error Summary Navigator itemMigration Control Data Set Error Summary workspace

This workspace contains report and graphical information on DFSMShsmMCDS errors.


Migration Control Data Set Error SummaryReport and graphical information of DFSMShsm MCDS errors.

MCDS Error SummaryReport and graphical information of DFSMShsm MCDS errors.

Chapter 3. Workspaces reference 11

Offline Control Data Set Error Summary Navigator itemOffline Control Data Set Error Summary workspace

This workspace contains report and graphical information on DFSMShsmOCDS errors.


Offline Control Data Set Error SummaryReport and graphical information of DFSMShsm OCDS errors.

OCDS Error SummaryReport and graphical information of DFSMShsm OCDS errors.


Chapter 4. Attributes reference

This chapter contains an overview of attributes, references for detailed informationabout attributes, and descriptions of the attributes for each attribute group includedin this monitoring agent.

About attributesAttributes are the application properties being measured and reported by the IBMTivoli Advanced Audit for DFSMShsm Monitoring Agent.

Attributes are organized into groups according to their purpose. The attributes in agroup can be used in the following two ways:

v Chart or table views

Attributes are displayed in chart and table views. The chart and table views usequeries to specify which attribute values to request from a monitoring agent. Youuse the Query editor to create a new query, modify an existing query, or applyfilters and set styles to define the content and appearance of a view based on anexisting query.

v Situations

You use attributes to create situations that monitor the state of your operatingsystem, database, or application. A situation describes a condition you want totest. When you start a situation, the Tivoli Enterprise Portal compares the valuesyou have assigned to the situation attributes with the values collected by the IBMTivoli Advanced Audit for DFSMShsm Monitoring Agent and registers an event ifthe condition is met. You are alerted to events by indicator icons that aredisplayed in the Navigator.

More information about attributesFor more information about using attributes and attribute groups, see the TivoliEnterprise Portal User's Guide.

For a list of the attributes groups, a list of the attributes in each attribute group, anddescriptions of the attributes for this monitoring agent, see the Attribute groups andattributes section in this chapter.

Attribute groups and attributes for the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent

This monitoring agent contains the following attribute groups. The table namedepends on the maximum table name limits of the target database being used forTivoli Data Warehouse. If the maximum name is 30 characters, then any warehousetable name longer than 30 characters is shortened to the table name.

v Attribute group name: Agent Status Summary

– Table name: KRGAGTERRM

– Warehouse table name: KRG_AGENT_STATUS_SUMMARY orKRGAGTERRM

v Attribute group name: Backup Control Data Set Error Summary

– Table name: KRGBCDSUM


– Warehouse table name:KRG_BACKUP_CONTROL_DATA_SET_ERROR_SUMMARY orKRGBCDSUM

v Attribute group name: BCDS Error Group1

– Table name: KRGBCDEG1

– Warehouse table name: KRG_BCDS_ERROR_GROUP1 or KRGBCDEG1






















v Attribute group name: Product Advice

– Table name: KRGAAEXPAV

– Warehouse table name: KRG_EXPERT_ADVICE or KRGAAEXPAV

v Attribute group name: HSEND List Event Information

– Table name: KRGZHEVENT

– Warehouse table name: KRG_HSEND_LIST_EVENT_INFORMATION orKRGZHEVENT

v Attribute group name: HSM Tape Error Summary

– Table name: KRGTAPSUM

– Warehouse table name: KRG_HSM_TAPE_ERROR_SUMMARY orKRGTAPSUM

v Attribute group name: HSMTAPE Error Group1

– Table name: KRGTPDEG1

– Warehouse table name: KRG_HSMTAPE_ERROR_GROUP1 or KRGTPDEG1

v Attribute group name: HSMTAPE Error Group2

– Table name: KRGTPDEG2

– Warehouse table name: KRG_HSMTAPE_ERROR_GROUP2 or KRGTPDEG2

v Attribute group name: LISTCAT Event Information

– Table name: KRGZLEVENT


– Warehouse table name: KRG_LISTCAT_EVENT_INFORMATION orKRGZLEVENT

v Attribute group name: MCDS Error Group1

– Table name: KRGMCDEG1

– Warehouse table name: KRG_MCDS_ERROR_GROUP1 or KRGMCDEG1



















v Attribute group name: Migration Control Data Set Error Summary

– Table name: KRGMCDSUM

– Warehouse table name:KRG_MIGRATION_CONTROL_DATA_SET_ERROR_SUMMARY orKRGMCDSUM

v Attribute group name: OCDS Error Group1

– Table name: KRGOCDEG1

– Warehouse table name: KRG_OCDS_ERROR_GROUP1 or KRGOCDEG1













v Attribute group name: Offline Control Data Set Error Summary

– Table name: KRGOCDSUM

Chapter 4. Attributes reference 15

– Warehouse table name:KRG_OFFLINE_CONTROL_DATA_SET_ERROR_SUMMARY orKRGOCDSUM

v Attribute group name: Performance Object Status

– Table name: KRGPOBJST

– Warehouse table name: KRG_PERFORMANCE_OBJECT_STATUS orKRGPOBJST

The remaining sections of this chapter contain descriptions of these attributegroups, which are listed alphabetically. The following information is provided foreach attribute group:

Historical groupWhether the attribute group is a historical type that you can roll off to a datawarehouse

Attribute descriptionsDescription, type, and Warehouse name for each attribute in the attributegroup

Some attributes are designated as key attributes. A key attribute is anattribute that is used in warehouse aggregation to identify rows of data thatrepresent the same object.

Agent Status Summary attribute group

Agent error messages If the warehouse default setting is enabled, data for thisattribute group is stored in Tivoli Data Warehouse.

Historical groupThis attribute group is part of the default historical group, and is eligible for use withTivoli Data Warehouse.

Attribute descriptionsThe following list contains information about each attribute in the Agent StatusSummary attribute group:

Node attribute - This attribute is a key attribute.

DescriptionThe managed system name of the agent.

Type String

Timestamp attribute

DescriptionThe local time at the agent when the data was collected.

Type String

Error Sequence Number attribute - This attribute is a key attribute.

DescriptionError sequence number

Type Integer (Counter) with enumerated values. The strings are displayedin the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:


v Value_Exceeds_Maximum (2147483647)

v Value_Exceeds_Minimum (-2147483648)

Any other values will display the actual value returned by the agentin the Tivoli Enterprise Portal.

Attribute Group attribute

DescriptionAttribute group error message applies to.

Type String

Error Message attribute

DescriptionError message

Type String

Backup Control Data Set Error Summary attribute group

Backup Control Data Set Error Summary If the warehouse default setting isenabled, data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Backup ControlData Set Error Summary attribute group:



Type String

Timestamp attribute


Type String

Error ID attribute - This attribute is a key attribute.

DescriptionDiagnostic error ID

Type String

Record Count attribute

DescriptionDiagnostic record count







DescriptionDiagnostic error message

Type String

Error Count attribute

DescriptionDiagnostic error count





Error Type attribute

DescriptionError format type





BCDS Error Group1 attribute group

Backup control data set error group 1 If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the BCDS ErrorGroup1 attribute group:



Type String

Timestamp attribute



Type String



Type String

Data Set Name attribute

DescriptionData set name

Type String

HSM Internal Data Set Name attribute

DescriptionHSM internal data set name

Type String

Backup Date attribute

DescriptionBackup date

Type String

VSAM Flag attribute

DescriptionVSAM or non-VSAM

Type Integer with enumerated values. The strings are displayed in theTivoli Enterprise Portal. The warehouse and queries return thevalues shown in parentheses. The following values are defined:

v Non-VSAM (0)

v VSAM (1)


Backup Version attribute

DescriptionBackup version number





Volser attribute

DescriptionVolser

Type String








Type String

Timestamp attribute


Type String



Type String



Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String

VSAM Flag attribute




v Non-VSAM (0)

v VSAM (1)


Tape/DASD attribute

DescriptionTape or DASD


v Tape (0)

v DASD (1)



DescriptionBackup version number





Backup Generation attribute

DescriptionBackup generation number

Type String

HSM Tape Type attribute

DescriptionHSM tape type

Type String

TTOC Extension Number attribute

DescriptionTTOC extension number






Primary Volser attribute

DescriptionPrimary volser

Type String







Type String

Timestamp attribute


Type String



Type String



Type String



Type String

Volser attribute

DescriptionVolser

Type String




Type String

VSAM Flag attribute



v Non-VSAM (0)

v VSAM (1)


Tape/DASD attribute



v Tape (0)

v DASD (1)


VTOC Error attribute

DescriptionVTOC Error












Type String

Timestamp attribute


Type String



Type String



Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String

VSAM Flag attribute



v Non-VSAM (0)

v VSAM (1)


Tape/DASD attribute




v Tape (0)

v DASD (1)



DescriptionBackup version





Backup Owner attribute

DescriptionBackup owner

Type String







Type String

Timestamp attribute


Type String




Type String

Volser attribute

DescriptionVolser

Type String



Type String

Tape Reference Count attribute

DescriptionTape reference count











Type String

Timestamp attribute


Type String




Type String

Volser attribute

DescriptionVolser

Type String



Type String

Valid Blocks attribute

DescriptionCounted valid blocks





Block Count attribute

DescriptionBlock count (TTOC)





TTOC/Update Date attribute

DescriptionTTOC update date

Type String

TTOC/Create Date attribute

DescriptionTTOC create date

Type String








Type String

Timestamp attribute


Type String



Type String

Migrate Volser attribute

DescriptionMigrate volser

Type String



Type String







Data Set Name Flag attribute

DescriptionData set name flag

Type String

Data set Patch Valid Flag attribute


DescriptionData set patch valid flag

Type String

TTOC Data Set Offset attribute

DescriptionOffset to data set in TTOC





TTOC Flag Offset attribute

DescriptionOffset to flag byte in TTOC





Alias Name attribute

DescriptionAlias name in TTOC

Type String

True Name attribute

DescriptionTrue name from BCD/MCC

Type String








Type String

Timestamp attribute


Type String



Type String

Duplicate Volser attribute

DescriptionVolser of Duplicate

Type String

Volume Type attribute

DescriptionVolume Type

Type String

Status attribute

DescriptionStatus

Type String

Conflicting Volser attribute

DescriptionConflicting Volser

Type String

Volume Type attribute

DescriptionVolume Type

Type String

Status attribute

DescriptionStatus

Type String

HSEND List Event Information attribute group

The attribute group provides event information from the HSEND List command. Ifthe warehouse default setting is enabled, data for this attribute group is stored inTivoli Data Warehouse.



Attribute descriptionsThe following list contains information about each attribute in the HSEND List EventInformation attribute group:



Type String

Timestamp attribute


Type String

Command attribute - This attribute is a key attribute.

DescriptionCommand issued.

Type String

Timestamp attribute

DescriptionTime when command was issued

Type Timestamp

User ID attribute

DescriptionUser ID used to issue the command.

Type String

Request Result attribute

DescriptionResult from the command issued.

Type String

Row Counter attribute

DescriptionShould be hidden.






HSM Tape Error Summary attribute group

HSM Tape Error Summary If the warehouse default setting is enabled, data for thisattribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the HSM Tape ErrorSummary attribute group:



Type String

Timestamp attribute


Type String



Type String









Type String














HSMTAPE Error Group1 attribute group

Tape error group 1 If the warehouse default setting is enabled, data for this attributegroup is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the HSMTAPE ErrorGroup1 attribute group:



Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String




Type String

Data Set Count attribute

DescriptionNumber of data sets





HSMTAPE Error Group2 attribute group

Tape error group 2 If the warehouse default setting is enabled, data for this attributegroup is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the HSMTAPE ErrorGroup2 attribute group:



Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String




Type String

Data Set Count attribute

DescriptionNumber of data sets





Expire Date attribute

DescriptionExpire date

Type String

Tape Data Set Name attribute

DescriptionTape data set name

Type String

Create Job Name attribute

DescriptionCreate job name

Type String

LISTCAT Event Information attribute group

The attribute group provides information from Listcat command. If the warehousedefault setting is enabled, data for this attribute group is stored in Tivoli DataWarehouse.


Attribute descriptionsThe following list contains information about each attribute in the LISTCAT EventInformation attribute group:



Type String

Timestamp attribute



Type String

Command attribute - This attribute is a key attribute.

DescriptionCommand issued.

Type String

Timestamp attribute

DescriptionTime when command was issued

Type Timestamp

User ID attribute

DescriptionUser ID used to issue the command.

Type String

Request Result attribute

DescriptionResult from the command issued.

Type String

Row Counter attribute

DescriptionShould be hidden.





MCDS Error Group1 attribute group

Migration control data set error group 1 If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the MCDS ErrorGroup1 attribute group:




Type String

Timestamp attribute


Type String



Type String



Type String



Type String

HSM Volser attribute

DescriptionHSM Volser

Type String

VSAM Flag attribute



v Non-VSAM (0)

v VSAM (1)


HSM Level attribute

DescriptionHSM Level

Type String

Cataloged Volser attribute

DescriptionCataloged Volser

Type String

Catalog Data Set Name attribute


DescriptionCatalog data set name

Type String







Type String

Timestamp attribute


Type String



Type String

VSAM Cluster Data Set Name attribute

DescriptionVSAM cluster data set name

Type String

VSAM Component Name attribute

DescriptionVSAM component name

Type String

HSM Alias Data Set Name attribute

DescriptionHSM generated alias data set name

Type String




Type String







Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String

Tape Reference Count attribute

DescriptionNumber of data sets referencing tape












Type String

Timestamp attribute


Type String



Type String



Type String



Type String



Type String

Create Date attribute

DescriptionCreate date

Type String








Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String

Valid Blocks attribute

DescriptionCounted valid blocks





Block Count attribute


DescriptionBlock count (TTOC)





Counted Records (Hex) attribute

DescriptionHex value of counted records

Type String

Valid TTOC Records (Hex) attribute

DescriptionHex value of valid TTOC records

Type String

TTOC/Update Date attribute

DescriptionTTOC update date

Type String

TTOC/Create Date attribute

DescriptionTTOC create date

Type String







Type String

Timestamp attribute



Type String



Type String

Migrate Volser attribute

DescriptionMigrate volser

Type String



Type String







Data Set Name Flag attribute

DescriptionData set name flag

Type String

Data Set Patch Valid Flag attribute

DescriptionData set patch valid flag

Type String

TTOC Data Set Offset attribute

DescriptionOffset to data set in TTOC






TTOC Flag Offset attribute

DescriptionOffset to flag byte in TTOC





Alias Name attribute

DescriptionAlias name in TTOC

Type String

True Name attribute

DescriptionTrue name from MCD/MCC

Type String







Type String

Timestamp attribute


Type String



Type String




Type String



Type String



Type String

VSAM Flag attribute



v Non-VSAM (0)

v VSAM (1)


HSM Level attribute

DescriptionHSM Level

Type String



Type String



Type String

Migration Control Data Set Error Summary attribute group

Migration Control Data Set Error Summary If the warehouse default setting isenabled, data for this attribute group is stored in Tivoli Data Warehouse.



Attribute descriptionsThe following list contains information about each attribute in the Migration ControlData Set Error Summary attribute group:



Type String

Timestamp attribute


Type String



Type String









Type String









Type Integer (Counter) with enumerated values. The strings are displayed


in the Tivoli Enterprise Portal. The warehouse and queries returnthe values shown in parentheses. The following values are defined:




OCDS Error Group1 attribute group

Offline control data set error group 1 If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the OCDS ErrorGroup1 attribute group:



Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String



Type String

Previous Volume in OCDS attribute


DescriptionPrevious volume in OCDS

Type String

Correct Previous Volume attribute

DescriptionCorrect previous volume (hex)

Type String

First Data Set attribute

DescriptionFirst data set on tape

Type String







Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String




Type String



Type String

Successor Volume in OCDS attribute

DescriptionSuccessor volume in OCDS

Type String

Correct Successor Volume attribute

DescriptionCorrect successor volume (hex)

Type String

Last Data Set attribute

DescriptionLast data set on tape

Type String







Type String

Timestamp attribute


Type String



Type String

Volser attribute


DescriptionVolser

Type String



Type String



Type String

Expected Sequence Number attribute

DescriptionExpected sequence number





Encountered Sequence Number attribute

DescriptionEncountered sequence number












Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String



Type String

Expected Extention Number attribute

DescriptionExpected extention number





Encountered Extention Number attribute

DescriptionEncountered extention number












Type String

Timestamp attribute


Type String



Type String

Volser attribute

DescriptionVolser

Type String



Type String



Type String

Expected Block Count attribute

DescriptionExpected block count






Encountered Block Count attribute

DescriptionEncountered block count





Offline Control Data Set Error Summary attribute group

Offline Control Data Set Error Summary If the warehouse default setting is enabled,data for this attribute group is stored in Tivoli Data Warehouse.


Attribute descriptionsThe following list contains information about each attribute in the Offline ControlData Set Error Summary attribute group:



Type String

Timestamp attribute


Type String



Type String










Type String













Performance Object Status attribute group

The Performance Object Status attribute group contains information that reflects thestatus of other attribute groups so you can see the status of all of the performanceobjects that make up this application all at once. Each of these other performanceattribute groups is represented by a row in this table (or other type of view). Thestatus for an attribute group reflects the result of the last attempt to collect data forthat attribute group, which allows you to see whether the agent is performingcorrectly. Unlike other attribute groups, the Performance Object Status attributegroup does not reflect the state of the monitored application. This attribute group ismost often used to determine why data is not available for one of the performanceattribute groups. If the warehouse default setting is enabled, data for this attributegroup is stored in Tivoli Data Warehouse.



Attribute descriptionsThe following list contains information about each attribute in the PerformanceObject Status attribute group:



Type String

Timestamp attribute


Type String

Query Name attribute - This attribute is a key attribute.

DescriptionThe name of the attribute group.

Type String

Object Name attribute

DescriptionThe name of the performance object.

Type String

Object Type attribute

DescriptionThe type of the performance object.


v WMI (0)

v PERFMON (1)

v WMI_ASSOCIATION_GROUP (2)

v JMX (3)

v SNMP (4)

v SHELL_COMMAND (5)

v JOINED_GROUPS (6)

v CIMOM (7)

v CUSTOM (8)

v ROLLUP_DATA (9)

v WMI_REMOTE_DATA (10)

v LOG_FILE (11)

v JDBC (12)

v CONFIG_DISCOVERY (13)

v NT_EVENT_LOG (14)

v FILTER (15)



Object Status attribute

DescriptionThe status of the performance object.


v ACTIVE (0)

v INACTIVE (1)


Error Code attribute

DescriptionThe error code associated with the query


v NO_ERROR (0)

v GENERAL_ERROR (1)

v OBJECT_NOT_FOUND (2)

v COUNTER_NOT_FOUND (3)

v NAMESPACE_ERROR (4)

v OBJECT_CURRENTLY_UNAVAILABLE (5)

v COM_LIBRARY_INIT_FAILURE (6)

v SECURITY_INIT_FAILURE (7)

v PROXY_SECURITY_FAILURE (9)

v NO_INSTANCES_RETURNED (10)

v ASSOCIATOR_QUERY_FAILED (11)

v REFERENCE_QUERY_FAILED (12)

v NO_RESPONSE_RECEIVED (13)

v CANNOT_FIND_JOINED_QUERY (14)

v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_1_RESULTS(15)

v CANNOT_FIND_JOIN_ATTRIBUTE_IN_QUERY_2_RESULTS(16)

v QUERY_1_NOT_A_SINGLETON (17)

v QUERY_2_NOT_A_SINGLETON (18)

v NO_INSTANCES_RETURNED_IN_QUERY_1 (19)

v NO_INSTANCES_RETURNED_IN_QUERY_2 (20)

v CANNOT_FIND_ROLLUP_QUERY (21)

v CANNOT_FIND_ROLLUP_ATTRIBUTE (22)

v FILE_OFFLINE (23)

v NO_HOSTNAME (24)

v MISSING_LIBRARY (25)

v ATTRIBUTE_COUNT_MISMATCH (26)

v ATTRIBUTE_NAME_MISMATCH (27)


v COMMON_DATA_PROVIDER_NOT_STARTED (28)

v CALLBACK_REGISTRATION_ERROR (29)

v MDL_LOAD_ERROR (30)

v AUTHENTICATION_FAILED (31)

v CANNOT_RESOLVE_HOST_NAME (32)

v SUBNODE_UNAVAILABLE (33)

v SUBNODE_NOT_FOUND_IN_CONFIG (34)

v ATTRIBUTE_ERROR (35)

v CLASSPATH_ERROR (36)

v CONNECTION_FAILURE (37)

v FILTER_SYNTAX_ERROR (38)

v FILE_NAME_MISSING (39)

v SQL_QUERY_ERROR (40)

v SQL_FILTER_QUERY_ERROR (41)

v SQL_DB_QUERY_ERROR (42)

v SQL_DB_FILTER_QUERY_ERROR (43)

v PORT_OPEN_FAILED (44)

v ACCESS_DENIED (45)

v TIMEOUT (46)

v NOT_IMPLEMENTED (47)

v REQUESTED_A_BAD_VALUE (48)

v RESPONSE_TOO_BIG (49)

v GENERAL_RESPONSE_ERROR (50)

v SCRIPT_NONZERO_RETURN (51)

v SCRIPT_NOT_FOUND (52)

v SCRIPT_LAUNCH_ERROR (53)


Product Advice attribute group

The attribute group provides product advice for errors reported by Advanced Auditfor DFSMShsm. If the warehouse default setting is enabled, data for this attributegroup is stored in Tivoli Data Warehouse.

The Error Summary reports (BCDS, MCDS, OCDS, and HSM Tape) all providepredefined links to the Product Advice workspace. This workspace provides detailedinformation regarding Advanced Audit Error IDs and suggestions for correctiveactions. This Advice text is often too large to be displayed within the report column,but the complete text may be viewed by placing the mouse on the text that is there.


Attribute descriptionsThe following list contains information about each attribute in the Product Adviceattribute group:




Type String

Timestamp attribute


Type String


DescriptionError ID

Type String

Product Advice Heading attribute

DescriptionBrief description of error

Type String

Product Advice attribute

DescriptionProduct Advice for the error.

Type String

Disk capacity planning for historical dataDisk capacity planning for a monitoring agent is a prediction of the amount of diskspace to be consumed for each attribute group whose historical data is beingcollected. Required disk storage is an important factor to consider when you aredefining data collection rules and your strategy for historical data collection.

The table in this chapter provides the following information required to calculate diskspace for this monitoring agent:

v Table is the table name as it is displayed in the warehouse database, if theattribute group is configured to be written to the warehouse.

v Attribute group is the name of the attribute group as it is displayed in thewarehouse configuration panel.

v Bytes per instance (agent) is an estimate of the record length for each row orinstance written to the agent disk for historical data collection. This estimate canbe used for agent disk space planning purposes.

v Database bytes per instance (warehouse) is an estimate of the record length fordetailed records written to the warehouse database, if the attribute group isconfigured to be written to the warehouse. Detailed records are those that havebeen uploaded from the agent for long-term historical data collection. Thisestimate can be used for warehouse disk space planning purposes.

v Aggregate bytes per instance (warehouse) is an estimate of the record length foraggregate records written to the warehouse database, if the attribute group isconfigured to be written to the warehouse. Aggregate records are created by theSummarization agent for attribute groups that have been configured forsummarization. This estimate can be used for warehouse disk space planningpurposes.


In addition to the information in the tables, you must know the number of instancesof data that you plan to collect. An attribute group can have single or multipleinstances of data depending on the application environment that is being monitored.For example, if your attribute group is monitoring each processor in your computerand you have a dual processor computer, the number of instances is two.

The following table contains capacity planning information for the data logged byIBM Tivoli Advanced Audit for DFSMShsm.

Table 1. Capacity planning for historical data logged by Advanced Audit for DFSMShsm

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

KRGAGTERRM KRG_AGENT_STATUS_SUMMARY 230 229 266

KRGBCDSUM KRG_BACKUP_CONTROL_DATA_SET_ERROR_\SUMMARY

153 154 236

KRGBCDEG1 KRG_BCDS_ERROR_GROUP1 190 193 245








KRGAAEXPAV KRG_EXPERT_ADVICE 2169 2172 2209

KRGZHEVENT KRG_HSEND_LIST_EVENT_INFORMATION 238 239 291

KRGTPDEG1 KRG_HSMTAPE_ERROR_GROUP1 93 93 145

KRGTPDEG2 KRG_HSMTAPE_ERROR_GROUP2 152 155 207

KRGTAPSUM KRG_HSM_TAPE_ERROR_SUMMARY 153 154 236

KRGZLEVENT KRG_LISTCAT_EVENT_INFORMATION 245 246 298

KRGMCDEG1 KRG_MCDS_ERROR_GROUP1 230 234 271







KRGMCDSUM KRG_MIGRATION_CONTROL_DATA_SET_ERROR_\SUMMARY

153 154 236

KRGOCDEG1 KRG_OCDS_ERROR_GROUP1 160 163 200






Table 1. Capacity planning for historical data logged by Advanced Audit for DFSMShsm (continued)

Table Attribute group

Bytes perinstance(agent)

Databasebytes perinstance(warehouse)

Aggregatebytes perinstance(warehouse)

KRGOCDSUM KRG_OFFLINE_CONTROL_DATA_SET_ERROR_\SUMMARY

153 154 236

KRGPOBJST KRG_PERFORMANCE_OBJECT_STATUS 288 289 326

For more information about historical data collection, see the IBM Tivoli MonitoringAdministrator's Guide.


Chapter 5. Situations reference

This chapter contains an overview of situations, references for detailed informationabout situations, and descriptions of the predefined situations included in thismonitoring agent.

About situationsA situation is a logical expression involving one or more system conditions.Situations are used to monitor the condition of systems in your network. You canmanage situations from Tivoli Enterprise Portal by using the Situation editor.

The monitoring agents that you use to monitor your system environment aredelivered with a set of predefined situations that you can use as-is or you cancreate new situations to meet your requirements. Predefined situations containattributes that check for system conditions common to many enterprises.

Using predefined situations can improve the speed with which you can begin usingthe IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent. You can examineand, if necessary, change the conditions or values being monitored by a predefinedsituation to those best suited to your enterprise.

You can display predefined situations and create your own situations using theSituation editor. The left frame of the Situation editor initially lists the situationsassociated with the Navigator item that you selected. When you click a situationname or create a new situation, the right frame opens with the following tabs:

FormulaFormula describing condition being tested

DistributionList of managed systems (operating systems, subsystems, or applications)to which the situation can be distributed. All of the IBM Tivoli AdvancedAudit for DFSMShsm Monitoring Agent managed systems are assigned bydefault.

Expert adviceComments and instructions to be read in the event workspace

ActionCommand to be sent to the system

Util Options to close the event after a period of time, or when another situationbecomes true

More information about situationsTivoli Enterprise Portal User's Guide contains more information about predefinedand custom situations and how to use them to respond to alerts.

For a list of the predefined situations for this monitoring agent and a description ofeach situation, refer to the Predefined situations section in this chapter and theinformation in that section for each individual situation.


Predefined situationsThis monitoring agent contains the following predefined situations, which areorganized by Navigator item:

v IBM Tivoli Advanced Audit for DFSMShsm

– Not applicable

v Agent Status Summary

– Not applicable

v Backup Control Data Set Error Summary

– KRG_BCDS_Critical_Error

v HSEND List Event Information

– Not applicable

v HSM Tape Error Summary

– KRG_HSM_Tape_Critical_Errors

v LISTCAT Event Information

– Not applicable

v Migration Control Data Set Error Summary

– KRG_MCDS_Critical_Error

v Offline Control Data Set Error Summary

– KRG_OCDS_Critical_Error

The remaining sections of this chapter contain descriptions of each of thesesituations. The situations are organized by Navigator item. The following informationis provided about each situation:

DescriptionInformation about the conditions that the situation tests

FormulaSyntax that contains one or more logical expressions describing theconditions for the situation to monitor

Run at startupWhether the situation is automatically distributed to instances of the agentor is available for manual distribution.

Sampling intervalNumber of seconds that elapses between one sample of data that themonitoring agent collects for the server and the next sample

Situation persistenceWhether the conditions specified in the situation evaluate to "true" for thedefined number of occurrences in a row before the situation is raised. Thedefault of 1 means no persistence checking takes place.

SeveritySeverity of the event: Warning, Informational, or Critical

Clearing conditionsControls when a true situation closes: after a period of time, when anothersituation is true, or whichever occurs first if both are selected.

IBM Tivoli Advanced Audit for DFSMShsm Navigator itemThere are no predefined situations for this Navigator item.


Agent Status Summary Navigator itemThere are no predefined situations for this Navigator item.

Backup Control Data Set Error Summary Navigator item

KRG_BCDS_Critical_Error situation

DescriptionBCDS discrepancies found.

Formula*IF ( ( *VALUE KRG_BACKUP_CONTROL_DATA_SET_ERROR_SUMMARY.BCSERRCNT *GT 0 )*AND ((*SUBSTR(*VALUEKRG_BACKUP_CONTROL_DATA_SET_ERROR_SUMMARY.BCSERRCNT,5,1) *EQ 'C') *OR(*SUBSTR(*VALUE KRG_BACKUP_CONTROL_DATA_SET_ERROR_SUMMARY.BCSERRCNT,5,1)*EQ 'V')))

See “Attribute groups and attributes for the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent” on page 13 for descriptions of the attributes in thisformula.

Distribution typeThis situation is available for distribution.

Sampling interval1 minute

Situation persistenceThe number of times the conditions of the situation must occur for the situation tobe true is 1.

SeverityCritical

Clearing conditionsThe situation clears when the condition becomes false.

HSEND List Event Information Navigator itemThere are no predefined situations for this Navigator item.

HSM Tape Error Summary Navigator item

KRG_HSM_Tape_Critical_Errors situation

DescriptionHSM Tape Inventory discrepancies found.

Formula*IF ( ( *VALUE KRG_HSM_TAPE_ERROR_SUMMARY.TPSERRCNT *GT 0 ) *AND((*SUBSTR(*VALUE KRG_HSM_TAPE_ERROR_SUMMARY.TPSDIAGID,5,1) *EQ 'C') *OR(*SUBSTR(*VALUE KRG_HSM_TAPE_ERROR_SUMMARY.TPSDIAGID,5,1) *EQ 'V')))

Chapter 5. Situations reference 63





SeverityCritical


LISTCAT Event Information Navigator itemThere are no predefined situations for this Navigator item.

Migration Control Data Set Error Summary Navigator item

KRG_MCDS_Critical_Error situation

DescriptionMCDS discrepancies found.

Formula*IF ( ( *VALUE KRG_MIGRATION_CONTROL_DATA_SET_ERROR_SUMMARY.MCSERRCNT *GT 0) *AND ((*SUBSTR(*VALUEKRG_MIGRATION_CONTROL_DATA_SET_ERROR_SUMMARY.MCSERRCNT,5,1) *EQ 'C') *OR(*SUBSTR(*VALUE KRG_MIGRATION_CONTROL_DATA_SET_ERROR_SUMMARY.MCSERRCNT,5,1)*EQ 'V')))





SeverityCritical



Offline Control Data Set Error Summary Navigator item

KRG_OCDS_Critical_Error situation

DescriptionOCDS discrepancies found.

Formula*IF ( ( *VALUE KRG_OFFLINE_CONTROL_DATA_SET_ERROR_SUMMARY.OCSERRCNT *GT 0 )*AND ((*SUBSTR(*VALUEKRG_OFFLINE_CONTROL_DATA_SET_ERROR_SUMMARY.OCSERRCNT,5,1) *EQ 'C') *OR(*SUBSTR(*VALUE KRG_OFFLINE_CONTROL_DATA_SET_ERROR_SUMMARY.OCSERRCNT,5,1)*EQ 'V')))





SeverityCritical


Chapter 5. Situations reference 65


Chapter 6. Take Action commands reference

This chapter contains an overview of Take Action commands, references fordetailed information about Take Action commands, and descriptions of the TakeAction commands included in this monitoring agent, if any.

About Take Action commandsTake Action commands can be run from the portal client or included in a situation ora policy.

When included in a situation, the command runs when the situation becomes true.A Take Action command in a situation is also referred to as reflex automation. Whenyou enable a Take Action command in a situation, you automate a response tosystem conditions. For example, you can use a Take Action command to send acommand to restart a process on the managed system or to send a text messageto a cell phone.

Advanced automation uses policies to perform actions, schedule work, andautomate manual tasks. A policy comprises a series of automated steps calledactivities that are connected to create a workflow. After an activity is completed,Tivoli Enterprise Portal receives return code feedback, and advanced automationlogic responds with subsequent activities prescribed by the feedback.

A basic Take Action command displays the return code of the operation in amessage box that is displayed after the action completes or in a log file. After youclose this window, no further information is available for this action.

More information about Take Action commandsFor more information about working with Take Action commands, see the TivoliEnterprise Portal User's Guide.

For a list of the Take Action commands for this monitoring agent and a descriptionof each command, see the Predefined Take Action commands section in thischapter and the information in that section for each individual command.

Predefined Take Action commandsThis monitoring agent contains the following Take Action commands:

v HSEND_LIST_DSNAME

v HSEND_LIST_TTOC

v LISTCAT_ENT

The remaining sections of this chapter contain descriptions of these Take Actioncommands, which are listed alphabetically. The following information is providedabout each Take Action command:

DescriptionWhich actions the command performs on the system to which it is sent, andthe permissions required for the Take Action command to function

Return codesInformation that the Take Action command returns


HSEND_LIST_DSNAME action

DescriptionList data set information from the MCDS and BCDS

System commandTo include the Take Action command in a situation or workflow policy, use thefollowing syntax for the system command:HSEND_LIST_DSNAME \

[DSNAME]

[WAIT]

You can use attribute substitution to supply the Take Action command argumentsfrom the situation, for example:HSEND_LIST_DSNAME \

[&{DSNAME}] \

[&{WAIT}]

You can also use attribute substitution in a workflow policy though the format isslightly different:HSEND_LIST_DSNAME \

[&WaitOnSituation:DSNAME] \

[&WaitOnSituation:WAIT]

Argumentsv Name: DSNAME

Description: Required - request a listing of the data set entry for theparticular data set.Default:

v Name: WAITDescription: Optional - Wait interval in seconds.Default: 0

Return codesv Return Code: 0000

Return Code Type: OKOperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0000Message: Take Action was successfully issued.

v Return Code: 0004Return Code Type: INSUFFICIENT_USER_AUTHORITYOperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0004Message: User ID Translation failed.

v Return Code: 0008Return Code Type: GENERAL_ERROROperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0008


Message: Bad Parameter List.

v Return Code: 0012Return Code Type: NOT_RUNNINGOperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0012Message: Bad KRS Environment.

HSEND_LIST_TTOC action

DescriptionList information for DFSMShsm primary and backup volume information from theBCDS.

System commandTo include the Take Action command in a situation or workflow policy, use thefollowing syntax for the system command:HSEND_LIST_TTOC \

[VOLSER]

[WAIT]

You can use attribute substitution to supply the Take Action command argumentsfrom the situation, for example:HSEND_LIST_TTOC \

[&{VOLSER}] \

[&{WAIT}]

You can also use attribute substitution in a workflow policy though the format isslightly different:HSEND_LIST_TTOC \

[&WaitOnSituation:VOLSER] \

[&WaitOnSituation:WAIT]

Argumentsv Name: VOLSER

Description: Required - request a listing of the volume for the particularvolume.Default:

v Name: WAITDescription: Required - Wait interval in seconds.Default:



v Return Code: 0004

Chapter 6. Take Action commands reference 69

Return Code Type: INSUFFICIENT_USER_AUTHORITYOperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0004Message: User ID Translation failed.

v Return Code: 0008Return Code Type: GENERAL_ERROROperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0008Message: Bad Parameter List.


LISTCAT_ENT action

DescriptionRecover a data set from a backup version or restore a data set froma dump copy.

System commandTo include the Take Action command in a situation or workflow policy, use thefollowing syntax for the system command:LISTCAT_ENT \

[DSNAME]

You can use attribute substitution to supply the Take Action command argumentsfrom the situation, for example:LISTCAT_ENT \

[&{DSNAME}]

You can also use attribute substitution in a workflow policy though the format isslightly different:LISTCAT_ENT \

[&WaitOnSituation:DSNAME]

Argumentsv Name: DSNAME

Description: Required - Name of the data set to process.Default:



v Return Code: 0004Return Code Type: INSUFFICIENT_USER_AUTHORITYOperating systems: Linux 2.4 (Intel), Windows


Message ID: KRG0004Message: User ID Translation failed.

v Return Code: 0008Return Code Type: GENERAL_ERROROperating systems: Linux 2.4 (Intel), WindowsMessage ID: KRG0008Message: Bad Parameter List.


Chapter 6. Take Action commands reference 71


Chapter 7. Policies reference

This chapter contains an overview of policies, references for detailed informationabout policies, and descriptions of the predefined policies included in this monitoringagent, if any.

About policiesPolicies are an advanced automation technique for implementing more complexworkflow strategies than you can create through simple automation.

A policy is a set of automated system processes that can perform actions, schedulework for users, or automate manual tasks. You use the Workflow Editor to designpolicies. You control the order in which the policy executes a series of automatedsteps, which are also called activities. Policies are connected to create a workflow.After an activity is completed, Tivoli Enterprise Portal receives return code feedbackand advanced automation logic responds with subsequent activities prescribed bythe feedback.

More information about policiesThis monitoring agent does not provide predefined policies. For more informationabout working with policies, see the Tivoli Enterprise Portal User's Guide.

For information about using the Workflow Editor, see the IBM Tivoli MonitoringAdministrator's Guide or the Tivoli Enterprise Portal online help.

Predefined policiesThe IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent does not providepredefined policies.



Chapter 8. Troubleshooting

This chapter provides agent-specific troubleshooting information. See the IBM TivoliMonitoring Troubleshooting Guide for general troubleshooting information. Also see“Support information” on page 90 for other problem-solving options.

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in Chapter 2, “Requirements for the monitoringagent,” on page 5.

Gathering product information for IBM Software SupportBefore contacting IBM Software Support about a problem you are experiencing withthis product, gather the information in Table 2 that relates to the problem.

Table 2. Information to gather before contacting IBM Software Support

Information type Description

Log files Collect trace log files from failing systems. Most logs are located in a logs subdirectory onthe host computer. See “Trace logging” on page 76 for lists of all trace log files and theirlocations. See the Tivoli Enterprise Portal User's Guide for general information about theIBM Tivoli Monitoring environment.

IBM Tivoli AdvancedAudit for DFSMShsminformation

v Version number and patch level

Operating system Operating system version number and patch level

Messages Messages and other information displayed on the screen

Version numbers for IBMTivoli Monitoring

Version number of the following members of the monitoring environment:v IBM Tivoli Monitoring. Also provide the patch level, if available.v IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent

Screen captures Screen captures of incorrect output, if any.

(UNIX only) Core dumpfiles

If the system stops on UNIX systems, collect the core dump file from install_dir/bindirectory, where install_dir is the directory where you installed the monitoring agent.

See http://www.ibm.com/software/support/probsub.html for information aboutworking with IBM Software Support.

Built-in troubleshooting featuresThe primary troubleshooting feature in the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent is logging. Logging refers to the text messages andtrace data generated by the IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent. Messages and trace data are sent to a file.

Trace data captures transient information about the current operating environmentwhen a component or application fails to operate as designed. See “Trace logging”on page 76 for more information.

Problem classificationThe following types of problems might occur with the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent:

v Installation and configuration

v General usage and operation


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

v Display of monitoring data

v Take Action commands

This chapter provides symptom descriptions and detailed workarounds for theseproblems, as well as describing the logging capabilities of the monitoring agent. Seethe IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Trace loggingTrace logs capture information about the operating environment when componentsoftware fails to operate as intended. The principal log type is the RAS (Reliability,Availability, and Serviceability) trace log. These logs are in the English languageonly. The RAS trace log mechanism is available for all components of IBM TivoliMonitoring. Most logs are located in a logs subdirectory on the host computer. Seethe following sections to learn how to configure and use trace logging:

v “Principal trace log files”

v “Examples: using trace logs” on page 78

v “Setting RAS trace parameters” on page 79

Note: The documentation refers to the RAS facility in IBM Tivoli Monitoring as"RAS1".

All components in the IBM Tivoli Monitoring environment have a default tracinglevel. The tracing level can be changed on a per-component level to adjust the typeof trace information collected, the degree of trace detail, the number of trace logs tobe kept, and the amount of disk space used for tracing.

Overview of log file managementTable 3 on page 77 provides the names, locations, and descriptions of RAS1 logfiles. The log file names adhere to the following naming convention:

Windows systemshostname_productcode_program_HEXtimestamp-nn.log

Linux and UNIX systemshostname_productcode_HEXtimestamp-nn.log

where:

v hostname is the host name of the computer where the monitoring component isrunning.

v productcode is the two-character product code. For IBM Tivoli Advanced Audit forDFSMShsm, the product code is rg.

v program is the name of the program being run.

v HEXtimestamp is a hexadecimal time stamp representing the time at which theprogram started.

v nn is a rolling log suffix.

Principal trace log files

Table 3 on page 77 contains locations, file names, and descriptions of trace logsthat can help determine the source of problems with agents.


Table 3. Trace log files for troubleshooting agents

System where logis located

File name and path Description

On the TivoliEnterpriseMonitoring Server

v Windows: The file in theinstall_dir\InstallITM path

v UNIX: The candle_installation.log file inthe install_dir/logs path

Provides details about products that are installed.Note: Trace logging is enabled by default. Aconfiguration step is not required to enable thistracing.

The Warehouse_Configuration.log file is inthe following location on Windows systems:install_dir\InstallITM

Provides details about the configuration of datawarehousing for historical reporting.

The name of the RAS log file is as follows:

v Windows: install_dir\logs\hostname_ms_timestamp-nn.log

v UNIX: install_dir/logs/hostname_productcode_timestamp.log

Note: File names for RAS1 logs include ahexadecimal time stamp.

Also on UNIX, a log with a decimal timestamp is provided:hostname_productcode_timestamp.log andhostname_productcode_timestamp.pidnnnnn in the install_dir/logspath, where nnnnn is the process ID number.

Traces activity on the monitoring server.

On the TivoliEnterprise PortalServer

The name of the RAS log file is as follows:

v Windows: install_dir\logs\hostname_cq_HEXtimestamp-nn.log

v UNIX®: install_dir/logs/hostname_cq_HEXtimestamp-nn.log

Note: File names for RAS1 logs include ahexadecimal time stamp.

Also on UNIX, a log with a decimal timestamp is provided:hostname_productcode_timestamp.log andhostname_productcode_timestamp.pidnnnnn in the install_dir/logspath, where nnnnn is the process ID number.

Traces activity on the portal server.

The teps_odbc.log file is located in thefollowing path

v Windows: install_dir\InstallITM path.

v UNIX: install_dir/logs

When you enable historical reporting, this log filetraces the status of the warehouse proxy agent.

Chapter 8. Troubleshooting 77

Table 3. Trace log files for troubleshooting agents (continued)

System where logis located

File name and path Description

On the computerthat hosts themonitoring agent

The RAS1 log files are as follows:

v Windows: hostname_rg_krgagent_HEXtimestamp-nn.log in theinstall_dir\tmaitm6\logs directory

v UNIX: hostname_rg_HEXtimestamp-nn.log in the install_dir/logs directory

These logs are in the following directories:

v Windows: install_dir\tmaitm6\logs


Traces activity of the monitoring agent.

The agent operations log files are as follows:

instance_hostname_RG.LG0 is the current logcreated when the agent was started

instance_hostname_RG.LG1 is the backup ofthe previous log

These logs are in the following directorydepending on the operating system that youare using:



Shows whether the agent was able to connect tothe monitoring server. Shows which situations arestarted and stopped, and shows other eventswhile the agent is running. A new version of thisfile is generated every time the agent isrestarted.

IBM Tivoli Monitoring generates one backup copyof the *.LG0 file with the tag .LG1. View .LG1 tolearn the following details regarding the previousmonitoring session:v Status of connectivity with the monitoring

server.v Situations that were running.v The success or failure status of Take Action

commands.

The Take Action command log files are asfollows:

v host_rg_takeactioncommand.log

The logs are in the following directories:



Traces activity each time a Take Action commandruns. For example, when a hypotheticalstart_command Take Action command runs,IBM Tivoli Monitoring generates astart_command.log file.

Definitions of variables:

timestamp is time stamp whose format includes year (y), month (m), day (d), hour (h), and minute (m), as follows:yyyymmdd hhmm

HEXtimestamp is a hexadecimal representation of the time at which the process was started.

install_dir represents the directory path where you installed the IBM Tivoli Monitoring component. install_dir canrepresent a path on the computer that host the monitoring system, the monitoring agent, or the portal.

instance refers to the name of the database instance that you are monitoring.

hostname refers to the name of the computer on which the IBM Tivoli Monitoring component runs.

nn represents the circular sequence in which logs are rotated. Ranges from 1-5, by default, though the first isalways retained, because it includes configuration parameters.

productcode specifies the product codes, for example, um for Universal Agent or nt for Windows.

See the IBM Tivoli Monitoring Installation and Setup Guide for more information onthe complete set of trace logs that are maintained on the monitoring server.

Examples: using trace logsYou can open trace logs in a text editor to learn some basic facts about your IBMTivoli Monitoring environment. The following examples are from the Tivoli EnterpriseMonitoring Server log.


Example oneThis excerpt shows the typical log for a failed connection between amonitoring agent and a monitoring server with the host name server1a:

(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup") status=1c020006,"location server unavailable", ncs/KDC1_STC_SERVER_UNAVAILABLE(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1157,"LookupProxy") Unable to connect tobroker at ip.pipe:: status=0, "success", ncs/KDC1_STC_OK(Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unableto find running CMS on CT_CMSLIST <IP.PIPE:#server1a>

Example twoThe following excerpts from the trace log for the monitoring server show thestatus of an agent, identified here as "Remote node." The name of thecomputer where the agent is running is SERVER5B:

(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter") Remote node SERVER5B:RG is ON-LINE.. . .(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter") Remote node SERVER5B:RG is OFF-LINE.

Key points regarding the preceding excerpt:

v The monitoring server appends the RG product code to the server nameto form a unique name (SERVER5B:RG) for this instance of the IBM TivoliAdvanced Audit for DFSMShsm Monitoring Agent. This unique nameenables you to distinguish multiple monitoring products that might berunning on SERVER5B.

v The log shows when the agent started (ON-LINE) and later stopped(OFF-LINE) in the environment.

v For the sake of brevity an ellipsis (...) represents the series of trace logentries that were generated while the agent was running.

v Between the ON-LINE and OFF-LINE log entries, the agent wascommunicating with the monitoring server.

v The ON-LINE and OFF-LINE log entries are always available in the tracelog. All trace levels that are described in “Setting RAS trace parameters”provide these entries.

On Windows, you can use the following alternate method to view trace logs:

1. In the Windows Start menu, choose Program Files > IBM Tivoli Monitoring >Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli EnterpriseMonitoring Services window is displayed.

2. Right-click a component and select Advanced > View Trace Log in the pop-upmenu. For example, if you want to view the trace log of the IBM Tivoli AdvancedAudit for DFSMShsm agent, right-click the name of the that agent in thewindow. You can also use the viewer to access remote logs.

Note: The viewer converts time stamps in the logs to a format that is easier toread.

Setting RAS trace parameters

ObjectivePinpoint a problem by setting detailed tracing of individual components of themonitoring agent and modules.


Background InformationThe IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent uses RAS1 tracingand generates the logs described in Table 3 on page 77. The default RAS1 tracelevel is ERROR.

Before you beginSee “Overview of log file management” on page 76 to ensure that you understandlog rolling and can reference the correct log files when you manage log filegeneration.

After you finishMonitor the size of the logs directory. Default behavior can generate a total of 45 to60 MB for each agent that is running on a computer. For example, each databaseinstance that you monitor can generate 45 to 60 MB of log data. See the"Procedure" section to learn how to adjust file size and numbers of log files toprevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlikethe RAS1 log files that are pruned automatically, other log types can growindefinitely, for example, the logs in Table 3 on page 77 that include a process IDnumber (PID).

Consider using collector trace logs as an additional source of troubleshootinginformation.

Note: The KDC_DEBUG setting and the Maximum error tracing setting cangenerate a large amount of trace logging. Use them only temporarily, whileyou are troubleshooting problems. Otherwise, the logs can occupy excessiveamounts of hard disk space.

ProcedureOn Windows systems, you can use the graphical user interface to set trace options:

1. Open the Manage Tivoli Enterprise Monitoring Services window.

2. Right-click the icon of the monitoring agent whose logging you want to modify.

3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring ServerTrace Parameters window is displayed.

4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filtersfield or type a valid string.

The selections are as follows:

v General error tracing. KBB_RAS1=ERROR

v Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)

v Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

Notes: As this example shows, you can set multiple RAS tracing options in asingle statement.

5. Modify the value for 'Maximum Log Size Per File (MB)" to change the log filesize (changes LIMIT value).

6. Modify the value for 'Maximum Number of Log Files Per Session" to change thenumber of log files per startup of a program (changes COUNT value).

7. Modify the value for 'Maximum Number of Log Files Total" to change thenumber of log files for all startups of a program (changes MAXFILES value).


8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log informationthat can help you diagnose communications and connectivity problems betweenthe monitoring agent and the monitoring server.

Note: The KDC_DEBUG setting and the Maximum error tracing setting cangenerate a large amount of trace logging. Use them only temporarily,while you are troubleshooting problems. Otherwise, the logs can occupyexcessive amounts of hard disk space.

9. Click OK. You see a message reporting a restart of the monitoring agent so thatyour changes take effect.

You can also manually edit the RAS1 trace logging parameters using this method:

1. Open the trace options file:

Windows: install_dir\tmaitm6\KRGENV

UNIX: install_dir/config/rg.ini

2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. Forexample, if you want detailed trace logging, set the Maximum Tracingoption:KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)

3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation oflog files:

v MAXFILES: the total number of files that are to be kept for all startups of agiven program. When this value is exceeded, the oldest log files arediscarded. Default value is 9.

v LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Defaultvalue is 5.

Notes: The KBB_RAS1_LOG parameter also provides for the specification ofthe log file directory, log file name, and the inventory control filedirectory and name. Do not modify these values or log information canbe lost.

4. Restart the monitoring agent so that your changes take effect.

Problems and workaroundsThe following sections provide symptoms and workarounds for problems that mightoccur with the IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent:

v “Installation and configuration troubleshooting” on page 81

v “Remote deployment troubleshooting” on page 83

v “Agent troubleshooting” on page 84

v “Workspace troubleshooting” on page 85

v “Situation troubleshooting” on page 87

Note: You can resolve some problems by ensuring that your system matches thesystem requirements listed in Chapter 2, “Requirements for the monitoringagent,” on page 5.

This chapter provides agent-specific troubleshooting information. See the IBM TivoliMonitoring Troubleshooting Guide for general troubleshooting information.

Installation and configuration troubleshootingThis section provides tables that show solutions for installation, configuration, anduninstallation problems.


Table 4. Problems and solutions for installation and configuration

Problem Solution

(UNIX only) During a command-line installation, youchoose to install a component that is already installed,and you see the following warning:

WARNING - you are about to installthe SAME version of "component_name"

where component_name is the name of the componentthat you are attempting to install.Note: This problem affects UNIX command-lineinstallations. If you monitor only Windows environments,you see this problem if you choose to install a productcomponent (for example, a monitoring server) on UNIX.

You must exit and restart the installation process. Youcannot return to the list where you selected components toinstall. When you run the installer again, do not attempt toinstall any component that is already installed.

A problem can arise when you install and configure anew monitoring agent to a computer where other agentsare running as described in this example:

v Agents are running on computer and communicatingwith a Tivoli Enterprise Monitoring Server, calledTEMS1.

v You install a new agent on the same computer andyou want this agent to communicate with a differentmonitoring server, called TEMS2.

v When you configure the new agent to communicatewith TEMS2, all the existing agents are re-configuredto communicate with TEMS2.

You must reconfigure the previously existing agents torestore their communication connection with TEMS1. Forexample, you can right-click the row for a specific agent inthe Manage Tivoli Enterprise Monitoring Services, andselect Reconfigure. See the IBM Tivoli MonitoringInstallation and Setup Guide for more information onreconfiguration.

Diagnosing problems with product browse settings(Windows systems only).

When you have problems with browse settings, performthe following steps:

1. Click Start > Programs > IBM Tivoli Monitoring >Manage Tivoli Enterprise Monitoring Services. TheManage Tivoli Enterprise Monitoring Services windowis displayed.

2. Right-click the Windows agent and select BrowseSettings. A text window is displayed.

3. Click Save As and save the information in the text file.

A message similar to "Unable to find running CMS onCT_CMSLIST" in the log file is displayed.

If a message similar to "Unable to find running CMS onCT_CMSLIST" is displayed in the Log file, the agent is notable to connect to the monitoring server. Confirm thefollowing points:

v Do multiple network interface cards (NICs) exist on thesystem?

v If multiple NICs exist on the system, find out which oneis configured for the monitoring server. Ensure that youspecify the correct host name and port settings forcommunication in the IBM Tivoli Monitoringenvironment.


Table 4. Problems and solutions for installation and configuration (continued)

Problem Solution

The system is experiencing high CPU usage. Agent process: View the memory usage of the KRGCMAprocess. If CPU usage seems to be excessive, recycle themonitoring agent.

Network Cards: The network card configurations candecrease the performance of a system. Each of thestream of packets that a network card receives (assumingit is a broadcast or destined for the under-performingsystem) must generate a CPU interrupt and transfer thedata through the I/O bus. If the network card in question isa bus-mastering card, work can be off-loaded and a datatransfer between memory and the network card cancontinue without using CPU processing power.Bus-mastering cards are generally 32-bit and are basedon PCI or EISA bus architectures.

Table 5. General problems and solutions for uninstallation

Problem Solution

On Windows, uninstallation of IBMTivoli Monitoring fails to uninstallthe entire environment.

Be sure that you follow the general uninstallation process described in the IBMTivoli Monitoring Installation and Setup Guide:

1. Remove Tivoli Enterprise Monitoring Server Application support by completingthe following steps:

a. Use Manage Tivoli Enterprise Monitoring Services.

b. Select Tivoli Enterprise Monitoring Server.

c. Right-click and select Advanced.

d. Select Remove TEMS application support.

e. Select the agent to remove its application support.

2. Uninstall monitoring agents first, as in the following examples:

v Uninstall a single monitoring agent for a specific database.

-OR-

v Uninstall all instances of a monitoring product, such as IBM TivoliMonitoring for Databases.

3. Uninstall IBM Tivoli Monitoring.

The way to remove inactivemanaged systems (systemswhose status is OFFLINE) fromthe Navigator tree in the portal isnot obvious.

Use the following steps to remove, but not uninstall, an offline managed systemfrom the Navigator tree:

1. Click the Enterprise icon in the Navigator tree.

2. Right-click, then click Workspace > Managed System Status.

3. Right-click the offline managed system, and select Clear offline entry.

If you also want to uninstall the monitoring agent, use the procedure described inthe IBM Tivoli Monitoring Installation and Setup Guide.

Remote deployment troubleshootingTable 6 on page 84 lists problems that might occur with remote deployment. Thissection provides information about troubleshooting remote deployment of themonitoring agent. See the IBM Tivoli Monitoring Troubleshooting Guide for generaltroubleshooting information.

This section describes problems and solutions for remote deployment and removalof agent software using Agent Remote Deploy.


Table 6. Remote deployment problems and solutions

Problem Solution

While you are using the remote deployment featureto install the IBM Tivoli Advanced Audit forDFSMShsm Monitoring Agent, an empty commandwindow is displayed on the target computer. Thisproblem occurs when the target of remotedeployment is a Windows computer. (See the IBMTivoli Monitoring Installation and Setup Guide formore information on the remote deployment feature.)

Do not close or modify this window. It is part of the installationprocess and is dismissed automatically.

The removal of a monitoring agent fails when youuse the remote removal process in the TivoliEnterprise Portal desktop or browser.

This problem might occur when you attempt the remoteremoval process immediately after you have restarted theTivoli Enterprise Monitoring Server. You must allow time forthe monitoring agent to refresh its connection with the TivoliEnterprise Monitoring Server before you begin the remoteremoval process.

Agent troubleshootingThis section lists problems that might occur with agents.

This chapter provides agent-specific troubleshooting information. See the IBM TivoliMonitoring Troubleshooting Guide for general troubleshooting information.

Table 7. Agent problems and solutions

Problem Solution

Log data accumulates too rapidly. Check the RAS trace option settings, which are described in “Setting RAS traceparameters” on page 79. The trace options settings that you can set on theKBB_RAS1= and KDC_DEBUG= lines potentially generate large amounts of data.

When using the F1 key orselecting Help --> Contents andIndex, you receive a message inyour Microsoft Internet Explorerbrowser which states, "It seemsjavascript is disabled in yourbrowser, please enable it andreload again, or click here toview without javascript." If youselect 'here', the Tivoli EnterprisePortal V6.1 Help is displayed, butthe agent help is not.

Ensure that the local site is added to the trusted site for the browser, and thenenable the javascript.

If you want to receive multipletrace logs for separateinvocations of the same TakeAction command, leaving thissetting on permanently fills theavailable disk space.

Do not leave this setting on permanently. By doing so, you create a new log filefor each invocation of the Take Action command and ALL of them are left on theagent system.


Table 7. Agent problems and solutions (continued)

Problem Solution

A configured and runninginstance of the monitoring agentis not displayed in the TivoliEnterprise Portal, but otherinstances of the monitoring agenton the same system do appear inthe portal.

Tivoli Monitoring products use Remote Procedure Call (RPC) to define and controlproduct behavior. RPC is the mechanism that allows a client process to make asubroutine call (such as GetTimeOfDay or ShutdownServer) to a server processsomewhere in the network. Tivoli processes can be configured to use TCP/UDP,TCP/IP, SNA, and SSL as the desired protocol (or delivery mechanism) for RPCs.

"IP.PIPE" is the name given to Tivoli TCP/IP protocol for RPCs. The RPCs aresocket-based operations that use TCP/IP ports to form socket addresses. IP.PIPEimplements virtual sockets and multiplexes all virtual socket traffic across a singlephysical TCP/IP port (visible from the netstat command).

A Tivoli process derives the physical port for IP.PIPE communications based onthe configured, well-known port for the HUB Tivoli Enterprise Monitoring Server.(This well-known port or BASE_PORT is configured using the 'PORT:' keyword onthe KDC_FAMILIES / KDE_TRANSPORT environment variable and defaults to'1918'.)

The physical port allocation method is defined as (BASE_PORT + 4096*N) whereN=0 for a Tivoli Enterprise Monitoring Server process and N={1, 2, ..., 15} for anon-Tivoli Enterprise Monitoring Server. Two architectural limits result as aconsequence of the physical port allocation method:

v No more than one Tivoli Enterprise Monitoring Server reporting to a specificTivoli Enterprise Monitoring Server HUB can be active on a system image.

v No more than 15 IP.PIPE processes can be active on a single system image.

A single system image can support any number of Tivoli Enterprise MonitoringServer processes (address spaces) provided that each Tivoli EnterpriseMonitoring Server on that image reports to a different HUB. By definition, there isone Tivoli Enterprise Monitoring Server HUB per monitoring Enterprise, so thisarchitecture limit has been simplified to one Tivoli Enterprise Monitoring Serverper system image.

No more that 15 IP.PIPE processes or address spaces can be active on a singlesystem image. With the first limit expressed above, this second limitation refersspecifically to Tivoli Enterprise Monitoring Agent processes: no more that 15agents per system image.

This limitation can be circumvented (at current maintenance levels, IBM® TivoliMonitoring V6.1 Fix Pack 4 and later) if the Tivoli Enterprise Monitoring Agentprocess is configured to use EPHEMERAL IP.PIPE. (This is IP.PIPE configuredwith the 'EPHEMERAL:Y' keyword in the KDC_FAMILIES / KDE_TRANSPORTenvironment variable). There is no limitation to the number of ephemeral IP.PIPEconnections per system image. If ephemeral endpoints are used, the WarehouseProxy Agent is accessible from the Tivoli Enterprise Monitoring Server associatedwith the agents using ephemeral connections either by running the WarehouseProxy Agent on the same computer or by using the Firewall Gateway feature.(The Firewall Gateway feature relays the Warehouse Proxy Agent connectionfrom the Tivoli Enterprise Monitoring Server computer to the Warehouse ProxyAgent computer if the Warehouse Proxy Agent cannot coexist on the samecomputer.)

Workspace troubleshootingTable 8 on page 86 shows problems that might occur with workspaces. This chapterprovides agent-specific troubleshooting information. See the IBM Tivoli MonitoringTroubleshooting Guide for general troubleshooting information.


Table 8. Workspace problems and solutions

Problem Solution

The process application components areavailable, but the Availability status showsPROCESS_DATA_NOT_ AVAILABLE.

This problem occurs because the PerfProc performance object isdisabled. When this condition exists, IBM Tivoli Monitoring cannotcollect performance data for this process. Do the following toconfirm that this problem exists and resolve it:

1. Choose Run in the Windows Start menu.

2. Type perfmon.exe in the Open field of the Run window. ThePerformance window is displayed.

3. Click the plus sign (+) in the tool bar located above the rightpane. The Add Counters window is displayed.

4. Look for Process in the Performance object pull-downmenu.

5. Perform one of the following actions:

v If you see Process in the pull-down menu, the PerfProcperformance object is enabled and the problem is comingfrom a different source.

v If you do not see Process in the pull-down menu, use theMicrosoft utility from the following Web site to enable thePerfProc performance object:

http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/exctrlst-o.asp

The Process performance object becomes visible in thePerformance object pull-down menu of the Add Counterswindows, and IBM Tivoli Monitoring is able to detectAvailability data.

6. Restart the monitoring agent.

The name of the attribute does not display in abar chart or graph view.

When a chart or graph view that includes the attribute is scaledto a small size, a blank space is displayed instead of a truncatedname. To see the name of the attribute, expand the view of thechart until there is sufficient space to display all characters of theattribute name.

You start collection of historical data but the datacannot be seen.

Managing options for historical data collection:

v Basic historical data collection populates the Warehouse withraw data. This type of data collection is turned off by default.See the IBM Tivoli Monitoring Administrator's Guide forinformation on managing this feature including how to set theinterval at which data is collected. By setting a more frequentinterval for data collection you reduce the load on the systemincurred every time data is uploaded.

v You use the Summarization and Pruning monitoring agent tocollect specific amounts and types of historical data. Be awarethat historical data is not displayed until the Summarizationand Pruning monitoring agent begins collecting the data. Bydefault, this agent begins collection at 2 AM daily. At that point,data is visible in the workspace view. See the IBM TivoliMonitoring Administrator's Guide to learn how to modify thedefault collection settings.


Table 8. Workspace problems and solutions (continued)

Problem Solution

Historical data collection is unavailable becauseof incorrect queries in the Tivoli Enterprise Portal.

The column, Sort By, Group By, and First/Last functions are notcompatible with the historical data collection feature. Use of theseadvanced functions makes a query ineligible for historical datacollection.

Even if data collection has been started, you cannot use the timespan feature if the query for the chart or table includes columnfunctions or advanced query options (Sort By, Group By, First /Last).

To ensure support of historical data collection, do not use theSort By, Group By, or First/Last functions in your queries.

See the IBM Tivoli Monitoring Administrator's Guide or the TivoliEnterprise Portal online help for information about the HistoricalData Collection function.

When you use a long process name in thesituation, the process name is truncated.

Truncation of process or service names for situations in theAvailability table in the portal display is the expected behavior.100 bytes is the maximum name length.

Regular (non-historical) monitoring data fails to bedisplayed.

Check the formation of the queries you use to gather data. Forexample, look for invalid SQL statements.

Navigator items and workspace titles are labeledwith internal names such as Kr6:KR60000 orKnt:KNT0000 rather than the correct names (suchas Disk).

Ensure application support has been added on the monitoringserver, portal server, and portal client.

For more information and instruction on installing applicationsupport see "Installing and enabling application support" in theIBM Tivoli Monitoring Installation and Setup Guide.

Situation troubleshootingThis section provides information about both general situation problems andproblems with the configuration of situations. See the IBM Tivoli MonitoringTroubleshooting Guide for more information about troubleshooting for situations.

General situation problemsTable 9 lists general problems that might occur with situations.

Table 9. General situation problems and solutions

Problem Solution

Monitoring activity requires too muchdisk space.

Check the RAS trace logging settings that are described in “Setting RAStrace parameters” on page 79. For example, trace logs grow rapidly whenyou apply the ALL logging option.

Monitoring activity requires too manysystem resources.

“Disk capacity planning for historical data” on page 58 describes theperformance impact of specific attribute groups. If possible, decrease youruse of the attribute groups that require greater system resources.

A formula that uses mathematicaloperators appears to be incorrect. Forexample, if you were monitoring Linux, aformula that calculates when FreeMemory falls under 10 percent of TotalMemory does not work: LT#'Linux_VM_Stats.Total_Memory' / 10

This formula is incorrect because situation predicates support only logicaloperators. Your formulas cannot have mathematical operators.Note: The Situation Editor provides alternatives to math operators.Regarding the example, you can select % Memory Free attribute andavoid the need for math operators.


Table 9. General situation problems and solutions (continued)

Problem Solution

You want to change the appearance ofsituations when they are displayed in theNavigation tree.

1. Right-click an item in the Navigation tree.

2. Select Situations in the pop-up menu. The Situation Editor window isdisplayed.

3. Select the situation that you want to modify.

4. Use the State pull-down menu in the lower right of the window to setthe status and appearance of the Situation when it triggers.Note: The State setting is not related to severity settings in IBM TivoliEnterprise Console.

When a situation is triggered in theEvent Log attribute group, it remains inthe Situation Event Console as long asthe event ID entry is present in theEvent Log workspace. When this eventID entry is removed from the Event Logworkspace on the Tivoli EnterprisePortal, the situation is also cleared evenif the actual problem that caused theevent is not resolved, and the event IDentry is also present in the WindowsEvent Viewer.

There is a timeout on the cache of events for the NT Event Log group.Increase the cache time of Event Log collection to meet your requirementsby adding the following variable and timeout value to the KXXENV file forthe agent: CDP_NT_EVENT_LOG_CACHE_TIMEOUT=3600

This variable determines how long events from the NT Event Log are kept.

Problems with configuration of situationsTable 10 lists problems that might occur with configuring situations.

This section provides information for troubleshooting for agents. Be sure to consultthe IBM Tivoli Monitoring Troubleshooting Guide for more general troubleshootinginformation.

Table 10. Problems with configuring situations that you solve in the Situation Editor

Problem Solution

Note: To get started with the solutions in this section, perform these steps:1. Launch the Tivoli Enterprise Portal.2. Click Edit > Situation Editor.3. In the tree view, choose the agent whose situation you want to modify.4. Choose the situation in the list. The Situation Editor view is displayed.

The situation for a specific agent isnot visible in the Tivoli EnterprisePortal.

Open the Situation Editor. Access the All managed servers view. If the situationis absent, confirm that the monitoring server has been seeded for the agent. Ifnot, seed the server, as described in the IBM Tivoli Monitoring Installation andSetup Guide.

The monitoring interval is too long. Access the Situation Editor view for the situation that you want to modify. Checkthe Sampling interval area in the Formula tab. Adjust the time interval asneeded.

The situation did not activate atstartup.

Manually recycle the situation as follows:

1. Right-click the situation and choose Stop Situation.

2. Right-click the situation and choose Start Situation.

Note: You can permanently avoid this problem by placing a check mark in theRun at Startup option of the Situation Editor view for a specific situation.

The situation is not displayed. Click the Action tab and check whether the situation has an automatedcorrective action. This action can occur directly or through a policy. Thesituation might be resolving so quickly that you do not see the event or theupdate in the graphical user interface.


Table 10. Problems with configuring situations that you solve in the Situation Editor (continued)

Problem Solution

An Alert event has not occurredeven though the predicate hasbeen properly specified.

Check the logs, reports, and workspaces.

A situation fires on an unexpectedmanaged object.

Confirm that you have distributed and started the situation on the correctmanaged system.

The product did not distribute thesituation to a managed system.

Click the Distribution tab and check the distribution settings for the situation.

The situation does not fire. This problem can be caused when incorrect predicates are present in theformula that defines the situation. For example, the managed object shows astate that normally triggers a monitoring event, but the situation is not truebecause the wrong attribute is specified in the formula.

In the Formula tab, analyze predicates as follows:

1. Click the fx icon in the upper-right corner of the Formula area. The Showformula window is displayed.

a. Confirm the following details in the Formula area at the top of thewindow:v The attributes that you intend to monitor are specified in the formula.v The situations that you intend to monitor are specified in the formula.v The logical operators in the formula match your monitoring goal.v The numerical values in the formula match your monitoring goal.

b. (Optional) Click the Show detailed formula check box in the lower leftof the window to see the original names of attributes in the applicationor operating system that you are monitoring.

c. Click OK to dismiss the Show formula window.

2. (Optional) In the Formula area of the Formula tab, temporarily assignnumerical values that immediately trigger a monitoring event. The triggeringof the event confirms that other predicates in the formula are valid.Note: After you complete this test, you must restore the numerical values tovalid levels so that you do not generate excessive monitoring data based onyour temporary settings.

See the IBM Tivoli Monitoring Troubleshooting Guide for additional informationabout situations that do not fire.

Table 11. Problems with configuration of situations that you solve in the Workspace area

Problem Solution

Situation events are not displayedin the Events Console view of theworkspace.

Associate the situation with a workspace.Note: The situation does not need to be displayed in the workspace. It issufficient that the situation be associated with any workspace.

You do not have access to asituation.

Note: You must have administrator privileges to perform these steps.

1. Select Edit > Administer Users to access the Administer Users window.

2. In the Users area, select the user whose privileges you want to modify.

3. In the Permissions tab, Applications tab, and Navigator Views tab, selectthe permissions or privileges that correspond to the user role.

4. Click OK.


Table 11. Problems with configuration of situations that you solve in the Workspace area (continued)

Problem Solution

A managed system seems to beoffline.

1. Select Physical View and highlight the Enterprise Level of the navigatortree.

2. Select View > Workspace > Managed System Status to see a list ofmanaged systems and their status.

3. If a system is offline, check network connectivity and the status of thespecific system or application.

Take Action commands troubleshootingTable 12 lists general problems that might occur with Take Action commands. Wheneach Take Action command runs it generates the log file listed in Table 3 on page77. This chapter provides agent-specific troubleshooting information.

See the IBM Tivoli Monitoring Troubleshooting Guide for general troubleshootinginformation.

Table 12. Take Action commands problems and solutions

Problem Solution

Take Action commands often require severalminutes to complete.

Allow several minutes. If you do not see a pop-up messageadvising you of completion, try to run the command manually.

Situations fail to trigger Take Action commands. Attempt to manually run the Take Action command in the TivoliEnterprise Portal. If the Take Action command works, look forconfiguration problems in the situation. See “Situationtroubleshooting” on page 87. If the Take Action command fails,see IBM Tivoli Monitoring Troubleshooting Guide for generalinformation on troubleshooting Take Action commands.

Tivoli Common Reporting troubleshootingTable 13 contains a list of problems that might occur with the Tivoli CommonReporting predefined reports for IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent.

For information about troubleshooting for the Tivoli Common Reporting tool, seehttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html.

Table 13. Tivoli Common Reporting for IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent problems andsolutions

Problem Solution

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html and follow the instructions.


http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_welcome.html



IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceabilityworkbench that helps you resolve questions and problems with IBMsoftware products. The ISA provides quick access to support-relatedinformation and serviceability tools for problem determination. To install theISA software, go to http://www.ibm.com/software/support/isa.

Informational, warning, and error messagesThis chapter introduces message logging and explains how to gather informationfrom those logs.

Message logging refers to the text and numeric messages created by the software.These messages relay information about how the system or application isperforming and can alert you to exceptional conditions when they occur. Messagesare sent to an output destination, such as a file, database, or console screen.

If you receive a warning or error message, you can do one of the following:

v Follow the instructions listed in the Detail window of the message if thisinformation is included there.

v Consult the message details listed in this chapter to see what action you cantake to correct the problem.

v Consult the message log for message ID and text, time and date of themessage, as well as other data you can use to diagnose the problem.

Message formatIBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent messages have thefollowing format:

Message ID and textExplanationOperator Response

The message ID has the following format:CCC####severity

where:

CCC Prefix that indicates the component to which the message applies. Thecomponent is one of the following:

KRG General IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent messages

#### Number of the message

severitySeverity of the message. There are three levels of severity:

I Informational messages provide feedback about something thathappened in the product or system that might be important. Thesemessages can provide guidance when you are requesting a specificaction from the product.

W Warning messages call your attention to an exception condition.The condition might not be an error but can cause problems if notresolved.


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

E Error messages indicate that an action cannot be completedbecause of a user or system error. These messages require userresponse.

The Text of the message provides a general statement regarding the problem orcondition that occurred. The Explanation provides additional information about themessage and what might have caused the condition. The Operator Responseprovides actions to take in response to the condition, particularly for error messages(messages with the "E" suffix).

Note: Many message texts and explanations contain variables, such as the specificname of a server or application. Those variables are represented in thischapter as symbols, such as "&1." Actual messages contain values for thesevariables.

This chapter includes the messages for the following software:

v IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent

IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent messagesNotes:

1. In the following KRS messages, id is replaced by the TEDA server ID. This IDmatches the TEDA(Kpp) parameter passed to the TEDA server started taskprogram.

2. When any of the IBM Tivoli Enterprise Portal agents (KRJ, KRG, KRN, or KRH)share the same address space, the id and Kpp values will be those of theTEDA server address space.

KRG0000 Take Action was successfully issued.

Explanation: The Take Action was successfully issued, check the Advanced Reporting Event Data Workspace forthe result.

Operator response: Check the Advanced Report Event Data Workspace for the result.

KRG0004 User ID Translation failed.

Explanation: An invalid User ID was used for the Take Action

Operator response: Check to make sure the user ID being used has sufficient authority for the Take Action to beused. For more specific information check the TEDA log.

KRG0008 Bad Parameter List.

Explanation: Parameter list is invalid.

Operator response: Check to make sure the parameters used are valid. For more specific reason check the TEDAlog.

KRG0012 Bad KRS Environment.

Explanation: The invalid KRS environment was encountered.

Operator response: Check to make sure the KRS environment is up and running. For more specific reason checkthe TEDA log.

KRG0000 • KRG0012


KRS0001E id Required LE module module not loaded

Explanation: The indicated load module module is required by the Language Environment interface cannot be foundor loaded.

Operator response: Validate that the indicated load module can be found in either the JOBLIB/STEPLIB data setsor the z/OS system linklist. A server restart will be required to resolve the problem.

KRS0002E id LE Environment initialization failed RC=rc

Explanation: An attempt to initialize Language Environment for this task has failed with the indicated return code rc.The return code is issued from the init_sub_dp function call to CEEPIPI.

Operator response: Please refer to the z/OS Language Environment Programming Guide for an explanation of thereturn codes and possible corrective actions. A server restart will be required to resolve the problem.

KRS0003E id LE Environment termination failed RC=rc

Explanation: An attempt to initialize Language Environment for this task has failed with the indicated return code rc.The return code is issued from the term function call to CEEPIPI.

Operator response: Please refer to the z/OS Language Environment Programming Guide for an explanation of thereturn codes and possible corrective actions.

KRS0004E id CEEPIPI add of module failed RC=rc

Explanation: An attempt to add the indicated load module module to the Language Environment function table hasfailed with the indicated return code rc. The return code is issued from the add_entry function call to CEEPIPI.


KRS0005E id CEEPIPI function module missing

Explanation: The required Language Environment function load module module could not be found.

Operator response: There should be an AGENT statement of type "PIPI" for the indicated load module module inthe KppPRDxx member that is being used by the TEDA server. A server restart will be required to resolve the problem.

KRS0006E id CEEPIPI call of module failed RC=rc

Explanation: An attempt to call the indicated load module module to the Language Environment function table hasfailed with the indicated return code rc. The return code is issued from the call_sub function call to CEEPIPI.


KRS0007I id Agent agent using port portnum

Explanation: The indicated TEP agent agent is using the indicated port number portnum. The value of the portnumber is taken from the PORT keyword on the PRODUCT statement in the KppPRDxx member.

Operator response: No action is required.

KRS0008I id Agent agent connected to TEMA

Explanation: The indicated TEP agent agent has successfully connected to the TEMA address space.


KRS0001E • KRS0008I


KRS0009I id Agent agent disconnected from TEMA

Explanation: The indicated TEP agent agent has successfully disconnected from the TEMA address space.


KRS0010E id Agent agent service function failed RC=rc

Explanation: The indicated agent agent encountered a non-zero return code rc when calling the indicated CPCIfunction function.

Operator response: Refer to the following list of return codes

v CP_PORT_NOT_SET

v CP_SOCKET_OPEN_FAILED

v CP_STATE_ERROR

v CP_WRITE_ERROR

v CP_PARSING_ERROR

v CP_ATTRIBUTE_GROUP_NOT_REGISTERED

v CP_HANDLE_NOT_FOUND

v CP_ID_NOT_FOUND

v CP_MALLOC_FAILED

For CP_SOCKET_OPEN_FAILED, check that the TEMA address space is active and accepting connections from the"Kpp" product. When this condition is received, the TEDA address space retries every 30 seconds. For all other returncodes, please contact IBM Support.

KRS0011E id Attribute group register not found

Explanation: The internal attribute group register was not found. All attribute groups will not be registered with TEP.

Operator response: Ensure that the KppTEP00 agent statement is present in the KppPRDxx member. A serverrestart will be required to resolve the problem.

KRS0012E id Attribute group register is full

Explanation: There is no more room in the internal attribute group register. All subsequent attribute groups will notbe registered with TEP.

Operator response: Contact IBM Support.

KRS0013E id Attribute group module module not found

Explanation: One or more attribute groups require the indicated load module module and it could not be found orloaded.

Operator response: Verify that the indicated load module can be found in either the JOBLIB or STEPLIB data setsor the z/OS system linklist. A server restart will be required to resolve the problem.

KRS0014I id:product Attribute group group assigned handle handle

Explanation: The indicated attribute group group has been assigned the indicated handle handle for the indicatedproduct.

Note: This message is only shown for MsgLevel(1) and above.


KRS0009I • KRS0014I


KRS0015I id:product Attribute group group inactivated

Explanation: The indicated attribute group group has been inactivated and no further requests will be handled. Thismessage is normally issued during server termination.


KRS0016E id:product Attribute group group already registered

Explanation: An attempt to register the indicated attribute group group has been made when there is already one ofthe same name registered. The register request will be refused.


KRS0017I id:product Attribute group group registered with TEMA

Explanation: An attempt to register the indicated attribute group group has been made successfully. Data can nowflow between TEP and the TEDA server for this attribute group.


KRS0018I id Attribute group registration complete for agent

Explanation: The indicated agent agent has completed its registration phase.


KRS0019I id text

Explanation: This message is issued in response to a Take Action TEP request. The text of text varies depending onthe context of the action.

Operator response: It is intended that this message is processed by your automated operations software.

KRS0020W id Agent agent has no associated attribute groups

Explanation: The indicated agent agent has completed its registration phase and has not registered any attributegroups. This happens when all of the attribute groups are asynchronous in nature (pure event table) but the KppSYNCagent is defined so that it can respond to the TEP shutdown requests.


KRS0021W id TaskRequest received but no handler defined for product

Explanation: A take action request from TEP has been received for this product but there are no take actionhandlers defined for this product.


KRS0022E id Required product product missing

Explanation: The indicated product has not been declared in the TEDA KppPRDxx PARMLIB member.

Operator response: Ensure that the KppPRDxx PARMLIB member is present and has been specified in theKRSSYSxx member.

KRS0023E id TaskRequest product text

Explanation: The indicated product has received a task request with the indicated action text.

Operator response: This is an informational message issued when the MsgLevel setting is greater than zero.

KRS0015I • KRS0023E


KRS0030W id TEDA Kpp not found - Retrying every 60 seconds

Explanation: The KRSSIGNL utility program could not find the TEDA server specified on the runtime parameter. Itwill retry in 60 seconds.

Operator response: Start the indicated TEDA server.

KRS0031E id TEDA Kpp not found and maximum retry attempts exceeded

Explanation: The KRSSIGNL utility program could not find the TEDA server specified on the runtime parameter andthe maximum number of retry attempts has been exceeded. The KRSSIGNL program will terminate with a return codeof 8.

Operator response: Start the indicated TEDA server.

KRS0032W id TEDA Kpp not found - Retry or Cancel (R/C)

Explanation: The KRSSIGNL utility program could not find the TEDA server specified on the runtime parameter andRETRY(WTOR) was either specified or defaulted to.

Operator response: Start the TEDA server indicated. Specify R to retry or C to cancel the wait for the TEDA server.

KRS0033W id TEDA Kpp not found and retry cancelled by operator

Explanation: The KRSSIGNL utility program could not find the TEDA server specified on the runtime parameter andRETRY(WTOR) was either specified or defaulted to. The operator then replied C to Kpp0032W.


KRS0034I id Signal service failed RC=rc RSN=rsn

Explanation: The KRSSIGNL utility program failed with the indicated return code rc and reason code rsn.

Operator response: Examine any previous messages issued by the KppSIGNL utility.

KRS0035W id Signal signal not found for teda

Explanation: The KRSSIGNL utility program could not find the indicated signal signal the TEDA teda.

Operator response: Check that the signal name is correct and has been defined as a resource for the TEDA server.

KRS0040I id datatype refreshed successfully - nnn records

Explanation: The data collection routine for datatype has refreshed its cache of data, nnn records were collected.


KRS0041I id Interface established to jobname (product)

Explanation: The.TEDA has established an interface to the Base Product API jobname jobname product nameproduct

Operator response: None.

KRS0042I id SMF Record number for product is number

Explanation: The SMF Record number used by this product for reporting is number.


KRS0030W • KRS0042I


KRS0050I id Device Monitor has detected SMS system number number

Explanation: An SMS System number number has been detected.


KRS0051E id Device Monitor SMS BCD locate error RC=code

Explanation: An error code code has been returned while trying to detect an SMS BCD.

Operator response: Find why the Device Monitor SMS BCDS dataset is missing and recreate/restore it if necessary.

KRS0053I id agent initializing

Explanation: The indicated agent agent is initializing.


KRS0054I id agent initialization complete

Explanation: The indicated agent agent has completed its initialization phase.


KRS0055W id agent invalid runtime keyword keyword ignored

Explanation: The indicated agent agent has encountered an invalid runtime keyword keyword. The keyword will beignored.

Operator response: Correct the specification of the runtime keyword or contact IBM Support. A server restart will berequired to resolve the problem.

KRS0056I id agent terminating

Explanation: The indicated agent agent is terminating.


KRS0057I id agent termination complete

Explanation: The indicated agent agent has completed its termination phase.


KRS0059I id Current user ASID id Jobname Jobname

Explanation: During shutdown, the TEDA server has detected that some address spaces that still have outstandingactive connections. Each address space is listed by the KRS0059I message. The TEDA server will retry shutdown in30 seconds.


KRS0060I id There are no current users

Explanation: During shutdown, the TEDA server has detected that there are no current connections—terminationcan now proceed.




KRS0062E id Operating system level not supported

Explanation: The TEDA server has detected a level of z/OS that is not supported. The server will terminate.

Operator response: Check the installation instructions for the software prerequisites.

KRS0063E id Architecture level not supported

Explanation: The TEDA server has detected a level of hardware that is not supported. The server will terminate.

Operator response: Check the installation instructions for the hardware prerequisites.

KRS0064W id Shutdown prevented by active users : Retry/Ignore (R, I)

Explanation: The TEDA server shutdown is prevented because there are still active sessions with other addressspaces. The TEDA server will automatically retry every 30 seconds if the operator does not reply to this message.

Operator response: Reply R to retry or I to ignore. Replying I should be used with extreme caution and only in anemergency situation or when the z/OS system is being shutdown in preparation for an IPL. If you specify I, the TEDAserver termination will remove critical resources from the system without attempting normal serialization and it will notfree the common storage control blocks — leaving approximately 240K of orphaned E-CSA. The TEDA server will alsonot be able to restart until the address spaces that were in session have completely disconnected. Therefore, it isstrongly recommended that you reply R or wait for the TEDA server to retry every 30 seconds.

KRS0074I id TEDA initialization complete

Explanation: The TEDA server has successfully completed its initialization phase.


KRS0075I id Waiting for active connections to terminate

Explanation: The TEDA server is terminating but cannot continue until all active connections are terminated. If activeconnections are present, message KRS0064W will be issued.


KRSH0078I id TEDA shutdown proceeding

Explanation: The TEDA server is shutting down and is about to pass control to its termination routines.


KRS0080I id TEDA removing services

Explanation: All active connections are terminated. The TEDA server is now removing internal services.


KRS0082I id Dataspace dataspace created successfully

Explanation: The indicated dataspace dataspace has been successfully created.



KRS0083I id Dataspace dataspace removed

Explanation: The indicated dataspace dataspace has been successfully removed.





KRS0084E id Unknown operation

Explanation: An unknown or invalid MODIFY command was received.

Operator response: Correct the command and retry.

KRS0085E id Required keywords not specified

Explanation: Required keywords on the TEDA server modify command were not specified.

Operator response: Check the TEDA server modify command syntax and re-specify the required keywords.

KRS0086E id Unknown server server specified

Explanation: An agent specified a server server that is not valid.

Operator response: Correct the agent statement and restart the server.

KRS0087E id Server server already started

Explanation: A request to start a server was received but a server of that name was already running.

Operator response: If required, correct the server name and retry.

KRS0088I id Command accepted: command

Explanation: The TEDA server operator command has been accepted.


KRS0089E id Invalid command command

Explanation: The TEDA server operator command command is not valid.

Operator response: Check the TEDA server modify command syntax and re-issue the command.

KRS0090I id TEDA starting

Explanation: The TEDA server is starting.


KRS0091I id TCP/IP Server using port port

Explanation: The port number port is being used by this host for communications.

Operator response: None

KRS0092I id Server server control task terminated

Explanation: The indicated server server control task has terminated.


KRS0093E id Server server already stopped

Explanation: An attempt was made to stop a server that was already stopped. The request was ignored.

Operator response:

KRS0084E • KRS0093E


KRS0095I id TCP/IP Server host addressaddress

Explanation: The IP Address address is being used by this host for communications.

Operator response: None

KRS0096W id TCP/IP SERVER|CLIENT RC=code ERRNO= hcode (dcode:text)

Explanation: A TCP/IP Error occurred in the Server or Client, hcode, dcode and text give additional informationabout the error.

Operator response: Take steps to correct the TCP/IP error dependent on the particular error does and text messagedisplayed in the message.

KRS0097I id Agent agent in server server quiesced

Explanation: The indicated agent named agent in server server is now quiesced. This message is issued for allmatching agents when the TEDA server quiesce command has been issued. If the agent code supports the quiescecommand, it will cease activity until its is resumed.


KRS0098I id Agent agent in server server already quiesced - no action taken

Explanation: The indicated agent named agent in server server was already quiesced when a new attempt toquiesce it was received. No action was taken.


KRS0099I id No matches for Agent agent in server server

Explanation: There was no matches for the agent mask agent for the indicated server server.

Operator response: Re-specify the AGENT() keyword on the TEDA server operator modify command.

KRS0100I id No action taken for agent agent in server server

Explanation: There was no actions taken against any agent agent in the indicated server server. This is usuallycaused by the agents already being in the desired state when the quiesce or resume commands were issued.

Operator response: Verify that the correct modify command was issued to the TEDA server.

KRS0102I id Agent task name agent heartbeat

Explanation: Trace message written by the indicated agent agent when the MsgLevel is greater than 0.


KRS0103E id Common Dataspace dataspace ALESERV failed RC=rc

Explanation: During initialization the TEDA server could not perform the ALESERV ADD for the TEDA commondataspace. All SMF record intercept functions will be disabled.


KRS0104E id Required type name missing

Explanation: The required object of type type named name could not be found.

Operator response: Ensure that the associated statement is present in the KppPRDxx PARMLIB member. A serverrestart will be required to resolve the problem.



KRS0105E id Required keyword type missing for command

Explanation: The required keyword of type type is missing for the operator modify command command.

Operator response: Verify the syntax of the modify command and re-issue the command.

KRS0107I id agent msgtext

Explanation: Trace message written by the indicated agent agent when the MsgLevel is greater than 0.


KRS0109I id Agent task name agent terminated RC=rc

Explanation: The indicated agent agent has terminated with the specified return code rc.

Operator response: If the return code is non-zero and unexpected please contact IBM Support.

KRS0110I id TCP/IP Server waiting for in-use port {1}

Explanation: The server is trying to bind to port port which is already in use.

Operator response: None, the Server will retry the connection again.

KRS0112W id TCP/IP Server connection to host failed RC=code ERRNO= hcode (dcode:text)

Explanation: An error occurred trying to connect to hostname host, code, hcode, dcode and textgive additionalinformation about the error.

Operator response: Take steps to correct the TCP/IP error dependent on the particular error does and text messagedisplayed in the message.

KRS0113I id TCP/IP Server host name host

Explanation: The host name host is being used by this host for communications.


KRS0114I id Agent agentestablished connection to host using protocol

Explanation: The Agent agent has successfully connected to host host using the protocol protocol.


KRS0115I id Agent agent : Quiesced(Y/N) Address (address)

Explanation: Issued as the response from the D AGENT(mask) modify command, this message shows the quiescedstate and the address address in common storage of the agent block for the indicated agent agent.


KRS0118I id Agent agent in server server resumed

Explanation: The indicated agent agent in server server has been resumed and will restart its work.


KRS0119I id Agent agent in server server already active - no action taken

Explanation: The indicated agent agent in server server is already active and an attempt was made to resume it.The request is ignored.

Operator response: Ensure that the R AGENT(mask) command was issued correctly.



KRS0121I id TCP/IP Server waiting for host TCP/IP initialization RSN=code

Explanation: The server is trying to connect to a host which has not completed TCP/IP initialization, code givesmore information.

Operator response: None, the Server will retry the connection again.

KRS0126I id IBM Tivoli/product TEDA version

Explanation: The version version or the IBM Tivoli product product shown at TEDA server startup.


KRS0127I id Agent task name agent initialization complete

Explanation: The indicated agent agent has completed its initialization phase.


KRS0134E id Unknown keyword keyword

Explanation: An unknown keyword was discovered in the TEDA KppPRDxx PARMLIB member or as part of the TAGENT(mask) operator command.

Operator response: Re-specify the keyword and restart the server or re-issue the operator command.

KRS0135E id Error in statement : statement

Explanation: During the process of reading the KppPRDxx PARMLIB member, the TEDA server encountered one ormore errors in the statement shown statement.

Operator response: Examine earlier messages that explain the errors discovered.

KRS0139I id (cont) : text

Explanation: This message is a continuation of a previously issued message.

Operator response: Refer to the previously issued message.

KRS0143E id One or more parameters missing from the type statement

Explanation: During the process of reading the KppPRDxx PARMLIB member, the TEDA server encountered one ormore missing parameters for the indicated statement type type.

Operator response: Correct the statement in error and restart the TEDA server.

KRS0144E id Dataspace dataspace DSPSERV failed RC=rc RSN=rsn

Explanation: During the creation of the indicated dataspace dataspace, the DSPSERV service failed with returncode rc and reason code rsn.


KRS0145E id ALESERV failed RC=rc

Explanation: During an attempt to add a dataspace ALET to the access list, the ALESERV service failed with returncode rc.




KRS0147I id Agent task name agent initializing

Explanation: The indicated agent agent is beginning its initialization phase.


KRS0151E id Required keyword keyword missing from type for agent

Explanation: During the process of reading the KppPRDxx PARMLIB member, the required keyword keyword wasmissing from the statement type type for the indicated agent agent.

Operator response: Correct the statement in error and restart the TEDA server.

KRS0152I id Module module loaded successfully at address address

Explanation: The indicated load module module has been loaded at address address.



KRS0153E id Agent task name agent storage obtain failed

Explanation: The indicated agent agent could not obtain the required storage to perform its actions. Processing issuspended and retried during the next sampling interval.

Operator response: Increase the REGION size allocated to the TEDA server.

KRS0157W id Agent task name agent disabled - maximum restart count exceeded

Explanation: The indicated agent agent has terminated unexpectedly too many times and has exceeded its Restart()value. The agent will not be restarted.

Operator response: Examine the cause of the unexpected termination and contact IBM Support.

KRS0161E id Fatal error error in module module

Explanation: There has been a non-recoverable error error in server module module. The TEDA server willterminate.

Operator response: Contact IBM support.

KRS0162I id Agent agent in server TEDA updated with new value

Explanation: The indicated agent agent has been updated with a new value using the SET modify operatorcommand.


KRS0164E id Agent task name agent data collection failed RC=rc RSN=rsn

Explanation: The indicated agent agent has encountered problems during its data collection processing, the returncode rc and reason code rsn is shown.


KRS0166I id PC Routine routine installed for index index

Explanation: The indicated PC Routine routine has been installed and its index value index is shown.





KRS0167I id Invoking initialization routine routine

Explanation: The indicated initialization routine routine has been invoked.



KRS0168I id Invoking termination routine routine

Explanation: The indicated termination routine routine has been invoked.



KRS0176I id Dealt SMF record type number

Explanation: The SMF record number number has been intercepted by the TEDA server and successfully dealt to aSMF record handler agent.



KRS0177W id Discarded SMF record type number

Explanation: The SMF record number number has been intercepted by the TEDA server but was not given to anyinterested SMF record handler agent.



KRS0178E id Duplicate name name found for type statement

Explanation: While processing a statement type from parmlib, a duplicate name was discovered.

Operator response: Change the name on the statement to be unique.

KRS0179E id Duplicate keyword name specified

Explanation: While processing a statements from parmlib, a duplicate keyword name was discovered.

Operator response: Correct or remove the duplicate keyword.

KRS0180E id No supplied parameters for statement

Explanation: During the process of reading the KppPRDxx PARMLIB member, the indicated statement statement didnot contain any valid parameters.

Operator response: Refer to the Monitoring Agent Planning and Configuration Guide for more information on thekeywords and expected values and formats. Correct the statement and restart the TEDA server.

KRS0181E id Maximum number of object reached

Explanation: The maximum number of items has been reached for the indicated object object. All following items ofthe same type will be ignored.




KRS0182E id Invalid length of keyword_or_statement

Explanation: An invalid length was detected for the indicated keyword or statement keyword_or_statement.

Operator response: Refer to the Monitoring Agent Planning and Configuration Guide for more information on thekeywords and expected values and formats. Re-specify the keyword with valid values.

KRS0183E id Non-Hexadecimal characters in keyword

Explanation: A keyword keyword was expecting only hexadecimal characters (0-9 and A-F) its value, howevernon-hexadecimal characters have been detected.


KRS0184E id Value of value greater than maximum allowed maximum

Explanation: The keyword value value is greater than the allowed maximum maximum. The value is rejected.


KRS0185E id Value of value less than minimum allowed minimum

Explanation: The keyword value value is less than the allowed minimum minimum. The value is rejected.


KRS0186E id Non-Numeric characters in keyword

Explanation: A keyword keyword was expecting only numerical characters (0-9) in its value, however non-numericalcharacters have been detected.


KRS0187E id Invalid time specification in keyword

Explanation: A keyword was expecting a time format value and it detected an invalid value. The time format is :hh:mm:ss.th with all leading zeros included.


KRS0188E id Invalid range specification in keyword

Explanation: The value in keyword keyword is not in a valid range as required by the keyword.


KRS0189E id Invalid value specification in keyword

Explanation: The value in keyword keyword is invalid.


KRS0182E • KRS0189E


KRS0190W id Bad statement found : Abort, Continue or Ignore (A,C,I)

Explanation: During the process of reading the KppPRDxx PARMLIB member, there has been an error encounteredin at least one statement.

Operator response: Examine earlier error messages to determine the reason for the failure. Refer to the MonitoringAgent Planning and Configuration Guide for more information on the keywords and expected values and formats.Reply with one of the following choices :

v A — Abort the server startup.

v C — Continue with startup and ignore this statement only.

v I — Continue with startup and ignore all following statement errors.

KRS0191E id Load failed for module module RC=rc RSN=rsn

Explanation: The indicated load module module could not be loaded. The return code rc and reason code rsn isshown.

Operator response: Verify that the indicated load module can be found in either the JOBLIB or STEPLIB data setsor the z/OS system linklist. A server restart will be required to resolve the problem.

KRS0192E id Invalid reply

Explanation: The reply to the TEDA server WTOR did not match one of the valid value. The reply will be ignored.

Operator response: Reply to the WTOR with one of the listed values.

KRS0194I id Server Abend ac RSN=rsn

Explanation: The TEDA server abended with the indicated abend code ac and reason code rsn.

Operator response: Please contact IBM Support.

KRS0195I id SMF Exit exit installed successfully

Explanation: The indicated SMF exit exit has been installed successfully.


KRS0196E id CSVDYNEX DEFINE for exit failed RC=rc RSN=rsn

Explanation: During the DEFINE for the indicated SMF exit exit, the TEDA server received an unexpected returncode rc and reason code rsn.


KRS0197E id CSVDYNEX ADD for exit failed RC=rc RSN=rsn

Explanation: During the ADD for the indicated SMF exit exit, the TEDA server received an unexpected return coderc and reason code rsn.


KRS0198E id Service service failed RC=rc RSN=rsn

Explanation: The indicated service service failed with return code rc and reason code rsn.


KRS0190W • KRS0198E


KRS0199E id text

Explanation: This is a general purpose error message. The text gives the specific error encountered.

Operator response: Review the contents of the message and take any steps indicated to correct the error.

KRS0999I id msgtext

Explanation: This is a trace message written by the various agents when the MsgLevel is greater than 0.


KRSJ0036I Signal signal updated for teda

Explanation: The KRSSIGNL utility program found the indicated signal signal for the TEDA teda and its value hasbeen updated.


KRSJ0041I id interface established to software (server)

Explanation: The TEDA has established an interface to the indicated software. If the software has a server addressspace, it is also listed.


KRS0199E • KRSJ0041I



Appendix A. IBM Tivoli Enterprise Console event mapping

Each event class corresponds to an attribute group in the IBM Tivoli EnterpriseConsole. For a description of the event slots for each event class, see the lists inthis appendix. For more information about mapping attribute groups to eventclasses, see the IBM Tivoli Monitoring Administrator's Guide.

Generic event mapping provides useful event class and attribute information forsituations that do not have specific event mapping defined. BAROC files are foundon the Tivoli Enterprise Monitoring Server in the installation directory in TECLIB(that is, install_dir/cms/TECLIB for Windows systems and install_dir/tables/TEMS_hostname/TECLIB for UNIX systems). IBM Tivoli Enterprise Console eventsynchronization provides a collection of ready-to-use rule sets that you can deploywith minimal configuration. Be sure to install IBM Tivoli Enterprise Console eventsynchronization to access the correct Sentry.baroc, which is automatically includedduring base configuration of IBM Tivoli Enterprise Console rules if you indicate thatyou want to use an existing rulebase. See the IBM Tivoli Monitoring Installation andSetup Guide for details.

Each of the event classes is a child of KRG_Base and is defined in the krg.barocfile. The KRG_Base event class can be used for generic rules processing for anyevent from the IBM Tivoli Advanced Audit for DFSMShsm.

For events generated by situations in the Agent Status Summary attribute group,Tivoli Enterprise Console events are sent using theITM_KRG_AGENT_STATUS_SUMMARY class. This class contains the followingslots:

v node: STRING

v timestamp: STRING

v errseqnum: INTEGER

v errattgrp: STRING

v errmsg: STRING

For events generated by situations in the Backup Control Data Set Error Summaryattribute group, Tivoli Enterprise Console events are sent using theITM_KRG_BACKUP_CONTROL_DATA_SET_ERROR_SUMMARY class. This classcontains the following slots:

v node: STRING

v timestamp: STRING

v bcsdiagid: STRING

v bcsreccnt: INTEGER

v bcsdiagmsg: STRING

v bcserrcnt: INTEGER

v bcserrtyp: INTEGER

For events generated by situations in the BCDS Error Group1 attribute group, TivoliEnterprise Console events are sent using the ITM_KRG_BCDS_ERROR_GROUP1class. This class contains the following slots:

v node: STRING

v timestamp: STRING

v bcd1diagid: STRING


v dsname: STRING

v bcd1hdsn: STRING

v bcd1bkdate: STRING

v bcd1vsam: INTEGER

v bcd1vsam_enum: STRING

v bcd1bkvers: INTEGER

v volser: STRING


v node: STRING

v timestamp: STRING


v dsname: STRING

v bcd2hdsn: STRING

v volser: STRING


v bcd2vsam: INTEGER


v bcd2tp: INTEGER

v bcd2tp_enum: STRING


v bcd2bkgen: STRING

v bcd2tapet: STRING

v bcd2ttxt: INTEGER

v bcd2privol: STRING


v node: STRING

v timestamp: STRING


v dsname: STRING

v bcd3hdsn: STRING

v volser: STRING


v bcd3vsam: INTEGER


v bcd3tp: INTEGER


v bcd3vtocer: INTEGER



v node: STRING

v timestamp: STRING


v dsname: STRING

v bcd4hdsn: STRING

v volser: STRING


v bcd4vsam: INTEGER


v bcd4tp: INTEGER



v bcd4bkown: STRING


v node: STRING

v timestamp: STRING


v volser: STRING

v bcd5tapet: STRING

v bcd5dsnnum: INTEGER


v node: STRING

v timestamp: STRING


v volser: STRING

v bcd6tapet: STRING

v bcd6bcnt: INTEGER

v bcd6btcnt: INTEGER

v bcd6dtupd: STRING

v bcd6dtcre: STRING


v node: STRING

v timestamp: STRING


v bcd7migvol: STRING

v bcd7tapet: STRING

v bcd7ttxt: INTEGER

v bcd7dsflg: STRING

Appendix A. IBM Tivoli Enterprise Console event mapping 111

v bcd7dsptch: STRING

v bcd7dsoff: INTEGER

v bcd7fgoff: INTEGER

v bcd7aname: STRING

v bcd7tname: STRING


v node: STRING

v timestamp: STRING


v bcd8vol1: STRING

v bcd8type1: STRING

v bcd8stat1: STRING

v bcd8vol2: STRING

v bcd8type2: STRING

v bcd8stat2: STRING

For events generated by situations in the Product Advice attribute group, TivoliEnterprise Console events are sent using the ITM_KRG_EXPERT_ADVICE class.This class contains the following slots:

v node: STRING

v timestamp: STRING

v errid: STRING

v heading: STRING

v advice: STRING

For events generated by situations in the HSEND List Event Information attributegroup, Tivoli Enterprise Console events are sent using theITM_KRG_HSEND_LIST_EVENT_INFORMATION class. This class contains thefollowing slots:

v node: STRING

v timestamp: STRING

v command: STRING

v datetime: STRING

v userid: STRING

v result: STRING

v rowcnter: INTEGER

For events generated by situations in the HSM Tape Error Summary attribute group,Tivoli Enterprise Console events are sent using theITM_KRG_HSM_TAPE_ERROR_SUMMARY class. This class contains thefollowing slots:

v node: STRING

v timestamp: STRING

v tpsdiagid: STRING

v tpsreccnt: INTEGER


v tpsdiagmsg: STRING

v tpserrcnt: INTEGER

v taperrtyp: INTEGER

For events generated by situations in the HSMTAPE Error Group1 attribute group,Tivoli Enterprise Console events are sent using theITM_KRG_HSMTAPE_ERROR_GROUP1 class. This class contains the followingslots:

v node: STRING

v timestamp: STRING

v tpd1diagid: STRING

v volser: STRING

v tpd1tapet: STRING

v tpd1dsnnum: INTEGER

For events generated by situations in the HSMTAPE Error Group2 attribute group,Tivoli Enterprise Console events are sent using theITM_KRG_HSMTAPE_ERROR_GROUP2 class. This class contains the followingslots:

v node: STRING

v timestamp: STRING

v tpd2diagid: STRING

v volser: STRING

v tpd2tapet: STRING

v tpd2dsnnum: INTEGER

v tpd2expire: STRING

v dsname: STRING

v tpd2crjob: STRING

For events generated by situations in the LISTCAT Event Information attributegroup, Tivoli Enterprise Console events are sent using theITM_KRG_LISTCAT_EVENT_INFORMATION class. This class contains thefollowing slots:

v node: STRING

v timestamp: STRING

v command: STRING

v datetime: STRING

v userid: STRING

v result: STRING

v rowcnter: INTEGER

For events generated by situations in the MCDS Error Group1 attribute group, TivoliEnterprise Console events are sent using the ITM_KRG_MCDS_ERROR_GROUP1class. This class contains the following slots:

v node: STRING

v timestamp: STRING

v mcd1diagid: STRING

v dsname: STRING

v mcd1hdsn: STRING


v mcd1hvol: STRING

v mcd1vsam: INTEGER

v mcd1vsam_enum: STRING

v mcd1hlvl: STRING

v mcd1catvol: STRING

v mcd1catlg: STRING


v node: STRING

v timestamp: STRING


v dsname: STRING

v mcd2comp: STRING

v mcd2halias: STRING

v volser: STRING


v node: STRING

v timestamp: STRING


v volser: STRING

v mcd3tapet: STRING

v mcd3dsnnum: INTEGER


v node: STRING

v timestamp: STRING


v dsname: STRING

v mcd4hvol: STRING

v mcd4catlg: STRING

v mcd4create: STRING


v node: STRING

v timestamp: STRING


v volser: STRING

v mcd5tapet: STRING

v mcd5bcnt: INTEGER


v mcd5btcnt: INTEGER

v mcd5bcntx: STRING

v mcd5btcntx: STRING

v mcd5dtupd: STRING

v mcd5dtcre: STRING


v node: STRING

v timestamp: STRING


v mcd6migvol: STRING

v mcd6tapet: STRING

v mcd6ttxt: INTEGER

v mcd6dsflg: STRING

v mcd6dsptch: STRING

v mcd6dsoff: INTEGER

v mcd6fgoff: INTEGER

v mcd6aname: STRING

v mcd6tname: STRING


v node: STRING

v timestamp: STRING


v dsname: STRING

v mcd7hdsn: STRING

v mcd7hvol: STRING

v mcd7vsam: INTEGER

v mcd7vsam_enum: STRING

v mcd7hlvl: STRING

v mcd7catvol: STRING

v mcd7catlg: STRING

For events generated by situations in the Migration Control Data Set ErrorSummary attribute group, Tivoli Enterprise Console events are sent using theITM_KRG_MIGRATION_CONTROL_DATA_SET_ERROR_SUMMARY class. Thisclass contains the following slots:

v node: STRING

v timestamp: STRING

v mcsdiagid: STRING

v mcsreccnt: INTEGER

v mcsdiagmsg: STRING

v mcserrcnt: INTEGER


v mcserrtyp: INTEGER

For events generated by situations in the OCDS Error Group1 attribute group, TivoliEnterprise Console events are sent using the ITM_KRG_OCDS_ERROR_GROUP1class. This class contains the following slots:

v node: STRING

v timestamp: STRING

v ocd1diagid: STRING

v volser: STRING

v ocd1tapet: STRING

v ocd1crdate: STRING

v ocd1pvol: STRING

v ocd1cpvol: STRING

v dsname: STRING


v node: STRING

v timestamp: STRING


v volser: STRING

v ocd2tapet: STRING


v ocd2svol: STRING

v ocd2csvol: STRING

v ocd2ldsn: STRING


v node: STRING

v timestamp: STRING


v volser: STRING

v ocd3tapet: STRING


v ocd3expseq: INTEGER

v ocd3encseq: INTEGER


v node: STRING

v timestamp: STRING


v volser: STRING

v ocd4tapet: STRING



v ocd4expext: INTEGER

v ocd4encext: INTEGER


v node: STRING

v timestamp: STRING


v volser: STRING

v ocd5tapet: STRING


v ocd5expblk: INTEGER

v ocd5encblk: INTEGER

For events generated by situations in the Offline Control Data Set Error Summaryattribute group, Tivoli Enterprise Console events are sent using theITM_KRG_OFFLINE_CONTROL_DATA_SET_ERROR_SUMMARY class. This classcontains the following slots:

v node: STRING

v timestamp: STRING

v ocsdiagid: STRING

v ocsreccnt: INTEGER

v ocsdiagmsg: STRING

v ocserrcnt: INTEGER

v ocserrtyp: INTEGER

For events generated by situations in the Performance Object Status attributegroup, Tivoli Enterprise Console events are sent using theITM_KRG_PERFORMANCE_OBJECT_STATUS class. This class contains thefollowing slots:

v node: STRING

v timestamp: STRING

v query_name: STRING

v object_name: STRING

v object_type: INTEGER

v object_type_enum: STRING

v object_status: INTEGER

v object_status_enum: STRING

v error_code: INTEGER

v error_code_enum: STRING



Appendix B. Documentation library

This appendix contains information about the publications related to the IBM TivoliAdvanced Audit for DFSMShsm Monitoring Agent. These publications are listed inthe following categories:

v IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent library

v Prerequisite publications

v Related publications

See the IBM Tivoli Monitoring and OMEGAMON XE products: DocumentationGuide, SC23-8816, for information about accessing and using publications. You canfind the Documentation Guide in the IBM Tivoli Monitoring and OMEGAMON® XEInformation Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm.

To find a list of new and changed publications, click What's new on the Welcomepage of the IBM Tivoli Monitoring and OMEGAMON XE Information Center. To findpublications from the previous version of a product, click Previous informationcenters on the Welcome page for the product.

IBM Tivoli Advanced Audit for DFSMShsm Monitoring Agent libraryThere is one document specific to the IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent: IBM Tivoli Advanced Audit for DFSMShsm Monitoring AgentUser's Guide. This publication provides agent-specific information for configuring,using, and troubleshooting the IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent

Use the configuration chapter in this guide with the IBM Tivoli Monitoring Installationand Setup Guide to set up the software.

Use the information in this guide with the Tivoli Enterprise Portal User's Guide tomonitor IBM Tivoli Advanced Audit for DFSMShsm resources.

Prerequisite publicationsTo use the information in this publication effectively, you must have someprerequisite knowledge, which you can obtain from the following IBM TivoliMonitoring publications:

v Exploring IBM Tivoli Monitoring

v IBM Tivoli Monitoring Administrator's Guide

v IBM Tivoli Monitoring Agent Builder User’s Guide

v IBM Tivoli Monitoring Command Reference

v IBM Tivoli Monitoring: Configuring Tivoli Enterprise Monitoring Server on z/OS

v IBM Tivoli Monitoring Installation and Setup Guide

v IBM Tivoli Monitoring: Messages

v IBM Tivoli Monitoring Troubleshooting Guide

v IBM Tivoli Monitoring: Upgrading from Tivoli Distributed Monitoring

v IBM Tivoli Monitoring: Upgrading from V5.1.2

v Tivoli Enterprise Portal User's Guide

v IBM Tivoli Monitoring: i5/OS® Agent User's Guide


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.docguide.doc/DocGuide.htm

v IBM Tivoli Monitoring: Linux OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX Log OS Agent User's Guide

v IBM Tivoli Monitoring: UNIX OS Agent User's Guide

v IBM Tivoli Monitoring: Windows OS Agent User's Guide

v IBM Tivoli Monitoring Universal Agent User's Guide

v IBM Tivoli Monitoring Universal Agent API and Command ProgrammingReference Guide

Related publicationsThe following documents also provide useful information:

v IBM Tivoli Enterprise Console Adapters Guide

v IBM Tivoli Enterprise Console Event Integration Facility User’s Guide

v IBM Tivoli Enterprise Console Reference Manual

v IBM Tivoli Enterprise Console Rule Builder’s Guide

Other sources of documentationYou can also obtain technical documentation about Tivoli Monitoring andOMEGAMON XE products from the following sources:

v IBM Tivoli Open Process Automation Library (OPAL)

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

OPAL is an online catalog that contains integration documentation as well asother downloadable product extensions. This library is updated daily.

v Redbooks

http://www.redbooks.ibm.com/

IBM Redbooks®, Redpapers, and Redbooks Technotes provide information aboutproducts from platform and solution perspectives.

v Technotes

You can find Technotes through the IBM Software Support Web site athttp://www.ibm.com/software/support/probsub.html, or more directly through yourproduct Web site, which contains a link to Technotes (under Solve a problem).

Technotes provide the latest information about known product limitations andworkarounds.


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

http://www.redbooks.ibm.com/


Appendix C. Accessibility

Accessibility features help users with physical disabilities, such as restricted mobilityor limited vision, to use software products successfully. The major accessibilityfeatures in this product enable users to do the following:

v Use assistive technologies, such as screen-reader software and digital speechsynthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.

v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the followingfeatures to aid accessibility:

v All documentation is available in both HTML and convertible PDF formats to givethe maximum opportunity for users to apply screen-reader software.

v All images in the documentation are provided with alternative text so that userswith vision impairments can understand the contents of the images.

Navigating the interface using the keyboardStandard shortcut and accelerator keys are used by the product and aredocumented by the operating system. See the documentation provided by youroperating system for more information.

Magnifying what is displayed on the screenYou can enlarge information on the product windows using facilities provided by theoperating systems on which the product is run. For example, in a Microsoft®

Windows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. See the documentation provided by youroperating system for more information.



Appendix D. Notices

This information was developed for products and services offered in the U.S.A. IBMmay not offer the products, services, or features discussed in this document in othercountries. Consult your local IBM representative for information on the products andservices currently available in your area. Any reference to an IBM product, program,or service is not intended to state or imply that only that IBM product, program, orservice may be used. Any functionally equivalent product, program, or service thatdoes not infringe any IBM intellectual property right may be used instead. However,it is the user's responsibility to evaluate and verify the operation of any non-IBMproduct, 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 you anylicense 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, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR 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 improvements and/orchanges in the product(s) and/or the program(s) described in this publication at anytime 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 thoseWeb sites. The materials at those Web sites are not part of the materials for thisIBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believesappropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purpose ofenabling: (i) the exchange of information between independently created programsand other programs (including this one) and (ii) the mutual use of the informationwhich 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 material availablefor it are provided by IBM under terms of the IBM Customer Agreement, IBMInternational Program License Agreement or any equivalent agreement between us.

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.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating systems. You may copy,modify, and distribute these sample programs in any form without payment to IBM,for the purposes of developing, using, marketing or distributing application programsconforming to the application programming interface for the operating system forwhich the sample programs are written. These examples have not been thoroughlytested under all conditions. IBM, therefore, cannot guarantee or imply reliability,serviceability, or function of these programs. You may copy, modify, and distributethese sample programs in any form without payment to IBM for the purposes ofdeveloping, using, marketing, or distributing application programs conforming toIBM's application programming interfaces.

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

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the Web at "Copyright andtrademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,and/or other countries.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.


www.ibm.com/legal/copytrade.shtml

www.ibm.com/legal/copytrade.shtml

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

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, 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.

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

Appendix D. Notices 125


Index

Aaccessibility 121actions

See Take Action commandsagent

trace logs 76Agent Status Summary

situations 62, 63workspaces

descriptions 10list 9

Agent Status Summary attribute group 16Agent Status Summary workspace 10agents

troubleshooting 84Alias Name attribute 29, 44Attribute Group attribute 17attribute groups

Agent Status Summary 16Backup Control Data Set Error Summary 17BCDS Error Group1 18BCDS Error Group2 20BCDS Error Group3 22BCDS Error Group4 23BCDS Error Group5 25BCDS Error Group6 26BCDS Error Group7 27BCDS Error Group8 29HSEND List Event Information 30HSM Tape Error Summary 32HSMTAPE Error Group1 33HSMTAPE Error Group2 34list of all 13LISTCAT Event Information 35MCDS Error Group1 36MCDS Error Group2 38MCDS Error Group3 39MCDS Error Group4 40MCDS Error Group5 41MCDS Error Group6 42MCDS Error Group7 44Migration Control Data Set Error Summary 45more information 13OCDS Error Group1 47OCDS Error Group2 48OCDS Error Group3 49OCDS Error Group4 50OCDS Error Group5 52Offline Control Data Set Error Summary 53overview 13Performance Object Status 54Product Advice 57

attributesAgent Status Summary 16Alias Name 29, 44Attribute Group 17Backup Control Data Set Error Summary 17

attributes (continued)Backup Date 19, 20, 23, 24Backup Generation 21Backup Owner 25Backup Version 19, 21, 25BCDS Error Group1 18BCDS Error Group2 20BCDS Error Group3 22BCDS Error Group4 24BCDS Error Group5 25BCDS Error Group6 26BCDS Error Group7 28BCDS Error Group8 29Block Count 27, 41Catalog Data Set Name 37, 40, 45Cataloged Volser 37, 38, 45Command 31, 36Conflicting Volser 30Correct Previous Volume 48Correct Successor Volume 49Counted Records (Hex) 42Create Date 40, 47, 49, 50, 51, 52Create Job Name 35Data Set Count 34, 35Data Set Name 19, 20, 22, 24, 37, 40, 44Data Set Name Flag 28, 43Data set Patch Valid Flag 28Data Set Patch Valid Flag 43Duplicate Volser 30Encountered Block Count 53Encountered Extention Number 51Encountered Sequence Number 50Error Code 56Error Count 18, 32, 46, 54Error ID 17, 19, 20, 22, 24, 25, 26, 28, 30, 32, 33,

34, 37, 38, 39, 40, 41, 43, 44, 46, 47, 48, 49, 51,52, 53, 58

Error Message 17, 18, 32, 46, 54Error Sequence Number 16Error Type 18, 33, 46, 54Expected Block Count 52Expected Extention Number 51Expected Sequence Number 50Expire Date 35First Data Set 48HSEND List Event Information 31HSM Alias Data Set Name 38HSM Internal Data Set Name 19, 20, 22, 24, 37, 45HSM Level 37, 45HSM Tape Error Summary 32HSM Tape Type 21, 26, 27, 28, 33, 34, 39, 41, 43,

47, 48, 50, 51, 52HSM Volser 37, 40, 45HSMTAPE Error Group1 33HSMTAPE Error Group2 34Last Data Set 49LISTCAT Event Information 35MCDS Error Group1 36


attributes (continued)MCDS Error Group2 38MCDS Error Group3 39MCDS Error Group4 40MCDS Error Group5 41MCDS Error Group6 42MCDS Error Group7 44Migrate Volser 28, 43Migration Control Data Set Error Summary 46more information 13Node 16, 17, 18, 20, 22, 24, 25, 26, 28, 29, 31, 32,

33, 34, 35, 36, 38, 39, 40, 41, 42, 44, 46, 47, 48,49, 50, 52, 53, 55, 58

Object Name 55Object Status 56Object Type 55OCDS Error Group1 47OCDS Error Group2 48OCDS Error Group3 49OCDS Error Group4 50OCDS Error Group5 52Offline Control Data Set Error Summary 53overview 13Performance Object Status 55Previous Volume in OCDS 47Primary Volser 22Product Advice 57, 58Product Advice Heading 58Query Name 55Record Count 17, 32, 46, 53Request Result 31, 36Row Counter 31, 36Status 30Successor Volume in OCDS 49Tape Data Set Name 35Tape Reference Count 26, 39Tape/DASD 21, 23, 24Timestamp 16, 17, 18, 20, 22, 24, 25, 26, 28, 30,

31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 44,46, 47, 48, 49, 51, 52, 53, 55, 58

True Name 29, 44TTOC Data Set Offset 29, 43TTOC Extension Number 21, 28, 43TTOC Flag Offset 29, 44TTOC/Create Date 27, 42TTOC/Update Date 27, 42User ID 31, 36Valid Blocks 27, 41Valid TTOC Records (Hex) 42Volser 19, 20, 22, 24, 26, 27, 33, 34, 39, 41, 47,

48, 49, 51, 52Volume Type 30VSAM Cluster Data Set Name 38VSAM Component Name 38VSAM Flag 19, 20, 23, 24, 37, 45VTOC Error 23

BBackup Control Data Set Error Summary

situations 62, 63

Backup Control Data Set Error Summary (continued)workspaces


Backup Control Data Set Error Summary attributegroup 17

Backup Control Data Set Error Summaryworkspace 11

Backup Date attribute 19, 20, 23, 24Backup Generation attribute 21Backup Owner attribute 25Backup Version attribute 19, 21, 25BCDS Error Group1 attribute group 18BCDS Error Group2 attribute group 20BCDS Error Group3 attribute group 22BCDS Error Group4 attribute group 23BCDS Error Group5 attribute group 25BCDS Error Group6 attribute group 26BCDS Error Group7 attribute group 27BCDS Error Group8 attribute group 29Block Count attribute 27, 41built-in troubleshooting features 75

Ccalculate historical data disk space 58capacity planning

IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent 59

capacity planning for historical data 58Catalog Data Set Name attribute 37, 40, 45Cataloged Volser attribute 37, 38, 45Command attribute 31, 36commands, Take Action 67components 2configuration 5Conflicting Volser attribute 30Correct Previous Volume attribute 48Correct Successor Volume attribute 49Counted Records (Hex) attribute 42Create Date attribute 40, 47, 49, 50, 51, 52Create Job Name attribute 35

Ddata

trace logs 76data logged


data provider logsSee agent

Data Set Count attribute 34, 35Data Set Name attribute 19, 20, 22, 24, 37, 40, 44Data Set Name Flag attribute 28, 43Data set Patch Valid Flag attribute 28Data Set Patch Valid Flag attribute 43disk capacity planning

See capacity planningdisk capacity planning for historical data 58


documentationSee publications

Duplicate Volser attribute 30

EEncountered Block Count attribute 53Encountered Extention Number attribute 51Encountered Sequence Number attribute 50environment

features 1functions 1

Error Code attribute 56Error Count attribute 18, 32, 46, 54Error ID attribute 17, 19, 20, 22, 24, 25, 26, 28, 30,

32, 33, 34, 37, 38, 39, 40, 41, 43, 44, 46, 47, 48, 49,51, 52, 53, 58

Error Message attribute 17, 18, 32, 46, 54Error Sequence Number attribute 16Error Type attribute 18, 33, 46, 54event

mapping 109Expected Block Count attribute 52Expected Extention Number attribute 51Expected Sequence Number attribute 50Expire Date attribute 35

Ffeatures, IBM Tivoli Advanced Audit for DFSMShsm

Monitoring Agent 1files

agent trace 76installation trace 76other trace log 77trace logs 76

First Data Set attribute 48functions, IBM Tivoli Advanced Audit for DFSMShsm

Monitoring Agent 1

Ggathering support information 75

Hhistorical data

calculate disk space 58capacity planning

IBM Tivoli Advanced Audit for DFSMShsmMonitoring Agent 59

disk capacity planning 58HSEND List Event Information



HSEND List Event Information attribute group 30HSEND List Event Information workspace 11HSEND_LIST_DSNAME action 68

HSEND_LIST_TTOC action 69HSM Alias Data Set Name attribute 38HSM Internal Data Set Name attribute 19, 20, 22, 24,

37, 45HSM Level attribute 37, 45HSM Tape Error Summary



HSM Tape Error Summary attribute group 32HSM Tape Error Summary workspace 11HSM Tape Type attribute 21, 26, 27, 28, 33, 34, 39,

41, 43, 47, 48, 50, 51, 52HSM Volser attribute 37, 40, 45HSMTAPE Error Group1 attribute group 33HSMTAPE Error Group2 attribute group 34

IIBM Software Support 75IBM Support Assistant 91IBM Tivoli Advanced Audit for DFSMShsm

situations 62workspaces


IBM Tivoli Advanced Audit for DFSMShsm MonitoringAgent

components 2features 1functions 1performance considerations 87

IBM Tivoli Advanced Audit for DFSMShsmworkspace 10

IBM Tivoli Enterprise Consoleevent mapping 109

informationtroubleshooting 75

information, additionalattributes 13policies 73situations 61Take Action commands 67workspaces 9

installationlog file 76problems 81silent 5

interface, user 2ISA 91

KKRG_BCDS_Critical_Error situation 63KRG_HSM_Tape_Critical_Errors situation 63KRG_MCDS_Critical_Error situation 64KRG_OCDS_Critical_Error situation 65

Index 129

LLast Data Set attribute 49legal notices 123library, IBM Tivoli Advanced Audit for DFSMShsm

Monitoring Agent 119list of messages 92LISTCAT Event Information



LISTCAT Event Information attribute group 35LISTCAT Event Information workspace 11LISTCAT_ENT action 70logged data


loggingagent trace logs 76, 77built-in features 75installation log files 76trace log files 76

MMCDS Error Group1 attribute group 36MCDS Error Group2 attribute group 38MCDS Error Group3 attribute group 39MCDS Error Group4 attribute group 40MCDS Error Group5 attribute group 41MCDS Error Group6 attribute group 42MCDS Error Group7 attribute group 44messages

built-in features 75for IBM Tivoli Advanced Audit for DFSMShsm

Monitoring Agent 92format 91overview 91syntax 91

Migrate Volser attribute 28, 43Migration Control Data Set Error Summary



Migration Control Data Set Error Summary attributegroup 45

Migration Control Data Set Error Summaryworkspace 11

NNode attribute 16, 17, 18, 20, 22, 24, 25, 26, 28, 29,

31, 32, 33, 34, 35, 36, 38, 39, 40, 41, 42, 44, 46, 47,48, 49, 50, 52, 53, 55, 58

OObject Name attribute 55Object Status attribute 56

Object Type attribute 55OCDS Error Group1 attribute group 47OCDS Error Group2 attribute group 48OCDS Error Group3 attribute group 49OCDS Error Group4 attribute group 50OCDS Error Group5 attribute group 52Offline Control Data Set Error Summary



Offline Control Data Set Error Summary attributegroup 53

Offline Control Data Set Error Summary workspace 12OPAL documentation 120

Pperformance considerations 87Performance Object Status attribute group 54policies

more information 73overview 73

Previous Volume in OCDS attribute 47Primary Volser attribute 22problems and workarounds 81Product Advice attribute 58Product Advice attribute group 57Product Advice Heading attribute 58publications


OPAL 120prerequisite 119Redbooks 120related 120Technotes 120types 119

purposestroubleshooting 75

Qqueries, using attributes 13Query Name attribute 55

RRecord Count attribute 17, 32, 46, 53Redbooks 120remote deployment

troubleshooting 83Request Result attribute 31, 36requirements 5Row Counter attribute 31, 36

Ssilent installation 5


situationsgeneral troubleshooting 87, 88KRG_BCDS_Critical_Error 63KRG_HSM_Tape_Critical_Errors 63KRG_MCDS_Critical_Error 64KRG_OCDS_Critical_Error 65list of all 62more information 61overview 61predefined 62

situations, using attributes 13Software Support 90Status attribute 30Successor Volume in OCDS attribute 49support

gathering information for 75list of messages 92messages 91

support assistant 91syntax

messages 91

TTake Action commands

HSEND_LIST_DSNAME 68HSEND_LIST_TTOC 69list of all 67LISTCAT_ENT 70more information 67overview 67predefined 67troubleshooting 90

Tape Data Set Name attribute 35Tape Reference Count attribute 26, 39Tape/DASD attribute 21, 23, 24Technotes 120Timestamp attribute 16, 17, 18, 20, 22, 24, 25, 26, 28,

30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 44,46, 47, 48, 49, 51, 52, 53, 55, 58

Tivoli Common Reportingtroubleshooting 90

trace logs 76trademarks 124troubleshooting 75, 81

agents 84built-in features 75installation 81installation logs 76messages 91remote deployment 83situations 87, 88Take Action commands 90Tivoli Common Reporting 90uninstallation 81uninstallation logs 76workspaces 85

True Name attribute 29, 44TTOC Data Set Offset attribute 29, 43TTOC Extension Number attribute 21, 28, 43TTOC Flag Offset attribute 29, 44

TTOC/Create Date attribute 27, 42TTOC/Update Date attribute 27, 42

Uuninstallation

log file 76problems 81

User ID attribute 31, 36user interfaces options 2

VValid Blocks attribute 27, 41Valid TTOC Records (Hex) attribute 42views

Agent Status Summary workspace 10Backup Control Data Set Error Summary

workspace 11HSEND List Event Information workspace 11HSM Tape Error Summary workspace 11IBM Tivoli Advanced Audit for DFSMShsm

workspace 10LISTCAT Event Information workspace 11Migration Control Data Set Error Summary

workspace 11Offline Control Data Set Error Summary

workspace 12Volser attribute 19, 20, 22, 24, 26, 27, 33, 34, 39, 41,

47, 48, 49, 51, 52Volume Type attribute 30VSAM Cluster Data Set Name attribute 38VSAM Component Name attribute 38VSAM Flag attribute 19, 20, 23, 24, 37, 45VTOC Error attribute 23

Wworkarounds 81

agents 84remote deployment 83situations 87Take Action commands 90Tivoli Common Reporting 90workspaces 85

workspacesAgent Status Summary 10Backup Control Data Set Error Summary 11HSEND List Event Information 11HSM Tape Error Summary 11IBM Tivoli Advanced Audit for DFSMShsm 10list of all 9LISTCAT Event Information 11Migration Control Data Set Error Summary 11more information 9Offline Control Data Set Error Summary 12overview 9predefined 9troubleshooting 85

Index 131


��

Printed in USA

SC27-2349-01

Documents

IBM Tivoli Advanced Audit for DFSMShsm Monitoring …publib.boulder.ibm.com/tividd/td/ITAAfDFSM/SC27-2349-01/en_US/PDF… · Capacity planning for historical data logged by Advanced