configuration and customization guide -...

Configuration and Customization GuideOMEGAMON II® for Mainframe Networks

Version 520

GC32-9271-00

June 2004

Candle Corporation100 North Sepulveda Blvd.

El Segundo, California 90245

2 OMEGAMON II for Mainframe Newtworks Configuration and Customization Guide, V520

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

Copyright © June 2004, Candle Corporation, a California corporation. All rights reserved. International rights secured.

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

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

Contents 3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Candle Customer Service and Satisfaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Chapter 1. Background about Components and Modes of Operation. . . . . . . . . . . . . . . . . 19Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Details about the TCP/IP Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Details about the ETE Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Details about the NCP Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Chapter 2. Installing, Configuring, and Customizing OMEGAMON II for Mainframe Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Configuration Planning and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31CICAT Background and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32CICAT Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Manual Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Manual Customization Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

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

Chapter 4. Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Starting End-to-End Version 500. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Contents

4 OMEGAMON II for Mainframe Networks Configuration and Customization Guide, V520

Activating OMEGAMON II Major Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Starting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Initializing the NAM Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Defining the User ID and Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Logging onto OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Enabling TCP/IP Data Collection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Enabling OMEGAMON II Console Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Setting Thresholds and Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64When Verification is Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Chapter 5. NCP Data Collection Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Background About NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68NCP Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69X.25 NCP Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70NPALU Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Enabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Disabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Chapter 6. Controlling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Background About ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Enabling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Disabling ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78ETE References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

Chapter 7. Setting Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Using the NAM Facility for Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Displaying User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Assigning User Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Using RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Using CA-ACF2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Using CA-TOP SECRET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87External Function Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Chapter 8. SMF Record Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Enabling SMF Recording. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Exception Record Format Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93SMF Record Layouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

Chapter 9. Dedicated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Activate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Deactivate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97Set the Polling Interval. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

Chapter 10. Connecting to OMEGAVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Enhanced Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100Procedures and Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

Contents 5

Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102Profile Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104

Appendix A. Operator Command KONFCCMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105Using the KONFCCMD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106KONFCCMD Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Appendix B. CT/Engine Startup Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111CT/Engine Startup Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

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

List of Figures 7

FIGURE 1. NCP Collector Within OMEGAMON II Address Space. . . . . . . . . . . . . . . . . . . . . . . . . .24FIGURE 2. NCP Collector in Another OMEGAMON II Address Space . . . . . . . . . . . . . . . . . . . . . .25FIGURE 3. Not Using and NCP Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

List of Figures

List of Tables 9

Table 1. Symbols in Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Table 2. Product Components for OMEGAMON II for Mainframe Networks . . . . . . . . . . . . . . .20Table 3. Characteristics and Requirements for OMEGAMON II Modes of Operation . . . . . . . . . .26Table 4. Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Table 5. CICAT Configuration Procedure Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Table 6. Manual Configuration Procedure Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Table 7. Manual Customization Procedure Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

List of Tables

10 OMEGAMON II for Mainframe Newtworks Configuration and Customization Guide, V520

Preface 11

Preface

About This Book

About this document

This guide explains how to perform the following installation processes for OMEGAMON II® for Mainframe Networks Version 520 (hereafter referred to as OMEGAMON II):

® planning and migration

® configuration

® verification

® customization

Who should read this bookThis is intended for those who have experience configuring and customizing mainframe 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.

In addition to the manuals described below, OMEGAMON II includes an online data dictionary for the historical component. The OMEGAMON II/OMEGAVIEW Messages Manual is also available online.

® OMEGAMON II for Mainframe Networks Configuration and Customization Guide, V520, ON51-6304

® OMEGAMON II for Mainframe Networks User’s Guide, V520, ON54-6305

® OMEGAMON II for Mainframe Networks NCP Monitoring Guide, V520, ON99-6306

® OMEGAMON II for Mainframe Networks Historical Reporting Guide, V520, ON99-6307

® OMEGAMON II/OMEGAVIEW Messages Manual, W052-6238, W052-6239, W052-6240,W052-6356, and W052-6357

P


® End-to-End Response Time Feature (ETE) Reference Manual, V500, ET53-5586

Online documentationWith V520, Candle Corporation has moved OMEGAMON II for Mainframe Networks manuals from IBM BookMaster to Adobe FrameMaker. This move was made to better enable us to address our customers’ needs by providing tools that enhance productivity.

One of the results of the move is that it is no longer possible to create BookManager versions of the OMEGAMON II for Mainframe Networks manuals. However, the manuals remain available online in the Adobe PDF version on CD-ROM and are also available on the Candle Corporation website at www.Candle.com.

The documentation CD being provided with this release has robust and easy-to-use search capabilities. You can search for information in multiple volumes, multiple versions, and across products. The CD also provides easy setup of search indexes with a single click of the mouse.

If you want to order printed copies of the documentation, please contact your Candle Support Services representative.

Where to look for more informationFor more information related to this product, please see the

® technical documentation CD-ROM that came with your product

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

® online help provided with this product

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

You can also send email to [email protected]. Please include OMEGAMON II for Mainframe Networks Configuration and Customization Guide in the subject line.

Preface 13

Candle Customer Service and Satisfaction

Candle Customer Service and Satisfaction

BackgroundTo assist you in making effective use of our products, Candle offers a variety of easy-to-use online support resources. The Candle Web site provides direct links to a variety of support tools that include these services:

eSupport allows you to create and update service requests opened with Customer Service and Satisfaction (CSS).

eDelivery allows you to download products, documentation, and maintenance 24 hours a day, 7 days a week.

eNotification notifies you of product updates and new releases.

In addition, you can find information about training, maintenance plans, consulting and services, and other useful support resources. Refer to the Candle Web site at www.candle.com for detailed customer service information.

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

http://www.candle.com

http://www.candle.com

Adobe Portable Document Format



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

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

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

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

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

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

printer should be the same. A setting of 300 dpi is recommended.)® the printer driver you are using. (You may need a different printer driver or the

Universal Printer driver from Adobe. This free printer driver is available at www.adobe.com.)

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

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

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

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

http://www.adobe.com

Preface 15


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

Documentation Conventions



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

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

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

beBA*ServiceMonitorb0990221161551000

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

Variables and literals in command syntax examplesIn examples of command syntax for the OS/390, VM, OS/400, and NonStop Kernel platforms, uppercase letters indicate actual values (literals) that the user should type; lowercase letters indicate variables that represent data supplied by the user:

LOGON APPLID (cccccccc)

However, for the Windows and UNIX platforms, variables are shown in italics:

-candle.kzy.instrument.control.file=instrumentation_control_file_name-candle.kzy.agent.parms=agent_control_file_name

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

SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

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

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

Preface 17


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

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

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

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

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

_ Default values are underscored. Example:

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

Table 1. Symbols in Command Syntax

Symbol Usage

Background about Components and Modes of Operation 19

Background about Componentsand Modes of Operation

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

® product components

® NCP performance data collector and the three types available

® TCP/IP component

® modes of operation

Chapter ContentsProduct Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Details about the TCP/IP Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Details about the ETE Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Details about the NCP Data Collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1

Product Components


Product Components

This section provides background information about the product components for OMEGAMON II for Mainframe Networks .

Product components for OMEGAMON II for Mainframe Networks The following table lists the components available when you install OMEGAMON II for Mainframe Networks , provides a brief description of each component, and indicates whether the component is required or optional.

Table 2. Product Components for OMEGAMON II for Mainframe Networks

Component Description

OMEGAMON II for Mainframe Networks (required)

Provides the interface for the OMEGAMON II for Mainframe Networks components and the performance data for VTAM

TCP/IP data collector (optional) Provides TCP/IP performance measurements

End-to-End Response Time (optional)

Provides OMEGAMON II for Mainframe Networks with response time data and required if you want to use the VTAM Trace Facility

NCP performance data collector (optional)

Collects data from the NPALUs in NCPs

SAS programs (optional) Provides network performance data written to SMF (SAS programs are Candle-supplied.)

SAS historical component (optional)

Uses the performance data collected by the SAS data to create historical reports


Details about the TCP/IP Data Collector

Details about the TCP/IP Data Collector

An OMEGAMON II for Mainframe Networks address space contains a TCP/IP performance data collector that monitors and collects the performance data for mainframe TCP/IP address spaces and the network resources and applications controlled by these address spaces.

During the CICAT configuration process, you will be asked to specify values for the TCP/IP component. If you do not want to collect TCP/IP performance data, you can specify N (No).

Types of TCP/IP data collectedUsing OMEGAMON II for Mainframe Networks , you can display a summary of each of the TCP/IP address spaces. For each address space, you can display:

