Configuration and Customization...

Configuration and Customization GuideOMEGAMON XE® for OS/390

Version 140

OMEGAMON XE for SysplexVersion 220

GC32-9312-00

March 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 OMEGAMON XE for OS/390 and OMEGAMON XE for Sysplex CCG

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/REMOTE, Availability Command Center, Candle, Candle CIRCUIT, Candle Command Center, Candle Direct logo, Candle Electronic Customer Support, Candle logo, Candle Management Server, Candle Management Workstation, CandleLight, CandleNet, CandleNet Command Center, CandleNet eBusiness Platform, CandleNet Portal, CL/CONFERENCE, CL/SUPERSESSION, CommandWatch, CT, CT/Data Server, CT/DS, DELTAMON, DEXAN, eBA, eBA*ServiceMonitor, eBA*ServiceNetwork, eBusiness at the speed of light, eBusiness Assurance, eBusiness Institute, ELX, EPILOG, ESRA, ETEWatch, IntelliWatch, IntelliWatch Pinnacle, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAMON Monitoring Agents, OMEGAVIEW, OMEGAVIEW II, PQEdit, Response Time Network, Roma, SitePulse, Solutions for Networked Applications, Solutions for Networked Businesses, TMA2000, Transplex, and Volcano.Trademarks and service marks of Candle Corporation: AF/Advanced Notification, AF/PERFORMER, Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS, Amsys, AutoBridge, AUTOMATED FACILITIES, Availability Management Systems, Business Services Composer, Candle Alert, Candle Business Partner Logo, Candle Command Center/SentinelManager, Candle CommandPro, Candle eDelivery, Candle eSupport, Candle Insight, Candle InterFlow, Candle Managing what matters most, Candle Service Suite, Candle Technologies, CandleNet, CandleNet 2000, CandleNet Conversion, CandleNet eBP, CandleNet eBP Access for S.W.I.F.T., CandleNet eBP Administrator, CandleNet eBP Broker Access for Mercator or MQSI, 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, Candle Vision, CCC, CCP, CCR2, 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, e2e, eBA*SE, eBAA, eBAAuditor, eBAN, eBANetwork, eBAAPractice, eBP, eBusiness Assurance Network, eBusiness at the speed of light, eBusiness at the speed of light logo, eBusiness Exchange, eBX, End-to-End, eNotification, ENTERPRISE, Enterprise Candle Command Center, Enterprise Candle Management Workstation, Enterprise Reporter Plus, ER+, ERPNet, ETEWatch Customizer, HostBridge, InterFlow, Candle InterFlow, Lava Console, Managing what matters most, MessageMate, Messaging Mastered, Millennium Management Blueprint, MMNA, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, NC4, NetGlue, NetGlue Extra, NetMirror, NetScheduler, New Times, New Team, New Readiness, OMA, OMC Gateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER Status Manager, OMEGAMON/e, OMEGAMON Management Center, OSM, PathWAI, PC COMPANION, Performance Pac, Powered by Roma Technology, PowerQ, PQConfiguration, PQScope, 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, Tracer, Unified Directory Services, WayPoint, and ZCopy.Trademarks and registered trademarks of other companies: AIX, DB2, MQSeries and WebSphere are registered trademarks of International Business Machines Corporation. Citrix, WinFrame, and ICA are registered trademarks of Citrix Systems, Inc. Multi-Win and MetaFrame are trademarks of Citrix Systems, Inc. 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 may be trademarks or registered trademarks of their respective owners.

Copyright © March 2004, 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

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11About this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 1. Start Here to Configure OMEGAMON XE for OS/390 . . . . . . . 15Using the Checklists and Topics in this Chapter . . . . . . . . . . . . . . . . . 16Checklist: Prerequisites for Configuring OMEGAMON XE for OS/390 18Checklist: Starting CICAT and Accessing the Menu for Configuration 19Checklists: Configuring OMEGAMON XE for OS/390 Using CICAT . 20Checklists: Configuring OMEGAMON XE for OS/390 Outside of CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 34Using Advanced Features in CICAT. . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 2. Start Here to Configure OMEGAMON XE for Sysplex . . . . . . . 37Using the Checklists and Topics in this Chapter . . . . . . . . . . . . . . . . . 38Checklist: Prerequisites for Configuring OMEGAMON XE for Sysplex 40Checklist: Starting CICAT and Accessing the Menu for Configuring OMEGAMON XE for Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Checklists: Configuring OMEGAMON XE for Sysplex Using CICAT . 42Checklist: Configuring OMEGAMON XE for Sysplex Outside of CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . 47Using Advanced Features in CICAT. . . . . . . . . . . . . . . . . . . . . . . . . . 48

Contents 3

Chapter 3. Overview of Processes, Methods, and CICAT Modes . . . . . . . . 49Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 50Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Processes for Installing, Configuring, and Maintaining Products. . . . . 52Background about CICAT Modes: Interactive and Batch . . . . . . . . . . 57

Chapter 4. Plan Your Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 60Candle Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . 61Details about the Candle Products and Components . . . . . . . . . . . . . 64Determining the Components to Install and Configure . . . . . . . . . . . 66Additional Terminology and An Example Configuration for OMEGAMON XE for Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Requirements and Restrictions for OMEGAMON XE . . . . . . . . . . . . . 72

Chapter 5. Start CICAT and Access the Menu for Configuring . . . . . . . . . 73Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Accessing the Menu for Configuring the Product . . . . . . . . . . . . . . . . 76Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 6. Completing the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 79Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . 80Copying the Procedures for the Started Task . . . . . . . . . . . . . . . . . . . 82Copying the VTAM Definition and Varying the VTAM Node Active . . 83Completing the Configuration of the Candle Subsystem . . . . . . . . . . 84Copying the Procedures for the End-to-End Response Time Feature . 86Copying the Procedures for the Persistent Datastore . . . . . . . . . . . . . 87Seeding the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Completing the Configuration for a Non-local CMS. . . . . . . . . . . . . . 93Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . 94Verifying the Configuration: Different Address Space. . . . . . . . . . . . . 95Verifying the Configuration: CMS on a Different Platform . . . . . . . . . 96Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 7. Completing the Customization . . . . . . . . . . . . . . . . . . . . . . . . . 99Determining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . 100


Migrating Your Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Specifying Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Collecting and Storing Historical Data . . . . . . . . . . . . . . . . . . . . . . . 107

Chapter 8. Managing and Updating the Configuration . . . . . . . . . . . . . . . 109Updating and Changing the Configuration . . . . . . . . . . . . . . . . . . . 110

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Contents 5


List of Tables

