Configuration and Customization Guidepublib.boulder.ibm.com/tividd/td/ITOXfIMS/GC32-9302-00/... ·...

Configuration and Customization GuideOMEGAMON XE® for IMS

Version 100

OMEGAMON XE for IMSplexVersion 220

GC32-9302-00

May 2003

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 OMEGAMON XE for IMS and IMSplex Configuration and Customization Guide

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER, AF/REMOTE, Availability Command Center, Candle, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleNet eBusiness Platform, CandleNet Portal, Candle Technologies, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CandleNet Command Center, CT, CT/Data Server, CT/DS, DELTAMON, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness Assurance, eBusiness Institute, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, PQEdit, Solutions for Networked Applications, Solutions for Networked Businesses, and Transplex.Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle CIRCUIT, Candle eDelivery, CandleLight, CandleNet, CandleNet 2000, CandleNet eBP, CandleNet eBP Access, CandleNet eBP Administrator, CandleNet eBP Broker Access, CandleNet eBP Configuration, CandleNet eBP Connector, CandleNet eBP File Transfer, CandleNet eBP Host Connect, CandleNet eBP Object Access, CandleNet eBP Object Browser, CandleNet eBP Secure Access, CandleNet eBP Service Directory, CandleNet eBP Universal Connector, CandleNet eBP Workflow Access, CandleNet eBusiness Assurance, CandleNet eBusiness Exchange, CandleNet eBusiness Platform Administrator, CandleNet eBusiness Platform Connector, CandleNet eBusiness Platform Connectors, CandleNet eBusiness Platform Powered by Roma Technology, CandleNet eBusiness Platform Service Directory, CCC, CCP, CEBA, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW, Command & Control, Connect-Notes, Connect-Two, CSA ANALYZER, CT/ALS, CT/Application Logic Services, CT/DCS, CT/Distributed Computing Services, CT/Engine, CT/Implementation Services, CT/IX, CT/Workbench, CT/Workstation Server, CT/WS, !DB Logo, !DB/DASD, !DB/EXPLAIN, !DB/MIGRATOR, !DB/QUICKCHANGE, !DB/QUICKCOMPARE, !DB/SMU, !DB/Tools, !DB/WORKBENCH, Design Network, DEXAN, e2e, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBusiness Institute, eBX, End-to-End, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, EPILOG, ER+, ERPNet, ESRA, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NetGlue, NetGlue Extra, NetMirror, NetScheduler, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ, PQConfiguration, PQScope, Response Time Network, Roma, Roma Application Manager, Roma Broker, Roma BSP, Roma Connector, Roma Developer, Roma FS/A, Roma FS/Access, RomaNet, Roma Network, Roma Object Access, Roma Secure, Roma WF/Access, Roma Workflow Access, RTA, RTN, SentinelManager, Somerset, Somerset Systems, Status Monitor, The Millennium Alliance, The Millennium Alliance logo, The Millennium Management Network Alliance, TMA2000, Tracer, Unified Directory Services, Volcano and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademark of SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. HP-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems, Inc. All other company and product names used herein are trademarks or registered trademarks of their respective companies.

Copyright © May 2003, Candle Corporation, a California corporation. All rights reserved. International rights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Tests in Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Using the XCF Coupling Facility, Patent No. 5,754,856; Intelligent Remote Agent for Computer Performance Monitoring, Patent No. 5,781,703; Data Server with Event Driven Sampling, Patent No. 5,809,238; Threaded Environment for Computer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility, Patent No. 5,848,234; End-to-End Response Time Measurement for Computer Programs, Patent No. 5,991,705; Communications on a Network, Patent Pending; Improved Message Queuing Based Network Computing Architecture, Patent Pending; User Interface for System Management Applications, Patent Pending.

NOTICE: This documentation is provided with RESTRICTED RIGHTS. Use, duplication, or disclosure by the Government is subject to restrictions set forth in the applicable license agreement and/or the applicable government rights clause.This documentation contains confidential, proprietary information of Candle Corporation that is licensed for your internal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents 3

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 11Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . 15

Chapter 1. Start Here to Configure Products and Maintenance . . . . . . . . . 17Using the Checklists and Topics in this Chapter . . . . . . . . . . . . . . . . . 18Checklist: Prerequisites for Configuring Products . . . . . . . . . . . . . . . . 20Checklist: Starting CICAT and Accessing the Menu for Configuration 21Checklist: Configuring OMEGAMON XE for IMS Using CICAT . . . . . 22Checklist: Configuring OMEGAMON XE for IMSplex Using CICAT . . 25Checklist: Configuring Your Product Outside of CICAT . . . . . . . . . . . 28Checklist: Customizing Your Product Outside of CICAT. . . . . . . . . . . 30Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 31Using Advanced Features in CICAT. . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 2. Overview of Processes, Methods, and CICAT Modes . . . . . . . . 33Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 34Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Processes for Installing, Configuring, and Maintaining Products. . . . . 36Background about CICAT Modes: Interactive and Batch . . . . . . . . . . 41

Chapter 3. Plan Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 44Overview of the Candle Products and Components . . . . . . . . . . . . . 45Details about the Candle Products and Components . . . . . . . . . . . . . 48Requirement for OMEGAMON XE for IMSplex . . . . . . . . . . . . . . . . . 50Determining the Components to Install and Configure . . . . . . . . . . . 51

Contents


Chapter 4. Start CICAT and Access the Configuration Menu . . . . . . . . . . . 55Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 56Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Accessing the Menu for Configuring the Product . . . . . . . . . . . . . . . . 58Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 5. Complete the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 62Copying the Procedures for the Started Tasks . . . . . . . . . . . . . . . . . . 63Copying the VTAM Definitions and Varying the VTAM Node Active . 64APF-authorizing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . 66Verifying the Configuration: Different Address Space. . . . . . . . . . . . . 67Verifying the Configuration: CMS on a Different Platform . . . . . . . . . 68

Chapter 6. Complete the Customization. . . . . . . . . . . . . . . . . . . . . . . . . . . 69Enabling the Zoom Feature to Access an OMEGAMON II Session. . . 70

Chapter 7. Manage and Update the Configuration . . . . . . . . . . . . . . . . . . . 71Updating and Changing the Configuration . . . . . . . . . . . . . . . . . . . . 72

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Tables 5

Table 1. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 2. Advanced Features Available in CICAT . . . . . . . . . . . . . . . . . . . . . . . 32Table 3. Installing Products and Maintenance: A Comparison . . . . . . . . . . . . . 36Table 4. Installing and Configuring: A Comparison . . . . . . . . . . . . . . . . . . . . . 37Table 5. Example Tasks for Installing, Maintaining, and Configuring . . . . . . . . 38Table 6. Locating Information for Installing and Configuring. . . . . . . . . . . . . . 39Table 7. CICAT Modes: Interactive and Batch. . . . . . . . . . . . . . . . . . . . . . . . . 41Table 8. Overview of the Products and Components . . . . . . . . . . . . . . . . . . . 45Table 9. Details about the Relationships and CMS Types . . . . . . . . . . . . . . . . 48

Table 10. Determining the Products and Components You Will Need . . . . . . . . 52Table 11. Determining the Products and Components to Configure . . . . . . . . . 53Table 12. Locate information about configuring the product or component . . . 54

Tables


Preface 7

Preface

IntroductionThis manual covers the configuration and customization for both of the following products:

� OMEGAMON XE for IMS, Version 100

� OMEGAMON XE for IMSplex, Version 220

This manual contains:

� a set of checklists you can use to complete the steps required to configure and customize the products

� an overview of the process for installing and configuring all Candle products and components

� the planning information you should review before you configure the products and components

� information about using the Candle Installation and Configuration Assistance Tool (CICAT) to configure the products and components

� the step-by-step instructions to follow to complete the manual configuration outside of CICAT and manual customization outside of CICAT (if any)