® the resources being used

® buffer pool utilization statistics

® the connections and the status for connections

® applications connected to the address space

® devices connected to the address space

® gateways connected to the address space

® the statements and parameters for the configuration

OMEGAMON II for Mainframe Networks provides a TCP/IP console feature that you can use to display TCP/IP data. You can use the TCP/IP console to execute TCP/IP and MVS commands.

Details about the ETE Component


Details about the ETE Component

An OMEGAMON II for Mainframe Networks address space contains an End-To-End (ETE) Response Time component that is used to collect response time data. You can use the component to monitor the response time of SNA terminals connected to applications on the host.

During the CICAT configuration process, you will be asked to specify the started task name for ETE.

Types of response time data collectedUsing ETE, you can display:

® the time experienced by a user who has pressed a key and is waiting for a response at the terminal (end-to-end response time)

® the time the user request and the application response spend in VTAM and in the application (host response time)

® the time the request and its response spend traveling through the network outside the host (network response time)


Details about the NCP Data Collector


An OMEGAMON II for Mainframe Networks 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 spaceIf 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 spacesIf 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.

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

Three Types of NCP Data CollectionCICAT will ask you to specify the type of NCP data collection. The three possible types are illustrated below.

Local NCP Collector

OMEGAMON II obtains its NCP performance data from the NCP collector running in its own address space.



This is the most common configuration.

FIGURE 1. NCP Collector Within OMEGAMON II Address Space

When you configure the local NCP collector, CICAT configuration asks you to specify the

® Dataset name of your NCP-generated NDF source library, to be used for ddname KONSRC in the OMEGAMON II for Mainframe Networks started task. The default is SYS1.VTAMLST.

® Dataset name of your NCP load library to be used for the Resource Resolution Table, ddname KONRRT in the OMEGAMON II for Mainframe Networks started task. The default is SYS1.VTAMLIB.

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.



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.

FIGURE 3. Not Using and NCP Collector

Modes of Operation


Modes of Operation

During configuration, you will be asked to select and customize an operating mode. The available operating modes are:

® VTAM mode

® dedicated mode

Operating mode characteristics and requirementsThe following table describes each operating mode and its requirements.

Table 3. Characteristics and Requirements for OMEGAMON II Modes of Operation

Mode Characteristics Configuration Requirements

VTAM VTAM mode enables you to run OMEGAMON II sessions from a VTAM terminal without an intermediate online application, such as TSO. You can set automatic update mode so that the screen refreshes automatically.

VTAM mode allows all VTAM terminal users to share a single copy of OMEGAMON II.

Copy VTAM major node definition created during CICAT install.

Dedicated Dedicated mode offers high availability and does not require VTAM services. Dedicated mode uses EXCP to communicate with a terminal and refreshes the screen every few seconds.

Dedicated mode allows OMEGAMON II to provide realtime data even when VTAM is not available.

Availability of a locally attached non-SNA terminal.

Installing, Configuring, and Customizing OMEGAMON II for Mainframe Networks 27

Installing, Configuring, and CustomizingOMEGAMON II for Mainframe Networks

This chapter provides information about installing, configuring, and customizing OMEGAMON II for Mainframe Networks .

Chapter ContentsConfiguration Planning and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Overview of the Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31CICAT Background and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32CICAT Configuration Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Manual Configuration Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Manual Customization Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2

Introduction


Introduction

This chapter provides:

® the considerations you should review before you begin to configure and customize OMEGAMON II for Mainframe Networks

® 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 Mainframe Networks using CICAT

® an overview of how you configure OMEGAMON II for Mainframe Networks 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 Mainframe Networks for the first time or you need a reminder about the different components and modes of operation for OMEGAMON II for Mainframe Networks, see “ Background about Components and Modes of Operation” on page 19.


Configuration Planning and Considerations


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

Requirements for hardware and softwareFor information about hardware and software requirements, see Installation & Configuration of Candle Products on OS/390 and z/OS.

For more details on historical reporting, see the OMEGAMON II for Mainframe Networks 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 520.

You can avoid redefining the information itemized below to OMEGAMON II by migrating your existing NAM and Table Database datasets to Version 520. If you elect to do so, specify the existing dataset name on 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 520 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 520.



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

SMF record considerationsThe format of OMEGAMON II SMF exception records changed in Version 200 to support NCP performance statistics. If necessary, modify these programs to recognize the exception record format changes.

For Version 520 SMF record layouts, refer to the appendix in the OMEGAMON II for Mainframe Networks OMEGAMON II for Mainframe Networks Historical Reporting Guide.

Security considerationsOMEGAMON 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 81 provides detailed instructions.

Monitoring the log fileThe 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 Mainframe Networks User’s Guide.


Overview of the Process

Overview of the Process

This section provides a broad overview of the installation, configuration, and customization process. It also includes information about accessing help when using CICAT.

Broad overview of the processThe following table contains the broad steps you follow when you install, configure, and customize OMEGAMON II for Mainframe Networks . The table also shows where you can find the information you will need during each of the steps.

Getting help with CICATThe 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.

Table 4. Overview of the Process

Step Action Information

1 Using CICAT, install the product and create any new runtime environments.

Installation & Configuration of Candle Products on OS/390 and z/OS and the online help for the product panel you are using

2 Using CICAT, configure the components you want to use.

Online help for the product panel you are using

4 Manually configure the components and verify that the configuration is complete.

Chapters 3 and 4 in this guide

5 Manually customize the components you want to use.

Chapters 5–10 in this guide

CICAT Background and Requirements


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 Mainframe Networks. 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 CICATImportant 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 availableIf you need information about installing OMEGAMON II for Mainframe Networks using CICAT, you can locate information in the:

® Installing Candle Products on MVS manual

® online help for the product panel you are using

Examples of the tasks performed by CICATCICAT performs tasks that make OMEGAMON II for Mainframe Networks operational with a basic set of defaults. You use CICAT to:

® install the SMP/E datasets

® modify JCL

® allocate datasets

® define started task name and applids

® create runtime libraries


CICAT Configuration Procedures


This section describes the CICAT configuration procedures for OMEGAMON II for Mainframe Networks .

Prerequisites for configuring OMEGAMON II for Mainframe Networks Before you start to configure OMEGAMON II for Mainframe Networks , be sure that you have reviewed the considerations and planning information in the chapter “Configuration Planning and Considerations” on page 29.

The following configuration procedures assume that you have:

® for a full SMP/E install, completed SMP/E installation and applied the appropriate maintenance

® for maintenance only, applied the appropriate maintenance

® for a multi-product quick install, completed the quick install

Reminder about the information availableIf you need information about configuring OMEGAMON II for Mainframe Networks using CICAT or specific information about the values you specify using CICAT, see the online help for the product panel you are using.

Accessing CICATFor information about starting CICAT, see Installing Candle Products on MVS.

Accessing the Configure OMEGAMON II for Mainframe Networks Menu in CICATThere are two versions of CICAT available to install and configure Candle products. These include:

® CICAT Version 200

® CICAT Version 300

The method you use to access the Configure OMEGAMON II for Mainframe Networks Menu will vary depending on the version of CICAT you are using.



Accessing the menu in CICAT Version 200 Follow these instructions to access the Configure OMEGAMON II for Mainframe Networks Menu in CICAT Version 200.

Accessing the menu in CICAT Version 300 Follow these instructions to access the Configure OMEGAMON II for Mainframe Networks Menu in CICAT Version 300.

Step Action

1 On the CICAT Main Menu, perform the appropriate action. ® If you are installing the MultiProduct Quick Install tape, select MultiProduct Quick

Install. ® If you are installing OMEGAMON II for Mainframe Networks as a separate product,

select the product.

2 On the Installation/Configuration Primary Menu, select Assist configuration and manage runtime environments.

3 On the Runtime Environments (RTE) panel, use C (Configure) to select a runtime environment.

Result: CICAT displays the Product Configuration Selection Menu.

4 On the Product Configuration Selection Menu, select OMEGAMON II for Mainframe Networks.

Result: CICAT displays the Configure OMEGAMON II for Mainframe Networks Menu.

Step Action

1 On the Main Menu, select Configure products.

2 On the Configure Products menu, select Setup Configuration Environment.

3 On the Setup Configuration Environment panel, specify the values.

4 Return to the Configure Products menu.

5 On the Configure Products menu, select Configure Products.

Result: CICAT displays the Product Selection Menu.

6 On the Product Selection Menu, select OMEGAMON II for Mainframe Networks.

