Operations Knowledge Module for IBM i

Operations Knowledge Module for IBM i

User Guide

1.3VMC-KIO

Operations Knowledge Module for IBM i User Guide

The software described in this book is furnished under a license agreement and may be used only in

accordance with the terms of the agreement.

Copyright Notice

Copyright © 2013 Tango/04 All rights reserved.

Document date: May 2013

Document version: 1.0

Product version: 1.3

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic mechani-cal, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Tango/04.

Trademarks

Any references to trademarked product names are owned by their respective companies.

Technical Support

For technical support visit our web site at www.tango04.com.

Tango/04 Computing Group S.L. Avda. Meridiana 358, 5 A-B Barcelona, 08027 Spain

Tel: +34 93 274 0051

http:\\www.tango04.com

http:\\www.tango04.com

Table of Contents

Table of Contents

Table of Contents .............................................................................. iii

How to Use this Guide........................................................................vi

Chapter 1

Introduction ...................................................................................... 1

Chapter 2

Generating Business Views and Dashboards ......................................... 22.1. Producing CSV Files.......................................................................................2

2.2. Generating IBM i System Controls..................................................................4

2.2.1. Created Controls .......................................................................................8

2.3. Generating Job Controls .................................................................................8


2.4. Generating Job Duration Controls ..................................................................9


2.5. Generating Subsystem Controls .....................................................................9

2.5.1. Created Controls .....................................................................................10

2.6. Generating Job Queue Controls ...................................................................10


2.7. Generating Port Controls ..............................................................................10


2.8. Generating Library Storage Controls ............................................................11


2.9. Generating Library Group Storage Controls .................................................12


© 2013 Tango/04 Computing Group Page iii

Table of Contents

2.10. Generating History Log Controls.................................................................12

2.11. Generating Configuration Component Controls..........................................13

2.12. Generating Message Queue Controls ........................................................14

Chapter 3

Mapping Applications....................................................................... 173.1. Creating an Application Folder......................................................................17

3.2. Copy-Paste as Link all Corresponding Controls ...........................................19

3.3. Create SLA Monitors.....................................................................................21

3.4. Final Result ...................................................................................................22

Chapter 4

Maintenance ................................................................................... 23

Chapter 5

Calendar Management ..................................................................... 275.1. Creating a Calendar......................................................................................27

5.1.1. Naming Calendars ..................................................................................28

5.2. Activating the Calendars Monitor ..................................................................28

5.3. Business Views in SmartConsole .................................................................29

5.4. Associating the Calendar with the Application ..............................................29

5.4.1. Application Criticalness Propagation.......................................................29

5.5. Final Effect ....................................................................................................30

Chapter 6

Alarms............................................................................................ 316.1. Awaiting Events in Specific Calendar Alarms ...............................................31

6.1.1. Creating a Calendar ................................................................................31

6.1.2. Generating the Job Folder ......................................................................32

6.1.3. Activating Alarms ....................................................................................32

6.1.4. Alarm Effect.............................................................................................33

6.1.5. Final Effect ..............................................................................................34

6.2. Model-based Alarms .....................................................................................34

6.2.1. Configuring Notifications .........................................................................34

6.2.2. Configuration Steps.................................................................................36

6.2.3. Creating New Notification Folders...........................................................37

© 2013 Tango/04 Computing Group Page iv

Table of Contents

Chapter 7

Reports ........................................................................................... 39

Appendices

Appendix A: Toolkit - Frequent Controls.............................................. 40A.1. Libraries........................................................................................................40

A.1.1. Size and Number of Objects of a Library (System i Custom Command)40

A.1.2. Size of a Library (Storage Management Agentless) ...............................42

A.1.3. Size of a Group of Libraries (Storage Management Agentless) .............43

A.2. Objects .........................................................................................................45

A.2.1. Existence Check (System i Custom Command).....................................45

A.2.2. Object Attribute (System i Custom Command).......................................47

A.3. Files ..............................................................................................................49

A.3.1. Number of Records in File/Deleted Records (System i Custom Command)...................................................................................................49

A.3.2. Data in Spooled File ...............................................................................50

A.4. Data Areas....................................................................................................52

A.4.1. Data Area Content ..................................................................................52

A.5. Integration with iSeries Performance Manager (Visual Control for Jobs).....54

Appendix B: Filters ........................................................................... 56

Appendix C: Contacting Tango/04...................................................... 58

About Tango/04 Computing Group .................................................... 60

Legal Notice .................................................................................... 61

© 2013 Tango/04 Computing Group Page v

How to Use this Guide

© 2013 Tango/04 Computing Group Page vi

How to Use this Guide

This chapter explains how to use Tango/04 User Guides and understand the typographical conventions

used in all Tango/04 documentation.

Typographical Conventions

The following conventional terms, text formats, and symbols are used throughout Tango/04 printed

documentation:

Convention Description

Boldface Commands, on-screen buttons and menu options.

Blue Italic References and links to other sections in the manual or further documentation containing relevant information.

Italic Text displayed on screen, or variables where the user must substitute their own details.

Monospace Input commands such as System i commands or code, or text that users must type in.

UPPERCASEKeyboard keys, such as CTRL for the Control key and F5 for the function key that is labeled F5.

Notes and useful additional information.

Tips and hints that will improve the users experience of working with this product.

Important additional information that the user is strongly advised to note.

Warning information. Failure to take note of this information could potentially lead to serious problems.

Introduction

© 2013 Tango/04 Computing Group Page 1

Chapter 1 1 Introduction

The Operations Knowledge Module for IBM i monitors all your critical applications available on the

platform to ensure you have the power to:

• quickly solve technical issues

• prioritize incidents according to their impact on the business

• control your systems and applications from anywhere via the Web

• manage a practical framework to guarantee continuous service improvements

• and much more...

This module is a complete IBM i Operations monitoring solution, with dashboards, reports, pre-

configured alerts, and agile processes included out of the box that will provide total visibility over the

platform and its applications.

Furthermore the Knowledge module harnesses all the vast experience that Tango/04 have of working

with the IBM i platform over many years, in a format that is easily and quickly deployed to ensure instant

results and value from the solution.

This user guide will explain exactly how to configure and use the knowledge module to ensure you get

the most from this powerful solution.

Generating Business Views and Dashboards

Chapter 22 Generating Business Views and Dashboards

In this chapter we will explain how to create all the controls needed by the Knowledge Module in order to

successfully monitor your IBM i Operations.

When we talk about controls we are referring to groups of events such as Availability, Performance, or

Storage events, which are modeled in SmartConsole. To create these controls we will generate sets of

monitors in ThinkServer based on the monitor templates included in the Knowledge Module and some

native agents.

From the monitors we will produce the controls in the form of events that will be retrieved by Business

Views, which in turn will be managed in SmartConsole folders.

Events will also be sent to dashboards in order to produce a complete series of graphs, accessible by

multiple users via the Web, showing real-time information, historic tendencies and even future events.

For further information regarding controls and their definitions please refer to the Operation Knowledge

Module for IBM i - Detailed Scope document.

2.1 Producing CSV FilesBefore you can start working with the Operations Knowledge Module for IBM i, an analysis phase will

take place, during which, the following excel file must be updated with user data which provides details

of all the controls to be created:

System i Module- CSV Generation.xls

This information will either be added by the end user or a Tango/04 consultant. An example of the