Table 1. Advanced Features Available in CICAT . . . . . . . . . . . . . . . . . . . . . . . 35Table 2. Advanced Features Available in CICAT . . . . . . . . . . . . . . . . . . . . . . . 48Table 3. Installing Products and Maintenance: A Comparison . . . . . . . . . . . . . 52Table 4. Installing and Configuring: A Comparison . . . . . . . . . . . . . . . . . . . . . 53Table 5. Example Tasks for Installing, Maintaining, and Configuring . . . . . . . . 54Table 6. Locating Information for Installing and Configuring. . . . . . . . . . . . . . 55Table 7. CICAT Modes: Interactive and Batch. . . . . . . . . . . . . . . . . . . . . . . . . 57Table 8. Overview of the Products and Components . . . . . . . . . . . . . . . . . . . 61Table 9. Details about the Relationships and Types of CMSs . . . . . . . . . . . . . . 64

Table 10. Determining the Products and Components You Will Need . . . . . . . . 66Table 11. Determining the Products and Components to Configure . . . . . . . . . 68Table 12. Locating Information About Configuring the Product or Component. 69Table 13. Additional Terminology for CMSs for OMEGAMON XE for Sysplex . 70Table 14. Methods for Defining the Candle Subsystem to OS/390 . . . . . . . . . . 84Table 15. Guidelines for Seeding the CMS for Products on MVS . . . . . . . . . . . 89Table 16. Parameters You Can Use with the Command to Migrate Your Profile 104

List of Tables 7


List of Figures

FIGURE 1. Illustration of An Example Configuration for OMEGAMON XE for Sysplex 71

FIGURE 2. Process for Verifying the Configuration: Same Address Space . . . . . 94FIGURE 3. Process for Verifying the Configuration: Different Address Space . . . 95FIGURE 4. Process for Verifying the Configuration: CMS on a Different Platform 96FIGURE 5. Process for Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . 97FIGURE 6. Process for Migrating Your OMEGAMON II Profile . . . . . . . . . . . . . 102FIGURE 7. Process for Updating and Changing Your Configuration . . . . . . . . . 110

List of Figures 9


Preface

P
This manual covers the configuration and customization for:
® OMEGAMON® XE for OS/390, Version 140

® OMEGAMON XE for Sysplex, Version 220 (renamed from Candle Command Center® for Sysplex)

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

Preface 11

About this Book

About this Book

Who should read this bookThis guide is intended for product administrators and systems programmers and other users of:

® OMEGAMON XE for OS/390, Version 140

® OMEGAMON XE for Sysplex, Version 220

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.

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 OS/390 and OMEGAMON XE for Sysplex CCG" in the subject line.


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.

Preface 13


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

Start Here to ConfigureOMEGAMON XE for OS/3901

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. . . . . . . . . . . . . . . . . . . . . 16Checklist: Prerequisites for Configuring OMEGAMON XE for OS/390 . . . 18Checklist: Starting CICAT and Accessing the Menu for Configuration . . . . 19Checklists: Configuring OMEGAMON XE for OS/390 Using CICAT . . . . . 20Checklists: Configuring OMEGAMON XE for OS/390 Outside of CICAT . 27Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT. . 33Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Using Advanced Features in CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Start Here to Configure OMEGAMON XE for OS/390 15

Using the Checklists and Topics in this Chapter


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 “Overview of Processes, Methods, and CICAT Modes” on page 49.



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 and customization of OMEGAMON XE for OS/390

� Checklist: Prerequisites for Configuring OMEGAMON XE for OS/390

18

� Checklist: Starting CICAT and Accessing the Menu for Configuration

19

� Checklists: Configuring OMEGAMON XE for OS/390 Using CICAT

20

� Checklists: Configuring OMEGAMON XE for OS/390 Outside of CICAT 27

27

� Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT

33

� Using Advanced Features in CICAT 35

Update or change the configuration for OMEGAMON XE for OS/390

� Checklist: Starting CICAT and Accessing the Menu for Configuration

19

� Checklist: Updating the Configuration 34



Checklist: Prerequisites for Configuring OMEGAMON XE for OS/390

Checklist: Prerequisites for Configuring OMEGAMON XE for OS/390

Checklist: Prerequisites for configuring products The 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 and Configuration of Candle Products on OS/390 and z/OS

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

® Installation and 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 Management Server Configuration and Customization Guide


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

“Overview of Processes, Methods, and CICAT Modes” on page 49

� 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).

“Plan Your Configuration” on page 59


Checklist: Starting CICAT and Accessing the Menu for Configuration

Checklist: Starting CICAT and Accessing the Menu for Configuration

Checklist: Start CICAT and access the configuration 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. “Starting CICAT” on page 75

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

“Accessing the Menu for Configuring the Product” on page 76


Checklists: Configuring OMEGAMON XE for OS/390 Using CICAT


Background about the possible configurations The table lists the relationships of the CMS to the agent.

The table shows the possible configurations for the Candle Management Server (CMS) and OMEGAMON XE.

Candle Term Description of the Relationship

Local CMS that is installed in the same RTE 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)

How You Want to Configure the CMS and OMEGAMON XE

Type of CMS to Use

Installed and configured in the same address space Local

Installed and configured in different address spaces Local

Non-local



Determine the checklist to use for configuring productsThe table contains the possible configurations and indicates the location of the checklist for the configuration procedures in CICAT that you need to use.

Relationship of the CMS and OMEGAMON XE

Type of CMS to Use

Checklist to Use

Installed and configured in the same address space

Local CICAT configuration for OMEGAMON XE for OS/390: Same address space

Installed and configured in different address spaces

Local CICAT configuration for OMEGAMON XE for OS/390: Different address spaces and local CMS

Non-local CICAT configuration for OMEGAMON XE for OS/390: Different address spaces and non-local CMS



CICAT configuration for OMEGAMON XE for OS/390: Same address space

The following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE.

The steps are listed in the order they must be performed. Use the ✓column to check off steps as you complete them.

✓ Location in CICAT

Configuration Step to Perform in CICAT

Location of Information

� Configure OMEGAMON XE Menu

Use Register with local CMS to specify the CMS for OMEGAMON XE.

Online help in CICAT


Use Install Agent into local CMS to install the OMEGAMON XE for OS/390 agent into the same address space as the CMS.



If you want to archive the data collected so that you can retrieve it at a later date, use Configure persistent datastore to specify the values for the persistent data store (CT/PDS).



If you have not already configured a Candle Subsystem for another Candle product, use Install Candle Subsystem to specify the values.



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


� Runtime Environments (RTEs) panel

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




CICAT configuration for OMEGAMON XE for OS/390: Different address spaces and local CMS

The following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE.






Use Register with local CMS to specify the CMS for OMEGAMON XE.



Use Specify Agent address space parameters to:

� Specify the values for the address space and select the local CMS.

� If you want to specify advanced agent startup parameters, use the F5 (Advanced key) and specify advanced configuration options, such as:®enabling the secondary CMS®enabling Ephemeral Pipe support

� Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent to support.®If Ephemeral Pipe support is enabled,

IP.PIPE is required.



Use Create runtime members to generate the job that defines the address space and installs the agent into the address space.



If you want to archive data at the agent instead of at the CMS, use Configure persistent datastore to specify the values for the persistent data store (CT/PDS).





If you have not already configured a Candle Subsystem for another Candle product, use Install Candle Subsystem to specify the values.