� the step-by-step instructions to follow to update or change the configuration

P

About This Book


About This Book

Who should read this guideThis guide is intended for users of the OMEGAMON XE for IMS and IMSplex products, including product administrators and system programmers.

Documentation set information

How to use this guideThis guide is designed to help new and experienced customers.

If you are a new customer, you can use:

� the chapters in the order they are included in this guide (The information and tasks are listed in the order they are needed or performed.)

� the checklists in Chapter 1 to verify that you have completed the steps required to configure the product and locate specific information or procedures (if needed)

If you are an experienced customer, you can use the checklists in Chapter 1 to verify that you have completed the steps required to configure and customize the product and locate specific information or procedures (if needed).

Product You Are Configuring

Product-specific Documentation provided

OMEGAMON XE for IMS � User’s Guide (I354-6773)� Configuration and Customization Guide

(I351-6762)

OMEGAMON XE for IMSplex � User’s Guide (IP54-6772)� Configuration and Customization Guide

(I351-6762)

Preface 9

About This Book

Determining the chapters to use in this guide The table shows the type of information covered in this guide and the chapters that contain the type of information.

Chapter to Use

Type of Information You Need 1 2 3 4 5 6 7

Checklists that you can use to verify that you have completed all the steps in the broad process for configuring products and maintenance (Recommended for all new and experienced customers.)

!

Background about CICAT !

Definitions for Candle terminology !

Overview of the entire process for installing and configuring Candle products and maintenance

!

Prerequisites you must complete before configuring the product and following the procedures in this guide

!

Procedures to follow to start CICAT and access the menu to configure the product

!

Procedures to follow outside of CICAT to configure the product and to verify that the configuration is complete by starting the product and components

!

Procedures to follow outside of CICAT to customize the product for your site (In most cases, these steps are optional.)

!

Procedures to follow to update or change the configuration !

About This Book


Where to look for more informationFor more information related to this product and other related products, please see the:

� technical documentation CD-ROM that came with your product

� technical documentation information available on the Candle Web site at www.candle.com

� online help provided with this and the other related products.

Ordering additional documentationTo order additional product manuals, contact your Candle Customer Support representative.

We would like to hear from youCandle welcomes your comments and suggestions for changes or additions to the documentation set. A user comment form, located at the back of each manual, provides simple instructions for communicating with the Candle Information Development department.

You can also send email to [email protected]. Please include “OMEGAMON XE for IMS and IMSplex Configuration and Customization Guide“ in the subject line.

http://www.candle.com

Preface 11

Adobe Portable Document Format


Printing this bookCandle supplies documentation in the Adobe Portable Document Format (PDF). The Adobe Acrobat Reader will print PDF documents with the fonts, formatting, and graphics in the original document. To print a Candle document, do the following:

1. Specify the print options for your system. From the Acrobat Reader Menu bar, select File > Page Setup… and make your selections. A setting of 300 dpi is highly recommended as is duplex printing if your printer supports this option.

2. To start printing, select File > Print... on the Acrobat Reader Menu bar.

3. On the Print pop-up, select one of the Print Range options for� All� Current page� Pages from: [ ] to: [ ]

4. (Optional). Select the Shrink to Fit option if you need to fit oversize pages to the paper size currently loaded on your printer.

Printing problems?The print quality of your output is ultimately determined by your printer. Sometimes printing problems can occur. If you experience printing problems, potential areas to check are:� settings for your printer and printer driver. (The dpi settings for both your

driver and printer should be the same. A setting of 300 dpi is recommended.)

