OMEGACENTER Status Manager for MVS ഀ唀猀攀爠ᤀ猀䜀甀椀...

User’s GuideOMEGACENTER Status Manager™ for MVS

Version 340

GC32-9233-00

September 2002

Candle Corporation201 North Douglas Street

El Segundo, California 90245-9796

2 OMEGACENTER Status Manager™ for MVS User’s Guide, Version 340

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

Copyright © August 2002, 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

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7About This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Adobe Portable Document Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Documentation Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

What’s New in OSM/MVS Version 340 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Getting Started

Chapter 1. Introduction to OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Availability Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Example of an OSM/MVS Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Chapter 2. The OSM/MVS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Action Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Action Codes and the Action Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Table and Entry Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Sorting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Using Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Exiting OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Chapter 3. OSM/MVS Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Probes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Status Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Relationships Between Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Relationship to OMEGAVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Chapter 4. OSM/MVS Additional Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Defining Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Invoking Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Directing Messages to OMEGAVIEW Special Panels . . . . . . . . . . . . . . . . . . . . . . . . . . .84

Contents


Setup

Chapter 5. Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92Setting Up Notification Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96Setting Up Notification Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99Rotation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107OMEGAVIEW Notification Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113Notification Default Values and Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115Making Notification Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Chapter 6. Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Assigning a Recommendation to a Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130

Chapter 7. Distributed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136DAS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137Using DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141

Chapter 8. Functional Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146Using RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .147Using CA-ACF2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149OSM/MVS Resource Definitions and Access levels. . . . . . . . . . . . . . . . . . . . . . . . . . . .152

Chapter 9. OSM/MVS Migration, Replication, and Distribution . . . . . . . . . . . . . . . . . . . . 159Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .161Replication and Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169Replicating OSM/MVS Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176Distributing OSM/MVS Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .184Displaying Replication and Distribution Information . . . . . . . . . . . . . . . . . . . . . . . . . .187

Controls

Chapter 10. General Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Setting Global Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192Setting File Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195OSM/MVS Assistant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197Displaying Actual Probe Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .201Updating OSM/MVS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .210Starting and Stopping OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213Managing the Message Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .216Balancing Probe Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

Contents 5

Chapter 11. Notification Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226Receiving Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227Resolving Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229Escalating Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230Refreshing Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .231

Developing an Availability Management Application

Chapter 12. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .235Introducing the Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236Case Study: Building a Sample Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Chapter 13. Monitoring for Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242Modifying the MVS Data Manager Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243Setting Thresholds for the Response Time Status Item. . . . . . . . . . . . . . . . . . . . . . . . .246Using the Probe Directive, Probe Input and Misc. Parms Fields . . . . . . . . . . . . . . . . . .248Specifying an Action Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .258Creating a Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260Sending a Recommendation to the Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263

Chapter 14. Monitoring for the Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .266Adding an Active Users Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .267Copying Source Code for the New Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271Adding a Status Item for User Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273Setting an Exception Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .277Evaluating Two Conditions as One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280Adding a Status Item for a Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

Chapter 15. Setting Up Distributed Systems Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . 287Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288Defining the Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289Copying and Modifying a DAS Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .291Adding a Status Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293Specifying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295Notifying Network Services Staff of an Offline Condition. . . . . . . . . . . . . . . . . . . . . . .297Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .300

Chapter 16. Building an Interface with OMEGAVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . .301Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302Building the Interface Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303Create the Detail Panel for Systems Management Staff . . . . . . . . . . . . . . . . . . . . . . . .306


Creating the Detail Panel for Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308Creating the Detail Panel for Field Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .310Creating the Main OMEGAVIEW Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .312

Appendix A. Writing a Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .316Status Item Values for Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .319Probe Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .320Example Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322Probe Code Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324

Appendix B. PROBELIB Sample Probes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332Probe Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333

Appendix C. REXXLIB Probes and Status Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341Using PROBELIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342Probe Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .342

Appendix D. Using the SHOWOSM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Purpose. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .348SHOWOSM Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .349Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .353

Appendix E. Guide to Candle Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .362Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .366Customer Support Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .369

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Preface 7

Preface

This OMEGACENTER Status Manager™ for MVS User’s Guide is designed for programmers of applications that provide availability views of an organization’s key business operations. This document contains:

n detailed descriptions of OMEGACENTER Status Manager for MVS (OSM/MVS) components, including probes, status items, situations, activities, and the Distributed Availability Subsystem (DAS)

n an explanation of the OSM/MVS user interface

n a case study that demonstrates how to build an availability management application

n a commented example of REXX code for a probe

Sections in this guideThis table shows where you can find information and instructions to help you learn how to use OSM/MVS.

If you want to... Turn to...

read a broad overview of the interface and basic components of OSM/MVS

“Getting Started” on page 15

find instructions for the tasks you need to perform before you can use OSM/MVS

“Setup” on page 89

find instructions for beginning to use OSM/MVS

“Controls” on page 189

practice using OSM/MVS to build a sample availability management application

“Developing an Availability Management Application” on page 233

P

About This Book


About This Book

Documentation set informationCandle provides a complete set of documentation for OMEGACENTER Status Manager for MVS. Each manual in this documentation set contains a specific type of information to help use the product. The relevant manual is

n OMEGACENTER Status Manager™ for MVS User’s Guide, Version 340, AT54-6544.For information on customizing OSM/MVS, see the OMEGACENTER Gateway for MVS Configuration and Customization Guide. It contains information on the following topics:

n using the Customizer

n setting system environments

n defining distributed systems

n defining VTAM applications

n defining logs

n defining system defaults

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

n technical documentation CD-ROM that came with your product

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

n online help provided with this product

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

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

You can also send email to [email protected]. Please include "OMEGACENTER Status Manager™ for MVS User’s Guide, Version 340" in the subject line.

Preface 9

Adobe Portable Document Format

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 forn Alln Current pagen 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:n 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.)n 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.)n 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.

n 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



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 literalsIn examples of command syntax, uppercase letters are actual values (literals) that the user should type; lowercase letters are used for variables that represent data supplied by the user. Default values are underscored.

LOGON APPLID (cccccccc)

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

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

Preface 11


SymbolsThe following symbols may appear in command syntax:

Table 1. Symbols in Command Syntax

Symbol Usage

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

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

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

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

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

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

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

_ Default values are underscored. Example:

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



What’s New in OSM/MVS Version 340 13

What’s New inOSM/MVS Version 340

This section provides a description of the new features that have been incorporated into OSM/MVS Version 340.

Online documentationWith Version 340, Candle Corporation has moved OSM/MVS 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 OSM/MVS manual. However, the manual remains 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.

Enhancements to product documentationAdditional documentation about using the Probe Directive, Probe Input, and Misc. Parms fields has been added to the OMEGACENTER Status Manager User’s Guide.

W


Section I: Getting Started 15

Section I: Getting Started

Introduction to OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17The OSM/MVS Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25OSM/MVS Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45OSM/MVS Additional Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69


Introduction to OSM/MVS 17

Introduction to OSM/MVS

OverviewThis chapter:

n describes the concept of availability management

n explains how OSM/MVS applications are used to manage availability

n includes an example of an OSM/MVS application

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Availability Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Example of an OSM/MVS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1

Introduction


Introduction

OSM/MVS componentsOMEGACENTER Status Manager for MVS (OSM/MVS) is a set of tools and interfaces designed to help you build availability management applications; that is, applications that ensure the availability of your enterprise’s business-critical system and network resources.

OSM/MVS consists of:

n a probe management system, which gathers data from the resources to be monitored

n a notification subsystem, which selects and notifies the correct staff when changes in status occur

n various managers and subsystems that expand on these capabilities, such as a status manager that allows you to process multiple sources of data and post their status, and a distributed monitoring system that gathers data from sources such as LANs and RS6000s

What OSM/MVS doesOSM/MVS allows you to build applications that:

n obtain availability data from a wide variety of sources, including:

– The OMEGAMON® family of products

– VTAM® applications

– MVS, VTAM, JES, and other subsystem console messages

– OMEGAVIEW®

– OMEGACENTER Gateway for MVS or AF/OPERATOR® facilities

– distributed computing systems (including LANs, DEC® VMS, Tandem™, RS/6000, AS/400®, and so on), through AF/REMOTE

n analyze the availability data to determine the status of system operations.

n pass the data to OMEGAVIEW, .Candle’s centralized status and alert facility.

n automatically initiate activities to perform further diagnosis, or to correct problem events or situations.


Availability Management


IntroductionAvailability management is the process of preventing and correcting threats to the availability of business-critical applications. In its attention to business objectives, availability management differs from traditional system management, which consists of monitoring and responding to changes in system performance. By focusing on the business goals of the computer systems, availability management bridges the gap between technical and business objectives.

OSM/MVS applications and availability managementIntegrating the availability design methodology into your OSM/MVS applications allows you to:

n focus on system issues having the greatest business impact

n prioritize the importance of resource availability across the enterprise

OSM/MVS applications provide the means to do the following.

1. Consolidate the results of monitors and other system and resource availability measurement tools.

2. Interpret the results in ways that are meaningful to critical business functions.3. Initiate activities to remedy problems.

Probes and status itemsOSM/MVS uses REXX programs called probes to obtain data from the resources to be monitored.

In the example shown above, one probe collects CICS transaction response time data, and a second probe collects CICS transaction throughput rate data.

Status items represent the data elements or attributes being monitored by the probes’ data collection activities. A status item can be simple, representing an attribute such as a single threshold (for example, CICS transaction rate), or can consist of logical combinations of several inputs, for example,

Example

Claims Processing might be considered unacceptably slow only if:n CICS transaction response time is more than 2 seconds andn CICS transaction throughput rate is less than 1,000 per minuteYou can set up an availability management application to initiate the following actions if both conditions are met.

1. Display a critical alert for Claims Processing.

2. Notify the appropriate data center staff.

3. Send a message to the Claims Processing manager.



IF CICS TRANSACTION RESPONSE TIME IS GREATER THAN 2 SEC

AND

CICS TRANSACTION RATE IS LESS THAN 1000

Integrated approachThe following figure illustrates the integrated approach of OSM/MVS to enterprise-wide availability management.

InterpretationOSM/MVS’s probes gather data from the resources to be monitored. Those resources can include:

n system, subsystem, and network resources monitored by OMEGAMONs

n network resources monitored by NetView

n VTAM applications

n automation facilities, such as console interfaces

n distributed computing systems, through AF/REMOTE



OG/MVS transmits the OSM/MVS probes to the monitored resources and returns the data the probes gather. OSM/MVS then uses predefined status items to do the following.

1. Evaluate the data.2. Associate it with a status.3. Display the status on an OMEGAVIEW panel.4. Initiate other activities (such as notification) in response to the status.Situations are aggregate status items used to evaluate a combination of more than one kind of data. In the Claims Processing example shown above, OSM/MVS determines the status of a business component by evaluating a combination of two kinds of data.

Example of an OSM/MVS Application



IntroductionThis section describes a basic availability management application that could be built with OSM/MVS and OMEGAVIEW.

OSM/MVS supplies the underlying structures, such as the data-gathering probes, the status items, and the action routines. OMEGAVIEW supplies the graphical interface that allows you to organize and present that information.

Business viewHere is the main panel of Alma Insurance Company’s availability management application. This panel shows the status of the company’s major business areas and permits navigation to other views.

Panel objectsThe key parts of this panel are status bars and pushbuttons. Status bars indicate the health of a monitored area, and pushbuttons allow you to navigate to different views.

In the figure, status bars are either green (indicated by light shading) or red (indicated by dark shading). Green indicates that resource availability for a business area is within acceptable

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/96 12:03:05 OMEGAVIEW Version nnn Alma Insurance Company Agency ///////// Actuarial ///////// Underwriting ///////// Claims Processing ///\\\\\\ ------------------------------------------------------------------------------ +----------------+ +-----------------+ | > Systems < | | > Telephones < | +----------------+ +-----------------+ F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel

///////// Green \\\\\\\\\ Red



limits; red indicates that availability is unacceptable, or critical. Although not shown in the figure, a yellow light is typically used to define a warning availability status.

InterpretationIn this example, Claims Processing has a status of critical (shown by the red light), indicating unacceptable resource availability. Other business areas have green lights. They are functioning within the availability limits defined for the enterprise.

Technical viewTo investigate the technical underpinnings of the Claims Processing availability problem, you could set up a Systems pushbutton on the main panel. Users could select this pushbutton to navigate to the following OMEGAVIEW panel.

InterpretationThis panel displays status bars for systems and subsystems monitored by OMEGAMONs. In this example, the source of the Claims Processing problem is a critical CICS condition on System A. Further navigation could lead the user to the exact cause of the CICS problem.

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/96 12:17:30 OMEGAVIEW Version nnn Alma Insurance Company TSO System B ///////// CICS System A ///\\\\\\ DB2 System B ///////// CICS System B ///////// ------------------------------------------------------------------------------ +----------------+ +-----------------+ | > Main Panel < | | > Telephones < | +----------------+ +-----------------+ F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel

///////// Green \\\\\\\\\ Red



Taking actionOSM/MVS allows you to take action when such a critical situation occurs. This can be accomplished through:

n notification lists, which identify individuals to notify if certain problems occur

n recommendations, which display console messages identifying the problem or suggesting courses of action

n action routines, which include problem resolution and follow-up programs

n exception and text messages displayed on OMEGAVIEW panels

In this example, when Claims Processing turns critical, a message could be sent to the head of Claims Processing and the appropriate data center staff, informing them of the situation and requesting corrective action.

The rest of this document gives detailed information and instructions for setting up OSM/MVS applications such as the one described above.

The OSM/MVS Interface 25

The OSM/MVS Interface

OverviewIn this chapter, you will learn how to:

n use the action bar to access OSM/MVS functions

n select from pull-down menus and pop-up windows

n add and modify information using action codes

n display help about OSM/MVS or any panel

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Action Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Action Codes and the Action Pull-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table and Entry Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Sorting Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Function Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Exiting OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2

Introduction


IntroductionIn this chapter, you will learn about the OSM/MVS interface and how to navigate through panels to customize and manage probes and the OSM/MVS configuration.

You will learn about the OSM/MVS main panel, which provides access to functions that let you:

n modify model probes to suit the operations of your site

n create customized recommendations that are automatically sent to the operator in response to a system event

n notify individuals or groups by page, TSO SEND, or WTO, and escalate the notification if no response is received

n record status changes to a log

Panels in OSM/MVS are based on the IBM® Common User Access™ (CUA™) standard. These standards are designed to facilitate ease of learning and use.

Note: If you are familiar with Candle’s implementation of IBM’s CUA standard, you may wish to go directly to “OSM/MVS Basics” on page 45, where OSM/MVS capabilities are explained.


Panels

Panels

IntroductionThe first panel that you see when you access OSM/MVS is the OSM/MVS main panel. From this panel, you access all functions.

Controls Managers Setup Preferences Help------------------------------------------------------------------------------ OMEGACENTER Status Manager for MVS Press F10 to select a function. Version 999 OOOOO SSSSS MM MM // MM MM VV VV SSSSS OO OO SS SS MMM MMM // MMM MMM VV VV SS SSOO OO SS MMMM MMMM // MMMM MMMM VV VV SSOO OO SS MM MM MM MM // MM MM MM MM VV VV SSOO OO SS MM MMM MM // MM MMM MM VV VV SSOO OO SS MM M MM // MM M MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SSS MM MM // MM MM VV VV SSSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VVV SS OO OO SS SS MM MM // MM MM VVV SS SS OOOOO SSSSS MM MM // MM MM VVV SSSSS Command ===> ___________________________________________________________________ F1=Help F3=Exit F10=ActBar

Panels


Panel featuresThe main panel areas are highlighted in this representative panel.

Panel formatThe four main areas of an OSM/MVS panel are called out in the figure above:

1. Action bar2. Action codes3. Table panel or entry panel (a table panel is displayed above)4. Function keys

_ Actions Managers Help 1 ------------------------------------------------------------------------------ OSM/MVS - DAS Manager ROW 1 FROM 52 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (R)efresh, (D)elete, and (>) Show Dependents. Distributed Item Name Probe ID -System ID- Active Flag _ L1_WLA_FIN_SERVER1 P82 L1 N _ PBE.ITEM3 T80 R1 N _ R1_RS6000_HEARTBEAT 081 R1 Y 3 _ R1_RS6000_LK 081 R1 N _ SEI_ITEM3 080 R1 Y Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar 4


Action Bar

Action Bar

IntroductionThe action bar appears at the top of many panels. You use it to access OSM/MVS functions.

The figure above shows choices available on the OSM/MVS main menu. Note that these choices are different from those available on the OSM/MVS - DAS Manager panel (displayed earlier). Not all choices are available from all panels. Action bar choices that are not available for a panel are not displayed.

Action bar choicesThe action bar choices, when selected, display other panels called pull-down menus.

Keyword Choice Purpose

Actions Display valid actions for fields that can be selected for action.

Controls n Start, stop and refresh OSM/MVSn Refresh and receive notificationsn Respond to and escalate incidentsn Balance probesn Write messagesn Replicate and distribute OSM/MVS imagesn Exit OSM/MVS

Managers Access probes, status items, situations, and DAS, which monitors distributed systems.

Setup Set OSM/MVS defaults for:n Notificationn Operator messagesn System environmentn DAS definitionsn VTAM definitionsn Log definitionsn Replication definitions.

_ Controls Managers Setup Preferences Help ----------------------------------------------------------------------------

Action Bar


Selecting from the action barTo select a choice from the action bar:

n Tab to the left of a choice and press Enter

Result: A pull-down menu is displayed.

To access Help, for example:

1. Move the cursor to the action bar by pressing F10.2. Tab to Help and press Enter.Result: The Help pull-down menu is displayed.

Selecting from a pull-downTo select from a pull-down menu:

n Type the number of the item at the cursor position and press Enter.

or

n Move the cursor to your selection and press Enter.

For example, to select Keys help... from the Help pull-down menu:

n Type 3 at the cursor position and press Enter.

Result: An explanation of function keys is displayed.

Preferences Set enterprise-wide defaults for:n Global preferences (e.g., OMEGAVIEW text type, peer link

settings, trap and other prefixes, session recovery settings, actual status display settings, special panels and security class).

n Notation preferences.n File preferences (e.g., OSM/MVS REXX library and dataset,

display panel and startup dataset).

Help Access the Help facility.

Keyword Choice Purpose

Actions Display valid actions for fields that can be selected for action.

Controls n Start, stop and refresh OSM/MVSn Refresh and receive notificationsn Respond to and escalate incidentsn Balance probesn Write messagesn Replicate and distribute OSM/MVS imagesn Exit OSM/MVS


Action Bar

EllipsisEllipses (...) follow some selections on pull-downs. They indicate that additional information is required and that a pop-up is displayed when you choose this selection.

For example, each selection on the Managers pull-down is followed by an ellipsis.

+----------------------------+| _ 1. Probe Manager... || 2. Status Manager... || 3. Situation Manager... || 4. DAS Manager... |+----------------------------+

Action Codes and the Action Pull-down



IntroductionOSM/MVS information such as probe definitions and data source definitions is stored in tables. Action codes let you perform actions on the tables. The action codes that are available for the current panel are displayed below the action bar and on the Actions pull-down.

For example, the Probe Manager panel displays these action codes..

Using action codesThis table shows the main action codes and their use, using the Probe Manager panel as an example. You enter the code on the selection field, represented by a single underscore character preceding each entry in the table panel area.

Action Code Definition How to use

A Add a probe Type A on any selection field to add a probe.

Result: The Add a Probe pop-up appears. A new probe is added to the table in alphanumeric sequence when you complete the popup panel and press Enter.

C Copy a probe Type C on the selection field of the item that you want to copy.

Result: A pop-up displays the detailed information in the record.

Type over existing information to create a new record. Review the help for the current panel for a definition of the fields that must be changed.

Actions View Managers Help ------------------------------------------------------------------------------ OSM/MVS - Probe Manager ROW 1 FROM 156 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate, and (>) Show Dependents. ----------------------------------------------------------------------------



M Modify a probe Type M on the selection field of the item you want to modify.

Result: The Modify pop-up appears.

Type over any current information that you want to change.

R Refresh a probe Type R on the selection field of the item you want to refresh.

This action activates the parameters of the item you selected.

D Delete a probe Type D on the selection field of the item you want to delete.

Result: The Delete Confirmation pop-up appears.

You can cancel the deletion by pressing the Cancel key.

F Find a probe in a table Type F on any selection field to display the Find pop-up. Enter one or more characters of the string to find. The Find action is case-sensitive.

E Edit a probe Type E on the selection field of a probe to display the REXX source code of that probe. Edit the source code as necessary and press the Exit key to apply your changes.

I Inactivate a probe Type I on the selection field of a probe to render an active probe inactive.

T Activate a probe Type T on the selection field of a probe to render an inactive probe active.

> Show a probe’s dependent components

Type > on the selection field of a probe to display the components which directly depend on the probe for data and proper execution.

Action Code Definition How to use



ExampleWhen you select Status Manager... from the Managers pulldown, the Status Manager panel is displayed.

n Type M to the left of a Probe ID and press Enter.

Result: The Modify Status Item pop-up is displayed.

_ Actions View Managers Help ------------------------------------------------------------------------------ OSM/MVS - Status Manager ROW 1 FROM 296 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, (F)ind, (R)efresh, (M)odify Status Item, Modify Critica(L), (W)arning, (O)K, and (N)one Activities. Probe Status Item Name Description System Domain _ 028 AMS_OMEGAVIEW_B Omegaview on System B B B _ 011 AMS_STC_CSA_COUNT Monitor CSA Usage On SYSG G G _ 050 ACTIVE_TASK_OMVTAMB OMEGAMON for MVS on Syste B B _ 031 CICS_ETE_RESP_B CICS End-to_end Resp.(B) B B _ 039 CICS_TRANS_RATE_B Transaction Rate for CICS B B _ JH5 MONITOR_TSO_USERS Tso users G G _ 004 MVS_TSO_USERS MVS TSO active users B B _ 028 NCP_021 CMC NCP 3745 at HQ B B _ 050 ORDER_RZZ_ACTIVE Diagnostics Ordering G G _ 999 RBE_AMS_STATUS4 RBE AMS Print Jobs B B _ 081 R1_RS6000_HEARTBEAT RS6000 Heartbeat G R1 _ 080 SEI_ITEM3 RS6000 CPU Utilization B R1 Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

+----------------------------Modify Status Item------------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . . . 028 VTAM Heartbeat || System ID . . . . . B32_____ + || Domain ID . . . . . B3______ + || Status Item . . . . AMS_OMEGAVIEW_B_____ || || Description . . . . OMEGAVIEW on System B___________________ || Default Status . . . NONE + || Threshold OK . . . . YES_________________ || Threshold Critical . NO__________________ || Spikes Check . . . . N (Y/N) || Log Status Change . N + || OMEGAVIEW Text Type Transient Text + || Probe Input . . . . ________ + || Probe Directive . . MVGATSDM____________ || Misc. Parms . . . . ________________________________________ || F1=Help F4=Prompt F12=Cancel |+----------------------------------------------------------------------------+



The Actions pull-downValid actions for the current panel are also available from the Actions pull-down, the first choice from the action bar. They are the same actions displayed in the action code area. The figure below shows all the actions that could appear on the Actions pull-down for the Status Manager panel.

+-----------------------------------+| __ 1. Add... || 2. Copy... || 3. Delete... || 4. Find... || 5. Refresh || 6. Modify Status Item... || 7. Modify Critical Activity... || 8. Modify Warning Activity... || 9. Modify OK Activity... || 10. Modify None Activity... || 11. Exit (F3) |+-----------------------------------+

Using the Actions pull-downTo use the Actions pull-down:

Step Action

1 Type a / next to the item of interest in a table.

2 Press F10 to move the cursor to the action bar.

3 Press Enter when the cursor is next to Actions.

Result: The Actions pull-down is displayed.

4 Type the number of the action or move the cursor beside the action that you want and press Enter.

Result: Either the action is performed or a pop-up is displayed that enables you to perform the requested action.



ExampleTo modify a probe:

Step Action

1 Select Managers from the Action bar.

Result: The Managers pull-down is displayed.

2 Select Probe Manager... from the pull-down.

Result: The Probe Manager table is displayed.

3 Type / in the selection field of the probe ID.

4 Press F10 to return to the action bar.

5 Press Enter to display the Actions pull-down.

6 Type 3 (Modify) and press Enter.

Result: The Modify a Probe pop-up is displayed.

Actions View Managers Help------------------------------------------------------------------------------ OSM/MVS - Probe Manager ROW 73 FROM 139 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify,(R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate,and (>) Show Dependents. ---------------------------------------------------------------------------- ID Probe Description Type System Domain A S_ 036 CICS VSAM waits Q G G N N_ 038 CICS Dataset Status Q G G N N_ 050 Active Tasks H G G N N_ 050 Active Tasks H SYSG3 SYSG3 N ?_ 051 MVS Batch Job count Q G G N N_ 052 MVS Started Task count Q G G N N_ 053 MVS Tape mount requests Q G G N N_ 054 MVS Intervention Required Coun Q G G N N_ 055 TSO Response Time Q G G N N_ 056 TSO Transaction Rate Q G G N N_ 056 TSO Transaction Rates Q SYSG3 SYSG3 Y ?_ 057 MVS Initiator status H G G N N_ 058 MVS Job class queues Q G G N N_ 059 MVS JES printer status H G G N N_ 066 CPU performance by task Q G G N N_ 071 TSO End-to-End Tran Rate Q G G N N_ 072 TSO End-to-End Host Response Q G G N N_ 073 TSO End-to-End Net Response Q G G N N Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar


Table and Entry Panels


IntroductionIn OSM/MVS:

n A Table panel displays a table of data and lets you select an item for action.

n An Entry panel displays the current detail of a table entry or displays a blank panel for data entry.

Using a table panelWhen you select an action from the Managers or Setup pull-down on the OSM/MVS main panel, a table panel is displayed. For example, when you select Users to Notify... from the Setup pull-down, the Notify Users table panel is displayed.

To use the panel:

Step Action

1 Tab to the selection field, the underscore to the left of the item of interest.

2 Type an action code and press Enter.

Result: A pop-up window is displayed.

_ Actions Help ------------------------------------------------------------------------------ OSM/MVS - Notify Users ROW 1 TO 7 OF 7 Select a row and press Enter. Valid actions are A(dd), M(odify) and D(elete). User ID User Name _ STAF01 Jan Garcia _ STAF02 Stella Morris _ STAF03 Gail Merriman _ STAF03A Robert Ling _ STAF04 Albert Smith _ STCS14 Ronald Jones _ STCS15 Bill Huston ******************************* BOTTOM OF DATA ******************************** Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Navigating in a table panelTo navigate in a table, use these keys:

ScrollingWhen more information is available than can be displayed on a single panel, you can scroll through the panels using the Backward and Forward function keys.

One of the following scroll indicators appears in the upper right corner of the panel:

ROW nnnn FROM nnnn

The first number shows the total number of rows currently displayed on the panel; the second number shows the total number of rows available for display.

ROW nnnn TO nnnn OF nnnn

The first two numbers show the rows currently displayed on the panel; the third number shows the total number of rows available for display.

Using an entry panelAfter you select an item from a table panel with an action code, an entry panel is displayed. For example, if you type A (for Add) in the selection field on the Notify Users table, the Add User entry panel is displayed.

+------------------ Add User ------------------+| OSM/MVS - Notify Users || || Fill in the information, then press Enter. || || User ID . . ________ || User Name . ______________________________ || Work Phone . ____________________ || Home Phone . ____________________ || Pager Phone ____________________ || Pager Type . _ (M/T) || Pager Number . __________________ || || || F1=Help F12=Cancel |+----------------------------------------------+

Key Description

Tab To move from item to item.

End or Cancel To close a panel without action.

Enter Access probes, status items, situations, and DAS, which monitors distributed systems.



Navigating in an entry panelTo navigate in an entry panel, use these keys:

Key Description

Tab To move from field to field

Help To display help information about the kind of data that is required

Prompt For fields followed by a plus (+) sign, display a list of choices to select from

Exit or Cancel To close a panel without changes

Enter To update with the changes that you made

Sorting Data


Sorting Data

DescriptionInformation in OSM/MVS panels can span several screens. You can modify the display by using the View choice from the action bar. View acts as a filter, allowing you to display only those rows of data you want.

Using View in the Probe Manager You will probably want to use the View feature in the Probe Manager panel. There, the View pull-down has these selections:

+------------------------------------+|- 1. Sort by Probe ID || 2. Sort by Probe Description |+------------------------------------+

The default is Sort by Probe ID.

View in the Status ManagerIn the Status Manager, the View pull-down has these selections:

+------------------------------------+|- 1. Sort by Status Item || 2. Sort by Probe ID |+------------------------------------+

The default is Sort by Status Item.

Using the View pull-downAfter you type 1 or 2 and press Enter, the data on the panel is sorted and displayed according to your selection.


Function Keys

Function Keys

DescriptionFunction keys provide a quick way to use OSM/MVS features, such as getting help or scrolling through panels. Active keys and their uses are displayed at the bottom of the panel. Only the function keys that are available for a panel are displayed on that panel.

Function key tableOSM/MVS supports the ISPF function key definitions shown in the table below. (Function keys F1 - F12 correspond to functions keys F13 - F24 respectively).

Function Key Use Description

F1 Help Displays a pop-up explaining the current panel.

F3 Exit Exits from the current panel and returns one level in the display hierarchy.

F4 Prompt Displays a list of valid entries for the field. Entry fields with a plus sign (+) indicate that you can press the Prompt key to display a list of entries for that field. The cursor must be on the entry field when the Prompt key is pressed.

F7 Backward Scrolls backward if more lines exist than can be displayed on the current panel.

F8 Forward Scrolls forward if more lines exist than can be displayed on the current panel.

F10 Action Bar Moves the cursor to the action bar to allow selection of a pull-down menu. If the cursor is already on the action bar, the cursor is moved to its prior position in the display.

F12 Cancel Cancels a panel, displaying the previous panel.

F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar F12=Cancel

Using Online Help


Using Online Help

IntroductionOSM/MVS has an online help facility that displays explanations about panels and fields and instructions for using OSM/MVS. You can display Help

n from the action bar by selecting the Help choice

n from any panel by pressing the Help key

Help pull-downFrom the Help pull-down, you can select from four topics:

+--------------------------+| || _ 1. How to get help... || 2. Extended help... || 3. Keys help ... || 4. Glossary... || || |+--------------------------+

Help topicsThe four Help topics are described in this table.:

Help Choice Description

How to get help Explains how to use the Help facility.

Extended help Gives an overview of OSM/MVS functions and features.

Keys help Describes the assignment of function keys.

Glossary Defines OSM/MVS terminology.


Using Online Help

ExampleTo learn about the functions of OSM/MVS:

Help from a panelWhen you use help from the action bar, you get general help on OSM/MVS. To display help specific to a displayed panel and its fields:

n press the Help key

You can scroll through and exit from panel help screens as described above for general help.

Step Action

1 Tab to Help and press Enter.

Result: The Help pull-down is displayed.

2 Place the cursor before Extended help or type 2 at the underscore.

3 Press Enter.

Result: The Welcome panel is displayed.+------------------------------------------------------------------+| OMEGACENTER Status Manager for MVS Main Panel || || More: + || Welcome to the OMEGACENTER Status Manager for MVS. || || || Introduction || || The OSM/MVS is a panel driven system which enables you to: || || o Set up monitoring routines called probes, which gather || system data. || || o Set up thresholds and rules for the incoming data, || called status items, which then define the status of || the system as OK, Warning, Critical, or None. In || || || F1=Help F3=Exit F7=Backward F8=Forward |+------------------------------------------------------------------+

4 Press the Forward and Backward keys to move through the help text.

5 Press the Cancel key or the Exit key to exit the help facility and display the OSM/MVS main panel.

Exiting OSM/MVS


Exiting OSM/MVS

ProcedureTo exit OSM/MVS:

n Press the Exit key or select Exit (F3) from the Controls pull-down on the OSM/MVS main panel.

OSM/MVS Basics 45

OSM/MVS Basics

OverviewOSM/MVS lets you build sophisticated data gathering and evaluation routines, connect those routines with status lights for meaningful display, and take a variety of actions based on a particular status.

This chapter describes the following major product capabilities.

Chapter ContentsProbes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Status Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Relationships Between Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Relationship to OMEGAVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Function Description

Gathering Data Build probes to gather availability data from systems and resources such asn MVS, CICS, DB2, and VTAMn distributed systems and networks

Creating Status Items Analyze the data collected by each probe and assign a status (OK, warning, critical, idle) based on preset thresholds.

Building Situations Build complex status items, or situations. These are status items composed of logical combinations of different pieces of data. Situations are used to perform activities based on data collected from a number of probes.

Notification Maintain a list of names for notification. When changes in a status item or situation occurs, individuals or groups from the list are selected and notified that a problem requires their intervention.

3

Probes


Probes

IntroductionProbes are programs that obtain data from the systems and resources you want to monitor. OSM/MVS supplies numerous probes that you use to build availability management applications. These range from probes that gather OMEGAMON data from sources such as MVS and CICS, to probes that check whether components of a distributed system or LAN are operational.

You can customize any probe to suit the requirements of your particular system configuration, or to enhance its capabilities. For information on customizing a probe, see “Writing a Probe” on page 315.

What probes measureProbes extract data from managed objects. Managed objects may include systems and subsystems such as MVS, CICS, DB2, VTAM, LANs, distributed systems such as a network of RS6000s, and resources such as printers, storage devices, and communication lines.

OSM/MVS probe librariesA set of probes and their source code is provided in an executable library called REXXLIB. This set of probes is designed to cover basic types of availability management applications. A list of these probes is provided in “REXXLIB Probes and Status Items” on page 341.

An additional, larger set of probes is provided in PROBELIB, the sample library. You can use these probes as models for additional probes that you may want to write to handle the special data-gathering needs of your application. Because these probes are in the sample library, you need to copy the ones you want to REXXLIB before using them. A list of these probes is provided in “PROBELIB Sample Probes” on page 331.

Probe typesThe following table lists all the OSM/MVS probe types along with their type IDs and a short description of how each probe works. Each probe type has a different purpose and uses a different method of gathering and storing information.

Type ID Type Description

A Initialization Runs only when OSM/MVS is started.

D OMEGAMON Data Manager

A type of heartbeat probe that collects OMEGAMON data from multiple sources for other dependent probes.

DG OMEGAMON Compiled Data Manager

A type of query probe that collects OMEGAMON data resulting from execution of commands to OMEGAMON. This probe uses the DP probe status item definition Probe Input field as a pointer to the definition source for the command(s).

OSM/MVS Basics 47

Probes

Note: O, S and T probes are system probes not available to users.

DP DG Dependent Query

A type of query probe that parses OMEGAMON data returned from the DG it is dependent upon to determine whether execution of one or more OMEGAMON commands has caused a change in status.

E Event Executes in response to a particular system event, such as a batch job exception or abend.

EM MVS Event Executes in response to any MVS event. The Probe Input field on the Status Item panel contains a pointer to where the MVS event is defined.

EO OMEGAMON Event

Executes when a defined OMEGAMON exception event occurs. The OMEGAMON event is defined in the user interface.

H Heartbeat Determines whether a particular subsystem is active or available by issuing requests directly to the environment or to the data manager for that environment.

M Distributed Data Manager

A Data Manager probe that gathers data from distributed

platforms.

O OMEGAVIEW Data Manager

A Data Manager probe that gathers data from OMEGAVIEW.

Q Query Obtains performance measurements by issuing requests directly to the environment or to the data manager for that environment.

QM MVS Query Obtains MVS information by issuing requests in the form of user commands to MVS. The Probe Input field on the Status Item panel contains a pointer to where the MVS command is defined.

S Situation Manager An internal probe that governs the situations or complex status items you define.

T Peer Link An internal probe that maintains operability of subsystems such as notification when peer-to-peer connections are disrupted or reconnected.

X Distributed Counterpart to the Distributed Data Manager. It gathers distributed data for display to OMEGAVIEW.

Type ID Type Description

Probes


This section describes the four basic probe types more fully:

n Event or “E” probe.

n Heartbeat or “H” probe.

n Query or “Q” probe.

n Data Manager or “D” probe.

The other probe types are based on one of the four basic probes.

Event probesEvent probes are executed as the result of some system event or alert..

Heartbeat probeHeartbeat probes work by polling the system or resource at regular intervals. You use heartbeat probes to determine whether a particular resource is available.

Query probeYou use query probes to obtain measurements by issuing commands directly to an environment.

Data manager probeData manager probes collect information for (on behalf of) two or more probes. Their purpose is to prevent degradation in system performance by reducing the number of individual requests for data.

Data manager probes are available only for information provided by a Candle OMEGAMON or DAS. They are not available for other subsystem environments such as MVS, VTAM, or

Example

Probe 345 is an event probe that monitors a payroll application. When the payroll batch job begins, the probe is activated. If the job abends, the probe detects that event.

Example

Probe 028 is a heartbeat probe that checks whether a particular VTAM node is active.

Example

Probe 030 issues a command that queries a selected CICS for transaction response time.

OSM/MVS Basics 49

Probes

JES. Probes collect availability data from those subsystems by accessing and parsing the messages they write to the system console.

The REXX source code for the data managers is supplied with OSM/MVS. This enables you to modify a data manager or to use one as a model for a data manager that you write.

For information on the different types of data manager probes, see “Probes” on page 46.

Note that eight-character probe IDs can cause the trap action limit of 128 characters to be exceeded. Therefore, if you use eight-character probe IDs for dependent query probes, you must add the following code fragment to your Data Manager. DG probes are exempted from this additional coding requirement.

Add the code at the point at which the probe is entered after parsing the variable PROBE_PARM in the incoming argument string.

IF PROBE_PARM = ‘REXX_SHARED_VARIABLE’ THEN

DO

RSV_NAME = ‘@OGAT.@PROBE_PARMS.’DATAMG_PROBE_ID

IF \ GETSHARED(“SYSTEM”,RSV_NAME) THEN

DO

MSG_PARMS = RSV_NAME R_C

MSG_ID = ‘KAT0077E’

SIGNAL ERROR1

END

PROBE_PARM = @OGAT.@PROBE_PARMS.DATAMG_PROBE_ID

END

Accessing probesYou access probes as follows:

n Select Probe Manager... from the Managers pull-down on the OSM/MVS main panel.

Result: The Probe Manager panel appears.

Example

Probe B09 is an OMEGAMON for MVS Data Manager probe that collects data for:n probe 055 (TSO response time)n probe 056 (TSO transaction rate)n probe 707 (paging rate)

Probes


The Probe Manager panelThe Probe Manager panel is shown below. It is the central point of reference for working with probes.

The panel consists of the following key parts (labeled on the figure):

Item Name Description

1 Action Bar Contains the following selections:

Actions Performs actions on the probes. The actions are the same as those listed for Action Codes (item 2 on the figure).

View Sorts the list of probes.

Managers Access status items, situations, and DAS, which monitors distributed systems.

Help Displays general help.

Actions View Managers Help 1 ------------------------------------------------------------------------------ OSM/MVS - Probe Manager ROW 1 FROM 157 2 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify (R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate, and (>) Show Dependents. 3 4 5 6 7 8 9 ---------------------------------------------------------------------------- ID Probe Description Type System Domain A S _ AA1000LH MVS TSO user count Q G G N N _ AA1234LH Data manager probe D G G N N _ AA2123LH Check CP usage DP G G Y Y _ AEM00001 Test EM probe EM G G Y N _ AJB New OMEGAMON Event Probe EO G G Y N _ DGPS0001 test dg datamanager DG G G Y Y _ E01 cics tran resp time E A A N N _ E50 Active Tasks H G G N N c 003 MVS TSO user count Q G G N N _ 006 CPU Utilization Q G G N N _ 007 Page rates Q G G Y Y _ 008 DASD pool response Q G G N N _ 009 TSO User counts Q G G N N _ 010 Batch Job Events E G G N N _ 011 DASD Space / Total, Free or Co Q G G N N _ 020 VTAM Node Alert Monitor E G G N ? _ 021 VTAM Node Performance Monitor E G G N N _ 027 VTAM Users Query (SYSA) H A A N N Command ===> _________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

OSM/MVS Basics 51

Probes

2 Action Codes List of actions for performing operations on a selected probe. In the figure, a C (for copy) action code is entered in the selection field of probe 003.

A Add a probe. When placed in the selection field of any probe, allows you to build a new probe.

C Copy an existing probe.

M Modify an existing probe.

R Update or refresh a probe with values just entered.

D Delete a probe.

F Find a probe. When placed in the selection field of any probe, allows you to search for a particular probe.

E Edit the REXX source file of the probe.

I Inactivate a currently active probe and send inactivate command to OSM/MVS.

T Activate a currently inactive probe and send activate command to OSM/MVS.

> Display the components which directly depend on a probe for data and proper execution.

3 Probe ID System identifier for a probe.

4 Probe Description Text description of a probe.

5 Probe Type One- or two-character type code that classifies a probe (for example, D=Data manager, E=Event, H=Heartbeat, Q=Query). For a complete list, see “Probe types” on page 46.

6 System The system on which the probe is running.

7 Domain The system on which the objects monitored by the probe are running.

8 Active Status The desired state of the probe: Y means the probe has been activated; N means the probe is inactive.

9 Actual Status The actual status of the probe: Y is active, N is inactive, ? is not known. (See “General Operational Features” on page 191 for more information.)


Probes


Building probesYou build a probe by:

1. Selecting a probe with an action from the Probe Manager panel, such as A (add a probe), C (copy a probe), or M (modify an existing probe).

2. Defining the probe by completing the sequence of panels that follow. This may require information on the probe, status items you attach to it, and thresholds for status item conditions.

3. If you are adding a new probe, copying the probe source code from PROBELIB, the sample library, into the new probe source file.

4. Refreshing the new probe.These procedures are covered in detail in the Case Study part of the manual. See “Monitoring for Customer Support” on page 241 for modifying an existing probe, “Monitoring for the Data Center” on page 265 for adding a new probe, and “Setting Up Distributed Systems Monitoring” on page 287 for copying an existing probe.

OSM/MVS Basics 53

Status Items

Status Items

IntroductionStatus items are basic building blocks for OSM/MVS applications. These status items are the means by which the data gathered by probes is evaluated, associated with a status, and displayed by OMEGAVIEW.

A basic set of status items is supplied with the product. These status items are designed to work with specific probes. Like the supplied probes, you can use them as supplied or as models for additional status items you want to create. A list of supplied probes and status items is provided in “REXXLIB Probes and Status Items” on page 341.

Value and statusEach managed object monitored by a probe returns a value. A value can be Yes, No, NO_DATA, or a number.

A status is the result of comparing the value gathered by the probe with one or more predefined thresholds. Based on the comparison, OSM/MVS assigns the status to one of four possible categories. This information is passed to OMEGAVIEW for display as one of four colored lights.

Defining a status itemYou define status items for probes through the:

n Status Manager

n OSM/MVS Assistant

Examplesn The value for CICS transaction response time might be 0.1 seconds.n The value for the DB2 subsystem availability indicator could be Yes

(available) or No (not available).

Status Light Color Meaning

None Turquoise The managed object is not being monitored.

OK Green The value returned from the managed object is less than or equal to the acceptable threshold.

Warning Yellow The value returned from the managed object is somewhere between the acceptable and unacceptable thresholds.

Critical Red The value returned from the managed object is greater than or equal to the unacceptable thresholds.

Status Items


Accessing the Status ManagerThe Status Manager provides a central reference point for working on status items. To access the Status Manager:

n Select Status Manager... from the Managers pull-down on the OSM/MVS main panel.

Result: The Status Manager panel appears.

The Status Manager panelThe Status Manager panel lists status items and their associated probes.

_ Actions View Managers Help 1 --------------------------------------------------------------------------------- OSM/MVS - Status Manager ROW 85 FROM 292 2 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, (F)ind, (R)efresh, (M)odify Status Item, Modify Critica(L), (W)arning, (O)K, and (N)one Activities. 3 4 5 6 7 ---------------------------------------------------------------------------- Probe Status Item Name Description System Domain _ 028 ACC_OMEGAVIEW_G ACC Omegaview SDM (TDAFS0 G G _ 028 ACC_OMEGAVIEW_G01 System-G OMEGAVIEW ($MV12 G G _ 028 ACC_OMEGAVIEW_G02 ACC Omegaview session (TD G G _ 028 ACC_OMS_ACB_G3 TDAFs03 acb SYSG3 S _ 050 ACTIVE_TASK_OMVTAMG OMEGAMON for MVS on Syste G G _ 050 ACTIVE_TASK_TDAFS01 OSM/MVS test system on SY SYSG3 S _ 050 ACTIVE_TASK_TDAFS03 Another OMS system on SYS G G _ 050 ACTIVE_TASK_VTAM OMEGAMON for MVS on Syste G G _ AJB AJB_TEST Test XREP exception G G _ 028 APPL_ACT_OIVTAMG OIVTAMG Applid Active Ite G G _ 028 APPL_ACT_OI110G OI110G Applid Active Item G G _ 027 APPL_STATUS_C2100A Number of C2 V100 Status A A _ 027 APPL_STATUS_DBVTAMT OMEGAMON/DB2 User Status A A _ 027 APPL_STATUS_DF2100A OMEGAMON SMS User Status A A m QMPS0001 GS_QM_STATUS1 Test of QM probe G G _ PS5 GS_STC number of stc’s G G _ DP000001 GS_TEST_DP_1 test dp probe G G _ AEM00001 GS_TEST_EM_1 test em status item G G Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

OSM/MVS Basics 55

Status Items

The panel contains the following key parts (labeled on the figure):



Actions Performs actions on the status items. The actions are the same as those listed for Action Codes (item 2 on the figure).

View Sorts the list of status items.

Managers Access probes, situations, and DAS, which monitors distributed systems.


2 Action Codes List of actions for performing operations on a selected status item. In the figure, a M (for modify) action code is entered next to status item GS_QM_STATUS1.

A When placed in the selection field of any status item, allows you to build a new status item.

C Copy an existing status item.

D Delete a status item.

F When placed in the selection field of any status item, allows you to search for a particular status item.

R Update or refresh a status item with values just entered.

M Modify an existing status item.

The Critical, Warning, Ok, and None codes allow you to attach activities to these status conditions. For example, you can direct a message to the operator console when a particular status item turns critical.

3 Probe System identifier for a status item.

4 Status Item Description

Unique internal name identifying the status item to OSM/MVS and OMEGAVIEW.

5 Description Freeform text description of the status item.

6 System The system on which the probe is running.

7 Domain The system on which the objects monitored by the probe are running.

Status Items


The OSM/MVS AssistantThe OSM/MVS Assistant helps you define and attach a status item. It prompts you and provides messages if any information is missing, incomplete, or incorrect.

In the figure, a probe has just been copied, and the OSM/MVS Assistant panel indicates that a status item needs to be added.

“OSM/MVS Assistant” on page 197 describes how to use this feature. For examples of setting up status items with the OSM/MVS Assistant, see “Monitoring for the Data Center” on page 265 and “Setting Up Distributed Systems Monitoring” on page 287 in the Case Study part of this manual.

+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 5 OF 7 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Probe has been copied, now select the Status Item || to build Status and Activity rows for the Probe. || || ----------------------------------------------------------------------- || Type Name Condition || _ Program ** Add New **PRBEXEC Required || _ Status Item ** Add New ** Required || _ Act-WARNING ** Add New ** Not Available || _ Act-OK ** Add New ** Not Available || _ Act-NONE ** Add New ** Not Available || ** Copy completed successfully || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel || |+----------------------------------------------------------------------------+

OSM/MVS Basics 57

Situations

Situations

IntroductionA situation is a named, composite status item consisting of up to five rules combined with AND or OR logical operators. A rule consists of three parts:

1. a status item or another situation2. a comparison function (equal to, not equal to, less than, greater than, and so on)3. a value or status, or the resolved value of another situationSituations behave like any other status item. They are listed on the Status Manager panel and can initiate actions.

ExampleYou have a service level agreement specifying that CICS response time is to be less than 2 seconds as long as the transaction throughput rate is less than 1,000 per minute. You define a situation, named SERVICE_POOR that consists of two rules connected by AND:

n CICS_RESP_TIME GE 2 AND

n CICS_TRAN_RATE LT 1000

Result: All situations evaluate to either True or False. If rules 1 and 2 above are both True, the SERVICE_POOR situation is True. Otherwise, it is False.

Note that another situation can be part of a situation definition. For example, you define a situation named NO_SERVICE in terms of a second situation (SERVICE_POOR) as follows:

n SERVICE_POOR EQ TRUE AND

n DB2_AVAILABLE EQ FALSE

Evaluating a situationDifferent user-specified activities can be initiated for situations that are True or False. For example, if the NO_SERVICE situation defined above evaluates True, you can turn the OMEGAVIEW status light for the situation red and notify the data center manager through a pager. If the situation evaluates False you can turn the status light green.

Situations


The Situation Manager panelYou access and define situations through the Situation Manager. This is available as a selection from the Managers pull-down of the main panel.

_ Actions Managers Help 1 ------------------------------------------------------------------------------ OSM/MVS - Situation Manager ROW 1 FROM 16 2 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (R)efresh, (D)elete, and (>) Show Dependents. 3 4 5 6 7 Situation Name System ID Domain ID Active Flag Enable Warnings r RESP_TIME_A_PROB B B N N _ SERVICE_POOR B B Y N _ TESTING_POOR B B N N _ TSO_USER_TOTALS B B Y N _ TSO_USER_TOTALS_G G G Y N _ USER_RESP_TIME B B Y N _ USER_RESP_TIME_1 B B Y N ******************************* BOTTOM OF DATA ******************************** Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

OSM/MVS Basics 59

Situations

The panel contains the following key parts (labeled on the figure):



Actions Performs actions on the status items. The actions are the same as those listed for Action Codes (item 2 on the figure).

Managers Access probes, status items, and DAS, which monitors distributed systems.


2 Action Codes List of actions for performing operations on a selected status item. In the figure, a R (for refresh) action code is entered next to situation RESP_TIME_A_PROB.

A When placed in the selection field of any situation, allows you to build a new situation.

C Copy an existing situation.

M Modify an existing situation.

R Update or refresh a situation with values just entered.

D Delete a situation.

> Display the dependent status item record for the situation.

3 Situation Name Unique internal name identifying the situation to OSM/MVS and OMEGAVIEW. These names also appear as status item names on the Status Manager panel.

4 System ID The system on which the attached probe is running.

5 Domain ID The system on which the objects monitored by the probe are running.

6 Active Flag Whether the situation is active (Y) or inactive (N).

7 Enable Warnings When warnings are enabled (Y), a warning status occurs if only one of the conditions of the situations evaluates to true.

Situations


Defining situationsThe table below shows the basics of defining a situation. For an in-depth example of defining a situation and attaching it to a probe see “Monitoring for the Data Center” on page 265.

Step Action

1 Select Situation Manager... from the Managers pull-down on the OSM/MVS main panel.

Result: The Situation Manager panel is displayed..

_ Actions Managers Help -------------------------------------------------------------------------- OSM/MVS - Situation Manager ROW 1 FROM 16 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (R)efresh, (D)elete, and (>) Show Dependents. Situation Name System ID Domain ID Active Flag Enable Warnings _ RESP_TIME_A_PROB B B N N _ SERVICE_POOR B B Y N _ TESTING_POOR B B N N _ TSO_USER_TOTALS B B Y N _ TSO_USER_TOTALS_G G G Y N _ USER_RESP_TIME B B Y N _ USER_RESP_TIME_1 B B Y N ******************************* BOTTOM OF DATA *************************** Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

OSM/MVS Basics 61

Situations

2 Enter the A action code in the selection field of any row to define a new situation. Press Enter.

Result: The Add Situation panel appears.+------------------------------ Add Situation --------------------------+| OSM/MVS - Situation Manager || || Fill in the information, then press Enter. || || Situation Name . ____________________ || Probe Desc . . : || Probe ID . . . . ________ + System ________ + Domain ________ + || Active Flag . . Y (Y/N) || Enable Warnings N (Y/N) || || Status Item Name Comparator Value And/Or || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ || || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+

3 Fill in the information requested. Notice that the Status Item Names and Comparators fields are promptable. Pressing the Prompt key with the cursor on one of those fields allows you to display and select from a list of all status items and logical operators.

An example of a completed panel is shown below. It defines situation WIDE_AREA_NETWORK_6, which checks the status of a group of servers.+------------------------------- Add Situation ------------------------------+| OSM/MVS - Situation Manager || || Fill in the information, then press Enter. || || Situation Name WIDE_AREA NETWORK_6 || Probe Desc . : Situation Manager (B) || Probe ID . . . 531656lh + System B + Domain B + || Active Flag . . Y (Y/N) || || Status Item Name Comparator Value And/Or || K2_NYC_FIN_SERVER + STEQ + GREEN OR || SF_HR_SERVER + STEQ + GREEN OR || DEN_MIS_SERVER + STEQ + GREEN OR || STL_PG_SERVER + STEQ + GREEN OR || LA_RD_SERVER + STEQ + GREEN OR || ** Situation Row Displayed || F1=Help F4=Prompt F12=Cancel |+----------------------------------------------------------------------------+

4 Press Enter when you are finished.

Result: The OSM/MVS Assistant panel appears, and you are prompted to attach the situation you just created to a probe. (See “OSM/MVS Assistant” on page 197 for information on using that panel.)

Relationships Between Components



DependentsOSM/MVS maintains relationships between probes and the other components which are defined using the management panels. These relationships are dependent relationships because the component depends on a probe for data and/or proper execution. These dependencies vary according to the type of probe. For example, a data manager probe supplies data to a heartbeat or query probe, and a heartbeat or query probe changes the color of a status item. Therefore a data manager probe has a heartbeat or query probe as a dependent, and a heartbeat probe has a status item as a dependent.

data manager probe > heartbeat or query probe > status item

A different type of probe will not have the same dependents as a data manager probe. For example, a situation manager probe manages a number of situation definitions, each of which changes the color of a status item. Therefore a situation manager probe has a situation as a dependent, and a situation definition has a status item as a dependent.

situation manager probe > situation > status item

The following table summarizes the relationships between the different types of probes and their dependents.:

Probe Type Primary Dependents Secondary Dependents

A None -

D Heartbeat or Query probes Status Item

DG DP probes Status Item

DP Status Item -

E Status Item -

EM Status Item -

EO Status Item -

H Status Item -

M Heartbeat or Query probes Status Item

O Status Item -

Q Status Item -

QM Status Item -

S Situation Status Item

T Status Item -

X DAS Item Status Item

OSM/MVS Basics 63


Navigating to show dependentsThe OSM/MVS management panels provide a way to navigate from a probe to its dependent components without requiring you to pulldown a management panel. Management panels with this navigation feature list an action called Show Dependents which you can invoke by typing a > character to the left of a row and pressing Enter. When you select a row in this manner, OSM/MVS determines the type of component which has been selected, and navigates to the appropriate management panel, showing only those components which are related to the selected one.

Relationship to OMEGAVIEW


Relationship to OMEGAVIEW

IntroductionEach OSM/MVS system must have at least one OMEGAVIEW session defined in order to display the color of status items and to display the text information that is returned by probes.

Defining an OMEGAVIEW sessionOMEGAVIEW sessions are defined using the VTAM Definitions option from the Setup pulldown on the OSM/MVS Main panel. Each OSM/MVS system may have multiple OMEGAVIEW sessions defined. When multiple OMEGAVIEW sessions are defined for an OSM/MVS system, all sessions having the Activate Logon flag set to Y must specify the same VTAM application ID. When OSM/MVS is started under OG/MVS, each of these sessions will be established. OSM/MVS can then use any of these sessions to update a status item’s color or text information.

When you have defined multiple OMEGAVIEW sessions for an OSM/MVS system, you can change the VTAM application ID for a a given session only after setting the Activate Logon flag to N. In a single-session system, you can change the VTAM application ID without changing the Activate Logon flag.

Session changes become effective at the next OSM/MVS startup or by selecting the Activate action on the VTAM definitions panel.

OSM/MVS Basics 65

Notification

Notification

IntroductionOSM/MVS lets you notify specified users, called notification users, when the value of a status item changes. The user notified receives an incident message, which carries information about the status change. Incident messages can be sent to one or more persons at the same time, and can be directed to:

n a user terminal

n the system operator’s console

n a pager

Processing an incidentAny system user defined to OSM/MVS as a notification user can be notified of an incident. When notification occurs, the recipient may choose to deal with the problem either by taking corrective action or by escalating the incident. If the corrective actions are successful, he or she can record its resolution on OSM/MVS, which closes the incident and removes it from the system. If the user wishes to escalate the incident, he or she can send the incident message to the next user in a notification chain.

Examplen The following incident message is sent when the status item measuring

end-to-end response time on system B turns critical:Please Respond to B_00004 Probe: 031 - CICS_ETE_RESP_B End-to-end response time unsatisfactory.

n The following incident ID is sent to a pager for thesame incident:

B_00004

Notification


The table below shows the procedure for processing an incident. “Notification Operational Features” on page 225 describes incident processing in detail. As part of this processing activity, you may wish to look up information for the incident in the notification log. The figure below shows a sample notification log.

The notification logThe notification log maintains an audit trail of incident processing activity.

Step Action

1 Select one of the following from the Controls pull-down on the OSM/MVS main panel:n Receive Notification...n Resolve Incident...n Escalate Incident...Result: The notification processing panel is displayed..

2 Enter the system ID and incident number on the panel. Press Enter.

Result:

1. If you selected Receive Notification... escalation of the incident is stopped.

2. If you selected Resolve Incident... the incident is closed and removed from the system.

3. If you selected Escalate Incident... the incident message is sent to the next member of the notification chain.

Help------------------------------------------------------------------------ OSM/MVS - Receive Notification Input System and Incident Number to receive and press Enter. User ID . . . . . . ADMIN01System . . . . . . . ________ +Incident Number . . _____ F1=Help F4=Prompt F10=ActBar F12=Cancel

OSM/MVS Basics 67

Notification

Date/time stamped incidents are automatically written to the log defined as the system notification log (see the OG/MVS Configuration and Customization Guide). In addition, all user notification processing steps are written to the notification log.

Notification groups, rotation lists, and notification chainsNotification groups are created as part of the notification setup so that an incident message can be sent to additional persons if a notification user does not receive an incident within a predefined period of time. A notification group can contain pre-grouped sets of users, called rotation lists, as well as individual users.

A rotation list consists of notification users in which only one member is active at a time. The active user is the only one who can be notified of an incident.

Rotation lists let you assign multiple users to a notification group using a single reference. Rotation lists are particularly useful for sites that rotate system responsibility, because they simplify changing notification information each time a rotation occurs.

All the notification users and rotation lists in a notification group constitute a notification chain.

Escalating an incidentNotifying the next member of a group when an incident occurs is called escalating an incident. An incident can be escalated as a result of

n The expiration of the escalation time defined for a user in the group without the user receiving the incident. Note that by receiving an incident, a user prevents the incident from being escalated.

n An explicit escalation action taken by any system user. OSM/MVS determination to escalate based on an incident priority assigned to each status for a status item.

EDIT ---- STAF03.AMS.LOGN1B ---------------------------------- COLUMNS 001 072 COMMAND ===> SCROLL ===> HALF ****** ***************************** TOP OF DATA ****************************** 000001 AMS Log N;19940412,20:38:07.160492;AMS Log Started - DD(AMSLOGN) DSN(STA 000002 AMS Log N;19940412,20:38:07.160492;------------------------------------- 000003 AMSSTART;19940412,20:38:09.593637;AMS Notify Log started successfully 000004 KATRAU32;19940412,20:39:39.449506;-------------------------------------- 000005 KATRAU32;19940412,20:39:39.652499;Notify requested during initialization 000006 KATRAU32;19940412,20:39:39.868396;Notify text is: There is no B Response 000007 KATRAU32;19940412,20:39:42.525823;-------------------------------------- 000008 KATRAU32;19940412,20:39:42.689857;Notify requested during initialization 000009 KATRAU32;19940412,20:39:42.851284;Notify text is: Please Fix this proble 000010 050;19940412,20:39:43.184493;Probe 050 found ACTIVE_TASK_STAF03 status 000011 KATRAU32;19940412,20:39:56.847714;Non-Incident Notify for ACTIVE_TASK_OM 000012 KATRAU32;19940412,20:39:57.014311;---- Notify Text is: Please Fix this p 000013 050;19940412,20:39:58.626113;Probe 050 found ACTIVE_TASK_OMVTAMB status 000014 MVUPDATE;19940412,20:39:59.002155;STATUS ITEM: TSO_TD_USERS changed to: 000015 KATRAU32;19940412,20:41:27.896356;Non-Incident Notify for ACTIVE_TASK_TD 000016 KATRAU32;19940412,20:41:28.082149;---- Notify Text is: Please Fix this p 000017 050;19940412,20:41:29.773954;Probe 050 found ACTIVE_TASK_STAF03 status

Notification


Closing incidentsAn incident is closed when it is resolved or when the automatic resolve time, established for the system, has elapsed. In either case, a message is written to the notification log and the incident is removed from the system.

Setting up notificationChanges in status determine notification. You use the Setup pull-down, available through the OSM/MVS main panel, to define who is to be notified, when they are to be notified and how they are to be notified. Then you use the Status Manager, available through the OSM/MVS main panel Managers pull-down, to assign notifications to specific statuses (Critical, Warning, OK or None) for a status item.

The setup of OSM/MVS’s notification feature is described in depth in “Notification” on page 91. Below is a list of the main parts of that process.

n Create notification users, since incident messages are only sent to system users defined to OSM/MVS as notification users. (See “Setting Up Notification Users” on page 96.)

n Create rotation lists. Rotation lists are used to create a group of users in which one user at a time is active for inclusion in notification groups. (See “Rotation Lists” on page 107.)

n Create notification groups. The members of a notification group are used as the notification chain for escalating an incident. (See “Setting Up Notification Groups” on page 99.)

n Assign notification codes, notification text, notification priority and optionally, alternate notification processing programs to appropriate statuses (Critical, Warning, OK and None) for a status item. (See “Making Notification Assignments” on page 119.)

Other notification setup activitiesOther notification setup activities include the following:

n Using the Preferences pull-down to set or change default notification values that appear on entry panels as well as notification system parameters. (See “Notification Default Values and Preferences” on page 115 for more information on setting notification preferences.)

n Setting up the system notification log. (See the OG/MVS Configuration and Customization Guide for more information on notification logs and for a description of how to define a log.)

OSM/MVS Additional Capabilities 69

OSM/MVS Additional Capabilities

OverviewOSM/MVS incorporates a calendar feature that enhances the monitoring process. After defining calendars, users can assign probes to run for specific days and times.

In addition, OSM/MVS contains numerous features that can invoke actions when a status change occurs. Besides notifying users, these include directing messages to various types of display panels and executing REXX programs and various types of routines.

This chapter describes the following additional product capabilities:

Chapter ContentsDefining Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Invoking Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Directing Messages to OMEGAVIEW Special Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Function Description

Defining Calendars Create calendars with specific Daytypes to enhance the scheduling of probe activity.

Directing Recommendations

Upon a change in status, direct a recommendation to the operator console.

Logging Status Changes

Record status changes to one or more logs.

Initiating Action Routines

Execute a REXX program or automation routine upon a status change in a probe directive.

Directing Information to OMEGAVIEW Special Panels

Upon a change in status, direct messages to OMEGAVIEW worklist, exception, and notification screens.

4

Defining Calendars


Defining Calendars

IntroductionThis section explains how to set up calendars for probes. An OSM/MVS calendar is a set of definitions that assign specific attributes (called Daytypes) to the days of the year. You can then apply the calendar to a probe, providing much more control and flexibility of scheduling.

Because each OSM/MVS calendar can apply to many probes, you need to set up the calendars before you define the probes. To set up a calendar, you specify:

1. which days of the week are normally business days, and which days are normally off days2. what Daytypes (for example, holidays or payroll processing days) require probe

scheduling different from that provided by the normal distinction between business and off days

3. a priority order of Daytypes, to be applied when a day is classified as more than one type

Task 1: Plan the calendarsConsider whether you need to define more than one calendar. For example, if you have offices, data centers, or other facilities in more than one country, you probably need to define separate calendars for probes assigned to each facility.

Task 2: Define the calendarsTo define a calendar, follow this procedure.

Step Action

1 From the Setup pull-down on the OMV/MVS panel, select Calendar Definitions...

Result: The Calendars panel lists all defined calendars and allows you to create new calendars. The first time you use OSM/MVS there are no calendars in the list..

Actions Help ------------------------------------------------------------------------------ KATIACL0 OSM/MVS - Calendars ROW 1 TO 1 OF 1 Select rows and press Enter. Valid selections are: (A)dd, (B)rowse, (C)opy,(D)elete, (E)dit Calendar Days, and (M)odify. Name Description ******************************* BOTTOM OF DATA ************************ Command ===> _________________________________________________________________ -


Defining Calendars

You are now ready to specify day definitions and Daytypes for the new calendar.

Day DefinitionsA Day definition provides a way to identify a point in time or a collection of points in time. Each day definition has a Daytype name that is used to identify the day definition. The Daytype designates a category of days on which you want the same probes scheduled. For

2 To add a new calendar, select ADD from the Actions pull-down and press Enter.

Result: The Add Calendar panel appears. You can use this panel to define a new calendar based on an existing one.

The example calendar identifies Monday-Friday as business days, and Saturday and Sundays as off days. Business day and off day are two predefined default Daytypes that may be used for probe scheduling.

3 Enter the calendar name and description in the spaces provided.

Tip: The calendar name can be up to 12 characters long, and the first character cannot be a number. The description can be up to 45 characters long.

4 Select the appropriate business or off days for your data center.

Tip: An X indicates that a day of the week is a business day, and a blank indicates that a day of the week is an off day.

5 When you have finished entering your information, press Enter to save the new calendar definition.

Result: The Calendars panel reappears, with a message KATG011A - Add completed successfully.

--------------------------- Add Calendar ---------------------------- KATIACL1 OSM/MVS - Calendar Definition Calendar Name . . . . . . ___________ Calendar Description . . . This is example calendar definition -------------------------------------------------------------- Weekly Business Calendar Enter “X” for Business Days or blank for Off Days. Changes below will affect every Business Day Calculation. -------------------------------------------------------------- Weekday Name Daytype Name Business Day Monday . . . (MON) . . . . X Tuesday . . . (TUE) . . . . X Wednesday . . (WED) . . . . X Thursday. . . (THU) . . . . X Friday . . . (FRI) . . . . X Saturday. . . (SAT) . . . . _ Sunday . . . (SUN) . . . . _ KATG010Q - Row displayed and ready for modification.

Defining Calendars


example, you might assign a Daytype called HOLIDAY to several days on which probes run on the same holiday schedule.

OSM/MVS provides 9 predefined Daytypes, called default Daytypes: MON, TUE, WED, THU, FRI, SAT, SUN, BUS (business day), and OFF (off day). The default Daytypes are used in scheduling, but you cannot specify them in your calendar day definitions.

You can categorize the days of the year into as many Daytypes as you find useful for scheduling purposes. A single calendar date can be assigned more than one Daytype. For this reason, you will order the calendar days to resolve potential scheduling conflicts. Daytypes are useful only to indicate differences in probe scheduling. Because the default Daytypes cover all days of the year, you need to add your own Daytypes only for probe scheduling that differs from the normal weekly schedule for business and off days. You can then set up the schedule by Daytype for each probe.

Day calculation methodsYou can choose among 4 methods of calculating calendar days.:

Method Description Example

Specific day A single date June 30, 1995 (specified as 1995/06/30)

Day of month One or more days occurring a specified number of days after the beginning or before the end of all months selected

Sixth day before the end of every month except December

Weekday of month One or more specified monthly occurrences of one or more specified days of the week

First and third Fridays from the beginning of every month

Business day of month One or more days occurring a specified number of business days after the beginning or before the end of all months selected

Third business day before the end of every month


Defining Calendars

Task 3: Specify calendar daysTo specify calendar days, follow this procedure.

Step Action

1 To define calendar days based on the Candle-supplied examples, select the calendar you just defined, based on EXAMPLE.n Type E (for Edit) in the entry field to the left of the name of your calendar, and

press Enter.Result: The Calendar Day Definitions panel lists all days defined for that calendar, in rank order. The first time you access the Calendar Day Definitions panel, you will see four Candle-supplied examples of calendar days. Each example uses one of the four calculation methods.

Actions Help----------------------------------------------------------------------KATIACA0 OSM/MVS - Calendar Day Definitions ROW 2 FROM 162 Select a row and press Enter. Valid actions are: (A)dd, (C)opy,(D)elete and (M)odify. Calendar Name : ORDEREDLIST Order Day Name Daytype Meth Ovrd Description _ 1 BUSINESSDAY 3BUSDAY business day calculation _ 2 DAYOFMONTH 6DAYOFMO day of month calculation _ 3 WEEKDAY TUES4 weekday calculation _ 4 SPECIFICDAY XMAS specific day calculation ******************************* BOTTOM OF DATA *********************** Command ===>_________________________________________________________

Defining Calendars


2 Type C (for Copy) in the entry field to the left of the day you want to base your first day definition on, and press Enter.

Result: The Copy Day in Calendar panel shows the day definition you selected. Now you can change the definition as needed..

This example shows a named day definition using the Daytype 3BUSDAY. It is based on the business day calculation method.

3 Change the day name, description, and Daytype by typing over the existing text.

Tips:n The day name must be unique. It can be up to 12 characters long, and the first

character cannot be a number. The description can be up to 40 characters long. The Daytype can be up to 12 characters long.

n Calendar day name and description fields are provided for your convenience in creating and reading calendars, but are not used in scheduling resources. Only the Daytype, relative order, business/off override, and calculation method specifications affect resource scheduling.

n The default Daytypes are predefined and reserved. You cannot specify a default Daytype (MON-SUN, BUS, or OFF) in your day definitions. Use Daytypes that reflect the calculation method specifications. For example, the Daytype BUSDAY123 reflects the first 3 business days of the month.

n Many calendar days can share the same Daytype. Make sure your Daytypes are useful ones for your resource scheduling needs.

4 Assign a relative order number between 1 and 999, where 1 is the highest priority rank.

Tip: Relative order is used to resolve potential conflicts between business and off day specifications for an individual day. For example, if the first Monday of every month is defined as a business day and U.S. Labor Day (which occurs on the first Monday of September) has the override set to offday, we recommend you place LABORDAY below 1STMONDAY in the list. This will ensure that 1STMONDAY will retain its higher priority number so that it will not be affected by the override.

5 If you want the day definition in this example to remain a business day, do not enter a business/off day override.

Tip: For days calculated by any method other than business day of month, you can use the Override field to override the business/off day designation the day would normally have as determined by the rest of the calendar.

Step Action

------------------------- Copy Day in Calendar ------------------------- KATIACAE OSM/MVS - Calendar Day Definition Calendar Name . . . . : EXAMPLE Day Definition Name . . . . . . BUSINESSDAY Description . . . . . . . . . Example of a business day calculation Daytype . . . . . . . . . . . . 3BUSDAY + Relative Order . . . . . . . . 1 (1-999) Override . . . . . . . . . . . _ (B)usiness Day,(O)ff Day, or blank Calculation Method . . . . . . B + KATG010P - Row copied and ready for modification.


Defining Calendars

You are now ready to define probes and their schedules.

6 Select a calculation method by entering one of these codes:n B for business day of monthn W for week day of monthn D for day of monthn S for specific dayFor a description of each of these methods, see “Day calculation methods” on page 72.

Result: A calculation method entry panel appears.

In this example, the day is calculated as the third business day from the beginning of every month.

7 Change the day calculation specifications as needed.

Tip: Whether a given date is a business day or not is determined by:n the business day specifications for the calendar as a wholen the business day overrides for days in this calendar that rank higher than the day

now being defined

8 When you have finished, press Enter to save the day definition.

Result: The Calendar Day Definition panel reappears, with a message indicating that your day definition has been added successfully.

9 Continue to define calendar days until you have all the day definitions you need for your calendar.

Step Action

.------------------- Copy Day in Calendar --------------------. | KATIACA4 Business Day of Month Method Entry | | | | Tab to choice. Press Enter when finished. | | | | Count days from Beginning or End B (“B” or “E”) | | | | Days of the Month (“X”=Selected, Blank=Not Selected) | | 1st _ 2nd X 3rd _ 4th _ 5th _ 6th _ 7th _ | | 8th _ 9th _ 10th _ 11th _ 12th _ 13th _ 14th _ | | 15th _ 16th _ 17th _ 18th _ 19th _ 20th _ 21st _ | | 22nd _ 23rd _ 24th _ 25th _ 26th _ 27th _ 28th _ | | 29th _ 30th _ 31st _ | | | | Months of the Year (“X”=Selected, Blank=Not Selected) | | Jan X Feb X Mar X Apr X May X Jun X | | Jul X Aug X Sep X Oct X Nov X Dec X | | | | | ‘-------------------------------------------------------------’

Recommendations


Recommendations

IntroductionRecommendations are messages displayed at an operator console in response to a change in a status. A recommendation includes the probe ID, the monitored item that generated the message (for example, CICS region), and the current status value of the status item in addition to up to 3 lines of text.

A recommendation differs from a notification message sent to the system operator’s console. A recommendation is:

n never escalated

n not priority based

n not connected with any other OSM/MVS activity

For information on creating a recommendation and assigning it to a status, see “Creating a recommendation” on page 127.

Example

Remote RS6000 system is down.

Restart if possible.

If not, notify J. Jones or M. Garcia.


Logging

Logging

IntroductionOSM/MVS lets you create and maintain logs of status changes and notification data.

To log status changes, you decide which status items and associated conditions you want to log.

Notification logging is similar, except that you record notification messages sent in response to a status change.

The log fileLog files are defined during setup as described in the OG/MVS Configuration and Customization Guide.

OSM/MVS uses three datasets in a round robin fashion for each log defined. When one dataset becomes full, the second dataset for that log is used. When all three datasets for the log are full, the first is overwritten. A log code, a 1-character identifier, is used to specify a set of log datasets.

A notification log is defined in the same way as any other log file. However:

n The notification log is always assigned the log code N.

n There can be only one notification log per system.

Example

You have a status item called Payroll and want to record each time its status turns critical.

Example

Whenever Payroll turns critical, a notification message is sent to a rotation list of operations staff. You set up a notification log that records the time, message, and staff member notified.

Logging


Logging procedureYou log status changes as follows:

Step Action

1 Select Status Manager... from the Managers pull-down on the main panel.


2 Select the status item you want with one of the following action codes and press Enter (you need to repeat this step for each condition you want to log):

L Critical

O OK

N None

W Warning

Result: The Activity panel is displayed.

3 Select Diagnosis and Log Data with an S action code and press Enter.

Result: The Modify Diagnosis and Log Data panel appears.

4 Enter a log code in the Log Status Changes field. (If you do not know the log code, press the Prompt key for a list.) Press Enter.

Result: For the status item you selected, you have set up logging for the status you chose. Now, when the activity you selected occurs, an entry is written in the log.


Invoking Routines

Invoking Routines

IntroductionIn addition to notifying staff, directing messages to a console, and logging, you can link changes in status to invocation of the following types of routines:

n diagnostic

n action

n follow-up

Note that the routines themselves are user-written and not supplied with OSM/MVS.

Diagnostic routineFollowing is an example of a diagnostic routine..

Example

You have a routine called CICSDIAG that you want activated any time the status of CICS transaction rate changes to warning. The program works by gathering data on critical CICS resources (for example, storage violations) and writing the data to a file.

Invoking Routines


Enabling diagnostic routinesThe following is the general procedure for specifying and enabling a diagnostic routine:

Step Action

1 Select Status Manager... from the Managers pull-down.



L Critical

O OK

N None

W Warning

Result: The Modify Activity panel is displayed. +--------------------------- Modify Activity --------------------------+ | OSM/MVS - Activity | | | | S(elect) the Activities you wish to modify, and press Enter. | | | | Status Item CICS_TRAN_RESP_G Condition Critical | | Probe ID . : 030 System ID : G Domain ID : G | | ------------------------------------------------------------------- | | _ Diagnosis and Log Data | | _ Notification and Recommendation Data | | _ Action, Follow-up, and Log Data | | _ Work List Data | | _ Exception List Data | | | | F1=Help F12=Cancel | +----------------------------------------------------------------------+

3 Select Diagnosis and Log Data with an S action code and press Enter.

Result: The Modify Diagnosis and Log Data panel appears.+----------------- Modify Diagnosis and Log Data ------------------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || || Note: This section applies to all values for this Status Item. || ------------------------------------------------------------- || Status Item CICS_TRAN_RESP_G Condition Critical || Probe . . : 030 System ID. G Domain ID. G || ------------------------------------------------------------- || Log Status Changes . . . . _ + || Diagnosis Flag . . . . . . N || Diagnosis Routine . . . . . ________ || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+

4 Tab to the Diagnosis Flag field and type Y.


Invoking Routines

Invoking diagnostic routinesA diagnostic routine is invoked when:

diagnosis_flag = Yes AND status_color = red or yellow.

OSM/MVS supplies the following parameters to the routine, in the order listed.

Parameter Description

status_item Name of the status item.

status_color red, yellow, green, or turquoise.

attribute_value Value returned by the probe (YES, NO, 1, -1, 0, etc.)

Action routineAction routines perform a system action to resolve a problem or react to a set of conditions.

Invoking action routinesAn action routine is invoked if defined, and the status has changed.

OSM/MVS supplies the following parameters to the routine, in the order listed.

Parameter Description

probe_id A unique ID up to eight characters in length.

seq_num A unique, internal number identifying the status item to the action routine. It can be used to build a unique trap name associated with the status item.

status_item Name of the status item.

status_color red, yellow, green, or turquoise.

status_change Flag indicating that the status has changed.

update_log_panel Flag indicating that the OMEGAVIEW Worklist panel should be updated (Y or N).

attribute_value Value returned by the probe (YES, NO, 1, -1, 0, etc.)

log_text Character string to be written to the OSM/MVS Log.

5 Tab to the Diagnosis Routine field and enter the name of the program. Press Enter.

Result: For the status item and condition you selected, you have set up a diagnostic routine.

Example

You have a routine called RSTVTAM that you want activated any time a VTAM node goes down. The program works by issuing the VTAM vary active command.

Invoking Routines


Follow-up routineFollow-up routines run after a problem is detected. Their purpose is to obtain more information about a situation and determine whether the problem has been resolved.

Invoking follow-up routinesA follow-up routine is invoked if defined, and the status has changed.

No parameters are passed by OSM/MVS to the routine.

Enabling action and follow-up routinesOSM/MVS allows you to specify which programs you want linked to a specific status item and change in status. See “Specifying an Action Routine” on page 258 for an example.

The following is the general procedure for accessing and enabling action and follow-up routines:

Example

A follow-up routine called VTAMFLW determines whether the action routine RSTVTAM described above successfully activated the VTAM node that went down.

Step Action




L Critical

O OK

N None

W Warning

Result: The Modify Activity panel is displayed.

+--------------------------- Modify Activity --------------------------+ | OSM/MVS - Activity | | | | S(elect) the Activities you wish to modify, and press Enter. | | | | Status Item CICS_TRAN_RESP_G Condition Critical | | Probe ID . : 030 System ID : G Domain ID : G | | ------------------------------------------------------------------- | | _ Diagnosis and Log Data | | _ Notification and Recommendation Data | | _ Action, Follow-up, and Log Data | | _ Work List Data | | _ Exception List Data | | | | F1=Help F12=Cancel | +----------------------------------------------------------------------+


Invoking Routines

3 Select Action, Follow-up, and Log Data with an S action code and press Enter.

Result: The Modify Action, Follow-up, and Log Data panel appears.

4 Enter the name of the action or follow-up routine in its respective field. Press Enter.

Result: For the status item and condition you selected, you have set up an action or follow-up routine.

Directing Messages to OMEGAVIEW Special Panels



IntroductionYou can use OSM/MVS to write text to the following special OMEGAVIEW panels:

Worklist Maintains a list of problems, work assignments, and whether or not an individual or group was notified.

Exception Maintains a list of exception names, their status, and severity level.

Notification Maintains a list of incidents, the triggering status item, who received the incident, and whether it was resolved.

Panel customizationThese special OMEGAVIEW panels are shipped with OSM/MVS. Their format is predefined at installation time. If you want to modify the format, you must do so through OMEGAVIEW. See the OG/MVS Configuration and Customization Guide for details on importing the panels and theOMEGAVIEW User’s Guide for details on modifying the panels.

How the panels workYou enable the display of a status item on the worklist and exception panels through the Status Manager panel. After selecting a status item, you link its warning, critical, OK, or none status to display on one of those panels.

The notification panel lists a row of data each time a problem incident occurs that results in the notification of a user or group of users. You can use the panel to view the status of an incident or resolve it. This panel is covered in more detail in “Notification” on page 91.

Controlling panel updatingYou can specify that

n the panels are or are not updated

n if updated, how often the panels are refreshed

See “Setting Global Preferences” on page 192 for more information.

Before you beginIn order to view these panels, you need to be logged onto OMEGAVIEW. Make sure that version 300 of OMEGAVIEW is installed and that you have a valid OMEGAVIEW logon.



Worklist panelsUse OMEGAVIEW worklist panels to post messages about problems and the progress being made toward their resolution..

The following figure shows how an OMEGAVIEW worklist panel posts this information as problem 1:.

Enabling data for a worklistYou enable a status item change to display an OMEGAVIEW worklist panel as follows:

Example

When TSO response time reaches a critical value, the text

“TSO reponse time slow” is sent to OMEGAVIEW worklist panel 1.

Step Action



File Switch(W) Tools Samples Options Help------------------------------------------------------------ 10/30/96 10:05:53 OMEGAVIEW Version nnn OSM/MVS Work List 1 Problem Time Description Notify 01 12:09:44 TSO response time slow Y 02 14:20:02 CICSA abend N 03 16:32:00 NYC RS6000 disconnected Y 04 11:19:12 Paging rate problem Y 05 06 07 08 09 10 11 12 13 14 15 @----------------- @----------------- | > Work List 2 < | | > Work List 3 < | %-----------------‘ %-----------------‘ F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel



Exception panelsUse exception panels to display exception conditions detected by OSM/MVS on OMEGAVIEW.


L Critical

O OK

N None

W Warning


3 Select Worklist Data with an S action code and press Enter.

Result: If you select Work List Data, the following panel appears (example status item data supplied).

+--------------------- Modify Work List Data ----------------------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item MVS_TSO_USERS Condition WARNING || Probe . . : AA1000LH System ID. G Domain ID. G || ------------------------------------------------------------- || Work List Flag 1 N (Y/N) || Work List Flag 2 N (Y/N) || Work List Flag 3 N (Y/N) || Work List Action _ (A/D) || Work List Text . ____________________ || || F1=Help F12=Cancel |+------------------------------------------------------------------+

4 Enable the worklist panels you want by:n entering Y in any Work List Flag field. There are 3 worklist panels. Enter Y for the

ones to which you want to direct the status item data.n specifying in the Work List Action field whether you want each message to

– display in sequence (A)– overwrite the previous one (D)

n adding the worklist text you want displayed. This is placed in the Description column of the Work List panel.

5 Press Enter.

Result: You have directed OSM/MVS to send data to one or more OMEGAVIEW worklist panels upon a change in a status item value.



Sample exception panelThe following figure is an example of an OMEGAVIEW exception panel.

Exception panel procedureYou enable OMEGAVIEW exception panels as follows:

Step Action




L Critical

O OK

N None

W Warning


File Switch(W) Tools Samples Options Help------------------------------------------------------------ 10/30/96 10:15:58 OMEGAVIEW Version nnn OSM/MVS Exception List 1 Name Description Status CICS_00023 OSCOR stor viol Warning MVS_2234 Paging rate Warning CICS_09899 Trans rate exc Critical @----------------- @----------------- | > Exception 2 < | | > Exception 5 < | %-----------------‘ %-----------------‘ F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel



3 Select Exception List Data with an S action code and press Enter.

Result: The following panel appears (example status item data supplied).+---------------------- Exception List Data -----------------------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item MVS_TSO_USERS Condition WARNING || Probe . . : AA1000LH System ID. G Domain ID. G || ------------------------------------------------------------- || Exception Flag 1 . . . N (Y/N) || Exception Flag 2 . . . N (Y/N) || Exception Flag 3 . . . N (Y/N) || Exception Flag 4 . . . N (Y/N) || Exception Flag 5 . . . N (Y/N) || Exception Action . . . _ (A/D) || Exception Name . . . . ________ || Exception Description ____________ || Exception Status . . . ____________________ || || F1=Help F12=Cancel |+------------------------------------------------------------------+

4 Enable the exception list panels you want to send data by:n entering Y for any Exception Flag field. There are five exception panels. Enter Y for

the ones to which you want to direct the status item data.n specifying in the Exception Action field whether you want each message to

– display in sequence (A)– overwrite the previous one (D)

n describing:– The name of the exception you want sent. This can be any arbitrarily named text

you want written to the screen.– A description of the exception you want sent. This can be an elaboration or

explanation of the exception name.– Its status (for example, critical, warning, OK).

5 Press Enter.

Result: You have directed OSM/MVS to send data to one or more OMEGAVIEW exception panels upon a change in a status item value.

Section II: Setup 89

Section II: Setup

Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Distributed Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Functional Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145OSM/MVS Migration, Replication, and Distribution . . . . . . . . . . . . . . . . 159


Notification 91

Notification

OverviewThis chapter covers the setup procedures for OSM/MVS notification.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Setting Up Notification Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Setting Up Notification Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Rotation Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107OMEGAVIEW Notification Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Notification Default Values and Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Making Notification Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

5

Introduction


IntroductionThe OSM/MVS notification feature alerts one or more users with a notification message when the status of a managed object changes. OSM/MVS can display a notification:

n at the TSO session terminal where a user is logged on

n on a pager

n on the system operator’s console

Notification activity is reported in two ways:

n in a notification log

n on an OMEGAVIEW notification panel

About this chapterThis chapter covers the setup procedures for OSM/MVS notification. The table below lists

n the major notification setup tasks

n how to access each task

n common procedures used to implement each task

Task Description Access Through Procedures

User list Create list of users for inclusion in notification groups.

Setup pull-down, Users to Notify selection

n Add users (page 96)

n Delete users (page 98)

Notification groups Organize users into meaningful groups. Set up notification chain, notification levels, and incident handling.

Setup pull-down, Notification Groups selection

n Defining notification groups (page 100)

n Add notification levels (page 101)

n Add users to a notification group (page 104)

n Modify notification group data (page 105)

n Delete notification group data (page 105)

Notification 93

Introduction

Incident and non-incident notificationNotification processing is associated with a managed object’s status condition. For each status condition, you can:

n send a message and perform notification reporting

n send a message, perform notification reporting, and create an incident

How incident notification worksIf directed to do so, OSM/MVS will create an incident when the status of a managed object changes. OSM/MVS assigns the incident a number, starts tracking the incident, records the incident and the names of the persons notified, and displays notification information. If displayed at a TSO session terminal where a user has logged on or on the system operator’s console, the incident notification includes:

n an incident ID

n probe number

n status item name

n notification text

Rotation lists Create a subgroup of users in which only one is active at a time.

Setup pull-down, Rotation Lists selection

n Add rotation lists (page 109)

n Add rotation list members (page 110)

n Change the active user (page 111)

n Delete rotation list data (page 112)

Defaults and preferences

Set data entry defaults for panels, define notification systems to be used across enterprise.

Preferences pull-down, Notification Preferences selection

Complete Notification Preferences panel (page 115)

Link notification actions to status changes

Link a change in the status of a probe directive to a notification action. Set status condition change to create an incident, set priorities, and establish alternate notification program.

Managers pull-down, Status Manager selection

n Assign notification to a status (page 121)

n Modify the notification activity (page 121)

Task Description Access Through Procedures

Introduction


In the example,

n the incident is on system B and the incident ID is B_00004

n the probe ID is 031

n the status item name is CICS_ETE_RESP_B

n the notification text is End-to-end response on B poor.

If sent to a modem pager, the individual is beeped, and only the incident ID is displayed:

B_00004

Receiving and resolving incidentsWhen an incident message is sent, the notified user accesses

the incident through OSM/MVS or OMEGAVIEW. The user can

then:

n view the notification log for additional information

n either resolve the incident or escalate it

By receiving an incident, you prevent it from being escalated. A user who receives an incident is considered busy and is not notified again until the incident is resolved. However, if a status item change is detected with an overriding incident priority, even a busy user may be notified (see “Making Notification Assignments” on page 119).

If the notified user corrects the problem, they can resolve the incident through OSM/MVS. If the incident is not received and/or resolved within a pre-established period of time, OSM/MVS escalates the incident.

After a recipient responds to an incident, or the automatic resolution time established for the system elapses, the incident is closed.

“Notification Operational Features” on page 225 contains procedures for receiving, resolving, and escalating incidents.

Escalating incident messagesNotifying the next member of a group after an incident occurs is called

escalating an incident. An incident is escalated when:

n the escalation time expires without the previous user receiving the incident

n a group member, who has been notified, takes an explicit action to escalate the incident

n the incident priority assigned to a status requires escalation (described in “Making Notification Assignments” on page 119)

Example

Please Respond to B_00004 Probe: 031 CICS_ETE_RESP_B End to end response on B poor.

Notification 95

Introduction

Escalation continues until:

n a user receives the incident message

n OSM/MVS has tried to notify all the members of a notification group, and having been unsuccessful, has notified the system operator

n the automatic resolution time (described in “Notification Default Values and Preferences” on page 115) is reached

Notification without incident creationYou can use notification to alert users of a status condition change without creating an incident. In such cases, a notification message is sent and appropriate reporting is performed in the notification log. However, an incident number is not assigned, incident tracking is not initiated, escalation does not occur, and the message is not sent to OMEGAVIEW.

Additional notification capabilitiesOther notification capabilities, described elsewhere in this manual include using the

n controls pull-down to reset incident numbering and change notification setup on a running system (see “Notification Operational Features” on page 225)

n setup pull-down to define the notification log (see the OG/MVS Customization Guide)

Setting Up Notification Users



IntroductionThis section describes how to define notification users. Only notification users can receive, respond to and escalate incidents. To set up your notification lists, you specify:

n the users to notify when a status changes

n the notification method

(sending an incident notification to a user’s TSO session terminal or to the operator console, or sending an incident ID to a user’s pager)

Procedure for defining a notification userFollow these steps to define a notification user:

Step Action

1 Select Users to Notify... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Notify Users panel.

The panel lists the user IDs and names of all defined notification users sorted by user ID.

_ Actions Help --------------------------------------------------------------------------- OSM/MVS - Notify Users ROW 1 TO 11 OF 11 Select a row and press Enter. Valid actions are (A)dd, (M)odify and (D)elete. User ID User Name _ RDBF01 John Johnson _ RDBF02 Arnold Hauser _ STAF03 Dave Beck _ STAF04 Miles Skirmish _ STAF13 Janice Owens _ STAF14 Phil Wu _ STAF15 Charles Christian _ WFLM23 Yolanda Peters _ WFLM28 Fred Moog _ WFLM32 Bob Sanchez ******************************* BOTTOM OF DATA **************************** Command ===> ______________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Notification 97


2 To add a new user, with the cursor in the select column, type A and press Enter.

Result: OSM/MVS displays the Add User panel.+-------------------- Add User ---------------------+| OSM/MVS - Notify Users || || Fill in the information, then press Enter. || || User ID . . . . ________ || User Name . . . ______________________________ || Work Phone . . ____________________ || Home Phone . . ____________________ || Pager Phone . . ____________________ || Pager Type . . _ (M/T) || Pager Number . ____________________ || || || F1=Help F12=Cancel |+---------------------------------------------------+

3 Enter the user ID, which is the user ID of the person to be notified. This field is required. You can use up to 8 characters, and each ID must be unique.

4 Tab to the User Name field. This required field contains the name of the person to be notified. The name can be up to 30 characters in length.

5 If you want to use any or all of the optional Work Phone, Home Phone, and Pager Phone fields to effect notification by phone, tab to the field and type the telephone number.

Note: Telephone numbers can contain up to 20 characters including parentheses, hyphens, and commas. Parentheses and hyphens will be ignored. Commas are used to represent dialing pauses. The pause time will be determined by the dialing program.

6 Tab to the Pager Type field and type either M, for a modem pager, or T, for a beeper pager. Note that the modem pager displays the notification incident number, whereas the beeper pager just sounds a tone.

7 Tab to the Pager Number field and type the pager activation code, if a Pager Phone number has been supplied and if a code is necessary. The pager activation code must be numeric and can be up to 20 digits in length. The user’s pager code will be transmitted after connecting with the paging service.

8 Press Enter.

Result: OSM/MVS saves the data and redisplays the Notify Users panel. The new entry is placed in user ID sequence in the list.



Procedure for deleting a notification userTo delete a notification user:

Step Action

1 Select Users to Notify... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Notify Users panel.

2 Move the cursor in the select column to the appropriate row, type D and press Enter.

Result: OSM/MVS displays the Delete User panel.

3 Press Enter.

Result: OSM/MVS deletes the user data and redisplays the Notify Users panel.

Notification 99

Setting Up Notification Groups


IntroductionAfter you define your notification users, you organize them into groups to specify who will get notified when an incident occurs and who will get notified through escalation. OSM/MVS refers to such groupings as notification groups.

Escalation occurs within a notification group and not between groups. The sequence of members within a notification group determines who OSM/MVS notifies first and the correct escalation order. This sequence is called the notification chain. If a notification group’s identification code is specified on status activity records, the notification chain goes into effect when the status of a managed object changes.

n How the incident is escalated (by paging, through a message on a user’s TSO session terminal, or a message to the operator’s console) is determined by the notification type you define for each group member.

n When the escalation notification occurs is determined by the escalation time you supply for users and the notification priority you establish on status activity records. (See “Making Notification Assignments” on page 119.)

There is virtually no limit to the number of members you can include in a notification group or the number of groups you can define.

Notification levelsUsers in groups are further organized into notification levels. At least one notification level must be defined for each group. Notification levels allow you to subdivide notification groups to reflect your business organization. They are meaningful only as a reflection of that organization.

Creating notification groupsTo create a notification group you:

1. Define it.2. Add levels to the group.3. Add users to the levels within the group.



Defining notification groupsFollow these steps to define a notification group:

Step Action

1 Select Notification Groups... from the Setup pull-down on the OSM/MVS main panel.

Result: The Notification Groups panel is displayed.

The panel lists all defined notification groups in sequential order by notification code. Within each group, notification users and rotation lists are displayed in their notification sequence within notification levels. The panel also displays the escalation time, notification type, and Continue to Next User setting for each group member.

_ Actions View Help -------------------------------------------------------------------------- OSM/MVS - Notification Groups ROW 1 TO 21 OF 43 Select a row and press Enter. Valid actions are (M)odify, (D)elete, (A)dd Notification Code, Add Notification (L)evel, and Add Notification (U)ser. Code Level User Name ---------------------- ID --- Escalate Type Continue _ CICS CICS Notification Chain _ 1 CICS Customer Support _ Network Support Team @ROTNET 30 SEND _ John Johnson RDBF01 20 SEND _ 2 CICS Systems Programmers _ Yolanda Peters WFLM23 0 SEND Y _ Fred Moog WFLM28 20 WTO _ Dave Beck STAF03 20 SEND _ MVS Primary Support Team @ROTMVS 30 SEND _ DB2 DB2 Notification Chain _ 1 DB2 Customer Support _ John Johnson RDBF01 10 SEND _ 2 DB2 DBAs _ Dave Beck STAF03 20 SEND _ NS Network Services _ 1 Network Support _ Network Support Team @ROTNET 20 SEND _ Dave Beck STAF03 20 SEND _ John Johnson RDBF01 20 SEND _ 2 Network Management _ Arnold Hauser RDBF02 20 SEND Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Notification 101


Adding a new group notification levelAt least one notification level must be defined for a group. (Up to 999 levels can be defined within each group.) OSM/MVS automatically assigns sequential notification level numbers. For each notification level added to a notification group, you provide a level description. The level description contains 1-40 characters of text.

2 Move the cursor to the select column, type A and press Enter.

Result: The Add Notification Code panel is displayed.+------------------------- Add Notification Code -----------------+| OSM/MVS - Notification Codes || || Enter the required Notification Code and Description. || || Notification Code ____ || Description . . . ________________________________________ || || F1=Help F12=Cancel |+-----------------------------------------------------------------+

3 Enter a unique 1 to 4 character Notification Code that will be used to reference this group of users. Each notification group must be assigned a unique notification code. The notification code associates this group with a status on the Notification and Recommendation Data panel available through the Managers pull-down. (See “Making Notification Assignments” on page 119.)

4 Tab to the Description field and type the 1 to 40 character text description of the group.

5 Press Enter.

Result: OSM/MVS redisplays the Notification Groups panel. The new group entry is inserted in notification code sequence.

6 Repeat this process as desired to define more groups.



Follow this procedure for adding notification levels to a group.

Adding users and rotation listsNotification users can be assigned to notification groups as either:

n individuals

n members of rotation lists (see “Rotation Lists” on page 107.)

Notification users and rotation lists can be added to more than one notification group.

Escalation is performed in the sequence in which group members are listed in a notification group. The sequence is displayed in the Notification Groups panel. Levels have no meaning in the notification chain other than the sequence in which the members are listed. Thus, OSM/MVS notifies each member of Level 1 in sequence before notifying the first member of Level 2, and so forth.

Step Action

1 Define at least one notification level for each group. On the Notification Groups panel, type L on the appropriate panel row within the group at which the level is to be added. Press Enter.

Result: The Add Notification Level panel is displayed; the level number has been assigned by OSM/MVS.+-------------------------- Add Notification Level ----------------+| OSM/MVS - Notification Levels || || Enter the required Level Description. || || Notification Code CICS CICS Notification Chain || Notification Level 1 || Level Description ________________________________________ || || F1=Help F12=Cancel |+------------------------------------------------------------------+

Note: The cursor location is important; as OSM/MVS inserts the level at the current location. For example, if the cursor is in the select column in the row displayed for the group title (header), OSM/MVS inserts the new level as Level 1, renumbering all subsequent levels within the group.

2 Enter the 1-40 character text description for the level. Press Enter.

Result: The Notification Groups panel is displayed. The new level has been inserted within the notification group in notification level sequence. If the level has been inserted ahead of other levels in the group, OSM/MVS has renumbered the subsequent levels.

3 Repeat this process as desired to add additional levels to the group.

Notification 103


For each user or rotation list in a group, the following information is provided:

Notifying more than one group member at a timeTo send an incident report to several group members at the same time:

1. Locate them sequentially within the group.2. Assign them an Escalation Time of zero.3. Assign them a Continue code of Y.

Field Description

User ID/Rotation List For a notification user, the 1 to 8 character unique identification. For a rotation list, the unique rotation list name in the format @ROTxxxx., where @ROT are the first 4 characters.

Escalation Time A 1-4 digit number representing the number of minutes to wait after an attempt is made to notify the user until escalating the incident message to the next member of the group. This value must be set to zero if Continue to Next User is set to Y. Otherwise, a non-zero value must be specified.

The Escalation Time assigned to the last member of a notification group determines how long to wait before sending the incident notification to the system operator’s console.

Notification Type One of the following values:

BEEP Notify the group member by paging, displaying the incident ID (a system ID and incident number).

SEND Notify the group member by sending an incident notification (an incident ID, probe number, status item name, and notification text) to the user’s TSO session terminal. The notification text is created for each status for a monitored item using the Status Manager (see “Making Notification Assignments” on page 119).

WTO Notify the operator by sending an incident notification to the operator's console.

Continue to Next User Type Y to establish that this member of the group and the next member in the group are to be notified simultaneously. Otherwise, leave this field blank. If the Continue flag is set to Y, Escalation Time must be set to zero. The Continue flag cannot be set to Y for the last member of a group. You can continue notification from one level to the next within a group, but you cannot continue notification from one group to the next.



Adding a user to a notification groupFollow this procedure for adding a user to a notification group.

Modifying notification groupsYou can change:

n a notification group description, but not its name

n a group level description, but not its number

n the escalation time, notification type, or Continue to Next User setting for a group member

Note: To move a notification group member from one group to another, follow the procedures for deleting a member from a group and then adding a member to a group.

Step Action

1 On the Notification Groups panel, move the cursor to the select column, type U on the panel row below which the member is to be added, and press Enter.

Result: The Add Notification User panel is displayed.+---------------------------- Add Notification User -----------------------+| OSM/MVS - Notification Users || || Enter the required User ID ( or Rotation List Name ), Escalation Time, || Notification Type, and Continue Flag. || || Notification Code . : CICS CICS Notification Chain || Notification Level : 2 CICS Systems Programmers || User ID/Rotation List ________ + || Escalation Time . . . 20 (Minutes) || Notification Type . . SEND (BEEP, SEND, or WTO) || Continue to Next User _ (Y or Blank) || || || F1=Help F4=Prompt F12=Cancel |+--------------------------------------------------------------------------+

2 Either:n Enter a notification user ID or a rotation list name.n Use the Prompt key to display a list of all notification user IDs and rotation list names,

select the member from the list, and press Enter.

3 Tab to the Escalation Time field and change the number of minutes to wait before escalating to the next member of the group, if necessary. To notify the next member of the group at the same time, enter 0.

4 Tab to the Notification Type field and specify how the member will be notified.

5 Tab to the Continue to Next User field, if necessary. Type Y if Escalation Time has been set to zero. Otherwise, leave this field blank.

6 Press Enter.

Result: OSM/MVS saves the data and redisplays the Notification Groups panel with the new information on it.

Notification 105


Procedure for modifying notification group dataTo modify any notification group data, perform the following steps.

Procedure for deleting notification group dataYou can delete:

n a notification group and all its members

n a group level and all its members

n a notification user from a group

To delete notification group data perform the following steps.

Step Action



2 Move the cursor in the select column to the appropriate row, type M and press Enter.

Result: The appropriate Modify Entry panel is displayed, for example:+----------------------Modify Notification User Entry ------------------------+| OSM/MVS - Notification Users || || Modify the User ID (or Rotation List Name ), Escalation Time, Notification || Type, or Continue Flag. || || Notification Code . : CICS CICS Notification Chain || Notification Level : 2 CICS Systems Programmers || User ID/Rotation List STAF03 + Dave Beck || Escalation Time . . . 20 (Minutes) || Notification Type . . SEND (BEEP, SEND, or WTO) || Continue to Next User _ (Y or Blank) || || || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------------+

3 Change data as appropriate and press Enter to save the changes.

Result: OSM/MVS saves the changes and redisplays the Notification Groups panel.

Step Action




Result: A delete entry panel is displayed.



3 Press Enter.

Result: OSM/MVS deletes the data and redisplays the Notification Groups panel as follows.n If you enter D on a row containing a notification group name and description, the

notification group and all its members are deleted.n If you enter D on a row containing a group level name and description, the group

level and all its members are deleted, and OSM/MVS renumbers subsequent levels.n If you enter D on a row containing a notification user, the notification user is deleted

from the group.Note: You cannot delete a group if its notification code has been used on a status activity record. (See “Making Notification Assignments” on page 119.)

Notification 107

Rotation Lists

Rotation Lists

IntroductionA rotation list is a group of notification users where only one user is active at any given time. The active user is the only one in the rotation list who can be notified of an incident. Therefore, there is no escalation within a rotation list.

You use a rotation list as a single entry in a notification group.

n You can use the same rotation list as an entry in one or more notification groups.

n A rotation list member can belong to more than one rotation list.

Rotation lists are particularly useful for sites that rotate system responsibility. It simplifies modification of notification information each time a rotation occurs.

Creating rotation listsTo create a rotation list:

1. Define the rotation list by providing the following information on the Add Rotation List panel, which you can access through the Setup pull-down.

Example

A rotation list named @ROTCICS consists of 8 individuals responsible for CICS. When responsibility shifts (because of normal rotation, illness, vacation, and so forth) you modify the active user. This is the only change required. You do not need to change any of the notification group definitions.

Several notification groups may share responsibility for CICS-related status items. All such notification groups will have the CICS primary rotation list defined as the first member of the group.

Field Description

Rotation List Name Each rotation list is given a unique name. The name is formatted:

@ROTxxxx The rotation list name must begin with the characters @ROT, followed by up to 4 characters.

Description The 1 to 30 character text description of the rotation list.

Rotation Lists


2. Add notification users to the rotation list by providing the following information.

Field Description

User ID The 1 to 8 character unique user identification of a notification user.

Active Flag Type Y to specify that this user is to be notified of status changes. Otherwise, leave blank. Only one user in a rotation list can be active.

Notification 109

Rotation Lists

Procedure for adding rotation lists

Step Action

1 Select Rotation Lists... from the Setup pull-down on the OSM/MVS main panel.

Result: The Rotation Lists panel is displayed. The panel lists all rotation lists and, for each rotation list the notification users who are members of that list. The panel also identifies the active user in each rotation list..

2 To add a new rotation list, move the cursor to the select column, type A and press Enter.

Result: The Add Rotation List panel is displayed.+------------------ Add Rotation List -------------------+| OSM/MVS - Rotation Lists || || Enter the required Rotation List Name and Description. || || Rotation List Name @ROT || Description . . . ______________________________ || || F1=Help F12=Cancel |+--------------------------------------------------------+

_ Actions View Help -------------------------------------------------------------------------- OSM/MVS - Rotation Lists ROW 1 TO 19 OF 19 Select a row and press Enter. Valid actions are (S)elect a User ID to Activate, (M)odify, (D)elete, (A)dd Rotation List, and Add Rotation (U)ser. Name User Name ---------------------- ID --- Active _ @ROTBOO Network Group _ Dave Beck STAF03 _ Miles Skirmish STAF04 Y _ @ROTJIM CICS Rotation List _ Meg Washington CCSF01 Y _ Alan Cole CCSF03 _ @ROTMVS MVS Primary Support Team _ Yolanda Peters WFLM23 _ Fred Moog WFLM28 Y _ Bob Sanchez WFLM32 _ @ROTNET Network Support Team _ Dave Beck STAF03 Y _ @ROTPERF System Performance Team _ John Johnson RDBF01 Y _ Arnold Hauser RDBF02 _ @ROT1 Primary Rotation List _ John Johnson RDBF01 _ Arnold Hauser RDBF02 Y _ Yolanda Peters WFLM23 ******************************* BOTTOM OF DATA *************************** Command ===>_____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Rotation Lists


Procedure for adding rotation list membersFollow these steps to add members to a rotation list.

3 The required first 4 characters of the rotation list name (@ROT) are displayed. Enter up to 4 additional characters to create a unique rotation list name.

4 Tab to the Description field and type the 1 to 30 character text description for the rotation list.

5 Press Enter.

Result: OSM/MVS saves the new definition and redisplays the Rotation Lists panel. The new rotation list entry has been inserted in the rotation list name sequence.

6 Repeat this process as desired to add additional rotation lists.

Step Action


Result: The Rotation Lists panel is displayed..

_ Actions View Help -------------------------------------------------------------------------- OSM/MVS - Rotation Lists ROW 1 TO 19 OF 19 Select a row and press Enter. Valid actions are (S)elect a User ID to Activate, (M)odify, (D)elete, (A)dd Rotation List, and Add Rotation (U)ser. Name User Name ---------------------- ID --- Active _ @ROTBOO Network Group _ Dave Beck STAF03 _ Miles Skirmish STAF04 Y _ @ROTJIM CICS Rotation List _ Meg Washington CCSF01 Y _ Alan Cole CCSF03 _ @ROTMVS MVS Primary Support Team _ Yolanda Peters WFLM23 _ Fred Moog WFLM28 Y _ Bob Sanchez WFLM32 _ @ROTNET Network Support Team _ Dave Beck STAF03 Y _ @ROTPERF System Performance Team _ John Johnson RDBF01 Y _ Arnold Hauser RDBF02 _ @ROT1 Primary Rotation List _ John Johnson RDBF01 _ Arnold Hauser RDBF02 Y _ Yolanda Peters WFLM23 ******************************* BOTTOM OF DATA *************************** Command ===>_____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Notification 111

Rotation Lists

Procedure for changing the active userTo change the active user within a rotation list, either change the Active Flag on the Rotation Lists panel or change the Active Flag on the Modify Rotation User Entry panel.

Perform the following steps to change the active user on the Rotation Lists panel:

Perform the following steps to change the active user on the Modify Rotation User Entry panel:

2 Move the cursor to the select column, type U on the panel row below which the member is to be added, and press Enter.

Result: OSM/MVS displays the Add User ID to Rotation List panel.+------------------------ Add User ID to Rotation List ---------------------+| OSM/MVS - Rotation Lists || || Enter the required User ID, and optionally, the Active Flag. || || Rotation List Name : @ROTBOO Network Group || User ID . . . . . . . ________ + || Active Flag . . . . . _ (Y or Blank) || || || F1=Help F4=Prompt F12=Cancel |+---------------------------------------------------------------------------+

3 Do one of the following:n Enter the user ID of a notification user.n Use the Prompt key to display a list of all notification user IDs, select the new member

from the list, and press Enter.

4 If this user is to be the active user for the rotation list, tab to the Active Flag field and type Y. Press Enter.

Result: OSM/MVS saves the addition and redisplays the Rotation Lists panel with the new entry.

Step Action


Result: The Rotation Lists panel is displayed.

2 Move the cursor to the select column in the row containing the notification user who is to be active.

3 Type S and press Enter.

Result: Active status is reassigned to the selected user.

Step Action


Result: The Rotation Lists panel is displayed.

Rotation Lists


Deleting rotation list dataTo delete an entire rotation list or a member from a rotation list:

2 To change the active user on the Modify Rotation User Entry panel:

1. Move the cursor to the select column containing the entry for the notification user who is to be the active user, type M, and press Enter.

Result: OSM/MVS displays the Modify Rotation User Entry panel for the selected notification user.

2. Tab to the Active Flag field and type Y.

3. Press Enter.

Result: OSM/MVS redisplays the Rotation Lists panel with the selected user as the active user in the rotation list.

Step Action


Result: The Rotation Lists panel appears.


Result: The appropriate Delete Rotation List User ID panel appears.

3 Press Enter.

Result: OSM/MVS deletes the data and redisplays the Rotation Lists panel as follows:n If you type D on a row containing a rotation list name and description, the rotation list

and all its members are deleted.n If you type D on a row containing a notification user, the member is deleted from the

rotation list.

Notification 113

OMEGAVIEW Notification Panel


IntroductionThe OMEGAVIEW notification panel allows you the convenience of performing some notification tasks through OMEGAVIEW. The panel, which can be accessed after logging on to OMEGAVIEW, lists

n each problem incident

n the status item change that generated the incident

n the individual or group receiving the incident

n whether or not the incident was resolved

Sample OMEGAVIEW notification panelFollowing is an example of an OMEGAVIEW notification panel.

The status bars on the right side of the panel indicate whether or not an incident has been resolved. A yellow color indicates that it has not been resolved. A green color indicates that it is resolved.

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 06/14/97 14:13:20 OMEGAVIEW Version nnn OSM/MVS Notification Page 1 Incident ID/ Status Item Received by Status Notify Text B_00001 TSO_RESP_POOR TDRD99 ///////// _ Chicago Operations Center RT Poor -------------------------------------------- B_00031 PAYROLL_APPL T4MPD1 ///////// _ Payroll Application Abends --------------------------------------------------- B_00017 NCP_DALLAS T1A0V1 ///////// _ Dallas 3705 Down ------------------------------------------------------------- \\\\\\\\\ _ ----------------------------------------------------------------------------- \\\\\\\\\ _ @------------------› | > To Page 2 < | %------------------` F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel

///////// Green \\\\\\\\\ Red \\\\\\\\\ Black ///////// Yellow



Using the OMEGAVIEW notification panelIn addition to viewing the progress of problem incidents, you can use an OMEGAVIEW notification panel to resolve an incident.

To resolve an incident:

n Type C next to the status bar of the incident you want to resolve and press Enter.

Result: The Change Status popup appears. Change the status to OK to resolve the incident.

Notification 115

Notification Default Values and Preferences


IntroductionSetting notification defaults allows you to specify a value once and then have it appear automatically as the default value in entry panels. In addition to setting data entry default values, you can set enterprise-wide notification preferences for incident processing programs and systems.

Setting notification defaults and preferencesTo set notification defaults and preferences:

n Select Notification Defaults... from the Preferences pull-down.

Result: The Notification Preferences panel appears.

Notification Preferences panelThe Notification Preferences panel is divided into two areas, each of which contains related data entry fields.

Help ------------------------------------------------------------------------------- OSM/MVS - Notification Preferences Enter or modify Notification System Default settings. Press Enter to apply, or press Cancel to exit without saving changes. ---------------------------------------------------------------------------- Set Notification Default Values Alternate Notification Program ALTPGM1 Leave blank for OSM/MVS Notification Default Escalation Time . . . 20 (Minutes) Automatic Resolution Time . . 120 (Minutes, 0 for No Automatic Resolution) Default Incident Priority . . Notify If Available + Default Notification Type . . SEND (SEND or BEEP) Default Notification Text . . 012345678 Telephone pager ---------------------------------------------------------------------------- Set Preferred Notification Systems Primary Notification System . G + Secondary Notification System B + Command ===> _________________________________________________________ F1=Help F4=Prompt F12=Cancel



Alternate notification program defaultsWhen a status change results in an incident, OSM/MVS initiates notification processing. If an alternate program has been associated with a status value for a monitored item, that program -rather than the OSM/MVS procedure- will be used to process the incident.

To specify an alternate notification program as the default notification processing program, enter the 1 to 8 character program name in the Alternate Notification Program field. The value specified will appear as the name of the program to execute in the appropriate field of the Modify Notification and Recommendation Data panel whenever a new activity record is added (see “Making Notification Assignments” on page 119).

Note: We recommend that you leave the Alternate Notification Program field blank if you want OSM/MVS to perform all notification processing. You can set exceptions for specific activity records using the Alternate Notification Program field on the Modify Notification and Recommendation Data panel (see “Making Notification Assignments” on page 119).

Default escalation timeThe escalation time is the number of minutes, a 1 to 4 digit value, that may pass before incident notification is advanced to the next member of a notification chain. The escalation time value appears in the Escalate column on the Notification Groups panel. This value is assigned on the Add Notification User panel, where the default value appears.

Automatic resolution timeThe automatic resolution time is the number of minutes, a 1 to 4 digit value, an incident will remain active before it is automatically closed and removed from the system, and its automatic resolution is logged to the notification log and displayed on the OMEGAVIEW notification panel. When OSM/MVS is installed, this value is set to 120 minutes. You can establish a different preference by changing this value.

Area Data Fields Description

1 Notification default values

Establish general notification processing defaults.

2 Preferred notification systems

Identifies the MVS peer system OSM/MVS uses as the preferred system for notification processing and the alternate peer system to use if the Preferred system is not available.

Notification 117


Default incident priorityThe incident priority determines how notification is managed when a status change is detected. It specifies when to notify the user as follows:.

The value specified appears as the default Incident Priority field value on the Modify Notification and Recommendation Data panel whenever a new activity record is added (see “Making Notification Assignments” on page 119).

Either type in a value or, with the cursor in the field, press the Prompt key to list the four available priorities and select a value from the list of valid entries.

Default notification typeThe notification type specifies the preferred method for notifying a group member as follows:

Incident Priority Description

Always Notify Notify the user every time a status change is detected, even if the user is busy and has already been notified of the incident. Use this priority if you want the user notified of status changes that occur after the user has already been notified of a change in status to the same item.

Notify If Available Notify the next user on the notification chain only if the next user is not busy processing an open incident.

Notify Even If Busy Notify the next user on the notification chain even if the user is busy on a different status item.

Escalate Until Available Notify the next available user on the notification chain. If no users are available, display the following message on the operator’s console:

No response to incident number nnn.Escalation completed

Notification Type Description

BEEP Notify the group member by paging and displaying the incident ID (a system ID and incident number).

SEND Notify the group member by sending an incident notification (an incident ID, probe number, status item name, and notification text) to the user’s TSO session terminal. The notification text is created for each status for a monitored item with the Status Manager (see “Making Notification Assignments” on page 119).

WTO Notify the operator by sending the incident notification to the operator’s console.

The notification type value is displayed in the Type column on the Notification Groups panel. This value is assigned on the Add Notification User panel, where the default value appears.



Default notification textThe default notification text is for telephone pager display only. Specify a default numeric message (for example, the telephone number of your data center) to be used if the notification user’s pager does not support alphanumeric character display. Default notification text is used when notification is requested, the notification type is BEEP, the notification user’s pager type is T, and the pager supports digital display.

Preferred notification systemsIf peer-to-peer MVS systems are running at your site, use the Set Preferred Notification Systems fields to specify the MVS system you want notification processing to run on. OSM/MVS will always use this system if it is available. The alternate - or secondary - notification system specifies the peer MVS system notification processing is to use if the primary system is not available. If neither the primary nor secondary peer system is available, notification processing will be performed on any MVS system that is available.

Either type in the notification values or, with the cursor in either field, press the Prompt key to list the available systems and select a system from the list of valid entries. System names contain up to 8 characters.

Notification preferences procedureFollow these steps to complete the Notification Preferences panel.

Step Action

1 Select Notification Defaults... from the Preferences pull-down on the OSM/MVS main panel.

Result: The Notification Preferences panel is displayed.

2 To specify data entry default values or system preferences, move the cursor to the appropriate field and enter a value.

3 Press Enter.

Result: OSM/MVS saves the entered values.

Notification 119

Making Notification Assignments


IntroductionA key part of setting up OSM/MVS notification is linking a change in the status of a managed object to a notification activity. To do this:

n assign a notification code, which establishes whom to notify

n specify the notification text

n specify whether a status condition change should result in creation of an incident

n establish the notification priority, which determines the conditions under which a user can be notified

n specify the alternate notification program to use if OSM/MVS is not to process incidents

You use the Notification and Recommendation Data panel available through the Status Manager to make these assignments.

Notification codeThe 1 to 4 character notification code is the link between a status value and the person who will be notified. Notification codes are assigned to each notification group (See “Setting Up Notification Groups” on page 99). By specifying a notification code on the Modify Notification and Recommendation Data panel, you identify the user or users who are to be notified when the status of a monitored item changes.

Notification textThe 1 to 40 character notification text string is displayed on a TSO session terminal or the system operator's console as part of an incident notification. It is included in the incident report written to the notification log.

When the notification type is BEEP, the incident ID (the system ID and the incident number) is sent to the user if the user has a modem pager.

Incident creationYou can use notification to report status condition changes without creating an incident. If the Create Incident field is set to N (the default), when a status condition changes:

n the first person in a notification chain is notified

n an entry is made in the notification log

You can still notify multiple users by setting the Continue flag to Y for the users at the beginning of a notification chain. (See “Adding users and rotation lists” on page 102.)

No further notification processing occurs: the change is not assigned an incident number nor will any escalation processing occur.



Incident priorityThe incident priority determines how notification is managed when a status change is detected.

Alternate notification programWhen a status change generates an incident, OSM/MVS initiates notification processing. If an alternate program has been associated with the status, the alternate program, rather than the OSM/MVS procedure, will be used to process the incident.

You specify the 1 to 8 character name of the REXX program that is to be invoked to process notification instead of OSM/MVS.

Example

You can notify the data processing manager when the status for system throughput changes to Warning but not create an incident unless the throughput status condition changes to Critical.

Incident Priority Description

Always Notify Notify the user every time a status change is detected, even if the user is busy and has been notified of the incident. Use this priority if you want the user notified of status changes that occur after the user has already been notified of a change in status of the same item.

Notify If Available Notify the next user on the notification chain only if the next user is not busy processing an open incident.

Notify Even If Busy Notify the next user on the notification chain even if the user is busy on a different status item.

Escalate Until Available Notify the next available user on the notification chain. If no users are available, display the following message on the operator’s console, enter it into the notification log, and display it on the OMEGAVIEW notification panel:

No response to incident number nnn.Escalation completed

Example

CICS abending is considered a critical event. A user in the @ROTCICS rotation list, responsible for CICS, must know when this happens. Therefore, on the Modify Notification and Recommendation Data panel for the critical status of the CICS item, the Notification Code field must identify a notification group containing the @ROTCICS rotation list. An ALWAYS NOTIFY incident priority is assigned to the status to ensure that the CICS group will be notified immediately whenever CICS abends.

Notification 121


Note: Leave the Alternate Notification Program field blank if you want OSM/MVS to perform notification processing.

Procedure for assigning notification to a statusFollow these steps to assign notification to a status.

Step Action

1 Select Status Manager... from the Managers pull-down on the OSM/MVS main panel.


-------------------------------------------------------------------------- OSM/MVS - Status Manager ROW 1 TO 16 OF 75 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, (F)ind, (R)efresh, (M)odify Status Item, Modify Critica(l), (W)arning, (O)K, and (N)one Activities. Probe Status Item Name Description System Domain _ 028 AMS_OMEGAVIEW_B AMS Omegaview on System-B B B _ 011 AMS_STC_CSA_COUNT Monitor CSA Usage On SYSG G G _ 012 AMS_STC_CSA_ED Monitor CSA Usage On SYSG G G _ 550 ACTIVE_TASK_G OMEGAMON for MVS on Syste G G _ 050 ACTIVE_TASK_OMVTAMG OMEGAMON for MVS on Syste G G _ 030 ASC_WH_CICS_RT Response time for Elk Gro G G _ 031 CICS_ETE_RESP_B CICS End-to_end Resp.(B) B B _ 030 CICS_TRAN_RESP_G CICS Transaction Response G G _ 039 CICS_TRANS_RATE_B Transaction Rate for CICS B B _ 066 CPU.TDAFS02 CPU Utilization for AMS B B _ 006 CPU_B CPU Utilization. System B B _ 028 CTC_01 Channel-to-Channel Connec G G _ 008 DASD_POOL_RESP_B DASD Pool response - Syst B B _ C02 DB2_DSNDB01_DBD01 @C01ST00 DB=DSNDB01 TS=DB B B _ 073 E2E_TSO_NET_RESPONSE End to End TSO net respon G G _ 071 E2E_TSO_TRAN_RATES End to End TSO transactio G G Command ===>_____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



2 The last four action codes on the Status Manager panel allow you to select a status item and attach an activity to a change in its status. Select one of those action codes and press Enter.

L Critical

O OK

N None

W Warning

Result: OSM/MVS displays the Modify Activity panel for the selected status value.+--------------------------- Modify Activity ---------------------------+| OSM/MVS - Activity || || S(elect) the Activities you wish to modify, and press Enter. || || Status Item AMS_OMEGAVIEW_B Condition Critical || Probe ID . : 028 System ID : B Domain ID : B || ------------------------------------------------------------------ || _ Status Item Global Data || _ Notification and Recommendation Data || _ Action, Follow-up, and Log Data || _ Work List Data || _ Exception List Data || || || F1=Help F12=Cancel |+-----------------------------------------------------------------------+

3 Select Notification and Recommendation Data.

Result: The Modify Notify and Recommend Data Activity panel appears.

+---------- Modify Notification and Recommendation Data -----------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item AMS_OMEGAVIEW_B Condition Critical || Probe . . : 028 System ID. B Domain ID. B || ------------------------------------------------------------- || Notification Code ATD + || Notification Text Omegaview BMVY2SDM not available || Create Incident . Y (Y or N) || Incident Priority Always Notify + || Alternate Notification Program ALTPGM1 || ------------------------------------------------------------- || Recommendation Code . . . . . ____ + || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+

Notification 123


4 Enter data as follows:

1. You can eithern Enter a notification code representing the group that is to be notified when this status

changes.n Use the Prompt key to display a list of all notification codes. Select a notification code

from the list, and press Enter.2. Tab to the Notification Text field and type the 1 to 40 character text to be included

when an incident notification is displayed on a user’s TSO session terminal or the operator’s console.

3. Tab to the Create Incident field. Type Y if you want OSM/MVS to process this status condition as an incident.

4. Tab to the Incident Priority Notify if Available field. Change (if necessary) the notification priority by either:

n Typing in one of the four notification priorities.n Using the Prompt key to display a list of the notification priorities, selecting a

notification priority from the list and pressing Enter.5. If you intend to use an alternate notification program, tab to the Alternate

Notification Program field and type the name of the REXX program that will perform notification activities.

6. Press Enter.

Result: You have assigned a notification action to a status item.



Recommendations 125

Recommendations

OverviewThis chapter describes how to define and change recommendations, and how to associate recommendations with status values.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Assigning a Recommendation to a Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

6

Introduction


Introduction

DescriptionRecommendations are messages displayed at an operator console in response to a change in the status of a managed object. In addition to up to 3 lines of text, a recommendation includes the probe ID, the managed object that generated the message (for example, a CICS region), and the managed object’s current status value.

Recommendations are messages you create that tell the operator how to respond to a certain set of circumstances.

Recommendations and notification incident messagesRecommendations are set up in a similar manner to notification incident messages. Like notification messages, they are associated with a status value on the Status Manager panel.

However, recommendations differ from to notification messages, as they are:

n only sent to the system operator’s console

n not escalated

n not priority-based

n not connected with any other activity being performed

They simply provide a means of displaying a text message on the operator console each time a particular status change is detected.

Recommendations 127

Introduction

Creating a recommendationTo create a recommendation follow these steps:

Step Action

1 Select Recommendations... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Recommendations panel.

The panel lists all recommendations in ascending sequence by code number.

2 Move the cursor to the select column, type A and press Enter.

Result: OSM/MVS displays the Add Recommendations panel.+---------------------- Add Recommendations -------------------------+| OSM/MVS - Recommendations || || Enter the required Recommendation Code and any additional text. || || Recommendation Code ____ || Text Field 1 . . . _____________________________________________ || Text Field 2 . . . _____________________________________________ || Text Field 3 . . . _____________________________________________ || || F1=Help F12=Cancel |+--------------------------------------------------------------------+

_ Actions Help ---------------------------------------------------------------------- OSM/MVS - Recommendations ROW 1 TO 18 OF 25 Select a row and press Enter. Valid actions are A(dd), M(odify) and D(elete). -------------------Recommendations---------------------- Code Text _ 0000 This is the first recommendation This is the second _ 0001 Review Payroll Operation Menu Contact Application Programmer Restart Batch JOB when problem Resolved _ 0002 Re-Activate VTAM Node Contact Network System Programmer _ 0003 !!!!!!!!!!!!!!!!!! !!!!!! IPL !!!!! !!!!!!!!!!!!!!!!!! _ 0011 Response time has reached warning level Response time is between 1 and 5 Notify system administrator to hold large jobs _ 0123 Response time has reached warning level. Response time is between 1 and 4. Notify System Administrator to hold large jobs. Command ===> _________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Introduction


Modifying recommendation textYou can change recommendation text, but you cannot change

recommendation code numbers. To change recommendation text:

3 Enter a unique 1 to 4 character message ID (Code Number).

4 Tab to Text Field 1 and enter up to 50 characters of text as the first line of text. Repeat this procedure for Text Field 2 and Text Field 3, if desired.

+---------------------- Add Recommendations -------------------------+| OSM/MVS - Recommendations || || Enter the required Recommendation Code and any additional text. || || Recommendation Code 1001 || Text Field 1 . Response time has reached the warning level.______ || Text Field 2 . Response time is between 1 and 4._________________ || Text Field 3 . Notify system administrator to hold large jobs.___ || || F1=Help F12=Cancel |+--------------------------------------------------------------------+

5 Press Enter.

Result: OSM/MVS saves the message and redisplays the Recommendations panel. The new message has been inserted in code number sequence.

Repeat this process to add additional recommendations.

Step Action



2 Move the cursor to the left column of the row containing the message to be modified, type M and press Enter.

Result: OSM/MVS displays the Modify Recommendation panel.+---------------------- Modify Recommendation -----------------------+| OSM/MVS - Recommendations || || When you have finished making changes, press Enter. || || Recommendation Code 0000 || Text Field 1 . Response time has reached the warning level.______ || Text Field 2 . Response time is between 1 and 4._________________ || Text Field 3 . Notify system administrator to hold large jobs.___ || || F1=Help F12=Cancel |+--------------------------------------------------------------------+

3 Replace the text in Text Field 1, Text Field 2, and Text Field 3, as desired. Press Enter.

Result: OSM/MVS saves the changes and redisplays the Recommendations panel with the modified data.

Recommendations 129

Introduction

Deleting a recommendationTo delete a recommendation:

Step Action



2 Move the cursor in the left column to the appropriate row, type D and press Enter.

Result: OSM/MVS displays the Delete Recommendation panel containing the selected message.

3 Press Enter to confirm the deletion.

Result: OSM/MVS deletes the message and redisplays the Recommendations panel.

Assigning a Recommendation to a Status



IntroductionYou use the Notification and Recommendation Data panel, available through the Status Manager, to assign recommendations to specific status values (Critical, Warning, OK, and None) for a monitored item.

Recommendations 131


Assigning recommendationsUse the following procedure to assign a recommendation to a status:

Step Action

1 Select Status Manager... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Status Manager panel..

The panel lists OSM/MVS probes, status item names and descriptions, and their systems and domains.

Actions View Managers Help ---------------------------------------------------------------------- OSM/MVS - Status Manager ROW 1 FROM 296 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, F)ind, (R)efresh, (M)odify Status Item, Modify Critica(L), (W)arning, (O)K, and (N)one Activities. Probe Status Item Name Description System Domain _ 028 AMS_OMEGAVIEW_B AMS Omegaview on System-B B B _ 011 AMS_STC_CSA_COUNT Monitor CSA Usage On SYSG G G _ 550 ACTIVE_TASK_G OMEGAMON for MVS on Syste G G _ 050 ACTIVE_TASK_OMVTAMB OMEGAMON for MVS on Syste B B _ 030 ASC_WH_CICS_RT Response time for Elk Gro G G _ 031 CICS_ETE_RESP_G CICS End-to_end Resp.(B) G G _ 030 CICS_TRAN_RESP_G CICS Transaction Response G G _ 066 CPU.TDAFS02 CPU Utilization for AMS B B _ 006 CPU_B CPU Utilization. System B B _ 028 CTC_01 Channel-to-Channel Connec G G _ 008 DASD_POOL_RESP_G DASD Pool response - Syst G G _ C02 DB2_DSNDB06 @C01ST01 DB=DSNDB06 TS=* B B _ 072 E2E_TSO_RESP_TIMES End to End TSO Response T G G _ 071 E2E_TSO_TRAN_RATES End to End TSO transactio G G Command ===> ___________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



2 Move the cursor to the left column for the appropriate probe, type one of the following status codes and press Enter:

L Critical

O OK

N None

W Warning

Result: OSM/MVS displays the Modify Activity panel for the selected status value. For example:+--------------------------- Modify Activity ---------------------------+| OSM/MVS - Activity || || S(elect) the Activities you wish to modify, and press Enter. || || Status Item AMS_OMEGAVIEW_B Condition Critical || Probe ID . : 028 System ID : B Domain ID : B || ------------------------------------------------------------------ || _ Diagnosis and Log Data || _ Notification and Recommendation Data || _ Action, Follow-up, and Log Data || _ Work List Data || _ Exception List Data || || F1=Help F12=Cancel |+-----------------------------------------------------------------------+

3 Select Notification and Recommendation Data.

Result: OSM/MVS displays the Modify Notification and Recommendation Data Activity panel.+---------- Modify Notification and Recommendation Data -----------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item AMS_OMEGAVIEW_B Condition Critical || Probe . . : 028 System ID. B Domain ID. B || ------------------------------------------------------------- || Notification Code ATD + || Notification Text Omegaview BMVY2SDM not available || Create Incident . Y (Y or N) || Incident Priority Always Notify + || Alternate Notification Program ________ || ------------------------------------------------------------- || Recommendation Code . . . . . ____ + || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+

Recommendations 133


4 1. You can:

a. enter a recommendation code representing the message to be displayed on the operator’s console when the status changes

b. use the Prompt key to display a list of all recommendation codes. Select a code from the list and press Enter.

2. Press Enter.

Result: OSM/MVS redisplays the Recommendations panel.



Distributed Systems 135

Distributed Systems

OverviewThis chapter describes the hardware and software components of DAS, along with what you need to know to define, initialize, and execute the subsystem.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136DAS Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Using DAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

7

Introduction


Introduction

DescriptionOSM/MVS provides an optional distributed monitoring system, the Distributed Availability Subsystem (DAS), that lets you monitor distributed systems such as RS6000s, DECs, and TANDEMs, as well as Novell LANs. DAS runs on two platforms, mainframe and PC, enabling you to monitor the statuses of distributed systems and to report those statuses on OMEGAVIEW.

Installing DASYou may install DAS either when you install OSM/MVS or at a later time. Installation instructions are in the OMEGACENTER Gateway for MVS Configuration and Customization Guide.

For other informationFor step-by-step instructions on completing the OSM/MVS panels necessary to create and use a DAS probe, see “Setting Up Distributed Systems Monitoring” on page 287.


DAS Components

DAS Components

ConfigurationThe following figure illustrates a DAS configuration.

Elements of the configurationGoing from left to right in the diagram, the DAS system elements are:

n the distributed systems to be monitored–RS6000, DEC, and TANDEM in this example. (No special code is supplied or required for installation on the distributed system.)

n connections using RS232 serial ports, and modems if necessary, to the distributed systems

n a Novell LAN connected by a token ring or Ethernet

n software running on a PC, under OS/2™ version 2.1 or later and AF/REMOTE version 250 or later. The PC is configured as an alternate MVS console (address, cabling, and so forth), and it emulates a TTY (dumb) terminal to the distributed systems.

n a 3270 coaxial connection to the host

n software running on the host, under OG/MVS Version 340

n OMEGAVIEW Version 120 serving as a front end

LimitationThe number of distributed systems you can monitor is determined by:

n The capacity (slots, CPU speed, etc.) of the PC running AF/REMOTE.

n The number of probes running and their frequency of execution.

A configuration typically consists of 1 to 6 distributed systems and one LAN.

OS/2AF/REMOTEDAS

OG/MVSDASProbes

MVSconsole

OMEGAVIEW Panels

RS232

Novell LAN

RS6000

DEC

TANDEM

Token ringorEthernet

3270Coax

Mainframe

MVS

DAS Components


PC componentsThe following DAS components reside on the PC under the

control of AF/REMOTE:

n Programs that service requests from the host-based probes. These programs comprise several routines, which handle:

– Inbound communication from MVS by WTORs to the AF/REMOTE console.

– Outbound communication to the host by issuing EXECUTE commands on the AF/REMOTE console.

– Outbound communication to LANs and distributed systems by issuing the required commands to the device or system.

n Translate (X-Late) Routine. Distributed systems occasionally produce response data informats and quantities that cannot be returned to a probe on the host because the distributed system's response is too complex to be processed. OSM/MVS includes an X-Late routine that translates the data to a format that can be processed by a standard probe; custom routines may also be developed.

You can use the product-provided translation routine, KATXL001.REXX, as a model to build your own routines. KATXL001.REXX is located in the default DAS install directory, C:\KAT and parses information coming from distributed systems.

n Control parameter file. A control parameter file, \KAT\KATPARM.DAT, contains environmental definitions for each distributed system or LAN to be monitored, one record for each system. You define the contents of this file with an OS/2 REXX dialog that executes when you type in the following text and press Enter:

C:\KAT\KATPARMC.CMD

You are prompted to enter each parameter. The parameters are described in the following section.

When you have finished, the distributed domain is dynamically added to AF/REMOTE.

Control parameter fileThe following table describes the parameters that define your distributed systems or LANs.

Note: There are no defaults.

Parameter Description Value Range Required for LANs?

Distributed domain ID: identifier assigned to a distributed system or LAN.

2 alphanumeric characters Yes

ID number of the serial port to which the distributed system is connected. This is the COM#.

0 for a LAN; 1, 2, 3, or 4 for a distributed system. More if an Artic card is installed.

Yes

Baud rate used by this port to communicate with the distributed system.

300, 1200, 2400, 9600, 14400 or 28800

No


DAS Components

Number of data bits used by this port to communicate with the distributed system.

7 or 8 No

Number of stop bits used by this port to communicate with the distributed system.

1 or 2 No

Parity setting used by this port to communicate with the distributed system.

N, O, E, M, or S (for None, Odd, Even, Mark, or Space)

No

Maximum time in seconds that DAS should wait for a valid reply from the distributed system before executing the communication failure routine.

Range is same as allowed by REXX compiler.

No

Prompt characters used by the distributed system. Their appearance on the distributed system console indicates that it is ready to accept a logon.

Maximum line length displayable on the distributed system monitor (typically 72).

No

Logon ID to be used by DAS in establishing a session with the distributed system.


No

String that prompts DAS to enter the logon ID.


No

Password required by the distributed system when establishing a session using the logon ID.


No

String that prompts DAS to enter the password.


No

Text that prompts the user to scroll by pressing Enter if the number of logon messages exceeds a single-screen display.


No

Flag that instructs the system to use a dial-up modem connection to the distributed system. Parameter required if connection is by modem.

Y or N No

Telephone number of the distributed system. A comma (,) generates a 2-second delay. Parameter required if connection is via modem.

Valid dial string characters:

0–9 , () - /

No


DAS Components


Host componentsThe host components of DAS are the:

n Distributed Data Manager

The Distributed Data Manager performs the following four functions:

1. Starts DAS.

2. Sets up the TOD (Time-of-Day) traps identifying the probes that are activated and how frequently they execute, and describes the information that is to be captured and when.

3. Reports any problems from the distributed systems via WTORs.

4. Stops DAS.

n DAS Probe Manager

The DAS Probe Manager collects data gathered by the REXX programs running on the distributed platforms and passes it to the probes.

n Distributed Probe Manager

The Distributed Probe Manager, which resides on the host, interprets data collected by distributed probes on the OS/2 PC. It passes that data through to OMEGAVIEW for display.

Maximum time in milliseconds DAS should wait for a connection to be established with the distributed system before attempting to redial. A value of -1 means wait until connected. Parameter required if connection is by modem.

Maximum value recommended is 300000 (5 minutes).

No

Number of times DAS should hang up and redial before executing the communication failure routine. Parameter required if connection is by modem.

No inherent range No



Using DAS

Using DAS

IntroductionThis section describes what the OSM/MVS programmer must do to define DAS. It then explains what occurs during DAS initialization and execution.

Defining DASThe OSM/MVS programmer performs the following actions before starting AF/REMOTE and DAS. The process is described in detail in “Setting Up Distributed Systems Monitoring” on page 287.

OSM/MVS Programmer does... How...

Physically connects the distributed system to AF/REMOTE.

By RS232 serial ports and, if necessary, modems.

Defines the logon ID and password on the distributed system.

Sets the appropriate parameters.

Defines the distributed system environment: communication protocols and systems to be monitored.

Executes the dialog used to complete the control parameter file described in “Control parameter file” on page 138.

Defines the probes (see “Setting Up Distributed Systems Monitoring” on page 287).

Uses the Probe Manager to complete information on a probe.

Defines the managed objects that are to be monitored and the status items to be updated.

Uses the OSM/MVS Assistant or Status Manager to complete information on a status item.

For each status item to be returned, determines what activities should occur.

Completes the Activity Manager panel. Available activities are:n Log to a file.n Notify a person or group of people

(via pager or TSO SEND).n Send a recommendation to the MVS

console operator (WTOs).n Perform a predefined action routine.n Send information to an

OMEGAVIEW worklist or exception panel.

If necessary, constructs a distributed probe on the host.

Combines elements of the REXX models as required.

Schedules the traps and commands to be issued to DAS.

Completes the Distributed Systems Manager panel, one entry for each status item.

Using DAS


DAS initialization and execution processesThe following figures illustrate the DAS initialization and execution process.

Ensures that DAS will be started automatically when OG/MVS is started.

Modifies the Probe Manager dialogs and schedules the Distributed Data Manager.

OSM/MVS Programmer does... How...


Using DAS

.

Using DAS


Functional Security 145

Functional Security

OverviewThis chapter shows you how to set up security for OSM/MVS.

Note: Your RACF or CA-ACF2 administrator can provide you with the location of resources described in this chapter.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Using RACF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Using CA-ACF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149OSM/MVS Resource Definitions and Access levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

8

Introduction


Introduction

DescriptionFunctional security allows the security administrator to authorize access to OSM/MVS functions and resources for selected users only.

The security administrator can provide different capabilities to users based on:

n Department or area. For example, you can base authorization on whether the user uses MVS, works in the data center, or is a member of a particular network group.

n Task. For example, you can authorize an OSM/MVS administrator to define OSM/MVS entities (probes, status items, etc.), but limit an operator’s authority to starting, stopping, and refreshing those entities.

Note: This chapter documents the customization and setup process for RACF™ and CA-ACF2®.

For other security products, such as TOP/SECRET, you should consult the appropriate product documentation that describes how to use the SAF interface.

Requirements

System Authorization Facility (SAF)

OSM/MVS supports functional security through the System Authorization Facility (SAF). Your security product must support SAF.

Software Requirements

To use the functional security feature, you must have RACF Version 1.9.0 or higher, CA-ACF2 Version 6.1 or higher, or another security product that supports SAF and the ENTITYX keyword of the RACROUTE REQUEST=AUTH SAF function.


Using RACF

Using RACF

IntroductionIf you want to enable OSM/MVS functional security and your security product is RACF, follow the procedure below and refer to “OSM/MVS Resource Definitions and Access levels” on page 152 for more information.

Enabling OSM/MVS functional security with RACF

Step Action

1 Define a new entry in the Descriptor table by adding the following class definition to your Class Descriptor table:

ICHERCDE CLASS=$OGOSM,ID=nnn,MAXLNTH=39,FIRST=ANY,OTHER=ANY,POSIT=nnn,DFTUACC=NONE

Note: The class name must match the class name that you will specify in step 4. The default class name is $OGOSM.

2 Define a new entry in the Router table by adding the following to your Router table:

ICHRFRTB CLASS=$OGOSM,ACTION=RACF

Note: The class name must match the class name that you will specify in step 4. The default class name is $OGOSM.

3 Activate the newly defined class by issuing the appropriate SETROPTS commands. You must also activate the generic profile checking for the class.

Using RACF


4 (Optional)

Complete this step only if you want to change the default class name, specifying the same name used in steps 1 and 2.

1. Select Global Defaults... from the Preferences pull-down on the OSM/MVS main panel. OSM/MVS displays the Global Preferences panel.

2. Type the new name you selected in the Security class name field and press Enter.

Note: A special resource name protects this field. The verification to change this field is performed using the old class name. If you have not defined any resource profiles, OSM/MVS allows the change because the resource is still unprotected.

5 Use the Rdefine command to define general resources for the OSM/MVS functions you wish to protect. See “OSM/MVS Resource Definitions and Access levels” on page 152 for a list of OSM/MVS functions and resources you can protect.

For example, if you want to deny users access to the OSM/MVS User Interface, define a general resource profile as follows:

RDEFINE $OGOSM OSM.** UACC(NONE)Then add any users to the access list using:

PERMIT OSM.** CLASS($OGOSM) ID(USER01) ACCESS(READ)

Help----------------------------------------------------------------------- OSM/MVS - Global Preferences Enter or modify global default settings. Default OMEGAVIEW Text Type . . . . Transient Text +Peer Link Probe Frequency . . . . . 240 (Seconds)Peer Link Trap Prefix . . . . . . . @POSM/MVS Trap Prefix . . . . . . . . @TOSM/MVS DDNAME Prefix . . . . . . . @FLogon Retry Interval . . . . . . . 300 (Seconds)Logon Retry Count . . . . . . . . . 2Logon Wait Interval . . . . . . . . 15 (Seconds)OG/MVS Match Information . . . . . OFF (ON|OFF)Update Omegaview special panels . . YES (YES|NO)Special panel refresh interval . . 120 (Seconds)Security class name . . . . . . . . $OGOSMActual Status Display . . . . . . . N (Y|N) Command ===> __________________________________________________________ F1=Help F4=Prompt F12=Cancel


Using CA-ACF2

Using CA-ACF2

IntroductionIf you want to enable OSM/MVS functional security and your security product is CA-ACF2, follow the procedure “Enabling OSM/MVS functional security with CA-ACF2” on page 149 and refer to “OSM/MVS Resource Definitions and Access levels” on page 152 for more information.

Important: CA-ACF2 uses Mandatory Access Control. If you do not want to use functional security, you must create a SAFDEF record so that CA-ACF2 ignores the SAF calls that this feature performs. To bypass functional security, follow the procedure “Disabling OSM/MVS functional security with CA-ACF2” on page 149.

Disabling OSM/MVS functional security with CA-ACF2

Enabling OSM/MVS functional security with CA-ACF2Follow the procedure below to enable functional security.

Important: You can only use an ACF2 version that supports the ENTITYX keyword of the SAF RACROUTE REQUEST=AUTH function, meaning that Extended Resource Rules must be supported.

For more information about using SAF and defining general resources, see the CA-ACF2 Administrator Guide.

Step Action

1 Create a SAFDEF record as shown below:

set control(gso) CONTROL insert safdef.osm id($ogosm) mode(ignore) retcode(4)- racroute(request=auth,class=$ogosm) rep

Step Action

1 Create a SAFDEF record as shown below:

set control(gso) CONTROLinsert safdef.osm id($ogosm) jobname(-) mode(global)- racroute(request=auth,class=$ogosm) userid(-) rep

2 Create a CLASMAP record as shown below:

set control(gso) CONTROL insert clasmap.osm resource($ogosm) rsrctype(osm)- entityln(39)

Using CA-ACF2


3 (Optional)

Complete this step only if you want to change the default class name. Follow this procedure to change the class name in a SAFDEF record and in the User Interface to match the name you used in steps 1 and 2:

1. Create the following SAFDEF record to disable the default class name ($ogosm)

set control(gso) CONTROL insert safdef.osm id($ogosm) mode(ignore)- retcode(4) racroute(request=auth,class=$ogosm)- rep

Now, follow steps 2 and 3 to change the resource class name in the user interface.

2. Select Global Defaults from the Preferences pull-down on the OSM/MVS main panel.

3. From the Global Preferences panel, type the new name you selected in the Security class name field and press Enter..

4 Refresh the records and rebuild the directories by issuing

the following commands:

F ACF2,REFRESH(CLASMAP),SYSID(sysid),CLASS(C),TYPE(GSO)F ACF2,REFRESH(SAFDEF),SYSID(sysid),CLASS(C),TYPE(GSO)

Help----------------------------------------------------------------------- OSM/MVS - Global Preferences Enter or modify global default settings. Default OMEGAVIEW Text Type . . . . Transient Text +Peer Link Probe Frequency . . . . . 240 (Seconds)Peer Link Trap Prefix . . . . . . . @POSM/MVS Trap Prefix . . . . . . . . @TOSM/MVS DDNAME Prefix . . . . . . . @FLogon Retry Interval . . . . . . . 300 (Seconds)Logon Retry Count . . . . . . . . . 2Logon Wait Interval . . . . . . . . 15 (Seconds)OG/MVS Match Information . . . . . OFF (ON|OFF)Update Omegaview special panels . . YES (YES|NO)Special panel refresh interval . . 120 (Seconds)Security class name . . . . . . . . $OGOSMActual Status Display . . . . . . . N (Y|N) Command ===> __________________________________________________________ F1=Help F4=Prompt F12=Cancel


Using CA-ACF2

CA-ACF2 exampleThe example rule below shows how to add a resource rule for authorizing user OPER to activate Probe XYZ on OSM/MVS system SYSA:

set resource(osm)

RESOURCE

compile * store

$key(osm) type(osm)

sysa.probe.xyz uid(oper) service(update) allow

Note: SAF and CA-ACF2 use different authority levels. You must convert the SAF access level values listed in the table in “OSM/MVS resource definitions” on page 155 to ACF2 authority types and specify the ACF2 authority levels on the resource definition Service keyword.

Using the above example, look up the resource names for probes in “OSM/MVS resource definitions” on page 155. The access level for the Activate action is Update. Then, locate the access level in the list shown below and substitute the CA-ACF2 access level in the Service keyword. For the example, the SAF UPDATE level translates to UPDATE for CA-ACF2.

SAF CA-ACF2

ALTER ADDCONTROL DELETEUPDATE UPDATEREAD READ

5 Define the resource rules by creating the following:

set resource(OSM) RESOURCEcompile * store $key(osm) type(osm) uid(osmadmin) service(read) allow - uid(osmadmin) service(read,update,delete,add) allow

Note: You must also create appropriate rules for any personnel who will need to perform OSM/MVS functions. See “OSM/MVS resource definitions” on page 155 for details about OSM/MVS functions.

OSM/MVS Resource Definitions and Access levels



IntroductionThe functional security feature enables you to protect OSM/MVS resources by defining RACF or CA-ACF2 general resource profiles. A general resource name has been defined for each OSM/MVS resource that can be protected. A generic profile can cover one or more resource names.

Note: The term profile is used throughout this section. If you are a CA-ACF2 user, a profile is the same as a rule.

OSM/MVS resources can be protected by discrete or generic profiles. (See your Security product documentation for details on general, discrete, and generic resources.) A discrete profile name matches exactly one of the resource names as described in “OSM/MVS resource definitions” on page 155, while a generic profile name can match one or more resource names.

OSM/MVS resource naming conventionsAn OSM/MVS resource is an OSM/MVS data entity (probes and status items) or action for which you can limit access.

The naming convention of an OSM/MVS resource follows:

OSM.<osmsys>.<resource type>.<resource instance>

where

OSM/MVS resource typesThe following lists the resource types for which you can assign authorization:

OSM/MVS System-Specific Resource Types:

OSM/MVS

OSM System

OSM Uniquely identifies the resource names as belonging to OSM/MVS.

<osmsys> identifies the OSM/MVS system this resource belongs to. If the resource does not belong to a specific OSM/MVS system, then <osmsys> takes the value global. Do not use the reserved word global as an OSM/MVS system name. For example, Notification is a global resource not linked to an OSM/MVS system.

<resource type> is a reserved name that identifies the OSM/MVS resource type. A resource can be either a data item for an OSM/MVS action.

<resource instance>

identifies a specific resource of type <resource type> that belongs to an OSM/MVS system <osmsys>. An instance can have the value null, meaning that the instance of resource type cannot be separately protected. For example, you cannot protect a single message.



Incident

Message

Probe

Status Item

Situation

DAS Item

VTAM Session

Log

Global Resource Types:

OSM/MVS User Interface

User Notification List

Notification Group

Rotation List

Recommendation

Preferences

OSM/MVS access levelsThe types of access are organized hierarchically as follows:

1. Read 2. Update3. Control4. Alter

Access Levels Table

Operation Access Level

Browse/Inquire Read

Activate Update

Deactivate Update

Refresh Update

Edit/Modify Control

Add Alter

Delete Alter

Copy Alter



CA-ACF2 Access Levels Conversion Table

SAF and CA-ACF2 use different authority types. Use the table below to translate a SAF level to a CA-ACF2 level. For more information,see “Using CA-ACF2” on page 149.

ExamplesThis section describes some functional security usage examples.

Example 1

If you want to allow only one user, named XYZ, to start OSM/MVS system OSMA, follow these steps:

n For RACF:

1. Create a discrete general resource profile with the name OSM.OSMA.OSMSYS.START with a Universal Access (UACC) authority of NONE, as follows:

RDEFINE $OGOSM.OSM.OSMA.OSMSYS.START UACC(NONE)

2. Add userid XYZ to the access list of OSM.OSMA.OSMSYS.START with Update authority, as follows:

PERMIT OSM.OSMA.OSMSYS.START CLASS(OGOSM) ID(XYZ) ACCESS(UPDATE)

n For CA-ACF2:

1. Create a rule as follows:

set resource(osm)

RESOURCE

compile * store

$key(osm) type(osm)

OSMA.OSMSYS.START UID(XYZ)-

service(read,update) allow

Example 2

If you want user XYZ to be authorized to start all OSM/MVS systems, you can:

n create a discrete general resource profile for each of the systems you defined and add XYZ to each of the access lists, or

n create a generic general resource profile with the name OSM.*.OSMSYS.START and add XYZ to the access list

SAF CA-ACF2

ALTER ADD

CONTROL DELETE

UPDATE UPDATE

READ READ



– For RACF, create the following:

RDEFINE $OGOSM OSM.*.OSMSYS.START UACC(NONE)

PERMIT OSM.*.OSMSYS.START CLASS($OGOSM) ID(XYZ) ACCESS(UPDATE)

– For CA-ACF2, create the following:

set resource(osm)

RESOURCE

compile * store

$key(osm) type(osm)

OSM.*.OSMSYS.START UID(XYZ)-

service(read,update)-

allow

If an OSM/MVS resource is protected by more than one general resource profile, the most to least specific rule applies. This means that if more than one profile protects a resource, the most specific one is used to determine the authorization of the caller. For example, if user XYZ wants to start Probe @99 of OSM/MVS system OSMA and the following two generic resource profiles are defined:

OSM.OSMA.PROBE.** (user XYZ has UPDATE access)

OSM.OSMA.PROBE.@* (user XYZ has READ access)

then OSM.OSMA.PROBE.@* will be selected to protect this resource. Therefore, user XYZ is denied access to this function because you need at least UPDATE access to activate a probe.

In general, if a user needs the same type of access to all underlying resources, you should add him to the access list of the least specific profile with that type of access. If one of the underlying resources requires another type of access, create a specific profile for that resource only.

OSM/MVS resource definitionsThe following table lists the resource types, actions, access levels, and resource names used when defining resources.

Resource Type Action Access Resource Name

OSM SYSTEM StartStopRefreshOverview Probe BalancerModifyAdd/Copy/Delete

UpdateUpdateUpdateReadControlControlAlter

OSM.<osmsys>.OSMSYS.STARTOSM.<osmsys>.OSMSYS.STOPOSM.<osmsys>.OSMSYS.REFRESHOSM.<osmsys>.OSMSYSOSM.<osmsys>.OSMSYS.PROBEBALOSM.<osmsys>.OSMSYS



INCIDENT Receive notificationResolveEscalate Refresh notification

UpdateUpdateUpdateUpdate

OSM.<osmsys>.INCIDENT.RECEIVEOSM.<osmsys>.INCIDENT.RESOLVEOSM.<osmsys>.INCIDENT.ESCALATEOSM.<osmsys>.INCIDENT.NFYREFR

MESSAGE Overview InquireModifyAdd/Copy/DeleteRefresh

ReadReadControlAlterUpdate

OSM.GLOBAL.MESSAGE OSM.<osmsys>.MESSAGE

PROBE Overview Show dependentsFindActivate/InactivateRefreshModify/EditAdd/Copy/Delete

ReadReadReadUpdateUpdateControlAlter

OSM.GLOBAL.PROBEOSM.<osmsys>.PROBE.<prb>

STATUS ITEM Overview FindRefreshModifyAdd/Copy/DeleteCritical/Warning/Ok/None

ReadReadUpdateControlAlterControl

OSM.GLOBAL.STITEMOSM.<osmsys>.STITEM.<item>

SITUATION Overview Show dependentsRefreshModifyAdd/Copy/Delete

ReadReadUpdateControlAlter

OSM.GLOBAL.SITITEMOSM.<osmsys>.SITITEM.<item>

DAS DEFINITION Overview Activate/InactivateAdd/Copy/Delete

ReadUpdateAlter

OSM.GLOBAL.DASDEFOSM.<osmsys>.DASDEF.<item>

DAS ITEM Overview Show dependentsRefreshModifyAdd/Copy/Delete

ReadReadUpdateControlAlter

OSM.GLOBAL.DASITEMOSM.<osmsys>.DASITEM.<item>

VTAM SESSION Overview ModifyActivate/InactivateAdd/Copy/Delete

ReadControlUpdateAlter

OSM.GLOBAL.VTAMDEFOSM.<osmsys>.VTAMDEF.<session>

VTAM SESSION LOGON PARMS

All operations Alter OSM.<osmsys>.VTAMDEF.<session>.LOGON




LOG Overview BrowseModify

ReadReadControl

OSM.GLOBAL.LOGOSM.<osmsys>.LOG.<log>

USER INTERFACE Invoke Read OSM

USER NOTIFICATION LIST

Overview ModifyAdd/Delete

ReadControlAlter

OSM.GLOBAL.NFYUSER

ROTATION LIST Overview Activate UserModifyAdd User Add/Delete

ReadUpdateControlControlAlter

OSM.GLOBAL.ROTATIONOSM.GLOBAL.ROTATION.<rotlist>

NOTIFICATION GROUP

Overview ModifyAdd levelAdd User Add/Delete

ReadControlControlControlAlter

OSM.GLOBAL.NFYGROUPOSM.GLOBAL.NFYGROUP.<group>

RECOMMENDATION

Overview ModifyAdd/Delete

ReadControlAlter

OSM.GLOBAL.RECOMMENDOSM.GLOBAL.RECOMMEND.<code>

GLOBAL PREFERENCES

BrowseModify

ReadControl

OSM.GLOBAL.PREFERENCES.GLOBAL

GLOBAL PREFERENCES SECURITY CLASS

Modify Control OSM.GLOBAL.PREFERENCES.GLOBAL.CLASS

NOTIFICATION PREFERENCES

BrowseModify

ReadControl

OSM.GLOBAL.PREFERENCES.NOTIFY

FILE PREFERENCES

BrowseModify

ReadControl

OSM.GLOBAL.PREFERENCES.FILE




OSM/MVS Migration, Replication, and Distribution 159

OSM/MVS Migration, Replication, and Distribution

OverviewThis chapter describes the activities you perform to migrate entities from one OSM/MVS system to another. It also describes how to replicate an OSM/MVS image and distribute the replicated image to one or more target MVS systems.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Replication and Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Replicating OSM/MVS Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Distributing OSM/MVS Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Displaying Replication and Distribution Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

9

Introduction


Introduction

DescriptionUsing OSM/MVS migration, you can copy or move probes, status items, DAS items, and situations from one OSM/MVS system to another in a single step. OSM/MVS migration is particularly useful for copying or moving these entities from a test or development system to a production system. Migration is often performed to populate an MVS image that is to be replicated and distributed.

Using OSM/MVS replication, you can share MVS images in a non-shared DASD environment. OSM/MVS replication creates a copy of the RKANISP table and the user interface startup EXEC for an MVS image and makes it available for distribution to one or more other OSM/MVS environments.

Note: Only the environment table hilev.RKANISP and the user interface startup datasets can be distributed using OSM/MVS distribution. Use your standard site procedures for distributing other OSM datasets needed in the target MVS environment.

The lowest level of distribution is the OSM/MVS system. You cannot use OSM/MVS replication to distribute individual probes, status items, DAS items, or situations.


Migration

Migration

IntroductionYou may wish to copy or move probes, status items, DAS items and situations defined in one OSM/MVS environment to another environment. For example, you may wish to use the probes and status items defined in your development or test system in your production system -- often with no change.

Migration allows you to:

n copy or move these entities from one system to another within a single OSM/MVS environment

n copy or move all probe, status item, DAS items, and situation definitions in a single step

Migration


Procedure for migrating entitiesUse the following procedure to migrate probes, status items, DAS items, and situations from one OSM/MVS system to another:

Step Action

1 Select System Environments... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the System Environments panel.

Actions Help -------------------------------------------------------------------------- OSM/MVS - System Environments ROW 1 TO 11 OF 11 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify (D)elete and the action series Mi(G)rate T(O). For DAS systems additional actions are Ac(T)ivate and (I)nactivate. Local Focal Sel System Sys. ID SYSNAME System Description _ G2 LINKID4G SYSG N Norman Lew System G2 _ G1 LINKID4G SYSG Norman Lew System G1 _ GO1PSD1 SYSGO1PS SYSG AR for notification testing _ GO1PS SYSGO1PS SYSG Y Candle Development System-G _ L3 SYSG3 SYSG Candle LAN _ SYSG3 SYSG3 SYSG N Another toolkit for System-G _ G SYSGO999 SYSG N Candle Development System-G _ R2 SYSGO999 SYSG Unix System (II) _ R3 SYSBO122 SYSB Unix System (III) _ L1 SYSGO999 SYSG Candle LAN _ R1 SYSGO999 SYSG Unix System ******************************* BOTTOM OF DATA ****************************

Command ===> __________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel


Migration

2 Move the cursor to the select column and type G next to the source system. Then, move the cursor to the select (Sel) column and type O next to the target system. In the following example, "GO1PS" is selected as the source system and "G" is selected as the target system.

Actions Help -------------------------------------------------------------------------- OSM/MVS - System Environments ROW 1 TO 11 OF 11 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify (D)elete and the action series Mi(G)rate T(O). For DAS systems additional actions are Ac(T)ivate and (I)nactivate. Local Focal Sel System Sys. ID SYSNAME System Description _ G2 LINKID4G SYSG N Norman Lew System G2 _ G1 LINKID4G SYSG Norman Lew System G1 _ GO1PSD1 SYSGO1PS SYSG AR for notification testing g GO1PS SYSGO1PS SYSG Y Candle Development System-G _ L3 SYSG3 SYSG Candle LAN _ SYSG3 SYSG3 SYSG N Another toolkit for System-G o G SYSGO999 SYSG N Candle Development System-G _ R2 SYSGO999 SYSG Unix System (II) _ R3 SYSBO122 SYSB Unix System (III) _ L1 SYSGO999 SYSG Candle LAN _ R1 SYSGO999 SYSG Unix System ******************************* BOTTOM OF DATA ************************** Command ===> __________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel

Migration


3 Either:n press Entern select Actions on the action bar to display the Actions pull-down, and select

Replicate...Result: OSM/MVS displays the Status Item Replication panel.

Actions Help + ---------------------------------------------------------------------- | OSM/MVS - Status item Replication | | | S | Status item names must be unique across all OSM systems because they | ( | share one Omegaview. Specify below how the Status items names of | F | system GO1PS should be modified for system G. | | | | Press PF1 for a detailed explanation of the operation of the fields | S | | _ | Old string . . ____________________ Position . 1 (1-20) | _ | New string . . ____________________ Position . 0 (0-20) | _ | | g | Apply to S(ource) or T(arget) system . . S (S or T) | _ | | _ | | o | Command ===> _______________________________________________________ _ | F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar | _ + -------------------------------------------------------------------- +

L1 SYSGO999 SYSG Candle LAN _ R1 SYSGO999 SYSG Unix System ******************************* BOTTOM OF DATA *************************** Command ===>_____________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel


Migration

4 Use the Status item Replication panel to assign unique names to the status items on the source and target systems. You can replace names on the source system as well as assign names to the target system.

Provide the entity strings and press Enter. (See“Status item replication fields” on page 167.)

Result: OSM/MVS performs the requested status item operation. Probes or situations with the same name will be changed as well.

In the following example, when the migration copy or replace operation is performed, status items, probes, and situations that start with the characters "ps" will start, instead, with the characters "lh".

Actions Help - +----------------------------------------------------------------------+ | OSM/MVS - Status item Replication | | | S | Status item names must be unique across all OSM systems because they | ( | share one Omegaview. Specify below how the Status items names of | F | system GO1PS should be modified for system G. | | | | Press PF1 for a detailed explanation of the operation of the fields | S | | _ | Old string . . ps__________________ Position . 1 (1-20) | _ | New string . . lh__________________ Position . 0 (0-20) | _ | | g | Apply to S(ource) or T(arget) system . . S (S or T) | _ | | _ | | o | Command ===> ________________________________________________________| _ | F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar | +----------------------------------------------------------------------+ _ L1 SYSGO999 SYSG Candle LAN _ R1 SYSGO999 SYSG Unix System ******************************* BOTTOM OF DATA**************************** Command ===> _____________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel

Migration


5 The scrollable portion of the panel shows processing and diagnostic messages generated during the migration process. In this example, the three messages identify probes that have been replaced. Similar messages will identify situations and DAS items that are replaced. Press F3 to remove the Status item Replication display.

Actions Help +---------------------------------------------------------------------+ | OSM/MVS - Status item Replication ROW 1 TO 3 OF 40 | | | S | Status item names must be unique across all OSM systems because the | ( | share one Omegaview. Specify below how the Status items names of | F | system GO1PS should be modified for system G. | | | | Press PF1 for a detailed explanation of the operation of the fields | S | | _ | Old string . : PS Position : 1 (1-20) | _ | New string . : LH Position : 0 (0-20) | _ | | g | Apply to S(ource) or T(arget) system . : T (S or T) | _ | | _ | Entity Message | o | AEM00001 PROBE HAS BEEN REPLACED ON G | _ | KP000001 PROBE HAS BEEN REPLACED ON G | _ | QMPS0001 PROBE HAS BEEN REPLACED ON G | _ | | _ | Command ===> ______________________________________________________ | * | F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar | +---------------------------------------------------------------------+ +---------------------------------------------------------------------+ |Warning messages have been issued - see scrollable display for details +---------------------------------------------------------------------+ Command ===> _________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel


Migration

Status item replication fieldsUse these field definitions as a guide when creating or modifying status item strings.

6 To see the copied or replaced entities, select Status Manager... from the Managers pull-down on the OSM/MVS main panel action bar. Use the F7 and F8 keys to browse the Status Manager panel scrollable list.

Field Description

Old string The characters to look for in the status item name. If old string is not specified, new string is applied unconditionally. If both old string and new string are specified, new string is applied only if old string is found.

Position The starting position of old string in the status item name.

Actions View Managers Help-------------------------------------------------------------------------- OSM/MVS - Status Manager ROW 102 FROM 273 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, (F)ind, (R)efresh, (M)odify Status Item, Modify Critica(L), (W)arning, (O)K, and (N)one Activities. -------------------------------------------------------------------------- Probe Status Item Name Description System Domain _ P22 LH_BMAX DB2 BMAX exception G G _ P21 LH_BMTH bmth probe G G _ P24 LH_DSND DB2 DSND exception G G _ P23 LH_DVCV DB2 DRCV exception G G _ P24 LH_EDMU DB2 EDMU exception G G _ P24 LH_IDBK DB2 IDBK exception G G _ P24 LH_IDFR DB2 IDFR exception G G _ P82 LH_NOVELL_LAN1 test G G _ P20 LH_PRBRAU36_XUSA Test of loc comp combinat G G _ QMPS0001 LH_QM_STATUS1 Test of QM probe G G _ PS5 LH_STC number of stc’s G G _ DP000001 LH_TEST_DP_1 test dp probe G G _ AEM00001 LH_TEST_EM_1 test em status item G G _ PS4 LH_TSO tso users G G _ PS1 LH_WTOR outstanding replies G G _ PS1 LH_WTOR_OMVTAMA outstanding replies G G _ PS1 LH_WTOR_OMVTAMG outstanding replies G G _ PS2 LH_XCSA csa usage G G Command ===> ____________________________________________________________ F1=Help F1=Exit F7=Backward F8=Forward F10=ActBar

Migration


New string Text to be used as the replacement string. If old string is not specified, new string is applied unconditionally. If both old string and new string are specified, new string is applied only if old string is found. If new string is longer than old string, existing characters are shifted right at the insertion point. Truncation occurs if the length of the status item name exceeds 20 characters.

Position The position at which new string is to be inserted in the status item name. 0 means insert the new string at the position at which old string is found. Truncation occurs if insertion causes the length of the status item name to exceed 20 characters.

Apply to S(ource) or T(arget) system

Status item name changes can be applied to the source (S) or target (T) system. Specify S to apply the new status item names to the source system. The target system will then use the original status item names. Specify T to apply the new status item names to the target system. The source system status item names will not be changed.


Replication and Distribution


IntroductionUsing replication, you can distribute an OSM/MVS environment to one or more MVS images in a non-shared DASD environment.

Note: There is no need to use replication/distribution in a shared DASD environment, since all MVS systems share the same OSM/MVS environment.

To use OSM/MVS replication effectively, you must install, customize, build and maintain all your OSM/MVS systems in one, central OSM/MVS environment. From this central environment, you:

1. Replicate OSM/MVS to a new, local set of OSM/MVS datasets. You can copy all or selected probes, status items, DAS items, and situations as part of the replication.

2. Distribute the replicated OSM/MVS environment to one or more target MVS images.To create a replicated MVS image, you:

n identify the replication model

n create the replication definition

n initiate the replication process. OSM/MVS replication creates a copy of the model table and startup datasets.

n modify the replication datasets

n distribute the replicated OSM/MVS system to the target MVS images. This step can be performed immediately after completing the replication process or at a later time.



Setting up the replication modelFollow these steps to identify the MVS image to use as the replication model:

Step Action

1 Select File Defaults... from the Preferences pull-down o the OSM/MVS main panel.

Result: OSM/MVS displays the File Preferences panel.

Note: Values for the first four parameters on the File Preferences panel are initially set during OSM/MVS customization as described in the OG/MVS Configuration and Customization Guide. You may want to update these settings. See “Setting File Preferences” on page 195 for a description of these fields and how to update them.

Help -------------------------------------------------------------------------- OSM/MVS - File Preferences Enter or Modify OSM/MVS File Preferences. OSM/MVS REXX Library . . . . . REXXDD (DD) OSM/MVS REXX Dataset Name . . TDSM.AT999PRB.ISPFILE (DSN) OSM/MVS Main Panel Display . . TDOG.OG999CUM.RKANISP (DSN) Main Panel Display Member . . KATKAM03 (Member) Table Model dsname . . . . (DSN) OSM startup dsname . . . . (DSN) OSM startup member . . . . (Member) Command ===>_____________________________________________________________ F1=Help F12=Cancel



Model fieldsUse these field definitions as a guide when creating the model definition.

2 Provide values for the Table Model dsname, OSM startup dsname, and the OSM startup member parameters and press Enter. For example:

Result: OSM/MVS saves the model definition and displays the main panel.

Field Description

Table Model dsname The name of the dataset to be used as the allocation model and as the source for new table data sets. Usually, the low level qualifer is RKANISP.

OSM startup dsname The name of the dataset that contains the REXX EXEC to be used to start the OSM user interface.

OSM startup member The name of the OSM user interface REXX EXEC in the start up data set. As shipped, the member name is OGAT.

Help ---------------------------------------------------------------------- OSM/MVS - File Preferences Enter or Modify OSM/MVS File Preferences. OSM/MVS REXX Library . . . . . REXXDD (DD) OSM/MVS REXX Dataset Name . . TDSM.AT999PRB.ISPFILE (DSN) OSM/MVS Main Panel Display . . TDOG.OG999CUM.RKANISP (DSN) Main Panel Display Member . . KATKAM03 (Member) Table Model dsname . . . . TDSM.DOC.ISPTLIB (DSN) OSM startup dsname . . . . CANDLE.USER.CLIST (DSN) OSM startup member . . . . OGAT (Member) Command ===> _________________________________________________________ F1=Help F12=Cancel



Creating the replication definitionFollow these steps to provide the information necessary to use an MVS image as a replication target system:

Step Action

1 Select Replication Definitions... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Target Systems panel.

Actions Help -------------------------------------------------------------------------- OSM/MVS Target Systems ROW 1 FROM 2 (B)rowse, M(odify), A(dd), D(elete), C(opy) or (S)elect a Target MVS Image and Press ENTER MVS Image mask . . . * Local HLQ Target HLQ Sel Sel MVS Image (first 15 ch.) (first 15 ch.) Destination Stat _ GO2PS PSEDM.GO2PS PSEDM.GO2PS SYSG _ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG ************************** BOTTOM OF DATA ******************************* Command ===> ___________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



2 Either:n move the cursor to the select column, type A and press Enter, orn delect Actions on the action bar to display the Actions pull-down, and select AddResult: OSM/MVS displays the Replication Definition panel.

Actions Help +-------------------------------------------------------------------+ | OSM/MVS - Replication Definition | 2 | | ( | Substitute values and press ENTER to save | T | | | MVS Image id . . . . . . . . . . ________ | | Destination . . . . . . . . . . _______________ | M | Local replication DS HLQ . . . . _______________________________ | | Target replication DS HLQ . . . _______________________________ | | User file transfer EXEC . . . . ________ | S | | A | Last Modified . : By : | _ | F1=Help F4=Prompt F12=Cancel | * +-------------------------------------------------------------------+** Command ===> ___________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Replication definition fieldsUse these field definitions as a guide when creating or modifying replication definitions.

3 Complete the replication definition (see “Replication definition fields” on page 174) and press Enter.

Result: OSM/MVS displays a confirmation message like the following for the table data set. (A similar confirmation message is displayed for the startup data set.)

4 Press Enter to create the datasets. Repeat Steps 2 through 4 to define additional target MVS images as appropriate. Use the Modify command to change existing replication definitions, and the Delete command to remove them.

Field Description

MVS Image id The unique name of an MVS image to which you will distribute an OSM/MVS

Destination The destination name. The value you specify depends on the file mechanism you will use to transfer the target datasets. Specify:n the JES2 Network Job Entry Node name if you will use TSO/E

Transmit/Receiven the server LUNAME or group name if you will use IBM

Netview File Transfern the destination code as appropriate for another FTP product

Actions Help- +--------------------------------------------------------------+-------- | OSM/MVS - Create Table Data Set Confirmation |W 1 FROM 2 | |( | A Table data set for target MVS image ’MAINT1’ was |T | not found. | | Press ENTER to create it or press PF3 to cancel. | | |M | If you cancel the Table data set creation you must | | allocate it yourself and restart the Replication Definition | | process. | elS | F1=Help F12=Cancel | tatA +--------------------------------------------------------------+_ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG*************************** BOTTOM OF DATA ******************************* Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Local replication DS HLQ

The high level qualifier for the datasets in the central OSM/MVS environment. These datasets are created locally by the replication process and used as input to the distribution process. The qualifier must be unique: you cannot use the same local HLQ for different target MVS images.

Target replication DS HLQ

The high level qualifier for the OSM/MVS datasets in the target environment. Used for documentation purposes only if the TSO/E Transfer/Receive file transfer mechanism is used.

User file transfer EXEC The name of a user-created REXX EXEC that will perform the data transfer to the target MVS image. The EXEC can invoke the customer’s file transfer mechanism directly from within TSO or submit a batch job. (See“Distributing OSM/MVS Environments” on page 184.)

Replicating OSM/MVS Environments



IntroductionOnce the model datasets are identified, the target MVS images are defined and the replication definition has been created, you are ready to direct OSM/MVS to perform the replication. To initiate replication, you:

1. Select the source OSM/MVS systems that are to be replicated.2. Select the target MVS images to which the source systems are copied.3. Change MVS image-dependent information in the OSM tables for the selected target

MVS images.

The replication processNote: Only the Table and Startup datasets can be replicated and distributed. All other datasets are distributed according to your installation distribution procedures.

Replication creates a new image.RKANISP and image.STARTUP member for each selected target MVS image.

For each target image, OSM/MVS:

n copies all the common tables (e.g., system, session, exception, and pattern tables) from the centrally managed OSM/MVS environment to the target MVS image table dataset identified as part of replication definition

n extracts information from the selected OSM/MVS systems in the centrally managed OSM/MVS environment and writes the data to the target MVS image rhilev.RKANISP table dataset. If the selected OSM/MVS system is already present in the target table library, the system table is updated.

n displays panels and accepts input to allow you to change preference and log information in the target table. (See “Changing Target Image Table information” on page 179.)

n copies the local target OSM/MVS startup member, modifying the image and assigning the dataset the high level qualifier specified for the target image dataset in the replication definition

n initiates distribution processing. You can perform this processing as part of replication or later, as described below



Selecting OSM/MVS source and target systemsUse the following procedure to identify the OSM/MVS system(s) to be replicated and then the target MVS images:

Step Action

1 Select Replication... from the Controls pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the OSM System Replication panel.

2 Select one or more OSM/MVS systems for replication by typing S in the Sel column for the OSM System entry. Press Enter.

Repeat this step, as desired.

Result: The letter Y is displayed in the Sel Status column, indicating the system has been selected as a replication source system.

OSM/MVS OSM System Replication Actions Help ---------------------------------------------------------------------- OSM/MVS OSM System Replication ROW 1 FROM 11 (S)elect one or more OSM systems and press ENTER. Press PF3 to process the selections. OSM system mask . . * Sel Sel OSM System Description Status _ G2 Norman Lew System G2 _ G1 Norman Lew System G1 _ GO1PSD1 AR for notification testing _ GO1PS Candle Development System-G _ L3 Candle LAN _ SYSG3 Another toolkit for System-G _ G Candle Development System-G _ R2 Unix System (II) _ R3 Unix System (III) _ L1 Candle LAN _ R1 Unix System ************************** BOTTOM OF DATA ******************************* Command ===> ___________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



3 Press F3 when all source systems are selected.

Result: OSM/MVS replicates the model common tables, building or updating the target MVS image rhilev.RKANISP table dataset, and displays the Target Systems Replication panel.

4 Select the target replication system or systems by typing S in the Sel column for the OSM System. Press Enter.

Repeat this step, as desired.

Result: The letter Y is displayed in the Sel Status column, indicating the system has been selected as a replication source system.

5 Press F3 when all replication target systems are selected.

Result: OSM/MVS displays the preference screens for the replication target system(s).

Actions Help------------------------------------------------------------------------- OSM/MVS Target Systems Replication ROW 1 FROM 3 (S)elect a Target MVS Image for Replication and Press ENTER. Press F3 to complete selection. MVS Image mask . . . * Local HLQ Target HLQ Sel Sel MVS Image (first 15 ch.) (first 15 ch.) Destination Stat _ GO2PS PSEDM.GO2PS PSEDM.GO2PS SYSG _ MAINT1 TDSM.DOC.ISPTLI TDSM.DOC CACOWLAA _ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG ************************** BOTTOM OF DATA ******************************* Command ===> ____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Changing Target Image Table informationNext, OSM/MVS displays the Global, Notification, and File Preferences and the Log Environment panels so you can adjust preferences in the target environment(s).

Step Action

1 OSM/MVS displays the Global Preferences panel. Either:n press F3 to make no changesn change global defaults for the target image(s), as appropriate, and press Enter. (See

“Setting Global Preferences” on page 192 for more information.)

Help----------------------------------------------------------------------- OSM/MVS - Global Preferences Enter or modify global default settings. Default OMEGAVIEW Text Type . . . . Transient Text +Peer Link Probe Frequency . . . . . 300 (Seconds)Peer Link Trap Prefix . . . . . . . @POSM/MVS Trap Prefix . . . . . . . . @OOSM/MVS DDNAME Prefix . . . . . . . @DLogon Retry Interval . . . . . . . 600 (Seconds)Logon Retry Count . . . . . . . . . 0Logon Wait Interval . . . . . . . . 0 (Seconds)OG/MVS Match Information . . . . . ON (ON|OFF)Update Omegaview special panels . . NO (YES|NO)Special panel refresh interval . . 360 (Seconds)Security class name . . . . . . . . $OGOSMActual Status Display . . . . . . . N (Y|N)+------------------------------------------------------------------------+|Processing MAINT1 - You are updating the Preferences for Target MVS Image||MAINT1. Make desired changes and press ENTER to accept, PF3 to cancel |+------------------------------------------------------------------------+ Command ===> ____________________________________________________________ F1=Help F4=Prompt F12=Cancel



2 OSM/MVS displays the Notification Preferences panel. Either:n press F3 to make no changesn change the notification defaults for the target image(s), as appropriate, and press

Enter. (See “Notification Default Values and Preferences” on page 115 for more information.)

Help-------------------------------------------------------------------------- OSM/MVS - Notification Preferences Enter or modify Notification System Default settings. Press Enter to apply, or press Cancel to exit without saving changes. -------------------------------------------------------------------------- Set Notification Default Values Alternate Notification Program _____ Leave blank for OSM/MVS Notification Default Escalation Time . . . 90 (Minutes) Automatic Resolution Time . . 180(Minutes, 0 for No Automatic Resolution) Default Incident Priority . . Escalate Until Available + Default Notification Type . . SEND (SEND, BEEP, or WTO) Default Notification Text . . 123 Telephone pager -------------------------------------------------------------------------- Set Preferred Notification Systems Primary Notification System . G + Secondary Notification System B + +------------------------------------------------------------------------+|Processing MAINT1 - You are updating the Preferences for Target MVS Image||MAINT1. Make desired changes and press ENTER to accept, PF3 to cancel |+------------------------------------------------------------------------+ Command ===> ____________________________________________________________ F1=Help F4=Prompt F12=Cancel



3 OSM/MVS displays the File Preferences panel. Either:n press F3 to make no changesn change file defaults for the target image(s), as appropriate, and press Enter. (See

“Notification Default Values and Preferences” on page 115 for more information.)

Help-------------------------------------------------------------------------- OSM/MVS - File Preferences Enter or Modify OSM/MVS File Preferences. OSM/MVS REXX Library . . . . . REXXDD (DD) OSM/MVS REXX Dataset Name . . TDSM.AT999PRB.ISPFILE (DSN) OSM/MVS Main Panel Display . . TDOG.OG999CUM.RKANISP (DSN) Main Panel Display Member . . KATKAM03 (Member) Table Model dsname . . . . TDSM.DOC.ISPTLIB (DSN) OSM startup dsname . . . . CANDLE.USER.CLIST (DSN) OSM startup member . . . . OGAT (Member) +------------------------------------------------------------------------+|Processing MAINT1 - You are updating the Preferences for Target MVS Image||MAINT1.Make desired changes and press ENTER to accept, PF3 to cancel |+------------------------------------------------------------------------+ Command ===> _____________________________________________________________ F1=Help F12=Cancel



4 OSM/MVS displays the Log Environments panel. Either:n press F3 to make no changesn change log environment settings on this panel, as appropriate and press F3Result: OSM/MVS saves the modified data and populates the startup datasets.

Actions Help -------------------------------------------------------------------------- OSM/MVS - Log Environments ROW 1 TO 2 OF 2 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify (D)elete, and (B)rowse log datasets. ----------------------------------Log----------------------------------- System Code Output DD Name DS Name MaxRec _ G A S 10 _ G N D OSMLOGN TDSM.AT999PRB.TDAFS01.RKATLG01 10 TDSM.AT999PRB.TDAFS01.RKATLG02 TDSM.AT999PRB.TDAFS01.RKATLG03 ****************************** BOTTOM OF DATA **************************** +------------------------------------------------------------------------+| Processing MAINT1 - You are updating the Log Definitions for Target MVS|| Image MAINT1. Add Logs or make modifications as desired, press PF3 to || continue |+------------------------------------------------------------------------+ Command ===>_____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



5 OSM/MVS displays the Target Systems Distribution panel.

You can:n initiate distribution now by pressing F3n postpone distribution until a later time. (See step 6.)The next section of this chapter describes the distribution process.

6 To postpone distribution, perform the following steps.

1. Locate each selected MVS image on the OSM/MVS Target System Distribution panel. (A Y is displayed in the Sel Stat column if the MVS image is selected.)

2. Deselect every selected image by typing S in the Sel column for each selected image.

3. Press Enter.

Actions Help -------------------------------------------------------------------------- OSM/MVS Target Systems Distribution ROW 1 FROM 3 (S)elect a Target MVS Image for Distribution and Press ENTER. Press F3 to complete selection. MVS Image mask . . . * Local HLQ Target HLQ Sel Sel MVS Image (first 15 ch.) (first 15 ch.) Destination Stat _ GO2PS PSEDM.GO2PS PSEDM.GO2PS SYSG _ MAINT1 TDSM.DOC.ISPTLI TDSM.DOC CACOWLAA Y _ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG *************************** BOTTOM OF DATA ******************************* +--------------------------------------------------------------------+ | Replication was successful, to Distribute select Target MVS images | +--------------------------------------------------------------------+ Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Distributing OSM/MVS Environments



IntroductionDistribution of the replicated environnment table and startup datasets is initiated either:

n as the next step in the replication process

n as a later separate step by selecting Distribution... on the Controls pull-down

Transmitting datasets using TSO/E TransmitBy default, the distribution process invokes TSO/E Transmit to send the replicated datasets. As part of replication definition, you can select a different file transfer mechanism to send the environment table and EXEC startup datasets to the target MVS image.

If you use TSO/E Transmit to transfer files:

n you will need to manually invoke TSO/E Receive to receive the datasets for each target MVS image

n the Table dataset must be named rhilev.RKANISP

n the replicated datasets are transferred to your userid at the destination node

Transmitting datasets using a different FTP protocolInstead of TSO/E Transmit, you can use:

n IBM’s Netview File Transfer program. OSM/MVS is shipped with REXX EXECs that use IBM’s Netview File Transfer program in batch and foreground modes

n another file transfer program

To use another file transfer mechanism, you identify the REXX EXEC that invokes the file transfer protocol in the replication definition for the target MVS image.

Note: You specify the name of the REXX EXEC that invokes the file transfer mechanism in the User file transfer EXEC field on the Replication Definition panel. (See “Creating the replication definition” on page 172.)

The EXEC can either:

n invoke the FTP program in the foreground under TSO/E

n submit a batch job to perform the file transfer

Candle supplies the following REXX EXECs to invoke IBM's Netview File transfer mechanism in the dataset rhilev.TKANEXEC:

n KATNVFT1 - invokes Netview FTP under TSO in the foreground.

n KATNVFT2 - submits a Netview FTP batch job.

You can use these REXX EXECs as models for building your own file transfer EXECs.

Candle also supplies the following examples of EXECs that invoke TCP/IP File transfer program in the dataset rhilev.TKANEXEC:



n KATTCFT1 - invokes TCP/IP FTP under TSO in the foreground.

n KATTCFT2 - submits a TCP/IP FTP batch job.

In addition, Candle supplies the following skeletons in the rhilev.SLKI dataset. You can use these skeletons to simplify the process of

building custom file transfer EXECs.

The following ISPF variables are available in the Shared variable pool for use by the file transfer EXEC:

Starting distributionAfter the target MVS images have been selected or defined and the source environments have been replicated and modified, you are ready to distribute the replicated MVS environments.

Member Description

KATNVSK1, KATNVSK2

The skeletons used to build the Netview File Transfer EXECs.

KATTCSK0, KATTCSK1, KATTCSK2

Skeletons you can use to build TCP/IP File Transfer EXECs.

Variable Description

KATDEST Destination code.

KATLSDSN Local Startup dataset name.

KATLTDSN Local Table dataset name.

KATMVSID Target MVS image identification.

KATSEXEC Startup REXX EXEC name.

ATTSDSN Target Startup dataset name.

KATTTDSN Target Table dataset name.



Follow these steps to distribute the MVS environments.

Step Action

1 If the OSM/MVS Target Systems Distribution panel is not displayed, select Distribution... from the Controls pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Target Systems Distribution panel.

2 Either:n verify that the correct target images are selectedn select one or more target images and press Enter. (Y) appears in the Sel Stat column

for each selected image.)

3 Press F3 to initiate the distribution process.

Actions Help -------------------------------------------------------------------------- OSM/MVS Target Systems Distribution ROW 1 FROM 3 (S)elect a Target MVS Image for Distribution and Press ENTER. Press F3 to complete selection. MVS Image mask . . . * Local HLQ Target HLQ Sel Sel MVS Image (first 15 ch.) (first 15 ch.) Destination Stat _ GO2PS PSEDM.GO2PS PSEDM.GO2PS SYSG _ MAINT1 TDSM.DOC.ISPTLI TDSM.DOC CACOWLAA _ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG ******************************* BOTTOM OF DATA *************************** Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar


Displaying Replication and Distribution Information


IntroductionYou can display information about all the source systems that have been replicated and distributed to a target system. Only information about the last replication and distribution of a source system is displayed.

Displaying target system informationTo display replication and distribution information for a target

system:

Step Action

1 Select Replication Definitions... from the Setup pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Target Systems panel.

Actions Help -------------------------------------------------------------------------- OSM/MVS Target Systems ROW 1 FROM 2 (B)rowse, M(odify), A(dd), D(elete), C(opy) or (S)elect a Target MVS Image and Press ENTER MVS Image mask . . . * Local HLQ Target HLQ Sel Sel MVS Image (first 15 ch.) (first 15 ch.) Destination Stat _ GO2PS PSEDM.GO2PS PSEDM.GO2PS SYSG _ MAINT1 TDSM.DOC.ISPTLI TDSM.DOC CACOWLAA _ SYSK TDOG.OG999CUM KPATR.OG999CUM CACOWLAG *************************** BOTTOM OF DATA ******************************* Command ===> ____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



2 Select a target system.

Result: OSM/MVS displays the Target Image Display panel.

In addition to the replication definition for the target system, the panel display includes a scrollable list that contains:n the names of all OSM systems that have been replicated and distributed to the target

MVS imagen for each source OSM system:

– the date and time that the OSM system was last replicated and the userid that requested the replication

– the date and time that the OSM system was last distributed to the target MVS image and the userid that requested the distribution

Actions Help +-------------------------------------------------------------------+-- | OSM/MVS - Target Image Display ROW 1 TO 3 OF 3 | 3 | | ( | MVS Image id . . . . . . . . . : MAINT1 | T | Destination . . . . . . . . . : CACOWLAA | | Local replication DS HLQ . . . : TDSM.DOC.ISPTLIB | | Target replication DS HLQ . . : TDSM.DOC | M | User file transfer EXEC . . . : | | | | Last Modified . : 28 Aug 199 08:03 By : LHIRS3 | S | | S | OSM----- ------Last Replicated------- ------Last Distributed----- | _ | system Date Time By Date Time By | * | GO1PS 22 Aug 1996 11:58 LHIRS3 28 Aug 1996 08:04 LHIRS3 | * | GO1PSD1 22 Aug 1996 11:33 LHIRS3 28 Aug 1996 08:04 LHIRS3 | * | G 28 Aug 1996 08:21 LHIRS3 28 Aug 1996 08:04 LHIRS3 | | ************************** BOTTOM OF DATA ************************** | | | | | | Command ===> _______________________________________________________ | | F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar | +---------------------------------------------------------------------+ Command ===> ____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Section III. Controls 189

Section III. Controls

General Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Notification Operational Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225


General Operational Features 191

General Operational Features

OverviewOSM/MVS contains operational features that simplify the building of an application, allow you to update modifications and set global and file preferences, perform take-down and restart procedures, and balance the load on the system generated by probes.

This chapter describes:

n how to set global and file preferences

n the OSM/MVS Assistant, an intelligent, panel-driven feature that walks you through the building of a fully functioning probe

n how to refresh OSM/MVS setup data, as well as individual probes, status items, and situations

n how to take down and restart OSM/MVS

n how to balance the activation of probes

Chapter ContentsSetting Global Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Setting File Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195OSM/MVS Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Displaying Actual Probe Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Updating OSM/MVS Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Starting and Stopping OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Managing the Message Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Balancing Probe Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

10

Setting Global Preferences



IntroductionThe Global Preferences panel allows you to set specific enterprise-wide defaults that are used by OSM/MVS running in an OG/MVS address space.

ProcedureFollow this procedure to set OSM/MVS global defaults:

Step Action

1 Select Preferences from the action bar on the OSM/MVS main panel.

Result: The Preferences pull-down is displayed.+--------------------------------+| 1 1. Global Defaults... || 2. Notification Defaults... || 3. File Defaults... |+--------------------------------+

2 Type 1 and press Enter to select Global Defaults....

Result: The Global Preferences panel is displayed.

3 Type the data beside each item that you want to set or update and press Enter.

Result: The settings are activated.

----------------------------------------------------------------------- OSM/MVS - Global Preferences Enter or modify global default settings. Default OMEGAVIEW Text Type . . . . Transient Text +Peer Link Probe Frequency . . . . . 300 (Seconds)Peer Link Trap Prefix . . . . . . . @POSM/MVS Trap Prefix . . . . . . . . @OOSM/MVS DDNAME Prefix . . . . . . . @DLogon Retry Interval . . . . . . . 600 (Seconds)Logon Retry Count . . . . . . . . . 0Logon Wait Interval . . . . . . . . 0 (Seconds)OG/MVS Match Information . . . . . ON (ON|OFF)Update Omegaview special panels . . NO (YES|NO)Special panel refresh interval . . 360 (Seconds)Security class name . . . . . . . . $OGOSMActual Status Display . . . . . . . N (Y|N) Command ===> __________________________________________________________ F1=Help F4=Prompt F12=Cancel



Field definitions

Use these field definitions as a guide when setting or updating global preferences.

Field Description

Default OMEGAVIEW Text Type

The OMEGAVIEW field in which OSM/MVS places the value returned by a probe. Valid types are:n compact.n transient textn action textn user static textn none

Peer Link Probe Frequency

The rate at which the peer link probe requests data. This setting overrides the frequency field in the peer link probe definition.

Peer Link Trap Prefix The prefix for the names of the traps that are created by peer link routines.

OSM/MVS Trap Prefix The prefix for the names of all traps that are created by OSM/MVS control routines and probes.

OSM/MVS DDNAME Prefix

The 2–character DDNAME prefix used to generate the ddnames that read the logon password dataset.

Logon Retry Interval The time in seconds to wait before retrying a failed VTAM session logon request. The recovery operation will then try to recover the VTAM session the number of times specified in Logon Retry Count. The combination of the Logon Retry Interval period and the Logon Retry Count attempts constitutes a retry cycle.

Logon Retry Count The number of times to attempt to recover a failed VTAM session logon request in each logon retry period. The default is 0.

Logon Wait Interval The period of time to wait (in seconds) before reinitiating a failed VTAM session logon request recovery cycle. The default is 0.

If a non-zero value is specified in this field, the recovery operation will try to recover the VTAM session the number of times specified in Logon Retry Count at an interval of Logon Recovery Interval and then stop recovery attempts for the time specified in Logon Wait Interval. When the Logon Wait Interval period is completed, the recovery operation cycle is repeated.

If this field is zero, the recovery operation will try to recover the VTAM session for the amount of times specified in Logon Retry Count and then stop. If Logon Retry Count is not specified or is set to zero the recovery attempt is repeated until successful.

OG/MVS Match Information

This field specifies whether or not an end-of-match record is written to the RKOGLOGM when the OG/MVS match terminates.

ON The record is written.

OFF The record is not written.



Update OMEGAVIEW special panels

This field specifies whether or not the OSM/MVS work list, exception list, and notification panels are updated on OMEGAVIEW.

YES The panels are updated.

NO The panels are not updated.

If you have defined any status items whose activities will update these panels, set this value to YES.

Special panel refresh interval

The interval in seconds at which the OMEGAVIEW special panels are refreshed.

Security class name The name of the security class to be used by OSM/MVS This class must have been defined using the appropriate procedures of your security product.

Note: If you change the class name to a value that has not been defined by your security product or if the new class name does not have profiles defined or other profiles than you have in your current class, OSM security will be inactive (or limited depending on the profiles defined). See the OMEGACENTER Gateway for MVS Configuration and Customization Guide for more details.

Actual Status Display This field specifies whether or not actual as well as desired probe status is displayed on the Probe Manager panel.

YES Actual and desired probe status are displayed.

NO Only desired probe status is displayed.

See “Displaying Actual Probe Status” on page 201.


Setting File Preferences


IntroductionThe File Preferences panel allows you to set specific enterprise-wide defaults that are used by OSM/MVS running in an OG/MVS address space.

ProcedureFollow this procedure to set OSM/MVS file preferences:

Step Action

1 Select Preferences from the action bar on the OSM/MVS main panel.

Result: The Preferences pull-down is displayed.+--------------------------------+| 1 1. Global Defaults... || 2. Notification Defaults... || 3. File Defaults... |+--------------------------------+

2 Type 3 and press Enter to select File Defaults....


3 Type the data beside each item that you want to set or update and press Enter.

Result: The settings are activated.

Help ------------------------------------------------------------------------- OSM/MVS - File Preferences Enter or Modify OSM/MVS File Preferences. OSM/MVS REXX Library . . . . . REXXDD (DD) OSM/MVS REXX Dataset Name . . TDSM.AT999PRB.ISPFILE (DSN) OSM/MVS Main Panel Display . . TDOG.OG999CUM.TKANISP (DSN) Main Panel Display Member . . KATKAM03 (Member) Table Model dsname . . . . TDSM.DOC.ISPTLIB (DSN) OSM startup dsname . . . . CANDLE.USER.CLIST (DSN) OSM startup member . . . . PAULOGAT (Member) Command ===> ____________________________________________________________ F1=Help F12=Cancel



Field definitions

Use these field definitions as a guide when setting or updating file preferences.

Field Description

OSM/MVS REXX Library

The name library to be used as the default OSM/MVS REXX library.

OSM/MVS REXX Dataset Name

The name of the dataset to be used as the default OSM/MVS REXX dataset.

OSM/MVS Main Panel Display

The name of the dataset that contains the main panel display member.

Main Panel Display Member

The name of the member that displays the main panel.

Table Model dsname The name of the dataset that can be used as a model for the allocation of table data sets for the Replication function. It is also used as the source for the the Replication function. It is also used as the source for the new table data set. Normally this is the data set with the low level qualifier RKANISP.

OSM startup dsname The name of the dataset that contains the REXX EXEC that starts the OSM User Interface.

OSM startup member The name of the member that contains the REXX EXEC that starts the OSM User Interface. Normally this member name is OGAT but can have been changed during installation.


OSM/MVS Assistant

OSM/MVS Assistant

IntroductionThe OSM/MVS Assistant displays panels that prompt for more data when you add, copy, or modify a

n probe

n status item

n situation

n distributed system

The OSM/MVS Assistant guides you through the process of building a fully functioning probe. It uses prompts, panels, and messages to ensure that you have entered all required information. You can also use the OSM/MVS Assistant to change a probe’s status from inactive to active.

Note: The OSM/MVS Assistant is not directly available as a pull-down menu selection. It is activated during the probe building process.

OSM/MVS Assistant panelAfter you type an action code to build a probe or status item and press Enter, an OSM/MVS Assistant panel, similar to the one below, is displayed.

+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 5 OF 7 || || (S)elect a referenced item and press Enter. || || ----------------------------------------------------------------------- || 1 Probe has been copied, now select the Status Item || to build Status and Activity rows for the Probe. || 2 3 4 5 || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item ** Add New ** Required || _ Program ** Add New **PRBEXEC Required || _ Act-WARNING ** Add New ** Not Available || _ Act-OK ** Add New ** Not Available || _ Act-NONE ** Add New ** Not Available || ** Copy completed successfully 6 || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

OSM/MVS Assistant


The panel consists of the following key parts (labeled on the figure):

How to use the OSM/MVS AssistantThe OSM/MVS Assistant displays the steps needed to build a working probe, with any required items displayed first. After you complete an item, it is moved to the bottom of the list.


1 Instruction Area

Prompts you for the next step in the probe building process.

2 Selection Field

Field for selecting an item.

3 Type Key items you select to assemble a working probe. They include the:n program, or the REXX source file for the proben status itemsn statuses (Act-WARNING, Act-OK, Act-NONE,

Act-CRITICAL)n distributed system definitionsn probe definitions.

4 Name Description of the item. If the item is undefined, the phrase ** Add New ** is displayed.

5 Condition Displays 1 of 5 values:

Required Add information for this item.

Complete Information for this required item was entered.

Not Available

After you complete other required items, this condition changes to Available, Required, or Optional.

Available You may enter additional information for this item.

Optional When copying a probe, modifying status items is optional.

6 Message Line Result of the last action.


OSM/MVS Assistant

To use the OSM/MVS Assistant:

Step Action

1 Tab to an item marked Required on the OSM/MVS Assistant

panel, type S in the entry field, and press Enter.

Result:

1. If you select Program, the source code for the probe is displayed.

2. If you select other choices, such as a new status item (shown below), an entry panel is displayed for you to provide the needed information.+----------------------------- Add Status Item ------------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . . . 004 + || System ID . . . . . B_______ + || Domain ID . . . . . B_______ + || Status Item . . . . ____________________ || || Description . . . . ________________________________________ || Default Status . . . NONE + || Threshold OK . . . . ____________________ || Threshold Critical . ____________________ || Spikes Check . . . . N (Y/N) || Log Status Change . _ + || OMEGAVIEW Text Type Transient Text + || Input Parms . . . . ________ + || Probe Directive . . ____________________ || Misc. Parms . . . . ________________________________________ || || F1=Help F4=Prompt F12=Cancel |+----------------------------------------------------------------------------+

OSM/MVS Assistant


ExamplesExamples of using the OSM/MVS Assistant to build a probe are shown in “Monitoring for the Data Center” on page 265 and “Setting Up Distributed Systems Monitoring” on page 287.

2 Enter the appropriate information. Press Enter if you typed information on a panel; press the Exit key if you edited or viewed a REXX source file.

Result: The OSM/MVS Assistant panel is displayed.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 7 OF 7 || || (S)elect a referenced item and press Enter. || || ----------------------------------------------------------------------- || Status Item has been updated. Modify Activity || rows for your desired actions. || || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item AMS_STC_CSA_2 Complete || _ Probe CSA Usage on SYSA Complete || _ Program KATRA011 Available || _ Act-WARNING AMS_STC_CSA_2 Available || _ Act-OK AMS_STC_CSA_2 Available || _ Act-NONE AMS_STC_CSA_2 Available || _ Act-CRITICAL AMS_STC_CSA_2 Available || ** Copy completed successfully || Command ===> _____________________________________________________________ || |+----------------------------------------------------------------------------+

If the condition of any other items is Required, the panel prompts you to complete the next required item.

When you have completed all required items, you may complete items with an Available condition, which will allow you to set thresholds and actions for a particular status.

3 When you have finished, press the Exit key.

Result: The OSM/MVS Assistant Exit Validation panel is displayed.

+------------------- Exit Validation --------------------+| OSM/MVS Assistant || || Press ENTER to continue. Press the CANCEL key to || return to the previous screen. || || ** All Required Rows Complete ** || Probe will be Activated || || Activate . Y (Y/N) || || F1=Help F12=Cancel |+--------------------------------------------------------+

4 Select Y to activate the probe or N to keep the probe inactive. Press Enter.

Result: The information is retained and the Probe Manager panel is displayed.


Displaying Actual Probe Status


IntroductionThe previous section of this chapter, “OSM/MVS Assistant” on page 197, describes how to set the initial probe status to active or inactive when you add, copy or modify a probe. (See “Using action codes” on page 32 for a description of how to reset the status of a probe.)

Setting a probe establishes the desired status for the probe. Whether a probe actually is active depends on:

n factors you control, such as the monitoring period defined for the the probe

n factors you do not control, such as the up or down status of a machine.

This section describes how to enable and define the display of probe status on the Probe Manager panel so that you display the actual state of probes as well as the desired state established through your probe settings.

Using the procedure described in this section allows you to use OSM/MVS under TSO/ISPF to see the actual status of probes running anywhere in your VTAM environment on OSM/MVS systems. You can use SNA or TCP/IP communications protocol to communicate probe status information from the Gateway system to ISPF.



The Probe Manager panel pictured below contains both types of probe status displays. Entries under the column heading A list the desired state. Entries under the column heading S list the actual status.

Note: The SHOWOSM command described in Appendix D of this document indicates whether a probe has been executed but does not indicate whether the data returned is valid. If the actual status display for a probe is set to Y, the probe is executing and the data being returned is valid.

To display actual probe status, you perform the following two steps.

1. Enable actual status display.2. Request actual status display for specific OG/MVS systems.

Using APPC and TCP/IP protocolsFor Gateway systems using Advanced Program-to-Program Communications (APPC) protocol, OSM/MVS utilizes the EXEC processing functions built in to an APPC command to communicate with APPC partners running on other OG/MVS systems to determine the actual state of probes on that system.

Actions View Managers Help------------------------------------------------------------------------------ OSM/MVS - Probe Manager ROW 73 FROM 139 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify,(R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate,and (>) Show Dependents. ---------------------------------------------------------------------------- ID Probe Description Type System Domain A S_ 036 CICS VSAM waits Q G G Y N_ 038 CICS Dataset Status Q G G Y Y_ 050 Active Tasks H G G N N_ 050 Active Tasks H SYSG3 SYSG3 N ?_ 051 MVS Batch Job count Q G G N N_ 052 MVS Started Task count Q G G Y N_ 053 MVS Tape mount requests Q G G Y Y_ 054 MVS Intervention Required Coun Q G G Y Y_ 055 TSO Response Time Q G G Y N_ 056 TSO Transaction Rate Q G G N N_ 056 TSO Transaction Rates Q SYSG3 SYSG3 Y ?_ 057 MVS Initiator status H G G N N_ 058 MVS Job class queues Q G G N N_ 059 MVS JES printer status H G G Y Y_ 066 CPU performance by task Q G G Y Y_ 071 TSO End-to-End Tran Rate Q G G N N_ 072 TSO End-to-End Host Response Q G G Y N_ 073 TSO End-to-End Net Response Q G G N N Command ===> __________________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Note: Before using this capability, make sure that OMEGACENTER Gateway APPC is installed on the current system as well as on all OG/MVS systems from which you will gather actual probe status.

See the OMEGACENTER Gateway for MVS documentation on APPC Interface Support for more information on using APPC functions to send and receive data from APPC partner transaction programs running on OSM/MVS systems.

For Gateway systems using TCP/IP protocol, be sure you have already concatenated the TCP library that contains EZASOK03 into your STEPLIB concatenation. (EZASOK03 is usually found in the library that has the low-level qualifier SEZALINK.) See your TCP/IP system administrator or the appropriate IBM documentation for more information on using TCP/IP protocol.

Enabling actual status displayYou must first enable the actual status display feature. You enable actual status display on the Global Preferences panel.

Note: Using the Global Preferences panel to enable actual status display also allows you to disable actual status display globally, which may be more convenient than turning actual status display on and off for individual OG/MVS systems.

Follow these steps to enable actual status display.

Step Action

1 Select Global Defaults... from the Preferences pull-down on the OSM/MVS main panel.


Help -------------------------------------------------------------------------- OSM/MVS - Global Preferences Enter or modify global default settings. Default OMEGAVIEW Text Type . . . . Transient Text + Peer Link Probe Frequency . . . . . 300 (Seconds) Peer Link Trap Prefix . . . . . . . @P OSM/MVS Trap Prefix . . . . . . . . @O OSM/MVS DDNAME Prefix . . . . . . . @D Logon Retry Interval . . . . . . . 600 (Seconds) Logon Retry Count . . . . . . . . . 0 Logon Wait Interval . . . . . . . . 0 (Seconds) OG/MVS Match Information . . . . . ON (ON|OFF) Update Omegaview special panels . . NO (YES|NO) Special panel refresh interval . . 360 (Seconds) Security class name . . . . . . . . $OGOSM Actual Status Display . . . . . . . N (Y|N) Command ===> _____________________________________________________________ F1=Help F4=Prompt F12=Cancel



Requesting actual probe status display for OG/MVS systemsFollow these steps to request actual probe status statistics be gathered on an OG/MVS system.

Note: This procedure assumes you are modifying an existing system definition. You can incorporate the steps performed here as part of the procedure you perform to create a new system definition.

2 Move the cursor to the Actual Status Display field. This field specifies whether you want to gather actual status information on probes that are running in your OSM/MVS run time systems. The default is N. Enable actual status display by typing Y, and pressing Enter. Once this global value is set to Y, you can then enable and disable actual status display for individual OG/MVS systems. Set this value to N to turn actual status display off for every system defined to this user interface.

Step Action

1 Select System Environments... from the Setup pull-down menu on the OSM/MVS main panel.

Result: The System Environments panel is displayed.

Actions Help-------------------------------------------------------------------------- OSM/MVS - System Environments ROW 1 TO 13 OF 13 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (D)elete and the action series Mi(G)rate T(O). For DAS systems additional actions are Ac(T)ivate and (I)nactivate. Local Focal Sel System Sys. ID SYSNAME System Description _ O1KP SYSG SYSG N test2 _ GO1KP SYSG SYSG N Candle Development System-G _ G2 LINKID4G SYSG N Norman Lew System G2 _ G1 LINKID4G SYSG Norman Lew System G1 _ GO1PSD1 SYSGO1PS SYSG AR for notification testing _ GO1PS SYSGO1PS SYSG Y Candle Development System-G _ L3 SYSG3 SYSG Candle LAN _ SYSG3 SYSG3 SYSG N Another toolkit for System-G _ G SYSGO999 SYSG N Candle Development System-G _ R2 SYSGO999 SYSG Unix System (II) _ R3 SYSBO122 SYSB Unix System (III) _ L1 SYSGO999 SYSG Candle LAN _ R1 SYSGO999 SYSG Unix System ************************** BOTTOM OF DATA ******************************** Command ===> ____________________________________________________________ F1=Help F7=Backward F8=Forward F12=Cancel



2 Move the cursor to the select column entry for the system for which you are adding actual status display (in this example, GO1PS). Type M to modify the definition and then press Enter.

Result: The Modify System Environment panel is displayed.+------------------ Modify System Environment ------------------+| OSM/MVS - System Data || || Modify the information, then press ENTER. || || System ID . . . . : GO1PS || Description . . . . Candle Development System-G || System Type . . . : M (M)VS or (D)AS || || For the MVS system type, please press ENTER || to view/modify additional information. || || || F1=Help F12=Cancel |+---------------------------------------------------------------+

3 Press Enter.

Result: OSM/MVS displays the Modify System Environment panel. Note that the actual status display information has not yet been entered for system GO1PS.

+------------------------- Modify System Environment -------------------------+| OSM/MVS - MVS System Data || || Modify the information, then press ENTER. || || System GO1PS Description Candle Development System-G || Local System ID . . SYSGO1PS || SYSNAME . . . . . . SYSG || Subsystem Name . . O1PS || MSMF? . . . . . . . Y (Y/N) || Focal System? . Y (Y/N) || Echo Time . . . 120 secs || VTAM ACB . . . . RGAT999P || VTAM LogMode . . OGLU62 || VTAM Major Node . . ARGAT12P || || Actual Status Display? . N N=None A=APPC T=TCP/IP || ------ APPC Definitions. ------ || TP Name . . ________ Partner Lu Name ________ Local Lu Name ________ || ------ TCP/IP Definitions. ------ || TCP/IP Port ________ TCP/IP STC Name ________ OSM Job Name ________ || TCP/IP Address . _______________ || F1=Help F12=Cancel |+-----------------------------------------------------------------------------+



The following example illustrates the MVS System Data panel completed for an APPC connection.

Use the following table as a guide for completing the APPC Definitions portion of the MVS System Data panel.

4 Tab to the Actual Status Display field. Enter one of the following values.n A to specify that you want to gather probe status information from a system that uses

APPC communication. The cursor moves to the TP Name field in the APPC Definitions section of the panel.

n T to specify that you want to gather probe status information from a system that uses TCP/IP communication. The cursor moves to the TCP/IP Port field in the TCP/IP Definitions section of the panel.

n N to turn off actual status display for this system. (Remember, you can turn off actual status display for all systems by resetting the Global Preferences actual status display value to N.)

5 Enter values appropriate for the communication protocol. (See the following tables.) When you are finished, press Enter to save the actual status display request.

Field Description

TP Name The name of the APPC transaction program running on the OG/MVS system from which actual probe status is desired. (See Candle’s APPC documentation for more information.)

Partner Lu Name The logical unit name defined for the OG system from which actual probe status is to be collected. (See the APPC documentation for more information.)

+------------------------- Modify System Environment -------------------------+| OSM/MVS - MVS System Data || || Modify the information, then press ENTER. || || System GO1PS Description Candle Development System-G || Local System ID . . SYSGO1PS || SYSNAME . . . . . . SYSG || Subsystem Name . . O1PS || MSMF? . . . . . . . Y (Y/N) || Focal System? . Y (Y/N) || Echo Time . . . 120 secs || VTAM ACB . . . . RGAT999P || VTAM LogMode . . OGLU62 || VTAM Major Node . . ARGAT12P || || Actual Status Display? . A N=None A=APPC T=TCP/IP || ------ APPC Definitions. ------ || TP Name . . SYSGTP Partner Lu Name ACTDIS01 Local Lu Name ACTDIS04 || ------ TCP/IP Definitions. ------ || TCP/IP Port ________ TCP/IP STC Name ________ OSM Job Name ________ || TCP/IP Address . _______________ || F1=Help F12=Cancel |+-----------------------------------------------------------------------------+



The following example illustrates the MVS System Data panel completed for a TCP/IP connection.

Use the following table as a guide for completing the TCP/IP definitions portion of the MVS System Data panel.

Local Lu Name The logical unit name you will use to communicate with the OG system from which actual probe status is to be collected. This name must be defined on the system on which you run the OSM/MVS user interface.

Note: If this name is not specified as the local LU in the local system VTAM definitions of systems, VTAM problems will occur if you try to use this interface to collect actual probe status.

Field Description

TCP/IP Port A number in the range 2500 to 9999. (The port numbers 0-1999 are reserved for well known ports. Port numbers 2000-2499 are not available through this interface.) The same port numbers must be used on both systems. Check with your TCP/IP administrator for the port number to use.

Note: This port number will be used across systems and so cannot be defined to another user in the same system.

TCP/IP STC Name The name of the TCP/IP started task on the MVS system that runs the OSM task on the system you are trying to connect to.

OSM Job Name The name of the started task that runs OSM on the system you are trying to connect to.

+------------------------- Modify System Environment -------------------------+| OSM/MVS - MVS System Data || || Modify the information, then press ENTER. || || System G Description Candle Development System-G || Local System ID . . SYSGO999 || SYSNAME . . . . . . SYSG || Subsystem Name . . OMS1 || MSMF? . . . . . . . Y (Y/N) || Focal System? . N (Y/N) || Echo Time . . . 240 secs || VTAM ACB . . . . RGAT9990 || VTAM LogMode . . OGLU62 || VTAM Major Node . . ARGAT999 || || Actual Status Display? . T N=None A=APPC T=TCP/IP || ------ APPC Definitions. ------ || TP Name . . ________ Partner Lu Name ________ Local Lu Name ________ || ------ TCP/IP Definitions. ------ || TCP/IP Port 2501 TCP/IP STC Name TCPIP23 OSM Job Name TDAFS01 || TCP/IP Address . 198.210.62.101 || F1=Help F12=Cancel |+-----------------------------------------------------------------------------+



Displaying actual probe statusPerform the following step to display actual probe status.

Notice that:

n the A column lists the desired status of the probe, and the S column contains the actual status display

n if the desired status of a probe is inactive (N), the actual status is always inactive also

TCP/IP Address The TCP/IP address, in TCP/IP notation, of the MVS system to which you are connecting (for example, 198.210.48.68).

Note: If two Gateway systems are running in the same MVS, the same address is used for both.

Step Action

1 Select Probe Manager... from the Managers pull-down on the OSM/MVS main panel.

Result: The Probe Manager panel is displayed.

Actions View Managers Help-------------------------------------------------------------------------- OSM/MVS - Probe Manager ROW 73 FROM 139 Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify,(R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate,and (>) Show Dependents. -------------------------------------------------------------------------- ID Probe Description Type System Domain A S_ 036 CICS VSAM waits Q G G Y N_ 038 CICS Dataset Status Q G G Y Y_ 050 Active Tasks H G G N N_ 050 Active Tasks H SYSG3 SYSG3 N ?_ 051 MVS Batch Job count Q G G N N_ 052 MVS Started Task count Q G G Y N_ 053 MVS Tape mount requests Q G G Y Y_ 054 MVS Intervention Required Coun Q G G Y Y_ 055 TSO Response Time Q G G Y N_ 056 TSO Transaction Rate Q G G N N_ 056 TSO Transaction Rates Q SYSG3 SYSG3 Y ?_ 057 MVS Initiator status H G G N N_ 058 MVS Job class queues Q G G N N_ 059 MVS JES printer status H G G Y Y_ 066 CPU performance by task Q G G Y Y_ 071 TSO End-to-End Tran Rate Q G G N N_ 072 TSO End-to-End Host Response Q G G Y N_ 073 TSO End-to-End Net Response Q G G N N Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



n if the desired status of a probe is active (Y), the actual status can be:

– Y, indicating the actual state of the probe is active

– N, indicating the actual state of the probe is inactive

– ?, indicating the actual state of the probe is unknown. For example, an unknown actual probe status is reported if a communication error has occurred or if the started task is not running on the queried system.

Updating OSM/MVS Data



IntroductionAt times, you may want to make changes to OSM/MVS. For example, you may want to add a new log or follow-up routine, or modify a probe. After making such changes, you need to perform a refresh, or update, procedure so OSM/MVS can accept them.

There are two types of refresh activity you perform with OSM/MVS:

n completely refreshing OSM/MVS after making environment changes

n refreshing individual probes, status items, or situations

Global OSM/MVS refreshYou need to perform a global refresh of OSM/MVS after making changes to any Setup or Preferences pull-down selection. These include such items as adding a log, and changing a VTAM definition. When the Global Refresh program is executed, it removes any update requests and processes any delete requests that are in the queue before starting Global Refresh processing. Once this processing has completed OSM/MVS checks to determine whether there are any new Single Requests in the queue. If there are, queue processing is restarted.

When the Shutdown program is executed, it initiates Shutdown processing and purges the Refresh queue.

Should the Refresh program abend, you can restart the Refresh queue by issuing the following command from the console:

O999 EX KATRAU04 ’RESTART’

where O999 is the OG/MVS subsystem name.

Note: Refreshing notification data is handled separately. See “Refreshing Notification” on page 231.



Refresh procedureFollow this procedure to refresh OSM/MVS:

Refreshing individual probes, status items, or situationsAfter you have created or modified an individual probe, status item, or situation, you need to register these updates with OSM/MVS. To do so, use the Refresh (R) action code available on their respective managers’ displays.

Each single probe Refresh request is processed serially and sequentially. If OSM/MVS has been started, a single probe Refresh is in progress, and a Global Refresh or a Shutdown is requested, the Global Refresh request or the Shutdown request is queued.

Step Action

1 Select Controls from the action bar on the OSM/MVS main panel.

Result: The Controls pull-down is displayed. +-------------------------------+ | __ 1. Start OSM/MVS... | | 2. Refresh OSM/MVS... | | 3. Stop OSM/MVS... | | 4. Refresh Notification... | | 5. Receive Notification... | | 6. Resolve Incident... | | 7. Escalate Incident... | | 8. Probe Balancer... | | 9. Messages... | | 10. Replication... | | 11. Distribution... | | 12. Exit (F3) | +-------------------------------+

2 Type 2 and press Enter to select Refresh OSM/MVS.

Result: The Refresh OSM/MVS panel is displayed.

3 Type S beside each system you want to refresh and press Enter.

Result: OSM/MVS is refreshed on the systems that you selected.

Help -------------------------------------------------------------------------- Refresh OSM/MVS ROW 1 FROM 11 (S)elect a System and press ENTER. System SYSNAME Description _ B SYSB Development System B _ C SYSG Administration System C _ G SYSG Development System-G _ GO1PS SYSG Another toolkit for System-G _ SYSG3 SYSG Candle Development System-G *************************** BOTTOM OF DATA *******************************

Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



As OSM/MVS loops through the Refresh queue to service single probe Refresh requests, it checks to determine whether there are any Global Refresh or Shutdown requests waiting. If so, the single probe Refresh processing is suspended. Then, if a Shutdown Request is waiting, it is processed. If there is no Shutdown request waiting, but a Global Refresh request is waiting, it is processed. If neither is waiting, OMEGACENTER Status Manager services the next single probe Refresh request in the queue.

Procedure for refreshing a probeThis is the procedure for refreshing an individual probe. The procedure for status items and situations is similar.

Step Action

1 On the Probe Manager display, select the probe you modified with an R action code. In the figure shown, probe 036 is selected.

2 Press Enter.

Result: Probe 036 is refreshed with the new values.

Actions View Managers Help-------------------------------------------------------------------------- OSM/MVS - Probe Manager ROW 73 FROM 139

Select a row and press Enter. Valid actions are (A)dd, (C)opy, (M)odify, (R)efresh, (D)elete, (F)ind, (E)dit Probe Program, (I)nactivate, Ac(T)ivate, and (>) Show Dependents.-------------------------------------------------------------------------- ID Probe Description Type System Domain A SR 036 CICS VSAM waits Q G G Y N_ 038 CICS Dataset Status Q G G Y Y_ 050 Active Tasks H G G N N_ 050 Active Tasks H SYSG3 SYSG3 N ?_ 051 MVS Batch Job count Q G G N N_ 052 MVS Started Task count Q G G Y N_ 053 MVS Tape mount requests Q G G Y Y_ 054 MVS Intervention Required Coun Q G G Y Y_ 055 TSO Response Time Q G G Y N_ 056 TSO Transaction Rate Q G G N N_ 056 TSO Transaction Rates Q SYSG3 SYSG3 Y ?_ 057 MVS Initiator status H G G N N_ 058 MVS Job class queues Q G G N N_ 059 MVS JES printer status H G G Y Y_ 066 CPU performance by task Q G G Y Y_ 071 TSO End-to-End Tran Rate Q G G N N_ 072 TSO End-to-End Host Response Q G G Y N_ 073 TSO End-to-End Net Response Q G G N N Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar


Starting and Stopping OSM/MVS


IntroductionYou need to run a start and stop procedure only if it becomes necessary to take OSM/MVS down. For example, your data center may need to stop OSM/MVS in order to run another application.

You do not need to start OSM/MVS prior to using it. It is automatically started as part of the installation and setup process.

Do not use the start and stop procedure to update changes made to OSM/MVS. Although stopping and restarting OSM/MVS updates changes, it is simpler to use the refresh feature. See “Updating OSM/MVS Data” on page 210.

Start procedurePerform the following steps to start OSM/MVS:

Step Action

1 Access OSM/MVS and display the main panel.

2 Press F10 to move the cursor beside the Controls pull-down.

Controls Managers Setup Preferences Help-------------------------------------------------------------------------- OMEGACENTER Status Manager for MVS Press F10 to select a function. Version 999 OOOOO SSSSS MM MM // MM MM VV VV SSSSS OO OO SS SS MMM MMM // MMM MMM VV VV SS SSOO OO SS MMMM MMMM // MMMM MMMM VV VV SSOO OO SS MM MM MM MM // MM MM MM MM VV VV SSOO OO SS MM MMM MM // MM MMM MM VV VV SSOO OO SS MM M MM // MM M MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SSS MM MM // MM MM VV VV SSSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VVV SS OO OO SS SS MM MM // MM MM VVV SS SS OOOOO SSSSS MM MM // MM MM VVV SSSSS Command ===> _____________________________________________________________ F1=Help F3=Exit F10=ActBar



3 Press Enter.

Result: The Controls pull-down menu is displayed. +-------------------------------+ | __ 1. Start OSM/MVS... | | 2. Refresh OSM/MVS... | | 3. Stop OSM/MVS... | | 4. Refresh Notification... | | 5. Receive Notification... | | 6. Resolve Incident... | | 7. Escalate Incident... | | 8. Probe Balancer... | | 9. Messages... | | 10. Replication... | | 11. Distribution... | | 12. Exit (F3) | +-------------------------------+

4 Select Start OSM/MVS... and press Enter.

Result: The Start OSM/MVS panel is displayed.

5 Type S beside each system where you want OSM/MVS to run and press Enter.

Result: OSM/MVS is started. It is also updated with the most current information from Managers and Setup. Probes, whose Domain IDs match the System IDs that you selected, are activated and operate according to their schedules.

Help -------------------------------------------------------------------------- Start OSM/MVS ROW 1 FROM 1 (S)elect a System and press ENTER. System SYSNAME Description _ B SYSB Candle Development System ************************** BOTTOM OF DATA ******************************** Command ===> ____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



Stop procedureThe procedure for stopping OSM/MVS is as follows:

Step Action

1 Select Controls from the action bar on the OSM/MVS main panel..

Result: The Controls pull-down is displayed. +-------------------------------+ | __ 1. Start OSM/MVS... | | 2. Refresh OSM/MVS... | | 3. Stop OSM/MVS... | | 4. Refresh Notification... | | 5. Receive Notification... | | 6. Resolve Incident... | | 7. Escalate Incident... | | 8. Probe Balancer... | | 9. Messages... | | 10. Replication... | | 11. Distribution... | | 12. Exit (F3) | +-------------------------------+

2 Select Stop OSM/MVS... and press Enter.

Result:The Stop OSM/MVS panel is displayed showing all systems defined to OSM/MVS.

3 Type S beside each system where you want to stop OSM/MVS and then press Enter.

Result: OSM/MVS is stopped on the selected systems.

Help -------------------------------------------------------------------------- Stop OSM/MVS ROW 1 FROM 3 (S)elect a System and press ENTER. System SYSNAME Description _ B SYSB Development System B _ D SYSD Administration _ B SYSH Development System H ************************** BOTTOM OF DATA ******************************** Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Managing the Message Log



IntroductionYou may want to send messages to a log when a problem occurs in your system. The message log allows you to view system messages as well as create your own messages. These messages have IDs that can be coded into a REXX exec causing the message to be issued under certain conditions.

Note:

n You cannot use the letter K as the first letter of a message ID. That ID is reserved for system messages.

n You cannot modify or delete system messages.

Editing a messageTo edit a message, follow these steps:

Step Action

1 Select Controls from the action bar on the OSM/MVS main panel.

Result: The Controls pull-down menu is displayed.

Controls Managers Setup Preferences Help-------------------------------------------------------------------------- OMEGACENTER Status Manager for MVS Press F10 to select a function. Version 999 OOOOO SSSSS MM MM // MM MM VV VV SSSSS OO OO SS SS MMM MMM // MMM MMM VV VV SS SSOO OO SS MMMM MMMM // MMMM MMMM VV VV SSOO OO SS MM MM MM MM // MM MM MM MM VV VV SSOO OO SS MM MMM MM // MM MMM MM VV VV SSOO OO SS MM M MM // MM M MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SSS MM MM // MM MM VV VV SSSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VV VV SSOO OO SS MM MM // MM MM VVV SS OO OO SS SS MM MM // MM MM VVV SS SS OOOOO SSSSS MM MM // MM MM VVV SSSSS Command ===> _____________________________________________________________ F1=Help F3=Exit F10=ActBar



2 Select Messages... and press Enter.

+-------------------------------+ | 9 1. Start OSM/MVS... | | 2. Refresh OSM/MVS... | | 3. Stop OSM/MVS... | | 4. Refresh Notification... | | 5. Receive Notification... | | 6. Resolve Incident... | | 7. Escalate Incident... | | 8. Probe Balancer... | | 9. Messages... | | 10. Replication... | | 11. Distribution... | | 12. Exit (F3) | +-------------------------------+

Result: The Messages panel is displayed showing all of the system and user-defined messages.

3 Type A beside one of the numbers to add a new message.

Result: The Add Message screen is displayed.

OSM/MVS - Messages ROW 1 TO 13 OF 150 Select a row and press Enter. Valid actions are (A)dd, (M)odify, (I)nquire, (D)elete, and (R)efresh. --------------------------------Messages-------------------------------- A ID Text _ KAT0001E ’ADDRESS command failed for OMEGAMON system’ p1 ’Return code:’ _ KAT0001I ’No response to Incident’ p1 ’Escalation completed’ _ KAT0001W msgparms _ KAT0002E ’Invalid argument string:’ p1 _ KAT0002W ’Status item’ p1 ’is not numeric. Current value:’ p2 _ KAT0003E ’Log Routine failure for Probe:’ p1 ’Return code:’ p2 _ KAT0003I ’More than 24 problems encountered in OSM/MVS’ _ KAT0004E ’OSM/MVS Data Manager:’ p1 ’failed.’ _ KAT0004I ’Data manager’ module ’starts at --’ p1 ’and ended at --’ p2 _ KAT0005I ’OMEGAMON/CICS RTA collector not active’ _ KAT0006E ’Follow-up routine’ p1 ’failure for status item:’ p2 ’Return C _ KAT0006I ’Starting’ p1 ’List initialization’ _ KAT0007E ’Notify routine failure for Status Item:’ p1 ’Return code:’ p2 Command ===> ____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



4 Enter the message number, message text, system action, and user response in the fields and press Enter

Note: For the Message Text field, you must enclose all text in single quotes.+-------------------------------Add Message---------------------------------+| OSM/MVS - Messages || || Enter the Message ID, Text, and System Action. You will then be || prompted for a Message Explanation and the User Response. || || Message ID . . . . ________ || Message Text . . . : || ______________________________________________________________________ || ___________________________________ || System Action . . : || ______________________________________________________________________ || || F1=Help F12=Cancel |+---------------------------------------------------------------------------+

Result: The message is added to the message log. To specify when you want a message to appear, code the message number into a REXX exec.


Balancing Probe Startup


IntroductionIf you plan to activate your probes on a daily basis, you may want to stagger their startup times. This prevents large numbers of probes from being activated simultaneously, which could cause CPU usage spikes.

Using the Probe BalancerThe Probe Balancer is a feature that addresses this potential problem. When using this feature you:

n select a system for analysis

n direct the Probe Balancer to perform an interval analysis and display a graph of probe start times

n identify and correct imbalances by selecting individual probes and changing their start times



Balancing Probe Activation procedureFollow these steps to balance the activation of probes on your system.

Step Action

1 Select Probe Balancer... from the Controls pull-down of the OSM/MVS main panel.+-------------------------------+| 8 1. Start OSM/MVS... || 2. Refresh OSM/MVS... || 3. Stop OSM/MVS... || 4. Refresh Notification... || 5. Receive Notification... || 6. Resolve Incident... || 7. Escalate Incident... || 8. Probe Balancer... || 9. Messages... || 10. Replication... || 11. Distribution... || 12. Exit (F3) |+-------------------------------+

Result: The Probe/Status Balancer panel appears.

Help-------------------------------------------------------------------------- OSM/MVS - Probe/Status Balancer Enter a MVS System ID and a Starting Time for load balance analysis. You can also change the default time period and sampling rate. MVS System ID ________ + Starting Time ________ (HH:MM:SS) Time Period . 10 (Minutes) Sampling Rate 5 (Seconds) F1=Help F4=Prompt F10=ActBar F12=Cancel



2 Choose the MVS system you want to analyze and the time parameters for load balance analysis.

a. Enter the identifier of the MVS system you want to analyze. To display a list of available systems, press the Prompt key. You can then select a system by tabbing to the one you want, typing S, and pressing Enter.

b. Enter the starting time in hh:mm:ss format. This should precede or correspond to a time you suspect a large number of probes are being activated.

c. The default time period analyzed by the load balancer is 10 minutes and the default sampling rate is 5 seconds. To change those values, tab to the respective field, type a new value, and press Enter.

Result:A load balance analysis is performed on your probes. After a few seconds, the Balance Display panel appears.

_ Actions Help-------------------------------------------------------------------------- OSM/MVS - Balance Display ROW 1 TO 14 OF 120 (S)elect a row and press Enter. System : Candle Development System Run Time Count Status Items Displayed / Datamanagers Executed _ 08:00:00 6 =====> _ 08:00:05 0 _ 08:00:10 1 > _ 08:00:15 0 _ 08:00:20 1 > _ 08:00:25 0 _ 08:00:30 1 > _ 08:00:35 0 _ 08:00:40 2 => _ 08:00:45 2 => _ 08:00:50 1 > _ 08:00:55 0 _ 08:01:00 1 > _ 08:01:05 0 ** Calculations complete Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



3 The Balance Display counts the number of probes activated in each time interval (usually 5 seconds) and graphs them for easy viewing.

Examine the Balance Display for high count values and select those intervals for probe redistribution.n Tab to the interval containing a large number of probe start times and press Enter.Result: The Probes in a Time Period panel is displayed.+---------------------------- Items at 08:00:00 ------------------------------+| OSM/MVS - Probes in a Time Period || || S(elect) a Probe and press Enter. || || ------------------------------------------------------------------------ || Run Time Probe Domain Items Probe Description || _ 08:00:00 G01 G 1 OMEGAMON/MVS Data Manager (G) || _ 08:00:00 658 G 1 Check The Job Queue For Class A || _ 08:00:00 A99 G 1 End-to-end response time probe || _ 08:00:00 K00 G 1 VTAMA probe || _ 08:00:00 AR2 G 1 TSO Response Time SYSG || ****************************** BOTTOM OF DATA ***************************** || || || || Command ===> ______________________________________________________________ || F1-Help F12=Cancel |+-----------------------------------------------------------------------------+

4 Select probes for redistribution to other time intervals.n Tab to the probe whose start time you want to change, and type S, then press Enter.Result: The Probe Schedule panel for the probe appears.

+-----------------------------------------------+| OSM/MVS - Probe Schedule || || Fill in the information, then press Enter. || || Start Time . . . . 08:00:00 (hh:mm:ss) || Stop Time . . . . 18:00:00 (hh:mm:ss) || Time Interval . . 120 (Seconds) || || F1=Help F12=Cancel |+-----------------------------------------------+

5 Change the probe start times.

a. Tab to the Start Time field on the Probe Schedule panel.

b. Type a new start time in hh:mm:ss format. Make sure the new start time corresponds to an interval with a low count value, as shown on the Probe Distribution panel.

c. If you also want to change the stop time or interval in which the probe collects data, tab to the respective field and change the value.

d. Press Enter to save the new values.

Result: The start time for the probe you selected is changed, and the Probes in a Time Period panel is redisplayed.

6 Continue the process described in Step 4 until you have redistributed all the probes you want to in that interval.



7 To redistribute probes in other intervals, back out to the Balance Display by pressing the Cancel key and repeat steps 3 through 5.

8 To exit from the Probe Balancer, press the Cancel key until you have backed out to the main panel.



Notification Operational Features 225

Notification Operational Features

OverviewThis chapter describes the activities you perform to receive an incident notification, to resolve an incident, and to escalate an incident. It also describes procedures performed to reset incident numbering and to update changes made to the notification setup and assignment while a system is running.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Receiving Notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Resolving Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Escalating Incidents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Refreshing Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

11

Introduction


Introduction

DescriptionThe OSM/MVS notification system contains operational features that allow you to receive, resolve, and escalate incidents, and refresh changes you make to your notification setup. All of these operations are performed from the Controls pull-down on the OSM/MVS main panel.

RequirementYou can receive, respond to, or escalate incidents only if you have been defined as a notification user. (See “Notification” on page 91.)


Receiving Notification


IntroductionIf notification has been set up for a status for a monitored item, when the status changes, OSM/MVS notifies you by sending you an incident message. If the notification is sent to your TSO session terminal, the following incident notification is displayed:

Please Respond to id Probe: number -item-name notification-text

The notification text will vary depending on the cause of the incident notification.

For example:

Please Respond to G_00004 Probe: 031 -CICS_ETE_RESP_B End toend response on B poor.

If the notification is sent to a pager, the following incident ID is displayed instead:

sysid_incident-number

For example:

G_00004

When you are notified that an incident has occurred, you can receive the notification. Receiving the notification means you acknowledge receipt of it and confirm that you are working on it. Receiving the notification prevents it from being escalated.

Procedure for receiving an incidentUse the following procedure to confirm receipt of an incident and prevent its escalation:

Step Action

1 Select Receive Notification... from the Controls pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Receive Notification panel.

+-------------------------------------------------------------+| Help ||-------------------------------------------------------------|| OSM/MVS - Receive Notification || || Input System and Incident Number to receive and press || Enter. || || User ID . . . . . . TDEV48 || System . . . . . . . ________ + || Incident Number . . _____ || || F1=Help F4=Prompt F10=ActBar F12=Cancel |+-------------------------------------------------------------+

The panel displays your User ID.



2 Type the ID of the system the incident occurred on as displayed on your terminal or pager or as listed in the notification log.

3 Tab to the Incident Number field and type the number of the incident as displayed on your terminal or pager, or as listed in the notification log. Press Enter. You can omit any leading zeros when typing the number.

Result: OSM/MVS displays a confirmation message, removes the Receive Notification panel, prevents escalation of the incident to the next user in the notification chain, and makes an appropriate entry in the notification log.

OSM/MVS also displays a message at your terminal verifying that you have received the incident and marks you as busy. Whether you receive additional notifications about this status item until it is resolved will depend on the incident priority assigned to the status for this incident (see “Notification” on page 91).


Resolving Incidents

Resolving Incidents

IntroductionAfter appropriate action has been taken, you can resolve an incident that you have received, which will remove it from the system and cause an entry to be written into the notification log. To do so, use the Resolve Incident... selection on the Controls pull-down.

If you receive notification but fail to complete the Resolve Incident panel, OSM/MVS automatically resolves the incident after a preset amount of time (see “Notification” on page 91). OSM/MVS closes the incident and notes that the incident has been closed in the notification log.

Procedure for resolving an incidentUse the following procedure to resolve an incident:

Step Action

1 Select Resolve Incident... from the Controls pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Resolve Incident panel.+-------------------------------------------------------------+| Help ||-------------------------------------------------------------|| OSM/MVS - Resolve Incident || || Input System and Incident Number to resolve and press || Enter. || || User ID . . . . . . TDEV48 || System . . . . . . . ________ + || Incident Number . . _____ || || F1=Help F4=Prompt F10=ActBar F12=Cancel |+-------------------------------------------------------------+


2 Type the ID of the system the incident occurred on as displayed on your terminal or pager, or as listed in the notification log.

3 Tab to the Incident Number field and type the number of the incident as displayed on your terminal or pager, or as listed in the notification log. You can omit any leading zeros when typing the number. Press Enter.

Result: OSM/MVS closes the incident, removes the busy status from any user who has received the incident notification, displays a confirmation message, removes the Resolve Incident panel, and makes an appropriate entry in the notification log.

Escalating Incidents


Escalating Incidents

IntroductionIf you are a user in a notification chain, you have a preset amount of time to act on the incident before it is forwarded to the next user. The process of forwarding incidents to the next person along the chain is called escalating the incident.

Procedure for escalating incidentsUse the following procedure if you cannot resolve the incident and wish to pass it to the next person in the notification chain.

Step Action

1 Select Escalate Incident... from the Controls pull-down on the OSM/MVS main panel.

Result: The Escalate Incident panel is displayed.

+-------------------------------------------------------------+| Help |+-------------------------------------------------------------+| OSM/MVS - Escalate Incident || || Input System and Incident Number to escalate and press || Enter. || || User ID . . . . . . TDEV48 || System . . . . . . . ________ + || Incident Number . . _____ || Recycle Notify List (Y/N) __ || || F1=Help F4=Prompt F10=ActBar F12=Cancel |+-------------------------------------------------------------+


2 Type the ID of the system the incident occurred on as displayed on your terminal or pager, or as listed in the notification log.

3 Tab to the Incident Number field, and type the number of the incident as displayed on your terminal or pager, or as listed in the notification log. Press Enter.

Result: OSM/MVS displays a confirmation message, removes the Escalate Incident panel, removes the busy status from any user who has received the incident message, sends the incident message to the next person on the notification chain, and makes an appropriate entry in the notification log.

4 Enter Y to recycle the notify list if every individual on the list has been notified. Enter N if the list is not to be recycled.

This field is only examined if OSM/MVS has reached the end of the Notify chain. Otherwise, it is ignored.


Refreshing Notification


IntroductionYou can change notification information in a system that is running over a sustained period (generally, 24 hours a day, 7 days a week) using the Notification Refresh panel.

When you press Enter, OSM/MVS reloads all notification user, notification group, and rotation list information, and implements any default preferences you have changed. The system does not need to be brought down to load the new and changed data.

Procedure for refreshing notification

Step Action

1 Select Refresh Notification... from the Controls pull-down on the OSM/MVS main panel.

Result: OSM/MVS displays the Notification Refresh panel.

2 In the Originating Refresh System field, specify the OSM/MVS system where the notification refresh request will be issued. Once the designated OSM/MVS accepts the command, it will reload the notification and preferences tables. It will also send a notification refresh request to the other OSM/MVS systems with whom the designated OSM/MVS can communicate (via peer-to-peer link).

The originating refresh system must be an OSM/MVS system running under the local MVS system. If the originating refresh system is not active, the notification refresh request will not be serviced.

3 Type Y in the Refresh Confirmation field to confirm the request to reload notification and preference tables.

4 Press Enter.

Result: OSM/MVS reloads the notification tables and removes the Notification Refresh panel.

Help ----------------------------------------------------------------------- OSM/MVS - Notification Refresh Fill in the input fields to refresh notification and preferences tables press Enter. Originating Refresh System . . ________ + Refresh Confirmation . . . . . N (Y or N) F1=Help F4=Prompt F12=Cancel



Section IV. Developing an Availability Management Application 233

Section IV. Developing an Availability Management Application

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Monitoring for Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Monitoring for the Data Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Setting Up Distributed Systems Monitoring . . . . . . . . . . . . . . . . . . . . . . . 287Building an Interface with OMEGAVIEW . . . . . . . . . . . . . . . . . . . . . . . . 301


Introduction 235

Introduction

OverviewThis chapter and those that follow present a case study that demonstrates how to build an application with OSM/MVS.

Chapter ContentsIntroducing the Case Study. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Case Study: Building a Sample Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

12

Introducing the Case Study


Introducing the Case Study

About the case studyThe case study covers these tasks:

n modifying and adding probes

n setting recommendation and action exception flags to notify operators when an event occurs

n modifying and adding status items to a probe

n creating a situation and linking it to a status light

n working with DAS, which lets you retrieve data from and post the status of distributed systems

n building an application interface with and displaying status items in OMEGAVIEW

Additional informationIf you want more specific information on the REXX code underlying an OSM/MVS probe, see “Writing a Probe” on page 315. This information is useful if you plan to extensively modify or write your own probes.

Introduction 237

Case Study: Building a Sample Application


BackgroundGreat Southern Financial is a medium-sized company whose MVS installation includes two IBM 3090s™ and several RS6000 workstations. Its data center is using OMEGAMONs for CICS, MVS, and VTAM to monitor system performance.

The company’s management is working on a plan to reduce downtime and increase cost-effectiveness by simplifying data center operations. Part of this plan entails building an application that centralizes performance monitoring, posting system status directly to key departments and staff.

To test this idea, management assigns a task force to develop a prototype application. The application would post system availability for customer support, data center staff, and field sales operations. Each of the 3 types of user has different interests.

n Customer support staff use TSO to log information management reports. Management wants to know:

– whether systems critical to department functioning are operational

– whether service level agreements for response time are being met

– whom to notify in case of a problem

n Systems management staff want to know whether a system is experiencing problems and, if so, whether an automation routine can handle the problem. They also want to view systems for customer support and field sales to make sure those systems are operational and have satisfactory availability.

n Sales staff in remote locations use an RS6000 connected by modem to a PC in the home office. That PC runs a copy of OG/OS2 or AF/REMOTE and communicates with the mainframe, on which OSM/MVS is running. The field sales staff uses this distributed RS6000 to perform their sales transactions. Management needs to know whether or not this RS6000 is operational so that all sales information is up-to-the-minute.

Problem resolutionHere's what you will accomplish by the end of the case study:

n set up the internal monitoring system and connect it to the OMEGAVIEW panels. This includes probes for such components as:

– the response times and rates of various subsystems

– the number of TSO users

– data from the DAS

n use OMEGAVIEW to set up panels so that customer support, field sales management, and systems management staff can view the information they want.



Prototype applicationThe sample application you will build uses four linked panels. One functions as a navigation tool; the others display data collected by the probes.

The main panel contains pushbuttons for the three user categories: Customer Support, systems management staff, and field office sales. Activating a pushbutton takes you to a screen displaying the principal status items for the labeled user category.

User interface and linksThe following diagram shows the sample application user interface and the links between panels. This represents the application front end that you will build with OMEGAVIEW.

OSM/MVS components for a status itemThe diagram below shows an example of the OSM/MVS components underlying a single status item (TSO Response Time).

From the main panel, the status item for TSO response time requests information from MVS. To obtain this data, the status item must go through its host probe and then through the MVS Data Manager, which gathers information from OMEGAMON for MVS. When the status item

Introduction 239


reports that TSO response time is high, an activity is initiated, which sends a message to an operator.

Gathering data for a status itemOnce you decide which information you want to monitor, you must perform the following steps for each status item:

n Use the probe manager to select the probe that monitors the type of information you want. To do so, you may have to copy a probe or modify an existing one.

n Determine whether that probe is associated with a data manager or whether you must go directly to the source for data.

n Use the status manager to select the status item that monitors for the specific information you want. (Each probe can have many status items. Each status item uses a particular piece of information from the probe.)

n Determine whether you want a message, WTO, or routine to start once the status item has reported a specific condition.

Procedure overviewBuilding the sample application for this case study consists of the following four phases:

n Gathering TSO response time data. Gather response time data to display availability for Customer Support. Send a message to the console and activate an action routine when a status change occurs. (“Monitoring for Customer Support” on page 241.)

n Creating a situation to represent system status. Combine two indicators of system performance into a single status item (situation) for systems management staff. (“Monitoring for the Data Center” on page 265.)



n Monitoring a distributed RS6000. Use the DAS to monitor the status of the field sales office RS600. (“Setting Up Distributed Systems Monitoring” on page 287.)

n Building the interface. Create and link OMEGAVIEW panels for visual display of data gathered by OSM/MVS. (“Building an Interface with OMEGAVIEW” on page 301.)

If you do not want to try all four phases, you can choose any of the first three (to create one or more status items), plus phase 4 (to build the OMEGAVIEW panel for status display).

Sequence of building an AMSWhen building an Availability Management System (AMS) application, Candle recommends that you begin by using OMEGAVIEW as a prototyping tool. You can use OMEGAVIEW to build high-level screens, and add some roll-up status items to view what the application would look like.

After you have mapped out your AMS application, and know which probes and status items you want to use, the next step is building the OSM/MVS probes and status items. It is somewhat more efficient to build the probes and status items before building the actual (as opposed to the prototype) OMEGAVIEW panels. Those status items are then available for use after you log on to OMEGAVIEW.

Configuration informationThe panels shown throughout the case study contain example configuration data. You will need to change some of the supplied values to suit your own system setup. For example, a panel may refer to a System B and Domain R1, which may not exist at your site.

Use the table below as a guide and worksheet to convert any values used in the case study to values that are valid on your system. For complete information on OSM/MVS supplied values that you may need to change, see the OMEGACENTER Gateway for MVS Configuration and Customization Guide.

In addition, before walking through the case study, you will want to give some thought to preselecting the appropriate entities -- such as the probes, status items, and action routines -- to use.

Field Name Supplied Value Your Value...

System ID B

Domain ID B

Distributed System S1

Monitoring for Customer Support 241

Monitoring for Customer Support

OverviewThis chapter shows how to use OSM/MVS to check for system availability for Customer Support. It details the steps needed to set up a probe, attach a status item, start an action routine, and send a message to the operator when a change in status occurs.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Modifying the MVS Data Manager Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Setting Thresholds for the Response Time Status Item . . . . . . . . . . . . . . . . . . . . . . . . . . 246Using the Probe Directive, Probe Input and Misc. Parms Fields . . . . . . . . . . . . . . . . . . . . 248Specifying an Action Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Creating a Recommendation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Sending a Recommendation to the Operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

13

Introduction


Introduction

BackgroundSurveys have shown that quick Information Management processing is critical to staff productivity and customer satisfaction. To maintain high levels of both, Customer Support wants to ensure that the Information Management processing system, running under TSO, is always operating at top efficiency.

In this case study, Customer Support wants to monitor TSO response and initiate different actions depending on the level of performance. When poor response occurs, Customer Support wants the operator to hold all large jobs. For a more critical situation where response time is very high, Customer Support wants an action routine initiated that performs functions that improve response.

Using OSM/MVS to monitor TSO responseTo accomplish Customer Support’s goals using OSM/MVS, you will perform the following steps.

1. Modify the MVS Data Manager probe to monitor period 1 TSO response time for a performance group containing those TSO IDs for Customer Support. Also, specify the appropriate OMEGAMON to monitor during a specific time period.

2. Choose a status item and set thresholds for acceptable response and critical response.3. Identify the action routine that will start when response time reaches the critical threshold.4. Create a recommendation message to send to the operator requesting that all large jobs

be held.5. Specify that the recommendation message be sent to the operator when response time

reaches the warning threshold.


Modifying the MVS Data Manager Probe


IntroductionOSM/MVS provides a Data Manager probe that monitors MVS. You need to customize this probe to suit your requirements. Use the Probe Manager to modify the probe to specify:

n the schedule for monitoring TSO response time

n the OMEGAMON that will gather the data

ProcedureFollow these steps to customize the MVS data manager probe.

Step Action

1 Select Probe Manager... from the Managers pull-down on the OSM/MVS panel to display the Probe Manager panel.

2 Type M (to modify) in the entry field next to OMEGAMON/MVS Data Manager (B) with probe ID B01 and press Enter.

Result: The Modify a Probe panel appears.

+------------------------------ Modify A Probe ------------------------------+| OSM/MVS - Probe Manager || || When you have finished making changes, press Enter. || || Probe ID . . . : B01 || System ID . . : B Development System - B || Domain ID . . : B Development System - B || Probe Type . . : D OMEGAMON Data Manager || || Calendar . . . . ______________ || Description . . OMEGAMON/MVS Data Manager (B) || Program Name . . KATRAM01 || Activate Probe . Y (Y/N) || || F1=Help F12=Cancel |+----------------------------------------------------------------------------+



3 On the Modify a Probe panel, verify that a Y appears in the Activate Probe field and press Enter.

Result: The Data Manager panel appears.+----------------------- Data Manager ------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Start Time . . . . 00:00:00 (hh:mm:ss) || Stop Time . . . . 02:00:00 (hh:mm:ss) || Time Interval . . . 120 (Seconds) || || VTAM Session Name . OMV2 + | | Use Command Delay . _ (Y|N) || Statistics Log . . N + || Dependent Probes . 006_____ 007_____ 008_____ 009_____ || 055_____ 056_____ ________ ________ || ________ ________ || || F1=Help F4=Prompt F12=Cancel |+-------------------------------------------------------------+

4 On the Data Manager panel, tab to the Start Time field and type 08:00:00 to begin monitoring at 8:00 a.m.

5 Tab to the Stop Time field and type 18:00:00 to end monitoring at 6:00 p.m.

6 Tab to the Time Interval field and type 180 to monitor every 3 minutes.

7 Tab to the VTAM Session Name field and press the Prompt key. Select OMV2 to use OMEGAMON for MVS on system B by typing S (to select) in the entry field. Press Enter.

8 Verify that probe 055 appears in the Dependent Probes field. The completed panel should now appear as follows:+----------------------- Data Manager ------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Start Time . . . . 08:00:00 (hh:mm:ss) || Stop Time . . . . 18:00:00 (hh:mm:ss) || Time Interval . . . 180 (Seconds) || || VTAM Session Name . OMV2 + || Statistics Log . . _ + || Dependent Probes . 006 007 008 009 || 055 056 ________ ________ || ________ ________ || || F1=Help F4=Prompt F12=Cancel |+-------------------------------------------------------------+

Press Enter and then the Exit key.

Result: The MVS Data Manager Probe will monitor TSO response time every 3 minutes (180 seconds) from 8:00 a.m. to 6:00 p.m. via an OMEGAMON identified as OMV2.



GuidelinesProbes 055 and 056, which appear in the Dependent Probes field, are supplied with OSM/MVS. These probes are dependent on the Data Manager probe to gather information from an OMEGAMON. Only after the information has passed from the OMEGAMON to the Data Manager probe can the dependent probe gather the information and begin monitoring.

You can develop new dependent probes using REXX and add them to a data manager probe. Creating probes is described in “Writing a Probe” on page 315.

Setting Thresholds for the Response Time Status Item



IntroductionOSM/MVS provides a status item for the Candle-supplied probe that monitors TSO Response Time. (The ID for that probe is 055 at install time. It may be different if the probe was later modified.) The status item is set up so that it monitors specifically for response time for performance group 210 on system B for period 1. You will use the Status Manager to set the thresholds for the status item so that when TSO response meets or exceeds those values, the status bar on the OMEGAVIEW panel changes color.

ProcedureFollow these steps to set thresholds for the response time status item.

Step Action


2 Enter M (to modify) in the entry field of TSO_B_RESP_GRP_210 with probe ID 055. Press Enter.

Result: The Modify Status Item panel appears.+------------------------- Modify Status Item --------------------------+| OSM/MVS - Status Manager || || After you have made your changes, press Enter. || || Probe ID . . . . . : 055 TSO Response Time || System ID . . . . : B || Domain ID . . . . : B || Status Item . . . : TSO_G_RESP_GRP_210 || || Description . . . . TSO Response Time for Grp 210, period 1 || Default Status . . . NONE + || Threshold OK . . . . _ || Threshold Critical _ || Spikes Check . . . . N (Y/N) || Log Status Change _ + || OMEGAVIEW Text Type Transient Text + || Probe Input . . . . ________ + || Probe Directive . . 210 || Misc. Parms . . . . 1 || ** Row displayed || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+

3 Tab to the Threshold OK field and type 1.

4 Tab to the Threshold Critical field and type 4.



GuidelinesThe Description field describes the activity that you want to measure. In this case, the description states that OSM/MVS monitors TSO response time for period 1, which includes actions with the fastest response time, in performance group 210 on system B. Performance group 210 contains TSO IDs for Customer Support staff.

TSO categorizes transactions into four periods based on the complexity of each transaction. Period 1 contains the quickest, most efficient transactions, and period 4 contains the slowest, lowest priority transactions. When you monitor response time, you can specify which period you want to monitor.

In this case study, we assume the service-level objectives are 1 and 4 for the thresholds. When you actually use the probe, the settings will vary according to the service-level objectives at your site.

5 Press Enter and then the Exit key.

+------------------------- Modify Status Item --------------------------+| OSM/MVS - Status Manager || || After you have made your changes, press Enter. || || Probe ID . . . . . : 055 TSO Response Time || System ID . . . . : B || Domain ID . . . . : B || Status Item . . . : TSO_G_RESP_GRP_210 || || Description . . . . TSO Response Time for Grp 210, period 1 || Default Status . . . NONE + || Threshold OK . . . . 1 || Threshold Critical 4 || Spikes Check . . . . N (Y/N) || Log Status Change _ + || OMEGAVIEW Text Type Transient Text + || Probe Input . . . . ________ + || Probe Directive . . 210 || Misc. Parms . . . . 1 || || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+

Result: You have modified the TSO response time status item so that the OMEGAVIEW status bar turnsn green when the response is 1 second or lessn yellow when response time is between 1 and 4 secondsn red when TSO response time is 4 seconds or greater

Using the Probe Directive, Probe Input and Misc. Parms Fields



IntroductionYou can use the Probe Directive, Probe Input, or the Misc. Parms fields to pass information to a probe as follows:

n Use the Probe Directive field to pass information to a Q or H probe. In this example, the performance group number 210 is passed to the probe in the Probe Directive field.

n Use the Probe Input field to pass information to a DP, EM or QM probe. The Probe Input field is not used in this example. (For more information on using this field, see Passing information to a DP, EM, or QM probe, below.)

n Use the Misc. Parms field to pass information to a probe looking for special parameter values. In this example, periods are specified in the Misc. Parms field. The 1 indicates that period 1, which contains the most simple transactions, is monitored.

OMEGAMON Exception (EO) probe status items can also use the Misc. Parms field to monitor various exceptions with greater accuracy. Refer to “Monitoring EO Exceptions” on page 251 for details.

Passing information to a DP, EM, or QM probeWhile DP, EM and QM probes are not used in this case study, this subsection describes how you can use the Probe Input field on a status item panel to pass information to a DP, EM or QM probe.

Assume that a Probe Input value for a status item associated with probe DP000001 has already been defined. You want to:

n locate the correct status item

n modify the Probe Input field value

Follow these steps to modify the status item:

Step Action




2 Type > (to show dependent status items for the probe) in the entry field next to the first occurrence of DP000001 and press Enter.

Result: The Status Manager panel appears listing the dependent status items.

3 Type M (to modify) in the entry field next to a Status Item name and press Enter. For this example, PS_TEST_DP_1 will be used.

Result: The Modify Status Item panel appears.

+------------------------- Modify Status Item -------------------------+ | OSM/MVS - Status Manager | | | | After you have made your changes, press Enter. | | | | Probe ID . . . . . : DP000001 test dp probe | | System ID . . . . : G | | Domain ID . . . . : G | | Status Item . . . : PS_TEST_DP_1 | | | | Description . . . . test dp probe | | Default Status . . . NONE + | | Threshold OK . . . . 30 | | Threshold Critical 60 | | Spikes Check . . . . N (Y/N) | | Log Status Change _ + | | OMEGAVIEW Text Type Transient Text + | | Probe Input . . . . DP000001 + | | Probe Directive . . ________________________________________ | | Misc. Parms . . . . ________________________________________ | | F1=Help F4=Prompt F12=Cancel | +----------------------------------------------------------------------+

Actions View Managers Help -------------------------------------------------------------------------- OSM/MVS - Status Manager ROW 88 FROM 296 Select a row and press Enter. Actions are (A)dd, (C)opy, (D)elete, (F)ind (R)efresh, (M)odify Status Item, Modify Critica(L), (W)arning, (O)K, and (N)one Activities. Dependent status items for probe: DP000001 G G -------------------------------------------------------------------------- Probe Status Item Name Description System Domain_ DP000001 GS_TEST_DP_1 test dp probe G G_ DP000001 LH_TEST_DP_1 test dp probe G G_ DP000001 PS_TEST_DP_1 test dp probe G G_ DP000001 ZZ_TEST_DP_1 test dp probe G G*************************** BOTTOM OF DATA ******************************** Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



The procedure is the same for EM and QM probes. Only the last panel -- the input panel -- will be different.

4 Move the cursor into the Probe Input field and press the Prompt key.

Result: The OSM Input List panel appears.+------------------------------ OSM Input List ------------------------------+º Actions |º ---------------------------------------------------------------------- |º OSM/MVS - Input Manager ROW 3 FROM 4 |º || (S)elect a row, (A)dd a row or (M)odify row. || || || --------------------------------------------------------------------- || ID Input Description || _ DP000002 STCJ command || _ DP000001 TSOJ command || ***************************** BOTTOM OF DATA ***************************** || || || || || || || || || Command ===> _____________________________________________________________ || F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar |+----------------------------------------------------------------------------+

5 Type M next to the item to be modified. In this example, an M is typed next to Probe Input item DP000002.

Result: The Data Manager Dependent Probe Input panel is displayed.

+-------------------------- OSM Input Panel --------------------------+ | OSM/MVS - Data Manager Dependent Probe Input | | | | Enter the OMEGAMON commands in the sequence of execution. | | | | Probe Input ID . . . DP000002 | | Description . . . . STCJ command | | OMEGAMON CMD 1 . . . #STCJ | | OMEGAMON CMD 2 . . . ____________________ | | OMEGAMON CMD 3 . . . ____________________ | | OMEGAMON CMD 4 . . . ____________________ | | OMEGAMON CMD 5 . . . ____________________ | | OMEGAMON CMD 6 . . . ____________________ | | OMEGAMON CMD 7 . . . ____________________ | | OMEGAMON CMD 8 . . . ____________________ | | OMEGAMON CMD 9 . . . ____________________ | | OMEGAMON CMD 10 . . ____________________ | | OMEGAMON CMD 11 . . ____________________ | | OMEGAMON CMD 12 . . ____________________ | | OMEGAMON CMD 13 . . ____________________ | | OMEGAMON CMD 14 . . ____________________ | | OMEGAMON CMD 15 . . ____________________ | | F1=Help F4=Prompt F12=Cancel | +---------------------------------------------------------------------+

You can now change the OMEGAMON commands or add additional ones.



That is, for an EM probe, an Exception Input panel like the following is displayed on which to identify WTO or command trap patterns and jobs to execute if the trap pattern is matched.

For a QM probe, a Query Probe Input panel like the following is displayed on which to enter an MVS command.

Monitoring EO ExceptionsThis section provides details of how to perform monitoring using an EO-type probe using the OMEGAMON/IMS NTIQ exception as an example. The NTIQ exception is used to detect the situation in which a noncompeting IMS transaction depth is greater than n. This same technique can be used for any of the OMEGAMON exceptions.

+------------------------------ OSM Input Panel -------------------------+| OSM/MVS - EM Probe Exception Input || || Enter the WTO or COMMAND TRAP PATTERNS. || || Probe Input ID . . . EM000001 || Description . . . . Test em probe || Event Type . . . . . W +(W - WTO/WTOR C - COMMAND) || Pattern 1 $HASP373* || ____________________________________________________________ || Pattern 2 IEF450I* || ____________________________________________________________ || Pattern 3 HASP395* || ____________________________________________________________ || + (Valid Trap Patterns cannot exceed 128 chars.) || Jobname . PSEDMAA + (Optional - Will be applied to all traps.) || || || || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------------+

+------------------------------ OSM Input Panel ------------------------+| OSM/MVS - Query Probe Input || || Enter the query command. || || Probe Input ID . . . QM000001 || || Description . . . . Display that tdafs01 is active || || MVS Cmd . D A,tdafs01 || || || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+



By default, OSM only triggers a WARNING or CRITICAL event when the exception is first raised and does not trigger an OK event to indicate that the problem has been resolved until the last instance of the exception has gone. That is, if IMS transaction TRAN1 starts queueing at time1 and IMS transaction TRAN2 starts queueing at time2, and both stop queueing at time3, you will only be notified of the first occurrence of the NTIQ excepotion at time 1 and notified again at time3 when the problem has been resolved. You will not know that TRAN2 had a queueing problem. You can resolve this situation by forcing the probe program to issue a WTO whenever an exception arrives and a corresponding WTO when each instance of an exception has been resolved.

Updating a status item with a correlation value

In order to detect when queueing for an IMS transaction is relieved, you must add some text to the Misc. Parms field of the status item. To be notified when queueing is relieved for each instance of a transaction, add the following text to the Misc. Parms field for the NTIQ status item:

CORR(w9)

This tells the probe program that it is to set up a trap that triggers when an instance of the NTIQ exception is resolved. CORR(W9) for the NTIQ exception informs the probe program that a trap is required to be added that contains NTIQ and the value in word 9 of the exception text.

Following are two example NTIQ exceptions:

+ NTIQ Input Queue length for Non-competing transaction ‘PART’=2+ NTIQ Input Queue length for Non-competing transaction ‘IVTNO’=5

Specifying CORR(W9) indicates that correlation is to occur on word 9 of the text. This resultant traps that are set up have names consisting of an exception name and the text that appears in word 9 of the NTIQ exception. For the two NTIQ exceptions above, the trap names would be @Tyyyy1TPART and @Tyyyy2TIVTNO, where yyyy is the probe name. Thus, if both the PART and IVTNO transactions are queueing, there will be two traps for the NTIQ exception. When the NTIQ for the PART transaction is resolved, the @Tyyyy1TPART TRAP expires and causes a WTO to be issued indicating the problem has been resolved. However, the @Tyyyy2TIVTNO TRAP continues in effect.

Example Misc. Parms values

The correlation keyword is always CORR(value), where value is specified in terms of word numbers (for example, W1, W2, W3) and/or starting position and number of characters (for example, P1-1, P30-4). Here are some other examples:

CORR(W9) correlates on word 9 of the exception data

CORR(P1-1) correlates on position 1 of the exception data

CORR(P30-4) correlates on positions 30-33 of the exception data

CORR(W8,P26-4) corrrelates on word 8 concatenated with positions 26-29 of the exception data



Example: Creating a probe with correlation data

The following example steps through what is required to add an EO-type probe that has a status item to monitor the NTIQ exception. It then steps through what is required within IMS to cause the NTIQ exception to trip and the WTO(s) to be issued.

1. Add a probe.

+------------------------------ Add a Probe ----------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Probe ID . . . SYSGIMSA || System ID . . SYSGA250 + SYSG - STC S9GBOG1 || Domain ID . . SYSGA250 + SYSG - STC S9GBOG1 || Probe Type . . EO + || || Calendar . . . ____________ + || Description . OM/IMS Exceptions for IMSA on SYSG || Program Name . OIMEOPROG + || |+-----------------------------------------------------------------------+

+------------------------------ OMEGAMON Event -------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Start Time . . . 00:00:00 (hh:mm:ss) || Stop Time . . . _________ (hh:mm:ss) || Time Interval. . _________ (seconds) || || VTAM Session Name OMOISYSG + || |+-----------------------------------------------------------------------+



2. Add a status item for NTIQ exception.

+------------------------------ Add Status Item ---------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . SYSGIMSA OM/IMS Exceptions for IMSA on SYSG || System ID . . . SYSGA250 || Domain ID . . . SYSGA250 || Status Item . . IMSA.NTIO || || Description . . . NTIO Exception on IMSA_________ || Default Status . . OK_______ + || Threshold OK . . . NO________________ || Threshold Critical YES_______________ || Spikes Check . . . N (Y/N) || Log Status Change. _ + || OMEGAVIEW Text Type Transient Text __ + || Input Parms . . . _________ || Probe Directive . . _______________________________ || Misc. Parms . . . CORR(W9)____________________ || Managed System Name _________ + || || **Row displayed |+--------------------------------------------------------------------------+

+------------ Add OMEGAMON Exception Environment --------------------------+| OSM/MVS - EO Probe Exception Input || || Enter the following Exception Information. || || EO Probe Name. . . . . . . . . .: SYSGIMSA || Domain . . . . . . . . . . . . .: SYSGA250 || System . . . . . . . . . . . . .: SYSGA250 || OMEGAMON APPLID . . . . . . . .: OMOISYSG || || OMEGAMON Exception . . . . . . . NTIQ || Exception Threshold . . . . . . 2 ___ || Additional Parameters . . . . . _______________ || Description . . . . . . . . . . _____________________________ || || Timeout Value . . . . . . . . . _______ || |+--------------------------------------------------------------------------+



3. Modify the probe program that OSM builds for you. In the Process_Event subroutine shown below, add the line to exec WTOGEN.

Process_Event:

attribute_value = ‘YES’ /*@005*/ if correlator = ‘YES’ then /*@005*/ temp_status_item = status_item || corrval /*@005*/ else /*@005*/ temp_status_item = status_item /*@005*/ Call Set_Timeout_Trap /*@005*/ rc = wtogen(‘ ‘, ‘ ‘, temp_status_item, ‘RED’, ‘ ‘, ‘ ‘, ‘ ‘)

Return attribute_value

This runs a REXX program called WTOGEN that issues a WTO. An alternative to modifying the Process_Event subroutine is to add code that issues the WTO verb with the required text that you want to display using the WTO. This is the only modification to the probe program.

4. Activate the probe.

5. Following is the result of a SH TRAPS(@TSYSGIMSA*) coimmand to show the trap that has been created.

SH TRAPS (@TSYSGIMSA*)!AOP0210 --- LIST OF ALL WTO CMD TOD XOM XOC XOI XO2 DOM TRAPS ---!AOP0201 ENABLED @TSYSGIMSA1E XOI(‘+ NTIQ *’) COUNT(2!AOP0201 ------ JOBTYPE(*) JOBNAME() JOBCLASS(‘*’)SYSID(SYSG) LINKID(*) NEWS!AOP0201 ------ CONTINUE ALLOW LOG NOTEST NORETAIN NOAOTRAP!AOP0201 ------ ACTION(‘EX KATRA995 ‘’SYSGA250,SYSGIMSA,OMEOPROG,IMSA.NTIQ’ ’ ’!AOP0201 ------ MATCHLIM(0) ALTACT(‘ ‘)!AOP0201 ------- USERID() DAYS()!AOP0201 ------- SESSION(OMOISYSG)!AOP0201 ------- JOURATTR(COLOR(),HIGHLIGHT(),INTENSITY()) JOURHELP()!AOP0208 1 ITEMS SHOWN

6. You now need to queue up an IMS transaction. This example is using class 66, which assumes you do not have any IMS message processing regions servicing class 66. If you do, select another class that is not being used by issuing the following commands to the IMS system you will be using:Using the IMS outstanding ID, issue command

/nnn/ass tran ivtno class 66

Using the outstanding ID, issue command

/nnnivtno a.

You will need to perform the above twice to get the NTIQ exception to trip, since it will monitor for a queue depth of 2.

7. You should now see the NTIQ WTO being issued to the SYSLOG. The WTO will be issued at the interval that has been defined for this OMEGAMON/IMS session. Following is an example of the WTO:

OSMALERT IMSA.NTIQPART RED 4 N N - NTIQ Input Queue length for Non-competing transaction PART = 2



8. The result of a SH TRAPS(@TSYSGIMSA*) command follows. This shows that another trap has been created. Note that a trap has been added to issue a WTO to indicate that the problem has gone away. This trap is only triggered when the problem has gone away.

SH TRAPS (@TSYSGIMSA*)!AOP0210 --- LIST OF ALL WTO CMD TOD XOM XOC XOI XO2 DOM TRAPS ---!AOP0201 ENABLED @TSYSGIMSA1TPART TOD(‘TIME=17:34:14 DATE=3/11/2002’) COUNT(0)!AOP0201 ------ SKIP LOG NOTEST NOCKPT!AOP0201 ------ACTION(‘wto ‘’OSMALERT IMSA.NTIQPART - PROBLEM HAS GONE AWAY’

!AOP0201 ------ TIME(17:34:14) DATE(03/11/2002) INTERVAL() LIMIT()!AOP0201 ------ MATCHLIM(0) ALTACT(‘ ‘)!AOP0201 ------- USERID() DAYS()!AOP0201 ENABLED @TSYSGIMSA1E XOI(‘+ NTIQ *’) COUNT(5)!AOP0201 ------- JOBTYPE(*) JOBNAME() JOBCLASS(“*”) SYSID(SYSG) LINKID(*) NEWS!AOP0201 ------- CONTINUE ALLOW LOG NOTEST NORETAIN NOAOTRAP!AOP0201 ------- ACTION(‘EX KATRA995 ‘’SYSGA250,SYSGIMSA,OMEOPROG,IMSA.NTIQ’ ‘ ‘ !AOP0201 ------- MATCHLIM(0) ALTACT(““)!AOP0201 ------- USRID() DAYS()!AOP0201 ------- SESSION(OMOISYSG)!AOP0201 ------- JOURATTR(COLOR(),HIGHLIGHT(),INTENSITY()) JOURHELP()!AOP0208 2 ITEMS SHOWN

9. You now need to queue up another IMS transaction. This example uses class 66, which assumes you do not have any message processing regions servicing class 66. If you do, select another class that is not being used by issuing the following commands to the IMS system you will be using:Using the IMS outstanding ID, issue command

/nnn/ass tran part class 66

Using the outstanding ID, issue command

/nnnpart a.

You will need to perform the above twice to get the NTIQ exception to trip for the PART transaction, since it will monitor for a queue depth of 2. At this point, there will be 1 PART and 1 IVTNO transaction queued, which will cause the NTIQ exception to trip twice on each polling interval.

10. You should now see 2 NTIQ WTOs being issued at the interval that has been defined for this OMEGAMON/IMS session. Following are examples of what the WTOs could look like:

OSMALERT IMSA.NTIQIVTNO RED 4 N N - NTIQ Input Queue length for Non-competing transaction IVTNO = 5

OSMALERT IMSA.NTIQPART RED 4 N N - NTIQ Input Queue length for Non-competing transaction PART = 2

11. You can then dequeue one of the IMS transactions and see the WTO issued that indicates the problem has gone away. This example is using class 1 which assumes you have a message processing region servicing class 1. If you do not, select another class that is being serviced by issuing the foillowing command to the IMS system you will be using. Using the IMS outstanding ID, issue command

/nnn/ass tran ivtno class 1



12. The following WTO will be issued to the SYSLOG:OSMALERT IMSA.NTIQIVTNO - PROBLEM HAS GONE AWAY

Specifying an Action Routine



IntroductionYou can direct OSM/MVS to automatically invoke a routine that addresses TSO response time problems when TSO response time reaches critical status. An action routine is a program that starts an event based on information obtained by a probe, such as sending out a broadcast message. The routine will also write a message to the OMEGACENTER log so that you know when and under what conditions it was invoked.

ProcedureFollow these steps to set up an action routine.

Step Action


2 Scroll to the TSO_B_RESP_GRP_210 status item. Type L (for critical) in the entry field. Press Enter.

Result: The Modify Activity panel appears.+--------------------------- Modify Activity ---------------------------+| OSM/MVS - Activity || || S(elect) the Activities you wish to modify, and press Enter. || || Status Item TSO_B_RESP_GRP_210 Condition Critical || Probe ID . : 055 System ID : B Domain ID : B || ------------------------------------------------------------------ || _ Diagnosis and Log Data || _ Notification and Recommendation Data || _ Action, Follow-up, and Log Data || _ Work List Data || _ Exception List Data || || F1=Help F12=Cancel |+-----------------------------------------------------------------------+

3 On the above panel, tab to the Action, Follow-up, and Log Data entry field and type S (to select). Press Enter.

Result: The Modify Action, Follow-up and Log Data panel appears.+------------- Modify Action, Follow-up and Log Data --------------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item TSO_B_RESP_GRP_210 Condition Critical || Probe . . : 055 System ID. B Domain ID. B || ------------------------------------------------------------- || Action Routine . . ROUTINE1 (Leave blank for none) || Follow-up Routine ________ (Leave blank for none) || Log Code . . . . . _ + || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+



GuidelinesAt this point, you can update changes made to OSM/MVS by selecting either the probe or status item you have worked on with an R action code from a Managers display. However, we recommend you postpone refreshing. In the next section, you will add a recommendation message, which requires a global OSM/MVS refresh. A global refresh updates all changes made during a session.

4 Tab to the Action Routine field and type ROUTINE1. ROUTINE1 is an action routine that you developed in REXX and stored in REXXLIB. Press Enter.

Result: You have set up an action routine that is invoked when TSO response time is 4 seconds or more.

Creating a Recommendation



IntroductionIn this section, you use OSM/MVS to create and store a recommendation. The recommendation is sent to the operator when the condition that you specify–in this case study, poor TSO response–is met.

ProcedureFollow these steps for creating a recommendation.

Step Action


Result:The Recommendations panel appears. It displays codes and up to 3 lines of text for each message.

_ Actions Help-------------------------------------------------------------------------- OSM/MVS - Recommendations ROW 1 TO 11 OF 17 Select a row and press Enter. Valid actions are A(dd), M(odify) and D(elete). ------------------Recommendations------------------ Code Text _ 0000 This is the first recommendation. This is the second. This is the third. _ 0001 Review payroll operation menu. Contact application programmer. Restart batch job when problem is resolved. _ 0002 Reactivate VTAM node. Contact network system programmer. _ 0003 !!!!!!!!!!!!!!!!!! !!!!!! IPL !!!!! !!!!!!!!!!!!!!!!!! _ 0004 Response Time line 1 line2 line3 _ 0005 Remote RS6000 system is down. Restart if possible. Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar



2 On the Recommendations panel, type A (to add) in any entry field. Press Enter.

Result: The Add Recommendations panel is displayed.+----------------------- Add Recommendations ------------------------+| OSM/MVS - Recommendations || || Enter the required Recommendation Code and any additional text. || || Recommendation Code ____ || Text Field 1 . . . _____________________________________________ || Text Field 2 . . . _____________________________________________ || Text Field 3 . . . _____________________________________________ || || F1=Help F12=Cancel |+--------------------------------------------------------------------+

This panel lets you assign a unique number to the recommendation and enter 3 lines of text that will be displayed at the operator console.

3 On the Add Recommendations pop-up, type 0123 in the Recommendation Code field. (You can enter any unique message number.)

4 Tab to Text Field 1 and type Response time has reached warning level..

5 Tab to Text Field 2 and type Response time is between 1 and 4..

6 Tab to Text Field 3 and type Notify system administrator to hold large jobs..

The panel should now look like the one below:+------------------------ Add Recommendations -----------------------+| OSM/MVS - Recommendations || || Enter the required Recommendation Code and any additional text. || || Recommendation Code 0123 || Text Field 1 . . . Response time has reached warning level. || Text Field 2 . . . Response time is between 1 and 4. || Text Field 3 . . . Notify system administrator to hold large jobs.|| || F1=Help F12=Cancel |+--------------------------------------------------------------------+

7 Press Enter and then the Exit key.

Result: You have created a recommendation to send to an operator. Later, you will see how to link this message to a change in response time through the Status Manager.

Sending a Recommendation to the Operator


Sending a Recommendation to the Operator

IntroductionYou will now recommend that the operator take a specific action when TSO response time reaches the warning status. Using the recommendation message you created in “Creating a Recommendation” on page 260, you can have OSM/MVS notify the operator when an event occurs.

ProcedureFollow these steps to send a recommendation to the operator.

Step Action

1 From the Status Manager panel, tab to the entry field of the TSO_B_RESP_GRP_210 status item and type W (for warning). Press Enter.

Result: The Modify Activity panel appears.

2 On the Modify Activity panel, tab to the Notification and Recommendation Data field and type S (to select). Press Enter.

Result:The Modify Notification and Recommendation Data panel appears.+---------- Modify Notification and Recommendation Data -----------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item TSO_B_RESP_GRP_210 Condition Warning || Probe . . : 055 System ID. B Domain ID. B || ------------------------------------------------------------- || Notification Code ____ + || Notification Text ________________________________________ || Create Incident . N (Y or N) || Incident Priority Notify If Available + || Alternate Notification Program ALTPGM1 || ------------------------------------------------------------- || Recommendation Code . . . . . ____ + || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+

3 Tab to the Recommendation Code‘ field and press the Prompt key.

4 Page down to and select the code 0123. (Recommendation 0123 was created and stored in OSM/MVS using Setup, which is described in “Creating a Recommendation” on page 260.) Press Enter twice and then press the Exit key.

Result: When the response time is between 1 and 4 seconds, a message is sent to the operator asking that all large jobs be held.


Refreshing OSM/MVS

Refreshing OSM/MVS

IntroductionWhen you make changes to individual probes or status items, as in the first few sections, you can update OSM/MVS by refreshing the probe or any of its linked status items. However, since you also added a recommendation, you need to do a global OSM/MVS refresh. This type of refresh updates all changes made to OSM/MVS.

For more information on refreshing OSM/MVS, see “Updating OSM/MVS Data” on page 210. For information on refreshing notification changes, see“Refreshing Notification” on page 231.

ProcedureFollow these steps for refreshing OSM/MVS.

Step Action

1 Select Controls from the action bar.

Result: The Controls pull-down is displayed.+-------------------------------+| 2_ 1. Start OSM/MVS... || 2. Refresh OSM/MVS... || 3. Stop OSM/MVS... || 4. Refresh Notification... || 5. Receive Notification... || 6. Resolve Incident... || 7. Escalate Incident... || 8. Probe Balancer... || 9. Messages... || 10. Replication... || 11. Distribution... || 12. Exit (F3) |+-------------------------------+

Refreshing OSM/MVS


2 Type 2 and press Enter to select Refresh OSM/MVS.

Result: The Refresh OSM/MVS panel is displayed.

3 Type S beside each system you want to refresh and press Enter.

Result: OSM/MVS is refreshed on the systems that you selected.

Help -------------------------------------------------------------------------- Refresh OSM/MVS ROW 1 FROM 11 (S)elect a System and press ENTER. System SYSNAME Description _ B SYSB Development System B _ C SYSD Administration System C _ GO1PS SYSG Candle Development System-G _ SYSG3 SYSG Another toolkit for System-G _ H SYSH Development System H *************************** BOTTOM OF DATA ******************************* Command ===> _____________________________________________________________ F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar

Monitoring for the Data Center 265

Monitoring for the Data Center

OverviewThis chapter shows how to use OSM/MVS to monitor for the number of active users, CICS response time, and TSO response time. It details the steps needed to set up the probes, status items, situations, and activities to track and display the status.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Adding an Active Users Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Copying Source Code for the New Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271Adding a Status Item for User Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273Setting an Exception Flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Evaluating Two Conditions as One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280Adding a Status Item for a Situation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

14

Introduction


Introduction

BackgroundIn an ongoing quality improvement project, the Great Southern Financial data center continually evaluates system usage and performance. The data center staff is focusing on the number of active users, CICS response time, and TSO response time. Specifically, they want toOSM/MVS

n send a message to OMEGAVIEW when the number of active TSO users exceeds a predetermined number

n change an OMEGAVIEW status bar to red when CICS response time and TSO response time for performance group 210 on system B for period 1 exceed acceptable levels

Using OSM/MVS to monitor for the data centerTo accomplish the data center’s goals using OSM/MVS, you will do the followingOSM/MVS

1. Add a probe to OSM/MVS that checks the number of users.2. Add a status item to the probe and set the threshold values for warning number of users

(between 90 and 100) and critical number of users (over 100).3. Create an exception message that will be displayed in OMEGAVIEW when the number of

users reaches the critical threshold.4. Evaluate CICS response time and TSO response time as a single condition.5. Add a status item for the combined condition, a situation.


Adding an Active Users Probe


IntroductionA probe that monitors active users is available in PROBELIB, the library containing probe code samples. (See “PROBELIB Sample Probes” on page 331 for descriptions of these probes.) To add the active users probe and make it available for use, you need to:

n define a new probe with the Add a Probe panel

n copy the REXX source code from PROBELIB into the new probe's source file

n view the source file to see whether any code customization is necessary

ProcedureTo add a probe named MVS TSO User Count to REXXLIB, the OSM/MVS library, follow these steps:

Step Action


2 Type A (to add) on any of the entry fields and press Enter.

Result: The Add a Probe panel appears.+------------------------ Add A Probe ------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Probe ID . . . ________ || System ID . . . ________ + || Domain ID . . . ________ + || Probe Type . . . ___ + || Calendar . . . ________ + || || Description . . ________________________________________ || Program Name . . ________ + || || || F1=Help F4=Prompt F12=Cancel |+-------------------------------------------------------------+

3 On the Add A Probe panel, type 004 in the Probe ID field to add the MVS TSO User Count probe.

4 Enter B in both the System ID field and the Domain ID field.

Notes:

1. Specify the system on which the probe resides in the System ID field, and the system from which the probe is gathering data in the Domain ID field.

2. The values for these fields will vary depending on your system identifiers. Use ones that correspond to your system configuration. (See “Configuration information” on page 240.)

5 In the Probe Type field, enter Probe Type information.



6 In the Calendar field enter the optional desired Calendar name.

7 In the Description field, type MVS TSO user count.

8 In the Program Name field, type PRBBB004 and press Enter. (You may want to consider naming probe programs according to your site naming conventions.) The Probe Schedule panel appears only if you don’t select a Calendar. If you select a Calendar, the Schedule Definitions Panel (KATIASCL) appears.

Result: The Probe Schedule panel appears.+--------------- Probe Schedule ----------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Start Time . . . . 00:00:00 (hh:mm:ss) || Stop Time . . . . ________ (hh:mm:ss) || Time Interval . . 120 (Seconds) || || F1=Help F12=Cancel |+-----------------------------------------------+

9 On the Probe Schedule pop-up, type 06:00:00 in the Start Time field.

10 Type 17:00:00 in the Stop Time field.

11 Tab to the Time Interval field and type 180 to monitor every 180 seconds. Press Enter, so the OSM/MVS Assistant panel appears.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 5 OF 7 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Probe has been added, now select the Status Item || to build Status and Activity rows for the Probe. || || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item ** Add New ** Required || _ Act-WARNING ** Add New ** Not Availab || _ Act-OK ** Add New ** Not Availab || _ Act-NONE ** Add New ** Not Availab || _ Act-CRITICAL ** Add New ** Not Availab || ** Add completed successfully || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel || |+----------------------------------------------------------------------------+

Result: You have added a probe that monitors the number of active TSO users. The probe monitors between 6 a.m. and 5 p.m. After you add source code to the probe (covered in the next part of the case study), you will have a functioning active users probe.



Using the Calendar Function

Schedule Definition

Schedule definition allows you to create a number of Probe schedules dependent upon the Daytype. For example, if we assume business days are Monday through Friday, then we can define a schedule for business days. If you wish to run the Probe at different times on weekends, you can define a weekend daytype in the calendar, and add a definition in the schedule with the relevant window times.

Daytype definitions should be defined in a RANK order. This means that the more explicit the definition, the higher rank it should have.

The following panel allows you to define a probe schedule.

After defining a probe schedule, the next step is assigning values to the defined Daytypes. The following panel provides you with the means to assign details to the Daytypes assigned to probes.

+----------------------------------------------------------------------------------+| Actions Help |+----------------------------------------------------------------------------------+| KATIASCL OSM/MVS - Schedule Definitions Row 1 from 6 || || || Select a row and press Enter. Valid actions are (A)dd, (D)elete, and (M)odify. || || || Probe Name . . AOOMWAIT || || Caldendar . . NEWTESTCAL || || Order Day Name || || __ 1 BUS || ||*********************************Bottom of data***********************************|| ||Command===>________________________________________________________ || ||F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar |+----------------------------------------------------------------------------------+



Add Daytype Schedule

Each Daytype has up to five (5) Activity Windows available to it. This allows you to have Activity Windows on a Monday totally different from those on a Tuesday, Weekend day, or holiday.

In the above panel example, you will see that for the Daytype of WED there are 3 Activity Windows defined. However, it appears that 2 of them are incomplete.

If we study the second entry:

Start . . 12:00:00 Stop . . . 20:00:00 Int. 120

We can see that this probe starts at 12:00:00, stops at 20:00:00, and fires at 120 second intervals.

If we study the first entry:

Start . . ________ Stop . . . 02:00:00 Int. 240

In this example, we have a stop time and interval but no start time. This is a valid entry as long as it is the first entry in the Activity Window. This entry activates the probe at midnight and runs the probe thru to 02:00:00 firing at 240 second intervals.

If we look at the third entry:

Start . . 22:00:00 Stop . . . ________ Int. 360

+------------------------- Add Daytype Schedule -------------------------------+| || KATIAASC Add Daytype-Probe Manager || || Fill in up to five activity window details and assign to a Calendar Daytype || || Probe name . . AOOMWAIT || || Daytype . . . . WED + || || Order . . 1 (1-999) || || Start . . ________ Stop . . . 02:00:00 Int. 240 || || Start . . 12:00:00 Stop . . . 20:00:00 Int. 120 || || Start . . 22:00:00 Stop . . . ________ Int. 360 || || Start . . ________ Stop . . . ________ Int. ___ || || Start . . ________ Stop . . . ________ Int. ___ || || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------------------+

a


Copying Source Code for the New Probe

In this example, we have a start and an interval but no stop time. The absence of a stop time indicates that the probe should continue until midnight firing at 360 second intervals.

If we want our probe to run from midnight to midnight on a WED Daytype, then do not code a start and stop time but we do code an interval in Entry 1. This provides an ALWAYS ACTIVE capability at a Daytype level. Using the above example, probe AOOMWAIT can be always active on a Wednesday but scheduled totally differently on other BUS days.


IntroductionTo complete the addition of a probe, you must add the REXX source code. This part of the case study shows how to copy the code from PROBELIB into the active users probe.

For additional information, see “Writing a Probe” on page 315.

ProcedureFollow these steps to copy the REXX source code into the

active users probe.

Step Action

1 On the OSM/MVS Assistant panel, select Program with an S action code. (You may need to use the Fwd key to scroll to the Program row.) Press Enter.

Result: The REXX model code appears. You are now in ISPF, in Edit mode.

2 Using the ISPF editor, review and update the program as necessary.



3 When you are finished editing the source file, press the End key.

Result: The OSM/MVS Assistant panel appears. The entry in the Condition column for Program changes to Complete, indicating that you have viewed or modified the program code for the probe.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 6 TO 7 OF 7 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Probe has been added, now select the Status Item || to build Status and Activity rows for the Probe. || || ----------------------------------------------------------------------- || Type Name Condition || _ Program PRBBB004 Complete || _ Probe MVS TSO User Count Complete || ***************************** BOTTOM OF DATA ***************************** || || || || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+


Adding a Status Item for User Count


IntroductionNext, you add a status item to the MVS TSO User Count probe. When adding a new status item, you need to

n name the status item

n set the threshold values

n set any additional parameters

ProcedureFollow these steps to complete the Add Status Item panel.

Step Action

1 On the OSM/MVS Assistant panel, select Status Item for the MVS TSO User Count probe.

Result: The Add Status Item panel appears.+--------------------------- Add Status Item ---------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . . : 004 MVS TSO User Count || System ID . . . . : B || Domain ID . . . . : B || Status Item . . . . ____________________ || || Description . . . . ________________________________________ || Default Status . . . NONE + || Threshold OK . . . . ____________________ || Threshold Critical ____________________ || Spikes Check . . . . N (Y/N) || Log Status Change _ + || OMEGAVIEW Text Type Transient Text + || Input Parms . . . . ________ + || Probe Directive . . ________________________________________ || Misc. Parms . . . . ________________________________________ || ** Row displayed || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+

All the fields on this panel are described following this procedure.

2 In the Status Item field, type MVS_TSO_USERS.

3 In the Description field, type MVS TSO active users.

| Type Name Condition || s Status Item ** Add New ** Required |



Adding or modifying status item panelsUse these field definitions as a guide when adding a status item via the Add Status Item panel or entering or changing field values on the Modify Status Item panel.

4 Tab to the Threshold OK field and type 90 to specify that the OMEGAVIEW status bar is green (or OK) if the number of active users is 90 or fewer.

5 In the Threshold Critical field, type 100 to specify that the OMEGAVIEW status bar is red (or critical) if the number of active users is 101 or more.

6 Tab to the Probe Directive field and type TSOUSER. Press Enter so the OSM/MVS Assistant panel appears.

+----------------------------------------------------------------------------+| OSM/MVS Assistant ROW 1 TO 5 OF 7 || || (S)elect a referenced item and press Enter. || || --------------------------------------------------------------------- || Status Item has been updated. Modify Activity || rows for your desired actions. || || --------------------------------------------------------------------- || Type Name Condition || _ Status Item MVS_TSO_USERS Complete || _ Program PRBBB004 Complete || _ Probe MVS TSO user count Complete || _ Act-WARNING MVS_TSO_USERS Available || _ Act-OK MVS_TSO_USERS Available || ** Add completed successfully || Command ===> _________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

The status item’s Condition entry has changed from Required to Complete.

Result: You have added a status item so that the OMEGAVIEW status bar turns green when the number of active users is 90 or fewer, yellow when the number of users is between 91 and 100, and red when the number of users is greater than 100.

Field Description

Probe ID A probe ID. Press the Prompt key to display the Probe List panel, from which you can select a probe ID (1-8 characters).

System ID The ID of the system the probe is running on. This field is filled in automatically when a probe ID is selected. Press the Prompt key to display the Probe List panel, from which you can select a probe ID and its related System and Domain IDs (1-8 characters).

Domain ID This field is filled in automatically when a probe ID is selected. Press F4 to display the Probe List panel, from which you can select a probe ID and its related System and Domain IDs (1-8 characters).

Status Item An OMEGAVIEW status item name (1-20 characters).

Description A description of the status item (1-40 characters).



Default Status The default status of the item when no data is being transmitted by the probe. You can use OK (Green), Warning (Yellow), Critical (Red), or None (Turquoise). Press the Prompt key to select from a list of valid statuses.

Threshold OK A numbered limit or text string (1-20 characters). The status will register OK if the value returned by the probe is less than or equal to the limit value.

Threshold Critical A numbered limit or text string (1-20 characters). The status will register Critical if the value returned by the probe is greater than the limit value.

Spikes Check Specifies whether or not the spike feature is activated for this status item. Y means the spike feature is active and the Spike Check menu will appear when you press Enter. N means the spike feature is not active.

Log Status Change A blank or single character code. If blank, status changes are not written to a log. Otherwise, the log code of the log to which status changes are written. Press the Prompt key to select the log from a log panel.

OMEGAVIEW Text Type

One of four possible text types used by OMEGAVIEW to display status item changes. For more information, see the OG/MVS Configuration and Customization Guide and the OMEGAVIEW User’s Guide. Press the Prompt key to select a text type.

Transient The default. Can be up to 128 characters in length and does not update the OMEGAVIEW Status Data Manager (SDM).

Action Up to 20 characters in length and updates the OMEGAVIEW SDM.

User Static Up to 128 characters in length and updates the OMEGAVIEW SDM.

None No OMEGAVIEW display text is used.

Input Parms A 1-8 character string that must be specified for a DP, EM or QM probe. The string is used by one of these probe types (only) to identify the input table entry that contains the probe input data. The same input table entry can be used by more than one probe.

Probe Directive A 1 to 40 character string that is used by query and heartbeat probes to analyze data from the Data Manager. See “PROBELIB Sample Probes” on page 331 and “REXXLIB Probes and Status Items” on page 341 for usage according to individual probes.

Misc. Parms A 1-40 character text field that can be picked up by a probe as special parameters.



Spike checking: how it worksThe Spike Checking feature is activated by setting percentage values in the Spike Checking Panel for the relevant status. You display the Spike Chcking panel by entering Y in the Spikes Check field of the Add/Modify Status Item panel. OMEGACENTER Status Manager stores the status returned for each interval specified in a bit map represented as the Periods field. In the example below, the bit map will be 6 bytes long. Each bit has a possible value of:

The number of occurrences of each status value (0, 1, 2, or 3) in the bit map is then converted to a percentage and compared against the values in the Spike Checking fields. If the bit map contained the value 111331, it indicates that the most recent interval was OK, the two previous intervals were Critical, and the 3 intervals prior to that were OK. Because spike checking is enabled, a further check is performed. The OK status code occurs 66% of the time and the Critical status code ocurs 33% of the time. These values are now processed through the following test:

When OK_occurrences => OK_value (60%)

Then set status to OK

When critical_occurrences => critical_value (40%)

Then set status to CRITICAL

When warning_occurrences => warnaing_value (80%)

Then set status to WARNING

Otherwise,

SET DEFAULT STATUS

The result of the above test on bitmap 111331 against the values in the example Spike Check Entry Panel shown below would result in a status of OK.

Note: Be sure to specify a value for all three conditions.

Spike Check Entry Panel: +----------------------------------------------------------------------------+ | ------------------ Modify Status Item -------------------------- | | OSM/MVS - Spikes Check | | Press Enter when finished | | | | Periods . . . . . . 6 | | Initial Value . . . NONE + | | OK . . . . . . . . 60 | | Warning . . . . . . 80 | | Critical. . . . . . 40 | +----------------------------------------------------------------------------+

0 Unknown

1 OK

2 Warning

3 Critical


Setting an Exception Flag


IntroductionYou can set an exception flag to send a message to OMEGAVIEW when the number of active TSO users reaches the critical threshold, in this case study, 100 users.

OMEGAVIEW exception panels are specialized OMEGAVIEW panels created during OSM/MVS installation. For more information, see “Directing Messages to OMEGAVIEW Special Panels” on page 84.



ProcedureFollow these steps to send a message to an OMEGAVIEW exception panel.

Step Action

1 From the OSM/MVS Assistant panel, scroll to Act-CRITICAL of the MVS_TSO_USERS name and type S (to select) in the entry field.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 6 TO 7 OF 7 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Status Item has been updated. Modify Activity || rows for your desired actions. || || ----------------------------------------------------------------------- || Type Name Condition || _ Act-NONE MVS_TSO_USERS Available || S Act-CRITICAL MVS_TSO_USERS Available || ***************************** BOTTOM OF DATA ***************************** || || || || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

Press Enter.

Result: The Modify Activity panel appears.+--------------------------- Modify Activity ---------------------------+| OSM/MVS - Activity || || S(elect) the Activities you wish to modify, and press Enter. || || Status Item MVS_TSO_USERS Condition CRITICAL || Probe ID . : 004 System ID : B Domain ID : B || ------------------------------------------------------------------ || _ Diagnosis and Log Data || _ Notification and Recommendation Data || _ Action, Follow-up, and Log Data || _ Work List Data || _ Exception List Data || || F1=Help F12=Cancel |+-----------------------------------------------------------------------+



2 On the Modify Activity panel, tab to the Exception List Data entry field and type S (to select). Press Enter.

Result: The Exception List Data panel appears.+---------------------- Exception List Data ------------------------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item MVS_TSO_USERS Condition CRITICAL || Probe . . : 004 System ID. B Domain ID. B || ------------------------------------------------------------- || Exception Flag 1 . . . N (Y/N) || Exception Flag 2 . . . N (Y/N) || Exception Flag 3 . . . N (Y/N) || Exception Flag 4 . . . N (Y/N) || Exception Flag 5 . . . N (Y/N) || Exception Action . . . _ (A/D) || Exception Name . . . . ________ || Exception Description ____________ || Exception Status . . . ____________________ || || F1=Help F12=Cancel |+-------------------------------------------------------------------+

3 Tab to Exception Flag 1 and type Y.

4 Tab to the Exception Action field and type A. This instructs OSM/MVS to display the exception messages in sequence, rather than each new messages overwriting the previous one.

5 Tab to the Exception Name field and type ACT_USER.

6 Tab to the Exception Description field and type USER_COUNT.

7 Tab to the Exception Status field and type Max active users. Press Enter and then the Exit key twice.

8 From the OSM/MVS Assistant Exit Validation panel, press Enter to confirm the probe activation. Press Enter, again.

Result: You have set up a message that is displayed to OMEGAVIEW when more than 100 users are active.

Evaluating Two Conditions as One



IntroductionNext, you want OSM/MVS to evaluate CICS response time and TSO response time as a single condition, a situation. The thresholds that you set must both be met before the condition is considered true. You will use the AND logical operator to establish this relationship.

For more information on using situations, see “Situations” on page 57.

Add Situation panelUse the Add Situation panel to create a situation that combines the condition of two or more status items.

ProcedureFollow these steps to create a situation made up of two status items.

Step Action

1 Select Situation Manager... from the Managers pull-down on the OSM/MVS main panel.

Result: The Situation Manager panel appears.

+---------------------------- Add Situation -----------------------------+| OSM/MVS - Situation Manager || || Fill in the information, then press Enter. || || Situation Name USER_RESP_TIME || Probe Desc . : Situation Manager (B) || Probe ID . . . 999 + System ID B + Domain ID B + || Active Flag . . Y (Y/N) || || Status Item Name Comparator Value And/Or || CICS_TRAN_RESP + VLGE + 3___________________ AND || TSO_G210_TRAN_RESP_ + VLGT + 3___________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ || ____________________ + ____ + ____________________ || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------------+



2 Tab to any row and type A (to add) a situation. Press Enter.

Result: The Add Situation panel appears.+------------------------------ Add Situation ----------------------------+| OSM/MVS - Situation Manager || || Fill in the information, then press Enter. || || Situation Name . ____________________ || Probe Desc . . : || Probe ID . . . . ________ + System ________ + Domain ________ + || Active Flag . . Y (Y/N) || Enable Warnings N (Y/N) || || Status Item Name Comparator Value And/Or || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ ___ || ____________________ + ____ + ____________________ || || F1=Help F4=Prompt F12=Cancel |+-------------------------------------------------------------------------+

3 On the Add Situation panel, type USER_RESP_TIME in the Situation Name field.

4 Tab to the Probe ID field and press the Prompt key.

Result: The Probe List panel appears. This panel lists any probes linked to the USER_RESP_TIME status item.+------------------------------ Add Situation -------------------------------+| OSM/MVS - Probe List || || S(elect) a Probe and press Enter. || || ----------------------------------------------------------------------- || Probe Manager System Domain Probe ID || _ Situation Manager (B) B B 999 || _ Situation Manager (G) G G 999 || ***************************** BOTTOM OF DATA ***************************** || || || || || || || ** List of probes matching: ProbeID=*, Sys=*, Domain=*, Type=S || Command ===> _____________________________________________________________ || || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

5 Select Situation Manager (B) from the Probe Manager column by typing S (to select) in the entry field. Press Enter.

Result: The Add Situation panel appears.



6 Tab to the Status Item Name field and press the Prompt key.

Result: A panel displaying a list of status items available for the situation appears.+----------------------- Add Situation -----------------------+| OSM/MVS - Situation Manage ROW 117 FROM 295 || || (S)elect a Status Item and press Enter. || || -------------------------------------------------------- || Status Item Name Description || _ LH_WTOR_OMVTAMA outstanding replies || _ LH_WTOR_OMVTAMG outstanding replies || _ LH_XCSA csa usage || _ L1_DASD_SPACE DAS DASD Space utilization (DI || _ L1_DASD_SPACE2 DAS DASD space utiliztion (Nov || _ MVS_INITIATOR_1 Status of MVS Initiator #1 || _ MVS_JOBS_IN_CLASS_A MVS Job queues for Class A || _ MVS_PRINTER_R26 Status of JES printer R26 || _ MVS_TSO_USERS MVS TSO active users || || Command ===> ______________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+-------------------------------------------------------------+

7 Scroll through the panel. When you find CICS_TRAN_RESP, select it by typing S (to select) in the entry field. Press Enter.

8 Tab to the Comparator field and press the Prompt key.

Result: A panel appears that lists the available logical operators or comparators.+------------- Add Situation -------------+| OSM/MVS - Situation Manager || || (S)elect a comparator and press Enter. || || ------------------------------------ || _ STEQ Status Equal || _ STNE Status Not Equal || _ VLEQ Value Equal || _ VLNE Value Not Equal || _ VLLT Value Less Than || _ VLGT Value Greater Than || _ VLLE Value Less Than or Equal || _ VLGE Value Greater Than or Equal || || || || F1=Help F12=Cancel |+-----------------------------------------+

9 From the above panel, select VLGE (for Value Greater Than or Equal to) by typing S (to select) in the entry field. Press Enter.

Result: The Add Situation panel is displayed.

10 Tab to the Value field and type 3.

11 Tab to the And/Or field and type AND.

12 Tab to the Status Item Name field and type TSO_G210_TRAN_RESP.

13 Tab to the Comparator field and type VLGT (for Value Greater Than).



14 In the Value field, type 3 Press Enter.

Result: The OSM/MVS Assistant panel appears.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 5 OF 6 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Situation has been added, update the new Status || Item to build Activities for the new Situation. || || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item ** Add New **USER_RESP_TIME Required || _ Act-OK ** Add New **USER_RESP_TIME Not Available || _ Act-NONE ** Add New **USER_RESP_TIME Not Available || _ Act-CRITICAL ** Add New **USER_RESP_TIME Not Available || _ Situation USER_RESP_TIME Complete || ** Situation Add successful || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

You have added a situation that monitors CICS response time and TSO response time (for performance group 210 for period 1) as a single condition.

Adding a Status Item for a Situation



IntroductionNext, add a status item for the situation that represents CICS response time and TSO response time. When adding a new status item, you need to:


n set the threshold values

n set any additional parameters

ProcedureFollow these steps to add a status item for the situation you built in the previous section.

Step Action

1 On the OSM/MVS Assistant panel, select Status Item for the ** Add New **USER_RESP_TIME situation.

Result: The Add Status Item panel appears.+----------------------------- Add Status Item ------------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . . . 999 Situation Manager (B) || System ID . . . . . B_______ + || Domain ID . . . . . B_______ + || Status Item . . . . USER_RESP_TIME______ || || Description . . . . ________________________________________ || Default Status . . . NONE + || Threshold OK . . . . TRUE________________ || Threshold Critical . FALSE_______________ || Spikes Check . . . . N (Y/N) || Log Status Change . _ + || OMEGAVIEW Text Type Transient Text + || Probe Directive . . ____________________ || Misc. Parms . . . . ________________________________________ || || F1=Help F4=Prompt F12=Cancel |+----------------------------------------------------------------------------+

2 In the Description field, type Poor response time for users.

3 Tab to the Threshold OK field and type FALSE.

4 Tab to the Threshold Critical field and type TRUE.



5 Tab to the Probe Directive field and type USERTIME. Press Enter.

Result: The OSM/MVS Assistant panel appears.

The Condition column entries for Status Item and Situation have now changed to Complete.+----------------------------------------------------------------------------+| OSM/MVS - OSM/MVS Assistant ROW 1 TO 5 OF 6 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Status Item has been updated. Modify Activity || rows for your desired actions. || || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item USER_RESP_TIME Complete || _ Situation USER_RESP_TIME Complete || _ Probe Situation Manager (B) Available || _ Act-OK USER_RESP_TIME Available || _ Act-NONE USER_RESP_TIME Available || ** Add completed successfully || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

6 From the OSM/MVS Assistant panel, press the Exit key.

Result: The Activate panel appears.

7 Type Y in the Activate panel to activate the situation you just created. Press Enter and then the Exit key.

Result: You have added a status item, USER_RESP_TIME, which monitors the TSO response time and the CICS response time. When TSO response time is greater than or equal to 3 seconds and CICS response time is greater than 3 seconds, the OMEGAVIEW status bar turns red.

Refreshing OSM/MVS


Refreshing OSM/MVS

IntroductionTo activate the changes made to OSM/MVS, you refresh either the probe or one of the status items linked to it. In this chapter, you used only the Managers (not Setup activities), so you do not need to perform a global OSM/MVS refresh.

For more information on refreshing OSM/MVS, see “Updating OSM/MVS Data” on page 210.

ProcedureFollow these steps for refreshing the probes and status items you just built.

Step Action


2 Select probe 004, MVS TSO USER COUNT with an R action code. Press Enter.

Result: Data from probe 004 and any status item linked to it is updated.

Setting Up Distributed Systems Monitoring 287

Setting Up DistributedSystems Monitoring

OverviewThis part of the case study shows how to set up a distributed probe to check the status of an RS6000. It begins by explaining how such a probe operates. The case study then details the steps needed to define the distributed system and set up the probe, status item, and activity needed to track and display its status.

Note:

n You do not need any special code on the distributed system (RS6000) to set up and run the DAS (e.g., drivers, X-late routines).

n The scenario described here is designed to supplement the “Distributed Systems” on page 135. Please refer to that chapter for specifics of OSM/MVS's distributed systems monitoring capability.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Defining the Distributed System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Copying and Modifying a DAS Probe. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Adding a Status Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Specifying Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295Notifying Network Services Staff of an Offline Condition . . . . . . . . . . . . . . . . . . . . . . . . 297Refreshing OSM/MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

15

Introduction


Introduction

BackgroundThe Great Southern Financial field sales organization, based in New York, enters its orders on an RS6000. This RS6000 is part of a distributed system connected to the Los Angeles home office.

Corporate headquarters wants up-to-the-minute sales information to be available to all offices. To meet this requirement, the field sales organization’s RS6000 must be operational at all times. If it is unavailable, the home office wants to know immediately so that it can take appropriate action.

How the DAS probe worksUsing OSM/MVS to monitor the status of the New York RS6000 requires a DAS probe. The DAS probe you will set up is a heartbeat probe. The probe works by issuing a UNIX date command through the DAS. This command polls the RS6000 at a specific interval for the date (specifically, the year). It verifies the correctness of the date by comparing it to the current date on the host. If the dates match, the RS6000 is considered online and healthy, and the status is OK (green). If no response is received or the date returned from the RS6000 does not match the one on the host, the connection between the PC and RS6000 is considered broken, and the status is critical (red).

Using OSM/MVS to monitor an RS6000You will build the DAS probe to monitor a distributed RS6000 workstation as follows.

1. Define the distributed system that includes the field sales office’s RS6000.2. Copy and modify an existing DAS probe, customizing it for the RS6000 system you

defined.3. Add a status item that specifies threshold values for the probe.4. Specify the commands you want the DAS to issue to the distributed system you defined.5. Create a notification message to be sent to the data center if the RS6000 goes down.


Defining the Distributed System


IntroductionYou begin setting up monitoring of the RS6000 by defining the distributed system and identifying it to OSM/MVS.

Procedure

Step Action

1 Select System Environments... from the Setup pull-down on the OSM/MVS main panel.

2 Type A in the Sel column of the line whose ID is R1 (the UNIX/AIX RS-6000 System).

Press Enter.

Result: The Add System Definition panel appears.+------------------- Add System Environment --------------------+| OSM/MVS - System Data || || Fill in the information, then press ENTER. || || System ID . . . . . ________ || Description . . . . ________________________________________ || System Type . . . . _ (M)VS or (D)AS || || For the MVS system type, please press ENTER || to view/modify additional information. || || || F1=Help F12=Cancel |+---------------------------------------------------------------+

3 In the System ID field, type the ID of the RS6000 system you want to monitor. In this example, type S1.

4 In the Description field, type RS6000 System #1.



5 In the System Type field, type D. Press Enter, then the Exit key.

Result: OSM/MVS displays the Add System Environments panel.+-------------------------- Add System Environment ---------------------------+| OSM/MVS - System Environments ROW 1 FROM 11 || || Select a MVS system row and press Enter. Valid actions are (S)elect. || (This will identify the MVS system for this Remote definition.) || || Local Focal || Sel System Sys. ID SYSNAME System Description || _ G2 LINKID4G SYSG N Norman Lew System G2 || _ G1 LINKID4G SYSG Norman Lew System G1 || _ GO1PS SYSGO1PS SYSG Y Candle Development System-G || _ SYSG3 SYSG3 SYSG N Another toolkit for System-G || || Command ===> ______________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+-----------------------------------------------------------------------------+

6 Select GO1PS as the MVS system for this remote definition.

Result: The DAS Selections panel is displayed.+-------------------------- Add System Environment ---------------------------+| OSM/MVS - DAS Selections ROW 1 FROM 3 || || To identify the MVS remote console for this remote system, please || (S)elect a row and press Enter. || || --- AF/REMOTE is Attached to... --- ConUnit Rout Beeper || Sel System Description Address Code Support? || _ GO1PS CANDLE DEVELOPMENT SYSTEM-G 6D5 15 N || ***************************** BOTTOM OF DATA ****************************** || || || || Command ===> ______________________________________________________________ || F1=Help F3=Exit F7=Backward F8=Forward F10=ActBar |+-----------------------------------------------------------------------------+

7 Select GO1PS to identify the MVS remote console for this remote system.

Result: The new distributed system has been identified to OSM/MVS.


Copying and Modifying a DAS Probe


IntroductionA probe to monitor distributed systems is available in OSM/MVS. For this case study, you will make a copy of that probe and customize it for your distributed system.

In some cases, you may want to code your own probe. Creating probes is described in “Writing a Probe” on page 315.

Procedure

Step Action


Result: The Probe Manager panel appears.

2 Type C (to copy) in the entry field next to probe ID 081 (DAS probe, UNIX RS-6000 Status) whose System ID is B and Domain ID is R1.

Press Enter.

Result: The Copy a Probe panel appears.+----------------------- Copy A Probe ------------------------+| OSM/MVS - Probe Manager || || Fill in the information, then press Enter. || || Probe ID . . . 081 || System ID . . . B Candle Development System-B || Domain ID . . . R1 Unix System || Probe Type . . . X + Distributed Probe || || Description . . DAS RS6000 HeartBeat || User Exit Name . KATRA081 || || F1=Help F4=Prompt F12=Cancel |+-------------------------------------------------------------+

You use the Copy a Probe panel to copy OSM/MVS’s DAS probe and add new identification information before defining the probe to the system.

Note:

1. The System ID is the MVS system under which the distributed probe will run, and the Domain ID is the identifier of the system to be monitored. In this scenario, only modify the Domain ID.

2. Probe 081 is designed to function in any UNIX or UNIX-like environment.



3 On the Copy a Probe panel, change the Probe ID to 281 and the Domain ID to S1. Press Enter.

The OSM/MVS Assistant panel appears.+----------------------------------------------------------------------------+| OSM/MVS Assistant ROW 1 TO 5 OF 8 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Probe has been copied, now select the Status Item || to build Status and Activity rows for the Probe. || Dist. Systems will be available after Status Item Add/Copy. || ----------------------------------------------------------------------- || Type Name Condition || _ Status Item ** Add New ** Required || _ Program ** Add New **KATRA081 Required || _ Dist. System ** Add New ** Not Available || _ Act-WARNING ** Add New ** Not Available || _ Act-OK ** Add New ** Not Available || ** Copy completed successfully || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

Result: You have completed copying the probe. Probe 281 will monitor for the existence of your RS6000 system.

For more information on using the OSM/MVS Assistant panel, see “OSM/MVS Assistant” on page 197.


Adding a Status Item


IntroductionNext, you add a status item to the distributed systems probe you copied.

When adding a new status item, you need to


n identify the probe directive that the status item monitors

n add a text description of the status item

n fill in threshold information

ProcedureFollow these steps to specify commands for the distributed system.

Step Action

1 From the OSM/MVS Assistant panel, type S in the entry field of the Status Item type for **Add new**. Press Enter. The Add Status Item panel appears.

+----------------------------- Add Status Item ------------------------------+| OSM/MVS - Status Manager || || Fill in the information, then press Enter. || || Probe ID . . . . . . 281 DAS RS6000 HeartBeat || System ID . . . . . B_______ || Domain ID . . . . . S1______ || Status Item . . . . ____________________ || || Description . . . . ________________________________________ || Default Status . . . NONE + || Threshold OK . . . . ____________________ || Threshold Critical . ____________________ || Spikes Check . . . . N (Y/N) || Log Status Change . _ + || OMEGAVIEW Text Type Transient Text + || Input Parms . . . . ________ + || Probe Directive . . ____________________ || Misc. Parms . . . . ________________________________________ || ** Row displayed || F1=Help F4=Prompt F12=Cancel |+----------------------------------------------------------------------------+

2 In the Status Item field (OMEGAVIEW status item name), type S1_Workstation.

3 The Description field is a text label for the status item you are creating. Type

RS6000 Workstation - heartbeat.

4 In the Threshold OK field, type Yes. This sets the status light to green when the date returned from the distributed probe matches the date on the host.



5 In the Threshold Critical field, type No. This sets the status light to red when the date returned from the distributed probe does not match that on the host.

6 In the Probe Directive field, type S1.

7 The Misc. Parms field is for special parameters that are picked up by the probe. Leave it blank. Press Enter. The OSM/MVS Assistant panel appears.

+----------------------------------------------------------------------------+| OSM/MVS Assistant ROW 1 TO 5 OF 8 || || S(elect) a referenced item and press Enter. || || ----------------------------------------------------------------------- || Status Item has been updated. Modify Activity || rows for your desired actions. || || ----------------------------------------------------------------------- || Type Name Condition || _ Program ** Add New **KATRA081 Required || _ Dist. System ** Add New **S1_WORKSTATION Required || _ Status Item S1_WORKSTATION Complete || _ Probe RS6000 CPU Utilization(OMS/OS2-Only) Complete || _ Act-WARNING S1_WORKSTATION Available || ** Add completed successfully || Command ===> _____________________________________________________________ || F1=Help F7=Backward F8=Forward F12=Cancel |+----------------------------------------------------------------------------+

Result: You have added a status item that monitors whether a distributed RS6000 is online.


Specifying Commands

Specifying Commands

IntroductionYou have defined the distributed system, the distributed UNIX date probe, and the status item. You now need to define the commands that the probe will use to obtain data from the distributed system.

ProcedureFollow these steps to notify a user of an incident.

Step Action

1 On the OSM/MVS Assistant panel, type S in the entry field of the Dist. System type (Add new S1_Workstation). Press Enter.

Result: The Add Distributed System panel appears.+----------------------- Add Distributed System ------------------------+| OSM/MVS - DAS Manager || || Fill in the information, then press Enter. || || Status Item S1_WORKSTATION || Probe ID . : 281 System B Domain S1 || Probe Desc : DAS RS6000 HeartBeat || || Active Flag . . . . . : N || Distributed System ID . ___ || || System Type Code . . . . _ + || Probe Frequency . . . . ________ (seconds) || Log Code . . . . . . . . _ + || Command Line . . . . . . ________________________________________ || ________________________________________ || Value Offset . . . . . . ___ || Value Size . . . . . . . __ || Translate Routine . . . ________ || || F1=Help F4=Prompt F12=Cancel |+-----------------------------------------------------------------------+

This panel lets you complete information about the command that the probe will use. You will specify:n the name of the commandn how frequently to issue the commandn which data you want to retainn whether to write the data to a log file

2 On the Add Distributed System panel, type S1 in the Distributed System ID field.

3 Type D (for Distributed) in the System Type Code field.

4 Type 240 in the Probe Frequency field. This indicates that the DAS heartbeat probe will issue a the UNIX date command every 240 seconds.

5 For the case study you will not enable logging. Therefore, type N in the Log Code field.

Specifying Commands


6 Type date in the Command Line field. date is the UNIX command you want issued by the probe.

Note: UNIX is a case-sensitive language. Make sure to type commands in lower case.

7 Type 25 in the Value Offset field to indicate that the data to be read starts with offset 25 of the response.

8 Type 4 in the Value Size field. This indicates that, starting at offset 25, 4 characters of data (the year) are read.

9 Press Enter. The OSM/MVS Assistant panel appears.

Result: You have specified the command issued by the distrbitued heartbeat probe, as well as its parameters, the frequency with which it is issued, and the data it gathers.


Notifying Network Services Staff of an Offline Condition


IntroductionIf the RS6000 goes offline, the person or department in charge of resolving the problem needs to be notified. You need to create a notification message and send it to data center staff when the distributed system’s status turns critical.



Procedure

Step Action

1 On the OSM/MVS Assistant panel, type S in the entry field of the Act-CRITICAL type field for S1_Workstation. Press Enter.

Result: The Modify Activity panel appears.

+-------------------------- Modify Activity ----------------------------+| OSM/MVS - Activity || || S(elect) the Activities you wish to modify, and press Enter. || || Status Item S1_WORKSTATION Condition CRITICAL || Probe ID . : 281 System ID : B Domain ID : S1 || ------------------------------------------------------------------ || _ Diagnosis and Log Data || _ Notification and Recommendation Data || _ Action, Follow-up, and Log Data || _ Work List Data || _ Exception List Data || || F1=Help F12=Cancel |+-----------------------------------------------------------------------+

Use this panel to enable an activity when the distributed system you defined enters a critical condition. For this scenario, you will use the Notification and Recommendation Data selection.

2 On the Modify Activity pop-up, tab to the Notification and Recommendation Data field and type S (to select). Press Enter.

Result: The Modify Notification and Recommendation Data panel appears. This panel lets you identify the individuals or lists of individuals you want to notify and the text of the message.+---------- Modify Notification and Recommendation Data -----------+| OSM/MVS - Activity || || After you have made your changes, press Enter. || || ------------------------------------------------------------- || Status Item S1_WORKSTATION Condition CRITICAL || Probe . . : 281 System ID. B Domain ID. S1 || ------------------------------------------------------------- || Notification Code ____ + || Notification Text ________________________________________ || Create Incident . N (Y or N) || Incident Priority Escalate Until Available + || Alternate Notification Program ________ || ------------------------------------------------------------- || Recommendation Code . . . . . ____ + || || F1=Help F4=Prompt F12=Cancel |+------------------------------------------------------------------+



SummaryIn this part of the case study, you used OSM/MVS to set up a distributed probe that monitors the availability of an RS6000. If the RS6000 goes down, a support team will be notified of the problem.

Remember that before a distributed probe is operational, the OS/2 PC running AF/REMOTE must be set up and configured. See “Distributed Systems” on page 135 for information on the required setup.

3 The Modify Notification and Recommendation Data pop-up lets you use codes to represent individuals or groups you want to notify. For example, you could label data center staff with a notification code of DC1, the head of operations with a code of DC0, and so on. You can scroll through the notification and recommendation lists by placing the cursor in the Notification Code or Recommendation Code field, and pressing the Prompt key.

For this case study, you will use a code to represent the data center team that supports the RS6000. Enter the network services support team code (NS) in the Notification Code field. For information on creating your own list of notification users, see “Setting Up Notification Users” on page 96.

4 Tab to the Notification Text field and type the following text: New York RS6000 is down. Press Enter and then press the Exit key twice.

5 From the Exit Validation panel, type Y in the Activate field. This enables notification if the RS6000 goes down. Press Enter, and then the Exit key.

Result: You have written a message that notifies Network Services Staff when the RS6000 in New York is not functioning.

Refreshing OSM/MVS


Refreshing OSM/MVS

IntroductionTo activate the changes you made to OSM/MVS, you need to perform a refresh. In this chapter, you made notification changes as well as changes to a probe. Therefore, you need to perform a global OSM/MVS refresh.

For more information on refreshing OSM/MVS, see “Updating OSM/MVS Data” on page 210.

ProcedureFollow these steps for performing a global OSM/MVS refresh.

Step Action

1 Select Refresh OSM/MVS... from the Controls pull-down on the OSM/MVS main panel.

Result: The Refresh OSM/MVS panel appears.

2 Tab to SYSB and type S (to select) in the entry field. Press Enter.

Result: You have updated OSM/MVS. All modifications are now active.

Building an Interface with OMEGAVIEW 301

Building an Interfacewith OMEGAVIEW

OverviewThis chapter shows how to build a user interface to the OSM/MVS structures you created in the previous three chapters. This involves creating several panels, populating them with graphic objects and screen text, and linking them together.

Chapter ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302Building the Interface Panels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303Create the Detail Panel for Systems Management Staff . . . . . . . . . . . . . . . . . . . . . . . . . . 306Creating the Detail Panel for Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Creating the Detail Panel for Field Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Creating the Main OMEGAVIEW Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

16

Introduction


Introduction

DescriptionOMEGAVIEW is an interactive system that allows you to build custom front ends to display the status information gathered by OSM/MVS probes. Its capabilities let you visually map availability data in appealing and meaningful display panels.

Before you beginMake sure that OMEGAVIEW has been installed and is available for use on your system. Although not required for this application, some familiarity with OMEGAVIEW and the types of objects it can build may be useful. For detailed information, see the OMEGAVIEW User’s Guide.


Building the Interface Panels


IntroductionThis part of the case study is designed to familiarize you with OMEGAVIEW and its role in displaying OSM/MVS data. OMEGAVIEW provides a variety of graphic objects and features for data display. The case study application uses a subset of these.

Using OSM/MVS to build interface panelsYou will build the interface by adding text and the following graphic objects to a set of blank OMEGAVIEW panels:

History Status Bars Display data for the last session measurement preceded by either 15 minutes (short term) or one hour (long term) of status. They allow you to display in color the status of OSM/MVS data over a period of time.

green Normal functioning

yellow Warning

red Critical

turquoise Idle; not receiving data

Pushbuttons Allow you to link panels and to zoom in on specific data items for detailed information.



Sample OMEGAVIEW panelThe following is an example of an OMEGAVIEW panel for Great Southern Financial. History status bars, representing the health of systems for domestic and international sales offices, occupy the main portion of the screen. Pushbuttons, which allow navigation to related panels, are displayed beneath them..

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/97 12:17:30 Great Southern Financial +-------------------------------------+-------------------------------------+| Domestic | International |+-------------------------------------+-------------------------------------+| | || Atlanta ///\\\////// | Athens //////////// || | || Chicago //////////// | London //////////// || | || Denver \\\///////// | Munich ///\\\////// || | || New York //////////// | Paris //////////// || | |+-------------------------------------+-------------------------------------+ @-------------› @---------------› @-----------------› @---------------› | > Systems < | | > Main Menu < | | > Telephones < | | > Org Chart < | %-------------` %---------------` %-----------------` %---------------` F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel




Application interfaceThe following diagram shows the panels you will build with OMEGAVIEW for this application.

The main panel contains pushbuttons for the three types of user: customer support, systems management staff, and field office sales. Activating one of the pushbuttons takes you to a detail panel displaying the principal status items for that user category.

Order of building panelsTo facilitate ease of linking the panels, build the detail panels before building the main panel. The following sections list the procedures for building the panels.

Create the Detail Panel for Systems Management Staff



IntroductionThe following procedures describe how to create history bars on the panel for use by systems management staff.

Systems Management panelWhen you are finished with this section, you will have built the following panel:

ProcedureFollow this procedure to create the detailed panel showing the short- and long-term history bars for systems management staff.

Step Action

1 Create a new OMEGAVIEW panel.

a. From any OMEGAVIEW panel, select File on the Action Bar. The File pull-down menu appears.

b. Type 1 and press Enter to create a new OMEGAVIEW file.

Result: A blank OMEGAVIEW Edit panel appears.

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/97 12:17:35 OMEGAVIEW Version nnn Systems Management _MVS TSO User Count //////////// _System Response //////////// F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel




2 Create a literal text string.

a. Move the cursor down 5 spaces and press F15 to display the Object Class Selection menu.

b. Type 1 and press Enter to display the Literal Text Definition pop-up.

c. Type Systems Management in the Text field.

d. If necessary, move the cursor to the Color field, press F4 to display the Color prompt menu, select Turquoise, and press Enter.

Result: The text string Systems Management appears on the Edit panel.

3 Create a Short-History Status bar.

a. Move the cursor 40 spaces to the right and press F15 to display the Object Class Selection menu.

b. Type 4 and press Enter to display the Status Item Choices pop-up.

c. Type / next to MVS_TSO_USERS and press Enter to select the Status name and to display the Status Bar Create pop-up. (Each status name indicates the status of a situation.)

d. Type MVS TSO User Count in the Status Label field and press Enter.

Result: The Short-History Status Bar appears.

4 Create another Short-History Status bar.

a. Move the cursor 4 spaces down, and press F15 to display the Object Class Selection menu.

b. Type 4 and press Enter to display the Status Item Choices popup.

c. Type / next to USER_RESP_TIME and press Enter to select the Status name and to display the Status Bar Create pop-up.

d. Type System Response in the Status Label field, and press Enter.


5 Save the file as follows.

a. Select File on the Action Bar so the File pull-down appears.

b. Type 4 to save the file.

c. Type Sys Mgmt in the Name field.

d. Press Enter.

Result: The File Properties panel appears.

e. Type a description in the Description field or leave the field blank. Press Enter.

Result: The panel is saved with the name Sys Mgmt.

6 Press F3. The Sys Mgmt panel replaces the Edit panel.

Creating the Detail Panel for Customer Support



OverviewYou will now create the detailed panel showing the short-term history bar for Customer Support. This history bar will display response time for TSO, the system used by Customer Support for Information Management.

Customer Support PanelWhen you are finished, you will have built the following panel:

ProcedureFollow the procedure below for creating the Customer Support detail panel.

Step Action


a. From an OMEGAVIEW panel, select File from the Action Bar so the pull-down menu appears.



File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/97 12:17:40 OMEGAVIEW Version nnn Customer Support TSO Response Time //////////// F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel





a. Move the cursor down 5 spaces and press F15 to display the Object Class Selection Menu.


c. Type Customer Support in the Text field.

d. Move the cursor to the Color field and press F4 for the Color Prompt menu.

e. Select Red.

f. Press Enter twice.

Result: The text string Customer Support appears on the Edit panel.

3 Create a Short-History Status Bar.



c. Type / next to TSO_RESP_G and press Enter to choose a Status name and to display the Status Bar Create pop-up. (Each status name indicates the status of a situation.)

d. Type TSO Response Time in the Status Label field, and press Enter.




b. Type 4 and press Enter to save the file.

c. Type Cust Supp in the Name field. Press Enter.


5 Type a description in the Description field or leave the field blank. Press Enter.

Result: The panel is saved with the name Cust Supp.

6 Press F3. The Cust Supp panel replaces the Edit panel.

Creating the Detail Panel for Field Sales



OverviewYou will now create the detailed panel showing the status of the field sales organization’s distributed system. A red light on this panel indicates that an RS6000 has gone offline.

Field Sales PanelWhen you are finished, you will have built the following panel:

ProcedureFollow this procedure for building the Field Sales detail panel.

Step Action


a. From an OMEGAVIEW panel, select File from the Action Bar so the pull-down menu appears.



File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/97 12:17:45 OMEGAVIEW Version nnn Field Sales Orders _RS6000 //////////// F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel





a. Move the cursor down 5 spaces and press F15 to display the Object Class Selection Menu.


c. Type Field Sales Orders in the Text field.

d. If necessary, move the cursor to the Color field, press F4 to display the Color Prompt pulldown, select Red, and press Enter.

Result: Text string Field Sales Orders appears on the Edit panel.

3 Create a Short-History Status Bar.



c. Type / next to S1_RS6000_HEARTBEAT and press Enter to choose a Status name and to display the Status Bar Create pop-up. (Each status name indicates the status of a situation.)

d. Type RS6000 in the Status Label field, and press Enter.





c. Type Field Sales in the Name field.

Press Enter.



Result: The panel is saved with the name Field Sales.

6 Press F3. The Field Sales panel replaces the Edit panel.

Creating the Main OMEGAVIEW Panel



OverviewThis section shows you how to build the main OMEGAVIEW panel for the prototype application. The panel consists of three pushbuttons, one for each of the three user categories. Selecting one of the pushbuttons takes you to a detail panel that displays status items for the category you selected.

Main OMEGAVIEW PanelWhen you have completed this section, you will have built the following panel:

ProcedureCreate the main OMEGAVIEW panel with pushbuttons for customer support, systems management, and field sales as follows.

Step Action


a. From an OMEGAVIEW panel, select File from the Action Bar.


Result: The OMEGAVIEW Edit panel appears.

File Switch(W) Tools Samples Options Help ------------------------------------------------------------ 10/30/97 12:17:50 OMEGAVIEW Version nnn System Availability @------------------------› | > Cust Supp < | %------------------------` @------------------------› | > Sys Mgmt < | %------------------------` @------------------------› | > Field Sales < | %------------------------` F1=Help F2=Keys F3=Exit F5=Refresh F10=Action Bar F15=Top Panel




a. Move the cursor down 5 spaces and 15 spaces to the right and then press F15 to display the Object Class Selection menu.

b. Type 1 and press Enter to create a Literal Text Definition pop-up.

c. Type System Availability in the Text field.

d. Move the cursor to the Color field and press PF4 for the Color Prompt menu.

e. Select Turquoise.

f. Press Enter.

Result: The text string System Availability appears on the screen.

3 Create a pushbutton.


b. Type 3 and press Enter to create a pushbutton.

c. Type Cust Supp in the Pushbutton text field.

d. Move the cursor to the Color field and press F4 for the Color Prompt menu.

e. Select Turquoise.

f. Move the cursor to the Destination field and type Cust Supp. (The Destination field tells the pushbutton which panel to link to.)

g. Press Enter.

Result: The pushbutton for the Cust Supp panel appears.

4 Create another pushbutton.


b. Type 3 and press Enter to create a pushbutton.

c. Type Sys Mgmt in the Pushbutton text field.

d. Move the cursor to the Destination field and type Sys Mgmt. (The Destination field tells the pushbutton which panel to link to.)

e. Press Enter.

Result: The pushbutton for the Sys Mgmt panel appears.

5 Create another pushbutton. Move the cursor down 2 spaces and press F15 to display the Object Class Selection menu.

a. Type 3 and press Enter to create a pushbutton.

b. Type Field Sales in the Pushbutton text field.

c. Move the cursor to the Color field and press F4 for the Color Prompt menu.

d. Select Turquoise.

e. Move the cursor to the Destination field and type Field Sales. (The Destination field tells the pushbutton which panel to link to.)

f. Press Enter.

Result: The pushbutton for the Field Sales panel appears.



Mission accomplishedYou have now used OSM/MVS and OMEGAVIEW to build a complete sample availability management application. In building this application, you have learned how to:

n customize probes

n create status items, including situations

n set thresholds for status items

n set up automatic action routines

n send recommendations to the operator

n refresh OSM/MVS

n send exception messages to OMEGAVIEW

n create OMEGAVIEW panels for status display

6 Save the file.

a. Select File from the Action Bar so the File pull-down appears.


c. Type Main Panel in the Name field. Press Enter.



Result: The panel is saved with the name Main Panel.

8 Press F3. The Main Panel replaces the Edit panel.

Writing a Probe 315

Writing a Probe

Appendix OverviewThis appendix provides annotated source code for a query probe that obtains TSO response time. This probe can be used as a model for other query probes that you write. When you are finished with this chapter, you will:

n understand the structure of a probe

n become familiar with a probe’s coding rules

n understand the meaning of key lines of code in a probe

Appendix ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316Status Item Values for Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319Probe Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320Example Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Probe Code Annotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

A

Introduction


Introduction

DescriptionOSM/MVS includes other sample probes in the libraries PROBELIB and REXXLIB. Some of the probes in REXXLIB have been designed to be used as models when creating your own probes. As models, they include templates and are otherwise coded to facilitate the probe coding process. Chapter 3 lists and describes the probe types. For each probe type, the following table lists:

n how the probe is executed

n how often the probe is executed and whether it can be scheduled

n whether the probe uses status items

n the parameters used by the probe

n the probe we recommend you use as a model

TypeHow

Executed Frequency Sched.

Uses Status Items

? Parameters Used Model

A Called from startup

Once at startup

No No parse_charDomain_Nameprobe_id

None

D TOD trap executes the probe program

Probe interval (defined via the Probe Manager panel)

Yes No parse_charDomain_Nameprobe_idprobe_environmentprobe_logprobe_parm

KATRAM01

DG TOD trap executes the probe program


Yes No parse_charDomain_Nameprobe_idprobe_environmentprobe_logprobe_parm

Uses program KATRA922. Values for the Input field are defined through the dependent probe (DP) status item definition.

DP Called by Data Manager

Set by Data Manager

No Yes parse_charDomain_Nameprobe_idstatus_item@PROBE_MGR_vars

When you create this probe, a Candle-supplied skeleton will be generated automatically.

Writing a Probe 317

Introduction

E Called by Event Probe Manager (KATRA995)

Probe START EVENT, Probe STOP

Yes Yes parse_charDomain_Nameprobe_idstatus_itemFunction@PROBE_MGR_vars

KATRA020

EM Called by Event Probe Manager (KATRA995)


Yes Yes parse_charDomain_Nameprobe_idstatus_itemFunction@PROBE_MGR_vars


EO Called by Event Probe Manager (KATRA995)


Yes Yes parse_charDomain_Nameprobe_idstatus_itemFunction@PROBE_MGR_vars@EXCP_data

KATRA919

H TOD trap executes Probe Manager (KATRA000) which calls probe program


Yes Yes parse_charDomain_Nameprobe_idstatus_item@PROBE_MGR_vars

KATRA028

M TOD trap executes probe program

Once at startup

No No ask_functionDomain_Namelog_codetext

KATRAM05

Q TOD trap executes Probe Manager (KATRA000) which calls probe program



KATRA055

TypeHow


Uses Status Items


Introduction


What you need to knowThis chapter assumes that you:

n know the REXX programming language

n understand the IBM mainframe environment

n are familiar with Candle’s OMEGACENTER products (the OMEGAMONs, OMEGAVIEW, and OG/MVS)

The probe models supplied with the OSM/MVS are referred to by their program names on the OSM/MVS panels.

QM TOD trap executes Probe Manager (KATRA000) which calls probe program




X Called from DAS Probe Manager (KATRA800)

n/a No Yes parse_charDomain_Nameprobe_idstatus_itemprobe_value@PROBE_MGR_vars

KATRA080

TypeHow


Uses Status Items


Writing a Probe 319

Status Item Values for Probes

Status Item Values for Probes

Retrieving a status item valueEach probe can support up to 100 separate status items. Each status item is represented in the OSM/MVS Status Manager table by a unique status item name.

The Probe Manager invokes the probe once for each status item the probe supports. Once the probe has identified the status item, it obtains the status item value either by:

n Issuing a command directly to the monitored object’s environment, or

n Accessing a system variable in which a Data Manager has stored the value for the probe.

Converting a status item valueIf necessary, the probe converts the retrieved status item value to meet application requirements. For example, the subsystem being monitored may provide a value that represents the percent of free DASD space. However, if the OSM/MVS application needs the percent of used DASD space, the probe converts the status item value from the percent of free space to the percent of used space before returning it to the Probe Manager.

Probe Model


Probe Model

IntroductionThis section describes how to code a query probe using a probe provided with the OSM/MVS as the example. You can access probe models in two ways.

n From the OSM/MVS Assistant panel, select the probe by entering S in the select column on the row containing the probe ID. For more information, see “Copying Source Code for the New Probe” on page 271.

n From the Probe Manager panel, select the probe you want by entering an E (for edit) in the select column on the row containing the probe ID.

Once the REXX code template is displayed, you can use the Edit Copy command to copy a probe from REXXLIB into the current member, or add or modify the code as necessary.

Coding rulesObserving the following rules when coding probes will help ensure that probes execute successfully.

n The PARSE ARG and PARSE VAR statements that obtain and parse the argument string passed by the Probe Manager are standard for all probes. They must be coded as shown in lines 24, 43, 50, 55, and 68 of the example. That is, the arguments listed in the statements must be used and must be used in the same sequence as they occur in the code.

n The RETURN statements must be coded as shown in lines 65 and 77. They return the status item value to the Probe Manager. The last statement in the program (line 93) returns an error condition that will cause the Probe Manager to terminate the probe.

Coding recommendationsYou can use:

n the SIGNAL ON ERROR statement (line 22) to execute the error-processing code in the event that an error occurs while processing a command

n the error-processing code (lines 83-93) as a template for passing error data

You can supplement the code with additional error-processing routines.

Probe-unique codeThe code that gets the status item value (lines 61-77 in this example) is unique to each probe. The example shown below obtains the status item value (TSO response time) from a system variable established by the Data Manager for this probe.

If you write a new probe that uses a Data Manager, you should be familiar with the names of the variables the Data Manager creates. You will also have to modify the Data Manager to create the variable needed by your probe.

Writing a Probe 321

Probe Model

Eight-character probe IDs can cause the trap action limit of 128 characters to be exceeded. Therefore, if you use eight-character probe IDs for dependent query probes, you must add the following code fragment to your Data Manager.

Note: DG probes are exempted from this additional coding requirement.

Add the code at the point at which the probe is entered after parsing the variable PROBE_PARM in the incoming argument string.

IF PROBE_PARM = ’REXX_SHARED_VARIABLE’ THEN

DO

RSV_NAME = ’@OGAT.@PROBE_PARMS.’DATAMG_PROBE_ID

IF \ GETSHARED("SYSTEM",RSV_NAME) THEN

DO

MSG_PARMS = RSV_NAME R_C

MSG_ID = ’KAT0077E’

SIGNAL ERROR1

END

PROBE_PARM = @OGAT.@PROBE_PARMS.DATAMG_PROBE_ID

END

Remember that while this sample probe relies on a Data Manager some probes do not.

OG/MVS REXX shared variable functionsOG/MVS REXX shared variable (RSV) functions allow you to use long and compound variable names when referencing REXX-stored data. This example uses the OG/MVS RSV function SHARVGET to get the compound variable @OGAT.domain_name.probe_id from the SYSTEM pool, a persistent REXX pool, and put the value into a pool local to the probe. See the OG/MVS Command Reference Manual for more information on the OG/MVS REXX shared variable functions.

OSM/MVS uses many variables in the RSV SYSTEM pool. These variables contain such information as the probe record, status item record, and status item color and value. Using the parameters of domain_name, probe_id and status_item, any of this data may be retrieved from the SYSTEM pool. For example, if probe 055 is running for domain G, the probe record is stored in the variable named @OGAT.G.055, so the probe description can be retrieved from that variable.

Example Probe


Example Probe

Source code for a query probeThe following is source code for a query probe that obtains TSO response time. See “Probe Code Annotation” on page 324 for a line-by-line annotation of this code.

1 /* REXX ************************************************************* *2 * *

3 * PROGRAM: KATRA055 (PROB055) -- AMS PROBE: TSO RESPONSE TIME * 4 * * 5 * ARGUMENTS: DOMAIN_NAME * 6 * PROBE_ID * 7 * Status_item * 8 * @PROBE_MGR_vars * 9 * * 10 * INPUTS/OUTPUTS: SYSTEM VARIABLES FOR UP TO 4 STATUS ITEM NAMES * 11 * * 12 * DESCRIPTION: PROBE EXECUTED BY A TOD TRAP TO OBTAIN DATA FROM * 13 * DATAMG01 EVALUATE IT AND REACT. * 14 * * 15 * ------------------------------------------------------------------ * 16 * CHANGE LOG: * 17 * NAME DATE CHANGE * 18 * mpd 01/31/94 AT11110;REXX shared variables * 19 * * 20 * ****************************************************************** */ 21 22 SIGNAL ON ERROR NAME ERROR 23 24 PARSE Arg pc +1, /* parse character */ 25 Domain_Name (pc) PROBE_ID (pc) status_item (pc) , 26 @PROBE_MGR_vars 27 28 MSG_PARMS = ’’ 29 Msg_Id = ’’ 30 31 /* ****************************************************************** * 32 * ESTABLISH PROBE-SPECIFIC PARAMETERS * 33 * ****************************************************************** */ 34 35 rsv_name = ’@OGAT.’Domain_Name’.’probe_id 36 r_c=SHARVGET("SYSTEM",rsv_name) 37 If r_c <> 0 Then 38 Do 39 msg_parms = rsv_name r_c 40 msg_Id = ’KAT0077E’ 41 Signal Error 42 End 43 Parse var @OGAT.Domain_Name.probe_id pc2 +1 , 44 prb_desc (pc2) . /* Get probe description */ 45

Writing a Probe 323

Example Probe

46 /* ****************************************************************** * 47 * COLLECT DEFINITION PARAMETERS FROM SYSTEM VARIABLES * 48 * ****************************************************************** */ 49 50 PARSE Var @PROBE_MGR_vars , 51 Default_status (pc) Green_Value (pc) Red_Value (pc) , 52 Log_MVupdate_code (pc) Probe_Directive (pc) , 53 MISC_PROBE_PARMS (pc) . 54 55 PARSE VAR MISC_PROBE_PARMS PERIOD_NUM . 56 57 /* ****************************************************************** * 58 * COLLECT DATA * 59 * ****************************************************************** */ 60 61 SYS_VAR_NAME = ’@TRT’||DOMAIN_NAME||Probe_Directive 62 DATAMG_DATA = KATRAF06(’G’ SYS_VAR_NAME) 63 IF DATAMG_DATA = -1 THEN 64 DO 65 RETURN ’NO_DATA’ 66 END 67 68 PARSE VAR DATAMG_DATA CMD_NAME VALUE1 VALUE2 VALUE3 VALUE4 . 69 70 IF VALUE(’VALUE’||PERIOD_NUM) > 0 THEN 71 ATTRIBUTE_VALUE = VALUE(’VALUE’||PERIOD_NUM) 72 ELSE 73 ATTRIBUTE_VALUE = 0 74 75 DONE: 76 77 RETURN ATTRIBUTE_VALUE 78 79 /* ****************************************************************** * 80 * TROUBLE PROCESSING * 81 * ****************************************************************** */ 82 83 ERROR: 84 Parse source env exec_type exec_name . 85 86 IF MSG_ID <> ’’ Then 87 Call KATRAU16 msg_Id, msg_parms, exec_name 88 89 Msg_Parms = sigl ’probe processing.’ 90 Msg_Id = ’KAT0084E’ 91 Call KATRAU16 msg_Id, msg_parms, exec_name 92 93 Return -1

Probe Code Annotation



IntroductionIn this section, the probe code is broken up functionally. Where appropriate, the source lines are followed by a table containing an explanation of the lines of code. The source line numbers listed in the tables correspond to the line numbers in the left margin of the code.

REXX program headerThe first 20 lines of the program contain a REXX header.

Retrieving values from the probe managerThe following section of the program retrieves argument values from the Probe Manager.

1 /* REXX ************************************************************* * 2 * * 3 * PROGRAM: KATRA055 (PROB055) -- AMS PROBE: TSO RESPONSE TIME * 4 * * 5 * ARGUMENTS: DOMAIN_NAME * 6 * PROBE_ID * 7 * Status_item * 8 * @PROBE_MGR_vars * 9 * * 10 * INPUTS/OUTPUTS: SYSTEM VARIABLES FOR UP TO 4 STATUS ITEM NAMES * 11 * * 12 * DESCRIPTION: PROBE EXECUTED BY A TOD TRAP TO OBTAIN DATA FROM * 13 * DATAMG01 EVALUATE IT AND REACT. * 14 * * 15 * ------------------------------------------------------------------ * 16 * CHANGE LOG: * 17 * NAME DATE CHANGE * 18 * mpd 01/31/94 AT11110;REXX shared variables * 19 * * 20 * ****************************************************************** */

24 PARSE Arg pc +1, /* parse character */ 25 Domain_Name (pc) PROBE_ID (pc) status_item (pc) , 26 @PROBE_MGR_vars 27

Writing a Probe 325


Initializing error messagesThe following lines of code:

n use SIGNAL ON ERROR for error processing when a command in a probe fails to execute. The statement is included in this model probe to show its potential use: this probe does not include any commands.

n initializes two variables (MSG_PARMS and Msg_Id) used in the error routines included in this program

Source Line Description

24-25 The PARSE ARG statement retrieves the argument strings Domain_Name, probe_ID, and status_item, which are passed by the Probe Manager. Domain_Name and PROBE_ID will be used to build the shared variable name that will be searched for in the SYSTEM pool (see line 35).

The statement must be coded as shown. status_item is not required for this probe. While not used in this probe, the status item is included in this sample probe because it will be required in any probe that retrieves OG/MVS records from the SYSTEM pool. The arguments are described below:

Domain_Namedomain ID specified for the probe in the Probe Manager record.

probe_id Up to 8-character probe ID taken from the Probe Manager record.

status_item the OMEGAVIEW status item name.

26 @PROBE_MGR_vars reads the remainder of the passed arguments into a single string for subsequent parsing. (See lines 50-55.)

22 SIGNAL ON ERROR NAME ERROR 23 24 . 25 . 26 . 27 28 MSG_PARMS = ’’ 29 Msg_Id = ’’



Probe specific parametersThe following section of the program:

n uses the OG/MVS SHARVGET function to find and retrieve the compound variable @OGAT.Domain_Name.probe_id (for example, @OGAT.G.055) from the shared pool SYSTEM and stores it in the probe (local) pool so that it can determine the probe’s description

n terminates the routine and returns the SHARVGET return code value if it cannot find the compound variable in the SYSTEM pool

Retrieving the probe description from the SYSTEM poolIf the OG/MVS SHARVGET function executes successfully (see line 36) then the PARSE VAR statement is used to retrieve the probe description. The following section of the program retrieves the description value from the SYSTEM pool:


35-36 Sets up the compound variable name and calls the SHARVGET function to pass the compound variable to the local pool for the probe.

37-42 If the return code is not zero, the routine branches to this error code, which calls routine KATRAU16 to display an error message. (See lines 86 and 87.)

35 rsv_name = ’@OGAT.’Domain_Name’.’probe_id 36 r_c=SHARVGET("SYSTEM",rsv_name) 37 If r_c <> 0 Then 38 Do 39 msg_parms = rsv_name r_c 40 msg_Id = ’KAT0077E’ 41 Signal Error 42 End

43 Parse var @OGAT.Domain_Name.probe_id pc2 +1 , 44 prb_desc (pc2) . /* Get probe description */ 45

Writing a Probe 327


Retrieving status manager values and miscellaneous parametersThe following section of the program retrieves additional values from the Status Manager record, including the Miscellaneous Parameters field value. The PARSE VAR statements parse another section of the arguments passed by the Probe Manager now stored in @PROBE_MGR_vars and must be coded as shown.


50-53 This PARSE VAR statement passes the following arguments:

Default_statusThe default status of the item when no data is being transmitted by the probe: OK (green), Warning (yellow), Critical (red) or None.

Green_ValueA numerical limit or text string. The status item is OK if the value returned by the probe is less than or equal to this value.

Red_Value A numerical limit or text string. The status item is Critical if the value returned by the probe is greater than or equal to this value.

Log_MVupdate_codeA blank or single character code. If blank, status changes are not written to a log. Otherwise, the log code of the log to which status changes are written.

Probe_DirectiveUsed by query and heartbeat probes to analyze data from the Data Manager. In this case, this field identifies the TSO performance group.

MISC_PROBE_PARMSThe Miscellaneous Parameters field value.

46 /* ****************************************************************** * 47 * COLLECT DEFINITION PARAMETERS FROM SYSTEM VARIABLES * 48 * ****************************************************************** */ 49 50 PARSE Var @PROBE_MGR_vars , 51 Default_status (pc) Green_Value (pc) Red_Value (pc) , 52 Log_MVupdate_code (pc) Probe_Directive (pc) , 53 MISC_PROBE_PARMS (pc) . 54 55 PARSE VAR MISC_PROBE_PARMS PERIOD_NUM .



Retrieving the status item valueThe following section of the program specifies how to obtain the status item value from the data stored by the Data Manager. The value is unique to each probe. In this example, the routine obtains the status item value from a system variable created by the OMEGAMON for MVS Data Manager. (Other probes may issue a command directly to the managed object’s environment or interface with a different Data Manager.)

55 This PARSE VAR statement parses the Miscellaneous Probe Parameters field in the status manager record for this status item. This statement will vary from probe to probe depending on the Miscellaneous Probe Parameters (usually none) that are specified. For this example, there are four separate TSO response time periods that can be measured. The first value passed by the Probe Manager in the Miscellaneous Probe Parameters field tells the Probe Manager which time period to measure. This value is stored in (PERIOD_NUM) and the rest of the values in the Miscellaneous Probe Parameters string are ignored.


61 The OMEGAMON for MVS Data Manager creates a unique variable name for each status item value it obtains when it issues OMEGAMON commands. The variable names associated with TSO response time begin with the characters @TRT to which the DOMAIN_NAME value (see line 25) and Probe_Directive value (see line 52) are appended. You need to know the variable names the Data Manager uses to code this statement correctly.

57 /* ****************************************************************** * 58 * COLLECT DATA * 59 * ****************************************************************** */ 60 61 SYS_VAR_NAME = ’@TRT’||DOMAIN_NAME||Probe_Directive 62 DATAMG_DATA = KATRAF06(’G’ SYS_VAR_NAME) 63 IF DATAMG_DATA = -1 THEN 64 DO 65 RETURN ’NO_DATA’ 66 END 67 68 PARSE VAR DATAMG_DATA CMD_NAME VALUE1 VALUE2 VALUE3 VALUE4 . 69 70 IF VALUE(’VALUE’||PERIOD_NUM) > 0 THEN 71 ATTRIBUTE_VALUE = VALUE(’VALUE’||PERIOD_NUM) 72 ELSE 73 ATTRIBUTE_VALUE = 0 74

Writing a Probe 329


Returning the status item value to the probe managerThe RETURN ATTRIBUTE_VALUE statement on line 77 returns the value of the status item to the Probe Manager. Valid return code values are:

n NO_DATA

n YES

n NO

n a numeric value equal to or greater than zero

n a numeric value less than zero (which indicates an error condition)

To use the transient text feature to return additional user text to the probe manager for display on OMEGAVIEW, the statement needs to be

ATTRIBUTE_VALUE||(PC)||TEXT

where TEXT is a variable that you previously defined and contains the text you wish to display next to the OMEGAVIEW status item.

If the text field in OMEGAVIEW is shorter than the returned text, then the display will be truncated to the field length.

62 This statement invokes program KATRAF06 as a function, passing its action code G (for Get) and the Data Manager variable name for this status item. The probe stores the value returned by KATRAF06 in DATAMG_DATA.

KATRAF06 is a general-purpose routine that locates a variable and returns its value to the caller. KATRAF06 returns the value -1 if it cannot locate the variable. KATRAF06 might not be able to locate a variable if the target subsystem is not available, which means that no data can be collected for this status item.

63-66 If KATRAF06 returns a -1 value for this status item, the probe returns the value NO_DATA to the Probe Manager and then terminates. Otherwise, the probe parses the status item value obtained from the Data Manager variable.

In this case, the value is an entire OMEGAMON message, consisting of the name of the OMEGAMON command (CMD_NAME) that was issued to get the status item value as well as the TSO response time measurements for 4 time periods: VALUE1, VALUE2, VALUE3, and VALUE4.

70-73 This IF statement accesses the response time value for the period as specified by the Miscellaneous Probe Parameter PERIOD_NUM given for this status item in the Status Manager record (see line 55). If that value is greater than zero, the value is assigned to ATTRIBUTE_VALUE. If the value is zero or less, the value 0 is assigned to ATTRIBUTE_VALUE.



Processing errorsThe following section provides a template for a standard error routine that other probes can use. Various error conditions can be encountered when a probe accesses the OG/MVS environment. If an error occurs, your program should modify this template code to determine the error and place the appropriate error message text in the call to the message module routine KATRAU16.


84 This line gets the name of the exec so it can be passed to the Message Manager for display as the name of the module that issued the message.

86-87 These lines set up and call the message module routine KATRAU16 to process errors detected if the SHARVGET call fails (see lines 35-42).

91 This call to KATRAU16 issues a KAT0084E message identifying the part of the program that called the error routine.

93 This line returns a value of -1 to the Probe Manager. The Probe Manager will terminate the probe.

79 /* ****************************************************************** * 80 * TROUBLE PROCESSING * 81 * ****************************************************************** */ 82 83 ERROR: 84 Parse source env exec_type exec_name . 85 86 IF MSG_ID <> ’’ Then 87 Call KATRAU16 msg_Id, msg_parms, exec_name 88 89 Msg_Parms = sigl ’probe processing.’ 90 Msg_Id = ’KAT0084E’ 91 Call KATRAU16 msg_Id, msg_parms, exec_name 92 93 Return -1

PROBELIB Sample Probes 331

PROBELIB Sample Probes

Appendix OverviewThis appendix contains a catalog of the PROBELIB sample probes supplied with OSM/MVS.

Appendix ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Probe Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

B

Introduction


Introduction

DescriptionPROBELIB is in the dataset thilev.TKANCMD. For each probe, it provides:

n the program name

n probe type

n an identifying description

n a short description of how the probe works

n the probe directive (from the status item panels)

n threshold information

n additional parameters that have to be supplied

n the name of the data manager probe, if the probe services one

PreparationBefore using any of these probes with OSM/MVS, you need to copy them to REXXLIB. See “Copying Source Code for the New Probe” on page 271 for an example of the procedure.

For information on the REXXLIB-supplied probes, see “REXXLIB Probes and Status Items” on page 341.


Probe Catalog

Probe Catalog

PROBELIB ContentsThe following table lists and describes the sample probes made supplied in PROBELIB.

Program Name

Probe Type Description Function

KATRA002 Q MVS TSO User Count

Monitors the total number of active TSO users. No probe directive is necessary; the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of users at the green and red levels.

KATRA004 Q TSO User Counts Monitors the total number of logged on TSO users by TSO ID group. The probe directive contains a mask, identifying the first n characters of the TSO ID group to be counted. No wild card characters are allowed. The system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of users at green and red levels.

KATRA006 Q CPU Percent Utilization

Monitors the CPU utilization as determined by the OMEGAMON MVS RCPU command. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the utilization percentage at green and red levels. This probe is serviced by the OMEGAMON for MVS Data Manager probe.

KATRA007 Q CPU Page Rates Monitors the CPU paging rate as determined by the OMEGAMON MVS RPAG command. No probe directive is necessary; the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the page rate at green and red levels. This probe is serviced by the OMEGAMON for MVS data manager probe.

KATRA008 Q DASD Volume Response Rate

Monitors the response rate of a particular DASD volume or volume grouping as determined by the OMEGAMON for MVS XDSK command. The probe directive contains a mask, identifying the first n characters of the DASD volume or group to be measured. No wild card characters are allowed. Thresholds should be specified at the response rate at green and red levels. This probe is serviced by the OMEGAMON for MVS data manager probe.

Probe Catalog


KATRA010 E Batch Job Event Monitors a batch job to determine if the job is executing normally. The probe directive is the jobname. Thresholds should be specified for the each status item at green and red levels.

KATRA020 E VTAM Node Monitor

This event probe monitors VTAM alerts that indicate the failure of a VTAM node on a specified system and domain. The probe directive is the node name. Thresholds should be specified as "YES" (the node failed) and "NO" (the node is OK).

KATRA021 E VTAM Node Performance Monitor

This event probe monitors VTAM alerts that show degraded performance on a VTAM node on a specified system and domain. The probe directive is the node name. Thresholds should be specified as "YES" (the node is performing poorly) and "NO" (the node is OK.)

KATRA031 Q CICS End-to-End Response Time

This probe monitors the end-to-end response time for the CICS region, as determined by the OMEGAMON for CICS TIMELU command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the response time at green and red levels. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

KATRA032 Q CICS Storage Violation

This probe monitors the CICS region for storage violations, as determined by the OMEGAMON for CICS STOR command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the number of violations at green and red levels. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

KATRA033 Q CICS OSCOR Free This probe monitors the CICS region for OSCOR statistics, as determined by the OMEGAMON for CICS STOR command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the amount of free OSCOR space at green and red levels. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

Program Name



Probe Catalog

KATRA034 Q CICS DSA Free This probe monitors the CICS region for DSA statistics, as determined by the OMEGAMON for CICS STOR command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the amount of free DSA space at green and red levels. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

KATRA035 Q CICS EDSA Free This probe monitors the CICS region for EDSA statistics, as determined by the OMEGAMON for CICS STOR command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the amount of free EDSA space at green and red levels. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

KATRA036 Q CICS VSAM Waits This probe monitors the CICS region for VSAM file access waits, as determined by the OMEGAMON for CICS CVSW command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the existence of a VSAM wait as "NO" for green and "YES" for red. This probe is serviced by the OMEGAMON for CICS Data Manager probe.

KATRA051 Q MVS Batch Job Count

This probe monitors the total number of active batch jobs. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of jobs at green and red levels.

KATRA052 Q MVS Started Task Count

This probe monitors the total number of started tasks. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of started tasks at green and red levels.

KATRA053 Q Tape Mount Requests Count

This probe monitors the total number of outstanding tape mount requests. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of requests at green and red levels.

Program Name


Probe Catalog


KATRA054 Q Intervention Required Count

This probe monitors the total number of outstanding intervention required requests. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the number of requests at green and red levels.

KATRA071 Q TSO User Group End-to-End Group Transaction Rate

This probe monitors the total end-to-end response time for a TSO user group, as determined by the OMEGAMON for MVS ZRTA command. The probe directive is a TSO user ID or ID mask. Thresholds should be specified for the response times at green and red levels. This probe is serviced by the OMEGAMON/ETE Data Manager probe.

KATRA072 Q TSO User Group End-to-End Host Response Time

This probe monitors the host portion of total end-to-end response time for a TSO user group, as determined by the OMEGAMON for MVS ZRTA command. The probe directive is a TSO user ID or ID mask. Thresholds should be specified for the response times at green and red levels. This probe is serviced by the OMEGAMON/ETE Data Manager probe.

KATRA073 Q TSO User Group End-to-End Network Response Time

This probe monitors the network portion of total end-to-end response time for a TSO user group, as determined by the OMEGAMON for MVS ZRTA command. The probe directive is a user ID or ID mask. Thresholds should be specified for the response times at green and red levels. This probe is serviced by the OMEGAMON/ETE Data Manager probe.

KATRA074 Q Sysplex Query The probe uses the D XCF command to see if the system specified in the probe directive is known within the Sysplex. The probe directive is the system ID. Thresholds should be specified as "YES" for OK and "NO" for CRITICAL.

KATRA080 X DAS CPU Utilization Percentage (UNIX)

This probe monitors the CPU utilization percentage of a distributed (UNIX/AIX) system. No probe directive is necessary as the system and domain IDs specify the system to be monitored. Thresholds should be specified for the utilization percentage at green and red levels. This probe is controlled by the DAS Data Manager probe. The command used to obtain the CPU percentage available must be specified in the DAS definitions command line.

Program Name



Probe Catalog

KATRA083 X DAS CPU Utilization Percentage (non-UNIX)

This probe monitors the CPU utilization percentage of a distributed (non-UNIX/AIX) system. No probe directive is necessary as the system and domain IDs specify the CPU to be measured. Thresholds should be specified for the utilization percentage at green and red levels. This probe is controlled by the DAS Data Manager probe. The command used on the distributed system to obtain the CPU percentage used must be specified in the DAS definitions command line.

KATRA101 Q JES2 Spool Utilization

The probe returns the percentage of spool utilization from the $DSPL. The probe directive is the SPOOL VOLSER or a blank. Blank means return the total spool utilization. Thresholds should be specified as 70 for OK and 90 for CRITICAL.

KATRA102 Q JES2 NJE Line Status

The probe monitors the status of an NJE LINE. The probe directive is the integer LINE number without leading zeros. Thresholds should be specified as 2 for OK and 4 for CRITICAL.

KATRA103 Q JES2 Job Class Queue Depth

The probe monitors JES2 job class queue depth. The probe directive is the JES2 job class. Thresholds should be specified at OK and CRITICAL levels for the queue depth.

KATRA107 Q TSO Users Active The probe determines the status of the MVS "active" job and monitors status changes. When the probe starts, either active (YES) or not active (NO) is returned. When the probe stops, NO_DATA is returned. The probe directive is a 1 to 8 character Job Name. Thresholds should be specified as "YES" for Threshold OK and "NO" for Threshold CRITICAL.

KATRA109 Q Pending VTAM Nodes

This query probe monitors the pending status of VTAM nodes. The probe directive is the VTAM node name. Thresholds should be specified as 3 for OK and 6 for CRITICAL.

Program Name


Probe Catalog


KATRA111 Q IMS PSB Status The probe obtains data from the OMEGAMON Generic Data Manager, and returns an attribute value for the status item. The probe directive is the OMEGAMON/IMS session name. Miscellaneous probe parameters provide the OMEGAMON commands to be issued. Multiple commands must be separated by semicolons. Thresholds should be specified as "YES" for OK and "NO" for CRITICAL. This probe is serviced by the OMEGAMON Generic Data Manager.

KATRA112 Q Get Number of TSO Users

The probe obtains data from the OMEGAMON Generic Data Manager, and returns an attribute value for the status item. The probe directive is the OMEGAMON/MVS session name. Thresholds should be specified for OK and CRITICAL which represent numbers of TSO users. This probe is serviced by the OMEGAMON Generic Data Manager.

KATRA114 Q Get CICS File Status

The probe obtains data from the OMEGAMON Generic Data Manager, and returns an attribute value for the status item. The probe directive is the OMEGAMON session name. Miscellaneous probe parameters are OMEGAMON commands separated by semicolons. Thresholds should be specified as 0 for OK and 2 for CRITICAL. This probe is serviced by the OMEGAMON Generic Data Manager.

KATRA119 E Generic OMEGAMON Single Exception

The event probe monitors single line OMEGAMON exceptions. Thresholds should be specified as "NO" OK (the exception has not occurred) and as "YES" for CRITICAL (the exception has occurred.)

KATRA121 D OMEGAMON for DB2 Data Manager

The probe monitors information from DB2 for a specified plan and returns the elapsed time, thread CPU time, and DB2 getpage rates.

KATRA122 Q DB2 Thread Elasped Time

The probe obtains data from the OMEGAMON for DB2 Data Manager, evaluates it, returns the current status item value, then updates OMEGAVIEW. The probe directive is the DB2 plan name. Thresholds should be specified for the elapsed time (hh:mm:ss) at the OK and CRITICAL levels. This probe is serviced by the DB2 Data Manager probe.

Program Name



Probe Catalog

KATRA123 Q DB2 Thread Time Total

The probe obtains data from the OMEGAMON for DB2 Data Manager, evaluates it, returns the current status item value, then updates OMEGAVIEW. The probe directive is the DB2 plan name. Thresholds should be specified for the elapsed time (hh:mm:ss) at the OK and CRITICAL levels. This probe is serviced by the OMEGAMON DB2 Data Manager probe.

KATRA124 Q DB2 Thread CPU Time

The probe obtains data from the OMEGAMON for DB2 Data Manager, evaluates it, returns the current status item value, then updates OMEGAVIEW. The probe directive is the DB2 plan name. Thresholds should be specified for the elapsed time (hh:mm:ss) at the OK and CRITICAL levels. This probe is serviced by the OMEGAMON for DB2 Data Manager.

KATRA125 Q DB2 Transplex Plan Getpages Rate

The probe obtains the transplex read I/O page rate. The probe directive is the DB2 plan name. Thresholds should be specified for the OK and CRITICAL page rates. This probe is serviced by the OMEGAMON for DB2 Data Manager.

KATRA919 E OMEGAMON Event Probe

The event probe monitors single line OMEGAMON exceptions. Thresholds should be specified as "NO" for OK (the exception has not occurred) and as "YES" for CRITICAL (the exception has occurred.)

KATRAM04 D OMEGAMON/End-to-End Data Manager

Retrieves data for each End-to-End probe. M04 manages probes 71, 72, and 73.

KATRAM10 D OMEGAMON Generic Data Manager

The probe monitors OMEGAMON generic data. This data manager services the probes KATRA111, KATRA112 and KATRA114.

KATRAM11 D OMEGAMON MVS Data Manager - Part 2

The probe is a probe manager that retrieves the FREE and CONTIG space in cylinders for a DASD volume. The probe directive is the VOLSER of the DASD volume. Miscellaneous probe parameters contain SPACE, CONTIG or blanks where SPACE and blank request the free space and CONTIG requests the largest contiguous block.

Program Name


Probe Catalog


REXXLIB Probes and Status Items 341

REXXLIB Probes and Status Items

Appendix OverviewThis appendix contains a catalog of the REXXLIB sample probes and their corresponding status items supplied with OSM/MVS. REXXLIB is in the dataset hilev.TKANEXEC.

For each probe, it provides:

n the probe identifier

n the probe type

n an identifying description

n the status item name

n a short description of how the probe works

n the probe directive (from the status item panels)

n threshold information

n additional parameters that have to be supplied

n the name of the data manager probe, if any, and the probe services.

Note: Probes 998 and 999, the Peer Link and Situation Manager probes are used for internal purposes by OSM/MVS and cannot be copied or modified.

Appendix ContentsUsing PROBELIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342Probe Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

C

Using PROBELIB


Using PROBELIB

DescriptionA sample library of additional probes, PROBELIB, is supplied with OSM/MVS. These probes must be copied to REXXLIB before they can be used. See “PROBELIB Sample Probes” on page 331 for a list of those probes.


Probe Catalog

Probe Catalog

REXXLIB ProbesThe following table lists the probes that must be copied from PROBELIB to REXXLIB before they can be used.

Probe ID

Probe Type Description Status Item Name Function

M01 D OMEGAMON for MVS Data Manager

- Submits the OMEGAMON commands to OMEGAMON for MVS and creates system variables and log entries from the data returned. No probe directive is necessary.

M01 manages the probes KATRA055, KATRA056, KATRA006, KATRA007, KATRA008, and KATRA009.

M02 D OMEGAMON for CICS Data Manager

- Submits the OMEGAMON commands to OMEGAMON for CICS and creates system variables and log entries from the data returned. No probe directive is necessary.

M03 D OMEGAMON for MVS Data Manager

- Submits the OMEGAMON commands to OMEGAMON for MVS and creates system variables and log entries from the data returned. No probe directive is necessary.

M03 manages probe KATRA066.

Probe Catalog


M05 M Data Manager (DAS only)

- Creates, stops and starts DAS and establishes traps to issue commands, which cause probes to fire. It communicates with OG/OS2 through the MVS console. No probe directive is necessary.

009 Q TSO Users Count TSO_USER_COUNT_210

Monitors, by performance group, the number of TSO users that are logged on. The probe directive contains the performance group number. Thresholds should be specified for the number of users at green and red levels. This probe is serviced by OMEGAMON for MVS Data Manager (M01).

028 H VTAM Node Heartbeat VTAM_NODE_HRTBEAT

Checks for the availability of a specific VTAM node on the specified system and domain. The probe directive is the VTAM node name. A VTAM D NET command is issued for the specified node. Thresholds should be specified as active (yes) or inactive (no).

Probe ID



Probe Catalog

030 Q CICS Response Time CICS_RESP_TIME Monitors the response time for the CICS region, as determined by the OMEGAMON for CICS TIME command. No probe directive is necessary as the system, domain, and environment IDs specify the CICS region to be measured. Thresholds should be specified for the response time at green and red levels. This probe is serviced by the OMEGAMON for CICS data manager probe.

050 H MVS Active Task Heartbeat

ACTIVE_TASK_VTAM Checks for the existence of a specific started task on the specified system and domain. The probe directive is the started task name. Thresholds should be specified as green (no) and red (yes).

055 Q TSO Response Time TSO_RESP_TIME Monitors the TSO response times by performance group, as determined by the OMEGAMON for MVS PRSP command. The probe directive contains the performance group to be measured. The Miscellaneous Parameters field contains the TSO Period Number (1 to 4). Thresholds should be specified for the response time at green and red levels. This probe is serviced by the OMEGAMON for MVS data manager probe.

Probe ID


Probe Catalog


056 Q TSO Transaction Rate TSO_RATE_GRP_210 Monitors the TSO transaction rates by performance group, as determined by the OMEGAMON for MVS PRTR command. The probe directive contains the performance group to be measured. The Miscellaneous Parameters field contains the TSO Period Number (1 to 4). Thresholds should be specified for the transaction rate at green and red levels. This probe is serviced by the OMEGAMON for MVS data manager probe.

066 Q CPU Utilization CPU.TDAFS02 Monitors CPU utilization. Thresholds should be specified at OK, WARNING and CRITICAL levels. This probe is serviced by the OMEGAMON for MVS Data Manager probe (M03).

081 X DAS RS6000 Heartbeat RS6000_HRTBEAT Monitors the status of an RS6000. No probe directive is necessary as the system and domain IDs specify the system to be measured. Thresholds should be specified for yes and no values at green and red levels. This probe is controlled by the DAS data manager probe. The command used to obtain the current date must be specified in the DAS parameter settings.

Probe ID



Probe Catalog

082 X DAS LAN Server Heartbeat

NOVELL_LAN Monitors the status of a Novell LAN server. The probe directive specified the server name. Thresholds should be specified for yes and no values at green and red levels. This probe is controlled by the DAS data manager probe. An XLATE routine is used to preprocess the response to a Novell SLIST command.

990 O System Maintained Status Item Manager

- Checks to see if a status item has changed color based on a request by an OMEGAMON and manages the response.

998 T Peer Link P2_SELF_CHK Checks the connection between peer links. This probe is serviced by the DAS Probe Manager.

999 S Situation Manager FIRSTSIT Evaluates situation logic and updates the status of situation status items.

Probe ID


Probe Catalog


Using the SHOWOSM Command 347

Using the SHOWOSM Command

Appendix OverviewThis appendix describes the SHOWOSM command.

Appendix ContentsPurpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348SHOWOSM Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

D

Purpose


Purpose

DescriptionThe SHOWOSM command serves two primary purposes:

1. It provides a composite of all the settings and definitions that have been defined in the user interface.

2. It displays dynamic OSM/MVS runtime information, providing more information for problem diagnosis.

Note: OSM/MVS must be active in order to execute the SHOWOSM command. The output from the SHOWOSM command is written to the OG MSGLOG only.

This section shows the command format and provides a general description of the SHOWOSM command and its options. Examples of command output follow the description section. For detailed explanations regarding any of the command types, for example, probes, see the appropriate section in this manual.


SHOWOSM Command

SHOWOSM Command

FormatThe format for the SHOWOSM command is:.

Note: The minimum number of characters that must be specified are displayed above in uppercase.

subsys Types: ALL PRObes DATAMgrs STATusitems EXCEptions DASstat SITuations SESSions SYStems PEER REMOte LOGcodes MVpanels INCIDents BUSYUsers USERS ROTList NOTList RECommend REFresh MISC Type name (optional): You can qualify the type with a specific name or name prefix for probes, data managers, status items, situations, and distributed status items. Options: DETAIL

subsys type(name)

>< SHOWOSM

option/s

SHOWOSM Command


ParametersThe SHOWOSM command parameters are described below.:

subsys This is the name of the OMEGACENTER address space where you want the command to execute. The subsys name is assigned by the SUBSYS startup parameter.

(No operand) The SHOWOSM command issued with no type defaults to the ALL type, displaying all information.

PROBES Displays information for all active probes, unless you specify a probe name or prefix.

DATAMGRS Displays information for all data managers, unless you specify a data manager ID or prefix.

STATUSITEMS Displays status item information and dynamic information for all status items, unless you specify a status item name or prefix.

EXCEPTIONS Displays information for all OMEGAMON exception data probes, unless you specify a name or prefix.

DASSTAT Displays status item information and dynamic information for all distributed system status items, unless you specify a status item name or prefix.

SITUATIONS Displays situation information and dynamic information for all situations, unless you specify a situation name or prefix.

SESSIONS Displays information about all defined VTAM sessions.

SYSTEMS Displays information about all defined MVS systems.

PEER Displays information about all defined peer systems.

REMOTE Displays information about all DAS console, or AF/REMOTE, systems.

LOGCODES Displays log definitions and shows which dataset information is written to.

MVPANELS Displays the contents of the special OMEGAVIEW panels defined in the user interface, for example, worklist, exception and notify rows.

INCIDENTS Displays incident information about all current incidents.

BUSYUSERS Displays the users who are currently processing incidents.

USERS Displays all the users defined in the user interface.

ROTLIST Displays the rotation lists defined in the user interface.

NOTLIST Displays the notification lists defined in the user interface.

RECOMMEND Displays recommendation codes.

REFRESH Displays active Refresh/Shutdown requests.

MISC Displays miscellaneous items, such as a report of when certain actions occurred or preferences you have selected.


SHOWOSM Command

ExamplesThe list below shows some examples of the use of the SHOWOSM command.

optional parameters

DETAIL This is an optional parameter. It provides detailed information about each type displayed. If you do not specify detail, a short form of the display is shown.

Command Meaning

SHOWOSM Displays all types

SHOWOSM PROBES

Displays all probes

SHOWOSM PROBES(119)

Displays probe 119

SHOWOSM ALL DETAIL

Displays detailed information for all types

SHOWOSM STAT DETAIL

Displays detailed information for status items

Messages


Messages

DescriptionA list of the new messages associated with the SHOWOSM command is shown below.

MessagesKAT0161I SHOWOSM P1

Explanation: This message is issued in response to the SHOWOSM command. It echoes the command and indicates the beginnning of the command response.

System Action: Processing continues.

User Response: None. This is an informational message only.

KAT0162I SHOWOSM DISPLAY COMPLETE

Explanation: This message is issued in response to the SHOWOSM command. It indicates the end of the command display.



KAT0163I SHOWOSM EXTRANEOUS PARAMETERS IGNORED: P1

Explanation: A SHOWOSM command was issues. The command contained extra parameters that were not part of the SHOWOSM syntax.

System Action: Processing continues. The SHOWOSM command is executed.


KAT0164E SHOWOSM INVALID SYNTAX: P1

Explanation: A SHOWOSM command was issued. The command contained invalid parameters that could not be processed.

System Action: Processing continues. THE SHOWOSM command is not executed.

User Response: Reissue the SHOWOSM command with the valid syntax.

KAT0165I SHOWOSM - OSM/MVS IS NOT CURRENTLY ACTIVE, NO DATA TO DISPLAY

Explanation: A SHOWOSM Command was issued. OSM/MVS was not active, therefore there was no data to display showing the current status. OSM/MVS msut be active in order to execute the SHOWOSM command.


User Response: Start OSM/MVS, then reissue the SHOWOSM command.


Examples

Examples

SHOWOSM ALL ExampleBelow is an example of the output generated by the SHOWOSM ALL command.

KAT0161I SHOWOSM ALL:-------------------------------------PROBES-------------------------------------Probe-Type-Domain---Program--Interval--Description---------------------301 E G KATRA301 OM Exception Event Probe040 Q G KATRA040 180 Dependent probe of M10 Data MngrM10 D G KATRAM10 180 OMEGAMON/MVS Data Manager999 S G KATRAU90 60 Situation Manager (G)4 PROBES SHOWN---------------------------------DATA MANAGERS----------------------------------Probe--Domain--Interval--Session--Dependent ProbesM10 G 120 OMV3 0401 DATA MANAGER SHOWN----------------------------------STATUS ITEMS---------------------------------- Current Current Crit OK Default-----Status Item------Probe Id----Color----Value----Thrshd---Thrshd---Status---SYSG_XCSA 301 YELLOW 52 75 50 BLUESYSG_XREP 301 RED 14 10 5 BLUESYSG_EXCEPTION_SIT 999 GREEN FALSE TRUE FALSE BLUE3 STATUS ITEMS SHOWN------------------------------OMEGAMON EXCEPTIONS------------------------------- Additional-----Status Item-----Exception-Threshold-Timeout-ParametersSYSG_XCSA XCSA 4096 900SYSG_XREP XREP 20 452 EXCEPTIONS SHOWN--------------------------------DAS STATUS ITEMS----------------------------------Status Item--------DSysid---Type-Probe-PrbDmn---PrbFreq--InitL1_LAN L1 L 083 L1 600 YL2_LAN_2 L2 L 083 L1 300 Y2 DAS STATUS ITEMS SHOWN-----------------------------------SITUATIONS----------------------------------- Current Current---Situation----------Color----Value-----Warning---SYSG_USER_SIT RED FALSE NSYSG_EXCEPTION_SIT GREEN FALSE N2 SITUATIONS SHOWN------------------------------------SESSIONS-------------------------------------Session-T-Applid--Connctd-Interval-Description---------------------------------OMV3 M TESTVTAM N 00:03:00 OMEGAMON for MVS on System GOMVWG W MVATGSDM Y 00:02:00 OMEGAVIEW on SYSG2 SESSIONS SHOWN------------------------------------SYSTEMS--------------------------------------System--T-AOLINKID-Focal-SYSNAME-SUBSYS-Echo-MajNode--MSMFNode-MSMF-LogonID--G M SYSG Y SYSG OKP1 5 ARGAT999 RGAT1230 Y SYSGB M SYSB N SYSB OKP1 120 ARBAT999 RBAT999P Y USR1352 SYSTEMS SHOWN----------------------------------PEER SYSTEMS-----------------------------------System--AOLINKID-SYSNAME--SUBSYS--Prim-Sec-Last_Updated-Ntfy_Sys-Curr_Stat---G SYSG SYSG OKP1 Y 14:10:15 G ActiveB SYSB SYSB OKP1 Y2 PEER SYSTEMS SHOWN

Examples


-------------------------------AF/REMOTE SYSTEMS---------------------------------System--Cons-Beep-Route_Code---G 6D5 Y 171 AF/REMOTE SYSTEM SHOWN

-----------------------------------LOG CODES------------------------------------Log-Dest-DDname---CurrentDSN-DSNames--------------N D NOTIFYDD 1 USR1.OG9401.RKATLS01 USR1.OG9401.RKATLS02 USR1.OG9401.RKATLS031 LOG CODES SHOWN----------------------------OMEGAVIEW SPECIAL PANELS----------------------------WORKLIST1: Problem--Time------Description-------------------------------------Notify 01 14:10:12 101 SPOOL_USAGE_1 SPOOL CRITICAL YEXCEPTION1: Resource--Description---Status SPOOL JES Spool CRITICAL SPOOL_USAGE_1 R TSO_USEA USR135A CRITICAL ACTIVE_USER_USR135A R3 ROWS FROM OMEGAVIEW SPECIAL PANELS SHOWN------------------------------------USERIDS-------------------------------------UserID---User Name----------------------T-Pager Phone----------Pager Number-----USER01 Joe Smith 555-1234USER02 Sue Jones 555-12332 USERIDS SHOWN---------------------------------ROTATION LISTS---------------------------------RotList--Active_UserID--User Name---------------------@ROTCSC user01 Joe Smith1 ROTATION LIST SHOWN ------------------------------NOTIFICATION GROUPS-----------------------Group--UserID---User Name----------------------Escalate-Type-Next---------------CICS USER01 Joe Smith 120 BEEP USER02 Sue Jones 120 BEEP 1 NOTIFICATION GROUP SHOWN ------------------------------RECOMMENDATION CODES------------------------------0001 Re-Activate VTAM Node Contact Network System Programmer 1 RECOMMENDATION CODE SHOWN ---------------------------REFRESH/SHUTDOWN REQUESTS---------------------------- 0 REFRESH/SHUTDOWN REQUESTS SHOWN -----------------------------------INCIDENTS------------------------------------Incident-Status Item----------Prb-LastNtfd----------Received-Notification Text--G_00001 STAT1_OSM_SPOOL_1 101 USER01 SPOOL_1 Critical 1 INCIDENT SHOWN-----------------------------------BUSYUSERS------------------------------------Userid---Incident-Status Item--------- 0 BUSYUSERS SHOWN


Examples

SHOWOSM ALL DETAIL ExampleBelow is an example of the output generated by the SHOWOSM ALL DETAIL command.

------------------------------MISCELLANEOUS ITEMS-------------------------------SPECIFIED DEFAULTS: Default trap prefix : @T Default P2P trap prefix : @P Peerlink interval time : 300 Default DDNAME prefix : @F VTAM retry logon interval: 300 Desired MATINFO setting : ON Update special panels : YES Special panel refresh int: 240 OSM runtime table Lib: SYSG.OG999.RKANISP Dflt auto-resolution time: 120 Primary Notify System : G Secondary Notify System : B Default Notification Text: 0123456789SYSTEM STATUS: Last incident number : 00003 MV init panel update time: 10/31/95 14:07:44 Last MV panel update time: 10/31/95 14:09:19 @OGAT.@GATEWAY_INDEX : 0 17 MISCELLANEOUS ITEMS SHOWN KAT0162I SHOWOSM display complete

KAT0161I SHOWOSM ALL DETAIL:-------------------------------------PROBES-------------------------------------301: OM Exception Event Probe W/Text TYPE.... E DOMAIN... G START... 00:00:00 LOG..... PROGRAM.. KATRA301 STOP.... INTERVAL SESSION.. TRAP_NAMES: @T301001 STATUS_ITEMS: SYSG_XCSA COLOR... YELLOW VALUE... 52 SYSG_XREP COLOR... RED VALUE... 14 M10: OMEGAMON/MVS Data Manager (G) TYPE.... D DOMAIN... G START... 00:00:00 LOG..... PROGRAM.. KATRAM10 STOP.... INTERVAL 180 SESSION.. OMV3 DEPENDENT_PROBES: 040 010 TRAP_NAMES: @TM10001 2 PROBES SHOWN

Examples


---------------------------------DATA MANAGERS----------------------------------M10: DOMAIN.. G SESSION. OMV3 INTERVAL 180 DEP_PROB 040 010 PROBE(010): STATITEM.. SYSG_TSOUSERS MISCPRMS.. #TSOJ DataManager Variables: #TSOJ 46 1 DATA MANAGER SHOWN----------------------------------STATUS ITEMS---------------------------------- SYSG_XCSA: XCSA OM Exception PROBE... 301 COLOR.... YELLOW VALUE... 52 DOMAIN.. G DEFCOLOR. BLUE OK_THR.. 50 PNLMGMT. N LOG...... CRIT_THR 95 DIAGRTN. DIAGFLAG. N TEXTTYPE Transient Text PRB_DIR. OMV3 MISC_PRM XCSA TEXT.... 52 OMV3 OK ACTIVITY: Work_Lists: FLAGS... N N N TEXT.... Exception_Lists: FLAGS... N N N N N ACTION.. STATUS.. NAME.... DESC.... Notification: INCIDENT N CODE.... REC_CODE ALTPGM.. ALTPGM1 PRIO.... Escalate Until Available TEXT.... Action/Followup: ACTION.. FOLLOWUP CRITICAL ACTIVITY: Work_Lists: FLAGS... N N N TEXT.... Exception_Lists: FLAGS... N N N N N ACTION.. STATUS.. NAME.... DESC.... Notification: INCIDENT N CODE.... REC_CODE ALTPGM.. ALTPGM1 PRIO.... Escalate Until Available TEXT.... Action/Followup: ACTION.. FOLLOWUP WARNING ACTIVITY: Work_Lists: FLAGS... N N N TEXT.... Exception_Lists: FLAGS... N N N N N ACTION.. STATUS.. NAME.... DESC....


Examples

Notification: INCIDENT N CODE.... REC_CODE ALTPGM.. ALTPGM1 PRIO.... Escalate Until Available TEXT.... Action/Followup: ACTION.. FOLLOWUP NONE ACTIVITY: Work_Lists: FLAGS... N N N TEXT.... Exception_Lists: FLAGS... N N N N N ACTION.. STATUS.. NAME.... DESC.... Notification: INCIDENT N CODE.... REC_CODE ALTPGM.. ALTPGM1 PRIO.... Escalate Until Available TEXT.... Action/Followup: ACTION.. FOLLOWUP 1 STATUS ITEMS SHOWN------------------------------OMEGAMON EXCEPTIONS----------------------- Additional-----Status Item-----Exception-Threshold-Timeout-ParametersSYSG_XCSA XCSA 4096 900SYSG_XREP XREP 20 452 EXCEPTIONS SHOWN--------------------------------DAS STATUS ITEMS------------------------STAT1_LAN: PROBE... 083 TYPE.... L DISTSYS. L1 FREQ.... 600 INIT.... Y DOMAIN.. L1 VAL_OFF. 0 VAL_SIZE 5 TRAN_RTN MYROUTIN LOG..... A COMMAND. SLIST 1 DAS STATUS ITEMS SHOWN-----------------------------------SITUATIONS-----------------------------------SYSG_USER_SIT: COLOR... RED VALUE... FALSE INIT.... Y WARNING. N ---StatItem---------Comp-Value----------------And/Or-Color--Value--- -------- SYSG_ACTIVE_USER1 STEQ OK AND GREEN NO SYSG_ACTIVE_USER2 STEQ OK RED NO SYSG_EXCEPTION_SIT: COLOR... GREEN VALUE... FALSE INIT.... Y WARNING. N

Examples


----StatItem---------Comp-Value----------------And/Or-Color--Value----------- SYSG_XACP VLEQ YES AND GREEN NO SYSG_PATM VLEQ YES RED YES 2 SITUATIONS SHOWN------------------------------------SESSIONS------------------------------------OMV3: OMEGAMON for MVS on System G APPLID.. TESTVTAM TYPE.... M LOGDATA. LROWS=300 INTERVAL 00:03:00 CONNCTD. N OMVWG: OMEGAVIEW on SYSG TDAFS07 APPLID.. MVATGSDM TYPE.... W LOGDATA. INTERVAL 00:02:00 CONNCTD. Y 2 SESSIONS SHOWN ------------------------------------SYSTEMS--------------------------------------System--T-AOLINKID-Focal-SYSNAME-SUBSYS-Echo-MajNode--MSMFNode-MSMF-LogonID---- G M SYSG Y SYSG OKP1 5 ARGAT999 RGAT1230 Y SYSG B M SYSB N SYSB OKP1 120 ARBAT999 RBAT999P Y USR135 2 SYSTEMS SHOWN ----------------------------------PEER SYSTEMS-----------------------------------System--AOLINKID-SYSNAME--SUBSYS--Prim-Sec-Last_Updated-Ntfy_Sys-Curr_Stat----- G SYSG SYSG OKP1 Y 14:10:15 G Active B SYSB SYSB OKP1 Y 2 PEER SYSTEMS SHOWN -------------------------------AF/REMOTE SYSTEMS---------------------------------System--Cons-Beep-Route_Code--- G 6D5 Y 17 1 AF/REMOTE SYSTEM SHOWN -----------------------------------LOG CODES------------------------------------LOG(N): DEST.... D DDNAME.. NOTIFYDD MAXREX.. 100000 CURRENT. 1 LOGCNT.. 14 SWAPSTAT DATASET NAMES: USR1.OG9401.RKATLS01 USR1.OG9401.RKATLS02 USR1.OG9401.RKATLS03 1 LOG CODE SHOWN


Examples

----------------------------OMEGAVIEW SPECIAL PANELS----------------------------WORKLIST1: Problem--Time------Description-------------------------------------Notify 01 14:10:12 101 SPOOL_USAGE POOL CRITICAL YEXCEPTION1: Resource--Description---Status SPOOL JES Spool CRITICAL SPOOL_USAGE R TSO_USEA USR135A CRITICAL SYSG_USER_SIT REXCEPTION2: Resource--Description---Status SPOOL JES Spool CRITICAL SPOOL_USAGE R 7 ROWS FROM OMEGAVIEW SPECIAL PANELS SHOWN ------------------------------------USERIDS-----------------------------------------UserID---User Name----------------------T-Pager Phone----------Pager Number---------USER01 Joe Smith 555-1234 USER02 Sue Jones 555-1233 2 USERIDS SHOWN ---------------------------------ROTATION LISTS-------------------------------------RotList--Active_UserID--User Name--------------------- @ROTCSC USER01 Joe Smith 1 ROTATION LISTS SHOWN ------------------------------NOTIFICATION GROUPS-----------------------------------Group--UserID---User Name----------------------Escalate-Type-Next CICS USER01 120 BEEP USER02 120 BEEP 1 NOTIFICATION GROUP SHOWN ------------------------------RECOMMENDATION CODES---------------------------------- 0002 Re-Activate VTAM Node Contact Network System Programmer 1 RECOMMENDATION CODE SHOWN ---------------------------REFRESH/SHUTDOWN REQUESTS-------------------------------0 REFRESH/SHUTDOWN REQUESTS SHOWN-----------------------------------INCIDENTS------------------------------------G_00001: PROBE... 101 COLOR... RED STATITEM SPOOL_USAGE GROUP... TEST NOTIFIED USR135A PRIO.... Escalate Until Available SEQ#.... 1 RECEIVED TEXT.... SPOOL_1 Critical 1 INCIDENT SHOWN

Examples


-----------------------------------BUSYUSERS------------------------------------Userid---Incident-Status Item--------- 0 BUSYUSERS SHOWN------------------------------MISCELLANEOUS ITEMS-------------------------------SPECIFIED DEFAULTS: Default trap prefix : @T Default P2P trap prefix : @P Peerlink interval time : 300 Default DDNAME prefix : @F VTAM retry logon interval: 300 Desired MATINFO setting : ON Update special panels : YES Special panel refresh int: 240 OSM/MVS runtime table Lib: SYSG.OG999.RKANISP Dflt auto-resolution time: 120 Primary Notify System : G Secondary Notify System : B Default Notification Text: 0123456789SYSTEM STATUS: Last incident number : 00003 MV init panel update time: 10/31/95 14:07:44 Last MV panel update time: 10/31/95 14:09:19 @OGAT.@GATEWAY_INDEX : 0 17 MISCELLANEOUS ITEMS SHOWN KAT0162I SHOWOSM display complete

Guide to Candle Customer Support 361

Guide to CandleCustomer Support

IntroductionCandle Corporation is committed to producing top-quality software products and services. To assist you with making effective use of our products in your business environment, Candle is also committed to providing easy-to-use, responsive customer support.

Precision, speed, availability, predictability—these terms describe our products and Customer Support services.

Included in this Guide to Candle Customer Support is information about the following:

Base Maintenance Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362– Telephone Support

– eSupport

– Description of Severity Levels

– Service-level objectives

– Recording and monitoring calls for quality purposes

– Customer Support Escalations

– Above and Beyond

Enhanced Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366– Assigned Support Center Representative (ASCR)

– Maintenance Assessment Services (MAS)

– Multi-Services Manager (MSM)

Customer Support Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367– Link to Worldwide Support Telephone and E-mail information

E

Base Maintenance Plan



OverviewCandle offers a comprehensive Base Maintenance Plan to ensure that you realize the greatest value possible from your Candle software investments. We have more than 200 technicians providing support worldwide, committed to being responsive and to providing expedient resolutions to support requests. Technicians are available worldwide at all times during the local business day. In the event of an after-hours or weekend emergency, our computerized call management and forwarding system will ensure that a technician responds to Severity One situations within one hour. For customers outside of North America, after-hours and weekend support is provided in English language only by Candle Customer Support technicians located in the United States.

Telephone supportCandle provides consistently reliable levels of service—thanks to our worldwide support network of dedicated experts trained for specific products and operating systems. You will always work with a professional who truly understands your problem.

We use an online interactive problem management system to log and track all customer-reported support requests. We give your support request immediate attention by routing the issue to the appropriate technical resource, regardless of geographic location.

Level 0 Support is where your call to Candle Customer Support is first handled. Your support request is recorded in our problem management system, then transferred to the appropriate Level 1 support team. We provide Level 0 manual interaction with our customers because we support more than 170 products. We feel our customers would prefer personal interaction to a complex VRU or IVR selection menu.

Level 1 Support is the service provided for initial support requests. Our Level 1 team offers problem determination assistance, problem analysis, problem resolutions, installation assistance, and preventative and corrective service information. They also provide product usage assistance.

Level 2 Support is engaged if Level 1 cannot provide a resolution to your problem. Our Level 2 technicians are equipped to analyze and reproduce errors or to determine that an error is not reproducible. Problems that cannot be resolved by Level 2 are escalated to Candle’s Level 3 R&D support team.

Level 3 Support is engaged if a problem is identified in Candle product code. At Level 3, efforts are made to provide error correction, circumvention or notification that a correction or circumvention is not available. Level 3 support provides available maintenance modifications and maintenance delivery to correct appropriate documentation or product code errors.



eSupportIn order to facilitate the support process, Candle also provides eSupport, an electronic full-service information and customer support facility, using the World Wide Web at www.candle.com/support/. eSupport allows you to open a new service request and update existing service requests, as well as update information in your customer profile. New and updated service requests are queued to a support technician for immediate action. And we can respond to your request electronically or by telephone—it is your choice.

eSupport also contains a continually expanding knowledge base that customers can tap into at any time for self-service access to product and maintenance information.

The Candle Web Site and eSupport can be accessed 24 hours a day, 7 days a week by using your authorized Candle user ID and password.

Description of Candle severity levelsResponses to customer-reported product issues and usage questions are prioritized within Candle according to Severity Code assignment. Customers set their own Severity Levels when contacting a support center. This ensures that we respond according to your individual business requirements.

Severity 1 Crisis

A crisis affects your ability to conduct business, and no procedural workaround exists. The system or application may be down.

Severity 2High

A high-impact problem indicates significant business effect to you. The program is usable but severely limited.

Severity 3Moderate

A moderate-impact problem involves partial, non-critical functionality loss or a reasonable workaround to the problem. A “fix” may be provided in a future release.

Severity 4Low

A low-impact problem is a “how-to” or an advisory question.

Severity 5Enhancement Request

This is a request for software or documentation enhancement. Our business units review all requests for possible incorporation into a future release of the product.

http://www.candle.com/support/



Candle has established the following service-level objectives:

Recording and Monitoring Calls for Quality PurposesCandle is committed to customer satisfaction. To ensure that our customers receive high levels of service, quality and professionalism, we’ll monitor and possibly record incoming and outgoing Customer Support calls. The information gleaned from these calls will help us serve you better. If you prefer that your telephone call with Candle Customer Support in North America not be monitored or recorded, please advise the representative when you call us at (800) 328-1811 or (310) 535-3636.

Customer Support EscalationsCandle Customer Support is committed to achieving high satisfaction ratings from our customers. However, we realize that you may occasionally have support issues that need to be escalated to Candle management. In those instances, we offer the following simple escalation procedure:

If you experience dissatisfaction with Candle Customer Support at any time, please escalate your concern by calling the Candle support location closest to you. Ask to speak to a Customer Support manager. During standard business hours, a Customer Support manager will be available to talk with you or will return your call. If you elect to hold for a manager, you will be connected with someone as soon as possible. If you wish a return call, please tell the Candle representative coordinating your call when you will be available. After contacting you, the Customer Support manager will develop an action plan to resolve your issue. All escalations or complaints received about support issues are logged and tracked to ensure responsiveness and closure.

Call Status Severity 1 Goal

Severity 2 Goal

Severity 3 Goal

Severity 4 Goal

Severity 5Goal

First Call Time to Answer

90% within one minute

Level 1 Response

(Normal Business Hours)

90% within 5 minutes

90% within one hour

Level 2 Response

(Normal Business Hours)

Warm Transfer

90% within two hours

90% within eight hours

Scheduled follow-up (status update)

Hourly or as agreed

Daily or as agreed

Weekly or as agreed Notification is made when an enhancement is incorporated into a generally available product.

Notification is made when a fix is incorporated into a generally available product.

The above information is for guideline purposes only. Candle does not guarantee or warrant the above service levels. This information is valid as of October 1999 and is subject to change without prior notice.



Above and BeyondWhat differentiates Candle’s support services from our competitors? We go the extra mile by offering the following as part of our Base Maintenance Plan:

n Unlimited multi-language defect, installation and operations support

n eSupport using the World Wide Web

n Regularly scheduled product updates and maintenance provided at no additional charge

n Over 200 specialized technicians providing expert support for your Candle products

Enhanced Support Services


Enhanced Support Services

OverviewOur Base Maintenance Plan provides a high level of software support in a packaged offering. However, in addition to this plan, we have additional fee-based support services to meet unique customer needs.

The following are some examples of our added-value support services:

n Assigned Support Center Representative Services (ASCR)

– An assigned focal point for managing support escalation needs

– Proactive notification of available software fixes

– Proactive notification of product version updates

– Weekly conference calls with your ASCR to review active problem records

– Monthly performance reviews of Candle Customer Support service levels

– Optional on-site visits (extra charges may apply)

n Maintenance Assessment Service (MAS)

– On-site assessment services

– Advice about product maintenance and implementation

– Training your staff to develop efficient and focused procedures to reduce overall cost of ownership of your Candle software products

– Analysis of your Candle product environment: versions, updates, code correction history, incident history and product configurations

– Reviews to ensure that purchased Candle products and solutions are used effectively

n Multi-Services Manager (MSM)

Multi-Services Manager provides highly valued services to customers requiring on-site full time expertise to complement their technical resources.

– Dedicated on-site Candle resource (6 months or one year) at your site to help ensure maximum use and effectiveness of your Candle products

– Liaison for all Candle product support activities, coordination and assistance with implementation of all product updates and maintenance releases

– Works with your staff to understand business needs and systems requirements

– Possesses technical and systems management skills to enhance your staff ’s knowledge and expertise

– Other projects as defined in Statement of Work for MSM services


Customer Support Contact Information


Link to Worldwide Support Telephone and E-mail informationTo contact Customer Support, the current list of telephone numbers and e-mail addresses can be found on the Candle Web site, www.candle.com/support/.

Select Support Contacts from the list on the left of the page.

http://www.candle.com/support/



Glossary 369

Glossary

A

Action Routine A user-supplied REXX program executed to resolve a problem or react to a set of conditions.

Availability Management System An Availability Management System is an OMEGACENTER implementation designed using Candle’s methodology for managing systems from a business orientation.

B

Basic Status Bar A graphic representation on an OMEGAVIEW display of a single measurement item.

D

Data Manager A program that controls access to a data source. For example, it can be used to reduce the number of data requests.

Diagnosis Routine A user-supplied REXX program executed by the Probe Manager when a managed object’s attribute status is Warning or Critical. A diagnosis routine may collect data, update OMEGAVIEW status items, send requests to the operator, or perform other functions.

Distributed Availability Subsystem (DAS) A stand-alone component of OSM/MVS that monitors distributed systems (RS/6000s, Tandems, DECs, and other Unix systems) and

LANs (Novell, etc.). It consists of a mainframe-based (host) set of programs and a PC-based set of programs.

Distributed System ID The identifier associated with a distributed system. It is identical to the domain ID.

Domain The MVS image on which a managed object resides.

Domain ID The identifier associated with a domain.

E

Environment ID The 8-character OMEGAMON application ID used by the Data Managers and probes.

Exception List An OMEGAVIEW panel, included with OSM/MVS, which lists system exception conditions.

Event Probe A probe that is executed as the result of a system event (for example, an alert, batch job exception, or failure).

F

Follow-Up Routine A user-supplied REXX program, executed by OSM/MVS in response to a change in the status of a managed object, that determines if a problem has been successfully resolved.

G


H

Heartbeat Probe A probe that determines if a system resource is active and/or available.

I

Initialization Probe A program module that is run once during the OSM/MVS start-up phase. It may be a Query, Heartbeat, or an Event probe, or a utility function.

M

Managed Object One or more objects monitored by an OSM/MVS probe and represented on an OMEGAVIEW display by situation or attribute status lights. For example, a Payroll Department, On-line Services, or Corporate LAN. Managed objects can also include lower levels of detail, such as TSO Users in Performance Group 210, Run Times for a set of batch jobs, and ABEND conditions for a set of batch jobs.

Multi-System Management Facility (MSMF) A Candle facility that performs direct (peer-to-peer) communication between MVS images on a VTAM network.

N

Notification Facility The OSM/MVS facility that automatically informs individuals of a status change, problem, event, etc.

Notification List A list of names, methods, and times to be used in the notification process.

O

Object A system resource or workload.

OMEGACENTER Gateway for MVS (OG/MVS) A Candle product that provides two-way communication between Candle’s OMEGACENTER products and other products, such as console automation products, IBM NetView, and ASCII hosts in a distributed systems environment.

OMEGAVIEW Candle’s status manager product.

P

Peer-to-Peer See Multi-System Management Facility.

Probe A program written in REXX that collects data about a managed object. See Heartbeat Probe, Query Probe, and Event Probe.

Probe Control Program A user-defined REXX routine that performs preprocessing tasks for a probe. Every event probe requires a Probe Control Program.

Probe ID The identifier associated with a probe.

Probe Manager A system driver module that controls the execution of a probe and, through the Status Manager, determines a status, and updates OMEGAVIEW.

Q

Query Probe A probe that collects measurement values which represent the current attributes of a managed object. See Managed Object.

R

Rollup (Rollup Status Bar) A graphic representation on an OMEGAVIEW display of an aggregate of basic status items or of both basic and rollup status items.

Glossary 371

Rule An equation used in situation definitions. It consists of an object, a comparator, and a value. The object is the status item for either a managed object or a situation. The comparator is one of the standard set of mathematical tests(equal to, greater than, less than, not equal to, etc.). The value is a status value (OK, Warning, Critical, or None). See Situation Rule Set.

Rule Set See Situation Rule Set.

S

SDM See Status Data Manager Database

Situation See Situation Object.

Situation Object A named, composite attribute consisting of up to five rules combined with AND or OR. All situations evaluate to either True or False.

Situation Manager The OSM/MVS component that evaluates the rule set and determines the status settings of situation objects.

Situation Rule Set The set of rules defining the analytical logic used to determine a situation’s status. Each rule of the set defines a formula involving other status items, operators, and attribute status or values. A Rule Set may contain up to five rules. See Rule.

Situation Status A setting assigned by the Status Manager. Situations are only evaluated in True/False terms, so a situation status can only have settings of OK (green) or critical (red).

Spike Smoothing A user-selected option in Status Manager that performs a statistical normalization of statuses. It provides a more representative picture of attributes whose statuses vary greatly over short periods of time.

Status Bar A graphic representation on an OMEGAVIEW display of the health of some aspect of a system’s performance, such as response time or availability. The status bar’s color corresponds to a status: Green (OK), Yellow (Warning), Red (Critical), and Turquoise

(None). See also Basic Status Bar and Rollup Status Bar.

Status Data Manager Database (SDM) The OMEGAVIEW database that stores and maintains the status items displayed on OMEGAVIEW panels. OSM/MVS updates the SDM.

Status Item A system-wide identifier, defined by the user, that associates a managed object attribute or a situation to an OMEGAVIEW status bar.

Status Manager The OSM/MVS component that compares an attribute value to a set of thresholds and assigns a status (OK, Warning, or Critical). The Status Manager is an integral part of the Probe Manager.

System ID An identifier representing the MVS image on which a probe executes. To be distinguished from the domain ID, which is the MVS image the probe monitors. The domain and the system may be identical.

T

Threshold The user-specified value against which the currentattribute value is compared to derive a status.

OSM/MVS Assistant An OSM/MVS facility that ensures that all necessaryparameters have been entered for a managed object.

Translate Routine See XLate Routine.

Trap A user-defined rule statement which defines how OG/MVS responds to specific system events such as messages, MVS commands, OMEGAMON exceptions, and date and time information.

W

Work List An OMEGAVIEW panel included with OSM/MVS which lists system problem areas requiring operator attention.


X

XLate Routine A PC-based DAS program that translates data received from distributed systems to a format recognizable by the host.

Index 373

Symbols@TRT variable 328

Aaction bar 29

accessing (F10) 41choices 29description 29Probe Manager 50Situation Manager 59Status Manager 55

action codes 32activate 33, 51add 32, 51, 55copy 32, 51, 55critical 55delete 33, 51, 55edit 33, 51find 33, 51, 55inactivate 33, 51modify 33, 51, 55none 55OK 55Probe Manager 51refresh 33, 51, 55show dependents 33, 51Situation Manager 59Status Manager 55using 32warning 55

action flag 258action pull-down 32action routine 79, 81, 258, 259Actions pull-down 35activate action code 33, 51activity

adding 277modifying 277

actual status display 201Add a Probe panel 267Add action code 32, 51, 55Add Calendar panel 71Add Daytype Schedule panel 270Add Distributed System panel 295Add Notification Code panel 101Add Notification Level panel 102

Add Notification User panel 104Add Notification User panel fields 103Add Recommendations panel 127, 261Add Rotation List panel 109Add Situation panel 61, 280Add Situation/Probe List panel 281Add Status Item panel 199, 273, 284, 293Add Status Item panel field definitions 274Add System Definition panel 289Add System Environments panel 290Add User ID to Rotation List panel 111Add User panel 38, 97adding

probe program code 271probes 267situations 280status items 273, 284, 293

Adobe portable document format 9AF/OPERATOR 18alternate notification program 116Always Notify field 117arguments

DOMAIN_ID 322, 328DOMAIN_NAME 322, 325MANAGE_OBJECT 328PERIOD_NUM 328PROBE_ID 322, 325status_item 322, 325

ASCRassigned support center representative 366

assigned support center representativeASCR 366

Assistant, OSM/MVSSee OSM/MVS Assistant

attributevalue 53

automatic resolution time 116availability

management 18, 19monitoring 241, 242

BBalance Display panel 221balancing probe startup 219Batch Job Event probe 334baud rate 138building an OSM/MVS application 236

Index


business day 71, 74business day of month 72Business Day of Month Method Entry panel 75

Ccalculation, calendar day 72

business day of month 72day of month 72specific day 72weekday of month 72

calendaplanning 70

calendarbusiness/off

business day 75Day definitions 71days 72, 75

business/off 74defining 73priority order 74relative order 74

Daytypes 71business 72default 72off 72

defined 70overview 70

Calendar Days panel 73Calendars panel 70cancel (F12) 41capabilities 45Case Study

recommendation 262case study 236, 286

adding a probe 266, 267adding a status item 273, 293adding a status item to a situation 284availability 242configuration information 240copying a probe 291copying probe source code 271creating a recommendation 260creating a situation 280DAS probe 288data gathering 239description 237distributed systems 288editing a probe program 271heartbeat probe 288history status bar 306, 312interface-building 302invoking an action routine 258

literal text string 312modifying a Data Manager probe 243modifying a probe 291modifying a status item 246monitoring 242, 266notification 297OMEGAVIEW 302, 305OMEGAVIEW exception panel 277procedure overview 239pushbutton 312recommendation 262refreshing a probe 300refreshing OSM/MVS 263RS6000 237, 288sample interface panel 304status item 238, 293user interface 238viewing a probe program 271

changing target image dataset informationfile preferences 179global preferences 179log environment 179notification preferences 179

CICS DSA Free probe 335CICS EDSA Free probe 335CICS End-to-End Response Time probe 334CICS OSCOR Free probe 334CICS Response Time probe 344CICS Storage Violation probe 334CICS VSAM Waits probe 335code, recommendation 128coding

probes 316recommendations 320rules 320

Command Line field 295Common User Access (CUA) 26communication failure 139, 140comparator 282configuring OSM/MVS 8Continue to Next User field 103control parameter file 138controlling panel updating 84Controls pull-down 211Copy a Probe panel 291Copy action code 32, 51, 55Copy Day in Calendar panel 74copying a probe 291CPU Page Rates probe 333CPU Percent Utilization probe 333Create Table Data Set confirmation panel 174Critical action code 55

Index 375

Critical status 53CUA 26customer support

base maintenance plan 362contact information 367enhanced support services 366eSupport 363severity levels 363telephone support 362

customizing OSM/MVS 8customizing probes 320

DDAS

See Distributed Availability Subsystem (DAS)DAS CPU Utilization Percentage (non-UNIX)

probe 337DAS CPU Utilization Percentage (UNIX) probe 336DAS LAN Server Heartbeat probe 346DAS probe 288DAS Probe Manager 140DAS RS6000 Heartbeat probe 345DASD Volume Response Rate probe 333data

bits 139gathering 239sorting 40

Data Manager 45, 321and OMEGAMON 47, 328and status item 238Distributed 47OMEGAVIEW 47probe 243variables 319, 320

Data Manager panel 244data manager probe 48Data Manager probe (DAS only) 343day calculation methods 72Day definition

defined 71day of month 72Daytype

defined 71DB2 Thread CPU Time probe 339DB2 Thread Elasped Time probe 338DB2 Thread Time Total probe 339DB2 Transplex Plan Getpages Rate probe 339Default_status argument 327defaults

enterprise-wide 30escalation time 116incident priority 117notification 115

notification text 118notification type 117OSM/MVS 29

definingcalendar 70calendar days 73distributed systems 8logs 8system defaults 8VTAM applications 8

Delete action code 33, 51, 55dependent components, navigating to 63Dependent Probes field 245dependent relationships 62diagnostic routine 79dial-up modem 139Distributed Availability Subsystem (DAS) 45

configuration 137defining 141host components 140PC components 138setting up an RS6000 probe 288UNIX commands 295

Distributed Data Manager (DDM) 46, 140Distributed Data Manager (DDM) probe 46distributed domain ID 138Distributed Gateway

See OMEGACENTER/Distributed GatewayDistributed Probe Manager 140distributed probes 47distributed systems

limitation 137monitoring 288parameters 138

distribution 160distribution information, displaying 187distribution process

replication 184domain

distributed 138ID 51, 274

DOMAIN_ID argument 328DOMAIN_NAME argument 325

EEdit action code 33, 51ellipsis 31EM Probe Exception Input 251entry panel 37error messages 325Escalate Incident panel 230Escalate Until Available field 117


escalation 117, 227, 230escalation order 102escalation time 116Escalation Time field 103eSupport

customer support 363event probe 46, 48exception

flag 277panel, OMEGAVIEW 86

exception flagsetting 277

Exception List Data panel 88, 279exit (F3) 41exiting OSM/MVS 44

Ffile

parameters, distributed systems 138file preferences

changing for target replication systems 179File Preferences panel 170, 181, 195File Preferences pulldown 196Find action code 33, 51, 55follow-up routine 79, 82function Keys 41functional security 146

GGeneric OMEGAMON Single Exception probe 338Get CICS File Status probe 338Get Number of TSO Users probe 338global preferences

changing for target replication systems 179Global Preferences panel 179, 192, 203Global Preferences pulldown 193Green_value argument 327group

notification 67

Hheader, REXX program 324heartbeat probe 46, 48help

description 42displaying (F1) 41pull-down 30, 42

history status barcreating 308, 312description 303example 306, 312

IIMS PSB Status probe 338Inactivate action code 33, 51incident

closing 68escalation 67, 230message 65, 227processing 65receiving 227resolving 229

Incident Number field 228incident priority 117, 120initialization probe 46, 47interface 25

example 238Intervention Required Count probe 336

JJES 18JES2 Job Class Queue Depth probe 337JES2 NJE Line Status probe 337JES2 Spool Utilization probe 337

KKATIACA0 panel 73KATIACA4 panel 75KATIACAE panel 74KATIACL0 panel 70KATIACL1 panel 71KATPARM.DAT file 138KATPARMC.CMD dialog 138KATRAU16 routine 330

LLAN, Novell

defining to DAS 138in DAS configuration 137limitation 137monitoring 136

libraryPROBELIB 46, 331REXXLIB 46, 341

linking OSM/MVS status items to OMEGAVIEW 240literal text string 308, 312log

datasets 77notification 66, 77OMEGACENTER 258procedure 78status 77

log environmentchanging for target replication systems 179

Index 377

Log Environments panel 182Log_MVupdate_code argument 327logon

distributed systems 139

Mmain panel 27, 213maintenance assessment service

MAS 366managed object 46MANAGED_OBJECT argument 328MAS

maintenance assessment service 366message

directing to OMEGAVIEW 84incident 65, 227notification 65operator console 76recommendation 76, 126

method, calendar day calculation 72migration 160Misc. Parms field 294MISC_PROBE_PARMS 327miscellaneous parameters

adding 248modifying 248OMEGAVIEW exception panel 248

modemflag 139redial 140timeout 140

Modify a Probe panel 243Modify a status item 249Modify action code 33, 51, 55Modify Action, Follow-up and Log Data panel 258Modify Activity panel 80, 82, 86, 87, 122, 132,

258, 278, 298Modify Diagnosis and Log Data panel 80Modify Notification and Recommendation Data

panel 122, 132, 262, 298Modify Notification User Entry panel 105Modify Recommendation panel 128Modify Status Item panel 34, 246Modify Status Item panel field definitions 274Modify System Environment panel 205Modify Work List Data panel 86modifying

DAS probes 291Data Manager probes 243status items 246

monitoring 135active users 267TSO response time 242

MSMmulti-services manager 366

multi-services managerMSM 366

MVS 18MVS Active Task Heartbeat probe 344MVS Batch Job Count probe 335MVS Data Manager probe 47, 243MVS Started Task Count probe 335MVS TSO User Count probe 333

Nnavigation 38, 63NetView 18NO return code value 329NO_DATA return code value 329NO_DATA value 329None action code 55None status 53notification

activity 297Add Notification User panel fields 103adding a notification level 101adding a rotation list 109adding a user to a group 104adding rotation list members 110adding rotation lists 102adding users 102alternate program 116, 120alternate system 118assigning to a status 121assignments 119automatic resolution time 116busy status 228chain 67, 99, 230changing active user in rotation list 111closing an incident 68code 119compared to recommendation 76, 126Continue to Next User field 103creating a group 99creating a rotation list 107default settings 115default text 118defining a group 100defining users 96deleting a user 98deleting group data 105deleting rotation list data 112description 92escalation 94, 117, 227, 230escalation order 99, 102


Escalation Time field 103example 297group 67, 99identification code 99incident creation 119incident escalation 67incident message 227incident priority 117incident reporting 93incident vs. nonincident reporting 93levels 99list 96log 66, 77message 297method of 117modifying a group 104multiple users 119nonincident reporting 95, 119Notification Type field 103OMEGAVIEW panel 113operational features 226paging 94, 96, 97, 103, 116, 119preferred system 118priority 120receiving an incident 94, 227refresh 231resolving an incident 94rotation list 67, 107setup 68, 92status item change 119text 119type 117update 231user 65User ID/Rotation List field 103with several group members simultaneously 103WTO 117

Notification Groups panel 100notification preferences

changing for target replication systems 179Notification Preferences panel 115

fields defined 118Notification refresh

confirmation 231system 231

Notification Refresh panel 231Notification refresh selection 231Notification Type field 103Notification Users panel 37, 96Notify Even If Busy field 117Notify If Available field 117

Ooff day 71, 74, 75OG/MVS 18

commands 330error handling 330probe communication 320REXX functions 321REXX shared variable functions 321SHARVGET function 326SIGNAL ON ERROR 320

OK action code 55OK status 53OMC/Gateway

in DAS configuration 137OMEGACENTER

log 258OMEGACENTER/Distributed Gateway 18OMEGAMON

Data Manager 47OMEGAMON Data Manager probe 46OMEGAMON Event Probe probe 339OMEGAMON for CICS Data Manager probe 342OMEGAMON for DB2 Data Manager probe 338OMEGAMON for MVS Data Manager probe 342,

343OMEGAMON Generic Data Manager 339OMEGAMON MVS Data Manager - Part 2 339OMEGAMON VTAM Session Name field 244OMEGAMON/ End-to-End Data Manager

probe 339OMEGAVIEW 53, 318

colors 303Data Manager 47description 18, 302Exception panel 86, 87exception panel 277history status bar 303, 306, 308, 312link with OSM/MVS status items 240literal text string 308, 312Notification panel 113pushbutton 303, 312relationship to OSM/MVS 64status lights 53, 303text type 275worklist panel 85

OMEGAVIEW Data Manager probe 47OMEGAVIEW special panels

directing messages to 84updating 194

operational features 191operator console 76operator message 262

Index 379

order, calendar days 74Originating Refresh System 231OSM Input List panel 250OSM System Replication panel 177OSM/MVS - Replication Definition 173OSM/MVS - Status item Replication panel 164OSM/MVS Assistant 197OSM/MVS Assistant Exit Validation panel 200OSM/MVS Assistant panel 56, 197, 200, 268, 272,

274, 278, 292, 294OSM/MVS Data Manager Dependent Probe Input

panel 250OSM/MVS description 18OSM/MVS Displaying Replication and Distribution

Information 187OSM/MVS Distributing MVS images 184OSM/MVS File Preferences panel 195OSM/MVS Global Preferences panel 192OSM/MVS Notification Preferences panel 180OSM/MVS Replicating MVS images 176override, business/off day 74

Ppaging 94, 96, 97, 103, 116, 119panel 85

Actions 35Add a Probe 267Add Calendar 71Add Daytype Schedule panel 270Add Distributed System 295Add Notification Code 101Add Notification Level 102Add Notification User 104Add Recommendations 127, 261Add Rotation List 109Add Situation 61, 280Add Situation/Probe List 281Add Status Item 199, 273, 284, 293Add Status Item field definitions 274Add System Definition 289Add System Environments 290Add User 38, 97Add User ID to Rotation List 111Balance Display 221Business Day of Month Method Entry 75Calendar Days 73Calendars 70Copy a Probe 291Copy Day in Calendar 74Data Manager 244Data Manager Dependent Probe Input 250EM Probe Exception Input 251

Escalate Incident 230Exception List Data 88, 279File Preferences 195, 196Global Preferences 192, 193, 203Help 30, 42KATIACA0 73KATIACA4 75KATIACAE 74KATIACL0 70KATIACL1 71main 27, 213Modify a Probe 243Modify Action, Follow-up and Log Data 258Modify Activity 80, 82, 86, 87, 122, 132, 258,

278, 298Modify Diagnosis and Log Data 80Modify Notification and Recommendation

Data 122, 132, 262, 298Modify Notification User Entry 105Modify Recommendation 128Modify Status Item 246Modify Status item 34Modify Status Item field definitions 274Modify System Environment 205Modify Work List Data 86Notification Groups 100Notification Preferences 115Notification Refresh 231Notification Users 37, 96OMEGAVIEW Exception 87OMEGAVIEW Notification 113OSM Input List 250OSM/MVS Assistant 56, 197, 200, 268, 272, 274,

278, 292, 294OSM/MVS Assistant Exit Validation 200OSM/MVS replication definition 173OSM/MVS Status item Replication 164Probe Manager 36, 50, 212Probe Schedule 222, 268Probe/Status Balancer 220Probes in a Time Period 222Query Probe Input 251Receive Notification 66, 227Recommendations 127, 260Refresh OSM/MVS 211, 264Resolve Incident 229Rotation Lists 109, 110Schedule Definitions panel 269Situation Manager 58, 60Start OSM/MVS 214Status Manager 34, 54, 121, 131, 249Stop OSM/MVS 215


System Environments 204View 40

parameters, distributed systems 138parity setting 139PARSE ARG statement 320, 325PARSE VAR statement 320, 326, 327password

distributed systems 139Peer Link probe 47, 346Pending VTAM Nodes probe 337PERIOD_NUM argument 328, 329planning

calendar 70resource management

calendar 70port, serial 138preferences 196

field definitions 193, 196file 196

setting 195global 192, 193notification

setting 115OSM/MVS Global Preferences panel 192setting 192

Preferences panel 30, 192, 195Preferences pull-down 115, 195Preferences pulldown 192Preferred notification systems 116printing problems 9priority order

calendar days 74probe 46, 286

activate 33activating 211active 51actual status 51adding 266, 267annotated 316balancing startup 219building 52, 197catalog 331, 341coding 316coding recommendations 320coding rules 320copying 291customizing 320data manager 48defined 46dependent 245description 19, 51distributed 47, 140Distributed Data Manager (DDM) 47

domain ID 51editing 33event 47, 48heartbeat 47, 48how it supports status items 319ID 51inactivate 33initialization 47library 46, 331, 341list 331, 341model 320modifying 243, 291OMEGAMON Data Manager 47OMEGAVIEW Data Manager 47program 198query 47, 48, 316refresh 211REXX source file 198samples 331, 341show dependents 33Situation Manager 47startup 219system ID 51table 341TSO Response Time 316type 51type code 47types 46update 211writing 316

Probe Directive field 275probe directives

adding 248modifying 248

probe inputadding 248modifying 248

Probe Manager 45adding a dependent probe 245adding a probe 266modifying a Data Manager probe 243status item values 319

probe managerretrieving values 324

Probe Manager panel 36, 50, 212Probe Schedule panel 222, 268probe status display

actual 201Probe/Status Balancer panel 220Probe_Directive argument 327PROBE_ID argument 325PROBELIB library 46, 271, 331probes

Index 381

product-supplied 341Probes in a Time Period panel 222prompt

characters 139for scrolling 139key (F4) 41string 139

pull-down menu 30pushbutton 303, 312

Qquery probe 46, 48, 316Query Probe Input 251

RReceive Notification panel 66, 227receiving an incident 227receiving notification 227recommendation

and notification 126associating with status 130code 128, 262compared to notification 76creating 127, 260defined 76, 126deleting 129example 260message 262modifying text 128setup 126

Recommendations panel 127, 260Red_value argument 327redial, modem 140refresh 210, 286

example 300global 210, 263, 300notification 231OSM/MVS 263, 300probe 211

Refresh action code 33, 51, 55Refresh OSM/MVS panel 211, 264refreshing a probe 286replication 160replication process

replication 176Resolve Incident panel 229resolving an incident 229resource management

calendar, defining 70planning

calendar 70RETURN ATTRIBUTE_VALUE statement 329

RETURN statement 320REXX programming language 47, 318

copying probe source code 271PARSE ARG 320, 325PARSE VAR 320RETURN 320SIGNAL ON ERROR 320statements

PARSE VAR 326, 327RETURN ATTRIBUTE_VALUE 329

REXX shared variable functions 321REXXLIB library 46, 341rotation list 67, 107

adding 109adding members 110changing active user 111creating 107deleting data 112

Rotation Lists panel 109, 110routine, translation 138routines, invoking 79

SSchedule Definitions panel 269scrolling 38

backward (F7) 41forward (F8) 41prompt 139

serial port 138setting file preferences 195setting global preferences 192setting notification preferences 115setting system environments 8setting thresholds 294setup

notification 68, 92severity levels

customer support 363SHARVGET function 326show dependents action code 33, 51SHOWOSM command 347SIGNAL ON ERROR statement 320situation

active flag 59adding 280adding a status item to 284comparator 282defined 57defining a 60description 21Enable Warnings 59evaluating 57


name 59Situation Manager 45, 47, 280Situation Manager panel 58, 60Situation Manager probe 47, 346sort 40special panels

controlling 84specific day 72spike 275Spikes Check field 275Start OSM/MVS panel 214start procedure

OSM/MVS 213statements

PARSE ARG 320, 325PARSE VAR 320, 326, 327RETURN 320RETURN ATTRIBUTE_VALUE 329SIGNAL ON ERROR 320

statusCritical 53light 53, 303, 306log 77None 53OK 53Warning 53

status item 238, 286action routine 81adding 273, 284catalog 341defined 53description 19, 21, 55diagnostic routine 79follow-up routine 82invoking a user-written routine 79library 341modifying 246name 55, 319probe ID 55product-supplied 341refresh 286retrieving the value 328value 329value conversion 319

status item change and notification 119Status Manager 45

adding a status item 273, 284modifying a status item 246retrieving values 325

Status Manager panel 34, 54, 121, 131status_item argument 325stop bits 139

Stop OSM/MVS panel 215stop procedure 215Sysplex Query probe 336system

ID 51, 228System Environments panel 162, 204system ID 274

Ttable panel 37Tape Mount Requests Count probe 335Target Image Display panel 188Target Systems Distribution panel 183, 186Target Systems panel 172, 178, 187telephone support

customer support 362text type 275threshold 53, 246, 275Threshold Critical field 293Threshold OK field 293timeout

distributed systems 140timeout, distributed systems 139, 140translate routine 138translation routines 138TSO Response Time probe 316, 344TSO response time probe 242, 246TSO Transaction Rate probe 345TSO User Counts probe 333TSO User Group End-to-End Group Transaction

Rate probe 336TSO User Group End-to-End Host Response Time

probe 336TSO User Group End-to-End Network Response

Time probe 336TSO Users Active probe 337TSO Users Count 343type code 47

UUNIX 288, 295update 286

example 300global 300notification 231OSM/MVS 300probe 211

updating data 210updating special panels 84User ID/Rotation List field 103user interface 25user-written routines 79

Index 383

VValue Offset field 296Value Size field 296variables

@TRT 328View pull-down 40VTAM 18VTAM Node Heartbeat probe 343VTAM Node Monitor probe 334VTAM Node Performance Monitor probe 334

WWarning action code 55Warning status 53weekday of month 72worklist panel, OMEGAVIEW 85writing a probe 316WTO 117WTOR 138

XX-late routine 138

YYES return code value 329


Date post:	20-Sep-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times

OMEGACENTER Status Manager for MVS ഀ唀猀攀爠ᤀ猀 䜀甀椀...

Documents

OMEGACENTER Status Manager for MVS ഀ唀猀攀爠ᤀ猀䜀甀椀...