information needed for a typical IBM i monitoring project is provided in the Operations Knowledge

Module for IBM i - Example Controls document.

Using the data added to this excel file, all required CSV files can be generated.

Important Before you begin the steps described below, you must already have all Tango/04 products

and the Operations Knowledge Module for IBM i installed. Remember that the names of the NiceLink connections to the system i’s must have the same

system names in Thinkserver, in order to make the Business Views work properly.


http://kb.tango04.com/content/155407

http://customers.tango04.com/sites/default/files/vmc-ibmiopsc-en.pdf

http://customers.tango04.com/content/155407







To create the CSV files:

Step 1. Open the System i Module- CSV Generation.xls excel file

Step 2. Navigate to the Input sheet in the excel file

Step 3. Click the CSV files for ThinkServer Generation macro execution button in the excel

file as shown in Figure 1:

Figure 1 – Click here to produce the CSV file

Step 4. The files are created by default in the same folder where the excel file resides.

This action generates the CSV files that will be used to create all the controls that the Knowledge

Module requires, as explained in the following sections.

(1) The 6 Applications.csv file is not required at this stage but will be used to map the application

structure in SmartConsole (see Chapter 3 - Mapping Applications on page 17).

CSV File Name Description

1 System i Servers Defines the systems to be monitored

2 THKSJobActivity Defines the jobs to be monitored

3 THKSJobDuration Defines the job durations to be monitored

4 THKSSBSActivity Defines the subsystems to be monitored

5 THKSJobQueues Defines the job queues to be monitored

6 Applications(1) Defines the application structure to map in the Smart-Console

8 THKSPorts Defines the ports to be listening on

9 THKSLibrarySize-Increase Defines the libraries to be monitored

10 THKSLibListSize-Increase

Defines the library lists to be monitored

11 System i HistoryLogDefines the filters to be applied to the History log mes-sages

12 System i DVM_DEV Defines DVM Agent devices that are to be monitored

13 System i DVM_CTLDefines DVM Agent controllers that are to be moni-tored

14 System i DVM_LINE Defines DVM Agent lines that are to be monitored

15 System i MsgQueues Defines the message queues to be monitored



2.2 Generating IBM i System ControlsThe CSV file containing details of the IBM i systems to be monitored is called:

1 System i Servers.csv

