configuration and customization...

Configuration and Customization GuideOMEGAMON II for VTAM

Version 500

GC32-9285-00

April 2000

Candle Corporation201 North Douglas Street

El Segundo, California 90245

Registered trademarks and service marks of Candle Corporation: AF/OPERATOR, AF/PERFORMER,AF/REMOTE, Availability Command Center, Candle Command Center, Candle Electronic Customer Support,Candle Logo, Candle Management Server, Candle Management Workstation, Candle Technologies,CL/CONFERENCE, CL/SUPERSESSION, CT, CT/Data Server, CT/DS, DB Logo, DB/QUICKCHANGE,DELTAMON, ETEWatch, IntelliWatch, MQSecure, MQView, OMEGACENTER, OMEGAMON, OMEGAMON/e,OMEGAMON II, OMEGAMON Monitoring Agent, OMEGAVIEW, OMEGAVIEW II, Solutions for NetworkedBusinesses, and Transplex.

Trademarks and service marks of Candle Corporation: Alert Adapter, Alert Adapter Plus, Alert Emitter, AMS,Amsys, AUTOMATED FACILITIES, Availability Management Systems, Candle Business Partner Logo, CandleDirect Logo, CandleLight, CCC, CECS, CICAT, CL/ENGINE, CL/GATEWAY, CL/TECHNOLOGY, CMS, CMW,Command & Control, CommandWatch, 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/DASD, DB/EXPLAIN, DB/MIGRATOR, DB/QUICKCOMPARE, DB/SMU,DB/Tools, DB/WORKBENCH, Design Network, DEXAN, eBA*ServiceMonitor, End-to-End, Enterprise CandleCommand Center, Enterprise Candle Management Workstation, EPILOG, ERPNet, ESRA, HostBridge, IntelliWatchPinnacle, Lava Console, Messaging Mastered, MQADMIN, MQEdit, MQEXPERT, MQMON, NBX, OMA, OMCGateway, OMC Status Manager, OMEGACENTER Bridge, OMEGACENTER Gateway, OMEGACENTER StatusManager, OMEGAMON Management Center, OSM, PC COMPANION, Performance Pac, PowerQ,PQConfiguration, PQEdit, PQScope, Response Time Network, Roma, Roma Broker, Roma BSP, Roma Connector,Roma Developer, Roma FS/A, Roma FS/Access, Roma Network, Roma Systems Manager, Roma Workflow Access,Roma WF/Access, RTA, RTN, SentinalManager, Solutions for Networked Applications, Status Monitor, Tracer,Unified Directory Services and Volcano.

Trademarks and registered trademarks of other companies: AIX, DB2, and MQSeries are registeredtrademarks of International Business Machines Corporation. SAP is a registered trademark and R/3 is a trademarkof SAP AG. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/OpenCompany Ltd. HU-UX is a trademark of Hewlett-Packard Company. SunOS is a trademark of Sun Microsystems,Inc.

All other company and product names used herein are trademarks or registered trademarks of their respectivecompanies.

ProtoView Development Corp. - May contain DataTable Version 3.0 Copyright 1989—1996 by ProtoViewDevelopment Corp. and distributed under license by Candle Corporation.

Copyright 1995,1997,1998 2000, Candle Corporation, a California corporation. All rights reserved. Internationalrights secured.

Threaded Environment for AS/400, Patent No. 5,504,898; Data Server with Data Probes Employing Predicate Testsin Rule Statements (Event Driven Sampling), Patent No. 5,615,359; MVS/ESA Message Transport System Usingthe 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 forComputer Systems Without Native Threading Support, Patent No. 5,835,763; Object Procedure Messaging Facility,Patent No. 5,848,234; Communications on a Network, Patent Pending; End-to-End Response Time Measurement forComputer Programs, Patent No. 5,9991,705; 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 theGovernment is subject to restrictions set forth in the applicable license agreement and/or the applicable governmentrights clause.

This documentation contains confidential, proprietary information of Candle Corporation that is licensed for yourinternal use only. Any unauthorized use, duplication, or disclosure is unlawful.

Contents

List of Illustrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

Read This First . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

| Chapter 1. Background about Components and Modes of| Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15| Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16| Details about the NCP Data Collector . . . . . . . . . . . . . . . . . . 17| Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

| Chapter 2. Installing, Configuring, and Customizing| OMEGAMON II for VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21| Configuration Planning and Considerations . . . . . . . . . . . . . . 22| Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 26| CICAT Background and Requirements . . . . . . . . . . . . . . . . . 28| CICAT Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . 30| CICAT Configuration Procedures . . . . . . . . . . . . . . . . . . . . . 31| Manual Configuration Procedures . . . . . . . . . . . . . . . . . . . . 36| Manual Customization Procedures . . . . . . . . . . . . . . . . . . . . 37

| Chapter 3. Completing the Configuration . . . . . . . . . . . . . . . . . 39| APF-Authorizing the Libraries . . . . . . . . . . . . . . . . . . . . . . . 39| Copying the Procedures and VTAM Definitions . . . . . . . . . . . 40| Setting the Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40| Setting the Dispatching Priority . . . . . . . . . . . . . . . . . . . . . . 40| If You Selected the NCP Data Collector . . . . . . . . . . . . . . . . 41| If You Are Running VTAM 4.3 and Above . . . . . . . . . . . . . . 41| If You Selected to Configure TCP/IP . . . . . . . . . . . . . . . . . . 42| If You Are Configuring for Larger Networks . . . . . . . . . . . . . 45| If You Want to Use TNSTATs . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4. Verifying the Configuration . . . . . . . . . . . . . . . . . . . 49Starting End-to-End Version 500 . . . . . . . . . . . . . . . . . . . . . 49Activating OMEGAMON II Major Node . . . . . . . . . . . . . . . 50Starting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . 50Initializing the NAM Database . . . . . . . . . . . . . . . . . . . . . . 51Defining the User ID and Password . . . . . . . . . . . . . . . . . . . 51Logging onto OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . 52When Verification is Complete . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 5. NCP Data Collection Requirements . . . . . . . . . . . . . 55| NCP Monitor Component Requirements . . . . . . . . . . . . . . . . 55

Contents 3

| NPALU Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55| NCP Dynamic Configuration . . . . . . . . . . . . . . . . . . . . . . . . 55| NCP Data Collection Requirements . . . . . . . . . . . . . . . . . . . 56

NCP Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56X.25 NCP Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57NPALU Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Enabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . 59Disabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 6. Controlling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Enabling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

| Disabling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62ETE References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 7. Enabling OMEGAMON II Console Support . . . . . . . . 65

Chapter 8. Setting Thresholds and Exceptions . . . . . . . . . . . . . 67

Chapter 9. Setting Security . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Using the NAM Facility for Security . . . . . . . . . . . . . . . . . . 69Displaying User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Assigning User Authorities . . . . . . . . . . . . . . . . . . . . . . . . . 70Using RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Using CA-ACF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Using CA-TOP SECRET . . . . . . . . . . . . . . . . . . . . . . . . . . 72External Function Level Security . . . . . . . . . . . . . . . . . . . . . 73

Chapter 10. SMF Record Considerations . . . . . . . . . . . . . . . . . 75Enabling SMF Recording . . . . . . . . . . . . . . . . . . . . . . . . . . 75Exception Record Format Changes . . . . . . . . . . . . . . . . . . . . 76SMF Record Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 11. Dedicated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 77Activate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . . . 77Deactivate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . 78Set the Polling Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 12. Connecting to OMEGAVIEW . . . . . . . . . . . . . . . . . 79Enhanced Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Procedures and Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 79Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Profile Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . 80References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Appendix A. Operator Command KONFCCMD . . . . . . . . . . . . . 81Using the KONFCCMD Command . . . . . . . . . . . . . . . . . . . 81KONFCCMD Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

4 OMEGAMON II for VTAM V500 Config/Customization Guide

Appendix B. CT/Engine Startup Parameters . . . . . . . . . . . . . . . 87CT/Engine Startup Parameters . . . . . . . . . . . . . . . . . . . . . . . 87

Appendix C. Candle Customer Support . . . . . . . . . . . . . . . . . 105

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Contents 5

List of Illustrations

| 1. NCP Collector Within OMEGAMON II Address Space . . . . . . . 18| 2. NCP Collector in Another OMEGAMON II Address Space . . . . 19| 3. Not Using an NCP Collector . . . . . . . . . . . . . . . . . . . . . . . . . 19

List of Tables

1. OMEGAMON II for VTAM Documentation . . . . . . . . . . . . . . 14| 2. Product Components for OMEGAMON II for VTAM . . . . . . . . 16| 3. Characteristics and Requirements for OMEGAMON II Modes of| Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20| 4. Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26| 5. CICAT Configuration Procedure Checklist . . . . . . . . . . . . . . . . 33| 6. Manual Configuration Procedure Checklist . . . . . . . . . . . . . . . . 36| 7. Manual Customization Procedures Checklist . . . . . . . . . . . . . . . 37

List of Illustrations 7

Read This First

Preface

About this document

This guide explains how to perform the following installation processes forOMEGAMON II for VTAM Version 500 (hereafter referred to asOMEGAMON II):

� planning and migration� configuration� verification� customization

This is intended for those who have experience configuring and customizingmainframe software.

| OMEGAMON II monitors SNA and TCP/IP resources in your network and| provides information to help you tune VTAM and your NCP-related| resources (NCPs, lines, PUs, and LUs) according to your site's needs.

| This guide assumes that you have completed the installation (initial laydown)| specified in your Installing Candle Products on MVS manual. You loaded| OMEGAMON II from tape to disk and applied maintenance, but you have| not yet made any modifications.

Read This First 9

Adobe Portable Document Format

Introduction

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

1. Specify the print options for your system. From the Acrobat ReaderMenu bar, select File > Print Setup... and make your selections. Asetting of 300 dpi is highly recommended as is duplex printing if yourprinter supports it.

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

3. On the Print popup, select one of the Print Range options for

� a single page� a range of pages� all of the document

4. (Optional) To fit oversize pages to the paper size currently loaded onyour printer, select the Shrink to Fit option.

Printing problems?

Your printer ultimately determines the print quality of your output.Sometimes printing problems can occur. If you experience printingproblems, potential areas to check are:

� settings for your printer and printer driver. (The dpi settings for bothyour driver and printer should be the same. A setting of 300 dpi isrecommended.)

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

� the halftone/graphics color adjustment for printing color on black andwhite printers. (Check the printer properties under Start > Settings >Printer. For more information, see the online help for the AcrobatReader.)

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

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


Documentation Conventions

Introduction

Candle documentation adheres to accepted typographical conventions forcommand syntax. Conventions specific to Candle documentation arediscussed in the following sections.

Panels and figures

The panels and figures in this document are representations. Actual productpanels may differ.

Revision bars

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

Variables and literals

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

LOGON APPLID(cccccccc)

In the above example, you type LOGON APPLID followed by an applicationidentifier (represented by cccccccc) within parentheses. The number ofcharacters indicates the maximum allowable length of the variable.

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

Read This First 11

Symbols

The following symbols may appear in command syntax.

Symbol Usage

| The 'or' symbol is used to denote a choice. Eitherthe argument on the left or the argument on the rightmay be used. Example:

YES | NO

In this example, YES or NO may be specified.

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

APPLDEST DEST [ALTDEST]

In this example, DEST is a required argument andALTDEST is optional.

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

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

The workload variable is required. The REPORTkeyword must be specified with a value ofSUMMARY or HISTOGRAM.

_ Default values are underscored. Example:

COPY infile outfile -[COMPRESS={YES | NO}]

In this example, the COMPRESS keyword isoptional. If specified, the only valid values are YESor NO. If omitted, the default is YES.

␣ The symbol ␣ indicates a blank space, when neededfor clarity.


Documentation Set

Introduction

Candle provides a complete set of documentation for OMEGAMON II forVTAM. Each manual in this documentation set contains a specific type ofinformation to help you use the product.

Candle welcomes your comments and suggestions for changes or additions tothe documentation set. A user comment form, located at the back of eachmanual, provides simple instructions for communicating with Candle'sInformation Development department. You can also send email [email protected]. Please include the product name, version, and booktitle in the subject line. To order additional manuals, contact CandleCustomer Support.

Online documentation

The following documents in the OMEGAMON II for VTAM Version 500documentation set are available online in BookManager format:

� OMEGAMON II for VTAM Version 500 Release Guide

� OMEGAMON II for VTAM Configuration and Customization Guide

� OMEGAMON II for VTAM User's Guide

� OMEGAMON II for VTAM NCP Monitoring Guide

� OMEGAMON II for VTAM Historical Reporting Guide

� OMEGAMON II for VTAM Messages Manual

� End-to-End Response Time Feature (ETE) Reference Manual

Printed documentation

The documentation listed in the following table is available forOMEGAMON II for VTAM. To order additional product manuals, contactyour Candle Customer Support representative.

Read This First 13

Table 1. OMEGAMON II for VTAM Documentation

DocumentNumber

Document Name Description

ON60-5384 OMEGAMON II for VTAMVersion 500 Release Guide

Lists new features, enhancements, andchanges for this release.

IC51-6057 Installing Candle Productson MVS

Provides instructions for installingOMEGAMON II

ON51-5385 OMEGAMON II for VTAMConfiguration andCustomization Guide

Shows how to configure, verify, andcustomize OMEGAMON II for VTAMto your site's requirements.

ON54-5386 OMEGAMON II for VTAMUser's Guide

Shows how to use OMEGAMON II forVTAM to monitor and tune yournetwork.

ON99-5389 OMEGAMON II for VTAMNCP Monitoring Guide

Shows how to use OMEGAMON II forVTAM to monitor and tune your NCPresources.

ON54-5387 OMEGAMON II for VTAMHistorical Reporting Guide

Shows how to produce reports and graphsfrom SMF records generated byOMEGAMON II and provides recordlayouts.

ON52-5388 OMEGAMON II for VTAMMessages Manual

Lists messages issued, their explanations,and suggested responses.

ET53-5586 End-to-End Response TimeFeature (ETE) ReferenceManual

Describes ETE and its commands, andlists error messages, return codes, andsense codes.

Carnegie Mellon University Copyright and Permission

Candle's OMEGAMON II for VTAM product employs a subset of the Carnegie Mellon University (CMU) SNMP Library indata collection for versions of TCP/IP greater than V3.2. Such software is subject to the following: Copyright (C) 1998 byCarnegie Mellon University. All Rights Reserved.

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is herebygranted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permissionnotice appear in supporting documentation, and that the name of CMU not be used in advertising or publicity pertaining todistribution of the software without specific, written prior permission.

CMU disclaims all warranties with regard to this software, including all implied warranties or merchantability and fitness. Inno event shall CMU be liable for any special, indirect or consequential damages or any damages whatsoever resulting from lossof use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection withthe use or performance of this software.


| Chapter 1.| Background about Components and Modes of Operation

| This chapter contains information about the components and modes of| operation for OMEGAMON II for VTAM. The chapter provides| background information about the:

| � product components

| � NCP performance data collector and the three types available

| � modes of operation

Chapter 1. Background about Components and Modes of Operation 15

| Details about the NCP Data Collector

| An OMEGAMON II for VTAM address space contains an NCP performance| data collector that is capable of connecting to, and requesting data from, the| NPALUs in your NCPs. An OMEGAMON II address space can collect| NCP performance data:

| � using its own NCP collector (a LOCAL collector) or

| � from the collector in another OMEGAMON II address space (a| REMOTE collector).

| During the CICAT configuration process, you will be asked to specify| whether the OMEGAMON II you are configuring will obtain its NCP| performance data using its own LOCAL collector, or using the collector in| another OMEGAMON II address space (a REMOTE collector). If you do| not want to collect NCP performance statistics, you can specify NONE.

| Single OMEGAMON II Address Space

| If you plan to use only one OMEGAMON II address space, and you want to| collect NCP performance statistics, specify LOCAL NCP data collection to| CICAT. OMEGAMON II will obtain NCP performance statistics from the| LOCAL collector in the OMEGAMON II address space you are configuring.

| Multiple OMEGAMON II Address Spaces

| If you plan to use multiple OMEGAMON II address spaces, you can use| CICAT to configure the address spaces so that performance data from all| NCPs is available to all the address spaces. To do so, use CICAT to| configure one OMEGAMON II as LOCAL and the rest as REMOTEs.| Connect all NPALUs to the LOCAL address space, and configure each of the| REMOTE OMEGAMON IIs to obtain their NCP performance statistics from| the address space that you configured as LOCAL.

| Guidelines

| Keep in mind that:

| � An NPALU can connect to only one NCP performance data collector.

| � One NCP collector can monitor multiple NCPs.

| � One NCP can be monitored by only one NCP collector.


| Remote NCP Collector

| If multiple OMEGAMON II address spaces need access to performance data| from the same NCP(s), one address space must be configured to collect the| NCP performance data (a LOCAL address space). Other OMEGAMON II| address spaces (REMOTEs) will obtain NCP performance data via an LU 6.2| (APPC) connection to the LOCAL OMEGAMON II address space.

| An NPALU can connect to only one NCP collector.

| ┌───────────────┐| │REMOTE │| │ │| │ OMEGAMON II │| │ for │| │ VTAM │| │ │| └───────────────┘| A LU 6.2| │| ┌───────┼───────┐| │LOCAL D │ ┌───────────┐| │ ┌─────────┐ │ ┌────┴──────┐ │| │ │ NCP │ │ │ ┌─────┐ │ │| │ │Collector│=─┼──────────┼─:│NPALU│ │ │| │ │ Task │ │ │ └─────┘ │NCPn│| │ └─────────┘ │ │ NCP1│────┘| │ OMEGAMON II │ └───────────┘| │ for │| │ VTAM │| └───────────────┘

| Figure 2. NCP Collector in Another OMEGAMON II Address Space

|

| No NCP Collector

| OMEGAMON II runs without the NCP collector and without connection to| the collector in another address space.

| NCP performance statistics are not available to OMEGAMON II.

| ┌─────────────┐| │ │| │ OMEGAMON II │| │ for │| │ VTAM │| │ │| └─────────────┘

| Figure 3. Not Using an NCP Collector


| Chapter 2.| Installing, Configuring, and Customizing OMEGAMON II for| VTAM

| This chapter provides information about installing, configuring, and| customizing OMEGAMON II for VTAM.

| This chapter provides:

| � the considerations you should review before you begin to configure and| customize OMEGAMON II for VTAM

| � a broad overview of the installation, configuration, and customization| process (as well as where you can locate the information you will need)

| � background about the Candle Installation and Configuration Assistance| Tool (CICAT)

| � an overview of how you install OMEGAMON II for VTAM using| CICAT

| � an overview of how you configure OMEGAMON II for VTAM using| CICAT and a checklist listing the steps for the CICAT configuration| procedure

| � a checklist listing the steps for the manual configuration procedures

| � a checklist listing the steps for the manual customization procedures

| If you are installing OMEGAMON II for VTAM for the first time or you| need a reminder about the different components and modes of operation for| OMEGAMON II for VTAM, see the chapter “Background about| Components and Modes of Operation” on page 15.

Chapter 2. Installing, Configuring, and Customizing OMEGAMON II for VTAM 21

| Configuration Planning and Considerations

| This section provides the considerations that you must review before you| begin to configure and customize OMEGAMON II for VTAM.

| Requirements for Hardware and Software

| For information about hardware and software requirements, see Installing| Candle Products on MVS.

| For more details on historical reporting, see the OMEGAMON II for VTAM| Historical Reporting Guide.

| Migrating NAM and Table Database Data

| OMEGAMON II stores user-defined data in two VSAM files:

| � the network access manager (NAM) database (RKONNAM)| � the table database (RKONTDB)

| If you currently use prior releases of OMEGAMON II, you must decide if| you want to migrate your NAM and/or Table Database data to Version 500.

| You can avoid redefining the information itemized below to| OMEGAMON II by migrating your existing NAM and Table Database| datasets to Version 500. If you elect to do so, specify the existing dataset| name in the CICAT configuration panel.

| The NAM houses the following information for all prior releases:

| � user preferences| � user IDs and passwords (optional)

| The Table Database houses the following information for all prior releases:

| � user response time definitions table| � SMF response time definitions table| � virtual route monitoring options table| � administrator monitoring options| � user authorities table| � saved VTAM traces


| Migrating Historical Component SAS Databases

| If you currently use the SAS-based historical component in a prior| OMEGAMON II release, you must decide whether you want to continue| using your existing SAS datasets in Version 500 or allocate new SAS| datasets for this new release.

| The prior releases of the historical component SAS databases and graphics| catalog are fully compatible with Version 500.

| The SAS-related CICAT configuration panels generate migration JCL, if you| specify to do so by entering existing dataset names.

| SMF Record Considerations

| The format of OMEGAMON II SMF exception records changed in Version| 200 to support NCP performance statistics.

| Examine your site's custom-tailored programs that process OMEGAMON II| SMF exception records. If necessary, modify these programs to recognize| the exception record format changes.

| For Version 500 SMF record layouts, refer to the appendix in the| OMEGAMON II for VTAM Historical Reporting Guide.

| Security Considerations

| OMEGAMON II supports the following security interfaces:

| � the CT/Engine Network Access Manager (NAM) interface| � RACF| � CA-ACF2| � CA-TOP SECRET

| After you complete the installation and configuration processes, you must| complete setting up OMEGAMON II security. The chapter “Setting| Security” on page 69 provides detailed instructions.


| Monitoring the Log File

| The log (trend/exception) file contains trend and exception records for| display. The shipped default for maximum trend/exception record size is the| allowable VSAM maximum. This record size is declared as variable.

| We recommend that you carefully monitor the usage and free space of your| log file as you would monitor any VSAM application file. For information| about monitoring the log file, see the OMEGAMON II for VTAM User's| Guide.

| Japanese Language Support

| A single address space can support Japanese as well as US English.

| If you want to use OMEGAMON II for VTAM in Japanese, you must have| specified National Language Support when you defined the Runtime| Environment (RTE) using CICAT.

| To access OMEGAMON II for VTAM, you must specify the Japanese| applid using 3270 emulator software that supports Japanese. (Japanese uses| the EBCDIC double byte character set.)

| If you are using 3270 emulator software, you must also configure the| software with the correct settings. If the settings are not correct, the| characters are not displayed correctly. If your software displays:

| � SBCD code pages, select the code page for 1027| � CCSIDs, select CCSID 939

| If these settings are not available in the configuration for your software or| the characters are not being displayed correctly, contact the vendor for your| software.


| Non-English Language Terminals

| OMEGAMON II displays upper and lowercase characters in panels and| messages. If your terminals display Kanji or other special characters in place| of lowercase characters, you can specify Y (Yes) for the following CT/Engine| startup parameters:

| INTLCHAR Displays the vertical bar (|) and diacritical marks correctly.

| UPPERDLG Displays OMEGAMON II panels in uppercase.

| UPPERLOG Displays RKLVLOG messages in uppercase.

| UPPERWTO Displays MVS console messages in uppercase.


| Getting Help with CICAT

| The help for CICAT contains detailed information about using the CICAT| panels. For example, the help contains information about:

| � how to use the panel| � why parameters are required| � what the available action codes provide| � what the input fields mean| � what you are required to supply

| To display help from any CICAT panel, press the Help key (F1) or enter| HELP on the command line.

| You can also display help for the help. For example, you can display| information about the command to use to return to the previous topic in the| help system. To display the help for help from any help panel, press the| Help key (F1) or enter HELP on the command line.


| CICAT Background and Requirements

| This section describes using the Candle Installation and Configuration| Assistance Tool (CICAT).

| You must use CICAT to install and configure OMEGAMON II for VTAM.| CICAT is an ISPF dialog that guides you through the installation and| configuration steps required to install this product. Data entry panels assist| you in understanding your site-specific parameter values. Associated help| panels assist you in understanding the CICAT process and describe the input| fields on the entry panels.

| CICAT is restartable. If necessary, you can end the dialog, start it again, and| continue from the point of interruption. ISPF V2.3 or above is required to| use CICAT.

| If you have not previously installed CICAT during installation of this or any| other Candle product, you must do so now. For instructions on installing| CICAT, see the Installing Candle Products on MVS manual. If you want to| use CICAT from a previous installation, you must ensure that it is the most| current version of CICAT. The Installing Candle Products on MVS manual| will help you make this determination.

| Restrictions on Specifying Values in CICAT

| Important Note: Entering ampersand (&) in any CICAT parameter string,| whether you are in interactive or batch mode, results in a CICAT abend.

| Reminder about the Information Available

| If you need information about installing OMEGAMON II for VTAM using| CICAT, you can locate information in the:

| � Installing Candle Products on MVS manual

| � online help for the product panel you are using


| CICAT Installation Procedure

| This section provides information about the CICAT installation process.

| Overview of the Installation Process Using CICAT

The following is an overview of how you select products to configure andmanage your runtime environment.

1. Invoke CICAT.

2. Select from the CICAT Main Menu as follows:

� If installing a standalone product, select the item for the product.

� If installing from a multi-product quick install tape, select the itemMultiProduct Quick Install, nnnn level.

3. Ensure that installation and maintenance is completed before startingconfiguration.

| 4. Select Assist Configuration.

5. If a target RTE has not already been defined, use action code A (Add) todefine an RTE.

6. Use action B (Build) to allocate runtime libraries.

7. Use action code C (Configure) to invoke configuration of an RTE.

8. Select a product to configure, depending on how you selected from theCICAT Main Menu, as follows:

� If you selected a single-component product on the CICAT MainMenu, the product configuration menu appears and you can proceedto configure.

� If you selected a multi-component product, a list of componentsappears. Select and configure each component in the orderpresented.

� If you selected a multi-product quick install tape, a list of productsand components found on the tape appears. Select and configureeach product/component in the order presented.

9. If you want to configure another product and it is not part of a quickinstall tape, return to the initial CICAT menu, select the product, and

| return to step 4 to select Assist Configuration.

10. When you are finished configuring all the products you want in an RTE,return to the Runtime Environments panel and use action code L (Load)to load the runtime libraries.

11. You can now proceed to verify and customize the products youconfigured in your RTE.


| CICAT Configuration Procedures

| This section describes the CICAT configuration procedures for| OMEGAMON II for VTAM.

| Prerequisites for Configuring OMEGAMON II for VTAM

| Before you start to configure OMEGAMON II for VTAM, be sure that you| have reviewed the considerations and planning information in the chapter| “Configuration Planning and Considerations” on page 22.

| The following configuration procedures assume that you have:

| � Completed SMP/E installation and applied maintenance for| OMEGAMON II for VTAM, or for a MultiProduct Quick Install tape| that includes OMEGAMON II for VTAM, as described in your| Installing Candle Products on MVS manual.


| If you need information about configuring OMEGAMON II for VTAM| using CICAT or specific information about the values you specify using| CICAT, see the online help for the product panel you are using.


| Accessing the Configure OMEGAMON II for VTAM Menu

To begin OMEGAMON II for VTAM configuration:

1. Start CICAT. (For a reminder, see your Installing Candle Products onMVS manual.)

2. On the CICAT Main Menu:

� If you installed the MultiProduct Quick Install tape, selectMultiProduct Quick Install.

To preview the list of products included in your MultiProduct QuickInstall tape, you can use action code V (View AdditionalInformation) on MultiProduct Quick Install.

� If you installed OMEGAMON II for VTAM as a separate product,select it.

| 3. On the Installation/Configuration Primary Menu, select Assist| Configuration.

4. On the Runtime Environments panel, use action code C (Configure) onthe RTE you are ready to configure.

5. If you installed the MultiProduct Quick Install tape or a multicomponentproduct, select OMEGAMON II for VTAM on the ProductConfiguration Selection Menu.

6. Proceed to use the Configure OMEGAMON II for VTAM Menu.

| Example of the Configure OMEGAMON II for VTAM Menu in CICAT

| The following figure is an example of the Configure OMEGAMON II for| VTAM menu.

| �| �| ----- CONFIGURE OMEGAMON II FOR VTAM / RTE: CMSIRA --------

| Last Selected

| Perform these configuration steps in order: Date Time

| 1 Specify configuration values

| 2 Allocate additional runtime datasets

| 3 Create runtime members

| 4 Run migration utility (optional)

| 5 Complete the configuration

| 6 Configure SAS historical reporting (optional)

| 7 Complete SAS configuration

| 8 Install BookManager data (optional)

| ;| <


| CICAT Configuration Checklist

| The following table contains the steps you perform on the CICAT Configure| OMEGAMON II for VTAM menu. The steps are listed in the sequence in| which they are to be performed. Use the √ column to check off steps as you| complete them.

| Table 5. CICAT Configuration Procedure Checklist

| √| CICAT Configuration Step

|

| Use Specify configuration values to specify the values CICAT| uses to create the runtime members. For example, you specify:

| � the names and applids for OMEGAMON II for VTAM

| � the type of security to be used

| � the type of NCP data collection

| | Use Allocate additional runtime datasets to review the JCL that| CICAT generates to allocate the datasets for historical reporting.

| | Use Create runtime members to review the JCL that CICAT| generates to create the members for OMEGAMON II for VTAM

|

| If you want to migrate NAM and TABLEDB data from a prior| release, select Run migration utility and specify the names of the| data sets. (This step is optional.)

|

| Use Complete the configuration to display the steps you must| perform to complete the configuration outside of CICAT. (The| steps are also covered in “Completing the Configuration” on| page 39.)

| | If you want to use SAS historical reporting, select Complete SAS| historical reporting. (This step is optional.)

|

| If you want to use SAS historical reporting, select Complete SAS| configuration to display the steps you must perform outside of| CICAT to complete the configuration for SAS. (This step is| optional.)

|