CICAT configuration for OMEGAMON XE for OS/390: Different address spaces and non-local CMS

The following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE. The steps are listed in the order they must be performed. Use the ✓column to check off steps as you complete them.





Use Specify Agent address space parameters to:

� Specify the values for the address space and and if the CMS is in:®another RTE defined within this INSTLIB,

use F10 (CMS List) and select the non-local CMS from a list of CMSs

®a different INSTLIB or another platform, use F10 (CMS List) to select the CMS, and then use F5 (Advanced key) to specify values for the non-local CMS

� If you want to specify advanced agent startup parameters, use the F5 (Advanced key) and specify advanced configuration options, such as:®enabling the secondary CMS®enabling Ephemeral Pipe support

� Specify the communication protocols (SNA, IP, IP.PIPE) you want the agent to support.®If Ephemeral Pipe support is enabled,

IP.PIPE is required.



Use Create runtime members to generate the job that defines the address space and installs the agent into the address space.



If you want to archive data at the agent instead of at the CMS, use Configure persistent datastore to specify the values for the Persistent Datastore (PDS).




Determining what to do nextSee “Checklists: Configuring OMEGAMON XE for OS/390 Outside of CICAT” on page 27.











Checklists: Configuring OMEGAMON XE for OS/390 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 OMEGAMON XE menu also displays the manual steps you perform outside of CICAT to complete the configuration.

Determining the checklist to use The table contains the possible configurations and indicates the location of the checklist for the configuration procedures in CICAT that you need to use.

How You Configured the CMS and OMEGAMON XE

Type of CMS You Can Use

Checklist to Use

Installed and configured in the same address space

Local Outside configuration for OMEGAMON XE for OS/390: Same address space

Installed and configured in different address spaces

Local Outside configuration for OMEGAMON XE for OS/390: Different address space and local CMS

Non-local, but installed on OS/390

Outside configuration for OMEGAMON XE for OS/390: Different address space and non-local CMS



Outside configuration for OMEGAMON XE for OS/390: Same address space


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

Will Need

� If you did not have a Candle Subsystem configured and you are configuring the Candle Subsystem for the first time:

� Define the Candle Subsystem to OS/390.

� Update the link list library to APF-authorize the load module for the Candle Subsystem

� IPL the system to initialize the Candle Subsystem

“Completing the Configuration of the Candle Subsystem” on page 84

� If you chose to configure End-to-End Response Time Feature®, copy the procedure for the started task to the procedure library (PROCLIB).

“Copying the Procedures for the End-to-End Response Time Feature” on page 86

� If you configured the persistent data store (CT/PDS), copy the procedures for the CT/PDS).

“Copying the Procedures for the Persistent Datastore” on page 87

� Seed the CMS, if required. “Seeding the CMS” on page 88

� Verify the configuration:

� If you selected SNA as the communication protocol instead of TCP/IP, vary the node for the CMS active.

� Start the started task for the CMS.

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

� If you want to: ® Customize the product to meet the requirements at your

site, see Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT.

® Replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT.

Page 33

Page 35



Outside configuration for OMEGAMON XE for OS/390: Different address space and local CMS



Will Need

� Copy the procedure for the started task to the procedure library.

“Copying the Procedures for the Started Task” on page 82

� If you selected SNA as the communication protocol for the OMEGAMON XE agent, copy the VTAM definitions and vary the VTAM node active.

“Copying the VTAM Definition and Varying the VTAM Node Active” on page 83



� Update the link list library to APF-authorize the load module for the Candle Subsystem.

� IPL the system to initialize the Candle Subsystem.


� If you chose to configure End-to-End Response Time Feature, copy the procedure for the started task to the procedure library (PROCLIB).


� If you configured the persistent data store (CT/PDS), copy the procedures for the CT/PDS).





� Verify the configuration:

� Vary the CMS VTAM major node active.


� Start the started task for the agent.

� Access the product in the CandleNet Command Center® (CCC) interface and display data.

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




Page 33

Page 35


Will Need



Outside configuration for OMEGAMON XE for OS/390: Different address space and non-local CMS



Will Need

� Copy the procedure for the started task to the procedure library.

“Copying the Procedures for the Started Task” on page 82

� If you selected SNA as the communication protocol for the OMEGAMON XE agent, copy the VTAM definitions and vary the VTAM node active.

“Copying the VTAM Definition and Varying the VTAM Node Active” on page 83



� Update the link list library to APF-authorize the load module for the Candle Subsystem.

� IPL the system to initialize the Candle Subsystem.


� If you chose to configure End-to-End Response Time Feature, copy the procedure for the started task to the procedure library (PROCLIB).


� If you configured the persistent data store (CT/PDS), copy the procedures for the CT/PDS.





� If the non-local CMS is installed on MVS, complete the configuration:

� Select the RTE that contains the non-local CMS.

� Register with the local CMS in that RTE.

� Load the libraries for the RTE with the non-local CMS.

If the non-local CMS is installed on a platform other than MVS, complete the configuration on that platform.

“Completing the Configuration for a Non-local CMS” on page 93

Installation guide for that platform

� If the non-local CMS is installed on MVS, verify the configuration as follows:

� Vary the CMS VTAM major node active.


� Start the started task for the components you configured.

� Access the product in the CCC interface and display data.

If the non-local CMS is installed on a platform other than MVS, verify the configuration as follows:

� On the platform where the CMS is installed, start the CMS.

� Start the started task for the components you configured.

� Access the product in the CCC interface and display data.

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

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




Page 33

Page 35


Will Need


Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT

Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT

Outside customization for OMEGAMON XE for OS/390The steps listed in the following checklist for customization are optional. The checklist contains only steps you perform to customize the product for your site and are not required to make the product operational.


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

Will Need

� If you want to use the thresholds from your OMEGAMON II for MVS profile, migrate your profile to OMEGAMON XE .

“Migrating Your Profile” on page 102

� Specify security for the agent. “Specifying Security” on page 106

� Collect and store historical data that you can later use with reporting tools.

“Collecting and Storing Historical Data” on page 107

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

Page 35


Checklist: Updating the Configuration


Updating and changing 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.


✓ 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).

“Managing and Updating the Configuration” on page 109

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

Page 35


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





Start Here to ConfigureOMEGAMON XE for Sysplex2

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. . . . . . . . . . . . . . . . . . . . . 38Checklist: Prerequisites for Configuring OMEGAMON XE for Sysplex. . . . 40Checklist: Starting CICAT and Accessing the Menu for Configuring

OMEGAMON XE for Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . 41Checklists: Configuring OMEGAMON XE for Sysplex Using CICAT . . . . . 42Checklist: Configuring OMEGAMON XE for Sysplex Outside of CICAT . . 44Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT . . 46Checklist: Updating the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Using Advanced Features in CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Start Here to Configure OMEGAMON XE for Sysplex 37



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 “Overview of Processes, Methods, and CICAT Modes” on page 49.



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 and customization of OMEGAMON XE for Sysplex