Monitors controlling the number of HLD, LCKW, INEL and MSGW jobs in the system (i.e 1. #SERVERNAME# iSeries Jobs - Job Status Agent - HLD) filter by job type. The filter is set to include only BCH jobs. Depending on the environment, you can change or eliminate this filter, but consider that eliminating this filter could generate overheads on the system i.

Figure 2 – Monitor filter configuration

To generate the system monitors:

Step 1. Open ThinkServer and select all the monitors corresponding to System i HEALTH that start with number 1. These monitors are the templates that will be propagated when configuring the systems. Check the health thresholds of each and validate that they are adequate for the environment. If not, adjust the values as desired.

Step 2. Open SmartConsole and check that the autoprovisioning alarms are activated.

Tip

If you change the filter, consider changing the title appearing in the dashboard that is set in the T04Custom file.



Figure 3 – Autoprovisioning alarms are activated in SmartConsole

Step 3. Open ThinkServer and select all the monitor templates starting with 1.

Figure 4 – Select all monitor templates beginning with the number 1 and select Multiple copy

Step 4. Right-click on the templates and select Multiple copy.

Step 5. Click the Import from... button and navigate to the 1 System i Servers.csv file and

click Open and click OK.



Figure 5 – Import monitors for each server from the 1 System i Servers.csv file

The monitors are automatically created.

To generate the system controls for each IBM i:

Step 1. Start the Ping monitor corresponding to the system.

Step 2. Click iSeries Operations Agents in the ThinkServer List and select all the new

Operations Agent monitors created for the system, right-click on them and select

Monitor Settings.

Figure 6 – Edit the monitor settings for all the new Operations Agents for the system

Step 3. Set the User and Password and click OK.



Figure 7 – Set the user and password in the Monitor Settings window

Step 4. Start the new Operations Agent monitors for the system.

Step 5. Click Data Adapter Agents in the ThinkServer List and select all the new Data Adapter

Agent monitors created for the system, right-click on them and select Monitor Settings.

Figure 8 – Edit the monitor settings for all the new Data Adapter Agents for the system

Step 6. Set the DSN, User and Password in the DSN settings dialog box and click OK.

Step 7. Start the Data Adapter monitors for the system.

Step 8. Open the IBM i terminal and enter option 35 in the BD_MENU.

Step 9. Enter option 6 to activate all INCLUDE filters of the HST Agent listed. All filters will

change to *ACTIVE status.



Figure 9 – activate all INCLUDE filters of the HST Agent

Step 10. Open SmartConsole and add a new NiceLink connection to the IBM i. Please refer to

the VISUAL Message Center SmartConsole User Guide for further details regarding

how to add a NiceLink connection.

2.2.1 Created ControlsThe following are automatically generated for each IBM i:

• In the SmartConsole:

− a folder for the IBM i is created

− performance events and generic job information appear

− HST and BCH events appear in the corresponding Business Views

• The following dashboards are populated with data:

− System i KIT – Initial Page

− System i KIT – System i General

− System i KIT – CPU Monitoring

− System i KIT – Disk Monitoring

− System i KIT – Memory Monitoring

2.3 Generating Job ControlsThe CSV file containing details of the jobs to be monitored is called:

2 THKSJobActivity.csv

To generate the job monitors:



Step 3. Click the Import from... button and navigate to the 2 THKSJobActivity.csv file and



To generate the job controls for each IBM i:

Step 1. Select all the new job monitors created for the system, right-click on them and select

Monitor Settings.


Step 3. Start the monitors for the system.






− for each job, a new folder is created within the JOBS folder of the corresponding IBM i.

− Job activity events appear

2.4 Generating Job Duration ControlsThe CSV file containing details of the duration to monitor jobs is called:

3 THKSJobDuration.csv

To generate the monitors:



Step 3. Click the Import from... button and navigate to the 3 THKSJobDuration.csv file and



To generate the job duration controls for each IBM i:

Step 1. Select all the new job monitors created for the system, right-click on them and select

Monitor Settings.





− for each job, a new folder is created within the JOBS folder of the corresponding IBM i.

2.5 Generating Subsystem ControlsThe CSV file containing details of the subsystems to be monitored is called:

4 THKSSBSActivity.csv

To generate the subsystem monitors:



Step 3. Click the Import from... button and navigate to the 4 THKSSBSActivity.csv file and





To generate the subsystem controls for each IBM i:

Step 1. Select all the new subsystem monitors created for the system, right-click on them and

select Monitor Settings.





− for each subsystem a new folder is created within the SUBSYSTEMS folder of the

corresponding IBM i.

− Subsystem activity events appear

2.6 Generating Job Queue ControlsThe CSV file containing details of the job queues to be monitored is called:

5 THKSJobQueues.csv

To generate the job queue monitors:



Step 3. Click the Import from... button and navigate to the 5 THKSJobQueues.csv file and click

Open and click OK.


To generate the job queue controls for each IBM i:

Step 1. Select all the new job queues monitors created for the system, right-click on them and

select Monitor Settings.





− for each job queue a new folder is created within the JOBQ folder of the corresponding IBM i.

− Job queue activity events appear

2.7 Generating Port ControlsThe CSV file containing details of the ports to be listened to is called:

8 THKSPorts.csv






Step 3. Click the Import from... button and navigate to the 8 THKSPorts.csv file and click

Open and click OK.


Step 4. Start all monitors.



− for each port a new Business View is created within the Network & Configuration Components \ Ports folder of the corresponding IBM i.

− Events appear in the Business View

2.8 Generating Library Storage ControlsThe CSV file containing details of library storage size is called:

9 THKSLibrarySize-Increase.csv




Step 3. Click the Import from... button and navigate to the 9 THKSLibrarySize-Increase.csv file and click Open and click OK.


To generate the library storage controls for each IBM i:

Step 1. Select all the new library storage size monitors created for the system, right-click on

them and select Monitor Settings.





− for each library a new folder is created within the Storage folder of the corresponding IBM i.


Important If a library does not contain objects, the monitor returns an error because the internal command used (DSPOBJD) cannot give any output.



2.9 Generating Library Group Storage ControlsThe CSV file containing details of library list storage size is called:

10 THKSLibListSize-Increase.csv




Step 3. Click the Import from... button and navigate to the 10 THKSLibListSize-Increase.csv file and click Open and click OK.


To generate the library group controls for each IBM i:

Step 1. Select all the new library storage size monitors created for the system, right-click on

them and select Monitor Settings.





− for each group of libraries a new folder is created within the Storage folder of the

corresponding IBM i.


2.10 Generating History Log ControlsThe CSV file where the filters to be applied to the History log messages are defined is called:

11 System i HistoryLog.csv

The Operations Knowledge Module for IBM i includes the basic filters needed to ensure that events from

the HST Agent are managed and do not consume too much CPU. These filters were installed during the

installation process (please refer to the Operations Knowledge Module for IBM i - Installation Guide for

further details), and activated earlier when generating the IBM i system controls in Step 9 on page 7.

Please refer to Appendix B: Filters on page 56 for a complete list of the filters and their expressions.

In this step we will need to create a new filter to ensure that all target applications are included when

generating history log controls.

Note In this case, no ThinkServer monitors exist, only the HST native agent. This means that

setting up this task is less automated than for previous tasks and requires manual

configuration on the IBM i side.




To generate history log controls:

Step 1. Open the IBM i terminal and enter option 35 in the BD_MENU.

Step 2. Create the custom filter.

Using the predefined Custom Messages filter as a template, create a similar INCLUDE

filter to include all the message patterns (#MSGPATTERN#) defined in the 11 System i HistoryLog.csv file.

For example:

(&agent_code='HST') and (&msg_id like 'VMC%')

Where 'VMC%' equals each #MSGPATTERN# defined in the CSV file. TIP: Replace the

asterisk (*) with %. To add more than one #MSGPATTERN# separate each one with a

comma (,).

All messages that match the filter will be included.

Figure 10 – Filter example for the message pattern: VMC*

Step 3. Open SmartConsole and navigate to the #MSGPATTERN# HST Messages folder: System i/ Templates/ #MSGPATTERN# HST Messages

Step 4. Right-click on the folder and select Multiple copy.

Click the Import from... button and navigate to the 11 System i HistoryLog.csv file

and click Open and click OK.

Step 5. A new folder for each message pattern is created in the following folder:

System i/ Templates/

Move these folders to this folder:

Availability/ #SERVERNAME# Historical Messages

where #SERVERNAME# is the name of the corresponding server.

2.11 Generating Configuration Component ControlsThe following CSV files where DVM Agent configuration components are defined, are used in this step:

12 System i DVM_DEV.csv

13 System i DVM_CTL.csv

14 System i DVM_LINE.csv

Note No ThinkServer monitors exist, only the DVM native agent.



To generate configuration component controls:

Step 1. Open the IBM i terminal and enter option 6 in the NiceLink Menu, then enter option 52

in the VISUAL Message Center Menu to access the DVM Agent controls.

Step 2. Enter option 1 in the Device Manager Monitor menu to access the DVM Agent

Maintenance configuration settings.

Step 3. Enter details of the DVM Agent devices, controllers, and lines to monitor, using the data

found in the above CSV files.

Step 4. Start the DVM Agent.

Step 5. When an event is generated, a folder is automatically created in SmartConsole in the

Network and Configuration Components folder. NOTE: Remember that this agent only sends events in case of a failure.

Figure 11 – Add the DVM Agent devices, controllers, and lines to monitor

2.12 Generating Message Queue ControlsThe CSV file where the message queues to be monitored are defined is called:

15 System i MsgQueues.csv

Note In this case, no ThinkServer monitors exist, only the BCH native agent. This means that

setting up this task is less automated than for previous tasks and manual intervention is

required.



To generate message queue controls:

Step 1. Open the IBM i terminal and enter option 6 in the NiceLink Menu, then enter option 11

in the VISUAL Message Center Menu to access the Work with message queues

configuration.

Step 2. Enter details of the BCH Agent configurations using the data found in the 15 System i MsgQueues.csv file. NOTE: The message pattern cannot be specified here, which means a further manual

step is required (see Step 5 below).

Step 3. Start the BCH Agent

Step 4. When an event is generated, a folder corresponding to the mesaage queue is

automatically created in SmartConsole in the Critical Messages folder.

Step 5. In each message queue folder you will need to manually add the message pattern used

in the filter to the name of the Business View using multiple copy in SmartConsole

Important After the implementation phase, it is recommend to de-activate the alarm associated with this task because this alarm can generate overheads in the SmartConsole if left activated. The alarm name is:

New iSeries #MSGQueueLib#/#MSGQueueName#

Figure 12 – Deactivate the alarm



Figure 13 – Add the message pattern used in the filter to the name of the Business View using multiple copy


Mapping Applications

Chapter 33 Mapping Applications

When all the necessary ºcontrols have been defined as explained in the previous chapter, it is time to

map each of them to the corresponding applications, copying Business Views or folders from their

source into the destination application subtree, thereby modeling the collected information in

SmartConsole by application.

By creating a new folder for each application, we use the applications as a Service Control Point (SCP),

which enables the automated monitoring of the availability of Service Level Agreements (SLAs).

The complete tree structures for IBM i Infrastructure Monitoring are detailed in the Operations

Knowledge Module for IBM i - Detailed Scope document.

There are three simple steps in this process:

Step 1. Create an application folder in the SmartConsole

Step 2. Copy and paste the corresponding controls as links

Step 3. Create the SLA monitors

3.1 Creating an Application FolderThe following monitor template corresponds to the definition of an application. It is defined as a Service

Control Point:

#APPLICATIONNAME# Application

Figure 14 – Template folder for applications

Note The copy action used in this step is copy-paste as link







To create an application folder:

Step 1. Open SmartConsole and right-click the #APPLICATIONNAME# Application template

in the Business Network tree, and select Multiple Copy.

Step 2. Click the Import button and navigate to the following CSV file generated by the Excel

spreadsheet earlier (see section 2.1 - Producing CSV Files on page 2):

6 Applications.csv

Figure 15 – Import the application structure from the 6 Applications.csv file using Multiple copy

Step 3. Enter the name/s of the application/s to replace the place holder text

#APPLICATIONNAME# in the Replace Texts List fields and click OK.

Figure 16 – Multiple Copy parameters for two applications

Step 4. The template will be duplicated in the Business Network for each application entered in

the previous step, and the name will be automatically changed.

Step 5. Move the folder/s of the application/s from the template folder to the corresponding IBM

i in the SmartConsole Business Network.



Figure 17 – Move the copied folders to the IBM i in the Business Network

A complete set of folders and Business Views for each application are now mapped in

the SmartConsole and ready for the controls that were created in the previous chapter.

Figure 18 – Application structures successfully modeled in SmartConsole

3.2 Copy-Paste as Link all Corresponding ControlsOnce the application structures have been created in SmartConsole, the next step is to allocate all the

previously generated controls to the correct folders using the Paste as link function.

To allocate the controls to the corresponding folders:

Step 1. Open SmartConsole and navigate to the controls in the Business Network that were

created in the previous chapter. We must perform the following steps for each control to

be mapped. TIP: Use the Consolidate Data macro in the Input sheet of the Excel file to filter by

application. This will tell you which controls correspond to each application and provide



a useful list to work through. In Figure 19 below we can see that we must start with the

Job controls and the first Job control in the list is the Daemon control.

Figure 19 – Use the Consolidate Data macro in the Input sheet of the Excel file to filter by application, which will help you to systematically allocate each control in SmartConsole. In the example above

we can see the jobs that we must map to the VMC application for the PIPELINE IBM i.

Step 2. Right-click on the controls and select Copy.

Step 3. Right-click the corresponding folder for the application in the Business Network and

select Paste as link.

Figure 20 – Copy and Paste as link each set of controls to the correct folder for each application

Step 4. Repeat for each control (not only jobs, but also job queues, ports, message queues,

etc.) and for each application created in section 3.1 - Creating an Application Folder on

page 17.



3.3 Create SLA MonitorsThe final step to ensure all applications are successfully mapped, is to create the corresponding SLA

monitors in ThinkServer for each application defined. These monitors will check SLA progress over

various time periods.

To create the SLA monitors:

Step 1. Open ThinkServer and navigate to the SLA monitor templates:

• #APPLICATIONNAME# This hour - SCP and Tags (Database) Monitor

• #APPLICATIONNAME# This Day - SCP and Tags (Database) Monitor

• #APPLICATIONNAME# This Month - SCP and Tags (Database) Monitor

Step 2. Select them all, right-click and select Multiple Copy.

Figure 21 – Multiple copy the SLA monitor templates in ThinkServer

Step 3. Click the Import from... button and navigate to the following CSV file and click Open:

6 Applications.csv

Step 4. The name/s of the application/s to replace the place holder text #APPLICATIONNAME# are filled in in the Replace Texts List fields, click OK.

Step 5. Select all the new SLA monitors, right-click on them and select Monitor Settings.

Step 6. Set the DSN, User and Password correspondig to the BSM database and click OK.

Step 7. Edit each monitor and modify:

• in the SCP FILTERS tab replace the text #APPLICATIONNAME# (do not remove the *at the end),

• in the Target DSN tab indicate the ODBC DSN name, user and password

corresponding to the output database.

Step 8. Start the monitors.

Important These monitors generate output data that is written in a specific database. Before you begin

this database must be created in the SQL Server engine and an ODBC data source created .



3.4 Final ResultAfter completing the above steps the following dashboard will be fully functional displaying data for the

mapped applications:

System i KIT – Application Monitoring

Figure 22 – System i KIT – Application Monitoring dashboard, in the control bar you can select the IBM i and the application to monitor in real-time. The application model or Business View tree is

displayed as well as problems detected and SLA values including worst components and history.


Maintenance

Chapter 44 Maintenance

This chapter explains the various procedures required to make sure the Operations Knowledge Module

for IBM i configuration is correctly maintained when infrastructure changes appear.

Note The following procedures described in the table below consider the System i Module- CSV Generation.xls Excel file as the basis for all actions.

Element Action Procedure

IBM i

Add

• Create a new Excel file

• Add the IBM i and any other controls desired for

that system in the correct worksheets

• Follow the standard procedure described in

section 2.2 - Generating IBM i System Controls

on page 4

Delete

• Delete the folder for the IBM i in SmartConsole

• Delete all monitors in ThinkServer that

correspond to the IBM i (starting with a number

followed by the system name)

Job

Add


• Add the IBM i where the job must run to the

Systems i worksheet and add the new job to

monitor in the Jobs sheet


section 2.3 - Generating Job Controls on page 8

Delete

• Delete the folder for the job in the IBM i folder in

SmartConsole


correspond to the job (monitors starting with

numbers 2 and 3 plus the system name)

Change• Follow the procedure above to delete a Job

• Follow the procedure above to add a Job


Maintenance

Subsystem

Add


• Add the IBM i where the subsystem must

run to the Systems i worksheet and add the

new subsystem to monitor in the Subsytems

worksheet


section 2.5 - Generating Subsystem Controls on

page 9

Delete

• Delete the folder for the subsystem in the IBM i

folder in SmartConsole


correspond to the subsystem (monitors starting

with number 4 plus the system name)

Change • N/A

JobQueue

Add


• Add the IBM i where the job queue must run

to the Systems i worksheet and add the new

job queue to monitor in the Job Queue

worksheet


section 2.6 - Generating Job Queue Controls on

page 10

Delete

• Delete the folder for the job queues in the IBM i



correspond to the job queue (monitors starting

with number 5 plus the system name)

Change

• Follow the procedure above to delete a job

queue

• Follow the procedure above to add a job queue

Port

Add


• Add the IBM i where the port is to be

monitored to the Systems i worksheet and

add the port in the System i Ports worksheet


section 2.7 - Generating Port Controls on

page 10

Delete

• Delete the folder for the port in the IBM i folder in

SmartConsole


correspond to the port (monitors starting with

number 8 plus the system name)

Change • N/A



Maintenance

Library Size

Add


• Add the IBM i where the library resides to

the Systems i worksheet and add the library

to monitor in the LibrarySize worksheet


section 2.8 - Generating Library Storage Controls

on page 11

Delete

• Delete the folder for the library in the IBM i folder

in SmartConsole




Change • N/A

Library List Size

Add


• Add the IBM i where the libraries resides to

the Systems i worksheet and add the library

list to monitor in the LibraryListSize

worksheet


section 2.9 - Generating Library Group Storage

Controls on page 12

Delete

• Delete the folder for the library list in the IBM i





Change • N/A

History log

Add

• Define the pattern of the messages that you want

to receive

• Activate filters in option 35 of the BD_MENU in

native agents and check that the pattern is

included


• Add the pattern in the HSTLog worksheet.


section 2.10 - Generating History Log Controls

on page 12

Delete

• Delete the Business View corresponding to the

pattern in the Historical Messages. folder

• Delete the inclusion filters in native agents, if

applicable

Change • N/A



Maintenance

Devices, controllers and lines

Add• Add the line, controller or device to the DVM

Agent in the IBM i

Delete

• Delete the folder corresponding to the device/

controller/line in the Network & configuration

components folder

• Delete the device/controller/line from the DVM

Agent configuration

Change • N/A

Message Queues

Add


• Add the IBM i where the message queue

resides in the Systems i worksheet and add

the new message queue name to monitor in

the Message Queue worksheet

• Add the message queue name in the BCH Agent

configuration


section 2.12 - Generating Message Queue

Controls on page 14

Delete

• Delete the message queue in the BCH Agent

configuration

• Delete the folder for the message in the MSGQ

folder for the IBM i in SmartConsole

Change • N/A



Calendar Management

Chapter 55 Calendar Management

It is often the case that an application or a component has periods of time that need special

consideration for monitoring, whether it is an unexpected downtime period, or specific times when the

application is extremely active.

For example, a server with maintenance tasks or an application that must be available from 8:00-9:00.

These periods often need to be excluded from calculations such as forecasting or historical reports to

make sure there are no anomalies in calculations so it is important to have flexible control of these

periods.

This chapter explains how to apply calendars to manage the availability of any element in the solution.

5.1 Creating a CalendarCalendars are created using the SharedObjects Calendar Service and define periods (ranges) of dates

and times, such as Monday to Friday 9:00-18:00. Those periods can be used to filter messages. For

instance, calendars help you easily define Business Views that take care of messages occurring at

some specific periods. Calendars are used by all VISUAL Message Center products that use

SharedObjects but it is important to maintain flexibility on a product by product basis, and therefore

calendars for use by SmartConsole Web Client are created within SmartConsole Web Client.

For detailed instructions regarding creating calendars please refer to the SmartConsole Web Client User

Guide.

For use with the Operations Knowledge Module for IBM i you can create calendars that detail the period

of time that a component must be available.

For example, if a service is unavailable due to a of maintenance task, on Sunday, from 4:00-7:00, the

calendar should look like this:

Figure 23 – Sample availability calendar




Calendar Management

5.1.1 Naming CalendarsCalendars for the operations Knowledge Module should use the following naming convention:

#SERVERNAME# xxxx

where #SERVERNAME# is the name of the IBM i, and xxxx represents a useful description of the

calendar.

5.2 Activating the Calendars MonitorIncluded in the Operations Knowledge Module for IBM i is a monitor called T04 – Calendars that, for

each calendar created for use with the module, generates an event indicating if, at this moment the

period indicated in the calendar is active or not.

• BLUE health indicates the calendar is NOT currently active.

• GREEN health indicates that the calendar IS active.

Therefore using the previous example on page 27, on Sunday at 5AM the event is BLUE. On Saturday,

at any time it will be GREEN.

Before starting the calendars monitor, the SharedObjects URL must be set within the monitor.

To set the SharedObjects URL for the calendars monitor:

Step 1. Open ThinkServer and select the T04 – Calendars monitor.

Step 2. Click the Monitor Settings button on the toolbar and click the Health and Actions

button and select the Additional Parameters tab.

Figure 24 – Additional Parameters tab displaying the sharedObjectURL variable to be edited

Step 3. Set the location of SharedObjects.

Add the URL to the sharedObjectURL variable:

Figure 25 – Enter the URL for SharedObjects

Note A default calendar 7 x 24, will always be GREEN.


Calendar Management

Click OK.

5.3 Business Views in SmartConsoleFor each new calendar, a Business View is automatically created in the Calendars folder when the first

event is received in the SmartConsole.

The name of the Business View is Calendar plus the CalendarName. In Figure 26 below we can see the

Business View for the calendar called PIPELINE – Online Customer Service.

Figure 26 – Calendar Business Views

5.4 Associating the Calendar with the ApplicationEach application has the following structure in the SmartConsole Business Network:

Figure 27 – Application structure in the Business Network

Note that there is a folder named Calendar. This folder, if applicable, will contain a link to a Business

View corresponding to a particular calendar.

5.4.1 Application Criticalness PropagationAn Advanced criticalness propagation for the application folder is selected and defined as shown in

Figure 28 below:

Figure 28 – Application folder criticalness propagation


Calendar Management

This rules set here dictate that if the health state of the Calendar folder is BLUE, then a BLUE health

state is propagated to the parent folder. If the health state of the Calendar folder is GREEN, then the

color propagated to the parent folder is the one corresponding to the other subtree.

5.5 Final EffectWhen a calendar is active the health of the SCP is BLUE, this means that when an SLA is calculated,

this period will be considered as available and taken into account.


Alarms

Chapter 66 Alarms

Alerts allow for real-time warning of abnormal situations, such as detecting when CPU consumption

surpasses a pre-defined level during peak time. They are configured through correlation and filtering

options, allowing for reporting by various means and uses, and can include escalation policies when

necessary.

This module includes two specific types of pre-defined alarms.

• Awaiting events in specific calendar alarms

• Modeling based alarms

Any other type of alarm must be manually created.

For detailed instructions regarding creating alarms please refer to the SmartConsole Web Client User

Guide.

6.1 Awaiting Events in Specific Calendar AlarmsA very frequent control is to check that a job has started or ended during a specific period of time. This

control responds to a real need such as: the backup must finish before 04:00, otherwise user activity

cannot start on time at 06:00.

In this section, we explain how to use calendars to cover this topic.

The following instructions relate to jobs starting and ending in a specific calendar but, bear in mind that

these instructions apply to any other situation where an event is expected in a specific calendar.

6.1.1 Creating a CalendarCreate a calendar detailing the period of time in which the job should start or end.

Important The name of the calendar is very important. It must have the following structure:

#SERVERNAME# #JOBNAME# Starting

or

#SERVERNAME# #JOBNAME# Ending

where #SERVERNAME# is the IBM i name, and #JOBNAME# is the name of the job.




Alarms

If the backup starts at 02:00 and must end before 04:00, the calendar should look like this:

Figure 29 – A calendar that is active between 2 A.M. and 4 A. M.

Note that PIPELINE is the name of the IBM i and BACKUP is the name of the job in the system.

6.1.2 Generating the Job FolderWhen job activity is monitored, a specific folder for the job is created (see section 2.3 - Generating Job

Controls on page 8). There are two Business Views within that folder relating to start and end of a job,

as shown below.

Figure 30 – Job Business Views relating to the start and end of a job

If the job folder does not exist, it must be generated by creating and starting a monitor for the job. The

folder will be created automatically when the first event is received in SmartConsole. Delete the monitor,

if the activity for that job is not needed.

6.1.3 Activating AlarmsThere are two standard alarms defined for this purpose, in the following folder:

\Automatic Configuration\System i Package\Start/End Jobs


Alarms

Figure 31 – Two alarms are available in the Start/End Jobs folder

To manually configure the alarms:

Step 1. Export the required alarm (Ending or Starting)

Step 2. Edit the generated xml file as follows:

Replace:

• #SERVERNAME# with the name of the IBM i server

• #JOBNAME# with the name of the job to monitor

Save the xml file.

Step 3. Import the alarm to SmartConsole

Step 4. Activate the alarm.

6.1.4 Alarm EffectWhen the start or end of a job is not detected, the alarm sends a critical message to SmartConsole with

the following Agent Code:

Waiting Event

All Business Views for start/end jobs have two inclusion filters as shown below:

Figure 32 – Inclusion filters for the start/end Business Views

Note The Multiple Copy feature is not available in SmartConsole for alarms, so manual

configuration is required.


Alarms

The first filter corresponds to the start or end message coming from the IBM i. The second filter

corresponds to the possible message coming from the alarm.

6.1.5 Final EffectIf the job does not start or end during the calendar period, the status of the corresponding folder in

SmartConsole will change to RED (Critical).

6.2 Model-based AlarmsThe Operations Knowledge Module for IBM i contains some action sets that have been developed by

Tango/04 consultants in order to define model-based alarms instead of event-based alarms.

Instead of alarms being event-based, quite often alerts will need to be synced with the Business

Network tree in SmartConsole. Reproducing the tree model in the Alarms configuration would usually

involve duplicating every single filter from the tree and creating corresponding alarms with each filter.

This configuration has been developed to solve this issue and allow for the creation of model-based

alarms (i.e. alarms that would be triggered based on the changes seen in the tree), using Action Sets,

which are a means of sending automated notifications to groups.

6.2.1 Configuring NotificationsIn the Alert Triggers folder, there are three notification folders:

• NotificationTo1

• NotificationTo2

• NotificationTo3

Figure 33 – Notification folders

These three folders are already included in the model-based action set:

In the SmartConsole address book there are three defined aliases, with the exact same name as the

path of these folders as shown in Figure 34 below.

/*Manual Folder Check */

Var Services; /* List to store the Folders */

/*Edit the following list manually to control some specific folders*/

//Services := [‘1.Other Folders\\Important Folder’,’1.Other Folders\\Another Folder’];

Services := [&ROOTCONFPATH+’\’+”Alert Triggers” , &ROOTCONFPATH’\’+”Alert Triggers\\NotificationT01” , &ROOTCONFPATH’\’+”Alert Triggers\\NotificationT02” , &ROOTCONFPATH’\’+”Alert Triggers\\NotificationT03”];


Alarms

Figure 34 – Notification Aliases in the SmartConsole address book

There are two alarms that send e-mails to these addresses, using the alias as association methods.

Details of the alarm for failures are shown in Figure 35:

Figure 35 – Failure alarm details

Details of the alarm for recoveries are shown in Figure 36:

Figure 36 – Recovery alarm details


Alarms

These following e-mails will be sent for failures and recoveries:

Figure 37 – Failure alarm e-mail

Figure 38 – Recovery alarm e-mail

6.2.2 Configuration Steps

1. Define the automation required.

It is important to define which model situations should trigger an automated action, this means

specifically defining which folders, SCPs, BSCPs, or Business Views’ health changes should trigger an

alert.

2. Define the destinations.

For each item defined in the previous step, specify the e-mail address/addresses to send the alarms to.

Some examples

• Whenever an IBM i has a RED (critical) status, notify the IBM i responsible. Also notify when

it becomes GREEN (success).

• Whenever an application becomes unavailable, notify its manager. Also notify when it

becomes available again.

Example

Whenever an IBM i folder changes status to RED, or changes from RED > GREEN, notify the

platform administrators ([email protected], [email protected]).

If there is a SAP application folder change, notify the SAP administrator ([email protected]).


Alarms

3. Associate destinations with the Notification folder.

Each group of destinations need to be associated with a Notification Name.

4. Add e-mail addresses to the Address book

In the Address Book, add e-mail addresses for the correct alias.

Figure 39 – Add e-mail addresses to the appropriate aliases

5. Paste elements in destination folders

Copy-paste as link all SCPs, BSCPs, folders and Business Views in the correct NotificationToX folder.

6. Activate alarms

Check that the alarms are activated.

Figure 40 – Alarms activated in SmartConsole

6.2.3 Creating New Notification FoldersNew notification folders can be created as required, we will use the folder name Notificate SAP responsible to illustrate how to create a new folder:

Figure 41 – Notificate SAP responsible folder added to the Alert Triggers folder

To create a new notification folder:

Step 1. Create a new folder in the Alert Triggers folder and call it: Notificate SAP responsible

Step 2. Edit the Action Set called BSCP/SCP/Folder Control, adding the path of the new

folder to the SERVICES variable.

Edit the Action Set pre-actions:

Example

NotificationTo1 <-> platform administrators ([email protected], [email protected]).


Alarms

Services := [&ROOTCONFPATH+'\'+"Alert Triggers" , &ROOTCONFPATH+'\'+"Alert Triggers\\NotificationTo1" , &ROOTCONFPATH+'\'+"Alert Triggers\\NotificationTo2" , &ROOTCONFPATH+'\'+"Alert Triggers\\NotificationTo3" ,

&ROOTCONFPATH+'\'+"Alert Triggers\\Notification SAP responsible” ]

Step 3. Edit the Logical Condition filter to include the new folder path in the following alarms:

• Components failures in ALERT TRIGGERS-NotificationToX

• Components recoveries in ALERT TRIGGERS-NotificationToX

Figure 42 – Edit the Logical Condition filter

Step 4. Add a new alias entry in the address book for the new path with the proper root.

Figure 43 – Add the new folder path as an alias to the address book


Reports


Chapter 77 Reports

The Operations Knowledge Module uses the standard reports shipped with VISUAL Message Center

Reports.

The following reports are recommended for use with this module:

• For application monitoring:

− SCP overview

− SCP Listing

• For IBM i:

− Replied Messages

− Unreplied messages

For further informatoin regarding using reports please refer to the VISUAL Message Center Reports

User Guide.

Note For performance reports, we suggest using the export feature in Dashboards. Any

dashboard output can be exported in PDF or XLS format easily, simply by clicking on an

icon.

This feature also supports scheduling.

Tip It is also possible to schedule reports using macros in Reports. Please bear in mind that this

feature can only send the exported files via e-mail.



Appendix A : Toolkit - Frequent Controls

Appendix AAppendix A: Toolkit - Frequent Controls

A.1 Libraries

A.1.1 Size and Number of Objects of a Library (System i Custom Command)

Figure 44 – Right-click the monitor template and select Multiple Copy and click the Advanced button

Template name Replacement Text Observation

Toolkit #SERVERNAME# Library Size and number of objects: #LIBRARYNAME#

#SERVERNAME##LIBRARY#(by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the library name in the command within the data source



Figure 45 – Replace the server name and library name

Figure 46 – iSeries Settings in the Datasource Configuration



Figure 47 – Size and number of objects of a library monitor in ThinkServer

A.1.2 Size of a Library (Storage Management Agentless)

Figure 48 – Multiple copy the monitor template

Template name Replacement Observation

Toolkit #SERVERNAME# Sys-tem i Library Size Monitor #LIBRARY#

#SERVERNAME##LIBRARY#(by Multiple Copy)

After the multiple copy, replace manually the ODBC data source name, user and pass-word.



Figure 49 – Replace the server name and library name

Figure 50 – Size of a library monitor in ThinkServer

A.1.3 Size of a Group of Libraries (Storage Management Agentless)


Toolkit #SERVERNAME# Sys-tem i Library Group Size Monitor: #LIBLIST#

#SERVERNAME##LIBLIST#(by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the ODBC data source name, user and password.




Figure 52 – Replace the server name and library list name

Figure 53 – Size of a group of libraries monitor in ThinkServer



A.2 Objects

A.2.1 Existence Check (System i Custom Command)

In this case, a custom program is run on the IBM i.

The standard command provided by the Operating System is the CHKOBJ. This command runs

successfully if the object exists. If it does not, it returns an error. This is a problem, when running a

command from ODBC, because in the case of ThinkServer the monitor goes into an error status.

This means a custom program is required.

The control language (CL) source of that program is shown in Figure 54 below.

Figure 54 – The custom program CL source

The monitor executes some commands as shown below:


Toolkit #SERVERNAME# Object existence: #LIBRARY#/#OBJECT# #TYPE#

#SERVERNAME# #LIBRARY##OBJECT##TYPE#(by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the library and object name and type in the command within the data source



Figure 55 – System i Settings in the Datasource Configuration

To generate a monitor, Multiple Copy the monitor template:




Figure 57 – Replace the required text

Figure 58 – Existence check monitor in ThinkServer

A.2.2 Object Attribute (System i Custom Command)

This case does not apply when the object does not exist. In such cases the previous example should be

used.

Any attribute retrieved by the DSPOBJD command could be monitored using this monitor.


Toolkit #SERVERNAME# Object attribute-size: #LIBRARY#/#OBJECT# #TYPE#

#SERVERNAME##LIBRARY##OBJECT##TYPE#(by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the library and object name and type in the command within the data source





Figure 61 – Object attribute monitor in ThinkServer



A.3 Files

A.3.1 Number of Records in File/Deleted Records (System i Custom Command)

Any other attribute that retrieves the DSPFD command could be monitored by this monitor.




Toolkit #SERVERNAME# File number of records: #LIBRARY#/#OBJECT#

#SERVERNAME##LIBRARY##OBJECT#(by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the library and object name in the command within the data source



Figure 64 – Number of records in file/deleted records monitor in ThinkServer

A.3.2 Data in Spooled File

Many commands in the IBM i do not have file output, only screen or print. This monitor facilitates the

retrieval of data from print output.

Run the following sequence of commands in the WRKDSKSTS command to retrieve the information:

After running these commands, you need to run a SELECT statement filtering the desired information.

The output file has only one column 132 characters in length, and has the same name as the file

containing the retrieved information (QTEMP/WRKDSK001).

This example corresponds to the WRKDSKSTS command:


Toolkit #SERVERNAME# - #COMMAND# output in spooled file - System i Monitor

#SERVERNAME##COMMAND# (by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the command within the data source, and apply the SELECT statement based on the output for-mat.

1. OVRPRTF FILE(*PRTF) SPLFOWN(*JOB) OVRSCOPE(*JOB) &&&

2. WRKDSKSTS OUTPUT(*PRINT) &&&

3. CRTPF FILE(QTEMP/WRKDSK001) RCDLEN(132) &&&

4. CPYSPLF FILE(QPWCDSKS) TOFILE(QTEMP/WRKDSK001) SPLNBR(*LAST) &&&

5. DLTSPLF FILE(QPWCDSKS) SPLNBR(*LAST)

SELECT substr(wrkdsk001 , 1 , 5) , substr(wrkdsk001 , 22, 6) FROM qtemp.wrkdsk001 WHERE (wrkdsk001 like ' 1%') or (wrkdsk001 like ' 2%')




Figure 66 – Data in Spooled File monitor in ThinkServer



Figure 67 – The *PRINT output

A.4 Data Areas

A.4.1 Data Area Content

This particular control deals with the problem of commands that do not have OUTFILE output. The

command is DSPDTAATA.

The monitor runs the following sequence of commands:

And the SQL statement to read the whole content of the data area is:


Toolkit #SERVERNAME# Data-area Content #LIBRARY#/ #DTAARA#

#SERVERNAME##DTAARA##LIBRARY# (by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the library and data area name within the data source, and apply the SELECT statement if you need specific positions within the data area.

1. OVRPRTF FILE(*PRTF) SPLFOWN(*JOB) OVRSCOPE(*JOB) &&&

2. DSPDTAARA ATERUEL/TEST *PRINT &&&

3. CRTPF FILE(QTEMP/ara) RCDLEN(132) &&&

4. CPYSPLF FILE(QPDSPDTA) TOFILE(QTEMP/ara) SPLNBR(*LAST) &&&

5. DLTSPLF FILE(QPDSPDTA) SPLNBR(*LAST)

SELECT substr(ara, 4,3) as pos, substr(ara, 17,52) FROM qtemp.ara WHERE substr(ara, 6 , 1)='0' order by pos




Figure 69 – Data Area Content monitor in ThinkServer

Figure 70 – The *PRINT output



A.5 Integration with iSeries Performance Manager (Visual Control for Jobs)Customers that have VISUAL Message Center iSeries Performance Manager can receive events in

SmartConsole in real time, related to the activity of the product: jobs that are changed by iSeries

Performance Manager.

To achieve this, an auxiliary table must be created in the IBM i, using the following SQL statements:


CREATE TABLE JOBCTL/VCJ_INTEGR

(DATE_PRV CHAR (6 ) NOT NULL WITH DEFAULT,

TIME_PRV CHAR (6 ) NOT NULL WITH DEFAULT,

DATE_AFT CHAR (6) NOT NULL WITH DEFAULT,

TIME_AFT CHAR (6 ) NOT NULL WITH DEFAULT)

INSERT INTO JOBCTL/VCJ_INTEGR VALUES('XXXXXX', '000000', 'XXXXXX', '000000') replacing XXXXXX by the current date in YYMMDD format


Toolkit #SERVERNAME# Inte-gration VisualControlfor-Jobs - Changed Jobs

#SERVERNAME# (by Multiple Copy)

Multiple copy the moni-tor template and manu-ally replace the data source name, user and password.



Figure 72 – Integration with iSeries Performance Manager in ThinkServer


Appendix B : Filters

Appendix BAppendix B: Filters

This Knowledge Module uses events coming from the HST Agent, and it is necessary to evaluate if

inclusion filters are needed for the agent. In some installations, this agent will conusme a lot of CPU

resources, and therefore starting it without filters could be problematic.

If there are too many events retrieved by the HST Agent create and activate the following inclusion

filters. Then only the events required by this Module will be collected. The filters indicated below are the

inclusion filters needed by this Module.

Filter Name Expression

Aix Server(&agent_code='HST') and ((&MSG_ID in {'CPI8010','CPI8111'}) or (&MSG_ID like 'CPI810%' ))

Battery

(&agent_code='HST') and (&MSG_ID in {'CPP9522','CPP951B','CPP9617','CPI0964','CPP0965', 'CPP0966'

Communications(&agent_code='HST') and (&MSG_ID in {'CPI7E9B','CPI7E98'})

Disks

(&agent_code='HST') and ((&MSG_ID in {'CPF0907','CPI0920','CPI0970','CPI0992','CPI0996', 'CPI0997','CPI0998','CPI0999','CPI1136','CPI1139', 'CPI9490','CPI94A0','CPP29B0','CPP29B8','CPP29BA', 'CPI1138','CPP1604','CPI0945','CPI0946','CPI0947', 'CPI0948','CPI0949','CPI0953','CPF096B','CPF096C', 'CPF096D','CPF096E'}) OR (&MSG_ID LIKE 'CPI095%') OR (&MSG_ID LIKE 'CPI116%'))

Hardware

(&agent_code='HST') and ((&MSG_ID in {'CPP8982','CPP8983','CPP8984','CPP8985','CPP8986', 'CPP8987','CPP8988','CPP29B9','CPPC00E'}) OR (&MSG_ID LIKE 'CPI800%') OR (&MSG_ID LIKE 'CPI801%') OR (&MSG_ID LIKE 'CPI802%') OR (&MSG_ID LIKE 'CPI803%') OR (&MSG_ID LIKE 'CPI804%') OR (&MSG_ID LIKE 'CPPC03%'))


Appendix B : Filters

IPL Battery

(&agent_code='HST') and ((&MSG_ID in {'CPI1138','CPP29BA','CPI0999','CPI1139','CPP9617', 'CPP9618'}) OR (&MSG_ID LIKE 'CPP95%') OR (&MSG_ID LIKE 'CPI096%'))

Tapes

(&agent_code='HST') and ((&MSG_ID in {'CPP630A','CPP630B','CPP630C','CPP630D','CPP630E', 'CPP630F','CPP6307','CPP6308','CPP6309','CPP6310', 'CPP6311','CPP6312','CPP6306'}) )

Tech Service

(&agent_code='HST') and ((&MSG_ID in {'CPPEA01','CPPEA02','CPPEA03','CPPEA04','CPPEA05', 'CPPEA06','CPPEA10','CPPEA11','CPPEA12','CPPEA13', 'CPPEA14','CPP1604','CPP7701','CPP7702','CPPEA26', 'CPPEA28','CPPEA30','CPPEA31','CPPEA38','CPPEA39', 'CPPEA40'}))

Thresholds(&agent_code='HST') and ((&MSG_ID in {'CPI0999'}))

UPS

(&agent_code='HST') and ((&MSG_ID in {'CPP951B','CPP9522','CPP955E','CPP9575','CPP9576', 'CPP9589','CPP9617','CPP9618'}) OR (&mSG_ID LIKE 'CPI096%') )

Windows Server

(&agent_code='HST') and ((&MSG_ID in {'CPI8120','CPI8121','CPI8122','CPI8123','CPI8124', 'CPI8125'}) OR (&msg_id LIKE 'CPI813%'))

Custom Messages (&agent_code='HST') and (&msg_id like 'VMC%')

Filter Name Expression

Tip In order to clearly identify the filters on the IBM i side and to ensure they are not modified in

any way, we recommend prefixing the filter name with:

INCLUDE Knowledge Module - DO NOT CHANGE -

So the complete name for the Windows Server fileter would be:

INCLUDE Knowledge Module - DO NOT CHANGE - Windows Server


Appendix C : Contacting Tango/04

Appendix CAppendix C: Contacting Tango/04

North America

Tango/04 North America

PO BOX 3301

NH 03458 Peterborough USA

Phone: 1-800-304-6872 / 603-924-7391

Fax: 858-428-2864

[email protected]

www.tango04.com

EMEA

Tango/04 Computing Group S.L.

Avda. Meridiana 358, 5 A-B

08027 Barcelona Spain

Phone: +34 93 274 0051

Fax: +34 93 345 1329

[email protected]

www.tango04.com

Italy

Tango/04 Italy

Viale Garibaldi 51/53

13100 Vercelli Italy

Phone: +39 0161 56922

Fax: +39 0161 259277

[email protected]

www.tango04.it

Sales Office in France

Tango/04 France

La Grande Arche

Paroi Nord 15ème étage

92044 Paris La Défense France

Phone: +33 01 40 90 34 49

Fax: +33 01 40 90 31 01

[email protected]

www.tango04.fr

Sales Office in Switzerland

Tango/04 Switzerland

18, Avenue Louis Casaï

CH-1209 Genève

Switzerland

Phone: +41 (0)22 747 7866

Fax: +41 (0)22 747 7999

[email protected]

www.tango04.fr

Latin American Headquarters

Barcelona/04 Computing Group SRL (Argentina)

Avda. Federico Lacroze 2252, Piso 6

1426 Buenos Aires Capital Federal

Argentina

Phone: +54 11 4774-0112

Fax: +54 11 4773-9163

[email protected]

www.barcelona04.com


Mailto:[email protected]

www.tango04.com


www.tango04.com


www.tango04.it


www.tango04.fr


www.tango04.fr


www.barcelona04.com

Sales Office in Peru

Barcelona/04 PERÚ

Centro Empresarial Real

Av. Víctor A. Belaúnde 147, Vía Principal 140 Edificio Real Seis, Piso 6

L 27 Lima

Perú

Phone: +51 1 211-2690

Fax: +51 1 211-2526

[email protected]

www.barcelona04.com

Sales Office in Chile

Barcelona/04 Chile

Nueva de Lyon 096 Oficina 702,

Providencia

Santiago

Chile

Phone: +56 2 234-0898

Fax: +56 2 2340865

[email protected]

www.barcelona04.com



www.barcelona04.com


www.barcelona04.com

About Tango/04 Computing Group

Tango/04 Computing Group is one of the leading developers of systems management and automation

software. Tango/04 software helps companies maintain the operating health of all their business

processes, improve service levels, increase productivity, and reduce costs through intelligent

management of their IT infrastructure.

Founded in 1991 in Barcelona, Spain, Tango/04 is an IBM Business Partner and a key member of IBM's

Autonomic Computing initiative. Tango/04 has more than a thousand customers who are served by over

35 authorized Business Partners around the world.

Alliances

Awards

Partnerships IBM Business Partner

IBM Autonomic Computing Business Partner

IBM PartnerWorld for Developers Advanced Membership

IBM ISV Advantage Agreement

IBM Early code release

IBM Direct Technical Liaison

Microsoft Developer Network

Microsoft Early Code Release


Legal Notice

The information in this document was created using certain specific equipment and environments, and it is limited in

application to those specific hardware and software products and version and releases levels.

Any references in this document regarding Tango/04 Computing Group products, software or services do not mean

that Tango/04 Computing Group intends to make these available in all countries in which Tango/04 Computing Group

operates. Any reference to a Tango/04 Computing Group product, software, or service may be used. Any functionally

equivalent product that does not infringe any of Tango/04 Computing Group's intellectual property rights may be used

instead of the Tango/04 Computing Group product, software or service

Tango/04 Computing Group may have patents or pending patent applications covering subject matter in this

document. The furnishing of this document does not give you any license to these patents.

The information contained in this document has not been submitted to any formal Tango/04 Computing Group test

and is distributed AS IS. The use of this information or the implementation of any of these techniques is a customer

responsibility, and depends on the customer's ability to evaluate and integrate them into the customer's operational

environment. Despite the fact that Tango/04 Computing Group could have reviewed each item for accurateness in a

specific situation, there is no guarantee that the same or similar results will be obtained somewhere else. Customers

attempting to adapt these techniques to their own environments do so at their own risk. Tango/04 Computing Group

shall not be liable for any damages arising out of your use of the techniques depicted on this document, even if they

have been advised of the possibility of such damages. This document could contain technical inaccuracies or

typographical errors.

Any pointers in this publication to external web sites are provided for your convenience only and do not, in any

manner, serve as an endorsement of these web sites.

The following terms are trademarks of the International Business Machines Corporation in the United States and/or

other countries: iSeries, iSeriese, iSeries, i5, DB2, e (logo)®Server IBM ®, Operating System/400, OS/400, i5/OS.

Microsoft, SQL Server, Windows, Windows NT, Windows XP and the Windows logo are trademarks of Microsoft

Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are

trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. UNIX is a

registered trademark in the United States and other countries licensed exclusively through The Open Group. Oracle

is a registered trade mark of Oracle Corporation.

Other company, product, and service names may be trademarks or service marks of other companies.


Documents

Operations Knowledge Module for IBM i