Result: CICAT displays the Configure OMEGAMON II for Mainframe Networks Menu.



Example of the Configure OMEGAMON II for Mainframe Networks menu in CICATThe following figure is an example of the Configure OMEGAMON II for Mainframe Networks menu.

----- CONFIGURE OMEGAMON II FOR Mainframe Networks/ 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



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

Table 5. CICAT Configuration Procedure Checklist

m 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 Mainframe Networks ® 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 Mainframe Networks

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

If you want to use SAS historical reporting, select Configure 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.)

Load the runtime libraries using “When to load the runtime libraries” on page 37.



When to load the runtime librariesYou 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 parametersOnce you complete configuration, if you need to change configuration parameters:

1. Reinvoke CICAT.

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

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

4. Review the Complete the Configuration selection on the Configure OMEGAMON II for Mainframe Networks 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


Manual Configuration Procedures

This section provides information about performing manual configuration procedures for OMEGAMON II for Mainframe Networks.

Manual configuration checklistThe following table contains the steps you perform manually to configure OMEGAMON II for Mainframe Networks. The steps are listed in the sequence in which they are to be performed. Use the mÊÊcolumn to check off steps as you complete them.

Table 6. Manual Configuration Procedure Checklist

m Manual Configuration Step

Complete the configuration using “Completing the Configuration” on page 41.

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


Manual Customization Procedures


This section provides information about performing manual customization procedures for OMEGAMON II for Mainframe Networks.

Reminder about the information availableThe checklist in the following table contains the location where you can find the information you will need.

Manual customization checklistThe following table contains the steps you perform manually to customize OMEGAMON II for Mainframe Networks. The steps are listed in the sequence in which they are to be performed. Use the mÊcolumn to check off steps as you complete them. Candle recommends that you review the entire process before you begin customizing OMEGAMON II for Mainframe Networks .

Table 7. Manual Customization Procedure Checklist

m Manual Customization Step

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

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

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

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

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

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

Completing the Configuration 41

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 Mainframe Networks . (These procedures are also covered on a panel displayed when you select to complete the configuration using CICAT.)

Chapter ContentsAPF-Authorizing the Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Copying the Procedures and VTAM Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Setting the Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Setting the Dispatching Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45If You Selected the NCP Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46If You Are Running VTAM 4.3 and Above. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47If You Selected to Configure TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48If You Are Configuring for Larger Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50If You Want to Use TNSTATs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3

APF-Authorizing the Libraries


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


Copying the Procedures and VTAM Definitions

Copying the Procedures and VTAM Definitions

Before you begin to use OMEGAMON II for Mainframe Networks , 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. CICAT creates the members for the procedures and VTAM definitions using the names you specified on the Specify Configuration Values panel. For example, if you used the default value for the End-to-End started task, the started task JCL can be found in shilvev.RKANSAM(CANSETE).

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


Setting the Security

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

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


Setting the Dispatching Priority

Setting the Dispatching Priority

The ensure the availability of OMEGAMON II for Mainframe Networks , you must set the dispatching priority.