� Checklist: Prerequisites for Configuring OMEGAMON XE for Sysplex

40

� Checklist: Starting CICAT and Accessing the Menu for Configuring OMEGAMON XE for Sysplex

41

� Checklists: Configuring OMEGAMON XE for Sysplex Using CICAT

42

� Checklist: Configuring OMEGAMON XE for Sysplex Outside of CICAT

44

� Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT

46


Update or change the configuration for OMEGAMON XE for Sysplex

� Checklist: Starting CICAT and Accessing the Menu for Configuring OMEGAMON XE for Sysplex

41

� Checklist: Updating the Configuration 47



Checklist: Prerequisites for Configuring OMEGAMON XE for Sysplex

Checklist: Prerequisites for Configuring OMEGAMON XE for Sysplex

Checklist: Prerequisites for configuring products The 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


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

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


� You must have created a runtime environment (RTE) using CICAT.

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

® Candle Management Server Configuration and Customization Guide


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

“Overview of Processes, Methods, and CICAT Modes” on page 49

� 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).

“Plan Your Configuration” on page 59


Checklist: Starting CICAT and Accessing the Menu for Configuring OMEGAMON XE for Sys-

Checklist: Starting CICAT and Accessing the Menu for Configuring OMEGAMON XE for Sysplex

Checklist: Start CICAT and access the configuration 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. “Starting CICAT” on page 75

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

“Accessing the Menu for Configuring the Product” on page 76


Checklists: Configuring OMEGAMON XE for Sysplex Using CICAT


CICAT configuration for OMEGAMON XE for SysplexThe following checklist contains the steps you perform in CICAT to begin to configure OMEGAMON XE.






Use Define Enterprise wide ENQ manager to specify the name and description for the ENQplex.



Use Define your Sysplex environment to specify the names of the sysplexes and the names of the ENQplex to which they are assigned.



Use Assign this RTE to a Sysplex to: ® select the Sysplex where this RTE will

run ® specify whether the CMS for the

Sysplex is eligible to be a Sysplex Proxy CMS



Use Register with local CMS to specify the CMS for OMEGAMON XE for Sysplex.



If you want to archive the data collected so that you can retrieve it at a later date, use Configure persistent datastore to specify the values for the Persistent Datastore (PDS).




Determining what to do nextSee “Checklist: Configuring OMEGAMON XE for Sysplex Outside of CICAT” on page 44.











Checklist: Configuring OMEGAMON XE for Sysplex 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 OMEGAMON XE menu also displays the manual steps you perform outside of CICAT to complete the configuration.

Outside configuration for OMEGAMON XE for SysplexThe steps are listed in the order they must be performed. Use the ✓column to check off steps as you complete them.


Will Need

� If you configured the Persistent Datastore, copy the procedures for the Persistent Datastore.



� Verify the configuration by:

� varying the CMS VTAM major node active

� starting the started task for the CMS

� starting the started task for the agent

� accessing the product in the CandleNet Command Center® (CCC) interface and displaying data

“Verifying the Configuration” on page 97



� If you want to: ® customize the product to meet the requirements at your

site, see Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT

® replicate the product or use the product on another MVS image, see Using Advanced Features in CICAT

Page 46

Page 48


Will Need


Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT

Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT

Outside customization for OMEGAMON XE for SysplexThe steps listed in the following checklist for customization are optional. The checklist contains only steps you perform to customize the product for your site and are not required to make the product operational.


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

Will Need

� Specify security for the agent. “Specifying Security” on page 106

� Collect and store historical data that you can later use with reporting tools.

“Collecting and storing historical data” on page 107

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

Page 48




Updating and changing 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.


✓ 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)

“Managing and Updating the Configuration” on page 109

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

Page 48




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

Modes3
Overview
Review this chapter only if you are not familiar with Candle or the process for installing and configuring Candle products.

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 50Candle Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Processes for Installing, Configuring, and Maintaining Products . . . . . . . . 52Background about CICAT Modes: Interactive and Batch . . . . . . . . . . . . . 57

Overview of Processes, Methods, and CICAT Modes 49

Determining the Topics to Use in this Chapter


This 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

4
Overview
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 . . . . . . . . . . . . . . . . . . . . . 60Candle Products and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Details about the Candle Products and Components . . . . . . . . . . . . . . . . 64Determining the Components to Install and Configure . . . . . . . . . . . . . . . 66Additional Terminology and An Example Configuration for OMEGAMON XE for Sysplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Requirements and Restrictions for OMEGAMON XE . . . . . . . . . . . . . . . . 72

Plan Your Configuration 59



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” on page 21.

Determining 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 topic is required. The O indicates the topic is optional.

Page Numbers for Topics

61 64 66 70 72

Determine the products and components to configure and determine whether or not the products and components have manual steps that you must perform outside of CICAT

O

Review additional terminology and an example configuration for OMEGAMON XE for Sysplex

O

Review details provided for some of the products and components

O

Review information about Candle products and components

O

Review the requirements and restrictions for the products R


Candle Products and Components


Background about how CICAT installs products and components When you use CICAT, 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 the products and components The following table shows all the product and components available with the Candle products that monitor MVS.

Table 8. Overview of the Products and Components

Component Name or Category Purpose

Platform(s) for Product or Component

Candle Command Center 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 CandleNet Portal™ (CNP) that communicates with the CMS (The interface can be run in desktop or browser mode.)

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

® Windows NT (Intel-based)

® Windows 98® Windows 2000



OMEGAMON XE

Component that monitors systems, subsystems, and applications on the system where they are installed. OMEGAMON XE: ® collects data and monitors performance ® provide data and performance information to

the CMS ® receive instructions from the CMS ® issue commands to the system or application

you are monitoring Components that provide data to a CCC interface include: ® OMEGAMON XE (Collect performance and

analysis data.)® Agents (Collect performance and analysis

data.)® Alert Adapters (Monitors alerts and relay the

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

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

® Gateways (Communicate events to a management application running on a supported platform using a network service.)

Platform appropriate for the system or software being monitored

Candle Management Server (CMS)

Component that: ® consolidates the data collected by the agent

and distributes the data to the CCC interface ® in some cases, receives commands from the

CCC interface and distributes them to the appropriate agent

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

® Windows NT (Intel-based)

® Windows 98® Windows 2000® MVS ® UNIX





Candle Subsystem

Component that is an MVS subsystem that runs in its own address space that provides Coupling Facility and dynamic I/O activity to:® OMEGAMON II® OMEGAMON XE

MVS

End-to-End Response Time Feature

Component that collects response time data and reports the data to: ® OMEGAMON II® OMEGAMON XE

MVS

EPILOG for MVS Collector

One of the two components for the Persistent Datastore that gathers and reports historical data

MVS

OMEGAMON II Component that collects and displays data in the OMEGAMON II user interface(s).

MVS

Persistent Datastore (PDS)

Component that records and stores historical data MVS




Details about the Candle Products and Components


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

Table 9. Details about the Relationships and Types of CMSs

Relationship Candle Term

Description

CMS to CMS relationship

Hub CMS that:® receives data from agents and Remote CMSs in the

environment ® communicates data and receives command from an

interface

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

communicate directly with an interface.)