� the printer driver you are using. (You may need a different printer driver or the Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

� the halftone/graphics color adjustment for printing color on black and white printers (check the printer properties under Start > Settings > Printer). For more information, see the online help for the Acrobat Reader.

� the amount of available memory in your printer. (Insufficient memory can cause a document or graphics to fail to print.)

For additional information on printing problems, refer to the documentation for your printer or contact your printer manufacturer.



Contacting AdobeIf additional information is needed about Adobe Acrobat Reader or printing problems, see the Readme.pdf file that ships with Adobe Acrobat Reader or contact Adobe at www.adobe.com.

Adding annotations to PDF filesIf you have purchased the Adobe Acrobat application, you can add annotations to Candle documentation in .PDF format. See the Adobe product for instructions on using the Acrobat annotations tool and its features.

http://www.adobe.com

Preface 13

Documentation Conventions


IntroductionCandle documentation adheres to accepted typographical conventions for command syntax. Conventions specific to Candle documentation are discussed in the following sections.

Panels and figuresThe panels and figures in this document are representations. Actual product panels may differ.

Required blanksThe slashed-b (!) character in examples represents a required blank. The following example illustrates the location of two required blanks.

!!!!eBA*ServiceMonitor!!!!0990221161551000

Revision barsRevision bars (|) may appear in the left margin to identify new or updated material.

Variables and literalsIn examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

In the above example, you type LOGON APPLID followed by an application identifier (represented by cccccccc) within parentheses.

Note: In ordinary text, variable names appear in italics.



SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

| The “or” symbol is used to denote a choice. Either the argument on the left or the argument on the right may be used. Example:

YES | NOIn this example, YES or NO may be specified.

[ ] Denotes optional arguments. Those arguments not enclosed in square brackets are required. Example:

APPLDEST DEST [ALTDEST]In this example, DEST is a required argument and ALTDEST is optional.

{ } Some documents use braces to denote required arguments, or to group arguments for clarity. Example:

COMPARE {workload} -REPORT={SUMMARY | HISTOGRAM}

The workload variable is required. The REPORT keyword must be specified with a value of SUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile - [COMPRESS={YES | NO}]In this example, the COMPRESS keyword is optional. If specified, the only valid values are YES or NO. If omitted, the default is YES.

Preface 15

Candle Customer Service and Satisfaction


BackgroundTo assist you in making effective use of our products, Candle offers a variety of easy-to-use online support resources.

The Candle Web site provides direct links to a variety of support tools that include a range of services. For example, you can find information about training, maintenance plans, consulting and services, and other useful support resources. Refer to the Candle Web site at www.candle.com for detailed customer service and support information.

Candle Customer Service and Satisfaction contactsYou will find the most current information about how to contact Candle Customer Service and Satisfaction by telephone or e-mail on the Candle Web site. Go to the www.candle.com support section and find the link to Support Contacts, to locate your regional support center.





Start Here to Configure Products and Maintenance 17

Start Here to ConfigureProducts and Maintenance

IntroductionThis chapter contains a checklist or topic for each of the steps in the process for configuring products and maintenance, that you can use to:

� guide you through the steps in the process for configuring and customizing products and components

� verify that you have used all of the options in CICAT required for your specific situation

� verify that you have completed all the required steps outside of CICAT to configure and customize the products and components

� locate detailed information when you need background information or step-by-step instructions for a specific task

Chapter contentsUsing the Checklists and Topics in this Chapter. . . . . . . . . . . . . . . . . . . . . 18Checklist: Prerequisites for Configuring Products . . . . . . . . . . . . . . . . . . . 20Checklist: Starting CICAT and Accessing the Menu for Configuration . . . . 21Checklist: Configuring OMEGAMON XE for IMS Using CICAT. . . . . . . . . 22Checklist: Configuring OMEGAMON XE for IMSplex Using CICAT . . . . . 25Checklist: Configuring Your Product Outside of CICAT. . . . . . . . . . . . . . . 28Checklist: Customizing Your Product Outside of CICAT . . . . . . . . . . . . . . 30Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Using Advanced Features in CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

1

Using the Checklists and Topics in this Chapter



Determine the checklists and topics to use This chapter contains a checklist or topic for each of the steps in the process for installing, maintaining, and configuring products. In most cases, there is a checklist you can use to verify that you have completed all the tasks.

The following table shows the checklist or topic you should use for your tasks.

Task Checklists and Topics to Use in this Chapter Page #

Complete the configuration of the product or maintenance

! Checklist: Prerequisites for Configuring Products page20

! Checklist: Starting CICAT and Accessing the Menu for Configuration

page21

! Checklist: Configuring OMEGAMON XE for IMS Using CICAT

page22

! Checklist: Configuring Your Product Outside of CICAT page28

! Checklist: Customizing Your Product Outside of CICAT page30

! Using Advanced Features in CICAT page32

Update or change the configuration for the product

! Checklist: Starting CICAT and Accessing the Menu for Configuration

page31

! Checklist: Updating the Configuration page31

! Using Advanced Features in CICAT page32



How to use the checklists The tasks in the checklists are listed in the order they are performed. You use:

� the first column with the box to track the tasks you complete

� the next column(s) to determine the task

� the last column to locate background information or step-by-step instructions in the resources provided with the product (such as the online help and this guide)

If you are not familiar with Candle, CICAT, or the processIf you are not familiar with Candle terminology, CICAT, or the process of installing, maintaining, and configuring products, see Chapter 2 in this guide.

Checklist: Prerequisites for Configuring Products


Checklist: Prerequisites for Configuring Products

Who should use this checklistUse this checklist if you are configuring and customizing:

� OMEGAMON XE for IMS

� OMEGAMON XE for IMSplex

Checklist: Product configuration prerequisitesThe checklist contains the prerequisite actions you must have completed before you can begin to configure the product.

✓ Prerequisite Location of Information

! If you have not already done so, verify for the product you want to configure that:

! you have the required software

! you have the required DASD space

! the product versions can exist in the same CSI

Installation & Configuration of Candle Products on OS/390 and z/OS

! You must have installed the product and components using CICAT.

� Installation & Configuration of Candle Products on OS/390 and z/OS

� the online help in CICAT ! You must have created a runtime environment (RTE)

using CICAT.

! You must have completed the configuration for a Candle Management Server® (CMS).

� Candle Mangement Server Configuration and Customization Guide

� the online help in CICAT

! If this is the first time you have used Candle products or you are not familiar with the terminology, CICAT, or the process, review an overview.

Chapter 2 in this guide

! If this is the first time you have used Candle products or you do not know the configuration you want, review the background, planning information, and migration information (if any).



Checklist: Starting CICAT and Accessing the Menu for Configuration

Checklist: Starting CICAT and Accessing the Menu for Configuration




Checklist: Start CICAT and access the configuation menuThe checklist contains the steps you perform to start CICAT and access the configuration menu.

✓ TaskLocation of Information

! Using TSO, start CICAT by executing shilev.INSTLIB. Chapter 4 in this guide

! On the CICAT Main Menu, select Configure products and complete the following options on the menu.

! If this is the first time you have used CICAT V300 to configure a Candle product, use Set up configuration environment to specify values that CICAT will use to build the JCL that allocates the runtime data sets for all the products you are configuring.

! Use Select product to configure to display a list of the products available and to select the product you want to configure using the S (Select product) select.

! On the Runtime Environments (RTEs) panel, either:

– if you want to configure an existing RTE, type C (Configure) in the Action field for the RTE

– if you want to create a new RTE, type A (Add) in the Action field and specify the values for the new RTE

! If you are configuring a product that communicates with the CMS, on the Product Configuration Selection Menu enter the selection number of the product or component.


Checklist: Configuring OMEGAMON XE for IMS Using CICAT



Who should use this checklistUse this checklist if you are configuring OMEGAMON XE for IMS.

Checklist: Configure OMEGAMON XE for IMS using CICATThe following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE.

✓ Location in CICAT

Configuration Step to Perform in CICAT

Location of Information

! Configure OMEGAMON XE for IMS menu

Use Register with local CMS to enable the OMEGAMON XE for IMS product, by registering it to the local CMS.

Online help in CICAT


Use Define IMS subsystems to CMS to define the IMS subsystems being monitored by OMEGAMON XE for IMS to the CMS.

Note: Autodiscovery is enabled by default. The “*” subsystem autodiscovery seed data is always the first entry in the list of IMS subsystems.

! If you want to add a new IMS subsystem, type A (Add) in the Action field and specify the values for the new IMS subsystem.

! After defining all your IMS subsystems, in the Action field you can type:

– U (Update) to select an IMS subsystem for processing

– R (Remove monitoring) to disable data collection for an IMS subsystem

– D ((Delete) to delete an IMS subsystem





If you are defining an agent to run in an agent address space, use Specify Agent address space parameters to provide information required to create the address space and communicate with the CMS.

! If this is a new agent to be configured in the agent address space:

– Specify the configuration values for the agent address space.

– Specify advanced configuration values, by using the Advanced key (F5).

– Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent address space to support.

! If this is the second or third agent to be configured in the agent address space, on the Agent Address Space Selection panel:

– To share an existing agent address space, type S (Select) next to the address space name and then use Create runtime members to generate the job that updates the runtime members for the agent address space.

– To add a new agent address space, type A (Add) in the Action field and use the steps for configuring a new agent in the agent address space.

Note: If the agent is already configured to share an agent address space, a message showing the agent address space owner appears in the upper right corner of the Configure panel.



If you are defining an agent to run in an agent address space, use Create runtime members to generate the job that creates the runtime members for the agent address space.







Determine what to do nextSee “Checklist: Configuring Your Product Outside of CICAT” on page 28.


If you are defining an agent to run in the CMS address space, use Install Agent into local CMS to generate the job that installs the agent into the specified CMS.



Use Complete the configuration to display a set of instructions for completing the configuration outside of CICAT.

(The instructions are also covered in this guide.)


and

“Complete the Configuration” on page 61

! Runtime Environments (RTEs) panel

Use L (Load libs after SMP/E) to load the target libraries to the runtime libraries for the RTE.






Checklist: Configuring OMEGAMON XE for IMSplex Using CICAT


Who should use this checklistUse this checklist if you are configuring OMEGAMON XE for IMSplex.

Checklist: Configure OMEGAMON XE for IMSplex using CICATThe following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE.




! Configure OMEGAMON XE for IMSplex menu

Use Register with local CMS to enable the OMEGAMON XE for IMSplex product, by registering it to the local CMS.



Use Define IMS subsystems to CMS to define the IMS subsystems being monitored by OMEGAMON XE for IMSplex to the CMS.

Note: Autodiscovery is enabled by default. The “*” subsystem autodiscovery seed data is always the first entry in the list of IMS subsystems.

! If you are running IMS 6.1, type the 4-character CQS subsystem name you have set up for IMSplex. (IMS 6.1 does not allow you to use the same one defined for IMS.)

Note: CQS subsystem name is not required for IMS 7.1 or higher.

! If you want to add a new IMS subsystem, type A (Add) in the Action field and specify the values for the new IMS subsystem.

! After defining all your IMS subsystems, in the Action field you can type:

– U (Update) to select an IMS subsystem for processing

– R (Remove monitoring) to disable data collection for an IMS subsystem

– D ((Delete) to delete an IMS subsystem





Use Define IRLM subsystems to CMS to define the IRLM subsystems being monitored by OMEGAMON XE for IMSplex to the CMS.

Note: Autodiscovery is enabled by default. The “*” subsystem autodiscovery seed data is always the first entry in the list of IRLM subsystems.

! If you want to add a new IRLM subsystem, type A (Add) in the Action field and specify the values for the new IRLM subsystem.

! After defining all your IRLM subsystems, in the Action field you can type:

– U (Update) to select an IRLM subsystem for processing

– R (Remove monitoring) to disable data collection for an IRLM subsystem



If you are defining an agent to run in the CMS address space, use Install Agent into local CMS to generate the job that installs the agent into the specified CMS.



If you are defining an agent to run in an agent address space, use Specify Agent address space parameters to provide information required to create the address space and communicate with the CMS.

! If this is a new agent to be configured in the agent address space:

– Specify the configuration values for the agent address space.

– Specify advanced configuration values, by using the Advanced key (F5).

– Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent address space to support.







Determine what to do nextSee “Checklist: Configuring Your Product Outside of CICAT” on page 28.

! Configure OMEGAMON XE for IMSplex menu (continued)

! If this is the second or third agent to be configured in the agent address space, on the Agent Address Space Selection panel:

– To share an existing agent address space, type S (Select) next to the address space name and then use Create runtime members to generate the job that updates the runtime members for the agent address space.

– To add a new agent address space, type A (Add) in the Action field and use the steps for configuring a new agent in the agent address space.

Note: If the agent is already configured to share an agent address space, a message showing the agent address space owner appears in the upper right corner of the Configure panel.



If you are defining an agent to run in an agent address space, use Create runtime members to generate the job that creates the runtime members for the agent address space.



Use Complete the configuration to display a set of instructions for completing the configuration outside of CICAT.

(The instructions are also covered in this guide.)


and “Complete the Configuration” on page 61

! Runtime Environments (RTEs) panel

Use L (Load libs after SMP/E) to load the target libraries to the runtime libraries for the RTE.





Checklist: Configuring Your Product Outside of CICAT






Reminder about the information availableIn addition to the detailed information provided in the online help in CICAT, CICAT contains a summary of the information contained in this guide.

The Complete the configuration option on the Configure menu also displays the manual steps you perform outside of CICAT to complete the configuration.

Checklist: Configure product outside CICATThe following checklist contains the manual steps you perform outside of CICAT to complete the configuration of OMEGAMON XE.

✓ Configuration Steps to Perform Outside CICAT Location of the Information You

Will Need

! Copy the started task procedures from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

“Copying the Procedures for the Started Tasks” on page 63

! Copy VTAM definitions and vary the major node active:

! Copy VTAM definitions from rhilev.midlev.RKANSAM to your VTAM list library (VTAMLST).

! Vary the VTAM major node in VTAMLST active.

“Copying the VTAM Definitions and Varying the VTAM Node Active” on page 64

! APF-authorize the RKANMODn runtime load libraries. “APF-authorizing Libraries” on page 65



! Verify the configuration:

! If your OMEGAMON XE product and the CMS are installed and configured in the same address space:

– vary the CMS VTAM major node active – start the started task for the CMS

! If your OMEGAMON XE product and the CMS are installed in different address spaces and the CMS is a local CMS:

– vary the CMS VTAM major node active– start the started task for the CMS– start the started tasks for the agent

! If your OMEGAMON XE product and the CMS are installed in different address spaces and the CMS is a non-local CMS:

– start the CMS on the platform where it is installed– start the started task for the agent

“Verifying the Configuration: Same Address Space” on page 66

“Verifying the Configuration: Different Address Space” on page 67

“Verifying the Configuration: CMS on a Different Platform” on page 68

✓ Configuration Steps to Perform Outside CICAT Location of the Information You

Will Need

Checklist: Customizing Your Product Outside of CICAT


Checklist: Customizing Your Product Outside of CICAT




Reminder about the information availableIn addition to the detailed information provided in the online help in CICAT, CICAT contains a summary of the information contained in this guide.

Checklist: Customize product outside CICATThe following checklist contains the manual steps you perform outside of CICAT to customize your OMEGAMON XE product.

✓ Customization Steps to Perform Outside CICAT Location of the Information You

Will Need

! If you will be using a CCC/3270 or CMW interface and want to be able to zoom to the OMEGAMON II product, enable the zoom function.

“Enabling the Zoom Feature to Access an OMEGAMON II Session” on page 70

! If you want to replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT.

page 32


Checklist: Updating the Configuration

Checklist: Updating the Configuration

Checklist: Update and change the configuration In some cases, you will need to update the configuration for a product.

The following checklist contains the steps you perform inside and outside of CICAT to update the configuration.

✓ Step Location of the Information You

Will Need

! Make the changes you want to the configuration in CICAT and

! use the L (Load libs after SMP/E) select on the Runtime Environments (RTEs) panel in CICAT to load the target libraries to the runtime libraries

! perform the manual steps required to complete configuration outside of CICAT (if any)

“Updating and Changing the Configuration” on page 72

! If you want to replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT.

page 32

Using Advanced Features in CICAT


Using Advanced Features in CICAT

Determine the advanced feature to use Use the following advanced features if you

� have completed the appropriate checklist for configuring products

� have completed the appropriate checklist for verifying that the configuration is complete

Table 2. Advanced Features Available in CICAT

TaskAdvanced

FeatureLocation of Information

Port an existing RTE to one or more MVS images, without reconfiguring the RTE for those MVS images

System Variable Support


Replicate and transport an RTE to one or more MVS images

Batch Mode Processing


Overview of Processes, Methods, and CICAT Modes 33

Overview of Processes,Methods, and CICAT

Modes

IntroductionReview this chapter only if you are not familiar with Candle or the process of installing and configuring Candle products.

Chapter ContentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 34Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Processes for Installing, Configuring, and Maintaining Products . . . . . . . . 36Background about CICAT Modes: Interactive and Batch . . . . . . . . . . . . . 41

2

Determining the Topics to Use in this Chapter



Determine the topics to use in this chapterThis chapter provides background information about Candle terminology, process, and the Candle Installation and Configuration Assistance Tool (CICAT).

If you are not familiar with the content, review all of the topics. These topics include:

� Candle terminology

� the process for installing products and the process for installing maintenance (including the similarities and differences between the two processes)

� the process for installing and configuring products and maintenance, and where the steps in the process are performed (including examples of the tasks performed during each of the steps in the process and where to locate the information you will need)

� modes available for working in CICAT and the tasks they are used to complete (Interactive Mode and Batch Mode)


Candle Terminology

Candle Terminology

Terminology

The following list contains some of the terms used in this guide and defines those terms.

Candle Installation and Configuration Assistance Tool (CICAT)

Tool used to: � install new products or new versions of products� install maintenance for existing products� begin the configuration of products or maintenance

(if required for that particular maintenance)

Component Product or feature provided by Candle that is a separate started task

Configuring Making a product operational by completing the configuration of the product inside CICAT and completing the manual steps required outside of CICAT

Cumulative Maintenance

Maintenance through a given date that is customer approved

Customizing Modifying the defaults for options and settings and other changes that reflect the needs of your site

Installing Loading the contents of the Candle product and maintenance and installing a product

Migrating Preserving the customized data so that you can use it in a newer version of the product

Preventive Maintenance

Maintenance through a given date that is customer approved, but not yet included in Cumulative Maintenance

Runtime Environments (RTEs)

A group of runtime libraries that execute Candle products on an MVS image

Runtime libraries Libraries in the RTE that are used by the product when the product is started

Target libraries SMP/E controlled libraries that contain the source from the distribution media

Processes for Installing, Configuring, and Maintaining Products



Processes for installing products and maintenance: a comparison

The following illustration shows the steps in the process and compares the steps you perform when:

� installing new products or new versions of existing products

� installing maintenance for existing products

Table 3. Installing Products and Maintenance: A Comparison

Step in the ProcessRequired to Install

Products?Required to Install

Maintenance?

Prepare to install products and maintenance X X

Load and start CICAT X X

Install products and components X

Install maintenance (if any) X X

Begin to configure the products and components

X X

Complete the configuration of products and components by performing the manual steps required to make the product operational

X

Once configured, complete the manual steps to customize the product for your site (if any)

X

If you want to replicate Candle products or use Candle products on other MVS images, use some of the advanced features in CICAT designed to make this implementation easier

X X



Processes for installing and configuring products: a comparison

The following illustration shows the steps in the process and compares the steps you perform when:

� installing new products or new versions of existing products

� installing maintenance for existing products

Table 4. Installing and Configuring: A Comparison

Step in the ProcessPerformed in

CICAT?Performed

Outside of CICAT?

Prepare to install products and maintenance X

Load and start CICAT V300 X (if CICAT has been previously installed)

X (if you are installing CICAT for the first

time)

Install products and components X

Install maintenance (if any) X

Begin to configure the products and components

X


X


X

If you want to replicate Candle products or use Candle products on other MVS images, use some of the advanced features in CICAT designed to make this implementation easier

X



Example tasks in the process The table shows some examples of tasks you perform.

Table 5. Example Tasks for Installing, Maintaining, and Configuring

Step in the Broad Process Examples of Tasks

Prepare to install products and maintenance

� Review the software and space requirements for CICAT and the products and components you want to install

� Perform optional steps to prepare, such as backup your existing data sets

Load and start CICAT � Review the available files and the information in the DOCFILE

� If you are using CICAT for the first time and do not have an earlier version of CICAT installed, load CICAT from the distribution media

Install products and components

� Specify the high-level qualifiers for the product libraries � Allocate the product libraries � Receive and apply product components

Install maintenance (if any) � Review information about the PTFs provided in the DOCFILE

� Receive and apply product maintenance

Begin to configure the product and components

� Inside CICAT, create or select the RTE that will contain the product you want to configure

� Inside CICAT, specify basic configuration values for the product


� Outside of CICAT, manually copy members and libraries required by the product

� Outside of CICAT, verify the configuration by starting the product and displaying data in the user interface


� For some products, specify the security settings� For some products, specify the monitoring options

specific to your site



Where to find the information you will need The table shows the steps in the process and where to locate the information you will need.

If you want to replicate or use Candle products on other images, use some of the advanced features in CICAT

� Use Batch Mode to replicate and transport RTEs � Port an existing RTE to one or more MVS images

without reconfiguring the RTE for those MVS images

Table 6. Locating Information for Installing and Configuring

Step in the Broad Process Where to Locate Information about Procedures

Where to Locate Information about

Specific Values

Outside of CICAT, prepare to install products and maintenance



If you are: � migrating from CICAT

V200, load and start CICAT V300 using CICAT V200

� installing CICAT V300 for the first time, load and start CICAT outside of CICAT



Using CICAT, install products and components



Using CICAT, install maintenance (if any)



Table 5. Example Tasks for Installing, Maintaining, and Configuring

Step in the Broad Process Examples of Tasks



Using CICAT, begin to configure the products and components



Outside of CICAT, complete the configuration of products and components by performing the manual steps required to make the product operational

This guide

The Complete the configuration option on the Configure OMEGAMON XE Menu


Outside of CICAT, complete the manual steps to customize the product for your site (if any)

This guide Online help in CICAT

If you want to replicate Candle products or use products on other images, use some of the advanced features in CICAT



Table 6. Locating Information for Installing and Configuring

Step in the Broad Process Where to Locate Information about Procedures

Where to Locate Information about

Specific Values


Background about CICAT Modes: Interactive and Batch


Modes provided in CICAT

CICAT has two modes:

� Interactive Mode

� Batch Mode

The following table provides a description for each of the two modes.

Table 7. CICAT Modes: Interactive and Batch

Mode Description

Interactive ISPF panel-driven facility that assists you in specifying parameters and tailoring jobs for � installing and configuring new products � installing and configuring new versions of products � installing maintenance

Batch Facility that creates a single batch job that you can use to build, configure, and load an RTE. This single job performs all of the same RTE processing as the interactive CICAT.

Batch Mode is a simple and useful way of replicating RTEs to other MVS systems.



Plan Your Configuration 43

Plan Your Configuration

Introduction This chapter contains information that you should review before configuring products and maintenance. This chapter:

� contains background about the products and components

� helps you determine the components to configure

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 44Overview of the Candle Products and Components . . . . . . . . . . . . . . . . . 45Details about the Candle Products and Components . . . . . . . . . . . . . . . . 48Requirement for OMEGAMON XE for IMSplex . . . . . . . . . . . . . . . . . . . . 50Determining the Components to Install and Configure . . . . . . . . . . . . . . . 51

3




Relationship of the topics in this chapter and the checklists

This chapter contains topics that correspond to the tasks in Checklist: Prerequisites for Configuring Products in Chapter 1.

Determine the topics to use in this chapter

If you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter. R indicates that topic is required; O indicates the topic is optional.

Page Numbers for Topics

page45

page48

page50

page51

Determine the products and components to configure and whether or not the products and components have manual steps performed outside of CICAT

R

Review details provided for some of the products and components

O

Review information about Candle products and components

O

Review requirements for the products before you begin the configuration

R


Overview of the Candle Products and Components


Background about how CICAT installs products and components CICAT automatically installs all the required and optional products and components.

In most cases, you must also configure the components to make them available.

Background about Candle products and components The following table shows all the product and components available with the Candle products. The products and components are listed in the order they should be installed and configured (if configuration is required)

Table 8. Overview of the Products and Components

Component Name or Category Purpose

Platform(s) for Product or Component

Candle Management Server (CMS)

Component that: � consolidates the data collected by the agent and

distributes the data to the CandleNet Command Center (CCC) interface

� in some cases, receives commands from the CCC interface and distributes them to the appropriate agent or OMEGAMON XE product

� stores historical data and prototypes for configuration in the form of seed data

Note: If you have a distributed environment, you can use a CMS on the different platforms in that environment.

� Windows NT (Intel-based)

� Windows 98� Windows 2000� MVS � UNIX

Persistent Data Store (CT/PDS)

Component that records and stores historical data that you can access using a CCC or OMEGAMON XE interface.

In some cases you can configure the CT/PDS with the agent or OMEGAMON XE product. If you decide not to configure the CT/PDS with the CMS, configure the PDS when you configure the agent.

MVS



OMEGAMON II Component that collects and displays data in the OMEGAMON II user interface(s). These include: � the menu driven CUA interface that is IBM

SAA/CUA compliant � the facility that allows multiple OMEGAMON IIs to

execute in the same address space and that communicates with all of them; the Common Interface (CI)

� for some OMEGAMON IIs, the command driven Classic interface

MVS

Candle Subsystem

Component that is an MVS subsystem running in its own address space, that provides dynamic I/O activity to OMEGAMON II

MVS

Agents and OMEGAMON XE products

Component that monitors systems, subsystems, and applications on the system where they are installed. Agents: � collect data and monitor performance � provide data and performance information to the

CMS � receive instructions from the CMS � issue commands to the system or application you

are monitoring

Platform appropriate for the system or software being monitored






Agents and OMEGAMON XE products (continued)

Agents can be: � OMEGAMON XE, which collect performance and

analysis data.� Alert Managers, which monitor alerts and relay

the information from console or message logs, network management products, and system management product.

� Alert Emitters, which monitor events or exceptions in products running under the control of the CMS and relay them back for corrective action (if applicable).

� Gateways, which communicate events to a management application running on a supported platform using a network service.

Platform appropriate for the system or software being monitored

OMEGAVIEW® If available, the product that can be used to: � display data from all the OMEGAMON IIs in a

single location � display an OMEGAMON II session in an

OMEGAMON XE, so that the condition that caused an alert can be researched in OMEGAMON II

MVS

CandleNet Command Center (CCC) interface

Component that is the graphical user interface (GUI) you use to display and work with data provided by the CMS or agent. These include: � the Windows based GUI Candle Management

Workstation® (CMW™) that communicates with the CMS

� the Java based GUI CandleLight Workstation that communicates directly with an agent one agent at a time (automatically installed with the CMW).


� Windows 98� Windows 2000

OMEGAMON XE platform

Component that is the graphical user interface (GUI) you use to display and work with data provided by the Java based GUI CandleNet Portal™ (CNP) that communicates with the CMS and CNP server. (This interface can be run in desktop or browser mode.)


� Windows 98� Windows 2000




Details about the Candle Products and Components



Details about the relationships and CMS typesThe following table shows the CMS types, the relationship for the type, and a description of the relationship.

Table 9. Details about the Relationships and CMS Types

Relationship Candle Term

Description

CMS to CMS relationship

Hub CMS that:� receives data from agents and remote CMS in the

environment � communicates data to and receives commands from

CNP interface

Remote CMS that: � receives data from agents � communicates data to the Hub CMS only (It does not

communicate with a CNP interface.)

CMS to agent relationship

Local CMS that is installed in the same CSI as the agent

Non-local CMS that is installed on: � MVS, but is not installed and configured in the same RTE

as the agent. � MVS, but is not installed and configured in the same CSI

as the agent. (For example, the CMS is installed using a different INSTLIB.)

� a platform other than MVS (such as UNIX)



Details about OMEGAMON XE for IMSOMEGAMON XE for IMS is an agent that you can use to monitor the performance of IMS subsystems.

For example, you can use OMEGAMON XE for IMS to monitor the performance of these characteristics of IMS subsystems:

� pool storage utilization

� IMS device activity

� CPU usage and page-in counts

The data collected by OMEGAMON XE for IMS can then be displayed using CandleNet Portal™.

Details about OMEGAMON XE for IMSplexOMEGAMON XE for IMSplex is an agent that you can use to monitor the performance of IMS and IMS subsystems. It includes all the monitoring capability of OMEGAMON XE for IMS and you can use it to monitor:

� coupling facility analysis of IMS components

� global database locks and shared queues

� multi-system coupling analysis

The data collected by OMEGAMON XE for IMSplex can then be displayed using:

� CandleNet Portal� Candle Management Workstation®

Requirement for OMEGAMON XE for IMSplex


Requirement for OMEGAMON XE for IMSplex

Build a CQS address space if running IMS V6.1If you are running IMS V6.1, OMEGAMON XE for IMSplex must have its own CQS started task to obtain information on Shared Queue resources. To build this CQS address space, begin with cloning the IMS CQS started task JCL.

Follow these steps to build a CQS address space for IMSplex.

1. Create a CQSIPxxx member in your IMS PROCLIB, using the sample format:ARMRST=NCQSGROUP=aaaaSSN=bbbbSTRDEFG=nnnSTRDEFL=zzz

where:

� The CQSGROUP must be the same as the IMS CQSIPyyy member.� The STRDEFG suffix must be the same as the IMS CQSIPyyy member.� The SSN and STRDEFL must be unique.

� The SSN name is specified in the KIPCQSID member in the RKANPAR library. You will need to specify this name during CICAT configuration on the IMS Subsystems Monitored panel in response to the following field:

For users of IMS V6.1, enter the CQS subsystem name ==> abcd

where abcd is the SSN.

Note: You must use a unique CQSINIT parameter in the JCL. This parameter is the suffix of the CQSIPxxx member in the PROCLIB.

2. Create a CQSSLzzz member in your PROCLIB, where zzz matches the STRDEFL=zzz in the CQSIPxxx member. In this member, the STRNAME must be the same as in the IMS CQSSL member. However, CHKPTDSN must be unique. Refer to the CQS manual for the requirements of these VSAM libraries. The CCIP CQS cannot specify the same CHKPTDSN being used by any other IMS CQS.

The CQSSG member that IMS uses must be shared with the IMSplex CSQ. You can share the BPECONFG member used by the IMS CQS. (Open an ITR to understand the performance implications of this member’s parameters, so that PLEX BPECONFG has minimal system impact.)


Determining the Components to Install and Configure


Components that can be shared by more than one productIn some cases, a product or component can be shared by more than one product. If you have already installed and configured these types of components, you can use the existing component.

For example, you can use the Candle Management Server (CMS) with more than one Candle product.

If you are going to use an existing component, the component must be current. You must have installed and configured the component for another Candle product at the same level.

Determine the products and components you will needThe following table shows the products and components available for most Candle products. The table shows:

� a typical Candle product and its components, and whether or not the components are required (R) or optional (O)

(A blank indicates that the product does not use the component.)

� whether or not the component can be shared

� additional information that might help you decide whether or not you want to configure the component (if any)

The products and components are listed in the order they should be installed and configured (if configuration is required).



Table 10. Determining the Products and Components You Will Need

Component Name or Category O

ME

GA

MO

N X

E

for

IMS

OM

EG

AM

ON

XE

fo

r IM

Sp

lex

Can

be

Sh

ared

?

Additional Information (If Any)

Candle Management Server (CMS)

R R Y

Persistent Datastore (CT/PDS)

O O N You can configure the CT/PDS with the CMS.

OMEGAMON II R R N

Candle Subsystem Y Required only if you configure an OMEGAMON II product.

Candle recommends using one Candle Subsystem for all the Candle products and components you install and configure.

Agents and OMEGAMON XE products

R R Y

OMEGAVIEW® O Y Configure this component only if you want to access an OMEGAMON II session using the zoom feature (if available).

CandleNet Command Center or OMEGAMON XE interface

R R Y If the interface you are using is the CandleNet Command Center, you can also use:� the 327x-family color terminals with

extended attributes with some Candle mainframe products

� all 329x-family terminals with Candle mainframe products



Determine whether or not you have to configure the products and components

The table shows the components and indicates whether or not you must:

� configure the component using CICAT to make the component available to the product

� perform manual steps outside of CICAT to configure the component to make it available to the product.

The products and components are listed in the order they should be installed and configured (if configuration is required).

Table 11. Determining the Products and Components to Configure

Component Name or Category Configure Using CICAT?

Requires Manual Steps Outside of

CICAT?

Candle Management Server (CMS) Y Y

Persistent Datastore (PDS) Y Y

OMEGAMON II Y Y

Candle Subsystem Y Y

Agents and OMEGAMON XE products Y Y

OMEGAVIEW®(if available) Y Y

CandleNet Command Center or OMEGAMON XE Platform interface

N/A N/A



Locate information about configuring the product or componentThe table shows where you can locate information about configuring the product or component if it is not included in this guide.

Table 12. Locate information about configuring the product or component

Component Name or Category Location of Information for Configuring

the Product or Component

Candle Management Server (CMS) Candle Management Server Configuration and Customization Guide

OMEGAMON II Configuration and Customization Guide for the OMEGAMON II product

Candle Subsystem Configuration and Customization Guide for the OMEGAMON II product

OMEGAVIEW® Configuration and Customization Guide for the OMEGAVIEW product

Agents and OMEGAMON XE products This guide

Persistent Datastore (PDS) Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center

CandleNet Command Center or OMEGAMON XE Platform interface

Installing Candle Products on Windows and OS/2

Start CICAT and Access the Configuration Menu 55

Start CICAT and Access theConfiguration Menu

IntroductionThis chapter provides detailed information about

� starting CICAT

� accessing the menu in CICAT for configuring the product

� using CICAT defaults and restrictions, and some of the commands available to assist while using CICAT to install products and maintenance

Chapter ContentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 56Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Accessing the Menu for Configuring the Product. . . . . . . . . . . . . . . . . . . . 58Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4




Relationship of the topics in this chapter and the checklistsThis chapter contains topics that correspond to the tasks in Checklist: Starting CICAT and Accessing the Menu for Configuration in Chapter 1.

This chapter also contains a topic that covers some additional information about using CICAT (such as CICAT defaults and commands).

Determine the topics to use in this chapterIf you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter. The R indicates that topic is required. The O indicates the topic is optional.


page57

page58

page59

Start CICAT R

Access the menu for configuring the product in CICAT R

Review information about restrictions, defaults, commands, and functions

O


Starting CICAT

Starting CICAT

Start CICAT

Follow these steps to start CICAT.

1. Log onto a TSO session.

2. Invoke ISPF.

3. Go to a TSO command line. (In most cases, this is option 6 on the ISPF Primary Option Menu.)

4. Enter the following command:

EX ‘shilev.INSTLIB’

(where shilev is the high-level qualifier you specified for CICAT)

Result: CICAT first displays the copyright panel and then the CICAT Main Menu. (Both the copyright panel and the CICAT Main Menu display the version and release of CICAT.)

Accessing the Menu for Configuring the Product


Accessing the Menu for Configuring the Product

Select the product to configure and access the menu

Follow these steps to access the Configure OMEGAMON XE Menu.

1. If this is the first time you have used CICAT V300 to configure a product, from the CICAT Main Menu select Configure products > Set up configuration environment.

2. From the CICAT Main Menu, select Configure products > Select product to configure.(Only those packages that are eligible to be configured are listed on this panel.)

3. On the Product Selection Menu, specify S to select a product to be configured. You can only select one product at a time for configuration.Result: CICAT displays the Runtime Environments (RTEs) panel.

4. On the Runtime Environments (RTEs) panel, specify: � to use an existing RTE, the C (Configure) select

� to create a new RTE, the A (Add), B (Build libraries), and C (Configure) selects

Result: CICAT displays the Product Configuration Selection Menu.

5. On the Product Configuration Selection Menu, select the component you want to configure.Result: CICAT displays the Configure OMEGAMON XE Menu.


Using CICAT

Using CICAT

Defaults provided with CICAT Whenever possible, CICAT provides defaults for fields and options. These defaults

� when provided, should be sufficient to complete the installation of products and maintenance

� can be changed to values specific to your site

Assistance provided in CICAT Whenever possible, CICAT checks the values you specify and verifies that you have specified the required values. If CICAT detects an error or omission, it displays a short message.

Display requirements in ISPF If you are using a 3270 Model 2 (24 x 80) display, you must turn off the pre-defined function (PF) keys so that the CICAT panels are not truncated.

To turn off the pre-defined function keys, type PFSHOW on any command line and press Enter until the function keys no longer appear.

Restrictions The length of the high-level qualifier for the runtime libraries must be 26 characters or less.

You cannot use

� the ampersand character (&) as input data in CICAT interactive or batch mode

� the ISPF feature for edit recovery

(If the ISPF RECOVERY ON command is entered, edits will produce a recovery error message. Enter the RECOVERY OFF command to suppress the error messages.)

Using CICAT


Commands and functions The following list shows some of the commands and functions available in CICAT, that you can use for navigation and to display information.

Advanced key On some panels for configuring products, displays panels where you can specify specialized values (such as values for the Persistent Data Store for a CMS).

End key Returns to the previous panel.

Enter key Accepts the values you have specified and displays the next panel in the process.

HELP command Displays information about a panel or the extended description for a message.

README command Displays the README for the current version of CICAT.

README APP command Displays information about default applids for started tasks and VTAM, and how CICAT processes VTAM applids.

README ERR command Displays a list of CLIST error codes and descriptions (for both interactive and batch mode).

README SYS command Displays a information about system variable support.

UTIL command Displays the Installation Services and Utilities menu.

Complete the Configuration 61

Complete the Configuration

IntroductionThis chapter contains:

� the manual steps you must perform outside of CICAT to complete the configuration of the OMEGAMON XE products

� the procedure to follow to verify the configuration of the OMEGAMON XE product

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 62Copying the Procedures for the Started Tasks . . . . . . . . . . . . . . . . . . . . . . 63Copying the VTAM Definitions and Varying the VTAM Node Active . . . . . 64APF-authorizing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . . . . 66Verifying the Configuration: Different Address Space . . . . . . . . . . . . . . . . 67Verifying the Configuration: CMS on a Different Platform. . . . . . . . . . . . . 68

5




Relationship of the topics in this chapter and the checklists

This chapter contains topics that correspond to the tasks in Checklists: Configuring the Product Outside of CICAT in Chapter 1.

Determine the topics to use in this chapter

If you are not sure of the topics you will need in this chapter or you are not using a checklist, review the matrix to determine the pages to use in this chapter. The R indicates that tasks in the topic are required. The O indicates the tasks in the topic are optional.


page63

page64

page65

page66

page67

page68

OMEGAMON XE product and the CMS are installed and configured in the same address space

R R R R

OMEGAMON XE product and the CMS are installed in different address spaces and the CMS is a local CMS

R R R R

OMEGAMON XE product and the CMS are installed in different address spaces and the CMS is a non-local CMS

R R R R


Copying the Procedures for the Started Tasks

Copying the Procedures for the Started Tasks

Background about the started tasks When you use CICAT to install and configure a product or component, CICAT creates the started task procedures.

You must copy the started task procedures to your procedure library (PROCLIB) to complete the configuration.

Copy the procedures for the started tasks to your procedure library You must copy the started task procedures for the product from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

Copying the VTAM Definitions and Varying the VTAM Node Active


Copying the VTAM Definitions and Varying the VTAM Node Active

Background about the VTAM definitions and the VTAM major nodeIf you configured OMEGAMON XE to use SNA as the communication protocol, CICAT created VTAM definitions.

To complete the configuration, you must:

� copy the VTAM definition to VTAMLST

� vary the VTAM major node active

Copy VTAM definitions and vary the VTAM major node activeFollow this procedure to complete the configuration for the SNA communication protocol.

1. Copy the VTAM definition from rhilev.midlev.RKANSAM to VTAMLST. The VTAM definition in rhilev.midlev.RKANSAM has the same name you specified using CICAT for either:

� the VTAM major node

� the Candle global VTAM major node (The default is KCANDLE1.)

2. Vary the VTAM major node active using the following command. V NET,ACT,ID=ccccccccc

The ccccccccc indicates the name for the VTAM major node you specified using CICAT for either:

� the VTAM major node

� the Candle global VTAM major node


APF-authorizing Libraries

APF-authorizing Libraries

Background about APF-authorization The load libraries must be APF-authorized or some of the functions in the product may not be available.

You APF-authorize the load libraries by adding them to your list of APF-authorized libraries.

APF-authorize the libraries If the RTE is sharing with SMP/E, APF-authorize the target load libraries:

� thilev.midlev.TKANMOD

� thilev.midlev.TKANMODL

For all other RTEs, APF-authorize the runtime load libraries:

� rhilev.midlev.RKANMOD

� rhilev.midlev.RKANMODL

If one library in a steplib or joblib concatenation requires APF-authorization, all the libraries in the concatenation require APF-authorization.

Verifying the Configuration: Same Address Space


Verifying the Configuration: Same Address Space

Prerequisites for verifying the configurationIn addition to completing the configuration for the product, you must also have:

� completed the configuration of the interface you want to use

� completed the configuration of the CMS on the appropriate platform (including seeding the CMS using the interface)

Process to follow to verify the configuration Follow this process to verify the configuration by starting the product. Follow this process only if:

� the CMS is installed on MVS

� the product and the CMS are installed in the same address space

Figure 1. Process for Verifying the Configuration: Same Address Space

If the Candle Management Server (CMS) is not already running, vary the CMS VTAM major node active.

.

If the CMS is not already running, start the started task for the CMS.

Using the appropriate CandleNet Portal interface, connect to the Hub CMS and use theinterface to verify that the data for the product is being displayed.


Verifying the Configuration: Different Address Space

Verifying the Configuration: Different Address Space

Prerequisites for verifying the configurationIn addition to completing the configuration for the product, you must also have completed the configuration of the:

� interface you want to use

� CMS on the appropriate platform (including seeding the CMS)


� the CMS is installed on MVS

� the agent and CMS are in different address spaces

Figure 2. Process for Verifying the Configuration: Different Address Space

If you selected SNA as the communication protocol for the agent instead of TCP/IP and the CMS is not already running, vary the CMS VTAM major nodeactive.

If the CMS is not already running, start the started task for the CMS.

Start the started task for the product and components you configured.

Using the appropriate CandleNet Portal interface, connect to the Hub CMSand use the interface to verify that the data for the product is being displayed.

Verifying the Configuration: CMS on a Different Platform


Verifying the Configuration: CMS on a Different Platform

Prerequisites for verifying the configurationIn addition to completing the configuration for the product, you must also have:

� completed the configuration of the interface you want to use

� completed the configuration of the CMS on the appropriate platform (including seeding the CMS using the interface)


� you installed the agent on MVS

� the CMS in installed on a different platform

Figure 3. Process for Verifying the Configuration: CMS on a Different Platform

.

If the CMS is not already running, start CMS on the platform where it is installed.(For information about using a CMS on a different platform, see the InstallationGuide for that platform.)

Start the started task for the product and components you configured.

Using the appropriate CandleNet Portal interface, connect to the Hub CMSand use the interface to verify that the data for the product is being displayed.

Complete the Customization 69

Complete the Customization

IntroductionThis chapter contains information about the manual steps you must perform outside of CICAT to complete the customization.

Chapter contentsEnabling the Zoom Feature to Access an OMEGAMON II Session . . . . . . 70

6

Enabling the Zoom Feature to Access an OMEGAMON II Session


Enabling the Zoom Feature to Access an OMEGAMON II Session

Background about the Zoom featureYou can use the Zoom feature to research the cause of an alert by displaying and reviewing the conditions raised by the OMEGAMON II product.

Prerequisites for using the Zoom featureYou must have installed and configured the:

� OMEGAMON XE for IMSplex product

� the corresponding OMEGAMON II

� OMEGAVIEW

You must have a logon ID for OMEGAVIEW with administrator authority.

Procedure to follow to use the Zoom feature Follow this procedure to enable the Zoom feature in OMEGAMON XE.

1. Log on to an OMEGAVIEW session.

2. On the Tools menu, select Tools > Configuration Manager.

3. On the Session Type pop-up, select the session type appropriate for the OMEGAMON II.

4. On the Add Session Information pop-up, complete the fields and press Enter.

5. On the Configuration Manager panel, confirm that the OMEGAMON II sessions you want to zoom to are active. (If the session is not active, type R in the select field to start a new session.)

6. Exit OMEGAVIEW.

Manage and Update the Configuration 71

Manage and Updatethe Configuration

IntroductionThis chapter contains information about updating and changing your configuration that correspond to the tasks in Checklist: Updating the Configuration in Chapter 1.

Chapter contentsUpdating and Changing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 72

7

Updating and Changing the Configuration


Updating and Changing the Configuration

Example of a change to the configuration that requires manual stepsIf the changes you make in CICAT are to configuration values that also require manual steps outside of CICAT, you must also perform the steps outside of CICAT when you update or change the values in CICAT.

For example, if you are using the persistent data store and you change the prefix for the procedure using CICAT, you must also copy the renamed procedure to your PROCLIB.

For step-by-step instructions for these tasks, see Chapter 5 in this guide.

Overview of the process for updating or changing your configurationThe illustration shows the process for updating or changing your configuration.

Figure 4. Process for Updating and Changing Your Configuration

.Using CICAT, make the changes you want to the configuration.

.

On the Runtime Environments (RTEs) panel in CICAT, use the L (Load libs after SMP/E select to load the target libraries to the runtime libraries.

.

If the changes are to values that require manual steps outside of CICAT to complete the configuration, perform the appropriate steps.

Index 73

Index

Aaccessing

CICAT 55menu for configuring 21, 58

addinga new agent address space 23, 27a new IMS subsystem 22, 25a new IRLM subsystem 26

Adobe portable document format 11advanced features 32Advanced key 60agent

OMEGAMON XE for IMS 49OMEGAMON XE for IMSplex 49

agent address space 23, 26agents 46alert emitters 47alert managers 47APF-authorization 65APF-authorizing load libraries 28autodiscovery 22, 25, 26

Bbatch mode 41batch mode processing 32building a CQS address space 50

CCandle Installation and Configuration

Assistance Tool (CICAT) 35Candle Management Server 45Candle Subsystem 46Candle terminology 35CandleNet Command Center 47CandleNet Portal 49CCC/3270 interface 30changing the configuration 31, 72

checklists 17, 19CICAT

accessing the menu for configuring 58commands 60defaults 59defaults and restrictions 55definition 35displaying information in 60functions 60modes 41release 57restrictions 59starting 57version 57

CMS to agent relationship 48CMS to CMS relationship 48CMS types 48CMW interface 30communication protocols 23, 26completing the configuration 24, 27, 28components 35

definition of shared 45configuring

definition 35inside CICAT 22, 25outside of CICAT 28prerequisites 20products 55updating or changing 72

copying started task procedures 28copying VTAM definitions 28CQS subsystem name 25creating a new RTE 58creating runtime members 23, 27CT/PDS 45cumulative maintenance 35customizing


definition 35detailed procedures 69

customizing product outside CICAT 30

Ddefaults provided with CICAT 59defining agents to run in an agent address

space 23, 26defining an agent to run in the CMS address

space 24defining IMS subsystems to CMS 22, 25defining IRLM subsystems to CMS 26determining products and components to

install and configure 51different address space 29disabling data collection 22, 25, 26displaying information in CICAT 60document organization 9documentation for the product 8documentation set information 8

Eedit recovery 59enabling zoom function 30End key 60Enter key 60

Ggateways 47global VTAM major node 64

HHELP command 59, 60historical data 45hub CMS 48

IIMS 6.1 25, 50IMS 7.1 or higher 25IMS subsystems 22, 25installing

definition 35installing agent into local CMS 24, 26interactive mode 41invoking ISPF 57IRLM subsystems 26ISPF display requirements 59

Llist of IMS subsystems 22, 25list of IRLM subsystems 26load libraries 65loading libraries after SMP/E 31loading target libraries 24, 27, 31local CMS 29, 48

Mmenu for configuring 58migrating 35modes in CICAT 41

Nnon-local CMS 29, 48

OOMEGAMON II 46OMEGAMON XE

platform 47products 46

OMEGAMON XE for IMS 49definition 49

OMEGAMON XE for IMSplexdefinition 49

OMEGAVIEW 47organization of the guide 9

PPDF files, adding annotations 12persistent data store 45PFSHOW command 59planning your configuration 43preventive maintenance

Index 75

definition 35printing problems 11procedures

copying for the started tasks 63processes

configuring products 37installing maintenance 36installing products 36

PROCLIBstarted tasks 63

product documentation 8

RREADME APP command 60README command 60README ERR command 60README SYS command 60RECOVERY OFF command 59RECOVERY ON command 59registering with local CMS 22, 25remote CMS 48replicating the product 30, 31restrictions in CICAT 59RTE 35RTE sharing with SMP/E 65running IMS V6.1 50Runtime Environments (RTEs) 35runtime libraries 27runtime load libraries 65runtime members 23, 27

Ssame address space 29shared queue resources 50sharing an agent address space 23, 27sharing an existing agent address space 23,

27specifying agent address space

parameters 23, 26started tasks

copying procedures 63starting CICAT 21, 55, 57

system variable support 32

Ttarget libraries 24target load libraries 65terminology 35

Uupdating

an IMS subsystem 22, 25an IRLM subsystem 26detailed procedures 71the configuration 31, 72

using an existing RTE 58using checklists in this guide 19using product on another MVS image 30UTIL command 60

Vvarying the major node active 28VTAMLST

copying the VTAM definition 64

ZZoom feature 70zooming to OMEGAMON II product 30


Date post:	15-Mar-2020
Category:	Documents
Upload:	others
View:	15 times
Download:	0 times

Configuration and Customization Guidepublib.boulder.ibm.com/tividd/td/ITOXfIMS/GC32-9302-00/... ·...

Documents