® You must execute OMEGAMON II for Mainframe Networks 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 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 shilev.RKANSAM. (The name is the name you specified for LU6.2 modetab 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 67.


If You Are Running VTAM 4.3 and Above

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 Mainframe Networks 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:

aÊ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:

aÊ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 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. The OMVS segment must be defined with SuperUser authority.

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



Providing OMEGAMON II with the TCP/IP data fileIf you will be using OMEGAMON II for Mainframe Networks 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 ReferencesFor 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 managementThe 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.

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

MAXIMUM(32768,X)

MINIMUMMINIMUM 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(1024,P)

MINIMUM(16384,X)



RESERVEThis 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(2048,P)

RESERVE(4096,X)

Storage Utilization ReportTo 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 Mainframe Networks using CICAT.

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

If You Want to Use TNSTATs



BackgroundVTAM records tuning statistics (TNSTATs) for the following channel-attached nodes:

® communications controller

® adjacent host processor

® SNA cluster controller

You can use TNSTATs to adjust VTAM and NCP parameters, and thereby improve VTAM performance.

RequirementsTo record and display TNSTATs, you must specify the TNSTAT VTAM start option, or you must turn on TNSTATs manually using the MODIFY TNSTAT command. Since TNSTATs are always recorded to the SMF dataset, you must also include the SMF facility in the system during system generation.

If unspecifiedIf TNSTATs are not active, OMEGAMON II

® displays turquoise TNSTATs status lights that read NOTNSTAT on the main status panel

® displays a turquoise (Idle) condition for each device listed under TNSTATs

® displays only configuration data under TNSTATs

® does not record TNSTATs data to online trend files or SMF



ReferencesFor more information about TNSTATs, see

® ”Gathering Tuning Statistics” in the IBM VTAM Network Implementation Guide

® ”Tuning Statistics:” in the OMEGAMON II for Mainframe Networks User’s Guide

Verifying the Configuration 55

Verifying the Configuration

This chapter provides more details about the verification process.

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

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

Chapter ContentsStarting End-to-End Version 500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Activating OMEGAMON II Major Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Starting OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Initializing the NAM Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Defining the User ID and Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Logging onto OMEGAMON II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Enabling TCP/IP Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Setting Thresholds and Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64When Verification is Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4

Starting End-to-End Version 500


Starting End-to-End Version 500

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

® Use Version 500 of ETE.

® Apply all ETE maintenance included in the cumulative maintenance tape that 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, you must first quiesce both the current ETE subsystem and address space completely by issuing this console command:

ETE QUIESCE

Result: You will see these responses:

ETE0086: ETE ADDRESS SPACE TERMINATED BY SUBSYSTEM QUIESCE

ETE0051: QUIESCE COMPLETE

ETE0003: COMPLETE

2. Start ETE Version 500 (with current maintenance) by issuing this console command:S ccccccc

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

Result: You will see this response

ETE0091 ETE VERSION 500 SUCCESSFULLY INITIALIZED


Activating OMEGAMON II Major Node

Activating OMEGAMON II Major Node

TheOMEGAMON II VTAM major node must be active:

1. Activate the OMEGAMON II major node by issuing this MVS command:VARY NET,ACT,ID=cccccccc

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

Starting OMEGAMON II


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 Mainframe Networks using CICAT.

Result:

® You will see these startup confirmation messages (not necessarily in this order):

KONPN001 OMEGAMON II for MAINFRAME NETWORKS(V520)--INITIALIZATION COMPLETED

KONPN005 ETE CONNECTED SUCCESSFULLY

KONPN002 ACT STARTED SUCCESSFULLY

KONFC010 FPON COMPONENT FUNCTIONS INSTALLATION COMPLETE

KONFC015 FPCT COMPONENT FUNCTIONS INSTALLATION COMPLETE

KONFC025 SEMV MVS ENVIRONMENT INSTALLATION COMPLETE

KONFC020 SEVT VTAM ENVIRONMENT INSTALLATION COMPLETE

KONFC050 NDMT NCP DATA MANAGER INSTALLATION COMPLETE

KONND100 NCP DATA MANAGER TASK AVAILABLE FOR REQUESTS

KONCT100 TCP/IP SERVICE THREAD INITIALIZATION COMPLETE

KONCT100 MIB BROWSER SERVICES THREAD INITIALIZATION COMPLETE

KONCT100 XMCS SERVICES THREAD INITIALIZATION COMPLETE

KONCT000 TCP/IP STATISTICS COLLECTOR INITIALIZATION COMPLETE

KONFC095 TCPC COLLECTOR STATUS IS ACTIVE

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

KONPN004 ETE CONNECTION FAILED

® If you chose not to start the NCP collector, OMEGAMON II continues to run, although the following message appears. This message appears until you use the NCP Performance Options under the Options pull-down to turn off NCP monitoring.

KONAF121 NDM STARTUP FAILED RC(hhhhhhhh) SC(hhhhhhhh)

WILL RETRY EACH ACT CYCLE INTERVAL


Initializing the NAM Database

Initializing the NAM Database

Note: If you migrated your prior release’s NAM file to Version 520, skip this step.

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

F ccccccc,KONNAM

where cccccccc is the started task name you specified for OMEGAMON II for Mainframe Networks using CICAT.

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

KLVOP909 variable DECLARED: LENGTH(length)

Defining the User ID and Password


Defining the User ID and Password

Notes:® If you are not using NAM security, skip this step.

® If you migrated your prior release’s NAM file to Version 520, skip this step.

To provide user access to OMEGAMON II, define a user ID and password to 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 Mainframe Networks using CICAT.

Result: You will see this response:

KLVOP910 ACCESS CREATED FOR USERID userid


Logging onto OMEGAMON II

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 Mainframe Networks using CICAT.

Result: The Candle logon panel appears.

2. Enter your name and password. If you use NAM, you are prompted to enter a new password.Result: The first panel you see is the OMEGAMON II for Mainframe Networks Status Display with status lights for the various VTAM and NCP components. By default, as the first user, you become the product administrator.

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 user authorities in

the OMEGAMON II for Mainframe Networks User’s Guide.As an alternative you can use your external security package to authorize users to functions. See “External Function Level Security” on page 88.

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 menus and

panels. See the chapter on monitoring options in the OMEGAMON II for Mainframe Networks User’s Guide.

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

Enabling TCP/IP Data Collection


Enabling TCP/IP Data Collection

Community nameOMEGAMON 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 OptionsIf 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 communicationsWith 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.0.0.0.0.21.0.0.0.0.0 = 15496483


Enabling OMEGAMON II Console Support

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 any OMEGAMON 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, OMEGAMON Console APPLID Prefix.

6. For console support, you must enter the same value that was specified for Terminal Pool Prefix in the CICAT configuration process. This is the name of the 1 to 5 byte OMEGAMON II terminal pool prefix used when accessing the OMEGAMON II VTAM console.A pool of applids are created, where all the applid names start with the same 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 enteringD NET,APPLS

Result

IST097I DISPLAY ACCEPTED

IST350I DISPLAY TYPE = APPL MAJ NODES/NAMES

IST314I END

Setting Thresholds and Exceptions


Setting Thresholds and Exceptions

The first user to log onto OMEGAMON II has administrator authority. An administrator uses the Options pull-down to set thresholds and exception values 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 the action 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 Options panel. For details on each monitoring option, refer to the chapter on monitoring options in the OMEGAMON II for Mainframe Networks User’s Guide.

4. Return to the main status panel. The status lights on the main status panel reflect VTAM and NCP status based on the settings you specify for® resources to monitor

® exception conditions to monitor

® threshold values

® exception severities


When Verification is Complete


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

NCP Data Collection Requirements 67

NCP Data Collection Requirements

This chapter indicates the definitions required in the Network Control Program generation for any NCP that you want to monitor with OMEGAMON II. You must regenerate and reload the NCP before you enable NCP data collection as described in “Enabling NCP Data Collection” on page 72.

Chapter ContentsBackground About NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68NCP Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69X.25 NCP Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70NPALU Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Enabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Disabling NCP Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

5

Background About NCP


Background About NCP

NCP monitor component requirementsThe 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 usageBecause 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 ConfigurationThere 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.

NCP data collection requirementsRefer to “NCP Data Collection Requirements” on page 67 for information about

® NCP generation parameters required

® X.25 NCP generation parameters required

® defining the NPALU

® enabling NCP data collection


NCP Generation

NCP Generation

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

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 resource summary panels so that you do not have to refer back to the gen. The value of 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 PU macro (on the GROUP or LINE macro), and have it sift down to the PU macro. Any keyword that is valid at more than one level in the NCP gen, can sift down from higher to lower levels.

NPACOLL=YES Code 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 LINK macros

OMEGAMON II uses the SPEED parameter to calculate line utilization. For SDLC or BSC lines using external clocking, be sure that your SPEED parameter value equals the speed of the modem, otherwise your utilization statistics will be invalid.

DUPLEX Code on SDLC and BSC LINE macros.

OMEGAMON II uses the DUPLEX parameter when calculating utilization statistics.

TRSPEED Code on token-ring physical LINE macros.

OMEGAMON II uses the TRSPEED parameter when calculating utilization statistics.

Important

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

X.25 NCP Generation


X.25 NCP Generation

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

1. On the BUILD statement, codeNPA=YES

2. On the OPTIONS statement, codeNEWDEFN=(YES,ECHO,NOSUPP,REUSE)

3. On the X25.MCH statement, codeNPACOLL=(MCHLINK,MCHPU,VCPU)

4. On the X25.MCH statement, also codeNPPVCN=(n)

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

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


NPALU Definition

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 terminal pool prefix specified during CICAT configuration with the characters NCP and uses that for the LOGAPPL value in KONCTNPA. The default value is KONNCP.

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

Code the following keywords on the NPALU LU macro:

NPALU definition for NCP collector connection (KONCTNPA)These are the sample NPALU macro definitions that automatically generate a session with the NCP collector task at NCP activation.

***********************************************************************

*** NCP NPALU Definitions for Automatic Connection to ***

*** NCP collector task at NCP Activation ***

***********************************************************************

NPAGRP00 GROUP NPARSC=YES, X

VIRTUAL=YES, X

LNCTL=SDLC

*

NPALNE00 LINE

*

NPAPU00 PU

*

NPALU00 LU LOGAPPL=konNCP

*

***********************************************************************

MAXCOLL Specifies the number of resources for which you can collect data. Add at least 10% for growth. This parameter defaults to number of lines plus number of PUs.

LOGAPPL Controls automatic activation of the NPALU to the NCP collector.

Enabling NCP Data Collection


Enabling NCP Data Collection

When the required NCP’s definitions are generated, the NCP collector automatically 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 to reconfigure OMEGAMON II without NCP data collection. Do the following:

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

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

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

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

b. Comments out the KONFCCMD START NDMT statement.

Controlling ETE 75

Controlling ETE

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

Chapter ContentsBackground About ETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Disabling ETE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78ETE References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

6

Background About ETE


Background About ETE

ETE operates under the following rules:

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

® ETE Version 500 was designed as a common component that can be shared by multiple OMEGAMON® products. OMEGAMONs that use End-to-End include it as part of the product package.

® If ETE Version 500 is already installed in your system, it can be used by OMEGAMON II.

® When the variable $$ETE in the NAM database is set to Y, which is the shipped default, OMEGAMON II starts up expecting ETE to be started and tries to connect to it.

® If OMEGAMON II cannot connect to ETE, it issues a message but continues to run.

® If you change the setting of the NAM variable $$ETE, you must restart OMEGAMON II to recognize the new setting.

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

® OMEGAMON II for OS/390 Networks

® ETE

Controlling ETE 77

Enabling ETE

Enabling ETE

Although the OMEGAMON II shipped default is ETE enabled, you may have 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 OS/390 Networks using CICAT.

2. Enable ETE by issuing this command at the MVS console:F cccccccc,NAM SET OMVTAM $$ETE:Y


Result: The system displays this message:

KLVOP905 $$ETE:Y FOR USERID OMVTAM

3. Stop OMEGAMON II.P cccccccc

where ccccccc is the started task name you specified for OMEGAMON II for OS/390 Networks 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


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, it will no longer try to connect to ETE, until you reenable it.

Controlling ETE 79

ETE References

ETE References

For more details about ETE, refer to the following:

® “Starting End-to-End Version 500” on page 56

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

ETE References


Setting Security 81

Setting Security

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

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

Using the CICAT configuration panels, you began the process of defining OMEGAMON II security. This chapter describes the remaining steps you must perform to define security to NAM and to other security systems including RACF, CA-ACF2, and CA-TOP SECRET.

In the examples below, cccccccc represents the started task name you specified for OMEGAMON II for OS/390 Networks using CICAT.

Chapter ContentsUsing the NAM Facility for Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Displaying User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Assigning User Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Using RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Using CA-ACF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Using CA-TOP SECRET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87External Function Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

7

Using the NAM Facility for Security


Using the NAM Facility for Security

If you are using the NAM facility for security, you do not need to change member rhilev.rte.RKANPAR(KONINNAM), because KONINNAM automatically 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 OS/390 Networks 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


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

Setting Security 83

Displaying User IDs

Displaying User IDs

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

F cccccccc,NAM LIST


Assigning User Authorities


Assigning User Authorities

Whichever security system you use for OMEGAMON II entry validation, each user ID is assigned user authorities by an authorized administrator through the User Authorities choice on the Options pull-down menu. Refer to the chapter on user authorities in the OMEGAMON II for OS/390 Networks User’s Guide for more information.

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

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 OS/390 Networks security, you can use your external security package to authorize users to specific functions. See “External Function Level Security” on page 88.

Setting Security 85

Using RACF

Using RACF

The CICAT configuration process made the necessary changes to rhilev.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 the changes.

Using CA-ACF2


Using CA-ACF2

Because OMEGAMON II uses a multiuser system access control point, it has all the characteristics of an ACF2 multiple user single address space system (MUSASS). That is, system access validations are initiated and enforced 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:


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

Setting Security 87

Using CA-TOP SECRET

Using CA-TOP SECRET

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


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 STC record, along with the related master FACILITY ACID. For example, enter

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


2. (Optional) If you want to protect all OMEGAMON II datasets, define them to CA-TOP SECRET. Make sure the OMEGAMON II started task has 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 production installation using CA-TOP SECRET as the security system. If some statements are not relevant to your system, modify them to fit your standards 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,NOM O)