CMS to OMEGAMON XE relationship (OMEGAMON XE for OS/390 only)

Local CMS that is installed in the same RTE 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 OS/390OMEGAMON XE for OS/390 is an agent based product that you can use to monitor the performance of MVS. The data collected by OMEGAMON XE for OS/390 can then be displayed using CandleNet Portal™.

For example, you can use OMEGAMON XE to monitor the performance of:

® address spaces ® channel path activity ® system paging activity ® CPU utilization

Details about OMEGAMON XE for SysplexOMEGAMON XE for Sysplex is a product that you can use to monitor the performance of MVS. The data collected by OMEGAMON XE for Sysplex can then be displayed using:

® CandleNet Portal® Candle Management Workstation®

® OMEGAVIEWFor example, you can use OMEGAMON XE for Sysplex to monitor the performance of:

® coupling facility systems ® global enqueues® shared DASD® performance of workloads


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.

Determining the products and components you will needThe following table shows the products and components available with the products. The table also indicates:

® which products use the components and whether or not they 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)

® if you decide to use the product and components, the order the products and components are configured

Table 10. Determining the Products and Components You Will Need

Component Name or Category O

ME

GA

MO

N X

Efo

r O

S/3

90

OM

EG

AM

ON

XE

for

Sys

ple

x

Can be Shared?

Additional Information (If Any)

Candle Management Server (CMS)

R R Y



OMEGAMON II O R N If you do not configure this component, service class periods data will not be displayed in the reports and workspaces.

Candle Subsystem O R Y Candle recommends that you use one Candle Subsystem for all the Candle products and components you install and configure.

End-to-End Response Time Feature

O O Y If you do not configure this component, data for user response times will not be displayed in the reports and workspaces.

EPILOG for MVS Collector

O N

OMEGAMON XE R R Y

Persistent Datastore (PDS)

O O Y ® For OMEGAMON XE for OS/390, you can configure the PDS with the CMS and/or the agent.

® For OMEGAMON XE for Sysplex, this component must be configured with the CMS.

Candle Command Center interface

R R Y

Component Name or Category O

ME

GA

MO

N X

Efo

r O

S/3

90

OM

EG

AM

ON

XE

for

Sys

ple

x

Can be Shared?

Additional Information (If Any)



Determining 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 are configured.

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

OMEGAMON II Y N

End-to-End Response Time Feature Y Y

EPILOG for MVS Collector Y N

Candle Subsystem Y Y

OMEGAMON XE Y Y

Persistent Datastore (PDS) Y Y

Candle Command Center interface N N/A



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

The products and components are listed in the order they are configured.

Table 12. Locating 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

Candle Subsystem Configuration and Customization Guide for OMEGAMON II

End-to-End Response Time Feature Configuration and Customization Guide for OMEGAMON II

OMEGAMON XE This guide

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

Candle Command Center interface Installing Candle Products on Windows


Additional Terminology and An Example Configuration for OMEGAMON XE for Sysplex


Additional terminology for OMEGAMON XE for SysplexThe following table lists the additional terminology for CMSs for OMEGAMON XE for Sysplex and provides a description.

Table 13. Additional Terminology for CMSs for OMEGAMON XE for Sysplex

Candle Term Description

Sysplex Proxy CMS

Within a single Sysplex, a CMS that: ® collects data from the backup CMSs ® sends a summary of the data for that Sysplex to the hub CMS so that

reports that show an overview for all the Sysplexes in the group can be created by the interface

® monitors situations that apply to the entire Sysplex If you have designated a CMS to be the Sysplex Proxy CMS for a Sysplex and the CMS is not available, the Hub CMS will use the first backup CMS available.

Backup CMS Within a single Sysplex, a CMS that: ® collects data ® sends the data to the Sysplex Proxy CMS ® unless otherwise specified, is used as the Sysplex Proxy CMS when the

designated Sysplex Proxy CMS is not available



Illustration showing an example configuration The illustration shows an example configuration for an environment with the following characteristics:

® six MVS images

® two Sysplexes each with for 3 of the MVS images

® one CMS on each of the MVS images

® one Hub CMS and five Remote CMSs

FIGURE 1. Illustration of An Example Configuration for OMEGAMON XE for Sysplex

Hub CMS for that is Sysplex Proxy CMS for

Remote CMS that is Backup CMS for Sysplex A

Remote CMS that is Backup CMS for Sysplex A

MVS Image 1

MVS Image 2 MVS Image 3

Remote CMS that is Sysplex Proxy CMS for Sysplex B

MVS Image 4

Remote CMS that is Backup CMS for Sysplex B

MVS Image 5 MVS Image 6

Remote CMS that is Backup CMS for Sysplex B

Sysplex A Sysplex B

CCC

Interface

Sysplex A


Requirements and Restrictions for OMEGAMON XE

Requirements and Restrictions for OMEGAMON XE

Requirements and restrictionsThe OMEGAMON XE products have the following requirements and restrictions.

® If you install either OMEGAMON XE for OS/390 Version 100, Version 120, or Version 140 in the same CSI as OMEGAMON II for MVS, OMEGAMON II for MVS must be Version 520. (If the CSI contains Version 500, CICAT will require you to upgrade to Version 520.)

® If you install either OMEGAMON XE for OS/390 Version 100, Version 120, or Version 140 in the same CSI as OMEGAMON XE for Sysplex, OMEGAMON XE for Sysplex must be Version 220.

® If either OMEGAMON XE for OS/390 Version 100, Version 120, or Version 140 uses the same Hub CMS as OMEGAMON XE for Sysplex, OMEGAMON XE for Sysplex must be Version 220.

® The names for the sysplexes must be unique.


Start CICAT and Access theMenu for Configuring5

OverviewThis 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. . . . . . . . . . . . . . . . . . . . . . . 74Starting CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Accessing the Menu for Configuring the Product. . . . . . . . . . . . . . . . . . . . 76Using CICAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

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.

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

Start CICAT and Access the Menu for Configuring 73

Determining 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 the topic is required. The O indicates the topic is optional.


75 76 77

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


Completing the Configuration

6
Introduction
This chapter contains:

® the manual steps you must perform outside of CICAT to complete the configuration of your OMEGAMON XE product

® the procedure to follow to verify the configuration of your OMEGAMON XE product

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . . 80Copying the Procedures for the Started Task. . . . . . . . . . . . . . . . . . . . . . . 82Copying the VTAM Definition and Varying the VTAM Node Active . . . . . 83Completing the Configuration of the Candle Subsystem . . . . . . . . . . . . . . 84Copying the Procedures for the End-to-End Response Time Feature . . . . 86Copying the Procedures for the Persistent Datastore . . . . . . . . . . . . . . . . . 87Seeding the CMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Completing the Configuration for a Non-local CMS . . . . . . . . . . . . . . . . . 93Verifying the Configuration: Same Address Space . . . . . . . . . . . . . . . . . . 94Verifying the Configuration: Different Address Space . . . . . . . . . . . . . . . . 95Verifying the Configuration: CMS on a Different Platform. . . . . . . . . . . . . 96Verifying the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Completing the Configuration 79




