OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's ... - IBM€¦ · OMEGAMON XE for IMS on z/OS...

OMEGAMON XE for IMS on z/OSVersion 5.1.0

OMEGAMON for IMS User's Guide

SC27-4439-00 (re-released November 2012)

��

OMEGAMON XE for IMS on z/OSVersion 5.1.0

OMEGAMON for IMS User's Guide

SC27-4439-00 (re-released November 2012)

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 109.

This edition applies to version 5, release 1, modification 0, of IBM Tivoli OMEGAMON XE for IMS on z/OS (productnumber 5698-T02) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2004, 2012.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Managing IMS performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Monitor performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Identify and correct problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

User interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2. Command basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Accessing the command interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Commands and screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Panel format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

INFO-line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Panel display symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Entering commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Command types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Command formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Command help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Major, minor, and immediate command help . . . . . . . . . . . . . . . . . . . . . . 9INFO-line command help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Commands to list commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Screen control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Clearing the screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Deleting comment lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Inserting and deleting lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Selecting Program Function (PF) keys . . . . . . . . . . . . . . . . . . . . . . . . 15Displaying continuation lines of command output . . . . . . . . . . . . . . . . . . . . 17Delaying automatic updating . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Activating the log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Checking the page limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Logging a single display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Logging part of a display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3. Screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Invoking screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Creating or modifying screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . 21Loading screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Listing screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Renaming a screen space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Deleting a screen space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Invoking screen spaces automatically . . . . . . . . . . . . . . . . . . . . . . . . . 24

Conditional screen space fetching . . . . . . . . . . . . . . . . . . . . . . . . . 24Delayed screen space fetching . . . . . . . . . . . . . . . . . . . . . . . . . . 24Looping screen spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Testing .FGO routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Manipulating the log within screen spaces . . . . . . . . . . . . . . . . . . . . . . 25

Chapter 4. Advanced commands and features . . . . . . . . . . . . . . . . . . . . . 27

© Copyright IBM Corp. 2004, 2012 iii

Rate and difference command arguments . . . . . . . . . . . . . . . . . . . . . . . 27Setting and using variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28The zooming feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Secondary console control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 5. Operating from the menu/command interface. . . . . . . . . . . . . . . . . 31Logging on to the menu/command interface directly . . . . . . . . . . . . . . . . . . . . 31Modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

VTAM mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31ISPF mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31TSO mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Dedicated mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Specifying a user profile in ISPF, VTAM, or TSO mode. . . . . . . . . . . . . . . . . . . 32Working with exceptions in VTAM, ISPF, TSO, or dedicated mode . . . . . . . . . . . . . . 32

Exceeding exception thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . 32Responding to exception messages. . . . . . . . . . . . . . . . . . . . . . . . . 33Starting exception analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Exception analysis summary commands . . . . . . . . . . . . . . . . . . . . . . . 34Controlling and customizing exception analysis . . . . . . . . . . . . . . . . . . . . 36Exception analysis for IMS messages . . . . . . . . . . . . . . . . . . . . . . . . 39

Chapter 6. Customization procedures for Realtime Performance Monitor . . . . . . . . . . 43Reviewing profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Reviewing types of profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Using profile suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Determining profile search order . . . . . . . . . . . . . . . . . . . . . . . . . . 44Storing profile data sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Reviewing exception analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Creating an installation-defined profile . . . . . . . . . . . . . . . . . . . . . . . . . 45

Step 1: Establishing default options . . . . . . . . . . . . . . . . . . . . . . . . . 45Step 2: Selecting session and exception analysis options . . . . . . . . . . . . . . . . . 45Step 3: Setting default startup configuration . . . . . . . . . . . . . . . . . . . . . . 46

Implementing the installation-defined profile . . . . . . . . . . . . . . . . . . . . . . . 48Step 1: Saving the installation-defined profile . . . . . . . . . . . . . . . . . . . . . 48Step 2: Securing the installation commands . . . . . . . . . . . . . . . . . . . . . . 48Step 3: Specifying the default profile . . . . . . . . . . . . . . . . . . . . . . . . 49

Implementing your BMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . 49Setting up your BMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Starting and stopping your BMP interface automatically . . . . . . . . . . . . . . . . . 50Starting your BMP interface manually . . . . . . . . . . . . . . . . . . . . . . . . 50Stopping your BMP interface manually. . . . . . . . . . . . . . . . . . . . . . . . 51

Implementing the SAP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 52When to customize OMEGAMON for IMS for SAP . . . . . . . . . . . . . . . . . . . 52Customizing OMEGAMON for IMS to start SAP automatically . . . . . . . . . . . . . . . 53Starting SAP support from the z/OS console . . . . . . . . . . . . . . . . . . . . . 53Starting SAP support from OMEGAMON for IMS . . . . . . . . . . . . . . . . . . . . 53Stopping SAP from the z/OS console . . . . . . . . . . . . . . . . . . . . . . . . 53Stopping SAP support from OMEGAMON for IMS . . . . . . . . . . . . . . . . . . . 53Checking the status of SAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Using KOIGBL to customize workload parameters . . . . . . . . . . . . . . . . . . . . 54Defining workload groups by using the KOIGBL load module . . . . . . . . . . . . . . . 54Specifying workload group definition versions . . . . . . . . . . . . . . . . . . . . . 54KOIGBL defines all workload group definitions . . . . . . . . . . . . . . . . . . . . . 54Defining OMEGAMON for IMS workload groups . . . . . . . . . . . . . . . . . . . . 54Defining targeted programs or program groups by using the KOIGBL data set . . . . . . . . . 55Modifying workload group definitions by using the KOIGBL24 macros . . . . . . . . . . . . 55

iv OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's Guide

Modifying the default workload groups macros ($OIGROUP) . . . . . . . . . . . . . . . 55Specifying RTA thresholds by using the $OIGROUP ID macro . . . . . . . . . . . . . . . 57Modifying the default Bottleneck Analysis parameters ($OIDEXAN) . . . . . . . . . . . . . 59

Concatenating screen space and profile data sets . . . . . . . . . . . . . . . . . . . . 60Saving and reading screen space data sets example . . . . . . . . . . . . . . . . . . 60Restricting parameter modification . . . . . . . . . . . . . . . . . . . . . . . . . 61

Appendix A. IPL Elimination utility . . . . . . . . . . . . . . . . . . . . . . . . . 63Running the KIPWIPER utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Sample JCL instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63KIPWIPER log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Appendix B. Startup operation and interface commands. . . . . . . . . . . . . . . . . 67Startup operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Interface z/OS IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Creating an internal z/OS ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Starting the interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Example using the MODIFY command . . . . . . . . . . . . . . . . . . . . . . . 68Showing identifiers for the IBM monitor job . . . . . . . . . . . . . . . . . . . . . . 68Displaying identifiers for an interface started as a started task . . . . . . . . . . . . . . . 68Displaying identifiers for an interface started as a batch job . . . . . . . . . . . . . . . . 68

Interface commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69COMMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71EXEC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76MODIFY MERGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Appendix C. IMS exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Appendix D. IMS Fast Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Appendix E. Journal Facility control settings . . . . . . . . . . . . . . . . . . . . . 97

Appendix F. Documentation library . . . . . . . . . . . . . . . . . . . . . . . . . 101OMEGAMON XE for IMS publications . . . . . . . . . . . . . . . . . . . . . . . . 101Shared OMEGAMON XE publications . . . . . . . . . . . . . . . . . . . . . . . . 102IBM Tivoli Monitoring library . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Other sources of documentation . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Appendix G. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Interface information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Related accessibility information . . . . . . . . . . . . . . . . . . . . . . . . . . 105IBM and accessibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Contents v

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

vi OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's Guide

Figures

1. Panel format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52. INFO-line format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63. VTAM user information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75. Types of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86. Command format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97. One-line help display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108. Extended help display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109. Minor command help display . . . . . . . . . . . . . . . . . . . . . . . . . . 11