FACILITY(cccccccc=NOTSOC,LOG(INIT,SMF,MSG,SEC9))

Where ccccccccc is the started task name you specified for OMEGAMON II for OS/390 Networks using CICAT.

Notes:

a. Make certain that the SIGN parameter is specified as SIGN(M). Otherwise, CA-TOP SECRET may produce a message stating that user 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 to OMEGAMON II for OS/390 Networks functions by defining resource rules to your external security manager: CA-ACF2, RACF, or CA-TOP SECRET. You can use this feature instead of OMEGAMON II internal security which is set under the User Authorities selection of the Options pulldown.

Functions securedExternal function level security uses your external security manager to restrict user access to any of these OMEGAMON II functions:

® OMEGAMON II access

® administrator authority

® VTAM trace

® response time

® VTAM console

RequirementsBefore implementing external function level security, you must do the following:

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

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

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

External security resource namesThe following external resource names are used to secure the five OMEGAMON II functions listed:

where ccccccc is the logon applid you specified for OMEGAMON II for OS/390 Networks using CICAT.

OMEGAMON II access cccccccc.KON.ACCESS

administrator authority cccccccc.KON.ADMIN

VTAM trace access cccccccc.KON.TRACE

response time access ccccccccKON.RESPONSE

VTAM console access cccccccc.KON.CONSOLE

Setting Security 89


Defining RACF resourcesAn OMEGAMON II for OS/390 Networks resource class name can be added to RACF Class Descriptor Table (CDT). The following example shows the attributes you can use.

XXXXXXXX ICHERCDE CLASS=xxxxxxxx,

ID=nnn,

MAXLEN=24,

FIRST=ALPHANUM,

OTHER=ANY,

POSIT=xxxx,

DFTUACC=none

Follow these guidelines when you add the resource class name to the CDT.

® If you code RACLIST=ALLOWED, use the ICHRFRTB macro to create a router table entry for the class. (The ICHERCDE macro sets RACLIST=DISALLOWED as a default.)

® A POSIT value must be chosen that does not conflict with any existing class.

® If you define a new resource class in the RACF CDT, you must IPL your system specifying CLPA to rebuild the PLPA.

You can use the following commands.

® To activate your new resource class, use the SETROPTS command.

® To define the resources, use the RACF RDEF commands.

® To authorize user access to the resources you defined, use the RACF PERMIT commands.

A completion code 4 may result from the assembly of the CDT because of the non-standard CLASS value.

Contact your RACF administrator if you need assistance. Also see the RACF Macros and Interfaces manual.



Example of authorizing user accessThis is an example of using RACF to authorize only one user to the VTAM trace function.

RDEFINE classname cccccccc.KON.TRACE UACC(NONE)

PERMIT cccccccc.KON.TRACE CLASS(classname) ID(user1) ACCESS(READ)

where

Messages to user® When this feature is implemented and you select User Authorities from the

OMEGAMON II Options pulldown, the following message appears:

User Authorities - External Security Active

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

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

cccccccc is the logon applid you specified for OMEGAMON II for OS/390 Networks using CICAT.

classname is the resource class name for the OMEGAMON II trace facility

user1 is the user ID of the authorized user

SMF Record Considerations 91

1SMF Record Considerations

1.

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 OS/390 Networks Historical Reporting Guide.

Chapter ContentsEnabling SMF Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Exception Record Format Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93SMF Record Layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8

Enabling SMF Recording


Enabling SMF Recording

You can produce historical reports using the SMF data generated by OMEGAMON 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 such as Buffer Pools, Virtual Routes, or NCP Performance.

4. Select Monitor Options.

5. Enter S (SMF) or B (Both) in the Exception and Trend Recording fields to enable SMF recording.See the chapter on monitoring options in the OMEGAMON II for OS/390 Networks User’s Guide for additional information on setting monitoring options.

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

® Verify operation of the SAS-based historical component.

® Generate historical reports using SAS.

SMF Record Considerations 93

Exception Record Format Changes

Exception Record Format Changes

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

SMF Record Layouts


SMF Record Layouts

You can find OMEGAMON II SMF record layouts in an OMEGAMON II for OS/390 Networks Historical Reporting Guide appendix.

Dedicated Mode 95

Dedicated Mode

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

Dedicated mode is useful when normal online response time becomes poor due to problems within VTAM. In this case, you can use a dedicated mode terminal to bypass VTAM during logon. To use dedicated mode, you must have a terminal online to MVS and not currently used by VTAM or any other subsystem.

Chapter ContentsActivate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Deactivate a Dedicated Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Set the Polling Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

9

Activate a Dedicated Terminal


Activate a Dedicated Terminal

To activate a terminal dedicated to OMEGAMON II, you can take one of the following 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.

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 the OMEGAMON II started task name specified during OMEGAMON II CICAT 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.

Dedicated Mode 97

Deactivate a Dedicated Terminal

Deactivate a Dedicated Terminal

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

F canson,CLOSE UNIT-xxx

where canson is the OMEGAMON II for OS/390 Networks started task procedure name.

Set the Polling Interval


Set the Polling Interval

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

DEDICATE UNIT-xxx KONDSTRT INTERVAL(3)

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

Connecting to OMEGAVIEW 99

Connecting to OMEGAVIEW

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

Chapter ContentsEnhanced Zoom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Procedures and Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Profile Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

10

Enhanced Zoom


Enhanced Zoom

In OMEGAVIEW you can select a status bar and zoom into a direct session with OMEGAMON II for OS/390 Networks so that you can investigate the cause of the warning or critical condition indicated. This enhanced zoom feature enables you to automatically navigate to one of several OMEGAMON II panels that tell you more about the problem that the status light represents. For a brief overview of the OMEGAVIEW enhanced zoom feature, see the chapter on OMEGAVIEW zoom in the OMEGAMON II for OS/390 Networks User’s Guide.


Procedures and Libraries

Procedures and Libraries

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

For more information, see the OMEGAVIEW Configuration and Customization Guide.

Connection


Connection

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


Profile Synchronization

Profile Synchronization

To synchronize the response time options for the OMEGAVIEW collector session and the zoomed to OMEGAMON II for OS/390 Networks session:

1. An authorized user logs onto OMEGAMON II for OS/390 Networks with the collector session user ID.

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

3. Users logged onto OMEGAVIEW while collector session options were modified must log off and then log on again to OMEGAVIEW.Result: The response time options for the OMEGAVIEW collector session and zoomed to OMEGAMON II for OS/390 Networks sessions are automatically synchronized. When an OMEGAVIEW user zooms to OMEGAMON II for OS/390 Networks , the same response time options that were in effect for the OMEGAVIEW collector session will be in effect for the OMEGAMON II for OS/390 Networks zoomed to session.

References


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 begin monitoring OMEGAMON II status conditions

® maintenance requirements

® zoom procedures

® panel customization

Operator Command KONFCCMD 105

Operator Command KONFCCMD

KONFCCMD commands are required to implement the following in the OMEGAMON 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 configuration and CICAT updates the runtime libraries. Usually these Candle-supplied commands will suffice.

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

Appendix ContentsUsing the KONFCCMD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106KONFCCMD Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108OMEGAMON II client only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

A

Using the KONFCCMD Command



KONFCCMD is an CT/Engine operator command that you can use to do the following 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 ....... argument

Command argumentsValid command arguments are as follows:

Command optionsYou use the following options along with the above arguments:

INSTALL Install the specified feature(s).

START Initiate the specified feature(s).

STOP Shutdown the specified feature(s).

STATUS Display the status of the specified feature(s).

HELP Display how to use this command.

FPON Install functions specific to the OMEGAMON II address space.

FPCT Install functions specific to the NCP collector

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

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

NCPCACBN(ncpappl.)

Specifies the applid of the NCP collector task that talks to the NPALU in the NCP.

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



GuidelinesWhen 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 command argument. You can accomplish a minimal installation by omitting the INSTALL arguments; you can later enter the desired options.

® You can install, start, stop, or status a number of components simultaneously.