This chapter contains topics that correspond to the tasks in the following checklists:

® For OMEGAMON XE for OS/390, Checklists: Configuring OMEGAMON XE for OS/390 Using CICAT.

® For OMEGAMON XE for Sysplex, Checklists: Configuring OMEGAMON XE for Sysplex Using CICAT.

Determining the topics to use in this chapter for OMEGAMON XE for OS/390

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.

In some cases, a task does not need to be completed if a component is not configured using CICAT. The R indicates that you must review the topic to determine whether or not it is required.


82 83 84 86 87 91 93 94 95 96

OMEGAMON XE for OS/390 and the CMS are installed and configured in the same address space

R R R R R

OMEGAMON XE for OS/390 and the CMS are installed in different address spaces and the CMS is a local CMS

R R R R R R R R

OMEGAMON XE for OS/390 and the CMS are installed in different address spaces and the CMS is a non-local CMS

R R R R R R R R



Determining the topics to use in this chapter for OMEGAMON XE for Sysplex

In some cases, a task does not need to be completed if a component is not configured using CICAT. Review the following topics to determine whether or not it is required.

® “Copying the Procedures for the Persistent Datastore” on page 87

® “Seeding the CMS” on page 88

® “Verifying the Configuration” on page 97


Copying the Procedures for the Started Task

Copying the Procedures for the Started Task

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 Definition and Varying the VTAM Node Active

Copying the VTAM Definition 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


Completing the Configuration of the Candle Subsystem


Defining the Candle Subsystem to OS/390You must update SYS1.PARMLIB(IEFSSNcc) to define the Candle Subsystem to OS/390. Use the table to determine the method to use.

Table 14. Methods for Defining the Candle Subsystem to OS/390

Method You Want to Use

Action to Perform Additional Information

Update the member by adding statements

In SYS1.PARMLIB(IEFSSNcc), specify one these statements. ® subsystemID, KCNDLINT® subsystemID,KCNDLINT,

‘SSPROC=procedurename’For example, if you are using the default subsystem ID CNDL and the default procedure CANSCN, you would specify one of these statements. ® CNDL,KCNDLINT ® CNDL,KCNDLINT,’SSPROC=CANSCN’

The subsystem ID and the procedure name must be unique. You cannot use the same name for both.

Copy the sample statements provided by CICAT

Copy the sample statements from rhilev.midlev.RKANSAM(KCNDLSSI) to SYS1.PARMLIB(IEFSSNcc)

The subsystem ID and the procedure name must be unique. You cannot use the same name for both.

The sample statements also automatically start the Candle Subsystem.



Updating the link list libraryIf you want the Candle Subsystem to be available when you IPL the system, you must make the KCNDLINT load module available in an APF-authorized link list library.

IPL the system to initialize the Candle Subsystem You must IPL the system to initialize the Candle Subsystem in these cases.

® You do not have a Candle Subsystem installed and this is the first time you have installed the Candle Subsystem.

® You have applied maintenance to an existing Candle Subsystem.

After you IPL the system, the following messages should appear in the SYSLOG.

® CNDL184I (indicating that the Candle Subsystem has been initialized)

® CNDL001I, CNDL190I, CNDL034I, and CNDL027I (indicating that the Candle Subsystem has started either automatically or by using the START command)

Method You Want to Use

Action to Perform

Add the library to the OS/390 link list

Add the rhilev.midlev.RKANMOD data set to the OS/390 link list

Copy the load module

Copy rhilev.midlev.RKANMOD(KCNDLINT) to an APF-authorized link list library


Copying the Procedures for the End-to-End Response Time Feature

Copying the Procedures for the End-to-End Response Time Feature

Background about the procedures for the End-to-End Response Time Feature

The End-to-End Response Time Feature collects response time data.

When you install and configure the End-to-End Response Time Feature using CICAT, CICAT creates the procedures for the End-to-End Response Time Feature.

If you decided to configure the End-to-End Response Time Feature, you must copy these procedures to your procedure library (PROCLIB) to complete the configuration.

Copying the procedures to your procedure library If you configured the End-to-End Response Time Feature, you must copy the procedure from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

The procedure name is the started task name you specified for the End-to-End Response Time Feature using CICAT.


Copying the Procedures for the Persistent Datastore

Copying the Procedures for the Persistent Datastore

Background about the procedures for the persistent data storeThe persistent data store (CT/PDS) is used to store the data for historical collection.

When you install and configure the CT/PDS using CICAT, CICAT creates the procedures for the CT/PDS.

If you decided to configure the CT/PDS, you must copy these procedures to your procedure library (PROCLIB) to complete the configuration.

Copy the procedures to your procedure library If you configured the CT/PDS, you must copy the following procedures from rhilev.midlev.RKANSAM to your procedure library (PROCLIB).

® pdsmprefix1

® pdsmprefix2

The value for pdsmprefix is the unique prefix you specified for the maintenance procedure using CICAT. The default is KPDPROC.


Seeding the CMS

Seeding the CMS

Background about seeding the CMS When you seed the CMS, you provide the CMS with product-specific information that the CMS uses:

® for product-provided solutions (such as predefined situations and policies)

® to build reports and the Topology view

Background about the guidelines for seeding the CMS The guidelines you follow to seed the CMS depend on the platform for the product. These platforms include:

® distributed platforms (such as UNIX and Windows)

® MVS

Guidelines for seeding the CMS for products on distributed platformsFollow these guidelines when seeding the Candle Management Servers for products on distributed platforms.

® Seed all the Candle Management Servers the product communicates with in your environment using Manage Candle Services.

® If the product is on UNIX, seed the CMS using Manage Candle Services as well as the seeding process provided on UNIX when you install the product.

® If the product communicates with remote Candle Management Servers, seed the hub Candle Management Server the remote Candle Management Servers communicate with in your environment using Manage Candle Services.

® If the product communicates with a CMS on MVS, you must also install product-specific solutions in the CMS using CICAT.


Seeding the CMS

Guidelines for seeding the CMS for products on MVS The guidelines for seeding the CMS for products on MVS vary depending on the product.

Review the following table to determine the guidelines to follow for your product(s). The table has the following organization.

® The first column contains the guideline.

® The second column contains the products and the versions of the products that follow the guideline.

® The third column contains additional information (if any).

If your product or the version of your product is not listed in the second column, do not follow the guideline.

Table 15. Guidelines for Seeding the CMS for Products on MVS

Guideline Products and Product Versions That Follow the Guideline Additional Information

Seed the remote Candle Management Servers and the hub Candle Management Server on MVS using Manage Candle Services

OMEGAMON XE for CICS V100