| If you want to install documentation that you can access using| BookManager, specify the values and select the documentation| using Install BookManager data. (This step is optional. The steps| are also covered in the OMEGAMON II for VTAM Historical| Reporting Guide.

| | Load the runtime libraries using “When to Load the Runtime| Libraries” on page 34.


| When to Load the Runtime Libraries

| You use action code L (Load Libs after SMP/E) on the Runtime| Environments (RTEs) panel to populate the load libraries for a selected RTE.| This action code upgrades your RTE to the latest Candle maintenance level.| Use action code L at the following points in the CICAT process:

| � After you install and configure the products you want in a new RTE.

| � After you install and configure an additional product into an existing| RTE.

| � After you apply additional Candle maintenance.

| When you defined or updated your RTE, you had the option to selectively| load from the target to the runtime libraries only those members that| changed.

| If you requested Load Optimization, the load job generated when you use| action code L (Load):

| � Copies only modified modules.| � Requires access to IBM's SuperC (ISRSUPC) utility.| � Uses less DASD space.| � Performs additional analysis which uses more CPU and I/O.

| If you bypass Load Optimization, the load job:

| � Copies all members.| � Requires more DASD space.| � Uses less CPU time.


| If You Decide to Change the Parameters

| Once you complete configuration, if you need to change configuration| parameters:

| 1. Reinvoke CICAT.

| 2. Use the Define OMEGAMON II for VTAM Configuration Values selection| on the Configure OMEGAMON II for VTAM panel to specify the new| values.

| 3. Be sure to select Create Runtime Members on the Configure| OMEGAMON II for VTAM panel and submit the generated JCL.

| 4. Review the Complete the Configuration selection on the Configure| OMEGAMON II for VTAM panel. There may be some processing to| perform outside of CICAT. For example:

| � If you change the OMEGAMON II proc name, recopy the proc from| shilev.RKANSAM to PROCLIB.

| � If you change the OMEGAMON II major node definition, recopy it| to VTAMLST.


| Manual Configuration Procedures

| This section provides information about performing manual configuration| procedures for OMEGAMON II for VTAM.


| The checklist in the following table contains the location where you can find| the information you will need.

| Manual Configuration Checklist

| The following table contains the steps you perform manually to configure| OMEGAMON II for VTAM. The steps are listed in the sequence in which| they are to be performed. Use the √ column to check off steps as you| complete them.

| Table 6. Manual Configuration Procedure Checklist

| √| Manual Configuration Step

| | Complete the configuration using “Completing the Configuration”| on page 39.

| | Verify configuration of the realtime monitor using “Verifying the| Configuration” on page 49.


| Manual Customization Procedures

| This section provides information about performing manual customization| procedures for OMEGAMON II for VTAM.


| The checklist in the following table contains the location where you can find| the information you will need.

| Manual Customization Checklist

| The following table contains the steps you perform manually to customize| OMEGAMON II for VTAM. The steps are listed in the sequence in which| they are to be performed. Use the √ column to check off steps as you| complete them. Candle recommends that you review the entire process| before you begin customizing OMEGAMON II for VTAM.

| Table 7. Manual Customization Procedures Checklist

| √| Manual Customization Step

|

| If you selected NCP data collection using CICAT, complete the| customization using “NCP Data Collection Requirements” on| page 55.

| | If you have not already enabled ETE, enable ETE using| “Controlling ETE” on page 61.

|

| If you want to enable OMEGAMON II console support, specify the| options in OMEGAMON II using “Enabling OMEGAMON II| Console Support” on page 65.

|

| To set exceptions and thresholds, specify tha values in| OMEGAMON II using “Setting Thresholds and Exceptions” on| page 67.

| | Select and customize a security system using “Setting Security” on| page 69.

| | If you want to enable SMF recording, specify the options in| OMEGAMON II using “SMF Record Considerations” on page 75.


| Chapter 3.| Completing the Configuration

| This chapter contains the configuration procedures that you must complete| outside of CICAT before you can begin to use OMEGAMON II for VTAM.| (These procedures are also covered on a panel displayed when you select to| complete the configuration using CICAT.)

| APF-Authorizing the Libraries

| OMEGAMON II must run APF-authorized and any library from which| OMEGAMON II loads routines must be APF-authorized. You must| APF–authorize:

| � OMEGAMON II load modules from the libraries defined to ddnames| STEPLIB and RKANMODL.

| � Additionally, the NCP collector loads modules from the libraries defined| to KONRRT (the NCP Resource Resolution Table).

| APF-authorize these load libraries defined to the following ddnames in the| OMEGAMON II for VTAM proc:

| � STEPLIB

| � RKANMODL

| � KONRRT (if you specified local NCP data collection)

| All these libraries must be APF-authorized; otherwise OMEGAMON II| abends with S306.

| For more information about MVS security see IBM's Authorized| Programming Services Guide.

Chapter 3. Completing the Configuration 39

| Copying the Procedures and VTAM Definitions

| Before you begin to use OMEGAMON II for VTAM, you must copy the| following procedures and VTAM definitions that you created using CICAT| to the locations listed. ( CICAT creates the procedures and VTAM definitions| in shilev.RKANSAM.)

| You must copy:

| � the VTAM major node from shilev.RKANSAM to VTAMLST

| � the VTAM procedure from shilev.RKANSAM to PROCLIB

| � the End-to-End started task JCL from shilvev.RKANSAM to PROCLIB| (If you have already installed ETE V500, you do not have to perform the| copy. You can also rename the procedure to meet your site's| requirements.)

| Setting the Security

| When you configured OMEGAMON II for VTAM using CICAT, you| selected the type of security you wanted to use. Before you can access| OMEGAMON II for VTAM, you must also set the security.

| For information about setting the security, see “Setting Security” on page 69.

| Setting the Dispatching Priority

| Th ensure the availability of OMEGAMON II for VTAM, you must set the| dispatching priority.

| � You must execute OMEGAMON II for VTAM with a dispatching| priority greater than the VTAM you monitoring.

| � If you are using End-to-End, you must execute ETE with a dispatching| priority equal to the VTAM you are monitoring.


| If You Selected the NCP Data Collector

| If you selected NCP data collection using CICAT, you must assemble and| linkedit the modetab. Follow these steps.

| 1. Review the jobstream CICAT created in shilevRKANSAM. (The name| is the name you specified for LU62 using CICAT.)

| 2. Submit the job.

| 3. Verify the results.

| For information about customizing the NCP data collector, see “NCP Data| Collection Requirements” on page 55.

| If You Are Running VTAM 4.3 and Above

| If you are running VTAM 4.3 and above, you must modify the startup JCL.| Follow these steps.

| 1. Add a DD statement for the library containing the PMI exit to the| VTAMLIB concatenation in your VTAM startup procedure:

| � If this RTE uses dedicated or shared runtime libraries, add| shilev.rte.RKANMOD.

| � If this RTE uses SMP/E target libraries, add thilev.TKANMOD.

| 2. Quiesce your network.

| 3. Restart VTAM.

| Result: The OMEGAMON II for VTAM Performance Monitor Interface| (PMI) exit is available to VTAM. OMEGAMON II uses the PMI to obtain| performance data from VTAM.


| If You Selected to Configure TCP/IP

| If you selected to configure TCP/IP using CICAT, you must also complete| the following configuration steps outside of CICAT.

| Obtaining TCP/IP performance measurements requires:

| � One of the following operating system environments:

| – MVS/ESA with TCP/IP version 3.2. This configuration also| requires:

| � Using the TCP/IP configuration command, OBEY, to authorize| the OMEGAMON II started task procedure to issue privileged| commands: DROP, TRACERTE.

| – OS/390 version 2.5 with TCP/IP version 3.4 or above and C| Language Environment 1.8 or above. This configuration also| requires:

| � Defining an OMVS segment in RACF for the OMEGAMON II| started task procedure.

| � An active SNMP agent.

| � An active SNMP subagent.

| � Enabling CSA Tracking to display TCP/IP CSA usage.

| � Answering Y to Configure the TCP/IP Component? and providing the| requested parameters during CICAT configuration

| OMVS Segment Requirement for OMEGAMON II

| The OMEGAMON II TCP/IP data collector uses TCP/IP service components| in Communications Server for OS/390 that exploit OS/390 UNIX services.| This requires an OS/390 UNIX security context, called an OMVS segment,| for the user ID associated with units of work requesting these services. Refer| to the IBM manual eNetwork Communications Server IP Planning and| Migration Guide for an explanation of how to provide an OMVS segment for| the OMEGAMON II started task.


| SNMP Agent and Subagent

| To obtain TCP/IP data for TCP/IP version 3.4 or above, OMEGAMON II| uses the Simple Network Management Protocol (SNMP) Management| Information Base (MIB). An SNMP agent and subagent must be active. The| chapter about SNMP in the IBM manual eNetwork Communications Server| Configuration explains the configuration procedure for running the TCP/IP| SNMP agent and subagent. The chapter also explains how to automatically| start the SNMP agent when TCP/IP starts.

| The SNMP subagent, a task in the TCP/IP address space, is an OS/390| UNIX application that communicates with the SNMP agent via an AF_UNIX| socket. Consequently, the AF_UNIX domain must be configured in your| BPXPRMxx member of SYS1.PARMLIB. Consult the BPXPRMxx chapter| in the IBM manual MVS Initialization and Tuning Reference for details about| activating the AF_UNIX domain.

| Community Name

| OMEGAMON II uses the community-based security of SNMPv2c, where| community name (password) is passed with each request to the SNMP agent.| You must provide a community name to authorize obtaining data from the| SNMP agent. To specify community name:

| 1. Select the Options pulldown on any OMEGAMON II panel.| 2. Select Monitoring Options.| 3. Select TCP/IP Options.| 4. Select TCP/IP Address Space Options

| If you do not provide a community name, public is used as the default.

| OMEGAMON II does not support the experimental user-based security of| SNMPv2u.


| Verifying SNMP Agent/Subagent Communications

| With TCP/IP version 3.4 or above, you can verify the communications| between your SNMP agent and subagent by issuing the following OSNMP| command:

| osnmp -v getbulk ibmMvsTcpConnLastActivity

| This command verifies whether the SNMP agent and subagent are active and| properly configured. The response from the command should be valid data,| without a timeout or error condition, such as:

| ibmMvsTcpConnLastActivity.K.K.K.K.21.K.K.K.K.K = 15496483

| Providing OMEGAMON II with the TCP/IP data file

| If you will be using OMEGAMON II for VTAM to monitor TCP/IP in| OS/390 2.5 or above and your installation TCPIP.DATA file cannot be| located using the search order documented in eNetwork Communications| Server IP Configuration, then you must add a SYSTCPD DD to your| OMEGAMON II started task procedure. The TCPIP.DATA file defines| system parameters required by TCP/IP client programs.

| An example SYSTCPD DD would be:

| //SYSTCPD DD DISP=SHR,DSN=TCPIP.PARMS(TCPDATA)

| Note: The TCPIP.DATA file may be a sequential file or a member of a| partitioned data set.

| Redbook References

| For additional information about implementing TCP/IP, you can refer to the| following IBM redbooks:

| � OS/390 eNetwork Communications Server V2/R5 TCP/IP Implementation| Guide Volume 1: Configuration and Routing

| Offers a good, complete overview of TCP/IP installation and| customization.

| � OS/390 eNetwork Communications Server V2/R5 TCP/IP Implementation| Guide Volume 2: OpenEdition Applications

| Discusses the SNMP agent and subagent.

| � OS/390 eNetwork Communications Server V2/R5 TCP/IP Implementation| Guide Volume 3: MVS Applications


| If You Are Configuring for Larger Networks

| In the CICAT startup parameters panel, you can modify the memory| management parameters to your site's requirements. These parameters are in| member KONSYSIN of the runtime library RKANPAR. If you have a very| large network, you may need to adjust these parameters to prevent error| messages and possible abends caused by insufficient storage.

| This section helps you decide whether modification is necessary and what| values to supply to CICAT.

| CT/Engine Storage Management

| The CT/Engine Storage Manager handles all storage allocation and| deallocation. Except when explicitly requested in certain situations, no OS| GETMAINs or FREEMAINs are used. This reduces the overhead in calling| OS services and expedites storage access and release.

| To perform its own storage management, CT/Engine GETMAINs the| maximum storage possible during startup. Storage blocks are then| dynamically acquired, freed, and tracked by CT/Engine to satisfy storage| requests.

| CT/Engine provides the MAXIMUM, MINIMUM, and RESERVE| parameters to control storage allocation and deallocation of primary and| extended storage.

| MAXIMUM

| This parameter specifies in kilobytes the maximum amount of primary (P)| and extended (X) storage that CT/Engine allocates for its own use, after| subtracting the amount specified by RESERVE.

| MAXIMUM is an overall storage throttle to prevent GETMAIN from| overallocating and occupying the page dataset with rarely referenced frames.| This value should allow CT/Engine to continue running without overloading| the paging volume and yet providing sufficient storage for dynamic requests.| The shipped defaults are usually sufficient. They are:

| MAXIMUM (8192,P) (32768,X)


| MINIMUM

| MINIMUM specifies in kilobytes the minimum amount of primary (P) and| extended (X) storage that CT/Engine allocates. If the MINIMUM amount| cannot be allocated, CT/Engine startup aborts. You may need to increase the| default values, which are:

| MINIMUM (1K24,P) (16384,X)

| RESERVE

| This parameter specifies the number of kilobytes of primary (P) and extended| (X) storage to reserve for OMEGAMON II use outside of CT/Engine| control. The total of the MINIMUM and RESERVE values must be less| than or equal to MAXIMUM. If RESERVE is larger than MINIMUM,| CT/Engine terminates.

| If you are getting abends due to lack of storage, you can increase the value| specified in the RESERVE parameter. The shipped defaults are:

| RESERVE (2K48,P) (4K96,X)

| Storage Utilization Report

| To obtain a storage utilization report, issue this modify command to the| OMEGAMON II started task:

| F cccccccc,STORAGE

| where ccccccc is the started task name you specified for OMEGAMON II| for VTAM using CICAT.

| You receive a series of KLVSDxxx messages indicating how much storage| remains free. These messages are documented in the OMEGAMON II for| VTAM Messages Manual.


Chapter 4.Verifying the Configuration

This chapter provides more details about the verification process.

The procedures in this chapter verify that OMEGAMON II has beeninstalled and configured properly.

| In the examples below, cccccccc represents the started task name you| specified for OMEGAMON II for VTAM using CICAT.

Starting End-to-End Version 500

For OMEGAMON II to use the End-to-End facility, you must do thefollowing:

� Use Version 500 of ETE.

� Apply all ETE maintenance included in the cumulative maintenance tapethat was shipped with OMEGAMON II.

� If ETE V500 is running, restart it to recognize the maintenance.

� Start ETE before you start OMEGAMON II

Perform the following procedure:

1. To bring up ETE Version 500 and to recognize current maintenance, youmust first quiesce both the current ETE subsystem and address spacecompletely by issuing this console command:

ETE QUIESCE

Result: You will see these responses:

ETEKK86: ETE ADDRESS SPACE TERMINATED BY SUBSYSTEM QUIESCEETEKK51: QUIESCE COMPLETEETEKKK3: COMPLETE

2. Start ETE Version 500 (with current maintenance) by issuing this consolecommand:

| S ccccccc

| where cccccccc is the started task name you specified for 500 using| CICAT.

Chapter 4. Verifying the Configuration 49

Result: You will see this response:

ETEKK91 ETE VERSION 5KK SUCCESSFULLY INITIALIZED

Activating OMEGAMON II Major Node

The OMEGAMON II VTAM major node must be active:

1. Activate the OMEGAMON II major node by issuing this MVScommand:

| VARY NET,ACT,ID=cccccccc

| where ccccccc is the major node name you specified for| OMEGAMON II for VTAM using CICAT.

Starting OMEGAMON II

To start the OMEGAMON II you just configured, enter this MVS command:

| S cccccccc

| where cccccccc is the started task name you specified for OMEGAMON II| for VTAM using CICAT.

Result:

� You will see these startup confirmation messages (not necessarily in thisorder):

KONPNKK1 OMEGAMON II for VTAM (V5KK)--INITIALIZATION COMPLETEDKONPNKK5 ETE CONNECTED SUCCESSFULLYKONPNKK2 ACT STARTED SUCCESSFULLYKONFCK1K FPON COMPONENT FUNCTIONS INSTALLATION COMPLETEKONFCK15 FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETEKONFCK25 SEMV MVS ENVIRONMENT INSTALLATION COMPLETEKONFCK2K SEVT VTAM ENVIRONMENT INSTALLATION COMPLETEKONFCK5K NDMT NCP DATA MANAGER INSTALLATION COMPLETEKONND1KK NCP DATA MANAGER TASK AVAILABLE FOR REQUESTS

� If you chose not to start ETE, OMEGAMON II continues to run withoutETE although this message appears:

KONPNKK4 ETE CONNECTION FAILED


� If you chose not to start the OMEGAMON II containing the NCPcollector, OMEGAMON II continues to run, although this messageappears until you use the NCP Performance Options under the Optionspull-down to turn off NCP monitoring.

KONAF121 NDM STARTUP FAILED RC(hhhhhhhh) SC(hhhhhhhh)WILL RETRY EACH ACT CYCLE INTERVAL

Initializing the NAM Database

Note: If you migrated your prior release's NAM file to Version 500, skip thisstep.

If you are a new OMEGAMON II user or have not migrated your NAMdatabase, you must declare the OMEGAMON II CT/Engine variables to theNAM database. Enter this command from the MVS console:

| F ccccccc,KONNAM


Result: You will see one or more messages in the following format:

KLVOP9K9 variable DECLARED: LENGTH(length)

Defining the User ID and Password

Notes:

1. If you are not using NAM security, skip this step.

2. If you migrated your prior release's NAM file to Version 500, skip thisstep.

To provide user access to OMEGAMON II, define a user ID and passwordto NAM. Issue this MVS MODIFY command to define yourself as a user:

| F cccccccc,NAM SET userid PASSWORD=password

where userid is your logon ID, password is a temporary password, and| ccccccc is the started task name specified for OMEGAMON II for VTAM| using CICAT.

Result: You will see this response:


KLVOP91K ACCESS CREATED FOR USERID userid

Logging onto OMEGAMON II

Log onto OMEGAMON II as follows:

1. Enter the following VTAM command:

| LOGON APPLID(cccccccc)

| where cccccccc is the logon applid you specified for OMEGAMON II| for VTAM using CICAT.

Result: The Candle logon panel appears.

2. Enter your name and password. If you use NAM, you are prompted toenter a new password.

Result: The first panel you see is the OMEGAMON II for VTAMStatus Display with status lights for the various VTAM and NCPcomponents. By default, as the first user, you become the productadministrator.

3. To define other users to OMEGAMON II:

a. Select the Options pull-down from the action bar.

b. Select User Authorities.

c. Specify other users and their authorities. See the chapter on userauthorities in the OMEGAMON II for VTAM User's Guide.

As an alternative you can use your external security package to authorizeusers to functions. See “External Function Level Security” on page 73.

4. To specify monitoring options for yourself and other users:

a. Select the Options pull-down from the action bar.

b. Select Monitoring Options.

c. Specify options, thresholds, and severities through subsequent menusand panels. See the chapter on monitoring options in theOMEGAMON II for VTAM User's Guide.

5. Navigate through various OMEGAMON II status, statistics, exception,and trend panels.


When Verification is Complete

When you have successfully completed the verification steps describedabove, you have finished the verification process.


Chapter 5.NCP Data Collection Requirements

This chapter indicates the definitions required in the Network ControlProgram generation for any NCP that you want to monitor withOMEGAMON II. You must regenerate and reload the NCP before youenable NCP data collection as described in “Enabling NCP Data Collection”on page 59.

| NCP Monitor Component Requirements

| The following are required to collect NCP statistics:

| � an OMEGAMON II configured for NCP collection

| � a Network Control Program generation, including required NPALU and| keyword definitions

| NPALU Usage

| Because the OMEGAMON II NCP performance component uses the| NPALU, it cannot coexist with the NCP functions of NetSpy or NPM which| also use the NPALU.

| The NPALU can be in session with only one application at a time.

| NCP Dynamic Configuration

| There is no need for you to define your NCP resources to OMEGAMON II| or the NCP collector. OMEGAMON II constructs a list of your active NCPs| and their subordinate resources dynamically during startup or at NCP| activation.

Chapter 5. NCP Data Collection Requirements 55

| NCP Data Collection Requirements

| Refer to “NCP Data Collection Requirements” on page 55 for information| about

| � NCP generation parameters required

| � X.25 NCP generation parameters required

| � defining the NPALU

| � enabling NCP data collection

NCP Generation

To collect performance data for any NCP resource, the following NCPgeneration parameters are required:

NPACOLL=YESCode on group, line, PU, and LU macros.

Provides performance statistics data to OMEGAMON II.

NPATP=YES Code on SDLC group, line, and PU macros.

Provides transmission priority data to OMEGAMON II.

SPEED Code on SDLC, BSC, CA LINE and X.25 MCH LINKmacros

OMEGAMON II uses the SPEED parameter to calculateline utilization. For SDLC or BSC lines using externalclocking, be sure that your SPEED parameter value equalsthe speed of the modem, otherwise your utilizationstatistics will be invalid.

DUPLEX Code on SDLC and BSC LINE macros.

OMEGAMON II uses the DUPLEX parameter whencalculating utilization statistics.

TRSPEED Code on token-ring physical LINE macros.

OMEGAMON II uses the TRSPEED parameter whencalculating utilization statistics.

For more information about these parameters, see the IBM manual, NCP,SSP, and EP Resource Definition Reference.


Performance-related NCP generation parameters are displayed on the resourcesummary panels so that you do not have to refer back to the gen. The valueof a parameter displays as N/A if you did not code it in your gen.

You can gen a parameter, such as PASSLIM, at a higher level than the PUmacro (on the GROUP or LINE macro), and have it sift down to the PUmacro. Any keyword that is valid at more than one level in the NCP gen,can sift down from higher to lower levels.

Important

For OMEGAMON II performance reasons, specify NPACOLLexplicitly for all resources, whether or not you want to collectdata for them, by coding NPACOLL=YES or NPACOLL=NO.As with other keywords, NPACOLL sifts down from higher tolower levels.

X.25 NCP Generation

In addition to the SPEED keyword on the MCH LINK macro, to displayperformance statistics for X.25 resources, you must code the following inyour NCP generation:

1. On the BUILD statement, code

NPA=YES

2. On the OPTIONS statement, code

NEWDEFN=(YES,ECHO,NOSUPP,REUSE)

3. On the X25.MCH statement, code

NPACOLL=(MCHLINK,MCHPU,VCPU)

4. On the X25.MCH statement, also code

NPPVCN=(n)

where n is the maximum number of virtual circuits for which data iscollected at the same time.

For more information about these keywords, see the IBM manual X.25Network Control Program Packet Switching Interface: Planning andInstallation.


NPALU Definition

This section shows the NPALU definition required for connection to the NCP| collector. This definition is provided in the shilev.RKANSAM library

member KONCTNPA. CICAT concatenates the OMEGAMON II terminalpool prefix specified during CICAT configuration with the characters NCP anduses that for the LOGAPPL value in KONCTNPA. The default value isKONNCP.

The NPALU definition is listed here for your information. It is required toactivate the NPALU to NCP collector applid connection.

Code the following keywords on the NPALU LU macro:

MAXCOLL Specifies the number of resources for which you cancollect data. Add at least 10% for growth. This parameterdefaults to number of lines plus number of PUs.

LOGAPPL Controls automatic activation of the NPALU to the NCPcollector.

NPALU Definition for NCP Collector Connection (KONCTNPA)

These are the sample NPALU macro definitions that automatically generate asession with the NCP collector task at NCP activation.

************************************************************************** NCP NPALU Definitions for Automatic Connection to ****** NCP collector task at NCP Activation **************************************************************************NPAGRPKK GROUP NPARSC=YES, X VIRTUAL=YES, X LNCTL=SDLC*NPALNEKK LINE*NPAPUKK PU*NPALUKK LU LOGAPPL=konNCP************************************************************************


BUILD Macro

On your generic BUILD macro, make sure to include the following keyword:

NPA=YES

Enabling NCP Data Collection

When the required NCP's definitions are generated, the NCP collectorautomatically connects to the NCP at NCP activation.

If the NPALU was previously defined, you can do the following:

1. Ensure that the NPALU is not in session with anything else.

2. Issue this command:

VARY NET,ACTIVE,ID=npalu_name,LOGON=konNCP

where konNCP is the logon applid for the NPALU.

For information about disabling NCP data collection, see below.

Disabling NCP Data Collection

If you do not want OMEGAMON II to collect NCP statistics, use CICAT toreconfigure OMEGAMON II without NCP data collection. Do thefollowing:

1. If no other OMEGAMON IIs use the NCP collector, reconfigureOMEGAMON II without the collector.

2. If another OMEGAMON II uses the NCP collector, reconfigure thatOMEGAMON II to include the collector.

3. Use CICAT to reconfigure OMEGAMON II. CICAT removes theOMEGAMON II startup commands that install and start the NCP DataManager Task (NDMT) by making the following revisions to theKONSTKON member in the rhilev.RKANCMD library:

a. Comments out the entire KONFCCMD INSTALL NDMT statementwhich spans several lines.

b. Comments out the KONFCCMD START NDMT statement.


Chapter 6. Controlling ETE

If you already have ETE Version 500 installed and enabled, you can skip thischapter.

ETE operates under the following rules:

� For OMEGAMON II to utilize the End-to-End facility, the End-to-EndResponse Time Feature must be started before OMEGAMON II.

� ETE Version 500 was designed as a common component that can beshared by multiple OMEGAMON products. OMEGAMONs that useEnd-to-End include it as part of the product package.

� If ETE Version 500 is already installed in your system, it can be used byOMEGAMON II.

� When the variable $$ETE in the NAM database is set to Y, which is theshipped default, OMEGAMON II starts up expecting ETE to be startedand tries to connect to it.

� If OMEGAMON II cannot connect to ETE, it issues a message butcontinues to run.

� If you change the setting of the NAM variable $$ETE, you must restartOMEGAMON II to recognize the new setting.

| In the examples below, the cccccccc represents these started task names you| specified using CICAT.

| � OMEGAMON II for VTAM

| � ETE

Enabling ETE

Although the OMEGAMON II shipped default is ETE enabled, you mayhave previously disabled ETE. To reenable OMEGAMON II to use ETE:

1. Start OMEGAMON II.

| S cccccccc

| where cccccccc is the started task name you specified for| OMEGAMON II for VTAM using CICAT.

2. Enable ETE by issuing this command at the MVS console:

| F cccccccc,NAM SET OMVTAM $$ETE:Y

Chapter 6. Controlling ETE 61


Result: The system displays this message:

KLVOP9K5 $$ETE:Y FOR USERID OMVTAM

3. Stop OMEGAMON II.

| P cccccccc

| where ccccccc is the started task name you specified for| OMEGAMON II for VTAM using CICAT.

| 4. Ensure that ETE is started. You can start ETE with the console| command:

| S cccccccc.

| where ccccccccc is the started task name you specified for ETE using| CICAT.

5. Restart OMEGAMON II.

| S cccccccc


| Result: OMEGAMON II starts and then connects to ETE.

| Disabling ETE

| Although OMEGAMON II can run with or without ETE, you may want to| disable ETE. You can enter the following command from the MVS console| while OMEGAMON II is running:

| F cccccccc,NAM SET OMVTAM $$ETE:N


Result: Next time and all subsequent times that OMEGAMON II starts, itwill no longer try to connect to ETE, until you reenable it.


ETE References

For more details about ETE, refer to the following:

� “Starting End-to-End Version 500” on page 49

� End-to-End Response Time Feature Reference Manual, Version 500

Chapter 6. Controlling ETE 63

Chapter 7.Enabling OMEGAMON II Console Support

To enable OMEGAMON II console support, perform these steps online:

1. Press F10 to move the cursor to the upper left corner of anyOMEGAMON II display panel, the action bar entry field.

2. Select the Options pull-down by entering O in the action bar entry field.

3. Select Monitoring Options by entering an M on the Options menu.

4. Select Global Options by entering O on the Monitoring Options menu.

5. On the Global Options panel, move the cursor to the last field, OMEGAMONConsole APPLID Prefix.

6. For console support, you must enter the same value that was specified forTerminal Pool Prefix in the CICAT configuration process. This is thename of the 1 to 5 byte OMEGAMON II terminal pool prefix used whenaccessing the OMEGAMON II VTAM console.

A pool of applids are created, where all the applid names start with thesame 5-byte prefix.

7. Press F12 until you return to the main status panel.

8. Press F6 to access the VTAM console panel.

9. Verify that the VTAM console feature works properly by entering

D NET,APPLS

Result:

ISTK97I DISPLAY ACCEPTEDIST35KI DISPLAY TYPE = APPL MAJ NODES/NAMES...IST314I END

Chapter 7. Enabling OMEGAMON II Console Support 65

Chapter 8.Setting Thresholds and Exceptions

The user who first installs OMEGAMON II has administrator authority. Anadministrator uses the Options pull-down to set thresholds and exceptionvalues in OMEGAMON II for your site.

To set monitoring options, perform the following steps:

1. Select the OMEGAMON II Options pull-down by entering O in theaction bar entry field.

2. Select Monitoring Options by entering M on the Options pull-down menu.

3. Select the options that you want to modify from the Monitoring Optionspanel. For details on each monitoring option, refer to the chapter onmonitoring options in the OMEGAMON II for VTAM User's Guide.

4. Return to the main status panel. The status lights on the main statuspanel reflect VTAM and NCP status based on the settings you specifyfor

� resources to monitor� exception conditions to monitor� threshold values� exception severities

Chapter 8. Setting Thresholds and Exceptions 67

Chapter 9. Setting Security

The network access manager (NAM) can serve either as a standalone securitysystem or as an interface to the security system of your choice.

Member rhilev.rte.RKANPAR(KONINNAM) contains security systeminformation. KONINNAM defines one or more control points, each of whichselects a security system and names a VSAM file (the NAM database) tostore user profile information. When NAM is the chosen security system, theVSAM file (the NAM database) also holds encrypted security information.By default, OMEGAMON II uses only one control point so that all usersaccess OMEGAMON II through the same security system.

Using the CICAT configuration panels began the process of definingOMEGAMON II security. This chapter describes the remaining steps youmust perform to define security to NAM and to other security systemsincluding RACF, CA-ACF2, and CA-TOP SECRET.

| In the examples below, cccccccc represents the started task name you| specified for OMEGAMON II for VTAM using CICAT.

Using the NAM Facility for Security

If you are using the NAM facility for security, you do not need to changemember rhilev.rte.RKANPAR(KONINNAM), because KONINNAMautomatically selects NAM. However, you must define your users to NAM.

To add more user IDs to the NAM database, do the following:

1. Start OMEGAMON II if you have not already done so.

| S ccccccccc

| Where cccccccc is the started task name you specified for| OMEGAMON II for VTAM using CICAT.

| 2. Issue the MVS MODIFY command from the MVS console. For| example:

| F cccccccc,NAM SET userid1 PASSWORD=password1| F cccccccc,NAM SET userid2 PASSWORD=password2


Chapter 9. Setting Security 69

3. Verify that the users can log onto OMEGAMON II.

Displaying User IDs

Issue the following operator command to display all user IDs that are definedto the NAM dataset:

| F cccccccc,NAM LIST


Assigning User Authorities

Whichever security system you use for OMEGAMON II entry validation,each user ID is assigned user authorities by an authorized administratorthrough the User Authorities choice on the Options pull-down menu. Referto the chapter on user authorities in the OMEGAMON II for VTAM User'sGuide for more information.

As a default, the first user to log onto OMEGAMON II has administratorauthority. To assign user authorities, a product administrator follows thesesteps:

1. Enter O in the action bar entry field to select the Options pull-down.2. Select User Authorities.3. Update user authorities, as required for your site.4. Verify that your users can access the OMEGAMON II components they

require.

As an alternative to internal OMEGAMON II for VTAM security, you canuse your external security package to authorize users to specific functions.See “External Function Level Security” on page 73.

Using RACF

The CICAT configuration process made the necessary changes torhilev.rte.RKANPAR(KONINNAM) so that it now looks like this:

DEFAULT DSNAME(rhilev.rte.RKONNAM) -RACF -NODB


If you want to change this member, restart OMEGAMON II to recognize thechanges.

Using CA-ACF2

Because OMEGAMON II uses a multiuser system access control point, ithas all the characteristics of an ACF2 multiple user single address spacesystem (MUSASS). That is, system access validations are initiated andenforced by the address space on behalf of the network user.

The CICAT configuration process accomplished the following:

� Updated member rhilev.rte.RKANPAR(KONINNAM) to look like this:

DEFAULT DSNAME(rhilev.rte.RKONNAM) -EXIT=KLVA2NEV -NORACF -NODB

| � Created a jobstream in the KONASM member of the shilev.RKANSAM| library that assembles and links ACF2 exit KLVA2NEV.

To complete defining ACF2 security, you must do the following:

1. Submit the jobstream in rhilev.rte.RKANSAM(KONASM) and verifysuccessful completion.

2. Define OMEGAMON II as a MUSASS to ACF2. For example:

| READY| acf| ACF| set lid| LID| ch cccccccc musass| LID| end| READY


3. Restart OMEGAMON II to recognize the change.


Using CA-TOP SECRET

The CICAT configuration process made memberrhilev.rte.RKANPAR(KONINNAM) look like this:

DEFAULT DSNAME(rhilev.rte.RKONNAM) -RACF -NODB

To complete defining TOP-SECRET security, you must do the following:

1. Define the OMEGAMON II address space as a started task in the STCrecord, along with the related master FACILITY ACID. For example,enter

TSS ADD(STC) PROC(cccccccc) ACID(mfacid)

where cccccccc is the started task name you specified forOMEGAMON II for VTAM using CICAT.

2. (Optional) If you want to protect all OMEGAMON II datasets, definethem to CA-TOP SECRET. Make sure the OMEGAMON II started taskhas access to them.

| 3. Define the started task as a facility to CA-TOP SECRET in the facility| matrix table. The started task name and the facility name must match.

The following example shows FACILITY statements from a productioninstallation using CA-TOP SECRET as the security system. If somestatements are not relevant to your system, modify them to fit yourstandards and configuration.

| FACILITY(USER3=NAME=cccccccc)| FACILITY(cccccccc=MODE=FAIL,ACTIVE,SHRPRF)| FACILITY(cccccccc=PGM=KLV,NOASUBM,NOABEND,NOXDEF)| FACILITY(cccccccc=ID=3,MULTIUSER,RES,LUMSG,STMSG,WARNPW,SIGN(M))| FACILITY(cccccccc=NOINSTDATA,NORNDPW,AUTHINIT,NOPROMPT,NOAUDIT,NOMRO)| FACILITY(cccccccc=NOTSOC,LOG(INIT,SMF,MSG,SEC9))

| Where ccccccccc is the started task name you specified for| OMEGAMON II for VTAM using CICAT.

Notes:

a. Make certain that the SIGN parameter is specified as SIGN(M).Otherwise, CA-TOP SECRET may produce a message stating thatuser access has been revoked.

b. Verify that MODE=FAIL is set.

4. Restart OMEGAMON II to recognize the change.


External Function Level Security

This section describes how to implement external function level security.The feature enables your security administrator to restrict user access toOMEGAMON II for VTAM functions by defining resource rules to yourexternal security manager: CA-ACF2, RACF, or CA-TOP SECRET. Youcan use this feature instead of OMEGAMON II internal security which is setunder the User Authorities selection of the Options pulldown.

Functions Secured

External function level security uses your external security manager torestrict user access to any of these OMEGAMON II functions:

� OMEGAMON II access� administrator authority� VTAM trace� response time� VTAM console

Requirements

Before implementing external function level security, you must do thefollowing:

1. Enable sign-on security through your external security manager. See theprevious sections of this chapter describing how to set up externalsecurity using RACF, CA-ACF2, or CA-TOP SECRET.

2. Provide a function level security resource class name when definingOMEGAMON II configuration values to CICAT.

3. Define the resource class name to your external security package.

External Security Resource Names

The following external resource names are used to secure the fiveOMEGAMON II functions listed:

| OMEGAMON II access cccccccc.KON.ACCESS| administrator authority cccccccc.KON.ADMIN| VTAM trace access cccccccc.KON.TRACE| response time access cccccccc.KON.RESPONSE| VTAM console access cccccccc.KON.CONSOLE


| where ccccccc is the logon applid you specified for OMEGAMON II for| VTAM using CICAT.

Example of Authorizing User Access

This is an example of using RACF to authorize only one user to the VTAMtrace function.

| RDEFINE classname cccccccc.KON.TRACE UACC(NONE)| PERMIT cccccccc.KON.TRACE CLASS(classname) ID(user1) ACCESS(READ)

where

| cccccccc is the logon applid you specified for OMEGAMON II for| VTAM using CICAT.

classname is the resource class name for the OMEGAMON II tracefacility

user1 is the user ID of the authorized user

Messages to User

� When this feature is implemented and you select User Authorities fromthe OMEGAMON II Options pulldown, the following message appears:

User Authorities - External Security Active

In this system, user authorities are maintained using an externalsecurity package. Please contact the system administrator.

� When a user selects an unauthorized function, the message displayed isthe same whether security is external or internal to OMEGAMON II.


Chapter 10.SMF Record Considerations

For the OMEGAMON II components where SMF recording is enabled,OMEGAMON II creates SMF exception and trend records.

For more details on historical reporting, see the OMEGAMON II for VTAMHistorical Reporting Guide.

Enabling SMF Recording

You can produce historical reports using the SMF data generated byOMEGAMON II. To set SMF recording options, follow these steps:

1. Select the Options pull-down from the action bar.

2. Select Monitoring Options.

3. From the Monitoring Options menu, select a performance category suchas Buffer Pools, Virtual Routes, or NCP Performance.

4. Select Monitor Options.

5. Enter S (SMF) or B (Both) in the Exception and Trend Recording fieldsto enable SMF recording.

See the chapter on monitoring options in the OMEGAMON II for VTAMUser's Guide for additional information on setting monitoring options.

You must enable SMF and use it to collect some data before you canaccomplish either of the following:

� Verify operation of the SAS-based historical component.

� Generate historical reports using SAS.

Chapter 10. SMF Record Considerations 75

Exception Record Format Changes

Check the custom-tailored programs at your site that processOMEGAMON II SMF exception records. They may require revisions torecognize that the exception record format expanded in Version 200.

SMF Record Layouts

You can find OMEGAMON II SMF record layouts in an OMEGAMON IIfor VTAM Historical Reporting Guide appendix.


Chapter 11. Dedicated Mode

In addition to a logon through VTAM, OMEGAMON II also supports thededicated mode of operation as an option. This provides direct access toOMEGAMON II through a local VTAM terminal.

Dedicated mode is useful when normal online response time becomes poordue to problems within VTAM. In this case, you can use a dedicated modeterminal to bypass VTAM during logon.

To use dedicated mode, you must have a terminal online to MVS and notcurrently used by VTAM or any other subsystem.

Activate a Dedicated Terminal

To activate a terminal dedicated to OMEGAMON II, you can take one of thefollowing two approaches.

Define Terminal at Startup

1. Insert the following line in member rhilev.RKANCMD(KONSTKON),before the DIALOG statement:

DEDICATE UNIT-xxx KONDSTRT

where xxx is the terminal's MVS address.

2. Stop OMEGAMON II.

3. Restart OMEGAMON II.

Result: OMEGAMON II begins dedicated mode operation.

Chapter 11. Dedicated Mode 77

Allocate Terminal Dynamically

1. With OMEGAMON II running, issue the following MVS command:

F canson,DEDICATE UNIT-xxx KONDSTRT

where xxx is the terminal's MVS address and canson is theOMEGAMON II started task name specified during OMEGAMON IICICAT configuration.

Result: The following message appears on the terminal (at address xxx):

Press ENTER to start dedicated session

2. Press Enter.

Result: OMEGAMON II begins dedicated mode operation.

Deactivate a Dedicated Terminal

To close and free a previously dedicated terminal, issue the following MVScommand:

F canson,CLOSE UNIT-xxx

where canson is the OMEGAMON II for VTAM started task procedurename.

Set the Polling Interval

The polling interval is the time between two reads from the screen. Bydefault, this value is 1 second. You can change this value by issuing aDEDICATE command and changing the INTERVAL parameter:

DEDICATE UNIT-xxx KONDSTRT INTERVAL(3)

In the example above, polling is changed to 3 seconds. We recommendsetting the polling parameter to a value that does not exceed 5 seconds.Otherwise, delays in accepting user input may occur.


Chapter 12.Connecting to OMEGAVIEW

OMEGAVIEW is the Candle product that enables you to view and managethe performance levels of your computing systems and alert you toimpending or existing problems. OMEGAVIEW uses Candle monitors andother sources to gather data and present a consolidated view of theperformance levels of local and remote systems and subsystems.

Enhanced Zoom

In OMEGAVIEW you can select a status bar and zoom into a direct sessionwith OMEGAMON II for VTAM so that you can investigate the cause ofthe warning or critical condition indicated. This enhanced zoom featureenables you to automatically navigate to one of several OMEGAMON IIpanels that tell you more about the problem that the status light represents.For a brief overview of the OMEGAVIEW enhanced zoom feature, see thechapter on OMEGAVIEW zoom in the OMEGAMON II for VTAM User'sGuide.

Procedures and Libraries

CICAT configuration updated the OMEGAMON II procedure to include theOMEGAVIEW libraries. CICAT configuration of OMEGAVIEW updatesthe OMEGAVIEW procedure to include OMEGAMON II libraries.

For more information, see the OMEGAVIEW Configuration andCustomization Guide.

Connection

To connect OMEGAMON II to OMEGAVIEW, you must restart theOMEGAMON II address space.

Chapter 12. Connecting to OMEGAVIEW 79

Profile Synchronization

To synchronize the response time options for the OMEGAVIEW collectorsession and the zoomed to OMEGAMON II for VTAM session:

1. An authorized user logs onto OMEGAMON II for VTAM with thecollector session user ID.

2. The authorized user updates the response time options as required forOMEGAVIEW, making sure to specify Start at Logon.

3. Users logged onto OMEGAVIEW while collector session options weremodified must log off and then log on again to OMEGAVIEW.

Result: The response time options for the OMEGAVIEW collector sessionand zoomed to OMEGAMON II for VTAM sessions are automaticallysynchronized. When an OMEGAVIEW user zooms to OMEGAMON II forVTAM, the same response time options that were in effect for theOMEGAVIEW collector session will be in effect for the OMEGAMON IIfor VTAM zoomed to session.

References

For more information about OMEGAVIEW and the enhanced zoom feature,see the OMEGAVIEW documentation set, which includes

� complete instructions for how to customize OMEGAVIEW and beginmonitoring OMEGAMON II status conditions

� maintenance requirements

� zoom procedures

� panel customization


Appendix A.Operator Command KONFCCMD

KONFCCMD commands are required to implement the following in theOMEGAMON II address space:

� the NPALU collector task and the NCP monitor component� the TCP/IP collector task and the TCP/IP component

The appropriate commands are provided in the RKANCMD library.

You define your configuration parameter values during CICAT configurationand CICAT updates the runtime libraries. Usually these Candle-suppliedcommands will suffice.

This appendix describes the arguments and options available withKONFCCMD in case you use this command for other purposes.

Using the KONFCCMD Command

KONFCCMD is an CT/Engine operator command that you can use to do thefollowing to an OMEGAMON II address space:

� Install specific components into specific address spaces.� Start, stop, or display the status of specific components within an address

space.

You can invoke this command in any of the following ways:

� through the MCS console via the MVS modify command� through the specifications in the RKANCMD file� through the KLV operator interface

The command format is

KONFCCMD argument1 argument2 ....... argumentn

Appendix A. Operator Command KONFCCMD 81

Command Arguments

Valid command arguments are as follows:

INSTALL Install the specified feature(s).START Initiate the specified feature(s).STOP Shutdown the specfied feature(s).STATUS Display the status of the specified feature(s).HELP Display how to use this command.

Command Options

You use the following options along with the above arguments:

FPON Install functions specific to the OMEGAMON II addressspace.

FPCT Install functions specific to the NCP collector

NCPC Install, start, stop, or display status of the NCP collector. Thefollowing options are specific to NCPC:

NCPCPATH(LUCS,COLLECTOR=collappl)Specifies the applid of the NCP collector task that talksto other OMEGAMON II address spaces.

NCPCACBN(ncpappl)Specifies the applid of the NCP collector task that talksto the NPALU in the NCP.

NCPCINTV(nn)Specifies the numeric interval, in seconds, for the NCPcollector task sampling rate.

NDMT Install, start, stop, or display status of the NCP Data Manager(NDM) within an OMEGAMON II address space. Thefollowing options are specific to NDMT:

NDMTPATH(LUCS,LOCAL)Specifies the NCP collector task resides in the same(local) OMEGAMON II address space.

NDMTPATH(LUCS, LOCALID=locappl,COLLECTOR=collappl, MODE=mode62)Specifies the NCP collector task resides in a remoteOMEGAMON II address space, where locappl residesin the local address space and talks to collappl whichresides in the remote address space containing the NCPcollector.


SEVT Install functions specific to the VTAM execution environmentfor an OMEGAMON II address space.

SEMV Install functions specific to the MVS execution environmentfor an OMEGAMON II address space.

TCPC Install, start, stop, or display status of the TCP/IP collector.The following option is specific to TCPC:

TCPCVIOU(vio_unit_name)Specifies the VIO unit name for the TCP/IP collector touse when dynamically allocating files. If omitted, thedefault VIO is used.

Guidelines

When using KONFCCMD, adhere to the following guidelines:

� You must use a command argument once per command invocation.

� The first invocation of KONFCCMD must use the INSTALL commandargument. You can accomplish a minimal installation by omitting theINSTALL arguments; you can later enter the desired options.

� You can install, start, stop, or status a number of componentssimultaneously.


KONFCCMD Examples

The examples that follow illustrate the KONFCCMD statements required foreach of three possible OMEGAMON II and NCP collector configurations.Depending on the type of configuration you specify, CICAT builds therequired KONFCCMD statements in the KONSTKON member of

| shilev.RKANSAM.

Variables

The examples include the following variables:

collappl Applid of the NCP collector task that talks to otherOMEGAMON II address spaces to provide NCP data. It isbuilt by CICAT from the specified OMEGAMON II applidprefix.

ncpappl Applid of the NCP collector task that talks to the NPALU toobtain NCP data. It is built by CICAT from the specifiedOMEGAMON II applid prefix.

locappl Applid in the OMEGAMON II without the NCP collector thattalks to the OMEGAMON II containing the NCP collector. Itis built by CICAT from the specified OMEGAMON II applidprefix.

nn NCP collection interval which may be different than thecollection interval specified during CICAT configuration.

mode62 Logmode entry specified during CICAT configuration for theLU 6.2 session between OMEGAMON II and the NCPcollector in another address space.


NCP Collector in OMEGAMON II Address Space

These are the statements required when the NCP collector is included in theOMEGAMON II address space:

KONFCCMD INSTALL SEVT SEMV FPCT FPONKONFCCMD INSTALL NCPC - NCPCPATH(LUCS,COLLECTOR=collappl,NCPCACBN=ncpappl) - NCPCINTV(nn)KONFCCMD START NCPCKONFCCMD INSTALL NDMT - NDMTPATH(LUCS,LOCAL)KONFCCMD START NDMT

NCP Collector in Another OMEGAMON II Address Space

These are the statements required when OMEGAMON II gathers NCPstatistics from the NCP collector in another OMEGAMON II address space.

KONFCCMD INSTALL SEVT SEMV FPCT FPONKONFCCMD INSTALL NDMT - NDMTPATH(LUCS,LOCALID=locappl,COLLECTOR=collappl,MODE=mode62)KONFCCMD START NDMT

OMEGAMON II Client Only

When you do not require OMEGAMON II to gather NCP performancestatistics and the OMEGAMON II address space does not include an NCPcollector, no KONFCCMD statements are required.


Appendix B.CT/Engine Startup Parameters

This appendix consists of CT/Engine initialization and customizationparameters. MINIMUM, MAXIMUM, and RESERVE parameters arerequired for OMEGAMON II. (See “If You Are Configuring for LargerNetworks” on page 45) The other CT/Engine parameters are listed here foryour information only. Candle does not recommend that you modify any ofthe other parameters.

CT/Engine Startup Parameters

CT/Engine startup parameters are defined with appropriate defaults in thedata set pointed to by the RKLVIN DD statement. CT/Engine startupparameters specify the execution and resource management environment.

You may override certain CT/Engine operating parameters at initializationtime by coding the parameters in RKLVIN or the EXEC PARM field of theJCL. JCL specification PARMs override RKLVIN parameters.

AMODE31

AMODE31(Y | N)

Determines whether CT/Engine runs in 31-bit addressing mode. Y is thedefault for MVS/XA and MVS/ESA. N is the default for MVS/SP.

If MVS/XA is running under VTAM prior to Version 3.1.1 or DFP prior toVersion 1.2, code the following:

AMODE31(N)

APF

APF(Y | N)

Determines whether CT/Engine runs as APF-authorized. Y is the default ifthe CT/Engine job step is APF-authorized; otherwise, N is the default.

Note: If you specify Y, the CT/Engine job step must be APF-authorized.

Appendix B. CT/Engine Startup Parameters 87

CONFIRM

CONFIRM(15 | n)

Sets the maximum number of seconds between two successive SHUTDOWNcommands or MVS STOP (P) commands to terminate the CT/Engine addressspace.

CONFIRM(0) allows CT/Engine shutdown to begin immediately without anadditional, confirming SHUTDOWN command.

CONFIRM(n) prevents accidental shutdowns by requiring you to confirm thecommand by entering it a second time within the specified number ofseconds.

For example, the default (15) requires you enter SHUTDOWN twice within15 seconds to terminate the CT/Engine address space.

CONSECHO

CONSECHO(N | Y)

Determines whether CT/Engine command output is routed back to theoriginating MVS operator console.

N causes all output from commands issued via the MVS MODIFY commandor subsystem consoles to be routed only to the master console and thoseconsoles which are receiving the appropriate MVS route codes.

Y causes the command output to be routed specifically to the originatingconsole, as well as the master and other consoles. By coding Y, productssuch as NetView and AF/OPERATOR are able to review the output ofCT/Engine commands.

DATEFMT

DATEFMT(MMDDYY | DDMMYY | YYMMDD)

Specifies the format of dates displayed by CT/Engine in the &SYSDATEdialog variable. Possible values are:

MMDDYY U.S. formatDDMMYY European formatYYMMDD International format


DEBUG

Important

Do not modify this parameter except under the guidance of aCandle support representative.

DEBUG(N | Y)

Specify Y to use the debug option for resolving internal problems.

DEBUG(Y) automatically turns on the internal trace with the default numberof entries (2048). See “TRACE” on page 101 for more information.

DEBUG(Y) will cause an increase in CPU and storage use, as well as theissuance of more messages. The amount of the increase depends on theactivity within the address space.

INBDLIM

INBDLIM(25 | n)

Specifies the maximum number of messages that can be queued for a sessionbetween an application and CT/Engine. If this number is exceeded, thesession terminates.

INBDLIM prevents applications from flooding CT/Engine with messages,which causes CT/Engine to run short of storage and abend. By specifying alarge value, an application that sends many outbound datastreams to aterminal without requesting input can cause CT/Engine to abend, even ifdefinite response is not specified for the session.

Most file transfer programs implement handshaking protocols that requirethem to perform read operations. These programs should not be affected bya small INBDLIM value.

Note: INBDLIM limits the number of messages an application sends toCT/Engine (the virtual terminal). OUTBDLIM limits the number ofmessages CT/Engine sends to the physical terminal.

INBOUND

INBOUND(248 | n)

Specifies the size of all VTAM RECEIVE buffers, regardless of origin.


If the length of a received RU is larger than the value assigned toINBOUND, excess path lengths result. If the value assigned to INBOUNDis much larger than the length of the RUs received, storage problems mayresult.

If you are running above VTAM 1.3, do not modify the INBOUNDparameter.

INITIAL

INITIAL(membername)

Identifies the command list (CLIST) that contains CT/Engine initializationcommands. membername is a member in the RKANCMD library. There isno hard-coded default.

RKANCMD may contain a member named smfid, where smfid is the SMFID of the CPU executing CT/Engine. If this member exists, it isautomatically invoked before the command list specified in the INITIALparameter.

INITLIST

INITLIST(membername)

Identifies the member of RKANPAR which contains initialization membername overrides. Normally, CT/Engine initialization modules read membersof RKANPAR whose names are the same as the modules. The memberidentified by the INITLIST keyword contains statements such as:

startup-module-name=override-name

Each line of the INITLIST member names a particular startup module andidentifies the member of RKANPAR which should be read by that modulefor its parameters. The valid startup module names vary with theCT/Engine-based products that are installed. The number of startup modulesmay also change as new features are added or new products becomeavailable. As a result, it is not possible to provide a comprehensive list ofstartup module names.

No wild-card characters are accepted during INITLIST processing. Eachoverride must be coded in full. Override statements must be coded one perline. The statements may appear in any column. Input will be converted toupper case prior to processing. Comment lines are indicated by an asteriskas the first non-blank character. On any line, anything following an asteriskis ignored.


Here is a sample input line:

KLVINNAM=NAMINITK * Override KLVINNAM parameter member name

If multiple override statements for the same startup module are present, thelast one will determine the member name to be used. No messages will beissued.

RKANPAR may contain a member named smfid, where smfid is the SMF IDof the CPU executing CT/Engine. If this member exists, it will be used asthe list of initialization member name overrides if the INITLIST keyword isnot coded. When INITLIST is coded, a member of RKANPAR named smfidwill not be read even if present in the library.

INTLCHAR

INTLCHAR(N | Y)

Implements the following national language support features:

1. The window vertical bar character (|) is changed from X'6A' to X'4F'.

2. Characters with diacritical marks that were previously interpreted asinvalid are now valid.

LIMIT

Important


LIMIT(16,P | n,P)LIMIT(16,X | n,X)

Specifies the largest block of primary (P) or extended (X) storage that can beallocated. This value is specified in bytes, as a power of 2. For example, ifn is 16, the largest block that can be allocated is 65,536 bytes.

Primary storage is below the 16-megabyte line; extended storage is above theline. To specify values for both primary and extended storage, include theLIMIT parameter twice in RKLVIN:

LIMIT(n,X)LIMIT(n,P)


If the LIMIT value is too small and a process in CT/Engine attempts toallocate a block of storage larger than LIMIT specifies, program interruptionU0100 or U0200 results. Too large a LIMIT value may waste storage andincrease processing overhead.

LOGBLOCK

LOGBLOCK(312K | n)

Specifies, in bytes, the block size of the CT/Engine RKLVLOG file.

LOGBUFS

Important


LOGBUFS(2 | n)

Specifies the number of buffers to allocate for the CT/Engine RKLVLOGfile.

If the value of LOGBUFS is small and extensive logging is performed (forexample, during debugging), CT/Engine response may suffer because ofexcessive physical I/O. If the value of LOGBUFS is large, storage shortagesmay occur.

LSRPOOL

LSRPOOL(size,count[,K | hiper])

No default; however, you must code at least one LSRPOOL parameter inorder for CT/Engine to start.

Corresponds to the BUFFERS parameter of the BLDVRP macro instruction,and specifies the number of buffers to be made available for each VSAMdataset used by CT/Engine.

size is a buffer (VSAM control interval) size. Valid sizes are 512, 1024,2048, 4096, 8192, 12288, 16384, 20480, 24576, 28672, and 32768.

count is the number of virtual storage buffers of size to be allocated. Theminimum is 3. The maximum is 65535, although this may be less,


depending on the amount of available virtual storage in the CT/Engineaddress space. Buffers will be allocated from extended storage ifAMODE31(Y) was coded or defaulted to; from primary storage otherwise.

hiper is the number of hiperspace buffers of size to be allocated. Theminimum is 0 (no hiperspace buffers). The maximum is 16777215, althoughthis may be less, depending on the hiperspace storage available to IBMVSAM services. Ensure the CT/Engine address space is non-swappablewhen you are using hiperspace buffers.

Note: IBM restricts hiperspace buffers to multiples of 4K. Do not codehiper for the 512, 1024, or 2048 sizes; an error message will be issued andCT/Engine startup will terminate.

For best storage use, code an LSRPOOL parameter for each different VSAMcontrol interval size that CT/Engine uses:

� index buffer for NAM and table database� data buffer for NAM and table database� data buffer for VIEWLOG

Candle distributes the recommended values in the RKLVIN dataset.

Note: You must enter LSRPOOLs individually; you cannot string them.

If you receive many KLVVS026 messages identifying buffer contention,increase the number of buffers allocated to the dataset identified in theassociated KLVVS021 messages.

LSRSTRNO

LSRSTRNO(32 | n)

Corresponds to the STRNO parameter of the BLDVRP macro instruction. Itis the maximum number of concurrent VSAM requests that CT/Engine canprocess against all the VSAM datasets allocated to it.

If you receive many KLVVS026 messages identifying string contention, or ifthe STRMAX value in the KLVVS002 messages issued during CL/ENGINEshutdown is consistently the same as the value in RKLVIN, increase theLSRSTRNO value.

The minimum value is 1. The maximum is 255.


MAXIMUM

MAXIMUM(8192,P | n,P)MAXIMUM(n,X)

The default value for extended storage (X) is the value specified by theMINIMUM keyword.

MAXIMUM is a storage throttle used to prevent GETMAINs fromoverallocating and occupying the page dataset with rarely referenced frames.

The variable n represents the maximum amount (in kilobytes) of primary orextended storage that can be allocated. X stands for extended storage (abovethe 16-megabyte line), and P stands for primary storage (below the line).

Set your MAXIMUM value to a value that will allow CT/Engine to continuerunning without overloading your page volumes when the steady-stateMINIMUM value is exceeded.

To use extended storage, you must do both of the following:

� Code the MINIMUM parameter.� Make sure that MAXIMUM is equal to or greater than MINIMUM +

RESERVE.

If MAXIMUM is too large and RESERVE is not large enough to meetyour requirements, the address space may run out of virtual storage.

If the value of MAXIMUM is greater than that of MINIMUM, CT/Engineattempts a conditional GETMAIN for the MAXIMUM value minus theRESERVE value (RESERVE defaults to 512,P.). If the MAXIMUM value isnot satisfied, CT/Engine accepts the amount of storage acquired by theGETMAIN.

MINIMUM

MINIMUM(1K24,P | n,P)MINIMUM(8192,X | n,X)

n represents the mimimum amount (in kilobytes) of primary or extendedstorage that can be allocated.

For example, to specify a 16-megabyte above-the-line region, code

MINIMUM(16384,X)

To specify a 32-megabyte above-the-line region, code

MINIMUM(32768,X)


To use extended storage, you must do both of the following:

� Code the MINIMUM parameter.� Make sure that MINIMUM + RESERVE is less than or equal to

MAXIMUM.

Note the following about the default above-the-line region:

� Specified in the IEFUSI and IEALIMIT MVS modules.� Distributed by IBM as 32 megabytes.� If smaller than the amount specified for the MINIMUM parameter, do

one of the following:– Alter the default.– Use the REGION parameter as follows:

0K or 0M All primary and extended storage is availablefor GETMAIN.

Up to 16M Primary region equals the specified value;extended region equals the default.

Up to 32M All available region goes to primary storage;extended region equals the default.

Above 32M All available region goes to primary storage;specified value goes to extended storage.

In general, Candle recommends REGION=0M.

OPLIMIT

OPLIMIT(K | n)

Specifies the maximum number of characters that can be queued to a singleCT/Engine operator before the messages are bypassed. The default (0) is nolimit.

OPLOCAL

OPLOCAL(REPLY,ERROR | messagetype,messagetype,...)

Specifies the types of messages an operator console receives in response toactions initiated by that same console.

With the default OPLOCAL setting, an operator performing an action thatgenerates a CT/Engine ALERT message does not receive the message at theconsole unless OPMASK allows it. For information on message types, seeOMEGAMON II for VTAM Messages Manual.


OPMASK

OPMASK(INFO,WARN,ALERT | messagetype,messagetype,...)

Specifies the types of unsolicited messages all operator consoles receive. Forinformation on message types, see OMEGAMON II for VTAM MessagesManual.

OPSTART

OPSTART(command)

Specifies an initial CT/Engine command or CLIST to be issued after anoperator logs on. There is no default. command is a member in theRKANCMD library.

OUTBDLIM

OUTBDLIM(5KK | n)

Specifies the maximum number of messages that can be queued for a sessionbetween CT/Engine and the physical terminal. If this number is exceeded,the session terminates.

The purpose of OUTBDLIM is to prevent excessive messages from causingCT/Engine to run short of storage and abend. If you specify a very largevalue for OUTBDLIM, an application that sends many outbound datastreamsto a terminal without requesting input can cause CT/Engine to abend, even ifdefinite response is not specified for the session.

Note: OUTBDLIM limits the number of messages CT/Engine sends to thephysical terminal. INBDLIM limits the number of messages an applicationsends to CT/Engine (the virtual terminal).

OUTBOUND

OUTBOUND(5K4 | n)

Specifies, in bytes, an outbound RU buffer length for VTAM sessions forwhich a length is not provided in the session parameters.


PACK

Important

Do not code this parameter except under the guidance of a Candlesupport representative.

PACK(Y | N)

Determines how CT/Engine loads modules into the CT/Engine region:

omitted Specifies that modules are placed into the next availabledoubleword storage location. If the address space isAPF-authorized, an MVS directed load is used and MVSCDEs are available; otherwise CT/Engine performs apseudo-directed load and no CDEs are created.

Y CT/Engine performs a pseudo-directed load to place modulesinto the next available doublword storage location. No MVSCDEs are created.

N Modules are loaded using standard MVS LOAD macros.MVS CDEs are created. Most CT/Engine-based modules arelinkedited on a page boundary; PACK(N) honors thatboundary, and therefore will require a larger CT/Engineregion.

QUIESCE

QUIESCE(9K,P,F | n,P,F)QUIESCE(95,P,C | n,P,C)QUIESCE(9K,X,F | n,X,F)QUIESCE(95,X,C | n,X,C)

Sets thresholds for slowing down allocation of storage. When the thresholdsare exceeded, quiesce mode goes into effect, causing rejection of allconditional storage requests. Conditional storage requests include session anddialog startup, as well as other functions that can recover from a storageshortage. Unconditional requests for storage continue to be satisfied inquiesce mode.

The variable n represents the percentage of primary (P) or extended (X), free(F) or carved (C) storage allowed to be allocated before quiesce mode takeseffect. Carved storage is storage put into use for the first time and allocatedto a specific size; free storage is storage that has been carved but is not inuse. Primary storage is below the 16-megabyte line; extended storage isabove the line.


A value of zero (0) indicates no QUIESCE threshold, which means quiescemode never goes into effect. A value of 100 indicates that all storage mustbe used or carved before quiesce mode takes effect.

To specify that quiesce mode takes effect when 80% of the total amount ofstorage is in use in extended storage, enter the following:

QUIESCE(8K,X,F)

To specify that quiesce mode takes effect when 90% of the total amount ofprimary storage has been carved, enter the following:

QUIESCE(9K,P,C)

When CT/Engine detects that the amount of storage carved or in use is abovethe QUIESCE threshold percentage, it enters quiesce mode and does notpermit new dialogs or sessions to start. For free storage, quiesce modecontinues until the amount of storage in use drops below a recovery point,calculated as follows:

Recovery point = Threshold amount - ((MAXIMUM - Threshold amount) / 2)

For example, with a MAXIMUM of 10 megabytes and a QUIESCE value of90:

Recovery point = 9M - ((1KM - 9M) / 2) = 8.5M

For carved storage, quiesce mode has no recovery point. Until CT/Engine isrecycled, no new sessions or dialogs can be started. However, existingsessions and dialogs continue to operate normally.

You can use the STGMON parameter to control reporting on quiesce modeconditions. See “STGMON” on page 100.

RESERVE

RESERVE(512,P | n,P)RESERVE(2K48,X | n,X)

The variable n represents the number of kilobytes of primary (P) or extended(X) storage to set aside for other routines that may perform their ownGETMAINs in the CT/Engine address space (for example, ACF2 andRACF). The default for primary storage (P) is 512. The default forextended storage (X) is 2048. Primary storage is below the 16-megabyteline, and extended storage is above the line.

To specify values for both primary and extended storage, include theRESERVE parameter twice in RKLVIN:


RESERVE(n,X)RESERVE(n,P)

If the RESERVE value is larger than the MINIMUM value, CT/Engineterminates. The total of the MINIMUM and RESERVE values must be lessthan or equal to the MAXIMUM value.

If you have ACF2 or RACF installed, the default setting (512,P) supportsabout 500 users. ACF2 and RACF use approximately 1K of primary storageper logged-on user. If your RESERVE value is too small, you mayencounter IST566I messages from VTAM or S80A, S878, S066, S40D, orS0F9 abends.

SDUMP

SDUMP(Y | N | S | M)

Determines whether or not SVC dumps are generated. If the CT/Engine jobstep is APF-authorized, the default is Y. Otherwise, the default is N, andyou must APF-authorize the CT/Engine job step before you can specifySDUMP(Y).

Y Specifies that an SVC dump is to be directed to a systemdump dataset (SYS1.DUMPxx).

To capture an entire SVC dump, perform these steps:

1. Ensure that the SYS1.DUMPxx datasets are large enoughto hold the contents of the CT/Engine address space.

2. Determine the size of the CT/Engine address space.

3. Provide enough DASD in the SYS1.DUMPxx datasets toaccommodate the SDUMP requirements.

For MVS/ESA 3.1.3 and higher, SDUMP writes an unblocked4160-byte record for each page of virtual storage beingdumped. For earlier versions of MVS, the record size is 4104bytes.

Candle recommends these storage guidelines for SVC DUMPdatasets:

� Allocate 32 meg if 16 to 32 meg are specified in RKLVINfor MINIMUM/MAXIMUM keywords.

� For each additional 16 meg specified in RKLVIN forMINIMUM/MAXIMUM keywords, add 25 meg for theSVC DUMP dataset.

For example:


MINIMUM (16384,x) - Allocate a 32 meg SVC DUMP datasetMINIMUM (32768,x) - Allocate a 57 meg SVC DUMP datasetMINIMUM (49152,x) - Allocate a 82 meg SVC DUMP datasetMINIMUM (65536,x) - Allocate a 1K7 meg SVC DUMP dataset

N Specifies that a formatted dump should be directed to theRKLVSNAP dataset. Formatted dumps should be avoidedwhen possible; they disable the CT/Engine address space for alonger period of time than either SVC dumps orSYSMDUMPs, and are more difficult to analyze.

S Specifies that a summary dump only should be directed to theRKLVSNAP dataset. A summary dump consists of an abendsummary and a dispatcher summary only. Warning:Summary dumps do not provide enough information to allowproblems to be analyzed. SDUMP(S) is provided only forvery specific testing purposes, where it is known that a dumpwill not be needed.

M Specifies that the system should take an ABEND dump to adataset defined with the SYSMDUMP ddname. This type ofdump is not formatted by the operating system and must beanalyzed with IPCS. Only the first dump taken will becaptured on the SYSMDUMP dataset unless the JCL specifiesDISP=MOD, in which case multiple dumps may be collectedon the same dataset.

CT/Engine automatically initializes the SYSMDUMP datasetwith an end-of-file mark at initialization. If DISP=SHR orDISP=OLD is specified for the SYSMDUMP dataset, existingdumps will be overwritten. If DISP=MOD is specified, thesystem will write the dump following any previous dumps.

If SDUMP(M) is specified and the SYSMDUMP DDNAME ismissing, or the initialization fails, startup is aborted.

Note: The CT/Engine address space need not beAPF-authorized to take a SYSMDUMP. For more informationregarding SYSMDUMP specification, refer to IBM's Planning:Problem Determination and Recovery.

STGMON

STGMON(15 | n)

Specifies the number of minutes between storage quiesce mode messagedisplays. Any value between 0 and 120 is valid. A value of 0 results inmessages being issued only when a short-on-storage condition is detected orrelieved (for example, when the quiesce mode state changes).


SWAP

SWAP(N | Y)

Specifies whether the CT/Engine job step is APF-authorized and theCT/Engine region is swappable. The default is N if the CT/Engine job stepis APF-authorized. Otherwise, it is Y.

TASKS

Important


TASKS(n)

Default is the number of available processors.

Specifies the number of general-purpose subtasks to be attached in theCT/Engine address space. If CT/Engine is running on a multiprocessor, theTASKS default increases both throughput and CPU usage. Reducing thenumber of tasks decreases both throughput and CPU usage.

In general, reduce the value of TASKS only when CPU usage is a concernand system paging is low, since fewer tasks will be available for performingwork whenever other tasks are in a page-fault wait.

TRACE

Important


TRACE(11 | n)

Specifies, as the exponent of 2, the number of internal trace table entries toreserve. Each entry consists of 32 bytes. For example, TRACE(12) reserves4096 trace entries.

If TRACE is not specified, no internal trace table will be allocated unlessDEBUG(Y) is specified, in which case a default trace value of 11 is used,reserving 2048 trace table entries.


The internal trace table is included in a dump and provides useful diagnosticinformation for Candle Customer Support. Elements that are included in theinternal trace table are controlled by the CT/Engine TRACE operatorcommand. Contact Candle Customer Support for information about thiscommand.

UPPERDLG

UPPERDLG(N | Y)

Determines whether or not SSPL dialog output is folded to upper case beforedisplaying on users' terminals.

Candle recommends that you specify Y only if your users' terminals displayKanji or other special characters in place of lowercase characters.

UPPERLOG

UPPERLOG(N | Y)

Determines whether or not output from the LOG SSPL dialog function isfolded to upper case. (LOG output is written to RKLVLOG.)

Candle recommends that you specify Y only if your terminals display Kanjior other special characters in place of lowercase characters.

UPPERWTO

UPPERWTO(N | Y)

Determines whether or not output from the WTO SSPL dialog function isfolded to upper case. (WTO output is written to the MVS consoles.)

Candle recommends that you specify Y only if your MVS consoles displayKanji or other special characters in place of lowercase characters.

WTO

WTO(Y | N)

Determines whether or not CT/Engine issues WTOs.


WTOs write information and exception condition messages to the operatorconsoles. ALERT messages are always written to the consoles.

Note: WTO(N) will suppress messages written with the WTO SSPL dialogfunction.

WTODC

WTODC(ALERT,2 | type,code,code,...)

Specifies WTO descriptor codes for CT/Engine message types.

Specify one WTODC parameter for each CT/Engine message type. Forexample, to assign descriptor code 7 (Application Program/Processor) toCT/Engine error messages, enter the following:

WTODC(ERROR,7)

For definitions of the descriptor codes, see IBM's Supervisor Services andMacro Instructions manual. For information on message types, seeOMEGAMON II for VTAM Messages Manual.

WTORC

WTORC(ALERT,1,8,11 | type,code,code,...)

Specifies WTO route codes for for CT/Engine message types. Specify theWTORC parameter for each CT/Engine message type.

For definitions of the route codes, see IBM's Supervisor Services and MacroInstructions manual. For information on message types, see OMEGAMON IIfor VTAM Messages Manual.


Appendix C.Candle Customer Support

Introduction

Candle Corporation offers a comprehensive maintenance and support plan toensure you realize the greatest value possible from your Candle softwareinvestments. We have more than 200 technicians worldwide, committed toproviding you with prompt resolutions to your support requests.

Customer Support hours of operation are from 5:30 A.M. to 5:00 P.M.,Pacific Time. In the event of an after-hours or weekend emergency, Candle'scomputerized call management system ensures that a technician will returnyour call within one hour. For customers located outside of North America,after-hours and weekend support is provided by Candle Customer Supportlocations in the United States.

Electronic Support

Candle provides information and support services using

� Candle's home page at www.candle.com. You can use the Candle Website to

– open problem records– access maintenance information– order products or maintenance– access IBM compatibility information– download fix packs for distributed products– read news and alerts– scan a list of scheduled Candle education classes

� Candle Electronic Customer Support (CECS), an electronic customersupport facility. You can access this facility through the IBM GlobalNetwork. You can use CECS to

– open problem records– search our database for solutions to known problems– look for answers to commonly asked questions– read news and alerts– scan a list of scheduled Candle education classes

Both CECS and the Candle Web site are available 24 hours a day, 7 days perweek.

Appendix C. Candle Customer Support 105

Telephone Support

Our support network consists of product specialists who work with you tosolve your problem.

Candle uses an online problem management system to log and track allsupport requests. Your request is immediately routed to the appropriatetechnical resource.

When you call to report a problem, please have the following information:

� your Candle personal ID (PID) number

� the release level of the Candle product

� the release level of IBM or other vendor software

� identifying information and dates of recently applied maintenance to yourCandle product or IBM product

� a detailed description of the problem (including the error message) andthe events preceding the problem

� a description of any unusual events that occurred before the problem


Customer Support Phone Numbers

Telephone Fax

North America (800) 328-1811

(310) 535-3636 (310) 727-4204

Europe

Belgium/Luxembourg +32 (0) 3 270 95 60 +32 (0) 3 270 95 41

France +33 (0) 1 53 61 60 60 +33 (0) 1 53 61 06 16

Germany/Switzerland/Austria

+49 (0) 89 54 554 333 +49 (0) 89 54 554 170

Italy - Freephone 800 780992

Netherlands +31 (0) 30 600 35 50 +31 (0) 30 600 35 10

Scandinavia +46 (0)8 444 5940 +46 (0)8 623 1855

U.K. +44 (0)161 437 5224 +44 (0)161 437 5225

(Southern Europe, Middle East and South Africa Agents call U.K.)

Asia Pacific - English Hub

+61 2 9954 1818

Australia +61 2 8912 9898

Hong Kong 800 908 457

India +61 2 8912 9898

Indonesia 0018 03061 2061

Malaysia 1800 803 459

New Zealand 0800 449 596

Philippines 1800 1612 0096

Singapore 800 616 2075

Thailand 0018 00612 1045

Asia Pacific - Japanese Hub

+81 3 3595 7150 +81 3 3595 7110

Asia Pacific - Korean Hub

+82 2 552 8744 +82 2 552 8746

Asia Pacific - Mandarin Hub

+88 62 2739 3223 +88 62 2378 5993

Asia Pacific e-mail address: [email protected]

When your local support office is unavailable, you can contact Candle'sNorth America support center. If USADirect service is available in yourcountry, use the 800 telephone number. If USADirect service is notavailable, ask your international operator for assistance in calling Candle'slocal (310) number.

Appendix C. Candle Customer Support 107

Incident Documentation

You may be asked to send incident documentation to the Candle CustomerSupport Center. On the outside of all packages you send, please write theincident number given to you by the Customer Support representative.

Send tapes containing the incident information to the following address,unless directed otherwise by your Customer Support representative:

Candle Customer SupportCandle Support Center, Incident number2K1 North Douglas StreetEl Segundo, CA 9K245

Send all other relevant documentation, such as diskettes or paperdocumentation, to the address provided by your Customer Supportrepresentative.

Ensuring Your Satisfaction with Customer Support

Candle Customer Support is committed to achieving high customersatisfaction ratings in all areas. These include

� connecting you to a support representative promptly� providing you with the appropriate fixes� answering support questions� filling your shipping orders� supplying documentation

If you have a concern that has not been resolved to your satisfaction, you canopen a complaint ticket. All tickets are logged and tracked to ensureresponsiveness and closure. Using the ticket information, a manager willcontact you promptly to resolve your problem.


Index

A

abend S306 39about this document 9ACF2

See CA-ACF2ACID parameter 72activate

dedicated terminal 77major node 50NCP 59

Adobe portable document format 10AF_UNIX domain 43agent, SNMP 42, 43allocating

terminal dynamically 77AMODE31

RKLVIN parameter 87APF

authorization 39RKLVIN parameter 87

applid, NCP collector 58authorize TRACERTE command 42authorizing users 70

external function level security 74

B

BPXPRMxx member 43

C

CA-ACF2 71Candle Electronic Customer Support

(CECS) 105carved storage 97CA-TOP SECRET 72changes, exception record 76CICAT 28

help 27OMEGAVIEW configuration 79

collection, NCP data 17, 18, 19, 57collector session profile, OMEGAVIEW 80

community name 43configuration

dynamic, NCP 55KONFCCMD usage 81NCP generation 58NPALU macro definitions 58OMEGAMON II and NCP collector 17SMF considerations 75terminal pool prefix 58

configuration with CICAT 29CONFIRM

RKLVIN parameter 88connection, OMEGAVIEW 79CONSECHO

RKLVIN parameter 88considerations

ETE 61TCP/IP 42

console support 65control points 69controlling ETE 61conventions, documentation 11CSA tracking 42CT/Engine

initialization 87–103AMODE31 parameter 87APF parameter 87CONFIRM parameter 88CONSECHO parameter 88DATEFMT parameter 88DEBUG parameter 89INBDLIM parameter 89INBOUND parameter 89INITIAL parameter 90INITLIST parameter 90INTLCHAR parameter 91LIMIT parameter 91LOGBLOCK parameter 92LOGBUFS parameter 92LSRPOOL parameter 92LSRSTRNO parameter 93MAXIMUM parameter 94MINIMUM parameter 94OPLIMIT parameter 95OPLOCAL parameter 95OPMASK parameter 96OPSTART parameter 96

Index 109

CT/Engine (continued)initialization (continued)

OUTBDLIM parameter 96OUTBOUND parameter 96PACK parameter 97QUIESCE parameter 97RESERVE parameter 98SDUMP parameter 99STGMON parameter 100SWAP parameter 101TASKS parameter 101TRACE parameter 101UPPERDLG parameter 102UPPERLOG parameter 102UPPERWTO parameter 102WTO parameter 102WTODC parameter 103WTORC parameter 103

KONFCCMD command 81startup 87–103

customer support 105customization

console support 65dedicated mode 77End-to-End 61larger networks 45memory management 45NCP defintions 56requirements for each mode 20security 69set thresholds and exceptions 67

D

data collection, NCP 18, 56, 57DATEFMT

RKLVIN parameter 88DB parameter 71, 72deactivate dedicated terminal 78deallocate terminal dynamically 78DEBUG

RKLVIN parameter 89DEDICATE command 77, 78dedicated mode 20, 77–78dedicated operating mode 20dedicated terminal, activate 77define terminal at startup 77disabling

End-to-End 62NCP data collection 59

documentation conventions 11documentation set 13DROP command authorization 42dumps 99DUPLEX parameter, NCP gen 56dynamic configuration, NCP 55dynamic terminal

allocation 77deallocation 78

E

electronic customer support 105enabling

console support 65End-to-End 61NCP data collection 59

encrypted security, NAM 69End-to-End

considerations 61disabling 62enabling 61quiesce 49references 63rules 61start 49SYSTEMS argument 49variable $$ETE 61

End-to-End Response Time FeatureSee End-to-End

enhanced zoom, OMEGAVIEW 79ETE

See End-to-End$$ETE variable 61exception

record changes 23, 76settings 67

EXIT parameter 71extended storage 97external security resource class 73external security resource names 73

F

FACILITY ACID 72FACILITY statements 72finalizing security 69


format changes, exception record 76FPCT parameter 82FPON parameter 82free storage 97free storage remaining 46function level security 52, 73functions secured externally 73

G

generation parameters, NCP 56

H

help, CICAT 27historical reporting

SMF 75

I

IBMTCP/IP address space 42

INBDLIMRKLVIN parameter 89

INBOUNDRKLVIN parameter 89

INITIALRKLVIN parameter 90

initialization 51CT/Engine 87–103

AMODE31 parameter 87APF parameter 87CONFIRM parameter 88CONSECHO parameter 88DATEFMT parameter 88DEBUG parameter 89INBDLIM parameter 89INBOUND parameter 89INITIAL parameter 90INITLIST parameter 90INTLCHAR parameter 91LIMIT parameter 91LOGBLOCK parameter 92LOGBUFS parameter 92LSRPOOL parameter 92LSRSTRNO parameter 93MAXIMUM parameter 94MINIMUM parameter 94OPLIMIT parameter 95

initialization (continued)CT/Engine (continued)

OPLOCAL parameter 95OPMASK parameter 96OPSTART parameter 96OUTBDLIM parameter 96OUTBOUND parameter 96PACK parameter 97QUIESCE parameter 97RESERVE parameter 98SDUMP parameter 99STGMON parameter 100SWAP parameter 101TASKS parameter 101TRACE parameter 101UPPERDLG parameter 102UPPERLOG parameter 102UPPERWTO parameter 102WTO parameter 102WTODC parameter 103WTORC parameter 103

error 39NAM 51

INITLISTRKLVIN parameter 90

INSTALL parameter 82installation

command KONFCCMD 81verification 49

INTERVAL parameter 78interval, dedicated mode polling 78INTLCHAR

RKLVIN parameter 91

K

keywords, NCP macro 56KLVA2NEV exit 71KONASM member 71KONCTNPA member 58KONFCCMD command 59, 81KONINNAM member 69, 70, 71, 72KONRRT ddname 18KONSRC ddname 18KONSTKON member 77KONSYSIN member 45

Index 111

L

larger networks 45libraries

APF-authorize 39RKANMODL 71RKANPAR 45, 69, 71

LIMITRKLVIN parameter 91

line utilization 56local NCP collection 17, 18LOCALID parameter 82LOGAPPL keyword 58LOGBLOCK

RKLVIN parameter 92LOGBUFS

RKLVIN parameter 92logon, OMEGAMON II 52LSRPOOL

RKLVIN parameter 92LSRSTRNO

RKLVIN parameter 93

M

macroNCP gen keywords 56NPALU definition 58

major node, OMEGAMON II 50Management Information Block (MIB) 43MAXCOLL keyword 58MAXIMUM

OMEGAMON II memory management 45,87

RKLVIN parameter 94memory management 45message

quiesce 100storage 100

migrationRKONNAM file 22RKONTDB file 22SAS databases 23

MINIMUMOMEGAMON II memory management 46,

87RKLVIN parameter 94

MODE=FAIL parameter 72

modem speed 56MODIFY command, MVS 51, 69monitoring options 52, 67, 75multiple user single address space system

(MUSASS) 71MUSASS 71MVS/ESA for TCP/IP 42

N

NAM 22adding users 69customization 69database 69encrypted security 69initialization 51password 51security system 69user ID 51, 70variable $$ETE 61

NCPactivating 55collection

applid 58configurations with OMEGAMON II 17generation 58KONFCCMD command usage 81requirements 55

Data Manager 82disabling data collection 59dynamic configuration 55enabling data collection 57, 59generation 56, 58NPACOLL parameter 57NPALU connection 58requirements 55, 56resource resolution table 18sift down 56source library, NDF 18with NetSpy 55with NPM 55

NCPC parameter 82NCPCACBN parameter 82NCPCINTV parameter 82NCPCPATH parameter 82NDF source library 18NDM

See NCP Data Manager


NDMT parameter 59, 82NDMTPATH parameter 82NetSpy

with NCP component 55Network Access Manager

See NAMNODB parameter 70, 71, 72non-English terminals 25NORACF parameter 72NPACOLL parameter, NCP gen 56, 57NPALU

application 55definition 58KONFCCMD command usage 81macro definitions 58NCP collector connection 58usage 55

NPATP parameter, NCP gen 56NPM with NCP component 55

O

OBEY command 42OMEGAMON II

KONFCCMD command usage 81libraries in OMEGAVIEW proc 79logon 52OMEGAVIEW libraries in proc 79performance 57with NetSpy 55with NPM 55

OMEGAVIEWconnection 79OMEGAMON II libraries 79procedure 79references 79synchronizing profile with 80zoom 79

OMVS segment 42operating mode requirements 20operator command, KONFCCMD 81OPLIMIT

RKLVIN parameter 95OPLOCAL

RKLVIN parameter 95OPMASK

RKLVIN parameter 96OPSTART

RKLVIN parameter 96

options, monitoring 67OS/390 42OUTBDLIM

RKLVIN parameter 96OUTBOUND

RKLVIN parameter 96

P

PACKSYSIN parameter 97

parametersCT/Engine 87OMEGAMON II startup

MAXIMUM 45MINIMUM 46RESERVE 46

performance, OMEGAMON II 57polling interval 78portable document format, Adobe 10primary storage 97PROCLIB

OMEGAMON II proc 79OMEGAVIEW proc 79

product components 16profile synchronization with OMEGAVIEW 80profiles for users 69

Q

quiesceETE 49recovery point 97RKLVIN parameter 97state change messages 100threshold 97

R

RACF 70RACF parameter 70, 72record layouts, SMF 76region size 45remote NCP collection 17, 19reporting

See historical reportingrequirements, external function level security 73

Index 113

RESERVEOMEGAMON II memory management 46,

87RKLVIN parameter 98

resource names, external security 73resource resolution table 18response time profiles 80restart OMEGAMON II 70RKANCMD library 77, 81RKANMODL library 71RKANPAR library 45, 59, 69, 71, 72, 87

KONSTKON member 59RKANSAM library 58, 71RKLVIN 87–103

AMODE31 87APF 87CONFIRM 88CONSECHO 88DATEFMT 88DEBUG 89INBDLIM 89INBOUND 89INITIAL 90INITLIST 90INTLCHAR 91LIMIT 91LOGBLOCK 92LOGBUFS 92LSRPOOL 92LSRSTRNO 93MAXIMUM 94MINIMUM 94OPLIMIT 95OPLOCAL 95OPMASK 96OPSTART 96OUTBDLIM 96OUTBOUND 96QUIESCE 97RESERVE 98SDUMP 99STGMON 100SWAP 101TASKS 101TRACE 101UPPERDLG 102UPPERLOG 102UPPERWTO 102WTO 102WTODC 103WTORC 103

RKONNAM library 70, 71, 72rules, ETE 61

S

S306 abend 39SAS

customization 23migration 23

SDUMPRKLVIN parameter 99

securityalternative to User Authorities 73CA-ACF2 71CA-TOP SECRET 72finalizing 69function level 73interfaces supported 23NAM 69RACF 70user authorities 70user IDs 70

SEMV parameter 83set thresholds and exceptions 67SEVT parameter 83short-on-storage 97, 100sift down, NCP gen 56SIGN parameter 72SMF

changes 23considerations 23, 75exception records 23programs using 23record layouts 76recording options 75revisions 23trend/exception records 75

SNMP agent and subagent 42, 43source library, NCP 18speed of modem 56SPEED parameter, NCP gen 56start OMEGAMON II 50START parameter 82startup

CT/Engine 87–103CT/Engine parameters 87OMEGAMON II parameters 45terminal definition 77


STATUS parameter 82STGMON

RKLVIN parameter 100STOP parameter 82storage

allocation 45carved 97extended 97free 97messages 100primary 97remaining free 46utilization report 46

SVC dumps 99SWAP

RKLVIN parameter 101symbols, use of 12synchronizing profile with OMEGAVIEW 80SYS1.PARMLIB 43SYS1.VTAMLIB 18SYS1.VTAMLST 18SYSIN

PACK 97SYSMDUMP 99system access validation 71SYSTEMS argument, ETE 49

T

table database migration 22TASKS

RKLVIN parameter 101TCPC parameter 83TCPCVIOU parameter 83TCP/IP

authorize privileged commands 42KONFCCMD command 81requirements 42SNMP agent and subagent 42, 43usage 42

telephone support 106terminal

allocation, dynamic 77deallocation, dynamic 78definition 77non-English 25

thresholdquiesce 97recovery 97setting 67

threshold (continued)short-on-storage 97

TOP SECRETSee CA-TOP SECRET

TRACERKLVIN parameter 101

TRACERTE command authorization 42TRSPEED parameter, NCP gen 56

U

uppercase displays 25UPPERDLG

RKLVIN parameter 102UPPERLOG

RKLVIN parameter 102UPPERWTO

RKLVIN parameter 102user

authorities 52, 70displaying IDs 70external function level security 73ID, NAM 51password, NAM 51profiles 69

V

verificationprocedures 49

VSAM encrypted security 69VTAM

major node activation 50mode 20

VTAM operating mode 20

W

WTORKLVIN parameter 102

WTODCRKLVIN parameter 103

WTORCRKLVIN parameter 103

Index 115

Z

zooming from OMEGAVIEW 79


configuration and customization...

Documents