Unicenter CA-Insight™ Performance Monitor for DB2 for z/OS and OS/390

System Guide 6.3

K00044-3E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

 2003 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Contents

Chapter 1: Introduction What Is Unicenter CA-Insight? ...... 1–1 Defining Areas of DB2 Responsibility ...... 1–2 Benefits ...... 1–3 Required Components...... 1–4 Data Collector ...... 1–4 PC Owner ...... 1–5 Query Language (IQL) Request ...... 1–5 TSO User Interface ...... 1–5 Batch Report Writer ...... 1–5 Online History ...... 1–6 Optional Components ...... 1–6 Global Subsystem (GSS) ...... 1–6 VTAM User Interface ...... 1–7 Remote Access Facility (RAF)...... 1–7 NATURAL for DB2 Support...... 1–8 System Condition Monitor (SCM)...... 1–8 Unicenter CA-24X7 ...... 1–8 Unicenter Agent for DB2 ...... 1–9 Unicenter Performance Management Predictor (PMP) ...... 1–9 Optional History Components ...... 1–9 Online History Archiver ...... 1–9 DB2 Performance Data Archive ...... 1–10 Typical Configurations ...... 1–10 One DB2 Subsystem, One MVS Image...... 1–11 Multiple DB2 Subsystems, One MVS Image ...... 1–11 Multiple DB2 Subsystems, Multiple MVS Images ...... 1–12

Contents iii Chapter 2: Verifying the Basic Installation Verify Batch Reporting ...... 2–1 Verify Online Access ...... 2–2 Verify Online Reporting ...... 2–3 Navigation Features ...... 2–4 Verify User Interface Reporting...... 2–4

Chapter 3: Beyond the Basic Installation Installing Components as Started Tasks ...... 3–1 DB2 Commands and EXPLAIN ...... 3–3 EXPLAIN and DSN3AUTH ...... 3–3 Scheduling High-Level DB2 Reports Using SMF Data ...... 3–4 From SMF Data Sets ...... 3–4 From Online History ...... 3–5 Scheduling Detailed DB2 Reports using SMF Data ...... 3–5 Managing Data Collector DASD Output ...... 3–6 Archiving by Generation Data Group (GDG) ...... 3–7 Archiving without Generation Data Groups ...... 3–7 Archiving DB2 History to the History Database ...... 3–8 Implementing the CICS Monitoring Facility ...... 3–8 Step 1: Create a Monitor Control Table ...... 3–8 Step 2: Define the Journal Control Table ...... 3–9 Step 3: Linkedit the CICS Type 2 SVC ...... 3–9 Step 4: Allocate Journal Data Sets ...... 3–10 Step 5: Update the SIT Table ...... 3–10 Turning Monitoring On and Off ...... 3–10 Data Sharing Implementation Considerations ...... 3–11

Chapter 4: Installing Optional Components Global Subsystem (GSS) ...... 4–1 When to Use GSS ...... 4–1 Dependencies...... 4–2 Installing the Global Subsystem (GSS) ...... 4–2 Step 1: Complete the GSS Installation Worksheet ...... 4–3 Naming Conventions ...... 4–3 DASD Space Requirements...... 4–3 GSS Installation Worksheet...... 4–4

iv System Guide Step 2: Modify the GSS Installation Edit Macro...... 4–4 Step 3: Allocate and Load GSS Product Libraries ...... 4–5 Step 4. Copy GSSRC Module to the Load Library (GSSRCCPY) ...... 4–6 Step 5: APF-Authorize the GSS LINKLIB ...... 4–6 Step 6. Define and Load Global GSS IMOD Data Set ...... 4–7 Step 7: Define Product-Specific GSS ILOG Data Sets ...... 4–7 Step 8: Install MVS Subsystem Names for GSS ...... 4–8 Step 9. Create GSS Started Task Procedure...... 4–8 Step 10: Modify the GSS PARMLIB Data Set ...... 4–9 DB2SSID Customization ...... 4–9 GSSSPARM Customization...... 4–10 GSSRUNP Customization ...... 4–10 Step 11: Verify GSS Installation ...... 4–11 Step 12: Install the GSS ISERVE Editor as an ISPF Application (Optional) ...... 4–11 Prerequisite...... 4–12 Modifying the Menu Panel ...... 4–12 Allocating Data Sets with a CLIST ...... 4–12 Dynamic Concatenation Programs ...... 4–13 Increasing ILOG File Sizes ...... 4–13 Adding ILOG Subfiles ...... 4–14 Enable the Unicenter CA-SYSVIEW or GSS User Interface ...... 4–14 The VTAM User Interface ...... 4–15 Installing the VTAM User Interface ...... 4–15 Step 1: Prepare VTAM ...... 4–15 Step 2: Prepare VTAM User Interface Parameters ...... 4–16 Step 3: Prepare VTAM User Interface JCL ...... 4–17 IDB2VUS Sample JCL Member ...... 4–17 IDB2VUS Sample JCL Explanation ...... 4–18 Step 4: Modify Security for the NSIGHTEX User Exit ...... 4–20 RACF and eTrust CA-Top Secret Considerations ...... 4–20 Additional CA-Top Secret Considerations ...... 4–21 eTrust CA-ACF2 Considerations ...... 4–22 Step 5: Verify VTAM User Interface Installation ...... 4–23 Remote Access Facility (RAF) ...... 4–23 Installing the Remote Access Facility ...... 4–24 Step 1: Prepare VTAM ...... 4–24 Step 2: Prepare Data Collector and User Interface Parameters ...... 4–26 Step 3: Prepare User Interface Parameters ...... 4–26 Step 4: Verify the RAF Installation ...... 4–27

Contents v NATURAL for DB2 Support ...... 4–27 Installing NATURAL for DB2 Support ...... 4–28 Step 1. Modify DB2, the Data Collector, and the PC Owner...... 4–28 Modify DB2 ...... 4–28 Modify the Data Collector...... 4–29 Modify the PC Owner ...... 4–29 Start the Data Collector ...... 4–29 Step 2: Modify NATURAL for use with CICS, TSO, and CAF...... 4–29 Modify CICS...... 4–29 Modify NATURAL ...... 4–30 Step 3: Modify NATURAL for Use with IMS (Optional)...... 4–31 Step 4: Validate the Installation ...... 4–32 Systems and DBA Menus ...... 4–32 Auditor Menu ...... 4–33 Active Threads Reports ...... 4–33 Probe Manager Reports ...... 4–33 User-Initiated Reports ...... 4–33 System Condition Monitor (SCM) ...... 4–34 Installing the System Condition Monitor (SCM) ...... 4–34 Step 1: Modify the Data Collector Initialization Parameters...... 4–34 Step 2: Modify the GSS Runtime Parameters ...... 4–34 Step 3: Modify the Startup Member (Optional) ...... 4–35 Step 4: Modify the VTAM User Interface (Optional) ...... 4–35 Step 5: Enable the SCM ...... 4–36 Step 6: Verify the Installation ...... 4–36 Global View Panel...... 4–36 Beyond the Basic SCM Installation ...... 4–37 Using Shadow Catalog Tables for EXPLAIN...... 4–38 Creating and Using Shadow Catalog Tables ...... 4–38 Using Existing Shadow Catalog Tables ...... 4–38 Optionally Create Table Indexes to Speed Performance ...... 4–39

vi System Guide Chapter 5: Operation and Customization Data Collector Operation and Customization ...... 5–1 Starting the Data Collector ...... 5–2 Batch Job JCL Example...... 5–2 JCL Procedure Explanation...... 5–3 Started Task Procedure Sample ...... 5–6 JCL Procedure Explanation ...... 5–7 Starting the Data Collector as a Started Task ...... 5–8 Started Task Options ...... 5–8 Stopping the Data Collector ...... 5–8 Recommended Procedure ...... 5–8 Optional Procedure...... 5–9 Operator Commands ...... 5–9 USERS ...... 5–9 IFI ...... 5–10 Canceling a User Interface Session ...... 5–11 Canceling a TSO or VTAM User ...... 5–11 Canceling a Remote Access Facility User ...... 5–11 Remote Access Facility Commands ...... 5–12 Switch History Files Command ...... 5–12 Issuing Unicenter CA-24X7 Commands from the Console ...... 5–13 Dynamically Starting and Stopping the Unicenter Agent for DB2 ...... 5–13 How the Data Collector Uses DB2 ...... 5–14 Basic Attachment to DB2 ...... 5–14 Authorization IDs ...... 5–14 Authorization ID for DB2 Commands ...... 5–14 IFI versus Non-IFI ...... 5–15 Data Collector Buffer Sizes ...... 5–15 About Traces ...... 5–16 DB2 Trace Destination ...... 5–16 DB2 Trace Types ...... 5–16 Trace Classes ...... 5–17 Performance Trace Classes ...... 5–18 How Unqualified Requests Affect Traces ...... 5–19 Qualified DB2 Traces ...... 5–19 Installing the Data Collector Without the IFI ...... 5–20 Monitoring a DB2 Subsystem without IFI ...... 5–20 Prepare System Parameters ...... 5–21

Contents vii Customizing Data Collector Initialization Parameters...... 5–21 DEFAULTS Statement ...... 5–21 Keywords ...... 5–22 Parameters You Can Override ...... 5–40 Startup Requests ...... 5–41 Sample Startup Requests File ...... 5–41 The Constants Table (CONSTBL) ...... 5–41 Changing Month Abbreviations ...... 5–42 Changing Day Abbreviations ...... 5–42 Translate Table for Alphas ...... 5–43 Translate Table for Uppercase ...... 5–43 Troubleshooting ...... 5–44 Online User Interface Operation and Customization ...... 5–44 How the User Interfaces Work With the Data Collector ...... 5–44 Requirements...... 5–45 Data Collector Communication ...... 5–45 TSO ...... 5–45 VTAM ...... 5–45 Batch...... 5–45 DD Statements...... 5–46 IUIMAPS ...... 5–46 REQUESTS ...... 5–46 SYSPARMS ...... 5–46 DBGPRINT ...... 5–47 Customizing User Interface Session Parameters ...... 5–47 Sample Member...... 5–47 DEFAULTS Statement ...... 5–48 Keywords ...... 5–48 TSO User Interface ...... 5–51 ISPF CLIST ...... 5–51 ISPF Menu...... 5–52 IQL Request Library ...... 5–52 Accessing the TSO User Interface ...... 5–52 Security Control...... 5–52 User ID...... 5–52 Security ID ...... 5–53 Default Menu ...... 5–53 RACF and eTrust CA-Top Secret Users ...... 5–53 eTrust CA-ACF2 Sites ...... 5–54 Profile...... 5–54

viii System Guide VTAM User Interface...... 5–54 VTAM Definitions...... 5–54 Sample JCL ...... 5–55 Starting the VTAM User Interface...... 5–55 Starting ...... 5–56 Accessing Using the VTAM User Interface ...... 5–56 Stopping the VTAM User Interface...... 5–56 Security Control...... 5–57 LOGON-CHECK=NO ...... 5–57 LOGON-CHECK=YES ...... 5–57 Customizing the Online User Interface ...... 5–57 User Interface Session Default Values ...... 5–58 Product Commands ...... 5–59 PF Key Sets ...... 5–60 Display Navigation...... 5–60 Customizing Navigation with Menu-Groups ...... 5–62 General Characteristics ...... 5–62 Menu-Groups...... 5–62 Menu-Group Syntax ...... 5–63 How the User Interfaces Interact with Menu-Groups ...... 5–65 Menu-Group Invocation ...... 5–65 Linking Requests...... 5–68 Selection...... 5–68 Navigation ...... 5–69 Context Passing ...... 5–69 Operating the Batch User Interface ...... 5–70 Extract Reports from Output Files ...... 5–70 Off-Hours Monitoring ...... 5–70 Reload the OBID Table ...... 5–71 Batch User Interface Requirements...... 5–71 Operational Overview ...... 5–71 Sample Jobs...... 5–71 Required DD Statements ...... 5–72 Required Parameter File ...... 5–72 Output Condition Codes ...... 5–73 Starting an IQL Request ...... 5–74 Stopping an IQL Request ...... 5–74 Security Control ...... 5–74

Contents ix Operating the Program Call (PC) Owner ...... 5–75 PC Owner JCL ...... 5–75 Batch Job Sample JCL ...... 5–75 JCL Explanation...... 5–76 Started Task Sample JCL ...... 5–77 JCL Explanation...... 5–77 STIMER Parameter ...... 5–78 PCSSID Parameter ...... 5–78 Running the PC Owner ...... 5–78 Keeping the PC Owner Task Active ...... 5–79 Terminating the PC Owner Program ...... 5–79 Restarting the PC Owner Program ...... 5–79 Troubleshooting ...... 5–79 System Condition Monitor (SCM) Customization ...... 5–80 Customizing the System Condition Monitor ...... 5–80 Color...... 5–80 Exception/Message Lifetime ...... 5–80 To Alter Cleanup Time ...... 5–81 To Alter Aging Time...... 5–81 Adding Additional Products ...... 5–81 IMODs Supplied for Additional Products...... 5–82 Before Modifying the Supplied IMODs ...... 5–83 Accessing an IMOD ...... 5–83 Installing Additional Products to the SCM...... 5–84 Step 1: Add a GSS Parameter ...... 5–84 Step 2: Modify $DB2CLNUP ...... 5–85 Step 3: Modify the Subsystem’s Definition IMOD ...... 5–85 Step 4: Modify the Subsystem’s Message IMOD ...... 5–87 Step 5: Modify the Subsystem’s Exception IMOD...... 5–87 Step 6: Recycle GSS...... 5–88 How the SCM Uses name.n Variables ...... 5–88

Chapter 6: Security Introduction to Security ...... 6–1 Options ...... 6–1 Security’s Role ...... 6–2 Controls ...... 6–2 Data Collector ...... 6–2 User Interface...... 6–3 In General ...... 6–3

x System Guide Flexibility ...... 6–3 Operation Overview ...... 6–4 Security Control ...... 6–4 User ID...... 6–4 Security ID ...... 6–4 Default Menu ...... 6–4 Profile...... 6–5 Security Exit Checking...... 6–5 Data Collector ...... 6–5 User Interface ...... 6–6 Refreshing SECURITY Parameters ...... 6–6 Security File Overview ...... 6–6 Components...... 6–6 Starter Member ...... 6–7 User ID Table ...... 6–13 ID List Syntax ...... 6–14 ID List Example ...... 6–14 How to Access the Security File...... 6–15 Online User Interface ...... 6–15 User Profiles...... 6–15 Sample User Profile ...... 6–16 Keywords ...... 6–17 Request Lists ...... 6–24 User Groups ...... 6–25 Syntax for Specifying User Groups ...... 6–26 Examples of Specifying User Groups ...... 6–26 Security File Validation ...... 6–27 Initialization Overview ...... 6–27 Data Collector Input Parameters...... 6–27 Security File ...... 6–28 Security User ID ...... 6–28 Authorization Issues for EXPLAIN and DB2 Commands ...... 6–28 How Authorizations are Supported ...... 6–28 TSO User Interface (non-RAF) ...... 6–29 VTAM User Interface and TSO User Interface (RAF) ...... 6–29 eTrust CA-ACF2 ...... 6–29 eTrust CA-Top Secret ...... 6–29 RACF ...... 6–30 None...... 6–30

Contents xi Chapter 7: Online History Online History Data Sets ...... 7–1 Data Types Stored...... 7–2 Online Interval Statistics History ...... 7–3 Online Thread Accounting History ...... 7–3 Controlling Online History ...... 7–3 Activating Online History Collection...... 7–4 Activating Online Interval Statistics Collection ...... 7–4 Activating Online Thread Accounting Collection...... 7–4 Collection of Online Child Threads ...... 7–5 Online History Data Set Size - Introduction...... 7–5 How Online History Files Are Allocated ...... 7–5 What Device Type Are You Using? ...... 7–6 Determining Data Set Sizes ...... 7–6 Online History Data Set Size - System Statistics ...... 7–7 Estimating the Record Sizes ...... 7–7 Average Record Size - STATS1 ...... 7–7 Average Record Size - STATS2 ...... 7–7 Computing Control Intervals...... 7–8 Maximum Record Sizes...... 7–9 Online History Data Set Size - Accounting...... 7–9 Estimating the Record Sizes ...... 7–9 Average Record Size - ACCTG ...... 7–10 Determining the Amount of Data to View Online...... 7–10 Computing Control Intervals...... 7–10 Maximum Record Sizes...... 7–11 Filtering Online Thread Accounting History...... 7–12 Filtering Strategies ...... 7–12 Activating Filtering ...... 7–13 Backing Up Online History ...... 7–14 SOURCE Library Member Modifications ...... 7–14

Chapter 8: Archiving DB2 Performance Data Flexibility in Archiving ...... 8–1 Types of Archive Data ...... 8–1 Loading Archive Data from Online History...... 8–2 Optimizing Your Archive Data ...... 8–4 Archive Data Sources ...... 8–4

xii System Guide Installing the Archive Component ...... 8–5 Requirement for Archiving...... 8–6 Migration Considerations ...... 8–6 Step 1: Create the Archive Database...... 8–6 Step 2: Obtain SMF Data from Online History...... 8–7 Step 3: Copy and Tailor the IDB2ARC Member ...... 8–8 Step 4: Automate the Unload Process ...... 8–8 General Recommendations ...... 8–9 Archiving Daily Data ...... 8–9 Archiving Detail Data ...... 8–9 Manipulating Archived Data ...... 8–9 Managing the Archive Environment ...... 8–10 Related Archive Component Members ...... 8–10

Chapter 9: Unicenter CA-24x7 Scheduler Components ...... 9–1 Security for Unicenter CA-24X7 ...... 9–2 Data Collector Cards for Unicenter CA-24X7...... 9–2 How the Scheduler Works ...... 9–2 Using Another Scheduler with the Unicenter CA-24X7 Batch Utility ...... 9–3 Scheduler Command Syntax ...... 9–3 Invoking the Scheduler ...... 9–3 Option A ...... 9–3 Option B ...... 9–4 A Note About FROM and TO ...... 9–4 Viewing Schedules Online ...... 9–6

Chapter 10: Unicenter Agent for DB2 Mainframe Requirements...... 10–1 Installation Steps to Add Agent ...... 10–1 Step 1: Modify System Initialization Parameters...... 10–2 Step 2: Modify and Add JCL to the Data Collector Procedure ...... 10–2 Step 3: Restart the Data Collector ...... 10–2

Contents xiii Chapter 11: Unicenter Performance Management Predictor Unicenter Performance Management Predictor Set Up...... 11–1 Step 1: Load The Product Definitions Into Pmp ...... 11–1 Product Definitions...... 11–1 Variable Definitions ...... 11–2 Sample Model Definitions...... 11–4 Step 2: Customize the Data Collector or Batch Report Writer Sysparms...... 11–4 Customizing Data to be Collected ...... 11–5 General Notes and Recommendations ...... 11–7

Appendix A: NSIGHTEX User Exit Operation ...... A–1 Exit Characteristics ...... A–1 Assembly and Link-Editing ...... A–2 Functions by Caller - Data Collector ...... A–2 INITUSER ...... A–2 ALLCALLS...... A–3 ALLREQS ...... A–3 STARTREQ...... A–3 Functions by Caller - TSO User Interface ...... A–3 INITTSO ...... A–4 EXITTSO ...... A–4 Functions by Caller - VTAM User Interface ...... A–4 LOGON...... A–4 LOGOFF ...... A–5 Functions by Caller - Batch User Interface ...... A–5 INITBAT ...... A–5 EXITBAT...... A–5 Modifying NSIGHTEX to Use Group Names Other Than INS* Names ...... A–6 Code Segments ...... A–6 Code segment 1 ...... A–6 Code segment 2 ...... A–7

xiv System Guide Appendix B: Data Collector Storage Data Collector Virtual Storage Requirements ...... B–1 Common Area Storage Requirements ...... B–2 For PCOWNER ...... B–2 For Data Collector...... B–3 For the User Interface...... B–4 Memory Planning ...... B–4 Factors ...... B–4 Output Buffers ...... B–4 Should They Be Larger? ...... B–5 SUMMARIZE Request Table Sizes...... B–5 Summary Table Entries ...... B–5 Entry Size ...... B–5 Allocation ...... B–6 Deallocation ...... B–6 To Check Table Sizes ...... B–6

Appendix C: Shadow Table for EXPLAIN Using Shadow Tables ...... C–1 Advantages ...... C–2 Disadvantages ...... C–2 EXPLAIN Plan ...... C–3 When Is EXPLAIN Using Shadow Tables? ...... C–4 Creating Shadow Tables ...... C–4 Keeping Shadow Tables Synchronized ...... C–5

Appendix D: Utilities OBID Translation Utility (IDB2OBI) ...... D–1 Requirements...... D–1 Format of the OBID Record ...... D–2 Db2ssidOBLD: OBID Translation JCL ...... D–3

Contents xv Load Statement Generator (NSIGHTRW) ...... D–3 Requirements...... D–4 Input and Output ...... D–4 Operation ...... D–4 Generated Statements ...... D–5 Input Parameter ...... D–5 IDB2LSJ: Load Statement Generator JCL...... D–5 JCL Explanation...... D–6 Request Case Converter (NALLCAPS) ...... D–7 Requirements...... D–7 IDB2UCJ: Request Converter JCL ...... D–8 JCL Explanation...... D–8 Change Members to Use New Request Library...... D–9 Online History Data Set Unload (IDB2UNLD) ...... D–9 Requirements...... D–10 IDUNLJCL: Online History Data Set Unload JCL...... D–10 JCL Explanation...... D–10 Dump ILOG to a Data Set (GSSIDUMP)...... D–13 Description ...... D–13 How It Works ...... D–13 Example ...... D–13 Unicenter CA-24X7 ...... D–14 Purpose ...... D–14 Sample JCL...... D–14 JCL Explanation...... D–15 The DEFAULTS Statement ...... D–15 Syntax ...... D–15 Example...... D–15 The SET Statement ...... D–16 Syntax ...... D–16 Example...... D–16 A Note About Commands and Command-Operands ...... D–16 SET Statement Commands and Operands ...... D–17

Index

xvi System Guide Chapter 1 Introduction

This chapter provides an overview of Unicenter CA-Insight Performance Monitor for DB2 for z/OS and OS/390 concepts and facilities. We highly recommend that you read this chapter before installing and using Unicenter CA-Insight or reading any other guide in the documentation set. The concepts described in this chapter are fundamental to your understanding of the power and flexibility of Unicenter CA-Insight.

Note: This guide assumes that all product components have been installed at your site. For more information about installing, see the Getting Started and the Installation Guide.

What Is Unicenter CA-Insight?

Unicenter CA-Insight is a software tool you use to monitor and tune your DB2 environment and to alert you to potential and ongoing performance problems and bottlenecks. It collects data from DB2 traces, the z/OS or OS/390 subsystem interface, and DB2 and z/OS or OS/390 control blocks. The staff in your data center is responsible for the performance and management of DB2 and they can use this data to effectively manage your DB2 environment.

You can view the following types of data online:

■ Real-time DB2 subsystem statistics (cumulative and delta).

■ Real-time application thread accounting.

■ Real-time system address space statistics for DB2 subsystem components and threads.

■ Real-time CICS RCT and IMS attachment and NATURAL statistics for application threads.

■ Online DB2 subsystem interval statistics history (at user-defined intervals).

■ Online thread accounting history.

■ Online DB2 console and utility phase change message history.

Introduction 1–1 What Is Unicenter CA-Insight?

■ Online DB2 subsystem, thread, SQL, and database exception history.

■ DB2 subsystem and application trace data.

■ SQL EXPLAIN data.

In addition, you can:

■ Archive online history and use as input for analyses, reports, and graphs.

■ Create batch reports.

■ Print the contents of the Unicenter CA-Insight screens.

■ Take actions, issue alerts, or start traces when exception thresholds have been exceeded.

Defining Areas of DB2 Responsibility

There are five distinct areas of DB2 responsibility in the typical MIS data center. People in these capacities uniquely manage various aspects of the DB2 environment. As such, they have specific monitoring needs. A unique primary menu structure is provided to support these needs as follows:

■ Application programmers are responsible for tuning DB2 applications and SQL before and after applications are put into production.

■ Auditors are security administrators or EDP Auditors responsible for implementing and managing corporate authorization procedures for DB2 data and application access.

■ Database administrators are responsible for insuring application, SQL, and data base performance and all other factors affecting the overall availability of DB2 subsystems.

■ Systems programmers are responsible for monitoring and tuning DB2 subsystems to balance MVS and DB2 resources to appropriate service levels.

■ Operators are responsible for quickly identifying critical problems and then taking appropriate action or notifying the appropriate people.

1–2 System Guide What Is Unicenter CA-Insight?

Benefits

Using Unicenter CA-Insight, you can:

■ Establish baseline statistics for a DB2 monitoring strategy.

■ Tune DB2 subsystem performance—You can use short-term DB2 subsystem history statistics intervals or logged exceptions to analyze performance deficiencies. You can also use DB2 subsystem trace data to tune specific DB2 resources such as: – Data sharing activity – Database I/O activity – Database scan activity – EDM pool activity – Lock suspensions – Logging activity

■ Monitor DB2 subsystem efficiency—Use the exception processor to detect when subsystem resource use has exceeded a limit you have set. You can view exceptions as they occur or examine a log of short-term exception history.

■ Diagnose DB2 application problems—Use several components to determine the cause of DB2 application performance problems or to tune an application as follows: – View real-time thread accounting data as the application is running – Trace an application’s execution – Analyze exceptions as they occur or examine a log of short-term exception history – EXPLAIN an application’s SQL as it is running or from its PLAN or PACKAGE – View online thread accounting history data after the application has terminated

■ Tune DB2 application performance—To tune application performance, you can: – Define and monitor performance thresholds using the Unicenter CA-Insight exception processor – Analyze an application’s DB2 access path using SQL EXPLAIN data – Analyze archived application accounting data to identify performance trends over time

Introduction 1–3 What Is Unicenter CA-Insight?

■ Perform stress test analysis—Use subsystem statistics and thread accounting data to analyze the performance of new or modified applications that are stressed tested prior to being migrated to your production environment.

■ Perform capacity planning—You can forecast DB2 subsystem resource use by comparing long-term and current DB2 subsystem history statistics. Using archived data that has been loaded into DB2 tables you can generate reports and graphs to perform long-term trend analyses.

Required Components

You can configure Unicenter CA-Insight to manage your entire DB2 environment whether you have a single DB2 subsystem on one MVS image or multiple DB2 subsystems on multiple MVS images. You use a combination of required and optional components to configure Unicenter CA-Insight to your DB2 environment.

The required components are describe in this section.

Data Collector

The data collector is the heart of Unicenter CA-Insight. Its primary function is to process IQL request instructions used to create reports and online displays. Reports can be viewed from the user interface or written to a report file for printing later. The data collector creates a report only when the corresponding IQL request is active.

The data collector is the only Unicenter CA-Insight component that is directly connected to DB2. Through this connection, it collects information about the DB2 subsystem, DB2 threads, DB2 users, DB2 databases, the IRLM and supporting MVS statistics.

Unicenter CA-Insight sampling intervals allow the data collector to report on real-time and recent DB2 subsystem and thread status, as well as, real-time and recent subsystem, thread, SQL, and database exceptions. Also, Unicenter CA-Insight automatically and efficiently obtains the trace data needed to report on recent thread and subsystem events.

You start one data collector for each DB2 subsystem you want to monitor. The data collector can run as a submitted job, but because it is active for long periods of time, you should run it as a started task.

Each data collector can support any number of interactive users running under the TSO or the VTAM user interface, “locally” (on the same MVS image as the data collector) or “remotely” (on a different MVS image).

1–4 System Guide What Is Unicenter CA-Insight?

PC Owner

One PC Owner task is required per MVS image. The PC Owner task “owns” the routines used for cross memory communications between users and each data collector monitoring a DB2 subsystem. PC stands for program call in reference to the Cross Memory Services (CMS) instruction. The PC Owner task creates an index that provides access to all Unicenter CA-Insight CMS service routines.

Query Language (IQL) Request

An IQL request is a set of instructions stored as a member of a PDS library. These instructions (as interpreted by the data collector) determine the format of the report or online display, its destination (terminal display, printed report, or data file), and what DB2 data needs to be presented. Unicenter CA-Insight is distributed with enough IQL requests to satisfy most, if not all, of your reporting needs. If you have special reporting requirements, you can use the Query Language to easily modify an existing request or write your own.

TSO User Interface

The Unicenter CA-Insight TSO user interface provides you with the ability to view online reports created by the data collector, manipulate IQL requests, view DB2 console and utility phase change messages, and issue DB2 commands. It also lets you create and change IQL requests using the ISPF editor.

Using the TSO user interface, you can select reports by menu, by command, or by zooming, and can print a report being viewed using a single function key.

You can off-load Unicenter CA-Insight data files or invoke unattended data collection by using the batch user interface to start and stop IQL requests from a batch job.

Batch Report Writer

The Unicenter CA-Insight Batch Report Writer lets you process a GTF or SMF DB2 trace data file in batch mode. You can also use the Batch Report Writer to process archived Unicenter CA-Insight History files. Like the data collector, the Batch Report Writer uses IQL requests to process trace data or an archived online History file and produce the desired reports. The batch reports distributed with Unicenter CA-Insight have been designed to reproduce many of the reports produced by DB2PM in order to simplify your DB2 maintenance.

Introduction 1–5 What Is Unicenter CA-Insight?

Online History

Unicenter CA-Insight Online History lets you view recent thread activity or intervals of subsystem performance data online.

The Online History files are dual VSAM KSDS data sets that contain the most recent DB2 data collected and stored by the data collector. The data collector accesses Online History to satisfy IQL requests for DB2 statistics interval and thread accounting history.

Each Online History file is actually an A/B pair of data sets that wrap when full. When one data set in a pair becomes full, the data collector switches the storing of data to the other data set of the pair. Data on the first data set remains available for retrieval until the second data set becomes full and the data collector starts writing over the first data set.

Note: Since the collection of Online History is optional but highly recommended, it is included as part of the Basic Installation. See the “Online History” chapter in this guide for information about disabling the Online History component.

The Online History data sets are used to store several types of data. Each log pair holds specific DB2 data in SMF format, as illustrated in the following table:

Type of DB2 Data Record Type Data Set Pair Qualifier DB2 System Services statistics SMF 100 type 0 HSTSTATA/B DB2 Database Services statistics SMF 100 type 0 HSTSTATA/B DB2 Thread Accounting data SMF 101 HSTACCTA/B

Optional Components

The optional components are described in this section.

Global Subsystem (GSS)

The Global Subsystem (GSS) is a common component of those Computer Associates products that require integration with other Computer Associates products. The GSS contains components such as the Message Handler, a data logging facility, and an extensible REXX automation facility.

1–6 System Guide What Is Unicenter CA-Insight?

The GSS Message Handler collects and logs DB2 console messages from all selected DB2 subsystems active on the MVS image and, optionally, messages from Unicenter CA-Insight data collectors. The GSS data logging facility is used by Unicenter CA-Insight data collectors to store exception and DB2 utility phase change messages.

The GSS logs can be accessed by Unicenter CA-Insight data collectors allowing the operations staff, DBAs and system programmers to review significant DB2 and Unicenter CA-Insight operational events without scrolling through hundreds of unrelated SYSLOG messages.

You must install and activate the GSS, if your data center wants to implement any of the following optional Unicenter CA-Insight features:

■ Collection, logging, and playback of DB2 console messages.

■ Logging and playback of exception messages.

■ Logging and playback of DB2 utility phase change messages.

■ Invocation of REXX automated operations routines from IQL requests and exceptions.

■ Installation and use of System Condition Monitor.

VTAM User Interface

The Unicenter CA-Insight VTAM user interface provides users with the ability to view online reports created by the data collector, manipulate IQL requests, view DB2 console and utility phase change messages, and issue DB2 commands.

Using the VTAM user interface, you can select reports by menu, by command, or by zooming, and can print a report being viewed using a single function key.

Remote Access Facility (RAF)

The Remote Access Facility (RAF) lets users connect to remote data collectors without having to logon to the system where those data collectors reside. RAF employs VTAM definitions on both the local and remote MVS images but does not require the VTAM user interface.

Both the TSO and VTAM user interfaces can take advantage of the RAF connection. With RAF enabled, the Unicenter CA-Insight PICK panel lists the RAF-connected data collectors as being REMOTE and ACTIVE.

Introduction 1–7 What Is Unicenter CA-Insight?

NATURAL for DB2 Support

Support for NATURAL for DB2 exposes basic NATURAL information necessary to determine which NATURAL programs and statements are accessing DB2. Without this additional information, NATURAL appears to be one program to DB2.

Unicenter CA-Insight reports on the following NATURAL items:

■ Library name

■ Program name

■ Statement number

These items have been defined as part of the Unicenter CA-Insight common header and are therefore available for use in any user-written IQL request that is thread-based except requests that use the ACCT record.

System Condition Monitor (SCM)

The SCM displays the status of MVS system components throughout your data center’s network. SCM accomplishes this by using the GSS REXX automation facility to access, summarize, and report on DB2, MVS, and CICS exception information stored in GSS by products participating in SCM data collection. There must be one GSS on each MVS image. Unicenter CA-Insight can be activated to send exception data to GSS.

Unicenter CA-24X7

24x7 support lets you:

■ Dynamically change DB2’s startup parameters (ZPARMS).

■ Cancel DB2 threads.

■ Add or delete active log data sets.

■ Free database page sets of all users.

■ Refresh user exit routines.

Contact your Computer Associates Account Manager for more information about Unicenter CA-24X7.

1–8 System Guide What Is Unicenter CA-Insight?

Unicenter Agent for DB2

The Unicenter Agent for DB2 can be used from Unicenter CA-Insight to interface with Unicenter to report on the performance of the monitored DB2 subsystem. This data can be used by Unicenter to report on subsystem status, and to respond to exception events within DB2. The Unicenter Agent for DB2 is also available separately from Unicenter CA-Insight, but when operated in this manner, the exception information from Unicenter CA-Insight is not available to Unicenter.

Contact your Computer Associates Account Manager for more information about the Unicenter Agent for DB2 option.

Unicenter Performance Management Predictor (PMP)

Unicenter CA-Insight can be used to feed data to Unicenter Performance Management Predictor (PMP). Unicenter PMP is a separate tool offered by Computer Associates that uses Neugent technology to analyze current and past performance data to predict when problems might occur. See the “Unicenter Performance Management Predictor”chapter for details on how to set up the interface and how Unicenter CA-Insight can be used to feed data to PMP.

Contact your Computer Associates Account Manager for more information about the Unicenter PMP product offering.

Optional History Components

In addition to the optional components described earlier, the following two components can also be installed:

Online History Archiver

When one data set in an Online History data set pair is full and the data collector switches to the other data set of the pair, an archive task can be dynamically invoked to unload Online History to a sequential file. This capability lets you collect a continuous stream of DB2 performance data while running a non-stop DB2 environment.

If you choose not to implement automatic archiving, Online History data is lost when a data set becomes the active data set of the pair.

For a discussion of the activation and use of this component, see the “Online History“ chapter in this guide.

Introduction 1–9 Typical Configurations

DB2 Performance Data Archive

Unicenter CA-Insight provides you with the option to automatically store summarized and detail statistics and accounting data in DB2 tables. This data can be used to generate reports or GDDM graphs that compare application and subsystem performance data for different time periods.

Detail data and daily summaries of DB2 subsystem statistics and thread accounting records are stored in eight DB2 tables as follows:

■ For base data: – Thread accounting detail – Thread accounting summarized by day – Subsystem statistics detail – Subsystem statistics summarized by day

■ For distributed data: – Thread accounting detail by location – Thread accounting summarized by day and location – Subsystem statistics detail by location – Subsystem statistics summarized by day and location

For a description of the installation and use of this component, see the “Archiving DB2 Performance Data” chapter in this guide.

Typical Configurations

The following illustrates how you can configure the components of Unicenter CA-Insight in different DB2 and MVS environments, from a single DB2 subsystem environment to a very complex DB2 environment spanning multiple MVS images. The Unicenter CA-Insight-related components are shown in the shaded boxes.

1–10 System Guide Typical Configurations

One DB2 Subsystem, One MVS Image

Multiple DB2 Subsystems, One MVS Image

Introduction 1–11 Typical Configurations

Multiple DB2 Subsystems, Multiple MVS Images

1–12 System Guide Chapter 2 Verifying the Basic Installation

This chapter will assist you in verifying the installation of the batch and online components. You first execute the Batch Report Writer and verify the creation of reports. You then run the PC Owner and data collector jobs, log on to the TSO user interface and begin using the online features to view the single “local” DB2 subsystem.

While the PC Owner and data collector components are run here as batch jobs, in a normal environment they would be run as started tasks; for further information, see Installing Components as Started Tasks in the “Beyond the Basic Installation” chapter.

Verify Batch Reporting

During installation, you created a sample GTF data set. This data set is used to verify that the Batch Report Writer functions properly. The Batch Report Writer uses IQL requests to produce printed reports similar to those available online.

To verify batch reporting, execute job IDB2RWJ now and examine the sample reports. The operation of the Report Writer, and an explanation of the reports are described in the Unicenter CA-Insight Batch Report Reference. Note that several of the requests might not produce reports.

You can produce other batch reports by specifying different request members in the DBGIN DD statement, or by providing your own IQL request members from some other library (see the Unicenter CA-Insight Writing Requests guide for information about how to write IQL requests).

Verifying the Basic Installation 2–1 Verify Online Access

Verify Online Access

Use the following steps to start a monitoring environment and verify that the user interface and the data collector are communicating: 1. Make sure that the DB2 subsystem you plan to monitor during Unicenter CA-Insight verification is active. 2. Submit member IDB2PCJ to start the PC owner. The PC owner is running properly when message DBG39046I is generated. 3. Submit member db2ssidDCJ to start the data collector. Allow up to five minutes for the data collector to initialize. The data collector is running properly when message DBG39044I is generated. If you are using the online history component, message DBG21002I will be also be displayed. 4. When both the PC owner and the data collector are active, use one of the following methods to log on to Unicenter CA-Insight:

■ Select option IS from the DB2 Products Main Menu.

■ Execute the INSIGHT CLIST directly from ISPF. The Systems Menu screen appears as follows:

Menu Print Tools Help CA-Insight SE19257

Systems Systems Menu

DB2 System 1 System Statistics 2 System History 3 CICS / IMS Attachments 4 Messages

Threads 5 Active Threads 6 Thread History 7 Explain 8 User Started Requests 9 Exception Monitor 0 Permanent Exception Definitions

2–2 System Guide Verify Online Reporting

5. From the Systems Menu, select the PickDB2 command or PF key to view the status of the data collector. The Pick a DB2 Subsystem panel appears:

Menu Print Tools Help CA-Insight SE19257 DBV3 Location GCOIDB2DEVDBV3

Pick Pick a DB2 Subsystem

Y Y Statistics, N No Statistics Location SSID Type System Status ------DB2LOCATION1 DB23 LOCAL MVSB1 Active DB2LOCATION2 YYYY Inactive

This panel lists each of the locations specified in the APPLS statement in the APPLS member in the SOURCE library. This illustration shows the following: DB2LOCATION1 The location name you supplied during the post install part 2. If the necessary Unicenter CA-Insight and DB2 components are in place and functioning, the Status field to the right of your SSID will indicate Active. The currently selected location is highlighted. DB2LOCATION2 The location name you supplied during the post install part 2 for a second DB2 subsystem. If the necessary Unicenter CA-Insight and DB2 components are in place and functioning, the Status field will indicate Active if the data collector is up, and Inactive if the data collector is down. 6. When you have successfully completed this verification step, you are ready to begin data collection and online reporting. Use the End command or PF key to return to the Systems Menu. Continue to the next step, Verify Online Reporting.

Verify Online Reporting

This section describes several important navigation features and how to verify user interface reporting. Detailed information about the online systems can be found in the Unicenter CA-Insight User Guide.

Verifying the Basic Installation 2–3 Verify Online Reporting

Navigation Features

From the Systems Menu, use the M command to display a primary menu list:

■ Systems

■ Applications

■ Auditors

■ DBAs

■ Operators

Each of these menus is designed for the specific types of jobs a typical data center employs to manage DB2 (see the “Introduction” chapter for more information). You can display these menus by selecting them from the pull-down list or using the following commands on the command line to directly invoke a menu:

■ SY—Displays the Systems menu.

■ AP—Displays the Applications menu.

■ AU—Displays the Auditors menu.

■ DB—Displays the DBAs menu.

■ OP—Displays the operators menu.

Use the Exit option or press PF3 to clear the Menu window. Note the Print, and Tools and Help options windows on the same menu bar as the Menu option.

Verify User Interface Reporting

To verify user interface reporting: 1. From the Systems menu, enter 1 or =1 (TSO navigation is supported) on the command line. The System Snapshot panel should appear as follows:

Menu Print Tools Help CA-Insight SE19257 DBVx S018 1 SnapShot 2 Buffer Pool 3 EDM Pool 4 Logs 5 Threads 6 More...

R/SYSSTATS System Snapshot - 30 seconds Row 1-14 of 22 Delta EXCEPTIONS Crit Warn Info BUFFERS EDM POOL Subsystem 6 1 1 Warnings 1 Free Pg 799 % Total 79.9 Database 0 0 0 Act Pools 8 DBD Lds 0 % Rqsts 0.0 Applicatn 0 0 0 % Act Pgs 0.6 CT Lds 0 % Rqsts 0.0 Getpages 6071 PT Lds 0 % Rqsts 0.0 Sync Rds 0 LIMITS Count % Max Read Eff ****** LOCKING LOGGING Users 10 14 Buf Updts 0 Suspend 0 Dlyd Wrts 0 TSO 4 10 Pg Writes 0 Escalate 0 Arch Read 0 Batch 6 30 Write I/O 0 Timeout 0 Warnings 0 DDF Actv 0 0 Deadlock 0 DDF Inac 0 0 RID POOL Datasets 80 4 Failures 0

2–4 System Guide Verify Online Reporting

This panel is a real-time display that presents an overview of the health of the DB2 subsystem selected from the Pick list. Note the 6 view bar options on the third line. These options can be entered on the Command line to view detailed statistics that support the snapshot summary. Many components have view bars that serve a similar purpose to the one on this panel. Also, note the Delta field on the right adjacent to the panel title. The System Snapshot panel defaults to displaying system statistics accumulated during the collection interval (the default interval is 30 seconds). You can enter Accum in this field to display the system statistics accumulated since DB2 was started. Other components have a function like the Delta/Accum field for controlling the data that displays. 2. Enter 2 on the Command line or tab up to the view bar and enter 2. Press Enter. The Buffer Pool List panel should be displayed. This panel displays a list of active Buffer Pools and their activity for the past 30 seconds (the interval). 3. Tab to one of the buffer pools and press Enter. The Buffer Pool Exception Counter panel appears.

Menu Print Tools Help CA-Insight SE19257 DBV3 S018 1 Exception Counters 2 Thresholds 3 Read/Write 4 Workfiles

R/BUFEXCPS BP Exception Counters - 30 Seconds Delta BUFFER POOL BP0 VP HP Pct Count Target Size (buffers). 2000 0 Data Management...... 95 0 Allocated Size...... 2000 0 Seq Prefetch Disabled 90 0 Current Active Buffers 0 0 Buffer Pool Full...... 0 Percent Active Buffers 0.0 0.0 Expansion Failures...... 0 Read Write DFHSM Recall Timeouts...... 0 I/Os with Paging...... 0 0 Workfile Prefetch Aborted...... 0 Unavailable I/O Engine. 0 0 Sync Reads for Sequential Access 0 Non-ADMF HP Pg Failures 0 0 Conditional Getpage Failures.... 0 ADMF HP Page Failures.. 0 0 Parallel I/O Degrees Reduced.... 0 Reduced Degree Parallel I/Os.... 0 Wrkfl Not Created - No Buffer.. 0 Average Degree Reduction...... 0.0 Sort Wrkfls Denied - No Buffer. 0 Prefetch Quantity Reduced to 1/2 0 Inefficient Sorts - No Buffer.. 0 Prefetch Quantity Reduced to 1/4 0

The view bar option you are currently viewing is highlighted. You can see other detailed Buffer Pool statistics by typing the appropriate option on the view bar or Command line and pressing Enter. 4. Enter SYSTEMS on the Command line and press Enter to return to the Systems Menu.

You have successfully verified that Unicenter CA-Insight has been installed correctly and is collecting data.

Verifying the Basic Installation 2–5

Chapter 3 Beyond the Basic Installation

Many data centers will want components to run as started tasks or to archive DB2 statistics and accounting records for historical reporting purposes.

With Unicenter CA-Insight, you can:

■ Install product components as started tasks

■ Schedule high-level DB2 reports using SMF data

■ Schedule detailed DB2 reports using SMF data

■ Manage data collector DASD output

■ Implement the CICS monitoring facility

This chapter outlines changes you must make to support these capabilities.

Installing Components as Started Tasks

The PC owner and data collector are long running jobs. Most installations prefer to run them as MVS started tasks.

Follow these steps to install product components as MVS started tasks: 1. Prepare Unicenter CA-Insight PROCs. The started task procedures should have already been created in your PROCLIB data set as part of the post install process. If they are not, then move SOURCE members IDB2PCS and db2ssidDCS to your PROCLIB data set. 2. Set data collector MVS dispatching priority. The dispatching priority specified for the data collector (assigned in MVS Performance Group parameters) must be set higher than DB2 or any connections to DB2 in order for Unicenter CA-Insight to collect accurate data.

Beyond the Basic Installation 3–1 Installing Components as Started Tasks

We recommend the following dispatch priority (from highest to lowest):

■ IRLM

■ Unicenter CA-Insight data collector

■ DB2 address spaces and associated connections The data collector should have a higher priority than DB2 to prevent the data collector from being swapped out while DB2 is active. If this were to happen, DB2 trace records could be lost. 3. Ensure the data collector has the required DB2 authorizations. This should have been done as part of the post install. If it was not, then you need to edit the SOURCE member IDGRANT and execute it under SPUFI (or similar dynamic SQL program) to grant the required privileges to the authorization ID that the data collector will be running under. If the user ID for the data collector started task is not obvious at your installation, use the following technique to discover its value:

■ Stop the data collector batch job (db2ssidDCJ) if it is still running.

■ Edit and submit SOURCE library member IDGRANT using SPUFI to temporarily GRANT the required privileges to PUBLIC. This step can fail in systems where the default started task authorization is invalid for DB2. In this case, use the external security package to change the authorization for the data collector started task, and do the following:

■ Make sure that the PC Owner Task is still running.

■ Start the data collector started task (db2ssidIDB2 or db2ssidDCS, by default).

■ Use the Unicenter CA-Insight user interface Active Threads display (select 5 from the Systems Menu or use the DISPLAY THRDACTV command) to find the three data collector threads. The Corr ID entries will be the data collector started task PROC name. Note the Auth ID assigned to the data collector threads.

■ Terminate the data collector task.

■ Modify and SOURCE library member IDGRANT using SPUFI to grant privileges to the auth ID noted in the previous Step.

■ Restart the data collector started task. 4. Change eTrust CA-Top Secret. If your security package is eTrust CA-Top Secret, you must instruct eTrust CA-Top Secret to permit RACROUTE calls from the data collector to defined secondary authorization IDs for the EXPLAIN and DB2 Command functions.

3–2 System Guide DB2 Commands and EXPLAIN

DB2 Commands and EXPLAIN

In eTrust CA-Top Secret, the data collector abnormally terminates if it has not been given the authority to perform a function (by eTrust CA-Top Secret). The Security file user profiles distributed with Unicenter CA-Insight are coded with EXPLAIN=TSO and DB2-COMMAND=TSO (for descriptions of these parameters, see the “Security” chapter). These permit access to functions from TSO on the same MVS. However, TSO users accessing through RAF are blocked from using EXPLAIN functions with the data collector until the security environment is corrected.

To authorize the data collector to eTrust CA-Top Secret, follow these steps: 1. Use eTrust CA-Top Secret to rename the master facility TSS MODIFY (FAC(USER3=NAME=INSIGHT) TSS MODIFY (FAC(INSIGHT=MODE=FAIL) TSS MODIFY (FAC(INSIGHT=PGM=NAI) TSS MODIFY (FAC(INSIGHT=SUAS) TSS MODIFY (FAC(INSIGHT=AUTHINIT) TSS MODIFY (FAC(INSIGHT=SIGNs) TSS MODIFY (FAC(INSIGHT=NOLUMSG)) 2. Add the master facility to an eTrust CA-Top Secret ACID for the data collector procedure. TSS ADD(profile-name) FAC(INSIGHT) 3. Create the eTrust CA-Top Secret ACID for the data collector procedure. TSS CRE(proc-name) TYPE(USER) PASSWORD(NOPSWS.0) NAME(‘INSIGHT DATACOLL’) PROF(profile-name) DEPT(department) MASTFAC(INSIGHT) 4. Assign the ACID to the data collector started task. TSS ADD(STC) PROC(proc-name) ACID(acid-name)

EXPLAIN and DSN3AUTH

If the DSN3AUTH routine is the standard exit provided by your security package vendor, DB2 primary and secondary authorization IDs will function as expected.

However, if the DSN3AUTH routine is not as provided by your security package vendor, but the following conditions are met, the DB2 primary and secondary authorization IDs will function as expected. DSN3AUTH should not modify the AIDLPRIM field passed to it by DB2.

Beyond the Basic Installation 3–3 Scheduling High-Level DB2 Reports Using SMF Data

In addition, the secondary authorization ID should be set as follows:

Security Package Based On eTrust CA-ACF2 AIDLPRIM IBM RACF Connect groups associated with the ACEE of the data collector eTrust CA-Top Secret The IBM groups associated with the ACEE of the data collector

Scheduling High-Level DB2 Reports Using SMF Data

Many data centers require that daily or weekly reports be generated to review DB2 or application performance. You can pass the Unicenter CA-Insight Batch Report Writer SMF DB2 subsystem statistics and thread accounting data (such as SMF 100 and 101 records) on a periodic basis to satisfy this goal.

To produce reports utilizing statistics and accounting data, you must ensure DB2 traces are executing and writing SMF data to a specific destination for collection. The destination can be to SMF where data is written to SYS1.MANx data sets or to an OPn buffer that Unicenter CA-Insight uses to collect data. Reports can then be generated using data extracted from SMF data sets or from data archived from Unicenter CA-Insight Online History.

From SMF Data Sets

You can use DB2 SMF data written to your data center’s SMF data sets. This is the preferred approach if you already use DB2 SMF records for other purposes, such as chargeback, or you will not be running Unicenter CA-Insight non-stop.

3–4 System Guide Scheduling Detailed DB2 Reports using SMF Data

To use data from the SMF data sets, you must: 1. Determine your data center’s cycle for collecting historical SMF data to decide how to schedule the Batch Report Writer. 2. Instruct DB2 to collect and write the SMF data required for Unicenter CA-Insight’s standard set of batch statistics and accounting reports. Each time the DB2 subsystem starts you must ensure that the proper trace data is collected by issuing the following commands: -START TRACE(STAT) DEST(SMF) -START TRACE(ACCTG) DEST(SMF) CLASS(1,2,3,7,8) Or by setting the DB2 initialization parameters (DSNZPARM) to automatically start these traces. Classes 7 and 8 are only applicable to DB2 Version 3 or later subsystems for package level accounting.

From Online History

You can use DB2 SMF data written to Unicenter CA-Insight’s Online History. This is the preferred approach if you are not currently using DB2 SMF from another source and will be running Unicenter CA-Insight in non-stop mode.

To use data from the Unicenter CA-Insight online history logs, you must:

■ Determine how often (daily or weekly) you will schedule the Batch Report Writer.

■ Customize the Unicenter CA-Insight environment to archive online history data on a schedule that coincides with your Batch Report Writer runs.

Scheduling Detailed DB2 Reports using SMF Data

There are specific batch reports you can run for more detailed tuning and problem resolution tasks. These reports deal specifically with detailed data manager or SQL event data. These reports are described in this table.

Performance Report Description Trace Class BTCONTSM Summary of lock timeouts and deadlocks 6 BTEDMSUM EDM I/O summary report 4 BTLKCONT Lock timeouts and deadlocks 6 BTPLIOSM I/O summary by database, page set, and plan 4 BTPSIOSM I/O summary by database and page set 4

Beyond the Basic Installation 3–5 Managing Data Collector DASD Output

Performance Report Description Trace Class BTRECTRC Detail trace of DB2 activity 1-14, 16, 17 BTSCNSM1 Summary of pagesets scanned by 8 authorization ID, PLAN and Correlation ID BTSQLSM1 Trace of SQL text and mini-EXPLAINS 3, 6 BTSQLTRL Detailed trace of SQL statements 1, 2, 3, 4, 6, 8, 10, 16 BTSUSPSM Lock suspension summary 6 BTSUSPTR Lock suspension details 6

You can instruct DB2 to collect the performance trace data needed to produce these reports or you can run the required Unicenter CA-Insight requests to produce the reports online, directing the reports to Unicenter CA-Insight print files. The latter approach is preferred if you do not collect DB2 SMF performance trace data for other purposes.

Enter the following command to ensure that DB2 collects the performance trace data required for the report you want to generate: -START TRACE(PERFM) DEST(SMF) CLASS(x,x,x)

Where x is the trace class specific to the report you are interested in.

For more information about these requests, see the Unicenter CA-Insight Batch Report Reference.

Managing Data Collector DASD Output

Monitoring DB2 in your data center can require the collection of specific historical data. If you determined that you need to collect data for historical reporting, you can write a specific IQL request to write this data to a file. You use the OUTFILE statement in the Unicenter CA-Insight IQL request to specify where the request-specific data is to be written. You can use one of the following techniques to archive the data.

3–6 System Guide Managing Data Collector DASD Output

Archiving by Generation Data Group (GDG)

Unicenter CA-Insight supports specification of GDGs in IQL. To accomplish this using a GDG for an OUTFILE, you can specify the statement as: OUTFILE(DS(‘x.y.z(+1)’)NEW)

This creates a new GDG file every time the request is started. The request can be stopped and then started again to create a new GDG data set.

Note: The GDG model definition must exist in the catalog.

Archiving without Generation Data Groups

The following technique does not use GDGs and so does not require that the data collector to be stopped and restarted.

■ Pre-allocate an outfile (specifications can be found in the “Output Files” chapter in the Unicenter CA-Insight Writing Requests guide).

■ Ensure that the OUTFILE statement in the IQL request specifies an explicit data set name has a disposition of SHR. For example: OUTFILE (DSN(‘TEST01’) SHR)

■ Build a JCL job stream that performs the following steps: – Using the batch user interface (described in Operation Overview), stop the IQL request in the data collector that uses the data set referenced in the OUTFILE statement. The data collector will then stop writing to the data set and close it. – Copy the data set to a historical data set with DISP=MOD to append the data to the end of that file. – Initialize the data set using IEBGENER (the DD statement for SYSUT1 should refer to DUMMY). – Use the batch user interface to issue a START command to restart the IQL request within the data collector.

■ Schedule the job stream for nightly or weekly execution.

Beyond the Basic Installation 3–7 Implementing the CICS Monitoring Facility

Archiving DB2 History to the History Database

Unicenter CA-Insight provides several ways to load DB2 SMF statistics and accounting data into DB2 tables. You can then use the flexibility and power of SQL from QMF or SPUFI to generate DB2 performance reports. The DB2 SMF data can be loaded from system SMF files or from the Unicenter CA-Insight Online History data sets.

All of these procedures can be found in the “Archiving DB2 Performance Data” chapter.

Implementing the CICS Monitoring Facility

To get values in the new CICS fields in the THRDDETL display, the CICS Monitoring Facility (CMF) has to be activated, as described in the following steps.

The CICS fields with the labels in the request of Elapsed, Suspend, CPU, I/O Wait, and Dispatch are blank or 0 if the CICS Monitor facility in CICS is not activated. All the other CICS fields are filled in from other CICS control blocks. If all the CICS fields are blank, the ! on each line means to not display this line.

Step 1: Create a Monitor Control Table

Provide an assembled Monitor Control Table (MCT), which has entries provided for both the Accounting class and the Performance Monitoring class. A sample table is shown here: MCTAW TITLE ‘DFHMCTAW CICS/MVS 2.1.1. MCT FOR CMF’ PRINT ON,GEN MCTAW DFHMCT TYPE=INITIAL,STARTER=YES,SUFFIX=AW DFHMCT TYPE=RECORD, X CLASS=ACCOUNT, X DATASET=2, X FREQ=0, X MAXBUF=2048 DFHMCT TYPE=RECORD, X CLASS=PERFORM, X DATASET=2, X FREQ=0, X MAXBUF=2048 X FREQ=YES DFHMCT TYPE=FINAL END

3–8 System Guide Implementing the CICS Monitoring Facility

This sample uses the CICS journal data sets whose ID is 2 (DATASET=2) to write the collected monitor records. Unicenter CA-Insight does not use the records, but they are a result of the monitoring that is started to have CICS collect the data Unicenter CA-Insight uses to display THRDDETL.

MCT=AW should be specified for the previous sample table in the SIT, or as an SIT override at CICS startup.

Step 2: Define the Journal Control Table

A Journal Control Table (JCT) must define the journal referenced in the MCT as output from the monitoring facility. The referenced JCT entry must specify the option FORMAT=SMF and have a JFILED parameter the same as specified in the MCT. A sample of the JCT corresponding to the previous MCT is shown here: JCT TITLE ‘DFHJCTA1 CICS/MVS 2.1.1 JCT FOR CMF’ PRINT ON,NOGEN JCTA1 DFHJCT TYPE=INITIAL,STARTER=YES,SUFFIX=A1 DFHJ01 DFHJCT TYPE=ENTRY, X JFILEID=SYSTEM, X BUFSIZE=4096, X BUFSUV=3584, X JTYPE=DISK2, DFHJ01A AND DFHJ01B X OPEN=INITIAL, X JOUROPT=(CRUCIAL,INPUT,RETRY) DFHJ02 DFHJCT TYPE=ENTRY, X JFILEID=2, X FORMAT=SMF, X BUFSIZE=6144, X BUFSUV=4096, X JTYPE=DISK2, DFHJ02A AND DFHJ02B X OPEN=INITIAL, X JOUROPT=(RETRY) DFHJCT TYPE=FINAL END

The second DFHJCT entry is the one that describes the journal associated with the MCT. It is defined as a set of dual data sets which will switch back and forth as filled. This probably should be monitored as to size and usage as described in the CICS documentation for performance reasons.

For the previous JCT, JCT=A1 should be specified in the SIT table or as a SIT override at CICS Startup.

Step 3: Linkedit the CICS Type 2 SVC

Since the option CPU=YES was specified for the performance class entry in the MCT, you must linkedit the CICS Type 2 SVC bootstrap module (DHCSVC) into the MVS nucleus as specified in the CICS documentation.

Beyond the Basic Installation 3–9 Implementing the CICS Monitoring Facility

Step 4: Allocate Journal Data Sets

Allocate and initialize the two journal data sets for Journal 2 as specified in the MCT and JCT. Execute the CICS utility DFHJCJFP to allocate and initialize each journal data set. This could be a job step in the CICS procedure to initialize each time CICS is started, since Unicenter CA-Insight does not use the data from these journals.

Add the two new required DD statements to the CICS execution step to allocate the two journal data sets. For the previous sample, the ddnames would be DFHJ02A and DFHJ02B.

Step 5: Update the SIT Table

Specify the MCT and JCT in the SIT table, or as SIT table overrides at CICS startup. You should also specify that monitoring is to be activated by specifying MONITOR=(ACC,PER) in the SIT table or as an override.

Turning Monitoring On and Off

If you see blanks as values in the appropriate fields in THRDDETL, then monitoring has been turned off. To turn monitoring on, use this form of the CSST transaction: CSST MONITOR,ON=(ACC,PER)

To turn monitoring off, use this form of the CSST transaction: CSST MONITOR,OFF=(ACC,PER)

3–10 System Guide Data Sharing Implementation Considerations

Data Sharing Implementation Considerations

Unicenter CA-Insight supports DB2 data sharing by providing several displays where data from all the members of the DB2 data sharing group displays on the same screen. This data includes general statistics data, selected thread data, and lock contention data. To enable this data to be displayed, and to be able to jump to the appropriate data collector, the Unicenter CA-Insight environment must be set up properly. Following are the considerations and steps that need to be accomplished to fully enable this environment.

Each member of the DB2 data sharing group must be monitored by its own data collector. This, of course, has always been true with Unicenter CA-Insight. A Unicenter CA-Insight PC address space must also be started on each MVS image on which a data collector is located. Unicenter CA-Insight also creates its own Sysplex data sharing group which includes all the data collectors which are monitoring the corresponding DB2 data sharing group members.

Each data collector must be enabled for data sharing by specifying the keyword DATA-SHARING=YES in the SYSPARMS. The Unicenter CA-Insight data sharing group name can be specified by naming the group in the DC-GROUP= parameter of SYSPARMS. The data collector group name will default to XDBGDCxx if not specified, where xx is the Unicenter CA-Insight release number. Any group name must be unique in the sysplex, so if an installation has more than one DB2 data sharing group in the sysplex, unique data collector group names must also be specified for each data sharing group. The data collector group name can also be overridden by specifying the name in the DCGRP= keyword in the JCL EXEC statement PARM parameter.

When the previous is implemented, the user can display the selected statistics data from all active DB2 data sharing members by selecting the SYSPLEX request display. This display is the default display for the System Statistics selection on the Systems Menu. The SYSDCOLL request can also be selected here to see which data collector is active with each DB2 member, along with selected DB2 and group characteristics. The SYSPLEX display defaults to show selected statistics information for all active DB2 members for which a data collector is active. The user can display only selected members by specifying qualifying information in the criteria field (____) under the DB2 column header on the request display. The Unicenter CA-Insight standard selection characters of * and ? can be used in the criteria fields for multiple column and single column characters.

Beyond the Basic Installation 3–11 Data Sharing Implementation Considerations

The THRDACTV display in the data sharing environment can show all threads, or selected threads from all DB2 data sharing members. The default is to show only the threads from the DB2 member being monitored by the data collector to which the user is connected. To show threads from all members, place an * in the criteria field under the DB2 column header. The user can also use the criteria fields under the Auth ID, Corr ID and Plan column headers to further qualify the threads displayed. The LOCKCONT request can be used to show the history of thread contention in the data sharing group across all members. The IRLMCONT display shows the current contention among threads in the DB2 data sharing group.

As mentioned previously, the Unicenter CA-Insight user interface has the capability to jump to another data collector to display detailed statistics or thread information when selected from the SYSPLEX or THRDACTV displays. The Unicenter CA-Insight Remote Access Facility (RAF) is required to be implemented on all data collectors in the group to support this feature. A VTAM Luname must be defined for each data collector, specified in the SYSPARMS for that data collector in the APPLS= parameter and activated. Don’t forget to make RAF=YES and specify the DB2-LOCATION= in the SYSPARMS. The Unicenter CA-Insight user interface SYSPARMS must also specify all the data sharing group members in the APPLS= parameter. The location name for each member must specify the same location value, followed by the unique member name and unique VTAM Luname for each member.

Unicenter CA-Insight is able to connect and disconnect individual data collectors from its data sharing group. This means that not all members have to be activated, and data collectors can be stopped and restarted individually without affecting operations. Of course when a data collector is not available, data for the monitored DB2 member will not be included in the appropriate displays. The SYSDCOLL display will show the status of each individual data collector.

3–12 System Guide Chapter 4 Installing Optional Components

Use this chapter to install the optional product components, depending on your DB2 environment and monitoring needs.

Global Subsystem (GSS)

The Global Subsystem (GSS) contains common components used by certain Computer Associates products that require integration with other Computer Associates products. The common components of GSS that Unicenter CA-Insight uses include the Message Handler, a data logging facility, and an extensible REXX automation facility that includes the execution of IMODs triggered by DB2 exceptions detected by Unicenter CA-Insight. For more information, see the “Introduction” chapter.

When to Use GSS

You must install and activate the GSS if your data center wants to implement any of the following optional Unicenter CA-Insight features:

■ Collection, logging and playback of DB2 console messages

■ Logging and playback of exception messages

■ Collection, logging and playback of DB2 utility phase change messages

■ Collection, logging and playback of DB-Delivery® messages

■ Invocation of REXX automated operations routines from IQL requests and exceptions

■ Installation and use of System Condition Monitor (See System Condition Monitor (SCM).

Note: If you want to read DB2 console messages from within Unicenter CA-Insight, you must install the Global Subsystem.

The Global Subsystem replaces the Message Handler function from earlier versions.

Installing Optional Components 4–1 Installing the Global Subsystem (GSS)

Dependencies

You must install GSS if you plan on installing the System Condition Monitor.

Important! If you have already installed GSS for any Computer Associates product, see Step 6. Define and Load Global GSS IMOD Data Set, Step 7: Define Product-Specific GSS ILOG Data Sets, and Step 10: Modify the GSS PARMLIB Data Set for details about adding or modifying the connection between Unicenter CA-Insight and GSS. If you have DB-Delivery installed, and you have been using the AUDIT and LOGS services, you already have GSS installed. You do not need to install GSS.

Installing the Global Subsystem (GSS)

This section outlines the steps required to install the GSS from the Computer Associates GSS distribution tape.

The IBB GSS for MVS Installation and Operations Guide fully describes the GSS installation options required for Unicenter CA-Insight.

The following list briefly describes the basic steps necessary to install the GSS for Unicenter CA-Insight. Installation member names, supplied in the SOURCE library, are referenced where applicable. This list is intended as an overview and does not contain the detail necessary to install the GSS.

JCL member names in this section are shown with all capital letters. __ Step 1: Complete the GSS Installation Worksheet __ Step 2: Modify the GSS Installation Edit Macro (GSSEDIT) __ Step 3: Allocate and Load GSS Product Libraries (GSSUNLD) __ Step 4. Copy GSSRC Module to the Load Library __ Step 5: APF-Authorize the GSS LINKLIB __ Step 6. Define and Load Global GSS IMOD Data Set (GSSIMOD) __ Step 7: Define Product-Specific GSS ILOG Data Sets (GSSILOG) __ Step 8: Install MVS Subsystem Names for GSS __ Step 9. Create GSS Started Task Procedure (GSSPROC) __ Step 10: Modify the GSS PARMLIB Data Set (DB2SSID, GSSSPARM, GSSRUNP) __ Step 11: Verify GSS Installation __ Step 12: Install the GSS ISERVE Editor as an ISPF Application (Optional)

4–2 System Guide Installing the Global Subsystem (GSS)

Step 1: Complete the GSS Installation Worksheet

The JCL members you will use on the SOURCE library to install GSS must be modified to conform to your site’s specifications. At a minimum, you must make three changes to each PDS member to supply job card, data set name, and VOLSER information.

In this step, you complete the GSS Installation Worksheet on the next page with the defaults you will use to modify the GSS installation PDS members.

Naming Conventions

The naming conventions used to allocate and build the GSS product libraries and supporting VSAM data sets are as follows: gsshq.gssmq.lowqual and gsshqv.gssmq.lowqual

The value for lowqual is unique and predefined for each GSS product library. VSAM data sets (those named with the gsshqv qualifier) contain an additional qualifier that is DATA or INDEX.

DASD Space Requirements

The following table lists the GSS product libraries you will create in this section. DASD space requirements, using 3390 geometry, are included for each library. Associated directory block requirements can be found in parentheses.

Lowqual Type GSSVOL Size Contents CLIST PDS 1 track (1) GSS TSO/E CLIST library LINKLIB PDS 12 cylinders (10) GSS APF LINKLIB MLIB PDS 1 track (1) GSS ISPF message library PARMLIB PDS 150 tracks (120) GSS parameter library PLIB PDS 1 track (1) GSS ISPF panel library SAMPLE PDS 1 track(1) GSS Sample library

Lowqual Type IMODVOL Size Contents SAMPIMOD VSAM 1 cylinder GSS sample IMODs SYSIMOD VSAM 1 cylinder GSS system IMODs

Installing Optional Components 4–3 Installing the Global Subsystem (GSS)

GSS Installation Worksheet

The following is a description of the GSS Installation worksheet: GSSHQV Specify GSSHQV value to replace high-level qualifier of VSAM data sets in distributed JCL. GSSHQ Specify GSSHQ value to replace high-level qualifier of non-VSAM data sets in distributed JCL. GSSMQ Specify GSSMQ value to replace mid-level qualifier of all data sets in distributed JCL. GAPFLINK Specify GAPFLINK value to replace data set name of APF-authorized LINKLIB in distributed JCL. GAPFDSP Specify GAPFDSP value to replace DISP of APF-authorized LINKLIB. The value of this variable depends on whether an existing APF-authorized library is used or one is allocated during installation. If you use the same library for Unicenter CA-Insight and GSS, specify MOD to append the new members to the library. GSSTPVOL Specify GSSTPVOL value to replace VOLSER of distribution tape in JCL used to unload GSS product libraries. GSSVOL Specify GSSVOL value to replace DASD volume on which GSS product libraries are allocated. IMODVOL Specify IMODVOL value to replace DASD volume on which Unicenter CA-Insight VSAM IMOD and ILOG data sets are allocated.

Step 2: Modify the GSS Installation Edit Macro

We recommend that you use the edit macro GSSEDIT in the Unicenter CA-Insight CLIST library to quickly and accurately make changes to the PDS members used to install GSS. Modify GSSEDIT with the values entered on the GSS Installation Worksheet.

4–4 System Guide Installing the Global Subsystem (GSS)

Follow these steps to modify GSSEDIT: 1. Replace the rightmost parameters of each ISREDIT CHANGE macro with the corresponding values entered on the GSS Installation Worksheet. 2. If your product installation CLIST data set is not in your SYSPROC concatenation, copy the GSSEDIT member to a library that is concatenated to the SYSPROC DD in your TSO logon procedure. 3. Each time you edit a GSS installation member, enter GSSEDIT on the TSO COMMAND line to replace the defaults with your specifications.

Step 3: Allocate and Load GSS Product Libraries

To allocate and load GSS product libraries: 1. Modify GSSUNLD member Use the GSSEDIT macro to change the jobcard1, jobcard2, tapeunit, dasdunit, gsstpvol, gsshqv, gsshq, gssmq, gapflink, gapfdsp, gssvol, and imodvol values in the GSSUNLD member in the SOURCE library as specified on the Unicenter CA-Insight Installation Worksheet and the GSS Installation Worksheet. 2. Determine load library The GSS LINKLIB must be APF-authorized. Choose one of the following methods:

■ Method 1—Load directly into an existing APF-authorized load library (or if you are using the same load library as Unicenter CA-Insight. Before running the load job, be sure that the existing authorized load library has sufficient space (see the table in the previous section, Step 1: Complete the GSS Installation Worksheet), and was created with a BLKSIZE of 6144.

■ Method 2—Copy into an existing APF-authorized load library. The GSS LINKLIB is allocated and loaded into a non-APF-authorized data set. When the job successfully completes, copy all LINKLIB members to an APF-authorized load library.

■ Method 3—Allocate and load library which will later be APF-authorized. The GSS LINKLIB is allocated and loaded into a non-APF-authorized data set. 3. Submit the GSSUNLD JCL.

Installing Optional Components 4–5 Installing the Global Subsystem (GSS)

If you receive a non-zero return code, correct the JCL and re-submit the job. You can use member GSSDLETE in the SOURCE library to delete any data sets allocated with GSSUNLD. If you selected Methods 1 or 2, you can skip to Step 6. Define and Load Global GSS IMOD Data Set. If you selected Method 3, continue to Step 5: APF-Authorize the GSS LINKLIB.

Step 4. Copy GSSRC Module to the Load Library (GSSRCCPY)

To copy GSSRC Module to the Unicenter CA-Insight load library: 1. Modify GSSRCCPY member. Use the GSSEDIT macro to change the jobcard1, jobcard2, gapfdsp, gapflink, gssvol, diskunit, apfdsn, and prodvol values in the GSSRCCPY member in the SOURCE library as specified on the Unicenter CA-Insight Installation Worksheet and the GSS Installation Worksheet 2. Submit the GSSRCCPY JCL. If you receive a non-zero return code, correct the JCL and re-submit the job.

Step 5: APF-Authorize the GSS LINKLIB

Use one of the following methods to APF-authorize the GSS LINKLIB created from the GSSUNLD member in the previous step:

Method 1

Define the LINKLIB as APF-authorized in SYS1.PARMLIB and wait for an IPL. If you choose this method, you might want to coordinate this step with the next IPL.

The library is defined by placing an entry in the IEAAPFxx member as follows: IEAAPFxx--gsshlq.gssmlq.LINKLIB gssvol

Where xx is the suffix of the IEAAPF member used at IPL.

The gsshlq, gssmlq, and gssvol values were specified by you on the GSS Installation Worksheet.

Method 2

Dynamically authorize the load library using a tool such as Unicenter CA-SYSVIEW.

4–6 System Guide Installing the Global Subsystem (GSS)

Method 3

Use the GSSUNLD member in the SOURCE library to allocate and load the GSS LINKLIB, then copy all load library members to an authorized library.

Method 4

Use the GSSUNLD member in the SOURCE library to load an existing authorized library. If you use an existing authorized load library you must insure that it has sufficient space and a BLKSIZE of 6144 as specified on the LINKLIB DD statement in the GSSUNLD member.

Step 6. Define and Load Global GSS IMOD Data Set

Unicenter CA-Insight requires the creation of a GSS IMOD data set that contains custom IMODs used by the Unicenter CA-Insight System Condition Monitor and other facilities. You use the GSSIMOD JCL member in the SOURCE library to define and load this Unicenter CA-Insight-specific IMOD data set as outlined in the following. 1. Use the GSSEDIT macro to change the jobcard1, jobcard2, gsshqv, gssmq, tapevol, imodvol, and tapeunit values in the GSSIMOD member in the SOURCE library as specified on the Unicenter CA-Insight Installation Worksheet and the GSS Installation Worksheet. Note: The GSSIMOD JCL uses the Unicenter CA-Insight tape, not the GSS tape. 2. Submit the GSSIMOD JCL. If you receive a return code of greater than 8, correct the JCL and re-submit the job. The first step issues a DELETE for the data set being defined, so you might encounter a return code of 8 during initial execution of this job.

Step 7: Define Product-Specific GSS ILOG Data Sets

Unicenter CA-Insight requires the creation of two GSS VSAM linear ILOG data sets for each DB2 subsystem for which DB2, exception, and utility messages are to be collected. You use the GSSILOG JCL member in the SOURCE library to define the data sets as outlined in the following. 1. Use the GSSEDIT macro to change the jobcard1, jobcard2, gsshqv, gssmq, and imodvol values in the GSSILOG member in the SOURCE library as specified on the Unicenter CA-Insight Installation Worksheet and the GSS Installation Worksheet.

Installing Optional Components 4–7 Installing the Global Subsystem (GSS)

2. Submit the GSSILOG JCL. When defining these data sets, you might encounter system messages prefixed by IEC1611 072-053, indicating initialization errors. These messages are part of the normal initialization process and might be ignored. Additional pairs of ILOG data sets must be allocated for each DB2 subsystem to be monitored on the same MVS image (up to a maximum of 14). Change the LOGnn#0 and LOGnn#1 values for each pair created. For example, a site’s ILOG allocation for three DB2 subsystems should be: DB2 #1 - LOG01#0 and LOG01#1 DB2 #2 - LOG02#0 and LOG02#1 DB2 #3 - LOG03#0 and LOG03#1 Note: The GSSILOG member in the source library has been changed from previous releases. The ILOGs are now created and initialized with the GSS utility program SRVMAINT. This utility program must be used to initialize any new ILOG data sets, since scrolling errors will result otherwise. GSSILOG assumes that the library containing the SRVMAINT program is part of the linklist libraries. If not, a STEPLIB DD statement must be added to the initialization step.

Step 8: Install MVS Subsystem Names for GSS

Important! If you do not define the subsystem names, the GSS initialization routines create them dynamically.

The GSS requires that two MVS subsystem names be defined, one for GSS and one for the IMOD facility, as follows:

■ GOAL—MVS subsystem name required for the GSS

■ ISRV—Recommended MVS subsystem name for the IMOD Facility. However, you can use any MVS subsystem name you choose.

For permanent installation, the MVS subsystem names should be defined in the SYS1.PARMLIB member.

Step 9. Create GSS Started Task Procedure

A GSS started task procedure must be created to load and execute programs required for initializing and maintaining the GSS.

Follow these steps to create a GSS started task member: 1. Use the GSSEDIT macro to change the gapflink, gsshq, gssmq, hlq, and mlq values in the GSSPROC member in the SOURCE library as specified on the Unicenter CA-Insight Installation Worksheet and the GSS Installation Worksheet.

4–8 System Guide Installing the Global Subsystem (GSS)

2. Create a PROCLIB member using the GSSPROC member in the SOURCE library as a model. 3. If you are using GSS Version 2.6 or greater, you might wish to uncomment the GNETLOG DD statement. Goalnet is used by the System Condition Monitor (SCM) to access the status of products and remote MVS images. If you do not intend to install the SCM, or if the SCM will be used to monitor local products, you need not uncomment the GNETLOG DD statement. See your GSS documentation for more information about Goalnet.

Step 10: Modify the GSS PARMLIB Data Set

Before starting the GSS, you must modify the members listed here:

Library Member Description Unicenter DB2SSID DB2 subsystems to be monitored by GSS CA-Insight SOURCE Unicenter GSSSPAR GSS IMOD editor options CA-Insight M SOURCE Unicenter GSSRUNP GSS runtime options CA-Insight SOURCE

DB2SSID Customization

Edit the DB2SSID member in the SOURCE library as shown here:

********************************************************************** * * * The GSSPROC member used to initiate the GSS started task uses * * this member to initialize ILOG logging for each DB2 subsystem * * being monitored. Each entry consists of an SSID (1 to 4 bytes), * * followed by an ILOG number (1-99) and an IMOD number (1-14). * * If an IMOD or ILOG are not to be assigned, a value of ‘*’ must * * be specified. * * * ********************************************************************** * * * DB2A 1 * /* ILOG = 1, NO IMOD <=== SPECIFY YOUR DB2 SSID * * DB2B 2 * /* ILOG = 2, NO IMOD <=== ENTRY FOR 2ND DB2 SSID * * DB2C 3 * /* ILOG = 3, NO IMOD <=== ENTRY FOR 3RD DB2 SSID * * * * Change the following parameter from NO to YES if you are using * * System Condition Monitor. * * * SYSTEM CONDITION MONITOR = NO

Installing Optional Components 4–9 Installing the Global Subsystem (GSS)

Each line specifies one DB2 subsystem and its associated ILOG data set number. In the previous example, the second line (DB2B) is commented out. The ILOG data set number corresponds to the nn in the LOGnn#0 and LOGnn#1 data sets created in Step 7: Define Product-Specific GSS ILOG Data Sets.

Normally, you would give each DB2 subsystem a distinct log number so that the Unicenter CA-Insight Messages component displays messages for each DB2 subsystem separately. You can choose to assign more than one DB2 subsystem to a given set of ILOG data sets. In this case, all messages from the selected subsystems will be stored in the same ILOG.

GSSSPARM Customization

Use the GSSEDIT macro to change the gsshqv and gssmq values in the GSSSPARM member.

The GSSSPARM member is used by the GSS IMOD editor to build a list of available IMOD data sets. For the Unicenter CA-Insight user, the GSSSPARM member specifies the two IMOD data sets distributed with the GSS and the IMOD data set distributed with Unicenter CA-Insight.

Each GSSSPARM entry consists of two records:

■ The first record contains two fields separated by one or more blanks: – ISET-name (1-16 character logical name of the IMOD data set) – DATASET-name (1-44 character IMOD data set name)

■ The second record contains a description of the IMOD data set

GSSRUNP Customization

The GSSRUNP member in the SOURCE library contains GSS initialization and operating parameters.

Follow these steps to customize the member: 1. Use the GSSEDIT macro to change the values in the GSSRUNP member. 2. If you plan to use the System Condition Monitor, you will un-comment the appropriate lines at the bottom of the GSSRUNP member. Installation of the System Condition Monitor is detailed in System Condition Monitor (SCM). 3. If you are using the System Condition Monitor or a heavily utilized DB2 subsystem, uncomment the MAXXREQ parameter. 4. Sample Goalnet parameters are included for both GSS Version 2.5 and GSS Version 2.6. See your GSS documentation for more information about Goalnet.

4–10 System Guide Installing the Global Subsystem (GSS)

Step 11: Verify GSS Installation

This step assists you in verifying the installation of the GSS. Follow the steps in the order they are presented. 1. Start the GSS by issuing the GSS START command (S) from an MVS console. For example, issue the following command to start the GSS: S GSSA 2. Ensure that the Unicenter CA-Insight PC Owner is running. 3. Start the data collector for a DB2 subsystem for which messages are being collected. Look for message DBG47001I to indicate that message logging is occurring. Also, look for message SRV282 in the GSS job. 4. Cause a DB2 message to be created by the monitored DB2 subsystem. For example, from an MVS console you could issue the following DB2 command: -DISPLAY THREAD(*) 5. Log on to a Unicenter CA-Insight user interface session. 6. Select the DB2 subsystem which displayed the results of the previous command, by using the PickDB2 command. 7. Select option 4 from the Systems Menu. 8. The message screen should appear displaying the last messages created by the DB2 subsystem. If you have a problem, first verify that all the installation steps were executed successfully. Then check any error messages that might have been issued by Unicenter CA-Insight by referencing the Messages Guide. 9. Issue the GSS STOP command (P) from the MVS console to terminate the GSS. For example, to stop the GSS started in Step 1, use the following command: P GSSA If you have problems stopping the GSS, purge the task.

Step 12: Install the GSS ISERVE Editor as an ISPF Application (Optional)

Important! You should perform this step only if you want to edit IMODs.

In this step, you perform the following tasks:

■ Modify the ISPF primary menu or submenu panel

■ Allocate data sets with a CLIST

Installing Optional Components 4–11 Installing the Global Subsystem (GSS)

Prerequisite

This step requires that you know how ISPF works and how your installation uses ISPF. Do not proceed with this step until you have completed all previous steps.

Important! Be careful when modifying the ISPF primary menu panel. An error can prevent you from using ISPF. Always keep a backup member and a tested procedure that is independent of ISPF.

Modifying the Menu Panel

Follow these steps to modify the Menu Panel: 1. Locate the menu or submenu panel from which you will invoke the ISERVE editor and add the following menu item in the PROC section of the panel: ISRV, ‘PGM(SRVEDIT) NEWAPPL(nnnn)’ 2. Replace nnnn with a four character ISPF application ID (e.g., ISRV).

Allocating Data Sets with a CLIST

You must allocate the GSS ISERVE data sets before you can invoke the ISERVE editor under ISPF. The GSSCLIST member in the Unicenter CA-Insight CLIST library performs these allocations and concatenations. You must store GSSCLIST in a SYSPROC library and modify as outlined in the following: 1. If your product installation CLIST data set is not in your SYSPROC concatenation, copy the GSSCLIST member to a library that is concatenated to the SYSPROC DD in your TSO logon procedure. 2. Use the GSSEDIT macro to change the gapflink, gsshq, gssmq, hlq, and mlq values in the GSSCLIST member as specified in the GSS and Unicenter CA-Insight Installation Worksheet.

4–12 System Guide Installing the Global Subsystem (GSS)

Dynamic Concatenation Programs

GSSCLIST references the SRVCCAT and SRVDCAT programs. These TSO command processors permit dynamic concatenation (SRVCCAT) and de-concatenation (SRVDCAT) of data sets, as explained in the following. By using these programs, the CLIST does not need to be aware of which libraries pre-exist in your SYSPROC concatenation.

■ SRVCCAT—Lets you dynamically concatenate two DD statements. It has the following format: SRVCCAT ddname1 ddname2 Replace ddname1 with the DD name of the concatenation to which you want to add another DD statement. Replace ddname2 with the DD name of the statement you want to add to the concatenation. For example, if you want to add the DD statement SRVPROC to the current SYSPROC concatenation, you typically would use the FREE SYSPROC command, which would require that you then reallocate all entries. Use the following command instead to dynamically concatenate the SRVPROC DD statement: SRVCCAT SYSPROC SRVPROC

■ SRVDCAT—Lets you cancel the concatenation performed by the SRVCCAT command. It has the following format: SRVDCAT ddname Replace ddname with the DD name of the concatenation that you had previously added with SRVCCAT. For example, to cancel the concatenations performed by the SRVCCAT previous example, issue the following command: SRVDCAT SYSPROC

Increasing ILOG File Sizes

If you want to increase the ILOG file sizes, you must follow the steps as outlined in the following: 1. Increase the ILOG PAGES parameter in the GSS startup parameters. See GSSRUNP. On a 3380 device, a cylinder contains 180 4k page records. 2. Reallocate the ILOG subfiles on DASD, making sure that the number of cylinders allocated are sufficient to contain the number of PAGES specified. 3. Make sure that you increase the GSS address space REGION parameter on the EXEC statement to allow for enough additional extended private area storage to contain the increased size of the ILOGs. Failure to follow this step can result in S0C4 or S0C1 abends in GSS.

Installing Optional Components 4–13 Enable the Unicenter CA-SYSVIEW or GSS User Interface

Adding ILOG Subfiles

If you want to increase the number of ILOG subfiles specified for an ILOG, you must follow the steps as outlined in the following: 1. Add additional ILOG FILE statements to the GSS startup parameters for each subfile you are adding to an ILOG file. Make sure the subfile numbers are incremented by one each time a subfile is added. Up to 10 subfiles can be specified for each ILOG file. See GSSRUNP for the format and a sample of an ILOG FILE statement. 2. Reallocate the ILOG subfiles on DASD, making sure that the number of cylinders allocated are sufficient to contain the number of PAGES specified. 3. Make sure you increase the GSS address space REGION parameter on the EXEC statement to allow for enough additional extended private area storage to contain the increase size of the ILOGs. Failure to follow this step can result in S0C4 or S0C1 abends in GSS.

Enable the Unicenter CA-SYSVIEW or GSS User Interface

You can invoke Unicenter CA-Insight from within Unicenter CA-SYSVIEW (CA's MVS performance monitoring tool) or GSS. To enable the interface, perform the following steps: 1. Make the IDB2COMM module available to the Unicenter CA-SYSVIEW user or GSS address space. You can do this in one of the following ways:

■ Make the Unicenter CA-Insight load library available to the address space using a STEPLIB or LINKLIST. (This is the recommended method.)

■ Copy the IDB2COMM load module to the GSS or Unicenter CA-SYSVIEW load library. 2. Install the VTAM user interface with the Unicenter CA-SYSVIEW/GSS option enabled. See The VTAM User Interface section later in this chapter for details on installing the VTAM user interface.

After these two steps are performed, you can invoke Unicenter CA-Insight from within a Unicenter CA-SYSVIEW user session by issuing the IDB2 command.

4–14 System Guide The VTAM User Interface

The VTAM User Interface

The VTAM user interface provides non-TSO users with the ability to view online reports created by the Unicenter CA-Insight data collector, manipulate IQL requests, view DB2 console and utility phase change messages, and issue DB2 commands. Once you successfully sign on to Unicenter CA-Insight, all of the panels and functionality are the same as when using the TSO/ISPF interface, except for request EDIT and BROWSE, and browse of reviewed files.

The VTAM user interface and the Remote Access Facility (RAF) are independent optional components, and neither requires the other to operate.

Installing the VTAM User Interface

The following list briefly describes the steps required to install the VTAM user interface. Applicable JCL members are shown with all capital letters. __ Step 1: Prepare VTAM __ Step 2: Prepare VTAM User Interface Parameters (IDUIPRMS) __ Step 3: Prepare VTAM User Interface JCL (IDB2VUS) __ Step 4: Modify Security for the NSIGHTEX User Exit (NSIGHTEXT) __ Step 5: Verify VTAM User Interface Installation

Step 1: Prepare VTAM

The VTAM user interface supports access to Unicenter CA-Insight from GSS and from VTAM. The GSS does not use VTAM to communicate with Unicenter CA-Insight. If you don’t intend to log on to Unicenter CA-Insight through VTAM but you do intend to use the GSS to access Unicenter CA-Insight, you can omit the VTAM-specific setup instructions in this section.

Follow these steps to prepare the Unicenter CA-Insight user interface to operate under VTAM: 1. You can define the application program to VTAM by adding the following to SYS1.VTAMLST: IDB2USER VBUILD TYPE=APPL IDB2USER APPL ACBNAME=IDB2USER,EAS=nn where nn specifies the approximate number of concurrent users. These statements can be added to an existing member in SYS1.VTAMLST. If a new member is used, the member name (VTAM node name) must be different than the APPLID (IDB2USER in the example).

Installing Optional Components 4–15 The VTAM User Interface

2. Vary the IDB2USER APPLID active by issuing the following MVS console command: V NET,ACT,ID=idb2node where idb2node is the name of the PDS member containing the previous VBUILD statements. The activation of the APPLID is typically automated by adding the node name to the VTAM startup list. 3. Optionally, you can add the following USS definition table to the USSTAB for Unicenter CA-Insight to simplify the manner in which a user logs on to the VTAM user interface. These statements can be found in the USSDEF member in the SOURCE library. USSCMD CMD=CA-INSIGHT,REP=LOGON,FORMAT=PL1 USSPARM PARAMETER=APPLID,DEFAULT=IDB2USER USSPARM PARM=LOGMODE USSPARM PARAMETER=DATA

Step 2: Prepare VTAM User Interface Parameters

Edit the APPLS and IDUIPRMS members in the SOURCE library. The parameters that affect the VTAM user interface are listed in the following. These parameters are the same as and are shared by the TSO user interface.

1. Change the APPLS parameter list to agree with your configuration. The APPLS parameter consists of a list of four item entries. Each row identifies a DB2 subsystem and the associated VTAM application name that is used when the data collector is accessed from a remote MVS. Specify all DB2 subsystems you wish to monitor in this list, and they will be available for selection while using the Unicenter CA-Insight user interface. The following example shows a dummy entry containing the optional VTAM password and an entry without it. APPLS=( (DB2LOCATION,xxxx,NOTRAF,RAFPW1), (GCOIDB2DEVDSN,DSN,ID22DSN) ) If you use the DB2 Distributed Database Facility, you should use the same DB2 location names that are in SYSIBM.SYSLOCATIONS or SYSIBM.LOCATIONS in DB2 V5.1.

4–16 System Guide The VTAM User Interface

2. Modify the user interface IDUIPRMS LOGON-CHECK= parameter as follows:

■ YES for RACF security users.

■ YES if you have completed the procedures allowing eTrust CA-Top Secret to allow the Unicenter CA-Insight VTAM user interface to validate user ID and password.

■ YES if you are an eTrust CA-ACF2 user and complete the steps outlined in eTrust CA-ACF2 Considerations in Step 4.

■ NO if you wish to bypass user ID and password validation.

Descriptions of all parameters are available in the “Operation and Customization” chapter.

Step 3: Prepare VTAM User Interface JCL

The VTAM user interface can be started as a batch job or as a started task.

IDB2VUS Sample JCL Member

The IDB2VUS SOURCE member was generated during the post install process and is intended to be run as a started task. You may have optionally had a copy of the VTAM user interface started task JCL copied into your PROCLIB data set under a different started task name during the post install.

The JCL member can be modified and used to execute the VTAM user interface as a batch job. //IDB2VUS PROC SYSP=IDUIPRMS, // APPLID=‘IDB2USER,NONE’, // PRT=A //* //IDB2VU EXEC PGM=IUIVTAM,REGION=4096K,TIME=1440, // PARM=‘&APPLID’ //* //STEPLIB DD DISP=SHR, CA-Insight LOAD LIBRARY / DSN=apfdsn //* /IUIMAPS DD DISP=SHR, CA-Insight PANEL LIBRARY / DSN=hlq.mlq.IUIMAPS //* //SYSPARMS DD DISP=SHR, CA-Insight SOURCE LIBRARY // DSN=hlq.mlq.SOURCE(&SYSP) //* //INSPROF DD DISP=SHR, CA-Insight USER PROFILES // DSN=hlqv.mlq.PROFILE //* //SYSUDUMP DD SYSOUT=&PRT //*

Installing Optional Components 4–17 The VTAM User Interface

//DBGPRINT DD DUMMY,DCB=BLKSIZE=80 DIAGNOSTIC PRINT OUT //* //*REQUESTS DD DISP=SHR, OPTIONAL IQL REQUEST LIBRARY //* DSN=hlq.mlq.REQUESTS //*

IDB2VUS Sample JCL Explanation

The following explains each JCL statement and parameter.

■ //IDB2VUS PROC—Supplies the APPLID and SSID symbolic parameters to the procedure. This is required. These symbolic parameters are used as follows:

■ SYSP=—Used to specify the member that contains the user interface parameters (detailed in the “Operation and Customization” chapter.

■ APPLID=—Used to specify the program parameters (PARM field on the EXEC card) for the VTAM user interface. You specify up to 3 positional parameters in the EXEC PARM field (APPLID PROC parameter) as follows: – VTAM logon application ID (APPLID) – MVS subsystem name to use when integrating Unicenter CA-Insight with Unicenter CA-SYSVIEW or GSS. If the interface is enabled, specify IDB2. Otherwise, specify NONE. The IDB2 subsystem does not need to be predefined to MVS. It is dynamically added if it is not currently defined. – If IDB2 is specified in the second parameter (the GSS/Unicenter CA-SYSVIEW interface is enabled), use the third parameter to specify the name of the subsystem used by the Unicenter CA-Insight PC task (same value as specified in PCSSID option in the user interface SYSPARMS). The default subsystem name is DBGI. Note: The PC task must be running at version 6.3 or higher.

■ //STEPLIB—Is normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules.

■ //IUIMAPS—(required). Allocates the Unicenter CA-Insight online panels and messages file. The TSO and batch user interfaces also use this file. Concatenation is allowed.

■ //SYSPARMS—(required). Points to the VTAM user interface initialization parameters. As one example, the parameters describe the available data collectors (as seen on the PickDB2 panel).

■ //INSPROF—(required). Points to the data set that contains your Unicenter CA-Insight session user profile.

4–18 System Guide The VTAM User Interface

■ //SYSUDUMP—(optional). Allocates an output destination for any ABEND dumps, which can occur during execution.

■ //DBGPRINT—(required). Allocates an output destination for VTAM user interface system messages. If a permanently allocated data set is specified with a disposition of SHR and enough space is allocated for anticipated message traffic, it can be browsed from TSO during execution.

■ //REQUESTS—(optional). Un-comment this and the following lines to access requests that are not part of the standard set supplied with Unicenter CA-Insight.

If you run this job as a started task, it must be in a data set allocated to your system PROC libraries.

APPLID PROC Parameter Examples

Example One

VTAM user interface using IDB2USER as the VTAM APPLID with no Unicenter CA-SYSVIEW interface enabled: APPLID='IDB2USER,NONE'

Example Two

VTAM user interface using IDB2APPL as the VTAM APPLID with the Unicenter CA-SYSVIEW interface enabled using the PC task defined with a subsystem ID of PC63: APPLID='IDB2APPL,IDB2,PC63'

Example Three

VTAM user interface using IDB2APPL as the VTAM APPLID with the Unicenter CA-SYSVIEW interface enabled using the default PC task: APPLID='IDB2APPL,IDB2'

or APPLID='IDB2APPL,IDB2,DBGI'

Example Four

VTAM user interface with no logon VTAM APPLID enabled and with the Unicenter CA-SYSVIEW interface enabled using the default PC task: APPLID='NONE,IDB2'

or APPLID='NONE,IDB2,DBGI'

Installing Optional Components 4–19 The VTAM User Interface

Step 4: Modify Security for the NSIGHTEX User Exit

The NSIGHTEX User Exit provides user ID and password validation to the VTAM user interface without coding changes. NSIGHTEX uses RACROUTE system services for basic authorization. Detailed information about NSIGHTEX can be found in the “NSIGHTEX User Exit” appendix.

The three supported external security packages are RACF, eTrust CA-Top Secret and eTrust CA-ACF2. Specific access control issues are described in the following sections.

RACF and eTrust CA-Top Secret Considerations

The NSIGHTEX routine validates the security User ID and password. As coded, anyone with a valid user ID and password is allowed access. This validation involves a RACROUTE VERIFY that creates an ACEE control block, which provides additional information.

As coded, you can direct users who have specific security connect groups to specific menus. The translation is based on the first four characters of the security connect group. The NSIGHTEX user exit scans the user’s connect groups for one that begins with INS. The fourth character of the first INS prefixed connect group that is found determines the initial menu that appears when the user logs on as follows:

Connect Group Unicenter CA-Insight Purpose of Menu Menu INSS SYSTEM Systems Menu INSD DBA DBA Menu INSA APPLDEVL Application Programmer’s Menu INSO OPERATOR Computer Operator’s Menu INSU AUDITOR Auditor’s Menu Otherwise SYSTEM Systems Menu

The security group ID is set to the security group ID or the “INS” Connect Group if available. For “INS” connect groups, the 5th through 8th characters can be used to distinguish groups or positions within a given menu. For example, a distinction can be made between a Senior and a Junior Applications Developer. If you want to use Connect Group names other than those that start with “INS,” you can modify the NSIGHTEX security exit. For details, See the “NSIGHTEX User Exit” appendix.

4–20 System Guide The VTAM User Interface

In order to made use of this feature for the VTAM user interface, make sure that LOGON-CHECK=YES is specified for the VTAM user interface in the IDUIPRMS member.

This exit is provided in source so that it can be tailored to meet your needs.

If the SECURITY-FILE parameter is specified in the user interface SYSPARMS, the menu named on the profile will override the “INS” menu selection previously described.

Additional CA-Top Secret Considerations

The NSIGHTEX User Exit validates the CA-Top Secret User ID and password. For this to occur, CA-Top Secret requires that you explicitly define the VTAM user interface as a Master Facility.

Follow these steps to explicitly define the VTAM user interface as a Master Facility: 1. Define a CA-Top Secret Master Facility or rename/alter an unused Master Facility. 2. Add the Master facility to a CA-Top Secret profile that is available to those who need to use it. 3. Create a CA-Top Secret ACID for the IDB2VUS started task. The ACID is a pseudo user ID for an MVS started task. If the VTAM user interface needs to be started as a batch job, then you must specify the ACID in the USER= parameter of the JOB card. The ACID for a batch job must not be longer than 7 characters. The following example assumes that Master Facility USER3 is unused. 4. Use CA-Top Secret to rename the Master Facility by issuing the following commands: TSS MODIFY(FAC(USER3=NAME=INSIGHT)) TSS MODIFY(FAC(INSIGHT=MODE=FAIL)) TSS MODIFY(FAC(INSIGHT=PGM=NAI)) TSS MODIFY(FAC(INSIGHT=SUAS)) TSS MODIFY(FAC(INSIGHT=AUTHINIT)) TSS MODIFY(FAC(INSIGHT=SIGN(S))) TSS MODIFY(FAC(INSIGHT=NOLUMSG)) You can change INSIGHT=SUAS to INSIGHT=MULTIUSER if the following conditions are met:

■ All User Profiles have EXPLAIN=TSO

■ All User Profiles have DB2-COMMANDS=TSO

■ The Remote Access Facility (RAF) is not used

Installing Optional Components 4–21 The VTAM User Interface

5. Add the Master Facility to a CA-Top Secret Profile: TSS ADD(profile-name) FAC(INSIGHT) 6. Create the CA-Top Secret ACID for the IDB2VUS procedure: TSS CRE(IDB2VUS) TYPE(USER) PASSWORD(NOPWS,0) NAME(‘INSIGHT FOR DB2’) PROF(profile-name...... ) DEPT(department) MASTFAC(INSIGHT) 7. Assign the ACID to the IDB2VUS started task: TSS ADD(STC) PROC(IDB2VUS) ACID(IDB2VUS) In addition, you must insure that IDB2VUS has access to all of the data sets named in the JCL. eTrust CA-ACF2 Considerations

The NSIGHTEX user exit validates the eTrust CA-ACF2 user ID and password. For this to occur, you must explicitly define the VTAM user interface to eTrust CA-ACF2.

Perform these steps before running the VTAM user interface in an eTrust CA-ACF2 environment. If you are using eTrust CA-ACF2 release 6.0 or higher, perform step 2 only. Otherwise, perform all four steps. 1. SAF must be turned on globally in the CA-ACF2 GSO OPTS record. 2. The started task needs to be defined to CA-ACF2 as a MUSASS. The following command sequence defines the MUSASS application using the CAQ-ACF2 command processor: ACF SET LID INSERT started task name NAME(descriptive text) MUSASS STC END Replace started task name with the VTAM user interface started task name (e.g., IDB2VUS). 3. Validate the RACROUTE by issuing the following CA-ACF2 commands: ACF SET CONTROL(GSO) INSERT SAFPROT.LEGENT SUBSYS(IUIAPPL)CNTLPTS(IUIAPPL)CLASSES(-) END 4. Refresh the definitions by issuing the following MVS console commands: F ACF2,REFRESH(OPTS) F ACF2,REFRESH(SAFPROT)

You should now be able to log on to the Unicenter CA-Insight VTAM user interface.

4–22 System Guide Remote Access Facility (RAF)

Step 5: Verify VTAM User Interface Installation

Once the VTAM user interface batch job or started task is active, you can log on as described in the following. You can tell when the VTAM user interface is active when the batch job or proc issues the following message: DBG51002I NOW ACCEPTING LOGONS

Logging on to a VTAM APPLID is highly MVS site specific. The following examples show logon variations that might be required at your installation (the following examples assume that the VTAM applid is IDB2USER):

■ When using the PL1 format logon, enter the following from an MVS logon screen: LOGON APPLID(IDB2USER) DATA(userid/password)

■ When using the Assembler format logon, enter the following from an MVS logon screen: LOGON APPLID=IDB2USER DATA=userid/password

■ If the USSCMD is in operation, enter the following command: CA-INSIGHT

Note: The DATA= or DATA() parameters are optional.

If you supplied the correct user ID and password in the LOGON command, the appropriate Unicenter CA-Insight Initial Menu appears.

However, if you did not supply both the user ID and correct password, or you did not use the DATA= or DATA() parameters, the Unicenter CA-Insight VTAM User Interface Logon panel appears. On this panel, enter your user ID and password as follows: USERID ===> xxxxxxxx PASSWORD ===> xxxxxxxx

Remote Access Facility (RAF)

The Remote Access Facility (RAF) provides users with the ability to connect to remote data collectors without having to logon to the system where those data collectors reside.

Both the TSO and VTAM user interfaces can take advantage of the RAF connection. With RAF enabled, the Unicenter CA-Insight PICK panel will list the RAF-connected data collectors as being REMOTE and ACTIVE.

Installing Optional Components 4–23 Remote Access Facility (RAF)

The SOURCE library contains several members that you can use as models for VTAM parameters.

RAF employs VTAM definitions on both the local and remote MVS images, but does not require the VTAM user interface.

Installing the Remote Access Facility

The following list briefly describes the steps required to install the Remote Access Facility (RAF). Applicable JCL members are shown with capital letters. __ Step 1: Prepare VTAM __ Step 2: Prepare Data Collector and User Interface Parameters (IDDCPRMS) __ Step 3: Prepare User Interface Parameters (IDUIPRMS) __ Step 4: Verify the RAF Installation

Step 1: Prepare VTAM

There are five steps to prepare VTAM for RAF operation: 1. Define a VTAM APPLID in SYS1.VTAMLST for each data collector to be accessed remotely. Add definitions similar to the following example to SYS1.VTAMLST on the remote MVS. (See the “Introduction” chapter for more information.) DCAPPLB APPL AUTH=(NOACQ,NOCNM,NOPASS,NOPO,NOTSO,VPACE), X EAS=32,ENCR=NONE,MAXPVT=0,PARSESS=NO, X PRTCT=pppppppp,SONSCIP=YES DCAPPLC APPL AUTH=(NOACQ,NOCNM,NOPASS,NOPO,NOTSO,VPACE), X EAS=32,ENCR=NONE,MAXPVT=0,PARSESS=NO, X PRTCT=pppppppp,SONSCIP=YES where pppppppp specifies the optional password. These statements can be added to an existing member or to a new member in SYS1.VTAMLST. If a new member is used, the member name (VTAM node name) must be different from the APPLID (DCAPPLB and DCAPPLC in this example). This example is in member RAFDCAPP in the SOURCE library. 2. Define a VTAM APPLID for each online user that will access a remote data collector. The definitions must be numbered sequentially from 001 and the number of definitions should equal the maximum estimated number of concurrent users. Add definitions similar to the following example and in member RAFUIAPP in the SOURCE library to SYS1.VTAMLST on the local MVS (See the “Introduction” chapter for more information.) DCAPPLB APPL AUTH=(NOACQ,NOCNM,NOPASS,NOPO,NOTSO,VPACE), X EAS=32,ENCR=NONE,MAXPVT=0,PARSESS=NO, X PRTCT=pppppppp,SONSCIP=YES DCAPPLC APPL AUTH=(NOACQ,NOCNM,NOPASS,NOPO,NOTSO,VPACE), X EAS=32,ENCR=NONE,MAXPVT=0,PARSESS=NO, X

4–24 System Guide Remote Access Facility (RAF)

PRTCT=pppppppp,SONSCIP=YES The ACBNAME parameter entries must start with DBG001 and be sequentially ascending (i.e. DBG002, DBG003, and so on) in the entries that follow. PRTCT= is an optional password. If PRTCT= is specified, then the LCLPSWD= keyword must be specified in the IDUIPRMS user interface initialization member (see the “Operation and Customization” chapter for more information.) 3. You must specify a cross-domain resource definition in SYS1.VTAMLST on the local MVS (MVS-1 Address Space in this example) for each remote data collector to be accessed. This example uses the VTAM APPLIDs defined in Step 1. DCAPPLB CDSRC CDRM=CDRMMVS1 DCAPPLC CDSRC CDRM=CDRMMVS1 This example is in member RAFCDRSC in the SOURCE library. 4. You must identify to the remote MVS (MVS-2 Address Space in this example) the resources (for example, user sessions) that will access one of its data collectors remotely. You can set up the system to dynamically create CDSRC resource definitions at the time of an access or explicitly define each accessing resource. You can specify dynamic cross-domain resource definition as follows: In the MVS-1 SYS1.VTAMLST specify: CDSRC=OPT In the MVS-2 SYS1.VTAMLST specify: CDRDYN=YES This example is in member RAFCDRM in the SOURCE library. 5. In each MVS containing Unicenter CA-Insight users who will communicate with a remote data collector (MVS-1 Address Space in this example), specify a VTAM mode table entry as follows: IDB2LTBL MODETAB IDB2MODE MODEENT LOGMODE=IDB2MODE,X FMPROF=X’12’, X TSPROF=X’04’, X PRIPROT=X’B1’, X SECPROT=X’B1’, X COMPROT=X’70A0’, X RUSIZES=X’8989’, X PSNDPAC=X’07’, X SRCVPAC=X’07’, X SSNDPAC=X’07’, X PSERVIC=X’060038000000380000000000’ MODEEND END

Installing Optional Components 4–25 Remote Access Facility (RAF)

If your network has an RUSIZES limit smaller than 4096, specify RUSIZES=X’8888’ for 2048, RUSIZES=‘8787’ for 1024, and RUSIZES=X’8686’ for 512. This example is in member IDB2LTBL in the SOURCE library.

Step 2: Prepare Data Collector and User Interface Parameters

You must specify the appropriate RAF and APPLS parameters to invoke the Remote Access Facility. In the local MVS (MVS-A in this example) the data collector will not be accessed using RAF, so specify RAF=NO in the data collector SYSPARMS (db2ssidSYSP member in SOURCE).

In the remote MVS (MVS-B in this example) the data collector is accessed using RAF. So specify RAF=YES in the data collector SYSPARMS (db2ssidSYSP member in SOURCE). The APPLS parameter in the APPLS member in SOURCE must contain an entry that identifies the DB2 subsystems that will be accessed remotely. Specify the DB2-LOCATION within APPLS that matches the DBLOC parameter in the data collector JCL. The DB2-LOCATION is used with the DBSUB parameter to uniquely identify each DB2 subsystem.

You should use one APPLS member for all data collectors and the user interface on the remote MVS by specifying each DB2 subsystem ID and location in the APPLS parameter as follows: APPLS=( (DB2ALOCATION,DB2A,NOTVTAM), (DB2BLOCATION,DB2B,DCAPPLB), (DB2CLOCATION,DB2C,DCAPPLC) )

In addition, you must specify DBSUB= and DBLOC= in the EXEC statement of each data collector JCL stream. EXEC PGM=NISGHTDC,REGION=5M,DPRTY=(14,15),TIME=1440, PARM=‘/DBSUB=DB2B,DBWAIT=YES,DBLOC=DB2BLOCATION’

Step 3: Prepare User Interface Parameters

If you are using a common APPLS member in the SOURCE library for both the data collectors and the user interface, then there is no additional task to be done for the user interface. Otherwise, you will need to update the APPLS parameter for the user interface SYSPARMS to match the APPLS parameter for the data collectors.

4–26 System Guide NATURAL for DB2 Support

Step 4: Verify the RAF Installation

Perform the following steps to verify RAF installation and operation: 1. Issue the VTAM commands to activate the VTAM definitions. It is usually best to vary objects INACTIVE before varying the objects ACTIVE. 2. Restart all the data collectors with modified parameters 3. Log on to the Unicenter CA-Insight user interface. 4. Enter PICKDB2 and press Enter to display the PickDB2 panel with a list of the data collectors you specified in the APPLS member of the SOURCE library. 5. Enter an S next to the remote DB2 subsystem you wish to monitor and press Enter. 6. Press PF3 to return to the Systems Menu and select the System Statistics option (1). The System Snapshot panel should appear, displaying data about the remote DB2 you selected.

If at any point during the verification process you encounter an error message, check the Messages Guide for an explanation and suggested corrective action. Also, verify that you followed the preceding installation steps correctly.

NATURAL for DB2 Support

Unicenter CA-Insight provides support for the display of additional information for NATURAL, the fourth-generation language from Software AG®, when using NATURAL for DB2.

Support for NATURAL for DB2 exposes basic NATURAL information necessary to determine which NATURAL programs and statements are accessing DB2. Without this additional information, NATURAL appears to be one program to DB2.

Unicenter CA-Insight reports on the following NATURAL items:

■ Library name

■ Program name

■ Statement number

NATURAL for DB2 support has no dependencies to other Unicenter CA-Insight optional components.

Installing Optional Components 4–27 NATURAL for DB2 Support

Installing NATURAL for DB2 Support

Before you continue, be aware of following requirements:

■ The implementation requires the use of the DSNWVSER trace writer in DB2, rather than the usual IFI OP trace writer. This is so that the NATURAL data can be added directly to the Event Trace record when the trace record is created.

■ The attachment front-ends use the BUSER4 user field in the NATURAL BB (Big Buffer). We assume this field is not being used at your installation. If the field is being used, contact Computer Associates DB2 Client Services for information about how to change the attachment code.

■ The current implementation requires that the Unicenter CA-Insight PC Owner subsystem name must be DBGI when collecting NATURAL data.

Once Unicenter CA-Insight has been installed and verified, the installation additions for NATURAL support can begin. These are the steps to be taken: __ Step 1. Modify DB2, the Data Collector, and the PC Owner __ Step 2: Modify NATURAL for use with CICS, TSO, and CAF __ Step 3: Modify NATURAL for Use with IMS (Optional) __ Step 4: Validate the Installation

Step 1. Modify DB2, the Data Collector, and the PC Owner

Use the following steps to modify DB2, the data collector, and the PC owner.

Modify DB2

Place the SRV trace writer module (DSNWVSER) into the DB2 libraries.

The DSNWVSER module provided in the Unicenter CA-Insight load library must be copied (with an ISPF copy or a batch IEBCOPY) to a DB2 load library which is available in a STEPLIB for each of the DB2 system services address spaces to be monitored.

4–28 System Guide NATURAL for DB2 Support

Modify the Data Collector

Modify the data collector SYSPARMS member (IDDCPRMS) as follows: 1. Change statement IFI=YES to IFI=READS. IFI=READS specifies that the SRV trace writer module (DSNWVSER) will be used for Event Trace data, while the IFI will be used for Control Block data. 2. Change statement NATURAL-DB2=NO to NATURAL-DB2=YES. NATURAL-DB2=YES causes the NATURAL interface to be activated and the conditional statements in the requests to be generated.

Note: See the “Operation and Customization” chapter for more information about the IDDCPRMS parameter.

Modify the PC Owner

Start the PC Owner address space with the subsystem name of DBGI.

The PCSSID should be allowed to default or be explicitly specified as DBGI.

Start the Data Collector

Start the data collector using the modified SYSPARMS.

Step 2: Modify NATURAL for use with CICS, TSO, and CAF

Modify CICS

Link edit and zap the CICS call attach module DSNCEXT3 or DSN2EXT3.

The DSNCEXT3 or DSN2EXT3 CICS call attach module must be relinked to add a Unicenter CA-Insight interface subroutine. Three members in the SOURCE library perform this task:

■ LKEXT323 for DB2 V2.3

■ LKEXT331 for DB2 V3

■ LKEXT341 for DB2 V4.1

■ LKEXT351 for DB2 V5.1

■ LKEXT361 for DB2 V6.1

■ LK2XT341 for CICS V4.1

Installing Optional Components 4–29 NATURAL for DB2 Support

In addition, there are several other members that perform the task. These differ depending on which IBM PTFs have been applied to DSNCEXT3 or DSN2EXT3.

Follow these instructions: 1. Make a copy of DSNCEXT3 or DSN2EXT3 from the DB2 SDSNLOAD library. 2. Edit the appropriate LKEXT3xx (or LK2XT3xx) member to add a JOB card and to change the indicated data set names. Note: We suggest that you link the member into a separate load library first, rather than directly into the DB2 library. 3. Run the job to linkedit and zap DSNCEXT3 or DSN2EXT3. 4. Copy the module to the proper execution library and then cycle DSNC in CICS.

Modify NATURAL

Linkedit the NATURAL modules containing NATURAL for DB2 to implement front-end attachment code.

Each copy of NATURAL which contains NATURAL for DB2 support must be link edited to replace the original attachment routines with front-end attachment routines.

Separate members are provided in the Unicenter CA-Insight LOAD library for the CICS, TSO, and CAF (Call Attach Facility) attachments as indicated in the following table:

CICS TSO CAF DB2 V2.3 DSNCLI23 DSNELI23 DSNALI23 DB2 V3 DSNCLI31 DSNELI31 DSNALI31 DB2 V4.1 DSNCLI41 DSNELI41 DSNALI41 DB2 V5.1 DSNCLI51 DSNELI51 DSNALI51 DB2 V6.1 N/A DSNELI61 DSNALI61

Each member includes the front-end subroutine with the standard attachment code.

The NATURAL module can be recreated by one of the following methods:

4–30 System Guide NATURAL for DB2 Support

Method 1

This method recreates the module from scratch by using the linkage editor INCLUDE statements provided for NATURAL with the attachment INCLUDE statement changed to include the appropriate attachment from the Unicenter CA-Insight library.

For example, to include the TSO DSN attachment code, the statement INCLUDE INSLOAD(DSNELI23)

will bring in the member for DB2 V2.3 from the DD card pointing to the Unicenter CA-Insight load library.

Method 2

This method relinks an existing NATURAL module.

To relink a NATURAL TSO module for the DSN attachment originally named NDB222T1, the following control statements could be used: REPLACE DSNELI INCLUDE SYSLMOD(NDB222T1) INCLUDE INSLOAD(DSNELI23) ENTRY CMSTART NAME NDB222T1(R)

The SYSLMOD DD statement points to the NATURAL load library, and the INSLOAD DD statement points to the Unicenter CA-Insight load library.

With this method, you must remember to REPLACE all the attachments which are contained in the NATURAL module and to INCLUDE all the required replacement attachments from the Unicenter CA-Insight LOAD library. This is especially true when the DSN attachment is used with plan switching, as plan switching uses the CAF attachment.

Step 3: Modify NATURAL for Use with IMS (Optional)

Each copy of NATURAL, which accesses DB2 through IMS, must be relinked to replace the original attachment routines with front-ended attachment routines.

The NATURAL module can be recreated by one of the following methods:

Method 1

This method recreates the module from scratch by using the linkage editor INCLUDE statements provided for NATURAL and the attachment INCLUDE statement changed to include the appropriate attachment from the Unicenter CA-Insight library and to rename two entry points in the standard DFSLI000.

Installing Optional Components 4–31 NATURAL for DB2 Support

This statement: INCLUDE IMSLIB(DFSLI000)

should be changed to these statements: INCLUDE INSLOAD(NATLI000) CHANGE DSNWLI(SLDSNWLI),DSNHLI(SLDSNHLI) INCLUDE IMSLIB(DFSLI000)

The INSLOAD DD card points to the Unicenter CA-Insight LOAD library.

Method 2

This method relinks an existing NATURAL module.

To relink a NATURAL IMS module for the DSN attachment originally named NDB222I1, the following control statements should be used: REPLACE DFSLI000 INCLUDE SYSLMOD(NDB222I1) INCLUDE INSLOAD(NATLI000) CHANGE DSNWLI(SLDSNWLI),DSNHLI(SLDSNHLI) INCLUDE IMSLIB(DFSLI000) ENTRY CMSTART NAME NDB222I1(R)

The SYSLMOD DD statement points to the NATURAL load library.

The INSLOAD DD statement points to the Unicenter CA-Insight LOAD library.

The IMSLIB points to the IMS library.

Step 4: Validate the Installation

After restarting the environments that use NATURAL for DB2, you should be fully operational.

Several of the Unicenter CA-Insight-provided reports (following description) distributed in the request library include the NATURAL for DB2 data fields. The requests have been coded to only display the NATURAL for DB2 fields if the data collector SYSPARM has been specified as NATURAL-DB2=YES. See the “Operation and Customization” chapter for more information about this parameter.

Systems and DBA Menus

The APPLEXCP (Applications Exceptions report) provides NATURAL information.

4–32 System Guide NATURAL for DB2 Support

Auditor Menu

The AUDCLAS6 report (Binds or Dynamic SQL on Audited Tables) provides NATURAL information.

Active Threads Reports

The SQLTEXT (Currently Executing SQL Statement for a Thread) and THRDDETL (Active Thread Detail) reports display NATURAL information.

Probe Manager Reports

From the Application Probe, the following reports display NATURAL information:

■ PLANSUM (SQL Statements by Plan and Program)

■ SQLSUM (Pages and Rows Processed for Each SQL Statement)

■ SQLTRACE (Trace all SQL Statements)

■ THRDTRAC (Trace Thread)

User-Initiated Reports

The following reports display NATURAL information:

■ APPLPROF (Application Profile)

■ CURSSUM (SQL Summary by Plan, Program, and Cursor)

■ DISTRIB (Detailed Trace of Distributed Data Activity)

■ EXPSQL (SQL Statements that Scan Many Pages)

■ IOWAITRS (Plans that Waited on I/O for Another Thread)

■ LONGIO (Long I/Os)

■ PGMSUM (SQL Summary by Plan and Program)

■ PLANRDIO (Read I/O Summary by Database, Pageset, and Plan)

■ PLANWRIO (Write I/O Summary by Database, Pageset, and Plan)

■ RECTRACE (Detailed Trace of DB2 Activity)

Installing Optional Components 4–33 System Condition Monitor (SCM)

System Condition Monitor (SCM)

The System Condition Monitor displays the status of system components that have been identified to it.

Computer Associates’ Unicenter CA-SYSVIEW and Unicenter CA-Insight products identify MVS, CICS, and DB2 to the System Condition Monitor.

System Applications, such as monitors from Candle Corporation and Landmark Systems Corporation, can also be defined to the System Condition Monitor. Console messages issued by these monitors (reflecting MVS, CICS, and DB2 status) can be collected and displayed.

Installing the System Condition Monitor (SCM)

The following list briefly describes the steps required to install the System Condition Monitor (SCM). Applicable JCL members are shown with capital letters. __ Step 1: Modify the Data Collector Initialization Parameters (IDDCPRMS) __ Step 2: Modify the GSS Runtime Parameters (GSSRUNP) __ Step 3: Modify the Startup Member (Optional) __ Step 4: Modify the VTAM User Interface (Optional) (DB2SSID) __ Step 5: Enable the SCM (DB2SSID) __ Step 6: Verify the Installation

Step 1: Modify the Data Collector Initialization Parameters

Uncomment the following line in the IDDCPRMS member in the SOURCE library: SCM-IMOD-NAME=IDB2MEXC

This will cause all exceptions logged to the Exception System to also be logged to the System Condition Monitor.

Step 2: Modify the GSS Runtime Parameters

Uncomment the lines beginning with WTO ID at the bottom of the GSSRUNP member of the SOURCE library.

4–34 System Guide System Condition Monitor (SCM)

Different ISERVE Subsystem Name

If you change (or have changed) the ISERVE subsystem name (SSNAME) in member GSSRUNPof the SOURCE library, you must make corresponding name changes in these other areas:

■ SOURCE library - Members IDUIPRMS and IDDCPRMS—Change ISRV in the MSSUB=ISRV statement to the SSNAME value.

■ Unicenter CA-Insight REQUESTS Library - Member SCMCONN—Change ISRV in the IMODSSID=ISRV statement to the SSNAME value.

Step 3: Modify the Startup Member (Optional)

If you are using SCM to monitor CICS regions, you must uncomment the SCMCONN request line in the STARTUP member of the SOURCE library (or whatever the name of the startup member is).

This request is used to identify the CICS regions that were started before GSS.

Step 4: Modify the VTAM User Interface (Optional)

To move to another application when accessing Unicenter CA-Insight through the VTAM user interface, the following changes must be made: 1. Add the following statement to the DB2SSID member of the SOURCE library (see DB2SSID Customization): VTAM-UI-APPLID=‘CA-INSIGHTuserapplid’ where CA-INSIGHTuserapplid is the name of the Unicenter CA-Insight application ID defined to VTAM in SYS1.VTAMLST and modified here in Step 2. See Step 1: Prepare VTAM for more information. 2. The APPL statement must be appended with ,AUTH=PASS. The entire statement would look similar to this: IDB2USER VBUILD TYPE=APPL IDB2USER APPL ACBNAME=IDB2USER,EAS=nn,AUTH=PASS

Installing Optional Components 4–35 System Condition Monitor (SCM)

Step 5: Enable the SCM

This step enables the SCM cleanup IMOD ($DB2CLEAN) to be spawned every 60 seconds. The time is modifiable (see the “Operation and Customization” chapter for more information.)

To enable SCM, the following changes must be made. 1. Change the parameter SYSTEM CONDITION MONITOR=NO to SYSTEM CONDITION MONITOR=YES in member DB2SSID of the SOURCE library (see the “Operation and Customization” chapter for more information). 2. In the Exception Monitor Control section of the data collector initialization parameters (IDDCPRMS), uncomment the line: SCM-IMOD-NAME=IDB2MEXC

Step 6: Verify the Installation

You must restart the data collector to make the changes from the Basic Installation steps effective.

If you made the changes in the Step 4: Modify the VTAM User Interface (Optional) step, you must also perform the following steps before you continue:

■ Restart the Global Subsystem (GSS).

■ If you made the change in Step 2 (the APPL statement), restart the APPLID

Global View Panel

To verify the SCM Basic Installation, logon to a Unicenter CA-Insight user interface session. From the Main Menu, enter COND on the Command line.

If the SCM has been properly installed, the System Condition Monitor Global View panel appears:

Menu Print Tools Help CA-Insight JBG2

DBV3 Condition System Condition Monitor Item 1-3 of 3 Line codes: S=Show Detail, X=Invoke Monitor (VTAM U/I only) Show * * * Inactive Y Line X X X Name Type System Time Count Condition ------DB23 DB2 S018 16:52:45 92 DBV3 DB2 S018 16:52:45 203 DBNB DB2 S028 16:58:43 20

4–36 System Guide System Condition Monitor (SCM)

The three possible colors for Conditions are red (Problem), yellow (Warning), and green (Okay).

There are as many rows of information (like Subsystem Names) displayed on the Global View panel as there are defined in DB2SSID. See DB2SSID Customization for more information.

Detailed instructions on the customization and use of the System Condition Monitor can be found in the Unicenter CA-Insight User Guide.

If you are using a monochrome (or non-extended attribute) terminal, the panel appears as follows:

Menu Print Tools Help CA-Insight SE19257 DB23

Condition System Condition Monitor Line codes: S=Show Detail, X=Invoke Monitor (VTAM U/I only) Problem x Show Warning x * DB2 B1 Inactive Y Line Ok x Name Type System Time Count Condition ------_ EXPLORE MVS B1 12:55:01 5 Okay _ NET VTAM B1 12:55:01 11 Problem _ CICS311A CICS B1 12:55:00 15 Okay _ DSN DB2 B1 16:10:12 22 Warning _ DB23 DB2 B1 Inactive 0 Okay _ CICS21A CICS B2 12:45:00 18 Warning

In these examples, all of the Conditions have been selected for display (using an x next to each condition type), all Names, Types, and Systems are shown (using an asterisk in the filtering option above each label), and Inactive Systems are shown (using a Y next to Show Inactive).

If at any point during the verification process you encounter an error message, check the Messages Guide for an explanation and suggested corrective action. Also, verify that you followed the preceding installation steps correctly.

Beyond the Basic SCM Installation

Customization of the System Condition Monitor, as well as installation for the support of additional products to be monitored, are in the “Operation and Customization” chapter.

Installing Optional Components 4–37 Using Shadow Catalog Tables for EXPLAIN

Using Shadow Catalog Tables for EXPLAIN

The Unicenter CA-Insight EXPLAIN feature accesses data from the DB2 system catalog tables. Some installations want to restrict the use of these tables and may prefer to define shadow catalog tables for users to access. This section defines how to implement the use of shadow catalog tables. This is optional and is not required.

Two plans are provided to use with the EXPLAIN feature. One plan is known as the system plan and the other as the user plan. The system plan is bound to access the DB2 system catalog tables (it uses a qualifier of SYSIBM). By default, the user plan is also bound to use the DB2 system catalog tables. However, you may define shadow catalog tables (or use existing shadow tables if you have them) and rebind the user plan to use the shadow tables by changing the qualifier used by the user plan. If you change the user plan to use shadow tables, each user can indicate which plan to use the via the PROFILE command. You can control the default setting via the EXPLPLAN value in the DEFAULTS member of the IUIMAPS data set.

Creating and Using Shadow Catalog Tables

If you want to create shadow catalog tables, you will need to do the following. A sample member was created for each DB2 subsystem during the post install in the source library as member db2ssidUSRQ. It was customized based on the table creator, database, and storage group that you specified during the install. You should modify it as per the comments within the member and execute it via SPUFI.

After creating the shadow tables, you should use member db2ssidSSJ to populate the tables and rebind the user plan to use the new catalog tables.

You should also edit and change SPFSLIB member NUXPLANU so that it uses the qualifier for the table you defined (see comments in this member for instructions). You need to do this in case the plans are rebound after applying maintenance.

Using Existing Shadow Catalog Tables

If you want to use existing shadow catalog tables, you should edit and change SPFSLIB member NUXPLANU so that it uses the qualifier for the table you want to use (see comments in this member for instructions). Once you change this member, you should regenerate your BIND statements and rebind the Unicenter CA-Insight plans so that the shadow tables will be used.

4–38 System Guide Using Shadow Catalog Tables for EXPLAIN

Optionally Create Table Indexes to Speed Performance

Some of the DB2 catalog tables do not, by default, have indexes which leads to very poor performance when accessing these tables. SOURCE member db2ssidCATI was generated during the post install and contains sample SQL to create indexes for these tables. It was customized based on the table creator, database, and storage group that you specified during the install. You should modify it as per the comments within the member and execute it via SPUFI. After successfully creating the indexes, you should rebind the Unicenter CA-Insight plans.

For additional details on the use of shadow tables, see the “Shadow Table for EXPLAIN” appendix.

Installing Optional Components 4–39

Chapter 5 Operation and Customization

This chapter provides information about operating Unicenter CA-Insight, an overview of the various methods Unicenter CA-Insight can use to collect DB2 data, and how you can customize Unicenter CA-Insight.

Data Collector Operation and Customization

The section details how to operate and customize the data collector.

When a data collector is started, a set of initialization parameters are read from the data set specified on the SYSPARMS DD statement. (See Customizing Data Collector Initialization Parameters for a detailed list of initialization parameters.) These parameters are used to tailor the data collector’s environment for the DB2 to be monitored. You can modify these parameters during installation and periodically thereafter to meet your site’s changing DB2 monitoring requirements. Some SYSPARMS parameters can be overridden at runtime (see Parameters You Can Override).

After initialization, the data collector attempts to connect to the DB2 subsystem specified in SYSPARMS. If the DB2 subsystem is not active, the data collector terminates or waits to be notified by DB2 (POSTed) that it is active. The DBWAIT parameter (see Customizing Data Collector Initialization Parameters) controls whether the data collector will terminate or wait for DB2 to start.

Once connected, the data collector obtains control block storage and issues a specific enqueue identifying the monitored DB2 subsystem. The data collector then checks the syntax of and starts all IQL requests included in the data stream specified on the DBGIN DD statement (see Startup Requests for more information).

The data collector continually collects accounting and event trace data and control block data while connected to DB2. This data is used to produce requested displays, reports, or other types of output files. In addition, users can interactively control the display of real-time data by starting, stopping, pausing, and resuming IQL requests.

Operation and Customization 5–1 Data Collector Operation and Customization

The data collector terminates when one of the following events occurs:

■ An MVS operator STOP command is issued specifying the data collector jobname, or

■ The DB2 subsystem terminates and NONSTOP=NO is specified as an initialization parameter

■ The data collector encounters an ABEND it cannot resolve

The data collector shuts down in an orderly fashion regardless of whether termination is normal or abnormal. Termination frees all allocated resources, which it has obtained including data sets and CSA storage and stops all DB2 traces it has started.

Starting the Data Collector

The data collector can be executed as a batch job or as a started task. On the following pages you will find samples of a batch job JCL stream and a started task procedure (both from the SOURCE library) along with explanations of all statements and parameters.

Batch Job JCL Example

The batch data collector JCL is generated during post install as member name db2ssidDCJ in the SOURCE library. The following JCL sample can be found in the SOURCE library in member db2ssidDCJ. You use this member to execute the data collector as a batch job. Typically, this JCL member is customized during basic installation. //jobcards //* //*------//* CA-INSIGHT FOR DB2 INSTALLATION - DATA COLLECTOR JCL FOR D71A //* //* FUNCTION: JCL TO INVOKE THE CA-INSIGHT DATA COLLECTOR. //* A DATA COLLECTOR MUST BE ACTIVE FOR EACH DB2 //* SUBSYSTEM TO BE MONITORED. //* //*------//* //IDB2DC EXEC PGM=NSIGHTDC,REGION=6M,DPRTY=(14,15),TIME=1440, //* PERFORM=5, // PARM='/DBSUB=D71A,DBWAIT=YES,DBLOC=CA31D71A' //* PARM='/DBSUB=D71A,DBWAIT=YES' //* //STEPLIB DD DISP=SHR, // DSN=PTIPROD.RP01B.LOADLIB //*

5–2 System Guide Data Collector Operation and Customization

//SYSPARMS DD DISP=SHR, DATA COLLECTOR SYSPARMS // DSN=IDB2.WRK063S.P01B.SOURCE(IDDCPRMS) // DD DISP=SHR,DSN=IDB2.WRK063S.P01B.SOURCE(APPLS) // DD DISP=SHR,DSN=IDB2.WRK063S.P01B.SOURCE(D71ASYSP) //* //DBGIN DD DISP=SHR, STARTUP REQUESTS // DSN=IDB2.WRK063S.P01B.SOURCE(STARTUP) //* //HSTIN DD DISP=SHR, HISTORY REQUESTS // DSN=CIDB.WRK063S.TGTREQ(HISTREQ) //* //HSTPARMS DD DISP=SHR, HISTORY CONTROL FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTPARMS //* //HSTSTATA DD DISP=SHR, HISTORY SYSTEM STATS - A FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTSTATA //HSTSTATB DD DISP=SHR, HISTORY SYSTEM STATS - B FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTSTATB //HSTACCTA DD DISP=SHR, HISTORY THREAD ACCT - A FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTACCTA //HSTACCTB DD DISP=SHR, HISTORY THREAD ACCT - B FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTACCTB //* //SECURITY DD DISP=SHR,FREE=CLOSE, SECURITY FILE // DSN=IDB2.WRK063S.P01B.SECURITY //* //EXCPDEF DD DISP=SHR, EXCEPTION DEFINITIONS // DSN=IDB2.WRK063S.P01B.EXCPDEF //* //OBIDTBL DD DISP=SHR, OBID TRANSLATIONS // DSN=IDB2.WRK063S.P01B.D71A.OBID //* //UDBSCHED DD DISP=SHR, 24X7 SCHEDULES // DSN=IDB2.WRK063S.P01B.SOURCE(SCHEDULE) //* //DBGPRINT DD SYSOUT=* DIAGNOSTIC INFORMATION //UDBOUT DD SYSOUT=* 24X7 OUTPUT //SYSUDUMP DD SYSOUT=* //DBGSNAP DD SYSOUT=*

JCL Procedure Explanation

An explanation of each JCL statement and parameter follows: jobcards (required) Contains a jobname and other parameters according to your conventions regarding installation job naming and JOB card parameter specification. The USER keyword must contain a user ID defined to DB2 that has TRACE, MONITOR1, and MONITOR2 privileges. The user ID length is from 1-7 characters.

Operation and Customization 5–3 Data Collector Operation and Customization

IDB2DC EXEC (required) Invokes the data collector program and specifies the available region size.

■ DPRTY=(xx,xx) Should be specified to place the data collector dispatching priority above the DB2 to be monitored and any connections to the DB2 (except the IRLM). We recommend the following dispatching priority scheme, from highest to lowest: – IRLM – Data collector – DB2 systems services address space (SSAS) – DB2 database address space (DBAS) – DB2 connections

■ TIME=1440—Specified to bypass step termination if the data collector is in a continuous wait for longer than the SMF wait time limit.

■ PERFORM=—Should specify a defined performance class that will ensure good response for the data collector. To specify the performance class, uncomment this line in the sample JCL. Note: It should be at least equal, if not higher, than that defined for the DB2 subsystem, so that trace buffers from DB2 can be continually processed without loss of trace data.

■ PARM=—Field overrides for certain data collector initialization parameters whose defaults are established in the SYSPARMS initialization parameter file. For more information about these parameters, see Parameters You Can Override. To use this override function, uncomment this line in the sample JCL. STEPLIB Is normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules. SYSPARMS (required) Points to the data collector initialization parameters. These describe the DB2 subsystem that is to be monitored, along with other parameters describing the environment. This DD statement normally points to a member in a PDS since the input consists of only a small number of 80-byte records. See Customizing Data Collector Initialization Parameters for a complete explanation of the data collector parameters. DBGIN (required) Points to the Startup Request file that identifies requests, which are to be started during data collector initialization (see Startup Requests). Note: This statement must be present even if there are no startup requests.

5–4 System Guide Data Collector Operation and Customization

HSTIN (optional) Points to the HISTREQ member of the Unicenter CA-Insight TGTREQ library that contains requests that are to be started to collect Online History data. SECURITY (optional) Points to a sequential file of records, generated by an installation, each of which defines the default capabilities and limits for a specific user ID or group ID. This DD statement is required only when the Security Parameters specify SECURITY=YES and you want to define individual or group security “profiles” by user ID. See Security Control for detailed information about this feature. EXCPDEF (required) Allocates a file that contains exception definitions distributed with Unicenter CA-Insight. This file is also used to store exception definitions you create and modify. HSTPARMS (required) Allocates the data set used to synchronize the dumping of the Online History files. HSTSTATA and HSTSTATB (optional) However, the basic installation procedures assume their use. These statements allocate the Online History data sets used to collect DB2 subsystem statistics records. If you want to view these recent past statistics online and possibly archive the data for long-term review, you must allocate and initialize these data sets. See the “Online History” chapter for detailed information. HSTACCTA and HSTACCTB (optional) However, the basic installation procedures assume their use. These statements allocate the online history data sets used to collect DB2 thread accounting records. If you want to view these recent past accounting records online or possibly archive the data for long-term review, you must allocate and initialize these data sets. See the “Online History” chapter for detailed information. OBIDTBL (optional) Allocates the OBID translation table that contains data extracted from the DB2 catalog. Note: We recommend its use for reporting clarity. UDBSCHED (optional) Specifies the name of a sequential data set or PDS member that contains the set of scheduled Unicenter CA-24X7 commands.

Operation and Customization 5–5 Data Collector Operation and Customization

DBGPRINT (required) Points to the destination for the data collector system messages file. If a permanently allocated data set is specified with a disposition of SHR, and enough space is allocated for anticipated message traffic, it can be BROWSEd from TSO during execution. SYSUDUMP (optional) Points to a destination for any abend dumps which can occur during execution. DBGSNAP (optional) Points to an optional ABEND dump data set when FULLDUMP=NO is specified in SYSPARMS.

Started Task Procedure Sample

The started task JCL procedure is generated during post install as member name db2ssidDCS in the SOURCE library. It may have also been generated in your PROCLIB data set under a different member name during post-installation processing. If you did not have the started task created in PROCLIB, you may copy the db2ssidDCS member from the SOURCE library to your PROCLIB data set. This member is used to execute the data collector as a started task. //* //*------//* CA-INSIGHT FOR DB2 INSTALLATION - DATA COLLECTOR JCL FOR D71A //* //* FUNCTION: JCL TO INVOKE THE CA-INSIGHT DATA COLLECTOR. //* A DATA COLLECTOR MUST BE ACTIVE FOR EACH DB2 //* SUBSYSTEM TO BE MONITORED. //* //*------//* //D71ADC PROC DBSUB=D71A, // DBWAIT=YES, // DBLOC=CA31D71A, // PRT='*', // SYSP=D71ASYSP, // REQ=STARTUP, // PER=5 //D71ADC EXEC PGM=NSIGHTDC,REGION=6M,TIME=1440,DPRTY=(14,15), // PERFORM=&PER,PARM='/DBSUB=&DBSUB,DBWAIT=&DBWAIT,DBLOC=&DBLOC' //* PERFORM=&PER,PARM='/DBSUB=&DBSUB,DBWAIT=&DBWAIT' //* //STEPLIB DD DISP=SHR, // DSN=PTIPROD.RP01B.LOADLIB //* //SYSPARMS DD DISP=SHR, DATA COLLECTOR SYSPARMS // DSN=IDB2.WRK063S.P01B.SOURCE(IDDCPRMS) // DISP=SHR,DSN=IDB2.WRK063S.P01B.SOURCE(&SYSP) //* //DBGIN DD DISP=SHR, STARTUP REQUESTS // DSN=IDB2.WRK063S.P01B.SOURCE(&REQ) //*

5–6 System Guide Data Collector Operation and Customization

//HSTIN DD DISP=SHR, HISTORY REQUESTS // DSN=PTIPROD.RP01B.TGTREQ(HISTREQ) //* //HSTPARMS DD DISP=SHR, HISTORY CONTROL FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTPARMS //* //HSTSTATA DD DISP=SHR, HISTORY SYSTEM STATS - A FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTSTATA //HSTSTATB DD DISP=SHR, HISTORY SYSTEM STATS - B FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTSTATB //HSTACCTA DD DISP=SHR, HISTORY THREAD ACCT - A FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTACCTA //HSTACCTB DD DISP=SHR, HISTORY THREAD ACCT - B FILE // DSN=IDB2.WRK063S.P01B.D71A.HSTACCTB //* //SECURITY DD DISP=SHR,FREE=CLOSE, SECURITY FILE // DSN=IDB2.WRK063S.P01B.SECURITY //* //EXCPDEF DD DISP=SHR, EXCEPTION DEFINITIONS // DSN=IDB2.WRK063S.P01B.EXCPDEF //* //OBIDTBL DD DISP=SHR, OBID TRANSLATIONS // DSN=IDB2.WRK063S.P01B.D71A.OBID //* //UDBSCHED DD DISP=SHR, 24X7 SCHEDULES // DSN=IDB2.WRK063S.P01B.SOURCE(SCHEDULE) //* //DBGPRINT DD SYSOUT=&PRT DIAGNOSTIC INFORMATION //UDBOUT DD SYSOUT=&PRT 24X7 OUTPUT //SYSUDUMP DD SYSOUT=&PRT //DBGSNAP DD SYSOUT=&PRT

JCL Procedure Explanation

An explanation of each JCL statement and parameter follows: db2ssidDC PROC Is required if the procedure contains symbolic parameters for which default values are to be specified.

■ The DBSUB symbolic parameter lets the operator specify the DB2 subsystem for which the data collector is to be started, overriding the subsystem name in the file specified in the input parameter file. The subsystem name has a maximum length of four (4) characters.

■ The DBWAIT specification also overrides the value specified in the input parameter file. A value of YES causes the data collector to wait for DB2 to start if it is not already active.

■ The DBLOC parameter overrides the value specified in the input parameter file. The DB2 Location must be enclosed within single quotes.

■ PRT allows for changing the SYSOUT class from the default.

■ The SYSP and REQ symbolic parameters specify the member names of the files to be used for the SYSPARMS and DBGIN statements, respectively.

■ PER indicates the performance class to be used by the data collector.

Operation and Customization 5–7 Data Collector Operation and Customization

db2ssidDC EXEC Invokes the data collector program and specifies the available region size. The run-time parameters are configured through the symbolic parameter values previously described.

The purpose of the remainder of the DD statements in the Started Task procedure is identical to those already described in Batch Job JCL Example.

Starting the Data Collector as a Started Task

When the data collector procedure is in the procedure library (for example SYS1.PROCLIB), you can issue the MVS START command from the MVS console to start it. For example, use the following command to start the data collector procedure stored as member IDB2DCS: S IDB2DCS

Started Task Options

To start the data collector and override some of the defaults from the PROC statement, such as DB2 subsystem name and whether to wait if DB2 is not active, use a command similar to the following: S IDB2DCS,DBSUB=DB2T,DBWAIT=NO

Stopping the Data Collector

Recommended Procedure

The data collector normally stops when the monitored DB2 subsystem stops (when NONSTOP=NO is specified) or when the MVS operator explicitly stops it with the MVS STOP command.

Use the following command to stop the data collector started in the previous section: P IDB2DCS

Use the STOP command to stop the data collector whether it was started as a job or as a started task. The program might not terminate immediately, but we recommend that you wait for proper termination, because repeated STOP commands will be ignored.

5–8 System Guide Data Collector Operation and Customization

Optional Procedure

The data collector can also be stopped with the MVS CANCEL command. If this is done, the data collector will clean up the resources it has acquired. However, we do not recommend stopping the data collector this way. If you choose to CANCEL the data collector, be aware that because of the its multitasking architecture, you might need to issue multiple CANCEL commands before termination is successful.

Also, be aware that if some DB2 thread is in a long-running ROLLBACK as part of thread termination, other threads will be queued for termination. The data collector could go into a wait state if any of its DB2 Interface threads are queued for termination. Use the DB2 -DISPLAY THREAD(*) command to determine if the data collector threads are in QD (queued for deallocation) status.

If NONSTOP=NO is specified and DB2 is terminated normally. The data collector will not terminate until all other active threads have been terminated.

Operator Commands

Data collector includes two display commands and commands to start and stop connections between the data collector and other external address spaces.

The display commands, USERS and IFI, give you information about the data collector itself.

■ The USERS command displays the users currently logged on.

■ The IFI command displays how many buffers and trace records the data collector has processed since it was started.

You can use these commands from an MVS console or from the Commands panel that can be accessed from the Tools menu.

USERS

For TSO, the USERS command lists the User ID, the literal value of “NONRAF” for LU name and the address space IDs (ASID) of all Unicenter CA-Insight users currently connected to the specified data collector as shown by ssid and jobname pppppppp. The asid is shown as a decimal number.

For VTAM, the USERS command lists the User ID, the VTAM LU name and the address space ID of the VTAM user interface task. For those users connected through the Remote Access Facility, the command displays the User ID, the LU name and the literal value “VTAM” for ASID.

Operation and Customization 5–9 Data Collector Operation and Customization

Use the following command from the MVS console (where jobname is the name of the data collectors shown by pppppppp): F jobname,D USERS

From the Command panel, issue the following command: USERS

The following is an example of the USERS display:

CA-INSIGHT USERS CONNECTED TO ssid DATA COLLECTOR pppppppp USER UNAME ASID USER LUNAME ASID USER LUNAME ASID USERxx LO3N454 287 USERxx NONRAF 51 USERxx LO6N512 VTAM

In the example, three Unicenter CA-Insight users are connected to the data collector; one native VTAM user, one TSO user and one Remote Access Facility user.

IFI

The IFI command displays current data collector trace buffer statistics and the number of trace records processed through the buffers. This resulting report displays the following information:

■ The size of the trace buffers (MONSZ)

■ The size of the private area buffer into which online trace record buffers are copied (PRVSZ)

■ The number of buffers passed because a time threshold was exceeded (BY TIME)

■ The number of buffers passed because the buffer was full (POSTED)

■ The total number of buffers passed to the data collector (TOTAL)

■ The report also displays the following information about the trace records that have been collected:

■ The total number of trace records passed in the buffers (RECORDS)

■ The number of trace records lost due to unavailable SRV or IFI buffers (LOST)

■ The number of records truncated due to an SRV size limitation (TRUNC; applies only if IFI=NO or IFI=READS)

■ The DB2 trace record number (IFCID), an indicator literal of “A” or “I” specifying the current status of the IFCID as Active or Inactive, and the number of records that have been collected for that record (NUMBER). Only non-zero values display for Inactive IFCIDs. Zero values for an Active IFCID shows no records have been collected yet for that IFCID.

5–10 System Guide Data Collector Operation and Customization

The following is an example of output from the IFI command. Similar statistics are written to the DBGPRINT system messages file when the data collector is terminated.

IFI STATISTICS FOR ssid DATA COLLECTOR MONSZ PRVSZ BY TIME POSTED TOTAL RECORDS LOST | 256K 512K 85 9 94 7055 0 IFCID NUMBER IFCID NUMBER IFCID NUMBER IFCID NUMBER 3 A 64 4 A 24 5 A 21 6 A 255 7 A 255 8 A 28 9 A 81 10 A 3 13 I 1 14 I 1 15 I 173 16 I 17 17 I 13 18 I 198 20 A 14 21 A 2729 22 A 4 23 A 0 24 A 0 25 A 0 38 A 0 39 A 0 44 A 3 45 A 3 53 A 107 54 A 0 58 A 836 59 A 517 60 A 0 61 A 301 62 A 1 63 A 12 64 A 6 65 A 6 66 A 5 68 I 2

Note: If you want to view IFI statistics from the MVS console, issue this command: F data-collector-task,D SRVSTATS

Canceling a User Interface Session

You might need to cancel a signed-on Unicenter CA-Insight user. This can happen if the user has somehow exited the user interface without going through the Unicenter CA-Insight termination routines. This could leave the user connected to the data collector control blocks and unable to sign on again with the same user ID. To terminate that user with the data collector, the operator must enter a data collector CANCEL command or, more drastically, take down the data collector and bring it back up.

Canceling a TSO or VTAM User

To cancel a TSO or VTAM user, use the following cancel command: F jobname,C U=userid

where F is the standard abbreviation for the MVS MODIFY command, jobname is the jobname of the data collector, and userid is the logon user ID of the Unicenter CA-Insight user to be canceled.

Canceling a Remote Access Facility User

When the Remote Access Facility is active and the user to be canceled is located on another operating system in the network, the user ID specified in the cancel command must be the VTAM LU name. Use the USERS display command (see Operator Commands) to determine the user ID or VTAM LU to specify.

Operation and Customization 5–11 Data Collector Operation and Customization

Remote Access Facility Commands

The data collector provides two commands for the control of the Remote Access Facility. These commands use the MVS MODIFY command interface to pass the request to the data collector.

To request a Remote Access Facility function, use the following command: F jobname,c VTAMTASK

where F is the standard abbreviation for the MVS MODIFY command, jobname is the jobname of the data collector, c is the command (see the following) and VTAMTASK is a literal that tells the data collector that the command will operate on the Remote Access Facility task.

The two Remote Access Facility commands are S for starting and P for stopping the Remote Access Facility:

■ Use the S (start) command if the Remote Access Facility is not active when the data collector is started or if it becomes inactive while the data collector is running. If either is true, the start command will reactivate the Remote Access Facility when it is ready.

■ Use the P or STOP command to deactivate the Remote Access Facility. For example, you can use it to make a data collector available only to Unicenter CA-Insight users who are resident on the MVS system on which the data collector is running.

For more information about the Remote Access Facility, see the “Installing Optional Components” chapter.

Switch History Files Command

You can use the SWITCH command to force the data collector to switch the accounting file, the statistics file, or both files.

To switch the files use the following command: F jobname,SWITCH {ACCT | STAT | ALL}

where F is the standard abbreviation for the MVS MODIFY command, jobname is the jobname of the data collector, SWITCH is the command, and ACCT|STAT|ALL is a required parameter which indicates which files to switch.

Note: SYSOPR needs to be authorized to issue the switch command by having HISTORY-SWITCH=YES in the security profile for SYSOPR.

5–12 System Guide Data Collector Operation and Customization

Issuing Unicenter CA-24X7 Commands from the Console

You can issue Unicenter CA-24X7 commands from a console interface using the data collector by using a modify command (F).

To issue a Unicenter CA-24X7 command, use the following command format: F datacollector,24X7 24X7command

where F is the standard abbreviation for the MVS MODIFY command, datacollector is the started task name of the data collector, and 24X7command is one of the commands listed in this guide.

Note: When the data collector processes the Unicenter CA-24X7 command, it uses an authorization ID of “SYSOPR.” Thus, for the command to be successful, SYSOPR must be authorized to perform the appropriate Unicenter CA-24X7 command as defined in the security data set.

Example

In this example, the logload size is increased by ten percent using data collector GSWU42V3. F GSWU42V3,24X7 SET LOGLOAD VALUE(+10%)

Dynamically Starting and Stopping the Unicenter Agent for DB2

If you have the Unicenter Agent for DB2 installed to run under the data collector, you can dynamically start and stop the agent by using the following console commands.

Issue the following command to dynamically start the agent, even if UNICENTER-AGENT=NO is specified in SYSPARMS: F datacollector,S AGENT

You can restart the agent anytime after the agent has terminated. Note that if the agent was previously terminated due to DB2 terminating, the data collector will automatically restart the agent when the DB2 subsystem becomes active.

Issue the following command to stop the agent: F datacollector,P AGENT

See Unicenter Agent for DB2 for more information about the agent.

Operation and Customization 5–13 Data Collector Operation and Customization

How the Data Collector Uses DB2

This section describes the DB2 facilities used by the data collector and how your actions can influence the data collector’s use of DB2. With this knowledge, you can choose the data collector parameters that are correct for your installation.

Basic Attachment to DB2

We use a facility that is similar to the DB2 Call Attach Facility (CAF) to connect to DB2. With our multi-task architecture, three tasks require access to DB2, so three threads will be allocated.

Authorization IDs

The DB2 authorization ID for the data collector must have TRACE, MONITOR1 and MONITOR2 privileges (only TRACE is needed if you are not using the IFI; see IFI versus Non-IFI). Determining which authorization ID to use can be difficult due to how authorization IDs are assigned to DB2 threads.

When running the data collector as a submitted job, you can assign an authorization ID by including a USER= parameter on the JOB statement. When running as a started task, however, the authorization ID must be assigned in other ways, depending on the security package at your installation. For example, if your security package is RACF, you can assign a user ID to a started task by modifying the RACF Started Task Table, in the same way that you assign a user ID to the DB2 started tasks. If you do not do this, the data collector started task will have no user ID associated with it at the time it connects to DB2, and therefore it will be assigned the IBM default authorization ID set in the DB2 parameters (usually IBMUSER).

If you have customized the DB2 authorization exit, DSN3@ATH, be sure that it allows the data collector to operate.

Authorization ID for DB2 Commands

The authorization ID used for DB2 commands issued from the user interface is the user’s Unicenter CA-Insight logon ID. For the TSO user interface, this is the user’s TSO logon ID. For the VTAM user interface, this is the ID specified by the user on the Unicenter CA-Insight Logon ID panel.

5–14 System Guide Data Collector Operation and Customization

IFI versus Non-IFI

The DB2 Instrumentation Facility Interface (IFI) provides a standard way to monitor the activities of DB2 online. It enables monitoring programs to invoke three types of functions: sample current activity and status (READS function), collect event trace records online (READA function), and issue DB2 commands (COMMAND function). When you specify IFI=YES in the data collector parameters, Unicenter CA-Insight uses the IFI for most control block sampling and all online event tracing. (See Customizing Data Collector Initialization Parameters for more information.)

In addition, Unicenter CA-Insight provides an alternative to the IFI. You want to use this if you are having problems with the IFI as indicated by error messages in the data collector DBGPRINT system messages file, or if you do not wish to incur the nominal IFI overhead. When you specify IFI=NO, Unicenter CA-Insight uses its own routines for control block sampling and online event tracing. When operating in this mode, however, some information about locks currently held by threads is not available.

A third alternative allows a partial implementation of IFI. Specifying IFI=READS lets Unicenter CA-Insight use IFI for control block sampling, including current lock activity, and memory-efficient Unicenter CA-Insight routines for online event tracing.

The “Beyond the Basic Installation” chapter, describes how to install Unicenter CA-Insight with IFI=YES. Installing the Data Collector Without the IFI describes the modifications to the basic installation needed to monitor DB2 without using the IFI.

Data Collector Buffer Sizes

If you are running IFI=YES, Unicenter CA-Insight is reading DB2 Trace records from an OP buffer. In this case the SRVBUFSZ and SRVBUFNUM control the size of the OP buffer. The maximum size for the entire OP buffer is 1024K.

If you are running IFI=READS or IFI=NO, Unicenter CA-Insight is using an SRV buffer. The maximum size for an entire SRV buffer is 1600K.

The PRVMAXSZ parameter is the total amount available for OP or SRV buffers in the data collector’s address space unless the initial allocation of PRV buffer areas is larger.

Operation and Customization 5–15 Data Collector Operation and Customization

The PRV buffer is where the data collector receives the DB2 trace records from the OP or SRV buffers.

The PRV buffer size is set automatically if you run IFI=YES. If you run IFI=READS or IFI=NO, you can alter the size. A good rule of thumb is that private buffers should be at least 50% larger than SRV buffers.

About Traces

The end result of the options previously described, along with the data collection specifications in the requests, is one or more DB2 traces. This section describes the DB2 trace types, their classes, their destination, the effect of starting and stopping requests, and how Unicenter CA-Insight can collect performance data without a performance trace.

DB2 Trace Destination

The IFI parameter controls the destination of the Unicenter CA-Insight traces. If IFI=YES, the destination is usually OP1, for Online Performance monitor buffer number 1. If other performance monitoring programs using the IFI are active, Unicenter CA-Insight will be assigned the next destination number in sequence, so you could see destination OP2 or OP3.

If IFI=NO or IFI=READS is specified, then the destination is SRV, or serviceability. An SRV trace uses what is essentially an exit routine in DB2 (Unicenter CA-Insight-supplied module DSNWVSER) to process trace records online.

DB2 Trace Types

An accounting trace causes DB2 to write an accounting record when a thread terminates. The Class parameter controls how detailed the timing information is on the accounting record.

A performance trace causes DB2 to write many different event trace records. The Class parameter controls what type of records to write by controlling what events to trace.

5–16 System Guide Data Collector Operation and Customization

A monitor trace is a different, more comprehensive type of trace, used specifically by performance monitoring programs. A monitor trace can “include” an accounting trace, performance traces and functions that are not related to traces, like control block sampling. The Class parameter controls what the monitoring program can do. Monitor Class 1 enables the monitoring program to do control block sampling and, if trace record buffering information is provided, to collect event trace records, including accounting, statistics, performance and audit records. Monitor Class 2 and 3 have the same effect as accounting class 2 and 3, that is, to collect the more detailed timing information for threads. DB2 V3 allows for additional monitor classes. Class 5 collects additional IFI information. Classes 7 and 8 are provided to collect more detailed information about packages.

The data collector IFI= parameter controls the type of DB2 trace that Unicenter CA-Insight starts. You will see one of several combinations of DB2 traces when Unicenter CA-Insight is active, depending on your IFI parameter selection.

If you selected IFI=YES, Unicenter CA-Insight starts one monitor (MON) trace. If you selected IFI=NO, Unicenter CA-Insight starts one accounting (ACCTG) and one performance (PERF) trace. If you selected IFI=READS, Unicenter CA-Insight starts a MON and a PERF trace.

Trace Classes

The class of trace Unicenter CA-Insight chooses depends on several factors:

■ Account Trace Classes—The data collector ACCTTRACE parameter affects the class of monitor or accounting trace. This parameter lets you control how much detailed timing information you want to see for active threads and on the accounting record.

■ The default value, ACCTTRACE=YES, causes the data collector to collect class 1, 2 and 3 accounting data by starting a ACCTG CLASS(1,2,3) or MON CLASS(1,2,3) trace for both DB2 V2 and V3.

■ With ACCTTRACE=1 or ACCTTRACE=2, the data collector starts only the classes of accounting or monitor trace up to the class number specified. Starting with DB2 V3, the highest class value can be 8. All classes up to and including the specified number will be started (except for classes 4 and 6).

■ With ACCTTRACE=NO, the data collector will not start an accounting trace unless a request that uses the accounting record is active. In this case, if IFI=YES, then you will still see a MON CLASS(1) trace active. If IFI=NO or IFI=READS, you will see no ACCTG trace.

Operation and Customization 5–17 Data Collector Operation and Customization

■ An ACCTTRACE=(n,n,n,...) can also be used to specify a list of the accounting or monitor classes to be started. Only the listed classes will be started with the trace.

YES NO 1 2 IFI=YES MON 1,2,3 MON 1 MON 1 MON 1,2 IFI=NO ACCT 1,2,3 PERF 1,2,3,10 ACCT 1 ACCT 1,2 IFI=READS MON 1,2,3 MON 1 MON 1 MON 1,2 PERF 29 PERF 29 PERF 29 PERF 29

The following chart summarizes this information for DB2 V3 and later:

YES NO 1 2 3 5 7 8 IFI=YES MON MON 1 MON 1 MON 1,2 MON MON MON MON 1,2,3 1,2,3 1,2,3 1,2,3,5,7 1,2,3,5,7,8 IFI=NO ACCT PERF ACCT 1 ACCT 1,2 ACCT ACCT ACCT ACCT 1,2,3 1,2,3, 10 PERF 29 PERF 29 1,2,3 1,2,3,5 1,2,3,5,7 1,2,3,5,7,8 PERF 29 PERF 29 PERF 29 PERF 29 PERF 29 IFI=READS MON MON 1 MON 1 MON 1,2 MON MON MON MON 1,2,3 PERF 29 PERF 29 PERF 29 1,2,3 1,2,3,5 1,2,3,5,7 1,2,3,5,7,8 PERF 29 PERF 29 PERF 29 PERF 29 PERF 29

One reason to have this amount of control is that the DB2 Instrumentation Facility has only one accounting component to service all accounting traces. Any class 3 accounting trace affects all accounting traces.

Performance Trace Classes

Performance trace classes are not used by Unicenter CA-Insight. You use a performance trace class as a shorthand way of telling DB2 to collect certain types of trace records; each class consists of many trace record types. However, Unicenter CA-Insight is easily able to keep track of trace record types individually. It will determine exactly what types of trace records are needed by a request, and it will start and stop performance trace records individually, and not by class. Unicenter CA-Insight collects only the trace record types needed to satisfy the active requests.

If your data collector is using IFI=NO or IFI=READS, you will see a performance trace active with class 29. Class 29 has no trace records currently defined for it.

5–18 System Guide Data Collector Operation and Customization

How Unqualified Requests Affect Traces

While data collector parameters IFI and ACCTTRACE affect the trace types, accounting classes and destination, the Unicenter CA-Insight requests determine the actual trace records that are to be collected. In other words, instead of starting a separate performance trace with a specific class, or group, of trace records, Unicenter CA-Insight uses just one trace type for all event trace records, dynamically modifying the list of trace records associated with that trace as requests start and stop.

For example, suppose Unicenter CA-Insight is not currently collecting SQL trace records and you start a request that uses that trace record. Unicenter CA-Insight first determines if the requested trace record is already being collected.

■ If it is, then no modification to the Unicenter CA-Insight trace is done; the new request will share the trace record with any other requests using the record.

■ If the record is not being collected, as in our example, then Unicenter CA-Insight modifies the DB2 trace to start collecting the specific trace records needed for that request. In the example, Unicenter CA-Insight collects beginning and ending SQL trace records.

Now, let us assume that you want to stop the request. When you stop a request, Unicenter CA-Insight determines if any other requests are using the trace records used by the stopped request.

If there are none, then Unicenter CA-Insight modifies the trace to stop the collection of that trace record. In our example, when you stop your SQL trace request, Unicenter CA-Insight stops the collection of the SQL trace records, because no other request needs them.

Qualified DB2 Traces

Under certain circumstances, Unicenter CA-Insight starts a qualified DB2 trace to further reduce the overhead of a request. With a qualified DB2 trace, DB2 writes trace records only for those plans and/or authorization IDs that meet the qualification parameters specified on the -START TRACE command. Unicenter CA-Insight starts a qualified DB2 trace any time you start an Application Probe from the Application Developers menu, or when you start a request and provide a PLAN and/or AUTHID qualifier on the Start Qualification panel. Unicenter CA-Insight starts a separate DB2 trace with a separate trace number (TNO) with the specified AUTH and/or PLAN parameters.

Operation and Customization 5–19 Data Collector Operation and Customization

Because there is a limit on the number of DB2 traces that can be active at any one time, Unicenter CA-Insight provides a way for you to set a limit on the number of traces that can be started from Unicenter CA-Insight. The data collector parameter NUMTRACES names (see Customizing Data Collector Initialization Parameters for information about the NUMTRACES names). The maximum number of DB2 traces that can be started by Unicenter CA-Insight, including both the initial traces (summarized in the tables in Trace Classes) and any qualified traces started after initialization.

Installing the Data Collector Without the IFI

The DB2 Instrumentation Facility Interface was introduced in DB2 Version 2.1 to facilitate online performance monitoring. The IFI is the preferred way for Unicenter CA-Insight to get DB2 performance data, but it is not the only way. If you need to monitor a DB2 subsystem that is having problems with the IFI, then you need to change the basic installation so that Unicenter CA-Insight can monitor the subsystem without the IFI. This section describes those changes. More information can be found in How the Data Collector Uses DB2.

Monitoring a DB2 Subsystem without IFI

When monitoring a DB2 subsystem, the data collector IFI parameter controls how Unicenter CA-Insight gets DB2 data. (See Customizing Data Collector Initialization Parameters for more information about the IFI parameter.)

The Basic Installation assumed that the IFI parameter value was YES, meaning that the data collector will use the IFI for both control block sampling and collecting event traces. The other IFI parameter values allow Unicenter CA-Insight to use the IFI for only control block sampling (IFI=READS), or to ignore the IFI altogether (IFI=NO). To monitor DB2 with either of these options, make the following changes in the Basic Installation:

For IFI=NO, grant the TRACE privilege to the data collector: GRANT TRACE TO authid

For IFI=READS, grant the TRACE, MONITOR1 and MONITOR2 privileges to the data collector. GRANT TRACE, MONITOR1, MONITOR2 TO authid

For both options, copy member DSNWVSER from the Unicenter CA-Insight load library into a library available to the DB2 subsystem (STEPLIB, DSNEXIT, and so on). DB2 load this module at the time the data collector is started. Usually there is no module with this name in any DB2 load libraries. If there is, our copy must be ahead of, or replace, the other module with this name.

5–20 System Guide Data Collector Operation and Customization

Prepare System Parameters

In addition to the changes specified in the basic installation, change the data collector parameter value to IFI=NO or IFI=READS.

Note: Certain reports are not available when monitoring a subsystem with IFI=NO. See IFI versus Non-IFI for more information.

Customizing Data Collector Initialization Parameters

The input parameters used by the data collector during its initialization are obtained from the files described by the SYSPARMS DD statement in the startup JCL. See Starting the Data Collector and Stopping the Data Collector for more information about input parameters. The parameters specified in these files indicate:

■ The DB2 subsystem to be monitored

■ The default data set options for a data set to be dynamically allocated for a request

■ The size and number of buffers to be acquired for DB2 trace record processing

■ Whether any of the optional features are to be enabled.

The data collector runtime system parameters (SYSPARMS) are generated into three members of the SOURCE library by the post install process, which are all concatenated together to form the SYSPARMS for a data collector.

■ The IDDCPRMS member contains the SYSPARM settings that you want to use for all your data collectors (common SYSPARMS).

■ A DB2-specific set of SYSPARMS are created for each data collector with the member name db2ssidSYSP (for example, XYZSYSP for DB2 subsystem XYZ). You may move parameters from the common IDDCPRMS member to the DB2-specific members and vice versa, if you wish.

■ The third SYSPARM member, the APPLS member, contains the APPLS SYSPARM parameter setting. It is built and update dynamically during the DB2-specific post install. It is used by all of the data collectors as well as the Unicenter CA-Insight user interface.

DEFAULTS Statement

DEFAULTS must be the first word on the first input record in the input parameter file, unless the first record consists of a comment.

Operation and Customization 5–21 Data Collector Operation and Customization

Keywords

This section describes all of the allowable keywords. The underlined value (if any) for each keyword is the default value, which is used only if no value is specified in the input parameter file.

Note: Some values (such as prodcode, hlq) were initially populated during post install process.

Identification Parameters

The identification parameters allow operation of the product and identify the subsystem to be monitored: DBSUB=DB2NAME /* DB2 SUBSYSTEM-ID DBWAIT=YES /* YES=WAIT FOR DB2 START, NO=DON’T WAIT REQLIB=‘HLQ.MLQ.REQUESTS’ /* STARTUP REQUEST LIBRARY MSSUB=ISRV /* GLOBAL SUBSYSTEM SSID DCMSGS=NO /* YES=LOG DC MESSAGES, NO=DON’T LOG MESSAGES NONSTOP=YES /* YES=START & STAY ACTIVE, NO=STOP IF NO DB2 DISPLAYSQL=YES /* YES=SQL FROM CONTROL BLOCKS IF NOT IN DB2 NUMUTASKS=3 /* NUMBER TASKS ATTACHED TO EXECUTE COMMANDS MAXUTASKS=6 /* MAXIMUM NUMBER OF TASKS ATTACHED BY DC SQL-WAIT-INTERVAL=60 /* TIME DC WILL WAIT FOR EXPLAIN FROM DB2 EXPLAIN-PLAN-SYSIBM=IDB2PLNS /* PLAN NAME FOR SYSIBM QUALIFICATION EXPLAIN-PLAN-USERQUAL=IDB2PLNU /* PLAN NAME FOR USER QUALIFICATION DC-DB2-STOP-MODE=SECO /* PRIM/SECO PRIMARY OR SECONDARY DC FULLDUMP=NO /* YES/NO FOR LARGE OR SHORT DUMP DB2-MESSAGE-PRTLIM=1000 /* 1-10000 - IF YOU CHANGE THIS PARM, YOU /* SHOULD CHANGE THE MVSFIILES REQUEST AS WELL. /* NEVENTS IN MVSFILES SHOULD BE AT LEAST AS /* LARGE AS DB2-MESSAGE-PRTLIM+1. DEFAULT-CONSOLE-DEV=‘XXX’/* DEFAULT COHSOLE DEVICE COLLECT-IFCID177=YES /* YES/NO TO POPULATE LAST PACKAGE INFO IN QWAC CALL-GSS=YES /* YES/NO TO MAKE GSS CALLS FOR IMODS AND LOGGING

Following are descriptions of these parameters: DBSUB=db2 Name Specifies the up to four-character name of the DB2 subsystem to be monitored or reported upon.

Tip: We recommend that you use the DBSUB override value in the JCL EXEC PARM field to specify this value.

DBWAIT=[YES|NO|ON|OFF] Specifies whether to wait for DB2 start-up if DB2 is inactive when the data collector is started. ON and OFF are synonyms for YES and NO respectively. If DB2 is inactive and DB2WAIT=NO is specified, the data collector immediately terminates.

5–22 System Guide Data Collector Operation and Customization

REQLIB=‘hlq.mlq.REQUESTS’ or REQLIB= (‘hlq.mlq.REQUESTS’, ‘2nd request library’, ‘...’,’...’) Specifies the name or names of the request libraries from which startup requests will be read. These libraries will be dynamically allocated during data collector initialization, and then freed. See Startup Requests for more information. MSSUB=ISRV Specifies the MVS subsystem name for the Global Subsystem IMOD facility (see Step 8: Install MVS Subsystem Names for GSS). If you have changed the name in that step, you should also change the MSSUB= value here. DCMSGS=[YES|NO] Specifies whether console messages issued by this data collector are to be logged by the Message Handler for later review. NONSTOP=[YES|NO] Specifies whether not the data collector will stay active when DB2 is stopped. See Migration Aids for potential conflicts. A potential problem exists when running nonstop data collectors for a long time when the DB2 subsystem is recycled frequently while Unicenter CA-Insight jobs are running. Unicenter CA-Insight prevents DB2 from coming up when the system is out of usable USER LX entries. This happens because DB2 does not free up those USER LX entries it had used during the previous cycle when other address spaces once connected to it are still active (like the data collector). DB2 will use a new set of USER LX entries each time it comes up. The length of time the data collector, PC Owner, and Global Subsystem jobs can run safely without causing a problem is controlled by:

■ The number of USER LX entries defined to the system

■ The frequency that DB2 is cycled while Unicenter CA-Insight runs DISPLAYSQL=[YES|NO] Specifies whether the last SQL statement text will be extracted from control blocks if the thread is not in DB2 when the display request is made. If YES is specified, an incorrect SQL statement could be displayed if the area pointed to has been reused. If NO is specified, the SQL statement text will only be shown when the thread is in DB2. NUMUTASKS=nn Specifies the number of users who can simultaneously be executing Unicenter CA-Insight commands from the user interface. The valid range is 2 to 16. Default value is 3. MAXUTASKS=nn Specifies the maximum number of user interface tasks which can be attached by this data collector. A user interface task is any task for data collector processing of Unicenter CA-Insight commands issued by a user; for example, a display or start request. The valid range is 2 to 16. Default value is 6.

Operation and Customization 5–23 Data Collector Operation and Customization

SQL-WAIT-INTERVAL=nnnn Specifies the lapsed time interval during which a data collector user interface tasks will wait for an EXPLAIN to be accomplished. EXPLAIN is canceled if not returned from DB2 within the time period (in seconds) specified in nnnn. Minimum value is 60. Default value is 180. EXPLAIN-PLAN-USERQUAL=xxxxx Specifies the EXPLAIN plan name to use when user qualified tables are to be used. The plan name specified should have been bound with a qualifier other than SYSIBM so that catalog shadow tables can be used. EXPLAIN-PLAN-SYSIBM=xxxxx Specifies the EXPLAIN plan name to use when the default SYSIBM tables are to be used. The plan name specified should have been bound with a default qualifier of SYSIBM when using the SYSIBM tables. DC-DB2-STOP-MODE=[PRIM|SECO] Specifies whether a data collector should terminate its DB2 threads immediately upon being posted that DB2 is terminating. The hierarchy is one primary data collector which behaves in the current manner by waiting until all other DB2 threads except its own terminate before terminating its threads; and one or more secondary data collectors which terminate their threads immediately. PRIM or SECO Specified in this parameter indicates a data collector’s stopping mode. The mode can also be specified as an EXEC PARM as STOPM=P or STOPM=S, respectively. When mode is specified on the EXEC statement, the SYSPARM value is ignored. The default is PRIM if no other specification is made. FULLDUMP=[YES|NO] Specifies whether a full ABEND dump (specify YES) or just a summary SNAP dump (specify NO) will be requested for an ABEND for which a dump is to be written. This value can also be specified on the EXEC PARM statement as FDUMP=YES or FDUMP=NO. When specified on the EXEC statement, any SYSPARM specification is ignored. The default is NO, which produces a summary dump. A further requirement to having a summary dump is to have a DD name allocated with the name DBGSNAP. This is the file to which the SNAP dump is directed. If the DBGSNAP file is not allocated, the dump option will be changed to YES, which will produce a full ABEND dump on the appropriate SYSUDUMP, SYSABEND, or SYSMDUMP DD statement (if present). DB2-MESSAGE-PRTLIM=nnnnn Specifies the number of DB2 messages or MVS file entries that will be printed for one print request. The default value is 1000 lines. The range, which you can specify, is 1-10,000. If a value outside this range is specified, a message will be written to DBGPRINT and the value changed to 1000.

5–24 System Guide Data Collector Operation and Customization

DEFAULT-CONSOLE-DEV=‘xxx’ Specifies the device address of the console that the data collector is to use. If this parameter is not specified, the data collector will default to the master console, if available. If no master console is available in a SYSPLEX environment, this parameter can be used to specify an alternative display console. CALL-GSS=[YES|NO] Specifies whether calls are to be made to GSS for execution of IMODs or for logging exceptions and DB2 commands. If GSS is not installed, not normally used, or if a required version of GSS is not available, NO should be specified so that additional overhead is reduced by eliminating the GSS call and subsequent error processing when GSS is not available. When GSS becomes available, the parameter should be changed to YES, and the data collector restarted. START-24X7=[YES|NO] Specifies whether the Unicenter CA-24X7 schedule routine should be started. If you are licensed for the optional Unicenter CA-24X7 component and are using scheduled commands, then you should set this parameter to YES (the default). Otherwise, set the parameter to NO to minize data collector overhead and to avoid warning messages if you are not licensed to run Unicenter CA-24X7.

Tracing Parameters

The tracing parameters control the type of traces started and the class of accounting data to be collected. ACCTTRACE=YES /* ACCOUNTING CLASS (NO,1,2,3,5,7,8,YES) IFI=YES /* YES,NO,READS NUMTRACES=12 /* MAX NUMBER OF DB2 TRACES ALLOWED (1-30) READA-BUFFER-PCT=50 /* READA BUFFER FULL PCT TO POST DC (10-50) IFCID2-NOTIFI=NO /* YES MEANS TO OBTAIN IFCID2 VIA CTL BLKS

Following are descriptions of these parameters: ACCTTRACE=[YES|NO|1|2|3|5|7|8] Indicates whether the accounting trace is to be activated and if so, what classes are to be activated. Note: No matter which option is chosen (even NO), an accounting trace is always activated for class 1.

■ NO—Do not activate the accounting trace.

■ YES (for IFI=NO)—Activate an accounting trace for classes 1, 2, and 3. For IFI=YES, the monitor trace to be started will have classes 1,2, and 3 activated, which are equivalent to accounting classes 1, 2 and 3. Activating accounting classes 2 and 3 causes increased overhead in DB2, but also produces resource usage information which can be valuable when tuning applications.

Operation and Customization 5–25 Data Collector Operation and Customization

■ 1|2|3|5|7|8—Indicate the accounting trace class or classes to be activated. This provides more options for controlling DB2 overhead. Even if not specified, accounting trace class 1 is always activated. If you specify more than one class, the classes must be enclosed in parentheses and separated by commas. For example, ACCTTRACE=(1,2,5,7). IFI=[YES|NO|READS] Determines how data is retrieved from DB2. If YES, the data collector uses the DB2 IFI for both sampled data and event trace records. If NO, the data collector uses its own routines for both sampled data and event trace records. If READS the data collector uses the IFI for sampled data and its own routines for event trace records. NUMTRACES=nn Determines the maximum number of traces that can be started by this data collector, including both qualified and unqualified traces. Valid entries are 1 to 30. Default is 6. READA-BUFFER-PCT=nn Specifies the percentage at which the IFI OPX buffer is filled when DB2 should POST the data collector that trace records are available for trace event processing. The default is when the buffer is 50% filled. The percentage value can be between 10 and 50. IFCID2-NOTIFI={NO|YES} NO means to continue to obtain IFCID 2 through the IFI when the keyword IFI=YES. YES means to obtain IFCID 2 through DB2 control blocks when the keyword IFI=YES. Specifying YES for this keyward can reduce the CPU usage in the DB2 DBM1 address space when Unicenter CA-Insight is active for a DB2 subsystem. Each site should evaluate the effect of the keyword setting in their own environment.

5–26 System Guide Data Collector Operation and Customization

History and Archive Parameters

The history and archive parameters control the operation of the Online History facility. You can use these parameters to:

■ Turn Online History on and off (if an Online History VSAM file was defined during installation)

■ Determine the collection interval for statistics records

■ Determine whether to gather thread accounting data HISTORY=YES /* (YES,NO) CAN USER ACCESS HISTORY HISTORY-ACCT=FILTER /* (YES,NO,FILTER) ACCOUNTING DATA? HISTORY-STATS-TIME=30 /* COLLECT STATS DATA INTERVAL, 0=NO HISTORY-MESSAGE-TIME=30 /* MESSAGE INTERVAL HIST-DISPLAY-COUNT=100 /* # OF THREADS TO LIST HISTARCH-TIME=‘230000’ /* START ARCHIVE TIME HISTARCH-TASK=‘IDB2UNLD’ /* START ARCHIVE TASK FOR TIME HISTARCH-STATS-TASK=‘IDB2UNLD’ /* START ARCHIVE TASK FOR STATS HISTARCH-ACCT-TASK=‘IDB2UNLD’ /* START ARCHIVE TASK FOR ACCTS HIST-CPUPARA-CHILD=YES /* COLLECT CPU PARALLELISM CHILD /* THREADS HISTORY-COMPRESSION=NO /* SPECIFY IF THE HISTORY RECORDS ARE /* COMPRESSED

Following are descriptions of these parameters: HISTORY=[YES|NO] If you have created and initialized an Online History VSAM file during installation, set this parameter to YES to activate Online History statistics and accounting collection. If you set HISTORY=NO, the Online History menu options will not operate. HISTORY-ACCT=[YES|NO|FILTER] Controls collection of thread accounting data. YES means all accounting records are collected. NO eliminates accounting record collection. FILTER limits accounting record collection through the use of one or more IQL FILTER requests (described in Online History ). HISTORY-STATS-TIME=nn Determines the interval (in minutes) at which DB2 STATS records (IFCIDs 1 and 2) are written to Online History. If you specify 0, no DB2 STATS records will be written to the file. The default value is 30. HISTORY-MESSAGE-TIME=nn The interval (in minutes) at which the statistics on Online History file usage are written. The default value is 30. HIST-DISPLAY-COUNT=nnnn Specifies the number of threads that the History System displays in a thread list. The default is 100. Setting this parameter too large will cause a degradation in response time.

Operation and Customization 5–27 Data Collector Operation and Customization

HIST-CPUPARA-CHILD=[YES|NO] If YES is specified, CPU Parallelism child threads will be collected in the History accounting data sets as in the previous release. When NO is specified, the child accounting records are only reflected in the CPU Parallelism Summary record for the parent thread. The individual Child threads are not written to the history data sets. HISTORY-COMPRESSION=[YES | NO] Specifies whether the records written to the history data sets will be compressed. The default is to not compress the records. The compression algorithm is a low CPU overhead multi-character compression, so overhead is minimal. The option can be turned on and off without reallocating the ACCT and STAT files. These files can have both uncompressed and compressed records mixed in the same file. HISTARCH-TIME=hhmmss Specifies the time you want the data collector to start the proc (specified in HISTARCH-TASK) to backup the Online History files. The default value is 230000. HISTARCH-TASK=‘xxxxxxxx’ Names the proc used to back up the Online History file. This proc is located in the SOURCE library. The default is proc IDB2UNLD, which is explained in Online History Data Set Unload (IDB2UNLD). HISTARCH-STATS-TASK=‘xxxxxxxx’ Names the proc started by the data collector to backup the Online History file when the active Interval Statistics data set becomes full. Blank disables backups at Interval Statistics file switch. The default proc is IDB2UNLD (explained in Online History Data Set Unload (IDB2UNLD)). HISTARCH-ACCT-TASK=‘xxxxxxxx’ Names the proc started by the data collector to backup the Online History file when the active Thread Accounting data set becomes full. Blank disables backups at Thread Accounting file switch. The default proc is IDB2UNLD (explained in Online History Data Set Unload (IDB2UNLD)).

Trace Record Buffer Parameters

The trace record buffer parameters control the size of the trace record buffers. SRVBUFSZ=8 /* # OF 4 K PAGES FOR EACH DB2 TRACE BUFFER SRVBUFNUM=8 /* # OF DB2 TRACE BUFFERS PRVBUFNUM=12 /* # OF DB2 TRACE BUFFERS IN PRIVATE AREA PRVMAXSZ=1024 /* MAX SIZE OF DB2 TRACE BUFFERS IN PRIVATE AREA TRUNCTIME=10 /* TIME INTERVAL IN SECONDS FOR FLUSHING BUFFERS

5–28 System Guide Data Collector Operation and Customization

Following are descriptions of these parameters: SRVBUFSZ=n If IFI=NO or IFI=READS has been specified. This parameter determines the number of 4K pages to be obtained in Extended CSA for each DB2 trace buffer. (See Customizing Data Collector Initialization Parameters for more information about the IFI parameter.) Value must be between 2 and 8 for a minimum size of 8K and a maximum of 32K. Default size of a trace buffer is 8 pages, which is 32K. If IFI=YES Has been specified, see the usage explanation for SRVBUFNUM (next). (See Customizing Data Collector Initialization Parameters for more information about the IFI parameter.) SRVBUFNUM=nn If IFI=NO or IFI=READS has been specified, then this parameter specifies the number of DB2 trace buffers of SRVBUFSZ size that are to be obtained in extended CSA. These buffers are filled by the SRV trace destination writer in DB2. If all the specified buffers are filled, trace data is lost until a buffer is made available after the data collector processes one. The minimum number that can be specified is 2 and the maximum number is 50. The default number of SRV buffers is 4. When IFI=YES has been specified, the data collector is monitoring a DB2 subsystem using IBM’s Instrumentation Facility Interface (IFI). (See Customizing Data Collector Initialization Parameters for more information about the IFI parameter.) Here, SRVBUFSZ and SRVBUFNUM are used to calculate the size of the IFI monitor buffer specified with the DB2 -START TRACE command. The monitor buffer size will be the product of (SRVBUFSZ) * (SRVBUFNUM) * (4K), with a maximum size limit of 1 megabyte. DB2 will obtain this buffer from extended CSA storage. This buffer is filled by the IFI trace destination writer in DB2. Note: Trace data can be lost if the buffer is filled before the data collector can request it to be processed. PRVBUFNUM=nn Specifies the number of buffers of SRVBUFSZ size to be allocated from storage in the private area of the data collector address space. These buffers are filled by an SRB routine (when IFI=NO or IFI=READS has been specified) which is invoked when an online trace buffer is filled and is to be processed. These buffers are emptied as each trace record is processed by the data collector. The minimum number that can be specified is 2 and the maximum is 50, and the default value is twice the value of SRVBUFNUM. If you are not using the IFI, you can specify a different value. If you are using the IFI, the value of PRVBUFNUM is automatically set to twice the value of SRVBUFNUM and cannot be set to a different value. These buffers are obtained in the extended private area.

Operation and Customization 5–29 Data Collector Operation and Customization

PRVMAXSZ=nnnn Specifies the maximum size of storage (in K) that is to be allocated for trace buffers in the data collector private area if more than PRVBUFNUM are required during processing. The data collector will dynamically obtain more private area buffers up to this maximum if SRV or IFI buffers are to be processed and no empty private area buffers remain. The default maximum size of the private area that will be used for buffers is 1024K. When the product of SRVBUFSZ times PRVBUFNUM is greater than the specified size, the larger size will become the initial maximum and consequently the private area limit. TRUNCTIME=nnnn Specifies the interval time (in seconds) after which a partially filled DB2 trace buffer is to be “flushed” or made available for data collector processing if no other DB2 trace buffer has been filled and been made available in the interval. This is intended for use in a lightly used DB2 subsystem where it normally would take a long period of time to fill a DB2 trace buffer. The default value is 10 seconds. When IFI=YES is specified, a READA IFI command is issued if trace data is available to obtain the trace data when this specified interval passes without having been posted for data by the IFI.

Data Set Allocation Parameters

The data set allocation parameters control the dynamic allocation of data sets by specifying defaults for data set characteristics not specified in the request. STATUS=NEW /* DEFAULT DATASET STATUS (NEW,MOD,OLD,SHR) DISP=CATLG /* DEFAULT DATASET DISP (KEEP,DELETE,CATLG) SPACETYPE=TRK /* DEFAULT DATASET SPACE (CYL,TRK) PRIMARY=25 /* DEFAULT DATASET PRIMARY SPACE ALLOCATION SECONDARY=10 /* DEFAULT DATASET SECONDARY SPACE ALLOCATION DSORG=PS /* DEFAULT DATASET ORGANIZATION UNIT=‘diskunit’ /* DEFAULT DATASET UNIT TYPE SYSOUT=‘A’ /* DEFAULT SYSOUT CLASS PREFIX=‘hlq.mlq.OUTPUT’ /* DATASET NAME PREFIX ENFORCE-PREFIX=YES /* (YES,NO) YES=USE PREFIX ON ALL DATASET NAMES

Following are descriptions of these parameters: STATUS=[NEW|MOD|OLD|SHR] Specifies the default status for a data set that is dynamically allocated for a request when the status is not specified in the request. DISP=[KEEP|DELETE|CATLG] Specifies the default disposition taken for a dynamically allocated data set when not indicated in the request. SPACETYPE=[CYLINDER|CYL|TRACK|TRK|xxxx] Specifies the default type of space to be allocated for a new data set which is dynamically allocated if the space type is not indicated in the request. CYL and TRK are synonyms for CYLINDER and TRACK respectively. xxxx means that space is to be allocated in blocks whose average length is specified by the value xxxx.

5–30 System Guide Data Collector Operation and Customization

PRIMARY=nnnn Specifies the default primary quantity of space of the type indicated by SPACETYPE to be allocated for a new data set when the quantity is not specified in the request. The default value is 25 tracks. SECONDARY=nnnn Specifies the default secondary quantity of space of the type indicated by SPACETYPE to be allocated for a new dynamically allocated data set when not specified in the request. Default is 10 tracks. DSORG=[PS|PO] Specifies the default data set organization for a new dynamically allocated data set when the data set organization is not specified in the request. UNIT=diskunit Specifies the default unit type for a new data set to be dynamically allocated when the unit type is not specified in the request. The default unit type is SYSDA. When an entirely numeric value is specified it must be enclosed in quotes, i.e. ‘3380’. SYSOUT=‘x’ Specifies the default sysout class for a sysout data set to be dynamically allocated for a request when the sysout class is not specified in the request. The default sysout class is A. PREFIX=‘hlq.mlq.OUTPUT’ Specifies the beginning prefixes for a dynamically allocated data set specified for use by a request. This prefix will be appended to the front of the data set name except when the fully-qualified name is given in the request. ENFORCE-PREFIX=[YES|NO] YES enforces the PREFIX string to be the highest level qualifier for all data sets created from requests. If YES is specified, any data set name used in a request will be appended behind the prefix and truncated if too long. NO allows requests to use any fully qualified data set name.

Remote Access Facility Parameters

The remote access facility parameters control whether this data collector can be accessed using the Remote Access Facility. APPLS=((DB2-LOCATION,DBSUB,RAF-APPL,RAF-PASSWORD))

DB2-LOCATION AND DBSUB ARE USED TO PICK THE RAF APPLICATION IDENTIFIER (RAFAPPL) THAT THE DC WILL USE WHEN STARTING THE RAF TASK ******************************************************************** RAF=NO /* YES=THIS DC WILL BE ACCESSED VIA RAF DB2-LOCATION=‘DB2-LOCATION’ /* IF RAF=YES, USED WITH DBSUB TO /* UNIQUELY IDENTIFY DC

APPLS=((DB2LOCATION1,xxxx,RAFAPPL1,RAFPW1), (DB2LOCATION2,yyyy,RAFAPPL1,RADPW2) ) RAF-RUSIZE=2048 /* USE ONLY IF CAN’T GET LOGMODE CORRECT

Operation and Customization 5–31 Data Collector Operation and Customization

Following are descriptions of these parameters: RAF=[YES|NO] Indicates whether the Unicenter CA-Insight Remote Access Facility is to be enabled. This lets users located on other MVS operating systems in the VTAM network connect to this data collector. The default is NO. DB2-LOCATION=‘xxxxxxxxxxxxxxxx’ Specifies a description of the DB2 subsystem being monitored. The location name must be specified in quotes (‘). Up to 16 characters are allowed. Used only when RAF=YES is specified. This location name is the same one you specify in the APPLS statement of the user interface parameters (page 172) so that the user interface can find this data collector. When using the DB2 Distributed Data Facility, use the DB2 Location specified in the DB2 Communications Database. APPLS=((location,dbsubsystem,raf-applid,raf-appl-password), ....) Specifies data for a table of Unicenter CA-Insight-to-VTAM-applid relationships. The data collector uses this information to determine the VTAM application ID to use when initiating the Remote Access Facility. Each row identifies a data collector monitoring the specified DB2 subsystem and the VTAM application name that is used when the data collector is accessed from a remote MVS. This parameter is only used if RAF=YES. The location name must be specified with quotes (‘) if it contains special characters. Otherwise, no quotes are needed. At least one entry must appear in this table. Multiple entries can be specified. The data collector will choose the entry for the subsystem specified in the DBSUB and DB2-LOCATION parameters. When using the DB2 Distributed Data Facility, the location name must be the same as the DB2 location specified in the DB2 Communications Database. For DB2 V4 data sharing, the location name must be the same for each member in the group. RAF-RUSIZE=rusize Specifies a value that overrides the RAF RUSIZE in the VTAM bind. rusize must be a value between 64 and 16 KB that is a power of 2. If this parameter is not specified, your site’s VTAM definitions will be used.

Security Parameters

The security parameters control the data collector security facility. See the “Security” chapter for detailed information about security features

Note: Not all restricted and forbidden IFCIDS are shown here. SECURITY=YES /* (YES,NO) SPECIFY SECURITY TYPE SECURITY-EXIT=NSIGHTEX /* SECURITY EXIT 1 NAME MAX-REQUEST-TIME=0 /* MAXIMUM REQUEST TIME MAX-TRACE-RECORDS=0 /* MAXIMUM TRACE RECORDS RESTRICTED-IFCIDS=( 6,7,8,9, /* READ AND WRITE IO */ 15,18, /* SCAN */

5–32 System Guide Data Collector Operation and Customization

20, /* LOCK-SUMMARY */ 22, /* MINI-PLAN */ 58,59,63, /* SQL STATEMENTS AND SQL TEXT */ )

FORBIDDEN-IFCIDS=( 1,2, /* STATS, DON’T COLLECT ONLINE */ 4,5, /* TRACE-START AND STOP */ 11, /* VALIDATION OR EDIT EXIT */ ) EXPLAIN-AUTHID=xxxxxx /* AUTH IF ALL BIND DONE WITH ONE AUTH

Following are descriptions of these parameters: SECURITY=[YES|NO] Indicates whether the optional security and resource limit facility should be enabled.

■ YES means that the facility is to be activated, and that the security profiles specified by the SECURITY DD statement are to be applied to Unicenter CA-Insight users.

■ NO means the security facility is not to be activated. If you specify NO, all users can PAUSE, RESUME, DISPLAY, STOP, and edit requests. SECURITY-EXIT=NSIGHTEX Specifies the member name of a load module which will be invoked by the data collector when a command is received from an Unicenter CA-Insight user. This parameter is ignored if SECURITY=NO is specified. This exit routine enables you to screen a command by user ID and request. The specified load module must be in an authorized library which has been made available to the data collector. See the “NSIGHTEX User Exit” appendix for details about the use, input and output requirements for this exit. MAX-REQUEST-TIME=nnnn Specifies a value if SECURITY=NO is specified, or if SECURITY=YES and MAX-REQUEST-TIME=DC in the user’s security profile. Specify the amount of time (in minutes) that a request started by such a user will be active before being terminated. If this parameter is omitted, Unicenter CA-Insight assumes the default value is zero (no time limit). MAX-TRACE-RECORDS=nnnn Specifies a value if SECURITY=NO is specified, or if SECURITY=YES and MAX-REQUEST-TIME=DC in the user’s security profile. Specify the number of DB2 trace records that a request started by such a user will collect before being terminated. If this parameter is omitted, Unicenter CA-Insight assumes the default value is zero (no record limit). RESTRICTED-IFCIDS=(nnn,nnn,...) Specifies a list of DB2 trace IFCIDs which are to be restricted from general use. Requests using these IFCIDs can only be started by users granted access to restricted IFCIDs in the Security file (Profile parameter START=RESTRICTED or START=ALL). This parameter is ignored if SECURITY=NO is specified.

Operation and Customization 5–33 Data Collector Operation and Customization

FORBIDDEN-IFCIDS=(nnn,nnn,...) Specifies a list of DB2 trace IFCIDs which are to be forbidden from general use. Requests using these IFCIDs can only be started by users granted access to forbidden IFCIDs in the Security file (Profile parameter START=ALL). This parameter is ignored if SECURITY=NO is specified. EXPLAIN-AUTHID=authid This parameter is important for sites where all BINDs are done under a single Authorization ID. If specified, authid indicates the Authorization ID that the EXPLAIN function uses. If not specified, the Unicenter CA-Insight User ID is used as the Authorization ID.

Migration Aids

The following migration aid parameters can be used in migrating new releases of the data collector and PC owner. These parameters limit the functionality of the NONSTOP= parameter. (See Customizing Data Collector Initialization Parameters for information about the NONSTOP= parameter.)

Note: If you try to terminate DB2 with two data collectors attached, DB2 will not terminate because both nonstop data collectors are waiting until only its threads are active. Data collectors must be stopped until only one remains active. TESTVER=V610 /* xxxx ALTERNATE DC, SEE SYSTEM GUIDE PCSSID=DBGI /* xxxx ALTERNATE PCAUTH (DEFAULT=DBGI)

Following are descriptions of these parameters: TESTVER=xxxx Specifies a 1-4 character identifier for a separate unique data collector, which can be started on the same DB2 subsystem as another data collector. PCSSID=xxxx Specifies a unique MVS subsystem ID for the PC Owner with which the data collector is to operate in conjunction.

Reporting Controls

The following reporting controls parameters control what information displays in IQL-based requests. The parameters are interrogated using IQL #IF statements in the requests. PRINT-REQUESTS=YES /* YES=LIST IQL IN DBGPRINT, NO=DON’T LIST IQL DB2VER=3.1 /* DB2 VERSION DDF=NO /* DISTRIBUTED DATA FACILITY NATURAL-DB2=NO /* NATURAL-DB2 PROGRAM NAMES RLF=NO /* REPORT RLF DATA

5–34 System Guide Data Collector Operation and Customization

Following are descriptions of these parameters: PRINT-REQUESTS=[YES|NO] Specifies whether the request IQL will be listed in DBGPRINT when the request is started. DB2VER=n.n Specifies the DB2 version. DDF=[YES|NO] indicates whether Distributed Data Facility (DDF) information should be reported. NATURAL-DB2=[YES|NO] Indicates whether NATURAL for DB2 fields should be reported. For information about installing the optional NATURAL for DB2 support, see the “Installing Optional Components” chapter. RLF=[YES|NO] Indicates whether RLF data should be reported.

Day/Date/Time Localization for IQL Requests

The following parameters control how dates and times display in Unicenter CA-Insight.

Note: These are only applicable to IQL-based reports and requests.

The use of these parameters as masks in reports is described in “IQL Syntax” in the Unicenter CA-Insight Writing Requests guide. /* DAY FORMAT FOR IQL WITH PF=‘DDD’ DAYS=(‘SUN’,’MON’,’TUE’,’WED’,’THU’,’FRI’,’SAT’) /* MONTH FORMAT FOR IQL WITH PF=‘MMM’ MONTHS=(‘JAN’,’FEB’,’MAR’,’APR’,’MAY’,’JUN’, ‘JUL’,’AUG’,’SEP’,’OCT’,’NOV’,’DEC’) DATE=‘MM/DD/YY’ /* DATE FORMAT FOR IQL USING PF=DATE DATEMD=‘MM/DD’ /* DATE FORMAT FOR IQL USING PF=DATEMD DATETIME=‘MM/DD/YY HH:MM:SS’ /* FORMAT FOR IQL USING PF=DATETIME TIME=‘HH:MM’ /* TIME FORMAT FOR IQL USING PF=TIME TIMESS=‘HH:MM:SS’ /* TIME FORMAT FOR IQL USING PF=TIMESS TIMED2=‘HH:MM:SS.TT’ /* TIME FORMAT FOR IQL USING PF=TIMED2 TIMED3=‘HH:MM:SS.TTT’ /* TIME FORMAT FOR IQL USING PF=TIMED3 TIMED4=‘HH:MM:SS.TTTT’ /* TIME FORMAT FOR IQL USING PF=TIMED4

Following are descriptions of these parameters: DAYS= Specifies the days of the week, using 3-character abbreviations. This applies to IQL request field output/print formats that have “DDD” specified (as in PF=‘DDD, DD MMM, YYYY’, which would display a date as TUE, 20 DEC, 1994). If you change a value, be sure to uncomment the line.

Operation and Customization 5–35 Data Collector Operation and Customization

MONTHS= Specifies the months of the year, using 3-character abbreviations. This applies to IQL request field output/print formats that have “MMM” specified (as in PF=‘DDD, DD MMM, YYYY’, which would display a date as TUE, 20 DEC, 1994). If you change a value, be sure to uncomment the line. DATE= Specifies the month, day, and year, using 2-character abbreviations DATEMD= Specifies the month and day, using 2-character abbreviations DATETIME= Specifies date and time, using 2-character abbreviations TIME= Specifies the hour and minute, using 2-character abbreviations TIMESS= Specifies the hour, minute, and seconds, using 2-character abbreviations TIMED2= Specifies the hour, minute, second, and hundredths of seconds, using 2-character abbreviations TIMED3= Specifies the hour, minute, second, and thousandths of seconds TIMED4= Specifies the hour, minute, second, and ten-thousandths of seconds

Exception Monitor Control

The following parameters control the processing of exceptions through Unicenter CA-Insight. EXCEPTION-PROCESSOR=YES /* YES=EXECUTE EXCEPTION PROCESSOR EXCEPTION-INTERVAL=10 /* TIME (SECS) BETWEEN EXCEPTION SCANS EXCEPTION-DB-INTERVAL=900 /* TIME (SECS) BETWEEN DB EXCEPTION SCANS EXCEPTION-TSO-SEND=LOGON /* DEFAULT TSO SEND OPTION: SAVE/NOW/LOGON SCM-IMOD-NAME=IDB2MEXC /* REMOVE * TO ISSUE SCM IMOD CALLS TO GSS

Following are descriptions of these parameters: EXCEPTION-PROCESSOR=[YES|NO] Specifies whether the Exception Processor task will be activated EXCEPTION-INTERVAL=nnn Specifies the interval (in seconds) in which the Exception Processor will evaluate exceptions (e.g. have any timed exceptions occurred during the interval period?). Minimum and default value is 5. EXCEPTION-DB-INTERVAL=nnnn Specifies the interval (in seconds) at which the Exception Processor will query DB2 about restricted databases. Minimum value is 60. Default value is 300.

5–36 System Guide Data Collector Operation and Customization

EXCEPTION-TSO-SEND={SAVE | LOGON | NOW} Controls the default action on the TSO SEND command issued by the exception processor on behalf of an exception. Valid values are:

■ SAVE—Specifies that the message is to be saved in the broadcast data set and not sent now.

■ LOGON—Specifies that the message is to be sent now if the user is currently logged on. Otherwise, the message is saved in the broadcast data set.

■ NOW—Specifies that the message is to be sent immediately. SCM-IMOD-NAME=IDB2MEXC Specifies the name of the IMOD that stores exception information in the System Condition Monitor. This exception information is generated by the Exception Processor. The default value is for this parameter to be commented out (no exception information is stored in the SCM). Uncomment the line to activate the IMOD. DB2-TYPE=[PROD | TEST] Identifies the type of DB2 subsystem that Unicenter CA-Insight is monitoring. Exceptions can be defined as applicable to test DB2 subsystems, production DB2 subsystems, or both. This parameter lets you share the exception data set and have a set of customized exception definitions and thresholds for test and production subsystems.

Data Sharing

The following parameters control the processing of data sharing information through Unicenter CA-Insight. DATA-SHARING=NO /* =YES ENABLES DATA SHARING IQL STATEMENTS DC-GROUP=xxxxxxxx /* SPECIFIC INSTALLATION DC GROUP NAME

Following are descriptions of these parameters: DATA-SHARING=[YES|NO] Specifies whether on not the data sharing specific IQL statements in requests will be enabled. These statements can be found in several IQL requests surrounded by #IF DATASHR, #IFENDIQL statements. DC-GROUP=xxxxxxxx Specifies an installation specific data sharing group name for the data collectors which are monitoring a specific DB2 data sharing group. The name specified must be unique among all XCF groups specified. The default DC group name is XDBGDCvv where vv equals the Unicenter CA-Insight release number.

Operation and Customization 5–37 Data Collector Operation and Customization

Unicenter Agent for DB2

The following parameters control the startup and debugging options of the Unicenter Agent for DB2. The Agent is an optional, separately-priced product for Unicenter CA-Insight. It is also available as an adjunct standalone product to Unicenter. UNICENTER-AGENT=NO /* SPECIFIES TO START AGENT AGENT-DEBUG=4 /* AGENT DEBUGGING OPTION AGENT-REQUESTS =( /* IQL REQUESTS TO OBTAIN AGENT DATA (‘DB2INITCONFIG’,’AGENTIC1’), (‘DB2CPUSTATUS’,’AGENTCS1’,’AGENTCS2’), (‘DB2IOSTATUS’,’AGENTIO1’,’AGENTIO2’), (‘DB2LOGSTATUS’,’AGENTLS1’,’AGENTLS2’), (‘DB2LOCKSTATUS’,’AGENTKS1’), (‘DB2WKLDSTATUS’,’AGENTWS1’), (‘DB2BPSTATUS’,’AGENTBS1’,’AGENTBS2’), (‘DB2EDMSTATUS’,’AGENTES1’), (‘DB2OTHERSTATUS’,’AGENTOS1’,’AGEBTOS2’,’AGENTIC1’), (‘DB2APPLSTATUS’,’AGENTRA1’,’AGENTRA2’) ) AGENT-OBJECT-STORE=NO /* USE OBJECT STORE OR AGENT FOR DATA VALUES AGENT-CONFIG=xxxxxxxx /* SPECIFY ALTERNATE CONFIG TABLE

Following are descriptions of these parameters: UNICENTER-AGENT=[YES|NO] Specifies whether the Agent should be started for communication with Unicenter. This parameter can be overridden from the EXEC statement PARM field by specifying AGENT=[YES|NO]. AGENT-DEBUG=n Specifies the value for the level of debugging messages to be written to the AGTDCLG file. The value can range from 1 to 6, where the higher the number, the more message volume is produced.

■ Level 1 writes just critical messages.

■ Level 2 adds warning messages

■ Level 3 adds informational messages (default value).

■ Levels 4 through 6 writes debugging messages in increasing levels of detail. This parameter can be overridden from the EXEC statement PARM field by specifying AGTDBG=x. AGENT-OBJECT-STORE=[YES|NO] Indicates whether data values from the Agent MIB are to be satisfied from the object store or from the agent directly (the Agent does not register for GET requests). We recommend that you leave this value as NO. This parameter can be overridden from the EXEC statement PARM field by specifying OBJST=[YES|NO].

5–38 System Guide Data Collector Operation and Customization

AGENT-CONFIG=xxxxxxxxxxxx Specifies an alternate configuration set to be used by the Agent. The configuration must have been previously loaded into object store with the LDCONFIG utility. This parameter can be overridden from the EXEC statement PARM field by specifying CONFIG=xxxxxxxxxxxxx. AGENT-REQUESTS=((‘mibgroupname1’,’request1’,’request2’,), (‘mibgroupname2’,’req1’,),(.)) Specifies the association between the MIB Configuration Group and the associated IQL request names which obtain the data to populate the appropriate MIB fields. Note: This parameter should not be changed.

Unicenter Performance Management Predictor (PMP)

The following parameters control the startup and debugging options of the Unicenter Performance Management Predictor (PMP) interface. Unicenter PMP is an optional separately-priced product from Computer Associates. UNIPMP-ENABLED=NO /* YES/NO UNICENTER PMP ENABLED UNIPMP-SSID=UNIP /* SUBSYSTEM ID USED BY UNICENTER PMP UNIPMP-DEBUG=NO /* YES/NO DEBUGGING MESSAGES UNIPMP-INTERVAL=900 /* COLLECTION INTERVAL IN SECONDS. /* THIS INTERVAL SHOULD MATCH THE /* COLLETION INTERVAL DEFINED TO /* UNICENTER PMP.

Following are descriptions of these parameters: UNIPMP-ENABLED=[YES|NO] Specifies whether Unicenter CA-Insight should try to connect and pass data to Unicenter PMP. UNIPMP-SSID=xxxx Specifies the subsystem ID of the Unicenter PMP task that Unicenter CA-Insight attempts to connect to if UNIPMP-ENABLED is set to YES. The default subsystem ID is UNIP. UNIPMP-DEBUG=[YES|NO] Specifies whether Unicenter CA-Insight writes debugging messages to the DBGPRINT output when sending data to Unicenter PMP. If YES, Unicenter CA-Insight echoes the contents of all the data sent to PMP in messages written to DBGPRINT. This option should only be set for debugging purposes if you need to verify the contents of the data being sent to PMP. This can generate large amounts of data to the DBGPRINT output and should only be enabled for a short period of time. Note that if you encounter an error when attempting to send the data to PMP, messages echoing the data will be written to DBGPRINT regardless of this setting.

Operation and Customization 5–39 Data Collector Operation and Customization

UNIPMP-INTERVAL=x Specify the collection interval for sending data to Unicenter PMP in seconds. You can specify a value from 60 seconds to 86400 seconds (24 hours). For best results, this value should match the collection interval specified in the Unicenter PMP options. The default is 900 (15 minutes). This value is used by IQL requests that specify INTERVAL UNIPMP (the default Unicenter PMP IQL requests) to control the collection interval for the IQL request. This interval also controls how often Unicenter CA-Insight tells PMP that a collection interval is finished.

Parameters You Can Override

You can override eleven parameters with the PARM parameter of the EXEC statement in the data collector startup JCL or PROC. See Starting the Data Collector and Stopping the Data Collector for more details.

■ DBSUB

■ DBWAIT

■ DB2-LOCATION (overridden with the DBLOC keyword)

■ DB2-VERSION (overridden with the DB2VER keyword)

■ PC Owner name (overridden with the PCSSID keyword)

■ FDUMP for changing FULLDUMP option

■ STOPM for data collector stop mode of primary (P) or secondary (M).

■ UNICENTER-AGENT (overridden with the AGENT keyword)

■ AGENT-DEBUG (overridden with the AGTDBG keyword)

■ AGENT-OBJECT-STORE (overridden with the OBJST keyword)

■ AGENT-CONFIG (overridden with the CONFG keyword)

■ DATA-SHARING (overridden with the DATASHR keyword)

■ DC-GROUP (overridden with the DCGRP keyword)

The PARM field must have a leading slash (/) to indicate to the software that these are program-specific parameters. Everything that follows PARM= must be enclosed within single quotes (‘).

In the following example, the DB2 Subsystem ID, Location, AND Version are being overridden: //IDB2DC EXEC GM=NSIGHTDC,REGION=5M,DPRTY=(14,15),TIME=1440, // PARM=‘/DBSUB=DB2T,DBLOC=DB2LOCATION1,DB2VER=2.3’

5–40 System Guide Data Collector Operation and Customization

Startup Requests

All requests are stored as members in the Unicenter CA-Insight TGTREQ and REQUESTS library. You can have the data collector automatically start any number of requests at initialization. These requests are called “startup” requests.

For a request to be automatically started, you must include its member name in a sequential file that is read by the data collector at initialization time, the startup request file. This file is made up of INCLUDE member statements, one for each request you want automatically started.

Sample Startup Requests File

A sample startup request file is included in the SOURCE library, member STARTUP, a portion of which is shown in the following.

The libraries from which the requests in the INCLUDE statements are read are specified in data collector parameter REQLIB. (See Customizing Data Collector Initialization Parameters for more information about the REQLIB parameter.) At initialization, the data collector opens the request library and starts each request named on an INCLUDE statement.

To change a startup request, edit the request, and save it in the request library specified in the REQLIB. The next time the data collector starts, the modified request will be started. To add or delete a startup request, simply edit the startup request file, insert a line into the list of request members or delete a line from the list.

If you add a request to the list, make sure the request does not use OWNER-UNIQUE=YES. If it does, you will only be able to display the request from the Show panel.

The Constants Table (CONSTBL)

The purpose of the Constants Table is to provide a means for each site to override the default values for abbreviations of the months of the year and days of the week. Also, it provides for filtering non-printables (such as converting lower-case letters to upper-case or making null values (X’00’) show up as periods in displays).

Note: Most customers will never have to alter this table.

Operation and Customization 5–41 Data Collector Operation and Customization

The Constants Table is in member CONSTBLA in the SOURCE library. A sample is shown in the following.

If you wish to change the default values for abbreviations and/or change the filtering values, make the changes to this source member. Assemble and linkedit it using the MAKECT member in the SOURCE library.

Note: Data collector and report writer parameters can override these values in IQL-based reports and displays. See Day/Date/Time Localization for more details.

Changing Month Abbreviations

Default values for month abbreviations are in the MONABBR segment of the member: MONABBR EQU * 3-CHARACTER MONTH-ABBREVIATION TABLE DC CL3’JAN’ <======DC CL3’FEB’ <======DC CL3’MAR’ <======DC CL3’APR’ <======DC CL3’MAY’ <======CHANGE ANY OF THESE DC CL3’JUN’ <======ENTRIES, BUT KEEP DC CL3’JUL’ <======LENGTHS EXACTLY 3 DC CL3’AUG’ <======DC CL3’SEP’ <======DC CL3’OCT’ <======DC CL3’NOV’ <======DC CL3’DEC’ <======

You can change any entry but keep the abbreviation limited to three characters. Do not add additional months.

Changing Day Abbreviations

Default values for day abbreviations are in the DAYABBR segment of the member: DAYABBR EQU * 3-CHARACTER DAY-ABBREVIATION TABLE DC CL3’SUN’ <==== DC CL3’MON’ <==== CHANGE ANY OF THESE ENTRIES DC CL3’TUE’ <==== BUT KEEP LENGTHS EXACTLY DC CL3’WED’ <==== 3 CHARACTERS DC CL3’THU’ <==== DC CL3’FRI’ <==== DC CL3’SAT’ <====

You can change any entry but keep the abbreviation limited to three characters. Do not add additional days.

5–42 System Guide Data Collector Operation and Customization

Translate Table for Alphas

The following (segment MSTPRTPM) shows how hex combinations are translated: MSTPRTPM DS 0D * 0 1 2 3 4 5 6 7 8 9 A B C D E F DC X’4B404040404040404040404040404040’ 0 BLANK DC X’40404040404040404040404040404040’ 1 BLANK DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ 2 DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ 3 DC X’404B4B4B4B4B4B4B4B4B4A4B4C4D4E4F’ 4 DC X’504B4B4B4B4B4B4B4B4B5A5B5C5D5E5F’ 5 DC X’60614B4B4B4B4B4B4B4B6A6B6C6D6E6F’ 6 DC X’4B4B4B4B4B4B4B4B4B797A7B7C7D7E7F’ 7 DC X’4B8182838485868788894B4B4B4B4B4B’ 8 DC X’4B9192939495969798994B4B4B4B4B4B’ 9 DC X’4BA1A2A3A4A5A6A7A8A94B4B4B4B4B4B’ A DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ B DC X’C0C1C2C3C4C5C6C7C8C94B4B4B4B4B4B’ C DC X’D0D1D2D3D4D5D6D7D8D94B4B4B4B4B4B’ D DC X’E04BE2E3E4E5E6E7E8E94B4B4B4B4B4B’ E DC X’F0F1F2F3F4F5F6F7F8F9FA4B4B4B4B4B’ F

The values in the row on the right (0-F) are the first hex character, those on top (0-F) are the second hex character.

For example, hex value ‘00’ (nulls) is translated to hex value ‘4B’ (period).

Translate Table for Uppercase

The following is similar to the preceding one, except that it is used primarily for the translation of lower-case characters to upper-case. This is segment MSTPRTUM. The uppercase translation only occurs when the user interface parameter UPPER-CASE=YES is specified (the default is NO). See Customizing User Interface Session Parameters for a description. MSTPRTUM DS 0D * 0 1 2 3 4 5 6 7 8 9 A B C D E F DC X’4B404040404040404040404040404040’ 0 BLANK DC X’40404040404040404040404040404040’ 1 BLANK DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ 2 DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ 3 DC X’404B4B4B4B4B4B4B4B4B4A4B4C4D4E4F’ 4 DC X’504B4B4B4B4B4B4B4B4B5A5B5C5D5E5F’ 5 DC X’60614B4B4B4B4B4B4B4B6A6B6C6D6E6F’ 6 DC X’4B4B4B4B4B4B4B4B4B797A7B7C7D7E7F’ 7 DC X’4BC1C2C3C4C5C6C7C8C94B4B4B4B4B4B’ 8 TOUPPER DC X’4BD1D2D3D4D5D6D7D8D94B4B4B4B4B4B’ 9 TOUPPER DC X’4BA1E2E3E4E5E6E7E8E94B4B4B4B4B4B’ A TOUPPER DC X’4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B4B’ B DC X’C0C1C2C3C4C5C6C7C8C94B4B4B4B4B4B’ C DC X’D0D1D2D3D4D5D6D7D8D94B4B4B4B4B4B’ D DC X’E04BE2E3E4E5E6E7E8E94B4B4B4B4B4B’ E DC X’F0F1F2F3F4F5F6F7F8F9FA4B4B4B4B4B’ F

Operation and Customization 5–43 Online User Interface Operation and Customization

The values in the row on the right (0-F) are the first hex character, those on top (0-F) are the second hex character. For example, hex value ‘81’ (lower-case a) is translated to hex value ‘C1’ (upper-case A.

Troubleshooting

If a GSV003I REQUESTED MODULE GSSRC NOT FOUND message is written to the system message file, it means that the GSSRC module was not copied to the Unicenter CA-Insight load library as described in Step 4 of Installing the Global Subsystem (GSS). Unicenter CA-Insight attempts to load the GSSRC module during initialization. If GSSRC is not found, the module INSGSSRC is loaded from the Unicenter CA-Insight load library, which means that a back level copy of GSSRC might have been loaded.

Online User Interface Operation and Customization

The section is intended for the person responsible for installing and administering Unicenter CA-Insight. The section discusses the requirements and considerations for operating and customizing the TSO and VTAM user interfaces.

How the User Interfaces Work With the Data Collector

The online user interfaces manage conversations between the terminal user and one or more data collectors of the same version. The online interfaces provide real-time, interactive facilities for sending data collection requests to the data collector and viewing the output of the requests on a terminal. The user interfaces also provide facilities to issue DB2 and MVS commands, view DB2 console messages and Unicenter CA-Insight exception messages, and EXPLAIN SQL.

User interface access is available from TSO ISPF or native VTAM. The online interfaces are very similar and can be used interchangeably for the majority of tasks involved in monitoring a DB2 subsystem.

The TSO user interface provides the following facilities that are not available under the VTAM user interface:

■ Editing Unicenter CA-Insight IQL requests

■ Browsing the REVIEW output of an IQL request

■ Edit SQL for EXPLAIN support

5–44 System Guide Online User Interface Operation and Customization

Requirements

The following sections describe the requirements for using the online user interface with the data collector.

Data Collector Communication

The user interface communicates with the data collector in one of two ways, depending on whether the data collector is on the same MVS image as the Unicenter CA-Insight user.

■ If the user is on the same MVS image as the data collector, the data transfer is accomplished by using the cross-memory routine owned by the Unicenter CA-Insight PC Owner routine. See Operating the Program Call (PC) Owner.

■ If the user is remote, the Unicenter CA-Insight Remote Access Facility (RAF) is used. See Remote Access Facility Commands for more information.

Exiting the user interface or selecting another DB2 subsystem to monitor does not stop the data collector or any active IQL requests.

The user interface connects to the data collector with a user ID it acquires from a user exit routine. Each user interface acquires its user ID from the applicable NSIGHTEX routine. See the “NSIGHTEX User Exit” appendix for details.

TSO

The NSIGHTEX exit routine sets the Unicenter CA-Insight user ID from the TSO User ID.

VTAM

The NSIGHTEX exit routine sets the Unicenter CA-Insight user ID from the user ID entered on the VTAM User Interface LOGON panel or from the initial Unicenter CA-Insight logon command.

Batch

The NSIGHTEX exit sets one of two user IDs depending on the environment that is running. If the batch job is executed under TSO, the TSO User ID will be used user interface. Otherwise the user ID is taken from the USER= parameter of the JOB card.

Operation and Customization 5–45 Online User Interface Operation and Customization

DD Statements

The following DD statements are common to the TSO and VTAM online user interfaces and the batch user interface.

IUIMAPS

This DD statement defines the MVS library containing Unicenter CA-Insight user interface messages, panels and plot entries. You can customize the messages and panels, which have formats similar to ISPF messages and panels. You can also specify a concatenation of IUIMAP libraries—however, the libraries must be on similar devices (for example, one cannot be on a 3380 while the others are on 3390s).

REQUESTS

This optional DD statement defines the MVS library that contains Unicenter CA-Insight’s IQL requests. If this statement is not specified, all started requests will come from the data set specified in the REQLIB parameter in the data collector IDDCPRMS member. REQUESTS DD statements cannot be concatenated: instead, a new facility has been provided, the REQUESTS2 DD statement. For example: //REQUESTS DD DISP=SHR,DSN=‘request library 1’ //REQUEST2 DD DISP=SHR,DSN=‘request library 2’

Should be used in the JCL for the VTAM Online User Interftace and the batch user interface.

A sample REQUESTS DD statement the CLIST for use in TSO is: FREE FI(REQUESTS,REQUEST2) IF &REQLIB=Y THEN - DO ALLOC FI(REQUESTS) DA(‘request library 1’) SHR ALLOC FI(REQUESTS) DA(‘request library 2’) SHR ENDDO

The order in which the libraries are searched for a request are first REQUESTS and then REQUEST2.

SYSPARMS

The SYSPARMS DD statement defines a file containing user interface parameters such as the table of available data collectors used to build the PickDB2 panel.

5–46 System Guide Online User Interface Operation and Customization

DBGPRINT

The DBGPRINT DD statement receives diagnostic user interface messages. Normally, this statement is dummied out. If you have edited the user interface IDUIPRMS member incorrectly, you might need to see these messages to diagnose a user interface initialization problem. The TSO user interface has an execution parameter to name the DBGPRINT using the PRTDD statement.

Customizing User Interface Session Parameters

Several input parameters are required to initialize a Unicenter CA-Insight user session. The following specified parameters indicate DB2 subsystems available to the user as well as other session control parameters. The parameters are obtained from a PDS member defined on the SYSPARMS DD statement. If the SYSPARMS DD statement is missing, the Unicenter CA-Insight user interface will not operate.

The user interface SYSPARMS are generated into 2 members of the SOURCE library by the post install process, which are all concatenated together to form the SYSPARMS for the user interface. The IDUIPRMS member contains all of the user interface SYSPARM settings except for the APPLS parameter. The APPLS parameter is defined in the APPLS member. It is built and updated dynamically during the DB2-specific post install. It is used by all of the data collectors as well as the Unicenter CA-Insight user interface.

Sample Member

The following SOURCE members IDUIPRMS and APPLS are built during the post install process and can be used to customize your user interface configuration at your installation.

Note: Some values (such as hlq and mlq) were initially populated during the post install process. DEFAULTS ******************************************************************** **** EACH APPL SUB-LIST HAS THE FORM **** **** (DB2-LOCATION,SUBSYSTEM,RAF-APPL,RAF-PASSWORD) **** **** * A RAF-APPL OF ‘NOTRAF’ INDICATES USE PC ONLY **** * ELIMINATING VTAM OVERHEAD **** * RAF-PASSWORD IS THE ONLY OPTIONAL PARAMETER ******************************************************************** APPLS=( (DB2LOCATION1,XXXX,NOTRAF,RAFPW1), (DB2LOCATION2,YYYY,NOTRAF,RAFPW2) ) * LCLPSWD=MYPSWD /* LOCAL VTAM PASSWORD(ON DBG001,2,...) REPEAT=YES /* (YES,NO) REPEAT PFKEY FOR DISPLAY UPPER-CASE=NO /* (YES,NO) UPPERCASE OUTPUT

Operation and Customization 5–47 Online User Interface Operation and Customization

******************************************************************** * LIMIT CONNECTIONS FROM USER INTERFACE TO DATA COLLECTORS ******************************************************************** CONNECT=ANY /* (ANY,PC,RAF) CONNECT TYPE ALLOWED ******************************************************************** * CLEANUP MENU PARAMETER ******************************************************************** STOP-REQUESTS=NO /* (YES,NO) YES=>STOP, NO=>PROMPT ******************************************************************** * VTAM USER INTERFACE - DESTINATIONS

* TSO USER INTERFACE - INITIAL VALUE FOR ISPF PROFILE * IN JCL THIS WOULD BE * //SYSPRINT DD SYSOUT=A,DEST=(NODE1,NODE2) ******************************************************************** PRINT-DESTINATION1=NODE1 /* PRINT NODE 1 PRINT-DESTINATION2=NODE2 /* PRINT NODE 2 ******************************************************************** * MIGRATION AIDS - THESE PARMS MUST MATCH IN THE DATA COLLECTOR * ******************************************************************** * TESTVER=V41 /* XXXX ALTERNATE DC * PCSSID=DBGI /* XXXX ALTERNATE PCAUTH (DEFAULT=DBGI) * /* PCSSID USED BY RAF ******************************************************************** * GSS ID FOR THE CONDITION MONITOR ******************************************************************** MSSUB=ISRV ******************************************************************** LOGON-CHECK=NO SECURITY-EXIT=NSIGHTEX SECURITY-FILE=‘hlq.mlq.SECURITY’ TERMINAL=LOGMODE ;

DEFAULTS Statement

DEFAULTS must be the first word in the first input record of the SYSPARMS member.

Keywords

Following are descriptions of the keywords that can be specified on the DEFAULTS statement. Some of the keywords do not have default values. (APPLS=((DB2-list),(DB2-list),...) Specifies a list of DB2 subsystems that the user can monitor. Each subsystem specified here appears in the Unicenter CA-Insight PickDB2 panel. Note: The APPLS parameter is defined in the APPLS member in the SOURCE library. It is used by the data collectors as well as the user interface.

5–48 System Guide Online User Interface Operation and Customization

A comma appears after each entry except the final one. Each entry consists of four positional parameters as follows: (DB2-list) = (location,ssid,RAF-applid,RAF-password)

■ location—(required) specifies the identifier for a DB2 subsystem that is to be displayed on the PickDB2 panel. You can use any descriptive identifier, up to 16 characters in length. In a distributed DB2 environment, this must match the DB2 location name specified in the DB2 Communications Database. The location name will be the same for each entry that specifies a DB2 subsystem in a DB2 V4 data sharing environment. Location name must begin with an alphanumeric character and must be specified in quotes (‘) if it contains special characters. Otherwise, no quotes are needed. Examples: TESTDB2, NYPRODDB2.

■ ssid—(required) is the DB2 subsystem identifier, up to four characters.

■ RAF-applid—(required) specifies the VTAM application ID of the remote data collector that is monitoring the DB2 subsystem identified by the location and ssid parameters. This parameter must be present, but is used only if the Remote Access Facility (RAF) is active. See Remote Access Facility Parameters. Examples: DCAPPL1, NOVTAM. Note: If RAF=NO was specified in the data collector SYSPARMS member (see Remote Access Facility Parameters), specify the RAF-applid value as NOTRAF and do not specify a RAF-password.

■ RAF-password—(optional) this is the password for the data collector specified in the RAF-APPLID. This is used only if the RAF is active. LCLPSWD=pppppppp Specifies a password to be used internally to access the local RAF application. All applications which access this local RAF application must use the same password. See Remote Access Facility Parameters for further details about how Unicenter CA-Insight uses VTAM. REPEAT=[YES|NO] Indicates whether the REPEAT PF Key and its corresponding function of the DISPLAY command are allowed. REPEAT=NO means the function will not be available (default). REPEAT=YES enables a user to monitor a request continuously without pressing the Enter key. The ATTN key terminates the REPEAT function. Users can specify a command in the User Profile panels, which will also terminate the REPEAT function. The default command is REPEAT. See the Unicenter CA-Insight User Guide for more information about the profile. UPPER-CASE=[YES|NO] Indicates whether the PF keys and output will be in uppercase or upper and lowercase. NO indicates upper and lowercase and is the default. YES indicates uppercase only.

Operation and Customization 5–49 Online User Interface Operation and Customization

CONNECT=[PC|RAF|ANY] Indicates whether the user interface is to look for RAF or PC Owner connections exclusively or any active connection. Bypassing a VTAM search can result in improved performance. Using PC search can result in improved performance if remote access is not needed. STOP-REQUESTS=[YES|NO] Indicates whether to stop all requests when a user exits the user interface. YES indicates that all requests will be stopped on exit. NO indicates that the user will be prompted on exit to ‘keep’ or ‘cleanup’ requests that are running. PRINT-DESTINATION1=print-node1 Specifies a destination for a SYSOUT data set. For more information, see the IBM MVS/ESA JCL Reference guide. PRINT-DESTINATION2=print-node2 Specifies a destination for a SYSOUT data set. For more information, see the IBM MVS/ESA JCL Reference guide. TESTVER=xxxx Specifies a 1-4 character identifier for a separate unique data collector which can be started on the same DB2 subsystem as another data collector. This parameter must match the value specified in the data collector parameters (see Migration Aids). PCSSID=xxxx Specifies a unique MVS subsystem ID for the PC Owner with which the data collector is to operate in conjunction. This parameter must match the value specified in the data collector parameters (see Migration Aids). MSSUB=ISRV Specifies the MVS subsystem name for the Global Subsystem IMOD facility (for more information, see the “Installing Optional Components” chapter) If you have changed the name in that step, you should also change the MSSUB= value here. LOGON-CHECK=[YES|NO] Indicates whether password validation should be done or bypassed during LOGON to the VTAM user interface. YES indicates that the password will be validated by calling NSIGHTEX at LOGON. SECURITY-EXIT=NSIGHTEX Is an optional parameter that indicates the name of the user security exit routine. If this parameter is omitted, the NSIGHTEX User Exit (see the NSIGHTEX User Exit appendix for more information) is loaded. SECURITY-FILE=hlq.mlq.SECURITY Specifies the name of the security data set to be used to determine the user’s menu at initial logon time.

5–50 System Guide Online User Interface Operation and Customization

TERMINAL=[LOGMODE|LOGMODE2|ON|OFF} Controls the use of extended attributes.

■ LOGMODE—Uses the extended attributes defined by the logmode of the terminal. If the device is defined with Rows=Columns=0, the device will be queried for its attributes.

■ LOGMODE2—Uses the extended attributes defined by the logmode of the terminal. If the device is defined with Rows=Columns=0, Unicenter CA-Insight uses the following values: Rows=24, Columns=80.

■ ON—Forces extended attributes on. This option is provided for diagnostic purposes.

■ OFF—Forces extended attributes off. This option is provided for diagnostic purposes.

TSO User Interface

The TSO user interface requires that the ISPF/Dialog Manager and the ISPF/PDF be available on the MVS system of the TSO user. Most of the features of the TSO user interface require at least one data collector to be active. If this data collector is on a remote MVS image, the Unicenter CA-Insight Remote Access Facility must be operational.

To access Unicenter CA-Insight under TSO, you must modify your ISPF libraries, signon CLIST, or TSO LOGON PROC.

ISPF CLIST

A CLIST is used to invoke the TSO user interface. A sample CLIST called INSIGHT is available on the Unicenter CA-Insight CLIST library. The INSIGHT CLIST was built and customized during the post install process.

You can modify the CLIST as follows:

■ You can control whether the CLIST uses the TSO LIBDEF library allocation function by specifying LIBD(ON) or LIBD(OFF).

■ If LIBD(OFF), you must insure that the Unicenter CA-Insight ISPLLIB, ISPPLIB, ISPSLIB and ISPTLIB libraries are added as data set concatenations to the appropriate DD statements in your TSO LOGON PROCs.

■ Copy the INSIGHT CLIST from the CLIST distribution library into a CLIST library available to all TSO users.

You can also modify the CLIST to force the TSO user interface to pick a specific DB2 subsystem. You do this by adding /DBSUB=ssid to the parm (shown here): ISPFEXEC SELECT PGM(IUISPF) + PARM (PRTDD=&OUTDD,INPDD=SYSPARMS/DBSUB=DB23)

Operation and Customization 5–51 Online User Interface Operation and Customization

The user interface will read the APPLS list in SYSPARMS (see Keywords) and attempt to connect to the data collector running at the location corresponding to the first SSID in the APPL list that matches the parm.

Note: If the user has a PICK for the initial command, it will still be executed.

ISPF Menu

To simplify the invocation of the TSO user interface, add the following line to the TRANS statement in your ISPF main menu: I,’CMD(INSIGHT)’ after the lines )PROC &ZSEL = TRANS(TRUNC (&ZCMD, .) and add the line % I + CA-INSIGHT CA-Insight

IQL Request Library

The allocation of IQL request libraries using the REQUEST DDNAME can name one or more data sets. ISPF limits the concatenation, including data sets defined by the OPTIONS panel, to four. In order to support ISPF split screen with Unicenter CA-Insight on both screens (each command to a separate data collector), the REQUEST library allocation is never freed.

Accessing the TSO User Interface

Typically, the TSO user interface is selected from the ISPF Main Menu. Control is returned to the ISPF Main Menu upon exiting the user interface.

Security Control

The following section describes the process of acquiring the User ID, Security ID, and the Unicenter CA-Insight Menu name in the TSO environment.

User ID

The User ID is validated when the user logs on to TSO. The TSO user ID is found through control blocks by the NSIGHTEX User Exit.

5–52 System Guide Online User Interface Operation and Customization

Security ID

This section applies to RACF or CA-Top Secret 4.3 or greater only.

The Security ID is an additional ID that the NSIGHTEX User Exit sets to facilitate the elimination of specific User IDs from the Security File. At this time, only RACF or CA-Top Secret Version 4.3 or greater can use Security IDs without changing NSIGHTEX.

NSIGHTEX first sets the Security ID from the ACEE GROUP field. In RACF, the ACEE GROUP contains the RACF default group.

Note: In CA-ACF2 or CA-Top Secret 4.2 and earlier, this field is unpredictable and the exit will set the Security ID to “NOGROUP.”

The NSIGHTEX User Exit then checks to see if any ACEE connect groups are specified. If so, the connect groups are searched for the first occurrence of a group starting with “INS.” If a connect group beginning with “INS” is found, the Security ID is set to the value of the group. If you want to use Connect Group names other than those that start with “INS,” modify the NSIGHTEX security exit. For details, see the “NSIGHTEX User Exit” appendix.

Default Menu

The NSIGHTEX User Exit also sets a default menu. This menu is ignored if a menu data set is specified in the user interface SECURITY-FILE parameter. (See Customizing User Interface Session Parameters for details.) The default menu is the System Menu (except for RACF users).

RACF and eTrust CA-Top Secret Users

The following table describes the Unicenter CA-Insight menu associated with each connect group prefix.

Connect Group Prefix Associated Menu Ž INSS System INSD DBA INSA Application INSO Operator INSU Auditor

Operation and Customization 5–53 Online User Interface Operation and Customization

If the security data set is specified, the menu is retrieved from the Security File.

Typically, the ID portion of the Security File uses TYPE=GROUP. This minimizes the maintenance of the Security File. eTrust CA-ACF2 Sites

At eTrust CA-ACF2 sites, Security ID and TYPE=GROUP cannot be used with modification of the NSIGHTEX User Exit. TYPE=USER specifications will use the User’s ID to identify the profile. You can minimize the maintenance in this environment if a prefix of the User ID denotes a logical group, for example a DBA-DBA9999 range specification.

Profile

If a profile is not defined for the user or the profile is defined but has no MENU specification, the user’s access to the user interface is denied.

VTAM User Interface

There are four prerequisites to operating the Unicenter CA-Insight VTAM user interface: 1. The VTAM user interface requires a separate address space. This address space is started by a job or as a started task. 2. The network must have the appropriate VTAM names defined and varied active to VTAM. 3. Most of the features of the user interface require at least one data collector to be active. See Requirements for a discussion of where the data collector gets the User ID. 4. If one or more data collectors are on a remote MVS image relative to the user interface, the Unicenter CA-Insight Remote Access Facility (RAF) must be active.

VTAM Definitions

You must define the VTAM APPLID by adding the following definitions to SYS1.VTAMLST: IDB2USER VBUILD TYPE=APPL IDB2USER APPL ACBNAME=IDB2USER,EAS=nn

where nn specifies the approximate number of concurrent logged on users.

5–54 System Guide Online User Interface Operation and Customization

These statements can be added to an existing member or to a new member in SYS1.VTAMLST. The member name serves as a node name to VTAM and must be different than the APPLID (IDB2USER in this example).

To simplify the manner in which a user logs on to the VTAM user interface, you can create a USS definition table for Unicenter CA-Insight by adding the following to the USSTAB (or use the USSDEF member in the SOURCE library): USSCMD CMS=CA-INSIGHT,REP=LOGON,FORMAT=PL1 USSPARM PARM=APPLID,DEFAULT=IDB2USER USSPARM PARM=LOGMODE USSPARM PARM=DATA

In this example, the user logs on to the Unicenter CA-Insight VTAM user interface by keying Unicenter CA-Insight. The user is then prompted for a User ID and password.

Important! Do not use the VTAM APPLID you established for the Remote Access facility (Step 1. Prepare VTAM). A separate APPLID is required for the VTAM user interface.

Sample JCL

The JCL member IDB2VUJ in the SOURCE library can be used to start the VTAM user interface as a job. The JCL member IDB2VUS in the same library can be used to start the VTAM user interface as a started task.

A listing of member IDB2VUS and the explanation of each statement can be found in IDB2VUS Sample JCL Member.

Starting the VTAM User Interface

Before the VTAM user interface can be started, its VTAM APPLID must be varied active to VTAM. If the VBUILD statement (described under VTAM Definitions ) is in the IDB2NODE member of SYS1.VTAMLST, the following MVS console command can be issued to activate the VTAM node: V NET,ACT,ID=IDB2NODE

When the node is varied active, all components of the node will become active. You can check the status of the node or the VTAM APPLID by using the following MVS console command: D NET,ACT,ID=name

where name is the node name or the VTAM APPLID.

VTAM provides a mechanism for starting a list of nodes each time VTAM starts. Typically, this configuration list is named ATCCONxx in SYS1.VTAMLST.

Operation and Customization 5–55 Online User Interface Operation and Customization

Starting

You can start the VTAM user interface as a job by submitting the JCL member IDB2VUJ found in the SOURCE library. You can also issue the MVS start command to execute the VTAM user interface as a started task using the proc member IDB2VUS found in the SOURCE library.

Accessing Using the VTAM User Interface

How a user logs on to the VTAM user interface after it is started depends on exits within your MVS installation. From a VTAM application prompt, the user must enter a LOGON command naming the Unicenter CA-Insight APPLID or enter the name defined in the USSTAB as previously described. The following are examples of possible LOGONs: LOGON APPLID(IDB2USER) DATA(USERID/PASSWORD) LOGON APPLID=IDB2USER DATA=USERID/PASSWORD CA-INSIGHT

If the user enters the LOGON command without the DATA parameter, or the specified USERID and/or PASSWORD is invalid, then he or she is prompted for a User ID and password. At this point the NSIGHTEX user exit controls access. The sample NSIGHTEX member provided in the SOURCE library requires that a User ID be entered. Once logged on to Unicenter CA-Insight, the user can exit the VTAM user interface by entering X on any command line or by pressing the PF3 key from the Main Menu.

Stopping the VTAM User Interface

You must issue the following MVS console command to stop the Unicenter CA-Insight VTAM user interface: F jclname, SHUTDOWN

where jclname is the name of the VTAM user interface started task name.

You can also issue an MVS CANCEL console command for the VTAM user interface started task name.

5–56 System Guide Online User Interface Operation and Customization

Security Control

When using the VTAM user interface to access Unicenter CA-Insight, the NSIGHTEX User Exit provides a basic level of User ID and password validation through a RACROUTE call to the your installation’s external security package (for example, RACF, CA-ACF2, or CA-Top Secret). Step 4. Modify Security for the NSIGHTEX User Exit describes the steps you need to take to permit the VTAM user interface to call the external security package for User ID and password validation.

NSIGHTEX does not need to be modified for User ID and password validation.

LOGON-CHECK=NO

When the IDUIPRMS member parameter LOGON-CHECK is set to “NO”, it allows the installer to use the product without calling the external security package. When LOGON-CHECK=NO is specified, users are prompted for the User ID and password three times. The User ID must not be blank or already in use. The Security ID is then set to PASSWORD, and the menu is set to SYSTEM. If a menu data set is specified, the menu is retrieved from the Security File as the default menu.

LOGON-CHECK=YES

The user is prompted three times for a valid User ID and password. If the User ID is not blank or already in use, the NSIGHTEX User Exit is called to issue the RACROUTE call to your security package. If RACROUTE allows access, the User ID is used as is.

Once the User ID has been validated, the controls for Security ID and Default Menu are the same as those under TSO.

Customizing the Online User Interface

The following key components of the user interface can be customized:

■ User interface session default values

■ Product panels

■ PF key labeling

■ Display navigation

■ Panel Libraries

Operation and Customization 5–57 Online User Interface Operation and Customization

Unicenter CA-Insight has two panel libraries:

■ IUIMAPS contains alterable panels.

■ INSPLIB allows the IUIMAPS panels to function in a TSO environment.

Important! Do not change the panels in the INSPLIB library.

The IUIMAPS panels are similar to ISPF panels. The IUIMAPS panels provide a very restricted subset of ISPF panel functionality but work both in the TSO and VTAM user interfaces. You can edit these panels to meet a particular need of your shop. The types of changes you can make are limited to changing literals on the panels and modifying the options on menus.

Help displays also come from the IUIMAPS library (although the format has no similarity to ISPF panels). When the HELP function is called, control remains within the help function until all help panels have been traversed. Help navigation is defined within the help panels themselves. New help can be added. See member DBGHDEST in the IUIMAPS library for an example of navigation.

Non-help panels can be added but they will not be accessed unless the Unicenter CA-Insight user interface knows about them. The COMMANDS member in the IUIMAPS library associates panels with commands, help panels, and PF Key sets. To add a new request and an associated help panel, you must alter the COMMANDS member.

User Interface Session Default Values

TSO and VTAM users can customize their Unicenter CA-Insight online user interface sessions by making changes in the User Profile panels (for descriptions, see the Unicenter CA-Insight User Guide). But the session profile baseline values (those that appear the first time the product is used) are established in the DEFAULTS member in the IUIMAPS library. You can make changes to this member to establish a different profile baseline from the one that is supplied with Unicenter CA-Insight, for example to provide different default values.

DEFAULTS provides values for EXPLAIN, PICK, and scrolling options, print lines per page, repeat interval, turquoise/blue transposition, and the default SYSOUT class.

The standard DEFAULTS member is shown on the next page. Instructions for changing the values can be found toward the bottom of the member in the library. *DEFAULTS FOR USER INTERFACE SESSION * VALUE FOR FIRST KEY FOUND IS USED *------* KEY ,VALUE *------EXPLEDIT,N /*N=EXPLAIN DOES EXPLAIN EXPLEDIT,Y /*Y=EXPLAIN DOES EDIT (TSO)

5–58 System Guide Online User Interface Operation and Customization

PICK ,* /* STATUS IF #SSIDS <6 PICK ,Y /*Y=PICK STATUS PICK ,N /*N=PICK NO STATUS PRINTLPP,55 /*PRINT LINES/PAGE PRINTTYP,D /*PRINT TYPE REPEAT ,02,10,99 /*REPEAT LOW,DEFAULT,HIGH SCROLL ,PAGE /*SCROLL AMOUNT TYPES SCROLL ,CRS /* SCROLL ,HALF /* SCROLL ,DATA /* SYSOUTC ,A /*SYSOUT CLASS TURQBLUE,N /*N=LEAVE BLUE BLUE, TURQ TURQ TURQBLUE,Y /*Y=TRANSPOSE TURQ/BLUE

Where multiple occurrences of the keyword occur (such as PICK and SCROLL), only the value of the first keyword is used.

Product Commands

The relationship between Unicenter CA-Insight commands and their related help and data panels is established in the COMMANDS member of the IUIMAPS library, a portion of which is shown in the following: *USER INTERFACE COMMANDS *------* COMMAND PANEL HELP CODENAME PF KEYS ,STACK COMMENTS *------APPLS ,2,DBGSMMA ,DBGHMMA ,INITMENU,INITMENU,MENUA AUDITORS,2,DBGSMMU ,DBGHMMU ,INITMENU,INITMENU,MENUU BROWSE ,2,DBGSBRO ,DBGHBRO ,BROWSE ,BROW ,START CHECK ,2,DBGSCHK ,DBGHCHK ,CHECK ,CHEC ,CHECK COMMANDS,1,DBGSCMD ,DBGHCMD ,COMMANDS,CMDS ,FLASH COND ,4,DBGSCON ,DBGHCON ,COND ,BROW ,DISPL DBAS ,2,DBGSMMD ,DBGHMMD ,INITMENU,INITMENU,MENUD

The commands are listed in alphabetical order.

You would add entries to this member if you:

■ Have a site-specific start panel

■ Have additional initial menus

Important! Due to the critical nature of this member for the operation of the product, we recommend that no changes be made without first consulting Unicenter CA-Insight Client Services.

If you are interested in changing the contents of the panels themselves, consult the Unicenter CA-Insight Writing Requests guide.

Operation and Customization 5–59 Online User Interface Operation and Customization

PF Key Sets

The PF Key table (IUIMAPS member PFKEYS) specifies sets of PF Keys (1-12). (PF Keys 13-24 are handled through the User Profile). Each set is uniquely named, and relates to the PF Keys column in the COMMANDS member (detailed on the previous section). A portion of the PFKEYS member is shown here: * PF Key sets * ------* name f1 f2 f3 f4 f5 f6 * f7 f8 f9 f10 f11 f12 * ------ALTMENU Help Split End

BROW Help Split End Rfind Up Down CHEC Help Split End Rfind Up Down Left Right CMDS Help Split End Up Down CONS Help Split End Rfind Up Down DISP Help Split End Rfind Up Down

The PF Key set name is shown in the left-most column (ALTMENU, BROW). Each set consists of two lines corresponding to the PF Keys shown in the comment box at the top of the member.

For example, the ALTMENU PF key set has only the following PF keys defined:

■ PF1—Help

■ PF2—Split

■ PF3—End

If you need a new set of PF keys, add one and then specify the PF Key set name in the appropriate COMMANDS member entry.

Note: Some PF Keys are dynamically added and/or overlaid in the application.

Display Navigation

Many IQL request-based panels use a View bar to display and control the linkage between different panels. The View bar is highlighted in the following System Statistics panel example:

Menu Print Tools Help CA-Insight SE19257 DB23 MVSB1 _ 1 SnapShot 2 Buffer Pool 3 EDM Pool 4 Logs 5 Threads 6 More...

R/SYSSTATS System Snapshot - 30 seconds Row 1-14 of 22

5–60 System Guide Online User Interface Operation and Customization

Unicenter CA-Insight lets you customize the View Bar if you:

■ Would prefer a different order for the selections

■ Want to add or remove items

■ Want to provide a second probe

A series of members in the REQUESTS library maintains the display and control of the View bar options. The member names start with MG, and are divided along functional lines (threads, system, attachments, and so on).

The information for the System Statistics View bar can be found in the MGSYSTEM member of the REQUESTS library. The portion of MGSYSTEM that pertains just to the System Statistics View bar is shown here: * (unqualified navigation) System Statistics MGsystem: menu-group

item="Start" view("SnapShot","R/sysstats") SELECT=("HISTORY",item=hssnap) pfkey=(9,"Plot","Plot PSYSSTAT") pfkey=(12,"History","History") view=("Buffer Pool","R/buflists") select=("*",item buffdetl) SELECT=("HISTORY",item=hsbufl) pfkey=(9,"Plot","Plot PHBP0ACT") pfkey=(12,"History","History") view=("EDM Pool","r/edmpool") SELECT=("HISTORY",item=hsedm) pfkey=(9,"Plot","Plot PHEDMUSD") pfkey=(12,"History","History") view=("Logs","R/LOGALLOC") SELECT=("HISTORY",item=hsloG) pfkey=(12,"History","History") view("Threads","D/thrdactv") select=("*",item listsome) view=("More...","M/msystem") SELECT=("1",item=MVSstats) SELECT=("2",item="DSN") SELECT=("3",item="SYSPARMS") SELECT=("4",item=logstat) SELECT=("5",item=multisyt) SELECT=("6",item=sysdrain) SELECT=("7",item=prefetch) SELECT=("8",item=syslocks) SELECT=("9",item=syssvcs) SELECT=("10" item="SQL") SELECT=("11" ITEM=sysrmote) SELECT=(“12” ITEM=sysbind) SELECT=(“13” ITEM-sysSTRG) SELECT=(“14” ITEM=sysgbuf) SELECT=(“15” ITEM=sysgLOCK) SELECT=(“16” ITEM=sysdynp) SELECT=(“17” ITEM=sysrtn) SELECT=(“18” ITEM=sysdyns)

Each of the numbered options on the panel relates directly to a corresponding view statement. For example, view=(“EDM Pool”,”r/edmpool”) is the statement for View bar option 3 (EDM Pool) on the System Statistics panel.

Operation and Customization 5–61 Online User Interface Operation and Customization

Customizing Navigation with Menu-Groups

The customization of the Unicenter CA-Insight navigation (other than panel TRANs) requires knowledge of the Menu-Groups’s:

■ General characteristics.

■ The Menu-Groups used by Unicenter CA-Insight.

■ Basic Syntax.

■ How the user interfaces use the control blocks generated by the syntax.

Each of these is detailed in the sections that follow.

Important! Incorrectly modifying Menu-Groups can impact the stability of both the user interface and the data collector!

General Characteristics

In general, the Menu-Group requests are similar to all other requests, but they differ in several important ways:

■ Menu-Group requests are started by the data collector’s startup request in the SOURCE library, or by the START command of the user interface. A START-MENU-GROUP security parameter controls who can issue the START command for a Menu-Group. STOP, PAUSE (FREEZE), RESET, and RESUME are invalid. Menu-Groups don’t involve DB2 traces. A START of Menu-Group “XYZ” replaces any prior “XYZ” Menu-Group.

■ Menu-Groups should be defined the same on all data collectors. Different Menu-Group definitions will cause unpredictable results!

Menu-Groups

The Menu-Groups used by the distributed Unicenter CA-Insight product are the seven members of the REQUESTS library whose names begin with “MG”: MGMSGS This is used by the Message routine to define the View bar. If you change this member, the Message facility could become completely disabled. MGATTACH Used for CICS and IMS attachments. This member is named in the initial menus (those IUIMAPS members beginning with DBGSMM).

5–62 System Guide Online User Interface Operation and Customization

MGSYSTEM Used for real-time System displays. This member is named in the initial menus (those IUIMAPS members beginning with DBGSMM). MGSYSHST Used for historical System displays. This member is named in the initial menus (those IUIMAPS members beginning with DBGSMM). MGTHREAD Used for real-time thread displays. This member is named in the initial menus (those IUIMAPS members beginning with DBGSMM). MGTHDHST Used for historical thread displays. This member is named in the initial menus (those IUIMAPS members beginning with DBGSMM). MGPROBE Defines the requests that belong to a probe. A probe name can be used instead of a request name in request-based user interface commands. The probe names are named in the Start menus (panels DBGUSI*).

Menu-Group Syntax

The Menu-Group has a very restricted syntax, as follows: mg-name: MENU-GROUP ITEM=”item-name” VIEW=(“view-title”,“view-type/view-information”) SELECT=(“select-value”,ITEM=”select-item”)

PFKEY=(pfkey-number,“pfkey-label”,“pfkey-command”)

VIEW=(“view-title”,“view-type/view-information”)

ITEM=”item-name” ...... ;

The italicized phrases are described as follows:

■ mg-name—Provides a unique name for each Menu-Group request. The mg-name values of MGMSGS and MGPROBES serve unique uses as previously described. The mg-name can be used in a DISPLAY command.

■ item-name—This is the name of a group of views. item-name should be unique within all of the Menu-Groups. item-name can be used in one of two ways: – Name specified in the ITEM= clause – SELECT=(“select-value”,ITEM=select-item) If selected, the current ITEM is stacked and the ITEM= item-name is processed.

Operation and Customization 5–63 Online User Interface Operation and Customization

– For MGPROBES only, ITEM= defines a valid Probe name. This name can be used within a panel to start and manipulate Probes (see panel DBGSMMA).

■ view-title—The string used on the View Bar line if more than one view is defined for an item. The View Bar is limited in size, and views that do not fit will not be shown.

■ view-type—Choose one of the following: – R—Simple request – D—Simple request but not from DISPLAY command – M—Menu – S—History selection panels – H—History request or exception – X—Active Thread exception

■ view-information—This is based on the view-type. Choose one of the following:

■ R—Request name – D—Request name – M—Menu name (member of IUIMAPS) – S—History selection information – H—History request or exception name – X—R/label for thread exception display

■ select-value—The select-value has one of these following uses (formats): – “a menu selection”—1-9, 10-nn – “an action code”—An action code – “”—A special action code – “History”, “Detail”, “Summary”—A special directive

These formats are described in “Context.”

■ select-item—The new item to navigate to, if selected.

■ pfkey-number—The number of a PF key to override (1, 4, 5, 6, 10, 11, 12). Use with pkey-number and pfkey-command to fully define the overridden PF key. Do not customize PF keys 2, 3, 7, 8, and 9. You can customize PF keys 10 and 11 if your request is not greater than 80 columns wide.

5–64 System Guide Online User Interface Operation and Customization

■ pfkey-label—The value to show for the override PF key on the panel (used with pfkey-number and pfkey-command).

■ pfkey-command—The command to execute if the pfkey is used (used with pfkey-number and pfkey-label).

How the User Interfaces Interact with Menu-Groups

The user interfaces use the Menu-Groups to navigate, but in the process of navigation, the user interface carries along contextual information from the requests and from the view information.

The following is broken down into how Menu-Groups get invoked, transition between requests, and how the context of what DB2 objects is determined.

Menu-Group Invocation

Menu-Groups are invoked in one of the following ways:

DISPLAY name

DISPLAY commands are issued by typing the command on the Command line (==>) or can be done by menu selection based on a panel’s TRANS function. In both cases, the display routine sees the command on the Command line.

The operand of the DISPLAY command (name) is usually the name of a request. The operand from a panel is typically a Menu-Group name.

The display processor uses the name value to search all of the data collector-defined menu-groups. The first occurrence of name as a menu-group or as a “R/name” type view is used. “H/”, “X/”, and “M/” types will not match.

■ If the name is not found, it will be used to retrieve the output of a request within the data collector. No navigation from the displays request will be provided and no View Bar will be shown.

■ If the name is a Menu-Group name, the first view-information of the first view of the first item will be used to display the View Bar and provide subsequent navigation. If the Menu-Group is one of Unicenter CA-Insight’s menus, you can reorder the View Bar without needing to change the panel. Subsequent navigation will use the information available to this item and view.

Operation and Customization 5–65 Online User Interface Operation and Customization

■ If the name is found to be an “R/name” type view, this item and view information will be used to display the view bar and provide subsequent navigation. The “R/” versus “D/” types permit the collection of Menu-Group requests to have multiple occurrences of one request. Unicenter CA-Insight’s THRDACTV request can be reached from both the Active Subsystems and the Active Threads selections from the Systems Menu. This is done by directing the command “DISPLAY THRDACTV” to the entry defined by the “R/” and ignore the “D/” entry.

■ Defining a Probe—The requests involved in a Probe are defined by the explicit probe commands issued on the terminal’s Command line, or implicitly through a panel’s TRANS statement, or implicitly by the action codes entered on the SHOW panel. When a probe’s definition is required, the MGPROBES request is retrieved and the ITEM= is searched for the name of the probe. The requests involved in the probe are defined in the VIEW=(“view-title”,”view-information”) statement’s view-information string. The view-information has either: – R/name—Standard request in probe – R?/name—detailed request in probe Detailed requests in probes are controlled by the PROBE-DETAIL security parameter and the PROBE-DETAIL batch user interface parameter.

Display Transitions

Display transitions are defined in the SELECT= clause. The selection-value is one of the following: A View or Menu Selection A menu selection value is a value entered in the view entry field or the Command line. Unicenter CA-Insight navigation should never have a menu with a View Bar because this makes the selection ambiguous. The menus defined by Unicenter CA-Insight’s display navigation are not Unicenter CA-Insight panels and cannot use the TRANS statement. The Views are numbered on the panel according to the order they appear in the Item. If this view is an “M/” entry, the current View is stacked and the new View processed. Otherwise, the View replaces the current View. “M/” views are Menu Views. Menu Views are stacked to avoid the ambiguity of View-versus-Menu selection. If Menu Views are used, they should be the last View, and give the terminal user the “...” visual clue that it is different. If a Menu selection is entered, the current item is stacked and the select-item processed.

5–66 System Guide Online User Interface Operation and Customization

“an action code” An action code is a value typed to select a screen object or the placement of the cursor into the action field of a screen object. Commonly, “S” is used to select an Item. An “*” will select any value. “” The value within the “< >” is an action code as described previously. The “< >” notation is reserved for the THRDLOCS request. It directs the request to change data collectors by using the location information provided in the KEY of the request. “History”, “Detail”, or “Summary” When these values are typed on the Command line or are invoked through a PF key, they will provide for the transition to another Item by stacking the current Item and processing the select-value. “Detail” and “Summary” are also explicit directives to the history component of the display. Context The transition from one panel to another can carry with it a context. SELECT-KEY and FOCUS-KEY are used to pass thread ID fields (AUTH-ID, CORR-ID, PLAN-NAME, CONN-NAME, and so on), the data set name from the XPB0 record to requests using XPB0 or EDB records, and the active RCT module name from the CRCT record to requests using the CRCT or CRCTSS records. KEY and INKEY are used to pass all other fields.

Example 1: Record Information

If you select a thread on the Thread Active (THRDACTV) panel, you are shown Thread Detail (THRDDETL) for that thread. Each “thread” is a separate record. Additional displays at this level continue to carry this “thread” context.

The context is carried because:

■ The THRDACTV request has a SELECT-KEY=YES specification. This means that each line of the panel carries the context of a “thread.”

■ The THRDDETL and associated requests have a FOCUS-KEY=YES specification. This means that these requests should use that same “thread” context.

Operation and Customization 5–67 Online User Interface Operation and Customization

Example 2: Record Repeating Section Information

If you select a Buffer Pool on the Buffer Pool List (BUFLISTS) panel, you are shown Buffer Pool detail reports for a particular Buffer Pool. The Buffer Pools are not represented as separate records, but as repeating sections of one record. In this case, the “Buffer Pool” context must be carried.

The context is carried because:

■ The BUFLISTS request has a KEY(buf-pool-name) specification. This means that each line of the panel carries the context of one “Buffer Pool.”

■ The BUFEXCPS and associated requests have a INKEY(buf-pool-name) specification. This means that these requests use that same “Buffer Pool” context. In other words, the information displayed on the BUFEXCPS panel is for the Buffer Pool selected from the BUFLISTS panel.

Linking Requests

A typical situation in which you would want to link requests is the case where one request lists events or objects and a second request provides detail information about one of the items in the list. The issues we have to deal with in order to implement linked requests are:

■ Selection—How to allow an item in the list to be selected

■ Navigation—How to specify which request is the detail request

■ Context passing—To tell the detail request which item was selected

We illustrate how requests are linked by looking at BUFLISTS, BUFEXCPS and MGSYSTEM.

Selection

An item in a list is selected by entering something in a field. BUFLISTS lists all Buffer Pools. The first field in the request is: ‘.’ (AT=M HELP=CURSLCT)

This AT=M means the field is modifiable. Initially it will display as a period, but the user can key any character in the field. The user can also cursor-select the field by placing the cursor in the field and pressing Enter.

The next field in the request identifies the Buffer Pool: BUF-POOL-NAME (PF=A7,HC=C,HD=‘Pool’)

5–68 System Guide Online User Interface Operation and Customization

This is the key which can be used to pass context to a request which reports more detail for this particular Buffer Pool.

All the remaining fields in the request are data fields which describe attributes of the Buffer Pool or indicate the level of activity in the pool. They are only a few of the many fields associated with Buffer Pools. The list screen shows fields that might prompt you to look into the Buffer Pool statistics in more detail.

Navigation

The linkage between two requests is defined in a menu-group request. All of the real-time system statistics requests are linked together in the MGSYSTEM request. For the purposes of this example, we’ll take the requests out of that context. Linking two requests together in a menu-group request could be as simple as: MGXAMPL: MENU-GROUP ITEM="ANAME" VIEW=(" ","R/BUFLISTS") SELECT=("*",ITEM=BUFFDETL) ITEM=‘BUFFDETL’ VIEW=(" ","R/BUFEXCPS")

MGXAMPL is a menu-group request. In order for Unicenter CA-Insight to know about this navigation, MGXAMPL has to be started. The request has two entities which are called ITEMs. Each ITEM has a name, so that it can be referenced. Each item, in this example, has a request. The “select” statement says that any character can be used to select the BUFFDETL item from BUFLISTS display. The BUFFDETL item will display the first view in its list of views. In this case, the request BUFEXCPS will be displayed whenever a line in the BUFLISTS display is selected.

Context Passing

The issue of context is discussed in Context. Because our example is not thread-based, FOCUS-KEY and SELECT-KEY are not used. BUFLISTS uses KEY(BUF-POOL-NAME) to pass the Buffer Pool ID to BUFEXCPS. BUFEXCPS uses KEYIN(BUF-POOL-NAME) to identify the which Buffer Pool’s data is to be displayed.

Operation and Customization 5–69 Operating the Batch User Interface

Operating the Batch User Interface

This section describes how you can use the Unicenter CA-Insight batch user interface to start, stop, reset, and resume IQL requests in an active data collector and signal the data collector to reload the OBID table.

The batch user interface is not the Batch Report Writer or an interactive display interface. It is, however, a limited function Unicenter CA-Insight interface that runs batch mode using common user interface code. It is most commonly executed as a scheduled job.

The main uses for the batch user interface are:

■ Extracting reports from Unicenter CA-Insight output files.

■ Monitoring off-hours.

■ Reloading the OBID table.

Extract Reports from Output Files

You can use the batch user interface to copy reports then re-initialize output files. You would use this if you run the data collector continuously (data collector parameter NONSTOP=YES ) and periodically (e.g. daily) need to extract reports from Unicenter CA-Insight output files. For this requirement, you can run a batch job with the following steps: 1. Stop IQL request, freeing the ENQ on the output data set. 2. Copy Unicenter CA-Insight output file to disk or tape. 3. Initialize Unicenter CA-Insight output file. 4. Restart IQL request.

Off-Hours Monitoring

Use the batch user interface to perform specific monitoring at off-hours. For example, if you have a recurring performance problem with a batch job that runs at 3:00AM, you could start and stop IQL requests using the batch user interface. The batch user interface JCL and commands can be placed in the same jobstream as the problem batch job. This provides you with very timely and specific performance information. To do this, you can run a batch job with the following steps: 1. Start IQL requests. 2. Run problem batch job. 3. Stop IQL requests.

5–70 System Guide Operating the Batch User Interface

Reload the OBID Table

Use the batch user interface to run a jobstep to issue the OBID command that instructs the data collector to reload its OBID table. Typically, you would insert this jobstep after the step that builds the OBID table.

Batch User Interface Requirements

The batch user interface has the following requirements:

■ Most features of the interface require at least one data collector to be active.

■ If one or more data collectors are on a remote MVS image relative to the interface, the Remote Access Facility (RAF) must be operational.

Operational Overview

When you run the batch user interface, a connection is established between the batch address space and the data collector identified in the DBSUB input parameter. (See Requirements for a discussion of where the User ID gets assigned to the batch user interface). If the data collector uses security (SECURITY=YES as an initialization parameter), then the User ID must have permission, as defined in the data collector security file, to execute the actions you want to perform. See the “Security” chapter for more information. The COMMAND input parameter describes the actions you want to perform.

If the command is START (to start an IQL request), the batch user interface opens the request library specified in the JCL, reads the IQL request member or members specified in the REQUEST parameter, and sends the request to the data collector. If the command is STOP, the batch user interface sends the request name to the data collector and the request is stopped.

The DBGPRINT DD statement records the results of each action in the form of a one-line message. A condition code is also set so you can control the execution of subsequent steps in the job.

Sample Jobs

Unicenter CA-Insight is distributed with three sample batch user interface jobs (located in the SOURCE library). They are:

■ IDB2BUJ1—Invokes the batch user interface to start one or more IQL requests

■ IDB2BUJ2—Invokes the batch user interface to stop one or more IQL requests

Operation and Customization 5–71 Operating the Batch User Interface

■ IDB2BUJ3—Invokes the batch user interface to demonstrate a job that starts then stops the application probe.

Details about IDB2BUJ1 and IDB2BUJ2 can be found in Starting and Stopping Requests.

Required DD Statements

No matter which JCL you use, the batch user interface requires the following DD statements, except for REQUEST2, which is optional: STEPLIB Unicenter CA-Insight Load Library IUIMAPS Unicenter CA-Insight Panels and Messages SYSPARMS Unicenter CA-Insight batch user interface parameters DBGPRINT Unicenter CA-Insight Printed Messages REQUESTS Library containing IQL requests to be started REQUEST2 An optional 2nd request library. The REQUESTS DD statement cannot be concatenated, so REQUEST2 can be used to specify a second PDS.

Required Parameter File

The batch user interface requires the following parameters to be input in a file allocated by the SYSPARMS DD statement: SECURITY-EXIT=NSIGHTEX Is a required parameter that indicates the name of the user security exit routine. COMMAND=[START|STOP|PAUSE|RESET|RESUME|OBID] Specifies the action to take on the IQL requests included on the REQUEST parameter. REQUEST=(‘xxxxxxxx’,’xxxxxxxx’,...) Specifies a list of IQL request names and probe names to be processed. In the case of a START command, each request in the list must exist in the library referenced by the REQUESTS DD statement. DBSUB=xxxx Specifies the 1-to-4 character DB2 subsystem name monitored by the data collector that the batch user interface will communicate with.

5–72 System Guide Operating the Batch User Interface

APPLS=((DB2-list)) Specifies detailed information concerning the DB2 subsystem entered in the DBSUB parameter where (DB2-list) = (location, ssid, RAF-applid, RAF-password). START-QUALIFY=[YES|NO] Specifies whether one or more of the following QUALIFY statement will be used to qualify the request. string is the appropriate value (that is, Plan, Authorization ID, and so on) for the parameter. Wildcard characters are allowed. If not specified, the default is blank (that is, parameter not used). QUALIFY-PLAN=‘string’ QUALIFY-AUTH=‘string’ QUALIFY-OPER=‘string’ QUALIFY-CONN=‘string’ QUALIFY-CORR=‘string’ Note: The Authorization ID and Plan enforcement from the Security Profile always takes precedence and are enforced when running the batch user interface. TESTVER=xxxx Specifies a 1-4 character identifier for a separate unique data collector which can be started on the same DB2 subsystem as another data collector. This parameter must match the value specified for the data collector you want the commands to execute on (see Migration Aids). OCCUR=n A one digit number, from 1-9, that identifies the occurrence number for request-based commands. You can specify this parameter if you have START-MULTIPLE=YES in your security profile. PROBE-DETAIL=[YES|NO] Indicates whether the detail request should also be started for COMMAND=START and REQUEST=probename. You can specify this parameter if you have PROBE-DETAIL=YES in your security profile. The default is PROBE-DETAIL=NO. Note: This option has the same functionality as the Detail option on the Start Qualification Panel for probes.

Output Condition Codes

The batch user interface will generate a condition code when the step accessing it has completed.

■ 0 means that the step completed successfully

■ Non-zero means that an error occurred

Consult the Messages Guide for detailed explanations of the error messages.

Operation and Customization 5–73 Operating the Batch User Interface

Starting an IQL Request

JCL member IDB2BUJ1 in the SOURCE library provides an example of how to invoke the batch user interface to start an IQL request. The SYSPARMS statements needed to start one or more requests are shown here: //SYSPARMS DD * DEFAULTS COMMAND=START /* START REQUEST */ REQUEST=(‘SQLTRAC’,’LOCKSUM’) /* IQL REQUEST NAMES */ DBSUB=db2name /* ON THIS SUBSYSTEM */ APPLS=( (DB2LOCATION1,db2name,NOAPPL,NOPSWD) ) SECURITY-EXIT=NSIGHTEX /*

For explanations of these SYSPARMS, see Customizing User Interface Session Parameters.

Stopping an IQL Request

JCL member IDB2BUJ2 in the SOURCE library provides an example of how to invoke the batch user interface to stop an IQL request. The SYSPARMS statements needed to start one or more requests are shown here: //SYSPARMS DD * DEFAULTS COMMAND=STOP /* STOP REQUEST */ REQUEST=(‘SQLTRAC’,’LOCKSUM’) /* IQL REQUEST NAMES */ DBSUB=db2name /* ON THIS SUBSYSTEM */ APPLS=( (DB2LOCATION1,db2name,NOAPPL,NOPSWD) ) SECURITY-EXIT=NSIGHTEX /*

For explanations of these SYSPARMS, see Customizing User Interface Session Parameters.

Security Control

The User ID/Security ID is accessed in the same manner as in the TSO user interface. The menu is set to BATCH and the menu data set is ignored.

The data collector is passed the User ID/Security ID on every call.

5–74 System Guide Operating the Program Call (PC) Owner

Operating the Program Call (PC) Owner

This section discusses requirements and issues concerning the operation of the Program Call (PC) Owner program.

The PC owner program owns the cross-memory routines, which are used to communicate between users and all data collectors executing on one MVS image. The program creates an index to the Cross Memory Services (CMS) program call table, providing access to all Unicenter CA-Insight CMS routines.

The PC Owner program has the following requirements:

■ The PC Owner program requires its own MVS address space.

■ A single copy of this program provides for all data collectors and users simultaneously executing on one MVS/ESA, OS/390, or z/OS image. Once started, this address space remains active until the operating system is IPL’ed. Unlike the data collector, the PC Owner task will not terminate when DB2 terminates. Since it needs to be started only once per IPL, we recommend that it be part of your IPL procedures.

■ One system linkage table index must be available to be dynamically acquired when the PC Owner program is started.

■ The module containing the Unicenter CA-Insight CMS routines requires space in Extended CSA. See the “Data Collector Storage“ appendix for a detailed description of storage requirements.

■ The program also requires a trivial amount of storage in SQA for a table of Program Call (PC) numbers.

PC Owner JCL

The PC Owner program can be started as a batch job or as a started task. Sample JCL for each invocation method is described in the following.

Batch Job Sample JCL

The JCL member IDB2PCJ in the SOURCE library (shown here) provides an example of how to invoke the PC Owner program as a batch job. //jobcards //* //*------//* CA-INSIGHT FOR DB2 INSTALLATION //* //* FUNCTION: JCL TO INVOKE THE CA-INSIGHT PC OWNER AS A BATCH JOB. //* THERE IS ONE PC OWNER PER MVS IMAGE. //* //* NOTES: MIGRATION AID PCSSID CAN BE SPECIFIED (4 CHARACTERS) //* AS FOLLOWS: //*

Operation and Customization 5–75 Operating the Program Call (PC) Owner

//* PARM='/STIMER=YES,PCSSID=V3PC' //* //* DEFAULT VALUE IS 'DBGI'. IF PCSSID IS USED, YOU MUST //* SPECIFY PCSSID IN SOURCE(IDDCPRMS) AND SOURCE(IDUIPRMS) //*------//* //$$$$$$@ EXEC PGM=NSIGHTPC,REGION=2048K,TIME=1440, // PARM='/STIMER=YES,PCSSID=DBGI' //* //STEPLIB DD DISP=SHR, // DSN=your.load.library //* //DBGPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //

JCL Explanation IDB2PCJ EXEC is required. It invokes the PC Owner program (NSIGHTPC) and specifies execution time values for the step.

■ The TIME specifies 1440 to bypass step termination when the step is in a continuous wait for longer than the SMF wait time limit.

■ The PARM field indicates that the program is not to initiate the 10 minute timer loop since the SMF wait time limit will not be in effect. Note the slash (/) preceding the STIMER keyword. This indicates that the parameter is a program-specific parameter. The STIMER keyword is explained in STIMER Parameter. STEPLIB Is normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules. DBGPRINT is required. It allocates an output destination for PC Owner system messages.

5–76 System Guide Operating the Program Call (PC) Owner

Started Task Sample JCL

The JCL member IDB2PCS in the SOURCE library (shown here) provides an example of how to invoke the PC Owner program as a started task. //* //*------//* CA-INSIGHT INSTALLATION //* //* FUNCTION: JCL TO INVOKE THE CA-INSIGHT PC OWNER AS A STARTED TASK. //* THERE IS ONE PC OWNER PER MVS IMAGE. //* //* NOTES: MIGRATION AID PCSSID CAN BE SPECIFIED (4 CHARACTERS) //* AS FOLLOWS: //* //* PARM=‘/STIMER=NO,PCSSID=V3PC’ //* //* DEFAULT VALUE IS ‘DBGI’. IF PCSSID IS USED, YOU MUST //* SPECIFY PCSSID IN SOURCE(IDDCPRMS) AND SOURCE(IDUIPRMS) //*------//* //IDB2PCS PROC TIMER=NO,PRT=Z //IDB2PC EXEC PGM=NSIGHTPC,REGION=2048K,TIME=1440, // PARM=‘/STIMER=&TIMER,PCSSID=DBGI’ //* //STEPLIB DD DISP=SHR, CA-INSIGHT LOAD LIBRARY // DSN=apfdsn //* //DBGPRINT DD SYSOUT=&PRT //SYSUDUMP DD SYSOUT=&PRT

JCL Explanation IDB2PCS PROC Is required if the procedure contains symbolic parameters for which default values are to be specified.

■ The TIMER symbolic parameter can be used to disable the 10 minute timer loop in the program. The default is to enable the loop.

■ The PRT symbolic parameter enables the operator to change the SYSOUT class to one which can be printed. IDB2PCS EXEC Is required. It invokes the PC Owner program (NSIGHTPC) and specifies execution time. STEPLIB Is required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules. DBGPRINT Is required. It allocates an output destination for PC Owner system messages.

Operation and Customization 5–77 Operating the Program Call (PC) Owner

STIMER Parameter

This parameter is used to determine whether the 10 minute timer loop is invoked.

The purpose of the loop is to avoid being canceled by the SMF non-activity wait time limit if it is enabled for the program. This limit is disabled by specifying TIME=1440. The timer loop would not be necessary and would be disabled to avoid CPU and paging activity.

The format of the STIMER parameter is: STIMER=[YES|ON|NO|OFF]

■ YES—Enables the 10 minute timer loop (default)

■ ON—Enables the 10 minute timer loop

■ NO—Disables the 10 minute timer loop

■ OFF—Disables the 10 minute timer loop

PCSSID Parameter

This parameter can be used to specify a PC Owner subsystem different than the default name of “DBGI.” This parameter is mainly a migration aid parameter used to allow more than one PC Owner subsystem to be started at the same time.

The format of the PCSSID parameter is: PCSSID=xxxx

where xxxx is the 1 to 4 character subsystem name to be associated with this PC Owner address space.

Running the PC Owner

The PC Owner program can be started as a batch job or as a started task. Batch job submission is simpler but ties up an initiator. Started task invocation is more complicated but leaves all initiators free. Once Unicenter CA-Insight becomes part of your normal production environment, we recommend that you invoke the PC Owner as a started task.

To make the PC Owner a part of your normal IPL procedure, include the appropriate command statement in the IEACMDxx member of the SYS1.PARMLIB.

5–78 System Guide Operating the Program Call (PC) Owner

Keeping the PC Owner Task Active

The data collector or the user interfaces will not run if the PC Owner program is inactive, so it will take steps to keep itself active. 1. Once the program has been started, it issues an ENQUEUE whose major name is DBUGDB2I and enters an enabled wait. 2. It then awakens every 10 minutes and sets a timer for a new 10 minute period to avoid being canceled by the SMF non-activity timer limit (if active for this job). 3. If the SMF timer-limit has been deactivated for this task, a parameter can be passed to the program at startup which eliminates the 10 minute timer (see STIMER Parameter).

The amount of CPU time used by this task once it is initialized is negligible with the timer running, and non-existent with the timer disabled.

Terminating the PC Owner Program

If you wish to terminate the PC Owner task, you can use an MVS CANCEL or an MVS STOP jobname command (preferred). The program will then release the storage it has acquired in both ECSA and SQA and will terminate connections between the system linkage table index and the other Unicenter CA-Insight address spaces.

Restarting the PC Owner Program

The PC Owner program can be restarted. When restarted, it will pick up the previously used system linkage table index number. The program will probably lose the use of the previously used Address Space ID (ASID).

Troubleshooting

You can also encounter a 047 ABEND during program initialization. This occurs when you attempt to execute the PC Owner program out of a load library that is not authorized. You must authorize the Unicenter CA-Insight load library or move the load modules into an existing authorized library.

You will get a 052 ABEND if you start two PC owner tasks with the same PCSSID parm value.

Operation and Customization 5–79 System Condition Monitor (SCM) Customization

System Condition Monitor (SCM) Customization

This section describes how to customize the System Condition Monitor, as well as how to install additional products for the SCM to monitor.

Customizing the System Condition Monitor

You can customize the following aspects of the System Condition Monitor:

■ Color

■ Exception/Message Lifetime

Customization for exceptions is done in the Exception Definition facility which is described in the Unicenter CA-Insight User Guide. Customization for DB2 messages is described in the following. Customization for messages from products other than Unicenter CA-Insight and DB2 (for example, ADABAS) is described in Adding Additional Products.

Color

The color (or for monochrome terminals, severity word) assigned to an exception or message is defined in the Exception IMOD. For Unicenter CA-Insight, IMOD IDB2MEXC contains the associates exceptions/messages and the colors.

The format of the REXX code is: when exception = ‘excpid’ then color = ‘c’

where ‘excpid’ is the ID of the exception or message, and ‘c’ is the color: G (Green—Ok), Y (Yellow—Warning), and R (Red—Problem). Change the ‘c’ value to assign a different color to the exception or message.

To change the color for Inactive subsystems or systems that are not communicating with the SCM (TIMEOUT status), modify the REXX code in the INTERVAL_CHECK routine at the end of the GETGSTAT IMOD.

Exception/Message Lifetime

Unicenter CA-Insight exceptions and messages are “kept” by the System Condition Monitor for the following amounts of “aging” time:

■ Exceptions—As set in the Exception Definition facility

■ Messages: Problems (Red)—20 minutes

■ Other (Yellow or Green)—7 minutes

5–80 System Guide System Condition Monitor (SCM) Customization

Every sixty seconds, the $DB2CLEAN IMOD goes through the queue and determines whether the above time limits have been exceeded. If so, the exception/message is removed from the queue.

You can customize all of these time parameters to perform “aging” at times more suitable to you by using the IDB2MEXC IMOD.

To Alter Cleanup Time

The ‘cleanup’ program time interval of sixty seconds can be modified in IMOD $DB2CLNUP. Change the time value in the pause statement: 000005 pause(60)

to the desired time value (in seconds).

To Alter Aging Time

The ‘aging’ program time intervals are declared in IMOD IDB2MEXC. The affected section has the following code: 000293 if color = ‘R’ then duration = ‘01200’ /* 20 minutes 000294 else duration = ‘00420’ /* 7 minutes

Change the value (measured in seconds) to the desired time value.

After you have modified one or both IMODs, follow the instructions in the Global Subsystem User Guide to re-compile and re-load the IMODs.

Adding Additional Products

If you will be using the System Condition Monitor with products other than Unicenter CA-SYSVIEW and Unicenter CA-Insight, such as OMEGAMON®, TMON™, and so on, you must create three types of IMODs to define each third-party subsystem:

■ Definition IMOD—Identifies the subsystem to the System Condition Monitor and updates the subsystem_s status at a defined interval. It also ages messages off the SCM.

■ Message IMOD—Filters the messages and passes those that you want the System Condition Monitor to report on to the Exception IMOD.

■ Exception IMOD—Identifies the severity to be assigned to individual messages and stores them as GSS variables.

Operation and Customization 5–81 System Condition Monitor (SCM) Customization

IMODs Supplied for Additional Products

The following IMODs are distributed with the System Condition Monitor to provide customers with examples of how to use the IMOD facility to collect messages from third-party monitors.

The System Condition Monitor provides a convenient way to collect and report on specific MVS, CICS, and DB2 messages. Some third-party monitors have exception components that issue messages about the entity it monitors, and some monitors do not. As such, it is up to the customer to determine what messages to collect and display in the System Condition Monitor, based on the third-party monitors they have installed.

The message processing capability of the System Condition Monitor is fully supported whereas the content of the samples cannot be guaranteed due to vendor- and customer-specific implementations.

Subsystem Definition IMOD Message IMOD Exception IMOD ADABAS ROM_ADABAS MSG_ADABAS ADABEXC DATACOM ROM_DATACOM MSG_DATACOM DCOMEXC JOBTRAC ROM_JOBTRAC MSG_JOBTRAC JOBTEXC IDMS ROM_IDMS MSG_IDMS IDMSEXC IMS ROM_IMS MSG_IMS IMSEXC OMEGAMON/ ROM_OMCICS MSG_OMCICS OMCSEXC CICS OMEGAMON/ ROM_OMVS MSG_OMVS OMVSEXC MVS TMON/CICS ROM_TMON MSG_TMON TMONEXC TMON/MVS ROM_TMVS MSG_TMVS TMVSEXC VTAM ROM_VTAM MSG_VTAM VTAMEXC ROM_USR1 MSG_USR1 USR1EXC Other ROM_USR2 MSG_USR2 USR2EXC Subsystems ROM_USR3 MSG_USR3 USR3EXC

You tailor these IMODs to define the corresponding subsystem to the SCM.

5–82 System Guide System Condition Monitor (SCM) Customization

Before Modifying the Supplied IMODs

All of the supplied IMODs are contained in the IMOD data set (ISET) named Unicenter CA-Insight. Since this ISET is updated with each new release of Unicenter CA-Insight, you should copy the supplied IMODs that you intend to use to a user-defined ISET.

Accessing an IMOD

Take the following steps to access a System Condition Monitor IMOD: 1. Access the IMOD facility by selecting an option from the ISPF menu. (An option for accessing the IMOD facility was added to the ISPF menu during the Global Subsystem installation (see the “Installing Optional Components” chapter). The ISET Selection panel appears. 2. Enter S in the input field (=) to the left of the ISET in which the IMOD resides and press Enter. The IMOD facility displays the IMOD Selection panel for that ISET. 3. Enter E in the input field to the left of the IMOD you want to modify and press Enter. The contents of the IMOD display. 4. Modify the IMOD. 5. Press PF3 to save the modified IMOD. 6. Enter G in the input field and press Enter to compile and load the IMOD. If you see an “*” in the STATUS field, you have a compile error. Start over at Step 3 and you will see the error message.

Operation and Customization 5–83 System Condition Monitor (SCM) Customization

Installing Additional Products to the SCM

We recommend that you use the ISERVE editor to view the REXX code while you read the following installation steps. The examples use the MSG_VTAM, ROM_VTAM, and VTAMEXC IMODs.

Take the following steps to define a subsystem to the System Condition Monitor: __ Step 1: Add a GSS Parameter—Add a WTO ID parameter to the GSS for MVS RUNPARM member to identify the messages the System Condition Monitor is to monitor. __ Step 2: Modify $DB2CLNUP—Modify $DB2CLNUP to execute the definition IMOD at a defined interval. __ Step 3: Modify the Subsystem’s Definition IMOD—Modify the subsystem’s definition IMOD to include the jobnames and VTAM application ID associated with the subsystem. __ Step 4: Modify the Subsystem’s Message IMOD—Modify the subsystem’s message IMOD to specify which messages issued by the subsystem the System Condition Monitor is to ignore. __ Step 5: Modify the Subsystem’s Exception IMOD—Modify the subsystem’s exception IMOD to assign the degree of severity to be associated with individual messages issued by the subsystem. __ Step 6: Recycle GSS—Recycle GSS to activate the new parameters and IMODs.

Step 1: Add a GSS Parameter

In this step, you add a WTO ID parameter to the GSS for the MVS RUNPARM member to identify the messages the System Condition Monitor is to monitor. 1. Access the GSS for MVS RUNPARM member in the GSS parmlib library. This member can have a different name; it is pointed to by the PARMLIB DD statement in the GSS startup procedure. 2. For each set of messages you want the System Condition Monitor to observe, include the following parameter in the RUNPARM member: WTO ID msgid IMOD MSG_imodname where msgid is the prefix of messages issued by the subsystem that you want the System Condition Monitor to observe. Replace imodname with the name of the message IMOD for the subsystem.

5–84 System Guide System Condition Monitor (SCM) Customization

Note: Only 16 WTO ID statements can be declared in the RUNPARM member, including the WTO IDs defined as part of the base System Condition Monitor.

For example, suppose VTAM issues messages with the prefixes AAU, BNJ, CNM, DSI, and IST. To have the System Condition Monitor observe all of these sets of messages, include the following parameters in the RUNPARM member: WTO ID AAU IMOD MSG_VTAM WTO ID BNJ IMOD MSG_VTAM WTO ID CNM IMOD MSG_VTAM WTO ID DSI IMOD MSG_VTAM WTO ID IST IMOD MSG_VTAM

Step 2: Modify $DB2CLNUP

In this step, you change the $DB2CLNUP IMOD to spawn the definition IMOD every 60 seconds. 1. Access the $DB2CLNUP IMOD. 2. Add a line to spawn the exception IMOD.

For example, the following line spawns the IMOD ROM_VTAM: spawnee=spawn(ROM_VTAM)

Step 3: Modify the Subsystem’s Definition IMOD

In this step, you modify the subsystem’s Definition IMOD to include the jobnames and application ID associated with the subsystem. 1. Access the definition IMOD for the subsystem you want to define. 2. Set the “name.n” compound variables as follows: a. Set the “name.0=” variable to the number of jobs associated with the subsystem. b. For each job associated with the subsystem, include the following: name.n=‘jobname’ c. Replace ‘n’ (the “tail”) with an integer. Begin with a tail of 1, and increment it by 1 for each jobname you specify. Replace ‘jobname’ (enclosed in single quotes) with the name of the job that produces the WTOs.

Operation and Customization 5–85 System Condition Monitor (SCM) Customization

For example, in the supplied definition IMOD ROM_VTAM, five VTAM jobs are defined as follows: 000022 name.0=5 000023 name.1=‘NET’ 000024 name.2=‘NETV’ 000025 name.3=‘NETVIEW’ 000026 name.4=‘NETMVS’ 000027 name.5=‘NETSPY’ Since five jobs are defined, name.0 is set to 5. See How the SCM Uses name.n Variables. 3. Set the “type” variable. This is an identifier that appears in the Type column in the System Condition Monitor Global View panel. For example, in ROM_VTAM, the Type is defined as follows: 000029 type=‘VTAM’ 4. Set the APPLID variable to the VTAM application ID of the system you are defining. For example, in ROM_VTAM, the APPLID variable is initially set to NVW05: 000030 applid=‘NVW05’ 5. You can modify the message aging criteria. (“Problem”-level messages are aged off the SCM after 7 minutes. All others are aged off after 2 minutes). For example, in ROM_VTAM, the aging is based on the message color: if color="R" then max_time=420 /* 7 minutes */ 90 000091 else max_time=120 /* 2 minutes */

5–86 System Guide System Condition Monitor (SCM) Customization

Step 4: Modify the Subsystem’s Message IMOD

In this step, you modify the subsystem’s Message IMOD to specify which messages issued by the subsystem are passed on to the Exception IMOD to be stored as GSS variables. You can accomplish this by listing the messages to be excluded (Step 2, Option 1), or by listing the messages to be included (Step 2, Option 2).

If no entries are made in this section, all of the messages beginning with the prefixes indicated in Step 3 will be sent on to the System Condition Monitor. 1. Access the Message IMOD for the subsystem you want to define. 2. Option 1—List Messages to be Excluded Include a statement of the following format in the Message IMOD for each message you want the System Condition Monitor to ignore: IF MSGID=‘msgid’ THEN EXIT Replace msgid with the message ID of the message you want ignored. For example, the following statements in MSG_VTAM cause the System Condition Monitor to ignore the VTAM messages IST097I and IST350I: 000018 IF MSGID=‘IST097I’ THEN EXIT 000019 IF MSGID=‘IST350I’ THEN EXIT

3. Option 2—List Messages To Be Included You can spawn the exception IMOD only for the messages you list. For example: IF MSGID=‘IST663I’ THEN RESULT=SPAWN(‘VTAMEXC’)

Step 5: Modify the Subsystem’s Exception IMOD

In this step, you modify the subsystem’s Exception IMOD to assign the degree of severity to be associated with individual messages passed from the Message IMOD. 1. Access the Exception IMOD for the subsystem you want to define. 2. Include a statement of the following format in the Exception IMOD to specify the severity to be assigned to an individual message: IF MSGID=‘msgid’ THEN COLOR=‘c’ where msgid is the ID of the message you want to assign a severity to. Replace ‘c’ as follows:

■ G—display green, or the word “Ok” on monochrome terminals

■ Y—display yellow, or the word “Warning” on monochrome terminals

■ R—display red, or the word “Problem” on monochrome terminals

Operation and Customization 5–87 System Condition Monitor (SCM) Customization

For example, the following statements could be added to VTAMEXC to cause the System Condition Monitor to display yellow (or ‘Warning’) when the VTAM messages IST530I, IST532I, or IST663I are issued: IF MSGID=‘IST530I’ THEN COLOR=‘Y’ IF MSGID=‘IST532I’ THEN COLOR=‘Y’ IF MSGID=‘IST663I’ THEN COLOR=‘Y’ 3. Identify those messages, if any, which cause removal of other previously collected messages. For example, if Message A records the failure of an IMS-to-CICS connection, and Message B records the establishment of an IMS-to-CICS connection, then you would not want to display Message B in the System Condition Monitor. Instead, when Message B occurred, you’d want to delete the corresponding Message A. If you look at the VTAMEXC IMOD, you will notice a commented-out example in lines 15 through 20. You would specify Message B (the deletor message) to the right of “msgid=” on line 15. You would specify Message A (the message to be deleted) to the right of “msg_to_delete=” in line 16. You would need to replicate the example for each such pair of “deletor/deletee” messages.

Step 6: Recycle GSS

Stop and restart GSS to activate all of the changes you have just made.

How the SCM Uses name.n Variables

When an exception is processed by the Exception IMOD, it stores the jobname issuing the WTO in a local variable called SYSID. It then attempts to store the exception text to GSS in a compound variable. The value in SYSID is used in the tail of that compound variable so that messages for the same subsystem can be stored together as elements in an array.

When you display a System Condition Monitor panel, the GETGSTAT IMOD checks to see if there are messages to be displayed. It does this by constructing compound variable names and checking to see if there is message text stored in those compound variables. In constructing the compound variable names, GETGSTAT uses the name.n variables defined in the Definition IMOD. Under this scheme, if you want to collect WTOs, you must list the issuers’ jobnames in the Definition IMOD. You must ensure that whatever values are assigned to the SYSID variable in the Exception IMOD are also listed in the Definition IMOD’s list of name.n variables.

5–88 System Guide Chapter 6 Security

Unicenter CA-Insight security enables you to control which Unicenter CA-Insight commands, which DB2 IFCIDs, and how much data a particular user can access.

Introduction to Security

Multi-level Unicenter CA-Insight security parameters provide a flexible and easy to use way to set up and enforce access.

Unicenter CA-Insight monitors the activity of a DB2 subsystem by gathering performance information from DB2 control blocks and by collecting data from DB2 internal trace records provided by the IFI (Instrumentation Facility Interface). There are no facilities to browse or update data in DB2 tables; however, Unicenter CA-Insight users can view data from dynamic SQL statements that add or update DB2 data.

Options

You can use the security facilities to restrict the reporting of those IFCIDs whose overhead might have an undue impact on performance. In addition, you can use them to restrict who can start, stop, reset, freeze, or resume requests. See the Unicenter CA-Insight User Guide for a listing of relative performance impact of the various performance trace classes.

Use the Unicenter CA-Insight security facility to control access to the product as well as specific menus.

Security 6–1 Controls

Security’s Role

The role of security for Unicenter CA-Insight usage is shown in the following illustration:

The components are, from left to right:

■ User interface (TSO, Batch, and VTAM)

■ External security package (RACF, CA-ACF2, CA-Top Secret)

■ Unicenter CA-Insight security file

■ Unicenter CA-Insight functions

Controls

The following section describes the facilities used to control data collector and user interface usage.

Data Collector

You can use a combination of the facilities listed in the following to control data collector usage.

■ Security parameters: SECURITY=[YES | NO] RESTRICTED-IFCIDS=list-of-ifcids FORBIDDEN-IFCIDS=list-of-ifcids SECURITY-EXIT=NSIGHTEX MAX-TRACE-RECORDS=nnnn MAX-REQUEST-TIME=nnnn

■ SECURITY DD file

6–2 System Guide Flexibility

Both of these facilities are active after the basic installation has been completed. See the “Operation and Customization” chapter for more information about these facilities.

By using the data collector security input parameter of SECURITY=NO, you disable all security components described in this chapter. The CONSOLE and NOTIFY IQL statements cannot be used unless SECURITY=YES and the required feature is enabled for the user starting the requests.

User Interface

You can use a combination of the facilities listed in the following to control user interface usage. User Interface Input Parameters: SECURITY-FILE=‘Security data set name’ SECURITY-EXIT=NSIGHTEX LOGON-CHECK=[YES | NO] Data Collector SECURITY DD file

See the “Operation and Customization” chapter for more information about these facilities.

In General

The remainder of this chapter describes procedures and facilities active when the SECURITY=YES parameter has been entered.

Flexibility

Unicenter CA-Insight provides a number of user profiles in the Security file that specify different sets of security options. You can then assign a profile to:

■ A single user ID

■ A single group ID (RACF and CA-Top Secret only)

■ A range of user IDs

■ A range of group IDs (RACF and CA-Top Secret only)

In addition, you can code user exit routines to provide for a unique requirement or as a bridge to a security package.

Security 6–3 Operation Overview

Operation Overview

The following section describes security operations.

Security Control

The following describes the process of acquiring the User ID, Security ID, and the Menu name in the TSO environment.

User ID

The User ID is validated when the user logs on to TSO. The TSO User ID is found through control blocks by the NSIGHTEX User Exit.

Security ID

Note: This section applies to RACF and CA-Top Secret Release 4.3 and above users only.

The Security ID is an additional ID that the NSIGHTEX User Exit sets to facilitate the elimination of specific User IDs from the Security file. At this time, only RACF can use Security ID without changing NSIGHTEX.

NSIGHTEX first sets the Security ID from the ACEE GROUP field. In RACF, ACEE GROUP contains the RACF default group.

Note: In CA-ACF2 or CA-Top Secret 4.2 and earlier, the field is unpredictable and the exit will set that ID to “NOGROUP.”

The NSIGHTEX User Exit will check to see if ACEE connect groups are specified. If so, the connect groups are searched for the first occurrence of a connect group starting with “INS.” The Security ID is set to the value of this connect group. If you want to use Connect Group names other than those that start with “INS,” modify the NSIGHTEX security exit. For details, see the “NSIGHTEX User Exit” appendix.

Default Menu

The NSIGHTEX User Exit also sets a default menu. This menu name will be ignored if a menu data set is specified in the user interface SECURITY-FILE parameter, described in the “Operation and Customization” chapter.

6–4 System Guide Operation Overview

The default menu is SYSTEM, except for the RACF user who has an “INS” connect group. The following shows which menu is used depending on what the first four letters of the connect group are:

■ INSS—Uses the SYSTEM menu

■ INSD—Uses the DBA menu

■ INSA—Uses the APPDEVL menu

■ INSO—Uses the OPERATOR menu

■ INSU—Uses the AUDITOR menu

If the security data set is specified, the menu is retrieved from the Security file.

Typically at RACF and CA-Top Secret sites, this ID portion of the Security file uses primarily TYPE=GROUP. This minimizes the maintenance of the Security file.

At CA-ACF2 sites, Security ID and TYPE=GROUP cannot be used without modification of the NSIGHTEX User Exit by the customer. TYPE=USER specifications will use theuser’s ID to identify the profile. You can minimize the maintenance in this environment if a prefix of the User ID denotes a logical group, i.e., DBA-DBA9999 range specification.

Profile

If a profile is not defined for the user, or the profile is defined but has no MENU specification, the user access to the user interface is denied.

Security Exit Checking

The following describes NSIGHTEX routine and where data collector and user interface occurs.

Data Collector

Before a data collector command is processed and the user security is checked, the NSIGHTEX routine is called. The routine indicates whether to explicitly allow access, explicitly disallow it, or to have the data collector decide based on the user’s security profile. If the data collector command is START, the NSIGHTEX routine is also called after the request syntax is checked. This routine also indicates whether to explicitly allow access, explicitly disallow it, or to have the data collector decide based on the user’s security profile.

Security 6–5 Security File Overview

User Interface

The NSIGHTEX User Exit is called at the start of the user interface session and at the termination of that session.

Refreshing SECURITY Parameters

The SECURITY command can be issued from the Unicenter CA-Insight user interface to let a user with the proper security profile request rebuilding the internal security table from information contained in the Security file. Specify the data set name of a new or updated security file on the panel displayed when you enter the SECURITY command. The security file is then dynamically allocated by the data collector, processed to build a new internal security table, and deallocated when the file is closed. Any user connecting Unicenter CA-Insight to that data collector after the security table has been rebuilt is then bound by the parameters of the new table.

Any user already connected to a data collector will retain the security information acquired when the user first connected. To force a re-connection without exiting the user interface, enter PICK as a command and press PF3.

Security File Overview

The following section provides an overview of the security file.

Components

The Unicenter CA-Insight installation process creates a Security file. The purpose of this file is to define profiles and assign one of the profiles to a user.

Note: The structure of the Security file includes a DB2 Subsystem ID (or wild-card character), so you only need to maintain one Security file that all Users and data collectors can use.

Profiles contains elements that permit access to Unicenter CA-Insight facilities such as EXPLAIN, DB2 messages and commands, and the Unicenter CA-Insight default menu. Profiles also contain elements specifying request management attributes such as the maximum trace records allowed, maximum request time, Restricted-IFCID or Forbidden-IFCID access, and the START, DISPLAY, and SHOW privileges.

6–6 System Guide Security File Overview

The following shows the two major components of the security file, the User ID Table and User Profiles.

The initial security file assigns all users (User IDs A through Z99999) to the SYSADM profile for any subsystem to be monitored.

Starter Member

As part of the Unicenter CA-Insight installation process, a starter Security file (SECURITY) is created in the SOURCE library. This file allows blanket access to Unicenter CA-Insight. Explanations and customization of this Security file can be found in the sections, The Security File: User ID Table and The Security File: User Profiles.

This file can be customized through the ISPF Editor. ======� * CA-INSIGHT - SECURITY FILE* * IDS=((P1,P2,P3,P4),...,(P1,P2,P3,P4))* * P1 TYPE=GROUP OR TYPE=USER * P2 USERID (TYPE=USER) * OR RANGE OF USERIDS, FOR EXAMPLE A-Z9999999 * RACF OR CA-TOP SECRET SECURITY-ID (TYPE=GROUP) * OR RANGE OF SECURITY-IDS, FOR EXAMPLE A-Z9999999 * P3 SUBSYSTEM, SPECIFIES A SPECIFIC SUBSYSTEM * * , SPECIFIES ANY SUBSYSTEM * P4 PROFILE-NAME * ======

Security 6–7 Security File Overview

IDS=(* (TYPE=GROUP,INSS-INSS9999,*,SYSADM), /*RACF FOR RACF WITH “INS” * (TYPE=GROUP,INSS-INSS9999,*,SYSADM), /* FOR RACF OR CA-TOP SECRET * (TYPE=GROUP,INSD-INSD9999,*,DBA), /* WITH "INS" * (TYPE=GROUP,INSO-INSO9999,*,OPERATOR), /* CONNECT GROUPS * (TYPE=GROUP,INSA-INSA9999,*,APPLS), /* " * (TYPE=GROUP,INSU-INSU9999,*,AUDITOR), /* " (TYPE=USER,$-Z9999999,*,SYSADM) /*EVERYONE IS SYSADM ) * ======* PROFILE=((P1,...,PN),...,(P1,...,PN)) * ======* ------* PROFILE(NOACCESS) - NOT ALLOWED ANY DATA COLLECTOR FUNCTIONS * ------PROFILES=( (NOACCESS, CONNECT=NO ), * ------* PROFILE(SYSADM) - ALLOWED SPECIFIED FUNCTIONS * ------(SYSADM, CONNECT=YES, /* CAN CONNECT AUTHID=‘‘, /* NO FOCUS/START QUALIFICATION PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=YES, /* YES/NO OBID-REFRESH=YES, /* YES/NO EXPLAIN=TSO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=ALL, /* NO/USER/USER-STARTUP/ALL SHOW=ALL, /* NO/USER/USER-STARTUP/ALL ALTER=ALL, /* NO/USER/USER-STARTUP/ALL START=ALL, /* NO/LIMITED/RESTRICTED/ALL START-MULTIPLE=YES /* YES/NO WTO-NOTIFY=YES, /* YES/NO MAX-TRACE-RECORDS=UNLIMITED, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=UNLIMITED, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=USER, /* USER/DC MENU=SYSTEM, /* INITIAL USER MENU PANEL-CHARACTER=‘S’, /* PANEL SUFFIX START-HISTORY-FILTER=YES, /* YES/NO START-WILDCARD=YES, /* YES/NO PROBE-SQLTRACE=YES, /* ALL-MENUS=YES, * LIST-BROWSE-EDIT=YES, /* PLAN-AUTH-ONLY=NO, /* SYSTEM-CONDITION-MONITOR=YES, START-MENU-GROUP=YES, MVS-COMMANDS=YES, MVS-DISPLAY=YES, X247CTHD=YES, X247SEC=YES, X247=YES, HISTORY-SWITCH=YES, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=YES, GROUP-VALIDATION=UNLIMITED /*NO/YES/UNLIMITED ),

6–8 System Guide Security File Overview

* ------* PROFILE(OPERATOR) * ------(OPERATOR, CONNECT=YES, /* CAN CONNECT AUTHID=‘‘, /* NO FOCUS/START QUALIFICATION PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=NO, /* YES/NO OBID-REFRESH=YES, /* YES/NO EXPLAIN=NO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=USER-STARTUP, /* NO/USER/USER-STARTUP/ALL SHOW=ALL, /* NO/USER/USER-STARTUP/ALL ALTER=ALL, /* NO/USER/USER-STARTUP/ALL START=NO, /* NO/LIMITED/RESTRICTED/ALL WTO-NOTIFY=YES, /* YES/NO MAX-TRACE-RECORDS=1, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=1, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=USER, /* USER/DC MENU=OPERATOR, /* INITIAL USER MENU PANEL-CHARACTER=‘O’, /* PANEL SUFFIX START-HISTORY-FILTER=YES, /* YES/NO START-WILDCARD=NO, /* YES/NO PROBE-DETAIL=NO, /* PLAN-AUTH-ONLY=YES, /* ALL-MENUS=YES, /* LIST-BROWSE-EDIT=YES, /* SYSTEM-CONDITION-MONITOR=YES, START-MENU-GROUP=NO, MVS-COMMANDS=YES, MVS-DISPLAY=YES, X247CTHD=NO, X247SEC=NO, X247=NO, HISTORY-SWITCH=YES, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=NO, GROUP-VALIDATION=NO /*NO/YES/UNLIMITED ),

Security 6–9 Security File Overview

* ------* PROFILE(DBA) * ------(DBA, CONNECT=YES, /* CAN CONNECT AUTHID=‘‘, /* NO FOCUS/START QUALIFICATION PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=NO, /* YES/NO OBID-REFRESH=YES, /* YES/NO EXPLAIN=TSO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=USER-STARTUP, /* NO/USER/USER-STARTUP/ALL SHOW=USER-STARTUP, /* NO/USER/USER-STARTUP/ALL ALTER=USER, /* NO/USER/USER-STARTUP/ALL START=RESTRICTED, /* NO/LIMITED/RESTRICTED/ALL WTO-NOTIFY=YES, /* YES/NO MAX-TRACE-RECORDS=9999, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=30, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=USER, /* USER/DC MENU=DBA, /* INITIAL USER MENU PANEL-CHARACTER=‘D’, /* PANEL SUFFIX START-HISTORY-FILTER=NO, /* YES/NO START-WILDCARD=NO, /* YES/NO PROBE-DETAIL=NO, /* PLAN-AUTH-ONLY=NO, /* ALL-MENUS=YES, /* LIST-BROWSE-EDIT=YES, /* SYSTEM-CONDITION-MONITOR=YES, START-MENU-GROUP=YES, MVS-COMMANDS=YES, MVS-DISPLAY=YES, X247CTHD=NO, X247SEC=NO, X247=NO, HISTORY-SWITCH=YES, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=YES, GROUP-VALIDATION=UNLIMITED /*NO/YES/UNLIMITED ),

6–10 System Guide Security File Overview

• * ------* PROFILE(APPLS) * ------(APPLS, CONNECT=YES, /* CAN CONNECT AUTHID=‘*3’, /* ENFORCE 1ST 3 CHARS OF USERS AUTH ID PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=NO, /* YES/NO OBID-REFRESH=NO, /* YES/NO EXPLAIN=TSO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=USER-STARTUP, /* NO/USER/USER-STARTUP/ALL SHOW=USER, /* NO/USER/USER-STARTUP/ALL ALTER=USER, /* NO/USER/USER-STARTUP/ALL START=LIST=APPLS, /* NO/LIMITED/RESTRICTED/ALL WTO-NOTIFY=NO, /* YES/NO MAX-TRACE-RECORDS=999, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=15, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=DC, /* USER/DC MENU=APPLDEVL, /* INITIAL USER MENU PANEL-CHARACTER=‘A’, /* PANEL SUFFIX START-HISTORY-FILTER=NO, /* YES/NO START-WILDCARD=NO, /* YES/NO PROBE-DETAIL=NO, /* PLAN-AUTH-ONLY=YES, /* ALL-MENUS=NO, /* LIST-BROWSE-EDIT=NO, /* SYSTEM-CONDITION-MONITOR=NO, START-MENU-GROUP=NO, MVS-COMMANDS=NO, MVS-DISPLAY=NO, X247CTHD=NO, X247SEC=NO, X247=NO, HISTORY-SWITCH=NO, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=NO, GROUP-VALIDATION=YES /* NO/YES/UNLIMITED ),

Security 6–11 Security File Overview

* ------* PROFILE(AUDITOR) * ------(AUDITOR, CONNECT=YES, /* CAN CONNECT AUTHID=‘ ‘, /* NO FOCUS/START QUALIFICATION PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=NO, /* YES/NO OBID-REFRESH=NO, /* YES/NO EXPLAIN=TSO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=USER, /* NO/USER/USER-STARTUP/ALL NON-DISPLAY=NOTZPARMS /* REQUEST LIST NAME SHOW=USER, /* NO/USER/USER-STARTUP/ALL ALTER=USER, /* NO/USER/USER-STARTUP/ALL START=LIMITED, /* NO/LIMITED/RESTRICTED/ALL WTO-NOTIFY=NO, /* YES/NO MAX-TRACE-RECORDS=999, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=15, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=DC, /* USER/DC REQUEST-LIBRARY=DC, /* USER/DC MENU=AUDITOR, /* INITIAL USER MENU PANEL-CHARACTER=‘U’, /* PANEL SUFFIX START-HISTORY-FILTER=NO,/* YES/NO START-WILDCARD=NO, /* YES/NO PROBE-DETAIL=NO /* PLAN-AUTH-ONLY=YES, /* ALL-MENUS=NO, /* LIST-BROWSE-EDIT=NO, /* SYSTEM-CONDITION-MONITOR=NO, START-MENU-GROUP=NO, MVS-COMMANDS=NO, MVS-DISPLAY=NO, X247CTHD=NO, X247SEC=NO, X247=NO, HISTORY-SWITCH=NO, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=NO, GROUP-VALIDATION=NO. /* NO/YES/UNLIMITED ) )

6–12 System Guide Security File Overview

*======* REQUEST NAMES ARE USED BY TWO PROFILE OPTIONS * * START=LIST=XXXXX USER CAN ONLY START ITEMS IN NAMED LIST * NON-DISPLAY=XXXXX USER CAN’T DISPLAY ITEMS IN NAMED LIST *======REQUESTS=( (NOTZPARMS, DSNZPARMS), /* DSNZPARMS NON-DISPLAY (APPLS, THRDTRAC,PLANSUM,SCANSUM, /* THE PROBE SQLSUM,LOCKSUM,APPLIO, /* WITH NO DETAIL APPLPROF, /* MINI-PROBE ACCSHIST), /* MINI-EXPLAIN (NOPROBE, APPLPROF, /* MINI-PROBE ACCSHIST) /* MINI-EXPLAIN ) *======* USER GROUPS ARE USED IF THE GROUP-VALIDATION=YES OR =UNLIMITED *======*USER-GROUPS=( * (‘*4’, /*GROUP NAME = 4 CHARACTERS OF USERID * ‘*’) /* ALL USER BELONG * , * (DBAS, /*GROUP OF DBAS * ‘DBA*’) /* WITH DBA AS PREFIX OF USERID * , * (SGOD, /*SPECIAL GROUP OF DEVELOPERS * TOM,DICK,MARY) /* WITH DBA AS PREFIX OF USERID * ) ;

User ID Table

The User ID table in the Security file contains all user-to-profile assignments.

Security 6–13 Security File Overview

ID List Syntax

The syntax of the ID list is: IDS=((TYPE=type,idname,ssid,profile)... (TYPE=type,idname,ssid,profile))

Where the parameters are substituted with these values:

■ TYPE=[USER|GROUP] is the ID type for this sublist. USER indicates that the next field (idname) matches using the User ID. Specify GROUP to match the Security ID that NSIGHTEX can set for RACF and CA-Top Secret sites or custom usage. NSIGHTEX is coded to check for connect groups that begin with the letters “INS.”

■ idname is the ID or range of IDs to be assigned a profile in this sub-list. An example of a range would be A-Z9999999.

■ ssid is the SSID of the DB2 subsystem used by the data collector on which the listed users or groups will be operating under the assigned profile. A value of * indicates all SSIDs.

■ profile is the Unicenter CA-Insight user profile name (see User Profiles for more information).

Each sub-list must be enclosed within parentheses.

ID List Example

The following is an example of the Security File IDs list: IDS=( (TYPE=USER,CHARLEY,*,SYSADM), (TYPE=GROUP,INSD-INSD9999,*,DBA), (TYPE=GROUP,INSO-INSO9999,*,OPERATOR), (TYPE=GROUP,INSA-INSA9999,DSN,APPLS), (TYPE=GROUP,INSSYS,*,SYSADM), (TYPE=GROUP,INSU-INSU9999,*,AUDITOR), (TYPE=GROUP,EXPLORE,*,OPERATOR), (TYPE=USER,A-A9999999,*,NOACCESS) )

To code the IDs list to include all users that do not have a specific entry, follow this example: IDS=( (TYPE=USER,XYZ789,A,DBA), (TYPE=USER,A-E999999,*,NOACCESS), )

6–14 System Guide Security File Overview

How to Access the Security File

The security file is accessed by the data collector and the online user interfaces (TSO and/or VTAM). The algorithm differs slightly between the components: the data collector uses the subsystem ID, but the online user interface does not.

The data collector reads the security file and builds an internal table of those ID entries that specify a Subsystem ID of * (all) and the specified Subsystem ID being monitored. Other Subsystem IDs in the file are ignored.

The search for a profile is done based on the User ID (or Group ID, if applicable).

Online User Interface

When the online user interface reads the menu data set, it retains all ID entries.

The search for a profile is done based on the User ID (or Group ID, if applicable). The user interface finds the MENU parameter in the profile to display when the user invokes Unicenter CA-Insight.

User Profiles

This section discusses the structure and contents of the Unicenter CA-Insight User Profiles which follow the User ID Table in the Security file.

Security 6–15 Security File Overview

Sample User Profile

Shown here is a sample User Profile from the Security File: ------* PROFILE(SYSADM) - ALLOWED SPECIFIED FUNCTIONS * ------(SYSADM, CONNECT=YES, /* CAN CONNECT AUTHID=‘‘, /* NO FOCUS/START QUALIFICATION PLAN=‘‘, /* ENFORCEMENT SECURITY-REFRESH=YES, /* YES/NO OBID-REFRESH=YES, /* YES/NO EXPLAIN=TSO, /* TSO/DC/ALL/NO HISTORY=YES, /* YES/NO VIEW HISTORY DB2-MESSAGES=YES, /* YES/NO VIEW DB2 MESSAGES DB2-COMMANDS=TSO, /* TSO/DC/ALL/NO INSIGHT-COMMANDS=YES, /* YES/NO ISSUE INSIGHT COMMANDS DISPLAY=ALL, /* NO/USER/USER-STARTUP/ALL SHOW=ALL, /* NO/USER/USER-STARTUP/ALL ALTER=ALL, /* NO/USER/USER-STARTUP/ALL START=ALL, /* NO/LIMITED/RESTRICTED/ALL START-MULTIPLE=YES /* YES/NO WTO-NOTIFY=YES, /* YES/NO MAX-TRACE-RECORDS=UNLIMITED, /* DC/UNLIMITED/NNNN MAX-REQUEST-TIME=UNLIMITED, /* DC/UNLIMITED/NNNN REQUEST-LIBRARY=USER, /* USER/DC MENU=SYSTEM, /* INITIAL USER MENU PANEL-CHARACTER=‘S’, /* PANEL SUFFIX START-HISTORY-FILTER=YES, /* YES/NO START-WILDCARD=YES, /* YES/NO PROBE-SQLTRACE=YES, /* ALL-MENUS=YES, /* LIST-BROWSE-EDIT=YES, /* PLAN-AUTH-ONLY=NO, /* SYSTEM-CONDITION-MONITOR=YES, START-MENU-GROUP=YES, MVS-COMMANDS=YES, MVS-DISPLAY=YES, X247CTHD=YES, X247SEC=YES, X247=YES, HISTORY-SWITCH=YES, EXCEPTION-DISPLAY=YES, EXCEPTION-DEFINITION=YES. GROUP-VALIDATION=UNLIMITED /* NO/YES/UNLIMITED ),

The format of the User Profile is: (profile name,keyword1,keyword2,...,keywordx)

A comma (,) must follow each keyword except the last one.

6–16 System Guide Security File Overview

Keywords

All of the allowable keywords that can be specified for the User Profile are described in the following. Some of the keywords have no default value. CONNECT=[YES|NO] Controls whether the user can connect to the data collector for a valid DB2 subsystem. AUTHID=[‘string’|’*’|’*n’|’ ‘] Controls the focus of the request display to allow viewing data for a particular Authorization ID. If you specify a non-blank value for this field, you should also specify REQUEST-LIBRARY=DC (described in the following). The reason for this is that users could bypass Auth ID and plan enforcement by editing requests in their own request library and by removing FOCUS-KEY=YES from the request.

■ ‘string’ enforces viewing for Authorization ID ‘string’. An underscore character (_) can be used as a wildcard.

■ ‘*’ enforces viewing only data for the user’s own ID.

■ ‘*n’ enforces viewing data for Authorization IDs containing the first n characters of the User’s ID.

■ ‘ ‘ (blank) means that this parameter is not enforced. PLAN=[‘string’|’*’|’*n’|’ ‘] Controls the focus of the request display to allow viewing data for a particular Plan name. If you specify a non-blank value for this field, you should also specify REQUEST-LIBRARY=DC (described in the following). See the previous explanation for AUTHID for when REQUEST-LIBRARY=DC should not be specified.

■ ‘string’ enforces viewing for Plan name ‘string’. An underscore character (_) can be used as a wildcard.

■ ‘*’ enforces viewing only data for the Plan corresponding to the user’s own ID.

■ ‘*n’ enforces viewing data for the Plan containing the first n characters of the User’s ID.

■ ‘ ‘ (blank) means that this parameter is not enforced. SECURITY-REFRESH=[YES|NO] Indicates whether Unicenter CA-Insight Security updating is checked after editing the Security file.

Security 6–17 Security File Overview

OBID-REFRESH=[YES|NO] Indicates whether the OBID translation table for any data collector is refreshed. EXPLAIN=[TSO|DC|NO|ALL] Controls access to Unicenter CA-Insight’s EXPLAIN facility. Be sure to read Authorization Issues for EXPLAIN and DB2 Commands before selecting a value for this parameter.

■ TSO indicates NO if you are on the VTAM user interface; otherwise, it means the same as ALL

■ DC indicates to always use the data collector to issue the command or EXPLAIN

■ NO indicates that commands or EXPLAIN cannot be done

■ ALL indicates to issue commands or EXPLAIN through TSO if it can; otherwise it will use the data collector If the DC issues DB2 commands, it does so under the User’s ID, so that authorization is controlled by your site’s external security system. The same is true for EXPLAIN, except that the SQL ID is used instead of the User ID. In general, we do not recommend using the DC value. It will use one of the data collector user tasks and will single thread the data collector for a very short period of time for all users using EXPLAIN or DB2 commands while the task is in DB2 IDENTIFY status. This table documents whether the user or the data collector does EXPLAIN or DB2-COMMANDS based on which user interface is being used and whether the data collector (and DB2) that the user is currently running is on the same or a different MVS image.

TSO User VTAM User Interface Interface Local Data DB2-COMMA DB2-COMMA Collector NDS NDS (same MVS) or EXPLAIN Issued by or EXPLAIN Issued by NO NO ONE NO NO ONE ALL TSO ALL DC TSO TSO TSO NO ONE DC DC DC DC

6–18 System Guide Security File Overview

Remote Data Collector (on DB2-COMMA DB2-COMMA a different NDS or NDS or MVS) EXPLAIN Issued by EXPLAIN Issued by NO NO ONE NO NO ONE ALL DC ALL DC TSO DC TSO NO ONE DC DC DC DC

HISTORY=[YES|NO] Controls access to the Unicenter CA-Insight Online History facility to view recent performance history. DB2-MESSAGES=[YES|NO] Controls whether the user can view DB2 messages from within Unicenter CA-Insight. DB2-COMMANDS=[TSO|DC|NO|ALL] Controls access to Unicenter CA-Insight’s DB2 Command interface.

■ TSO indicates that if a TSO user issues a DB2 command, it will be done by the Unicenter CA-Insight user interface directly with DB2. The data collector will only be involved to provide the user’s Security Profile.

■ DC indicates that if a TSO or VTAM user issues a DB2 command, it will be done by the data collector.

■ NO indicates that a TSO or VTAM user’s attempt to issue DB2 commands will be blocked by security.

■ ALL indicates that if a TSO or VTAM user issues a DB2 command, it will be executed as follows: The DB2 command will be executed for a TSO user in the Unicenter CA-Insight user interface if the user and DB2 are on the same MVS system. The DB2 command will be executed by the data collector for a VTAM user, or if the user and DB2 are not on the same MVS system. If you use CA-Top Secret, you will need to authorize the data collector to perform a RACROUTE call to set the user authorization. Failure to do this will result in abnormal termination of the data collector. INSIGHT-COMMANDS=[YES|NO] Controls access to the INSIGHT Commands interface.

Security 6–19 Security File Overview

DISPLAY=[NO|USER|USER-STARTUP|ALL] Indicates the type of requests that the user can display.

■ NO means that the user cannot display requests.

■ USER means that the user can only display requests that they have started.

■ USER-STARTUP means that the user can display only requests they have started as well as requests started by the data collector.

■ ALL means that the user can display all requests. SHOW=[NO|USER|USER-STARTUP|ALL] Controls the user’s ability to issue the Unicenter CA-Insight SHOW command to display active requests.

■ NO means that the user cannot issue the SHOW command.

■ USER means that the user can issue the SHOW command to display only requests that they have started.

■ USER-STARTUP means that the user can issue the SHOW command only for requests they have started as well as requests started by the data collector.

■ ALL means that the user can issue the SHOW command to display all requests. ALTER=[NO|USER|USER-STARTUP|ALL] Controls the user’s ability to STOP, FREEZE, RESET, and RESUME requests that have already been STARTed. Related to the START command that follows.

■ NO means that the user cannot issue these commands.

■ USER means that the user can issue these commands only for requests that they have started.

■ USER-STARTUP means that the user can issue these commands only for requests they have started as well as requests started by the data collector.

■ ALL means that the user can issue these commands. START=[NO|RESTRICTED|LIMITED|ALL|LIST=request-name-list] Controls the user’s ability to START requests (related to the ALTER command).

■ NO means that the user cannot START any request.

■ RESTRICTED means that the user can START requests referencing IFCIDs that are not on the FORBIDDEN-IFCIDS list in the data collector initialization parameters.

6–20 System Guide Security File Overview

■ LIMITED means that the users can START requests referencing IFCIDs that are not on the RESTRICTED-IFCIDS or FORBIDDEN-IFICDS lists in the data collector initialization parameters.

■ ALL means that the user can START any request.

■ LIST=request-name-list means that the user can START only those requests specified in the request-name-list. The format of the request list is shown in The Security File: Request Lists. The START parameter specifying the LIST option using the NOPROBE request list would appear like this: START=LIST=NOPROBE START-MULTIPLE=[YES|NO]. A value of YES indicates that a user is allowed to start several occurrences on a single request or probe. The default is NO. WTO-NOTIFY=[YES|NO] Controls the user’s ability to START requests that contain a WTO or NOTIFY statement. MAX-TRACE-RECORDS=[DC|UNLIMITED|nnnn] Specifies the maximum number of DB2 trace records that a user’s request can collect. When the request reaches this limit, the request is changed from ACTIVE to FROZEN.

■ DC causes the value to be taken from the MAX-TRACE-RECORDS= parameter in the data collector’s SYSPARMS.

■ UNLIMITED causes no limit to be placed on the number of trace records. This option is equivalent to MAX-TRACE-RECORDS=0.

■ nnnn specifies the maximum number of trace records. MAX-REQUEST-TIME=[DC|UNLIMITED|nnnn] Specifies the maximum number of minutes that a request can remain active. When the request reaches this limit, the request is changed from ACTIVE to FROZEN.

■ DC causes the value to be taken from the MAX-REQUEST-TIME= parameter in the data collector’s SYSPARMS.

■ UNLIMITED causes no limit to be placed on the number of minutes. This option is equivalent to MAX-REQUEST-TIME=0.

■ nnnn specifies the maximum number of minutes.

Security 6–21 Security File Overview

REQUEST-LIBRARY=[DC|USER] Indicates whether a user can start requests from a library other than the one specified in the REQLIB parameter of the data collector initialization member.

■ DC means that the text of the request will be taken from the data collector’s request library by changing the user’s request to an INCLUDE “request-name” statement.

■ USER means that the text of the request will be taken from the request libraries of the user interface unless no REQUESTS DD name is specified. If this is the case, an “INCLUDE request-name” statement will be generated to retrieve the text from the data collector’s request library. MENU=[SYSTEM|DBA|OPERATOR|APPLDEVL|AUDITOR] Specifies the name of the Unicenter CA-Insight menu to use for this user. PANEL-CHARACTER=‘c’ Specifies a panel suffix for these user interface commands with an ‘*’ in the eighth position. See Product Commands for related information. START-HISTORY-FILTER=[YES|NO] Indicates whether a user can start requests that are History requests. START-WILDCARD=[YES|NO] Indicates whether a user can start requests using wildcard characters, as well as requests that have no qualification. Using wildcard characters means that DB2 qualified traces will not be used. PROBE-SQL-TRACE=[YES|NO] or PROBE-DETAIL=[YES|NO] Controls the starting of the detail requests of the Unicenter CA-Insight probes. As delivered, the APPLPROB probe has the detailed trace SQLTRACE, and the HPROBE probe has the detailed request HPRSTDTL. In previous releases of Unicenter CA-Insight, this parameter was called PROBE-SQL-TRACE, which can also be specified.

■ YES gives the user the option (on the Start Qualification panel) to start the detailed requests.

■ NO removes the option to start the detailed requests from the Start Qualification panel. ALL-MENUS=[YES|NO] Indicates whether to list all available menus under the Menu pull down menu. If NO is specified, only the user’s initial menu will be listed. LIST-BROWSE-EDIT=[YES|NO] Indicates whether to list the LIST command under the Tools pull down menu. This also controls access to the LIST, BROWSE, and EDIT commands.

6–22 System Guide Security File Overview

PLAN-AUTH-ONLY=[YES|NO] Controls specifications for the Start Request and Start Probe Qualification panels. If YES is specified, this means that the user will only be permitted to specify Plan and Auth ID. NO indicates that the Qualification panels will have additional fields such as Connection, Correlation, and so on SYSTEM-CONDITION-MONITOR=[YES|NO] Controls access to the System Condition Monitor (see the “Installing Optional Components” chapter for details). A value of NO means that the SCM option will not be available from the Tools pull down menu or from the Command line. START-MENU-GROUP=[YES|NO] Controls whether a user can start MENU-GROUP requests. MENU-GROUPS are described in the “Operation and Customization” chapter, YES means that the user can start the requests. This function is typically allowed only for those individuals who administer Unicenter CA-Insight. MVS-COMMANDS=[YES|NO] Controls access to the MVS console panel and the issuance of MVS commands. A value of YES indicates that the user is permitted to see the MVS console panel and issue MVS commands. A value of NO means that the Commands view bar does not show “MVS Console.” MVS-DISPLAY=[YES|NO]. A value of NO indicates a user is restricted from viewing requests with MVS data. The default is YES. X247CTHD=[YES | NO] Controls whether an individual can cancel threads. Also controls who uses the FREE page set commands. X247SEC=[YES | NO] Controls whether an individual can:

■ REPLACE the signon and connection exit routines

■ Use the AUTH command to enable/disable DB2 security

■ Use the SYSADM/SYSADM2 commands

■ Use the SYSOPR1/SYSOPR2 commands

■ Use the DEFLTID command X247=[YES | NO] Controls all other Unicenter CA-24X7 functions from the Unicenter CA-Insight online user interface. HISTORY-SWITCH=[YES|NO] Controls whether the user is authorized to issue the SWITCH command to switch on one or more history files.

Security 6–23 Security File Overview

EXCEPTION-DISPLAY=[YES|NO]. A value of YES indicates that the user is allowed to view Exceptions from the initial menu. EXCEPTION DEFINITION=[YES|NO]. A value of YES indicates that the user is allowed to view and modify Exceptions. NON-DISPLAY=request-name-list. Specifies a list of requests that a user is not allowed to display. The format of the request-name-list is shown under The Security File: Request Lists. GROUP-VALIDATION=[YES|NO|UNLIMITED] Controls whether the user starting a request can allow other users to display, alter or stop that request.

■ YES—Users can, if they choose, specify a group they belong to, thereby allowing the other members of that group to display, alter or stop the request.

■ NO—Users cannot grant any group the capability to display, alter or stop the request.

■ UNLIMITED—Users can, if they choose, specify any valid group, thereby allowing the members of all groups to display, alter or stop the requests they start.

Request Lists

Request Lists are ways of grouping a series of requests under one name to be used the START-LIST or NON-DISPLAY keywords.

REQUESTS=( (APPLS, THRDTRAC,PLANSUM,SCANSUM, /* THE PROBE SQLSUM,LOCKSUM,APPLIO, /* WITH NO SQLTRACE APPLPROF, /* MINI-PROBE ACCSHIST), /* MINI-EXPLAIN (NOPROBE, APPLPROF, /* MINI-PROBE ACCSHIST) /* MINI-EXPLAIN )

6–24 System Guide Security File Overview

The Request List is usually the second to last section of the Security File, and has the format:

REQUESTS=( (request-list-name1, request1, request2, request3) (request-list-name2, request1, request3, request4) )

Where request-list-namen is the unique list name (APPLS and NOPROBE in the previous example) and requestn is the name of an Unicenter CA-Insight request (such as THRDTRAC, PLANSUM, SQLSUM in the previous example).

User Groups

User groups define and group users so that those starting a request can allow other members of the group to display, alter, and stop the request.

The GROUP-VALIDATION parameter controls whether users can grant this privilege only to members of groups to which they themselves belong or to members of any group. It is also used to specify that users cannot grant the privilege.

For example, if DBA users need to have the capacity to allow Application profile users to alter and stop requests started by DBA owners, the following steps would be taken. 1. Create a user group whose members include both DBA and Application profile users. 2. Define GROUP-VALIDATION=YES in the DBA owners’ profiles.

Should a DBA user want to let Application users display, alter, or stop a request, the DBA user enters the group name in the Start Qualification panel.

Another example is the following. If Application users are to be able to allow each other to display, alter or stop their requests, the following steps would be taken. 1. Create a user group whose members include all Application users. 2. Define GROUP-VALIDATION=YES in the Application users’ profile.

Security 6–25 Security File Overview

Syntax for Specifying User Groups

The syntax used to specify user groups is the following. USER-GROUPS=( (groupname1, userid1,userid2,...useridn), (groupname2, ... (groupnamen, userid1,userid2,...useridn) )

where: groupname Can be any name of no more than eight characters. Alternatively, user ids can be organized so that each begins with shared prefix, each prefix distinguishing users by some criteria. For example, the prefix of every id of all users in the accounting department might be ACCT, and all user IDs in the shipping department might be prefixed by SHPG. When this is so, a groupname can be no more than an asterisk and the number of characters in the prefix. The asterisk and number must appear within single quotes. For example, ‘*4’ instructs INSIGHT to regard the first four characters of every user ID as a group. There would be an ACCT and a SHPG group. Naming conventions allow a prefix of one to seven characters. userid Can be any valid user id. Alternatively, the * wildcard can be specified by itself to indicate all users IDs or, when user IDs are grouped by a shared prefix, as a suffix. For example, ‘*’ or ‘ACCT*’. The asterisk, whether alone or with other characters, must appear within single quote.

Examples of Specifying User Groups

In one organization, a user group might serve to associate the three individuals in the human resources department with the letters HR assigned as the groupname. USER-GROUPS=( (HR, TOM,JANE,HARRY) )

In another, each user id for a given department begins with the same three letter prefix, EDP for the data processing department and ACG for the accounting department. USER-GROUPS=( (EDP, ‘EDP*’), (ACG, ‘ACG*) )

6–26 System Guide Initialization Overview

Finally, the user can work in an organization in which all user IDs are grouped according to a prefix which denotes some distinguishing criteria, a department, an office location, and so on denoted by a two-character prefix assigned to all user IDs. USER-GROUPS=( (‘*2’, ‘*’) )

In this case, Unicenter CA-Insight recognizes as many user groups as there are unique two-character prefixes and assigns all user ids to their corresponding group.

Security File Validation

When you use the Unicenter CA-Insight Security File, the contents must be syntactically correct for the data collector or user interface to initialize (see Security User ID for a related discussion).

To test changes to the Security File (as well as to the user interface parameters), execute the Unicenter CA-Insight CLIST with the addition of DBGP(D). If using the ISPF command facility, enter: %NSIGHT DBGP(D)

From the ISPF command line enter: TSO %NSIGHT DBGP(D)

If the Security File and IDUIPRMS are correct, you will see the appropriate Unicenter CA-Insight Menu. Press PF3 to show the user interface’s DBGPRINT file in browse-mode.

If a syntax error is detected, you will be shown the user interface’s DBGPRINT file in browse-mode with the errors noted therein.

Initialization Overview

The following section describes the initialization process.

Data Collector Input Parameters

The data collector security facility is initiated during the data collector startup by reading the initialization parameters file (IDDCPRMS), loading the optional security exit routine, and reading the security file (if one has been specified). The data collector initialization parameters define the global security parameters.

Security 6–27 Authorization Issues for EXPLAIN and DB2 Commands

Security File

The Security File allows access to Unicenter CA-Insight on a user-by-user basis and enables you to set individual user access ‘profiles’. These user-specific security parameters are specified in the SECURITY DD file. The SECURITY file is read into an internal table at startup. Be sure to specify FREE=CLOSE on this DD statement to assist subsequent modifications.

Security User ID

During each user interface initialization, the user interface initialization parameters member (IDUIPRMS) is read. The NSIGHTEX User Exit routine retrieves the User ID and assigns the security ID. The security ID is then available for passing to the data collector with each Unicenter CA-Insight command. The NSIGHTEX routine is provided as a member in the LOAD library and should be reviewed and modified to meet your requirements. See the “NSIGHTEX User Exit” appendix for details.

Authorization Issues for EXPLAIN and DB2 Commands

The goal of EXPLAIN and DB2 commands is to execute the function using the user’s primary and secondary authorization IDs. Part of the responsibility for this authorization to function correctly is under the control of the user. You need to be aware of the constraints that your system can have that affect Unicenter CA-Insight’s ability to get the correct authorizations.

Be aware that if you intend to use the EXPLAIN-AUTHID= SYSPARM (see the “Operation and Customization” chapter for a complete description) to allow all users to use the same plan table when EXPLAINing, you must specify EXPLAIN=DC in the Security file.

Note: If an SQLID is entered on the User Profile panel or EXPLAIN panel, the EXPLAIN function will issue a -SET CURRENT SQLID equal to the entered ID before issuing an EXPLAIN.

How Authorizations are Supported

Unicenter CA-Insight supports the execution of EXPLAIN and DB2 commands differently, depending upon which user interface is being used:

6–28 System Guide Authorization Issues for EXPLAIN and DB2 Commands

TSO User Interface (non-RAF)

TSO Users can directly execute these functions with the same authorization that would be used if the function were done with SPUFI. These TSO functions can only occur if the TSO user is on the same MVS as DB2, as determined by the Unicenter CA-Insight TSO user to Unicenter CA-Insight data collector being a PC Owner (not RAF) connection.

VTAM User Interface and TSO User Interface (RAF)

VTAM user interface and TSO user interface users connected throughRAF can execute the functions but only through the data collector acting as a server. In this mode, authorization can be different based on your external security package and your DSN3@ATH routine: eTrust CA-ACF2

The correct authorization will be used if the eTrust CA-ACF2 distributed DSN3@ATH routine is used. This routine uses the AIDLPRIM field passed to it as the primary authorization and builds the secondary authorization from the primary.

Many eTrust CA-ACF2 sites have altered DSN3@ATH to ignore AIDLPRIM, or they build the secondary authorization based on the data collector’s address space. Authorization will not be correct for these sites. eTrust CA-Top Secret

The correct authorization will be used if the TSS distributed DSN3@ATH routine is used. This routine uses the AIDLPRIM field passed to it as the primary authorization and builds the secondary authorization from the ACEE attached to the data collector.

For eTrust CA-Top Secret, the data collector builds the ACEE attached to the data collector according to the user ID. To accomplish this, the data collector must be authorized to eTrust CA-Top Secret to execute a RACROUTE CREATE.

Expect eTrust CA-Top Secret to abend the data collector if RACROUTE permission is not set for the data collector.

Security 6–29 Authorization Issues for EXPLAIN and DB2 Commands

RACF

The correct authorization will be used if the DB2 distributed DSN3@ATH routine is used. This routine uses the AIDLPRIM field passed to it as the primary authorization and builds the secondary authorization from the ACEE attached to the data collector.

For RACF, the data collector builds the ACEE attached to the data collector according to the User ID. No additional setup actions are required.

None

The data collector will detect that security is not active and will not use RACROUTE logic. The data collector is then at the mercy of the user’s DSN3@ATH routine, but it probably is hard coded and will work.

6–30 System Guide Chapter 7 Online History

This chapter provides you with detailed information about the installation and customization of the Unicenter CA-Insight Online History component. The specifics of Online History activation, as well as allocations and operational considerations, are also included.

The Unicenter CA-Insight Online History component is used to store DB2 subsystem Interval Statistics and Thread Accounting data. The goal of this component is to provide a high-speed, continually available facility for the storage and online access of recent-past DB2 performance data.

You must activate the Online History component if your data center wants to store, access, and create any of the following:

■ Online access to DB2 Interval Statistics (Unicenter CA-Insight format) in the Statistics History component

■ Online access to Thread Accounting records (Unicenter CA-Insight format) in the Thread History component

■ SMF-format Interval Statistics (SMF 100 Type 0 and 1) records dumped from Online History

■ SMF-format Thread Accounting (SMF 101) records dumped from Online History

■ Detailed and summarized Interval Statistics and Thread Accounting data archived in DB2 History tables

Online History Data Sets

Unicenter CA-Insight Online History consists of two pairs of data sets used to store data collected by the data collector plus a control data set that records the sequence of dumped history. Each data collector has its own set of these data sets.

Online History 7–1 Online History Data Sets

Each pair consists of dual VSAM KSDS data sets that contain the most recent DB2 SMF data collected and stored by the data collector. The data collector accesses these data sets to satisfy IQL requests for DB2 interval statistics and thread accounting history.

Each Unicenter CA-Insight online history pair is actually an A/B set of data sets that wrap when full. When one data set in a pair becomes full, the data collector switches the storing of data to the other data set of the pair. Data on the first data set remains available for retrieval until the second data set becomes full and the data collector starts writing over the first data set. Additionally, you can customize Unicenter CA-Insight to automatically dump Online History when an A or B data set becomes full and a file switch occurs or dump Online History at a specific time.

Data Types Stored

The Online History data sets are used to store several types of data. Each A/B pair holds specific DB2 SMF data. The following table illustrates the data sets used in the Online History component:

Type of DB2 Data Record Type Data Set Pair Qualifiers DB2 System Services SMF 100 type 0 HSTSTATA/B statistics DB2 Database Services SMF 100 type 1 HSTSTATA/B statistics DB2 Thread Accounting SMF 101 HSTACCTA/B data Online History control N/A HSTPARMS records

7–2 System Guide Controlling Online History

Online Interval Statistics History

The Unicenter CA-Insight Online History Interval Statistics data set pair is used to store the most recent DB2 subsystem statistics intervals. Two records are actually collected for each interval; the SMF 100 type 0 and SMF 100 type 1 records. You can play back these intervals online using the Unicenter CA-Insight Statistics History component.

An interval record contains statistics that are retrieved on a user-defined time frame; the Unicenter CA-Insight default is 30 minutes. Therefore, the number of interval records collected relates to the time frame you select and not to DB2 subsystem activity. Note that even if there is little or no thread activity occurring within the DB2 subsystem, the data collector stores a delta statistics interval at the specified time frame.

Online Thread Accounting History

The Unicenter CA-Insight Online Thread Accounting History data set pair is used to store the most recent thread accounting records reflecting the most recent application and utility activity in the DB2 subsystem. The SMF 101 accounting record is collected on this data set pair. You can play back these thread accounting records online using the Unicenter CA-Insight Thread History component.

A Thread Accounting record contains performance statistics for a single DB2 thread execution or a set of CICS reusable thread executions. The number of thread accounting records written to Online History corresponds to DB2 subsystem activity.

Controlling Online History

When you installed Unicenter CA-Insight using the post install process, you performed steps to define and initialize the Online History and control data sets and to activate the collection of history data. The activation of Online History is controlled by the four data collector SYSPARM parameters that follow.

Online History 7–3 Controlling Online History

Activating Online History Collection

You enable and disable the collection of Online History using the HISTORY parameter as follows: YES Enables the collection of Online History NO Disables the collection of Online History

Activating Online Interval Statistics Collection

You enable and disable the collection of Online Interval Statistics History using the HISTORY-STATS-TIME parameter as follows: nn Enables the collection of Online Interval Statistics History where nn is the time frame, in minutes, at which the delta statistics are calculated and written. For example, HISTORY-STATS=30 would write an interval statistics record every 30 minutes. 0 Disables the collection of Online Interval Statistics History

Activating Online Thread Accounting Collection

You enable and disable the collection of Online Thread Accounting History using the HISTORY-ACCT parameter as follows: YES Enables the collection of Online Thread Accounting History NO Disables the collection of Online Thread Accounting History FILTER Enables the collection of Online Thread Accounting History through the use of one or more IQL filter requests (see Online History Data Set Size - Accounting for more information.)

7–4 System Guide Online History Data Set Size - Introduction

Collection of Online Child Threads

You enable or disable the collection of online child thread CPU Parallelism accounting records using the HIST-CPUPARA-CHILD parameter as follows: YES Enables the collection of child accounting history. NO Disables the collection of child accounting records.

Online History Data Set Size - Introduction

To optimize storage usage and performance, you might need to adjust the default allocations and/or the data collection filters for the Online History data sets according to the following factors:

■ The amount of DB2 activity indicates a heavy workload will result in the collection of greater amounts of data and thereby require more DASD.

■ The type of thread accounting history you choose to collect indicates whether you want to collect every thread accounting record or filter those records collected. For example, by connection type, elapsed time, number of I/Os, and so on) will determine the amount of space allocated to the Online Thread Accounting History data sets. The more data you choose to collect, the more space you will need. See Online History Data Set Size - Accounting for more information.

■ The amount of history data you wish to maintain online indicates how far back in time you want to access data online will determine how much space you are required to allocate to the Online History data sets.

How Online History Files Are Allocated

The Online History VSAM files are allocated during the post install process. A sample JCL member for allocating the VSAM files is created in db2ssidVSAM in the SOURCE library. This job defines both the size of the Online History files and the maximum sizes of the records written into those files.

Online History 7–5 Online History Data Set Size - Introduction

db2ssidVSAM defines two pairs of files. The space allocations discussed in this section are for a single data set. Each System Statistics pair is defined with the same number of cylinders, as is each Accounting pair. Since one of the pair is always viewable while the other is being written to, the amount of Online History viewable data varies from the size of one data set to the size of both data sets.

Allocating the Online History data sets too large wastes space and can increase the amount of time required to find a record. Allocating the Online History data sets too small means that some data might not be there when you need it. Allocating a maximum record length too long will waste buffer space in the data collector. Allocating a maximum record length too short can result in truncation of data.

If the files are defined incorrectly, new files can be reallocated and the data REPRO’d with IDCAMS.

What Device Type Are You Using?

The type of device on which the files reside complicates space calculations:

Device Type Track Calculation VSAM Cylinder Calculation 3380 5 8K control intervals per track 75 8K control intervals per cylinder 3390 6 8K control intervals per track 90 8K control intervals per cylinder

Determining Data Set Sizes

You can use the following formula to determine approximate size allocations for each type of Online History data set pair: (Amount accumulated) / (Cylinder capacity) = Size in cylinders

The variables in the formula are as follows: Amount accumulated The amount of data you need to view online Cylinder capacity The average number of records of a specific type that can be stored in one cylinder. See the descriptions in the following section describing how to estimate the average sizes of the records Size in cylinders The number of cylinders to allocate to each of the data sets in the Online History pair

7–6 System Guide Online History Data Set Size - System Statistics

Online History Data Set Size - System Statistics

Estimating the Record Sizes

The sizing of the System Statistics Online History data sets involves the following variables:

■ The length of the history statistics interval (HIST-STATS-TIME parameter)

■ The average sizes of the SMF 100 subtypes 0 (STATS1) and 1 (STAT2) records

■ The amount of data to view online

Average Record Size - STATS1

The average size of the STATS1 record can be calculated as: 1796 bytes + (172 * number of locations)

If you have 0 locations (no distributed DB2 monitoring), the average size of the record is: 1796 bytes + (172 * 0) = 1796 bytes

and if you have 20 locations, the average size of this record would be: 1796 bytes + (172 * 20) = 5236 bytes

Average Record Size - STATS2

The average size of the STATS2 record can be calculated as: 806 bytes + (272 * number of buffer pools)+ (140 * number of global buffer pools)

If you use 1 buffer pool and 0 global buffer pools, the average size of the record would be: 806 bytes + (272 * 1) + (140 * 0) = 1078 bytes

If you use 12 buffer pools and 2 global pools, the average size of the record would be: 806 bytes + (272 * 12)+ (140 * 2) = 3544 bytes

Online History 7–7 Online History Data Set Size - System Statistics

Computing Control Intervals

Normally, two time intervals fit within an 8K control interval until the number of locations or buffer pools push the total size to over 4089 bytes.

To perform calculations for two time intervals per 8K control intervals; do one of the following: (1796 + (locations * 172)) + (806 + (buffer pools * 272) + (global buffer pools * 140) 4089 (locations * 172) + (buffer pools * 272) + (global buffer pools * 140) 1487

The following shows the combination of locations and Buffer Pools that will fit two time intervals within an 8K control interval:

0—Locations 4—Buffer Pools

1—Location 4—Buffer Pools

2—Locations 3—Buffer Pools

3—Locations 3—Buffer Pools

4—Locations 2—Buffer Pools

5—Locations 1—Buffer Pool

6—Locations 1—Buffer Pool

Example

Assume that a shop’s 24-hour coverage (with appropriate STATS1 and STATS2 record sizes) fits two time intervals per 8K control interval. The shop collects System Statistics every 30 minutes (48 times per day). How much space would be required for the System Statistics Online History data sets in a 90 day period? (90 days x 48 intervals per day) / (2 control intervals per block x 90 blocks per cylinder) = 24 cylinders

7–8 System Guide Online History Data Set Size - Accounting

Maximum Record Sizes

The IDDCVSAM job specifies RECORDSIZE (600 6144) to define the maximum record size that can be written. Typically, System Statistics records will grow in size with DB2 usage. Be careful to avoid truncation: once it starts, all records become affected. Truncation first removes the higher sections of the record, and then repeating sections are deleted one by one until the record fits.

The STATS1 record will exceed 6144 bytes when the number of locations exceeds: (6144 - 1796) / 172 = approximately 25 locations

The STATS2 record will exceed 6144 bytes when the number of buffer pools exceeds: (6144 - 806) / 272 = approximately 19 buffer pools

If the DB2 subsystem is part of a data sharing group, the number of active global buffer pools * 140 must be factored into the equation.

Some memory (not disk space) can be saved with a control interval size of 4096 and a maximum record size of 4089. For a maximum record size of 4089, you can specify 13 locations and 10 buffer pools. Reduction in control interval size directly affects the maximum record size (which is control interval size minus 7 bytes).

Online History Data Set Size - Accounting

Estimating the Record Sizes

The sizing of the Accounting Online History data sets involves the following variables:

■ The average size of the SMF 101 (ACCTG) record

■ The amount of data to view online (dictated by environment)

Online History 7–9 Online History Data Set Size - Accounting

Average Record Size - ACCTG

The average size of the ACCTG record can be calculated as: 1198 bytes + (64 * number of buffer pools used) + (44 * number of global buffer pools used) + (220 * number of locations) + (276 * number of packages)

If you have 1 buffer pool, 0 global buffer pools, 2 locations, and 0 packages, the average ACCTG record size would be: 1198 bytes + (64 * 1) + (44 * 0) + (220 * 2) + (276 * 0) = 1702 bytes

Determining the Amount of Data to View Online

In a Development or QA environment, you typically need to see all accounting data. Specify HIST-ACCT=YES. The duration of data needed online can be as long as one week.

In a Production environment, you typically only want to save that data that might be used. Specify HIST-ACCT=FILTER and use a FILTER request to capture all TSO, batch, DBATs, and aborts, as well as CICS/IMS threads that used too much CPU time or had a high-elapsed time. The duration of data needed online can be in the range of 24-36 hours.

Computing Control Intervals

Space calculations are driven by how many average size Accounting records can fit per block. For example, if the average Accounting record size is 1262 bytes (1 buffer pool, no locations, no packages), then 6 records fit per 3390 control interval (6 * 1262 < 8K) or 540 records per 3390 cylinder (6 * 90).

If the average Accounting record size is 1870 bytes (3 buffer pools, no locations, 2 packages), then 4 records fit per 3390 control interval (4 * 1870 < 8K) or 360 records per 3390 cylinder (4 * 90).

Another Example

A shop collects (with filtering) 10,000 records per day with the average size per record being 1600 bytes. How much space would be required for the Accounting Online History data sets in a 7 day period? (7 days x 10,000 records per day) / (5 records per Control Interval x 90 Cls per cylinder) = 155 cylinders

7–10 System Guide Online History Data Set Size - Accounting

Typically, in a high-volume shop, it is not necessary to write all Accounting records to the History System. See Filtering Online Thread Accounting History for more details.

The Online History Quick Summaries (available as option 6.3 from the Main Menu) are not affected by filtering and meet many overall reporting requirements.

Maximum Record Sizes

The IDDCVSAM job specifies RECORDSIZE(600 6144) to define the maximum record size that can be written. Typically, Accounting records will vary greatly in size because of the flexibility in number of Buffer Pools, locations, and packages. Truncation will typically affect just the largest records. When truncation occurs, the higher sections of the record are lost first, followed by the repeating sections being deleted one by one, until the record fits.

This table shows the combination of locations, Buffer Pools, and packages that will fit within 6144 bytes:

Locations Buffer Pools Packages 0 58 5 39 10 21 15 2 20 10 42 0 24 5 5 10 20 8 0

Some memory (not disk space) can be saved with a control interval size of 4096 and a maximum record size of 4089. Reduction in control interval size directly affects the maximum record size (which is control interval size minus 7 bytes).

Online History 7–11 Filtering Online Thread Accounting History

Filtering Online Thread Accounting History

Some sites might not want to allocate large amounts of DASD to collect all thread activity during a specific time frame (e.g., 24 hour) or might not be interested in collecting every type of thread accounting history. If you want to limit the amount, type or frequency of thread accounting history collected, you can use Unicenter CA-Insight’s history filter option.

When history filtering is active, data collector initialization scans each IQL request contained in the STARTUP member of the SOURCE library for the “FILTER” keyword. Every IQL request that contains this keyword is used to additively select the records to be written to thread history. Thread Accounting records that meet the selection criteria specified in at least one filter request are written to history. If the “FILTER” keyword is not found in any IQL request, all thread accounting records are written to history.

For example, one IQL filter request might select threads with a connection type of “TSO” while a second filter request might select threads that exceed an elapsed time of 1 second. Threads that exceed 1 second elapsed time or have a connection type of “TSO” will be written to history and all other threads are discarded.

Filtering Strategies

If your site wants to collect all Thread Accounting history for playback online or for performance and capacity planning purposes then history filtering does not need to be activated. However, if you only need to collect Thread Accounting records for problem determination or if you want to collect data to tune a particular connection type, you should consider history filtering.

The following are some examples of collection strategies that can be implemented through filtering:

■ Test DB2 subsystems: – Select threads that abend – Select threads involved in deadlocks – Select threads with high ratios of lock wait time to elapsed time – Select threads with low ratios of DB2 time to application elapsed time – Discard all other threads

7–12 System Guide Filtering Online Thread Accounting History

■ Production DB2 subsystems: – Filter CICS threads that exceed elapsed time by 2 seconds and TSO application threads by 5 seconds for CICS thread – Filter all thread types that exceed 1 minute elapsed – Filter online threads that experience lock escalation – Filter online threads that issue more than 200 getpages or more than 50 -I/Os – Filter non-batch threads that invoke a tablespace scan – Filter threads with high ratios of lock wait time to elapsed time – Discard all other threads

Activating Filtering

The history filtering option is controlled by the HISTORY-ACCT parameter in the IDDCPRMS data collector initialization member found in the SOURCE library. As described previously, you can use this parameter to control whether thread history is collected. To activate filtering, code the “FILTER” keyword as follows: HISTORY-ACCT=FILTER

This parameter notifies the data collector to initiate filtering. However, all thread records are written to history until you code one or more IQL requests that contain the “FILTER” keyword. The following example of a filter request is contained in the FILTERAC member in the REQUESTS library: FILTERAC: FILTER (FLASH) ACCT WHERE CONN-TYPE = ‘BATCH’ OR ‘TSO’ OR ‘DB2CALL’ OR ‘SERVER’ OR ‘UTILITY’ OR THD-ELAPSED > 0 /* > 0 SECONDS *OR THD-ELAPSED > 1 /* > 1 SECONDS OR THD-TERM-CODE > 16 ;

Online History 7–13 Backing Up Online History

Backing Up Online History

Unicenter CA-Insight in non-stop mode provides 24-hour operation. Non-stop mode coupled with Unicenter CA-Insight’s Online History Unload utility lets you create complete and synchronized daily or weekly historical backups of DB2 performance data. This data can be used in place of SMF collected data as input to the Unicenter CA-Insight Batch Report Writer or MICS or SAS chargeback routines. You can also summarize and insert this data into DB2 history tables using procedures provided with Unicenter CA-Insight (see the “Archiving DB2 Performance Data” chapter for more information).

SOURCE Library Member Modifications

You use the IDDCPRMS, IDUNLJCL and db2ssidGDG members in the SOURCE library to implement the backing up of Online History.

You can modify IDDCPRMS to backup Online History at file switch (when an active file becomes full) or backup Online History at a specific time. Both the Interval Statistics and Thread Accounting data sets are backed up together to form a synchronized file containing all DB2 performance data for a specific time frame.

Make the following modifications to the IDDCPRMS data collector initialization member, the IDUNLJCL JCL procedure and the db2ssidGDG JCL member to backup the Online History data sets:

■ To automatically backup Online History at file switch: 1. Change the HISTARCH-STATS-TASK parameter to the name of the proc started by the data collector to backup Online History when the active Interval Statistics data set becomes full: HISTARCH-STATS-TASK=xxxxxxxx Where xxxxxxxx is the name of the proc (default IDUNLJCL) started at Interval Statistics file switch, or blank to disable backups at Interval Statistics file switch. 2. Change the HISTARCH-ACCT-TASK parameter to the name of the proc started by the data collector to archive Online History when the active Thread Accounting data set becomes full: HISTARCH-ACCT-TASK=xxxxxxxx Where xxxxxxxx is the name of the proc (default IDUNLJCL) started at Thread Accounting file switch or blank to disable backups at Thread Accounting file switch.

7–14 System Guide Backing Up Online History

■ To backup Online History at a specific time: 1. Change the HISTARCH-TIME parameter to the time you want the data collector to start the proc to backup Online History: HISTARCH-TIME=hhmmss Where hhmmss is the time of day in hours, minutes and seconds when you want the data collector to start the proc (default is 230000). 2. Change the HISTARCH-TASK parameter to the name of a proc that is started by the data collector to backup Online History as follows: HISTARCH-TASK=xxxxxxxx Where xxxxxxxx is the name of the proc that will be started at the time specified in the HISTARCH-TIME parameter to backup Online History.

■ Copy the IDUNLJCL member into a PROCLIB. If you rename the proc, you must also modify the HISTARCH-STATS-TASK and HISTARCH-ACCT-TASK parameters to match the new name.

■ Use the db2ssidGDG members in SOURCE library to create a GDG definition that IDUNLJCL uses to create backup generation data sets. You will need to create the GDG for each data collector that you will be customizing to unload data.

The IDUNLJCL procedure is automatically started by the data collector to backup Online History data. The defaults shipped with the IDUNLJCL procedure are coded to remember data set positioning and to backup only records that have been added since the last backup was taken. You can execute IDUNLJCL stand-alone to do ad hoc off-loads of data without disrupting data set positioning. To do this, override the default unload parameters as documented in Online History Data Set Unload (IDB2UNLD) in the “Utilities” appendix.

You may also have the unloaded data automatically loaded into DB2 tables, known as the archive database. The IDB2ARC procedure in the SOURCE library may be used to accomplish this. Refer to the “Archiving DB2 Performance Data” chapter for details on setting up and using the archive database.

Online History 7–15

Chapter 8 Archiving DB2 Performance Data

This chapter describes how you can archive DB2 application and subsystem performance data for later retrieval and analysis. The data can be used to generate reports or GDDM graphs that compare application and subsystem performance data for different time periods.

Flexibility in Archiving

The following section describes the flexibility in archiving.

Types of Archive Data

There are two types of archive data: daily and detail. For each of the daily and detail types, there are two sets of data: application and subsystem data. For each set of data, there are three or four DB2 tables:

■ One table to hold the base data

■ One table to hold the distributed data (broken down by location) associated with the base data

■ One table to hold the Buffer Pool data (broken down by Buffer Pool)

■ One table to hold new Package/DBRM accounting data (broken down by program)

■ One table to hold the Group Buffer Pool data (broken down by Group Buffer Pool)

A one-to-many relationship exists between the base data and the other tables because each base record can contain from zero to any number of Buffer Pools, programs, and remote locations.

Archiving DB2 Performance Data 8–1 Flexibility in Archiving

This table identifies the fourteen DB2 tables and their indexes:

DB2 Table Index CA-INSIGHT.APPLICATION_DETAIL INSACCTDI CA-INSIGHT.APPLICATION_DAILY INSACCTSI CA-INSIGHT.SUBSYSTEM_DETAIL INSSTATDI CA-INSIGHT.SUBSYSTEM_DAILY INSSTATSI CA-INSIGHT.APPL_DDF_DETAIL INSACCTDI_DDF CA-INSIGHT.APPL_DDF_DAILY INSACCTSI_DDF CA-INSIGHT.SUBSYS_DDF_DETAIL INSSTATDI_DDF CA-INSIGHT.SUBSYS_DDF_DAILY INSSTATSI_DDF CA-INSIGHT.APPL_BP_DETAIL INSACCTDI_BP CA-INSIGHT.APPL_BP_DAILY INSACCTSI_BP CA-INSIGHT.SUBSYS_BP_DETAIL INSSTATDI_BP CA-INSIGHT.SUBSYS_BP_DAILY INSSTATSI_BP CA-INSIGHT.APPL_PGM_DETAIL INSACCTDI_PGM CA-INSIGHT.APPL_PGM_DAILY INSACCTSI_PGM CA-INSIGHT.APPL_GBP_DETAIL INSACCTDI_GBP CA-INSIGHT.APPL_GBP_DAILY INSACCTSI_GBP CA-INSIGHT.SUBSYS_GBP_DETAIL INSSTATDI_GBP CA-INSIGHT.SUBSYS_GBP_DAILY INSSTATSI_GBP

Loading Archive Data from Online History

The Archive tables are populated with SMF-format DB2 performance data. The source of this data can be the Online History files (described in the “Online History” chapter. As shown in the following graphic, you can use the Unicenter CA-Insight Unload utility (IDB2UNLD) to off-load Online History data to a sequential file in native SMF format. The Archive tables do not need to be installed in order for you to use the Unload utility.

8–2 System Guide Flexibility in Archiving

The following illustration shows the general flow used to unload Online History and store the detailed and summarized data into the fourteen tables described earlier.

The data to be archived can come from two sources:

■ Online History

■ A sequential data set containing SMF records

The detail tables contain rows for each DB2 accounting record and statistics interval record. Therefore, the amount of DB2 activity controls the amount of data and determines the size of the accounting detail tables. The statistics collection interval controls the amount of data to be stored in the statistics detail tables (and their sizes).

The list of columns generated by the IDB2ARCmember can be found in the ARCDDL member of the SOURCE library.

Archiving DB2 Performance Data 8–3 Optimizing Your Archive Data

Optimizing Your Archive Data

The daily tables contain a daily summary for the subsystems and their applications. This data is ideal for trend analysis and very useful for capacity planning. For applications, the data is summarized for each system, subsystem, plan name, and connection ID combination.

For subsystems, the data is summarized by system and subsystem. You can archive data from multiple systems and subsystems into the same set of DB2 tables because both the system name and the subsystem name are a part of the keys for the tables.

However, because the Unicenter CA-Insight Batch Report Writer Archive IQL requires that the input be sorted by date and time, you might want to process data from only one data collector at a time. In other words, if you process data from multiple data collectors at the same time, you need to presort the SMF data before you can archive it.

The Unicenter CA-Insight Batch Report Writer Archive IQL cannot ensure that duplicate data is not put into the DB2 tables, particularly in the _DAILY tables (unique keys help with the _DETAIL tables). Thus, you should ensure that you are processing new data when archiving to DB2 tables.

You should also periodically delete data that is over x days old and run REORG to reclaim deleted space. Sample SQL member ARCSQLD in the SOURCE library has been provided to perform the delete.

Archive Data Sources

For flexibility, you can use other data that has been off-loaded from the Online History files (using the Unicenter CA-Insight Unload utility), or you can use data collected and off-loaded from SMF (MANx data sets). In both cases, you end up with an SMF flat file.

Using the SMF flat file, you can run a Unicenter CA-Insight Batch Report Writer job that creates “outfiles” containing data for the Unicenter Fast Load or DB2 Load utility. Finally, you can run either load utility to put the data in the DB2 tables.

If you have multiple CPUs, you can transfer the sequential SMF file from one CPU to another. You can then use the unloaded SMF data from one system as input to the Batch Report Writer Archive IQL in another. In this way, you can keep all of your DB2 data together in one database on a single system.

8–4 System Guide Installing the Archive Component

The following illustration shows this consolidation process.

Installing the Archive Component

After completing the basic installation under the post install process, you can perform the following steps to install Unicenter CA-Insight’s Archive component: __ Step 1: Create the Archive Database (ARCSPACE, ARCDDL). __ Step 2: Obtain SMF Data from Online History (IDB2UNLD). __ Step 3: Copy and Tailor the IDB2ARC Member (IDB2ARC). __ Step 4: Automate the Unload Process (IDDCPRMS).

Perform the first step for DB2 subsystems that are to have an Archive database. Perform the third step for the MVS system that is to execute the data preparation and load jobs.

The fourth step is necessary only if you wish to perform the Online History unload using an automatically invoked task.

Archiving DB2 Performance Data 8–5 Installing the Archive Component

Requirement for Archiving

If a sequential data set is used as input to the archive process, the data must first be sorted by date and time (for each system-subsystem combination).

Migration Considerations

If you created archive tables in an older release of Unicenter CA-Insight, you need to create a new set of archive tables for the current release. The new archive tables include new fields added to support the latest release of DB2. When you use the ARCSPACE CLIST to generate the DDL, you can change the table qualifier (creator) so the new tables can exist with your current tables. You can then use the ARCV4CPY, ARC51CPY, ARC52CPY, ARC61CPY, and ARC62CPY member in the SOURCE library to copy data from your Unicenter CA-Insight V4, V5.1, V5.2, V6.1, and V6.2 tables to the current release.

Step 1: Create the Archive Database

Follow these steps to create the Archive database: 1. Edit the ARCSPACE CLIST in the Unicenter CA-Insight CLIST library following its instructions for customizing and executing the member. 2. Use SPUFI under DB2I to execute the $ARCDDL member created by the ARCSPACE CLIST. Upon successful execution, the $ARCDDL member:

■ Provides a STOGROUP for the Unicenter CA-Insight Archive database

■ Defines the Archive database, tablespaces, DB2 tables, and indexes, and

■ Grants privileges to authorized users for access to the Archive database

This step is complete when the $ARCDDL member finishes executing with a condition code of 0.

Keeping Archive Data Synchronized

You can alter columns and delete tables as desired, but you should keep the DDL for table creation, IQL for processing and converting SMF data, and the load utility statements synchronized. That is, if you add or delete a column, that column should be added/deleted in the DDL member, the IQL member, and the load statement member.

Note: It is highly recommended that you do not alter the indexes or the “identification section” for each table.

8–6 System Guide Installing the Archive Component

This table shows each table’s related IQL and load utility statement members.

Load Utility Table IQL Member Statement Member APPL_DETAIL ARCIACD ARCLACD APPL_BP_DETAIL ARCIACDB ARCLACDB APPL_GBP_DETAIL ARCIACDG ARCLACDG APPL_DDF_DETAIL ARCIACDD ARCLACDD APPL_PGM_DETAIL ARCIACDP ARCLACDB APPLICATION_DAILY ARCIACS ARCLACS APPL_BP_DAILY ARCIACSB ARCLACSB APPL_GBP_DAILY ARCIACSG ARCLACSG APPL_DDF_DAILY ARCIACSD ARCLACSD APPL_PGM_DAILY ARCIACSP ARCLACSP SUBSYSTEM_DETAIL ARCISTD ARCLSTD SUBSYS_BP_DETAIL ARCISTDB ARCLSTDB SUBSYS_GBP_DETAIL ARCISTDG ARCLSTDG SUBSYS_DDF_DETAIL ARCISTDD ARCLSTDD SUBSYSTEM_DAILY ARCISTS ARCLSTS SUBSYS_BP_DAILY ARCISTSB ARCLSTSB SUBSYS_GBP_DAILY ARCISTSG ARCLSTSG SUBSYS_DDF_DAILY ARCISTSD ARCLSTSD

Step 2: Obtain SMF Data from Online History

You can use the Online History files for your data source, but you must first use the IDB2UNLD utility to unload the data to a flat file. If you use the IDB2UNLD utility to create the SMF file, it is highly recommended that you use the default options of REMEMBER-POS=YES and UNLOAD=NEW. See the “Utilities” appendix for a complete description of the IDB2UNLD utility.

Member db2ssidGDG can be used to define a GDG base for use with the unload process.

Archiving DB2 Performance Data 8–7 Installing the Archive Component

Step 3: Copy and Tailor the IDB2ARC Member

The IDB2ARC member in the SOURCE library can be used as a sample proc for unloading, converting, and loading into DB2. You can copy the member to a proc library, then tailor the copied member as indicated by the comments in it.

You can give the procedure any name you want.

The list of columns generated by the IDB2ARC member can be found in the ARCDDL member of the SOURCE library.

Step 4: Automate the Unload Process

You can automate the Online History unload process using the data collector initialization parameters member (IDDCPRMS). The parameters tell when and what task (proc) the data collector should start to perform an unload.

You can also run the unload job on a demand basis, or use a scheduling product such as JOBTRAC to submit and track execution of the unload job.

The data collector initialization parameters for starting an unload task (proc) include: HISTARCH-TIME Specifies the time of day to invoke the unload as a started task (HHMMSS). HISTARCH-TASK Identifies the name of the proc to invoke as a started task. If no name is specified, then a proc for a time of day is not submitted. HISTARCH-STATS-TASK Identifies the name of the proc to invoke when a switch occurs in the STATS A/B files. HISTARCH-ACCT-TASK Identifies the name of the proc to invoke when a switch occurs in the ACCT A/B files.

The main purpose of the last two parameters is to handle the instance of more than one file switch per day.

Unicenter CA-Insight passes the DBSUB, DBLOC, and TESTVER parameters to identify the data collector to the started task. The IDB2ARC member in the SOURCE library can be used as a sample started task.

8–8 System Guide General Recommendations

General Recommendations

While processing needs can vary from one installation to another, the following is a suggested approach for archiving DB2 application and subsystem data to DB2 tables.

Archiving Daily Data

Archiving daily data for both applications and subsystems is generally recommended for all systems. You can retain this data for extended periods at a relatively low processing and DASD cost.

You can maintain years of subsystem daily summary data at a very low cost because there will be only one subsystem record (row) per day of activity. Most installations can probably maintain at least a year’s worth of application daily summary data depending upon the amount of DASD dedicated to holding this data and the number of plans executed on a daily basis.

Note: If you have DB2 SMF data on tape, you might want to place it in the Archive database using the Batch Report Writer.

Archiving Detail Data

Archiving detail data should generally be performed on an as-needed basis. However, for development subsystems, you might want to archive application detail data on a permanent basis, keeping the data for a relatively short period of time (a few weeks to a month). This will cause little difficulty for your system because development environments typically do not generate great activity (except during stress test situations). This also provides you with the detailed data that you need in a development environment.

You should consider archiving subsystem detail data whenever you want to measure activity on a time interval basis. This data can show you the peak and low periods of DB2 activity. You can use this information during stress test situations and for capacity planning.

Manipulating Archived Data

Once data has been loaded into the Archive database, you can use it as input for generating graphs using GDDM or for generating reports. The ARCSQL member in the SOURCE library contains sample SQL statements for manipulating archived data from the Archive database.

Archiving DB2 Performance Data 8–9 Related Archive Component Members

Managing the Archive Environment

Since the Archive tables can hold data for multiple systems and subsystems, the archive environment is easy to manage. Because of this design, you can extract data from one or more systems (using the unloaded Online History data, or raw SMF data), transfer it to the system with the Archive database, and download it to the DB2 tables using the Archive download job. This way, you can keep the Archive database on one system and minimize the impact on critical (production) systems.

If you choose to store data from multiple subsystems in the same set of Archive tables, you should run STEP1 (Unload) and STEP2 (Report Writer) of the IDB2ARC job for each data collector. The remaining steps must be run at the site where you are storing the data into DB2 tables.

Related Archive Component Members

The following is a listing of the related SOURCE library members for the Archive component: ARCV4CPY Sample SQL for moving data from Unicenter CA-Insight V4 tables to the current tables. ARC51CPY Sample SQL for moving data from Unicenter CA-Insight V5.1 tables to the current tables. ARC52CPY Sample SQL for moving data from Unicenter CA-Insight V5.2 tables to the current tables. ARC61CPY Sample SQL for moving data from Unicenter CA-Insight V6.1 tables to the current tables. ARC62CPY Sample SQL for moving data from Unicenter CA-Insight V6.2 tables to the current tables. ARCCOPY Sample copy statements for the DB2 COPY utility1 ARCDDL Sample SQL for creating Archive databases $ARCDDL Generated by the ARCSPACE CLIST

8–10 System Guide Related Archive Component Members

ARCLxxxx Sample load statement members1 ARCSPACE CLIST to calculate DASD space and generate customized DDL ARCSQL Sample SQL for retrieving data from the Archive database1 ARCSQLD Sample SQL for deleting old data from Archive tables1 IDB2ARC Sample proc for unloading, converting, and loading Online History data db2ssidGDG Sample JCL to create a GDG base IDRWPRMS SYSPARM for the Batch Report Writer If Unicenter CA-Insight’s default table qualifier is modified, the ARCSPACE CLIST updates this member to reflect the new qualifier. The ARCIxxxx member (sample archive IQL member) can be found in the TGTREQ library.

Archiving DB2 Performance Data 8–11

Chapter 9 Unicenter CA-24x7 Scheduler

This chapter describes how to use Unicenter CA-24X7 Scheduler.

Unicenter CA-24X7 is a utility that lets you:

■ Dynamically change DB2’s startup parameters (ZPARMS)

■ Cancel DB2 threads

■ Add and delete active log data sets

■ Free database page sets of all users

■ Refresh user exit routines

The utility can be run as a batch job or directly from the Unicenter CA-Insight online user interface. The integrated scheduler lets you set runtime parameters for a particular period of time without having to be on hand to perform the changes.

Components

Unicenter CA-24X7 has three main components:

■ Unicenter CA-Insight Online Panels—an interactive process for invoking Unicenter CA-24X7 functions by entering values on a series of panels. Options are also added to Thread List displays to cancel threads. For guidance in using this online version of Unicenter CA-24X7, see the Unicenter CA-Insight User Guide.

■ Batch Utility—Unicenter CA-24X7 syntax is treated as input to a batch job. For Unicenter CA-24X7 batch syntax, see the “Utilities” appendix.

■ Scheduler—Unicenter CA-24X7 syntax (including scheduling commands) is created as an input data set to the data collector, which handles the execution of the syntax. The Scheduler is described in this chapter.

Unicenter CA-24x7 Scheduler 9–1 How the Scheduler Works

Security for Unicenter CA-24X7

To use Unicenter CA-24X7, you must enable security. By default, all Unicenter CA-24X7 security is turned off.

Unicenter CA-24X7 is designed to alter DB2 parameters affecting security, operations, memory, and logging functions of DB2. Carefully consider who should be able to access Unicenter CA-24X7. Generally, security should be set up to allow access to those individuals who normally would update the DSNZPARMS for DB2. As in any tool that changes operational system parameters, use care that you understand the impact of your change. All parameters contain field-level online help and are also documented in the IBM DB2 Administration Guide.

The following security parameters associated with Unicenter CA-24X7 functions are shown here. For their descriptions, see the “Security” chapter.

■ X247CTHD=[YES | NO]

■ X247SEC=[YES | NO]

■ X247=[YES | NO]

Additionally, if you are planning on using the Unicenter CA-24X7 Scheduler, you should protect your Schedule data set (described in How the Scheduler Works) as needed.

Data Collector Cards for Unicenter CA-24X7

If the Unicenter CA-24X7 optional product extension is licensed, two additional DD statements must be added to the data collector JCL procedure. They are: //UDBOUT DD SYSOUT=* 24X7 sysout //UDBSCHED DD DUMMY

The UDBSCHED DD statement can be specified as dummy, or can to a file of 24X7 commands as explained in the next section.

How the Scheduler Works

The Unicenter CA-24X7 Scheduler can be used to control when DB2 should be running with a particular set of customized parameter values. For example, you can use the Scheduler to change the Buffer Pool size during prime-time processing.

9–2 System Guide Scheduler Command Syntax

The Scheduler works by defining a set of desired values, through Unicenter CA-24X7 schedule commands, that should be in effect for a given time and/or days of the week, in a sequential data set. The data set is preallocated in the data collector startup JCL as DD name UDBSCHED.

Using Another Scheduler with the Unicenter CA-24X7 Batch Utility

You can use another batch job scheduler to execute the Unicenter CA-24X7 Batch Utility to process Unicenter CA-24X7 commands at a given time of day. But unlike the Unicenter CA-24X7 Scheduler, if DB2 is restarted, the default parameters will once again be in effect.

Scheduler Command Syntax

To use the Scheduler, code the following syntax into a data set: SCHEDULE FROM(start-time) TO(end-time) DAYS([MON] [,TUE] [,WED] [,THU] [,FRI] [,SAT] [,SUN] | *) COMMAND=“CA-24X7command”

where:

■ start-time specifies the begin time of the day that the command is to be issued (00:00-24:00)

■ end-time specifies the end time of the day that the command is to be issued (00:00-24:00)

■ * specifies that the command is to be issued every day

■ CA-24X7 (command) gives the command text of the command that is to be issued.

Invoking the Scheduler

The Unicenter CA-24X7 Scheduler can be invoked in several ways. The following are the two recommended options for invoking the Scheduler:

Option A

We recommend this option if you have a separate SOURCE library for each DB2 subsystem.

All commands in the SCHEDULE SOURCE library for this DB2 only reside in the SCHEDULE member of the SOURCE library.

Unicenter CA-24x7 Scheduler 9–3 Scheduler Command Syntax

First example SCHEDULE member for DB23 SCHEDULE FROM(17:20) TO(17:25) DAYS(THU) COMMAND=“SET BPMAX BPID(BP0) VALUE(2000) FOR(DB23)” SCHEDULE FROM(17:26) TO(17:30) DAYS(THU) COMMAND=“SET BPSIZE BPID(BP0) VALUE(2000) FOR(DB23)”

Second example SCHEDULE member for DBV3 SCHEDULE FROM(17:20) TO(17:25) DAYS(THU) COMMAND=“SET BPMAX BPID(BP0) VALUE(2500) FOR(DBV3) SCHEDULE FROM(17:26) TO(17:30) DAYS(THU) COMMAND=“SET BPSIZE BPID(BP0) VALUE(2000) FOR(DBV3)

Option B

We recommend this option if you have a shared SOURCE library.

Establish a different SCHEDULE member for each data collector.

First example SCHDDB23 controls DB23 SCHEDULE FROM(17:20) TO(17:25) DAYS(THU) COMMAND=“SET BPMAX BPID(BP0) VALUE(2500) FOR(DB23)” SCHEDULE FROM(17:26) TO(17:30) DAYS(THU) COMMAND=“SET BPSIZE BPID(BP0) VALUE(2000) FOR(DB23)”

Second example: SCHDDBV3 controls DBV3 SCHEDULE FROM(17:20) TO(17:25) DAYS(THU) COMMAND=“SET BPMAX BPID(BP0) VALUE(2500) FOR(DBV3)” SCHEDULE FROM(17:26) TO(17:30) DAYS(THU) COMMAND=“SET BPSIZE BPID(BP0) VALUE(2000) FOR(DBV3)”

Although the same SCHEDULE member can contain commands for all DB2s on the same MVS subsystem and, in this case, the user would be responsible for resolving conflicts in dates and times to perform a specific act, this is not a recommended procedure. You should use one of the options previously described to invoke the Scheduler.

A Note About FROM and TO

Unicenter CA-24X7 will not change any values when the TO time is reached. The purpose of the FROM/TO range is to define a time range when the specified value should be in effect. This is normally done when the FROM time occurs. However, if the system or DB2 subsystem is (re)started after the FROM time has occurred, then the FROM/TO range will indicate to Unicenter CA-24X7 that the scheduled command is still valid and should be issued.

9–4 System Guide Scheduler Command Syntax

If you want to change the value at the end of the FROM/TO range, then you should define another SCHEDULE command to reset the value.

Note: There is no checking to ensure that FROM/TO time ranges overlap for the same commands.

First example

In this example: SCHEDULE FROM(08:00) TO (17:00) DAYS(MON,TUE,WED,THU,FRI) COMMAND=“SET SYSOPR2 VALUE(JJZ) FOR(DBV3)”

Unicenter CA-24X7 will change the SYSOPR2 value to “JJZ” on the DBV3 subsystem weekdays from 8AM to 5PM.

Second example

In this example:

SCHEDULE FROM(00:00) TO (07:59) DAYS(*) COMMAND=“SET BPSIZE BPID(BP0) VALUE(20000) FOR(DB23)”

Unicenter CA-24X7 will change the Buffer Pool 0 size to 20,000 on the DB23 subsystem every day from 12:00 AM to 07:59 AM.

Third example

In this example SCHEDULE FROM(08:30) TO(17:30) DAYS(*) COMMAND=“SET BPSIZE BPID(BP0) VALUE(2500) FOR(DBV3)” SCHEDULE FROM(17:30) TO(24:00) DAYS(*) COMMAND=“SET BPSIZE BPID(BP0) VALUE(5000) FOR(DBV3)” SCHEDULE FROM(24:00) TO(08:29) DAYS(*) COMMAND=“SET BPSIZE BPID(BP0) VALUE(5000) FOR(DBV3)”

Unicenter CA-24X7 will change the Buffer Pool 0 size to 2500 on the DBV3 subsystem everyday from 8:30 AM to 5:30 PM. From 5:30 PM to 8:29 AM, Unicenter CA-24X7 will set the Buffer Pool 0 size to 5000. Note that since time ranges are not allowed to span midnight, the time period is divided into two parts: 17:30 to 24:00, and then 24:00 to 8:29.

Unicenter CA-24x7 Scheduler 9–5 Viewing Schedules Online

Viewing Schedules Online

You can view the existing Scheduler items, as well as refresh the list.

Select Option 13 (CA-24X7 Schedules) from the CA-24X7 Main Menu to display the Schedules panel (a sample is shown in the following):

Menu Print Tools Help CA-INSIGHT SE19257 DBV3 S018

CA-24X7 CA-24X7 Schedules

Use F5 to edit and F6 to refresh the CA-24X7 schedules.

Day/wk From To MTWTFSS Command text 16:06 16:30 YYY.... SET BPSIZE BPID(BP0) VALUE (2000) 16:00 16:05 YYY.... SET BPSIZE BPID(BP0) VALUE (1800) 16:06 16:30 YYY.... SET BPMAX BPID(BP0) VALUE (2000) 16:00 16:05 YYY.... SET BPMAX BPID(BP0) VALUE (1800)

To update the command in the Scheduler, press PF5. After the commands have been entered, press PF3 to save the SCHEDULE member. To activate the new commands and refresh the list of schedules, press PF6.

9–6 System Guide Chapter 10 Unicenter Agent for DB2

This chapter describes the steps necessary to add support of the Unicenter Agent for DB2 for z/OS and OS/390 to a Unicenter CA-Insight data collector.

Unicenter agents are applications that support network management of the components of an enterprise. The Unicenter agent for z/OS and OS/390 provides information about a DB2 subsystem to the Unicenter management application. The information is a simplified and standardized view of monitored data about the health of the DB2 subsystem. The data is used to monitor many network components from a single Unicenter workstation console. You can tell at a glance when a DB2 for OS/390 subsystem needs your attention. Using easy-to-understand icons, symbols, and color, you can respond to critical situations when they arise.

This chapter describes the steps required to enable the separately licensed Agent support in the Unicenter CA-Insight data collector. The Unicenter Using the DB2 Agent guide should be used for general product information. It should also be used for background for the z/OS and OS/390 installation of the Agent. It must be used for the Agent workstation installation and for configuring the Agent.

Mainframe Requirements

See the Unicenter Using the DB2 Agent guide for the requirements of the Agent.

Installation Steps to Add Agent

See the Unicenter Using the DB2 Agent guide for instructions on how to install the Agent. Once the Agent has been installed, perform the following steps to add support for the Agent to a Unicenter CA-Insight data collector:

Unicenter Agent for DB2 10–1 Installation Steps to Add Agent

Step 1: Modify System Initialization Parameters

The original db2ssidSYSP in the Unicenter CA-Insight distribution library has parameter UNICENTER-AGENT=NO. To activate the DB2/MVS Agent, change the parameter to UNICENTER-AGENT=YES.

Step 2: Modify and Add JCL to the Data Collector Procedure

The data collector can be executed as a batch job or as a started task . The following steps should be followed to add Agent JCL to the procedure with which Unicenter CA-Insight is currently executed.

To modify the data collector JCL, take the DAGTIDBJ member in the Agent SOURCE library and copy its contents immediately following the last concatenated library for the STEPLIB DD statement in your current data collector JCL procedure.

Step 3: Restart the Data Collector

Restart the data collector with the modified JCL from the last step.

10–2 System Guide Chapter Unicenter Performance 11 Management Predictor

This chapter describes the steps necessary to let Unicenter CA-Insight send data to Unicenter Performance Management Predictor (PMP). Unicenter PMP is a separately-licensed product that uses Neugent technology to predict future performance problems. You can feed the data to PMP in real time mode from a data collector or in batch through the batch report writer. Once enough data has been sent to PMP, you can run an analysis (training) of the data so that PMP will have a model for which to base predictions. See the Unicenter Performance Management Predictor Administration Guide for details on understanding and using PMP.

Unicenter Performance Management Predictor Set Up

To send data to PMP, you must perform the following steps: __ Step 1: Load The Product Definitions Into Pmp __ Step 2: Customize the Data Collector or Batch Report Writer Sysparms.

Step 1: Load The Product Definitions Into Pmp

Edit the UPMPLOAD member in the SOURCE library. Set the name of the Unicenter PMP load library in the STEPLIB and set the PMP subsystem ID in the parm field on the EXEC card. Then submit the JCL to have the Unicenter CA-Insight product definitions loaded into the PMP data base.

Product Definitions

The following definitions will be loaded.

■ Product—DB2

■ Filter Action—Accept

■ Product Name—Unicenter CA-Insight

■ Description—DB2 Performance Monitor

Unicenter Performance Management Predictor 11–1 Unicenter Performance Management Predictor Set Up

Variable Definitions

Warning Critical Threshold Default Variable Name Threshold Threshold Type Type Rule Method APPL_AVG_DB2CPU 0 0 Gauge Low Default APPL_AVG_DB2ELAP 0 0 Gauge Low Default APPL_BP_AVG_GETP 0 0 Gauge Low Default APPL_BP_AVG_READ 0 0 Gauge Low Default APPL_BP_AVG_SEQP 0 0 Gauge Low Default APPL_COMMITS 0 0 Delta Low Default APPL_LOCK_ERRORS 1 10 Delta Low Default APPL_RECORDS 0 0 Delta Low Default APPL_ROLLBACKS 0 0 Delta Low Default SS_ACCT 0 0 Delta Low Default SS_BP_EFFICIENCY 4 2 Gauge High Default SS_BP_GETPAGE 0 0 Delta Low Default SS_BP_PCT_ACTIVE 75 90 Percent Low Default SS_BP_PG_WRITES 0 0 Delta Low Default SS_BP_SIZE 0 0 Gauge Low Default SS_BP_SYNC_READS 0 0 Delta Low Default SS_BP_UPDATES 0 0 Delta Low Default SS_BP_WARNINGS 1 10 Delta Low Default SS_DB2_AS_PAGING 5 20 Rate Low Default SS_DB2_AS_PCTCPU 20 50 Percent Low Default SS_DB2_AS_WSS 0 0 Gauge Low Default SS_DB2_ELAP_SECS 0 0 Counter Low Default SS_EDM_%CT_LOAD 10 20 Percent Low Default SS_EDM_%DBD_LOAD 5 20 Percent Low Default SS_EDM_%DYN_LOAD 50 75 Percent Low Default SS_EDM_%PT_LOAD 10 20 Percent Low Default SS_EDM_FAIL 0 1 Delta Low Default SS_EDM_PAGES 0 0 Gauge Low Default

11–2 System Guide Unicenter Performance Management Predictor Set Up

Warning Critical Threshold Default Variable Name Threshold Threshold Type Type Rule Method SS_EDM_PAGES_DS 0 0 Gauge Low Default SS_EDM_PCT_FREE 0 0 Percent Low Default SS_LOCK_SUSPENDS 0 0 Delta Low Default SS_LOCK_WARNINGS 1 10 Delta Low Default SS_LOG_DELAY_WRT 1 100 Delta Low Default SS_LOG_WARNINGS 1 10 Delta Low Default SS_PCT_DSMAX 90 95 Percent Low Default SS_PCT_MAX_BATCH 80 90 Percent Low Default SS_PCT_MAX_DDF 80 90 Percent Low Default SS_PCT_MAX_INACT 80 90 Percent Low Default SS_PCT_MAX_THRDS 80 90 Percent Low Default SS_PCT_MAX_TSO 80 90 Percent Low Default SS_RIDPOOL_FAIL 0 0 Delta Low Default SS_SQL_DYNAMIC 0 0 Delta Low Default SS_SQL_FETCH 0 0 Delta Low Default SS_SQL_INSUPDDEL 0 0 Delta Low Default SS_SQL_OPEN_SEL 0 0 Delta Low Default SS_STORPROC_FAIL 2 20 Delta Low Default SS_UOW 0 0 Delta Low Default

In addition to the above, variable descriptions are added to the variable definitions. See the variable descriptions in the loaded definitions for details on each variable.

Unicenter Performance Management Predictor 11–3 Unicenter Performance Management Predictor Set Up

Sample Model Definitions

There are two sample model definitions supplied. One model is used for training with subsystem data for analyzing subsystem performance and another for training with application data for analyzing application performance. The subsystem model name is DB2 SUBSYSTEM and the application model name is DB2 APPLICATION.

The settings for these models do not take on the default PMP options at the time the definitions are loaded. Customize these models as needed. Each sample model contains one pattern each. The DB2 SUBSYSTEM pattern includes all the variables that start with SS and the DB2 APPLICATION pattern includes all variables that start with APPL. Before using the application model, you should customize the definition so that you train for specific applications.

Once the definitions have been loaded into the PMP database, you should use the PMP user interface to change the definitions as needed. The definitions loaded are intended to be sample definitions to get you started.

Step 2: Customize the Data Collector or Batch Report Writer Sysparms.

You must perform the following:

■ Enable the connection to Unicenter PMP through the UNIPMP-ENABLED sysparm option.

■ Ensure that the UNIPMP-SSID is set to the correct subsystem ID

■ Ensure that the UNIPMP-INTERVAL matches the interval specified in the Unicenter PMP options.

See Customizing Data Collector Initialization Parameters in the “Operation and Customization” chapter for details on these parameters.

For the batch report writer, if you are loading data from a different system into the PMP database, you should also set the UNIPMP-SYSNAME and UNIPMP-SMFID sysparms to define the source system from which the data was collected. See the Batch Report Reference Guide for details on these parameters.

11–4 System Guide Customizing Data to be Collected

Customizing Data to be Collected

Unicenter CA-Insight uses data collected on behalf of IQL requests to send data to PMP. You can customize the existing IQL or code your own to pass data you need to PMP. When coding IQL to pass data to PMP, you should use the UPMP IQL destination and the INTERVAL UNIPMP clause. See the Writing IQL Requests guide for details on these options.

Note: When adding your own fields, remember to add the associated variable definitions for the DB2 product in PMP.

When Unicenter CA-Insight writes data to PMP, it passes the following:

■ The variable name. Identifies the data item being passed to PMP. This is the same name as defined in the variable definition in the PMP database. Unicenter CA-Insight uses the convention of starting all subsystem-related metrics with “SS” and all application related metrics with “APPL.” This makes it convenient when defining patterns in PMP.

■ The instance ID. The instance ID identifies a specific occurrence of a variable. The default standards used by Unicenter CA-Insight are as follows: – For subsystem data, the instance ID contains the DB2 subsystem name. – For application data, the instance ID contains the DB2 subsystem name in bytes 1-4, the plan name in bytes 6-13, and the connection name in bytes 15-22. Each name is separated by blanks. Thus when defining models in PMP, you can use the instance ID to only look at data for a specific application.

■ The data value. This is the value to be passed to PMP.

■ The data type. Identifies the type of data as one of the following: – GUAGE—Indicates the data value is a snapshot or an average value – COUNTER—Indicates the data value is a cumulative counter spanning over intervals – PERCENT—Indicates the data value is a percentage – RATE—Indicates the data value is a rate – DELTA—Indicates the data value represents a count of a value during a specific interval

■ An optional warning threshold value.

■ An optional critical threshold value.

Unicenter Performance Management Predictor 11–5 Customizing Data to be Collected

Each line of IQL output is parsed by Unicenter CA-Insight and the data passed to PMP. Note that there is a byte before each data item which is used for the field attribute. This byte is ignored by Unicenter CA-Insight when processing the data. Each line should have the following format. * instance: columns 2-129 (attr + 128 bytes) * variable: columns 131-146 (attr + 16 bytes) * value: columns 148-159 (attr + 12 bytes right justified) * type: columns 161-168 (attr + 8 bytes) GAUGE/COUNTER/PERCENT/ * RATE/DELTA (AVG => GAUGE) * (NOTE: warn/crit threshold values can be set in the PMP variable * definition for the product) * warn: columns 170-181 (attr + 12 bytes right justified) * crit: columns 183-194 (attr + 12 bytes right justified)

The following is an example of IQL code used to generate a line with the format above: %:001 SUBSYS PLAN-NAME CONN-TYPE :130 ‘APPL_COMMITS ‘ :147 SUM(COMMITS) (PF=N12) :160 ‘DELTA ‘ :169 ‘ ‘ :182 ‘ ‘

The following sample IQL members are sent with Unicenter CA-Insight: UPMPAPPL Passes real time application data to PMP. UPMPSYS Passes real time subsystem data to PMP. UPMPSSBP Passes real time subsystem buffer pool data to PMP. UPMPBTAP Passes historical application data to PMP through the batch report writer. UPMPBTSS Passes historical subsystem (including buffer pool) data to PMP through the batch report writer. When you enable PMP through the UNIPMP-ENBLAED sysparm, the UPMPAPPL, UPMPSYS and UPMPBTAP requests are started automatically. They are included in the default STARTUP member in a set of #IF UNIPMP - #IFEND statements. While you can use SMF to feed data to PMP through the batch report writer, we recommend you use real time subsystem data (application data makes no difference) because some of the data collected in real time is not available in the SMF statistics records.

11–6 System Guide General Notes and Recommendations

For example, the UPMPBTSS request does not include the following data: SS_DB2_AS_PAGING DB2 address space paging rate. SS_DB2_AS_WSS DB2 address space working set size. SS_DB2_ELAP_SECS The length of time DB2 has been active. SS_PCT_DSMAX The percent of maximum data sets allowed. SS_PCT_MAX_BATCH The percent of maximum batch threads allowed. SS_PCT_MAX_DDF The percent of maximum remote threads allowed. SS_PCT_MAX_INACT The percent of maximum inactive threads allowed. SS_PCT_MAX_THRDS The percent of maximum threads allowed. SS_PCT_MAX_TSO The percent of maximum TSO threads allowed. The same application data is passed by both the UPMPAPPL and UPMPBTAP requests.

General Notes and Recommendations

■ While you can define the threshold values for a variable in the IQL request, we recommended that you set the threshold values in the variable and/or pattern definitions in PMP.

■ PMP allows filtering of data to limit the data stored in the PMP database. However, it is more efficient if you use IQL to limit the data collected.

■ You can use the UNIPMP-DEBUG sysparm option to help in debugging your IQL and identifying what data is being sent to PMP. This option will cause all data to be echoed to the DBGPRINT output.

■ When connecting to PMP, Unicenter CA-Insight defines the product name as DB2 and the connecting job name as the DB2 subsystem ID. This is useful when defining variable patterns in PMP.

Unicenter Performance Management Predictor 11–7

Appendix A NSIGHTEX User Exit

This appendix discusses NSIGHTEX, the one routine used for all user exit functions in Unicenter CA-Insight.

The NSIGNTEX exit is called from the data collector as well as the TSO, VTAM, and batch user interfaces. The function requested is specified with the call.

The NSIGHTEX User Exit is provided in both the AUTH.LOAD and SOURCE libraries. NSIGHTEX only needs to be modified if you require additional functionality. Default functionality includes checks to RACF, CA-Top Secret, and CA-ACF2 security. The sample code is in the SOURCE library member NSGHTEXA.

Operation

Each routine is passed in register R1 as the address of a control block. The first eight characters of the control block name the function to be performed.

■ R1- Address of IUIUPL control block (see IUIUPL in the SOURCE library)

■ R13 - Address of standard OS save area

■ R14 - Return address

■ R15 - Entry point address

Exit Characteristics

These are the characteristics of the NSIGHTEX User Exit:

■ The TSO, VTAM, and batch user interfaces require an NSIGHTEX load module. These routines will abnormally terminate if the routine is not present.

■ The data collector requires the NSIGHTEX User Exit only if SECURITY=YES and SECURITY-EXIT=NSIGHTEX have been specified. The load module can have any name, but we suggest that you call it NSIGHTEX and use the same load module as the user interface.

NSIGHTEX User Exit A–1 Functions by Caller - Data Collector

■ In the data collector the User Exit runs in an authorized environment in program state.

■ The VTAM user interface needs to be authorized only if the exit needs to access an external security package (RACF, CA-Top Secret, or CA-ACF2). If the VTAM user interface is authorized, the exit will be called in an authorized environment.

■ Each routine is entered in 31-bit addressing mode and must return in the same mode.

■ An ESTAE environment is established before the exit routine is called from the data collector from an abend within the exit routine. If an abend does occur, the exit routine is disabled and processing continues as if no exit routine had been specified.

Assembly and Link-Editing

Sample JCL is provided in member MAKEEX in the SOURCE library. This sample JCL assembles and link-edits the NSIGHTEX User Exit.

Functions by Caller - Data Collector

The following section discusses the functions by caller for data collector.

INITUSER

The data collector calls INITUSER during the first call from an Unicenter CA-Insight user interface. This function controls whether the user can connect to the data collector and it can alter the PROFILE name that has been assigned to the user.

If the connection is allowed, the exit can specify a new profile name from a specified list.

R15 Return Codes

■ 0—Connection is allowed

■ non-zero—Connection is disallowed

A–2 System Guide Functions by Caller - TSO User Interface

ALLCALLS

The data collector calls ALLCALLS for every call from the Unicenter CA-Insight user interface. This function controls whether the user can perform the action.

R15 Return Codes

■ 0—Function is unconditionally allowed

■ 4—Use default data collector criteria

■ else—Function is unconditionally disallowed

ALLREQS

The data collector calls ALLREQS for the following request-based functions: SHOW, DISPLAY, ADD(START), STOP, FREEZE, RESET, and RESUME. The exit controls whether these functions should be performed.

R15 Return Codes

■ 0—Function is unconditionally allowed

■ 4—Use default data collector criteria

■ > 4—Function is unconditionally disallowed

STARTREQ

The data collector calls STARTREQ during ADD(START) processing. The request to be started has already been syntax-checked and the required DB2 trace IFCIDs determined. This exit can control the start based on actual resources required.

Note: This exit point replaces the functionality of SECURITY-EXIT2 in pre-V3.0 Unicenter CA-Insight releases.

R15 Return Codes

■ 0—START is unconditionally allowed

■ 4—Use default data collector criteria

■ > 4—START is unconditionally disallowed

Functions by Caller - TSO User Interface

The following section describes the functions by caller for TSO user interfaces.

NSIGHTEX User Exit A–3 Functions by Caller - VTAM User Interface

INITTSO

The TSO user interface calls INITTSO during initialization. This exit must determine the user ID from TSO control blocks and/or the ACEE because it is not running as an authorized program.

The NSIGHTEX User Exit:

■ Could control access to the TSO user interface

■ Must specify the user ID and security group for data collector calls

■ Must specify the initial menu set for the user interface

R15 Return Codes

■ 0—Permit access

■ 4—Deny access

EXITTSO

The TSO user interface calls EXITTSO during termination. The return code in Register 15 is ignored.

Functions by Caller - VTAM User Interface

The following section describes the functions by caller for VTAM user interfaces.

LOGON

The VTAM user interface calls LOGON when a user attempts to logon. The exit is called before the user is prompted for the user ID and password. The exit is also called after the user presses ENTER on the keyboard.

This exit must be authorized to call external security packages.

The NSIGHTEX User Exit:

■ Controls access to the VTAM user interface

■ Specifies the user ID and security group for data collector calls

■ Specifies the initial menu set for the user interface

■ Ensures that the user ID is not used in multiple VTAM user interface sessions

A–4 System Guide Functions by Caller - Batch User Interface

R15 Return Codes

■ 0—Permit access

■ 4—Deny access

■ 8—User interface should prompt for user ID/password - no message returned

■ 12—User interface should prompt for user ID/password - a message is returned to place on panel and sound alarm

■ 16—User interface should prompt for user ID/password - a message is returned to place on panel but no alarm sounded

LOGOFF

The VTAM user interface calls the NSIGHTEX User Exit on termination of the user session in order to free external security package control blocks. The return code in Register 15 is ignored.

Functions by Caller - Batch User Interface

The following section describes the functions by caller for batch user interfaces.

INITBAT

The batch user interface calls INITBAT during initialization. This exit must determine the user ID from control blocks and/or the ACEE because it is not running as an authorized program.

The NSIGHTEX User Exit could:

■ Control access to the batch user interface

■ Specify the user ID and security group for data collector calls

R15 Return Codes

■ 0—Permit access

■ 4—Deny access

EXITBAT

The batch user interface calls EXITBAT during termination. The return code in Register 15 is ignored.

NSIGHTEX User Exit A–5 Modifying NSIGHTEX to Use Group Names Other Than INS* Names

Modifying NSIGHTEX to Use Group Names Other Than INS* Names

For RACF and CA-Top Secret users, you can modify the sample NSIGHTEX routine (NSGHTEXA member in the SOURCE library) to use your own security group names. There are two sections of code that need to be changed. The code sections are highlighted by a BEGIN comment: *CHANGEGROUPPREFIX CODE BEGIN

and an END comment: *CHANGEGROUPPREFIX CODE END

making up a change code block. After the BEGIN comment line, there are a set of comments that describe what the code in the change code block is doing and how you can change the code to perform as desired.

Code Segments

The two sections of code and their comments are as follows:

Note: If the code and comments in the SOURCE member are different, you should assume that the SOURCE member is more current.

Code segment 1 *CHANGEGROUPPREFIX CODE BEGIN... * THIS BLOCK OF CODE CHECKS THE USER’S GROUP NAME (PREVIOUSLY * IDENTIFIED AND SET) AND SETS THE DEFAULT DISPLAY MENU IF THE * GROUP NAME STARTS WITH INS. THE USER’S GROUP NAME IS POINTED * TO BY R2 AND THE DESIRED MENU NAME LOCATION IS POINTED TO BY * R1. IF YOU WHICH TO CHECK FOR ALTERNATE GROUP NAMES, COMPARE THE * GROUP NAME VALUE POINTED TO BY R2 (UP TO 8 CHARACTERS) AND SET * THE MENU NAME TO THE DESIRED VALUE BASED ON THE GROUP NAME. * NOTE THAT YOU DO NOT HAVE TO UPDATE THIS CODE IF YOU ARE USING * ALTERNATE GROUP NAMES. YOU CAN CONTROL THE USER’S DEFAULT MENU * BY SETTING THE VALUE IN THE SECURITY DATA SET. MVC 0(8,R1),=CL8’SYSTEM ‘ SYSTEMS? CLC 0(4,R2),=CL4’INSS’ BER R14 MVC 0(8,R1),=CL8’DBA ‘ DBAS? CLC 0(4,R2),=CL4’INSD’ BER R14 MVC 0(8,R1),=CL8’OPERATOR’ OPERATOR? CLC 0(4,R2),=CL4’INSO’ BER R14 MVC 0(8,R1),=CL8’AUDITOR ‘ AUDITIOR? CLC 0(4,R2),=CL4’INSU’ BER R14 MVC 0(8,R1),=CL8’APPLDEVL’ APPL DEVELOPER CLC 0(4,R2),=CL4’INSA’ BER R14 *CHANGEGROUPPREFIX CODE END.

A–6 System Guide Modifying NSIGHTEX to Use Group Names Other Than INS* Names

Code segment 2 *CHANGEGROUPPREFIX CODE BEGIN... * * THIS CODE BLOCK IS IN A PROCESSING LOOP LOOKING AT THE * LIST OF USER’S CONNECT GROUPS LOOKING FOR A CONNECT GROUP * THAT STARTS WITH INS. IF AND WHEN AN INS CONNECT GROUP NAME IS * FOUND, A BRANCH IS MADE TO LABEL "SAVEGOT" WHERE THE CURRENT * CONNECT GROUP NAME (CGRPNAME) IS SET AS THE USER’S DEFAULT * GROUP THAT CA-INSIGHT WILL USE TO CHECK SECURITY. * VARIABLE UPLGROUA CONTAINS THE ADDRESS OF THE USER’S DESIRED * GROUP NAME WHICH YOU MAY UPDATE (8 BYTES). * IF YOU WISH TO LOOK FOR GROUP NAMES OTHER THAN ONE THAT STARTS * WITH INS, YOU SHOULD CHECK THE CGRPNAME (CONNECT GROUP NAME) * FIELD FOR A DESIRED CONNECT GROUP NAME. IF ONE IS FOUND * YOU SHOULD BRANCH TO LABEL "SAVEGOT" IF YOU WANT TO USE * THE CGRPNAME ASIS. OTHERWISE, YOU SHOULD SET THE GROUP NAME * (AREA POINTED TO BY UPLGROUA) TO THE DESIRED VALUE AND * BRANCH TO LABEL "SAVEEXIT" TO RETURN FROM THIS SECTION OF * CODE. IF YOU DESIRE, YOU MAY ALSO SET THE GROUP NAME * BASED ON THE USER ID (IN FIELD ACEEUSRI). HOWEVER, UNLESS * YOUR COMPANY’S USER IDS ARE SOMEHOW GENERICALLY ASSIGNED * OR CAN BE GENERICALLY CHECKED, YOU WILL NEED TO RECODE THIS EXIT * WHEN YOU WANT TO CHANGE THE LIST OF USER ID’S BEING CHECKED. * IF YOU DO THIS, YOU SHOULD ADD CODE TO CHECK FOR USER IDS * AFTER LABEL "CKCGRP" ABOVE AND BRANCH TO LABEL "SAVEEXIT" TO * RETURN FROM THIS SECTION OF CODE. * CLC CGRPNAME(3),=CL3’INS’ IS IT FOR CA-INSIGHT? @V51038 BE SAVEGOT *CHANGEGROUPPREFIX CODE END.

Note: If you are using connect group names, you must leave the &NOCGRP variable setting to 0 (&NOCGRP SETB 0 ) and assemble with the CGRP macro. This is the default settings.

Once you have modified the exit and successfully assembled and linked the NSIGHTEX module, you should update the security file to use the group names as intended by the changes made to the exit.

NSIGHTEX User Exit A–7

Appendix B Data Collector Storage

This appendix describes the factors that determine how much virtual storage and fixed real storage the data collector requires in a given execution.

Data Collector Virtual Storage Requirements

Data collector virtual storage requirements in the address space at any point during execution depend on the factors shown here:

Item Storage Code 1522K Globals and main stack 28K Subtask stack (8 * 24K) + (NUMUTSKS * 24K) Request, file control blocks 2K each Output buffers (per file) 2 * blksize Basic Summary Table: (12 * y) / 0.86 (one per active SUMMARIZE) n * (k + f) Index Data (If INTERVAL is specified, two data areas are required) Monitor Table NINTERVAL * f (one per active MONITOR) Trace Table NEVENTS * f (one per active TRACE) Record ID Table 16K User ID Table 216K Hashed Symbol Table 100K

Data Collector Storage B–1 Common Area Storage Requirements

Item Storage SRV Private Area Buffers (SRVBUFSZ * 4 * PRVBUFNUM) K <= PRVMAXSZ IFI Private Area Buffers (SRVBUFSZ * 4 * SRVBUFNUM * 2) <=PRVMAXSZx User Interface Buffer 22K (one per user)

The variable symbols used in the previous table are defined as:

■ n— number of entries in table (one per unique combination of GROUP BY values)

■ y—next power of 2 greater than n

■ k—key length (combined lengths of GROUP BY fields)

■ f— field lengths of fields and functions

Common Area Storage Requirements

The storage listed here, broken out by Unicenter CA-Insight component, are the amounts and locations of common area storage used by Unicenter CA-Insight:

For PCOWNER

For PC OWNER address space:

Description Amount Subpool Location SSCT Control Block 40 241 CSA PCTA Control Block 136 245 SQA PC Number Table 28 245 SQA PC DB2 Table 40 + 241 ECSA (288 * number of DB2s)

B–2 System Guide Common Area Storage Requirements

Description Amount Subpool Location NXCMSROM program 7688 241 ECSA code Tables for NATURAL ((ASVTMAXU + 1) * 16) + (DB2 241 ECSA information maxthreads * 4 * 64) + 48) (if rounded up to 4K boundary NATURAL-DB2=YES)

For Data Collector

For data collector (per each data collector):

Description Amount Subpool Location DCCOMM Control 280 241 CSA Block Fixed Stats Area 128 228 ECSA Save Area for 72 241 ECSA - CALLRTM trans SRB Control Block 44 245 SQA - trans ITFB Control Block - 664 241 ECSA 1/connected user DBDCOMM Control 1616 227 CSA Block (SRV) NXSRBROM program 19568 241 ECSA code NXSRVSRM program 1784 241 ECSA code (SRV) DSNWVSER program 2264 241 ECSA code (SRV) VTAM used by 128 227 CSA ISTORMVA (RAF) CSACICAR Control 208 241 ECSA Block - 1/each NUMUTASKS SRV or OPx (IFI) (SRVBUFSZ * 4 * 241 ECSA Buffers SRVBUFNUM)K

Data Collector Storage B–3 Output Buffers

For the User Interface

For user interface:

Description Amount Subpool Location INSCOMM Control 640 241 ECSA Block - 1/connected user VTAM used by 128 227 CSA ISTORMVA

Total below the 16M line usage of common storage by Unicenter CA-Insight for the PC Owner and one data collector without using SRV is 484 bytes. The trans values in the location fields in the tables on the previous page indicate that this is transient storage usage. If RAF and/or the VTAM user interface are used, add 128 bytes of below-the-line usage for each area used by VTAM.

Memory Planning

A simple guideline for planning purposes is that 1000K bytes should be considered the minimum practical amount of virtual storage for a modest number of requests, while 2000K bytes is usually adequate for what most sites typically wish to do.

Factors

Aside from the basic storage requirement, the amount of space required for execution will depend mostly on:

■ The number of output files and the blocksizes of these files

■ The number of active SUMMARIZE requests

■ The number and lengths of entries built in the tables constructed for each request

Output Buffers

The following section discusses the output buffers.

If no blocksizes are specified in the JCL, output blocksizes default to 4096.

B–4 System Guide SUMMARIZE Request Table Sizes

Should They Be Larger?

Evaluate blocksize against the number of records that will be written to the file. The following general guidelines apply:

■ Relatively few records are written for SUMMARIZE requests, so blocksize is usually unimportant.

■ TRACE requests could write large amounts of trace records, so large blocksizes can be very important.

When you have larger block sizes, you also have increased use of virtual storage. In virtual storage systems, this is usually a small price to pay, particularly when creating sequential file. Since the data is being added to the buffer sequentially (rather than randomly), the impact on paging will be negligible.

Note: In fact, large blocksizes will improve overall system performance by reducing the amount of time spent executing access method code and by reducing device contention.

SUMMARIZE Request Table Sizes

One virtual storage summary table is maintained for each active SUMMARIZE request. An additional data portion of the summary table, equal in size to the first, will be maintained if the request includes the INTERVAL parameter.

Summary Table Entries

Before executing new summary requests, make a rough estimate of the space required.

Entry Size

The size of each entry is the total of the lengths of the accumulators for each summary field or function, plus the combined lengths of the break (GROUP BY) fields. Additional space is required for pointers, counters, and so on

Data Collector Storage B–5 SUMMARIZE Request Table Sizes

Allocation

Space is allocated for each summary table when the request is activated. If the initial allocation is exceeded, the table size will be increased if enough virtual storage is available; otherwise, an implicit RESET will occur (data in the table will be output, then all accumulators will be reset to zero and processing will continue).

Deallocation

The space occupied by a table is released (and is available for reuse) when the request is deleted. PAUSE commands do not release tables.

RESET will reset the table size to the original allocation, or 20K, whichever is greater.

To Check Table Sizes

The size of the table increases directly in relation to the number of unique values contained in the GROUPed BY fields.

B–6 System Guide Appendix C Shadow Table for EXPLAIN

Several new features requiring retrieval from the DB2 catalog were introduced with Unicenter CA-Insight V4.1. These features included the display of all DBRMs and packages contained in a plan, the retrieval of SQLtext based on a DBRM name and statement number, and the displaying of index information for indexes used in access paths chosen by the optimizer. This appendix describes the use of Shadow Tables to greatly improve the speed of these functions.

Using Shadow Tables

A Shadow Table is a user-defined copy of a DB2 catalog table. To improve the performance of retrieval of information from the DB2 catalog, such as SQL text and data describing information about DBRMs and indexes, the Unicenter CA-Insight EXPLAIN plan can be bound to user copies of DB2 catalog tables.

Note: Starting with DB2 Version 4, you can create indexes on catalog tables. As an alternative to using shadow catalog tables, you might want to use indexed catalog tables.

Typically, a user of DB2 would create “shadow tables” when there would be a need to retrieve specific data from the DB2 catalog utilizing an index. In the case of the Unicenter CA-Insight Explain plan, there are 3 unindexed DB2 catalog tables which can be copied and indexed to improve performance. The tables are:

■ SYSIBM.SYSSTMT—Contains all the SQL text in a DBRM (Database Request Module)

■ SYSIBM.SYSDBRM—Contains all pertinent information that describes a DBRM

■ SYSIBM.SYSKEYS—Contains information describing columns contained in an index

Shadow Table for EXPLAIN C–1 Using Shadow Tables

Advantages

The major advantage of using Shadow Tables for DB2 catalog information retrieval is that the user can avoid repeated tablespace scans of DSNDB06.SYSPLAN, and in the case of the GETSTATS function, DSNDB06.SYSDBASE.

Repeated scanning of DSNDB06.SYSPLAN could conceivably cause locking problems with concurrent BINDing and FREEing of plans. Scanning of DSNDB06.SYSDBASE could be impacted by the creating, altering, and dropping of DB2 objects.

The performance degradation that you can incur if you do not use Shadow Tables is directly related to the size and fragmentation of all the DB2 catalog tables contained in table spaces DSNDB06.SYSDBASE and DSNDB06.SYSPLAN.

Disadvantages

A problem with using Shadow Tables is that several things can cause their data to become out of synch with the DB2 catalog: 1. If SQL is rewritten, or new SQL is added to existing programs, once a plan is rebound, the data contained in SYSIBM.SYSSTMT and SYSIBM.SYSDBRM is updated. For example, if the SQL contained in a program is changed, what was once Statement 100 can now be Statement 105. 2. If index definitions are changed, or indexes are added or dropped, the information contained in SYSIBM.SYSKEYS will change.

To keep the tables synchronized, you can run a Unicenter CA-Insight unload/load job daily (or as needed). This is described in Keeping Shadow Tables Synchronized.

C–2 System Guide EXPLAIN Plan

EXPLAIN Plan

All references to DB2 catalog tables in the EXPLAIN plan are unqualified, so if your shop already has Shadow catalog tables, you can simply use the qualifier for these tables. To do this simply edit the NUXPLANU member in the SPFSLIB and change the qualifier as per the comments in this member. Then regenerate the BIND statements and rebind the Unicenter CA-Insight plans.

All of the following catalog tables need to be shadowed or have synonyms owned by the binder of the Unicenter CA-Insight plan in order for the BIND of the plan to be successful. (The db2ssidUSRQ DDL member in the SOURCE library does this for you). SYSIBM.SYSDBRM Should be shadowed by an indexed table SYSIBM.SYSKEYS Should be shadowed by an indexed table SYSIBM.SYSSTMT Should be shadowed by an indexed table SYSIBM.SYSCOLUMNS Optionally shadow or create synonym or alias SYSIBM.SYSINDEXES Optionally shadow or create synonym or alias SYSIBM.SYSPACKAGE Optionally shadow or create synonym or alias SYSIBM.SYSPACKLIST Optionally shadow or create synonym or alias SYSIBM.SYSPACKSTMT Optionally shadow or create synonym or alias SYSIBM.SYSPLAN Optionally shadow or create synonym or alias SYSIBM.SYSSYNONYMS Optionally shadow or create synonym or alias SYSIBM.SYSTABLES Optionally shadow or create synonym or alias SYSIBM.SYSTABLESPACE Optionally shadow or create synonym or alias

Shadow Table for EXPLAIN C–3 Creating Shadow Tables

When Is EXPLAIN Using Shadow Tables?

Whenever users invoke functions that would cause Unicenter CA-Insight to read the Shadow Tables, they will receive the following message in the user interface: DBG55136I Catalog data retrieved from tables using qualfier xxxxxxxx.

Use PF1 (Help) to get a more detailed explanation of the message, if necessary.

Creating Shadow Tables

If your shop is not currently using Shadow Tables, you must first create indexed Shadow Tables in each DB2 subsystem you are monitoring with Unicenter CA-Insight. DDL to create indexed copies of SYSIBM.SYSSTMT, SYSIBM.SYSKEYS, and SYSIBM.SYSDBRM is provided in member db2ssidUSRQ in the SOURCE library. This member also contains DDL to create synonyms for the other DB2 catalog tables that are used by the EXPLAIN feature. The purpose of the synonyms is to allow resolution of unqualified table names contained in the SQL of the EXPLAIN plan.

The second step is to populate the Shadow Tables and REBIND the EXPLAIN plan to them. This function is provided in member db2ssidSSJ in the SOURCE library.

You can execute these steps as described in Creating and Using Shadow Catalog Tables in the “Installing Optional Components” chapter

C–4 System Guide Keeping Shadow Tables Synchronized

Keeping Shadow Tables Synchronized

As stated before, there are several things that can happen to cause the data contained in the Shadow Tables to become out of synch with the DB2 catalog. These things are:

■ Changing of SQL text followed by a BIND of a PLAN. This will change data in both SYSIBM.SYSDBRM, and SYSIBM.SYSSTMT.

■ Adding or removing DBRMs from a PLAN. This will change data in SYSIBM.SYSDBRM.

■ Adding, dropping or changing DB2 indexes. Also dropping tables with indexes or table spaces containing tables in indexes. This will change data in SYSIBM.SYSKEYS.

We recommend that you if decide to implement the three shadow tables provided with Unicenter CA-Insight, that you set up db2ssidSSJ as a scheduled job. The scheduling of this job should be based on how frequently SQL contained in DBRMs is changed, how often DBRMs are added or removed from plans, and how often indexes are changed.

Typically, in a test environment, BINDs and index changes are frequent, while in a production environment, the opposite is usually true. In the test environment, it would be advisable to run db2ssidSSJ at least nightly. Ideally in your production environment, you would want to include the execution of db2ssidSSJ at the end of your production migration procedure. This would ensure that the data contained in the shadow catalogs is always current.

If shadow tables are not synchronized with the DB2 catalog, some potential problems are the retrieval of incorrect SQL text for static SQL, erroneous displays of PLAN/DBRM lists, and outdated or incorrect information displayed by the GETSTATS function of Unicenter CA-Insight.

Shadow Table for EXPLAIN C–5

Appendix D Utilities

This appendix describes the five Unicenter CA-Insight utilities: OBID Translation, Load Statement Generator, Request Case Converter, Online History Data Set Unload, the ILOG to Data Set Dump, and 24X7.

OBID Translation Utility (IDB2OBI)

The trace records generated by DB2 do not contain translations of DBIDs and OBIDs for objects stored in segmented tablespaces. The IDB2OBI Utility extracts these translations from the DB2 catalog and stores them in a sequential file. The data collector reads the OBIDTBL file when it is started and whenever the OBID command is executed from the Unicenter CA-Insight user interface.

During the installation process you created and loaded the OBID table for the DB2 subsystem for which you did the initial Unicenter CA-Insight installation. The information provided here is to support subsequent runs of the IDB2OBI job to update the OBID table, such as when DB2 tables are created or dropped.

Requirements

The DB2 subsystem must be started before running this job, and the following catalog tables must be available for read access:

■ SYSIBM.SYSTABLES

■ SYSIBM.SYSTABLESPACE

■ SYSIBM.SYSTABLEPART

■ SYSIBM.SYSINDEXES

■ SYSIBM.SYSINDEXPART

Ensure that plan IDB2OBI is bound for the DB2 subsystem you intend to extract data from.

Important! If you run this job while the data collector is active, you must inform the data collector that the OBID table has been updated. Do this by issuing the “OBID” command from the TSO or VTAM user interface.

Utilities D–1 OBID Translation Utility (IDB2OBI)

Format of the OBID Record

The OBID record’s fields are described in the following, in the order in which they appear. DBID Database identifier. OBID or ISOBID Object identifier for table spaces, tables, and indexes or object identifier for index spaces. DBNAME or CREATOR Database name for page sets, or creator name for tables and indexes. Name Name of table, index, or page set. Object Type Abbreviations used to indicate object type:

■ T—Table

■ P—Page set

■ I—Index High-level qualifier The data set high-level qualifier is used for page sets, otherwise this field is blank. Partitions The number of partitions is included for page sets, otherwise this field is blank. I or J Indicates which pageset data set the DB2 subsystem is currently using, the I or J copy. This mainly applies to DB2 V7 or higher. For earlier releases of DB2, the value will default to I.

D–2 System Guide Load Statement Generator (NSIGHTRW)

Db2ssidOBLD: OBID Translation JCL

A sample jobstream for the IDB2OBI Utility is provided in member db2ssidOBLD (shown here) in the SOURCE library.

If running in a data sharing environment, include the following parameter in the PARM field to share the same OBID translation file with all members of a DB22 data sharing group: =GROUP-db2group

where db2group is the name of your DB2 data sharing group.

Note: If plan IDB2OBI was bound using a different plan name, then change the IDB2OBI value to that name in the =PLAN=IDB2OBI parameter in the JCL. jobcard1 jobcard2 //STEP1 EXEC PGM=IDB2OBI,REGION=1M, // PARM=‘=UPPER=NO =PLAN=IDB2OBI =SSID=db2name’ //STEPLIB DD DISP=SHR, DB2 LOAD LIBRARY DSN=db2load, // DD DISP=SHR, CA-INSIGHT LOAD LIBRARY // DSN=apfload //OBIDTBL DD DISP=SHR, OBID TRANSLATIONS // DSN=hlq.mlq.db2name.OBID //SYSPRINT DD SYSOUT=* //SYSTERM DD SYSOUT=* //

Load Statement Generator (NSIGHTRW)

The Load Statement Generator is a Unicenter CA-Insight utility that enables you to store DB2 performance data into DB2 tables. It does this by analyzing a Unicenter CA-Insight request and creating the DB2 CREATE TABLE and Load Utility Control statements that would match an OUTFILE produced by the request.

Utilities D–3 Load Statement Generator (NSIGHTRW)

The actual flow of using the Load Statement Generator would be as follows: 1. Create or edit an IQL request containing an OUTFILE statement. 2. Use that IQL request as input to the Load Statement generator. 3. The IQL request is evaluated. Based on the structure of the output fields, the appropriate SQL and Load Utility DCL statements are generated. 4. Create the DB2 table using the generated SQL statements. 5. Run the IQL request in batch or online environments to create the output data in the OUTFILE. 6. Use that OUTFILE as input (along with the generated Load Utility DCL statements) to load the records into the DB2 table.

Requirements

You must provide the following:

■ Sufficient virtual storage for processing the desired request

■ Sufficient DASD storage (approximately four tracks) for the two output files

Input and Output

The Load Statement Generator is submitted as a batch job whose input file is the IQL request to be analyzed. The output is a system message file (DBGPRINT), a file containing an SQL CREATE TABLE statement (DBGDDL), and a file containing DB2 Load Utility control statements (DBGLOAD).

Operation

The Load Statement Generator is actually a module of the Unicenter CA-Insight Report Writer program (NSIGHTRW). It is activated when you specify LOAD=YES on the EXEC statement that invokes the program.

The Load Statement Generator reads the request file to determine the layout of the output file. Then, a CREATE TABLE statement is generated with one column for each field in the request. Finally, the Load Utility control statements that define the format of the output file are generated.

D–4 System Guide Load Statement Generator (NSIGHTRW)

Generated Statements

The following considerations apply to the generated SQL and Load statements:

■ The DB2 table name used is the name of the Unicenter CA-Insight request. You might want to change the table name in both files.

■ The column names are derived from the Unicenter CA-Insight field names. Hyphens in the field names are translated into underscores (_) in the DB2 column names. If the field name is longer than 18 characters, it is truncated to 18 characters. If the truncated field was also a repeating group field, then the column name will have an asterisk (*) appended to it in position 19, making it an illegal column name. This is an indication that you must edit the column name in both files.

■ Literal values in the field list, as you might use in a report that is not column-formatted, are translated into column names of the form ‘ERR_nn’, where nn is a sequence number incremented by one for each such field.

■ Summary function fields, like AVG(LOCK-WAIT-DB2), are translated into column names of the form AVG_LOCK_WAIT_DB2, where the function abbreviation becomes part of the column name. If the function operates on multiple fields, then the generated column name includes only the first field name used in the function.

Input Parameter

The contents of this input parameter file should be a valid set of batch report writer parameters. The parameters specified will not affect the generation of the DDL and load statements, but they must be syntactically correct. The IDRWPRMS member of the SOURCE library can be used, by default.

IDB2LSJ: Load Statement Generator JCL

A sample jobstream for the Load Statement Generator is provided in member IDB2LSJ (shown here) in the SOURCE library.

You will need to supply the IQL request name in the reqname field (if the request library is not the standard-format Unicenter CA-Insight REQUESTS library, also change the DSN).

Utilities D–5 Load Statement Generator (NSIGHTRW)

Un-comment the Step 1 statements to delete the two data sets if they have already been created. jobcard1 jobcard2 //* //*STEP1 EXEC PGM=IEFBR14 //*DB2LOAD DD DISP=(OLD,DELETE),DSN=hlq.mlq.DB2LOAD //*DB2DDL DD DISP=(OLD,DELETE),DSN=hlq.mlq.DB2DDL //* //STEP2 EXEC PGM=NSIGHTRW,REGION=4096K,PARM=‘LOAD=YES’ //STEPLIB DD DISP=SHR, CA-Insight LOAD LIBRARY // DSN=apfdsn //SYSPARMS DD DISP=SHR, // DSN=hlq.mlq.SOURCE(parmfile) //* //DBGIN DD DISP=SHR, INPUT REQUEST FILE // DSN=hlq.mlq.REQUESTS(reqname) //* //* DBGLOAD AND DBGDDL ARE THE OUTPUT DATASETS //* //DBGLOAD DD DSN=hlq.mlq.DBGLOAD, // DISP=(,CATLG,DELETE),SPACE=(TRK,(1,1),RLSE), // UNIT=diskunit,DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //* //DBGDDL DD DSN=hlq.mlq.DBGDDL, // DISP=(,CATLG,DELETE),SPACE=(TRK,(1,1),RLSE), // UNIT=diskunit,DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //* //DB2DDN DD DUMMY //DBGPRINT DD SYSOUT=* //

JCL Explanation

The following describes the fields in the previous sample JCL: jobcard1 (Required) Contains a jobname and other parameters according to your conventions regarding installation job naming and JOB card parameter specification. jobcard2 (Optional) Must be included if specified in your Unicenter CA-Insight Installation worksheet. //STEP1 (Optional) Invokes the IEFBR14 utility to delete the Load Statement data sets if previously defined. Un-comment this and the following two statements to execute this step. //DB2LOAD (Optional) Specifies the data set that contains previously generated Load Utility control statements. See the comment in #2. //DB2DDL (Optional) Specifies the data set that contains previously generated CREATE TABLE statements. See the comment in #2.

D–6 System Guide Request Case Converter (NALLCAPS)

//STEP2 EXEC (Required) Invokes the Unicenter CA-Insight Report Writer program (NSIGHTRW). PARM=‘LOAD=YES’ (Required) Invokes the Load Statement Generator module of the Unicenter CA-Insight Report Writer program. //STEPLIB is normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules. //SYSPARMS (Required) Points to data collector (or Report Writer) initialization parameters. //DBGIN (Required) Points to the Unicenter CA-Insight Request file that contains the member specified in reqname. //DBGLOAD (Required) Names the data set that will contain the generated Load Utility control statements. //DBGDDL (Required) Names the data set that will contain the generated CREATE TABLE statements. //DB2DDN (Required) Must be “dummied” out. //DBGPRINT (Required) Points to the destination for the Report Writer system messages file. If a permanently allocated data set is specified with a disposition of SHR, and enough space is allocated for anticipated message traffic, it can be BROWSEd from TSO during execution.

Request Case Converter (NALLCAPS)

Requests are now converted to uppercase as an optional step in the post install process. To convert the IQL requests to upper case, you should run the system- wide post install to generate the JCL to convert the requests to upper case.

Requirements

The only requirement is that you have enough DASD storage for the new REQUESTS file (created in Step 2).

Utilities D–7 Request Case Converter (NALLCAPS)

IDB2UCJ: Request Converter JCL

A sample jobstream for the Request Case Converter is provided in member IDB2UCJ (shown here) in the SOURCE library.

Use the IDEDIT macro to change the jobcard1, jobcard2, hlq, mlq, apfdsn, prodvol, and diskunit values in the jobstream with the values supplied on the Unicenter CA-Insight Installation Worksheet in the “Beyond the Basic Installation” chapter. jobcard1 jobcard2 //* //* //STEP1 EXEC PGM=NALLCAPS //* //STEPLIB DD DISP=SHR, DB2 LOAD LIBRARY // DSN=apfdsn //* //SYSLIB DD DISP=SHR, CA-INSIGHT IQL REQUEST LIBRARY // DSN=hlq.mlq.REQUESTS //* //SYSUT2 DD DSN=&UPPER, OUTPUT IDBUPDTE STREAM // DISP=(NEW,PASS), // UNIT=SYSDA,SPACE=(CYL,(2,1),RLSE), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=23440) //* //STEP2 EXEC PGM=IEBUPDTE,PARM=NEW //SYSPRINT DD SYSOUT=* //SYSIN DD DSN=&UPPER,DISP=(OLD,DELETE),UNIT=SYSDA //* //SYSLIB DD DISP=(,CATLG,DELETE), NEW IQL REQUEST LIBRARY // DSN=hlq.mlq.NEW.REQUESTS, // VOL=SER=prodvol,SPACE=(3120,(500,50,40)), // UNIT=diskunit,DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //

JCL Explanation

The following describes the fields in the previous sample JCL: jobcard1 (Required) Contains a jobname and other parameters according to your conventions regarding installation job naming and JOB card parameter specification. jobcard2 Optional, but must be included if specified in your Unicenter CA-Insight Installation worksheet. //STEP1 EXEC (Required) This statement invokes the Unicenter CA-Insight Request Case Converter program (NALLCAPS). //STEPLIB Normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement describes the authorized library containing the load modules.

D–8 System Guide Online History Data Set Unload (IDB2UNLD)

//SYSLIB (Required) Points to the Unicenter CA-Insight Request library. //SYSUT2 (Required) Creates a temporary data set that contains the case-converted Request library. This is used as input to the next step. //STEP2 EXEC (Required) This statement executes the IEBUPDTE utility which creates a partitioned data set containing source data.

■ PARM=NEW is required. This indicates to the utility that a new data set it to be created. //SYSPRINT (Required) Prints system messages. //SYSIN (Required) Points to the temporary data set specified in #5. //SYSLIB (Required) This statement specifies the new IQL Request Library to create.

Change Members to Use New Request Library

Once you have converted the requests and created the new library, you must change the following members to point to the new library:

■ IDDCPRMS—Change the REQLIB= statement to point to the new library

■ IDB2RWJ—Change the DSN in the DBGIN DD statements

■ IDB2VUS—Change the DSN in the REQUESTS DD statement (VTAM user interface users only)

■ IDB2BUJ1, IDB2BUJ2, IDB2BUJ3—Change the DSN in the REQUESTS DD statement (batch user interface users only)

Online History Data Set Unload (IDB2UNLD)

The Online History Data Set Unload utility is used to unload the Online History VSAM data sets to a sequential file in SMF format. This file can be used as input to the Batch Report Writer, MICS or SAS chargeback routines, and the Unicenter CA-Insight DB2 Archive component (see the “Online History” chapter for details).

When the IDB2UNLD job is executed, it unloads data from both the HSTSTATx and HSTACCTx files. The data is processed such that all system interval and thread accounting records written since the last unload are written out. This gives you a complete set of performance data synchronized for one time period.

Utilities D–9 Online History Data Set Unload (IDB2UNLD)

Requirements

The data collector must be active in order for IDB2UNLD to execute properly.

IDUNLJCL: Online History Data Set Unload JCL

The Online History Data Set Unload utility is run as a proc, and can be found as member IDUNLJCL (shown here) in the SOURCE library.

Note: No DD statements for the Online History files being unloaded are required because IDB2UNLD dynamically allocates the correct files. //IDB2UNLJCL PROC DBSUB=db2name, // DBLOC=‘DB2LOCATION1’, // REMEMBR=YES, // TESTVER=TESTV, // UNLOAD=NEW, // UNLDCHD=YES, // UNLDTYP=ALL //* //S01 EXEC PGM=IDB2UNLD,REGION=5M,TIME=1440, // PARM=(‘DBSUB=&DBSUB,DBLOC=(&DBLOC),’, // ‘REMEMBER-POS=&REMEMBR,TESTVER=&TESTVER,’, // ‘UNLOAD=&UNLOAD,UNLOAD-TYPE=&UNLDTYP,’,’ // ‘UNLOAD-CHLD=&UNLDCHD’) //* //STEPLIB DD DISP=SHR, CA-INSIGHT Load Library // DSN=apfdsn //* //SMFOUT DD DISP=(,CATLG,DELETE), Online History Archive // DSN=hlq.mlq.&DBSUB..ARCHIVE(+1), // UNIT=diskunit,SPACE=(CYL,(10,10)),VOL=SER=prodvol, // DCB=(MODEL.DSCB,RECFM=VBS,LRECL=32760,BLKSIZE=4096) //* //DBGPRINT DD SYSOUT=X //SYSUDUMP DD SYSOUT=X //SYSPARMS DD DUMMY

JCL Explanation

The following describes the fields in the previous sample JCL: //IDUNLJCL (Required) Provides values for the symbolic parameters that are used by IDB2UNLD. The parameters are as follows:

■ The DBSUB symbolic parameter specifies the DB2 subsystem name.

■ The DBLOC parameter specifies the DB2 location and is used with the DBSUB and TESTVER parameters to identify the data collector owning the Online History data sets. The DB2 location must be enclosed within single quotes (‘ ‘).

D–10 System Guide Online History Data Set Unload (IDB2UNLD)

■ The REMEMBR symbolic parameter gives you the option of keeping track of the last record unloaded using this job. The default value of YES means that the position of the last record unloaded will be maintained in the History Control File specified by the HSTPARMS DD statement in the data collector JCL (described in the “Operation and Customization” chapter. A value of NO means that the last unloaded record will not be tracked.

■ The TESTVER parameter is used with the DBSUB and DBLOC parameters to identify the data collector owning the Online History data sets. It specifies the unique 1-4 character ID of the data collector that is being run on the DB2 subsystem specified in DBSUB at the location specified in DBLOC.

■ The UNLOAD symbolic parameter tells IDB2UNLD which type of unload to perform. If you specify NEW (default), only those Online History records added since the last unload will be written to the sequential data set. (This will only work if you specified REMEMBR=YES on the previous IDB2UNLD run). Specify ALL to unload all records from the Online History data sets to the sequential file.

■ The UNLDCHD symbolic parameter tells IDB2UNLD whether to unload the parent and children CPU Parallelism thread accounting records or unload just the summary record for these threads. YES (default) unloads the parent and children, while NO unloads only the summary accounting record. This parameter should be set with the setting of HIST-CPUPARA-CHILD parameter in SYSPARMS.

■ Finally, the UNLDTYP parameter is used to control which types of Online History records will get written to the sequential data set. You can specify ACCTG to unload only Thread Accounting History records, STAT to unload only Accounting Statistics History records, or the default ALL to unload all Online History records. //S01 (Required) Invokes the IDB2UNLD program, specifies the region size and an unlimited runtime. The run-time parameters are configured through the symbolic parameter values previously described. You can specify the run-time parameters in the PARM field using the short form of the names. You can also specify the run-time parameters in the SYSPARMS DD statement, using the long or short forms of the names. See the description for //SYSPARMS, at the end of this list. //STEPLIB Normally required unless the library containing the Unicenter CA-Insight load modules is part of the LINKLIB concatenation. This statement specifies the authorized library containing the load modules.

Utilities D–11 Online History Data Set Unload (IDB2UNLD)

//SMFOUT (Required) Specifies the sequential data set where the unloaded Online History records will be written. It is set up as a GDG so you can see previous versions of saved SMF-format Online History records. Use the db2ssidGDG member in the SOURCE library to create a base GDG definition for IDUNLJCL. //DBGPRINT (Required) Points to the destination for the IDB2UNLD messages file. //SYSUDUMP (Optional) Points to a destination for any abend dumps which can occur during execution. //SYSPARMS (Optional) You can specify the run-time parameters in the SYSPARMS DD. Any parameters specified in the PARM parameter of the EXEC statement will override parameters specified in the SYSPARMS DD statement. You can use the long or short forms of the names as follows:

Short Name Long Name UNLD UNLOAD TSTV TESTVER UNLCHD UNLOAD-CHILD UNLTYP UNLOAD-TYPE REMPOS REMEMBER-POS DBLOC DB2-LOCATION

For example: //SYSPARMS DD * DEFAULTS DB SUB=DB2E DB LOC=DB2ESP RE MEMBER-POS=YES UN LOAD=NEW UN LOAD-TYPE=ALL UN LOAD-CHLD=YES ;

D–12 System Guide Dump ILOG to a Data Set (GSSIDUMP)

Dump ILOG to a Data Set (GSSIDUMP)

The following section discusses DUMP ILOG to a Data Set.

Description

GSSIDUMP is used to dump the Unicenter CA-Insight messages ILOG to a data set.

How It Works

The job, as shipped in the SOURCE library, consists of two steps: 1. Allocates the dump data set. The DCB for the data set must be: DCB=(DSORG=PS,RECFM=FB,LRECL=1024,BLKSIZE=1028) 2. The second step is to execute a program which causes the Unicenter CA-Insight Message Handler to unload the messages ILOG. The SYSIN input identifies each ILOG subfile to be dumped. The format of the input is: CA-INSIGHT,dsn,log#,ilog subfile

Example

These two lines will dump the first two subfiles of the first ILOG(as defined by the GSSILOG job): CA-Insight,GSW.DSNA.DUMP1#0,1,0 CA-Insight,GSW.DSNA.DUMP1#1,1,1

Utilities D–13 Unicenter CA-24X7

Unicenter CA-24X7

The following section discusses the Unicenter CA-24X7 utility.

Purpose

Unicenter CA-24X7 is a utility that lets you:

■ Dynamically change DB2’s startup parameters (ZPARMS)

■ Cancel DB2 threads

■ Add/delete active log data sets

■ Free database page sets of all users

■ Refresh User Exit routines

Using a small jobstream, you submit control statements to the Unicenter CA-24X7 program, which performs a syntax check on the statements. If all of the statements successfully pass the check, the statements are processed by Unicenter CA-24X7. The actions are performed on the specified DB2 subsystems. Output messages are generated, including a reporting of each action taken by Unicenter CA-24X7.

The Batch Utility runs independently of CA-Insight. You can also run the online version of Unicenter CA-24X7 from the CA-Insight panels.

Sample JCL

Sample JCL to run Unicenter CA-24X7 is shown here: 1. //jobcard 2. //STEP1 EXEC PGM=UDBBATCH 3. //STEPLIB DD DISP=SHR,DSN=UDB24X7.LOAD 4. //UDBIN DD * 5. DEFAULTS DB2(DBV5) 6. SET ABIND ENABLED 7. SET AUTH ENABLED 8. /* 9. //UDBOUT DD SYSOUT=*

D–14 System Guide Unicenter CA-24X7

JCL Explanation 1. Jobcard 2. Step Card 3. Step Lib 4. Unicenter CA-24X7 input file DD statement 5. DEFAULTS Statement (described in The DEFAULTS Statement) 6. SET Statement (described in The SET Statement) 7. SET Statement 8. End of input delimiter 9. Unicenter CA-24X7 output file DD statement

The DEFAULTS Statement

The DEFAULTS statement specifies runtime parameters to Unicenter CA-24X7.

You can use multiple DEFAULTS statements in the input stream to reset the default DB2 subsystem ID for subsequent statements to use.

Syntax

The syntax for the DEFAULTS statement is: DEFAULTS [DB2(ssid)]

where:

ssid is the DB2 subsystem ID. If you do not specify the DB2 parameter, Unicenter CA-24X7 will default to the subsystem ID on the individual commands (the SET statement, described on the next page). If the subsystem ID is not specified in the DEFAULTS or the SET statement, then a syntax error is generated.

Example

A typical DEFAULTS statement will look like this: DEFAULTS DB2(DBV5)

Utilities D–15 Unicenter CA-24X7

The SET Statement

The SET statement performs the Unicenter CA-24X7 functions. At least one statement is required.

Syntax

The syntax for the SET statement is: [SET] command command-operand [FOR(ssid)]

where:

■ command identifies the function being requested. This is the same as the ZPARM macro operand when possible.

■ command-operand identifies the specifics of the function.

■ ssid identifies the DB2 subsystem that is the target of the requested action. This parameter is required if the DB2 ssid is not specified on a DEFAULTS statement (described on the previous page). If no ssid is specified on the SET statement, it will default to the most recent DEFAULTS ssid value. If the ssid is specified in neither the DEFAULTS or SET statements, then an error message is generated.

A table of commands and their related operand is shown starting on the next page.

Example

A typical SET statement will look like this: SET AUTH ENABLED

or like this: SET BPSIZE BPID(BP32K) VALUE(+15%)

A Note About Commands and Command-Operands

In the table shown in this chapter, the following conventions are used:

■ In the Operands column, available keywords are shown in UPPERCASE, BOLDFACE type (such as YES, COPY, BP).

■ Variables are shown in lowercase, italicized type (such as value, days)

■ If you have a choice of value to enter, they are separated by a vertical pipe (|). Select only one of the listed values.

■ Optional items are enclosed in brackets (such as [CONN(connection)])

D–16 System Guide Unicenter CA-24X7

■ Any numeric value can be represented in K (for example, 8K = 8192)

■ Use the BLANKS keyword for character operand data to have a desired value set to blanks.

SET Statement Commands and Operands

This table lists the commands that can be used with the SET statement:

Command Description Operands

ABEXP Controls whether EXPLAIN is ■ YES—Specifies that EXPLAIN during autobind ENABLE during autobind. is to be ENABLE (can also be specified as ON or Note: This command does not ENABLE) apply to DB2 V2.3. ■ NO—Specifies that EXPLAIN during autobind is to be DISABLE (can also be specified as OFF or DISABLE)

ABIND Controls whether autobind is ■ YES—Specifies that autobind is to be ENABLE ENABLE (can also be specified as ON or ENABLE) ■ NO—Specifies that autobind is to be DISABLE (can also be specified as OFF or DISABLE) ■ COEXIST—Specifies that remigration automatic rebind is to be DISABLE while all other automatic rebinding is ENABLE. This operand is valid starting with DB2 V6. ADDLOG Adds new Active Log data set DSN(name) COPY(1 | 2) ■ name—Specifies the name of Active Log data set that is to be added. This data set should be allocated before issuing this command. Unicenter CA-24X7 does not perform data set verification. The data set name should be fully qualified without quotes. ■ 1 | 2—Specifies the log copy the data set is to be added to AGCCSID Controls the ASCII graphics VALUE(ccsid value) character code ID value ccsid value—Specifies the desired ASCII graphics character code ID value. The value can range from 1 to 65534. Note: This option is new for DB2 V5.0.

Utilities D–17 Unicenter CA-24X7

Command Description Operands

ALCUNIT Changes the Archive Log space ■ TRK—Specifies to allocate the Archive Log space allocation units in tracks ■ CYL—Specifies to allocate the Archive Log space in cylinders ■ BLK—Specifies to allocate the Archive Log space in blocks AMCCSID Controls the ASCII mixed VALUE(ccsid value) character ID value ccsid value—Specifies the desired ASCII mixed character code ID value. The value can range from 1 to 65534. Note: This option is new for DB2 V5. APPENSCH Changes the default application {EBCDIC|ACSII|UNICODE|VALUE(value)} encoding scheme ccsid value. Specify EBCDIC, ASCII, or UNICODE to set the default ccsid value to the respective character set, or specify VALUE(value) to set the ccsid to value. value can range from 1 to 65533. Note: This option is new for DB2 V7. ARC2FRST Specifies whether Copy 2 or {YES | NO} Copy 1 archives are to be read ■ YES—Specifies that Copy 2 archives are to be first read first (can also be specified as ON or ENABLE) ■ NO—Specifies that Copy 1 archives are to be read first (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V6. ARCPFX1 Change the data set name prefix VALUE(prefixname) for new Archive Log 1 data set prefixname—Specifies the data set name prefix for Archive Log 1 data sets ARCPFX2 Change the datset name prefix VALUE(prefixname) for new Archive Log 2 data set prefixname—Specifies the data set name prefix for Archive Log 2 data sets ARCRETN Changes the number of days VALUE(days) DB2 is to retain newly-created days—Specifies the number of days to retain Archive Archive Log data sets Log data sets

ARCWTOR Controls whether DB2 will issue ■ YES—Specifies DB2 will issue a WTOR (can also a WTOR before attempting an be specified as ON or ENABLE) Archive Log tape mount ■ NO—Specifies that DB2 will not issue a WTOR (can also be specified as OFF or DISABLE)

D–18 System Guide Unicenter CA-24X7

Command Description Operands ASCCID Sets the ASCII single-byte VALUE(ccsid value) character code ID value. ccsid value—Specifies the desired ASCII single-byte character code ID value. The value can range from 0 to 65534. Note: This option is new for DB2 V5.

AUTH Controls whether DB2 ■ YES—Specifies that DB2 authorization checking authorization checking is is to be performed (can also be specified as ON ENABLE or ENABLE) ■ NO—Specifies that DB2 authorization checking is not to be performed (can also be specified as OFF or DISABLE) AUTHCACH Changes the default VALUE(cache size) authorization cache size used cache size—A cache size value from 0 to 4096 which is when binding new plans. 1 a multiple of 256. A value of zero implies no cache is to be used. BINDNV Changes the authorization [BIND | BINDADD] required for binding new BINDADD—Implies that the BINDADD system packages. 1 privilege is required to create a new package or a new version of a package. BIND implies that only the BIND privilege is needed on a package or collection to create a new version of an existing package. BLKSIZE Changes the block size for VALUE(blocksize) newly-created Archive Log data blocksize—Specifies the new blocksize for Archive sets Log data sets BMPTOUT Changes the IMS BMP lock wait VALUE(value) timeout multiplier value value—Specifies the desired IMS BMP lock wait timeout multiplier value. The value can range from 0 to 254 for DB2 V5 and 1 to 254 for DB2 V6 and above. For DB2 V5, a value of zero implies using the DB2 default. BPDMC Changes the Data Manager BPID(id) VALUE(percentage) Critical (DMC) threshold for the ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Buffer Pool BP32K-BP32K9. Starting with DB2 V6, you can Note: If the Buffer Pool is also specify BP8K-BP8K9 and BP16K-BP16K9. deleted and reallocated by DB2, ■ percentage—Specifies the desired data manager the original DMC threshold will critical threshold value. The value can range be in effect. from 1 to 100 (syntax checked) representing a percentage of the Buffer Pool being unavailable (in use) before DB2 starts forcing synchronous writes.

Utilities D–19 Unicenter CA-24X7

Command Description Operands BPMAX Change the maximum Buffer BPID(id) VALUE(value) Pool size value ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Note: This function applies to BP32K-BP32K9. Starting with DB2 V6 you can DB2 V2.3 only. also specify BP8K-BP8K9 and BP16K-BP16K9. ■ value—Specifies the desired maximum Buffer Pool size. This can conceptually range from 14 to 500,000 (syntax-checked). But realistically, the range can be limited (value checked at command execution time). For example, the maximum value cannot drop below the minimum value. BPPREF Changes the default Buffer Pool BPID(id) VALUE(value) prefetch quantity size (in ■ id—Specifies the Buffer Pool ID as BP0-BP49 and number of pages) BP32K-BP32K9. Starting with DB2 V6, you can Note: The Buffer Pool prefetch also specify BP8K-BP8K9 and BP16K-BP16K9. value can only be changed for ■ value—Specifies the desired prefetch quantity for an allocated Buffer Pool. the Buffer Pool specified. The value can be 8, 16, Furthermore, the value will or 32 for 4K Buffer Pools; 0, 2, or 4 for 32K Buffer only remain in effect until the Pools; 4, 8, or 16 for 8K Buffer Pools; or 2, 4, or 8 Pool is deallocated. If the Pool is for 16K Buffer Pools. subsequently reallocated, DB2 will recalculate the prefetch quantity. Also, for DB2 V3, if the Buffer Pool is resized, DB2 will recalculate the prefetch quantity. BPSIZE Change the Buffer Pool size BPID(id) VALUE([+|-] value [%]) See also VPSIZE Note: When decreasing the size ■ id—Specifies the Buffer Pool ID as BP0-BP49 and of a DB2 V2.3 Buffer Pool, you BP32K-BP32K9. Starting with DB2 V6, you can cannot decrease it past the also specify BP8K-BP8K9 and BP16K-BP16K9. original Buffer Pool size. Also, ■ value—Specifies a desired value, an offset from for DB2 V2.3, decreasing of the the current, or a percent change from the current. Buffer Pool size will not be If + or - is specified, then the value is a change immediate and can take some from the current value. If % is specified, then the time for DB2 to quiesce the value is a percent change from the current. If buffers. neither +, -, or % is specified, then the value For DB2 V3, Unicenter CA-24X7 specifies the desired Buffer Pool size. uses the -ALTER BUFFERPOOL command to change the value.

D–20 System Guide Unicenter CA-24X7

Command Description Operands BPSPT Changes the sequential prefetch BPID(id) VALUE(percentage) DISABLE threshold for the ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Buffer Pool BP32K-BP32K9. Starting with DB2 V6, you can Note: If the Buffer Pool is also specify BP8K-BP8K9 and BP16K-BP16K9. deleted and reallocated by DB2, ■ percentage—Specifies the desired sequential the original SPT threshold will prefetch DISABLE threshold value. The value be in effect. can range from 1 to 100 (syntax checked) representing a percentage of the Buffer Pool being unavailable before DB2 temporarily disables sequential prefetch. CANCEL Cancel the currently running [CONN(connection)] SQL statement for qualifying [AUTH(auth-ID)] threads. [PLAN(planname)] Note: At least one of the [CORR(corr-ID)] qualifying parameters (CONN, AUTH, PLAN, or CORR) must [ACE(ace-address)] be specified. For distributed ■ connection—Specifies the connection ID of the threads, DB2’s -CANCEL DDF threads whose SQL statement is to be canceled. If command will be used to carry no CONN parameter is specified, then all out this function. For DB2 V4, connection types will qualify. the -CANCEL THREAD ■ auth-ID—Specifies the authorization ID of the command will be used for threads whose SQL statement is to be canceled. If non-distributed threads that are no AUTH parameter is specified, then all currently executing in DB2. authorization IDs will qualify. ■ planname—Specifies the plan name of the threads whose SQL statement is to be canceled. If no PLAN parameter is specified, then all plans will qualify.corr-id specifies the correlation ID of the threads whose SQL statement is to be canceled. If no CORR parameter is specified, then all correlation IDs will qualify. ■ ace-address—Specifies the ACE control block address associated with the thread being canceled. CASTOUT Change the castout value for BPID(id) {YES | NO} Buffer Pools using hyperpools. ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Note: This option does not BP32K-BP32K9. Starting with DB2 V6, you can apply to DB2 V2.3. also specify BP8K-BP8K9 and BP16K-BP16K9. Unicenter CA-24X7 uses the ■ YES—Specifies that castout should be in effect -ALTER BUFFERPOOL ■ NO—Specified that castout should not be in command to change the castout effect value.

Utilities D–21 Unicenter CA-24X7

Command Description Operands

CATALOG Controls whether DB2 will ■ YES—Specifies that DB2 will catalog Archive catalog Archive Log data sets Log data sets (can also be specified as ON or ENABLE) ■ NO—Specifies that DB2 will not catalog Archive Log data sets (can also be specified as OFF or DISABLE) CDSSRDEF Sets the default value of the {1 | ANY} CURRENT DEGREE special Specify 1 or ANY to set the desired default value of register the CURRENT DEGREE special register when no degree is specifically set using the SQL statement SET CURRENT DEGREE. Note: This option is new for DB2 V5.

CHGDC Controls whether change data ■ YES—Specifies that change data capture is to be capture is ENABLE ENABLE (can also be specified as ON or ENABLE) ■ NO—Specifies that change data capture is to be DISABLE (can also be specified as OFF or DISABLE)

CMTSTAT Controls whether to make a ■ ACTIVE—Specifies that DB2 will leave the thread active or inactive after it thread active commits or rolls back and holds ■ INACTIVE—Specifies that DB2 will make the no database locks or cursors thread inactive Note: You cannot change the status from INACTIVE to ACTIVE while INACTIVE threads still exist. Note: This command does not apply to DB2 V2.3.

COMPACT Controls whether data written ■ YES—Specifies that data written to the Archive to the Archive Logs is Logs is to be compacted (can also be specified as compacted ON or ENABLE) ■ NO—Specifies that data written to the Archive Logs is not to be compacted (can also be specified as OFF or DISABLE)

D–22 System Guide Unicenter CA-24X7

Command Description Operands CONDBAT Changes the maximum number VALUE([+|-] value [%]) of remote concurrent users value—Specifies a desired value, an offset from the Note: This command does not current, or a percent change from the current. If + or apply to DB2 V2.3. - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired maximum number of remote concurrent users. CONTSTOR Specifies whether DB2 will [YES | NO] periodically contract thread ■ YES—Specifies that DB2 will periodically working storage areas in order contract thread working storage areas (can also to save space be specified as ON or ENABLE) ■ NO—Specifies that DB2 will not periodically contract thread working storage areas (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V6. CTHREAD Changes the maximum number VALUE([+|-] value [%]) of users value—Specifies a desired value, an offset from the Note: If there are currently any current, or a percent change from the current. If + queued threads and you or--is specified, then the value is a change from the increase the CTHREAD value, it current value. If % is specified, then the value is a will take one of the connected percent change from the current. If neither +, -, or % threads to terminate in order for is specified, then the value specifies the desired DB2 to start dequeueing the maximum number of users. threads. DATE Changes the default date format {ISO | USA | EUR | JIS | LOCAL} ■ ISO—Use a default date format of yyyy-mm-dd ■ USA—Use a default date format of mm/dd/yyyy ■ EUR -Use a default date format of dd.mm.yyyy ■ JIS—Use a default date format of yyyy-mm-dd ■ LOCAL—Use the local date exit routine. DATELEN Changes the default local date VALUE(length) length length—Specifies the new date length in a range from 10 to 254. A value of 0 can be used to specify that no local date is to be used.

Utilities D–23 Unicenter CA-24X7

Command Description Operands DBACRVW Indicates whether an {YES|NO} authorization ID with DBADM ■ YES—Specifies that DB2 allows a DBADM user authority can create a view for to create a view for another user. It can also be another authorization ID. It also specified as ON or ENABLE. controls whether an ■ NO—Specifies that DB2 does not allow a authorization ID with DBCTRL DBADM user to create a view for another user. It or DBADM authority, on the can also be specified as OFF or DISABLE. database of the table for which an alias is being created, can Note: This option is new for DB2 V7. create an alias for itself or another authorization ID.

DBCHK Control whether database ■ YES—Specifies that database checking is checking is ENABLE ENABLE (can also be specified as ON or ENABLE) ■ NO— Specifies that database checking is to be DISABLE (can also be specified as OFF or DISABLE) DBPROTCL Specifies which protocol will be {DRDA | PRIVATE} used for 3-part names when the ■ DRDA—Indicates that DRDA protocol will be option DBPROTOCOL BIND is used for 3-part names not explicitly specified for the ■ PRIVATE—Indicates that DB2 private protocol bind of a plan or a package will be used for 3-part names Note: This option is new for DB2 V6. DEADLOK Changes the default detection VALUE(seconds) time in IRLM seconds—Specifies the number of seconds between deadlock detection cycles

DECARTH Changes the default decimal ■ DEC15—Specifies to use the rules that do not arithmetic value allow for a precision greater than 15 digits (can also be specified as 15) ■ DEC31—Specifies to use the rules that allow for a precision up to 31 digits (can also be specified as 31)

DECDIV3 Controls whether the minimum ■ YES—Specifies that the minimum divide scale is divide scale is ENABLE to be ENABLE (can also be specified as ON or ENABLE) ■ NO—Specifies that the minimum divide scale is to be DISABLE (can also be specified as OFF or DISABLE)

D–24 System Guide Unicenter CA-24X7

Command Description Operands

DECIMAL Changes the default decimal ■ ,—Specifies to use a comma as the default point value decimal point value ■ .—Specifies to use a period as the default decimal point value DEFIXTP Changes the default index type VALUE([1 | 2]) when creating new indexes. a Specify a value of 1 or 2 to indicate whether type 1 or type 2 indexes will be created when no index type is specified on the CREATE INDEX statement. DEFLTID Changes the default user ID VALUE(id) value id—Specifies the new ID to use for the default user ID DELLOG Deletes the Active Log data set DSN(datasetname) COPY(1|2) [FORCE | NOFORCE] Note: Unicenter CA-24X7 ■ datasetname—The name of the Active Log data prohibits you from deleting the set to be deleted. Be sure that the Active Log to current log data set. Also, to be deleted is not the current Active Log data set! delete an active log that has not ■ COPY—Specifies which Log copy (1 or 2) the been offloaded yet, you must data set is to be deleted from. use the FORCE option. ■ FORCE—Specifies to delete an active log even if it has not been offloaded yet ■ NOFORCE—Specifies not to delete an active log if it has not been offloaded (default) DESCSTAT Specifies whether support for {YES | NO} “extended dynamic SQL” is ■ YES—Specifies that the support for “extended ENABLE. dynamic SQL” is ENABLE (can also be specified as ON or ENABLE). If ENABLE, when a plan or package is bound, information is saved with each applicable static SQL statement that will allow an SQL DESCRIBE to be done against the statement. This is most useful for remotely connected programs running on a DBMS that allows extended-dynamic SQL. This will slightly increase the storage needed for plans and packages on DASD and in the EDM pool. ■ NO—Specifies that the support for “extended dynamic SQL” is DISABLE (can also be specified as OFF or DISABLE). Note: This option is new for DB2 V5.

Utilities D–25 Unicenter CA-24X7

Command Description Operands DLDFREQ Changes the value for the VALUE(checkpoints) current number of checkpoints checkpoint—Specifies a value from 0 to 65535 for DB2 that can occur between level ID V5 and earlier, and from 0 to 32767 for DB2 V6 and updates. 1 later, to indicate the number of checkpoints after which the level ID of a page set or partition is to be updated. A value of zero implies that down level detection is DISABLE. DLITOUT Changes the IMS DLI lock wait VALUE(value) timeout multiplier value. value—Specifies the desired IMS DLI lock wait timeout multiplier value. The value can range from 0 to 254 for DB2 V5 and from 1 to 254 for DB2 V6 and above. For DB2 V5, a value of zero implies using the DB2 default. Note: This option is new for DB2 V5. DSMAX Changes the DSMAX ZPARM VALUE([+|-] value [%]) value value—Specifies a desired value, an offset from the current, or a percent change from the current. If + or--is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired DSMAX value. DSSTIME Controls the time interval, in VALUE(value) minutes, between the resetting value—Specifies the desired data set statistics time of data set statistics for online interval in minutes. The value can range from 1 to performance monitors 1440. Online performance monitors can request DB2 data set statistics for the current interval with an IFI READS request for IFCID 0199. Note: This option is new for DB2 V6.

D–26 System Guide Unicenter CA-24X7

Command Description Operands DYNRULS Permits the user to indicate {YES | NO} whether ■ YES—Indicates that the application DYNAMICRULES(BIND) programming defaults for dynamic SQL should use the precompiler statements of the DYNAMICRULES option in options or use the DECP values effect should be used (can also be specified as for dynamic SQL statements ON or ENABLE) ■ NO—Indicates that the following application defaults should be ignored for dynamic SQL statements when bind option DYNAMICRULES(BIND) is in effect: DECIMAL POINTS IS, STRING DELIMITER, SQL STRING DELIMITER, MIXED DATA, EBCDIC CODED CHARACTER SET, and DECIMAL ARITHMETIC (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V6. DWQT Changes the deferred write BPID(id) VALUE(percentage) threshold for the Buffer Pool ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Note: For DB2 V2.3, if the BP32K-BP32K9. Starting with DB2 V6, you can Buffer Pool is deleted and also specify BP8K-BP8K9 and BP16K-BP16K9. reallocated by DB2, the original ■ percentage—Specifies the desired deferred write DWQT threshold will be in threshold value. The value can range from 1 to effect. 100 (syntax checked) representing a percentage For DB2 V3, Unicenter CA-24X7 of the Buffer Pool being unavailable before DB2 uses the -ALTER BUFFERPOOL schedules asynchronous writes in order to free command to change the value. up buffers. EDMPOOL Changes the EDM Pool size. VALUE([+|-] value [%]) value—Specifies a desired value, an offset from the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired EDM Pool size. EDPROP Controls whether data The following are valid values: propagation is ENABLE ■ YES—Specifies that data propagation is to be Note: This command does not ENABLE (can also be specified as ON or apply to DB2 V2.3 ENABLE) ■ NO—Specifies that data propagation is to be DISABLE (can also be specified as OFF or DISABLE)

Utilities D–27 Unicenter CA-24X7

Command Description Operands ENSCHEME Changes the default encoding {EBCDIC | ASCII|UNICODE} scheme value Specify EBCDIC or ASCII to change the default encoding scheme value. Starting with DB2 V7, you can also specify UNICODE. Note: This option is new for DB2 V5. EVALUNC Indicates whether the predicate {YES | NO} evaluation during table access ■ YES - specifies that predicate evaluation during can proceed upon uncommitted table access can proceed upon uncommitted data data. This applies only to (can also be specified as ON or ENABLE). isolation levels of read stability ■ NO - specifies that predicate evaluation during (RS) and cursor stability (CS). table access can not proceed upon uncommitted The DB2 default is NO. data (can also be specified as OFF or DISABLE). Note: This option is new for DB2 V7. The “evaluation of uncommitted data OK” value is specified on the "Application Programming Defaults" installation panel, and is assembled as the EVALUNC parameter of the DSN6SPRM macro. EXTRAREQ Establishes an upper limit on VALUE(value) the number of extra DRDA value—Specifies the upper limit. The value can query blocks DB2 returns to a range from 0 to 100. DRDA client This does not limit the size of the SQL query answer set; it simply controls the total amount of data that can be transmitted on any given network exchange. Note: This option is new for DB2 V6. EXTRASRV Establishes an upper limit on VALUE(value) the number of extra DRDA value—Specifies the upper limit. The value can query blocks DB2 requests from range from 0 to 100. a remote DRDA server This does not limit the size of the SQL query answer set. It simply controls the total amount of data that can be transmitted on any given network exchange. Note: This option is new for DB2 V6.

D–28 System Guide Unicenter CA-24X7

Command Description Operands EXTSEC Controls whether extended {YES | NO} security is ENABLE ■ YES—Specifies that extended security is ENABLE (can also be specified as ON or ENABLE). Extended security determines content of the error message returned to a network client when a DDF connection request fails due to security errors. In addition, it indicates whether DDF will permit an end user to update their RACF password using the DRDA change password function. ■ NO—Specifies that extended security is DISABLE (can also be specified as OFF or DISABLE). Note: This option is new for DB2 V5.

Utilities D–29 Unicenter CA-24X7

Command Description Operands FREE Frees specified page set of all DATABASE(dbname) users PAGESET(pageset-name) Note: The RESTART option is [STOP | NOSTOP ] only valid when the STOP [RESTART (NONE | RO | UT | RW| FORCE)] option is used ■ dbname—Specifies the name of the database containing the pageset that is to be freed ■ pageset-name—Specifies the name of the database pageset that is to be freed ■ STOP—Indicates that Unicenter CA-24X7 should issue a -STOP DATABASE PAGESET command before cancelling threads using the pageset ■ NOSTOP—Tells Unicenter CA-24X7 not to issue a -STOP DATABASE PAGESET command ■ RESTART—Tells Unicenter CA-24X7 to issue a -START DATABASE PAGESET ACCESS(option) command when all users have been cancelled. option can be: ■ NONE—Tells Unicenter CA-24X7 not to issue the START command ■ RO—Tells Unicenter CA-24X7 to use the ACCESS(RO) option on the START command ■ RW—Tells Unicenter CA-24X7 to use the ACCESS(RW) option on the START command ■ UT—Tells Unicenter CA-24X7 to use the ACCESS(UT) option on the START command ■ FORCE—Tells Unicenter CA-24X7 to use the ACCESS(FORCE) option on the START command GCSSID Changes the graphics character VALUE(value) code ID value value—Specifies the desired graphics character code ID value. The value can range from 1 to 65534 (syntax checked).

D–30 System Guide Unicenter CA-24X7

Command Description Operands

HOPAUTH Controls whether the package ■ YES—Specifies that the package ID will be used owner ID will be used as the (can also be specified as ON or ENABLE) Auth ID when a non-DB2 ■ NO—Specifies that the package ID will not be application requester uses a used (can also be specified as OFF or DISABLE) 3-part table name to retrieve ■ BOTH—indicates that the package owner is used data from a third site for static SQL and the runner’s authority is used Note: This command does not for dynamic SQL (can also be specified as YES, apply to DB2 V2.3 ON, or ENABLE) ■ RUNNER—indicates that both static and dynamic SQL use the runner’s authorization (can also be specified as NO, OFF, or DISABLE) HPSEQT Changes the hiperpool BPID(id) VALUE(percentage) sequential steal threshold for ■ id—Specifies the Buffer Pool ID as BP0-BP49 and the Buffer Pool BP32K-BP32K9. Starting with DB2 V6, you can Note: This command is not also specify BP8K-BP8K9 and BP16K-BP16K9. valid for DB2 V2.3. ■ percentage—Specifies the desired hiperpool Unicenter CA-24X7 uses the sequential steal threshold value. The value can -ALTER BUFFERPOOL range from 0 to 100 (syntax checked) command to change the value. representing a percentage of the hiperpool size. HPSIZE Changes the hiperpool size BPID(id) VALUE([+|-] value [%]) Note: This command is not ■ id—Specifies the Buffer Pool ID as BP0-BP49 and valid for DB2 V2.3. BP32K-BP32K9. Starting with DB2 V6, you can Unicenter CA-24X7 uses the also specify BP8K-BP8K9 and BP16K-BP16K9. -ALTER BUFFERPOOL ■ value—Specifies a desired value, an offset from command to change the value. the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired hiperpool size. IDBACK Changes the maximum number VALUE([+|-] value [%]) of batch DB2 users value—Specifies a desired value, an offset from the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired IDBACK value.

Utilities D–31 Unicenter CA-24X7

Command Description Operands IDFORE Changes the maximum number VALUE([+|-] value [%]) of TSO foreground users value—Specifies a desired value, an offset from the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired IDFORE value. IDTHTOIN Changes the current idle thread VALUE(seconds) timeout interval 1 seconds—Specifies a number of seconds from 0 to 9999 for which an active server thread is allowed to hold locks and remain dormant before being canceled. A value of 0 indicates server threads cannot become victim of a timeout. IDXBPOOL Specifies the default buffer pool VALUE(value) to be used for creating indexes value—Specifies the default Buffer Pool to be used for creating indexes. Valid values range from BP0 to BP49. Note: This option is new for DB2 V6. IRLMRWT Changes the IRLM resource VALUE([+|-] value [%]) timeout value value—Specifies a desired value, an offset from the Note: Dropping the timeout current, or a percent change from the current. If + or value below 2 times the - is specified, then the value is a change from the detection cycle will not cause current value. If % is specified, then the value is a the actual timeout to occur any percent change from the current. If neither +, -, or % less frequently is specified, then the value specifies the desired IRLMRWT value. LC_CTYPE Specifies the locale value. VALUE(value) A locale is that part of your value—Specifies the local value (a valid string up to system environment which 50 characters long). If the string contains special depends on language and characters, enclose the string in quotes. cultural conventions; in other Note: This option is new for DB2 V6. words, a combination of characters defined for a specific language and country. For example, the UPPER, LOWER, and TRANSLATE scalar functions use the locale. The results of these functions can vary, depending on the value of the locale.

D–32 System Guide Unicenter CA-24X7

Command Description Operands LEMAX Controls the maximum number VALUE(value) of LE tokens active at any time value—Specifies the maximum number of LE tokens active at any time. The value can range from 0 to 50. Note: This option is new for DB2 V6. LOBVALA Establishes an upper limit for VALUE(value) the amount of storage each user value—Specifies the upper limit per user for storing can have for storing LOB values LOB values. The value can range from 1 to 2097152 (kilobytes). Note: This option is new for DB2 V6. LOBVALS Establishes an upper limit for VALUE(value) the amount of storage value—Specifies the upper limit (system-wide) for (system-wide) used to store storing LOB values. The value can range from 1 to LOB values 51200 (megabytes). Note: This option is new for DB2 V6. LOGAPSTG Specifie s the maximum VALUE(value) ssnmDBM1 storage that can be value—Specifies the maximum ssnmDBM1 storage used by the fast log apply that can be used by the fast log apply process. The process value can range from 0 to 100 (megabytes). The default value, 0 MB, of ssnmDBM1 storage is used for the fast log apply function for all RECOVER jobs. A value of 0 MB means that the fast log apply function is DISABLE. Note: This option is new for DB2 V6.

Utilities D–33 Unicenter CA-24X7

Command Description Operands LOGLOAD Changes the checkpoint {VALUE|MINUTES} (value) frequency. For DB2 V6 and ■ Specify VALUE to set the number of log records earlier, this is the number of log to be written between checkpoints, or MINUTES records written between to set the number of minutes between checkpoints. Starting with DB2 checkpoints. Note that MINUTES is only valid V7, this value can also indicate for DB2 V7 and higher. the number of minutes between ■ value—Specifies a desired value, an offset from checkpoints. the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired LOGLOAD value. You cannot specify +, -, or % if you are changing the type of logging from minutes to records (VALUE) or vice versa. Minutes can have a value from 0 to 60. Otherwise the LOGLOAD value can be from 200 to 16000000. Note: Starting with DB2 V7, CA-24x7 will use the -SET LOG command to change the checkpoint frequency. You must have appropriate authority to issue the -SET LOG command in order to change this value. MAXALLC/M Change the maximum number VALUE(number) AXRTU of Archive tape units that can number—Specifies the new maximum number of be allocated concurrently Archive tape units MAXARCH Change the maximum number VALUE(number) of Archive Log entries number—Specifies the new number of Archive maintained in the BSDS volumes to record in the BSDS MAXCSA Changes the maximum amount VALUE([+|-] value [%]) of CSA allowed for IRLM lock value—Specifies a desired value, an offset from the storage current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired MAXCSA value

D–34 System Guide Unicenter CA-24X7

Command Description Operands MAXDBAT Changes the maximum number VALUE([+|-] value [%]) of concurrent database access value—Specifies a desired value, an offset from the threads (DBATs) current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired MAXDBAT value. MAXKEEPD Changes the “max kept VALUE(value) dynamic statements” value. Value—Specifies a value from 0 to 65535. This value specifies the total number of prepared, dynamic SQL statements that can be kept past a commit point by applications running with the KEEPDYNAMIC(YES) option. This is a system-wide limit. This parameter does not limit the size of the dynamic cache itself. When many applications bound with KEEPDYNAMIC(YES) are run in a system that has the dynamic statement cache active, they can use a considerable amount of storage in the DBM1 address space. This parameter helps limit the amount of storage used by these applications by limiting the total number of prepared statements held by these applications past a commit point. If this limit is exceeded, the KEEPDYNAMIC(YES) behavior will be honored by DB2, but implicit prepares might be necessary to rebuild the executable version of some SQL statements when they are executed after a commit. When you enter 0, DB2 can not keep the executable version of dynamic SQL statements past commit points. To retain the KEEPDYNAMIC(YES) behavior after a commit point, DB2 performs implicit prepares to rebuild the executable version of the dynamic SQL statements. This field is new with DB2 V5. The “max kept dynamic statements” is specified on the “Thread Management” installation panel, and is assembled as the MAXKEEPD parameter of the DSN6SPRM macro.

Utilities D–35 Unicenter CA-24X7

Command Description Operands MAXRBLK Changes the maximum number VALUE([+|-] value [%]) of RID pool blocks allowed Value—Specifies a value from 0 to 62500 to specify value. the maximum RID pool size in 16K blocks. A value of zero disables the use of the RID pool. In this case, DB2 does not use access paths or join methods that depend on RID pool storage. The value can also be specified as an offset or a percentage change from the current value. If + or - is specified, then the value is an offset change from the current value. If % is specified, then the change is a percent change from the current. If you decide to change this field, estimate the storage required for the RID pool with the following formula: (number of concurrent RID processing activities) * (the average number of RIDs) * 2 * (number of bytes per RID), where (number of bytes per RID) is 4 for non-large tables or 5 for large tables. Note that when changing the size of the RID pool to a smaller value, the actual size is not decreased until DB2 performs a storage contraction. However, the new value is immediately used in determining the access path. When changing the value to a larger value, DB2 will immediately use the larger value if needed. The maximum RID pool size is not specified on any installation, but is calcuated by the install CLIST and shown on the “CLIST calculations panel 1”. It is assembled as the MAXRBLK parameter of the DSN6SPRM macro. MAXTYPE1 Specifies the maximum number VALUE(value) of type 1 inactive threads value—Specifies the maximum number of type 1 allowed by DB2 inactive threads allowed by DB2. The value can range from 1 to 150000. A value of 0 indicates that type 1 inactive connections are not allowed. Note: This option is new for DB2 V6. MCCSID Changes the mixed character VALUE(value) code ID value value—Specifies the desired mixed character code ID value. The value can range from 1 to 65534 (syntax checked).

D–36 System Guide Unicenter CA-24X7

Command Description Operands MINSTOR Indicates whether DB2 will use {YES| NO} storage management algorithms ■ YES—Specifies that DB2 will perform extra that minimize the amount of processing to minimize the amount of working working storage consumed by storage consumed by individual threads (can individual threads. For best also be specified as ON or ENABLE). performance this parameter ■ NO—Specifies that DB2 will not perform extra should be NO. For subsystems processing to minimize the amount of working that have long-running threads storage consumed by individual threads (can and are constrained on storage also be specified as OFF or DISABLE). in the DBM1 address space, specifying YES can reduce the Note: This option is new for DB2 V7. total storage used in the DBM1 address space.

MIXED Controls whether x’0E’ and ■ YES—Specifies that the code points have special x’0F’ have special meaning as meaning (can also be specified as ON or shift in and shift out controls for ENABLE) character strings with ■ NO—Specifies that the code points do not have double-byte character sets special meaning (can also be specified as OFF or DISABLE) MONSIZE Changes the default buffer size VALUE(value) for a monitor trace value—Specifies the new buffer size for trace monitors MSVGP Changes the mass storage VALUE(value) volume group used for the value—Specifies the new mass storage volume Archive Log copy 1 group name for Archive Log copy 1 To change the value to blanks, use a value of “BLANKS” MSVGP2 Changes the mass storage VALUE(value) volume group used for the value—Specifies the new mass storage volume Archive Log copy 2 group name for Archive Log copy 2 To change the value to blanks, use a value of “BLANKS” NUMLKTS Changes the maximum number VALUE([+|-] value [%]) of concurrent page locks per value—Specifies a desired value, an offset from the table space current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired NUMLKTS value.

Utilities D–37 Unicenter CA-24X7

Command Description Operands NUMLKUS Changes the maximum number VALUE([+|-] value [%]) of concurrent page locks per value—Specifies a desired value, an offset from the user current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired NUMLKUS value.

OFFLOAD Controls whether DB2 will ■ YES—Specifies that DB2 will unload active Log unload active Log data sets data sets (can also be specified as ON or when they become full ENABLE) ■ NO—Specifies that DB2 will not unload active Log data sets (can also be specified as OFF or DISABLE) OJPERFEH Controls whether the outer join {YES | NO} performance enhancements are ■ YES—Specifies that the outer join performance ENABLE enhancements are ENABLE (can also be specified as ON or ENABLE) ■ NO—Specifies that the outer join performance enhancements are DISABLE (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V6. OPTHINTS Controls whether optimizer {YES | NO} hints are allowed ■ YES—Lets you pass information to DB2 that influence the access path selected for certain queries (can also be specified as ON or ENABLE). The information passed is in the form of rows in the PLAN_TABLE. ■ NO—Specifies that optimizer hints are not allowed (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V 6. OUTBUFF Changes the active log output VALUE([+|-] value [%]) buffer size. value—Specifies a number from 40k to 400,000k indicating the number of bytes for the desired output buffer size. The value should be a multiple of 4k. CA-24x7 will round the value up to the next 4k size if the value specified is not a multiple of 4k. The value can also be specified as an offset or a percentage change from the current value. If + or - is specified, then the change is a percent change from the current.

D–38 System Guide Unicenter CA-24X7

Command Description Operands PARAMDEG Specifies the desired degree of VALUE(value) parallelism for a parallel group. value—Specifies the maximum degree of parallelism for a parallel group. A value of 0 means there is no upper limit. Valid values are 0 to 254. Note: This option is new for DB2 V6. PCLOSEN Changes the value of the VALUE(checkpoints) current number of checkpoints checkpoint—Specifies a value from 1 to 32767. since the last update that DB2 will wait to change the state of a data set from read-write to read-only.2 PCLOSET Changes the current number of VALUE(minutes) minutes since the last update minute—Specifies a value from 1 to 32767. that DB2 will wait to change the state of a data set from read-write to read-only. b POOLINAC Specifies the length of time that VALUE(value) a DBAT can remain idle in the value—Specifies the desired pool thread timeout pool before it is terminated. value, in seconds, that a DBAT can remain idle in the pool before it is terminated. 0 causes a DBAT to terminate rather than go into the pool if there is a sufficient number of threads in the pool to process the number of type 2 inactive threads that currently exist. Valid values are 0 to 9,999. Note: This option is new for DB2 V6. PRIQTY Changes the primary space VALUE(value) allocation when allocating value—Specifies the new primary space allocation Archive Logs on DASD quantity

PROTECT Controls whether Archive Logs ■ YES—Specifies that Archive Log data sets are are protected with individual protected with individual RACF profiles (can RACF profiles also be specified as ON or ENABLE) ■ NO—Specifies that Archive Log data sets are not protected with individual RACF profiles (can also be specified as OFF or DISABLE)

Utilities D–39 Unicenter CA-24X7

Command Description Operands PTASKROL Controls whether to roll up {YES | NO} query parallel task’s accounting ■ YES—Specifies that the originating task will cut trace into originating task’s an additional accounting trace record with all the accounting trace roll up values from parallel tasks (can also be specified as ON or ENABLE) ■ NO—Specifies that each parallel task will produce its own accounting trace record (can also be specified as OFF or DISABLE) Note: This option is new for DB2 V6. QUIESCE Changes the maximum number VALUE(value) of seconds DB2 will attempt a value—Specifies the seconds DB2 will attempt full full system quiesce system quiesce

RECALL Controls whether DB2 will wait ■ YES—Specifies that DB2 will wait for an HSM for an HSM recall for the recall (can also be specified as ON or ENABLE) RECALLD time ■ NO—Specifies that DB2 will not wait for an HSM recall (can also be specified as OFF or DISABLE) RECALLD Changes the number of seconds VALUE([+|-] value [%]) that DB2 will wait for an HSM value—Specifies a desired value, an offset from the recall request current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired RECALLD value. RELCURHL Specifies whether DB2 bypasses {YES | NO} the promotion of data locks for ■ YES—Specifies DB2 bypass lock promotion of cursor_with_hold. data locks for cursor_with_hold (can also be specified as ON or ENABLE). Lock promotion causes a lock to be held across a commit until the next commit. Bypassing lock promotion causes a lock to be released at the current commit. ■ NO—Specifies DB2 promote data locks for cursor_with_hold (can also be specified as OFF or DISABLE). Note: this option is new for DB2 V5.

D–40 System Guide Unicenter CA-24X7

Command Description Operands REPLACE Dynamically replaces an exit REPLACE EXIT(exitname) DSN(datasetname) routine. {CONNECTION | SIGNON | EDITPROC | DB2 has specific naming VALIPROC | DATE | TIME | FIELDPROC | requirements for the DATE, LOGCAPTURE | AUTH} TIME, CONNECTION, ■ exitname—Specifies the EXIT module name. Note LOGCAPTURE, access control that certain exit types are required to have a authorization (AUTH), and specific name and/or entry point. SIGNON exits. However, ■ datasetname—Specifies the source load library Unicenter CA-24X7 does not from which the exit is to be loaded. The require these names. You can datasetname should be fully qualified without replace any of these exits with a quotes. module name of your choice. You must specify the exit type that is being loaded For connection, sign-on, date, (CONNECTION, SIGNON, and so on). time, access control authorization, and log capture exit routines, you must ensure that the exit module name specified is NOT the same name as another exit module or DB2 module. That is, it can be the same name as the one being replaced, or a different unique name. If a different name is specified, no attempt is made to delete the current exit. If the same name is specified, the current exit is deleted.

Utilities D–41 Unicenter CA-24X7

Command Description Operands (REPLACE The load library specified must continued) be an APF authorized library. Otherwise, the load will fail and the prior exit routine will be left in place. For edit procs, validation procs, and field procs, Unicenter CA-24X7 has no way of validating the exit name if the exit is not loaded. If the exit is not currently loaded by DB2, Unicenter CA-24X7 will perform a load on the module so that when DB2 does require the module, it will use the one you specified using Unicenter CA-24X7. Unicenter CA-24X7 also ensures that the module use count will never drop to zero so that a requested module will always stay loaded and be used by DB2. That is, there is no chance that the module will become unused and subsequently deleted by DB2 (and thus the original module being reloaded the next time it is needed).

D–42 System Guide Unicenter CA-24X7

Command Description Operands (REPLACE When the access control continued) authorization exit is refreshed, Unicenter CA-24x7 will allocate a new work area and will invoke the EXIT with initialization parameters so that the work environment can be properly initialized. ■ If the exit routine abends during initialization, the current routine, its work area, and its setting (enabled/disabled) are left intact and a dump of the abend is taken to a system dump data set. ■ If the previous exit routine had been disabled by DB2, refreshing the exit will reenable DB2 to use the exit. To disable the active exit from being invoked, you can refresh the exit with the default DB2 exit module in SDSNLOAD which generates an RC12 to tell DB2 not to invoke the exit routine again (until you reenable it with another Unicenter CA-24x7 refresh). Unicenter CA-24x7 will issue a UDB0119I message with the initialization return codes when the exit is successfully replaced. CA-24x7 will issue a UDB0120W message with the initialization return codes when the exit is successfully replaced, but has been disabled due to the return code from the exit routine during initialization. RESYNC Change the time interval for VALUE(time-interval) DDF resynchronization period time-interval—Specifies the new time interval for the DDF resynchronization period

Utilities D–43 Unicenter CA-24X7

Command Description Operands RETLWAIT Controls whether DB2 waits for {YES | NO} (for DB2 V5 and later) incompatible retained locks. VALUE(wait-time) (for DB2 V6 and later) ■ YES—Specifies DB2 to wait for incompatible retained locks (can also be specified as ON or ENABLED). If enabled, IRLM lock or change requests will wait for incompatible retained locks. ■ NO—Specifies DB2 not to wait for incompatible retained locks (can also be specified as OFF or DISABLED). If disabled, IRLM lock or change requests will not wait for incompatible retained locks, but instead will be immediately rejected. ■ wait-time—Specifies a number from 0 to 254, indicating a numerical value that is used as a multiplier to the connection’s normal timeout interval to determine how long the application will wait for an incompatible lock. A value of 0 indicates that IRLM lock or change requests will not wait for incompatible retained locks, but will instead be immediately rejected. Note: This option is new for DB2 V5. RETVLCFK Specifies whether the {YES | NO} VARCHAR column will be ■ YES—Indicates that index-only access of retrieved from the index. The varying-length column data will be enabled (can data sharing scope of this also be specified as ON or ENABLE). Enabling parameter is GROUP. this option results in better performance; the data retrieved from the index contains padded blanks to the maximum length of the column. ■ NO—Indicates that DB2 must go to the data page to retrieve data, because index-only access of varying-length column data will not be possible (can also be specified as OFF or DISABLE). With a setting of NO, data is retrieved with no padding. Note: This option is new for DB2 V6.

RGFDEDPL Controls whether DDL ■ YES—Specifies that DDL can only be issued by statements are limited to applications in the ART (can also be specified as applications that are in the ON or ENABLED) Application Registration Table ■ NO—Specifies that DDL is not limited to (ART) applications in the ART (can also be specified as OFF or DISABLED)

D–44 System Guide Unicenter CA-24X7

Command Description Operands

RGFDEFLT Specifies the default action to ■ ACCEPT—Specifies to accept the DDL take for DDL that names an ■ REJECT—Specifies to reject the DDL unregistered object ■ APPL—Specifies to accept the DDL if the application is registered RGFESCP Specifies the escape character to VALUE(escape-character) use in the application and object escape-character—Specifies the new escape character registration tables (any non-alphanumeric character) Note: This command does not Note: To change the escape character to a blank, apply to DB2 V2.3. use a value of “X”

RGFFULLQ Controls whether registered ■ YES—Specifies that registered objects require objects require fully qualified fully qualified names (can also be specified as names ON or ENABLED) ■ NO—Specifies that registered objects do not require fully qualified names (can also be specified as OFF or DISABLED)

RGFINSTL Controls whether DDL ■ YES—Specifies that DDL validation is to be validation is enabled enabled (can also be specified as ON or Note: You can only disable and ENABLED) re-enable DDCS. You cannot ■ NO—Specifies that DDL validation is to be enable DDCS if it was not disabled (can also be specified as OFF or installed at DB2 start-up. DISABLED) RLFAUTH Cha nges the default VALUE(authorization-ID) authorization ID used for the authorization-ID—Specifies the new authorization ID resource limit table to use for the resource limit table Note: The Authorization ID specified becomes the default qualifier for the resource limit facility (RLF). When you change this value, Unicenter CA-24X7 will attempt to stop and restart the rlimit facility in order to pick up the new value. You should pay close attention to the output messages to ensure that the resource limit facility gets restarted correctly. If it does not, then you will need to correct the problem and restart RLF.

Utilities D–45 Unicenter CA-24X7

Command Description Operands

RLFERR Specifies the default resource ■ NORUN—Specifies that the statement is not to limit action to take when an be executed RLF table row is not found ■ NOLIMIT—Specifies that the statement will execute with no resource limit ■ VALUE(limit)—Specifies that the statement will execute with a limit of limit.

RLFERRD Specifies the default resource ■ NORUN—Specifies that the statement is not to limit action to take when an be executed RLF table row is not found for ■ NOLIMIT—Specifies that the statement will remote threads execute with no resource limit ■ VALUE(limit)—Specifies that the statement will execute with a limit of limit. RLFTBL Changes the default resource VALUE(suffix) limit table suffix value suffix—Specifies the new resource limit table suffix Note: The table suffix becomes the default suffix for the resource limit facility. When you change this value, Unicenter CA-24X7 will attempt to stop and restart the rlimit facility in order to pick up the new value. You should pay close attention to the output messages to ensure that the resource limit facility gets restarted correctly. If it does not, then you will need to correct the problem and restart RLF. RRULOCK Changes the current “use U lock [YES | NO] for repeatable read” value. a This value specifies whether to use the U (UPDATE) lock when using repeatable read (RR) isolation to access a table. ■ Specify NO (or OFF or DISABLE) to indicate the default lock mode for operations with RR is S (SHARE). ■ Specify YES (or ON or ENABLE) to indicate that the default lock mode is U (UPDATE).

D–46 System Guide Unicenter CA-24X7

Command Description Operands SCCSID Changes the single-byte VALUE(value) character code ID value value—Specifies the desired single-byte character code ID value. The value can range from 1 to 65534 (syntax checked). SECQTY Changes the secondary space VALUE(quantity) allocation when allocating quantity—Specifies the new secondary space Archive Logs on DASD allocation quantity

SEQCACH Controls whether DB2 will use ■ YES—Specifies that sequential mode is to be sequential mode to read cached enabled (can also be specified as ON or SEQ or data from a 3390-3 device. ENABLED) Note: This command does not ■ NO—Specifies that sequential mode is to be apply to DB2 V2.3. disabled (can also be specified as OFF or BYPASS or DISABLED) SEQPRES Specifies whether the 3390 {YES | NO} cache option is enabled or ■ YES—Specifies that the utility 3390 cache option disabled. is enabled (can also be specified as ON or ENABLED). This parameter controls whether certain utilities allow data to remain in 3990 cache longer when reading data. ■ NO—Specifies that the utility 3390 cache option is disabled (can also be specified as OFF or DISABLED). Note: This option is new for DB2 V5.

SITETYP Controls whether the site type ■ LOCALSITE—Specifies that DB2 will run as a is local or recovery local site (can also be specified as LOCAL) ■ RECOVERYSITE—Specifies that DB2 will run as a recovery site (can also be specified as RECOVERY)

SQLDELI Changes the default SQL ■ “—Specifies to use a quote as the SQL delimiter delimiter ■ ‘—Specifies to use an apostrophe as the SQL delimiter SRTPOOL Changes the maximum sort VALUE([+|-] value [%]) pool size value—Specifies a desired value, an offset from the current, or a percent change from the current. If + or - is specified, then the value is a change from the current value. If % is specified, then the value is a percent change from the current. If neither +, -, or % is specified, then the value specifies the desired SRTPOOL size.

Utilities D–47 Unicenter CA-24X7

Command Description Operands STATHIST Controls whether and how {NONE|SPACE|ALL|ACCESSPATH} inserts and updates are ■ NONE— Indicates that changes made by DB2 to recorded in catalog history the catalog are not recorded. tables. ■ SPACES—Indicate that all inserts and updates made to space- related catalog statistics by DB2 are recorded. ■ ALL—Indicates that all inserts and updates made to the DB2 catalog statistics by DB2 are recorded. ■ ACCESSPATH—Indicates that all inserts and updates made to access path-related catalog statistics by DB2 are recorded. Note: This option is new for DB2 V7. STATIME Changes the statistics trace time VALUE(time) interval (in minutes) time—Specifies the new statistics trace interval STATROLL Indicates whether the {YES|NO} RUNSTATS utility will ■ YES—Specifies that RUNSTATS will aggregate aggregate the partition level partition level statistics. It can also be specified statistics. as ON or ENABLE. ■ NO—Specifies that RUNSTATS will not aggregate partition level statistics. It can also be specified as OFF or DISABLE. Note: This option is new for DB2 V7.

STDSQL Changes the default standard ■ YES—Specifies that SQL is written in accordance SQL value with the current ANSI/ISO standard. ■ NO—Specifies that SQL is written by IBM DB2 rules ■ 86—Specifies that SQL is to conform to ANSI 1986 standards STORMXAB Changes the current stored VALUE(value) procedure maximum abend value—Specifies a number from 0 to 225 for the count value.1 number of times a stored procedure is allowed to terminate abnormally, after which SQL CALL statements for the stored procedure are rejected. A value of 0 means that the first abend of a stored procedure causes SQL CALLs to that procedure to be rejected.

D–48 System Guide Unicenter CA-24X7

Command Description Operands STORPROC Changes the default stored VALUE(value) procedure started task name. 1 value—Specifies a valid JCL procedure name that is currently in the default system PROCLIB concatenation. Note: You should not change this value while a stored procedures address space is active. First stop the current stored procedure address space with the DB2 -STOP PROCEDURE command, and then change to the new name. STORTIME Changes the current stored {NOLIMIT | VALUE(seconds)} procedure timeout value. 1 second—Specifies a number from 5 to 1800 (or NOLIMIT) for the number of seconds before DB2 ceases to wait for an SQL CALL to be assigned to one of the task control blocks (TCBs) in the DB2 stored procedures address space. If the time interval expires, the SQL statement fails. SUPERRS Indicates whether DB2 will {YES|NO} suppress LOGREC recording of ■ YES—Specifies that DB2 will suppress LOGREC recoverable RDS abends (soft recording of soft errors. It can also be specified errors). as ON or ENABLE. ■ NO—Specifies that DB2 will not suppress LOGREC recording of soft errors. It can also be specified as OFF or DISABLE. Note: This option is new for DB2 V7. SYNCVAL Indicates whether and when the {NO|VALUE(value)} DB2 statistics recording is ■ NO—Indicates that DB2 will not synchronize the synchronized with some part of statistics recording. the hour. ■ VALUE(value)—Ranges from 0 to 59. It also indicates the number of minutes past the hour for which DB2 produces statistics records. Note: This option is new for DB2 V7. SYSADM Changes the SYSADM ID 1 VALUE(id) value id—Specifies the new ID to use for SYSADM ID number 1 SYSADM2 Changes the SYSADM ID VALUE(id) 2value id—Specifies the new ID to use for SYSADM ID number 2

Utilities D–49 Unicenter CA-24X7

Command Description Operands SYSOPR1 Changes the SYSOPR ID 1 value VALUE(id) id—Specifies the new ID to use for SYSOPR ID number 1 SYSOPR2 Changes the SYSOPR ID 2 value VALUE(id) id—Specifies the new ID to use for SYSOPR ID number 2 TBSBPOOL Specifies the default Buffer Pool VALUE(value) to be used for creating value—Specifies the default Buffer Pool to be used tablespaces for creating tablespaces. Valid values range from BP0 to BP49. Note: This option is new for DB2 V6. TCPALVER Specifies whether the “TCP/IP {YES | NO} already verified” value is ■ YES—Specifies that the “TCP/IP already enabled. verified” value is enabled (can also be specified as ON or ENABLED). TCP/IP already verified determines whether TCP/IP connection requests containing only a userid (and no password, RACF PassTicket, or DCE ticket) are accepted by DB2. If the value is YES, TCP/IP connection requests containing only a userid are accepted. ■ NO—Specifies that the “TCP/IP already verified” value is disabled (can also be specified as OFF or DISABLED). Note: This option is new for DB2 V5. TCPKPALV Determines whether to override {ENABLE | DISABLE | VALUE(value)} the TCP/IP stack KeepAlive ■ ENABLE—Specifies not to override the TCP/IP value value (can also be specified as ON or YES) ■ DISABLE—Disables KeepAlive probing altogether (can also be specified as OFF or NO) ■ value—Specifies that the TCP/IP stack KeepAlive value should be modified in favor of the given value. The value can range from 1 to 65534 (seconds). Note: This option is new for DB2 V6.

D–50 System Guide Unicenter CA-24X7

Command Description Operands

TIME Changes the default time format ■ ISO—Use a default time format of hh.mm.ss ■ USA—Use a default time format of hh:mm AM/PM ■ EUR—Use a default time format of hh.mm.ss ■ JIS—Use a default time format of hh:mm:ss ■ LOCAL—Specifies to use the local time exit routine. TIMELEN Changes the default local time VALUE(value) length value—Specifies the new time length in a range from 10 to 254. A value of 0 can be used to specify that no local time is to be used.

TSTAMP Controls whether DB2 will ■ YES—Specifies that DB2 puts a timestamp in the place a timestamp in the Archive Log data set name (can also be specified Archive Log data set name as ON or ENABLED) ■ NO—Specifies that DB2 does not put a timestamp in the Archive Log data set name (can also be specified as OFF or DISABLED) ■ EXT—Specifies that DB2 puts date and time qualifiers in the archive log data set name; the year portion of the date is in 4-digit format. This operand is valid starting with DB2 V6. UNIT Changes the device type or unit VALUE(device-type) name for allocating new device-type—Specifies the device type for allocating Archive Log data sets new Archive Log data sets UNIT2 Changes the archive log device VALUE(device-type) type or unit name to use with device-type—Specifies an alphanumeric string for the the second archive copy data desired device type 2 or unit 2 name. set. 1 URCHKTH Changes the UR checkpoint VALUE(value) frequency value. value—Specifies the desired UR checkpoint frequency value. The value can range from 0 to 255. This value indicates the number of complete checkpoint cycles before DB2 issues a warning message to the console for a UR. Note: This option is new for DB2 V5.

Utilities D–51 Unicenter CA-24X7

Command Description Operands URLGWTH Changes the UR log to write VALUE(value) threshold value. value—Specifies a value from 0 to 1,000,000 to indicate the number of log records that can be written by an uncommitted unit of recovery (UR) before DB2 issues a warning message to the console. The purpose of this option is to provide notification of a long-running UR that can result in a lengthy recovery situation for critical tables. The value should be specified in increments of 1,000 (1,000 log records). A value of 0 indicates that no write check is to be done. Note: This option is new for DB2 V7. UTIMOUT Changes the utility timeout VALUE(factor) factor.2 factor—Specifies the new utility timeout factor VDWQT Changes the vertical deferred BPID(id) VALUE(percentage[,pages]) write threshold for the Buffer ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Pool. BP32K-BP32K9. Starting with DB2 V6, you can Note: For DB2 V2.3, if the also specify BP8K-BP8K9 and BP16K-BP16K9. Buffer Pool is deleted and ■ percentage—Specifies the desired vertical reallocated by DB2, the original deferred write threshold value. The value can VDWQT threshold will be in range from 0 to 90 (syntax checked) representing effect. For DB2 V3, Unicenter a percentage of the virtual pool being consumed CA-24X7 uses the -ALTER by updated pages of a pageset before invoking BUFFERPOOL command to deferred writes for that pageset. change the value. ■ pages—Specifies the desired vertical deferred write threshold as a number of updated pages in the virtual Buffer Pool for a given pageset. The value can range from 0 to 9999. This operand is valid starting with DB2 V6. For DB2 V6 and above, if the percentage value is 0, then the count of updated pages value is used. Otherwise, the count of updated pages value is ignored and the percentages value is used.

D–52 System Guide Unicenter CA-24X7

Command Description Operands VPPSEQT Changes the parallel sequential BPID(id) VALUE(percentage) steal threshold for the virtual ■ id—Specifies the Buffer Pool ID as BP0-BP49 and pool. BP32K-BP32K9. Starting with DB2 V6, you can Note: This command is not also specify BP8K-BP8K9 and BP16K-BP16K9. valid for DB2 V2.3. ■ percentage—Specifies the desired parallel Unicenter CA-24X7 uses the sequential steal threshold value. The value can -ALTER BUFFERPOOL range from 0 to 100 (syntax checked) command to change the value. representing a percentage of sequential steal threshold for virtual pool buffers that can be used for sequentially access pages using parallel I/O. VPSEQT Changes the sequential steal BPID(id) VALUE(percentage) threshold for the virtual pool. ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Note: For DB2 V2.3, if the BP32K-BP32K9. Starting with DB2 V6, you can Buffer Pool is deleted and also specify BP8K-BP8K9 and BP16K-BP16K9. reallocated by DB2, the original ■ percentage—Specifies the desired sequential steal VPSEQT threshold will be in threshold value. The value can range from 0 to effect. For DB2 V3, Unicenter 100 (syntax checked) representing a percentage CA-24X7 uses the -ALTER of the virtual pool that can be used for BUFFERPOOL command to sequentially access pages. change the value. VPSIZE See also BPSIZEChanges the BPID(id) VALUE([+|-] value [%]) virtual Buffer Pool size. ■ id—Specifies the Buffer Pool ID as BP0-BP49 and Note: When decreasing the size BP32K-BP32K9. Starting with DB2 V6, you can of a DB2 V2.3 Buffer Pool, you also specify BP8K-BP8K9 and BP16K-BP16K9. cannot decrease it past the ■ value—Specifies a desired value, an offset from original Buffer Pool size. Also, the current, or a percent change from the current. for DB2 V2.3, decreasing of the If + or - is specified, then the value is a change Buffer Pool size will not be from the current value. If % is specified, then the immediate and can take some value is a percent change from the current. If time for DB2 to acquiesce the neither +, -, or % is specified, then the value buffers. specifies the desired virtual Buffer Pool size. For DB2 V3, Unicenter CA-24X7 uses the -ALTER BUFFERPOOL command to change the value

Utilities D–53 Unicenter CA-24X7

Command Description Operands WLMENV Specifies the name of the VALUE(value) WLM_ENVIRONMENT to use value—Specifies the name of the for a user-defined function or WLM_ENVIRONMENT to use stored procedure when a value Note: This option is new for DB2 V6. is not given for the WLM_ENVIRONMENT option on statements CREATE FUNCTION or CREATE PROCEDURE WRTHRSH Changes the threshold value for VALUE([+|-] value [%]) the number of log buffer pages value—Specifies a number from 1 to 256. The value to be filled up before initiating a can also be specified as an offset or a percentage write. change from the current value. If + or - is specified, then the value is an offset change from the current value. If % is specified, then the change is a percent change from the current. The log write threshold is specified on the “Active Log Data Set Parameters” installation panel, and is assembled as the WRTHRSH parameter of the DSN6LOGP macro. Note: This parameter was removed in DB2 V6, but can still be changed through CA-24x7. XLKUPDLT Controls the locking method {YES | NO} used when performing a ■ YES—Indicates that DB2 will use an X lock when searched update or delete scanning for qualifying rows (can also be specified as ON or ENABLE) ■ NO—Indicates that an S or U lock will be obtained when scanning for qualifying rows (can also be specified as OFF or DISABLE). Note: This option is new for DB2 V6.

D–54 System Guide Index

AGENT-OBJECT-STORE= parameter, 5-38 $ AGENT-REQUESTS= parameter, 5-39 AIDLPRIM field, 6-29, 6-30 $ARCCOPY member, 8-10 ALCUNIT command, D-18 $ARCDDL member, 8-6 ALLCALLS, A-3 $DB2CLEAN IMOD, 5-81 ALL-MENUS= parameter, 6-22 $DB2CLNUP IMOD, 5-85 ALLREQS, A-3 Alphanumeric translation table, 5-43 3 ALTER= parameter, 6-20 AMCCSID command, D-18 3390-3 sequential mode, D-47 APF authorization Global Subsystem LINKLIB, 4-6 A APPENSCH command, D-18 APPLS member, 4-26 abbreviations months and days, 5-42 APPLS= parameter, 4-26, 5-32, 5-48, 5-73 ABEND ARC2FRST command, D-18 full dump, 5-24 ARCCOPY member, 8-10 SNAP dump, 5-24 ARCDDL member, 8-3, 8-8, 8-10 ABEXP command, D-17 Archive Log 1 data set name prefix, D-18 ABIND command, D-17 Archive Log 1 mass storage volume group, D-37 ACBNAME parameter, 4-25 Archive Log 2 mass storage volume group, D-37 ACCTTRACE= parameter, 5-25 Archive Log data compaction, D-22 ACID, 4-21 Archive Log Data Set blocksize, D-19 Active Log Data Set, D-17 delete, D-25 Archive Log Data Set cataloging, D-22 ADDLOG command, D-17 Archive Log Data Set retention, D-18 AGCCSID command, D-17 Archive Log data sets device type, D-51 AGENT-CONFIG= parameter, 5-39 timestamp, D-51 AGENT-DEBUG= parameter, 5-38 Archive Log Data Sets secondary space allocation, D-47

Index–1 Archive Log space allocation units, D-18 Authorization IDs data collector usage, 5-14 Archive Log tape mount WTOR, D-18 usage by EXPLAIN, 3-3 Archive Logs Autobind enablement, D-17 primary space allocation, D-39 RACF protection, D-39 Archive tape units B maximum, D-34

Archiving Basic Installation by Generation Data Group, 3-7 verification, 2-1 columns generated, 8-3

creating the database, 8-6 Batch Report Writer

daily data, 8-9 scheduling reports, 3-5

data sources, 8-4 verification, 2-1 detail data, 8-9 batch user interface getting data from the data collector, 8-8 and the data collector, 5-71 introduction, 8-1 condition codes, 5-73 keeping data synchronized, 8-6 data collector User ID, 5-45 loading data from Online History, 8-2 DD statements, 5-72 managing the environment, 8-10 DD Statements, 5-46 manipulating data, 8-9 NSIGHTEX functions, A-5 obtaining SMF data from Online History, 8-7 operation, 5-70 optimizing data, 8-4 operational overview, 5-71 related component members, 8-10 parameter file, 5-72 to the History Database, 3-8 requirements, 5-71 without Generation Data Groups, 3-7 sample jobs, 5-71

ARCLxxxx member, 8-11 User ID for data collector, 5-45

ARCPFX1 command, D-18 BINDNV command, D-19

ARCPFX2 command, D-18 BLKSIZE command, D-19

ARCRETN command, D-18 BMPTOUT command, D-19

ARCSPACE CLIST, 8-6 BPDMC command, D-19

ARCSPACE member, 8-11 BPMAX command, D-20

ARCSQL member, 8-9, 8-11 BPPREF command, D-20

ARCSQLD member, 8-4, 8-11 BPSIZE command, D-20

ARCWTOR command, D-18 BPSPT command, D-21

Arithmetic decimal default value, D-24 buffer OP, 5-15 ART and DDL, D-44 PRV, 5-16 SRV, 5-15 ASCCID command, D-19 Buffer Pool AUTH command, D-19 deferred write threshold, D-27 security, 6-23 hiperpool sequential steal threshold, D-31 AUTHCACH command, D-19 virtual size, D-50, D-51, D-53, D-54 AUTHID= parameter, 6-17 Buffer Pool castout value, D-21 authorization ID, 5-13 Buffer Pool DMC threshold, D-19

Index–2 System Guide Buffer Pool maximum size, D-20 CICS modifications for NATURAL for DB2 support, 4-29 Buffer Pool prefetch DISABLE threshold, D-21 monitoring with the System Condition Monitor, Buffer Pool prefetch quantity size, D-20 4-35 Buffer Pool size, D-20 CICS Monitoring Facility, 3-8 Buffer Pools CLIST library members vertical deferred write threshold, D-52 GSSCLIST, 4-12 buffer size CMF, 3-8 data collector, 5-15 CMTSTAT command, D-22 Buffer size Code points, D-37 monitor trace, D-37 COMMAND= parameter, 5-72 BUSER4 user field, 4-28 Commands ABEXP, D-17 C ABIND, D-17 ADDLOG, D-17 AGCCSID, D-17 CA-ACF2, 4-20 ALCUNIT, D-18 and DB2 commands, 6-29 AMCCSID, D-18 and EXPLAIN, 6-29 APPENSCH, D-18 CANCEL command, D-21 ARC2FRST, D-18 ARCPFX1, D-18 Cancel threads ARCPFX2, D-18 security, 6-23 ARCRETN, D-18 CASTOUT command, D-21 ARCWTOR, D-18 ASCCID, D-19 CATALOG command, D-22 AUTH, D-19

CA-Top Secret AUTHCACH, D-19

modifications for the VTAM user interface, 4-21 BINDNV, D-19 BLKSIZE, D-19 CA-TOP SECRET BMPTOUT, D-19 and DB2 commands, 6-29 BPDMC, D-19 and EXPLAIN, 6-29 BPMAX, D-20 BPPREF, D-20 CDSSRDEF command, D-22 BPSIZE, D-20 Change data capture enablement, D-22 BPSPT, D-21 CANCEL, D-21 changing data set to read-only, D-39 CASTOUT, D-21 Character code ID value, D-36 CATALOG, D-22 CDSSRDEF, D-22 Checklist CHGDC, D-22 Global Subsystem installation, 4-2 CMTSTAT, D-22 NATURAL for DB2 support installation, 4-28 COMPACT, D-22 Remote Access Facility installation, 4-24 CONDBAT, D-23 System Condition Monitor installation, 4-34 CONTSTOR, D-23 Checkpoints CTHREAD, D-23 log records written, D-34 DATE, D-23 DATELEN, D-23 CHGDC command, D-22 DBACRVW, D-24 DBCHK, D-24

Index–3 DBPROTCL, D-24 OJPERFEH, D-38 DEADLOK, D-24 OPTHINTS, D-38 DECARTH, D-24 OUTBUFF, D-38 DECDIV3, D-24 PARAMDEG, D-39 DECIMAL, D-25 PCLOSEN, D-39 DEFIXTP, D-25 PCLOSET, D-39 DEFLTID, D-25 POOLINAC, D-39 DELLOG, D-25 PRIQTY, D-39 DESCSTAT, D-25 PROTECT, D-39 DLDFREQ, D-26 PTASKROL, D-40 DLITOUT, D-26 QUIESCE, D-40 DSMAX, D-26 RECALL, D-40 DSSTIME, D-26 RECALLD, D-40 DWQT, D-27 RELCURHL, D-40 DYNRULS, D-27 REPLACE, D-41 EDMPOOL, D-27 RESYNC, D-43 EDPROP, D-27 RGFDEDPL, D-44 ENSCHEME, D-28 RGFFULLQ, D-45 EVALUNC, D-28 RGFINSTL, D-45 EXTRAREQ, D-28 RLFAUTH, D-45 EXTRASRV, D-28 RLFERRD, D-46 EXTSEC, D-29 RLFTBL, D-46 FREE, D-30 RRULOCK, D-46 from Console interface, 5-13 SCCSID, D-47 GCSSID, D-30 SECQTY, D-47 HOPAUTH, D-31 SEQCACH, D-47 HPSEQT, D-31 SITETYP, D-47 HPSIZE, D-31 SQLDELI, D-47 IDBACK, D-31 SRTPOOL, D-47 IDFORE, D-32 STATHIST, D-48 IDTHTOIN, D-32 STATROLL, D-48 IDXBPOOL, D-32 STATTIME, D-48 IRLMRWT, D-32 STDSQL, D-48 LC_CTYPE, D-32 STORMXAB, D-48 LEMAX, D-33 STORPROC, D-49 LOBVALA, D-33 STORTIME, D-49 LOBVALS, D-33 SUPERRS, D-49 LOGAPSTG, D-33 SYNCVAL, D-49 LOGLOAD, D-34 SYSADM, D-49 MAXALLC, D-34 SYSADM2, D-49 MAXARCH, D-34 SYSOPR1, D-50 MAXCSA, D-34 SYSOPR2, D-50 MAXDBAT, D-35 TBSBPOOL, D-50 MAXTYPE1, D-36 TCPALVER, D-50 MCCSID, D-36 TCPKPALV, D-50 MINSTOR, D-37 TIME, D-51 MIXED, D-37 TIMELEN, D-51 MONSIZE, D-37 TSTAMP, D-51 MSVGP, D-37 UNIT, D-51 MSVGP2, D-37 UNIT2, D-51 NUMLKTS, D-37 URCHKTH, D-51 NUMLKUS, D-38 URLGWTH, D-52 OFFLOAD, D-38 UTIMOUT, D-52

Index–4 System Guide VDWQT command, D-52 modifications to backup Online History, 7-14 VPPSEQT, D-53 NSIGHTEX functions, A-2 VPSEQT, D-53 operator commands, 5-9 VPSIZE, D-53 parameters you can override, 5-40 WLMENV, D-54 Remote Access Facility parameters, 5-31 XLKUPDLT, D-54 reporting control parameters, 5-34 running without IFI, 5-20 COMMANDS member, 5-58, 5-59 Security, 6-2 Common Area Storage requirements, B-2 security parameters, 5-32 started task proc example, 5-6 COMPACT command, D-22 starting, 5-2 Components starting as a started task, 5-8 Unicenter CA-24X7, 9-1 startup requests, 5-41 stop mode, overriding, 5-40 CONDBAT command, D-23 stopping, 5-8 CONNECT= parameter, 5-50, 6-17 stopping mode, 5-24 trace record buffer parameters, 5-28 Console interface tracing parameters, 5-25 issuing commands, 5-13 verifying operation, 2-2 Constants Table, 5-41 virtual storage requirements, B-1 CONSTBL, 5-41 Data propagation enablement, D-27 CONTSTOR command, D-23 Data Set allocation parameters, 5-30 CSA allowance for IRLM lock storage, D-34 Database checking, D-24 CTHREAD command, D-23 DATA-SHARING= parameter, 5-37 cursor_with_hold DATE command, D-23 RELCURHL, D-40 Date length default, D-23 Date, default format, D-23 D DATE= parameter, 5-36 DATELEN command, D-23 data collector and the batch user interface, 5-71 DATEMD= parameter, 5-36 and the online user interfaces, 5-44 Dates archive parameters, 5-27 localization, 5-35 authorizing with eTrust CA-Top Secret Security, 3-3 automating the unload process, 8-8 DATETIME= parameter, 5-36 batch job JCL example, 5-2 Day abbreviations, 5-42 buffer sizes, 5-15 data set allocation parameters, 5-30 DAYS= parameter, 5-35 date and time parameters, 5-35 DB2 authorization cache size, D-19 DB2 usage, 5-14 dispatching priority, 5-4 DB2 authorization checking, D-19 exception monitor control parameters, 5-36 DB2 BIND PACKAGE authorization, D-19 history parameters, 5-27 how it works, 5-1 DB2 commands identification parameters, 5-22 use of authorization IDs, 6-28 initialization parameters, 5-21 DB2-COMMANDS=parameter, 6-19 migration parameters, 5-34 modifications for NATURAL for DB2 support, 4-29 DB2-LOCATION= parameter, 5-32

Index–5 DB2-MESSAGE-PRTLIM= parameter, 5-24 DEFAULT-CONSOLE-DEV= parameter, 5-25 DB2-MESSAGES= parameter, 6-19 DEFAULTS member, 5-58 DB2SSID member, 4-9, 4-35 DEFAULTS statement data collector, 5-21 DB2-TYPE= parameter, 5-37 DEFAULTS Statement, D-15 DB2VER= parameter, 5-35 user interface DBACRVW command, D-24 online, 5-48 DBATs maximum, D-35 deferred write threshold, D-27 DBCHK command, D-24 DEFIXTP command, D-25 DBGHDEST member, 5-58 DEFLTID command, D-25 security, 6-23 DBGPRINT DD statement, 5-47 DELLOG command, D-25 DBGSNAP DD statement, 5-24 DESCSTAT command, D-25 DBLOC= parameter, 4-26 DFHJCJFP utility, 3-10 DBPROTCL command, D-24 DFHJCT, 3-9 DBSUB= parameter, 4-26, 5-22, 5-72 DFHMCT, 3-8 DBWAIT= parameter, 5-22 DHCSVC module, 3-9 DC-DB2-STOP-MODE= parameter, 5-24 DISP= parameter, 5-30 DC-GROUP= parameter, 5-37 Dispatching priority DCMSGS= parameter, 5-23 data collector, 5-4 DD statements Display navigation, 5-60 batch user interface, 5-46 DBGSNAP, 5-24 Display transitions, 5-66 SYSABEND, 5-24 DISPLAY= parameter, 6-20 SYSDUMP, 5-24 SYSMDUMP, 5-24 DISPLAYSQL= parameter, 5-23 user interfaces, 5-46 Distributed Data Facility DDF resynchronization period, D-43 data collector parameter, 5-35 DDF= parameter, 5-35 Divide scale minimum, D-24 DDL and ART, D-44 DLDFREQ command, D-26 DDL validation, D-45 DLITOUT command, D-26 DEADLOK command, D-24 DMC threshold, D-19 DECARTH command, D-24 Double-byte character sets, D-37 DECDIV3 command, D-24 down level detection Decimal arithmetic default value, D-24 DLDFREQ command, D-26 DECIMAL command, D-25 DSMAX command, D-26 Decimal point DSN2EXT3 member, 4-30 default value, D-25 DSN3@ATH, 6-29, 6-30 Default menu, 6-4 DSN3AUTH routine, 3-3

Index–6 System Guide DSNALI23 member, 4-30 EXCEPTION-PROCESSOR= parameter, 5-36 DSNALI31 member, 4-30 EXCEPTION-TSO-SEND= parameters, 5-37 DSNALI41, 4-30 Exit routine replacment, D-41 DSNCEXT3 member, 4-30 Exit routines DSNCLI23 member, 4-30 security, 6-23 DSNCLI31 member, 4-30 EXITBAT, A-5 DSNCLI41, 4-30 EXITTSO, A-4 DSNDB06.SYSDBASE, C-2 EXPLAIN DSNDB06.SYSPLAN, C-2 use of authorization IDs, 6-28 DSNELI23 member, 4-30 EXPLAIN enablement, D-17 DSNELI31 member, 4-30 EXPLAIN= parameter, 6-18, 6-28 DSNELI41, 4-30 EXPLAIN-AUTHID= parameter, 5-34, 6-28 DSNWVSER trace writer, 4-28 EXPLAIN-PLAN-SYSIBM= parameter, 5-24 DSORG= parameter, 5-31 EXPLAIN-PLAN-USERQUAL= parameter, 5-24 DSSTIME command, D-26 Extended attributes controlling the use of, 5-51 DWQT command, D-27 EXTRAREQ command, D-28 DYNRULS command, D-27 EXTRASRV command, D-28 EXTSEC command, D-29 E

EDM Pool size, D-27 F EDMPOOL command, D-27 FILTERAC member, 7-13 EDPROP command, D-27 FORBIDDEN-IFCIDS= parameter, 5-34 ENFORCE-PREFIX= parameter, 5-31 FREE command, D-30 ENSCHEME command, D-28 FREE pageset eTrust CA-ACF2 security, 6-23 modifications for the VTAM user interface, 4-22 FROM/TO range, 9-4 eTrust CA-Top Secret Security authorizing the data collector, 3-3 FULLDUMP= parameter, 5-24 EVALUNC command, D-28 EXCEPTION DEFINITION= parameter, 6-24 G Exception processor data collector parameters, 5-35, 5-36 GCSSID command, D-30 EXCEPTION-DB-INTERVAL= parameters, 5-36 GDG see Generation Data Group, 3-7 EXCEPTION-DISPLAY= parameter, 6-24 Generation Data Group EXCEPTION-INTERVAL= parameter, 5-36 for data collector archiving, 3-7

Index–7 GETGSTAT IMOD, 5-80, 5-88 HISTARCH-TIME parameter, 8-8 Global Subsystem HISTARCH-TIME= parameter, 5-28 DASD space requirements, 4-3 HIST-CPUPARA-CHILD= parameter, 5-28 dependencies, 4-2 installation, 4-1 HIST-DISPLAY-COUNT= parameter, 5-27 installation checklist, 4-2

installation naming conventions, 4-3 HISTORY= parameter, 5-27, 6-19, 7-4 installation verification, 4-11 HISTORY-ACCT= parameter, 5-27, 7-4, 7-5 installation worksheet, 4-4 LINKLIB APF authorization, 4-6 HISTORY-COMPRESSION= parameter, 5-28 modifications for System Condition Monitor, 5-84 HISTORY-MESSAGE-TIME= parameter, 5-27 starting and stopping, 4-11 HISTORY-STATS= parameter, 7-4 GNETLOG DD statement, 4-9 HISTORY-STATS-TIME= parameter, 5-27 Goalnet, 4-9, 4-10 HISTORY-SWITCH= parameter, 6-23 Graphics character code ID value, D-30 HOPAUTH command, D-31 GSS, 4-8 enabling, 4-14 HPSEQT command, D-31 GSSCLIST member, 4-12 HPSIZE command, D-31 GSSDLETE member, 4-6 HSM recall, D-40 time to wait, D-40 GSSEDIT member, 4-5 GSSIDUMP, D-13 GSSILOG member, 4-7 I

GSSIMOD member, 4-7 IDB2ARC member, 8-3, 8-8, 8-11 GSSRUNP member, 4-10, 4-34 IDB2BUJ1 member, 5-74 GSSSPARM member, 4-10 IDB2BUJ2 member, 5-74 GSSUNLD member, 4-5 IDB2BUJ3 member, 5-72 IDB2DCJ member, 5-2 H IDB2DCS member, 5-6 IDB2LSJ member, D-5 Help in the online user interface, 5-58 IDB2LTBL member, 4-26 hiperpool sequential steal threshold, D-31 IDB2MEXC IMOD, 5-80 Hiperpool size, D-31 IDB2PCJ member, 5-75 HISTARCH-ACCT-TASK parameter, 8-8 IDB2PCS member, 5-77 HISTARCH-ACCT-TASK= parameter, 5-28 IDB2SSJ member, C-4, C-5 HISTARCH-STATS-TASK parameter, 8-8 IDB2UCJ member, D-8 HISTARCH-STATS-TASK= parameter, 5-28 IDB2UNLD member, D-10 HISTARCH-TASK parameter, 8-8 IDB2VUJ member, 5-55 HISTARCH-TASK= parameter, 5-28 IDB2VUS member, 5-55

Index–8 System Guide IDBACK command, D-31 Installation, 9-2 Archive requirements, 8-6 IDDCPRMS member, 4-34 Global Subsystem, 4-1 IDFORE command, D-32 NATURAL for DB2 support, 4-27 Remote Access Facility, 4-23 IDGDG member, 8-11 System Condition Monitor, 4-34 idle thread timeout interval, D-32 Instrumentation Facility Interface IDOBLOAD member, D-3 data collector usage, 5-15 IDRWPRMS member, 8-11 Interval Statistics records activating Online History collection, 7-4 IDSTMTS member, C-3, C-4 Online History, 7-3 IDTHTOIN command, D-32 IQL Request IDUIPRMS LOGON-CHECK= parameter, 4-17 library, 5-52 IDXBPOOL command, D-32 IRLM resource timeout value, D-32 IEAAPFxx member, 4-6 IRLMRWT command, D-32 If IFI= parameter, 5-29 ISERVE Editor installing as an ISPF application, 4-11 IFCID2-NOTIFI parameter, 5-26 ISPF Menu, 5-52 IFI see Instrumentation Facility Interface, 5-15 IUIMAPS DD statement, 5-46 IFI command, 5-10 IUIMAPS library, 5-58 IFI= parameter, 5-26 IUIMAPS library members COMMANDS, 5-59 ILOG data set creation, 4-7 DBGHDEST, 5-58 ILOG dump to data set utility, D-13 DEFAULTS, 5-58 PFKEYS, 5-60 IMOD data sets building using GSSSPARM, 4-10 IUIUPL member, A-1 creation, 4-7 IMODs $DB2CLNUP, 5-85 L data set, 5-83 GETGSTAT, 5-80, 5-88 LC_CTYPE command, D-32 IDB2MEXC, 5-80 LCLPSWD= parameter, 5-49 modifying the Definition, 5-85 modifying the Exception, 5-87 LEMAX command, D-33 modifying the Message, 5-87 Linking requests, 5-68 setup for editing, 4-11 VTAMEXC, 5-88 LIST-BROWSE-EDIT= parameter, 6-22 INITBAT, A-5 LOAD library members DSNALI23, 4-30 INITTSO, A-4 DSNALI31, 4-30 INITUSER, A-2 DSNCLI23, 4-30 DSNCLI31, 4-30 INSIGHT-COMMANDS= parameter, 6-19 DSNELI23, 4-30 INSPLIB library, 5-58 DSNELI31, 4-30

Index–9 Load Statement Generator utility, D-3 invocation, 5-65 MGATTACH, 5-62 LOBVALA command, D-33 MGMSGS, 5-62 LOBVALS command, D-33 MGPROBE, 5-63 MGSYSHST, 5-63 locking MGSYSTEM, 5-63 while using repeatable read, D-46 MGTHDHST, 5-63 Log data sets MGTHREAD, 5-63 unloading active, D-38 Security file access, 6-23 syntax, 5-63 Log records written between checkpoints, D-34 MGATTACH Menu-Group, 5-62 LOGAPSTG command, D-33 MGMSGS Menu-Group, 5-62 LOGLOAD command, D-34 MGPROBE Menu-Group, 5-63 LOGOFF, A-5 MGSYSHST Menu-Group, 5-63 LOGON, A-4 MGSYSTEM member, 5-61 LOGON command, 4-23 MGSYSTEM Menu-Group, 5-63 LOGON-CHECK= parameter, 5-50, 5-57 MGSYSTEM request, 5-69 MGTHDHST Menu-Group, 5-63 M MGTHREAD Menu-Group, 5-63

MAKEEX member, A-2 Migration data collector parameters, 5-34 Map Title Step 4. Copy GSSRC Module to the Load Library, minimize working storage 4-6 MINSTOR, D-37 MAXALLC command, D-34 MINSTOR command, D-37 MAXARCH command, D-34 MIXED command, D-37 MAXCSA command, D-34 Monitor trace buffer size, D-37 MAXDBAT command, D-35 MONSIZE command, D-37 Maximum number of users, D-23 Month abbreviations, 5-42 MAX-REQUEST-TIME= parameter, 5-33, 6-21 MONTHS= parameter, 5-36 MAX-TRACE-RECORDS= parameter, 5-33, 6-21 MSSUB= parameter, 5-23, 5-50 MAXTYPE1 command, D-36 MSVGP command, D-37 MAXUTASKS= parameter, 5-23 MSVGP2 command, D-37 MCCSID command, D-36 Multiple subsystems and archiving, 8-10 menu data set, 5-53, 5-54, 5-57, 6-4, 6-5, 6-15 MVS-COMMANDS= parameter, 6-23 MENU= parameter, 6-22 MVS-DISPLAY= parameter, 6-23 Menu-Groups context, 5-67 customization, 5-62 defining a Probe request, 5-66 introduction, 5-62

Index–10 System Guide N computing control intervals System Statistics, 7-8 Thread Accounting, 7-10 NATURAL for DB2 support data collector parameters, 5-27 CICS modifications, 4-29 data set size, 7-5 data collector modifications, 4-29 data sets, 7-1 data collector parameter, 5-35 data types stored, 7-2 installation, 4-27 determining data set sizes, 7-6 installation checklist, 4-28 estimating record sizes modifications for IMS, 4-31 System Statistics, 7-7 PC Owner modifications, 4-29 Thread Accounting, 7-9 NATURAL-DB2= parameter, 5-35 filtering Thread Accounting records, 7-12 maximum record sizes Navigation of panels, 5-60 System Statistics, 7-9 NON-DISPLAY= parameter, 6-24 maxiumum record sizes Thread Accounting, 7-11 NONSTOP= parameter, 5-23 Security file access, 6-19 NSIGHTEX User Exit, 5-57, 6-4, 6-14 unload to sequential file, D-10 assembly and link-editing, A-2 unloading for archiving, 8-7 batch user interface functions, A-5 OP buffer, 5-15 data collector functions, A-2 exit characteristics, A-1 Operator commands location, A-1 data collector, 5-9 NSIGHTEX member, 5-56 OPn buffer, 3-4 TSO user interface functions, A-3 VTAM user interface functions, A-4 OPTHINTS command, D-38 NSIGHTRW member, D-4 OUTBUFF command, D-38 NUMLKTS command, D-37 Output buffers, B-4 NUMLKUS command, D-38 NUMTRACES= parameter, 5-26 P NUMUTASKS= parameter, 5-23 Package owner ID, D-31 Page locks O maximum concurrent, D-37 maximum concurrent per user, D-38 OBID translation utility, D-1 Pageset OBID-REFRESH= parameter, 6-18 free of users, D-30 OCCUR= parameter, 5-73 PANEL CHARACTER= parameter, 6-22 OFFLOAD command, D-38 Panel libraries, 5-57 OJPERFEH command, D-38 Panel navigation, 5-60 Online History Panels activating collection, 7-4 Unicenter CA-24X7 Schedules, 9-6 archiving data, 8-2 Parallel sequential steal threshold, D-53 backing up, 7-14 PARAMDEG command, D-39

Index–11 Parameters PROBE-SQL-TRACE= parameter, 6-22 data collector, 5-21 Product commands, 5-59 user interface online, 5-47 Profile X247, 6-23, 9-2 Security definition, 6-6 X247CTHD, 6-23, 9-2

X247SEC, 6-23, 9-2 PROTECT command, D-39

Password validation PRTCT= parameter, 4-25 user interface parameter, 5-50 PRV buffer, 5-16 PC Owner PRVBUFNUM= parameter, 5-29 batch job sample JCL, 5-75 modifications for NATURAL for DB2 support, 4-29 PRVMAXSZ parameter, 5-15 operation, 5-75 PRVMAXSZ= parameter, 5-30 started task sample JCL, 5-77 starting PTASKROL command, D-40 stopping and restarting, 5-78 troubleshooting, 5-79 Q verifying operation, 2-2 PCLOSEN command, D-39 QUIESCE command, D-40 PCLOSET command, D-39 PCSSID= parameter, 5-34, 5-50, 5-78 R Performance Trace Classes, 5-18 RACF PF Keys and DB2 commands, 6-30 labeling, 5-60 and EXPLAIN, 6-30 PFKEYS member, 5-60 Connect Group prefixes and associated menus, 5-53 Security ID, 6-4 PLAN= parameter, 6-17 RACROUTE, 4-22 PLAN-AUTH-ONLY= parameter, 6-23 RACROUTE CREATE, 6-29 POOLINAC command, D-39 RAF= parameter, 5-32 PREFIX= parameter, 5-31 RAFCDRM member, 4-25 Primary menus, 2-4 RAFCDRSC member, 4-25 PRIMARY= parameter, 5-31 RAFDCAPP member, 4-24 PRINT-DESTINATION1= parameter, 5-50 RAF-RUSIZE= parameter, 5-32 PRINT-DESTINATION2= parameter, 5-50 RAFUIAPP member, 4-24 PRINT-REQUESTS= parameter, 5-35 READA-BUFFER-PCT= parameter, 5-26 PRIQTY command, D-39 RECALL command, D-40 private buffers, 5-16 RECALLD command, D-40 Probe definition in Menu-Groups, 5-66 Registered objects qualified names, D-45 PROBE-DETAIL= parameter, 5-73, 6-22 RELCURHL command, D-40

Index–12 System Guide Remote Access Facility RGFFULLQ command, D-45 canceling a user, 5-11 RGFINSTL command, D-45 commands, 5-12 data collector parameters, 5-31 RLF= parameter, 5-35 installation, 4-23 installation checklist, 4-24 RLFAUTH command, D-45 specifying the local password, 5-49 RLFERRD command, D-46 starting, 5-12 stopping, 5-12 RLFTBL command, D-46 user interface parameters, 5-49 RRULOCK command, D-46 VTAM preparation, 4-24 RUSIZES Remote concurrent users, D-23 Remote Access Facility, 4-26 REPEAT= parameter, 5-49

REPLACE command, D-41 S REQLIB= parameter, 5-23 REQUEST= parameter, 5-72 Sample JCL batch utility, D-14 REQUEST-LIBRARY= parameter, 6-22 SCCSID command, D-47 requests linking, 5-68 SCHEDULE member, 9-3 MGSYSTEM, 5-69 Scheduler Requests command syntax, 9-3 startup list, 5-41 description, 9-2 examples, 9-5 REQUESTS DD statement, 5-46 invoking, 9-3 REQUESTS library members viewing schedules online, 9-6 FILTERAC, 7-13 SCM-IMOD-NAME= parameter, 4-34, 4-36, 5-37 MGSYSTEM, 5-61 Screen requirements see Panel, 5-60 batch user interface, 5-71 SECONDARY= parameter, 5-31 Requirements Archiving, 8-6 SECQTY command, D-47 Common Area Storage, B-2 Security, 9-2 user interface controls, 6-2 online, 5-45 data collector parameters, 5-32 Resource Limit Facility exit checking, 6-5 data collector parameter, 5-35 ID List example, 6-14 default action for remote threads, D-46 ID List syntax, 6-14 operation, 6-4 Resource Limit Table options, 6-1 default authorization ID, D-45 overview, 6-1 Resource Limit table suffix value, D-46 refreshing parameters, 6-6 TSO user interface, 5-52 RESTRICTED-IFCIDS= parameter, 5-33 VTAM user interface, 5-57 RESYNC command, D-43 RGFDEDPL command, D-44

Index–13 Security file GSSIMOD, 4-7 components, 6-6 GSSRUNP, 4-10, 4-34 initialization overview, 6-27 GSSSPARM, 4-10 keywords, 6-17 GSSUNLD, 4-5 user groups, 6-25 IDB2ARC, 8-3, 8-8, 8-11 validation, 6-27 IDB2BUJ1, 5-74 IDB2BUJ2, 5-74 Security ID validation, 5-53 IDB2BUJ3, 5-72 SECURITY member, 6-7 IDB2DCJ, 5-2 IDB2DCS, 5-6

SECURITY= parameter, 5-33, 6-3 IDB2LSJ, D-5 SECURITY-EXIT= parameter, 5-33, 5-50, 5-72 IDB2LTBL, 4-26 IDB2PCJ, 5-75 SECURITY-FILE= parameter, 5-50 IDB2PCS, 5-77 SECURITY-REFRESH= parameter, 6-17 IDB2SSJ, C-4, C-5 IDB2UCJ, D-8 SELECT= parameter, 5-66 IDB2UNLD, D-10 SEQCACH command, D-47 IDB2VUJ, 5-55 IDB2VUS, 5-55 SET statement, D-16 IDDCPRMS, 4-34

Shadow Tables IDGDG, 8-11

creating, C-4 IDOBLOAD, D-3

explanation, C-1 IDRWPRMS, 8-11

synchronizing with DB2 catalog, C-5 IDSTMTS, C-3, C-4 IUIUPL, A-1 SHOW= parameter, 6-20 MAKEEX, A-2 NSIGHTEX, 5-56 Single-byte character code ID value, D-47 NSIGHTRW, D-4 Site type, D-47 RAFCDRM, 4-25 RAFCDRSC, 4-25 SITETYP command, D-47 RAFDCAPP, 4-24 SMF data sets, 3-5 RAFUIAPP, 4-24 SECURITY, 6-7 SNAP dump, 5-24 STARTUP, 4-35, 5-41 Sort pool USSDEF, 5-55 maximum size, D-47 SPACETYPE= parameter, 5-30 SOURCE library members SQL default delimiter, D-47 $ARCCOPY, 8-10 $ARCDDL, 8-6 SQL rules, D-48 ARCCOPY, 8-10 SQL statement ARCDDL, 8-3, 8-8, 8-10 cancelling, D-21 ARCLxxxx, 8-11 ARCSPACE, 8-11 SQLDELI command, D-47 ARCSQL, 8-9, 8-11 SQL-WAIT-INTERVAL= parameter, 5-24 ARCSQLD, 8-4, 8-11 COMMANDS, 5-58 SRTPOOL command, D-47 DB2SSID, 4-9, 4-35

DSN2EXT3, 4-30 SRV buffer, 5-15 DSNCEXT3, 4-30 SRVBUFNUM parameter, 5-15 GSSDLETE, 4-6 GSSEDIT, 4-5 SRVBUFNUM= parameter, 5-29 GSSILOG, 4-7 SRVBUFSZ parameter, 5-15

Index–14 System Guide SRVBUFSZ= parameter, 5-29 SYS1.PARMLIB, 4-8 START= parameter, 6-20 SYS1.VTAMLST, 4-24, 4-35, 5-54 START-24X7= parameter, 5-25 SYSABEND DD statement, 5-24 START-HISTORY-FILTER= parameter, 6-22 SYSADM command, D-49 START-MENU-GROUP= parameter, 6-23 SYSADM commands security, 6-23 START-MULTIPLE= parameter, 6-21 SYSADM ID 1 value, D-49 START-QUALIFY= parameter, 5-73 SYSADM ID 2 value, D-49 STARTREQ, A-3 SYSADM2 command, D-49 STARTUP member, 4-35, 5-41 SYSIBM.SYSCOLUMNS, C-3 Startup Requests, 5-41 SYSIBM.SYSDBRM, C-1, C-3 START-WILDCARD= parameter, 6-22 SYSIBM.SYSINDEXES, C-3 Statements DEFAULTS, D-15 SYSIBM.SYSKEYS, C-1, C-3 SET, D-16 SYSIBM.SYSPACKAGE, C-3 STATHIST command, D-48 SYSIBM.SYSPACKLIST, C-3 STATIME command, D-48 SYSIBM.SYSPACKSTMT, C-3 Statistics trace time interval, D-48 SYSIBM.SYSPLAN, C-3 STATROLL command, D-48 SYSIBM.SYSSTMT, C-1, C-3 STATUS= parameter, 5-30 SYSIBM.SYSSYNONYMS, C-3 STDSQL command, D-48 SYSIBM.SYSTABLES, C-3 STIMER= parameter, 5-78 SYSIBM.SYSTABLESPACE, C-3 stopping mode, 5-24 SYSMDUMP DD statement, 5-24 STOP-REQUESTS= parameter, 5-50 SYSOPR ID 1 value, D-50 Stored procedures SYSOPR ID 2 value, D-50 STORMXAB command, D-48 STORPROC command, D-49 SYSOPR1 command, D-50 STORTIME command, D-49 SYSOPR1 commands STORMXAB command, D-48 security, 6-23 STORPROC command, D-49 SYSOPR2 command, D-50 STORTIME command, D-49 SYSOUT= parameter, 5-31 Subsystem name SYSPARMS DD statement, 5-46 GOAL, 4-8 ISRV, 4-8 System Condition Monitor aging time, 5-81 SUMMARIZE Request table sizes, B-5 cleanup time, 5-81 color, 5-80 SUPERRS command, D-49 customization, 5-80 SYNCVAL command, D-49 data collector parameter, 5-37 enable cleanup IMOD, 4-36 SYS1.MANx data sets, 3-4 enabling CICS monitoring, 4-35

Index–15 exception/message lifetime, 5-80 Trace record buffers Global View panel, 4-36 data collector parameters, 5-28 installation, 4-34 Traces installation checklist, 4-34 classes, 5-17 installing additional products, 5-84 data collector parameters, 5-25 VTAM user interface modifications, 4-35 destination, 5-16 System Snapshot panel, 2-4 monitor definition, 5-17 performance definition, 5-16 SYSTEM-CONDITION-MONITOR= parameter, 6-23 qualified, 5-19 SYSUDUMP DD statement, 5-24 types, 5-16 TRUNCTIME= parameter, 5-30 T TSO foreground users maximum number, D-32

TBSBPOOL command, D-50 TSO user interface accessing, 5-52 TCPALVER command, D-50 canceling a user, 5-11 TCPKPALV command, D-50 DD statements, 5-46 invoking through ISPF CLIST, 5-51 TERMINAL= parameter, 5-51 IQL request library, 5-52 TESTVER= parameter, 5-34, 5-50, 5-73 ISPF menu, 5-52 listing users currently logged on, 5-9 Thread Accounting records NSIGHTEX functions, A-3 activating Online History collection, 7-4 security, 5-52 filtering for Online History, 7-12 verifying operation, 2-2 Online History, 7-3 TSTAMP command, D-51 Thread active/inactive, D-22 Threads security for canceling, 6-23 U Time local time default length, D-51 Unicenter CA-24X7 components, 9-1 TIME command, D-51 installation, 9-2 Time format Scheduler, 9-2 default, D-51 scheduler command syntax, 9-3 security, 9-2 TIME= parameter, 5-36 Unicenter CA-24X7 functions TIMED2= parameter, 5-36 security, 6-23 TIMELEN command, D-51 Unicenter CA-24X7 Schedules panel, 9-6 Times Unicenter CA-SYSVIEW localization, 5-35 enabling, 4-14 TIMESS= parameter, 5-36 UNICENTER-AGENT= parameter, 5-38 Timestamp UNIPMP-DEBUG= parameter, 5-39 Archive Log data sets, D-51 UNIPMP-ENABLED= parameter, 5-39 Trace buffer statistics displaying, 5-10 UNIPMP-INTERVAL= parameter, 5-40 UNIPMP-SSID= parameter, 5-39

Index–16 System Guide UNIT command, D-51 V UNIT= parameter, 5-31 VDWQT command, D-52 UNIT2 command, D-51 Vertical deferred write threshold, D-52 UPMPAPPL IQL member, 11-6 View Bar customization, 5-61 UPMPBTAP IQL member, 11-6 Virtual pool UPMPBTSS IQL member, 11-6 parallel sequential steal threshold, D-53 UPMPSSBP IQL member, 11-6 sequential steal threshold, D-53 UPMPSYS IQL member, 11-6 Virtual Storage SUMMARIZE Request table sizes, B-5 Uppercase translation table, 5-43 VPPSEQT command, D-53 UPPER-CASE= parameter, 5-49 VPSEQT command, D-53 URCHKTH command, D-51 VPSIZE command, D-53 URLGWTH command, D-52 VTAM User ID preparation for the Remote Access Facility, 4-24 default value, D-25 VTAM user interface, 4-15, 4-17 User ID validation, 5-52 accessing Unicenter CA-Insight, 5-56 user interface canceling a user, 5-11 online, 5-44 CA-Top Secret modifications, 4-21 and the data collector, 5-44 data collector User ID, 5-45 customizing, 5-57 DD statements, 5-46 DD statements, 5-46 defining as a Master Facility, 4-21 default values, 5-58 eTrust CA-ACF2 modifications, 4-22 Help navigation, 5-58 listing users currently logged on, 5-9 interaction with Menu-Groups, 5-65 logging on, 4-23 parameters, 5-47 modifications for the System Condition Monitor, requirements, 5-45 4-35 Security file access, 6-15 NSIGHTEX functions, A-4 security, 6-3 requirements, 5-45 security control, 5-57 USER= parameter, 4-21 starting, 5-55 Users stopping, 5-56 maximum number, D-23 User ID for data collector, 5-45 maximum number of batch DB2, D-31 VTAM Definitions, 5-54 remote concurrent, D-23 VTAMEXC IMOD, 5-88 USSDEF member, 4-16, 5-55 Utilities IDB2OBI, D-1 W IDB2UNLD, D-9 Load Statement Generator, D-3 Wildcard characters NSIGHTRW, D-3 use in Security, 6-22 OBID Translation, D-1 WLMENV command, D-54 Online History Data Set Unload, D-9 Worksheet Utility timeout factor, D-52 Global Subsystem installation, 4-4 UTIMOUT command, D-52 WTO-NOTIFY= parameter, 6-21

Index–17 X X247SEC parameter, 6-23, 9-2 XLKUPDLT command, D-54 X247 parameter, 6-23, 9-2 X247CTHD parameter, 6-23, 9-2

Index–18 System Guide