OMEGAMON XE for CICSplex V220 (see Migration Considerations)

OMEGAMON XE for DB2 V100

OMEGAMON XE for DB2plex V220

OMEGAMON XE for IMS V100

OMEGAMON XE for OS/390 V120 or higher

OMEGAMON XE for Mainframe Networks V100

OMEGAMON XE for Storage V100

OMEGAMON XE for WebSphere MQ Monitoring V360

The products not included in this list are seeded automatically by CICAT when the product is registered with the CMS during configuration.

Seed the hub Candle Management Server on distributed platforms using Manage Candle Services

All products and versions of products


Seeding the CMS

Seed the remote Candle Management Servers on distributed platforms using Manage Candle Services

Alert Adapter for OMEGACENTER Gateway V150

OMEGAMON XE for CICS V100

OMEGAMON XE for CICSplex V220

OMEGAMON XE for DB2 V100

OMEGAMON XE for DB2plex V220

OMEGAMON XE for IBM Cryptographic Coprocessors V100

OMEGAMON XE for Mainframe Networks V100

OMEGAMON XE for OS/390 V120 or higher

OMEGAMON XE for Storage V100

OMEGAMON XE for Unix System Services V220

OMEGAMON XE for WebSphere Application Server V120

OMEGAMON XE for WebSphere Integration Brokers V120

OMEGAMON XE for WebSphere MQ Configuration V360

OMEGAMON XE for WebSphere MQ Monitoring V360

The products not included in this list are seeded automatically by CICAT when the product is registered with the CMS during configuration.

Table 15. Guidelines for Seeding the CMS for Products on MVS

Guideline Products and Product Versions That Follow the Guideline Additional Information


Seeding the CMS

Locating the information you will need The following table lists the tasks for seeding the CMS and the locations where you can find detailed information about seeding the CMS.

Prerequisites for seeding the CMS for products on MVSBefore seeding the CMS, verify that:

® the MVS products are installed and available with CandleNet Portal

® the same versions of the MVS products are installed and available with CandleNet Portal

Also verify that the image you used to install CandleNet Portal is compatible with the products you installed and configured using tape or Candle eDelivery.

For example, if you received a product package containing tapes and a CD image, verify that an older or newer CD image of CandleNet Portal has not been installed on the workstation you will be using to seed the CMS. If you have any question about whether or not they are compatible, contact Candle Customer Service and Satisfaction.

Task You Want to Perform Location of the Information You Will Need

For Candle Management Servers on distributed platforms, seeding the CMS

The topics on seeding the CMS in the Installation Guide for that platform

For Candle Management Servers on MVS, seeding the CMS on MVS

The topics on seeding the CMS in the:product-specific Configuration and Customization Guide (if applicable) Candle Management Server on OS/390 and z/OS Configuration and Customization Guide

For distributed products that communicate with a CMS on MVS, installing product-specific solutions

The topics on registering distributed products in the Candle Management Server on OS/390 and z/OS Configuration and Customization Guide


Seeding the CMS

Seeding the CMS using Manage Candle Services Follow these steps to seed the CMS using Manage Candle Services:

1. On the workstation where you installed the CandleNet Portal Server, select Start > Programs > Candle OMEGAMON® XE >Manage Candle Services.

2. In the Manage Candle Services window, select Actions >Advanced > Seed CMS.

3. On the Seed CMS dialog, select On a different computer and click OK.Result: The Manage Candle Services dialog appears. Confirm that the CMS to be seeded is running and click OK.

4. On the Non-resident CMS Connection dialog(s), specify the appropriate values and click the OK button.

5. On the Select Product to Seed dialog, select the products you have installed and click the OK button. Result: Manage Candle Services seeds the CMS and displays the Seed Data Operation Complete dialog box indicating whether or not the seeding completed successfully.


Completing the Configuration for a Non-local CMS

Completing the Configuration for a Non-local CMS

Completing the configuration: non-local CMS on MVS If you are completing the configuration for a non-local Candle Management Server (CMS) that is installed on MVS, you must complete the steps listed in this table to register with the non-local CMS on MVS.

Completing the configuration: non-local CMS on a platform other than MVS

If the CMS is installed on a platform other than MVS, see the Installation Guide for that platform.

Step Action

1 Perform the appropriate action. ® If the CMS is installed and configured in a different RTE in the same

CSI, return to the Runtime Environments (RTEs) panel.® If the CMS is installed and configured in a different CSI, access CICAT

in that CSI and access the Runtime Environments (RTEs) panel.

2 On the Runtime Environments (RTEs) panel, use the C (Configure) action code to select the RTE where the non-local CMS is installed and configured.

3 On the Product Configuration Selection Menu, select the product.

4 On the Configure OMEGAMON XE Menu, select Register with local CMS.

5 On the Runtime Environments (RTEs) panel, use the L (Load libs after SMP/E) to load the target libraries to the runtime libraries for the RTE.


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 2. 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 3. 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.


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





® you installed the agent on MVS

® the CMS in installed on a different platform

FIGURE 4. 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.


Verifying the Configuration





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.

FIGURE 5. Process for Verifying the Configuration

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

.


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




Completing the Customization

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

Chapter contentsDetermining the Topics to Use in this Chapter . . . . . . . . . . . . . . . . . . . . 100Migrating Your Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Specifying Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Collecting and storing historical data . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Completing the Customization 99




This chapter contains topics that correspond to the tasks in the following checklists:

For OMEGAMON XE for OS/390, “Checklist: Customizing OMEGAMON XE for OS/390 Outside of CICAT” on page 33.

For OMEGAMON XE for Sysplex, “Checklist: Customizing OMEGAMON XE for Sysplex Outside of CICAT” on page 46.

Determining the topics to use in this chapter for OMEGAMON XE for OS/390

The tasks listed in the following table for customization are optional. The table contains only steps you perform to customize the product for your site and are not required to make the product operational.

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 O indicates the tasks in the topic are optional.


102 106 107

Collect and store historical data that you can later use with reporting tools

O

Migrate your existing OMEGAMON II profile so that the thresholds in the profile can be used as predefined situations in OMEGAMON XE

O

Specify security for the product O



Determining the topics to use in this chapter for OMEGAMON XE for Sysplex

The tasks listed in the following table for customization are optional. The table contains only steps you perform to customize the product for your site and are not required to make the product operational.

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 O indicates the tasks in the topic are optional.


106 107

Collect and store historical data that you can later use with reporting tools O

Specify security for the product O


Migrating Your Profile


Background about migrating your profile CandleNet Portal provides a utility that you can use to migrate your existing OMEGAMON II profile so that the thresholds in the profile can be used as predefined situations in OMEGAMON XE.

Prerequisites for migrating your profile You must have CandleNet Portal installed on your workstation to access the utility. (The utility you use to migrate your existing OMEGAMON II profile is provided with CandleNet Portal.)

Overview of the process of migrating your profile The illustration shows the process for migrating your existing OMEGAMON II profile so that the thresholds in the profile can be used as predefined situations in OMEGAMON XE.