NDMT Install, start, stop, or display status of the NCP Data Manager (NDM) within an OMEGAMON II address space. The following 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 remote OMEGAMON II address space, where locappl resides in the local address space and talks to collappl which resides in the remote address space containing the NCP collector.

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

SEMV Install functions specific to the MVS execution environment for 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 to use when dynamically allocating files. If omitted, the default VIO is used.

KONFCCMD Examples


KONFCCMD Examples

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

VariablesThe examples include the following variables:

NCP collector in OMEGAMON II address spaceThese are the statements required when the NCP collector is included in the OMEGAMON II address space:

KONFCCMD INSTALL SEVT SEMV FPCT FPON

KONFCCMD INSTALL NCPC -

NCPCPATH(LUCS,COLLECTOR=collappl,NCPCACBN=ncpappl) -

NCPCINTV(nn)

KONFCCMD START NCPC

KONFCCMD INSTALL NDMT -

NDMTPATH(LUCS,LOCAL)

KONFCCMD START NDMT

collappl Applid of the NCP collector task that talks to other OMEGAMON II address spaces to provide NCP data. It is built by CICAT from the specified OMEGAMON II applid prefix.

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

locappl Applid in the OMEGAMON II without the NCP collector that talks to the OMEGAMON II containing the NCP collector. It is built by CICAT from the specified OMEGAMON II applid prefix.

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

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


KONFCCMD Examples

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

KONFCCMD INSTALL SEVT SEMV FPCT FPON

KONFCCMD INSTALL NDMT -

NDMTPATH(LUCS,LOCALID=locappl,COLLECTOR=collappl,MODE=mode62)

KONFCCMD START NDMT

OMEGAMON II client onlyWhen you do not require OMEGAMON II to gather NCP performance statistics and the OMEGAMON II address space does not include an NCP collector, no KONFCCMD statements are required.

KONFCCMD Examples


CT/Engine Startup Parameters 111

CT/Engine Startup Parameters

This appendix consists of CT/Engine initialization and customization parameters. MINIMUM, MAXIMUM, and RESERVE parameters are required for OMEGAMON II. The other CT/Engine parameters are listed here for your information only. Candle does not recommend that you modify any of the other parameters.

Appendix ContentsAMODE31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113APF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113CONFIRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113CONSECHO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113DATEFMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114DEBUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114INBDLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114INBOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115INITIAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115IINITLIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115INTLCHAR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116LOGBLOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116LOGBUFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117LSRPOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117LSRSTRNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118MAXIMUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118MINIMUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118OPLIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119OPLOCAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119OPMASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120OPSTART. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120OUTBDLIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120OUTBOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120PACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

B


QUIESCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121RESERVE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122SDUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122STGMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124SWAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124TRACE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125UPPERDLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125UPPERLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125UPPERWTO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126WTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126WTODC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126WTORC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126




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

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

AMODE31AMODE31(Y | N)

Determines whether CT/Engine runs in 31-bit addressing mode. Y is the default 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 to Version 1.2, code the following:

AMODE31(N)

APFAPF(Y | N)

Determines whether CT/Engine runs as APF-authorized. Y is the default if the 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.

CONFIRMCONFIRM(15 | n)

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

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

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

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

CONSECHOCONSECHO(N | Y)

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



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

Y causes the command output to be routed specifically to the originating console, as well as the master and other consoles. By coding Y products such as NetView and AF/OPERATOR are able to review the output of CT/Engine commands.

DATEFMTDATEFMT(MMDDYY | DDMMYY | YYMMDD)

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

DEBUG

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 number of entries (2048). See “TRACE” on page 125 for more information.

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

INBDLIMINBDLIM(25 | n)

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

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

Most file transfer programs implement handshaking protocols that require them to perform read operations. These programs should not be affected by a small INBDLIM value.

MMDDYY U.S. format

DDMMYY European format

YYMMDD International format

Important

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



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