10. INFO-line command help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211. Commands that list commands . . . . . . . . . . . . . . . . . . . . . . . . . 1212. Using the DCL command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1413. Result of the DCL command . . . . . . . . . . . . . . . . . . . . . . . . . . 1414. .I command (step 1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1515. .I command (step 2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516. .I command (step 3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1517. PFK definitions in command mode . . . . . . . . . . . . . . . . . . . . . . . . 1618. Display of .PFK command . . . . . . . . . . . . . . . . . . . . . . . . . . . 1619. Extended display of all PF key assignments . . . . . . . . . . . . . . . . . . . . . 1620. Continuing major command output . . . . . . . . . . . . . . . . . . . . . . . . 1721. Continuing major and minor command output . . . . . . . . . . . . . . . . . . . . 1722. Session options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1823. .PRT command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924. Typical user-created screen space . . . . . . . . . . . . . . . . . . . . . . . . 2225. Default screen space listing . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326. .R argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2727. Zoom PF11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2928. Profile SW in use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3229. Systemwide exceptions display . . . . . . . . . . . . . . . . . . . . . . . . . 3330. Set All Clear Message screen . . . . . . . . . . . . . . . . . . . . . . . . . . 3431. History of all tripped exceptions . . . . . . . . . . . . . . . . . . . . . . . . . 3532. Set Communications External Subsystem Pool Exceptions panel . . . . . . . . . . . . . 3733. TERSE keyword display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3834. Exceptions displayed by the LEXC command . . . . . . . . . . . . . . . . . . . . 3935. Display of predefined IMS/MTO messages . . . . . . . . . . . . . . . . . . . . . 4036. Defining message exception display characteristics . . . . . . . . . . . . . . . . . . 4137. PROFILE MAINTENANCE AND SESSION CONTROLS Menu . . . . . . . . . . . . . . 4638. Format of $OIGROUP ID to Name a Group and/or Specify RTA Values . . . . . . . . . . . 5939. KIPWIPER job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6440. Sample log where OMEGAMON tasks for IMS systems are active . . . . . . . . . . . . 6441. Sample log where no OMEGAMON tasks for IMS systems are active . . . . . . . . . . . 6542. Default member KOIJLF00 (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . 9743. Default member KOIJLF00 (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . 9844. Default member KOIJLF00 (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . 99

© Copyright IBM Corp. 2004, 2012 vii

viii OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's Guide

Tables

1. Product components available with OMEGAMON for IMS . . . . . . . . . . . . . . . . 22. Characteristics and Requirements for OMEGAMON for IMS Modes of Operation . . . . . . . . 33. START CBMP Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504. Understanding ATTACH= values . . . . . . . . . . . . . . . . . . . . . . . . . 515. IMS command options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526. Using OMEGAMON for IMS with SAP . . . . . . . . . . . . . . . . . . . . . . . 537. Terminal-related group actions . . . . . . . . . . . . . . . . . . . . . . . . . . 578. IF parameter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749. IMS fast path mnemonics. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

© Copyright IBM Corp. 2004, 2012 ix

x OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's Guide

Chapter 1. Introduction

This chapter introduces you to the user interfaces, product components, and modes of operation ofOMEGAMON for IMS.

Managing IMS performanceOMEGAMON for IMS provides tools for you to manage your IMS™ system resources effectively, and toassist the help desk staff to identify and resolve problems, often before they affect the user:

v Performance indicators alert you to impending problems so that you can quickly navigate to detailpanels.

v The Operator Assist function provides you with an easy way to display database transactions, programs,and so on, and to make them available.

For example, you can request a view of only those resources that are unavailable. Then, if you see astopped database, you can move your cursor next to the database name and type the action code to startthe database. OMEGAMON for IMS creates the appropriate IMS command and passes it to IMS forexecution.

Managing IMS performance includes balancing workloads and resources, and monitoring the effects ofthese balancing decisions. You monitor IMS to determine whether IMS transactions are processing at anacceptable rate. Even though IMS is a complex environment, something as simple as a stopped databasecan delay the completion of the IMS transactions. The user typically feels the effects of resourcecontention or unavailable resources and informs help desk personnel.

Managing your system is an iterative process that consists of the following steps:

1. Monitoring the performance of your system.

2. Identifying the cause when a workload or key system resource shows a problem.

3. Correcting problems that arise.

4. Using the data from your observations and your knowledge of data center priorities to arrive atperformance targets.

5. Continuing the monitoring of your system.

Monitor performanceYour site might not have formal, written performance objectives, but almost all sites have informalobjectives. OMEGAMON for IMS can help you translate informal objectives into formal objectives, and canalso help you monitor performance on your system. Once OMEGAMON for IMS is up and running, youcan start monitoring current IMS performance by asking yourself the following questions:

v How are my groups of transactions performing?

v How are my IMS resources performing?

v Are the problems that OMEGAMON for IMS points up really problems for my site?

v Is OMEGAMON for IMS missing any problems for my site?

The IBM® Tivoli® OMEGAMON® XE for IMS on z/OS®: Response Time Analysis Reference explains howto set response-time exception values.

Identify and correct problemsWhen one of the status indicators signals that a problem exists, OMEGAMON for IMS can help youidentify the cause of this problem.

© Copyright IBM Corp. 2004, 2012 1

For example, OMEGAMON for IMS can provide information about what might be causing poorperformance for a particular group of transactions, and help you identify which resources or systemcomponents are busiest. You can also identify which components are unusually active when the responsetime for a particular group of transactions is delayed. You can then use this information to correct theproblem. If you need to issue an IMS command to correct the problem, you can navigate to panels whereyou can select IMS commands from a menu or issue IMS commands directly.

OMEGAMON for IMS online help system also provides advice for resolving problems.

User interfacesOMEGAMON for IMS offers the following user interfaces to IMS information.

v The menu interface provides the user access to real-time data with an easy-to-use menu system. Eachmenu option leads to a panel that displays appropriate commands and output.

v The command interface offers a set of extensive and flexible commands that cover almost every aspectof the IMS environment in real time.

v For historical information from the OMEGAMON for IMS historical component, users request printedreports via a batch report generator, or make interactive queries through a series of TSO panels. Forinformation about these interfaces, see the IBM Tivoli OMEGAMON XE on z/OS: Historical Component(EPILOG) User's Guide.

To navigate from the menu interface to the command interface or from the command interface to the menuinterface, press PF12.

Product componentsThis section provides background information about the product components for OMEGAMON for IMS.

The following table provides a brief description of each OMEGAMON for IMS component and indicateswhether the component is required or optional.

Table 1. Product components available with OMEGAMON for IMS

Component Description

CUA interface for the Realtime Monitor(optional)

A graphical user interface that provides real-time information about an IMSsubsystem

Realtime Performance Monitorcomponent (required)

Provides basic real-time information about the IMS environment

Menu interface for the Realtime Monitor(required)

The original OMEGAMON for IMS menu system interface that providesreal-time information about an IMS subsystem

Command interface for the RealtimeMonitor (required)

An extensive set of flexible commands that provides real-time informationabout an IMS subsystem

OMEGAMON Subsystem (optional) Provides dynamic I/O information to OMEGAMON for IMS

End-to-End Response Time (required) Provides OMEGAMON for IMS with response time data

Response Time Analysis (optional) Provides monitoring of IMS transaction and end-to-end response time

Application Trace Facility (ATF)(optional)

Tracks activity on a transaction by transaction basis and records theindividual events for transactions

Bottleneck Analysis (optional) Provides information for degradation analysis

Historical component (optional) Provides historical information about the IMS environment

IMS Console Facility (optional) Provides a complete IMS Master Console for OMEGAMON for IMS

Logging Facility, also known asJournaling Facility (optional)

Collects and saves Application Trace Facility data. This facility isautomatically enabled and configured if ATF is configured.

2 OMEGAMON XE for IMS on z/OS: OMEGAMON for IMS User's Guide

In previous releases, the configuration tool was known as CICAT (the Candle Installation and ConfigurationAssistance Tool). The configuration tool is still used to perform both installation and configuration ofprevious versions of products. In this context, the tool is called the installation and configuration tool(ICAT). However, for OMEGAMON XE zSeries® monitoring agents, the tool is known as the ConfigurationTool because it is used for configuration only and these components are installed by using SMP/E. Tomake these components available, you must:

v Use the Configuration Tool to configure the component.

v Use the instructions in this guide to complete the configuration and customization steps for thecomponent.

Modes of operationDuring configuration, you are asked to select and customize an operating mode. Available operatingmodes include:

v VTAM® mode (required to run the CUA interface)

v TSO/ISPF mode

v Dedicated mode

The following table describes each operating mode and its requirements.

Table 2. Characteristics and Requirements for OMEGAMON for IMS Modes of Operation

Mode Characteristics Configuration requirements

VTAM By using VTAM mode, you can run OMEGAMONfor IMS sessions from a VTAM terminal without anintermediate online application, such as TSO. Youcan set automatic update mode so that the screenrefreshes automatically.

VTAM mode allows all VTAM terminal users toshare a single copy of OMEGAMON for IMS.

Define a VTAM applid for OBVTAM.

TSO and ISPF The TSO address space communicates with theOMEGAMON for IMS address space via a VTAMapplication, VTM1. In this mode, there is no autoscreen refresh; the screen refreshes when youpress the Enter key. By using TSO mode, you canaccess OMEGAMON for IMS without logging offTSO.

ISPF mode includes split-screen capability that youcan swap between multiple OMEGAMON for IMSsessions, or between OMEGAMON for IMS andanother ISPF application.

v Define a VTAM applid for OBVTAM.

v Requires an active OBVTAMapplication.

v Define a set of virtual terminals toVTAM. You can define up to 99 virtualterminals in the virtual terminal pool(VTPOOL).

Dedicated Dedicated mode offers high availability and doesnot require VTAM services. Dedicated mode usesEXCP to communicate with a terminal andrefreshes the screen every few seconds.

Dedicated mode allows OMEGAMON for IMS toprovide real-time data even when VTAM is notavailable.

Availability of a locally attached non-SNAterminal.

If you choose to log on to the menu and command interfaces directly, you can do so with several differentmodes of operation that includes dedicated, VTAM, TSO, and ISPF modes. For information about thesemodes, see “Logging on to the menu/command interface directly” on page 31.

Chapter 1. Introduction 3


Chapter 2. Command basics

This chapter provides basic information about the format of the OMEGAMON for IMS command interfacepanel and the syntax of OMEGAMON for IMS commands. It also describes how to log screens and tocontrol screen output in command mode.

Accessing the command interfaceTo access the command interface from the menu interface, press PF12 or PF24. This same key togglesyou back to the menu interface.

You can enter commands in both the menu interface and the command interface. However, the PF keysettings are different in these two interfaces.

The PF keys in the menu interface support menu system navigation; in the command interface, they fetchanalysis screens directly. For example, in the command interface, pressing PF3 takes you to a screenspace named #03. New users might consider entering commands on the menu interface panels, ratherthan switching to the command interface. The menu interface is easier to use than the command interface.

Commands and screen spacesThere are two ways to operate OMEGAMON for IMS in the command interface: you can enter individualcommand names or you can execute screen spaces.

A screen space is a predefined set of commands that is saved in a file and given a name. When you typethe screen space name on the INFO-line and press Enter, all the commands assigned to that screenspace execute automatically in sequence. You can also assign a screen space name to a PF key, whichyou can use to execute the screen space with one keystroke.

Creating screen spaces is discussed in Chapter 3, “Screen spaces,” on page 21.

Panel formatFigure 1 shows the panel format.

Each line of the panel consists of an input area and a display area. You enter commands in the input areaon the left side of the screen, and OMEGAMON for IMS displays command output on the right of thescreen.

The input area of the top line, or the INFO-line, is where you enter menu options, INFO-line commands, orscreen space names. The display area shows status information about your session. In the main body ofthe panel, which follows the INFO-line, OMEGAMON for IMS accepts the input of other types ofcommands and displays their output.

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 8:37:46 B

<Main body of panel>

| <Input area> | | <Display area> |

Figure 1. Panel format


OMEGAMON for IMS processes data on the INFO-line first. If an entry there begins with a slash,OMEGAMON for IMS treats it as an INFO-line command. Otherwise, it attempts to find and display ascreen space by that name.

Next, OMEGAMON for IMS processes the input area of the main body of the panel. It executescommands as it encounters the commands, starting at the beginning of the panel.

INFO-lineThe following figure shows the format of the INFO-line, which can include the following components:

v The input area where you enter menu options

v Screen space name, for example, ZMENU

v Mode of operation, for example, VTM

v Logging status

v Product ID

v User profile suffix

v System ID

v Screen refresh date

v Screen refresh time

v Scrolling depth

v Automatic screen facility

v Screen stacking and bell status

The IBM Tivoli OMEGAMON XE for IMS on z/OS: Realtime Commands Reference discusses the statussymbols on the INFO-line in more detail. The symbols for the logging status (LOG), the scrolling depthoption (5), the automatic screen facility status (A), and the bell status (B) are displayed on the INFO-lineonly when those features are in use. Otherwise, the field is blank.

If the zero-value display option is on, the system displays zero values as zeros. If the option is off, thesystem displays zero values as blanks.

__________________ ZMENU VTM LOG OI-II V510./C I91C 03/25/09 8:40:23 5 AB| | | | | | | | | | ||

Input Area <---` | | | | | | | | | ||| | | | | | | | | ||

Screen Space Name <---` | | | | | | | | ||| | | | | | | | ||

Mode of Operation <---` | | | | | | | ||| | | | | | | ||

Logging Status <----` | | | | | | ||| | | | | | ||

Product ID <------` | | | | | ||| | | | | ||

User Profile Suffix <-` | | | | ||| | | | ||

System ID <-——-` | | | ||| | | ||

Screen Refresh Date <----—-` | | ||| | ||

Screen Refresh Time <---—--` | ||| ||

Scrolling Depth <---` ||||

Automatic Screen Facility <-----` ||

Screen Stacking and Bell Status <---`

Figure 2. INFO-line format


Panel display symbolsThis section explains the panel symbols that OMEGAMON for IMS displays with command output.

Comment lines (>)

To designate a comment line, enter a greater-than sign (>) in column 1. Any command entered onthat line does not execute.

In addition to the comment symbols that you enter yourself, OMEGAMON for IMS automaticallycomments out some commands after they execute to prevent re-execution on the next cycle.OMEGAMON for IMS also comments out help text so that it remains on the screen until you clearit.

Continuation character (+)

OMEGAMON for IMS displays a plus sign (+) at the end of a line of output to indicate when moreoutput is available. You might see this continuation character after you issue certain majorcommands that select a long list of items (such as DISK, which displays all online disks). So thatthe display does not extend off the screen, OMEGAMON for IMS displays only one line of data ata time unless you request additional lines. “Displaying continuation lines of command output” onpage 17 explains how to request the additional lines.

Online help text also displays the continuation character when more help is available.

Commands that produce multiple display lines when they execute display the plus sign (+) incolumn 1. For example, if you enter the .VTM command, multiple lines of information about VTAMusers are displayed as shown in Figure 3.

Commands that you enter after a command with multiple display lines might extend off the screen.These commands reappear as soon as you scroll through the output.

If you enter a new command on a continuation line, OMEGAMON for IMS automatically positionsthe new command after the existing output lines.

Input character (:)

Some commands allow multi-line input for setting parameters. When you issue this type ofcommand, OMEGAMON for IMS responds with a table of keywords and their current settings. Oneach line of a multi-line input command, column 1 displays a colon (:) to indicate that you canovertype the current setting and change the value as shown in Figure 4.

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 8:46:07 B.VTM Userid Terminal Mode Session Start Last Update

+ ATERM507 VTM 03/25/09 7:28:12 03/25/09 8:46:07+ RGI21102 VTM 03/25/09 7:57:06 03/25/09 8:46:07+ RGI21124 VTM 03/25/09 8:31:25 03/25/09 8:46:07

Figure 3. VTAM user information

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 8:51:37 B.SET

: FGOLIMIT = 64 FGOLOOP = OFF: GDEVUCBS = 200 INTERVAL = 5.00: IODELAY = 5 LOOPCOUNT = 50000: LOOPTIME = 150.00 PAGELIMIT = 400: PEEKSIZE = 16384 STATUSMODE = OFF: OCMDMASTER = ON

Figure 4. Keywords

Chapter 2. Command basics 7

Entering commandsTo operate OMEGAMON for IMS in the command interface, know the types of commands and theappropriate time and place to enter each type.

Command typesBeginning in column 1 of Figure 5, examples including sample output of the four types of commands usedin OMEGAMON for IMS are displayed.

The types of commands include:

INFO-line

These commands perform control functions such as printing a screen (/PRINT) and stopping yoursession (/STOP).

INFO-line commands are executed first and disappear as soon as they execute. Therefore, youcannot save them in a screen space. INFO-line commands always begin with a slash (/) and mustbe entered on the top line (starting in column 2).

If you are running in an automatic update mode, placing the cursor in column 1 on this line pausesupdating until you move the cursor.

Major

These commands select general categories for display, such as system information, resourceutilization, or storage utilization. In the example, the major command DISK produces a list of onlinedisks. You can enter major commands on any line after the INFO-line.

Minor

These commands display detailed information about the category that the major selects. In theexample, the minor command DADR displays the unit addresses of the devices listed with DISK.You can enter minor commands on any line after the INFO-line, but they do not execute unlessthey are preceded by an appropriate major command.

Immediate

These commands serve various functions. Some are system monitoring commands, while othersprovide information about your session or about OMEGAMON for IMS.

In the example, .MIN produces a list of all the minors of DISK. Immediate commands can alsoprovide screen and session controls, and often perform the same or similar functions as INFO-linecommands of the same name. You can include control commands as part of a screen space.

Enter immediate commands on any line after the INFO-line. You can enter immediate commandsbetween a major command and one of its minors.

Command formatsThe following is another example of different OMEGAMON for IMS commands and their output. Commandfields are four characters long. Commands can also be entered with labels or arguments, as shown inFigure 6 on page 9, and described following the figure.

/PRINT__________ KOI#01 VTM OI-II V510./C I91C 03/25/09 8:55:15 B

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2.MIN DADR DALC DIO DIOQ DOPN DRES DSTA DTYP DUSR DVMP +

Figure 5. Types of commands


Command format

label field

Many commands accept a character in the label field that alters the type of output displayed. Youcan also use this field for special command modifiers, such as those that request online help textfor commands.

In Figure 6, the numeral 2 in the label field of the GDEV command restricts the display to only thesecond row of all available output.

command name

This field contains the four-character command name. Although the command name field occupiescolumns 2 through 5, OMEGAMON for IMS recognizes most commands that begin in column 1and automatically shifts the command one space to the right.

argument field

Many commands accept arguments that modify their function or specify output options. In theexample, .MJ command produces a list of major commands. It is entered with an argument of DS,a group code that specifies that only disk major commands be listed.

Extended arguments are entered in columns 8 through 72. In the example, the GDEV command is enteredwith an argument of SYSDA, which is a generic device name in the system. This means that only devicesin the SYSDA category are displayed. Many commands also accept keywords and parameters that canextend to column 72. OMEGAMON for IMS cannot extend a parameter string to a second line. You mustre-enter the command (along with keywords) on succeeding lines.

Command helpOMEGAMON for IMS provides online help for every command in the product. This section describes howto request help for different kinds of commands.

Major, minor, and immediate command helpTo request an explanation of a major, minor, or immediate command, enter one of three symbols (?, /, or;).

All commands offer a brief, one-line help. Many commands also have an extended help, which providesmore information about the command or displays the command operands. A continuation character (+) tothe right of the one-line help indicates that more (extended) help is available.

? Display a one-line help start on the screen until you clear it.

.MJ DS DISK DLST DSKB DSKC DSKE DSKG DSKM DSKN DSKP DSKQ DSKR DSKS +

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2

2GDEV SYSDAMIS003 HSM001 WORKB1 PDB002 MIS002 MIS003 SYSB24 SYSD22 PROD02 +

lccccnn________|| | ||| | +-----> extended argument or keyword field (cols. 8 through 72)|| ||| +-----> argument field (cols. 6 and 7)|||+----> command name (cols. 2 through 5)|+--> label field (col. 1)

Figure 6. Command format


/

Displays an extended help that stays on the screen until you clear it.

You can clear the help text with the .DCL command discussed later in this guide.

; Displays an extended help that is no longer displayed from the screen on the next cycle.

Examples of the three help symbols used with the .WAT command follows. This entry for the .WATimmediate command

?.WAT

produces a one-line help as shown in Figure 7.

OMEGAMON for IMS comments out the help symbol when the help displays.

When you use a slash instead of a question mark,

/.WAT

an extended help displays as shown in Figure 8.

The entry

;.WAT

produces the same output as /.WAT, except that plus signs display in column 1 after the one-line help. Theplus signs are continuation symbols and indicate that the extended help text is not displayed on the nextcycle.

You can obtain help for a minor command by using the symbols previously described, without knowing theassociated major command name. In some cases, however, the same minor name is used for multiple

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:01:27 B>.WAT> Specifies a delay before executing the commands that follow. +

Figure 7. One-line help display

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:01:27 B>.WAT> Specifies a delay before executing the commands that follow. +>> Type of Command: Immediate>> Command Format: .WATnn>> 1 | 2 | Definition of operands> -----------------------------------------------------------------------> | .WAT | nn Specifies the length of the delay (seconds) before> | | the command(s) that follow are executed.>> EXAMPLE:>> .WAT02> .FGO MYSCREEN>> The commands shown above cause OMEGAMON to wait 2 seconds before> fetching screen space MYSCREEN.

Figure 8. Extended help display


majors. If the function of the minor command is the same for all of its associated majors, OMEGAMON forIMS displays a help panel like Figure 9.

In cases where OMEGAMON for IMS uses the same minor command name for multiple major commands,but the function and help text differ, OMEGAMON for IMS instructs you to place your cursor under themajor command name that you require. When you press Enter, the appropriate help displays.

If you know that several major commands share the minor command commands, type the major commandname on the same line after the help request. For example, the entry

/dio DISK

produces the help text for the DIO minor specific to the DISK major.

INFO-line command helpYou can obtain INFO-line with the .ILC immediate command rather than with a symbol in column 1. Enterthe name of the INFO-line command (cccccc) after .ILC:

.ILC cccccc

You do not need the slash before the command. For example, to get help for the /DEF command, enter:

.ILC DEF

A help panel like one shown in Figure 10 on page 12 displays.

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:01:27 B>DIO> DIO is a minor command of the following major(s):> DEV DEVL DEVP DISK DSKB DSKC DSKE DSKG DSKM DSKN DSKP DSKQ> DSKR DSKS DSKU DSKV GDEV TAPE TPAL TPBS TPCU TPFR TPMT TPOF> TP16 TP38 TP62 TP7T TP80 2305 2314 3330 3340 3350 3375 3380> 3390> Help:> Displays the I/O count since IPL of the device(s). +

Figure 9. Minor command help display


Commands to list commandsYou can use another form of help to list all OMEGAMON for IMS commands by type. You can also usesome of these listing commands to show brief help for each command that displays.

If you issue the .MJ, .MJC, .MJI, or .MIN command preceded by an H in the label field (column 1), aone-line help for each command displays. The display in Figure 11 lists available OMEGAMON for IMScommands:

OMEGAMON for IMS commands

.MJ Deletes lines

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:02:53 B>.ILC /DEF> Sets definition mode. +>> Type of Command: INFO-line>> Command Format: /DEF cccc>> 1 | 2 Definition of operands:> ----------------------------------------------------------------------> | /DEF <cccc> ON Turns on definition mode. Definition mode> | suspends command execution (except for the> | commands which control screen editing> | functions) so that you can define a screen> | space without executing commands. Once you> | set definition mode with /DEF ON, it remains> | in effect until you issue /DEF OFF or the> | screen space is saved or replaced.> | OFF Restores normal command execution (cancels> | /DEF ON or /DEF HOLD).> | HOLD Same as ON argument, but definition mode> | remains in effect after you save a screen> | space. It is only cancelled when you issue> | /DEF OFF. Use this option when you want to

Figure 10. INFO-line command help

>.MJ>..> Deletes lines(s). +>.AUP> Displays/resets the status of automatic update in VTAM mode. +>.BEL> Displays/sets bell (audible alarm) support. +>.CN> Opens, closes, swaps, or sets address of the secondary console. +>.D> Deletes lines(s). +>.DCL> Deletes its own line and all comment lines below it. +>.DD> Deletes a block of data from the screen. +>.DEF> Displays/resets the status of definition mode. +>.DIR> Executes a director/collector command.>.DSA> Sets authorization to list and/or zap non-sharable data-only spaces. +>.DSE> Displays the status of the stack. +

Figure 11. Commands that list commands


.AUP Displays or resets the status of automatic update in VTAM mode

.BEL Displays or sets bell, that is, an audible alarm support:

.CN Opens, closes, swaps, or sets the address of the secondary console

.D Deletes lines

.DCL Deletes its own line and all comment lines that follow it

.DD Deletes a block of data from the screen

.DEF Displays/resets the status of definition mode

.DIR Executes a director/collector command.

.DSA Sets authorization to list and or eliminate non-sharable data-only spaces

.DSE Displays the status of the stack

You can limit the major command listing produced with .MJ, .MJC, or .MJI to a particular group ofcommands by typing the group code. Type .MJ for a list of the group codes.

Screen controlThis section describes the following screen control functions:

v Scrolling

v Clearing the screen

v Clearing comment text only

v Inserting and deleting lines

v Using program function keys

v Displaying continued lines of command output

v Delaying automatic updating

ScrollingIn the menu interface, you use PF7 and PF8 for scrolling. However, in the command interface,OMEGAMON for IMS assigns PF7 and PF8 to analysis screens, so PF19 and PF20 are the defaultscrolling keys (on terminals with 24 programmed function keys). The keys are set to /UP and /DOWN(alias /U and /D), and you can scroll one physical screen at a time. You can change the default scrollamount with the OPTN command. You can also scroll by using the /UP and /DOWN INFO-line commands.Both /UP and /DOWN accept the following arguments:

nnn Scrolls nnn lines (nnn can be any number from one to 999).

PAGE Scrolls a physical screen at a time.

MAX Scrolls up or down the number of LROWS defined for your terminal. The short form of MAX is M.

CSR Scrolls according to the current location of the cursor. If the cursor is on the INFO-line, the scrollamount is one page.

As an alternative to /UP and /DOWN, you can use the INFO-line command /TOP to scroll to the top of thelogical screen and /BOTTOM to scroll to the bottom of the logical screen.

You can also type any of the /UP and /DOWN arguments (such as nnn, MAX, or CSR) on the INFO-linebefore you press the PF key. If, for example, you type MAX on the INFO-line and then press PF20 tochange the scroll amount, OMEGAMON for IMS scrolls forward the maximum number of lines.


Clearing the screenIf a menu, screen space, or any commands display on your screen, and you want to clear the screen, usethe clear screen immediate command. The clear screen command consists of two periods followed by twoblanks. Enter ..bb in the input area of any line below the INFO-line to clear the screen below it.

Deleting comment linesIf your screen contains multiple lines of comment text, and you want to clear the comments but retainother command text, you can enter the /DCL INFO-line command or the .DCL immediate command. The/DCL command clears all comment lines on the logical screen, while the .DCL command clears all commentlines after its entry line.

Figure 12 is an example of how to use the .DCL command to clear help text.

On the next cycle, the panel shown in Figure 13 displays.

Inserting and deleting linesTo insert blank lines into a screen, use the following immediate command:

.I nn

The variable nn indicates the number of lines to insert. The default is 1. The nn argument must begin incolumn 6.

OMEGAMON for IMS inserts the new lines above the line where you type the insert command. Therefore,all other lines currently on the screen that follows the inserted line move downward. When the commandexecutes, the line that you typed over with the insert command restores to its original data. The followingdisplay, Figure 14 on page 15, presents the screen in which you can insert a blank line by using the .I nn

/dcl____________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:03:45 B>.SPT> Sets pattern number n to the value cccccccc for generic selection..SPT/1 >M* <DEVP/1 MVSA21 MP220A MP220D MVSD21 MVSE21

>dadr> Device unit address (cuu)>dio> Device I/O count (For rate use: 'DIO.R’)>dres> Number of outstanding RESERVEs from this CPU for this device.DEFON >> OB0130: Definition mode ENABLED. <<DEVP/1dadrdalcdio.DEFOF >> OB0130: Definition mode DISABLED. <<

Figure 12. Using the DCL command

________________ KOI#01 VTM OI-II V510./C I91C 03/25/09 9:04:03 B.SPT/1 >M* <DEVP/1 MVSA21 MP220A MP220D MVSD21 MVSE21.DEFON >> OB0130: Definition mode ENABLED. <<DEVP/1dadrdalcdio.DEFOF >> OB0130: Definition mode DISABLED <<

Figure 13. Result of the DCL command


command. This is step 1 of 3:

In step 2 of 3, Figure 15 shows how you enter .I on the second line of the screen:

In step 3 of 3, Figure 16 shows how OMEGAMON for IMS inserts one blank line after the first line, andrestores all the original data on the second line:

To delete lines from a screen space, use the .D nn immediate command. This command works like .I nn.The default is 1.

To delete a block of data from the physical screen, enter.DD on the first and last lines of the block.

Selecting Program Function (PF) keysWhen you use the command interface, the default PF key definitions differ from those key definitions usedin the menu system. In the command interface, some PF keys are preset to control commands such asscrolling and printing, and a number of keys are set to IBM-defined screen spaces for various types ofanalysis. Use the .PFK immediate command to list the settings.

Figure 17 on page 16 lists the default PF key definitions in the command interface.

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2dalc 8 16 6 12 24 16 32 8

Figure 14. .I command (step 1 of 3)

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +.I 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2dalc 8 16 6 12 24 16 32 8


DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +

dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2dalc 8 16 6 12 24 16 32 8



You can define new PF key settings for your current session with the .PFK command. For example, whileyou create a screen space, you could assign the /DEF ON to PF19 to turn definition mode ON and /DEFOFF to PF20 to turn definition mode OFF when you finish. Define the keys and type comment text (afterthe slash and asterisk (/*) as shown in Figure 18).

The PF keys that you define with .PFK are in effect only for the current session.

You can use the installers to assign screen spaces or use the INFO-line commands to assign up to 99 PFkeys by using the .PFK immediate command.

You can access 99 logical PF keys by typing the PF key number on the INFO-line. You can redefineseveral PF keys at once without having to re-enter the .PFK command.

1. Beginning in column 1, type:

E.PFK

and press Enter. OMEGAMON for IMS gives you an extended display of all current PF keyassignments, and inserts .PFK before each key number as shown in Figure 19.

2. For each new assignment, blank out the plus sign (+) in front of .PFK and type the new assignmentafter the equal sign. When you press Enter, the assignments take effect for the duration of the session.

.PFK+ 01=KOI#01 /* EXCEPTION ANALYSIS, GENERAL INFO+ 02=KOI#02 /* ANALYZE ONE IMS REGION+ 03=KOI#03 /* ANALYZE ALL DEPENDENT REGIONS+ 04=KOI#04 /* PROGRAM SPECIFICATION BLOCKS+ 05=KOI#05 /* DATABASE MANAGEMENT BLOCKS+ 06=KOI#06 /* TRANSACTIONS+ 07=KOI#07 /* LOGICAL TERMINALS+ 08=KOI#08 /* SCHEDULING CLASSES+ 09=KOI#09 /* DEVICE STATISTICS (DASD TAPE)+ 10=KOINOSHI /* SELF EDUCATION FACILITY REPLACED+ 11=KOI#11 /* NO ASSIGNMENT YET+ 12=KOISWCH /* COMMAND MODE/MENU MODE TOGGLE+ 13=KOI#13 /* IMS INITIALIZATION PARAMETERS+ 14=KOI#14 /* IMS DATASETS STATISTICS+ 15=KOI#15 /* REAL, VIRTUAL MEMORY UTILIZATION+ 16=KOI#16 /* IMS POOL STATISTICS+ 17=KOI#17 /* DATABASE BUFFER POOL STATISTICS+ 18=KOI#18 /* DUMPING IMS CONTROL BLOCKS+ 19=/U /* SCROLL UP+ 20=/D /* SCROLL DOWN+ 21=/PRINT /* PRINT THE CURRENT SCREEN+ 22=KOI#22 /* CONTROLLING EXCEPTION ANALYSIS+ 23=KOI#23 /* CONTROLLING EXCEPTION GROUPS+ 24=KOISWCH /* CMD/MENU MODE TOGGLE

Figure 17. PFK definitions in command mode

.PFK19=/DEF ON /* Turns definition mode on

.PFK20=/DEF OFF /* Turns definition mode off

Figure 18. Display of .PFK command

+.PFK21=/P /* PRINT CURRENT SCREEN

Figure 19. Extended display of all PF key assignments


Displaying continuation lines of command outputSome major commands select a series of items. Often, the display output does not fit on one line. In thiscase, the major command displays only the first line of output, and a plus sign displays to indicate thatmore data is available.

To see a count of the number of items selected by a major command, enter a pound sign (#) in column 1before the command. The following example shows that there are 20 online disks for the DISK commandto display:

#DISK 20

Continuing major command output

You can use a number of different continuation characters and commands to control the outputdisplay.

v Enter a less-than sign (<) in column 1 in front of a major command to generate all the output atonce when it executes, as shown in the following figure.

v After you issue a major command for the first time, you can put a number in column 1 to specifyhow many lines of the display to skip.

v You can repeat a major command to display only the next line of output.

Continuing major and minor command output

When a major command lists a series of items that continues for more than one line, any minorcommand that you enter after the major command applies only to the last line of output. Therefore,if you enter a minor command after the third line of major command output, that minor commandonly generates information about the third line of items listed by the major. Normally, the major andminor commands must be repeated once for each line of available output.

The .RC command is a shortcut to this process. The .RC command automatically repeats themajor and the minor until all available lines of data are displayed. Enter the major command once,followed by the minor commands, and then .RC after the minor commands as shown in thefollowing figure.

Delaying automatic updatingThe delay and hold features temporarily defer updating when you are in dedicated mode or in VTAM modewith automatic updating in effect (see the .AUP command).

Delay feature

<DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02

Figure 20. Continuing major command output

DISK VMXA04 VMXA05 VMSP50 VMHP02 OMONVM DOSTST DP215R DOSRES +dadr 1A0 1A1 1B0 1B1 2A7 2B0 4F1 4F2dio 4157 4240 3975 4010 4422 272 1638 1147DISK PPSMPE TSO024 QM0001 OMON25 MTBLI3 DB2002 PPSMPE TSO042 +dadr 148 149 14A 14B 14C 14D 14E 14Fdio 6157 40885 3325 4115 277 1122 44322 48995DISK CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02dadr 4F3 4F4 4F5 4F6 4F7 4F8dio 3284 2140 3287 3967 298 275

.RC

Figure 21. Continuing major and minor command output


While OMEGAMON for IMS is automatically updating, you can continue to enter commands. IfOMEGAMON for IMS detects a cursor movement since the last update, it defers processing toavoid executing half-entered input. The words "I/O Delay" appear on the INFO-line, and the screenis not updated for the number of cycles specified with the IODELAY keyword of the .SETcommand.

Hold feature

If your screen display contains data that you want to study for longer than the normal automaticupdate interval, you can use the hold feature to temporarily freeze the screen image. To do so,place the cursor in the Home position, then move it back one space to the blank space in column1 of the INFO-line. The words "Hold Mode" appear on the INFO-line, and the information about thescreen does not change until you move the cursor away from row 1, column 1.

Screen logging

The OMEGAMON for IMS logging facility supports your printing screen spaces, output appearingon the logical screen, or selected lines from the screen. When the log is on, a copy of everyscreen display is written to the log. The OUTP major command sets the characteristics of theREPORT file.

OMEGAMON for IMS can log exception analysis screens automatically with the exception loggingfacility (XLF).

Activating the logTo turn on the log, enter the OPTN immediate command in the input area of the main body of the screen.Two columns of session options appear as shown in Figure 22.

The status of the log (ON or OFF) displays after the LOG= entry. To initiate logging, type ON over the OFFentry. The word LOG appears on the INFO-line when the log is activated.

When the log is on, OMEGAMON for IMS logs the screen output on each cycle. If you freeze the screenwith the hold feature during automatic updating OMEGAMON for IMS logs only once until you move thecursor from row 1, column 1.

To force printing of the log, enter the /LOGOUT INFO-line command or the .LOGOUT immediatecommand. This command closes the current log file and dynamically reallocates it so that it is immediatelyreopened. If you set new parameters for the log file, you must issue a LOGOUT command for the newparameters to take effect.

To turn off the log, re-enter the OPTN command and type LOG=OFF over the LOG=ON entry. The wordLOG is no longer displayed on the INFO-line.

Checking the page limitThe OMEGAMON for IMS profile in effect at your site contains a default limit on the number of pages thatare printed before the log stops. The PAGELIMIT= keyword of the .SET immediate command controls thepage limit.

________________ KOIMENU VTM OI-II V510./C I91C 03/25/09 9:11:35 B

OPTN: ASF = OFF BELL = OFF: BELLINT = 60.00 DATEFORMAT = USA: FIRSTSCREEN = KOINITZZ LOG = OFF: MINORCASE = LOWER SCREENCASE = MIX: SCROLL = PAGE TSF = OFF: XLF = OFF ZEROES = OFF

Figure 22. Session options


Before the log begins to print, .SET displays the current default page limit. To change the limit for yoursession enter .SET and type a new value over the old one, after the PAGELIMIT= keyword.

During printing, the number displayed by .SET decreases to reflect the number of pages that can beprinted before the limit is reached. You can check the progress of the log by entering .SET while logging.When the page limit display reaches zero, the screen space clears and a message appears to inform youthat the page limit was reached. Press Enter to restore the screen display.

Logging a single displayTo print a single screen image without turning on the log, use the /PRINT (or /P) INFO-line command.

The PAGELIMIT= keyword does not affect the /P command. /P continues to work even when the counteris at zero.

Logging part of a displayTo print selected lines from a screen space, use the .PRT command (see Figure 23).

In this example, OMEGAMON for IMS logs one copy of the lines that precedes the .PRT command, andthen changes the command to a comment (>.PRT). To log these lines continually, add the H (Hold)argument to .PRT (.PRTH), which prevents OMEGAMON for IMS from changing the command to acomment.

DISK CPM023 DBRCPROD DLSPROD IRLMPROD MPP01 MPP02dadr 4F3 4F4 4F5 4F6 4F7 4F8>.PRT >> Screen Printed up to this line <<dalc 8 16 6 12 24 16 32 8

Figure 23. .PRT command



Chapter 3. Screen spaces

Through its powerful screen space feature, OMEGAMON for IMS can store, recall, and invoke a set ofcommands. The OMEGAMON for IMS program includes a number of predefined screen spaces, whichprovides you with detailed information by category.

Invoking screen spacesYou can invoke an IBM-defined screen space by selecting a menu option, or by pressing certain PF keys(if you are working in the command interface). You can also create custom screen spaces and recall themby typing the screen space name on the INFO-line, or by assigning the screen space name to a PF key.

When you invoke a screen space, its commands replace the commands currently on the screen. Thecommands then execute in the same way as they would if you entered them individually. You must set upscreen spaces in advance of an OMEGAMON for IMS session in order to use the OMEGAMON for IMSautomatic screen facility, the timed screen facility, and the zooming feature.

Creating or modifying screen spacesYou can create a screen space at any time on any screen by simply typing in a group of commands,assigning a name to them, and saving them. Note the following points about creating screen spaces:

v Include separator lines in screen spaces you create to make the screen more readable. OMEGAMONfor IMS automatically draws a separator line across the screen for you with the ==== immediatecommand. The format of this command is c====aa. Use the variable c to specify the color, if youextend color on your terminal. Use the variable aa to specify the characters that you want to use for theline.

v Use comment lines, wherever appropriate, to explain the commands. Begin all lines of comment textwith a greater-than sign (>) in column 1.

v If you include any commands that are commented out after execution, use the definition mode(described later in this section) while you design the screen. By doing this, you prevent the commentcharacter (>) from appearing in column 1 when you save the screen.

v You cannot include INFO-line commands as part of a screen space. Instead, use the equivalentimmediate command.

v OMEGAMON for IMS does not save blank lines at the end of a screen space.

v Use the /REP or /SAVE commands to save the cursor in a particular position on the screen.

The default cursor position is the first position of the INFO-line. To save the cursor in another position,type/REP or /SAVE on the INFO-line, move the cursor to the desired position, and then press Enter toexecute the command. The cursor then appears in that position whenever OMEGAMON for IMSinvokes the screen.

v Use a standard text editor to create or alter screen spaces. When you use a text editor to view or edit ascreen, keep in mind the following points:

– You can add or change the cursor position in a saved screen by adding or changing CURS=(n,m.).

– Figure 24 on page 22 shows a screen created for a screen space named SAMPLE. The commandexplanations are provided following the diagram.

Typical user-created screen space


ISYS Displays general IMS information

MSYS Displays overview MVS information

LXIMS Displays exceptional conditions

XPIQ Displays program isolation conflicts

OMEGAMON for IMS accepts variable symbols as arguments for commands. Use the .VAR immediatecommand to set variable symbols for use in designing screen spaces. You can define the variables atOMEGAMON for IMS startup or at any other time during your session. For more information about usingvariables, see “Setting and using variables” on page 28.

To create or modify a screen space, follow this procedure:

1. Use definition mode to inhibit updating and prevent OMEGAMON for IMS from executing thecommands that you entered.

If you are creating a single screen space, enter the .DEFON immediate command or the /DEFONINFO-line command to place OMEGAMON for IMS in definition mode.

If you are creating several screen spaces at once, use /DEF HOLD or .DEFHO to preserve definitionmode until you issue a /DEFOFF or .DEFOFF command. Otherwise, saving the screen spaceautomatically turns off definition mode.

2. Enter the desired commands on the screen.

3. Use the /SAVE INFO-line command to save the screen. To replace an existing screen space with anew screen space of the same name, use the /REP command. See the IBM Tivoli OMEGAMON XEfor IMS on z/OS: Realtime Commands Reference for the format of /SAVE and /REP.

4. Use .DEFOFF or /DEFOFF to restore automatic updating if you turned on definition mode with theHOLD option in step 1.

Loading screen spacesThe LSCR immediate command loads screen spaces from disk storage to main storage. By placing screenspaces in main storage with LSCR, you make them more available and more easily fetched. If a disk isnot available, you can continue to invoke the screen spaces that you loaded into main storage with LSCR.

The format is:

LSCR cccccccc cccccccc . . . cccccccc

________________ SAMPLE VTM OI-II V510./C I91C 03/25/09 9:16:32 B>================= DISPLAY GENERAL IMS INFORMATION ==========================>ISYS

>>================= DISPLAY OVERVIEW MVS INFORMATION ==========================>MSYS

>>================= DISPLAY EXCEPTIONAL CONDITIONS ==========================>LXIMS>>================= DISPLAY PROGRAM ISOLATION CONFLICTS ======================>XPIQ

>

Figure 24. Typical user-created screen space


The variables are screen space names. Beginning with column 8, specify screen space names. You canload as many screens as can fit on the input line, up to the last eight columns. The following exampleinstructs OMEGAMON for IMS to load screen spaces ZZ1, ZZ2, and ZZ3 from disk to main storage.

LSCR ZZ1 ZZ2 ZZ3

Listing screen spacesUsed without an argument, the SCRN immediate command lists all screen spaces in main storage and inthe disk data sets, which are pointed to by the RKOIPCSV and CANSOI ddnames. You can limit the list byusing arguments to request a list of screens in main storage only, disk only, or both. You can also specifyalphabetic limits for a range of member names, and use wildcard characters. See the IBM TivoliOMEGAMON XE for IMS on z/OS: Realtime Commands Reference for details.

Figure 25 shows a typical default screen space listing. OMEGAMON for IMS sorts the list by data set, within-storage screens first, followed by RKOIPCSV, then each data set in the CANSOI concatenation.

Renaming a screen spaceUse the RENM immediate command to rename a screen space. The RENM command accepts anargument that specifies where the screen space is to be found.

To rename the SAMPLE screen space to EXAMPLE in both main storage and RKOIPCSV, enter:

RENMB SAMPLE EXAMPLE

The following message appears:

>> Member “SAMPLE” Renamed to “EXAMPLE” Both In-Storage and in RKOIPCSV <<

The screen space SAMPLE no longer exists.

>SCRNB $ thru 99999999> In-storage screen facility 20 members 4232 bytes used> $ #01 #02 #03 DEBUG DEBUG01 DEBUG02 DEBUG03> ...> RKOIPCSV TDIMST.I5420SMP.IP10.I91C.RKOIPCSV> #01 SAMPLE VSAM> RKOIPROC TDIMST.I5420SMP.IP10.I91C.RKOIPCSV> #01 SAMPLE VSAM> RKOIPROC+01 TDIMST.I5420SMP.IP10.RKOIPROC> #01 #02 #03 #04 #05 #06 #07 #08> #09 #10 #11 #13 #14 #15 #16 #17> #18 #19 #20 #21 #22 #23 A AD> ADA ADADA ADADB ADADC ADADD ADADE ADADF ADADG> ADADH ADB ADBDA ADBDB ADBDC ADBDD ADBDE ADBDF> ADBDG ADC ADCDA ADCDB ADCDC ADCDD B BD> BDA BDB BDC BDD C CD CDA CDADA> CDADB CDADC CDADD CDADE CDB CDBDA CDBDB CDBDC> CDC CDCDA CDCDB CDCDC CDCDD CDD CDDDA CDDDB> CDDDC CDDDD CDDDE CDDDF CDDDG CDE CDEDA CDEDB> CDEDC CDEDD CDEDE CDEDF CDEDG CDEDH CDEDI CDEDJ> ...

Figure 25. Default screen space listing

Chapter 3. Screen spaces 23

Deleting a screen spaceUse the DELT immediate command to delete screen spaces. deletes screen spaces only from main storageand the data set pointed to by the RKOIPCSV ddname, not from CANSOI, the read-only data set. TheDELT command accepts an argument specifying where the screen space is to be found.

To delete the screen space SAMPLE from both main storage and RKOIPCSV, enter:

DELTB SAMPLE

The following message displays:

> >> Member “SAMPLE “ Deleted Both In-Storage and from RKOIPCSV <<

Invoking screen spaces automaticallyOMEGAMON for IMS offers the capability of chaining together a group of screen spaces, so that an entireseries of screens can execute without operator intervention.

An .SGO or .FGO immediate command, entered in a predefined screen space, fetches the next screenautomatically. The .FGO (fast go) and .SGO (screen go) commands perform identical functions, but .SGOdisplays the screens as they execute, whereas .FGO bypasses the OMEGAMON for IMS cycle and theterminal display.

The screen space fetch feature is useful when using the OMEGAMON for IMS Automatic Screen Facility(ASF) or Timed Screen Facility (TSF). The ASF invokes your system to react automatically to problemconditions that occur in the system. It can invoke predefined screen spaces with commands thatinvestigate the problem condition in detail and then log the output. By using TSF, you can schedulemonitoring of tasks at regular intervals.

See the IBM Tivoli OMEGAMON XE for IMS on z/OS: Realtime Commands Reference for an explanationof how to set up ASF and TSF.

Conditional screen space fetchingThe .FGO and .SGO commands give you the flexibility of conditional screen space fetching. You can enteran argument, which might include relational operators, to fetch a screen space only if certain conditionsare true. Use relational operators to compare the CPU serial number, the mode of operation, the operatingsystem level, the profile in use, the SMF ID, the OMEGAMON for IMS console address, or any variablethat you set with the .VAR command. For example, to specify that you want to fetch screen spaceSAMPLE only if you are running in an ESA 3.1 environment, enter:

.SGO SAMPLE OPSYS=310

Delayed screen space fetchingYou can delay the fetching of a screen space for a specified number of OMEGAMON for IMS cycles byusing the .SGO command. By using this command, you can accommodate commands that take more thanone cycle to initialize (gather data). It also permits you to log several successive executions of a screenspace before moving on to the next screen space. The label in front of .SGO specifies the delay.

n.SGO screenname

The variable n can be a number that represents a delay of 1-9 cycles or a letter from A-Z representing adelay of 10-35 cycles.


Looping screen spacesAn improper sequence of .FGO screens could cause a looping condition. To protect against this possibility,OMEGAMON for IMS limits the number of consecutive fetches allowed (64 by default). After reaching thislimit, .FGO acts like .SGO so that executing screen spaces display on each cycle. Once .FGO screenspaces cause a loop, you need to correct the condition and re-enable .FGO.

To re-enable .FGO, use the FGOLOOP keyword of the .SET command. The FGOLOOP keyword is set toOFF until the limit of consecutive fetches is reached. At that point OMEGAMON for IMS sets FGOLOOP toON, indicating the probability of a loop. To reset .FGO, issue the .SET command and replace the ONargument with OFF.

Testing .FGO routinesBecause FGOLOOP=ON causes .FGO not to bypass the OMEGAMON for IMS cycle and the terminaldisplay, you might want to turn it on yourself to test your screen space fetch routines.

Manipulating the log within screen spacesTo log screen spaces selectively, the .LOG immediate command has PUSH and POP arguments. You caninclude these arguments in screen spaces to change the ON or OFF status of the log when you branch toother screen spaces, and to return the log to its original state after the screen routines complete.

For example, if you have a series of four screen spaces chained together with .FGO and you want to logonly the last two, you can use .LOGPUSH and .LOGPOP in the following manner:

1. At the end of screen space 2, enter .LOGPUSH to have OMEGAMON for IMS record the previousstatus of the log.

2. Enter OPTN LOG=ON to turn on the log at the beginning of screen space 3.

3. Enter .LOGPOP at the end of screen space 4.

This causes the log to be restored to its original status when your branching routine is complete.

The .LOGPUSH and .LOGPOP functions are performed automatically when you log screen spaces byusing the Exception Logging Facility (XLF), the Automatic Screen Facility (ASF), or the Timed ScreenFacility (TSF).

Chapter 3. Screen spaces 25


Chapter 4. Advanced commands and features

This chapter highlights some of the OMEGAMON for IMS operational features not covered in earlierchapters:

v Rate and difference command arguments

v Variable substitution

v The zooming feature

v Secondary dedicated terminals

If you operate OMEGAMON for IMS through the menu system, you already use zooming and variablesubstitution. This chapter shows you how you can also take advantage of these features in customizingyour own sessions.

Rate and difference command argumentsFor minor commands that normally display numeric values, you can use arguments to change the outputto a rate or to a difference between OMEGAMON for IMS intervals. You enter rate or difference argumentsin columns 6 and 7 after the command. The rate and difference command arguments are:

.S or .RDisplays the output as a rate per second.

.M Displays the output as a rate per minute.

.H Displays the output as a rate per hour.

.D Displays the output as a difference between the two most recent values of the parameter (that is,between OMEGAMON for IMS cycles).

The RGNA major command selects all regions for display, and the JPUI minor command displays thenumber of private area page-ins. When the .R argument is entered after the JPUI command, OMEGAMONfor IMS displays a rate of four page-ins per second for the region TDO310A.

OMEGAMON for IMS requires data from two cycles to calculate a rate or a difference. On the first cycle(the initialization cycle), a row of eight periods (........) appears, indicating that the rate appears on the nextcycle. The rate and difference arguments are not effective in the following cases:

v If a major command selects different items from cycle to cycle. For example, the DSKB major commandmight select different busy disks at each screen update. When a rate argument is used with a minor ofDSKB, the periods might display after each update, indicating that OMEGAMON for IMS is initializingeach time.

v If a command displays a value that is reset to zero by the system between OMEGAMON for IMSintervals.

For commands that normally display time values (for example, CPU time), any rate calculated represents ascaled percentage of utilization (expressed as a decimal value), where the real time of the interval equals100%.

RGNA BMPRGN01 BMPRGN02 BMPRGN03 BMPRGN04 BMPRGN05 BMPRGN06 BMPRGN07jpui 921 134 258 179 69 1074 50jpui.R .4

Figure 26. .R argument


Setting and using variablesYou can use variables in building OMEGAMON for IMS screen spaces by using the .VAR immediatecommand. With this capability, you can exploit the powers of various other OMEGAMON for IMS features.For example:

v Build generic screen spaces that pick up values and analyze any number of like items, such as devices.The OMEGAMON for IMS zooming feature uses this capability.

v Set up conditional branches to other screen spaces (using .FGO) based on relationships of variablevalues.

v Pick up values in screen spaces designed for IMS automating and logging features: XLF, ASF, and TSF.

You can use variables in several ways.

v You can define your own variables with .VAR. For example:

.VAR SET &NXTSCRN MONITOR

.VAR SET &DEVICE 123

v You can use .VAR with relational operators to set a variable equal to a value under the conditionspecified. For example, you can specify that a variable is resolved only if a device address is greaterthan 150.

v You can use variables that are internally defined by OMEGAMON for IMS at initialization. They are:

– &ZFRSTSS - first screen space name

– Zoom command variables (see /ZOOM)

– Exception variables (cccc is the exception name):

&ZXccccTThreshold value

&ZXccccVLast trip value

&ZXccccWWorst trip value

v You can use the following keywords for conditional setting of variables. Their values are initialized byOMEGAMON for IMS.

CPSERThe CPU serial number.

DIR The ID assigned to the director in cross system mode.

MODE The mode of operation for OMEGAMON for IMS.

OPSYSThe operating system level.

PREFIXThe OMEGAMON for IMS product code.

IMSID The system ID from the SYS= startup parameter.

UNIT The device number from the UNIT= startup parameter.

USER The profile suffix from the USER= startup parameter.

&var A variable. Allows you to set any comparison you want.

For example, to pass values to screen spaces with .SGO, enter the following commands:

.VAR SET &NXTSCRN MONITOR


.VAR SET &DEVICE 123

This sets values for NXTSCRN and DEVICE. You can now use those variables in a screen space:

DEV &DEVICE

DIO

.SGO &NXTSCRN

OMEGAMON for IMS interprets the screen space entries as if you entered the following:

DEV 123

DIO

.SGO MONITOR

You can also set variables conditionally. In the following example, the variable SYSTEM is set to A if thevariable SWITCH is set to YES; SYSTEM is set to B if SWITCH is set to NO; and SYSTEM is set to C ifSWITCH is set to MAYBE.

C.VAR SET &SYSTEM A &SWITCH=YES

C.VAR SET &SYSTEM B &SWITCH=NO

C.VAR SET &SYSTEM C &SWITCH=MAYBE

In the following example, the variable TOKEN is set to IMS only if the product prefix is OI:

C.VAR SET &TOKEN IMS PREFIX=OI

The zooming featureIBM designed the zooming feature to simplify the investigation of system conditions by supplying adetailed level of information at the touch of the Zoom key. /ZOOM substitutes whatever value the cursor ison for a variable contained in a predefined screen space. In the OMEGAMON for IMS software, the/ZOOM INFO-line command is assigned to the PF11 key.

You can use zooming to perform the same operation on a series of items. By using the cursor as a pointerand pressing the Zoom key, you can get a detailed analysis of any device, volume serial number, oraddress space.

The OMEGAMON for IMS menu system uses the zooming feature extensively. For example, when you arelooking at a display of databases, you can place your cursor on a database name and press PF11.OMEGAMON for IMS zooms to a panel that gives detailed information about that database.

In the menu system, when there are fields on a display that respond to the Zoom key, such as exceptionnames or device names, Zoom PF11 is shown after the INFO-line as shown in the following example.

________________ KOISYS VTM OI-II V510./C I91C 03/25/09 9:16:32 B> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11================================================================================

Figure 27. Zoom PF11

Chapter 4. Advanced commands and features 29

You can use zooming in the command interface by setting up customized investigative screen spaces andzooming on command or exception names. For example, a systems programmer might want to set up ascreen space to monitor an intermittent performance problem. The screen space can include commandsthat give specific information about the problem area, as well as a command to turn on the log. When theproblem recurs, an operator can zoom to the screen space. OMEGAMON for IMS executes the screenand logs the information for the programmer to examine later.

For a more thorough discussion of the zooming feature, see the /ZOOM INFO-line command in the IBMTivoli OMEGAMON XE for IMS on z/OS: Realtime Commands Reference.

Note the following guidelines when setting up screen spaces for use with the /ZOOM command.

v The screen space name must start with a four-character prefix that begins with an alpha or nationalcharacter (@ZOM is the default) and is followed by the command or exception name (@ZOMcccc).

v When creating your own zooming screen spaces, you can name them with your own prefix (aaaa)instead of @ZOM. To invoke a zooming screen space that has your aaaa prefix, complete one of thefollowing steps:

– Type /ZOOM aaaa on the INFO-line, move the cursor to the data, and press ENTER.

– Type aaaa on the INFO-line, move the cursor to the data, and press the Zoom key.

– Redefine the Zoom key, PF11, or assign another PF key to /ZOOM aaaa, move the cursor to thedata, and press the Zoom key.

Secondary console controlIf you run OMEGAMON for IMS in dedicated mode, you can set up a secondary console for output displayonly. The secondary console is a repeater console; it echoes everything that appears on the primaryconsole, but accepts no input of any kind.

To use a secondary console, first define the unit, and then open it up for OMEGAMON for IMS outputdisplay. To define the console, enter the .CNxxx immediate command, where xxx is the hexadecimaladdress of the secondary console. Then, enter .CN OP to open the console for OMEGAMON for IMSoutput display. The secondary console, like the dedicated console, must be a non-SNA local device.

To close a secondary console, enter the .CN CL command. You can also enter the .CN SW command toswitch the primary and secondary console functions.


Chapter 5. Operating from the menu/command interface

You can log on to the menu/command interface directly in VTAM, ISPF, TSO, and dedicated modes. Fromthe menu/command interface, you can:

v Start exception analysis

v View exception analysis summary information

v Respond to exception messages

v Control and customize exceptions

v Perform message exception analysis

Logging on to the menu/command interface directlyIf you choose to log on to the OMEGAMON for IMS menu/command interface directly, you can do so inseveral different modes of operation. These include VTAM, ISPF, TSO, and dedicated modes. Each ofthese modes and their advantages are described as follows.

For information about how to install and start OMEGAMON in each mode, see the IBM TivoliOMEGAMON XE for IMS on z/OS: Planning and Configuration Guide.

Modes of operationThis section describes the VTAM, ISPF, TSO, and dedicated modes of operation.

VTAM modeIn VTAM mode, OMEGAMON for IMS is connected directly to VTAM terminals, without the intervention ofan intermediate online application such as TSO. VTAM mode allows up to 99 persons to operateOMEGAMON for IMS, each from an individual terminal, without requiring access to TSO.

In VTAM mode, you can set OMEGAMON for IMS so that the screen refreshes automatically as indedicated mode, but also responds immediately when you press Enter or any other program function key,as in TSO mode. This mode also assures the availability of OMEGAMON for IMS if TSO is experiencingproblems or is inoperable.

ISPF modeIn ISPF mode, users use ISPF to communicate with OMEGAMON for IMS through TSO. In this mode, thescreen does not refresh automatically. It refreshes when you press Enter or any other program functionkey.

can run in ISPF split screen mode; this mode supports your swapping back and forth between multiplesessions or between OMEGAMON for IMS and another ISPF application.

TSO modeIn TSO mode, OMEGAMON for IMS communicates with the TSO address space via VTM1, anIBM-supplied VTAM application. TSO mode allows up to 99 persons to operate OMEGAMON for IMS,each from an individual terminal. Because TSO use is widespread, this mode can provide many users withconvenient access to OMEGAMON for IMS. In TSO mode, the OMEGAMON for IMS screen does notrefresh automatically. It refreshes when you press Enter or any program function key.

Dedicated modeIn dedicated mode, OMEGAMON for IMS is connected to one or optionally two dedicated consoles, eachof which is a local non-SNA device. Dedicated mode offers the highest OMEGAMON for IMS availability,


because it is least affected by system problems such as a VTAM outage. In dedicated mode,OMEGAMON for IMS uses no telecommunications access methods; it communicates with the terminal viaEXCP. By operating this way, OMEGAMON for IMS can report hardware and software problems, even ifVTAM is unavailable or the MTO console is disabled.

In dedicated mode, OMEGAMON for IMS refreshes the screen automatically every five seconds withoutoperator intervention. The default five-second interval can be changed to suit your reporting requirements.See the IBM Tivoli OMEGAMON XE for IMS on z/OS: Planning and Configuration Guide for moreinformation about customizing this interval.

Specifying a user profile in ISPF, VTAM, or TSO modeBy default, your OMEGAMON for IMS session is started with the profile specified on the USER=parameter in your startup JCL or CLIST. To override the default, enter the two-character suffix that youassigned to your profile as follows:

v In ISPF mode, on the USER SUFFIX option of the ISPF logon menu.

v In VTAM mode, on the USER= startup parameter.

The following format is used for starting OMEGAMON for IMS and specifying the USER parameter:

LOGON APPLID(applid) DATA(USER=’cc’)

v In TSO mode, on the USER parameter in the CLIST.

The suffix of the current session profile displays on the INFO-line next to the product version number.Figure 28 shows that a profile named SW is in use.

Working with exceptions in VTAM, ISPF, TSO, or dedicated modeException analysis is a key factor in the logical tuning approach. It helps you determine the problems inthe system.

Exceeding exception thresholdsException analysis alerts you to system problems, by producing messages on your terminal wheneverexceptions to normal system performance occur. Your site defines normal system performance in the formof exception thresholds. Exception analysis compares IMS operating statistics to the exception values inyour current profile and automatically warns you when threshold limits are exceeded or when unexpectedproblem conditions occur. Figure 29 on page 33 is an example of an exception analysis display.

________________ KOIMENU VTM OI-II V510.SW I91C 03/25/09 9:34:13 B

Figure 28. Profile SW in use


Responding to exception messagesAn exception trips when the performance value it monitors exceeds the threshold you set or, incidentoccurs. Tripped exceptions indicate warning or critical conditions. When an exception trips, you decidewhether to change the exception threshold, gather more information to help you interpret the exceptionmessage, or take immediate action.

Setting exception thresholdsOMEGAMON for IMS includes a default set of threshold values that you can use immediately. However,you can also set new threshold values to conform to your installation performance standards. Becauseexception conditions vary in each site, you need to customize OMEGAMON for IMS to define whichexceptions should execute and to set valid thresholds. Determining your exception thresholds is acontinuing process. You need to establish system parameters for:

v Environment (CPU, I/O, working set size)

v Storage utilization (storage availability, violations)

v Task activity (response time, limit situations)

so that an exception message is generated only when a value indicates that a condition is reached acritical level and action is needed. If you set exception criteria improperly, operators might spend too muchtime reacting to exceptions that do not represent real problems.

When deciding on appropriate thresholds for your site, you might want to check some current systemvalues to determine what a normal value is for your system, and then set the threshold appropriately. Youcan test an exception through the selections on the Profile Menu (Option P on the Main Menu). Thesepanels are discussed later in this chapter.

Investigating an exceptionYou can use the following features to help you investigate exception conditions.

v By using the zooming feature, you can investigate an exception condition with the touch of a key. Youcan place your cursor on an exception and press PF11 to zoom to a Help panel that containsrecommended actions for the exception. You can also place your cursor on fields in a display such asvolume serial numbers, device names, and address space names and press PF11 to zoom to greaterdetail.

v The Automatic Screen Facility (ASF) automatically reacts when an exception trips by invokinguser-specified screen spaces and logging the command output, all without operator intervention.

________________ KOIMENU VTM OI-II V510./C I91C 03/25/09 9:36:27 B> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>> For an explanation of an exception, place the cursor on the exception> name and press PF11.

===============================================================================> Systemwide Exceptions

LXIMS OMEGAMON/IMS Exception Analysis+ DISP ########################################################################+ # OMEGAMON/IMS’s dispatching priority is lower than IMS’s #+ ########################################################################+ BQHI Fast Path available buffers for new PST use = 40 (High)+ DLTR DL/I Trace ON+ DSTR DISPATCHER Trace ON+ LKTR LOCK Trace ON+ ICHI Control Region: I/O Rate = 4.44/second (High)===============================================================================

Figure 29. Systemwide exceptions display

Chapter 5. Operating from the menu/command interface 33

v The Exception Logging Facility (XLF) automatically turns on the log to capture detailed informationabout performance exceptions when they occur. You can use this feature to ensure documentation andsubsequent correction of intermittent performance problems. See the IBM Tivoli OMEGAMON XE forIMS on z/OS: Realtime Commands Reference for a detailed explanation of ASF and XLF.

v OMEGAMON for IMS supplies a number of display panels that analyze various areas, such as IMSregions, device statistics, and memory utilization. These display panels are accessed through a set ofmenus.

Starting exception analysisThis section explains how to initiate exception analysis for all exceptions or for a limited group ofexceptions.

All exceptionsTo start exception analysis:

1. Select option E from the Main menu.

2. From the Exceptions menu, select option A to start group exception analysis or option B to displaysystemwide exceptions. When exception analysis is running, a warning message appears whenever anexception condition occurs.

When no exception conditions exist in your system, OMEGAMON for IMS displays the message

No exceptions tripped this cycle

3. You can customize this message on the Set All Clear Message panel. TypeP.F.A on the INFO-line andpress Enter.

OMEGAMON for IMS displays the Set All Clear Message panel shown in Figure 30.

Exceptions by groupOMEGAMON for IMS organizes exceptions into logically related types, which you can use to execute,display, and customize as a group. To display exception groups, you can select an option on theExceptions menu. For example, the Master Terminal Operator Exceptions panel displays the exceptionsrelated to IMS internals, and those exceptions related to DASD logging (DL group).

You can see a list of the existing exception groups at your site. From command mode (press PF12 totoggle to command mode from menu mode), type GDFN with no arguments. You can also useOMEGAMON for IMS to define your own exception groups with GDFN. For more information about usingcommand mode, see Chapter 2, “Command basics,” on page 5.

Exception analysis summary commandsYou can display exception analysis summary information in command mode (by using the XSUM andXTRP commands) or in menu mode (by using the History of All Tripped Exceptions panel). You can usethis information to help you set appropriate threshold values. For example, if an exception is tripped often,

________________ KOIMENU VTM OI-II V510./C I91C 03/25/09 9:37:15 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22===============================================================================> Set All Clear Message

> The display below shows the current message that appears when exception> analysis detects no components above their exception threshold. To change> the message, type a new one of up to 60 characters enclosed in quotes after> XTXT. To make the change permanent, be sure to save the profile.

XTXT+ '==> *** NO EXCEPTIONS TRIPPED ON THIS CYCLE *** >== '

===============================================================================

Figure 30. Set All Clear Message screen


the threshold value might be set too low. Once you fine-tune the threshold value for each exception, youcan use this information to accurately monitor your IMS system for performance problem areas.

The summary display shows whether the exceptions are on or off, the threshold settings, the ASFparameters, and trip times and values. To display the History of All Tripped Exceptions type E.D on theINFO-line of any panel and press Enter. Figure 31 represents a partial display of the History of All TrippedExceptions panel.

The Total Trips column shows the number of times the exception tripped since the session started. Theexceptions are displayed in alphabetical order.

If you use the XSUM and XTRP commands to display this information, the following keywords areavailable:

GROUP=ccYou can limit the tripped exceptions displayed to a specified exception group. Enter anytwo-character code for an IBM-supplied exception group or a user-defined group.

LIST=IEnter I to request that the exceptions are listed in order of invocation.

RESETEnter RESET to reset the last and worst trip values to zero. By resetting these values, you canchange the default thresholds to ones that meet your installation performance standards. It canalso be helpful when you want statistics on a specific job, or if you want to track exception activityin addition to cumulative activity.

Note: The XTRP command generates the summary display. The XSUM command displays allexceptions that are set, whether they trigger or not. You can include the XSUM or XTRPRESET command in a TSF screen space for automatic resetting at periodic intervals.Resetting either XSUM or XTRP resets the counters for both commands.

For more information about XSUM or XTRP, or about TSF, see the IBM Tivoli OMEGAMON XE for IMS onz/OS: Realtime Commands Reference.

________________ KOIHIST VTM OI-II V510./C I91C 03/25/09 9:38:21 B> Help PF1 Back PF3 Up PF7 Down PF8 Zoom PF11>> To have the Exception History update, remove the > preceding the XIMS> command. The XIMS command must be executed to drive exception analysis.> Exception analysis must be performed to create a history of tripped> exceptions. For an explanation of an exception, place the cursor on the> exception name and press PF11.>================================================================================> History of All Tripped Exceptions

>XIMSXTRP LIST=A

+----------+----------+-----------+--------------+-----------+----------------++ DISP Threshold Trip Value Time Occurred Total Trips Trips Since Reset+ State=On+ Last 03/25 08:40:11 5 5+ Worst 03/25 08:40:11+ Group=ST Limit=0 Persist=0 Auto=Off Log=Off+----------+----------+-----------+--------------+-----------+----------------++ DLTR Threshold Trip Value Time Occurred Total Trips Trips Since Reset+ State=On+ Last 03/25 08:40:11 5 5+ Worst 03/25 08:40:11+ Group=ST Limit=0 Persist=0 Auto=Off Log=Off+----------+----------+-----------+--------------+-----------+----------------+

Figure 31. History of all tripped exceptions


Controlling and customizing exception analysisAlthough customizing exception analysis is generally part of the installation process, OMEGAMON for IMSallows individual users to customize their sessions and to save these settings in individual profiles for laterrecall. This section provides an overview of the profile feature. For detail on individual command syntaxand additional customization options, see the IBM Tivoli OMEGAMON XE for IMS on z/OS: RealtimeCommands Reference.

You can customize exception analysis in the following ways:

v Group definition

v Exception group switches

v Exception control

v Invocation order

You can then save the settings you define in a user profile. New group settings are not saved in the userprofile. To reuse those settings in future sessions, save them in a screen space and invoke the screenspace at the start of your session. For more information, see Chapter 3, “Screen spaces,” on page 21 orsee the IBM Tivoli OMEGAMON XE for IMS on z/OS: Realtime Commands Reference.

Defining group exceptionsYou can define your own exception groups by using the GDFN command in command mode. You mightwant to supplement or change the default groupings to organize exceptions in groups that are related toyour application. You could also group highly critical exceptions that have a potentially severe impact onthe system.

Some advantages of defining exception groups are:

v Related or critical exception messages appear when you invoke exception analysis by group. They aremore visible, because they are shown at the beginning of the display.

v A summary of the last and worst occurrences of exception warnings by group displays on the History ofall Tripped Exceptions panel.

v You can set group switches by using the XGSW command to determine the invocation state of thegroup as a whole. To display the existing groups, switch to command mode and enter XGSW. You canalso define new groups or delete old ones in menu mode. See the IBM Tivoli OMEGAMON XE for IMSon z/OS: Realtime Commands Reference for more information about the XGSW command.

Setting group switchesYou can control the state of all exceptions within a specified group by using the XGSW command. Forexample, you can turn all exceptions in a group on or off at once, force a sample warning message foreach exception in a group for testing purposes, or suppress the display of messages for a group eventhough the exception switch is on (the latter option is useful for XLF and ASF).

The group switch overrides individual exception settings (unless you define a null state for the group).

You can list the existing groups or change them. To change the status of a group, add the keywords onthe XGSW panel.

Here is an example of XGSW with keywords:

XGSW GROUP=IM STATE=NDSP

The entry specifies that the IM group of exceptions is on and can be logged, but does not display on theterminal.

See the IBM Tivoli OMEGAMON XE for IMS on z/OS: Realtime Commands Reference for moreinformation about XGSW keywords.


Controlling individual exceptionsOMEGAMON for IMS provides a set of panels from which you can view the current characteristics of anexception or change the characteristics of an exception. On these panels, you can dynamically change thesettings of each keyword in the display by typing over the displayed value and pressing Enter. You canaccess these panels from the Profile menu (option P on the Main menu). Any new definitions you createcan be saved in a user profile for future sessions.

Some of the options on this panel focus attention on an exception message. For example, you can causethe terminal bell to ring, control the color in which a warning displays, and assign display attributes thathighlight the message. Figure 32 is an example of the Set Communications External Subsystem PoolExceptions panel that shows the current characteristics for the ACEA exception (option P.A.A).

Use this panel to specify five types of parameters for each exception.

DisplaySpecifies display characteristics for the exception, such as the two-character group name thatidentifies the type of exception, whether the exception is ON or OFF, and whether to activate anaudible alarm when the exception trips.

Box Specifies whether you want the warnings for this exception to be enclosed in a box. If not, specifyNOBOX. Otherwise, you can specify the box character for the box, the box color, or intensity, andattributes such as blinking, reverse video, and underlining.

ThresholdSets the exception threshold, typically numeric. You can also set display color and attributes forthe exception message if you do not request a boxed message.

Cycle

Limits OMEGAMON for IMS exception checking, which limits the use of CPU time to test highoverhead exceptions.

The EXNCYC keyword sets the frequency for checking exceptions. For example, you can chooseto have OMEGAMON for IMS check for a particular exception condition only every 5 or 10 cycles.See the .NXE immediate command in the IBM Tivoli OMEGAMON XE for IMS on z/OS: RealtimeCommands Reference for information about controlling the frequency of display.

The STOP keyword stops the checking of exceptions after they trigger the specified number oftimes. It also displays how many times an exception triggered since STOP= was reset.

________________ KOIODFB VTM OI-II V510./C I91C 03/25/09 9:42:00 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22===============================================================================> Set Communications External Subsystem Pool Exceptions

> To display the threshold of an exception, remove the > preceding XACB,> and type the exception name following LIST=.

> To change the setting for an exception, type over the current setting> and press ENTER. To make your changes permanent, you must SAVE your> OMEGAMON profile.

>XACB LIST=cccc

> The CESS exceptions are:

> ACEA Utilization > n%.> ACES IMS in selective dispatching for CESS pool.> ACEW Pool extension IWAITs > n.> ACEX Pool extension size > n.===============================================================================

Figure 32. Set Communications External Subsystem Pool Exceptions panel


The CUMULATIVE keyword is informational, indicating how many times an exception triggeredduring the session.

XLF For a description of the XLF parameters, see the exception logging facility in the IBM TivoliOMEGAMON XE for IMS on z/OS: Realtime Commands Reference.

The following keywords can be used with the XACB command shown on the previous panel:

LIST= Allows you to list the exceptions to display or modify.

GROUP=Allows you to limit the list of exceptions to those exceptions in the specified exception group.

FORCEDisplays the current value of the exception as a sample exception message.

TERSEDisplays an abbreviated, single-line status for each defined exception, showing the thresholdvalue, display color, exception state, and the state of the bell.

Figure 33 shows a TERSE keyword display:

Reordering the displayYou can display a list of the exceptions and the order in which OMEGAMON for IMS executes anddisplays them by using the LEXC command (press PF12 for command mode).

Figure 34 on page 39 shows a partial display of the exceptions in the OMEGAMON for IMS default order:

________________ KOIODFB VTM OI-II V510./C I91C 03/25/09 9:43:18 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22================================================================================

Set Communications External Subsystem Pool Exceptions

> To display the threshold of an exception, remove the > preceding XACB,> and type the exception name following LIST=.

> To change the setting for an exception, type over the current setting> and press ENTER. To make your changes permanent, you must SAVE your> OMEGAMON profile.

XACB LIST=ACEA TERSE: ACEA Threshold=60 Display=DEFAULT State=ON Bell=OFF

The CESS exceptions are:

> ACEA Utilization > n%.> ACES IMS in selective dispatching for CESS pool.> ACEW Pool extension IWAITs > n.> ACEX Pool extension size > n.================================================================================

XACB TERSE: DNRS Threshold=N/A Display=Red State=ON Bell=ON: TNRS Threshold=N/A Display=Blue State=TEST Bell=OFF: WSHI Threshold=2500 Display=Pink State=ON Bell=OFF: WSLO Threshold=300 Display=Blue State=NDSP Bell=OFF

Figure 33. TERSE keyword display


To dynamically change the order of the exceptions, type over an exception name or its number. You cansave the new definition in your user profile.

Exception analysis for IMS messagesOMEGAMON for IMS contains a facility that you can use to capture your IMS messages as exceptions.This facility is called message exception analysis.

Message exception analysis is activated from any OMEGAMON for IMS terminal with the ICNS command.To ensure that message exception analysis is activated, define the ICNS command in an initializationpanel invoked at OMEGAMON for IMS session initialization. For more information, see Chapter 3, “Screenspaces,” on page 21, the OPTN command in the IBM Tivoli OMEGAMON XE for IMS on z/OS: RealtimeCommands Reference and the IBM Tivoli OMEGAMON XE for IMS on z/OS: Planning and ConfigurationGuide.

Listing, defining, and deleting messages with menusOMEGAMON for IMS includes a group of predefined IMS messages. To view or modify this list throughthe menu system, follow these steps.

1. From the Main menu, select option P, Profile.

The Profile menu displays.

2. Select option F, Messages, from the Profile menu.

You see the Set Exception Messages menu.

3. Select option B, Messages.

Figure 35 on page 40 shows a list of IMS/MTO messages that are currently defined.

________________ KOIMENU VTM OI-II V510./C I91C 03/25/09 9:44:43 BLEXC

: INAC = 1 TCOI = 2 TCOT = 3 DISP = 4 DNRS = 5 TNRS = 6: DRDY = 7 TRDY = 8 IORC = 9 SPAH = 10 QBKH = 11 SMGH = 12: LMGH = 13 RDSH = 14 MFSH = 15 TMFH = 16 ACBH = 17 OSBL = 18: SAPW = 19 ITWH = 20 COMW = 21 SDSP = 22 CROL = 23 ARSP = 24

. . . . . .

. . . . . .

. . . . . .

Figure 34. Exceptions displayed by the LEXC command


4. Follow the instructions on the panel to define or delete messages.

Defining message exception display characteristicsTo define the display characteristics of each message exception, complete the following steps:

1. Define the messages for message exception analysis on the Specify IMS/MTO Messages for Displaypanel (option P.F.B).

2. Press PF12 to enter command mode.

3. Enter the XACB command with the message exception name that you want to display.

For example, enter:

XACB LIST=M001

Figure 36 on page 41 shows a sample of the Specify IMS/MTO Messages for Display panel.

________________ KZIMSGD VTM OI-II V510./C I91C 03/25/09 9:46:59 B> Help PF1 Back PF3 Up PF7 Down PF8 Save Profile PF22>===============================================================================> SPECIFY EXCEPTION MESSAGES> This is a list of all currently defined IMS/MTO messages (such as DFSnnn or> ICEnnn) that display under Exception Analysis.

MSGD+ M001 DFS144 OPTION = BUFSHOW+ M002 DFS236 OPTION = BUFSHOW+ M003 DFS243 OPTION = BUFFER

. . . .

. . . .

. . . .

+ M024 DFS2179 OPTION = BUFSHOW+ M025 DFS2473 OPTION = BUFSHOW+ M026 DFS2474 OPTION = BUFSHOW

> To add an IMS message, remove the > before MSGD below, and enter the specific> DFS message number.

>MSGD ADD DFSnnn

> To add an MVS message generated by an IMS region, remove the > before MSGD> below and enter the specific message number.

>MSGD ADD ICEnnn

> To delete an existing IMS/MTO message, remove the > before MSGD below, and> enter the specific DFS or MVS message number.

> MSGD DELETE DFSnnn===============================================================================

Figure 35. Display of predefined IMS/MTO messages


4. Type over the setting for the display characteristic that you want to change. For example, if you wantto cause the terminal bell to ring when this exception trips, type ON after the BELL= parameter for anaudible signal.

5. To retain your changes after the current session, be sure to save them in a user profile.

________________ KOIMENU VTM OI-II V510./C I91C 03/25/09 9:48:46 BXACB

: INAC+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=IM Display=CLR1 Log=OFF: Bell=OFF Attribute=REVERSE Limit=0 (0): BOX Parameters: CYCLE Parameters: Repeat=NO: Boxchar=’#’ ExNcyc=0 Persist=0: Boxclr=TURQUOISE Stop=0 (0) SS=: Boxattr=REVERSE Cumulative=0: TCOI+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=IM Display=CLR1 Log=OFF: Bell=OFF Attribute=NONE Limit=0 (0): BOX Parameters: CYCLE Parameters: Repeat=NO: Boxchar=NO BOX ExNcyc=0 Persist=0: Boxclr=NONE Stop=0 (0) SS=: Boxattr=NONE Cumulative=0: TCOT+ DISPLAY Parameters: THRESHOLD Parameters: XLF Parameters:: State=ON Threshold=N/A Auto=OFF: Group=IM Display=DEFAULT Log=OFF

Figure 36. Defining message exception display characteristics



Chapter 6. Customization procedures for RealtimePerformance Monitor

This chapter guide you through the customization of the Realtime Performance Monitor and assumes thatyou installed and configured OMEGAMON for IMS. See the IBM Tivoli OMEGAMON XE for IMS on z/OSPlanning and Configuration Guide for detailed configuration instructions and verifying your installation.

Reviewing profilesProfiles control the characteristics of an active session. Both the installer and the general user communitycan create and save customized profiles. Users can configure profile options according to their needs.Profile options include all thresholds that you can define in the system and the start-up profile.

This section describes the types of profiles, tells how to create an installation profile, and discusses profilesecurity.

Reviewing types of profilesThere are three types of OMEGAMON for IMS profiles:

IBM-supplied This profile contains session configuration defaults and default exceptionanalysis thresholds.

This profile permits you to easily install OMEGAMON for IMS withoutcustomization and assures that you can always initialize an OMEGAMONfor IMS session, even if there are no other profiles defined.

The IBM-supplied profile is always available; you cannot change thisprofile.

Installation-defined This profile enables the installer to define default settings that are differentfrom the IBM-supplied profile settings.

You can specify this customized profile as the default for all OMEGAMONfor IMS sessions at your installation.

This profile is optional and can exist independently of the other profiles.

User-defined This profile allows users to customize their individual OMEGAMON forIMS sessions.

This profile is optional and can exist independently of the other profiles.

Using profile suffixesEach profile has a unique two-character suffix.

The suffixes for the three types of OMEGAMON for IMS profiles are:

/C IBM-supplied profile

/I Installation-defined profile

OMEGAMON for IMS automatically assigns the suffix /I when you save an installationprofile.

cc User-defined profile-any two alphanumeric characters

Users specify the suffixes for user-defined profiles when they save profiles.


You can also use profile suffixes to specify the desired profile on the USER parameter in yourOMEGAMON for IMS startup JCL, CLIST, VTAM logon data stream, or on the USER SUFFIX option onthe ISPF logon menu. The suffix of the current session profile displays in the middle of the INFO-line, asshown in the following example:

________________ ZMENU VTM OI-II V510./I I91C 03/25/09 9:51:30 B

Determining profile search orderDuring OMEGAMON for IMS initialization, OMEGAMON for IMS always loads the IBM-supplied profile, aswell as the installation-defined profile and user-defined profiles if they exist.

To determine which profile to use, OMEGAMON for IMS checks the value on the USER parameter.

IF... THEN OMEGAMON for IMS uses...

/C is specified the IBM-supplied profile

/I is specified the installation-defined profile

If no installation profile is found, OMEGAMON for IMS defaults to /C,the IBM-supplied profile.

A user-defined (cc) profile is specified, andOMEGAMON for IMS cannot find the usermember

the /I profile

If OMEGAMON for IMS cannot find the installation profile, thenOMEGAMON for IMS defaults to /C.

Storing profile data setsIBM stores the IBM-supplied command/menu interface profile in the load library; you cannot change thisprofile. Therefore, the IBM-supplied values are always available.

OMEGAMON for IMS stores both the installation-defined profile and the user-defined profiles in the sameprofile data sets that the DD statement RKOIPFSV references (rhilev.IMSID.RKOIPFSV). Both types ofprofiles use the same naming conventions as their DD name statements.

Reviewing exception analysisException analysis is one of the most powerful features of OMEGAMON for IMS. An exception is anunusual condition or situation which might affect system availability and/or performance.

OMEGAMON for IMS includes defaults for each exception. However, because each IMS environment isdifferent, you might want to adjust some exceptions to meet the needs of your site.

This section describes how to tailor exceptions to your site. For information about how to use exceptionanalysis to improve the performance of your system, see the User’s Guide for your product.

You can use exceptions to specify

v Which system activities you want to monitor

v When you want the system to notify you about potential problems associated with the performance ofactivities

Thresholds represent levels of activity, and allow you to define acceptable and unacceptable performance.There are high and low thresholds to represent high and low activity levels. Both kinds of thresholds havewarning and critical values. If you are monitoring a threshold and you specified a warning value, a yellow


light displays when the associated activity reaches or falls to that value (depending on the threshold type,high or low). If you specified a critical value, a red light displays when the activity reaches or falls to thatvalue.

Each exception belongs to a group of related exceptions (an exception group). You can choose to monitorany of the following types:

v An entire exception group

v An individual exception

v Either the warning or the critical component of an individual threshold

Each exception maps to a light on the System Overview panel. The help for each exception groupexplains the exception light mapping.

If multiple exceptions trip at their critical thresholds, the corresponding light turns red. If multiple exceptionstrip at their warning thresholds, the corresponding light turns yellow.

Warning: You must follow the procedure in step 3 of “Creating an installation-defined profile” on page 45to customize exceptions.

Creating an installation-defined profileYou can change some or all of the IBM-supplied profile defaults to customize OMEGAMON for IMS foryour system.

Customization includes determining, selecting, and saving appropriate options and thresholds to create aninstallation-defined profile. Customization also includes specifying the installation-defined profile as thedefault for your system.

The customization options for user-defined profiles are the same as those options discussed in this sectionfor the installation-defined profile.

You must follow a three-step process to customize your profiles, as follows:

1. Establish the default options.

2. Select the appropriate session and exception analysis options.

3. Set a default startup configuration.

Step 1: Establishing default optionsTo establish default options for your installation-defined profile, run OMEGAMON for IMS with theIBM-supplied profile to become familiar with basic OMEGAMON for IMS session and exception analysisoptions. You can then determine what options your installation requires, so that you can create aninstallation-defined profile.

Step 2: Selecting session and exception analysis optionsTo display the following figure, that is, the Profile Maintenance and Session Controls Menu, select theProfile (P) option from the Main Menu.

Chapter 6. Customization procedures for Realtime Performance Monitor 45

You can specify settings through the Profile menu and use them for the current session only or you cansave them in a profile for subsequent sessions.

You can choose as many or as few of the menu options as you want to customize your profile.

Press PF1 for online help on each option or consult the IBM Tivoli OMEGAMON XE for IMS on z/OS:Realtime Commands Reference for details on individual commands.

Step 3: Setting default startup configurationThe following example shows and explains the options required to set the default startup parameters forOMEGAMON for IMS:

Set Startup Configuration options

________________ KOIOPTE VTM OI-II V510./C I91C 03/25/09 9:54:25 B> Help PF1 Back PF3 Save Profile PF22> Type a selection letter on the top line and press ENTER.================================================================================> Set Startup Configuration

_ A DISPLAY ............... Display options_ B CONTROL ............... Control function options_ C ROUTING ............... Log sysout class, destination, and printer options_ D PLOT .................. IMS plot thresholds

> Most changes you make from this menu path become permanent when you save your> profile. Press PF22 to save your profile.

================================================================================

A Select for the display options

B Select for the control function options

C Select for the log sysout class, destination, and printer options

________________ KOIPOPT VTM OI-II V510./C I91C 03/25/09 9:52:21 B> Help PF1 Exit PF3 Save Profile PF22> Type a selection letter on the top line and press ENTER.===================================================================================> PROFILE MAINTENANCE AND SESSION CONTROLS> Exceptions_ A POOLS ............... Set pool utilization and fragmentation exceptions_ B DATABASE/FAST PATH... Set database, DASD logging, and fast path exceptions_ C IMS MISC ............ Set miscellaneous IMS-related exceptions_ D OPERATING SYSTEM .... Set operating system-related exceptions_ E VSAM/STATIC ......... Set VSAM, trace, and other static exceptions_ F MESSAGES ............ Set exception messages> Configuration_ G CONFIGURE ........... Set default start-up configuration_ H SAVE/DELETE ......... Create, delete, save profiles> Quick-set Options_ I COLOR ............... set color mode and colors_ J BACKGROUND .......... Set background processing (XLF, ASF, and TSF)_ K AUTO ON ............. Set automatic updating ON_ L AUTO OFF ............ Set automatic updating OFF_ M LOGGING ............. Log on, log off, log out, log options

>> Changes you make from this menu become permanent when you save your profile.> Use PF22 to save the profile.==================================================================================

Figure 37. PROFILE MAINTENANCE AND SESSION CONTROLS Menu


D Select for the IMS plot thresholds

The following table summarizes the display, control, and routing options that you access from the SetStartup Configuration Menu. In addition, the table summarizes the IOPT command, which the installer canissue in command mode. (Press PF24 from the menu system to access command mode.)

Command function Command Description

Controls session anddisplay options

OPTN Activates and deactivates the:

v Automatic screen facility (ASF)

v Timed screen facility (TSF)

v Exception logging facility (XLF)

v Terminal bell

v Log

Controls display characteristics:

v The date (USA or EUROPEAN)

v Minor commands (UPPER or LOWER case)

v All command output (UPPER or MIXED case)

v Scroll amount (PAGE or CSR)

v The first screen when you start OMEGAMON for IMS

v The interval for the terminal bell

Important: OMEGAMON for IMS does not save the setting for theZEROS keyword in a profile.

Sets color options .SCC Allows you to set color, highlighting, and extended attribute options foreach field on the OMEGAMON for IMS display.

Sets operationalparameters

.SET Sets parameters for:

v The screen space fetch feature (.FGO)

v The interval for OMEGAMON for IMS cycles

v The number of entries in the device name table

v Guarding against loops caused by the PEEK command

v The automatic updating delay cycle

v The size of the REPORT file for logging screens

v The size of the work area for the PEEK command

Sets installation profileoptions

IOPT Controls installation options, such as:

v Issuing DASD reserves when OMEGAMON for IMS saves members inrhilev.IMSID.RKOIPCSV

v Whether OMEGAMON for IMS storage is page-fixed in memory

Sets print output options OUTP The minor command settings saved in a profile are:

COPY Specifies number of copies to print.

DDNM Specifies ddname to override standard ddname.

DEST Specifies the report destination.

DSTU Specifies the userid for a report.

FOLD Specifies whether lowercase is folded to uppercase.

FORM Specifies the name of the form on which to print.

HOLD Specifies that OMEGAMON for IMS place the output in the hold queue and retrieve theoutput from TSO.


ID1 Requests separator pages and page headers that identify output from differentOMEGAMON for IMS sessions.

ID2 Defines up to 16 characters on the left of the separator page.

ID3 Defines up to 16 characters in the center of the separator page.

ID4 Defines up to 16 characters on the right of the separator page.

LNCT Sets number of lines per page on report.

SOUT Defines the SYSOUT class of the report.

Implementing the installation-defined profileTo implement the profile, you must perform the following three steps:

1. Save the installation-defined profile.

2. Secure the installation commands.

3. Specify the default profile.

Step 1: Saving the installation-defined profileYou can change the setting of any installation-defined profile option at any time during an OMEGAMON forIMS session. OMEGAMON for IMS uses the changed setting for the duration of the current session exceptfor the IOPT command. You can use the IOPT command to effect global changes. Most of these changesdo not take effect immediately until the product is recycled. The RESERVE parameter takes effectimmediately.

To save the changed profile for future sessions, press PF22 to access the profile save screen or issue theIPRF command as follows:IPRF SAVE

OMEGAMON for IMS automatically assigns the /I suffix to profiles that you save with IPRF command.

You can also use Profile Menu Option H to save, delete, or list installation profiles.

Important: The saved profile picks up not only the settings that you changed, but all of the currentsettings for all profile-definition commands.

You can delete the installation-defined profile by issuing the IPRF command as follows:IPRF DELETE

You can save or delete individual user profiles by using the PPRF SAVE or DELETE commands.

By distinguishing between IPRF and PPRF, you can restrict access to the installation-defined profile whileallowing the general user community to customize their own profiles.

Step 2: Securing the installation commandsThe IPRF and IOPT commands that are specific to the installation-defined profile are included in theprogram as unsecured so that you can easily install and start the program.

However, if you create another installation-defined profile, you might want to protect the profile. There is noneed for users to have access to the installation-defined profile, because each user can create and save aunique profile by using the PPRF command. This user-defined profile overrides the installation-defined anddefault profiles.


To protect the installation-defined profile, you can use either the default internal security or the IMSinterface to external security packages, such as RACF® or CA-ACF2.

Step 3: Specifying the default profileIf you want the installation-defined profile to be the default profile for your site, set the USER parameter to/I in your CLIST startup procedure or VTAM logon data stream.

For ISPF mode, specify /I in the USER SUFFIX field on the ISPF invocation panel.

Implementing your BMP interfaceIBM designed the IMS Command Batch Message Processing Interface subfunction (known as the BMPinterface) supplements (instead of replaces) the Write-to-Operator with Reply (WTOR) interface. The ICMDmenu command and common interface uses the WTOR interface. You might use both the commoninterface or the WTOR interface, or use only one of them.

Using the BMP interface in addition to the WTOR interface has the following advantages:

v Reduces contention for the WTOR interface if you are using the WTOR interface to control IMS, or ifyou have other software products that use the WTOR interface

v Increases command throughput

v Provides additional features, such as:

– A user security exit, which you can use to control which users can issue which IMS commands

– An option which you can use to wait for IMS commands to complete

Note: You cannot use BMP if you are monitoring a DBCTL system.

Setting up your BMP interfaceTo set up your BMP interface, you must perform the following steps:

Step 1: Define your BMP interface to IMSTo define your BMP to IMS:

1. Run the PSBGEN utility, by using the sample JCL and instructions in rhilev.RKANSAM(KI2BPGEN).

2. Run the ACBGEN utility, using the sample JCL and instructions in rhilev.RKANSAM(KI2BAGEN).

3. Update the IMS SYSGEN to define your BMP to IMS. Sample IMS SYSGEN statements are inrhilev.RKANSAM(KI2BIGEN).

4. Update IMS security to allow the BMP to enter IMS commands. If your site uses the IMS SecurityMaintenance Utility (SMU), you can use the sample input statements in rhilev.RKANSAM(KI2BSGEN).

Step 2: Link-edit DL/I into your BMP interfaceLink-edit DL/I into your BMP, by using the sample JCL and instructions in rhilev.RKANSAM(KI2BLDLI).

Step 3: Remove the comment character from the IMS RESLIB data setRemove the comment character from the IMS RESLIB data set to include it with your OI online PROCagain.

Step 4: Optionally implement command-level securityIf your site implements OMEGAMON for IMS command-level security, you must update that security inorder to use the BMP interface. You need to give each user who is going to use the BMP interface accessto the BCMD command. Only the BMP interface uses this internal command.

Step 5: Optionally implement a security exitYou can choose to secure individual IMS commands with an external security product such as CA-ACF2or RACF. If you do so, you must write a stand-alone security exit by using the following guidelines:


v Use standard OS linkage.

Note: Register 1 at entry to the user exit points to an 8-byte user ID field, followed immediately by anLLZZ field, a slash, and an IMS command.

v Implement the following return code standard:

– To allow an IMS command, return a return code of zero.

– To disallow an IMS command, return a return code that is greater than zero.

v Name your stand-alone load module KI2BMPX1, and place it in rhilev.RKANMOD.

Important: If your security exit results in an abend, OMEGAMON for IMS turns the exit off. You muststop and restart OMEGAMON for IMS to reimplement your security exit. No IMS commandsecurity is in force between the time your security exit abends, and the time you stopOMEGAMON for IMS.

If the BMP results in an abend, IMS stops the associated PSB and transaction. The BMPcannot reATTACH until you:

1. /START the PSB.

2. /START the transaction.

3. Restart your BMP interface. For more detailed information, see Starting your BMPinterface manually

Starting and stopping your BMP interface automaticallyDuring ICAT configuration of OMEGAMON for IMS, you can specify that you want the BMP interface tostart automatically when you start OMEGAMON for IMS. See the ICAT online help for more information.

To start and stop your BMP interface automatically at the same time you start and stop your OMEGAMONfor IMS address space, use the instructions and sample EXEC card in rhilev.RKANPAR membersKOImpP00 and KI2BMPmp.

Starting your BMP interface manuallyYou can start your BMP interface manually by using the following interface command:START CBMP keyword

where keyword is any of the keywords that are listed in Table 3.

The following table lists all of the keywords and keyword values that are available for you to use with theSTART CBMP command.

Table 3. START CBMP Keywords

Keyword Possible values

PSB= The PSBNAME defined in the PSBGEN and named in the IMS SYSGEN APPLCTN statement.The default is CANDLE1.

TRAN= The transaction code you associated with the BMP in the IMS SYSGEN TRANSACT statement.The default is CANDLE1.

AGN= The optional RACF AGN associated with the BMP. No default is specified.

PROCLIM= The number of commands the BMP processes before it terminates. (The BMP reATTACHesitself when needed by a user whose profile has Automatically Attach BMP when neededON.) This keyword accepts the same values as the PROCLIM= keyword on the IMS SYSGENTRANSACT statement. The default is zero, which indicates that there is no limit on the numberof commands the BMP can process.Note: Specifying PROCLIM= on the IMS SYSGEN TRANSACT statement has no effect,because the BMP does not issue a GU (get unique) for each IMS command it processes.


Table 3. START CBMP Keywords (continued)

Keyword Possible values

ATTACH= v YES

v NO

v WAIT

v AUTO

v SUSP

v END

For more information about when to use each of these values, see Table 4.

The following table provides information to help you understand when to use the various ATTACH=keyword values.

Table 4. Understanding ATTACH= values

IF you...THEN use this ATTACH=value...

want to ATTACH the BMP during OMEGAMON for IMS initialization, YES (default)

do not want the BMP ATTACHed during OMEGAMON for IMS initialization, anddo not want the BMP to ATTACH automatically, regardless of the user profilesetting for Automatically Attach BMP when needed,

NO

do not want the BMP attached during OMEGAMON for IMS initialization, but dowant the BMP to ATTACH automatically when it is needed, regardless of the userprofile setting for Automatically Attach BMP when needed,

WAIT

want the BMP to ATTACH automatically when it is needed in accordance with theuser profile setting for Automatically Attach BMP when needed, except whenthe BMP is detached and explicitly reATTACHed with a different ATTACH= value,

AUTO

want to detach the BMP and prevent the BMP from ATTACHing automatically untilthe BMP is explicitly reATTACHed with a START CBMP command,

SUSP

want to detach the BMP, but allow the BMP to reATTACH automatically inaccordance with the ATTACH= value specified when the BMP was lastATTACHed,

END

Stopping your BMP interface manuallyYou can stop your BMP interface manually by using one of the following interface commands:

v START CBMP with ATTACH=SUSP or ATTACH=END

v STOP ID=CBMP

STOP ID=CBMP does not accept any keywords, but its effect is the same as START CBMPATTACH=END.

For more information about ATTACH= values, see Table 4.

Changing the IMS command options in your user profile

You can change the IMS command options in your user profile as follows:

1. Select the Options menu from the Action Bar of any panel.

2. Select Set IMS Options from theOptions menu.

3. You can change the following IMS command options:


Table 5. IMS command options

Submit Commands via BMP Interface

On By default, OMEGAMON for IMS submits your commands through the BMP interface wheneverpossible. If OMEGAMON for IMS cannot use the BMP interface, OMEGAMON for IMS attemptsto submit your commands by using the WTOR interface.

Off Turn this option OFF if you do not want to submit any commands by using the BMP interface.

Wait for IMS to Process Each Command

On Turn this option ON if you want to wait for each IMS command that you submit by using the BMPinterface to process. If you submit multiple commands, or if you request an action that requiresOMEGAMON for IMS to submit multiple IMS commands, it takes a maximum of 30 seconds forthe last of these commands to process.Note: After 30 seconds, the system terminates the wait; the IMS command continues toprocess.

Off By default, you do not wait for your IMS commands to process. IMS responses to yourcommands appear on the console and Operator Assist panels.

Automatically Attach BMP when needed

On Turn this option ON if you want the BMP to attach automatically when you need it (for example,if the BMP terminates itself after processing the number of commands specified on PROCLIM=).Note: The BMP cannot attach automatically if the current CBMP ATTACH= value is either NO orSUSP.

Off By default, the BMP does not attach automatically for you unless you start the BMP withATTACH=WAIT and you setSubmit Commands via BMP interface to ON. If the BMP is notcurrently

ATTACHed, and you submit commands by using the BMP interface only (Automatically UseWTOR if needed OFF), your IMS commands queue in memory until the BMP is reATTACHed.

Automatically Use WTOR if needed

On By default, OMEGAMON for IMS uses the WTOR interface as a backup interface for submittingyour IMS commands.

Off Turn this option OFF if you do not want your commands submitted using the WTOR interfaceunder any circumstances.Note: You cannot submit some IMS commands by using a BMP interface. For a list of thesecommands, see your IBM IMS Operator's Reference. If you turn this option OFF, you cannotissue any of these IMS commands. And if the BMP is not ATTACHed and cannot ATTACHautomatically, you cannot issue any IMS commands.

Note: If you are going to use the BMP facility to submit IMS commands, you must be authorized to enterthe BCMD command.

Implementing the SAP interfaceYou can customize OMEGAMON for IMS to start SAP automatically or manually. You can also check thestatus of SAP. This unit describes when and how to customize OMEGAMON for IMS to work with SAP. Italso informs you to how to start SAP, stop SAP, and check the status of SAP.

When to customize OMEGAMON for IMS for SAPUse the following chart to determine whether you want to customize OMEGAMON for IMS to use it withSAP.


Table 6. Using OMEGAMON for IMS with SAP

IF you are using... AND... THEN...

OMEGAMON for IMS SAP read the information in this unit.

are not using SAP skip this unit.

Customizing OMEGAMON for IMS to start SAP automaticallyDuring ICAT configuration of OMEGAMON for IMS, you can specify that you want SAP support to startautomatically when you start OMEGAMON for IMS. See the ICAT online help for more information.

You can also start SAP support by including the START SAP command or the EXEC KOISAPmpcommand in your automatic start member KOImpP00. The mp in KOImpP00 is the modify prefix assignedin your procedure.

Starting SAP support from the z/OS consoleComplete the following steps to start SAP support with an OMEGAMON for IMS interface command.

1. From the z/OS console, typeMODIFY interface_name, START SAP

2. Press Enter.

Result: The system displays the OSP050 SAP SUPPORT STARTED message.

Starting SAP support from OMEGAMON for IMSComplete these steps to start SAP support by using the ISAP immediate command from the OMEGAMONfor IMS command interface.

1. From the command interface, typeISAP ON

2. Press Enter.

Result: The system displays a message that SAP support is started.

Stopping SAP from the z/OS consoleComplete the following steps to stop SAP support.

1. From the z/OS console, typeMODIFY interface_name, STOP ID=SAP

2. Press Enter.

Result: The system displays a message that indicates that SAP support is stopped.

Stopping SAP support from OMEGAMON for IMSComplete these steps to stop SAP support by using the ISAP immediate command from the OMEGAMONfor IMS command interface.

1. From the OMEGAMON for IMS command interface, typeISAP OFF

2. Press Enter.

Result: The system displays a message that SAP support is stopped.

Checking the status of SAPComplete these steps to check the status of SAP support by using the ISAP immediate command from theOMEGAMON for IMS command interface.

1. From the OMEGAMON for IMS command interface, type


ISAP

2. Press Enter.

Result: The system displays the status of SAP support.

Using KOIGBL to customize workload parameters

Defining workload groups by using the KOIGBL load moduleAfter you install OMEGAMON for IMS, there are a number of items that you might want to change to suitneeds in your environment.

The OMEGAMON for IMS Realtime Performance component and the DEXAN component support yoursegregating specific workloads into groups. You can define these workload groups by using the KOIGBLload module.

You can also set defaults for parameters related to this support; for example, MAXIDS, the maximumnumber of PSB groups which you can define.

Specifying workload group definition versionsThe two-character suffix on the global data module (KOIGBL) permits you to specify which version of theworkload group definitions you want to use for a particular execution of IMS.

In this manner, the test IMS system can use a different set of PSB group definitions from those groupdefinitions of the production IMS system.

Important: Make sure that the suffix you select for the GLOBAL=mp parameter is reflected in the PARMfile members KOIVTMmp and KOIDEXmp. You edited these members previously during theinstallation process.

If you have different members, OMEGAMON for IMS executes the first member loaded.

All OMEGAMON for IMS users monitoring the same IMS system share workload definitions.The GLBL command loads a new KOIGBLmp global data module regardless of what youspecify on the GLOBAL=mp parameter in the PARM file members.

Note: The two-character suffix on the global data module is different from the two-character suffix on theuser profile.

KOIGBL defines all workload group definitionsAll OMEGAMON for IMS users monitoring the same IMS system share workload group definitions.

OMEGAMON for IMS uses the KOIGBL module the first user selects to start all subsequent OMEGAMONfor IMS users, regardless of the GLOBAL parameter these users specify on their START command.

Defining OMEGAMON for IMS workload groupsThe $OIGROUP macro defines the workload groups which OMEGAMON for IMS uses.

There are three types of $OIGROUP macros:

v $OIGROUP INITIAL

v $OIGROUP ID

v $OIGROUP FINAL


Defining targeted programs or program groups by using the KOIGBLdata setUse the rhilev.RKANSAM(KOIGBLmp) member to define workload groups that you can use to target theOMEGAMON for IMS analysis to individual programs or groups of programs.

Assembling and linking KOIGBL (Batch)After you edit the KOIGBLmp member, you must assemble it to generate a new KOIGBL load module,linking into your OMEGAMON for IMS load module data set:

Note: Use the member KI2GBLmp in rhilev.RKANSAM that contains a model of the JCL to assemble andlink a new KOIGBL24 under Batch.

1. Change the -THILEV- value to reflect what you specified for &thilev.

2. Change the -RHILEV- value to the high-level qualifier for your runtime library.

The GLOBAL=mp parameter on the START OMEGAMON for IMS statement at execution time tellsOMEGAMON for IMS which KOIGBL24 module to use. In this way, you can build up a library of differentprogram group definitions, and select among them when you invoke OMEGAMON for IMS.

You can also use the GLBL command to dynamically reload a new copy of a reassembled KOIGBL24module, or to dynamically load a KOIGBL24 module with a suffix different from the one currently in use.For more information about the GLBL command, see the IBM Tivoli OMEGAMON XE for IMS on z/OS:Realtime Commands Reference.

The same KOIGBL24 modules work with any version of z/OS or IMS. Remember, however, that yourKOIGBL24 modules require reassembly when you install a new version of OMEGAMON for IMS, becausethe thilev.TKANMAC library often changes between versions.

Modifying workload group definitions by using the KOIGBL24 macrosIBM provides macro instructions that allow you to modify the workload group definitions. Comments withinthe KOIGBL24mp describe these macros.

The macros that we provide for defining workload groups are:

v $OIGROUP INITIAL

v $OIGROUP ID

v $OIGROUP FINAL

v $OIDEXAN

The following sections discuss each macro and its parameters.

Modifying the default workload groups macros ($OIGROUP)Use the $OIGROUP macros to modify the default workload groups for Bottleneck Analysis (DEXAN).

$OIGROUP INITIAL macroThe $OIGROUP INITIAL macro is required. Define the macro only once. The INITIAL macro must precedeany other $OIGROUP macro.

Determine which format of the $OIGROUP INITIAL macro to use, as follows:

v If you are modifying workload group definitions for OMEGAMON for IMS, then the format for$OIGROUP INITIAL is...$OIGROUP INITIAL,MAXGRPS=nn, X

MAXIDS=nnnn, XMAXTERM=nnnn, XMAXNODE=nnnn


MAXGRPS Specifies the maximum number of groups. The valid range is from one to 30 groups. Youcan change this value dynamically by using the MAXG command. For more informationabout the MAXG command, see the IBM Tivoli OMEGAMON XE for IMS on z/OS:Realtime Commands Reference.

MAXIDS Specifies the maximum number of PSBs, transactions, and classes. Transactions andclasses are only valid for OMEGAMON for IMS. The valid range is from one to 1000 IDs.

MAXTERM Specifies the maximum number of logical terminal names. The valid range is from one to1000 IDs. This parameter is only valid for OMEGAMON for IMS.

MAXNODE Specifies the maximum number of VTAM node names. The valid range is from one to1000. This parameter is only valid for OMEGAMON for IMS.

Defining a group by using the $OIGROUP macroUse the $OIGROUP ID macro to specify to which group or groups the entry belongs, and optionally givethe group a name. You can also specify threshold and display characteristics with this macro.

Use the following chart to determine which format of the $OIGROUP ID macro to use.

v If you are modifying workload group definitions for OMEGAMON for IMS, then the format for$OIGROUP ID is$OIGROUP ID, item=cccccccc, X

GROUPS=(nn,.,nn) XTHRESH=(nnnn,...,nnnn) XEXPTHR=(nnnn,...,nnnn)

item Can be one of the following

PSB Code cccccccc with 1-8 characters as follows:

– Use an asterisk (*) to define generic PSB names. For example, ifyou want to include all PSB names that begin with the letters AB inPSB group 1, code the following macro:$OIGROUP ID,PSB=AB*,GROUPS=1

– To include all PSB names that contain the letters CD in the third andfourth position of the name in PSB groups 2 and 4, code thefollowing macro:$OIGROUP ID,PSB=**CD*,GROUPS=(2,4)

– To include multiple transactions in a single group, you can includemultiple $OIGROUP statements, such as:$OIGROUP ID,PSB=ABC001,GROUPS=1$OIGROUP ID,PSB=XYZ00*,GROUPS=1

TRAN Defines a transaction name (1-8 characters). You can use asterisks tospecify generic names as outlined in the PSB description. Thisparameter is only valid for OMEGAMON for IMS.

CLASS Defines transaction classes that the specified transaction groupsinclude. The valid range is from one to 255. If the number exceeds themaximum class number you specify in the IMS SYSGEN, the systemignores the maximum class number. This parameter is only valid forOMEGAMON for IMS.

TERM Defines logical terminal names. The logical terminal name is 1-8characters. As with the PSB parameter, you can use asterisks to specifygeneric names. This parameter is only valid for OMEGAMON for IMS.

NODE Specifies a VTAM node name used in collecting end-to-end responsetime data. Generic node names are not allowed. This parameter is onlyvalid for OMEGAMON for IMS.


GROUPS Specifies which group or groups include the ID. You can code the group in the formGROUPS=n or GROUPS=(nn,..,nn).

A terminal-related group can contain LTERMS or VTAM nodes, but not both.

A NODE-related group is a terminal-related group that contains VTAM nodes (NODE=parameter). Thefollowing table identifies what happens when you add a terminal name to a PSB group or transaction itemsto terminal-related groups.

Table 7. Terminal-related group actions

If you try... Then... And...

to add a terminal name (TERM= or NODE=parameter) to a PSB group, which already containsPSB-related items:

TRAN=

PSB=

CLASS=

an error message is issued the request is ignored.

to add a transaction item to a terminal-related group,which contains only logical terminals or contains onlyVTAM nodes:

TERM=parameter

NODE=paramete

an error message is issued the request is ignored.r

Specifying RTA thresholds by using the $OIGROUP ID macroSpecify the following three additional parameters to define thresholds for RTA displays:

v FIX=

v THRESH=

v EXPTHR=

RTA is valid only for OMEGAMON for IMS.

FIX Provides information for the RTA display command, GRSP. The GRSP commandgraphically displays the response time history for workload groups or group items (such astransaction or PSB names). If you define these groups or items as FIXed, GRSP alwaysdisplays them. If you do not define the groups as FIXed, GRSP displays the groups onlywhen they exceed a response time threshold. The THRESH parameter defines thisthreshold.

The format of the FIX parameter is as follows:FIX=(YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO)

orFIX=(YES|NO,ALL)

RTA reports information about six components of transaction response time. Thesecomponents are as follows:

1. Input queue time

2. Program input queue time

3. Processing time

4. Output queue time

5. Response time 0 (sum of input queue and processing time)

6. Response time 1 (sum of input queue, processing, and output queue time)


For more information about RTA, see the OMEGAMON XE for IMS on z/OS: RealtimeCommands Reference.

Because RTA reports on six different components of transaction response time, the FIX=parameter allows a different display setting for each of the components.

In the first format example, enter values of either YES (always display this item) or NO(display this item only when it exceeds the response time threshold) for each of the sixresponse types.

To have the same display setting for all six response type components, enter the latterformat example. For example, by coding FIX=(YES,ALL), you define the item as FIXeddisplay for all six of the response time components.

If you code the value FIX=(NO,NO,YES,NO,NO,YES), you define the item as FIXeddisplay only for the processing and response time 1 components. The default is(FIX=NO,ALL).

THRESH Provides response time threshold values for the RTA command GRSP. The thresholdvalues are specified as integers but are interpreted in tenths of a second or in milliseconds(depending on UNITS parameter in $OIGROUP macro) and the valid range is from one to9999. You can change the $OIGROUP macro UNITS parameter to get millisecondprecision for the GRSP display and the ARSP exception. UNITS=SECONDS is the default(no change to GRSP and ARSP precision). If you specify UNITS=MILLIS you getmilliseconds precision for both.

The format of the THRESH parameter is as follows:THRESH=(9999,9999,9999,9999,9999,9999)

orTHRESH=(9999,ALL)

You can enter different threshold values for each of the six response time components, oruse the second format to set the same threshold value for all six of the precedingcomponents. For example, coding the value THRESH=(5,ALL) results in a 0.5 secondthreshold value for all six response time components.

EXPTHR Provides critical response time threshold values for the average response time (ARSP)exception analysis as the IBM Tivoli OMEGAMON XE for IMS on z/OS: RealtimeCommands Reference, describes. The threshold values are in tenths of a second or inmilliseconds (depending on UNITS parameter in $OIGROUP macro) and the valid range isfrom one to 9999. You can change the $OIGROUP macro UNITS parameter to getmillisecond precision for the GRSP display and the ARSP exception. UNITS=SECONDS isthe default (no change to GRSP and ARSP precision). If you specify UNITS=MILLIS youget milliseconds precision for both. When a group or group item exceeds the EXPTHRresponse time threshold, exception analysis displays a warning message.

The format of the EXPTHR parameter is as follows:EXPTHR=(9999,9999,9999,9999,9999,9999)

orEXPTHR=(9999,ALL)

You can enter different threshold values for each of the six response time components, oruse the second format to set the same threshold value for all six components. Forexample, coding EXPTHR=(5,ALL), results in a 0.5 second threshold value for all sixresponse time components.

Use the format described in Figure 38 to define a group, give the group a name, and toset RTA display values.


Format of $OIGROUP ID to Name a Group and/or Specify RTA Values

GRP Identifies a group number, for which you assign a group name(NAME parameter).

NAME Assigns a group name to the group you specify in GRP. This valuecan include blanks, but you must enclose the value in singlequotes.

FIX Works the same way as the FIX parameter for definingtransaction, node, or terminal group items. See that FIXdescription under “Specifying RTA thresholds by using the$OIGROUP ID macro” on page 57.

THRESH Works the same way as the THRESH parameter for definingtransaction, node, or terminal group items. (See that THRESHdescription under “Specifying RTA thresholds by using the$OIGROUP ID macro” on page 57.

EXPTHR Works the same way as the EXPTHR parameter for definingtransaction, node, or terminal group items. (See that EXPTHRdescription under“Specifying RTA thresholds by using the$OIGROUP ID macro” on page 57.

You can change all of the group definitions via the SETG command. See the OMEGAMON XE for IMS onz/OS: Realtime Commands Reference for more information about SETG.

You can change the RTA response time thresholds via the ISET command. See the OMEGAMON XE forIMS on z/OS: Realtime Commands Reference for more information about ISET.

$OIGROUP FINAL macroOMEGAMON for IMS requires the $OIGROUP FINAL macro and it must be the last $OIGROUP macro.This macro indicates the end of all the KOIGBL24mp group definition macros.

The $OIGROUP FINAL macro sorts the ID entries in alphabetical order and prints a KOIGBL24mp groupsummary list. The format of the macro is as follows:$OIGROUP FINAL

Modifying the default Bottleneck Analysis parameters ($OIDEXAN)Use the $OIDEXAN macro to specify options that control the information that OMEGAMON for IMScollects and displays. By using the $OIDEXAN macro, you can also permanently change the BottleneckAnalysis options.

The format of the $OIDEXAN macro is:$OIDEXAN DBSW=ON/OFF, XCLRL=nnn, XCLRS=nn, XSTIM=nn, XTHRS=nn, XMTHR=nnnn, X

$OIGROUP ID,GRP=nn, XNAME=cccccccc, XFIX=ccc, XTHRESH=ccc, XEXPTHR=cccc

Figure 38. Format of $OIGROUP ID to Name a Group and/or Specify RTA Values


SCAL=nnn XBMPX=OFF, XNMSX=ON X

The $OIDEXAN macro and its parameters are all optional.

Bottleneck Analysis uses the default values in the following table if you do not supply an overriding valueby using the $OIDEXAN macro. In addition, you can change the various Bottleneck Analysis collectorcontrol commands to dynamically change the option values the $OIDEXAN macro sets. See the IBM TivoliOMEGAMON XE for IMS on z/OS: Bottleneck Analysis Reference for more information.

The following list shows the default value for each parameter in the $OIDEXAN macro.

DBSW=ON I/O activity recorded by individual database name.

CLRL=30 Long-term interval counters cleared every 30 minutes.

CLRS=5 Short-term interval counters cleared every 5 minutes.

STIM=5 Collector samples once every .5 seconds.

THRS=0 PDEX minimum display threshold is 0 percent.

MTHR=0 MDEX minimum display threshold is 0.

SCAL=1 MDEX display scale factor.

BMPX=OFF Collect data for BMP regions, but only if they are message-driven BMPs.

NMSX=ON Exclude non-message driven BMP regions from Bottleneck Analysis data collection.

For a further description of each option parameter, see the IBM Tivoli OMEGAMON XE for IMS on z/OS:Bottleneck Analysis Reference.

Concatenating screen space and profile data setsThe standard screen spaces that are used in the menu and command interfaces, and referenced by theRKOIPROC DD statement are stored in the rhilev.RKOIPROC data set.

To create, modify, or delete screen spaces for your use without modifying either the standard screens orscreens of other users, create one or more additional data sets called cccccccc.RKOIPCSV. The prefixcccccccc can be for your site or for an individual user.

OMEGAMON for IMS writes the members you change to the data set that the DD statement RKOIPCSVreferences.

Saving and reading screen space data sets exampleOMEGAMON for IMS accesses the data sets in the following order:

v Personal data sets in cccccccc.RKOIPCSV

v Installation

v rhilev.IMSID.RKOIPCSV

v rhilev.RKOIPROC

The following example shows how OMEGAMON for IMS saves and reads the screen space data sets:

OMEGAMON for IMS saves screen spaces in this file://RKOIPCSV DD DISP=SHR,DSNAME=cccccccc.RKOIPCSV.OMEGAMON for IMS reads screen spaces from these files://RKOIPROC DD DISP=SHR,DSNAME=cccccccc.RKOIPCSV.// DD DISP=SHR,DSNAME=rhilev.RKOIPROC.


To allow general users the freedom to use their own personal profiles, or to restrict users toinstallation-defined parameters, concatenate profile data sets as shown.

Restricting parameter modificationTo restrict users from changing selected parameters, but allow them to customize others, you canimplement the security facility for the desired commands and then concatenate the RKOIPROF DDstatement in the following manner:

Individual profiles are saved in this file:

//RKOIPFSV DD DISP=SHR,DSN=userid.RKOIPFSV

Installation profiles are saved in this file:

//RKOIPFSV DD DISP=SHR,DSN=rhiliev.INSID.RKOIPFSVProfiles are read from this file:

//RKOIPROF DD DISP=SHR,DSN=userid.RKOIPFSV

The IBM default profile is a load module in your STEPLIB, so it is always available if you do not load anyother profile.



Appendix A. IPL Elimination utility

IBM Software Support provides fixes that occasionally require that you run an IPL (initial program load)procedure on a z/OS system to successfully apply the maintenance. To eliminate delays in applying themaintenance due to this requirement, run the KIPWIPER utility. This appendix lists the tasks that the utilityperforms, describes its parameters, and provides sample JCL (job control language) instruction and eventlogs.

Running the KIPWIPER utilityBy running the KIPWIPER utility, the following tasks are performed:

1. Determine if any OMEGAMON 3270 monitoring tasks are active, and terminating them if requested.

2. Discover all active IMS systems.

3. Release common storage that relates to IMS console messages.

4. Release common storage that relates to z/OS console messages.

5. Provide a log (SYSPRINT) of all activity performed.

ParametersThe KIPWIPER utility operates in one of two modes: REPORT and CLEAN. The REPORT option providesa non-invasive method for determining all active OMEGAMON 3270 monitoring sessions. The CLEANoption, with the FORCE parameter specified, provides a method for removing OMEGAMON artifacts frommemory and for releasing any common storage.

The parameters are:

v REPORT – This option directs the KIPWIPER utility to report any active OMEGAMON 3270 monitoringtasks and IMS systems. All information is written to the activity log (SYSPRINT). The parameter ismutually exclusive of CLEAN and FORCE.

v CLEAN – This option directs the KIPWIPER utility to release all common storage in use by theOMEGAMON program because some common storage remains even after the OMEGAMON programterminated. This option first discovers all active OMEGAMON 3270 monitoring tasks and issues a z/OSSTOP (P) command for each OMEGAMON 3270 monitoring task. The utility waits up to 5 minutes toensure that all OMEGAMON tasks terminate. If any OMEGAMON tasks are still active after 5 minutes,the KIPWIPER utility terminates the tasks with a return code of 8 (RC=8).

v FORCE – This option can either be specified alone or with CLEAN option. The FORCE option operatesin the same way as the CLEAN option, but includes an additional function. In the case where anOMEGAMON task does not terminate within 5 minutes, the FORCE option issues a z/OS cancel on theOMEGAMON task. Exercise caution with this option; the primary reason for the OMEGAMON task notterminating within this period is that the OMEGAMON task is actively monitoring an IMS application in aDL/I call. Canceling the OMEGAMON task can cause IMS to terminate as well.

v DEBUG – This option logs activity for IBM Software Support. Use this option only when directed by IBMSoftware Support personnel.

Sample JCL instructionThe following sample JCL instruction (see Figure 39 on page 64) is provided in member KIPWIPER in thertehilev.TKANSAM library:


Note: Replace the RTEHLEV member with your runtime environment high-level qualifier. All activity islogged and written to the SYSPRINT DD statement.

KIPWIPER logAll activity from the the KIPWIPER utility is written to the SYSPRINT output file. Figure 40 depicts asample log (with line numbers) where OMEGAMON tasks for IMS systems are active and commonstorage is released.

Description of log events:

Lines 1 - 4KIPWIPER header and parameters selected for this run.

Lines 5 - 7An OMEGAMON 3270 monitoring task (PLOIIP17) was identified and a z/OS stop command wasissued. The utility waited for 5 seconds before checking the status of the task. When the utilitybecame active after a 5-second interval, the OMEGAMON 3270 monitoring task (PLOIIP17) wasfound to have terminated normally.

Line 8 The OMEGAMON for IMS Global work area (GWHA) is released from common storage.

//KIPWIPER JOB ()//*//* THIS IS THE SAMPLE JCL TO EXECUTE THE KIPWIPER PROGRAM.//*//* THIS PROGRAM WILL REMOVE OMEGAMON ARTIFACTS FROM COMMON//* STORAGE (PARM=CLEAN) OR REPORT ON ACTIVE OMEGAMON//* 3270 MONITORING TASKS (PARM=REPORT).//*//* THE FOLLOWING PARAMETERS MAY BE SPECIFIED://*//* REPORT - GENERATES A REPORT OF ACTIVE OMEGAMON 3270 MONITORING//* TASKS. MUTUALLY EXCLUSIVE WITH CLEAN/FORCE PARAMETERS.//*//*//* CLEAN - STOPS ACTIVE OMEGAMON 3270 MONITORING TASKS VIA THE//* Z/OS STOP (P) COMMAND. WAITS FOR ALL OMEGAMONS TO//* TERMINATE AND THEN REMOVES RESIDUAL OMEGAMON ARTIFACTS//* FROM COMMON STORAGE.//*//* FORCE - OPERATES THE SAME AS CLEAN AND MAY BE SPECIFIED WITH//* CLEAN OR BY ITSELF. THIS OPTION WILL WAIT FOR OMEGAMONS//* TO TERMINATE AND WILL CANCEL THE TASKS IF OVER 5 MINS.//* RESIDUAL OMEGAMON ARTIFACTS WILL THEN BE REMOVED FROM//* COMMON STORAGE.//*//KIPWIPER EXEC PGM=KIPWIPER,REGION=0M,PARM=’CLEAN’//STEPLIB DD DISP=SHR,DSN=RTEHLEV.TKANMOD//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*

Figure 39. KIPWIPER job

1. OMEGAMON/XE for IMS on z/OS Wiper Utility Date:2010.039 Time:19:02:182.3.4. The following option(s) are enabled: CLEAN with FORCE5. Stopping OMEGAMON 3270 monitoring task: PLOIIP176. Waiting 5 seconds for 3270 monitoring shutdown7. OMEGAMON 3270 monitoring task now stopped: PLOIIP178. GWHA of length=004096, freed9. MTO hook has been removed from IMSID=IMSK10. MTO SSCT of length=004096, freed

Figure 40. Sample log where OMEGAMON tasks for IMS systems are active


Lines 9 - 10The OMEGAMON for IMS on z/OS console hook is removed from IMSID IMSK and is releasedfrom common storage.

Figure 41 depicts a sample log (with line numbers) where no OMEGAMON tasks for IMS systems areactive.

Description of log events:

Lines 1 - 4KIPWIPER header and parameters selected for this run.

Line 5 No OMEGAMON 3270 monitoring tasks were active.

Line 6 The OMEGAMON for IMS global work area (GWHA) was not found in common storage. EitherOMEGAMON was never active or the KIPWIPER utility was executed and freed the storage beforethis run.

Line 7 No IMS systems were active, indicating the MTO hook is not active. Either an OMEGAMON taskwas never active or the KIPWIPER utility was executed and freed the storage before this run.

1. OMEGAMON/XE for IMS on z/OS Wiper Utility Date:2010.039 Time:18:59:182.3.4. The following option(s) are enabled: CLEAN with FORCE5. No OMEGAMON for IMS tasks active6. GWHA SSCT not found, SSCT chain is clean7. No IMS systems are active at this time

8.MTO SSCT not found, SSCT chain is clean

Figure 41. Sample log where no OMEGAMON tasks for IMS systems are active

Appendix A. IPL Elimination utility 65


Appendix B. Startup operation and interface commands

The OMEGAMON for IMS product interface is a set of z/OS console commands and associated displaysthat you can use to communicate with or control various tasks in OMEGAMON for IMS.

During normal operation, the interface is transparent. When you start your system, the system defaults totake all necessary actions automatically.

This appendix acquaints you with the functions and facilities of the product interface, including:

v OMEGAMON for IMS startup operation of the interface

v Commands to the interface

Startup operationThe startup parameters to KOIIA00 (the product interface) determine how the interface runs and whichIMS system the interface monitors based on the IMSID.

When you start OMEGAMON for IMS, it checks the dispatching priority to ensure that priority of theOMEGAMON for IMS is higher than the priority of the IMS. If it is not, OMEGAMON for IMS issues awarning message to the console.

Note: DEXAN values might be inaccurate when OMEGAMON for IMS is not as prioritized as IMS.

Interface z/OS IDsThe product interface has two z/OS IDs:

v Stepname

v Internal ID

Important: These two z/OS IDs cannot be the same.

The task name is used as the stepname unless you override it.

The z/OS console operator can address the stepname z/OS ID and issue z/OS STOP and MODIFYcommands. These commands terminate the OMEGAMON for IMS address space.

The internal ID, which the interface uses to communicate with the OMEGAMON, DEXAN, and EPILOGcomponents, accepts only z/OS MODIFY commands from an z/OS operator. The interface does not acceptz/OS STOP commands.

Note: The security routines might restrict the z/OS Modify command. Contact your security administratorfor assistance.

Creating an internal z/OS IDTo create an internal ID for itself, the product interface prefixes two characters to the IMSID of the IMSsystem it is monitoring.

The product interface notifies z/OS that it accepts z/OS MODIFY commands addressed to that ID. Thedefault prefix is M0.

Use the MPREFIX= parameter to specify the prefix in the M0 startup JCL. When OMEGAMON for IMSinitializes, it displays the following message on the z/OS console:OIB425i MODIFY ID ASSIGND 15: M0IMSA


For example, if you run the IMS control region with an IMSID of IMSA, the interface asks z/OS to pass itall z/OS MODIFY commands you enter for ID M0IMSA.

The interface processes only z/OS MODIFY commands; the interface rejects z/OS STOP commands forthe internal ID with an error message.

Starting the interfaceWhen the interface starts, it first executes a series of commands automatically. These commands are inmember KOIM0P00. in the rhilev.RKANPAR library. KOIM0P00. is the default.

Note: IBM supplies a default series of commands with OMEGAMON for IMS. You can tailor thesecommands for your installation.

For the interface to operate automatically, the interface issues its first command to execute the defaultstartup member, KOIM0P00., for example:EXEC KOIM0P00.

The startup member processes automatically only at initial region startup.

After the interface performs all actions that KOIM0P00. defines, you can issue more interface commandsby using the special internal ID of the interface and the z/OS MODIFY command.

Example using the MODIFY commandHere is an example of a MODIFY command with an IMSID of IMSA and the default prefix:MODIFY M0imsa,START SESSION,UNIT=560

This command starts a dedicated session.

Showing identifiers for the IBM monitor jobWhen you start the interface, the system command D A,L displays a line that shows identifiers for the IBMmonitor job and internal MODIFY ID that the interface uses.

Displaying identifiers for an interface started as a started taskIf you start the interface as a started task, modify the STEPname to produce a unique z/OS MODIFY ID(for example, IMSMON) as follows:START OMIMS.IMSMON

Now D A,L shows the following output:JOBname STEPname PROCSTEPname------- -------- ------------OMIMS IMSMON IMSPROD NSW SOMIMS M0IMSA IMSMON NSW S

In this case, the interface MODIFY ID is M0IMSA and the z/OS MODIFY ID is IMSMON. The second lineis the internal MODIFY ID that the interface builds.

Displaying identifiers for an interface started as a batch jobSuppose you start the interface as a batch job, with an IMSID of IMSA and JOBname MONIMS. Thedisplay active command (D A,L) shows the following output:JOBname STEPname PROCSTEPname------- -------- ------------MONIMS IMS IMSPROD NSW JM0IMSA M0IMSA IMSMON NSW J


In this case, the z/OS modify ID is MONIMS, and the interface MODIFY ID is M0IMSA. The second line isthe internal MODIFY ID that the interface builds.

In this started task example, you can terminate the interface with any of the following MODIFY or STOPcommands.STOP MONIMSP MONIMSMODIFY MONIMS,STOPF MONIMS,STOP

Interface commandsThe interface supports the following commands:

Interface command Action

* Comment

DISPLAY Displays active interface subtasks

EXEC Executes the interface commands in a member

HELP Displays help for interface commands

IF Conditionally processes an EXEC, START, or STOP command

LIST Displays active interface subtasks

LOG Sends a message to the z/OS console

MODIFY MERGE Starts VSAM message logging

P Stops an interface subtask

S Starts an interface subtask

START Starts an interface subtask

STOP Stops an interface subtask

The MODIFY command and the MODIFY ID must precede all commands from the console.

The commands in the EXEC members can start in any column if the command word completes beforecolumn 72. To continue a command, place any character in column 72.

The following sections describe the interface commands and their parameters.

Appendix B. Startup operation and interface commands 69

COMMENT

PurposeThe COMMENT command places comments in the members of the thilev.TKANPAR library. The interfaceignores these comments.

FormatThe format is*<comment>

A non-blank character in column 72 indicates a continuation of the comment.

ExamplesThe following example shows a sample comment line in an EXEC member.* THIS COMMENT CAN SAY ANYTHING YOU WISH.


DISPLAY

PurposeThe DISPLAY command displays the program name and internal ID of all tasks that are currently active.

Use the ID shown with the STOP command to stop an active task (see “STOP” on page 82).

FormatThe format isF M0IMSA,DISPLAY

SynonymLIST is a synonym for DISPLAY.

Example OutputThe example output from the DISPLAY command is shown as follows.

OIR043: OMEGAMON - THE FOLLOWING TASK IDS ARE ACTIVE:OIR044 ID=OMU448 PROGRAM=KOIOICROIR044 ID=CTDOI PROGRAM=KOBVTAMOIR047 VTAM APPLID=CTDOIOIR048 SLU=R08A03OIR048 SLU=L566OIR044 ID=DX PROGRAM=KOIDXCROIR044 ID=MR PROGRAM=KOIMRAR

IMS task IDs and DISPLAYOMEGAMON for IMS builds each task with a unique ID.

The OMEGAMON for IMS sessions that run under OMEGAMON for IMS VTAM support do not have aseparate ID; the OMEGAMON for IMS VTAM support ID controls all of the sessions.

OMEGAMON for IMS in dedicated mode has the task ID of OMUcuu where cuu is the dedicated terminaladdress.

The task ID of the DEXAN component collector is DX.

When OMEGAMON for IMS VTAM support is active, the interface DISPLAY command shows its VTAMapplication ID and the secondary logical unit (SLU) names of all active tasks that use it.

You cannot use SLU names to terminate individual sessions by using interface commands. You might,however, use them in VTAM commands you issue from an z/OS console to stop an active session. See“STOP” on page 82.


EXEC

PurposeThe EXEC command processes a member in either the rhilev.RKANPAR or the thilev.TKANPAR librarythat contains a predefined set of commands.

You can enter this command by using MODIFY or as a command in an EXEC member to process anotherpredefined set of commands.

FormatThe format isEXEC member_name

ExamplesThese examples all assume that the internal modify ID is M0IMSA.

If you enter this command at the console:F MOIMSA,EXEC member_a

and if member_a contains these commands:START SESSION,UNIT=53E,...EXEC member_bSTART DEXAN,GLOBAL=mp

and member_b contains these commands:LOG *** OM/IMS VTAM interface START - APPLID=CTDOI ***START cccccccc,APPLID=cccccccc,UMAX=05

where cccccccc is the logon applid for OMEGAMON for IMS to VTAM that you specified by using ICAT.

The effect of the EXEC member_a is the same as if you entered the following commands at the console:F M0IMSA,START SESSION,UNIT=53E,...F M0IMSA,LOG *** OM/IMS VTAM interface START - APPLID=ccccccccF M0IMSA,START cccccccc,APPLID=cccccccc,UMAX=05F M0IMSA,START DEXAN,GLOBAL=mp

where ccccccc is the logon applid for OMEGAMON for IMS to VTAM that you specified by using ICAT.

LimitationsYou cannot nest EXEC commands more than 10 deep at any one command invocation. EXEC loopswhere A EXECs B and B EXECs A.

EXEC members area procedureYou can think of these members as a JCL procedure or as a TSO CLIST.

The EXEC member might contain any interface command, including another EXEC command.

When an EXEC member executes another EXEC command, the called EXEC command is executed inlineas if its statements replace the EXEC statement. The called EXEC command is treated like an INCLUDEstatement in other programming languages.


HELP

PurposeThe HELP command

v Displays the commands the interface supports

v Finds information about a specific command, typed as an operand.

FormatThe format isHELP <command-name>

ExamplesThis example assumes that the internal modify ID is M0IMSA.

Type the following command to display help about all of the available interface commands.F M0IMSA,HELP

The result of this command looks similar to the following figure.

LOG 'HELP' CommandSyntax: HELP <command-name>

Description: The 'HELP' command is used to display the help information available on the commands that are usedto control the OMEGAMON for IMS interface.

HELP is available for all the commands below:

* - Comment (ignored by the interface)EXEC - Execute the commands in the member specifiedDISPLAY - Display active interface subtasksHELP - Displays help for all or specific interface

commandsLIST - Alias of DISPLAY - Display active interface

subtasksLOG - Send a message to the MVS ConsoleSTART - Start an interface Subtask (for example, OMEGAMON II)STOP - Stop an interface Subtask

Follow HELP with the name of a command to obtain information about that command.

If you do not specify a command name or if OMEGAMON for IMS does not recognize the command nameyou specify, then the help text for HELP appears at the console.


IF

PurposeThe IF command conditionally processes the EXEC, START, or STOP command that follows it on thesame command input.

IF is especially useful when you want to use the same members of the rhilev.RKANPAR library to controlcopies of OMEGAMON for IMS that run with different IMS systems. You can reduce the maintenance effortin certain environments.

FormatThe format is as follows:

IF <IMSID=cccc> Then <EXEC ...><SMFID=cccc> <P ...><CPUID=cccccccccccc> <S ...><IMSTYPE=ccc> <START ...>

<STOP ...>

Test values and their descriptionsThe IF keyword permits you to test several different values to determine whether the command thatfollows its THEN keyword executes.

The following table shows the various IF test values that you can specify.

Table 8. IF parameter values

Parameter Value Description

CPUID cccccccccccc The 12-character hardware CPUID of the machine. (See the title line on thefirst page of a dump.)

cccccc The 6-character hardware CPU serial number of the machine. It is availablefrom the RMF™ CPU report.

For a multiprocessor, OMEGAMON for IMS compares the CPUID with allthose within the multiprocessing complex.

IMSID cccc IMS ID of the IMS or DBCTL system you are measuring.

SMFID cccc SMF ID of the z/OS system you are executing upon. This information is inSYS1.PARMLIB(SMFPRMnn).

IMSTYPE CTL

DBC

Determines the set of interface commands that are executed, depending onwhether the IMS environment is a DB/DC (CTL) or a DBCTL (DBC)environment.

If the test is successful, OMEGAMON for IMS issues the normal messages for the conditionally processedcommand. If the test fails because of an invalid value in the command, OMEGAMON for IMS issues amessage that indicates this outcome.

The IF keyword supports your testing several different values to determine whether the command thatfollows its THEN keyword executes.

OutputThe output of the IF command depends upon the success of its tests.


LIST

PurposeThe LIST command displays the program name and internal ID of each currently active task. The LISTcommand is an alternate name for the DISPLAY command. For a description of the DISPLAY command,see “DISPLAY” on page 71.

FormatThe format of the LIST command is:F M0IMSA,LIST


LOG

PurposeThe LOG command displays a message at the system console.

Use this command in your EXEC members to indicate what commands you process in that member.

FormatThe format isLOG OMEGAMON sends this message to the system console

Example 1You can use log messages to display the name of the currently processing member, such as:LOG *** Processing KOIM0P00. ***

Example 2Another typical use is to indicate the start of a task such as the Bottleneck Analysis (DEXAN) collector. Forexample:LOG *** Starting DEXAN ***

OutputThe output from the LOG command looks exactly like its input.


MODIFY MERGE

PurposeThe MODIFY MERGE command merges and chronologically sorts a copy of IMS messages that go to thez/OS console and to the Master Terminal Operator (MTO) console.

The command writes the messages to a VSAM data set.

FormatThe format isF M0IMSA, MODIFY MERGE DSN='rhilev',ARCH=prefix

where:

Variable Definition

ims The imsid that the system monitors.

’rhilev’ The high-level qualifier of the VSAM data set to which messages are logged.

This high-level qualifier might be different from the high-level qualifier for otherOMEGAMON for IMS data sets.

prefix The prefix of the archive job to copy a full VSAM data set to a backup data set.

OMEGAMON for IMS appends 1 or 2 to the job name specified.

It uses prefix1 to archive rhilev.ims.LOG1, and prefix2 to archive rhilev.ims.LOG2.KI2ARCH is the default name for prefix.

If you use a different name, it must not exceed 7 characters.

This syntax assumes that M0IMSA is the internal modify ID.

How MODIFY MERGE worksThe MERGE task sets up a pair of VSAM data sets (rhilev.ims.LOG1 and rhilev.ims.LOG2) for logging.When one of the data sets fills, OMEGAMON for IMS automatically switches to the second data set, andarchives and reinitializes the first data set.

Another way to execute MODIFY MERGEYou can also execute MODIFY MERGE by entering the EXEC KI2VSMmp interface command, becausethe KI2VSMmp member contains the MODIFY MERGE command.


START

PurposeThe START command starts the following tasks under the interface:

v Response time analysis (RTA) component

v RTA data collector

v Display controller session

v DEXAN collector

v OMEGAMON for IMS VTAM support

v EPILOG collector

v SAP support

v TRF support

v ATF support

Description Format of the START command

Start Response Time Analysis(RTA)

START RTA <,IRTA=ON><,CMPAT=YES/NO>

Start the RTA data collector START DATACOL <,BUFNO=nnn><,CMPAT=YES/NO>

Start the DEXAN for IMScollector

START DEXAN <,GLOBAL=mp><,IDEG=BEGN>

Start dedicated controllersession

START SESSION ,COLS=nnn><,DIR=cccc><,GLOBAL=cc><,LROWS=nnn><,MODE=cc><,ROWS=nn><,SYS=cccc><,UNIT=cuu><,USER=cc>

Start VTAM support START ccccccccc ,COLS=nnn><,GLOBAL=cc><,LROWS=nnn><,ROWS=nn><,SYS=cccc><,USER=cc><,APPL=ccccccccc><,AUP=YES/NO><,PRTCT=ccccccccc><,PSWD=ccccccccc><,UMAX=nn><,DATA=nn><,TIMOUT=NN>

Start SAP support START SAP

Start TRF support START ITR ,ITRF=ON|OFF><,BMP=ON|OFF><,DB2=ON|OFF><,DBSUM=ON|OFF><,DL1=ON|OFF><,FP=ON|OFF><,LOGS=IMS|SMF><,RECID=nnn>


Description Format of the START command

Start ATF support START ATF ,ATFACT=ON|OFF><,AUTORESTART=YES|NO><,BUFFSIZE=nnnnn><,ECSAMAX=nnnnn><,SANDBOX=ON|OFF><,TOTTRANS=nnnnnnnn><,TRACE=DETAIL|EXCEPTION|ALL>

FormatThe formats are as follows.

START RTA <,IRTA=ON> (start RTA)<,CMPAT=YES|NO>

- or -START DATACOL <,BUFNO=nnn> (start RTA data collector)

<,CMPAT=YES|NO>- or -START DEXAN <,GLOBAL=mp> (start the DEXAN for IMS collector)

<,IDEG=BEGN>

- or -START SESSION <,COLS=nnn> (start dedicated controller session)

<,DIR=cccc><,GLOBAL=cc><,LROWS=nnn><,MODE=cc><,ROWS=nn><,SYS=cccc><,UNIT=cuu><,USER=cc>

- or -START cccccccc <,COLS=nnn> (start OMEGAMON for IMS VTAM support)

<,GLOBAL=cc><,LROWS=nnn><,ROWS=nn><,SYS=cccc><,USER=cc><,APPL=cccccccc><,AUP=YES/NO><,PRTCT=cccccccc><,PSWD=cccccccc>

<,UMAX=nn><,DATA=nn><,TIMEOUT=NN>

- or -START SAP (start SAP support)- or -START ITR <,ITRF=ON|OFF> (start TRF support)

<,BMP=ON|OFF><,DB2=ON|OFF><,DBSUM=ON|OFF><,DL1=ON|OFF><,FP=ON|OFF><,LOGS=IMS|SMF><,RECID=nnn>

- or -START ATF <,ATFACT=ON|OFF> (start ATF support)

<,AUTORESTART=YES|NO<,BUFFSIZE=nnnnn><,ECSAMAX=nnnnn><,SANDBOX=ON|OFF><,TOTTRANS=nnnnnnnn><,TRACE=DETAIL|EXCEPTION|ALL>


START command parametersThe figure uses the following notation conventions:

v n denotes operands which are numeric only

v c denotes operands which are character data

v cuu denotes a control unit address

Numbers are allowed in character data, however, for some operands the first character must be a letter.

The length of the strings of n or c show you the maximum length of the operand.

Operands can be shorter than the figure shows, if that is appropriate in the individual case.

For example, you can code the UMAX= parameter as UMAX=1 or UMAX=01 to limit the number of VTAMterminals which can access OMEGAMON for IMS.

Items enclosed in angle brackets (< >) can be written in any order and can have defaults. OMEGAMONfor IMS does not require you to specify those parameters that have defaults.

You can enter the parameters marked with an asterisk (*) in START Command Parameters table of theIBM Tivoli OMEGAMON XE for IMS on z/OS Planning and Configuration Guide in the VTAM logon datastream to override the setting in the VTAM START procedure.

Most of the parameters that you can specify have defaults taken from the interface or from the startedtask. You can change some of these defaults if you use an installation or user profile.

SynonymS is a synonym for START.

Starting OMEGAMON II VTAM supportStart OMEGAMON for IMS VTAM support with the START command.

The parameters you specify with the START command become the defaults for any OMEGAMON for IMSsessions that OMEGAMON for IMS VTAM support creates in response to LOGON requests.

To change a default value or any other command at logon time, use the DATA keyword of the VTAMLOGON command to override it.

The following example shows the DATA parameter in the LOGON command:LOGON APPLID(cccccccc) DATA('USER=01')


What to do if you stop OMEGAMON II VTAM supportIf you stop OMEGAMON for IMS VTAM support, any OMEGAMON for IMS display controller sessions thatare running also stop, and you must restart the sessions manually. The EPILOG collector, however,continues to collect data, even if you stop the EPILOG display controller session or OMEGAMON forIMSVTAM support.

ExamplesThe following examples all assume that M0IMSA is your OMEGAMON for IMS installation modify ID. Formore information about the modify ID, see 67 through 69 in this chapter.

Type these commands at the SDSF z/OS console to restart sessions:


v To start a Bottleneck Analysis (DEXAN) collector with a global module of KOIGBL2424, type/F M0IMSA, START DEXAN,GLOBAL=24

v To start a display controller to the dedicated terminal at 53E by using global module KOIGLBL.24, enter:/F M0IMSA, START SESSION,UNIT=53E,GLOBAL=24

v To start a display controller to the dedicated terminal at 53A with 43 physical rows and 255 logical rows,enter:/F M0IMSA, START SESSION,ROWS=43,LROWS=255,UNIT=53A

v To start VTAM support, enter:/F M0IMSA, START cccccccc APPL=OIAPPLID,UMAX=05


v To start a display controller in cross system mode, enter:/F M0IMSA, START SESSION,MODE=XS,LROWS=255,SYS=IMSA,DIR=*

where * implies use of cross system mode by using a collector ID of IMSA.

v To start a display controller in cross memory mode with an ID of SYSA, enter/F M0IMSA, START SESSION,MODE=XM,LROWS=255,SYS=IMSA,DIR=SYSA

Location of sample START commandThe rhilev.RKANPAR(KOImpP00) contains a sample START command for OMEGAMON for IMS for yourinstallation.


STOP

PurposeThe STOP command stops any interface subtask (for example, OMEGAMON for IMS VTAM support) thatmight not be functioning, due to a problem such as a terminal error.

The system console operator usually enters the STOP command by using the z/OS MODIFY command.The STOP command needs a task ID to know which task to stop. To find this ID, use the DISPLAY orLIST command.

FormatThe format is:F M0IMSA,STOP ID=cccccccc


SynonymP is a synonym for STOP.

OutputThe output from the STOP command is one or more task termination messages followed by a taskdetached message. If the task does not promptly honor the interface request for termination, the interfacedetaches it.

Stopping VTAM tasksSessions that run under OMEGAMON for IMS VTAM support do not have an interface task ID that youcan use to stop them. You can use VTAM commands to detach an individual session that runs underOMEGAMON for IMS VTAM support.

The commands you enter from an z/OS console are:V NET,INACT,I,ID=sluname

andV NET,ACT,ID=sluname

The first command causes OMEGAMON for IMS VTAM support to stop the task that runs at thatsecondary logical unit (or terminal). The message NODE NOW INACTIVE appears to indicate thatOMEGAMON for IMS VTAM support removed the task.

Wait until OMEGAMON for IMS VTAM support removes the task before you issue the second command.The second command makes the terminal available for use again by VTAM.

Note: If you use the STOP command in the format for RTA, the buckets are not cleared.


Appendix C. IMS exceptions

The following table lists all of the product exceptions in alphabetical order, along with a short description ofwhat activity each exception monitors and the name of the exception group.

Exception ID Description Exception group

ABUF Displays if sequential buffering storage utilization is > nn%. Pools (Other)

ACBH Displays if ACBLIB data set I/O rate is > nn per second. I/O Rates (Datasets)

ACEA Displays if utilization is > nn% for the communication external subsystem pool. Pools (CES)

ACIO Displays if the communications I/O pool (CIOP) utilization is > nn%. Pools (CIO)

ACWA Displays if the communications work area pool (CWAP) utilization is > nn%. Pools (CWA)

ADBH Displays if Application database call count is > nn. The default value is 100.Note: This exception is only available for IMS v10 and higher.

ApplicationExecution (AE)

ADBW Displays if database work pool utilization is > nn%. Pools (Other)

ADHI Displays if area DASD I/O per second is > nn. The value of nn is the averageDASD read + write rate for a DEDB area within a dataspace.

Fast Path (High)

ADLO Displays if area DASD I/O per second is < nn. The value of nn is the averageDASD read + write rate for a DEDB area within a dataspace.

Fast Path (Low)

ADMB Displays if database management block (DMB) pool utilization is > nn%. Pools (DMB)

ADSU Displays if the data entry database (DEDB) area is unavailable. Fast Path (Alerts)

AEPC Displays if the extended PCB pool utilization is > nn% for IMS systems thatwere generated with Fast Path.

Pools (Other)

AESH Displays if Application External Subsystem Attach Facility (ESAF) call count is >nn. The default value is 100.Note: This exception is only available for IMS v10 and higher.


AETH Displays if Application elapsed time in milliseconds is > nn. The default value is10.Note: This exception is only available for IMS v10 and higher.


AFRE Displays if the fetch request element (FRE) pool utilization is > nn%. There isno such thing as an FRE pool, but for convenience you can think of FRE thatway. Use the IMS FRE= parameter to specify the number of fixed FREs toallocate when IMS builds the message format block pool (MFP). If all of thefixed FREs are ever in use at the same time, the AFRE exception shows thepool as 100% utilized. For more FREs, IMS must carve space out of the MFPbuffer pool. These FREs are dynamic and are available as long as IMS is usingthem.Note: The FREP command displays the number of dynamic FREs that IMSallocates.

Pools (Other)

AHIO Displays if the high I/O pool (HIOP) utilization is > nn%. Pools (Other)

AIOH Displays if Application Total I/O count is > nn. The default value is 10.Note: This exception is only available for IMS v10 and higher.


ALMD Displays if the long message data set utilization is > nn%. Pools (Data SetUtilization)

AMFS Displays if the message format services (MFS) pool utilization is > nn%. Pools (Other)

AMSG Displays if the message queue buffer pool utilization is > nn%. Pools (Other)

AORH Displays if Application OSAM I/O READ count is > nn. The default value is 10.Note: This exception is only available for IMS v10 and higher.


APIE Displays if the program isolation (PI) pool utilization is > nn%. Pools (Other)



APSB Displays if the active program specification block (PSB) pool utilization is >nn%.

Pools (PSB)

APSW Displays if the PSB work pool (PSBW) utilization is > nn%. Pools (PSB)

AQBD Displays if the queue blocks data set utilization is > nn%. Pools (Data SetUtilization)

ARAU Displays if the receive any pool utilization is > nn%. Pools (CIO)

ARCB Displays if the receive any buffers in use is > nn. Pools (CIO)

ARSP Displays if the average response time > nn. Response TimeAnalysis (RTA)

ASAP Displays if the save area prefix (SAP) pool utilization is > nn%. Pools (Other)

ASHI Displays if the area dataspace I/O per second is > nn. The value of nn is theaverage dataspace read + write rate for a DEDB area within a dataspace.

Fast Path (High)

ASLO Displays if the area dataspace I/O per second is < nn. The value of nn is theaverage dataspace read + write rate for a DEDB area within a dataspace.

Fast Path (Low)

ASMD Displays if the short message data set utilization is > nn%. Pools (Data SetUtilization)

AVRH Displays if Application VSAM I/O READ count is > nn. The default value is 10.Note: This exception is only available for IMS v10 and higher.


BLGH Displays if the balancing group input is > nn. Fast Path (High)

BQHI Displays if the number of Fast Path available buffers for new PST use is > nn. Fast Path (High)

BQLO Displays if the Fast Path available buffers for new PST use are < nn. Fast Path (Low)

CBHI Displays if BMP region CPU utilization is > nn%. CPU (High)

CBLO Displays if BMP region CPU utilization is < nn%. CPU (Low)

CCHI Displays if control region CPU utilization is > nn%. CPU (High)

CCLO Displays if control region CPU utilization is < nn%. CPU (Low)

CILO Displays if the number of free control intervals in independent overflow for aDEDB area is < nn. This means that you might need to reorganize thedatabase.

Fast Path (Low)

CILP Displays if the percentage of free control intervals in independent overflow for aDEDB area is < nn%. The default value is 10.

Fast Path (Low)

CLHI Displays if the IRLM region CPU utilization is > nn%. CPU (High)

CLLO Displays if the IRLM region CPU utilization is < nn%. CPU (Low)

CMHI Displays if the MPP region CPU utilization is > nn%. CPU utilization is thepercentage of the total CPU that the MPP region used over the lastOMEGAMON cycle. CPU utilization ranges from 0% to 100% for all onlineprocessors in the complex. The default OMEGAMON cycle is five seconds.

CPU (High)

CMLO Displays if the MPP region CPU utilization is < nn%. CPU utilization is thepercentage of the total CPU that the MPP region used over the lastOMEGAMON cycle. CPU itilization ranges from 0% to 100% for all onlineprocessors in the complex. The default OMEGAMON cycle is five seconds.

CPU (Low)

CPUA Displays if the IMS CPU utilization is >= nn %. CPU (Low)

CRHI Displays if the DBRC region CPU utilization is > nn%. CPU (High)

CRLO Displays if the DBRC region CPU utilization is < nn%. CPU (Low)

CSHI Displays if the DLS region CPU utilization is > nn%. CPU (High)

CSLO Displays if the DLS region CPU utilization is < nn%. CPU (Low)



CSVC Displays if IMS control task is waiting in SVC code. IMS Status(Alerts)

CUOW Displays if one Fast Path region is in unit-of-work contention with another FastPath region.

Fast Path (Alerts)

CVAH Displays if LU 6.2 total active asynchronous conversations equal or exceedthresholds.

IMS Status(Other)

CVHI Displays if LU 6.2 total active conversations equal or exceed thresholds. IMS Status(Other)

CVSH Displays if LU 6.2 total active synchronous conversations equal or exceedthresholds.

IMS Status(Other)

DBWE Displays if an I/O error against a database occurred. Databases (Alerts)

DCMN Displays if IMS DC monitor is active. Traces (Alerts)

DDHI Displays if the dataspace DASD I/O per second is > nn. The value of nn is theaverage dataspace read + write rate for a dataspace.

Fast Path (High)

DDLO Displays if the dataspace DASD I/O per second is < nn. The value of nn is theaverage dataspace read + write rate for a dataspace.

Fast Path (Low)

DISP Displays if the dispatching priority of OMEGAMON is >= the dispatching priorityof IMS.

IMS Status(Alerts)

DLTR Displays if the DL/I trace table is on. Traces (Alerts)

DMBE Displays the names of the databases that have dynamic backout errors. Databases (Alerts)

DMER Displays if a Fast Path DEDB area has an I/O error. Fast Path (Alerts)

DMFF Displays if free space in DMB pool is fragmented. Pools (Alerts)

DNRS Displays if an I/O issued to a DASD device allocated to the IMS control regiontook longer than one OMEGAMON cycle to complete.

Resources (Alerts)

DRDY Displays if DASD device drops ready. Resources (Alerts)

DSHI Displays if the dataspace I/O per second is > nn. The value of nn is theaverage dataspace read + write rate.

Fast Path (High)

DSLO Displays if the dataspace I/O per second is < nn. The value of nn is theaverage dataspace read + write rate.

Fast Path (Low)

DSPI No areas are loaded in dataspace. Fast Path (Alerts)

DSTR Displays if dispatcher trace is on. Traces (Alerts)

DSWP Displays if a dependent region is swapped out. Resources (Alerts)

ESNC Displays if an external subsystem is defined to the control region, but not toany dependent region.

ExternalSubsystem(Alerts)

ESND Displays if an external subsystem is defined to a dependent region, but not tothe control region.

ExternalSubsystem(Alerts)

ESTH Displays if the number of active threads for an external DB2®® subsystem is >nn.

ExternalSubsystem (High)

FCIO Displays if the largest free block of the communications I/O pool (CIOP) is < nnbytes.

Fragmentation(Low)

FCWA Displays if the largest free block of the communications work area pool (CWAP)is < nn bytes.

Fragmentation(Low)

FDBW Displays if the largest free block of the database work pool is < nn bytes. Fragmentation(Low)

Appendix C. IMS exceptions 85


FDMB Displays if the largest free block of the database management block (DMB) is <nn bytes.

Fragmentation(Low)

FEPC Displays if the largest free block of the extended PCB pool is < nn bytes in IMSsystems generated with Fast Path.

Fragmentation(Low)

FHIO Displays if the largest free block of the high I/O pool (HIOP) is < nn bytes. Fragmentation(Low)

FMFS Displays if the largest free block of the message format services (MFS) pool is< nn bytes.

Fragmentation(Low)

FPSB Displays if the largest free block of the PSB pool is < nn bytes. Fragmentation(Low)

FPSW Displays if the largest free block of the PSBW is < nn bytes. Fragmentation(Low)

FPTR Displays if a Fast Path region exists, there is activity in the FP region and theFast Path trace is on. The exception requires an FPTRACE DD statement inthe IMS Fast Path region to indicate that the Fast Path trace is on.

Traces (Alerts)

HSBH Displays if the HSSP private area buffer pool usage is > nn%. Fast Path (High)

HSBL Displays if the HSSP private area buffer pool usage is < nn%. Fast Path (Low)

IBHI Displays if the BMP region I/O rate is > nn EXCPs per second over the lastOMEGAMON cycle.

I/O Rates(Regions High)

IBLO Displays if the BMP region I/O rate is < nn EXCPs per second over the lastOMEGAMON cycle.

I/O Rates(Regions Low)

ICHI Displays if the control region I/O rate is > nn EXCPs per second over the lastOMEGAMON cycle.


ICLO Displays if the control region I/O rate is < nn EXCPs per second over the lastOMEGAMON cycle.


ILHI Displays if the IRLM region I/O rate is > nn EXCPs per second over the lastOMEGAMON cycle.


ILLO Displays if the IRLM region I/O rate is < nn EXCPs per second over the lastOMEGAMON cycle.


IMHI Displays if the message processing region I/O rate is > nn EXCPs per second,during the last OMEGAMON cycle. The default OMEGAMON cycle is fiveseconds.


IMLO Displays if the message processing region I/O rate is < nn EXCPs per second,during the last OMEGAMON cycle. The default OMEGAMON cycle is fiveseconds.


INAC Displays if IMS is inactive. IMS Status(Alerts)

IORC Displays if a device allocated to IMS is in I/O error recovery. Resources (Alerts)

IRCS Displays if the CSA usage in the IRLM is > nn% of MAXCSA. Resources (High)

IRFC Displays if the false contention rate is > 70 per second.Note: This exception applies only to IRLM version 2.1 and higher versions.

Resources (High)

IRGC Displays if the IRLM is not connected to a data sharing group.Note: This exception applies only to z/OS version 5.1, 5.2, and OS/390®.

Resources (Alerts)

IRHI Displays if the DBRC region I/O rate is > nn EXCPs per second during the lastOMEGAMON cycle.


IRIN Displays if the required IRLM is not available for IMS.Note: This exception applies only to IRLM version 2.1 and higher versions.

Resources (Alerts)



IRLO Displays if the DBRC region I/O rate is < nn EXCPs per second during the lastOMEGAMON cycle.


IRQH Displays if the number of IRLM locks by region exceeds the threshold. I/O Rates(Regions Low)

IRRC Displays if the real contention rate is > 70 per second.Note: This exception applies only to IRLM version 2.1 and higher versions.

Resources (High)

IRRU Displays if the IRLM RLE usage is > 70%.Note: This exception applies only to IRLM version 2.1 and higher versions.

Resources (High)

IRTP Displays if the IRLM pass-the-buck (PTB) trace is active. Traces (Alerts)

IRTR Displays if the IRLM resource handler (RH) trace is active. Traces (Alerts)

ISHI Displays if the DLS region I/O rate is > nn EXCPs per second during the lastOMEGAMON cycle.


ISLO Displays if the DLS region I/O rate is < nn EXCPs per second during the lastOMEGAMON cycle.


ITWH Displays if the ITASKS waiting for dynamic SAPs are > nn. Pools (Other)

LALO Displays if the LSQA storage assurance is < nn K. Virtual Storage(Low)

LDMB Displays if the DMB pool blocks loaded <= nn%. Pools (DMB)

LKTR Displays if the lock trace is on. Traces (Alerts)

LLBR Displays if the OLDS buffer waits per second are > nn. Logging (OLDS)

LLCH Displays if the WADS checkwrite requests per second are > nn. Logging (WADSHigh)

LLKW Displays if the region status is WT-IRLM or WT-PIENQ and the lock waitelapsed time > nn. The default threshold is one second.

Long Lock Waits

LMGH Displays if the long message data set I/O rate is > nn per second. I/O Rates (DataSets)

LMLO Displays if the LSQA maximum free block size is < nn K. Virtual Storage(Low)

LPEX Displays if the the number of writes to WADS is > nn per second. Logging (WADSHigh)

LPOQ Displays if all logical terminals, except video-type, have an output queue length> nn.

LTERMS

LPOR Displays if the OLDS reads (dynamic backout) are > nn per second. Logging (OLDS)

LPOW Displays if the OLDS writes are > nn per second. Logging (OLDS)

LPSB Displays if the PSB pool blocks loaded <= nn%. Pools (PSB)

LSLO Displays if the LSQA total free storage is < nn K. Virtual Storage(Low)

LTOQ Displays if a video-type, logical terminal has an output queue length > nn. LTERMS

LTWA Displays if the log tape write-ahead is not active. Resources (Alerts)

LVOQ Displays if a video-type, virtual terminal has an output queue length > nn. LTERMS

MDHI Displays if the message dequeue rate is > nn per second. MessageProcessing (High)

MDLO Displays if the message dequeue rate is < nn per second. MessageProcessing (Low)



MFLD Displays if the TMEMBER is in a flood condition which occurs if the number ofTIBs in use is 100%. The number of TIBs in use reaches 100% if the TIBs inuse equal the maximum TIB count.

IMS OTMA

MFSH Displays if the MFS data set I/O rate is > nn per second. I/O Rates (DataSets)

MIRT Displays the number of message inserts that the specified region did to themessage queue. A sample MIRT message is MSG INSERT COUNT FORREGION xxxxxxxx = nn, where xxxxxxxx is the transaction and nn is the count.The count field displays the number of get calls the region did to the messagequeue. If the count field remains constant and the nn value increases, it mightindicate that the application program is in a loop.

MessageProcessing (High)

Mnnn Displays dynamic exceptions you create by using the MSGD command. Theydisplay if they detect special IMS message numbers on the log.Note: You can see these exceptions only in the menu/command interface. Formore information, See the MSGD command in the IBM Tivoli OMEGAMON XEfor IMS Realtime Commands Reference.

n/a

MPCH Displays if the MPP region database calls are > nn. MessageProcessing (High)

MSDI Displays if an MSDB has an invalid packed field. IMS resets only the packedfield if IMS restarts.

Fast Path (Alerts)

MSDO Displays if an MSDB has an overflowing field.Note: IMS resets the overflowing field at the next synchronization point.

Fast Path (Alerts)

MSGE Displays if the ICNS command is not issued. IMS Status(Alerts)

MTBR Displays if the TIB rate for a TMEMBER is > nn. IMS OTMA

MTBU Displays if the percentage of TIBs in use for a TMEMBER is 70% or higher. IMS OTMA

NACB Displays if VTAM ACB is not open. IMS Status(Alerts)

NDIR Displays if the systems programmer does not define the $$IMSDIR table. TheNDIR analysis detects an undefined $$IMSDIR table and alerts you to thepotential cause of any MFS overhead your system might be incurring.

Resources (Alerts)

NDRE Displays if the $$IMSDIR table entry is not in the MFS format library.OMEGAMON did not find a $$IMSDIR table entry in the MFS format library;you are using critical storage incorrectly.

Resources (Alerts)

NILU Displays if the IMSLU connection with APPC/MVS is not enabled. Thisexception trips only on START and FAILED.

IMS Status(Alerts)

NLOQ Displays if there is an unavailable video-type, logical terminals with an outputqueue length > nn.

LTERMS

NOFB Displays if a region is in buffer wait due to a lack of Fast Path buffers. Fast Path (Alerts)

NOOT Displays if all output threads are in use and there are buffers queuing up forOTHRs.

Fast Path (Alerts)

NPDL Displays if there is no parallel DL/I. IMS Status(Alerts)

NPOQ Displays if there is an unavailable non-video-type, logical terminals with anoutput queue length > nn.

LTERMS

NQRE Displays if a RECON data set is enqueued by another job. Resources (Alerts)

NSDC Displays if IMS does not perform START DC. IMS Status(Alerts)



NTIQ Displays non-competing transactions with an input queue length > nn. Anon-competing transaction is a transaction that is unable to run for somereason other than the competition for IMS resources. Examples are atransaction where you stopped the transaction code or a transaction thatrequires the use of a stopped database.

Transactions

NVAP Displays if there is no VTAM authorized path. Running an IMS VTAM networkwithout the VTAM authorized path option can have significant performancepenalties.

IMS Status

NVOQ Displays if there is an unavailable virtual video-type terminal with an outputqueue length > nn.

LTERMS

OBAU Displays if a region is currently using the Fast Path overflow buffer allocation. Fast Path (Alerts)

ODIE Displays if fewer than three OLDS are still active. Logging (Alerts)

OHLO Displays if the ISAM/OSAM hit ratio is < nn%. Buffer Pools

OLER Displays if OLDS nn encountered a write I/O error. Logging (Alerts)

OLNA Displays if OLDS auto archiving is not active. Logging (Alerts)

OLST Displays if OLDS nn is stopped. Logging (Alerts)

ONLC Displays if an online change is in progress. IMS Status(Alerts)

ONLO Displays if an online change occurred. IMS Status(Alerts)

ORER Displays if the number of OLDS with I/O errors is > nn. Logging (OLDS)

ORIP Displays if the number of OLDS inactive is > nn. Logging (OLDS)

ORST Displays if the number of OLDS that are stopped is > nn. Logging (OLDS)

OSBL If there are any ISAM/OSAM database buffer pools locked due to a write error,OSBL displays the number that are locked.

Pools (Alerts)

OSDN Displays if: There is only one OLDS available. The rest of the OLDS arestopped or have write errors. IMS is terminating because the last availableOLDS is damaged.

Logging (Alerts)

OXHI Displays if the OSAM database data set EXCP rate is > the user-specified limitand applies to all OSAM databases.

Databases (Alerts)

OXLO Displays if the OSAM database data set EXCP rate is < the user-specified limitand applies to all OSAM databases.

Databases (Alerts)

PAQC Displays if the asynchronous output queue count for a TPIPE is > nn. IMS OTMA

PBTR Displays if PSB trace facility is on. Traces (Alerts)

PIBC Displays if the BMP common area page-in rate is > nn per second during thelast OMEGAMON cycle.

Virtual Storage(Page-In Rates)

PIBP Displays if the BMP private area page-in rate is > nn per second during the lastOMEGAMON cycle.


PICC Displays if the common area page-in rate for the control region is > nn persecond during the last OMEGAMON cycle.


PICP Displays if the private area page-in rate for the control region is > nn persecond during the last OMEGAMON cycle.


PIDC Displays if the common area page-in rate for DBRC is > nn per second duringthe last OMEGAMON cycle.


PIDP Displays if the private area page-in rate for DBRC is > nn per second duringthe last OMEGAMON cycle.




PILC Displays if the common area page-in rate for IRLM is > nn per second duringthe last OMEGAMON cycle.


PILP Displays if the private area page-in rate for IRLM is > nn per second during thelast OMEGAMON cycle.


PIMC Displays if the message processing region common area page-in rate is > nnper second during the last OMEGAMON cycle. The default OMEGAMON cycleis five seconds.

Virtual Storage(Page-In Rate)

PIQC Displays if the input queue count for a TPIPE is > nn (IMS V10 or higher). IMS OTMA

PIQH Displays if the number of PI enqueue locks held by the indicated thread is >nn.

Locks

PIQR Displays if the input queue rate for a TPIPE is > nn (IMS V10 or higher). IMS OTMA

PIRP Displays if the message processing region private area page-in rate is > nn persecond during the last OMEGAMON cycle. The default OMEGAMON cycle isfive seconds.


PISC Displays if the common area page-in rate for the DLS region is > nn persecond during the last OMEGAMON cycle.


PISP Displays if the private area page-in rate for the DLS region is > nn per secondduring the last OMEGAMON cycle.


PITR Displays if the program isolation trace facility is on. Traces (Alerts)

POQC Displays if the output queue count for a TPIPE is > nn. IMS OTMA

POQR Displays if the output queue rate for a TPIPE is > nn. IMS OTMA

PROQ Displays if the printer is unable to receive output. Resources (Alerts)

PSTP Displays if the status of a TPIPE is stopped or input stopped. IMS OTMA

PSVC Displays if IMS physical logger task waiting in SVC code. Resources (Alerts)

PWTA Displays if the status of a TPIPE is WAITA or WAIT, which are two differenttypes of waits for the transaction pipe on a synchronous message. Thesestates indicate that IMSis waiting for an ACK or waiting for a NAK for acommit-then-send, commit-mode 0 (CM0), output response.

IMS OTMA

QBKH Displays if the queue blocks data set I/O rate is > nn per second. I/O Rates (DataSets)

RDSH Displays if the restart data set I/O rate is > nn per second. I/O Rates (DataSets)

RGNW Displays if region waiting time is > nn minutes. Regions

RGSH Displays if checkpoints taken for an IMS BMP are > nn. Regions

RGSI Displays if the region sync point interval is > nn minutes. The RGSI alerts thecustomer if current time minus time of the latest system checkpoint is greaterthan nn minutes and the region has insert and/or update activity.

Regions



ROHI Displays if the message region occupancy is > nn%. OMEGAMON calculatesthe occupancy factor by sampling each message region once everyOMEGAMON cycle, to see whether OMEGAMON scheduled a transaction. Asthis is a statistical method, the data is not significant until there is a relativelylarge number of samples. OMEGAMON bypasses this exception until it takes atleast 120 samples. If the interval setting for the OMEGAMON is five seconds,there is a 10 minute delay for OMEGAMON to calculate occupancy.OMEGAMON does not automatically treat WFI region occupancy as 100%, andconsiders only a WFI region occupied if the region is not in the waiting for inputstate. For the occupany factor calculation, OMEGAMON maintains onlysamples fewer than 60 minutes old. Therefore, the region occupancy is anaverage over the preceding hour. As message regions stop and restart,OMEGAMON begins the calculation again. A sample exception message isROHI MPP 'MESSAGE': Region Occupancy = 93.84% (High).

MessageProcessing (High)

ROLO Displays if the message region occupancy is < nn%. OMEGAMON calculatesthe occupancy factor by sampling each message region once everyOMEGAMON cycle, to see whether OMEGAMON scheduled a transaction.Because it is a statistical method, the data is not significant until there is arelativley large number of samples. OMEGAMON bypasses this exception untilit takes at least 120 samples. If the interval setting for the OMEGAMON is fiveseconds, there is a 10 minute delay for OMEGAMON to calculate occupancy.OMEGAMON does not automatically treat WFI region occupancy as 100%, andconsiders only a WFI region occupied if the region is not in the waiting for inputstate. For the occupancy factor calculation, OMEGAMON only maintainssamples fewer than 60 minutes old. Therefore, the region occupancy is anaverage over the preceding hour. As message regions stop and restart,OMEGAMON begins the calculation again. A sample exception message isROHI MPP 'MESSAGE': Region Occupancy = 6.72% (Low).

MessageProcessing (Low)

RSRV Displays if there is no VTAM connection to the RSR Tracking System. TheVTAM connection between the ACTIVE IMS and the TRACKING IMS is notavailable. The VTAM connection is only available from the ACTIVE IMS.Note: Because the TRACKING IMS can function for multiple ACTIVE IMSsystems, we cannot identify an IMS that is not connected but should be.

IMS Status(Alerts)

SAPW Displays if IMS puts an ITASK into the IWAIT state because no dynamic SAPs(save area prefix sets) are available. The SAPW exception message mightdisplay with the SDSP (selective dispatching) message. Running out ofdynamic SAPs is one reason why IMS activates selective dispatching.

IMS Status(Alerts)

SCTR Displays if the scheduler trace is active. Traces (Alerts)

SDLO Displays if the number of free control intervals in the sequential dependent partof the DEDB area is < nn%. The default value is 10.

Fast Path (Low)

SDSP Displays if selective dispatching is active. IMS invokes selective dispatching,when there is a shortage of storage for some of the IMS internal resources.IMS must restrict the scheduling of new work until IMS relieves the shortage.

IMS Status(Alerts)

SMGH Displays if the short message data set I/O rate is > nn per second. I/O Rates (DataSets)

TCOI Displays if the Time Controlled Operations (TCO) is inactive. IMS Status(Alerts)

TCOT Displays if the time controlled operations (TCO) trace is active. Traces (Alerts)

THHI Displays if the number of active threads is > nn. Threads (High)

THHP Displays if the number of active threads is > nn% of all available threads. Threads (High)

THLO Displays if the number of active threads is < nn. Threads (Low)

THLP Displays if the number of active threads is < nn% of all available threads. Threads (Low)



TMFH Displays if the test MFS data set I/O rate is > nn per second. I/I Rates (DataSets)

TMSI Displays if the Transport Manager Subsystem (TMS) is not active.Note: This also causes a break in the VTAM connection. Without TMS, youcannot re-establish the VTAM connection from the ACTIVE IMS to theTRACKING IMS.

IMS Status(Alerts)

Tnnn Displays a dynamic exception that you create by using the THIN command.This exception Displays if it detects that a CCTL exceeded its percentage ofthreads in use threshold. For more information, see the THIN command in theIBM Tivoli OMEGAMON XE for IMS Realtime Commands Reference.

n/a

TNRS Displays if a tape device is not responding to an I/O request. Resources (Alerts)

TPSB Displays a dynamic exception that you create by using the TTIM command.This exception Displays if it detects that a PSB exceeded a time threshold.Note: You can see this exception only in the command/menu interface. Formore information, see the TTIM command in the IBM Tivoli OMEGAMON XEfor IMS Realtime Commands Reference.

n/a

TRDY Displays if a tape device drops ready. Resources (Alerts)

TXIQ Displays if there are competing transactions with an input queue length > nn.The TXIQ analysis examines all competing transactions to identify thosetransactions with an input message queue length <= the threshold n, which theuser sets.Note: A transaction might queue if a message region of the appropriate classis not currently available to run the transaction. A non-competing transaction isa transaction that is unable to run for some reason other than the competitionfor IMS resources. Examples are a transaction where you stopped thetransaction code or a transaction that requires the use of a stopped database.

Transactions

VCAS Displays if database VSAM control area splits are > per minute. VSAM

VCIS Displays if database VSAM control interval splits are > nn per minute. VSAM

VHLO Displays if the VSAM hit ratio is < nn%. Buffer Pools

VMEX Displays if the number of extents for the VSAM data set is increasing. VSAM (Alerts)

VMLO Displays if IMSCTL maximum private free block size is < nn K. Virtual Storage(Low)

VROQ Displays if logical terminal is unable to receive output. IMS Status(Alerts)

VSLO Displays if IMSCTL total private free block size is < nn K. Virtual Storage(Low)

VTLO Displays if IMSCTL free block size is < nn K. Virtual Storage(Low)

VWRC Displays if the VSAM writecheck is ON for a database. VSAM (Alerts)

VXHI Displays if the VSAM database data set EXCP rate is > the user-specified limit.Note: This exception applies to all VSAM databases.

Databases (Alerts)

VXLO Displays if the VSAM database data set EXCP rate is < the user-specified limit.Note: This exception applies to all VSAM databases.

Databases (Alerts)

WBHI Displays if BMP working set size is > nn K. Working Sets(High)

WBLO Displays if BMP working set size is < nn K. Working Sets(Low)

WCHI Displays if the control region working set size is > nn K. Working Sets(High)



WCLO Displays if the control region working set size is < nn K. Working Sets(Low)

WDNA Displays if the write-ahead data sets (WADS) are inactive. Logging (Alerts)

WDNB Displays if the number of spare WADS remaining is < nn. Logging (WADSLow)

WLHI Displays if the IRLM working set size is > nn K. Working Sets(High)

WLLO Displays if the IRLM working set size is < nn K. Working Sets(Low)

WMHI Displays if the message processing region working set size is > nn K. Theworking set size is the number of real pages the region currently has inmemory. Under MVS/ESA, the working set size includes expanded storage.

Working Sets(High)

WMLO Displays if the message processing region working set size is < nn K. Theworking set size is the number of real pages the region currently has inmemory. Under MVS/ESA, the working set size includes expanded storage.

Working Sets(Low)

WRHI Displays if DBRC working set size is > nn K. Working Sets(High)

WRLO Displays if DBRC working set size is < nn K. Working Sets(Low)

WSHI Displays if DLS working set size is > nn K. Working Sets(High)

WSLO Displays if DLS working set size is < nn K. Working Sets(Low)

XCNF Displays if a Program Isolation (PI) or IMS/VS Resource Lock Manager (IRLM)resource conflict exists.

Locks (Alerts)

XRAT Displays if XRF automatic takeover is not active. XRF (Alerts)

XRAV Displays if XRF availability manager is not active. XRF (Alerts)

XRIP Displays if I/O prevention is in progress on the active IMS system. XRF (Alerts)

XRIT Displays if I/O toleration is in progress on the standby IMS system. XRF (Alerts)

XRNS Displays if XRF surveillance is not active. XRF (Alerts)

XRPH Displays if the number of PSTs held on the standby system is > nn. XRF

XRSR Displays if no secondary RDS is allocated. XRF (Alerts)

XRTO Displays if an XRF takeover is in progress. XRF (Alerts)



Appendix D. IMS Fast Paths

By using fast path navigation, you can move directly to a panel instead of navigating through a series ofpanels to reach the one that you want.

1. Tab over to Options on the Action Bar and press Enter.

2. Key in 2 (Set Preferences) and press Enter.

3. Set mnemonics to ON and press Enter. Exit from this panel.

4. Now you can use a fast path from any panel that has an Action Bar.

5. Enter the mnemonic string in the home entry field at the upper left of the panel and press Enter. Thepanel you selected displays.

Use the mnemonics in the following table as a fast path to IMS panels.

Table 9. IMS fast path mnemonics

Mnemonic Go To

GB/G1 Buffer Pools

GDG2 Databases

GO/G3 I/O

GM/G4 Message Queue

GS/G5 System Status

GC/G6 Zoom to underlying OMEGAMON session

GI/G7 Index

Move to GOTO on the Action Bar and select Index.

The following mnemonics are in the Index.

GIT Traces

GIB DB2

GII I/O

GIX XRF

GIO OSAM Pools

GIV VSAM Pools

GID Databases

GIP Storage Pools

GIL Logging

GIN Conflicts

GIF FastPath Status

GI% Device Statistics

GI( Logging Buffers and Status

GI/ Logging Details

GI# Conflicts CI

GI* Conflicts Latch

GIC CPU

GIS Virtual Storage

GIR Regions

GI1 Databases OP


Table 9. IMS fast path mnemonics (continued)

Mnemonic Go To

GI3 Logging OP WADS

GI+ Logging OP OLDS

GI5 Programs OP

GI7 Regions OP

GIZ Transactions

GIM Terminals

GIQ Message Queue

GI@ Pools Description

GIE Conversations OP

GI2 Lines OP

GI4 LTERMS OP

GI6 PTERMS OP

GI8 Transactions OP

GI9 VTAM Nodes OP

GI) Fast Path Balancing Groups

Note: If RTA is active, then the following mnemonics are active:

GIA Response Time All

GI= Bottlenecks

From the Options pull-down, select Issue IMS Queries.

Under IMS Startup Parameters and Overrides, you see a new item: Expandable Storage Pool Upper Limits.

Use any one of the following mnemonics for this item; each one takes you to the same popup: OISE OIS5 OI1EO5SE O5S5 O51E O515


Appendix E. Journal Facility control settings

The Journal Facility feature replaces the writing of data to a dataspace with the writing of data to 64-bitvirtual private storage, also known as "above-the-bar" storage. This feature also supports (optionally)archiving the data to VSAM data sets for long-term history support. The PDS member&rhilev.&rte.RKANPARU(KOIJLFnn) contains parameters that control the operation of the Journal Facility.The default values are sufficient for most environments. However, you might alter their values to suit thespecific needs of your own z/OS environment. If you do so, create a new member with a differenttwo-character suffix (such as KOIJLFnn). You might then modify the JLF Start command to specify akeyword argument of SFX=nn. Figure 42, Figure 43 on page 98, and Figure 44 on page 99 represent thedefault member KOIJLF00.

************************************************************* OMEGAMON/IMS JOURNAL FACILITY CONTROL SETTINGS** THESE VALUES CONTROL THE OPERATION OF THE JOURNAL* FACILITY AND MAY BE ALTERED TO SUIT THE SPECIFIC* NEEDS OF YOUR OWN Z/OS ENVIRONMENT. THESE VALUES* WERE CHOSEN TO WORK ’OUT-OF-THE-BOX’ AND SO THEY* ARE ALL SET TO THE SMALLER END OF THEIR RANGES.************************************************************** VIRTUAL STORAGE CONFIGURATION* ========================================*M64:2 * MAXIMUM NUMBER OF 64-BIT STORAGE (GIGABYTES).* ** * THIS NUMBER SETS THE LIMIT ON THE AMOUNT OF* * ABOVE-THE-BAR STORAGE THAT MAY BE ALLOCATED.* * THE UNIT VALUE IS A GIGABYTE AND MAY BE SET* * IN THE RANGE 1 TO 4095. THIS IS SUBJECT TO* * WHATEVER SITE LIMITATIONS ARE SPECIFIED FOR* * VIRTUAL STORAGE USAGE. CONSULT YOUR Z/OS* * SYSTEM CONFIGURATION PARAMETERS BEFORE RAISING* * THIS VALUE, AS IT CAN ADVERSELY IMPACT YOUR* * PAGING SUB-SYSTEM.** DATASET NAMING CONVENTION* ========================================** * NON-VSAM AND VSAM ARE TREATED SEPARATELY TO* * SUPPORT DATA CENTER DISK ALLOCATION POLICIES* * THAT DIFFERENTIATE BETWEEN VSAM AND NON-VSAM.** * HILEV HAS A MAXIMUM LENGTH OF 26, GIVING A TOTAL*

Figure 42. Default member KOIJLF00 (1 of 3)


DYNDSDEF:YES * SUPPORT DYNAMIC CREATION OF VSAM (YES|NO)* * IF THIS IS SET TO NO, THEN ANY NECESSARY* * VSAM DATASET NEEDED FOR DISK ARCHIVAL MUST* * ALREADY EXIST. CURRENTLY THERE IS NO JOURNAL* * CONFIGURATION SECTION FOR ICAT.*DYNNVREF:RKANPAR * DERIVE NON-VSAM DSN FROM THIS DDNAME* ** * THIS FEATURE IS USED IF THE NON-VSAM HIGH* * AND MID-LEVEL QUALIFIERS ARE NOT SPECIFIED.* * IT WILL DERIVE THE NECESSARY HIGH AND MID-LEVEL* * STANZAS FROM THE DATASET ALLOCATED TO THIS DDNAME*DYNVSREF:RKANPAR * DERIVE VSAM DSN FROM THIS DDNAME* ** * THIS FEATURE IS USED IF THE VSAM HIGH* * AND MID-LEVEL QUALIFIERS ARE NOT SPECIFIED.* * IT WILL DERIVE THE NECESSARY HIGH AND MID-LEVEL* * STANZAS FROM THE DATASET ALLOCATED TO THIS DDNAME** DISK ARCHIVAL OPTIONS* ========================================*DISKARCH:YES * SUPPORT ARCHIVAL TO DISK (YES|NO)MAXCSODS:5 * MAX NUMBER OF VSAM CLUSTERS (1-16)* ** * EACH LOGGING CLIENT (E.G ATF) CAN HAVE* * 1 TO 16 VSAM CLUSTERS FOR DISK ARCHIVAL.* * THUS WHEN MULTIPLE CLIENTS ARE LOGGING* * SIMULTANEOUSLY, YOU MAY SEE MANY MORE VSAM* * CLUSTERS THAN THE VALUE SPECIFIED HERE.* **ARCHAUTO:NO * INDICATES WHETHER MESSAGES SHOULD BE OUTPUT* * DURING ARCHIVAL WHEN SWITCHING VSAM DATASETS.* * THE VALUE FOR THIS PARAMETER CAN BE YES OR NO;* * THE DEFAULT IS NO. IF YES IS SPECIFIED, THE* * FOLLOWING WTO MESSAGES WILL BE OUTPUT DURING* * ARCHIVAL WHEN SWITCHING VSAM DATASETS:* ** * OIJ490: SWITCH FROM DSN* * OIJ491: SWITCH TO DSN* ** * WHERE DSN IS THE NAME OF THE VSAM DATASET* * BEING SWTICHED TO OR FROM DURING ARCHIVAL.* *** DISK ARCHIVAL RACE COLLISION OPTIONS* ========================================



*ARCHRACE:STOP * THE JOURNAL LOGGER WRITES TO 64-BIT STORAGE.* * THE DISK ARCHIVAL READS FROM 64-BIT STORAGE.* * IN A CONSTANT HIGH-THROUGHPUT ENVIRONMENT* * THE WRITER WILL EVENTUALLY CATCH UP WITH* * THE READER. WHEN THIS RACE COLLISION OCCURS* * THERE ARE TWO ACTIONS THAT MAY BE TAKEN.* ** * STOP - MEANS STOP ALL FURTHER DISK ARCHIVAL.* * THIS WILL ABANDON THE CURRENT WRITE* * TO VSAM, CLOSE DATASETS, AND TERMINATE* * THE DISK ARCHIVAL SUB-TASK. IT CAN BE* * RESTARTED BY RESTARTING THE TASK THAT* * WAS ISSUING THE LOGGING REQUESTS.* ** * SKIP - MEANS RESUME ARCHIVAL AFTER THE READER* * HAS PASSED BY. THIS WILL RESULT IN THE* * LOSS OF ALL CURRENT IN-MEMORY 64-BIT DATA* * FROM BEING WRITTEN TO DISK. DISK ARCHIVAL* * WILL RESUME AT THE NEXT AVAILABLE 64-BIT* * EXTENT WHEN THE JOURNAL TASK FILLS IT.* *** VSAM DATASET OPTIONS* ========================================*VSAMALLO:MEG * VSAM ALLOC UNIT (CYL, TRK, MEG)* ** * THE DEVICE INDEPENDANT USE OF MEGABYTES IS* * THE RECOMMENDED DATASET ALLOCATION METHOD.* * CONSULT THE DFSMS ACCESS METHOD SERVICES* * REFERENCE MANUAL FOR MORE INFORMATION.*VSAMPRIA:64 * VSAM PRIMARY ALLOCATION UNIT (1 TO 999)* ** * THE JOURNAL FACILITY USES MULTIPLE WRAPPING* * VSAM CLUSTERS. WHEN ONE DATASET FILLS UP, IT* * SWITCHES TO THE NEXT VSAM DATASET. THIS IS* * WHY WE USE ONLY A PRIMARY ALLOCATION VALUE.*VSAMSHRO:(1,3) * VSAM CONTROL SHARE OPTIONS (N N)* ** * THE DEFAULT VALUE FOR CROSS-REGION AND* * CROSS-SYSTEM READ/WRITE INTEGRITY IS 1,3.* * CONSULT THE DFSMS ACCESS METHOD SERVICES* * REFERENCE MANUAL FOR MORE INFORMATION.** JLF RAS OPTIONS* ========================================** * RAS MAY BE ENGAGED FOR EACH INDIVIDUAL TASK* * (MAIN, CSO, VSAM ARCHIVE, AND 64-BIT CACHE)* * WITHIN EACH TASK, RAS MAY BE ENGAGED FOR A* * PARTICULAR ACTIVITY (START/STOP, WAIT/POST,* * READ/WRITE, VSAM/DISK, CACHE/ARCHIVE, ETC).* * ALL RAS OPTIONS ARE INTENDED TO BE USED BY* * PRODUCT TEST AND/OR CUSTOMER SUPPORT PERSONNEL.* * INFORMATION ON RAS OPTIONS WILL BE ADDED HERE:************************************************************** END OF JOURNAL FACILITY DEFAULT CONTROLS***********************************************************


Appendix E. Journal Facility control settings 99


Appendix F. Documentation library

This appendix contains information about the publications related to the OMEGAMON XE products and toIBM Tivoli Monitoring and the commonly shared components of Tivoli Monitoring Server. Thesepublications are listed in the following categories:

v “OMEGAMON XE for IMS publications”

v “Shared OMEGAMON XE publications” on page 102

v “IBM Tivoli Monitoring library” on page 102

v “Related publications” on page 104

See IBM Tivoli Monitoring and OMEGAMON XE Products: Documentation Guide, SC23-8816, forinformation about accessing and using the publications. You can find the Documentation Guide in the IBMTivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

To find a list of new and changed publications, click What's new on the Welcome page of the IBM TivoliMonitoring and OMEGAMON XE Information Center. To find publications from the previous version of aproduct, click Previous information centers on the Welcome page for the product.

OMEGAMON XE for IMS publicationsThe following publications provide information about the OMEGAMON XE for IMS product:

v Program Directory, GI13-2251

Contains information about the material and procedures that are associated with the installation ofOMEGAMON XE for IMS on z/OS. The Program Directory is intended for the system programmer whois responsible for program installation and maintenance.

v Planning and Configuration Guide, SC27-4441

Documents the planning and configuration tasks necessary for the implementation of on OMEGAMONXE for IMS on z/OS. This document is written for system administrators and others who are responsiblefor installing and configuring OMEGAMON XE for IMS.

v User's Guide, SC27-4440

Introduces the features, workspaces, attributes, and predefined situations for the product andsupplements the user assistance provided with this product.

v Parameter Reference, SC27-4430

Provides reference information about the parameters that are used to set and store configuration valuesfor the runtime environments in which the on OMEGAMON XE for IMS on z/OS monitoring agent andthe OMEGAMON II for IMS components are configured.

v Troubleshooting Guide, SC27-4438

Provides explanations for the messages issued by the product and the OMEGAMON II for IMScomponent.

v OMEGAMON for IMS User's Guide, SC27-4439

Describes in detail all of the features of the OMEGAMON XE for IMS classic interface

v Realtime Commands Reference, SC27-4437

Describes in detail all of the features of the OMEGAMON XE for IMS command interface.

v Bottleneck Analysis Reference, SC27-4436

Provides reference information and descriptions of the features of the bottleneck analysis component.

v Response Time Analysis Reference, SC27-4435

Provides reference information and descriptions of the features of the response time analysis (RTA)component.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/


v Application Trace Facility Reference, SC27-4434

Explains how the Application Trace Facility (ATF) monitors and collects detailed information about IMSand Data base Control (DBCTL) transactions to help you analyze and improve performance.

v Historical Component (EPILOG) User's Guide, SC27-4433

Teaches you, step-by-step, how to operate the historical component (EPILOG) reporter after installation.

v Historical Component (EPILOG) Reference, SC27-4432

Provides a comprehensive description of the features of the historical component (EPILOG).

v Transaction Reporting Facility Reference, SC27-4431

Provides user and reference information about the features of the batch Transaction Reporting Facilitycomponents.

Shared OMEGAMON XE publicationsThe following publications provide information common to the OMEGAMON XE products:

v Quick Start Guide, GI11-8918

Summarizes the installation and setup of an OMEGAMON XE monitoring agent on z/OS.

v Common Parameter Reference, SC14-7280

Provides reference information about the parameters that are used to set up runtime environments andconfigure hub and remote Tivoli Enterprise Monitoring Servers on z/OS.

v IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: PARMGEN Reference,SC22-5435

Provides detailed instructions and common configuration scenarios for creating and maintaining runtimeenvironments by using the PARMGEN configuration method.

v IBM Tivoli Monitoring and Tivoli Management Services on z/OS: Enhanced 3270 User Interface Guide,SC22-5426

Describes the features of the interface and provides operating instructions and reference material.

v Common Planning and Configuration Guide, SC23-9734

Gives instructions for planning and configuration tasks common to the components of TivoliManagement Services on z/OS and the OMEGAMON XE monitoring agents on z/OS.

v Upgrade Guide, SC23-9745

Gives instructions for complete and staged upgrades of the OMEGAMON XE products.

v End-to-End Response Time Feature Reference, SC27-2303

Provides instructions and reference information for the End-to-End Response Time Feature, whichsupplies response time data to several OMEGAMON XE products.

v Reports for Tivoli Common Reporting, SC27-2304

Explains how to use the Tivoli Common Reporting tool to create reports from data displayed in the TivoliEnterprise Portal and stored in the Tivoli Data Warehouse database.

IBM Tivoli Monitoring libraryThe following publications provide information about IBM Tivoli Monitoring V6.2 and about the commonlyshared components of Tivoli Monitoring Server:

v Quick Start Guide, GI11-8058

Introduces the components of IBM Tivoli Monitoring.

v Exploring IBM Tivoli Monitoring, SC32-1803

Provides a series of exercises to help you explore IBM Tivoli Monitoring. By completing the activities inthis workbook, you can install and configure your monitoring environment, explore both the graphicaland command-line interfaces of the product, use some of the new features, and work with severalmonitoring agents.


v Installation and Setup Guide, GC32-9407

Provides instructions for installing and configuring IBM Tivoli Monitoring components on Windows, Linux,and UNIX systems.

v Program Directory for IBM Tivoli Management Services on z/OS, GI11-4105

Gives instructions for the SMP/E installation of the Tivoli Monitoring Server components on z/OS.

v Configuring the Tivoli Enterprise Monitoring Server on z/OS, SC27-2313

Gives detailed instructions for using the Configuration Tool to configure Tivoli Enterprise MonitoringServer on z/OS systems. Includes scenarios for using batch mode to replicate monitoring environmentsacross the z/OS enterprise. Also provides instructions for setting up security and for adding applicationsupport to a Tivoli Enterprise Monitoring Server on z/OS.

v Administrator's Guide, SC32-9408

Describes the support tasks and functions required for the Tivoli Enterprise Portal Server and clients,including Tivoli Enterprise Portal user administration.

v Tivoli Enterprise Portal online help

Provides context-sensitive reference information about all features and customization options of theTivoli Enterprise Portal. Also gives instructions for using and administering the Tivoli Enterprise Portal.

v User's Guide, SC32-9409

Complements the Tivoli Enterprise Portal online help. The guide provides hands-on lessons and detailedinstructions for all Tivoli Enterprise Portal features.

v Command Reference, SC32-6045

Provides detailed syntax and parameter information and examples of the commands you can use inIBM Tivoli Monitoring.

v Troubleshooting Guide, GC32-9458

Provides information to help you troubleshoot problems with the software.

v Deployment Guide, SC23-8873

Outlines key activities such as planning, maintenance, and tuning considerations that are needed toensure a successful deployment of your IBM Tivoli Monitoring environment.

v Messages, SC23-7969

Lists and explains messages generated by all IBM Tivoli Monitoring components and by z/OS-basedTivoli Monitoring Server components (such as Tivoli Enterprise Monitoring Server on z/OS andTMS:Engine).

v Upgrading from V5.1.2, GC32-1976

Gives instructions for upgrading custom resource models from IBM Tivoli Monitoring V5.1.2 to IBM TivoliMonitoring V6.2.

v IBM Tivoli Universal Agent User's Guide, SC32-9459

Introduces you to the IBM Tivoli Universal Agent, an agent of IBM Tivoli Monitoring. The IBM TivoliUniversal Agent enables you to use the monitoring and automation capabilities of IBM Tivoli Monitoringto monitor any type of data you collect.

v IBM Tivoli Universal Agent API and Command Programming Reference Guide, SC32-9461

Explains the procedures for implementing the IBM Tivoli Universal Agent APIs and providesdescriptions, syntax, and return status codes for the API calls and command-line interface commands.

v Agent Builder User's Guide, SC32-1921

Explains how to use the Agent Builder for creating monitoring agents and their installation packages,and for adding functions to existing agents.

v Fix Pack Readme and Documentation Addendum

Describes the installation process for a fix pack and provides updated information about problems andworkarounds associated with the fix pack. A new version of this document is created for each fix pack.

Appendix F. Documentation library 103

Related publicationsYou can find useful information about the OMEGAMON XE Tivoli Enterprise Monitoring Agents in the IBMTivoli Monitoring and OMEGAMON XE Information Center at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/.

Other sources of documentationYou can also obtain technical documentation about monitoring products from the following sources:

v IBM Integrated Service Management Library

http://www.ibm.com/software/brandcatalog/ismlibrary/

The Integrated Service Management Library is an online catalog that contains integration documentationas well as other downloadable product extensions.

v IBM Redbooks publications

http://www.redbooks.ibm.com/

Redbooks® publications, Redpapers, and Redbooks Technotes provide information about products fromplatform and solution perspectives.

v Technotes

Technotes provide the latest information about known product limitations and workarounds. You can findTechnotes through the IBM Software Support website at http://www.ibm.com/support/entry/portal/software.

v Tivoli wikis on the IBM developerWorks website

Tivoli Wiki Central at http://www.ibm.com/developerworks/wikis/display/tivoli/Home is the home forinteractive wikis that offer best practices and scenarios for using Tivoli products. The wikis contain whitepapers contributed by IBM employees, and content created by customers and business partners.

Two of these wikis are of particular relevance to IBM Tivoli Monitoring:

– Tivoli Distributed Monitoring and Application Management Wiki at http://www-10.lotus.com/ldd/tivmonitorwiki.nsf provides information about IBM Tivoli Monitoring and related distributed products,including IBM Tivoli Composite Application Management products.

– Tivoli System z Monitoring and Application Management Wiki at http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home provides information about the OMEGAMON XE products, TivoliNetView for z/OS, Tivoli Monitoring Agent for z/TPF, and other System z monitoring and applicationmanagement products.




http://www.ibm.com/software/brandcatalog/ismlibrary/

http://www.redbooks.ibm.com/

http://www.ibm.com/software/support

http://www.ibm.com/software/support

http://www.ibm.com/developerworks/wikis/display/tivoli/Home

http://www-10.lotus.com/ldd/tivmonitorwiki.nsf

http://www-10.lotus.com/ldd/tivmonitorwiki.nsf

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

http://www.ibm.com/developerworks/wikis/display/tivoliomegamon/Home

Appendix G. Accessibility

Accessibility features help users with physical disabilities, such as restricted mobility or limited vision, touse software products successfully. OMEGAMON XE monitoring products support several user interfaces.Product functionality and accessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:

v Use assistive technologies, such as screen-reader software and digital speech synthesizer, to hear whatis displayed on the screen. Consult the product documentation of the assistive technology for details onusing those technologies with this product.

v Operate specific or equivalent features using only the keyboard.

v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the following features to aid accessibility:

v All documentation is available in both HTML and convertible PDF formats to give the maximumopportunity for users to apply screen-reader software.

v All images in the documentation are provided with alternative text so that users with vision impairmentscan understand the contents of the images.

The OMEGAMON XE on z/OS Information Center, and its related publications, are accessibility-enabled.The accessibility features of the information center are described at http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html.

Interface informationThe Tivoli Enterprise Portal interface offers the greatest range of functionality, but is not entirelyaccessible. The OMEGAMON enhanced 3270 user interface offers more limited functionality, but is entirelyaccessible. (The enhanced 3270 user interface supports all the accessibility features supported by youremulator. If you are using IBM Personal Communications, you can find information on its accessibilityfeatures at http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm. If you are using a third-party emulator, see the documentation for thatproduct for accessibility information.)

The OMEGAMON ("classic") and OMEGAMON II (CUA) 3270 interfaces use an ISPF style interface.Standard and custom PF Key settings, menu options, and command-line interface options allow for shortcuts to commonly viewed screens. While basic customization options allow for highlights and othereye-catcher techniques to be added to the interface, the customization options are limited.

Related accessibility informationYou can view the publications for OMEGAMON XE on z/OS in Adobe Portable Document Format (PDF)using the Adobe Acrobat Reader. The PDFs are provided on a CD that is packaged with the product, oryou can access them at http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm

IBM and accessibilitySee the http://www.ibm.com/able for more information about the commitment that IBM has to accessibility.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://publib.boulder.ibm.com/infocenter/pcomhelp/v6r0/index.jsp?topic=/com.ibm.pcomm.doc/books/html/quick_beginnings10.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm

http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.omegamon.xe_ims.doc_5.1.0/welcome_omxeims510.htm

http://www.ibm.com/able


Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the followingways for you to obtain the support you need:

OnlineGo to the IBM Software Support site at http://www.ibm.com/software/support/probsub.html andfollow the instructions.

IBM Support AssistantThe IBM Support Assistant (ISA) is a free local software serviceability workbench that helps youresolve questions and problems with IBM software products. The ISA provides quick access tosupport-related information and serviceability tools for problem determination. To install the ISAsoftware, go to http://www.ibm.com/software/support/isa.

Troubleshooting GuideFor more information about resolving problems, see the products Troubleshooting Guide.


http://www.ibm.com/software/support/probsub.html

http://www.ibm.com/software/support/isa


Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Any referenceto an IBM product, program, or service is not intended to state or imply that only that IBM product,program, or service may be used. Any functionally equivalent product, program, or service that does notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement might not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication. IBMmay make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including this one)and (ii) the mutual use of the information which has been exchanged, should contact:


IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some casespayment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the resultsobtained in other operating environments may vary significantly. Some measurements may have beenmade on development-level systems and there is no guarantee that these measurements will be the sameon generally available systems. Furthermore, some measurement may have been estimated throughextrapolation. Actual results may vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change withoutnotice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before theproducts described become available.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programs inany form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conforming toIBMs application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, must include a copyrightnotice as follows:

© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. ©Copyright IBM Corp. _enter the year or years_. All rights reserved.


If you are viewing this information in softcopy form, the photographs and color illustrations might not bedisplayed.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at“Copyright and trademark information” at www.ibm.com/legal/copytrade.shtml.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of SunMicrosystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Notices 111


Index

Special characters/ASF INFO-line

See OPTN immediate/BELL INFO-line

See OPTN immediate/LOG OFF INFO-line

See OPTN immediate/LOG ON INFO-line

See OPTN immediate/TSF immediate

See OPTN immediate/XLF INFO-line

See OPTN immediate/ZER INFO-Line

See OPTN immediate.ASF immediate

See OPTN immediate.BEL immediate

See OPTN immediate.LOGOFF immediate

See OPTN immediate.LOGON immediate

See OPTN immediate.SMT immediate

See OPTN immediate.TSF immediate

See OPTN immediate.XLF immediate

See OPTN immediate.ZER immediate

See OPTN immediate$OIDEXAN macro 59$OIGROUP FINAL 54$OIGROUP FINAL macro 59$OIGROUP ID 54$OIGROUP ID macro 56$OIGROUP INITIAL 54$OIGROUP INITIAL macro 55$OIGROUP macro 55, 57

Aaccessibility features 105Application Trace Facility (ATF) 79assembling 55asterisk (*) 70ATF 79automatic screen facility (ASF)

activating 47automatic update

setting cycles 47

Bbatch job

displaying identifiers 68

bellactivating 47setting interval 47

BMPinterface 49

bottleneck analysisaccuracy of values 67

CChanging IMS Command Options 51CLASS parameter 56CLRL

in macro 60CLRS

in macro 60color support

setting options 47command 47

options 51commands 68, 74

comment 70D A,L

display active 68DISPLAY 71display active

D A,L 68EXEC 72

START 74F 68HELP 73IF 74LIST

DISPLAY 75LOG 76MODIFY 68

MODIFY ID 69MODIFY MERGE 77P 68START 78STOP 68

MODIFY 67P 82

VTAM LOGON 80comment 70concatenating screen space and profile data sets 60conditional processing commands 74console

using LOG command to display messages 76CPUID parameter 74customization

requirements for each mode 3

DD A,L command 68DASD reserve 47


DATA parameter 80data sets 68, 70, 72, 74date

format 47DBSW

in macro 60dedicated mode 3default

starting the interface 68default Bottleneck Analysis (DEXAN) parameters

modifying 59default options 45defaults

setting 55developerWorks website 104device

name table entries 47DEXAN

accuracy of values 67DEXAN macro 60display active command 68DISPLAY command 71, 75documentation

See publications

Eediting

KOIGBL 55environments

creating KOIGBL modules 54exception analysis 44exception logging facility (XLF)

activating 47EXEC command 72, 74EXPTHR 59

FIX 59EXPTHR parameter 58, 59EXPTHR= parameter 58

FF command 68fetch (.FGO)

setting parameters 47FIX 59FIX parameter 57, 59formats

macro 55

Ggroup number 58, 59GROUPS parameter 57GRP paramerter 59GRP parameter 58GRSP 59

SETG 59

HHELP command 73

IIBM monitor job

showing identifiers 68IBM Support Assistant 107IBM-supplied profile 43identifiers

batch job 68IBM monitor job 68started task 68

IDs, z/OSSee MVS IDs

IF command 74IMS

command options 51using MODIFY MERGE command 77

IMSID parameter 74IMSTYPE parameter 74input queue time 57installation profile

IOPT command 47installation-defined profile

create 45save 48

Integrated Service Management Librarydocumentation 104

interface 67, 68See also interface commandsconditional execution of 74starting 68startup parameters 67terminating 68

interface z/OS IDsSee MVS IDs

internaldisplaying 71

intervalsetting 47

IPL Elimination utility 63IPRF command

delete profile 48save profile 48

ISA 107ISET 59ISPF mode 3

JJCL model 55

KKIPWIPER utililty 63KIPWIPER utility

log 64parameters 63sample JCL 63


KOIGBLdata set 55macros 55module 54

KOIGBL modules 55KOIGBLA

in TKANSAM 55KOIIAOO

startup parameter 67KOIM0P00 68

Llibraries 68, 70, 72, 74

IBM Tivoli Monitoring 102OMEGAMON XE shared publications 102

linkingKOIGBL 55

LIST command 75load

module data set 55log

activating 47LOG command 76log message for processing member 76looping

setting parameters 47

Mmacro formats 55macro instructions 55Macro instructions 55menus

Profile Maintenance 48messages 76, 77minor commands

setting case 47modes of operation 3MODIFY

example 68strating the interface 68

MODIFY command 67, 68, 69example 68starting the interface 68

MODIFY ID command 69MODIFY MERGE command 77monitor job, IBM

showing identifiersdisplay active command 68

MTHRin macro 60

multiple 54

NNAME parameter 59NODE parameter 56, 57

OOMEGAMON for IMS DATA (KOIGBLmp) 54operating modes 3operational parameters

setting 47output

setting case 47output queue time 57

PP command 68, 82parameters

CPUID 74DATA 80IMSID 74IMSTYPE 74interface startup

startup parameter, interface 67KOIIAOO,startup 67MPREFIX=

MPREFIX= parameter 67SMFID 74

PARM field 55printing

setting output options 47processing time 57product components 2profile maintenance and session controls menu 45profiles 43

defining 45IBM 46search order 44select options 45storage 44suffix 43types 43

program input queue time 57program name

displaying 71using LIST command to display 75

PSB parameter 56publications

developerWorks website 104IBM Tivoli Monitoring 102Integrated Service Management Library 104OMEGAMON XE 102Redbooks 104related 104shared 102Technotes 104Tivoli Management Services on z/OS 102types 101wikis 104

RRedbooks 104REPORT file

defining size 47

Index 115

response time 0 57response time1 57RKANPAR

using the EXEC command 72RKANPAR(KOIM0P00)

starting the interface 68RKOIPCSV 60RKOIPROC 60RKOIPROF DD 61RTA 57, 58, 59

THRESH 59thresholds 57

SSAP

checking the status 53implementing 52starting 53starting automatically 53starting from z/OS console 53stopping 53stopping from the z/OS console 53

saveinstallation-defined profile 48

SCALin macro 60

screendisplay options 46, 47

screen space 47first 47

scrollingsetting 47

securityconsiderations 48console commands 67

session options command 46, 47SETG 59shared publications 102SMFID parameter 74Software Support 107START command 74, 78started as started task

displaying identifiers 68started task

displaying identifiers 68starting ATF 79starting tasks 78STEPLIB 61STIM

in macro 60STOP command 67, 68, 82support assistant 107system console

using LOG command to display messages 76

Ttask ID

using LIST command to display 75task IDs 71

tasksstarting 78

Technotes 104TERM parameter 56, 57terminal 47terminate interface 68THRESH 59THRESH parameter 58, 59thresholds 44

specifying 57THRS

in macro 60timed screen facility (TSF)

activating 47TKANMAC 55TKANMAC library 55TKANPAR

using the comment interface command 70using the EXEC command 72using with the IF command 74

TRAN parameter 56TSO 3

UUSER

start option for profiles 44user profile 51user profiles 43user thresholds and parameters - building a library 55utility

IPL Elimination 63

VVTAM

mode 3VTAM LOGON command 80VTAM nodes

group containing 57

Wwikis 104work area

size for PEEK command 47workload groups

modifying 55

Zz/OS IDs

creatingdefault 67


��

Printed in USA

Date post:	17-Apr-2018
Category:	Documents
Upload:	hoangthuy
View:	241 times
Download:	4 times