FIGURE 6. Process for Migrating Your OMEGAMON II Profile

.

Prepare the profile to be migrated by exporting and transferring the profile to the workstation where you have CandleNet Portal installed.

.

On the workstation, run the utility to create the equivalent predefined situations.

.

Make the predefined situations available by seeding the situations with the Candle Management Server (CMS).



Preparing the profile for migrationPerform the following steps to prepare the profile to be migrated.

Migrating the profile using the command for utility Once you have prepared the profile for migration, follow this procedure to migrate the profile using the command for the utility.

The following table:

® lists the parameters available with the KXEMIGR command

® indicates whether or not the parameter is required (Parameters with default values are optional.)

® provides a description of the purpose of the parameter

Step Action

1 Export the file that contains the profile.

2 Using a program that transfers files, transfer the file that contains the profile to the workstation where CandleNet Portal is installed.

3 On the workstation, copy the file to drive:\Candle\CNPS.

For example, if you have installed CandleNet Portal on your c: drive, you would copy the file to the c:\Candle\CNPS directory.

Step Action

1 On the workstation, open a DOS session.

2 Change the directory in the DOS session to drive:\Candle\CNPS.

3 At the prompt, specify the following command.

KXEMIGR <options> profile pp <outfile> <ctl>

Result: The utility creates the file that contains the migrated profile, the control file, and the log (if any).



Table 16. Parameters You Can Use with the Command to Migrate Your Profile

Parameter Required? Purpose

profile Yes Specifies the name of the file that you exported that contains the profile.

pp Yes Specifies the product code.

outfile No Specifies the name of the file that will contain the migrated profile. The default is Kpp_UPD.SQL (where pp is the 2 character product code).

ctl No Specifies the name of the product control file. The default is KppPROD.txt (where pp is the 2 character product code).

options No Specifies the following option. ® To display diagnostic messages for the utility, specify

-v. ® To display help, specify -?. ® To migrate predefined situations with the status of

critical and exclude the migration of situtations with a status of warning, specify -nw.



Completing the migration by seeding the file with the CMS For the predefined situations to be available to CandleNet Portal, you must seed the predefined situations with the CMS. Follow this procedure to seed the predefined situations with the CMS.

Step Action

1 On the workstation, select the Start command.

2 On the Start menu, select the Programs command.

3 On the Programs menu, select the command for Candle products.

4 On the menu, select the Manage Candle Services command.

Result: The program displays the Manage Candle Services dialog.

5 On the Action menu, select the Advanced command.

6 On the Advanced menu, select the Seed CMS command.

Result: The program displays the Seed CMS dialog.

7 On the Seed CMS dialog, specify the options you want.

For a CMS on your workstation, select the On this computer radio button and the Monitoring and automation definitions check box.

For a CMS installed on a different computer, select the On a different computer radio button and the Monitoring and automation definitions check box.

Result: The program displays the Select Product to Seed CMS dialog.

8 On the Select Product to Seed CMS dialog, select the migration data for OMEGAMON XE for OS/390.

9 Select the OK button.

Result: The program seeds the CMS and saves any messages or errors in the log file.


Specifying Security

Specifying Security

Specifying security Security for OMEGAMON XE is controlled using the Candle Management Workstation® (CMW). For example, user access and user authorities are granted using the CMW.

For information about specifying security, see the Administering OMEGAMON Products: CandleNet Portal.


Collecting and Storing Historical Data


Collecting and storing historical data You can customize OMEGAMON XE to collect and store historical data. You can then use:

® a CandleNet Command Center® interface to display short term history

® a reporting tool to display the long term history stored using one of the available methods

For information about collecting and storing historical data, see the Historical Data Collection Guide for OMEGAMON XE and CandleNet Command Center.




Managing and Updating theConfiguration8

IntroductionThis chapter contains information about updating and changing your configuration.

Chapter contentsUpdating and Changing the Configuration . . . . . . . . . . . . . . . . . . . . . . . 110

Managing and Updating the Configuration 109

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

110 OMEGAMON XE for OS/390 OMEGAMON XE for Sysplex CCG

Index

definition 65

AAbout 12accessing

menu for configuring 19, 41, 76accessing the menu

checklist 19, 41Adobe portable document format 13advanced features 35, 48Advanced key 78agent

65

Bbatch mode processing 35, 48, 57

CCandle Installation and Configuration

Assistance Tool (CICAT) 51Candle Subsystem

defining to OS/390 84IPL to initialize 85updating the link list library 85

Candle terminology 51CandleNet Portal

definition 65changing the configuration 110checklists 15, 37, 38CICAT

accessing the menu for configuring 76commands 73, 78defaults 77definition 51displaying information in 78functions 78modes 57

release 75restrictions 77starting 75version 75

CMSconfiguring for non-local 93seeding for migrated profiles 105

CNDL001I 85CNDL027I 85CNDL034I 85CNDL184I 85CNDL190I 85components 51

definition of shared 61configuring

definition 51migrating your profile 103prerequisites 18, 40updating or changing 110

creating a new RTE 76cumulative maintenance 51customizing

definition 51detailed procedures 99

Ddefaults provided with CICAT 77displaying information in CICAT 78

Eedit recovery 77End key 78Enter key 78

Gglobal VTAM major node 83

Index 111

HHELP command 77, 78

IIEFSSNcc 84installing

definition 51interactive mode 57invoking ISPF 75ISPF display requirements 77

KKCNDLINT 84, 85KXEMIGR command and parameters 103

Mmenu for configuring 76migrating 51modes in CICAT 57

Nnon-local CMS

definition 93

PPDF files, adding annotations 14PFSHOW command 77predefined situations

migrating existing profiles 105preventive maintenance

definition 51printing problems 13procedures

copying for the Persistent Datastore 86copying for the persistent datastore 87copying for the started tasks 82

processesconfiguring products 53installing maintenance 52installing products 52

PROCLIB

Persistent Datastore 86persistent datastore 87started tasks 82

profile migration 102

RREADME APP command 78README command 78README ERR command 78README SYS command 78RECOVERY OFF command 77RECOVERY ON command 77restrictions in CICAT 77RKANSAM(KCNDLSSI) 84RTE 51Runtime Environments (RTEs) 51

Ssecurity

specifying 106seeding the CMS 88

background 88guidelines for products on distributed

platforms 88guidelines for products on MVS 89prerequisites for seeding products on

MVS 91using Manage Candle Services 92

specifying security 106started tasks

copying procedures 82starting CICAT 19, 41, 75SYS1.PARMLIB(IEFSSNcc) 84SYSLOG 85system variable support 35, 48

Tterminology 51

Uupdating


detailed procedures 109the configuration 110

usingchecklists in this guide 38

using an existing RTE 76UTIL command 78

VVTAMLST

copying the VTAM definition 83

Index 113


Date post:	06-Oct-2020
Category:	Documents
Upload:	others
View:	10 times
Download:	0 times

Configuration and Customization...

Documents