INBOUNDINBOUND(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 to INBOUND, excess path lengths result. If the value assigned to INBOUND is much larger than the length of the RUs received, storage problems may result.

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

INITIALINITIAL(membername)

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

RKANCMD may contain a member named smfid, where smfid is the SMF ID of the CPU executing CT/Engine. If this member exists, it is automatically invoked before the command list specified in the INITIAL parameter.

IINITLISTINITLIST(membername)

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

startup-module-name=override-name

Each line of the INITLIST member names a particular startup module and identifies the member of RKANPAR which should be read by that module for its parameters. The valid startup module names vary with the CT/Engine-based products that are installed. The number of startup modules may also change as new features are added or new products become available. -As a result, it is not possible to provide a comprehensive list of startup module names.

No wild-card characters are accepted during INITLIST processing. Each override must be coded in full. Override statements must be coded one per line. The statements may appear in any column. Input will be converted to upper case prior to processing. Comment lines are indicated by an asterisk as the first non-blank character. On any line, anything following an asterisk is ignored.

Here is a sample input line:

KLVINNAM=NAMINIT0 * Override KLVINNAM parameter member name



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

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

INTLCHARINTLCHAR(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 as invalid are now valid.

LIMIT

LIMIT(16,P | n,P)

LIMIT(16,X | n,X)

Specifies the largest block of primary (P) or extended (X) storage that can be allocated. This value is specified in bytes, as a power of 2. For example, if n 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 the line. To specify values for both primary and extended storage, include the LIMIT parameter twice in RKLVIN:

LIMIT(n,X)

LIMIT(n,P)

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

LOGBLOCKLOGBLOCK(3120 | n)

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

Important




LOGBUFS

LOGBUFS(2 | n)

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

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

LSRPOOLLSRPOOL(size,count[,0 | hiper])

No default; however, you must code at least one LSRPOOL parameter in order 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 VSAM dataset 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. The minimum is 3. The maximum is 65535, although this may be less, depending on the amount of available virtual storage in the CT/Engine address space. Buffers will be allocated from extended storage if AMODE31(Y) was coded or defaulted to; from primary storage otherwise.

hiper is the number of hiperspace buffers of size to be allocated. The minimum is 0 (no hiperspace buffers). The maximum is 16777215, although this may be less, depending on the hiperspace storage available to IBM VSAM services. Ensure the CT/Engine address space is non-swappable when you are using hiperspace buffers.

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

For best storage use, code an LSRPOOL parameter for each different VSAM control 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.

Important




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

LSRSTRNOLSRSTRNO(32 | n)

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

If you receive many KLVVS026 messages identifying string contention, or if the STRMAX value in the KLVVS002 messages issued during CL/ENGINE shutdown is consistently the same as the value in RKLVIN, increase the LSRSTRNO value.

The minimum value is 1. The maximum is 255.

MAXIMUMMAXIMUM(8192,P | n,P)

MAXIMUM(n,X)

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

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

The variable n represents the maximum amount (in kilobytes) of primary or extended storage that can be allocated. X stands for extended storage (above the 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 continue running without overloading your page volumes when the steady-state MINIMUM 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 meet your requirements, the address space may run out of virtual storage.

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

MINIMUMMINIMUM(1024,P | n,P)

MINIMUM(8192,X | n,X)



n represents the mimimum amount (in kilobytes) of primary or extended storage 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:

In general, Candle recommends REGION=0M.

OPLIMITOPLIMIT(0 | n)

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

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

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

With the default OPLOCAL setting, an operator performing an action that generates a CT/Engine ALERT message does not receive the message at the console unless OPMASK

0K or 0M All primary and extended storage is available for 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.



allows it. For information on message types, see OMEGAMON II/OMEGAVIEW Messages Manual.

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

Specifies the types of unsolicited messages all operator consoles receive. For information on message types, see OMEGAMON II/OMEGAVIEW Messages Manual.

OPSTARTOPSTART(command)

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

OUTBDLIMOUTBDLIM(500 | n)

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

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

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

OUTBOUNDOUTBOUND(504 | n)

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

PACK

PACK(Y | N)

Important

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



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

QUIESCEQUIESCE(90,P,F | n,P,F)

QUIESCE(95,P,C | n,P,C)

QUIESCE(90,X,F | n,X,F)

QUIESCE(95,X,C | n,X,C)

Sets thresholds for slowing down allocation of storage. When the thresholds are exceeded, quiesce mode goes into effect, causing rejection of all conditional storage requests. Conditional storage requests include session and dialog startup, as well as other functions that can recover from a storage shortage. Unconditional requests for storage continue to be satisfied in quiesce 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 takes effect. Carved storage is storage put into use for the first time and allocated to a specific size; free storage is storage that has been carved but is not in use. Primary storage is below the 16-megabyte line; extended storage is above the line.

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

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

QUIESCE(80,X,F)

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

QUIESCE(90,P,C)

When CT/Engine detects that the amount of storage carved or in use is above the QUIESCE threshold percentage, it enters quiesce mode and does not permit new dialogs

omitted Specifies that modules are placed into the next available double word storage location. If the address space is APF-authorized, an MVS directed load is used and MVS CDEs are available; otherwise CT/Engine performs a pseudo-directed load and no CDEs are created.

Y CT/Engine performs a pseudo-directed load to place modules into the next available double word storage location. No MVS CDEs are created.

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



or sessions to start. For free storage, quiesce mode continues 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 of 90:

Recovery point = 9M - ((10M - 9M) / 2) = 8.5M

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

You can use the STGMON parameter to control reporting on quiesce mode conditions. See “STGMON” on page 124.

RESERVERESERVE(512,P | n,P)

RESERVE(2048,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 own GETMAINs in the CT/Engine address space (for example, ACF2 and RACF). The default for primary storage (P) is 512. The default for extended storage (X) is 2048. Primary storage is below the 16-megabyte line, and extended storage is above the line.

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

RESERVE(n,X)

RESERVE(n,P)

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

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

SDUMPSDUMP(Y | N | S | M)



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

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

To capture an entire SVC dump, perform these steps:

1. Ensure that the SYS1.DUMPxx datasets are large enough to 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 to accommodate the SDUMP requirements.

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

Candle recommends these storage guidelines for SVC DUMP datasets:® Allocate 32 meg if 16 to 32 meg are specified in RKLVIN for

MINIMUM/MAXIMUM keywords.® For each additional 16 meg specified in RKLVIN for

MINIMUM/MAXIMUM keywords, add 25 meg for the SVC 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 107 meg SVC DUMP dataset

N Specifies that a formatted dump should be directed to the RKLVSNAP dataset. Formatted dumps should be avoided when possible; they disable the CT/Engine address space for a longer period of time than either SVC dumps or SYSMDUMPs, and are more difficult to analyze.



STGMONSTGMON(15 | n)

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

SWAP SWAP(N | Y)

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

TASKS

TASKS(n)

S Specifies that a summary dump only should be directed to the RKLVSNAP dataset. A summary dump consists of an abend summary and a dispatcher summary only. Warning: Summary dumps do not provide enough information to allow problems to be analyzed. SDUMP(S) is provided only for very specific testing purposes, where it is known that a dump will not be needed.

M Specifies that the system should take an ABEND dump to a dataset defined with the SYSMDUMP ddname. This type of dump is not formatted by the operating system and must be analyzed with IPCS. Only the first dump taken will be captured on the SYSMDUMP dataset unless the JCL specifies DISP=MOD, in which case multiple dumps may be collected on the same dataset.

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

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

Note: The CT/Engine address space need not be APF-authorized to take a SYSMDUMP. For more information regarding SYSMDUMP specification, refer to IBM’s Planning: Problem Determination and Recovery.

Important




Default is the number of available processors.

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

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

TRACE

TRACE(11 | n)

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

If TRACE is not specified, no internal trace table will be allocated unless DEBUG(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 diagnostic information for Candle Customer Support. Elements that are included in the internal trace table are controlled by the CT/Engine TRACE operator command. Contact Candle Support Services for information about this command.

UPPERDLGUPPERDLG(N | Y)

Determines whether or not SSPL dialog output is folded to upper case before displaying on users’ terminals.

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

UPPERLOGUPPERLOG(N | Y)

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

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

Important




UPPERWTOUPPERWTO(N | Y)

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

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

WTOWTO(Y | N)

Determines whether or not CT/Engine issues WTOs.

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

NOTE: WTO(N) will suppress messages written with the WTO SSPL dialog function.

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

Specifies WTO descriptor codes for CT/Engine message types.

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

WTODC(ERROR,7)

For definitions of the descriptor codes, see IBM’s Supervisor Services and Macro Instructions manual. For information on message types, see OMEGAMON II/OMEGAVIEW Messages Manual.

WTORCWTORC(:ALERT,1,8,11 | type,code,code,...)

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

For definitions of the route codes, see IBM’s Supervisor Services and Macro Instructions manual. For information on message types, see OMEGAMON II for OS/390 Networks Messages Manual.

Index 127

Aabend S306 42about this document 11ACF2

see CA-ACF2ACID parameter 87activate

dedicated terminal 96major node 57NCP 72

Adobe portable document format 14AF_UNIX domain 48agent, SNMP 48allocating

terminal dynamically 96AMODE31

RKLVIN parameter 113APF

authorization 42RKLVIN parameter 113

applid, NCP collector 71authorize TRACERTE command 48authorizing users 84

external function level security 90

BBPXPRMxx member 48

CCA-ACF2 86Candle Web site 13carved storage 121CA-TOP SECRET 87changes, exception record 93CICAT 32

accessing 33help 31OMEGAVIEW configuration 101

collection, NCP data 21, 22, 23, 24, 69collector session profile, OMEGAVIEW 103community name 48, 62configuration

dynamic, NCP 68

KONFCCMD usage 105NCP generation 71NPALU macro definitions 71OMEGAMON II and NCP collector 21, 22, 23SMF consideration 91terminal pool prefix 71

configuration with CICAT 32CONFIRM

RKLVIN parameter 113connection, OMEGAVIEW 99CONSECHO

RKLVIN parameter 113considerations

ETE 76TCP/IP 48

control points 81controlling ETE 76CSA tracking 48CT/Engine

AMODE31 parameter 113initialization 113–126

AMODE31 parameter 113APF parameter 113CONFIRM parameter 113CONSECHO 113DATEFMT parameter 114DEBUG 114INBDLIM parameter 114INBOUND parameter 115INITIAL parameter 115INITLIST parameter 115INTLCHAR parameter 116LIMIT parameter 116LOGBLOCK parameter 116LOGBUFS parameter 117LSRPOOL parameter 117LSRSTRNO parameter 118MAXIMUM parameter 118MINIMUM parameter 118OPLIMIT parameter 119OPLOCAL parameter 119OPMASK parameter 120OPSTART parameter 120

Index


OUTBDLIM parameter 120OUTBOUND parameter 120PACK parameter 120QUIESCE parameter 121RESERVE parameter 122SDUMP parameter 122STGMON parameter 124SWAP parameter 124TASKS parameter 124TRACE parameter 125UPPERDLG parameter 125UPPERLOG parameter 125UPPERWTO parameter 126WTO parameter 126WTODC parameter 126WTORC parameter 126

KONFCCMD command 106startup 113–126

customizationconsole support 63dedicated mode 95End-to-End 76larger networks 50memory management 50NCP definitions 69requirements for each mode 26security 81

Ddata collection, NCP 23, 68, 69DATEFMT

RKLVIN 114DB parameter 86, 87deactivate dedicated terminal 97deallocate terminal dynamically 97DEBUG

RKLVIN parameter 114DEDICATE command 96, 98dedicated mode 26, 95dedicated operating mode 26dedicated terminal, activate 96define terminal at startup 96defining RACF resources using ICHERCDE 89disabling

End-to-End 78NCP data collection 73

DROP command authorization 48dumps 122DUPLEX parameter, NCP gen 69

dynamic configuration, NCP 68dynamic terminal

allocation 96deallocation 97

Eenabling

End-toEnd 77NCP data collection 72

encrypted security, NAM 81End-to-End

considerations 76disabling 78enabling 77quiesce 56references 79rules 76start 56SYSTEMS argument 56variable $$ETE 77

End-to-End Response Time Featuresee END-to-END

enhanced zoom, OMEGAVIEW 100ETE

see End-to-Endexception

record changes 30, 93settings 64

EXIT parameter 86extended 121extended storage 121external security resource class 88external security resource names 88

FFACILITY ACID 87FACILITY statements 87finalizing security 81format changes, exception record 93FPCT parameter 106FPON parameter 106free 121free storage 121free storage remaining 51function level security 61, 88functions secured externally 88

Ggeneration parameters, NCP 69

Index 129

Hhelp, CICAT 31historical repoting

SMF 92

IIBM

TCP/IP address space 48ICHERCDE 89INBDLIM

RKLVIn parameter 114INBOUND

RKLVIN parameter 115INITIAL

RKLVIN parameter 115initialization 113

CT/Engine 113–126AMODE31 parameter 113APF parameter 113CONFIRM parameter 113CONSECHO parameter 113DATEFMT parameter 114DEBUG parameter 114INBDLIM parameter 114INBOUND parameter 115INITIAL parameter 115INITLIST parameter 115INTLCHAR parameter 116LIMIT parameter 116LOGBLOCK parameter 116LOGBUFS parameter 117LSRPOOL parameter 117LSRSTRNO parameter 118MAXIMUM parameter 118MINIMUM parameter 118OPLIMIT parameter 119OPLOCAL parameter 119OPMASK paameter 120OPSTART parameter 120OUTBDLIM parameter 120OUTBOUND parameter 120PACK parameter 120QUIESCE parameter 121RESERVE parameter 122SDUMP parameter 122STGMON parameter 124SWAP parameter 124TASKS parameter 124TRACE parameter 125

UPPERDLG parameter 125UPPERLOG parameter 125UPPERWTO parameter 126WTO parameter 126WTODC parameter 126WTORC parameter 126

error 42NAM 59

INITLISTRKLVIN parameter 115

INSTALL parameter 106installation

command KONFCCMD 105verification 55

INTERVAL parameter 98interval, dedicated mode polling 98INTLCHAR

RKLVIN parameter 116

Kkeywords, NCP macro 69KLVA2NEV exit 86KONASM member 86KONCTNPA member 71KONFCCMD command 73, 105KONINNAM member 81, 82, 86, 87KONRRT ddname 24KONSRC ddname 24KONSTKON member 96KONSYSIN member 50

Llarger networks 50libraries

APF-authorize 42RKANMODL 86RKANPAR 50, 81, 82

RKANMODL 86LIMIT

RKLVIN parameter 116line utilization 69local NCP collection 23LOCALID parameter 107LOGAPPL Keyword 71LOGBLOCK

RKLVIN parameter 116LOGBUFS

RKLVIN parameter 117logon, OMEGAMON II 61


LSRPOOLRKLVIN parameter 117

LSRSTRNORKLVIN parameter 118

Mmacro

NCP gen keywords 69NPALU definition 71

major node, OMEGAMON II 57Management Information Block (MIB) 48MAXCOLL keyword 71MAXIMUM

OMEGAMON II memory management 50, 111RKLVIN parameter 118

memory management 50message

quiesce 124storage 124

migrationRKONNAM file 29RKONTDB file 29SAS databases 29

MINIMUMOMEGAMON II memory management 50, 111RKLVIN parameter 118

MODE=FAIL parameter 87modem speed 69MODIFY command, MVS 60, 82monitoring options 61, 64, 92multiple user single address space system (MUSASS)

86MUSASS 86MVS/ESA for TCP/IP 48

NNAM 29

adding users 82customization 81database 82encrypted security 81initialization 59password 60security system 81user ID 60, 83variable $$ETE 77

NCPactivating 68collection

applid 71configurations with OMEGAMON II for VTAM 23KONFCCMD command usage 105requirements 67

Data Manager 107disabling data collection 73dynamic configuration 68enabling data collection 69, 72generation 69, 71NPACOLL parameter 69NPALU connection 71requirements 68resource resolution table 24sift down 69source library, NDF 24with NetSpy 68with NPM 68

NCPC parameter 106NCPCACBN parameter 106NCPCINTV parameter 106NCPCPATH parameter 106NDF source library 24NDM

see NCP Data ManagerNDMT parameter 73, 107NDMTPATH parameter 107NetSpy

with NCP component 68Network Access Manager

see NAMNODB parameter 85, 86, 87NORACF parameter 86NPACOLL parameter, NCP gen 69NPALU

application 68definition 71KONFCCMD command usage 105macro definitions 71NCP collector connection 71usage 68

NPATP parameter, NCP gen 69NPM with NCP component 68

OOBEY command 48OMEGAMON II 68

KONFCCMD command usage 105libraries in OMEGAVIEW proc 101logon 61

Index 131

OMEGAVIEW libraries in proc 101performance 69with NetSpy 68with NPM 68

OMEGAVIEWconnection 99OMEGAMON II libraries 101procedure 101references 99synchronizing profile with 103zoom 99

OMVS segment 48operating mode requirements 26operator command, KONFCCMD 105OPLIMIT

RKLVIN parameter 119OPLOCAL

RKLVIN parameter 119OPMASK

RKLVIN parameter 120OPSTART

RKLVIN parameter 120options, monitoring 64OS/390 48OUTBDLIM

RKLVIN parameter 120OUTBOUND


PPACK

SYSIN parameter 120parameter 121parameters

CT/Engine 111OMEGAMON II startup

MAXIMUM 50MINIMUM 50RESERVE 51

PDF files, adding annotations 15performance, OMEGAMON II 69polling interval 98primary storage 121printing problems 14PROCLIB

OMEGAMON II proc 101OMEGAVIEW proc 101

product components 20profile synchronization with OMGAVIEW 103profiles for users 81

Qquiesce

ETE 56recovery point 121RKLVIN 121state change messages 124threshold 121

RRACF 85RACF Class Descriptor Table 89RACF parameter 85, 87record layouts, SMF 94region size 50remote NCP collection 23, 24reporting

see historical reportingrequirements, external function level security 88RESERVE

OMEGAMON II memory management 51, 111RKLVIN parameter 122

resource names, external security 88resource resolution table 24response time profiles 103restart OMEGAMON II 85RKANCMD library 96, 105RKANMODL library 86RKANPAR library 50, 81, 82, 86, 87, 111

KONSTKON member 73RKANSAM library 71, 86RKLVIN 113–126

AMODE31 113APF 113CONFIRM 113CONSECHO 113DATEMFT 114DEBUG 114INBDLIM 114INBOUND 115INITIAL 115INITLIST 115INTLCHAR 116LIMIT 116LOGBLOCK 116LOGBUFS 117LSRPOOL 117LSRSTRNO 118MAXIMUM 118MINIMUM 118


OPLIMIT 119OPLOCAL 119OPMASK 120OPSTART 120OUTBDLIM 120OUTBOUND 120QUIESCE 121RESERVE 122SDUMP 122STGMON 124SWAP 124TASKS 124TRACE 124UPPERDLG 125UPPERLOG 125UPPERWTO 126WTO 126WTODC 126WTORC 126

RKONNAM library 85, 86, 87, 88rules, ETE 76

SS306 abend 42SAS

customization 29migration 29

SDUMPRKLVIN parameter 122

securityalternative to User Authorities 88CA-ACF2 86CA-TOP SECRET 87finalizing 81function level 88interfaces supported 30NAM 81RACF 85user authorities 84user IDs 83

SEMV parameter 107SEVT parameter 107short-on-storage 121, 124sift down, NCP gen 69SIGN parameter 87SMF

changes 30considerations 30, 91exception records 30

programs using 30record layouts 94recording options 92revisions 30trend/exception records 91

SNMP agent and subagent 44, 48source library, NCP 24speed of modem 69SPEED parameter, NCP gen 69start OMEGAMON II 58START parameter 106startup

CT/Engine 113–126CT/Engine parameters 111OMEGAMON II parameters 50terminal definition 96

STATUS parameter 106STGMON

RKLVIN parameter 124STOP parameter 106storage

allocation 50carved 121extended 122free 122messages 124prmary 121remaining free 51utilization report 51

SVC dumps 122SWAP

RKLVIN parameter 124synchronizing profile with OMEGAVIEW 103SYS1.PARMLIB 48SYS1.VTAMLIB 24SYS1.VTAMLST 24SYSIN

PACK 120SYSMDUMP 122system access validation 86SYSTEMS argument, ETE 56

Ttable database migration 29TASKS

RKLVIN parameter 124TCP/IP

authorize privileged commands 48KONFCCMD command 105

Index 133

requirements 48SNMP agent and subagent 48usage 48

TCPC parameter 107TCPCVIOU parameter 107terminal

allocation, dynamic 96deallocation, dynamic 97definition 96

thresholdquiesce 121recovery 122setting 64short-on-storage 122

TOP SECRETsee CA-TOP SECRET

TRACERKLVIN parameter 125

TRACERTE command authorization 48TRSPEED parameter, NCP gen 69

UUPPERDLG

RKLVIN parameter 125UPPERLOG

RKLVIN parameter 125UPPERWTO

RKLVIN parameter 126user

authorities 61, 84displaying IDs 83external function level security 88ID, NAM 60password, NAM 60profiles 81

Vverification

procedures 55VSAM encrypted security 81VTAM

major node activation 57mode 26

VTAM operating mode 26

WWeb site, Candle 13WTO

RKLVIN parameter 126WTODC

RKLVIN parameter 126WTORC


Zzooming from OMEGAVIEW 100

configuration and customization guide -...

Documents